/snap/frame-it/18/frame-it: line 21: ubuntu-frame_beta: command not found

Followed the instructions on https://mir-server.io/docs/make-a-secure-ubuntu-web-kiosk and https://mir-server.io/docs/how-to-use-remote-assistance-with-ubuntu-frame in order to convert a default Ubuntu Server Minimal installation (Ubuntu 22.04.4 LTS) with the desktop installed (using sudo apt-get install --no-install-recommends ubuntu-desktop) into a kiosk, dislaying a webpage.
I've used the following commands to do so:
sudo snap install ubuntu-frame
sudo snap install wpe-webkit-mir-kiosk
sudo snap set ubuntu-frame daemon=true
sudo snap set wpe-webkit-mir-kiosk daemon=true
sudo snap connect wpe-webkit-mir-kiosk:wayland
sudo snap connect ubuntu-frame:login-session-control
sudo snap set wpe-webkit-mir-kiosk url=https://ubuntu.com
sudo snap start wpe-webkit-mir-kiosk

So far, this works perfectly, but I'm trying to install and configure VNC onto it in order to remotely login onto the display in order to view what the user will see, so used the commands below:
sudo snap install ubuntu-frame-vnc
sudo snap set ubuntu-frame-vnc daemon=true
/snap/ubuntu-frame-vnc/current/bin/setup.sh

From there, i tried to install and run frame-it in order to allow/enable remote access, by using these commands
sudo snap install --classic frame-it
sudo snap set frame-it shell-app=wpe-webkit-mir-kiosk.cog

When calling frame-it wpe-webkit-mir-kiosk, I get the following error "/snap/frame-it/18/frame-it: line 21: ubuntu-frame_beta: command not found".
Continued by executing frame-it.check, which gives me the following response:
~$ frame-it.check

Checking: ubuntu-frame_beta installation (needed for all commands)
 WARNING: ubuntu-frame_beta NOT installed. Please run the following:
  sudo snap install ubuntu-frame_beta
Checking: ubuntu-frame_beta has login-session-control (needed to run a login shell)
error: snap "ubuntu-frame_beta" not found
 WARNING: ubuntu-frame_beta:login-session-control NOT connected. Please run the following:
  sudo snap connect ubuntu-frame_beta:login-session-control
Checking: shell-app option (needed for frame-it.shell and to run a login shell)
 . OK . : shell-app is set (to 'wpe-webkit-mir-kiosk.cog') and can be found
Checking: osk option
 . OK . : "osk" is unset
Checking: vnc-viewer option (needed for frame-it.vnc)
 . OK . : vnc-viewer is set (to 'gvncviewer') and can be found

Executing sudo snap connect ubuntu-frame_beta:login-session-control
When I call frame-it.shell, the same error (/snap/frame-it/18/frame-it: line 21: ubuntu-frame_beta: command not found) appears. The application continues, but I'm unable to connect using RealVNC Viewer. How can is solve this issue?

Got a little further with a fresh/clean installation and the steps described above. After installing gvncviewer with sudo apt-get install gvncviewer, executing frame-it.check, which gives me the following response:
~$ frame-it.check

Checking: Ubuntu Frame installation (needed for all commands)
 . OK . : Ubuntu Frame is installed
Checking: Ubuntu Frame has login-session-control (needed to run a login shell)
 . OK . : ubuntu-frame:login-session-control is connected
Checking: shell-app option (needed for frame-it.shell and to run a login shell)
 . OK . : shell-app is set (to 'wpe-webkit-mir-kiosk.cog') and can be found
Checking: osk option
 . OK . : "osk" is unset
Checking: vnc-viewer option (needed for frame-it.vnc)
 . OK . : vnc-viewer is set (to 'gvncviewer') and can be found

When I run frame-it.shell, I get the response and errors below:
~$ frame-it.shell

+ [ /snap/ubuntu-frame/8587/bin/run-frame = --help ]
+ mkdir -p /root/snap/ubuntu-frame/8587/.config/
+ grep -vE (^vt=|^console-provider=vt) /var/snap/ubuntu-frame/8587/frame.config
+ rm -f /root/snap/ubuntu-frame/8587/.config/frame.display
+ cp /var/snap/ubuntu-frame/8587/frame.display /root/snap/ubuntu-frame/8587/.config/
+ exec /snap/ubuntu-frame/8587/bin/run-frame /snap/ubuntu-frame/8587/bin/graphics-core22-wrapper /snap/ubuntu-frame/8587/usr/local/bin/frame
+ [ /snap/ubuntu-frame/8587/bin/graphics-core22-wrapper = --help ]
+ dirname /run/user/0/snap.ubuntu-frame
+ XDG_RUNTIME_DIR=/run/user/0
+ export XDG_RUNTIME_DIR
+ mkdir -p /run/user/0 -m 700
+ [ -n wayland-0 ]
+ [ -e /run/user/0/wayland-0 ]
+ unset WAYLAND_DISPLAY
+ exec /snap/ubuntu-frame/8587/bin/graphics-core22-wrapper /snap/ubuntu-frame/8587/usr/local/bin/frame
[2024-03-19 09:19:41.526216] < - debug - > miral: Loaded display configuration file: /root/snap/ubuntu-frame/8587/.config/frame.display
[2024-03-19 09:19:41.556321] <information> mirserver: Starting
[2024-03-19 09:19:41.577238] < - debug - > mirserver: Not using logind for session management: Seat has no active session
[2024-03-19 09:19:41.578196] < - debug - > mirserver: Using Linux VT subsystem for session management
[2024-03-19 09:19:41.578690] <information> mircommon: Loading modules from: /snap/ubuntu-frame/8587/usr/lib/x86_64-linux-gnu/mir/server-platform
[2024-03-19 09:19:41.578882] <information> mircommon: Loading module: /snap/ubuntu-frame/8587/usr/lib/x86_64-linux-gnu/mir/server-platform/graphics-eglstream-kms.so.21
[2024-03-19 09:19:41.578974] <information> mircommon: Loading module: /snap/ubuntu-frame/8587/usr/lib/x86_64-linux-gnu/mir/server-platform/graphics-gbm-kms.so.21
[2024-03-19 09:19:41.579019] <information> mircommon: Loading module: /snap/ubuntu-frame/8587/usr/lib/x86_64-linux-gnu/mir/server-platform/renderer-egl-generic.so.21
[2024-03-19 09:19:41.579067] <information> mircommon: Loading module: /snap/ubuntu-frame/8587/usr/lib/x86_64-linux-gnu/mir/server-platform/server-x11.so.21
[2024-03-19 09:19:41.579108] <information> mircommon: Loading module: /snap/ubuntu-frame/8587/usr/lib/x86_64-linux-gnu/mir/server-platform/input-evdev.so.8
[2024-03-19 09:19:41.581794] <information> mirserver: Found display driver: mir:eglstream-kms (version 2.16.3)
[2024-03-19 09:19:41.587123] < - debug - > eglstream: Found EGLDeviceEXT with device extensions: EGL_EXT_device_drm EGL_EXT_device_drm_render_node
[2024-03-19 09:19:41.587633] <information> eglstream: Failed to query DRM node for EGLDevice: Failed to claim DRM master: Device or resource busy
[2024-03-19 09:19:41.587731] < - debug - > eglstream: Found EGLDeviceEXT with device extensions: EGL_MESA_device_software EGL_EXT_device_drm_render_node
[2024-03-19 09:19:41.587856] <information> eglstream: Failed to query DRM node for EGLDevice: Failed to determine DRM device node path from EGLDevice: EGL_BAD_PARAMETER (0x300c)
[2024-03-19 09:19:41.587890] < - debug - > eglstream: EGLDeviceEXTs found, but none are suitable for Mir
[2024-03-19 09:19:41.587927] <information> mirserver: (Unsupported by system environment)
[2024-03-19 09:19:41.587971] <information> mirserver: Found display driver: mir:gbm-kms (version 2.16.3)
[2024-03-19 09:19:41.592024] < - debug - > gbm-kms: Quirks: checking device with devnode: /dev/dri/card0, driver i915
[2024-03-19 09:19:41.592488] <information> gbm-kms: Failed to probe DRM device: ./src/server/console/linux_virtual_terminal.cpp(167): Throw in function {anonymous}::DRMDevice::DRMDevice(mir::VTFileOperations&, const char*, std::unique_ptr<mir::Device::Observer>, const std::shared_ptr<mir::LinuxVirtualTerminal::DeviceList>&)
Dynamic exception type: boost::wrapexcept<boost::exception_detail::error_info_injector<std::system_error> >
std::exception::what: Failed to claim DRM master: Device or resource busy
[boost::errinfo_file_name_*] = /dev/dri/card0

[2024-03-19 09:19:41.592992] < - debug - > gbm-kms: Quirks: checking device with devnode: (null), driver
[2024-03-19 09:19:41.593426] < - debug - > gbm-kms: Quirks: checking device with devnode: (null), driver
[2024-03-19 09:19:41.593864] < - debug - > gbm-kms: Quirks: checking device with devnode: (null), driver
[2024-03-19 09:19:41.594303] < - debug - > gbm-kms: Quirks: checking device with devnode: (null), driver
[2024-03-19 09:19:41.594731] < - debug - > gbm-kms: Quirks: checking device with devnode: (null), driver
[2024-03-19 09:19:41.594855] <information> mirserver: (Unsupported by system environment)
[2024-03-19 09:19:41.594909] <information> mirserver: Found display driver: mir:egl-generic (version 2.16.3)
[2024-03-19 09:19:41.595015] <information> mirserver: Found display driver: mir:x11 (version 2.16.3)
[2024-03-19 09:19:41.595090] <information> mirserver: (Unsupported by system environment)
ERROR: ./src/server/graphics/default_configuration.cpp(253): Throw in function virtual const std::vector<std::shared_ptr<mir::graphics::DisplayPlatform> >& mir::DefaultServerConfiguration::the_display_platforms()
Dynamic exception type: boost::wrapexcept<std::runtime_error>
std::exception::what: Exception while creating graphics platform
ERROR: ./src/server/graphics/platform_probe.cpp(184): Throw in function std::vector<std::pair<mir::graphics::SupportedDevice, std::shared_ptr<mir::SharedLibrary> > > {anonymous}::modules_for_device(const std::function<std::vector<mir::graphics::SupportedDevice>(const mir::SharedLibrary&)>&, const std::vector<std::shared_ptr<mir::SharedLibrary> >&)
Dynamic exception type: boost::wrapexcept<std::runtime_error>
std::exception::what: Failed to find any platforms for current system

From there, i tried to install and run frame-it in order to allow/enable remote access, by using these commands
sudo snap install --classic frame-it
sudo snap set frame-it shell-app=wpe-webkit-mir-kiosk.cog

The reason frame-it is mentioned is that it provides a handy script (frame-it.vnc) for the client machine to connect to the VNC host. To do this:

frame-it needs to be installed on the client
There is no need to set the shell-app

When calling frame-it wpe-webkit-mir-kiosk, I get the following error "/snap/frame-it/18/frame-it: line 21: ubuntu-frame_beta: command not found".

There is also no need to set shell (especially not to "ubuntu-frame_beta" - that is used as an example of how to test parallel installs of ubuntu-frame) it is also irrelevant to your use case.

Continued by executing frame-it.check, which gives me the following response:
~$ frame-it.check
Checking: ubuntu-frame_beta installation (needed for all commands)
 WARNING: ubuntu-frame_beta NOT installed. Please run the following:
  sudo snap install ubuntu-frame_beta
