Register Microgrids.jl

@JuliaRegistrator register
(in order to retrigger the checks for https://github.com/JuliaRegistries/General/pull/71212)

Registration pull request created: JuliaRegistries/General/71214
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.9.0 -m "<description of version>" bc0e96eba0b12053d18ae67f054db00c9db29c64
git push origin v0.9.0

Also, note the warning: This looks like a new registration that registers version 0.9.0.
Ideally, you should register an initial release with 0.0.1, 0.1.0 or 1.0.0 version numbers
This can be safely ignored. However, if you want to fix this you can do so. Call register() again after making the fix. This will update the Pull request.

@JuliaRegistrator register
(in order to retrigger the checks, now for 2nd attempt https://github.com/JuliaRegistries/General/pull/71214)

Registration pull request updated: JuliaRegistries/General/71214
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.9.0 -m "<description of version>" ce89059051b753f8724f36728aafbba49bce3a06
git push origin v0.9.0

Also, note the warning: This looks like a new registration that registers version 0.9.0.
Ideally, you should register an initial release with 0.0.1, 0.1.0 or 1.0.0 version numbers
This can be safely ignored. However, if you want to fix this you can do so. Call register() again after making the fix. This will update the Pull request.

@JuliaRegistrator register (after fixing Julia version compact ~1.6 → 1.6)

Registration pull request updated: JuliaRegistries/General/71214
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.9.0 -m "<description of version>" 98a2aa7b20c6594b778aa00fa3cc2933433754ab
git push origin v0.9.0

Also, note the warning: This looks like a new registration that registers version 0.9.0.
Ideally, you should register an initial release with 0.0.1, 0.1.0 or 1.0.0 version numbers
This can be safely ignored. However, if you want to fix this you can do so. Call register() again after making the fix. This will update the Pull request.

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

Tagging done: https://github.com/Microgrids-X/Microgrids.jl/releases/tag/v0.9.0

Try register v0.10.1. I misinterpreted the notion of commit comment (it should be inside the commit message...)
@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/92320
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.10.1 -m "<description of version>" 11ce7c19f852091a3f1934ea8542ba2df52b3ebc
git push origin v0.10.1

Also, note the warning: Version 0.10.1 skips over 0.10.0
This can be safely ignored. However, if you want to fix this you can do so. Call register() again after making the fix. This will update the Pull request.

@JuliaRegistrator register
for 0.10.2

Registration pull request created: JuliaRegistries/General/93347
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.10.2 -m "<description of version>" 4dfe9a9af2849244af417dc33dca85709692ed63
git push origin v0.10.2

tagging and release done manually (https://github.com/Microgrids-X/Microgrids.jl/releases/tag/v0.10.2)

@JuliaRegistrator register
for 0.11.0

Registration pull request created: JuliaRegistries/General/112027
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.11.0 -m "<description of version>" 26de0de0267ad26a5af03f11269a7fe6bd1bb063
git push origin v0.11.0

Tagging and release done manually: https://github.com/Microgrids-X/Microgrids.jl/releases/tag/v0.11.0
Also, a CHANGES.md file was added afterwards to cumulate these release notes


ui-jq jQuery Passthrough doesn't support ng-model (for sliders etc)

There's no way to use jqueryui's widgets that should/could be bound to ng-model (slider, progressbar, autocomplete?, spinner) ng-model should be set up to update the value of the plugin for these types.
i'll just leave this here: (this additional directive works for me)

function uiJq($timeout, $log) {
    return {
        require: '?ngModel',
        link: function(scope, elm, attrs, ngModel) {
            var block = false;
            if (ngModel) {
                ngModel.$render = function() {
                    block = true;
                    try {
                        plugin('value', ngModel.$viewValue);
                    } finally {
                        block = false;
                    }
                };
            }
            //specific events for slider, could add more.
            elm.on('slidechange slide', function(evt, ui) {
                if (!block) {
                    scope.$apply(function() {
                        ngModel.$setViewValue(plugin('value'));
                    });
                }
            });

            function plugin() {
                if (elm.is(':ui-' + attrs.uiJq)) {
                    return elm[attrs.uiJq].apply(elm, arguments);
                }
            }
        }
    }
}

UI.Utils modules was split in individuals repositories. If still valid, please consider re-submitting the issue on its dedicated issue tracker.
See the README for details.


Use an adaptive design, for tablet/mobile for pub.dartlang.org

Some general notes:
Add social sharing buttons
Add a "send feedback" link
Use an adaptive design, for tablet/mobile

This issue has been moved to dart-lang/pub-dartlang#298.


Extension causes high cpu load

Issue Type: Performance
Extension Name: bracket-pair-colorizer-2
Extension Version: 0.0.28
OS Version: Linux x64 4.15.0-46-generic
VSCode version: 1.32.3

:warning: Make sure to attach this file from your home-directory: /home/yudi/CoenraadS.bracket-pair-colorizer-2-unresponsive.cpuprofile.txt :warning:
Find more details here: https://github.com/Microsoft/vscode/wiki/Explain:-extension-causes-high-cpu-load

Duplicate of #55. Please close this and post there instead.
@yudiandela


mjolnir: 1.5.0 -> 1.6.4

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for mjolnir is: "A moderation tool for Matrix"
meta.homepage for mjolnir is: "https://github.com/matrix-org/mjolnir"
meta.changelog for mjolnir is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
Warning: a test defined in passthru.tests did not pass
found 1.6.1 with grep in /nix/store/8z12f64dhhnxmiasz9bvkha2gpjwbsky-mjolnir-1.6.1
found 1.6.1 in filename of file in /nix/store/8z12f64dhhnxmiasz9bvkha2gpjwbsky-mjolnir-1.6.1

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
mjolnir

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/8z12f64dhhnxmiasz9bvkha2gpjwbsky-mjolnir-1.6.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A mjolnir https://github.com/r-ryantm/nixpkgs/archive/aa05bb08f09bc480e7cad491c7dd7228b657a8cc.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/8z12f64dhhnxmiasz9bvkha2gpjwbsky-mjolnir-1.6.1
ls -la /nix/store/8z12f64dhhnxmiasz9bvkha2gpjwbsky-mjolnir-1.6.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

mjolnir

Maintainer pings
cc @jojosch for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for mjolnir is: A moderation tool for Matrix
meta.homepage for mjolnir is: https://github.com/matrix-org/mjolnir
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
Warning: a test defined in passthru.tests did not pass
found 1.6.4 with grep in /nix/store/l83cpqw84wax6171y0ygc8x0m76dsmb8-mjolnir-1.6.4
found 1.6.4 in filename of file in /nix/store/l83cpqw84wax6171y0ygc8x0m76dsmb8-mjolnir-1.6.4

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
mjolnir

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/l83cpqw84wax6171y0ygc8x0m76dsmb8-mjolnir-1.6.4 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A mjolnir https://github.com/r-ryantm/nixpkgs/archive/eb971650729956eca7059a4189a36ca43bc20fc3.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/l83cpqw84wax6171y0ygc8x0m76dsmb8-mjolnir-1.6.4
ls -la /nix/store/l83cpqw84wax6171y0ygc8x0m76dsmb8-mjolnir-1.6.4/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

mjolnir

Maintainer pings
cc @jojosch for testing.

@ofborg build mjolnir mjolnir.passthru.tests

Result of nixpkgs-review pr 205820 run on aarch64-darwin 1

@ofborg test mjolnir

Needs to be migrated to Node.js 18 at the minimum.


Improve disk I/O efficiency at DSC job preparation step

Currently the preparation stage of DSC jobs uses the same routine as the execution stage which records all information including signature of parameters, auto-generated file names in MD5, etc; yet it is not necessary to keep track of them because the files will have to be renamed before execution starts. It is thus good idea to implement a separate routine for job preparation stage that involves minimal disk I/O operations. Current implementation is not efficient: it takes 4 seconds on an SSD to prepare for only a few hundred jobs.

Done -- via changes to both dsc2 and the upstream pysos library.


Refactor code for routing and navbar using a dictionary with pageName-viewName

This is a technical issue related to code management.
Current snippets of code:
# In App.js
<Route exact path="/links" render={(props) => <Links {...props}/>} />
<Route exact path="/summary" render={(props) => <Summary {...props}/>} />
<Route exact path="/clusters" render={(props) => <Cluster {...props}/>} />

# In navbar.js
<Link
  to="/clusters"
  onClick={() => {
    setView("Clusters");
  }}
>
  <span {...navLinkProps('/clusters', 0.3)}>
    Clusters
  </span>
</Link>

<Link
  to="/links"
  onClick={() => {
    setView("Helpful Links");
  }}
>
  <span {...navLinkProps('/links', 0.4)}>
    Helpful Links
  </span>
</Link>

As discussed in earlier PR https://github.com/covid19india/covid19india-react/pull/291 , this can be written in following way which will be better:

Create a dictionary with ViewName, Pathname key value pair to be used across the project, including in App.js and Navbar.js . Loop through this dictionary in both places.
In Navbar js create a new component for these links and create them by looping through the above mentioned dictionary.

We can reduce redundancy of code this way and also make adding new Views/Links easier.

Please assign it to me. I would like to work on it.


return username instead id

function get_media_likers
could you return also username?

@alexshavelev44
Yes, if you take a look at the function you can change it to return not only user['pk']
Just add to your script the rewritten function and use it as you wish.
def get_likers(bot, media_id):
    bot.api.get_media_likers(media_id)
    if "users" not in bot.api.last_json:
        return []
    return bot.api.last_json["users"]

of course, i can. but it strange some funcs return the only id, other whole object

feel free to open a pull requests, this library contains a lof of shitcode

@ohld How can I use 'get_user_id_from_username — Get user_id by username' in a script exactly?
would you put an example in a script?
I couldn't get it as I followed the available examples on the website and docs.
Thanks in advance.

@KazemRahimzadeh  Here is an example where I scrape the userid from "username" and then print the username and userid.
user_id = bot.get_user_id_from_username("yourusername") username = bot.get_username_from_user_id(user_id) print(f"Welcome {username} your userid is {user_id}")


What dependencies need for production and what can be moved to dev?

dingo and xenthron move to require


[Question]Failed to install yurt-manager

What happened:
Failed to install openyurt 1.4.0, I'm not sure which version I had installed, the helm release showed that:
root@beijing:~/yurt-manager# helm list
NAME        	NAMESPACE  	REVISION	UPDATED                                	STATUS  	CHART             	APP VERSION
yurt-hub    	kube-system	1       	2023-11-06 02:42:54.317822487 +0000 UTC	failed  	yurthub-1.4.0     	1.4.0
yurt-manager	kube-system	1       	2023-11-06 02:01:43.085102655 +0000 UTC	deployed	yurt-manager-1.4.0	1.4.0

but the image of yurt-manager is v1.3.4.
I encounters some errors:

unkown flag "Error: unknown flag: --leader-elect-resource-name"

Error: unknown flag: --leader-elect-resource-name
Usage:
  yurt-manager [flags]

Generic flags:

      --controllers strings                    A list of controllers to enable. '*' enables all on-by-default controllers, 'foo' enables the controller named 'foo', '-foo' disables the controller named 'foo'. (default [*])
      --disable-independent-webhooks strings   A list of webhooks to disable. '*' disables all webhooks, 'foo' disables the webhook named 'foo'.
      --enable-leader-election                 Whether you need to enable leader election. (default true)
      --feature-gates mapStringBool            A set of key=value pairs that describe feature gates for alpha/experimental features. Options are:
                                               AllAlpha=true|false (ALPHA - default=false)
                                               AllBeta=true|false (BETA - default=false)
                                               RavenL7Proxy=true|false (ALPHA - default=false)
      --health-probe-addr string               The address the healthz/readyz endpoint binds to. (default ":10272")
      --metrics-addr string                    The address the metric endpoint binds to. (default ":10271")
      --rest-config-burst int                  rest-config-burst. (default 50)
      --rest-config-qps int                    rest-config-qps. (default 30)
      --version                                Print the version information, and then exit
      --webhook-port int                       The port on which to serve HTTPS for webhook server. It can't be switched off with 0 (default 10273)
      --working-namespace string               The namespace where the yurt-manager is working. (default "kube-system")

Nodepool controller flags:

      --create-default-pool   Create default cloud/edge pools if indicated.

Yurtstaticset controller flags:

      --node-servant-image string   Specify node servant pod image used for YurtStaticSet upgrade. (default "openyurt/node-servant:latest")

Global flags:

      --add_dir_header                   If true, adds the file directory to the header of the log messages
      --alsologtostderr                  log to standard error as well as files
  -h, --help                             help for yurt-manager
      --log-flush-frequency duration     Maximum number of seconds between log flushes (default 5s)
      --log_backtrace_at traceLocation   when logging hits line file:N, emit a stack trace (default :0)
      --log_dir string                   If non-empty, write log files in this directory
      --log_file string                  If non-empty, use this log file
      --log_file_max_size uint           Defines the maximum size a log file can grow to. Unit is megabytes. If the value is 0, the maximum file size is unlimited. (default 1800)
      --logtostderr                      log to standard error instead of files (default true)
      --one_output                       If true, only write logs to their native severity level (vs also writing to each lower severity level)
      --skip_headers                     If true, avoid header prefixes in the log messages
      --skip_log_headers                 If true, avoid headers when opening log files
      --stderrthreshold severity         logs at or above this threshold go to stderr (default 2)
  -v, --v Level                          number for the log level verbosity (default 0)
      --vmodule moduleSpec               comma-separated list of pattern=N settings for file-filtered logging

I removed it from deployment yurt-manager and then I got second error.

Failed to watch *v1.Secret: failed to list *v1.Secret: secrets is forbidden: User "system:serviceaccount:kube-system:yurt-manager" cannot list resource "secrets" in API group "" in the namespace "kube-system"

I1106 03:02:09.472051       1 reflector.go:219] Starting reflector *v1.Secret (0s) from pkg/mod/k8s.io/client-go@v0.22.3/tools/cache/reflector.go:167
I1106 03:02:09.472066       1 reflector.go:255] Listing and watching *v1.Secret from pkg/mod/k8s.io/client-go@v0.22.3/tools/cache/reflector.go:167
I1106 03:02:09.472193       1 reflector.go:219] Starting reflector *v1.MutatingWebhookConfiguration (0s) from pkg/mod/k8s.io/client-go@v0.22.3/tools/cache/reflector.go:167
I1106 03:02:09.472331       1 reflector.go:255] Listing and watching *v1.MutatingWebhookConfiguration from pkg/mod/k8s.io/client-go@v0.22.3/tools/cache/reflector.go:167
I1106 03:02:09.472675       1 reflector.go:219] Starting reflector *v1.ValidatingWebhookConfiguration (0s) from pkg/mod/k8s.io/client-go@v0.22.3/tools/cache/reflector.go:167
I1106 03:02:09.472829       1 reflector.go:255] Listing and watching *v1.ValidatingWebhookConfiguration from pkg/mod/k8s.io/client-go@v0.22.3/tools/cache/reflector.go:167
E1106 03:02:09.476882       1 reflector.go:138] pkg/mod/k8s.io/client-go@v0.22.3/tools/cache/reflector.go:167: Failed to watch *v1.Secret: failed to list *v1.Secret: secrets is forbidden: User "system:serviceaccount:kube-system:yurt-manager" cannot list resource "secrets" in API group "" in the namespace "kube-system"
I1106 03:02:09.477244       1 webhook_controller.go:125] ValidatingWebhookConfiguration yurt-manager-validating-webhook-configuration added
I1106 03:02:09.478205       1 webhook_controller.go:108] MutatingWebhookConfiguration yurt-manager-mutating-webhook-configuration added
I1106 03:02:10.355671       1 reflector.go:255] Listing and watching *v1.Secret from pkg/mod/k8s.io/client-go@v0.22.3/tools/cache/reflector.go:167
E1106 03:02:10.359119       1 reflector.go:138] pkg/mod/k8s.io/client-go@v0.22.3/tools/cache/reflector.go:167: Failed to watch *v1.Secret: failed to list *v1.Secret: secrets is forbidden: User "system:serviceaccount:kube-system:yurt-manager" cannot list resource "secrets" in API group "" in the namespace "kube-system"
I1106 03:02:12.316235       1 reflector.go:255] Listing and watching *v1.Secret from pkg/mod/k8s.io/client-go@v0.22.3/tools/cache/reflector.go:167
E1106 03:02:12.323776       1 reflector.go:138] pkg/mod/k8s.io/client-go@v0.22.3/tools/cache/reflector.go:167: Failed to watch *v1.Secret: failed to list *v1.Secret: secrets is forbidden: User "system:serviceaccount:kube-system:yurt-manager" cannot list resource "secrets" in API group "" in the namespace "kube-system"
I1106 03:02:18.410158       1 reflector.go:255] Listing and watching *v1.Secret from pkg/mod/k8s.io/client-go@v0.22.3/tools/cache/reflector.go:167
E1106 03:02:18.417307       1 reflector.go:138] pkg/mod/k8s.io/client-go@v0.22.3/tools/cache/reflector.go:167: Failed to watch *v1.Secret: failed to list *v1.Secret: secrets is forbidden: User "system:serviceaccount:kube-system:yurt-manager" cannot list resource "secrets" in API group "" in the namespace "kube-system"
I1106 03:02:25.073674       1 reflector.go:255] Listing and watching *v1.Secret from pkg/mod/k8s.io/client-go@v0.22.3/tools/cache/reflector.go:167
E1106 03:02:25.081265       1 reflector.go:138] pkg/mod/k8s.io/client-go@v0.22.3/tools/cache/reflector.go:167: Failed to watch *v1.Secret: failed to list *v1.Secret: secrets is forbidden: User "system:serviceaccount:kube-system:yurt-manager" cannot list resource "secrets" in API group "" in the namespace "kube-system"
E1106 03:02:29.472178       1 deleg.go:144] setup "msg"="unable to initialize webhook" "error"="failed to prepare certificate for webhook within 20s"

