API Update Errors?

Hi @drstrangelooker, we're suddenly receiving failures of ldeploy with an error mentioning missing_method query_space. Full log below. Wondering if this is related to GA of API 4.0. I see in our older logs the connection string built ended in 3.1. Is there something we can switch on the frontend to force our string back to referencing API 3.1?
Full error (--- substituted for some detail)
[2022-03-16T16:11:51.581Z] /var/lib/gems/2.5.0/gems/looker-sdk-0.0.7/lib/looker-sdk/client/dynamic.rb:105:in `method_missing': undefined method `space' for #<LookerSDK::Client:0x000055b8a6c4dbc8> (NoMethodError)   [2022-03-16T16:11:51.581Z]      from /var/lib/gems/2.5.0/gems/gazer-0.2.44/lib/gzr/modules/space.rb:65:in `query_space'   [2022-03-16T16:11:51.581Z]      from /var/lib/gems/2.5.0/gems/gazer-0.2.44/lib/gzr/commands/space/export.rb:87:in `process_space'   [2022-03-16T16:11:51.581Z]      from /var/lib/gems/2.5.0/gems/gazer-0.2.44/lib/gzr/commands/space/export.rb:81:in `block in execute'   [2022-03-16T16:11:51.581Z]      from /var/lib/gems/2.5.0/gems/gazer-0.2.44/lib/gzr/modules/session.rb:207:in `with_session'   [2022-03-16T16:11:51.581Z]      from /var/lib/gems/2.5.0/gems/gazer-0.2.44/lib/gzr/commands/space/export.rb:49:in `execute'   [2022-03-16T16:11:51.581Z]      from /var/lib/gems/2.5.0/gems/gazer-0.2.44/lib/gzr/commands/space.rb:80:in `export'   [2022-03-16T16:11:51.581Z]      from /var/lib/gems/2.5.0/gems/thor-0.20.3/lib/thor/command.rb:27:in `run'   [2022-03-16T16:11:51.581Z]      from /var/lib/gems/2.5.0/gems/thor-0.20.3/lib/thor/invocation.rb:126:in `invoke_command'   [2022-03-16T16:11:51.581Z]      from /var/lib/gems/2.5.0/gems/thor-0.20.3/lib/thor.rb:387:in `dispatch'   [2022-03-16T16:11:51.581Z]      from /var/lib/gems/2.5.0/gems/thor-0.20.3/lib/thor/invocation.rb:115:in `invoke'   [2022-03-16T16:11:51.581Z]      from /var/lib/gems/2.5.0/gems/thor-0.20.3/lib/thor.rb:238:in `block in subcommand'   [2022-03-16T16:11:51.581Z]      from /var/lib/gems/2.5.0/gems/thor-0.20.3/lib/thor/command.rb:27:in `run'   [2022-03-16T16:11:51.581Z]      from /var/lib/gems/2.5.0/gems/thor-0.20.3/lib/thor/invocation.rb:126:in `invoke_command'   [2022-03-16T16:11:51.581Z]      from /var/lib/gems/2.5.0/gems/thor-0.20.3/lib/thor.rb:387:in `dispatch'   [2022-03-16T16:11:51.581Z]      from /var/lib/gems/2.5.0/gems/thor-0.20.3/lib/thor/base.rb:466:in `start'   [2022-03-16T16:11:51.581Z]      from /var/lib/gems/2.5.0/gems/gazer-0.2.44/exe/gzr:36:in `<top (required)>'   [2022-03-16T16:11:51.581Z]      from /usr/local/bin/gzr:23:in `load'   [2022-03-16T16:11:51.581Z]      from /usr/local/bin/gzr:23:in `<main>'   [2022-03-16T16:11:51.581Z] options: {"debug"=>true, "host"=>"---", "port"=>"443", "ssl"=>true, "verify_ssl"=>true, "timeout"=>60, "force"=>false, "client_id"=>"---", "client_secret"=>"---", "dir"=>"/looker_export/Shared"}   [2022-03-16T16:11:51.581Z] API 3.1 available? true   [2022-03-16T16:11:51.581Z] connecting to ["api_endpoint=>https://---:443/api/4.0", "connection_options=>{:ssl=>{:verify=>true, :verify_mode=>3}, :request=>{:timeout=>60}}", "user_agent=>Gazer 0.2.44", "client_id=>---", "client_secret=>---"]   [2022-03-16T16:11:51.581Z] check for connectivity: true   [2022-03-16T16:11:51.581Z] verify authentication: true   [2022-03-16T16:11:51.581Z] logout

@JCPistell @jannarobertson-bytecode any thoughts on this? Seems like this would likely be impacting everyone

Hi @alec-flatiron,
There was a fix applied to gzr last week related to the API 3.1 vs 4.0. https://github.com/looker-open-source/gzr/pull/125
Can you upgrade gzr and confirm if you are still experiencing the issue?
Thanks!

Looks like that worked for us! Pinned to the latest version. Thank you


update plot_spatial_weights for new libpysal api

