test_smart_open: close gzip obj after writing

Motivation
fixes test_smart_open unit tests when run under python 3.12.
https://hydra.nixos.org/build/257823750
log
=========================== short test summary info ============================
FAILED smart_open/tests/test_smart_open.py::SmartOpenHttpTest::test_http_gz - EOFError: Compressed file ended before the end-of-stream marker was reached
FAILED smart_open/tests/test_smart_open.py::SmartOpenHttpTest::test_http_gz_query - EOFError: Compressed file ended before the end-of-stream marker was reached
FAILED smart_open/tests/test_smart_open.py::test_s3_gzip_compress_sanity - EOFError: Compressed file ended before the end-of-stream marker was reached
FAILED smart_open/tests/test_smart_open.py::test_s3_read_explicit[s3://bucket/gzipped-.gz] - EOFError: Compressed file ended before the end-of-stream marker was reached
FAILED smart_open/tests/test_smart_open.py::test_s3_write_explicit[.gz-\x1f\x8b\x08\x087'\x93`\x02\xffkey\x00] - assert b"\x1f\x8b\x0...3\x00\x00\x00" == b"\x1f\x8b\x0...02\xffkey\x00"
FAILED smart_open/tests/test_smart_open.py::test_s3_write_implicit[s3://bucket/key.gz-.gz-\x1f\x8b\x08\x087'\x93`\x02\xffkey\x00] - assert b"\x1f\x8b\x0...3\x00\x00\x00" == b"\x1f\x8b\x0...02\xffkey\x00"
FAILED smart_open/tests/test_smart_open.py::test_s3_disable_compression[s3://bucket/key.gz-.gz-\x1f\x8b\x08\x087'\x93`\x02\xffkey\x00] - assert b"\x1f\x8b\x0...3\x00\x00\x00" == b"\x1f\x8b\x0...02\xffkey\x00"
= 7 failed, 372 passed, 4 skipped, 4 deselected, 4 xfailed, 2 xpassed, 2412 warnings in 93.89s (0:01:33) =

does it make sense to add 3.12 to the github test matrix?

@ddelange Yes, can you do that in a separate PR?

Thank you @annaleeleaves


address rustdoc warnings

Codecov Report

Merging #131 (6817aa4) into master (a70a323) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #131   +/-   ##
=======================================
  Coverage   70.29%   70.29%
=======================================
  Files          88       88
  Lines        8047     8047
=======================================
  Hits         5657     5657
  Misses       2390     2390

Continue to review full report at Codecov.

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


Fake dev KYC provider

like devsms and devemail services, so we don't rely on an actual provider if we implement related features

Not really all that important for the immediate release, but we will need it eventually

KYC has been moved to TF app.


Cleanup

Codecov Report
Patch coverage is 100.00% of modified lines.
:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.

Files Changed
Coverage

src/DistanceTransforms.jl
ø

src/maurer.jl
ø

src/utils.jl
ø

src/felzenszwalb.jl
100.00%

:loudspeaker: Thoughts on this report? Let us know!.


S3 loader not working in AWS EC2 environment

Hello everyone, I'm facing this error when I try to run llama index download_loader function but I 'm getting this error running on AWS Linux with Python 3.8. With some research I found that this problem is often related to python trying to open a folder as a file.
Note: this error is happening just calling S3Reader function from download_loader.
--->  S3Reader = download_loader("S3Reader")  <--- just that line to reproduce this error.
Someone could help me with this? thks

Maybe just adding 'r' to this temporary folder path resolves..
file: llama-hub/loader_hub/s3/base.py  lines 73 and 82

I think this simple fix could be the solution. Can anyone check this pls? Thks
https://stackoverflow.com/questions/13207450/permissionerror-errno-13-in-python
https://github.com/emptycrown/llama-hub/blob/main/loader_hub/s3/base.py

UPDATE
I cloned the repo and tried to use the S3Loader directly in  my app. Still failing and after some tests I thinking that the problem is most likely in the SimpleDirectoryReader file.
In the error below, the orange line shows the local file witch references the SimpleDirectoryReader file from llama_index  marked in purple.

It appears an issue related to your Instance permissions rather than the Loader itself.
Closing due to inactivity, feel free to open again if needed


bug(Sidenav): Sidenav not displayed on production build

Reproduction
This issue occurs only on production build, on dev build the sidenav is displayed correctly. It happens both if using ng build --prod and hosting files on a static server or running ng serve --prod  directly.
I have created a git repo for reproduction at https://github.com/GCSDC/sidenav-issue
Steps to reproduce (after cloning repo and npm install):

Run ng serve --prod
Open app on browser
Click the 'Toggle' button to toggle sidenav

Expected Behavior
Sidenav contents should be displayed correctly, as it happens on a dev build (using ng build or ng serve):

Actual Behavior
Sidenav contents are not displayed:

Environment

Angular: dependencies below
CDK/Material: dependencies below
Browser(s): Chrome Version 86.0.4240.198 (Official Build) (x86_64) / Safari Version 14.0 (156<IP_ADDRESS>.9, 15610)
Operating System (e.g. Windows, macOS, Ubuntu): macOS Catalina 10.15.7

"dependencies": {
    "@angular/animations": "~11.0.1",
    "@angular/cdk": "^11.0.0",
    "@angular/common": "~11.0.1",
    "@angular/compiler": "~11.0.1",
    "@angular/core": "~11.0.1",
    "@angular/forms": "~11.0.1",
    "@angular/material": "^11.0.0",
    "@angular/platform-browser": "~11.0.1",
    "@angular/platform-browser-dynamic": "~11.0.1",
    "@angular/router": "~11.0.1",
    "rxjs": "~6.6.0",
    "tslib": "^2.0.0",
    "zone.js": "~0.10.2"
  },
  "devDependencies": {
    "@angular-devkit/build-angular": "~0.1100.2",
    "@angular/cli": "~11.0.2",
    "@angular/compiler-cli": "~11.0.1",
    "@types/jasmine": "~3.6.0",
    "@types/node": "^12.11.1",
    "codelyzer": "^6.0.0",
    "jasmine-core": "~3.6.0",
    "jasmine-spec-reporter": "~5.0.0",
    "karma": "~5.1.0",
    "karma-chrome-launcher": "~3.1.0",
    "karma-coverage": "~2.0.3",
    "karma-jasmine": "~4.0.0",
    "karma-jasmine-html-reporter": "^1.5.0",
    "protractor": "~7.0.0",
    "ts-node": "~8.3.0",
    "tslint": "~6.1.0",
    "typescript": "~4.0.2"
  }

I'm not completely sure why it happens, but the problem is that the style override here is turned into opacity: 1% in production mode which makes the sidenav invisible.  If I had to guess, it could mean that something weird is going on with the CSS minifier, but that's just speculation. What's the context behind changing the opacity?

@crisbeto thanks for your help. I added opacity to get kind of a transparency effect, but I was not aware it was causing this issue. I removed it and the sidenav is working fine. Should this issue be close then?

This could be something to be fixed in the CLI team since changing the opacity is a totally valid use case.


custom fields in connection dialog

About You:
Name: Chris Clark
Company: Actian
Your question:
Is it possible to add custom fields to connection dialogs? I can't see anything about this in https://tableau.github.io/connector-plugin-sdk/docs/ui - e.g. a new field called "custom_field". Supporting string entry as well as drop downs would be very useful.
Right now I'm handling this by adding extra options to the database name and using a special character as a separator which is not ideal.

Hi Chris,
At the moment, we do not have support for custom fields. For now, we do have an example where we rename the Service field and re-label it here: https://github.com/tableau/connector-plugin-sdk/tree/master/samples/components/dialogs/new_text_field
With the 2020.1 release of Tableau, there will be support for an additional 3 custom text fields.
We are also working on a more modular connection dialog that supports an arbitrary number of fields for a future release.

@clach04
With the connection dialog v2 we now enable creating custom fields making them required and optional as required . The documentation for that is available here : https://tableau.github.io/connector-plugin-sdk/docs/mcd . Does this fix the issue ?


Hide arbitrary extension

I have a similar case as described in #30, however I have a multi user solution.
I now have the doorbell visible plus every user that has an extension,
in my setup it's unsupported to call anyone other than doorbell.
If it would be possible to set extension visibility per extension it would greatly simplify the experience for the users.
Thanks!

Hi @gfduszynski,
When I got some time I will add a option to hide a extension.


Does not serve static files from public

Steps that reproduce the problem
I have the following configuration:
# config/trinidad.yml
address: localhost
port: 3000
environment: production
jruby_min_runtimes: 1
jruby_max_runtimes: 2
rackup: config.ru

I don't have a config/web.xml file.
I start the server with the command:
# in my Rails.root
> jruby -S trinidad

The server starts just fine.
The problem
When I open localhost:3000 the server serves the pages, but does not serve the static assets like javascripts, css's, images etc.
What should happen instead
The server should serve the static assets from public.
Additional information
The params sent to the context are the following
# name value
jruby.min.runtimes 1
jruby.max.runtimes 2
jruby.initial.runtimes 1
public.root /public
jruby.compat.version 1.8.7
rackup.path config.ru
rack.env production

Using:

Windows 7
JRuby 1.6.3
Trinidad 1.2.3
JRuby-Rack  1.0.9
Rails 3

The link is 404'ing. the correct link is https://github.com/jruby/jruby-rack/issues/20


Homebrew install issues with M3 arm64 architecture

Before Proceeding, please acknowledge:

[x] I have consulted the Troubleshooting guide.
[x] I have searched Issues and Discussions in this repo.
[x] Feature requests should be initiated as Discussions. This is a bug report.

Describe the bug
Not sure if best to create an issue here or at Homebrew.
The first attempt failed with Reinstalling 1 dependent with broken linkage from source, the second attempt installed an executable but it appears to be missing some apache-arrow dependencies.
$ brew install harlequin
==> Downloading https://ghcr.io/v2/homebrew/core/harlequin/manifests/1.25.2
############################################################################################################################################################## 100.0%
==> Fetching dependencies for harlequin: aws-sdk-cpp, re2, grpc, snappy, thrift, utf8proc, apache-arrow and<EMAIL_ADDRESS>...
==> Fetching harlequin
==> Downloading https://ghcr.io/v2/homebrew/core/harlequin/blobs/sha256:431c1d2d62756ffe35844622de0752cd921442607dc4053dbeeb3df4cb48c05d
############################################################################################################################################################## 100.0%
==> Installing dependencies for harlequin: aws-sdk-cpp, re2, grpc, snappy, thrift, utf8proc, apache-arrow and<EMAIL_ADDRESS>...
==> Installing harlequin
==> Pouring harlequin--1.25.2.arm64_sonoma.bottle.tar.gz
🍺  /opt/homebrew/Cellar/harlequin/1.25.2: 3,361 files, 101.8MB
==> Running `brew cleanup harlequin`...
Disable this behaviour by setting HOMEBREW_NO_INSTALL_CLEANUP.
Hide these hints with HOMEBREW_NO_ENV_HINTS (see `man brew`).
==> No outdated dependents to upgrade!
==> Checking for dependents of upgraded formulae...
Disable this behaviour by setting HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK.
Hide these hints with HOMEBREW_NO_ENV_HINTS (see `man brew`).
==> Reinstalling 1 dependent with broken linkage from source:
harlequin

$ harlequin
-bash: harlequin: command not found

$ brew install harlequin
==> Downloading https://ghcr.io/v2/homebrew/core/harlequin/manifests/1.25.2
Already downloaded: /Users/xxx/Library/Caches/Homebrew/downloads/3494fa1508f5ec620002e3a359fadb666cc8cdda625530d26b972800d6816dcb--harlequin-1.25.2.bottle_manifest.json
==> Fetching harlequin
==> Downloading https://ghcr.io/v2/homebrew/core/harlequin/blobs/sha256:431c1d2d62756ffe35844622de0752cd921442607dc4053dbeeb3df4cb48c05d
Already downloaded: /Users/xxx/Library/Caches/Homebrew/downloads/a1b7b4348ac005485d0455895e9e61d16485b110bc0903e583e9fb93134a2044--harlequin--1.25.2.arm64_sonoma.bottle.tar.gz
==> Pouring harlequin--1.25.2.arm64_sonoma.bottle.tar.gz
🍺  /opt/homebrew/Cellar/harlequin/1.25.2: 3,361 files, 101.8MB
==> Running `brew cleanup harlequin`...
Disable this behaviour by setting HOMEBREW_NO_INSTALL_CLEANUP.
Hide these hints with HOMEBREW_NO_ENV_HINTS (see `man brew`).

$ harlequin
Traceback (most recent call last):
  File "/opt/homebrew/bin/harlequin", line 5, in <module>
    from harlequin.cli import harlequin
  File "/opt/homebrew/Cellar/harlequin/1.25.2/libexec/lib/python3.11/site-packages/harlequin/__init__.py", line 1, in <module>
    from harlequin.adapter import HarlequinAdapter, HarlequinConnection, HarlequinCursor
  File "/opt/homebrew/Cellar/harlequin/1.25.2/libexec/lib/python3.11/site-packages/harlequin/adapter.py", line 7, in <module>
    from textual_fastdatatable.backend import AutoBackendType
  File "/opt/homebrew/Cellar/harlequin/1.25.2/libexec/lib/python3.11/site-packages/textual_fastdatatable/__init__.py", line 1, in <module>
    from textual_fastdatatable.backend import (
  File "/opt/homebrew/Cellar/harlequin/1.25.2/libexec/lib/python3.11/site-packages/textual_fastdatatable/backend.py", line 17, in <module>
    import pyarrow as pa
  File "/opt/homebrew/Cellar/harlequin/1.25.2/libexec/lib/python3.11/site-packages/pyarrow/__init__.py", line 65, in <module>
    import pyarrow.lib as _lib
ImportError: dlopen(/opt/homebrew/Cellar/harlequin/1.25.2/libexec/lib/python3.11/site-packages/pyarrow/lib.cpython-311-darwin.so, 0x0002): Library not loaded: /opt/homebrew/opt/apache-arrow/lib/libarrow_dataset.1800.dylib
  Referenced from: <F0CDA121-6C5D-3E63-99AF-3720A44F7F8E> /opt/homebrew/Cellar/harlequin/1.25.2/libexec/lib/python3.11/site-packages/pyarrow/lib.cpython-311-darwin.so
  Reason: tried: '/opt/homebrew/opt/apache-arrow/lib/libarrow_dataset.1800.dylib' (no such file), '/System/Volumes/Preboot/Cryptexes/OS/opt/homebrew/opt/apache-arrow/lib/libarrow_dataset.1800.dylib' (no such file), '/opt/homebrew/opt/apache-arrow/lib/libarrow_dataset.1800.dylib' (no such file), '/opt/homebrew/Cellar/apache-arrow/18.1.0/lib/libarrow_dataset.1800.dylib' (no such file), '/System/Volumes/Preboot/Cryptexes/OS/opt/homebrew/Cellar/apache-arrow/18.1.0/lib/libarrow_dataset.1800.dylib' (no such file), '/opt/homebrew/Cellar/apache-arrow/18.1.0/lib/libarrow_dataset.1800.dylib' (no such file)

To Reproduce
Steps to reproduce the behavior.
Expected behavior
A clear and concise description of what you expected to happen.
Actual behavior
A clear and concise description of what happened; please include screenshots or videos of Harlequin if possible.
Contributing
Are you interested in contributing a fix?

[ ] Yes
[x] Maybe
[ ] No

Additional context
Please provide as much as you can, but don't waste your time if it's definitely not relevant or you don't know.
What is the output of harlequin --version?
What database adapter are you using with Harlequin? (Default is duckdb)
What other options are you using when invoking Harlequin? (If you are using a profile, please add relevant items from your profile here).
Can you tell us more about your system?
$ uname -a
Darwin xxx.domain 23.6.0 Darwin Kernel Version 23.6.0: Wed Jul 31 20:50:54 PDT 2024; root:xnu-10<IP_ADDRESS>0.5~1/RELEASE_ARM64_T8122 arm64

How did you install Harlequin?

[ ] pipx
[ ] conda/mamba
[ ] pip (global install)
[ ] pip + venv/virtualenv or pipenv
[ ] Poetry
[ ] uv/Rye
[x] other:  Homebrew

I didn't know there was a homebrew formula for Harlequin and I don't maintain it.

Apparently it's new as of yesterday: https://github.com/Homebrew/homebrew-core/pull/198108

I recommend opening an issue in Homebrew and tagging @mfinelli

Thanks, will do!

I suspect this is because harlequin was bottled with apache-arrow 18.0.0, but 18.1.0 was released but the harlequin wasn't rebuilt and rebottled against the new version. Does it work if you brew install --build-from-source?

Does it work if you brew install --build-from-source?

I think that this was fixed in https://github.com/Homebrew/homebrew-core/commit/4364f921e3411951fda2e535868f2095d8c56d6b

Thank you!

Yes, I can confirm it works now.  Thank you @mfinelli @tconbeer!
$ brew uninstall harlequin
$ brew update
$ brew install harlequin
...
==> Installing harlequin
==> Pouring harlequin--1.25.2_1.arm64_sonoma.bottle.tar.gz
🍺  /opt/homebrew/Cellar/harlequin/1.25.2_1: 3,361 files, 101.9MB


pull request for e2e test at 01/09/2017 16:45:11

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


{AzureStorage} fix the typo for the source blob size

fixes Azure/azure-sdk-for-net#35139
This PR has fix for the typo for the source blob size.
The Maximum blob size for the source blob is 256 mebibytes (MiB) and not 256 MB. Refer: https://learn.microsoft.com/en-us/dotnet/api/azure.storage.blobs.specialized.blobbaseclient.synccopyfromuriasync?view=azure-dotnet
Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

API change check
API changes are not detected in this pull request.

There's no changes needed. The existing documentation is correct.
Our REST docs say
"The size of the source blob can be up to a maximum length of 256 mebibytes (MiB)."

https://learn.microsoft.com/en-us/rest/api/storageservices/put-blob-from-url?tabs=azure-ad
Please follow up with the customer and correct their understanding of the API. Thanks.

Ah I see your point, I got them backwards.

We should be good to merge. The pipeline failures are unrelated to your changes. Let me rerun them again just to see if they will run green, or else we can just override it

@amnguye Since all the checks are passed, could you please merge it once you get a chance ?


Enrich the CRD printcolumn

/kind feature
Describe the solution you'd like
[A clear and concise description of what you want to happen.]
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

ODLM CRs already have Phase
NAMESPACE              NAME                                         AGE   PHASE        CREATED AT
common-services-ford   common-service                               22m   Running      2021-01-04T23:19:30Z
common-services-ford   ibm-commonui-request                         20m   Installing   2021-01-04T23:21:30Z
common-services-ford   ibm-iam-request                              20m   Installing   2021-01-04T23:21:21Z
common-services-ford   ibm-metering-request                         20m   Running      2021-01-04T23:21:30Z
common-services-ford   ibm-mongodb-request                          20m   Running      2021-01-04T23:21:20Z
common-services-ford   management-ingress                           20m   Running      2021-01-04T23:21:27Z
common-services-ford   monitoring-exporters-operator-request        20m   Running      2021-01-04T23:21:22Z
common-services-ford   monitoring-grafana-operator-request          20m   Running      2021-01-04T23:21:23Z
common-services-ford   monitoring-prometheus-ext-operator-request   20m   Running      2021-01-04T23:21:23Z

ODLM CRs already have Phase
NAMESPACE              NAME                                         AGE   PHASE        CREATED AT
common-services-ford   common-service                               22m   Running      2021-01-04T23:19:30Z
common-services-ford   ibm-commonui-request                         20m   Installing   2021-01-04T23:21:30Z
common-services-ford   ibm-iam-request                              20m   Installing   2021-01-04T23:21:21Z
common-services-ford   ibm-metering-request                         20m   Running      2021-01-04T23:21:30Z
common-services-ford   ibm-mongodb-request                          20m   Running      2021-01-04T23:21:20Z
common-services-ford   management-ingress                           20m   Running      2021-01-04T23:21:27Z
common-services-ford   monitoring-exporters-operator-request        20m   Running      2021-01-04T23:21:22Z
common-services-ford   monitoring-grafana-operator-request          20m   Running      2021-01-04T23:21:23Z
common-services-ford   monitoring-prometheus-ext-operator-request   20m   Running      2021-01-04T23:21:23Z

ODLM CRs already have Phase
NAMESPACE              NAME                                         AGE   PHASE        CREATED AT
common-services-ford   common-service                               22m   Running      2021-01-04T23:19:30Z
common-services-ford   ibm-commonui-request                         20m   Installing   2021-01-04T23:21:30Z
common-services-ford   ibm-iam-request                              20m   Installing   2021-01-04T23:21:21Z
common-services-ford   ibm-metering-request                         20m   Running      2021-01-04T23:21:30Z
common-services-ford   ibm-mongodb-request                          20m   Running      2021-01-04T23:21:20Z
common-services-ford   management-ingress                           20m   Running      2021-01-04T23:21:27Z
common-services-ford   monitoring-exporters-operator-request        20m   Running      2021-01-04T23:21:22Z
common-services-ford   monitoring-grafana-operator-request          20m   Running      2021-01-04T23:21:23Z
common-services-ford   monitoring-prometheus-ext-operator-request   20m   Running      2021-01-04T23:21:23Z

ODLM CRs already have Phase
NAMESPACE              NAME                                         AGE   PHASE        CREATED AT
common-services-ford   common-service                               22m   Running      2021-01-04T23:19:30Z
common-services-ford   ibm-commonui-request                         20m   Installing   2021-01-04T23:21:30Z
common-services-ford   ibm-iam-request                              20m   Installing   2021-01-04T23:21:21Z
common-services-ford   ibm-metering-request                         20m   Running      2021-01-04T23:21:30Z
common-services-ford   ibm-mongodb-request                          20m   Running      2021-01-04T23:21:20Z
common-services-ford   management-ingress                           20m   Running      2021-01-04T23:21:27Z
common-services-ford   monitoring-exporters-operator-request        20m   Running      2021-01-04T23:21:22Z
common-services-ford   monitoring-grafana-operator-request          20m   Running      2021-01-04T23:21:23Z
common-services-ford   monitoring-prometheus-ext-operator-request   20m   Running      2021-01-04T23:21:23Z


The plug-in messed up my comment color

I have a user settings:
"editor.tokenColorCustomizations": {
"comments": "#24c347"
},
But after installing the plug-in, this life failed to work. The pale color of comments now is not ideal for my eyes. Can someone do something?

The problem is, I have these sitting in the setting.json, after I uninstall the plug in, my settings doesn't seem to go back into effect.

I am having the same problem with my custom comments color. I feel like it should use/restore whatever color you have set in your settings.json or at the very least remove whatever restriction is causing vscode to ignore the color set.

@martianmartian @BillGato, about the uninstall process, it would indeed be great if the process could be reverted, but unfortunately, VSCode does not provide any hooks for it. That is why there is a remark in the README: https://github.com/estruyf/vscode-hide-comments#removing-the-extension
The suggestion of keeping the previous color, is a good one.


Fix document generation job.

Fixes #3928 .

Doc gen job fails because shinx version installed doesnt support ast.parse(annotation, type_comments=True) ; Since the job pulls from main, where this fix isnt there it fails.


Added chirp mass constraint to prior constraint function

@EthanMarx is this good for what you want, or should we also bump up the minimums on the masses?

This implements the ability to apply a chirp mass constraint, but not an actual chirp mass constraint, correct?

Check that you're looking at the latest commit - I forgot to add the actual Constraint the first time

Could you plot the resulting m1 / m2 distributions and also determine the maximum signal duration?
We could also just only bump up the minimum masses to 10 and in that case we'll know the max is ~ 1.7

Here's the mass distribution. The signal duration is just determined by chirp mass, right? A 10/10 merger has a chirp mass of ~8.7, so constraining chirp mass to > 10 should have a max signal duration of < 1.7 s

Yeah exactly. I was being lazy and didn't calculate, wanted to make sure the math was done haha.

Ha, excellent. For future reference, the explicit max signal duration with this constraint. should be about 1.3-1.4 seconds

Yeah, I don't have the full picture of what the issue was, but astropy was entering through bilby, so we constrained both to avoid conflicts.


Commend Issue

I have 70 saved accounts and Titan is only sending 55 accounts, ignoring the rest, and I can not identify the reason in the console

This ist most likely because of the Steam Rate Limit, could you please send all your logs in the logs directory as .zip? Please keep in mind that AccountManager log contains login username & password, so remove them before posting them publicly.

I'll send the log later
From what I saw, Titan started straight to the accounts with Steam Guard off, ignoring the accounts with Steam Guard. And yes, it's true in enabled=

For Steam Guard Accounts, you'll need to set to sentry to true in order for Titan to use the Steam Guard implementation. For Non-Steam Guard Accounts, sentry should be default on false.

I did the test again, and yes, the error appears:
Unable to logon to account: RateLimitExceeded: RateLimitExceeded
Did you have any suggestions to avoid the problem? If I put 70 accounts, he send about 50. If I put 50, he sends some 30 commends. Thanks in advance

Try to commend with ~25 accounts, wait 30 minutes, do it again with ~25 accounts and so on. I can't fix the Steam Rate Limit, I'm sorry.

User hasn't replied in 7 days, closing this issue for now. Please reopen if needed.


feat(#minor): Open interest and collateralIN/out

added open interest
clarified collateralIn/out at positional level
added collateralin/out counters

updated @jaimehgb


Create a Staging CI/CD Pipeline via Argo Workflows

Create a Staging CI/CD pipeline via Argo Workflows that allows the developer to manually trigger the pipeline after creating a pull request (PR). The pipeline will run unit tests and integration tests via GitHub Actions. Once those tests pass, the application will be deployed to a staging environment, where business acceptance (BA) tests will be executed. If all tests pass, the workflow state will be marked as COMPLETED. Developer should also have the ability to re-run individual test steps or cancel the workflow if necessary.

The pipeline should be manually triggered by the developer after creating a PR.
Unit and integration tests will run via GitHub Actions.
The application will be deployed to the staging environment, where BA tests will run.
If all tests pass, the pipeline moves to the COMPLETED state.
Developers should be able to re-run failed test steps individually.
Developers should be able to cancel the pipeline at any point.
If the pipeline is canceled or fails, it should not return to the initial state but allow the developer to continue re-running or canceling specific steps.

Consider creating a PR Policy Github Action which ensures the PR can not be merged until all required steps passed. This pipeline is for staging and at the end of this pipeline, only production pipeline will be available to run and merging will happen in that pipeline.
Here is the example state diagram of the pipeline:

@startuml
title "Staging Deployment CI/CD Pipeline via Argo Workflows State Diagram"

' Define states
state IDLE : System is idle, waiting for actions
state WORKFLOW_PENDING_START : PR created, waiting for workflow start
state WORKFLOW_STARTING : Argo Workflows starting workflow
state PR_POLICY_CHECKING : Argo Workflows checking PR policy
state PR_POLICY_FAILED : PR policy check failed
state PR_POLICY_PASSED : PR policy check passed
state UNIT_TESTS_RUNNING : GitHub Actions running unit tests (triggered by Argo Workflows)
state UNIT_TESTS_FAILED : Unit tests failed
state INTEGRATION_TESTS_RUNNING : GitHub Actions running integration tests (triggered by Argo Workflows)
state INTEGRATION_TESTS_FAILED : Integration tests failed
state TESTS_PASSED : All tests passed
state IMAGE_PUBLISHING : GitHub Actions publishing Docker image
state DEPLOYMENT_PENDING : Argo CD detecting new image
state DEPLOYMENT_IN_PROGRESS : Argo CD deploying new version
state DEPLOYMENT_SUCCESSFUL : Deployment completed successfully
state BA_TESTS_RUNNING : Argo Workflows running BA tests
state BA_TESTS_FAILED : BA tests failed
state BA_TESTS_PASSED : BA tests passed
state COMPLETED: PR staging deployment is completed
state WORKFLOW_CANCELLED : Workflow cancelled

' Define the flow
[*] --> IDLE
IDLE --> WORKFLOW_PENDING_START : Developer creates a new PR
WORKFLOW_PENDING_START --> WORKFLOW_STARTING : Developer starts workflow with environment name input
WORKFLOW_STARTING --> PR_POLICY_CHECKING : Argo Workflows triggers PR policy check
PR_POLICY_CHECKING --> PR_POLICY_FAILED : PR policy failed
PR_POLICY_FAILED --> WORKFLOW_PENDING_START : Developer resolves issues and retries workflow
PR_POLICY_CHECKING --> PR_POLICY_PASSED : PR policy passed
PR_POLICY_PASSED --> UNIT_TESTS_RUNNING : Argo Workflows triggers GitHub Actions to run unit tests
UNIT_TESTS_RUNNING --> UNIT_TESTS_FAILED : Unit tests failed
UNIT_TESTS_FAILED --> UNIT_TESTS_RUNNING : Developer retries unit tests
UNIT_TESTS_FAILED --> WORKFLOW_CANCELLED : Developer cancels the workflow
UNIT_TESTS_RUNNING --> INTEGRATION_TESTS_RUNNING : Unit tests pass, trigger integration tests
INTEGRATION_TESTS_RUNNING --> INTEGRATION_TESTS_FAILED : Integration tests failed
INTEGRATION_TESTS_FAILED --> INTEGRATION_TESTS_RUNNING : Developer retries integration tests
INTEGRATION_TESTS_FAILED --> WORKFLOW_CANCELLED : Developer cancels the workflow
INTEGRATION_TESTS_RUNNING --> TESTS_PASSED : Integration tests pass
TESTS_PASSED --> IMAGE_PUBLISHING : Argo Workflows triggers GitHub Actions to publish Docker image
IMAGE_PUBLISHING --> DEPLOYMENT_PENDING : Argo CD detects new image
DEPLOYMENT_PENDING --> DEPLOYMENT_IN_PROGRESS : Argo CD starts deployment
DEPLOYMENT_IN_PROGRESS --> DEPLOYMENT_SUCCESSFUL : Deployment complete
DEPLOYMENT_SUCCESSFUL --> BA_TESTS_RUNNING : Argo Workflows triggers BA tests
BA_TESTS_RUNNING --> BA_TESTS_FAILED : BA tests failed
BA_TESTS_FAILED --> BA_TESTS_RUNNING : Developer retries BA tests
BA_TESTS_FAILED --> WORKFLOW_CANCELLED : Developer cancels the workflow
BA_TESTS_RUNNING --> BA_TESTS_PASSED : BA tests pass
BA_TESTS_PASSED --> COMPLETED: Workflow completes successfully

@enduml

While working on this pipeline, I realized that synchronizing Argo Workflows with GitHub Workflows is unnecessarily complicated. I also discovered Arc Runners, which are much easier to set up and use. It seems there's no need to use Argo Workflows after all. I’ll complete this task using GitHub Actions and Arc Runners instead.


chore: add support for multiple import solutions of JavaScript assets

This PR improve the way the sprockets file foundation.js is handled and make JavaScript assets importable by two differents ways according to the needs:

By the main Foundation file foundation.js (or foundation.min.js)
By all or some plugins foundation.[plugin].js (or foundation.[plugin].min.js)

Changes:

Make foundation.js a static asset and rename it to foundation.sprockets.js
As a precise import order must be kept, "foundation.js" sprocket file cannot be dynamically generated.
Add warning message on assets update to manually update foundation.sprockets.js
Move plugins files to "vendor/assets/js/plugins"
Add main Foundation distribution file foundation.js to assets
Add main and plugins minified files *.min.js to assets
See commits descriptions for more informations.

Others changes:

Import responsive menus in last in foundation.sprockets.js as they require others menus.

See https://github.com/zurb/foundation-rails/pull/257 (@patricklindsay)

@patricklindsay Could you review this ?

Poke @DanielRuf too.

Note: tests were already failing before this PR.

Note: tests were already failing before this PR.

Should be easy to solve. It's many years since I worked with RoR for the last time.
Not sure if I can properly test this.

@DanielRuf See https://github.com/zurb/foundation-rails/issues/259

My bad just seen this but looks good!


Inconsistent behavior in example_dem.py

From example_dem.py:
def update(self):

    with wp.ScopedTimer("simulate", active=True):

        if (self.use_graph):

            with wp.ScopedTimer("grid build", active=False):
                self.grid.build(self.x, self.grid_cell_size)

            with wp.ScopedTimer("solve", active=False):
                wp.capture_launch(self.graph)
                wp.synchronize()

        else:
            for s in range(self.sim_substeps):

                with wp.ScopedTimer("grid build", active=False):
                    self.grid.build(self.x, self.point_radius)

                with wp.ScopedTimer("forces", active=False):
                    wp.launch(kernel=apply_forces, dim=len(self.x), inputs=[self.grid.id, self.x, self.v, self.f, self.point_radius, self.k_contact, self.k_damp, self.k_friction, self.k_mu], device=self.device)
                    wp.launch(kernel=integrate, dim=len(self.x), inputs=[self.x, self.v, self.f, (0.0, -9.8, 0.0), self.sim_dt, self.inv_mass], device=self.device)

            wp.synchronize()

The captured kernels are defined as:
if (self.use_graph):

    wp.capture_begin()

    for s in range(self.sim_substeps):

        with wp.ScopedTimer("forces", active=False):
            wp.launch(kernel=apply_forces, dim=len(self.x), inputs=[self.grid.id, self.x, self.v, self.f, self.point_radius, self.k_contact, self.k_damp, self.k_friction, self.k_mu], device=self.device)
            wp.launch(kernel=integrate, dim=len(self.x), inputs=[self.x, self.v, self.f, (0.0, -9.8, 0.0), self.sim_dt, self.inv_mass], device=self.device)

    self.graph = wp.capture_end()

If use_graph==True, grid.build() is called once, then the kernels are replayed 64 times.  If use_graph==False, grid.build() is called every time the kernels are called.  I think this is a bug.

Thanks, fixed in 94da260d5cf0e3c7511d55d2c9df35cc5fd07b2d


Error appears and I do not figure it out. How to solve it ,please?Honestly.

###############
File "intensio_obfuscator.py", line 299, in
main()
File "intensio_obfuscator.py", line 132, in main
verboseArg=args.GetArgsValue().verbose
File "C:\Users\10698\Desktop\Intensio-Obfuscator-master\Intensio-Obfuscator-master\intensio\core\obfuscation\intensio_delete.py", line 116, in Comments
for eachLine in inputFile:
File "C:\Users\10698\AppData\Local\Programs\Python\Python37\lib\fileinput.py", line 252, in next
line = self._readline()
File "C:\Users\10698\AppData\Local\Programs\Python\Python37\lib\fileinput.py", line 366, in _readline
return self._readline()
UnicodeDecodeError: 'gbk' codec can't decode byte 0xaa in position 519: illegal multibyte sequence
###########

UnicodeDecodeError: 'gbk' codec can't decode byte 0xaa in position 519: illegal multibyte sequence

I'm getting this error too. The reason is that my code has non-ASCII strings. I wrote all my docstrings and code in English and the problem solved.

I get this error, too! Then I add "encoding=utf8" to "open(file, "r") as readFile", and add "inputFile = str(inputFile)" after "with fileinput.input(file, inplace=True) as inputFile:". It seems I solved this problem. But the console shows "Obfuscation [ replace string to hex ] feature no asked !". I need you help.@Hnfull

The OS is windows10, and the sys.getdefaultencoding() says utf-8

It seems the module named "fileinput" doesn't support specify encoding when inplace mode

I have the exactly same problem and I solve it by adjusting the source code a bit.
Look at the exception trace like yours
File "C:\Users\10698\Desktop\Intensio-Obfuscator-master\Intensio-Obfuscator-master\intensio\core\obfuscation\intensio_delete.py", line 116, in Comments

then find that file and modify all occurances like
with fileinput.input(file, inplace=True ... )

change it to
with fileinput.input(file, openhook=fileinput.hook_encoded("utf8"))
#modify utf8 as your requirement

open(file, ...)

change it to
open(file, encoding='utt8', ...)
# change utf8 as your requiremnt

I think it is better that hook encoding from .py file first line, for example, when my file indicate that
# -*- codinng: utf8 -*-

Intensio would like to open that file as it is.
Good luck.

I have the exactly same problem and I solve it by adjusting the source code a bit.
Look at the exception trace like yours
File "C:\Users\10698\Desktop\Intensio-Obfuscator-master\Intensio-Obfuscator-master\intensio\core\obfuscation\intensio_delete.py", line 116, in Comments

then find that file and modify all occurances like
with fileinput.input(file, inplace=True ... )

change it to
with fileinput.input(file, openhook=fileinput.hook_encoded("utf8"))
#modify utf8 as your requirement

open(file, ...)

change it to
open(file, encoding='utt8', ...)
# change utf8 as your requiremnt

I think it is better that hook encoding from .py file first line, for example, when my file indicate that
# -*- codinng: utf8 -*-

Intensio would like to open that file as it is.
Good luck.

The error is caused due to none-ascii characters in project source file like comments or filename.


Test fails if there is .swp file in directory

So not sure if this is a hotsos issue or a vim peculiarity but here it is.
Vim (and maybe other editors) create a .swp file for each window (displaying file) in the file's directory.
Hotsos lists the contents of the test dirs to gather the paths with the tests and excludes only the files
that end in .disabled.
As a result, if you run the test suite and you happen to have a test file open in vim, hotsos will consider .myrandomtestfile.yaml.swp as a file with tests and will fail the test with the following :
Captured traceback:
~~~~~~~~~~~~~~~~~~~
    ImportError: Failed to import test module: tests.unit.test_lxd
Traceback (most recent call last):
  File "/usr/lib/python3.10/unittest/loader.py", line 436, in _find_test_path
    module = self._get_module_from_name(name)
  File "/usr/lib/python3.10/unittest/loader.py", line 377, in _get_module_from_name
    __import__(name)
  File "/home/ubuntu/hotsos/tests/unit/test_lxd.py", line 40, in <module>
    class TestLXDScenarios(LXDTestsBase):
  File "/home/ubuntu/hotsos/tests/unit/utils.py", line 49, in _inner
    tg = TemplatedTestGenerator(path, testdef)
  File "/home/ubuntu/hotsos/tests/unit/utils.py", line 180, in __init__
    self.testdef = yaml.safe_load(open(test_def_path)) or {}
  File "/home/ubuntu/hotsos/.tox/py3/lib/python3.10/site-packages/yaml/__init__.py", line 125, in safe_load
    return load(stream, SafeLoader)
  File "/home/ubuntu/hotsos/.tox/py3/lib/python3.10/site-packages/yaml/__init__.py", line 79, in load
    loader = Loader(stream)
  File "/home/ubuntu/hotsos/.tox/py3/lib/python3.10/site-packages/yaml/loader.py", line 34, in __init__
    Reader.__init__(self, stream)
  File "/home/ubuntu/hotsos/.tox/py3/lib/python3.10/site-packages/yaml/reader.py", line 85, in __init__
    self.determine_encoding()
  File "/home/ubuntu/hotsos/.tox/py3/lib/python3.10/site-packages/yaml/reader.py", line 124, in determine_encoding
    self.update_raw()
  File "/home/ubuntu/hotsos/.tox/py3/lib/python3.10/site-packages/yaml/reader.py", line 178, in update_raw
    data = self.stream.read(size)
  File "/usr/lib/python3.10/codecs.py", line 322, in decode
    (result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xf0 in position 17: invalid continuation byte

This can be fixed with something like this or maybe by including for testing only  the files that end in .yaml.
Anyway, if you think this is a vim problem feel free to close the issue.

should be fixed by https://github.com/canonical/hotsos/commit/f7be62a0ee4e55c13b61548dd4895695e1bc5d59


Use horizontal lines consistently and purposefully across peripheral pages

Since in the interim this cleans up some of the spacing issues. Horizontal lines have been applied on denser information pages, with multiple sections, such as:

Expected Activities x4
Privacy
Terms and conditions

This change was made in Contentful directly.


Segmentation Fault after `assert failure: false. Details: attempted to add shared target SdsApi <NAME_OF_SECRET> to initialized init manager Server

I've emailed<EMAIL_ADDRESS>and was told to raise the issue here.
Please see the Segmentation Fault section at the later part of this email for the stack trace.
Please also see: https://github.com/envoyproxy/go-control-plane/issues/581.
Issues
I've noticed a couple of things.

When we implement SecretDiscoveryServiceServer "github.com/envoyproxy/go-control-plane/envoy/service/secret/v3" sometimes the StreamSecrets does not get called back at all.
when StreamSecrets is called, it is called endlessly with a new stream each time, see the log output further down in this message.

When StreamSecrets is not called, obviously, our dynamically supplied secrets are titled dynamic_warming_secrets instead of dynamic_active_secrets.
Code
Our code is public so, here are the definitions of:

StreamSecrets: https://github.com/kubeshop/kusk-gateway/blob/mbana-oauth-issue-401-sds/internal/envoy/sds/sds.go#L72
Where we register the SecretDiscoveryServiceServer: https://github.com/kubeshop/kusk-gateway/blob/mbana-oauth-issue-401-sds/internal/envoy/manager/envoy_config_manager.go#L183
Configuring the cache etc: https://github.com/kubeshop/kusk-gateway/blob/mbana-oauth-issue-401-sds/internal/envoy/manager/envoy_config_manager.go#L56.

Log of StreamSecrets being called multiple times (the stream=&{0xc000f19c70} is different each time):
2022-08-12T09:19:30Z | sds.go:74: SecretDiscoveryServiceServer.StreamSecrets: exiting method
2022-08-12T09:19:30Z | sds.go:92:
2022-08-12T09:19:30Z | sds.go:93: SecretDiscoveryServiceServer.StreamSecrets: calling stream.Recv - stream=&{0xc000f19380}, len(s.ClientSecrets)=2
2022-08-12T09:19:30Z | sds.go:116: SecretDiscoveryServiceServer.StreamSecrets: request.TypeUrl=type.googleapis.com/envoy.extensions.transport_sockets.tls.v3.Secret, len(s.ClientSecrets)=2
2022-08-12T09:19:30Z | sds.go:153: SecretDiscoveryServiceServer.StreamSecrets: stream.Send(response) sent - responses=[<*>version_info:"2022-08-12T09:19:30Z"  resources:{[type.googleapis.com/envoy.extensions.transport_sockets.tls.v3.Secret]:{name:"hmac_secret"  generic_secret:{secret:{inline_bytes:"f9eckuGEcUNxAqKT0uK8OyM2Se01ukVLPHsiSoTh2X8="}}}}  type_url:"type.googleapis.com/envoy.extensions.transport_sockets.tls.v3.Secret" <*>version_info:"2022-08-12T09:19:30Z"  resources:{[type.googleapis.com/envoy.extensions.transport_sockets.tls.v3.Secret]:{name:"client_secret"  generic_secret:{secret:{inline_string:"Z6MX7NreJumWLmf6unsQ5uiEUrTBxfNtqG9Vy5Kjktnvfj-_fRCBO9EU1mL1YzAJ"}}}}  type_url:"type.googleapis.com/envoy.extensions.transport_sockets.tls.v3.Secret"]
2022-08-12T09:19:30Z | sds.go:154:
2022-08-12T09:19:30Z | sds.go:74: SecretDiscoveryServiceServer.StreamSecrets: exiting method
2022-08-12T09:19:30Z | sds.go:92:
2022-08-12T09:19:30Z | sds.go:93: SecretDiscoveryServiceServer.StreamSecrets: calling stream.Recv - stream=&{0xc000f19c70}, len(s.ClientSecrets)=2
2022-08-12T09:19:30Z | sds.go:116: SecretDiscoveryServiceServer.StreamSecrets: request.TypeUrl=type.googleapis.com/envoy.extensions.transport_sockets.tls.v3.Secret, len(s.ClientSecrets)=2
2022-08-12T09:19:30Z | sds.go:153: SecretDiscoveryServiceServer.StreamSecrets: stream.Send(response) sent - responses=[<*>version_info:"2022-08-12T09:19:30Z"  resources:{[type.googleapis.com/envoy.extensions.transport_sockets.tls.v3.Secret]:{name:"client_secret"  generic_secret:{secret:{inline_string:"Z6MX7NreJumWLmf6unsQ5uiEUrTBxfNtqG9Vy5Kjktnvfj-_fRCBO9EU1mL1YzAJ"}}}}  type_url:"type.googleapis.com/envoy.extensions.transport_sockets.tls.v3.Secret" <*>version_info:"2022-08-12T09:19:30Z"  resources:{[type.googleapis.com/envoy.extensions.transport_sockets.tls.v3.Secret]:{name:"hmac_secret"  generic_secret:{secret:{inline_bytes:"f9eckuGEcUNxAqKT0uK8OyM2Se01ukVLPHsiSoTh2X8="}}}}  type_url:"type.googleapis.com/envoy.extensions.transport_sockets.tls.v3.Secret"]

What we expect when we look at /config_dump of when StreamSecrets is being called:
{
   "@type": "type.googleapis.com/envoy.admin.v3.SecretsConfigDump",
   "dynamic_active_secrets": [
    {
     "name": "client_secret",
     "version_info": "2022-08-12T09:22:18Z",
     "last_updated": "2022-08-12T09:22:18.140Z",
     "secret": {
      "@type": "type.googleapis.com/envoy.extensions.transport_sockets.tls.v3.Secret",
      "name": "client_secret",
      "generic_secret": {
       "secret": {
        "inline_string": "[redacted]"
       }
      }
     }
    },
    {
     "name": "hmac_secret",
     "version_info": "2022-08-12T09:22:18Z",
     "last_updated": "2022-08-12T09:22:18.386Z",
     "secret": {
      "@type": "type.googleapis.com/envoy.extensions.transport_sockets.tls.v3.Secret",
      "name": "hmac_secret",
      "generic_secret": {
       "secret": {
        "inline_bytes": "W3JlZGFjdGVkXQ=="
       }
      }
     }
    }
   ]
  }

Don't worry about the exposed the secrets, they'll be removed soon.
Logs or Debug Information
In addition to that, here are dumps taken from the admin endpoint (/config_dump) of when it is working and when it is not working, i.e., when the StreamSecrets gRPC method is not invoked on the go-control-plane and when it is. Notice how the secrets are called dynamic_warming_secrets.

config_dump-broken.json: https://gist.github.com/mbana/61305292ddb9fd83e260a0125893f6ca
logs-broken.log: https://gist.github.com/mbana/a4636cf5e96a035db618f7c37b8dc275
config_dump-working.json: https://gist.github.com/mbana/e9b7b29ed7c1be032aca867304d86d60
logs-working.log: https://gist.github.com/mbana/2881bc1873090d8d82649ba95625d789

If there's anything further I can do to help get to the cause of this issue, please let me know.

Envoy Compiled From 7af7608b022c5e3ae2ad110b4d94aa7506a643d7
Edit: I went a step further and compiled Envoy from source and made a Docker image of it:
Dockerfile
FROM docker.io/ubuntu:22.04

COPY envoy-static /usr/local/bin/envoy
COPY envoy-static /usr/bin/envoy

ENTRYPOINT ["/usr/local/bin/envoy"]

Build Steps
$ git remote -vv
origin	git@github.com:envoyproxy/envoy.git (fetch)
origin	git@github.com:envoyproxy/envoy.git (push)
$ git rev-parse HEAD
7af7608b022c5e3ae2ad110b4d94aa7506a643d7
$ bazel/setup_clang.sh
$ echo "build --config=clang" >> user.bazelrc
$ echo "build --copt=-fno-limit-debug-info" >> user.bazelrc
$ bazel build --jobs=32 -c fastbuild envoy
$ cp bazel-bin/source/exe/envoy-static .
$ docker build --tag ttl.sh/kubeshop/envoy:24h --file ./Dockerfile .
$ docker push ttl.sh/kubeshop/envoy:24h

The image is available at ttl.sh/kubeshop/envoy:24h (docker run --rm -it ttl.sh/kubeshop/envoy:24h). Note: This image is only available for ~24 hours from the time of editing this post (2022-08-12T13:47:31+00:00 UTC).
Segmentation Fault
I noticed that Envoy crashes:
[2022-08-12 13:35:16.253][7][critical][assert] [source/common/init/manager_impl.cc:36] assert failure: false. Details: attempted to add shared target SdsApi client_secret to initialized init manager Server
[2022-08-12 13:35:16.253][7][critical][backtrace] [./source/server/backtrace.h:104] Caught Aborted, suspect faulting address 0x7
[2022-08-12 13:35:16.253][7][critical][backtrace] [./source/server/backtrace.h:91] Backtrace (use tools/stack_decode.py to get line numbers):
[2022-08-12 13:35:16.253][7][critical][backtrace] [./source/server/backtrace.h:92] Envoy version: 7af7608b022c5e3ae2ad110b4d94aa7506a643d7/1.24.0-dev/Modified/DEBUG/BoringSSL
[2022-08-12 13:35:16.272][7][critical][backtrace] [./source/server/backtrace.h:96] #0: Envoy::SignalAction::sigHandler() [0x5579a06c8b28]
[2022-08-12 13:35:16.273][7][critical][backtrace] [./source/server/backtrace.h:98] #1: [0x7f086bc6a520]
AsyncClient 0x550cbfc8ec00, stream_id_:<PHONE_NUMBER>0745907833
&stream_info_:
  StreamInfoImpl 0x550cbfc8edc8, protocol_: 1, response_code_: null, response_code_details_: via_upstream, attempt_count_: 1, health_check_request_: 0, route_name_:   upstream_info_:
    UpstreamInfoImpl 0x550cbfc81570, upstream_connection_id_: 0
Http2::ConnectionImpl 0x550cbf8d7dc8, max_headers_kb_: 60, max_headers_count_: 100, per_stream_buffer_limit_: 268435456, allow_metadata_: 0, stream_error_on_invalid_http_messaging_: 0, is_outbound_flood_monitored_control_frame_: 0, dispatching_: 1, raised_goaway_: 0, pending_deferred_reset_streams_.size(): 0
&protocol_constraints_:
  ProtocolConstraints 0x550cbf8d7e48, outbound_frames_: 0, max_outbound_frames_: 10000, outbound_control_frames_: 0, max_outbound_control_frames_: 1000, consecutive_inbound_frames_with_empty_payload_: 0, max_consecutive_inbound_frames_with_empty_payload_: 1, opened_streams_: 1, inbound_priority_frames_: 0, max_inbound_priority_frames_per_stream_: 100, inbound_window_update_frames_: 4, outbound_data_frames_: 4, max_inbound_window_update_frames_per_data_frame_sent_: 10
Number of active streams: 1, current_stream_id_: 1 Dumping current stream:
stream:
  ConnectionImpl::StreamImpl 0x550cbf50bd40, stream_id_: 1, unconsumed_bytes_: 0, read_disable_count_: 0, local_end_stream_: 0, local_end_stream_sent_: 0, remote_end_stream_: 0, data_deferred_: 1, received_noninformational_headers_: 1, pending_receive_buffer_high_watermark_called_: 0, pending_send_buffer_high_watermark_called_: 0, reset_due_to_messaging_error_: 0, cookies_:   pending_trailers_to_encode_:   null
  absl::get<ResponseHeaderMapPtr>(headers_or_trailers_):   null
Dumping corresponding downstream request for upstream stream 1:
  UpstreamRequest 0x550cbfdfcd80
[2022-08-12 13:35:16.273][7][critical][backtrace] [./source/server/backtrace.h:104] Caught Segmentation fault, suspect faulting address 0x0
[2022-08-12 13:35:16.273][7][critical][backtrace] [./source/server/backtrace.h:91] Backtrace (use tools/stack_decode.py to get line numbers):
[2022-08-12 13:35:16.273][7][critical][backtrace] [./source/server/backtrace.h:92] Envoy version: 7af7608b022c5e3ae2ad110b4d94aa7506a643d7/1.24.0-dev/Modified/DEBUG/BoringSSL
[2022-08-12 13:35:16.273][7][critical][backtrace] [./source/server/backtrace.h:96] #0: Envoy::SignalAction::sigHandler() [0x5579a06c8b28]
[2022-08-12 13:35:16.273][7][critical][backtrace] [./source/server/backtrace.h:98] #1: [0x7f086bc6a520]
[2022-08-12 13:35:16.292][7][critical][backtrace] [./source/server/backtrace.h:96] #2: Envoy::Http::ResponseDecoderWrapper::dumpState() [0x55799f4d23f8]
[2022-08-12 13:35:16.311][7][critical][backtrace] [./source/server/backtrace.h:96] #3: Envoy::Http::Http2::ClientConnectionImpl::dumpStreams() [0x55799fae8b21]
[2022-08-12 13:35:16.330][7][critical][backtrace] [./source/server/backtrace.h:96] #4: Envoy::Http::Http2::ConnectionImpl::dumpState() [0x55799fae850a]
[2022-08-12 13:35:16.348][7][critical][backtrace] [./source/server/backtrace.h:96] #5: Envoy::Event::DispatcherImpl::onFatalError() [0x5579a031cd35]
[2022-08-12 13:35:16.367][7][critical][backtrace] [./source/server/backtrace.h:96] #6: Envoy::FatalErrorHandler::callFatalErrorHandlers() [0x5579a06cf35a]
[2022-08-12 13:35:16.386][7][critical][backtrace] [./source/server/backtrace.h:96] #7: Envoy::SignalAction::sigHandler() [0x5579a06c8b8a]
[2022-08-12 13:35:16.386][7][critical][backtrace] [./source/server/backtrace.h:98] #8: [0x7f086bc6a520]
Our FatalActions triggered a fatal signal.
Segmentation fault (core dumped)

Can anyone see anything useful in this stack-trace? The assertion failing is particular interesting, but I don't know much about the Envoy code-base to tell if this is an issue or not:
[2022-08-12 13:35:16.253][7][critical][assert] [source/common/init/manager_impl.cc:36] assert failure: false. Details: attempted to add shared target SdsApi client_secret to initialized init manager Server

It's not clear where and when secrets are being used. Could you provide more info on that?
cc @adisuissa

It's not clear where and when secrets are being used. Could you provide more info on that? cc @adisuissa

Are you referring to how I create the secrets? If so, here is the part of the code where it's being done:

https://github.com/kubeshop/kusk-gateway/blob/mbana-oauth-issue-401-sds/internal/envoy/sds/sds.go#L198
https://github.com/kubeshop/kusk-gateway/blob/mbana-oauth-issue-401-sds/internal/envoy/sds/sds.go#L229
https://github.com/kubeshop/kusk-gateway/blob/mbana-oauth-issue-401-sds/internal/envoy/config/envoy_configuration.go#L220: Here a snapshot with the secrets is generated to include the secrets added from the above steps.

Also, if you look at the "broken" and "working" /config_dumps you will see that we've configured the envoy.filters.http.oauth2 filter that uses these secret to populate the token_secret (really it's a client_secret in OAuth2 terms, but anyway) and the hmac_secret fields:

config_dump-broken.json: https://gist.github.com/mbana/61305292ddb9fd83e260a0125893f6ca
config_dump-working.json: https://gist.github.com/mbana/e9b7b29ed7c1be032aca867304d86d60

To answer your question, if you search in the above files for client_secret, you'll find that's where they are "defined".
What would be ideal is if the envoy.filters.http.oauth2 filter provided an option to specify the secrets as an inline_string or inline_bytes but unfortunately it doesn't so one has to resort to writing an secret discovery server (SDS). We can't hold the secrets in a file because the envoy.filters.http.oauth2 filter we use needs to be dynamically defined by a user.
Hope that all makes sense, if not, please let me know.

https://github.com/envoyproxy/envoy/issues/22625 might be related, seems like secret subscription management in oauth2 filter is broken.

Hello, @kyessenov, hope you're well.

Is there an ETA for this?
Are there unittests in the code base that test out the SDS and ensures that it polls/streams for secrets? If so, where would should I look for those?

@kyessenov, hello, please keep this open until a fix arrives for it.
Many thanks.


Resolve inconsistency between VARCHAR and STRING

https://github.com/confluentinc/ksqldb-recipes/pull/131#discussion_r783591267
Looking for clarification on differentiation of VARCHAR vs STRING and when to use which.  I usually see VARCHAR in the context below, but STRING also works:
CREATE STREAM pages (
   page STRING, ....

We have recipes that reference both...

ksqlDB uses STRING as synonym to VARCHAR -- so semantically there is no difference.
VARCHAR is the standard SQL type, even if it usually need a "max size" parameter that ksqlDB does not implement. -- STRING is no standard SQL type (seems to be syntactic sugar -- but sure why ksqlDB added it).
To avoid confusing users, it might be good to just pick either one and use it exclusively in all tutorials.

To avoid confusing users, it might be good to just pick either one and use it exclusively in all tutorials.

@mjsax agree.  Which would be your recommendation, VARCHAR or STRING?

I would go with VARCHAR.

Closing and moving to https://github.com/confluentinc/kafka-tutorials/issues/1044


ManageIQ::Password raises exception on plaintext

Fix the fix_auth auth_model_spec after manageiq-password v1.1.0
Fixes https://app.travis-ci.com/github/ManageIQ/manageiq-cross_repo-tests/jobs/547146397#L1050-L1062
Failures:

  1) FixAuth::AuthModel#authentications #recrypt should not encrypt plaintext columns
     Failure/Error: subject.fix_passwords(plain, options)

     ManageIQ::Password::PasswordError:
       cannot decrypt plaintext string

     # ./tools/fix_auth/auth_model.rb:48:in `recrypt_password'
     # ./tools/fix_auth/auth_model.rb:37:in `recrypt'
     # ./tools/fix_auth/auth_model.rb:62:in `block in fix_passwords'
     # ./tools/fix_auth/auth_model.rb:60:in `each'
     # ./tools/fix_auth/auth_model.rb:60:in `fix_passwords'
     # ./spec/tools/fix_auth/auth_model_spec.rb:73:in `block (4 levels) in <top (required)>'

I'm not sure about this one - I think we want it to leave the column alone as per the discussion in https://github.com/ManageIQ/manageiq/pull/21178#pullrequestreview-637148954 .  So I think we leave this test as is and make it pass.  I'll take a look at it.


Initialize Lean project

This pull request initializes Lean4 formalization project. The focus of these initial commits is on establishing the project structure (which is still tentative) and introducing the minimal version of the calculus.
The following files were added:

Minimal directory

Сalculus.lean specifies representation of 𝜑-calculus terms in Lean and contains implementation of reductions to both weak head normal form and normal form
Еest.lean contains conversion of terms to String and evaluates reductions of objects

Extended directory, which is empty at the moment
lakefile.lean contains information dependencies and how to build a project
lake-manifest.json is auto-generated
lean-toolchain specifies version of lean4
PhiCalculus.lean is a build target

To-Do before merge:

[ ] get feedback on the project structure for improvements

PR-Codex overview
This PR focuses on adding the Minimal.Calculus module and implementing the Term and OptionalAttr types with their respective functions. It also includes a whnf function for weak head normal form evaluation and an nf function for normal form evaluation.
Detailed summary

Added Minimal.Calculus module
Implemented Attr, OptionalAttr, and Term types
Implemented functions mapObj, incLocatorsFrom, incLocators, substituteLocator, lookup, insert, whnf, and nf
Added ToString instances for OptionalAttr and Term
Updated README.md with installation instructions

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

Slightly fixed package format and filenames, added CI workflow to build and generate docs, with caching. Once this PR is merged, documentation should be submitted to gh-pages branch, at which point we should enable Pages for this repository.


[Bug]: Date warnings appear twice

What happened?
When switching to a new layer. If there is a date conflict, we show a warning and inform the user of the new selected date. For some reason, this warning appears twice. We should only display the warning once.

Which country / deployment are you running?
All
Add a screenshot (if relevant)
No response

@ericboucher - yes this is annoying and something that was fixed before but was reintroduced at some stage - I think with the new UX


[CI] Add PR labeler

PRs will be labeled with an automatic regexp-based labeler and a changed-files-based one.
The labeler_regexp.yml and labeler_files.yml files under the .github/labeler folder contain the mapping between labels and associated regular expressions and changed files.

If the PR's title and/or description match the regular expression, a label is added to the PR.
If the PR's changed files match the provided paths, a label is added to the PR.

@akashchi I worry this is a too simple solution. I'd expect something like checking if:

the notebook hasn't existed before - "new notebook"
the existing notebook changed - "improvement"
any of the readme files changed - "documentation"
gsoc in the title/description - "gsoc"

We have to check for real changes in most cases instead of titles/descriptions. I hope you can design the rules like these above.

See the comment above

I have added rules for labeling based on the changed files.


SDE not loading

Describe the bug
SDE not loading since new update equinox.

I literally burnt +5h today on this #275 here 😅

Zip archive is changed

sorry can't see, your issue.
It"s fix in 2 minutes, commit in progress

same as #275

thank you <3


feat: Display image in a graphics_card #1817

The PR fulfills these requirements: (check all the apply)

[x] It's submitted to the main branch.
[x] When resolving a specific issue, it's referenced in the PR's title (e.g. feat: Add a button #xxx, where "xxx" is the issue number).
[x] When resolving a specific issue, the PR description includes Closes #xxx, where "xxx" is the issue number.
[x] If changes were made to ui folder, unit tests (make test) still pass.
[x] New/updated tests are included

Closes #1817
As requested in the ticket, I have made changes so that a background image can be displayed in ui.graphics_card. I added 3 new props to graphics.tsx - path, image, and path. I modeled these after similar props in image.tsx.
  /**
   * The path or URL or data URL of the background image,
   * e.g. `/foo.png` or `http://example.com/foo.png` or `data:image/png;base64,???`.
   */
  path?: S
  /** Background image data, base64-encoded. */
  image?: S
  /**
   * The background image MIME subtype. One of `apng`, `bmp`, `gif`, `x-icon`, `jpeg`, `png`, `webp`.
   * Required only if `image` is set.
   */
  type?: S

I then defined a new backgroundImageSrc const if one of these new props is defined.
          backgroundImageSrc = path
            ? 'url('+path+')'
            : image ? `url(data:image/${type};base64,${image})`
            : undefined

In the JSX code, I added a parent div to wrap the existing div. This parent div is where the background image is rendered, if it exists. A new div was needed since the existing div is defined with a 15px offset from each side of the containing block, which would prevent a background image on the existing div from covering the entire area of the card. So I felt the best way to cover the entire card was to add a new parent div for the background. Let me know if you think there is a better approach.
          <div style={{ backgroundImage: `${backgroundImageSrc ? backgroundImageSrc : undefined}`,
                        backgroundSize: `${backgroundImageSrc ? 'cover' : undefined}`,
                      }}>

I then ran the make generate target to update the generated python and R code to reflect this new attribute in files, such as py/h2o_wave/h2o_wave/ui.py.
Locally, I modified the graphics_hilbert.py example to render a background image using a relative path to one of the out-of-box Wave images. Here is a screen shot of that:

I also created a new custom python example that renders a graphics_card without a background image and then 4 others that use the 3 variations of the path prop and another that uses the image and type props. Here is a screen shot of that:

I created a new unit test in graphics.test.tsx, where it passes dummy values and then checks that new parent div to make sure it has the background-image set properly. I remember before you said not to bother with visual unit tests, but I felt like something was needed here. If you disagree and think it should be removed, just let me know.
  it('Renders with background image', () => {
    const { queryByTestId } = render(<View {...graphicsBackgroundImageProps} />)
    expect(queryByTestId(name)).toBeInTheDocument()
    expect(queryByTestId(name)?.parentElement?.style.backgroundImage).toEqual('url(foobar.png)')
  })

I ran all the ui tests and confirmed they passed. Here is a screen shot for that:

I also ran the visual regression tool at tools/showcase. This was fine except for 1 mismatch found with wide_article_preview-0.png. I looked at the before and after images and they looked identical to me. I suspect this was just a false positive?
Let me know if you have any questions or would like me to make any changes. Thanks!

I looked at the before and after images and they looked identical to me. I suspect this was just a false positive?

Yes. The tool is very sensitive, which is fine.

@mturoci I think I've made all the changes you requested. I added a new Python example called graphics_background.py and rebuilt the docs. Here's a screen shot of that:

I also re-ran all the unit tests and they still pass:

Let me know if you have any questions or see something else I need to change. I'll jump on the changes in the Table Filter Count PR next. Thanks!


Tumbling window supports a one-to-one relationship i.e. only one pipeline can be triggered

The article states "Pipelines and triggers have a many-to-many relationship." This is contradicted further down where it talks about tumbling window triggers that it "Supports a one-to-one relationship. Only one pipeline can be triggered."
This exception should be added to the general statement.

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

ID: 3d564675-f719-57fc-a406-6aec51d26b29
Version Independent ID: 84124e8f-efad-274f-c2eb-40a04748296c
Content: Pipeline execution and triggers in Azure Data Factory
Content Source: articles/data-factory/concepts-pipeline-execution-triggers.md
Service: data-factory
GitHub Login: @djpmsft
Microsoft Alias: daperlov

@abdale :Thanks for the feedback and bringing this to our notice . At this time we are reviewing the feedback and will update the document as appropriate .


Get full sha for api repo in manifest file

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: utka
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

release/OWNERS [utka]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/lgtm

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: duderino, utka
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

release/OWNERS [utka]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/lgtm
/approve

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: duderino, icygalz, utka
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

release/OWNERS [utka]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Feature - Tooltip render method

Is your feature request related to a problem? Please describe.
At the last pivoting, users asked for a more complete report of the data. The team has created some visual representation of the required data. That visual representation has a lot of charts that may be confusing.
Describe the solution you'd like
According to Prototype, every chart must have a tooltip that is rendered aside from the graph title.
To avoid code duplication, we need a function that receives the tooltip message as parameter and inserts on the HTML document a :?: with the desired values.
Describe alternatives you've considered
Another way of showing the data may be considered since the Acceptance Criteria is satisfied.
Additional context
The prototype can be used as a visual guide.
Example:

Acceptance Criteria

[ ] Render a :question: icon wherever it is called
[ ] Render the help message when hovering
[ ] Follow the style purposed by the prototype and / or the GitHub visual identity.

We need the SVG of the question icon to proceed with what is asked in the issue.

Done!

We tried use the  for SVG.
But the tag  dont support SVG image

We were able to use the img tag to use IMG.
Function used:
chrome.extension.getURL ("../ images / questionMark.svg")
For this it was necessary to add the SVG image in the manifest:
"web_accessible_resources": [
"images / questionMark.svg"
]


Halo model for power spectrum calculation

This branch works to add a halo model calculation and refactor some of the code in ccl_massfunc as a result of this. This will allow a new method of power spectrum calculation.
I think one key thing prior to pushing to master will be to develop benchmarks of this for validation purposes.

I've tried to resolve all the conflicts, all the python tests pass, and only the tests/ccl_test_power_nu.c fails in check_ccl, with the following error:
TEST 60/65 power_nu_nl:model_3 [OK]
TEST 61/65 power_nu_nl:model_2 ERROR 1032: ccl_power.c: ccl_cosmology_compute_power_class(): Error computing CLASS power spectrum

Pull Request Test Coverage Report for Build 1651

20 of 24 (83.33%)  changed or added relevant lines in 4 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.5%) to 93.972%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pyccl/power.py
3
4
75.0%

pyccl/massfunction.py
4
7
57.14%

Totals

Change from base Build 1626:
-0.5%

Covered Lines:
530

Relevant Lines:
564

💛  - Coveralls

OK, something broke with commit 6279f4d -- it's causing a segfault on my system, and I'm getting mysterious Travis errors. What happened?

@alexander-mead  I have just pushed a tiny fix that should solves the problem you were having. Here is what was happening:
In ccl_massfunc.c, the  double nu_mass(ccl_cosmology *cosmo, double halomass, double a, int *status) function has been commented out, but it was still declared in ccl_massfunc.h. It is not a problem for the C executable and library, but SWIG creates a symbol, without and actual definition for it. So when _ccllib.so gets loaded by the python interpreter, it looks for this symbol and can't find it's definition, hence the following error message:
In [1]: import pyccl
---------------------------------------------------------------------------
ImportError                               Traceback (most recent call last)
~/repo/CCL/pyccl/ccllib.py in swig_import_helper()
     13         try:
---> 14             return importlib.import_module(mname)
     15         except ImportError:

/usr/lib/python3.6/importlib/__init__.py in import_module(name, package)
    125             level += 1
--> 126     return _bootstrap._gcd_import(name[level:], package, level)
    127

/usr/lib/python3.6/importlib/_bootstrap.py in _gcd_import(name, package, level)

/usr/lib/python3.6/importlib/_bootstrap.py in _find_and_load(name, import_)

/usr/lib/python3.6/importlib/_bootstrap.py in _find_and_load_unlocked(name, import_)

/usr/lib/python3.6/importlib/_bootstrap.py in _load_unlocked(spec)

/usr/lib/python3.6/importlib/_bootstrap.py in module_from_spec(spec)

/usr/lib/python3.6/importlib/_bootstrap_external.py in create_module(self, spec)

/usr/lib/python3.6/importlib/_bootstrap.py in _call_with_frames_removed(f, *args, **kwds)

ImportError: /home/francois/repo/CCL/pyccl/_ccllib.so: undefined symbol: nu_mass

During handling of the above exception, another exception occurred:

ModuleNotFoundError                       Traceback (most recent call last)
<ipython-input-1-7837a010f21e> in <module>()
----> 1 import pyccl

~/repo/CCL/pyccl/__init__.py in <module>()
     15     environ["CLASS_PARAM_DIR"] = path.dirname(path.abspath(__file__))
     16
---> 17 from pyccl import ccllib as lib
     18
     19 from pyccl import core, constants, background, power, massfunction, halomodel

~/repo/CCL/pyccl/ccllib.py in <module>()
     15         except ImportError:
     16             return importlib.import_module('_ccllib')
---> 17     _ccllib = swig_import_helper()
     18     del swig_import_helper
     19 elif _swig_python_version_info >= (2, 6, 0):

~/repo/CCL/pyccl/ccllib.py in swig_import_helper()
     14             return importlib.import_module(mname)
     15         except ImportError:
---> 16             return importlib.import_module('_ccllib')
     17     _ccllib = swig_import_helper()
     18     del swig_import_helper

/usr/lib/python3.6/importlib/__init__.py in import_module(name, package)
    124                 break
    125             level += 1
--> 126     return _bootstrap._gcd_import(name[level:], package, level)
    127
    128

ModuleNotFoundError: No module named '_ccllib'

It looks like it's not finding _ccllib, but the .so file is there, it's just because the import is crashing in the middle when it encounters the nu_mass symbol.
Long story short, I've commented out nu_mass() in ccl_massfunc.h and everything seems to be working for me. If that function is no longer needed, it should be completely removed from ccl_massfunc.h and ccl_massfunc.c

Also, I see that we have a test failing due to a precision issue:
TEST 58/65 halomod:model_2 [FAIL]
  ERR: /home/travis/build/LSSTDESC/CCL/tests/ccl_test_halomod.c:156  expected 1.388688e-01, got 1.390115e-01 (diff -1.427826e-04, tol 1.388688e-04)

@elisachisari suggests that this might be caused by the recent changes to the default set of physical constants.

Here is a concrete set of tasks that need to be addressed concerning this PR.

[ ] Address review by @philbull
[ ] Fix failure in CTEST, most likely due to the new physical constants adopted by CCL @damonge
[ ] Upload benchmark code that produces the benchmark to the relevant branch @damonge
[ ] Make a plot for the paper comparing to the benchmarks - add this in the paper and in the jupypter notebook #369.
[ ] Address comments in the paper itself: making sure notation is homogeneous with respect to HMF section, add implementation and validation details.

Benchmark plot is now in the notebook and in the paper.


imshow_node_grid gets a field error for 'landslide__mean_factor_of_safety' (landslide driver)

Create error by running the following:
imshow_node_grid(grid, 'landslide__mean_factor_of_safety', cmap='OrRd_r',
            `grid_units=('coordinates', 'coordinates'), vmax=5.,`

             `shrink=0.75, var_name='Factor of Safety',`

             `var_units='no units')`

This will return the following error:

FieldError: landslide__mean_factor_of_safety

Which basically means that landslide__mean_factor_of_safety is not a valid field for this method. I tried getting rid of the extra underscore and that did not help either.

@itaher1995 Please close and move to https://github.com/hydroshare/hydroshare-jupyterhub


The Stop/Start hint text in Service Detail Popup is not showing up

Version - Master with reskin UI
Steps:

Create a stack and add a service
Go to Stack detail page and select Graph view
Click on Service to bring up popup
Move mouse over the stop/start icon

Results:
The black hint text does not show up. Since it's on the left, you can see a little of the black > but the rest is cut off.

Expected:
Text should not be cut off

This seems ok with the current layout

Version - Master with latest reskin UI
Verified fixed


doc: finish the provider child up call documentation

The bulk of the documentation was there but it wasn't quite complete.
Fixes #15678

[x] documentation is added or updated
[ ] tests are added or updated

ping for review please

Merged to master.  Thanks for the reviews.


Migrate Logsearch to Credhub

Migrate Logsearch to Credhub
In order to get Logsearch credentials into Credhub, we need to import Logsearch's variables into Credhub.
Acceptance Criteria

[ ] Development Logsearch manifest should be identical to existing manifest, but with variables pulled from Credhub.
[ ] Staging Logsearch manifest should be identical to existing manifest, but with variables pulled from Credhub.
[ ] Production Logsearch manifest should be identical to existing manifest, but with variables pulled from Credhub.

Provided @bengerman13 finishes his log search work #961 then it makes sense to tackle this in the next sprint (19.10.30).

This still needs to get done - that being said I'm not sure if it would be a higher priority than Kubernetes, though (i.e. which should come first).

I would say that it's not a higher priority than the K8s work nor the Coalfire artifacts list.

Sure, but this and Coalfire's priorities are separate - I was musing about this work's priority in reference to the greater Credhub work, not comparing against other priorities.

duplicate of #1111


how to send the data to other app from first app and back to the data to first app.

use socket progrming

This sample has been deprecated/archived (check README for more information on newer samples related to this technology).
As recommended by GitHub, we are closing all issues and pull requests.


Menu is opening in wrong position on IOS if page is scrolled.

Version
2.6.3
Steps to reproduce

Scroll down the page on Safari on IOS
Bring up context menu by long pressing

Expected Behavior
Context menu should open at position of long click
Actual Behavior
Menu opens further down the page or off screen

I have noticed the same behavior in v2.8.0 under iOS with both Safari AND Chrome


Closes: #1

Updated validations.py python script.
Fixed the behavior of validate_user function in validations.py.
Fixes #<issue_number_goes_here>

It's a good idea to open an issue first for discussion.

[x] Tests pass
[x] Appropriate changes to README are included in PR

validation of pull request


Question: Is classification training on only one task different to normal Torch training?

Sorry if this is off-topic, I just did not know where else to ask this question.
I like the Snorkel Classification modules, as they are fairly intuitive to use, and make adding new tasks to an MTL model a cinch.
If I create an MTL model with only one task, will that model train in the same was as if I were to train it through vanilla PyTorch?
From the best of my understanding, I think that it would, but I was wondering if there would be any subtle peculiarities with the training regime of Snorkel's Classification modules.
The reason I would like to use the Snorkel MTL framework to do single task training is that I would later like to easily add additional tasks to training, and would not like to change the set-up too much.
Thanks

Hi @Peter-UCL, great question! First of all, we're glad you're enjoying the MultitaskClassifier model! Model architectures are not the focus of the Snorkel repo, but we found it so useful in our own prototyping to have a model with that much control that we decided to open source it as well.
Now to answer your question: yes, I believe an MTL model made in Snorkel with only one task will train the exact same a single-task model. There will only be one loss function, that loss will propagate through all the parameters it touches (in this case, all the model parameters), and training will occur as normal.

Tagging as Q&A for future reference and closing- thanks for the great question!


Remove android:allowBackup="true"

Allow apps using the library to select their own backup option without needing to override it.

Pull requests won't be merged into master

Also it's fixed in dev

It may be worth noting in the README that pull requests should be submitted against dev, and/or changing the default branch to dev

That's correct, I'll update the README, thank you


Patch request for 7.x from 8.x PhpRedisConnector

Laravel Version: #.#.# 7.22.4
PHP Version: 7.3.19
Database Driver & Version: Redis 6.0.9
phpredis Version 5.3.1

Description:
We are using Laravel with phpredis and a redis server that needs TLS1.2 and a verified CA and cert.
In vendor/laravel/framework/src/Illuminate/Redis/Connectors/PhpRedisConnector.php function establishConnection() in Laravel 8.x, you have:
if (version_compare(phpversion('redis'), '5.3.0', '>=')) {
if (! is_null($context = Arr::get($config, 'context'))) {
$parameters[] = $context;
}
}
But it was not patched into Laravel 7.x (at least not 7.22.4).  We are running 7.22.4 in production and phpredis is not passing the context ssl parameters from config/database.php to the redis extension (or openssl).  Would it be possible for you to patch Laravel 7.x?  Upgrading our environment to 8.x will take a significant effort in our FDA compliant environment.
Steps To Reproduce:
On a system running Laravel 7.x:
Create a self-signed certificate and extract the CA, key and cert files.
Update your redis settings in config/database to include these in the 'context' array.
For example:
'context' => [
'stream' => [
'allow_self_signed' => true,
'ciphers' => 'DEFAULT:!TLSv1.0:!TLSv1.1:!SSLv3',
'local_cert' => '/usr/local/certs/tls.crt',
'local_pk' => '/usr/local/certs/tls.key',
'cafile' => '/usr/local/certs/ca.pem'
],
]

Hey there,
Unfortunately we don't support this version anymore. Please check out our support policy on which versions we are currently supporting. Can you please try to upgrade to the latest version and see if your problem persists? We'll help you out and re-open this issue if so.
Thanks!

Hey there,
Unfortunately we don't support this version anymore. Please check out our support policy on which versions we are currently supporting. Can you please try to upgrade to the latest version and see if your problem persists? We'll help you out and re-open this issue if so.
Thanks!

It was fixed in 7.28.   Anyone running previous version should just update with composer.

It was fixed in 7.28.   Anyone running previous version should just update with composer.


Octopi.txt fix

Downloaded new version of octopi.txt, and modified REPLACEMENT_STRINGS to match the new file.

Alright nvm, tested in now on MAKE-009, and it works like a charm 😄


GPT4o

GPT-4o (“o” for “omni”) is openai's most advanced model. It is multimodal (accepting text or image inputs and outputting text), and it has the same high intelligence as GPT-4 Turbo but is much more efficient—it generates text 2x faster and is 50% cheaper. Additionally, GPT-4o has the best vision and performance across non-English languages of any of openai's models. GPT-4o is available in the OpenAI API to paying customers. https://platform.openai.com/docs/models/gpt-4o

Thanks! We are aware of this model and will add it to our leaderboard.

Once you have completed the evaluation, I would greatly appreciate it if you could notify me on this issue interface.


Are menus working ?

It does not open in my test, when clicking on button, this is how I have wired it up:
<Button id="demo" icon><Icon icon="more_vert" /></Button>
<Menu for="demo" bottom-right={ true } bottom-left={ false }>
  <Menu.Item>Foo</Menu.Item>
  <Menu.Item disabled={ true }>Bar</Menu.Item>
</Menu>

Hi @rsaccon - MDL's wiring for setting up button<->menu click events does not support dynamically rendered components.  In my own projects, I am using the following setup to toggle them:
function toggleMenu(e) {
  let menu = e.target.parentNode.querySelector('.mdl-menu');
  if (menu) menu.MaterialMenu.toggle();
  e.preventDefault();
}

In your example, this would be:
<Button icon onClick={toggleMenu}><Icon icon="more_vert" /></Button>
<Menu bottom-right>
  <Menu.Item>Foo</Menu.Item>
  <Menu.Item disabled>Bar</Menu.Item>
</Menu>

(side note:  and  do the same thing)

ok, thanks a lot, now it works halfway as expected. But I had to adapt the dom query:
let menu = e.target.parentNode.parentNode.querySelector('.mdl-menu');
unfortunately the alignment options seem to have no effect, and when I click anywhere outside the menu, it does not close (but toggling the button, off course works)

@rsaccon are you calling preventDefault() in a delegated even handler somewhere?  I'm using this exact technique in Nectarine and clicking outside the menu closes it: https://github.com/developit/nectarine/blob/master/src/components/post/comment.js#L39-L45

@developit thanks again, now clicking outside works as well, just alignment not yet, and I have them wired up as in nectarine, where it seems to work perfectly

I was having issues with alignment too.  Make sure you are setting position relative or absolute on the parent element in order for their offsets to work.
Closing but please keep me posted on the positioning, since I believe I ended up overriding it in Nectarine.

Ok, all fine now. Thanks a lot again. I use a wrapper, where I can optional set alignment class (without, it aligns left)

  <Button id="demo-menu-right"
    onClick={ toggleMenu }
    icon><Icon icon="more_vert" /></Button>
  <Menu for="demomenurigth">
    <Menu.Item>Foo</Menu.Item>
    <Menu.Item disabled>Bar</Menu.Item>
  </Menu>

and this is the css:
.menu-wrap {
	position: relative;
}

.menu-wrap.right .mdl-menu__container {
  right: 0;
}

Looks good. Only thing I'd mention is just to remember IDs are supposed to be document-unique, and since you're triggering the menu toggling programmatically you can drop both id and for. Cheers.


fix truncated license

copied the missing end of the MIT license from
https://opensource.org/licenses/MIT

Thanks I will integrate this once I merge the TypeScript branch.

👍 thanks!


Fixes #823 context attributes with nil raises error

https://github.com/getsentry/raven-ruby/issues/823

skipps context attributes with value nil

Needs a test but otherwise 👍

@joker-777 can you add a test?

Yes, I will add a test.Is on my todo-list.

@nateberkopec Added the requested test.


Update create-ilb-ase.md

Include comments on how to use hosts file when no DNS server configured in the VNET.

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

@EvanBasalik Thank you for your contribution. I apologize for the delay in getting back to you on this.  We have reviewed your addition, and while it may work, we do not want to add notes on how to modify a hosts file on a machine in the App Service Environment documentation. Please don't hesitate to reach out if you have any additional feedback in the future. #please-close

Not sure I understand why not. If a customer is using a VM in the same VNET to run Kudu, etc. and does not have a DNS server assigned to the VNET adding a hosts file to the client VM is the only way they can make Kudu work. Or am I missing something.
From: George Wallace<EMAIL_ADDRESS>Sent: Wednesday, October 23, 2019 11:49 PM
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: Evan Basalik<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] Update create-ilb-ase.md (#39720)
@EvanBasalikhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FEvanBasalik&data=02|01|Evan.Basalik%40microsoft.com|cc8461772de849f5a9fe08d758350bd7|72f988bf86f141af91ab2d7cd011db47|1|0|637074857164232356&sdata=VcpU11I0VUgTh8KWjZbROyCy3x04gL2gV%2FPw7H546sw%3D&reserved=0 Thank you for your contribution. I apologize for the delay in getting back to you on this. We have reviewed your addition, and while it may work, we do not want to add notes on how to modify a hosts file on a machine in the App Service Environment documentation. Please don't hesitate to reach out if you have any additional feedback in the future. #please-close
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fpull%2F39720%3Femail_source%3Dnotifications%26email_token%3DABCTFUNQZYWMAEB2IGMRNJ3QQELJFA5CNFSM4I3OOKLKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECDTBYQ%23issuecomment-545730786&data=02|01|Evan.Basalik%40microsoft.com|cc8461772de849f5a9fe08d758350bd7|72f988bf86f141af91ab2d7cd011db47|1|0|637074857164232356&sdata=Ep7nZYW5Ysy90dzeDO3ahMBS6%2B%2Ba4r1xQ5hq0FxcNKk%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FABCTFUM3VAX75KU74LEDCFTQQELJFANCNFSM4I3OOKLA&data=02|01|Evan.Basalik%40microsoft.com|cc8461772de849f5a9fe08d758350bd7|72f988bf86f141af91ab2d7cd011db47|1|0|637074857164242308&sdata=muGgkIuvZkCigIrgqzhGcBACM0LESHsIpxaTlX3E1Bo%3D&reserved=0.


remove coin prefix of showing address

What does this implement/fix? Explain your changes.
移除地址二维码的币种前缀
Does this close any currently open issues?
If it fixes a bug or resolves a feature request, be sure to link to that issue.
https://github.com/OneKeyHQ/TaskHub/issues/1254
Pull request type

Put an x in the boxes that apply

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

Where has this been tested?
…
Any other comments?
…

记得eth_wallet下有个类似的加prefix的逻辑，看是不是相关的也需要去掉

是指 identity property 里加的 prefix 吗？那个不需要去掉

@QuincySx @liuzjalex 这个 PR 开始，会移除地址二维码的币种前缀。 @guosaitester 有空帮忙回归下地址二维码


add splitter benchmarks

Benchmarks for the old splitter and the current (pipeline) splitter need to be added to the codebase.
related to #619

This still needs to be done @acud ?


Pr/22

https://github.com/TheBrainFamily/wait-for-expect/pull/22 + linting

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add the National Academy of Managerial Staff of Culture and Arts with URL https://nakkkim.edu.ua/

Check the National Academy of Managerial Staff of Culture and Arts out.

@GitTest8 file I am sorry, I have to close the request without merging, because you made a mistake in a request and did not specify any filepath. Please ensure that you are familiar with this repository rules located at the bottom of this page and make a new correct request. Thank you for your understanding!

Please fork SWOT repository, copy file.zip in the root folder of your forked SWOT repository. Then unzip file.zip there with no changes to the directory structure. Then make a new pull request. If you are not able to make the pull request according the instructions, please send us an email to<EMAIL_ADDRESS>Please mention this request URL in the message. I have to close this request without merging. Thank you for your understanding.


Version fix

Affected Issues

Fixes #214

Proposed Changes

Use more standard VERSION file and Travis CI

Codecov Report

Merging #215 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master   #215   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          18     18
  Lines         461    461
  Branches       43     43
=====================================
  Hits          461    461

Impacted Files
Coverage Δ

pybotics/__init__.py
100% <100%> (ø)
:arrow_up:

Coverage remained the same at 100.0% when pulling b35a5a6182bb1fa5b17b56907205a060dc2b92d5 on version-fix into 4f78e666f64c35c93b0f8d5fb2192036749c801d on master.

Coverage remained the same at 100.0% when pulling b35a5a6182bb1fa5b17b56907205a060dc2b92d5 on version-fix into 4f78e666f64c35c93b0f8d5fb2192036749c801d on master.

Coverage remained the same at 100.0% when pulling b35a5a6182bb1fa5b17b56907205a060dc2b92d5 on version-fix into 4f78e666f64c35c93b0f8d5fb2192036749c801d on master.

Coverage remained the same at 100.0% when pulling c53b5515d8262028191725087eeeb706b76f3fa1 on version-fix into 4f78e666f64c35c93b0f8d5fb2192036749c801d on master.

Coverage remained the same at 100.0% when pulling c53b5515d8262028191725087eeeb706b76f3fa1 on version-fix into 4f78e666f64c35c93b0f8d5fb2192036749c801d on master.

Coverage remained the same at 100.0% when pulling c53b5515d8262028191725087eeeb706b76f3fa1 on version-fix into 4f78e666f64c35c93b0f8d5fb2192036749c801d on master.

Coverage remained the same at 100.0% when pulling c53b5515d8262028191725087eeeb706b76f3fa1 on version-fix into 4f78e666f64c35c93b0f8d5fb2192036749c801d on master.


In Gear category, the filter contains only a black color, despite the products available in different colors.

Visit the Vuestorefront
Go to the Hardware category
Check the available colors in the filter

Current results:
There is only a black color, although there are products of different colors.

Expected results:
More colors should be available in the filter.

Fixed!


http.ReadRequest doesn't recognize http2?

What version of Go are you using (go version)?
Go 1.10.2
Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
linux/amd64
What did you do?
I am trying to read http2 request on a tcp connection, which is set up like this -
            cert, err := tls.LoadX509KeyPair(certfile, certkeyfile)
            if err != nil {
                    return nil, err
            }
            tlsConfig := &tls.Config{
                    Certificates: []tls.Certificate{cert},
                    ServerName:   "mysrvr",
                    NextProtos:   []string{"h2", "http/1.1", "http/1.0"},
                    Time:         time.Now,
                    Rand:         rand.Reader,
            }
            tlsConfig.BuildNameToCertificate()
            tlsConfig.PreferServerCipherSuites = true
            listener := tls.Listen("tcp", ":"+sqp.ListenerPort, tlsConfig)

            for {
                   conn, err := listener.Accept()
                   reader := bufio.NewReader(conn)
                   req, err := http.ReadRequest(reader) // problem here
                   // do other things with req
             }

What did you expect to see?
When I do curl https://<IP_ADDRESS>:8000 -k --http2 to the above server, I was expecting http.ReadRequest to parse the request same as it does for http/1.1 or 1.0.
What did you see instead?
What I saw was that the request contained PRI method (which is defined in http2 rfc) and even if I ignore the complete connection preface and the SETTINGS frame after it, I still don't get the original request. Though if I try reading directly from tcp connection, I get a blob right after PRI and SETTINGS frame.
I looked at ParseHTTPVersion (https://golang.org/src/net/http/request.go?s=29537:29588#L708) called from readRequest and it doesn't even have a case for HTTP/2. Does it mean I can't use http.ReadRequest for HTTP/2 requests?

Hi,
the Go project does not use its bug tracker for general discussion or asking questions. The Github bug tracker is only used for tracking bugs and proposals going through the Proposal Process.
Please see the Questions wiki page; it has a list of good places for asking questions. Thanks!
Closing, it appears that this is not a bug. If it turns out to be a bug, comment here and we'll re-open.

I won't categorize it as a bug, but it certainly seems like it's a feature or documentation miss. There might be allternatives to what I am trying to do but it certainly is not clear.

Okay.. re-opening and marking as a possible doc enhancement.

CC: @bradfitz


enhancement speed up decommission process (#13579)

Proposed changes
Issue Number: close #13579
Problem summary
Describe your changes.
Checklist(Required)

Does it affect the original behavior:

[ ] Yes
[x] No
[ ] I don't know

Has unit tests been added:

[x] Yes
[ ] No
[ ] No Need

Has document been added or modified:

[ ] Yes
[ ] No
[x] No Need

Does it need to update dependencies:

[ ] Yes
[x] No

Are there any changes that cannot be rolled back:

[ ] Yes (If Yes, please explain WHY)
[x] No

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 38.02 seconds
load time: 581 seconds
storage size:<PHONE_NUMBER>2 Bytes
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20221102072225_clickbench_pr_38053.html


Is it possible to use without MPI?

I would like to avoid any MPI setup.
I'm using only 1 machine, so I guess that I won't get any performance boost by using MPI, right?
Is there any configuration parameter or similar that we can use to avoid needing MPI?
Thanks!

Unfortunately, this is not an option at the moment.


2.5.1 (043C): Droplet drag filter no longer suppresses non-folder items

Dragging non-folder items to the app icon/alias no longer rejects the items. Drawing to the app window works as expected though. (Yes, I understand these are different mechanisms ;-)
The only issue I see in CFBundleDocumentTypes in the app plist is a duplicate CFBundleTypeOSTypes key:

  	<key>CFBundleTypeOSTypes</key>
  	<array>
  		<string>fold</string>
  	</array>

This is a tricky one. It seems that some files are represented as folders, like zip files, and so the OS won't filter them out. I need to do more research here...

Here's the CFBundleDocumentTypes from a Applescript droplet I did. It will not any item except folders to be dropped on the icon/alias. I just tested this again by dragging a CBZ file to the Applescript droplet – circle slash pointer displayed and rejected the item.

CFBundleDocumentTypes

CFBundleTypeName
Folders
CFBundleTypeOSTypes

fold

CFBundleTypeRole
Viewer

This is something I can't fix. Some files are just treated like folders by the OS, doesn't matter how many different types I try to exclude, as long as fold or public.folder or public.directory is included, they are seen as valid files. For the time being, I'm calling this an apple bug.


should we add this disclaimer about if it applies to you

This is from the list of activities that require a plan:
A comprehensive listing of all activity codes that generally require applicants to submit a Data Management and Sharing Plan. Read funding opportunities carefully – requirements may differ from general activity code applicability for a small number of opportunities
Maybe we should add the bold part

also wonder if we need a disclaimer to check that the link we have is up-to-date? they include a link at the bottom about that


Extend mysql access to custom commands

Good morning!
I'm testing the code, trying to implement a command that uses mysql as storage.
I've seen that on a recent update of the source now the pdo variable it's inside a new DB class... but I cannot figure out how to use the class to make custom queries to the database...
Can anyone help me please?
Thanks in advance, Sergio

Thanks for reporting, the idea is to have all the queries inside DB.php so you can make your own extending the DB class and creating new methods.
Anyway in 0.17.1 I've reintroduced the pdo var in Telegram.php.

Hi, thank you for the update. Maybe it would be better remove the pdo var in Telegram and implement some mecanism inside DB.php, if you can provide a quick example it would be a great starting point, I think.

You can inspire from the ConversationDB.php Class