Checking: ubuntu-frame_beta has login-session-control (needed to run a login shell)
error: snap "ubuntu-frame_beta" not found
 WARNING: ubuntu-frame_beta:login-session-control NOT connected. Please run the following:
  sudo snap connect ubuntu-frame_beta:login-session-control
Checking: shell-app option (needed for frame-it.shell and to run a login shell)
 . OK . : shell-app is set (to 'wpe-webkit-mir-kiosk.cog') and can be found
Checking: osk option
 . OK . : "osk" is unset
Checking: vnc-viewer option (needed for frame-it.vnc)
 . OK . : vnc-viewer is set (to 'gvncviewer') and can be found

Executing sudo snap connect ubuntu-frame_beta:login-session-control
When I call frame-it.shell, the same error (/snap/frame-it/18/frame-it: line 21: ubuntu-frame_beta: command not found) appears. The application continues, but I'm unable to connect using RealVNC Viewer. How can is solve this issue?

This also relates to a different usecase (and the error is because you have set set shell=ubuntu-frame_beta.

https://mir-server.io/docs/how-to-use-remote-assistance-with-ubuntu-frame

Hi Alan,
Thans for your reply. I've found and followed the instructions on this URL. At the end, it says "It is up to the operator to expose it securely to the outside or provide other means of access. SSH port forwarding is a common approach: Here is one example using the frame-it snap and gvncviewer", which lead me here. It was never clear to me that this was about the client.
It says the it wat tested with RealVNC for example, but when I try to connect, it tels me "the connection was refused by the computer". When I use sudo ss -tlnp | grep 5900, I find out that wayvnc is using <IP_ADDRESS>:5900 as address and port.
LISTEN 0      16         <IP_ADDRESS>:5900      <IP_ADDRESS>:*    users:(("wayvnc",pid=1122,fd=13))

Also ps aux | grep "wayvnc" tells me wayvnc is running using localhost:
root        1122  0.0  1.6<PHONE_NUMBER>4 ?        Ssl  08:47   0:02 /snap/ubuntu-frame-vnc/325/usr/local/bin/wayvnc --gpu localhost 5900

There is no iptables or ufw active, however, I'm unable to find any helpful instructions, how to "expose it to the outside"... Ubuntu Frame looks like a good solution, but setting it up is still quite a challenge.

The frame-it.vnc script sets up the ssh tunnelling (assuming the current user has ssh credentials) and then runs a VNC client.
Here's the script: https://github.com/AlanGriffiths/frame-it/blob/master/frame-it/frame-it-vnc
This defaults to vnc-viewer=gvncviewer, but that can be set to other commands.

Here's the script: https://github.com/AlanGriffiths/frame-it/blob/master/frame-it/frame-it-vnc

How to get this script to work, using RealVNC from any Windows PC in order to connect. I just want to open RealVNC on my PC, insert the IP-address of the Ubuntu system and connect to it. Are there any options to run ubuntu-frame-vnc without binding it to <IP_ADDRESS>/localhost, but using <IP_ADDRESS> instead?
And if not, how to connect to the Ubuntu Frame VNC environment using Real VNC from a Windows PC? The frame-it-vnc script won't work on Mac/Windows. How to configure this?

I have no experience of RealVNC on Windows, you are the expert on that.
As it says in How to use remote assistance with Ubuntu Frame "Rather than expose an extra attack surface, ubuntu-frame-vnc is configured to only listen on localhost, on port 5900 (the default VNC port). It is up to the operator to expose it securely to the outside or provide other means of access."
The frame-it.vnc script is one way to do this and uses ssh tunnelling to provide secure access from the client system. I chose that because ssh is the normal way to access Ubuntu Core remotely.
I'm fairly sure I used ssh on Windows (but that was last millennium) so this approach should be possible on Windows too. But I don't remember what tools I used, nor how to configure them.

@claskfosmic we don't expose VNC outside of localhost because there's just no reliable way to secure it.
A simple ssh -L 5900:localhost:5900 <user>@<remote> should allow you to connect with RealVNC on localhost.
I'm adding that to the documentation at https://mir-server.io/docs/how-to-use-remote-assistance-with-ubuntu-frame?trk=public_post_comment-text#heading--remote-access


[Event Request] Table 5940 - onValidate "Serial No."

Hello
We need to add a new Event to skip the validation of the "Serial No." field
    field(2; "Serial No."; Code[50])
    {
        Caption = 'Serial No.';

        trigger OnValidate()
        var
            isHandled: Boolean;
        begin
            isHandled := false;
            OnBeforeValidateNoSeries(Rec, xRec, isHandled);
            if not isHandled then begin

With the event
[IntegrationEvent(false, false)]
local procedure OnBeforeValidateNoSeries(var ServiceItem: Record "Service Item"; var xServiceItem: Record "Service Item"; var IsHandled: Boolean)
begin
end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


Action link not handled in Cygwin

Hello Sir,
Dotbot fails to make symbolic links in windows Cygwin environment. I am using babun (http://babun.github.io/).
Is it possible to make it work across platform?
Thank you!

I'm using Dotbot under GNU/Linux platforms, and Cygwin, and it works like a charm. Can you provide a minimal example and the logs?

Turn out to be an issue with Anaconda python, it has issues wih the path. Works perfectly when I removed Anaconda from my path.

Huh, interesting, I wonder why Anaconda Python doesn't work properly…
Well, I'm glad you got this figured out :)


[Bug Report] how to implement v-model for el-select in Msgbox

Element UI version
2.11.1
OS/Browsers version
Chrome
Vue version
2.6.10
Reproduction Link
https://jsfiddle.net/zuLwa845/1/
Steps to reproduce
Click the button in the page, then the message box will pop up. Try to select an item.
What is Expected?
The item should appear in the select box, and be highlighted in the list.
What is actually happening?
Nothing happened visually. I have checked the value in the vue instance, which prove to be correctly altered. However, the selector doesn't render it.

This may not be a bug, but i didn't find the way to tackle it in element's doc or vue's doc.

but el-checkbox works


Add "circle" geometry type

The work in https://github.com/mapbox/mapbox-gl-native/pull/10103 uses mapbox/geometry.hpp for collision geometries, and needs a circle type added.
I just read the readme of geometry.hpp and saw that it's intended for GeoJSON geometry types, so maybe "circle" is not actually a good fit here?
/cc @ansis @jfirebaugh

Decided this doesn't belong here.


Create a 3-Panel View for all themes.

#278
Hi can we have a 3-Panel view like Redocly.
1st panel to have groups and list of APIs
2nd panel to have in-page links to direct to a particular API where we are able to see the request/response schemas, validators and descriptions of each API endpoint.
3rd panel to have the try-it-out feature and different code implementations.
If you need help in understanding this or technical assitance. I can be of help.
Thank you.

Like to understand whats the goal here

Is it more usable that way,  it just looks better or more people are used to that layout ?

list down your pain points with the rendering styles that RapiDoc supports and how those pain points can be solved through the 3 col view ?

RapiDocs UI is one of its USP, we take our user experience very seriously and we have conducted many user feedback about our styling in the past and here are few things that I remember what our user said against 3-col-view

gets too crammed up in narrow devices such as tablets
too many duplication of information on the middle and last panel, like responses are repeated etc
due to duplication of information, a small spec too looks quite big and overwhelming
difficult to understand due to information duplication

closing due to lack of response. please feel free to open new one and provide few reasons for the change you are asking so that i can take it forward


Fix for PropertiesFileTransformer breaks Reproducible builds in 8.1.1

Closes https://github.com/johnrengelman/shadow/pull/858.

Please have a look, added a test (which should fail with 8.1.1) and a fix on CleanProperties.
Removing the timestamp which default Properties class is adding could be tricky. I changed the previous mechanism to be bit more flexible (was not working either as some blank comment line is added now), but either way don't know if is a good approach. Please check

I've published this in https://github.com/Goooler/shadow/releases/tag/v8.1.8


Update dependency

Updating the haystack client java version to 0.2.5. This will go in release 0.2.5 of this project.

Codecov Report

Merging #4 into master will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master       #4   +/-   ##
=========================================
  Coverage     66.32%   66.32%
  Complexity       19       19
=========================================
  Files             2        2
  Lines            98       98
  Branches          6        6
=========================================
  Hits             65       65
  Misses           32       32
  Partials          1        1

Impacted Files
Coverage Δ
Complexity Δ

...ack/opentracing/spring/starter/TracerSettings.java
52.3% <ø> (ø)
2 <0> (ø)
:arrow_down:

...k/opentracing/spring/starter/TracerConfigurer.java
93.93% <ø> (ø)
17 <0> (ø)
:arrow_down:

Continue to review full report at Codecov.

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


Add non-dist files to bower.json ignore property.

When distributing the package through bower, all build, test, and documenation requirements can be ignored. Users only require the files in dist. Results in a smaller package and faster deployment.

This is needed. Right now there's too much on the package that's not really needed.
+1

Thank you, sorry for the delay.


Bug 1943804: split encryption tests

The current timeout for all encryption tests is 4 hours.
Previously the time needed to roll out a new KAS was 15 minutes, due to a known issue on AWS with the NLB it can take now 22 minutes.
It means that the tests need ~25 min to make sure that all servers are on the same revision and it is safe to start the test.
Since the rotation scenario needs to enable the encryption first, then wait and check if all resources were migrated, then change the encryption key and check the migration again.
It means that only these tests will need ~1 hour just for installing the servers.
Thus this PR moves the rotation tests to a separate CI job.
It will shorten the overall time needed to test encryption but also increase the pass rate of the tests as we have seen them frequently failing to due to a timeout.
xref: https://github.com/openshift/cluster-kube-apiserver-operator/pull/1079

/hold
I need to create a new CI job first before we can merge it

/assign @sttts

/test e2e-aws-operator-encryption-rotation

/test verify

/test e2e-aws-operator-encryption-rotation

/retest

e2e-aws-operator-encryption failed on e2e-aws-operator-encryption-gather-extra container test the encryption tests passed.

e2e-aws-operator-encryption-rotation green!

/lgtm

/hold cancel

/override ci/prow/k8s-e2e-gcp

/override ci/prow/e2e-aws-operator
/override ci/prow/e2e-aws-operator-encryption
/override ci/prow/e2e-aws-operator-encryption-rotation
/override ci/prow/e2e-upgrade


SCRUM-3952: add ExpressionPattern, TemporalContext and AnatomicalSite

You will need to rename your migration file as varun's file that just went in has the same number: v<IP_ADDRESS>__expression_pattern.sql will need to be: v<IP_ADDRESS>__expression_pattern.sql

File renamed and annotation ElementCollection removed


For the lolz cog can you have it on selfbots edit the message and spa lolz sentence

replace it with a lolz sentence*

it doesnt work in dms. Other than that its good

#23 working on it


keras-rl seems to require a specific version of supporting packages

I installed the latest keras-rl and have all packages updated. When I try
from rl.agents.dqn import DQNAgent
I get the error message

Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python2.7/site-packages/rl/agents/init.py", line 2, in
from .dqn import DQNAgent, ContinuousDQNAgent
File "/usr/lib/python2.7/site-packages/rl/agents/dqn.py", line 4, in
import keras.backend as K
File "/usr/lib64/python2.7/site-packages/keras/init.py", line 4, in
from . import activations
File "/usr/lib64/python2.7/site-packages/keras/activations.py", line 6, in
from .engine import Layer
File "/usr/lib64/python2.7/site-packages/keras/engine/init.py", line 8, in
from .training import Model
File "/usr/lib64/python2.7/site-packages/keras/engine/training.py", line 25, in
from .. import callbacks as cbks
File "/usr/lib64/python2.7/site-packages/keras/callbacks.py", line 26, in
from tensorflow.contrib.tensorboard.plugins import projector
File "/usr/lib/python2.7/site-packages/tensorflow/contrib/init.py", line 31, in
from tensorflow.contrib import factorization
File "/usr/lib/python2.7/site-packages/tensorflow/contrib/factorization/init.py", line 24, in
from tensorflow.contrib.factorization.python.ops.gmm import *
File "/usr/lib/python2.7/site-packages/tensorflow/contrib/factorization/python/ops/gmm.py", line 27, in
from tensorflow.contrib.learn.python.learn.estimators import estimator
File "/usr/lib/python2.7/site-packages/tensorflow/contrib/learn/init.py", line 88, in
from tensorflow.contrib.learn.python.learn import *
File "/usr/lib/python2.7/site-packages/tensorflow/contrib/learn/python/init.py", line 23, in
from tensorflow.contrib.learn.python.learn import *
File "/usr/lib/python2.7/site-packages/tensorflow/contrib/learn/python/learn/init.py", line 25, in
from tensorflow.contrib.learn.python.learn import estimators
File "/usr/lib/python2.7/site-packages/tensorflow/contrib/learn/python/learn/estimators/init.py", line 297, in
from tensorflow.contrib.learn.python.learn.estimators.dnn import DNNClassifier
File "/usr/lib/python2.7/site-packages/tensorflow/contrib/learn/python/learn/estimators/dnn.py", line 30, in
from tensorflow.contrib.learn.python.learn.estimators import dnn_linear_combined
File "/usr/lib/python2.7/site-packages/tensorflow/contrib/learn/python/learn/estimators/dnn_linear_combined.py", line 31, in
from tensorflow.contrib.learn.python.learn.estimators import estimator
File "/usr/lib/python2.7/site-packages/tensorflow/contrib/learn/python/learn/estimators/estimator.py", line 49, in
from tensorflow.contrib.learn.python.learn.learn_io import data_feeder
File "/usr/lib/python2.7/site-packages/tensorflow/contrib/learn/python/learn/learn_io/init.py", line 21, in
from tensorflow.contrib.learn.python.learn.learn_io.dask_io import extract_dask_data
File "/usr/lib/python2.7/site-packages/tensorflow/contrib/learn/python/learn/learn_io/dask_io.py", line 26, in
import dask.dataframe as dd
File "/usr/lib/python2.7/site-packages/dask/dataframe/init.py", line 3, in
from .core import (DataFrame, Series, Index, _Frame, map_partitions,
File "/usr/lib/python2.7/site-packages/dask/dataframe/core.py", line 40, in
pd.computation.expressions.set_use_numexpr(False)
AttributeError: 'module' object has no attribute 'computation'

I see from the web that it is solved with a specific version of pandas. The latest version is 0.20.3.

Sorry, found that updating dask fixes this.


ccache: 4.10.1 -> 4.10.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for ccache is: Compiler cache for fast recompilation of C/C++ code
meta.homepage for ccache is: https://ccache.dev
meta.changelog for ccache is: https://ccache.dev/releasenotes.html#_ccache_4_10_2
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 4.10.2 with grep in /nix/store/6brbzkd7svaws7jqw7ykpqjyrgqdnh57-ccache-4.10.2
found 4.10.2 in filename of file in /nix/store/6brbzkd7svaws7jqw7ykpqjyrgqdnh57-ccache-4.10.2

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

6 total rebuild path(s)

6 package rebuild(s)

First fifty rebuilds by attrpath

ccache
ccacheStdenv
ccacheWrapper
python311Packages.nuitka
python312Packages.nuitka

Instructions to test this update (click to expand)

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

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

Or:
nix build github:r-ryantm/nixpkgs/30afe6ea5c75c825933f949b2a036bc4198e2af6#ccache

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

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

8 packages built:

ccache
ccache.man
ccacheStdenv
ccacheWrapper
python311Packages.nuitka
python311Packages.nuitka.dist
python312Packages.nuitka
python312Packages.nuitka.dist

Maintainer pings
cc @kira-bruneau @r-burns for testing.

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

8 packages built:

ccache
ccache.man
ccacheStdenv
ccacheWrapper
python311Packages.nuitka
python311Packages.nuitka.dist
python312Packages.nuitka
python312Packages.nuitka.dist


Tracking Issue KCSNA 2024

ToDo's for the KCSNA 2024 related to the website

[x] Create scaffold page for summit
[x] Insert CfP
[x] Insert Notes Folder
[x] Insert Location & Venue Details
[x] Insert Registration Link & Details
[x] Remove Cfp
[x] Insert Sched
[x] Insert Uncof Details & Issue
[x] Insert Contributor Social Details

/assign @kaslin
/assign @mfahlandt

/remove-lifecycle stale

kcsna is complete
/close


the stable/prometheus and stable/grafana helm charts repo are deprecated

Hi everybody!
Where is the problem?
https://docs.konghq.com/kubernetes-ingress-controller/1.3.x/guides/prometheus-grafana/
What happened?
I want to monitor my kong/kubernetes-ingress-controller with prometheus and grafana.
in the documentaion of KIC they did this using helm , but the problem is helm charts of prometheus and grafana used in the installation guide are DEPRECATED.
What did you expect to happen?
the guide is using deprecated Prometheus components and should be updated
Code of Conduct and Community Expectations

[X] I agree to follow this project's Code of Conduct
[X] I agree to abide by the Community Expectations

@Kong/team-k8s can you please take a look? I checked v2.0 docs (here) and it looks like they refer to the same Helm charts.

@lena-larionova this is a follow up to this discussion: https://github.com/Kong/kubernetes-ingress-controller/discussions/1827
The long and short is that they are deprecated and while we may have a little bit of runway we need to test and document integrating against other non-deprecated Prometheus deployment mechanisms (such as the Prometheus operator which is linked in the discussion thread).

Completed in https://github.com/Kong/docs.konghq.com/pull/3288


Add ops-metric-client cli

Add 2 clis that use metric_sender class to send metrics:
ops-metric-client.py
ops-metric-gpg-client.py.
PR depends on https://github.com/openshift/openshift-tools/pull/1511

@twiest PTAL

Closing this - content already in https://github.com/openshift/openshift-tools/pull/1650


Vendor swarmkit, containerd, and related dependencies

Update swarmkit to 037b491.
As swarmkit switched to a newer gRPC version, this also involves updating Docker's vendored gRPC, which in turn requires updating containerd to a new version that has protobufs generated against this gRPC version.
Replaces #30226
Includes docker/containerd#371, docker/containerd#436, docker/containerd#428
Fixes #30156
Fixes #28821
Addresses #30026
cc @thaJeztah @docker/core-swarmkit-maintainers @docker/core-containerd-maintainers

ping @aaronlehmann was the TTY change for https://github.com/docker/docker/issues/30156 reverted? If so, that one should probably be reopened


Certificate not matching private key when creating multiple ingress resources

Describe the bug:
We currently have an issue which affects v0.7.X & v0.8.X during the following flow:
Two ingress resources are newly deployed at the same time with the same FQDN (different path though) pointing to two different secrets using http01 validation and ingress-shim.
In this scenario we often get a raise condition where cert-manager creates the two secrets with a new private key, then requests the certificate(s) and then writes one of the resulting certificates in BOTH secrets. So we end up with nginx reporting that the certificate and private key does not match. Additionally cert-manager logs an endless loop of the following messages:
cert-manager-logs.txt
Expected behaviour:
We expect cert-manager to either deduplicate the certificates and store the same cert and private key in the secrets which are used by nginx or to not deduplicate and request two certificates for the same domain with dedicated cert & private keys.
Steps to reproduce the bug:

deploy cert-manager via helm (chart v0.6.7)
deploy nginx via helm (chart v0.24.1 or v0.25.0)
create let's encrypt issuer with http01 validation (for this test we used the staging endpoint)
create two ingress resources with the same domain and different path as well as different secret name in the same namespace at the same time

Anything else we need to know?:
Short discussion on Slack: https://kubernetes.slack.com/archives/C4NV3DWUC/p1562761629206900
@munnerz proposed to add an e2e test for this scenario and then see if the issue also occurs in the test.
Environment details::

Kubernetes version (e.g. v1.10.2): v1.13.6
Cloud-provider/provisioner (e.g. GKE, kops AWS, etc): GKE
cert-manager version (e.g. v0.4.0): v0.7.X & v0.8.X
Install method (e.g. helm or static manifests): helm v2.14.1

/kind bug

I'm seeing the same issue in v0.9.X as well. Haven't tested v0.10.X yet

/remove-lifecycle stale

We've run into what looks like the same issue on v0.10.1. We only discovered it today thanks to an alarm on upcoming certificate expiration, but it turns out the conflicting order problem first started two weeks ago and since then cert-manager has been "completing" the same order 5 times per second.
The renewal orders were created automatically from certificates resources that have existed for some months. We don't use ingress-shim. The certificates are in different namespaces but have the same name and commonName. In this particular case, the orders happened to get the same name as well:
NAMESPACE    NAME                                STATE   AGE
consul       letsencrypt-production-2532835370   valid   16d
default      letsencrypt-production-2532835370   valid   16d

We don't see the same error message as above, only the following endless loop:
cert-manager-logs.txt
Fixing the issue was a matter of deleting the order resource, which was recreated automatically and completed properly this time.
Further details:
Kubernetes version: v1.14.9
cert-manager version: v0.10.1
Install method: Helm v2.14.1
Validation method: dns01

For what it's worth, it's considered a misconfiguration to have two ingress resources both referencing the same Secret name and both with cert-manager annotations. My first bit of advice here would be to get rid of this situation 😄
That said, we should fail safer in these cases to avoid it actually becoming an issue in the first place.

I just updated to v0.12 and still get the same issues even if using multiple secrets and also with the DNS01 method. As soon as they contain the same domain, there seems to be a raise condition (multiple private keys are generated, certs requested and then one cert is used which does not match the the other private keys).

Same problem applies when using csi driver with acme (private pki). There should be different certificates generated and used for each pod and should share common_name.
Can anyone recommend any workaround so I can use csi driver to issue mtls certificates.
csi.cert-manager.io/dns-names and csi.cert-manager.io/dns-names allow only one domain for all pods.

@jakobhostnik can you open an issue on the cert-manager-csi repo for this request? (cc @JoshVanL)
This issue is going to take a bit of work to resolve I think. It's also not something specifically covered by https://github.com/jetstack/cert-manager/pull/2753 yet either.
/area acme

@jakobhostnik The csi.cert-manager.io/dns-names volume attribute accepts a comma separated list of DNS names, i.e a.b.foo.com,c.d.foo.com

Looks like this issue has seen many thumbs up over time, and it seems to still appear on v1.3. I will try to reproduce it (somehow).
/assign

/good-first-issue

/remove-lifecycle stale

/remove-lifecycle stale

@munnerz could you please take a look?

@munnerz could you please take a look?

/remove-lifecycle rotten

I think I understand why this is happening, and I also don't think this is a good first issue for new contributors 😅
When both Order objects are created, because they point to the same FQDN, they are 'deduped' into a single ACME order. This results in 1 validation (or 'challenge') needing to be completed for the referenced FQDN.
At this stage, we still have not submitted a CSR to the ACME server (as this happens after a successful validation/challenge response).
The validation goes through and completes as normal, and at this point one of the two Orders will complete and submit their CSR to the ACME server. The certificate will then be signed and made available with the private key for this first Order object.
The second order will then also go to reconcile, and will query the ACME server to check the status of the order. The order has already been validated, so it'll then just update the Order objects status to reflect its current state (it'll set status.state = Valid).
This then hits this block of code on the next reconciliation: https://github.com/cert-manager/cert-manager/blob/aeae4b35fced192c9d7f8dc11dfcb7f746ff4e2f/pkg/controller/acmeorders/sync.go#L112-L115
In turn, this will be called: https://github.com/cert-manager/cert-manager/blob/aeae4b35fced192c9d7f8dc11dfcb7f746ff4e2f/pkg/controller/acmeorders/sync.go#L631
The issue here is that the ACME Order has been completed with a private key from the other Order object, which is referencing a different private key. Here though we are blindly copying the Order's issued certificate assuming that we are the one to have finalized it, when it fact due to order deduplication, it's been finalized using the other private key.
To fix this, we should have these areas of code check where the public keys match/the certificate & key forms a valid pair, and if it doesn't then mark the Order as failed and have it automatically be recreated. When recreated, an actual new order will be created (and the old validation can even be re-used, so the whole challenge flow won't happen again) and this will allow its own CSR to be submitted with an expected private key.

I'd really like to see an e2e or integration test for this however, that can reliably test this case out and fail (prior to us adding a patch to resolve it). This is a pretty complex chain of events, and I think we may struggle to ensure we never regress on this once fixed.

@munnerz thank you for your feedback.

/remove-lifecycle stale

/remove-lifecycle stale

/remove-lifecycle stale

/remove-lifecycle stale

Hi!
Is it possible that the behaviour of the let's encrypt (staging) acme server changed since this problem was reported?
I tried to reproduce the issue in a minimal microk8s cluster with just cert-manager and nginx.
However I get stuck at the order stage.
When I try to create two ingress objects with certificates at the same time, i just get two bad orders.
One is "errored" and the other one becomes "invalid".
This is the yaml file I used to create the two ingress objects:
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: ingress1
  annotations:
    cert-manager.io/issuer-kind: ClusterIssuer
    cert-manager.io/issuer: "letsencrypt-staging"
  namespace: sandbox

spec:
  ingressClassName: public
  tls:
  - hosts:
    - hello.microk8s.schimandl.at
    secretName: ingress1
  rules:
  - host: hello.microk8s.schimandl.at
    http:
      paths:
      - path: /
        pathType: Prefix
        backend:
          service:
            name: nginx
            port:
              number: 80
---
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: ingress2
  annotations:
    cert-manager.io/issuer-kind: ClusterIssuer
    cert-manager.io/issuer: "letsencrypt-staging"
  namespace: sandbox

spec:
  ingressClassName: public
  tls:
  - hosts:
    - hello.microk8s.schimandl.at
    secretName: ingress2
  rules:
  - host: hello.microk8s.schimandl.at
    http:
      paths:
      - path: /
        pathType: Prefix
        backend:
          service:
            name: nginx2
            port:
              number: 80

Here is the log output of cert-manager:
I1117 15:36:55.830607       1 start.go:75] cert-manager "msg"="starting controller"  "git-commit"="e466a521bc5455def8c224599c6edcd37e86410c" "version"="v1.8.0"
I1117 15:36:55.830806       1 controller.go:242] cert-manager/controller/build-context "msg"="configured acme dns01 nameservers" "nameservers"=["<IP_ADDRESS>:53"]
W1117 15:36:55.830925       1 client_config.go:617] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
I1117 15:36:55.831538       1 controller.go:70] cert-manager/controller "msg"="enabled controllers: [certificaterequests-approver certificaterequests-issuer-acme certificaterequests-issuer-ca certificaterequests-issuer-selfsigned certificaterequests-issuer-vault certificaterequests-issuer-venafi certificates-issuing certificates-key-manager certificates-metrics certificates-readiness certificates-request-manager certificates-revision-manager certificates-trigger challenges clusterissuers ingress-shim issuers orders]"
I1117 15:36:55.831859       1 controller.go:134] cert-manager/controller "msg"="starting leader election"
I1117 15:36:55.832213       1 leaderelection.go:248] attempting to acquire leader lease kube-system/cert-manager-controller...
I1117 15:36:55.832805       1 controller.go:91] cert-manager/controller "msg"="starting metrics server"  "address"={"IP":"::","Port":9402,"Zone":""}
I1117 15:36:55.847418       1 leaderelection.go:258] successfully acquired lease kube-system/cert-manager-controller
I1117 15:36:55.850111       1 controller.go:182] cert-manager/controller "msg"="not starting controller as it's disabled" "controller"="certificatesigningrequests-issuer-ca"
I1117 15:36:55.853364       1 controller.go:205] cert-manager/controller "msg"="starting controller" "controller"="certificates-readiness"
I1117 15:36:55.853428       1 controller.go:205] cert-manager/controller "msg"="starting controller" "controller"="orders"
I1117 15:36:55.853571       1 controller.go:205] cert-manager/controller "msg"="starting controller" "controller"="certificaterequests-issuer-acme"
I1117 15:36:55.853661       1 controller.go:205] cert-manager/controller "msg"="starting controller" "controller"="certificaterequests-issuer-ca"
I1117 15:36:55.853760       1 controller.go:205] cert-manager/controller "msg"="starting controller" "controller"="certificaterequests-issuer-vault"
I1117 15:36:55.854014       1 controller.go:205] cert-manager/controller "msg"="starting controller" "controller"="certificates-trigger"
I1117 15:36:55.854079       1 controller.go:205] cert-manager/controller "msg"="starting controller" "controller"="clusterissuers"
I1117 15:36:55.854198       1 controller.go:205] cert-manager/controller "msg"="starting controller" "controller"="certificates-key-manager"
I1117 15:36:55.959471       1 controller.go:182] cert-manager/controller "msg"="not starting controller as it's disabled" "controller"="gateway-shim"
I1117 15:36:55.959720       1 controller.go:205] cert-manager/controller "msg"="starting controller" "controller"="challenges"
I1117 15:36:55.960190       1 controller.go:205] cert-manager/controller "msg"="starting controller" "controller"="ingress-shim"
I1117 15:36:55.961516       1 controller.go:182] cert-manager/controller "msg"="not starting controller as it's disabled" "controller"="certificatesigningrequests-issuer-acme"
I1117 15:36:55.961539       1 controller.go:182] cert-manager/controller "msg"="not starting controller as it's disabled" "controller"="certificatesigningrequests-issuer-vault"
I1117 15:36:55.962142       1 controller.go:182] cert-manager/controller "msg"="not starting controller as it's disabled" "controller"="certificatesigningrequests-issuer-selfsigned"
I1117 15:36:55.962163       1 controller.go:182] cert-manager/controller "msg"="not starting controller as it's disabled" "controller"="certificatesigningrequests-issuer-venafi"
I1117 15:36:55.962473       1 controller.go:205] cert-manager/controller "msg"="starting controller" "controller"="certificaterequests-approver"
I1117 15:36:55.962541       1 controller.go:205] cert-manager/controller "msg"="starting controller" "controller"="certificaterequests-issuer-venafi"
I1117 15:36:55.962585       1 controller.go:205] cert-manager/controller "msg"="starting controller" "controller"="certificates-issuing"
I1117 15:36:55.962620       1 controller.go:205] cert-manager/controller "msg"="starting controller" "controller"="certificates-request-manager"
I1117 15:36:55.962681       1 controller.go:205] cert-manager/controller "msg"="starting controller" "controller"="certificates-revision-manager"
I1117 15:36:55.962712       1 controller.go:205] cert-manager/controller "msg"="starting controller" "controller"="issuers"
I1117 15:36:55.962756       1 controller.go:205] cert-manager/controller "msg"="starting controller" "controller"="certificaterequests-issuer-selfsigned"
I1117 15:36:55.962784       1 controller.go:205] cert-manager/controller "msg"="starting controller" "controller"="certificates-metrics"
I1117 15:36:56.057065       1 setup.go:202] cert-manager/clusterissuers "msg"="skipping re-verifying ACME account as cached registration details look sufficient" "related_resource_kind"="Secret" "related_resource_name"="example-issuer-account-key" "related_resource_namespace"="cert-manager" "resource_kind"="ClusterIssuer" "resource_name"="letsencrypt-staging" "resource_namespace"="" "resource_version"="v1"
I1117 15:37:00.972097       1 setup.go:202] cert-manager/clusterissuers "msg"="skipping re-verifying ACME account as cached registration details look sufficient" "related_resource_kind"="Secret" "related_resource_name"="example-issuer-account-key" "related_resource_namespace"="cert-manager" "resource_kind"="ClusterIssuer" "resource_name"="letsencrypt-staging" "resource_namespace"="" "resource_version"="v1"
I1117 15:37:26.410737       1 trigger_controller.go:200] cert-manager/certificates-trigger "msg"="Certificate must be re-issued" "key"="sandbox/ingress1" "message"="Issuing certificate as Secret does not exist" "reason"="DoesNotExist"
I1117 15:37:26.411952       1 conditions.go:201] Setting lastTransitionTime for Certificate "ingress1" condition "Ready" to 2023-11-17 15:37:26.411947962 +0000 UTC m=+30.609255278
I1117 15:37:26.410762       1 conditions.go:201] Setting lastTransitionTime for Certificate "ingress1" condition "Issuing" to 2023-11-17 15:37:26.41075782 +0000 UTC m=+30.608065116
I1117 15:37:26.429541       1 trigger_controller.go:200] cert-manager/certificates-trigger "msg"="Certificate must be re-issued" "key"="sandbox/ingress2" "message"="Issuing certificate as Secret does not exist" "reason"="DoesNotExist"
I1117 15:37:26.429591       1 conditions.go:201] Setting lastTransitionTime for Certificate "ingress2" condition "Ready" to 2023-11-17 15:37:26.429491095 +0000 UTC m=+30.626798400
I1117 15:37:26.429558       1 conditions.go:201] Setting lastTransitionTime for Certificate "ingress2" condition "Issuing" to 2023-11-17 15:37:26.429554775 +0000 UTC m=+30.626862069
I1117 15:37:26.512316       1 controller.go:161] cert-manager/certificates-readiness "msg"="re-queuing item due to optimistic locking on resource" "key"="sandbox/ingress1" "error"="Operation cannot be fulfilled on certificates.cert-manager.io \"ingress1\": the object has been modified; please apply your changes to the latest version and try again"
I1117 15:37:26.512451       1 conditions.go:201] Setting lastTransitionTime for Certificate "ingress1" condition "Ready" to 2023-11-17 15:37:26.512445292 +0000 UTC m=+30.709752597
I1117 15:37:26.516998       1 controller.go:161] cert-manager/certificates-trigger "msg"="re-queuing item due to optimistic locking on resource" "key"="sandbox/ingress2" "error"="Operation cannot be fulfilled on certificates.cert-manager.io \"ingress2\": the object has been modified; please apply your changes to the latest version and try again"
I1117 15:37:26.517821       1 trigger_controller.go:200] cert-manager/certificates-trigger "msg"="Certificate must be re-issued" "key"="sandbox/ingress2" "message"="Issuing certificate as Secret does not exist" "reason"="DoesNotExist"
I1117 15:37:26.518530       1 conditions.go:201] Setting lastTransitionTime for Certificate "ingress2" condition "Issuing" to 2023-11-17 15:37:26.518524988 +0000 UTC m=+30.715832314
I1117 15:37:26.917762       1 conditions.go:261] Setting lastTransitionTime for CertificateRequest "ingress2-lmfjg" condition "Approved" to 2023-11-17 15:37:26.917755644 +0000 UTC m=+31.115062949
I1117 15:37:26.965102       1 conditions.go:261] Setting lastTransitionTime for CertificateRequest "ingress2-lmfjg" condition "Ready" to 2023-11-17 15:37:26.965094047 +0000 UTC m=+31.162401342
I1117 15:37:27.144178       1 controller.go:161] cert-manager/certificates-key-manager "msg"="re-queuing item due to optimistic locking on resource" "key"="sandbox/ingress1" "error"="Operation cannot be fulfilled on certificates.cert-manager.io \"ingress1\": the object has been modified; please apply your changes to the latest version and try again"
I1117 15:37:27.171356       1 conditions.go:261] Setting lastTransitionTime for CertificateRequest "ingress1-4gtkk" condition "Approved" to 2023-11-17 15:37:27.171345672 +0000 UTC m=+31.368652966
I1117 15:37:27.199161       1 conditions.go:261] Setting lastTransitionTime for CertificateRequest "ingress1-4gtkk" condition "Ready" to 2023-11-17 15:37:27.199140545 +0000 UTC m=+31.396447840
I1117 15:37:27.213545       1 conditions.go:261] Setting lastTransitionTime for CertificateRequest "ingress1-4gtkk" condition "Ready" to 2023-11-17 15:37:27.213538082 +0000 UTC m=+31.410845377
I1117 15:37:27.221857       1 controller.go:161] cert-manager/certificaterequests-issuer-acme "msg"="re-queuing item due to optimistic locking on resource" "key"="sandbox/ingress1-4gtkk" "error"="Operation cannot be fulfilled on certificaterequests.cert-manager.io \"ingress1-4gtkk\": the object has been modified; please apply your changes to the latest version and try again"
E1117 15:37:29.110872       1 sync.go:545] cert-manager/orders "msg"="failed to finalize Order resource due to bad request, marking Order as failed" "error"="403 urn:ietf:params:acme:error:orderNotReady: Error finalizing order :: Order was already processing. This may indicate your client finalized the same order multiple times, possibly due to a client bug." "resource_kind"="Order" "resource_name"="ingress2-lmfjg-969872278" "resource_namespace"="sandbox" "resource_version"="v1"
I1117 15:37:29.142041       1 conditions.go:190] Found status change for Certificate "ingress2" condition "Issuing": "True" -> "False"; setting lastTransitionTime to 2023-11-17 15:37:29.141996439 +0000 UTC m=+33.339303734
I1117 15:37:29.160882       1 trigger_controller.go:179] cert-manager/certificates-trigger "msg"="Backing off from issuance due to previously failed issuance(s). Issuance will next be attempted at 2023-11-17 16:37:29.000000462 +0000 UTC m=+3633.197307757" "key"="sandbox/ingress2"
E1117 15:37:29.171959       1 controller.go:166] cert-manager/orders "msg"="re-queuing item due to error processing" "error"="error finalizing order: acme: order  status: invalid" "key"="sandbox/ingress1-4gtkk-969872278"
I1117 15:37:29.197352       1 conditions.go:190] Found status change for Certificate "ingress1" condition "Issuing": "True" -> "False"; setting lastTransitionTime to 2023-11-17 15:37:29.197344616 +0000 UTC m=+33.394651911
I1117 15:37:29.205647       1 trigger_controller.go:179] cert-manager/certificates-trigger "msg"="Backing off from issuance due to previously failed issuance(s). Issuance will next be attempted at 2023-11-17 16:37:29.000000661 +0000 UTC m=+3633.197307956" "key"="sandbox/ingress2"
I1117 15:37:29.215688       1 trigger_controller.go:179] cert-manager/certificates-trigger "msg"="Backing off from issuance due to previously failed issuance(s). Issuance will next be attempted at 2023-11-17 16:37:29.000000681 +0000 UTC m=+3633.197307976" "key"="sandbox/ingress1"
I1117 15:37:29.234580       1 trigger_controller.go:179] cert-manager/certificates-trigger "msg"="Backing off from issuance due to previously failed issuance(s). Issuance will next be attempted at 2023-11-17 16:37:29.000000481 +0000 UTC m=+3633.197307777" "key"="sandbox/ingress1"

