Make opacity of overlay and opacity of background controllable

Hi,
is it possible to have a background opacity without touching the opacity of the overlay controller? this would be really nice

Hi @Windisch94, thanks for opening an issue, that's a very good catch, thanks!
I just made a new release with this, please check out v0.8.8. Let me know if it doesn't resolve your issue.


[Microsoft.StorageSync] Add AFS file share metadata certificate public keys API to version 2022-06-01 (S360 compliance)

The purpose of this PR is to address an S360 item for swagger completeness. We have a special API that is used by the Azure Backup (MAB) RP to query some information from our RP. We previously didn't document this API in swagger because it's only meant to be used by MAB. However, due to the swagger compliance item, we will need to document it. This will be consisten with other backup/restore APIs that we have documented at the cloud endpoint level
ARM API Information (Control Plane)
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Azure 1st Party Service can try out the Shift Left experience to initiate API design review from ADO code repo.  If you are interested, may request engineering support by filling in with the form https://aka.ms/ShiftLeftSupportForm.
Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[ ] update existing version for new feature
[x] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
Our service has already been deployed with this feature. It's used by MAB, so they don't have any dependency on the API being in documented in swagger.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
We are looking to publish the swagger as soon as possible.
By default, Azure SDKs of all languages (.NET/Python/Java/JavaScript for both management-plane SDK and data-plane SDK, Go for management-plane SDK only ) MUST be refreshed with/after swagger of new version is published. If you prefer NOT to refresh any specific SDK language upon swagger updates in the current PR, please leave details with justification here.

Contribution checklist (MS Employees Only):

[x] I commit to follow the Breaking Change Policy of "no breaking changes"
[x] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[x] Check this box if any of the following apply to the PR so that the label "ARMReview" and "WaitForARMFeedback" will be added by bot to kick off ARM API Review.  Missing to check this box in the following scenario may result in delays to the ARM manifest review and deployment.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits. You can use OpenAPIHub to initialize the PR for adding a new version. For more details refer to the wiki.

[x] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If you have any breaking changes as defined in the Breaking Change Policy, request approval from the Breaking Change Review Board.
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Additional details on the process and office hours are on the Breaking Change Wiki.
NOTE: To update API(s) in public preview for over 1 year (refer to Retirement of Previews)
Please follow the link to find more details on PR review process.

/azp run

Signed off from ARM side , but this still needs approval from breaking change board before checking in

Signed off from ARM side , but this still needs approval from breaking change board before checking in

@raosuhas This API version (2022-06-01) has not yet been publicly released, I'm making this PR to a dev branch for the API version. This should not constitute a breaking change. Based on this information, could you please comment and confirm that this is not a breaking change?


Flipping coordinates for biplot ordination

Addition Description
One thing that could become increasing helpful with the introduction of feature-specific stats (i.e. songbird, aldex2, rhapsody, qurro) is the ability to flip ordinations.
For example, if someone wants to analyze their metabolites in a qurro rank plot, they would need to first flip their ordination coordinates (i.e. swap sample coordinates with feature coordinates) so that they can have metabolites as "features".
Another use case is if someone wants to visualize the microbe co-occurrences learned from DEICODE - it'll require the features to be plotted instead of the samples.
Given that this will likely be a recurring pattern, it may make sense to have this "flipping" operation further upstream.
Current Behavior
Doesn't exist at the moment.
Proposed Behavior
I've written a simple CLI script that can do this at the moment - but if there is interest, I'll be happy to make a contribution to q2-diversity
from skbio import OrdinationResults
import sys

res = OrdinationResults.read(sys.argv[1])
samples = res.samples.copy()
features = res.features.copy()
res.samples = features
res.features = samples
res.write(sys.argv[2])

References
https://github.com/biocore/qurro
https://github.com/biocore/DEICODE
https://msystems.asm.org/content/4/1/e00016-19
CC @fedarko @cameronmartino @ElDeveloper

Wouldn't it make more sense for the visualizers to do the flipping as appropriate? Otherwise I worry that this could enable "illicit" actions, e.g., if passing those ordination results to a method that should not operate on flipped samples/loadings.
I see that this makes more sense for feature-specific stats, but keep in mind that rhapsody is currently making use of the PCoAResults % Properties('biplot') type. Should we be allowing samples/loadings to be flipped for all biplot results? Maybe we need to define a new OrdinationResults % Properties('FeaturesBiplot') type that rhapsody and other plugins use when they make microbe/metabolite biplots?

Good point @nbokulich .  One option along those lines is to have an --p-invert option for each of the visualizers that flips the assignment of points vs arrows or vice versa.
There is a similar issue raised here.
I'm not sure how I feel about defining a OrdinationResults % Properties('FeaturesBiplot') - how would a FeaturesBiplot be difference just a Biplot?  There are definitely use cases for allowing for all biplots to be flipped -- for instance, if the coordinates in DEICODE were flipped (where points now represent microbes), the distances between points would directly map to microbe-microbe co-occurrence strengths.

@thermokarst @nbokulich moving this to emperor and eventually qurro, since it is probably a better place to put this


the division of data set

Hello,
Thank you for sharing the code. I'm interesting in your work. But I still have a question about  the division of the data set. How did you divide your test data set?

Hi, the split between training/val/test splits is the same as in the original training set.
About the division for the incremental training: we followed previous works on the topic, like ILT or MiB.
To make it short: we consider in the test set all the images having only previously seen classes inside.
Hope that this helps.
Kind regards.


Running OccamBSD on non-HAMMER platforms

Currently, if I run ./occambsd.sh -p some-profile.txt on a non-AMD64 machine, I get an error like this.
buildkernel failed

root@devbsd14:~/occambsd # tail -5 /tmp/occambsd/logs/build-kernel.log
/tmp/occambsd/OCCAMBSD: unknown option "HAMMER"

make[1]: stopped in /usr/src

make: stopped in /usr/src

Obviously, the issue is that we're setting the CPU to HAMMER, while we're on a non-AMD64 machine.
I did a simple change which is
-echo "cpu      HAMMER" > $work_dir/OCCAMBSD
+case "$(uname -m)" in
+  arm64) CPU=ARM64;;
+  amd64) CPU=HAMMER;;
+esac
+
+echo "cpu      ${CPU}" > $work_dir/OCCAMBSD

And now I get
buildkernel failed

root@devbsd14:~/occambsd # tail -10 /tmp/occambsd/logs/build-kernel.log
WARNING: duplicate device `scbus' encountered in /tmp/occambsd/OCCAMBSD
config: Error: device "aesni" is unknown
config: Error: device "atkbdc" is unknown
config: Error: device "psm" is unknown
config: Error: device "vga" is unknown
config: 4 errors

make[1]: stopped in /usr/src

make: stopped in /usr/src

Clearly, OccamBSD is AMD64 specific.
Digging into the code I found things such as
https://github.com/michaeldexter/occambsd/blob/50eca54e59e0edc8f43aeeaa809bb3fe4359a593/occambsd.sh#L92
https://github.com/michaeldexter/occambsd/blob/50eca54e59e0edc8f43aeeaa809bb3fe4359a593/occambsd.sh#L108
https://github.com/michaeldexter/occambsd/blob/50eca54e59e0edc8f43aeeaa809bb3fe4359a593/occambsd.sh#L144-L171
And the list goes on.
Maybe under this issue we can discuss how can we make OccamBSD platform-agnostic, which steps we need to take and test it on multiple systems.
Personally, I AMD64 and ARM64 as well as IBM Power8, which should cover most of the cases.
The complex part is going to be adding some grepping and what-not to get the list of the modules that we need.

Fixed. Please test.
ARM uses kernel includes while the other platforms support kernel options and devices.
I have added support for this and it builds, but I have not tried it on QEMU or hardware.
The only bug I see is that the CD-ROM step fails with:
install -T release -o root -g wheel -m 555   cc_cdg.ko /usr/obj/usr/src/arm64.aarch64/release/dist/kernel/boot/kernel/
install: cc_cdg.ko: No such file or directory
*** Error code 71
I did not investigate to see if the ARM* CD-ROM images are built differently (like the RPi images).
It is HIGHLY LIKELY that you will need to modify the profile-arm64-minimum.txt profile to get it to boot, but, the infrastructure is there.


[Python][CI] Extension type test fails with pandas 2.0.2

Describe the bug, including details regarding any error messages, version, and platform.
These tests were already skipped on pandas 2.0.1 but on 29th May a new release of Pandas was done (2.0.2) and those tests have started failing again.
This was fixed on: https://github.com/apache/arrow/issues/35321
Example of job failing with 2.0.2: https://github.com/ursacomputing/crossbow/actions/runs/5116312550/jobs/9198356098
Component(s)
Continuous Integration, Python

@jorisvandenbossche I saw you assigned this to yourself. I did a quick PR but happy to drop it if you do a new one :)

That PR is fine to just have the CI green short-term, but I can still take it on me to do a proper investigation (whether it's a regression on the pandas side that should be fixed, or something to fix on our side, ..)


Add docs contributor's guide and docs template

Description
This PR contains most of the docs contributor's guide. It is missing the "open a PR online" guide as that guide contained many screenshots and is currently (I think?) not possible anyway if a user wants to add images since they wouldn't be able to use lfs.
New documents:

contributing documentation index contains a step by step guide to writing a new document, including updating TOC and pairing the document with jupytext
a documentation template notebook with instructions for taking screenshots and hiding code cells

I've made quite a few edits since we last looked at this stuff, so I'd appreciate a really thorough review from @jni and whoever else is interested.
Particular notes

there is currently no mention of git-lfs in this documentation, or indeed, any explanation on how to add non-autogenerated screenshots. Since that's currently in flux, I wasn't sure whether we wanted to say anything - @jni thoughts?
we may want to move this to make it more discoverable? Certainly once it's merged we should update our PR template to point to these resources

@jni I think I've addressed everything? It's late in the afternoon for me though and I'm all out of scooby snacks so please let me know if I've missed anything 🙏


Change request - AngularJS & Angular

I'm submitting a ...  (check one with "x")
[ ] bug report => search github for a similar issue or PR before submitting
[x] feature request
[ ] support request => Please do not submit support request here, instead see https://github.com/ceolter/ag-grid/blob/master/CONTRIBUTING.md#question

Current behavior
In some docs you use Angular 2, in some AngularJS, AngularJS 1.
In code, the initialization method is initialiseAgGridWithAngular1
Expected behavior
Use the names Angular and AngularJS
Not a pressing matter, just a nice change to see
What is the motivation / use case for changing the behavior?
Angular 2 is long gone, Angular 4 is currently out, and 5 is in beta. This is just the preferred naming by the angular team

Hi @AmitMY - this is something we'd like to do and are aware of the naming change, but a lot of our users aren't I'm afraid.
We found that there was some confusion - at least initially - when we replaced Angular 2 with just Angular.
I think this will remain as is for at least another few months after which we will switch to the new names.
Thanks for the suggestion though :-)


Array mutation events are fired twice when changing the last item in an array when the item is a paper-toggle-button.

This may not be limited to paper-toggle-button (may be related to boolean data types).
Whenever I use Polymer.Base to add a new record to a two-way bound array of objects, and I toggle a paper-toggle-item bound to one of the fields in the last item in the array, the change is fired twice.  Future toggles of the same item only fire once.
Reproduced here:
http://jsbin.com/varucanica/edit?html,console,output

This is an element-specific side-effect of known issue https://github.com/Polymer/polymer/issues/2360.
Note in the example, the model for the added checkbox is not equivalent to the initial models: whereas the initial models have either state: true or state: false, the newly added model has an undefined state (this is important for the repro).  Issue https://github.com/Polymer/polymer/issues/2360 covers the problem with binding checked={{item.state}} where state is undefined resulting in the checked property being undefined despite having a default value of false.
The reason the observer is fired twice when toggling the button is due to an element-specific implementation detail:

in response to the down event, the element syncs the checked value to the active value, causing the still false active value to be set to checked, resulting in an undefined --> false change sent to the observer
in response to the tap event, the element sets the checked value to true, resulting in another call to the observer

If you click the element slowly, you can notice the observers fire on different events (down vs. up).
If the repro is modified so that the state property is valued when pushing a new object, the issue is avoided:
  addThing: function(e) {
    this.push('listOfThings', {state: false});
  },

That would be the suggested workaround for now until the underlying issue is resolved (which is relatively high priority for us).

Kevin thanks for the write up.  I'll give the workaround a try.

Closing as duplicate of #2360


Avoid misuse of Build annotations

Don't store the 'docker build' logs there.
Don't store the rpm package list there.

Coverage decreased (-0.4%) to 87.089% when pulling bf9bd3728701ed5f8521a44f291d92f52a09e4c6 on no-rpmqa-logs-annotations into ebeea780762f87dd3df103269b26157783b5462d on master.

Coverage decreased (-0.04%) to 87.436% when pulling 062d0f4282efc015153e4fb0437400e99be07cbc on no-rpmqa-logs-annotations into ebeea780762f87dd3df103269b26157783b5462d on master.

LGTM, merged, looking forward to OSBS working on unpatched OpenShift;)


update to go1.18, drop go1.18, and replace deprecated syscall.Syscall

gha: update golangci-lint to v1.52.x
update to go1.18
tools/mkwinsyscall: replace deprecated funcs with SyscallN (drops go1.17)
The "syscall.Syscall" functions were deprecated in go1.18 in favor
of the "syscall.SyscallN" function, which does not need the "nargs" argument,
and does not need the list of arguments to be padded with zeros.
https://github.com/golang/go/blob/go1.18/src/syscall/dll_windows.go#L27-L45
Now that go1.17 reached EOL and is no longer maintained, we can update the
code to use the new SyscallN function. This patch updates the mkwinsyscall
utility to generate code using the new SyscallN function, and removes the
utilities that are now redundant.
internal/socket: replace deprecated syscall.Syscall9

This should be ready for review /cc @kevpar 😄
(I should probably point out that containerd 1.6 still tests against go1.17 as "old version", in case this version from main ends up in containerd at some point; https://github.com/containerd/containerd/blob/v1.6.20/.github/workflows/ci.yml#L236)


_zsh_autosuggest_modify:27: unrecognized modifier `0'

