docker start failed with 404 page not found

I test the following commands,
$ weave launch --no-dns

$ eval $(weave env)

then
$ docker run -it ubuntu:16.04 bash

docker: Error response from daemon: unable to register f8fe8aea2f12634faa6676b6605e124c678067410c47063f41bff61a4ff3d841 with weaveDNS: 404 Not Found: 404 page not found
Error: failed to start containers

Versions:
$ weave version
2.0.1

$ docker version
Client:
 Version:      17.06.0-ce
 API version:  1.30
 Go version:   go1.8.3
 Git commit:   02c1d87
 Built:        Fri Jun 23 21:22:33 2017
 OS/Arch:      linux/amd64

Server:
 Version:      17.06.0-ce
 API version:  1.30 (minimum version 1.12)
 Go version:   go1.8.3
 Git commit:   02c1d87
 Built:        Fri Jun 23 21:23:51 2017
 OS/Arch:      linux/amd64
 Experimental: false

$ uname -a
Linux  4.11.8-200.fc25.x86_64 #1 SMP Thu Jun 29 16:13:56 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

Logs:
$ docker logs weave

INFO: 2017/07/10 03:04:09.969608 GET /_ping
INFO: 2017/07/10 03:04:09.970265 GET /v1.30/images/json
INFO: 2017/07/10 03:04:22.507601 GET /_ping
INFO: 2017/07/10 03:04:22.514763 POST /v1.30/containers/create
INFO: 2017/07/10 03:04:22.514932 Creating container with WEAVE_CIDR ""
INFO: 2017/07/10 03:04:25.276593 POST /v1.30/containers/f8fe8aea2f12634faa6676b6605e124c678067410c47063f41bff61a4ff3d841/attach?stderr=1&stdin=1&stdout=1&stream=1
INFO: 2017/07/10 03:04:25.279439 POST /v1.30/containers/f8fe8aea2f12634faa6676b6605e124c678067410c47063f41bff61a4ff3d841/wait?condition=next-exit
INFO: 2017/07/10 03:04:25.281895 POST /v1.30/containers/f8fe8aea2f12634faa6676b6605e124c678067410c47063f41bff61a4ff3d841/start
INFO: 2017/07/10 03:04:25.957226 Attaching container f8fe8aea2f12634faa6676b6605e124c678067410c47063f41bff61a4ff3d841 with WEAVE_CIDR "" to weave network
INFO: 2017/07/10 03:04:26.052918 Discovered local MAC 7a:db:b4:aa:06:69
WARN: 2017/07/10 03:04:26.121546 read unix /var/run/weave/weave.sock->@: use of closed network connection
WARN: 2017/07/10 03:04:27.116142 Error intercepting response: unable to register f8fe8aea2f12634faa6676b6605e124c678067410c47063f41bff61a4ff3d841 with weaveDNS: 404 Not Found: 404 page not found
: 404 Not Found: 404 page not found

Hi @jacknlliu,
Many thanks for raising this issue and the detailed steps & symptoms
I confirm I can definitely reproduce the issue :+1:

@jacknlliu, just to better understand your use case, and advise in case there is a workaround:
Why do you need to disable the DNS at the moment?

@marccarre yeah, I disabled DNS because I also use weave on a ARM device which will show the following error if not disable DNS,
FATA: 2017/07/09 16:18:27.336931 Unable to start dns server: listen udp <IP_ADDRESS>:53: bind: address already in use

and clock skew issue is also confusing.

@jacknlliu I had the exact same issues, as I don't want to use weave-dns. When I tried to launch docker container using the weave socket I would get the same 404 error for weaveDNS.
After reading the docs again, the solution was simple though not immediate obvious:

To disable an application container's use of weaveDNS, add the --without-dns option to weave launch. To disable weaveDNS itself, launch weave with the --no-dns option.

So you actually need to apply both options to launch weave, in order do disable the DNS server (which is useful, if you have another DNS server running) and make the containers not use this DNS server:
$ weave launch --no-dns --without-dns

Cheers 😄

Thanks for your reply, I also think that DNS server is not needed for my use case.

Fixed by #3088


Add MultiDatePicker

Closes #74
Note that this element isn't a form control, since it has a collection of values, which I think is more than can reasonably be encoded as a string.
<multi-date-picker value-binding="dates" start="2023-01-01" end="2023-01-31">
  <text>Dates</text>
</multi-date-picker>

https://user-images.githubusercontent.com/7091588/223870309-7d1fad3d-219d-4c84-8ae5-66d90c82b99c.mp4

In your example you have <text>Dates</text> embedded but I don't see that on the demo video. Does it get hidden?


When I open a pop-up page in the window, the main web view is no longer available.

[x] I have read the Getting Started section
[x] I have already searched for the same problem

Environment

Technology
Version

Flutter version
3.24.3

Plugin version
6.1.1

Android version

iOS version

macOS version

Xcode version

Google Chrome version

windows
10

Device information:
Description
Expected behavior:
Current behavior:
Steps to reproduce
Windows app has been built.
Click the link that opens to a new window.
Return to the previous window.
I can't do anything.
Click, type in the input box, etc
I build Android apps with the same code.
The above error does not occur.
Error when building Winzow app.

    Expanded(
      child: InAppWebView(
        initialUrlRequest: URLRequest(url: WebUri("https://example.com")),
        initialSettings: InAppWebViewSettings(
          supportMultipleWindows: true,
        ),
        onWebViewCreated: (controller) {
          _controllerTEST = controller;
          javaScriptHandlerNaver(ndx);
        },
        onLoadStart: (controller, url) {
          debugPrint("Started loading: $url");
        },
        onLoadStop: (controller, url) async {
          debugPrint("Finished loading: $url");
        },
        onProgressChanged: (controller, progress) {
          debugPrint("Progress: $progress%");
        },
        onCreateWindow: (controller, createWindowRequest) async {
          _openPopup(createWindowRequest.request);
          return true;
        },
      ),
    ),

The _controllerTEST will fail after the following code is executed by the pop-up page.
        onCreateWindow: (controller, createWindowRequest) async {
          _openPopup(createWindowRequest.request);
          return true;
        },

If I build with android it works fine.
But if I build to windows it doesn't work.

This
Than that
Then

Images
Stacktrace/Logcat

yes and popup is not opening seperately

@pichillilorenzo  There is issue in windows platform


Connect button behavior with available connectors is incorrect

Describe the bug
The available methods from starknet react is not working well.
To Reproduce
Steps to reproduce the behavior:

Install only one wallet
Click on connect button in portfolio

Behavior
Expected behavior
If a wallet is available, open the wallet to connect the dapp, if not, open the wallet install page
Actual behavior
If the wallet is not available, nothing happens
Frequency:
All the time
Additional context
Use the available method of a connector instead of the available method from starknet react

Private Zenhub Image
Private Zenhub Image


[FEATURE] Allow for disabling "background" class for specific windows

Description of the requested feature
Currently Eww automatically applies the "background" CSS class to widgets. The problem with such a system is that when somebody is using a GTK style such as Catppuccin which overides the Background class in the gtk.css, the usual unset doesn't work as what is set inside of the gtk.css overides what is given which means you cannot achieve transparency without setting that class inside of the GTK.css to (0,0,0,0) or removing the gtk.css as a whole.The problem with this solution is that removing the gtk.css means other apps don't use the theme, but keeping it at 0,0,0,0 means any app that relies on the background class such as libreoffice it's popups will be transparent which is annoying.
So I am proposing to allow for the disabling of the "background" default given class for windows which would allow people to still use themes such as Catppuccin GTK, but still be able to achieve transparency inside of eww.
Proposed configuration syntax
(defwindow bar
  :stacking "bg"
  :wm-ignore true
  :monitor 0
  :namespace "bar"
  :geometry (geometry
    :x "0%"
    :y "0%"
    :width "100%"
    :height "20px"
    :anchor "top center"
  )
  :exclusive true
  (bar)
)

This is my current eww bar config section, I would propose adding the :nodefaultclass option which will remove all default given classes.
Additional context
No response

Did some more testing and I can confirm that it appears that gtk.css overides

Inline Style
Added Style via eww.scss

I also tried setting the .background class in eww.scss to transparent and that didn't work either

@elkowar Thanks for looking into it, if it's not possible that's also fine. What is also interesting is looking at other non-catppuccin GTK themes they don't use the .background class, which confuses me because how do they in that case style stuff?
And what is double weird is in theory unset: *; should just remove all gtk css configuration so that's the most confusing. It's like it overides that setting which it shouldn't.

@elkowar So after doing more testing I tried setting the catppuccin theme via gnome-tweaks... and it worked. I got no clue why that works while setting it manual doesn't. The only diffrence I see is in the gtk settings.ini darkmode is set to true. Why this works I do not know but if you want you can close this issue(I will not be closing this issue incase you think being able to disable the background class is handy/possible.


[release-v1.67] Unpin version for upgrade tests

This reverts commit f937eb88d13b671db50b3c1bef73122922cd82b5.
How to categorize this PR?

/area testing
/kind cleanup
What this PR does / why we need it:
This PR unpins version for upgrade tests because<EMAIL_ADDRESS>is released.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Release note:

NONE

/lgtm
/approve


Allow exclusion of optional dependencies

Great plugin!
Would it be possible to release 1.0.7 if this pull request is accepted?

Hey @shantstepanian! :wave:
Welcome to the Apereo community!
Thanks for putting this together, having the ability to filter optional dependencies is a feature that could be a great fit for this plugin. :+1:
Next Step: Could you sign the Apereo ICLA? https://www.apereo.org/licensing/agreements/icla

Signed via the online form


follow up to PR #940 with PEP8 formatting changes

Issue # 581
Description of changes:
Quick Follow up to PR #940 with PEP8 formatting changes.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Job PR-944-1 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-944/1/index.html


y21ga 0.1.2 issues and new tests

The command gzip is not working, but this even in previous version, I tried to launch it and it says:
gzip: applet not found

Streams miss audio, video works both with direct player (i.e. mplayer) and integrated with HA. I hope it'll come back because if I'm not wrong at the beginning it was working.

MQTT sensor works integrated with HA.
Looks quite stable, good release! :) :+1:

Forgot, I used the upgrade firmware feature on the Maintenance page and it worked :+1:

Forgot, I used the upgrade firmware feature on the Maintenance page and it worked 👍

coming from 0.1.1?

coming from 0.1.1?

I was on the 0.1.0 without boot loop (partial upgrade, only the folder yi-hack).

In general do you guys activate the sd swap feature?

Yes

cool - so even from macgyver version OTA update to 0.1.2 ,)
this hack is getting pretty pro 👍
let me repeat at this point: fantastic job remote reverse engineering this cam and thank you so much @roleoroleo !

I agree, it runs very nice, smoothly with Home Assistant too!
Great job @roleoroleo !

Works great 😊 I made the update with ota. Thanks @roleoroleo

