Token error when connecting via SSH to Ubuntu VM with Azure AD login

Describe the bug
Unable to connect via SSH to an Ubuntu VM using Azure AD login (AADSSHLoginForLinux extension) - token error
Command Name
az ssh vm Extension Name: ssh. Version: 0.1.6.
Errors:
The command failed with an unexpected error. Here is the traceback:
Get Token request returned http error: 400 and server response: {"error":"invalid_grant","error_description":"AADSTS700082: The refresh token has expired due to inactivity.Â The token was issued on 2021-11-07T15:33:50.2272016Z and was inactive for 90.00:00:00.\r\nTrace ID: c3312c26-f395-4027-8ae0-278146bf2f00\r\nCorrelation ID: a08e5af8-a9b1-43ab-9276-56a04c7f8341\r\nTimestamp: 2022-04-01 10:23:15Z","error_codes":[700082],"timestamp":"2022-04-01 10:23:15Z","trace_id":"c3312c26-f395-4027-8ae0-278146bf2f00","correlation_id":"a08e5af8-a9b1-43ab-9276-56a04c7f8341","error_uri":"https://login.microsoftonline.com/error?code=700082"}
Traceback (most recent call last):
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\knack/cli.py", line 231, in invoke
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 657, in execute
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 720, in _run_jobs_serially
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 691, in _run_job
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 328, in __call__
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/command_operation.py", line 121, in handler
  File "C:\Users\MyUserName\.azure\cliextensions\ssh\azext_ssh\custom.py", line 22, in ssh_vm
    _do_ssh_op(cmd, resource_group_name, vm_name, ssh_ip,
  File "C:\Users\MyUserName\.azure\cliextensions\ssh\azext_ssh\custom.py", line 49, in _do_ssh_op
    cert_file, username = _get_and_write_certificate(cmd, public_key_file, None)
  File "C:\Users\MyUserName\.azure\cliextensions\ssh\azext_ssh\custom.py", line 74, in _get_and_write_certificate
    _, certificate = profile.get_msal_token(scopes, data)
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/_profile.py", line 645, in get_msal_token
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/_profile.py", line 1115, in retrieve_token_for_user
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\adal/authentication_context.py", line 145, in acquire_token
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\adal/authentication_context.py", line 128, in _acquire_token
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\adal/authentication_context.py", line 143, in token_func
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\adal/token_request.py", line 349, in get_token_from_cache_with_refresh
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\adal/token_request.py", line 127, in _find_token_from_cache
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\adal/cache_driver.py", line 198, in find
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\adal/cache_driver.py", line 177, in _refresh_entry_if_necessary
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\adal/cache_driver.py", line 153, in _refresh_expired_entry
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\adal/token_request.py", line 137, in _get_token_with_token_response
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\adal/token_request.py", line 341, in _get_token_with_refresh_token
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\adal/token_request.py", line 112, in _oauth_get_token
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\adal/oauth2_client.py", line 289, in get_token
adal.adal_error.AdalError: Get Token request returned http error: 400 and server response: {"error":"invalid_grant","error_description":"AADSTS700082: The refresh token has expired due to inactivity.Â The token was issued on 2021-11-07T15:33:50.2272016Z and was inactive for 90.00:00:00.\r\nTrace ID: c3312c26-f395-4027-8ae0-278146bf2f00\r\nCorrelation ID: a08e5af8-a9b1-43ab-9276-56a04c7f8341\r\nTimestamp: 2022-04-01 10:23:15Z","error_codes":[700082],"timestamp":"2022-04-01 10:23:15Z","trace_id":"c3312c26-f395-4027-8ae0-278146bf2f00","correlation_id":"a08e5af8-a9b1-43ab-9276-56a04c7f8341","error_uri":"https://login.microsoftonline.com/error?code=700082"}

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az ssh vm --ip {}

Expected Behavior
Environment Summary
Windows-10-10.0.22000-SP0
Python 3.8.9
Installer: MSI

azure-cli 2.29.0 *

Extensions:
ssh 0.1.6

Additional Context

route to CXP team

@marineadz Apologies for the late reply. The error is self explanatory. Due to inactivity the refresh AAD bearer token seems to be expired. Could you please follow the below steps in order ?

az extension update --name ssh  # update ssh extension since you are using an older one
az login # Login to your Azure account. So that we get a new AAD bearer token

On a side note, you may also have to update your AzCLI since you are using an older version. Please let me know if you still encounter the same issue after following the above plan. Awaiting your reply.

@navba-MSFT All solved, updating AzCLI did the trick. Thanks for your help.


Bump Metronome to 0.6.44

High-level description
What features does this change enable? What bugs does this change fix?
Corresponding DC/OS tickets (required)

A bug was introduced in Metronome for DC/OS 2.0.3 in which jobs created in previous versions of DC/OS were not seen. This has been fixed, and jobs created before 2.0.3 are visible once again.  MARATHON-8746
Metronome jobs can be configured to join container networks - MARATHON-8727

Related tickets (optional)
Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[x] Change log from the last version integrated (this should be a link to commits for easy verification and review): a4d46e8..f89f00d

@mesosphere-mergebot label ready for review


add path parameters

I'm coming from issue #203 and wanted to open a PR to discuss my changes. Currently, how I have it working is you add entries to a table in a new "Params" tab, and it replaces the instances of :${paramName} (colon preceding parameter name), with the value of said param. I think I should add a visual indicator in the RequestUrlBar for params, similar to how environment variables appear. This is very WIP, so please let me know what must be changed or what is a bad idea. Thanks for being part of this wonderful app!
Image of Functionality:

This should be a priorized feature.

feature that will help a lot, I look forward to this version.

Reading through the code, looks nice so far - great work, haven't determined whether it's backwards compatible yet.

I think I should add a visual indicator in the RequestUrlBar for params, similar to how environment variables appear.

💯% It would be great if the indicator was similar to the env variables, and when you click on it, it focuses the parameter in the params table.

Reading through the code, looks nice so far - great work, haven't determined whether it's backwards compatible yet.

I think I should add a visual indicator in the RequestUrlBar for params, similar to how environment variables appear.

💯% It would be great if the indicator was similar to the env variables, and when you click on it, it focuses the parameter in the params table.

Maybe I should be suggesting this in the parent issue, and I'm not a maintainer, but:
Would Placeholders be able to supplement Environment variables and use the same syntax?
That way I could, for example, have a request like {{ my_service.url }}/api/v1/user/{{ userId }}/attributes with my_service: { url: "..." } in the environment and userId in the parameters tab.
I thought for a minute that would preclude @apisaint's [suggestion]:(https://github.com/Kong/insomnia/pull/2936#issuecomment-756576846):

It would be great if the indicator was similar to the env variables, and when you click on it, it focuses the parameter in the params table
...but maybe in this case it would focus on the params table if it's defined there, and open the Environment Variable prompt if it's not?

Maybe I should be suggesting this in the parent issue, and I'm not a maintainer, but:
Would Placeholders be able to supplement Environment variables and use the same syntax?
That way I could, for example, have a request like {{ my_service.url }}/api/v1/user/{{ userId }}/attributes with my_service: { url: "..." } in the environment and userId in the parameters tab.
I thought for a minute that would preclude @apisaint's [suggestion]:(https://github.com/Kong/insomnia/pull/2936#issuecomment-756576846):

It would be great if the indicator was similar to the env variables, and when you click on it, it focuses the parameter in the params table
...but maybe in this case it would focus on the params table if it's defined there, and open the Environment Variable prompt if it's not?

+1 on this feature, since it tries to incorporate by default the Path Variables as in Postman.
There is this plugin as a temporary workaround https://github.com/gschier/insomnia-plugin-path-parameters, but the url preview does not work.

Any updates?

any update on this? Is work still ongoing?

The parent issue was converted to a discussion and has a response on it, @danshapir and @eltonsandre to address this #3551 (comment)

@apisaint what's going on with this pull?
It's a crucial feature why you don't merge it?

shouldn't the path parameters be like {paramName} instead of :paramName ?
This will conform with open api 3.0 https://swagger.io/docs/specification/describing-parameters/
The request generation in insomnia should also be fixed, because now {paramName} in design gets converted to {{paramName}} in debug

Closed as stale.

This won't be merged?


"com.ouroboros.enable=false" not working properly

Hi all
I have have explicitly set that ouroborus is disabled on the postgres container, but it still updated it.
Have I set the label incorrectly?
Postgres docker-compose:
version: '3.7'

services:
  postgres:
    image: postgres:12.1
    labels:
      ### Ouroboros config
      - "com.ouroboros.enable=false"
    restart: always

Ouroboros docker-compose:
version: '3.7'

services:
  ouroboros:
    image: pyouroboros/ouroboros:latest
    container_name: ouroboros
    restart: always
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - $HOME/.docker/config.json:/root/.docker/config.json
    environment:
      #- INTERVAL=300 # Checks every 5 minutes - value in seconds
      #- RUN_ONCE=true # testing environment requires manual trigger
      - LOG_LEVEL=info
      - SELF_UPDATE=true
      #- IGNORE=postgres mongo # ignores the containers (container names) # done with labels
      - CLEANUP=true # deletes the old image after a successful update
      - TZ=Europe/Zurich
      - LABELS_ONLY # ouroborus has to be explicitly enabled or disabled on a container

Thanks all

You have to set - LABELS_ONLY=true in your ouroboros config. If you set this option you can neglect the label in your postgres config...

You have to set - LABELS_ONLY=true in your ouroboros config. If you set this option you can neglect the label in your postgres config...

Thanks, I missed that!
I updated my config to:
version: '3.7'

services:
  ouroboros:
    image: pyouroboros/ouroboros:latest
    container_name: ouroboros
    restart: always
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
    environment:
      #- INTERVAL=300 # Checks every 5 minutes - value in seconds
      #- RUN_ONCE=true # testing environment requires manual trigger
      - LOG_LEVEL=info
      - SELF_UPDATE=true
      - CLEANUP=true # deletes the old image after a successful update
      - TZ=Europe/Zurich
      - LABELS_ONLY=true # ouroborus has to be explicitly enabled or disabled on a container

and:
version: '3.7'

services:
  app:
    image: app:latest
    labels:
      ### Ouroboros config
      - "com.ouroboros.enable=true"
    restart: always

When I docker-compose up Ourobors I receive the following INFO log:
ouroboros    | 2020-03-02 14:57:28 : INFO : ouroboros : Version: 1.4.3-master
ouroboros    | 2020-03-02 14:57:28 : WARNING : config : labels_only enabled but not in use without label_enable
ouroboros    | 2020-03-02 14:57:28 : WARNING : NotifySlack : No user was specified; using "Ouroboros".
ouroboros    | 2020-03-02 14:57:29 : INFO : dockerclient : No containers are running or monitored on ********.sock
ouroboros    | 2020-03-02 14:57:29 : WARNING : NotifySlack : Failed to send to Slack: error=200.

The Slack startup message is still send, but that's another thing. Primarily, I wonder why the containers are not being udpated.
I assume it is not related to the docker network as Ouroboros binds directly into the docker socket.

I also missed a thing. you have to set - LABEL_ENABLE=true to get LABELS_ONLY working in your ouroboros config. See WIKI entry for LABELS_ONLY:

If label_enable is not true, this option is ignored

That's it, many thanks @cybermcm
These two labels were required:
- LABELS_ONLY=true
- LABEL_ENABLE=true


Coverage improvements

Coverage decreased (-0.2%) to 92.436% when pulling cd691b52a306e70bf872076892ac683ff91324fd on CoverageImprovements into 4744d9b9624e7341884d56f251342566ffa56505 on master.


[daw-json-link] update to v3.23.1

Library name
daw-json-link
New version number
v3.23.1
Other information that may be useful (release notes, etc...)
What's Changed

Fix link in readme by @codeinred in https://github.com/beached/daw_json_link/pull/415

Bugfix for narrow_cast and updated deps by @beached in https://github.com/beached/daw_json_link/pull/414

Updated deduced empty fix to serialize and fast path the parsing

Added test for issue 409

Bugfix: MSVC caught error in checking code

small change to test

Initial support of parsing to/from aggregates without mapping

Fixed issue with using cpp20 features

Potential workout for gcc < 12 bug in detection

Updated deps, and minor cleanups

Fixed attribute placement

Pruned some headers

Readded missing header for MSVC

Fixed warning from clang-17 when static call op is used
clang-16 and above sets the feature flag for the static call operator
even in prior C++ versions and with pedantic-errors set.  It will
sometimes warn though.  Disabled warning around areas of use when
clang-17 is used.

missing include in test

Reduced symbol sizes and minimized headers

Added Boost PFR mapping header and some minor refactors

Fixed ref issue

Rewrote the code around digits100 to work around MSVC issue

Fixed compile time error message

Fixed example in aliases.md and added clarification of how it works

Added extra check for uniqueness in json_variant.

Added extra check for uniqueness in json_variant that warns earlier and
with less noise

Small update to includes

Added new test related to issue and updated alias test

Added missing include

Split out io related writable_outputs
Split out io related writable_outputs in order to allow compile time
disabling their default inclusion via DAW_JSON_NO_DEFAULT_OSTREAM_WRITER
and DAW_JSON_NO_DEFAULT_CSTDIO_WRITER cmake/compile options

Fixed constexpr in 17 issue and missing namespace

Fixed bug in error checking plus strings in unknown types

Expended test to other types

Disabled clang-12 to 14 with C++20 as it breaks on libstdc++

New Contributors

@codeinred made their first contribution in https://github.com/beached/daw_json_link/pull/415

Full Changelog: https://github.com/beached/daw_json_link/compare/v3.23.0...v3.23.1

If it hasn't been done yet, v3.23.2 would be better there was a small update that may not affect packaged sources


Regular update for Dependencies

User Story - Business Need
We wish to keep dependencies up to date so we do not need such massive overhauls of our system. This will be a recurring ticket that will be done every sprint. We will update all dependencies we are able to. Any conflicts will get a ticket. This is intended to be a day of work at most because this is intended to update with only non-breaking changes.

[ ] Ticket is understood and QA has been contacted

User Story
As VA Notify
I want to keep our service up to date
So that we are secure and as free of bugs as possible
Additional Info and Resources

Relevant section of README.md

Engineering Checklist

[x] Update performed
[ ] Dependabot issues updated
[ ] Any conflicts removed and tickets created
[x] Passes all tests locally
[x] Passes userflows and QA Suite testing against Dev
[ ] Any major changes are investigated (compare existing to new version changes)

[ ] Any questionable version changes are removed and a ticket is created

[ ] Tickets created are added to the Epic for tracking purposes

Acceptance Criteria
Repo dependencies are updated and we have no broken functionality. Issues opened by Dependabot are resolved. Tickets created for any updates we could, or should, not do.
QA Considerations

[ ] Check to see if these updates cancel out any Twistlock issues
[ ] QA Regression tests pass after deploying this code.

@EvanParish noting that the click Dependbot issue could not be closed out the last time because requirements-cli.txt was not updated with click.  Can you be sure to take a look at that file, please?

When attempting to test the dependency updates the regression suit was run against the deployed code and something in this branch caused it to run for 30+ min before we stopped it. Going back to master we saw it take the usual < 5 min amount of time. I'm working on figuring out what might be causing the issue.

I rolled back all of the patch updates and deployed with just minor version updates. This seems to have solved the issue, but I'm not sure which package caused the delayed sending in the first place. I suspect that future updates probably won't have that issue, so it's most likely just a waste of time finding the specific one.

Sending approved and merged PR to Perf on tag v1.6.13-1472-dependencies. Doesn't look like any Twistlock issues can be cleared here.

Click dependabot issue cleared on this one.

A number of failed tests on the first run
 FAILED tests/test_communication_item.py::test_get_communication_item_invalid_communication_item_404
FAILED tests/test_service.py::test_get_all_services - AssertionError: Invalid...
FAILED tests/test_service_api_key.py::test_get_an_api_key - AssertionError: I...
FAILED tests/test_service_template.py::test_get_all_templates - AssertionErro...
FAILED tests/test_v2_notifications_email.py::test_send_email[Email: Basic Formatting w/ EDIPI and Optional Properties]
FAILED tests/test_v3_notifications_email.py::test_send_v3_email[Email: Basic Formatting]
FAILED tests/test_v3_notifications_email.py::test_send_v3_email_invalid_payload_400[400 EMAIL: Missing required property 'template_id']
FAILED tests/test_v3_notifications_email.py::test_send_v3_email_invalid_payload_400[400 EMAIL: Invalid type 'client_reference' not a string]
FAILED tests/test_v3_notifications_sms.py::test_send_v3_sms[SMS: Short w/ sms and EDIPI recipient ID]
FAILED tests/test_v3_notifications_sms.py::test_send_v3_sms_invalid_auth_401_403[SMS 403: invalid bearer token]

Re-running tests, might be related to the same issue as when the regression is run immediately after the deploy to Staging. The tag Push to Perf also runs the regression immediately.

Now even more test failures on run 2
FAILED tests/test_communication_item.py::test_create_communication_item[Create Communication Item w Default Send Indicator as true]
FAILED tests/test_communication_item.py::test_create_communication_item[Create Communication Item w Default Send Indicator as false]
FAILED tests/test_communication_item.py::test_get_by_communication_item_id - ...
FAILED tests/test_communication_item.py::test_update_communication_item_negative_tests_400[Payload Name non-unique]
FAILED tests/test_communication_item.py::test_get_communication_item_invalid_bearer_token_401[GET All]
FAILED tests/test_communication_item.py::test_create_communication_item_negative_tests_400[Payload VAProfile Item ID non-unique]
FAILED tests/test_service_sms_sender.py::test_get_all_sms_senders - Assertion...
FAILED tests/test_v2_notifications_email.py::test_get_email_notification_statuses
FAILED tests/test_v2_notifications_sms.py::test_get_sms_notification_statuses
FAILED tests/test_v2_notifications_sms.py::test_send_sms_incorrect_format_phone_number_400
FAILED tests/test_v3_notifications_email.py::test_send_v3_email[Email: Basic Formatting w/ BIRLSID]
FAILED tests/test_v3_notifications_email.py::test_send_v3_email_invalid_auth_401_403[SMS 403: invalid bearer token]
FAILED tests/test_v3_notifications_email.py::test_send_v3_email_invalid_payload_400[400 EMAIL: Invalid type 'template_id' not a UUID]
FAILED tests/test_v3_notifications_email.py::test_send_v3_email_invalid_payload_400[400 EMAIL: Invalid type 'email_address' not a string]
FAILED tests/test_v3_notifications_email.py::test_send_v3_email_invalid_payload_400[400 EMAIL: Invalid type 'client_reference' not a string]
FAILED tests/test_v3_notifications_email.py::test_send_v3_email_invalid_payload_400[400 EMAIL: Invalid type 'billing_code' not a string]
FAILED tests/test_v3_notifications_sms.py::test_send_v3_sms[SMS: Short w/ alternate Pinpoint SMS Sender ID]
FAILED tests/test_v3_notifications_sms.py::test_send_v3_sms_invalid_payload_400[400 SMS: Invalid format 'phone_number']
============ 18 failed, 172 passed, 3 xfailed in 264.17s (0:04:24) =============

I need to investigate this prior to running any more regressions.

Running the regression from the QA repo against the private endpoints now.

Private regression failed due to a communication item not being properly deleted on the previous test run. Re-running.

Regression passes in Perf
================== 190 passed, 3 xfailed in 172.58s (0:02:52) ==================
Holding ticket for the remaining dependabot upgrades.

Dependbot issue merged and sent to Perf on v1.6.13-1472-cryptography.
Regression fails against public endpoints with read timeouts, running regression from QA repo against private endpoints.

Regression passes
================== 190 passed, 3 xfailed in 160.74s (0:02:40) ==================
The next dependabot issues are all for actions.

Rather than use the tag push to perf to test the dependabot docker/build-push-action upgrade, am sending master up to Perf using the Deploy to Env action.
Will wait for the cron to run tonight on Update cached Docker image.

Created ticket up update phonenumbers package in utils repo: https://app.zenhub.com/workspaces/va-notify-620d21369d810a00146ed9c8/issues/gh/department-of-veterans-affairs/notification-utils/143

Have removed the run-qa-suite from the 3 workflows and merged to master.
Using Deploy to Env to send up docker/build-push-action (which will actually test that action).

Build/Push validated as working correctly.
The next PR combines and touches a number of workflows, including Build, User Flows, Locust, DB Downgrade, Deploy Lambda, Deployment, Regression (not going to bother testing), Tests, Twistlock, Update Cached Image (will wait for cron), Datadog Image Update. Will come up with a test plan after it is merged.

aws-actions/configure-aws-credentials from 2.2.0 to 4.0.1
actions/checkout v3 to v4
setup-buildx-action v2 to v3

Validation checklist for combined PR for workflow updates:

[ ] Wait for tomorrow's run of Update Cached Image and ensure it ran without errors
[ ] Deploy to Perf with action and send lambdas to vet a number of workflows

[ ] Twistlock
[ ] Build
[ ] Deploy
[ ] Deploy Lambda

[ ] Run an sms locust test
[ ] Run an email locust test
[ ] Wait for some PR push to see if unit tests still run
[ ] Datadog Image Update?
[ ] Not testing the regression workflow
[ ] Not testing DB downgrade

Who knows if the locust email load test ever worked. Has not been run before, I ran it against perf and dev and kept getting
Waiter CommandExecuted failed: Max attempts exceeded. Previously accepted state: For expression "Status" we matched expected path: "InProgress"

The locust instance is up and running, reporting healthy status checks.

Update cached docker image works as expected.
Closing as passed!

I felt that I should leave my notes here about the rest of the dependencies.
Dependabot PR Test failures:

urllib3 v1.26.16 -> v2.0.6

botocore depends on urllib3<1.27 and >=1.25.4
ticket to find a workaround for this is already created

phone numbers v8.12.57 -> v8.13.22

utils depends on v8.12.57 and a test breaks when updating to v8.13.22
create ticket for this - utils-143

flake8 v3.7.7 -> v6.1.0

code style check fails in many places
would this be handled by the black format ticket?

marshmallow v2.20.5 -> v3.20.1

we need to upgrade sql alchemy first, which is planned for a later time


spruce: Fix build to use go_1_17 and teach go-module a trick.

The root cause of the bug here is that while the go.mod file was updated
to say 1.17, it was not actually run through go.mod 1.17, which ensures
that all deps are enumerated in the go.mod and require files. It
correctly fixes this when run - updating go.mod and go.sum
Note that since these deps are recursive child deps of the existing deps, this
hash should be stable.

Motivation for this change
Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

Haven't we tried this before anyway? Seems very familiar.

This is a 1.17 specific problem (it got a little stricter about the modules.txt folder matching the go.mod folder, and apparently does some undocumented go.mod changes when you run go mod vendor.
I've pushed some patches upstream - I think there are 7 packages this would fix.

This is a 1.17 specific problem (it got a little stricter about the modules.txt folder matching the go.mod folder, and apparently does some undocumented go.mod changes when you run go mod vendor.

It isn't a problem with buildGoModule, it is an upstream problem. If it can be fixed there why should we add another workaround? Upstreams will need to fix it eventually anyway won't they?

I'll go poke upstreams - Some of the upstreams are super dead (i.e. I think one of the packages hasn't updated itself since go 1.12), I guess if upstreams don't respond we should just mark the packages broken? Or should we delete them?


Fix #973, CFE_MSG_Init clear option removed

Describe the contribution
Fix #973 - removed the clear=false logic (and clear parameter)
Testing performed
Built and ran test cases with no extended header, extended header with msgid v1, and extended header with msgid v2.  All passed
Expected behavior changes
Always zeroes entire message and sets defaults.
System(s) tested on

Hardware: cFS Dev Server
OS: Ubuntu 18.04
Versions: Bundle main + this commit

Additional context
None
Third party code
None
Contributor Info - All information REQUIRED for consideration of pull request
Jacob Hageman - NASA/GSFC

CCB 2020-11-04 APPROVED

6b453be - rebased on main


{"code":"failure","message":"Invalid list id passed: 1","data":[]}

{"code":"failure","message":"Invalid list id passed: 1","data":[]}
I dont know where am i wrong ?
Isn't the ID = 1 ?

Hello @jpca999
Thank you for contacting us.
The ID 1 you passed is actually the active template ID and not the list ID. Its clear from the screen shot you provided.
You can get all the list details from get_lists() API ( Front end: https://my.sendinblue.com/lists )
Regards
SendinBlue Team

I get this error for list api :  https://github.com/mailin-api/mailin-api-node-js/issues/10
fyi resolved.
I appreciate your time in this issue. Feel free to login in to my account and see whats going wrong---


constrained click to known compatible range

Description
See #4111 for motivation (probably best to review that one first). Does this warrant a patch release?
Self Check:
Strike through any lines that are not applicable (~~line~~) then check the box

[ ] Attached issue to pull request
[ ] Changelog entry
[ ] Type annotations are present
[ ] Code is clear and sufficiently documented
[ ] No (preventable) type errors (check using make mypy or make mypy-diff)
[ ] Sufficient test cases (reproduces the bug/tests the requested feature)
[ ] Correct, in line with design
[ ] End user documentation is included or an issue is created for end-user documentation (add ref to issue here: )

Reviewer Checklist:

[ ] Sufficient test cases (reproduces the bug/tests the requested feature)
[ ] Code is clear and sufficiently documented
[ ] Correct, in line with design

Processing this pull request

Merged into branches iso4 in f5740b0379cfe02ff01979903a94ef7075b481c4


Question about  the pretrained weights for ShuffleNet

Hello,
I tried to verify ShuffleSeg's real-time performance locally, but I didn't find the pretrained weights for ShuffleNet.
Did you release it?

I have the same problem.


Many AT fixes

There are two spurious commits in this PR, which fix the acoustic example when benchmarking.
Apart from those, with this PR a number of issues concerning the AT are fixed:

Avoid unacceptably long AT runs, because too many block sizes were attempted. Now a heuristic is used: only square blocks whose size is a multiple of 2 are picked. This can be refined by extending the corresponding method at_controller.py:AutoTuner:_filter
Avoid executing useless sample runs.
Avoid executing a dry run, which was just a hack to populate some lists and make things work. The dry run was also using block sizes that could go beyond the limits imposed by minimum and maximum, so this might also result in a C-level bug.
Fill in output arrays with some random values, to ensure that the AT works on initialized data. Otherwise, the AT output is just garbage, as some runs (some block sizes) would end up with a lower memory traffic.

Also add a logger function for AT

I know that some tests are still failing, but I've opened the PR so that people can start looking into it

Now there should be only one failing test, which has to do with the fact that I changed the precision of Acoustic from float64 to float32.
I don't remember what it should be. @mloubout enlighten us please

gradient_test should fail. if adjoint_test fails I'l look into the numbers to validate it or not.

@mloubout Later today I'll introduce the minor fixes pointed out by @mlange05 ; once we know how to deal with the acoustic example, this gets a green light and shall be merged

OK, pushed a few fixes here and there that address both your previous comments and the failing tests (I'm making test_gradient as xfailsince now we make use of float32 instead of float64)
I wanna merge this ASAP. Then, I'll file a new PR to merge the performance_measurement branch. Once both are in, we should focus again on having a working TTI as well as performance (acoustic, tti)

Allright, merging as soon as travis is happy

Merging...

Merged.


[Documentation] Code Sample for $.hdb api returns an error

Describe the bug
The code sample in https://www.xsk.io/api/%24.hdb/ returns an error when tried out on Trial.
To Reproduce
Steps to reproduce the behavior:

Create a new .xsjs file and open it.
Copy the code sample from the section Sample Usage of this page: https://www.xsk.io/api/%24.hdb/
Paste the code sample and save.
See error in the Preview view.

Expected behavior
Code sample should not return an error.
Screenshots

Desktop:

OS: Windows 10
Browser: Chrome
Version: Version 93.0.4577.63 (Official Build) (64-bit)

Code in Basic Usage in fact works, so I'm closing the issue.
Best regards,
Svetoslav


Build Instructions for opentelemetry-cpp

Hi @MrMoose ,
I wonder if I could ask you how to build opentelemetry-cpp for Unreal Engine 4/5 on Windows 10 platform. Can you share your build scripts to me?  I have tried many times but still failed (build success but run failed). I'm building the otel-cpp project with setup-buildtools.cmd and build.cmd  scripts where under the opentelemetry-cpp/tools source code directory.

Hello @cnbleu,
build scripts are included in here. You can find instructions in the README.md docs. The script is under Scripts/build_deps.py
It will build all the dependencies including OpenTelemetry
HTH,
Moose

@MrMoose Thank you! I have build with the build_deps.py on my Windows 10. Building were very positive until an error occurs when building grpc:
libprotobuf-lite.lib(libprotobuf-lite.dll) : error LNK2005: "public: __cdecl google::protobuf::io::CodedOutputStream::~CodedOutputStream(void)" (??1CodedOutputStream@io@protobu
f@google@@QEAA@XZ) already defined in libprotobuf.lib(coded_stream.obj [C:\source\CloudConnector\Scripts\raw\grpc-1.49.2\_build\grpc_cpp_plugin.vcxproj]

I don't known the reason for this failure. I didn't change any configuration information from build_deps.py and any other files. Can you help me? Thanks!

Thank you, Moose. Follow is my dependencies:

VS2019: Microsoft Visual Studio Community 2019 (Version Number: 16.11.25)
Windows SDK:  Windows SDK version 10.0.19041.0
C compiler: MSVC 19.29.30148.0 (ABI: x64)
CXX compiler: MSVC 19.29.30148.0 (ABI: x64)
Python

> python --version
> Python 3.11.2

Perl

> perl --version
> This is perl 5, version 32, subversion 1 (v5.32.1) built for MSWin32-x64-multi-thread

CMake

> cmake --version
> cmake version 3.25.3
>
> CMake suite maintained and supported by Kitware (kitware.com/cmake).

nmake

> name/?
> 14.29.30148.0

Above dependencies are already configured in system path (including NASM):

According to the 256-character-filenames, I have already move the source code to C:\source\CloudConnector dir.
One more thing:
When creating CMake build files, there was a warnning:
CMake Warning:
Manually-specified variables were not used by the project:

   BUILD_TESTING
   PROTOBUF_USE_DLLS

I'm not sure above warnings made a difference.
Thank you Moose, please let me know if you need more information.

Thanks, this all looks very much all right.
I can't see what would be causing this but the build process, as you can see is very complex and quite error prone.
I'm currently in the process of bumping all the dependencies to more recent versions, VS2022 and Unreal Engine 5.x.
This may fix your problem. I'm doing some tests with the new versions right now and keep you informed.

Ok, you are doing a great job! I'll build with the scripts again in a new system, and will try your version when it's ready. Thanks.

Thanks, I have updated the scripts to recent versions in master. I wanted to prepare for UE5 anyway. So if you could pull current master and try the scripts with that?
Note that I have only been able to develop and test this using Visual Studio 2022 which is not entirely binary compatible with UE5 unless I install an older (VS2019) toolchain along with and specify it in the CMake targets.
Since you said you are using VS2019 this shouldn't be necessary for you. If the scripts complain about wrong compiler versions right in the beginning, go to line 49 and replace
cmake_toolset = "-T v142,version=14.29"
with
cmake_toolset = "-T v142"
If it doesn't complain, leave it as it is. Perhaps this will yield a new build. If not, you may want to choose the updated OpenTelemetry build that is already checked in this repository. It may work for your use case.
In any case, plz keep me informed if the scripts provided a build for you.

Hi Moose! I have compiled it successfully with your new script after reinstall my windows and vs2022. But it still not work with vs2019. Anyway, I can build my own binary! You do a great job, thank you.


Add Crate to repo

ack.
note that we probably need to revert that merge commit later when rebasing master with upstream


Add support for [env] section in .cargo/config.toml

This adds support for an [env] section in the config.toml files. Environment variables set in this section will be applied to the environment of any processes executed by cargo.
This is implemented to follow the recommendations in https://github.com/rust-lang/cargo/pull/8839#issuecomment-725678657
Variables have optional force and relative flags. force means the variable can override an existing environment variable. relative means the variable represents a path relative to the location of the directory that contains the .cargo/ directory that contains the config.toml file. A relative variable will have an absolute path prepended to it before setting it in the environment.
[env]
FOOBAR = "Apple"
PATH_TO_SOME_TOOL = { value = "bin/tool", relative = true }
USERNAME = { value = "test_user", force = true }

Fixes #4121

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @ehuss (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see the contribution instructions for more information.

Thanks for the PR! Since it's been a few months since I've at least thought about this could you detail your expected use case with this as well? I'm not sure if this should close #4121 since that seems like a different feature request for Cargo

My specific use case is that the rust-cpython and pyo3 crates both look for a PYTHON_SYS_EXECUTABLE environment variable to find the python installation it should link against. I work in a large monorepo that contains rust code that is using rust-cpython, a full win64 python installation and a bunch of other stuff. Whenever possible we avoid using environment variables and prefer to use relative paths to find various components. This means the monorepo is easily relocatable to any location on a developers machine and multiple different versions can exist without having to modify/set any environment variables or other system-wide settings. I want to be able to set PYTHON_SYS_EXECUTABLE for a config.toml at or near the root of the monorepo:
[env]
PYTHON_SYS_EXECUTABLE = { value = "tools/lang/python3.7/python.exe", relative = true }

It seems to be a common thread that comes up during any search for "environment variables in cargo", crates people are using need to find libraries or tools (such as openssl, ffmpeg, python) and the crates use environment variables for that. If you have those dependencies at a known relative location you prefer not to have to rely on global environment variables for that. You can set them locally before you run cargo build but then you have all these issues with tools like IDEs that might not be running within that context. @rib calls out several issues related to this from other projects here: https://github.com/rust-lang/cargo/issues/4121#issuecomment-723465503
You are right, I don't think it solves every aspect of #4121 because there are two different use cases in that issue and the comments. What some would like is a "prebuild" script that runs before dependencies are built that would allow you to set environment variables (and maybe some other settings) that the dependencies would consume. I would love to have a prebuild script myself, but I know there is some reticence about going down that road.

I confirm we have exactly the same use case.

Thanks for the explanation! That all sounds quite reasonable to me and I'd be happy to r+ this especially given that it's unstable. I think we'll want more team sign-off once a motion is made to stabilize, but for now seems good!

:pushpin: Commit 05acf73604a2ac0e16e0bc5f58fff59166ddb84c has been approved by alexcrichton

:hourglass: Testing commit 05acf73604a2ac0e16e0bc5f58fff59166ddb84c with merge 4742e8295769d6d6bac8b7346cfdd5f10cdfe7aa...

:sunny: Test successful - checks-actions
Approved by: alexcrichton
Pushing 4742e8295769d6d6bac8b7346cfdd5f10cdfe7aa to master...

This is going to be very helpful for a number of my projects. Thanks guys.

Big thanks to @wickerwaka for implementing this! I guess #8839 can also be closed based on this?

Perhaps there should be a test that shows what happens if a dependency requires an environment variable. I tried testing this change in that manner with an environment variable that points to the path of a shared library. cargo build worked just fine however cargo run ended with an error with the environment variable not being found. I'm not sure if this is the point of the change, but curious to hear some thoughts.

Perhaps there should be a test that shows what happens if a dependency requires an environment variable. I tried testing this change in that manner with an environment variable that points to the path of a shared library. cargo build worked just fine however cargo run ended with an error with the environment variable not being found. I'm not sure if this is the point of the change, but curious to hear some thoughts.

Could you provide some more details on this? Environment variables are getting set for both build and run and my own personal use case is handling a situation where a dependency needs an environment variable set. However, I am not using that environment variable during the run step. Do you have a minimal example you can share?

Is there a way to generate this Cargo.toml env section from a build.rs script? I am passing in environment variables that are only known at runtime.

@wickerwaka Sorry for the late reply. Here's an example I'm using with https://github.com/Twinklebear/oidn-rs:
// config.toml
OIDN_DIR = "path/to/lib/shared_obj_file.so"
LD_LIBRARY_PATH = "path/to/lib/"

cargo build executes just fine, however cargo run will see an error about not finding the shared object file. I'm assuming this is because at runtime these environment variables are not used.

Shouldn't this have a tracking issue for the -Z configurable-env gate?

Sure, posted #9539 as a tracking issue.


Deployment improvements.

limited deployment options
currently npx pepr build will create a raw manifest and a zarf package. This is a great option but we need more:
ideas:

I think it should generate a helm chart, this will make it easier for people to integrate pepr into autoscaling, proper naming, using a different namespace (if needed), locking down the cluster role bindings. Also including easy environment variables we can pass in via the values file.
we should consider a deployment that splits cluster role bindings, CRD, needed, in the event we work with openshift.
we also will need a way for people to deploy larger capabilities that might contain additional JS modules that don't fit into a Kubernetes secret.
naming the objects with a UUID isn't awesome, those should be defined in the module spec, we can check to make sure it doesn't violate naming in Kubernetes.

I'd rather move things away from (rather than towards) Helm in general. SSA gives us a lot of power and I think is the great future for us. That would also allow to make the whole deployment process far more flexible without additional complexity. See the Kubernetes Fluent Client README for examples:
import { K8s, kind } from "kubernetes-fluent-client";

// Let's create a random namespace to work in
const namespace = "my-namespace" + Math.floor(Math.random() * 1000);

// Create a few resources to work with: Namespace, ConfigMap, and Pod
Promise.all([
  // Create the namespace
  K8s(kind.Namespace).Apply({
    metadata: {
      name: namespace,
    },
  }),

  // Create the ConfigMap in the namespace
  K8s(kind.ConfigMap).Apply({
    metadata: {
      name: "my-configmap",
      namespace,
    },
    data: {
      "my-key": "my-value",
    },
  }),

  // Create the Pod in the namespace
  K8s(kind.Pod).Apply({
    metadata: {
      name: "my-pod",
      namespace,
    },
    spec: {
      containers: [
        {
          name: "my-container",
          image: "nginx",
        },
      ],
    },
  }),
])
  .then(() => console.log("done!"))
  .catch(err => {
    console.error(err);
  });

Someone would have to import an absolutely massive JS library to trigger that, perhaps for those libraries (think the ridiculous beast that AWS) we look at how those are imported first, e.g. using default import vs named import.

Since we already have npx pepr deploy` it might be interesting to make that extensible using the Fluent Client if teams want more power.

We can look into number number 2 for OpenShift, which would be along the lines of creating the correct securityContexts in order for it to pass through the OpenShift's ValidatingAdmissionWebhooks. Link to relevant docs.

Number 4 sees like it is tracked here

All of this is now accounted for in:

(1) We have not had any user ask for this but if they do they can npx pepr build and put the manifests into the templates directory.
(2) Pepr's Deployments use securityContext on pods and containers
(3) Mount multiple secrets as a way to increase module size
(4) https://github.com/defenseunicorns/pepr/issues/281 optional unique name


Provide babel with caller info

Hi @cheton,
Would you be okay with adding in a caller option to the babel call? It would help projects using find-imports to be able to differentiate between the different utilities calling babel.
Thanks!

Coverage remained the same at 97.753% when pulling 0b27801bae36eee3c0b8c3d0eba09ee650919505 on samouri:Provide-babel-with-caller-metadata into 84ff3b5c0e68fca8c3574a3af5b0fc3f838464a8 on cheton:master.


Calibre Update update.ps1

package: https://community.chocolatey.org/packages/calibre
Changed version 5.x download site to version 6.x download site.

Description
change to version 6.x
Motivation and Context

automatic script did not update to version 6 (see comments on: https://community.chocolatey.org/packages/calibre)

https://github.com/chocolatey-community/chocolatey-packages/issues/1949

How Has this Been Tested?

Screenshot (if appropriate, usually isn't needed):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Migrated package (a package has been migrated from another repository)

Checklist:

[ ] My code follows the code style of this repository.
[ ] My change requires a change to documentation (this usually means the notes in the description of a package).
[ ] I have updated the documentation accordingly (this usually means the notes in the description of a package).
[ ] I have updated the package description and it is less than 4000 characters.
[ ] All files are up to date with the latest Contributing Guidelines
[ ] The added/modified package passed install/uninstall in the chocolatey test environment.
[ ] The changes only affect a single package (not including meta package).

Original Location

Original Repository
Open Issues Add the different issues underneath, and tick those that are fixed in this PR

[ ] Issue 1 link
[ ] Issue 2 Link

[ ] Include the link to the opened PR that removes the package from the original location
[ ] The migration guidelines have been followed

:x: Package verification failed, please review the Appveyor Logs and the provided Artifacts before requesting a human reviewer to take a look.

Also see #1947 for another fix for this same issue, awaiting response from @AdmiringWorm

Closing in favor of #1947


Content for issue asset

Heading should be “Add Assets”
For Issue text: “Issue new coins or collectibles on RGB. Set limit and send it around your tribe”
For Receive text: “You can also add an asset to your Tribe wallet by receiving it from someone”

Resolved


INT_SERV_ERR 1 500 returned  when using getVolumes() API call

Hi,
we have a python script that pulls volume capacity information from the 3Par arrays to be stored in InfluxDB. The script worked fine with the old hp3parclient on our 3par 7400s and 8450 until the 3par 8450 was upgraded to <IP_ADDRESS>0 (MU3)+P50  .
If I ran the script now, it returns values up until a point where it give this response:
Unable to get volume capacity
Internal Server Error (HTTP 500) 1 - internal server error
the actual call that fails (values in <> not shown for privacyreasons):
REQ: curl -i http://:8008/api/v1/volumes -X GET -H "Accept: application/json" -H "X-Hp3Par-Wsapi-Sessionkey: " -H "User-Agent: python-3parclient"
Anyone encountered this? Anything changed in that OS version that changes API behavior?

Above curl call will fetch all the volumes from the 3PAR. Do you have a data on the number of volumes on the 3PAR which failed ? Based on this information i can experiment in our lab setup
If you share some logs of working / non-working setup via email to me (william.dur.sandanaraj@hpe.com).. i can further analyse.

when I ran the script, it returned 372 volumes and failed at that point.
But after the upgrade I see some SQLite errors in the activity log on the array as well, that may be connected.

this was resolved, there is a bug in the 3par code that crashes when querying volumes and there is no rcopy license on the array. we applied a temp license and the script started to pull data again from the array.


[Feature] Aspect Ratio support

What problem does this feature solve?
Example of layout I'm trying of achieve:

What I have now, with default settings:

Next row is invisible due to height of first. So I'm looking way to set aspect ratio, so charts will follow it when page resized, not taking way too much height, and different for mobile view.
What does the proposed API look like?
Chart.js have it: https://www.chartjs.org/docs/latest/configuration/responsive.html
options: {
   aspectRatio: 0.5,
}

Aspect ratio would be excellent. I had to go in and mess about with containers and CSS code to get my image scale properly, which was somewhat annoying to do.

Perhaps you can apply the native CSS property aspect-ratio on the container of the chart.

This point is quite critical for my applications.
I often need to get the axis scaled.
Plotly.js has something that let me do that:
https://plotly.com/javascript/reference/layout/xaxis/#layout-xaxis-scaleanchor
Playing with aspect ratio, as a CSS properties may be useful when you have just one vertical axis, for example,
but I need to handle  two or more y-axis.
Please, would you mind to consider to introduce the feature?

I see two issues at stake here.

aspect-ratio, as @plainheart said, is about the container of a chart. It works fine.
responsiveness of a grid of ECharts, as @Depact says - "Next row is invisible due to height of first".
This could be solved with CSS tricks like flex-direction: column;.

This Demo shows both working nicely together, despite not being related.
For Mobile view see this doc.


unsupported mattermost version: 7.0.0

Describe the bug
When Mattermost version 7 is installed, Matterbridge is no longer working. It produces an error
level=fatal msg="Starting gateway failed: Bridge xxxxxx failed to start: unsupported mattermost version: <IP_ADDRESS>.0.0.edd040ffb1f8cc90e91673758a2f2040.false" prefix=main

To Reproduce
Install mattermost version 7.0.0
Expected behavior
should working
Screenshots/debug logs
...
Environment (please complete the following information):

OS: Debian 11
Matterbridge version:  version: 1.25.1 051e6e76

You can try with SkipVersionCheck=true in your mattermost server section

it's works =)

Yes, but some stuff will break the skipversioncheck will make you use mattermost v5 api again.
I'll be releasing an update soon


Implement createPortal API

https://reactjs.org/docs/portals.html

Likely doable via preact-portal

Also material-ui

This is #1 on the todo list.

also in 'reactstrap`
61:13-25 "export 'createPortal' was not found in 'react-dom'
 @ ./node_modules/react-portal/es/Portal.js
 @ ./node_modules/react-portal/es/PortalCompat.js
 @ ./node_modules/react-portal/es/index.js
 @ ./node_modules/reactstrap/dist/reactstrap.es.js```

I took a swing at implementing this (very naively), but no success; render fails with <undefined></undefined> output. I'm going to take a deeper look and also set up a smaller project to reproduce a test environment.
If there's anyway to get a stack trace on an undefined tag, that would be helpful, but I assume the only reason that's not happening is because the root of the issue comes from the custom code in preact-compat that I've added.

When you enable the debug tools you have callback where you can make custom assertions on each vnode object. It has a check if the tag is undefined already built-in. That should help :)

So actually, quick question: is it only related to preact-compat or preact itself? I'm still thinking about switching to preact.
Would the same error show up without using the compatibility layer but preact directly? Thanks!

@samtheprogram hiya! Mind joining our chat?
https://preact-slack.now.sh

Hey @developit, I've joined under the same username as my GitHub account!

Also breaks compatibility with searchkit (elasticsearch component library) with the same error of export createPortal not found in react-dom. I assume all use of the Portal API is not currently available

Hey @Madhu0.
I updated your example code to use a wrapper component to pass the context.
You find it here in the preact repl.

Hey @Kanaye, this works. Thank you for your time.
If we can provide props and context to the component which will be mounted somewhere outside our actual app, aren't we achieving everything React.createPortal does? am i missing something?
I am trying to understand the portal implementation in react, i've gone through createPortal source code and i wasn't able to understand completely. But the basic idea is, it should work just like any other component inside our app, right?
We can even use render(App, target, previousApp) to find the diff in DOM and update, instead of deleting it and rendering it again.

@Madhu0 around 90% of it, yes. They also redirect event bubbling through portal boundaries, which Preact is unlikely to ever do.

This is causing an issue with react-md,
./node_modules/react-md/es/Helpers/Portal.js
11:23-35 'react-dom' does not contain an export named 'createPortal'.

is there any thing we can do while this is not implemented?

Same issue with react-select
'react-dom' does not contain an export named 'createPortal'

If anyone wants to PR the implementation, something like this would work:
import { h } from 'preact';
import Portal from 'preact-portal';

export function createPortal(child, container) {
  return <Portal into={container}>{child}</Portal>
}

nevermind, there was a much smaller and simpler way and I've implemented it in #486. If anyone has time to test it out that would be lovely.

I'm getting the same error about 'createPortal' above.
I know it's not yet released, but I've copied the updates for 'createPortal' from https://github.com/developit/preact-compat/blob/master/src/index.js but am still getting this error:
129:12-33 "export 'createPortal' (imported as 'ReactDOM') was not found in 'react-dom'

What am I missing?


Set servo max voltage to 16 volts on startup

The servos may not have their max voltage set to 16 volts yet. If they are less, we will likely get errors on battery. This PR writes to the servos on startup to set the max voltage to 16 volts.

This should probably be 16.8v, as a fully charged battery could be 16.8v (ignoring the likely voltage droop that will occur)

This should probably be 16.8v, as a fully charged battery could be 16.8v (ignoring the likely voltage droop that will occur)

Dynamixel maximum seems to be 16 volts on the specs

The max that they can "handle" isn't the value you're giving them though. You're giving them 16.8 at startup. Unless the max voltage field only accepts a maximum of 16 then this won't help

The max that they can "handle" isn't the value you're giving them though. You're giving them 16.8 at startup. Unless the max voltage field only accepts a maximum of 16 then this won't help

I can test in dynamixel wizard to see if it will go above, but the docs
https://emanual.robotis.com/docs/en/dxl/mx/mx-106/#max-voltage-limit
say the value can only be in the range of 5v to 16v

The max that they can "handle" isn't the value you're giving them though. You're giving them 16.8 at startup. Unless the max voltage field only accepts a maximum of 16 then this won't help

I can test in dynamixel wizard to see if it will go above, but the docs https://emanual.robotis.com/docs/en/dxl/mx/mx-106/#max-voltage-limit say the value can only be in the range of 5v to 16v

It is not possible to increase it more than 160 in dynamixel wizard

Pretty sure this isn't relevant anymore after some fixes recently to account for the voltage issues.


Could not start StarryPy server

Hi there,
I got stuck by following error at the end of the logs. My server version 20151216 giraffe, and in starbound.config of this version i couldn't find port 21024 so i set the upstream_port to 21025 the same as the gameport. Could you kindly advise how to resolve the issue? Thanks a lot.
Attempting initialization of configuration manager singleton.
Setup console logging...
Setup file-based logging...
2016-05-15 23:12:03,630 - DEBUG - starrypy # Port check enabled. Performing port check to localhost:21025
2016-05-15 23:12:03,632 - DEBUG - starrypy # Port check succeeded. Continuing.
2016-05-15 23:12:03,633 - INFO - starrypy # Started StarryPy server version 1.7.2
2016-05-15 23:12:03,836 - DEBUG - starrypy.plugin_manager.PluginManager # Instantiated plugin "command_plugin"
2016-05-15 23:12:03,837 - DEBUG - starrypy.plugin_manager.PluginManager # Instantiated plugin "mute_manager"
2016-05-15 23:12:03,837 - DEBUG - starrypy.plugin_manager.PluginManager # Instantiated plugin "player_manager_plugin"
2016-05-15 23:12:03,839 - INFO - starrypy.player_manager.manager # Loading player database.
2016-05-15 23:12:03,900 - DEBUG - starrypy.plugin_manager.PluginManager # Instantiated plugin "starbound_config_manager"
2016-05-15 23:12:03,901 - DEBUG - starrypy.plugin_manager.PluginManager # Instantiated plugin "admin_commands_plugin"
2016-05-15 23:12:03,901 - DEBUG - starrypy.plugin_manager.PluginManager # Instantiated plugin "colored_names"
2016-05-15 23:12:03,921 - CRITICAL - starrypy.plugin_manager.PluginManager # Import error for udp_forwarder
2016-05-15 23:12:03,923 - DEBUG - starrypy.plugin_manager.PluginManager # Instantiated plugin "planet_visitor_announcer_plugin"
2016-05-15 23:12:03,924 - DEBUG - starrypy.plugin_manager.PluginManager # Instantiated plugin "chat_logger"
2016-05-15 23:12:03,924 - DEBUG - starrypy.plugin_manager.PluginManager # Instantiated plugin "announcer_plugin"
2016-05-15 23:12:03,924 - DEBUG - starrypy.plugin_manager.PluginManager # Instantiated plugin "new_player_greeter_plugin"
2016-05-15 23:12:03,924 - DEBUG - starrypy.plugin_manager.PluginManager # Instantiated plugin "afk_plugin"
2016-05-15 23:12:03,930 - DEBUG - starrypy.plugin_manager.PluginManager # Instantiated plugin "plugin_manager_plugin"
2016-05-15 23:12:03,930 - DEBUG - starrypy.plugin_manager.PluginManager # Instantiated plugin "uptime_plugin"
2016-05-15 23:12:03,931 - DEBUG - starrypy.plugin_manager.PluginManager # Instantiated plugin "teleport_plugin"
2016-05-15 23:12:03,931 - DEBUG - starrypy.plugin_manager.PluginManager # Instantiated plugin "bookmarks_plugin"
2016-05-15 23:12:03,931 - DEBUG - starrypy.plugin_manager.PluginManager # Instantiated plugin "loginwho_plugin"
2016-05-15 23:12:03,931 - DEBUG - starrypy.plugin_manager.PluginManager # Instantiated plugin "motd_plugin"
2016-05-15 23:12:03,932 - DEBUG - starrypy.plugin_manager.PluginManager # Instantiated plugin "brutus_whisper"
2016-05-15 23:12:03,932 - DEBUG - starrypy.plugin_manager.PluginManager # Instantiated plugin "emotes"
2016-05-15 23:12:03,933 - DEBUG - starrypy.plugin_manager.PluginManager # Instantiated plugin "poi_plugin"
2016-05-15 23:12:03,933 - DEBUG - starrypy.plugin_manager.PluginManager # Instantiated plugin "backups_plugin"
2016-05-15 23:12:03,933 - DEBUG - starrypy.plugin_manager.PluginManager # Instantiated plugin "players_plugin"
2016-05-15 23:12:03,934 - DEBUG - starrypy.plugin_manager.PluginManager # Instantiated plugin "planet_protect"
2016-05-15 23:12:03,936 - DEBUG - starrypy.plugin_manager.PluginManager # Instantiated plugin "admin_messenger"
2016-05-15 23:12:03,937 - DEBUG - starrypy.plugin_manager.PluginManager # Instantiated plugin "mod_chatter"
2016-05-15 23:12:03,937 - DEBUG - starrypy.plugin_manager.PluginManager # Instantiated plugin "claims"
2016-05-15 23:12:03,938 - INFO - starrypy.plugin_manager.PluginManager # Loaded plugins:
afk_plugin
uptime_plugin
teleport_plugin
colored_names
motd_plugin
chat_logger
announcer_plugin
loginwho_plugin
poi_plugin
command_plugin
players_plugin
plugin_manager_plugin
player_manager_plugin
starbound_config_manager
bookmarks_plugin
mute_manager
new_player_greeter_plugin
admin_commands_plugin
brutus_whisper
emotes
backups_plugin
claims
planet_visitor_announcer_plugin
planet_protect
admin_messenger
mod_chatter

2016-05-15 23:12:03,939 - DEBUG - starrypy # Factory created, endpoint of port 21025
2016-05-15 23:12:03,939 - DEBUG - starrypy # Attempting to listen on TCP port 21025
2016-05-15 23:12:03,940 - CRITICAL - starrypy # Cannot listen on TCP port 21025. Exiting.

Hey, it's configuration problem.
Please read https://github.com/StarryPy/StarryPy/blob/master/README.md#configuration

Thanks for replying :)
i actually did tried to set upstream_port to 21024 but got below errors. and i cant find port 21024 in starbound.config either..
steam@starbound:~/StarryPy$ python server.pyAttempting initialization of configuration manager singleton.
Setup console logging...
Setup file-based logging...
2016-05-16 08:47:47,330 - DEBUG - starrypy # Port check enabled. Performing port check to localhost:21024
2016-05-16 08:47:47,334 - CRITICAL - starrypy # The starbound server is not connectable at the address localhost:21024.
2016-05-16 08:47:47,334 - CRITICAL - starrypy # Please ensure that you are running starbound_server on the correct port and that is reflected in the StarryPy configuration.


Feature request: Firefox support?

Any plans to support Firefox?

Yeah, but unfortunately firefox hasn't implemented declarativeNetRequest.onRuleMatchedDebug
I don't know of any other way to do it
https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/declarativeNetRequest/onRuleMatchedDebug
https://bugzilla.mozilla.org/show_bug.cgi?id=1745773

While we can't see the requests in FF, I think we can block them.
I'm not sure how useful that'd be. The extension won't be able to give you any feedback but it could allow you to just block network requests for a particular extension (or all.)
I haven't tried it, but you can probably do that with uBlock Origin already using custom rules.

Ah that's interesting I wasn't sure if UBO was working with extension traffic.
So it might be the case that requests are made but then blocked by UBO
Little rat would show these?

In Firefox, I can't even filter requests originating from other extensions, no matter what I try.

Closing this, I don't see a way of making this work in FF. Reopen if you have any ideas

There is probably a security benefit in not allowing extensions to spy on each other. But, if that's the route Mozilla is going for, I think they should implement the functionality of Little rat into the browser itself. Someone write a feature request?


fix(template): add quantumultx require fields

These fields are mandatory options for the configuration file, even if they have no content.

感谢贡献代码！


Fix up a few things related to min, start and gateway address

the get address pools api was incorrecting only returning the min address, not the configured gateway
the IP allocation code was always starting at min address, instead of starting at min address
min address should be the min address in the range, not the configured start address.
Added a basic unit test for the ipam api

@davidblum - I think this should still have the right behavior for you.  Can you please verify?  I don't think I can write a unit test to cover the case you ran into, since pools cannot be changed via the API.  I'll also try to verify tomorrow.
We figured out something was up when our Gateways became misconfigured when we started running the latest master, which was caused by the IPAM api gateway looking at the wrong value.
@tumblr/collins

👍  although there are more test cases that would be nice to have.  e.g.
no gateway & no start address
a gateway & no start address
no gateway & start address

I have verified that this does not reintroduce the bug reported in #428
I ran the populate.sh script to create 10 dummy assets.
$ curl --basic -u blake:admin:first http://localhost:9000/api/address/pools | jq '.'
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   963  100   963    0     0    711      0  0:00:01  0:00:01 --:--:--   711
{
  "status": "success:ok",
  "data": {
    "POOLS": [
      {
        "NAME": "ADMIN-OPS",
        "NETWORK": "<IP_ADDRESS>/24",
        "START_ADDRESS": "<IP_ADDRESS>",
        "SPECIFIED_GATEWAY": "Unspecified",
        "GATEWAY": "<IP_ADDRESS>",
        "BROADCAST": "<IP_ADDRESS>",
        "POSSIBLE_ADDRESSES": 254
      },
      {
        "NAME": "WEB-EDIT",
        "NETWORK": "<IP_ADDRESS>/24",
        "START_ADDRESS": "<IP_ADDRESS>",
        "SPECIFIED_GATEWAY": "Unspecified",
        "GATEWAY": "<IP_ADDRESS>",
        "BROADCAST": "<IP_ADDRESS>",
        "POSSIBLE_ADDRESSES": 254
      },
      {
        "NAME": "DEV",
        "NETWORK": "<IP_ADDRESS>/24",
        "START_ADDRESS": "<IP_ADDRESS>",
        "SPECIFIED_GATEWAY": "Unspecified",
        "GATEWAY": "<IP_ADDRESS>",
        "BROADCAST": "<IP_ADDRESS>",
        "POSSIBLE_ADDRESSES": 254
      },
      {
        "NAME": "WEB-SECURE",
        "NETWORK": "<IP_ADDRESS>/28",
        "START_ADDRESS": "<IP_ADDRESS>",
        "SPECIFIED_GATEWAY": "Unspecified",
        "GATEWAY": "<IP_ADDRESS>",
        "BROADCAST": "<IP_ADDRESS>",
        "POSSIBLE_ADDRESSES": 14
      },
      {
        "NAME": "AAA",
        "NETWORK": "<IP_ADDRESS>/28",
        "START_ADDRESS": "<IP_ADDRESS>",
        "SPECIFIED_GATEWAY": "Unspecified",
        "GATEWAY": "<IP_ADDRESS>",
        "BROADCAST": "<IP_ADDRESS>",
        "POSSIBLE_ADDRESSES": 14
      }
    ]
  }
}
$ curl --basic -u blake:admin:first -X PUT -d pool=DEV http://localhost:9000/api/asset/tumblrtag300/address | jq '.'
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   193  100   185  100     8   1156     50 --:--:-- --:--:-- --:--:--  1163
{
  "status": "success:created",
  "data": {
    "ADDRESSES": [
      {
        "ASSET_ID": 2,
        "ASSET_TAG": "tumblrtag300",
        "GATEWAY": "<IP_ADDRESS>",
        "ADDRESS": "<IP_ADDRESS>",
        "NETMASK": "<IP_ADDRESS>",
        "POOL": "DEV",
        "ID": 1
      }
    ]
  }
}

I then modified DEV to start at address <IP_ADDRESS>
$ curl --basic -u blake:admin:first http://localhost:9000/api/address/pools | jq '.'
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   964  100   964    0     0    510      0  0:00:01  0:00:01 --:--:--   510
{
  "status": "success:ok",
  "data": {
    "POOLS": [
      {
        "NAME": "ADMIN-OPS",
        "NETWORK": "<IP_ADDRESS>/24",
        "START_ADDRESS": "<IP_ADDRESS>",
        "SPECIFIED_GATEWAY": "Unspecified",
        "GATEWAY": "<IP_ADDRESS>",
        "BROADCAST": "<IP_ADDRESS>",
        "POSSIBLE_ADDRESSES": 254
      },
      {
        "NAME": "WEB-EDIT",
        "NETWORK": "<IP_ADDRESS>/24",
        "START_ADDRESS": "<IP_ADDRESS>",
        "SPECIFIED_GATEWAY": "Unspecified",
        "GATEWAY": "<IP_ADDRESS>",
        "BROADCAST": "<IP_ADDRESS>",
        "POSSIBLE_ADDRESSES": 254
      },
      {
        "NAME": "DEV",
        "NETWORK": "<IP_ADDRESS>/24",
        "START_ADDRESS": "<IP_ADDRESS>",
        "SPECIFIED_GATEWAY": "Unspecified",
        "GATEWAY": "<IP_ADDRESS>",
        "BROADCAST": "<IP_ADDRESS>",
        "POSSIBLE_ADDRESSES": 254
      },
      {
        "NAME": "WEB-SECURE",
        "NETWORK": "<IP_ADDRESS>/28",
        "START_ADDRESS": "<IP_ADDRESS>",
        "SPECIFIED_GATEWAY": "Unspecified",
        "GATEWAY": "<IP_ADDRESS>",
        "BROADCAST": "<IP_ADDRESS>",
        "POSSIBLE_ADDRESSES": 14
      },
      {
        "NAME": "AAA",
        "NETWORK": "<IP_ADDRESS>/28",
        "START_ADDRESS": "<IP_ADDRESS>",
        "SPECIFIED_GATEWAY": "Unspecified",
        "GATEWAY": "<IP_ADDRESS>",
        "BROADCAST": "<IP_ADDRESS>",
        "POSSIBLE_ADDRESSES": 14
      }
    ]
  }
}
$ curl --basic -u blake:admin:first -X PUT -d pool=DEV http://localhost:9000/api/asset/tumblrtag301/address | jq '.'
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   194  100   186  100     8   1305     56 --:--:-- --:--:-- --:--:--  1309
{
  "status": "success:created",
  "data": {
    "ADDRESSES": [
      {
        "ASSET_ID": 3,
        "ASSET_TAG": "tumblrtag301",
        "GATEWAY": "<IP_ADDRESS>",
        "ADDRESS": "<IP_ADDRESS>",
        "NETMASK": "<IP_ADDRESS>",
        "POOL": "DEV",
        "ID": 2
      }
    ]
  }
}

I agree with @byxorna that there is still a problem where start address is not specified, but I think that has been a bug from before these changes were made.  I'll open a different PR to try to address that problem.

LGTM for the sake of getting things back to a more sane state while we iron out the other details.

@davidblum - I'm going to merge this, but please let me know if you discover this reintroduces your old bug, or introduces any new bugs for you.

👍

@Primer42
Yes, this appears to cause a regression.

Was this reverted? Or can #446 get closed?


document new option for uncertainty in dynamic B0

New Simple_Lorenzen model discussed in https://github.com/nmfs-stock-synthesis/ss-test-models/issues/5 uses the new option for reporting uncertainty in dynamic B0
input: https://github.com/nmfs-stock-synthesis/ss-test-models/blob/main/models/Simple_Lorenzen/control.ss#L313
output: https://github.com/nmfs-stock-synthesis/ss-test-models/blob/main/models/Simple_Lorenzen/ss_summary.sso#L403-L407
I just made commit 9f0dcb7 in an attempt to describe this option. The new revised text looks like

...
and here...
...

@Rick-Methot-NOAA please let us know if there's more to add here other than the ")" that I forgot after "future options" in the final item.

Thanks @iantaylor-NOAA  for documenting this! Still want to:

[ ] Get or create a model that uses this feature to make sure the setup is parsable by SS
[ ] Add an example of using this feature to the helper spreadsheets

also added documentation for the Summary bio option also included in option 2 for reporting variance of derived quantities


Fixed broken import button

First ticket completed with Kobey. Did visual inspection to check and see if it works. Passed Unit test.

Just dawned on me... instead of adding a third-party library, let's try a compromise that does it the "Angular way," but isolates the warts.
Add this to the app.js file:
UHGroupingsApp.directive('fileModel', [ '$parse', function($parse) {
    return {
        restrict: 'A',
        link: function(scope, element, attrs) {
            var model = $parse(attrs.fileModel);
            var modelSetter = model.assign;

            element.bind('change', function() {
                scope.$apply(function() {
                    modelSetter(scope, element[0].files[0]);
                });
            });
        }
    };
} ]);

Then in the input tag for the html page, add the "file-model" attribute. E.g.,
<input type="file" file-model="somevariablename" ...


May need to add post-commit call back to loader

I strongly suspect that the Loader interface will need a post commit callback in order to support apache/incubator-fluo-recipes#123 and apache/incubator-fluo-recipes#124.  If something like Kafka or Nifi is initiating load transactions, then those system will need to know when those load transactions are successful.
This could be accomplished currently by executing individual transactions.  However using the LoaderExecutor is much more efficient at committing batches of transactions.

Another possible solution to this problem, would be to add an async commit.  This would allow transactions to get a callback when a commit completes.  This offer similar functionality as adding a post commit callback to the loader interface.  This would avoid having a thread wait for commit and allow many transactions to be working their way through the commit process.

I described a solution without describing the problem very well.  The problem this issue is trying to solve is getting good throughput from a source of continuous information that needs feedback on when that information was successfully processed by Fluo.  The LoaderExecutor gives good throughput for committing transactions, but lacks the feedback mechanism.
I was thinking about how to solve  this w/ the current 1.0.0 release.  One way would be to process batches with the loader executor.  For example process 10,000 transactions with the LoaderExecutor and then shut the LoaderExecutor down.  After its shut down, then feedback can be given to the information source that all 10,000 transactions completed.


typehole not working with angular?

I installed the vscode extension, but in quickfix menu, the 'add typehole' entry is missing. I'm trying this in an angular application, is this supposed to work with angular?

Typehole is supposed to work in any TS files as long as the files can be parsed by the TS compiler.
Code actions are available for typescript and typescriptreact language identifiers https://code.visualstudio.com/docs/languages/identifiers . This seems like a bug to me. What would be a good example Angular project for me to try and debug this?

ok, it seems to work now. i cannot reproduce it. got some failures that i have to manually install typehole, after 'ng add typehole' it worked. insanely helpful tool.
thanks for responding so fast anyway ^^

No worries at all, and I'm glad you find it helpful :) Let me know if other issues come up!


Update QueryWatcher.php

Move setting check before DB::listen, execution not required when setting disabled

The tests are failing, could you take a look at that?

Closing due to inactivity.


Does it work with factory or seeder?

Normal registration and login are working fine. But when I try to use UserSeeder/UserFactory it's not working. It gets stuck after one insert into the users table.

Maybe because you have not nullable love_ column in users table?

No that's already nullable. I tried to reproduce it with a new project. But it works fine.
Maybe there is some problem with observers in my project.
When I run withoutEvents it works.
Then I have run these commands.
php artisan love:register-reacters --model="App\Models\User"
php artisan love:register-reactants --model="App\Models\User"

BTW I'm using User model for both reacter and reactant.
If anyone has this problem please mention me again.

Damn, I have found the problem. At the same time, there was 2 observer running, my own UserObserver and Reacterable/Reactable Observer. Both tried to update the User model. That's why it got stuck.

Thanks for share it. Issue could be closed?

Yeah, sure.


skip flaky test

https://github.com/microsoft/vscode/issues/225678

hopefully fixed by https://github.com/microsoft/vscode/pull/225820 instead. The failure is more likely a side effect of another test.


'ed' characters appended to address bar search string

This isn't an extension issue as I have tested for that. When the default search engine is set to DuckDuckGo, ed characters are appended to the address bar search string.  This only happens when DuckDuckGo is the default search engine. For example, searching for NASA in the address bar will return the string nasaed in the resulting DuckDuckGo search box.

I've found the problem and it relates to the default DuckDuckGo query URL under: Privacy and security > Manage search engines. There's an 'ed' at the end of the Query URL which shouldn't be there. The workaround is to copy the DuckDuckGo Query URL, omitting the offending 'ed', and then 'Add' your own entry for DuckDuckGo using the copied URL and make your entry the default.


Docker container

Hello! I'm running a container that successfully compiles everything but when I try to see the cameras available using camera-ip-config -l it doesn't show up, whereas running it outside the container (on the actual machine) it works. Do you see any limitation on the way the cameras are discovered when using it from a docker container?
Thanks!

Maybe I need to expose a specific port on the container?

Ok, I answered my own question. Running the container using the parameter --net = "host" solves the issue. Probably because when using this parameter there's no need to expose specific ports, and the discovering process of the cameras probably uses a specific incoming port or even a random one?

Hi,
Sorry for the late reply.
Ports are random. Be it for discovery, configuration or streaming. Should you have multiple application that act independently from eachother you would see some conflicts there if they would all use the same ports.

Thanks!


URL not available for help on Datasphere for new connection for Google Big Query

Issue description
Hello,
I tried to establish a new datasphere connection for Google Big Query. The connection works but the help cannot be found. See https://help.sap.com/docs/page-not-found?url=https%3A%2F%2Fhelp.sap.com%2Fhttp.svc%2Foutputlink%3Fproductname%3DSAP_DATASPHERE%26projectname%3DDWC%25202023.24%2520-%2520In-App%2520Help%26deliverable%3De9275e9c7684454f9cf8b7c687848c64%26version%3D2023.24%26language%3Dde-DE%26state%3DPRODUCTION%26filepath%3Db9b5579054df48c39381d5b17286bf21.html%26transtype%3Dxhtml.body%26buildablemaploio%3D%26projectphio%3Dkat1696319849513%26dependantprojects%3Defa1696319835071%26source%3Dproductlink-webassistant
Best regards
Feedback Type (Optional)
content gaps
Page Title on SAP Help Portal (prefilled)
Upload Third-Party ODBC Drivers (Required for Data Flows)
Page URL on SAP Help Portal (prefilled)
https://help.sap.com/docs/SAP_DATASPHERE/9f804b8efa8043539289f42f372c4862/b9b5579054df48c39381d5b17286bf21.html?locale=en-US

Dear customer,
thank you for your feedback. We're investigating the issue and will get back to you soon.
Best Regards,
the SAP Datasphere User Assistance team

Dear customer,
the in-app help for Google Big Query connections has been revised. All links to Help Portal documentation should work. There is no direct link to https://help.sap.com/docs/SAP_DATASPHERE/9f804b8efa8043539289f42f372c4862/b9b5579054df48c39381d5b17286bf21.html?locale=en-US anymore but to the overall prerequisites described in https://help.sap.com/docs/SAP_DATASPHERE/9f804b8efa8043539289f42f372c4862/529cef1eee6a45a69ae4e51951718900.html

Thanks again for your feedback.
Best Regards,
the SAP Datasphere User Assistance team


Two problems

Hi,  nmred:
I am using your php kafka extension, Here is my question:
1, How to fetch only one message when consumer is running?
2, How to know that Message exists or not in the topic partition?

Not support fetch only one message, Can you talk about your specific needs?
You can reference example code https://github.com/weiboad/kafka-php/blob/master/example/Consumer.php#L24-L29

example:
if ($partition->getHighOffset() > $partition->getMessageOffset()) {
...... message exists
} else {
..... message not exists
}

First, consumer always start from last offset.
Now queue is just like [100, 101, 102, ...], and No. 100 is the last offset.
If function fetch() takes [100, 101, 102], last offset is changed to 103.
Luckily consumer is running very well, and that's ok. But Sometimes consumer has a long flow, and An error has occurred in one flow.
And processing message is nothing(dropped down or redo), and the consumer maybe crashed, So what about other unprocessed messages?
If fetch takes just one message, this situation will not happen, at least other unprocessed messages will not be affected.

By setting consumer maxbytes restrict fetch message, You can estimate the message size.
$consumer->setMaxBytes(102400);


Transfer any Domains

Please send a transfer code to<EMAIL_ADDRESS>

Krator does not currently own any domains.


Don't run CI on mdanalysis latest + latest python

Fixes #92 (I think)
This might need some discussion.
Currently CI will run all the versions that the develop version of MDAnalysis will support.
This will cause failures when it attempts to run a brand new version of Python that the last release of MDA doesn't support (for example Python 3.12 + MDAnalysis 2.6.1).
There are two options I can see out of this:

We just don't run the latest version of Python against the last release of MDAnalysis - this fix does this.
We split up the test step into two, a latest & development step. On the latest step we take the output of mdanalysis-compatible-python with the latest version of MDA, and the development the same python matrix as what we call currently.

Note: This will need a bit of work to grab out the latest version of MDA, it's not the end of the world but I'm unlikely to have much time to do this in the next couple of days given work requirements (indeed this is the last thing I can do today since I have to go back to my day job).

In all cases we're going to have to go to the MDAnalysis cookie-cutter using repos and fix this workflow, because right now all their CI is failing.
PR Checklist

[ ] Tests?
[ ] Docs?
[ ] CHANGELOG.md updated?
[ ] AUTHORS.md updated?
[ ] Issue raised/referenced?

In all cases we're going to have to go to the MDAnalysis cookie-cutter using repos and fix this workflow, because right now all their CI is failing.

Yeah this is going to be a hassle now and in the future -- when there's time I'd like to look into a bot or similar that can keep watch on changes to the cookiecutter and maybe open PRs with cherry-picked changes when we update cookie-related things.

In all cases we're going to have to go to the MDAnalysis cookie-cutter using repos and fix this workflow, because right now all their CI is failing.

A long term solution here is great, and I'm happy to have that discussion - indeed there is lots we can do.
However, the intent of that comment was "who takes responsibility for dealing with this today".
I don't want to spend time cycling on this too much, so I've already added the short term fix to PRs to transport-analysis, waterdynamics, pathsimsanalysis and mdaencore.
@ianmkenney @orbeckst @fiona-naughton @lilyminium If there are any other MDAKits that you know need updating, please either chime in here with the list of mdakits or spread the fix around.

However I think I prefer your Option 2 that you outlined there, so that we can keep testing develop with the newest and greatest. Unless I'm missing something, I don't see many downsides aside from additional CI complexity (maybe a slightly larger matrix?)

This is to be discussed elsewhere, but the current environment.yaml strategy won't work because it will always include MDAnalysis within it, so it won't work unless MDA is on conda-forge already. There are options I can think of but they aren't super user friendly / easy to fix. Very likely I'm missing something obvious though.
Honestly my long term opinion here is that, if we want to build our user community, we should, like numpy and scipy, take on the responsibility of having a Python 3.12 release as soon as possible. However that's a core library time & efforts allocation issue.

Sounds like a good insight, born from experience.
Do we have a document with our maintenance aspirations? At least internally we should have an idea what our goals are.

I don't think we've written down maintenance aspirations in that way before, although of course @IAlibay would know better here. There is a related maintenance SDG application but it focuses more on dev docs and CI/CD utilities.
Not to cut the discussion short, but I might merge this PR given the approvals just we can get CI back for now!

Thank you again @IAlibay for the fix!


Is there a way to compress rotated files?

Hi
Is there a way to configure Winston to produce gzipped rotated files? I could not see it in the documentation or plugins.

This landed in #606. Will go out in<EMAIL_ADDRESS>


[luau-performance] Backfill historical data

We want benchmark data for the before and after commits for the following points in time:

[ ] This commit includes an optimization that works around a x64 code generation regression in Visual Studio 2022, charts should show a double-digit percentage improvement in some specific benchmarks between this commit (release 501) and the previous commit (release 500)

https://github.com/Roblox/luau/blame/f2e6a8f4a57d4b1e92c1828dbf7632404237438c/VM/src/lvmexecute.cpp#L2421

[ ] This commit includes an optimization to tostring() that should show a double-digit percentage improvement in some specific benchmarks between this commit (release 509) and the previous commit (release 508)

https://github.com/Roblox/luau/commit/d50b0793257b39cd70f7bbf0057f37f718b1beb9

[ ] This commit includes an optimization that makes the binary-trees and qsort benchmark 5-25% faster on Apple M1 between this commit (release 507-pre) and the previous commit (release 506)

https://github.com/Roblox/luau/commit/f2e6a8f4a57d4b1e92c1828dbf7632404237438c

https://github.com/luau-lang/benchmark-data/pull/1
https://github.com/Roblox/luau/pull/581

Resolved by https://github.com/luau-lang/benchmark-data/pull/1
Resolved by #581


Cache groupby result in PandasDataset

Description of changes: On small datasets, this doesn't make much of a difference. On larger datasets such as M5, I observed a 10% slowdown at construction time, but then the same overhead is avoided when iterating the dataset over and over again.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Please tag this pr with at least one of these labels to make our release process faster: BREAKING, new feature, bug fix, other change, dev setup

I guess we don't really care about memory consumption?

I guess we don't really care about memory consumption?

We can worry about that when needed


use sonoff-debug also to change state

I need a simple script, without HASS, like sonoff-debug.py but also to change state of sonoff...

sorry not happening right now, you can copy the needed code from main __init__.py file if you want this feature.
in the feature i might be able to create a standalone sonoff library that could achieve what you want


I'm a newbie, Need help

Task 5.
Copy the body of 'getPattern()' to the 'task5()' function
and rewrite it in such a way that it matches '13 JUN 1992'.
Use the 'month' variable.
I cannot pass the test in "i_introduction  _5_String_Templates"
How do I pass this using getPattern() and ‘month’ variable?

Hi, CodingPapi! The corresponding documentation pages can help you to understand what language features can be used. The reference to the documentation is in the beginning of the task description. If you're desperately stuck with some task, you can use 'show answer' button to move on.


First round of modifications on ZIP227

As per the title, this PR does a first round of changes on ZIP 227.
Each commit does one change, so we can easily cherry pick/rebase to keep the relevant ones.

I'm a bit lost on notations (especially the use of math fonts). We seem to be using mathsf which makes sense, but sometimes we use the double backtick or simply backticks (e.g. for 'finalize' and 'notes').
(see screenshot enclosed).
Is there a convention somewhere?

I'm a bit lost on notations (especially the use of math fonts). We seem to be using mathsf which makes sense, but sometimes we use the double backtick or simply backticks (e.g. for 'finalize' and 'notes'). (see screenshot enclosed).
Is there a convention somewhere?

Looking at other ZIPs (ZIP 225 for example), it seems that table entries are denoted via double backticks (with the use of \mathtt if they appear in a math equation).

Thanks @vivek-arte, but then, why is notes used with single backticks?

You're right, the use of single backticks was confusing and unnecessary. I've tried to improve on those parts in PR#28, moving to double backticks for the table items.
The finalize is a tricky case for the reason you mentioned, there was a time when we didn't have a full byte and only had the bit in, which is why it originally was in double backticks. That was changed to using the flagIssuance for serialization purposes, but I didn't edit the finalize formatting.
I'm also wondering how strict we need to be about using double backticks only for table entries -- for example, in the above PR, I changed ik to use double backticks because we use it in the issuance bundle table. But then it felt jarring to have isk, the private key that corresponds to ik, in \mathsf format. So I changed isk to also use double backticks. Open to suggestions on how to handle this.
I'm not sure there is a single consistent choice throughout all the prior ZIPs, but if we pick a strict format and stick to it that would be good too. We should document it somewhere, probably in the issue #25 discussion. I'm not sure we should include it in the Rationale section of either ZIP, but we can bring it to the attention of the ZIP editors, and they could choose if they want to make these conventions uniform going ahead and so on.

As an update, also see this comment made by Daira on the isk change I was unsure about. That seems to give clarity on the convention we should use (and means isk should be moved back to mathsf).


[SUPPORT] Control file sizing during FULL_RECORD bootstrap mode

Tips before filing an issue

Have you gone through our FAQs? Yes

Join the mailing list to engage in conversations and get faster support at<EMAIL_ADDRESS>

If you have triaged this as a bug, then file an issue directly.

Describe the problem you faced
I want to bootstrap a table into Hudi. Size of the table is around 12 TB. The base path of the source table is in S3. Its a partitioned hive table and the average parquet file size is 2.5Gb.  I used the FULL_RECORD bootstrap mode using Spark for bootstrapping and it was successful.
However, the average file size of hudi table was around 120 Mb which aligns with the default which ended up creating 100K+ files. I am using S3 storage as the DFS. This made the read performance quite slow.
I am not using any table partitioning yet. I did set hoodie.parquet.max.file.size":<PHONE_NUMBER>, (~1.2Gb) but this configuration was completely ignored.
FAQs and File Sizing docs mainly talk about ways to adjust the file size while streaming data into Hudi.
How can I control the file size during the bootstrapping process itself?
I also read in the docs that -
A full record bootstrap is functionally equivalent to a bulk-insert.

Does that mean both are essentially the same. Is there any advantage of using one over the another? (Note: METADATA_ONLY does not work for our use-case)
And final thing - apart from controlling the file size, what other options can we tune to improve on the read performance?
Environment Description
Running it via EMR

Hudi version : 13.0

Spark version : 3.3

Storage (HDFS/S3/GCS..) : S3

Running on Docker? (yes/no) : no

@fenil25 bulk-insert operation doesn't handle the small file handling, that is why you see the file sizes equal to split size. Sp the total number of partitions is calculated as number_of_files * number_of_blocks_in_file.

One way to handle this case will be running clustering with proper configuration to achieve the correct size files.
The other way is to configure the spark configuration spark.sql.files.maxPartitionBytes while doing bulk-insert which is default 128 MB in spark.

Got it. Thanks @ad1happy2go 🙇
Are bulk_insert and full_record bootstrap modes the same then?

FULL_RECORD bootstrap internally uses the bulk_insert operation type.

@fenil25 Closing this. Please reopen if you have any more questions. Thanks.


Automated cherry pick of #3598: fix: 支持创建时指定多个安全组

Cherry pick of #3598 on release/2.11.
#3598: fix: 支持创建时指定多个安全组

Codecov Report

:exclamation: No coverage uploaded for pull request base (release/2.11@c68bec9). Click here to learn what that means.
The diff coverage is 0%.

@@              Coverage Diff               @@
##             release/2.11   #3601   +/-   ##
==============================================
  Coverage                ?   7.12%
==============================================
  Files                   ?     477
  Lines                   ?   77679
  Branches                ?       0
==============================================
  Hits                    ?    5536
  Misses                  ?   71675
  Partials                ?     468

Flag
Coverage Δ

#aFlag
7.12% <0%> (?)

Impacted Files
Coverage Δ

pkg/cloudcommon/cmdline/helper.go
46.36% <0%> (ø)

pkg/mcclient/options/servers.go
0% <0%> (ø)

pkg/compute/models/guests.go
0.63% <0%> (ø)

pkg/compute/guestdrivers/managedvirtual.go
0% <0%> (ø)

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 c68bec9...9e2e45d. Read the comment docs.

/lgtm

/lgtm

/approve

/approve


Add SFTP Support

Im just wondering, why you don't provide an SFTP storage class? Is there some reasons or was it not needed by anybody yet? Alternatively i could take a look at it and create a pull request, if this feature is wanted.

I think this issue can be closed: https://github.com/django-dbbackup/django-dbbackup/blob/master/dbbackup/storage/sftp_storage.py ?

Yes, the feature has been added :+1:  Any subsequent wishes or problems with the sftp storage should be reported elsewhere :)


Ability to provide certificate and key data directly

What was changed
This adds the ability to directly provide the certificate and private key values using two new flags:

--tls-cert-data (or TEMPORAL_TLS_CERT_DATA)
--tls-key-data (or TEMPORAL_TLS_KEY_DATA)

Why?
This allows for for use cases where secrets are stored in a vault app (like 1Password), and then injected in at runtime using the vault's CLI.
Checklist

Closes #253

How was this tested:
I'm unsure the best way to test this.  I noticed that the existing code in clientFactory.createTLSConfig that loads the certificate using file paths appears to not be directly tested.  I can extract the small bit of code that I added into an un-exported function and test it, but I question the value.
One other path I considered, and have almost working, is to add a test for NewClientFactory().SDKClient().  With this path, I could add a test for specifying the cert/key via the path or data flags. I'm unsure if you all want to go down this route.

Any docs updates needed?
Probably!  It would be nice for these new flags to be called out in the docs.

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

This effort no longer applies since the latest merge which rewrites most of the code


Support private docker registry for images

From @tamalsaha on November 22, 2017 5:4
Example: https://github.com/appscode/voyager/tree/master/chart/stable/voyager
--docker-registry=kubedb

Copied from original issue: kubedb/operator#138

[ ] Host all docker images in Kubedb docker hub org.
[ ] In cases where we are using official Docker images, pull/push those into KubeDB repo.
[ ] Main DB repo will not have any tag
[ ] Util images will be named -util

This will allow user's to run KubeDB in offline/airgapped cluster.

https://github.com/kubedb/apimachinery/pull/164

[ ] Image pull secrets
[ ] init flags to mount secret


implement transformation and projection stacks

this allows for separate transformation and projection stacks and addresses the core issue stated in https://github.com/raysan5/raylib/pull/2146

This is a good improvement of current implementation but a Matrix stack does seem a feature more aligned with legacy OpenGL style API than new graphics APIs... for the moment, I'm not merging this improvement.

This is a good improvement of current implementation but a Matrix stack does seem a feature more aligned with legacy OpenGL style API than new graphics APIs... for the moment, I'm not merging this improvement.

true, tho this is mainly to remain compatible with a core legacy OpenGL feature that is present when using raylib with legacy OpenGL but absent when using raylib with modern OpenGL
simply so RayLib can remain compatible with both legacy OpenGL and modern OpenGL without rewriting code (most modern GL users implement their own matrix stacks anyway so this just makes it easier)

I know... but I don't know how long the OpenGL 1.1 backend will be kept as an option. Current matrix implementation is not perfect it's probably more than enough for users targeting OpenGL 1.1 in 2022.

I know... but I don't know how long the OpenGL 1.1 backend will be kept as an option. Current matrix implementation is not perfect but it's probably more than enough for users targeting OpenGL 1.1 in 2022.

true, gl 1.1 is quite old

maybe the matrix stack can be optional?