Relative paths mounts in volumes renders incorrectly

Description
Mounting a relative path - such as ./mounted-folder - renders as mounted-folder.
Then when running docker-compose up I receive this error:
invalid mount config for type "bind": invalid mount path: 'mounted-folder' mount path must be absolute.
I would expect the source path to stay as is.
Steps to reproduce the issue:

My .dockerapp file

version: 0.1.0
name: test
---
version: "3.6"
services:
  hello:
    image: hashicorp/http-echo
    volumes:
    - ./mounted-folder:/mounted-folder

---
{}

Run docker app render

Describe the results you received:
version: "3.6"
services:
  hello:
    image: my-image
    volumes:
    - type: bind
      source: mounted-folder
      target: /mounted-folder

Describe the results you expected:
version: "3.6"
services:
  hello:
    image: my-image
    volumes:
    - type: bind
      source: ./mounted-folder
      target: /mounted-folder

Output of docker version:
Client: Docker Engine - Community
 Version:           19.03.1
 API version:       1.40
 Go version:        go1.12.5
 Git commit:        74b1e89
 Built:             Thu Jul 25 21:18:17 2019
 OS/Arch:           darwin/amd64
 Experimental:      true

Server: Docker Engine - Community
 Engine:
  Version:          19.03.1
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.12.5
  Git commit:       74b1e89
  Built:            Thu Jul 25 21:17:52 2019
  OS/Arch:          linux/amd64
  Experimental:     true
 containerd:
  Version:          v1.2.6
  GitCommit:        894b81a4b802e4eb2a91d1ce216b8817763c29fb
 runc:
  Version:          1.0.0-rc8
  GitCommit:        425e105d5a03fabd737a126ad93d62a9eeede87f
 docker-init:
  Version:          0.18.0
  GitCommit:        fec3683

Output of docker-app version:
Version:               v0.8.0
Git commit:            7eea32b7
Built:                 Thu Jul 25 21:26:00 2019
OS/Arch:               darwin/amd64
Experimental:          off
Renderers:             none
Invocation Base Image: docker/cnab-app-base:v0.8.0

Output of docker info:
Client:
 Debug Mode: false
 Plugins:
  app: Docker Application (Docker Inc., v0.8.0)
  buildx: Build with BuildKit (Docker Inc., v0.2.2-10-g3f18b65-tp-docker)

Server:
 Containers: 13
  Running: 4
  Paused: 0
  Stopped: 9
 Images: 41
 Server Version: 19.03.1
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Native Overlay Diff: true
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: active
  NodeID: sf6i0kaitvdk1oy9p8k9h1vf1
  Is Manager: true
  ClusterID: 044hk80wcl7rw968ijom7vi4t
  Managers: 1
  Nodes: 1
  Default Address Pool: <IP_ADDRESS>/8
  SubnetSize: 24
  Data Path Port: 4789
  Orchestration:
   Task History Retention Limit: 5
  Raft:
   Snapshot Interval: 10000
   Number of Old Snapshots to Retain: 0
   Heartbeat Tick: 1
   Election Tick: 10
  Dispatcher:
   Heartbeat Period: 5 seconds
  CA Configuration:
   Expiry Duration: 3 months
   Force Rotate: 0
  Autolock Managers: false
  Root Rotation In Progress: false
  Node Address: <IP_ADDRESS>
  Manager Addresses:
   <IP_ADDRESS>:2377
 Runtimes: runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 894b81a4b802e4eb2a91d1ce216b8817763c29fb
 runc version: 425e105d5a03fabd737a126ad93d62a9eeede87f
 init version: fec3683
 Security Options:
  seccomp
   Profile: default
 Kernel Version: 4.9.184-linuxkit
 Operating System: Docker Desktop
 OSType: linux
 Architecture: x86_64
 CPUs: 6
 Total Memory: 1.952GiB
 Name: docker-desktop
 ID: 4VMB:BMJ2:FKFI:G6WP:3FX5:NV67:4YIA:QJHH:LF3R:EUZB:Y7ZP:7FER
 Docker Root Dir: /var/lib/docker
 Debug Mode: true
  File Descriptors: 123
  Goroutines: 253
  System Time: 2019-07-29T11:42:02.253667702Z
  EventsListeners: 3
 HTTP Proxy: gateway.docker.internal:3128
 HTTPS Proxy: gateway.docker.internal:3129
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: true
 Insecure Registries:
  <IP_ADDRESS>/8
 Live Restore Enabled: false
 Product License: Community Engine

Hello @maxhr Thank you for reporting this issue.

We are addressing this issue among others on render, with #602 . I think it should fix this particular issue.
cc @aiordache

I was testing this issue with 0.9.0-zeta1.
Things has changed, but there are still things to clarify.
Having volume:
    volumes:
    - "./db_tisapi:/var/lib/postgresql/data"
    - "./db_tisapi_init:/docker-entrypoint-initdb.d"

rendering results in:
    volumes:
    - type: bind
      source: /cnab/app/ttt.dockerapp/db_tisapi
      target: /var/lib/postgresql/data
    - type: bind
      source: /cnab/app/ttt.dockerapp/db_tisapi_init
      target: /docker-entrypoint-initdb.d

so it ignores current directory and assumes, that the relative folder is relative to folder /cnab/app.
This makes rendering of docker-compose.yml not usable for docker-compose command.
Possible solutions:

skip: skip supporting docker app render for docker-compose using volumes bound to relative folder. Call this use case as out of scope for docker app.
render-mode: Introduce option --render-mode with options docker-compose and app. docker-compose would respect relative folders, app would assume relative folders to be relative to /cnab/app. Default render-mode would be app.
volumes-root: Introduce option --volumes-root defaulting to /cnab/app.

I would prefer the render-mode solution as it brings real value to docker-compose users allowing to parametrize the application as needed.


aiohttp / sniffio is unhappy with "--opt"

When I use granian with --opt, aiohttp's use of sniffio gets unhappy when trying to detect the async library, without --opt it works just fine. How I trigger this is by going to /docs in my FastAPI project, which produces an HTTP 500 - Internal Server Error with the below traceback.

Linux amd64
Python 3.13 with the project managed by uv + pyenv

