ENH: Add compatibility for Random Forest Quantile Regressor

Problem Description
Would be great to make Random Forest Quantile Regressor library compatible with Shap Tree Explainer
https://github.com/zillow/quantile-forest
This shouldn't be difficult to do considering the fact that it inherits Random Forest Regressor offered by sklearn.
Alternative Solutions
https://github.com/zillow/quantile-forest/issues/55
The QRF estimators in this package aren't currently compatible with the Tree SHAP explainer due to a strict class check. This check currently only allows sklearn.ensemble.RandomForestRegressor, sklearn.ensemble.forest.RandomForestRegressor, and econml.grf._base_grf.BaseGRF.
Given how SHAP validates the model input for the Tree SHAP explainer, this issue likely falls under the scope of the SHAP project. A practical solution would be to raise an issue with the SHAP project maintainers, suggesting that they include quantile_forest.ExtraTreesQuantileRegressor and quantile_forest.RandomForestQuantileRegressor in the list of safe model instances.
In the meantime, a workaround is possible. The QRF estimators in this package fit the same estimators as a standard scikit-learn RF. So you can create a new RandomForestRegressor instance and populate it with the fitted estimators from a QRF. You can then use this RF instance to extract SHAP values. The resulting explanations should be identical to those produced directly from the QRF. Here's an example:
import shap
from quantile_forest import RandomForestQuantileRegressor
from sklearn import datasets
from sklearn.ensemble import RandomForestRegressor
from sklearn.model_selection import train_test_split

X, y = datasets.fetch_california_housing(as_frame=True, return_X_y=True)
X_train, X_test, y_train, y_test = train_test_split(X, y, test_size=100, random_state=0)

# Train the QRF.
qrf = RandomForestQuantileRegressor(random_state=0)
qrf.fit(X_train, y_train)

# Set the RF estimators with the fitted QRF ones.
rf = RandomForestRegressor(random_state=0)
rf.estimators_ = qrf.estimators_

# Use Tree SHAP to generate explanations.
explainer = shap.TreeExplainer(rf, X_test)
shap_values = explainer(X_test, check_additivity=False)
shap.plots.waterfall(shap_values[0])

Additional Context
No response
Feature request checklist

[X] I have checked the issue tracker for duplicate issues.
[X] I'd be interested in making a PR to implement this feature

While waiting for a proper solution within SHAP library, devs of quantile_forest lib gave another way of computing TreeSHAP for quantile regression forest.
https://zillow.github.io/quantile-forest/gallery/plot_qrf_treeshap_explanations.html


Docs: Update Epoch installation instructions

Page URL: Epoch IDE
Issue: This refers to version 0.3 as the latest stable version and doesn't have info about the new curl-based installation mechanism.
Recommended Fix: This needs to be updated.
Also: The Epoch splash page still says its version is 0.4.1 Snapshot

Note: problems with the publication of nightly (evidenced by out-dated splash screen) are resolved in https://github.com/lf-lang/epoch/pull/46.


Newsfeed appears to crash the electron app - no error message(s)

Appears that the newsfeed module is making the electron app shutdown - app silently shuts down.  I tried to change the logging levels but didnt make a difference in terms of useful errors, etc.  I confirmed this issue is specific to the newsfeed by configuring each module one at a time.  Likewise, I tried several different feed and module configuration options.
    {
        module: 'newsfeed',
        position: 'bottom_bar',
        config: {
            feeds: [
                {
                    title: "New York Times",
                    url: "http://www.nytimes.com/services/xml/rss/nyt/HomePage.xml"
                },
                {
                    title: "BBC",
                    url: "http://feeds.bbci.co.uk/news/video_and_audio/news_front_page/rss.xml?edition=us"
                }
            ]
        }
    }

