pdo-crypto-lib integration

What this PR does / why we need it:
it add the Private Data Objects project as a module to compile and integrate its crypto library.
Special notes for your reviewer:
In this PR, the crypto lib is only compiled and linked in some executables, but not actually used.
Packages using this library will be pushed in separate PRs.
Does this PR introduce a user-facing changes and/or breaks backward compatability?:
no
Signed-off-by: Bruno Vavala<EMAIL_ADDRESS>

question: glancing through the files, presumably, private-data-objects repo will be added as a sub-module under common/crypto/pdo and you will add a corresponding .gitmodules stanza?

question: glancing through the files, presumably, private-data-objects repo will be added as a sub-module under common/crypto/pdo and you will add a corresponding .gitmodules stanza?

Yes it/I will, but it's not right now -- the PR is WIP; as PDO adapts, I will add the submodule.

. Would be nice to also run the crypto tests when building here, not only when building PDO ....

Good idea, I have added a todo

. Would be nice to also run the crypto tests when building here, not only when building PDO ....

Good idea, I have added a todo

@g2flyer it turns out that the tests in PDO need some refactoring:

they rely on common
they use pdo's base64 package
they are under tests where also state tests are called, which need common.
I will open an issue for this (to document that we need crypto tests).
Anyway, for the moment, it would not be much of a gain to run those tests here too.

I really was too liberal in the approval for the PDO PR ;-)

No, you were not.

I somewhat expected that there might be some smaller issues we might discover via this PR.

It is not an issue:

the adopted library is already tested as part of PDO
FPC has currently no (different) tests for the crypto part
any test can already be implemented separately now

I agree that it's not worth here to run all other tests (as this almost certainly brings other unwanted sw and config dependencies from PDO). We should keep this in mind though when touching any related part in PDO again (similar to the types.cpp issue)

yes, and yes -- I have a todo to document this.

Looks in general good, just the suggested consistency of defaults in config.mk and i'm happy :-)

Really in this PR?
I will make you happy as part of the next one - these modifications have nothing to do with the crypto lib integration.

Looks in general good, just the suggested consistency of defaults in config.mk and i'm happy :-)

Really in this PR?
I will make you happy as part of the next one - these modifications have nothing to do with the crypto lib integration.

oh, c'mon. You already touched the two files and did half of the job....

I would like to see a "small" test in ecc_enclave which uses the new crypto lib. Something easy just to have some code usage that shows that the integration is successful.

I have added a code snippet to use the crypto library.
Here some notes:

the snippet simply creates a keys and dumps the PEM encoding;
the snippet will be removed
common/types.h has been renamed to fpc-types.h

Also, would it make sense to hide the pdo crypto behind an fpc crypto interface? So we may have the chance to swap out pdo dependency if needed in the future?

This is the exact reason why we created the pdo crypto lib in the first place. It's actually a wrapper of openssl, that's it! So unless you want to create a wrapper-of-a-wrapper, I would suggest taking a quick look at its headers.

Last, let's pull the commits from #338 here as this makes it easier to review.

This PR is self-contained and does not need 338.


Error 404 without any header

Laravel Version: 5+
PHP Version: 7+

Description:
I was just trying to replicate the abort 404 with a header:
 abort(404, 'testing', ['White-Label' => true]);
and I found something curious. Is there any reason why the 404 is not showing the Header like all the others?
Application.php
    {
        if ($code == 404) {
            throw new NotFoundHttpException($message);
        }

        throw new HttpException($code, $message, null, $headers);
 }

Why don't do like this?
    {
        if ($code == 404) {
            throw new NotFoundHttpException($message, null, $code, $headers);
        }

        throw new HttpException($code, $message, null, $headers);
    }

Thanks in advance, cheers!

Probably an oversight.

Hi there,
Thanks for reporting but it looks like this is a question which can be asked on a support channel. Please only use this issue tracker for reporting bugs with the library itself. If you have a question on how to use functionality provided by this repo you can try one of the following channels:

Laracasts Forums
Laravel.io Forums
StackOverflow
Discord
Larachat
IRC

However, this issue will not be locked and everyone is still free to discuss solutions to your problem!
Thanks.


Fix a wrong particle in "Poetry and PEP-517"

Pull Request Check List
This is just a reminder about the most common mistakes. Please make sure that you tick all appropriate boxes.  But please read our contribution guide at least once, it will save you unnecessary review cycles!

[ ] Added tests for changed code.
[ ] Updated documentation for changed code.

Note: If your Pull Request introduces a new feature or changes the current behavior, it should be based
on the develop branch. If it's a bug fix or only a documentation update, it should be based on the master branch.
If you have any questions to any of the points above, just submit and ask!  This checklist is here to help you, not to deter you from contributing!

Good catch! Thank you!


provide a better check for duplicate names

Currently the name is only checked for some predefined rules to make it openshift resource name friendly. In addition there need to be checks if the name you want to use already exists in the model.

please create related JIRA isseu in FUSETOOLS2 project as we agreed durign team meeting. it allows to give more visibility to everyone, especially for QE team.


suffix action_version meta if there is a mismatch with the latest on GitHub

In entry.sh, when we post action_version meta let's do a check: go to GitHub and see what is the version of the zerocracy/judges-action latest release. If there is a mismatch, let's modify the meta and make it look like this:
0.0.38!0.0.39

Here, 0.0.38 is the current version being used, while 0.0.39 is the one available on GitHub releases.

@yegor256 may I try this one?

@Yegorov go ahead, please

@yegor256 please close


CasperJS test won't return after execution

I'm having a problem getting casperjs test to exit after execution, I have to hit CTL-C to exit execution.
//misc.js
var require = patchRequire(require);
var site = {
goToSite: function (url) {
casper.start(url, function checkSite() {
this.test.assert(this.getCurrentUrl() === url, 'Url is: ' + this.getCurrentUrl());
this.test.assertHttpStatus(200, 'HTTP status code 200 OK');
}
);
},
login: function () {
    casper.then(function fillTheForm() {
            this.fill("form[action='/auth/login']", {
                'email'<EMAIL_ADDRESS>                'password': 'pass'
            }, true);
        }
    );
}

};
module.exports.site = site;
/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
// test.js
var system = require('system');
var misc = require('./misc');
casper.options.logLevel = "debug";
casper.options.verbose = true;
casper.test.begin('Cow can moo', 2, function suite(test) {
var url = "http://ym.cms2cms/auth/login";
misc.site.goToSite(url);
misc.site.login();
casper.run(function () {
    test.done();
});

});
////////////////////////////////////////////////////////////////////////////////////////////////////////
// terminal
[info] [phantom] Starting...
[info] [phantom] Running suite: 3 steps
[debug] [phantom] opening url: http://ym.cms2cms/auth/login, HTTP GET
[debug] [phantom] Navigation requested: url=http://ym.cms2cms/auth/login, type=Other, willNavigate=true, isMainFrame=true
[debug] [phantom] url changed to "http://ym.cms2cms/auth/login"
[debug] [phantom] Successfully injected Casper client-side utilities
[info] [phantom] Step checkSite 2/3 http://ym.cms2cms/auth/login (HTTP 200)
PASS Url is: http://ym.cms2cms/auth/login
PASS HTTP status code 200 OK
[info] [phantom] Step checkSite 2/3: done in 1564ms.
[info] [phantom] Step fillTheForm 3/3 http://ym.cms2cms/auth/login (HTTP 200)
[info] [remote] attempting to fetch form element from selector: 'form[action='/auth/login']'
[debug] [remote] Set "email" field value to<EMAIL_ADDRESS>[debug] [remote] Set "password" field value to ******
[info] [remote] submitting form to /auth/login, HTTP POST
[warning] [remote] unable to submit form
[info] [phantom] Step fillTheForm 3/3: done in 1601ms.
[info] [phantom] Done 3 steps in 1602ms
PASS 2 tests executed in 1.596s, 2 passed, 0 failed, 0 dubious, 0 skipped.

Where is the test defined, of which the done() method is called in the run callback?

As part of a cleanup effort:
Looks to be a stale help request. Assuming you've moved on to better and cooler things.  Please feel free to re-open if this is still an active issue for you and we'll try our best to help out.


Deploy Eidos on production hardware

@tgoodyear is setting up the Eidos webapp on prem.
Open Questions:

How do we change the port that it runs on?
Can we modify the rules without restarting the service?

@jpfairbanks oh no, my intention wasn’t to suggest using the shell command line tool, just to communicate that I’ve come across an ability to reload grammars and then of course plug-in wherever it makes the most sense. :)

From: James<EMAIL_ADDRESS>Sent: Thursday, December 13, 2018 8:23:25 AM
To: jpfairbanks/SemanticModels.jl
Cc: Appling, Scott; Mention
Subject: Re: [jpfairbanks/SemanticModels.jl] Deploy Eidos on production hardware (#17)
@scottagthttps://github.com/scottagt thanks for finding that. It look like that is available from the Eidos shell command line tool, but we could probably add a route that calls that ieSystem.reload() function and be be g2g. It looks like there is a list of configuration variables that get reloaded by that function https://github.com/clulab/eidos/blob/386386b11c35b8e63dde0128cc305db008f78fd4/src/main/scala/org/clulab/wm/eidos/EidosSystem.scala#L84 for example def entityRulesPath: String = eidosConfString
@tgoodyearhttps://github.com/tgoodyear, On the "how do I change the port" question I see that docker is one solution (cf PR clulab/eidos#529https://github.com/clulab/eidos/pull/529) and maybe just pass it as first CLI parameter (cf clulab/eidos#24 (comment)https://github.com/clulab/eidos/pull/24#issuecomment-359610611)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/jpfairbanks/SemanticModels.jl/issues/17#issuecomment-446966468, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AYtl0M_zjwLYqgbPAP-m2xh5m0rm-yG7ks5u4lTNgaJpZM4ZQ1LH.

Sounds good, will do, thanks for finding.
Trevor
On Thu, Dec 13, 2018 at 9:22 AM Scott Appling<EMAIL_ADDRESS>wrote:

@jpfairbanks oh no, my intention wasn’t to suggest using the shell command
line tool, just to communicate that I’ve come across an ability to reload
grammars and then of course plug-in wherever it makes the most sense. :)