when the libpysal change goes live (libpysal.weights.W(...use_index=True) it will break the spatial weights plotting function

We wanted to refactor that anyway and merge the plotting method we have here with the one over in lib anyway. So it may actually be a candidate for a quick-ish PR.

while we're at it, one thing it would be nice to add is auto ability to scale linewidths by weight value for nonbinary weights

also maybe an interactive analogue

An easy way to do those would be to create a GeoSeries from the links and use geopandas plot and explore methods but it means one more copy of the data as an intermediate step.

thats what i had in mind. And maybe @walkerke would be willing to contribute his interactive LISA code?

I thought that's just explore over LISA labels, no?

yeah pretty much. just a function to wrap the labels and hit explore

Looking through splot I think an interactive analogue to the methods that wraps .explore() would be pretty useful.  Happy to take a look at it.


Watcher for pods.v1@none has failed

I installed in the default netchecks namespace and created an assertion there, it works fine.
Creating an assertion in another namespace (let's call it ns=foo) however, the operator pod starting in this namespace fails with:
2023-12-20 14:30:04 [debug    ] Setting config from file       config_file_path=PosixPath('/var/config/config.json')
2023-12-20 14:30:04 [debug    ] Starting operator              config={"probe": {"imagePullSecrets": [], "podAnnotations": {}, "image": {"repository": "ghcr.io/hardbyte/netchecks", "pullPolicy": "Always", "tag": "main"}, "resources": {}, "verbose": false}, "metrics": {"port": 9090, "enabled": true}}
/home/netchecks/bin/.cache/virtualenvs/netcheck-operator-9TtSrW0h-py3.11/lib/python3.11/site-packages/kopf/_core/reactor/running.py:179: FutureWarning: Absence of either namespaces or cluster-wide flag will become an error soon. For now, switching to the cluster-wide mode for backward compatibility.
  warnings.warn("Absence of either namespaces or cluster-wide flag will become an error soon."
[2023-12-20 14:30:04,243] kopf._core.engines.a [INFO    ] Initial authentication has been initiated.
[2023-12-20 14:30:04,246] kopf.activities.auth [INFO    ] Activity 'login_via_client' succeeded.
[2023-12-20 14:30:04,246] kopf._core.engines.a [INFO    ] Initial authentication has finished.
[2023-12-20 14:30:04,310] kopf._core.reactor.o [WARNING ] Not enough permissions to watch for resources: changes (creation/deletion/updates) will not be noticed; the resources are only refreshed on operator restarts.
[2023-12-20 14:30:04,311] kopf._core.reactor.o [ERROR   ] Watcher for pods.v1@none has failed: ('pods is forbidden: User "system:serviceaccount:foo:netcheck-operator" cannot list resource "pods" in API group "" at the cluster scope', {'kind': 'Status', 'apiVersion': 'v1', 'metadata': {}, 'status': 'Failure', 'message': 'pods is forbidden: User "system:serviceaccount:foo:netcheck-operator" cannot list resource "pods" in API group "" at the cluster scope', 'reason': 'Forbidden', 'details': {'kind': 'pods'}, 'code': 403})
Traceback (most recent call last):
  File "/home/netchecks/bin/.cache/virtualenvs/netcheck-operator-9TtSrW0h-py3.11/lib/python3.11/site-packages/kopf/_cogs/clients/errors.py", line 148, in check_response
    response.raise_for_status()
  File "/home/netchecks/bin/.cache/virtualenvs/netcheck-operator-9TtSrW0h-py3.11/lib/python3.11/site-packages/aiohttp/client_reqrep.py", line 1011, in raise_for_status
    raise ClientResponseError(
aiohttp.client_exceptions.ClientResponseError: 403, message='Forbidden', url=URL('https://<IP_ADDRESS>:443/api/v1/pods')
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
  File "/home/netchecks/bin/.cache/virtualenvs/netcheck-operator-9TtSrW0h-py3.11/lib/python3.11/site-packages/kopf/_cogs/aiokits/aiotasks.py", line 108, in guard
    await coro
  File "/home/netchecks/bin/.cache/virtualenvs/netcheck-operator-9TtSrW0h-py3.11/lib/python3.11/site-packages/kopf/_core/reactor/queueing.py", line 175, in watcher
    async for raw_event in stream:
  File "/home/netchecks/bin/.cache/virtualenvs/netcheck-operator-9TtSrW0h-py3.11/lib/python3.11/site-packages/kopf/_cogs/clients/watching.py", line 86, in infinite_watch
    async for raw_event in stream:
  File "/home/netchecks/bin/.cache/virtualenvs/netcheck-operator-9TtSrW0h-py3.11/lib/python3.11/site-packages/kopf/_cogs/clients/watching.py", line 174, in continuous_watch
    objs, resource_version = await fetching.list_objs(
                             ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/netchecks/bin/.cache/virtualenvs/netcheck-operator-9TtSrW0h-py3.11/lib/python3.11/site-packages/kopf/_cogs/clients/fetching.py", line 28, in list_objs
    rsp = await api.get(
          ^^^^^^^^^^^^^^
  File "/home/netchecks/bin/.cache/virtualenvs/netcheck-operator-9TtSrW0h-py3.11/lib/python3.11/site-packages/kopf/_cogs/clients/api.py", line 111, in get
    response = await request(
               ^^^^^^^^^^^^^^
  File "/home/netchecks/bin/.cache/virtualenvs/netcheck-operator-9TtSrW0h-py3.11/lib/python3.11/site-packages/kopf/_cogs/clients/auth.py", line 45, in wrapper
    return await fn(*args, **kwargs, context=context)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/netchecks/bin/.cache/virtualenvs/netcheck-operator-9TtSrW0h-py3.11/lib/python3.11/site-packages/kopf/_cogs/clients/api.py", line 85, in request
    await errors.check_response(response)  # but do not parse it!

I can see the service account was created:
$ k get serviceaccount -n $ns
NAME                SECRETS   AGE
default             0         50d
netcheck-operator   0         21m

Thanks for the bug report. I might not be able to look into this until after Christmas.
Did you install via helm?
One thing to check is whether the system:serviceaccount:foo:netcheck-operator has a cluster role binding to the role I defined in the chart, and if any other time bindings are present.

Thanks for the bug report. I might not be able to look into this until after Christmas.

no stress, I also need to dig a bit more.

Did you install via helm?

yes

One thing to check is whether the system:serviceaccount:foo:netcheck-operator has a cluster role binding to the role I defined in the chart, and if any other time bindings are present.

I would need to check that in details indeed.

Here is some feedback:
k get  clusterrole | grep netchecks
netchecks                                                                2023-11-21T14:33:34Z
netchecks-operator                                                       2023-11-21T08:37:15Z
netchecks-operator-policy-reporter                                       2023-11-21T08:37:15Z

k get -n $ns serviceaccount
NAME                SECRETS   AGE
default             0         51d
netcheck-operator   0         19h

k get  clusterrolebinding | grep netchecks
netchecks                                                             ClusterRole/netchecks                                                                29d
netchecks-operator                                                    ClusterRole/netchecks-operator                                                       30d
netchecks-operator-policy-reporter                                    ClusterRole/netchecks-operator-policy-reporter                                       30d

k get clusterrolebinding netchecks-operator -o yaml
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: |
      {"<...>"}]}
  creationTimestamp: "2023-11-21T08:37:15Z"
  labels:
    app.kubernetes.io/instance: netchecks-operator
    app.kubernetes.io/name: netchecks
    app.kubernetes.io/version: 0.1.1
  name: netchecks-operator
  resourceVersion: "159469406"
  uid: f3ee9d83-7e55-4171-8f16-d9363a6addaa
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: netchecks-operator
subjects:
- kind: ServiceAccount
  name: netcheck-operator
  namespace: netchecks

Hi @chevdor I haven't been able to replicate this yet. The netchecks-operator ClusterRole that should have been created from the helm chart asks for quite broad Pod permissions - defined here.
Would you be able to try the latest version and report back?
https://artifacthub.io/packages/helm/netchecks/netchecks/0.1.12

I just upgraded (using helm) and applied the exact same NetworkAssertion.
I triggered the cron manually and shortly after I saw that everything works now and the result nicely shows in the Polikcy Reporter as well. Nice, thanks for the ping !
Would you mind adding a link to what you think could be the fix ? I am closing anyway since the issue is now resolved.


Rust optimizer doesn't work in Mac

OS: OS X M1

I had been struggling to study cosmwasm smart contracts.
And I found that cargo run-script optimize doesn't work as I expected.
You can reproduce this issue through below.
$ cargo generate --git https://github.com/CosmWasm/cw-template.git --branch 0.8 --name test
$ cargo wasm
$ cargo schema
$ cargo run-script optimize

Running script 'optimize': 'docker run --rm -v "$(pwd)":/code --mount type=volume,source="$(basename "$(pwd)")_cache",target=/code/target --mount type=volume,source=registry_cache,target=/usr/local/cargo/registry cosmwasm/rust-optimizer:0.12.4
'
WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested
Info: RUSTC_WRAPPER=sccache
Info: sccache stats before build
Compile requests                      0
Compile requests executed             0
Cache hits                            0
Cache misses                          0
Cache timeouts                        0
Cache read errors                     0
Forced recaches                       0
Cache write errors                    0
Compilation failures                  0
Cache errors                          0
Non-cacheable compilations            0
Non-cacheable calls                   0
Non-compilation calls                 0
Unsupported compiler calls            0
Average cache write               0.000 s
Average cache read miss           0.000 s
Average cache read hit            0.000 s
Failed distributed compilations       0
Cache location                  Local disk: "/root/.cache/sccache"
Cache size                            0 bytes
Max cache size                       10 GiB
Building contract in /code ...
    Updating crates.io index
Killed
Finished, status of exit status: 13

And there is one thing I'm curious.
Does the below message mean that I should execute cargo run-script. optimize command on linux os only?
WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested

You can make an issue on rust-optimizer to publish arm builds.
In the meantime, check out the repo and build the dockerfile locally. I have done that on a Mac m1 and it works fine

@ethanfrey Thanks for your answer.
I have tried to optimize wasm with cosmwasm/rust-optimizer-arm64:0.12.4 Docker image and it works fine.
So. This issue should be closed.

@orkunkl maybe you can add a small section to the Readme to mention that?


Text2image

Python plugin to run text to image models from the app and add the generated images directly to the dataset.
Built out support for VQGAN-CLIP, DALLE2, and Stable Diffusion, with optional "advanced" settings.
You will need

an openai API key (and openai python package installed)
replicate python package installed, and replicate API key

This has been converted to a community plugin here!


Businesses

Once a certain level in a job is reached, a player can decide to start up a business that relates to that job. When a player starts a business they will no longer be rewarded with experience and money. Instead, the items gained from the job can be sold(Automatically sold, not sold to players) in order to gain an increased amount of money as well as experience that is put towards your business. As usual, everything relating to businesses, including rewards and business enhancements, can be changed/removed to your liking.

Closing this as I feel it would be better implemented by a standalone plugin.


Race condition with reset of _self._cmds in invoke().

The invoke() function only clears the internal _self._cmds array of "added" commands upon asynchronous completion of the PowerShell execution of the commands.  This sets up a race condition with other command executions.
In certain circumstances, it is possible for additional commands to be added and invoke() called again before the processing of the previous invoke()has completed -- and before node-powershell has cleared the _cmds array.  In these cases, the secondary invoke() calls "inherit" and extend the current contents of _cmds array already being processed by the original invoke() call.
In short, this race condition can result in PowerShell commands being executed multiple times and other unexpected chaos.
I quite easily ran into this in a project I was working on, where node-powershell was being hosted on a remote machine with addCommand() and invoke() calls being sent to it.  Throw in any moderately long-running command (thus causing invoke() to take some time to complete), and the race condition is exposed.
The fix would appear to be to eliminate the race condition by simply clearing the _cmds array earlier, as the PowerShell command is submitted, rather than after it completes.
Like so:
      var _self = this;
      return new Promise(function (resolve, reject) {
        var _cmdsStr = _self._cmds.join('; ');

        // NEW
        // To avoid races, the commands array should be cleared up-front, here:
        _self._cmds = [];
        // END

        _self.__print__(OK_MSG, 'Command invoke started');
        _self._cfg.debugMsg && console.log(' ' + colors.gray(_cmdsStr));

        function resolve_listener(data) {
          _self.__print__(OK_MSG, 'Command invoke finished\n');
          reset();
          return resolve(data);
        }
        function reject_listener(error) {
          _self.__print__(ERROR_MSG, 'Command invoke failed\n');
          reset();
          return reject(ERROR_MSG(error));
        }
        function reset() {
          _self.removeListener('_resolve', resolve_listener);
          _self.removeListener('_reject', reject_listener);

          // OLD
          // Clearing it here (the current code) is way too late and creates race conditions.
          // _self._cmds = [];
          // END
        }

        _self.on('_resolve', resolve_listener);
        _self.on('_reject', reject_listener);

        _self._proc.stdin.write(_cmdsStr);
        _self._proc.stdin.write(os.EOL);
        _self._proc.stdin.write('echo ' + EOI);
        _self._proc.stdin.write(os.EOL);
      });

It might also be helpful for node-powershell to internally serialize multiple asynchronousinvoke() executions (perhaps with some kind of "operation queue"), since the target PowerShell process can only process one invocation at a time.
The node-powershell API also isn't helping out here, by separating into independent and potentially "racy" steps (addCommand() and invoke()) what really should be tied together.  An improved API might instead provide a way to build a set of "commands" as an entity, which can then be specifically "invoked" (with no possible confusion with other any commands, as can occur with the current API).
Usage might look like this:
    let shell = new Shell();
    let commands = new shell.Commands();
    await commands.add('echo Now I can');
    await commands.add('echo build my commands');
    await commands.add('echo as a unit');
    let output = await commands.invoke();

Hey @mattflix,
You are right about cleaning up the array of commands and in the next version I will clean it immediately after receiving the confirmation that it has passed to the PS treatment.
With regard to race condition, the library is based on promises and therefore, using the existing API, it is very easy to avoid the situation you described.
Thank you very much for turning my attention. 💯 👍

Yes, it is not very "difficult" to avoid the race, but the race is created entirely by the design of the existing API.
Due the current API, every library client must:
a) first be aware that there may be a problem (which they may not be until strange behavior emerges, possibly after they have shipped their code),
b) debug and understand the problem, and
c) possibly write extra code to ensure that any group of addCommand() call(s) and the final invoke() call are always executed as an "atomic" operation.
So, my feedback is that, a slightly different API design (like the one I proposed) would eliminate the possibility for the race altogether, rendering moot concerns a), b), and c), making the library that much more robust and reliable.


