How works Prometheus Integration ?

Hello team,
I see that IBm bridge for grafana support promtheus.
It is possible to explain how it is working (update readme maybe) ? And how to use it ?
And can you update your dockerfile to use Prometheus Exporter API ?
Regards,

Hi @SckyzO,
Prometheus support is currently in the implementation phase.
The dockerfile update is also on the development todo list.
As soon as the development is finished, I'll post a clear user guide on the wiki.
If you want to try out the current code, say a beta version, I can give you a short tutorial on how to set it up.
Helene

Hello @Helene
Ok, I understand :) This will definitely be a good feature :)
Do you know when a final version with official Prometheus support will arrive?
I would like a "docker/podman" version even in beta. I have to implement it for a client and I would like to start working on the subject. I understood how it worked but in container mode it is not yet supported (I adapted the dockerfile but there is still work). The problem is that I am on a closed network, so the python pip offline part must be managed offline. I would therefore prefer to make it work with containers :)
Tom

Hi @SckyzO,
I updated the Dockerfile. Now you should be able build and run grafana-bridge as prometheus-exporter in a container.
Check PR #172 for some examples. The wiki article will be updated once implementation and testing are complete.
Don't forget to create ssl certificates prior you start with pod deployment.
Your early feedback would be greatly appreciated.

Hello Helene. I can't run my container, I have many error with cherry and certificate :
For example :
[22/Feb/2024:14:20:23] ENGINE Error in HTTPServer.serve
Traceback (most recent call last):
  File "/usr/local/lib/python3.9/site-packages/cheroot/server.py", line 1814, in serve
    self._connections.run(self.expiration_interval)
  File "/usr/local/lib/python3.9/site-packages/cheroot/connections.py", line 198, in run
    self._run(expiration_interval)
  File "/usr/local/lib/python3.9/site-packages/cheroot/connections.py", line 241, in _run
    new_conn = self._from_server_socket(self.server.socket)
  File "/usr/local/lib/python3.9/site-packages/cheroot/connections.py", line 294, in _from_server_socket
    s, ssl_env = self.server.ssl_adapter.wrap(s)
  File "/usr/local/lib/python3.9/site-packages/cheroot/ssl/builtin.py", line 270, in wrap
    s = self.context.wrap_socket(
  File "/usr/lib64/python3.9/ssl.py", line 501, in wrap_socket
    return self.sslsocket_class._create(
  File "/usr/lib64/python3.9/ssl.py", line 1074, in _create
    self.do_handshake()
  File "/usr/lib64/python3.9/ssl.py", line 1343, in do_handshake
    self._sslobj.do_handshake()
ssl.SSLZeroReturnError: TLS/SSL connection has been closed (EOF) (_ssl.c:1129)

And, if we use container with certificate, why do not add certificate directly in the container ? It is a localhost self-signed certificate
Another bug, log folder haven't good right, logrotate can't work and if you mount local path with container log path (/var/log/ibm_bridge_for_grafana), container can't create log files. Workarround, local folder 777 mode and create empty log files with 777 mode. 😄
I continue to debug :) I don't know why, I started my container one time, but after kill and re-run container, it never restarted ...
Another question, I have to recover mmsdrfs, but in my case, you have to add hardware gradually to my ESS architecture, so I think that this file should be passed as an argument (mount a local path with this file I think) , because I will have to rebuild the container if my architecture evolves.

Juste for information, my container is started, i always have "ssl error" as said in my previons comment, but it working.
In log, I have many Warnings
Like this :
[ . . . ]
2024-02-27 09:28 - CP Server Thread-10            - WARNING  - Received null values in all data points for gpfs_fs_write_ops
2024-02-27 09:28 - CP Server Thread-10            - WARNING  - Received null values in all data points for gpfs_fs_write_ops
2024-02-27 09:28 - CP Server Thread-10            - WARNING  - Received null values in all data points for gpfs_fs_write_ops
2024-02-27 09:28 - CP Server Thread-10            - WARNING  - Received null values in all data points for gpfs_fs_write_ops
2024-02-27 09:28 - CP Server Thread-10            - WARNING  - Received null values in all data points for gpfs_fs_write_ops
2024-02-27 09:28 - CP Server Thread-10            - WARNING  - Received null values in all data points for gpfs_fs_write_ops
2024-02-27 09:28 - CP Server Thread-10            - WARNING  - Received null values in all data points for gpfs_fs_write_ops
2024-02-27 09:28 - CP Server Thread-10            - WARNING  - Received null values in all data points for gpfs_fs_write_ops
2024-02-27 09:28 - CP Server Thread-10            - WARNING  - Received null values in all data points for gpfs_fs_write_ops
2024-02-27 09:28 - CP Server Thread-10            - WARNING  - Received null values in all data points for gpfs_fs_write_ops
2024-02-27 09:28 - CP Server Thread-10            - WARNING  - Received null values in all data points for gpfs_fs_write_ops
2024-02-27 09:28 - CP Server Thread-10            - WARNING  - Received null values in all data points for gpfs_fs_write_ops
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_bytes_read
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_bytes_read
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_bytes_read
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_bytes_read
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_bytes_read
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_bytes_read
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_bytes_read
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_bytes_read
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_bytes_read
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_bytes_read
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_bytes_read
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_bytes_read
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_bytes_read
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_bytes_read
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_bytes_read
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_bytes_read
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_bytes_read
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_bytes_written
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_bytes_written
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_bytes_written
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_bytes_written
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_bytes_written
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_bytes_written
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_bytes_written
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_bytes_written
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_bytes_written
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_bytes_written
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_bytes_written
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_bytes_written
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_bytes_written
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_bytes_written
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_bytes_written
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_bytes_written
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_bytes_written
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_disks
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_disks
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_disks
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_disks
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_disks
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_disks
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_disks
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_disks
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_disks
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_disks
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_disks
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_disks
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_disks
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_disks
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_disks
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_disks
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_disks
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_max_disk_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_max_disk_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_max_disk_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_max_disk_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_max_disk_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_max_disk_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_max_disk_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_max_disk_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_max_disk_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_max_disk_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_max_disk_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_max_disk_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_max_disk_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_max_disk_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_max_disk_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_max_disk_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_max_disk_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_max_disk_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_max_disk_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_max_disk_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_max_disk_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_max_disk_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_max_disk_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_max_disk_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_max_disk_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_max_disk_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_max_disk_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_max_disk_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_max_disk_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_max_disk_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_max_disk_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_max_disk_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_max_disk_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_max_disk_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_max_queue_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_max_queue_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_max_queue_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_max_queue_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_max_queue_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_max_queue_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_max_queue_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_max_queue_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_max_queue_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_max_queue_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_max_queue_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_max_queue_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_max_queue_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_max_queue_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_max_queue_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_max_queue_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_max_queue_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_max_queue_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_max_queue_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_max_queue_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_max_queue_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_max_queue_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_max_queue_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_max_queue_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_max_queue_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_max_queue_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_max_queue_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_max_queue_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_max_queue_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_max_queue_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_max_queue_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_max_queue_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_max_queue_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_max_queue_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_min_disk_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_min_disk_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_min_disk_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_min_disk_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_min_disk_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_min_disk_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_min_disk_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_min_disk_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_min_disk_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_min_disk_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_min_disk_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_min_disk_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_min_disk_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_min_disk_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_min_disk_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_min_disk_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_min_disk_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_min_disk_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_min_disk_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_min_disk_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_min_disk_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_min_disk_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_min_disk_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_min_disk_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_min_disk_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_min_disk_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_min_disk_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_min_disk_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_min_disk_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_min_disk_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_min_disk_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_min_disk_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_min_disk_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_min_disk_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_min_queue_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_min_queue_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_min_queue_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_min_queue_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_min_queue_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_min_queue_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_min_queue_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_min_queue_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_min_queue_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_min_queue_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_min_queue_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_min_queue_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_min_queue_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_min_queue_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_min_queue_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_min_queue_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_min_queue_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_min_queue_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_min_queue_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_min_queue_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_min_queue_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_min_queue_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_min_queue_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_min_queue_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_min_queue_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_min_queue_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_min_queue_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_min_queue_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_min_queue_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_min_queue_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_min_queue_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_min_queue_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_min_queue_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_min_queue_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_read_ops
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_read_ops
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_read_ops
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_read_ops
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_read_ops
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_read_ops
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_read_ops
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_read_ops
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_read_ops
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_read_ops
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_read_ops
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_read_ops
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_read_ops
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_read_ops
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_read_ops
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_read_ops
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_read_ops
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_tot_disk_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_tot_disk_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_tot_disk_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_tot_disk_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_tot_disk_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_tot_disk_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_tot_disk_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_tot_disk_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_tot_disk_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_tot_disk_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_tot_disk_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_tot_disk_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_tot_disk_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_tot_disk_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_tot_disk_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_tot_disk_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_tot_disk_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_tot_disk_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_tot_disk_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_tot_disk_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_tot_disk_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_tot_disk_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_tot_disk_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_tot_disk_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_tot_disk_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_tot_disk_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_tot_disk_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_tot_disk_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_tot_disk_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_tot_disk_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_tot_disk_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_tot_disk_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_tot_disk_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_tot_disk_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_tot_queue_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_tot_queue_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_tot_queue_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_tot_queue_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_tot_queue_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_tot_queue_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_tot_queue_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_tot_queue_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_tot_queue_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_tot_queue_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_tot_queue_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_tot_queue_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_tot_queue_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_tot_queue_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_tot_queue_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_tot_queue_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_tot_queue_wait_rd
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_tot_queue_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_tot_queue_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_tot_queue_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_tot_queue_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_tot_queue_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_tot_queue_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_tot_queue_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_tot_queue_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_tot_queue_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_tot_queue_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_tot_queue_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_tot_queue_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_tot_queue_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_tot_queue_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_tot_queue_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_tot_queue_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_tot_queue_wait_wr
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_write_ops
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_write_ops
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_write_ops
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_write_ops
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_write_ops
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_write_ops
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_write_ops
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_write_ops
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_write_ops
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_write_ops
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_write_ops
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_write_ops
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_write_ops
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_write_ops
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_write_ops
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_write_ops
2024-02-29 13:39 - CP Server Thread-12            - WARNING  - Received null values in all data points for gpfs_fs_write_ops

I don't know why and how to check this warnings ... If you have an idea :)

Oh, I found in code the list of all endpoints :)
https://github.com/IBM/ibm-spectrum-scale-bridge-for-grafana/blob/master/source/prometheus_endpoints.json
Maybe you should update Prometheus Readme with this list :)
@Helene very good job pour this prometheus integration development