From: James<EMAIL_ADDRESS>Sent: Thursday, December 13, 2018 8:23:25 AM
To: jpfairbanks/SemanticModels.jl
Cc: Appling, Scott; Mention
Subject: Re: [jpfairbanks/SemanticModels.jl] Deploy Eidos on production
hardware (#17)
@scottagthttps://github.com/scottagt thanks for finding that. It look
like that is available from the Eidos shell command line tool, but we could
probably add a route that calls that ieSystem.reload() function and be be
g2g. It looks like there is a list of configuration variables that get
reloaded by that function
https://github.com/clulab/eidos/blob/386386b11c35b8e63dde0128cc305db008f78fd4/src/main/scala/org/clulab/wm/eidos/EidosSystem.scala#L84
for example def entityRulesPath: String =
eidosConfString
@tgoodyearhttps://github.com/tgoodyear, On the "how do I change the
port" question I see that docker is one solution (cf PR clulab/eidos#529<
https://github.com/clulab/eidos/pull/529>) and maybe just pass it as
first CLI parameter (cf clulab/eidos#24 (comment)<
https://github.com/clulab/eidos/pull/24#issuecomment-359610611>)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<
https://github.com/jpfairbanks/SemanticModels.jl/issues/17#issuecomment-446966468>,
or mute the thread<
https://github.com/notifications/unsubscribe-auth/AYtl0M_zjwLYqgbPAP-m2xh5m0rm-yG7ks5u4lTNgaJpZM4ZQ1LH

.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jpfairbanks/SemanticModels.jl/issues/17#issuecomment-446985453,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAHHy6-PhnIUHS4tcfUm7_3mB6ZkoeYIks5u4mKsgaJpZM4ZQ1LH
.

After our call with team Clulab, I think we should run the CLI app they wrote for us and put the output into a solr store.
PR pending with JSON output. https://github.com/ml4ai/automates/pull/6


@conda-forge-admin, please add user @consideratio

Adding myself as a maintainer here as well following being added in PyPI: https://pypi.org/project/gh-scoped-creds/

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I added user @consideratio in conda-forge/gh-scoped-creds-feedstock#2.


Property route undefined on replacement of route

Hey Leo,
thanks for looking into https://github.com/LeoLeBras/react-router-navigation/issues/23 and updating the Renderer. The rendering of multiple cards is not a problem anymore. However, there is now an error inside the NavBar:

I'm using the newest release candidate:
"react-router-navigation": "^1.0.0-rc.2",
I looked into the code and I think I've found something. In the DefaultRenderer replacing
return [   ...acc.slice(0,indexOf),   scene ]
with
return [...acc]
and therefore, using the last occurrence in case of finding a duplicate index fixed it for me. With the old code the newly replaced route was simply sliced of again and replaced by the old one. However, the scene in the ownProps was still the new one, but could not be found in the newly generated scenes, which resulted in the exception.
Thanks for looking into that and keep up the good work,
Georg

Hello @georgberecz ,
I can't reproduce your issue. You should consider creating a minimal test case to demonstrate the issue you're having 😀

Wasn't it fixed by #25?

@georgberecz ?

Hi @georgberecz! Did you give a shot to the new ß3? Feel free to keep us update about your issue :)

Closing due to inactivity

Thanks @georgberecz
This actually worked
return [ ...acc.slice(0,indexOf), scene ]
with
return [...acc]
I was getting the same error when using history.replace("...") the second time. It works the first time though.

@insaneinc01 Do you have an example (or a Github) repo that reproduces the issue?

This should be fixed in 1.0.0-rc.5


Remove stray .orig files

Another small thing: I found some .orig files originating from this commit: 56db882059468c9af278f6e01a8ef81eff331d5e, probably a result of conflicts. This PR removes them all :)

Shall we add those to the local gitignore? I've got them in my global one, but things tend to go wrong quite frequently when dealing with manual merges 😆


Python 3.12 support: use ConfigParser

SafeConfigParser was removed in 3.12, after being deprecated since 3.2
Fixes: #330

Thanks!


Request for Testing Code on Agent Benchmarks for Qwen2-VL

Hi,
I am thoroughly impressed by the performance of Qwen2-VL on the Agent Benchmarks. However, I was unable to locate the corresponding testing code in the repository. Could you please point me to where the testing code is located? If it is not currently available, do you have any plans to release the testing code in the future?
Thank you for your time and assistance.
Best regards

I’m interested in reproducing the results shown in the image below. Could you please provide the steps or code needed to replicate this experiment?
Thank you for your assistance.


Can't get history for index fund

Example:
In [1]: import yfinance as yf

In [2]: yf.download(tickers='FXAIX', prepost=True, period='1d', interval='1m')
[*********************100%***********************]  1 of 1 completed

1 Failed download:
- FXAIX: No data found for this date range, symbol may be delisted
Out[2]:
Empty DataFrame
Columns: [Open, High, Low, Close, Adj Close, Volume]
Index: []

In [3]: yf.__version__
Out[3]: '0.1.87'

Though yahoo finance has this listed: https://finance.yahoo.com/quote/FXAIX/

It looks like on the browser it uses a request like:
https://query1.finance.yahoo.com/v8/finance/chart/FXAIX?useYfid=true&range=1mo

Looks like both the range/interval has to follow a specific format AND it needs useYfid=true... no idea what that is intended to mean though.

Visit finance.yahoo.com and confirm they have your data

Did you confirm they have data for today? You only requested one day of trades, the most recent day.

Ahh ok yeah. I tried '1m' and thought that was month but it was minute. All good. Closing this out.

One other question @ValueRaider: is there a way to just get the 'last/most recent' price?  Like I don't need history beyond just that single price point.

Ticker.info has 'currentPrice', but that fetch is much more expensive than just fetching a bunch of price history.

the problem with history is that is there a combo of interval/period that work with everything? I was previously using interval=1m and period=1d but that didn't work here.

Leave interval alone, the last row close price will always be most recent regardless. It might help to understand what it's fetching - https://finance.yahoo.com/quote/FXAIX/history?p=FXAIX


Build Fusion/Earth Server from third_party/python/SConscript: remove -idirafter replacement for sandbox path

where is the sanbox path and how to get? if I donot modify third_party/python/SConscript,whether there will be problems on the program

Hi @wangjunqin, this was added to the instructions by @pengfei666. I don't know exactly what it means. Do you have any issues with running the scons command as it's written, disregarding the instructions to "remove -idirafter replacement for sandbox path"? I think that text should be removed from the instructions. I've never even noticed it was there.

This has been removed. Suggest closing.


Detected that custom integration 'irm_kmi' sets option flow config_entry explicitly, which is deprecated at custom_components/irm_kmi/config_flow.py, line 110

Version

Home Assistant: [e.g. 2024.12.5]
IRM KMI integration [e.g. 0.2.24]

Find in Log
Enregistreur: homeassistant.components.recorder.db_schema
Source: components/recorder/db_schema.py:624
intégration: Recorder (documentation, problèmes)
S'est produit pour la première fois: 28 décembre 2024 à 09:27:58 (88 occurrences)
Dernier enregistrement: 10:05:55
State attributes for weather.maison exceed maximum size of 16384 bytes. This can cause database performance issues; Attributes will not be stored
Enregistreur: homeassistant.helpers.frame
Source: helpers/frame.py:324
S'est produit pour la première fois: 10:07:50 (2 occurrences)
Dernier enregistrement: 10:08:59
Detected that custom integration 'irm_kmi' sets option flow config_entry explicitly, which is deprecated at custom_components/irm_kmi/config_flow.py, line 110: self.config_entry = config_entry. This will stop working in Home Assistant 2025.12, please create a bug report at https://github.com/jdejaegh/irm-kmi-ha/issues
Detected that custom integration 'irm_kmi' uses async_config_entry_first_refresh, which is only supported for coordinators with a config entry at custom_components/irm_kmi/init.py, line 27: await coordinator.async_config_entry_first_refresh(). This will stop working in Home Assistant 2025.11, please create a bug report at https://github.com/jdejaegh/irm-kmi-ha/issues
Enregistreur: homeassistant.helpers.frame
Source: helpers/frame.py:324
S'est produit pour la première fois: 10:07:50 (2 occurrences)
Dernier enregistrement: 10:08:59
Detected that custom integration 'irm_kmi' sets option flow config_entry explicitly, which is deprecated at custom_components/irm_kmi/config_flow.py, line 110: self.config_entry = config_entry. This will stop working in Home Assistant 2025.12, please create a bug report at https://github.com/jdejaegh/irm-kmi-ha/issues
Detected that custom integration 'irm_kmi' uses async_config_entry_first_refresh, which is only supported for coordinators with a config entry at custom_components/irm_kmi/init.py, line 27: await coordinator.async_config_entry_first_refresh(). This will stop working in Home Assistant 2025.11, please create a bug report at https://github.com/jdejaegh/irm-kmi-ha/issues

Hello,
Thanks for the report!  I would help if you could describe what you were doing to get those lines to show up in the logs.  I managed to reproduce the two issues anyways.
The first issue ('irm_kmi' sets option flow config_entry explicitly) is triggered when modifying the configuration of the integration.  It produces the following line:
2024-12-29 15:38:46.827 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'irm_kmi' sets option flow config_entry explicitly, which is deprecated at custom_components/irm_kmi/config_flow.py, line 110: self.config_entry = config_entry. This will stop working in Home Assistant 2025.12, please create a bug report at https://github.com/jdejaegh/irm-kmi-ha/issues

The second issue ('irm_kmi' uses async_config_entry_first_refresh, which is only supported for coordinators with a config entry) is triggered when using the repair flow.  It produces the following line:
2024-12-29 15:45:11.775 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'irm_kmi' uses `async_config_entry_first_refresh`, which is only supported for coordinators with a config entry at custom_components/irm_kmi/__init__.py, line 27: await coordinator.async_config_entry_first_refresh(). This will stop working in Home Assistant 2025.11, please create a bug report at https://github.com/jdejaegh/irm-kmi-ha/issues

I have to investigate further to see what the correct fix is.

Both issues should be solved by PR #65 and #66.  The changes will be included in the next version of the integration.  Feel free to test and report any error you might encounter


spring-cloud: new way to query url from app details

@hellokangning : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off


[CCI] Remove Elastic References from OuiBasicTable

Description
Removed Elastic References from OuiBasicTable Actions examples

Issues Resolved
https://github.com/opensearch-project/oui/issues/697
Check List

[ ] New functionality includes testing.
[ ] New functionality has been documented.
[x] All tests pass

[x] yarn lint
[x] yarn test-unit

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Hi @SergeyMyssak,
Thanks for the change.
Is this PR remove the Elastic References from Actions when toggle the option for "multiple actions" (Please see screen-shot below)?

Can you please attach that screenshot as well?

Pulled this down and works as expected. LGTM!
No Elastic references found on Actions when toggle the option for "multiple actions"


[vtk] Build error

Host Environment

OS: Windows
Compiler: Microsoft Visual Studio Community 2019 16.11.19

To Reproduce
Steps to reproduce the behavior:
./vcpkg install vtk[all]:x64-windows
Failure logs
--- Could NOT find Git (missing: GIT_EXECUTABLE)
CMake Error at CMake/vtkModuleRemote.cmake:146 (message):
error: could not find git for clone of MomentInvariants
Call Stack (most recent call first):
Remote/MomentInvariants.remote.cmake:5 (vtk_fetch_module)
Remote/CMakeLists.txt:9 (include)

