Migrate BaseOptionsList.js to functional component

Details
Migration of BaseOptionsList to functional component. This component is used by OptionsSelector, which is used in many places. Because of this, we are testing more than one workflow.
Fixed Issues
$ https://github.com/Expensify/App/issues/16182
Tests

When in a room click on the header
Click on members
Check if members are correctly displayed
Exit the page/RHP
Enter the split bill workflow
Check if you can change the currency.
Enter the amount and click next
Check if the list of the users you want to split with is displayed properly
Check if you can change the users you want to split with by clicking them
Exit the page/RHP
Try to assign task, navigate to assignee screen
Check if assignees are correctly displayed
Choose the assignee

[x] Verify that no errors appear in the JS console

Offline tests

When in a room click on the header
Click on members
Check if members are correctly displayed
Exit the page/RHP
Enter the split bill workflow
Check if you can change the currency.
Enter the amount and click next
Check if the list of the users you want to split with is displayed properly
Check if you can change the users you want to split with by clicking them
Exit the page/RHP
Try to assign task, navigate to assignee screen
Check if assignees are correctly displayed
Choose the assignee

[x] Verify that no errors appear in the JS console

QA Steps

When in a room click on the header
Click on members
Check if members are correctly displayed
Exit the page/RHP
Enter the split bill workflow
Check if you can change the currency.
Enter the amount and click next
Check if the list of the users you want to split with is displayed properly
Check if you can change the users you want to split with by clicking them
Exit the page/RHP
Try to assign task, navigate to assignee screen
Check if assignees are correctly displayed
Choose the assignee

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] If we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web

https://github.com/Expensify/App/assets/43684335/9d559808-607e-4003-b21d-fa4c85af2172

Mobile Web - Chrome

https://github.com/Expensify/App/assets/43684335/08c513e3-41e1-4625-9066-2db00b64e946

Mobile Web - Safari

https://github.com/Expensify/App/assets/43684335/46a00874-1f32-4856-b7b1-1cf1e128d3ce

Desktop
https://github.com/Expensify/App/assets/43684335/120881f8-5c0a-4a89-b2fc-820a21163cbc

iOS

https://github.com/Expensify/App/assets/43684335/85bf8cf6-8ed4-4ee3-a8c7-d511b30a02c5

Android
https://github.com/Expensify/App/assets/43684335/1bee5d96-f18c-46ba-b1f8-e991a5b42d74

LGTM, thanks for the changes 👍

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by https://github.com/marcaaron in version: 1.3.58-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/luacmartins in version: 1.3.58-5 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to staging by https://github.com/marcaaron in version: 1.3.59-0 🚀

platform
result

🤖 android 🤖
failure ❌

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/luacmartins in version: 1.3.59-5 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅


Add PHP samples for GCP buildpacks

Cool.  Can you flatten the dirs under sample-php-entrypoint like to sample-php-entrypoint-envar to be consistent with the others?  Also, can you add Cloud Run Button to the READMEs and add each sample to the root README?

@jamesward - Addressed your comments.

Thanks!


Add Better AWS Worker Tagging

Propagate any AWS Terraform Provider Default Tags To Worker Instances & Volumes for better AWS account management.
The only tag attached to worker nodes presently when they are spun up by the ASG is their Name.  In many scenarios however it is desirable to classify infrastructure with additional tags whether it be for billing / cost analysis / environment segregation etc.  Indeed the AWS Terraform Provider provides for this in its declaration.  This works out-of-the-box for many assets, e.g. in Typhoon's case for EC2 controller nodes, NLBs etc.  However, Application Scaling Groups need special attention if the intent is to have the dynamic nodes they spin up tagged correctly.  This enhancement addresses this point.
Doing so has necessitated switching from AWS's legacy Launch Config methodology to the newer recommended Launch Template methodology which has more flexibility in amongst other things specifying tags.
High level description of the change.

Change is confined solely to fedora-coreos workers.tf presently pending maintainer feedback.
Change will be extended to cover flatcar too if there is buy-in for this change.

Testing

Terraform used to update existing spot worker node cluster in-place successfully and new worker node EC2/EBS tags validated via console.
New terraform cluster deployed with on-demand worker nodes and tags validated on worker nodes.

Launch Template Items For Discussion

Launch Template Root block device declarations require a device name which has been hard coded to /dev/xvda which should work fine for Fedora CoreOS x86 AMIs ... for the time being ... but is perhaps potentially brittle.  Also, aarch64?
Launch Templates are versioned objects in AWS.  We define the ASG to use the $Latest which seems reasonable given the Launch Template is not shared.
Launch Templates with spot instances require an instance_market_options block which seemingly does not support on-demand instances.  Instead for on-demand the block is absent.  A dynamic terraform block implements this.

Other Topics For Discussion

Right now I've arbitrarily chosen to apply/cascade tagging to instance and volume assets.  It is equally possible to also cascade to other assets, e.g. elastic-gpu, network-interface, spot-instances-request.  See here.

@dhubble this is my first pull request so apologies for any unintentional faux-pas, e.g. if it is bad form to submit one without an accompanying issue.  Do you have any thoughts on content?  (Awesome project by the way - I'm inching towards using it in anger but currently just experimenting with two small test clusters).

No problem.  Closing.


Delay when clicking the select button - Uploading files feature

Problem description
The first time you open the ODE on your laptop, there is a minor delay after clicking the Select button within the Upload your data feature. I then opened the ODE several times and repeated the same action and it seems to work faster. Is this an expected behavior during the first run?
https://github.com/user-attachments/assets/c073443d-22fe-493c-b9a6-3971156ca6ba

I'm closing this issue. It's a minor delay outside the ODE operation (user laptop)


Exposes all chunk types through the API.

Fixes issue #57.

@nwin Do you want to merge this before releasing 0.10?


Where can the integrity value of a v3.3.7 Bootswatch theme be found?

We are using a 3.3.7 Bootswatch theme served up from the CDN, using an integrity attribute:
 <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootswatch/3.3.7/paper/bootstrap.min.css" integrity="sha384-awusxf8AUojygHf2+joICySzB780jVvQaVCAt1clU3QsyAitLGul28Qxb2r1e5g+" crossorigin="anonymous">
We would like to use the "slate" theme:
<link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootswatch/3.3.7/slate/bootstrap.min.css">
Where can I find the integrity attribute value for the 3.3.7 version of the slate theme?

You can use https://www.srihash.org/ for this.

Or do it manually:
openssl dgst -sha384 -binary local-folder/css/bootstrap.min.css | openssl base64 -A


Compatibility with pip10

After update to pip10, I met a problem with running migrations, related with your library.
pip install --upgrade pip
Collecting pip
  Downloading pip-10.0.0-py2.py3-none-any.whl (1.3MB)
    100% |████████████████████████████████| 1.3MB 768kB/s
Installing collected packages: pip
  Found existing installation: pip 9.0.3
    Uninstalling pip-9.0.3:
      Successfully uninstalled pip-9.0.3
Successfully installed pip-10.0.0
...
python manage.py migrate --noinput
Traceback (most recent call last):
  File "manage.py", line 9, in <module>
    execute_from_command_line(sys.argv)
  File "/srv/project/lib/python3.6/site-packages/django/core/management/__init__.py", line 364, in execute_from_command_line
    utility.execute()
  File "/srv/project/lib/python3.6/site-packages/django/core/management/__init__.py", line 338, in execute
    django.setup()
  File "/srv/project/lib/python3.6/site-packages/django/__init__.py", line 27, in setup
    apps.populate(settings.INSTALLED_APPS)
  File "/srv/project/lib/python3.6/site-packages/django/apps/registry.py", line 108, in populate
    app_config.import_models()
  File "/srv/project/lib/python3.6/site-packages/django/apps/config.py", line 202, in import_models
    self.models_module = import_module(models_module_name)
  File "/opt/Python-3.6/lib/python3.6/importlib/__init__.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 994, in _gcd_import
  File "<frozen importlib._bootstrap>", line 971, in _find_and_load
  File "<frozen importlib._bootstrap>", line 955, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 665, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 678, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/srv/project/src/app1/models.py", line 15, in <module>
    from app2.hasoffers.models import HOffer
  File "/srv/project/src/app2/hasoffers/models.py", line 14, in <module>
    from djoffers.models import HasOffersModel as DefaultHasOffersModel
  File "/srv/project/lib/python3.6/site-packages/djoffers/models.py", line 5, in <module>
    from pyoffers.api import HasOffersAPI
  File "/srv/project/lib/python3.6/site-packages/pyoffers/api.py", line 9, in <module>
    from .models import MANAGER_ALIASES, MODEL_MANAGERS, ApplicationManager
  File "/srv/project/lib/python3.6/site-packages/pyoffers/models/__init__.py", line 10, in <module>
    from .raw_log import RawLogManager  # noqa
  File "/srv/project/lib/python3.6/site-packages/pyoffers/models/raw_log.py", line 6, in <module>
    from pip.utils import cached_property
ModuleNotFoundError: No module named 'pip.utils'

Information from pypi's newsletter may be useful for you:

In addition, the previously announced reorganisation of pip's
internals has now taken place. Unless you are the author of code that
imports the pip module (or a user of such code), this change will not
affect you. If you are affected, please report the issue to the author of the
offending code (refer them to
https://mail.python.org/pipermail/distutils-sig/2017-October/031642.html
for the details of the announcement).

Thank you for the bug report! It will be fixed soon


Updating client library

Please refer to the code of conduct : link

Please check if the PR fulfills these requirements :clipboard:

[x] The commit message follows our guidelines : link
[x] Docs have been added/updated (for bug fixes/features)
[x] A new branch is created for the change(s) and the changes are not committed on the main or master branch
[x] No credentials or secrets are committed

What kind of change does this PR introduce? (Bug fix, feature, docs update, refactor, chore, test, config) :information_desk_person: :scroll:
chore, refactor, docs

Updated the version number in openapi specs to 1.1.0
Refactored classes to resolve checkstyle errors
Updated client library

Checklist for the current PR :page_with_curl:

[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] New and existing unit tests pass locally with my changes
[x] pmd, check style issues are resolved locally
[x] I have added reviewers to check the proposed changes

retest this please

ok to test

ok to test

Build finished.

Build finished.

Build finished.

ok to test

Build finished.

Build finished.

Build finished.

Build finished.

Build finished.


[FLINK-35639][runtime] Fixes wrong deprecation in RestartStrategies#FixedDelayRestartStrategyConfiguration

What is the purpose of the change
The package-private constructor slipped through when deprecating the Time classes in FLINK-32570 causing the the ClassCastException when deserializing the 1.18 JobGraph with 1.19 as described in FLINK-35639:
[...]
Caused by: java.lang.ClassCastException: cannot assign instance of org.apache.flink.api.common.time.Time to field org.apache.flink.api.common.restartstrategy.RestartStrategies$FixedDelayRestartStrategyConfiguration.delayBetweenAttemptsInterval of type java.time.Duration in instance of org.apache.flink.api.common.restartstrategy.RestartStrategies$FixedDelayRestartStrategyConfiguration
    at java.io.ObjectStreamClass$FieldReflector.setObjFieldValues(ObjectStreamClass.java:2096) ~[?:?]
    at java.io.ObjectStreamClass$FieldReflector.checkObjectFieldValueTypes(ObjectStreamClass.java:2060) ~[?:?]
    at java.io.ObjectStreamClass.checkObjFieldValueTypes(ObjectStreamClass.java:1347) ~[?:?]
    at java.io.ObjectInputStream$FieldValues.defaultCheckFieldValues(ObjectInputStream.java:2679) ~[?:?]
    at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:2486) ~[?:?]
    at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:2257) ~[?:?]
    at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1733) ~[?:?]
    at java.io.ObjectInputStream$FieldValues.<init>(ObjectInputStream.java:2606) ~[?:?]
    at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:2457) ~[?:?]
    at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:2257) ~[?:?]
    at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1733) ~[?:?]
    at java.io.ObjectInputStream.readObject(ObjectInputStream.java:509) ~[?:?]
    at java.io.ObjectInputStream.readObject(ObjectInputStream.java:467) ~[?:?]