So I checked role yurt-manager-role and got this:
- apiGroups:
  - ""
  resources:
  - secrets
  verbs:
  - create
  - get
  - patch
  - update
- apiGroups:
  - ""
  resources:
  - secrets
  verbs:
  - get
  - update

It's weird you have another setting for secrets.
I added list and watch to verbs and then got third problem.

yurt-manager kept restarting and no explict errors.

I1106 03:11:40.079494       1 deleg.go:130] setup "msg"="Starting metrics server"  "path"="/metrics"
I1106 03:11:40.079777       1 server.go:213] controller-runtime/webhook/webhooks "msg"="Starting webhook server"
I1106 03:11:40.080289       1 deleg.go:130] controller-runtime/certwatcher "msg"="Updated current TLS certificate"
I1106 03:11:40.080610       1 deleg.go:130] controller-runtime/webhook "msg"="Serving webhook server"  "host"="<IP_ADDRESS>" "port"=10273
I1106 03:11:40.080895       1 deleg.go:130] controller-runtime/certwatcher "msg"="Starting certificate watcher"
I1106 03:11:40.082575       1 shared_informer.go:270] caches populated
I1106 03:11:40.083673       1 leaderelection.go:352] lock is held by yurt-manager-f4f5c8d4c-k62fg_d6206d32-d358-4454-bcea-27b66c827743 and has not yet expired
I1106 03:11:40.083694       1 leaderelection.go:253] failed to acquire lease kube-system/yurt-manager
I1106 03:11:42.655323       1 leaderelection.go:352] lock is held by yurt-manager-f4f5c8d4c-k62fg_d6206d32-d358-4454-bcea-27b66c827743 and has not yet expired
I1106 03:11:42.655596       1 leaderelection.go:253] failed to acquire lease kube-system/yurt-manager
I1106 03:11:45.130863       1 leaderelection.go:352] lock is held by yurt-manager-f4f5c8d4c-k62fg_d6206d32-d358-4454-bcea-27b66c827743 and has not yet expired
I1106 03:11:45.131172       1 leaderelection.go:253] failed to acquire lease kube-system/yurt-manager
I1106 03:11:49.358357       1 leaderelection.go:352] lock is held by yurt-manager-f4f5c8d4c-k62fg_d6206d32-d358-4454-bcea-27b66c827743 and has not yet expired
I1106 03:11:49.358478       1 leaderelection.go:253] failed to acquire lease kube-system/yurt-manager
I1106 03:11:52.173634       1 leaderelection.go:352] lock is held by yurt-manager-f4f5c8d4c-k62fg_d6206d32-d358-4454-bcea-27b66c827743 and has not yet expired
I1106 03:11:52.173761       1 leaderelection.go:253] failed to acquire lease kube-system/yurt-manager
I1106 03:11:55.704935       1 leaderelection.go:258] successfully acquired lease kube-system/yurt-manager
I1106 03:11:55.705290       1 recorder.go:103] setup/events "msg"="Normal"  "message"="yurt-manager-f4f5c8d4c-k62fg_be64afdd-cf5c-4f43-b61d-08179337a4bf became leader" "object"={"kind":"Lease","namespace":"kube-system","name":"yurt-manager","uid":"a3dcb022-680f-4ca0-a597-78db8226080f","apiVersion":"coordination.k8s.io/v1","resourceVersion":"8543"} "reason"="LeaderElection"
I1106 03:11:55.705477       1 controller.go:178] setup/controller/yurtstaticset "msg"="Starting EventSource"  "source"="kind source: *v1alpha1.YurtStaticSet"
I1106 03:11:55.705512       1 controller.go:178] setup/controller/yurtstaticset "msg"="Starting EventSource"  "source"="kind source: *v1.Node"
I1106 03:11:55.705528       1 controller.go:178] setup/controller/yurtstaticset "msg"="Starting EventSource"  "source"="kind source: *v1.Pod"
I1106 03:11:55.705541       1 controller.go:178] setup/controller/yurtstaticset "msg"="Starting EventSource"  "source"="kind source: *v1.Pod"
I1106 03:11:55.705554       1 controller.go:186] setup/controller/yurtstaticset "msg"="Starting Controller"
I1106 03:11:55.712275       1 controller.go:178] setup/controller/servicetopology-endpoints "msg"="Starting EventSource"  "source"="kind source: *v1.Service"
I1106 03:11:55.712324       1 controller.go:178] setup/controller/servicetopology-endpoints "msg"="Starting EventSource"  "source"="kind source: *v1beta1.NodePool"
I1106 03:11:55.712344       1 controller.go:186] setup/controller/servicetopology-endpoints "msg"="Starting Controller"
I1106 03:11:55.714397       1 controller.go:178] setup/controller/servicetopology-endpointslice "msg"="Starting EventSource"  "source"="kind source: *v1.Service"
I1106 03:11:55.714436       1 controller.go:178] setup/controller/servicetopology-endpointslice "msg"="Starting EventSource"  "source"="kind source: *v1beta1.NodePool"
I1106 03:11:55.714454       1 controller.go:186] setup/controller/servicetopology-endpointslice "msg"="Starting Controller"
I1106 03:11:55.714606       1 controller.go:178] setup/controller/yurtappset "msg"="Starting EventSource"  "source"="kind source: *v1alpha1.YurtAppSet"
I1106 03:11:55.714634       1 controller.go:178] setup/controller/yurtappset "msg"="Starting EventSource"  "source"="kind source: *v1.StatefulSet"
I1106 03:11:55.714656       1 controller.go:178] setup/controller/yurtappset "msg"="Starting EventSource"  "source"="kind source: *v1.Deployment"
I1106 03:11:55.714675       1 controller.go:186] setup/controller/yurtappset "msg"="Starting Controller"
I1106 03:11:55.715110       1 controller.go:178] setup/controller/yurtappdaemon "msg"="Starting EventSource"  "source"="kind source: *v1alpha1.YurtAppDaemon"
I1106 03:11:55.715149       1 controller.go:178] setup/controller/yurtappdaemon "msg"="Starting EventSource"  "source"="kind source: *v1alpha1.NodePool"
I1106 03:11:55.715173       1 controller.go:186] setup/controller/yurtappdaemon "msg"="Starting Controller"
I1106 03:11:55.715430       1 controller.go:178] setup/controller/csrapprover "msg"="Starting EventSource"  "source"="kind source: *v1.CertificateSigningRequest"
I1106 03:11:55.715451       1 controller.go:186] setup/controller/csrapprover "msg"="Starting Controller"
I1106 03:11:55.715702       1 controller.go:178] setup/controller/delegatelease "msg"="Starting EventSource"  "source"="kind source: *v1.Lease"
I1106 03:11:55.715731       1 controller.go:186] setup/controller/delegatelease "msg"="Starting Controller"
I1106 03:11:55.716005       1 controller.go:178] setup/controller/podbinding "msg"="Starting EventSource"  "source"="kind source: *v1.Node"
I1106 03:11:55.716034       1 controller.go:186] setup/controller/podbinding "msg"="Starting Controller"
I1106 03:11:55.716321       1 controller.go:178] setup/controller/ravenl3-gateway "msg"="Starting EventSource"  "source"="kind source: *v1alpha1.Gateway"
I1106 03:11:55.716356       1 controller.go:178] setup/controller/ravenl3-gateway "msg"="Starting EventSource"  "source"="kind source: *v1.Node"
I1106 03:11:55.716373       1 controller.go:186] setup/controller/ravenl3-gateway "msg"="Starting Controller"
I1106 03:11:55.716491       1 controller.go:178] setup/controller/ravenl3-service "msg"="Starting EventSource"  "source"="kind source: *v1.Service"
I1106 03:11:55.716520       1 controller.go:178] setup/controller/ravenl3-service "msg"="Starting EventSource"  "source"="kind source: *v1alpha1.Gateway"
I1106 03:11:55.716540       1 controller.go:178] setup/controller/ravenl3-service "msg"="Starting EventSource"  "source"="kind source: *v1.Endpoints"
I1106 03:11:55.716557       1 controller.go:186] setup/controller/ravenl3-service "msg"="Starting Controller"
I1106 03:11:55.716807       1 controller.go:178] setup/controller/nodepool "msg"="Starting EventSource"  "source"="kind source: *v1beta1.NodePool"
I1106 03:11:55.716859       1 controller.go:178] setup/controller/nodepool "msg"="Starting EventSource"  "source"="kind source: *v1.Node"
I1106 03:11:55.716877       1 controller.go:186] setup/controller/nodepool "msg"="Starting Controller"
I1106 03:11:55.716997       1 controller.go:178] setup/controller/daemonpodupdater "msg"="Starting EventSource"  "source"="kind source: *v1.DaemonSet"
I1106 03:11:55.717141       1 controller.go:178] setup/controller/daemonpodupdater "msg"="Starting EventSource"  "source"="kind source: *v1.Pod"
I1106 03:11:55.717167       1 controller.go:186] setup/controller/daemonpodupdater "msg"="Starting Controller"
I1106 03:11:55.717314       1 controller.go:178] setup/controller/poolcoordinatorcert "msg"="Starting EventSource"  "source"="kind source: *v1.Service"
I1106 03:11:55.717335       1 controller.go:186] setup/controller/poolcoordinatorcert "msg"="Starting Controller"
I1106 03:11:55.719627       1 reflector.go:219] Starting reflector *v1.Pod (9h35m5.942017359s) from pkg/mod/k8s.io/client-go@v0.22.3/tools/cache/reflector.go:167
I1106 03:11:55.719655       1 reflector.go:255] Listing and watching *v1.Pod from pkg/mod/k8s.io/client-go@v0.22.3/tools/cache/reflector.go:167
I1106 03:11:55.720114       1 reflector.go:219] Starting reflector *v1beta1.NodePool (9h34m58.442318047s) from pkg/mod/k8s.io/client-go@v0.22.3/tools/cache/reflector.go:167
I1106 03:11:55.720148       1 reflector.go:255] Listing and watching *v1beta1.NodePool from pkg/mod/k8s.io/client-go@v0.22.3/tools/cache/reflector.go:167
I1106 03:11:55.720337       1 reflector.go:219] Starting reflector *v1.Endpoints (10h46m43.40638878s) from pkg/mod/k8s.io/client-go@v0.22.3/tools/cache/reflector.go:167
I1106 03:11:55.720352       1 reflector.go:255] Listing and watching *v1.Endpoints from pkg/mod/k8s.io/client-go@v0.22.3/tools/cache/reflector.go:167
I1106 03:11:55.720722       1 reflector.go:219] Starting reflector *v1.Service (9h15m13.772410123s) from pkg/mod/k8s.io/client-go@v0.22.3/tools/cache/reflector.go:167
I1106 03:11:55.720744       1 reflector.go:255] Listing and watching *v1.Service from pkg/mod/k8s.io/client-go@v0.22.3/tools/cache/reflector.go:167
I1106 03:11:55.720970       1 reflector.go:219] Starting reflector *v1alpha1.NodePool (10h26m0.678921328s) from pkg/mod/k8s.io/client-go@v0.22.3/tools/cache/reflector.go:167
I1106 03:11:55.720980       1 reflector.go:255] Listing and watching *v1alpha1.NodePool from pkg/mod/k8s.io/client-go@v0.22.3/tools/cache/reflector.go:167
I1106 03:11:55.720982       1 reflector.go:219] Starting reflector *v1alpha1.YurtStaticSet (10h4m3.951943722s) from pkg/mod/k8s.io/client-go@v0.22.3/tools/cache/reflector.go:167
I1106 03:11:55.720997       1 reflector.go:255] Listing and watching *v1alpha1.YurtStaticSet from pkg/mod/k8s.io/client-go@v0.22.3/tools/cache/reflector.go:167
I1106 03:11:55.721210       1 reflector.go:219] Starting reflector *v1alpha1.Gateway (9h43m56.076838563s) from pkg/mod/k8s.io/client-go@v0.22.3/tools/cache/reflector.go:167
I1106 03:11:55.721220       1 reflector.go:255] Listing and watching *v1alpha1.Gateway from pkg/mod/k8s.io/client-go@v0.22.3/tools/cache/reflector.go:167
I1106 03:11:55.721251       1 reflector.go:219] Starting reflector *v1.CertificateSigningRequest (10h47m2.810721562s) from pkg/mod/k8s.io/client-go@v0.22.3/tools/cache/reflector.go:167
I1106 03:11:55.721275       1 reflector.go:255] Listing and watching *v1.CertificateSigningRequest from pkg/mod/k8s.io/client-go@v0.22.3/tools/cache/reflector.go:167
I1106 03:11:55.720727       1 reflector.go:219] Starting reflector *v1.Deployment (9h21m31.478683572s) from pkg/mod/k8s.io/client-go@v0.22.3/tools/cache/reflector.go:167
I1106 03:11:55.721373       1 reflector.go:255] Listing and watching *v1.Deployment from pkg/mod/k8s.io/client-go@v0.22.3/tools/cache/reflector.go:167
I1106 03:11:55.721475       1 reflector.go:219] Starting reflector *v1.Lease (9h25m15.28893132s) from pkg/mod/k8s.io/client-go@v0.22.3/tools/cache/reflector.go:167
I1106 03:11:55.721483       1 reflector.go:255] Listing and watching *v1.Lease from pkg/mod/k8s.io/client-go@v0.22.3/tools/cache/reflector.go:167
I1106 03:11:55.724809       1 reflector.go:219] Starting reflector *v1.Node (9h10m56.268200005s) from pkg/mod/k8s.io/client-go@v0.22.3/tools/cache/reflector.go:167
I1106 03:11:55.724832       1 reflector.go:255] Listing and watching *v1.Node from pkg/mod/k8s.io/client-go@v0.22.3/tools/cache/reflector.go:167
I1106 03:11:55.725052       1 reflector.go:219] Starting reflector *v1alpha1.YurtAppSet (10h8m30.477940322s) from pkg/mod/k8s.io/client-go@v0.22.3/tools/cache/reflector.go:167
I1106 03:11:55.725060       1 reflector.go:255] Listing and watching *v1alpha1.YurtAppSet from pkg/mod/k8s.io/client-go@v0.22.3/tools/cache/reflector.go:167
I1106 03:11:55.725242       1 reflector.go:219] Starting reflector *v1.StatefulSet (10h41m22.264308797s) from pkg/mod/k8s.io/client-go@v0.22.3/tools/cache/reflector.go:167
I1106 03:11:55.725249       1 reflector.go:255] Listing and watching *v1.StatefulSet from pkg/mod/k8s.io/client-go@v0.22.3/tools/cache/reflector.go:167
I1106 03:11:55.725424       1 reflector.go:219] Starting reflector *v1.DaemonSet (10h51m37.284872099s) from pkg/mod/k8s.io/client-go@v0.22.3/tools/cache/reflector.go:167
I1106 03:11:55.725432       1 reflector.go:255] Listing and watching *v1.DaemonSet from pkg/mod/k8s.io/client-go@v0.22.3/tools/cache/reflector.go:167
I1106 03:11:55.728749       1 reflector.go:219] Starting reflector *v1alpha1.YurtAppDaemon (10h40m54.038595239s) from pkg/mod/k8s.io/client-go@v0.22.3/tools/cache/reflector.go:167
I1106 03:11:55.728768       1 reflector.go:255] Listing and watching *v1alpha1.YurtAppDaemon from pkg/mod/k8s.io/client-go@v0.22.3/tools/cache/reflector.go:167
I1106 03:11:55.769698       1 warning_handler.go:65] KubeAPIWarningLogger "msg"="apps.openyurt.io/v1alpha1 NodePool is deprecated in v1.0.0+; use apps.openyurt.io/v1beta1 NodePool"
I1106 03:11:55.806640       1 shared_informer.go:270] caches populated
I1106 03:11:55.813027       1 shared_informer.go:270] caches populated
I1106 03:11:55.813379       1 shared_informer.go:270] caches populated
I1106 03:11:55.814621       1 shared_informer.go:270] caches populated
I1106 03:11:55.814858       1 shared_informer.go:270] caches populated
I1106 03:11:55.815000       1 shared_informer.go:270] caches populated
I1106 03:11:55.815198       1 shared_informer.go:270] caches populated
I1106 03:11:55.816371       1 shared_informer.go:270] caches populated
I1106 03:11:55.816456       1 shared_informer.go:270] caches populated
I1106 03:11:55.816523       1 shared_informer.go:270] caches populated
I1106 03:11:55.816556       1 shared_informer.go:270] caches populated
I1106 03:11:55.816711       1 shared_informer.go:270] caches populated
I1106 03:11:55.816782       1 shared_informer.go:270] caches populated
I1106 03:11:55.816909       1 shared_informer.go:270] caches populated
I1106 03:11:55.816921       1 shared_informer.go:270] caches populated
I1106 03:11:55.816981       1 shared_informer.go:270] caches populated
I1106 03:11:55.816792       1 shared_informer.go:270] caches populated
I1106 03:11:55.817012       1 shared_informer.go:270] caches populated
I1106 03:11:55.817072       1 gateway_enqueue_handlers.go:42] ravenl3-gateway: node(beijing) does not belong to any gateway
I1106 03:11:55.817111       1 nodepool_enqueue_handlers.go:46] nodepool: node(beijing) does not belong to any nodepool
I1106 03:11:55.816798       1 shared_informer.go:270] caches populated
I1106 03:11:55.816806       1 shared_informer.go:270] caches populated
I1106 03:11:55.817162       1 controller.go:220] setup/controller/csrapprover "msg"="Starting workers"  "worker count"=3
I1106 03:11:55.817326       1 csrapprover_controller.go:190] csr(csr-h78zq) is approved
I1106 03:11:55.817366       1 shared_informer.go:270] caches populated
I1106 03:11:55.817432       1 shared_informer.go:270] caches populated
I1106 03:11:55.816811       1 shared_informer.go:270] caches populated
I1106 03:11:55.817526       1 controller.go:220] setup/controller/delegatelease "msg"="Starting workers"  "worker count"=5
I1106 03:11:55.817753       1 controller.go:220] setup/controller/podbinding "msg"="Starting workers"  "worker count"=5
I1106 03:11:55.817847       1 shared_informer.go:270] caches populated
I1106 03:11:55.818099       1 shared_informer.go:270] caches populated
I1106 03:11:55.818122       1 controller.go:220] setup/controller/poolcoordinatorcert "msg"="Starting workers"  "worker count"=1
I1106 03:11:55.820350       1 shared_informer.go:270] caches populated
I1106 03:11:55.820410       1 shared_informer.go:270] caches populated
I1106 03:11:55.820422       1 shared_informer.go:270] caches populated
I1106 03:11:55.820444       1 shared_informer.go:270] caches populated
I1106 03:11:55.820472       1 shared_informer.go:270] caches populated
I1106 03:11:55.820493       1 shared_informer.go:270] caches populated
I1106 03:11:55.820504       1 shared_informer.go:270] caches populated
I1106 03:11:55.820534       1 shared_informer.go:270] caches populated
I1106 03:11:55.820551       1 shared_informer.go:270] caches populated
I1106 03:11:55.820575       1 shared_informer.go:270] caches populated
I1106 03:11:55.820598       1 controller.go:220] setup/controller/servicetopology-endpoints "msg"="Starting workers"  "worker count"=3
I1106 03:11:55.820616       1 shared_informer.go:270] caches populated
I1106 03:11:55.820669       1 shared_informer.go:270] caches populated
I1106 03:11:55.820714       1 controller.go:220] setup/controller/ravenl3-gateway "msg"="Starting workers"  "worker count"=3
I1106 03:11:55.820726       1 shared_informer.go:270] caches populated
I1106 03:11:55.820747       1 shared_informer.go:270] caches populated
I1106 03:11:55.820771       1 controller.go:220] setup/controller/ravenl3-service "msg"="Starting workers"  "worker count"=3
I1106 03:11:55.820867       1 shared_informer.go:270] caches populated
I1106 03:11:55.820883       1 shared_informer.go:270] caches populated
I1106 03:11:55.820892       1 shared_informer.go:270] caches populated
I1106 03:11:55.820911       1 shared_informer.go:270] caches populated
I1106 03:11:55.820928       1 controller.go:220] setup/controller/servicetopology-endpointslice "msg"="Starting workers"  "worker count"=3
I1106 03:11:55.820949       1 shared_informer.go:270] caches populated
I1106 03:11:55.820977       1 shared_informer.go:270] caches populated
I1106 03:11:55.821002       1 controller.go:220] setup/controller/yurtappset "msg"="Starting workers"  "worker count"=3
I1106 03:11:55.821036       1 shared_informer.go:270] caches populated
I1106 03:11:55.821058       1 shared_informer.go:270] caches populated
I1106 03:11:55.821074       1 controller.go:220] setup/controller/daemonpodupdater "msg"="Starting workers"  "worker count"=3
I1106 03:11:55.823040       1 podbinding_controller.go:92] node request: beijing
I1106 03:11:55.825200       1 delegatelease_controller.go:160] detaint beijing: no key node.openyurt.io/unschedulable exists, nothing to do
I1106 03:11:55.826308       1 shared_informer.go:270] caches populated
I1106 03:11:55.826347       1 shared_informer.go:270] caches populated
I1106 03:11:55.826404       1 controller.go:220] setup/controller/nodepool "msg"="Starting workers"  "worker count"=3
I1106 03:11:55.829587       1 shared_informer.go:270] caches populated
I1106 03:11:55.829620       1 shared_informer.go:270] caches populated
I1106 03:11:55.829646       1 controller.go:220] setup/controller/yurtappdaemon "msg"="Starting workers"  "worker count"=3
I1106 03:11:55.906884       1 shared_informer.go:270] caches populated
I1106 03:11:55.907251       1 controller.go:220] setup/controller/yurtstaticset "msg"="Starting workers"  "worker count"=3
I1106 03:11:55.907534       1 yurtstaticset_controller.go:281] yurtstaticset: Reconcile YurtStaticSet kube-controller-manager
I1106 03:11:55.907579       1 yurtstaticset_controller.go:281] yurtstaticset: Reconcile YurtStaticSet etcd
E1106 03:11:55.907809       1 yurtstaticset_controller.go:286] Fail to get YurtStaticSet kube-system/etcd, YurtStaticSet.apps.openyurt.io "etcd" not found
I1106 03:11:55.907874       1 yurtstaticset_controller.go:281] yurtstaticset: Reconcile YurtStaticSet kube-apiserver
E1106 03:11:55.907891       1 yurtstaticset_controller.go:286] Fail to get YurtStaticSet kube-system/kube-apiserver, YurtStaticSet.apps.openyurt.io "kube-apiserver" not found
I1106 03:11:55.907596       1 yurtstaticset_controller.go:281] yurtstaticset: Reconcile YurtStaticSet kube-scheduler
E1106 03:11:55.907919       1 yurtstaticset_controller.go:286] Fail to get YurtStaticSet kube-system/kube-scheduler, YurtStaticSet.apps.openyurt.io "kube-scheduler" not found
E1106 03:11:55.908116       1 yurtstaticset_controller.go:286] Fail to get YurtStaticSet kube-system/kube-controller-manager, YurtStaticSet.apps.openyurt.io "kube-controller-manager" not found
W1106 03:12:40.091709       1 configuration.go:89] Ignore webhook for /validate-raven-openyurt-io-v1beta1-gateway in configuration
W1106 03:12:40.091738       1 configuration.go:89] Ignore webhook for /validate-core-openyurt-io-v1-node in configuration
W1106 03:12:40.091746       1 configuration.go:89] Ignore webhook for /validate-iot-openyurt-io-v1alpha2-platformadmin in configuration
W1106 03:12:40.091753       1 configuration.go:89] Ignore webhook for /validate-apps-openyurt-io-v1alpha1-yurtappoverrider in configuration
I1106 03:13:08.846539       1 deleg.go:130] controller-runtime/webhook "msg"="shutting down webhook server"
I1106 03:13:08.846668       1 webhook_controller.go:167] Shutting down webhook-controller
I1106 03:13:08.850286       1 reflector.go:225] Stopping reflector *v1.Secret (0s) from pkg/mod/k8s.io/client-go@v0.22.3/tools/cache/reflector.go:167
I1106 03:13:08.852967       1 reflector.go:225] Stopping reflector *v1.Endpoints (10h46m43.40638878s) from pkg/mod/k8s.io/client-go@v0.22.3/tools/cache/reflector.go:167
I1106 03:13:08.853261       1 reflector.go:225] Stopping reflector *v1.Pod (9h35m5.942017359s) from pkg/mod/k8s.io/client-go@v0.22.3/tools/cache/reflector.go:167
I1106 03:13:08.853644       1 reflector.go:225] Stopping reflector *v1.Deployment (9h21m31.478683572s) from pkg/mod/k8s.io/client-go@v0.22.3/tools/cache/reflector.go:167
I1106 03:13:08.853715       1 controller.go:240] setup/controller/yurtstaticset "msg"="Shutdown signal received, waiting for all workers to finish"
I1106 03:13:08.854316       1 controller.go:240] setup/controller/yurtappdaemon "msg"="Shutdown signal received, waiting for all workers to finish"
I1106 03:13:08.854352       1 controller.go:240] setup/controller/nodepool "msg"="Shutdown signal received, waiting for all workers to finish"
I1106 03:13:08.854394       1 controller.go:240] setup/controller/daemonpodupdater "msg"="Shutdown signal received, waiting for all workers to finish"
I1106 03:13:08.854411       1 controller.go:240] setup/controller/yurtappset "msg"="Shutdown signal received, waiting for all workers to finish"
I1106 03:13:08.854428       1 controller.go:240] setup/controller/servicetopology-endpointslice "msg"="Shutdown signal received, waiting for all workers to finish"
I1106 03:13:08.854444       1 controller.go:240] setup/controller/ravenl3-service "msg"="Shutdown signal received, waiting for all workers to finish"
I1106 03:13:08.854480       1 controller.go:240] setup/controller/ravenl3-gateway "msg"="Shutdown signal received, waiting for all workers to finish"
I1106 03:13:08.854498       1 controller.go:240] setup/controller/servicetopology-endpoints "msg"="Shutdown signal received, waiting for all workers to finish"
I1106 03:13:08.854515       1 controller.go:240] setup/controller/poolcoordinatorcert "msg"="Shutdown signal received, waiting for all workers to finish"
I1106 03:13:08.854551       1 controller.go:240] setup/controller/podbinding "msg"="Shutdown signal received, waiting for all workers to finish"
I1106 03:13:08.854572       1 controller.go:240] setup/controller/delegatelease "msg"="Shutdown signal received, waiting for all workers to finish"
I1106 03:13:08.854599       1 controller.go:240] setup/controller/csrapprover "msg"="Shutdown signal received, waiting for all workers to finish"
I1106 03:13:08.854868       1 reflector.go:225] Stopping reflector *v1alpha1.YurtAppSet (10h8m30.477940322s) from pkg/mod/k8s.io/client-go@v0.22.3/tools/cache/reflector.go:167
I1106 03:13:08.855203       1 reflector.go:225] Stopping reflector *v1.DaemonSet (10h51m37.284872099s) from pkg/mod/k8s.io/client-go@v0.22.3/tools/cache/reflector.go:167
I1106 03:13:08.855576       1 reflector.go:225] Stopping reflector *v1alpha1.Gateway (9h43m56.076838563s) from pkg/mod/k8s.io/client-go@v0.22.3/tools/cache/reflector.go:167
I1106 03:13:08.860159       1 reflector.go:225] Stopping reflector *v1alpha1.YurtStaticSet (10h4m3.951943722s) from pkg/mod/k8s.io/client-go@v0.22.3/tools/cache/reflector.go:167
I1106 03:13:08.861842       1 reflector.go:225] Stopping reflector *v1alpha1.YurtAppDaemon (10h40m54.038595239s) from pkg/mod/k8s.io/client-go@v0.22.3/tools/cache/reflector.go:167
I1106 03:13:08.862129       1 reflector.go:225] Stopping reflector *v1.StatefulSet (10h41m22.264308797s) from pkg/mod/k8s.io/client-go@v0.22.3/tools/cache/reflector.go:167
I1106 03:13:08.862913       1 controller.go:242] setup/controller/daemonpodupdater "msg"="All workers finished"
I1106 03:13:08.863042       1 reflector.go:225] Stopping reflector *v1.Node (9h10m56.268200005s) from pkg/mod/k8s.io/client-go@v0.22.3/tools/cache/reflector.go:167
I1106 03:13:08.863185       1 controller.go:242] setup/controller/podbinding "msg"="All workers finished"
I1106 03:13:08.863246       1 controller.go:242] setup/controller/delegatelease "msg"="All workers finished"
I1106 03:13:08.863272       1 controller.go:242] setup/controller/csrapprover "msg"="All workers finished"
I1106 03:13:08.863334       1 controller.go:242] setup/controller/yurtappdaemon "msg"="All workers finished"
I1106 03:13:08.863359       1 controller.go:242] setup/controller/poolcoordinatorcert "msg"="All workers finished"
I1106 03:13:08.863612       1 reflector.go:225] Stopping reflector *v1.CertificateSigningRequest (10h47m2.810721562s) from pkg/mod/k8s.io/client-go@v0.22.3/tools/cache/reflector.go:167
I1106 03:13:08.864615       1 reflector.go:225] Stopping reflector *v1.ValidatingWebhookConfiguration (0s) from pkg/mod/k8s.io/client-go@v0.22.3/tools/cache/reflector.go:167
I1106 03:13:08.865436       1 controller.go:242] setup/controller/nodepool "msg"="All workers finished"
I1106 03:13:08.865476       1 controller.go:242] setup/controller/yurtappset "msg"="All workers finished"
I1106 03:13:08.865499       1 controller.go:242] setup/controller/servicetopology-endpointslice "msg"="All workers finished"
I1106 03:13:08.865542       1 controller.go:242] setup/controller/ravenl3-service "msg"="All workers finished"
I1106 03:13:08.865562       1 controller.go:242] setup/controller/ravenl3-gateway "msg"="All workers finished"
I1106 03:13:08.865583       1 controller.go:242] setup/controller/servicetopology-endpoints "msg"="All workers finished"
I1106 03:13:08.865625       1 controller.go:242] setup/controller/yurtstaticset "msg"="All workers finished"

