@deanrp2 I won't revert the change since it is correct, but I realized that the output for the problems with grid type is not converted from integer back to how its original value in the grid space. This is needed for reporting. You still need to apply the function  decode_discrete_to_grid before reporting the final results. Please see in gwo.py lines 315-345 how this conversion occurs. Given AEO is not using a new fitness function, then there is no need to apply similar lines as 123-125 in GWO. When testing with the example, make sure that the output found by AEO for the input parameters with grid type belongs to how the grid was defined. Thanks!

Problem with discrete testing: Originally posted by @mradaideh in https://github.com/mradaideh/neorl/issues/31#issuecomment-1097499561

Closed, will submit issue as new pull request.


UI labels same color as background under MacOS

I've seen this bug under MacOS only so far. It could be related to Qt bugs 73897 / 71020 which have been reported for macOS 10.14 with Dark Theme and Qt 5.12.
https://bugreports.qt.io/plugins/servlet/mobile#issue/QTBUG-73897
https://bugreports.qt.io/browse/QTBUG-71020
Please confirm / disagree, I have no access to a MacOS computer.

Could not be reproduced

This is still an issue here. Mac OS Sonoma 14.6.1., latest pyfda.
A screenshot of pyfdax in regular/light mode:

A screenshot of pyfdax when the system is in dark mode:

If you need testing for a fix, I'd be happy to do so, and use light theme while using pyfda in the meantime.

Could you please check whether pyfda 0.9.1 has fixed the problem? You should get a dark mode by setting THEME = 'dark'  in your pyfda.conf file.

Yes! Light mode is perfectly legible and dark mode is looking really good! Thank you for the fix!


Update hardF5.sh

Adding HSTS to default HTTP profile can cause problems with IAPP deployments.

I will look into it, thanks.


feat(retention): added image retention policies

feat(metaDB): add more image statistics info

What type of PR is this?

Which issue does this PR fix:
What does this PR do / Why do we need it:
If an issue # is not available please add repro steps and logs showing the issue:
Testing done on this change:

Automation added to e2e:

Will this break upgrades or downgrades?
Does this PR introduce any user-facing change?:

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Also call this "feat(retention)"

sync policies (are per-repo, regex, semver, etc) are a good fit here IMO. Thoughts?

You have dryRun as an all-or-nothing for all policies, IIUC.  It seems to me I might want to say "all image produced by pull requests (as signified by a CI-XXX tag) are deleted (dryRun: false) after 5 days.  But for any unknown namespaces, simply report (dryRun: true), because someone may have pushed a new namespace which I don't know about yet."  This would send me notification of unhandled namespaces, which simply having the catch-all be to not delete would not do.
Maybe that's too much complication, though.  Just a thought.

One problem I see here - which admins should at least be warned about - is, IIUC, if I start with expiration rules set, then run for a week without expiration rules set, then re-enable them, the Metadb will not have been used during that week, and images pushed in the meantime will not have pushed/pulled times set.  Am I right about that?  That could lead to very wrong behavior (from admin's POV).

You have dryRun as an all-or-nothing for all policies, IIUC. It seems to me I might want to say "all image produced by pull requests (as signified by a CI-XXX tag) are deleted (dryRun: false) after 5 days. But for any unknown namespaces, simply report (dryRun: true), because someone may have pushed a new namespace which I don't know about yet." This would send me notification of unhandled namespaces, which simply having the catch-all be to not delete would not do.
Maybe that's too much complication, though. Just a thought.

Would be nice, but it's not clear what the definition of unknown namespace is.
If I start a zot server with empty rootDir, all namespaces are unknown, until I restart zot?
when do I switch from "unknown namespace" to "old namespace".

Thanks - feature-wise looks good to me.

Pls resolve the conflicts and push again

cc: @mbshields this needs documentation as well

Good interface, nice options for any case - great job, thanks! I will build and test it for sure, I need this!
I have one suggestion, I need it and I think it will be nice option too! I don't know how to name it exactly, let it be "dynamic tags":
Imagine tags like environment-{1,2,..}-* and I want to keep 2 latest for each environment (1, 2, etc), so I must write rules for each environment, but it's a dynamic thing, and there are many of them, I suggest to simplify it somehow.
So many groups of tags and single rule for each group, something like regex capture group (maybe named) I think the best solution cause our group value must be in any matched tag and we should extract&compare it for each tag, and it's also very "flat":
names: [(environment-\d+)-.*]

.., so for each matched tag we should compare $1 and interpret tags with same group as unique list/rule and do the things.
Maybe you imagine better interface, but I really think it's cool feature, and it will be very unique feature!

Update after first testing:

Please update main from upstream to pull changes about "delete repositories without manifests", now in your fork repositories are left after policies delete all tags.

Help me understand what is deleteReferrers, how it works? Also deleteUntagged about unfinished blobs, when it's uploaded, but not tagged (canceled push for ex.)?

I'm right that if some tags matched to rule, than only this rule defines who will be retained and this tags can't be now affected by rules below?

        {
          "repositories": ["**"],
          "deleteUntagged": true,
          "deleteReferrers": true,
          "keepTags": [{
            "patterns": ["main$"]
          },{
            "patterns": ["main"],
            "mostRecentlyPushedCount": 3
          },{
            "pushedWithin": "72h",
            "pulledWithin": "720h"
          }]
        }

For ex. here for tags like: main (meta-tag, always points to the last build of this branch), main.1, main.2, branch-foo (meta), branch-foo.13 I want:

main meta-tag always presented
3 latest build from main branch not counting main meta-tag, cause it already matched by rule above
for builds from other branches and it will not affect any main builds cause all of them already matched by above rules

So the main point that this rules will not preserve main builds for 3 days how builds from other branches and will keep only 3 latest how it says, right? Then it's great implementation, thank you very much!
Also about above feature dynamic tags, in real world for complete retention I need something like this:
        {
          "repositories": ["**"],
          "deleteUntagged": true,
          "deleteReferrers": true,
          "keepTags": [{
            "patterns": ["main$"]
          },{
            "patterns": ["main\\..+"],
            "mostRecentlyPushedCount": 8
          },{
            "patterns": ["environments-[a-z]+$"]
          },{
            "patterns": ["(environments-[a-z]+)\\..+"],
            "mostRecentlyPushedCount": 1
          },{
            "pushedWithin": "72h",
            "pulledWithin": "720h"
          }]
        }

Everything like above, but also keep meta-tag for any environment and 1 latest build for each, and also, as for main, not match them by last rule (so not delay deletion for 72h).
In general, everything looks working, I use build of fork with retention for 2 days in my main zot installation, also seems that all works as I described in 3, and so as I said - it's great!

And also, I see there is a no difference between "patterns": ["main", "master"] and "patterns": ["(main|master)"], so it generates a single list to which the rule applies (pushedCount for example). I think it will be great if each pattern will generate personal list and when we write like "patterns": ["main", "master"] then we just want apply the single rule, but for each match, they are not the same, and my dynamic tags in this case will just automatic propagation of the patterns, when single "patterns": ["(environment-[a-z]+)\\..+"] will be processed (based on existing tags) as "patterns": ["(environment-foo\\..+", "(environment-bar\\..+", "(environment-baz\\..+"].

Update after first testing:

Please update main from upstream to pull changes about "delete repositories without manifests", now in your fork repositories are left after policies delete all tags.
Help me understand what is deleteReferrers, how it works? Also deleteUntagged about unfinished blobs, when it's uploaded, but not tagged (canceled push for ex.)?
I'm right that if some tags matched to rule, than only this rule defines who will be retained and this tags can't be now affected by rules below?

        {
          "repositories": ["**"],
          "deleteUntagged": true,
          "deleteReferrers": true,
          "keepTags": [{
            "patterns": ["main$"]
          },{
            "patterns": ["main"],
            "mostRecentlyPushedCount": 3
          },{
            "pushedWithin": "72h",
            "pulledWithin": "720h"
          }]
        }

For ex. here for tags like: main (meta-tag, always points to the last build of this branch), main.1, main.2, branch-foo (meta), branch-foo.13 I want:

main meta-tag always presented
3 latest build from main branch not counting main meta-tag, cause it already matched by rule above
for builds from other branches and it will not affect any main builds cause all of them already matched by above rules

So the main point that this rules will not preserve main builds for 3 days how builds from other branches and will keep only 3 latest how it says, right? Then it's great implementation, thank you very much!
Also about above feature dynamic tags, in real world for complete retention I need something like this:
        {
          "repositories": ["**"],
          "deleteUntagged": true,
          "deleteReferrers": true,
          "keepTags": [{
            "patterns": ["main$"]
          },{
            "patterns": ["main\\..+"],
            "mostRecentlyPushedCount": 8
          },{
            "patterns": ["environments-[a-z]+$"]
          },{
            "patterns": ["(environments-[a-z]+)\\..+"],
            "mostRecentlyPushedCount": 1
          },{
            "pushedWithin": "72h",
            "pulledWithin": "720h"
          }]
        }

Everything like above, but also keep meta-tag for any environment and 1 latest build for each, and also, as for main, not match them by last rule (so not delay deletion for 72h).
In general, everything looks working, I use build of fork with retention for 2 days in my main zot installation, also seems that all works as I described in 3, and so as I said - it's great!

Hello, and thanks for trying it!

done
deleteReferrers, will remove manifests for which their subject is missing.(was deleted, or was never uploaded)
deleteUntagged, will remove manifests without tags
yes, that's right, only the first tag policy is applied so your "main$" should be safe.

Imagine tags like environment-{1,2,..}-* and I want to keep 2 latest for each environment (1, 2, etc), so I must write rules for each environment, but it's a dynamic thing, and there are many of them, I suggest to simplify it somehow.

^here, I don't understand why you need rules per each environment, you want different rules for each one?
Let me think about the rest of the points, thanks for raising them.

@peusebiu pls rebase

I don't understand why you need rules per each environment, you want different rules for each one?

The same, the same to keep last N, but N for each, 1 latest for env-A, 1 latest for env-B, not 1 for any. It seems to me that the best implementation that I have reached is described here.

deleteReferrers, will remove manifests for which their subject is missing.(was deleted, or was never uploaded)

PS what is subject?)