Guys please lets test the following on 0.1.2 and give feedback here:
rtsp high res - yes but with more artefacts in low light than before. gets worse the longer the stream runs.
rtsp low res - not tested yet
rtsp audio - no
snapshot high res - yes
snapshot low res  yes
status page - yes
hostname - updates
timezone - works after giving the string
onvif - not tested yet
ftp upload - not tested yet
mp4 management in "Motion Events" page - not tested completely but seems to work
web snapshot - yes
ptz (only R30 model) - n/a
load/save configuration - save yes. load tbd.

@pep4n
Try to run rRTSPServer manually with debug option.
Check if there are errors.

Ok, I guess I would need some help running this.
Connect via SSH or telnet?

Connect via SSH:
. /tmp/sd/yi-hack/script/env.sh
killall rRTSPServer
rRTSPServer -r both -d

Another minor issue is that the check about free space on SD card is not working.
I set up for 30% free space and now it is at 15%.

rtsp high res - tested via VLC: yes but with more artefacts in low light than before. gets worse the longer the stream runs.  see screenshot attached. also probably around 2fps. need to compare to daylight though.

Mine is much better on low light that the quality of image you posted.

Connect via SSH:
. /tmp/sd/yi-hack/script/env.sh
killall rRTSPServer
rRTSPServer -r both -d

putty can't connect: access denied.
tried with set user and password and also removing credentials doesnt help...

Failed to create RTSP server: bind() error (port number: 554): Address in use

After killing rRTSPServer you have to wait 20-30 seconds, the system doesn't release the socket immediately.

Failed to create RTSP server: bind() error (port number: 554): Address in use

After killing rRTSPServer you have to wait 20-30 seconds, the system doesn't release the socket immediately.

There is the watchdog that restart the server, so if you wait it'll start again.
Try this:
. /tmp/sd/yi-hack/script/env.sh
ps| grep rRTSPServer | grep -v grep | cut -d ' ' -f3 | xargs kill ; rRTSPServer -r both -d
You should have a queue of:
frame_len: 750 - cb_current->size: 49152
frame_len: 1530 - cb_current->size: 196608
To interrupt use Ctrl+C

@pep4n
Try this binary:
rRTSPServer.gz
I increased verbosity.

There is the watchdog that restart the server, so if you wait it'll start again.

Kill wd_rtsp.sh too.

There is the watchdog that restart the server, so if you wait it'll start again.

Kill wd_rtsp.sh too.

If you don't kill the watchdog, the RSTP server will restart again without need to reboot or manually start the watchdog :)
One tool that would be useful in this case would be 'tee' , to see and log the output. Tried with busybox but it isn't included.

@pep4n
Try this binary:
rRTSPServer.gz
I increased verbosity.

again sorry guys, but how can I test this?
:)

@pep4n
Try this binary:
rRTSPServer.gz
I increased verbosity.

again sorry guys, but how can I test this?
:)

Are you familiar with Linux or Windows ?

just a little little bit and yes a lot.
guess what goes for linux ,)

Copy the file using ftp or scp client to /tmp/sd/yi-hack/bin (Filezilla or WinSCP are ok).
Connect with putty (user root without password) and run the following commands:
. /tmp/sd/yi-hack/script/env.sh
killall rRTSPServer
cd /tmp/sd/yi-hack/bin
mv rRTSPServer rRTSPServer.ori
gzip -d rRTSPServer.gz
rRTSPServer -r both -d

The 1st command load the envornment variables for the current shell.
The 2nd command terminates the process rRTSPServer.
The last command run the new rRTSPServer.

awesome - thanks. will do and return with feeback.
or failure ,)

I could update the rRTSPServer.
Now I should do the "rRTSPServer -r both -d" again and post output, right?

So you moved the old binary and substituted it with the new one, then you can run this line:
ps| grep rRTSPServer | grep -v grep | cut -d ' ' -f3 | xargs kill ; rRTSPServer -r both -d
and see what is the output.
If you want to save the output, run this:
ps| grep rRTSPServer | grep -v grep | cut -d ' ' -f3 | xargs kill ; rRTSPServer -r both -d 2> rtsp.log
and share the file rtsp.log

I get the following when trying to run this:
xargs: not found

I get the following when trying to run this:
xargs: not found

Do:
cp /tmp/sd/yi-hack/bin/gzip /tmp/sd/yi-hack/bin/xargs
then try again.

hmm still.

root@yi-cam:~# cp /tmp/sd/yi-hack/bin/gzip /tmp/sd/yi-hack/bin/xargs

root@yi-cam:~# ps| grep rRTSPServer | grep -v grep | cut -d ' '-f3 | xargs kill ; rRTSPServer -r both -d 2> rtsp.log
-ash: xargs: not found

root@yi-cam:~#

Have you:
. /tmp/sd/yi-hack/script/env.sh
If still not working, reboot the cam then it'll work.

aha seems we're one step further:
kill: you need to specify whom to kill
I like this one :D

Remember to source the env.
First line:

. /tmp/sd/yi-hack/script/env.sh
killall rRTSPServer
cd /tmp/sd/yi-hack/bin
mv rRTSPServer rRTSPServer.ori
gzip -d rRTSPServer.gz
rRTSPServer -r both -d

I run this line by line right?

Only env.

Ok try this:
. /tmp/sd/yi-hack/script/env.sh
killall wd_rtsp.sh
killall rRTSPServer
cd /tmp/sd/yi-hack/bin
mv rRTSPServer rRTSPServer.ori
gzip -d rRTSPServer.gz
rRTSPServer -r both -d

Ok try this:
. /tmp/sd/yi-hack/script/env.sh
killall wd_rtsp.sh
killall rRTSPServer
cd /tmp/sd/yi-hack/bin
mv rRTSPServer rRTSPServer.ori
gzip -d rRTSPServer.gz
rRTSPServer -r both -d

We will never see the light ! :-D GZIP isn't working but okay, maybe @pep4n can transfer it uncompressed :+1:

I improved the command, try this:
ps | grep rRTSPServer | grep -v grep | awk '{print $1}' | xargs kill ; rRTSPServer -r both -d 2> rtsp.log
This time should work.

Another minor issue found, we miss the sort command so the ftp feature cannot work: I have some ftppush.sh hanging.
So, till now, have to fix gzip and sort.

Ok.

The rtsp server isn't perfect, today I enabled my automation that record a video when something happen (now camera motion mqtt sensor) using the camera.record feature of HA and sometime the video is readable but sometime it isn't.
When it is not readable I found this exception in the HA log:
2020-11-01 17:40:37 ERROR (recorder_save_worker) [libav.mp4] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 13434267 >= -37381920 2020-11-01 17:40:37 ERROR (recorder_save_worker) [root] Uncaught thread exception Traceback (most recent call last):   File "/usr/local/lib/python3.8/threading.py", line 932, in _bootstrap_inner     self.run()   File "/usr/local/lib/python3.8/threading.py", line 870, in run     self._target(*self._args, **self._kwargs)   File "/usr/src/homeassistant/homeassistant/components/stream/recorder.py", line 51, in recorder_save_worker     output.mux(packet)   File "av/container/output.pyx", line 204, in av.container.output.OutputContainer.mux   File "av/container/output.pyx", line 227, in av.container.output.OutputContainer.mux_one   File "av/container/core.pyx", line 257, in av.container.core.Container.err_check   File "av/error.pyx", line 336, in av.error.err_check av.error.ValueError: [Errno 22] Invalid argument: '/media/surveillance/LivingRoom_camera.mp4'; last error log: [mp4] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 13434267 >= -37381920

Another minor issue found, we miss the sort command so the ftp feature cannot work: I have some ftppush.sh hanging.
So, till now, have to fix gzip and sort.

https://github.com/roleoroleo/yi-hack-Allwinner-v2/commit/5fe19b4113e57e8f07440f8034efa11fb184244d

For FTP push to work, missing nc and ftpput too.
Then a small change (look at the diff) to the ftppush.sh script, starting at row 159:
      if [ "${FTP_DIR_TREE}" == "yes" ] ; then                                                                                if ( ! ftpput -u "${FTP_USERNAME}" -p "${FTP_PASSWORD}" "${FTP_HOST}" "${FTP_DIR}${FTP_DIR_HOUR}$(lbasename "${UTF_FULLFN}")" "${UTF_FULLFN}" ); then                            logAdd "[ERROR] uploadToFtp: ftpput FAILED."                                                                                return 1                                                                                fi                                                                                else                                                                                if ( ! ftpput -u "${FTP_USERNAME}" -p "${FTP_PASSWORD}" "${FTP_HOST}" "${FTP_DIR}$(lbasename "${UTF_FULLFN}")" "${UTF_FULLFN}" ); then                                           logAdd "[ERROR] uploadToFtp: ftpput FAILED."                                                                                return 1                                                                                fi                                                                                fi
A / was breaking the ftpput. Replaced echo with logAdd.

Done.
Thank you.


