[FR] KeyError: 'Accessing samples by numeric index is not supported. Use sample IDs, filepaths, slices, boolean arrays, or a boolean ViewExpression instead'

Proposal Summary
It would be great if I can index into the dataset
Motivation

integer indexing into the dataset
Why is this use case valuable to support for FiftyOne users in general?
Why is this use case valuable to support for your project(s) or organization?
Why is it currently difficult to achieve this use case?

What areas of FiftyOne does this feature affect?

[ ] App: FiftyOne application
[x] Core: Core fiftyone Python library
[ ] Server: FiftyOne server

Details
import fiftyone as fo
import fiftyone.zoo as foz

dataset = foz.load_zoo_dataset("quickstart")
# randomly sample an item from the dataset
dataset[torch.randint(low=0, high=len(dataset), size=(1,1)).item()]

gives KeyError: 'Accessing samples by numeric index is not supported. Use sample IDs, filepaths, slices, boolean arrays, or a boolean ViewExpression instead'. Converting the integer index to ids or to boolean arrays is just one extra unnecessary step
Willingness to contribute
The FiftyOne Community welcomes contributions! Would you or another member of your organization be willing to contribute an implementation of this feature?

[x] Yes. I can contribute this feature independently
[ ] Yes. I would be willing to contribute this feature with guidance from the FiftyOne community
[ ] No. I cannot contribute this feature at this time

Thank you for your interest and use of fiftyone @zshn25 !
Yes thank you for commenting @gboeer.
That's right, integer indexing is not intended to be supported because there is no guaranteed order so integer indexing is theoretically meaningless. However in practice the samples almost always retain the order because of the current implementation using MongoDB. Which is why it can be tempting to think in this manner.
Indexing by filepaths or IDs is supported because these are unique and always database-indexed (read: fast). So the referenced sample is the same one every time.
Using filters or view expression indexing is always supported because this is often the best way to think about your data - in "views" of the dataset with various filters rather than immutable sets of samples.
In addition to what Gordon suggests, if you really must use torch.randint instead of dataset.take, then you could do this if you want.
rand_index = torch.randint(low=0, high=len(dataset), size=(1,1)).item()
sample = dataset[rand_index: rand_index + 1].first()

Closing this issue. Please feel free to reply here, or join our Slack community, for further discussion.


Random Wording and Grammar Fixes

Just fixed a few inconsistent wordings and a couple of grammar issues as I worked through the koans.

Hey there.
It looks amazing. I'm merging your PR.
Thanks for contributing. Have a nice day! :)


VRTK_UI_Pointer doesn't respect gameobject colliders

If there's a worldspace UI behind a gameobject with collider, the simple pointer will stop at the collider but the UI elements behind it are still hit/highlighted.
To replicate, open Scene 034 (InteractingWithUnityUI), and add a collider (or a whirlygig object from scene 19, or whatever) in front of the WorldKeyboard.  You can see that the laser pointer correctly terminates on the surface of the collider, but that the UI Button elements behind are still being hit and highlighted.
This is particularly problematic for scenes where pointing to and using a gameobject opens up a UI panel.  If any button happens to appear behind the gameobject's collider, but still in view of the raycast, their click event is also fired immediately (even though the user only intended to open the panel, not also push a random button too).
I imagine this has something to do with UIPointer and SimplePointer BOTH firing a raycast, and not knowing about one other?

You can set the raycast blocking object on the Graphics Raycast component of the event system.
If you look at the Unity docs at:
https://docs.unity3d.com/Manual/script-GraphicRaycaster.html
You'll see it has a Blocking Objects setting. If you set this accordingly then the UI raycast will not pass through 3d objects.
The simple pointer has nothing to do with the UI pointer and is purely used as a visual aid. You can use the UI pointer without the simple pointer to interact with UI elements and therefore you need to specify the Blocking Objects on the Graphics Raycast to adhere to Unity standards.

Thanks for the response. I learned something new!  However, I am still
seeing the issue occur when the blocking object is close enough to GUI
elements. To replicate:

Open Scene 34
Set "Canvas" position = (0, 0, 0)
Create a cube w/ collider. Set position = (0.3, 1, 0), scale = (0.2,
0.2, 0.2)

At runtime, if you aim at the cube from the correct angle, the raycast
passes through and highlights buttons behind it.
On Wed, Aug 31, 2016 at 1:51 AM StoneFox<EMAIL_ADDRESS>wrote:

You can set the raycast blocking object on the Graphics Raycast component
of the event system.
If you look at the Unity docs at:
https://docs.unity3d.com/Manual/script-GraphicRaycaster.html
You'll see it has a Blocking Objects setting. If you set this accordingly
then the UI raycast will not pass through 3d objects.
The simple pointer has nothing to do with the UI pointer and is purely
used as a visual aid. You can use the UI pointer without the simple pointer
to interact with UI elements and therefore you need to specify the Blocking
Objects on the Graphics Raycast to adhere to Unity standards.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/thestonefox/SteamVR_Unity_Toolkit/issues/485#issuecomment-243686290,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AMwOAzUujPgK8LWHPS3ZhhAE-tt4hL1Sks5qlTJ9gaJpZM4JxC0_
.

Okay, I think I found the issue.  At runtime, GraphicRaycaster is copied then deactivated, and a VRTK_UIGraphicRaycaster component is added in its place.  This class has a private constant UI_CONTROL_OFFSET which is set to 0.5f .  What's the purpose of this?

I'll look into this further and treat this as a bug

I think UI_CONTROL_OFFSET was originally there to fix an old issue that has subsequently been resolved another way. I'm going to make a commit that removes the need for it as it fixes your issue and it's redundant anyway (i believe)

Fixed with https://github.com/thestonefox/SteamVR_Unity_Toolkit/commit/284a5adc03a49e2544bb56475514bac79a45bcd4


v5.2.1 not in PyPi