The OCI distribution spec is working towards allowing uploading of arbitrary content and add "soft links" to each other.
https://github.com/opencontainers/distribution-spec/blob/main/spec.md#enabling-the-referrers-api

@lictw Thanks for all the feedback and testing.
This PR has been merged, so build from main and try.
We will take up further enhancements in future PRs.

@rchincha yep, nice job! Please ping me in future PRs to watch.

@peusebiu Hi! I'm back. I'm faced with a situation that I can't seem to solve with the current implementation. But a task seems so basic that I can't believe in it, so I decided to ask if I understand everything correctly.
I want to keep 3 latest tags, but only for some time, something like:
          "repositories": ["foo/**"],
          "keepTags": [{
            "mostRecentlyPushedCount": 3,
            "pushedWithin": "100h"
          }]

but there is OR logic, so above will keep latest 3 tags for forever. It's a DEV builds, I want to delete them fully after some time, but I also what to have only some latest builds if there is many, so it's the reason.
Also, I also have the latest tag, so I want to always keep the latest and 3 latest pushed tags, and delete all of them after some time.
And as side question about latest pulled, is it tracking for a specific tag or for whole image? If an image has 2 tags, but was pulled only by one, the second will be deleted?

@peusebiu up (@rchincha maybe?)

@lictw
To answer your last paragraph, only the tags are deleted, the actual image/manifest is kept/deleted afterwards based on the separate setting you used for deleteUntagged. If the manifest is still referenced by at least one other remaining tag it should not be deleted.
I'm not sure there is a possibility to do an intersection between mostRecentlyPushedCount and pushedWithin. They were designed to independently apply for the same regex pattern identifying the tag strings. And I believe this constraint was because the patterns were meant to be unique, so there wouldn't be a possibility to have the same patterns value in multiple entries inside keepTags if you wanted to implement the OR.
I may be mistaking though. @peusebiu , @rchincha , what do you think?

@peusebiu why 4? Just to clarify that I understand how it equally works. Latest already done after first rule and should be excluded, is not it? So 3 from of the remaining.
After all, does my case is actual? Do you have any thoughts on feature improvements?


Use cases/User Stories

They are pretty much all completely out of date since from early february when we had no conception of how the app would work.

Thats completely fine (for now i guess), we just need to make sure that every use case is there such as our extra one. We also need an updated release planning.


The TensorFlow library was compiled to use AVX instructions, but these aren't available on your machine

The Jenkins build fails at the merge step due to what I previously thought was an Ensmallen error, but it's just tensorflow:
14:32:28  + python3.8 generate_subgraphs.py --nodes merged-kg_nodes.tsv --edges merged-kg_edges.tsv
14:32:32  The TensorFlow library was compiled to use AVX instructions, but these aren't available on your machine.

What is importing tensorflow, though?

Ensmallen shouldn't still be requiring tensorflow, but I think the solution may be to re-compile it (and maybe tensorflow? Hopefully not) for the non-AVX environment.

TF is installed because the Jenkinsfile installs NEAT (it isn't in the setup.py).

resolved by https://github.com/Knowledge-Graph-Hub/kg-phenio/pull/42


Improve the UI of the page

The UI of the page is very raw and has scope for improvement.
It can be redesigned and given a modern aesthetic look.
Please assign me this issue.

@fineanmol please also add the hacktoberfest-accepted tag to this issue
Thank you :)

Hey I'm new to open source contribution but i would love to learn and grow,
can someone help me what i can contribute to the project
I know HTML CSS Javascript React

hey Anmol, can you assign me to this issue, I'll try to improve the background.

Hey Anmol
I Want To Improve the ui of given page please assign me this issue

@fineanmol , I want to work on this issue and make the UI best , would you please assign this to me

Is this still open?

Hi @fineanmol, is this still open for Hacktoberfest 2024?


handheld-daemon: 3.3.8 -> 3.3.11

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for handheld-daemon is: Linux support for handheld gaming devices like the Legion Go, ROG Ally, and GPD Win
meta.homepage for handheld-daemon is: https://github.com/hhd-dev/hhd/
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 3.3.9 with grep in /nix/store/mzw36khwp6k162i77pcdgw1vyl26f334-handheld-daemon-3.3.9
found 3.3.9 in filename of file in /nix/store/mzw36khwp6k162i77pcdgw1vyl26f334-handheld-daemon-3.3.9

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

handheld-daemon

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/mzw36khwp6k162i77pcdgw1vyl26f334-handheld-daemon-3.3.9 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix 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 handheld-daemon https://github.com/r-ryantm/nixpkgs/archive/ff484f06a106906b6b1109caa839cb9b748e13bb.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/ff484f06a106906b6b1109caa839cb9b748e13bb#handheld-daemon

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/mzw36khwp6k162i77pcdgw1vyl26f334-handheld-daemon-3.3.9
ls -la /nix/store/mzw36khwp6k162i77pcdgw1vyl26f334-handheld-daemon-3.3.9/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.
Result of nixpkgs-review run on x86_64-linux 1

2 packages built:

handheld-daemon
handheld-daemon.dist

Maintainer pings
cc @appsforartists @toast003 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.

@ofborg eval

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for handheld-daemon is: Linux support for handheld gaming devices like the Legion Go, ROG Ally, and GPD Win
meta.homepage for handheld-daemon is: https://github.com/hhd-dev/hhd/
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 3.3.11 with grep in /nix/store/2qndfqy0yrc6bdh13fq4jjji5kncyqgw-handheld-daemon-3.3.11
found 3.3.11 in filename of file in /nix/store/2qndfqy0yrc6bdh13fq4jjji5kncyqgw-handheld-daemon-3.3.11

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

handheld-daemon

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/2qndfqy0yrc6bdh13fq4jjji5kncyqgw-handheld-daemon-3.3.11 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix 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 handheld-daemon https://github.com/r-ryantm/nixpkgs/archive/5ec3aafd5f7cc72b50674b8f028449c4d9f910dd.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/5ec3aafd5f7cc72b50674b8f028449c4d9f910dd#handheld-daemon

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/2qndfqy0yrc6bdh13fq4jjji5kncyqgw-handheld-daemon-3.3.11
ls -la /nix/store/2qndfqy0yrc6bdh13fq4jjji5kncyqgw-handheld-daemon-3.3.11/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.
Result of nixpkgs-review run on x86_64-linux 1

2 packages built:

handheld-daemon
handheld-daemon.dist

Maintainer pings
cc @appsforartists @toast003 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.


MyVariant.Info tabs off-by one error

Clicking the tabs doesn't open to the correct content

I can't reproduce this, did you have to do something first to get  it to happen?

To reproduce:

Browse to https://staging.civicdb.org/variants/12/summary
Click on the MyVariantInfo gnomAD (2.1.1) tab. It opens the ClinVar tab, not the gnomAD tab


Add managed option for RMM Pool memory resource to C API

/ok to test

Hi @cjnolet I think this implementation using make_owning_wrapper is more extensible and doesn't throw an error when the current memory resource is not a cuda_memory_resource

/ok to test

/ok to test

/merge

/ok to test

/ok to test

/merge


Issue with k8s.io/docs/tasks/debug-application-cluster/debug-service/

This is a Bug Report

Problem:
Sample with yaml code are not rendered properly.
Example:

"Note: This is the same as if you had started the Deployment with the following YAML: ..."

"Note: As before, this is the same as if you had started the Service with YAML:"

Might be related to upgrade of the markdown parser - existing issue#20915 - https://github.com/kubernetes/website/issues/20915.
Proposed Solution:
Page to Update:
https://kubernetes.io/docs/tasks/debug-application-cluster/debug-service/

Relevant to issue #20335

Fixed by #21390
/close


Machine.current is typed as dynamic

Hi, thanks for this nice library.
It works well for me.
One thing I noticed is that accessing machine.current is typed as dynamic.
I assume this is because in machine.dart
it is defined as
State? get current => _current;

When it probably should be
State<T>? get current => _current;

Thank you for the fix. I'll see what I can do for the setter.


Feature/enhancement Add more shoppers and better shopping

I intend on creating several shoppers ahead of ladder and I wanted to start by setting it up so they can be added dynamically where there will not be a need to modify shopper.py each time a new shopper is added/removed.

I like this PR a lot, this was a ton of work! Sorry it's taken so long to review. One concern I have is that we are planning to merge #724 shortly which will get rid of template matching for item properties, so all the new templates/assets that would be added in this PR would have to be dealt with after merging. Another concern I have is template_finder.py the new multi_search() function duplicates too much code. I'd like to see an implementation more like #683 for that.

Closing for now. Will need to revamp shopper bot after #724 at which point we can revisit this. Really like what you did here.


2024 Kia Sportage - Incorrect request payload format

