Issues with re-create

Hey -- I've been running into this issue whereby PowerDNS does not restart properly after initial config. I get the following error, fix has been to delete the mariadb and powerdns containers and let it re-instantiate
May 18 13:31:45 Guardian is launching an instance
May 18 13:31:45 Loading '/usr/lib/pdns/pdns/libgmysqlbackend.so'
May 18 13:31:45 This is a guarded instance of pdns
May 18 13:31:45 UDP server bound to <IP_ADDRESS>:53
May 18 13:31:45 UDPv6 server bound to [::]:53
May 18 13:31:45 TCP server bound to <IP_ADDRESS>:53
May 18 13:31:45 TCPv6 server bound to [::]:53
May 18 13:31:45 PowerDNS Authoritative Server 4.2.1 (C) 2001-2019 PowerDNS.COM BV
May 18 13:31:45 Using 64-bits mode. Built using gcc 9.2.0 on Dec  3 2019 17:17:37 by buildozer@build-3-11-x86_64.
May 18 13:31:45 PowerDNS comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it according to the terms of the GPL version 2.
May 18 13:31:45 [webserver] Listening for HTTP requests on <IP_ADDRESS>:8081
May 18 13:31:45 Polled security status of version 4.2.1 at startup, no known issues reported: OK
May 18 13:31:45 Master/slave communicator launching
May 18 13:31:45 Creating backend connection for TCP
May 18 13:31:45 About to create 3 backend threads for UDP
May 18 13:31:45 Exiting because communicator thread died with error: GSQLBackend unable to retrieve list of master domains: Could not prepare statement: select d.id, d.name, d.notified_serial, r.content from records r join domains d on r.name=d.name where r.type='SOA' and r.disabled=0 and d.type='MASTER': Table 'powerdns.records' doesn't exist
May 18 13:31:45 Done launching threads, ready to distribute questions
May 18 13:31:46 Guardian is killed, taking down children with us

Same here.
@carpenike Can you tell me how you deleted a single container out of the pod?

Same here.
@carpenike Can you tell me how to delete a single container out of the pod?  Thanks!

@ttinkr I haven’t done that before. In my case I deleted the entire pod.

What have been the steps you have taken?

Same here.
In my case after restarting pod when powerdns-powerdnsadmin starts it deletes tables in database.
...
===> DB management
---> Running DB Migration
 * Tip: There are .env files present. Do "pip install python-dotenv" to use them.
INFO  [alembic.runtime.migration] Context impl MySQLImpl.
INFO  [alembic.runtime.migration] Will assume non-transactional DDL.
INFO  [alembic.autogenerate.compare] Detected removed table 'supermasters'
INFO  [alembic.autogenerate.compare] Detected removed index 'name_index' on 'domains'
INFO  [alembic.autogenerate.compare] Detected removed table 'domains'
INFO  [alembic.autogenerate.compare] Detected removed index 'comments_name_type_idx' on 'comments'
INFO  [alembic.autogenerate.compare] Detected removed index 'comments_order_idx' on 'comments'
INFO  [alembic.autogenerate.compare] Detected removed table 'comments'
INFO  [alembic.autogenerate.compare] Detected removed index 'domainidindex' on 'cryptokeys'
INFO  [alembic.autogenerate.compare] Detected removed table 'cryptokeys'
INFO  [alembic.autogenerate.compare] Detected removed index 'nametype_index' on 'records'
INFO  [alembic.autogenerate.compare] Detected removed table 'records'
INFO  [alembic.autogenerate.compare] Detected removed index 'namealgoindex' on 'tsigkeys'
INFO  [alembic.autogenerate.compare] Detected removed table 'tsigkeys'
INFO  [alembic.autogenerate.compare] Detected removed index 'domainmetadata_idx' on 'domainmetadata'
INFO  [alembic.autogenerate.compare] Detected removed table 'domainmetadata'
...

Steps to reproduce:

Install helm chart
delete powerdns pod
get logs from powerdns-powerdnsadmin container

Testing:
$ helm repo add aecharts https://raw.githubusercontent.com/aescanero/helm-charts/master/
$ helm repo update
$ helm install powerdns-release --set domain=disasterproject.com aecharts/powerdns

$ kubectl -n external-dns get pv
pvc-55ad55ca-4d00-48f5-aa71-65a8abec49bd   1Gi        RWO            Delete           Bound    default/pvc-powerdns-release-mariadb   gp2                     3m48s

$ kubectl exec -it powerdns-release-56cbd58bbd-fct92 -c powerdns-powerdnsadmin -- kill 1

But you can't kill the container with this, you need to close all the gunicorns threads, now testing with "delete pod":
$ kubectl delete pod powerdns-release-56cbd58bbd-fct92
pod "powerdns-release-56cbd58bbd-fct92" deleted

$ kubectl logs powerdns-release-56cbd58bbd-9w7hb -c powerdns-powerdnsadmin
===> Waiting for <IP_ADDRESS> MySQL service
<IP_ADDRESS> (<IP_ADDRESS>:3306) open
INFO  [alembic.runtime.migration] Context impl MySQLImpl.
INFO  [alembic.runtime.migration] Will assume non-transactional DDL.
===> Update PDNS API connection info
Connection ok
Connection ok
[2020-07-26 18:56:09 +0000] [14] [INFO] Starting gunicorn 20.0.4
[2020-07-26 18:56:09 +0000] [14] [INFO] Listening at: http://<IP_ADDRESS>:9191 (14)
[2020-07-26 18:56:09 +0000] [14] [INFO] Using worker: sync
[2020-07-26 18:56:09 +0000] [16] [INFO] Booting worker with pid: 16
[2020-07-26 18:56:09 +0000] [17] [INFO] Booting worker with pid: 17
[2020-07-26 18:56:09 +0000] [18] [INFO] Booting worker with pid: 18
[2020-07-26 18:56:09 +0000] [19] [INFO] Booting worker with pid: 19

I can't reproduce it, but I'll check the entrypoint script.

Seems somehow may be related to k8s version or storage provider.
Got different results for two k8s instances:

k3s(v1.18.2+k3s1) with out-of-the-box storage
Do not survive pod deletion.
kubespray(release-2.13) - kubernetes v1.17.8 - with ceph pv
Works fine.

Yes, but how exactly storage affects booting up?


Added debug logging to ProviderSpi.cpp on writes.

1. Tell us something about your changes.
If you have more leds configured than the SPI buffer can support you now get this:
[HYPERIOND LedDevice]  ProviderSpi.cpp:92:writeBytes() SPI failed to write. errno: 90, Message too long
2. If this changes affect the .conf file. Please provide the changed section
nope
3. Reference an issue (optional)
Note: For further discussions use our forum: forum.hyperion-project.org

Don't merge this yet

I think this should actually result in a fatal error as it won't do anything without any apparent reason.

It's now error - it can't be fatal to the point of killing hyperiond - we need to be able to reconfigure things on the fly


Remove Unnecessary README Information

Two things were removed. First, there's no need to have an introduction to Julia in the README. Maybe it was useful before, but people installing Sundials.jl should know what Julia is by now.
Secondly, I removed the second on Sims.jl. This README is about using Sundials.jl, not Sims.jl.

Coverage remained the same at 11.056% when pulling b5b76d47721834f61173908b01ccbd204fde921b on ChrisRackauckas-patch-2 into 1ca207d233f37c685de28ded4fbb3f579d65b1fc on master.

I'll merge this in 7 days unless there's votes not to.


Should ActiveSupport::TimeWithZone cast to a date?

Presently it's casting to a time.
> future_date = 2.days.from_now
Sat, 09 Jan 2016 21:18:25 UTC +00:00
> graph << [:hello, RDF::Vocab::DC.created, future_date]
#<RDF::Graph:0x3ff65d0d9ccc(default)>
> graph.dump(:ttl)
"\n [ <http://purl.org/dc/terms/created> \"21:16:28Z\"^^<http://www.w3.org/2001/XMLSchema#time>] .\n"

Should we try #to_datetime?
> graph = RDF::Graph.new
#<RDF::Graph:0x3ff6593632a8(default)>
> graph << [:hello, RDF::Vocab::DC.created, 2.days.from_now.to_datetime]
#<RDF::Graph:0x3ff6593632a8(default)>
> graph.dump(:ttl)
"\n [ <http://purl.org/dc/terms/created> \"2016-01-09T21:22:15.244393+0000\"^^<http://www.w3.org/2001/XMLSchema#dateTime>] .\n"

RDF.rb uses Ruby Time as xsd:time. It's not an ideal fit, but it's the choice we made. Cast to DateTime to get the desired effect.
If you think this should be changed for 2.0, open an issue and we can discuss.


Secret Management for the spotify connect token

