RA-318: Guest User's Name Can't Be a Space

Description
This modifies the jitsi input field functionality on the premeeting screen so that guest users cannot input just a space for their name; they have to input a character. This works by rejecting the input if the input field only contains a space (i.e. reverts it to being blank).
NOTE: This branch was created off of the feature/jitsi-6689 branch which has the latest version of jitsi, so it should not be merged in until that branch has been merged.
Motivation and context
This resolves the RA-318 bug.
How has this been tested?
This has been tested by deploying to sandbox1, starting a meeting, and attempting to join the meeting as a guest user.
Types of changes

✅ Bug fix (non-breaking change which fixes an issue)
✅ New feature (non-breaking change which adds functionality)

Checklist:

✅ My code follows the code style of this project. [REQUIRED]
✅ All new and existing tests passed. [REQUIRED]

A couple of points:

This is NOT currently based on the feature/jitsi-6689 branch
I see the comment about not using String.trim(), but I believe you should. In particular instead of rejecting a name consisting only of whitespace characters, you only reject a name consisting of a single space character.

I can still enter a name using other whitespace characters, and I can even enter a name consisting of more than one space character. Instead of resetting the name value, you should instead have a function which gets the name by getting the value and trimming it. Then check that name to see if it has a length > 0 and if so you can enable join and use that name.


LR page need to work without shell page like standalone app

Hi Team,
UI Version- 1.97
We successfully created a List report page using CAP + V4LR Page annotations.
However, I want to run the application from index.html without using a shell and have FLP appear in the Home screen.
I modified the index script as shown below.
data-sap-ui-oninit="module:sap/ui/core/ComponentSupport"
commented Shell Container .
Remove: sap.ui.getCore().attachInit(function() {
sap.ushell.Container.createRenderer().placeAt('content');
});

Application loading without FLP look now .

However, the first time I create an entry, it works, but the second time I click the create button, the navigation fails. Every time I start a new record, I start with the first one.
If the LR page loads the data, the Create entry will not work again.

Error :

Debug Error :

Hello, Team could please help me here

Hello @CodeCode7 ,
Thank you for sharing your case. Sorry for delay but I needеа time to check how to proceed with you case since it's not directly related with specific OpenUI5 issue, but with FLP integration. I've created an internal incident<PHONE_NUMBER>. The status of the issue will be updated here in GitHub. If you are SAP customer or partner please use the official channels for support. In OpenUI5 GitHub we are supporting only OpenUI5 and I see from the screenshot that there are Smart controls in your application.
Regards, Diana

Hello @CodeCode7 , Thank you for sharing your case. Sorry for delay but I needеа time to check how to proceed with you case since it's not directly related with specific OpenUI5 issue, but with FLP integration. I've created an internal incident<PHONE_NUMBER>. The status of the issue will be updated here in GitHub. If you are SAP customer or partner please use the official channels for support. In OpenUI5 GitHub we are supporting only OpenUI5 and I see from the screenshot that there are Smart controls in your application. Regards, Diana
👍
Thank you so much for  your help

@Vinod S Nair,   Could you please help here?

As @Shtilianova already mentioned, FLP integration is part of SAPUI5 and not OpenUI5. GitHub is a place for managing issues for OPENUI5 only.
Please, open a ticket in SAP ticket system for managing incidents. Sorry that the issue was not closed earlier.


ignore SCSS settings

How can we reproduce this bug?
Add

and change hr SCSS settings
$hr-width: 100px;
$hr-border: 1px solid $medium-gray;
$hr-margin: 100px auto;

What did you expect to happen?
'hr' element should change its styling according to settings. As far as I see in foundation-emails sources, it should be replaced with

What happened instead?
'hr' settings are ignored. 'hr' element is not replaced with 'table'
What email clients does this happen in?
Dev server

me too

Please try <h-line> in inky. See https://github.com/foundation/inky/blob/develop/lib/inky.js#L29

See also https://github.com/foundation/foundation-emails/blob/develop/scss/components/_typography.scss#L363


Swimming issue / Paper doll suggestion

Please , make it possible to move paper doll to top right or bottom right/left . Would be nice :)
And there's some bugs while swimming in first person at forge version .
And cosmetics button is , for some reason , top right and (i think) should be at the centre when you press esc (forge version)

The swimming has been fixed, adding the other 4 corners will be done soon :D

Actually all of this has is fixed.

yeah , thanks !


Add Irssi under Messenger/IRC Clients

Title speaks.

Thanks a lot!

you're welcome. Happy to contribute...


Allow matching event to pipeline by modified files for GitHub push request

Added changes to trigger pipelinerun for matched files using custom CEL functions for GitHub Push Request

Changes

Submitter Checklist