I noticed that with the 5.2.1 release, the build for PyPi failed (https://github.com/jazzband/djangorestframework-simplejwt/actions/runs/3050912664). I'm guessing the change I made (#600) required a locale update anyways (sorry 😞). What should the next steps be? Update the locales so 5.2.2 can be released instead?

thanks for the catch! since we never released 5.2.1 on pypi, i usually just delete the GitHub release.


Automator: update istio/client-go@master dependency in istio/istio@master

Generated by Automator - 2023-10-16T01:58:00+00:00

@istio-testing: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
61062378eb4b76fba2488165e28f0338083bd05a
link
true
/test unit-tests-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
61062378eb4b76fba2488165e28f0338083bd05a
link
true
/test unit-tests-arm64

unit-tests_istio
61062378eb4b76fba2488165e28f0338083bd05a
link
true
/test unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
61062378eb4b76fba2488165e28f0338083bd05a
link
true
/test unit-tests-arm64

unit-tests_istio
61062378eb4b76fba2488165e28f0338083bd05a
link
true
/test unit-tests

integ-pilot-istiodremote_istio
61062378eb4b76fba2488165e28f0338083bd05a
link
true
/test integ-pilot-istiodremote

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
61062378eb4b76fba2488165e28f0338083bd05a
link
true
/test unit-tests-arm64

unit-tests_istio
61062378eb4b76fba2488165e28f0338083bd05a
link
true
/test unit-tests

integ-pilot-istiodremote_istio
61062378eb4b76fba2488165e28f0338083bd05a
link
true
/test integ-pilot-istiodremote

integ-cni_istio
61062378eb4b76fba2488165e28f0338083bd05a
link
true
/test integ-cni

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
61062378eb4b76fba2488165e28f0338083bd05a
link
true
/test unit-tests-arm64

unit-tests_istio
61062378eb4b76fba2488165e28f0338083bd05a
link
true
/test unit-tests

integ-pilot-istiodremote_istio
61062378eb4b76fba2488165e28f0338083bd05a
link
true
/test integ-pilot-istiodremote

integ-cni_istio
61062378eb4b76fba2488165e28f0338083bd05a
link
true
/test integ-cni

integ-pilot-multicluster_istio
61062378eb4b76fba2488165e28f0338083bd05a
link
true
/test integ-pilot-multicluster

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
61062378eb4b76fba2488165e28f0338083bd05a
link
true
/test unit-tests-arm64

unit-tests_istio
61062378eb4b76fba2488165e28f0338083bd05a
link
true
/test unit-tests

integ-pilot-istiodremote_istio
61062378eb4b76fba2488165e28f0338083bd05a
link
true
/test integ-pilot-istiodremote

integ-cni_istio
61062378eb4b76fba2488165e28f0338083bd05a
link
true
/test integ-cni

integ-pilot-multicluster_istio
61062378eb4b76fba2488165e28f0338083bd05a
link
true
/test integ-pilot-multicluster

integ-pilot_istio
61062378eb4b76fba2488165e28f0338083bd05a
link
true
/test integ-pilot

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
61062378eb4b76fba2488165e28f0338083bd05a
link
true
/test unit-tests-arm64

unit-tests_istio
61062378eb4b76fba2488165e28f0338083bd05a
link
true
/test unit-tests

integ-pilot-istiodremote_istio
61062378eb4b76fba2488165e28f0338083bd05a
link
true
/test integ-pilot-istiodremote

integ-cni_istio
61062378eb4b76fba2488165e28f0338083bd05a
link
true
/test integ-cni

integ-pilot-multicluster_istio
61062378eb4b76fba2488165e28f0338083bd05a
link
true
/test integ-pilot-multicluster

integ-pilot_istio
61062378eb4b76fba2488165e28f0338083bd05a
link
true
/test integ-pilot

integ-pilot-istiodremote-mc_istio
61062378eb4b76fba2488165e28f0338083bd05a
link
true
/test integ-pilot-istiodremote-mc

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

This one cannot be done automatically since it involves tests failure. We've already making manual updating.

https://github.com/istio/istio/pull/47364 and https://github.com/istio/istio/pull/47261


errors: no obvious way to map error to errno values

go version go1.11.2 linux/amd64
I'm writing some Go code that is called by C code, and I find there's no obvious way to map an error value to a Unix errno value.  For example, at one point I write:
        n, err := conn.WriteToUDP(data, &addr)
	if err != nil {
		e := unix.EIO
		if os.IsTimeout(err) {
			e = unix.EAGAIN
		}
                C.set_errno(e)
                return -1
       }

While that keeps the code working, it obviously loses a lot of the error granularity.  Given that the errno value must be available somewhere under the hood, it's infuriating that it's not exported.
(I'd envision for example an interface with a single method ToOsInteger and that is implemented for those errors for which it makes sense to map to a Unix errno.)

Thanks a lot for your code, that seems to do the trick.  Still, would you agree that this is not something you'd expect the average Go programmer to discover on his own?  And that this should either be encapsulated in a standard library function, or at least documented?

Still, would you agree that this is not something you'd expect the average Go programmer to discover on his own?

Fair point that it would require a little bit more digging than usual, which is why I mentioned this perhaps being a docs discovery issue.
Adding it to the standard library is something to consider carefully because how many people have encountered this issue? It is a cross-package utilitiy i.e. os, syscall, it involves error introspection. But also adding it in means that its signature has to be kept intact. for the lifetime of a GoX series which can be decades
I think that what we can do is, please distill this issue into an "Experience Report" https://github.com/golang/go/wiki/ExperienceReports which will help a lot with informing the design process as we proceed towards Go2.
The "Experience Report" could be a blogpost or Github Gist and then add it to that linked listing, share it with your friends, gather feedback, and the Go maintainers will take a look. Such feedback is highly valuable and will also help with errors redesign (/cc @mpvl)
Concurrently with the report, you can create a small library that does this translation and once we have a tangible reference that's used with various applications but also demonstrates demand, that makes it really easy for decisions into including into the standard library.

Adding it to the standard library is something to consider carefully

That makes perfect sense.  (Please take it literally -- I'm not sure whether I agree, but your argument definitely makes sense.)
(I'm not quite sure whether to close this issue — on the one hand, you've solved my immediate technical problem, for which thanks; on the other hand, I still think there's a documentation problem somewhere.)

(I'm not quite sure whether to close this issue — on the one hand, you've solved my immediate technical problem, for which thanks; on the other hand, I still think there's a documentation problem somewhere.)

Given that this is an issue that isn't frequently reported and that we have solved it, let's close it. However, as I had suggested in https://github.com/golang/go/issues/29054#issuecomment-443468911 whenever you get some free time, please write an "Experience Report" and share it on the wiki, on golang-nuts, social media etc. In this issue I've also paged some interested parties and as we work towards Go2, the feedback will be considered towards the next design.

I don't see how a SysErr() or Errno() method fits in the scope of either Go 2 Error Values or Error Handling, as it's specific to errors stemming from syscalls.
https://go.googlesource.com/proposal/+/master/design/go2draft.md
It looks to me like a method of net.Error, os.PathError, and similar types, or a new interface type. And the solution above looks to me like it could be brittle.
I'd suggest leaving it open, with title "proposal: Go2: add SysErr interface type" and tag Go2. That's the common approach to gaps in the stdlib.

I think this issue is reasonably addressed by error.As in the current error design draft (see https://go.googlesource.com/proposal/+/master/design/go2draft.md).

@networkimprov: Wanting a C errno means you want platform-specific details which means you're dealing with the syscall package, that sounds very reasonable. Consider lack of Errno in https://golang.org/pkg/syscall/?GOOS=plan9


Improve readme screenshot and icon

Fixes #.
Improve calculator screenshot by moving it to the center for more awesomeness
Description of the changes:

Added icon
Centered screenshot

How changes were validated:
Simply take a look at the README

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: e-minguez sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

@e-minguez - Please let me know if you intend to provide a follow-up to this PR and sign the CLA (Contributor License Agreement), or if I should close this PR out.  Thanks!

Closing out this pull request due to no updates and a failure to sign the required CLA.  @e-minguez, we can definitely reactivate this PR in the future if you decide to sign the CLA and provide an update to the PR that addresses the PR feedback.  Thanks again for your contribution!


For the startpage create all twistedmatrix.com links as local links

The plan is to host the current https://twisted.org website as the main https://twistedmatrix.com/
https://twisted.org is for now a staging area, but should go into production very soon.
Once in production, the content of this site will be served under the https://twistedmatrix.com/ domain.

While doing this change, many links to https://twistedmatrix.com/trac/wiki will be broken, as we don't have wiki for twisted.org.
But that is ok. We will implement redirection as part of the #11 PR.

While we are on it, the link to reporting a security issue should now be https://github.com/twisted/twisted/security/policy

My initial idea was to make them as local links, but I guess we can make all links direct to the wiki archive.


Update the cluster validation step

On this page the user doesn't have access to validate-cluster.sh .
We should replace it with other commands

/assign danyc97


DB seed error message

Using MySql i got the message below
Creating shop products...
16/50 [========>-------------------]  32%
Illuminate\Database\QueryException
SQLSTATE[22007]: Invalid datetime format: 1292 Incorrect datetime value: '2023-03-26 03:21:04' for column abc_abcb_b10.shop_products.updated_at at row 1 (SQL: insert into shop_products (name, slug, sku, barcode, description, qty, security_stock, featured, is_visible, old_price, price, cost, type, published_at, created_at, updated_at, shop_brand_id) values (Cross-group demand-driven synergy, cross-group-demand-driven-synergy, 53728579,<PHONE_NUMBER>410, Alice desperately: 'he's perfectly idiotic!' And she squeezed herself up and leave the court; but on second thoughts she decided on going into the air off all its feet at the Cat's head with great., 5, 5, 1, 1, 440.86, 339.05, 106, downloadable, 2022-10-05 01:56:12, 2022-10-19 00:59:44, 2023-03-26 03:21:04, 177))

Please have a look at the README.md file. just above "Features to explore" title, there is a warning which is down below.

Note
If you get an "Invalid datetime format (1292)" error, this is probably related to the timezone setting of your database.
Please see https://dba.stackexchange.com/questions/234270/incorrect-datetime-value-mysql


Still requires omp.h when USE_OPENMP=OFF

In file included from /wrkdirs/usr/ports/math/mkl-dnn/work/mkl-dnn-1.1-rc-177-gf32e21b48/src/cpu/jit_uni_batch_normalization.cpp:20:
/wrkdirs/usr/ports/math/mkl-dnn/work/mkl-dnn-1.1-rc-177-gf32e21b48/src/common/dnnl_thread.hpp:42:10: fatal error: 'omp.h' file not found
#include <omp.h>
         ^~~~~~~
1 error generated.

1.1-rc-177-gf32e21b48
FreeBSD 12

Can you please provide full build instructions as per the issue template? There is no USE_OPENMP=OFF build-time option for DNNL. If this is related to ideep, please file the bug with them.

@yurivict,
DNNL requires either OpenMP or TBB runtime and headers at build time. Choice of the runtime is managed with build options. If you are not building DNNL directly please report the issue downstream.


Add ability to trace a check request

Provides a trace output when requested, as well as the schema used
Fixes https://github.com/authzed/spicedb/issues/696

Waiting on changes in API to be merged and pulled into authzed-go

The display logic should get teased apart from the CLI flag logic and moved to into the internal/printers package.

Done


Atari code

Hi, I've spent the past week or so trying to recover the results that you posted previously to one of my questions regarding Montezuma's revenge. It doesn't get anything above 100 rewards even after 10 million steps. With the same hyperparamters you posted. My question is, is it possible to submit your code for Atari as well? Maybe on a different branch?
thank you

Hi @hlsafin, thank you for your post.
At request, we have uploaded the code from our preliminary Atari experiments conducted in June 2023 in a separate branch. I am sorry that since we haven't been working on this project for a while, we haven't had the time to organize and comment on the code in that branch. Still, we believe that with the code from it and the hyperparameters we shared earlier, your agents should be able to obtain non-zero returns in Montezuma's Revenge.
However, there are a few points to note:
Firstly, since we didn't conduct any exhaustive hyperparameter search for Atari games, the hyperparameters we provided above are for reference only and are likely not optimal. For example, we found that setting frame_skip=8 can lead to faster convergence, but skipping too many frames may cause the agent to miss the right timing to pass certain obstacles, and this might be a reason why it is hard to get a return higher than 2500. However, conversely, if too few frames are skipped, more timesteps would be needed to obtain the same rewards, and hyper-parameters such as gamma and gae_lambda would need adjustments accordingly.
Secondly, in the first room of Montezuma's Revenge, the agent may choose to open either the door in the upper left or the upper right after getting the key, and get into different rooms. It the agent chooses to open the right door, it may get 2500 points within a short time. If it chooses to open the left door, it may only get 400 points in the end. As discussed in the RND paper [1] (in the footnote on page 8), the agent's choices are completely random, but once it receives an extrinsic reward from its choice, it is likely to consistently choose the same door in later episodes. Therefore, among all experiments with non-zero returns, some experiments may converge to an episode return of 2500, while other experiments may only converge to 400.
Furthermore, we observed that even when using the provided hyperparameters, DEIR may occasionally fail to get any rewards (with a relatively low probability). This could be related to the advantage normalization method we adopted, which can accelerate the convergence rate by scaling up near-zero advantages, but it may also lead to instability when updating network parameters. If you encounter such issues, we suggest stopping the use of advantage normalization (though you may also need to adjust other hyperparameters accordingly).

[1]  Burda Y, Edwards H, Storkey A, Klimov O. Exploration by random network distillation. In Seventh International Conference on Learning Representations, May 9, 2019.


Fix broken links

I'm not sure how to link the "Learn about our infrastructure text" link that was broken, but guessed https://docs.2i2c.org/en/latest/ - please chime in on that!

this looks great to me, thanks so much @consideRatio :-)


GCC asm updates

This fixes a few things regarding asm, GCC and Eclipse.

Eclipse CDT needs assembly files names with .asm or .S (not lowercase) http://gnuarmeclipse.livius.net/blog/faq/#The_plug-in_seems_to_ignore_assembly_s_files_How_can_I_add_them_to_the_project

RTOS for Cortex-M4 with floating point uses a __FPU_PRESENT macro. Makefiles not using the c preprocessor and this CPU type would fail. Makefiles now use the assembler after the preprocessor

Tested with a CM4 MCU, RTOS, no RTOS on windows with MSYS, GNU MAKE and Ubuntu 14.04. All combinations build successfully and run without modifications.
import os
import sys

if __name__ == '__main__':

    if len(sys.argv) < 2:
        print 'usage: <path> <old ext> <new ext>'
        sys.exit()

    change_count = 0
    for root, dirs, files in os.walk(sys.argv[1]):
        for file in files:
            if file.endswith(sys.argv[2]):
                print file
                (name, ext) = os.path.splitext(file)
                name += sys.argv[3]
                os.rename(os.path.join(root, file), os.path.join(root, name))
                print name
                change_count += 1

    print 'files changed: ', change_count

The change to the gcc arm template must also be applied after merging #1204 for the efm32 targets.

@chrta Thanks , we should do

@sg- lot of refactoring done, nice! I can't locate the issue here but I remember creating an issue for this.


Adding combined cycle power plant (CCGT)

Description of the issue
Currently, we have different types of power plants, but we do not have a combined cycle power plant. Since we have gas power plant, steam, steam turbine and gas turbine already defined, I think adding combined cycle power plant (and therefore also steam power unit) is a nice complement to the existing terms.
Ideas of solution

A steam power unit is a power generating unit that uses steam energy.
A combined cycle power plant (CCGT) is a gas power plant that has gas fired power units and steam power units as parts.

Workflow checklist

[X] I discussed the issue with someone else than me before working on a solution
[X] I already read the latest version of the workflow for this repository
[X] The goal of this ontology is clear to me

I am aware that

[X] every entry in the ontology should have a definition
[X] classes should arise from concepts rather than from words

In my view, your definition proposal excludes single shaft CCGTs. In those, the gas turbine, the heat recovery steam generator, the steam turbine and the generator form one unit.
Maybe, it is helpful, to define the CCGT process first and then the actual units / power plants.

@l-emele what do you mean with define the CCGT process first? For example gas power plant just participates in some energy transformation and has part some power generating unit and no specific process.
I think introducing also heat recovery steam generator is quite easy:

heat recovery steam generator with the parent class  energy converting component:

A heat recovery steam generator is an energy converting component that recovers heat from a hot gas stream and produces steam with a lower temperature.

Then, we can use the heat recovery steam generator with the axiom has part for the definition of CCGT.

I think introducing also heat recovery steam generator is quite easy:
* `heat recovery steam generator` with the parent class  **energy converting component**:

  * ```
    A heat recovery steam generator is an energy converting component that recovers heat from a hot gas stream
    ```

Isn't that a special kind of a heat exchanger? Then it would be better to define: _A heat recovery steam generator is a heat exchanger component that recovers heat from a hot gas stream. _

From todays OEO-dev meeting:

It is currently unclear what exactly is needed. The SEDOS project needs to provide input further input. Especially the terms proposed definitions for combined cycle power plant, heat recovery steam unit and heat recovery steam generator need further discussion as the concepts are not yet clear.
To move forward:

Implement the alternative definition of steam power unit: A steam power unit is a power generating unit that only has a steam turbine as turbine.
Delete the class gas power unit (OEO:00310030) and add gas power unit as alternative term to the existing class gas fired power unit (OEO:00000017).
The issue #1256 will stay open, there we can further discuss the open classes.

State before cleaning up the feature branch resp. latest proposals:

heat recovery steam generator (OEO_00310023): A heat recovery steam generator is a heat exchanger that recovers heat from a hot steam.
combined cycle power plant (OEO_00310029): A combined cycle power plant (CCGT) is a gas power plant that has gas fired power units, steam power units, gas power units and heat recovery steam units as parts.
heat recovering steam unit (OEO_00310031): A heat recovering steam unit is an energy transformation unit that recovers heat from steam.
steam generator: A steam generator is a boiler that converts liquid water into steam.
heat recovery steam generator: A heat recovery steam generator is a steam generator that contains a heat exchanger hat recovers heat from a hot gas stream.

PR #1362 is merged and closed now. This issue stays open as not everything was solved, but I move the milestone.


Incompatible with newest IntelliJ IDEA

After updating IntelliJ IDEA to the newest version I get this error:
Plugin error: Not compatible with the version of your running IDE (IntelliJ IDEA 2022.2.3)

Updated the dependency versions
next published version will be compatible with 2023


fix block.transaction mutation

missed in #874 and shows up when running vyper tests using develop
note: the CI will fail until #878 gets merged

Thanks!


Demos missing on readthedocs

I think some important things for notebook rendering got left out of the migration because the demos aren't on readthedocs at all anymore.
EDIT: @OliviaLynn has reminded me it wasn't forgotten or anything, just postponed until after the migration due to speed of building the notebooks.

I posted about this on slack.The notebook render times out on read the docs.So we will have to come up with some other strategy to auto render the notebooks.-eOn Jun 26, 2023, at 5:57 PM, Alex Malz @.***> wrote:
Assigned #42 to @eacharles.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were assigned.Message ID: @.***>


This feature is great

Please don't remove it! Helps a ton when developing and doing a lot of testing when you're on a tight budget!
Just wanted to let you guys know ;)

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

ID: f07b13b8-6b8b-57f9-7fb3-361329af08be
Version Independent ID: d3c6ae95-654f-be23-5dcd-3c3146d5cf63
Content: Start and Stop an Azure Kubernetes Service (AKS) - Azure Kubernetes Service
Content Source: articles/aks/start-stop-cluster.md
Service: container-service
GitHub Login: @palma21
Microsoft Alias: mlearned

Woops I might have removed references and stuff... but here's the page I was talking about...
https://docs.microsoft.com/en-us/azure/aks/start-stop-cluster

Woops I might have removed references and stuff... but here's the page I was talking about...
https://docs.microsoft.com/en-us/azure/aks/start-stop-cluster

@spacecat Thank you so much for the feedback and great words.
@palma21 FYI This is a great feedback. Kudos!!

@spacecat Thank you so much for the feedback and great words.
@palma21 FYI This is a great feedback. Kudos!!

We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.

We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.

@spacecat thank you for the feedback, it's really appreciated. We love the feature as well and have no intention of removing it :), just continue to improve.
This feature should GA now during this quarter and have a few more capabilities.

@spacecat thank you for the feedback, it's really appreciated. We love the feature as well and have no intention of removing it :), just continue to improve.
This feature should GA now during this quarter and have a few more capabilities.


[BUG] CrudRepository.save(..) failed. Got a 404 NotFound

Describe the bug
After we upgrade azure-spring-data-cosmos from 3.30.0 to 3.33.0, we ran into this error when invoking CrudRepository.save(..) to persist a newly-created entity. See the exception below. So, we had to roll back to 3.30.0, with which the error goes away.
Exception or Stack Trace
com.azure.spring.data.cosmos.exception.CosmosAccessException: Failed to upsert item; nested exception is {"ClassName":"CosmosException","userAgent":"azsdk-java-cosmos/4.42.0 Linux/5.4.0-1103-azure JRE/11.0.18","statusCode":404,"resourceAddress":"https://.documents.azure.com:443/dbs//colls/***","error":"{"code":"NotFound","message":"Message: {\"Errors\":[\"Resource Not Found. Learn more: https:\\/\\/aka.ms\\/cosmosdb-tsg-not-found\"]}\r\nActivityId: 6f226245-298e-4975-afab-e5d3e0383c2c, Request URI: /apps/41f52872-9300-4928-b18e-d15ad2e4d29b/services/10a67a68-87f9-490e-bd73-b6c40fa72956/partitions/dd353fe8-219a-4dfa-8cc0-dc67b3686f55/replicas/132839721753710598s, RequestStats: \r\nRequestStartTime: 2023-04-10T08:08:41.3365508Z, RequestEndTime: 2023-04-10T08:08:41.3365508Z,  Number of regions attempted:1\r\n{\"systemHistory\":[{\"dateUtc\":\"2023-04-10T08:07:26.0049359Z\",\"cpu\":0.788,\"memory\":487745112.000,\"threadInfo\":{\"isThreadStarving\":\"False\",\"threadWaitIntervalInMs\":0.0168,\"availableThreads\":32763,\"minThreads\":52,\"maxThreads\":32767},\"numberOfOpenTcpConnection\":165},{\"dateUtc\":\"2023-04-10T08:07:36.0051993Z\",\"cpu\":0.336,\"memory\":487748444.000,\"threadInfo\":{\"isThreadStarving\":\"False\",\"threadWaitIntervalInMs\":0.0343,\"availableThreads\":32731,\"minThreads\":52,\"maxThreads\":32767},\"numberOfOpenTcpConnection\":165},{\"dateUtc\":\"2023-04-10T08:07:46.0153962Z\",\"cpu\":0.592,\"memory\":487743636.000,\"threadInfo\":{\"isThreadStarving\":\"False\",\"threadWaitIntervalInMs\":0.0115,\"availableThreads\":32764,\"minThreads\":52,\"maxThreads\":32767},\"numberOfOpenTcpConnection\":165},{\"dateUtc\":\"2023-04-10T08:08:06.0258365Z\",\"cpu\":0.640,\"memory\":487464420.000,\"threadInfo\":{\"isThreadStarving\":\"False\",\"threadWaitIntervalInMs\":0.041,\"availableThreads\":32764,\"minThreads\":52,\"maxThreads\":32767},\"numberOfOpenTcpConnection\":165},{\"dateUtc\":\"2023-04-10T08:08:16.0360005Z\",\"cpu\":0.309,\"memory\":487699308.000,\"threadInfo\":{\"isThreadStarving\":\"False\",\"threadWaitIntervalInMs\":0.0253,\"availableThreads\":32691,\"minThreads\":52,\"maxThreads\":32767},\"numberOfOpenTcpConnection\":165},{\"dateUtc\":\"2023-04-10T08:08:36.0464783Z\",\"cpu\":0.715,\"memory\":487746952.000,\"threadInfo\":{\"isThreadStarving\":\"False\",\"threadWaitIntervalInMs\":0.0109,\"availableThreads\":32740,\"minThreads\":52,\"maxThreads\":32767},\"numberOfOpenTcpConnection\":166}]}\r\nRequestStart: 2023-04-10T08:08:41.3365508Z; ResponseTime: 2023-04-10T08:08:41.3365508Z; StoreResult: StorePhysicalAddress: rntbd://<IP_ADDRESS>:11000/apps/41f52872-9300-4928-b18e-d15ad2e4d29b/services/10a67a68-87f9-490e-bd73-b6c40fa72956/partitions/dd353fe8-219a-4dfa-8cc0-dc67b3686f55/replicas/132839721753710598s, LSN: 7628, GlobalCommittedLsn: 7628, PartitionKeyRangeId: , IsValid: True, StatusCode: 404, SubStatusCode: 0, RequestCharge: 1, ItemLSN: -1, SessionToken: -1#7628, UsingLocalLSN: False, TransportException: null, BELatencyMs: 0.265, ActivityId: 6f226245-298e-4975-afab-e5d3e0383c2c, RetryAfterInMs: , TransportRequestTimeline: {\"requestTimeline\":[{\"event\": \"Created\", \"startTimeUtc\": \"2023-04-10T08:08:41.3365508Z\", \"durationInMs\": 0.0088},{\"event\": \"ChannelAcquisitionStarted\", \"startTimeUtc\": \"2023-04-10T08:08:41.3365596Z\", \"durationInMs\": 0.0022},{\"event\": \"Pipelined\", \"startTimeUtc\": \"2023-04-10T08:08:41.3365618Z\", \"durationInMs\": 0.0789},{\"event\": \"Transit Time\", \"startTimeUtc\": \"2023-04-10T08:08:41.3366407Z\", \"durationInMs\": 1.3054},{\"event\": \"Received\", \"startTimeUtc\": \"2023-04-10T08:08:41.3379461Z\", \"durationInMs\": 0.021},{\"event\": \"Completed\", \"startTimeUtc\": \"2023-04-10T08:08:41.3379671Z\", \"durationInMs\": 0}],\"serviceEndpointStats\":{\"inflightRequests\":1,\"openConnections\":1},\"connectionStats\":{\"waitforConnectionInit\":\"False\",\"callsPendingReceive\":0,\"lastSendAttempt\":\"2023-04-10T08:08:41.3365508Z\",\"lastSend\":\"2023-04-10T08:08:41.3365508Z\",\"lastReceive\":\"2023-04-10T08:08:41.3365508Z\"},\"requestSizeInBytes\":492,\"responseMetadataSizeInBytes\":137,\"responseBodySizeInBytes\":87};\r\n ResourceType: Collection, OperationType: Read\r\nRequestStart: 2023-04-10T08:08:41.3365508Z; ResponseTime: 2023-04-10T08:08:41.3365508Z; StoreResult: StorePhysicalAddress: rntbd://<IP_ADDRESS>:11300/apps/41f52872-9300-4928-b18e-d15ad2e4d29b/services/10a67a68-87f9-490e-bd73-b6c40fa72956/partitions/dd353fe8-219a-4dfa-8cc0-dc67b3686f55/replicas/132772599043365230s, LSN: 7628, GlobalCommittedLsn: 7628, PartitionKeyRangeId: , IsValid: True, StatusCode: 404, SubStatusCode: 0, RequestCharge: 1, ItemLSN: -1, SessionToken: -1#7628, UsingLocalLSN: False, TransportException: null, BELatencyMs: 0.242, ActivityId: 6f226245-298e-4975-afab-e5d3e0383c2c, RetryAfterInMs: , TransportRequestTimeline: {\"requestTimeline\":[{\"event\": \"Created\", \"startTimeUtc\": \"2023-04-10T08:08:41.3365508Z\", \"durationInMs\": 0.0047},{\"event\": \"ChannelAcquisitionStarted\", \"startTimeUtc\": \"2023-04-10T08:08:41.3365555Z\", \"durationInMs\": 0.0064},{\"event\": \"Pipelined\", \"startTimeUtc\": \"2023-04-10T08:08:41.3365619Z\", \"durationInMs\": 0.0689},{\"event\": \"Transit Time\", \"startTimeUtc\": \"2023-04-10T08:08:41.3366308Z\", \"durationInMs\": 0.6315},{\"event\": \"Received\", \"startTimeUtc\": \"2023-04-10T08:08:41.3372623Z\", \"durationInMs\": 0.031},{\"event\": \"Completed\", \"startTimeUtc\": \"2023-04-10T08:08:41.3372933Z\", \"durationInMs\": 0}],\"serviceEndpointStats\":{\"inflightRequests\":1,\"openConnections\":1},\"connectionStats\":{\"waitforConnectionInit\":\"False\",\"callsPendingReceive\":0,\"lastSendAttempt\":\"2023-04-10T08:08:38.7865599Z\",\"lastSend\":\"2023-04-10T08:08:38.7865599Z\",\"lastReceive\":\"2023-04-10T08:08:38.7865599Z\"},\"requestSizeInBytes\":492,\"responseMetadataSizeInBytes\":137,\"responseBodySizeInBytes\":87};\r\n ResourceType: Collection, OperationType: Read\r\n, SDK: Microsoft.Azure.Documents.Common/2.14.0, StatusCode: NotFound","additionalErrorInfo":null}","innerErrorMessage":"Message: {"Errors":["Resource Not Found. Learn more: https:\/\/aka.ms\/cosmosdb-tsg-not-found"]}\r\nActivityId: 6f226245-298e-4975-afab-e5d3e0383c2c, Request URI: /apps/41f52872-9300-4928-b18e-d15ad2e4d29b/services/10a67a68-87f9-490e-bd73-b6c40fa72956/partitions/dd353fe8-219a-4dfa-8cc0-dc67b3686f55/replicas/132839721753710598s, RequestStats: \r\nRequestStartTime: 2023-04-10T08:08:41.3365508Z, RequestEndTime: 2023-04-10T08:08:41.3365508Z,  Number of regions attempted:1\r\n{"systemHistory":[{"dateUtc":"2023-04-10T08:07:26.0049359Z","cpu":0.788,"memory":487745112.000,"threadInfo":{"isThreadStarving":"False","threadWaitIntervalInMs":0.0168,"availableThreads":32763,"minThreads":52,"maxThreads":32767},"numberOfOpenTcpConnection":165},{"dateUtc":"2023-04-10T08:07:36.0051993Z","cpu":0.336,"memory":487748444.000,"threadInfo":{"isThreadStarving":"False","threadWaitIntervalInMs":0.0343,"availableThreads":32731,"minThreads":52,"maxThreads":32767},"numberOfOpenTcpConnection":165},{"dateUtc":"2023-04-10T08:07:46.0153962Z","cpu":0.592,"memory":487743636.000,"threadInfo":{"isThreadStarving":"False","threadWaitIntervalInMs":0.0115,"availableThreads":32764,"minThreads":52,"maxThreads":32767},"numberOfOpenTcpConnection":165},{"dateUtc":"2023-04-10T08:08:06.0258365Z","cpu":0.640,"memory":487464420.000,"threadInfo":{"isThreadStarving":"False","threadWaitIntervalInMs":0.041,"availableThreads":32764,"minThreads":52,"maxThreads":32767},"numberOfOpenTcpConnection":165},{"dateUtc":"2023-04-10T08:08:16.0360005Z","cpu":0.309,"memory":487699308.000,"threadInfo":{"isThreadStarving":"False","threadWaitIntervalInMs":0.0253,"availableThreads":32691,"minThreads":52,"maxThreads":32767},"numberOfOpenTcpConnection":165},{"dateUtc":"2023-04-10T08:08:36.0464783Z","cpu":0.715,"memory":487746952.000,"threadInfo":{"isThreadStarving":"False","threadWaitIntervalInMs":0.0109,"availableThreads":32740,"minThreads":52,"maxThreads":32767},"numberOfOpenTcpConnection":166}]}\r\nRequestStart: 2023-04-10T08:08:41.3365508Z; ResponseTime: 2023-04-10T08:08:41.3365508Z; StoreResult: StorePhysicalAddress: rntbd://<IP_ADDRESS>:11000/apps/41f52872-9300-4928-b18e-d15ad2e4d29b/services/10a67a68-87f9-490e-bd73-b6c40fa72956/partitions/dd353fe8-219a-4dfa-8cc0-dc67b3686f55/replicas/132839721753710598s, LSN: 7628, GlobalCommittedLsn: 7628, PartitionKeyRangeId: , IsValid: True, StatusCode: 404, SubStatusCode: 0, RequestCharge: 1, ItemLSN: -1, SessionToken: -1#7628, UsingLocalLSN: False, TransportException: null, BELatencyMs: 0.265, ActivityId: 6f226245-298e-4975-afab-e5d3e0383c2c, RetryAfterInMs: , TransportRequestTimeline: {"requestTimeline":[{"event": "Created", "startTimeUtc": "2023-04-10T08:08:41.3365508Z", "durationInMs": 0.0088},{"event": "ChannelAcquisitionStarted", "startTimeUtc": "2023-04-10T08:08:41.3365596Z", "durationInMs": 0.0022},{"event": "Pipelined", "startTimeUtc": "2023-04-10T08:08:41.3365618Z", "durationInMs": 0.0789},{"event": "Transit Time", "startTimeUtc": "2023-04-10T08:08:41.3366407Z", "durationInMs": 1.3054},{"event": "Received", "startTimeUtc": "2023-04-10T08:08:41.3379461Z", "durationInMs": 0.021},{"event": "Completed", "startTimeUtc": "2023-04-10T08:08:41.3379671Z", "dura...
To Reproduce
Steps to reproduce the behavior:
Code Snippet
ourRepository.save(entity);

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Setup (please complete the following information):

OS: Windows
IDE: IntelliJ
Library/Libraries: com.azure:azure-spring-data-cosmos:3.33.0
Java version: 11
App Server/Environment: Tomcat
Frameworks: Spring Boot

Additional context
N/A
Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

[ ] Bug Description Added
[ ] Repro Steps Added
[ ] Setup information Added

@kushagraThapar Let's talk offline.

@trande4884   can you please take a look at this, looks like something changed between 3.30.0 and 3.33.0. @domainname can you please reach out to Trevor for this, thanks!

@trande4884  - FYI, actually this might be related to multi-tenancy support via CosmosFactory. Worth looking into that as well, thanks!

@domainname can you provide the config you are using to build the cosmos client?

So you have a parent class 'Certificate' with two child classes 'KeyVaultCertificate' and 'ContentCertificate'. When you were calling save with a KeyVaultCertificate in the past it was saving simply to the 'Certificate' container. With the new release that includes enhancements to CosmosTemplate to support multi-tenancy the database name is pulled on the fly which is KeyVaultCertificate, which is actually the correct thing for the code to do. Your worked around to this of defining @Container(containerName = "Certificate") on the parent class Certificate is going to be the new way of achieving your end goal. There was actually a bug in CosmosTemplate in the past with the way the database name was set once at the beginning instead of being found on the fly as we do now.
Let me know if you have any questions/issues with this.


Reform fragment shader coordinate systems

We should have as few coordinate systems in the fragment shader as possible. Currently we have an extra one from swapping  the y axis in mod. We should get rid of that one if possible. We should also consider getting rid of pixel coordinates entirely, and basing everything off of [-1,1] coordinates. (Or at least basing everything that we expose to the user on [-1,1] coordinates.)

We could also consider making everything [0,1] coordinates, since pixel colors are between 0 and 1, and texture coordinates are between 0 and 1.

I think things are pretty good as is. We got rid of the y swapping.


Partial solution to "sails.getBaseUrl()" deprecation warning

Partial solution to #140.
I'm not smart enough to figure out an elegant solution to "guessing" a pre-defined baseUrl key, but that would improve this somewhat.

Well I done goofed...

Too used to using standard.js :laughing: (poor excuse)

I'm not smart enough to figure out an elegant solution to "guessing" a pre-defined baseUrl key

Me either, so thanks for trying :)


Small boring js fixes

Before merging this, have a look at my branch at the current state.
I added backbone.js which allows to do some sort of mvc in js.
This is some heavy changes and maybe not the direction you want collective.dynatree go to. In this case, merge this request, since that does not add any of these.

whats the state on this? long time open...

The question above was about a future merge, I think this can be merged safely.
The only complaint was the indentation, and the code is properly indented, the diff is displaying it wrong.


Add bfp8 with LoFi for matmul

Needed for SD, have bfp8 math but it’s in HIFI4 for which there’s no reason

@TT-BrianLiu , do we already have support for this?

Yes, if you use primary matmuls directly.

Is this still an issue?

Sounds like it's supported, closing.  We can re-open if necessary.


Website broken for output of .dimensions()

Odd. I assume this is to do with notebook building as I don't see this issue running in the live notebook.
We could manually edit the HTML to fix it for the release version of the website but that isn't a suitable long term solution.

Isn't there a script to patch notebook links?  Seems like this fix could go in there; it's unrelated but could use the same mechanism.

Ah, ' which is for an apostrophe - pretty obvious now I look at it.
Could be a search and replace in the link processing script unless we actually need ' in our HTML code somewhere?

Turns out ' isn't valid HTML, it's an XML character. For now I've added a one line JS fix to replace them. Closing.


Viewer doesn't deal well with binary files

Load the sample SARIF file EmbbeddedBinaryContent.sarif.

Double-click on its single result.

Expected: Well, it's not clear what to expect here, because I don't know VS Code's facilities for displaying binary files.
Actual: It loads the 5-byte contents into a text editor window and displays squares for the bytes -- which I can't blame it for -- but it doesn't highlight anything, even though the result sepcifies a region with byteOffset of 2 and byteLength of 2.

@lgolding - We have addressed this in the current Insiders version as well as the new UI @jeffersonking is working on.


Add minicrawler

Adding minicrawler (testomatobot) to the patterns.
Testomato is website monitoring service using https://github.com/testomato/minicrawler for crawling websites and uptime monitoring.

Thanks @OzzyCzech


Consume Jersey and all dependencies using Maven repositories

Now that Eclipse target definitions can contain Maven artifacts, let's try to switch over from Orbit and other sources to directly get Jersey and all dependencies (Jackson, etc) directly from Maven repositories.
I'm guessing the best way to do this would be in isolation from the Jersey 3 upgrade, though we could do them both at the same time. In the Eclipse IDE, this requires m2e PDE 1.17.0 and Tycho requires 2.1.
The easiest way to add these artifacts is to modify the target definition source directly. Here's an example for Mockito:
	<location missingManifest="generate" type="Maven">
		<groupId>org.mockito</groupId>
		<artifactId>mockito-core</artifactId>
		<version>3.7.0</version>
		<type>jar</type>
	</location>

Hi Patrick.
I've added a target file that I've constructed with the Maven artifacts support.   It's currently on branch:  mvn_artifacts_in_target and the file is:  org.eclipse.ecf.jaxrs.releng.target/ecf-jaxrs-2019-12_mvn.target
With this target set, I'm able to build JaxRSProviders projects in PDE.   It does so with using p2 repos in the target for ECF and Eclipse, and maven central for all the Jersey, CXF, and their dependencies.
I have not yet tried to build with Tycho and this target platform...I'll probably try this weekend.
If this all works, I'll probably do a new release of the JaxRSProviders, and then begin looking into contributing the JaxRSProviders projects to the ECF Eclipse Foundation project.   One thing I need to look into a little:  What the EF rules are wrt redistributing (i.e. in p2 repo) artifacts from maven repos.

Hi Patrick.
I've added a target file that I've constructed with the Maven artifacts support.   It's currently on branch:  mvn_artifacts_in_target and the file is:  org.eclipse.ecf.jaxrs.releng.target/ecf-jaxrs-2019-12_mvn.target
With this target set, I'm able to build JaxRSProviders projects in PDE.   It does so with using p2 repos in the target for ECF and Eclipse, and maven central for all the Jersey, CXF, and their dependencies.
I have not yet tried to build with Tycho and this target platform...I'll probably try this weekend.
If this all works, I'll probably do a new release of the JaxRSProviders, and then begin looking into contributing the JaxRSProviders projects to the ECF Eclipse Foundation project.   One thing I need to look into a little:  What the EF rules are wrt redistributing (i.e. in p2 repo) artifacts from maven repos.

That's great! Let me know what you find out distributing Maven artifacts. I suppose this new target location type might open up a set of new issues around that. Was Orbit a way to "vet" third party libraries and make them acceptable for distribution?

That's great! Let me know what you find out distributing Maven artifacts. I suppose this new target location type might open up a set of new issues around that. Was Orbit a way to "vet" third party libraries and make them acceptable for distribution?

Hi Pat,

That's great! Let me know what you find out distributing Maven artifacts. I suppose this new target location type might open >up a set of new issues around that. Was Orbit a way to "vet" third party libraries and make them acceptable for distribution?

Yes, it played that role wrt 'vetting' source code (i.e. provenance, license compatibility, copyright mgmt, etc).   The good thing is that Jersey is already an EF member, so it should be complying already with all the EF licensing/copyright/provenance stuff...and for it's dependencies (e.g. Jackson).   I'm hopeful I will be able to just point to Jersey and say this code is dependent upon Jersey, and Jersey is an EF project so...but I'll have to figure that all out.
I've run into a bit of a snag wrt Tycho wrt the maven build support, however.  It seems that Tycho 2.2 is not yet available on Maven Central (although it was recently released on Tycho site)...and afaict 2.2 is the one that has the maven artifact in target support.   So for the moment I can build p2 repo with Eclipse + m2e PDE on the new branch, but I can't build it via maven/tycho (this is all with 2.30.1 of Jersey...not yet with 3.x of Jersey).
So while waiting for Tycho 2.2 being deployed to maven and looking into the EF licensing/deployment implications of using the maven artifacts in target, would you rather that I release a new version of JaxRSProviders (1.14.2)...with a few small metadata changes to support dependencies diffs...or wait until Tycho 2.2 is available?

Hi Pat,

That's great! Let me know what you find out distributing Maven artifacts. I suppose this new target location type might open >up a set of new issues around that. Was Orbit a way to "vet" third party libraries and make them acceptable for distribution?

Yes, it played that role wrt 'vetting' source code (i.e. provenance, license compatibility, copyright mgmt, etc).   The good thing is that Jersey is already an EF member, so it should be complying already with all the EF licensing/copyright/provenance stuff...and for it's dependencies (e.g. Jackson).   I'm hopeful I will be able to just point to Jersey and say this code is dependent upon Jersey, and Jersey is an EF project so...but I'll have to figure that all out.
I've run into a bit of a snag wrt Tycho wrt the maven build support, however.  It seems that Tycho 2.2 is not yet available on Maven Central (although it was recently released on Tycho site)...and afaict 2.2 is the one that has the maven artifact in target support.   So for the moment I can build p2 repo with Eclipse + m2e PDE on the new branch, but I can't build it via maven/tycho (this is all with 2.30.1 of Jersey...not yet with 3.x of Jersey).
So while waiting for Tycho 2.2 being deployed to maven and looking into the EF licensing/deployment implications of using the maven artifacts in target, would you rather that I release a new version of JaxRSProviders (1.14.2)...with a few small metadata changes to support dependencies diffs...or wait until Tycho 2.2 is available?

I'm fine waiting until Tycho 2.2 is available and we've clarified the licensing issues. The functionality is where I need it to be right now.

I'm fine waiting until Tycho 2.2 is available and we've clarified the licensing issues. The functionality is where I need it to be right now.

Hi Patrick.  FYI...the policy discussion around use of maven artifacts in Tycho/PDE builds (to produce maven repos) has begun here:
https://www.eclipse.org/lists/p2-dev/msg05910.html
FYI:  I anticipate that this is going to be a while.  The reason is that currently the EF has stronger signing requirements for Eclipse Foundation projects than Maven does for Maven Central.   What that implies is that projects like ECF...that want to consume Jersey Maven artifacts won't necessarily be able to package and redistribute those artifacts as p2 repo as we must at ECF EF even if we can get them from maven via the new maven artifacts support in PDE and soon Tycho.
In the mean time, another possibility is that I build the JaxRSProvider and put the org.eclipse.ecf bundles on Maven Central...for your and others consumption via Maven Central (rather than as p2 repo as you have been doing).   Even with the maven artifacts support (which is not fully there yet) this might not be ideal as there are some issues to work out with maven artifacts which will make them harder to use (e.g. not full support for deps, no notion of features/groups at this point).
Wanted to keep you updated.  Things are moving toward full policy and technical support for maven artifacts in RCP libs and apps, but at EF the policy stuff might lag behind as there are a lot of stakeholders there.

Hi Patrick.  FYI...the policy discussion around use of maven artifacts in Tycho/PDE builds (to produce maven repos) has begun here:
https://www.eclipse.org/lists/p2-dev/msg05910.html
FYI:  I anticipate that this is going to be a while.  The reason is that currently the EF has stronger signing requirements for Eclipse Foundation projects than Maven does for Maven Central.   What that implies is that projects like ECF...that want to consume Jersey Maven artifacts won't necessarily be able to package and redistribute those artifacts as p2 repo as we must at ECF EF even if we can get them from maven via the new maven artifacts support in PDE and soon Tycho.
In the mean time, another possibility is that I build the JaxRSProvider and put the org.eclipse.ecf bundles on Maven Central...for your and others consumption via Maven Central (rather than as p2 repo as you have been doing).   Even with the maven artifacts support (which is not fully there yet) this might not be ideal as there are some issues to work out with maven artifacts which will make them harder to use (e.g. not full support for deps, no notion of features/groups at this point).
Wanted to keep you updated.  Things are moving toward full policy and technical support for maven artifacts in RCP libs and apps, but at EF the policy stuff might lag behind as there are a lot of stakeholders there.


ZFS support (ideally Canonical's pre-built ZFS-on-Linux modules)

First off, let me acknowledge that this feature request "should" go to UserVoice. The problem being, UserVoice seems to be broken; searches don't finish, can't add new requests, etc. Furthermore, Git is a far more user-friendly platform and appears to be more active. (Though hard to be sure.)
That said, I was surprised to find that this request hasn't already been made here.
Quick checklist of top ZFS benefits

Metadata-based integrity verification
Copy-on-write
Snapshots for free
Clones for free
Send and receive snapshots
On-the-fly compression
Sophisticated redundancy options, etc.
Containers work best on ZFS

Even Btrfs has been unable to reliably crack this nut after years of development. Microsoft has been waffling on ReFS (e.g. pulled from 10 Pro) - and like Btrfs, has it's share of problems and even more compromises.
Problems and challenges with supporting ZFS on WSL, that I'm currently aware of

ZFS is a kernel module, which currently is not supported in WSL, may never be, and isn't currently the intended goal of WSL (whic is currently to provide user-space linux dev tooling).
ZFS requires direct block device access, which similarly isn't currently supported in WSL, and /dev/disk doesn't exist.
ZFS is released under CDDL, which is incompatible with GPL v3 (and lxss isn't even open source).
ZFS on Linux is itself a hybrid port/re-implementation of Solaris ZFS, and already has a number of kludgey workarounds and shims (such as the SPL translation layer).
ZFS on Linux uses memory and disk caching in a poorly integrated way, due to the fundamental architectural differences between Linux, and ZFS's original target OS.
There are already open-source efforts to bring ZFS to Windows natively. (E.g. ZFSin.) While this may solve a much-desired wish for many: ZFS self-contained on Windows - without having to run a VM and jump through hoops with vmdk passthrough and loopback samba sharing - it still comes with these drawbacks:

It's not currently stable.
It doesn't have the backing and engineering resources of the host OS's owning company behind it, or large teams like ZFS on Linux. (Yet, at least.)
Other attempts to bring Linux filesystems to Windows have been fraught with stability and/or reliability issues for long-term, high-volume applications (e.g. FUSE modules on Dokan).

There would be many open questions - such as

How would ZFS volumes be accessed?

Only via WSL? (Very limited - only access via local terminal, remote SSH, or remote SSHFS.)
Samba? This might be a great cross-platform option, but Samba does not appear to work on WSL currently. Also, there would be port conflicts with native CIFS to work out.
NFS? Not an ideal cross-platform solution, and being a kernel module, not currently supported by WSL. (Third-party user-space nfs-ganesha apparently might work though.)
A Windows CIFS pass-through feature? This could be ideal, could leverage performance improvements of Windows CIFS (such as direct memory mapping), and would solve other problems as well (e.g. accessing WSL filesystem from Windows since accessing the lxss folder directly is a no-no). Granted, it seems like it might be a significant technical hurdle.

Some solution ideas to problems listed above

No support for kernel modules in WSL: Lxss is itself a shim/translation layer that fakes a linux kernel to user space, so it should be possible to also fake a kernel module interface.

This could even be extended to allow building against the kernel ala DKMS (which Ubuntu's ZFS no longer needs to do), which could further WSL's place as a useful dev tool.
Would solve countless other kernel module -related requests, such as support for FUSE, NFS, eCryptFS, etc.
The fact that WSL already works so well on Windows, has led to an explosion of end-user interest. For example, it is already trivially easy to get an Ubuntu desktop running on WSL (e.g. via VcXsrv). While that's not officially "supported" or even recommended, and things can get wonky, it's still cool - and (arguably) more promising than Wine on Linux which is (arguably) more wonky still, even after decades of development (given how closed, complicated, and rapidly moving Windows is). Allowing kernel module support would significantly expand the options and capabilities of running a Linux GUI on Windows. (And of course expand the number of potential problems.)

No block device access, no /dev/disk: This could also be supported, in theory - or at least Cygwin does (granted Cygwin is a very different thing and with different goals). Obviously some precautions would be needed, such as restricting access to devices already mounted by Windows, to read-write mode (if at all). Adding this level of support would again expand the horizons and capabilities of WSL. There would also be challenges in virtualizing and/or passing-through access to hardware registers, so that unmodified linux drivers could access them as they expect to - probably no small feat.
ZFS's CDDL license: The Linux world solves this by not including it in a distribution, but making it easily available. (Ubuntu even precompiles it and makes available through standard repositories.) Then it is a user choice and - arguably - nice and legal.
ZFS on Linux being a hybrid port/re-implementation of Solaris ZFS: As long as it works on Linux, and the above points are addressed, it should work. And again, the ZOL project is working on making ZFS on Linux more Linux native.
Memory and disk caching is poorly integrated into Linux model: The ZOL project is working on this.

Again, these are not modest challenges and the solutions wouldn't be cheap or easy. There may never be enough justification for Microsoft to throw engineers and money at such a challenge. It could remain a pipe dream forever. (Or until Microsoft abandons WSL, whichever happens first.) But you have to admit - that Microsoft is the one developing WSL in the first place, and that it is pretty robust so far- is pretty amazing! Just imagine how much more amazing it can or could get.

Windows has iscsi initiators, use those to talk to a storage appliance that supports ZFS. Export a zvol to windows, it can format as NTFS and manage the filesytem for WSL to use.
you can run the NAS as a VM and provide it a disk drive from the host. Perf would likely be lousy, but you get all the COW features that might acccelarate your workflow in spite of that - branching & snapshots are wonderful for build bots.
Not sure why you’d think that Windows supporting binary Linux kernel modules is even remotely possible — Linux doesn’t guarantee a stable ABI from version to version. Rebuilding external mods from source against some mythical compatibility layer is likely not possible either,  native Linux distributions rely on DKMS for this and that can easily be stymied.

@kfix thanks for the comment, but it was helpful, didn't add new information in context, was (probably unintentionally) misleading, and unnecessarily derisive.
That Linux doesn't guarantee kernel ABI stability is irrelevant, in context. The fundamental point of WSL itself is to provide a substantial portion of a distro-specific kernel ABI, upon which corresponding native Linux userland dev tooling runs. (Then thunk those syscalls to Windows.)
It is in fact "remotely possible" to expand that thunking layer arbitrarily, including support for kernel modules, which are consumers of the kernel interface. (Whether easy and/or worth it to Microsoft, is debatable at best or doubtful at worst. But certainly not impossible.) If you still disagree, that's fine - but you should probably do the Wine project a favor, and inform them stat that they can't thunking low-level APIs is not remotely possible. And also Microsoft, so that they can stop wasting time on their x86:x86_64 WOW translation layer - which is also an ever-moving target. And MAME. And all the other native game console translators that not only target unstable ABIs, but undocumented ABIs. You may rightly argue that WSL, Wine, and MAME are different projects with different goals and legal justifications - which is true and great. But would miss the point about what is "remotely possible" with low-level ABI tunking against an impermanent and even undocumented interface. Countless examples of "likely not possible mythical compatibility layers", if you will.
As for iSCSI SAN, that is beyond the intended scope of this post. I tried to be clear that this was for single-host "enthusiast" use, not for enterprises, or for physical multi-host configurations. (And for the same price, a straightforward native ZFS NAS over CIFS would perform better than NTFS on ZFS over iSCSI SAN, be less brittle, and make more sense for typical home users.)
As for your "NAS in a VM" idea: 1) I already mentioned that as a viable alternative, and 2) given modern-enough consumer-grade hardware and virtio - and all else being equal including storage controllers and media - performs significantly better than gigabit NAS or SAN. (I'm using this setup as we speak. The only real challenges to the configuration is remapping the physical devices to raw VMDK attachments every time the VM starts, which can be [and is] scripted; and setting up a second virtual host-only adapter for sharing to host, for optimal performance. As an alternative to raw VMDK mapping, one could - and many do - configure virtualization I/O pass-through to one or more dedicated adapters, also all on the same host.)
So again, the point of this thread is to get the idea of (single-host) ZFS in WSL in writing, point out why and to whom it might be useful (not necessarily the current WSL target of developers), acknowledge the challenges so that it hopefully doesn't devolve into pedantry, solicit informed and technically accurate discussion/agreement/disagreement, and to do so on a user-friendly forum that Microsoft is hopefully reading but isn't their problematic UserVoice site.
(And so far, it appears there's either not much interest, it's not reaching enough eyes, and/or the idea wasn't presented concisely/well enough. That's a risk I knew I was taking.)

@kfix thanks for the comment, but it didn't add new information in context, was (probably unintentionally) misleading, and came off as unnecessarily derisive.
That Linux doesn't guarantee kernel ABI stability is irrelevant, in context. The fundamental point of WSL itself is to provide a substantial portion of a distro-specific kernel ABI, upon which corresponding native Linux userland dev tooling runs. (Then thunk those syscalls to Windows.)
It is in fact "remotely possible" to expand that thunking layer arbitrarily, including support for kernel modules, which are consumers of the kernel interface. (Whether easy and/or worth it to Microsoft, is debatable at best or doubtful at worst. But certainly not impossible.) If you still disagree, that's fine - but you should probably do the Wine project a favor, and inform them stat that thunking low-level ABIs is not remotely possible. And also Microsoft, so that they can stop wasting time on their x86:x86_64 WOW thunking layer - which is also an ever-moving (and even often undocumented) target. And MAME. And all the other native game console translators that thunk the entire stack. You may rightly argue that WSL, Wine, and MAME are different projects with different goals and legal justifications - which is true and great. But would miss the point about what is "remotely possible" with low-level tunking against impermanent and even undocumented interfaces. All examples of "likely not possible mythical compatibility layers".
As for iSCSI SAN, that is beyond the intended scope of this post. I tried to be clear that this was for single-host "enthusiast" use, not for enterprises, or for physical multi-host configurations. (And either way, for the same price, a straightforward native ZFS NAS over CIFS would perform better than NTFS on ZFS over iSCSI SAN, be less brittle, and make more sense for typical home users.)
As for your "NAS in a VM" idea: 1) I already mentioned that as a viable alternative, and 2) given modern-enough consumer-grade hardware and virtio - and all else being equal including storage controllers and media - performs significantly better than gigabit NAS or SAN. (I'm using this setup as we speak. The only real challenges to the configuration is remapping the physical devices to raw VMDK attachments every time the VM starts, which can be [and is] scripted; and setting up a second virtual host-only adapter for sharing to host, for optimal performance. As an alternative to raw VMDK mapping, one could - and many do - configure virtualization I/O pass-through to one or more dedicated adapters, also all on the same host.)
So again, the point of this thread is to get the idea of (single-host) ZFS in WSL in writing, point out why and to whom it might be useful (not necessarily the current WSL target of developers), acknowledge the challenges so that it hopefully doesn't devolve into pedantry, solicit informed and technically accurate discussion/agreement/disagreement, and to do so on a user-friendly forum that Microsoft is hopefully reading but isn't their problematic UserVoice site.
(And so far, it appears there's either not much interest, it's not reaching enough eyes, and/or the idea wasn't presented concisely/well enough. That's a risk I knew I was taking.)

Discussion appears to have run it's course. Fundamentally dupe #1893, which actually has zfs as the use case cited. If or when openzfsonwindows goes stable release, mount -t drvfs might be a well formed ask, much like #579.

If or when openzfsonwindows goes stable release

@therealkenc what is the most appropriate public place where Microsoft could discuss zfs on Windows? For example could they assign some people on the mentioned ZoW github project?
I mean I know it's a competitor to it's own proprietary ReFS, but still would be very interested to know their opinion (not just technical but legal also)!
So far everyone seems to fear Oracle except Canonical, and Canonical appear to be in warm relations with Microsoft...

I've been building my own wsl kernel with zfs support for the last 6 months or so and it works well enough, but I'm a bit uneasy about keeping my own kernel up to date. I would much prefer to be on the microsoft native kernel, but without zfs support this is a no go for me. Please reconsider supporting zfs natively. Seeing as how canonical has found a way to do it without legal issues, I've got to imagine that it should be possible here too.

@mailinglists35 Microsoft's stance has greatly evolved with time (for the better!), perhaps partly because:
https://www.zdnet.com/article/microsoft-developer-reveals-linux-is-now-more-used-on-azure-than-windows-server/
For a history you can read links from this search result:
https://www.google.com/search?q=microsoft+holds+patents+against+linux+get+royalties
So, the about-face Microsoft did is great news for Linux and for ZFS as well. In fact, Microsoft is in much better position to use ZFS on Windows, even distributing binaries without any issue. Because as far as I know there is "zero" license issue with "distributing" ZFSonWindows "binaries", compared to the 'license technicality' that causes a gray area if "distributing" ZFS binaries within Linux. Therefore, Microsoft could literally make ZFS as an officially supported filesystem if it wanted to.
@jim-collier @kfix I do not think that the ZFSonWindows project tries to load Linux kernel modules and zfs modules meant for Linux kernel. I have not looked at any of the code, but it seems to be that it is a real "port" of zfs code to the Windows platform.
@xrishox Have you used the latest from https://github.com/openzfsonwindows/ZFSin and if so can report on stability etc?

This is fantastic to hear. I started watching releases on https://github.com/openzfsonwindows/openzfs.
Interestingly, with WSL2 it is also now actually possible to run the linux "version" of ZFS within WSL2 (at least the linux ZFS code compiled under WSL2). People have gotten it to work, apparently without too many kludges. I'm not saying I would personally trust important data with this approach (I still use the linux VM and disk passthrough with samba sharing approach to "use" ZFS on Windows). But it's still pretty fascinating:
https://wsl.dev/wsl2-kernel-zfs/

@jim-collier I'm not an expert on WSL2 but it seems its basically a lightweight "Virtual Machine" running on their "Hyper-V". In that sense, if zfsonlinux native is more stable than openzfsonwindows then I'd think ZFS via "WSL2" may be more stable as well.
I would be very curious of a "performance" test between openzfsonwindows versus ZFS via WSL2 versus ZFS inside a full VM like in Virtualbox/VMware or even full Hyper-V instance not wsl2.


[fix] Add serializer to InstitutionAuth to fix API Docs [OSF-5957]

https://openscience.atlassian.net/browse/OSF-5957
Purpose
API Swagger docs were throwing a server error:
AssertionError: 'InstitutionAuth' should either include a `serializer_class` attribute, or override the `get_serializer_class()` method.

Changes
Add a serializer (the most basic one I could think of, the JSONAPISerializer)
Side Effects

None anticipated, unless the way that view was intended to be serialized is dramatically different

Looks good. Simple. Works. Doesn't break tests. Shouldn't break anything. My only question for @icereval is whether institutional endpoints should also be dev only at this point. That can be a separate issue though.

@brianjgeiger, devmode should be use very sparingly as we discussed, originally it was only intended for the api's very first release to limit its scope a bit, but its certainly usable in special case by case scenarios going forward :-)


Clarify docs of Navigator.onPopPage

Navigator.onPopPage docs state:

Called when pop is invoked but the current Route corresponds to a Page found in the pages list.

This is incorrect.  Navigator calls onPopPage if the Route corresponds to a Page.  It doesn't check that the page is in the pages list.  See navigator.dart:5073.
Fixes #81610.
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[ ] I read the Tree Hygiene wiki page, which explains my responsibilities.
[ ] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[ ] I added new tests to check the change I am making or feature I am adding, or Hixie said the PR is test-exempt.
[ ] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

test-exempt: documentation

Hi @chunhtai, Would you like to review this tiny PR?

Closing this since we believe it's not the right fix and the discussion about the right fix is at https://github.com/flutter/flutter/issues/81610#issuecomment-838698924.


edit story form first draft

will obviously need some changes to make it actually do anything

just realized I need to make a few changes to this based on the project requirements doc

FYI, I force pushed to overwrite history and tags because we needed to purge sensitive data from another branch. I don't think it should affect this branch or PR.


test: Set-up integration test [PAGOPA-786]

List of Changes

GitHub Actions pipelines added
.identity added
docker HOST_PORT updated
check health logic in run_docker.sh changed

Motivation and Context

How Has This Been Tested?

It has been tested via smoke test and integration test pipelines interacting with resources in dev environment
Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[ ] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.

update_code

update_code

update_code


Node Graph Crashing when non-ROS2 DDS Traffic is on the network

With latest ROS2 eloquent packages on Ubuntu 18.04
sudo apt-get update && sudo apt-get install --upgrade-only ros-eloquent-\*

The rqt node graph crashes when unrelated DDS traffic is running on the same domain.
How to reproduce:
# Shell 1
$ . /opt/ros/eloquent/setup.bash
$ ros2 run demo_nodes_cpp talker

# Shell 2
$ . /opt/ros/eloquent/setup.bash
$ ros2 run demo_nodes_cpp listener  # Shows the messages from talker

# Shell 3
$ rtiddsping  # from RTI Connext Evaluation package, version 6.0.0

# Shell 4
$ . /opt/ros/eloquent/setup.bash
$ rqt
# Within rqt, select "Plugins->Introspection->Node Graph".
# Then, this occurs in the console:
PluginManager._load_plugin() could not load plugin "rqt_graph/RosGraph":
Traceback (most recent call last):
  File "/opt/ros/eloquent/lib/python3.6/site-packages/qt_gui/plugin_handler.py", line 102, in load
    self._load()
  File "/opt/ros/eloquent/lib/python3.6/site-packages/qt_gui/plugin_handler_direct.py", line 55, in _load
    self._plugin = self._plugin_provider.load(self._instance_id.plugin_id, self._context)
  File "/opt/ros/eloquent/lib/python3.6/site-packages/qt_gui/composite_plugin_provider.py", line 72, in load
    instance = plugin_provider.load(plugin_id, plugin_context)
  File "/opt/ros/eloquent/lib/python3.6/site-packages/qt_gui/composite_plugin_provider.py", line 72, in load
    instance = plugin_provider.load(plugin_id, plugin_context)
  File "/opt/ros/eloquent/lib/python3.6/site-packages/rqt_gui_py/ros_py_plugin_provider.py", line 64, in load
    return super(RosPyPluginProvider, self).load(plugin_id, ros_plugin_context)
  File "/opt/ros/eloquent/lib/python3.6/site-packages/qt_gui/composite_plugin_provider.py", line 72, in load
    instance = plugin_provider.load(plugin_id, plugin_context)
  File "/opt/ros/eloquent/lib/python3.6/site-packages/rqt_gui/ros_plugin_provider.py", line 107, in load
    return class_ref(plugin_context)
  File "/opt/ros/eloquent/lib/python3.6/site-packages/rqt_graph/ros_graph.py", line 193, in __init__
    self._update_rosgraph()
  File "/opt/ros/eloquent/lib/python3.6/site-packages/rqt_graph/ros_graph.py", line 285, in _update_rosgraph
    self._graph.update()
  File "/opt/ros/eloquent/lib/python3.6/site-packages/rqt_graph/rosgraph2_impl.py", line 495, in update
    updated = self._graph_refresh()
  File "/opt/ros/eloquent/lib/python3.6/site-packages/rqt_graph/rosgraph2_impl.py", line 307, in _graph_refresh
    self._node.get_publisher_names_and_types_by_node(name, namespace):
  File "/opt/ros/eloquent/lib/python3.6/site-packages/rclpy/node.py", line 1501, in get_publisher_names_and_types_by_node
    capsule, no_demangle, node_name, node_namespace)
RuntimeError: Failed to get_publisher_names_and_types: node name must not contain characters other than alphanumerics or '_', result: 2, at /tmp/binarydeb/ros-eloquent-rcl-0.8.4/src/rcl/graph.c:62

Even though it's clear that rqt cannot show the extra raw DDS publisher, it should still show the existing ROS Nodes.

Please consider to contribute a pull request to make the plugin for resilient against this exception.


How to send quantitative information associated to a microbiology germ?

This issue has been identified by one of our customers during there tests:
In our LIS, when a germ was identified as part of a culture test, the germ is sometimes associated to a quantitative information in free text form (for example +++ to indicate that a lot of germs where found).
Example of how it looks on our PDF attachment:

We currently send the information as follow in our FHIR message
microbiology report with quantification.json
"valueCodeableConcept": {
"coding": [
{
"code": "esco",
"display": "Escherichia coli",
"system": https://www.uza.be/MOLIS/MCRES
}
],
"text": "Escherichia coli (Positief voor)"
}
but we noticed that the text 'Escherichia coli (Positief voor)' is not displayed in the visualizer:

Are we doing it wrong and, if so, do you have any recommandations how we should send this?
If was thinking about adding this information as annotation to the observation or maybe generate an additional child observation of the culture with a "string value" as result but I'm unsure what is the best solution from the point of view of the FHIR standard and I prefer to ask your advice before changing anything.
Thank you for your help!

@frederic-istace ,
Frederic, here is my take at encoding this info: (based on example from UZGent):
{
			"fullUrl": "urn:uuid:9b7f62d2-c491-4978-b0f7-757df16b94e9",
			"resource": {
				"resourceType": "Observation",
				"code": {
					"coding": [
						{
							"code": "esco",
							"display": "Escherichia coli",
							"system": "https://www.uza.be/MOLIS/MCRES"
						}
					],
					"text": "Escherichia coli"
				},
				"id": "9b7f62d2-c491-4978-b0f7-757df16b94e9",
				"performer": [
					{
						"reference": "urn:uuid:e182bf60-889a-451e-84a2-c0c971b9b797"
					}
				],
				"status": "final",
				"subject": {
					"reference": "urn:uuid:b8fae4dd-df40-4f4c-bfbe-c7410e92bc4c"
				},
				"valueString": "+++",
				"note": [
					{
						"text": "Geen kiemen gezien, mogelijks vals positief. Hk-fles wordt verder geincubeerd."
					},
					{
						"text": "Geen kiemen gezien, mogelijks vals positief. Hk-fles wordt verder geincubeerd. (Positief voor)"
					}
				]
			}
		}

What you definitely cannot do is this:
{
      "fullUrl": "urn:uuid:e501074c-abcc-4207-acb6-48f10b3b7f59",
      "resource": {
        "resourceType": "Observation",
        "code": {
          "text": "1"
        },
        "id": "e501074c-abcc-4207-acb6-48f10b3b7f59",

Because there is no code in .code, and the text value of code is meaningless (just an ordinal number), it is completely unclear what this Observation is about, when you remove it from the document. In phase 3, Observations will be made searchable on criteria, and if you do not make .code meaningful, this Observation will never be found based on the .code .

@frederic-istace ,
Not completely. Basically, you should consider an Observation resource as a key - value pair.
The key is in .code, and should contain what it is about (i.e. test ID or a panel ID), and value[x] is the result of the test, or .hasMember contains the elements of the  panel.
The .code can never contain "Negatief", because that is a value, not a key. The same for "Geen kiemen gezien[...]", that is also the result of the test, not which test has been done. These results should be in valueString (if they are textual, and the core result) or in .note.text (if they are comments to the core result).

@bdc-ehealth
It's a little bit difficult to explain to somebody who doesn't know our application but I don't see exactly how I can map our logic to what you describe in perfectly structured way.
In our LIS, a general culture test can have on ore more result. Each result is basically an isolation of this culture. The result of an 'isolation' is either a germ which was found (e.g. "Escherichia coli") or a code associated to a result like "neg" for "negative". In addition to that, the germ is typically associated with a quantitative information like for example '+++'.
So, what code could we use when there is no growth for a isolation? Is there a suitable code in LOINC available for that? Should we just repeat the code of the parent observation? This would look a little bit strange in the visualizer, as we would see 2 times the  text "Anaerobe kweek".
An easy solution, to follow your description, would be to put the whole thing in a string value and send it as the result of the observation "Anaerobe kweek" but this would very poorly structured. We would lose the possible to encode microbiology organism found as result of a culture with SNOMED. (There is SNOMED code included in our example but it's just because no mapping to SNOMED has been configured on the system yet and thus, you just see our internal code 'esco' for 'Escherichia coli' instead of the SNOMED CT code 112283007.
So, is it really a good idea to send everything as string value? I know that none of the use cases on the test server is currently checking for SNOMED but is not something which will be expected in the future?
I'm not a biologist, so I understand that my explanation is maybe a little bit unclear and my wording not totally right from a microbiology point of view...

@bdc-ehealth
I have adapted the previous example a little bit:
81160393998_MI23110075_l_L_999_4_20240325.json

Would you consider this one as ok?


create sort_drawdown macro

In R, sort_drawdowns simply sort the data from find_drawdowns from the worst return to the best. I think it'll be more convenient to add a 'sort' option in find_drawdowns macro to implement this function.

Sort_Drawdowns will still be created in consistent with R package

done by #129


Add JDK_VERSION and JDK_IMPL in AutoReenableJob

Add JDK_VERSION and JDK_IMPL in AutoReenableJob https://ci.adoptopenjdk.net/view/Test_grinder/job/AutoReenableJob/
A user is able to run AutoReenableJob with specific JDK_VERSION and JDK_IMPL. Both JDK_VERSION and JDK_IMPL values can be comma-separated. The default value is 11 and hotspot respectively.
Once the user provides the values, the pipeline script should loop through output.json and only trigger the matched tests.
Related: https://github.com/adoptium/aqa-tests/issues/1853

Can I have this issue assigned to me? Thank you!


a sidecar injector exists for secretless

GIVEN a pod template with relevant annotations e.g.
    metadata:
      annotations:
        sidecar.secretless.io/inject: "true"
        sidecar.secretless.io/config: "quick-start-application-secretless-config"
        sidecar.secretless.io/secret: "quick-start-backend-credentials"

AND the sidecar injector has been installed
WHEN the pod is created
THEN a secretless sidecar should be injected
AND the annotation schema/definition should provide sufficient flexibility to allow for configuration of the secretless sidecar using configmaps and kubernetes secrets etc.
See reference implementation.
AC:

[ ] cert generation for mTLS
[ ] k8s deployment that includes our sidecar injection webhook webserver
[ ] k8s service bound to that deployment
[ ] k8s webhook config defining where k8s should look to find out webhook endpoint/service
[ ] installation guide

Should be followed by https://github.com/cyberark/secretless-broker/issues/336


is there a plan for debug adapter feature for vsc,it's useful.

is there a plan for debug adapter feature for vsc,it's useful.

No plans, but it is on my mental wishlist. It would certainly be very useful.

I'm working on it.
#4


Fastnlight: Watch ensembledata.com

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

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

Approved by Jeff Schaller in Charcoal HQ


Support remote ISPN caches

This is a big PR. I tried to break it to some commits, but still big.
I have done some tests on my local, i.e., start a docker for infinispan-server, config/enable remote cache for content-index, maven-metadata, etc, then run some requests, and watch the status on remote cache admin console.
The point to highlight is that this PR support remote cache in a flexible way, i.e., if remote cache is not enabled, it just works as usual embedded caches.
Please review.

I merge it. We can see how it works on devel.


FeatureCache is over-checked and over-reset

From @benaadams on Wednesday, August 23, 2017 6:59:06 PM
A simple plantext middleware as below, will check the Frame IFeatureCollection 7 times and initialize/reset the Context, Resquest and Responses feature caches twice each.
public static Task WriteResponse(HttpResponse response)
{
    var payloadLength = _helloWorldPayload.Length;
    response.StatusCode = 200;
    response.ContentType = "text/plain";
    response.ContentLength = payloadLength;
    return response.Body.WriteAsync(_helloWorldPayload, 0, payloadLength);
}

The extra reset and checks are from initalization; then reinitialization after RequestServicesFeature is added to the collection by the host, increasing the IFeatureCollection's version count.
Copied from original issue: aspnet/HttpAbstractions#924

Resolved by https://github.com/aspnet/AspNetCore/pull/7659


feat: support for schnorr signatures

Add support for schnorr signatures in secp256k1 signer

it would be cool to integrate the new keychain with asests' bitcoin and run all the tests Another alternative is to generate more fixtures from assets' tests

There is a draft here: https://github.com/ExodusMovement/assets/pull/2059

in addition to pass key, this new key chain would reduce the desktop signing process to bare bone right? Removing all of this wallet code

Yes it would! :grin:


Kernel behavior

This is a python kernel Notebook:

Is there a way to do it with dart kernel:

@tomas291184   thanks for reporting the issue.
My understanding is this has to do w/ function scope.  So, basically, the way the program runs is that it wraps everything in a main rust program and runs it and gives you the output in the notebook.  i.e., you can't have two functions in your main program with the exact same function signature.
This is a simple wrapper kernel.  When you use python in jupyter, it relies on an interactive kernel, ipython.
https://ipython.readthedocs.io/en/stable/
Since writing this wrapper kernel for dart, an interactive package has also been released for Dart:
https://pub.dev/packages/interactive
In any case, I think such functionality ** can ** be achieved, but it would require integrating with a more interactive kernel, where you have access to certain intermediate representations of variables, functions, the call stack, etc.
If you would like, we can repurpose this issue (I.e., just change the title) to something like - "Investigate using an Interactive Kernel for Dart".  Basically, a spike - b/c this would be a heavier lift and would require understanding what/how the nature of the interactive kernel works.
It would certainly be cool and it would be much more like how python works inside the notebook.
Thanks again for reporting this.

@tomas291184   going to keep this issue open, just in case, anyone wants to investigate using the interactive package for Dart and see if that makes things easier.


Feat: Adding ContactUs Backend Functionality using NodeMailer

Fixes #271 Adding contactUs backend functionality using nodemailer:)
@soham0005 Please assign level-3 because it required alot of code:)
Testing:)
https://github.com/user-attachments/assets/cc5aada9-f5f1-45f4-9ce7-b6961fac1ac8
MAIL

When onSubmit called then it call to apiConnector:)

Api Connector called to backend api by creating axios instance:)

Backend:)
Middleware for contactUs

Backend "/contact" recieve post request and called to contactUsController

It call to mail sender function using try catch for error handling:)

It create a instance of nodemailer and after call to sendMail function and also render template for recieving mail

Mail template:)