[ERROR] Application callable raised an exception
Traceback (most recent call last):
  File "./discord_bot/.venv/lib/python3.13/site-packages/granian/asgi.py", line 118, in _http_logger
    rv = await _runner(scope, proto)
  File "./discord_bot/.venv/lib/python3.13/site-packages/fastapi/applications.py", line 1054, in __call__
    await super().__call__(scope, receive, send)
  File "./discord_bot/.venv/lib/python3.13/site-packages/starlette/applications.py", line 113, in __call__
    await self.middleware_stack(scope, receive, send)
  File "./discord_bot/.venv/lib/python3.13/site-packages/starlette/middleware/errors.py", line 177, in __call__
    response = await self.handler(request, exc)
  File "./discord_bot/main.py", line 148, in catch_all_handler
    await async_excepthook(*sys.exc_info())
  File "./discord_bot/main.py", line 56, in async_excepthook
    ryan: discord.User = await discord_client.fetch_user(
  File "./discord_bot/.venv/lib/python3.13/site-packages/discord/client.py", line 1804, in fetch_user
    data = await self.http.get_user(user_id)
  File "./discord_bot/.venv/lib/python3.13/site-packages/discord/http.py", line 286, in request
    async with self.__session.request(
  File "./discord_bot/.venv/lib/python3.13/site-packages/aiohttp/client.py", line 1359, in __aenter__
    self._resp: _RetType = await self._coro
  File "./discord_bot/.venv/lib/python3.13/site-packages/aiohttp/client.py", line 579, in _request
    with timer:
  File "./discord_bot/.venv/lib/python3.13/site-packages/aiohttp/helpers.py", line 712, in __enter__
    raise RuntimeError(
RuntimeError: Timeout context manager should be used inside a task
2024-11-30 09:39:34,432 - async_excepthook - ERROR: Exception in AsyncLibraryNotFoundError: unknown async library, or not in async context

Yeah, this falls into the same category of #387 and #323.
There's no plan to fix this: in fact I'm planning to just remove the --opt option at all given the actual performance gain in latest Python versions is somewhat unclear.
Gonna keep this opened until the option is removed.


The is_logging column of the aws_cloudtrail_trail table returns  when value is 'true'

Describe the bug
The value for the is_logging column seems to be incorrect. I noticed this when the aws compliance mod alarmed incorrectly on this query.
Steampipe version (steampipe -v)
steampipe version 0.12.0
Plugin version (steampipe plugin list)
+--------------------------------------------------+---------+--------------------------------------------------------------+
| Name                                             | Version | Connections                                                  |
+--------------------------------------------------+---------+--------------------------------------------------------------+
| hub.steampipe.io/plugins/turbot/aws@latest       | 0.46.0  | meta_connection,REDACTED,REDACTED,REDACTED |
| hub.steampipe.io/plugins/turbot/steampipe@latest | 0.2.0   | steampipe                                                    |
+--------------------------------------------------+---------+--------------------------------------------------------------+
To reproduce
run select * from aws_cloudtrail_trail, or a more targeted query to pull back information about whether a cloudtrail is currently logging, and compare that data to AWS CLI output or console information. Here's an example CLI command aws  cloudtrail get-trail-status --name MyTargetTrail --region us-east-1
Expected behavior
I expect the information about the logging status of a trail to be consistent across steampipe/CLI/Console.
Additional context
None

@cmd-ctrl-freq Appreciate trying out Steampipe
Sorry to see this reported inconsistent; er are checking this one to replicate and will update you soon.
If you wish, feel free to send PR as well

Hello @cmd-ctrl-freq, while digging into the above issue, we realised that the issue is deep-rooted in the AWS plugin.
Thank you for reporting this, I have opened another issue in the AWS plugin here.
Please let us know if you run into more issues.

hello @cmd-ctrl-freq , the issue has now been resolved and it is available in aws plugin version 0.62.0. Please let us know if you still face issues. 👍


Brace-Initialization Fails with json::parse and Key Access on Linux

Description
On Linux, using brace-initialized literals with json::parse or accessing JSON keys with auto results in unexpected behavior or compile-time errors. This issue does not occur on other platforms and requires modifying code to use assignment (=) syntax instead of brace initialization. This is a non-issue for MacOS and iOS. I have not tested Windows.
Reproduction steps

Create a JSON string, e.g., std::string str = "{"key": "value"}";
Attempt to parse it using auto parsed{json::parse(str)};
Attempt to access a key using auto key{parsed["key"]};

Expected vs. actual results
The code should run on Linux like it does on MacOS and iOS, allowing the use of brace-initialized literals ({}) for json::parse and key access with JSON. It seems to be making an array only on Linux when using {} initialization.
Minimal code example
#include <nlohmann/json.hpp>
#include <string>

using json = nlohmann::json;

int main() {
    std::string str = "{\"key\": \"value\"}";
    auto parsed{json::parse(str)};   // Fails on Linux
    auto key{parsed["key"]};         // Fails on Linux
    return 0;
}

Error messages
On Linux, the code throws exception when using brace-initialization {}, and errors arise specifically in these cases. Changing to assignment (=) syntax for both parsing and key access, like auto parsed = json::parse(str);, works as expected.

Compiler and operating system
g++14 with C++20
Library version
Latest release
Validation

[ ] The bug also occurs if the latest version from the develop branch is used.
[ ] I can successfully compile and run the unit tests.

Have you read the first FAQ?
https://json.nlohmann.me/home/faq/


feat(back/api): upload  photos request handling

Context
API should let authenticated users to upload some photos by upload file form created in dashboard.
Solution(s)
Use ModelViewSet / Serializer / Model to push data from formData in frontend into the database
Additional informations
api route is : /api/v1/upload/
ℹ The actions provided by the ModelViewSet class are .list(), .retrieve(), .create(), .update(), .partial_update(), and .destroy()

Duplicate and already done


Cupertino NavBar default Close text shouldn't scale with the font

Problem
If you look into the native iOS NavBar texts (such as Close, Edit, and so on) those won't scale with the font settings (thus having textScaleFactor: 1.0).
Currently, the Close button from the bottom navigation route, is being able to scale and can't have its property overriden unless you explicitly create it yourself the leading widget). This will either add a lot of boilerplate if you want to provide the best native experience possible; or make the Close button smaller/bigger than the others across the system UI.
This should also be considered to the AppBar title and action buttons (both text and icon).
Solution
A simple (and correct) solution would be to set the CupertinoButton's textScaleFactor to 1.0 in the default leadingContent of the NavBar.
leadingContent = CupertinoButton(
        child: const Text(
          'Close',
          textScaleFactor: 1.0,
        ),
        padding: EdgeInsets.zero,
        onPressed: () { route.navigator.maybePop(); },
      );

Edit: I already PR'd a solution with #35200.

@miguelpruivo thank you for pointing that out! Looks like nav bars, tab bars and pickers are exempt from the regular "text size" setting or the accessibility "larger text" setting.


Can wrap-multilines work with no-extra-parens turned on?

When no-extra-parens is enabled the following returns a warning:
    render: function () {
        return (

                Hello

        )
    },

Is it possible for these two rules to co-exist?

As I responded for a similar issue:

Sadly, as far as I know, a plugin don't have the power to silent an error reported by an ESLint rule, the only way we have to do something approaching is to replicate the ESLint rule, "patch" it to fit our needs and use it instead of the ESLint one. It is not very clean and it can be time consuming to maintain the rule in sync with the ESLint one.

So, currently we cannot have these two rules enabled :(

No worries. Thanks for the quick response and creating this repo!

https://github.com/eslint/eslint/issues/3034 covers this issue as well. One tip suggested by @michaelficarra is to use the following form:
    render: function () {
        return 0,

                Hello

    },

It's a little weird, but it silences the no-extra-parens error and maintains the balanced line spacing.

It looks like this was fixed in eslint/eslint#7926 (v3.14.0+), you can now do the following;
{
  "rules": {
    "no-extra-parens": [ "warn", { "ignoreJSX": "none|all|multi-line|single-line" } ]
  }
}

In the case of this issue, it sounds like you want multi-line;

allows extra parentheses around no/all/multi-line/single-line JSX components.


Add memberNames attr identifier to enhance kind="enum"

By default, kind="enum" uses a CamelCasing-ish strategy on values to decide on member names to correspond to those values. This is a nice default, but it doesn't help when the values of the disjunct are numerics instead of strings, or if the user just plain wants some other pattern.
For that, we need cuetsy to support another attribute identifier. What i did here should work fine - a memberNames attr identifier, which expects a |-delimited list of strings, equal in count to the number of elements in the disjunction. memberNames will be required if the disjunction contains any numeric values.

CUE
TS

package cuetsy

AutoCamel: "foo" | "bar" @cuetsy(kind="enum")
ManualCamel: "foo" | "bar" @cuetsy(kind="enum",memberNames="Foo|Bar")
Arbitrary: "foo" | "bar" @cuetsy(kind="enum",memberNames="Zip|Zap")
Numeric: 0 | 1 | 2 @cuetsy(kind="enum",memberNames="Zero|One|Two")
// TS authors: "you can do this, but it's probably silly, maybe don't?"
Heterogeneous: 0 | 1 | "foo" @cuetsy(kind="enum",memberNames="Zero|One|Foo")
ErrMismatchLen: "a" | "b" | "c" @cuetsy(kind="enum",memberNames="a|b")
ErrNamelessNumerics: 0 | 1 | 2 @cuetsy(kind="enum")

enum AutoCamel {
  Foo = "foo",
  Bar = "bar",
}
enum ManualCamel {
  Foo = "foo",
  Bar = "bar",
}
enum Arbitrary {
  Zip = "foo",
  Zap = "bar",
}
enum Numeric {
  Zero = 0,
  One = 1,
  Two = 2,
}
enum Heterogeneous {
  Zero = 0,
  One = 1,
  Foo = "foo",
}

@ying-jeanne this might be better to work on than trying to dynamically inject the cuetsy attributes

@ryantxu asked about comments over in #14. i've updated the OP accordingly.

// TS authors: "you can do this, but it's probably silly, maybe don't?"
Heterogeneous: 0 | 1 | "foo" @cuetsy(kind="enum",memberNames="Zero|One|Foo")

Lets not promote that one :)
The "number" case is an artifact of defining an enum directly -- it translates to numbers, but I think is something we should avoid generally.  (and need good ways to map from numbers to strings in migrations)

Fair enough, removed the heterogeneous case :) It'll still be supported, necessarily, but no need to promote it.
Is the concern about numeric enums specific to what we want to define as best practices in Grafana, or does it extend to TS more widely?

Make sense, I could take over this request, I don't have right to assign myself to the issue somehow :).

assigned!


yabridge, yabridgectl: 3.0.2 -> 3.1.0

Motivation for this change
Upgrade to the latest version: https://github.com/robbert-vdh/yabridge/releases/tag/3.1.0
Things done

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

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

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

Result of nixpkgs-review pr 119718 at 2814a535 run on x86_64-linux 1

2 packages built successfully:

yabridge
yabridgectl

1 suggestion:

warning: missing-phase-hooks
installPhase should probably contain runHook preInstall and runHook postInstall.
Near pkgs/tools/audio/yabridge/default.nix:112:3:
    |
112 |   installPhase = ''
    |   ^


Unable to parse chrome Cache

When i run
python chromagnonCache.py ~/.cache/google-chrome/Default/Cache/
I get Invalid Chrome cache file. (Under the above directory there is index file.)
Traceback (most recent call last):
File "chromagnonCache.py", line 103, in
main()
File "chromagnonCache.py", line 89, in main
args.getattribute("Cache Directory"), args.u)
File "/home/<>/<>/Chromagnon/chromagnon/cacheParse.py", line 58, in parse
cacheBlock = CacheBlock(path + "index")
File "/home/<>/<>/Chromagnon/chromagnon/cacheBlock.py", line 85, in init
raise Exception("Invalid Chrome Cache File")
Exception: Invalid Chrome Cache File

When i printed the magicnumber, the output is:
2809289776

I believe this is due to chrome code switching to "Very Simple HTTP Cache Backend" by default.
from the current index file, I was able to observe a magic that matches 0xfcfb6d1ba7725c30 which is the updated magic signature of the format.
Unfortunately I haven't got more time to look into parsing it, I
Refs:

https://www.chromium.org/developers/design-documents/network-stack/disk-cache/very-simple-backend
https://github.com/chromium/chromium/blob/4f9c35c3635144e2c2d1b87d09cbcf076d138b66/net/tools/cachetool/cachetool.cc
https://github.com/chromium/chromium/blob/2ca8c5037021c9d2ecc00b787d58a31ed8fc8bcb/net/disk_cache/simple/simple_entry_format.h

As noted in the Chromium source, disk cache implementation, disk caches use different implementations on Windows/Linux OS.
Trying to export cache with this project will fail on Linux (because it uses simple cache), however it still works on Windows.


⚠ Bofrost.at has degraded performance

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

HTTP code: 200
Response time: 1904 ms

Resolved: Bofrost.at performance has improved in faa77ab after 6 minutes.


Refactor cursors API and implement joined inventory.

@aviau | @mlefebvre
Big PR with a few core changes and a complete rewrite of the join inventory.
This new one is pretty much a Saturn inside Saturn allowing to create new inventories from a root inventories and running them concurrently. The challenge has been handling the cursors and scheduling. For now I tested the simplest case of max_concurrency=1 (So same support as we had before) and no handling on partial cursor progress. More to come soon.


Bluetooth: controller: Moves lll_adv.h to common

Moved the lll_adv.h header from the nordic subdirectory
to the common ll_sw directory. This will allow the higher layers
to include the ull_adv_types.h file, as that depends on the structures in
lll_adv.h. This also puts the files next to the other lll_x.h headers.
Signed-off-by: Emil Gydesen<EMAIL_ADDRESS>

lll_adv.h is not a common header file, it's vendor specific header file as the lll_adv structure can contain vendor specific fields needed by that lll implementation.
What do you mean by "allow the higher layers"? What problem is it that your are trying to solve? Many of the ull_*.c files include lll_adv.h before including ull_adv_types.h.

@thoh-ot The ull_adv_types.h depend on the lll_adv struct to be defined. E.g. hci.c cannot include ull_adv_types.h for that reason. By higher layer I'm specifically talking about the hci (controller) layer.
I was also under the understanding that the lll_xxx.h files were vendor specific and not common, but lll_scan.h, lll_conn.h and lll_sync.h files are all in the common ll_sw directory.

It seems that when we did the reorganization of the code, we (Oticon) only had a need to have a custom lll_adv.h and lll_xxx.h header files where forgotten and not moved. Non the less our lll_adv.h is vendor specific so we cannot move lll_adv.h to common.
Why is it impossible to include lll_adv.h (and all of it's dependencies) in hci.c before including ull_adv_types.h?

It seems that when we did the reorganization of the code, we (Oticon) only had a need to have a custom lll_adv.h and the other lll_xxx.h header files where forgotten and not moved. Non the less our lll_adv.h is vendor specific so we cannot move lll_adv.h to common.
Why is it impossible to include lll_adv.h (and all of it's dependencies) in hci.c before including ull_adv_types.h?

@thoh-ot I'm sorry for not disclosing that in the PR: ull_adv_types.h contains references to struct lll_adv which is defined in lll_adv.h.
I'd be very open for any ideas on how we can expose the ULL adv types, without moving the lll_adv.h. Perhaps this is part of a larger problem of consistency in the file structure of the controller, if we treat adv types different than scan types.
I suggest that we take this discussion tomorrow at our weekly meeting.

It's possible to include the lll_adv.h file without the full path, so that it'll include the right one without having to move this. Closing.


[INLONG-2220] move dataproxy-sdk to inlong-sdk

Title Name: [INLONG-XYZ][component] Title of the pull request
where XYZ should be replaced by the actual issue number.
Fixes #2220
Motivation
Explain here the context, and why you're making that change. What is the problem you're trying to solve.
Modifications
Describe the modifications you've done.
Verifying this change

[ ] Make sure that the change passes the CI checks.

(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end deployment with large payloads (10MB)
Extended integration test for recovery after broker failure

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)
If a feature is not applicable for documentation, explain why?
If a feature is not documented yet in this PR, please create a followup issue for adding the documentation

Codecov Report

Merging #2221 (a46a48d) into master (75a21cd) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head a46a48d differs from pull request most recent head 187d8bd. Consider uploading reports for the commit 187d8bd to get more accurate results

@@            Coverage Diff            @@
##             master    #2221   +/-   ##
=========================================
  Coverage     12.58%   12.58%
  Complexity     1208     1208
=========================================
  Files           417      417
  Lines         35735    35735
  Branches       5590     5590
=========================================
  Hits           4499     4499
  Misses        30435    30435
  Partials        801      801

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 75a21cd...187d8bd. Read the comment docs.


Pilot parameter to MergeHistograms and MergeShiftedHistograms

The "pilot" parameter is also added to "prefer_cli", allowing to set the pilot e.g. when creating datacards:
law run cf.CreateDatacards --version v1 --workflow htcondor --workers 4 --cf.MergeShiftedHistograms-pilot
With this minor change, the time spent to build the dependency tree when creating datacards is reduced to a few seconds and the number of workflows that needs to be submitted is reduced significantly.
(If you prefer to submit a workflow for each systematic uncertainty, you can use the --cf.MergeHistograms-pilot instead)

I performed a test on this branch with the pilot parameter set and no requirements being previously request. As you already guessed, all workflows up to the heavy processing in ProduceColumns, MLTraining, MLEvaluation, etc. are bypassed, which leads to 1 htcondor job eventually run all upstreams task.
I don't think we should go with this approach, but we should follow-up on accelerating the initial task graph building.


Implements KDTree::RangeSearch method.

Summary
Part of https://github.com/maliput/maliput/issues/516

Implements KDTree::RangeSearch method.

@agalbachicar Ready to review. I added some comments/reviews for debating.


Adding parcel bundler

Summary
Jest is supported and can be integrated with parcel-bundler for testing of the applications and that was not listed under documentation so added that.
Test plan
Changes were made inside the documentation part so there were no changes done in the codebase.
However, the installation code for parcel-bundler follows:
npm install -g parcel-bundler
or
yarn add parcel-bundler

Can you add the info to https://github.com/facebook/jest/blob/master/docs/GettingStarted.md as well? Then we can merge 🙂

Sure

@SimenB added details inside GettingStarted.md file kindly review it.

Thanks!


Is this production ready?

Guessing from contribution activity that it's not, but just wanted to check to be sure.. Hoping to use Google SSO in an app Im working on

Same here! I would love to use this in an upcoming project. Any idea how "production ready" it is?

@asleepingpanda and @philbaker4 thanks for asking it.
I'm actively working on this libraries on my fork, seeking for "production readiness". I basically refactored everything, bumped minimum targets to iOS 13 and macOS 10.15 and refactored to async/await only, cause that what make sense to the projects I'll be using this.
Once it's ready I'll try to PR it into the supabase-community repos if everyone accepts it.
You can find them in the links below, the Auth and Database is quite ready, the other ones I'm still working on them, but would be awesome if you could use them and give me some feedback on whats needs to be fixed.
https://github.com/grsouza/supabase-swift
https://github.com/grsouza/gotrue-swift
https://github.com/grsouza/postgrest-swift
https://github.com/grsouza/storage-swift
https://github.com/grsouza/realtime-swift

Same here. Is there any roadmap to deliver a production ready version 1?


Pass empty Configuration in DelegatingCluster

Otherwise, it causes NPE at https://github.com/yugabyte/cassandra-java-driver/blob/3.8.0-yb-x/driver-core/src/main/java/com/datastax/driver/core/Cluster.java#L1620

@tedyu @nmalladi Could you review this PR when you have time?

@tedyu @nmalladi Gentle reminder.

Seems reasonable to me.
@nchandrappa
What do you think ?

Hello @ebyhr, Thanks for submitting the PR.
You have mentioned the code fix is to prevent an NPE, is it possible to define a test case scenario when NPE can occur.
Also, DelegatingCluster is an abstract class, and based on the DelegatingClusterIntegrationTest super constructor is not getting invoked.  can you please provide the requested details before merging the PR?
Thanks,
Nikhil

Here is the test case that fails before this change and succeeds after that.
import static org.testng.Assert.assertNotNull;

import org.testng.annotations.Test;

public class DelegateClusterTest {
  @Test(groups = "short")
  public void should_not_throw_null_pointer_exception() {
    Cluster cluster = Cluster.builder().addContactPoints("localhost").build();
    SimpleDelegatingCluster delegatingCluster = new SimpleDelegatingCluster(cluster);
    assertNotNull(delegatingCluster);
  }

  private static class SimpleDelegatingCluster extends DelegatingCluster {
    private final Cluster cluster;

    SimpleDelegatingCluster(Cluster cluster) {
      this.cluster = cluster;
    }

    @Override
    protected Cluster delegate() {
      return cluster;
    }
  }
}

Thanks for providing the testcase @ebyhr.  Code fix looks good.


Update FHIRPersistenceJDBCImpl.java

searchHelper.getSearchParameter might return null, and constructure of JDBCParameterBuildingVisitor needs searchParameter. Added new control For checking null reference and create a useful log entry.
Signed-off-by: Berkant Karduman<EMAIL_ADDRESS>

Thanks  Berkant.  Can you share what is the current behavior if we hit this case (composite search parameter where it references a component that doesn't exist)?

Thanks Berkant. Can you share what is the current behavior if we hit this case (composite search parameter where it references a component that doesn't exist)?

Throws  nullpointerexception with out details like below.  We can add some details to log entry .
[10/7/22, 11:23:56:321 TRT] 00000033 FHIRPersisten E   Unexpected error while performing a create operation  java.lang.NullPointerException
	at org.linuxforhealth.fhir.persistence.jdbc.util.JDBCParameterBuildingVisitor.<init>(JDBCParameterBuildingVisitor.java:116)


Mac Catalyst Support

Hi All,
Is it possible to get this library to work on Mac using Mac Catalyst?
'SecAddSharedWebCredential' is unavailable on macCatalyst.
Thanks!

Just co-signing on this one. I noticed the swift version was already patched for catalyst, and im hoping for an objc update 🙏

Bumping for updates, thanks!


Extract audio after media is imported

Why is this change needed?

The app requires the audio of the imported media to be available for use.

Some context

Before this PR audio extract was just a function being called when the app started (this was a demo when Patrick and I worked on that initial feature)

What did I change?

I changed the implementation the extractAudio function which now takes in a project as input rather than (simply because the project object has the fields that are required by the method at that stage).
Now saves the extracted audio under mlvet/extractedAudio/<project-id>.wav

I used the project id as the name for the audio file instead of project name since it is unique and we will never have to deal with project id changing

reviewers
Justin, because he brought this up during the SA meeting + his work depends on it
Kate, because she also works on the transcription team
Dan, because i've never had him in any of my PR's before

Awesome work Mutaz! Just a quick question (which is maybe looking too far ahead but if we can come up with a solution now I think it will save time down the road) - how will this work going forwards if there is more than one media file associated with a project? I haven't looked into exactly how that would work in terms of storage within the project file structure, but if the audio file name is based on the project ID I think that could be problematic for projects with multiple media files down the line as you wouldn't know which media file the audio is referring to. The only reason for mentioning it is it may mean any projects created with the MVP won't work in a later release, although not sure if that's actually a problem.

@kateahyde

how will this work going forwards if there is more than one media file associated with a project?

If we have more than 1 audio file per project then this approach will not work.
To accommodate for more than 1 audio file we could create a directory under extractedAudio using the uuid. e.g. extractedAudio/<project id>/audio1.wav or extractedAudio/<project id>/<media name>.wav
I think this is enough for the MVP however, we could (easily) implement the method for multiple audio sources now but we just 1 one.

Very fair @Taz17 I wasn't sure what had been decided for the project object so thought it would be worth asking in case it was worth pre-empting the change. In some ways I think it'd be great if we could use an array/list so that it will barely require any changes to have multiple files, but if it's already been implemented in the project object and given no-one will actually be using the MVP and have existing projects that won't work with the updated version, I think it's reasonable to keep it to 1 for now.


sops: 3.8.1 -> 3.9.0

Description of changes

https://github.com/getsops/sops/compare/v3.8.1...v3.9.0
https://github.com/getsops/sops/blob/v3.9.0/CHANGELOG.rst#390
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

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

2 packages built:

kubernetes-helmPlugins.helm-secrets
sops


Pyrra UI Detail page grouping doesn't work in v0.6.0

It came to my attention that the detail page is slightly broken right now when it comes to SLOs that use grouping.
Instead of querying for sum by(code) (rate(http_requests_total{handler="/api/v1/metadata"}[5m])) or sum by(code) (rate(http_requests_total{handler="/api/v1/series"}[5m])) we don't merge the grouping into the label matchers and only query for sum by(code) (rate(http_requests_total{}[5m])).
This is a bug that was introduced by moving from querying Prometheus through a proxy in the backend to querying Prometheus more directly (still through a proxy but essentially the same API) in v0.6.0.
Right now, I'm planning to fix this as soon as possible to unblock people who want to upgrade to v0.6.

Turns out this was a false alarm. The only indicator type I've seen this now for is the newly create (unreleased) native histograms latency type. 😬


Config for text values + formatting

hello could you add text editing to the config for possible translations and changing the color of the text?

Done in 1.2.0

and Empty hand message ?

Oh sorry I forgot about the failure message
and yes thats the only way to do it

Done in 1.2.1

you are super fast in support I appreciate it.. after today testing everything works great but I encountered a problem with the fact that in the config can not color player_name and item_name .. after coloring they remain in the chat white

How did you try to color them

chatMessage=§8§l[§c§li§8§l] §6%player:displayname% §ezaflexil s §6%itemflexer:item%

Seems like an issue with the API im using, cant do anything about it sorry


Provide a flag to override configuration values at runtime

I reckon that using the env() function you can already achieve most of it actually. closing it for now, will reopen if we feel it is necessary.


Introduce single error code for bad input data in ARIA, Camellia and Blowfish modules

This PR introduces new error codes MBEDTLS_ERR_{ARIA|BLOWFISH|CAMELLIA}_BAD_INPUT_DATA to be returned on any kind of bad input data. At the same time, it deprecates the more specific error codes MBEDTLS_ERR_{ARIA|BLOWFISH|CAMELLIA}_INVALID_{KEY|INPUT}_LENGTH in favor of this new error code and replaces their use throughout the library and tests.

Thanks @RonEld for the review! The ChangeLog formatting was deliberate to keep the lines short, but I'm open to change, however waiting for @sbutcher-arm's feedback first.
I fixed the mentioning of the deprecated error constants in the documentation. I didn't make any further corrections, because the parameter validation PRs significantly improve the documentation.

@Patater - I think you'll appreciate reviewing this, as it defines how we deprecate constants now.

This is failing tests/scripts/check-names.sh. Marking as 'needs: rework'.

@sbutcher-arm @RonEld This is due to the rigidity of check-names.sh which cannot handle the __attribute__((deprecated)) in the typedef of mbedtls_deprecated_{numeric|string}_constant_t. I've pushed a commit circumventing this problem by temporarily using MBEDTLS_DEPRECATED in place of __attribute__((deprecated)). However, I kept the decision of not exporting the latter, but instead #undefining it immediately after use, because exporting it would require changing all header files which temporarily define and use it, too, and I want to avoid that in this PR.
@RonEld @sbutcher-arm Please re-review.

@sbutcher-arm @Patater After this PR is merged, I am going to deprecate all the existing module errors that were replaced with MBEDTLS_ERR_PLATFORM_XXX.

I checked with both MBEDTLS_DEPRECATED_WARNING and MBEDTLS_DEPRECATED_REMOVED unset, and generate_errors.pl doesn't fail. In addition, the deprecated errors were not added in errors.c.
I will approve this PR, once my comments about same value errors are addressed

@hanno-arm @sbutcher-arm I have serious reservations about backwards compatibility here. To me this looks like an API break. Imagine code going like
ret = mbedtls_aria_xxx();
switch( ret ) {
    case MBEDTLS_ERR_ARIA_INVALID_INPUT_LENGTH:
         puts("bad input length");
    case MBEDTLS_ERR_ARIA_INVALID_KEY_LENGTH:
         puts("bad key length");
    case 0:
        puts("success");
    default:
        puts("unexpected error");
}

We're changing the observable behaviour of this code.

@mpg This is why we are deprecating the errors, and not removing them altogether.
You example is valid for any other function call we deprecate.

@RonEld No, we must not change observable behaviour even when deprecating parts of the API.
In this case, I see no option than restricting the deprecation to a single error code. I'll do the corresponding rework.

@RonEld The point is that we must not use the deprecated constants anymore, hence return the single new one in place of the two now deprecated ones. So two previously distinguishable situations are now no longer distinguishable. That's an API break.
I'll restrict deprecation to a single error code per module.

@hanno-arm I disagree.
For example, using the deprecated function mbedtls_sha512() in an application:
ret = mbedtls_sha512()...

If MBEDTLS_DEPRECATED_REMOVED is defined, then there is a compilation error.
If it is defined and MBEDTLS_DEPRECATED_WARNING , you'll get a deprecation warning
If both are undefined, then everything works as expected.
The same with example @mpg showed, except the fact that there are two errors with same value

@RonEld @mpg @sbutcher-arm Please re-review.

If both are undefined, then everything works as expected.

No, it doesn't, that's the point, because functions return the same error where the previously returned different ones.

I see your point
In this case, we should consider a different way to deprecate constants, that will not have this limitation

At least we should add comments to these errors, that they are expected to be removed in later releases

@RonEld What would users take away from such a comment? I think it would be more confusing than helpful.

@hanno-arm

What would users take away from such a comment? I think it would be more confusing than helpful.

The users will know they should modify their code, and remove their usage of the deprecated errors.
Perhaps we should just remove the error codes altogether, which will break ABI and compilation

@mpg said:

I have serious reservations about backwards compatibility here. To me this looks like an API break.

This isn't without precedent. We have changed before the error codes emitted in error conditions, where previously an error would return x, we've changed it to return y.
Errors are errors, and it should be possible to differentiate them by the class of error, but fundamentally, we're not breaking the API so much as the ABI, and only in certain error conditions, and in this case, the issue isn't a runtime fault (such as resource unavailable), but most likely a programmatic error, that can only be recovered by restart, and will most commonly be used for debugging, not for runtime error handling.
Therefore I was comfortable with the previous PR as it was.
Having said that, I don't have a problem with the new change, and I see no strong reason to revert back to the way we did it before. I'm just making the point that we fixed something I wasn't convinced needed fixing.
So, approving the PR.
@Patater / @RonEld - Can you also approve, given this is defining how we deprecate constants?

@sbutcher-arm  done

@sbutcher-arm

Having said that, I don't have a problem with the new change, and I see no strong reason to revert back to the way we did it before. I'm just making the point that we fixed something I wasn't convinced needed fixing.

Point taken. Perhaps we erred a bit too much on the safe side here, but OTOH I don't see much harm in it (except the time spent discussing and reworking).

@Patater @sbutcher-arm @mpg @RonEld Please re-review.

CI failure is only FreeBSD timing-suite, a known issue.


Clear all data on model , if API return as empty

Fix clear data on the model ,
if API response from response is return as empty data.

@mean-cj Thank you so much for the PR!
But I would like to discuss with this feature a bit more. I think maybe it's better to add an option to define which Vuex ORM method should be used on persistent. Because if you pass an empty array to Vuex ORM insert method, it will do nothing (current behavior). And sometimes it's desired too.
So how about adding these options
persistBy
insert
create
insertOrUpdate
update
delete
persistBy method defines what method should be used as a default.
User.api().get('/users', {
  persistBy: 'create' // Default is `insertOrUpdate`
})

// Is equal to.
User.create({ data })

Other options work as same as Vuex ORM persistent methods.
User.api().get('/users', {
  insert: ['posts']
})

// Is equal to.
User.create({ data, insert: ['posts'] })

Hello @kiaking
Thank you so much for your answer.
I think clear all data on the model is better than define persistBy
because it make sense , if ajax response data is empty.
Example 1 : When i delete final id
Item.api().delete('/delete/item/${id}')
the last response data is empty, clear data on the model
Example 2: if other device have been fetch data
if ajax response data is empty clear all data on the model

today i will found after fetch data from api()
the data on model not sync or not auto delete data id
if the id is not exists on API response
API Response : Item.fetch()
[  {id:1 , name:'aaaaa'}, {id:3 , name:'cccc'} ] ]
Example My PC
Current Item Model have been data
[  {id:1 , name:'aaaaa'}, {id:2 , name:'bbbb'} ] ]
Call Item.all() have response
[  {id:1 , name:'aaaaa'}, {id:2 , name:'bbbb'} , {id:3 , name:'cccc'} ] ]
item id=2 is not delete
i think create "sync" variable for enable sync mode
use for model sync all data from api response
User.api().fetch('/users', {
sync: true
})
if (config.sync || !data || data.length === 0) {
this.model.deleteAll()
}

idea override option work only return all data.
add refresh method is better , use for sync between api with model
model.api().refresh()
  /**
   * Perform a refresh request.
   */
  refresh(url: string, config: Config = {}): Promise<Response> {
    this.model.deleteAll()
    return this.request({ method: 'get', url, ...config })
  }

Yeah, I like the idea of having an override or a sync option. One thing to consider is what we do with relationships.
Let's say a user wants to fetch User. If the api response only contains users records, it would be safe to delete all users when the override option is set to true.
But if the user response could contain relationships, for example, posts records as well, it would be hard to find out what post record should be deleted.
I don't think there is an easy way to handle this situation. Therefore, I think it would be a bit more intuitive to have options for users to choose what Vuex ORM persistent method to use (create, insert, etc.). Because the override option is essentially the same as the create method on Vuex ORM Core.
What do you think?

Hello @kiaking
I agree with you , i found problem with relation
How can i do make the sync() function on model
Example
this.sync().hasMany(Comment, 'post_id')
this.sync().get()
this.sync().post()
when i will use the sync()
call model.deleteAll() before sync from api response.
What do you think?

I add two function to @vuex-orm\core\src\model\Model.ts
  static sync(): any {
    this.dispatch('deleteAll')
    return this
  }

  $sync(): any {
    this.$dispatch('deleteAll')
    return this
  }

but doesn't work because when i call function on api() the model call sync() every time.
  static fields = () => {
    return {
      items: this.hasMany(PosItem.sync(), 'order_id')
    }
  }

If we would like to delete all relationships and recreate everything with API response, we could simply iterate through fields and delete all records.
function persistResponseData (response: AxiosResponse, config: Config): Promise<any> {
  const fields = this.model.fields()

  Object.keys(fields).forEach((name) => {
    const related = this.model.relation(name)

    related && related.deleteAll()
  })

  return this.model.insertOrUpdate({
    data: this.getDataFromResponse(response, config)
  })
}

But there are all sorts of relationships between models, and models could relate to more than one model. If we delete everything, some other model might lose their relationship.
This is going to be very complicated when we think about more complex relationships like belongsToMany or morphTo. I really don't think it's a good idea to take this path...
There(re too many edge cases. I think it should be handled by users if they really need this functionality.

Thank you so much

I'll closing this PR for now. Maybe there'll be good idea to achieve something like this, though I think we should have discussion at issues.


sift test fails

Ubuntu 20.04, Python 3.8.5 (venv)
======================================================================
ERROR: test_matching (silx.opencl.sift.test.test_matching.TestMatching)
tests keypoints matching kernel
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/users/denolf/dev/silx/build/lib.linux-x86_64-3.8/silx/opencl/sift/test/test_matching.py", line 164, in test_matching
    delta = abs(res_sort - siftmatch).max()
ValueError: operands could not be broadcast together with shapes (491,2) (304,2)

Python 64 bits
       maxsize:<PHONE_NUMBER>854775807      maxunicode: 1114111
3.8.5 (default, Sep 15 2020, 11:23:56)
[GCC 9.3.0]

Platform: Linux-5.4.0-51-generic-x86_64-with-glibc2.2.5
- Machine: x86_64

Config: ["'--prefix=/users/denolf/.pyenv/versions/3.8.5' '--enable-shared' '--libdir=/users/denolf/.pyenv/versions/3.8.5/lib' 'LDFLAGS=-L/users/denolf/.pyenv/versions/3.8.5/lib -Wl,-rpath=/users/denolf/.pyenv/versions/3.8.5/lib ' 'CPPFLAGS=-I/users/denolf/.pyenv/versions/3.8.5/include '"]

Numpy 1.19.2
      include /users/denolf/virtualenvs/silx/py38/lib/python3.8/site-packages/numpy/core/include
      options {'edgeitems': 3, 'threshold': 1000, 'floatmode': 'maxprec', 'precision': 8, 'suppress': False, 'linewidth': 75, 'nanstr': 'nan', 'infstr': 'inf', 'sign': '-', 'formatter': None, 'legacy': False}

PyOpenCL platform:
  <pyopencl.Platform 'NVIDIA CUDA' at 0x55ef25544cd0>
    <pyopencl.Device 'Quadro P1000' on 'NVIDIA CUDA' at 0x55ef25544860> max_workgroup_size is 1024
Unable to import silx
Qt (from PyQt5): 5.15.1
SIP: 5.4.0

I was able to reproduce the issue on a similar platform with a Quadro P2000 GPU.
In the logs of silx.opencl.sift.test.test_matching.suite, I get the following:
INFO:silx.opencl.sift.plan:Computing descriptors with older-GPU optimized kernels
DEBUG:silx.opencl.processing:KernelContainer.get_kernel(descriptor_gpu1)

Which differs from what we get on other platforms, for ex.
INFO:silx.opencl.sift.plan:Computing descriptors with newer-GPU optimized kernels
DEBUG:silx.opencl.processing:KernelContainer.get_kernel(descriptor_gpu2)

For some reason self.LOW_END is set to 1 in sift/plan.py, although the target GPU is a recent one.
Using the old descriptor_gpu1 kernel leads to descriptors with many zeros, which cannot be "patched" correctly (see match.py). I suspect that the descriptor_gpu1 implementation (which explicitly targets old compute capabilities) behaves weirdly when used on "recent" compute capabilities.
Tweaking the code to use the other implementation (descriptor_gpu2) fixes the problem. So I think the issue should be solved by setting accurately the LOW_END flag when browsing available devices.

Still investigating. I narrowed to the function check_workgroup_size() in opencl/processing.py which always return 256 instead of 1024 for the P2000 GPU.
@kif  any idea on this ?

Sorry I did not see the message. I'll investigate.

I don't have the same results on a Maxwell (gen1) and on a Pascal:
In [9]: p=silx.opencl.sift.SiftPlan((1024,1024), "float32", platformid=0,deviceid=1)

In [10]: p.ctx
Out[10]: <pyopencl.Context at 0x1254e80 on <pyopencl.Device 'GeForce GTX 750 Ti' on 'NVIDIA CUDA' at 0x7f809845c830>>

In [11]: p.LOW_END
Out[11]: 0

In [12]: q=silx.opencl.sift.SiftPlan((1024,1024), "float32", platformid=0,deviceid=0)

In [13]: q.ctx
Out[13]: <pyopencl.Context at 0x150a320 on <pyopencl.Device 'GeForce GT 1030' on 'NVIDIA CUDA' at 0x7f8098493ac0>>

In [14]: q.LOW_END
Out[14]: 0

For info, the freshly created process is OK even on a P2000 (scisoft11):
In [3]: p=silx.opencl.sift.SiftPlan((1024,1024), "float32", devicetype="gpu")

In [4]: p.LOW_END
Out[4]: 0

In [5]: p.ctx
Out[5]: <pyopencl.Context at 0x1bb5c00 on <pyopencl.Device 'Quadro P2000' on 'NVIDIA CUDA' at 0x1bafb80>>

If I remember the code, there is a try-except which tries the high-end kernel and later on degrades if it fails because many resources are used in this kernel (registers if I remind properly, but it could be shared memory)

Yes, there is a "up to 3 attempt" loop. IIRC this loop works as expected on the Quadro P2000 ; but then the workgroup size is reported with a "small value" afterwise.


mzlff - privet by mazellovvv

Song Name
mzlff - privet
Artist Name
mazellovvv
Source
Youtube
Youtube Link
E_GKMpjoX_lgciU0
Direct File Link
No response
Song ID
1
Start Offset [ms]
0
Extra
Created from Auto Nong.
Created for level: 108795037

reject
invalid YouTube link


Enable IPv6 support in VM when IPv6 address is assigned

When we enable IPv6 support in Docker, a runq container fails to start.
https://docs.docker.com/config/daemon/ipv6/
# docker run --runtime runq --rm busybox ip addr show eth0
[init(1) 7291815] permission denied
main.setupNetwork
	/runq/cmd/init/network.go:74
main.runInit
	/runq/cmd/init/main.go:140
main.main
	/runq/cmd/init/main.go:48
runtime.main
	/usr/local/go/src/runtime/proc.go:204
runtime.goexit
	/usr/local/go/src/runtime/asm_s390x.s:779

This is because default sysctl settings defined in cfg.go disable IPv6 support in VM.
https://github.com/gotoz/runq/blob/d013e878cc2f35d23b4e85f5ac60ff9a872f27c4/internal/cfg/cfg.go#L23-L32
To enable IPv6 in runq, we explicitly need to specify sysctl option as follows.
# docker run --runtime runq --rm --sysctl net.ipv6.conf.all.disable_ipv6=0 --sysctl net.ipv6.conf.default.disable_ipv6=0 busybox ip addr show eth0
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 1000
    link/ether ee:17:03:1a:3d:1a brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/16 brd <IP_ADDRESS> scope global eth0
       valid_lft forever preferred_lft forever
    inet6 2001:db8:1::242:ac1f:2/64 scope global flags 02
       valid_lft forever preferred_lft forever
    inet6 fe80::42:acff:fe1f:2/64 scope link tentative
       valid_lft forever preferred_lft forever

This behavior is inconvenient when IPv6 is enabled.
This patch enables IPv6 support in runq when proxy detects a IPv6 address.

Thanks @yoheiueda for this PR.
Can you please add a simple test case with with 2 runq containers talking to each other via IPv6 similar to the existing test case in net.sh ?

OK, I will add a test case to net.sh

It turns out that we need to configure mavctap to let it pass multicast packets correctly in order to make IPv6 working.
https://superuser.com/questions/944678/how-to-configure-macvtap-to-let-it-pass-multicast-packet-correctly#1033768
With libvirt, we can enable it by setting trustGuestRxFilters="yes". I need further investigation on how to enable it without libvirt.
I also noticed that we should not copy link-local addresses from host to guest.
https://en.wikipedia.org/wiki/Link-local_address#IPv6

I did some experiments with multicast in the past. There is a netlink function: https://godoc.org/github.com/vishvananda/netlink#LinkSetAllmulticastOn

Stale PR


FATAL error during execution of JavaScript file 'server/initialize.js' after upgrade to 3.1.6

my environment running ArangoDB
I'm using the latest ArangoDB of the respective release series:

[x] self-compiled devel branch (3.1.6 - via Arch Linux AUR package)

On this operating system:

[x] Linux

[x] other: Arch Linux

this is an installation-related issue:
After upgrade from v3.0.7 to 3.1.6 via Arch Linux AUR package running
arangod

or
arangod --database.auto-upgrade

arangodb fails to start with the following output:
2017-01-04T13:27:48Z [1968] INFO ArangoDB 3.1.6 [linux] 32bit, using VPack 0.1.30, ICU 54.1, V8 <IP_ADDRESS>, OpenSSL 1.0.2j  26 Sep 2016
2017-01-04T13:27:48Z [1968] INFO using SSL options: SSL_OP_CIPHER_SERVER_PREFERENCE, SSL_OP_TLS_ROLLBACK_BUG
2017-01-04T13:27:48Z [1968] INFO file-descriptors (nofiles) hard limit is 4096, soft limit is 1024
2017-01-04T13:27:48Z [1968] INFO Authentication is turned on
2017-01-04T13:27:48Z [1968] INFO Authentication system only
2017-01-04T13:27:48Z [1968] INFO Authentication for unix sockets is turned on
2017-01-04T13:27:50Z [1968] INFO JavaScript using startup '/usr/share/arangodb3/js', application '/var/lib/arangodb3-apps'
2017-01-04T13:27:54Z [1968] WARNING reached heap-size limit, interrupting V8 execution (heap size limit 36700160, used 1974912)
2017-01-04T13:27:54Z [1968] FATAL error during execution of JavaScript file 'server/initialize.js'
2017-01-04T13:27:54Z [1968] WARNING reached heap-size limit, interrupting V8 execution (heap size limit 36700160, used 1974740)
2017-01-04T13:27:54Z [1968] FATAL error during execution of JavaScript file 'server/initialize.js'

This didn't help:
arangod --javascript.v8-options="--max_old_space_size=4096"

but this solved the problem:
arangod --javascript.v8-options="--max_old_space_size=1024"

I got to this solution by a lucky trial and error, and i don't know what is the cause. The solution is rather counter-intuitive for me, since it involves not increasing, but decreasing heap-size limit. It wasn't happening before the mentioned upgrade. (I also upgraded arch linux just before upgrading Arango, so that could be another potential source of fail.)
If you think it is Arango-related issue and you wish to spend time with it: Do you need some more information?

I think this is because you're running it on a 32 bit OS.
The default value for max_old_space_size is 3 GB, which is potentially too high.
Does the following patch fix the startup?
diff --git a/lib/Basics/operating-system.h b/lib/Basics/operating-system.h
index 396ad6c..0d029d4 100644
--- a/lib/Basics/operating-system.h
+++ b/lib/Basics/operating-system.h
@@ -53,6 +53,8 @@

 #if defined(__arm__) || defined(__aarch64__)
 #define TRI_V8_MAXHEAP 1 * 1024
+#elif TRI_PADDING_32
+#define TRI_V8_MAXHEAP 1 * 1024
 #else
 #define TRI_V8_MAXHEAP 3 * 1024
 #endif

@jsteemann Yes. The patch fixes it. :+1:

Just pushed the patch in the 3.1 branch. Will become part of 3.1.8.

Hi, thanks for your kind words - good to hear ;-)
We just released 3.1.8 with this bugfix.


Addons disappear from machines when middleclick sorting

Industrial Foregoing Version: industrial-foregoing-1.16.4-<IP_ADDRESS>
TeslaCoreLib Version: None
Crashlog (If Any): Did not crash the game

Not an IF issue, sorting mod issue


widget_tweaks causes 'DeprecationWarning: pkg_resources is deprecated as an API'

Python 3.8
widget_tweaks 1.4.2
    from pkg_resources import get_distribution, DistributionNotFound
  File "/Users/felixsargent/src/hiring/resume-ranker-frontend/mysite/.venv/lib/python3.8/site-packages/pkg_resources/__init__.py", line 121, in <module>
    warnings.warn("pkg_resources is deprecated as an API", DeprecationWarning)
DeprecationWarning: pkg_resources is deprecated as an API

found using pytest -W error

FWIW, both pkg_resources and directly invoking setup.py install are semi-deprecated and are mostly unsupported.
The replacement for pkg_resources.distribution(...).version is importlib.metadata.version(...) (backported to pre-3.7 Python as importlib_metadata), though I doubt that will solve anyone's problem if the installation metadata is simply not present.
https://github.com/pypa/setuptools/issues/2088#issuecomment-623567153, but the short answer is that you should always prefer pip install to setup.py install, even in a package manager. A few people (particularly those involved in Arch linux packaging) have been working on minimal PEP 517 build frontend to build wheels and a minimal wheel installer, so possibly early adoption of those technologies will work better for you, @PureTryOut.

https://github.com/googleapis/python-api-core/issues/27#issuecomment-676563754

Please remove usernames when quoting, as you now pinged me needlessly.


chore: add essential guides for open source project

Description

resolve #24

Changes

[x] Add SECURITY.md
[x] Add CONTRIBUTING.md
[x] Add CODE_OF_CONDUCT.md

Thank you very much for this!


SSM Parameters Reset

When we recently updated from version 0.49.2 to 0.54.4 all our SSM parameters were reset to their original values.
It is okay in most cases, but some parameters were updated "out of band" and needed to be manually reset afterward.
Is this expected behavior? I don't believe we experienced this before so we would like to understand what caused it and how we can guard against it in the future.
Thank you

Hi @robosung, thanks for bringing this up. Can I see how the SSM parameters are created in ur app? And how are the values updated usually, through AWS Console?

Hi @fwang, I apologize for the delayed response.
The SSM parameter is created like so:
    new ssm.StringParameter(this, "this-is-my-parameter", {
      stringValue: "CHANGEME",
      parameterName: "this-is-my-parameter",
    });

Thanks @robosung. And are they updated manually through the AWS SSM Console?

Hey @robosung typically with IaC tools all changes should be done through code.  If you make changes in the console there is "drift" and things maybe be set back to the IaC determined value at any time

@fwang Yes, it's done manually, usually via console.
@thdxr Yes, that's what we try to do most of the time, but because it's CDK, it doesn't work for things provisioned outside of AWS, like webhook URLs, API keys, etc.  It would be great if there is a recommendation for a better approach?
Thank you

I see. Is there any specific reason why you are not creating the SSM parameter in the console to begin with?

The main reason is that if they were solely created through ClickOps, it's not clear that it's required with provisioning the application. It also allows us to establish references and linkage to the parameters/secrets in code, as part of IaC.
I know it's a little arbitrary since we decided to document the need to update the parameters instead of documenting the need to create the parameters.

We are transition this repo to https://github.com/sst/v2 and are closing this issue for now. If it is still relevant please reopen it there - sorry for the trouble


Log FSAC http request failures to console,

regardless of the value of FSharp.logLanguageServiceRequestsToConsole, because errors should be seen, and shouldn't happen often (if all goes well).

good improvement, I'm always for more accurate error info :+1:


SearchBar placeholder color?

Hey,
Great library! I was curious if it'd be possible to extend the SearchBar component to allow customizing the text color of the placeholder via .searchTextField.attributedPlaceholder. I was going to try to make this change myself, but after opening the project and trying to compile I receive this error when building for previews:
cannot find type 'UIViewType' in scope

----------------------------------------

CompileDylibError: Failed to build SearchBar.swift

Compiling failed: cannot find type 'UIViewType' in scope

/Users/tjnickerson/Library/Developer/Xcode/DerivedData/SwiftUIX-dqevcaimfamqbyflaqvhfmzzokzo/Build/Intermediates.noindex/Previews/SwiftUIX-Package/Intermediates.noindex/SwiftUIX.build/Debug-iphonesimulator/SwiftUIX.build/Objects-normal/x86_64/SearchBar.1.preview-thunk.swift:453:107: error: cannot find type 'UIViewType' in scope
    @_dynamicReplacement(for: searchBar(_:textDidChange:)) private func __preview__searchBar(_ searchBar: UIViewType, textDidChange searchText: String) {
                                                                                ^~~~~~~~~~
/Users/tjnickerson/Library/Developer/Xcode/DerivedData/SwiftUIX-dqevcaimfamqbyflaqvhfmzzokzo/Build/Intermediates.noindex/Previews/SwiftUIX-Package/Intermediates.noindex/SwiftUIX.build/Debug-iphonesimulator/SwiftUIX.build/Objects-normal/x86_64/SearchBar.1.preview-thunk.swift:453:6: error: replaced function 'searchBar(_:textDidChange:)' of type '(SearchBar.Coordinator) -> (<<error type>>, String) -> ()' could not be found
    @_dynamicReplacement(for: searchBar(_:textDidChange:)) private func __preview__searchBar(_ searchBar: UIViewType, textDidChange searchText: String) {
     ^
<unknown>:0: note: found function 'searchBar(_:textDidChange:)' of type '(SearchBar.Coordinator) -> (UISearchBar, String) -> ()'

I'm not exactly sure if there's something special I might need to do? The project builds fine when building for simulator.
Additionally, I was trying to change the icon tint color in the navigation search bar via the environment key, but it doesn't seem to work:
.navigationSearchBar {
  SearchBar("Placeholder", text: $query)
    .foregroundColor(.white)
}.environment(\.tintColor, Color.white)

Does the tintColor environment key control something else? I feel like there should maybe be a more straightforward to controlling the specific tint of the search bar. In vanilla SwiftUI, you can use the template rendering method for images, then just set a foregroundColor, but because the SearchBar .icon() expects a UIImage, this isn't possible.
Happy to help to get a solution together! Let me know your thoughts.

@Nickersoft could you PR your changes? I can investigate why the canvas might be breaking.

Hey @vmanot, thanks for getting back to me! I can give it a shot, though I'm not sure how to test my changes if the canvas is broken 😂

@Nickersoft the easiest way to test would be to create a dummy Xcode project and add your forked version locally.

Closing due to inactivity.


SLIM-1662: Lower number of consumers to prevent overloading the syste…

…m when processing many and/or large shipment files.

All is well.


Kore doesn't allow for A(n) Firebase (all) popup(s).

For some reason, I have no idea why, but when I used signInWithPopup from Firebase, it doesn't work, and the first time nothing is printed out in the console, so I decided to remove some libraries to see if they are causing issues, and once I removed Kore, it worked. Kore was the only thing removed when I removed it. I would like you to look into this, and it may be an issue with my framework, which is Sveltekit. Hope you can find the cause of this and I will try to help if I can, Thanks!

Also would like to point out, that all popups don't work either, so maybe it is not necessarily an issue with Firebase.


Cannot create cluster: Timeout waiting for ssh key

Hi, using latest Rancher and installed the Upcloud driver.
Tried to create a cluster but get the following error:
Error with pre-create check: "Authentication failed using the given username and password. (AUTHENTICATION_FAILED)"; Timeout waiting for ssh key
What is the requirement for ssh key? This wasn't mentioned in the documentation. Thanks.

Hey @hc-codersatlas! Thanks for reaching out.
This is caused because the user/password combination you provided aren't valid and the docker-machine driver can't create the required instances.
We're waiting for response from UpCloud to fix some of the authentication bugs, but we know that it can be kind of a hassle right now.
Also, thanks for submitting and we'll document in case anyone else bumps into this!


Squashing credo consistency issue about spaces around operators

There was a space missing before the ->

Thank you!


sha1 from docs does not match actual file

Following this guide fails because of sha1 sum mismatch:
https://bosh.io/docs/init-vsphere.html
resource_pools:
- name: vms
  network: private
  stemcell:
    url: https://bosh.io/d/stemcells/bosh-vsphere-esxi-ubuntu-trusty-go_agent?v=2950
    sha1: 1153bc17fda0755fa8f99a3e360d952362170ac8

Command 'deploy' failed:
  Failed to download from 'https://bosh.io/d/stemcells/bosh-vsphere-esxi-ubuntu-trusty-go_agent?v=2950':
    SHA1 of downloaded file 'bf2752e1be480d75a34e127a0989b3b16a7ee9aa' does not match expected SHA1 '1153bc17fda0755fa8f99a3e360d952362170ac8'

$ wget https://bosh.io/d/stemcells/bosh-vsphere-esxi-ubuntu-trusty-go_agent?v=2950

$ sha1sum bosh-vsphere-esxi-ubuntu-trusty-go_agent\?v=2950
bf2752e1be480d75a34e127a0989b3b16a7ee9aa  bosh-vsphere-esxi-ubuntu-trusty-go_agent?v=2950

$ du -h bosh-vsphere-esxi-ubuntu-trusty-go_agent\?v=2950
517M	bosh-vsphere-esxi-ubuntu-trusty-go_agent?v=2950

Closing - now corrected in the docs.


[Documentation] Attribute Release in CAS 2.0 Protocol - Clarification

While working on this POC I spent/wasted some time trying to figure this out, i.e. that with CAS protocol version 2.0 attributes are not passed as part of the service response XML unless you mess up with the WEB-INF/view/jsp/protocol/2.0/casServiceValidationSuccess.jsp.
On the other hand it's not possible to switch to CAS protocol version 3.0 with the currently released artifacts to Maven central, i.e. org.jasig.cas.client.validation.Cas30ServiceTicketValidator is not part of the cas-client-core-3.3.3.jar.

All true. The behavior you describe is documented in the CAS protocol spec. This seems like it might more of a request to the client to make the release available.

The release will happen soon.  We merged in @leleuj changes for Cas30 validators (I did not have time to propose a better solution that did not generate more  classes) and we were waiting for Marvin's SAML improvement.

Great. Thanks for prompt reply. I found the spec you mentioned at http://jasig.github.io/cas/development/protocol/CAS-Protocol.html and I'll wait for new CAS client release.


[Action/SCI] Metrics for Embodied Emissions factor (M) for Falco

SCI = (E * I) + M per R
TBD - focusing on energy metric pre-KubeCon+CloudNativeCon EU '24

Summary
I've used the Boavizta front end to calculate the emissions factor for the Equinix m3.small.x86 server where Falco is deployed.
With the information available it returns a TE (Total Emissions) of 524.3 kgCO2eq for an EL (Expected Lifespan) of 4 years (35,040 hours) this results in an hourly value for M of 14.96 gCO2eq
The inputs and areas that need clarification are listed below. Once we're happy with this approach I'll write docs and the text for the panel in the Grafana dashboard.
Calculation
You can read about Boavizta's methodology here.
https://www.boavizta.org/en/blog/empreinte-de-la-fabrication-d-un-serveur
Currently all Equinix nodes we use are m3.small.x86 if we change instance types we'll need to repeat this process.
This screenshot shows the inputs and outputs. They are listed below and text in bold are inputs were more information or clarification is needed.

The output includes both the embodied carbon and a calculation for the energy consumption of the server during its expected lifetime. However we only use the embodied carbon since energy is measured with Kepler.
Inputs
CPU

1 x Intel Xeon E-2378G 8 cores @ 2.8 GHz
Intel datasheet states a TDP of 80W and Rocket Lake architecture

RAM

1 x 64GB
Manufacturer unknown - using Samsung default

SSD

2 x 480GB
Manufacturer unknown - using Micron default

Others

HDD quantity 0
Server type Rack - blade is the other supported type
PSU quantity 2 - using default

Server Usage

Localisation France - cluster is currently hosted in Equinix's Paris metro
LIfespan 4 years - using 4 years as per GSF embodied carbon docs

Outputs

Global Warming Potential Total : 884.3 kgCO2eq
Electricity Usage 360 kgCO2eq (excluded since we measure with Kepler)
Manufacturing 524.3 kgCO2eq

Result
TE (Total Emissions) of 524.3 kgCO2eq with an EL (Expected Lifespan) of 4 years (35,040 hours)
results in an hourly value for M of 14.96 gCO2eq
Out Of Scope

I kept networking out of scope for this first iteration. I'd be up for revisiting this in future iterations as suggested by Ed in https://github.com/cncf-tags/green-reviews-tooling/issues/4#issuecomment-1967321158

See above comment above the results of the Boavizta calculator.
@vielmetti It would be great to get your feedback on this. As well as any extra details you can share on the server spec.
@JacobValdemar I think you have experience with the Boavizta dataset? If are able to double check my working that would be much appreciated.
@nikimanoledaki @AntonioDiTuri likewise PTAL 🙏

CPU: Nice that you have obtained information about the specific CPU being used.
RAM Manufacturer: OK to use default when manufacturer is unknown.
SSD Manufacturer: OK to use default when manufacturer is unknown.
Server type: All AWS servers are "rack", so I think it is fair to assume that it is also the case for this server.
PSU quantity: using the value 2 is fine. Normally data centers have a "normal" power supply and one backup power supply.
Lifetime: The typical lifetime for a server in a data center are 3-4 years [1, p. 131], so I think it is fair to assume a lifetime of 4 years (unless Equinix specifically state otherwise).
I would recommend you to use the BoaviztAPI API instead of Datavizta to get the embodied impact of the server. It provides a more detailed response.
Since the m3.small.x86 instance is its own server, i.e. not a server which is shared across multiple customers (as is the case for many instance types on AWS) I don't think you have to perform further calculations.
[1] L. A. Barroso, U. Hölzle, and P. Ranganathan, The Datacenter as a Computer (Synthesis Lectures on Computer Architecture), 3rd ed. Cham: Springer Nature, 2019, isbn: 978-3-031-01761-2. [Online]. Available: https://library.oapen.org/handle/20. 500.12657/61844 (visited on 12/08/2023).

@JacobValdemar Thank you for the link and confirming on the defaults.
Using the API is a better approach. It returns a slightly higher TE of 550 kgCO2eq with 4 years EL that is an hourly M of 15.70 gCO2eq.
Here is the API request. Not posting the response as its large but its very interesting and has more accurate config for the CPU.
curl -X 'POST' \
  'https://api.boavizta.org/v1/server/?verbose=true&archetype=platform_compute_medium&criteria=gwp&criteria=adp&criteria=pe' \
  -H 'accept: application/json' \
  -H 'Content-Type: application/json' \
  -d '{
  "model": {
    "type": "rack"
  },
  "configuration": {
    "cpu": {
      "units": 1,
      "name": "intel xeon e-2378g"
    },
    "ram": [
      {
        "units": 1,
        "capacity": 64
      }
    ],
    "disk": [
      {
        "units": 2,
        "type": "ssd",
        "capacity": 480
      }
    ]
  },
  "usage": {
    "avg_power": 150,
    "usage_location": "FRA"
  }
}' | jq .


Don't require restart of Terminal on updating environment variables

Windows Terminal version (or Windows build number)
1.6.10571.0
Other Software
No response
Steps to reproduce

Open a bunch of tabs in terminal + customize them by splitting pane
Install anything that updates system environment variables
Launch a new tab

PS: In my case I had to install Cuda stuff that updates environment variables required by tensorflow gpu libs
Expected Behavior
The new tabs / panes should have the update environment variables
Actual Behavior
I have to kill all existing tabs and restart terminal

Reloading the environment variables is part of https://github.com/microsoft/terminal/issues/1125. It was already implemented but has been repeatedly reverted from stable branches (e.g. https://github.com/microsoft/terminal/commit/ba534aaad693d942ec6da4380005a09f6520d0c5 for release-1.6) because the existing implementation makes an environment block that is not compatible with Windows PowerShell https://github.com/microsoft/terminal/issues/7418.

Yep, sure is!
/dup #1125


Spelling mistake on Readme

Small thing i know, but might help noobs who are getting started (like me)
on the "Another Custom Insert Form" example
{{/autoForm}}
has a capital F
this must be a lowercase f

Actually my solution is wrong, they should both be capital F

Please close this issue if it is no longer valid :-)

still valid, the opening tag should have a capital F


Bump skybellpy version to fix api issue

Description:
Increase skybellpy version number to version with fixes for API changes.
Related issue (if applicable): fixes #
fixes https://github.com/home-assistant/home-assistant/issues/17617
Pull request in home-assistant.io with documentation (if applicable): home-assistant/home-assistant.io#<home-assistant.io PR number goes here>
n/a
Example entry for configuration.yaml (if applicable):
n/a

Checklist:

[ x ] The code change is tested and works locally.
[ x ] Local tests pass with tox. Your PR cannot be merged unless tests pass
[ x ] There is no commented out code in this PR.

If user exposed functionality or configuration variables are added/changed:

[ x ] Documentation added/updated in home-assistant.io

If the code communicates with devices, web services, or third-party tools:

[ x ] New dependencies have been added to the REQUIREMENTS variable (example).
[ x ] New dependencies are only imported inside functions that use them (example).
[ x ] New or updated dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[ x ] New files were added to .coveragerc.

If the code does not interact with devices:

[ x ] Tests have been added to verify that the new code works.

@MartinHjelmare any chance this could get pulled into 0.84? It's just a dependency bump (and no changes in upstream deps from that). Thanks!

@MartinHjelmare one of the build steps failed, but it seems unrelated. Can you take a look? Thank you.

That's a flaky test. Merging.


Why preg_match() expects parameter 2 to be string, object given?

Required Information

Operating system:
PHP version: 7.1
PHP Telegram Bot version: 0.50.0
Using MySQL database: no
Update Method: Webhook
Self-signed certificate: no
RAW update (if available):

I only install it to laravel project. After that a have error:

preg_match() expects parameter 2 to be string, object given
in Telegram.php (line 153)

What is wrong?

Can you share your hook.php? (remember to remove any private info, like API key and bot name)

@mrKorg Did you manage to get this fixed? Can I close here?


EvaluateAsync Esprima parsing fails on >ECMA 2016

Some Background: Puppeteer-sharp has two functions for evaluating JS, namely "evaluate function" and "evaluate expression", Playwright consolidated these into a single API, "EvaluateAsync", and uses Esprima-dotnet to parse that function and determine whether it's a function or expression before sending to Chromium. Which is cool. But,
The problem is that Esprima-dotnet doesn't seem to support ECMA Script >2016, so when calling .EvaluateAsync() on an ECMA 2020 that say, uses option chaining e.g. var name = person?.firstName, the C# method throws a parsing exception and does not send to the underlying browser.
Some solutions: a) provide a fallback when Esprima parsing fails, e.g. maybe default fallback to function since this is an easy convention to remember b) pass a boolean / options object for the evaluation that would allow the user to disable Esprima parsing and/or specify whether it's an expression or a function c) Update / replace Esprima .NET to support latest ECMA Script. Easier said than done obviously but these are options.
Current workarounds: escape js string and use eval()
Just my thoughts, and happy to submit a PR if someone can point me in the right direction. Thanks for looking.