Add a E2E based performance test case

Description
This PR reimplement cull_opacity_perf__timeline_summary test as cull_opacity_perf__e2e_summary using E2E, as a trial for running performance test using E2E that's host-independent in terms of driving the test.
Related Issues
This is the first migration of performance test for go/flutter-nonhost
This is also a first step to #38329 for the new test case is self-driven.
Tests
The PR itself is adding a test case
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I signed the CLA.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I updated/added relevant documentation (doc comments with ///).
[x] All existing and new tests are passing.
[x] The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Did any tests fail when you ran them? Please read Handling breaking changes.

[x] No, no existing tests failed, so this is not a breaking change.

A few things to address:

part of dev/benchmarks/macrobenchmarks/test_driver/e2e_test.dart and dev/benchmarks/macrobenchmarks/test/util.dart may be better go to E2E;
Should we or when should we replace the original perf test case: For this one there will be duplicate on the flutter-build webpage, but I don't think eventually we need both flutter_driver version and E2E version running.

I may also need to update the macrobenchmark/readme.md, which is also the case for #61388. That will be done on whichever of the two PR who lands later.


NIFI-7192 - nifi.sh install not working on systemd servers

Thank you for submitting a contribution to Apache NiFi.
Please provide a short description of the PR here:
Description of PR
After invoking nifi.sh install, systemd manager configuration is reloaded. In this way, wrapper from init.d to systemd service is generated and the service will work smoothly. Fixes bug NIFI-7192.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[x] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[x] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[x] Has your PR been rebased against the latest commit within the target branch (typically master)?

[x] Is your initial contribution a single, squashed commit? Additional commits in response to PR reviewer feedback should be made on this branch and pushed to allow change tracking. Do not squash or use --force when pushing to allow for clean monitoring of changes.

For code changes:

[x] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[ ] Have you written or updated unit tests to verify your changes?
[x] Have you verified that the full build is successful on both JDK 8 and JDK 11?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.

@pvillard31 / @alopresto can you please take a look on this?

@rmarturano For due diligence, what distributions has this been tested against? I have two worries with this: (1) that the commands might not always be on the path and (2) that using pidof might not be reliable.
I think it might be worthwhile to add some additional checks (e.g., what's mentioned by https://www.freedesktop.org/software/systemd/man/sd_booted.html).

@jfrazee @exceptionfactory first of all thanks for your inputs.
I applied suggested changes and rebased.

@jfrazee Shall we merge it?

@jfrazee why did you hold off on merge after approving? Was more work required?


[Bug]: imgproxy not working properly?

Describe the bug
Below is the docker-compose.yml file:
services:
  teldrive:
    image: ghcr.io/tgdrive/teldrive
    restart: always
    container_name: teldrive
    volumes:
      - ./config.toml:/config.toml
      - ./session.db:/session.db
    ports:
      - 9080:8080
    networks:
      - internal
  db:
    image: ghcr.io/tgdrive/postgres
    container_name: postgres_db
    restart: always
    environment:
      - POSTGRES_USER=teldrive
      - POSTGRES_PASSWORD=secret
      - POSTGRES_DB=postgres
    volumes:
      - ./postgres_data:/var/lib/postgresql/data
    networks:
      - internal
  imgproxy:
    image: darthsim/imgproxy
    container_name: imgproxy
    environment:
      IMGPROXY_ALLOW_ORIGIN: "*"
      IMGPROXY_ENFORCE_WEBP: true
      IMGPROXY_MALLOC: "jemalloc"
    restart: always
    ports:
      - 9090:8080
    networks:
      - internal
networks:
  internal:

I updated the image resizer in the Teldrive GUI to http://imgproxy:9090 and also tried http://imgproxy:8080, but there was no output in the imgproxy logs.
I tested the network by entering the imgproxy container using exec /bin/bash, installed ping, and verified that I could reach Teldrive successfully. However, I am unable to test the connection from Teldrive since the container uses scratch with no available shell.
I assigned imgproxy a subdomain and visited it in the browser, where the page loaded as expected. I then updated the image resizer to https://resizer.domain.td, but received the following error:
imgproxy     | INFO    [2024-10-16T20:51:13Z] Started /insecure/w:360/plain/https%3A%2F%2Fresizer.domain.td%2Fapi%2Ffiles%2F019296ce-7fdc-7004-a941-2f8220ec4d99%2Fstream%2Ffolder.jpg%3Fhash%3D649bd3cd558e243af2aa50b85828f217  request_id=R5U3DMudkL5POKiC6OhFh method=GET client_ip=CLIENT_IP
imgproxy     | ERROR   [2024-10-16T20:51:43Z] Completed in 30.000314815s /insecure/w:360/plain/https%3A%2F%2Fresizer.domain.td%2Fapi%2Ffiles%2F019296ce-7fdc-7004-a941-2f8220ec4d99%2Fstream%2Ffolder.jpg%3Fhash%3D649bd3cd558e243af2aa50b85828f217  request_id=R5U3DMudkL5POKiC6OhFh method=GET status=504 client_ip=CLIENT_IP error="Can't download source image: The image request timed out: Get \"https://resizer.domain.td/api/files/019296ce-7fdc-7004-a941-2f8220ec4d99/stream/folder.jpg?hash=649bd3cd558e243af2aa50b85828f217\": dial tcp SERVER_IP:443: i/o timeout"

Repoduction

Set up Teldrive and imgproxy within the same network using the docker-compose.yml configuration above.
Set the image resizer in the Teldrive GUI to point to imgproxy.

Expected behavior
The images should be generated correctly and displayed in the web interface.
Version
1.5.3
Which Platform are you using?
Linux
Additional context
For privacy reasons, I've redacted my client and server IP addresses.
The imgproxy container is reachable via the subdomain, and the network connectivity between containers has been confirmed from the imgproxy side.

@Jopo-JP you can use host network if you are facing issues othwise use need machine ip for accesing urls.

what imgproxy actually does in teldrive? I want to test it to make sure it works


Question: is it possible to limit lines?

We have very long lines without breaks and it causes the render to slide:

Is there any chance to limit the box and add word and lines wrap?
Example: https://saveourtool.com/vuln/collection/GHSA-xh5m-8qqp-c5x7 (tab: Changes)

It looks like it is a bug happening when you press on expand:
https://github.com/Aeolun/react-diff-viewer-continued/assets/58667063/8e456e0e-be4e-4ffb-924a-3363bc07e756

You could try v4, which might solve the jumping but I don’t think it’d ultimately solve your issue because right now it doesn’t support line wrap at all.


Wrong file size units in Catalan (N, KN, DT)

Description
Having the app in Catalan language, when showing files, the file size units are shown as N, KN, DT instead of B, KB, MB

Steps To Reproduce
Open any folder with files of various sizes (B, KB, MB...)
Requirements
Units should be shown as in English: B for bytes, KB for kilobytes, MB for megabytes, etc.
I've checked the crowdin translation for Catalan and it seems to be correct there:

Files Version
<IP_ADDRESS>
Windows Version
10.0.22631.2861
Log File
debug.log

Thanks for the report, I've added this to the project board.

Just to add more detail, the bug seems to happen on all places where KB, MB, ... should be shown. For instance, in the progress indicator:

Upon checking, the file units are displayed as translated on Crowdin. If you believe it should be different, you should be able to suggest changes on Crowdin.


deploy getting started repo

To Github pages and / or Netlify

live on Netlify
https://vigorous-williams-62bdb4.netlify.com/


Clarification on ?include assymetry for relationship operations

As I read the spec:

When calling the relationship related link GET /articles/1/comments, the primary data is comment, and if you want the comment authors, you ?include=author
When calling the relationship self link GET /articles/1/relationships/comments (as well as POST, PATCH, and DELETE), the primary data are just resource identifiers, and you have to include=comments.author (which will include both the actual comment resources as well as their authors).

In other words, for the relationship related link, ?include works similarly to a resource self link, i.e. relative to the primary data of the response, but for a relationship self link, any include path must necessarily start with the name of the current relationship (e.g. comments in the example above).
Is this correct? Is this asymmetry intended?

Also, ?include=comments gives the impression that the "include context" is the "parent resource", and that it would be possible to include other article relationships, e.g. ?include=author. Is this possible? The spec seems silent about it.

Does it even make sense to use include with a relationship's self link?
If not, that should probably be clarified in the spec so this question is answered for future implementors.

Does it even make sense to use include with a relationship's self link?

It's explicitly supported by the spec:

@cmeeren: Once again it is proven that I can't read!  Thank you for pointing out the specific exposition explaining what I didn't understand correctly.
Regardless of whether the asymmetry you identified is intended, I suspect it can't reasonably be changed because of the full linkage requirement.  There is some language about sparse field sets creating an exception to that, but I'm not convinced I understand it.

Related: #1492
Sparse fieldsets:

If you say GET /articles?include=author., you get articles as primary data and authors as secondary data. There is full linkage.
If you say GET /articles?include=author&fields[article]=title, you get articles as primary data and authors as secondary data, but since you only show the title of each article and not the author field, there is not full linkage. This is the allowed exception. it would, of course, be generally impossible in this case to know which authors correspond to which articles, but it's allowed.

@cmeeren: Thank you!  Another case where my implementation doesn't get it right.  I've only been including resources where the full linkage is supported by the response document.  Fortunately, this feels very much like an edge case no sane client would choose to deal with.


DataAnalysis Exception

Issue Description
Please describe our issue, along with:

expected behavior

encountered behavior

Exception in thread "main" java.lang.NumberFormatException: For input string: "RowNumber"
        at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
        at java.lang.Integer.parseInt(Integer.java:580)
        at java.lang.Integer.parseInt(Integer.java:615)
        at org.datavec.api.writable.Text.toInt(Text.java:611)
        at org.datavec.api.transform.analysis.counter.IntegerAnalysisCounter.add(IntegerAnalysisCounter.java:82)
        at org.datavec.api.transform.analysis.counter.IntegerAnalysisCounter.add(IntegerAnalysisCounter.java:30)
        at org.datavec.local.transforms.analysis.aggregate.AnalysisAddFunction.apply(AnalysisAddFunction.java:81)
        at org.datavec.local.transforms.AnalyzeLocal.analyze(AnalyzeLocal.java:64)
        at org.datavec.local.transforms.AnalyzeLocal.analyze(AnalyzeLocal.java:50)
        at com.cch.dl4j.Test.main(Test.java:36)

Version Information
Please indicate relevant versions, including, if relevant:

Deeplearning4j version  1.0.0-beta4
Platform information (OS, etc) Windows10
CUDA version, if used 10.0
NVIDIA driver version, if in use

Additional Information
Where applicable, please also provide:

Full log or exception stack trace (ideally in a Gist: gist.github.com)
pom.xml file or similar (also in a Gist)

Contributing
If you'd like to help us fix the issue by contributing some code, but would
like guidance or help in doing so, please mention it!

This doesn't look like a bug. You have text values in your integer column, that (by definition) don't match your schema.
java.lang.NumberFormatException: For input string: "RowNumber"
Possibly a header line that needs to be removed/filtered before analysis?


Files filtering and stay alive

This pull request implemented 2 new features, the files filtering and the stay alive flag.
files filtering
By passing a dictionary (key=message to display, value=search engine) it's possible to narrow down the list of files displayed
fsel= ipywe.fileselector.FileSelectorPanel(instruction='select file', start_dir='.',
                                           filter={'notebooks': ['*.ipynb'],'csv': ['*.csv']})
fsel.show()

When passing a filter dictionary, the program will automatically add the 'All':['.'] element to the dictionary
stay alive
when the flag is passed, the application won't be removed once the user click Select

I changed the signature of filtering a bit
fsel= ipywe.fileselector.FileSelectorPanel(
    instruction='select file', start_dir='.',
    filters={'notebooks': ['*.ipynb'],'csv': ['*.csv']}, default_filter="notebooks")

When passing a filter dictionary, the program will automatically add the 'All':['.'] element to the dictionary

Now working on rearranging the layout a bit

I was looking at mac's file open dialog. It does not exactly have a "filter" widget, but it has a "search" widget on the top right corner of the panel, on top of the list of entries. That is why I put it up there.

I finished all my changes for now. Please give it a try

ok. I'm checking

I changed my mind... I really like it there. I'm wondering now about the two other buttons enter directory and select. Those always confused users. We need to find them a better name or to move them apart (like before for example)


Clone repo failed

Submodule 'scraping_utils' (https://github.com/A-Coom/coomer.party-scraper/scraping_utils) registered for path 'scraping_utils'
Cloning into 'D:/segg/tools/coomer.party-scraper/scraping_utils'...
remote: Not Found
fatal: repository 'https://github.com/A-Coom/coomer.party-scraper/scraping_utils/' not found
fatal: clone of 'https://github.com/A-Coom/coomer.party-scraper/scraping_utils' into submodule path 'D:/segg/tools/coomer.party-scraper/scraping_utils' failed
Failed to clone 'scraping_utils'. Retry scheduled
Cloning into 'D:/segg/tools/coomer.party-scraper/scraping_utils'...
remote: Not Found
fatal: repository 'https://github.com/A-Coom/coomer.party-scraper/scraping_utils/' not found
fatal: clone of 'https://github.com/A-Coom/coomer.party-scraper/scraping_utils' into submodule path 'D:/segg/tools/coomer.party-scraper/scraping_utils' failed
Failed to clone 'scraping_utils' a second time, aborting

When i run .exe file, it return this error:
Traceback (most recent call last):
  File "scrape.py", line 135, in <module>
  File "scrape.py", line 110, in main
  File "scrape.py", line 36, in download_media
  File "scraping_utils\scraping_utils.py", line 220, in multithread_download_urls
UnboundLocalError: local variable 'download_threads' referenced before assignment
[16892] Failed to execute script 'scrape' due to unhandled exception!

Thanks for opening an issue.
It appears that further error checking is required to confirm that downloadable content is found before attempting to download.
Can you please describe how you are running the .exe file? (i.e. are you double clicking it or running it in the terminal?)
- If you are double clicking it, what is the input you provide?
- If you are running it in the terminal, what is the full command?

Thanks for opening an issue.
It appears that further error checking is required to confirm that downloadable content is found before attempting to download.
Can you please describe how you are running the .exe file? (i.e. are you double clicking it or running it in the terminal?) - If you are double clicking it, what is the input you provide? - If you are running it in the terminal, what is the full command?

Thanks for reply. The error will be described below:
If I double click on the .exe file, enter the link and folder location, include video, and press Enter, I can see it fetching the post, but after that the command line disapeared. So that I choose the way, open a terminal (Command Prompt) in the folder stored .exe file, run it in terminal, do exactly when double click the .exe file, the traceback above appeared. I try with another link and it works, maybe the link I try to download have some problem. Can you try that, i will post the link below:
https://www.coomer.su/onlyfans/user/umekoj0910

Thank you for the details.
The last page was not being included in the download queue, which becomes obvious when there is only one page. I corrected this so that all pages are included and the link you provided will now work.
Please redownload release 2.0 and let me know if the problem is solved on your side.

Thanks for your efforts, the tool work perfectly. I will closed this issue.


Missing config set option

There's a config sub-command that's supposed to have get and set options ala git config pattern... the get works the set isn't there.
crictl config - Get and set crictl options

@mikebrow I can work on this if thats ok?

/assign @hickeyma

Thanks @mikebrow. I will push a PR shortly.

@mikebrow The functionality is already there to set config from the cli. It is just not very user friendly.
I pushed PR #604 as a usability improvement. Please note in the PR description that it breaks CLI backwards compatibility. So, it might not be a suitable change.

@mikebrow The functionality is already there to set config from the cli. It is just not very user friendly.
I pushed PR #604 as a usability improvement. Please note in the PR description that it breaks CLI backwards compatibility. So, it might not be a suitable change.

I see so the --set option was implemented in a silent fashion... or was the default for config if a field was provided...  hmm.. yeah that wasn't obvious

Yeah, not obvious. You called it without a flag as per this example:
$ crictl config image-endpoint unix:///run/containerd/containerd.sock


Optional Pure C# Implementation of Opus Codec

Per the Readme, I wanted to create an issue to share what I'm working on.
My end goal is to use MumbleSharp in a Xamarin application for iOS and Android. However, the current framework MumbleSharp has set up for loading binaries does not appear to be compatible with iOS, to the best of my understanding. I am admittedly not very experienced with native code in C#, and even less so with iOS, so it may yet be possible to adapt the current system to mobile.
edit: It's absolutely possible to reference static libraries on iOS, but I think it will require some refactoring of NativeMethods.cs, or a mobile-specific implementation thereof, anyway.
However, rather than pursue that route, I decided to seek out a C# implementation of the Opus Codec. Concentus is one implementation I found. They claim 40-50% of native performance, which I believe on modern devices (at least for my end use case) should be acceptable. The license looks compatible  with MumbleSharp's as well.
My chosen pathway for integration into MumbleSharp was to set it up as a new "codec", in parallel to the existing codecs. Then, in CodecSet.cs, I check the current platform and return the Concentus "Codec" instead of Opus.
The bulk of the integration is already done. I've tested with the MumbleGuiClient built for Windows, forcing GetCodec to always return the Concentus "codec", and so far it works great! Well, I know it works great for encoding; my transmissions to other clients sound crystal clear.
However, even with the regular Opus codec, when I build MumbleGuiClient for Windows, I get extremely choppy audio. That is, I hear a few ms at a time broken up by silences. I think this is related to #46, but I'm not experienced enough to say. Can anyone confirm that my symptoms are indeed "jitter"? If so, I'll also start to tackle the jitter buffer problem. When that's done, I can get back to testing decoding and playback with Concentus.
My ongoing work is available here.
edit: Upon further investigation, I really don't think it would be that hard to use the libopus binaries on iOS (see above), but it might be nice to have the pure C# implementation of Opus available as an option anyway, so I still intend to continue work on this.

Perhaps an option could be to add the appropriate build switches into nativeMethods.cs so that it switches to using the correct method for a platform and if no natively supported platform is identified it can fall back to using pure C# Opus.

FYI, with my work on the jitter buffer I was able to confirm that this C# implementation works for both playback and recording (including on iOS!) As you said, we'll want a more refined system for detecting whether or not to use it before submitting a PR. I'll hopefully get around to that cleanup work soon as part of my app development.


Support custom raycasting implementations

(Ported to GitHub, reference 20077217)
Some of the MRW apps use "custom" raycasting for certain interactions. It does not appear that there is a way to provide a custom raycaster with the MRTK vNext input system. This poses a problem when trying to adopt MRTK vNext (at least the input system) for MRW.
One of the requirements in was that we override the default RayCast logic that HTK has, and while performing Raycasts we consider whether we hit a hologram, SR mesh or a hole in the SR mesh. If we have a hole in the SR mesh, we still generate a hit point for our annotations to get placed at. Monterrey input system had the ability to allow consuming apps to override the raycast logic. And so this was identified as a potential feature parity gap between the app's existing input system and HoloToolKit/MRTK.

@wiwei - these folks would be good contacts to validate any proposed solutions to this issue: @Kjakubzak, @rferrese, @ritijain

@Kjakubzak, @rferrese, @ritijain do you guys have some more specific asks here (i.e. are there some specific points in the code that you can help point to that are inflexible, or have snippets of code that show the overall pain points and illustrate things?)
I want to get sufficient detail within this issue that we can both understand what it is we're trying to improve and then also understand how to validate that as well.

Also @smcbeth may have thoughts here.

This is a feature request that would benefit the maps sdk project as well.
It would be great if the focus/gaze cursors and controller rays would follow the surface of the map; however, the map doesn't generate a collider on the fly (a lot of perf overhead for that), so it's not ray-castable through Unity's physics system.

@wiwei  This ask was due to multiple scenarios that were missing in HTK, and due to some custom solutions that our apps had. Some of the things have definitely been fixed in MRTK and having the ability to write custom Gaze/pointer  systems because of availability  of more interfaces  definitely makes this easier.

The version of HTK that we were using only did Layer prioritization based comparison of hit results, and not distance based comparison, which is why we had to override/swap what HTK did. An ability to override the prioritization logic would help.
Sometimes depending on scenario, we might need to prioritize a distance based comparison of raycast hit result rather than a layer based prioritization. So i would like the ability to update raycast hit prioritization logic based on application scenario on the fly.

I guess the ask boils down to a customizable raycast result prioritization rather than the raycast itself. (i am looking at GetPrioritizedHitResult in https://github.com/microsoft/MixedRealityToolkit-Unity/blob/mrtk_release/Assets/MixedRealityToolkit.Services/InputSystem/FocusProvider.cs)

@julenka would love your input here as this may affect interaction, near/far based on distance.
This is an ask for support both layered and distance based raycasting. for example, if an app wants to prioritize UI even when UI is behind SR mesh.

Not blocking currently, may cause regression in some edge cases. We will look to fix before GA

I think this falls under our principle of "easy to customize" and should be considered for GA. We want to provide reliable defaults that are easy to customize. If we don't make it easy to customize now it will get harder to do in future since once GA is out it will be harder to make breaking changes.

Note that another issue was filed which has the same request:
https://github.com/microsoft/MixedRealityToolkit-Unity/issues/4379
I duped that issue to this.


CLOUDSTACK-9267: String is not localized on create instance wizards.

Repro Steps:

Setup basic environments as normal.
Open a browser, go to Web Console.
Upload a iso template.
Go to "Instances" page and add new instance.
Check the strings on create instance wizards.

Expected Result:
All the strings should be localized on create instance wizards.
Actual Result:
Some strings are not localized on create instance wizards.
Language:
JA -> Fail
SC -> Fail
Fix:
Fixed the hard coded string.

more explanation then code, but makes sense. mostly cosmatic: LGTM

I thought of making a small explanation. But I follow this template while making a PR so that it would be easy for committer to review very fast. Anyway Thanks @DaanHoogland

There is one more localised issue in the project page, So instead of creating a new one adding it to this PR only.

LGTM as well

@nitin-maharana,
Your changes LGTM.
I just noticed that function “_l”, is that something we have created?

@rafaelweingartner : Its already present in our code. It translates the dictionary keys.

@nitin-maharana have you tested everything? @DaanHoogland  Can we merge this? And then forward it to master

@rafaelweingartner : I have tested all changes.

@rafaelweingartner go ahead, if you LGTM as well.

merged to 4.7, and then forwarded to master

Do we need to add a resources file to the Jenkins box to provide translations for these entries?
I believe this is the cause of the recent jenkins failure.  Does that make sense?
http://markmail.org/message/svyyit7klk6ixvya?q=list:org.apache.incubator.cloudstack-*+Build+failed+in+Jenkins:+build-master-slowbuild+%233320

@swill those entries already exist.
That failure in Jenkins seems to be happening even before Feb. 24th
It seems that I do not have access to Jenkins, can someone with access provide us with the log of that new warning that was generated.

Thanks.  I will dig a bit deeper and and see if I can figure out why the failures are happening in jenkins.

Sorry for the false alarm here.  I didn't dig deep enough initially.  It seems that the Jenkins slave is out of disk space which is resulting in errors.

ACS CI BVT Run
Sumarry:
Build Number 101
Hypervisor xenserver
NetworkType Advanced
Passed=104
Failed=10
Skipped=4
The follwing tests have known issues
test_vpc_remote_access_vpn
test_vpc_site2site_vpn
test_01_test_vm_volume_snapshot
test_02_vpc_privategw_static_routes
test_03_rvpc_privategw_static_routes
test_04_change_offering_small
ContextSuite context=TestNiciraContoller>:setup
test_01_primary_storage_iscsi
test02_internallb_haproxy_stats_on_all_interfaces
test_01_internallb_roundrobin_1VPC_3VM_HTTP_port80
ContextSuite context=TestDeployVM>:setup
test_04_extract_template
test_04_extract_Iso
test_07_list_default_iso
Link to logs Folder (search by build_no): https://www.dropbox.com/sh/yj3wnzbceo9uef2/AAB6u-Iap-xztdm6jHX9SjPja?dl=0
Failed tests:

integration.smoke.test_privategw_acl.TestPrivateGwACL

test_01_vpc_privategw_acl Failed in this run

integration.smoke.test_guest_vlan_range.TestDedicateGuestVlanRange

test_dedicateGuestVlanRange Failed in this run

Skipped tests:
test_vm_nic_adapter_vmxnet3
test_deploy_vgpu_enabled_vm
test_06_copy_template
test_06_copy_iso
Passed test suits:
integration.smoke.test_deploy_vm_with_userdata.TestDeployVmWithUserData
integration.smoke.test_affinity_groups_projects.TestDeployVmWithAffinityGroup
integration.smoke.test_portable_publicip.TestPortablePublicIPAcquire
integration.smoke.test_over_provisioning.TestUpdateOverProvision
integration.smoke.test_global_settings.TestUpdateConfigWithScope
integration.smoke.test_scale_vm.TestScaleVm
integration.smoke.test_service_offerings.TestCreateServiceOffering
integration.smoke.test_loadbalance.TestLoadBalance
integration.smoke.test_routers.TestRouterServices
integration.smoke.test_reset_vm_on_reboot.TestResetVmOnReboot
integration.smoke.test_snapshots.TestSnapshotRootDisk
integration.smoke.test_deploy_vms_with_varied_deploymentplanners.TestDeployVmWithVariedPlanners
integration.smoke.test_network.TestDeleteAccount
integration.smoke.test_non_contigiousvlan.TestUpdatePhysicalNetwork
integration.smoke.test_deploy_vm_iso.TestDeployVMFromISO
integration.smoke.test_public_ip_range.TestDedicatePublicIPRange
integration.smoke.test_multipleips_per_nic.TestDeployVM
integration.smoke.test_regions.TestRegions
integration.smoke.test_affinity_groups.TestDeployVmWithAffinityGroup
integration.smoke.test_network_acl.TestNetworkACL
integration.smoke.test_pvlan.TestPVLAN
integration.smoke.test_volumes.TestCreateVolume
integration.smoke.test_ssvm.TestSSVMs
integration.smoke.test_nic.TestNic
integration.smoke.test_deploy_vm_root_resize.TestDeployVM
integration.smoke.test_resource_detail.TestResourceDetail
integration.smoke.test_secondary_storage.TestSecStorageServices
integration.smoke.test_vm_life_cycle.TestDeployVM
integration.smoke.test_disk_offerings.TestCreateDiskOffering

ACS CI BVT Run
Sumarry:
Build Number 102
Hypervisor xenserver
NetworkType Advanced
Passed=104
Failed=13
Skipped=4
The follwing tests have known issues
test_vpc_remote_access_vpn
test_vpc_site2site_vpn
test_01_test_vm_volume_snapshot
test_02_vpc_privategw_static_routes
test_03_rvpc_privategw_static_routes
test_04_change_offering_small
ContextSuite context=TestNiciraContoller>:setup
test_01_primary_storage_iscsi
test02_internallb_haproxy_stats_on_all_interfaces
test_01_internallb_roundrobin_1VPC_3VM_HTTP_port80
ContextSuite context=TestDeployVM>:setup
test_04_extract_template
test_04_extract_Iso
test_07_list_default_iso
Link to logs Folder (search by build_no): https://www.dropbox.com/sh/yj3wnzbceo9uef2/AAB6u-Iap-xztdm6jHX9SjPja?dl=0
Failed tests:

integration.smoke.test_guest_vlan_range.TestDedicateGuestVlanRange

test_dedicateGuestVlanRange Failing since 2 runs

ContextSuite context=TestDedicateGuestVlanRange>:teardown Failed in this run

integration.smoke.test_loadbalance.TestLoadBalance

test_01_create_lb_rule_src_nat Failed in this run

Skipped tests:
test_vm_nic_adapter_vmxnet3
test_deploy_vgpu_enabled_vm
test_06_copy_template
test_06_copy_iso
Passed test suits:
integration.smoke.test_deploy_vm_with_userdata.TestDeployVmWithUserData
integration.smoke.test_affinity_groups_projects.TestDeployVmWithAffinityGroup
integration.smoke.test_portable_publicip.TestPortablePublicIPAcquire
integration.smoke.test_over_provisioning.TestUpdateOverProvision
integration.smoke.test_global_settings.TestUpdateConfigWithScope
integration.smoke.test_scale_vm.TestScaleVm
integration.smoke.test_service_offerings.TestCreateServiceOffering
integration.smoke.test_routers.TestRouterServices
integration.smoke.test_reset_vm_on_reboot.TestResetVmOnReboot
integration.smoke.test_snapshots.TestSnapshotRootDisk
integration.smoke.test_deploy_vms_with_varied_deploymentplanners.TestDeployVmWithVariedPlanners
integration.smoke.test_network.TestDeleteAccount
integration.smoke.test_non_contigiousvlan.TestUpdatePhysicalNetwork
integration.smoke.test_deploy_vm_iso.TestDeployVMFromISO
integration.smoke.test_public_ip_range.TestDedicatePublicIPRange
integration.smoke.test_multipleips_per_nic.TestDeployVM
integration.smoke.test_regions.TestRegions
integration.smoke.test_affinity_groups.TestDeployVmWithAffinityGroup
integration.smoke.test_network_acl.TestNetworkACL
integration.smoke.test_pvlan.TestPVLAN
integration.smoke.test_volumes.TestCreateVolume
integration.smoke.test_ssvm.TestSSVMs
integration.smoke.test_nic.TestNic
integration.smoke.test_deploy_vm_root_resize.TestDeployVM
integration.smoke.test_resource_detail.TestResourceDetail
integration.smoke.test_secondary_storage.TestSecStorageServices
integration.smoke.test_vm_life_cycle.TestDeployVM
integration.smoke.test_disk_offerings.TestCreateDiskOffering


please make a release if the master is stable

I'm planning on making an AUR package.

Calling it stable may be a bit much. But i'll tag a release.

thanks :)


Implement a SOCKSv5 client

Implement a SOCKSv5 client according to RFC 1928. Server implementation will be added in another PR to keep sizes down.
https://datatracker.ietf.org/doc/html/rfc1928
A few meaningful changes:

Add all relevant types used across SOCKS clients and servers
Add a state machine used to manage a connection from a clients side
Add a channel handler that should be added at the very start of a channel pipeline

@avolokhov FYI :)

@Lukasa FYI I'll go through and document what's missing when you're happy