I noticed that the message Let's Encrypt returns when trying to finalize an order that had already been finalized has slightly changed between 2021 and 2023.
Message in 2021:

403 urn:ietf:params:acme:error:orderNotReady: Order's status ("processing") is not acceptable for finalization

Message in 2023:

403 urn:ietf:params:acme:error:orderNotReady: Error finalizing order :: Order was already processing. This may indicate your client finalized the same order multiple times, possibly due to a client bug.

What I do not understand is why the "happy" order (ingress1) becomes invalid:

error finalizing order: acme: order status: invalid

Could you kubectl describe ingress ingress1-4gtkk-969872278 to show the reason for the order to be invalid?

@maelvls
The ingress objects look perfectly fine:
Name:             ingress1
Labels:           <none>
Namespace:        sandbox
Address:          <IP_ADDRESS>
Ingress Class:    public
Default backend:  <default>
TLS:
  ingress1 terminates hello.microk8s.schimandl.at
Rules:
  Host                         Path  Backends
  ----                         ----  --------
  hello.microk8s.schimandl.at
                               /   nginx:80 (<IP_ADDRESS>:80)
Annotations:                   cert-manager.io/issuer: letsencrypt-staging
                               cert-manager.io/issuer-kind: ClusterIssuer
Events:
  Type    Reason             Age                 From                       Message
  ----    ------             ----                ----                       -------
  Normal  CreateCertificate  104s                cert-manager-ingress-shim  Successfully created Certificate "ingress1"
  Normal  Sync               68s (x2 over 104s)  nginx-ingress-controller   Scheduled for sync