Brief change log

Added package-private constructor back and marked it as deprecated

Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
I verified once more that we don't have any other similar error in the FLINK-32570 related commits: https://github.com/apache/flink/commit/99d6fd3c68f46daf0397a35566414e1d19774c3d and https://github.com/apache/flink/commit/c943ab49
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): yes
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: yes
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? no
If yes, how is the feature documented? not applicable

Closing the PR again. See the comments in FLINK-35639 for further details.


Fix duplicate item in User Guide

Motivation and context

This PR contains the removal of a duplicate of the "Annotation with automatic segmentation" item, since this duplicates the "Make AI polygon" item.
How has this been tested?

N/A
Checklist

[x] I submit my changes into the develop branch
[ ] I have added description of my changes into CHANGELOG file
[x] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[ ] I have linked related issues (read github docs)
[ ] I have increased versions of npm packages if it is necessary (cvat-canvas,
cvat-core, cvat-data and cvat-ui)

License

[x] I submit my code changes under the same MIT License that covers the project.
Feel free to contact the maintainers if that's a concern.
[x] I have updated the license header for each file (see an example below)

# Copyright (C) 2020 Intel Corporation
#
# SPDX-License-Identifier: MIT

Pull Request Test Coverage Report for Build 5370

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.02%) to 65.666%

Totals

Change from base Build 5369:
0.02%

Covered Lines:
10838

Relevant Lines:
16101

💛  - Coveralls


Booleans not changed into int values by MonitorRegistryMetricPoller

From the documentation on the wiki I understand that the poller is able to change booleans into 0/1 values.

The poller will try to match all values with simple numeric types. Boolean data will also be collected and recorded as a 1 if the value is true and 0 if the value is false.

Looking in my implementation and while debugging I see that my boolean values still end up in metrics as boolean values instead of integers. This makes that the metric is not published to Cloudwatch because CloudWatchMetricObserver checks for a numerical value.
Should I use a different poller, or am I missing something else?
NB. It is fairly easy to extend MonitorRegistryMetricPoller and override the getValue() method, but since the docu is so explicit I wonder if I could do it without implementing a custom poller.

I know that is something the JmxMetricPoller does, not sure if it was ever done anywhere else. @dmuino might have more context.

I'm afraid I don't have any more context. I was unaware of the fact that JmxMetricPoller converts booleans to numbers. Internally we don't use the JmxMetricPoller, and just ignore non-numeric values. My vote is to fix the documentation to reflect that fact.

I'm affraid that I have to change MonitorRegistryMetricPoller to also have this ability. We use it to monitor Hystrix (with the help of hystrix-servo-metrics-publisher and the most important metric is isCircuitBreakerOpen, which is a boolean.
I will make a PR when I get it working.

PR created: https://github.com/Netflix/servo/pull/428 not sure why it is not linked automatically


mix.scripts no error if file is not found

"laravel-mix": "^0.8.1",
node v7.2.1
npm 3.10.10
If a file specified in .script is not existing compile is running normal.
I expected an error like it is happening in .js.
By the way thanks for this great tool!
Best Max

That's because you could provide a regular expression, so we can't easily check if the file exists (I don't think). So it just skips over it, if it can't read the file.

Hi, I have the same trouble..
mix.styles([
'node_modules/html5-boilerplate/dist/css/main.css',
'node_modules/datatables/media/css/dataTables.bootstrap.css'
], 'public/css/vendor.css'));
results
/css/vendor.css  58.5 kB          [emitted]
results If I change the filenames
/css/vendor.css  0 kB          [emitted]
But no errors or warnings.


Update readme files with config changes

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

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

Totals

Change from base Build<PHONE_NUMBER>1:
0.0%

Covered Lines:
724

Relevant Lines:
957

💛  - Coveralls


Error Domain=NSURLErrorDomain Code=-1202 "The certificate for this server is invalid

Image not load. getting error when i load the image.
2019-10-11 11:07:34.697971+0530 ABCMobile[6924:2083244] Connection 11: default TLS Trust evaluation failed(-9843)
2019-10-11 11:07:34.698030+0530 ABCMobile[6924:2083244] Connection 11: TLS Trust encountered error 3:-9843
2019-10-11 11:07:34.698048+0530 ABCMobile[6924:2083244] Connection 11: encountered error(3:-9843)
2019-10-11 11:07:34.699320+0530 ABCMobile[6924:2083244] Connection 11: unable to determine interface type without an established connection
2019-10-11 11:07:34.699836+0530 ABCMobile[6924:2083244] Task <03DD0ADE-1638-41D9-B779-6543C536539A>.<13> HTTP load failed, 0/0 bytes (error code: -1202 [3:-9843])
2019-10-11 11:07:34.701356+0530 ABCMobile[6924:2083742] Task <03DD0ADE-1638-41D9-B779-6543C536539A>.<13> finished with error [-1202] Error Domain=NSURLErrorDomain Code=-1202 "The certificate for this server is invalid. You might be connecting to a server that is pretending to be “abc.xyz.com” which could put your confidential information at risk." UserInfo={NSLocalizedRecoverySuggestion=Would you like to connect to the server anyway?, _kCFStreamErrorDomainKey=3, NSErrorPeerCertificateChainKey=(
"<cert(0x128879800) s: *.pacificabs.com i: RapidSSL RSA CA 2018>",
"<cert(0x12887a200) s: RapidSSL RSA CA 2018 i: DigiCert Global Root CA>"
), NSErrorClientCertificateStateKey=0, NSErrorFailingURLKey=https://abc.xyz.com/Image/UserImage/c66ca0dc-3cd2-41eb-872f-5bb7ff09cbb2.png, NSErrorFailingURLStringKey=https://abc.xyz.com/Image/UserImage/c66ca0dc-3cd2-41eb-872f-5bb7ff09cbb2.png, NSUnderlyingError=0x281ecd230 {Error Domain=kCFErrorDomainCFNetwork Code=-1202 "(null)" UserInfo={_kCFStreamPropertySSLClientCertificateState=0, kCFStreamPropertySSLPeerTrust=<SecTrustRef: 0x282270a20>, _kCFNetworkCFStreamSSLErrorOriginalValue=-9843, _kCFStreamErrorDomainKey=3, _kCFStreamErrorCodeKey=-9843, kCFStreamPropertySSLPeerCertificates=(
"<cert(0x128879800) s: *.pacificabs.com i: RapidSSL RSA CA 2018>",
"<cert(0x12887a200) s: RapidSSL RSA CA 2018 i: DigiCert Global Root CA>"
)}}, _NSURLErrorRelatedURLSessionTaskErrorKey=(
"LocalDataTask <03DD0ADE-1638-41D9-B779-6543C536539A>.<13>"
), _kCFStreamErrorCodeKey=-9843, _NSURLErrorFailingURLSessionTaskErrorKey=LocalDataTask <03DD0ADE-1638-41D9-B779-6543C536539A>.<13>, NSURLErrorFailingURLPeerTrustErrorKey=<SecTrustRef: 0x282270a20>, NSLocalizedDescription=The certificate for this server is invalid. You might be connecting to a server that is pretending to be “abc.xyz.com” which could put your confidential information at risk.}
2019-10-11 11:07:34.791273+0530 ABCMobile[6924:2083244] [] tcp_input [C11.2:3] flags=[R.] seq=2594700783, ack=1391590276, win=0 state=FIN_WAIT_1 rcv_nxt=2594700783, snd_una=1391590275
2019-10-11 11:07:43.938050+0530 ABCMobile[6924:2083757] Connection 12: default TLS Trust evaluation failed(-9843)
2019-10-11 11:07:43.938139+0530 ABCMobile[6924:2083757] Connection 12: TLS Trust encountered error 3:-9843
2019-10-11 11:07:43.938179+0530 ABCMobile[6924:2083757] Connection 12: encountered error(3:-9843)
2019-10-11 11:07:43.940587+0530 ABCMobile[6924:2083757] Connection 12: unable to determine interface type without an established connection
2019-10-11 11:07:43.940993+0530 ABCMobile[6924:2083757] Task .<14> HTTP load failed, 0/0 bytes (error code: -1202 [3:-9843])
2019-10-11 11:07:43.943060+0530 ABCMobile[6924:2083742] Task .<14> finished with error [-1202] Error Domain=NSURLErrorDomain Code=-1202 "The certificate for this server is invalid. You might be connecting to a server that is pretending to be “abc.xyz.com” which could put your confidential information at risk." UserInfo={NSLocalizedRecoverySuggestion=Would you like to connect to the server anyway?, _kCFStreamErrorDomainKey=3, NSErrorPeerCertificateChainKey=(
"<cert(0x12801e000) s: *.pacificabs.com i: RapidSSL RSA CA 2018>",
"<cert(0x128044000) s: RapidSSL RSA CA 2018 i: DigiCert Global Root CA>"
), NSErrorClientCertificateStateKey=0, NSErrorFailingURLKey=https://abc.xyz.com/Image/UserImage/c66ca0dc-3cd2-41eb-872f-5bb7ff09cbb2.png, NSErrorFailingURLStringKey=https://abc.xyz.com/Image/UserImage/c66ca0dc-3cd2-41eb-872f-5bb7ff09cbb2.png, NSUnderlyingError=0x281ecdce0 {Error Domain=kCFErrorDomainCFNetwork Code=-1202 "(null)" UserInfo={_kCFStreamPropertySSLClientCertificateState=0, kCFStreamPropertySSLPeerTrust=<SecTrustRef: 0x28226eb50>, _kCFNetworkCFStreamSSLErrorOriginalValue=-9843, _kCFStreamErrorDomainKey=3, _kCFStreamErrorCodeKey=-9843, kCFStreamPropertySSLPeerCertificates=(
"<cert(0x12801e000) s: *.pacificabs.com i: RapidSSL RSA CA 2018>",
"<cert(0x128044000) s: RapidSSL RSA CA 2018 i: DigiCert Global Root CA>"
)}}, _NSURLErrorRelatedURLSessionTaskErrorKey=(
"LocalDataTask .<14>"
), _kCFStreamErrorCodeKey=-9843, _NSURLErrorFailingURLSessionTaskErrorKey=LocalDataTask .<14>, NSURLErrorFailingURLPeerTrustErrorKey=<SecTrustRef: 0x28226eb50>, NSLocalizedDescription=The certificate for this server is invalid. You might be connecting to a server that is pretending to be “abc.xyz.com” which could put your confidential information at risk.}
2019-10-11 11:07:44.003372+0530 ABCMobile[6924:2083143] [] tcp_input [C12.2:3] flags=[R.] seq=2456623032, ack=3372388621, win=0 state=FIN_WAIT_1 rcv_nxt=2456623032, snd_una=3372388620
Thanks in Advance