[ ] ♽  Run make test lint before submitting a PR (ie: with pre-commit, no need to waste CPU cycle on CI
[ ] 📖 If you are adding a user facing feature or make a change of the behavior, please verify that you have documented it
[ ] 🧪 100% coverage is not a target but most of the time we would rather have a unit test if you make a code change.
[ ] 🎁 If that's something that is possible to do please ensure to check if we can add a e2e test.
[ ] 🔎 If there is a flakiness in the CI tests then don't necessary ignore it, better get the flakyness fixed before merging or if that's not possible there is a good reason to bypass it. (token rate limitation may be a good reason to skip).

can we get a unit test please?

Codecov Report

Merging #772 (b16ec50) into main (da4638c) will decrease coverage by 0.09%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main     #772      +/-   ##
==========================================
- Coverage   65.25%   65.16%   -0.10%
==========================================
  Files          75       75
  Lines        4533     4544      +11
==========================================
+ Hits         2958     2961       +3
- Misses       1295     1303       +8
  Partials      280      280

Impacted Files
Coverage Δ

pkg/provider/github/github.go
62.26% <0.00%> (-3.09%)
:arrow_down:

pkg/templates/templating.go
100.00% <0.00%> (ø)

pkg/sort/task_status.go
90.00% <0.00%> (+1.76%)
:arrow_up:

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 da4638c...b16ec50. Read the comment docs.

can we get a unit test please?

Yes will add it :+1:

can we get a unit test please?

Yes will add it +1

Updated PR with UT
PTAL
Thank you


Data table: live demo shows incorrect type token and alignment in expandable row

The data table live demo on the usage tab shows an incorrect type token and alignment for the text in the expandable portion of the row. It should be updated with what we have in the React storybook.
Note: I also have an issue against the react storybook for type alignment issues. Ref: #14240

Replaced with storybook demo https://github.com/carbon-design-system/carbon-website/pull/3716


Enable builtin loaded scripts view in VS Code

see https://github.com/Microsoft/vscode/issues/37767

builtin loaded scripts view is now enabled.


IMS VoIP Server error on LIR select next S-CSCF

Hi,
I´m doing a test based on docker_open5gs files isolating the IMS core  components (pcscf, icscf, scscf, fohss, mysql, dns, rtpengine, ims_base), to have a testbed on GNS3.
Since the tests are performed on a network outside the core network (TEST_NETWORK = <IP_ADDRESS> / 24), I have enabled the NAT related parameters in the pcscf. On the other hand, I intend to use the HOMER SIP Capture docker images to take QoS traces, so I need to make modifications to the RTPENGINE configuration to activate HOMER support.
In the tests that I have carried out based on the attached files, according to the scenario raised, when making the call between alice and bob. I get the error "Server error on LIR select next S-CSCF". I attach the SIP traces (pcap) and the corresponding log. From what I can see, in the icscf the error is the following on the log file (IMS.log):
Line 1514 ERROR:

Please check the authentication mechanism set for bob in HSS.

Hi, I check the authentication mechanism but the problem persist:
This is the hss information for Alice:

This is the hss information for Bob:

And this is the PCAP:
PCAP11112021.zip
IMS11112021.log
I'm using Boghe IMS as client

Now the REGISTER for bob is successful. The call is failing because your UE is behind a NAT.

I´m using this configuration on the P-CSCF:
IP-Adress for incoming SIP-Traffic, in the following format:
SIP / UDP
#listen=udp:PCSCF_IP:5060
listen=udp:PCSCF_IP:5060 advertise PCSCF_PUB_IP:5060
SIP / TCP
#listen=tcp:PCSCF_IP:5060
listen=tcp:PCSCF_IP:5060 advertise PCSCF_PUB_IP:5060
SIP / TCP/TLS
#listen=tls:PCSCF_IP:5061
IPSEC / UDP
##!define IPSEC_LISTEN_ADDR "PCSCF_IP"
#!define IPSEC_LISTEN_ADDR "PCSCF_PUB_IP"
#!define IPSEC_CLIENT_PORT 5100
#!define IPSEC_SERVER_PORT 6100
#!define IPSEC_MAX_CONN 10
IP used in Rx_AAR_Register - IP of this P-CSCF, to be used in the flow for the AF-signaling
##!define RX_AF_SIGNALING_IP "PCSCF_IP"
Uncomment the below line only when UE is behind double NAT (e.g. VoIP calling over WiFi/ CN behind a NAT)
#!define RX_AF_SIGNALING_IP "PCSCF_PUB_IP"
alias=pcscf.IMS_DOMAIN
#!define MY_WS_PORT 80
#!define MY_WSS_PORT 443
#!define PCSCF_URL "sip:pcscf.IMS_DOMAIN:5060"
#!define TCP_PROCESSES 8
#!subst "/NETWORKNAME/IMS_DOMAIN/"
#!subst "/HOSTNAME/pcscf.IMS_DOMAIN/"
#!subst "/PCRF_REALM/EPC_DOMAIN/"
SIP-Address of capturing node, if not set, capturing is disabled.
##!define CAPTURE_NODE "sip:<IP_ADDRESS>:9060"
Allowed IPs for XML-RPC-Queries
##!define XMLRPC_WHITELIST_1 "<IP_ADDRESS>"
##!define XMLRPC_WHITELIST_2 "<IP_ADDRESS>"
##!define XMLRPC_WHITELIST_3 "<IP_ADDRESS>"
Databases:
#!define DB_URL "mysql://pcscf:heslo@MYSQL_IP/pcscf"
##!define DB_URL2 "con2=>mysql://pcscf:heslo@MYSQL_IP/pcscf"
#!define SQLOPS_DBURL "pcscf=>mysql://pcscf:heslo@MYSQL_IP/pcscf"
#! Optional: Server-URL for Websocket-Requests
##!define WEBSOCKET_WEBSERVER "phone.ng-voice.com"
##!define TRF_FUNCTION "trf.IMS_DOMAIN"

Several features can be enabled using '#!define WITH_FEATURE' directives:

*** To run in debug mode:
- define WITH_DEBUG

*** To enable nat traversal execute:
- define WITH_NAT
- define the connection to the RTP-Proxy: RTPPROXY_ADDRESS

*** To force alls calls through the RTP-Proxy
- this will automagically enable NAT-Traversal
- define FORCE_RTPRELAY

*** To enable IPv4/IPv6 Translation (RTPProxy)
- this will automagically enable NAT-Traversal
- define WITH_RTPIPV4

*** To enable TCP support execute:
- define WITH_TCP

*** To enable TLS support execute:
- adjust CFGDIR/tls.cfg as needed
- define WITH_TLS
- this will automagically enable TCP

*** To enable XMLRPC support execute:
- define WITH_XMLRPC
- this will automagically enable TCP

*** To enable anti-flood detection execute:
- adjust pike and htable=>ipban settings as needed (default is
block if more than 16 requests in 2 seconds and ban for 300 seconds)
- define WITH_ANTIFLOOD

*** To enable the Rx-Interface:
- Configure Rx-Diameter-Interface in pcscf.xml
- define WITH_RX

*** To enable a Homer SIP-Capter-Node:
- define CAPTURE_NODE with a proper address

*** To enable support for the SEMS-SBC
- define WITH_SBC
- configure dispatcher-list with a set of SBC's

Enabled Features for this host:
##!define WITH_DEBUG
#!define WITH_NAT
#!define WITH_NATPING
#!define FORCE_RTPRELAY
##!define WITH_TLS
##!define WITH_XMLRPC
##!define WITH_IPBLOCK
##!define WITH_ANTIFLOOD
##!define WITH_RX
##!define WITH_RX_REG
##!define WITH_RX_CALL
#!define WITH_TCP
##!define WITH_RTPIPV4
##!define WITH_SBC
##!define WITH_SBC_CALL
##!define WITH_REGINFO
##!define WITH_RTPPING
##!define WITH_WEBSOCKET
#!define WITH_IPSEC
#!define WITH_IMS_HDR_CACHE
#!define WITH_PING_UDP
#!define WITH_PING_TCP

Dear Herle I'm using the following configuration on the pcscf, it´s ok?

IP-Adress for incoming SIP-Traffic, in the following format:

SIP / UDP

#listen=udp:PCSCF_IP:5060
listen=udp:PCSCF_IP:5060 advertise PCSCF_PUB_IP:5060

SIP / TCP

#listen=tcp:PCSCF_IP:5060
listen=tcp:PCSCF_IP:5060 advertise PCSCF_PUB_IP:5060

SIP / TCP/TLS

#listen=tls:PCSCF_IP:5061

IPSEC / UDP

##!define IPSEC_LISTEN_ADDR "PCSCF_IP"
#!define IPSEC_LISTEN_ADDR "PCSCF_PUB_IP"
#!define IPSEC_CLIENT_PORT 5100
#!define IPSEC_SERVER_PORT 6100
#!define IPSEC_MAX_CONN 10

IP used in Rx_AAR_Register - IP of this P-CSCF, to be used in the flow for the AF-signaling

##!define RX_AF_SIGNALING_IP "PCSCF_IP"

Uncomment the below line only when UE is behind double NAT (e.g. VoIP calling over WiFi/ CN behind a NAT)

#!define RX_AF_SIGNALING_IP "PCSCF_PUB_IP"

alias=pcscf.IMS_DOMAIN

#!define MY_WS_PORT 80
#!define MY_WSS_PORT 443

#!define PCSCF_URL "sip:pcscf.IMS_DOMAIN:5060"

#!define TCP_PROCESSES 8

#!subst "/NETWORKNAME/IMS_DOMAIN/"
#!subst "/HOSTNAME/pcscf.IMS_DOMAIN/"
#!subst "/PCRF_REALM/EPC_DOMAIN/"

SIP-Address of capturing node, if not set, capturing is disabled.

##!define CAPTURE_NODE "sip:<IP_ADDRESS>:9060"

Allowed IPs for XML-RPC-Queries

##!define XMLRPC_WHITELIST_1 "<IP_ADDRESS>"
##!define XMLRPC_WHITELIST_2 "<IP_ADDRESS>"
##!define XMLRPC_WHITELIST_3 "<IP_ADDRESS>"

Databases:

#!define DB_URL "mysql://pcscf:heslo@MYSQL_IP/pcscf"
##!define DB_URL2 "con2=>mysql://pcscf:heslo@MYSQL_IP/pcscf"

#!define SQLOPS_DBURL "pcscf=>mysql://pcscf:heslo@MYSQL_IP/pcscf"

#! Optional: Server-URL for Websocket-Requests
##!define WEBSOCKET_WEBSERVER "phone.ng-voice.com"

##!define TRF_FUNCTION "trf.IMS_DOMAIN"

Several features can be enabled using '#!define WITH_FEATURE' directives:

*** To run in debug mode:

- define WITH_DEBUG

*** To enable nat traversal execute:

- define WITH_NAT

- define the connection to the RTP-Proxy: RTPPROXY_ADDRESS

*** To force alls calls through the RTP-Proxy

- this will automagically enable NAT-Traversal

- define FORCE_RTPRELAY

*** To enable IPv4/IPv6 Translation (RTPProxy)

- this will automagically enable NAT-Traversal

- define WITH_RTPIPV4

*** To enable TCP support execute:

- define WITH_TCP

*** To enable TLS support execute:

- adjust CFGDIR/tls.cfg as needed

- define WITH_TLS

- this will automagically enable TCP

*** To enable XMLRPC support execute:

- define WITH_XMLRPC

- this will automagically enable TCP

*** To enable anti-flood detection execute:

- adjust pike and htable=>ipban settings as needed (default is

block if more than 16 requests in 2 seconds and ban for 300 seconds)

- define WITH_ANTIFLOOD

*** To enable the Rx-Interface:

- Configure Rx-Diameter-Interface in pcscf.xml

- define WITH_RX

*** To enable a Homer SIP-Capter-Node:

- define CAPTURE_NODE with a proper address

*** To enable support for the SEMS-SBC

- define WITH_SBC

- configure dispatcher-list with a set of SBC's

Enabled Features for this host:

##!define WITH_DEBUG
#!define WITH_NAT
#!define WITH_NATPING
#!define FORCE_RTPRELAY
##!define WITH_TLS
##!define WITH_XMLRPC
##!define WITH_IPBLOCK
##!define WITH_ANTIFLOOD
##!define WITH_RX
##!define WITH_RX_REG
##!define WITH_RX_CALL
#!define WITH_TCP
##!define WITH_RTPIPV4
##!define WITH_SBC
##!define WITH_SBC_CALL
##!define WITH_REGINFO
##!define WITH_RTPPING
##!define WITH_WEBSOCKET
#!define WITH_IPSEC
#!define WITH_IMS_HDR_CACHE
#!define WITH_PING_UDP
#!define WITH_PING_TCP

I have found that this error is due to the IMS client, doubango Boghe does not support NAT traversal when registering both Alice and Bob. I have done tests using Jitsi and Zoiper without problems and in the same way I have integrated Homer SIP Capture, this issue can now be closed.


Default WAF rules not that safe. (doesn't check capitals)

Raising this issue here as I am not sure where to raise it but here is a finding on the WAF rules.
In Azure functions API, If I type the URL in all capitals or if I capitalise one letter on the protocol then I am allowed to post the payload:
You can also create a feedback issue here in the repo. If you do this, please make sure your issue lists:

[ ] The relevant Azure service or technology. : WAF
[ ] A link to the published documentation article that you have feedback about.
[ ] Clear, specific feedback that the author can act on.

https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/web-application-firewall/ag/application-gateway-web-application-firewall-portal.md

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

ID: de82b14b-7574-ae63-d155-5ddedfab16fc
Version Independent ID: 8e925358-7916-7573-353b-3f745c860865
Content: Tutorial: Create using portal - Web Application Firewall
Content Source: articles/web-application-firewall/ag/application-gateway-web-application-firewall-portal.md
Service: web-application-firewall
GitHub Login: @vhorne
Microsoft Alias: victorh

Hi @marios-siatis, thanks for bringing this to our attention. I have assigned the issue to the content author to evaluate and update as appropriate

Thank you for your dedication to our documentation.
Unfortunately, we have been unable to review this issue in a timely manner. We sincerely apologize for the delayed response. We are closing this issue. If you feel that the problem persists, please respond to this issue with additional information.
Please continue to provide feedback about the documentation. We appreciate your contributions to our community.
#please-close


Add update time to workflow execution info

Added update time field to workflow execution info

@neil-xie  can you add an explanation as to what this diff is trying to accomplish?

@neil-xie can you add an explanation as to what this diff is trying to accomplish?

Sure! Let me update the description now

I don't really have enough context on this diff. It looks good to me, but please get stamp with someone who's more familiar with this project maybe?


Is there a way to set the PROJ_DIR during installation?

When installing ddev-viteserv, the .ddev/.env file is always created with VITE_PROJECT_DIR=frontend. Is it possible to pass an argument or run a command to change this to something else? Thanks!

I don't know if you can set this before installation, but once you've installed the plugin with
ddev get torenware/ddev-viteserve

the main config file for the plugin, .ddev/.env will be set up, and you can edit it. In your case, you want to change VITE_PROJECT_DIR=frontend  to VITE_PROJECT_DIR=..  Then do
ddev restart
ddev vite-serve start

and start working.


fix modules

dyups module's lua api test cases does not running, because it depends on the new lua nginx module.
$TEST_NGINX_BINARY=/home/fakang.wfk/github/tengine/objs/nginx  prove -v -I tests/nginx-tests/nginx-tests/lib/   ./tests/nginx-tests/cases/dyups.t ./tests/nginx-tests/cases/session_sticky.t
./tests/nginx-tests/cases/dyups.t ...........
1..74
your test dir is /tmp/nginx-test-mJXcUlo4lW at ./tests/nginx-tests/cases/dyups.t line 86.
ok 1 - 2013-02-26 16:51:46
ok 2 - 2013-02-26 17:30:07
ok 3 - 2013-02-26 17:35:19
ok 4 - 2013-02-26 16:51:51
ok 5 - 2013-02-26 16:51:54
ok 6 - 2013-02-26 17:36:42
ok 7 - 2013-02-26 17:36:46
ok 8 - 2013-02-26 17:02:13
ok 9 - 2013-02-26 17:36:59
ok 10 - 2013-02-26 17:40:24
ok 11 - 2013-02-26 17:40:28
ok 12 - 2013-02-26 17:40:32
ok 13 - 2013-02-26 17:40:36
ok 14 - 2013-02-26 17:40:39
ok 15 - 2013-02-26 17:41:09
ok 16 - 2013-02-26 16:51:57
ok 17 - 2013-02-26 16:52:00
ok 18 - 2013-02-26 17:00:54
ok 19 - 2013-02-26 17:42:27
ok 20 - 2013-02-26 17:44:34
ok 21 - 2013-02-26 17:08:00
ok 22 - 2013-02-26 17:08:04
ok 23 - 2013-02-26 17:45:03
ok 24 - 2013-02-26 17:05:20
ok 25 - 2013-02-26 17:05:30
ok 26 - 2013-06-20 17:46:03
ok 27 - 2013-02-28 16:27:45
ok 28 - 2013-02-28 16:27:49
ok 29 - 2013-02-28 16:27:52
ok 30 - 2013-02-28 16:28:44
ok 31 - 2013-02-28 16:23:41
ok 32 - 2013-02-28 16:23:48
ok 33 - 2013-02-28 16:25:32
ok 34 - 2013-02-28 16:25:35
ok 35 - 2013-03-04 15:53:41
ok 36 - 2013-03-04 15:53:44
ok 37 - 2013-03-04 15:53:46
ok 38 - 2013-03-04 15:53:49
ok 39 - 2013-03-05 15:36:40
ok 40 - 2013-03-05 15:37:25
ok 41 - 2013-03-05 16:13:11
ok 42 - 2013-03-05 16:13:23
ok 43 - 2013-03-25 10:29:48
ok 44 - 2013-03-25 10:39:02
ok 45 - 2013-03-25 10:39:28
ok 46 - 2013-03-25 10:49:44
ok 47 - 2013-03-25 10:49:47
ok 48 - 2013-03-25 10:50:41
ok 49 - 2013-03-25 10:49:51
ok 50 - 2014-06-15 07:45:30
ok 51 - 2014-06-15 07:45:33
ok 52 - 2014-06-15 07:45:40
ok 53 - 2014-06-15 07:45:43
ok 54 - 2013-02-26 16:51:46
ok 55 - 2013-02-26 17:30:07
ok 56 - 2013-02-26 17:35:19
ok 57 - 2013-02-26 16:51:51
ok 58 - 2013-02-26 17:02:13
ok 59 - 2013-02-26 17:36:59
ok 60 - 2013-02-26 17:40:24
ok 61 - 2013-02-26 17:41:09
ok 62 - 2013-02-26 17:00:54
ok 63 - 2013-02-26 17:42:27
ok 64 - 2013-02-26 17:45:03
ok 65 - 2013-02-26 17:05:20
ok 66 - 2013-02-26 17:46:03
ok 67 - 2013-02-28 16:27:45
ok 68 - 2013-02-28 16:23:41
ok 69 - 2013-03-04 15:53:41
ok 70 - 2013-03-05 15:36:40
ok 71 - 2013-03-05 15:37:25
ok 72 - 2013-03-05 16:13:11
ok 73 - no alerts
ok 74 - no sanitizer errors
ok
./tests/nginx-tests/cases/session_sticky.t ..
1..40
ok 1 - test insert frist seen
ok 2 - insert with cookie
ok 3 - insert with cookie, maxidle timeout
ok 4 - insert with indirect
ok 5 - insert with indirect -- upstream don't recv cookie
ok 6 - rewrite -- upstream set cookie
ok 7 - rewrite -- upstream set cookie and session_sticky modify the value only
ok 8 - rewrite -- with cookie in request
ok 9 - rewrite -- upstream don't set cookie
ok 10 - prefix -- upstream set cookie
ok 11 - prefix -- with cookie in request
ok 12 - prefix -- upstream don't set cookie
ok 13 - insert with indirect and fallback off
ok 14 - insert with indirct --- frist and fallback off
ok 15 - insert without indirect adn fallback off
ok 16 - insert -- frist and fallback off
ok 17 - rewrite -- fallback off
ok 18 - rewrite -- frist and fallback off
ok 19 - prefix-cookie invailied
ok 20 - prefix -- frist and fallback off
ok 21 - insert -- without domain
ok 22 - insert -- without path
ok 23 - insert--without max-age
ok 24 - insert--without maxidle
ok 25 - insert--without maxidle
ok 26 - insert--without cookie
ok 27 - Not Found
ok 28 - not config session_sticky_hide_cookie
ok 29 - no maxlife
ok 30 - nomaxlif with cookie
ok 31 - indirect--no cookie in request and no cookie to upstream
ok 32 - indirect--with cookie in request and cookie to upstream
ok 33 - direct--no cookie in request and no cookie to upstream
ok 34 - direct--with cookie in request and cookie to upstream
ok 35 - prefix--without maxidle or maxlife
ok 36 - prefix--without maxidle or maxlife
ok 37 - hash=plain
ok 38 - hash=plain, the same real server
ok 39 - no alerts
ok 40 - no sanitizer errors
ok
All tests successful.
Files=2, Tests=114,  5 wallclock secs ( 0.07 usr  0.01 sys +  0.38 cusr  0.14 csys =  0.60 CPU)
Result: PASS

checked for these commit:

modify session_sticky module for nginx-1.15.1.
modify dyups module for nginx-1.15.1.


Fix finding libsodium.so with ruby 2.5

Fixes #25

I'm not sure if it's the right path to look into. It's both in vendor/libsodium/src/libsodium/.libs/libsodium.so and tmp/x86_64-linux/stage/vendor/libsodium/dist/lib/libsodium.so. Former seemed simpler.

I actually understood what's going on there and made a more complete and proper fix:
For some reasons, starting with ruby 2.5, HOST ends up being defined in extconf.rb, thus DIST ends up with a different value. I adjusted the check here to look into the two different DIST possibilities when we used to look inside of only one of those.

there are some ongoing issues with that code. see #24

@tarcieri right, thanks for the notice. doesn't seem to be the same error though, do you think it could be related?
This PR basically fixes the fact that extconf.rb could install the so in two different locations but rbnacl/libsodium.rb was only looking into one of those two locations

Thanks!


Set up the Tox docker container and deploy it on docker hub

[x] Take the Tox Dockerfile from the csvcubed repo.
[x] Deploy the container on docker hub (using github actions). -- Probably from a new repo you create for this purpose.
[x] Once the new container has been pushed to docker hub, you should update the Jenkins file in the csvcubed repo so that it uses this image instead of building from the Dockerfile itself -- make sure to remove the docker file from the repo too!.

https://github.com/GSS-Cogs/csvcubed/pull/465


modified extraction to make a corpus of all annotatedDocs, not one pe…

…r annotatedDoc
I think this fixes the issue that @adarshp found tonight

You beat me to it!  Thanks for using FileUtils.  Well, actually if it is Sourcer instead of Source, then UTF8 standard will be maintained.  Besides, I had to fix my extra bug.

The 200,000 line output for DocN.txt is a little hard to work with.  I broke the file up into ten pieces and am putting them on Google Drive.  This makes more sense for ExtractFromDirectory.  We should have other programs for ExtractFromFile.


SEPG Automated Release - v1.3.0

SEPG Details
Release Build Link: https://sou-jenkins2.swinfra.net/job/Auto-Release/577/
Build Token: github.com/FileAnalysisSuite/adaptersdk-schema/main/395fe9a008154f9dfce6d4fb36bd6c7095de59fe
Versioning Behaviour: Roll on to next minor
Artifacts For Release
Maven

io.github.fileanalysissuite.adaptersdk.schema:adaptersdk-schema-aggregator:1.3.0-226(pom,pom.asc)
io.github.fileanalysissuite.adaptersdk.schema:adaptersdk-schema-java-lib:1.3.0-226(jar.asc,sources.jar.asc,sources.jar,javadoc.jar.asc,jar,pom,javadoc.jar,pom.asc)
io.github.fileanalysissuite.adaptersdk.schema:adaptersdk-schema-dotnet:1.3.0-226(pom,pom.asc)
io.github.fileanalysissuite.adaptersdk.schema:adaptersdk-schema-java-interfaces:1.3.0-226(sources.jar,pom.asc,javadoc.jar,sources.jar.asc,pom,jar,jar.asc,javadoc.jar.asc)
io.github.fileanalysissuite.adaptersdk.schema:adaptersdk-schema-java:1.3.0-226(pom,pom.asc)
io.github.fileanalysissuite.adaptersdk.schema:adaptersdk-schema-java-jsonbuilder-jackson:1.3.0-226(javadoc.jar.asc,sources.jar.asc,pom.asc,pom,javadoc.jar,sources.jar,jar.asc,jar)

NuGet

<EMAIL_ADDRESS>(download)
<EMAIL_ADDRESS>(download)

 Build Stage
Action
Status

Release Checks
completed
:heavy_check_mark:

Gather Release Data

:white_small_square:

QA Documentation Site Deployment

:white_small_square:

QA Deployment Branch Promotion

:white_small_square:

Docker Image Promotion

:white_small_square:

Maven Artifact Promotion (Closed Source)

:white_small_square:

NuGet Artifact Promotion

:white_small_square:

Artifactory Release Artifact Tagging

:white_small_square:

Generic Artifact Promotion

:white_small_square:

Maven Artifact Promotion (Open Source)

:white_small_square:

Maven Staging Repository Removal (Open Source)

:white_small_square:

Git Tagging

:white_small_square:

Git Release

:white_small_square:

Git Release Asset Deployment

:white_small_square:

Pull Request Merge

:white_small_square:

Release Branch Deletion

:white_small_square:

view the build log here

RETRY

Retrying Auto-Release.....
Release Build Continuation: https://sou-jenkins2.swinfra.net/job/Auto-Release/578/

Build Stage
Action
Status

Release Checks
in progress
:clock130:

Gather Release Data

:white_small_square:

QA Documentation Site Deployment

:white_small_square:

QA Deployment Branch Promotion

:white_small_square:

Docker Image Promotion

:white_small_square:

Maven Artifact Promotion (Closed Source)

:white_small_square:

NuGet Artifact Promotion

:white_small_square:

Artifactory Release Artifact Tagging

:white_small_square:

Generic Artifact Promotion

:white_small_square:

Maven Artifact Promotion (Open Source)

:white_small_square:

Maven Staging Repository Removal (Open Source)

:white_small_square:

Git Tagging

:white_small_square:

Git Release

:white_small_square:

Git Release Asset Deployment

:white_small_square:

Pull Request Merge

:white_small_square:

Release Branch Deletion

:white_small_square:

view the build log here

Retrying Auto-Release.....
Release Build Continuation: https://sou-jenkins2.swinfra.net/job/Auto-Release/579/

Build Stage
Action
Status

Release Checks
in progress
:clock130:

Gather Release Data

:white_small_square:

QA Documentation Site Deployment

:white_small_square:

QA Deployment Branch Promotion

:white_small_square:

Docker Image Promotion

:white_small_square:

Maven Artifact Promotion (Closed Source)

:white_small_square:

NuGet Artifact Promotion

:white_small_square:

Artifactory Release Artifact Tagging

:white_small_square:

Generic Artifact Promotion

:white_small_square:

Maven Artifact Promotion (Open Source)

:white_small_square:

Maven Staging Repository Removal (Open Source)

:white_small_square:

Git Tagging

:white_small_square:

Git Release

:white_small_square:

Git Release Asset Deployment

:white_small_square:

Pull Request Merge

:white_small_square:

Release Branch Deletion

:white_small_square:

view the build log here

Retrying Auto-Release.....
Release Build Continuation: https://sou-jenkins2.swinfra.net/job/Auto-Release/580/

Build Stage
Action
Status

Release Checks
in progress
:clock130:

Gather Release Data

:white_small_square:

QA Documentation Site Deployment

:white_small_square:

QA Deployment Branch Promotion

:white_small_square:

Docker Image Promotion

:white_small_square:

Maven Artifact Promotion (Closed Source)

:white_small_square:

NuGet Artifact Promotion

:white_small_square:

Artifactory Release Artifact Tagging

:white_small_square:

Generic Artifact Promotion

:white_small_square:

Maven Artifact Promotion (Open Source)

:white_small_square:

Maven Staging Repository Removal (Open Source)

:white_small_square:

Git Tagging

:white_small_square:

Git Release

:white_small_square:

Git Release Asset Deployment

:white_small_square:

Pull Request Merge

:white_small_square:

Release Branch Deletion

:white_small_square:

view the build log here

Retrying Auto-Release.....
Release Build Continuation: https://sou-jenkins2.swinfra.net/job/Auto-Release/581/

Build Stage
Action
Status

Release Checks
in progress
:clock130:

Gather Release Data

:white_small_square:

QA Documentation Site Deployment

:white_small_square:

QA Deployment Branch Promotion

:white_small_square:

Docker Image Promotion

:white_small_square:

Maven Artifact Promotion (Closed Source)

:white_small_square:

NuGet Artifact Promotion

:white_small_square:

Artifactory Release Artifact Tagging

:white_small_square:

Generic Artifact Promotion

:white_small_square:

Maven Artifact Promotion (Open Source)

:white_small_square:

Maven Staging Repository Removal (Open Source)

:white_small_square:

Git Tagging

:white_small_square:

Git Release

:white_small_square:

Git Release Asset Deployment

:white_small_square:

Pull Request Merge

:white_small_square:

Release Branch Deletion

:white_small_square:

view the build log here

Retrying Auto-Release.....
Release Build Continuation: https://sou-jenkins2.swinfra.net/job/Auto-Release/582/

Build Stage
Action
Status

Release Checks
in progress
:clock130:

Gather Release Data

:white_small_square:

QA Documentation Site Deployment

:white_small_square:

QA Deployment Branch Promotion

:white_small_square:

Docker Image Promotion

:white_small_square:

Maven Artifact Promotion (Closed Source)

:white_small_square:

NuGet Artifact Promotion

:white_small_square:

Artifactory Release Artifact Tagging

:white_small_square:

Generic Artifact Promotion

:white_small_square:

Maven Artifact Promotion (Open Source)

:white_small_square:

Maven Staging Repository Removal (Open Source)

:white_small_square:

Git Tagging

:white_small_square:

Git Release

:white_small_square:

Git Release Asset Deployment

:white_small_square:

Pull Request Merge

:white_small_square:

Release Branch Deletion

:white_small_square:

view the build log here

Retrying Auto-Release.....
Release Build Continuation: https://sou-jenkins2.swinfra.net/job/Auto-Release/584/

Build Stage
Action
Status

Release Checks
in progress
:clock130:

Gather Release Data

:white_small_square:

QA Documentation Site Deployment

:white_small_square:

QA Deployment Branch Promotion

:white_small_square:

Docker Image Promotion

:white_small_square:

Maven Artifact Promotion (Closed Source)

:white_small_square:

NuGet Artifact Promotion

:white_small_square:

Artifactory Release Artifact Tagging

:white_small_square:

Generic Artifact Promotion

:white_small_square:

Maven Artifact Promotion (Open Source)

:white_small_square:

Maven Staging Repository Removal (Open Source)

:white_small_square:

Git Tagging

:white_small_square:

Git Release

:white_small_square:

Git Release Asset Deployment

:white_small_square:

Pull Request Merge

:white_small_square:

Release Branch Deletion

:white_small_square:

view the build log here

Retrying Auto-Release.....
Release Build Continuation: https://sou-jenkins2.swinfra.net/job/Auto-Release/586/

Build Stage
Action
Status

Release Checks
in progress
:clock130:

Gather Release Data

:white_small_square:

QA Documentation Site Deployment

:white_small_square:

QA Deployment Branch Promotion

:white_small_square:

Docker Image Promotion

:white_small_square:

Maven Artifact Promotion (Closed Source)

:white_small_square:

NuGet Artifact Promotion

:white_small_square:

Artifactory Release Artifact Tagging

:white_small_square:

Generic Artifact Promotion

:white_small_square:

Maven Artifact Promotion (Open Source)

:white_small_square:

Maven Staging Repository Removal (Open Source)

:white_small_square:

Git Tagging

:white_small_square:

Git Release

:white_small_square:

Git Release Asset Deployment

:white_small_square:

Pull Request Merge

:white_small_square:

Release Branch Deletion

:white_small_square:

view the build log here


[SPARK-36231][PYTHON] Support arithmetic operations of decimal(nan) series

What changes were proposed in this pull request?
This patch has changes as below to follow the pandas behavior:

Add nan value process in _non_fractional_astype: Follow the pandas to_string covert method, it should be "NaN" rather than str(np.nan)("nan")， which is covered by self.assert_eq(pser.astype(str), psser.astype(str)).
Add null value process in rpow, which is covered by def test_rpow(self)
Add index_ops.hasnans in astype, which is covered by test_astype.

This patch also move numeric_w_nan_pdf into numeric_pdf, that means all float_nan/decimal_nan separated test case have been cleaned up and merged into numeric test.
Why are the changes needed?
Follow the pandas behavior
Does this PR introduce any user-facing change?
Yes, correct the null value result to follow the pandas behavior
How was this patch tested?
ut to cover all changes

cc @HyukjinKwon @xinrong-databricks

After this patch, we can finally close the SPARK-36000 .

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/144369/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/48844/

Test build #145217 has started for PR 34314 at commit 6bf68b1.

Test build #145217 has finished for PR 34314 at commit 6bf68b1.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/145217/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/49687/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/49687/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/49687/

Merged to master.

@Yikun, I am very sorry but I realised that this patch breaks the test cases with lower pandas versions (because it requires to have https://pandas.pydata.org/pandas-docs/stable/whatsnew/v1.3.0.html#missing). Decimal("NaN") is not considered as null in old pandas versions, and it makes a bunch of related failures.
I was preparing a followup with, for example an approach as below:
-                    nullable=bool(col.isnull().any()),
+                    nullable=bool(col.isnull().any())
+                    # To work around https://github.com/pandas-dev/pandas/pull/39409
+                    | bool(
+                        col.map(lambda x: isinstance(x, decimal.Decimal) and math.isnan(x)).any()
+                    ),

However, then the test fails because of difference behaviours in old pandas versions.
While technically we can make a followup, please let me just revert it to make it easier to move forward - I hear complaints about that the tests are being failed from here and there.

@HyukjinKwon Thanks for your help, and one more question, what's the mainly version of pandas should be tested and supported? Should we announce it in somewhere, and then add the test to install specific pandas version in CI to do an extra check?

It's actually documented here; https://github.com/apache/spark/blob/master/python/setup.py#L115.
We should probably have to bump up .. ideally we should test all the combinatins just like other python projects .. but we can't do this due to the resource problem in GA 😢

Testing on 1.1.x or 1.2.x should be good enough for the fix itself.

We should probably have to bump up .. ideally we should test all the combinatins just like other python projects .. but we can't do this due to the resource problem in GA.

@HyukjinKwon OK, thanks! That means we soulld test it after v0.23.2. I will address soon. : )

Testing on 1.1.x or 1.2.x should be good enough for the fix itself.

OK, thanks for reminder.

@Yikun, if you're stuck to support this with old pandas versions, we can just conditionally run the tests with only pandas 1.3+ for now

if you're stuck to support this with old pandas versions
@HyukjinKwon I do some simple test yesterday, there are many test case failed with decimal("Nan")

we can just conditionally run the tests with only pandas 1.3+ for now

Code and test should also only support 1.3+? right?

yeah, that is fine because it already doesn't work with 1.2 and 1.1 and no regression.


Repository restructuration

This repository will finally hold a collection of hardware IPs for cryptographic operations, starting with sha1 in its basic form.
A RTL design will be proposed for each hardware IP and a testbench will be provided as well. As planned for the sha1 IP, a physical design flow for either ASIC or FPGA designs will be attempted using open source flows. The goal is to reuse the same philosophy and components as much as possible.
Break down in several tasks to rework the repository:

[x]  Restructure the files: nested directories in hw/ and tb/ holding the sha1 design must be created
[x]  Update CI to have actions for each IPs
[x]  Rework the register interface and make it into its own generic module to be reused in other designs
[x]  Update README.md
[x]  When all of the above is done, change the repo's name: current ideas are cryptopen, cryptoforge, sechwa, openhwa

On the other hand, we could list other algorithms we want to implement. I propose we finish off the secure hash algorithm series and explore other options after.

sha256
sha3

Restructuration done and CI flow not broken, closing.


Update Recipes to use the generic Robot class instead of the specific…

… RyanteckRobot
Fixes #288

Current coverage is 72.30%

Merging #290 into master will not affect coverage as of 95b6a46

@@            master   #290   diff @@
=====================================
  Files           28     28
  Stmts         4113   4113
  Branches         0      0
  Methods          0      0
=====================================
  Hit           2974   2974
  Partial          0      0
  Missed        1139   1139

Review entire Coverage Diff as of 95b6a46

Powered by Codecov. Updated on successful CI builds.


can this code to rasspberry pi 3?

can device used microphone?

Hi,
I don't have an RPi 3 so I cannot confirm but my instinct says that it will work with 99% of probability.
Br,


search.js: Escape the string passed to the jquery selector.

Fixes referencing ids containing special characters.

IMHO it'd be better to use CSS.escape() with the polyfill for browsers where it's unavailable.

:+1: Agreed, I'd much prefer a pre-written escape function (whether that's CSS.escape, or something else) as opposed to a homemade regex. If you could also repoint this to the dev branch instead of master that would be great.
Otherwise, this looks like an important and good change. Thanks for contributing!

Closed in favor of #208 — thanks for helping report this bug!


Make external link small and middle aligned

Fixes

https://issues.redhat.com/browse/RHTAPBUGS-242
Description

Middle aligning external link and making it small
Type of change

[ ] Feature
[x] Bugfix
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

Screen shots / Gifs for design review

vs Earlier

How to test or reproduce?

Browser conformance:

[x  Chrome
[ ] Firefox
[ ] Safari
[ ] Edge

@abhinandan13jan can we not use our ExternalLink component for this?

@abhinandan13jan I think we need to target main-next branch

@christianvogt @rottencandy https://github.com/openshift/hac-dev/pull/658 main-next


ProcessUnexpectedlyTerminatedException

I tried some hello world code in your readme.
and i got this error
Nesk/Rialto/Exceptions/ProcessUnexpectedlyTerminatedException with message 'The process has been unexpectedly terminated.'
im trying in tinker environment
use Nesk\Puphpeteer\Puppeteer;
$puppeteer = new Puppeteer;
$browser = $puppeteer->launch(); // here the exception triggered

what did i do wrong?

You're using Laravel Tinker? This might be linked to an issue I already had with PsySH (which Tinker is based on), process statuses aren't properly retrieved, you have to disable the usePcntl option.
See bobthecow/psysh#441 and how to create a PsySH configuration.


fix triton attention bug

The implementation of Triton does not carry out log2 scaling for bias, resulting in a large error. After correction, I can obtain an error with an absolute value <0.015 in my test here.

Thank you for the PR @zhanglei1172! Can you also add the test that you used to build this?
Just to make sure you won't think I forgot about this, I'm going to be on vacation until November 27th starting today. I'll review it again once I'm back! Thank you again for sending a PR!

Hey @zhanglei1172 - I merged this as part of https://github.com/pytorch-labs/segment-anything-fast/pull/108 . I was going to push to this pull request, but didn't want to push to your fork's main branch and interfere with something there. Thank yo for filing this PR and fixing the issue!


Fix sis-oodikone showing too much credits on student statistics

See e.g. 014092253
oodi-oodikone:

sis-oodikone:

examples of courses which are calculated multiple times:

laskennan mallit (original failed, 5 credit --> then success, 5 credits)
tietorakenteet ja algoritmit (original success, 5 credits --> then success, 5 credits)


[Information Request] docker image update policy

Hello and thank you for all the amazing work!
We would like to understand the policy behind updating images in quay.io/tnozicka/openshift-acme.
When are images pushed and updated?
Thank you very much again!

/remove-lifecycle stale

Hi @maorfr,
thanks and sorry this slipped out of my radar. I've updated the issue template a while back to automatically cc me.
The images are built from master and pushed to registry.svc.ci.openshift.org/openshift-acme/0.9 (tags controller, exposer) right after a merge to master happens.
https://github.com/openshift/release/blob/02ba446/ci-operator/config/tnozicka/openshift-acme/tnozicka-openshift-acme-master.yaml
It is being mirrored to quay.io in about an hour it think by this spec
https://github.com/openshift/release/blob/02ba446e097581806a3ec25345ede712486afc8a/core-services/image-mirroring/tnozicka/mapping_tnozicka_openshift-acme

thanks a lot @tnozicka.
cc @rporres

Hi @tnozicka. Could you explain the reason behind not having versioned tags? You're only keeping a sort of latest and 0.9 tags for exposer and controller components...

Gentle poke @tnozicka, also interested.

/remove-lifecycle stale

/lifecycle stale


Change group name for operations path, and rename response type definition

Change group name for operations path, and rename response type definition so that it does not conflict with the group name. This seems to be a common pattern in a lot of RPs and makes more sense.
PR information

[X] The title of the PR is clear and informative.
[X] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[X] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[ ] If applicable, the PR references the bug/issue that it fixes.
[X] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[X] I have read the contribution guidelines.
[X] My spec meets the review criteria:

[X] The spec conforms to the Swagger 2.0 specification.
[X] The spec follows the guidelines described in the Swagger checklist document.
[X] Validation tools were run on swagger spec(s) and have all been fixed in this PR.

Automation for azure-sdk-for-go

Automation for azure-sdk-for-python

@marstr None of the Travis CI build jobs seem to have started since I submitted this. Any known issues that require me to do something to get this going?

Note: No SDK was generated/published yet for this, hence the method name and response type changes will not effect any customers. I wanted to do this change before I start generating SDKs, which is the next step for us.

@marstr Not sure I understand the change you are requesting. These went in this repo for the first time two days ago and I was not asked to make any changes to the folder structure when reviewed. Please see https://github.com/Azure/azure-rest-api-specs/pull/2523 . Could you please sync up with @sarangan12 and/or @salameer ?


AppImages and '.deb' support

Is your feature request related to a problem? Please describe.
I prefer AppImages and '.deb' packages rather than flatpak.
Describe the solution you'd like
I'd like to be able to use unsnap to automatically remove all snaps from my system and then install the equivalent AppImages or '.deb' packages. I'd be nice to have a fallback system such that if a preferred format isn't available or found, but for another second or third format that package is available, then unsnap would suggest that alternative instead.
Describe alternatives you've considered
Having to manually reinstall everything in another software format; or having to write some kind of script to do that; which feels strange since in my humble opinion unsnap should be capable of doing that.
Bonus
I believe utilities such as AppMan or Pacstall could be helpful to achieve this goal; in addition to, of course, the API of 'apt'.
Thank you for your time and this wonderful software! 🥰

I think the thing would be to have a clear "path" for non-snaps... like what takes priority... if there is a flatpak AND a DEB for Foobar App? ... what if there is no DEB (sort of ..) but there is a PPA for it?  Official PPA by the devs or not? (some people may not want to load their system up with PPAs anymore than using Flatpaks.  IF there is a PPA and a Flatpak for Foobar App ... what if the Flatpak is third party (vs the dev) and the dev posts instructions to the PPA ....  should there be a question to the user and let the user choose?
I think these things would have to be figured out if not done already just so adding support for non-Flatpaks (if added at all) would be easier and at least clear to unsnap devs or anyone contributing.


BeanCreationException

I'm trying to integrate Spring Boot Vaadin (https://github.com/peholmst/vaadin4spring) with Vaadin's Dashboard Demo Code (https://github.com/vaadin/dashboard-demo). The only thing modification I made was add the annotation "@VaadinUI" in the DashboardUI class. I checked in my code using the branch "integrate-vaadin-dashboard-demo-project".
I get the error message: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.springframework.boot.context.properties.ConfigurationPropertiesBindingPostProcessor': Invocation of init method failed; nested exception is java.lang.NoClassDefFoundError: javax/validation/ParameterNameProvider.
I'm not really sure what the message means. Can somebody explain it and come up with a resolution to the error message.
Gist Error Output:
https://gist.github.com/anonymous/43d602c1105e00d4d7d6
Clone Url:
https://github.com/caritos/pangolin.git
Branch:
integrate-vaadin-dashboard-demo-project

My guess is there is an older version of the Bean Validation API on your classpath. See http://stackoverflow.com/questions/14730329/jpa-2-0-exception-to-use-javax-validation-package-in-jpa-2-0 for more information.

see them pom.xml of the security-sample, please add the following dependency to your pom.
<dependency>
    <groupId>javax.validation</groupId>
    <artifactId>validation-api</artifactId>
    <version>1.1.0.Final</version>
</dependency>

After adding this dependency all should work fine.
@closed


An application with the camunda-starter and the connector-bundle tries to connect to Operate

Describe the bug
I have a Spring Boot application that depends on the latest spring-boot-starter-camunda in version 8.2.1 and on the connector-runtime-bundle.
Since version 0.19.0 of the connector-runtime-bundle, the Spring Boot application tries to connect to an Operate API. Since I don't run an Operate instance, the application fails on startup. I see no way to disable the Operate client.
In version 0.18.2 of the connector-runtime-bundle, the Spring Boot application doesn't connect to Operate and starts as expected.
To Reproduce
I created a simple repository to reproduce the issue here: https://github.com/saig0/camunda-connectors-operate-issue
Expected behavior
The Spring Boot application doesn't connect automatically to Operate.
Or, at least, I can disable the Operate client.
Environment (please complete the following information):

spring-boot-starter-camunda: 8.2.1
connector-runtime-bundle: 0.19.2
spring-boot: 2.7.8

Additional context
This issue affects Zeebe-Play. We are not able to update to the latest connectors bundle.
From the perspective of Zeebe-Play, it would be useful to have the option to switch the implementation that connects to Operate. We want to use inbound connectors but provide a different source for the deployed processes than the Operate API, for example, by providing an interface for the process importer.

@chillleader is this issue related to #399?

Closed and linked as the runtime has been moved to the connectors-bundle: https://github.com/camunda/connectors-bundle/issues/588

Hey @saig0, in the latest Connectors release we moved all Connectors functionality out of Spring Zeebe to our mono repo. To add connectors (including Zeebe & Operate clients) as a spring boot starter, please use the following dependency from now on:
<dependency>
    <groupId>io.camunda.connector</groupId>
    <artifactId>spring-boot-starter-camunda-connectors</artifactId>
    <version>0.19.2</version>
</dependency>

When using this dependency, you can use the following combination of properties to disable operate connectivity:
camunda.connector.polling.enabled=false
operate.client.enabled=false

I saw you already tried it in your example, but I just tested it with the new spring boot starter and it works for me. I suspect that the issue in your example is that connectors configurations are now gone from the spring-boot-starter-camunda and properties are therefore not resolved.

@chillleader nice catch. :tada:
I can confirm the workaround. :+1: I added an empty application.properties file next to the application.yml file. Then, the application starts and doesn't try connecting to Operate. :rocket:


Unexpected, Misleading mypy Failures After pandas-stubs Update: DataFrame.from_dict() Behavior

Describe the bug
The DataFrame.from_dict() method allows parsing lists of dictionaries, where each dictionary is interpreted as a single row. However, this behavior is not reflected in the typed method signatures coded in pandas-stubs. We use that behavior and add # type: ignore comments to suppress mypy errors.
This worked without issue up until pandas-stubs version <IP_ADDRESS>316, but with the update to version <IP_ADDRESS>514, it leads to unexpected mypy failures, see below. The specific change responsible might be this commit.
To Reproduce

Provide a minimal runnable pandas example that is not properly checked by the stubs.

import pandas as pd

# %% mypy error Returning Any from function declared to return "int"  [no-any-return]

def f() -> int:
    b = [
        {"key1": "value1", "key2": 42},
        {"key1": "value2", "key2": 123},
    ]
    df = pd.DataFrame.from_dict(b)  # type: ignore
    return df.shape[0]

Indicate which type checker you are using (mypy or  pyright).

mypy

Show the error message received from that type checker while checking your example.

✕ mypy failed.
17:19:33.84 [ERROR] Completed: Typecheck using MyPy - mypy - mypy failed (exit code 1).
src/python/mdl-data-insertion/mdl_data_insertion/util/typing_problem.py:12: error: Returning Any from function declared to return "int"  [no-any-return]
Found 1 error in 1 file (checked 1 source file)

Please complete the following information:

OS: MacOS
OS Version 14.5 (23F79)
python version 3.10.13
version of type checker: 1.9.0
version of installed pandas-stubs: <IP_ADDRESS>514

Btw. the following example works:
b = [
    {"key1": "value1", "key2": 42},
    {"key1": "value2", "key2": 123},
]
df = pd.DataFrame.from_dict(b)  # type: ignore
i: int = df.shape[0]

You wrote:

The DataFrame.from_dict() method allows parsing lists of dictionaries

If I look at the docs https://pandas.pydata.org/pandas-docs/stable/reference/api/pandas.DataFrame.from_dict.html , it doesn't say that a list of dict is allowed.  So while that may work, that may be a pandas bug or a documentation bug.  Can you create an issue in pandas about the docs of to_dict() and see what the pandas core team has to say?

Related to #929 .

You wrote:

The DataFrame.from_dict() method allows parsing lists of dictionaries

If I look at the docs https://pandas.pydata.org/pandas-docs/stable/reference/api/pandas.DataFrame.from_dict.html , it doesn't say that a list of dict is allowed. So while that may work, that may be a pandas bug or a documentation bug. Can you create an issue in pandas about the docs of to_dict() and see what the pandas core team has to say?

Sure!

Created a pandas issue, see https://github.com/pandas-dev/pandas/issues/58862.


Content does not play

My service provider has banned Ne...ix From my Technicolor tv box, download (kodi 20.3)
Install repository y.castagnait-2.0.1.zip To see my content and I get the following error

Please report issues with the Netflix addon to its developer:
https://github.com/CastagnaIT/plugin.video.netflix/issues


Define the lambda function name

Is your feature request related to a problem? Please describe.
The name of the lambda function is a random string.
Describe the solution you'd like
Can I define my own name in yml?

Hi Daniel,
When will we have the next version with the support of the lambda name?
Thanks
Gary

I don’t think this would be too difficult to do. How about giving us a PR 😃
On Sat, Nov 16, 2019 at 11:56 AM Gary Zhang<EMAIL_ADDRESS>wrote:

Hi Daniel,
When will we have the next version with the support of the lambda name?
Thanks
Gary
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/danielcondemarin/serverless-next.js/issues/232?email_source=notifications&email_token=AALXKRFXTOJAN4ZXX6222VTQUBGAJA5CNFSM4JLIMGT2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEEHZHXA#issuecomment-554669020,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AALXKRHWMVPZLOPOQP2ZMVLQUBGAJANCNFSM4JLIMGTQ
.

--
Barry Steyn
Blog http://doctrina.org LinkedIn http://ca.linkedin.com/in/barrysteyn
GitHub https://github.com/barrysteyn

Hi
I'm tempted to start working on this, but need a little guidance. Would this imply adding a name property here and here?

@marcoschicote Yes it would be in those 2 places.
We need to make sure these works across deployments:
npx serverless deploy
npx serverless remove
npx serverless deploy # using the same name
Unfortunately the lambda@edge functions are not deleted on serverless remove. This is because of the time it takes for the cloudfront distribution to delete etc. Considering this, we need to check if reusing the same function name across multiple deployments works fine.

@marcoschicote Appreciate the help on this improvement!
Thanks lot
Gary

@marcoschicote Yes it would be in those 2 places.
We need to make sure it works across deployments:
npx serverless deploy
npx serverless remove
npx serverless deploy # using the same name
Unfortunately the lambda@edge functions are not deleted on serverless remove. This is because of the time it takes for the cloudfront distribution to delete etc. Considering this, we need to check if reusing the same function name across multiple deployments works fine.

Not sure I follow. Are you deleting the lambdas when a new deployment is generated? O generating new content for the same lambdas and uploading it?

@marcoschicote, the cloudfront interacts with Lambda@Edge essentially means that we do not have control over when they are deleted. What happens is that cloudfront get's removed, and AWS says that sometime after CF is removed, the lambdas will get removed (normally within a few hours).
With the above in mind, the problem becomes that if you deploy with named lambdas, then subsequently remove your deployment, you would need to wait until AWS has removed those lambdas in order to redeploy with the same name. Unless of course, we can instruct AWS to just reuse the lambdas that are already present.

@barrysteyn  and @marcoschicote, will the lambda always use the initial name during each deployment? If yes,  deleting lambda should be only worried when we delete the whole deployment right? If this is the case, IMO it is totally fine to have a named lambda and wait for it to be deleted before cleaning up anything else manually.
Thanks
Gary

@barrysteyn  and @marcoschicote, will the lambda always use the initial name during each deployment? If yes,  deleting lambda should be only worried when we delete the whole deployment right? If this is the case, IMO it is totally fine to have a named lambda and wait for it to be deleted before cleaning up anything else manually.
Thanks
Gary

Hi, is it possible to define part of the lambda function name? I understand the necessity to generate random function names, but we use Dynatrace for monitoring and that requires us to attach handlers to lambda function names. This would also be possible to do with a regex, so if we had a partial pattern to look for (e.g. next-serverless-$random, that would make it a bit easier for us.
Thanks!

I agree with @doque
I came here to suggest using some sort of hash/UUID appended to the custom function name (similar to how next's own build IDs are generated). Subsequently, have the generated UUID could be output in some fashion so that dependent services may update themselves as needed with each newly named deployment.


[video_player] Fix persisting of errorDescription even after successful reinitialize

This PR fixes bug which persist errorDescription even after successful initialize
https://github.com/flutter/flutter/issues/82772
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the relevant style guides and ran the auto-formatter. (Unlike the flutter/flutter repo, the flutter/plugins repo does use dart format.)
[x] I signed the CLA.
[x] The title of the PR starts with the name of the plugin surrounded by square brackets, e.g. [shared_preferences]
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy, or this PR is exempt from version changes.
[x] I updated CHANGELOG.md to add a description of the change, following repository CHANGELOG style.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is test-exempt.
[x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

@IlyaMax Once you resolve the conflicts here, we can get this landed. (GitHub isn't allowing it from the UI for some reason.)


Ladybird news: are there news?

So, I checked, and news appear to be here:
https://ladybird.org/#news
Now compare it to GraalVM news:
https://medium.com/graalvm
I am not saying ladybird should be like GraalVM in regards to news. But, one thing that I think
is currently better in regards to GraalVM is that they write articles, with a date, and also show the
date at once (though they use medium.com, which is a negative, but here I focus just on the content,
not where it is hosted). That way we can look after, say, 8 months (we all may be busy meanwhile) and
look at what is new.
Of course ldaybird is newer and more recentish, so we can not expect the same article series
and blog entries, but I am thinking more long term. If you look at the current articles there,
none of those is time-stamped - at the least not when you look at it on https://ladybird.org/#news.
So I think the first change should be a mandatory timestamp right there, somewhere next to
those articles. That way we can look at things chronologically. The time IS showing up in the
individual article, so this is only a display issue. Hence convenience.
Also, aside from this, I would suggest to the ladybird devs that every once in a while there is
some summary over the development. This does not have to happen every week, not even
ever month, mind you. It does not have to happen regularly as such either. But I think something
that may be managable, would be nice, and just summarizes the main changes. Say, once every
three months, or once every six months, may be a good compromise. That way people can be
updated quite quickly. At any rate, thank you for reading this suggestion; it can be closed once
one or the other main ladybird dev has a look at it.

There are monthly newsletters, e.g. https://ladybird.org/newsletter/2024-07-31/
They are not currently accessible from the home page, but there is an open issue on the website repo to do so, and to improve newsletters in general:
https://github.com/LadybirdBrowser/ladybird.org/issues/19


[FEATURE] Theme Build: Add compress option to minify output

Coverage increased (+0.002%) to 85.928% when pulling cb5132258bba2cc2bed8b9163c7bb2aec88b58f0 on theme-build-compress-option into df7c7898e0b260379a3e531c40e4e7492f5091cd on master.

This now by default activates the compress option when running a build, which is the expected behavior I think.
The server will still serve the "debug" CSS.

Done


Causal regularization in training

We want to promote causal parametric configurations while not excessively compromising on accurately reproducing the data generating process. Hence we want to regularize the loss function in the training with a causal bias term.

Done.


Fix quilt test TEST-FILL-DELAYS-FENCE-EXPANSION

It was observed that one of the cl-quil/quilt tests was failing. I'm not sure how this got through the original PR process (perhaps I goofed something in a rebase??), but here's an easy fix. It's worth noting two things:

As far as I know, cl-quil/quilt is not currently used by anyone.
The change here reflects the minor work needed to get the test to pass, and it is at least consistent with the stated intent of the analysis pass (previously it was inserting a spurious DELAY). But I'm not otherwise verifying the correctness of cl-quil/quilt with respect to the proposed Quilt standard or the Rigetti pidgin implementation.

There's another Quilt test, test-definition-signature, that fails under some circumstances due to how the hash method for frames is currently implemented. That may be addressed in a separate PR.

On second glance, this is probably a consequence of the system-dependent behavior of the frame hash function. Closing for now.


[FEAT] JCE support for actors text fields (i.e. bio)

Is your feature request related to a problem? Please describe.
Currently JCE is of no use on actors.
Describe the solution you'd like
Enable JCE on actors text fields (i.e. bio)
Describe alternatives you've considered
Best way imo would be to enable JCE on the tinymce used by Foundry rather than it currently works. This would enable it for every text fields which allow source view. At the same time it would be system independent. Systems might have other things than just bio, targeting the tinymce would make it a) much easier to use (no need to activate it first) and more versatile in the long run.

Good idea. I can't believe I never thought of this 🙂


Update CustomPantheon

idk why you needed to merge in order to change a link, sha and version number, but i can merge


How to include raygui.h in multiple files other than main.c

Hello.
I'm trying to make custom controls. So i created a control.c and control.h just to test and i added the following lines to control.c and main.c :
#define RAYGUI_IMPLEMENTATION
#include "raygui.h"
But when i compile, i get errors with no error message.
so i saw this Issue and i tried to add #define RAYGUI_STATIC instead of #define RAYGUI_IMPLEMENTATION in the control.c file but nothing seems to be working.
Some example would be nice.
Thanks.

@MNAJIM75 RAYGUI_IMPLEMENTATION only have to be defined in one module. If it is eaiser for you, just split raygui.h into raygui.h and raygui.c.

@MNAJIM75 RAYGUI_IMPLEMENTATION only have to be defined in one module. If it is eaiser for you, just split raygui.h into raygui.h and raygui.c.

thanks, it works


docs(guide/Providers): Line no: 220 ; function name will start with l…

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
doc update
What is the current behavior? (You can also link to an open issue here)
What is the new behavior (if this is a feature change)?
Does this PR introduce a breaking change?
Please check if the PR fulfills these requirements

[ ] The commit message follows our guidelines: https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#commit-message-format
[ ] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)

Other information:
…ower-case u

Thx for taking the time to submit a PR, but this change is invalid.
The constructor function was intentionally capitalized. It is a common JS convention to capitalize contructor functions. (For example, most linting tools will complain if you use this inside a non-capitalized function, since it is an indication that you are treating a non-constructor function as a constructor function.)
Btw, it is also common in Angular to capitalize the name of services, but this is a matter of preferrence.

myApp.config(["unicornLauncherProvider", function(unicornLauncherProvider) {
unicornLauncherProvider.useTinfoilShielding(true);
}]);
In the config function , we have taken dependency with lower-case 'u' character , i was wondering if this is correct or we need to change the dependency name to capitalized UnicornLauncherProvider

This is what I am referring to in:

Btw, it is also common in Angular to capitalize the name of services, but this is a matter of preferrence.

Either way is fine (lowercase is more "politically correct", although capitalized is more common imo).
--
Basically, this is how the $injector understands things:
Developer: .provide('foo', FooProvider() { ... })
$injector: Whenever someone requests foo for the first time, I will use FooProvider to create such an instance. I will first create a provider instance (using new FooProvider - thus FooProvider is a constructor function) and then invoke its $get method, which will give me foo.
Developer: .config(function(foo) { ... }) means:
$injector: Someone needs foo. I'll give the foo.
Here foo is just an instance (an object), not a constructor function.


8539 add remove repeat item

Looks terrific. Thanks for changes.
I did a small refactor of the context class using double splat. Please take a look:
https://github.com/thecartercenter/elmo/pull/471/commits/4698d9b891749ecfe32d57a5d1edb9c9e2b5cc2d
Thanks!


Update kubernetes packages to v0.31.0

This PR contains the following updates:

Package
Type
Update
Change

k8s.io/api
require
minor
v0.30.3 -> v0.31.0

k8s.io/apimachinery
require
minor
v0.30.3 -> v0.31.0

k8s.io/cli-runtime
require
minor
v0.30.3 -> v0.31.0

k8s.io/client-go
require
minor
v0.30.3 -> v0.31.0

k8s.io/metrics
require
minor
v0.30.3 -> v0.31.0

Release Notes

kubernetes/api (k8s.io/api)
v0.31.0
Compare Source

kubernetes/apimachinery (k8s.io/apimachinery)
v0.31.0
Compare Source

kubernetes/cli-runtime (k8s.io/cli-runtime)
v0.31.0
Compare Source

kubernetes/client-go (k8s.io/client-go)
v0.31.0
Compare Source

kubernetes/metrics (k8s.io/metrics)
v0.31.0
Compare Source

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

ℹ Artifact update notice
File name: go.mod
In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

13 additional dependencies were updated

Details:

Package
Change

github.com/davecgh/go-spew
v1.1.1 -> v1.1.2-0.20180830191138-d8f796af33cc

github.com/go-logr/logr
v1.4.1 -> v1.4.2

github.com/google/uuid
v1.3.1 -> v1.6.0

github.com/moby/term
v0.0.0-20221205130635-1aeaba878587 -> v0.5.0

golang.org/x/net
v0.23.0 -> v0.26.0

golang.org/x/oauth2
v0.13.0 -> v0.21.0

golang.org/x/sys
v0.18.0 -> v0.21.0

golang.org/x/term
v0.18.0 -> v0.21.0

google.golang.org/protobuf
v1.33.0 -> v1.34.2

k8s.io/klog/v2
v2.120.1 -> v2.130.1

k8s.io/utils
v0.0.0-20230726121419-3b25d923346b -> v0.0.0-20240711033017-18e509b52bc8

sigs.k8s.io/kustomize/api
v0.14.0 -> v0.17.2

sigs.k8s.io/kustomize/kyaml
v0.14.3 -> v0.17.1


Feat: Social media handles at footer

Describe the feature
At Footer of the Page Social Media Handles are not redirecting to the mentioned handles so kindly provide the social media respective account website links to fix this issue. Kindly assign me this issue, so i can work towards it under GSSOC'24. Thank You
Add ScreenShots
https://github.com/arghadipmanna101/Flipkart_Clone/assets/115927008/27b6db8f-3d3a-4478-994f-c4b3861d7885
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

@arghadipmanna101
Can you assign me this issue?

@arghadipmanna101 please assign me this issue


Importing issues when renaming Templates/Features

Original post thx dread for reporting it
Steps to reproduce

Create new empty Unreal project
Install the Articy Importer plugin and enable it.
Export the fresh Maniac Manfred articy project to Unreal projects Content directory.
Import the generated articy project assets when prompted.
Go to articy project and change the Technical name of "Template Design/Templates/Entities/Character" to CharacterChanged.
Export the articy project.
Import the project in Unreal when prompted to.
8, Observer unreal engine crash.

Workaround
Deleting the whole Generated folder resolves the import

This has been resolved a long time ago now, by deleting the old assets before creating new ones, which resolves an issue where Unreal tried overwriting an asset with the same path, but a different class.


Arabic presentation forms still required?

The Arabic subset says:
https://github.com/googlefonts/glyphsets/blob/575273691bcc9c0dfc220c3c21b86bc64b052354/Lib/glyphsets/encodings/arabic_unique-glyphs.nam#L5-L8
However, for automatic subset detection (gftools-add-font) this is a bit of a pain. Because there are so many presentation forms, if you don't support them, Arabic support falls below the threshold and does not get detected. I don't know if it's still true that lots of Arabic text is encoded using presentation forms; I don't think so, but others might know better.

@nathan-williams Is there any way we could get a sense of what proportion of Arabic web pages include characters in the range U+FB50-FBFF U+FE80-U+FEFC compared to those which just use U+0600-06FE?

I’d do without Arabic Presentation Forms. Their use has been discouraged by Unicode from the day they were included and their use on the web falls into two categories 1) bad copy&paste (usually from PDF files, because PDFs are horrible at preserving text) 2) selecting a positional form in isolation, something that could be done by ZWJ if people knew any better.
Both are fringe use case IMHO and does not justify such requirement. They also can add quite a bit to file size, in one font where I measured this, they almost doubled file size (that was Arabic Presentation Forms  A and B, so a subset of it might add a bit less than this). They don’t add much space for simple fonts that are built with composed glyphs.


Update data-factory-pig-hive-activities.md

Fix anchor in the TOC to point to Walkthrough. Small typo there.

Hi @JasonWHowell, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no contribution license agreement is required at this point. Real humans will now evaluate your PR.

TTYL, AZPRBOT;


Cave types may need to be recognised inside description if Ralfs moves them there.

Or maybe they do. If the cave categories under sub activities are updated in the same time, we may not need to do anything.

I think this works now


Fix number of expected fake quantized

In this PR we fixed the number of expected FakeQuantized resulting from NNCF static and aware training quantization

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


Failed to load system roots

I cannot get the security-credentials in my container. When I check docker logs ec2metaproxy the error is recorded as:
caused by: Post https://sts.amazonaws.com/: x509: failed to load system roots and no roots provided
it seems ca-certificates aren't installed/configured correctly in the image?

Thanks for the report. A new dump247/ec2metaproxy image has been built and pushed that resolves the issue.
For reference, the issue was resolved in #300adc1f62e921cef6e036c9b01d5dcc4a929dca.


Bump nuraft to latest HEAD.

Enhancements:

Add an API to schedule snapshot creation (https://github.com/eBay/NuRaft/pull/483[)](https://github.com/eBay/NuRaft/commit/b54b09c28462d9bfc36db4484d0668ef486e9505)
Add a callback for leader resignation (https://github.com/eBay/NuRaft/pull/484[)](https://github.com/eBay/NuRaft/commit/78bae7062eb59e3dc85f51dd073e7865ab2f60f1)
Add change buffer API to log_entry (https://github.com/eBay/NuRaft/pull/490[)](https://github.com/eBay/NuRaft/commit/bc1db87415a83dc7e5284d22f56b75a1a99ee285)
auto_fwd_resp_handler should forward resp->get_result_code (https://github.com/eBay/NuRaft/issues/497[)](https://github.com/eBay/NuRaft/commit/d195630b5f7a54b13ed6dc5ec6f471c9a7a3dc3a)
1. cmd_result::get_result_str add SERVER_IS_LEAVING (https://github.com/eBay/NuRaft/issues/505) (https://github.com/eBay/NuRaft/pull/506[)](https://github.com/eBay/NuRaft/commit/3a64f74a9cd4fe32da3fe57e2e961adc8b7e21cd)

Includes fixes:

Fix to bug on snapshot ctx of removed member (https://github.com/eBay/NuRaft/pull/473[)](https://github.com/eBay/NuRaft/commit/e66b4b65c90ff3a0be852d484bf15583672ea7fd)
Avoid snapshot creation index inversion (https://github.com/eBay/NuRaft/pull/479[)](https://github.com/eBay/NuRaft/commit/9de4522beccaa1901d49488fcbb01447a9335ea9)
fix: prevent a server joining another cluster whlit it is already i…

Is it possible to update the conanfile version of nuraft_mesg as well, so we can track it easier?


example codes crashed (ResNet)

After I updated the newest changes, the training for ResNet 50 is crashed; however, the inference is fine. (I clean install the newest version to avoid my changes in source codes.)
Thanks!
my command:
python3 examples/ResNet/imagenet-resnet.py --gpu 0,1,2,3 --data /home/chenrich/dataset/imagenet -d 50

Here is log:
[0808 10:09:00 @input_source.py:427] Pre-filling staging area ...
[0808 10:09:00 @input_source.py:195] ERR Exception in EnqueueThread:
Traceback (most recent call last):
  File "~/Developer/temp/tensorpack/tensorpack/graph_builder/input_source.py", line 186, in run
    self.dataflow.reset_state()
  File "~/Developer/temp/tensorpack/tensorpack/dataflow/base.py", line 79, in reset_state
    self.ds.reset_state()
  File "~/Developer/temp/tensorpack/tensorpack/dataflow/prefetch.py", line 183, in reset_state
    self.start_processes()
  File "~/Developer/temp/tensorpack/tensorpack/dataflow/prefetch.py", line 189, in start_processes
    start_proc_mask_signal(self.procs)
  File "~/Developer/temp/tensorpack/tensorpack/utils/concurrency.py", line 188, in start_proc_mask_signal
    with mask_sigint():
  File "~/tools/Python-3.6.2/lib/python3.6/contextlib.py", line 81, in __enter__
    return next(self.gen)
  File "~/Developer/temp/tensorpack/tensorpack/utils/concurrency.py", line 174, in mask_sigint
    sigint_handler = signal.signal(signal.SIGINT, signal.SIG_IGN)
  File "~/tools/Python-3.6.2/lib/python3.6/signal.py", line 47, in signal
    handler = _signal.signal(_enum_to_int(signalnum), _enum_to_int(handler))
ValueError: signal only works in main thread
[0808 10:09:00 @input_source.py:201] EnqueueThread Exited.

My bad.


Consider moving to a single daemon thread (and shared worker) for the asset watcher

If I move to a single daemon thread for the watching, and have N active requests (tabs) open doing essentially, while True: queue.get(...) is that going to be better for my battery life/power usage than N watchers?
I'm pondering this because for django-technicalerrors I kind of want to toy with using django-pattern-library which fulfils an idea I had long ago quite nicely by the look of it (yay). Except it loads all components as iframes, so I'd end up with 1+N SSE connections.
This might also fit with the notion of using a shared worker, which IIRC @adamchainz's django-browser-reload uses; It looks like each "port" is a tab, so I could send messages to them all with 1 worker, and thus still one long-lived request...maybe?
Need to investigate the trade-offs. Debugging a shared worker looks painful, but would get me 1 request per connected browser I guess. N watchers is what I currently have (hi, would you like to stat lots of files?) 1 watcher + N requests spinning on queues is a middle-ground which could be better or worse, IDK :D
Could be kinda grim to re-factor now, though. Hmmm.

This might also fit with the notion of using a shared worker, which IIRC @adamchainz's django-browser-reload uses; It looks like each "port" is a tab, so I could send messages to them all with 1 worker, and thus still one long-lived request...maybe?

Yes this is exactly how django-browser-reload works.

Debugging a shared worker looks painful,

I couldn't find the worker's log messages in Chrome. But in Firefox they seem to route to the console of the tab that opened the worker, so not so bad.

Ah you're a gem for stopping by to fill in some gaps and unknowns for me, thanks so much. It looks like you can also summon the devtools for a shared worker in Chrome through a magic portal page, so maybe that'd make things less irksome too.

Fantastic!


[BUG] AMBS Submit more evaluations than max-evals

Describe the bug
AMBS Submit more evaluations than max-evals
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I run DeepHyper with two evaluations
results = serach.serach(max_eval=2)

DH does these two and save results. But before exit it starts third job, which is still running when DH finished. So it looks like DH started one additional async process before exit.
Desktop (please complete the following information):

DeepHyper Version 0.3.3

This does not happen when serial evaluations are submitted, in a parallel asynchronous case this problem is non trivial to resolve, if the user wants to make sure the resource is limited after a given time budget then a custom callback can be defined and use to raise a SearchTermination exception and finish properly the search.


Code Cleanup

Problem
At the moment our insights functions are in the module selected functions and our data provider is a single file, rather than a module.
Proposed Solution
Rename selected functions to insights functions and add a module data provider and move the current data provides into this module.

Updated in https://github.com/hotosm/field-campaigner/issues/46


Feature: Llava executor

This is just a preview, the code it's not clean or finished. But I think It's enough to talk about the implementation.
Introduction to the example

Changes in the Interactive Executor to add an additional constructor to enable the support of vision models.
An example using the Interactive Executor to create and initialize the llava model.

This is just a raw capture of the example working:

Things to talk about:

[ ] The interface to the executors. I just create some properties in ILLavaExecutor (I know there are some duplicate property) basically to identify if it's a vision model and the current Image. This was the easiest approach to get an example working. I would like to get your suggestions on the integration on ILLamaExecutor interface. Especially I didn´t review the implications in the Chat or Semantic Kernel integrations, to allow to support that kind of models in all the layers.

LGTM, please convert it from draft to formal PR if it's ready to merge.

I will solve the current conflicts today and change the PR to formal PR.

The latest changes are:

Change the example to make a "preview" in the console of the image. Just to have an idea of the file loaded.
Allow to introduce image files with the path in the console (in the example).
Theoretically to be able to manage more than a file.

Notes: The example is just tested with llava-v1.6-mistral. The prompt could change if the model used is a different one.
This is an execution of the example:


Adding both gmail and inbox shows inbox in both tabs

Expected Behavior
Show different UIs

Current Behavior
Adding both gmail and inbox for the same google account shows exactly the same UI (inbox). Probably because it's set as default for my google mail.

Possible Solution

Openwmail does not have this problem
Probably should be using this link
https://mail.google.com/mail/?ibxr=0
to use gmail, and not this
https://github.com/meetfranz/recipe-gmail/blob/master/package.json#L10
which gets redirected to inbox
Your Environment

Franz Version used: 5.0.0-beta.14
Operating System and version: macOS 10.12.6

If anyone wants immediate fix for this - just replace gmail URL in package.json of gmail recipe.
On macOS it's located in
~/Library/Application Support/Franz/recipes/gmail/package.json

Will close this as proper way to achieve that is to change inbox setting.
https://lifehacker.com/change-this-setting-to-redirect-gmail-to-google-inbox-1717733739


Universalise backends

We shouldn't need the web branch. Instead, we should be able to build the same codebase to whichever Nim backend we want. This takes care of that by using the appropriate when defined(js) guards.

(to build to the JS backend, add backend = "js" to the nimble file)


Add validations for Azure node resources

Add validations for Azure node resources, which include

Validate route tables are set correctly
Validate node's providerID are set correctly (note: vmss and vmas formats are different)
Validate node's publicIP
Validate node's privateIP

/kind testing
/milestone v1.16

Not finished yet, move to v1.17.
/milestone v1.17

/assign @nilo19

Added by #253.


Implement Transaction Rollback

The problem exists on SORA - if transaction fails the refund would not be sended to sender to parachains/relaychain

Since there is an origin erasure problem we can create a root extrinsic in substrate-app or bridge-proxy that would take transaction hash and receiver - and i would send assets through the bridge back to sender.

Will be implemented if time permits before the release

@N1ghtStorm  Is it part of the upcoming release plan?


ed25519::GE fails in serialization and deserialization

There seems to be an error in encoding/decoding of a GE (Ed25519Point) in version 0.7.0. In the example below, the base_point is serialized to JSON, and a new point is recreated from it. I expect the new point to contain the same x, y coordinates, but it isn't the case:
    let base_point: GE = GE::generator();
    println!("base_point.x:{:?}", base_point.x_coor().unwrap().to_hex());
    println!("base_point.y:{:?}", base_point.y_coor().unwrap().to_hex());
    //Prints:
    //base_point.x:"216936d3cd6e53fec0a4e231fdd6dc5c692cc7609525a7b2c9562d608f25d51a"
    //base_point.y:"6666666666666666666666666666666666666666666666666666666666666658"

    let base_point_json = serde_json::to_string(&base_point).unwrap();
    let new_point = serde_json::from_str::<GE>(&base_point_json).unwrap();

    println!("new_point.x:{:?}", new_point.x_coor().unwrap().to_hex());
    println!("new_point.y:{:?}", new_point.y_coor().unwrap().to_hex());
    //Prints:
    //new_point.x:"6742e15f97d771b642862d5cf84ecf93eb3ac67b80698b993b87fdbc08a584c8"
    //new_point.y:"21d30600c9e573796ead6f09668af38f81783cfc621ee4931e2f5ba9fc37b9b4"

    assert_eq!(base_point, new_point);//assertion failed

This causes the EdDSA thresholdsig to always fail with "invalid key" error in the stage: phase1_verify_com_phase2_distribute() because the  y_vec: &Vec<GE> has to be collected from different parties, and this needs serialize/deserializing the GE's.
You have said that improving the v0.7 is no longer a priority(unless critical issues) so it would be great if you please consider this as a critical issue!

The real cause of the problem seems to be in from_bytes() where the encoded point is multiplied by 8.

Hi @Hrezaei,
So you're right, we intentionally multiply decoded point by 8, it clears a small cofactor from the point. That might seem odd, but that's how it works. FYI since<EMAIL_ADDRESS>we don't do multiplication by 8 anymore.
Nevertheless, multi-party-eddsa is tested to work, it takes into account that feature of curv library. Could you describe how you encountered "invalid key" error?

Hi @survived,
Thanks for your consideration.
Regarding the v0.8 we can't use it currently because upgrading to it, needs a lot of changes, not only in the eddsa project but also in many dependencies such as paillier's, centipede, bulletproofs, etc.

Nevertheless, multi-party-eddsa is tested to work, it takes into account that feature of curv library. Could you describe how you encountered "invalid key" error?

Yeah, tests in the multi-party-eddsa work without error because all parties are executed in the same machine. Consider for example, the test function keygen_t_n_parties(), in the line 153 you have collected y_vec by simply iterating over party_keys_vec. But in a real scenario, each y_i has to be collected from different parties, executed on separated machines. So they have to be serialized and deserialized in the communications between parties. I suggest changing the lines 153-155 from
let y_vec = (0..n.clone())
            .map(|i| party_keys_vec[i].y_i.clone())
            .collect::<Vec<GE>>();

to this snippet below, to mimic the real scenario.
let y_vec = (0..n.clone())
    .map(|i| party_keys_vec[i].y_i.clone())
    .map(|y_i| serde_json::to_string(&y_i).unwrap())//serialize y so to be broadcasted to other parties
    .map(|y_i_json| serde_json::from_str(&y_i_json).unwrap())//deserialize y, as it happens in each recipient party
    .collect::<Vec<GE>>();

You will see two tests will fail with the error "invalid key: InvalidKey".

but also in many dependencies such as paillier's, centipede, bulletproofs, etc

All of these libraries are updated to use the latest curv, thanks to @tmpfs. multi-party-ecdsa is almost updated too, see https://github.com/ZenGo-X/multi-party-ecdsa/pull/144. It is possible to update eddsa library as well, if you want to contribute to the project 😉
Regarding deserialization, unless the library is updated to use latest curv, you can divide deserialized point by 8, it will yield the original point.

Updating the eddsa would be appealing if time limits permit. 😊
About division by eight, I followed your advice, but as you can see in the above commit, it needs many changes in many places as GE's are used inside vectors and more complex structs. It also would be a source of runtime errors, not easily discernible errors, because it's related to values, not data types. The developers should be careful to remedy the situation whenever a data structure containing GE is deserialized.

Yeah that's frustrating. If it's applicable for your case — you can define a structure pub struct MyGE(GE); and define Serialization/Deserialization traits for it. Maybe that could help you to minify the changes?
Also, you can tag the wrapping structure with #[repr(transparent)] and this will allow you to define relatively safe zero-cost cast Vec<MyGE> -> Vec<GE>.

Thank you @survived for your advice.
But if I decided to define such a custom type in my own fork for my own use, why not remove that multiply by eight? What's the harm of removing that and adding a check for being on the curve?

Multiplication by 8 is security related operation, it clears out small cofactor part from the point. Not doing this might leak some bits of your secrets, or affect the protocol in some unexpected way. Note that it's not related to checking whether a point is on curve. When we multiply point by 8, we already checked that the point is on curve.
New version of curv performs an expensive check instead of multiplying by 8. It's less efficient, but more clear.

@HRezaei thanks for that, can you check again with v.0.10.0?

Hi @leontiadZen,
Sorry for late reply!
The initial issue was reported on v0.7.0, however I can confirm it is resolved in v0.9 and v0.10.0.


Readme.md improved

Windows 11 Setup Issues:

Noted that the command Install-WindowsFeature Containers -Restart is only applicable to Windows Server, not Windows 11.
Highlighted that Docker Desktop is set up for Linux containers by default, even if Hyper-V is selected instead of WSL.

Guidance for Docker Desktop Users:

Added a hint in New-NavContainer.ps1 to switch to Windows containers if Docker Desktop is installed, ensuring proper configuration.

Generic Images Section:

Added a new generic image section, based on @freddydk's recent LinkedIn post, to give users more information about how the generic image is selected.

Overview of Isolation Differences:

Provided a detailed comparison between Hyper-V and Process isolation containers, clarifying their differences in terms of isolation level, performance, compatibility, resource requirements, startup time, and host OS requirements.

Thanks for this @DanielGoehler - much appreciated

@freddydk I noticed that you have deleted your comment. Feel free to add your experience or others and we all benefit. This is from my experience, but is not intended to be one-sided.


Cassandra: Fix UUID comparisons on Cassandra partition key. Fixes #2927

Currently when you try to query on a UUID that is also the partition key (Cassandra's primary key), you get an error java.lang.String cannot be cast to io.airlift.slice.Slice (CassandraType.java#L412). Oddly enough you don't get this issue when trying to query a UUID that is not the partition key. Solving the casting issue, the next issue you get is java.lang.IllegalArgumentException: Mismatched Domain types: class io.airlift.slice.Slice vs class java.lang.String Looking over the code already, it seems this case is already understood (CassandraType.java#L232), and it was just a matter of adding a case for UUIDs to solve the Domain issue.

Merged, thanks!

Thank you @nemothekid!


Automate upgrade tests

We should start adding upgrade tests to check if our migration scripts works and any changes we are making in schemas and apis works by upgrading a previous version.
Steps for upgrade test

Install current released version, 0.7 in this case
Install current released ingestion version , openmetadata-ingestion==0.7.4
Start the server
Ingest sample data and other databases that are available
Run API tests
Build new release from main
Install new ingestion libs from the main
Run ./bootstrap/bootstrap-storage.sh migrate-all
Run ingestion , verify if the job is successful
Run API tests

Manual test results

Install & Ingest 0.7

3. After the fix #2321
4. run step-6 to step-8
5. need to metadata ingest -c pipelines/metadata_to_es.json to re-index all of elasticsearch

@vivekratnavel @pmbrull @akash-jain-10 this is extremely important for 0.12.0 release

@akash-jain-10 @Rabi-Sahoo update on this please

@akash-jain-10 can we prioritize this for 0.13.1?

@akash-jain-10 where are we with this?


More information regarding this tool.

Would like to see a step by step of how to add the tasks. Also possibly it would be worthwhile to have a tutorial like other doc's pages and also more information on how permissions get preserved and more on how those gets moved over. Seems like right now the information is a little bare. Also more in-depth information around how the migration works instead of just a high level overview.

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

ID: 210e3fb6-665e-a4e6-7b5e-fe3776ec1635
Version Independent ID: 80b1c7f6-736f-70a4-ae6c-503d64e94a26
Content: Get started with Migration Manager  - SharePoint - Migrate to SharePoint and OneDrive
Content Source: migration/mm-get-started.md
Service: sharepoint-online
GitHub Login: @JoanneHendrickson
Microsoft Alias: jhendr

@kempt101 Thank you for submitting feedback and contributing to the docs. We are currently investigating this.

Hello @kempt101 Sean, how are you?
Several updates were applied since you opened this feedback to the Migration Manager articles, I would like to know if you could review them. The team welcomes your feedback and is working on constantly improving the articles.

We appreciate any feedback that improves the content in the Microsoft docs but we haven't had any response from you so we are going to close this issue.
Please feel free to re-open this issue if there is a specific area of the docs that we can improve or make better. Thank you.

We appreciate any feedback that improves the content in the Microsoft docs but we haven't had any response from you so we are going to close this issue.
Please feel free to re-open this issue if there is a specific area of the docs that we can improve or make better. Thank you.


send current position

Has anyone been able to implement the shipment of the current position?

i dont think that web whatsapp able to send current position

But you do not know if there is the possibility of sending the latitude and longitude and that it reaches the user as a type of location?

Would be nice to send geolocation messages. This library does not have this function yet.
:(


Chart Improvements

refer to incomplete tasks in https://github.com/Teradata/covalent/issues/1

@covalent/charts are deprecated since 0.10 in favor of our partnership with ngx-charts


[Q] how to select particular network interface to push multicast rtp streaming data (eth0,eth1,wifi..)

currently, I am using the below command for RTP streaming from mpeg ts file
tsp -v -I file -i file.mpg -P regulate -O ip -r <IP_ADDRESS>:5001
is there a way to push multicast streaming data only to a particular network interface (eth0,eth1, wifi..)?

@lelegard I couldn't find the answer in the document, could you please mention the topic/title name from the document where i can find the interface selection

TSDuck User's Guide from https://tsduck.io/ => Documentation => User's guide => tsp plugins => ip output plugin.
Or simply:
$ tsp -O ip --help
...
  -l value
  --local-address value
      When the destination is a multicast address, specify the IP address of
      the outgoing local interface. It can be also a host name that translates
      to a local address.
...


Aiken confuses namespaces while importing

What Git revision are you using?
https://github.com/aiken-lang/aiken/commit/fd14da0720abffdc5bd772f691989b4e5e0e58f7
What operating system are you using, and which version?

[x] macOS

Describe what the problem is?
It should be perfectly legal to import the same files from different namespaces yet Aiken get's confused and signals an error:
   ╭─[/Users/mati/Devel/OpenSource/aiken-trees/lib/aiken/trees/mt.ak:1:1]
 1 │ use acca/either.{Either, Left, Right}
 2 │ use acca/list.{prepend}
   · ───────────────────────
 3 │ use aiken/bytearray
 4 │ use aiken/hash.{Hash, Sha2_256, sha2_256}
 5 │ use aiken/list
   · ──────────────
 6 │ use aiken/option.{choice, is_none}
   ╰────
  help: The best thing to do from here is to remove one of them.

What should be the expected behavior?
I expect that I can use list from two different namespaces.

Not a bug you need to Alias the second one.
use aiken/list as ls

got it, thanks