Name:             ingress2
Labels:           <none>
Namespace:        sandbox
Address:          <IP_ADDRESS>
Ingress Class:    public
Default backend:  <default>
TLS:
  ingress2 terminates hello.microk8s.schimandl.at
Rules:
  Host                         Path  Backends
  ----                         ----  --------
  hello.microk8s.schimandl.at
                               /   nginx2:80 (<IP_ADDRESS>:80)
Annotations:                   cert-manager.io/issuer: letsencrypt-staging
                               cert-manager.io/issuer-kind: ClusterIssuer
Events:
  Type    Reason             Age                 From                       Message
  ----    ------             ----                ----                       -------
  Normal  CreateCertificate  104s                cert-manager-ingress-shim  Successfully created Certificate "ingress2"
  Normal  Sync               68s (x2 over 104s)  nginx-ingress-controller   Scheduled for sync

here are the orders:
ubuntu@microk8s:~/cert_acme_collision$ kubectl describe orders -A                                                                                [38/548]
Name:         ingress1-rfdb8-969872278
Namespace:    sandbox
Labels:       <none>
Annotations:  cert-manager.io/certificate-name: ingress1
              cert-manager.io/certificate-revision: 1
              cert-manager.io/private-key-secret-name: ingress1-wshkw
API Version:  acme.cert-manager.io/v1
Kind:         Order
Metadata:
  Creation Timestamp:  2023-12-08T07:37:40Z
  Generation:          1
  Owner References:
    API Version:           cert-manager.io/v1
    Block Owner Deletion:  true
    Controller:            true
    Kind:                  CertificateRequest
    Name:                  ingress1-rfdb8
    UID:                   9842a4be-e67a-46bb-ab99-3e7f38df33e0                                                                                Resource Version:        13985                                                                                UID:                     5f819842-462b-4121-bc7b-0923782d588a                                                                                Spec:                                                                                Dns Names:                                                                                hello.microk8s.schimandl.at
  Issuer Ref:
    Group:  cert-manager.io
    Kind:   ClusterIssuer
    Name:   letsencrypt-staging
  Request:  LS0tLS1CRUdJTiBDRVJUSUZJQ0FURSBSRVFVRVNULS0tLS0KTUlJQ2l6Q0NBWE1DQVFBd0FEQ0NBU0l3RFFZSktvWklodmNOQVFFQkJRQURnZ0VQQURDQ0FRb0NnZ0VCQU1ISwpoT1VlN2ZTclB3UXQ3YUNLRGZ1ZEoxcVNSS2pjNUxuVHdWaGZUdHNuTTkrUFhzL0FHYTJDSldCSHplUVUvdUtiCmdKelZOVUpDVW5reVBBYX