nodejs install source:
http://thisdavej.com/beginners-guide-to-installing-node-js-on-a-raspberry-pi/
(specifically this version of the install:  https://github.com/nodesource/distributions/blob/master/deb/setup_6.x)
nodejs version: v0.6.19
npm version: 1.1.4

Could you try updating Node by running the MagicMirror installer script?

What version of Node should I be running?  What is the best place to get this version for a v2 Pi?

At least 5.1.0 (this is what I've tested.)
But if you run the MM installer, it will be upgraded automatically. Just run:
curl -sL https://raw.githubusercontent.com/MichMich/MagicMirror/master/installers/raspberry.sh | bash

For further support, please check http://forum.magicmirror.builders


Add e2e tests for mint NFT flow

https://testing.standwithcrypto.org/action/nft-mint
Open technical questions:

How can we mock out the Thirdweb auth flow?
-- naive approach would be to have a bunch of conditionals that only work in cypress environment

We're now using LocalWallets for the cypress environment https://blog.thirdweb.com/guides/how-to-use-local-wallets/


List supported platforms in SDK docs v5 -Closes #1108

Closes #1108

Hey Mona! Good points, I think it looks better now.


Android link for "How To Find Your Secrets" is down.

Just to let you know. The link to the repository (Android guide) is down (404).

Thanks! I'll start to look for an alternative link. If you find one first, let me know!

https://www.reddit.com/r/SteamBot/comments/3w5zwb/info_get_your_2fa_codes_from_android_no_root/
Don't have my Android device to test atm, but that might work.

I don't own an Android device. So I can't confirm if it works. When I was reading the docs I noticed the link wasn't working.
Maybe someone else with an Android device can confirm if this is working? 👍

This method does not work for me.

In the application of Steam there is a restriction on backup and debug. Only use root.
Bad news :(

@alicrypto ah ok. Do you have any links for a tutorial on that?

@andrewda
https://github.com/JustArchi/ArchiSteamFarm/wiki/Escrow
https://stackoverflow.com/questions/13006315/how-to-access-data-data-folder-in-android-device
https://stackoverflow.com/questions/1043322/why-do-i-get-access-denied-to-data-folder-when-using-adb
http://denniskubes.com/2012/09/25/read-android-data-folder-without-rooting/

@alicrypto awesome thanks! I'll change the link later today.

I finally solved this problem.
I had to disassemble the AIC. Now you can easily retrieve account information using my method.
https://github.com/alicrypto/steam_crack
Testing, pls.

Great, thanks @alicrypto !

Can be closed.

The link is still down. Shouldn't it be changed to the one @alicrypto provided?

Slight issue – @alicrypto's account has been deleted and their repository no longer exists. Not sure if anyone forked it. I'm going to link this one for now. Please open a PR if you'd like to suggest a better one.


Release secrets-gradle-plugin to gMaven

Any ETAs on the maven release?

The plugin is live on google maven now. Please refer to the README for installation instructions as install steps have changed since v1.2.0 due to google maven requirements (the maven coordinates are different and additions to the project's build.gradle file are necessary)


[BUG] Azure App Configuration client not be able to take a client request id

Azure App Configuration client cannot take a custom client request id when user creates, retrieves or deletes a key value. This will block the future issue investigation.

Completed with #7793


[EventRequest] Page 5827 “Item Statistics”, SetItem [External]

Please add a new publisher event OnAfterSetItem as shown in the picture below in the function Set in page 5827

Please add the corresponding Integration Event In the bottom of the page soruce code

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


Screenshots of long pages get interrupted

Screnshooting longer pages result in incomplete images.
Example:
docker run --shm-size 1G --rm -v ${PWD}:/screenshots alekzonder/puppeteer:latest full_screenshot_series "https://medium.com/@micheledaliessi/how-does-the-blockchain-work-98c8cd01d2ae" 1366x768 1500

Gives this result:

Is there any way to receive a complete screenshot of longer pages?

It's a Chromium Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=770769&desc=2
Here's an example how to make screenshotting long pages work: https://github.com/GoogleChrome/puppeteer/blob/230be28b067b521f0577206899db01f0ca7fc0d2/examples/screenshots-longpage.js
Maybe this can get included into your Docker image @alekzonder ?

@derFunk yes, i add screenshot patch to docker image

I created this, it should be working: https://gist.github.com/derFunk/10747ce60e965de5b771e96b7a4ba8f7
I extended the returned JSON to contain the created single images with the 16k max texture size.
Stitching has to be done with e.g. ImageMagick: convert -append file1.png file2.png out.png, by iterating over the filenames (e.g. jq -r '.files[].filename').
I had a little caveat though: Pretty regularly I encountered that the screenshot loop gets stuck, resulting in Error: Protocol error (Page.captureScreenshot): Target closed..
I didn't dig too deep into it, but found out that a page reload inside of the for loop seems to mitigate that specific error. It's a dirty hack (and commented out in my Gist), without me knowing why this helps, I just tried out several things to fix the getting-stuck problem.
I'll continue testing and can eventually provide a PR.


 However, the delay time does work when the mouse exits the hover area. This is kind of bad because it causes the tooltip to show up instantly when the user just quickly hovers over the area. My app needs to give the user about one second before deciding to show the tooltip. It would be nice if you could provide a fix for this. Thanks!

Hi, this is not a bug do I'll close this issue :) You have to use a setTimeout and use your own listeners in that case before using the open method, if that's what you want. Thank you


Add release process documentation

Closes #18

Hm ideally we should also add a sentence to the readme to draw users' attention to the fact that binary releases are available?


perf: reduce factory memory usage

Previously we use concret values for fields in message struct, using unsafe.Sizeof(mesgs), it will produce 3362000 B (3.36 MB)

type message struct {
	Num    typedef.MesgNum
	Fields [256]proto.Field
}

var mesgs = [...]message{ /* data */ }

We change it to use pointer values since most of the message only has small amount of fields, it will only produce 842960 (0,84 MB)

type message struct {
	Num    typedef.MesgNum
	Fields [256]*proto.Field // <---- this
}

There is no significant performance reduction on decoding process after factory uses pointer values
goos: darwin
goarch: amd64
pkg: github.com/muktihari/fit/decoder
cpu: Intel(R) Core(TM) i5-5257U CPU @ 2.70GHz
         │   new.txt   │           new2.txt            │
         │   sec/op    │   sec/op     vs base          │
Decode-4   108.6m ± 1%   108.8m ± 1%  ~ (p=0.529 n=10)

         │   new.txt    │              new2.txt               │
         │     B/op     │     B/op      vs base               │
Decode-4   67.39Mi ± 0%   67.39Mi ± 0%  -0.00% (p=0.050 n=10)

         │   new.txt   │            new2.txt             │
         │  allocs/op  │  allocs/op   vs base            │
Decode-4   900.0k ± 0%   900.0k ± 0%  ~ (p=1.000 n=10) ¹
¹ all samples are equal

Another change is proto messages variable used by CreateMesg is now using array to ensure O(1) lookup, it will only use 22960 (22.96 KB) on its empty state.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 99.02%. Comparing base (b9d8239) to head (f675a34).

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #123   +/-   ##
=======================================
  Coverage   99.02%   99.02%
=======================================
  Files          45       45
  Lines        4391     4391
=======================================
  Hits         4348     4348
  Misses         43       43

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Fix SQLiteConstraintException spike crashes

Task/Issue URL: https://app.asana.com/0/488551667048375/1207351226753468/f
Description
Gracefully stop the VPN in case of code 1555 SQLITE_CONSTRAINT_PRIMARYKEY db error
Steps to test this PR
NA, just code review

#4558  👈
develop

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @aitorvs and the rest of your teammates on  Graphite


Use clipboard register when to yank

Enable yank action correctly to use correct clipboard register.
It's same way of yanking in unite.vim

Thanks.


Adopt the resolver cookbook into sous chefs

Description
This is intended to import the cookbook fully into the Sous Chefs environment.
Issues Resolved

Adds inspec testing
Removes deprecated platforms
Moves ci over to sous-chefs

Check List

[X] All tests pass. See TESTING.md for details.
[X] New functionality includes testing.
[X] New functionality has been documented in the README if applicable.

Seems like it's failing due to #33 again

Released as: 2.2.0


Refactor "/google" Route for Improved Code Structure

Description:
This GitHub issue focuses on refactoring the "/google" route within the packages/server/src/api_auth/index.ts file. The objective is to enhance the code structure by utilizing res.locals.reqClientData as the source for client data, eliminating direct access to req.body, req.query, and req.params. The refactoring should also implement error handling using a try-catch block, following the error handling approach in the "login" route within the same folder.
Tasks:

Code Refactoring:

[ ] Review the existing "/google" route in packages/server/src/api_auth/index.ts.
[ ] Replace direct accesses to req.body, req.query, and req.params with res.locals.reqClientData.
[ ] Ensure consistent retrieval of client data from res.locals.reqClientData.

Error Handling:

[ ] Implement a try-catch block to handle errors gracefully.
[ ] Customize error messages and responses for meaningful feedback.

Testing:

[ ] Test the refactored "/google" route to ensure it functions correctly.
[ ] Verify that error handling is effective in different scenarios.

Documentation:

[ ] Update any relevant documentation to reflect the changes made to the "/google" route.

Acceptance Criteria:

The "/google" route is successfully refactored to use res.locals.reqClientData.
Direct accesses to req.body, req.query, and req.params are eliminated.
The refactored code includes a try-catch block for error handling.
Testing confirms the correct functionality of the refactored route.
Documentation accurately reflects the changes made to the "/google" route.

Additional Information:

Utilizing res.locals.reqClientData improves code structure and reduces dependencies on direct request access.
Effective error handling enhances the robustness of the route.

Hi @prasenjeet-symon I am interested to work in this issue. will u assign it to me?

Hi @prasenjeet-symon I am interested to work in this issue. will u assign it to me?

Yes assigned to you


SignalR Service details

It would be great if you can include SingalR service architectural and implementation details.

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

ID: 53ea26cb-1cc0-2616-d0b4-cd50f1194a75
Version Independent ID: 01eb1d9d-060a-01a8-aa50-68e017b2db38
Content: Messaging - Azure Solution Ideas
Content Source: docs/solution-ideas/articles/messaging.md
Service: architecture-center
Sub-service: solution-idea
GitHub Login: @adamboeglin
Microsoft Alias: pnp

Thanks for reporting - this issue is under review.  This is a Microsoft Internal DevOps Bug ID AB#217570

I can imagine a similar strategy as presented in https://youtu.be/6w6E_B55p0E?t=531 by Netflix using their Zuul server implementation. Have a separate SignalR service infrastructure that is a subscriber to the event queue (Azure Redis Cache in this case) and deliver those to the clients - but keep it totally separated not breaking the API gateway in other places of your app infrastructure.

@ashuisonline, Using the SignalR service to implement a messaging solution is showcased in the Real-time Web Dashboard  solution idea. Let us know, through the feedback on that page, if you'd like to see us expand this article with more information (implementation details, pricing guidance, code examples, etc)


Include Tixati

I would love it if you could include Tixati in the software.
https://www.tixati.com/download/

not open source or in winget


Hi, is there a way to get best checkpoint?

for eval setting. We run server times and choose the best final one.

在 2021年12月15日，下午5:56，konyul @.***> 写道：

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.


Help with pgpass file

The use of create_user or add_user commands requires a ~/.pgpass file (or whatever $PGPASSFILE points to). This can create some confusion and extra steps. So this PR makes first the error messages more information (and log lines also provide next steps)., then adds a default .pgpass file to show the expected format. Now the only exception message should be about a missing line, and that message is preceded by a line which can by added to .pgpass (along with a suitable and secure password!).

@tvogels01
I looked at the spec for pgpass : https://www.postgresql.org/docs/9.3/libpq-pgpass.html
and noticed that we wouldn't really have room to add metadata to construct groups or add users to those groups. Please disregard the q for now!

The intention of ~/.pgpass is set the password in a repeatable way when running create_user.
The construction of groups should go into the settings file.
See https://github.com/harrystech/arthur-redshift-etl/blob/v1.23.1/python/etl/config/settings.schema#L167


fix: resolve miscellaneous errors in various C examples

Resolves #1690.
Description

What is the purpose of this pull request?

This pull request resolves failed C examples in develop.
Related Issues

Does this pull request have any related issues?

Fixes #1690.
Questions

Any questions for reviewers of this pull request?

No.
Other

Any other information relevant to this pull request? This may include screenshots, references, and/or implementation notes.

No.
Checklist

Please ensure the following tasks are completed before submitting this pull request.

[x] Read, understood, and followed the contributing guidelines.

@stdlib-js/reviewers

Thanks @kgryte ! Didn't wish to bother you but can you please quickly go through PR #1670?


Support for tapscripts (scripts within tr descriptor)

This tracks the work necessary to spend P2TR outputs containing scripts.
Since signatures for the key-path spend and for each tapleaf are distinct, the interface should take that into account; the default behaviour could be to sign for all the valid paths (key path spend + each script, repeating for each internal placeholder).
To decide:

How does the client specify what spending paths should be used? Should all paths be signed as default behaviour? Should the client be able to specify which internal keys should sign (if more than one is present)?
Does the UX tell the user which spending path is being used? If so, how? Probably: show the descriptor for that tapleaf, but it might not be a great UX. Different applications might have different requirements, so we should aim for flexibility.

TODO:

[ ] Generalize the signing code with the Common Signature Message Extension per BIP-342
[ ] Parse correctly tr(KP, TREE) policies, for the supported descriptors.
[ ] Support descriptors within tr:

[ ] pk
[ ] multi_a, sortedmulti_a

About the signing strategy and format: before taproot scripts, "signing a transaction" means "approving it unconditionally"; this is reflected in the typical UX flow, showing to the user all the outputs (except change) and summary information like transaction fees.
The fact that spending a tapscript creates a signature that is only valid for that spending path could allow more fine-grained control that might be useful in certain protocols. For example, a taptree might have an and(Alice, Bob) leaf and an and(Alice, Carl)  leaf; if Alice is the first signer, by only signing one of the two paths she can effectively (and non-interactively) delegate the final decision to either Bob or Carl.
For the initial support of tapscripts, it probably makes sense to keep things simple and limit support to the "unconditionally authorize transactions" when signing policies with taptrees; therefore, for each internal key placeholder,  the device will sign all the spending paths (including the key-path spend) that contain that internal key placeholder.
When signing for a taproot script path, instead of yielding the current
        <input_index> <pubkey_len> <pubkey> <signature>
response, we might yield
        <input_index> <pubkey_len> <pubkey> <tapleaf_hash_len = 32> <tapleaf_hash> <signature>
in order to facilitate the client to identify which script path we are spending from; the length of the response makes it unambiguous.
If support for signing individual spending paths is added in the future, we could use vendor-specific fields added by the client in the psbt2 to signal to the device that the signing behavior is not "unconditionally authorize this transaction".


Want to add a blockchain development course

Please assign this to me

I would like to work on this,
Dear maintainer , please add hacktoberfest label to the issues ,


📌 DittoSwiftPackage (4.4.2-alpha1)

This changes the dependency on DittoSwiftPackage to use a pre-release version. This doesn't need to be merged into the target branch, but would need to be tagged with 4.4.2-alpha1 in order to be consumable by an app or tool.

Put this PR back in draft mode because this change should not be merged into the normal branches. It is a one-off change just for an alpha release - which is essentially required to use an alpha version of DittoSwiftPackage 🙄

This update was implemented in the 4.4.2-alpha1 release


Update zio-json, zio-json-golden to 0.7.1

About this PR
📦 Updates

dev.zio:zio-json
dev.zio:zio-json-golden

from 0.6.2 to 0.7.1
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "dev.zio" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "dev.zio" }
}]

labels: library-update, early-semver-major, semver-spec-minor, commit-count:1

Superseded by #163.


Allow where clauses on direct features in Deep Feature Synthesis

DFS will automatically add where clauses to aggregation features based on the values in the interesting_valuesproperty of a variable within that entity.
This PR allows DFS to add where clauses using the interesting values of a direct feature.
First reported by @favstats on stackoverflow: https://stackoverflow.com/questions/52673694/specifying-interesting-variables-with-featuretools-does-not-work

Codecov Report

Merging #279 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #279      +/-   ##
==========================================
+ Coverage   94.45%   94.46%   +<.01%
==========================================
  Files          71       71
  Lines        7704     7711       +7
==========================================
+ Hits         7277     7284       +7
  Misses        427      427

Impacted Files
Coverage Δ

featuretools/tests/testing_utils/mock_ds.py
87.4% <ø> (ø)
:arrow_up:

featuretools/synthesis/deep_feature_synthesis.py
93.29% <100%> (+0.01%)
:arrow_up:

featuretools/primitives/direct_feature.py
95.83% <100%> (+0.37%)
:arrow_up:

...ols/tests/dfs_tests/test_deep_feature_synthesis.py
98.45% <100%> (ø)
:arrow_up:

...sts/feature_function_tests/test_direct_features.py
100% <100%> (ø)
: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 0e93f2a...5652258. Read the comment docs.

This fixed my issue! Thank you so much for the very quick help, this is really amazing!

@rwedge addressed your comments. does this look good to merge?


Generating installer too slow

How long should generating the installer take? My full nupkg is ~120 MB, and generating the setup.exe, setup.msi, and .fullnupkg files takes 5-10 minutes. Is this normal? What are ways of making this process faster?

Duplicate of this. Also, support seems to be in favour of electron-builder, and I'm having on issues with it, so I'm going to switch to that.


mitmdrump crashes with --ssl-insecure option with certain website requests

Steps to reproduce the problem:

Install mitmproxy for Ubuntu Desktop 18.04.1 or CentOS-7-x86_64-Minimal-1804
Install mitmproxy-ca certificate on Windows 10 host. Confirm web browsing works with trust in the proxy
Monitor "mitmdump --mode transparent --no-http2 --ssl-insecure" command output and see it crashes when Windows 10 tries to go to its websites (e.g. v10.vortex-win.data.microsoft.com). The following error message will be displayed:

::ffff:<IP_ADDRESS>:50088: Certificate verification error for v20.vortex-win.data.microsoft.com: unable to get local issuer certificate (errno: 20, depth: 1)
::ffff:<IP_ADDRESS>:50088: Ignoring server verification error, continuing with connection
<IP_ADDRESS>:50088: Traceback (most recent call last):
  File "/usr/local/lib/python3.6/dist-packages/mitmproxy/net/tcp.py", line 118, in read
    data = self.o.read(rlen)
  File "/usr/local/lib/python3.6/dist-packages/OpenSSL/SSL.py", line 1783, in recv
    self._raise_ssl_error(self._ssl, result)
  File "/usr/local/lib/python3.6/dist-packages/OpenSSL/SSL.py", line 1631, in _raise_ssl_error
    raise SysCallError(errno, errorcode.get(errno))
OpenSSL.SSL.SysCallError: (104, 'ECONNRESET')

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.6/dist-packages/mitmproxy/proxy/server.py", line 121, in handle
    root_layer()
  File "/usr/local/lib/python3.6/dist-packages/mitmproxy/proxy/modes/transparent_proxy.py", line 19, in __call__
    layer()
  File "/usr/local/lib/python3.6/dist-packages/mitmproxy/proxy/protocol/tls.py", line 286, in __call__
    layer()
  File "/usr/local/lib/python3.6/dist-packages/mitmproxy/proxy/protocol/http1.py", line 83, in __call__
    layer()
  File "/usr/local/lib/python3.6/dist-packages/mitmproxy/proxy/protocol/http.py", line 188, in __call__
    if not self._process_flow(flow):
  File "/usr/local/lib/python3.6/dist-packages/mitmproxy/proxy/protocol/http.py", line 282, in _process_flow
    f.request.data.content = b"".join(self.read_request_body(request))
  File "/usr/local/lib/python3.6/dist-packages/mitmproxy/net/http/http1/read.py", line 138, in read_body
    content = rfile.read(chunk_size)
  File "/usr/local/lib/python3.6/dist-packages/mitmproxy/net/tcp.py", line 140, in read
    raise exceptions.TlsException(str(e))
mitmproxy.exceptions.TlsException: (104, 'ECONNRESET')

Traceback (most recent call last):
  File "/usr/local/lib/python3.6/dist-packages/mitmproxy/net/tcp.py", line 118, in read
    data = self.o.read(rlen)
  File "/usr/local/lib/python3.6/dist-packages/OpenSSL/SSL.py", line 1783, in recv
    self._raise_ssl_error(self._ssl, result)
  File "/usr/local/lib/python3.6/dist-packages/OpenSSL/SSL.py", line 1631, in _raise_ssl_error
    raise SysCallError(errno, errorcode.get(errno))
OpenSSL.SSL.SysCallError: (104, 'ECONNRESET')

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.6/dist-packages/mitmproxy/proxy/server.py", line 121, in handle
    root_layer()
  File "/usr/local/lib/python3.6/dist-packages/mitmproxy/proxy/modes/transparent_proxy.py", line 19, in __call__
    layer()
  File "/usr/local/lib/python3.6/dist-packages/mitmproxy/proxy/protocol/tls.py", line 286, in __call__
    layer()
  File "/usr/local/lib/python3.6/dist-packages/mitmproxy/proxy/protocol/http1.py", line 83, in __call__
    layer()
  File "/usr/local/lib/python3.6/dist-packages/mitmproxy/proxy/protocol/http.py", line 188, in __call__
    if not self._process_flow(flow):
  File "/usr/local/lib/python3.6/dist-packages/mitmproxy/proxy/protocol/http.py", line 282, in _process_flow
    f.request.data.content = b"".join(self.read_request_body(request))
  File "/usr/local/lib/python3.6/dist-packages/mitmproxy/net/http/http1/read.py", line 138, in read_body
    content = rfile.read(chunk_size)
  File "/usr/local/lib/python3.6/dist-packages/mitmproxy/net/tcp.py", line 140, in read
    raise exceptions.TlsException(str(e))
mitmproxy.exceptions.TlsException: (104, 'ECONNRESET')

mitmproxy has crashed!
Please lodge a bug report at: https://github.com/mitmproxy/mitmproxy

Any other comments? What have you tried so far?
If I remove --ssl-insecure, mitmdump no longer crashes, but instead displays:
Certificate verification error for v20.vortex-win.data.microsoft.com: unable to get local issuer certificate (errno: 20, depth: 1)
Invalid certificate, closing connection. Pass --insecure to disable validation.
In addition, when running mitmdump --mode transparent --ssl-insecure (without --no-http2), it also crashes.
I tried setting up a CentOS 7 version 1804 server and it has the same error messages and behavior.
System information

Mitmproxy: 4.0.3
Python:    3.6.5
OpenSSL:   OpenSSL 1.1.0h  27 Mar 2018
Platform:  Linux-4.15.0-29-generic-x86_64-with-Ubuntu-18.04-bionic

We just merged a brand new protocol implementation - if you can repeat the problem with the latest version from git-master, please re-open this issue.


Support netstandard2.0

Why do you only support NET 7 now? Can you support netstandard2.0 again?
#Background
You have released a new version that only works on .NET 7.0. But this is bad and a breaking change. Can't you please just support .NET 7.0 additionally? So just like before with <TargetFrameworks>netstandard2.0;netstandard2.1;net5.0;net6.0;net7.0</TargetFrameworks>
https://github.com/eaba/AvroSchemaGenerator/commit/9c9c363d06de5bf2c720d2c2b0babe7361d03ed6#diff-63f903ddf61b5ae02fd6dd39234381603d0258694c66d9d5ca4075af07086927
Background is, that we have our APIs in .NET 6.0 because that is an LTS version.
Originally posted by @danny-krueger in https://github.com/eaba/AvroSchemaGenerator/issues/80

@eaba could you please return .netstandard2.0 support, otherwise pulsar-client-dotnet will have to remove dependency on your library and publish a separate nuget package from the fork.

Thank you!


Chore/swift uniffi

To fix the unused dependencies error,
unused dependencies:
`ffi v0.1.0 (/home/runner/work/yttrium/yttrium/crates/ffi)`
└─── build-dependencies
     └─── "swift-bridge-build"
Note: These dependencies might be used by other targets.
      To find dependencies that are not used by any target, enable `--all-targets`.
Note: They might be false-positive.
      For example, `cargo-udeps` cannot detect usage of crates that are only used in doc-tests.
      To ignore some dependencies, write `package.metadata.cargo-udeps.ignore` in Cargo.toml.

You need to remove the dependency swift-bridge-build from crates/ffi/Cargo.toml


[FIX] Ensure subjects without imaging sessions are considered in main query

Closes #331

This PR reverts a change to the query template introduced as part of https://github.com/neurobagel/api/pull/326

Changes proposed in this pull request:

Use left join approach for imaging session subquery to ensure that subjects without an imaging session are still included in the results (with a count of 0 imaging sessions)

otherwise, due to the aggregation used in the subquery (GROUP BY ?subject), when the results are joined back to the main query, subjects without imaging sessions may be excluded b/c there are no rows for them in the subquery results

Note that this is not needed for the phenotypic session subquery, because all subjects must have >=1 phenotypic session

Checklist
This section is for the PR reviewer

[ ] PR has an interpretable title with a prefix ([ENH], [FIX], [REF], [TST], [CI], [MNT], [INF], [MODEL], [DOC]) (see our Contributing Guidelines for more info)
[ ] PR has a label for the release changelog or skip-release (to be applied by maintainers only)
[ ] PR links to GitHub issue with mention Closes #XXXX
[ ] Tests pass
[ ] Checks pass

For new features:

[ ] Tests have been added

For bug fixes:

[ ] There is at least one test that would fail under the original bug conditions.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>2
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 96.044%

Totals

Change from base Build<PHONE_NUMBER>2:
0.0%

Covered Lines:
704

Relevant Lines:
733

💛  - Coveralls


Use new action for setUserTypedLocation instead of wrapping it into setPageDetails

r? @jsantell

Looks good; I'd prohibit userTyped being modified by setPageDetails, and consider consistency of pageIndex between these APIs (if this is a property, it should also be a prop on setPageDetails, navigate etc)

Coverage increased (+0.2%) to 87.137% when pulling 462a830729f8522396277076cc35aaf883195b41 on bgrins:SET_USER_TYPED into a6db99bef4c99c83ed8a39bcd40416d0fe4bab7e on mozilla:master.

I'd prohibit userTyped being modified by setPageDetails

Done

consider consistency of pageIndex between these APIs (if this is a property, it should also be a prop on setPageDetails, navigate etc)

Agreed - i'll do that in a follow up

Coverage increased (+0.2%) to 87.19% when pulling 771d741f874354c324b7959e60eaf438b05ae776 on bgrins:SET_USER_TYPED into a6db99bef4c99c83ed8a39bcd40416d0fe4bab7e on mozilla:master.


This can be closed?


Add query_counter and get_query_parameter_u64_with_offset

Not sure about the naming of get_query_parameter_ptr, as ptr doesn't correspond to u32 in get_query_parameter_u32.

Thanks! I'm not sure about the value: *mut () here - could we return the value directly instead?

It's an input, so that won't work. Maybe name it get_query_parameter_with_offset which takes usize?

Oh I see, yeah get_query_parameter_with_offset with usize sounds good!

I've changed this to use the 64-bit variant and renamed the function to get_query_parameter_u64_with_offset.


Spacing after indent in bullet list needs adjustments

Please adjust the text block so that when using indent within a bullet list, there is no spacing until you change from bullet list to text (bullet list ends), as it is in Word.
See #1632 and #1880

From Word:

Spacing after indent in bullet list is adjusted, please verify @meols

Great @millianapia - thanks and approved :smile:


Specify project.version in Readme sample build

Hi,
while migrating .idea format to gradle with your plugin I was getting
version = unspecified in target plugin.xml (overriding the default set in source plugin.xml)
adding project.version = "0.1.0" fixed the issue,
Please check the sample at https://github.com/mfedko/idea-file-language, am I doing something wrong?

Hi, it's supposed that you will maintain plugin version via gradle, so setting project.version in build.gradle is a proper solution.
Anyway, I'll make the changes to restrict patching plugin.xml if project.version is undefined.

Fixed in 0.0.25

Thanks!


use short

Uses short for PathSegment. Results for plaintext microbenchmark
Before
           Method |       Mean |     Error |    StdDev |        Op/s | Scaled | ScaledSD |  Gen 0 | Allocated |
----------------- |-----------:|----------:|----------:|------------:|-------:|---------:|-------:|----------:|
         Baseline |   181.8 ns |  1.692 ns |  1.413 ns | 5,501,495.5 |   1.00 |     0.00 | 0.0002 |      40 B |
              Dfa |   317.2 ns |  6.213 ns |  7.155 ns | 3,152,332.2 |   1.75 |     0.04 | 0.0010 |     168 B |
 LegacyTreeRouter | 2,451.0 ns | 16.982 ns | 15.054 ns |   407,990.9 |  13.49 |     0.13 |      - |     480 B |
     LegacyRouter | 1,345.2 ns | 14.328 ns | 11.964 ns |   743,363.7 |   7.40 |     0.08 | 0.0019 |     344 B |

After
           Method |       Mean |     Error |    StdDev |        Op/s | Scaled | ScaledSD |  Gen 0 | Allocated |
----------------- |-----------:|----------:|----------:|------------:|-------:|---------:|-------:|----------:|
         Baseline |   184.8 ns |  3.759 ns |  3.516 ns | 5,411,169.6 |   1.00 |     0.00 | 0.0002 |      40 B |
              Dfa |   312.5 ns |  2.708 ns |  2.262 ns | 3,199,525.4 |   1.69 |     0.03 | 0.0010 |     168 B |
 LegacyTreeRouter | 2,167.9 ns | 15.722 ns | 14.706 ns |   461,275.4 |  11.73 |     0.22 |      - |     480 B |
     LegacyRouter | 1,476.3 ns | 28.429 ns | 26.593 ns |   677,351.5 |   7.99 |     0.20 | 0.0019 |     344 B |

int16.MaxValue is 32k so that's plenty of space for the URL sizes we allow.

Are those results repeatable? This looks like noise

It might be noise. What I'm trying to do is make the zero-initialization of this less costly


Clean up and debugging interface stresses

@cekees I think we should wrap up this one. Results for the settling velocity are decent (see below)


HLD: drop Patch Version feature

This feature is very advanced and doesn't really fit in to scope of MVP.

Patch Version feature dropped from HLD


Add onChangeEnd handler

Hi! I was running into an issue with allotment where its onChange handler's constant-firing was creating some performance issues in a webapp that I'm working on.
I'd like to propose adding an onChangeEnd callback, which gets called exactly-once when the user either (a) stops-dragging-with-their-mouse or (b) clicks Reset for the layout.

Looks like my PR is no longer needed - closing!

Hi @bryanjclark. Do let me know if there is anything missing in the merged PR that isn't in yours. I really appreciate you taking the time to put together a PR and it's just the fact that I'm merging things in the order they arrived 👍.

Oh it's all good! I'm just excited to have the functionality - was getting some weird lagginess in our frontend from the constant-calling-of-the-callback-function (even with debounce somehow?) so I'm glad there's now an option to just get an update once the drag is complete. Cheers!


Forwarded port details - truncate long arguments

Try the VS Code Remote Node sample
npm install
F5

Notice that the debugger runs some bootstrap processes that have very long arguments which can be overwhelming:

Suggest to truncate the command line after some number of characters, e.g. 30 and show the full name only on hover.

Duplicate of https://github.com/microsoft/vscode/issues/115213


fix(api): required client version to 1.20.0

A new mobile app version was pushed to the store

The new app version is 1.12.0 and not 1.20.0 I don't know how picky the api endpoint is. But I'm working on a patch to auto update the app version based on the version published to the istore.


[BUG] Point in time does not work

What is the bug?
The lib tries to make request to _pit which is wrong and ends in a 400 from opensearch.
How can one reproduce the bug?
Use the lib with PIT against Opensearch 2.6.0
What is the expected behavior?
The lib should use _search/point_in_time and not _pit
What is your host/environment?
Openearch 2.6.0

This PR will handle this: https://github.com/opensearch-project/opensearch-ruby/pull/155

Said PR has been merged.
Check this guide to see how to use the new point-in-time:
https://github.com/opensearch-project/opensearch-ruby/blob/main/guides/search.md#pagination-with-point-in-time


Sidekiq Integration

Enable Sidekiq to handle versions by enable_sidekiq
Define own worker by sidekiq_worker

Closed in favour of another implementation


License?

Great project with some very nice touches! I've learned a lot from it.
What is the license on your code? I'm interested in exploring using some elements in a project I am working on.

Thank you for showing interest in the project. I've added the MIT license.


Use Object.create() instead of Object()

This bug drive me crazy. It cost me 2 hours to find out the issue. And finally I found it was coursed by missing "create" in cloning object.
PLEASE FIX IT AS SOON AS POSSIBLE.

Oh crap, I'm sorry for that! Merged it

Published v2.0.22 containing your fix.

Thanks!


Improve version identification

Would you like to extend the specification of version information for the involved software components?

external/fetch_sources.py already specifies exact versions of third-party components used by CTS. You may substitute libpng and zlib with other versions as well but compatibility is not guaranteed.
Did you have something else in mind?

Are there any more chances for software evolution around variables like "PROJECT_VERSION" from the CMake software build system?

It is not immediately clear to me what benefits maintaining PROJECT_VERSION for CTS would bring. The framework has its own versioning scheme built on top of git commits and tags (see framework/qphelper/CMakeLists.txt).

Do you use only special variables from the other framework?
Can the collaboration be improved between the mentioned software components?

Could you provide a concrete example of a problem that you'd like to solve here?

I would generally appreciate the clarification if version identification is performed in a way which supports software evolution safely. I became curious if you would like to express corresponding data by more dedicated CMake variables while you are using this software build system.

Git, as a version control system, takes care of the versioning. We use the version information provided by Git in the build and include it in the compiled binaries.
If there is a specific need that should be addressed, feel free to create a new issue.


Add markdown editor for editing facility description

add mdxeditor in care to allow editing markdown for facility description field
keep it as adynamic import so it's only loaded when user wants to edit the description
create a pr for form-field-v1 branch
ref: https://github.com/ohcnetwork/care_fe/issues/9523

Hi @sainak , Let me know if I can work on this issue.

I would like to carry this task out @sainak

@srijantrpth @rajku-dev Core team only for now for form-field-v1 branch 👍


Academic Search API: POST documentation sites are missing Request body

The documentation sites for Interpret POST, Evaluate POST and CalcHistogram POST are missing the information for the "Request body", whereas the corresponding GET sites have this information under "Request parameters": Interpret, Evaluate, CalcHistogram
Also, on a different note, there may be some recent server side issues with CORS and preflight OPTIONS requests, rendering the API unusable for some (see here)

@timwoelfle Thank you very much for bringing this to our attention. These APIs appear to be hosted outside the MicrosoftDocs GitHub repository. I am reaching out to the team that supports these services but wanted to see if you engaged the support option at the bottom of the page: Contact Microsoft?

@Mike-Ubezzi-MSFT Thank you for your reply and for reaching out to the right team! I assumed this to be the right place because I have seen other Microsoft Academic Search API related questions being answered here (e.g. this one).

I've also filed another problem with the Microsoft Academic API documentation.

Hi everyone, this documentation has nothing to do with Azure Cognitive Search (recently rebranded from Azure Search).  Can you remove the "search/svc" label?  Due to its labeling, this issue is showing up in our queue but its not actionable.

@timwoelfle We will now proceed to close this thread. If there is a specific issue or recommendation with an article found in the Microsoft Docs repository, please click on the feedback link at the bottom of the page and your detailed feedback will be properly routed. Thank you, ~Mike


1/31 PM Publish

Docs Build status updates of commit 4a03845:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-conceptual/azps-7.0.0/index.yml
:white_check_mark:Succeeded
View (azps-7.0.0)

docs-conceptual/azps-7.1.0/azps-versioning-release-cadence.md
:white_check_mark:Succeeded
View (azps-7.1.0)

docs-conceptual/azps-7.1.0/toc.yml
:white_check_mark:Succeeded
View (azps-7.1.0)

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


Add relatives to API output

After discussion, we agreed that for JIRA 283 we would simply add the relatives object to the API response unconditionally.
Note that I also tidied the routes file a little and left in a small tryout CSS change on the UI for the footer.

Now ready for merge


Empty libm package for Windows

Right now if cmake script requires libm library, we have edit it to exclude checks on Windows. Having empty package that does nothing should help with this problem

Same question about unistd.h

Answer: No.
Reason: Library authors make often wrong assumptions if anything like this is found while configuring. So it does not help, it just moves the problem to a different position.

Thanks for posting this issue. Please reopen this issue if this is still a problem for you.


feat: synchronize docker images to a local ECR repository

Refactor changes out of aws/cdk-ops so that it can be re-used.
Motivation
EcrRegistrySync is also needed for aws-delivlib PR builds and
CodePipeline CI since they also use jsii/superchain as their base
image.

TODO:

[ ] improve api and usage

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

AWS CodeBuild CI Report

CodeBuild project: GitHubPipelineAutoBuildProj-eNGjrh4O6eRH
Commit ID: 23c4e0b63b500821c078f6e16206dd18c1197647
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubPipelineAutoBuildProj-eNGjrh4O6eRH
Commit ID: 32dcbee6d450188ac4b84718193a05add140270d
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubPipelineAutoBuildProj-eNGjrh4O6eRH
Commit ID: bccba9f7109312308e0ef14fd9175c2204cae427
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubPipelineAutoBuildProj-eNGjrh4O6eRH
Commit ID: aaca0db1ffcfc329349be56cd14a996f296914b0
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubPipelineAutoBuildProj-eNGjrh4O6eRH
Commit ID: 1ab1c4ddd66b4fc51a4b5a093ceb90532f016281
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubPipelineAutoBuildProj-eNGjrh4O6eRH
Commit ID: 0294f0509be39384b5cd2783f82ba7b67cdf89a3
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubPipelineAutoBuildProj-eNGjrh4O6eRH
Commit ID: f447065ee3a89678776bdfdfd42f0a7635ddccea
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubPipelineAutoBuildProj-eNGjrh4O6eRH
Commit ID: a8d0906b9409bc0f2d84fabd50a3de5c2449e014
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubPipelineAutoBuildProj-eNGjrh4O6eRH
Commit ID: 8339de6c622c2aa9c78e08a2f81a39af3c1206ba
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubPipelineAutoBuildProj-eNGjrh4O6eRH
Commit ID: d2c7783fc558470a12ec2780cb427bb10ef00c69
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubPipelineAutoBuildProj-eNGjrh4O6eRH
Commit ID: 2127481a87e23abcfe832e664cef3c763b748442
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubPipelineAutoBuildProj-eNGjrh4O6eRH
Commit ID: d86983ab5df26cc191325fa662191724c4b166bc
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubPipelineAutoBuildProj-eNGjrh4O6eRH
Commit ID: d616c9ac6753c68a60cb073cdf9bb406f9192b9f
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubPipelineAutoBuildProj-eNGjrh4O6eRH
Commit ID: e1f021340df901886041352541124d508a9b3be7
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


Train on 2020.  Test on 2021.  No validation set?

To align with ESO's PV forecasts, let's configure nowcasting_dataset to use 2020 for the training set, and use 2021-01-01 to 2021-08-31 for the test set.
Do we need a separate validation set?  I'm not sure we do, given that we're unlikely to use early stopping.  And, "just" a year of training data feels a bit tight, so I'm keen to make sure we use as much of our data as possible for training.  What do you guys think?

is it nice to have a seperate validation set for the ML models to use - i.e so they dont over-fit.
Perhaps as a balance we could do

train: 90% of 2020
validation: 10% of 2020
test: all of 2021

This would be able to do this - just need to turn it on
https://github.com/openclimatefix/nowcasting_dataset/blob/main/nowcasting_dataset/dataset/split/split.py#L152

is it nice to have a seperate validation set for the ML models to use - i.e so they dont over-fit

I'm really sorry, I haven't had enough coffee yet :slightly_smiling_face: please could you explain how the 10% validation data would be used during model training?

Ah, maybe Ive mis understood something. But I thought you can provide various ML models and training dataloader and a validation data loader. Then at the end of each epoch the validation data loader is used to measure some sort of metric. This can be then used for 'early stopping' when training the model. I was using this a bit in 'predict_pv_yield'
Perhaps there is a more modern way to do it, or just a different way to handle this now

Yeah, I'm honestly not sure what's best!
You're right that, if we're using early stopping, then we should have separate test and validation sets.
But, if we're not using early stopping, then I think it's OK to give PyTorch 2021 as PyTorch's "validation DataLoader", so we can see metrics on the "real" test set (although perhaps that's a bit naughty because we'll be optimising hyper params based on the score on the 2021 data).
But, if I've understood correctly, most self-attention papers don't seem to use early stopping:  They just train for as long as they can!  (But, that said, the Perceiver IO paper did go to great lengths to limit over-fitting... maybe that included early stopping, I don't quite remember!)
@jacobbieker do you plan to use early stopping?  What do you think about whether we should split our data two or three ways (train, test & validation)?   :slightly_smiling_face:

I am fine without a validation set, I think its nice to have, so that we aren't optimizing to the 'future' we are predicting for, I think that might skew the results and make our models look better than they actually are. But yeah, just training as long as possible and seeing what happens would also work. I am just a bit hesitant on optimizing the model against the data we are forecasting for directly, that just seems to bias ours to look better. But for now, since we don't have huge amounts of data ready, then its fine, but I'd prefer a validation set once we start training on the whole time we have

So maybe for now we go for
train: 100% of 2020
validation: 0% of 2020
test: all of 2021

Ill create a PR for this - should be to much work

SGTM! Thanks!

relates to #322


fixed command to install package

Q
A

Is bugfix?

New feature?

Breaks BC?

Fixed issues
comma-separated list of tickets # fixed by the PR, if any

👍


fixing highlighting in routing section

Coverage remained the same at 96.262% when pulling 6bd5c1dbb97659d0f1f935f90b9929ef8908c07a on apieceofbart:patch-2 into c74d999dcd6b0627283180992d2e7de23923d472 on donejs:master.

This PR should be closed in favor or #695, which adds the missing header mentioned in original issue #629 and then fixes highlighting offset.


cyn.eth

cyn.eth https://medium.com/@ctremblayperron/list/cyneth-efc82e2eb593

?Sent from my iPhoneOn Jun 18, 2023, at 6:38 AM, Cynthia Tremblay Perron @.> wrote:
cyn.eth @./list/cyneth-efc82e2eb593
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>


⚠ Bofrost.at has degraded performance

In a8bb3f2, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2341 ms

Resolved: Bofrost.at performance has improved in a64509d after 27 minutes.


Add ability to suspend/resume NSOperationQueue

Add ability to suspend/resume NSOperationQueue
Description:
Adds the ability to use the suspended property on operation queue. This was previously implmented but not actually hooked up to stop operations from running while suspended. Adds a new UT to check this case.

:shipit:

:shipit:

:shipit:


Is this available, yet?

Hi All,
I came across this buildpack while trying to integrate OpenTelemetry with a spring boot app. This buildpack is exactly what I'm looking for, but I think it is not available yet. Can you confirm?
I ask because I do not see the buildpack published to docker hub (I hope I have not missed it).
Thanks in advance!

Correct. It's still in development. I don't think we're far off, but I believe @ThomasVitale might have a few more things he wanted to do before we release. I'll let him speak to that more.

Is there a way to test this in advance of release?

@margic you can find instructions on how to test it locally with your own applications in the README file here: https://github.com/paketo-buildpacks/opentelemetry/blob/main/README.md
Feel free to share feedback and ideas to improve it, thank you!

You can run go install -ldflags="-s -w" github.com/paketo-buildpacks/libpak/cmd/create-package@latest to install create-package, then run create-package --source . --destination ./out --version "0.0.1-dev" from the buildpack directory. This will create a compiled version of the buildpack in the ./out directory. You can point pack to that with pack build <all your normal args> -b ./out.

Is there a way I can try this with kpack? I have it all setup but was wondering why the agent isn't getting included.

You need an image to test it. You can build yourself an image, but it's a little tricky. I just built an image and pushed it up to my personal docker hub, if you'd like to try it out, that's the easiest for now.
https://hub.docker.com/r/dmikusa/paketo-buildpacks-opentelemetry
Run pack build <app-img> -b paketo-buildpacks/java -b docker.io/dmikusa/paketo-buildpacks-opentelemetry -e BP_OPENTELEMETRY_ENABLED=true.

Thanks, for creating the container. I want to use it in our pipeline which means, I am only allowed to use official releases. Any idea when this will be Generally Available?

@dmikusa I think we can start preparing the first release. I've just opened a PR with the remaining changes: https://github.com/paketo-buildpacks/opentelemetry/pull/23

@PriyankPa the first release is now out: https://github.com/paketo-buildpacks/opentelemetry/releases/tag/v0.1.0

Hi all! I cut a 0.2.0 release for everyone to try (consider it a RC). If you see any issues please report them. If no issues are reported, we'll bump this to 1.0 shortly.

Version 1.0.0 has been released 2 weeks ago: https://github.com/paketo-buildpacks/opentelemetry/releases/tag/v1.0.0 We should be able to close this issue now.


[select] allow left/right navigation on filter input

When filtering the left/right keys should allow to navigate through the input. This currently clashes with paging so i assume we simply disable paging via left/right when filtering.

yeah I think so. I think navigating through the input is more useful.


Fix: Convert Game class to a namespaced area

Continued from PR #101 ...
This is a large size PR and 98%~ complete so pushing changes. :smiley:

Removes Game class for a namespace.
Added relevant game-* translation units to help break up the large game translation unit.
Removed a lot of member variables of the previous Game class into more local function variables.
Moved out-of-place functions (like tileColor) to better suited translation units.
Introduced loadresource and saveresource translation units.
A lot of functions are now much more "stand-alone" and testable!
Function names (and their parameters required) are much more clearer and understandable.
Repeated code / functionality has been templated. (See Draw{Always,AsOneTimeFlag,OnlyWhen})

--
Note: It may help to go through the commits in age order to understand the critical changes over time.
(There are still a few more changes that could be applied but decided to make a separate PR for them).

NB: As this is a large commit, the PR will be closed via a regular "Merge". :incoming_envelope: :inbox_tray:.
This will keep the commit history for any problems which may arise.
However, this PR can also be closed via "Squash and Merge". :card_file_box:
The trade-off is that the detailed commit history will be lost.

(Will be automatically merged in <72hrs from this message if no objections)

As there are no objections, will merge.


🛠 Allow jupyter as alias for thebe

Alias for option thebe of jupyter #473
Allows for { jupyter: lite }

This is a start at #463.
Future work:

remove the boolean | Object from the binder and server options. We should be explicit in the CLI.
Update the docs should happen in #463

This is a little bit of a smaller change than I had initially imagined, and is mostly refactoring. I have now ensured that thebe/resources/requirements are only added to the project (before they were validated but not used on a page).
This also opens up jupyter: 'lite' and other simple config declarations, but does not change the underlying key (still thebe). This should make any downstream changes pretty simple.

ok, so after this change jupyter and thebe are interchangeable but the string based root value lite needs downstream code to change, correct?


Is fastcomposer good at generalizing concepts in images?

I checked the examples:

It seems to retain the same photorealistic style as that input image and the same facial expression.

Thank you for the questions!

Changing the facial expression is indeed hard. I think this is due to our training where we utilize crops from the original image as conditioning. Retrieval-based training may improve it and test-time conditioning on multiple reference images will also help. We will add this discussion to the paper later.

I think currently stylization works quite well. It is essentially a tradeoff between identity preservation and prompt consistency. If we want to push for style consistency, we can lower the alpha, and get a more stylized image with some loss in identity preservation.


[BUG][sdk] Issue with inferred return type of object literals

Bug Report
Note that, the bug you're reporting may have registered in the issues by another user. Even the bug you're reporting may have been fixed in the @next version. In such reasons, I recommend you to check the old issues and reproduct your code with the @next version before publishing the bug reporting issue.
`npm install --save-dev nestia@next`

When the same error occurs even in the @next version, then please fill the below template:
Summary
Issue with inferred return type of object literals

SDK Version: 1.3.9
Expected behavior:  All types of  my controllers, either parameters types or return type, resolved correctly.
Actual behavior:  Inferred return types of methods that return object literals, resolve to an undefined object __object and it's imported in api/functional/index.ts.

Write detailed description in here.
I have the @core.TypedBody() body: LoginData parameter in the /auth/login POST route of the AuthController.
I return the body and let TS infer the return type.
The type  LoginData for the body parameter gets imported in the generated client sdk successfully and set as input and output types.
But in the /auth/user GET route, I return an object literal {}, and no return type.
Instead of having the built-in type object as type for the output, it adds an import __object, but because I'm not defining a type or interface __object, it is of course undefined and throws the expected error shown in a screenshot (shown below).
Solution Attempt
I then set the return type for the /auth/user route to object and it fixed it.
Code occuring the bug
/* Demonstration code occuring the bug you're reporting */

Write the demonstration code occuring the bug you're reporting.

However, as the nestia is not a typical library who being used by the import statement but a executable program generating the SDK (Software Development Kit), it would be difficult to describe the bug with only the demonstration code.
In that case, you'd better to make a demonstration project occuring the bug to report. After the demonstration repository composition, fill the below bash script section. Of course, if you can describe the bug clearly, without the demonstration project construction, just skip it. Creating the demonstration repository is not essential.
git clone https://github.com/someone/nestia-bug-report-xxx
cd nestia-bug-report-xxx
npx nestia sdk

Write exact return type explicitly please.
I should make it an error with detailed message.

Write exact return type explicitly please.
I should make it an error with detailed message.

I'm confused. Are you suggesting that in order to solve this library generating a strange type, I have to put explicit return type?
Please help me understand.

Nestia is planned to generating SDK library for client developers.
If return type is not defined as an independent DTO, how client developer use it?
Do they have to define duplicate DTO structure looking at object literal expression in your backend server code?
I think this is not sensible.

I read the Code of Conduct.
Did you know respect goes both ways?
You first marked my issue as [invalid], then closed it arrogantly, without even trying to explain why you decided to generate a made up type __object for object literals instead of using the TypeScript built-in object type, which is what's causing this issue  in the first place.
I even went to the generated api/functional/auth/index.ts, removed the __object from the import, and replaced it everywhere with object and it fixed the issue. Because I love to experiment with stuff, before having to open Issues and waste other people's time and energy.
But if this is how you are going to treat consumers and possibly contributors (I love to contribute), then I'm not going to consume or contribute to anything made by you.
I just got a very bad vibe from you and I deal with many maintainers daily, many of them are kind, they take their time to explain, to understand, etc.
I think you are suffering from the Dunning-Kruger syndrome, judging by all the badges you have earned, one of the badges even calls you a "god". I recommend keeping your humility in touch.
I was very hopeful with this library. It sounded great with the premise of

Only one line required, with pure TypeScript type
Runtime validator is 20,000x faster than class-validator
JSON serialization is 200x faster than class-transformer
SDK is similar with tRPC(opens in a new tab), but much advanced

But if the creator/maintainer is going to treat me like this, not even using kind words or greetings to let me know the intention behinds his words to create a non-toxic relationship, then I'll have to find another alternative.
Even though I was left with a bitter taste, I'm going to wish you health, peace, and success.

Sorry for rapid decision without detailed explanation. I will explain the detailed reason why probiting implicit type, even if it is too late.
In TS compiler, __object named type comes when array or object literal expression being used without any type definition. It is possible to analyze those literal expressions by make virtual types. Actually, typia and @nestia/core are already doing it.
However, considering purpose of SDK that delivering to client developers, such imperfection  should not be allowed. Delivered API spec must be clear and have not to make client developers to read backend server code just for understanding DTO spec.

Sorry for rapid decision without detailed explanation. I will explain the detailed reason why probiting implicit type, even if it is too late.
In TS compiler, __object named type comes when array or object literal expression being used without any type definition. It is possible to analyze those literal expressions by make virtual types. Actually, typia and @nestia/core are already doing it.
However, considering purpose of SDK that delivering to client developers, such imperfection should not be allowed. Delivered API spec must be clear and have not to make client developers to read backend server code just for understanding DTO spec.

Wow. That's the kind response I expected, but didn't imagine I would get. Thank you a lot for that.
(Don't want to use my condition or justify my words, but I suffer from Generalized Anxiety and depression and even the easiest task gives me a hard time, I'm always expecting the worse).
With that said, I did my own experimentation and ChatGPT also helped me and I achieved why I needed with the following code:
import * as ts from 'typescript'

function getReturnTypesFromControllers(
  controllerFilePaths: string[],
): string[] {
  const program = ts.createProgram(controllerFilePaths, {})
  const typeChecker = program.getTypeChecker()

  const returnTypes: string[] = []

  for (const filePath of controllerFilePaths) {
    const sourceFile = program.getSourceFile(filePath)

    if (sourceFile) {
      ts.forEachChild(sourceFile, (node) => {
        if (ts.isClassDeclaration(node)) {
          const className = node.name
          if (className) {
            const controllerSymbol = typeChecker.getSymbolAtLocation(className)
            if (controllerSymbol) {
              const classType =
                typeChecker.getDeclaredTypeOfSymbol(controllerSymbol)
              const properties = typeChecker.getPropertiesOfType(classType)

              for (const property of properties) {
                const propertyDeclaration = property.valueDeclaration
                if (
                  propertyDeclaration &&
                  ts.isMethodDeclaration(propertyDeclaration)
                ) {
                  const signature =
                    typeChecker.getSignatureFromDeclaration(propertyDeclaration)
                  if (signature) {
                    const returnType =
                      typeChecker.getReturnTypeOfSignature(signature)
                    const returnTypeString =
                      typeChecker.typeToString(returnType)
                    returnTypes.push(returnTypeString)
                  }
                }
              }
            }
          }
        }
      })
    }
  }

  return returnTypes
}

// Usage example
const controllerFilePaths = ['src/auth/auth.controller.ts']
const returnTypes = getReturnTypesFromControllers(controllerFilePaths)
console.log(returnTypes)

src/auth/auth.controller.ts
import { Controller, Get, Post } from '@nestjs/common'
import { AuthService } from './auth.service'
import core from '@nestia/core'

export interface LoginData {
  email: string
  password: string
}

export interface RegisterData {
  email: string
  password: string
  firstname: string
  lastname: string
  username: string
}

@Controller('auth')
export class AuthController {
  constructor(private readonly authService: AuthService) {}

  @core.TypedRoute.Post('login')
  public login(@core.TypedBody() body: LoginData): LoginData {
    return body
  }

  @core.TypedRoute.Post('register')
  public register(@core.TypedBody() body: RegisterData): RegisterData {
    return body
  }

  @core.TypedRoute.Get('user')
  public user() {
    return {}
  }

  @core.TypedRoute.Get('test')
  public test(): object {
    return {}
  }
}

Code Result Screenshot

I hope this time I could be useful to solve the issue with Nestia instead of waiting for someone else to solve it.
Also this motivated me to try and make my own "mini library" to replicate Nestia, and also add my own transforms/field validation.
Also, yes I'm a strong advocate for being explicit, I always mark my return types even for :void. It was just a curiosity, after I created a Nest project very quickly with some dummy code,  about why Nestia sdk didn't used the object type for an object literal, instead of using the made-up type __object.
Thank you for taking the time to understand my frustration and my intention which is based on good faith.
My apologies for any typo, my main language is Spanish.


darktable: 3.8.1 - 4.0.0

Description of changes
(https://github.com/darktable-org/darktable/releases/tag/release-4.0.0)
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] 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
[x ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 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

[ ] Fits CONTRIBUTING.md.

@goibhniu @flosse @mrVanDalo @paperdigits

Looks good to me if everything builds successfully.
On July 3, 2022 6:56:26 AM PDT, "Leiser Fernández Gallo" @.***> wrote:

Description of changes
(https://github.com/darktable-org/darktable/releases/tag/release-4.0.0)
Things done

Built on platform(s)
[x ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin
[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] 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
[x ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 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
[ ] Fits CONTRIBUTING.md.

@.*** @flosse @mrVanDalo @paperdigits

You can view, comment on, or merge this pull request online at:
https://github.com/NixOS/nixpkgs/pull/180012
-- Commit Summary --

Darktable 3.8.1 -> Darktable 4.0.0

-- File Changes --
M pkgs/applications/graphics/darktable/default.nix (4)
-- Patch Links --
https://github.com/NixOS/nixpkgs/pull/180012.patch
https://github.com/NixOS/nixpkgs/pull/180012.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/NixOS/nixpkgs/pull/180012
You are receiving this because you were mentioned.
Message ID: @.***>

The commit message should have an arrow, like darktable: 3.8.1 -> 4.0.0
Builds and runs for me. (linux-x86_64)
One thing I've noticed:

Upstream requires latest/current lua (5.4) but in nixpkgs lua (without version) references to an older lua (5.2). Still seems to work but maybe lua alias should be a reference to current lua. (But I'm not qualified to judge on this. My knowledge of Lua is non-existent.)

Please fix:
* The commit message should have an arrow, like `darktable: 3.8.1 -> 4.0.0`
  (As described at: https://nixos.org/manual/nixpkgs/stable/#submitting-changes-making-patches)

Builds and runs for me. (linux-x86_64)

Wondering: Upstream requires latest/current lua (5.4) but in nixpkgs lua (without version) references to an older lua (5.2). Still seems to work but maybe lua alias should reference to latest/current lua. (But I'm not qualified to judge on this. My knowledge of Lua is non-existent.) [My preference would be to have lua (without version) to refer to latest version of it.]

Regarding the version of lua, the change was in version 3.8.0 so I'm not sure if bumping the version is required to be honest, but just in case I will bump it as well.

Please fix:
* The commit message should have an arrow, like `darktable: 3.8.1 -> 4.0.0`
  (As described at: https://nixos.org/manual/nixpkgs/stable/#submitting-changes-making-patches)

Builds and runs for me. (linux-x86_64)
Wondering: Upstream requires latest/current lua (5.4) but in nixpkgs lua (without version) references to an older lua (5.2). Still seems to work but maybe lua alias should reference to latest/current lua. (But I'm not qualified to judge on this. My knowledge of Lua is non-existent.) [My preference would be to have lua (without version) to refer to latest version of it.]

Regarding the version of lua, the change was in version 3.8.0 so I'm not sure if bumping the version is required to be honest, but just in case I will bump it as well.

I'm not telling you to bump lua. Just was trying to understand if we should be tracking latest lua instead. Maybe someone had a good answer I wanted to know.

Lua does changes from version to version, so if they advise using 5.4 it's better to do it. I just tested it and it builds fine.

Lua does changes from version to version, so if they advise using 5.4 it's better to do it. I just tested it and it builds fine.

You could open a new PR for bumping lua alias to latest (5.4). And make sure to ask lua users/maintainers to provide feedback on it.

The lua alias is already at 5.4 and is defined in all-packages.nix (i think) and is passed into this drv.
On July 3, 2022 12:30:20 PM PDT, superherointj @.***> wrote:

Lua does changes from version to version, so if they advise using 5.4 it's better to do it. I just tested it and it builds fine.

You could open a new PR for bumping lua alias to latest (5.4). And make sure to ask lua users/maintainers to provide feedback on it.
--
Reply to this email directly or view it on GitHub:
https://github.com/NixOS/nixpkgs/pull/180012#issuecomment-1173158286
You are receiving this because you were mentioned.
Message ID: @.***>

Lua for darktable should already be at 5.4 it's call in all-packages.nix I think.
On July 3, 2022 12:25:26 PM PDT, "Leiser Fernández Gallo" @.***> wrote:

Lua does changes from version to version, so if they advise using 5.4 it's better to do it. I just tested it and it builds fine.
--
Reply to this email directly or view it on GitHub:
https://github.com/NixOS/nixpkgs/pull/180012#issuecomment-1173157617
You are receiving this because you were mentioned.
Message ID: @.***>

To clear the confusion:
lua references to lua_5_2
  lua5 = lua5_2_compat;
  lua = lua5;

But yes, darktable is indeed using lua5_4.
  darktable = callPackage ../applications/graphics/darktable {
    lua = lua5_4;
    pugixml = pugixml.override { shared = true; };
  };

So, in a sense, we were both right.
My wondering was, why lua is not tracking latest lua. In that case, it wouldn't be necessary to hardcode the lua version for dark-table. But yes, in this case, it wouldn't make much of a difference. So no action is needed indeed.

To clear the confusion:
In top-level/all-packages.nix, lua references to lua_5_2:
  lua5 = lua5_2_compat;
  lua = lua5;

But yes, darktable is indeed using lua5_4.
  darktable = callPackage ../applications/graphics/darktable {
    lua = lua5_4;
    pugixml = pugixml.override { shared = true; };
  };

So, in a sense, we were both right. My wondering was, why lua is not tracking latest lua. In that case, it wouldn't be necessary to hardcode the lua version for dark-table. But yes, in this case, it wouldn't make much of a difference. So no action is needed indeed.

I'm not a nixos dev but a neovim plugin one, which gives me the experience to say that every lua version is a different language. I assume lua tracks lua5.2 because most of the packages use that one.

My expectation is package_name without a version should track latest version of package (and not an older fixed version). In some cases that doesn't happen but I find that a mistake. Because if an application needs an older version it should lock to it and not track latest. I'm not proposing any further changes here.


Fine tune events triggering workflows to avoid running useless jobs.

This is an attempt at avoiding duplication of workflows when they are modified (only one of the pull_request and pull_request_target events should match and the pull_request event should only match when the workflow itself has been updated).

I'll open some test PRs with this branch as the base to confirm that this logic works.

This works as expected. No need to wait for the workflows here to pass to merge this one.

@Zimmi48 I encountered a case (https://github.com/math-comp/Abel/pull/75) where this failed:

I deleted some old nix action files
added new ones (i.e. edited bundles in config.nix)
git recognized new files as renaming of old ones
so github apparently didn't recognized the new files as edited and worth trigerring the pull_request target

Don't know if that's a known bug in github action or if there is any nice workaround, but for the time being, maybe we should consider keeping the ** in pull_request?

Was the issue specifically with the files that were "renamed" (according to git) without being modified? Are you saying that the workflow that they defined was triggered neither by the pull_request_target workflow (because they were recognized as edited in this case) nor by the pull_request workflow (because they were not recognized as edited)?

Ah, you packed the two changes in a single PR!
Then yes, it seems possible that this is related. We should be on the lookout for other cases of workflow files being renamed to see if the problem is there again. In this case, maybe we should open a support request from GitHub.


added related routeTables to the Azure Resources list Action

made Geneva Action continue if vnetClient.Get() fails.

Which issue this PR addresses:
Fixes https://msazure.visualstudio.com/AzureRedHatOpenShift/_workitems/edit/7688600/
What this PR does / why we need it:
This PR gets any RouteTable objects attached to subnets in the cluster Vnet. It will help us diagnose
Test plan for issue:
There's new unit tests in /pkg/frontend/adminactions/resources_list_test.go.
The "basic coverage" case has been extended with a subnet which contains a route table.
The new "vnet get error" case checks if the GET succeeds even if there's an error getting the Vnet.
Manual check:
Created a RouteTable and attached it to a subnet of one of my dev clusters. Performed:
curl  -k -H 'Content-Type: application/json' "https://localhost:8443/admin/subscriptions/${AZURE_SUBSCRIPTION_ID}/resourcegroups/${RESOURCEGROUP}/providers/Microsoft.RedHatOpenShift/openShiftClusters/${CLUSTER}/resources" | jq

with env vars set and checked if the route table appears in the results.
Is there any documentation that needs to be updated for this PR?
No documentation changed. Route Tables appear as just another resource in the JSON result of an existing Geneva Action. There's no direct references to route tables (the Azure ones) in the SOPs or other wiki pages.

needs rebase now

Applied requested changes and rebased.

Resolved the issues, simplified the arguments in appendAzureNetworkResources since the receiver already has the required clients.

thanks!


bug: using pydocstyle (D) does not enable D417

Description of the bug
selecting pydocstyle (D) does not enable D417
issue might be linked to using 'convention = "numpy"'
To Reproduce
ruff.toml:

[lint]
select = [ "D"]

[lint.pydocstyle]
convention = "numpy"

example.py:
(docstring error see var2 -> var3)

'''Example module that contains a function with type hints.'''

def example(var1: int, var2: str) -> str:
    '''Concat variables.

    Parameters
    ----------
    var1 : int
        This is an integer argument
    var3 : str
        This is a string argument

    Returns
    -------
    str
        This is a string that contains the values of the two arguments
    '''
    return f"var1: {var1}, var2: {var2}"

ruff check
All checks passed!

(Expected a D417 error)
change ruff.toml:
[lint]
select = [ "D", "D417"]

[lint.pydocstyle]
convention = "numpy"

or
change ruff.toml:
[lint]
select = [ "D"]

ruff check
D417 Missing argument description in the docstring for `example`: `var2`
  |
4 | def example(var1: int, var2: str) -> str:
  |     ^^^^^^^ D417
5 |     """Concat variables.
  |

(Expected D417 Error showed up)
Also: should there not be an error for "var3" in the docstring?
Expected behavior
Selecting a rule enables all stable rules of the set.
Environment information
ruff 0.8.3
Python 3.10.15

Yep - this rule is currently only supported for the google convention. Apologies!
From the docs:

This rule is enabled when using the google convention, and disabled when using the pep257 and numpy conventions.

It would be nice to get some level of information about this. Are there any other excluded? Are there any other Rules with this behavior? When I'm using one Rule I don't always want to second guess if it uses all the subrules.
Thank you for your time

That's understandable. The FAQ section lists the enabled rules by convention


Problem with fastSetValue on Material UI Components

The problem
Material UI is one of the most popular React Components library.
And when i'm trying to use Selenide with fastSetValues (setting values via js) it's not working correctly.
Details
When Selenide sets value via JS Material UI component ( Autocomplete ) do not call hooks like onInputChange and others.
Tell us about your environment

Selenide Version: 5.8.0
Yandex browser: <IP_ADDRESS>5
Browser Driver Version: 79
Selenium Version: embedded in Selenide
OS Version: mac OS

Code To Reproduce Issue [ Good To Have ]
To reproduce the bug you may run the test:
@Test
    void check() {
        Configuration.fastSetValue = true;
        open("https://rusakovstas.github.io/material-autocomplete/");
        $(byText("Вбейте что нибудь или скопируйте")).closest("div").$("input").setValue("123");
        $(byText("Поймали логику!")).shouldBe(visible);
    }

For now it's failed. If you remove Configuration.fastSetValue = true; it works fine.

Hi!
I've finally found the solution of this question! It's really simple)
To set value via js properly for Material UI you have to do this by setAttribute('value', 'some text');
Not just element.value =
I think the reason in some JS Proxy or something like that.
I even have changed the method setValue in Selenide and it's working (after local install)!
But now:

i can't push branch (getting 403). Maybe there are some rules for that?
i'm not sure how can i write the test for this?

Just in case code for fix is pretty simple:
private String setValueByJs(Driver driver, WebElement element, String text) {
    return driver.executeJavaScript(
        "return (function(webelement, text) {" +
            "if (webelement.getAttribute('readonly') != undefined) return 'Cannot change value of readonly element';" +
            "if (webelement.getAttribute('disabled') != undefined) return 'Cannot change value of disabled element';" +
            "webelement.focus();" +
            "var maxlength = webelement.getAttribute('maxlength') == null ? -1 : parseInt(webelement.getAttribute('maxlength'));" +
            "webelement.setAttribute('value', " +
            "maxlength == -1 ? text " +
            ": text.length <= maxlength ? text " +
            ": text.substring(0, maxlength));" +
            "return null;" +
            "})(arguments[0], arguments[1]);",
        element, text);
  }

P.S. As far as i can see - all tests works properly.

@rusakovStas Good catch!
I created a fix in Selenide 5.8.1-SNAPSHOT - can you try it?

Thank you!
I tried - it works. But unfortunately not for all cases(
i'd like to add a few more tests.

It looks like another cases doesn't work cause another reasons. After all, the case with custom business logic works. So, i think that's enough for now.

By the way, for the feature, is this normal to use githubactions pages for Integration tests in Selenide? I think it's really convenient)

@rusakovStas We currently use TravisCI for Selenide builds. Yes, we could migrate to Github actions, but I don't know if it really changes our lives drastically.

@rusakovStas Something is wrong with PR https://github.com/selenide/selenide/pull/1076. It breaks a lot of tests in some my my work projects. Could not figure out why.

Hm.
It's weird. I read this article and thought that it would be more right to change value attribute. But it's good to have tests) So then i better set attribute via execute command like in your selectBootstrap

P.S.
I tried that way:
  private String setValueByJs(Driver driver, WebElement element, String text) {
    return driver.executeJavaScript(
        "return (function(webelement, text) {" +
            "if (webelement.getAttribute('readonly') != undefined) return 'Cannot change value of readonly element';" +
            "if (webelement.getAttribute('disabled') != undefined) return 'Cannot change value of disabled element';" +
            "webelement.focus();" +
            "var maxlength = webelement.getAttribute('maxlength') == null ? -1 : parseInt(webelement.getAttribute('maxlength'));" +
            "var clearText = "+
            "maxlength == -1 ? text " +
            ": text.length <= maxlength ? text " +
            ": text.substring(0, maxlength);"+
            "webelement.setAttribute('value', clearText);" +
            "webelement.value = clearText;"+
            "return null;" +
            "})(arguments[0], arguments[1]);",
        element, text);
  }

It doesn't work for my case.

Hi, we also found this issue and evaluated it a little bit further and created an issue at MaterialUI https://github.com/mui-org/material-ui/issues/19346. The issue seemed to be exclusive to the ChromeDriver.

Hi @occupant23)
It's cool) Will monitor developments)

But for now you could use custom command via execute method)
For my case i wrote command like this:
public static Command<SelenideElement> setValueAttribute(String value) {
       return (proxy, locator, args) -> {
           Selenide.executeJavaScript("arguments[0].focus(); arguments[0].setAttribute('value', arguments[1]);", proxy, value);
           events.fireEvent(locator.driver(), proxy, "keydown", "keypress", "input", "keyup", "change");
           return proxy;
       };
    }

And in tests it's look like:
$("input").execute(setValueAttribute("some value"));

@rusakovStas Thank you for sharing the knowledge.
Do I correctly understand that there is nothing to fix in Selenide?
Can we close this issue then?

So, since the fix https://github.com/selenide/selenide/issues/1074#issuecomment-593118940
broke tests, i think there is nothing to do.
Issue may be closed.

You could upvote the issue, so that it's not postponed.

done


Provider of DB is now selected by default

By default, the SqliteModelConfigurator is selected.

 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.


UOM of utility_meters and energy_sensor?

Any chance to adjust the UOM of utility_meters and energy_sensor? Until now, every other in my installation has the unit Wh, and If I want to display in cards, etc., I would have to multiply here (only) for the entity created via this integration. Would really love to be able to adjust from kWh to Wh here (of course with values*1000).

Work in progress #847

This has been implemented. You can test this by installing the master branch.
You can set energy_sensor_unit_prefix now on global level or per sensor.
i.e.
  - platform: powercalc
    entity_id: light.spot_bar
    energy_sensor_unit_prefix: M
    linear:
      min_power: 0.05
      max_power: 5.3

Looks like HA restores the state of the energy sensor regardless if the unit prefix has changed. So I would suggest to reset the sensors after you change the unit prefix.
The utility_meters are based on the energy sensor and look at the unit of measurement of the energy sensor, so did not have to change anything for that.

Will do it. But how to understand the energy_sensor_unit_prefix. Thought it will be unit_of_measurement as in the daily_fixed_energy.
I can live with energy_sensor_unit_prefix as well, but how to set it to Wh instead of kWh?

It's in the readme. I have set it to the same options as the riemann integration sensor, because that is the one I am creating under the hood.
To set it to Wh you can set energy_sensor_unit_prefix: none
The default is k, but you can also set M, G, T for MWh, GWh and TWh. The last one is only relevant for Google data centers ;-)

Ahhh. Didn't expect, that the readme has already updated as well. 😂 Will test later.

Yeah, the readme is shown from the default branch (which is master). Sometimes it confuses users because they expect to be able to use a certain setting in latest stable, but this is not always the case.

It only confuses me, that you are that fast, even with documentation. 😉
Am I wrong, that the master is not containing the new naming, etc. Then it would be hard to test it, because I have just changed all my namings and would have to start all over again.

The new naming is also in master. Seems you somehow installed an old version of master when you still got the old naming.
Did you install with HACS or manual?

Didn't update before my question. Updated to beta2 via HACS and only wanted to double-check, if I lose this changes form beta2 if I install Master manually, because beta2 could be on another branch.
But saw now, that you have created beta3. So I installed via HACS. But currently I'm stuggling to get the old kWH entries and entities gone. Completely deleted them, but history is still there in kWh after recreation. Reset isn't helping either. Will try more or wait some minutes, what will happen.

Even with new sensors (tried fixed_energy), the global
energy_sensor_unit_prefix: none
is not taken into account. 😥

I will have another look tomorrow. This setting won't work with daily_fixed, only with the normal energy sensors.
Btw could you have a look into the energy sensors attributes in developer tools? What unit_of_measurement is shown there?

That is, what I said. Sensors attributes in developer tools are always kWh, if I used the global energy_sensor_unit_prefix setting. For all kind of powercal-sensors. the fixed_energy were only an example. Same for new fixed media_player, etc.
Now with local energy_sensor_unit_prefix setting.
Groups of hue lights: Not working
hue lights: Working inside and outside groups
light fixed: working
binary sensor fixed: working
sensor fixed: working
media player fixed: working
group of vacuums: Not working
vacuuums fixed, etc: Working
daily_fixed_energy: Not working
Summery:
Global settings: completely not working
Local settings, working partly, but at least not for groups and not for daily_fixed_energy

Ah I misunderstood. I thought it was never working for you, but only global setting was not working.
I have found this bug, and have it resolved. Will do a commit and PR tomorrow.
Also need to have a look into groups. You are right these are still forced to kWh. And maybe also daily_fixed, depending on how difficult it is to implement.

I have also implemented the unit prefix for the group sensors and daily fixed sensors.
Will issue a new beta within an hour.

More than great. Will test it directly, when the beta is out.

beta v0.23.0-beta.4 just released

Testfeedback: First time ever here, booting is not possible / stagnating. Installed beta 4 and roboot is not possible anymore. With installed beta4 yes, but with powercal in yaml it is hanging up completely. Even ha ssh reboot or hassio restart is not possible anymore. So power off/on is not good, but the only possibility here.

hmm not sure what causes this, however you can try beta.5 first which also contains a fix which prevented powercalc (and potentially HA) to be loaded correctly.

Will try. I have already tried with only
  - platform: powercalc
    entity_id: light.galerie
    name: Galerie
    fixed:
      power: 100

this does not harm the reboot.
And wanted to iterate to the new, groupd and daily_fixed. I will do so now with beta5

Ok good to know you were able to succesfully start with just a simple sensor. Just enable one by one and see which one is the culprit. Also keep an eye on the error logs to see if we can get any clues there.

Did so. The topic of the log, that there isn't any error or any progress in the log, if this is happening. And it was reproducible with powercalc and working every time without.
But until I come to the clue, here my feedback:
Groups Now working
daily_fixed_energy: Partly working,
Partly because: the utility meters are always setting and returning to kWH, even for new test entires. There is login statistiks as well: "The unit of the statistics in your database for this entity is not a supported unit for the device class of the entity, energy. It should be kWh."
The difference I see, is that for daily_fixed_energy there is a state class total_increasing, whereas your others, including groups have total. But if this is the reason for the problem, I don't know.
And for the problem, I will create a separate issue. Most probably not related to the recent changes. Before your betas this morning, I adjusted one existing daily_fixed_energy sensor. I'm not sure anymore if I have rebooted before the betas, but now, with this change the booting stops forever (fortunately ssh, config-directory, etc. are still accessible), see https://github.com/bramstroker/homeassistant-powercalc/issues/857

Partly because: the utility meters are always setting and returning to kWH, even for new test entires. Then energy_sensor is fine. There is login statistiks as well: "The unit of the statistics in your database for this entity is not a supported unit for the device class of the entity, energy. It should be kWh."

Maybe you'll have to wait a bit for the utility_meter to cycle, than it will look at the latest state of the energy sensor and it will see this is Wh now. For which entity do you see this statistics error? Do you have a screenshot?

No, the returning is later. After update cycle it is set to Wh, but later (reboot, whatever check) it was returning to kWh.
But why ever, now it is back to Wh and stable until now. I will report back, if it is happening again.

I think HA only writes to core.restore_state each hour or something like that. When you restart in the meantime than HA will restore an old state.
Normally nobody will change the unit_prefix after setting it up initial, so that HA is acting up a little on that is expected.
When everything stabilizes after a few hours and you don't have any issues I think we can release the stable.
Keep me updated if you have any problems today.

Will do. But it happened with a new greenfield test sensor. There was no history before. But I'll see.

Will do. But it happened with a new greenfield test sensor. There was no history before. But I'll see.

Ah, I can remember when I looked at the utility_meter code some time ago the unit_of_measurement was None when initially created. Then when a cycle is done it will change the unit to whatever the underlying energy sensor has.
I assume HA will set to kWh when an energy sensor has an energy device class and no unit_of_measurement available.
So this is HA core behaviour (maybe considered bug) which I cannot change.

Until now, everything is fine now. Global settings, Local settings. Different Sensor types.
Very great to have this enhancement so I can remove all the cluttered 1000x in the sum templates, etc. Wonderful integration. Getting even better now!