Name:         yurt-manager-f4f5c8d4c-k62fg
Namespace:    kube-system
Priority:     0
Node:         beijing/<IP_ADDRESS>
Start Time:   Mon, 06 Nov 2023 03:10:08 +0000
Labels:       app.kubernetes.io/instance=yurt-manager
              app.kubernetes.io/name=yurt-manager
              pod-template-hash=f4f5c8d4c
Annotations:  cni.projectcalico.org/containerID: 09f6b08e252fb0f44ac52e68a758ed4ad8d57789caae176c08b70bbb81e9ce01
              cni.projectcalico.org/podIP: <IP_ADDRESS>/32
              cni.projectcalico.org/podIPs: <IP_ADDRESS>/32,fd96:ee88:2:0:b32c:cb7c:f82a:344d/128
Status:       Running
IP:           <IP_ADDRESS>
IPs:
  IP:           <IP_ADDRESS>
  IP:           fd96:ee88:2:0:b32c:cb7c:f82a:344d
Controlled By:  ReplicaSet/yurt-manager-f4f5c8d4c
Containers:
  yurt-manager:
    Container ID:  docker://59faa2e8457bca5f0d0150aa8fe831ef3096121c520e07c631150fae2377bdd5
    Image:         openyurt/yurt-manager:v1.3.4
    Image ID:      docker-pullable://openyurt/yurt-manager@sha256:c22f50eac17197e105a6122872109b30a501fd92d95a49b688563d29243cb68d
    Ports:         10273/TCP, 10271/TCP, 10272/TCP
    Host Ports:    0/TCP, 0/TCP, 0/TCP
    Command:
      /usr/local/bin/yurt-manager
    Args:
      --metrics-addr=:10271
      --health-probe-addr=:10272
      --webhook-port=10273
      --logtostderr=true
      --v=4
      --working-namespace=kube-system
      --controllers=*
    State:          Running
      Started:      Mon, 06 Nov 2023 03:13:09 +0000
    Last State:     Terminated
      Reason:       Completed
      Exit Code:    0
      Started:      Mon, 06 Nov 2023 03:11:39 +0000
      Finished:     Mon, 06 Nov 2023 03:13:08 +0000
    Ready:          True
    Restart Count:  2
    Liveness:       http-get http://:10272/healthz delay=60s timeout=2s period=10s #success=1 #failure=3
    Readiness:      http-get http://:10272/readyz delay=60s timeout=2s period=10s #success=1 #failure=2
    Environment:    <none>
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-jmv42 (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             True
  ContainersReady   True
  PodScheduled      True
Volumes:
  kube-api-access-jmv42:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    DownwardAPI:             true
QoS Class:                   BestEffort
Node-Selectors:              <none>
Tolerations:                 node-role.kubernetes.io/control-plane:NoSchedule
                             node-role.kubernetes.io/master:NoSchedule
                             node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                             node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
  Type     Reason     Age                  From               Message
  ----     ------     ----                 ----               -------
  Normal   Scheduled  4m19s                default-scheduler  Successfully assigned kube-system/yurt-manager-f4f5c8d4c-k62fg to beijing
  Normal   Killing    79s (x2 over 2m49s)  kubelet            Container yurt-manager failed liveness probe, will be restarted
  Normal   Pulled     78s (x3 over 4m17s)  kubelet            Container image "openyurt/yurt-manager:v1.3.4" already present on machine
  Normal   Created    78s (x3 over 4m17s)  kubelet            Created container yurt-manager
  Normal   Started    78s (x3 over 4m17s)  kubelet            Started container yurt-manager
  Warning  Unhealthy  9s (x7 over 3m9s)    kubelet            Liveness probe failed: HTTP probe failed with statuscode: 404

Seems like a liveness probe error, so I checked the liveness probe:
curl http://<IP_ADDRESS>:10272/healthz
404 page not found

What you expected to happen:
The yurt-manager can be installed easyily and smoothly.
How to reproduce it (as minimally and precisely as possible):
Install openyurt as described in this document
Anything else we need to know?:
Environment:

OpenYurt version:
Kubernetes version (use kubectl version):
OS (e.g: cat /etc/os-release):
Kernel (e.g. uname -a):
Install tools:
Others:

others
/kind question

@bluven Thank you for raising issue. please use yurt-manage:latest image at present, and we will release v1.4.0 as soon as possible.  please stay tuned.

@bluven sorry to response late, OpenYurt v1.4.0 has been released, please enjoy the new version.


SCL compare function in XML

As a engineer
I would like to compare SCL file versions
So I can see the changes in files and trace bugs
Other use-case:
Make changes to an existing file to show others what as changed
Acceptance criteria:
Select 2 versions (atlassian confluence style)
SCL Compare in front-end: and display XML differences (github style)
Check if RiseClipse has already an compare function

RTE is working on a compare function using schematron (finished by november).

We can discuss the current functionality with OpenSCD: Why did they compare per section?

https://github.com/openscd/open-scd/blob/main/src/wizards.ts diff function can be used
also the same and as-equal.


Yes.
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
set GO111MODULE=on
set GOARCH=amd64
set GOBIN=
set GOCACHE=C:\Users\MNP1LHG\AppData\Local\go-build
set GOENV=C:\Users\MNP1LHG\AppData\Roaming\go\env
set GOEXE=.exe
set GOFLAGS=
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GONOPROXY=tfs.ups.com
set GONOSUMDB=tfs.ups.com
set GOOS=windows
set GOPATH=C:\Users\MNP1LHG\go
set GOPRIVATE=tfs.ups.com
set GOPROXY=nexusrmps.njrar.us.ups.com:8443/repository/goproxy-test/
set GOROOT=c:\go
set GOSUMDB=sum.golang.org
set GOTMPDIR=
set GOTOOLDIR=c:\go\pkg\tool\windows_amd64
set GCCGO=gccgo
set AR=ar
set CC=gcc
set CXX=g++
set CGO_ENABLED=1
set GOMOD=NUL
set CGO_CFLAGS=-g -O2
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-g -O2
set CGO_FFLAGS=-g -O2
set CGO_LDFLAGS=-g -O2
set PKG_CONFIG=pkg-config
set GOGCCFLAGS=-m64 -mthreads -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=C:\Users\MNP1LHG\AppData\Local\Temp\go-build106505266=/tmp/go-build -gno-record-gcc-switches

What did you do?
I tried to run a go get to retrive a local package hosted on an internal repo

go get -v tfs.ups.com/tfs/opt/P04A/_git/file-download
go get tfs.ups.com/tfs/opt/P04A/_git/file-download: disabled by GOPRIVATE/GONOPROXY

What did you expect to see?
I expected to see go get output display the no go-import meta tags error.
What did you see instead?
Instead, I received the error above disabled by GOPRIVATE/GONOPROXY
Additional Info
If I set GOPROXY='direct', it seems to throw the correct no go-import meta tags error.

This seems to be working correctly: GOPROXY is set to nexusrmps.njrar.us.ups.com:8443/repository/goproxy-test/, which instructs the go command to only download modules from that proxy. But GOPRIVATE (and GONOPROXY, which defaults to GOPRIVATE) is set to tfs.ups.com, which instructs the go command not to use a proxy for modules with the prefix tfs.ups.com. There's no place it's allowed to get those modules.
You may want to clear GOPRIVATE and set GONOSUMDB to tfs.ups.com. Or alternatively set GOPROXY to nexusrmps.njrar.us.ups.com:8443/repository/goproxy-test/,direct (adding direct to the end).
go help modules-private has more information on these settings.

Ah okay, thank you so much @jayconrod.

@jayconrod Here is the problem, I am noticing. If I add the direct, it allows go get to download packages from all sites, our use case is not to allow that. In theory, shouldn't the GONOPROXY set via the GOPRIVATE env allow for direct connections to that host only?

@lafrontz So if I understand correctly, you want to download modules starting with tfs.ups.com directly from version control, and all other modules from your proxy, not from version control?
If that's correct, use the settings below. The proxy should return 404 or 410 responses for modules that can be retrieved directly. It should return 200 for modules it can provide and other 4xx codes (for example 403) for modules that should not be retrieved directly. The go command will only fall back to later sources in the GOPROXY list after a 404 or 410 response. GONOPROXY will cause it to skip all proxies for matching modules.
GOPROXY=nexusrmps.njrar.us.ups.com:8443/repository/goproxy-test/,direct
GOPRIVATE=tfs.ups.com

Alternatively, the proxy can be responsible for serving all allowed modules, and the go command can be forbidden from connecting to other sources.
GOPROXY=nexusrmps.njrar.us.ups.com:8443/repository/goproxy-test/
GONOSUMDB=tfs.ups.com

@jayconrod Let me explain so more facts.
Our network does not allow direct access to the internet unless you are authenticated and connecting through an HTTP Proxy server.
The Go Proxy hosted at nexusrmps.njrar.us.ups.com:8443 can connect to the internet since the Nexus server has credentials to connect to the internet.
In theory, we are trying to set it up, a user can only download Go packages via the Proxy, and the internal VCS (tfs.ups.com)
From the test, I have been running, if I add directly to the end of the GOPROXY env go get attempts to connect to the remote server directly. When running go get -v github.com/grailbio/bigslice
This output is given:
go get -v github.com/grailbio/bigslice go: finding github.com/grailbio/bigslice latest go: downloading github.com/grailbio/bigslice v0.0.0-20191127055513-215d6078cbbc verifying<EMAIL_ADDRESS><EMAIL_ADDRESS>Get<EMAIL_ADDRESS>dial tcp <IP_ADDRESS>:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
The IP Address in the response does not match the sum.golang.org one, nor any other internal network IPs.

Sounds like it's hitting an error connecting to sum.golang.org, which is blocked on your network. You'll need to set GOSUMDB=off to disable it. (I'm not seeing the same IP address, but it is the same subnet).
Please look through go help module-private and module authentication failures for more info.

Two things.
First, sum.golang.org is not that IP address; this is confusing for me.

nslookup sum.golang.org <IP_ADDRESS>
Server:         <IP_ADDRESS>
Address:        <IP_ADDRESS>#53

Non-authoritative answer:
Name:   sum.golang.org
Address: <IP_ADDRESS>
Name:   sum.golang.org
Address: 2607:f8b0:4009:804::2011
Second, according to the documentation, setting the GOPRIVATE which intern sets the GONOPROXY should skip the GOPROXY settings for private packages.
The GOPRIVATE and GONOPROXY environment variables allow bypassing the proxy for selected modules. See 'go help module-private' for details. - Module downloading and verification
The GOPRIVATE environment variable controls which modules the go command considers to be private (not available publicly) and should therefore not use the proxy or checksum database.  Module configuration for non-public modules
The documentation goes on to say the following:

For example, if a company ran a module proxy serving private modules, users would configure go using:

GOPRIVATE=*.corp.example.com
GOPROXY=proxy.example.com
GONOPROXY=none

This would tell the go command and other tools that modules beginning with a corp.example.com > subdomain are private but that the company proxy should be used for downloading both public and private modules, because GONOPROXY has been set to a pattern that won't match any modules,  overriding GOPRIVATE.

Which from how I am reading this, is that my original set up should have skipped the GOPROXY settings for tfs.ups.com.

set GONOPROXY=tfs.ups.com
set GONOSUMDB=tfs.ups.com
set GOPRIVATE=tfs.ups.com
set GOPROXY=nexusrmps.njrar.us.ups.com:8443/repository/goproxy-test/
set GOSUMDB=sum.golang.org

If I am misunderstanding this all, please explain it to me, because it does not seem to be adding up correctly.

@lafronzt Did you find a solution for that problem?
I'm actually facing the same issue.

@lucas-dehandschutter I do not seem to be having this issue anymore; however, I have had to set GOSUMDB=off since it is unavailable behind the proxy.
What exactly is the issue you are getting right now?

@lafronzt
Hello, I have browsed the above records, the problems I encountered are the same as yours, and even our needs are the same. Excuse me, how did you solve it,
thank you

@hotshot-dot it was actually never fixed.
my pending question to @jayconrod has never been addressed, and I am still noticing discrepancies between what they mentioned and what is written in the documentation.

@lafronzt
My problem has been solved.
The strange thing is that I did n’t use GOPRIVATE. Now, I can freely introduce private projects on gitlab, not as complicated as the official documentation.


Not Recognizing the arabic numbers

Password feild error out with:
When choosing your password, please ensure it is a minimum of 10 characters in length and contains at least one number.
•Passwords must have at least one digit ('0'-'9').
•Passwords must have at least one lowercase ('a'-'z').
Even though the password was:
٤٥٧٨٨٩٤٥٧٨٨٩m
It either should accept these arabic/hindi numbers or clearly say that it accepts only latin/english digits.

I am working on this issue.

Can I be assigned to work on this issue, it would be really great!!

Issue 1345 has been addressed, please go through it and let me know.


reduce libjxl_dec binary size

The code for separable 5x5 and 7x7 convolutions as well as Gaussian blurring is not used anywhere in the decoder, only in the encoder. This PR adjusts the build scripts accordingly so the decoder-only library libjxl_dec doesn't include unnecessary code.
On my x64 linux build, after stripping debug symbols, this reduces libjxl_dec.so from 1456 KB to 1251 KB.

Let's just rename files. That will be less surprising for future developers... I'll prepare a PR


Images and diagrams are not displayed in the documentation

Description

Examples
https://docs.shopware.com/en/shopware-platform-dev-en/references-internals/core
https://github.com/shopware/platform/blob/2f0f1379273f6869d20e5e5032f720aae746d80c/src/Docs/Resources/current/60-references-internals/10-core/__categoryInfo.md
https://github.com/shopware/platform/blob/2f0f1379273f6869d20e5e5032f720aae746d80c/src/Docs/Resources/current/60-references-internals/10-core/__categoryInfo.md
Possible Solution

rebuild documentation?
The "dist" folder does not seem to be there.
Additional context

Hi @seriewe - thank you for noting the issue! The documentation is not maintained anymore. Please refer to developer.shopware.com or github.com/shopware/docs instead.


GEOMESA-2619 Fix sort by an attribute that is not returned

Signed-off-by: Emilio Lahr-Vivaz<EMAIL_ADDRESS>

stacks on top of #2282


proposal: Go 2: spec: expand reserved keywords list to include: true, false, nil

Should this be allowed? https://play.golang.org/p/_ige_iHPQEn
false := true
nil := false

fmt.Println(false, nil)

That would break current code so this should be a Go2 request.

@andizzle, true, false are predeclared constants, nil, iota are predeclared identifiers whose values can be created even by programmers so am not sure what the bar for reserving them would and perhaps that might also warrant reserving predeclared types? As @meirf notes this would break current code.
I'll loop in @griesemer for his wisdom

This is a dup of #18193; which includes explanation for this design decision.

If anything, we want to remove keywords if at all possible. Again, see #18193 for the details of the discussion.
If you want to write false := true, go right ahead. There's plenty of ways one can shoot oneself in the foot in any language, and that's also true for Go. The solution is simple: Don't do that!
I'm going to close this as there's zero chance of this getting adopted. It also doesn't solve any real problem.

@andizzle Thanks for the update. The question really is: Is it worthwhile to add more keywords, which then have to be mentioned in the respective expression grammar, and which have to be explained in the spec, simply to protect against people doing false := true? By making true, false, and nil predeclared constants (or value, for nil), no extra keywords need to be introduced, the expression grammar doesn't need special cases, and the usual scoping rules take care of the rest. It's simpler and gets the job done w/o exceptions.
Or looking from a different angle: If we were to disallow false := true (which could also be done with special handling of those predeclared identifiers, not just with keywords), should we also prevent zero := 1.0 ? And if not, why not? How is it different? (Surely, anyone seeing zero would assume it to be some sort of zero value!). Or what about disallowing the declaration of a local function panic that doesn't panic? Etc.
There's plenty of opportunity for mischief in Go (and any language for that matter) - and these examples are things people don't really do accidentally in the real world. They do these if they want to prove a point or, well, create trouble (for themselves or others). We can't prevent this and thus we don't even try in these cases.
Thanks.

PS: There's a different design argument that could be made if true, false, and nil were the only predeclared identifiers: Maybe then it would make sense to make them keywords, and then there wouldn't be any notion of predeclared identifiers. But Go has many predeclared identifiers, so adding these three fits right into the design w/o complicating it.

Agree. If people want to write false := true, let them. To me, this question raised because I naturally assumed this behaviour would be considered as abnormal, or somehow should be illegal because it "looks wrong". But I now see the reason behind this design decision.
This is unlike some cases in other languages where if you don't know about them, you can be tricked. If people deliberately write false := true, then they are looking for trouble.
Thanks again for clearify this.


Add type in url parameter for filter

Certainly! Below is an example of an issue description:

Issue Title: Add type in url parameter for filter
Description:
Currently, the API provides images for various categories without a clear distinction in the URL parameter. It would be beneficial to introduce a type parameter in the URL to filter images based on specific categories. This enhancement would enhance usability and make the API more versatile.
Example Usage:

Video Game Cover

URL: https://picsum.photos/image?type=game

Movie Poster Cover

URL: https://picsum.photos/image?type=movie

Album Cover

URL: https://picsum.photos/image?type=album

Book Cover

URL: https://picsum.photos/image?type=book

Face Image

URL: https://picsum.photos/image?type=face

Fashion Picture

URL: https://picsum.photos/image?type=fashion

AI Image

URL: https://picsum.photos/image?type=ai

Dashboard

URL: https://picsum.photos/image?type=dashboard

CRM

URL: https://picsum.photos/image?type=crm

Finance

URL: https://picsum.photos/image?type=finance

Calendar

URL: https://picsum.photos/image?type=calendar

Messenger Landscape

URL: https://picsum.photos/image?type=messenger

Messenger Landscape

URL: https://picsum.photos/image?type=landscape

Hi,
Thank you for opening an issue, we're not currently planning to add this functionality.
Duplicate of #81


Fixes #2319 Unexpected error dialog needs version number

Fixes #2319 Unexpected error dialog needs version number
Adds version number to details.
Moves strings to resource files so they will be localized.
Note that the details string is deliberately non-localized, since the intent is to send it back to the development team for review (and we all speak English right now).

👍  this should be very useful


No longer working as of today. Errors in log.

Hey all,
No longer working for me as of today. Sad, it had been so stable for so long. Wondering if anyone else is having issues. Log below:
2022-11-30 14:03:12.094 ERROR (MainThread) [homeassistant.components.sharkiq] Unexpected error updating SharkIQ
File "/usr/src/homeassistant/homeassistant/components/sharkiq/update_coordinator.py", line 63, in _async_update_data
File "/usr/local/lib/python3.10/site-packages/sharkiq/ayla_api.py", line 199, in async_list_devices
2022-11-30 14:03:12.097 ERROR (MainThread) [homeassistant.components.sharkiq] Error fetching sharkiq data: 0, message='Attempt to decode JSON with unexpected mimetype: text/html', url=URL('https://ads-field-39a9391a.aylanetworks.com/apiv1/devices.json')
2022-11-30 14:22:57.168 ERROR (MainThread) [homeassistant.components.sharkiq] Unexpected error updating SharkIQ
File "/usr/src/homeassistant/homeassistant/components/sharkiq/update_coordinator.py", line 72, in _async_update_data
File "/usr/src/homeassistant/homeassistant/components/sharkiq/update_coordinator.py", line 58, in _async_update_vacuum
await sharkiq.async_update()
File "/usr/local/lib/python3.10/site-packages/sharkiq/sharkiq.py", line 228, in async_update
2022-11-30 14:22:57.170 ERROR (MainThread) [homeassistant.components.sharkiq] Error fetching sharkiq data: 0, message='Attempt to decode JSON with unexpected mimetype: text/html', url=URL('https://ads-field-39a9391a.aylanetworks.com/apiv1/dsns/AC000W021484217/properties.json')
2022-11-30 15:18:46.092 ERROR (MainThread) [homeassistant.components.sharkiq] Unexpected error updating SharkIQ
File "/usr/src/homeassistant/homeassistant/components/sharkiq/update_coordinator.py", line 63, in _async_update_data
File "/usr/local/lib/python3.10/site-packages/sharkiq/ayla_api.py", line 199, in async_list_devices
2022-11-30 15:18:46.093 ERROR (MainThread) [homeassistant.components.sharkiq] Error fetching sharkiq data: 0, message='Attempt to decode JSON with unexpected mimetype: text/html', url=URL('https://ads-field-39a9391a.aylanetworks.com/apiv1/devices.json')
2022-11-30 15:20:49.572 ERROR (MainThread) [homeassistant.components.sharkiq] Unexpected error updating SharkIQ
File "/usr/src/homeassistant/homeassistant/components/sharkiq/update_coordinator.py", line 72, in _async_update_data
File "/usr/src/homeassistant/homeassistant/components/sharkiq/update_coordinator.py", line 58, in _async_update_vacuum
await sharkiq.async_update()
File "/usr/local/lib/python3.10/site-packages/sharkiq/sharkiq.py", line 228, in async_update
2022-11-30 15:20:49.573 ERROR (MainThread) [homeassistant.components.sharkiq] Error fetching sharkiq data: 0, message='Attempt to decode JSON with unexpected mimetype: text/html', url=URL('https://ads-field-39a9391a.aylanetworks.com/apiv1/dsns/AC000W021484217/properties.json')
2022-11-30 15:42:09.112 ERROR (MainThread) [homeassistant.components.sharkiq] Unexpected error updating SharkIQ
File "/usr/src/homeassistant/homeassistant/components/sharkiq/update_coordinator.py", line 63, in _async_update_data
File "/usr/local/lib/python3.10/site-packages/sharkiq/ayla_api.py", line 199, in async_list_devices
2022-11-30 15:42:09.113 ERROR (MainThread) [homeassistant.components.sharkiq] Error fetching sharkiq data: 0, message='Attempt to decode JSON with unexpected mimetype: text/html', url=URL('https://ads-field-39a9391a.aylanetworks.com/apiv1/devices.json')
2022-11-30 17:06:36.095 ERROR (MainThread) [homeassistant.components.sharkiq] Unexpected error updating SharkIQ
File "/usr/src/homeassistant/homeassistant/components/sharkiq/update_coordinator.py", line 63, in _async_update_data
File "/usr/local/lib/python3.10/site-packages/sharkiq/ayla_api.py", line 199, in async_list_devices
2022-11-30 17:06:36.096 ERROR (MainThread) [homeassistant.components.sharkiq] Error fetching sharkiq data: 0, message='Attempt to decode JSON with unexpected mimetype: text/html', url=URL('https://ads-field-39a9391a.aylanetworks.com/apiv1/devices.json')
2022-12-01 06:00:03.093 ERROR (MainThread) [homeassistant.components.sharkiq] Unexpected error updating SharkIQ
File "/usr/src/homeassistant/homeassistant/components/sharkiq/update_coordinator.py", line 63, in _async_update_data
File "/usr/local/lib/python3.10/site-packages/sharkiq/ayla_api.py", line 199, in async_list_devices
2022-12-01 06:00:03.094 ERROR (MainThread) [homeassistant.components.sharkiq] Error fetching sharkiq data: 0, message='Attempt to decode JSON with unexpected mimetype: text/html', url=URL('https://ads-field-39a9391a.aylanetworks.com/apiv1/devices.json')
2022-12-01 06:00:33.090 ERROR (MainThread) [homeassistant.components.sharkiq] Unexpected error updating SharkIQ
File "/usr/src/homeassistant/homeassistant/components/sharkiq/update_coordinator.py", line 63, in _async_update_data
File "/usr/local/lib/python3.10/site-packages/sharkiq/ayla_api.py", line 199, in async_list_devices
2022-12-01 06:01:03.105 ERROR (MainThread) [homeassistant.components.sharkiq] Unexpected error updating SharkIQ
File "/usr/src/homeassistant/homeassistant/components/sharkiq/update_coordinator.py", line 63, in _async_update_data
File "/usr/local/lib/python3.10/site-packages/sharkiq/ayla_api.py", line 199, in async_list_devices
2022-12-01 06:01:03.266 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry "REDACTED" for sharkiq
File "/usr/src/homeassistant/homeassistant/components/sharkiq/init.py", line 53, in async_setup_entry
File "/usr/src/homeassistant/homeassistant/components/sharkiq/init.py", line 33, in async_connect_or_timeout
File "/usr/local/lib/python3.10/site-packages/sharkiq/ayla_api.py", line 97, in async_sign_in

Well, even though the issue was still present after restarting Home Assistant, going to Devices and Services and manually reloading the integration actually fixed it. Weird. Closing this for now.

@proactivematter Did you happen to update Home Assistant to a new release around the same time this happened?
Sometimes the integration id will change when a new release comes out, and it will break any reload automations people have in place at the moment.  This will not be necessary soon, but this discussion may help if this was in fact your issue: https://github.com/JeffResc/sharkiq/issues/23#issuecomment-1190987431
Also for future issues when using this library with Home Assistant integration, please open them on the Home Assistant repository as opposed to this one.

Hey, sorry about the delayed reply. Glad to say things have been stable. I just checked and the reload automation has been running once a day most days, sometimes twice. I didn't update the ID it uses, so doesn't seem that it is related.
I also don't believe I had update homeassistant prior to it having stopped working. Still confused as to what happened originally since it seems logical that restarting homeassistant would include reloading the integration. But alas, that is what happened.
Very cool that we may not need the reload automation soon! Reliability improved dramatically since you guys rescued this integration - truly grateful!


KAFKA-3428 Remove metadata sync bottleneck from mirrormaker's producer

Repalce topics with a concurrent hashset so it would not require to be
modified inside a synchrnoized method.
Make cluster a volatile varialble so fetch which just returns the
pointer does not have to be synchrnized.
@ijuma @becketqin
the contribution is my original work and that i license the work to the project under the project's open source license.

@ijuma would you be interested in reviewing this pull request?

Thanks for the PR. I think we need to document in the code the reasoning for the proposed strategy where most fields are protected by synchronization but a couple are not.
It would also be interesting to know if the consumer also suffers from similar bottlenecks and, if so, whether these change fix that case too.
What are your thoughts @guozhangwang @ewencp? For reference, I quote from the JIRA the relevant figures:
"Due to sync on the single producer, MM in a setup with 32 consumer threads could not send more than
358k msg/sec hence not being able to saturate the NIC."
"After applying the patch, MM could copy the entire data (447k msg/sec) with no lagging. The bytes-in rate was 183m per sec. We have not tried it yet with an input rate large enough to saturate a 10G NIC and we might discover other bottlenecks when doing so."

Also, it would be good to verify that changing topics to a Concurrent implementation doesn't slow down the case where there are less threads.

fyi, with this change we got around 1M msg/s (varies on different setup), which is still not high enough to saturate the NIC but still a non-negligible improvement.
we could not identify an obvious bottleneck after this point. the time consuming operations seems to be synchronization on free and incomplete, as well as synchronization on partition dequeue.

I think its great to see performance optimizations like this, but agreed with @ijuma that this definitely needs documentation about the approach and reasoning (and probably a reference to the relevant JIRA). The synchronized approach is clearly simpler to reason about and without any notes in the code it'd be really easy to revert important changes here. (Ideally we'd also have tests that could detect performance regression here. We don't have real support for this in the system tests yet, but this is a pretty specific scenario we'd need to test -- very large # of threads utilizing a single producer.)

Sure. I am about to submit a new PR with documentation.
About concerns of ConcurrentHashMap's read performance, I did a quick test with a single consumer and both approaches gave about 194 Msg/s. Although the experiment was performed only once and number varied over time, it suggests that ConcurrentHashMap's read latency is negligible compared to the overall latency of invoking producer.send
Still if that is a concern we have the option of making topics volatile and replace the reference with a new updated HashMap but i don't see evidence that this would be necessary.

not sure why is Jenkins complaining about this test:

kafka.api.SaslPlaintextConsumerTest > testSimpleConsumption FAILED
java.lang.AssertionError: expected:<1> but was:<0>

I ran the test on my laptop and passed successfully!

@ijuma @ewencp are you guys comfortable with the latest patch?

@ijuma @ewencp a kindly reminder

Hi @maysamyabandeh ,
It seems like this PR stalled. I'll close it out for now, but if you or anyone else want to resume this work, please feel free to re-open it (or start a new one)!
Thanks,
John


Why isn't the Windows SysInternals OpenSource ?

Why isn't the Windows SysInternals - as complete or at least some files - OpenSource?
Or if it is not possible: Why don't existing a better license?
The Linux-SysInternals are OpenSource at
https://github.com/Sysinternals
And the Windows SysInternals have the following license:
https://github.com/MicrosoftDocs/sysinternals/blob/live/sysinternals/license-terms.md

Scope of License
[...] In doing so, you must comply with any technical limitations in the software that only allow you to use it in certain ways. You may not

work around any technical limitations in the software;
reverse engineer, decompile or disassemble the software, except and only to the extent that applicable law expressly permits, despite this limitation;
make more copies of the software than specified in this agreement or allowed by applicable law, despite this limitation;
publish the software for others to copy;
rent, lease or lend the software;
transfer the software or this agreement to any third party; or
use the software for commercial software hosting services.

Have you ever seen before a license like that for a "free" software? Most Shareware programs have a better license.

Because there isn't as big of a market for Linux software than there is for Windows software, Windows has the most market share. The license you're referencing is a pretty standard license; it's not intended to place restrictions on independent users. What it does intend to restrict however would be anything that would infringe upon the rights of the copyright holder. Such violations include redistributing intellectual property as part of commercial services and reverse-engineering it to assist in the creation of a new work -- both requiring explicit consent from the author. Authors are allowed to protect their work so people can't turn a profit at the author's expense.


UpdateException: Cause: Error updating 'CVE-2007-5199'

Error
Receiving the following error when executing a Dependency-Check scan, in a Jenkins job, using the Jenkins plugin.
[DependencyCheck] OWASP Dependency-Check Plugin v2.1.0
[DependencyCheck] Executing Dependency-Check with the following options:
[DependencyCheck]  -name = mobilecloud-owasp
[DependencyCheck]  -scanPath = /var/lib/jenkins/workspace/Mobile/Test-Jobs/mobilecloud-owasp
[DependencyCheck]  -outputDirectory = /var/lib/jenkins/workspace/Mobile/Test-Jobs/mobilecloud-owasp
[DependencyCheck]  -dataDirectory = /var/lib/jenkins/workspace/Mobile/Test-Jobs/mobilecloud-owasp/dependency-check-data
[DependencyCheck]  -dataMirroringType = none
[DependencyCheck]  -isQuickQueryTimestampEnabled = true
[DependencyCheck]  -jarAnalyzerEnabled = true
[DependencyCheck]  -nodeJsAnalyzerEnabled = false
[DependencyCheck]  -nspAnalyzerEnabled = true
[DependencyCheck]  -composerLockAnalyzerEnabled = false
[DependencyCheck]  -pythonDistributionAnalyzerEnabled = false
[DependencyCheck]  -pythonPackageAnalyzerEnabled = false
[DependencyCheck]  -rubyBundlerAuditAnalyzerEnabled = false
[DependencyCheck]  -rubyGemAnalyzerEnabled = false
[DependencyCheck]  -cocoaPodsAnalyzerEnabled = false
[DependencyCheck]  -swiftPackageManagerAnalyzerEnabled = false
[DependencyCheck]  -archiveAnalyzerEnabled = true
[DependencyCheck]  -assemblyAnalyzerEnabled = true
[DependencyCheck]  -centralAnalyzerEnabled = true
[DependencyCheck]  -nuspecAnalyzerEnabled = true
[DependencyCheck]  -nexusAnalyzerEnabled = false
[DependencyCheck]  -autoconfAnalyzerEnabled = false
[DependencyCheck]  -cmakeAnalyzerEnabled = false
[DependencyCheck]  -opensslAnalyzerEnabled = false
[DependencyCheck]  -showEvidence = true
[DependencyCheck]  -formats = XML HTML
[DependencyCheck]  -autoUpdate = true
[DependencyCheck]  -updateOnly = false
[DependencyCheck] Data directory created
[DependencyCheck] Scanning: /var/lib/jenkins/workspace/Mobile/Test-Jobs/mobilecloud-owasp
[DependencyCheck] Analyzing Dependencies
[DependencyCheck] One or more exceptions were thrown while executing Dependency-Check
[DependencyCheck] Exception Caught: org.owasp.dependencycheck.data.update.exception.UpdateException
[DependencyCheck] Cause: Error updating 'CVE-2007-5199'
[DependencyCheck] Message: org.xml.sax.SAXException: Error updating 'CVE-2007-5199'
[DependencyCheck] org.owasp.dependencycheck.data.nvdcve.DatabaseException: Error updating 'CVE-2007-5199'
[DependencyCheck] Exception Caught: org.owasp.dependencycheck.exception.InitializationException
[DependencyCheck] Cause: org.owasp.dependencycheck.data.cpe.IndexException: Error reading CPE data
[DependencyCheck] Message: An exception occurred accessing the database

It's 99% the same as #843.

Correct - I believe I understand what is happening in the Jenkins environment. It comes down to the fact that dependency-check is not yet thread-safe. This is something we are working on and hope to have a release in the near future that will resolve this issue.

@jeremylong , you guys are doing great things with this tool, thank you so much.
However, I was wondering if there is a work around in the mean time?

You could use a database server instead of the embedded H2. See
https://jeremylong.github.io/DependencyCheck/data/database.html
For Jenkins I'd recommend setting this up.
On Thu, Sep 21, 2017 at 4:56 PM, rpiskule<EMAIL_ADDRESS>wrote:

@jeremylong https://github.com/jeremylong , you guys are doing great
things with this tool, thank you so much.
However, I was wondering if there is a work around in the mean time?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jeremylong/DependencyCheck/issues/860#issuecomment-331279606,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA0qwv4Ex1k34C-2EMSxY79337VU2nJcks5sks2ZgaJpZM4PE2SY
.

@jeremylong any idea on when this release will be made? Thank you!

I'm hoping the release will be very soon - at the latest next weekend (10/15).

@jeremylong, can you confirm that the fix was released in the latest version 3.0.0?
Thanks!

We have forked a version containing this fix, but it looks like it does not fix the database issue...

The fix for this should be in 3.0.0 - which was released yesterday. I'm working on sending out the release notes via google groups shortly.
Are people still seeing this issue in 3.0.0? @robinvanpraet Any chance you could submit a PR or tell me how you fixed this in your fork?

@jeremylong we just forked to use the latest version before it was released. And we then used that version in our build. We still had issues with the database. No changes done to make it work...

@robinvanpraet was the database issue reported under another issue?

No, I mean exactly this issue. Workaround was to use an external db. We are going to try this now


1.1.4 issue

after updating to 1.1.4, getting crash:
dyld: Symbol not found: _$S11WhatsNewKit08KeyValueaB12VersionStoreCAA08ReadableabfG0AAWP
  Referenced from: /Users/me/Library/Developer/CoreSimulator/Devices/F61169B1-9C1F-4301-9DF6-BDB79FA902A0/data/Containers/Bundle/Application/D9BF5E1D-67E3-46EC-8D5C-F6E6573374DD/MyApp.app/MyApp
  Expected in: /Users/me/Library/Developer/CoreSimulator/Devices/F61169B1-9C1F-4301-9DF6-BDB79FA902A0/data/Containers/Bundle/Application/D9BF5E1D-67E3-46EC-8D5C-F6E6573374DD/MyApp.app/Frameworks/WhatsNewKit.framework/WhatsNewKit
 in /Users/me/Library/Developer/CoreSimulator/Devices/F61169B1-9C1F-4301-9DF6-BDB79FA902A0/data/Containers/Bundle/Application/D9BF5E1D-67E3-46EC-8D5C-F6E6573374DD/MyApp.app/MyApp
(lldb)

cleaned build folder and seems the error went away.


search_data() function does not recognize doi key

Attempting to use search_data() and a DOI string (here, using the function's own example of doi="10.5067/SLREF-CDRV2" returns an unknown key error. Any assistance here would be appreciated, thanks!
import earthaccess
auth = earthaccess.login()

some authentication lines hidden for privacy...
You're now authenticated with NASA Earthdata Login
Using token with expiration date: 06/17/2023
Using user provided credentials for EDL

datasets = earthaccess.search_data(
    doi="10.5067/SLREF-CDRV2",
    cloud_hosted=True,
    temporal=("2002-01-01", "2002-12-31")
)

ValueError                                Traceback (most recent call last)
Cell In[16], line 1
----> 1 datasets = earthaccess.search_data(
      2     doi="10.5067/SLREF-CDRV2",
      3     cloud_hosted=True,
      4     temporal=("2002-01-01", "2002-12-31")
      5 )

File ~\Anaconda3\envs\earthaccess\Lib\site-packages\earthaccess\api.py:103, in search_data(count, **kwargs)
     65 def search_data(
     66     count: int = -1, **kwargs: Any
     67 ) -> List[earthaccess.results.DataGranule]:
     68     """Search dataset granules using NASA's CMR.
     69
     70     [https://cmr.earthdata.nasa.gov/search/site/docs/search/api.html](https://cmr.earthdata.nasa.gov/search/site/docs/search/api.html)
   (...)
    101         ```
    102     """
--> 103     query = DataGranules().parameters(**kwargs)
    104     granules_found = query.hits()
    105     print(f"Granules found: {granules_found}")

File ~\Anaconda3\envs\earthaccess\Lib\site-packages\earthaccess\search.py:342, in DataGranules.parameters(self, **kwargs)
    339 for key, val in kwargs.items():
    340     # verify the key matches one of our methods
    341     if key not in methods:
--> 342         raise ValueError("Unknown key {}".format(key))
    344     # call the method
    345     if isinstance(val, tuple):

ValueError: Unknown key doi

Hi @Joshdpaul earthaccess supports 2 kind of queries, dataset queries (collections) and data queries (files), NASA CMR does not support DOI as parameters on file level queries. Perhaps what you were looking for is
datasets = earthaccess.search_datasets(
    doi="10.5067/SLREF-CDRV2",
    cloud_hosted=True
)

which returns 0 results, after looking at the dataset I noticed that it was just deprecated by PODAAC, the version 3 DOI is
datasets = earthaccess.search_datasets(
    doi="10.5067/SLREF-CDRV3",
    cloud_hosted=True
)

datasets will be a list of the datasets found, this one returns one. If you don't want to print all the metadata you can configure the fields too. After looking at the data you should find short_name, or concept_id which are the key parameters for NASA CMR to fund you the files from a particular dataset. The next step would be to use them like in your original query:
results = earthaccess.search_data(
    concept_id="C2270392799-POCLOUD",
    cloud_hosted=True,
    temporal=("2002-01-01", "2002-12-31")
)

that gives me 73 files that we can finally open or download, I'd recommend downloading them unless you are executing the code in AWS (us-west-2). Hopefully this answers your question.

Great, thank you for the clarification between the search_data() and search_datasets parameters.

closing this one as resolved!


SMTP settings via url

This PR allows the SMTP-settings to be configured via a url, e.g.
Mail.defaults do
  delivery_method :smtp, url<EMAIL_ADDRESS>end

The Travis-builds seemed to fail for reasons unrelated to the code. Fixing this failed so I setup separate builds reachable via the ✅ at https://gitlab.com/eval/mail/tree/smtp-url.
The included smtp-delivery examples for gmail and fastmail were successfully tested.

Draft-status removed - feedback welcome!

Nice @eval !  - Please rebase this onto latest master, include a changelog and I'll include it in 2.9

Hi @mikel, I updated the PR. I made the following changes:

url-attributes now take precedence, so it's similar to how one would configure the database in Rails.
I used different default-settings in case of smtp for localhost and non-localhost.
This to make targeting a test-setup (e.g. mailcatcher) convenient, but also to require starttls by default for non-localhosts.

I tested the setup using mailcatcher and fastmail.

Updated docs&code to bring in line with the new acceptable values for enable_starttls.


[Select][material-ui] Add root class to SelectClasses

closes: https://github.com/mui/material-ui/issues/38275
before: https://codesandbox.io/s/select-theme-bug-forked-vyvncq?file=/index.tsx
after: https://codesandbox.io/s/peaceful-phoebe-lxr5lr?file=/index.tsx

[x] I have followed (at least) the PR section of the contributing guide.

Not sure why argos test is failing, any help? @DiegoAndai

I left two comments about things we could remove. I think adding root to selectClasses is enough to solve the issue.

Ready from my side 😊

Great

@sai6855 should I merge? I forgot if you have merging permissions or not 😅

@sai6855 should I merge? I forgot if you have merging permissions or not 😅

Yeah you can merge. I don't have merge permission


C# Using Prompt Dialog.Choice ends up firing twice or auto selects first answer

Hi,
Am using the following code.
`public Task StartAsync(IDialogContext context)
{
string WelcomeMsg = "hi";
try
{
var PromptOptions = new string[] { "Yeah", "Nope" };
PromptDialog.Choice(
context,
WelcomePrompt,
PromptOptions,
WelcomeMsg, promptStyle: PromptStyle.Auto
);
}
catch (TooManyAttemptsException ex)
{
if (Controllers.DebugMode.Debug)
{
context.PostAsync("exception" + ex);
}
}
return Task.CompletedTask;
}
private async Task WelcomePrompt(IDialogContext context, IAwaitable result)
{
var Prompt = await result;
string PromptString = Prompt.ToString().ToLower().Trim();
if (PromptString.Length > 0)
{
            PromptString = PromptString.Trim();
            if (PromptString == "yeah")
            {
                NextFunction NF = new NextFunction();
                await NF .StartAsync(context);
            }
            {
                AnotherFunction AF = new AnotherFunction ();
                await AF.Give(context);
            }
        }
    }`

My problem is that the confirm box is shown twice or it will auto select a reply ( the first one) and go  to next function!
Is it a bug or coding problem?!

In your IDialog.StartAsync implementation, you may want to send some welcome message, then start the choice prompt.  Code that sends messages in the StartAsync is really meant for proactive bots (https://docs.botframework.com/en-us/technical-faq/#what-is-the-difference-between-proactive-and-reactive) - reactive bots will often just call "context.Wait(MessageReceived)" in their IDialog.StartAsync implementation.

@willportnoy  Thanks for the Help,
Mine is a proactive bot.
Hence how should i recode this structure to that?!

@willportnoy  This is my whole code.
Am new to c# hence is confused about this,
What modifications should I do? and is there any stack overflow page for posting this doubts?
`
[Serializable]
public class WelcomeDialogue : IDialog
{
public Task StartAsync(IDialogContext context)
{
string WelcomeMsg = "Hi";
try
{
var PromptOptions = new string[] { "Yay", "Nope" };
PromptDialog.Choice(
context,
WelcomePrompt,
PromptOptions,
WelcomeMsg, promptStyle: PromptStyle.Auto
);
}
catch (TooManyAttemptsException ex)
{
context.PostAsync("exception" + ex);
}
return Task.CompletedTask;
}
private async Task WelcomePrompt(IDialogContext context, IAwaitable<string> result)
{
    var Prompt = await result;
    string PromptString = Prompt.ToString().ToLower().Trim();
    if (PromptString.Length > 0)
    {

        PromptString = PromptString.Trim();
        if (PromptString == "yay")
        {
          NextTask NT = new NextTask();
            await NT.StartAsync(context);
        }
        else
        {
            AnotherTask AT = new AnotherTask();
            await AT.go(context);
        }
    }
}

`

I got the problem! skype had my conversation id which he kept. once an error occurs, he will not destroy it until yu clear the Bot memory.
activity.GetStateClient().BotState.DeleteStateForUser(activity.ChannelId, activity.From.Id);
Used this code to clear it

Good to hear - I'm going to close this issue for now, but feel free to open a new issue for further discussion.

on first attempt it self it's calling ChoiceReceivedAsync method as well.
public async Task StartAsync(IDialogContext context)
{
await context.PostAsync($"I can help you with it.");
PromptDialog.Choice(
context: context,
resume: ChoiceReceivedAsync,
options: (IEnumerable)Enum.GetValues(typeof(RequestChoice)),
prompt: "You want to create Request for Self or someone else :",
promptStyle: PromptStyle.Auto
);
}
    public virtual async Task ChoiceReceivedAsync(IDialogContext context, IAwaitable<RequestChoice> activity)
    {

}


Overwrites inventory

I have my EFF 20 pick that cost me $100 USD and I did /mcpainter imagemap link.png and it overwrote my pick and now it's gone. /mcpainter imagemap even works on blank inventory slots without a map allowing for eco exploits selling maps...
/mcpainter imagemap also overwrites my friends maps with my new images...

Regarding the first part: its by design.
Regarding the 2'nd part: you did not provide enough information. If you had a map in hand then its by design, if not this could mean you had run out of maps.


Problem with TOR

admin@RaspiBolt:~ $ sudo cat /var/lib/tor/hidden_service_electrs/hostname
cat: /var/lib/tor/hidden_service_electrs/hostname: No such file or directory

Hi, I got through everything fine until the Remote Access section under Electrum. I get the above error after restarting TOR.
If it matters on the following step...

Add the following three lines in the section for “location-hidden services” in the torrc file.

I found an empty file before adding those three lines.
Any guidance would be much appreciated!

The file /etc/tor/torrc to configure the hidden service must not be empty in the beginning. It is the same file where you configured the basic Tor config in the Privacy section.
If /etc/tor/torrc really is empty or has been deleted, try pasting the following:
ControlPort 9051
CookieAuthentication 1
CookieAuthFileGroupReadable 1

HiddenServiceDir /var/lib/tor/hidden_service_electrs/
HiddenServiceVersion 3
HiddenServicePort 50002 <IP_ADDRESS>:50002

After that, you should get the following output:
admin@raspibolt:~ $ tor --version
Tor version <IP_ADDRESS>.

admin@raspibolt:~ $ sudo ls -la /var/lib/tor/hidden_service_electrs
total 24
drwx--S--- 3 debian-tor debian-tor 4096 Feb  1 13:43 .
drwx--S--- 4 debian-tor debian-tor 4096 Feb  1 13:46 ..
drwx--S--- 2 debian-tor debian-tor 4096 Feb  1 13:43 authorized_clients
-rw------- 1 debian-tor debian-tor   63 Feb  1 13:43 hostname
-rw------- 1 debian-tor debian-tor   64 Feb  1 13:43 hs_ed25519_public_key
-rw------- 1 debian-tor debian-tor   96 Feb  1 13:43 hs_ed25519_secret_key

admin@raspibolt:~ $ sudo cat /var/lib/tor/hidden_service_electrs/hostname
3fpv2mfnb7bd4sqrcmwp4zwifq35dgtzxcf6x6jpvgx7g7qmts4x47ad.onion

Any progress solving your issue?

Closing this issue due to inactivity. Feel free to reopen it if further assistance is required.


Some buttons of a PS4 controller don't work on Linux

All buttons worked on browsers (on Linux). I guess this is a problem of GLFW...

The machine was DELL Inspiron 3162.

We would need to implement HID drivers. Duplicated with #2320