YreXJCU3JTZjVPbkRiRFNlQmM4TFNZdkViNUlhVHJaMkxwWW1zS1FTMzE1SmV5dHUKTVpnU2p6TVdRUCsza1lhU1pPRm1xTzFmSEtFTTlTMGQyZmx6T0poaXd0N0dmdy8wWXVmSk1DQ2NaUndJYk1Megp0NGFBenhEdGRGUSs2ek5WQ3NVR1pCajBDTU1Zakw0U3FUVUYyKy9NWnFTNUplWUVZMGJvdXYvV3NCMk53UCs3CkFHczdOZGUwQkdm
enl1ZHhWdEdtNUxTVTVRMlV2SkZkQU0vQlh5YlVIN2kzbWVGTEVXTW9ZT21KMHVOV055ZHYKT2ZidlpldHdseUxFMXBhTlQ4c0NBd0VBQWFCR01FUUdDU3FHU0liM0RRRUpEakUzTURVd0pnWURWUjBSQkI4dwpIWUliYUdWc2JHOHViV2xqY205ck9ITXVjMk5vYVcxaGJtUnNMbUYwTUFzR0ExVWREd1FFQXdJRm9EQU5CZ2txCmhraUc5dz
BCQVFzRkFBT0NBUUVBUXpFa2xEK1l3aC9RanUyK0Y3eXhXb0R1SmY2eE1RN0orKzdlWVJIejBjdEsKeC9pVDE1UGphNUt6MHYwSk9XZVJBY3dtSkJiaUR1YUhrc2IzYlFtK0FVQzhSWjZFaklobjdFbm9NZ0JjZkRDeQpGaEVMb1lWd1VGRFUrcHJ3eDh6WlVOeldlc0xpU2RodkRCZzJpWnpSMmQvZE1POEc0SkhBcklXYjFoVmYzblM3CnB4
NnN2OENBVHd6VWJqM3NmaEk3YWNhbFBoTjZkQkhPblVHN1BaREJ0dERGZTFVZXdmeGVXSzNVcmFLRy90SVEKcFZDUzN0ajFEWUx5TFBPRnYvUWNvQmYwa0tyd2NPU0U2SXNyS0tmYWRWSGYrMytkSk1jU0dUT2tIZlJoVGlzMgphV2c0WEVXTjVZYWNhbUM5em1hdjdOUEttSVpvRkZjT0RFajg5NmZEL1E9PQotLS0tLUVORCBDRVJUSUZJQ0
FURSBSRVFVRVNULS0tLS0K
Status:
  Authorizations:
    Challenges:
      Token:        lqrkN0nne93vfVSIrQ8BKVooX2q5NxdoMGsy3TAEoUE
      Type:         http-01
      URL:          https://acme-staging-v02.api.letsencrypt.org/acme/chall-v3/9420878784/yDr8iA
    Identifier:     hello.microk8s.schimandl.at
    Initial State:  valid
    URL:            https://acme-staging-v02.api.letsencrypt.org/acme/authz-v3/9420878784
    Wildcard:       false
  Failure Time:     2023-12-08T07:37:43Z
  Finalize URL:     https://acme-staging-v02.api.letsencrypt.org/acme/finalize/125170484/12827856964
  Reason:           Failed to finalize Order: 403 urn:ietf:params:acme:error:orderNotReady: Error finalizing order :: Order was already processing. This may indicate your client finalized the same order multiple times, possibly due to a client bug.
  State:            errored
  URL:              https://acme-staging-v02.api.letsencrypt.org/acme/order/125170484/12827856964
Events:             <none>