Hello  @SckyzO ,
I'm very sorry for answering with delay to you. I was very busy with another project.
Many thanks for your feedback.
The ssl exception you are seening is comming from CherryPy application. It is known issue. Finally it has been fixed 2 weeks ago but not published yet from CherryPy development team. You can follow on this
https://github.com/cherrypy/cheroot/pull/518.

Workarround, local folder 777 mode and create empty log files with 777 mode. 😄

That is correct your local folder, where you mount the grafana-bridge logs, need to have write permissions, otherwise the log files could not be updated. Are you running grafana-bridge container on baremetal or on a kubernetes cluster. On kubernetes you can make the installing process much easier using deployment script.

Another question, I have to recover mmsdrfs, but in my case, you have to add hardware gradually to my ESS architecture, so I think that this file should be passed as an argument (mount a local path with this file I think) , because I will have to rebuild the container if my architecture evolves.

This is a good point. Mounting mmsdrfs/ZIMonsensors.cfg file would make sense. Please open for this a separate issue.
I'm a little bit worry about the messages
2024-02-27 09:28 - CP Server Thread-10            - WARNING  - Received null values in all data points for gpfs_fs_write_ops
2024-02-27 09:28 - CP Server Thread-10            - WARNING  - Received null values in all data points for gpfs_fs_write_ops
2024-02-27 09:28 - CP Server Thread-10            - WARNING  - Received null values in all data points for gpfs_fs_write_ops
2024-02-27 09:28 - CP Server Thread-10            - WARNING  - Received null values in all data points for gpfs_fs_write_ops
2024-02-27 09:28 - CP Server Thread-10            - WARNING  - Received null values in all data points for gpfs_fs_write_ops
2024-02-27 09:28 - CP Server Thread-10            - WARNING  - Received null values in all data points for gpfs_fs_write_ops

Are you using the latest grafana-bridge code?
Could you please paste me your settings in the config.ini for prometheus part. Something like this:
##################### Prometheus Exporter API Connection Defaults #############
# Port number the bridge listening on for Prometheus server https requests;
# ssl cert and key configuration required
prometheus = 9250

# Sensor counters deltas will be exported by default.
# Set True if you want export original sensor counters.
rawCounters = True

Also verify your prometheus config file prometheus.yaml has a correct job definition
  - job_name: 'GPFSFilesystem_cluster1'
    scrape_interval: 300s
    honor_timestamps: true
    metrics_path: '/metrics_gpfs_filesystem'
    scheme: https
    tls_config:
      cert_file: /etc/prometheus/certs/cluster1/cert.pem
      key_file: /etc/prometheus/certs/cluster1/privkey.pem
      insecure_skip_verify: true
    static_configs:
    - targets: ['9.152.x.x:9250']

Oh, I found in code the list of all endpoints :)
https://github.com/IBM/ibm-spectrum-scale-bridge-for-grafana/blob/master/source/prometheus_endpoints.json
Maybe you should update Prometheus Readme with this list :)
@Helene very good job pour this prometheus integration development

Yes the endpoints need to be documented. I'm still working on documentation.
Many thanks for the praise !


Add implementations for node_replace_with/node_insert_before/node_insert_after, minor tweaks

I need such implementation in the project I'm working at. Might be helpful as well for others.
Also please review if the implementation is correct.
Thanks!

@lexborisov, can you also take a look if it is a proper way to do something like this with Modest?
Thanks!

Looks good. Can you please update CHANGES.rst and add your recent changes to it?

@rushter , done! I've rebased with master, created new version row and added new methods there.

@kkszysiu Does it make sense to keep separate methods for nodes?
I think we can check the type of the argument. We can also convert strings to nodes and remove the plain-text limitation.
So, instead of two methods, we could use one with an extra argument for backward compatibility:
def replace_with(self, value, bool parse=False):

If value is a string and parse is True, treats the input as HTML and parses it.

What do you think?

@rushter that's a good question. I was thinking about it at first to just make them single methods but I was afraid I will degrade the performance. As far as I understand then, Cython would need to add another guard in such case as it wouldn't be able to assume we are passing string (I'm not an expert in Cython in any way, that was just my understanding).
I was trying to avoid performance degradation in this case, after all that's why I chosen selectolax over lxml at first place, so that's why I've implemented it as separate methods, but if you think it makes sense to keep them as single methods and the performance woudln't be affected much, then I can surely change it! :)