Hey, @nh43de could you tell me a little bit more about your use case?
Are you importing scripts from other places? Because my first thought would be why no writing ECMA 2016.

Nothing fancy, just using nice new ECMA script features like optional chaining (https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Optional_chaining) which saves me from having to write tedious code.
Surprised that more people aren’t having this problem.
To me it just seems silly to have the method rely on the parsing to succeed by some secondary parsing layer. I get the convenience aspect that it brings but it shouldn’t throw an error because the outdated ECMA 2016 parser fails to recognize new language features that the web engine it’s passing it along to certainly can.

@nh43de I can review a PR with a bullet-proof way of detecting if a string contains a function or an expression and supporting new ECMA Scripts.

@kblok a preferred approach would be much simpler:

Parse using Esprima as before

If parsing succeeds, continue as before
If parsing fails

Instead of throwing an unhandled parsing exception, pass as a function string

That way, it becomes a matter of convention: just pass wrapped in a function. That is, until the Esprima engine can catch up beyond ECMA 2016.

@kblok a preferred approach would be much simpler:

Parse using Esprima as before

If parsing succeeds, continue as before

If parsing fails

Instead of throwing an unhandled parsing exception, pass as a function string

That way, it becomes a matter of convention: just pass wrapped in a function (when parsing fails). That is, until the Esprima engine can catch up beyond ECMA 2016. Unless I am missing something.