Name:         ingress2-bnphh-969872278
Namespace:    sandbox
Labels:       <none>
Annotations:  cert-manager.io/certificate-name: ingress2
              cert-manager.io/certificate-revision: 1
              cert-manager.io/private-key-secret-name: ingress2-p5sdj
API Version:  acme.cert-manager.io/v1
Kind:         Order
Metadata:
  Creation Timestamp:  2023-12-08T07:37:40Z
  Generation:          1
  Owner References:
    API Version:           cert-manager.io/v1
    Block Owner Deletion:  true
    Controller:            true
    Kind:                  CertificateRequest
    Name:                  ingress2-bnphh
    UID:                   e57c762f-d84e-43e5-9807-7ef9745f5dee
  Resource Version:        13996
  UID:                     cda12091-c8f9-47f5-a9a2-4924113ba6e9
Spec:
  Dns Names:
    hello.microk8s.schimandl.at
  Issuer Ref:
    Group:  cert-manager.io
    Kind:   ClusterIssuer
    Name:   letsencrypt-staging
  Request:  LS0tLS1CRUdJTiBDRVJUSUZJQ0FURSBSRVFVRVNULS0tLS0KTUlJQ2l6Q0NBWE1DQVFBd0FEQ0NBU0l3RFFZSktvWklodmNOQVFFQkJRQURnZ0VQQURDQ0FRb0NnZ0VCQUxtcAovY3ZKQ2xoN29XZzBMOXUzWi9uQlhiUmJIMFVjdk5oYldpM1lnM3hlV1RoaTJvOUwyMFUvdEV6dEpVNzZkb2R3CnQ5MTVlU09CTDg3VVd1UGp3bVFkSnFDYUp1WmhSMDlrRDl5anl3a2RpU0E5bEFkV2xUUXJFT3p4V3NBWjJwMU8KYVR5V0pmRlVZUElPdGo5WW8zVUxuWDlHdFJaM3RoREFxa2l2WTFsdERWemhTb1hmaS9FZGU0SkRSRk9ldmgvOQptV3Q1TFVPeUVtbENXZVp0YnlObHRYSElTcHo3SlA0NU5VdUgvenE4VDhqUTlpNUl0LzVHbkpjZjcybGpCd1hBCmpSTTBZR2VpZmo4RVBXbmZVWDZuYjk5WUNsb3dUUEo4eUtCUEc4b0pDZnQ2VlFLSzV2ZkdNOWpscTB6L2dFOG8KUytSV1lIZkw0cDZpUndsckdsOENBd0VBQWFCR01FUUdDU3FHU0liM0RRRUpEakUzTURVd0pnWURWUjBSQkI4dwpIWUliYUdWc2JHOHViV2xqY205ck9ITXVjMk5vYVcxaGJtUnNMbUYwTUFzR0ExVWREd1FFQXdJRm9EQU5CZ2txCmhraUc5dzBCQVFzRkFBT0NBUUVBaDhhMzdPejJhbDQxUExkTFFDNGFSQWFSdCtGQ0tlL1I4cjQrMi9xUkdNU2IKdklJZy8wLzh5aW10WVdWN0NGYWQxV0RPRXU1aE1WUkF4cE5rRGRtSTN6dzdvY0tNVlRvY0dZTkYwYW5UT09yRAo2TGg0dlAxWUFLOTNlaXJxaytKVzlBczdTV1gvRzgxTGlySlcwTmg3Q2g3RWY1VStQNWllNFNoWkNUT2RWQTM1CmNLN2VVT0FYaGhzcXVRMytVRmVBMG1ubmk1eTZSQjlISkdUSUNJOGdWOXBnL0tNZzZ4OEpmTnVvWUVXd1NZeDQKODQ0bkI5MUNWc1dHQk9tYUdWWUpWaXNzSnNla29LVmgvUDFqbWRKT0xIcFdacVd1b0lGN0JWYS9DSUVldDhaTQpjaXJVaUYyc3pjYnYwUTNmODN1Skg0aTM5RHREbnk5VDV5NTIyaU54cXc9PQotLS0tLUVORCBDRVJUSUZJQ0FURSBSRVFVRVNULS0tLS0K
Status:
  Authorizations:
    Challenges:
      Token:        lqrkN0nne93vfVSIrQ8BKVooX2q5NxdoMGsy3TAEoUE
      Type:         http-01
      URL:          https://acme-staging-v02.api.letsencrypt.org/acme/chall-v3/9420878784/yDr8iA
    Identifier:     hello.microk8s.schimandl.at
    Initial State:  valid
    URL:            https://acme-staging-v02.api.letsencrypt.org/acme/authz-v3/9420878784
    Wildcard:       false
  Failure Time:     2023-12-08T07:37:46Z
  Finalize URL:     https://acme-staging-v02.api.letsencrypt.org/acme/finalize/125170484/12827856964
  State:            invalid
  URL:              https://acme-staging-v02.api.letsencrypt.org/acme/order/125170484/12827856964
Events:             <none>

and here is the state of the order from the staging server's perspective:
{
  "status": "invalid",
  "expires": "2023-12-12T13:03:53Z",
  "identifiers": [
    {
      "type": "dns",
      "value": "hello.microk8s.schimandl.at"
    }
  ],
  "authorizations": [
    "https://acme-staging-v02.api.letsencrypt.org/acme/authz-v3/9420878784"
  ],
  "finalize": "https://acme-staging-v02.api.letsencrypt.org/acme/finalize/125170484/12827856964",
  "error": {
    "type": "urn:ietf:params:acme:error:serverInternal",
    "detail": "Error setting order processing",
    "status": 500
  }
}

@kevinkupski, is this still an issue?

/remove-lifecycle stale


changed apiVersion to batch/v1beta1, which does support the CronJob kind

The v2alpha1 version has an error for the CronJob type: "Error: validation failed: unable to recognize "": no matches for kind "CronJob" in version "v1" ". Replacing it with v1beta1 solves this issue.

As with #48 you don't actually need the cleanup job if you're running recent versions of kubernetes (with the new API version spec). The old jobs will be cleaned up automatically.

Ah, alright I will remove the cleanup job then. Thanks Pieter


About MVS annotation in COCO format

Hi @pkontschieder ,
By following the instruction, it seems that the coco-format json file used here is missing for Mapillary Vista. Is this the same one created in this repo?
Also, the extracting data script assumes the MVS dataset version is v1.1, while the most recent version I requested if v1.2. Can I assume I can use v1.2 for the challenge since there is no much difference between the versions?

@xingyizhou : until we get a confirmation, I have added the prepare_vista script as a step during the extractor step. Please test this script:
https://github.com/ozendelait/rvc_devkit/blob/master/segmentation/convert_mvd_coco.sh
I have renamed all "mvs" abbreviations to the correct "mvd". All you have to do is rename the mvs folder, everthing else stay the same

Oh, and I also updated the extractor to use v1.2 instead of v1.1 although both should work with the converter script and both are fine for usage during training

The difference between v1.1 and v1.2 is that RGB images now have privacy blurring. There is no difference wrt data loading, filenames, etc. @xingyizhou @ozendelait

Thanks for the clarification. Issue closed


pyrax - out of date

Hi,
Pyrax is out-of-date and insists on pulling in the old python-novaclient-2.27.0 package!  Can this not be updated to pull in python-novaclient-6.0.0?
Currently it is not possible to install pyrax and supernova on the same device!  Supernova removes 2.27.0:
...
  Found existing installation: python-novaclient 2.27.0
    Uninstalling python-novaclient-2.27.0:
      Successfully uninstalled python-novaclient-2.27.0
Successfully installed configobj-5.0.6 debtcollector-1.8.0 keystoneauth1-2.12.1 monotonic-1.2 netifaces-0.10.5 oslo.i18n-3.9.0 oslo.serialization-2.13.0 oslo.utils-3.16.0 pbr-1.10.0 positional-1.1.1 pyparsing-2.1.9 python-novaclient-6.0.0 pytz-2016.7 requests-2.11.1 six-1.10.0 stevedore-1.17.1

Pyrax has been deprecated in favor of, the currently in development, rackspacesdk.  As such we are no longer developing pyrax and have decided to freeze its dependencies to known working versions.
https://pypi.python.org/pypi/rackspacesdk
rackspacesdk is not yet a full replacement for pyrax, and should you need to utilize pyrax it is recommended that you install pyrax inside of a python virtualenv to handle dependency versions.

The support for Nova/Cloud Servers in openstacksdk/rackspacesdk currently includes support for the following resources, which make up a pretty good portion of them. It's fairly easy to add the rest so if there's something you need now it can be added, otherwise we'll eventually get through everything:

metadata
server ip
server interface
server group
image
hypervisor
extension
availability zone
keypair
limits
flavor
service
server


Create pull_request.yml

Trying to get docs auto-building on PRs.

Looks like a great idea, but with the current user guide we won't get any syntax highlight. As it depending upon cilexer styling. Either we figure out how to include and build it**. Or we update to the latest Sphinx and source/conf.py settings to default into PHP instead. Future proofing the project. As it refers to easy_install that's not being used anymore.
** I tried building it today on my server to check that my latest user guide PR looked good. But it never found ci styling. No idea what went wrong.

@jreklund this is next on my list to look at after #2668. However I have zero Sphinx experience so I’m glad to see you do. I’ll reach out on Slack but feel free to share any resources here too.

I have made PR #2671, removing internal package (cilexer) as a requirement.
For this we will need to run pre-build-command: apt install -y python-pip in case it's not already included in that action.
At first glance they use pip (Python 2) and not pip3 (Python 3), so we should be all good there. As the Sphinx version we require only works with Python 2.

I think this has already been addressed by the userguide_ci.yml workflow?

Oh, wow. Forgot about this one. But, yes, this is already handled. Thanks!


New version: EffectiveWaves v0.4.0

Registering package: EffectiveWaves
Repository: https://github.com/JuliaWaveScattering/EffectiveWaves.jl
Created by: @arturgower
Version: v0.4.0
Commit: 6ad045aa9b3ca7f8e1296299aac5577773bc06f2
Reviewed by: @arturgower
Reference: https://github.com/JuliaWaveScattering/EffectiveWaves.jl/commit/6ad045aa9b3ca7f8e1296299aac5577773bc06f2#commitcomment-43303574

Cancel this PR


Fixes Issue# 2115

Description

Below are the changes made to fix #2115
242d3bc - Added 5 sec's sleep to launch peers in "compose-default.yaml" file.
fcc2d17 -  printing docker container IP address
c1d20a0 - Increased timeout to 10 sec's from 5 sec's in Issue_1851 behave test case.
Motivation and Context

Fixes #
#2115
How Has This Been Tested?

Executed behave tests in Jenkins build machines
Checklist:

[x] I have added a Signed-off-by.
[x] I have either added documentation to cover my changes or this change requires no new documentation.
[x] I have either added unit tests to cover my changes or this change requires no new tests.
[] I have run golint and have fixed valid warnings in code I have added or modified. This tool generates false positives so you may choose to ignore some warnings. The goal is clean, consistent, and readable code.

<EMAIL_ADDRESS>

reverify jenkins

reverify jenkins

reverify jenkins

reverify jenkins

reverify jenkins

reverify jenkins

reverify jenkins

reverify jenkins

reverify jenkins

reverify jenkins

reverify jenkins

reverify jenkins

reverify jenkins

@jeffgarratt Please review

@srderson @rameshthoomu looks good to me.  I am always a bit concerned that our peers do NOT manage the membersvc not being ready.  We should probably create a new issue to address that.

@jeffgarratt Thanks for the quick review!
LGTM


Cursor based pagination for SQL queries