[Enhancement] add nap_sleep() to handle sleep a large portion of time(#29689)

respect AWS_EC2_METADATA_DISABLED if already set in env
BE binary can stop with 10 seconds with this change nap_sleep() change and also AWS_EC2_METADATA_DISABLED=true in non-ec2 env

(cherry picked from commit ef6c33877b8198faf1756260a240a58dbcdfb02c)
Fixes #issue
What type of PR is this:

[ ] BugFix
[ ] Feature
[X] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Does this PR entail a change in behavior?

[ ] Yes, this PR will result in a change in behavior.
[X] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[ ] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[X] I have checked the version labels which the pr will be auto-backported to the target branch

[ ] 3.1
[ ] 3.0
[ ] 2.5
[ ] 2.4

[FE Incremental Coverage Report]
:heart_eyes: pass : 0 / 0 (0%)

[BE Incremental Coverage Report]
:disappointed: fail : 3 / 7 (42.86%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
src/agent/task_worker_pool.cpp
0
1
00.00%
[746]

:large_blue_circle:
src/runtime/profile_report_worker.cpp
0
1
00.00%
[123]

:large_blue_circle:
src/common/daemon.cpp
0
1
00.00%
[222]

:large_blue_circle:
src/service/service_be/starrocks_be.cpp
0
1
00.00%
[82]

:large_blue_circle:
src/runtime/stream_load/transaction_mgr.cpp
1
1
100.00%
[]

:large_blue_circle:
src/runtime/broker_mgr.cpp
1
1
100.00%
[]

:large_blue_circle:
src/runtime/fragment_mgr.cpp
1
1
100.00%
[]


Fix for latest DANDI release

Latest DANDI release (1 hour ago) broke tests due to an altered import path
This should fix it

Pin to be less than maybe?

Yeah, just to get the CI passing again to unblock other things
It looks like more changed than just that, investigation into why taking a little while


kubectl-kcp Command to Unsync a Workload Cluster

Is your feature request related to a problem? Please describe.
The kubectl kcp workload sync command makes it easy to configure a workload cluster on kcp, and create a manifest to deploy the syncer on a workload cluster.
Tearing down a workload cluster, however, requires the following manual steps on the kcp side:

Delete the WorkloadCluster
Delete the associated service account
Delete the associated clusterrolebinding

Describe the solution you'd like
An inverse command - kubectl kcp workload unsync - which removes the WorkloadCluster and associated RBAC.
Describe alternatives you've considered
Keep the status quo, but document the steps needed to remove a workload cluster.
Additional context
N/A

Related: #948 cc @kasturinarra

Will this also remove the syncer pod and namespace/project from the workload cluster?

/transfer-issue contrib-tmc


Create PSuU custom run nb

similar to single custom run
pick first set of visualizations from other nbs
Phase evolution (line) from psuu test

Clear to me.


Add "title should not be translated" checkbox

Motivation
More an more municipalities use machine translations to translate their content. Some page titles, e.g. "Cafe Tür an Tür" or "Sprachschule Arche Noah" should not be translated. For the content they have the option to choose "do not translate text" because it is embed in TinyMCE. For the title field we have no TinyMCE and implementing it there as well would be overkill.
Proposed Solution
See the attached screenshot. A checkbox should be available in the "Translation"-block which can be checked if the complete title should become a "do not translate"-tag. So the user can choose if the whole title becomes translated or not. Translate only parts of the title is not possible.
Alternatives
You could also add a do not translate Icon next (right) to the title which can be "activated". This would cost less place.

Translation memory could be a more robust solution to this, in case we decide to add it.

@david-venhoff how would the translation memory apply for newly translated pages where the title should not be translated?
I added prio to this bcs of POIs where titles often should not be translated but sometimes are.

how would the translation memory apply for newly translated pages where the title should not be translated?

It is a while ago since I wrote that comment, so unfortunately I don't fully remember. Though I think what would work is if we have a storage of phrases that should not be translated (For example "Cafe Tür an Tür"). Then any translation title would automatically get a do-not-translate tag around these phrases.
The advantage would be that automatic translations of titles would still work, and users would not have to manually decide that a title should not be translated, they'd just need to maintain a list of words that should not be translated.

But that would definitely be a higher effort to implement

The advantage would be that automatic translations of titles would still work, and users would not have to manually decide that a title should not be translated, they'd just need to maintain a list of words that should not be translated.

I'm honstely not sure which would be easier - I think having to maintain a list is also a lot of work - and for municipalities probably more difficult than simply checking or unchecking a box....
So maybe for a start we can just implement the checkbox?
I'll add UI/UX since I think it makes sense for @nikolahoff to think about which the best way to have this checkbox (2 examples from Daniel above), would be.


Quantization aware training help

Thanks a lot for this awesome repro.
I have a question regarding quantization aware training. I am new in this area and want to know if you can share example to do quantization aware training for MobileNet or Efficientnet.

All I learned is from TF tutorial Quantization aware training in Keras example, and it should be easy but not tested. Just adding quantize_model after basic_model being created should work.
import tensorflow_model_optimization as tfmot
quantize_model = tfmot.quantization.keras.quantize_model
...
from keras_cv_attention_models import efficientnet
basic_model = efficientnet.EfficientNetV2B0(input_shape=(112, 112, 3), num_classes=0)
basic_model = models.buildin_models(basic_model, dropout=0, emb_shape=512, output_layer='GDC', bn_epsilon=1e-4, bn_momentum=0.9, scale=True, use_bias=False)
basic_model = models.add_l2_regularizer_2_model(basic_model, weight_decay=5e-4, apply_to_batch_normal=False)

# q_aware stands for for quantization aware.
basic_model = quantize_model(basic_model)

tt = train.Train(..., basic_model=basic_model, model=None, ...)
...

Anyway, quantization not working well for face recognition in my earlier tests. Say a basic_model with 256 embedding shape, after quantization, each value can only be [0, 256], means it can be only representing 256 * 256 == 65536 different embeddings, also means only 65536 different faces, which is too small.

@leondgarse Thanks a lot.

@PR451 you can also try post training quantization when you already have the pre-trained model, in my experience it worked pretty well to reduce model size and obtain better inference times (in my case I obtained a model 3x faster than the non-quantized).
Make sure you have the tensorflow model optimization package:
!pip install -q tensorflow-model-optimization

And after you have the pre-trained model:
import tensorflow as tf
converter = tf.lite.TFLiteConverter.from_keras_model(model)
converter.optimizations = [tf.lite.Optimize.DEFAULT]
tflite_quant_model = converter.convert()

# Saving corresponding quantized model
with open('quantized_model.tflite', 'wb') as f:
  f.write(tflite_quant_model)

Ya, just QAT can reach a better accuracy in most cases. If you need the tflite and PTQ data, we have a bunch tests here How to speed up inference on a quantized model #44, comparing float16 / uint8 model size and inference speed on x86 / arm using efficientnetv2_s.

@leondgarse I tried your above code
`import tensorflow_model_optimization as tfmot
quantize_model = tfmot.quantization.keras.quantize_model
...
basic_model = models.buildin_models("mobilenet", dropout=0.4, emb_shape=512, output_layer='GDC', add_pointwise_conv=True, scale=False, use_bias=True)
q_aware stands for for quantization aware.
basic_model = quantize_model(basic_model)
tt = train.Train(..., basic_model=basic_model, model=None, ...)`
But I am getting following error
RuntimeError: Layer pre_embedding:<class 'keras.layers.normalization.batch_normalization.BatchNormalization'> is not supported. You can quantize this layer by passing a tfmot.quantization.keras.QuantizeConfiginstance to thequantize_annotate_layer API. I don't know how to quantize the layers using tfmot.quantization.keras.QuantizeConfig.
Have you faced this before?

Yes, you are right, sorry I didn't take some tests ealier. The reason is that previously appling BatchNormalization on a 2D tensor. Should be fixed now.
import tensorflow as tf
import tensorflow_model_optimization as tfmot
from tensorflow import keras
import models

basic_model = models.buildin_models("mobilenet", dropout=0.4, emb_shape=512, output_layer='GDC', add_pointwise_conv=True, use_bias=True, scale=False, weights=None)
q_aware_model = tfmot.quantization.keras.quantize_model(basic_model)
mm = keras.models.Model(q_aware_model.inputs[0], models.NormDense(10)(q_aware_model.outputs[0]))

xx, yy = tf.random.uniform([1000, 112, 112, 3]), tf.one_hot(tf.random.uniform([1000], 0, 10, dtype='int64'), 10)
mm.compile(optimizer='adam', loss=keras.losses.categorical_crossentropy, metrics=['accuracy'])
mm.fit(xx, yy, epochs=2)
# Epoch 1/2
# 32/32 [==============================] - 31s 198ms/step - loss: 7.1859 - accuracy: 0.1050
# Epoch 2/2
# 32/32 [==============================] - 6s 193ms/step - loss: 7.2841 - accuracy: 0.0930

@leondgarse Thanks a lot for quick reply. I was able to start the training. Closing the issue.


Chainlit debugging best practices?

Hi there, thanks very much for sharing this library, it looks great!
I'm trying out the PDF-QA example with a local LLM, but I keep getting:
ERROR: The prompt size exceeds the context window size and cannot be processed.. I'm trying to identify/edit the prompt, but I can't find it?
Not sure if you can help with this specific question or chainlit debugging best practices more generally?
Thanks!

Hey, what is the context window size of your local LLM? Make sure that the max_tokens_limit parameter is not exceeding it.

Thanks for the info and quick response.
So I also get an error of LLaMA ERROR: The prompt is2906tokens and the context window is2048!, so I tried changing the setting to 2048 but unfortunately I still seem to be getting errors.
I've added my full changes to https://github.com/Chainlit/cookbook/pull/6/files in case you notice something I'm doing wrong (I'm trying to use gpt4all for the local chat model, but I'm open to using any local model if you have a better example).
Many thanks for any help!

Maybe you could change the chunk size int the text splitter and the k parameter here to limit the number of documents returned by a search. Your context window is 2048 tokens so maybe a chunk size of 500 and k=2?

This is the default prompt for this chain, you can tweak it if you need to.

Thanks, sorry do you have any useful links/example regarding how to change this?

Maybe this can help https://stackoverflow.com/questions/76240871/how-do-i-add-memory-to-retrievalqa-from-chain-type-or-how-do-i-add-a-custom-pr

how to debug llm when using chainlit?

We are going to release a new version of the prompt playground tomorrow which will help a lot for debugging


RFC: removing Lua support?

How about we remove Lua support from Gleam?
This is because of:

Complexity to install Gleam. Although installation is fairly easy, installing Lua and the message pack library are still extra steps.

Complexity to support Lua. To support a scripting language, I need to support serialization and deserialization between MsgPack and Lua in memory data row, meta data, etc. This makes adding new features, such as windowing, watermark, etc, more complicated.

Lua has several flavors. Impossible to support and test all of them. Currently it is already limited to only LuaJit. The pure Go interpreters for Lua do not work due to subtle details. And they are yet another flavor of Lua.

Lua's nil in the array is causing truncated rows.

Lua treat both []byte and string as string. Losing type information during SerDe.

If removing Lua,

Conceptually much simpler to add new Gleam features. Being an open source project, this is very important to move this project forward.

Conceptually much simpler to deploy.

No need for Go developers to learn Lua. Lua is simple, but hidden pitfalls are not obvious to beginners.

One way to write Gleam code. Multiple ways to do one thing is not Go style.

If removed lua,What is the difference with Glow?
I think you can split lua support to a new project, it maybe supported   by somebody who use it

Moved the existing branch that has lua support to:
https://github.com/chrislusf/gleamold


File lock on log files

Hi,
I have encountered an issue, possibly due to the way I want my setup to work, but maybe you can help solving it. As my plotter is a headless linux and really don't want to use that for this kind of interactive statistics, I want to move regularly the log files to my desktop and run your software for monitoring.
Now the issue is that Chia-Plot-Status puts a lock on the log files and SCP cannot update/sync with the changes. Would it be possible to only read the files and not lock them permanently? I am not a programmer and not really adept with .NET
Using 3703a751323a9fcbf2b13bd7a52a224f62e01428 commit

This comment should help: chia plot status preventing files from updating in syncthing #40

Perfect answer, thank you!


Will fit_generator circle input file?

I have very huge file of words which I want to convert to vectors and put them to learn online. As I read other issues the most "correct" way to do so is to use model.fit_generator. But I am in doubt will fit_generator circle my huge file by itself? And second question what to put  to samples_per_epoch to make fit_generator use all data from file?

Ok I should use while(1) in generator and use generator for validation set also. Thank you everyone for help.


[18.03] oraclejdk8psu: mark as insecure

Followup of #43842 (cc @srhb).
This is a sort port of 4d6f880 (#43811) to 18.03. The mentioned issues are not
being fixed in the release. The CPU release should be used instead.
Since someone might still need the PSU version it will just be marked as
insecure allowing the user to whitelist it, if required.
Acquiring the files required for testing this requires some Oracle Voodoo. Since we are only marking them as insecure (with a bit of indirection) this should be fine as is.

No attempt on aarch64-linux (full log)
The following builds were skipped because they don't evaluate on aarch64-linux: oraclejdk8psu
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnfree = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnfree = true; }
to ~/.config/nixpkgs/config.nix.

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: oraclejdk8psu
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnfree = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnfree = true; }
to ~/.config/nixpkgs/config.nix.

No attempt on x86_64-linux (full log)
The following builds were skipped because they don't evaluate on x86_64-linux: oraclejdk8psu
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnfree = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnfree = true; }
to ~/.config/nixpkgs/config.nix.


