”Carașova”, ”Iabalcea”, ”Nermed” are listed in the drop-down menu

Description:
When user writes ”Carașova”, ”Iabalcea”, ”Nermed” the locations appear in the drop-down menu next to the comune and the county witch is a part according to the law.
Precondition:
The website is up an running.

Step 1
Write in the search bar "Carașova"

Expected results
The location appears in the drop-down menu as "Carașova, Caraș-Severin(Carașova)".

Step 2
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 3
Write in the search bar "Iabalcea"

Expected results
The location appears in the drop-down menu as "Iabalcea, Caraș-Severin(Carașova)".

Step 4
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 5
Write in the search bar "Nermed"

Expected results
The location appears in the drop-down menu as "Nermed, Caraș-Severin(Carașova)".


network similarity - removed parameters (#219)

Update network-similarity.md

V2

V3

V4

V5

Docs Build status updates of commit 24fdd81:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

academic-services/graph/language-similarity-computesimilarity.md
:white_check_mark:Succeeded

academic-services/graph/language-similarity-constructor.md
:white_check_mark:Succeeded

academic-services/graph/language-similarity-gettopfieldsofstudy.md
:white_check_mark:Succeeded

academic-services/graph/media/create-hdinsight-select.png
:white_check_mark:Succeeded

academic-services/graph/media/create-spark-cluster-1.png
:white_check_mark:Succeeded

academic-services/graph/media/create-spark-cluster-2.png
:white_check_mark:Succeeded

academic-services/graph/media/create-spark-cluster-3.png
:white_check_mark:Succeeded

academic-services/graph/media/create-spark-cluster-4.png
:white_check_mark:Succeeded

academic-services/graph/media/network-similarity/databricks-get-top-entities.png
:white_check_mark:Succeeded

academic-services/graph/media/network-similarity/folder.png
:white_check_mark:Succeeded

academic-services/graph/media/network-similarity/usql-get-top-entities.png
:white_check_mark:Succeeded

academic-services/graph/media/network-similarity/usql-top-entities-detail.png
:white_check_mark:Succeeded

academic-services/graph/media/samples-login-hdinsight.png
:white_check_mark:Succeeded

academic-services/graph/media/samples-run-pyspark-script.png
:white_check_mark:Succeeded

academic-services/graph/network-similarity-databricks-constructor.md
:white_check_mark:Succeeded

academic-services/graph/network-similarity-databricks-getsimilarity.md
:white_check_mark:Succeeded

academic-services/graph/network-similarity-databricks-gettopentities.md
:white_check_mark:Succeeded

academic-services/graph/network-similarity-usql-getsimilarity.md
:white_check_mark:Succeeded

academic-services/graph/network-similarity-usql-gettopentities.md
:white_check_mark:Succeeded

academic-services/graph/network-similarity.md
:white_check_mark:Succeeded

academic-services/graph/samples-usql-network-similarity.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 docs.microsoft.com contributor guidesPost your question in the Docs support channel


Updated documentation Specifying types for GradingPrimary attributes #1640

Updated Documentation: Specify Types for GradingPrimary Attributes
Description:
This pull request updates the documentation for the GradingPrimary class in OpenColorIO to specify the expected types for its attributes, enhancing clarity for developers mentioned in the issue #1640
Changes Made:
Added type specifications for the following attributes:

brightness: GradingRGBM
clampBlack: float
clampWhite: float
contrast: GradingRGBM
exposure: GradingRGBM
gain: GradingRGBM
gamma: GradingRGBM
lift: GradingRGBM
offset: GradingRGBM
pivot: float
saturation: float

While I was running initial tests mentioned in the issue, it did not mention pivotWhite and pivotBlack, which is why they were not included in my first response. However, considering your feedback, I think it is reasonable to assume that these properties also follow the pattern observed for similar properties like pivot. If that's not the case, please let me know.


Build tests in a single binary

Fixes #354
I think that tests structure can be reorganized to avoid this workaround:
Tests data files are copied to build directory to ease access for tests. These files may be large (e.g. mem_trace.txt is ~11 MiB), so keeping them in a fixed location (such as simulator/tests/) can let us avoid unnecessary copying.

so keeping them in a fixed location (such as simulator/tests/) can let us avoid unnecessary copying.

Sounds good. The actual problem is not copying, but files reaching out of Git control if CMake is invoked in a wrong place — I've seen it in several previous pull requests and it is annoying.

I think TESTS variable should be moved from CMakeLists.txt to tests/CMakeLists.txt .

Seems that CMake 3.9 doesn't support GoogleTest module, so I'll try to use add_test(). However, it's not flexible.

Looks like some file was not added to git commit.
[ 90%] Linking CXX executable tests
CMake Error: Error processing file: /Users/travis/build/MIPT-ILab/mipt-mips/simulator/tests/GoogleTestAddTests.cmake
make[2]: *** [tests] Error 1
make[2]: *** Deleting file `tests'
make[1]: *** [CMakeFiles/tests.dir/all] Error 2
make: *** [all] Error 2

Seems that CMake 3.9 doesn't support GoogleTest module

Do I understand correctly the module is needed to get list of available tests?
If yes, we probably do not need it much, as we run all the tests, no exceptions.

This module registers tests in CTest via GTest interface. Not a must-have feature, but without it CTest traits all test as a single one.
Looks like this conditional test registering works fine.

Updating Travis CMake to 3.10 would be better.

You may open a ticket to Travis guys, actually there was one: https://github.com/travis-ci/travis-ci/issues/7437.
However, they are not very responsive for C and C++ tools, default versions of GCC, Clang, Boost etc. are obsolete...


⚠ ClamAV has degraded performance

In 11bf091, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 167 ms

Resolved: ClamAV performance has improved in 43b0d58.


uninstalled homebridge, now I can't get it to install again

I uninstalled (had to manually delete some folders because I couldn't get a clean uninstall/remove) homebridge because it was giving me different results when running 'homebridge' vs 'sudo homebridge'.  now I can't get it to install again.
Versions

pi@retropie:~ $ homebridge --version
-bash: homebridge: command not found
pi@retropie:~ $ node -v
v10.5.0

OS:         Linux 4.9.35-v7+ armv7l GNU/Linux (raspberry pi 3)

any help greatly appreciated.
thanks!

What happens when you try to reinstall?

I ended up reformatting the sd card and was able to get it all back up and running. Thanks!

Hello,
@mreassassin how to uninstall homebridge can you tell me the steps?
Thanks

npm uninstall -g homebridge

@KhaosT Thank you very much


Add support for hexadecimal input

This changes allow the user to insert hexadecimal color codes, as requested on #8 .
I have added an EditText to the ColorPickerDialogFragment which can be activated/deactivated by a new parameter of the fragment.
The hexadecimal input depends on the availability of the alpha slider.
To improve the building of the fragment I've added a Builder to the ColorPickerDialogFragment and deprecated the current way of building the fragment, although it would still work.
I've taken care of backward compatibility so that user's of the previous version of the library will keep their behaviour when updating.

may i add this to my  repository?i have forked this.

Definitely, feel free to do it

thankyou,i will commit to my repository later.but i notice when click show activity,hex input don't appear,it is my mistake or you didn't do it ?


Add Python formatting with Ruff

I don't see a ruff config file in the PR. Shouldn't we add your config?

Make sure to run the formatter and commit the changed files

Well I want to see the CI fail first.

Shouldn't we add your config?

I think the configuration I suggested before is all configuring the lints for ruff check, for ruff format I think we can just use the defaults and it will work fine. I looked through the list of ruff format configuration options and none of them look that interesting to me.

I think I'll add ruff linting in a separate PR.

PEP 8 recommends 4 spaces for Python, so that's my personal preference

Commenting just in case: Make sure to merge this PR via "Merge" and not "Squash". Otherwise, .git-blame-ignore-revs will not work properly.

I wish it were possible to disable squash merge ahead of time on a particular PR, I have a tendency to accidentally squash merge patch release PRs and things like that.

Yeah, same here.


Add Carthage support

Marked Xcode scheme as shared to support Carthage. I think a new tag will need to be created too - see here.
Fixes this error when trying to use SwiftMoment with Carthage:
Project "SwiftMoment.xcodeproj" has no shared schemes

Thanks @chrissloey !

Pretty cool @akosma  can you push a new git tag
so we can use
github "akosma/SwiftMoment" == x.x.x
instead of
github "akosma/SwiftMoment" "95bd8c2acfb20e51e1fe4862ac53c49a0cad11e8"
Thanks for maintaining this cool project!

Done! Tag 0.1.1 is up.
Thanks for the support :)


SPO Daemonset values are not configurable

What happened:
The daemonset CRD is correctly generated in the makefile during a kustomize build targeting the helm folder
$(BUILD_DIR)/kustomize build deploy/base-crds -o deploy/helm/crds/crds.yaml
https://github.com/kubernetes-sigs/security-profiles-operator/blob/main/Makefile#L182
Then at runtime this daemonset should be generated based on the chart values.yaml to install profiles on the mounted node.
The issue is here, since the daemonset seems to be generated always from static values, ignoring namespace changes, dnsNames changes (#1591 ) taints, tolerations etc...
We have nodes tolerations and taints so we need to schedule only on specific nodes, this is blocking daemonset pods to spawn, which is critical for the basic operation.
What you expected to happen:
SPOD whould have same values as the deployment manager, taking them from the chart values.
How to reproduce it (as minimally and precisely as possible):
Install the chart on a cluster with taints.
Pods won't be able to start if not manually patching the daemonset with a toleration.
After any pod deletion or daemonset restart the pods won't be scheduled again sine they will be reset.
Anything else we need to know?:
Environment:
Any Kubernetes supporting taints
@stephen-fox maybe?

Still relevant.

@hans-fischer thank you for the ping on this issue. Do you consider to contribute the required changes to fix that problem?

I'm afraid I don't have the right skills to work on go-lang code. I have written one small projekt but never understood some basic go-lang prinziples.


No Callbacks for Validation Batch Step - How To Get Progress of Validation?

🚀 Feature
The Callbacks has two functions on_batch_start and on_batch_end. The documentation and code execution shows that these are only called for training batches, not validaton (or test). I am building a Callback for my own logging/dashboarding via Streamlit and I have a requirement to track the progress of both the train batch steps and validation batch steps during training. I see that there is a validation progress bar in the console during training - how is this implemented (if not via a Callback)?
Current Code
class MyCallback(pl.Callback):
    def on_train_start(self, trainer, pl_module):
        self.train_batch_count = 0
        self.train_batch_total = len(trainer.train_dataloader)

    def on_batch_end(self, train, pl_module):
        self.train_batch_count += 1
        percent_complete = self.train_batch_count / self.train_batch_total
        # display on screen

    def on_epoch_end(self, train, pl_module):
        self.train_batch_count = 0

hello, as you stated you want to have a logger, not a callback, you can write a custom logger...
Moreover, it would be welcome to add Streamlit.io as Lightning loggers, what do you think?

Hi, @Borda, thanks for the reply. I looked over the documentation for Loggers and it will indeed be helpful for my future work. However, looking at LightiningLoggerBase, I don't see anything for capturing the epoch or batch progress for training (i.e. Epoch 1 of 5 or Batch 1 of 200) as I am doing above so that I can use Streamlit's streamlit.progress to render a progress bar of the training iterations.
I do think a Streamlit logger would be an excellent addition to Lightning but I am still in the early exploratory phase of using Streamlit myself and it currently seems like it would require a bit of work to make a useful generic dashboard a la Tensorboard. I'll continue experimenting on my end to see where it goes.

In case this is still relevant to you, we now also have callbacks for validatation and test batches!
See https://pytorch-lightning.readthedocs.io/en/latest/callbacks.html#callback-base

Closing this. As far as i can tell, with the recently introduced new callback methods (validation_batch_start etc) it is not possible to track the progress as you desired.

https://pytorch-lightning.readthedocs.io/en/latest/pytorch_lightning.callbacks.base.html?highlight=callback#callback-base

https://pytorch-lightning.readthedocs.io/en/latest/callbacks.html#callback-base

good work!


It hungs when run in mac M2 chip env.

Hi, @SlashScreen
Sorry for disturbing, but each time I run this proj in my godot editor, it will hung for few minutes until I cancel it. And I do not see any alert information in the console. So, I wonder how can I debug this proj and locate more useful infomation for this issue?
my dev environment:
godot 4.0.3
mac air with M2 chip.

The chip should not matter, since it's written in GDScript.
The first thing I noticed is that your version is 4.0.3; Skelerealms relies on static variables in gdscript, so only 4.1+ is supported.
Also, I have pushed some changes I have made in the mast few months to this repository just now, so you can use the new version if you wish; I believe it fixes a few issues I had with loading.

The chip should not matter, since it's written in GDScript. The first thing I noticed is that your version is 4.0.3; Skelerealms relies on static variables in gdscript, so only 4.1+ is supported. Also, I have pushed some changes I have made in the mast few months to this repository just now, so you can use the new version if you wish; I believe it fixes a few issues I had with loading.

Thanks for you reply, I upgrade my godot and it works well now :)


allow prisma v3

Prisma released version 3 a couple days ago so it would be great to allow users to install it. The blocker seems to be @next-auth/prisma-legacy-adapter, which is a dependency of next-auth. Looking at the breaking changes there, changes to the package should be none or minimal as they seem to be mostly on the user side. Tests will probably need updating if the devDependencies version is updated though.
If the legacy adapter is no longer being maintained, then I suggest allowing prisma v3 in its peerDependencies anyway, at least until next-auth@4 is released.

I don't have plans for doing any changes for the legacy adapter. If you really must use it and the issue is npm 7, have  a ready here how to make it work anyway https://github.blog/2021-02-02-npm-7-is-now-generally-available/#peer-dependencies
I haven't checked what Prisma 3 breaks yet, but I'm fairly confident that the new adapter wouldn't need changes:
https://github.com/nextauthjs/adapters/blob/next/packages/prisma/src/index.ts
I'm happy to extend in the peer dependency version on that one, against the next branch.

The new adapter already allows version 3:
https://github.com/nextauthjs/adapters/blob/fae5c50d3accac2c4b380f456ef5ffe96402df6b/packages/prisma/package.json#L34
I agree, doesn't look like any changes are necessary. Installing with force is not ideal, but it's an acceptable temporary solution.

If the new adapter already works correctly, I am inclined to close this. As said, there are no plans to do changes to the legacy adapter, as it is going to be totally removed soon.

Just to clarify: I'm actually using the new adapter, but since next-auth depends on the legacy adapter, the peerDependencies there block the install. But that's fine, force installing is just a minor inconvenience and can wait until v4.

I see. v4 won't have any direct dependencies on any adapters and this problem will just go away!

@sachinraja I assume this is the error that you were getting
Could not resolve dependency:
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>
I installed with --force as well, but I wasn't entirely certain that was the correct course of action at this point.

That doesn't look right. The error should be for legacy adapter, not the next-auth package itself. You may want to run npm i next-auth@latest.

Thanks @sachinraja.  My issue is indeed with the new adapter.  With<EMAIL_ADDRESS>and<EMAIL_ADDRESS>I get the following error trying to run npm install.  I'll keep looking for a solution.
npm ERR! Could not resolve dependency:
npm ERR! peer next-auth@">=4" from<EMAIL_ADDRESS>

>=4 does not match prerelease tags (see npm docs). You will have to force install if you want to use the 4.0.0-beta.

🤦 I didn't realize that.  It builds fine using --force.  Thank you so much!!!  I've had a difficult time finding the right version combinations, but it all seems to be working with
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>

again, apologies for the hard time. 😬 when v4 goes stable, everything should/will be much easier.

No apologies necessary!! I could never build anything without great people writing awesome libraries like this.


Failed to obtain dependence path of CTKTesting

when I compile the top CMakeLists.txt, Occuring a error where  CMake Error at CMake/ctkMacroValidBuildOptions.cmake:138(message)
I want to know how to address this question ,If you have time to tackle it ,It' a very great help for me,
thanks  to you

What is the error message exactly?

the error Note is :"/home/linux/Desktop/CTK-master/CMake/ctkMacroValidateBuildOptions.cmake:138: error: Failed to obtain dependence path of CTKTesting. 2 /tmp/QtCreator-lUEbbs/qtc-cmake-XXlFjAmZ /tmp/QtCreator-lUEbbs/qtc-cmake-XXlFjAmZ/Utilities/DGraph/DGraph: 1: /tmp/QtCreator-lUEbbs/qtc-cmake-XXlFjAmZ/Utilities/DGraph/DGraph: Syntax error: word unexpected (expecting ")") CMakeLists.txt:864 (ctkMacroValidateBuildOptions)"
and as following this  shotcuts
[cid:4a9d02c0-dd45-4ba7-9b4c-9a706dac8857]

发件人: Andras Lasso<EMAIL_ADDRESS>发送时间: 2019年11月4日 9:25
收件人: commontk/CTK<EMAIL_ADDRESS>抄送: jupitermyself<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>主题: Re: [commontk/CTK] Failed to obtain dependence path of CTKTesting (#891)
What is the error message exactly?
―
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/commontk/CTK/issues/891?email_source=notifications&email_token=AJAE7FLSHVLR27T55JINR43QR5TXBA5CNFSM4JIB6INKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEC6CJ2Q#issuecomment-549201130, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AJAE7FLQVL4K6XKB7K7GB23QR5TXBANCNFSM4JIB6INA.

msvc 2015 x86, lastest  master branch source code.

Plz help!!

Has the problem been solved？

I've encountered this problem once because the DGraph executable in the build directory did not run correctly.
I intentionally omitted MinGW's bin directory from the PATH on my Windows machine and manually set the CMAKE_C_COMPILER and CMAKE_CXX_COMPILER variables, which caused DGraph to not find the libstdc++ library.
Hope this helps.


Fix deprecation of .URL in Paginator in theme

It looks like the pagination module in Hugo has deprecated the .URL directive, and thus you currently get warnings like this on the latest version:

WARN 2019/09/30 21:04:09 Page's .URL is deprecated and will be removed in a future release. Use .Permalink or .RelPermalink. If what you want is the front matter URL value, use .Params.url.

I tested this out on my own site locally and verified that changing these references to .RelPermalink alleviates the warnings. I'm unsure of modifications to card.page.html, but all other files exist directly in {{ range .Paginator.Pages }} or similar blocks, which are directly relevant.
So, this PR should fix the deprecation warning generated by using .URL since it's deprecated.

@hakusaro Thank you for the PR!
The fix looks good!

It seems there's other few .URL not covered in header.html, but I'll just fix them later on. :)

My bad, there seemed to be some .URL shouldn't change. Fixed in #32

Thanks!! I wasn't sure which ones were/weren't necessary but I really appreciate the time you've taken to look into this! :)
Lucas Nicodemus
http://keybase.io/xn
On Wed, Oct 09, 2019 at 12:14 AM, Qiushi Pan <<EMAIL_ADDRESS>> wrote:

My bad, there seemed to be some .URL shouldn't change. Fixed in #32 (
https://github.com/qqhann/hugo-primer/pull/32 )
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub (
https://github.com/qqhann/hugo-primer/pull/31?email_source=notifications&email_token=AAECBJZOXIUMUNJJPHWV2P3QNWAE5A5CNFSM4I6LUZW2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAW4Q4Q#issuecomment-539871346
) , or mute the thread (
https://github.com/notifications/unsubscribe-auth/AAECBJ37SR7ISBTR2VAKU7TQNWAE5ANCNFSM4I6LUZWQ
).


[Mathematical functions] Implemented sinh function

Project: https://github.com/orgs/apache/projects/237/views/1

implemented the age_sinh() function
added regression tests

Sample Usage:
postgres=# select * from ag_catalog.age_sinh(2);
     age_sinh
-------------------
 3.626860407847019
(1 row)

postgres=# select * from ag_catalog.age_sinh(3);
      age_sinh
--------------------
 10.017874927409903
(1 row)

postgres=#

Closing this. The PR has been made in the correct branch here: https://github.com/AgeDB-Enterprise/agedb/pull/96


It's a great project but difficult to use

As you say how to use:
Installation
Manually
Download the latest tag and drag the PINRemoteImage folder into your Xcode project.
Install the docs by double clicking the .docset file under docs/, or view them online at cocoadocs.org
First,i tried clone in desktop directly,but find the Contents is so complex that i do not know  how to 'drag the PINRemoteImage folder into your Xcode project'  .
Then,i use 'pod search PINRemoteImage‘ code,but  it shows:
[!] Unable to find a pod with name matching `PINRemoteImage'
I love this project but i really can not find how to put it in my Xcode project. I guess you should learn the SDWebImage's usage.Thank you!
My English is so pool,sorry  for that!

Hi @lqcjdx when I run the command
pod search PINRemoteImage

it returns:
-> PINRemoteImage (1.2.1)
   A thread safe, performant, feature rich image fetcher
   pod 'PINRemoteImage', '~> 1.2.1'
   - Homepage: https://github.com/pinterest/PINRemoteImage
   - Source:   https://github.com/pinterest/PINRemoteImage.git
   - Versions: 1.2.1, 1.2, 1.1.2, 1.0 [master repo]
   - Subspecs:
     - PINRemoteImage/Core (1.2.1)
     - PINRemoteImage/FLAnimatedImage (1.2.1)

Maybe there's something wrong with your cocoapods install? You can try upgrading cocoapods with:
sudo gem install cocoapods

Also, the README has been updated with a bit more clarity on how to install. Hopefully this helps!


fix(webview): Prevent double loads of pages, and fixes back button

Description
Fixes an issue we've had for a while with double WebView loading and broken back button states.
What this does is immediately prevents the subsequent webview link from loading if it meets certain conditions, and will jump backwards in the stack. By the time the user has it the actual back button, the webview has stabilized at the place where it first departed from to launch the native view.
cc @artsy/mobile-platform
https://user-images.githubusercontent.com/236943/232156389-00fd5820-157e-4195-b0f3-971822b158a0.mp4

PR Checklist

[x] I have tested my changes on iOS and Android.
[x] I hid my changes behind a feature flag, or they don't need one.
[x] I have included screenshots or videos, or I have not changed the UI.
[x] I have added tests, or my changes don't require any.
[x] I added an app state migration, or my changes do not require one.
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[x] I have added a changelog entry below, or my changes do not require one.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

Cross-platform user-facing changes

iOS user-facing changes

Android user-facing changes

Dev changes

Need help with something? Have a look at our docs, or get in touch with us.

@brainbicycle - there are likely some missed edge-cases here so if you wouldn't mind pulling down, but i think this points us in the right direction.

This looks good to me. It doesn't work with the pageable artwork flag on, but that's not a priority for this release, so I would be in favour of merging this and making a ticket to fix that.


ligo: 0.55.0 -> 0.57.0

Description of changes

https://gitlab.com/ligolang/ligo/-/releases/0.57.0
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[x] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 205005 run on aarch64-darwin 1

1 package built:

ligo

Please mark broken on aarch64-linux and darwin.

nix run github:ulrikstrid/nixpkgs/ligo--0_57#ligo -- --help works on my m1 and old intel based mac.
So should platforms = [ "x86_64-linux" "aarch64-darwin" "x86_64-darwin" ]; be a good change?
@SuperSandro2000

So should platforms = [ "x86_64-linux" "aarch64-darwin" ]; be a good change?

I assume this is easily fixable so I would suggest to mark it broken for that platform instead.

The failure on x86_64-darwin is actually in ocamlPackages.class_group_vdf, should that be marked broken instead?

yes, please

@SuperSandro2000 is this now correct?

I'm not sure what the criteria is for backporting stuff @vbgl, but I guess it might be a good idea :+1:


Create how-java-works.md [Completed hacktober fest issue]

okay

Add the post im  src/content/posts directory, then update your username in src/util/authors.ts file

Chcek out, completed the PR

lol i merged this without checking exactly while eating


Updater deleted uninstall.exe

Binary Ninja Version: 1.0.776 Personal, 6573250f
Platform: Windows 10
Application can no longer be uninstalled. The software has to be "re-installed" and then uninstalled.
Happens when binaryNinjaUpdater.exe runs

Fixed in build 1341


update docs/Contributing.md #782

update Contributing, adding some instructions #782

This change is

In README.md I just added  * Involvement: [Contribute](./docs/Contributing.md)

Great! about the section hacking, does it need change?

:+1:  thanks


Abhay nath001 patch 1

See the changes.
https://github.com/shrawani21/gamer_21/assets/103759014/65eda18c-aee8-4246-8967-1e726390bf7b

please give the GSSOC label for this work


Fix pipeline steps default on update

The refactor in #474 didn't account for updates on pipelines that previously relied on the default setting of steps - this ensures it's always set if not otherwise provided.

Thanks for contributing this @drcapulet 👍 I've run the tests and they pass and will get the team to check this out further to get it merged in

@drcapulet I think these changes are correct but we found there was a larger problem with the way steps and pipeline templates interact. As a result, I've pulled these changes into #539 which resolves it all in one go. Thanks for you contribution!


Update to Cadence v1.0.0-preview.13

Description
Automatically update to:

onflow/cadence v1.0.0-preview.13
onflow/flow-go-sdk v1.0.0-preview.11
onflow/flow-go 6c1b120ed2ac

Realized there is another module, integration, that also needs to get updated. Will open a new PR


And it's black screen

Hi, any platform and configuration info? android version,emulator or real device,and react-native version.

Sorry,I'm using the genymotion simulator, react native:0.50.4 and 0.49.2,At present, all devices appear black screen

Then have you follow all steps in README?
It seems that there are some errors in the android-building.check whether Gradle builds or other step cause errors and feel free to paste it here.

@Obooman  Yes, I follow the README operation, the content area or the black screen

Can you tell me more info about this?I have tested this project and it works well on my platform, you may offer me the android error log or react-native build service log, sorry but I can't tell any solution without more information.

I also have that problems with RN: "0.50.4". Please check it. thanks

Hi, sr for my mistake, add style with flex :1, will resolve this

good job @matsatit  cc @TrustTheBoy is this also your problem?

I'm going to close this issue, feel free to reopen it if this issue still exists.


add support for loading resources via NativeContext

Motivation
It is often necessary for Move native functions implemented in Rust to read resources. Currently, there is no easy way to do this in a native function because the load_resource method inside the DataStore in a NativeContext is not accessible.
This PR makes it accessible, together with a load_type method for converting a TypeTag to a Type, which is needed as an argument of load_resource.
Have you read the Contributing Guidelines on pull requests?
Yes!
Test Plan
Just exporting some existing APIs. No testing.

Generally, I'd say we are better off putting the chain_id in the NativeTransactionContext of Aptos. This will be lesser code changes.

I guess we should close this PR, then?


vim: clear search highlighting when done

for other tabs, search results remain highlighted even after clearning in one buffer

fixed in next update


[Feature Request] Add Drag and drop to include image and js files in enclosed  and

VSCode Version: All Versions
OS Version: All Platforms

Feature Desciption

Add Drag and drop to include image and js files in enclosed <img> and <script> tags.

duplicate of #5772


What are pedestal file, transfer function file and adc2pe file and what is the expected format

What are those?
How are they used?
How can one produce them for existing experiments?

I think these are defined only for CHEC right now (is that correct @watsonjj ?) They should at least be documented in the docs/calib directory (but are not right now, as far as I can tell)
To follow what we require for CTA, they should at least be FITS files (probably something readable by astropy.table.Table would be best, but the column definitions should be explicitly written down), but I have no idea what the current format is.

So why are those in a general CalibrationFactory if they are specific for CHEC?

In the current implementation of factories, any traits that exist in one of the products of a factory need to also be included in the factory so that the trait value is propagated.
Those files are required in TargetioR1Calibrator which exists in an external module using ctapipe for analysis (for now). These file paths are supplied to TargetCalib, which is the calibration software for CHEC.
But CHEC is presumably not the only camera that will subtract pedestals, or convert from adc to pe in the r1 calibration. So these traits could be used by other cameras wishing to perform r1 calibration in ctapipe.

Each camera team is responsible for their r1 calibration. What files they need, how they choose to apply the files, and even what format those files exist in depend on their choice.

#489 Has included some extra documentation on these file paths, and R1 calibrators


fix import @pixi/math/src to @pixi/math

Description of change

fix import @pixi/math/src to @pixi/math
Pre-Merge Checklist

[x] Lint process passed (npm run lint)
[x] Tests passed (npm run test)

Codecov Report

Merging #6483 into dev will not change coverage by %.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev    #6483   +/-   ##
=======================================
  Coverage   80.14%   80.14%
=======================================
  Files          57       57
  Lines        2825     2825
=======================================
  Hits         2264     2264
  Misses        561      561

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 dbff69b...0518a54. Read the comment docs.

Thank you!


docs: add forge script

closes: https://github.com/foundry-rs/book/issues/332

Should forge script be under References/forge Commands/Deploy Commands or Utility Commands like forge run ?
forge run should be changed to forge debug I think, maybe address in separate issue

I just noticed that forge script is using multi_wallets.rs
https://github.com/foundry-rs/foundry/blob/b192af49c6e1f3874bc6775cfd969040fddce740/cli/src/opts/multi_wallet.rs#L86
for its wallet options rather than wallet.rs
https://github.com/foundry-rs/foundry/blob/b192af49c6e1f3874bc6775cfd969040fddce740/cli/src/opts/wallet.rs#L52
I will update docs shortly
changes

added src/reference/common/multi-wallet-options.md with plural and different short flag for --froms

Think I got it all

Change forge run to forge debug
All forge script docs
forge script --debug help text in foundry pr: https://github.com/foundry-rs/foundry/pull/1782


add link to make github happy

Github wants this file to exist to confirm the existence of a code of conduct...

going to try a better solution


Retire dormant Fabric maintainers

Retire maintainers that have been inactive for the last 3 months:
Chris Ferris
Note:
"A maintainer removed for inactivity should be restored following a
sustained resumption of contributions and reviews (a month or more)
demonstrating a renewed commitment to the project."
Signed-off-by: David Enyeart<EMAIL_ADDRESS>

The people have spoken, Chris Ferris must come back!


Help with node-monitor and monitor-dashboard

Hi Loren, I'd like to know if you can help me with node-monitor and monitor-dashboard. I need to monitoring a node app, specifically http requests and the node server cluster status (freemem, cpu status) and be able to see this information in monitor-dashboard.
I tried to do this by reading your code, but I can't.
Hope you help me. Thanks!
Ignacio.

Hi Loren,
I have the following code:
var inspectMonitor = new Monitor({
hostName:'<IP_ADDRESS>',
probeClass: 'Inspect',
initParams: {
key: 'global.http_requests',
pollInterval: 10000
}
});
inspectMonitor.on('change', function () {
    var xxx = inspectMonitor.get('value');
    console.log(inspectMonitor.toJSON());
});

inspectMonitor.connect(function (error) {
    console.log('Inspect probe connected.');

    if (error) {
        console.error('Error connecting with the inspect probe: ', error);
        process.exit(1);
    }
});

..and output:
Inspect probe connected.
{ hostName: '<IP_ADDRESS>',
probeClass: 'Inspect',
initParams: { key: 'global.http_requests', pollInterval: 10000 },
id: '',
name: '',
probeName: '',
appName: '',
appInstance: '',
probeId: '4092dcdb-d9dd-47b8-5d00-09bb69f027cd',
writableAttributes: [ 'value' ],
key: 'global.http_requests',
pollInterval: 10000,
cronPattern: '* * * * * *',
value: undefined,
isModel: false }
It seems that "value" is undefined as shown, can you please advise?


v-on:click with target not in the correct element?

Hi,
I have a template like :

    entry 1
    entry 2

and the event.target in action is either the first or second span, never the a.
Using jQuery, I know .target is always the intended (listened) element.
Is this not the case here or is there an issue?

http://blog.bittersweetryan.com/2013/04/a-quick-look-at-etarget-and.html

My bad. I analyzed the event but didn't saw the currentTarget value, hence my question.
Thank you for you quick answer.

Somewhat related. I stumbled upon this thread when I searched why event.target is not the "clicked element", and why vue's event.currentTarget is always null. Turns out its due to how console.log works:
Thus:
console.log(event); // When expanded on browser's console, currentTarget is always null.
However:
console.log(event.currentTarget); // Does contain the element clicked.
Stackoverflow explanation: http://stackoverflow.com/questions/26496176/when-loggin-an-event-object-currenttarget-is-null-but-when-logging-event-curre
So its not a bug in vue but caused by how JS and console.log works.
Just leaving this here for other users who will have the same issue and not waste hours scratching their head. Hope this helps.

I was searching for a solution for catching relatedTarget for not-focusable elements, such as li, p, div, etc. So if you are searching the same and ended up reading this thread too, please consider taking a look at this StackOverflow topic.


Lumina style feature

Feature request: Lumina or similar idea function metadata sharing.
Hopefully this isn't a dupe :-)

a plugin: https://github.com/Boberttt/lumina-binja-improved
omg that's mine! keep in mind that the push function is broken and not that many people use the lumen server. So please keep working on this feature!

WARP, introduced as experimental in 4.2 will be the format which we use to network function "signatures". This issue is now tracking that.


When using dockerize with NPM , build fails due to wrong esbuild platform type

Using NPM with dockerize fails es wrong esbuild platform is being referenced.
#13 2.765 Building your admin UI with development configuration...
#13 3.728 ℹ Compiling Webpack
#13 3.976 HookWebpackError:
#13 3.976 You installed esbuild for another platform than the one you're currently using.
#13 3.976 This won't work because esbuild is written with native code and needs to
#13 3.976 install a platform-specific binary executable.
#13 3.976
#13 3.976 Specifically the "esbuild-darwin-64" package is present but this platform
#13 3.976 needs the "esbuild-linux-64" package instead. People often get into this
#13 3.976 situation by installing esbuild on Windows or macOS and copying "node_modules"
#13 3.976 into a Docker image that runs Linux, or by copying "node_modules" between
#13 3.976 Windows and WSL environments.
#13 3.976
#13 3.976 If you are installing with npm, you can try not copying the "node_modules"
#13 3.976 directory when you copy the files over, and running "npm ci" or "npm install"
#13 3.976 on the destination platform after the copy. Or you could consider using yarn
#13 3.976 instead of npm which has built-in support for installing a package on multiple
#13 3.976 platforms simultaneously.
#13 3.976
#13 3.976 If you are installing with yarn, you can try listing both this platform and the
#13 3.976 other platform in your ".yarnrc.yml" file using the "supportedArchitectures"
#13 3.976 feature: https://yarnpkg.com/configuration/yarnrc/#supportedArchitectures
#13 3.976 Keep in mind that this means multiple copies of esbuild will be present.
#13 3.976
#13 3.976 Another alternative is to use the "esbuild-wasm" package instead, which works
#13 3.976 the same way on all platforms. But it comes with a heavy performance cost and
#13 3.976 can sometimes be 10x slower than the "esbuild" package, so you may also not
#13 3.976 want to do that.
#13 3.976
#13 3.976     at makeWebpackError (/opt/app/node_modules/webpack/lib/HookWebpackError.js:48:9)
#13 3.976     at /opt/app/node_modules/webpack/lib/Compilation.js:3060:12
#13 3.976     at eval (eval at create (/opt/app/node_modules/tapable/lib/HookCodeFactory.js:33:10), :55:1)
#13 3.976     at processTicksAndRejections (node:internal/process/task_queues:96:5)
#13 3.976 -- inner error --

This seems to be an issue with your build environment
IF you are using WSL you need to also have build tools etc to make it work.
Also make sure you are not binding node_modules


Add export configurations to project repository

In order to make it easier for users to build or package this project, would it be possible to add the export.cfg and export_presets.cfg files to this repository?
Godot supports exporting projects directly from the command-line using this syntax: --export <preset> <path>
(The <path> argument overrides the export_path option in export_presets.cfg)
So having those files included in the repository would allow users to clone and export the project automatically, such as through a script

That sounds like a good idea, i'm going to add them soon.
I normally don't check in export configs, because often times they contain sensitive information, but for an open source project like this it's fine.


Automatically adding attribution for DO data to map metadata

As we expand the Data Observatory we are going to getting a lot of data from a lot of different places. For some of the providers of this data, attribution is going to be important. We already have an attribution field in the metadata for datasets, could we add one for maps/dashboards as well which would automatically be populated by the attribution for Data Observatory sources a user uses in analysis. The attribution should probably be shown in a few places but at minimum in the attribution line in leaflet.
@talos is already recoding this in the metadata for each column, we could pull it from there when a user runs an analysis that uses DO data.
@saleiva

👍  My preference would be a new text array field in the map/dashboard metadata, which we can populate with however many attributions are required by the metadata.
There will be many cases where there will be several necessary attributions, and handling them concatenated in a single string would be messy.

Sounds good to me. Adding to the backlog


Java 12.5: Using final with Inheritance

Description
Add audio, documentation, and video regarding the Using final with Inheritance.

Location of File to be added
The files should be added inside the Using final with Inheritance  folder which is inside the Inheritance  folder present in the   Java  main folder.  The documentation file can be in the .md/.py/.ipynb format. Audio should be in .mp3 format and to be submitted through a Google drive link. Video can be in any format and should be submitted through a Google Drive link.
Note:

You are required to comment with \assign CONTENT_TYPE, so that other content types can be created at the same time.
Failing to comment in the above manner will lead to the removal of assignment from the issue even if the bot assigns.
You are required to do a PR within 7 days otherwise you will be unassigned and others will be assigned.
Issues will be assigned on a first come first serve basis.

Domain
Java_Domain
Type of Contribution
Audio, Video, Documentation
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of this project.

/assign documentation

/assign documentation

@AkMo3 My Java Bytecode PR has been merged so i can take up this one? The bot automatically unassigned me

Yes as you still have 5 assigned issues. Please finish them first. If you have merged PR for them, let me know.

Yes as you still have 5 assigned issues. Please finish them first. If you have merged PR for them, let me know.

@AkMo3 Yes, all my 5 Pull requests are merged

\assign documentation

@AbhinandanAdhikari You have been assigned documentation. @ganaaduvva He actually commented so I am assigned him, otherwise you can ask for other comment.


Update monaco 13.x

Backports the monaco editor update to 0.52.2 to 13.0.x, which fixes CVE-2024-45801 and CVE-2024-47875 (see https://github.com/microsoft/monaco-editor/issues/4692 / https://github.com/microsoft/monaco-editor/issues/4738)

We should probably do this for 14.X as well?

Ah makes sense, I forgot we were already at version 15 RC

I will release 13.X today!

Awesome, thanks for the quick release! I made a PR for the update for 14.x


Revert "bcf: Add UART console"

Reverts zephyrproject-rtos/zephyr#64558
The PR breaks the sensor sample, see https://github.com/zephyrproject-rtos/zephyr/pull/64558#issuecomment-1797805291

Hi @yperess. I think it would be better to work on #64693 and #64881 rather than reverting the commit.


resize popup on click and few other features

popups sometimes takes a lot of the screen space, so i added an option to resize them.
that's the main reason i created this pull request
the link to open the image in new view and the size in ko are also good features i think..

I don't know why, although I'm pushing those commits (from a local repository) , github doesn't consider them mine ??

That's strange. What does git log show on your end?
Sorry that I still haven't had time to review and merge but I'll do it soon.


Update _index.md

👷 Deploy Preview for dat4lab processing.

Name
Link

🔨 Latest commit
665ecd3c900550b08633f76a16f5f75cb7b4ff79

🔍 Latest deploy log
https://app.netlify.com/sites/dat4lab/deploys/6536b3606749fd0008e96694


State of the project

This repo was not changed since four years.
What is the state of the project?
I am searching for a way to handle pop-up forms with django :-)

@guettli joinourtalents is no more, so the repo is not being maintained.
feel free to fork it and update to fit the new django versions though.
open source baby!

It would be nice if this is immediately visible. Otherwise people might loose time. Have you the permissions to do so?

to do what exactly?

To exactly that:
To add the status "not being maintained" above the big word "Problem" here https://github.com/joinourtalents/django-popup-forms


Make it possible to ignore unknown formatter error

See issues #48

Thank you for the PR and sorry for the delay. I thought about this a bit and decided it would be simplest to make another version of the format-all-buffer function that never causes an error if the buffer doesn't have a formatter associated with it. That code is now pushed to master.


Clean up transactions older than X days for a given token

allow users to set it
provide a default value
config per token
could probably be added to the t_events table

I don't think we want that.
To the contrary, we want this to be the etherscan for the community token.
Everything should always be there.

This was a good idea back when we wanted to index everything on a single server and USDC was taking all the space.
Now that we are moving to a more decentralized infrastructure, we don't really need it anymore.

Yeah, this changes things.
And there can just be a warning for people who want to index very large active contracts that it will consume a lot of data.
Also, that the initial indexing of transactions might take a few hours to complete.


Open command does not handle path conversion correctly

I don't know if this is intended behaviour:
cd /; open . opens VM root directory
open / opens host root directory

Fixed for the next version. Thanks for reporting!

Fix released in v0.6.0.


Redesign to cdef functions and array.array

In my app I reached +40% performance on writing.
Resolves #17

Hi @izhukov1992 -- I'm no longer at PS so I can't merge (I don't have write access to this repository anymore). I have my own fork that's had some improvements added and is the source for the pypi package now. https://github.com/mikepk/spavro

Hi @mikepk ! I got it. I will try to propagete this MR to your repo as soon as possible.


Clean up all symlinks in venv

Cleans up all symlinks in generated venv. This needs to happen such that remote caching works properly when --remote_download_minimal or --remote_download_toplevel are used.

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

@mattem PTAL.


Import actin coordinates from tomography data and visualize and calculate metrics

Use the data found in https://github.com/RangamaniLabUCSD/actincme (data folder)

[ ] visualize in simularium
[ ] run PCA on all the coordinates
[ ] on a subset of the coordinates (e.g. all unbranched actin filaments)
[ ] put on the same PCA or PACMAP plot as the simulated readdy & cytosim simulations

This issue is the same as this issue our Roam graph. The title also includes a second issue, which is to calculate the filament metrics (non-coplanarity, etc) on the tomography data


black screen after failing to load

Player log 1.txt
Player log 2.txt

Should be fixed in the latest Steam version


Color area support

❔ Question
I couldn't find the Color Area component in the stories. Do you guys plan to release the color components?

Hi @deebov, that is not an immediate component for us and we probably wouldn't be starting it until late in the year. If you're interested in contributing it, we would love to talk about how to do that.

Hey @snowystinger, I am working on a new design system. And a ColorPicker is an important part of that DS. I am working on a ColorPicker component. Would love to build the ColorPicker using something reusable like @react-aria.
I couldn't find enough documentation/guides on how to contribute and create new packages. Do you think you may help with this?

We're in the process of creating many of those docs right now actually. For instance, the Contributing guide and this section in particular https://react-spectrum.adobe.com/contribute.html#feature-requests
As for creating new packages, the easiest way to do it is to run the plop command from package.json.

Superseded by #1118.


[Roots 3] Method of obtaining different soils unclear in guide book

It's really unclear exactly what you need to do. I get the impression now that you hold the bulb in your off-hand and then use the knife on the soil, but I'm not 100% certain.

Yes, that's how it works. Let's make that more clear in the book.

Fixed, now explains how to get them on each page, and runic carving uses the herb directly rather than with a pouch


new post: Announcing sigstore-python 2.0

This blog post announces the (pending) release of sigstore-python 2.0. It's currently dated to 9/29, since that's the expected release date.
CC @di (who I've listed as co-author, in expectation that he'll have feedback/suggested edits 🙂)
CC @sigstore/core-team

Overall LGTM! Would be nice to include a reference to https://github.com/sigstore/gh-action-sigstore-python indicating that it exists and has been updated to use the latest version as well.

Done! I've also added a section highlighting @sethmlarson's work on getting CPython's signatures/docs ready.

:shipit: 🚀

This is ready to go whenever!

It's aliiiiive! :zombie: https://blog.sigstore.dev/announcing-sigstore-python-20/


[DOCS]Update new backend guide to support the latest develop

Description
It was found that the create_new_backend.rst document is outdated and the instructions do not work with the current develop branch.
Solution/Changes

Update usage of scripts to match latest header file changes (.hpp->.hxx) for actual API declarations to be picked up by the scripts.
Add missing generate_ct_templates.py usage.

Test
All script (scripts/*.py) outputs now match the expected output shown in the docs.

I am curious, have you tried to add a dummy backend and compile the files generated by the python scripts?
We went through these instructions when we worked on adding the DFT domain a little while ago and found that using these scripts did not generate files that could be compiled. We ended up copying and adapting the files from an existing domain which was much easier.
I understand the intention of making it easier for anyone to add a backend and I think it could be a good idea if done well. I am concerned that the current instructions may instead waste the time of anyone trying to run them.
I think we should consider removing docs/create_new_backend.rst and the scripts folder, for the following reasons:

Last time we tried the generated files were not compiling and not aligned with the existing domains in oneMKL. This should be verified if we want to keep support for it.
It is common in software engineering to get inspiration from existing code and adapting it for a different purpose. We have found it was easier to copy existing domains or backends rather than starting from scratch.
Even if we were to fix them now the python scripts are not often used or updated. They are more likely to fail or generate outdated file than work at first try.
We have some relatively recent PRs that add new domains (DFT domain PR, SPARSE domain PR) or add new backends to existing domains (cuFFT backend PR, rocFFT PR or cuSPARSE PR). They are a more concrete example of what is needed to add new backends.

@Rbiessy

I am curious, have you tried to add a dummy backend and compile the files generated by the python scripts?

I did try that with BLAS, as mentioned in the document and saw some issues during the CMake configure steps. I believe that part is dependent on the backend library being used/ported, so the existing documentation may not be very useful beyond the generation of the CMake config file. There is room for improvement here.

Last time we tried the generated files were not compiling and not aligned with the existing domains in oneMKL. This should be verified if we want to keep support for it.
It is common in software engineering to get inspiration from existing code and adapting it for a different purpose. We have found it was easier to copy existing domains or backends rather than starting from scratch.
Even if we were to fix them now the python scripts are not often used or updated. They are more likely to fail or generate outdated file than work at first try.

The problem I see here is that each of the domains like BLAS, DFT etc have different ways of implementing the headers and the API declarations. This requires a different layout, which the scripts cannot manage at this time to the extent of being helpful for other domains than BLAS.

We have some relatively recent PRs that add new domains (DFT domain PR, SPARSE domain PR) or add new backends to existing domains (cuFFT backend PR, rocFFT PR or cuSPARSE PR). They are a more concrete example of what is needed to add new backends.

I agree with your POV that the scripts/*.py are difficult to maintain at this time.
My recommendation is that we update the document as per this PR for now (it still works), and then have a community poll to decide if we want to keep these generation scripts or not. If the consensus is to keep them, we may try to tailor them to support the specific differences of each domain as described in the oneMKL Specification, else remove them in a separate PR. What do you think?

My recommendation is that we update the document as per this PR for now (it still works), and then have a community poll to decide if we want to keep these generation scripts or not. If the consensus is to keep them, we may try to tailor them to support the specific differences of each domain as described in the oneMKL Specification, else remove them in a separate PR. What do you think?

That's fine with me.

The problem I see here is that each of the domains like BLAS, DFT etc have different ways of implementing the headers and the API declarations. This requires a different layout, which the scripts cannot manage at this time to the extent of being helpful for other domains than BLAS.

I agree, this is part of the issue. The way I see it we have 3 different kinds of domains today:

BLAS and LAPACK which are mostly independent free functions
RNG and DFT which rely a lot on oriented-object programming
SPARSE_BLAS which also uses free functions but has many opaque objects to store information across functions

My recommendation is that we update the document as per this PR for now (it still works), and then have a community poll to decide if we want to keep these generation scripts or not. If the consensus is to keep them, we may try to tailor them to support the specific differences of each domain as described in the oneMKL Specification, else remove them in a separate PR. What do you think?

That's fine with me.

The poll is now active: https://github.com/oneapi-src/oneMKL/discussions/598


Invalid port name "otlp-traces-http" on Azure AKS

When attempting to deploy this chart on Azure AKS, the grafana-k8s-monitoring-grafana-agent stateful set fails to deploy with the following error:
Pod "grafana-k8s-monitoring-grafana-agent-0" is invalid: spec.containers[0].ports[2].name: Invalid value: "otlp-traces-http": must be no more than 15 characters

I don't know if this is AKS specific (Azure has lots of random limits all over the place so I wouldn't be surprised).
As a workaround, I edited the stateful set manifest to rename the port to otlp-traces-h.
Additional info:
$ helm ls
NAME                  	NAMESPACE	REVISION	UPDATED                                	STATUS  	CHART                	APP VERSION
grafana-k8s-monitoring	grafana  	3       	2023-10-27 14:54:34.15259691 +0200 CEST	deployed	k8s-monitoring-0.2.12	1.3.2

Yeah, we had an issue earlier with the port name in the examples. As you saw, you can shorten the name. We currently recommend otlp-http.

oh right I hadn't realized the port name comes from my values.yaml :facepalm: Thanks for the hint, we can close the issue then.

All good! Happy to help.


nexd: Optionally build with pprof support

Go has tooling that makes profiling pretty easy. Add some build
automation and instructions for using it with nexd.
Signed-off-by: Russell Bryant<EMAIL_ADDRESS>

LGTM. Maybe we should also do this for the apiserver?

Yes, good idea, done here: https://github.com/nexodus-io/nexodus/pull/1243


hubot loads with a syntax error

This get emitted upon startup and repeats until Hubot eventually shuts down
[Mon Sep 21 2015 17:34:11 GMT+0000 (UTC)] INFO hubot-redis-brain: Using default redis on localhost:6379
[Mon Sep 21 2015 17:34:11 GMT+0000 (UTC)] ERROR SyntaxError: Unexpected token <
  at Object.parse (native)
  at /opt/hubot/node_modules/hubot-stackstorm/scripts/stackstorm.js:117:28
  at IncomingMessage.<anonymous> (/opt/hubot/node_modules/hubot/node_modules/scoped-http-client/src/index.js:95:22)
  at IncomingMessage.emit (events.js:129:20)
  at _stream_readable.js:908:16
  at process._tickCallback (node.js:355:11)

Should be working with the current version.

I just cloned this:
https://github.com/StackStorm/st2workroom
then:
vagrant up st2

And I see the exact same error. I am trying the slack adapter. Could be a problem in the workroom.yaml file but I could not find a good example.

Please try with the new packages -
Ubuntu https://docs.stackstorm.com/latest/install/deb.html
RHEL/CentOS https://docs.stackstorm.com/latest/install/rhel7.html
Tested, works.
We are deprecating st2workroom.

So no Vagrant setup ?
I was following a June 2015 blog: https://stackstorm.com/2015/06/08/enhanced-chatops-from-stackstorm/?doing_wp_cron=1456936590.6317980289459228515625

No, no more "heavy" vagrant setup: but still using vagrant is easy: spin one of the boxes from here https://docs.stackstorm.com/1.3/install/index.html, and either run AIO installer by curl -sSL https://install.stackstorm.com/ | sudo sh -s -- -r v1.3.2 or go for new package installation, as pointed above. Given our direction to deprecate AIO, I recommend trying the new packages.
There are correspondent script there too - https://github.com/StackStorm/st2-packages/blob/master/scripts/st2bootstrap-el7.sh https://github.com/StackStorm/st2-packages/blob/master/scripts/st2bootstrap-deb.sh
They don't currently include Chatops step (PR coming) so today you'll run the script, and finish up Chatops with "Setting up Chatops"
or, for AIO installer,

thanks @dzimine the st2 install worked, but trying to get st2chatops package fails.
following:
https://docs.stackstorm.com/latest/install/deb.html#setup-chatops
`
$ st2 rule list --pack=chatops
/usr/local/lib/python2.7/dist-packages/requests/packages/urllib3/connectionpool.py:791: InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.org/en/latest/security.html
InsecureRequestWarning)
ERROR: 401 Client Error: Unauthorized
MESSAGE: Unauthorized - One of Token or API key required. for url: https://<IP_ADDRESS>/api/rules/?limit=50
vagrant@vagrant-ubuntu-trusty-64:~$ sudo apt-get install -y st2chatops
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package st2chatops
`


Investigate using the --newline=[LF|CRLF|native|preserve] option in pip-compile

Is there an existing issue for this?

[X] I have searched the existing issues

Code improvement description
New pip-compile feature: https://github.com/jazzband/pip-tools/pull/1652

From that URL:

The default is preserve, which tries to be consistent with an existing output file, or input file, or falls back to LF, in that order.

That's the behavior we'd want, so no need to be explicit about it unless it starts causing problems, in which case I expect users will report problems with unexpected diffs.


Support for .NET

Build SDK support for .NET.
I'd be happy to contribute to the project.

While the core team probably doesn't have bandwidth to develop it at the moment, we'd love to help where possible if there are enough maintainers to a .net version!
The golang support organically developed in a similar way https://discord.com/channels/1038097195422978059/1097608449266831390

Thanks for the response @vowelparrot. I'm definitely on board with taking on support for the .NET version. I've connected with Harrison on Twitter and I'll check out the Go implementation.

Hi, .net support would be great.
I'm a junior .net developer so not yet experienced enough to lead such project but I'd be happy to contribute some time every week if anyone would take the lead.

@jeastham1993 i started with .net implementation in my own repository, but since i don't have that much free time my progress in not that good. you can check it out here. https://github.com/oorosh/langchain-dotnet

@oorosh ah ok, do you want to join up our efforts? I've implemented most of the base types, the LLM for OpenAI and HuggingFace, the prompts and have just started on the actual chaining. The repo is still private at the moment but I've just added you. I've got a bunch of changes I need to comitt from my other laptop as well, so it isn't quite up to date.

Sure. Btw, my repo is definitely behind what you have.

It would be awesome to collaborate in that case. I'm going to be travelling for a few hours tonight so I'll commit everything I have and then add some issues for what needs to happen next. We can split up the work then :)

yes, im up for it.

@oorosh I have just pushed an updated version of my .NET implementation that contains the basic functionality for chains, prompts and support for OpenAI and HuggingFace. If you want to review the code that would be awesome.

For anyone coming across this issue, the .NET implementation is here
https://github.com/jeastham1993/langchain-dotnet

For anyone interested, I've had some initial luck calling into the official langchainjs library in .NET using Microsoft ClearScript and some specially crafted polyfills.

Why not use Semantic Kernel for .NET ?
https://learn.microsoft.com/en-us/semantic-kernel/overview/

I have made some work that could be used (maybe).

Use of Llamasharp models version 1 and 2, incl ASP.NET WebApi
Use of OpenAI, incl a .Net Client. The use of it can be found in a Console and WPF appl in Examples, and a Test project.
Use of Qdrant Vector database and a new .Net Client for it
Use of Microsoft.SemanticKernel (Using the Qdrant Vector database).
As written by @itorian in the comment above, I would also consider this as a good candidate for a .Net LangChain
ImageClassification - TensorFlow.Net:
ImageClassification - Microsoft.ML/TensorFlow

A lot of the more experimental stuff is driven from Tests, but can easily be moved into an application
AI-playground

Hello everyone,
I'm thrilled to introduce LangChainJSDotNet, an open-source library designed as a wrapper for LangChain.js. It offers .NET developers a seamless interface to run LangChain-based code with minimal adjustments. Given that the official JS/TS version closely mirrors the Python version, this library enables easy porting of LangChain code to .NET, unlocking the latest AI advancements and features from LangChain's vast ecosystem for the .NET community.
Your feedback and collaboration would be invaluable. Check it out here:
https://github.com/iassafc/LangChainJSDotNet

FYI for anyone that comes upon this issue/request - here's another .NET implementation of LangChain that has been started: https://github.com/tryAGI/LangChain. I haven't worked with the project yet, but as of now I see there are still commits happening by its author and if you're interested in contributing this may be a good one to watch.
@jeastham1993 - it looks like you archived your original repo here, did you end up continuing your work anywhere else?


Support derived column of any type

Fix the issue of derived column expects function return type and cause cast exception. Leverage PinotDataType to convert the value
Add support for BIG_DECIMAL as default column or derived column

Codecov Report

Merging #8942 (4696479) into master (8474bae) will decrease coverage by 1.30%.
The diff coverage is 21.21%.

@@             Coverage Diff              @@
##             master    #8942      +/-   ##
============================================
- Coverage     69.73%   68.43%   -1.31%
+ Complexity     4888     4696     -192
============================================
  Files          1814     1814
  Lines         94506    94542      +36
  Branches      14117    14125       +8
============================================
- Hits          65905    64697    -1208
- Misses        23984    25286    +1302
+ Partials       4617     4559      -58

Flag
Coverage Δ

integration1
26.65% <4.54%> (-0.06%)
:arrow_down:

integration2
?

unittests1
66.26% <21.21%> (-0.02%)
:arrow_down:

unittests2
14.83% <0.00%> (-0.03%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...al/segment/index/readers/BigDecimalDictionary.java
80.00% <ø> (ø)

...main/java/org/apache/pinot/spi/data/FieldSpec.java
82.03% <ø> (ø)

...loader/defaultcolumn/BaseDefaultColumnHandler.java
58.24% <16.66%> (-4.92%)
:arrow_down:

...a/org/apache/pinot/spi/data/DateTimeFieldSpec.java
89.74% <33.33%> (-4.86%)
:arrow_down:

...java/org/apache/pinot/common/utils/DataSchema.java
69.00% <100.00%> (ø)

...apache/pinot/common/helix/ExtraInstanceConfig.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...t/core/plan/StreamingInstanceResponsePlanNode.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...ore/operator/streaming/StreamingResponseUtils.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...ager/realtime/PeerSchemeSplitSegmentCommitter.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...ator/streaming/StreamingSelectionOnlyOperator.java
0.00% <0.00%> (-90.00%)
:arrow_down:

... and 130 more

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 8474bae...4696479. Read the comment docs.


cherry-pick titan missing blob file fix and a few other rocksdb changes

What have you changed?
Update rust-rocksdb to pick up the following rocksdb and titan changes. The most notable one is fixing titan missing blob file issue.
rocksdb:
7e4e054ae 2019-10-15<EMAIL_ADDRESS>   Make WaitForFlushMemTable public (#125)
89ff3e3b8 2019-09-29<EMAIL_ADDRESS>   Lower the risk for users to run options.force_consistency_checks = true (#5744) (#120)
9c5b744ee 2019-09-26<EMAIL_ADDRESS>   Relax warnings as errors so we can build on Clang 11 (#123)
179a8f5e0 2019-09-20<EMAIL_ADDRESS>   fast look up purge_queue (#5796) (#119)

titan:
43225d4 2019-10-16<EMAIL_ADDRESS>   Fix Titan missing blob issue (#97)

What is the type of the changes?
Bugfix
How is the PR tested?
CI
Does this PR affect documentation (docs) or should it be mentioned in the release notes?
no
Does this PR affect tidb-ansible?
no
Refer to a related PR or issue link (optional)
Benchmark result if necessary (optional)
Any examples? (optional)

/run-all-tests

Same as #5672 but for 3.1 branch.

/run-all-tests

@yiwu-arbug Pls fix the  conflicts.

/run-all-tests

/run-all-tests

/run-all-tests

/tests


Standard Config not running on first time run

Hi, I'm new to EMHASS, and basically just downloaded it, and readed the docs for some days...
Sadly I was not able to get it to run, as the standard config does throw an error...The only thing I changed, was the variable:
I have no photovoltaic...I wanted to use the forecast for energy usage...
logging_level: DEBUG
costfun: profit
sensor_power_photovoltaics: sensor.power_photovoltaics
sensor_power_load_no_var_loads: sensor.gesamtenergieverbrauch_in_watt
set_total_pv_sell: false
set_nocharge_from_grid: false
set_nodischarge_to_grid: false
maximum_power_from_grid: 9000
number_of_deferrable_loads: 2
list_nominal_power_of_deferrable_loads:
  - nominal_power_of_deferrable_loads: 3000
  - nominal_power_of_deferrable_loads: 750
list_operating_hours_of_each_deferrable_load:
  - operating_hours_of_each_deferrable_load: 5
  - operating_hours_of_each_deferrable_load: 8
list_start_timesteps_of_each_deferrable_load:
  - start_timesteps_of_each_deferrable_load: 0
  - start_timesteps_of_each_deferrable_load: 0
list_end_timesteps_of_each_deferrable_load:
  - end_timesteps_of_each_deferrable_load: 0
  - end_timesteps_of_each_deferrable_load: 0
list_peak_hours_periods_start_hours:
  - peak_hours_periods_start_hours: "05:54"
  - peak_hours_periods_start_hours: "10:24"
list_peak_hours_periods_end_hours:
  - peak_hours_periods_end_hours: "09:24"
  - peak_hours_periods_end_hours: "11:54"
list_treat_deferrable_load_as_semi_cont:
  - treat_deferrable_load_as_semi_cont: true
  - treat_deferrable_load_as_semi_cont: true
list_set_deferrable_load_single_constant:
  - set_deferrable_load_single_constant: false
  - set_deferrable_load_single_constant: false
load_peak_hours_cost: 0.1907
load_offpeak_hours_cost: 0.1419
photovoltaic_production_sell_price: 0.065
list_pv_module_model:
  - pv_module_model: CSUN_Eurasia_Energy_Systems_Industry_and_Trade_CSUN295_60M
list_pv_inverter_model:
  - pv_inverter_model: Fronius_International_GmbH__Fronius_Primo_5_0_1_208_240__240V_
list_surface_tilt:
  - surface_tilt: 30
list_surface_azimuth:
  - surface_azimuth: 205
list_modules_per_string:
  - modules_per_string: 16
list_strings_per_inverter:
  - strings_per_inverter: 1
set_use_battery: false
battery_nominal_energy_capacity: 5000

Logs:
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun emhass (no readiness notification)
s6-rc: info: service legacy-services successfully started
2024-02-14 11:00:30,613 - web_server - INFO - Launching the emhass webserver at: http://<IP_ADDRESS>:5000
2024-02-14 11:00:30,613 - web_server - INFO - Home Assistant data fetch will be performed using url: http://supervisor/core/api
2024-02-14 11:00:30,613 - web_server - INFO - The data path is: /share
2024-02-14 11:00:30,615 - web_server - INFO - Using core emhass version: 0.7.7
waitress   INFO  Serving on http://<IP_ADDRESS>:5000
2024-02-14 11:03:39,626 - web_server - INFO - EMHASS server online, serving index.html...
2024-02-14 11:03:39,637 - web_server - WARNING - The data container dictionary is empty... Please launch an optimization task
2024-02-14 11:03:40,715 - web_server - INFO - Setting up needed data
2024-02-14 11:03:40,768 - web_server - INFO - Retrieving weather forecast data using method = scrapper
2024-02-14 11:03:42,154 - web_server - INFO - Retrieving data from hass for load forecast using method = naive
2024-02-14 11:03:42,155 - web_server - INFO - Retrieve hass get data method initiated...
2024-02-14 11:03:42,171 - web_server - ERROR - The retrieved JSON is empty, check that correct day or variable names are passed
2024-02-14 11:03:42,171 - web_server - ERROR - Either the names of the passed variables are not correct or days_to_retrieve is larger than the recorded history of your sensor (check your recorder settings)
2024-02-14 11:03:42,171 - web_server - ERROR - Exception on /action/dayahead-optim [POST]
Traceback (most recent call last):
  File "/usr/local/lib/python3.11/dist-packages/flask/app.py", line 1463, in wsgi_app
    response = self.full_dispatch_request()
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/dist-packages/flask/app.py", line 872, in full_dispatch_request
    rv = self.handle_user_exception(e)
         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/dist-packages/flask/app.py", line 870, in full_dispatch_request
    rv = self.dispatch_request()
         ^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/dist-packages/flask/app.py", line 855, in dispatch_request
    return self.ensure_sync(self.view_functions[rule.endpoint])(**view_args)  # type: ignore[no-any-return]
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/dist-packages/emhass/web_server.py", line 49, in action_call
    input_data_dict = set_input_data_dict(config_path, str(data_path), costfun,
                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/dist-packages/emhass/command_line.py", line 91, in set_input_data_dict
    P_load_forecast = fcst.get_load_forecast(method=optim_conf['load_forecast_method'])
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/dist-packages/emhass/forecast.py", line 589, in get_load_forecast
    rh.get_data(days_list, var_list)
  File "/usr/local/lib/python3.11/dist-packages/emhass/retrieve_hass.py", line 150, in get_data
    self.df_final = pd.concat([self.df_final, df_day], axis=0)
                                              ^^^^^^
UnboundLocalError: cannot access local variable 'df_day' where it is not associated with a value
2024-02-14 11:03:47,351 - web_server - INFO - Setting up needed data
2024-02-14 11:03:47,355 - web_server - INFO - Retrieve hass get data method initiated...
2024-02-14 11:03:47,376 - web_server - ERROR - The retrieved JSON is empty, check that correct day or variable names are passed
2024-02-14 11:03:47,377 - web_server - ERROR - Either the names of the passed variables are not correct or days_to_retrieve is larger than the recorded history of your sensor (check your recorder settings)
2024-02-14 11:03:47,377 - web_server - ERROR - Exception on /action/perfect-optim [POST]
Traceback (most recent call last):
  File "/usr/local/lib/python3.11/dist-packages/flask/app.py", line 1463, in wsgi_app
    response = self.full_dispatch_request()
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/dist-packages/flask/app.py", line 872, in full_dispatch_request
    rv = self.handle_user_exception(e)
         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/dist-packages/flask/app.py", line 870, in full_dispatch_request
    rv = self.dispatch_request()
         ^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/dist-packages/flask/app.py", line 855, in dispatch_request
    return self.ensure_sync(self.view_functions[rule.endpoint])(**view_args)  # type: ignore[no-any-return]
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/dist-packages/emhass/web_server.py", line 49, in action_call
    input_data_dict = set_input_data_dict(config_path, str(data_path), costfun,
                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/dist-packages/emhass/command_line.py", line 78, in set_input_data_dict
    rh.get_data(days_list, var_list,
  File "/usr/local/lib/python3.11/dist-packages/emhass/retrieve_hass.py", line 150, in get_data
    self.df_final = pd.concat([self.df_final, df_day], axis=0)
                                              ^^^^^^
UnboundLocalError: cannot access local variable 'df_day' where it is not associated with a value

I should have enough history...eve trying defining the days to two didn't wor out...maybe I'm doing something wrong? Please help =)

I have not put it in... should I put it? Do I need to create an access token?

Just check that they have and empty value if you are using the add-on.

Do I need to create an access token?

No (if using the add-on)

Okay I'm using the add-on and altered the config...still same error;
logging_level: DEBUG
costfun: profit
sensor_power_photovoltaics: sensor.power_photovoltaics
sensor_power_load_no_var_loads: sensor.gesamtenergieverbrauch_in_watt
set_total_pv_sell: false
set_nocharge_from_grid: false
set_nodischarge_to_grid: false
maximum_power_from_grid: 9000
number_of_deferrable_loads: 2
list_nominal_power_of_deferrable_loads:
  - nominal_power_of_deferrable_loads: 3000
  - nominal_power_of_deferrable_loads: 750
list_operating_hours_of_each_deferrable_load:
  - operating_hours_of_each_deferrable_load: 5
  - operating_hours_of_each_deferrable_load: 8
list_start_timesteps_of_each_deferrable_load:
  - start_timesteps_of_each_deferrable_load: 0
  - start_timesteps_of_each_deferrable_load: 0
list_end_timesteps_of_each_deferrable_load:
  - end_timesteps_of_each_deferrable_load: 0
  - end_timesteps_of_each_deferrable_load: 0
list_peak_hours_periods_start_hours:
  - peak_hours_periods_start_hours: "05:54"
  - peak_hours_periods_start_hours: "10:24"
list_peak_hours_periods_end_hours:
  - peak_hours_periods_end_hours: "09:24"
  - peak_hours_periods_end_hours: "11:54"
list_treat_deferrable_load_as_semi_cont:
  - treat_deferrable_load_as_semi_cont: true
  - treat_deferrable_load_as_semi_cont: true
list_set_deferrable_load_single_constant:
  - set_deferrable_load_single_constant: false
  - set_deferrable_load_single_constant: false
load_peak_hours_cost: 0.1907
load_offpeak_hours_cost: 0.1419
photovoltaic_production_sell_price: 0.065
list_pv_module_model:
  - pv_module_model: CSUN_Eurasia_Energy_Systems_Industry_and_Trade_CSUN295_60M
list_pv_inverter_model:
  - pv_inverter_model: Fronius_International_GmbH__Fronius_Primo_5_0_1_208_240__240V_
list_surface_tilt:
  - surface_tilt: 30
list_surface_azimuth:
  - surface_azimuth: 205
list_modules_per_string:
  - modules_per_string: 16
list_strings_per_inverter:
  - strings_per_inverter: 1
set_use_battery: false
battery_nominal_energy_capacity: 5000
days_to_retrieve: 2
hass_url: empty
long_lived_token: empty

Are you sure that you have enough history data on sensor.gesamtenergieverbrauch_in_watt

Oh I'm sorry my bad...the parent sensor would have enough history, but the template only has one and a half day... But even if I set "days_to_retrieve to one, I get the same error...Screenshot_20240214_145101_Home Assistant.jpg

It is hard coded to 2 days minimum.
So the logged message of your first post is correct:
days_to_retrieve is larger than the recorded history of your sensor (check your recorder settings)

@davidusb-geek , maybe we can set it to auto set to two days if any numbers under 2, and warn the user with a logger.error ?
May reduce the python error in some workflows yet still letting the user know there is an issue.

Was also wondering if we can spot an error that states the sensor doesn't have enough history?

Yes that could be an option. But for example in the case with this issue the result will be the same right?
The real solution will be finding a way to let the user just enter their normal load power sensor and then automatically identify the deferrable loads on that data to subtract them from the total load. An idea could be that for a first ever run with just the load data as it is but for a seond run we use the saved results from a previous optimization load schedule run to try to identify at which time the deferrable loads are and then subtract them. That could work

try to identify at which time the deferrable loads are and then subtract them.

I do something quite different to subtract my deferrable loads and have been meaning to discuss this online as they would greatly simplify setup for new users:
    - name: power_load_no_var_loads
      unit_of_measurement: W
      device_class: power
      state_class: measurement
      unique_id: 9e2d02cb-2ac4-4eb2-9f57-c4c158c145e7
      state: >-
        {{states('sensor.gateway_load_power')|int(0)
        - states('sensor.p_deferrable0')|int(0)
        - states('sensor.p_deferrable1')|int(0)
        - states('sensor.p_deferrable2')|int(0)
        - states('sensor.p_deferrable3')|int(0)
        - states('sensor.p_deferrable4')|int(0)
        - states('sensor.p_deferrable5')|int(0)
        }}

My original motivation was that my HVAC load is quite variable (dependent on the setpoint difference, but that is another conversation).
Anyway I noticed that EMHASS couldn't allocate additional power if it was going to be consumed by the load, sometimes upto 5000W difference and I observed how power_load_no_var_loads was being utilised to manage the overs and unders with the power allocation, so i tried this alternative calculation and it works really well.
Giving an example my p_deferrable3 is my HVAC which has a p_nom (average) of 3000W, but in reality the power draw could be anywhere between 0W - 11,000W, depending on the set point.  So using the modified load calculation above I have gateway_load_power = 8000W (which includes the actual HVAC maybe 6000W) and p_deferrable3 = 3000W (p_nom).  So the power_load_no_vars comes out at 8000 - 3000 = 5000W. If p_pv is 10000W then EMHASS allocates 3000 to deferrable_3, 5000W to load_no_vars (which includes the missing 3000W from HVAC) and has 2000 W remaining to allocate to other loads.
vs the traditional method of calculation would be power_load_no_vars = 8000 - 6000 = 2000 W.  If p_pv is 10000W then EMHASS allocates 3000 W to deferrable_3, 2000W to load_no_vars and has 5000W to allocate.  But the HVAC is already consuming 3000W, so in reality EMHASS only should be allocating 2000W to the other loads.
Now where this can really simply EMHASS optimisation is these values are all internal (except gateway_load) to EMHASS, so the user doesn't need to supply a subtraction calculation to come up with load_no_vars, it can be calculated internally within EMHASS.

@purcell-lab I don't think that I completely understand well. How is that template a modified version of what is needed to compute the power_load_no_var_loads sensor. It is actually what is prescribed and it is also what I use everyday.
Or states('sensor.p_deferrable3')|int(0) is just retrieving the constant nominal value of your deferrable load 3?
The main goal for power_load_no_var_loads is to be used for the load power forecast, either naive of the more advanced ML method. So I don't see how can we do what you say internally without knowing for each deferrable both the power value AND when these loads where scheduled in the past by EMHASS.
Maybe an example on a time series curve could help

Yes, I agree I haven't explained the connect too well.
I shall try and connect since examples to demonstrate the concept.

Great! you can close it please


Support C/C++

Connect osv-scanner with

https://github.com/google/osv.dev/issues/561
https://github.com/google/osv.dev/issues/783

To provide C/C++ dependency detection and vuln management.

@andrewpollock this would be the logical next step after your work on the NVD coverage!

I don't know if this is the right place for this input. If not, please direct me somewhere else :).
The point of #561 seems to be:

Given: file hashes
Return: Repository URL, CPEs, Closest tag/version

For our use case, the input of file hashes would be rather cumbersome. We know our dependencies and their versions – the main problem is effectively mapping these to CPEs. Having an API that takes the library name or source repository URL as input and returns a CPE would be really helpful – or does this already exist?

@andrewpollock any rough ETA for C/C++ support? Thanks much for working on this btw.

@varun-endor it's an end-of-year goal overall, but per https://github.com/google/osv.dev/issues/783#issuecomment-1407906210 I'll break this down into some milestones for interested parties to follow along on.

The NVD database part is out now!
The remaining bits for OSV-Scanner support are:

https://github.com/google/osv-scanner/issues/612
https://github.com/google/osv-scanner/pull/581

I think we can call this "done"?


Fail to unpack messages with custom headers in case java(pack)-->python(unpack)

If a java client packs a message that includes a custom header, when it is unpacked by Python client, it fails with MalformedMessageCode.INVALID_PLAINTEXT error.
The other cases works fine: java-->java, python-->python, python-->java. All are unpacked without error.
How to reproduce the error:

add .customHeader("return_route","all") in line 109 of DIDCommDemoHelper.kt

val message = Message.builder(
            id = UUID.randomUUID().toString(),
            body = mapOf("msg" to data),
            type = "my-protocol/1.0"
)
.customHeader("return_route","all")
.build()

rebuild
run demo.py
check error at the end:
Bob received MalformedMessageCode.INVALID_PLAINTEXT.

Same results were obtained using both libraries but outside this demo, just to confirm that is not a problem of the demo code. I'm opening the issue in this repo because I can't say if it's a problem in the python library or in the JVM library.

tagging @dmitry-vychikov and @dkulic, so you at least see this issue. It may be relevant for some of your current work because at least the java DIDComm v2 libraries are likely to be relevant, and the error may be on the java side?