Right now platformatic supports offset based pagination (#206) which starts falling off in performance with lots of records. Almost forming a linear growth when it comes to query execution time. Cursor based pagination is almost constant even with 100's of millions of records.
Possible approach
The following are params that could be accepted from the API (say query string):

Direction of page
Cursor
Limit

Examples of known public API's using this approach:

https://stripe.com/docs/api/pagination (They merge cursor and direction into 1 param)
Reddit

Example spec
For the sake of simplicity, we can form our own spec for the scope of this issue:
Query params

?next (boolean) if next=true, move to next page else previous
?limit (number) max of 1000
?cursor (id) usually the id field

Pagination util applied on querystring
// some pseudocode to give an idea of how it could look likr
let { next, limit, cursor } = req.query
let firstPage = false

if (limit > 1000) {
  limit = 1000
}

if (!next && cursor < 1) {
  firstPage = true
}

return {
  next,
  firstPage,
  limit,
  cursor
}

SQL queries
const pagination = paginationUtil(req.query)

// this assumes the latest data is the most important (e.g. payment transactional data)
// https://www.db-fiddle.com/f/5LSQFRasNxh7y9jtthnPhV/0
// for oldest data as more important see https://www.db-fiddle.com/f/iWFY9uScYiGU1d9TKCYQVk/1
if (pagination.firstPage) {
  sql`SELECT id, val FROM test ORDER BY id DESC LIMIT ${pagination.limit}`
} else if (pagination.next) {
  sql`SELECT id, val FROM test WHERE id < ${pagination.cursor} ORDER BY id DESC LIMIT ${pagination.limit}`
} else {
  sql`SELECT * FROM (SELECT id, val FROM test WHERE id > ${pagination.cursor} ORDER BY id ASC LIMIT ${pagination.limit}) AS previous_page ORDER BY id DESC;`
}

Documenation
If paginating forward, pass in the id of the last result i.e. results[length(results) - 1]. If paginating backwards pass the id of the first element of the current result set i.e. results[0].

This would be an amazing feature to have.


NNAPIFlags for Specifying CPU or GPU Inference Do Not Take Effect

ONNX Runtime version: 1.17.0
Android version: 10
Kotlin version: 1.9.22
JAVA version: 2.1
SDK Build-Tools: 33.0.1
AGP: 8.1.3
GPU: ARM Mali GPU | G310
CPU: ARMv8 Processor rev 4 (v8l)

Steps to Reproduce:
I'm trying to configure the ONNX Runtime session within the DepthAnything Class to use NNAPI with specific flags (e.g. USE_FP16 and CPU_DISABLED). Here's the code snippet for setting up the session options:
    private val ortEnvironment = OrtEnvironment.getEnvironment()
    private val ortSession : OrtSession
    private val inputName: String
    init
    {
            // Create session options
            val options = OrtSession.SessionOptions().apply
            {
                 addNnapi(EnumSet.of(NNAPIFlags.USE_FP16, NNAPIFlags.CPU_DISABLED))
            }
            val modelByteArray = context.assets.open("depth_anything_small_fp16.onnx").readBytes()
            ortSession = ortEnvironment.createSession(modelByteArray, options)
            inputName = ortSession.inputNames.iterator().next()
    }

Expected Behavior:
I expected the model inference to run using NNAPI with FP16 precision and without using the CPU.
Actual Behavior:
The inference seems to run as if these options were not applied at all. The performance and behavior do not change regardless of the flags set.

@BeIanChang I have not explored the USE_FP16 and CPU_DISABLED options in onnxruntime. I'll study them and check how we can apply these options effectively to the Depth-Anything ONNX model used in this project.

In Android Studio Logcat I got following information during loading model:
2024-02-28 17:49:49.464 17037-17037 onnxruntime             com.ml.shubham0204.depthanything     W   [W:onnxruntime:, graph.cc:108 MergeShapeInfo] Error merging shape info for output. 'post-postop-output' source:{-1,-1,-1,1} target:{1,518,518,3}. Falling back to lenient merge.
2024-02-28 17:49:49.481 17037-17037 Manager                 com.ml.shubham0204.depthanything     I  DeviceManager::DeviceManager
2024-02-28 17:49:49.482 17037-17037 Manager                 com.ml.shubham0204.depthanything     I  findAvailableDevices
2024-02-28 17:49:52.742 17037-17037 onnxruntime             com.ml.shubham0204.depthanything     W   [W:onnxruntime:ort-java, nnapi_execution_provider.cc:225 GetCapability] NnapiExecutionProvider::GetCapability, number of partitions supported by NNAPI: 3 number of nodes in the graph: 724 number of nodes supported by NNAPI: 11
2024-02-28 17:49:52.808 17037-17037 onnxruntime             com.ml.shubham0204.depthanything     W   [W:onnxruntime:ort-java, nnapi_execution_provider.cc:225 GetCapability] NnapiExecutionProvider::GetCapability, number of partitions supported by NNAPI: 3 number of nodes in the graph: 725 number of nodes supported by NNAPI: 11
2024-02-28 17:49:52.869 17037-17037 TypeManager             com.ml.shubham0204.depthanything     I  Failed to read /vendor/etc/nnapi_extensions_app_allowlist ; No app allowlisted for vendor extensions use.
2024-02-28 17:49:55.624 17037-17037 onnxruntime             com.ml.shubham0204.depthanything     W   [W:onnxruntime:, session_state.cc:1166 VerifyEachNodeIsAssignedToAnEp] Some nodes were not assigned to the preferred execution providers which may or may not have an negative impact on performance. e.g. ORT explicitly assigns shape related ops to CPU to improve perf.
2024-02-28 17:49:55.624 17037-17037 onnxruntime             com.ml.shubham0204.depthanything     W   [W:onnxruntime:, session_state.cc:1168 VerifyEachNodeIsAssignedToAnEp] Rerunning with verbose output on a non-minimal build will show node assignments.

So I guess that most of the model is simply not suppported by NNAPI.


stops recording after few hours

Sir you wrote a nice application. Thanks a ton for your effort. I am testing for few days the issue is it stops recording in 2 to 4 hours. I have to relaunch.  It says stream stopped etc. My phone is active no network issues. Could you help. Thx

Can confirm. There is an issue that WaTracker stops recording however still thinks he is recording properly. There is no real log output that indicates the issues. Restarting the recording window solves the problem.

Hello,
Sorry to hear about the problem.
Currently I don't have time to work on the app,
but if someone figures our the solution I'll be happy to update the code.
-Andrey

I think simply faking some mouse clicks in the web app window would solve this.

So using my logitech keyboard I generated a infinite left click script that ran every second and the application still goes into Signed in but not recording

Well it runs for me for about 30 mins to an hour I simulated clicks within the chrome app loading different chats every 5 seconds but I still get signed in but not recording. So we can at least rule out the user input theory. The only solution is to close the record window and hit the record button again.
I'm not a JavaScript developer or chrome app dev so I don't really understand where the code execution starts. So could someone update the current script to close the record window and relaunch it every ten minutes or so and we should be able to get around the recording timing out. If someone can tell me which files I need to modify I should be able to do it myself and push the changes for everyone.

It works for me. I mean you might need to debug it. Remove the infinite
while loop and see if it closes the record window when it says signed in
but not recording.
However, again this is a fix that makes it work but it's not a solution.
Can a JavaScript developer help us find a permanent solution?
if I understood the flow of the program I would do the following for a
solution:
1.I would check when the record windows says "Signed in but not recording"
2. kill the record window
3. relaunch the record window event when you hit the record button in the
main menu
Hope that helps!
Let me know if you have any other additional questions?
Cheers,
Erik
On Wed, Apr 11, 2018 at 1:19 AM, MAISTA23<EMAIL_ADDRESS>wrote:

Even tho i installed sikulix and used the code above, its just does
nothing. There seems something to be missing. Care to eloberate on this?
Thanks ;)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/andrey-leshenko/WaTracker/issues/11#issuecomment-380277497,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACVe8qoq0LLEgvbfNmPzJyinbleN0sqPks5tnT3sgaJpZM4RL-Qj
.