I think fused types can take care of type dispatching.
Usually, type checking and conversion is not the most expensive operation. The lxml library is slow because of the underlying libxml2 library.

@rushter, yeah. That makes sense. Okay then, let me rewrite it as a single methods, it would be much cleaner.

@rushter , one more thing. Do you think it would be better to add parse param or just allow people to pass string or Node?
Something like that:
def replace_with(self, value):
Where value could be str or Node and inside the method we will check what was passed.
Otherwise we will kind of limit/assume that user wants to have root.body.child.html, right?
But what if user actually want to insert some other node?
For example in my case I have bunch of dummy tags in my HTML tree and I'm replacing them with actual, real elements from another parsed tree, so such method makes much more sense to me, but not sure about real world usage.

@rushter , one more thing. Do you think it would be better to add parse param or just allow people to pass string or Node?
Something like that:
def replace_with(self, value):
Where value could be str or Node and inside the method we will check what was passed.
Otherwise we will kind of limit/assume that user wants to have root.body.child.html, right?
But what if user actually want to insert some other node?
For example in my case I have bunch of dummy tags in my HTML tree and I'm replacing them with actual, real elements from another parsed tree, so such method makes much more sense to me, but not sure about real world usage.

We should definitely allow passing Node objects. I was concerned about backward compatibility. What's why I proposed an extra parameter. But after your comment, I think it's safe to use def replace_with(self, value). Since old implementation allowed only plain-text, I think our new implementation won't break anything trying to convert it to HTML.
I think we just need to make sure that our new function accepts simple strings with no HTML tags (only text). Selectolax may not parse it correctly.

@rushter , we can check isinstance, in case it is a string, then we will use old logic, in case it is Node, then we will use node replacing logic, something like this I assume would work:
    def replace_with(self, value):
        if isinstance(value, (str, bytes, unicode)):
            cdef myhtml_tree_node_t* text_node
            if isinstance(value, (str, unicode)):
                bytes_val = value.encode(_ENCODING)
            elif isinstance(value, bytes):
                bytes_val = value

            text_node = myhtml_node_create(self.parser.html_tree, MyHTML_TAG__TEXT, MyHTML_NAMESPACE_HTML)
            myhtml_node_text_set(text_node, <char*> bytes_val, len(bytes_val), MyENCODING_UTF_8)
            myhtml_node_insert_before(self.node, text_node)
            myhtml_node_delete(self.node)
        elif isinstance(value, Node):
            cdef myhtml_tree_node_t *node = value.node
            myhtml_node_insert_before(self.node, node)
            myhtml_node_delete(self.node)
        else:
            raise TypeError("Expected a string or Node instance, but %s found" % type(value).__name__)

Right?

@kkszysiu Yes, please document the difference between string and Node objects in the function description.
My idea was to allow passing HTML as a string, but your approach works for me too.

Yes yes, will document everything and fix tests. Thank you!

Any updates?

Hey @rushter , @ppwwyyxx actually yes.
I've tried to implement it in a way @rushter described, but generally it requires to initialise parser inside node.pxi module, which is not a trivial task.
I've also tried to use my approach, where I will just recognise which data is passed to method, but cython is not supporting it.
Do you guys have any idea how we can implement it the other way? If not then maybe merging the current approach I've prepared would be enough for now?
I am already using this approach in my project without any issues.
Thanks!

I've also tried to use my approach, where I will just recognise which data is passed to method, but cython is not supporting it.

What was the problem? It definitely can accept multiple types.

@rushter , maybe then I'm doing something wrong, here is example branch: https://github.com/rushter/selectolax/compare/master...kkszysiu:insert_after_before_replace_nodes2?expand=1
And then when I'm trying to compile it, I'm getting:
selectolax/node.pxi:597:24: Cannot convert Python object to 'myhtml_tree_node_t *'
When I directly pass Node as argument it works.
Any ideas?

@kkszysiu Most likely, you just need to make it obvious for the compiler that you are working with the right object.
node = <myhtml_tree_node_t*> value.node

Oh, let me try @rushter !

Thank you for you contribution. I've published a new release.

I noticed an issue regarding reference. The following code works:
from selectolax.parser import HTMLParser