@soham0005 Please review it and merge with lable and assign level-3.

@soham0005 Please review and merge it with label and please assign level-3 because it required alot of code.

@soham0005 Please review:)

@soham0005 Please review it and merge with label and assign level-3.

@soham0005 Please assign level-3 and merge it:)

@soham0005 Please review and merge it with labels:)

@soham0005 Please assign Level-3 it required alot of code.


Reconfigure Renovate - group scala http packages together

resolves https://github.com/apereo/openEQUELLA/pull/1000#issuecomment-502536618

Thanks for that @ChristianMurphy !! :+1:
Just tweaked the title to comply with: https://renovatebot.com/docs/reconfigure-renovate/
Once renovate gives us the ticket I'll merge.

Okay, it would seem renovate is taking too long, and travis is unhappy again. So... I'm just going to cowboy it - i.e. merge and see.


MRTK/Standard Shader Clipping Primitives Improvements & Additions

Overview
Improved per-pixel primitive clipping feature by adding:

Performant sphere, and box shape clipping (plane clipping already existed)
Ability to specify which side of the primitive to clip against (inside or outside)
User friendly shader GUI and gizmo support
Examples in the material gallery

Other changes:

Improved refractive glass material
Moved the HoverLight component to the core for nameof support in the shader GUI

Such a good feature. Thanks @Cameron-Micka!