Order Depth displayed buggy when working with local backtester

1712044214.463666_a1dc682f-a3bb-4198-8576-08b7b436d26c.log
Hello there!
After utilizing a local backtester that also mimics the logs produced in the format needed for download I find that everything works fine except for the order depths displays. To reproduce the error you should just be able to upload the log, scroll a bit in time to the right (maybe two 20000 or so) and the order depths look like a mess!

I checked the order books that he trades on and they look fine. Also the logs look fine to me, but I also dont understand from which part of the log he takes that information.
Best,
Luka

Fixed in 5434d07086116893180273fbc1f514d484d7c248, thanks for reporting the issue and attaching a log file that reproduces it!
You may have a bug in your backtester though, I'm not sure whether it should be possible to have open bid and ask orders at the same price (see the STARFRUIT table below). I certainly don't remember seeing that in logs generated by Prosperity's submission environment:


Fix Axl Network Selection

To fix the readability of Network names in the global Deposit and Withdrawal (transfer-asset-select) modal.
Renamed SourceChain values from axelar API inputs -> a prettyName.
export type SourceChain =
  | "Aurora Testnet"
  | "Avalanche"
  | "Avalanche Fuji Testnet"
  | "Binance Smart Chain"
  | "BSC Testnet"
  | "Ethereum"
  | "Goerli Testnet"
  | "Fantom"
  | "Fantom Testnet"
  | "Moonbeam"
  | "Moonbase Alpha"
  | "Polygon"
  | "Mumbai";

There are now separate maps for axelar keys and ethereum chain IDs by SourceChain (reverse).
Added USDC transfers to/from Binance.
Frontier and Testnet environments now show a pretty Network Name in both modals, triggers Eth wallet to switch to correct network, and can detect when the correct network is selected.
Untested: whether transfers actually work.

Let's include fee updates to this PR. I'll also create an issue to try to use the getTransferFee Axelar SDK API, as it wasn't working properly when I built this integration.
Thread from Axelar

FYI created this issue
https://github.com/osmosis-labs/osmosis-frontend/issues/982

Let's include fee updates to this PR. I'll also create an issue to try to use the getTransferFee Axelar SDK API, as it wasn't working properly when I built this integration.
Thread from Axelar

Fees have been updated for all assets (mainnet and testnet)


added nbt editors

The 'Editing NBT Safely' page links to the 'Commonly Used Tools' Page, but the CUT page does not have any nbt editing tools, so i added em in!

I'd add a disclaimer to the MCC Tool Chest section that while it can probably be used for NBT editing, the other world editing functions probably shouldn't be used on current Bedrock worlds because it stopped development over 2 years ago now and hasn't been updated for changes to chunk saving since then.  (The weebly site is an even older version that looks like it's from 5 years ago by the mediafire upload timestamp)

I'd add a disclaimer to the MCC Tool Chest section that while it can probably be used for NBT editing, the other world editing functions probably shouldn't be used on current Bedrock worlds because it stopped development over 2 years ago now and hasn't been updated for changes to chunk saving since then. (The weebly site is an even older version that looks like it's from 5 years ago by the mediafire upload timestamp)

thanks, updating!

(Sorry for the delay in time in getting to this.)  At the moment, we probably won't be adding a specific section on NBT tools because - that might get a little bit more advanced and potentially hard-to-support than we were intending for this section.


scrollTo method

Hi,
I looked into your code to use it with tabs, the scrollTo(index) method was great but is bugged. You should get rid of the this.state.index which has nothing to do here. This took me so much time to find the problem so I share it !

What bug were you addressing with this @ilansas? I've just come across a bug where attempting to scroll past the limits then clicking an action containing scrollTo fails. Is this the same thing?

I've opened an issue for it. If it's the same thing I'll close it. https://github.com/leecade/react-native-swiper/issues/41

Merged #87


Memory Allocation Issue (ESP RainMaker + ESP-WHO Face Detection + BLE NimBLE) (IDFGH-13641)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

IDF version.
5.3
Espressif SoC revision.
ESP32-S3 WROOM2 with 32MB
Operating System used.
Windows
How did you build your project?
Command line with idf.py
If you are using Windows, please specify command line type.
PowerShell
Development Kit.
custom board
Power Supply used.
USB
What is the expected behavior?
I'm working on a project with the ESP32-S3 where I need to integrate ESP RainMaker, BLE NimBLE, and the Face Detection Web API from ESP-WHO. When I run each API individually, or even combine ESP RainMaker and BLE NimBLE, everything works perfectly fine. However, when I try to combine all three (ESP RainMaker + BLE + Face Detection), I run into memory allocation failures.
I have already tried various memory optimizations.
Has anyone faced similar issues or have suggestions for further memory optimizations to run all three components successfully on the ESP32-S3? Any advice or alternative approaches would be greatly appreciated!
Thanks in advance!
What is the actual behavior?
none
Steps to reproduce.
1 idf.py build
2 idf.py flash
Debug Logs.
I (5873) app_wifi: Connected with IP Address:<IP_ADDRESS>
I (5873) esp_netif_handlers: sta ip: <IP_ADDRESS>, mask: <IP_ADDRESS>, gw: <IP_ADDRESS>
I (5873) main_task: Returned from app_main()
I (5873) esp_rmaker_cmd_resp: Enabling Command-Response Module.
I (5883) esp_rmaker_node: Node attribute cmd-resp created
I (5893) esp_rmaker_local: Enabling Local Control
I (5893) esp_rmaker_local: Local Control Service Enabled
I (5903) esp_rmaker_local: Starting ESP Local control with HTTP Transport and security version: 1
I (5913) esp_https_server: Starting server
I (5923) esp_https_server: Server listening on port 8080
I (5923) esp_rmaker_local: esp_local_ctrl service started with name : 348518A1BDC0
I (5933) esp_mqtt_glue: Connecting to a1p72mufdu6064-ats.iot.us-east-1.amazonaws.com
I (5943) esp_rmaker_core: Waiting for MQTT connection
I (6133) ioexpander: fa
I (6133) ADC: ADC1 Channel[1] Raw Data: 4095
I (6133) ADC: ADC1 Channel[1] Cali Voltage: 3076 mV
I (6133) ADC: Resistance: 274642.84 Ohms, ambient_Temperature: -36.82°C

I (6533) esp-x509-crt-bundle: Certificate validated
I (8153) ADC: Raw Data: 52 MAIN MOTOR Cali Voltage: 44 mV
I (8193) esp_mqtt_glue: MQTT Connected
I (8193) esp_rmaker_cmd_resp: Checking for pending commands.
I (8193) esp_rmaker_node_config: Generated Node config of length 2180
I (8203) esp_rmaker_param: Params MQTT Init done.
I (8203) esp_rmaker_param: Reporting params (init): {"MotorFanLight":{"Motor Speed":0,"Fan Speed":0,"Light Brightness":0},"read Sensor":{"Name":"read Sensor","Temperature":-36.82250,"battery Sensor":0.00000},"Time set":{"Hour":0,"Minute":0,"Second":0},"Time":{"TZ":"Asia/Kolkata","TZ-POSIX":"IST-5:30"},"Schedule":{"Schedules":[]},"Scenes":{"Scenes":[]},"Local Control":{"POP":"90aef653","Type":1}}
I (8243) esp_rmaker_param: Reporting Time Series Data for read Sensor.Temperature
I (8553) esp_rmaker_param: Reporting Time Series Data for read Sensor.Temperature
I (8553) esp_rmaker_param: Reporting params: {"read Sensor":{"Temperature":-36.82250}}
I (8563) app_main: Provisioning completed
I (8563) BLE_INIT: BT controller compile version [ba3b3e3]
I (8573) BLE_INIT: Bluetooth MAC: 34:85:18:a1:bd:c2
E (8573) BLE_INIT: Malloc failed
assert emi.c 164, param 00000000 00008400
Guru Meditation Error: Core  0 panic'ed (Interrupt wdt timeout on CPU0).

ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0xc (RTC_SW_CPU_RST),boot:0xb (SPI_FAST_FLASH_BOOT)
Saved PC:0x40376088
SPIWP:0xee
Octal Flash Mode Enabled
For OPI Flash, Use Default Flash Boot Mode
mode:SLOW_RD, clock div:1
load:0x3fce2810,len:0x178c
load:0x403c8700,len:0x4
load:0x403c8704,len:0xcb8
load:0x403cb700,len:0x2df4
entry 0x403c8914

More Information.

sdkconfig.zip

Hi, could you try initiate other app, before initializing the esp-dl models?

No, now I initialized ESP RainMaker and successfully completed the provisioning. After that, I initialized BLE, and only then did I initialize the ESP-DL model."  i got this error


Progress bar is finishing prematurely [BUG]

Prerequisites

[X] I have read the documentation.
[X] I have checked other issues for similar problems.

Backend
Local
Interface Used
CLI
CLI Command
autotrain llm --train --project_name everythingLM-20b --model /run/media/knut/HD/huggingface\ models/language\ models/LLMs/pretrained/40b/internlm-20b-llama/ --data_path . --train_batch_size 1 --num_train_epochs 5 --trainer sft --use_int4 --use_peft --merge_adapter --block_size 1000 --max-length 4096 --target_modules "q_proj,k_proj,v_proj,o_proj" --use_flash_attention
UI Screenshots & Parameters

Error Logs
56%|███████████████████████████████████████▏                              | 3000/5365 [1:41:55<1:20:20,  2.04s/it]

INFO    Finished training, saving model...

Additional Information
I don't know how this happens, but i've had this since quite a while. the progress bar reaches 50-60 percent and then training finishes, also indicating that the epochs have roughly reached the goal. It just stores the model as it should.
Something gotta be wrong here, either the estimate is off, or perhaps it's not using the records right. I don't think I have wrongly formated the records. But the models I get out of it are working, which is why I've ignored it and just occasionally picked double the epochs I wanted. It happens with both peft and full fine tuning.

sft with packing doesnt show actual progress. training is indeed finished. if you'd like the progress bar be fixed, please open an issue in TRL repo :)

Thanks glad it's fine!


Fix broken link

Found a broken link when I read the code.

We will need you ti sign CLA before we merge it. We will add CLA assistant to this repo soon.

We will need you ti sign CLA before we merge it. We will add CLA assistant to this repo soon.

@korniltsev Friendly ping~
Do you have time to set up it? Thanks!

Cc @petethepig


How to set localeStrings ?

https://jsfiddle.net/kn381h7s/873/        I want to change totals text  but not working  please  help me

Hi there, I had the same question as you. I was able to change the "Totals" text by setting the localeStrings inside the rendererOptions.
rendererOptions:{
    localeStrings: {
        totals: "Totaleseee",
    }
}

I've updated your jsfiddle to reflect the change I made to make it work:
https://jsfiddle.net/kn381h7s/905/

Thank You


Update SDKs & show path to running update tests