html_parser = HTMLParser('
Get

')
img_node = html_parser.css_first('img')

html_parser2 = HTMLParser('
Test
')
img_node.replace_with(html_parser2.body.child)
assert html_parser.body.child.html == '
Get
Test

'

but the following fails:
from selectolax.parser import HTMLParser

html_parser = HTMLParser('
Get

')
img_node = html_parser.css_first('img')

img_node.replace_with(HTMLParser('
Test
').body.child)
assert html_parser.body.child.html == '
Get
Test

'

since this is python, I would expect the two to work the same and are memory safe

It seems that a myhtml_tree_node_t cannot have shared ownership. So for a statement A.replace_with(B), it has to do one of the following:

Let B keep ownership -- cause strange failures like above
Let A steal the ownership -- needs to invalidate B in this call, and document the unintuitive behavior clearly
Let A copy the node -- more expensive

Ok, I've opened a new issue

Oh, I haven't experienced this issue myself. I will try to came up with a solution.


Domain services

Designed 3 domain services
Customer aggregate requires AccountId instead of IAccount
Account aggregate requires CustomerId instead of ICustomer
Aggregates and Entities set to abstract

Just to clarify some patterns:

the intent with DomainServices is to create a reusable business rules against aggregates and repositories, they should not invoke UnitOfWork.Save().
the use cases are the coordination object and they should invoke UnitOfWork.Save() in case of writing operations.


Domains doesn't list in the UI Search filter if the count is greater than 500

ISSUE TYPE

BUG

COMPONENT NAME
UI
CLOUDSTACK VERSION
Cloudstack 4.18
SUMMARY
Domains doesn't list in the UI Search filter if the count is greater than 500
Steps to reproduce the issue

Create about 510 domains

Go To compute >instance > Search filter

Try to search domains greater than

Screenshot attached

There is no issue with the listdomains api call, it works properly when pagesize is passed
https://cloudstack.apache.org/api/apidocs-4.18/apis/listDomains.html
The maximum pagesize is 500
(cmk)  > list domains filter=name,state,path, pagesize=501 page=1
🙈 Error: (HTTP 431, error code 4350) Page size can't exceed max allowed page size value: 500
(cmk)  > list domains filter=name,state,path, pagesize=500 page=2
{
"count": 521,
"domain": [
Actual behavior
Cloudstack ui doesn't display the domains > 500 in the search filter
Expected behavior
Cloudstack ui should display the domains > 500 in the search filter

The list domain api response returns all the domain but cloud stack UI is not showing the domains greater than pagesize 500

May be need to look into the "SearchView.vue" in the code base

fixed by #7766, but has 7780 as a follow-up


feat: Public dashboard security rules

Fixes #1557
Checklist

[x] Documented
[x] Unit tested

I have read the CLA Document and I hereby sign the CLA


App crashing in debug mode

I use agora rtc enging version 4.2.0 in my app for video calling but when i import dependency it show me the error
"E/FlutterLoader(13632): Flutter initialization failed.
E/FlutterLoader(13632): java.util.concurrent.ExecutionException: java.lang.UnsatisfiedLinkError: dalvik.system.PathClassLoader[DexPathList[[zip file "/data/app/com.example.video_call_test-2/base.apk"],nativeLibraryDirectories=[/data/app/com.example.video_call_test-2/lib/arm, /data/app/com.example.video_call_test-2/base.apk!/lib/armeabi-v7a, /system/lib, /vendor/lib]]] couldn't find "libflutter.so"
this is my flutter doctor information
Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel stable, 2.8.1, on Microsoft Windows [Version 10.0.19042.1466], locale en-US)
[√] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
[√] Chrome - develop for the web
[√] Android Studio (version 4.2)
[√] VS Code (version 1.63.2)
[√] Connected device (3 available)
• No issues found!

couldn't find "libflutter.so"
pls check your build.gradle

def localProperties = new Properties()
def localPropertiesFile = rootProject.file('local.properties')
if (localPropertiesFile.exists()) {
localPropertiesFile.withReader('UTF-8') { reader ->
localProperties.load(reader)
}
}
def flutterRoot = localProperties.getProperty('flutter.sdk')
if (flutterRoot == null) {
throw new GradleException("Flutter SDK not found. Define location with flutter.sdk in the local.properties file.")
}
def flutterVersionCode = localProperties.getProperty('flutter.versionCode')
if (flutterVersionCode == null) {
flutterVersionCode = '1'
}
def flutterVersionName = localProperties.getProperty('flutter.versionName')
if (flutterVersionName == null) {
flutterVersionName = '1.0'
}
apply plugin: 'com.google.gms.google-services'
apply plugin: 'com.android.application'
apply plugin: 'kotlin-android'
apply from: "$flutterRoot/packages/flutter_tools/gradle/flutter.gradle"
android {
compileSdkVersion 31
compileOptions {
    sourceCompatibility JavaVersion.VERSION_1_8
    targetCompatibility JavaVersion.VERSION_1_8
}

kotlinOptions {
    jvmTarget = '1.8'
}

sourceSets {
    main.java.srcDirs += 'src/main/kotlin'
}

defaultConfig {
    // TODO: Specify your own unique Application ID (https://developer.android.com/studio/build/application-id.html).
    applicationId "com.kmz.TheCounsler"
    minSdkVersion 21
    targetSdkVersion 30
    multiDexEnabled true
    versionCode flutterVersionCode.toInteger()
    versionName flutterVersionName
}

buildTypes {
    release {
        // TODO: Add your own signing config for the release build.
        // Signing with the debug keys for now, so `flutter run --release` works.
        signingConfig signingConfigs.debug
    }
}

}
flutter {
source '../..'
}
dependencies {
implementation "org.jetbrains.kotlin:kotlin-stdlib-jdk7:$kotlin_version"
implementation 'com.android.support:multidex:1.0.3'
implementation 'com.google.android.gms:play-services-safetynet:18.0.1'
implementation 'com.google.firebase:firebase-appcheck-safetynet:16.0.0-beta04'
implementation 'androidx.browser:browser:1.3.0'
}

this is my build.gradle file code

when i comment this dependency than app will running fine but adding this dependency create the issue and app crashing

seem like a bug from flutter.
https://github.com/flutter/flutter/issues/57237

how can i get libflutter.so file

minSdkVersion 25
targetSdkVersion 29
compileSdkVersion 31
please chek these value are right or wrong beacuse when i give minSdk to 31 my emulator shows minSdk is 25 and did not show any other error please guide about this

i use agora 3.1.3 its working fine but 4.2.0 is not working and giving errror flutter not initialize and libflutter.so file not found
please help

Please try agora_rtc_engine: 5.1.0.


The page doesn't explain how to remove command menus

If you simply remove it from the manifest, then they are continued to be rendered in the app. How can they be removed?

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

ID: 3a982542-ae03-2ada-cf71-4d586272e0c3
Version Independent ID: 9e1fd82b-79e4-1b8d-5367-a8de3d04b3aa
Content: Create a command menu for your bot - Teams
Content Source: msteams-platform/bots/how-to/create-a-bot-commands-menu.md
Product: msteams
GitHub Login: @clearab
Microsoft Alias: anclear

Page does also not describe how to actually handle the commands in code. The paragraph only describes how to strip mentions.

@laujan , Could you please help to update the document?

Hi - If you remove the command from your manifest you'll need to redeploy your app for the changes to take effect (any changes to the manifest require this).
As far as handling the commands in code, they are sent to your bot as a regular message so you'll need to handle them as you would any other message from your users. They are purely a UI treatment that inserts pre-configured text into the text box. The user must then send that text as they would any other message.

I have removed them from my app and redeployed. However, Teams still suggests them. After a few weeks it finally started suggesting the correct ones instead, but then reverted back (all without any re-deploys inbetween). Now, 10 months later, it is still showing the original.

Thanks for following up - the team has been able to recreate this behavior with bot menus, and is investigating. For updates about this, please follow the Issue here: https://github.com/microsoft/botframework-sdk/issues/6101


circleci: Update xcode version

circleci started notifying that the image that we use will be dropped in
September 2021, better to upgrade now.
https://circleci.com/docs/2.0/xcode-policy/
https://circleci.com/docs/2.0/testing-ios/#supported-xcode-versions

ahh, Circle CI build is not getting triggered

ahh, Circle CI build is not getting triggered

It was triggered here https://app.circleci.com/pipelines/github/cfergeau/crc/236/workflows/b8baa15c-4761-4541-a8a3-95ea17a5dd9f/jobs/708 (CI on the cfergeau:xcode branch the PR is based on)


Render Controllers - More comments and explanation

This page could use more comments in the examples or explanations outside of the examples
Made a PR with examples: https://github.com/MicrosoftDocs/minecraft-creator/pull/137

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

ID: fc18d47a-e328-c81a-b3e6-3f8400b0d060
Version Independent ID: 9587d402-df15-2a0e-a690-cb0bb6ebe3f1
Content: Animation Documentation - Render Controllers
Content Source: creator/Reference/Content/AnimationsReference/Examples/AnimationRenderController.md
Product: gaming
GitHub Login: @v-josjones
Microsoft Alias: v-josjones

Merged the PR into our main branch. Will close issue once hotfix is released.


Add /api/v1/format_query API endpoint for formatting queries

This uses the formatting functionality introduced in
https://github.com/prometheus/prometheus/pull/10544.
I've chosen "query" instead of "expr" in both the endpoint and parameter
names to stay consistent with the existing API endpoints. Otherwise, I
would have preferred to use the term "expr".
Signed-off-by: Julius Volz<EMAIL_ADDRESS>

They are removed because the parser doesn't even remember comments or tell you that it encountered any. It just throws them away currently. So there'd also not be a way to mark such an expression invalid, but I also would not have expected that as a user.
I added a comment that the comments are being removed.

It could be cool to have the prettifier in the graph page too

We tried to preserve comments in the first attempt, by totally bypassing the parser. But that turned out to be a way too complex and fragile of a code. So this is a step 1, a simpler implementation with the trade-off of comments to get the ground moving.

It could be cool to have the prettifier in the graph page too

We are doing it, right? :eyes:

Actually, will merge now so I can build on top of it better.


[WIP] Add templates

This adds HMC partition templates to the inventory. So far it only records memory and operating system information.
Event-based targeted refresh not functional at this time.

Event-based targeted refresh works.

VM-to-template capture to be completed as a separate PR.

VM-to-template capture to be completed as a separate PR.


quiche: implement QUIC stats API

source/extensions/quic_listeners/quiche/platform/quic_server_stats_impl.h has no-op implementation for QUIC stats interface, i.e. QUIC_SERVER_HISTOGRAM_ENUM_IMPL. We need to implement those with Envoy stats.

/assign @RenjieTang

I did some research and found the following histograms currently logged in Quiche: QuicConnection::FlushPackets() status, rate of stream frame coalescing, QPACK compression ratio, connection close error codes, tls latency, and number of packets per write.
Most of the histograms above are about internal quiche implementation. The only thing Envoy users might care is connection close error.
So instead of implementing the generic QUIC_HISTOGRAM_BOO macros, we can simply add connection close histograms inside Envoy's quiche subclasses.

As of https://github.com/envoyproxy/envoy/pull/17496, Envoy supports QUIC connection and stream error stats for both upstream and downstream connections.
A pipeline for adding sparse QUIC counters has been built, and additional stats can be added when necessary with relatively easy steps.


loading svelte packages from node_modules

Not every Svelte packages are providing CommonJSmodules needed by Jest.
Examples:
svelte-select: provides es, mjs modules and the svelte component
svelte-calendar: provides only the svelte component.
Is there something I can do to tell jest that it has to look for the svelte component when it comes from node_modules?
import Select from 'svelte-select';
import * as CommonJSSelect from 'svelte-select';
const SelectComponent = Select || CommonJSSelect; // issues with jest, needs CommonJS

Hey @darkship you can use jest-svelte-resolver to make Jest resolve the .svelte files.

I tried it. It breaks the handling of my own svelte components with svelte-jester. And I don't find the related github page of this package

Hi @darkship ,
You can use "transformIgnorePatterns" configuration of jest. By default the node_modules folder is ignored. So by setting it as follows
  "transformIgnorePatterns": [
    "node_modules/(?!(svelte-select|svelte-calendar)/)"
  ],

the folders "svelte-select" and "svelte-calendar" in the node_modules, will be transformed based on the transform config.

Hi @darkship ,
You can use "transformIgnorePatterns" configuration of jest. By default the node_modules folder is ignored. So by setting it as follows
  "transformIgnorePatterns": [
    "node_modules/(?!(svelte-select|svelte-calendar)/)"
  ],

the folders "svelte-select" and "svelte-calendar" in the node_modules, will be transformed based on the transform config.

This should be fixed with Jest 27+ and Sveltekit requiring ESM.


Lightspeed multitask inference e2e test cases

Note: This PR is built on the top of #1067

EE test are failing on macos which is a known issue.


Make Kubernetes specific env variables available when joining a cluster via SSH

This enables K8s specific env vars to be available in an SSH session. It does this by:

Creating a .k8s_env file and symlinking it to /etc/environment during setup.
Running kubectl exec {pod_name} --  env as part of SSH Proxy command and saving env vars to the .k8s_env file
Creating a separate bash script for ProxyCommand per cluster and handling cleanup during teardown

Tested (run the relevant ones):

[x] Code formatting: bash format.sh
[ ] Any manual or new tests for this PR (please specify below)
[ ] All smoke tests: pytest tests/test_smoke.py
[ ] Relevant individual smoke tests: pytest tests/test_smoke.py::test_fill_in_the_name
[ ] Backward compatibility tests: bash tests/backward_comaptibility_tests.sh

The issue exists for both ssh approaches. Let me see a way to use it in the nodeport approach as well.

@landscapepainter Added support for nodeport in https://github.com/landscapepainter/skypilot/pull/1/commits/da940ff0182907ca3673951731b7d280f94c7f04

Thanks @hemildesai! After you have merged the latest changes from upstream (which includes GPU support), it would be great to test and see if this PR resolves https://github.com/skypilot-org/skypilot/issues/2453.


Add files via upload

Can you accept the pull request?

Here are few things to do befor merge

[] Flake8 linting
[] Add requirements.txt and README
[] Change folder name to cputemp_checker


Error: Out of range

Some addresses with onchain metadata cannot be displayed. Examples:
EQCMvH6kA9d4bOW3E0mbey867Llxmp3bAiUyuMPkOYm89Z1u
EQDvu5CuKN43FiFJoRWDxRQx-E2oq2KwrKvFmID5C7BTc3CS
EQCMvH6kA9d4bOW3E0mbey867Llxmp3bAiUyuMPkOYm89Z1u

@ingria is this on mainnet?

Yes
https://minter.ton.org/jetton/EQCMvH6kA9d4bOW3E0mbey867Llxmp3bAiUyuMPkOYm89Z1u


Keyed parquet files

Use a cached keyed parquet file instead of parsing the result if available

See if this can help with the speed: https://joblib.readthedocs.io/en/latest/memory.html#memory


Improve russian translation

Change response translation to "ответ"

Coverage remained the same at 87.968% when pulling 9abdc395f67a2ac4b2b86c1d65a69eea2e05abea on Nobotym:patch-1 into 7ce62a8a3ddfd15de71c7aa40e322337bb26c20e on Swagger2Markup:master.

Coverage remained the same at 87.968% when pulling 6e8d9f6c09e91fccf1fa627419d26b4b9e812f1b on Nobotym:patch-1 into 7ce62a8a3ddfd15de71c7aa40e322337bb26c20e on Swagger2Markup:master.

Hi, thx.
What did you change?


Bumped main branch to version 2.2.1.

Description
Bumped main branch to version 2.2.1. Closing https://github.com/opensearch-project/alerting-dashboards-plugin/pull/329 in favor of this PR.
Issues Resolved
[List any issues this PR will resolve]
Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #330 (c229b53) into main (9d3813b) will not change coverage.
The diff coverage is n/a.

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

@@           Coverage Diff           @@
##             main     #330   +/-   ##
=======================================
  Coverage   52.73%   52.73%
=======================================
  Files         209      209
  Lines        5450     5450
  Branches      763      763
=======================================
  Hits         2874     2874
  Misses       2574     2574
  Partials        2        2

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Error in Generating Release Notes on RC Release PR when created from fork

Bug information
Error thrown in 'Generate release note from template' workflow on RC Release PR (for release v0.28.0-rc1) when created from fork.

Steps to reproduce (required)
When creating a RC release PR with updates to versions.yaml for v0.28.0-rc1 release, a PR was created using a forked repository instead of a branch.
This issue can be reproduced by creating a PR with updates to versions.yaml from a forked repository.
Observed behavior (required)
Error as displayed in image above indicates that a token is not available.
sample PR: https://github.com/radius-project/radius/pull/6919
Desired behavior (required)
release notes to be generated without errors
Workaround (optional)
Create PR from a branch for v0.28.0 release.
AB#10704

Since the official guidance is to create the release directly from radius main, this work is not required. To get this to work, we would have to do setup similar to Approve Functional Tests to get the comment on the PR or we can use action summary instead of comment on the PR. I think we can un-mark this as important and pick it up as a work item later once we decide what we want to do.


Adding Sonatype logo to "who uses Infer" section of Infer website.

Sonatype uses Infer. This PR adds Sonatype's logo to the infer website.

Thank you! :fireworks:


could not able to clone in local device

When cloning, permission denied message is popping up. please see the screenshot for more info.

Hi,
I could not reproduce the issue and am able to clone the repository. Do you have a SSH key associated with your GitHub account, as you are trying to use SSH for cloning? Please refer to the following link for more information about authorization:
https://stackoverflow.com/questions/12940626/github-error-message-permission-denied-publickey


Can't alter mapping to open file from select_default to tab_drop or select_tab.

I'd like the file to be opened with a tab drop because thats how I organize my files. This doesn't seem to support that event when trying to override default mappings in telescope config. Also show_scores is not working for me when set to true.

I'm not familiar with tab drop.  Could you explain it or provide a link?
I'll look at show_scores, but I've been tempted to remove it for some time now.  There's no good way of providing enough relevant scoring info for each entry anymore.  There's not enough space.  It's cryptic and apparently easy to break

similarly, I'd love to be able to set the mappings for file opening to use vnew, etc, for <cr>; but the normal way of settings mappings for this extension doesn't seem to be working.

Likewise I'd also like to use select_tab_drop.
@danielfalk :tab drop will open a file in either a new tab, or will use the existing window in a tab if the file is already open in that window.
That means that for those of us who use tabs to organise our buffers then we can ensure that the buffer is only open in a specific tab.
When I use the following config for telescope:
        defaults = {
          mappings = {
            i = {
              ["<CR>"] = "select_tab_drop",
              ["<C-b>"] = "select_default",
              ["<C-_>"] = "select_horizontal",
              ["<C-Bslash>"] = "select_vertical",
          },
        },

I get this error:
Error executing Lua callback: .../nvim/lazy/telescope.nvim/lua/telescope/actions/init.lua:74: Key does not exist for 'telescope.actions': select_tab_drop
stack traceback:
	[C]: in function 'error'
	.../nvim/lazy/telescope.nvim/lua/telescope/actions/init.lua:74: in function '__index'
	...hare/nvim/lazy/telescope.nvim/lua/telescope/mappings.lua:233: in function 'telescope_map'
	...hare/nvim/lazy/telescope.nvim/lua/telescope/mappings.lua:308: in function 'apply_keymap'
	...share/nvim/lazy/telescope.nvim/lua/telescope/pickers.lua:569: in function 'find'
	...pen.nvim/lua/telescope/_extensions/smart_open/picker.lua:95: in function 'start'
	...smart-open.nvim/lua/telescope/_extensions/smart_open.lua:23: in function <...smart-open.nvim/lua/telescope/_extensions/smart_open.lua:10>
	...share/nvim/lazy/telescope.nvim/lua/telescope/command.lua:193: in function 'run_command'
	...share/nvim/lazy/telescope.nvim/lua/telescope/command.lua:259: in function 'load_command'
	...ocal/share/nvim/lazy/telescope.nvim/plugin/telescope.lua:108: in function <...ocal/share/nvim/lazy/telescope.nvim/plugin/telescope.lua:107>

Here's an example of where that feature usage is mentioned: https://github.com/nvim-telescope/telescope.nvim/issues/2188#issuecomment-1516861881
This is the implementing PR: https://github.com/nvim-telescope/telescope.nvim/pull/2143
And a PR supporting it as a jump_type: https://github.com/nvim-telescope/telescope.nvim/pull/2751

Thanks for this @lougreenwood  That really helps.
I think I've just pushed up some changes in the 0.2.x branch that should allow the mappings to be configured, but I'm not sure about the error message you pasted because that doesn't look like a mapping issue.  I could only see getting that error if there was no select_tab_drop in your version of telescope.nvim but maybe I'm missing something.

Update: I saw the issue with select_tab_drop as well, until I updated telescope to the latest master branch.  I was on 0.1.x which didn't seem to have the implementing PR that was mentioned.

Sorry, you can close this out if you want I've stopped organizing by tabs now that I have this plugin: https://github.com/romgrk/barbar.nvim


Merge 5.4.x -> master

CLA signed by all contributors.

The travis failure is occurring because of a change that landed in 5.3.x (which doesn't check for ruby warnings) and now the mergeup fails. I submitted https://tickets.puppetlabs.com/browse/PUP-8535 so that we catch these issues earlier. Also I pushed https://github.com/puppetlabs/puppet/commit/67428d2d7cf52b13d042943109de33f96523ec96 which will resolve the failure that is occurring in this PR. You may want to resubmit this PR (rebased off of 5.4.x) after the change makes it there.

I took care of this in 7bb619e42f, closing.


[CfW] Text fields are broken in new beta

Describe the bug
After https://github.com/JetBrains/compose-multiplatform-core/pull/1259 text fields are broken on desktop browsers

[ ] singleLine text fields don't react on input
[ ] Cursor always jumps to the end of line when trying to type something in the middle
[ ] Selection doesn't work on the right side from cursor (enter some text, move cursor to the beginning, try select something - doesn't work because of invisible textarea that is placed after cursor).

All issues are gone if i remove the invisible textarea from the dom tree.
Affected platforms
Web JS. Tested in Chrome and Edge on Windows. Didn't check wasm
Versions

Kotlin version*: 1.9.23
Compose Multiplatform version*: 1.6.10-beta01

Same story on wasm

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


Turn on tracing, add .dockerignore

Discussed offline. But to recap: no since this change is only for local dev use. miner.toml is only used by devnet for development purposes, and not against ropsten, etc.


--log-base /dev/null doesn't seem to work

Ubuntu 20.04
Noetic/Foxy
colcon-core 0.7.1
colcon-output 0.2.12

According to the documentation found here, you should be able to do something like this:
colcon --log-base /dev/null build

However when I try that I get the following error no matter what package I try to compile:
ERROR:colcon.colcon_core.event_reactor:Exception in event handler extension 'log': unsupported operand type(s) for /: 'NoneType' and 'str'
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/colcon_core/event_reactor.py", line 78, in _notify_observers
    retval = observer(event)
  File "/usr/lib/python3/dist-packages/colcon_output/event_handler/log.py", line 80, in __call__
    base_path = get_log_directory(job)
  File "/usr/lib/python3/dist-packages/colcon_output/event_handler/log.py", line 166, in get_log_directory
    return get_log_path() / job.identifier
TypeError: unsupported operand type(s) for /: 'NoneType' and 'str'

I found this issue that reports a similar but different issue with the same test case (--log-base /dev/null):
https://github.com/colcon/colcon-core/issues/263
Does anyone know of a work-around? I tried COLCON_LOG_PATH environment variable but it results in the same error.

This is solved by colcon/colcon-output#39, which hasn't been released yet.


Android 11 support

Just to let you know, I started development with the intent to get Android 11 supported. But first, I will switch to Debian, ref #4.

Should be supported. I am building GrapheneOS with it, ref https://github.com/hashbang/os/issues/47. I have not build vanilla AOSP with it. That issue can be closed when anyone firms that this works also.


Volume control

Great plugin, works like a charm changing source and turning the TV on/off.
However, i'm not able to get the volume control to show. I must be missing config for this but i'm not able to figure out what is missing.

Hey @Dippely
I think this might be a misunderstanding. The volume controls only work within the "tv remote" that you can add to your control center.
When you pull down the cc and open the remote app, you will be able to adjust the tv volume by using your hardware volume buttons on your iPhone.
If this is not a misunderstanding and this functionality indeed doesn't work, please report back and I'll take a closer look :)


Tweak features for regex-syntax

This commit tweaks the features enabled for the regex-syntax crate
from the regex crate itself. This isn't intended to actually have any
functional change, but should help feature unification for Cargo in some
projects.
One project I work on exhibits an issue where executing cargo build
followed by cargo test will rebuild regex-syntax and all of its
transitive dependencies. The cause for this issue is that the tests are
using the proptest crate. The proptest crate depends on
regex-syntax with normal features (e.g. the defaults). All other
crates depend on regex with normal default features too.
The problem happens where when only the regex crate depends on
regex-syntax then the default and unicode features of
regex-syntax are disabled. This is because the regex crate disables
default features and regex's unicode feature delegates to all the
individual features of regex-syntax. When the regex-syntax crate is
depended on directly by proptest it then enables the default and
unicode features of regex-syntax.
Functionally these two builds of regex-syntax are exactly the same
since default is simply a proxy for unicode and unicode is simply
an umbrella including other features.
This PR updates the features enabled on regex-syntax by the regex
crate in two ways:

The default feature for regex enables regex-syntax/default.
The unicode feature for regex enables the regex-syntax/unicode
feature.

This makes is so that if another crate in your crate graph depends on
regex-syntax then it'll have, by default, the same set of features
enabled than if you also depend on regex.

@alexcrichton Wow, thank you for the detailed explanation and tracking this down! Definitely agree with this change, and this is probably how I should have set it up in the first place. :-)

This PR is on crates.io in regex 1.3.7.

Thanks so much! And no worries, it took me awhile to track this down b/c I've never had to do this to any other crates before either. A good tip for myself for the future though :)


look into password hashing and implement it via typeorm hooks

We'll need to look into best solution for password hashing and salting and implement it via typeorm hooks.
https://github.com/typeorm/typeorm/blob/master/docs/listeners-and-subscribers.md
I'm currently thinking salted bcrypt but doing a little bit of reading on the subject would be ideal.

implemented with argon2, winner of phc, recommended by owasp
https://password-hashing.net/
https://github.com/OWASP/CheatSheetSeries/blob/master/cheatsheets/Password_Storage_Cheat_Sheet.md#leverage-an-adaptive-one-way-function
also adds min and max length limits and a very simple config setup


Minor: clarify comment about empty dependencies

Which issue does this PR close?
Follow on to https://github.com/apache/datafusion/pull/12759
Rationale for this change
@comphead and myself wondered why a particular code path existed, and @berkaysynnada helped find the answer: https://github.com/apache/datafusion/pull/12759#discussion_r1789128349
Let's encode that learning into comments so we don't have to re-discover it the next time we read the code.
What changes are included in this PR?
Add comments
Are these changes tested?
N/A
Are there any user-facing changes?
No, internal comments only

I think CI / clippy will be fixed by https://github.com/apache/datafusion/pull/12724

Thanks for the review @berkaysynnada


UE4.18

I was just wondering if UE4-OSC works with UE4.18 yet and if there will be a version released soon that does.

I tried quickly, and it seems to work properly on 4.18.
There is a new "deprecated" compilation warning, that has no impact yet.


Legal(?) and size issues with bundled test clips

Ping @ethanhugg
The recently added support for b-frames also came with a few test samples, which turn out to be clips from actual movie trailers. Is this ok copyright wise for this project?
And even if they'd be ok license wise, these clips are way way too big for the testsuite. When running the whole testsuite in valgrind (in order to catch use of uninitialized data, reads/writes out of bounds etc, including in assembly which address sanitizer doesn't catch), these 4 test clips more than doubled the runtime of the testsuite, from around 30 minutes before, to 70 minutes now, with these 4 clips taking over 40 minutes to decode when run in valgrind.
Either the clips must be reduced, or I have to reconsider running regular testing of this project in valgrind.

I think we would prefer to use test clips which were well accepted test data that was  commonly used in to develop video codecs. That type of data has copyright that clearly allows us to use it and is also well known what it should look like to video experts so it tends to be easier to catch mistakes in.     How long are these clips right now? I suspect that there is no real gain to longer clips and to be able to speed up testing, we should probably use clips that are long enough to test the system but as short as possible.

The current tests for high profile are 200, 300, 300 and 580 frames long, but they are in 720p and 1080p, and weigh in at about 40 MB - imo total overkill for this test case. (And then the tests don't even cover CAVLC-encoded B-slices, which the pull request didn't contain support for.)

@xiaotianshi2 we will need to remove the test-clips for B-frames if the copy-right problem is not clear. Thanks.

@sijchen If that's the issue, it had better to remove the trailer test cases.

@xiaotiansf
I have removed two test samples on the PR#3010
can you help to check the other two files?

@GuangweiWang
I am sure these two files have no licence issue.
res/HighProfile_B_Frame_1920x1080p_2397fps.h264
res/HighProfile_B_Frame_1920x1080p_30fps.h264

@xiaotiansf License issues aside, can you produce samples with similar code coverage but shorter clips and much lower resolution? It doesn't need to be HD content just to test decoding of b-frames.

@mstorsjo
Sure and I'll find and add some suitable samples.


Want to contribute but build takes time

I am new to TensorFlow's contribution community. I want to add some features and write test some scripts for it, but as it is taking so much time to build. I want to import TensorFlow from the source without re-building every time.
Please let me know if it's possible or if there is another way of doing that.

After the first compile the others should be cached and don't take that much of time. Unless you sync to master again, an action which would likely invalidate the cache again.
Unfortunately, we don't have too much engineering time dedicated to streamlining the build. There is some effort in this line but we can benefit from open source community contributions too.

@ratansingh98,
If you want to install TensorFlow from pre-built packages, please check this guide.
Or if you have built TensorFlow from source, the whl file is stored in the /tmp/tensorflow_pkg/ directory. You can use this whl file to install TensorFlow every time instead of re-building from source.
Please check this installation guide for more information. Thanks!

After the first compile the others should be cached and don't take that much of time. Unless you sync to master again, an action which would likely invalidate the cache again.
Unfortunately, we don't have too much engineering time dedicated to streamlining the build. There is some effort in this line but we can benefit from open source community contributions too.

Thanks for the info. As for now, the cache can be very useful for me. If possible, I will look into streamlining the build.

@ratansingh98,
If you want to install TensorFlow from pre-built packages, please check this guide.
Or if you have built TensorFlow from source, the whl file is stored in the /tmp/tensorflow_pkg/ directory. You can use this whl file to install TensorFlow every time instead of re-building from source.
Please check this installation guide for more information. Thanks!

Thanks @amahendrakar , but that's not exactly was my question. I wanted to reduce that build time or a handy way to import TensorFlow. In my case, I wanted to generate a new whl file every time I build TensorFlow from my modified source.
As @mihaimaruseac told, the building is not streamlined enough. I have to rely on the cache.
Thanks for your guidance though.

@mihaimaruseac Hey, i was actually having the same doubt i built tf from source the day before yesterday and today after pulling the new changes from tf repo i ran bazel build again, it is still taking a lot of time. How much time do you think is reasonable after the initial build? And how are other contributors updating the build everytime new commits are merged? Thanks

It depends on your operating system and hardware. You should watch memory consumption during build to make sure you are not using swap, since that would definitely slow down builds. There are bazel flags to limit how much RAM should be used by the compilation process and how many processes to run in parallel. These should help with contention issues.
Then, you should make sure you use the bazel cache between builds so that you don't always rebuild from scratch.
Finally, you don't need to always build everything. The way I do it is first I build a pip package from scratch, identify the issue, identify a smaller test showcasing the issue or writing one if it does not exist. Then, as I work on fixing the issue, I only run that test and only when done do I build the entire package again

@mihaimaruseac Thanks for the reply.

Then, you should make sure you use the bazel cache between builds so that you don't always rebuild from scratch.

I didn't quite understand what you meant by using the bazel cache as I'm fairly new to bazel and open source, this being my first project.

The way I do it is first I build a pip package from scratch, identify the issue, identify a smaller test showcasing the issue or writing one if it does not exist. Then, as I work on fixing the issue, I only run that test and only when done do I build the entire package again

It would be great if you could provide a little insight.

https://docs.bazel.build/versions/master/remote-caching.html

You can follow our effort to optimize and continuously monitoring the contributor experience with our official docker developer image at https://github.com/tensorflow/tensorflow/pull/48421 /cc @theadactyl


Data import supports partition atomic coverage

(you don't have to strictly follow this form)
Data import supports partition atomic coverage
We have tasks that need to be refreshed every day, including full table refresh and partition refresh. We hope that data partition refresh will not affect business queries, so we hope to support full table or partition coverage like hive and druid, or support table and partition atomic replacement 'swap' like doris

hi @bright-zy, could you please elaborate more what feature you want?

hi @bright-zy, could you please elaborate more what feature you want?

hi @GallifreyY , I want atomic operations to implement table or partition data replacement
For example, Hive uses OVERWRITE to replace table partitions
insert overwrite test.table1 partition (pt='20240328')
select
column1 ,
column2 ,
column3
FROM
test.table2
where pt = '20240328'
like StarRocks,
ALTER TABLE table1 SWAP WITH temp_table1;
ALTER TABLE tbl1 REPLACE PARTITION (p1) WITH TEMPORARY PARTITION (tp1);

hi @bright-zy , ByConity has a new feature of INSERT OVERWRITE to address your issue. We are updating the document of such new feature and will send it to you when ready.

hi @smmsmm1988 ,That would be great. I'm looking forward to it.

hi @smmsmm1988 ,That would be great. I'm looking forward to it.

https://byconity.github.io/zh-cn/docs/sql-syntax/sql-statements?open_in_browser=true#insert-overwrite

hi @smmsmm1988  Version 0.3.2 does not support

hi @kevinthfang , could you help check which ByConity version contains the feature of INSERT OVERWRITE?

hi @smmsmm1988 Version 0.3.2 does not support
ClickHouse client version <IP_ADDRESS>. Connected to ClickHouse server version 21.8.7 revision 54450.

hi @bright-zy , version 0.3.2 does not contain this feature. You can try the latest version 0.4.0.


AzureFunctionApp fails when attempting to change FUNCTIONS_EXTENSION_VERSION and linuxFxVersion

Required Information
Type: Bug
Task Name: AzureFunctionApp
Environment
Server: Azure Pipelines
Agent: Hosted
Issue Description
When attempting to change both FUNCTIONS_EXTENSION_VERSION and linuxFxVersion on release, a failure appears to be caused due to the request order.
In a failure the process attempts to perform Syncing triggers for function app and gets the following error:
Syncing triggers for function app
##[error]Error: Failed to sync triggers for function app '____'. Error: BadRequest - Encountered an error (ServiceUnavailable) from host runtime. (CODE: 400)

When FUNCTIONS_EXTENSION_VERSION is removed from appSettings the process succeeds, leaving the app with the incorrect extension version:
Syncing triggers for function app
Sync triggers for function app completed successfully
Trying to update App Service Configuration settings. Data: {"linuxFxVersion":"PYTHON|3.8"}
Updated App Service Configuration settings.

Task logs
Partial pipeline to reproduce...

Assumes clean Function App exists in consumption plan
Example initial state

FUNCTIONS_WORKER_RUNTIME: python
FUNCTIONS_EXTENSION_VERSION: ~3
linuxFxVersion: PYTHON|3.6

- task: AzureFunctionApp@1
  inputs:
    azureSubscription: __serviceConnection__
    appType: "functionAppLinux"
    appName: "testfunction"
    package: "testfn.zip"
    runtimeStack: "PYTHON|3.8"
    configurationStrings: "-linuxFxVersion PYTHON|3.8"
    appSettings: >-
      -FUNCTIONS_WORKER_RUNTIME: python
      -FUNCTIONS_EXTENSION_VERSION: ~4

Output
Starting: AzureFunctionApp
==============================================================================
Task         : Azure Functions
Description  : Update a function app with .NET, Python, JavaScript, PowerShell, Java based web applications
Version      : 1.206.0
Author       : Microsoft Corporation
Help         : https://aka.ms/azurefunctiontroubleshooting
==============================================================================
Got service connection details for Azure App Service:'___'
Trying to update App Service Application settings. Data: {"FUNCTIONS_EXTENSION_VERSION":"~4","FUNCTIONS_WORKER_RUNTIME":"python","WEBSITE_RUN_FROM_PACKAGE":"[https://____.blob.core.windows.net/azure-pipelines-deploy/package_XXX.zip?***"}]
Updated App Service Application settings.
Updated WEBSITE_RUN_FROM_PACKAGE Application setting to https://____.blob.core.windows.net/azure-pipelines-deploy/package_XXX.zip?***
Syncing triggers for function app
##[error]Error: Failed to sync triggers for function app '____'. Error: BadRequest - Encountered an error (ServiceUnavailable) from host runtime. (CODE: 400)
Successfully added release annotation to the Application Insight : XXX
App Service Application URL: http://____.azurewebsites.net/
Finishing: AzureFunctionApp

Hello, @jenko1080 please let me know if this is still happening and let me the App Name and Timeframe?

Hi @FinVamp1, attempted to set up a quick insecure (public) test and it appears that it can't happen any more due to the following error:
https://jenko1080.visualstudio.com/AzureFunctionsTests/_build/results?buildId=1&view=logs&j=845195f5-6388-51b2-d3f0-92c8cacc2296&t=4d7d333d-492e-5ebf-ed4f-b7e05246619f&l=11
Code:
https://github.com/jenko1080/FunctionAppTest
Noting that setting FUNCTIONS_WORKER_RUNTIME isn't allowed, is there a preferred method to pin a function app to a minor version? (eg. One of my other apps isn't behaving on 3.11)

Hi, resolving this issue. The app settings for Linux don't apply and for the pinning please refer to https://learn.microsoft.com/en-us/azure/azure-functions/set-runtime-version?tabs=portal#manual-version-updates-on-linux


To be reviewed.

Useful hint by @mfranzon:
Relationships list_jobs_input and list_jobs_output are likely the problem here.
Question: are they actually needed? The original goal was to make sure that deleting a dataset sets e.g. input_dataset_id=None for the appropriate jobs, but maybe this is already happening thanks to the foreign keys.

Note that the same change would be needed for Workflow.job_list

On a specific example, we went from ~12 second to ~2 seconds as of #1130. This is good, but there is still room for improvement.
Debugging strategy is the usual one:

Set DB_ECHO=1, and have a quick look at the generated SQL statements
If 1 is not enough to get an idea of where the issue could be, then let's go through #1128

The latest re-opening was then deferred to

#1138
#1140


Apk not designed for tablets - possible "Support Large" and "Support Xlarge" export option problem.

Operating system or device - Godot version:
Linux Xubuntu 14.04 64-bit, Godot 2.1-alpha and Godot 1.1 - both custom compile.
Issue description (what happened, and what was expected):
After properly uploading apk to Google Play Developer Console, Google gives me following notification

My export settings about screen sizes look like this

Steps to reproduce:
To see the notification in Google Plays Development Console you need to choose one of your apps from your app's list and go to Statistics.

Then in the middle of stats page, which shows "Android Version" stats by default,
you need to change it to "Tablets", and in the lover part of the page you should be able to  see something like this

My app published using 2.1-stable (custom build) doesn't have this issue.

It seems as https://github.com/godotengine/godot/issues/4144 that has been fixed in 2.1 stable.