Attach .\vcpkg\buildtrees\vtk\config-x64-windows-out.log mentioned in the console output.

Additional context
Add any other context about the problem here, such as what you have already tried to resolve the issue.

Cofirmed.

I also ran into this bug, I wonder if you found a way to fix it?

Using the latest VTk version now encountering the following error:
CMake Warning at F:/Feature-test/boost/scripts/buildsystems/vcpkg.cmake:859 (_find_package):
  By not providing "Findospray.cmake" in CMAKE_MODULE_PATH this project has
  asked CMake to find a package configuration file provided by "ospray", but
  CMake did not find one.

  Could not find a package configuration file provided by "ospray" (requested
  version 2.1) with any of the following names:

    osprayConfig.cmake
    ospray-config.cmake

  Add the installation prefix of "ospray" to CMAKE_PREFIX_PATH or set
  "ospray_DIR" to a directory containing one of the above files.  If "ospray"
  provides a separate development package or SDK, be sure it has been
  installed.
Call Stack (most recent call first):
  CMake/vtkModule.cmake:4573 (find_package)
  Rendering/RayTracing/CMakeLists.txt:58 (vtk_module_find_package)

CMake Error at CMake/vtkModule.cmake:4579 (message):
  Could not find the ospray external dependency.
Call Stack (most recent call first):
  Rendering/RayTracing/CMakeLists.txt:58 (vtk_module_find_package)

Duplicate of https://github.com/microsoft/vcpkg/issues/25579


can it work with a telegram boy ?

This is actually not a valid template, please choose Bug Report!
PICK BUG REPORT
PICK BUG REPORT
PICK BUG REPORT
PICK BUG REPORT
PICK BUG REPORT
PICK BUG REPORT
PICK BUG REPORT
PICK BUG REPORT
PICK BUG REPORT
PICK BUG REPORT
PICK BUG REPORT
PICK BUG REPORT
PICK BUG REPORT
PICK BUG REPORT
PICK BUG REPORT

it cant

Support for Telegram has not been added Yet!


Provide site url during post-install migrations

Hard lesson learned from spinning up http://future.islandora.ca
We bake in localhost here.  This led to gemini entries with localhost instead of future.islandora.ca.  We need to allow for a configurable -l parameter so folks can add their site name properly.

Would this work or do we have (possibly) multiple vhosts?

Yes, still relevant.  The code shifted a bit tho.  The offending line is now https://github.com/Islandora-Devops/islandora-playbook/blob/master/post-install.yml#L37


Text extractor isn't working on a picture in photos app

Microsoft PowerToys version
0.69.1
Installation method
Microsoft Store
Running as admin
Yes
Area(s) with issue?
TextExtractor
Steps to reproduce

Open a picture with text using Photos App
Press:>    'Win' + 'Shift' + 'T'
Select text using the selector

✔ Expected Behavior
Text to be selected and copied to the Clipboard. The selection tool should close after the text is copied to the Clipboard.
❌ Actual Behavior
The screen shows the selection tool.
I can't select any other app until I press 'Esc'.
The text is not copied to the Clipboard.
Other Software
Photos - Updated 2023.1103027009.0
@ 2022 Microsoft Corporation
Session identifier: d75f0431-253e-46c8-bafd-07d893b851d6

can we get the actual picture?
/reportbug

Possible Clue
I noticed some weird Text Extractor glitches occuring when text (such as letter p) is touching a box outline.

PowerToysReport_2023-04-27-11-54-25.zip
I attached the Zip File more information

I wonder if this has something to do with the small height of the selection. I was able to use Text Extractor on the screenshot, but obviously my DPI and actual size of the selection are different. If you select the same text but with a larger vertical size does that work?


docs: Document appimage artifacts

Document how to download/install the new appimages.
Checklist

[ ] Language changes are updated in man/adoc/bpftrace.adoc and if needed in docs/reference_guide.md
[ ] User-visible and non-trivial changes updated in CHANGELOG.md
[ ] The new behaviour is covered by tests

Fixed; thanks for looking


Annotating edges in mutations

We need a strategy to deal with annotations on fields during mutations. This is supported in the spec with regard to types for edges and their corresponding operations. However, the use of arguments on input type fields is not supported in GraphQL, and if an object has an edge annotation marked as required/non-null, it can currently not be created.
There are a couple of alternatives for this as I see it (naming may vary). Assume the following incomplete schema:
type Person {
   id: ID!
   name: String!
   knows(since: Date!, description: String): [Person]
}

mutation {
   createPerson(data: _InputToCreatePerson)
}

input _InputToCreatePerson {
   name: String!
   knows: [_InputToConnectKnowsOfPerson]
}

We could provide additional fields for the annotations in _InputToConnectX, e.g.:

input _InputToConnectKnowsOfPerson {
   connect: ID
   create: _InputToCreatePerson
   since: Date!
   description: String
}

Another alternative would be to define a new type that defines fields for annotations on the edge, e.g.:

input _InputToConnectKnowsOfPerson {
   connect: ID
   create: _InputToCreatePerson
   annotation: _InputToAnnotateKnowsOfPerson! # when should this field be marked as non-null?
}

input _InputToAnnotateKnowsOfPerson {
   since: Date!
   description: Date
}

The benefit of using alt 1 is that we don't have to add any additional input types, but simply extend the current _InputToConnectX. This is also close to the pattern for _InputToCreateXEdgeFromY in the spec. The benefit of using alt 2 is that the field names for all _InputToConnectX input types are fixed (similar to providing a single input type as data during mutations). If we go with alternative 2, we may also consider using it for the _InputToCreateXEdgeFromY, e.g.
input _InputToCreateKnowsEdgeFromPerson {
   sourceID: ID!
   targetID: ID!
   annotations: _InputToAnnotateKnowsOfPerson! # when should this field be marked as non-null?
}

@hartig

Just to see what each of the two alternatives would look like from the perspective of the users, I am writing example mutation operations here:
Assuming alternative 1, the user would have to write something like the following.
createPerson(
   data: {
      name: "Alice"
      knows: [
         {
            connect: 261
            since: "02-02-2016"
            description: "abcdef"
         }
      ]
   }
) {
   id
   name
}

Assuming alternative 2, the user would have to write something like the following.
createPerson(
   data: {
      name: "Alice"
      knows: [
         {
            connect: 261
            annotations: {
               since: "02-02-2016"
               description: "abcdef"
            }
         }
      ]
   }
) {
   id
   name
}

Alternative 2 looks cleaner. Let's go with that one.
Then, as you say, we should adapt the _InputToCreateXEdgeFromY types accordingly. I will edit the wiki.

I have updated the wiki -- see: https://github.com/LiUGraphQL/pgschema-to-apischema/wiki/Overview-of-the-Approach#54-creating-an-edge
One thing though regarding naming conventions: In your example, the input type for the annotation object is named _InputToAnnotateKnowsOfPerson. To be consistent with the naming scheme for creating and for updating edges (Sections 5.4 and 5.5 in the aforementioned wiki page), I propose to name it _InputToAnnotateKnowsEdgeFromPerson.

Another thing, which is unrelated to the actual issue but related to your first code example: Notice that this piece of schema mixes parts from the DB schema and parts from the generated API schema.
That is, while the mutation type and the input type is part of the generated API schema, the following line is DB schema:
     knows(since: Date!, description: String): [Person]

More precisely, the argument definitions in this field definition may occur only in the DB schema, but they should be removed when generating the API schema.

Thanks for clarifying this. I assume that this means that before having the edge objects in place we will not be able to filter on any of the annotations of edges?

I assume that this means that before having the edge objects in place, we will not be able to filter on any of the annotations of edges?

Again, this is unrelated to the current issue. However, since you ask: It would be possible to add a second filter argument into the field definitions that correspond to edges (such as the knows field in the examples above). That is, there would be one filter argument that allows users to filter the resulting list by conditions on the objects the list should contain (which is what we currently have with the filter arguments), and the new second filter argument (which would need to be named differently) would allow users to to filter the resulting list by conditions on the edges that lead to the objects in the list. Perhaps this gets to confusing for users. Therefore, I propose to ignore this option. Instead, filtering based on edge annotations should be added only to the generated fields that allow users to traverse to edge objects (as described in Sect.4 of the approach).

#31 and #32 are related issues.
#31 is about enabling users to request the edge properties created/updated based on the feature to be added by this issue.
#32 is about enabling users to filter based on these edge properties.

@rcapshaw please check to which extend it is already possible now to specify edge properties. It needs to be possible both i) in edge-creation operations and ii) when creating an edge inline (i.e., within other creation operations). Please first document here the findings of checking and, then, start implementing the missing parts.

The corresponding gitlab issue was 16.

Things missing so far seems to be:
Adding annotations to _InputToConnectXOfY,
handling annotations in create,
handling annotations in update.
Annotation fields exists for edge-types. They can be given values when creating edges directly, but not when adding edges indirectly from createObject-mutations.

With #66 being merged and this being reflected in the changelog, this issue is now implemented.


failed to create index [elastalert_status]

My version of elastic slack is 7.2.0.
elasticsearch-python version is 7.0.0
When I run elastalert-create-index and am prompted to enter the configuration, it doesn't work.
this is error message:
Traceback (most recent call last):   File "/usr/local/python3.6/bin/elastalert-create-index", line 11, in <module>     load_entry_point('elastalert==0.2.4', 'console_scripts', 'elastalert-create-index')()   File "/usr/local/python3.6/lib/python3.6/site-packages/elastalert-0.2.4-py3.6.egg/elastalert/create_index.py", line 264, in main     create_index_mappings(es_client=es, ea_index=index, recreate=args.recreate, old_ea_index=old_index)   File "/usr/local/python3.6/lib/python3.6/site-packages/elastalert-0.2.4-py3.6.egg/elastalert/create_index.py", line 55, in create_index_mappings     es_index.create(index_name)   File "/usr/local/python3.6/lib/python3.6/site-packages/elasticsearch/client/utils.py", line 84, in _wrapped     return func(*args, params=params, **kwargs)   File "/usr/local/python3.6/lib/python3.6/site-packages/elasticsearch/client/indices.py", line 101, in create     "PUT", _make_path(index), params=params, body=body   File "/usr/local/python3.6/lib/python3.6/site-packages/elasticsearch/transport.py", line 318, in perform_request     status, headers_response, data = connection.perform_request(method, url, params, body, headers=headers, ignore=ignore, timeout=timeout)   File "/usr/local/python3.6/lib/python3.6/site-packages/elasticsearch/connection/http_requests.py", line 91, in perform_request     self._raise_error(response.status_code, raw_data)   File "/usr/local/python3.6/lib/python3.6/site-packages/elasticsearch/connection/base.py", line 131, in _raise_error     raise HTTP_EXCEPTIONS.get(status_code, TransportError)(status_code, error_message, additional_info) elasticsearch.exceptions.RequestError: RequestError(400, 'validation_exception', 'failed to create index [elastalert_status]')
Can help me with this?