Is your feature already implemented in the latest master?
I don't think so, but please show me otherwise.
Is your feature request related to a problem? Please describe.
I'm using Spotify-player with home-manager for a declarative config. However, I don't want to leak my secrets in my config, because the get evaluated and put into the world-readable nix store.
Describe the solution you'd like
Add a 'token command' field like spotifyd's 'password_cmd' or neomutt's 'account_command' (https://neomutt.org/feature/account-cmd)
Describe alternatives you've considered
Not putting the key in the upstream repo.
Additional context
I'm using nixos + home-manager + sops-nix

For secret, do you mean client_id? Should be addressed by https://github.com/aome510/spotify-player/pull/548


backtrace command doesn't work anymore

cc @noahj
https://sunblazecollaborators.slack.com/archives/G8234P6RM/p1520219658000132
error[E0433]: failed to resolve. Could not find `backtrace` in `std`
   --> src/lib.rs:173:10
    |
173 |     std::backtrace::enable_backtrace("/contracts/evm/target/enclave/evm.signed.so", std::backtrace::PrintFormat::Short).expect("Failed to enable backtrace");
    |          ^^^^^^^^^ Could not find `backtrace` in `std`

find out how, update https://github.com/oasislabs/ekiden/blob/master/docs/enclave-backtrace.md

No longer relevant.


ceph-osd: set 'openstack_keys_tmp' only when 'openstack_config' is defined.

If 'openstack_config' is false this task shouldn't be executed.

jenkins test luminous-ansible2.4-centos7_cluster

@k0ste could you rebase your branch on master please?

@guits done.

Closes: https://bugzilla.redhat.com/show_bug.cgi?id=1589783

Closes: https://bugzilla.redhat.com/show_bug.cgi?id=1589792


Unify url prefixing of HttpServices of any kind

Currently there's a few ways to URL prefix various services.

mountService, Router, and URITranslation (which should really be UriTranslation) are all means to relocate a service underneath another.  Multiple mountService calls is natural in servlet containers, but Blaze assembles them into one service.

I'd favor some kind of middleware, with possibly a prefix method attached to HttpService.

URITranslation is already that middleware, isn't it?
prefix syntax for a Service[Request, ?] would be plausible.  Although really it's just andThen:
service andThen URITranslation("/foo") andThen CORS andThen ...

withHttpApp has been introduced as the common way for Blaze and Ember.  It doesn't make sense on the servlet containers (or at least fights with servlet mappings), so those are different.
I think we're consistent, but since this is confusing to people, leaving open to make sure it's better documented.


Feature : Command for reading option from tsconfig.json

can you guys add command for extracting option from tsconfig.json, like tsc -p tsconfig-spec.json, especially for dist and source directory, etc

I could look into this. This library is however more of a 'hack' than a proper solution so far.
So I mostly just hope that this functionality gets added to TypeScript itself at some point, making this library obsolete.


Display point value above/below each point

Hi dude! I found your chart lib awesome with many configuration possibilities but I was wondering if is possible to display the point value above/below each point.
Can I do it? how?
Thanks a lot!

Hi, thanks for your feedback. At the moment this is not possible. Shouldn't be hard to add that feature however, just a few lines of code..
Which charts in particular are you talking about (lines, splines, area, etc?) I'm quite busy at the moment, but if  have some spare time next week I'll add that feature.
If you want to have a go yourself and submit a PR, you probably just need to add a a  in the function _makeMarker in arty-charty/animated-circles-marker.js.

Hi! thanks for the quick answer!
I was talking about line charts. I will try to do it by myself but is the first time that I do this kind of things, anyway, I will do my best ^^'
Thanks a lot!


Syntax definition missing end-of-line non-terminal

IFB textitem ;;
;; ::= (;[\x00-\xFF^\x10]*)?\x10

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

ID: 8c02eb01-083d-3fc8-6c69-72aeafc0a2cf
Version Independent ID: 1622c277-0a85-816f-8ed9-3604b335c5c6
Content: IFB
Content Source: docs/assembler/masm/ifb.md
Product: visual-cpp
Technology: cpp-masm
GitHub Login: @corob-msft
Microsoft Alias: corob

Incorporated into Incomplete Syntax definition issue.


caffe2 spec/SRPM

Hello,
I've created caffe2 RPM file compatible with RHEL7.  Please let me know if you are interested in spec/SRPM files.
Thank you.

@advorkin, Did you distribute RPM version of Caffe2 for Linux distro such as RHEL7/CentOS7?


it doesn't worked

it don't work

yes it did.

I forgor

Ok thank you

hello this is a very important thred.
please do not use it to make fun and have laugh ok.


Update key stores to be compatible with Java 11

Changes done in the PR

Create the key stores with Mac algorithm HmacPBESHA1 to be compatible with Java 11.0.11 or earlier versions.
https://github.com/wso2/product-is/pull/21173

Fixes the issue https://github.com/wso2/product-is/issues/21193

Ran the integration tests locally

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/11102793398

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/11102793398
Status: failure


Feature/kgfu02/create side navigation component

Administrative Info
[GitHub Issue #]
Make sure your branch name conforms to: <feature/staging/hotfix/...>/[username]/[3-4 word description separated by dashes]. Otherwise, please rename your branch and create a new PR.
Changes
What changes did you make?

added a side navigation component that has positionally styled buttons to be used for navigation
added css styling to App.css
import side navigation to App.js

Testing
How did you confirm your changes worked?

checked npm start

Confirmation of Change
Upload a screenshot, if possible. Otherwise, please provide instructions on how to see the change.

Side navigation bar

Not too sure where we'll be placing our page components since I noticed you put yours in a components folder but it looks great overall!🤘🏼

I'll be adding a pages folder and refactoring some stuff once the current PRs are approved.


vim freezes if suspended with Ctrl-Z while running system command

Steps to reproduce

Start Vim in a Unix terminal using vim --clean -i NONE -c "call system('sleep 10')"
Press Ctrl-Z

The SIGTSTP signal is received by the sleep process, but not by Vim.  Vim waits for the suspended sleep command to complete and is thus blocked.  Typed keys appear on the screen, but don't do anything, pressing Ctrl-C or Ctrl-Z has no effect.
The only way of exiting that state is to open a new terminal and run pkill -CONT sleep, which will resume the sleep process and unblock Vim.
Bisection shows this behavior was introduced in v8.2.3941.
Expected behaviour
Vim is suspended together with the system command that was executing.  The user is back at interactive terminal.
Version of Vim
8.2.4897
Environment
Debian GNU/Linux, xterm, zsh, but these should not matter.
The behavior appears at v8.2.3941.
cc: @dbivolaru
Logs and stack traces
No response

Based on what I see on my box, this starts both a shell and the sleep command itself. The CTRL-Z suspends both the bash and the sleep instance but not vim.
$ ps aux | grep sleep
1234 vim --clean -i NONE -c call system('sleep 10')
1235 /bin/bash -c (sleep 10)>/tmp/vcHzT0f/0 2>&1
1236 sleep 10

The SIGCONT using the command you mentioned, only affects the child sleep process and the bash invocation stays suspended. The sleep process becomes defunct after the 10 seconds are gone.
To replicate fg/bg behavior, you need to send the SIGCONT to the process group, ie kill -CONT -1234 instead of kill -CONT -1236. Please take note of the minus sign in front of the PID.
To me it seems it works like intended. If you're in vim, CTRL-Z is taking out vim. If vim is executing an external command, CTLR-Z takes out the child processes started by vim only.

Well, having to "kill -9" processes to get back to Vim does not look like intended behavior.
I think we can use the old behavior, before patch 8.2.3941, when inside system().

@brammool In his example kill -9 also doesn't work because sleep is finished already (defunct) but bash stays suspended so process cleanup does not happen. As bash is run in non-interactive mode, the child is in the same process group. This does not happen with bash -i -c (sleep 10) where the CTRL+Z only stops the child process.

@brammool In his example kill -9 also doesn't work because sleep is
finished already (defunct) but bash stays suspended so process cleanup
does not happen. As bash is run in non-interactive mode, the child is
in the same process group. This does not happen with bash -i -c (sleep 10) where the CTRL+Z only stops the child process.

Killing the shell works.  It looks like Vim is getting the key (or the
signal) and the shell doesn't.
When Vim is waiting for a system() command to finish, having CTRL-Z only
make that command pause makes no sense, since nothing can be done.  The
only sensible thing to do is also make Vim sleep. Then when bringing it
to the foreground the system command continues until it's done.
I hope it can be made to work this way.  I thought it worked before the
change, and the bisection confirms that.
--
hundred-and-one symptoms of being an internet addict:
130.
/// Bram Moolenaar -- @.*** -- http://www.Moolenaar.net   \
///                                                                      \
\\        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

For some context, the blocked state occurs when some autocommand executes system call and user happens to press CTRL-Z at that moment.  From users POV Vim does not suspend, is unresponsive, and there is no easy way of getting out of that state.

The SIGCONT using the command you mentioned, only affects the child sleep process and the bash invocation stays suspended. The sleep process becomes defunct after the 10 seconds are gone.

I see.  I am using zsh which seems to do exec (process substitution) to run the sleep command.  For bash the shell stays around so it needs to be signaled to continue as well.

duplicate of #6565?

Patch v8.2.3941 is also causing nested vim to hang when ctrl-Z is pressed.  As in,
vim foo # to enter a vim session
:!vim bar # to enter a nested vim session
ctrl-Z # stops the second vim, but the first vim does not also stop
Subsequent ctrl-Z and ctrl-C are ignored until 'kill -STOP $PID1' is done.
I reverted patch v8.2.3941 in master, and I no longer see this problem.

I am still able to reproduce this problem on v8.2.4532 and v9.1.16, using :call system('sleep 10') followed by ctrl-z.
Neovim has solved this problem by waiting until the subprocess finishes before finally handling the ctrl-z. If after ctrl-z the user hits ctrl-c, the process is terminated immediately, and handling the ctrl-z is canceled.

Can this be fixed somehow? This is not just a sleep 10 problem it's only a reproducer. Real example, I run tig blame to view git blame blame on the current file and habitually press ^Z after this point terminal is unrecoverable hanged unless subprocess or vim itself is killed from in another screen.
Expected behavior is, when I suspend with ^Z inside of subcommand, vim should be suspended too (and I get into shell). Perhaps SIGSTOP should not be cached and left SIG_DFL? So when user press ^Z whole process group is suspended and not just subprocess (with a nested command) and vim remain up not knowing and not being able to do anything. Or at least make this behavior configurable?


Spike in postgres connections when routes are added or updated

We are observing a spike in database connections whenever we add a route to a service or update an existing route. We are running kong version 0.14.0 on 8 (4 core ec2) machines with default configuration.
On regular periods, the number of connections to database is 4 per node and we see 32 connections to the db overall. But during this issue, the connection goes beyond 2000 in the db. It lasts for less than a minute. During this period, the "active connections" spikes in kong and we see slowness in the calling systems. Below is our configuration, I have attached the kong connection metrics and rds connection metrics as well

{"plugins":{"enabled_in_cluster":["prometheus","request-size-limiting","syslog"],"available_on_server":{"response-transformer":true,"oauth2":true,"acl":true,"correlation-id":true,"pre-function":true,"jwt":true,"cors":true,"ip-restriction":true,"basic-auth":true,"key-auth":true,"rate-limiting":true,"request-transformer":true,"http-log":true,"file-log":true,"hmac-auth":true,"ldap-auth":true,"datadog":true,"tcp-log":true,"zipkin":true,"post-function":true,"request-size-limiting":true,"bot-detection":true,"syslog":true,"loggly":true,"azure-functions":true,"udp-log":true,"response-ratelimiting":true,"aws-lambda":true,"statsd":true,"prometheus":true,"request-termination":true}},"tagline":"Welcome to kong","configuration":{"plugins":["bundled"],"admin_ssl_enabled":false,"lua_ssl_verify_depth":1,"trusted_ips":["<IP_ADDRESS>\/0"],"prefix":"\/usr\/local\/kong","loaded_plugins":{"response-transformer":true,"request-termination":true,"prometheus":true,"ip-restriction":true,"pre-function":true,"jwt":true,"cors":true,"statsd":true,"basic-auth":true,"key-auth":true,"ldap-auth":true,"aws-lambda":true,"http-log":true,"response-ratelimiting":true,"hmac-auth":true,"request-size-limiting":true,"datadog":true,"tcp-log":true,"zipkin":true,"post-function":true,"bot-detection":true,"acl":true,"loggly":true,"syslog":true,"azure-functions":true,"udp-log":true,"file-log":true,"request-transformer":true,"correlation-id":true,"rate-limiting":true,"oauth2":true},"cassandra_username":"kong","admin_ssl_cert_csr_default":"\/usr\/local\/kong\/ssl\/admin-kong-default.csr","dns_resolver":{},"pg_user":"kong","pg_password":"******","cassandra_data_centers":["dc1:2","dc2:3"],"nginx_admin_directives":{},"custom_plugins":["prometheus"],"pg_host":"kong-db.swiggy.prod","nginx_acc_logs":"\/usr\/local\/kong\/logs\/access.log","proxy_listen":["<IP_ADDRESS>:80"],"client_ssl_cert_default":"\/usr\/local\/kong\/ssl\/kong-default.crt","ssl_cert_csr_default":"\/usr\/local\/kong\/ssl\/kong-default.csr","dns_no_sync":false,"db_update_propagation":0,"nginx_err_logs":"\/usr\/local\/kong\/logs\/error.log","cassandra_port":9042,"dns_order":["A","CNAME","LAST","SRV"],"dns_error_ttl":1,"headers":["server_tokens","latency_tokens"],"dns_stale_ttl":30,"nginx_optimizations":true,"database":"postgres","pg_database":"db_kong","nginx_worker_processes":"auto","lua_package_cpath":"","admin_acc_logs":"\/usr\/local\/kong\/logs\/admin_access.log","lua_package_path":".\/?.lua;.\/?\/init.lua;","nginx_pid":"\/usr\/local\/kong\/pids\/nginx.pid","upstream_keepalive":60,"admin_access_log":"logs\/admin_access.log","client_ssl_cert_csr_default":"\/usr\/local\/kong\/ssl\/kong-default.csr","proxy_listeners":[{"ssl":false,"ip":"<IP_ADDRESS>","proxy_protocol":false,"port":80,"http2":false,"listener":"<IP_ADDRESS>:80"}],"proxy_ssl_enabled":false,"cassandra_contact_points":["<IP_ADDRESS>"],"enabled_headers":{"latency_tokens":true,"X-Kong-Proxy-Latency":true,"Via":true,"server_tokens":true,"Server":true,"X-Kong-Upstream-Latency":true,"X-Kong-Upstream-Status":false},"ssl_ciphers":"XXXXXXX","cassandra_ssl":false,"db_resurrect_ttl":30,"ssl_cert_key_default":"\/usr\/local\/kong\/ssl\/kong-default.key","cassandra_consistency":"ONE","db_cache_ttl":0,"admin_error_log":"logs\/error.log","pg_ssl_verify":false,"dns_not_found_ttl":30,"pg_ssl":false,"client_max_body_size":"0","client_ssl":false,"cassandra_repl_strategy":"SimpleStrategy","ssl_cipher_suite":"modern","lua_socket_pool_size":30,"db_update_frequency":5,"nginx_http_directives":[{"value":"prometheus_metrics 5m","name":"lua_shared_dict"}],"kong_env":"\/usr\/local\/kong\/.kong_env","cassandra_schema_consensus_timeout":10000,"dns_hostsfile":"\/etc\/hosts","admin_listeners":[{"ssl":false,"ip":"<IP_ADDRESS>","proxy_protocol":false,"port":8001,"http2":false,"listener":"<IP_ADDRESS>:8001"}],"cassandra_lb_policy":"RoundRobin","error_default_type":"text\/plain","real_ip_header":"X-Real-IP","admin_ssl_cert_key_default":"\/usr\/local\/kong\/ssl\/admin-kong-default.key","cassandra_ssl_verify":false,"proxy_error_log":"logs\/error.log","nginx_proxy_directives":{},"real_ip_recursive":"off","cassandra_repl_factor":1,"client_ssl_cert_key_default":"\/usr\/local\/kong\/ssl\/kong-default.key","nginx_daemon":"on","anonymous_reports":true,"cassandra_timeout":5000,"proxy_access_log":"logs\/access.log","pg_port":5432,"nginx_kong_conf":"\/usr\/local\/kong\/nginx-kong.conf","client_body_buffer_size":"400k","mem_cache_size":"128m","admin_ssl_cert_default":"\/usr\/local\/kong\/ssl\/admin-kong-default.crt","log_level":"notice","cassandra_keyspace":"kong","ssl_cert_default":"\/usr\/local\/kong\/ssl\/kong-default.crt","nginx_conf":"\/usr\/local\/kong\/nginx.conf","admin_listen":["<IP_ADDRESS>:8001"]},"version":"0.14.0","node_id":"f54f803b-6ebd-4bcf-aa9e-68f2157acb9d","lua_version":"LuaJIT 2.1.0-beta3","timers":{"pending":58,"running":1},"hostname":"kong-p-node-1"}

On a multi-node setting like yours, when there is a change in one of the "core" entities (such as Services or Routes) it needs to be replicated to other nodes, and this is done via database queries. All nodes query the database periodically looking for changes.
One of the things that these event trigger is the re-creation of the routers. Routers are matching engines composed of all the routes in the database, and are cached per-worker. If you happen to have a lot of routes and/or services, this could be the cause of your spikes, since they all are reloaded from the database every time a new one is added, on every worker. Does this sound correct?

@kikito So, is it proportional to the number of concurrent calls being handled by nginx? Increasing our db connection limit for a not-so-frequent case of adding/updating routes seems overkill. Can the connection/cache be reused in this case via a background daemon?

This has come up in the forum too: https://discuss.konghq.com/t/route-caching-and-latency/840/4 , would be neat to solve as there is a bit of a risk if your running Kong really hot say 4000-5000 TPS and you add a route/service better hope your DB is ready for the heat 😆 . The idea of two cache primary and secondary (backup) and a switch on workers that uses the backup while while the new is being built out. Granted wait and run deployments at night all at once or some time outside critical hours and this can be avoided when your down to like 500-1000 TPS. Kong 15 improvement eh :P .

Uh. We will go with increasing the connections for time being. Hoping we will have a fix by 15. Thanks

@kikito @thibaultcha I have made a fix to not rebuild the router during the access phase. The approach I have tried is to trigger a worker_events.post to rebuild on all workers in the local node when there's a change in route. And also subscribe to cluster_events invalidations on 'router:version' to rebuild the router
https://github.com/Kong/kong/compare/master...ganeshs:master
Initial testing does seem to work. Would like to get an initial feedback on the approach before I build a full fledged fix. Thanks

Fixed in #3782 thanks to @p0pr0ck5! This will be included in the next release candidate for 1.0, in the next couple of weeks. Thanks for the report!


RandomThings Spectre Tree

Drops Ectoplasm as its fruit

Thanks for your help!
Please create a single pull request per mod integration, not per file.

oops, sorry about that! It's my first time

No worries!
Programming and development just requires a -for outside people- ridiculous level of cleanliness and absurd amount of rules to follow. Those are there for a reason though - we aren't just being mean ;)


[BUG] - Ledger corruption of testnet blockchain after retiring and re-registering pool

External
Other
Summary
Since I retired and re-registered a pool on testnet, unexplainable bug occured on ledger which leads to absolutely broken calculation of pledge wallet balance in ledger dump as well as all tools that work with it (pooltool.io, cncli etc.)
It's described in details here: https://github.com/AndrewWestberg/cncli/issues/47
Basically what happened - after retiring a pool, I re-registered it (I could see 500 balance in rewards in Daedalus, the returned deposit), but ever since I re-registered the pool, the calculated active pledge from ledger is showing absolutely wrong numbers that make no sense (not only they are different from the actual balance, they are different from any balance ever on that wallet).
Right now, the wallet has about 2M ADA, but according to ledger there is 22.1k balance (I don't even think there ever was that amount of ADA) - there was 10M since 17. 3. (I sent 8M away right after that), so that's like 4 epochs already, yet ledger is showing balance about 22.1k (where is that number even coming from)? These numbers just don't make any sense.
The pool is otherwise normally operating and producing blocks (but probably no rewards, since registering it again, I raised the pledge to 2M (there was > 2M balance in pool wallet even before re-registering the pool), but it was instantly marked as not-adhering to pledge everywhere as ledger is showing balance only 22.1k, so probably no rewards will be created in upcoming epochs. Currently it's impossible to increase the pledge on that pool, any amount of ADA I send to that pool wallet, even after waiting 2 epochs doesn't get reflected by ledger and has no effect on active pledge (raising it when re-registering pool just invalidates any rewards as pledge is not "adhered to")
Pool ID is b264b05a99fdebb8c15c9a5eac3646f808c0cb57c0b9751566594089
Steps to reproduce
I don't know how to reproduce it, this is what I did:
Steps to reproduce the behavior:

Create a wallet with balance X (using mnemonic method in my case)
Register staking address for that wallet
Register a new pool using that wallet with pledge < X
Operate it for an epoch or two
Retire it
Register it again
Now increase balance X
Wait few epochs - ledger will show nonsense

Expected behavior
I would expect ledger to show numbers that correspond to reality - eg. when your pool wallet has balance over 2M for more than 4 epochs, ledger should not be showing some random number (22.1k) as active balance of that same wallet
System info (please complete the following information):

OS: debian
Version 10
Node version 1.25.1

Additional context
See this thread https://github.com/AndrewWestberg/cncli/issues/47

Also - another part of this bug - there are 2 wallets registered in this pool (for over 4 epochs), total balance of both of them is > 10M, but active stake for this pool is calculated as ~8M

interesting update, despite the ledger is showing stake of 8M and pledge (that was set to 2M) as NOT MET, I received rewards for that epoch where pledge wasn't met. So it really looks like perhaps the data in blockchain are correct, but nonsense data are generated in ledger dump?
note there are 2 wallets delegated, pool wallet with 2M and other wallet with 8M, the pledge was set to 2M, but according to everything it was not met (even daedalus was showing the pool red with star, until I decreased pledge to 20k) but rewards for that epoch were paid anyway

Closing this. If this is still relevant please reopen.


Continued from other location - tablet issue

https://www.amazon.com/gp/product/B08GHHT32V/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&th=1
I was asked which tablet I'm using that won't allow screen rotation, and is incredibly glitchy / laggy -- this is the one that won't work, and I'm not quite sure why.
Mine is a Samsung Galaxy A7 10.5 inch

as said in the other issue, it seems an issue in your device
maybe you have rotation locked
or the browser you are using is not handling the site correctly

I think it could be device, I did check the rotation lock, works on everything cept your site, your site is also the only one i've found which gives me issues like this, sadly because it is nice to use my tablet by my computer - I tried 3 browsers on my tablet, all seem to lag, and the app is the one that doesn't rotate properly it's stuck in portrait mode (not the Desktop Site) But both desktop site, and the app lag super bad on my device.  So yeah I'm not sure. I tried it on my chromebook which is 10 years old and it works just fine and my tablet is only 4 years old, so I'm really not sure why it's happening but I do wish I could fix it.


增加signUrl 限制访问IP的能力

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


Bidi Bug(Material components): Angular material components use wrong css rules for bidi

Description
Some angular material components do not work as expected in complex bidi situations where we have an RTL application with some LTR pages.
suppose you have a simple HTML as follows:

                 // some angular material components here (e.g. mat-form-field with outline appearance)

The outcome would be a mess like this:

The problem comes from some CSS rules like this one:
[dir=rtl] .mat-form-field {
    text-align: right;
}

It is obvious that this rule applies to all components with an RTL ancestor!! even if the actual effective dir is LTR like the example above.
One solution here could be using a directive like this one:
export class BidiClassDirective
{

    constructor(readonly dir: Directionality)
    {
    }

    @HostBinding("class.ltr")
    get isLtr(): boolean
    {
        return this.dir.value === 'ltr';
    }

    @HostBinding("class.rtl")
    get isRtl(): boolean
    {
        return this.dir.value === 'rtl';
    }
}

In any component that has some direction-sensitive CSS, you have to use this directive to get the actual direction value.
For example inside the mat-form-field component:

               //..................

The CSS would be something like:
mat-form-field-wrapper.rtl >  .mat-form-field {
    text-align: right;
}

The proposed approach makes it a bit harder to implement the mat components but the result would be solid in any bidi situation.
Reproduction
Steps to reproduce:
suppose you have a simple HTML as follows:

                 // some angular material components here (e.g. mat-form-field with outline appearance)

Expected Behavior
The components should appear properly with respect to the actual effective dir! Like this:

Actual Behavior
But they currently appear like this:

Environment

Angular:  12.2.7
CDK/Material: 12.2.7
Browser(s): Chrome
Operating System (e.g. Windows, macOS, Ubuntu): Windows

Until now i have seen this issue in the form field and the paginator

We talked through this in our team meeting and decided not to support it for now, because it'll require refactors in most of our components in order to handle something that's somewhat of an edge case. Furthermore, even if we did refactor all our CSS, this will break again when we switch to the MDC component CSS in the near future.


with npm start does not report compile error

When using browserify-directory with npm start does not report compile errors, rather silently fails.
Such as, in package.json:
"scripts": {
    "start": "browserify-directory lib/js/ public/js/ & bin/cmd.js"
}

Thanks! A bit busy with work right now, but will try to push a fix sometime this weekend.


fix(package.json): trigger semantic release + update package.json

use (fix) in the commit message to trigger a semantic release
update package.json based on https://semantic-release.gitbook.io/semantic-release/support/faq

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


GPU support

I think in theory it should be possible to communicate data directly from GPU memory. mpi4py seems to support it, and we should be able to get a handle to device memory from JAX, e.g. via its DLPack support.

Yes, I had investigated this a bit and I'm sure it's possible to support it.
it's on my todo list, but now I don't have access to a GPU.
I'll work on this in October when I pick up a new position and I should have access to a gpu.

Sure. If you're eager to start before that, you could also do your testing on Google Colab.
I'd probably give this a stab at some point, but I doubt it will be before next year.

This should take 3 main ingredients:

Different low-level implementations (Cython or C++) for GPU primitives, because they have a different signature:
https://github.com/google/jax/blob/b040df20cb3005ec1af472028a3e5dd1b22b17f2/jaxlib/cuda_prng_kernels.cu.cc#L109-L110

Different implementation rules to account for layout and workspace:
https://github.com/google/jax/blob/b040df20cb3005ec1af472028a3e5dd1b22b17f2/jaxlib/cuda_prng.py#L38-L59
(it might be possible to use the same translation rule for CPU and GPU, I haven't figure that out yet)

Ensuring that mpi4py is built with CUDA support so it can actually read from device memory.

I think it could be valuable to have a workaround right now that does a copy to the host before performing the communication, but I haven't figured out how to do that yet (and have it callable from jitted GPU kernels).

I'm not sure I understand point 1 and 2...
I had given a look at this in the past, and from what I had understood:

How the XLA rule should be implemented for GPUs is detailed here, and it should simply involve defining a new operation in Cython and registering it for the right XLA backend. We probably have to use the custom-tuple machinery to pass CPU-side parameters (comm, op, stuff like this).

Note that we don't really need to write the GPU kernel itself, because we won't have one.

The function call itself should still be an MPI.Allreduce/Send/Whatever with the same signature. However, as you correctly noted, the MPI library to which mpi4py is linked to should be built with MPI support...

Cython, I'd say.
We just need to also link to CUDA somehow and find it's headers in order to get the cudaStream_t type. I guess a look at cupy internals might help.

I think we would ideally not be using the stream at all, right? In that case we could leave that as void*.
The GPU Cython wrappers will probably look very similar to the CPU ones, so it's too bad we can't re-use the same functions. Maybe with a thin wrapper that just parses the arguments and calls the CPU implementation.

I think we would ideally not be using the stream at all, right? In that case we could leave that as void*

Possibly true.

The GPU Cython wrappers will probably look very similar to the CPU ones, so it's too bad we can't re-use the same functions. Maybe with a thin wrapper that just parses the arguments and calls the CPU implementation.

we can start by writing new kernels and then see if we can merge them.
As both are CPU-functions that mostly do the same thing, I'd say that you are right: they will mostly be identical


Found device on tuya-cli list-app but homebridge failed to discover 3 gangs switch

As the title said, I had used tuya-cli to get the id and key of my devices then add the config.
My previous tuya smart breaker work well without any problem and it's still working now.
I've just bought a 3 gangs wall switch form Aliexpress and do the samething but homebridge can not discover it. I've tried SimpleLight, MultiOutlet or CustomMultiOutlet and neither of them work.
Link to device: https://aliexpress.com/item/Tuya-Smart-home-WiFi-Touch-Schalter-Drahtlose-Wand-Touch-Telefon-APP-control-UNS-typ-1-2/32980592592.html

Can you please define it as a SimpleLight and post some logs?

Yeah I've updated to rc and it's working now. Thank you very much!

That is great news. Best of luck.


refactor of AMDRequireItemDependency to es6

What kind of change does this PR introduce?
refactor
Did you add tests for your changes?
current tests should pass
If relevant, link to documentation update:
N/A
Summary
upgrade AMDRequireItemDependency to es6
Does this PR introduce a breaking change?
No

trigger rebuild for appveyor

Thanks for resetting again. We had a bit of build snafu in master and Travis is sooo slow right now.

all good :D


Fixed code typos in readme

Small typos in the code examples of the readme.
A Draggable instance was created but swappable.on was being called.

Thanks for the contribution


T5740 TransferHeader Excessive locktable

Hello,
in OnValidate trigger on fields
Transfer-from Code
Transfer-to Code
after succesful confirmation handling there are these two lines
TransLine.LockTable();
TransLine.SetRange("Document No.", "No.");

nothing happens after above filtering with these records, moreover function executed after this code
UpdateTransLines(Rec, FieldNo("Transfer-from Code"));
UpdateTransLines(Rec, FieldNo("Transfer-to Code"));

operates on its own local Transfer Line record variable.
Looks like a bug or is there a purpose behind it which I can't spot?
Thanks,
Bartek

Thank you for reaching out. Your request could be reporting a product bug not related to the AL extensibility.
Please reach out to the relevant support channels as specified in Product Support
On premises - https://support.microsoft.com/en-us/supportforbusiness/productselection?sapId=93d37907-ad94-d591-22e9-593cfa09dd3f
On line – read more here https://docs.microsoft.com/en-ca/dynamics365/business-central/dev-itpro/administration/manage-technical-support or contact your partner
If you are a partner open a support incident through Partner Center - https://partner.microsoft.com/en-us/pcv/dashboard/overview


DAWN 379 - Restore block_tests

Restore block_tests from 2.x and merge it (tests/tests/block_tests) with tests/chain_tests/block_tests

#1639 removes tests/tests/block_tests.cpp, so one of these will have a merge conflict. probably want to merge this one first.


ERROR in Error: ScrollDispatchModule is not an NgModule on material beta.10

I have this issue after update angular material beta.10... this is my package
"dependencies": {     "@angular/animations": "4.4.0-RC.0",     "@angular/cdk": "2.0.0-beta.10",     "@angular/common": "4.4.0-RC.0",     "@angular/compiler": "4.4.0-RC.0",     "@angular/compiler-cli": "4.4.0-RC.0",     "@angular/core": "4.4.0-RC.0",     "@angular/flex-layout": "2.0.0-beta.8",     "@angular/forms": "4.4.0-RC.0",     "@angular/http": "4.4.0-RC.0",     "@angular/material": "2.0.0-beta.10",     "@angular/platform-browser": "4.4.0-RC.0",     "@angular/platform-browser-dynamic": "4.4.0-RC.0",     "@angular/platform-server": "4.4.0-RC.0",     "@angular/router": "4.4.0-RC.0",     "@covalent/core": "1.0.0-beta.6",     "@covalent/dynamic-forms": "1.0.0-beta.6",     "@types/core-js": "0.9.43",     "@types/hammerjs": "2.0.34",     "@types/lodash": "4.14.74",     "angular2-markdown": "1.6.0",     "blob-polyfill": "1.0.20150320",     "classlist-polyfill": "1.2.0",     "classlist.js": "1.1.20150312",     "core-js": "2.4.1",     "formdata-polyfill": "2.0.2",     "hammerjs": "2.0.8",     "intl": "1.2.5",     "moment": "2.18.1",     "rxjs": "5.0.1",     "typedarray": "0.0.6",     "web-animations-js": "2.3.1",     "zone.js": "0.8.14"   }
and my app.module I try to import ScrollDispatchModule like this:
import { ScrollDispatchModule } from '@angular/cdk/scrolling';
but I have the same error. Can Someone help me please?
Thank youu

resolved updating covalent with 1.0.0-beta.7


how to use getLifecycle().addObserver(youTubePlayerView) in adapter for RecyclerView

This might be a stupid question but I can't find a way to use getLifecycle().addObserver(youTubePlayerView) in adapter for RecyclerView.

RecyclerView doesn't have a lifecycle. You need to get the lifecycle from your Activity/Fragment.

can you tell me how to get lifecycle form activity or fragment inside recyclerView Adapter.?

actully what i wanna do is video should not play automatically i added autoplay="false" in XML but it's not work in the adapter yes it's work in activity. Please tell me the solution if you. i m new in android

play

https://github.com/PierfrancescoSoffritti/android-youtube-player/blob/master/core-sample-app/src/main/java/com/pierfrancescosoffritti/androidyoutubeplayer/core/sampleapp/examples/recyclerViewExample/RecyclerViewAdapter.java


Possibly too easy to get rate limited by OpenSea on a specific device with slightly heavier usage?

Not sure if its related to this issue, in console appears error [OpenSea] API error: invalidApiKey from: performRequestWithRetry(chainId:url:maximumRetryCount:delayMultiplayer:retryDelay:queue:) with invalidApiKey

Strange, I don't see the invalidApiKey error for both mainnet and testnet

@oa-s is this with the keys committed into the repo? Mainnet or testnet?

Ah, I do hit .invalidApiKey (i.e. 401) from time to time. Will continue to look at it. This is with the repo's key:
2022-06-07 12:58:06.604272+0800 0x29d8c2   Default     0x0                  1399   0    AlphaWallet: (libswiftFoundation.dylib) xxx this is error: invalidApiKey on chainId: 1
2022-06-07 12:58:07.221078+0800 0x29d8c2   Default     0x0                  1399   0    AlphaWallet: (libswiftFoundation.dylib) xxx this is error: invalidApiKey on chainId: 1
2022-06-07 12:58:07.982072+0800 0x29d8c2   Default     0x0                  1399   0    AlphaWallet: (libswiftFoundation.dylib) xxx this is error: invalidApiKey on chainId: 1
2022-06-07 12:58:08.615892+0800 0x29d8c2   Default     0x0                  1399   0    AlphaWallet: (libswiftFoundation.dylib) xxx this is error: invalidApiKey on chainId: 1
2022-06-07 12:58:09.003575+0800 0x29d8c2   Default     0x0                  1399   0    AlphaWallet: (libswiftFoundation.dylib) xxx this is error: invalidApiKey on chainId: 1
2022-06-07 12:58:09.183035+0800 0x29d8c2   Default     0x0                  1399   0    AlphaWallet: (libswiftFoundation.dylib) xxx this is error: invalidApiKey on chainId: 1
2022-06-07 12:58:09.183623+0800 0x29d8c2   Default     0x0                  1399   0    AlphaWallet: (libswiftFoundation.dylib) xxx this is error: invalidApiKey on chainId: 1
2022-06-07 12:58:09.524658+0800 0x29d8c2   Default     0x0                  1399   0    AlphaWallet: (libswiftFoundation.dylib) xxx this is error: invalidApiKey on chainId: 1
2022-06-07 12:58:09.705019+0800 0x29d8c2   Default     0x0                  1399   0    AlphaWallet: (libswiftFoundation.dylib) xxx this is error: invalidApiKey on chainId: 1
2022-06-07 12:58:10.340289+0800 0x29d8c2   Default     0x0                  1399   0    AlphaWallet: (libswiftFoundation.dylib) xxx this is error: rateLimited on chainId: 1
2022-06-07 12:58:10.340641+0800 0x29d8c2   Default     0x0                  1399   0    AlphaWallet: (libswiftFoundation.dylib) xxx this is error: rateLimited on chainId: 1
2022-06-07 12:58:10.896656+0800 0x29d8c2   Default     0x0                  1399   0    AlphaWallet: (libswiftFoundation.dylib) xxx this is error: rateLimited on chainId: 1

this should be fixed with latest OpenSea class updates


MSID: 100652 Version: 1 DOI: 10.1101/2<IP_ADDRESS>2373

MSID: 100652
Version: 1
Preprint DOI: https://doi.org/10.1101/2<IP_ADDRESS>2373
Step 1. Awaiting reviews
Editorial to post reviews via hypothesis
Useful links:

DocMap: https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v2/by-publisher/elife/get-by-manuscript-id?manuscript_id=100652
New model tracking: https://docs.google.com/spreadsheets/d/1_fHaoOy7hjyocptKtVJRijeNpUY4hBS7Ck_aVmx6ZJk/
Reviews on sciety: https://sciety.org/articles/activity/10.1101/2<IP_ADDRESS>2373

For trouble shooting (e.g. no Docmaps available):

DocMap issue addressing: https://miro.com/app/board/uXjVNCwK6EI=/
Explore DataHub DocMaps API: https://lookerstudio.google.com/reporting/4c2f0368-babb-4beb-b5b3-497e7e7b0f08/page/ejphD
Unmatched submissions and preprints: https://lookerstudio.google.com/u/0/reporting/9f86204f-3bf7-477c-9b18-5c5ef141bf69/page/p_gxi57ha93c
Unmatched manuscripts spreadsheet: https://docs.google.com/spreadsheets/d/15QcK8w-ssB7109RQEDtFpJPZ0J5HTGxoHa_2TtpMBbg/edit#gid=1336081641

Step 2. Preview reviewed preprint
Production QC content ahead of publication
Instructions:

QC preview: https://prod--epp.elifesciences.org/previews/100652v1
Update ticket with any problems (add blocked label)
When QC OK, add QC OK label to ticket and add publication date and time to https://docs.google.com/spreadsheets/d/1amAlKvdLcaDp5W8Z8g77NmkwbMF5n_u89ArSqPMO8jg
Move card to next column
(At end of the day post link in #enhanced-preprint and ask for PDF to be generated)

Useful links:

Preprint DOI :  https://doi.org/10.1101/2<IP_ADDRESS>2373
Confirm reviews returned by EPP: https://prod--epp.elifesciences.org/api/reviewed-preprints/100652/v1/reviews
To update the MECA path in the docmap: https://docs.google.com/spreadsheets/d/1mctCQuNFBjSn97Lihy7_vBO6z7-N-oqyLv4clyi6zHg

Step 3: Awaiting search reindex
This step adds the reviewed preprint to the homepage: https://elifesciences.org
The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.
Useful links:

Jenkins pipeline to reindex search can be triggered sooner or monitored here: https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 4: Published! PDF requested
Waiting for PDF to be generated
Useful links:

PDF tracking: https://docs.google.com/spreadsheets/d/106_XeDjmuBae7gexOTNzg60lapeqjl2aRn9DzupGyS8/

Step 5: Introduce PDF to data folder and git repo
Upload PDF to relevent folder in git repo https://github.com/elifesciences/enhanced-preprints-data/
Step 6: Done!

[ ] Kettle is on!

Hi @acollings, should the term 'useful' be adjusted here?

https://sciety.org/evaluations/hypothesis:VUnwoHDrEe-tW0Mlce7s6A/content


500 status code on update share

Describe the bug
In ocis, when a user tries to update the last created share using the int value of the share_id, the status code is 500 when ocs_api_version 2 is used.
Steps to reproduce
Steps to reproduce the behavior:

Create users Alice, Brian and Carol
As user Alice, create a folder /TMP and share the folder with user Brian
As user Brian, get all the shares and accept the share /TMP as:

curl -k -X GET https://localhost:9200/ocs/v2.php/apps/files_sharing/api/v1/shares\?shared_with_me\=true\&state\=all -u Brian:1234 | xmllint --format -

<ocs>
  <meta>
    <status>ok</status>
    <statuscode>200</statuscode>
    <message>OK</message>
  </meta>
  <data>
    <element>
      <id>6c1276d3-a4d7-4690-8737-93ee9fa355db</id>
       .
       .
    </element>
  </data>
</ocs>

curl -k -X POST https://localhost:9200/ocs/v2.php/apps/files_sharing/api/v1/shares/pending/6c1276d3-a4d7-4690-8737-93ee9fa355db -u Brian:1234

As user Brian, share folder Shares/TMP with user Carol
As user Carol, get all the shares and accept the share Shares/TMP as

curl -k -X GET https://localhost:9200/ocs/v2.php/apps/files_sharing/api/v1/shares\?shared_with_me\=true\&state\=all -u Carol:1234 | xmllint --format -

<ocs>
  <meta>
    <status>ok</status>
    <statuscode>200</statuscode>
    <message>OK</message>
  </meta>
  <data>
    <element>
      <id>27238dc5-b2c2-4c6f-8ce8-e64c0d742770</id>
       .
       .
    </element>
  </data>
</ocs>

curl -k -X POST https://localhost:9200/ocs/v2.php/apps/files_sharing/api/v1/shares/pending/27238dc5-b2c2-4c6f-8ce8-e64c0d742770 -u Carol:1234 -v;

As user Alice, get all the shares and update the last share as:

curl -k -X GET https://localhost:9200/ocs/v2.php/apps/files_sharing/api/v1/shares -u Alice:1234 | xmllint --format -

    <element>
      <id>6c1276d3-a4d7-4690-8737-93ee9fa355db</id>
      <share_type>0</share_type>
      <uid_owner>Alice</uid_owner>
      <displayname_owner>Alice</displayname_owner>
<EMAIL_ADDRESS>      <permissions>23</permissions>
      ...
      <uid_file_owner>Alice</uid_file_owner>
      <displayname_file_owner>Alice</displayname_file_owner>
<EMAIL_ADDRESS>      <state>0</state>
      <path>/TMP</path>
      <item_type>folder</item_type>
      ...
      <file_target>/TMP</file_target>
      <share_with>Brian</share_with>
      <share_with_displayname>Brian</share_with_displayname>
<EMAIL_ADDRESS>      ...
    </element>
    <element>
      <id>27238dc5-b2c2-4c6f-8ce8-e64c0d742770</id>
      <share_type>0</share_type>
      <uid_owner>Brian</uid_owner>
      <displayname_owner>Brian</displayname_owner>
<EMAIL_ADDRESS>      <permissions>23</permissions>
      ...
      <uid_file_owner>Alice</uid_file_owner>
      <displayname_file_owner>Alice</displayname_file_owner>
<EMAIL_ADDRESS>      <state>0</state>
      <path>/TMP</path>
      <item_type>folder</item_type>
       ...
      <file_target>/TMP</file_target>
      <share_with>Carol</share_with>
      <share_with_displayname>Carol</share_with_displayname>
<EMAIL_ADDRESS>      <mail_send>0</mail_send>
    </element>

curl -k -X PUT https://localhost:9200/ocs/v2.php/apps/files_sharing/api/v1/shares/6 -u Alice:1234 -d permissions=7

< HTTP/1.1 500 Internal Server Error
<ocs><meta><status>error</status><statuscode>996</statuscode><message>grpc update share request failed</message></meta></ocs>

Expected behavior
The share should be updated with the integer value as with ocs_api_version 1.
Actual behavior
While using the integer value of the share_id to update the share, the server responds with 500 internal server error.
WIth the actual share_id used, the share is actually updated, but after the share permisson has been updated, the share receiver Brian gets 500 server error when the share to Carol is tried to be deleted.
In short, the behavior on Ocs_api_version 1 and Ocs_api_version 2 are different.

In step 6, when user Alice updates the share using the share id instead of the integer value of the share id, as follows:
curl -k -X PUT https://localhost:9200/ocs/v2.php/apps/files_sharing/api/v1/shares/6c1276d3-a4d7-4690-8737-93ee9fa355db -u Alice:1234 -d permissions=1 -v;

<ocs>
  <meta>
    <status>ok</status>
    <statuscode>200</statuscode>
    <message>OK</message>
  </meta>
  <data>
    <id>6c1276d3-a4d7-4690-8737-93ee9fa355db</id>
    <share_type>0</share_type>
    <uid_owner>Alice</uid_owner>
    <displayname_owner>Alice</displayname_owner>
<EMAIL_ADDRESS>    <permissions>1</permissions>
    ...
    <uid_file_owner>Alice</uid_file_owner>
    <displayname_file_owner>Alice</displayname_file_owner>
<EMAIL_ADDRESS>    <state>0</state>
    <path>/TMP</path>
    <item_type>folder</item_type>
   ...
    <file_target>/TMP</file_target>
    <share_with>Brian</share_with>
    <share_with_displayname>Brian</share_with_displayname>
<EMAIL_ADDRESS>    <mail_send>0</mail_send>
    <name/>
  </data>
</ocs>

However, now user Brian cannot delete his last share as:
curl -k -X DELETE https://localhost:9200/ocs/v2.php/apps/files_sharing/api/v1/shares/27238dc5-b2c2-4c6f-8ce8-e64c0d742770 -u Brian:1234 -v;

HTTP/1.1 500 Internal Server Error

<ocs><meta><status>error</status><statuscode>996</statuscode><message>grpc delete share request failed</message></meta></ocs>

Investigation of: https://github.com/owncloud/ocis/issues/1999

Duplicate of https://github.com/owncloud/ocis/issues/1950 ? If yes, please close.

Duplicate of #1950 ? If yes, please close.

NO. This is different issue.

Note: #1999 has been closed, and the entry in expected-failures has been updated to link to this issue #2011

Since this is 3 years old I consider it either fixed or not relevant enough to be fixed. Closing.

The issue number is no longer mentioned in expected-failures, so it must have been fixed.


Implicit mutability while using APPEND

Here is an example :
[ 'a' ] 'list' STORE
$list 'b' + DROP
$list

The stack contains : ['a']
[ 'a' ] 'list' STORE
$list [ 'b' ]  APPEND DROP
$list

The stack contains : ['a','b']
Since the $list has not been STOREd back, it seems that APPEND is applying mutabilty on the given object.
If this is a normal behaviour, we should point it out in the reference doc for APPEND and other concerned functions.

I think it's something we have to be cautious with. In other language, APPEND is also mutable. May be what we are lacking of is a PUSH and POP mutable functions?

I agree with @aurrelhebert, adding PUSH and POP would be an elegant way to solve the issue without doing any breaking change.

PUSH or APPEND, the wording is not really the issue. What matters most it the behaviour behind the word.

I guess than a mutable PUSH (and POP) fit nicely (in a semantic way) with other list and map manipulation functions (APPEND, PUT...). As I don't see easy modifying all those functions, adding them could make things more uniform (IMHO).

The function '+!' was added in novembre 2016 (commit 8562e01669ea895b0535afc8d806f032d59951c6) to allow to add elements to the original list.


Publisher does not automatically propagate otel baggage information when publishing event

Is your feature request related to a problem? Please describe.
In version 1.133.0, java pubsub client already use OpenTelemetry. But after testing it, it does not automatically propagate baggage information. It only propagates traceparent information.
Describe the solution you'd like
Automatically propagate baggage information.
Describe alternatives you've considered
Automatically propagate context using registered propagators in open telemetry.
Additional context
Similar to how kafka auto instrumentation works, they use openTelemetry.getPropagators().getTextMapPropagator() to get the propagators and inject it using propagator().inject(context, record.headers(), SETTER);.
https://github.com/open-telemetry/opentelemetry-java-instrumentation/blob/e2dd703a8a0d47ed12d3beca79dc9740822da4f1/instrumentation/kafka/kafka-clients/kafka-clients-2.6/library/src/main/java/io/opentelemetry/instrumentation/kafkaclients/v2_6/KafkaTelemetry.java#L226

Hello! Currently, across all languages, the Pub/Sub OpenTelemetry design uses the global propagator. In order to propagate baggage information, we would require allowing users to set their own composite propagators. We are considering this in the future, but do not have current plans to implement this. I would advise creating an issue at https://issuetracker.google.com/issues, so that other users may mark their interest in this as well. Thank you!


Apple Privacy Manifest

[x] I've read, understood, and done my best to follow the *CONTRIBUTING guidelines.

Apple is enforcing privacy manifests by Spring 2024, is this something on your radar? 🙏
https://developer.apple.com/news/?id=r1henawx

+1

Alamofire is specifically listed as needing a privacy manifest: https://developer.apple.com/support/third-party-SDK-requirements/

Alamofire has an open PR to add one, pending more confirmation from Apple about what exactly is needed. https://github.com/Alamofire/Alamofire/pull/3792 AlamofireImage doesn't use any of the limited APIs and so shouldn't need one at all.

@jshier Do you have confirmation from Apple that Alamofirelmage will not require this Manifest and will not include it? If so, I will cross this dependency off my list.
Thanks

AlamofireImage shouldn't need its own manifest, as it doesn't use any of the newly restricted APIs (no Alamofire framework collects data of any sort). It should just inherit Alamofire's privacy policy automatically without update.

@jshier Excellent thank you for the fast reply. I will mark this SDK down as it's not required to include the manifest! Great news there.

Alamofire's privacy manifest shipped with 5.9.0, make sure to update.

My reasoning is that if Alamofire is included in the list of privacy manifest requiring SDK's and AlamofireImage is depending on Alamofire then Alamofire needs to include the privacy manifest and AlamofireImage needs to point to that updated version as well.
Now I guess it depends on how deep into child's dependencies the Apple scanning goes 😅


Struggling with making this work on Apple Silicon (M1 Max)

Hi Mark
Thank you very much for your detailed information about graalvm on lambda and the code with cdk using docker to build a native image.  When I run cdk deploy for graalvm-on-lambda/walkthrough/serverless-graalvm-arm64/infrastructure
I get this error in the lambda console when trying to call product route... the function build with graalvm.
START RequestId: ad65dc9b-f6d0-49d5-bd93-6ff92dd7b86e Version: $LATEST
Failed to load the native runtime interface client library /aws-lambda-runtime-interface-client.glibc.so. Exception: Can't load library: /tmp/.aws-lambda-runtime-interface-client
Failed to load the native runtime interface client library /aws-lambda-runtime-interface-client.musl.so. Exception: Can't load library: /tmp/.aws-lambda-runtime-interface-client
Failed to load the native runtime interface client library /aws-lambda-runtime-interface-client.glibc.so. Exception: Can't load library: /tmp/.aws-lambda-runtime-interface-client
Failed to load the native runtime interface client library /aws-lambda-runtime-interface-client.musl.so. Exception: Can't load library: /tmp/.aws-lambda-runtime-interface-client
END RequestId: ad65dc9b-f6d0-49d5-bd93-6ff92dd7b86e
REPORT RequestId: ad65dc9b-f6d0-49d5-bd93-6ff92dd7b86e	Duration: 1144.37 ms	Billed Duration: 1145 ms	Memory Size: 256 MB	Max Memory Used: 43 MB
RequestId: ad65dc9b-f6d0-49d5-bd93-6ff92dd7b86e Error: Runtime exited with error: exit status 255
Runtime.ExitError
I think I have tried almost everything possible, can you perhaps spot the issue?
Kind regards and thanx in advance!
Steffen Egelund Jensen

Im facing the same issue. I build the binary in an ARM Docker  Container on a Intel MacBook.
@stejsj could you find a solution in the meantime?

Sorry for the slow response. The latest version of the aws-lambda-java-runtime-interface-client supports ARM.
<dependency>
    <groupId>com.amazonaws</groupId>
    <artifactId>aws-lambda-java-runtime-interface-client</artifactId>
    <version>2.1.1</version>
</dependency>

You will also need to update the resource-config.json to account for the path change.
https://github.com/aws-samples/serverless-graalvm-demo/blob/main/software/products/src/main/resources/META-INF/native-image/com.amazonaws/aws-lambda-java-runtime-interface-client/resource-config.json
https://github.com/aws-samples/serverless-graalvm-demo - has a complete working sample of these changes.


Online public notice - include year-based timeline of operations

As legal staff working on FOM regulations
I want a statement on the online public notice for each FOM regarding the planned duration of operations using the following wording: "Road construction and harvesting of cutblocks depicted on this Forest Operations Map is scheduled to be conducted between YYYY and YYYY." where YYYY is the start and end years entered by the licensee in the Create/Edit Online Public Notice screen.
so that legal requirements are met.
**Tasks **
-moved to #222 Add database columns for start & end year to the public_notice entity

moved to #222 Modify API back-end to accept these fields
Modify Admin front-end to prompt for these fields on the Create/Edit Online Public Notice screen. Use picker for the year, minimum value will be current year, maximum value will be current year + 7.
Validation logic to treat these as mandatory fields. End year must be >= start year.
To confirm default value, could either be blank, or use current year, or use min/max year of development_date of FOM objects. Start by keeping it simple, start date defaults to current year, end date defaults to blank.
Modify Public - online public notice to provide this statement, likely next to the other dates (exact layout TBD)
pre-existing notices will leave dates blank and not show the statement in the public notice.
Will need to demo functionality to Julius (and/or share screenshots).
Need to clarify what Julius wants to do for his testing and whether he needs this in the demo environment.

Acceptance Criteria

Given a new FOM, I can create the online public notice and pick reasonable years. I am unable to pick a year in the past or a year far in the future.
Given an existing FOM in initial state with an existing online public notice, I can edit the online public notice and change the start/end year values. Validation rules will prevent end < start year.
Given a published FOM with an online public notice that has reached the commenting open date, I can view it in the Public site, see the online public notice, and see the statement with the start/end years.
Given a FOM created, published, and in commenting open prior to this change being deployed, I can view the online public notice and not have the system crash (business behavior to be determined).

Definition of Done

[ ] Ready to Demo in Sprint Review
[ ] Does what I have made have appropriate test coverage?
[ ] Documentation and/or scientific documentation exists and can be found
[ ] Peer Reviewed by 2 people on the team
[ ] Manual testing of all PRs in Dev and Prod
[ ] Merged

There was a strange bug found by Anne-Marie while testing on dev environment which led her to be able to enter year in the past or in future that is not in the year range provided from the date-picker.
The input box was disabled for manually entering and only allows for users to use date-picker to pick the year. This works locally but strangely not working in deployed dev environment provided it happens on the same browsers(Edge/Chrome). This bug is unknown, but I found an alternative solution to disable the input.
Also added additional class-validator at backend to validate year should not be less than current year.

Bug fixes has been pushed to test for Anne-Marie

Julius reviewed the FOM TEST environment and mentioned the functionality is good.
He suggested to change the label (minor change) to remove "Proposed" wording from the frontend label for the new fields to "Start of Operations" and "End of Operations".

While Anne-Marie was testing on new PR for the minor label change that deploy from pipeline to 'dev' she found that the existing public-notices (4 current test data) on the public frontend does not have the new fields show up (for Years of Operations) while she checked the admin frontend with the same FOM record and the Years of Operations appear in admin.
There was no code change for public frontend and only admin that time, nothing is wrong for public code and I checked with that as well after discussion with Anne-Marie.
However, while looking into frontend code, I also changed one more label at frontend although it was not mentioned from business, but just need to keep it consistent with the labeling change at admin. The pipeline redeployed with 'public' end change this time, and after deployment, the fields (for Years of Operation) shows up.
The strange behaviors of the public frontend described above need some investigation. It feels like the admin connects to the backend that has the database with test data migrated correctly while public connects to the backend that has the database with test data migration incorrectly, but how could that happen?
@ArogeG @basilv


Integrating Twitter search API as a tool

Feature request
We are seeking to add a tool to Langchain for Twitter API (v1.1). Integrating the API as a tool will allow agents to search for tweets and timelines using a specific search query that filters by users, locations, hashtags, etc. to respond to prompts.
Motivation
Although Langchain currently has TwitterTweetLoader, we have noticed a plethora of more parameters the Twitter API provides that are not integrated into Langchain. TwitterTweetLoader currently only allows us to specify a list of users to return tweets from and the maximum number of tweets. It would be beneficial if we had more options to specify different operators in search queries. A tool also allows an agent to actively use the API to respond to prompts, without the user having to manually create their own custom tool or load tweets manually.
Your contribution
We have a small team of developers who will be working on this feature request, and we will submit a pull request later in 1-2 months which implements it. We will do our best to follow the guidelines for contributions, as stated in contributing.md.

We like to expand on our initial post by explaining our team's plan for implementing the feature to see if the community has any suggestions. We will provide code later in our pull request, but this is intended to be a high-level summary to engage with the community.
Our tool will be using the Twitter tweet search endpoint (https://developer.twitter.com/en/docs/twitter-api/v1/tweets/search/api-reference/get-search-tweets). We are looking into using the requests package or Tweepy. We will be using BaseModel to add a new utility called TwitterAPIWrapper (added to libs/langchain/utilities) to make a request to the Twitter API. This utility will validate API keys and module installation(s), as well as make requests based on the parameters given. Currently, we are looking to include parameters for: keywords, hashtags, mentions, sender, lang, locale, date, tweet list and max number of results.
The tool will be created as TwitterSearchRun (extending BaseTool and added to libs/langchain/tools) and we will write a new BaseModel subclass TwitterSearchSchema which will describe the run parameters for TwitterSearchRun.
We'll of course be adding tests to libs/langchain/tests/integration_tests/utilities to make sure all our methods are working as intended. We will also look into adding it into docs and a notebook example in docs/extras/integrations/tools.
We welcome any suggestions or concerns about our plan!

Closing the issue, since we ran into unexpected problems getting access to API with the pricing updates. We won't be working on it, so anyone else interested can pick it back up.


enha: add config for linger.ms and batch.size

PR Type
Enhancement

Description

Added Kafka producer configuration for linger.ms (100ms) and batch.size (1MB) to optimize performance:

linger.ms: Introduces a small delay in sending messages, allowing for more batching and potentially reducing the number of requests
batch.size: Sets the maximum size of a request in bytes, helping to accumulate more messages in a single batch

Refactored Kafka client configuration to reduce code duplication:

Created a base client_config with common settings
Modified security protocol-specific configurations to build upon the base config

Maintained existing security protocol configurations (None, SASL_SSL, SSL) while incorporating the new performance settings

Changes walkthrough 📝
Relevant filesEnhancement

kafka.rsOptimize Kafka producer settings and refactor configuration

src/infra/kafka/kafka.rs
Added configuration for linger.ms and batch.size to improve Kafka producer performance  Refactored Kafka client configuration to reduce code duplication  Maintained existing security protocol configurations

+9/-10

💡 PR-Agent usage: Comment /help "your question" on any pull request to receive relevant information

Final benchmark:
RPS Stats: Max: 900.00, Min: 755.00, Avg: 817.92, StdDev: 25.36
TPS Stats: Max: 900.00, Min: 755.00, Avg: 817.59, StdDev: 25.03
Plot: View Plot

Final benchmark:
Run ID: bench-945550140
Git Info:

Branch: main
Commit: 109a456
PR: #1869

Configuration:

Target Account Strategy: Default (Random)

RPS Stats: Max: 1091.00, Min: 449.00, Avg: 888.97, StdDev: 60.41
TPS Stats: Max: 1043.00, Min: 743.00, Avg: 862.79, StdDev: 65.41
Plot: View Plot


Creating a Collapse/Expand All Nodes Button

Hello,
I have successfully struggled in creating my Collapsible Tree Layout with all of my information that I want to display, but I feel it's missing the functionality of a button that expands and collapses all nodes within the tree, without having to click on the nodes themselves. Does anyone know how to create this button? Here's my code for my .html file:
.html:
"

"
I'm not really versed in how this stuff works since I'm still learning, but I am a quick learner when experimenting with it. I haven't been able to crack this yet though, and I'm sure it's probably something simple. Thanks for the help.

hi just add this
         function collapse(d) {
	if (d.children) {
	  d._children = d.children;
	  d._children.forEach(collapse);
	  d.children = null;
	}
  }

  function expand(d) {
	if (d._children) {
		d.children = d._children;
		d.children.forEach(expand);
		d._children = null;
	}
  }

          $("#expand_button").click(function(){
		source.children.forEach(expand);
		update(source);
	});

	$("#collapse_button").click(function(){
		root.children.forEach(collapse);
		update(root);
	});

thanksyou so kuch


Error: Matomo has already been initialized

When I open my app on my localhost and then click on the shopping card for instance,
I get the error "Matomo has already been initialized".
I am not really sure how to fix the error as I only read your documentation and typed in the code as being told to.
This is my module set up:
[...]
`import { UtilsService } from './services/utils.service';
import { NgxMatomoModule, NgxMatomoRouterModule } from 'ngx-matomo-client';
import { environment } from './environment/environment';
export function getCustomSettings(appLoadService: AppLoadService) {
return async () => {
await appLoadService.getSettings();
};
}
@NgModule({
imports: [
CommonModule,
TranslateModule.forChild(),
NgxMatomoModule.forRoot({
siteId: environment.customSettings.matomoConfig.matomoSiteId,
trackerUrl: environment.customSettings.matomoConfig.matomoTrackerUrl,
}),
NgxMatomoRouterModule,
],
exports: [
],`[...]
package.json:
"ngx-matomo-client": "5.0.4",
(Angular 16.2.12)
P.S: Matomo shows me when ever I run the app though.

Hi @GreenfieldC
Can you please provide a minimal repro ?
I can see your configuration contains:
TranslateModule.forChild() and
NgxMatomoModule.forRoot(...) which suggest a confusion in modules configuration. Is NgxMatomoModule.forRoot called at multiple locations? (in lazy-loaded modules, for example)

Indeed, this is explained in README instructions, please take a look.
That's a common pattern in most Angular libraries (never call .forRoot in a child module)


Standardize: global-shortcuts, ipc (main), ipc (render)

Updating the docs per the docs style guide.
Definitely would like @zcbenz :eyes: here. I've made quite a few edits to the ipc docs and want to make sure they're :ok:

This one is ready!
I'd like to double check @zcbenz that how wrote this method and described it looks good (repeated it a few times exchanging async for sync and such):

ipc.sendSync(channel[, arg1][, arg2][, ...])

channel String - The event name.
message (optional)

Send an event to the main process synchronously via a channel. Optionally,
there can be a message: one or a series of arguments, arg, which can have any
type. The main process handles it by listening for the channel event with ipc.

Looks good to me :+1:.

:sparkles:


Constants for defined values

This issue is more of a suggested improvement than a direct issue.
For objects that have defined values, the SDK would be easier to use if the values were constants such as Java enums.  It may also fit with good programming standards to use constants instead of passing strings around where defined values are expeted.
I'm sure there could be other defined values that would work well as constants, but the two that I have dealt directly with so far are:  messaging "type" and integration "status".
Messaging "type" would be beneficial to have defined as constants for supported types. In my implementation we have something like this:
/**
 * Smooch messaging type enum. Supported messaging platforms
 */
public enum MessageType {

    TWITTER("twitter"),
    FACEBOOK("messenger"),
    LINE("line");

    private final String type;

    MessageType(String type) {
        this.type = type;
    }

    public String getType() {
        return type;
    }
}

For the integration "status"  I defined them like this based of the documentation possible values:
/**
 *  Possible values for a smooch integration status.
 *
 *  https://github.com/smooch/smooch-java/blob/master/docs/Integration.md
 */
public enum IntegrationStatus {

    ACTIVE("active"),
    INACTIVE("inactive"),
    ERROR("error");

    private final String status;

    IntegrationStatus(String status) {
        this.status = status;
    }

    public String getStatus() {
        return status;
    }
}

Thanks for the suggestion. The code in this library is auto-generated, so depending on the tooling it might not be possible to make improvements like this, but we'll look into whether or not it's possible and update this issue


eth_subscribe not working

Component
Anvil
Have you ensured that all of these are up to date?

[X] Foundry
[X] Foundryup

What version of Foundry are you on?
0.2.0
What command(s) is the bug in?
No response
Operating System
macOS (Apple Silicon)
Describe the bug
eth_subscribe gives the following error:
{'jsonrpc': '2.0', 'id': 1, 'error': {'code': -32602, 'message': 'data did not match any variant of untagged enum EthRpcCall'}}

Here's the code:
async with connect("ws://localhost:8545") as ws:
    await ws.send(json.dumps({
        "jsonrpc": "2.0",
        "id": 1,
        "method": "eth_subscribe",
        "params": ["newHeads"]
    }))
    subscription_id = json.loads(await ws.recv())["result"]
    print(subscription_id)
    while True:
        message = await ws.recv()
        print(json.loads(message))
        # this prints: {'jsonrpc': '2.0', 'id': 1, 'error': {'code': -32602, 'message': 'data did not match any variant of untagged enum EthRpcCall'}}

this looks like eth_subscribe installs correctly because you get the subscription_id ?
what does
message = await ws.recv() do exactly?
could you please try running with RUST_LOG=rpc=warn anvil ... this should log the rpc call that failed

thank you for this @mattsse
I was able to debug with RUST_LOG=rpc=warn anvil it was an error on my code! Sorry for the spam :(


"gerrit-repo-list" entity missing on GET & POST Gerrit endpoint for "https://mockapi.gerrit.dev.itx.linuxfoundation.org/"

Summary
"gerrit-repo-list" entity missing on GET & POST Gerrit endpoint for "https://mockapi.gerrit.dev.itx.linuxfoundation.org/"
Issue:
"gerrit-repo-list" not listed due to that Gerrit connection failed on PCC
Background
Link: https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/api-docs#tag/gerrits/operation/ListGerrits
GET Endpoint:
{{baseUrl}}cla-service/v4/cla-group/{{cla_group_id}}/project/{{project_sfid}}/gerrits

Response:
{
"list": [
{
"dateCreated": "2024-07-30T10:09:11Z",
"dateModified": "2024-07-30T10:09:11Z",
"gerritId": "ad1a8b61-88f6-4679-b6b1-085a3ec34f92",
"gerritName": "mock",
"gerritUrl": "https://mockapi.gerrit.dev.itx.linuxfoundation.org/",
"projectId": "01af041c-fa69-4052-a23c-fb8c1d3bef24",
"projectSFID": "a09P000000DsCE5IAN",
"version": "v2"
}
]
}

POST Endpoint
{{baseUrl}}cla-service/v4/cla-group/{{cla_group_id}}/project/{{project_sfid}}/gerrits

Response:
{
"dateCreated": "2024-07-30T10:09:11Z",
"dateModified": "2024-07-30T10:09:11Z",
"gerritId": "ad1a8b61-88f6-4679-b6b1-085a3ec34f92",
"gerritName": "mock",
"gerritUrl": "https://mockapi.gerrit.dev.itx.linuxfoundation.org/",
"projectId": "01af041c-fa69-4052-a23c-fb8c1d3bef24",
"projectSFID": "a09P000000DsCE5IAN",
"version": "v2"
}

Expected behavior

{
"list": [
{
"dateCreated": "2019-05-03T18:59:13.082304+0000",
"dateModified": "2019-05-03T18:59:13.082304+0000",
"gerrit-repo-list": {
"repos": [
{
"claEnabled": true,
"connected": true,
"contributorAgreements": [
{
"description": "Test Project Authorized Contributor",
"name": "CLA Project 1",
"url": "https://api.dev.lfcla.com/v2/gerrit/138c2d54-1151-11e9-ab14-d663bd873d93/individual/agreementUrl.html"
}
],
"description": "Ansible docker installation role",
"id": "ansible%2Froles%2Fdocker-install",
"name": "ansible/roles/docker-install",
"state": "ACTIVE",
"webLinks": [
{
"name": "gitweb",
"url": "https://gerrit.linuxfoundation.org/infra/gitweb?p\u003dansible%2Froles%2Fhaveged-install.git;a\u003dsummary"
}
]
}
]
},
"gerritId": "e82c469a-55ea-492d-9722-fd30b31da2aa",
"gerritName": "ONAP",
"gerritUrl": "https://gerrit.onap.org",
"groupIdCcla": "1902",
"projectId": "c71c469a-55ea-492d-9722-fd30b31da2aa",
"projectSFID": "abda234423",
"version": "v1"
}
]
}

Screenshots

@thakurveerendras kindly reverify this change

Tested on the dev site & found that it is working fine for the GET endpoint but still failing for the POST call
POST Endpoint:

Expected:

https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/api-docs#tag/gerrits/operation/addGerrit

GET Endpoint:

@thakurveerendras kindly reverify the Add gerrit flow

@nickmango with mock Gerrit server, it is still reproducible for POST endpoint

so due to the production release planned for today will revert these updates for now

@thakurveerendras kindly review

Tested on dev site & found that it is fixed as expected for POST Gerrit endpoint too.
Refer screenshot for more details

@thakurveerendras is this working as expected and can we release this "Gerrit authorization API"? Once this is released then we will fix pending records mentioned here and build logic which uses this API.

Hi @mlehotskylf , @nickmango
Retested and it is working fine dev site & we are good to deploy it on prod
Refer screenshot for more details


Beautify Table of Contents in CV

Is your feature request related to a problem? Please describe.
For "Table of Contents" in recently merged CV #1339 , when there are many contents it leaves the right side empty which looks a bit odd.

Describe the solution you'd like

Option for a horizontal table of contents would be nice.  Maybe something like this,

Table of contents on the sidebar like blog??

cc: @george-gca @jmrplens

Maybe it could look something like this template?

Its table of contents looks very nice. But it doesn't have the nice floating "card" view that al-folio have. So may be table of contents from the template + al-folio theme???

Exactly what I was thinking. Now let's see if anyone can tackle this issue.

Would you be happy with the screenshots below? If yes, I can make a pull request. Or must there be dots on the sidebar as well? (which I would be unable to do at the moment)

I think it looks nice, @george-gca  what do you think???

I believe it doesn't need to have the dots, but it would look nice. Maybe something as shown in this template. But create the PR, maybe we could help to create this layout.

@george-gca I agree the dots would make it even better


update alert report query to verify column exists before keeping it

from: https://github.com/influxdata/flux/issues/1977
looks like we need to be more defensive here and add a check for if a column exists in our alert history query since the system buckets are open for anyone to write into.
This could also be solved if the flux team decides to add this: https://github.com/influxdata/flux/issues/1975

We'll need to do something like
from(bucket: "_monitoring")
  |> range(start: -60d)
  |> filter(fn: (r) => r._measurement == "statuses" and r._field == "_message")
  |> filter(fn: (r) => exists r._check_id)
  |> filter(fn: (r) => exists r._check_name)
  |> filter(fn: (r) => exists r._level)

for the alert history page

Link https://github.com/influxdata/influxdb/pull/15525

@ebb-tide will we need to update the queries that are used to populate the event markers?


"N snapshots can be trimmed" but nothing is trimmed?

When I run my test suite, I get this output at the end:
=============== inline snapshot ====================
Info: 11 snapshots can be trimmed (--inline-snapshot=trim)

From the docs:

trim removes every snapshots form the storage which is not referenced with external(...) in the code.

However if I run pytest with --inline-snapshot=trim it doesn't do anything. I have 11 external files indeed, so I suspect inline-snapshot doesn't detect external calls in my code:
snapshots = snapshot(
    {
        (
            ("annotations_path", "brief"),
            ("separate_signature", True),
            ("show_signature", False),
            ("show_signature_annotations", False),
            ("signature_crossrefs", False),
            ("unwrap_annotated", True),
        ): external("3603a08e7614*.html"),
        ...
    }
)

Can't reproduce while debugging. external calls are correctly identified.

0.9.0 contains now a check if you use xdist at the same time.
I think there are several issues with the current implementation of outsource. I have some ideas how the DX could be improved and wrote it down (#86). Please tell me if you have some feedback.

I think we can close this, since pytest-xdist is explicitly not supported. I tried again today and it works fine when xdist is not used.


Issue-112: Implement the header layout.

[X] This pull request has been linted by running npm run lint without errors
[X] This pull request has been tested by running npm run dev and reviewing affected routes
[X] This pull request has been built by running npm run generate without errors
[X] This isn't a duplicate of an existing pull request

Description

Implement the layout for the site header.
Take the chance to adjust the style linting config to set the indentation rule to 4 spaces.

Steps to test

Run npm run dev
Test the header layout in desktop and mobile browsers.

Expected behavior:
The header style should match the visual design.

All review comments have been addressed. This pull request is ready for another review. Thanks.

I think the breakpoint for switching from mobile nav to desktop nav needs to be increased. Maybe 1024px?  Thoughts @cindyli?

Good point. Will make the adjustment.

@TeddTech as now the netlify site is fetching data from a non-production backend. I added a few more views-typed posts into it. The "new and views" page now has more than 1 page and pagination is showing. Could you style the pagination too. Thanks.

All comments have been addressed. This pull request is ready for another look.


Remove wl_shell support

This protocol is part of the core Wayland, but it is pretty badly
designed and is missing quite a few features, and is in the process of
being phased out in compositors.  Its support in GLFW requires
duplicating pretty much every single window management codepath.
This bumps the required compositor versions to the ones which have
implemented xdg-shell, approximately two years ago, which seems sensible
to me.

Seems good 👍

FYI neither weston nor sway have current releases that support the stable version of this, so if you want to do it, you will need to add support for the unstable version as well (zxdg_shell_v6)

Sway at least does, since its 1.0 release.
As for Weston, it is in RC1 stage now, and most users won’t use it as their main compositor anyway so we can easily ignore it.

Yes but sway 1.0 was just released, which means lots of people wont have
it on their distros for a while.

3.3 got released, there is no reason not to merge this anymore, the next version will most likely get released in a world where wl_shell is completely irrelevant. \o/


Is there any plan to add ustl::function class?

Only if you want to do the work. functors are perhaps the single most complex part of the standard library, and I am not even going to try.


will add Excel word PDFfile upload?

will add Excel word PDFfile upload?

what's the use case you are considering?

check out comfyui_LLM_party node: https://github.com/heshengtao/comfyui_LLM_party
I might have what you need


VSCode RPM package is not signed

VSCode Version: 1.40.1-1573664332.el7
OS Version: Fedora 30

Steps to Reproduce:

Install latest VS Code

Results:
code-1.40.1-1573664332.el7.x86_64.rpm: Already downloaded
Package code-1.40.1-1573664332.el7.x86_64.rpm is not signed

I can confirm.

/duplicate of #84752


Hide microphone logo

Issue #: #3
Description of changes: Add Firefox preferences to hide microphone indicator
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

If this one is accepted I will create another PR into https://github.com/aws-samples/amazon-chime-meeting-broadcast-demo


Drop peer list and discovery integration

All the logic that is related to peers should be either completely removed or extracted into another package.

https://github.com/ArkEcosystem/typescript-peers


Gene search not working

Neither by ENSEMBL id nor by gene symbol. For example, "no DNA Features found" for BRCA1: https://test-cegsptl.dkstest.dhe.duke.edu/search/results/?query=ENSG00000012048

Fixed by https://github.com/ReddyLab/cegs-portal/issues/12


Spain changes

Fixed some typos (Ceuta) and some wrong short codes and names, according to ISO 3166

Thanks @gui64!


CI is broken due to PR #488

CI is broken due to PR #488. Let's revert the PR.
Please run local test enough.

Screenshot:

 ./checker-pr-gateway.sh<PHONE_NUMBER>45250.28938007354736 58f5ed8a51a2561d6c012303b177f4583acde96d https://github.com/leemgs/TAOS-CI.git upstream-apptest-network-model-time 491 12165dc0-4c6e-11e9-909a-02c075ef7d1f

/var/www/html/TAOS-CI/ci/repo-workers/pr-checker/491-201903221545250.28938007354736-58f5ed8a51a2561d6c012303b177f4583acde96d/TAOS-CI
[DEBUG] Added format checker
[DEBUG] Added audit checker
[DEBUG] Running all checkers
./checker-pr-gateway.sh: line 152: warning: checker_cmd_list: circular name reference
[DEBUG] Completed all checkers
www-data@ip-172-31-27-164:~/TAOS-CI/ci/taos$ vi ./

:octocat: cibot: Thank you for posting issue #492. The person in charge will reply soon.

PTAL @kparichay


[BUG] After adding taint to a node, volume cannot be attached to any other node

Describe the bug
Volume stuck in attaching after setting taint for a one of it replicas' node
To Reproduce

Create a cluster of 3 Longhorn nodes.
Create a volume of 3 replicas
Set taint f:b=NoExecute for a node
Wait for Kubernetes to evict workloads from tainted node
Attach the volume. Observe that the volume stuck in attaching state

Expected behavior
Longhorn should skip the replica on the tainted node and finish attaching volume
Environment:

Longhorn version: Longhorn master  version - 04/12/21

Additional context
The replica controller always set the state of the replica: status.CurrentState = types.InstanceStateStopped when the corresponding instance manager is in error state. On the other hand, the volume controller insists on waiting until all replicas to be in running state before finishing attaching the volume

Proposal: when the instance manager is in error or unknown state. We should mark the related replica/engine as unknown instead of stopped. Then in the volume controller, don't wait for the unknown replica to be running.

This is not a regression and it's a day 1 issue.

Validation: PASSED


[iOS] When closing the Google Translate screen, it does not return to the previously opened screen.

Steps to Reproduce

Launch the app and open the timeline or feed.
Open a thread with a post written in a language different from the one set as Primary Language.
Tap the Translate button to open the Google Translate screen.
Tap Done in the top left corner of the screen.

Attachments
https://github.com/user-attachments/assets/f5c15ac8-03a6-41f7-9098-2e9ec28d832e
What platform(s) does this occur on?
iOS
Device Info
iPhone 14 Pro
What version of the app are you using?
Build version: <IP_ADDRESS>2; Bundle info: 3c30bb1 (prod); Bundle date: 24111623; Platform: ios; Platform version: 18.1.1
Additional Information
No response

@surfdude29
Since version 1.95 of the iOS app is not yet available, I would like to wait until it's released and verify that the issue is resolved before closing this issue. Would that be okay with you?
I’m not entirely familiar with how issues are handled in this project. If the Bluesky team usually handles closing issues, I don’t mind if you go ahead and close it.

Since version 1.95 of the iOS app is not yet available, I would like to wait until it's released and verify that the issue is resolved before closing this issue. Would that be okay with you?

@nnabeyang Of course, that's totally fine, I just wanted to let you know what the status was and that it should be fixed soon :)

I’m not entirely familiar with how issues are handled in this project. If the Bluesky team usually handles closing issues, I don’t mind if you go ahead and close it.

To be clear, I'm just a volunteer contributor, so I can't close other people's issues in any case 😅

@surfdude29
Got it, thank you for the clarification.

I have conducted initial tests on Android and iOS, and the translation feature works well after this PR. But hey, I agree that we should perform a secondary confirmation after the official release.
As a temporary workaround, you might want to try this.

I have confirmed that the bug has been fixed in version 1.95.

I have confirmed that the bug has been fixed in version 1.95.