@kblok or anyone else, thoughts on this approach?

Instead of throwing an unhandled parsing exception, pass as a function string

I think we could do this. If the script is invalid we will end up with an exception from the driver. We will ship this for v0.190.0

@nh43de I hit a wall upstream. The driver is validating the script and the Node version is not ECMA 2020 compatible yet. So, although I think this is a valid approach, you won't be able to implement your code yet. I suggest you create an issue upstream.

Commenting on closed issue, but latest Esprima 2 beta has support for also optional chaining https://github.com/sebastienros/esprima-dotnet/releases/tag/v2.0.0-beta-1339 .

Esprima dependency and function detection logic has been removed!


Typo in buttons screen.

ouline button instead of OUTLINE button

@Ayushi-Singh-1903 please assign me this issue would love to work on it.


Question: running commands on multiple instances

Hi!
When I'm developing Ansible roles I usually target multiple operating systems or multiple versions of a single operating system.
Let's say I have molecule.yml which has the following vagrant section:
vagrant:
  raw_config_args:
    - "ssh.insert_key = false"

  platforms:
    - name: centos7
      box: centos/7
    - name: fedora23
      box: fedora/23-cloud-base
      # Install Python 2 and dependencies
      # NOTE: This is a work-around to make Ansible work with the Fedora 23's
      # official Vagrant box which doesn't include Python 2
      triggers:
        - trigger: after
          action: up
          cmd: run_remote 'dnf install -y python2 python2-dnf libselinux-python'

  providers:
    - name: virtualbox
      type: virtualbox

  instances:
    - name: test
      ansible_groups:
        - molecule
      interfaces:
        - network_name: private_network
          type: dhcp
          auto_config: true