when i use zsh_autosuggestion in my oh-my-zsh plugins, it prompt “_zsh_autosuggest_modify:27: unrecognized modifier `0'”. I don't know what happend, help me, please!

I repaired it when i upgrade cento OS from version 6.3 to version 6.10. Tank you!

Looks like a dup of #250


[AutoPR network/resource-manager] Modify some PE/PLS properties for update

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/6894

This PR has been merged into https://github.com/Azure/azure-sdk-for-go/pull/5512


eclint: 0.5.0 -> 0.5.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/eclint/versions.
meta.description for eclint is: EditorConfig linter written in Go
meta.homepage for eclint is: https://gitlab.com/greut/eclint
Updates performed

Golang update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.5.1 with grep in /nix/store/jvdxqisz0xwainyjs3h2ng1v7kyp655z-eclint-0.5.1
found 0.5.1 in filename of file in /nix/store/jvdxqisz0xwainyjs3h2ng1v7kyp655z-eclint-0.5.1

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

eclint

Instructions to test this update (click to expand)

Either download from the cache:
nix-store -r /nix/store/jvdxqisz0xwainyjs3h2ng1v7kyp655z-eclint-0.5.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nixpkgs-update-cache.nix-community.org/' \
  --option trusted-public-keys '
  nixpkgs-update-cache.nix-community.org-1:U8d6wiQecHUPJFSqHN9GSSmNkmdiFW7GW7WNAnHW0SM=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The nixpkgs-update cache is only trusted for this store-path realization.)
For the cached download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A eclint https://github.com/r-ryantm/nixpkgs/archive/73a527ae79c8450aa9b29b7235874d672837590d.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/73a527ae79c8450aa9b29b7235874d672837590d#eclint

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/jvdxqisz0xwainyjs3h2ng1v7kyp655z-eclint-0.5.1
ls -la /nix/store/jvdxqisz0xwainyjs3h2ng1v7kyp655z-eclint-0.5.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review

x86_64-linux

:white_check_mark: 1 package built:

eclint

Maintainer pings
cc @lucperkins for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 368039

aarch64-darwin

:white_check_mark: 1 package built:

eclint


Dissociate virtual display size and capture size

Allow capturing virtual displays at a lower resolution using -m/--max-size.
In the original implementation in #5370, the virtual display size was necessarily the same as the capture size. The --max-size value was only allowed to determine the virtual display size when no explicit size was provided.
Since the dpi was scaled down accordingly, it is often better to create a virtual display at the target capture size directly. However, not everything is rendered according to the virtual display DPI. For example, a page in Firefox is rendered too big on small virtual displays. Thus, it makes sense to be able create a virtual display at a given size, and capture it at a lower resolution with --max-size. This is now possible using OpenGL filters.
Therefore, change the behavior of --max-size for virtual displays:

it does not impact --new-display without size argument anymore (the virtual display size is the main display size);
it is used to limit the capture size (whether an explicit size is provided or not).

This new behavior is consistent with main display capture.
@Withoutruless This is the behavior you requested here: https://github.com/Genymobile/scrcpy/pull/5370#issuecomment-2439690605

scrcpy-win64-pr5506.zip SHA-256: 7d4b7451fd56820b64bd33060137b7a44391979318a5c82db67c33ad7354943

i tried it out and it works just fine, thank you rom1v.
are you going to merge this?

i tried it out and it works just fine

:+1: Thank you for the test!

are you going to merge this?

Yes.


Briefing Book

From @joebayles on September 28, 2015 18:14
https://nsec.esri.com/arcgis/home/item.html?id=db3f367dcfca4cc7b28ca288c0037323

[x] No Summary
[x] No Credits
[x] Delete Protection Disabled

Copied from original issue: ArcGIS/mil-intel-desktop-solutions-templates#125

Updated from AGOL version. Back at you @joebayles

Released to ReleasedOpsServer


Email subscription not visible

I enabled "Allow people to signup to email notifications?" in the settings view, but it's not showing up on the status page. Did i miss something?

Have you cached the config? If so, you need to clear the cache - normally done by just caching it again.

in the settings view

Ahhh, missed that...

any idea how to solve that?

Enable the setting in the dashboard.
Set the .env settings for MAIL_NAME and MAIL_ADDRESS.
Clear the cache php artisan config:clear

Done :)

would be nice to have some info in the README ;) thx will try it out!

We do have documentation at https://docs.cachethq.io/v1.0/docs/subscribers :)

thx! i just tried tried it...even after setting all required env variables and clearing existing cache configuration (even after reboot) it's not visible (i'm running cachet in the docker container)

Is the Docker build up to date?

We don't do much with Docker, it's left to contributors.

I'm using the lastest available docker container. I enabled the function in the settings, cleared the cache, defined the required env variables. What else could be the reason for not showing up on the status page? Any idea?

Hi @svenmueller, are you setting those variables via the docker run -e MAIL_NAME=Email ?
I am still trying to determine the behavior of the ENV variables in the Docker container version. It seems like there is some dependency on the .env file existing per the Cachet design, but it is not present in the current iteration of the Dockerfile and resulting image.  (Some discussion on this in #732)

@rtrauntvein yes, i think this is the underlying cause (#732) the passed variable (via -e) are simply not used as expected

Ok that confirms my suspicions.
We will need to figure out how the Database variables work currently for the Docker version, and if this can be extended to the other variables.
Otherwise there may be some re-working required to make the docker version actually use a .env within the container.

Is there any reason why Docker can't use the .env file?

It could use an .env file.
It is a pretty common convention in the docker world to set environment variables dynamically at container runtime.  That way we don't statically create an external file then mount it into the container, or build it into the image. Then we can do cool things with orchestration tools like have different DB credentials or other .env settings based on your environment etc.
If the application can directly read and use the system ENV variables - like with php's getenv() or something it just makes it easy, and no additional work is needed to support this.
That being said, it is pretty simple to add an init script of sorts that can inject the provided variables into a file in the container such as .env - Just requires a little sed and bash voodoo ;)

Closed by https://github.com/cachethq/Cachet/pull/788

Confirming that I am now seeing the subscribe button running the new docker image.

:+1:


advertisement&album

The completion of the album and advertisement. Advertisement data is saved in a session and ready to be inserted into the database

Great work, awaiting build fixes

Acknowledged
On Sat, Oct 19, 2024, 10:22 PM UpTech Inc. @.***> wrote:

Great work, awaiting build fixes
—
Reply to this email directly, view it on GitHub
https://github.com/uptech2021/Ourlime-Web/pull/16#issuecomment-2424430045,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BDBRNFSEZN62L4ZBQEIV6NLZ4MHVNAVCNFSM6AAAAABQH73Y3KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRUGQZTAMBUGU
.
You are receiving this because you authored the thread.Message ID:
@.***>


Check user name in route

Hello,
first of all thanks for your nice and simple to use crate!
Is it possible, to check the login user name in a route? I have only seen that AuthDetails has only a permissions value.
I ask because I would like to implement a function that a user can change his credentials, but for that I have to be sure, that the user can only change his own ones, and not from other users.

Thank you very much! This is way more easy then I though!


Segmental Fault when using Jemalloc with DTO

Environment:
Debian10
Steps to reproduce:

build jemalloc

git clone git clone https://github.com/jemalloc/jemalloc.git
./autogen.sh
make -j

start test program with jemalloc and dto

 LD_PRELOAD=path-to-libjemalloc.so:./libdto.so.1.0 ./dto-test-wodto
Segmentation fault (core dumped)

From coredump, it appears that,

Jemalloc has a dependncy on libstdc++, so loader loads libstdc++ first.
libstdc++'s init routine calls malloc which is redirected to jemalloc
jemalloc calls memset
memset is redirecto to dto
init_dto calls dlsym, which calls malloc, and goes to jemalloc again
6.after that things become a mess....

There is  a temporary hack to comment out the explicit calling of init_dto to bypass the issue, but this doesn't looks to be a reasonable soultion.
The init_dto will be inexplicitly called due to the constructor attribute, while this is happening later the time.
@@ -1328,7 +1331,7 @@ void *memset(void *s1, int c, size_t n)
                /* Use internal implementation while the
                 * library is being initialized
                 */
-               if (init_dto() == DTO_INITIALIZING)
+               //if (init_dto() == DTO_INITIALIZING)
                        return dto_internal_memset(s1, c, n);
        }

Thanks for reporting the issue.
I will look into fixing it.
From: Asa Myth @.>
Sent: Wednesday, September 13, 2023 1:21 AM
To: intel/DTO @.>
Cc: Subscribed @.***>
Subject: [intel/DTO] Segmental Fault when using Jemalloc with DTO (Issue #3)
Environment:
Debian10
Steps to reproduce:

build jemalloc

git clone git clone https://github.com/jemalloc/jemalloc.git
./autogen.sh
make -j

start test program with jemalloc and dto

LD_PRELOAD=path-to-libjemalloc.so:./libdto.so.1.0 ./dto-test-wodto
Segmentation fault (core dumped)
From coredump, it appears that,

Jemallo has a dependncy on libstdc++, so loader will load libstdc++ first.
libstdc++'s init routine will call malloc which is redirected to jemaloc
jemalloc will call memset
memset is redirecto to dto
dto_init will call dlsym, which call malloc, and go jemalloc again
and from there on things become a mess....

There is a temporary hack to comment out the explicit calling of init_dto to bypass the issue, but this doesn't looks to be a reasonable soultion.
@@ -1328,7 +1331,7 @@ void *memset(void *s1, int c, size_t n)
            /* Use internal implementation while the

             * library is being initialized

             */

          if (init_dto() == DTO_INITIALIZING)

          //if (init_dto() == DTO_INITIALIZING)

                  return dto_internal_memset(s1, c, n);

  }

—
Reply to this email directly, view it on GitHubhttps://github.com/intel/DTO/issues/3, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ADK2QY2GRVCIY4EVAQF7BRLX2FUILANCNFSM6AAAAAA4WATSVM.
You are receiving this because you are subscribed to this thread.Message ID<EMAIL_ADDRESS>

The issue is that jemalloc is trying to initialize itself and calling memmove which DTO intercepts. Now DTO calls init_dto which tries to subscribe to DSAs using accel-config APIs. It calls accfg_new() which calls calloc which goes to jemalloc again but jemalloc hasn't fully initialized yet and hence it segfaults.
To avoid this issue, use DTO_WQ_LIST environment variable. This enables DTO to subscribe to DSAs without using accel-config (and hence without calling calloc).

I have pushed a proper fix for this issue so that DTO_WQ_LIST is no longer required as a workaround. This jemalloc scenario can work now even without DTO_WQ_LIST.


FEAT: LINK GOOGLE CLOUD STORAGE DATABASE WITH CLASS MODEL

This pull request introduces several enhancements and modifications to the existing learning microservices related to file storage according to classes:

File Upload Handling:

Integrated multer middleware for handling file uploads.

Implemented logic to save uploaded files to Google Cloud Storage using the @google-cloud/storage package.

Endpoint Modifications:

Updated the POST endpoint to utilize multer for handling file uploads.

Enhanced the logic for creating a new class by storing the uploaded file in Google Cloud Storage and updating the class data
accordingly.

Modified the PUT endpoint to support both updating class fields and replacing the uploaded file if necessary.

Implemented logic to delete the old file from Google Cloud Storage when updating the file.

Checklist for Reviewer:

[x] You must to add a .json file in /server folder with google cloud API credentials

[ ]  Verify that multer is correctly configured for handling file uploads.

[x]  Ensure that the logic for saving and updating files in Google Cloud Storage is functioning as intended.

[x] Confirm that the POST and PUT endpoints are correctly handling both class fields and file uploads.

[x] Check for any potential error scenarios and ensure appropriate error handling is in place.

[x]  Validate that the DELETE endpoint correctly deletes the associated file from Google Cloud Storage.

[x] Ensure that the code adheres to best practices and maintains consistency with the existing codebase.

[x] Review the overall code structure and provide feedback on any areas for improvement or optimization.

Dont link the pr with the project pls.

There are quite a few errors missing in the methods, but you will see that in the task of reviewing the routes.

There are quite a few errors missing in the methods, but you will see that in the task of reviewing the routes.

According to this comment, I have assigned another task which I must review class routing


[web-components]: Blue border on hamburger menu first element

Description
the first item in the hamburger menu is highlighted with a blue border

In our project this is visible from the first click on the hamburger menu, but on the codepen example and in the demo links for masthead, in the documentation, it can be reproduced only on the second time you open the hamburger menu.
Component(s) impacted
masthead hamburger menu
Browser
Chrome
Carbon for IBM.com version
v2.1.0-rc.0
Severity
Severity 4 = The problem is not visible to or noticeable to an average user. Affects minor functionality, no workaround needed.
Application/website
ibm docs
Package
@carbon/ibmdotcom-web-components
CodeSandbox example
https://codepen.io/jakaeser/pen/gOqErGE
Steps to reproduce the issue (if applicable)

resize the window for a smaller resolution, until you have the hamburger menu visible in the masthead.
open the hamburger menu: nothing is highlighted
Close the hamburger menu and reopen it again: first item in the menu has a blue border

In our project, this highlight is visible from the first time the hamburger menu is opened
Release date (if applicable)
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct
[X] I checked the current issues for duplicate issues

This is a accessibility feature where when the menu is open, focus should be applied to the first menu item to make the menu keyboard accessible.
https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/menu_role


Analysis options in two places

What is the expected behavior?
In #67 analysis options will be placed in two places, namely **options of run method and as a part of experiment_data metadata. This may confuse the developers, because the same data is available in two places. We need some logic update.

This should be mostly fixed by #517 and #556. After these analysis options are only in Analysis classes, not experiment classes.


Fix blank transition builder

Alternative to https://github.com/RGB-WG/rgb-std/pull/108
Close #81
Close #108

In https://github.com/RGB-WG/rgb-std/pull/126 I moved from using dedicated *Allocation type and instead re-use types from RGB Core this way: https://github.com/RGB-WG/rgb-std/pull/126/files#diff-16373c59058401969ad1892e8d953d68a88387b2b435267816c230033c083201R83-R87
Can you please re-base this PR on top of that one to make them matching?

@dr-orlovsky,
Done.


Autocomplete in sample app

(moved from https://code.google.com/p/solrnet/issues/detail?id=74 )
Add autocomplete to the free search textbox in the sample app.

Current issue has been closed as part of cleanup process, which is tracked in https://github.com/SolrNet/SolrNet/issues/338.
Please reopen if needed, hopefully helping bringing up to date with current code.


Visual studio2015 can't open project

Error content：
The project's default XML namespace must be the MSBuild XML namespace. If the project was created in MSBuild 2003 format, add xmlns="http://schemas.microsoft.com/developer/msbuild/2003" to the  element. If the project was created in the old 1.0 or 1.2 format, convert it to MSBuild 2003 format.
What should I do to successfully compile the project?

I understand. Thank you for your help

Is there any way to open the project with vs2015?

Unfortunately, I don't know how to do it.
If you want to study or contribute OSS, you can use Visual Studio Community even if you belong a "big" company (of course, you should read its license terms carefully).


[pyupgrade] Show violations without auto-fix for UP031

Summary

This shows violations of the UP031 rule which can't be auto-fixed, so that they can be fixed manually (similar to the pylint consider-using-f-strings rule)
Test Plan

Updated fixtures.

The changes look reasonable to me but I would like a second opinion, especially if we should gate this behind preview first. @AlexWaygood wdyt?

This seems reasonable to me too. For a stylistic/modernisation rule like this, it can be annoying if it has lots of complaints that can't be autofixed. However, the unfixable complaints here are relatively small in number: most complaints from this rule are still autofixed.
I'd also prefer if this was a preview-only change first, though, just to be on the safe side.


Status of ZF3 / Trends / MVC

I use ZF2 and now 3 since it was released. I observe the status and news about the framework regularly, in the last time however I recognized that the activity of the framework decreased in some way.
I want you ask, the contributors or someone who knows more, unobtrusive about the plans of ZF3 or maybe moving trends which affects the ZF3 strategy / time of life.
I know node.js is on a never ending trend, lot of frontend stuff is moving away from backend, which is definitely affects the backend responsibilities.
I really like the ZF3 architecture because we use it in an extremely complex application.
However I really would like to see that the framework and ecosystem get developer further.
Especially the MVC and it component parts was left lying.
So:
Is ZF3 just to complex for most of the use cases or what exactly is going on with it?
Are there any further long-term plans for the framework / what's the vision?

I use ZF2 and now 3 since it was released. I observe the status and news about the framework regularly, in the last time however I recognized that the activity of the framework decreased in some way.

The activity on the components increased by a huge lot - you are most probably not following all repositories, but we have loads of releases every week, and since the split, code is much more manageable.

I want you ask, the contributors or someone who knows more, unobtrusive about the plans of ZF3 or maybe moving trends which affects the ZF3 strategy / time of life.
I know node.js is on a never ending trend, lot of frontend stuff is moving away from backend, which is definitely affects the backend responsibilities.
I really like the ZF3 architecture because we use it in an extremely complex application.

If you are worried about the MVC architecture, you must track https://github.com/zendframework/zend-mvc, which is the package that handles the currently enstablished mvc-event/route/controller/view-model/view approach. Specifically, check the releases: https://github.com/zendframework/zend-mvc/releases for anything that may break things for you.
MVC 3.x is currently stable and we're not going to change its public API, so you can safely keep relying on it.

However I really would like to see that the framework and ecosystem get developer further. Especially the MVC and it component parts was left lying.

As mentioned above, it's not left lying - we got you covered.

Is ZF3 just to complex for most of the use cases or what exactly is going on with it?

You are not watching the components, which is where the work is happening, and therefore you don't see any changes in zendframework/zendframework, which now is just a meta-package with only some defined dependencies.

Are there any further long-term plans for the framework / what's the vision?

Releases will keep going on the single packages. Meta-package may be updated on major version bumps of the component packages (only very few of those happening).
MVC component is staying as-is, with just upgrades to latest dependencies as these changes land in the other components

Hope that clarifies everything.


Update OS detection for environment report

Update OS detection for MacOS #2775
Update OS detection for Windows #2776

I recognize @kaylareopelle's request for tests as satisfied now.


cats errand is configurable for new diego tests

this is blocked on https://www.pivotaltracker.com/story/show/111813688
[#111125958]
Signed-off-by: Amelia Downs<EMAIL_ADDRESS>

Following the discussion on Slack, we are going to fix this PR by removing the skip_diego_unsupported property, and update which NO_{DEA,DIEGO}_SUPPORT tests we skip based on the value of the backend property.
/cc @zaksoup @cwlbraa @ematpl @dsabeti


Question regarding downloading reblogs

Is there an option to download only reblogs of posts from that blog?
i.e. exclude only reblogs that have a source value that is different from the blog being downloaded?

There is no option to download only reblogged posts.

Sorry I should clarify, I meant with the "download originals" option, is it possible to include self-reblogs?
Say I'm downloading the blog tumblr323 and they reblog their own original post and add content to it, would it be included?

With the option "download originals" (checkbox "Download reblogged posts" off) reblogged posts of their old posts to their own blog are skipped, even if additional content was added. At the moment it doesn't recognize this additional content and only distinguishes between normal and reblogged posts.

A blog's own reblogged posts are now treated as valid content independent from the option "download reblogged posts".

A blog's own reblogged posts are now treated as valid content independent from the option "download reblogged posts".

The issue has been fixed and closed. You can still comment. Feel free to ask for reopening the issue if needed.

The issue has been fixed and closed. You can still comment. Feel free to ask for reopening the issue if needed.


Matches not automatically parsing

Hi,
My matches have not been automatically parsing, even though it says they will be parsed.

I can manually parse the matches.
Profile:  29492429
Thanks!

It looks like you are playing almost all Ability Draft matches.
I disabled automatic replay parsing for non-significant game modes (AD/ARDM, etc.) during Dark Moon to avoid the additional load.


Release the v1.0.0

And make rid of the heavy development warning in the README file. What do you think about that @PanierAvide? :)

If it was only me, I would keep the warning and 0.x version until we have a more complete code testing and coverage. I had some surprises using functions I wasn't using before and unexpected behaviour. For example I haven't tested in a real project user preferences methods and can't be sure of their behaviour. And also improve documentation and give more practical examples.

Closing as in between there was a 1.x and 2.x release :grin:


Implement ADR-036 data signing

Closes #844

Thank you for doing this. I'm going to try it out and see if I can borrow logic. Whether or not it works for me, thanks :)

@mikedotexe please note that ADR-036 is not finalized. The current state seems to be completely discareded. Nobody is owning the spec process right now. This is one of a million ways to implement the functionality, but we're missing a spec.

@mikedotexe please note that ADR-036 is not finalized. The current state seems to be completely discareded. Nobody is owning the spec process right now. This is one of a million ways to implement the functionality, but we're missing a spec.

Thank you, I hadn't noticed that the status was "draft" here:
https://github.com/cosmos/cosmos-sdk/blob/master/docs/architecture/adr-036-arbitrary-signature.md
I wasn't able to use the code from here, but did find that I could use signAmino code I found in some unit tests elsewhere.
Basically…
    const signDoc = {
      msgs: [{
        type: 'starry-login',
        value: this.state.messageToSign
      }],
      fee: {
        amount: [],
        // Note: this needs to be 0 gas to comply with ADR36, but Keplr current throws an error. See: https://github.com/cosmos/cosmos-sdk/blob/master/docs/architecture/adr-036-arbitrary-signature.md#decision
        gas: "1" },
      chain_id: this.chainId,
      memo: "You are powerful and capable, friend.",
      account_number: "0",
      sequence: "0",
    };

    try {
      const { signed, signature } = await this.signer.signAmino(this.accounts[0].address, signDoc);
      // TODO: here's where do we a post request to our backend, localhost:5000 with info
      //   we'll copy the code stuffs below
      const valid = await Secp256k1.verifySignature(
        Secp256k1Signature.fromFixedLength(fromBase64(signature.signature)),
        sha256(serializeSignDoc(signed)),
        this.accounts[0].pubkey,
      );
      console.log('valid', valid);
      // Clear the messages area
      this.setState({message: ''});
    } catch (e) {
    …

I also noticed that Keplr doesn't allow 0 gas to be attached yet. I'll be making an issue and PR for that as soon as I can get the local version to build so I can test it.
I want to thank you for your response and concern. Your code here and elsewhere has been invaluable and thanks for following up. We're building a fun Discord bot for our project, wish us luck!

Is this ever going to be merged?

Is this ever going to be merged?

Unfortunately my last info is that there is not agreement on a spec and I don't see a point in merging some draft state.
What could work is find a few parties to develop the current draft into a spec that is independent of Cosmos SDK and has a different name.


adding icon for local-multiplayer package

Preview:

Tried my best to match the colors from @jwunderl's ui

Looks great


Delete VM related resource to fix pipeline failure.

Delete VM related resource to fix pipeline failure.

/azp run java - spring - tests

/azp run java - spring - tests

/azp run java - spring - tests

/azp run java - spring - tests

/azp run java - spring - tests

/azp run java - spring - tests

/azp run java - spring - tests

/azp run java - spring - tests

/check-enforcer override

/check-enforcer override


Command failed: /usr/bin/git checkout conf-override

When i install<EMAIL_ADDRESS>will report error.
npm ERR! Command failed: /usr/bin/git checkout conf-override
npm ERR! error: pathspec 'conf-override' did not match any file(s) known to git.
npm ERR!

I am getting the same both locally and on Travis.
 Nothing changes。

Hello! Same error here.

Looks like a dependency change that was supposed to be temporary leaked into the release, #540 fixes the problem.

Same error.

Oooops.  Sorry about that.  Fixed  by #540.


Script for bringing in Eureka Docker Image

Should we add a script for downloading the Eureka Docker Image. We could then write an integration test that does the registration, heartbeat, registration and deregister.

Yeah I wonder what that would look like. Do we assume they already have Docker and at least the default docker machine set up? Seems like we need something at least. I did add a wiki page for running Eureka server, for now.

Yeah I think it would be reasonable to have a gulp task that a task that downloads the image and starts it up. We could just update the README to get Docker setup and installed before using.

We can automate the docker setup in the travis build script: http://docs.travis-ci.com/user/docker/

We can do this now that I figured out what the problem was. We should run these tests after coveralls so that the coverage numbers only reflect the actual unit tests.
Successful startup and cURL request:
https://travis-ci.org/jquatier/eureka-js-client/jobs/106119219

Awesome!!!

Completed last week.


[Question] ApplicationDbContext as IDisposable Transient Service

Hello!
From src\Infrastructure\DependencyInjection.cs :
services.AddScoped<IDbContextFactory<ApplicationDbContext>, BlazorContextFactory<ApplicationDbContext>>();
services.AddTransient<IApplicationDbContext>(provider =>
    provider.GetRequiredService<IDbContextFactory<ApplicationDbContext>>().CreateDbContext());

Why you invoke CreateDbContext() directly within service registration? If my assumption is correct this call shall register ApplicationDbContext in DI and because ApplicationDbContext is IDisposable it's lifetime be lifetime of user circuit, if not created from custom scope. So you get new ApplicationDbContext on every mediator handler invocation and it not disposed until user connection is alive.
Can you clarify this?

I understand your concern. I have tried registering IApplicationDbContext with a Scoped lifetime, but I encountered issues because Blazor Server applications are different from MVC applications. Therefore, I can only use Transient registration.

Yes, Blazor server scope bound to user circuit but your solution solves this by spawning new DbContext on every mediator handler call and doesn't dispose them for as long as user connection is alive.
You could check this as solution:

https://github.com/dotnet/blazor-samples/tree/main/8.0/BlazorWebAppEFCore. Register DbContextFactory and inject IDbContextFactory directly in component. As you use mediator this seems not a good solution for you.
https://github.com/jbogard/MediatR/issues/607#issuecomment-1312616013. You can create wrapper around Mediator.Send with costume scope. This should work as scope disposed after every Send() invocation.

What do you think about this as drop-in replacement for Mediator?
using MediatR;

namespace Infrastructure.ScopedMediator;

public interface IScopedMediator : IMediator
{
}

using System.Runtime.CompilerServices;
using MediatR;

namespace Infrastructure.ScopedMediator;

public class ScopedMediator : IScopedMediator
{
    private readonly IServiceScopeFactory _scopeFactory;

    public ScopedMediator(IServiceScopeFactory scopeFactory)
    {
        _scopeFactory = scopeFactory;
    }

    public async Task<TResponse> Send<TResponse>(
        IRequest<TResponse> request,
        CancellationToken cancellationToken = default)
    {
        AsyncServiceScope scope = _scopeFactory.CreateAsyncScope();
        await using (scope.ConfigureAwait(false))
        {
            Mediator mediator = scope.ServiceProvider.GetRequiredService<Mediator>();

            TResponse response = await mediator.Send(request, cancellationToken);

            return response;
        }
    }

    public async Task Send<TRequest>(TRequest request, CancellationToken cancellationToken = default)
        where TRequest : IRequest
    {
        AsyncServiceScope scope = _scopeFactory.CreateAsyncScope();
        await using (scope.ConfigureAwait(false))
        {
            Mediator mediator = scope.ServiceProvider.GetRequiredService<Mediator>();

            await mediator.Send(request, cancellationToken);
        }
    }

    public async Task<object?> Send(object request, CancellationToken cancellationToken = default)
    {
        AsyncServiceScope scope = _scopeFactory.CreateAsyncScope();
        await using (scope.ConfigureAwait(false))
        {
            Mediator mediator = scope.ServiceProvider.GetRequiredService<Mediator>();

            object? response = await mediator.Send(request, cancellationToken);

            return response;
        }
    }

    public async Task Publish<TNotification>(
        TNotification notification,
        CancellationToken cancellationToken = default)
        where TNotification : INotification
    {
        AsyncServiceScope scope = _scopeFactory.CreateAsyncScope();
        await using (scope.ConfigureAwait(false))
        {
            Mediator mediator = scope.ServiceProvider.GetRequiredService<Mediator>();

            await mediator.Publish(notification, cancellationToken);
        }
    }

    public async Task Publish(object notification, CancellationToken cancellationToken = default)
    {
        AsyncServiceScope scope = _scopeFactory.CreateAsyncScope();
        await using (scope.ConfigureAwait(false))
        {
            Mediator mediator = scope.ServiceProvider.GetRequiredService<Mediator>();

            await mediator.Publish(notification, cancellationToken);
        }
    }

    public async IAsyncEnumerable<TResponse> CreateStream<TResponse>(
        IStreamRequest<TResponse> request,
        [EnumeratorCancellation]
        CancellationToken cancellationToken = default)
    {
        AsyncServiceScope scope = _scopeFactory.CreateAsyncScope();
        await using (scope.ConfigureAwait(false))
        {
            Mediator mediator = scope.ServiceProvider.GetRequiredService<Mediator>();

            IAsyncEnumerable<TResponse> items = mediator.CreateStream(request, cancellationToken);

            await foreach (TResponse item in items)
            {
                yield return item;
            }
        }
    }

    public async IAsyncEnumerable<object?> CreateStream(
        object request,
        [EnumeratorCancellation]
        CancellationToken cancellationToken = default)
    {
        AsyncServiceScope scope = _scopeFactory.CreateAsyncScope();
        await using (scope.ConfigureAwait(false))
        {
            Mediator mediator = scope.ServiceProvider.GetRequiredService<Mediator>();

            IAsyncEnumerable<object?> items = mediator.CreateStream(request, cancellationToken);

            await foreach (object? item in items)
            {
                yield return item;
            }
        }
    }
}

What do you think about this as drop-in replacement for Mediator?
using MediatR;

namespace Infrastructure.MediatorWrapper;

public interface IScopedMediator : IMediator
{
}

using System.Runtime.CompilerServices;
using MediatR;

namespace Infrastructure.MediatorWrapper;

public class ScopedMediator : IScopedMediator
{
    private readonly IServiceScopeFactory _scopeFactory;

    public ScopedMediator(IServiceScopeFactory scopeFactory)
    {
        _scopeFactory = scopeFactory;
    }

    public async Task<TResponse> Send<TResponse>(
        IRequest<TResponse> request,
        CancellationToken cancellationToken = default)
    {
        AsyncServiceScope scope = _scopeFactory.CreateAsyncScope();
        await using (scope.ConfigureAwait(false))
        {
            IMediator mediator = scope.ServiceProvider.GetRequiredService<IMediator>();

            TResponse response = await mediator.Send(request, cancellationToken);

            return response;
        }
    }

    public async Task Send<TRequest>(TRequest request, CancellationToken cancellationToken = default)
        where TRequest : IRequest
    {
        AsyncServiceScope scope = _scopeFactory.CreateAsyncScope();
        await using (scope.ConfigureAwait(false))
        {
            IMediator mediator = scope.ServiceProvider.GetRequiredService<IMediator>();

            await mediator.Send(request, cancellationToken);
        }
    }

    public async Task<object?> Send(object request, CancellationToken cancellationToken = default)
    {
        AsyncServiceScope scope = _scopeFactory.CreateAsyncScope();
        await using (scope.ConfigureAwait(false))
        {
            IMediator mediator = scope.ServiceProvider.GetRequiredService<IMediator>();

            object? response = await mediator.Send(request, cancellationToken);

            return response;
        }
    }

    public async Task Publish<TNotification>(
        TNotification notification,
        CancellationToken cancellationToken = default)
        where TNotification : INotification
    {
        AsyncServiceScope scope = _scopeFactory.CreateAsyncScope();
        await using (scope.ConfigureAwait(false))
        {
            IMediator mediator = scope.ServiceProvider.GetRequiredService<IMediator>();

            await mediator.Publish(notification, cancellationToken);
        }
    }

    public async Task Publish(object notification, CancellationToken cancellationToken = default)
    {
        AsyncServiceScope scope = _scopeFactory.CreateAsyncScope();
        await using (scope.ConfigureAwait(false))
        {
            IMediator mediator = scope.ServiceProvider.GetRequiredService<IMediator>();

            await mediator.Publish(notification, cancellationToken);
        }
    }

    public async IAsyncEnumerable<TResponse> CreateStream<TResponse>(
        IStreamRequest<TResponse> request,
        [EnumeratorCancellation]
        CancellationToken cancellationToken = default)
    {
        AsyncServiceScope scope = _scopeFactory.CreateAsyncScope();
        await using (scope.ConfigureAwait(false))
        {
            IMediator mediator = scope.ServiceProvider.GetRequiredService<IMediator>();

            IAsyncEnumerable<TResponse> items = mediator.CreateStream(request, cancellationToken);

            await foreach (TResponse item in items)
            {
                yield return item;
            }
        }
    }

    public async IAsyncEnumerable<object?> CreateStream(
        object request,
        [EnumeratorCancellation]
        CancellationToken cancellationToken = default)
    {
        AsyncServiceScope scope = _scopeFactory.CreateAsyncScope();
        await using (scope.ConfigureAwait(false))
        {
            IMediator mediator = scope.ServiceProvider.GetRequiredService<IMediator>();

            IAsyncEnumerable<object?> items = mediator.CreateStream(request, cancellationToken);

            await foreach (object? item in items)
            {
                yield return item;
            }
        }
    }
}

This definitely works very well. Thank you

done


Lint/Void maybe not working right in setter methods

Given the following file
# frozen_string_literal: true

# A comment
class Foo
  def some_setter=(val)
    @val = run_some_code_and_change_type(val)
    val
  end

  def run_some_code_and_change_type(val)
    val.to_s
  end
end

Expected behavior
There should be no Lint/Void error on val on the last line of the method #some_setter= since I'm using it as a return value (and also I've used in in a method call it to set @val)
Actual behavior
Inspecting 1 file
W

Offenses:

test.rb:7:5: W: Lint/Void: Variable val used in void context.
    val
    ^^^

1 file inspected, 1 offense detected, 1 offense auto-correctable

RuboCop version
$ rubocop -V
0.92.0 (using Parser <IP_ADDRESS>, rubocop-ast 0.7.0, running on ruby 2.6.6 x86_64-darwin19)

Not sure if it's strictly relevant, but I discovered this through standardrb
$ standardrb -v
0.7

and reported it there first: https://github.com/testdouble/standard/issues/206

Also notice that the output says it's auto-correctable. Trying to actually autocorrect it fails. Also every once in a while it wont say 1 offense auto-correctable, but it usually does, even if the file hasn't changed at all.

I think the offense is correct. Assignment methods should return the assigned value (for which they don't need explicit return as assignment will return it).
Assignment methods are explicitly marked as void context here.

Do they return the value that is assigned, or the value that is passed in? I can't think of places to check for precedent of methods that modify on the way in and return that modified value.

It normally does not matter what you return
obj = Object.new; def obj.foo=(_); 42;end
x = obj.foo = 666
x # => 666, not 42

The only way to get the result is to use send :foo= and use the result; nobody should do that.

The "1 offense auto-correctable" seems to be a bug though. Lint/Void doesn't even extend AutoCorrector, odd.

Can't reproduce the "1 offense auto-correctable" with 0.92.0 or master, so unless there's anything else, I'll close this, but we can reopen if there's something else.
Just to be clear, the correct code for your example should simply be:
# A comment
class Foo
  def some_setter=(val)
    @val = run_some_code_and_change_type(val)
  end

  def run_some_code_and_change_type(val)
    val.to_s
  end
end


Object classification of the output masks

In the FAQ, the model predicts object masks only and does not generate labels.
How can I obtain the class labels of the output masks?
Do I need to train a classifier?

Do I need to train a classifier?

Yes


TransactionDB + Transaction + Checkpoint

Would like to add transactions as available in rocksdb c

Checkpoint code looks good to me now :)

nice :)


Spelling error

http://expressjs.com/guide/routing.html
Under Route paths
"Route paths, in combination with a request method, define the endpoints at which requests can be made to. They be strings, string patterns, or regular expressions."
They could be strings, string patterns, or regular expressions. could is missing.

Fixed here - 64d9bb778a9a1256423d496a9177fc3d61bf39d2. Thanks for reporting!


chore: remove unnecessary sync

PR Type

Chore

Related Links

Description
Removed unnecessary sync files

Review Procedure

Remarks

Pre-Review Checklist for the PR Author
PR Author should check the checkboxes below when creating the PR.

[x] Code follows coding guidelines
[x] Assign PR to reviewer

Checklist for the PR Reviewer
Reviewers should check the checkboxes below before approval.

[ ] Commits are properly organized and messages are according to the guideline
[ ] Code follows coding guidelines
[ ] (Optional) Unit tests have been written for new behavior
[ ] PR title describes the changes

Post-Review Checklist for the PR Author
PR Author should check the checkboxes below before merging.

[ ] All open points are addressed and tracked via issues or tickets
[ ] Write release notes

CI Checks

Build and test for PR: Required to pass before the merge.
Check spelling: NOT required to pass before the merge. It is up to the reviewer(s). See here if you want to add some words to the spell check dictionary.

@kminoda We added the sync files for the launch/config unification task, which I think are not necessary anymore.
Could you review the PR?

@takayuki5168 Thank you :pray:


made numbers look prettier

instead of lets take for example the transparency being 0.49999999999999 it would turn to 0.5, 0.5781528 would turn into 0.57815 and 0.5781551 would turn into 0.57816 etc. you get what i mean at this point

im also open to any optimization requests with the code i changed


Added legacy_go_mod_version to gomodule

What does this PR do?
Following https://github.com/DataDog/datadog-agent/pull/30753 and https://github.com/DataDog/datadog-agent/pull/31073, added legacy attributes for agent 6 module files (context).
This will be used to load agent 6 modules from agent 7 files.
Motivation
Describe how to test/QA your changes
Possible Drawbacks / Trade-offs
Additional Notes

/merge


Publish uutils-term-grid to crates.io

Hi, thanks for keeping this going!
Over at eza we are pretty sure this solves some of our problems.
Could you publish this to crates.io?

I'll try to revive the PR I was working on that simplifies the code first. If that doesn't work out we'll push it as is. Glad you gave me a reason to look at this again :)
eza is looking nice, btw!


Kalk ought to strip line terminator when reading from standard input

# kalk thinks the line terminator is part of the expression
$ echo 2 | kalk
kalk
Type 'help' for instructions.
Invalid number literal: '2
'.
# let's try without the linefeed
$ echo -n 2 | kalk
kalk
Type 'help' for instructions.
2

Sorry, I forgot to tell: kalk 0.5.3

Thank you! This should now be fixed.


linux build broken?

After making a fresh new repo using the "use this template" button, the initial commit fails to build for linux. The issue is in the "Install JUCE's Linux Deps" section:
Get:1 file:/etc/apt/apt-mirrors.txt Mirrorlist [142 B]
Get:6 https://packages.microsoft.com/repos/azure-cli jammy InRelease [3596 B]
Hit:2 http://azure.archive.ubuntu.com/ubuntu jammy InRelease
Hit:7 https://packages.microsoft.com/ubuntu/22.04/prod jammy InRelease
Hit:3 http://azure.archive.ubuntu.com/ubuntu jammy-updates InRelease
Hit:4 http://azure.archive.ubuntu.com/ubuntu jammy-backports InRelease
Hit:5 http://azure.archive.ubuntu.com/ubuntu jammy-security InRelease
Fetched 3596 B in 1s (6367 B/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
Package libc6 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
  libdb1-compat libnss-nisplus libnss-nis libcrypt1

Package libc6-dev is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
  rpcsvc-proto libnsl-dev libcrypt-dev

E: Version '2.35-0ubuntu3.7' for 'libc6' was not found
E: Version '2.35-0ubuntu3.7' for 'libc6-dev' was not found
Error: Process completed with exit code 100.

I seem to recall this working just last week, not sure what changed since then?

Heh, working on it right now here: #100

Linux has been a sort of disaster over time, things should start to be more stable once that PR merges.


fix: removed flickering effect in navbar for small devices

Description
The navbar is now opening smoothly without causing any visual flicker to the logo or other elements.
Before:-
https://github.com/asyncapi/website/assets/115611556/0029f1a0-6761-4f6f-a1e3-d157c7ec5ce3
After:-
https://github.com/asyncapi/website/assets/115611556/db0704c9-5d90-4d55-991b-34f4ba39d885
Related issue(s)
#3013

@sambhavgupta0705 Please re-check this, as one test case was failing before so it's refreshed again

/rtm


possible bug in http::read method

PLEASE DON'T FORGET TO "STAR" THIS REPOSITORY :)
If you rather keep your project secret, feel free
to email the author at<EMAIL_ADDRESS>any
private correspondence is treated as confidential.
When reporting a bug please include the following:
Version of Beast
1.71
Steps necessary to reproduce the problem
Unfortunately this happens relatively rarely and very hard to reproduce.
I am running on linux 18.04 compiled with gcc7.
I have an instance of parser of type h2::response_parser<h2::buffer_body>
and I call beast::http::read(*client_, tmp_buffer_, parser, ec);
to read from a client socket. my buffer_body.size is 4096 bytes.
Expected: to get "body.size=0" if parser is not done and the status is error::partial_message. (I am assuming that read() differs from read_some() by guaranteeing to fill up the body if possible) - please tell me if I am wrong.
Actual:  parser is not done and the status is error::partial_message and buffer_body.size is some positive number.
Please note that sometimes the same response is parsed correctly, the behavior depends on how data flows on the socket and it requires gigabytes of data to trigger this condition.

You have to use read_some. See: https://www.boost.org/doc/libs/1_71_0/libs/beast/doc/html/beast/ref/boost__beast__http__read/overload1.html

I do not understand. What's the difference between read_some and read ?

read assumes that it will see the entire message, which is not possible with buffer_body.

It's a bug in my socket code, sorry for false alarm


Update production to 1.11 build 235 a32731d

Update production to 1.11 build 235 a32731d

Deploy Link - https://deploy-preview-1563--tc-create-app.netlify.app/


Remove idt and uninstaller. Add ic shortcut for "ibmcloud"

Tested on MacOS, Ubuntu, Centos, Debian, and Windows.


Bug/fix concurrent use of xmlschemaset

XmlSchemaSet should not be shared among multiple threads for validation, as otherwise validation might fail.
Reproduced by having multiple concurrent request call RequestTransactionStatus and see that some of them fail with validation error.

So surprising that it is not safe for read-only access but apparently it is. It can be potentially very slow to load schemas. Do you know how long it takes? If it is too long, we can consider to cache schemas in thread-local storage.

Apparently this happens when XmlSchemaSet is compiled, which modifies it.
Seems it gets compiled during validation, unless it's already compiled. So we might in theory pre-compile it (XmlSchemaSet.Compile()), but don't think we should rely on this behaviour.
The loading takes about 7 ms.

The loading takes about 7 ms

Loading + First validation = 7 ms?
Looks fine, I guess, to not bother with performance optimization.

yes, it's usually within 7 ms (or even much less). Unless right after the startup (27 ms) or in case of concurrent requests (17 ms).

On second thoughts, I ran a few tests by re-using pre-compiled XmlSchemaSet (by invoking Compile) and could not see any errors.
So will close this PR in favour of this one: https://github.com/ckolabs/ing-ideal-connectors-net/pull/11/ - will re-open in case errors occur in the future


Remove redundancy in OWNERS

There is no need to have the same owners both under reviewers and
approvers. Approvers always takes the precedence over reviewers.

/approve

/approve

/lgtm


drivers/devicetree/fdt: get 'reg' property

Summary
drivers/devicetree/fdt: get 'reg' property
Original code can only deal with single 'address & size' cell
Add function dealing with multiple 'address & size' cell
Add function getting 'bankwidth' property, for cfi-flash device

devicetree/fdt: fix fdt_get_reg_size() get wrong size
Impact
fdt, new API
Testing
vela qemu

[Experimental Bot, please feedback here]
Let's break down this PR against the NuttX requirements:
Meets Requirements?
Likely NO, but it needs more information.
Here's Why and What's Missing:

Summary:

Good: It clearly states the change (handling multiple 'address & size' cells in device trees).
Missing:

Necessity: Why was this change necessary? Was the existing code broken? Did a new device driver need this functionality?
Functional Part: Be more specific.  Is this in the device driver framework? The device tree parser itself?
Issue References: Are there any related issues in the NuttX or NuttX Apps repositories? This helps with tracking and context.

Impact:

Too Vague:  "fdt, new API" doesn't tell us enough.
Needs Details:

New Feature:  Since it's a new API, this is likely YES. Briefly explain what the new API allows developers to do.
User Impact: Will users of the device tree framework need to modify their code? If so, how?
Hardware Impact: Are there specific architectures or boards affected?
Documentation: Does this new API need to be documented?  If so, has documentation been added/updated in the PR?
Consider:  Think about potential side effects.  Could this change break existing drivers that rely on the old behavior?

Testing:

Insufficient: "vela qemu" is not enough detail.
Provide:

Build Host Details:  Which OS, compiler, and versions were used for testing?
Target Details: Be specific about the QEMU architecture and board configuration you tested with.
Logs (Important!):

Before Change: Show logs demonstrating the issue or limitation the PR addresses.
After Change: Show logs demonstrating the issue is resolved or the new functionality works.

How to Improve the PR:

Expand the Summary: Explain the "why" and provide context.
Detailed Impact Assessment: Go through each impact point with specifics.
Thorough Testing Information:  Provide build details, target details, and the essential before/after logs.

By addressing these points, your PR will be much stronger and easier for the NuttX maintainers to review and merge.


Feature/SWP-1918 - Extracting the reviews service from installs tool

This is the reviews service extracted. Started by Adrien and completed by me.
This package covers the following.

Reviews.co.uk logic for getting reviews and sending invites through reviews.co.uk
Tests for the code (And Travis config)
Readme Documentation
A Dockerfile along with a Makefile to help with local development.

Please read the following -> https://podpoint.atlassian.net/browse/SWP-1918

In terms of using our own image as a posed to a public one is just having a consistent environment in which we develop and run our code. Like some of the things inside of our image are not going to be used directly in this package but there isn't much setup speed different in using a public one just that our url is there.


Fix OSCO-to-OSCAL transformation bug

Describe the bug
The produced OSCAL has small properties issues.

target should not be part of relevant-evidence properties
subject should have target-ip and each property should have namespace and class
observation should have benchmark if specified in metadata

To Reproduce
See tests/data/tasks/osco/output/ssg-ocp4-ds-cis-111.222.333.444-pod.json for example relevant-evidence's containing "target" property.
Expected behavior

target should be removed from relevant-evidence
target-ip should be added to subject
subject properties should have namespace and class
if benchmark in metadata, observation should have benchmark property

Screenshots
bad:

good:

Desktop (please complete the following information):
N/A
Smartphone (please complete the following information):
N/A
Additional context
N/A

Fixed by #398.


Grant access button is not shown at the Your contact code area

No Grant access button is shown. User is not asked for permissions for the dapp

Mentioned in this issue - https://github.com/status-im/ens-usernames/issues/38


chore(main): release 1.26.42

:robot: I have created a release beep boop
1.26.42 (2024-01-24)
Bug Fixes

use class to locate frame (#225) (0154e04)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/aidanaden/canvas-sync/releases/tag/v1.26.42 :sunflower:


endpoint: move patching update functionality to pkg/endpoint

A lot of Endpoint implementation information, including locking, internal fields, etc. was being leaked outside of the Endpoint package in the handling of PATCH /endpoint. Factor this into a function within the Endpoint package instead. As a result of this, the function ForcePolicyCompute is no longer used outside of pkg/endpoint, so do not export it.
Signed-off by: Ian Vernon<EMAIL_ADDRESS>

This change is

test-me-please

Coverage decreased (-0.03%) to 44.123% when pulling 0997b90fb78a9db51a8a854def53edda78c421d0 on pr/ianvernon/patch-refactor into 42229305fd2e24cf6ece5e9411539341f23852ff on master.

Build failure: https://github.com/cilium/cilium/pull/8968
Node lost?

Build failure: https://github.com/cilium/cilium/pull/8968
Node lost?

test-me-please

Istio pods didn't get ready in time: https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-Validated/14523/testReport/junit/Suite-k8s-1/15/K8sIstioTest_Istio_Bookinfo_Demo_Tests_bookinfo_inter_service_connectivity/

test-me-please

test-me-please

Build failure: https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-Validated/14554/

test-me-please

Had to resolve conflicts, testing again

test-me-please

Running tests again, Cilium operator is taking forever to get ready:
10:45:41  STEP: Waiting for cilium-operator to be ready
10:49:09  STEP: Waiting for kube-dns to be ready

test-me-please

Failure is BPF NodePort with VXLAN: https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-Validated/14596/testReport/junit/Suite-k8s-1/10/K8sServicesTest_Checks_service_across_nodes_Tests_NodePort_BPF_Tests_with_vxlan/
Unrelated to these changes - this has been flaky in master. Merging.


xournal: Support gtk with quartz or x11 backend

Motivation for this change
Allows to use gtk2 with either quartz or x11 backend to build xournal on darwin.
Things done

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

[ ] NixOS
[x] macOS
[ ] Linux

[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Fits CONTRIBUTING.md.

Note that the binaries suffer from #12346
interim this does workaround it:
DYLD_FRAMEWORK_PATH=/System/Library/Frameworks ./result/bin/xournal


Mark empty listings for optional hiding

Fix https://github.com/plone/volto/issues/4393
This does not modify the markup except that it adds a CSS class.

Any objection?

Despite ready, I would close this PR satisfied, with https://github.com/plone/volto/pull/3602 having an option to hide a "no result" listing at all, including the heading.

@ksuess can we merge both https://github.com/plone/volto/pull/3602 and this one?
/cc @erral @ionlizarazu

Closed in favor of https://github.com/plone/volto/pull/4474


CMS 5 compatability

Note there aren't really any useful tests in this module but that's out of scope for this PR. I've created a separate card for that concern: https://github.com/silverstripe/silverstripe-dynamodb/issues/47
For now, manually test this with a local dynamodb install (or docker image) and use the AWS CLI to confirm that the sessions table gets updated as expected.
Don't squash
Each commit here is its own concern (albeit related to the overall purpose of making this module CMS 5 compatible) - we should keep the commit history readable by keeping all of these commits.
CI Run
Because this is the first time github actions are being added to this module, they won't run on this PR (because they're not in the default branch yet).
See the CI run on creative-commoners.
AFTER MERGING
After you merge this, create a new 5.0 branch off the 5 branch, and tag 5.0.0-beta1!
Parent issue

https://github.com/silverstripe/silverstripe-dynamodb/issues/45

Note there aren't really any useful tests in this module but that's out of scope for this PR. I've created a separate card for that concern: https://github.com/silverstripe/silverstripe-dynamodb/issues/47
For now, manually test this with a local dynamodb install (or docker image) and use the AWS CLI to confirm that the sessions table gets updated as expected.

Tagged as 5.0.0-beta1


Limit bash completion to current scope

This commit limits the bash completion output
to the current scope.
Fixes #926
Signed-off-by: Dominik Schulz<EMAIL_ADDRESS>

Thanks for testing. I'll fix the tests, than merge.


Tidy up the glossary javadoc in the Subject area java API

The subject area omas java api javadoc should use html tags to format the text more elegantly.

I would like this kept open


Missing data handling in boolean processes

I've already brought this up in the devtelco a while ago and I said I would summarise the problem in a github issue, but was interrupted due to being on sick leave for a while - so here it goes:

Summary of the problem
The logic processes as defined by OpenEO can return True/False/null.

This is fine in R, because the NA value is deeply integrated throughout the language
According to @jdries here it's fine in geotrellis, because there's missing data values for all dtypes

However, in numpy there is no sentinel value for missing data in boolean arrays (like there is with NaN for float). See this blog for a good overview to missing data handling. Also see NEP-26 for the state of this issue in the python community.
To implement and as specified, instead of this:
# Example A: What you'd expect from an implementation for a logical `and` process

logical_and = np.logical_and(x, y)

we have to do this:
# Example B: Workaround we have to use to account for null values are returned by logic processes

nan_x = np.isnan(x)
nan_y = np.isnan(y)
xy = np.logical_and(x, y)
nan_mask = np.logical_and(nan_x, xy)
xy = np.where(~nan_mask, xy, np.nan)
nan_mask = np.logical_and(nan_y, xy)
xy = np.where(~nan_mask, xy, np.nan)
return xy

Note that the output array of Example A has the dtype bool_, whereas the output array of Example B has dtype float64. This is because the missing data value np.nan is only defined for dtype float64 and thus the entire array needs to be upcast to float64.
See these numpy snippets to confirm this:
>>> np.array([True, False])
array([ True, False], dtype='bool')  # boolean array
>>> np.array([True, False]).itemsize
1  # one byte per item

>>> np.array([True, False, np.nan])
array([ 1., 0., nan], dtype='float64')  # casts to float64
>>> np.array([True, False, np.nan]).itemsize
8

Apart from looking really awkward, this also has direct performance implications, as the memory footprint of this array is multiplied by 8 and operations with float64 arrays will also be slower than on pure boolean arrays.
Here's a list of all processes where we've found this to be problematic:

and/not/or/xor
any/all
eq/neq
between
gt/gte/lt/lte
text_begins/text_contains/text_ends

Sorry for the wall of text here, but I'm extremely reluctant to deploy an 8-line implementation of a boolean primitive function that should be 1 line, where it's already clear that it causes a clear performance problem.
Proposed solutions:
We cannot use numpy masked arrays to do this, because numpy ufuncs that are applied to an ndarray cannot transform their parent to a masked array. We don't want to transform all parent ndarrays to masked arrays preemptively for performance reasons.
Therefore I'd propose the following:

The processes should not implicitly assume that nodata is supported for all datatypes.
Boolean functions should return True or False, anything else isn't a boolean function. Nodata can be treated as false. On a sidenote, this is already what the if process does according to example 2.

Looking forward to hear what people think about this!
For reference, this is the PR in which I first raised these issues:
https://github.com/Open-EO/openeo-processes-dask/pull/40
cc @ValentinaHutter @danielFlemstrom @clausmichele

The changes required here would be relatively huge across a lot of processes, not only the boolean ones.
As such we need more evidence that this is not just a numpy limitation that may eventually go away, e.g. how is it handled in other implementations (e.g. WCPS, GrassGIS, Java, Scala, Julia, JS, rust, ...). Right now it seems we have:
Supported: R, geopyspark
Not supported: numpy
PS: What's the conclusion from the NEP? Will missing data eventually land in Python or not? @LukeWeidenwalker

The numpy implementation is based on C, so I doubt the behaviour will change. I found an interesting discussion on this topic here: https://github.com/numpy/numpy/issues/2316
Anyway @LukeWeidenwalker, even if the Python code needs more lines of code to the same as R or geopyspark, this doesn't mean it will be slower or take more memory, since probably they also do the same under the hood.

Anyway @LukeWeidenwalker, even if the Python code needs more lines of code to do the same as R or geopyspark, this doesn't mean it will be slower or require more memory, since probably they also do the same under the hood.

No, it definitely does mean that, memory is allocated depending on the dtype.
You can check this by firing up a clean python container with numpy, run the following examples and monitor what happens to your container memory with docker stats:
a = np.arange(0, 10e7, dtype=np.int8)
print(a.shape)
print(a)
# This takes up about 90 MB

a = np.arange(0, 10e7, dtype=np.int64)
print(a.shape)
print(a)
# This takes about 800 MB

a = np.full(10e7, True)
print(a.shape)
print(a)
# This takes about 90 MB

the int8 and bool arrays take exactly the same amount of memory (because both dtypes take 8 bytes), while the int64 array takes 8 times as much. The only difference is the dtype.

Yes I do not doubt that different data types have different memory footprints.
What I mean is: could it be that other programming languages are also doing an intermediate step converting between types implicitly? Personally I don't know.

maybe I'm misunderstanding, but you seem to suggest that the problem is with the process definitions, but isn't the problem related to the input data itself?
# Example A
logical_and = np.logical_and(x, y)

if x and y are "boolean" arrays (e.g. dtype int8), there is no NaN in play anyway as there is no standardized representation for it, so nothing to worry about for the implementation of logical and.
if x and y are NaN-aware that implies that they already have dtype like float64, so again there is no need for conversion. The implementation is indeed uglier probably (ex B), but at least there is no conversion penalty.

Anyway @LukeWeidenwalker, even if the Python code needs more lines of code to do the same as R or geopyspark, this doesn't mean it will be slower or require more memory, since probably they also do the same under the hood.

Oh, apologies @clausmichele - you meant that it doesn't mean that it is comparatively slower than R or geopyspark, because these might have to do similar conversions under the hood? Yes, totally agree with that!

@m-mohr

PS: What's the conclusion from the NEP? Will missing data eventually land in Python or not? @LukeWeidenwalker

The conclusion is that this NEP is 11 years old and nothing has happened yet, and I was unable to identify any currently active efforts to resolve this. So I think the probability of this problem "going away" anytime soon is rather small.

The changes required here would be relatively huge across a lot of processes, not only the boolean ones (e.g. https://github.com/Open-EO/openeo-processes/issues/408).
As such we need more evidence that this is not just a numpy limitation that may eventually go away, e.g. how is it handled in other implementations (e.g. WCPS, GrassGIS, Java, Scala, Julia, JS, rust, ...). Right now it seems we have:
Supported: R, geopyspark
Not supported: numpy

I get where you're coming from with this comment, but I don't think that this is the right angle to approach this from in the first place. We don't have the relevant expertise across all these tech stacks, and even if we did, I really don't think this is necessary to meaningfully resolve this question.
Three arguments for why:

Numpy is not fringe: I don't think it's a stretch to claim that numpy is one of the most (perhaps even the most) widely used reference implementation of ndarrays for scientific computing even across ecosystems. If this is not in numpy, that's already strong evidence that missing values for any datatype (especially booleans) isn't a feature that you can just expect to be supported in any given ndarray library.

Note: This argument could be refuted by someone with deep understanding of numpy internals saying "No, this is just numpy being bad in this regard for legacy reasons".

Performance: We can also look at this from a theoretical perspective (again, see this blog for a summary). How would you implement a representation of missing values in arrays from primitive datatypes? You can either designate a sentinel value, i.e. a specific bit pattern (e.g. -9999, np.nan), to signify that a value is missing. Afaict this doesn't make sense for booleans (because which bitpattern would you use?) and might just not be implemented in a given stack. The second option is to build a mask over the original array that keeps track of which elements were missing. This must have worse performance characteristics than working with the raw arrays, because the mask both takes up memory and needs to be checked against when doing computations. So allowing missing values for any datatype

Note: This argument could be refuted by someone pointing out that I misunderstand how this works under the hood.

Is this even useful? What does it even mean for my boolean function to return anything other than True or False? I (and everyone I've spoken to about it) totally did not expect this behaviour when learning about it. I assume that the main usage pattern of these functions is to create masks. I can't think of a case where I'd want to have a mask where some values are undefined. I want my mask to say for every pixel whether it's in our out. The other usage pattern is using these processes in the if process. In if, nodata is treated as false, so this information is ignored again anyways.

Note: This argument could be refuted by providing a real-life example of a usage pattern I haven't considered.

maybe I'm misunderstanding, but you seem to suggest that the problem is with the process definitions, but isn't the problem related to the input data itself?
# Example A
logical_and = np.logical_and(x, y)

if x and y are "boolean" arrays (e.g. dtype int8), there is no NaN in play anyway as there is no standardized representation for it, so nothing to worry about for the implementation of logical and.
if x and y are NaN-aware that implies that they already have dtype like float64, so again there is no need for conversion. The implementation is indeed uglier probably (ex B), but at least there is no conversion penalty.

Fair point, but I think that's only true for the narrow example of logical_and. Something like gt is always able to produce a boolean array with missing values, so will cause the upcasting directly.


Add Mutex to protect certs/keys of Istio CA.

When Istio CA interacts with upstream CAs to renew its key/cert, it needs to have a mutex to protect the R/W accesses to the key/cert.

/test all

/retest


ModuleNotFoundError: No module named 'pyaf.ForecastEngine'

Hi,
Im encountering module not found error when running the demo python script. I imported the git through:
!pip3 install --upgrade git+https://github.com/antoinecarme/pyaf.git
When I tried looking at the submodules inside the module through git, this is what was returned:
from github_com.antoinecarme import pyaf
def sort_by_type(t):
return t[0].name
attrs = [(type(getattr(pyaf, attr)), attr) for attr in dir(pyaf)]
attrs.sort(key=sort_by_type)
for t, n in attrs:
print(t, n)
<class '_frozen_importlib.ModuleSpec'> spec
<class 'NoneType'> doc
<class '_frozen_importlib_external.SourceFileLoader'> loader
<class 'dict'> builtins
<class 'list'> path
<class 'str'> cached
<class 'str'> file
<class 'str'> name
<class 'str'> package
I also tried installing through pip but to no use

I also tried answers from #123 but to no use

Please use this instead:
from github_com.antoinecarme import pyaf
def sort_by_type(t):
return t[0].name
attrs = [(type(getattr(pyaf, attr)), attr) for attr in dir(pyaf)]
attrs.sort(key=sort_by_type)
for t, n in attrs:
print(t, n)

@eoagustin
Thanks for using PyAF.
I do not understand why you use :
from github_com.antoinecarme import pyaf

Isn't a simple
import pyaf

enough ?

Hello. Yes I was able to import it successfully. However, I encountered another issue and I dont know if I should post it here and edit the issue title and description instead.
Anyway, issue is that my subprocess.Popen was not able to find my dot.exe from graphviz. Im using cloudera data science workbench. I installed graphviz through conda (local) since its not permitted in our group to use sudo apt install graphviz (which was mentioned as solution in other issues in this git). I located the directory of the dot.exe in my local and added it in my os.environ("PATH") so that I can use it in cds workbench. However, it wasnt able to find the executable in the said path.
pydot==1.4.1
graphviz==0.15
pyaf==2.0.1
Python 2.7.18

Nice to see that you are able to import pyaf.
The issue you describe is related with the way you installed pydot/graphzviz. The great guys at pydot are probably better for getting more help on this.
https://github.com/pydot/pydot


[#2598] Fix: Fix HDFS IP resolution for Docker Desktop

What changes were proposed in this pull request?
Fix HDFS client IP address resolution when using Docker Desktop. Originally it may resolve to invalid domain name causing error.
Why are the changes needed?
Fix: #2598
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Existing tests.

@diqiu50 Hi, could you help take a look when you have time? Thank you!


How does one update the version?

pip3 install starepandas --upgrade

or a specific version
pip3 install starepandas=0.5.10


Support Bond IDL mapping to C# nested classes

I currently have some C# classes that I'm attempting to modify for use with Bond.
Some of these classes are nested, e.g.:
public class BunchOfClasses {
       public class SerializableSubclass {
           public int numberField;
           public void DoStuff() {
             //things
           }
      }
}

It would be useful to me to allow creation of Bond IDL that will generate
public partial class BunchOfClasses{
       public partial class SerializableSubClass {
               public int numberField; //Or as properties, or any of the other IDL field generating options
       }
}

then all I have to do to for the conversion is delete the old field and put partial modifiers on the classes. Currently there doesn't seem to be a way of describing nested classes so the only options are manual code generation instead of the IDL or extracting my nested classes out of their parent class. It's possible I may pull the nested classes from their parent anyway, but this seems like an issue people will eventually run into.

Do your inner classes access internal/protected/private members of BunchOfClasses? (e.g., you pass an instance of BunchOfClasses to the nested instances when you construct them) If not, then I'd try converting to nested namespaces. That might be an easier path forward. If they do access private things, converting to namespace won't help.
That being said, I don't think that supporting structs defined inside of structs in a good long term direction. Not all of the languages we're looking at targeting in the future support defining structs/classes/objects inside of one another.
Thoughts?

As I mentioned above, it's possible for my case that pulling the classes into a separate namespace + a little refactoring will be enough to make this work. I definitely agree that having language specific features in the IDL is not great.
Perhaps a way to do this is basically by giving the language specific code generators more flags. For example, if I could name my IDL struct BunchOfClasses.SerializableSubClass then I could flag the c# generator to do what I mentioned above. However, for another language BunchOfClasses.SerializableSubClass could be interpreted as BunchOfClassesSerializableSubClass or BunchOfClasses or SerializableSubClass.
There are likely better ways to do this then I've suggested, and perhaps this feature is a little too language specific to be generally useful, but for those that have a harder time extracting nested classes into new namespaces it might be worthwhile.

We're planning to start a large push on more robust target-language specific settings. I'm going to park this issue for now, and see whether something falls out of the forthcoming design work. Thanks for the ideas.

Sounds good, if I come across other issues like this in my code conversion I'll post them so you guys have that info available.


feature(clean-up): proper handling of non-contained elements on model and storage level

Non-contained elements on model level are represented in consistently.
Suggestion:
{   "name": "StudyNC",   "type": "CORE:Blueprint",   "extends": ["CORE:NamedEntity"],   "description": "",   "attributes": [     {       "name": "special",       "label": "Special Case",       "type": "CORE:BlueprintAttribute",       "attributeType": "./Case",       "contained": false     },     {       "name": "cases",       "label": "Cases",       "type": "CORE:BlueprintAttribute",       "attributeType": "./Case",       "dimensions": "*",       "contained": false     }   ] }
Above Blueprint suggests that StudyNC has a non-contained list of Case. Then the entity studyNC should look like this.
{   "name": "studyNC",   "type": "AppModels:StudyNC",   "description": "",   "special": {         "type": "CORE:Reference",         "ref_id": 'AppStorage:{2d0dd4a4-0429-4310-ad00-8a33c4039800}.cases[0,1].content'    }   ] }
other examples of reference,
"ref_id": 'dmss://AppStorage/instances/study.cases[5].content'
"ref_id": 'AppStorage/instances/study.cases[5].content'
Requires further discussions.

Rental Company
  -> Cars[] (contained)
  -> Customers (contained)

Customer
  -> Car (not contained)

myCompany
  cars: [{car0},{car1},{car2}]
  customers: [{customer1}]

customer1
   car:
      type: CORE:Reference
      id: ...myCompany.cars.2
      type: SomeBlueprint

Expected behavior (acceptance criteria)

Do not resolve non-contained attributes

What does non-contained on the model level means?

If an attribute is non-contained on the model level it means that the entity does not own it (it points to it), then it does not make sense to have it contained on a storage level.

Example 1: Want to reference the same object
(company id)
{id}.cars.0.platenumber

Example 2: Want to be able to replace the engine
{id}.engine.power

Any complex object can have an id.
Should all objects that should be referenced directly be storage non-contained?

Reference is of type Simos/Reference
ref: str
PathReference extends Reference
some of the path
QueryReference  extends Reference
query string
IdReference extends Reference
protocol/ds/id
Reference is of type Simos/Reference
ref: AbsolutePathReference | RelativePathReference | QueryReference |  IdReference
what about dmss+query://?

@eoaksnes I think we need to have another round of discussion on this.
It seems we remember differently what we concluded for references.
I am not sure which one is best right now either, but I am sure we need an easy way to understand we need to treat a string attribute as a reference.


Dead example link

@sgratzl

When I click on the codepen badge, it says 404: https://codepen.io/sgratzl/pen/TODO
There's a TODO in the link.  Maybe the demo exists but it's just not in the readme?
To Reproduce

Click https://codepen.io/sgratzl/pen/TODO

Expected behavior
I expect it to open a demo of the pictured graph in the readme.

Screenshots

N/A
Context

Version: N/A
Browser: N/A

Additional context

Thanks!

I never had the time to write one, here you go https://codepen.io/sgratzl/pen/RwQdBLY
see also https://github.com/upsetjs/cytoscape.js-bubblesets/tree/main/samples

The demo looks great.  Could you update the link in the readme?  It's still dead for me
Maybe the codepen badge could also be at the top of the readme with the other badges?  I think a lot of people would want to access the demo, and the top of the readme is the most seen place