Please share your config.yaml, rule.yaml.

<IP_ADDRESS> for the same location as elastalert. If not, specify the IP address of the server
curl -XGET 'http://<IP_ADDRESS>:9200/elastalert_status/_mapping/'

Do you use python virtualenv when setting up elastalert?
setup is "pip install elastalert"
or
"git clone https://github.com/Yelp/elastalert.git" and  "pip install" setuptools> = 11.3 "" and "python setup.py install"

elastic slack is 7.2.0 installed directly or Docker?

conf.yaml
buffer_time:   minutes: 15 es_host: <IP_ADDRESS> es_port: 9600 es_username: elastic es_password: xxx alert_time_limit:  days: 2
rule_demo.yaml
`
es_host: <IP_ADDRESS>
es_port: 9600
es_username: elastic
es_password: synnex
name: Example frequency rule
type: frequency
index: heartbeat-*
num_events: 10
timeframe:
hours: 1
filter:

term:
monitor.status: "up"

alert:

"email"

email:

<EMAIL_ADDRESS>run get elastalert_status/_mapping/ "type": "index_not_found_exception",
"reason": "no such index [elastalert_status]",
"resource.type": "index_or_alias",
"resource.id": "elastalert_status",
"index_uuid": "na",
"index": "elastalert_status"`
I got it from git and ran pip install" setuptools> = 11.3 "" and "python setup.py install"
7.20 installed directly

Please share your elasticsearch.yml.
Edit the IP address, username, and password to xxxx. Please do not put the actual value

Are you aware that elastalert and elasticsearch are running on different servers?

Is there the following setting in elasticsearch.yml?
http.port: 9600
network.host: <IP_ADDRESS>

Thank you for your enthusiasm.
I've fixed it.
The reason is that the maximum number of shard was exceeded.


Update high-res configuration

This PR:

Gets rid of commented lines.
Turns off known buggy switches.
Turns on VERTEX_SHEAR (requested by @Dooruk and suggested by @travissluka).
Turns off 2018 answers.

Does not impact answers with MOM5 ocean model.
These changes will cause answers to differ (@mathomp4 please note for testing at this resolution; we already have DEFAULT_2018_ANSWERS = False for coarse-res configuration that is used for testing), for the better!

Thank you @sanAkel for making this update. I see the checkerboard pattern disappear with the new option.

Thank you @sanAkel for making this update. I see the checkerboard pattern disappear with the new option.

For sake of bookkeeping, @Dooruk, would you please upload that plot? Showing that pattern disappear? Thanks!

For sake of bookkeeping, @Dooruk, would you please upload that plot? Showing that pattern disappear? Thanks!

Sure, top one is without the VERTEX_SHEAR option turned on. Also, thanks @travissluka for finding this issue!

Thanks a lot!

@sanAkel, The override is missing  #override RESTART_CONTROL = 2 which impacts RECORD_FREQUENCY checkpoint dumps. I don't want to create a new issue for it but that is needed either in MOM_input or MOM_override.
Essentially, RECORD_FREQUENCY option is not creating MOM6 checkpoint files properly. MOM6 restarts keep getting overwritten:

@sanAkel, The override is missing #override RESTART_CONTROL = 2 which impacts RECORD_FREQUENCY checkpoint dumps. I don't want to create a new issue for it but that is needed either in MOM_input or MOM_override.
Essentially, RECORD_FREQUENCY option is not creating MOM6 checkpoint files properly. MOM6 restarts keep getting overwritten:

@Dooruk will you please add that yourself- in your own version of MOM_override?
I checked previous versions of MOM_input and MOM_override for RESTART_CONTROL, they had default (=1) too.
If I recall correct, you either got that =2 from me offline (or from maybe from someone)? Because clearly previous versions (in this repo) did not have anything but default value.
When we run the model (only) without an assimilation or need for it, we do not want restarts piling up- long runs will exhaust the disk space. That's not your case with short runs. We need to create another MOM_override for assimilation, so please gather this and others you might want and we'll make a new config next time. Ok?

@Dooruk will you please add that yourself- in your own version of MOM_override?

Yeah, what you say makes sense, all good 👍


Create Search Page - Create Welcome Banner

Requirements

[ ] Create new banner component
[ ] Apply Styling
[ ] Add Closing functionality
Note: this is for desktop mode for now until we have mobile mockups. Will set up mobile support in a separate issue.

Dependencies

None (Add any issue dependencies here)

@all-contributors please add @kei-design-jp for design


Update nodes.md to correct descriptions

To correct descriptions of Node Condition like MemoryPressure and DiskPressure.

Can you add the original English to the changes you have made? convenient for examination and approval of

How do i add the original english to my commit? Another patch for a new PR? I'm a github novice.
original english:
https://github.com/copileft/kubernetes-website/blob/release-1.14/content/en/docs/concepts/architecture/nodes.md

Instead of opening a new pr, use markdown's syntax below or above your changes.
eg:
<--  content...  -->

I have added the original english by a new commit.

cool
/lgtm
/approve


Datepicker keyboard navigation stops working if min/max applied to input element

Bug, feature request, or proposal:
Bug discovered if min or max attributes are applied to the input element associated with a mat-datepicker.
What is the expected behavior?
Keyboard navigation of the datepicker popup should work (e.g. left/right/up/down arrow keys should move the selected date marker and enter key should select the date under the marker).
What is the current behavior?
Keyboard navigation stops working if either min, max or both min and max attributes are specified on the input element associated with mat-datepicker.
What are the steps to reproduce?
Providing a StackBlitz/Plunker (or similar) is the best way to get the team to see your issue.
https://embed.plnkr.co/CK3qnKNX8gnIDKBdW4ZA/
What is the use-case or motivation for changing an existing behavior?
Consistency of behaviour.
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
I am using Angular 4.4.5, Material 2.0.0-beta.12, OS Mac Sierra 10.12.6, Chrome 61.0.3163.100 (Official Build) (64-bit), TypeScript 2.5.3
Is there anything else we should know?
Also tried with TypeScript 2.1.1 and get same behaviour

The issue comes from the fact that you're using a function to determine the minDate and maxDate. This means that every time Angular runs change detection (for example every keypress in the calendar) it'll get a new date object for min and max which ends up throwing off the datepicker. It works if you replace the functions with properties. Here's a forked Plunkr. @mmalerba is this something that we want to handle?

Thanks for the explanation and workaround. Unfortunately I cannot use the proposed workaround because, in my case, the min/max dates change depending on other fields in my form. This is why I made them both functions. Is there a way you can think of that will cater for my requirements?

Rather than returning the dates from a function, you can assign them after any other the other fields have changed. I think the issue is only that the dates change while the calendar is open (which is what happens when it's in the function). It's slightly less convenient, but it should be more resource-efficient since you're not creating and throwing out date objects all the time.

OK - so I guess I'll have to add listeners to all the fields that could change the min/max dates. On a slightly related note, I am using dynamic forms where I add Validators to each of my form fields. Since I am adding min/max attributes to the input element associated with mat-datepicker then would it be reasonable for me not to specify field validators for the date fields? (the date field Validators I have also check that the date entered is within the given min/max dates)

The datepicker already attaches its own validators (matDatepickerMin, matDatepickerMax etc.) when you set the min and max so you shouldn't have to add any more validators on top it.

Great - thanks for all your help - greatly appreciated

Actually I have one edge case that I'd like your opinion on. The min date for one of my dates is set to  new Date() (i.e. today's date). With my original implementation this automatically changed at mid-night to the next date. However, with properties, the min date will remain at the same fixed date. Is there some smart way to automagically update the min date property so that it keeps in track with "today" as time passes?

How about something like this?
ngAfterContentInit() {
  this.scheduleUpdateDate();
}

scheduleUpdateDate() {
  let today = new Date();
  let tomorrow = new Date(today.getFullYear(), today.getMonth(), today.getDate() + 1);
  setTimeout(() => this.updateDate(), tomorrow.getTime() - today.getTime())
}

updateDate() {
  // do update...
  this.scheduleUpdateDate();
}

Closing since the datepicker is working as expected.


KAFKA-17367: Share coordinator impl. Broker side code. [2/N]

Added impl for ShareCoordinatorService and ShareCoordinatorShard
Moved group-coordinator: GroupCoordinatorRuntimeMetrics -> coordinator-common: CoordinatorRuntimeMetricsImpl. The new impl class can be inherited and used in both group and share coordinators.
Added tests wherever applicable
Added plumbing in BrokerServer and BrokerMetadataPublisher to create share coordinator and start/stop it.
Added ShareCoordinatorConfig class to house various coordinator related configs.
Added code to create share state topic in  AutoTopicCreationManager.scala
Added

share.coordinator.state.topic.replication.factor=1
share.coordinator.state.topic.min.isr=1

to config/kraft/{broker.properties, controller.properties, server.properties} to make it easier for people to try out.

Thanks for the patch @smjn! This is a pretty big PR, so I've just reviewed part of it for now.
Regarding the leader epoch, it seems like we are checking the MetadataImage for some things (like if a topic exists), but using the given leader epoch in the RPC to see if the leader has changed. I wonder if we should be checking the given leader epoch against the MetadataImage.
Where are we handling topic deletions and re-creations? Maybe this is coming in a future PR?

For EA only read and write RPCs will be provided.

Will this logic be replaced by the init RPC once it is added?
In general, we should not be updating our log based in-memory state on reads. It's probably safe in this case just based >on the nature of leader epoch, but it is definitely atypical.

No it will stay.
The initialize rpc does not include any information about the leader epoch which we can store and reference.
We are going by epoch definition.

@junrao Thanks for the review, incorporated comments.


Make cosmwasm_std::Error serializable

When passing info over API boundaries, we lose all type info. This issue has been faced with all integration tests, where we have to adapt the error handling from matching on type to string compares.  While beginning work on the Querier trait in #197 I realized this becomes an issue.
In unit tests, Querier would have access to a full Result. However, when running in integration, we would either have QueryResult(Err(String)) or fake a Result like we do in ExternalApi.canonical_address. The other approach would be to downgrade all local errors into QueryResult as well....
This PR is an experiment of making the cosmwasm_std::Error type something we can pass through an API (serialization boundary). Naturally the source error field and backtraces fields cannot be de/serialized properly, so I create a custom ApiError type for deserialization which captures all information in a serializable form. And use a bit of serde magic to make this all work together.
Before actually using these richer errors in the Querier, I want to see if such transforms are acceptable. They should create no overhead (runtime or bytecode) if not used. But will make usage of Querier a bit bulkier in runtime. We would also want to update the Query implementation in general to return this richer data.