How can I work with multiple supported platforms (namely, centos7 and fedora23)?

Do I define multiple instances, one for each supported platform? How can I specify which platform an instance uses in instance's definition in molecule.yml?
Can I specify a parameter to molecule commands that will tell Molecule to iterate through all supported platforms? Is it possible to specify a setting to pass this parameter to molecule commands by default?

@tjanez At the moment we don't have a mechanism to do multiple platforms in a single converge. The entire thing is built around the idea that you're converging one or multiple instances of the same platform. For our needs, we do these as separate steps, though I could definitely see how it would be convenient to test multiple platforms in a single shot.

@abrown-sg, thanks for your explanation.
So, if I understand current Molecule's design correctly, instances are meant to be used to test how a role behaves under different configurations/states of the currently chosen platform?
Furthermore, defining multiple instances to test a role on different platforms is not an intended Molecule's usage pattern?

@tjanez IIRC - The reason we didn't incorporate mixed platforms was due to vagrant.  We ran into issues getting vagrant to boot different platforms in the same Vagrantfile.  I haven't looked into this for quite some time.  We felt having the --platform flag was a decent compromise.

Furthermore, defining multiple instances to test a role on different platforms is not an intended Molecule's usage pattern?

I now remember why we took this approach.  When we wrote molecule, we were solving a use case specific to us.  We wanted the ability to perform multi-node testing.  Kitchen didn't support this, however, it did support multi-platform.   We implemented multi-host on a single platform.  Once we decided to implement multi-platform, it was implemented against a single-platform at a time.  I'm working on a rewrite of molecules config, which will likely address this in the future.  However, thats a couple months away from landing.