Figured it out. Thanks alot. Now WaTracker is not working at all anymore (since like 2 hours). Its just says port is closed or something like that immediately after i wanna start recording. Reinstalled (even the other fork) and restartet everything. Not working ;(

Yeah mine says that all the time but it still works
On Thu, Apr 12, 2018 at 1:44 AM, MAISTA23<EMAIL_ADDRESS>wrote:

Figured it out. Thanks alot. Now WaTracker is not working at all anymore
(since like 2 hours). Its just says port is closed or something like that
immediately after i wanna start recording. Reinstalled (even the other
fork) and restartet everything. Not working ;(
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/andrey-leshenko/WaTracker/issues/11#issuecomment-380629667,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACVe8iU1Ek2xuiWclchjAYexhr7W54xfks5tnpVjgaJpZM4RL-Qj
.

It is still working for you? I just woke up and tried again. Nothing. Hes not starting the record. Even tried to reinstall chrome.

Yeah it's working for me without issue I'll send you a screen shot when I
get home
On Thu, Apr 12, 2018, 10:39 MAISTA23<EMAIL_ADDRESS>wrote:

It is still working for you? I just woke up and tried again. Nothing. Hes
not starting the record. Even tried to reinstall chrome.
[image: unbenannt]
https://user-images.githubusercontent.com/28226054/38665861-c1060e7e-3e3d-11e8-97e5-c29404c49d60.png
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/andrey-leshenko/WaTracker/issues/11#issuecomment-380724527,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACVe8tc04e74cDQQS-3NF-Kf10YIP_Qaks5tnxK6gaJpZM4RL-Qj
.

same for me.
worked till yesterday, today the port is closed just from the start :(

I can confirm my solution still works

So. Everyone else got the same error but you? Im using Windows 10, reinstalled the tracker, chrome and whatsapp itself on my phone. Tried it on another PC. Nothing works. It just wont record anymore.

I think we got banned or something. Cause mine stopped working just now
On Sat, Apr 14, 2018, 01:24 MAISTA23<EMAIL_ADDRESS>wrote:

I can confirm my solution still works
So. Everyone else got the same error but you? Im using Windows 10,
reinstalled the tracker, chrome and whatsapp itself on my phone. Tried it
on another PC. Nothing works. It just wont record anymore.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/andrey-leshenko/WaTracker/issues/11#issuecomment-381283150,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACVe8sHZejgThQvF2bSjX0vT13LwOXf4ks5toTPIgaJpZM4RL-Qj
.

I think we got banned or something. Cause mine stopped working just now

Then its not an account ban. I tried it on another whatsapp account. Same error.

me to face the same problem I used to restart the record button multiple times it worked for a day and then no I get Signed in not recording. I reinstalled on multiple machines. getting the same issue. Can some one help?

it looks like something is happening to block this

I had the same problem.
Notice that when "wa_stream_end" occurred in the log it said that it was throwing the messages because the port was closed, but the messages were coming.
So edit the script and modify it. I deleted
case 'wa_stream_end':
if (port) {
port.disconnect ();
port = null;
}
break;
So the port does not close.
I've been without problems for weeks

I have another problem. The activity of some contacts is never recorded, but if I consult through the whstsapp on the phone, I can see the last connection or if there is the line, but wa tracker only recoerd it on a few occasions.,
Can someone help? thanks

I have another problem. The activity of some contacts is never recorded, but if I consult through the whstsapp on the phone, I can see the last connection or if there is the line, but wa tracker only recoerd it on a few occasions.,
Can someone help? thanks

It somehow records only contacts who have an active conversation tab open. There was some workaround here, look for  it.
So it is working for you as we speak? I tried your solution and it does not work

I keep getting the following message and it is not recording but in the logs I see the messages for login and logout timing, But it is not recording it shows  "Signed in but no Recording"
i almost spend a day but unable to resolve can you please help?

any help on this please now I am getting stream.store.markUnavailable blocked, what is the reason


Choose appropriate representation for AST

http://stackoverflow.com/questions/33679522/choose-an-ast-representation-in-haskell

Indexed recursion scheme as final solution.


Add pp/pl/tl into docs and init

closes #23 #29

@flying-sheep can we merge this?

Sure, looks fine!


Finish auto-book program

Introduction
The auto-book program enables us to schedule a meeting room at CSUF.
Steps

[x] Log in
[ ] Check if bookings are able to be created
[ ] Create a booking at a valid date and time
[ ] Screenshot and log the result
[ ] Profit

https://titans.service-now.com/library/library_catalog.do

TODO: Rewrite in Deno Astral.


Move PropagationUtil to BinaryPropagationHandler.

This is a preparation for the https://github.com/google/instrumentation-java/pull/201

Codecov Report

Merging #202 into master will not change coverage.
The diff coverage is 0%.

@@            Coverage Diff            @@
##             master     #202   +/-   ##
=========================================
  Coverage     94.51%   94.51%
  Complexity      412      412
=========================================
  Files            56       56
  Lines          1294     1294
  Branches         90       90
=========================================
  Hits           1223     1223
  Misses           45       45
  Partials         26       26

Impacted Files
Coverage Δ
Complexity Δ

...nstrumentation/trace/BinaryPropagationHandler.java
87.17% <0%> (ø)
4 <0> (?)

Continue to review full report at Codecov.

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


Doesn't work on RC2

Hi Damien :godmode:
Came across your repo, cool package and thanks for sharing :tada:.
However I'm having trouble using this in a RC2 project. Everything's alright except when I try to add and apply the migration. The library code is integrated properly, and everything is set up according to your documentation. Here's the migration error:
warning NU1012: Dependency conflict. Microsoft.EntityFrameworkCore                                                                                1.0.0-rc3-21343 expected Microsoft.Extensions.Logging >= 1.0.0-rc3-21343 but go                                                                                t 1.0.0-rc2-final
And a little more down in the stack trace:
Could not load type 'Microsoft.Extensions.DependencyInjection.ServiceCollectionE                                                                                xtensions' from assembly 'Microsoft.Extensions.DependencyInjection, Version=1.0.                                                                                0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60'
I think if you rebuild the package on RC2, this issue will be resolved.

Hello again,
I've updated the package to "Localization.SqlLocalizer": "1.0.1" and the first dependency conflict is resolved. However the second issue is still present when i try to add this migration:
dotnet ef migrations add AddSqlLocalization --context LocalizationModelContext
Any ideas? :8ball:

Resolved :godmode:
I had a mixture of RC1, beta and RC2 dependencies listed in project.json. Just removed all version identifiers and replaced them with 1.0.0-*. After that a package restore and voila, works like a charm :game_die:

Hi @inexuscore
great, if you have any improvements or suggestions of how to improve this, let me know.
Thanks and greetings Damien

@damienbod Greetings. Sure thing, I'm tinkering with i18n in ASP.NET Core and your package. I'll keep contact :tada:


Using Pandas for data analysis in Python by Tiffany Timbers

Details
Pandas is an open source library providing high-performance, easy-to-use data structures and data analysis tools for the Python programming language.
Where: Simon Fraser University, Burnaby Campus, Library Research Commons
When: 11:30 am - 12:30 pm, Monday, November 30, 2015
Prerequisite knowledge: Entry level Python
Dependencies:  Python 3 (or higher) and Pandas library
Etherpad:

Would love to attend, but I'll be away that day teaching a visualization workshop in Winnipeg. Any chance we could move this to a later date in December?

Sorry, we already have this scheduled, and so will be holding it as scheduled. But, we can definitely do another variation of this lesson again in the near future. We will also be screen casting this session if you want to watch it remotely. The link should be available above in the issue shortly.


Question - can localStorage store a blob

Since scratchpad is down, i am requesting this question. Can localStorage store a blob ?

From the docs:

The localStorage is only meant to store relatively short strings. To store larger amounts of data it is recommended to use the Cordova FileSystem plugin.


SEO - Indexing PDF documents

Related to this issue on open-raadsinformatie.
In order to make ori documents finable in external weg search engines (google / bing), we need to make sure that:

Documents have a view on their own URL (id.openraadsinformatie currently only returns data representations, not HTML)
Rendered documents result in valid HTML (I believe this is already the case, since this is what react-pdf does well)
or... Find some trick to make sure the current resource sidebar viewer is parsed by google's crawler?

Since this is probably quite a bit of work, I don't expect to fix this myself. Any help is very welcome!

Indexing can be improved by using/providing sitemaps, which list the URLs to the documents


Any chance of a release with Amazing Print?

I use Semantic Logger in all my projects, and absolutely love it.
I was just wondering if there's going to be a release soon with Amazing Print included? I see the semantic_logger was released but I don't see a rails_semantic_logger release. The deprecation messages are getting a bit annoying.
Thanks

I don’t believe Rails Semantic Logger needs any changes to use Amazing Print.
Upgrade Semantic Logger and replace awesome_print with amazing_print in the Gemfile.

Ah great, thanks for the help. I'll close the issue.


We should add a cache to naviDimension.all

We should add a cache to naviDimension.all
Originally posted by @kevinhinterlong in https://github.com/yavin-dev/framework/pull/1495#discussion_r728144360

Resolved by https://github.com/yavin-dev/framework/pull/1566


Easily create attachments to notes

Please Select if your Request is Either something new or an Enhancement

[ ] Enhancement of an existing Feature.
[x] Request of a new feature.

Please select the area your request applys to. (Multiple selections are Possible)

[ ] Onboard. Initial vault setup and import/export pods
[x] Create. Note creation, lookup, snippets and templates
[ ] Retrieve. Backlinks, references, graph view
[ ] Structure. Refactoring, multi-vault and schemas
[ ] Publish. Sharing your repo with the world
[ ] Misc (Choose this if your not sure)

Is your feature request related to a problem? Please describe
When writing literature notes I often have a PDF of the article in question, sometimes I have even annotated it directly. It would be very useful to have a simple way to attach the file to my note.
Describe the solution you'd like
My ideal scenario would be a Dendron: Create attachment command, which would open a file selector. I choose the file I want to attach, and Dendron copies it to the assets folder. In doing so the name would be converted to kebab-case with all non-alphanumeric characters removed and have the date and time pre-pended.
Rather than inserting a link directly into the note (one option, indeed), perhaps there could be an attachments: field in the YAML front matter, allowing multiple attachments to be displayed together in a distinctively styled way in the preview. For example icons representing the mime-types of the attachments could be used.
It is essential that such attachments be easily openable in suitable external applications by directly clicking in the preview pane (not currently possible).
Describe alternatives you've considered
I have tried manually copying PDFs into the assets folder and then manually adding links to the note. However, neither markdown:
[Local PDF](assets/example.pdf)

nor HTML
Local PDF

generate a link in the preview which can actually open the PDF. Similarly cmd-clicking the link in the editor also fails to open the PDF. The only way to open it from inside VS Code is to right-click the file in the VS Code file explorer, select “Reveal in Finder” and then open the file from the Finder.

Duplicate of #575. This has good info though which we should take into account when implementing the command.


Copy binstar packages from rsignell to ioos

It's silly to have the ioos system-test binstar packages at rsignell instead of at ioos.    @srossross, can you please copy everything from binstar/rsignell to binstar/ioos?

@jkupiec Rich and I implement a system using travis-ci and AppVeyor that builds and uploads the packages in IOOS/conda-recipes.  The builds are working  for Linux and windows, MacOS will be available soon.
PRs to https://github.com/ioos/conda-recipes will trigger a new build, but the upload only occurs when the PR is merged.  The packages are hosted in the IOOS binstar channel,
https://binstar.org/IOOS/
I just tested the following commands (on Linux):
conda config --add channels ioos -f

cat >req.txt <<EOL
iris
pyoos
pandas
folium
rdflib
geojson
requests
prettyplotlib
ipython-notebook
libnetcdf=<IP_ADDRESS>=1
EOL

ENV_NAME=system-test
conda create --yes -n $ENV_NAME --file req.txt python=2.7
source activate system-test

This creates a conda virtual environment that is able to run all the notebooks in system-test.
PS: Make sure that ioos is the only channel in your .condarc, or other package version might get installed.


TGA loader

Status:

done

Tell me when done and tested.

@devshgraphicsprogramming done and tested, but I had to insert some code into some swtich cases, it looks awful, so I will do a small clean code refactor tomorrow and then it will be ready to merge

@devshgraphicsprogramming convertColor needed patching with default values on certain texel, but nut sure about alpha. Afaik there are some rules defining how to put default alpha values when inteeger or normalized etc

Afaik there are some rules defining how to put default alpha values when inteeger or normalized etc

Default value is (0,0,0,1) whatever channel is not defined, you take from that default vector.

Are we done?


Case details

Description of change
add case details form as specified in figma and prototype
Link to relevant ticket
Notes for reviewer
still a wip - so expect more changes
Screenshots of changes (if applicable)
Before changes:
After changes:
How to manually test the feature

merged  case_details into main


Launch file for "full scan" (multiScan)

How do I have to adjust the launch file so that the sensor gives me a "full scan" or "fullframe" with all 16 layers?
I also want to query which layer the current scan is from.I tried setting "custom_pointclouds" to "cloud_all_fields_fullframe":

Unfortunately, this did not work in with "SickScanApiRegisterCartesianPointCloudMsg", or rather, the callback is never called.
With the setting , the callback of "SickScanApiRegisterCartesianPointCloudMsg" is only called once.
Only the setting  works well, but I don't want to split the scans into segments, but into layers.

Thanks for your feedback. I assume the customer is using the sick_scan_xd API without ROS.
There is no need to adjust the launch file to get the full frame point clouds with all layers. The callback registered with "SickScanApiRegisterCartesianPointCloudMsg" is called for the segments and for the full frame point clouds. The segment_idx of the message is -1 for fullframe point clouds (or the segment index otherwise). To process only the fullframe point clouds, just use if (msg->segment_idx < 0) { /* msg contains the fullframe point cloud */ } and ignore all other messages.
Note that custom point clouds are only supported with ROS. The API only provides the cartesian point clouds with fields (x,y,z,intensity) and the polar point clouds with fields (range,azimuth,elvation,intensity).
Each scan (full frame or segmented) contains the scan points of different layers. The layer of a scan point can be derived from the elevation angle if necessary.
If the callback is not called (or is called only once), the error is probably different. A common error is a wrong or empty udp_receiver_ip parameter, which must be the IP address of the PC running sick_scan_xd.
It is recommended to use SOPAS Air to check the settings, i.e. open the lidar IP address in a browser. If the point cloud is visible in SOPAS Air, the IP addresses are valid. Use the arguments hostname:=<lidar_ip_address> udp_receiver_ip:=<pc_ip_address> to run sick_scan_xd. See usage example and picoScan/multiScan configuration for examples. Please post a full logfile or screenshots of the sick_scan_xd console messages if the problem persists.

I am using the sick_scan_xd_console_log.txtAPI for Windows without ROS.
if (msg->segment_idx < 0) { /* msg contains the fullframe point cloud */ } is only called once or sometimes twice at the beginning. I still recieve the segment msg with if (msg->segment_idx >= 0) but the fullframe is not called anymore.
See console log:
sick_scan_xd_console_log.txt


Landing Page - YouTube Embed (above Goals)

Use for reference: https://dev.to/bravemaster619/simplest-way-to-embed-a-youtube-video-in-your-react-app-3bk2