Sorry, we use our GitHub project for bug reports and feature requests. In the future, you should open questions like this on Stack Overflow.
Cheers. 🍻

From our Contribution Guidelines
Asking Questions
We don't use GitHub as a support forum. For any usage questions that are not specific to the project itself, please ask on Stack Overflow instead. By doing so, you'll be more likely to quickly solve your problem, and you'll allow anyone else with the same question to find the answer. This also allows maintainers to focus on improving the project for others.


Feature/billing

There's currently no way to exit a trial and go back to self custody wallet. We could add the same (...) button with just one option to opt out of the trial and a confirmation?

There's currently no way to exit a trial and go back to self custody wallet. We could add the same (...) button with just one option to opt out of the trial and a confirmation?

looks like a product decision generally. Let's discuss this with @anilmurty
in the meanwhile I don't really see any reason to add extra into this PR, the feature is incomplete anyway

Funn

There's currently no way to exit a trial and go back to self custody wallet. We could add the same (...) button with just one option to opt out of the trial and a confirmation?

looks like a product decision generally. Let's discuss this with @anilmurty in the meanwhile I don't really see any reason to add extra into this PR, the feature is incomplete anyway

nice coincidence. I ran into that just this morning - was trying to show someone a demo of the "Start Trial" button and couldn't get back into that state after starting a trial. let's discuss for sure


coq: making sure coq master and 9.0 compile

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] 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/)
25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)

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

[ ] Fits CONTRIBUTING.md.

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