@retr0h Hey, so is there any progress on that?
FYI my current case (maybe I'll change this up) looks like this:

one Ansible role that's supposed to work on many OSes
I'm using Vagrant as the driver
CentOS7 should use virtualbox provider
Ubuntu 16 should use the lxc provider

Molecule v2 supports scenarios.  Your scenarios can be written for each distro and driver.

@retr0h Thanks!


Improve paths and commit message

Uses env to execute bash rather than hardcoding a path and removes the hardcoded path to json expecting it to be on the users PATH like everything else.
Also adds a line to the final merge commit that will cause github to close the PR.

👍🏾 and looks like you shoudn’t squash this (which I’m guessing was already your plan).


Logs (1/n) Basic formatting

Add the Timestamps option to retrieve a timestamp for each log entry

tested. Timestamps added.

verified on prod. OK


test: add tests for view command

Closes #103

Codecov Report

Merging #150 (a5dd506) into master (688510c) will increase coverage by 2.13%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##             master     #150      +/-   ##
============================================
+ Coverage     56.03%   58.17%   +2.13%
- Complexity      406      423      +17
============================================
  Files            80       80
  Lines          1731     1731
  Branches        168      168
============================================
+ Hits            970     1007      +37
+ Misses          677      638      -39
- Partials         84       86       +2

Impacted Files
Coverage Δ

...java/seedu/address/logic/commands/ViewCommand.java
88.23% <100.00%> (+88.23%)
:arrow_up:

...va/seedu/address/logic/commands/CommandResult.java
59.25% <0.00%> (+25.92%)
:arrow_up:

Continue to review full report at Codecov.

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


FileNotFoundError: [WinError 2] The system cannot find the file specified python-whois

Information :
--> Python - 3.8.2
--> Visual Studio Code
--> installed by -- "pip install python-whois"
--> Windows 10 64 Bit
command line:  domain = whois.query('google.com')
Traceback (most recent call last):
File "", line 1, in
File "G:\Python\lib\site-packages\whois_init_.py", line 67, in query
pd = do_parse(do_query(d, force, cache_file, slow_down, ignore_returncode), tld)
File "G:\Python\lib\site-packages\whois_1_query.py", line 46, in do_query
_do_whois_query(dl, ignore_returncode),
File "G:\Python\lib\site-packages\whois_1_query.py", line 60, in _do_whois_query
p = subprocess.Popen(['whois', '.'.join(dl)], stdout=subprocess.PIPE, stderr=subprocess.STDOUT)
File "G:\Python\lib\subprocess.py", line 854, in init
self._execute_child(args, executable, preexec_fn, close_fds,
File "G:\Python\lib\subprocess.py", line 1307, in _execute_child
hp, ht, pid, tid = _winapi.CreateProcess(executable, args,
FileNotFoundError: [WinError 2] The system cannot find the file specified

I have the same error

I had a very similar issue posted in my own issue-thread after Danny fixed the variable tz not being set in the else statement. He labeled it as a bug so I think he's aware of it. The only thing I can think of is reinstalling everything and trying it again. I don't think I use this in my project so I can't help you further.

No Reply From The Team : (

The problem is that you try this on windows. Windows has no whois tool on the system so you need to install sysinternals whois in your path to make it run
https://docs.microsoft.com/en-us/sysinternals/downloads/whois
capy whois.exe to your path. If you have windows 64 you need to rename whois64.exe and copy to your path.
This library calls whois and read the replay
https://github.com/DannyCork/python-whois/blob/2f75d1a079eac1738349564758c6678f5c406202/whois/_1_query.py#L60

The problem is that you try this on windows. Windows has no whois tool on the system so you need to install sysinternals whois in your path to make it run
https://docs.microsoft.com/en-us/sysinternals/downloads/whois
capy whois.exe to your path. If you have windows 64 you need to rename whois64.exe and copy to your path.
This library calls whois and read the replay
https://github.com/DannyCork/python-whois/blob/2f75d1a079eac1738349564758c6678f5c406202/whois/_1_query.py#L60

To make my comment more clear, that was under Ubuntu 14.04 I believe and Python 2.7, not Windows (as opposed to the issue starter here).

The problem is that you try this on windows. Windows has no whois tool on the system so you need to install sysinternals whois in your path to make it run
https://docs.microsoft.com/en-us/sysinternals/downloads/whois
capy whois.exe to your path. If you have windows 64 you need to rename whois64.exe and copy to your path.
This library calls whois and read the replay
https://github.com/DannyCork/python-whois/blob/2f75d1a079eac1738349564758c6678f5c406202/whois/_1_query.py#L60

To make my comment more clear, that was under Ubuntu 14.04 I believe and Python 2.7, not Windows (as opposed to the issue starter here).

Under ubuntu you need to install whois using apt
sudo apt-get update
sudo apt-get install whois
on ubuntu 14.04

The problem is that you try this on windows. Windows has no whois tool on the system so you need to install sysinternals whois in your path to make it run
https://docs.microsoft.com/en-us/sysinternals/downloads/whois
capy whois.exe to your path. If you have windows 64 you need to rename whois64.exe and copy to your path.
This library calls whois and read the replay
https://github.com/DannyCork/python-whois/blob/2f75d1a079eac1738349564758c6678f5c406202/whois/_1_query.py#L60

To make my comment more clear, that was under Ubuntu 14.04 I believe and Python 2.7, not Windows (as opposed to the issue starter here).

Under ubuntu you need to install whois using apt
sudo apt-get update
sudo apt-get install whois
on ubuntu 14.04

Which was installed, as stated by the ReadMe.

Still It's Not Working

oh yes it is.

I also had the same issue and I also add to PATH env. the whois by renaming it but it didn't work. So u can use a Virtual Machine with Ubuntu or u can use subprocess module and try to parse the output on your own

oh yes it is.

I also had the same issue and I also add to PATH env. the whois by renaming it but it didn't work. So u can use a Virtual Machine with Ubuntu or u can use subprocess module and try to parse the output on your own

I also had the same issue and I also add to PATH env. the whois by renaming it but it didn't work. So u can use a Virtual Machine with Ubuntu or u can use subprocess module and try to parse the output on your own

oh yes it is.

I also had the same issue and I also add to PATH env. the whois by renaming it but it didn't work. So u can use a Virtual Machine with Ubuntu or u can use subprocess module and try to parse the output on your own

Or if u fpund out a way you can share :D


Performance improvement of FermionicOp.reduce

Summary
This PR introduces the following two changes.

Vectorize FerimionicOp.reduce
Add normal_order option to FerimionicOp.reduce (default is True)

import random
from timeit import timeit
from qiskit_nature.operators.second_quantization import FermionicOp

def random_op(k, n):
    random.seed(123)
    op = sum((FermionicOp("".join(random.choices("+-ENI", k=k)), display_format="dense") * random.random()) for _ in range(n))
    return op

def bench_reduce(op):
    print(f"normal order: {timeit(lambda: op.reduce(), number=1)} sec")
    try:
        print(f"no normal order: {timeit(lambda: op.reduce(normal_order=False), number=1)} sec")
    except TypeError:
        pass

op = random_op(5, 10000)
bench_reduce(op)

main
normal order: 2.4304106099998535 sec

this PR
normal order: 2.271573748999799 sec
no normal order: 0.05692009299946221 sec

Details and comments
The motivation to apply reduce before qubit mapping is #585. The output operator can be redundant.
So, I want to simplify the operators. But, I don't think qubit operator requires the normal order.
I added the normal_order option because applying normal_order may increase the number of operators and to_normal_order can be slow.
If users apply reduce to an operator before qubit mapping, it takes more time than without reduce due to the larger number of operators.
I attach an example. The size of operator grows from 1000 to 18950 by applying reduce.
import random
from timeit import timeit

from qiskit_nature.operators.second_quantization import FermionicOp
from qiskit_nature.converters.second_quantization import QubitConverter
from qiskit_nature.mappers.second_quantization import JordanWignerMapper

def random_op(k, n):
    random.seed(123)
    op = sum((FermionicOp("".join(random.choices("+-E", k=k)), display_format="dense") * random.random()) for _ in range(n))
    return op

qubit_converter = QubitConverter(mapper=JordanWignerMapper())

def bench_convert(op):
    print(f"w/o reduce: {timeit(lambda: qubit_converter.convert(op), number=1)} sec")
    print(f"w/ reduce of normal order: {timeit(lambda: qubit_converter.convert(op.reduce()), number=1)} sec")
    try:
        print(f"w/ reduce no normal order: {timeit(lambda: qubit_converter.convert(op.reduce(normal_order=False)), number=1)} sec")
    except TypeError:
        pass

op = random_op(10, 1000)

print("qubit convert")
bench_convert(op)

print("\noperator sizes")
print(f"original op: {len(op)}")
print(f"w/ reduce of normal order: {len(op.reduce())}")
try:
    print(f"w/ reduce no normal order: {len(op.reduce(normal_order=False))}")
except TypeError:
    pass

this PR
qubit convert
w/o reduce: 1.7863747950004836 sec
w/ reduce of normal order: 17.12350188399978 sec
w/ reduce no normal order: 1.741173968000112 sec

operator sizes
original op: 1000
w/ reduce of normal order: 18950
w/ reduce no normal order: 989

I have not written the docstring of the new option reduce(normal_order). If the option is allowed, I will write it.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

8 of 8 (100.0%)  changed or added relevant lines in 1 file are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+0.002%) to 83.146%

Files with Coverage Reduction
New Missed Lines
%

qiskit_nature/operators/second_quantization/fermionic_op.py
1
88.89%

Totals

Change from base Build<PHONE_NUMBER>:
0.002%

Covered Lines:
8821

Relevant Lines:
10609

💛  - Coveralls

This PR is made obsolete by https://github.com/Qiskit/qiskit-nature/pull/607.

I will port this optimization to the upcoming simplify methods #607.
https://github.com/Qiskit/qiskit-nature/pull/607#issuecomment-1076457920


lv_mem_monitor can crash with DIV0 exception

Describe the bug
I was debugging my app crashing at startup when implementing lv_mem_monitor into my logging function. It turns out this was because lv_mem_monitor throws a Divide by 0 exception, when called before lv_initand thus before lv_mem_init. But I also found another edge case where it could crash.
To Reproduce

Call lv_mem_monitor before lv_init.

or

There also seems to exist an edge case where the actual value of mon_p->free_size can be exactly zero if all the entries are in use:

    lv_init();

    // Check initial free_size:
    lv_mem_monitor_t mem_mon;
    lv_mem_monitor(&mem_mon);
    printf("initial free_size = %u\n", mem_mon.free_size);

    // Use all the available memory, free_size is now zero:
    void * test = lv_mem_alloc(mem_mon.free_size);
    lv_mem_monitor(&mem_mon);
    printf("actual free_size = %u\n", mem_mon.free_size);
    lv_mem_free(test);

returns
initial free_size = 12208
actual free_size = 0

The second call to lv_mem_monitor crashes too if this edge case is not handled.
Expected behavior
Gracefully return even when  mon_p->free_size is zero:
https://github.com/littlevgl/lvgl/blob/7f0677917972c0c1782fa66dd641b91de8d1b300/src/lv_misc/lv_mem.c#L359-L362
Could add a check like:
    mon_p->total_size = LV_MEM_SIZE;
    mon_p->used_pct   = 100 - (100U * mon_p->free_size) / mon_p->total_size;
    if(mon_p->free_size != 0) {
        mon_p->frag_pct = (uint32_t)mon_p->free_biggest_size * 100U / mon_p->free_size;
        mon_p->frag_pct = 100 - mon_p->frag_pct;
    }

Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Adding a check on mon_p->free_size != 0 before the division solved my issue.
I know that using lv_mem_monitor before lv_init is definitely not wise, and I considered implementing a flag to check it in my app. But looking at the source code I see there is also another rare edge case where there is a risk of a divide by zero.
It seems best to handle this exception gracefully inside the function.

Thank you for the fast response.


Playback suddenly interrupts

Expected Behavior
Playback whole file from start to end
Current Behavior
Playback suddenly interrupts in the middle
Possible Solution
None
Steps to Reproduce (for bugs)
Usual playback from magnet link
Context
None
Your Environment

Version used: 0.0.34, 0.0.35, 0.0.36
Environment name and version: Kodi 16.1
Operating System and version: Android 4
Link to Kodi debug log: (issue at the end of the log) http://rgho.st/8pG8snpcl

23:15:24 T:1929507320  NOTICE: [plugin.video.elementum] INFO  bittorrent   ▶ UpdateWatched    Currently at 56.186532%, KodiID: 0
23:15:24 T:1929507320  NOTICE: [plugin.video.elementum] INFO  main         ▶ Notification     Stopped at 56.186532%

I didn't stopped it myself.
Additional info
I've tried to change the memory buffer sizes without any luck. Right now configuration is following:

cache memory buffer in advancessettings.xml is set to 50MB
ram memory buffer in Elementum is set to 200MB
cache in Bittorrent settings in Elementum is set to 50MB

Any solution for this problem? its happening with me too.

Here is the info right before interrupt
https://pastebin.com/9ngsrASX

Btw it is the torrent with multiple files

And I've updated plugins versions

Have you tried with default memory size of 100mb?
In the log everything is fine. That is a known issue, and nobody knows why that happen.

@avoidik Any  updates? Should we close the issue?

Closing without response.


WEEKNUM compatibility with ISO 8601

I'm using the DaxDate Template v.1.14 and I guess there is a problem with the week number. Related to ISO 8601 the first three days in January 2021 are week number 53 where as in the DaxDateTemplate the week number starts with 1.

The ISO standard is implemented in FW prefixed columns. Check comments to properly setup parameters.

The ISO standard is implemented in FW prefixed columns. Check comments to properly setup parameters.