Updated SDKs & added some stuff to readmes and the fuzzer scenario to better explain how to run it and how to do repeatable runs.
Also added some seeds I encountered issues on while testing.
It was very, very easy to encounter issues (often update related, sometimes not). So I don't know that you really need to use the saved seeds. This was using the CLI as of https://github.com/temporalio/cli/commit/29b1eb17d29cf968df0c9ce89c4627901d869ce3

Actually, after approving I had a couple of thoughts / findings:

When running with --embedded-server I'm getting$ go run ./cmd run-scenario-with-worker --scenario workflow_with_single_noop_activity --language go --embedded-server
compile: version "go1.22.5" does not match go tool version "go1.21.2"

Since users will often want to test a specific server version, perhaps remove --embedded-server from README examples, so that people know it expects to connect to a running server?
Is it possible to collect information on the server version used in the yaml file?


Controller connecting after game starts fails to navigate UI focus

Tested versions

Reproducible in: 4.3.beta3 ; 4.2.1.stable

System information
Windows 10
Issue description
If a controller connects after the game starts, the d-pad navigation buttons fail to change the ui item focus for that controller.
It seems that ui_accept works as the button clicks register, but D-pad is dysfunctional for navigation. I tested on both the XBox One controller and PS5 controller with and without Steam open. Both of the controllers exhibit the same behavior.
In case of two controllers, it will affect the one that connects during the run whilst the other will keep on working.
Steps to reproduce
Add two Button controls, make one of them call grab_focus() at the start.

Make sure thet the controller is disconnected, run project, connect the controller.
Observe that navigation using the D-üad will fail to move the focus to the other button. (You can still hit A to make the button click (if you configure it as ui_accept manually)).

Minimal reproduction project (MRP)
focustest.zip

I found the cause.
By default the UI input navigation expects "Device 0" as the device.
For some reason the additional controller does not start as device 0 and is 1 instead. Thus the navigation will fail in an obscure manner.


⚠ Bofrost.es has degraded performance

In 03c6917, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1645 ms

Resolved: Bofrost.es performance has improved in 42d8100 after 9 minutes.


[TEST-DO NOT MERGE]

Relevant information

Checklist

[ ] I've read the guidelines and understand the acceptance criteria.
[ ] The value of the attribute marked as identifier will be unique and valid.
[ ] I've confirmed that my entity type wasn't already defined. If it is I'm providing an explanation above.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.2 out of 3 committers have signed the CLA.:white_check_mark: manuelrodriguez-nr:white_check_mark: durgaprasad95:x: dsankaraganti-nrYou have signed the CLA already but the status is still pending? Let us recheck it.


Change minimum required Python version to 3.7

[ ] Adapt build script
[ ] Add version check to CLI
[ ] Change requirements in README

Useful changes in Python 3.7:

insertion-order preservation nature of dict objects has been declared to be an official part of the Python language spec.

Data Classes


sequence feature pages

Sequence features, such as centromeric bits in #36, should have pages analogous to gene pages. SO term searches can then list IDs and link to pages in results.
To start with, just mimic the (few) parts of a gene page that have corresponding info for features – ID, coordinates, map image, literature, external refs if any, etc. Once there are some test pages available we can see if any further refinements are needed.

We can wait a little while longer for these....

SO term searches can then list IDs and link to pages in results.

That's going to require a bit of work as the query system is currently very gene oriented.
Adding sequence feature pages is reasonably straight forward.
Here are the counts of feature types in Chado.  Most of the list is handled already on the gene pages.  Which types would be good to test sequence feature pages?
2 or 3 suggestions would be very helpful.  Thanks.

feature type
count

allele
14945

chromosome
6

dg_repeat
11

dh_repeat
16

exon
12114

five_prime_UTR
4874

gap
4

gene
56161

gene_group
5

genotype
23045

intron
994

long_terminal_repeat
239

low_complexity_region
60

LTR_retrotransposon
14

mating_type_region
1

mRNA
5140

ncRNA
1527

nuclear_mt_pseudogene
17

origin_of_replication
7

polyA_signal_sequence
1

polyA_site
17

polypeptide
5140

promoter
73

pseudogene
31

pseudogenic_exon
73

pseudogenic_transcript
31

region
28

regional_centromere
3

regional_centromere_central_core
4

regional_centromere_inner_repeat_region
6

repeat_region
44

rRNA
49

snoRNA
57

snRNA
6

three_prime_UTR
4803

transcript
6697

TR_box
2

tRNA
196

SO term searches can then list IDs and link to pages in results.

That's going to require a bit of work as the query system is currently very gene oriented.
Adding sequence feature pages is reasonably straight forward.
Here are the counts of feature types in Chado.  Most of the list is handled already on the gene pages.  Which types would be good to test sequence feature pages?
2 or 3 suggestions would be very helpful.  Thanks.

feature type
count

allele
14945

chromosome
6

dg_repeat
11

dh_repeat
16

exon
12114

five_prime_UTR
4874

gap
4

gene
56161

gene_group
5

genotype
23045

intron
994

long_terminal_repeat
239

low_complexity_region
60

LTR_retrotransposon
14

mating_type_region
1

mRNA
5140

ncRNA
1527

nuclear_mt_pseudogene
17

origin_of_replication
7

polyA_signal_sequence
1

polyA_site
17

polypeptide
5140

promoter
73

pseudogene
31

pseudogenic_exon
73

pseudogenic_transcript
31

region
28

regional_centromere
3

regional_centromere_central_core
4

regional_centromere_inner_repeat_region
6

repeat_region
44

rRNA
49

snoRNA
57

snRNA
6

three_prime_UTR
4803

transcript
6697

TR_box
2

tRNA
196