Cool stuff. I just discovered the same problem when looking into the query response. I guess this is not very safe against refactorings, since only runtime tests can ensure it works. What about creation a type safe Error -> ApiError one way mapper function. This can be called in _do_init and friends. This way only ApiError need to have serde capabilities.

What about creation a type safe Error -> ApiError one way mapper function. This can be called in _do_init and friends. This way only ApiError need to have serde capabilities.

That does sound like a simpler/more efficient way of achieving the same goal. I will make this change (likely Monday) and push this again.

Okay, I got inspired and refactored this. Much nicer now with your feedback :+1:
If you like it, feel free to merge and base future Query API stuff on this.


Stuck at loading template

Environment

FAST RPM Version: 1.25.0
BIG-IP Version: <IP_ADDRESS>
AS3 (3.49)

Summary
Whever I click on one of the provided templates, it says "Loading template: bigip-fast-templates/<template_name>" and the template never renders.
Steps To Reproduce
List the steps to reproduce the behavior:
Install ASM and FAST.
Go to Application Services > Applications LX > F5 Application Services Templates.
Click on any of the templates.
Expected Behavior
A clear and concise description of what you expected to happen.
I expect the template to load so I can fill it out and deploy an app.
Actual Behavior
A clear and concise description of what actually happens.
Please include any applicable error output.
The template doesn't load. It says "Loading template: bigip-fast-templates/<template_name>".
I never see an error in my browser, but if I run dev tools, I see a 400 Bad Request for "/mgmt/shared/fast/templates/bigip-fast-templates/bluegreen?userAgent=FASTGUI/NA". I get similar errors for all provided templates.
Here are things I've tried:
Uninstall/reinstall ASM and FAST
Restart all REST services
Reboot BIG-IP
Download templates from Github and import them under a new zip file. Import successful, but same errors.

I also started to see the following errors every few minutes in /var/log/ltm after I installed FAST. The node referred to below already exists as part of a Telemetry Streaming configuration.
Feb 16 14:09:01 bigiphost err mcpd[6168]: 0107176c:3: Invalid Node, the IP address <IP_ADDRESS> already exists.

I found the following error in /var/log/restnoded/restnoded.log when attempting to open a template:
Thu, 07 Mar 2024 12:31:42 GMT - severe: [appsvcs] {"message":"Declaration failed: 0107176c:3: Invalid Node, the IP address <IP_ADDRESS> already exists.","level":"error"}
This node already existed prior to deploying FAST package. You would already have this node if you are using Telemetry Streaming for various log sources such as system logging, ASM, LTM requests, etc. See https://my.f5.com/manage/s/article/K000134780 for details.
Apparently, FAST assumes that none of this exists and attempts to create its own VS, pool, and node for Telemetry Streaming. I was able to workaround the issue by removing the VS, pool and node that was previously configured for TS. I also had to temporarily disassociate several log profiles and log destinations that referenced the pool. Once that was done, I redeployed FAST and I was able to load a template without getting the 400 error.
Upon first deployment of a FAST app, it created its own VS, pool, and node for TS in /Common/shared. I then updated all my pre-existing log profiles and log destinations to reference the telemetry pool that FAST created.
I don't know if this is the best workaround for a mixed environment where you're adding FAST into an existing environment. At the very least, it would be nice to document this in the FAST deployment guide for those who already have telemetry streaming pools configured.


Add a welcoming and inclusive Code of Conduct

Will need to evaluate some candidates and pick a good one.

The Citizen Code of Conduct was carefully crafted, and has been adopted by many FOSS projects.
http://citizencodeofconduct.org/
An adaptation I particularly like is the one for Plasma Lang
https://github.com/PlasmaLang/plasma/blob/master/CODE_OF_CONDUCT.md


python310Packages.onvif-zeep-async: 1.2.5 -> 1.2.11

Description of changes

Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 226621 run on x86_64-linux 1

5 packages built:

home-assistant-component-tests.onvif
python310Packages.onvif-zeep-async
python310Packages.onvif-zeep-async.dist
python311Packages.onvif-zeep-async
python311Packages.onvif-zeep-async.dist


Refactor

HI @n400peanuts , really sorry for those noisy emails from the previous bad pull requests. Hopefully this time it will work as expected...

Ehyyy no problem. I am going to look at those tomorrow morning! Thanks a lot
Il giorno 21 apr 2023, alle ore 16:18, Ji Qi @.***> ha scritto:

HI @n400peanutshttps://github.com/n400peanuts , really sorry for those noisy emails from the previous bad pull requests. Hopefully this time it will work as expected...

You can view, comment on, or merge this pull request online at:
https://github.com/covid19ABM/mhm/pull/17
Commit Summary

170c723https://github.com/covid19ABM/mhm/pull/17/commits/170c723a0d626367c1c7ec088dbcf8d0f8e06947 Add setup.py; change .gitignore.
f9c66d8https://github.com/covid19ABM/mhm/pull/17/commits/f9c66d8641126a90cb3c4cfe3cf0aae64755c824 Remove requirements.txt.
e53746fhttps://github.com/covid19ABM/mhm/pull/17/commits/e53746fee9d4c7af3776b4ff206e54c40c418765 Change setup.py.
4ba7b18https://github.com/covid19ABM/mhm/pull/17/commits/4ba7b1800b58c5d847eb00f4efbee22967075ec0 Change setup.py.
24f5bd6https://github.com/covid19ABM/mhm/pull/17/commits/24f5bd64405d0be5a4f2d750c306fb0711c6e5ae Add frameworks of the individual and model class.
4515deahttps://github.com/covid19ABM/mhm/pull/17/commits/4515deafd9676f66a4ebb6eb95b0a51d04302bb2 Convert hypothesis files into CSV format.
e7ed189https://github.com/covid19ABM/mhm/pull/17/commits/e7ed189c33f1f1b3c1dea9bca3d953b38db341f9 Unify format of parmeters of individual features for creating population.
25ef324https://github.com/covid19ABM/mhm/pull/17/commits/25ef32460788bab36fce54413e0fe84b6240400c Implement populate method.
848f276https://github.com/covid19ABM/mhm/pull/17/commits/848f2760f8649082dde952bb4fd1ca5f9b9f4941 Add get_features function.
afc1d85https://github.com/covid19ABM/mhm/pull/17/commits/afc1d850b06a2c942fafeaf3dfb3be5f47952266 Set default seed for the populate method.
0fad8abhttps://github.com/covid19ABM/mhm/pull/17/commits/0fad8abb91690c570ed2fc6784d6f4f7aa3d7e18 Rename some features and values; remove setup method; add status as a class variable.
4da6042https://github.com/covid19ABM/mhm/pull/17/commits/4da60426576a1b9858ffb9bad3b63bbb6dc4d349 Update hypotheses.
54e79dchttps://github.com/covid19ABM/mhm/pull/17/commits/54e79dcd829c0014cf9fa1d83359cffcaab44fee Add one-hot encoding in the populate function.
3019b5dhttps://github.com/covid19ABM/mhm/pull/17/commits/3019b5df9dee52a21c483eafddacb406fa9f24b3 Add get_status() and implement action().
38d2a21https://github.com/covid19ABM/mhm/pull/17/commits/38d2a218fb4bb1faadec8a4984cbc0b595b62a9c Minor.
b4d3e47https://github.com/covid19ABM/mhm/pull/17/commits/b4d3e472fad0ed11e25106d5488ffceae4750d6b Amend commit.
7a8e45dhttps://github.com/covid19ABM/mhm/pull/17/commits/7a8e45d601489c7a7a1c85162f142826a64f6bff Merge branch 'refactor' of https://github.com/covid19ABM/mhm into refactor
fa071c3https://github.com/covid19ABM/mhm/pull/17/commits/fa071c318d77d8e40bd8e1cf3559b0520eb1a4c5 Merge branch 'refactor' of https://github.com/covid19ABM/mhm into refactor
0af3ed4https://github.com/covid19ABM/mhm/pull/17/commits/0af3ed4bf69a9a1d32559f06828f5d215a160902 Merge branch 'refactor' of https://github.com/covid19ABM/mhm into refactor
f491bd6https://github.com/covid19ABM/mhm/pull/17/commits/f491bd6715612d5db150798b96e5eb0f1b8a0f58 Fix #14.
718caffhttps://github.com/covid19ABM/mhm/pull/17/commits/718caffaff4205cd1a4f578a2c0c209aea3c4e4c Update gitignore file; remove old unit tests.
2d39a54https://github.com/covid19ABM/mhm/pull/17/commits/2d39a5477386980ed2a3a9c47032e7252f22cae2 Add a placeholder test.

You are receiving this because you were mentioned.Message ID: @.***>


Ready to release 0.3.0

The branch of 0.2.0 is master-0.2.0. If your PR is to solve the problem of 0.2.0, please submit the PR to it.
Please do not create a Pull Request without creating an issue first.
What is the purpose of the change
Ready to release 0.3.0
Brief changelog

Modified version to 0.3.0
Adjust POM dependencies and use Dubbo's dependency version control
Add display of version on UI
Add 0.3.0 docker related scripts