Agreed!

@radicalad @davidkline-ms thank you!


pgr-query returns no hits for known sequence

Hi,
I am attempting to use pgr-query to search the human pangenome draft.  Known exact hits are not being found.  For example:
pgr-query pangenome_draft1_v1.1 test1.fa test1_output
returns no hits and an empty fasta:
cat test1_output.hit
#out_seq_name   ctg_bgn ctg_end color   q_name  orientation     idx     q_idx   query_bgn       query_end       q_len  aln_anchor_count

The input sequence is definitely present:
cat test1.fa
>test1
CAGAATGGACCTTCTCCACCAGGAGAGGCTTCCAAGTGACTTGGACGGCATGCTCACTGAGCCCTTGGACTGTGACATGG

Querying a contig with agc returns the sequence:
agc getctg pangenome_draft1_v1.1.agc<EMAIL_ADDRESS>| grep -n CAGAATGGACCTTCTCCACCAGGAGAGGCTTCCAAGTGACTTGGACGGCATGCTCACTGAGCCCTTGGACTGTGACATGG
3:CAGAATGGACCTTCTCCACCAGGAGAGGCTTCCAAGTGACTTGGACGGCATGCTCACTGAGCCCTTGGACTGTGACATGG

What might cause this?  Is there a minimum query sequence length?