We already have tickets open for allele pages (but these are slightly different  feature types  to the sequence features we are requesting pages for here)
allele | 14945
I don't think we need pages for
chromosome | 6
low_complexity_region | 60
gap | 4
We will never manually annotate origins so we don't need pages for these:
origin_of_replication | 7 (these are the early 'well studied' origins, annotated so they appear in the browser with labels)
Obviously we have gene pages already
gene | 56161
and is_a gene(s):
ncRNA | 1527
rRNA | 49
snoRNA | 57
snRNA | 6
pseudogene | 31
LTR_retrotransposon | 14
and we have
genotype | 23045
and we don't need separate pages for 'transcripts' or their 'parts' because these are covered on the gene pages:
exon | 12114
five_prime_UTR | 4874
intron | 994
mRNA | 5140
tRNA | 196
three_prime_UTR | 4803
transcript | 6697
polyA_signal_sequence | 1
polyA_site | 17
polypeptide | 5140
promoter | 73
pseudogenic_exon | 73
pseudogenic_transcript | 31
TR_box | 2
This leaves:
the various 'regions'
region | 28 (this is a grouping term)
regional_centromere | 3
The centromeric parts:
dg_repeat | 11
dh_repeat | 16
regional_centromere_central_core | 4 (I"m a bit baffled why we have 4, need to look into that!)
regional_centromere_inner_repeat_region | 6
mating_type_region | 1
I'm not even sure that pages for these regions will be so useful.  What would they show? There is not really anything to annotate on the  individual repeats,  It might be better if our drop-down menus allowed people to get to these regions of the genome in the browser quickly
https://www.pombase.org/jbrowse/?loc=I%3A3753692..3789426&tracks=PomBase forward strand features%2CPomBase reverse strand features&highlight=
gene_group | 5 (I don't know what this refers to)
These are probably OK just as features in the browser
long_terminal_repeat | 239
nuclear_mt_pseudogene | 17
repeat_region | 44

We already have tickets open for allele pages (but these are slightly different  feature types  to the sequence features we are requesting pages for here)
allele | 14945
I don't think we need pages for
chromosome | 6
low_complexity_region | 60
gap | 4
We will never manually annotate origins so we don't need pages for these:
origin_of_replication | 7 (these are the early 'well studied' origins, annotated so they appear in the browser with labels)
Obviously we have gene pages already
gene | 56161
and is_a gene(s):
ncRNA | 1527
rRNA | 49
snoRNA | 57
snRNA | 6
pseudogene | 31
LTR_retrotransposon | 14
and we have
genotype | 23045
and we don't need separate pages for 'transcripts' or their 'parts' because these are covered on the gene pages:
exon | 12114
five_prime_UTR | 4874
intron | 994
mRNA | 5140
tRNA | 196
three_prime_UTR | 4803
transcript | 6697
polyA_signal_sequence | 1
polyA_site | 17
polypeptide | 5140
promoter | 73
pseudogenic_exon | 73
pseudogenic_transcript | 31
TR_box | 2
This leaves:
the various 'regions'
region | 28 (this is a grouping term)
regional_centromere | 3
The centromeric parts:
dg_repeat | 11
dh_repeat | 16
regional_centromere_central_core | 4 (I"m a bit baffled why we have 4, need to look into that!)
regional_centromere_inner_repeat_region | 6
mating_type_region | 1
I'm not even sure that pages for these regions will be so useful.  What would they show? There is not really anything to annotate on the  individual repeats,  It might be better if our drop-down menus allowed people to get to these regions of the genome in the browser quickly
https://www.pombase.org/jbrowse/?loc=I%3A3753692..3789426&tracks=PomBase forward strand features%2CPomBase reverse strand features&highlight=
gene_group | 5 (I don't know what this refers to)
These are probably OK just as features in the browser
long_terminal_repeat | 239
nuclear_mt_pseudogene | 17
repeat_region | 44

gene_group | 5 (I don't know what this refers to)

There are five misc_features on chromosome 3 with /SO="SO:0005855":
FT   misc_feature    2450422..2452883
FT                   /note="18S, 5.8S, and 28S ribosomal RNA"
FT                   /SO="SO:0005855"

gene_group | 5 (I don't know what this refers to)

There are five misc_features on chromosome 3 with /SO="SO:0005855":
FT   misc_feature    2450422..2452883
FT                   /note="18S, 5.8S, and 28S ribosomal RNA"
FT                   /SO="SO:0005855"

If there are interesting non-gene features but it's not worth making a page per feature, we could always add a table of features to the documentation with columns: feature_type, chromosome, start, end.
The table could be automatically generated from a list of feature types in the configuration file.

If there are interesting non-gene features but it's not worth making a page per feature, we could always add a table of features to the documentation with columns: feature_type, chromosome, start, end.
The table could be automatically generated from a list of feature types in the configuration file.

That might work well.

That might work well.

Chromosomes 1 and 3 have one each. Chromosome 2 has 2:

Now merged into a single core. This is probably a hangover from continuation!

Chromosomes 1 and 3 have one each. Chromosome 2 has 2:

Now merged into a single core. This is probably a hangover from continuation!

I'll add a basic sequence feature page to the documentation containing an automatically updating table. I won't link to the page from the rest of the documentation until it's ready to go.

Done!  But very basic:  https://www.pombase.org/documentation/misc-sequence-features
More features can be added by adding SO term names to the "so_types_to_show" option in the config file:
https://github.com/pombase/pombase-config/blob/master/website/pombase_v2_config.json#L27
And the Markdown file for the page is here:
https://github.com/pombase/website/blob/master/src/docs/documentation/misc-sequence-features.md
There are no links to the page yet.  Let me know if there is anything to add or remove from the table.

I'll add a basic sequence feature page to the documentation containing an automatically updating table. I won't link to the page from the rest of the documentation until it's ready to go.

Done!  But very basic:  https://www.pombase.org/documentation/misc-sequence-features
More features can be added by adding SO term names to the "so_types_to_show" option in the config file:
https://github.com/pombase/pombase-config/blob/master/website/pombase_v2_config.json#L27
And the Markdown file for the page is here:
https://github.com/pombase/website/blob/master/src/docs/documentation/misc-sequence-features.md
There are no links to the page yet.  Let me know if there is anything to add or remove from the table.

Could we configure some prettier display strings somewhere, e.g. substitute for the SO term names

regional_centromere -> centromere
regional_centromere_central_core -> centromere central core

and just use '1', '2', and '3' for the chromosome?

Could we configure some prettier display strings somewhere, e.g. substitute for the SO term names

regional_centromere -> centromere
regional_centromere_central_core -> centromere central core

and just use '1', '2', and '3' for the chromosome?

It's off to a good start, though - thanks!

It's off to a good start, though - thanks!

Could we configure some prettier display strings somewhere, e.g. substitute for the SO term names

Good plan.  I'll do that next week.

and just use '1', '2', and '3' for the chromosome?

Would "I", "II", "III", etc. be OK?  That what we have in JBrowse and in the "Genomic location" on the gene pages.

Could we configure some prettier display strings somewhere, e.g. substitute for the SO term names

Good plan.  I'll do that next week.

and just use '1', '2', and '3' for the chromosome?

Would "I", "II", "III", etc. be OK?  That what we have in JBrowse and in the "Genomic location" on the gene pages.

Would "I", "II", "III", etc. be OK?

Sure! The important thing (to me) is not to repeat "chromosome" in the table cells when it's already right there in the header.

Would "I", "II", "III", etc. be OK?

Sure! The important thing (to me) is not to repeat "chromosome" in the table cells when it's already right there in the header.

Would "I", "II", "III", etc. be OK?

That's done now.

Could we configure some prettier display strings somewhere, e.g. substitute for the SO term names

I've added a new config setting (term_display_names) to specify the displayed term names:
https://github.com/pombase/pombase-config/blob/master/website/pombase_v2_config.json#L5786
https://github.com/pombase/website/wiki/Config-file#term_display_names

Would "I", "II", "III", etc. be OK?

That's done now.

Could we configure some prettier display strings somewhere, e.g. substitute for the SO term names

I've added a new config setting (term_display_names) to specify the displayed term names:
https://github.com/pombase/pombase-config/blob/master/website/pombase_v2_config.json#L5786
https://github.com/pombase/website/wiki/Config-file#term_display_names

I should have mentioned this earlier:
some of the feature IDs in the table aren't great: CU329670_regional_centromere_3753687..3789421
These are automatically generated by the loader because there is no /systematic_id for the feature.

I should have mentioned this earlier:
some of the feature IDs in the table aren't great: CU329670_regional_centromere_3753687..3789421
These are automatically generated by the loader because there is no /systematic_id for the feature.

[ ] CU329670_regional_centromere_3753687..3789421
This is the "CU329670" should we give a shorter PomBase ID?

[ ] The centromere repeat features aren't strand-specific so this should be n/a

[ ] CU329670_regional_centromere_3753687..3789421
This is the "CU329670" should we give a shorter PomBase ID?

[ ] The centromere repeat features aren't strand-specific so this should be n/a

OK I now see your follow up comment about the IDs!

OK I now see your follow up comment about the IDs!

I've added a new config setting (term_display_names) to specify the displayed term names:

cool; thanks :)

I've added a new config setting (term_display_names) to specify the displayed term names:

cool; thanks :)

The centromere repeat features aren't strand-specific so this should be n/a

Currently all features are stored as either forward or reverse strand in Chado.  I don't know how to specify that a feature is unstranded in EMBL format.  Googling didn't help.  We might have to make something up, perhaps a qualifier.

The centromere repeat features aren't strand-specific so this should be n/a

Currently all features are stored as either forward or reverse strand in Chado.  I don't know how to specify that a feature is unstranded in EMBL format.  Googling didn't help.  We might have to make something up, perhaps a qualifier.

The centromere repeat features aren't strand-specific so this should be n/a

As a temporary fix, I'll remove the strand column.

The centromere repeat features aren't strand-specific so this should be n/a

As a temporary fix, I'll remove the strand column.

We have a use case for feature  pages for japonicusDB.
PomBAse transposons always correspond to  ORFs, so are annotated as CDS.
In japonicus the transposons are often quite degraded, and even the ones which aren't  are
annotated as the full length Transposon, including  the LTR (I think).
Anyway I could not easily see Orfs, but I will look again once they are in the contigs as misc features.
I think we could have pages for these so that people find them when they search with the IDs, although there would not be much to say about them....

I think we could have pages for these so that people find them when they search with the IDs, although there would not be much to say about them....

Would it be enough to be able to search by ID, but get sent to a page like this when you press enter?:
https://www.pombase.org/documentation/misc-sequence-features
That saves a bit of work for me and avoids having features pages that don't contain very much.

This works for me. It is a nice stepping stone until there is sufficient motivation & justification to add the pages which would have knock-on effects for querying etc.
It would at least allow people to see what non-gene features were annotated, and allow them to get to the location in the browser for any non-gene feature.
I think this page would be better if the JBrowse link was the first column after the name and feature types because I didn't realise it was there (you need to scroll right to see it).

This works for me. It is a nice stepping stone until there is sufficient motivation & justification to add the pages which would have knock-on effects for querying etc.

That makes sense.  I'll do that soon.  I should be pretty quick to implement.

I think this page would be better if the JBrowse link was the first column after the name and feature types because I didn't realise it was there (you need to scroll right to see it).

I've made that change, which should be visible in 20-30 minutes.

Does anyone remember the history of why we have the coordinates in the regional centromere IDs?

Does anyone remember the history of why we have the coordinates in the regional centromere IDs?

I don't remember.  It doesn't seem very useful.  Something shorter makes sense.

I think we could have pages for these so that people find them when they search with the IDs,

Now I've thought about it more, how will they know the IDs so they can search for them?  They're pretty obscure.

Just spotted a comment above:
'I should have mentioned this earlier:
some of the feature IDs in the table aren't great: CU329670_regional_centromere_3753687..3789421"
CU329670 can be the ID, and  they can have labels CEN1, CEN2, CEN3 which are the 'traditional' abbreviations as 'primary/human readable names'

I think we could have pages for these so that people find them when they search with the IDs, although there would not be much to say about them....

this was in the context of the full length transposons which should have a label that the users recognise, but I don't think there is any urgency for these pages since the will not be any annotation. They are basically coordinates and a label.

I prefer just the sequence feature page,  I think...it is really only required to 'get to this place in the genome' so a page where you can see all  non gene features as a list will be great...

'I should have mentioned this earlier:
some of the feature IDs in the table aren't great: CU329670_regional_centromere_3753687..3789421"

There are lots of features in Chado with similar IDs.  These are automatically generated for features that don't have a /systematic_id.  The start..end is added to make them unique.  The SO feature name (like regional_centromere) is there because of /SO=... qualifiers.
Here are some examples:
 CU329670_promoter_2992573..2992582
 CU329670_promoter_2992592..2992599
 CU329670_polyA_site_2999546..2999546
 CU329670_polyA_site_2999663..2999663
 CU329670_low_complexity_region_3030456..3033580

CU329670 can be the ID

I think that would be confusing because that's the ENA ID for the chromosome.

So should I just give them IDs
SPCEN1
SPCEN2
SPCEN3
?

So should I just give them IDs
SPCEN1
SPCEN2
SPCEN3

That seems sensible to me.

I had forgotten about this. Do we link to this page yet? I could not find it

I had forgotten about this. Do we link to this page yet? I could not find it

There's no link to it yet.

https://www.pombase.org/documentation/misc-sequence-features
needs a link from the documentation, and we need a list of outstanding tasks here.

needs a link from the documentation,

I've added a "Non-gene sequence features" section here, with a link to the new page:

https://www.pombase.org/documentation

(If you have any ideas for a better title please let me know, or edit directly)
The new sequences features page has a bit of an overlap with:

https://www.pombase.org/status/centromeres

It's not urgent, but should we combine them somehow?

I think it is good to keep the centromere cartoon.
We could relabel this page 'Schematic of the centromere" and link to it from the new page.
We don't need any of this text:
~At present, each centromere is annotated as a single sequence feature in PomBase, which can be viewed in and downloaded from the genome browser.
Chromosome coordinates (links to JBrowse):
CEN 1: I:3753687-3789421
CEN 2: II:1602264-1644747
CEN 3: III:1070904-1137003
Note that specific repeats within centromeres cannot yet be viewed or searched as features on PomBase pages, but they are included in the forward and reverse strand feature tracks in the genome browser, which are enabled by default.~

we need a list of outstanding tasks here.

I don't think there's anything else to do and this issue is getting a bit long. So I'll close it.
I've made the changes to the centromeres pages that you suggested.


Port all modules into a .go file

We should have a working go version of all core modules.
Ones currently done:

shell
yum

Change the modules directory to modules/modName/osName or (modName if it's a script)
update package.sh so Circle compiles all the modules instead of pushing up the binaries

I say we should port the modules which don't work in python 2.6.  If we port all core modules, retrieving the henchman tar from circle will become extremely large after a while.  Right now it's already at 30~ mb with only 4 modules ported.  Thoughts?


Small tidy of composer.json and travis config

satooshi/php-coveralls is already a dependency of codeclimate/php-test-reporter, our travis config will now test against more versions of PHP

Thanks @jonnybarnes


Improve the wbr_start documentation

Preview: https://www.cyberbotics.com/doc/guide/controller-plugin?version=enhancement-remote-control-doc#remote-control-plugin

👍


Velocity vs. Speed

Hello. I am working on a little patch for this code, and in it i am extending the "Velocity" class with additional units.
Since it currently only has one unit ("meters per second"), i am guessing noone is actually using it. So might it be possible if we rename it to "Speed" instead?
If ok, I will rename the class to Speed in my branch before sending a pull request
From wikipedia:
"Distinction between speed and velocity Speed describes only how fast an object is moving, whereas velocity gives both how fast and in what direction the object is moving. If a car is said to travel at 60 km/h, its speed has been specified."

Here is my proposed change:
https://github.com/martinlindhe/php-units-of-measure/commit/263428103d52723af2052ba62912d7279ee99617

I believe this was addressed as part of #40.  I  agreed that in hindsight, speed might've been more technically accurate, but changing the name now would be a backwards-incompatible breakage and the ambiguity is unlikely to cause confusion as it stands.


Multiple selection via shift-click for controlled selection

Addresses https://github.com/nadbm/react-datasheet/pull/156/files#r307206217
Changes DataSheet onMouseDown while shift is held to account for when selection is controlled.
Add tests for shift-clicking for both controlled and uncontrolled selection.

Hello! I'm curious to know if this does fix both errors described on my issue?
https://github.com/nadbm/react-datasheet/issues/235
Thanks!


Add a way to see list of videos I've liked (feature request from reddit)

https://www.reddit.com/r/OdyseeForever/comments/xjgjpr/is_there_anyway_anyway_to_view_previously_liked/

We'd probably do this via a liked playlist and insert a video there each time a user likes one. Maybe this could be turned on/off.


Release 11.7

Codecov Report

Merging #723 into master will decrease coverage by 1.05%.
The diff coverage is 30.62%.

@@             Coverage Diff              @@
##             master     #723      +/-   ##
============================================
- Coverage     57.78%   56.72%   -1.06%
- Complexity     1753     1882     +129
============================================
  Files           183      201      +18
  Lines          8978     9644     +666
  Branches        777      849      +72
============================================
+ Hits           5188     5471     +283
- Misses         3587     3958     +371
- Partials        203      215      +12

Impacted Files
Coverage Δ
Complexity Δ

...ui/src/main/kotlin/com/almasb/fxgl/ui/MDIWindow.kt
0% <ø> (ø)
0 <0> (ø)
:arrow_down:

.../main/java/com/almasb/fxgl/core/math/FXGLMath.java
98.38% <ø> (ø)
45 <0> (ø)
:arrow_down:

.../com/almasb/fxgl/achievement/AchievementManager.kt
92.72% <ø> (+10.27%)
22 <0> (+2)
:arrow_up:

...com/almasb/fxgl/pathfinding/CellMoveComponent.java
0% <0%> (ø)
0 <0> (?)

...l/src/main/kotlin/com/almasb/fxgl/dsl/FXGLForKt.kt
6.41% <0%> (-0.54%)
0 <0> (ø)

...ain/kotlin/com/almasb/fxgl/dsl/AnimationBuilder.kt
20.23% <0%> (-0.73%)
6 <0> (ø)

...xgl/dsl/components/view/GenericBarViewComponent.kt
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...ava/com/almasb/fxgl/pathfinding/maze/MazeCell.java
0% <0%> (ø)
0 <0> (?)

.../main/java/com/almasb/fxgl/ui/PropertyMapView.java
0% <0%> (ø)
0 <0> (?)

...lmasb/fxgl/dsl/components/KeepOnScreenComponent.kt
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

... and 61 more

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 ddef3c7...eaf6e86. Read the comment docs.


Clarity: secrets store CSI driver vs external secrets... what to use?

Hi - thanks for this project. Currently looking for the best way to seed/bridge vault/azure-kv stored secrets and provision/access them from k8s. I came across the Secrets Store CSI project yesterday and today came across this project.
What are the main differences? is the CSI (or this project) becoming more part of an official standard? Just trying to determine which route to go.
https://github.com/external-secrets/kubernetes-external-secrets/issues/722

The main differences:

ESO synchronizes secrets from a cloud provider to secrets in k8s, so you can keep using k8s secrets if you are used to that.

SSCSID mounts the external secret as a volume in a pod directly, and having a secret in the cluster is optional

ESO focuses on having configuration on the CRD, what you create on the secret store in the provider is only the secret value itself

SSCSID requires the entire config/secret to be stored in the provider directly as the application will need to consume it. This may be too difficult to use with larger configurations that have some secrets embedded.

ESO secrets can be used with any resource in k8s natively, that's obvious, but 👇

SSCSID  needs a pod webhook to really have it work well. You can not easily use SSCSID secrets to reference them in ingress, or dockerconfig for pulling images, since their goal is just to mount to a pod. Even if you want to enable k8s secret sync, you need to first mount the secret to a pod to sync it.

In ESO, Since we sync secrets with k8s native secrets, if you have connectivity problems, you can still access the secret that is present in your cluster, when you re-connect, it will just continue to re-sync

with SSCSID, if you loose connectivity, your csi driver mounts stop working if you get some restarts and all that. They are thinking about that, not sure what is the progress there: doc. You would need to check with them.

ESO will be just one operator deployment in your cluster

SSCSID will have a privileged provider daemonset that will be responsible to make the mounts in your pods

If you need to follow any compliance and need to avoid having kubernetes native secrets in your cluster, you need to go with SSCSID, then you can mount secrets from external provider directly as volumes in your pods. If you don't need that, you can probably give ESO a go.
We have in our roadmap the plan to integrate with them: https://github.com/external-secrets/external-secrets/issues/336
We have some discussions going: https://github.com/external-secrets/external-secrets/discussions/461
But it can get quite complicated and we lack the engineering time to pursue that right now.

Closing the issue. Feel free to comment or ask us to re-open :)

A big difference (I may be wrong): "ESO will decouple the secret provider with the workload, because it creates k8s secrets. SSCSID will call the secret provider every time a workload unit (aka pod) is created."
SSCSID is more similar to "vault k8s injector"

The main differences:

ESO synchronizes secrets from a cloud provider to secrets in k8s, so you can keep using k8s secrets if you are used to that.
SSCSID mounts the external secret as a volume in a pod directly, and having a k8s secret in the cluster is optional
ESO focuses on having configuration on the CRD, what you create on the secret store in the provider is only the secret value itself
SSCSID requires the entire config/secret to be stored in the provider directly as the application will need to consume it. This may be too difficult to use with larger configurations that have some secrets embedded.
ESO secrets can be used with any resource in k8s natively, that's obvious, but 👇
SSCSID  needs a pod webhook to really have it work well. You can not easily use SSCSID secrets to reference them in ingress, or dockerconfig for pulling images, since their goal is just to mount to a pod. Even if you want to enable k8s secret sync, you need to first mount the secret to a pod to sync it.
In ESO, Since we sync secrets with k8s native secrets, if you have connectivity problems, you can still access the secret that is present in your cluster, when you re-connect, it will just continue to re-sync
with SSCSID, if you loose connectivity, your csi driver mounts stop working if you get some restarts and all that. They are thinking about that, not sure what is the progress there: doc. You would need to check with them.
ESO will be just one operator deployment in your cluster
SSCSID will have a privileged provider daemonset that will be responsible to make the mounts in your pods

If you need to follow any compliance and need to avoid having kubernetes native secrets in your cluster, you need to go with SSCSID, then you can mount secrets from external provider directly as volumes in your pods. If you don't need that, you can probably give ESO a go.
We have in our roadmap the plan to integrate with them: #336
We have some discussions going: #461
But it can get quite complicated and we lack the engineering time to pursue that right now.

Hi!
I see this answer is referenced by the official documentation but after two years new features were implemented (like now CSI also supports secrets syncing), could this be updated on the docs please?
https://external-secrets.io/latest/introduction/faq/#differences-to-csi-secret-store

Also,

SSCSID mounts the external secret as a volume in a pod directly, and having a k8s secret in the cluster is optional

The having a k8s secret in the cluster is optional was probably what you were looking for, in the perspective of the documentation, and it is already there in the issue response.

One thing that might be stressed more from a security point of view, is that Kubernetes Secrets are best avoided. This is spelled out CIS Benchmarks for Kubernetes, AWS Security Best Practices, and numerous other sources. It stems from the lack of RBAC specificity.
So, in my view, the choice is more like: "if you must have secrets, then use ESO"
That said, one thing that is not clear wrt SSCSID is that the quality and features vary per implementation. The AWS impl. for example, does not provide a way to fetch SSM Parameters by path, and it does not cache. Every pod that needs those parameters is going to execute its own fetches (which, in my case, nullifies the very reason I wanted to use ASCP).

I wouldn't stress that out on the documentation as I don't agree with that (and I believe others maintainers agree with me). Of course, open to discuss and change that perspective. I briefly wrote a bit about that (without much rigor, and within an opinionated article, but still), and I think that when thinking about threat modeling avoiding k8s secrets does not give necessarily more security, and this is one of those 'best practices' that sound right only on the surface, without analyzing all the details.
If you are synchronizing secrets from an external providers into your cluster it does not matter much if they are injected by a sidecar, stored as ephemeral volumes, or k8s native secrets, threat modeling from an attacker perspective is pretty similar and you are a subject of lack of RBAC specificity either way as far as I understand.
I still think the general idea is 'if you need to avoid k8s native secrets, look for other solutions' and not the other way around.

That said, one thing that is not clear wrt SSCSID is that the quality and features vary per implementation. The AWS impl. for example, does not provide a way to fetch SSM Parameters by path, and it does not cache. Every pod that needs those parameters is going to execute its own fetches (which, in my case, nullifies the very reason I wanted to use ASCP).

Yeah, agree
This is an interesting discussion, but maybe better moved to the 'discussion' tab here on github? Not sure here is the best place to discuss that.

@knelasevero I think it is worth mentioning because these benchmarks & best practices are what the security auditors and pen testers will be using to assess the security of one's clusters. It's a legit difference because of the extra attention it will generate, even if in practice reasonable minds can provide an explanation. (Whether the findings presented by the auditors are relevant is another matter, that I agree is best discussed elsewhere, but I can say from experience that every Kubernetes Secret will be scrutinized.)

Hi @joebowbeer ! Security benchmarks and the need to comply is something that varies from company to company. ESO itself is just tool, and IMO, should not drive that type of conclusions. The use (or not) of any tool from a security perspective is always prone to evaluation (that’s why people have security departments to analyze what on the benchmark makes sense and what doesn’t).
I really don’t want to drive the projects documentation to only a sector of the whole Cloud native landscape (regulated environments).

I am all aboard for avoiding K8S secrets if it will make your life easier during audits! I even wrote that in that article. I would not write that directly in the docs as this can sound like a pinch on how we tackle security nowadays, but I think I am comfortable mentioning it here on the issue :D That is a very valid point on being pragmatic on everything you will have to do in your company, not everything is technical, and we have processes to go through. So +1

Discussion: https://github.com/external-secrets/external-secrets/discussions/2680

In brief: installing an external operator is a much much bigger risk than using secrets which are allowed to be read by an attacker which has already RBAC or AD permissions to spawn a container in the cluster + Get/List permissions to see them

not sure if I understood your point here! My point is that you can’t evaluate risk outside of implementation. Automatic rotation of sensitive information (that you can do with ESO) would be less riskier to having a separate process to inject that same static information (and have it compromised anywhere in your stack)

Is the container built from scratch, with 0 cves, denied privileged execution, restricted by seccomp? (Sorry still AFK)

containers are built from distroless/ubi images, have 0 high/critical CVEs. As any other container, we can’t really control how people deploy it in terms of privileged execution/seccomp. We do provide sensible defaults.

one of the difference is that CSI driver runs as daemon set in the cluster whereas ESO do not, so it's better to use ESO as it's easy to manage an save resources as well.

One of the differences is that the CSI driver runs as a daemon set in the cluster whereas ESO does not, so it's better to use ESO as it's easy to manage and save resources as well.

How could an operator with its complex control loop and custom resources reconciliation save resources with respect to a native daemonset implementing a much simpler control loop?

One of the differences is that the CSI driver runs as a daemon set in the cluster whereas ESO does not, so it's better to use ESO as it's easy to manage and save resources as well.

How could an operator with its complex control loop and custom resources reconciliation save resources with respect to a native daemonset implementing a much simpler control loop?

You can just install both projects into a cluster and check how much CPU and RAM are being eaten to answer that question :).
Not sure what you mean by "Native" Daemonset, or what makes the other logic simpler, as it is dependant of several components.
This difference is also already mentioned in the original answer up above.
Btw, I'd like us to stop necrobumping this closed issue and instead start opening different discussions in the 'Discussions' tab of GitHub on this repo. We can even link them here, but I think this can branch out too much for these specific sub-topics inside the project's differences.


Move core Flask repositories to an organization

Now that Github supports redirects, maybe it's time to consider moving Flask, and core extensions (Flask-SQLAlchemy, Flask-OAuth, etc) into an organization.
Thoughts from the team?

+1
It seems @mitsuhiko is pretty busy/excited about other projects, which is great, but for those still excited by the Flask ecosystem, it'd probably be easier if @mitsuhiko was open to giving up control a bit and migrating Flask and the core modules that he's the owner of over to a Github organization. I'm aware of the Metaflask repo, but it feels like a hack that doesn't work that well.

Flask is now part of the pallets Github org.


delay

The video delay is very large. Is there a way to solve it. I'm a novice.

Did you build in release mode (cargo build --release)? Please provide more information, a case where this can be reproduced would be best.

Closing due to inactivity.


[DO NOT MERGE] testing Jenkins CI

Please don't close this. I created it with account that is not in droolsjbpm org. unit to see how Jenkins copes with that.

Can one of the admins verify this PR? Comment with 'ok to test' to start the build.

ok to test

Can one of the admins verify this PR? Comment with 'ok to test' to start the build.


Values of the diagramm

Hey guys,
we are a group from a university, and we are trying to use your implementation to analyze the face in order to get the pulse and resp diagrams.
The problem is that we are getting weird values in the axes of the diagram despite using a video with 30 s length.
We would like to know, how to change those values in the code.
Thank you very much.

Hi @MoustafaAlissa, although I am not the author. I'll try to answer if that's okay with you. From the plot above and the information that you have given about using 30 sec. videos. I can make out that your video is recorded at about 30 FPS provided that a 30 sec video has almost 900 values (from your plot). The MTTS-CAN model gives a prediction for each frame and hence you get about 900 values in your plot. If you follow the steps as given in predict_vitals.py.
Additional note about the cutoff freq. of the Butterworth bandpass filter used by the authors:-

For heart rate- fl = 0.75 Hz and fh = 2Hz (So the authors assume that the normal HR will lie in between [0.75 x60, 2x60 ] BPM or [45,120] BPM
For Resp. rate- fl = 0.08 Hz and fh = 0.5Hz (normal resp. rate [ 4.8, 30 ] Breaths per min.

After filtering the signals as given in predict_vitals.py you can follow these steps:-

Calculate the power spectral density (can use this) of both the signals
Filter out all PSD for all freq outside your desired range [0.75,2] Hz for HR and so on
Calculate at which freq. does the maximum PSD lie
Multiply the freq obtained by 60 (to convert from Hz to BPM)

Finally, I apologize if you have already tried this and asked the question from a different context. I tried explaining to the best of my ability. Others are welcome to correct me. Have fun learning.


Feature/backbone bugfix

fixes 4 issues:

SelectAsset

selected image is blank in dropdown
upload asset popup response does not become selected asset
switching chosen asset does not update 'edit crop' href

ImageCropper

submit sporadically fails / does not invoke WindowPopup.respond to close popup

👍


Conditional eval transform is not spec compliant

Bug Report
🔎 Search Terms
eval, conditional, transform
🕗 Version & Regression Information
This is the behavior in every version I tried, and I reviewed the FAQ for entries about eval
⏯ Playground Link
https://www.typescriptlang.org/play?ts=4.3.2#code/GYVwdgxgLglg9mABFApgZygCgJSIN4BQixiANilIgIaIC8iAjANxEnmUBO6Ipl9KANyqkA-ADpMAciqTsLEoggI0ccmNJwA5pi5oeUOQQC+BAqgw4mQA
💻 Code
function test() {
    let a = 1;
    let result = eval?.('a'); // this should not have access to 'a'
    console.log(result);
}

🙁 Actual behavior
Code logs the value of a.
let result = eval === null || eval === void 0 ? void 0 : eval('a');

🙂 Expected behavior
Expect a runtime exception
// from Babel
let result = eval === null || eval === void 0 ? void 0 : (0, eval)("test");

Duplicate of https://github.com/microsoft/TypeScript/issues/43327
My search term was eval

Duplicate of #43327
My search term was eval

Thanks @nmain! Not sure why I jumped immediately to searching for “eval transform”. I probably assumed “eval” on its own would have too many results 🙂


Add more morphisms

I was watching @DrBoolean's A Million Ways to Fold in JS but I couldn't understand most of the morphism jargons. I presume the video is for experienced devs who are from a FP language background. The moment when I tried to search for "Catamorphism javascript" on google I couldn't get anything. I really hope there would be more in depth FP resources written in JavaScript. Luckily @i-am-tom kindly wrote up something that could be understood by JS devs like me. I have fixed a minor mistake in @i-am-tom's original write up and tweaked a few wording.
Also cc @joneshf @getify @shineli1984
Thanks!

Oh no :O what was my mistake?

Trailing spaces are meaningful in markdown so you shouldn't be stripping them automatically

@jethrolarson not with one space. Two spaces would create a \n but there are two newlines after it so it creates a seperate node already.

Whats up with this whole project? so many PRs and issues, can we get this merged in?

@mrtnbroder This is pretty much active, there are many reasons for open PRs and issues if you go through them.
@stevemao it needs a rebase.

@hemanth Sorry for the delay. Conflicts should be resolved

NP!
Awesomeness after ~2years this PR is going!


Edge supports Scroll-To-Text fragment

As expected, Edge 83 supports Scroll-To-Text Fragment by default 🥳
This was tested manually.
I also added a few Chromium versions that had support behind flags. Not sure why i missed that originally.  In my testing, Opera's implementation didn't work until v66, so that's why it doesn't have flag support going back to v61/62.
Is there any reason this is not live on the site? If there's anything i can help with, let me know :)

Thanks! No real reason, just haven't reviewed it yet. Looks pretty straightforward so will take a look soon.

Awesome!


Move layer argument to $1 for bin/build and bin/develop

As described in #28, this change moves the <layers[EIC]> argument to the $1 position for both bin/build and bin/develop.

This seems to be an optimization for people who won't use all the features at the expense of those who will.  Is this an accurate characterization?  If so, why do we want to target this group?  Why don't we want to optimize for buildpacks that make use of all of the features available in the spec?

My intention is to reduce friction for the base case. In some sense, that does mean optimizing for people who won't use all the features, at least in the beginning.
I want to target this group because it will help grow an ecosystem. I want us to do everything we can to increase adoption and implementation of buildpacks. A healthy and strong ecosystem will be key to the success of buildpacks. Small points of friction can add up and make the buildpack experience unattractive, which works against that goal.
This particular issue (the order of arguments) stands out to me as a point of friction for people trying to implement their first buildpack or a buildpack that is very simple. Every buildpack will use the layer directory, but only some will use the platform and plan.
Thus, I'm arguing for arguments in order of significance.
I did some analysis of the existing v2 buildpacks used on Heroku (there are thousands). I selected about a hundred that are the most commonly used, well-maintained, and not written by Heroku. Of those, only 18% reference $3 (the ENV_DIR).
For advanced buildpack authors, I don't consider the arg order a big concern. Most will use platform and layer directories, and a few will use plan. But we'll all be very familiar with the spec, and relying on tools like libbuildpack.
We have a spec to encourage the community to adopt it. We should make that adoption onramp as easy and frictionless as possible.
All that said, I understand where you're coming from @nebhale . I also understand the tradeoffs in my proposal. Ultimately, I want the best thing for buildpacks overall, and these discussions are an important part of that process, so let's keep at it.

This change is now on https://github.com/buildpack/lifecycle/tree/spec-28-great-layer-merger.


cross compile on x86_64 for cortexA57 target fail!!!please help

i have install aarch64-linux-gnu-gcc and set the $PATH
but when i git clone the source code of openblas using:
make BINARY=64 ARCH=arm64  CC=aarch64-linux-gnu-gcc HOSTCC=gcc TARGET=CORTEXA57
it returns to this:
getarch.c:80:19: fatal error: stdio.h: No such file or directory
compilation terminated.
make: *** [getarch] Error 1
Makefile.system:169: Makefile.conf: No such file or directory
make: *** No rule to make target `Makefile.conf'.  Stop.

but the stdio.h does exist:
find / -name stdio.h /usr/local/arm-toolchain/aarch64-gnu/lib/gcc/aarch64-linux-gnu/5.4.1/include/ssp/stdio.h /usr/local/arm-toolchain/aarch64-gnu/aarch64-linux-gnu/libc/usr/include/stdio.h /usr/local/arm-toolchain/aarch64-gnu/aarch64-linux-gnu/libc/usr/include/bits/stdio.h /usr/local/arm-toolchain/aarch64-gnu/aarch64-linux-gnu/include/c++/5.4.1/tr1/stdio.h
cloud anyone help me? any advice or suggestions will be helpful,thanks.

getarch.c is compiled using HOSTCC.
Check whether stdio.h is available for your HOSTCC.

thanks ashwinyes for your advice.it really works~~~even though i spent 1.5days to slove the problem that build-essentiall couldn't be installed through the apt source offered by inner companny.
thanks again~~~@ashwinyes


az functioapp remove

with reference to https://github.com/Azure/azure-cli/issues/8514
az functionapp cors remove -g {myRG} -n {myAppName} --allowed-origins * doesn't remove all the allowed origins as suggested in the examples
az functionapp cors remove -g {myRG} -n {myAppName} --allowed-origins will clear all the allowed origins

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

ID: 9a3961a2-da0c-5697-b52d-35c8e676537d
Version Independent ID: 3111fdd6-55ed-c1c8-7ac6-c4806a16945c
Content: az functionapp cors
Content Source: src/command_modules/azure-cli-appservice/azure/cli/command_modules/appservice/_help.py
Service: functions
GitHub Login: @rloutlaw
Microsoft Alias: routlaw

@panchagnula what is the intended behavior here?

@shaochen see this known issues on the documentation https://github.com/Azure/azure-cli/issues/8514  if the cors values is not set to * (i.e to allow all then it won't remove this) if you want remove all the values  run the command as az functionapp cors -g {} -n {} --allowed-origins

I found it indeed, as referenced in a github issue.
Thank you for pointing out that the behaviour I've reported is the behaviour you're suggesting.
Hover this is nowhere to be found in the documentation, for which the issue has been raised.
The suggestion is to properly document this "intended behaviour" so people don't need to sherlock holmes it from a github issue through google.
The existing documented example is at the very least ambiguous.

@ankitkumarr

The example need to be updated, so the correct behavior is documented

tracked in https://github.com/Azure/azure-cli/pull/9700

This should be out in Sprint 64, will close when 2.0.68 is released