Verifying this change
XXXX
Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Make sure there is a Github issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a Github issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[ ] Format the pull request title like [ISSUE #123] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist.
[ ] Run `mvn clean compile --batch-mode -DskipTests=false -Dcheckstyle.skip=false -Drat.skip=false -Dmaven.javadoc.skip=true to make sure basic checks pass.

Codecov Report

Merging #797 (e280b1b) into develop (021c3f5) will decrease coverage by 0.08%.
The diff coverage is n/a.

@@              Coverage Diff              @@
##             develop     #797      +/-   ##
=============================================
- Coverage      20.36%   20.27%   -0.09%
+ Complexity       331      326       -5
=============================================
  Files             97       97
  Lines           3885     3887       +2
  Branches         616      614       -2
=============================================
- Hits             791      788       -3
- Misses          3018     3023       +5
  Partials          76       76

Flag
Coverage Δ

unit
20.27% <ø> (-0.09%)
:arrow_down:

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

Impacted Files
Coverage Δ

...apache/dubbo/admin/service/RegistryServerSync.java
83.58% <0.00%> (-10.45%)
:arrow_down:

...va/org/apache/dubbo/admin/config/ConfigCenter.java
88.13% <0.00%> (+0.86%)
:arrow_up:

...ava/org/apache/dubbo/admin/model/domain/Route.java
44.77% <0.00%> (+1.29%)
: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 021c3f5...e280b1b. Read the comment docs.


[output] implement Elasticsearch output

Outputs JSON of dataUnit to configured Elasticsearch. The ES configuration should be passed in a configuration file.

Left for completion:

[ ] tests


Use node 0.12 in AppVeyor

This will allow appveyor to run the tests on both node 0.10 and 0.12 just like they do on travis

thanks @xt0rted!


arrays.lastIndexOf

Like indexOf but it iterates from right to left
Checklist

[x] implementation
[x] tests
[x] jsdoc

Details

References

_.lastIndexOf

Added in 0.44

Removed in 0.74.5


actions: Combine duplicate code and add Windows support

I set it up to continue on cargo test errors, because some minivorbis related tests fail on Windows without causing any noticeable problems later.

Thanks!

Thanks!


librepo: 1.9.2 -> 1.11.2, zchunk

Motivation for this change
Update librepo, now featuring zchunk support
which is packaged in ##78040 as it's expected
(didn't check if required or just optional but default on).
This PR includes commit from zchunk PR.
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Welp, this made it into master from another PR (#79416)-- which better motivates the change anyway ^_^.
Closing!


Constructor

Should we ditch the DSN and just accept an array instead? i.e.
$AES = new \PCO\Symmetric([
    'driver' => 'openssl',
    'cipher' => 'aes-128'
]);

Arrays may be easier to read in the long run. What about using JSON if we made some sort of custom parser?

+1 on the array personally...no extra overhead of extra parsing just for the sake of it. I could see allowing both in the future though, just for convenience.

Okay, that's what I'll go with then.


Update munit, munit-scalacheck to 0.7.27

Updates

org.scalameta:munit
org.scalameta:munit-scalacheck

from 0.7.25 to 0.7.27.
GitHub Release Notes - Version Diff
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!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalameta" } ]

labels: test-library-update, semver-patch

Superseded by #393.


Build fails on OpenSSL 1.0

Since the TLS subject key id attribute was added in commit 9bb338e, OpenSSL 1.0 builds have been failing.

OpenSSL 1.0.x support has been removed with commit 04fb8a2.


Playlists in subfolders not shown

At the moment, it appears that any playlists that have been sorted into subfolders within the playlists folder are not shown in the "My Playlists" tab. I imagine this could be remedied if I just removed the subfolders, but I am hesitant to that as I have many playlists and would like to keep them organized in subfolders, especially for ones I create myself.

The beatlist created by Alaanor does not have that feature.
It will take some time to add that feature, so please be patient.

Thank you for the report.
Fixed.
https://github.com/ranmd9a/beatlist/releases/tag/v1.3.7

Thank you for the report. Fixed. https://github.com/ranmd9a/beatlist/releases/tag/v1.3.7

Thank you for the quick fix!

yw. If you have any problems, please create an issue again.


pyenv-rehash: look for python*

This was rejected for rbenv, where it does not make much sense
(https://github.com/sstephenson/rbenv/pull/735).
Ref: https://github.com/yyuu/pyenv/pull/368#issuecomment-102806837

@blueyed Could you explain the actual use case scenario of this?

@yyuu
The "use case" is that python2 and python3 get handled like python for this code path (PYENV_DIR gets set).

Idealistically all python, python2 and python3 should be handled evenly. Although, at least with current impl, python is the special name for executable in pyenv (and ruby for rbenv). Honestly I'm not sure what is the benefit of setting PYENV_DIR on invocation of python2 and python3 in addition to python....

python is the special name for executable in pyenv

So it's just for internal calls?
Then this PR is void - and I might add a comment instead.  It wasn't really clear to me what this was doing.  I've thought it would be triggered by calling python3 some.py, too.

Kind of internal call, or some kind of legacy code. I've just forgotten what that's for....
The PYENV_DIR will be read by ./libexec/pyenv and pyenv will once try to chdir to the directory if it is possible or not. However it will return to original cwd once it suceeded to chdir. So if I understand correctly it isn't so meaningful.

Re-opening.  See https://github.com/yyuu/pyenv/issues/404 for where this is relevant.

Good catch :+1:
I confirmed the behaviour reported on #404, and confirmed that this changes the behaviour to respect local version at symlink destination.
I believe your changes seem to be reasonable and useful for most cases, though it changes current behaviour slightly. Please add tests for this feature, then I'll merge this. (and, I think it's worth to reopen PR on rbenv as well)

I added tests in 438e828eb507536eebe42adee3e896bceb165d8c and merged into master. Thanks for PR.


De-dupe ODES responses by ID

@sleepylemur noticed that with two ODES keys, the list of ODES extracts was doubled up.

This was from a misunderstanding about the results of the /extracts list. /extracts?api_key=odes-1234567 returns the list of extracts associated with the developer that owns the key odes-1234567.
If you loop through all of a developer's odes keys and aggregate the results you will get duplicates.
Should just grab one of a developer's odes keys and show those extracts.


Update todo-java-postgresql-aca-terraform README

Update todo-java-postgresql-aca-terraform README to use azd init and azd up instead of azd up --template according to https://github.com/Azure/azure-dev/issues/1769.
@jongio, @rajeshkamal5050, @fangjian0423 for notification.

@zedy-wj can you close this one? since @fangjian0423 will be creating a new one for this under Azure-Samples.

Okay, closed it.


Remove CacheControl

It's just making the bot less reliable. @sarina, can you review this?

How does CacheControl make the bot less reliable?

@nedbat - it doesn't recognize new labels in the repo, and a few other things that I can't remember, but have always been solvable by restarting the bot so it's forced to clear its cache.
:+1:

(if this causes other issues we can always revert it)

:+1:


Proposed ordering for table entries

Currently the JSON table items are sorted mostly in alphabetical order.
It could be useful to order the entries from "minor" to "major" - i.e. so that treasure tables, for example, would have the most common items first, and the most rare and valuable items last.
This way it would be possible at a later stage to add modifiers to table "rolls". A modifier of, say, +10 would weigh the rarer end of the table and ensure that none of the cheapest trinkets would be generated. And vice versa for negative modifiers. (Minimum and maximum values should of course be capped to the lowest and highest values of the table, respectively.)
Even though that functionality is not yet available, the tables would already be ready for that functionality, if/whenever it will be available.
Would this be a sensible approach?

The original tables were created by a third person. I don't recall why the entries are sorted that way.
I like the idea of being able to apply mods to rolls on tables. This would extent the versatility of the generator nicely!

Great idea @evesala We could post guidelines/tips to file creators so they do more of this in the future. We might also ask the community for help editing files to a certain standard.
Is there a way to create a Healing category @JochenLinnemann on GitHub? Branch files to there with comments about what we'd like to see changed?

We could just create a Healing branch, add a markdown file of tasks and files, and let the work begin.

I have added some of my  tables to a separate branch. Is it OK for me to add improvement suggestions to the standard tables there?
When I'm happy with the updates, I could then ask you to check the changes so that they could be merged back to trunk.

Go for it!

Thanks! I have been a bit cautious about this, as I'm not familiar with your practices, but just let me know when I err.


VersionChecker doesn't check without command

VersionChecker is not executed when just calling the cli, it always requires an argument
$ export SIDEKICK_ENABLE_UPDATE_CHECK=true
$ noa

(no check)
$ export SIDEKICK_ENABLE_UPDATE_CHECK=true
$ noa vault

(does the check)
The reason for this is, that we do an early return for zero args
  if (args.isEmpty) {
    print(runner.usage);
    return;
  }

Will be fixed by #157


Cross Added To Sort Modal

Resolved issue #142
Cross Button Added to Sort Modal

@arzitmahajan Could you attach a video of the changes you made?

Also next time when you make a PR create a different branch other than main.

Ok I will Create different branch from next time
On Thu, Mar 3, 2022 at 11:41 PM Tess-Vanta @.***> wrote:

Also next time when you make a PR create a different branch other than
main.
—
Reply to this email directly, view it on GitHub
https://github.com/SaraswatGit/PlanZap/pull/160#issuecomment-1058339398,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARTWUAXWR3W5U7I2QXMT443U6D6F3ANCNFSM5P3GFCJA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

Yes sure
On Thu, Mar 3, 2022 at 11:41 PM Tess-Vanta @.***> wrote:

@arzitmahajan https://github.com/arzitmahajan Could you attach a video
of the changes you made?
—
Reply to this email directly, view it on GitHub
https://github.com/SaraswatGit/PlanZap/pull/160#issuecomment-1058338751,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARTWUAXQUO6VEJXH7A72WLTU6D6DLANCNFSM5P3GFCJA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

https://drive.google.com/file/d/1_byj4I89_R4bqqbK1sj3ILSPKxG17NU0/view?usp=sharing
On Thu, Mar 3, 2022 at 11:41 PM Tess-Vanta @.***> wrote:

@arzitmahajan https://github.com/arzitmahajan Could you attach a video
of the changes you made?
—
Reply to this email directly, view it on GitHub
https://github.com/SaraswatGit/PlanZap/pull/160#issuecomment-1058338751,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARTWUAXQUO6VEJXH7A72WLTU6D6DLANCNFSM5P3GFCJA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

https://drive.google.com/file/d/1_byj4I89_R4bqqbK1sj3ILSPKxG17NU0/view?usp=sharing
On Thu, Mar 3, 2022 at 11:41 PM Tess-Vanta @.***> wrote:

@arzitmahajan https://github.com/arzitmahajan Could you attach a video
of the changes you made?
—
Reply to this email directly, view it on GitHub
https://github.com/SaraswatGit/PlanZap/pull/160#issuecomment-1058338751,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARTWUAXQUO6VEJXH7A72WLTU6D6DLANCNFSM5P3GFCJA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

Good job!


refactor(): cleanup Promises handlers

@umarrasydan the root of this is actually the whole situation where some live Promises are by politicians that are not live.
we have several routes to go about this.
either way the ability to take a politician offline (live = false) should be retained
the paths to take:

on API side, ensure that the /promises/ endpoint returns only live promises by live politicians

this might be very expensive as it needs to check each politician's live value based on politician_id of the promise

create a handler whereby when a politician is taken offline, all their promises will be updated as offline too

we'd need both setPromisesToLive and setPromisesOffline methods

Aside from the above I feel like we should utilise the 'Status' field of politicians. The values can be 'active' and 'inactive'
We can have a separate section for inactive politicians

in short, this task is also blocked by the mentioned API design problem

We should definitely go with number 2


Human 1.15

Main improvements in this PR:

Fixes (PR #551)

remove MAR04568, make MAR04567 irreversible in the direction of ATP consumption, and phosphatase reaction MAR20070, as proposed in #547:

Features/Style (PR #550, #542):

add new contributors

Features (PR #549)

add new field geneShortNames for gene symbols, as discussed in #539

Features/Style (PR #546):

remove authors, email, and organization fields in code and Yaml file for moving toward community curation on GitHub

Fixes (PR #555, #541, #538, #532, #529, #525)

resolve duplicate krebs cycle reactions catalyzed by aconitase, isocitrate dehydrogenases, pyruvate dehydrogenase, 2-oxoglutarate dehydrogenase, as well as glycine cleavage system, by only keeping the highest resolution versions except IDH
pinpoint GPRs of above reaction to compartment-specific enzymatic genes, and modify reversibilities when necessary
the implementation plans are discussed in #523, #524, and #525
fix GPRs for Cytochrome C Oxidoreductase, as discussed in #526

Fixes (PR #540)

modify GPRs of MAR01453, MAR11476, MAR11479 AND MAR04281, as introduced in #528

Fixes (PR #537)

replace ENSG00000137700 with ENSG00000281500, as proposed in #510

take away GPI (ENSG00000105220) from transport reaction MAR04856
complete association to Uniprot ids in genes.tsv

remove other GCS genes from GPR of MAR06409, as discussed in #529

Features (PR #535)

add 87 new mets, 68 new reactions in Glycolysis pathway, as listed in #507

Fixes (PR #534)

remove duplicate met MAM00077x and corresponding rxns MAR03488 and MAR03489, as reported in #519

Fixes (PR #533)

rename mets in tyrosine exchange, transport, and metabolism reactions from XxxtyrYyy to XxxTyrYyy

Fixes (PR #520)

modify GPRs of CoA metabolism, as proposed by #502

Fixes (PR #518)

fix the met name of MAM02053, as discussed in #491

Fixes (PR #517)

remove wrongly associate genes in glycolysis (#507) and lactate dehydrogenase (#516)

Fixes (PR #515)

refine GPRs in Pentose phosphate pathway, as proposed in #501

Fixes (PR #513)

remove 21 pseudogenes, read through genes, and ones with only predicted functions, as proposed in #510.

Fixes (PR #509)

refine GPRs of Pyrroline-5-carboxylate reductase according to compartment and cofactor annotation reported in #505

Features (PR #508, #506)

add/update Rhea master IDs to reacitons.tsv annotation file for a total of 1334 reactions

Fixes (PR #504)

assign compartment-specific NAD kinase genes to MAR04268 and MAR04269, and remove MAR04279, based on discussion in #503

Fixes (PR #499)

separate genes TYMP (ENSG00000025708) and PNP (ENSG00000198805) to GPRs of MAR04603, MAR04695, MAR04709, and MAR04485, as reported in #498

Fixes (PR #497)

update the Docker image used in GH Actions workflow

Fixes (PR #496)

correct GPRs of Arginases (MAR03816 and MAR08426) by using compartment-specific enzymatic genes, as reported in #495

Features/Style (PR #492)

re-organize subsystem names by merging Pantothenate and CoA biosynthesis, CoA synthesis, and CoA catabolism into one Pantothenate and CoA metabolism, as proposed in #487

Fixes (PR #490)

refactor the GitHub workflow by using native support for Docker rather than a separate action

Fixes (PR #489)

fix GPR rules of mitochondrial complexes II, IV, and V, as proposed in #468, #469, #470 based on Complex Portal annotation

Here's small scale essentiality evaluation of combined Hart2015 datasets (all), by reusing the code of Human1 paper.

version
TP
TN
FP
FN
accuracy
sensitivity
specificity
F1
MCC

v1.12
40
2333
175
77
0.904000000000000
0.341880341880342
0.930223285486443
0.240963855421687
0.204768560393159

v1.13
40
2334
174
77
0.904380952380952
0.341880341880342
0.930622009569378
0.241691842900302
0.205504558241293

v1.14
40
2334
175
77
0.904036557501904
0.341880341880342
0.930251096054205
0.240963855421687
0.204787829413435

v1.15
40
2342
168
77
0.906737723639132
0.341880341880342
0.933067729083665
0.246153846153846
0.210053956889428

Overall, the latest model shows good improvements in decreased false positive values and increased true negatives, which actually reversed a little bit after #551 compared to the result #390.

IMHO, several comments:

forget about perfect, because being the best always delay things from getting better
follow the rule of release early, release often - Eric S. Raymond
therefore avoid too much curations (i.e. limit the number of PRs) for each release
welcome critical comments from research community, because given enough eyeballs, all bugs are shallow

#555 is now included to v1.15


WebP support

Hi.
Is it possible to add support for the WebP format?
There is a library for the "imagemin" that might help.
Thanks.

Hi @derevandal
Thanks for your feedback.
I don't think this is currently possible with this module. I suspect there may be further use case to not only use imagemagick/graphicsmagick, but also imagemin or other binaries. Perhaps it makes sense the create a 'third-party' pipeline in this module to execute anything else after imagemagick has done it's thing.
I'd like to leave this issue open and will tag as a feature request. I'm sure others may want to do something similar.
I don't have any immediate availability to work on this due to other commitments, so I'll pick this up if and when I get time in the coming weeks/months.
Thanks,
Barry


Lose images after db migration

Issue description:
After database migration (change site url) Kirki can't get some fields. I noticed then these fields contain image url, like this: a:1:{s:5:"image";s:52:"http://gameclubvr.cf71210.tmweb.ru/uploads/2017/10/vr-glasses.png";}. This image exists, but getting field or whole section return nothing (false/NULL).
If I choose same image again - it's works properly. In DB I have row: a:1:{s:5:"image";s:65:"http://gameclubvr.cf71210.tmweb.ru/uploads/2017/10/vr-glasses.png";}
Version used:
(Did you try using the develop branch from github? There's a chance your issue has already been adressed there)
3.0.10 from wpackagist
Using theme_mods or options?
options

Ok, I understand my problem - it's data serialization.
But my next question: why repeater field save image as ID and image field save image as URL?

Ok, I understand my problem - it's data serialization.

I'm glad that's sorted :)

But my next question: why repeater field save image as ID and image field save image as URL?

That's an inconsistency/bug, but the main problem here is that it's been this way for a long time and there are a lot of themes out there that use it like that now, so changing the implementation is a bit troublesome and could cause backwards-compatibility issues.
I'm experimenting with this in v3.1 and hopefully it will be resolved then in a way that doesn't cause compatibility issues.
I'm closing this one since there's already another ticket open for the repeater inconsistency. 👍


How to enrich document before indexing in ES for example?

Hello,
I have a collection with documents that keep an ObjectId reference to documents in another collection. Before sending document to index I need to retrieve the referenced document and to merge them (denormalize).
Can someone link an example?

Hi, I would try discuss.elastic.co logstash section.

+1

Hello! I'm going to close this ticket because it is out of the scope of the Mongo-Connector project.


Deploy chat application rather than web server

Updates for my 100 Day Plan tasks.

Deploy a node application rather than a static website I made a simple

https://github.com/stelligent/chat-app
This cleared up the zap warnings as well

Removed duplicate internet gateway template source files from the various iterations that went through
Add a rake task for running the config rules rather than calling gulp from the Jenkinsfile

This is so the results can be tested to actually stop the pipeline.

Add optional param to the create task so you can append an identifier to the CloudFormation stack

rake jenkins:create[<IP_ADDRESS>/0,davem]

Zap logs now get sent to /var/log/zap.out

@mince27 rebase?

I had completely forgotten about this 😅
I'll reopen/make a new PR when I get a chance.


Add routes

Current coverage is 43.78% (diff: 100%)

Merging #108 into master will decrease coverage by 0.15%

@@             master       #108   diff @@
==========================================
  Files            16         16
  Lines          8916       8916
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
- Hits           3918       3904    -14
- Misses         3992       4006    +14
  Partials       1006       1006

Powered by Codecov. Last update fff82c3...6c7c488


Lunarfusion/css 116 divider core tokens

Description
BREAKING CHANGE: This migrates the Divider component to core tokens.

Jira issue CSS-116 https://jira.corp.adobe.com/browse/CSS-116
Added static black and static white variants
No Windows High Contrast Mode specifications are included

How and where has this been tested?

Chrome 103 for macOS
Firefox 102 for macOS
Safari 15.5 for macOS
How this was tested: comparing local build of http://localhost:3000/docs/divider.html with XD redline components batch 2 and with https://spectrum.adobe.com/page/divider/

Screenshots

To-do list

[ ] If my change impacts other components, I have tested to make sure they don't break.
[x] If my change impacts documentation, I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have tested these changes in Windows High Contrast mode.

[ ] This pull request is ready to merge.

VRT test is: https://spectrum-visual-regression.ci.corp.adobe.com/view/Spectrum CSS/job/css-vrt-test/36/artifact/backstop_data/html_report/index.html
2022-08-10 -- 1486 - field-group.zip

VRT test is: 	https://spectrum-visual-regression.ci.corp.adobe.com/view/Spectrum CSS/job/css-vrt-test/34/artifact/backstop_data/html_report/index.html
2022-08-10 -- 1490 - divider.zip

Released:
<EMAIL_ADDRESS>

@jnurthen - would you be able to take a look at this in Windows High Contrast Mode and let us know if what's been done here is sufficient? You should be able to view it here: https://pr-1490--spectrum-css.netlify.app/docs/divider.html. Thank you!

Released updated beta<EMAIL_ADDRESS>


Iss 948

NetflixOSS » Hystrix » Hystrix-pull-requests #248 SUCCESS
This pull request looks good

I look forward to reviewing this Monday!

NetflixOSS » Hystrix » Hystrix-pull-requests #249 SUCCESS
This pull request looks good

@spencergibb thanks in advance, I haven't finish it yet, but you can take a look at the [test] (https://github.com/dmgcodevil/Hystrix/blob/master/hystrix-contrib/hystrix-javanica/src/test/java/com/netflix/hystrix/contrib/javanica/test/common/observable/BasicObservableTest.java) for observable, because PL is very big. BTW I didn't implement collapser feature for observable command, but hopefully will add it soon.

NetflixOSS » Hystrix » Hystrix-pull-requests #250 SUCCESS
This pull request looks good

NetflixOSS » Hystrix » Hystrix-pull-requests #251 SUCCESS
This pull request looks good

NetflixOSS » Hystrix » Hystrix-pull-requests #252 SUCCESS
This pull request looks good

@dmgcodevil Is this ready for review and merge?  If so, I'll take a look this weekend

@mattrjacobs yes, it's pretty much done except Collapser for observable but it will change within separate issue

@dmgcodevil :+1:

LGTM.  Thanks for all your work on this


x/tools/internal/diff: diff generates invalid edits

Just encountered in a regtest: formatting a particular go.work file (that isn't newline terminated) results in out of bounds edits:
env.OpenFile("go.work")
env.SetBufferContent("go.work", "go 1.18\nuse moda/a")
env.Save("go.work")

        metadata_test.go:175: formatting before save: editing "go.work": diff has out-of-bounds edits; edits:
            [{1:0 1:0
            } {2:0 2:0
            }]

CC @adonovan @pjweinb

The bug is in the fake editor's applyEedits function. Fix pending. (Sorry for casting aspersions on the diff package, which hasn't had any bugs yet.)


[Usage]  Can you consider making release?

When did you clone our code?
I cloned the code base after 5/1/23
Describe the issue
Issue:
For now i see there's no release in this repository and just commit directly to main branch, but i need llava package versioning to make my service, because package dependency changes frequently on version update.
How about make release of this repository?

plz...

right now it looks like a mess...

I can't follow these release versions too... 🥲

Thank you for the great suggestion! I have added the v1.0.1 release tag. In the future, we will conitnue adding necessary release notes as well.
Please let me know if you have any suggestions in terms of the workflow of this project.
Also, it seems that I cannot turn on the release on the main page of the github repo. Any ideas on why this is happening? Thanks.


create a settings directory for devtools docs

Problems:

The settings link on /web/tools/chrome-devtools links out to DCC.
The keyboard shortcuts doc is awkwardly organized under the iterate docs.
There's no natural place to document general appearance features, like being able to reorder the panel tabs.
Solution:
Create a directory /web/tools/chrome-devtools/settings and house the stuff there. We could name it "configure" so that it's consistent with the rest of action-oriented stuff, but I think "settings" is more straightforward. Or we can just store the docs directly under chrome-devtools. E.g. chrome-devtools/shortcuts, chrome-devtools/settings.

Thoughts @pbakaus?
cc @paulirish

We've left these things on the old page for some reason, but I think it makes sense to migrate them all over. That would only leave the "Let's work on DevTools themselves" docs on the old site, which is fine for now. Thoughts, @paulirish and @Meggin?

URL wise i don't care very much... but "just store the docs directly under chrome-devtools. E.g. chrome-devtools/shortcuts, chrome-devtools/settings."  is my favorite.
Left-nav wise I'd be fine if they never showed up, but if they only showed at top-level when open, that'd be cool too.
But regardless they should be linked from the homepage.

That was my preferred approach too. I'm going with that


Return the query with the findcontrolstate

of D85140.
@Snuffleupagus any suggestions?

Thanks!

/botio-linux preview

Thanks!


Auto-update on Linux

It would be great if the app could update itself instead of asking me to update it. It's a bit cumbersome to have to download and install updates on each of the desktops and laptop I use Toggl Desktop on

+1 for flatpak (or rpms)

Will be solved with creating flatpak


How is the ANCE FirstP training data generated?

How is the ANCE FirstP training data (bids_marco-doc_ance-maxp-10.tsv) generated?

Hi,
We followed the instructions in https://github.com/thunlp/OpenMatch/blob/master/retrievers/openmatch_ance_retriver_readme.md, loaded the checkpoint of TREC DL document firstP/maxP to encode the query and document, and inference the top-k documents similar to the query.
For each query-doc manual label, we randomly selected 10 docs from the top-k subset as negatives.
Kaitao

Hi,
We followed the instructions in https://github.com/thunlp/OpenMatch/blob/master/retrievers/openmatch_ance_retriver_readme.md, loaded the checkpoint of TREC DL document firstP/maxP to encode the query and document, and inference the top-k documents similar to the query.
For each query-doc manual label, we randomly selected 10 docs from the top-k subset as negatives.
Kaitao


Service calls

Break from issue #23 :
viliam-husar : allow service calls before and after fixtures file is loaded (not after object is persisted)
khepin : service calls: can't remember very precisely how it worked, have to look at it again

Currently from what I see in the code viliam-husar is right : the services are called just at object level, not before/after fixture files are loaded, but they are run right after the object is created and  not after persist is called on entity manager.
So @khepin the question is does the bundle want to support service calls before/after fixture file load ?
I could work on this if it's a scope ...
Thanks

Well if you have an immediate use for it, I'd say go ahead. Otherwise, This bundle has been roughly stable for a long time and I'm not sure there's much interest in this.

Currently I don't have a use case for this either, so maybe we can close this issue also until someone else has this use case.


Last Man Standing Bug!!

When i put or change the console to **#

serverGamemode = 5

**
no leaderboard no score fix

https://github.com/Megabyte918/MultiOgar-Edited/blob/master/src/gameserver.ini#L29
this is wrong or you.
btw as i have test. LMS work with 4.

same error

@systemroot That seems to be the case. But, I'm wondering. HOW DA HELL did the Server work cause there's no gamemode 5

The leaderboard works fine for me.

@Megabyte918 Same

lmao same here


Inconsistency in different implementation of rs2_project_point_to_pixel and rs2_deproject_pixel_to_point

Before opening a new issue, we wanted to provide you with some useful suggestions (Click "Preview" above for a better view):

Consider checking out SDK examples.
Have you looked in our documentations?
Is you question a frequently asked one?
Try searching our GitHub Issues (open and closed) for a similar issue.

All users are welcomed to report bugs, ask questions, suggest or request enhancements and generally feel free to open new issue, even if they haven't followed any of the suggestions above :)

Required Info

Camera Model
{ D455 }

Firmware Version
(Open RealSense Viewer --> Click info)

Operating System & Version
Ubuntu 20

Kernel Version (Linux Only)
(e.g. 4.14.13)

Platform
Any

SDK Version
mater

Language
C++/CUDA

Segment
{Robot/Smartphone/VR/AR/others }

Issue Description
Some time ago there were questions in #7335 about the distortion model of the D455, and it was confirmed that it was inverse brown conrady. At the end of that issue, it was mentioned that there was an implementation of rs2_deproject_pixel_to_point for the inverse brown conrady. That code looks like
    if (intrin->model == RS2_DISTORTION_INVERSE_BROWN_CONRADY)
    {
        // need to loop until convergence
        // 10 iterations determined empirically
        for (int i = 0; i < 10; i++)
        {
            float r2 = x * x + y * y;
            float icdist = (float)1 / (float)(1 + ((intrin->coeffs[4] * r2 + intrin->coeffs[1]) * r2 + intrin->coeffs[0]) * r2);
            float xq = x / icdist;
            float yq = y / icdist;
            float delta_x = 2 * intrin->coeffs[2] * xq * yq + intrin->coeffs[3] * (r2 + 2 * xq * xq);
            float delta_y = 2 * intrin->coeffs[3] * xq * yq + intrin->coeffs[2] * (r2 + 2 * yq * yq);
            x = (xo - delta_x) * icdist;
            y = (yo - delta_y) * icdist;
        }
    }
    if (intrin->model == RS2_DISTORTION_BROWN_CONRADY)
    {
        // need to loop until convergence
        // 10 iterations determined empirically
        for (int i = 0; i < 10; i++)
        {
            float r2 = x * x + y * y;
            float icdist = (float)1 / (float)(1 + ((intrin->coeffs[4] * r2 + intrin->coeffs[1]) * r2 + intrin->coeffs[0]) * r2);
            float delta_x = 2 * intrin->coeffs[2] * x * y + intrin->coeffs[3] * (r2 + 2 * x * x);
            float delta_y = 2 * intrin->coeffs[3] * x * y + intrin->coeffs[2] * (r2 + 2 * y * y);
            x = (xo - delta_x) * icdist;
            y = (yo - delta_y) * icdist;
        }

    }

Note that the both involves iteration, this seems incorrect, as according to the documentation here https://dev.intelrealsense.com/docs/projection-in-intel-realsense-sdk-20#section-distortion-models, for inverse conrady
This model provides a closed-form formula to map from distorted points to undistored points, while mapping in the other direction requires iteration or lookup tables.

and for brown conrady
This model provides a closed-form formula to map from undistorted points to distorted points, while mapping in the other direction requires iteration or lookup tables.

Therefore, for the same reprojection code, it cannot be true that both the forward and inverse distortion model would require iteration, one of them must be an incorrect implementation. I think in this case that the inverse brown conrady implementation is incorrect, because in the CUDA implementation of these functions in https://github.com/IntelRealSense/librealsense/blob/master/src/cuda/rscuda_utils.cuh, rs2_deproject_pixel_to_point for inverse brown conrady is
        if (intrin->model == RS2_DISTORTION_INVERSE_BROWN_CONRADY)
        {
            float r2 = x * x + y * y;
            float f = 1 + intrin->coeffs[0] * r2 + intrin->coeffs[1] * r2*r2 + intrin->coeffs[4] * r2*r2*r2;
            float ux = x * f + 2 * intrin->coeffs[2] * x*y + intrin->coeffs[3] * (r2 + 2 * x*x);
            float uy = y * f + 2 * intrin->coeffs[3] * x*y + intrin->coeffs[2] * (r2 + 2 * y*y);
            x = ux;
            y = uy;
        }

which is completely different from the deprojection code in the C++ implementation, and closed form, which matches the documentation.
This same inconsistency can be observed in the rs2_project_point_to_pixel code too, where the code for brown conrady and inverse brown conrady projection is functionally identical, which again violates what the documentation states. Given this, I'm think the projection and deprojection code for the inverse brown conrady distortion model in the C++ implementation is exactly flipped, the section for deprojection should be in projection, and vice versa.

Hi @oceanusxiv  As mentioned in your other case at https://github.com/IntelRealSense/realsense-ros/issues/2458#issuecomment-1225488204 the D455 is known for its unusual coefficients compared to other RealSense 400 Series camera models and the nature of its distortion model has been previously discussed.
As the D455 model functions correctly and accurately in regard to its image output, there is unlikely to be a problem with its distortion model code.

Hi again @oceanusxiv  I just wanted to update you that discussion of this subject with my Intel RealSense colleagues continues to be ongoing.  Thanks for your patience!

Whilst Intel discussions are ongoing, it may take some time before there is progress to report.  I have therefore added an Enhancement label to this case as a reminder to keep it open whilst those internal discussions are ongoing.

Hello! Any news about this issue? I plan to switch from D435 to D455 because of RGB sensor larger FOV needed for my object color segmentation and then I reconstruct the pointcloud based on undistorted aligned images of depth and color streams. I would like to use the undistorted RGB images to be aligned with Depth images. Will that be possible to do with D455?

Hi @levasmol  I checked the outcome of the discussions that my Intel RealSense colleagues had about this subject.  It was acknowledged that there was the possibility of a discrepancy between the documentation and how the distortion model was actually implemented.   They thought that it was unlikely though that there is a fundamental flaw in the implementation, such as using the reversed version of the model from what is needed.
If you are aligning with the SDK's align_to instruction then the SDK's 'align processing block' will automatically make adjustments for differences between the depth and RGB streams, no matter which camera model is used.

Hi @levasmol  Bearing in mind the response in the above comment, do you require further assistance with this case, please?  Thanks!

Case closed due to no further comments received.