For now this errors with the following message when running ./result/bin/coqtop :confused:
Welcome to Coq 9.0+alpha
Error:
Findlib error: zarith not found in:
/nix/store/c2hwnp5ryalzz1rwldp7a87lzxaq1329-coq-dev/lib/coq/../coq-core/..
/nix/store/c2hwnp5ryalzz1rwldp7a87lzxaq1329-coq-dev/lib/coq/user-contrib/Ltac2
/nix/store/c2hwnp5ryalzz1rwldp7a87lzxaq1329-coq-dev/lib/coq/user-contrib/Ltac2/Compat
/nix/store/bj6kj93sbg5j0vgv5yrxfcq91fj9pqfi-ocaml4.14.2-findlib-1.9.8/lib/ocaml/4.14.2/site-lib
required by `coq-core.interp'

Thanks Cyril for working on this! Regarding the coqtop failure, did you try wrapping the binary (like, e.g., rtop): https://github.com/NixOS/nixpkgs/blob/b3438737b45049d9968e8ad510fb1d188d6b13b7/pkgs/development/compilers/reason/rtop.nix#L23-L28

This was wrong advice. Sorry about that.
I guess this PR can be closed, thanks to the nice work by Pierre.

Subsumed by https://github.com/NixOS/nixpkgs/pull/364617/


Not all whitespace in  tags is preserved

What is this feature about (expected vs actual behaviour)?
While spaces and tabs are preserved, newlines inside
 tags are gone.
string(23) "
foo	bar		zoo
"

How can I reproduce it?
$html = '

foo
        bar
                zoo

';

$htmlMin = new voku\helper\HtmlMin();
$result = $htmlMin->minify($html);

var_dump($result);

Does it take minutes, hours or days to fix?
Unsure
Any additional information?
Using 3.1.3 installed via composer on PHP 7.2.10.

fixed in version 3.1.5


Update: solution for [Day 28] in [Python] language to run with python v3

day 28 in #4

@osoba request you to go through Contributing guideline about commit message format. also you need to comment on the issue first to tell which all question you want to work on before raising PR.

@sagarchoudhary96 I think I've successfully renamed all of the commit messages, and I also made a comment on #4, thanks


Font family not defined

Example from time tracker plugin page, think font family "FontAwesome" was forget

Hi,
Which version of Time Tracker plugin do you use?
I recommend hicknhack-software/redmine_time_tracker, it's still being developed and is supported by PurpleMine.
The one you have doesn't work, because there is missing icon class, which applies font and some other basic styling for icons.

Ah, sorry, my mistake - there are in fact missing icons in report. Fix is on the way!

Fixed with 76fc0f4

I use the forked repository from hicknhack-software.
Thanks !


Documentation Streamlit Code

@adhamarif since you ask me to create a topic for this and already said that you wanted to add your documentation I would also like to ask you to remove the code in our project which we don't use/need, because you currently have the best overview of our project since you built the platform with Streamlit on that we will work.

Noted. I will working on that 👍

Most of the code in streamlit has documentation there. If there sis no upcoming issue, Im considering to close this issue.
Do you guys have any comment? @l4nz8 @till-teb @velixko


docs: document CI versions of Ubuntu

[ ] Have you followed the guidelines in our Contributing document?
[ ] Have you checked to ensure there aren't other open Pull Requests for the same change?
[ ] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.
[ ] Have you successfully run brew style with your changes locally?
[ ] Have you successfully run brew typecheck with your changes locally?
[ ] Have you successfully run brew tests with your changes locally?

Review period will end on 2022-08-02 at 00:00:00 UTC.

As asked in #13619, here is a first attempt to document our decision (if everyone is in line with this). The document is still a draft.

Review period ended.

I rewrote the documentation based on all your feedback.
@MikeMcQuaid I did not describe the migration process: I plan to do this in a second pull request, to keep the discussion focused in this one.

Done. Let's gather some more feedback before merging this.

@MikeMcQuaid / @carlocab I initially wrote 22.04, and I think this was discussed elsewhere, but I thought no strong decision was taken up to now.
I sort of changed my mind as I wrote the text, because I wanted an explanation for our reasoning. It's my fault that it changed in this pull request.
I was looking at the statistics @sjackman posted on Slack: 50% of our users are using Ubuntu 20.04 and 20% Ubuntu 22.04.
This means that if we use 22.04, more than 50% of our users will need to install Homebrew's glibc.
My logic for using 20.04 (the proposed latest LTS - 1 "rule") was that there is a 2 year timeframe after a LTS release were adoption is low. Using the latest version as soon as it is released is probably not ideal. With this strategy it leaves 2 years for usage to grow.
On macOS there are always 3 supported versions: the rotation is 3 years. There we can always ship the latest version because we build for 3 macOS versions. On Linux we are not doing this, so a 2 year rotation is a good middle ground in my opinion.
Of course if we already decided to use 22.04 and there are good reasons (that we want to write down), then disregard my change and let me know :)

I'll try to make a case for 22.04 instead.  From what I understand, the desire to limit how many users have to use brewed glibc and seems to have at least 3 motivations:

Extra disk space usage - my response to this is that disk space is cheap and we have much larger formulae like LLVM which are widely installed.
For non-default prefixes, glibc is trickier to install because it has to use the host toolchain - now that we are (for now) vendoring all but the most basic build dependencies in https://github.com/Homebrew/homebrew-core/pull/106837 and I hope to get glibc an :any cellar soon, this concern should be greatly reduced and hopefully irrelevant in the future.
For non-default prefixes, some formulae may fail to build with brewed glibc that work if the host glibc were being used - this invariably seems to be result of shim bypasses or opportunistic linking, which is something that formula aren't supposed to be doing and should be fixed.  If binary patching actually succeeds in a 95% reduction in non-relocatable formulae I'm anticipating from previous testing, this will also become a largely irrelevant concern.

There is also concern about using a newer GCC in 22.04 in CI because some (mostly C++) formulae will fail to build, but I also think this is something we should try to fix, and usually it's just a matter of some missing include statements.  It's also trivial to build with an older brewed GCC if needed, because at run time the libstdc++ provided by the either the host or brewed GCC is backwards compatible and consequently the older GCC only has to be build dependency.
By contrast, when a formula needs a newer GCC because our host GCC in CI is too old, it can be quite painful.  All C++ dependents of that formulae immediately acquire a dependency on brewed GCC as well.  While we have taken the steps to make sure this no longer holds up GCC updates, it still creates a maintenance headache.  Importantly, unlike the above issues, it is not due to "bad behavior" on the part of the formula like shim bypasses, opportunistic linking or lack of maintenance to maintain compatibility with newer GCC.
Ironically this problem is more likely for formula which are very actively maintained and try to use newer features of C++. To me we shouldn't be creating maintenance burdens for formulae which are doing the right thing by staying up to date.  It makes a lot of sense for us to be submitting upstream fixes when formulae are missing include statements or hardcoding compilers.  It makes a lot less sense for us to be spending time playing "catch up" with the latest C++ standards because our host compiler is too old.
There are probably many valid rebuttals to what I've said so please let me know what you think!

My logic for using 20.04 (the proposed latest LTS - 1 "rule") was that there is a 2 year timeframe after a LTS release were adoption is low. Using the latest version as soon as it is released is probably not ideal. With this strategy it leaves 2 years for usage to grow.

Does this mean we have a 2 year window to migrate but also we have to migrate in that 2 year window?
I'd probably like to see something like e.g. we use the latest LTS at least ~3-4 months after release and we always migrate to the latest LTS within at most 12 months of release.
Given we're a rolling-release package manager and we're aggressively migrating to the latest macOS version on release (sometimes even in public beta): we need to ensure that macOS and Linux are somewhat in-step with e.g. compiler usage.

This means that if we use 22.04, more than 50% of our users will need to install Homebrew's glibc.

my response to this is that disk space is cheap

I agree with this. This is similar to what we've done with portable Ruby on macOS: often only the newest version of macOS with relatively low adoption avoids a portable Ruby but this makes it easier for us to be able to rely on a newer Ruby version everywhere. Same deal here but with glibc and gcc.
@danielnachun for reference: how big is a 1) bottled and 2) installed glibc today?

2. I hope to get glibc an :any cellar soon, this concern should be greatly reduced and hopefully irrelevant in the future.

@danielnachun how hard is this looking currently? Is it a question of overzealous detection we could hack around in Homebrew/brew or legitimate location hardcoding that will break when moved?

To me we shouldn't be creating maintenance burdens for formulae which are doing the right thing by staying up to date.

Agreed. Again: we're a rolling-release package manager. We try to ship the newest things as quickest as possible. That's going to be easier for us on Linux with newer toolchains.

I rewrote the document for Ubuntu 22.04, with some more explanations. @danielnachun / @MikeMcQuaid I copied / adjusted some stuff you said above directly into the documentation. It will probably need some rewording but at least we can all agree on the reasoning and the final choice for Ubuntu 22.04 (this year) and the proposed migration timeline.

@danielnachun for reference: how big is a 1) bottled and 2) installed glibc today?

It's 200MB in both cases to my knowledge.  Not the smallest package but not huge either.

@danielnachun how hard is this looking currently? Is it a question of overzealous detection we could hack around in Homebrew/brew or legitimate location hardcoding that will break when moved?

It is absolutely legitimate location hardcoding, so prefix patching is obligatory for this to work.  That on its own isn't too bad as we know how we will implement that.  The harder part is that there are 3 issues I'm aware of where prefix patching is insufficient to make glibc relocatable.
Two of them are because in iconv and gconv there are string constants with prefixes in them that are "garbled" in such a way that we can't do the standard replacement and the tools end up failing because they still have prefix references.  I suspect this is because of how the constants are defined in the code but I have to test if that is actually right.
The other problem is that ld.so appears to bake in a list of directories to search for libraries separated by of all things a null character, which gets messed up when the prefix replacement occurs.  I believe it should be possible to write and upstream a patch to fix these issues, but I haven't had the time to dig into this yet because of all the other issues we're trying to work out right now.  For that reason I'd like to tackle this once we've completed the migration, as I can't promise a timeline of when I'll be able to figure everything out.

@danielnachun for reference: how big is a 1) bottled and 2) installed glibc today?

It's 200MB in both cases to my knowledge. Not the smallest package but not huge either.

Yeh, that's tiny.

It is absolutely legitimate location hardcoding, so prefix patching is obligatory for this to work. That on its own isn't too bad as we know how we will implement that. The harder part is that there are 3 issues I'm aware of where prefix patching is insufficient to make glibc relocatable.

@danielnachun Good to know. From my perspective I think we need to operate with the assumption that this will take a non-trivial amount of time after a migration to occur. If we beat that pessimistic assumption: great, but let's not rely on it for our plans.
Does that change anyone's mind given it's the case?

For that reason I'd like to tackle this once we've completed the migration, as I can't promise a timeline of when I'll be able to figure everything out.

👍🏻 totally fair @danielnachun.

Let's merge this. I'll work on adding a small section for the necessary migration steps (though these may change over time as new challenges arise).


Update OAI ETDMS format for lastest  ndltd.org standard

ETDMS format update: the Texas Digital Library Metadata group released new guidelines for ETDs (https://tdl-ir.tdl.org/tdl-ir/handle/2249.1/68437), part of this study looked at the current DSpace ETD OAI format. Due to changes in the ndltd.org standard, author names and degree information are not being exposed through the default DSpace OAI-ETD format. An updated version is available here: https://github.com/TexasDigitalLibrary/DSpace/blob/dspace-5_x-TDL-ETD/dspace/config/crosswalks/oai/metadataFormats/etdms1-1.xsl

Hi @mprivero : First off, thanks for trying to give us these changes.
To create a clean PR, you might need to create a new Git branch (based off the latest "master" branch) and only bring in the single XSL that you are trying to send our way.
If it ends up being too confusing, you are also welcome to just send us the updated XSL (or a patch file) in a new JIRA ticket (https://jira.duraspace.org/projects/DS/issues) and we can find someone to turn it into a Pull Request.
For now, I'm going to close this PR as we'll need to get one that just includes the XSL changes


fix(): rework effect implementation field validation, adjust error message

split reset field logic into multiple useEffects,
rework effect implementation field validation to be based on effect type and scala version,
add react-hook-form devtools and enable them in development environment for ease of debugging.

Looks better!


issue with mosquitto.pem in example MqttEncryptedUnauthenticated.ino

Hi David,
I was testing with a SIM7600E-H,4G LTE cat 4 modem and found an issue in the MqttEncryptedUnauthenticated.ino example.
In the example the name of the Mosquito CA Cert is defined as: #define MOSQUITTO_CA_CERTNAME "mosquitto.pem"
It took quite some time to find the reason why the example did not work.
The command to  set the server root CA of the first SSL context should be: AT+CSSLCFG=”cacert”,0,”mosquitto.pem”
But when you use the example the command send to the module was:  AT+CSSLCFG=”cacert”,0,mosquitto.pem
And it does not produce an error! Just a normal "OK"
So whithout quotes.
When changing the setCert command in the code to: if (mqtt.setCaCert(""mosquitto.pem"") == false)  solves the problem. Just simply escaping the quotes.
I test only the MQTT related examples and the SaveCertificates example but it all looks good until now.
I will test with a SIM7670G as well.
I was surprised as well about the performance of the SIM7600E-H,4G LTE cat 4. It seems very useful for my project were I have burst of event data (10 hz).
Do you have any plans on extending the library? i.e. with GNSS?
Thanks for your excellent work and kind regards,
Adriaan

Hi Adriaan,
I think the fix is easy, just adding extra quotes in configSSLCacert should work.
Can you check if updating the function configSSLCacert like so
    // CSSLCFG cacert
    int8_t configSSLCacert(uint8_t ssl_ctx_index, const char* ca_file) {
        _serial.sendCMD("AT+CSSLCFG=\"cacert\",", ssl_ctx_index, ",\"", ca_file, "\"");
        A76XX_RESPONSE_PROCESS(_serial.waitResponse());
    }

does the job? if so, I will accept a pull request.
For the GNSS functionality, i so have implemented most of things, and I have an unpublished branch that does pretty much what's needed. I need to get back to it, but i have struggled to get good gps signal on my devices in my flat, so I have not been able to test stuff well enough. I could push the branch to github and set the GPS feature to be "experimental" for people to try it out.

Yes that would be a valid solution. I will test it tomorrow and let you know.
If there is a way I would like to test the GNSS functionality and provide you feedback.

closed by #7

closed by #7

Hi @aquila1968, the new branch "gnss" is ready for you to look at. You could start with the GNSS example sketch.
There are also some other changes, including less String allocations, that is have made, so I would appreciate a lot if you also tested the branch  with other examples, or with your own code.
Many thanks!


Create an opcap debug mode report for failed or timed out operators

While troubleshooting operator installation, generally speaking, engineers will follow some steps like the ones below:

check events
check CSV status
check installPlan status
check operator's pod status
check operator's CR status and conditions
check for messages in OLM package server

The proposal here is to create a report as rich as possible that can be enabled for a short list of operators that are either failing or timing out in order to determine the cause of failure and gather data to approach the partner developer.

Include deprecated APIs:

you may find errors on the controller logs.
check for RBAC permissions as well
check OCP kube api version and check release notes
check OCP api endpoints on release notes as well

@acmenezes: @yashoza19 and I were reviewing use of ApiRequestCount API.
It appears too unreliable due to the time it takes to populate with origin user account.
We were thinking we could tie into PR #334 and check installreport for KubeAPIWarningLogger. We did some testing and thsi should not only appear in controller logs when watching a deprecated endpoint, but will also appear on any CRUD function against API (i.e. after CR creation/operand install).


Refactor convert_batch_append_all

The method convert_batch_append_all uses the same logic twice for very similar situations. That code should be refactored to allow the minor differences to be passed in as arguments.

Currently, this is how the method is being processed:
#!/usr/bin/python3

from cgc import CGC

cgc = CGC()
use_images_dir = "/tmp/cards"
cgc.convert_batch_individual(use_images_dir)
cgc.convert_batch_append_all()

It is expected to not require any inputs and is a "do everything" method. It should also be refactored to execute cgc.convert_batch_individual() in itself:
#!/usr/bin/python3

from cgc import CGC

cgc = CGC()
cgc.convert_batch_append_all()

The code has been refactored. The other concerns mentioned here about default values will be addressed with the upcoming CLI update.


Quick fix until I can get Photoshop to do what I tell it.

Confirmed fixes the problem. Splash screen is unaffected.


tile cannot extend outside image

File "C:\Python37\lib\site-packages\PIL\ImageFile.py", line 504, in _save
e.setimage(im.im, b)
SystemError: tile cannot extend outside image

Did you get this error when starting the script?

when try to configure screen

You need to cut the image from low points to high points (first left points and after that, right points). You may be cutting the first point as the higher point and this will cause the error that you sent.
How to do that? Start selecting the point more left side and then the right side points.
Thank you very much to notice the error. I will fix that as soon as possible. Untill that, try what i said.

did u have discord? maybe because im running it on linux

Yeah! What is your user? I can ping you there.

Riven Lara#2774


Fix unit tests to load segments from correct directory

Fixed unit tests that were loading segments from incorrect directory.
Also fixed BitmapInvertedIndexTest logic to actually load inverted indexes
for testing.
Tests: Unit tests

Current coverage is 64.29% (diff: 100%)

No coverage report found for master at cf0b1da.

Powered by Codecov. Last update cf0b1da...3b57e35


disallow user-defined function overloading

Danny Goldstein reported on stan-users that the following problem parses and code generates, but doesn't compile.
functions {

  real add_mul(int a, int b){
    return a + b * a + b;
  }

  vector add_mul(vector a, vector b){
    return a + b .* a + b;
  }

}

data {
  int N;
  vector[N] y;
  vector[N] x;
}

parameters {
  real sigma;
  real m;
  real b;
}

model {
  vector[N] f;
  f <- m * x + b;
  y ~ normal(f, sigma);
}

This produces the following error on the develop branch of cmdstan and stan:
--- Linking C++ model ---
clang++ -DBOOST_RESULT_OF_USE_TR1 -DBOOST_NO_DECLTYPE -DBOOST_DISABLE_ASSERTS -I src -I stan/src -isystem stan/lib/stan_math_2.7.0 -isystem stan/lib/eigen_3.2.4 -isystem stan/lib/boost_1.58.0 -Wall -pipe -DEIGEN_NO_DEBUG -Wno-unused-function -Wno-tautological-compare -Wno-c++11-long-long -ftemplate-depth=256    -O0 -o /Users/carp/temp2/dg src/cmdstan/main.cpp -include /Users/carp/temp2/dg.hpp
In file included from <built-in>:326:
In file included from <command line>:5:
/Users/carp/temp2/dg.hpp:71:8: error: redefinition of 'add_mul_functor__'
struct add_mul_functor__ {
       ^
/Users/carp/temp2/dg.hpp:41:8: note: previous definition is here
struct add_mul_functor__ {
       ^
1 error generated.

Either we need to figure out how to allow overloading, or have stanc catch the redeclaration and return an error.

I am continuing to think that appending the argument types to the C++ class name would work around this relatively easily
https://groups.google.com/d/msg/stan-users/arKMsfesJp0/ld_KVwj2YNUJ

Hi folks,
I have PyStan installed on a Linux environment with no internet connection, so I installed it from source.
I keep getting the following output:
python nealfunnel.py pystan version: <IP_ADDRESS> INFO:pystan:COMPILING THE C++ CODE FOR MODEL anon_model_0abdc67925ea6570cce7f28cf38d9cd4 NOW. Traceback (most recent call last):   File "nealfunnel.py", line 12, in <module>     fit = pystan.stan(file = 'funnelright.stan', iter=1000, chains=4)   File "/home/workgroups/reit/apps/python/2.7.7/pystan/<IP_ADDRESS>/lib/python2.7/site-packages/pystan/api.py", line 368, in stan     verbose=verbose)   File "/home/workgroups/reit/apps/python/2.7.7/pystan/<IP_ADDRESS>/lib/python2.7/site-packages/pystan/model.py", line 312, in __init__     build_extension.run()   File "/apps/python/2.7.7/lib/python2.7/distutils/command/build_ext.py", line 337, in run     self.build_extensions()   File "/apps/python/2.7.7/lib/python2.7/distutils/command/build_ext.py", line 446, in build_extensions     self.build_extension(ext)   File "/apps/python/2.7.7/lib/python2.7/distutils/command/build_ext.py", line 496, in build_extension     depends=ext.depends)   File "/apps/python/2.7.7/lib/python2.7/distutils/ccompiler.py", line 574, in compile     self._compile(obj, src, ext, cc_args, extra_postargs, pp_opts)   File "/apps/python/2.7.7/lib/python2.7/distutils/unixccompiler.py", line 122, in _compile     raise CompileError, msg distutils.errors.CompileError: command 'gcc' failed with exit status 1
I have the latest version of Pystan, with Stan 2.9.0. Also, I have RStan installed on the same environment and it works fine.
Thank you in advance

@aeleuterio would you mind opening an issue at the pystan repository? https://github.com/stan-dev/pystan/issues When you open an issue, please let us know what Linux distribution you're using and what version of gcc if you know it.

@ariddell Will do, I apologize for posting on the wrong forum


Changes all occurences of %(RelativePath) to %(RelativeDir) in csharp doc

This fixes some misleading syntax in src/csharp/BUILD-INTEGRATION.md. I lost several hours trying to follow the documentation as is until i figured out that the keyword was wrong. I am submitting this PR to hopefully prevent others from doing the same.

@veblush

CC @kkm000

CC @Falco20019 do you agree?

Docs only change, merging.

RelativeDir should be correct. I will update the documentation again once we discussed if we take the proposed approach with ProtoRoot.
@simo9000 Thanks for fixing!


Making a version of rx.redirect that opens a new tab

because currently, returning rx.redirect edits the existing tab, i wanted a version that will open a new tab with the link, while keeping the old tab active, a developer on the discord told me to create an issue

bump

bump

Solved by #1902


fix install-global

I was so focused on the local installation scenario that I didn't notice I broke install-global.

CI: https://travis-ci.org/dunn/qi/builds/182909812

Ah dang, good catch. I'll test this one locally, but feel free to merge whenever if you're happy with it! And nice tests, that's great.


Remove types.ParseUint64orHex and use the one from common package

Description
Removes types.ParseUint64OrHex and uses the existing function from the common package.
Changes include

[ ] Bugfix (non-breaking change that solves an issue)
[ ] Hotfix (change that solves an urgent issue, and requires immediate attention)
[ ] New feature (non-breaking change that adds functionality)
[ ] Breaking change (change that is not backwards-compatible and/or changes current functionality)

Checklist

[ ] I have assigned this PR to myself
[ ] I have added at least 1 reviewer
[ ] I have added the relevant labels
[ ] I have updated the official documentation
[ ] I have added sufficient documentation in code

Testing

[ ] I have tested this code with the official test suite
[ ] I have tested this code manually

types package keeps additional functions: ParseUint256orHex, ParseBytes, ...  Isn't it better to leave ParseUint64OrHex inside types and remove it from common?

types package keeps additional functions: ParseUint256orHex, ParseBytes, ... Isn't it better to keep ParseUint64orHex inside types and remove it from common? Otherwise, ParseUint256orHex will be a part of types and ParseUint64orHex will be a part of common

Yes it would be better, however it is not possible because of this function:
https://github.com/0xPolygon/polygon-edge/blob/develop/helper/common/common.go#L83-L97 (it uses ParseUint64OrHex and it is not possible to move it to types package because of circular imports).


Any plan for avif/hcif support?

as title

Thanks for your interest in my project. I've had a look and I'm not able to find a decoder that's both written in pure Rust and looks sufficiently mature. I'll keep your ticket open to remind me to check again in the future.


[SPARK-39109][PYTHON] Adjust GroupBy.mean/median to match pandas 1.4

What changes were proposed in this pull request?
The PR is proposed to

Implement numeric_only of SeriesGroupBy.mean and DataFrameGroupBy.mean
Adjust SeriesGroupBy.mean/median to match pandas 1.4

Why are the changes needed?
Improve API compatibility with pandas.
Does this PR introduce any user-facing change?
Yes. GroupBy.mean/median behaves the same as pandas 1.4's.
Take GroupBy.mean as an example:

DataFrameGroupBy.mean

>>> psdf = ps.DataFrame({"A": [1, 2, 1, 2],"B": [3.1, 4.1, 4.1, 3.1],"C": ["a", "b", "b", "a"],"D": [True, False, False, True]})
>>> psdf
   A    B  C      D
0  1  3.1  a   True
1  2  4.1  b  False
2  1  4.1  b  False
3  2  3.1  a   True

>>> psdf.groupby('A').mean(numeric_only=False)
...: FutureWarning: Dropping invalid columns in GroupBy.mean is deprecated. In a future version, a TypeError will be raised. Before calling .mean, select only columns which should be valid for the function.
  warnings.warn(
     B    D
A
1  3.6  0.5
2  3.6  0.5

>>> psdf.groupby('A').mean(numeric_only=None)
...: FutureWarning: Dropping invalid columns in GroupBy.mean is deprecated. In a future version, a TypeError will be raised. Before calling .mean, select only columns which should be valid for the function.
  warnings.warn(
     B    D
A
1  3.6  0.5
2  3.6  0.5

>>> psdf.groupby('A').mean(numeric_only=True)
     B    D
A
1  3.6  0.5
2  3.6  0.5

# Not raise the FutureWarning when there is no non-numeric aggregation column
>>> psdf[['A', 'B', 'D']].groupby('A').mean(numeric_only=False)
     B    D
A
1  3.6  0.5
2  3.6  0.5

SeriesGroupBy.mean

>>> psdf.groupby("A")["C"].mean()
Traceback (most recent call last):
...
TypeError: Only numeric aggregation column is accepted.

How was this patch tested?
Unit tests.

@ueshin @HyukjinKwon @itholic @Yikun May I get a review? Thank you!

Merged to master.


fix: dap erased after typo

closes https://github.com/TBD54566975/didpay/issues/269
https://github.com/user-attachments/assets/f9001b6e-0e7f-4f00-a6c0-c32e62e3f200

Amazing and fast work!


Fix Android Q with Conscrypt or Session Tickets

09:29:05 V/InstrumentationResultParser: INSTRUMENTATION_STATUS: numtests=13
09:29:05 V/InstrumentationResultParser: INSTRUMENTATION_STATUS: stream=
09:29:05 V/InstrumentationResultParser: INSTRUMENTATION_STATUS: test=testConscryptRequest
09:29:05 V/InstrumentationResultParser: INSTRUMENTATION_STATUS_CODE: 1
09:29:05 V/InstrumentationResultParser: INSTRUMENTATION_STATUS: class=okhttp.android.test.OkHttpTest
09:29:05 V/InstrumentationResultParser: INSTRUMENTATION_STATUS: current=13
09:29:05 V/InstrumentationResultParser: INSTRUMENTATION_STATUS: id=AndroidJUnitRunner
09:29:05 V/InstrumentationResultParser: INSTRUMENTATION_STATUS: numtests=13
09:29:05 V/InstrumentationResultParser: INSTRUMENTATION_STATUS: stream=.
09:29:05 V/InstrumentationResultParser: INSTRUMENTATION_STATUS: test=testConscryptRequest
09:29:05 V/InstrumentationResultParser: INSTRUMENTATION_STATUS_CODE: 0
09:29:06 V/InstrumentationResultParser: INSTRUMENTATION_RESULT: stream=
09:29:06 V/InstrumentationResultParser:
09:29:06 V/InstrumentationResultParser: Time: 14.037
09:29:06 V/InstrumentationResultParser:
09:29:06 V/InstrumentationResultParser: OK (12 tests)
09:29:06 V/InstrumentationResultParser:
09:29:06 V/InstrumentationResultParser:
09:29:06 V/InstrumentationResultParser: INSTRUMENTATION_CODE: -1
09:29:06 V/InstrumentationResultParser:
09:29:06 I/XmlResultReporter: XML test result file generated at /Users/yuri/workspace/okhttp/android-test/build/outputs/androidTest-results/connected/TEST-New_Device_API_29(AVD) - 10-android-test-.xml. Total tests 13, passed 11, assumption_failure 1, ignored 1,
09:29:06 V/ddms: execute 'am instrument -w -r   -e notClass org.conscrypt.KitKatPlatformOpenSSLSocketImplAdapter okhttp.android.test.test/android.support.test.runner.AndroidJUnitRunner' on 'emulator-5554' : EOF hit. Read: -1
09:29:06 V/ddms: execute: returning
09:29:06 V/ddms: execute: running pm uninstall okhttp.android.test.test
09:29:06 V/ddms: execute 'pm uninstall okhttp.android.test.test' on 'emulator-5554' : EOF hit. Read: -1
09:29:06 V/ddms: execute: returning

> Task :android-test:connectedAndroidTest
> Task :android-test:connectedCheck

Deprecated Gradle features were used in this build, making it incompatible with Gradle 6.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/5.5/userguide/command_line_interface.html#sec:command_line_warnings

BUILD SUCCESSFUL in 28s


Allow different profit percentages for some items

Firstly, this mod is amazing and something I've been looking for for some time! Absolutely fantastic work @BeanHeaDza
High volume, low cost commodities like crops may be 10% profit while furniture or one time purchases you may want a higher percentage.  I'm suggesting the ability to set different profit margins for specific items, or possibly category.
I'm very happy to work with you in coding new features as well if wanted.

Thanks @AllDayJon!
Yeah I've had some suggestions about it as well. I definitely want this in the mod.
I think adding two new sections to the config would help. One for tags and one for items. The code needs to always prioritize picking from the items list, and it shouldn't allow duplicate items or tags in the UI (I haven't played around with the UI validation yet).
And then if an item matches multiple tags it should always follow the rule of the topmost tag. So hopefully you can drag drop items in the ui to reorder. It would also need some form of a tooltip to explain how the tag priorities works.
The explain text would also need a foldout on the profit section when an item or tag is matched and the overriden percentage is used instead.
That's my thinking on how to add the feature. Feel free to suggest changes if you'd like it done another way that might be better or simpler.
And PRs are always more than welcome.

We had someone who made a custom change for this mod on our server in the past that added so you could specify one or more categories with one symbol/letter/number at the start of the category name to use a seperate profit amount. (You can set the character that you use yourself) (Credit to FilixDark)


⚠ SolarOscp has degraded performance

In 1a73ed5, SolarOscp ($SOLAROSCP_URL) experienced degraded performance:

HTTP code: 200
Response time: 256 ms

Resolved: SolarOscp performance has improved in b7eea34.


Ability to use tags independently from different models

This PR is based on 2 issues:

when used on different models, tags get unified by name and taggings_count shows sum across all models
for a simple thing like "get all tags applicable to 1 model, not to others" we have to aggregate through taggings like group by type, use ids to select tag records and counts instead of taggings_count.

After PR we can use an option to split tags exclusively for a model
class Order < ActiveRecord::Base
  acts_as_taggable exclusive: true # this will isolate order tags completely
end

# and use additional dsl to get needed tags only
ActsAsTaggableOn::Tag.exclusively_for(:order)

For further details please, see updated readme and a new spec :)
P.S. I saw find_or_create_tags_from_list_with_context in the code, but I think this hook looks kinda ugly, exclusively option makes this useless, as you can pass a tags_class directly and it will work out of the box.
Do you like the idea of PR?
I also thought about making type column optional and commentabe/uncommentable in migration for users which don't wont to migrate possible huge tables, but WDYT about default behaviour?

Have you tried to use context ?
https://github.com/mbleigh/acts-as-taggable-on/blob/master/lib/acts_as_taggable_on/taggable.rb#L39-L41
I think almost use case is cleared by using context .
If you need excluding after using context,  I think you should implement the method for negative condition of below.
https://github.com/mbleigh/acts-as-taggable-on/blob/master/lib/acts_as_taggable_on/tag.rb#L51-L55
Thanks.

@syguer you're partially right, but the drawback of context is that it's located on taggings, but really we need it (or I suggest type on tags)
Please see https://github.com/mbleigh/acts-as-taggable-on/issues/700 people already complaining about that and forking because of this

I've understood it is convenient if tags have context( or type, kind).
Idea looks good. But my concern is It looks complicated and decrease maintainability.
Maybe, best solution is it is able to create some tags-taggings set.
I want to hear maintainer's opinion.


Control email of github-actions bot?

Hello! I found this GH action recently and I would love to use it in my repository: https://github.com/google/comprehensive-rust/pull/2396.
However, I've run into a small problem: we use a CLA bot to ensure that we have the correct paperwork for everybody who contributes to the repository. It seems we don't have this for the github-actions user which becomes a co-author of the PR:

I will try to talk with the people in Google who maintain the CLA bot about this — I just wanted to note the issue and ask if you perhaps know of a way to control the email address used? Perhaps it would be possible to post the comment as a different user completely?
Ah, reading a bit more lead me to this discussion — the email address used it the same for all actions done by the bot. So I guess this would have to be handled on our side.

https://github.com/actions/stale/issues/61#issuecomment-625653899 seems to answer my first question — it would be possible to use a different bot user by changing the token used.

https://github.com/actions/stale/issues/61#issuecomment-625653899 seems to answer my first question — it would be possible to use a different bot user by changing the token used.

Yes, that's right. The default token used is GITHUB_TOKEN. You can use a different token with the token input. I recommend using a GitHub App token in this case. Here's an example:
jobs:
  suggest-changes:
    runs-on: ubuntu-latest
    steps:
      - name: Generate token
        id: generate-token
        uses: actions/create-github-app-token@v1
        with:
          app-id: ${{ vars.APP_ID }}
          private-key: ${{ secrets.APP_PRIVATE_KEY }}
      - name: Suggest changes
        uses: parkerbxyz/suggest-changes@v1
        with:
          token: ${{ steps.generate-token.outputs.token }}

Let me know if that answers your questions and if you have any additional questions. 🙂

Thanks for the help, I'll talk with our admins to see if I can create and install such an app.


ARTEMIS-1542 - AMQP message cluster-bridging fix

Fixing and issue where AMQP messages would lose their address when being sent accross a cluster-bridge.

@clebertsuconic  @michaelandrepearce
in ClusterConnectionBridge.beforeForward(Message message, SimpleString forwardingAddress), we call super.beforeForward(message, null). The is why we lose the address. This code path is executed when broker1 forwards an AMQP message to broker2. This is why we will only see this in a cluster, when a producer sends a message to broker1 and a consumer is listening on broker2.

The address wasn’t set at the producer.
The address would be reset at the target.

I am still seeing the issue. With the changes in this PR, the issue is resolved. Can you please look at the diff?

 messageCopy = super.beforeForward(messageCopy, null);

 messageCopy = super.beforeForward(messageCopy, forwardingAddress);

Why would we want to call super.beforeForward() with a null second arg? This is the source of the problem.

@toddbaert just for future reference, as I told you on #1701 I made a mistake a reverted your fix by accident. this PR is fixing my accidental revert...
it should be done now.. thanks for contributing!!! Opensource rocks!

@clambertus  :guitar: Opensource :guitar:  Thanks so much for your help! I've tested and all seems well now.

@toddbaert clambertus? :)


memory leak when more request is received

I found there is a meory leack issue when I used this on our production env.
We used nginx server with 4core , 4GB memory
When I used nginx without this moudle,  on our production env,  nginx used 20% memory.
When I just add serverlist_service at http , and no call on it , nginx used 50% memory.
serverlist_service url=http://anther-server/upstream/ conf_dump_dir=/data/temp/dump interval=5s timeout=2s;

When call serverlist_service in upstream, nginx memory will increasing up to almost 100%,
 serverlist apiServerList;
    server fake_server down;
    include /data/temp/apiServerList.conf*;

I had a screen shot for server:

nginx -V output with nginx-upstream-serverlist module:
nginx version: openresty/<IP_ADDRESS>
built by gcc 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.11)
built with OpenSSL 1.1.1d  10 Sep 2019
TLS SNI support enabled
configure arguments: --prefix=/data/server/openresty/nginx --with-cc-opt=-O2 --add-module=../ngx_devel_kit-0.3.1rc1 --add-module=../echo-nginx-module-0.61 --add-module=../xss-nginx-module-0.06 --add-module=../ngx_coolkit-0.2 --add-module=../set-misc-nginx-module-0.32 --add-module=../form-input-nginx-module-0.12 --add-module=../encrypted-session-nginx-module-0.08 --add-module=../srcache-nginx-module-0.31 --add-module=../ngx_lua-0.10.15 --add-module=../ngx_lua_upstream-0.07 --add-module=../headers-more-nginx-module-0.33 --add-module=../array-var-nginx-module-0.05 --add-module=../memc-nginx-module-0.19 --add-module=../redis2-nginx-module-0.15 --add-module=../redis-nginx-module-0.3.7 --add-module=../rds-json-nginx-module-0.15 --add-module=../rds-csv-nginx-module-0.09 --add-module=../ngx_stream_lua-0.0.7 --with-ld-opt=-Wl,-rpath,/data/server/openresty/luajit/lib --pid-path=/data/server/openresty/nginx/var/nginx.pid --http-client-body-temp-path=/data/server/openresty/nginx/temp/client_body_temp --http-proxy-temp-path=/data/server/openresty/nginx/temp/proxy_temp --http-fastcgi-temp-path=/data/server/openresty/nginx/temp/fastcgi_temp --http-uwsgi-temp-path=/data/server/openresty/nginx/temp/uwsgi_temp --http-scgi-temp-path=/data/server/openresty/nginx/temp/scgi_temp --with-poll_module --with-threads --with-file-aio --with-http_v2_module --with-http_realip_module --with-http_addition_module --with-http_xslt_module --with-http_xslt_module=dynamic --with-http_image_filter_module --with-http_image_filter_module=dynamic --with-http_geoip_module --with-http_geoip_module=dynamic --with-http_sub_module --with-http_dav_module --with-http_flv_module --with-http_mp4_module --with-http_gunzip_module --with-http_gzip_static_module --with-http_auth_request_module --with-http_random_index_module --with-http_secure_link_module --with-http_degradation_module --with-http_slice_module --with-http_stub_status_module --with-mail=dynamic --with-mail_ssl_module --with-stream --with-stream=dynamic --with-stream_ssl_module --with-stream_realip_module --with-stream_geoip_module --with-stream_geoip_module=dynamic --with-stream_ssl_preread_module --with-pcre=/data/src/pcre-8.43 --with-zlib=/data/src/zlib-1.2.11 --with-openssl=/data/src/openssl-1.1.1d --add-module=/data/src/nginx-module-vts --add-module=/data/src/nginx-upstream-serverlist --with-stream --with-stream_ssl_preread_module --with-http_ssl_module

request to nginx  with QPS > 4000, it will happend definitely， you may test it.
memory increase is slow,  it used about 5 hours from 50% to 90% on our servers.

这个插件只有一个已知的内存泄漏, 只发生在后端serverlist频繁刷新的时候, 其余时候在我们公司的线上是稳定的, 包括双十一期间, 我们的请求量在单机8000以上.
你能把你的serverlist内容贴一下么?

serverlist返回的就是很多话如下配置信息：
server server001:8000 weight=10 max_fails=5 fail_timeout=1s;
大概30个左右，内存泄露很明显。

能把整个文件附在附件里吗?

curl http://<IP_ADDRESS>:8080/upstream/apiServerList
server sapi-001:8081 weight=10 max_fails=5 fail_timeout=1s;
server sapi-002:8081 weight=55 max_fails=3 fail_timeout=1s;
server sapi-003:8081 weight=55 max_fails=3 fail_timeout=1s;
server sapi-004:8081 weight=55 max_fails=3 fail_timeout=1s;
server sapi-005:8081 weight=55 max_fails=3 fail_timeout=1s;
server sapi-006:8081 weight=55 max_fails=3 fail_timeout=1s;
server sapi-007:8081 weight=55 max_fails=3 fail_timeout=1s;
server sapi-008:8081 weight=55 max_fails=3 fail_timeout=1s;
server sapi-009:8081 weight=55 max_fails=3 fail_timeout=1s;
server sapi-010:8081 weight=55 max_fails=3 fail_timeout=1s;
其他见文件
ng-conf.zip

OK, I saw, and the case is caused by the pool used by the serverlist parser, which is the main conf's never-destroyed pool. Every parse action may allocate some memory, and never free.
It is intentionally, because nginx is designed only support static conf, and the upstream servers struct in the static conf are used in many code corners, so free outdated upstream servers struct is very hard, except you can accept coredump ---- which is occurred in many other dynamic upstream modules, like this: https://github.com/GUI/nginx-upstream-dynamic-servers/issues/30. and the pull request in this issue was incomplete either, it will coredump in keep-alive enabled connections.
As a workaround, you can use LAST-MODIFIED or ETAG http header to tell the module the serverlist are not refreshed, and the module then will bypass parse serverlist, and bypass memory allocation eventually.

Last-Modified header 我已经加上了，短期观察内存确实比较稳定了，
到今天3天左右的时候，现在内存占用开始涨了，两个机器分配的流量是一样的，机器配置也一样。
这段时间 serverlist 的返回值和 Last-Modified 没有任何变化。
图一：正常的

图2 ：包含 nginx-upstream-serverlist 的：

你中间做了什么变更么? serverlists有极频繁变化和大量增加? 能不能确认返回值是304? 只要是304, 就一定不会分配新内存.

你好，我想我已经解决了这个动态解析模块的memory crash 和 memory leak的问题，你可以尝试一下我的模块或者帮我检查一下吗？ 谢谢
https://github.com/zhaofeng0019/nginx-upstream-dynamic-resolve-servers

在原来的模块我也提了一个pr，专门解决了内存问题，你也可以看一下
谢谢
https://github.com/GUI/nginx-upstream-dynamic-servers/pull/33/

你好，我想我已经解决了这个动态解析模块的memory crash 和 memory leak的问题，你可以尝试一下我的模块或者帮我检查一下吗？ 谢谢
https://github.com/zhaofeng0019/nginx-upstream-dynamic-resolve-servers

@zhaofeng0019  This looks pretty cool. There are a couple of things going on here: using a pool queue, avoiding exiting the process (and initializing that queue on starting a new process) and using ngx_http_upstream_init_round_robin vs init (as well as requiring a mod to the main source.
Do all these things need to be done together or each of the them alone solves different issues?
The reason I ask is that i use another 3rd party lib (https://github.com/gnosek/nginx-upstream-fair) and I'm running into issues (not really memory growing fast since I use the LAST-MODIFIED/ETAG) where after a while, nginx just starts trying to make connections against the dummy server: 2020/08/31 07:36:29 [error] 29352#0: *10 connect() to <IP_ADDRESS>:80 failed (101: Network is unreachable) while connecting to upstream and I wonder if this has something to do with either the ngx_http_upstream_init_round_robin vs init thing or the exiting the process thing (seeing as this module is a bit diff from the nginx-upstream-dynamic-resolve-servers by replacing the servers inside of the upstream not using the resolver, but has some shared overlap when in concerns the changes you made).

cinquemb,  thank you for looking into my code.
mod to the main source is not necessary.
if you don't want to mod the main source ,
you can see my pr into the original project  https://github.com/GUI/nginx-upstream-dynamic-servers/pull/33/commits
and try it. it may helpful.
And about the  3rd party lib (https://github.com/gnosek/nginx-upstream-fair)
nowdays i'm busy, and maybe don't have time to check it out.
thanks again.

yeah i saw that pr @zhaofeng0019, the thing is that https://github.com/abadcafe/nginx-upstream-serverlist works differently than  https://github.com/GUI/nginx-upstream-dynamic-servers so its not a 1 to 1 map with this project.
but I can test out a couple of the changes you made ( https://github.com/GUI/nginx-upstream-dynamic-servers/pull/33/commits) by porting them to this module and see if they clear up some things im seeing.
thanks!


Expectation value

There will be an option to do expectation values of Hermatian operators (e.g energy) using the GPU?
It would be very useful.

A few minutes ago, I released QuPy v1!
You can calculate expectation values quickly using GPU now.
Please read the README as the usage has changed a little. https://github.com/ken-nakanishi/qupy#upgrade-qupy-from-v0-to-v1

Sorry, did you deleate the examples where they show how to calculate with the GPU?

I made it possible to use the same code on CPU and GPU.
Please update v1.1.0.

Im getting this error when I try to run with GPU:
if device >= 0:
TypeError: '>=' not supported between instances of 'str' and 'int'
In version 1.0 it worked fine for me.

Thank you for your report!
Could you try v1.1.1?

Now works fine!
If i dont set QUPY_GPU, all the program will be running on the CPU?
I have been trying a program where im using a variational quantum algorithm
(i miniminize an energy tunning some parameters of the circuit) and the program
runs faster on the CPU. Maybe since the minimization runs on the CPU (im using minimization
methods from scipy) the communication between GPU and CPU makes the program slower?
Thanks for your attention!

If i dont set QUPY_GPU, all the program will be running on the CPU?
Yes! If you don't set QUPY_GPU or you set QUPY_GPU=-1, all the program will be running on the CPU.

the communication between GPU and CPU makes the program slower?
Communication of variational quantum circuit parameters between CPU and GPU doesn't make so slower, I think.

Can i send you a python script that im using?
Im running a circuit with 8 qubits and using the program with CPU takes like 5 seconds and with GPU 50 seconds. It is the same script, i change only the QUPY_GPU to -1 (CPU) and to 0 for GPU.

OK. I'll check it!

I send you an email. Thanks for your attention!

Summary
The cause of the slowdown is in the importing part.
This is probably inevitable when using GPU.
# test01.py
import time
start = time.time()
from qupy import Qubits
print(time.time() - start)

$ export QUPY_GPU=-1
$ python test01.py
0.18606972694396973
$ export QUPY_GPU=0
$ python test01.py
3.443936586380005


[charts] Allow to configure a sleep command to let the main app stop properly

Please provide a description of this PR:
This command add a short sleep by default to the istio-proxy when the pod shutdowns.
It can be overwritten with the annotation sidecar.istio.io/preStopSleep on each pods.
This can be useful for apps that takes some time to shutdown and needs to handle last requests.

Hi @etifontaine. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.


Page needs updating New visuals - where do we turn on Drill through cross report

Page needs updating New visuals - where do we turn on Drill through cross report?
The Visuals pane no longer exists.
[Enter feedback here]

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

ID: 70cc0df0-14a7-079d-c32c-78fff8aef03f
Version Independent ID: ff23bd8e-3901-3010-af39-19fb69f2fa6c
Content: Use cross-report drillthrough in Power BI Desktop - Power BI
Content Source: powerbi-docs/create-reports/desktop-cross-report-drill-through.md
Service: powerbi
Sub-service: pbi-reports-dashboards
GitHub Login: @maggiesMSFT
Microsoft Alias: maggies

Hi @BobCreamer, can you provide a bit more detail? When you say the Visuals pane no longer exists, do you mean the Visualizations pane? I still see that pane, and I see a cross-report toggle. Is this what you were referring to? In any event, I am closing this issue now, but please feel free to reopen it if you are still having problems and can provide more detail. Thanks!


docs: ignore bin folder

Makes this go away :)

looks good to me :+1: merge away once tests pass ... which they should!

Good catch. :+1:

manually build & deployed docs :+1:


riak-debug should include dump of bucket-type information [JIRA: RIAK-1988]

We have a need to include the bucket-type information in riak-debug, for example, where diagnosing the case where both DVV and last_write_wins are enabled.
Back when buckets were the only mechanism, it was easy, just decode the ring-file and extract the custom bucket information from there.
But bucket-type information isn't stored in the ring-file, it now lives in a secondary location - '/cluster_meta', stored in DETS database files.
If we can't be bothered writing something to iterate the bucket-type stuff, and dump as text - we could just dump the contents of the /metadata directory then decode the DETS files on our side using an Erlang snippet.

Seconded. However we must consider the case where there a lot of bucket-types. How many is it practical to list (including configuration)? i.e. what's the overhead, does it bloat the size of debug-output?

Never good practice anyway to have too many bucket-types. In fact, if that causes problems the user is probably doing it wrong anyway.

FYI - just dug up this old gist ... very amateur ha ha  but enough info to write an Erlang script to dump out the bucket-type info.

So's it's been recorded, this week I started the process of updating riak-debug in a few ways. Gathering meaningful bucket (type) property data is high on the TODO list. I had CLISERV-32 assigned to myself, so I'd be happy to take this task if that would be appropriate. It may take me a while to produce any meaningful changes, though, as I'll be working on this between normal CSE activities.
[posted via JIRA by Drew Pirrone-Brusse]

This has been, at least partially, incorporated into #907. That PR adds a section that loops over Bucket Types listed with riak-admin bucket-types list and prints the configuration set for each Type.


Nami wallet "Signature not possible" issue

When submitting a transaction where a signature is only required for collateral the nami wallet warns "Signature not possible" and does not allow you to sign the tx.
Here is the raw bytes the popup offers
84a60081825820e8946ebf2989722355e3ad9d9b1cd5a377f85b71360a99f2a112285f3c978e350101818258390047fa7409f0f0ed730dfcb351c7cf1c9a1372c3679492dbe71fcbd924a6ee431ff271651eab61776379312912ebfbcedfec57cbb4784569d01a0095bc40021a0002da400b58204b93abc2eb88a22abbee57e370c6802dba654ade402d9d8b6be82d8ff2bb77e60d8182582092e08d5fbc36a923b9c524f362579fb9d6ab893f973ff7f0e99e4c2db1c2dd07000f00a40380068159017c590179010000332323232323232323232222232333222323232533300e3370e90000010991919191919299980a19b87480080084c8c8c94ccc05ccdc3a400800426464a66603266e1ccdc00088090008a4c2c6eb4c070008dd6980d8008b180e001180e0009baa3230193230193019001301a0013253330140011613253330150011301a00216301800133322233333015222533301900112250011533301a3002301e001132223002003301e001133003002301d00130180010032332301722533301a00114bd70099299980e1802000899aba00013003301f00213003301f002301f001301932301d301e001301c301b301d001003163758603000a6eb0c060010c06000458c064008c064004dd5180a980a00198099809800980a180980098098020a4c602600460260026ea8008dd68020018011bad0042323002233002002001230022330020020015573eae6888cc00c008c014c01800488cdd79ba73005002374e600a002ae895d0918011baa0015573caae753010102000104800581840000d87a80821926221a002a1eaef5f6

Here is the json of the unbalanced tx I logged:
raw.txt

https://github.com/berry-pool/nami/issues/757

Cross-posted: https://discord.com/channels/862607192926060544/868234677905940610/1042100024093446154

note that this rarely happens with non-broke human users as nami collects all funds at a single address - therefore there's usually the account utxo in the inputs.

@zmrocze it happens when you need to unlock ADA from the script. CTL does not select inputs other than collateral in this case, because they are not needed.


Select what groups that you actually want it turned on for

My whole house is set up for LIFX.
Turning it on changed the whole house which was not clear at all when I launched, which unintentionally annoyed my wife who was preparing dinner. ;)
could we please get the detection of lights and groups more clear cut - because it's not always appropriate for every LIFX.

Yes my app is pretty simple - triggers all the lights. You can send a PR for a light selection, it shouldn't be too hard.

+1 This would be awesome. Only thing missing from the app. Any progress with this?

@ackfool As I said I don't actively develop this, but I will accept PRs.

It seems there is one person who has worked on the app most recently and that's @johnwang16 https://github.com/johnwang16/MoodSync
Since he created a preferences menu, it seems the first step is already there for extending to group/bulb selection, if anyone is tempted to work on it.


bump CSS for duckplayer fixes

Please review the release process for BrowserServicesKit here.
Required:
Task/Issue URL:
iOS PR:
macOS PR:
What kind of version bump will this require?: Major/Minor/Patch
Optional:
Tech Design URL:
CC:
Description:

Steps to test this PR:
1.
1.

OS Testing:

[ ] iOS 14
[ ] iOS 15
[ ] iOS 16
[ ] macOS 10.15
[ ] macOS 11
[ ] macOS 12

Internal references:
Software Engineering Expectations
Technical Design Template

#759  👈
main

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

Join @shakyShane and the rest of your teammates on  Graphite


Grammar improvements

[x] Add support for arrays
[x] Improve naming of symbols to improve transformations (AST)
[x] Merge global variables and local variables declarations (there is no technical reason for them to be separated)
Differentiate left hand side from right hand side in assignments

[ ] Remove assignment &&= and ||=

Fixed in #7


this.get() urls need to be preceded with a "/" when this.namespace is not being used

When this.namespace is not set in config.js you have to define the url used for this.get() with a "/" preceding the values (i.e. this.get('/api/resource')) but not for calls to this.put(), this.post(), or this.del().
If you set this.namespace then all of these function "out of the box" without any errors about incorrect urls.

Hm that's annoying. A default namespace of / should take care of this?

I can't reproduce this issue. I posted an example here. I'm going to close this, but if you're still experiencing this problem, please reopen with an example (feel free to fork my example linked above!)


feat: deploy charon rustdoc on Github Pages

close https://github.com/AeneasVerif/charon/issues/445
If the deployment is successful[^1], the default site https://AeneasVerif.github.io/charon will be 404 since there is no index.html under target/doc/, so the entry point should be
https://AeneasVerif.github.io/charon/charon
[^1]: maybe Github Pages source should be set to Github Actions to make it work

Thank you! :) Today is a public holiday in France, I'll have a look on Monday

No problem!

Looks perfect, let's merge and see if it works!

It worked! https://aeneasverif.github.io/charon/charon_lib/index.html


ts-loader, webpack and webpack-cli not loading

Hi,
I am using VS 2017 version 15.9.2 and Node.js v10.14.0. I refer your steps from below URL
https://docs.microsoft.com/en-us/visualstudio/javascript/tutorial-nodejs-with-react-and-jsx?view=vs-2017
But when I tried to add ts-loader, webpack and webpack-cli from install missing package its not installed.
Please let me know how can I install it.
I also attached screenshot for the same.

Thanks in advance..

It may be that the versions specified in package.json are out of date. This has probably been fixed in an update (i.e., the versions of those npm packages updated in package.json). But if not, you can right-click the npm node, choose Install package, and install each npm package separately.


Lost Zenith calculation at input lat/lon nodes

Lost this somewhere with the new raytracing modularity

@jlmaurer this has been addressed, no?

Yes, this was fixed in #40 .


Unable to connect to on-prem HipChat with XMPP disabled

By default, in the latest versions of on-prem HipChat, XMPP is disabled.  Unfortunately, the ability to turn on XMPP is something that Atlassian has stated will be removed altogether in the next version.  This basically means that simply turning on XMPP is not an option.
While attempting to connect to the HipChat server, I receive a repetitive list of the following messages:
[Fri Jan 05 2018 17:29:34 GMT-0500 (EST)] INFO Connection went offline
[Fri Jan 05 2018 17:29:34 GMT-0500 (EST)] DEBUG Disconnecting here
The messages do stop after about 15 seconds, and Hubot fails to respond to anything other than a break command.
Just for completion purposes, here's the output when executing the bot:
bin/hubot -a hipchat
up to date in 1.968s
[Fri Jan 05 2018 17:35:12 GMT-0500 (EST)] DEBUG Loading adapter hipchat
[Fri Jan 05 2018 17:35:12 GMT-0500 (EST)] DEBUG HipChat adapter options: {"jid":"1_89@chat.btf.hipchat.com","password":"","token":"","rooms":"@conf.btf.hipchat.com","rooms_blacklist":"","rooms_join_public":true,"host":"","bosh":"https:///http-bind","autojoin":true,"xmppDomain":"conf.btf.hipchat.com","reconnect":true}
[Fri Jan 05 2018 17:35:12 GMT-0500 (EST)] INFO Connecting HipChat adapter...
Environment file:
###HIPCHAT####
export<EMAIL_ADDRESS>export HUBOT_HIPCHAT_PASSWORD=********
export HUBOT_HIPCHAT_HOST=*************************
export HUBOT_LOG_LEVEL=debug
export HUBOT_HIPCHAT_XMPP_DOMAIN=conf.btf.hipchat.com
export HUBOT_HIPCHAT_BOSH_URL=https://*************************/http-bind
export HUBOT_HIPCHAT_RECONNECT=false
HUBOT_HIPCHAT_JOIN_PUBLIC_ROOMS=true
HUBOT_HIPCHAT_JOIN_ROOMS_ON_INVITE=true
<EMAIL_ADDRESS>###HIPCHAT####
While I have seen a few others having password problems, I did verify that the password for the user in question is indeed known and working.  Any ideas on how to resolve this issue?

hitting the same issue..

hitting the same issue here as well..

I believe this to be a side effect of https://confluence.atlassian.com/hipchatkb/xmpp-bosh-clients-not-working-in-hipchat-datacenter-946019722.html. The workaround mentioned there might help unblock hubot users until that issue is fixed.

This is what you want:
hipchat network --enable-xmpp-ports
Run this as the admin user from the hipchat on-prem appliance.


Bugfix: Include missing return value for matching struct

This addresses #1121
The corresponding data structure in cdproto was updated and broke the dependent function call in chromedp/query.go.

Thank you! Please update go.mod too.

Sorry for the force-push. Squashed the go.mod update into a single commit.

The force-push is preferred. I should mentioned that go.sum should be updated too.

Added go.sum via force-push.


Debug log level is not working as expected

The problem
The mapping between Home Assistant and Cloudflared log levels, as currently defined in the cloudflared-config.sh script, seems incorrect to me. The current mapping prevents the use of Cloudflared debug level, which can be used to log and display the request URL, method, protocol, content length, as well as all request and response headers (see doc : tunnel logs). I think this is just a typo, and the fix is as simple as changing the mapping for trace and debug levels as follows:
# Map Home Assistant log levels to Cloudflared
if bashio::config.exists 'log_level' ; then
    case $(bashio::config 'log_level') in
        "trace") log="debug";;
        "debug") log="debug";;
        "info") log="info";;
        "notice") log="info";;
        "warning") log="warn";;
        "error") log="error";;
        "fatal") log="fatal";;
    esac
else
    log="info"
fi

What version of Cloudflared has the issue?
4.2.2
What was the last working version of Cloudflared?
No response
What type of installation are you running?
Home Assistant OS
Add-on YAML Configuration
external_hostname: xxxxxx
additional_hosts: []
log_level: debug

Anything in the logs that might be useful for us?
-----------------------------------------------------------
 Add-on: Cloudflared
 Use a Cloudflare Tunnel to remotely connect to Home Assistant without opening any ports
-----------------------------------------------------------
 Add-on version: 4.2.2
 You are running the latest version of this add-on.
 System: Home Assistant OS 10.4  (aarch64 / raspberrypi3-64)
 Home Assistant Core: 2023.8.1
 Home Assistant Supervisor: 2023.07.1
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
Log level is set to DEBUG
[12:15:40] DEBUG: Cloudflared log level set to "info"
...

Steps to reproduce the issue

set the log level to DEBUG in the configuraton tab

Additional information
No response

We had a discussion about this some time ago. We had put the focus on analyzing errors from an add-on perspective, not necessarily on verbose output from Cloudflared.
For the "debug" log output, I'd like to leave that at the current logic (to be able to further analyze add-on specific problems in a reasonable way). But maybe we could switch on the Cloudflared debug mode for "trace" severity.

Sorry I didn't find that thread. Now I see the logic behind this. Anyway, if I may say so, I think it's more correct to have another option to control the Cloudflared logs, so we can have the best of both worlds. For example, in my use case, I'm only interested in the addon's error logs, but I need the Cloudflared debug logs to check the traffic going through the tunnel, which is an important feature in my opinion. You could set this additional option to fatal as default, and even hide it in the configuration tab, so that everything is left as it is now. Otherwise, if you think it's not worth it, we can give the trace/debug mapping a shot, but I feel it's a bit of a stretch.

My time is a little bit tight at the moment, but if you would like to, feel free to create a PR for the solution that you prefer.

Sadly I am short on time too and also managed to use Cloudflare logs for debugging purposes so my interest in this issue has faded at this time. Feel free to close it if it's not worth your time. Anyway thanks for your work.