Region and Brand of car
US 2024 Kia Sportage X-Pro Prestige
Version of the integration
v2.16.3
Describe the bug
Trying to start the car with heating: 4, it fails with the error Incorrect request payload format. Screenshot below shows I do have all of these features available in the app.
Debug logs if an error occurred
2023-12-17 21:19:11.227 DEBUG (SyncWorker_4) [hyundai_kia_connect_api.KiaUvoAPIUSA] hyundai_kia_connect_api - Planned start_climate payload: {'remoteClimate': {'airCtrl': True, 'airTemp': {'unit': 1, 'value': '80'}, 'defrost': True, 'heatingAccessory': {'rearWindow': 4, 'sideMirror': 4, 'steeringWheel': 4}, 'ignitionOnDuration': {'unit': 4, 'value': 10}}}
2023-12-17 21:19:11.228 DEBUG (SyncWorker_4) [hyundai_kia_connect_api.KiaUvoAPIUSA] hyundai_kia_connect_api - sending https://api.owners.kia.com/apigw/v1/rems/start request with {'remoteClimate': {'airCtrl': True, 'airTemp': {'unit': 1, 'value': '80'}, 'defrost': True, 'heatingAccessory': {'rearWindow': 4, 'sideMirror': 4, 'steeringWheel': 4}, 'ignitionOnDuration': {'unit': 4, 'value': 10}}}
2023-12-17 21:19:11.671 DEBUG (SyncWorker_4) [hyundai_kia_connect_api.KiaUvoAPIUSA] hyundai_kia_connect_api got response {"status":{"statusCode":1,"errorType":1,"errorCode":9001,"errorMessage":"Incorrect request payload format"}}
2023-12-17 21:19:11.671 ERROR (SyncWorker_4) [hyundai_kia_connect_api.KiaUvoAPIUSA] hyundai_kia_connect_api - Error: unknown error response {"status":{"statusCode":1,"errorType":1,"errorCode":9001,"errorMessage":"Incorrect request payload format"}}
2023-12-17 21:19:11.674 ERROR (MainThread) [homeassistant.helpers.script.websocket_api_script] websocket_api script: Error executing script. Unexpected error for call_service at pos 1:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 468, in _async_step
await getattr(self, handler)()
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 704, in _async_call_service_step
response_data = await self._async_run_long_action(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 666, in _async_run_long_action
return long_task.result()
^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/core.py", line 2067, in async_call
response_data = await coro
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/core.py", line 2104, in _execute_service
return await target(service_call)
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/kia_uvo/services.py", line 70, in async_handle_start_climate
await coordinator.async_start_climate(vehicle_id, climate_request_options)
File "/config/custom_components/kia_uvo/coordinator.py", line 198, in async_start_climate
await self.hass.async_add_executor_job(
File "/usr/local/lib/python3.11/concurrent/futures/thread.py", line 58, in run
result = self.fn(*self.args, **self.kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/hyundai_kia_connect_api/VehicleManager.py", line 134, in start_climate
return self.api.start_climate(self.token, self.get_vehicle(vehicle_id), options)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/hyundai_kia_connect_api/KiaUvoAPIUSA.py", line 652, in start_climate
response = self.post_request_with_logging_and_active_session(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/hyundai_kia_connect_api/KiaUvoAPIUSA.py", line 41, in request_with_active_session_wrapper
return func(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/hyundai_kia_connect_api/KiaUvoAPIUSA.py", line 86, in request_with_logging_wrapper
raise RequestException
requests.exceptions.RequestException
2023-12-17 21:19:11.705 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140429685065152] Error handling message: Unknown error (unknown_error) Chase Bolt from <IP_ADDRESS> (Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36)
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/websocket_api/decorators.py", line 26, in _handle_async_response
await func(hass, connection, msg)
File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 782, in handle_execute_script
script_result = await script_obj.async_run(
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 1578, in async_run
return await asyncio.shield(run.async_run())
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 420, in async_run
await self._async_step(log_exceptions=False)
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 470, in _async_step
self._handle_exception(
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 493, in _handle_exception
raise exception
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 468, in _async_step
await getattr(self, handler)()
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 704, in _async_call_service_step
response_data = await self._async_run_long_action(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 666, in _async_run_long_action
return long_task.result()
^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/core.py", line 2067, in async_call
response_data = await coro
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/core.py", line 2104, in _execute_service
return await target(service_call)
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/kia_uvo/services.py", line 70, in async_handle_start_climate
await coordinator.async_start_climate(vehicle_id, climate_request_options)
File "/config/custom_components/kia_uvo/coordinator.py", line 198, in async_start_climate
await self.hass.async_add_executor_job(
File "/usr/local/lib/python3.11/concurrent/futures/thread.py", line 58, in run
result = self.fn(*self.args, **self.kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/hyundai_kia_connect_api/VehicleManager.py", line 134, in start_climate
return self.api.start_climate(self.token, self.get_vehicle(vehicle_id), options)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/hyundai_kia_connect_api/KiaUvoAPIUSA.py", line 652, in start_climate
response = self.post_request_with_logging_and_active_session(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/hyundai_kia_connect_api/KiaUvoAPIUSA.py", line 41, in request_with_active_session_wrapper
return func(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/hyundai_kia_connect_api/KiaUvoAPIUSA.py", line 86, in request_with_logging_wrapper
raise RequestException
requests.exceptions.RequestException

To Reproduce
service: kia_uvo.start_climate
data:
  duration: 10
  climate: true
  temperature: 80
  defrost: true
  heating: 4
  device_id: 5115d312c9cce9f562401c1bb71ffc85
  flseat: 8
  frseat: 8

Expected behavior
Start the car with heated steering wheel, heated mirrors, and rear defrost.
Screenshots

Additional Info
I tested different values for heating and these are available to me: 0, 1

Does that option exist in the native app?

Does that option exist in the native app?

Attached to the original post is a screenshot of what I have available in the app. My interpretation from what I see in the app - yes. But they are individual toggles.

To confirm seats work fine?  If you send a 1 does it turn the items on you want?
We just changed this per: https://github.com/Hyundai-Kia-Connect/kia_uvo/pull/747
Maybe Canada and USA are different which makes this a pain to map.

sending 1 turns on Steering Wheel, Side and Back Defroster.
frseat and flseat setting does not respond on my vehicle. i sent it values 0-12 and the ventilated/heated seats never activated.
might need a new property for region to know how to handle these mappings.

Seats are a different value. It has a spot for each seat to send those values.

is there debug documentation i can follow to help provide more info?

Looks like USA doesn't support this in our code for seats. https://github.com/Hyundai-Kia-Connect/hyundai_kia_connect_api/blob/00724b5ab2c4acf315b7752fe18ba32ff06fc2f4/hyundai_kia_connect_api/KiaUvoAPIUSA.py#L633-L650
Someone needs to sniff the traffic and adjust that section to include the seat commands.   Unfortunately no one in the USA maintains this code today.

I tried sniffing the iOS traffic for the Kia Access app, which is what I use, but unfortunately I believe they are using SSL pinning and I am unable to make it work.
I will bust out an android device and see if I can make that work.

Awesome thanks for giving it a go.  That's exactly the work that's needed to improve the USA Kia integration.

saving here the api data for any future searches
{
  "action": "ACTION_EXEC_REMOTE_CLIMATE_ON",
  "remoteClimate": {
    "airTemp": {
      "value": "80",
      "unit": 1
    },
    "airCtrl": true,
    "defrost": true,
    "ventilationWarning": false,
    "ignitionOnDuration": {
      "value": 10,
      "unit": 4
    },
    "heatingAccessory": {
      "steeringWheel": 1,
      "steeringWheelStep": null,
      "sideMirror": 1,
      "rearWindow": 1
    },
    "heatVentSeat": {
      "driverSeat": {
        "heatVentType": 1,
        "heatVentLevel": 4,
        "heatVentStep": 1
      },
      "passengerSeat": {
        "heatVentType": 2,
        "heatVentLevel": 4,
        "heatVentStep": 1
      },
      "rearLeftSeat": {
        "heatVentType": 0,
        "heatVentLevel": 1,
        "heatVentStep": 0
      },
      "rearRightSeat": {
        "heatVentType": 0,
        "heatVentLevel": 1,
        "heatVentStep": 0
      }
    }
  }
}

Is this something you could play with further to understand how options map for the seats for heat vs cool and the levels?
Would be very open for you to drop a pull request for the above code link to get this working.

how do we get a new release with the recent merge in the API?

Title wasn't correct so ci didn't release.  From my phone card to tell if CI is happy or not. I often just fudge something to force it.  I'll do that now.
If interested the USA api could add a lot of data and services to catch up to what this integration is capable of.

Done.  Release is out of API.

thanks. how should i be titling PRs to make sure they get released?

The CI follows semantic release titles.  It is how it picks the release number and generates release notes.   I'm not sure why that last one didn't.
If you google semantic release it shows the rules of it.  I'm no pro with this.   When by a computer I'll tinker to try make sure the checks tell us in advance before I merge it.

@cdnninja when you get a chance can you cut a new release of the API?
also, forgive me I don't develop in python, how do I manually pass options to start_climate()? trying to test locally as described in the readme.

I thought it released yesterday? If you look at the home page of the api repo it shows the current bug fix release number.  Put that into manifest to test.
As for running this with python I'll get you example shortly when I'm at a computer.

Example code that I use to test.  This is so I can reference a local copy of the code:
`from pathlib import Path
import logging
import sys
import os
path_root = r"path to local github directory with edit"
sys.path.append(str(path_root))
from hyundai_kia_connect_api import *
from hyundai_kia_connect_api.exceptions import *
logging.basicConfig(stream=sys.stdout, level=logging.DEBUG, format='%(asctime)s %(name)s %(levelname)s:%(message)s')
logger = logging.getLogger(name)
vm = VehicleManager(region=1, brand=3<EMAIL_ADDRESS>password="test", pin="", geocode_api_enable = True)
print(vm.check_and_refresh_token())
vm.update_all_vehicles_with_cached_state()
print(vm.vehicles)
`
Now in here where the print is called you could add other items to run:
start climate would be something like.  It would also need seats added if you like following the names here: https://github.com/Hyundai-Kia-Connect/hyundai_kia_connect_api/blob/b705f143aa87f82c8e45d383254636281ecb96f0/hyundai_kia_connect_api/ApiImpl.py#L19-L28
climateOptions = ClimateRequestOptions(set_temp = 70, duration = 10, defrost = True, climate = True, heating = 1)
vm.start_climate(vm.vehicles[0].id, climateOptions)

great, thanks for all the help! heated/ventilated seats are complete for USA now. going to close this out 😄
not sure if there are any other missing features, ill poke around but if you know of any feel free to let me know and ill see what I can do to add them!

Great thanks!! The two things that come to mind are:

Trip data.  Our API supports it for EU. I assume it exists for USA.
A lap around the response of raw API data to see if our mapping could add other items.  I would expect we don't map all the data we could.


Segfault Running Pre-Compiled Binary

Hi, I cross compiled a rust binary for arm-unknown with hardware floating point. I copy it into the docker container, but when I run it, it segfaults. Is this a known problem or am I targeting the wrong architecture? The target device is a first generation Raspi.

Cross-compilation for Rpi 1 (ARMv6) is trickier than Rpi 2 & 3 and I personally encountered similar segfaults. The problem is not with Rust, but the debian cross-compilation toolchain linker that does not support ARMv6. You can check the binary with readelf -a <binary> or file <binary> and most probably you will find that it is linked as ARMv7 binary.
The correct Rust target for Rpi 1 (ARMv6) is arm-unknown-linux-gnueabi.
Most probably you can get positive results using this cross-compilation Rust toolchain: https://github.com/japaric/cross
For my use case (WiFi Connect) I could not use the above toolchain, so I had to go with a custom solution. I managed to successfully compile using a Raspbian fork of the debian toolchain that supports ARMv6. You can look at this Dockerfile for how I achieved that: https://github.com/resin-io/resin-wifi-connect/blob/master/scripts/docker/arm-unknown-linux-gnueabihf/Dockerfile

Thanks for the help. I managed to fix this with cross as you suggested.
There was one thing that had to be done in addition to simply using the toolchain:
For the benefit of people seeing this in the future, link /lib/arm-linux-gnueabihf/ld-linux.so.3 to /lib/ld-linux.so.3 if using Debian as the base image.
Thanks,
Dan


After the updated version of the Dyson Ball Project, the antimatter fuel rod formula has been changed and a new furnace has been added.

Is your feature request related to a problem? Please describe.
After the updated version of the Dyson Ball Project, the antimatter fuel rod formula has been changed and a new furnace has been added.
Describe the solution you'd like
According to the 5.28 update version, the official has made the following changes:
Modify antimatter fuel rod energy 7.5GJ -> 7.2GJ, consume antimatter quantity 10 -> 6
Added more advanced furnaces, related technologies, and synthesis formulas
Describe alternatives you've considered
nothing
Additional context
https://store.steampowered.com/news/app/1366540/view/3044975900132654798

I appreciate the additional information, but I think this is covered by #493.

I appreciate the additional information, but I think this is covered by #493.

I saw it, thank you, then I close this issuses


Hierarchical facet: add a configuration option to disable the automatic selection of subconcepts

Closed with https://github.com/SemanticComputing/sampo-ui/commit/0066a9d1f05bdbdac6bc5c4eb64a0f4b32e63fde


small update to glossary.md

missing "/id" in the example URL under "route"

Thanks for the correction!


MailMessage Template Laravel 7 Unexpected response

I'm trying to use the MailMessage class to send in postmark template, the configuration is correct but I receive a json as a message to my mailbox.
this is my implementation

this is my response
{"__env":{},"app":{"contextual":[]},"id":18999584,"alias":"user-c=
onfirmation","model":{"name":"Usuario","product_name":"Maquillate=
.com","action_url":"https://dev.maquillate.com/confirmation","=
login_url":"https://dev.maquillate.com/login","username":"Usua=
rio"},"__laravel_notification_id":"02bb8627-5d08-485f-9122-4e7091=
79f8c1","__laravel_notification":"App\Notifications\UserConfirm=
ation","__laravel_notification_queued":false,"message":{}}=0D=0A

Your environment
Include as many relevant details about the environment you experienced the bug in and how to reproduce it.

Laravel Postmark Version: 2.8
Laravel Version: 7.x
PHP Version: 7.4

Hey @DevelTwist, that seems like what is supposed to happen to me. When the package detects that it's trying to send a templated email (by checking if the body of the message can be properly JSON decoded), it includes TemplateId, TemplateAlias, and TemplateModel in the request to Postmark.
Perhaps there is an error happening when it is being decoded? It would look like it's not hitting the /email/withTemplate endpoint for some reason. Can you try adding some logging locally and see what does?

Let me check

@craigpaul we couldnt find the issue, we thought about other solution and we fixed it using http package of laravel and postmark api while you can fix this issue.

I'm not exactly certain I understand the problem. I'm curious if others who use this feature have experienced this. @MatanYadaev have you experienced this?

@craigpaul  For some reason the templated method on Transport class is not executing. Unusual

That's very unusual, never heard of that happening. I'm gonna try a fresh Laravel 7 install to try and reproduce this. If you're able to provide an example repo that can reproduce this problem, that would be very helpful.

Hey @DevelTwist, I just tried the fresh Laravel 7 install and it worked. I'm going to need to see a repo that can reproduce the error in order to assist any further.

I'm going to close this for now. If someone can come up with a repository to reproduce the problem, we can take another look 👍


Revise ApplyFunctionWithLookupTable (#617)

Taking the fix we need for release.

There were no other commits to main. However, I'll close this request and create a new one with the cherry-pick process.


Scramble String

Problem Link
https://leetcode.com/problems/scramble-string/
Coding platform
Leetcode
Programming language

[ ] C
[ ] C++
[ ] Java
[ ] Python

Additional context (OPTIONAL)
I want to solve it in Java

Hi @Nivedita967
I would like to solve it in Python. Please assign it to me.

I would like to solve it in c++

@Nivedita967 can I do in C?

@Nivedita967 can I work in Java??


Parent nodes sometimes are not deselected when choosing child nodes

Hello,
as you can see in the image, the child nodes are selected along with their parents (not the expected behavior, since only one node san be selected simultaneously in the demo). It somehow depends on node fetching, probably. The highlighted nodes were fetching their child nodes from the backend, populating them into the tree and the component was re-rendered.

Code:
        if (this.state.cursor) {
            this.state.cursor.active = false;
        }
        node.active = true;
        if (node.children) {
            node.toggled = toggled;
        }
        this.setState({cursor: node});
        if (node.hasChildren && node.description) {
            this.props.dispatch(fetchNode(node.id, node.applicationId));
        }
    }

Please notify me if something else is needed from me.

The reason was the state mutation in improper action implementation.


Any ideas on TO-MHT implementation?

Dear experts,
I am currently working on TO-MHT algorithms. I was wondering is it possible(convenient) to implement TO-MHT using current available modules?
I appreciate your valuable advice!
Sincerely,
Chuan

We've got a lot of building blocks. I think we'd need to create a Tracker class, which doesn't have a DataAssociator but instead an Hypothesiser (which would include Gater classes), and then handles creation/pruning of track tree structure. We could then create different tracker classes, or maybe pass in different pruning classes, to create different variants.
It may make sense to have this track tree structure have a set like interface which is yielded from the tracker, which then yields the current time "best" tracks when iterating over. This way you could create a copy of the structure at each timestep if you wanted to understand how MHT evolved over time, as well as providing familiar interface to other components.

Thank you! I'll work on it after I discuss with my colleagues. Hope there will be a meaningful conversation going on.

We are currently commissioning development of MHT into Stone Soup, so hopefully see something in coming months. I've reopened this issue so we can track it here.
@Bebert98 Maybe you could open a discussion with the issues you're having and we can try and help.
You may also be interested in #568. I've just been updating this to latest version and adding an example, which I'll push in draft form soon.


Fix fixed min samples

See #185 (but doesn't close that issue)

Also, setting tox to test all versions that I saw in .travis.yml

Codecov Report

Merging #194 into master will increase coverage by 0.21%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #194      +/-   ##
==========================================
+ Coverage   77.59%   77.80%   +0.21%
==========================================
  Files          10       10
  Lines         741      739       -2
  Branches      156      155       -1
==========================================
  Hits          575      575
  Misses        134      134
+ Partials       32       30       -2

Impacted Files
Coverage Δ

kmapper/kmapper.py
88.44% <100.00%> (-0.10%)
:arrow_down:

kmapper/plotlyviz.py
42.76% <0.00%> (ø)

kmapper/cover.py
89.77% <0.00%> (+2.27%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 925f09c...69b2858. Read the comment docs.


KAFKA-5469: Created state changelog topics not logged correctly

Fixed debug logging for the created state changelog topics
Added toString() for InternalTopicMetadata and InternalTopicConfig for above debug logging

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/kafka-pr-jdk8-scala2.12/5453/
Test FAILed (JDK 8 and Scala 2.12).

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/kafka-pr-jdk7-scala2.11/5468/
Test PASSed (JDK 7 and Scala 2.11).

Retest this please

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/kafka-pr-jdk7-scala2.11/5470/
Test PASSed (JDK 7 and Scala 2.11).

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/kafka-pr-jdk8-scala2.12/5455/
Test PASSed (JDK 8 and Scala 2.12).

@dguy maybe you can take a look at this as well even related to log in the Streams library ?

@mjsax can you review this please ? I'd like to have it merged because I have some other fixes but want to avoid conflicts.

@dguy thanks ! Now I can work on another proposal related to logging.


Tuesday 05-12-2023  roll call

Roll Call!
Leave a comment with these two things:

A summary of your study using only emojis
Something you'd like to share, anything goes! (within respect)

emoji cheat sheet

Good morning 🦩

Good morning

Hi

good morning

Good morning

Good morning

Good morning

good morning


Parse LiveQuery not working on Digitalocean

I am running Parse server on Digitalocean with liveQuery every time when the application trying to connect to websockets i got this error:
WebSocket connection to 'ws://xxx.xxxx.com/api' failed: Error during WebSocket handshake: Unexpected response code: 403
Everything else is working fine in my app just livequery not working and when i am trying to run the application and parse server locally it's working fine and live working fine on locally.
My index.js for parse is:
var app = new ParseServer({
databaseURI: databaseUri || database.url,
cloud: process.env.CLOUD_CODE_MAIN || __dirname + '/cloud/main.js',
appId: process.env.APP_ID || appid,
masterKey: process.env.MASTER_KEY || masterkey,
serverURL: process.env.SERVER_URL || serverurl,
javascriptKey: jsKey,
restAPIKey: restapi,
facebookAppIds: fbid,
liveQuery: {
classNames: ["conversations", "messages"]
},
});
var port = process.env.PORT || 80;
var httpServer = require('http').createServer(app);
httpServer.listen(port, function() {
console.log('parse-server-example running on port ' + port + '.');
});
// This will enable the Live Query real-time server
ParseServer.createLiveQueryServer(httpServer);
Please include a detailed list of steps that reproduce the issue. Include curl commands when applicable.

Server

parse-server version (Be specific! Don't say 'latest'.) : 2.2.24
Operating System:      Ubuntu 14.04.4 x64
Hardware:            DELL with hardware RAID, 32-64GB
Localhost or remote server? (AWS, Heroku, Azure, Digital Ocean, etc): Digital Ocean

If you can drill this down to a particular issue with Parse Server, please open a new issue. We're unable to troubleshooting individual deployments.


v3.0.18 - syno_app_mover.sh: line 1151: package_names["${package_name}"]: bad array subscript

i went to execute the script to try re-doing calendar, container manager, and download station.
after pressing "2" for backup, i get an error and the "ready" question has the wrong item in the confirmation field. see blow.
root@DS-920_spare:/volume3/volume3_share# bash syno_app_mover.sh
Synology_app_mover v3.0.18
DS920+ DSM 7.2.1-69057-4
Running from: /volume3/volume3_share/syno_app_mover.sh

Move
Backup
Restore
Select the mode: 2
You selected Backup

Backup path is: /volume3/volume3_share/backup_before_move
syno_app_mover.sh: line 1151: package_names["${package_name}"]: bad array subscript
Destination volume is /volume3
Ready to Backup  to /volume3/volume3_share/backup_before_move? [y/n]
here are lines 1150 through 1152. not sure if those lines are meant to be commented out?
if [[ ! ${package_names[*]} =~ "${package}|${package_name}" ]]; then
        package_names["${package_name}"]="${package}"

fi

i also get the same error when trying option 1
root@DS-920_spare:/volume3/volume3_share# bash syno_app_mover.sh
Synology_app_mover v3.0.18
DS920+ DSM 7.2.1-69057-4
Running from: /volume3/volume3_share/syno_app_mover.sh

Move
Backup
Restore
Select the mode: 1
You selected Move

syno_app_mover.sh: line 1151: package_names["${package_name}"]: bad array subscript

/volume1
/volume2
/volume3
Select the destination volume:

Strange. I'm not getting any error.
What does ls /var/packages return?
Try uncommenting line 50 and 52. Then change line 50 to:
if [[ ! ${package_names[*]} =~ "${package}" ]]; then

root@DS-920_spare:~# ls /var/packages
ActiveBackup            CloudSync         FileStation       MariaDB10     PHP7.3           RagicBuilder         SynoFinder                  Virtualization
ActiveBackup-GSuite     CMS               Git               MediaServer   PHP7.4           ReplicationService   SynologyApplicationService  VPNCenter
ActiveBackup-Office365  CodecPack         GlacierBackup     MediaWiki     PHP8.0           resiliosync          SynologyDrive               vtigerCRM
ActiveInsight           Contacts          GoodSync          MEGAcmd       PHP8.1           ScsiTarget           SynologyPhotos              WebDAVServer
AntiVirus               ContainerManager  HighAvailability  MinimServer   PHP8.2           SecureSignIn         SynoOnlinePack_v2           WebStation
Apache2.4               DdbBackup         HybridShare       NBR           phpMyAdmin       SMBService           SynoSmisProvider            WordPress
ArchiwareP5             DirectoryServer   HyperBackup       Node.js_v14   PlexMediaServer  SnapshotReplication  Tailscale
AudioStation            DNSServer         HyperBackupVault  Node.js_v16   PrestoServer     Spreadsheet          TeamViewer
BackupRestoreManager    DocumentViewer    IDrive            Node.js_v18   ProxyServer      SSOServer            TextEditor
BitDefenderForMailPlus  domotz            Joomla            Node.js_v20   Python2          StorageAnalyzer      UniversalViewer
C2IdentityLDAPAgent     DownloadStation   KodExplorer       NoteStation   Python3.9        StorageManager       USBCopy
Calendar                elephantdrive     LogCenter         OAuthService  QuickConnect     SupportService       VideoStation
Chat                    exFAT-Free        MailPlus-Server   Perl          RadiusServer     SurveillanceStation  VirtualHere

i edited the script as you requested
        if [[ ! ${package_names[*]} =~ "${package}" ]]; then
            package_names["${package_name}"]="${package}"
        fi

and this is the results
root@DS-920_spare:/volume3/volume3_share# bash syno_app_mover.sh
Synology_app_mover v3.0.18
DS920+ DSM 7.2.1-69057-4

Running from: /volume3/volume3_share/syno_app_mover.sh

1) Move
2) Backup
3) Restore
Select the mode: 2
You selected Backup

Backup path is: /volume3/volume3_share/backup_before_move

syno_app_mover.sh: line 1151: package_names["${package_name}"]: bad array subscript
Destination volume is /volume3

Ready to Backup  to /volume3/volume3_share/backup_before_move? [y/n]

no longer getting the error with 3.0.19


merge from konsum-frontend-svelte,template-css,template-svelte-app

package-lock.json

add missing package-lock.json from template

.github/pr_labeler.yml

chore: add package-lock.json (npm)

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

npm package (@latest dist-tag)
v1.32.0
GitHub release

Your semantic-release bot :package::rocket:


I want to add FibonacciNumber c++ code

This issue is about [FibonacciNumber ].

[X] Issue Title is in form FibonacciNumber [C++].
[X] I searched or browsed the repo’s other issues to ensure this is not a duplicate.
[X] This Algo/DS is worth adding to this repository.
[X] Assign this issue to me (I want to work on this).

[X] I ensure that I am not already assigned to 2 or more issues.

[X] I will send my PR only after I'm assigned to this issue by any maintainer.
[X] I understand that I will be unassigned from this issue if I fail to send a PR for this within a week.

assign this issue to me


Chapter 4 Address 2 update #2

Looks like we diverged from the challenge repo made a change to see if this is right for address 2
also fixes some copy
Preview

@pinheadmz when testing, you won't really be able to reach a success page since logging in on this branch is blocked but as long as you are replacing compressed_public_key in the function with the actual hex string you can verify the value

I addressed everrything you brought up in your last comment!


cmake: fix dependencies so that make with multi jobs can be used

Signed-off-by: Alessandro Comodi<EMAIL_ADDRESS>Fixes https://github.com/QuickLogic-Corp/symbiflow-arch-defs/issues/171

@acomodi since #174 is merged, can we rebase this PR so it gets tested in GH actions?

@kgugala Sure, makes sense

I have reverted back CI to use make instead of ninja (as make is more unstable) so that it gets tested in CI.

as expected GH actions passed, travis timed out. I think we can remove travis from this repo, or use it just for quick checks (like e.g. code formatting)

We can keep the Travis.
From: Karol Gugala<EMAIL_ADDRESS>Sent: 20 October 2020 00:40
To: QuickLogic-Corp/symbiflow-arch-defs<EMAIL_ADDRESS>Cc: Kishor Kumar<EMAIL_ADDRESS>Review requested<EMAIL_ADDRESS>Subject: Re: [QuickLogic-Corp/symbiflow-arch-defs] cmake: fix dependencies so that make with multi jobs can be used (#172)
as expected GH actions passed, travis timed out. I think we can remove travis from this repo, or use it just for quick checks (like e.g. code formatting)
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHubhttps://github.com/QuickLogic-Corp/symbiflow-arch-defs/pull/172#issuecomment-712383910, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AOX6WQBKD4DVHE7NPV437F3SLSFKDANCNFSM4SR3BZ2Q.

@kgugala : for email notification's on the build status , do we need to set anything for GH actions ?

By default, the notifications are sent to the author of the commit which triggered the build


SurfaceProducer needs a "will destroy" signal, not a "did destroy"

This is the same issue as #152839.
To recap, the SurfaceProducer API currently provides an onSurfaceDestroyed callback that is invoked after a surface has been destroyed. However, if the surface is being accessed by another thread, this is too late to do any cleanup as the thread may attempt to access the surface in between the call to cleanup() and the callback being invoked. Instead, we need a callback that is invoked before the call to cleanup() so that the rendering thread can be notified appropriately.
public void onTrimMemory(int level) {
  if (!trimOnMemoryPressure) {
    return;
  }
  if (level < ComponentCallbacks2.TRIM_MEMORY_BACKGROUND) {
    return;
  }
  synchronized (lock) {
    numTrims++;
  }
  // add callback.onSurfaceDestroying() here
  cleanup();
  // currently, surface could still be accessed from another thread here, but it is invalid
  createNewReader = true;
  if (this.callback != null) {
    this.callback.onSurfaceDestroyed();
  }
}

This is the reason for the video_player package needing to destroy and recreate the entire player instance, as ExoPlayer will attempt to access the surface from the renderer thread after it has been destroyed, and go into an invalid state. This workaround is problematic as it breaks background playback, and results in the entire player state needing to be reloaded. This comment in the previous issue mentioned that it impossible to avoid this save/restore of the state, but this is not true since an onSurfaceDestroying callback would allow us to call player.setVideoSurface(null) on the ExoPlayer instance to ensure that it does not access the surface once it is destroyed, and allow playback to continue without a video surface.

Thank you for explaining the outcome you want, and thank you for debugging why the invalid state is happening.
Let's imagine for a moment that we changed onTrimMemory to the following:
public void onTrimMemory(int level) {
  if (!trimOnMemoryPressure) {
    return;
  }
  if (level < ComponentCallbacks2.TRIM_MEMORY_BACKGROUND) {
    return;
  }
  synchronized (lock) {
    numTrims++;
  }
  // add callback.onSurfaceDestroying() here
+  if (this.callback != null) {
+    this.callback.onSurfaceDestroyed();
+  }
  cleanup();
  // currently, surface could still be accessed from another thread here, but it is invalid
  createNewReader = true;
-  if (this.callback != null) {
-    this.callback.onSurfaceDestroyed();
-  }
}

(1) Would that be sufficient? I'd rather not add another API, and I'm trying to understand if users need to know both before and after signals. That is, specifically - do you know any reason you'd need to know after the destruction happen, and is just before sufficient?
(2) How would you propose changing video_player_android if this change was made? If I understand your request, it would be:
@RestrictTo(RestrictTo.Scope.LIBRARY)
// TODO(matanlurey): https://github.com/flutter/flutter/issues/155131.
@SuppressWarnings({"deprecation", "removal"})
public void onSurfaceCreated() {
-  if (savedStateDuring != null) {
-    exoPlayer = createVideoPlayer();
-    savedStateDuring.restore(exoPlayer);
-    savedStateDuring = null;
-  }
+ exoPlayer.setVideoSurface(surfaceProducer.getSurface());
}

@RestrictTo(RestrictTo.Scope.LIBRARY)
public void onSurfaceDestroyed() {
-  // Intentionally do not call pause/stop here, because the surface has already been released
-  // at this point (see https://github.com/flutter/flutter/issues/156451).
-  savedStateDuring = ExoPlayerState.save(exoPlayer);
-  exoPlayer.release();
+  exoPlayer.setVideoSurface(null);
}

(1) Agreed, I don't think there is a use case for needing to be notified after the destruction.
(2) Exactly.

Ok, let's make this change.
I am guessing this supersedes the need for https://github.com/flutter/flutter/pull/160920 as well and fixes https://github.com/flutter/flutter/issues/156488?

Looks like it should indeed address both of those.

@matanlurey Shall I file a docs follow-up for updating https://docs.flutter.dev/release/breaking-changes/android-surface-plugins ?


added windows 11

added windows 11

Learn Build status updates of commit 4177e46:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

windows/security/threat-protection/security-policy-settings/network-list-manager-policies.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel


Investigate using ionice to lower disk io priority of tile downloads

Currently the opsman vm (for pioneer) becomes almost unresponsive when tiles are being downloaded.
https://linux.die.net/man/1/ionice
Prefered solution would use go binding (if available) so this solution would be applied to all projects using om-tiler (it might need to be configurable because of the concourse-resource usecase).

after investigation, have opted for using ionice via bash script for pioneer, since the azure quickstart project is currently the only project executing om-tiler from the opsman vm directly.


Add changelog

It would be really nice with a changelog for each new release.

can we use git releases for this?

would be really sweet if this page had the release notes of each version https://github.com/lwansbrough/react-native-camera/releases
Every time there's an update I have to go through the commit logs and try to figure out what changed

we gonna come up with something on this issue https://github.com/lwansbrough/react-native-camera/issues/246#issuecomment-350577509


Add an option to disable anonymous requests to the 5984 port

What this PR does / why we need it:
CouchDB allows anonymous requests despite the COUCHDB_USER and the COUCHDB_PASSWORD variables are set. With these changes the cluster is able to deny any unauthenticated requests to the port 5984 port.
Checklist

[x] DCO signed
[x] Chart Version bumped

cc: @kocolosk

/ok-to-test
/assign

/lgtm

Cool.
I would have proposed to update this commit message and PR to read "Fix liveness and readiness probes to work with require_valid_user setting". The "option to disable anonymous requests" is not a new option, and this PR preserves the existing default of false for that option. It rather addresses the oversight that the health checks will fail if this config flag is set - so thanks!
This would all be a bit cleaner if the httpGet probe supported a username and password for Basic auth. Of course we could compute the Authorization header ourselves, but that's probably no better than the exec out to curl.


Add instructions to set the repo to private

We should add instructions to have the user set the repo to private, so that the date they upload is not publically visible

We already documented in https://github.com/fortinet-fortisoar/solution-pack-cicd/blob/release/2.0.0/README.md file under "Initial Configuration" section point no 2


MAINT: Replace some Unicode dash-like chars with an ASCII hyphen.

A trivial change, but let's minimize the use of non-ASCII characters.
Also modernize a string used as a warning message.

The test failure is the recurring "Windows Python36-32bit-full" 60 minute time out.

Thanks @rlucas7.  I assume that it wasn't merged earlier to allow for more time for review from other devs.  But now that there are two approvals...

Thanks Warren et al.

If anyone has a moment, another PR with a tiny change is https://github.com/scipy/scipy/pull/12404.  Once that PR is merged, we can move ahead with https://github.com/scipy/scipy/pull/12393, which will make the message about unwanted unicode characters much nicer.


Update README with SSL support.

Merged, thanks!

@yossigo You put USE_TLS=1 in the READMD.md, but I shouldn't it actually be USE_SSL=1

@michael-grunder thanks, you are right of course.


"before all" hook error when running ./specs-docker.sh

Have followed README line by line. When running the tests I get the following errors:
Setup specs
1) "before all" hook
Authentication
Signin
2) should fail to return token for invalid provider
All the Authentication Providers error as well. Serverless 1.0.2 installed. OSX El Capitan. Docker 1.12.1

Ok, I see that the instructions how to run specs are not so good. Obviously you have ran npm install on project root (which was missing from instructions) because it would of fail before running nay tests. Do you have docker compose installed? You could check that LOCAL_DDB_ENDPOINT ip in specs-docker.sh is same than default docker machine ip by running docker-machine ip default. Can you share the error that it thows or least parts of it?

When I run docker-machine ip default it outputs Host does not exist: "default". I'm new to docker so I may be missing something here. I ran docker-compose up -d from the root of the project.

This is resolved. On my system it was just localhost.


Incorrect measurements for simplest circuits

For trivial circuits on 2 qbits like:

Circuit(X(0), X(1), X(0)) stats should be |01> only, for some reason simulation gives only 10.
Circuit(X(0), CNOT(0, 1), X(0)) [this is inverse CNOT], stats should be |01> only, again, for some reason simulation gives only 10.

@RomanPylypchuk Scotty uses little-endian for registers and redouts, so the results you're getting are correct.

Yes, sorry, I understood it just a while after posting this issue, and closed it. It is strange for a person with physics background to see such notation for qubit basis states.
Will someone be adding any new features to this framework? It seems like there were no commits for the last 2 years)
I've started writing some quantum machine learning code using Scotty for learning purposes, and faced the problem of having to write many essential things from scratch. For example, there is no inverse CNOT gate. I've built it is as CompositeGate, but then if you try to build inverse CCNOT using Controlled of that inverse CNOT, this fails type match in finalTarget in ControlGate trait, since CompositeGate is neither a ControlGate nor TargetGate. And this also applies to building any single qubit unitary, controlled by a few qubits pattern as one gate. For now, I've implemented this on a circuit level, but I expect, that for bigger quantum algorithms such limitations might quickly become a nuisance.

@RomanPylypchuk, sorry for the delayed response!

It is strange for a person with physics background to see such notation for qubit basis states.

I've definitely seen both. For example, the pyQuil Wavefunction Simulator also uses little-endian.

Will someone be adding any new features to this framework?

If there is any meaningful demand for new features I will work on it. Currently, the simulator is only useful for toy projects as it doesn't scale out horizontally. One interesting possibility is adding support for distributed states and gate applications via Ray, Dask, or Spark distributed primitives.

I've started writing some quantum machine learning code using Scotty for learning purposes, and faced the problem of having to write many essential things from scratch

It would definitely help to have more gate implementations added. Currently, it should be possible to implement most gates with existing primitives though.

I've built it is as CompositeGate, but then if you try to build inverse CCNOT using Controlled of that inverse CNOT

Could you post example code for this?


How can I add a new customized cipher？

Hi,
Can someone provide any clue or guide to add a new customized cipher into this project? Thank you so much!

I have just started studying SoftEther code, so I'm not the best to answer this, but here goes anyway.
It doesn't seem that difficult. SoftEther import libssl-dev headers and depends on their implementation.
To understand how a cipher is imported into SoftEther, do a text search on one of the famous ciphers, basically the cipher is defined and added to the list of supported ciphers. Example:
sh grep -rn "AES-128-CBC " *
Hope this helps


I think I should build an RESTful api for backend!

I think I should build an RESTful api for backend!

done


Realm Predicate

Hi There
I am using the new realm 0.92.3 and my predicate is for some reason ordered by id.  I am using a for loop on specific id's from an array and return results.  example my id array [21,2,3,5] (previously ordered).  If I use a realm predicate to return something like 'name' from a specific id in that order (id = 21, id = 2 etc), the predicate orders the realm objects ascending in terms of id.  E.g name for id = 2, id = 3, id = 5 and not is the above mentioned order.

@WayneNotTaken could you please share the code you're using to construct your result?

Sure.
for var i=0; i < gigIdArray.count; i++ {
        let ii = gigIdArray[i]

        let artistPredicate = NSPredicate(format: "id = %@", argumentArray: [ii])
            let details = realm.objects(Gigs).filter(predicate)

        for event in details { // 2
            let eventDetails = event  as Gigs
            let artistNames = eventDetails.artists
            let gigDate = eventDetails.startDate

            self.gigArtistsName.append(artistNames)
            self.gigDate.append(gigDate)

        }

So my gigIdArray reads as follows [58, 38, 12, 73, 72], if i run a println(artistPredicate) it returns in that order.  But if I run a println on details it returns the object ordered accending but gigId. e.g 12,38,58 etc.
This snippet of code worked on the old realm release.

On 22 May 2015, at 5:33 PM, Samuel E. Giddins<EMAIL_ADDRESS>wrote:
@WayneNotTaken https://github.com/WayneNotTaken could you please share the code you're using to construct your result?
—
Reply to this email directly or view it on GitHub https://github.com/realm/realm-cocoa/issues/1983#issuecomment-104692645.

Filtering objects has no guarantee of ordering in Realm, so you should used Results.sorted(_:) for your details:
for gigID in gigIdArray {
  let details = realm.objects(Gigs).filter("id = %@", gigID).sorted("id")
  for eventDetails in details { // 2
    self.gigArtistsName.append(eventDetails.artists)
    self.gigDate.append(eventDetails.startDate)
  }
}

Thanks JP. Half asleep here. Thanks so much for your help.
Sent from my iPhone

On 22 May 2015, at 22:42, JP Simard<EMAIL_ADDRESS>wrote:
Filtering objects has no guarantee of ordering in Realm, so you should used Results.sorted(_:) for your details:
for gigID in gigIdArray {
let details = realm.objects(Gigs).filter("id = %@", gigID).sorted("id")
for eventDetails in details { // 2
self.gigArtistsName.append(eventDetails.artists)
self.gigDate.append(eventDetails.startDate)
}
}
—
Reply to this email directly or view it on GitHub.

haha, no problem! anytime


Aurora Over-rides Default Lighting Schema

Just a quick thing, I'm not sure if there's a way to avoid this but Aurora over-rides the default lighting schema for certain games. Example in question, I'm playing Evolve and LGS (I'm using a Logitech 910) has some cool effects for the keyboard built-in. However, if I alt+tab, Aurora turns it back into the Desktop effects (CPU and RAM usage, etc.). When I go back into the game, the lighting schema doesn't change back to the Evolve lighting effects, it stays in the Desktop lighting mode from Aurora.
Any way to fix this or avoid it w/o disabling the desktop lighting altogether?

If you patch the Logitech Wrapper with Aurora, all Logitech lighting effects will go through aurora. Which will map effects based on process name, and will recover them when tabbing back in.
Logitech wrapper install can be found under the GTA 5 Profile.

Did this answer your question?

Oh, sorry -  yes it did. I had to restart after using your advice but it
works like a charm now.
On Jul 14, 2016 02:10, "Anton Pupkov"<EMAIL_ADDRESS>wrote:

Did this answer your question?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/antonpup/Aurora/issues/59#issuecomment-232565489, or mute
the thread
https://github.com/notifications/unsubscribe/ATVc1pUjCvwobZp3NTt23ru5cC1jzv9yks5qVdK9gaJpZM4JHknf
.


Fix the automatic override for networking.nameservers when services.bind is enabled.

Motivation for this change
The Nixos-networking code assumes that when services.bind is enabled it means it runs in local resolver mode. This is not always true as I run Bind in master mode to host a domain and I point networking.nameservers to an external name server.
What happens is that my system cannot run Bind in master mode and resolve names at a remote name server.
Things done
This PR changes the Nixos networking configurator to check for a new attribute resolveLocalQueries to services.bind. It defaults to true to keep the existing behaviour of setting <IP_ADDRESS> as nameserver in /etc/resolv.conf
When that flag is set to false, it doesn't set the resolver and the standard behaviour applies. I.e.: If networking.nameservers is set, choose that, otherwise let resolveconf handle DHCP. etc.
See for more discussion my previous PR: https://github.com/NixOS/nixpkgs/pull/29205
Closes #29202

Built on platform(s)

[X] NixOS
[ ] macOS
[ ] Linux

Thanks! Merged and squashed your commits into one.
In future PRs, please try to make commits self-contained and remove/squash commits whose code was removed or are merely small fixes to previous commits.
Oh, and just noticed this is your contribution! Welcome on bord! :wave:

@fpletz indeed, my first contribution to Nixos.
Does this get merged with master later or do I need to submit a PR against master as well?

Oh, damn, I didn't notice this PR was against 17.09. You should base all your PR against master. They will be picked into the release branches as needed. I'll pick it into master.

@fpletz, thanks for explaining the procedure. Will abide.

This change breaks my name server: https://github.com/NixOS/nixpkgs/pull/29205#pullrequestreview-63014190. @fpletz, can you please revert this merge? I don't think we should add this PR as-is.

@peti Really? Have you tested it? resolveLocalQueries defaults to true now so PR shouldn't change the old behavior.

Reverted in 23a021d12e8f939cd0bfddb1c7adeb125028c1e3 and 99f759de1c6c943fd747afd8fb896a0d65ae4ed8.

I agree that the problem this PR tries to solve is real, but I don't agree with the proposed solution.

@peti, please don't take my change to a different PR as a way to avoid the review process. On the contrary. I closed the old one because I messed it up. Then, I linked both to each other for continuity. Apologies for causing the confusion.
I took your remarks of not breaking existing setups to heart and removed the assertion. That would have broken your situation and forced you to comment out the nameservers attribute.
I then changed the way Nixos handles Bind to do it identical to Dnsmasq. That leaves existing installations intact while lets me run Bind in a master-only role.
Please read this patch again to check whether it would break your situation.


feat(motion_velocity_smoother): add force acceleration function

Description
A function to adjust the parameters for the motion velocity smoother is added. The purpose is to realize quick acceleration when needed.
As it is a basic function, std_srvs::srv::SetBool service is implemented to adjust few parameters.
Once there is a request with "true", the parameters would be updated. If the request is "false" or there is no request the default values would be used for the velocity smoothing.
Related links
https://github.com/autowarefoundation/autoware_launch/pull/1010
Tests performed
TIER IV interal evaluator + Psim
Notes for reviewers

Interface changes

ROS Service Changes

Service Name
Type
Description

/planning/scenario_planning/motion_velocity_smoother/adjust_common_param
std_srvs::srv::SetBool
Changes the parameter for maximum acceleration,  maximum jerk, and maximum lateral acceleration

/planning/scenario_planning/motion_velocity_smoother/slow_driving
std_srvs::srv::SetBool
Receive a request

Effects on system behavior
Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.
[ ] The PR has been properly tested.
[ ] The PR has been reviewed by the code owners.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.
[ ] The PR is ready for merge.

After all checkboxes are checked, anyone who has write access can merge the PR.

@go-sakayori
This advice is not just for this PR but in general: when communicating between systems (like between nodes in this case), it’s important to clearly define the scope and meaning of the interface. Here are a few ways to improve this PR:

The type currently used (std_srvs::srv::SetBool) doesn’t convey meaningful information, making it hard to understand its function. This is why std_msgs is deprecated in ROS2. It’s better to create specific types for specific purposes.
The service name (adjust_common_param) is unclear. Terms like "common" and "adjust" are vague (and there is no README to explain). Since this command updates acceleration behavior constraints, a clearer name like enable_aggressive_mode or use_strong_acceleration_params would be better, especially for an OSS project. (slow_driving is a good example of a clear name).
Using a Bool for this operation limits future extensibility. If there might be a need to change acceleration behavior in steps in the future, consider introducing modes or an interface that allows direct control of acceleration and deceleration. However, extensibility should be balanced with the scope of the interface.

I leave it to you to decide how much to address these points in this PR (at least I want to have a README though), but please keep them in mind. Autoware.ai had many interfaces with unclear and vague names, making maintenance very difficult.

It would be closed. Would make a PR once the functions are arranged in proper architecture.


mesh_demo

This is a simple application demonstrating a nRF52840_PDK based #BluetoothMesh node.
Root element has following Models:

Generic OnOff Server
Generic OnOff Client
Generic Level Server
Generic Level Client

We could provision & configure it using following mentioned options:

BlueZ #meshctl daemon
#nRFMesh iOS App
Silicon Labs Bluetooth Mesh App

Codecov Report

Merging #8101 into master will decrease coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #8101      +/-   ##
==========================================
- Coverage   64.55%   64.55%   -0.01%
==========================================
  Files         420      420
  Lines       40141    40141
  Branches     6763     6763
==========================================
- Hits        25913    25912       -1
  Misses      11106    11106
- Partials     3122     3123       +1

Impacted Files
Coverage Δ

boards/posix/native_posix/timer_model.c
98.21% <0%> (-1.79%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 43553da...fa115f0. Read the comment docs.

@dbkinder I've make suggested changes.


Good to have "scroll to top" button

For longer posts, it's always a best UX to have "Scroll to top" button.

I would like to work on this, if the issue is marked as valid.

+1

@bkeepers  What do you think ?

I don't feel strongly either way. If someone submits a PR that is well designed an subtle, we'd consider merging it. I'm going to close this out in the mean time since this isn't something we're actively seeking, but feel free to open a PR.

@bkeepers Cool! Will work on it and send a PR.


[RTM] ENH: Use --template flag to specify normalization target

This PR separates the normalization directive (--output-space template) from the specification of a normalization target via --template <TEMPLATE>.
Currently only MNI152NLin2009cAsym is supported, but this lays the groundwork for additional targets with minimally intrusive modifications.
See discussion in #487.
Depends on poldracklab/niworkflows#158.

Updated the help string. Want to make sure this looks okay in the docs before merging.

Fancy docs:

Could you rebase/merge master?

Rebased.


Issue in Calculator project

Describe the bug
It is taking multiple operators
To Reproduce
Steps to reproduce the behavior:

Go to 'Front-End-Projects Repository'
Click on 'Projects'
Scroll down to 'Calculator' and then run it.
Type some digits and put operator it takes Multiple operators as input.
See error

Expected behavior
It should take only 1 Arithmatic operation after we add a number.
Screenshots

Desktop (please complete the following information):

OS: [IOS]
Browser [chrome]

Name - Abhishant Padam
SSOC Participant

Please Assign this issue to me. i have solution for this issue and want to update this issue.

please assigned me this issue

Please assign me this issue , I will work  to resolve this issue.

I can solve this issue and make it as a proper calculator by taking only one operator . Please assign it to me.

Go ahead

Okk sir
On Fri, Jun 2, 2023, 6:54 PM Tushar Kesarwani @.***>
wrote:

Go ahead
—
Reply to this email directly, view it on GitHub
https://github.com/TusharKesarwani/Front-End-Projects/issues/783#issuecomment-1573730230,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AXO4H7RF7Z2FOR3VX3QKG3LXJHSQLANCNFSM6AAAAAAYWVMBVM
.
You are receiving this because you commented.Message ID:
@.***>

Hello Sir i have send the pull request to you, but i want to ask how it will get me score in quine.sh because it is not listed there. Please list this issue there. and then merge the pull request.


Create the "Join game" function

Description

The join game function should be added to game actions
The function should allow a player to join a pending game using the game ID.
It should take in the game Id and the player color and add the player's username to the game state

Action Items

Create the join game function
Create the corresponding test cases for the join game function

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
Hello , i am a frontend and blockchain developer , with a strong background in Next.js, Typescript,Javascript,React,and cario.and i am exicted to contribute my skills to this project . i am avaliable to work . please assign me
How I plan on tackling this issue

Add joinGame to gameActions:

Take gameId,  playerColor , and add the player to the game state.

Write tests:

Test successful join and edge cases (e.g., invalid gameId, taken color).

Hello can i be assigned this issue, thank you

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
I am fullstack blockchain developer and I have experience in Javascript ,Typescript,React, Go, Rust,Move.
How I plan on tackling this issue

Create a join_game function in game actions
The function take in the game Id and the player color and add the player's username to the game state.
Check if the Player color is not taken and game is in pending.

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
I am Om Santoshwar,
Final year btech UG at IIT Dhanbad,
i have a strong background in web development and blockchain development particularly in Ethereum and Starknet with 3 years of software development experience.
My Technical Skills-
Languages: Typescript, Javascript, Solidity, Rust, Cairo, C++
Frameworks and tools: Scaffold-eth/Stark, Nextjs, MERN, Ethersjs, Hardhat, Foundry, Openzeppelin contracts, Defi, AWS
Experience-
Participated in EthGlobal and other blockchain hackathons
Internships as Blockchain and Fullstack web developer
How I plan on tackling this issue
i can see, cuurently the errors are handled using assert and panic in various files,
i have to change all the error handling from assert and panic to custom Error like using
mod Errors {
pub const NULL_REWARDS: felt252 = 'Reward amount must be > 0';
pub const NOT_ENOUGH_REWARDS: felt252 = 'Reward amount must be > balance';
}

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
i'm a block chain dev and would love to work on this
How I plan on tackling this issue
Function Requirements:
Allow a player to join a pending game using the game ID.
Accept the game ID and player color.
Add the player's username to the game state.
Action Items:
Implement the Join Game Function:
Create the function that handles joining a game.
Develop Test Cases:
Write corresponding test cases to ensure the functionality works correctly.

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
Hello @princeibs I'm a frontend and a blockchain developer and this is something i can work. I did love to be assigned
How I plan on tackling this issue
Here is how I plan to approach it:

I will add the function to game actions, taking the game ID and player color, validate if the game is pending, and update the game state with the player's username and color
I will modify the game state to reflect the player's addition, ensuring everything is handled efficiently
I will ensure that edge cases like invalid game IDs or a full game are managed gracefully with proper error handling
I will write unit tests to cover different scenarios, including successful joins and various edge cases

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
My name is Collins Ikechukwu. I'm a full stack blockchain developer developer.
How I plan on tackling this issue
Step 1: Understand the Requirements
The join game function will:
    Allow a player to join a pending game using the game ID.
    Accept the game ID and the player color as parameters.
    Add the player's username to the game state.

Step 2: Implement the Join Game Function
Define the Function:
    In the gameActions module, create a new function named joinGame.
    This function should accept two parameters: gameId and playerColor.

Step 3: Create Corresponding Test Cases
Set Up Test Cases:
Create test cases for the joinGame function.
Step 4: Run the Tests

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
I am a Full Stack Developer with extensive experience in blockchain development, specializing in Next.js, TypeScript, Node.js, and Rust. With over 18 contributions across projects in the OnlyDust ecosystem, I’ve developed a strong proficiency in delivering high-quality solutions and tackling complex issues under tight deadlines. My experience spans frontend, backend, smart contract development, and a deep understanding of optimizing and maintaining scalable codebases.
How I plan on tackling this issue
First, I’d add the join game function to the game actions. This function will let players join a pending game by using the game ID. It will take the game ID and the player’s color and add the player’s username to the game state. Once I have that working, I’ll write some test cases to make sure everything works well and handles different situations.
I expect to complete this task in about 2 days. On the first day, I’ll focus on building the join game function and making sure it fits with the other game actions. On the second day, I’ll create and run the test cases to confirm that the function works correctly in various scenarios.

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
Boss IBS please let me handle this issue.

Thanks @princeibs


Nested table becomes unsortable upon sort of outer table

I modified an example plunker to illustrate the issue: http://plnkr.co/edit/SAQWCzSZBsO6gyZxTlDe?p=preview
Basically, if you have an ngTable inside of another ngTable and you make them both sortable, the inner table is only sortable up until the point you manually re-sort the outer table.
I named the fields differently just to verify it wasn't somehow an issue with them having the same name.

This might already be fixed. The problem is the plunker is referencing old version of ng-table.
I've asked the project owner (@esvit) to provide some guidance on how collaborators can fix this (#550).


how do i retrain net after quantization?

i had used tensorflow tool, quantization_graph.py, to quantize my graph successfully. how do i retrain this net after quantization? since the tool requires using freeze_graph.py to convert variables in graph to constant.
BTW, can i set up my graph using quantize ops, and train from the scratch? if can, is there any example?

This question is better asked on  StackOverflow since it is not a  bug or feature request. There is also a larger community that reads questions there. Thanks!


Invalid Date responded  at Specific Date

Dear Behrang;
I am using this lib for three months and I did not see this problem till know.
Converting date works fine but at specific date it returns Invalid date; I am using this code at api, here is my code:
var moment = require('moment');
var momentJalali = require('moment-jalaali');

  .post(function (req, res) {

    var jFormat = "jYYYY-jM-jD HH:mm:ss z";
    var format = "YYYY-M-D HH:mm:ss z";
    console.log("pure : " + req.body.date);

    var date = moment(req.body.date).tz('UTC').format(format);
    console.log("moment : " + date);

    date = momentJalali(date.toString(), jFormat).format(format);

    console.log("momentJalali : " + date");
}

Output:

pure : 1396-02-30T00:00:00.00+04:30
moment : Invalid date
momentJalali : Invalid date

pure : 1396-02-29T00:00:00.00+04:30
moment : 1396-2-28 19:30:00 UTC
momentJalali : 2017-5-18 19:30:00

The problem is 30th Ordibehesht (the second month)
I know the moment is returning Invalid date and the issue is on that library but because of my input in Jalali format I prefer to ask it here  and hope you can find the solution.

Oh my god, I made a big mistake; I am trying to convert a date to February month which has maximum 29 days!
The Invalid result is my fault; I need to convert date to Gregorian then apply time zone, but I don't know how can I do that.

I use this code to fix my problem:
   var date = momentJalali(req.body.date, jFormat).tz('UTC').format(format);

Ok, seems to me that everything is fine. Can we close this?


[BUG]: App Published Field for abandoned apps

Describe the bug
The Flow fails if the abandoned App (no owner) has en empty LastPublishedTime because of the empty date inserted to the CDS.
DateTime is less than minumum value supported by CrmDateTime. Actual value: 01/01/0001 00:00:00, Minimum value supported: 01/01/1753 00:00:00
Component (please tell us which flow or app you are experiencing issues with):

Core Solution
1.70 Version
Admin | Sync Template v2 (Apps)

To Reproduce
Have an orphaned app with no published date
Run the Admin | Sync Template v2 (Apps) Flow
Expected behavior
The action shouldnt fail.
Proposed solution
Use the following formula into the App Published field of the Upsert App record (abandoned app) action
@{if(empty(items('Apply_to_each_App')?['properties']?['lastPublishTime']), null, items('Apply_to_each_App')?['properties']?['lastPublishTime'])}

Looks like the Upsert action in CoE doesn't accept null values....

I believe apps are now published automatically now and so this should not occur in the future.
Is this an old app? Just one of them?
Rather than complicating the flow further I'm wondering if we can just clean this up in your tenant.

Good to know. Is that true even for model driven apps ?
I'm deploying CoE on a 2+ years old tenant so yes errors app are all from 2017.

I have updated the flow to mark as Now if no published date exists. Will close this when we release with that fix.
Thanks for using CoE!

This has been resolved in the new version of the toolkit released today: https://aka.ms/CoEStarterKitDownload
PLEASE NOTE: In order to receive updates, you now have to remove all unmanaged layers from any apps/flows you have created in the past. Otherwise you will not see the changes for the app/flow that maintains its unmanaged layers.
For more details on what this looks like, please view installing updates
Thanks for using CoE, and helping make it great with your feedback.