The PGR-TK is not designed for searching for short sequencing. If you read the algorithm section, it needs the sequence long enough for creating the minimizer anchors. Please take a look at the provided examples. You can increase the windows of the sequences that you want to search to get results.

Ok, thanks.


Switch loki to use graphicsmagick instead of look-same

look-same is javascript only image comparision and slow. Switching to
graphicsmagick may help as it's processing is faster
Description
Explain a little about the changes at a high level.
Reviewer Notes
Is there anything you would like reviewers to give additional scrutiny?
Setup
Add any steps or code to run in this section to help others prepare to run your code:
echo "Code goes here"

Code Review Verification Steps

[ ] Code follows the guidelines for Logging
[ ] The requirements listed in
Querying the Database Safely
have been satisfied.
Any new migrations/schema changes:

[ ] Follow our guidelines for zero-downtime deploys (see Zero-Downtime Deploys)
[ ] Have been communicated to #g-database
[ ] Secure migrations have been tested following the instructions in our docs

[ ] There are no aXe warnings for UI.
[ ] This works in Supported Browsers and their phone views (Chrome, Firefox, IE, Edge).
[ ] Tested in the Experimental environment (for changes to containers, app startup, or connection to data stores)
[ ] User facing changes have been reviewed by design.
[ ] Request review from a member of a different team.
[ ] Have the Jira acceptance criteria been met for this change?

References

Jira story for this change
this article explains more about the approach used.

Screenshots
If this PR makes visible UI changes, an image of the finished UI can help reviewers and casual
observers understand the context of the changes. A before image is optional and
can be included at the submitter's discretion.
Consider using an animated image to show an entire workflow instead of using multiple images. You may want to use GIPHY CAPTURE for this! 📸
Please frame screenshots to show enough useful context but also highlight the affected regions.

Warnings

:warning:
Please add the JIRA issue key to the PR title (e.g. MB-123)

  Generated by :no_entry_sign: dangerJS against 718db2b9863762ef25bf4404741a1b0a947cc01b

@gidjin Should this be closed now that we've moved to Happo instead of Loki?

@duncan-truss yes this is defunct now that loki is gone. I'll close this pr, thanks for checking!


Specializations

Given charter 15 of the specification a specialization is a std element with a special objective.
I need a specialization of a capability and want to add that to the palette.

Hi,
For the moment Archi does not directly support language customization. The best you can do is to manually add a "Stereotype" property on concepts to keep track of the specialization name. You can then use Herve's Specialization plugin to change the concept's label to "Concept_Name <<Specialization_Name>>" and (if needed) an alternate icon. And instead of doing all this manully for each new concept, you can prepare it in a "Toolbox" that can be used as a custom palette.


[#168752299] Order by name the administration search results

This PR aims to order alphabetically the results of the administration search.

Affected stories

🌟 #168752299: Come gestore, quando cerco un ente, voglio che i risultati siano in ordine alfabetico

  Generated by :no_entry_sign: dangerJS against 044d85c6732ad1e96356c4eb9d92148f8cc4a94c