CHORE: Synchronize Page,Action and ActionCollection object from original corresponding object

…responding object

Pull Request Template
Use this template to quickly create a well written pull request. Delete all quotes before creating the pull request.

Description
This change is to synchronize permission to newly created git branched object from default branch object, for CE permission model this has no effect

Please include a summary of the changes and which issue has been fixed. Please also include relevant motivation
and context. List any dependencies that are required for this change
Links to Notion, Figma or any other documents that might be relevant to the PR

Add a TL;DR when description is extra long (helps content team)

Fixes # (issue)

if no issue exists, please create an issue and ask the maintainers about this first

Media

A video or a GIF is preferred. when using Loom, don’t embed because it looks like it’s a GIF. instead, just link to the video

Type of change

Please delete options that are not relevant.

New feature (non-breaking change which adds functionality)

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions, so we can reproduce.
Please also list any relevant details for your test configuration.
Delete anything that is not important

Test Plan

Add Testsmith test cases links that relate to this PR

Issues raised during DP testing

Link issues raised during DP testing for better visiblity and tracking (copy link from comments dropped on this PR)

Checklist:
Dev activity

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[ ] PR is being merged under a feature flag

QA activity:

[ ] Test plan has been approved by relevant developers
[ ] Test plan has been peer reviewed by QA
[ ] Cypress test cases have been added and approved by either SDET or manual QA
[ ] Organized project review call with relevant stakeholders after Round 1/2 of QA
[ ] Added Test Plan Approved label after reveiwing all Cypress test

/ok-to-test sha=https://github.com/appsmithorg/appsmith/pull/18846

/ok-to-test sha=22086adfa148a453c7385a4d9ef97e825d1e8a2a


Direct DB endpoint: Use host and port from environmental variables

Relies on https://github.com/ausaccessfed/aaf-ansible/pull/427

All good in devfed @smangelsdorf


draft-05 interop with moq-rs (subscribe / watch endpoint)

Hello Mike @englishm ,
With this PR have attempted to add interop support for "/watch" in moq-js with the draft-05 version of moq-rs as of commit https://github.com/englishm/moq-rs/commit/bf830f7887dd94ee6f531c5e375ab3fcc32f9043
i.e. moq-pub -> moq-relay <- moq-js (/watch)
Code changes are pending to make  /publish in moq-js work with  draft-05 version of moq-rs , eventually will attempt on the same.

UT
moq-pub -> moq-relay <- moq-js (/watch)
https://github.com/user-attachments/assets/ee321563-9b04-49ea-a983-5001d5bc6ceb

This looks great, thank you so much @TilsonJoji!

Publish endpoint support added with this PR


Fix #169

Fix TypeError in graph_transitions management command when using django's lazy translations for FSMIntegerField choices labels, e.g.
from django.utils.translation import ugettext_lazy as _
from django.db import models
from django_fsm import FSMIntegerField, transition

class Test(models.Model):
    state = FSMIntegerField(default=0, choices=((0, _('closed')), (1, _('opened'))))

    @transition(field=state, source=0, target=1)
    def open(self):
        pass

Thank you!


[Self-host deploy] px auth login failed with error upstream prematurely closed connection while reading upstream

Describe the bug
TBH, our installation guide is not well-documented. I've been tried to deploy pixie in minikube, and I've been fixed lots of issues:

As issue #347, I've been setup an ingress-nginx controller by manually, and update our ingress with adding annotations:

# Note1: the lastest version k8s need ingressClass!
---
apiVersion: networking.k8s.io/v1
kind: IngressClass
metadata:
  labels:
    app.kubernetes.io/component: controller
  name: nginx
  annotations:
    ingressclass.kubernetes.io/is-default-class: "true"
spec:
  controller: k8s.io/ingress-nginx
---
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  annotations:
    networking.gke.io/managed-certificates: cloud-ingress-managed-cert
    networking.gke.io/v1beta1.FrontendConfig: frontend-config
    # Note2: we do need this line to ensure the cert config
    nginx.ingress.kubernetes.io/backend-protocol: "HTTPS"
  labels:
    app: pl-cloud
  name: cloud-ingress
  namespace: plc
spec:
  ingressClassName: nginx
...

What's more, I've been configured our cloud proxy cert as ingress-nginx default cert, to make https works.

after fixed https issue, I've been able to open the browser and reset the passwd, and it works well. But when I'm going to install pixie cli, it would failed with login. I've been tried it again and again, with px auth login, and it failed with page error:

We hit a snag trying to authenticate you. Please try again later.

Details: rpc error: code = Internal desc = server closed the stream without sending trailers

and the logs from cloud-proxy service was:
<IP_ADDRESS> - - [06/Nov/2021:01:40:14 +0000] "POST /oauth/kratos/self-service/login/methods/password?flow=575cc018-32ac-4d4a-9a63-8e426ab4a9ac HTTP/1.1" 302 0 "https://work.dev.withpixie.dev/auth/password-login?flow=575cc018-32ac-4d4a-9a63-8e426ab4a9ac" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/95.0.4638.69 Safari/537.36"
2021/11/06 01:40:14 [error] 9#9: *16466 upstream prematurely closed connection while reading upstream, client: <IP_ADDRESS>, server: work.dev.withpixie.dev, request: "GET /api/auth/oauth/login?hydra_login_state=f7b535640ed769f7bbd119cc7d40a355a9f2f12ba0454eb643ea5f8f3665afeef78f46f9f413d9471caa1191fe6b7c64&login_challenge=753e51e09e57481396a28c86aa43e889 HTTP/1.1", upstream: "https://<IP_ADDRESS>:51200/api/auth/oauth/login?hydra_login_state=f7b535640ed769f7bbd119cc7d40a355a9f2f12ba0454eb643ea5f8f3665afeef78f46f9f413d9471caa1191fe6b7c64&login_challenge=753e51e09e57481396a28c86aa43e889", host: "work.dev.withpixie.dev", referrer: "https://work.dev.withpixie.dev/auth/password-login?flow=575cc018-32ac-4d4a-9a63-8e426ab4a9ac"
<IP_ADDRESS> - - [06/Nov/2021:01:40:14 +0000] "GET /api/auth/oauth/login?hydra_login_state=f7b535640ed769f7bbd119cc7d40a355a9f2f12ba0454eb643ea5f8f3665afeef78f46f9f413d9471caa1191fe6b7c64&login_challenge=753e51e09e57481396a28c86aa43e889 HTTP/1.1" 302 0 "https://work.dev.withpixie.dev/auth/password-login?flow=575cc018-32ac-4d4a-9a63-8e426ab4a9ac" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/95.0.4638.69 Safari/537.36"
<IP_ADDRESS> - - [06/Nov/2021:01:40:14 +0000] "GET /oauth/hydra/oauth2/auth?client_id=auth-code-client&consent_verifier=50adfb7c7793483e8272fe9b2169b0b9&redirect_uri=https%3A%2F%2Fwork.dev.withpixie.dev%2Fauth%2Fcallback%3Fmode%3Dcli_get%26redirect_uri%3Dhttp%253A%252F%252Flocalhost%253A8085%252Fauth_complete&response_type=token&scope=vizier&state=PANbRDTJV6iy-Qlsg1Dn~.LviCCc9qkTBSDYYznvlJTlY.3b HTTP/1.1" 302 0 "https://work.dev.withpixie.dev/auth/password-login?flow=575cc018-32ac-4d4a-9a63-8e426ab4a9ac" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/95.0.4638.69 Safari/537.36"
<IP_ADDRESS> - - [06/Nov/2021:01:40:14 +0000] "GET /auth/callback?mode=cli_get&redirect_uri=http%3A%2F%2Flocalhost%3A8085%2Fauth_complete HTTP/1.1" 200 1162 "https://work.dev.withpixie.dev/auth/password-login?flow=575cc018-32ac-4d4a-9a63-8e426ab4a9ac" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/95.0.4638.69 Safari/537.36"

And see the api service logs below:
time="2021-11-06T01:40:09Z" level=info msg="HTTP Request" func=px.dev/pixie/src/shared/services.HTTPLoggingMiddleware.func1 file="src/shared/services/logging.go:63" req_method=GET req_path="/api/auth/oauth/login?hydra_login_state=f7b535640ed769f7bbd119cc7d40a355a9f2f12ba0454eb643ea5f8f3665afeef78f46f9f413d9471caa1191fe6b7c64&login_challenge=753e51e09e57481396a28c86aa43e889" resp_code=302 resp_size=322 resp_status=Found resp_time="677.821µs"
time="2021-11-06T01:40:13Z" level=info msg="[core] Subchannel Connectivity change to CONNECTING" func=google.golang.org/grpc/internal/grpclog.InfoDepth file="external/org_golang_google_grpc/internal/grpclog/grpclog.go:37" system=system
time="2021-11-06T01:40:13Z" level=info msg="[core] Subchannel picks a new address \"\" to connect" func=google.golang.org/grpc/internal/grpclog.InfoDepth file="external/org_golang_google_grpc/internal/grpclog/grpclog.go:37" system=system
time="2021-11-06T01:40:13Z" level=warning msg="[core] grpc: addrConn.createTransport failed to connect to {  <nil> 0 <nil>}. Err: connection error: desc = \"transport: Error while dialing dial tcp: missing address\". Reconnecting..." func=google.golang.org/grpc/internal/grpclog.WarningDepth file="external/org_golang_google_grpc/internal/grpclog/grpclog.go:46" system=system
time="2021-11-06T01:40:13Z" level=info msg="[core] Subchannel Connectivity change to TRANSIENT_FAILURE" func=google.golang.org/grpc/internal/grpclog.InfoDepth file="external/org_golang_google_grpc/internal/grpclog/grpclog.go:37" system=system
time="2021-11-06T01:40:13Z" level=info msg="[balancer] base.baseBalancer: handle SubConn state change: 0xc000472370, CONNECTING" func=google.golang.org/grpc/internal/grpclog.InfoDepth file="external/org_golang_google_grpc/internal/grpclog/grpclog.go:37" system=system
time="2021-11-06T01:40:13Z" level=info msg="[balancer] base.baseBalancer: handle SubConn state change: 0xc000472370, TRANSIENT_FAILURE" func=google.golang.org/grpc/internal/grpclog.InfoDepth file="external/org_golang_google_grpc/internal/grpclog/grpclog.go:37" system=system
time="2021-11-06T01:40:14Z" level=info msg="HTTP Request" func=px.dev/pixie/src/shared/services.HTTPLoggingMiddleware.func1 file="src/shared/services/logging.go:63" req_method=GET req_path="/api/auth/oauth/login?hydra_login_state=f7b535640ed769f7bbd119cc7d40a355a9f2f12ba0454eb643ea5f8f3665afeef78f46f9f413d9471caa1191fe6b7c64&login_challenge=753e51e09e57481396a28c86aa43e889" resp_code=302 resp_size=0 resp_status=Found resp_time=75.400411ms
time="2021-11-06T01:42:25Z" level=info msg="[core] Subchannel Connectivity change to CONNECTING" func=google.golang.org/grpc/internal/grpclog.InfoDepth file="external/org_golang_google_grpc/internal/grpclog/grpclog.go:37" system=system
time="2021-11-06T01:42:25Z" level=info msg="[core] Subchannel picks a new address \"\" to connect" func=google.golang.org/grpc/internal/grpclog.InfoDepth file="external/org_golang_google_grpc/internal/grpclog/grpclog.go:37" system=system
time="2021-11-06T01:42:25Z" level=warning msg="[core] grpc: addrConn.createTransport failed to connect to {  <nil> 0 <nil>}. Err: connection error: desc = \"transport: Error while dialing dial tcp: missing address\". Reconnecting..." func=google.golang.org/grpc/internal/grpclog.WarningDepth file="external/org_golang_google_grpc/internal/grpclog/grpclog.go:46" system=system
time="2021-11-06T01:42:25Z" level=info msg="[core] Subchannel Connectivity change to TRANSIENT_FAILURE" func=google.golang.org/grpc/internal/grpclog.InfoDepth file="external/org_golang_google_grpc/internal/grpclog/grpclog.go:37" system=system
time="2021-11-06T01:42:25Z" level=info msg="[balancer] base.baseBalancer: handle SubConn state change: 0xc000472370, CONNECTING" func=google.golang.org/grpc/internal/grpclog.InfoDepth file="external/org_golang_google_grpc/internal/grpclog/grpclog.go:37" system=system

To Reproduce
Steps to reproduce the behavior:
Follow the self-host deploy document, try to install pixie in minikube on macOS.
Expected behavior
I am able to do px auth login and deploy pixie.
Screenshots

px auth login cli outputs:
➜  pixie git:(main) ✗ px auth login
Pixie CLI
*******************************
* IN TESTING MODE
* 	 PL_CLOUD_ADDR=dev.withpixie.dev
*******************************
Starting browser
Fetching refresh token ...
Failed to perform browser based auth. Will try manual auth error=rpc error: code = Internal desc = server closed the stream without sending trailers

Please Visit:
 	 https://work.dev.withpixie.dev:443/login?local_mode=true

BTW, When I tried to re-login by the url https://work.dev.withpixie.dev:443/login?local_mode=true, it would succeed. But when I tried px auth login again, it would still failed with the same error.
Logs
App information (please complete the following information):

Pixie version: master branch
K8s cluster version: v1.22.2, macOS 10.15.7, minikube v1.23.2

Additional context

Since @vihangm explained in https://github.com/pixie-io/pixie/issues/347#issuecomment-963828372, I'd like to close this issue, as it's not the right way to install pixie in minikube on macOS.

Hi @Colstuwjx , I run pixie on non-minikube self-managed cluster and I get the same error after attempting to login. How did you resolve the issue? Thanks for advance!


[LIBCLOUD-684] Add auto-scale support for AWS and Softlayer providers

Link to JIRA: https://issues.apache.org/jira/browse/LIBCLOUD-684

Thanks.
As mentioned on IRC, I'm pretty busy these days, but I will try to have a look ASAP.

OK, thanks.

I have moved autoscale support to a new 'autoscale' folder per your recommendation in IRC. This is done under a new PR, with the same title, that I have just opened.
I will be happy to get your comments.

Great, thanks.


Idea: handle errors the stream way

Wondering about the performance hit though.

Sorry, that got published by mistake. Here's what I meant:
Hi there! Thank you for a great piece of code. I was delighted with the idea of reducing streams so idiomatically.
The problem arises when I need to handle errors though. I wanted to use through2-reduce in a gulp task. It's in fact nothing but a node stream. And as such it shouldn't throw errors – otherwise you get stack traces hunreds of calls deep.
The right way to handle an error in through2 is to pass it as the first argument of callback. That's of course impossible in through2-reduce as there's no callback argument. Perhaps we could simply catch errors from fn and issue an error event?
Wondering about the performance hit though.

Great idea! The performance impact shouldn't be much, given in most cases the stream chunk handling is done asynchronously. Generally the stream overhead and event loop overhead should trivialize the cost of this try/catch.
I've gone ahead and published this as version 0.3.0 -- please take a look!
I added two tests, one where instead of throwing you can just "emit" an error in the reducing function. This worked prior this patch, but didn't have a test.
Also I added the try/catch around the reducer which then does what you suggested.
In both cases the correct way to handle the errors is just to capture the "error" event off the reducing stream, which means it maintains the stream API.
Take a look at the tests for implementation and let me know what you think!

I've looked at the tests and used it in the wild – works like a charm! Thanks a lot for the quick reaction.
Now working with streams actually starts being fun for me :)


Error 500 Something went wrong

Following the installation instructions all steps were performed and htpasswd file create. After restarting the httpd24 service I am getting an error 500. In Apache I turned on debug logging and got the following:
[Tue Sep 18 13:19:53.051712 2018] [alias:debug] [pid 19325] mod_alias.c(628): [client <IP_ADDRESS>:59606] AH00673: incomplete redirection target of '/pun/sys/dashboard' for URI '/' modified to 'http://<IP_ADDRESS>/pun/sys/dashboard'
[Tue Sep 18 13:19:53.064163 2018] [authz_core:debug] [pid 19325] mod_authz_core.c(809): [client <IP_ADDRESS>:59606] AH01626: authorization result of Require valid-user : denied (no authenticated user yet)
[Tue Sep 18 13:19:53.064171 2018] [authz_core:debug] [pid 19325] mod_authz_core.c(809): [client <IP_ADDRESS>:59606] AH01626: authorization result of : denied (no authenticated user yet)
[Tue Sep 18 13:19:53.064388 2018] [authz_core:debug] [pid 19325] mod_authz_core.c(809): [client <IP_ADDRESS>:59606] AH01626: authorization result of Require valid-user : granted
[Tue Sep 18 13:19:53.064391 2018] [authz_core:debug] [pid 19325] mod_authz_core.c(809): [client <IP_ADDRESS>:59606] AH01626: authorization result of : granted
[Tue Sep 18 13:19:53.092885 2018] [proxy:debug] [pid 19325] mod_proxy.c(1227): [client <IP_ADDRESS>:59606] AH01143: Running scheme unix handler (attempt 0)
[Tue Sep 18 13:19:53.092909 2018] [proxy_ajp:debug] [pid 19325] mod_proxy_ajp.c(738): [client <IP_ADDRESS>:59606] AH00894: declining URL http://localhost/pun/sys/dashboard
[Tue Sep 18 13:19:53.092914 2018] [proxy_fcgi:debug] [pid 19325] mod_proxy_fcgi.c(974): [client <IP_ADDRESS>:59606] AH01076: url: http://localhost/pun/sys/dashboard proxyname: (null) proxyport: 0
[Tue Sep 18 13:19:53.092919 2018] [proxy_fcgi:debug] [pid 19325] mod_proxy_fcgi.c(977): [client <IP_ADDRESS>:59606] AH01077: declining URL http://localhost/pun/sys/dashboard
[Tue Sep 18 13:19:53.092930 2018] [proxy:debug] [pid 19325] proxy_util.c(2156): AH00942: HTTP: has acquired connection for ()
[Tue Sep 18 13:19:53.092937 2018] [proxy:debug] [pid 19325] proxy_util.c(2209): [client <IP_ADDRESS>:59606] AH00944: connecting http://localhost/pun/sys/dashboard to localhost:80
[Tue Sep 18 13:19:53.092943 2018] [proxy:debug] [pid 19325] proxy_util.c(2246): [client <IP_ADDRESS>:59606] AH02545: http: has determined UDS as /var/run/nginx/rcsg/passenger.sock
[Tue Sep 18 13:19:53.093026 2018] [proxy:debug] [pid 19325] proxy_util.c(2418): [client <IP_ADDRESS>:59606] AH00947: connected /pun/sys/dashboard to httpd-UDS:0
[Tue Sep 18 13:19:53.093043 2018] [proxy:debug] [pid 19325] proxy_util.c(2789): AH02823: HTTP: connection established with Unix domain socket /var/run/nginx/rcsg/passenger.sock ()
[Tue Sep 18 13:19:53.093062 2018] [proxy:debug] [pid 19325] proxy_util.c(3054): AH00962: HTTP: connection complete to <IP_ADDRESS>:0 (httpd-UDS)
[Tue Sep 18 13:19:53.093074 2018] [core:debug] [pid 19325] core.c(5090): (95)Operation not supported: [remote :12150] AH00139: apr_socket_opt_set(APR_TCP_NODELAY)
[Tue Sep 18 13:19:53.095667 2018] [proxy:debug] [pid 19325] proxy_util.c(2171): AH00943: : has released connection for ()
[Tue Sep 18 13:19:53.095688 2018] [proxy:debug] [pid 19325] proxy_util.c(2994): [remote \ufffd
:12150] AH02642: proxy: connection shutdown
[Tue Sep 18 13:19:53.096119 2018] [lua:info] [pid 19325] [client <IP_ADDRESS>:59606] req_protocol="HTTP/1.1" req_handler="proxy-server" req_method="GET" req_accept="text/html,application/xhtml+xml,application/xml;q=0.9,/;q=0.8" req_user_agent="Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:62.0) Gecko/20100101 Firefox/62.0" res_content_length="3065" req_content_type="" res_content_encoding="" req_status="500" req_origin="" time_user_map="27.904" local_user="rcsg" req_referer="" res_content_language="" req_port="80" req_is_websocket="false" req_server_name="<IP_ADDRESS>" log_hook="ood" req_accept_charset="" req_hostname="<IP_ADDRESS>" log_id="W6FByeJhP35M6ujSf-UXqgAAAAQ" res_content_location="" res_location="" log_time="2018-09-18T18:19:53.96014Z" remote_user="rcsg" req_user_ip="<IP_ADDRESS>" res_content_disp="" req_is_https="false" req_filename="proxy:http://localhost/pun/sys/dashboard" req_uri="/pun/sys/dashboard" time_proxy="3.255" res_content_type="text/html; charset=utf-8" req_accept_language="en-us,en;q=0.5" req_cache_control="" req_accept_encoding="gzip, deflate"

Could you share the non-sensitive portions of /opt/rh/httpd24/root/etc/httpd/conf.d/ood-portal.conf? RedHat or CentOS 6 or 7?

<VirtualHost *:80>
Lua configuration

LuaRoot "/opt/ood/mod_ood_proxy/lib"
LogLevel lua_module:info
Log authenticated user requests (requires min log level: info)
LuaHookLog logger.lua logger
Authenticated-user to system-user mapping configuration

SetEnv OOD_USER_MAP_CMD "/opt/ood/ood_auth_map/bin/ood_auth_map.regex"
Per-user Nginx (PUN) configuration
NB: Apache will need sudo privs to control the PUNs

SetEnv OOD_PUN_STAGE_CMD "sudo /opt/ood/nginx_stage/sbin/nginx_stage"

Below is used for sub-uri's this Open OnDemand portal supports

Serve up publicly available assets from local file system:

http://localhost:80/public/favicon.ico
#=> /var/www/ood/public/favicon.ico

Alias "/public" "/var/www/ood/public"
<Directory "/var/www/ood/public">
Options Indexes FollowSymLinks
AllowOverride None
Require all granted

Reverse proxy traffic to backend PUNs through Unix domain sockets:

http://localhost:80/pun/dev/app/simulations/1
#=> unix:/path/to/socket|http://localhost/pun/dev/app/simulations/1

SetEnv OOD_PUN_URI "/pun"
<Location "/pun">
AuthType Basic
AuthName "Private"
AuthUserFile "/opt/rh/httpd24/root/etc/httpd/.htpasswd"
RequestHeader unset Authorization
Require valid-user
ProxyPassReverse "http://foo.bar/pun"

# ProxyPassReverseCookieDomain implementation (strip domain)
Header edit* Set-Cookie ";\s*(?i)Domain[^;]*" ""
# ProxyPassReverseCookiePath implementation (less restrictive)
Header edit* Set-Cookie ";\s*(?i)Path\s*=(?-i)(?!\s*/pun)[^;]*" "; Path=/pun"

SetEnv OOD_PUN_SOCKET_ROOT "/var/run/nginx"
SetEnv OOD_PUN_MAX_RETRIES "5"
LuaHookFixups pun_proxy.lua pun_proxy_handler

Control backend PUN for authenticated user:
NB: See mod_ood_proxy for more details.

http://localhost:80/nginx/stop
#=> stops the authenticated user's PUN

SetEnv OOD_NGINX_URI "/nginx"
<Location "/nginx">
AuthType Basic
AuthName "Private"
AuthUserFile "/opt/rh/httpd24/root/etc/httpd/.htpasswd"
RequestHeader unset Authorization
Require valid-user
LuaHookFixups nginx.lua nginx_handler

Redirect root URI to specified URI

http://localhost:80/
#=> http://localhost:80/pun/sys/dashboard

RedirectMatch ^/$ "/pun/sys/dashboard"
Redirect logout URI to specified redirect URI

http://localhost:80/logout
#=> http://localhost:80/pun/sys/dashboard/logout

Redirect "/logout" "/pun/sys/dashboard/logout"

CentOS 7, sorry forgot to add that

Thank you for the extra info. Looking into it. I'll keep you posted.

@jeremypmann just wanted to give you an update. My colleague tried to reproduce the problem but did not yet have success. He turned on debug logging as well and noticed that in his logs he saw:

proxy_util.c(2156): AH00942: HTTP: has acquired connection for (*)

versus what is in your log:

proxy_util.c(2156): AH00942: HTTP: has acquired connection for ()

Do you by any chance have an /etc/ood/config/nginx_stage.yml file and if so what modifications have you made to it? Feel free to contact me directly if you want to share some more details that might not be appropriate to post on a public issue<EMAIL_ADDRESS>

I do have a nginx_stage.yml file but it is the default file with all options commented out. One question, could the issue be we do not have a FQDN for our test portal, we are just using the DHCP address.

@treydock would DHCP affect anything?

DHCP should not cause problems unless the host getting DHCP isn't able to determine it's hostname.  The OSC systems hosting OnDemand all use DHCP but if you run the command hostname at command line you get the FQDN of the node.  We do set HOSTNAME to FQDN in /etc/sysconfig/network but it's possible for FQDN to be provided by DHCP too which is what we do on cluster compute nodes.

Trey, could the issue also be that I am trying to run the OnDemand portal on the login node? We have a small test cluster consisting of 1 login node, 1 head node and 2 compute nodes. I figured I could put OnDemand on the login node. I have reinstalled the login node multiple times starting from a fresh OS each time and each time I get the same error. If you are able to I can create you an account so you can SSH in and poke around.

Jeremy Mann
Enterprise Research Solutions Engineer
Research Computing Support
The University of Texas at San Antonio
(210) 458-4074
Jeremy.Mann<EMAIL_ADDRESS>[LOGO]
Not satisfied with the service you’re receiving? LET’S TALK! I’m open to all comments and suggestions.  Also, feel free to contact my manager Brent League 458-5877.  We want to give you the best experience in Research Technology.

From: treydock<EMAIL_ADDRESS>Sent: Thursday, October 18, 2018 1:11:05 PM
To: OSC/Open-OnDemand
Cc: Jeremy Mann; Mention
Subject: Re: [OSC/Open-OnDemand] Error 500 Something went wrong (#45)
DHCP should not cause problems unless the host getting DHCP isn't able to determine it's hostname. The OSC systems hosting OnDemand all use DHCP but if you run the command hostname at command line you get the FQDN of the node. We do set HOSTNAME to FQDN in /etc/sysconfig/network but it's possible for FQDN to be provided by DHCP too which is what we do on cluster compute nodes.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FOSC%2FOpen-OnDemand%2Fissues%2F45%23issuecomment-431108072&data=02|01|jeremy.mann%40utsa.edu|c6872bd2d12c43b9f9c908d63525138f|3a228dfbc64744cb88357b20617fc906|0|0|636754830719519375&sdata=65YL%2F4uPhFgw74rYNBRLt37YhwuNLkjIFAXPTEe%2FBD4%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAci4TYSJ04ER1ZIVOqpmie-2bHAqi_FLks5umMQ5gaJpZM4WufgG&data=02|01|jeremy.mann%40utsa.edu|c6872bd2d12c43b9f9c908d63525138f|3a228dfbc64744cb88357b20617fc906|0|0|636754830719529382&sdata=qfe9X83Ojb7YLdSaN6HYaye6jcQcy2aR%2B1tU3QuSYfI%3D&reserved=0.

Login node shouldn't matter unless it runs some conflicting service but that would be difficult given most services for OnDemand are under SCL.  An account would help me try to reproduce the problem on our end by replicating configs, etc.

Also got this on a RHEL 7 box.  In my case, eventually realized that each user (?) has their own nginx process running behind Apache, with its own error logs in /var/log/nginx/$USER.  In the error.log there is the helpful message
App 182097 stdout: [2018-11-15 13:46:48 -0800 ]  INFO "method=GET path=/pun/sys/dashboard/ format=html controller=DashboardController action=index status=500 error='Psych::SyntaxError: (<unknown>): found a tab character where an intendation space is expected while scanning a block scalar at line 18 column 23' durat
ion=8.80 view=0.00"
App 182097 stdout: [2018-11-15 13:46:48 -0800 ] FATAL "Psych::SyntaxError ((<unknown>): found a tab character where an intendation space is expected while scanning a block scalar at line 18 column 23):\n  app/models/batch_connect/app.rb:114:in `cluster'\n  app/models/batch_connect/app.rb:120:in `valid?'\n  app/apps
/ood_app.rb:29:in `each'\n  app/apps/ood_app.rb:29:in `none?'\n  app/apps/ood_app.rb:29:in `invalid_batch_connect_app?'\n  app/controllers/application_controller.rb:30:in `reject'\n  app/controllers/application_controller.rb:30:in `nav_sys_apps'\n  app/controllers/application_controller.rb:42:in `sys_app_groups'\n
 app/controllers/application_controller.rb:14:in `set_nav_groups'"
App 182097 stdout: [2018-11-15 13:46:48 -0800 ]  INFO "method=GET path=/pun/sys/dashboard/500 format=html controller=ErrorsController action=internal_server_error status=500 error='Psych::SyntaxError: (<unknown>): found a tab character where an intendation space is expected while scanning a block scalar at line 18
column 23' duration=8.30 view=0.00"
App 182097 stderr: Error during failsafe response: (<unknown>): found a tab character where an intendation space is expected while scanning a block scalar at line 18 column 23

Hitting nginx with strace uncovers the location of the file with the errant tab character, which is our cluster config file.
Your error might be different, but I'd start with the nginx log files.
@ericfranz : It'd be useful to have the filename mentioned in the diagnostic.  Also to syntax check the config files on startup.  (And bonus points for "intendation"!)

That was exactly the problem. I removed all tabs from the cluster config file and bingo, it works. You can close this issue.


Add main, support rule execution

The main.py file should be added to the asana_extensions root.  This should at the very least support executing all rules.  This should be straight-forward -- should largely be a wrapper for calling the appropriate method in the rules module.

This should also support input arg parsing, which at the very least should allow configuring whether to force test report only mode and to set a logger level (full logger config will be left to #22).


[engsys] update dev dependency typedoc

[cosmos] Update dev dependency "typedoc" #9327

Why only cosmos? Almost all packages in our repo have a dev dependency typedoc...

I copied Mike's notes.  Apparently things has changed since then.  Description updated.

Now, that we have dropped support for Node.js 10 in our test matrix, we can move to the latest version of typedoc
There are 2 kinds of places where we take a dependency on typedoc

The generate-doc tool. When updating here, the index.js file in the linked folder will also need to be updated as certain options are no longer supported in the latest version of typedoc
In the package.json for most of the packages in this repo as a devDependency. When updating here, the docs script in the same file will need to be updated as certain options are no longer supported in the latest version of typedoc

@deyaaeldeen, We added the docs script for each package in https://github.com/Azure/azure-sdk-for-js/pull/12941 so that we have a way to see what the ref docs would look like in docs.microsoft.com.
Recently, we added the ability to see the ref docs in review.docs.microsoft.com on a daily basis i.e. changes that go to the main branch today are review-able the next day. With this new ability and the potential for our docs script to have gaps compared to what the docs team actually uses, I don't see much value in us having the docs script anymore. Thoughts?
cc @witemple-msft @KarishmaGhiya

@ramya-rao-a I agree on ditching the docs command. On one hand, it will still be faster for you to review changes using it instead of having to commit your changes to main and then wait for the next scheduled job of the doc generation. On the other hand, the speed should not really matter that much because typically we inspect the documentation as a whole before we release.

Thanks @deyaaeldeen!
For anyone looking to pick up this issue, below are the set of tasks

Remove the docs script from the package.json file of all the packages in this repo and the devDependency on typedoc
Update the generate-doc tool to use the latest version of typedoc. When updating here, the index.js file in the linked folder will also need to be updated as certain options are no longer supported in the latest version of typedoc.

it will still be faster for you to review changes using it instead of having to commit your changes to main and then wait for the next scheduled job of the doc generation.

We also build and upload the output as an artifact in the CI pipeline so we could review the doc artifact if needed.

The only way I've ever previewed these docs is by downloading the doc zip file from the pipeline like Jeremy is suggesting. If the docs script isn't used in the pipeline and isn't something devs are actually using day-to-day anymore, than lets kill it.

Please close #19241 after we done removing typedoc dependency and the docs NPM scripts


Add dockerfile to make it easier to use aflgo

Maybe the following could be added to the readme
How to use AFLGO with Docker
Build with Docker
$ docker build -t aflgo .

$ docker images

REPOSITORY          TAG                 IMAGE ID            CREATED             SIZE
aflgo               latest              2082a1056d39        3 minutes ago      6.06GB
ubuntu              18.04               dcf4d4bef137        6 weeks ago        63.2MB

Use an already built docker image [Recommend]
docker pull ricardio609/aflgo

Once the build or pull has been successful, lunch the Docker image to test out AFLGO.
# use --privileged flag to allow docker to mount a ramdisk

$ docker run --cap-add=SYS_PTRACE --privileged -it aflgo:latest /bin/bash    #build

$ docker run --cap-add=SYS_PTRACE --privileged -it ricardio609/aflgo:latest /bin/bash    #pull an already built docker image


Use floskell from hackage

Thanks to @ennocramer for the upload https://github.com/ennocramer/floskell/issues/6#issuecomment-489230007

@bubba did you follow the process outlined in the top of .gitmodules to remove the submodule?

@alanz I've deleted and checked in submodules/floskell folder, but was not able to find/delete it in .git/modules, although this is inside a different worktree, whilst I also have master checked at the same time.


Do not assign previously assigned node

On node failure, db.Nodes() may return a node even if it was unassigned due to lease expiration. In this case, we should not assign it anymore.

Maybe think about different TTLs for db.Nodes() and assignments?

This cannot happen anymore since a node is assigned with its lease coupled to next.
It should be checked that a "no such lease" error does not kill the assignment


Timeslider tests fix

@jesusvazquez these are not depending on timezones anymore, shouldn't give you any problems.

@fdansv it's now working. Thank you.


Make LanguageModelOptions (like ChatOpenAIOptions) more bind-friendly

Feature request
LanguageModelOptions (like ChatOpenAIOptions, ChatMistralAIOptions etc) should not set a default model, as this will reset the model to the default one every time you use the bind operator (for instance). Example:
final llm = ChatOpenAI(
  defaultOptions: const ChatOpenAIOptions(model: 'gpt-4o', temperature: 0.1),
);
final modifiedLlm = llm.bind(const ChatOpenAIOptions(temperature: 1.0));
// Below invocation will use the default gpt-3.5-turbo model, instead of
// the expected gpt-4o model
final res = await modifiedLlm.invoke(PromptValue.string('Hello'));

Motivation
Removing the default value (and moving it into the Chat/LLM API implementations) will improve the developer experience and reduce the likelihood of errors (using the incorrect model). It would also be more in line with the Python implementation.

Hey @tolo ,
Thanks for the suggestion. It was something I had in mind as I already got a couple of reports of people getting confused about why the wrong model was used (e.g. when binding tools).
I would still like to keep model as part of the options, as that allows the use of the same wrapper (and underlying HTTP client) for calling different models.
So maybe we can have something like:
const defaultModel = 'gpt-3.5-turbo';

//...

class ChatOpenAI extends BaseChatModel<ChatOpenAIOptions> {

  ChatOpenAI({
    //...
    super.defaultOptions = const ChatOpenAIOptions(
      model: defaultModel,
    ),
  });

  //...

  CreateChatCompletionRequest _createChatCompletionRequest(
    final List<ChatMessage> messages, {
    final ChatOpenAIOptions? options,
    final bool stream = false,
  }) {
    return CreateChatCompletionRequest(
      model: ChatCompletionModel.modelId(
        options?.model ?? defaultOptions.model ?? defaultModel,
      ),
      //...
    );
  )

And remove the default value from the ChatOpenAIOptions constructor.
What do you think?

Yes, the model property should definitely remain in the options classes, it's just the default value in the constructor that should be removed. So above (falling back on default model instead of throwing error I guess?) looks good provided that is done. 👍

This should further improve the binding experience:
https://github.com/davidmigloz/langchain_dart/pull/500


Added More Cities Support and Simple Bar React for UI

Hello,
I've added some more cities functionality

Los Angeles
Paris
Tokyo
Shanghai
Dubai
Chennai
Cairo
Mumbai
Istanbul
São Paulo
Seoul

I've also implemented simplebar-react for a hidden and minimalistic scrollbar that allows for a clean look of the map, simultaneously allowing support of many cities.

Type of change
[✔ ] New feature (non-breaking change which adds functionality)
Checklist:

[✔ ] My code follows the style guidelines of this project
[✔ ] I have performed a self-review of my own code
[✔ ] I have commented my code, particularly in hard-to-understand areas
[✔ ] I have made corresponding changes to the documentation
[✔ ] My changes generate no new warnings
[✔ ] I have added tests that prove my fix is effective or that my feature works
[ ✔] New and existing unit tests pass locally with my changes
[✔ ] Any dependent changes have been merged and published in downstream modules


chore(rate): increase API rate limit

Pull Request Test Coverage Report for Build 1799

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 64.286%

Totals

Change from base Build 1798:
0.0%

Covered Lines:
106

Relevant Lines:
157

💛  - Coveralls


bug: Several collection-repeat on the same template

Type: bug
Platform: android 4.4 webview
I have a ion-list with several ion-item like that:
<ion-list>
        <ion-item class="item-divider">
            Pending
        </ion-item>
        <ion-item
                collection-repeat="pending in pendings">

{{pending}}

        </ion-item>
        <ion-item class="item-divider">
            Recent
        </ion-item>
        <ion-item class="item-text-wrap"
                  collection-repeat="recent in recents">

{{recent}}

        </ion-item>
</ion-list>

The items are not displayed and I get
Uncaught RangeError: Maximum call stack size exceeded
RepeatController.scrollView.__callback

The error is in the following code:
    scrollView.__callback = function(transformLeft, transformTop, zoom, wasResize) {
      var scrollValue = view.getScrollValue();
      if (renderStartIndex === -1 ||
          scrollValue + view.scrollPrimarySize > renderAfterBoundary ||
          scrollValue < renderBeforeBoundary) {
        render();
      }
   ====>   scrollView.__$callback(transformLeft, transformTop, zoom, wasResize);
    };

Please note that this error occurs with JS Scrolling. If I have only one collection-repeat instead of 2, it's OK.
I also tried one collection-repeat and one ng-repeat with native scrolling and the collection-repeat does not display all the items.

have the same issue rc3. haven't tried upgrading or usering overflow-scroll="true" yet though.

Collection-repeat does not work with native scrolling. As of 1.0, it will force JS scrolling, but in the earlier RCs it would break collection-repeat.
Collection-repeat heavily manipulates the scrollable area, and does not play well with multiple collection-repeats. To achieve this functionality, nest them inside ion-scroll elements.

i have same problem, any suggestion?
ion-scroll didn't do the trick

:+1: Same problem

@lightZam @diegobill What version of ionic are guys seeing this issue with?

@jgw96  ionic 1.7.12

@jgw96 same issue.

@jgw96 ionic 1.7.12

Sorry, would you be able to post the output of ionic info 1.7.12 is the cli version not the version of the framework your using. Sorry should have been more clear!

@jgw96
--
Cordova CLI: 5.3.3
Gulp version:  CLI version 3.9.0
Gulp local:   Local version 3.9.1
Ionic Version: 1.2.4
Ionic CLI Version: 1.7.14
Ionic App Lib Version: 0.7.0

Same issue when using chrome or an android device... Is there any other way to fix it than replacing the 2nd collection-repeat or both by ng-repeat ?
Dev Environment :
Node Version : 4.4.0
Ionic CLI : 1.7.14
Ionic App : 0.7.0
Angular : 1.5.3

+1 same issue here.
Cordova CLI: 6.1.1
Gulp version:  CLI version 3.9.0
Gulp local:   Local version 3.9.0
Ionic Version: 1.3.0
Ionic CLI Version: 1.7.14
Ionic App Lib Version: 0.7.0
OS: Distributor ID:	LinuxMint Description:	Linux Mint 17.2 Rafaela
Node Version: v0.12.14

How multiple collection-repeats to play with ion-scroll ?

same issue ..

Same here. In my case, I see errors in the console but the elements look smaller than the specified height. @perrygovier When I wrap the collections inside ionic-scroll elements, I don't see anything, not even an error.

Same issue over here to..
Is this a bug or it is out of scope of collection-repeat (It is not met to do this)
Do any one have at least tempory fix to this

+1

You can use ng-repeat instead of collection-repeat where this happens.
ng-repeat is not ideal but it is working

I have the same problem with only one collection-repeat. appears when i go to another page. but all items are displayed.

+1. Now use ng-repeat, but it's slow for >100 records list
Cordova CLI: 6.3.1
Gulp version:  CLI version 3.9.0
Gulp local:   Local version 3.9.1
Ionic Framework Version: 1.3.1
Ionic CLI Version: 1.7.16
Ionic App Lib Version: 0.7.3
OS: Distributor ID:	Ubuntu Description:	Ubuntu 15.04
Node Version: v1.8.4


Bug: rotate_iou CUDA mode

🐛 Bug

from maskrcnn_benchmark.layers.rotate_nms import rotate_iou
a=torch.tensor([[50.7325,50.7325,100.7325,300.7325,-3.4]]).float().to('cuda')
b=torch.tensor([[50.7325,50.7325,100.7325,300.7325,-3.4]]).float().to('cuda')
rotate_iou(a,b)     # get the result 0.3333
a=torch.tensor([[50.7325,50.7325,100.7325,300.7325,-3.4]]).float()
b=torch.tensor([[50.7325,50.7325,100.7325,300.7325,-3.4]]).float()
rotate_iou(a,b)   # get the result 1.0

however, when I test on the cpu mode,
It return the result, tensor=1.0
Quite surprised to debug the result, maybe the rotate_iou cuda version is wrong?
Whats more, I test the rotated ops file (maskrcnn_benchmark/modeling/rotate_ops.py) the rotated version used in GPU mode is slower than CPU mode. It's because the test box array is small?
@mrlooi , hope for your updates, Thanks

Hey, that's interesting. I remember I've tested the cuda version and it works fine, maybe I've missed something. Lately I don't have time to make adjustments to this repo, so if you do find a fix, pull requests are very welcome!

@mrlooi  Hello, thanks for your reply.
I find the problem is caused mainly by the float precision, maybe you will get inspirations from this point. I am not familiar to cuda code, hope you can renew this file.
Maybe you can refer to the detectron2 project. reference link
Hope you can update the files. Thanks very much.

Hey thanks for sharing the detectron2, it looks good. I remember fixing the code to handle those floating precision errors, and even so the results shouldn't be that different. Will have a look at it when I find the time. Thanks again for pointing it out

Hello, Thanks for your reply.
Looking forward to your updates.

I don't unfortunately, but you can still use the code as it is.
I tested the code, and the results are different from cpu only if the numbers are exactly the same.

@mrlooi  Thanks for your reply.
I have used rotated iou script in detectron2  project. successfully ported to your project.

add_gt_proposals - I did this to augment the shape of the rotated boxes. The motivation was to increase robustness to differences in rotated box width + height, since there is more variability in rotated boxes than bounding boxes
cos function - I found a very slight AP improvement using cos (+0.02 AP). But this may vary. Bottom line: I found somewhat negligible impact, and marginal improvement at best
Comments: those are just there for reference


defined option classes should be passed to selectable/selected divs

I had some issues styling the selected/selectable divs based on the unique classes (polymorphic set of items) provided directly to the options.  This pull request adds support for this by passing any explicit classes from the options to their selectable/selected counterpart within multi-select.

This doesn't work right when no classes are passed in explicitly, it writes out 'undefiend' as the class.
You should probably check if the class exists first, then write it out, otherwise don't do it.

Nice catch @top-flight,
I just pushed a fix vor this one.
ps: sorry for the delay I was on "offline" vacation for 3 weeks.


The compiler says the code is unable to parse! how do i fix?

when i run the compiler it gives me this error:

skip the compiler, just store it in /bin


Rite Aid Scraper is currently showing all locations as unavailable

It looks like the Rite Aid data format changed so availableSlots is always an empty array. Need to figure out what different API calls we need to make to get actual data.

Disabled the scraper for now in #527, will investigate this afternoon. It may or may not be worth fixing, since the official API looks to be working again.


SDA-8882 | fix: add more validations before terminating run for upgrade roles

Related issue: https://issues.redhat.com/browse/SDA-8882
What
Flow was being terminated beforehand when executing in manual mode
Why
Customer was not being listed the commands for the operator roles

/lgtm


Defect in d0323r2 Expected: Implicit conversion from T cannot be combined with ordering operators

Feedback from ACCU was pretty clear the audience would prefer implicit construction for both E and T where E and T are not constructible into one another. I know you dislike that, and I entirely see your reasoning.
However they were very clear they would far prefer implicit construction from T over Expected being default usable in associative containers. After all, if you really want to store Expected in one of those, you can define custom comparison and hash functions for the STL container. They don't need to be free functions.

The first paragraph has nothing to be with the title.
expected is implicitly convertible from T already.
What is the issue? that you want operator < to be removed?

What is the issue? that you want operator < to be removed

The defect is you cannot have both as is currently proposed.
One resolution is always explicit construction via make_expected. Another is to remove the comparison operators. I, and the ACCU audience, prefer the latter.

This is not a more defect to the current situation for optional. It is defined like it is. It has the gotcha described by Andrzej.
The paper already mention it and it is up to the committee to decide. My suggestion is to have explicit constructors. I can understand that some prefer to remove the comparison operators, but I aside the failing intents of Tony Van Eerd I have no see any paper trying to fix this issue in optional.
If you consider that this is an issue that must be addressed by the committee please write a paper or at least post a mail in the std-proposal ML. We have time until expected will integrate a TS or the IS.

We have removed the comparison operators on the last proposal.


Rounding up CFS numbers in combination with a common multiprocessing use case will result in the process being throttled

Hi 👋
a very common pattern I've spotted is to spawn cpu_count number of threads with multiprocessing library. That leaves you with cpu_count + 1 threads, but the main thread commonly tends to chill until the others are done, so that's mostly fine if cfs_quota / cfs_period is a whole number. One could guarantee no throttling by spawning cpu_count - 1 threads in such a scenario as well.
You run into a problem if cfs_quota / cfs_period isn't a whole number given ceiling the number has been a chosen strategy. If your threads hammer the cpu, you're guaranteed to be throttled, unless you spawn cpu_count - 2 or fewer threads.
I wonder whether this library could help alleviate this issue, by either providing an option to choose between ceil or floor or by having an option to return float from cpu_count function.
What do you think?

Hello, thanks for taking interest in this lib.
About the issue you raise, those are very good points. I think the matter of choosing between ceil and floor strategies can be better solved with the introduction of a tolerance argument. That would allow users to choose the decimal cut-off they want and also allow avoiding some hypothetical odd edge cases such as a 1000ms quota with a 1999ms period resulting in 1 thread with a hard floor, instead of the more sane 2 threads result.
What I am thinking is something like this:
# Considering a 1000ms quota and 2750ms period on a 4 core machine

# Sane floor
cpu_count(tolerance=0.99) #> 2 Threads

# Sane ceil
cpu_count(tolerance=0.01) #> 3 Threads

# Round
cpu_count(tolerance=0.5) #> 3 Threads

# Skewed Round
cpu_count(tolerance=0.8) #> 2 Threads

# Hard floor
cpu_count(tolerance=1) #> 2 Threads

# Hard ceil
cpu_count(tolerance=0) #> 3 Threads

@rugg2, @cvonsteg any thoguhts on the intuitiveness of the above?


Make editor UI Panel for OBS

This wil get the md content and show it
The Editor will have editable text boxes for each image taken form the md file
Provide the place to put header and footer
For styling see the WIP folder Arpit has made the UI code for this, editor-obs.js

Feedback from Joel

Use debounce/lose focus for cursor in middle issue

Textarea fix height


Remove Hierarchy Endpoints (from 72)

Remove Hiearchy Endpoints from the middle tier after the frontend is able to handle them on its own (do this ticket after https://git.yale.edu/lux-its/lux-web/issues/1590)
Note: 1590 is closed.
Blocked by: https://git.yale.edu/lux-its/lux-web/issues/1723 | https://github.com/project-lux/lux-frontend/issues/25
Blocking: https://git.yale.edu/lux-its/lux-web/issues/2030 | https://github.com/project-lux/lux-frontend/issues/84
Bugherd: https://www.bugherd.com/projects/284041/tasks/1582

@kamerynB - was this deployed?


[WIP] Add a signal when the link status changes

This PR references #27. As of now, only a test signal has been added to confirm if the implementation of django-signals and the process of sending signals is right.

Coverage remained the same at 100.0% when pulling 305d51bcef8613e1366a8aba52b9da837d3c4c99 on rohithasrk:link-status-signal into e300a6784865540a5afbf5a701fc842911ad1bbb on netjson:master.

Coverage remained the same at 100.0% when pulling 174f2f9bd85daa13e0f7ace0789c59b28cad3732 on rohithasrk:link-status-signal into e300a6784865540a5afbf5a701fc842911ad1bbb on netjson:master.

Coverage remained the same at 100.0% when pulling e820d2636752eebc0bb121be9122b67af5c59fb6 on rohithasrk:link-status-signal into e300a6784865540a5afbf5a701fc842911ad1bbb on netjson:master.

Coverage remained the same at 100.0% when pulling 12205d4251326e71f56fcee0292d8ba49babd030 on rohithasrk:link-status-signal into e300a6784865540a5afbf5a701fc842911ad1bbb on netjson:master.


Demo code in documentation doesn't work

Running on Debian unstable with an upgraded Python Requests 4.6.  Consider this code taken from the documentation:
import pycrest
eve = pycrest.EVE()

eve()

print(eve.motd)
print(eve.incursions)
print(eve.incursions())
print(eve.incursions().totalCount)

def getByAttrVal(objlist, attr, val):
    ''' Searches list of dicts for a dict with dict[attr] == val '''
    matches = [getattr(obj, attr) == val for obj in objlist]
    index = matches.index(True)  # find first match, raise ValueError if not found
    return objlist[index]

def getAllItems(page):
    ''' Fetch data from all pages '''
    ret = page().items
    while hasattr(page(), 'next'):
        page = page().next()
        ret.extend(page().items)
    return ret

region = getByAttrVal(eve.regions().items, 'name', 'Catch')
item = getByAttrVal(getAllItems(eve.itemTypes), 'name', 'Tritanium').href
print(getAllItems(region().marketSellOrders(type=item)))

gives me this:
Traceback (most recent call last):
  File "std-demo.py", line 27, in <module>
    print(getAllItems(region().marketSellOrders(type=item)))
  File "/usr/local/lib/python3.4/dist-packages/pycrest-0.0.5-py3.4.egg/pycrest/eve.py", line 314, in __call__
  File "/usr/local/lib/python3.4/dist-packages/pycrest-0.0.5-py3.4.egg/pycrest/eve.py", line 151, in get
pycrest.errors.APIException: Got unexpected status code from server: 404

Thanks much for any help you can give!

Can you try that over an authenticated API connection? The last time I
played with this, CCP was throwing 404 even if the same endpoint was
available after auth.
If that's the case then this is pretty much a doc bug (sorry!).
2015-04-02 8:29 GMT+02:00 Bart Massey<EMAIL_ADDRESS>
Running on Debian unstable with an upgraded Python Requests 4.6. Consider
this code taken from the documentation:
import pycrest
eve = pycrest.EVE()
eve()
print(eve.motd)print(eve.incursions)print(eve.incursions())print(eve.incursions().totalCount)
def getByAttrVal(objlist, attr, val):
''' Searches list of dicts for a dict with dict[attr] == val '''
matches = [getattr(obj, attr) == val for obj in objlist]
index = matches.index(True)  # find first match, raise ValueError if not found
return objlist[index]
def getAllItems(page):
''' Fetch data from all pages '''
ret = page().items
while hasattr(page(), 'next'):
page = page().next()
ret.extend(page().items)
return ret
region = getByAttrVal(eve.regions().items, 'name', 'Catch')
item = getByAttrVal(getAllItems(eve.itemTypes), 'name', 'Tritanium').hrefprint(getAllItems(region().marketSellOrders(type=item)))
gives me this:
Traceback (most recent call last):
File "std-demo.py", line 27, in
print(getAllItems(region().marketSellOrders(type=item)))
File "/usr/local/lib/python3.4/dist-packages/pycrest-0.0.5-py3.4.egg/pycrest/eve.py", line 314, in call
File "/usr/local/lib/python3.4/dist-packages/pycrest-0.0.5-py3.4.egg/pycrest/eve.py", line 151, in get
pycrest.errors.APIException: Got unexpected status code from server: 404
Thanks much for any help you can give!
--
Reply to this email directly or view it on GitHub
https://github.com/Dreae/PyCrest/issues/8.

The marketSellOrders endpoint definitely requires authentication as described here: https://developers.eveonline.com/blog/article/nom-nom-tastey-market-data

K. Thanks for looking at it. I'll try to figure out how to get authenticated crest working without standing on my head.


Fixes timestamp errors occurring during retransmission where RTMP eve…

…nts are packed differently

@Andy--S If you're confident with this, I'll get it in and released.

Only one small issue, it needs to be PR'd against relocated sources.. https://github.com/Red5/red5-server/tree/master/common


Change versioning schema

The current schema is
{major}.{minor}.{patch}-{release}
I want to change it to more flexible
{major}.{minor}.{patch}-{release}{pre-release}.{build}
pre-release part is a value-type part:
alpha
beta
rc

Changed to
{major}.{minor}.{patch}-{release}.{build}


[MBO-941] Fix hook detection to reposition dashboardZoneTwo and fix on PS Install

Ok for me, maybe add a migration 4.4.2 with the call of the function ?


A library uses the same package

Error:Execution failed for task ':library:processDebugResources'.

Error: A library uses the same package as this project: com.arlib.floatingsearchview

@rakesh779 can you look at issue #45 and let me know if it is related to your issue?


keyd doest start deamon it appears

Describe the bug
After installing the keyd package there is no systemd service running. I am sorry if this is the intended behavior, but it seemed weird to me.
Steps To Reproduce
Steps to reproduce the behavior:

Add keyd to your system
sudo systemctl status keyd // not found

Expected behavior
The deamon / service to be started & enabled on system startup
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
Notify maintainers
@peterhoeg

Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.5.3, NixOS, 23.11 (Tapir), 23.11.20230915.bdc382d`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.17.0`
 - channels(albert): `""`
 - channels(root): `"home-manager, nixos, nixos-hardware"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

Sticking a package into `environment.systemPackages' does not make it launch.
Have a look at this NixOS option instead: https://search.nixos.org/options?channel=23.05&show=services.keyd.enable&from=0&size=50&sort=relevance&type=packages&query=keyd


KSP Interstellar Extended

Here is a .netkan file for Interstellar Extended, please add it to the repository. The file was created in collaboration with FreeThinker, the current mod maintainer.
https://gist.github.com/A2K/ac4e0275c222b741169c

I concur

It doesn't depend on InterstellarFuelSwitch?

Dazpoet, as far as I know InterstellarFuelSwitch was originally part of the Interstellar mod, but you can play Interstellar without fuel switch. I'm not sure, maybe it is absolutely necessary when using some high level technologies, that's why it is listed in "recommends" section. CKAN GUI will suggest to install the fuel switch mod when installing Interstellar Extended.

Trying to speed up the process I have created a pull request with this metadata file. Someone with write access please click the green button here: https://github.com/KSP-CKAN/NetKAN/pull/1314

InterstellarFuelSwitch is required if you want to use any propulsion

Closed via https://github.com/KSP-CKAN/NetKAN/pull/1363.


File upload visibility

Should project attachments be publicly accessible? It is also possible to configure this per upload (a checkbox when uploading to specify public/private)

Attachments should not be publicly accessible. We have to maintain Uploader-Admin confidentiality because attachments may contain sensitive information

@FezileRSA. Okay, thanks. Let me know if you are interested in working on this and/or other open bugs/issues in the repository (you indicated you might be on Friday). Send me an email on<EMAIL_ADDRESS>and I can guide you through setup and walk you through a couple contributions


Maintenance: Disable Unix and TCP sockets for unit tests

We should ensure unit tests aren't accidentally creating sockets for security and determinism purposes. A common issue is the initialization of a boto3 client that would trigger a socket - this can help us with design too.
Pytest plugin to make this easier to selectively disable groups of tests (tests/unit/conftest.py) and optionally disable/enable sockets: https://pypi.org/project/pytest-socket/

Done for stream processor


Added Open in preview action

I needed a way to view the diff in Preview (I needed to comare little details). Here's a little bit crude implementation but it works.

would love a screenshot of new UI

There's no major difference

It should probably be something like "Open diff in Preview" will fix it.

I'm alright with this :+1:

Thanks of the PR


Question: why do we need to pass actual schema to the constructor to flink if the schemas are in the schema registry?

In https://github.com/awslabs/aws-glue-schema-registry?tab=readme-ov-file#flink-kafka-consumer-with-avro-format
when flink needs to get generic Avro record, why do we need actual schema in
            GlueSchemaRegistryAvroDeserializationSchema.forGeneric(schema, configs),

When message is read from kafka, the magic bytes are used to find the schema ID from schema registry, which is then used to fetch the actual schema.
If the actual schema is in the schema registry, why do we need to still pass the schema when creating Flink source?
In our case, we have large number of schemas, and would like to have a single source that can read all of them.

Oh, you are right. Thnx, feel free to close.
On Thu, 26 Sept 2024, 7:43 pm Oli Scherer, @.***> wrote:

I think you're in the wrong repo. This is about serialization and
deserialization of Rust code
—
Reply to this email directly, view it on GitHub
https://github.com/serde-rs/serde/issues/2830#issuecomment-2377677423,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFZ6RH5QBOXKCTJOTUCUA3ZYRIW3AVCNFSM6AAAAABO5NUB72VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNZXGY3TONBSGM
.
You are receiving this because you authored the thread.Message ID:
@.***>


Invalid / unbalanced HTML in the embed card won't save.

The HTML parser used by the embed card doesn't respond well to malformed HTML.
To reproduce:

Create an HTML card
Type in <h1>TEST
Save

We either need to find a new HTML parser or save broken HTML as plain text.

To play DA here, why do we need to parse the HTML?

I really wish we didn't have to.
Because the mobiledoc-html-renderer was deprecated we've switched to the mobiledoc-dom-renderer which uses the Ember simple-dom library, although it has just occurred to me that we can pass in any library which simulates the DOM so should be able to use jsdom directly and not as a middle man 🤦♂.
If we don't want to parse the HTML we need to revert to mobiledoc-html-renderer.
For our light weight use case for cards on the frontend the HTML renderer is the better option, I'll find out why it was deprecated.

OK cool, cos parsing HTML just to render a blog post is total overkill IMO 👍

I agree.

I've left it using the mobiledoc-dom-renderer as recommended by the mobiledoc project, if this starts causing problems then we can move back to the unsupported mobiledoc-html-renderer.
My main reason for doing this is because Mobiledoc is moving to 1.0, and while the features haven't been finalised yet we can expect some breaking changes.


Does node-sass support spaces in map keys?

Hi,
I'm using a library which has a palette function that throws an error when using node-sass when a map key has spaces.
For details see:
https://github.com/danlevan/google-material-color/issues/13
Even though spaces in key names doesn't seem like a good idea they are supported in other sass bindings.
Can you confirm if they are supported or not?

If it's in Sass it should in Node Sass. We can't confirm every possible use case. If you can confirm it doesn't work please open an issue.


let param type to be public

the param type is private _ParameterList, it cause i can't specify type annotation, dart analysis will report this warning (I use flutter project analysis_option)

Using list is inspired by koin, of course using map is also possible. @windrunner414

@ditclear I use code generator to  use it easier and named parameters
but _ParameterList is private, I can't specify type annotation like single(({ParameterList param})=>x())
Although it won't cause any problems, but dart analysis server report a warning if u open related option
I think ParameterList should be public

@windrunner414
You can copy the dartin.dart file and make _ParameterList public


4.6 compatibility?

I have installed a fresh ckeditor build with this tabletoolstoolbar addon included.
The plugin folder did not contain a plugin.js or icons.
I manually downloaded and applied, but still not displaying in 4.6 build.
Is there a problem with 4.6?

Ignore this. I finally realise that there is a new toolbar feature called groups that i have to implement and use in my custom toolbars.


Importing one user.js into another?

I would like to separate betterfox's user.js and my custom changes in it, so instead of manually copy pasting my custom changes to the updated betterfox user.js every time it updates, would be great to have one that is being git pulled all the time, and another that imports it and applies the custom changes. Would this work with how Firefox handles things, I have no idea what js version/handling they use for such thing.
File 1 (betterfox_user.js):
/** DISK CACHE ***/
user_pref("browser.cache.jsbc_compression_level", 3);

/** MEDIA CACHE ***/
user_pref("media.memory_cache_max_size", 65536);
user_pref("media.cache_readahead_limit", 7200);
user_pref("media.cache_resume_threshold", 3600);

File 2 (user.js):
/** Import Betterfox and make custom changes ***/

import './betterfox_user.js';

user_pref("media.cache_readahead_limit", 3600);
user_pref("browser.urlbar.trimHttps", false);

This way I always keep user.js clean, can git pull/curl when updates are needed, and play with my custom config without touching the betterfox config?

Please see https://github.com/yokoffing/Betterfox/pull/318


Reporting: Skipped Test

Was the parameter_ordering test skipped mostly for report generation testing purposes? It seems like a test like this shouldn't be included in the report. It makes sense that a Node might raise this exception, but we should require a description/reason for skipping (maybe it's a bug, maybe it's intentional, ...).
In the future, the framework might skip tests if we have a capabilities model, the test is associated with required capabilities, and we know the server(s) being tested don't have that capability.

The parameter_ordering test being not fleshed out was just me being lazy. Sorry.
Also https://github.com/fediverse-devnet/feditest/pull/151


python3Packages.pyssim: 0.4 -> 0.6

Description of changes
https://github.com/jterrace/pyssim/blob/master/CHANGES.md
Update pyssim to 0.6. This also unbreaks it.

Things done

Built on platform(s)

[x] x86_64-linux
[x] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

@ofborg eval


track user id in GA for better support

TODO: I need to provide the cookie policy updates

@dreamfall we need to add similar copy to to the cookie policy as https://www.universal-credit.service.gov.uk/cookiepolicy/
We then need to allow users to opt-out by dropping another cookie that disables this.

Added a card for this https://trello.com/c/GPbJyASi/655-add-userid-tracking-to-google-analytics

 [QAE17] Add User_ID tracking to google analytics


Consider removing optional operator address

See this issue for a default address while IL-DCP is pending - https://github.com/interledger-rs/interledger-rs/issues/279
In other words, we can use something like ‘local.host’ while IL-DCP is working.
Same for accounts that are newly added as children .

This is blocked by https://github.com/hyperledger/quilt/issues/259

During this change, consider this suggestion/proposal from Adrian in the Interledger Slack:

While we’re at it: An alternative approach is for connectors to be able to have multiple addresses.Assuming that connectors have a routing table that maps an address/address prefix to a peer (with a weighting that orders these when they are equal), one way to store the local address of the connector is to have an entry in the routing table that maps to a special peer, local. If you do this then you can have more than one address that maps to local and the default address that maps to local can be self. When the connector needs to determine it’s own address (to answer an IL-DCP request, for example) it can get all addresses from the routing table for the local peer, ordered by weight and use the top one.

This will get resolved by #312


pull request for e2e test at 12/25/2016 12:45:07

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/31480

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/41183

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/62748


Add yauaa 1-0-4

Thanks for your pull request. Is this your first contribution to a Snowplow open source project? Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
:memo: Please visit https://docs.snowplowanalytics.com/docs/contributing/contributor-license-agreement/ to learn more and sign.
Once you've signed, please reply here (e.g. I signed it!) and we'll verify. Thanks.

The yauaa schema already got thoroughly reviewed in a previous PR.  It was not included in the R136 release, because of concerns about breaking RDB loader migrations.
Since then, RDB Loader 4.3.0 was released, which fixes the bug in which Redshift columns were not altered for the new field lengths.  So we are safe to release a new version of yauaa schema with longer field lengths.
We have not, however, fixed a different RDB Loader bug which causes problems when evolving a schema to have new fields.  This bug is going to take longer to fix.  It is a race condition, so it will affect some pipelines, but not others.  Given the high number of pipelines that use the yauaa schema, I think it is dangerous to add a new field to this schema.
This new PR therefore drops the idea of adding a new field webviewAppNameVersion.  This field is generated by newer versions of the yauaa lib, but we will configure Enrich so it filters out this field when we update the yauaa version.

LGTM

Update: I also removed format: email from the field agentInformationEmail in the yauaa schema.  Because the new yauaa lib outputs "Unknown" for this field.  I can't imagine this will upset any downstream consumers of this data.

LGTM, one note, I think we should make it very clear in the Enrich release which includes this new schema that they should be running RDB Loader 4.3+ to ensure they don't hit the length issue.

@paulboocock it's a bit more complicated:  The RDB Loader migrates tables immediately when the schema is published.  So if a pipeline has events containing 1-0-3 and tomorrow we release 1-0-4 then the loader would tomorrow migrate the table.  It's always been this way, and it's a horrible design decision.
So for anyone running a version of RDB Loader released between April 2022 and 6th September 2022, the migration will "run" but won't actually change the column lengths.  Nothing will break, and open source users won't immediately notice that anything happened.
It could only affect pipelines later, when they upgrade to an Enrich with a newer version of yauaa.  Some events might exceed the maximum lengths in their warehouse, and then loading would break.  When it gets this far, it will not even help to update their RDB loader version.
It's a horrible mess.  My only suggestions to alleviate this problem are:

Put big warnings on the next Enrich release, so Redshift users know to check their warehouse columns before updating
Or release this schema as version 2-0-0.  But that sets precedent for using major bump for all iglu-central schema patches.

I think:

Put big warnings on the next Enrich release, so Redshift users know to check their warehouse columns before updating

is likely the best result we've got here in terms of balancing the situation. Bumping to 2-0-0 is also going to be extremely disruptive for users (data models everywhere) and I'd hope that anyone who is running an upgraded RDB Loader since April 2022 is reasonably on top of their upgrades.

This is now tested against RDB Loader 4.3.0 and against the pending Enrich PR

To be clear... merging this PR is not the dangerous merge.  The dangerous step (for some pipelines) will be upgrading enrich at a later date.
Having said that, it's sensible to merge this at a time of day when people are on hand to trouble shoot something unexpected.  And it's courteous to put a notice on discourse just in case.
Bear with me until I prepare a notice.  Then hopefully you can merge this either Friday morning, or a morning early next week.


Use ONNX_MLIR_SRC_ROOT to find the version file

If onnx-mlir is being built as a sub-project, CMAKE_SOURCE_DIR will point to the parent's top-level directory, rather than onnx-mlir's top-level directory. This can can cause issues finding the VERSION_NUMBER file.

Can one of the admins verify this patch?

@jenkins-droid test this please

Thanks for the PR. I think that @whitneywhtsang would be the best candidate to review this, thanks

Jenkins Linux amd64 Build #6229 [push] use onnx-mlir src root (... started at 19:46

Jenkins Linux s390x Build #6245 [push] use onnx-mlir src root (... started at 20:46

Jenkins Linux ppc64le Build #5367 [push] use onnx-mlir src root (... started at 20:50

Jenkins Linux s390x Build #6245 [push] use onnx-mlir src root (... passed after 1 hr 44 min

Jenkins Linux amd64 Build #6229 [push] use onnx-mlir src root (... passed after 1 hr 46 min

Jenkins Linux ppc64le Build #5367 [push] use onnx-mlir src root (... passed after 1 hr 56 min


fix/4872-Contact-Diary-Layout-Not-Centric

Description
This PR moves the background view (grey view with rounded corners) of DiaryEditEntriesTableViewCell from the contentView (and its boundaries) to the view of the cell. This way the layout is simpler and works on 12.5 devices.
Link to Jira
4872
Screenshots

Accidentally merged 1.13. Will create a new PR.


Incorrect "General Usage" code for Updating Hessian and Solution

Issue Report: Incorrect "General Usage code" for Updating Hessian
Description:
The current "General Usage" code in the SophiaG repository contains errors, particularly in the part responsible for updating the Hessian. As a result, users may face difficulties while attempting to utilize the code for general purposes. To improve the functionality and allow other PyTorch users to seamlessly test SophiaG by using the sophia.py file, I propose replacing the existing code with the following suggested code snippet.
Problematic Code (Existing):
The problematic code for updating the Hessian in the "General Usage" section is causing issues for users trying to test the SophiaG model.
# Existing code with issues in updating Hessian
import torch
from torch import nn
from sophia import SophiaG

#init model loss function and input data
model = Model()
data_loader = ...

#init the optimizer
optimizer = SophiaG(model.parameters(), lr=2e-4, betas=(0.965, 0.99), rho = 0.01, weight_decay=1e-1)

k = 10
iter_num = 0
#training loop
for epoch in range(epochs):
   for X,Y in data_loader:
       if iter_num % k != k - 1:
           # standard training code
           logits, loss = model(X, Y)
           loss.backward()
           optimizer.step(bs=4096)
           optimizer.zero_grad(set_to_none=True)
           iter_num += 1
       else:
           # standard training code
           logits, loss = model(X, Y)
           loss.backward()
           optimizer.step(bs=4096)
           optimizer.zero_grad(set_to_none=True)
           iter_num += 1
           # update hessian EMA
           logits = model(X, None)
           samp_dist = torch.distributions.Categorical(logits=logits)
           y_sample = samp_dist.sample()
           loss_sampled = cross_entropy(logits, y_sample)
           loss_sampled.backward()
           optimizer.update_hessian()
           optimizer.zero_grad(set_to_none=True)

Suggested Improvement:
The following code snippet provides an improved version for updating the Hessian in the "General Usage" section. This code has been tested and verified to work correctly, offering a more reliable experience for users testing the SophiaG model.
# Proposed improved code for updating Hessian
import torch
import torch.nn.functional as F
from sophia import SophiaG

# init model loss function and input data
model = Model()
data_loader = ...

# init the optimizer
optimizer = SophiaG(model.parameters(), lr=2e-4, betas=(0.965, 0.99), rho=0.01, weight_decay=1e-1)

total_bs = len(data_loader)
bs = total_bs * block_size
k = 10
iter_num = -1

# training loop
for epoch in range(epochs):
    for X, Y in data_loader:
        # standard training code
        logits, loss = model(X, Y)
        loss.backward()
        optimizer.step(bs=bs)
        optimizer.zero_grad(set_to_none=True)
        iter_num += 1

        if iter_num % k != k - 1:
            continue
        else:
            # update hessian EMA
            logits, _ = model(X, None)
            samp_dist = torch.distributions.Categorical(logits=logits)
            y_sample = samp_dist.sample()
            loss_sampled = F.cross_entropy(logits.view(-1, logits.size(-1)), y_sample.view(-1), ignore_index=-1)
            loss_sampled.backward()
            optimizer.update_hessian()
            optimizer.zero_grad(set_to_none=True)
            model.zero_grad()

Steps to Reproduce:

Download the "sophia.py" file from the SophiaG repository.
Place the downloaded "sophia.py" file in the same folder as your code.
Import the SophiaG class from "sophia.py" and utilize it as a template, as provided in the suggested code snippet.

Expected Behavior:
Upon updating the Hessian using the suggested improved code, the SophiaG model should function as expected for general use cases, and users should be able to utilize the sophia.py file to test the model seamlessly.
Additional Information:
Updating the "General Usage" code with the proposed improvement will enhance the usability of the SophiaG repository for the PyTorch community. This will ensure a smooth experience for users who want to explore and experiment with the SophiaG optimizer.
Please let me know if you require any further information or assistance in resolving this issue.
Note: Before merging the changes, it is advisable to have other developers review the code and conduct additional testing to validate its correctness and efficacy.

Thanks so much for catching this! I have updated the readme as you suggested.


Test Tank Drive

Tank drive did not work the night of bag night. Need to make sure it was just the joystick numbers

Has been fixed


Sign pgp using subkey

I can't sign a message using subkey with keybase
scortes@drakaris:~$ keybase pgp sign << EOT
Teste
EOT
▶ ERROR Bad key found: no private key material or GPGKey

my log id: 672ee62ddee52be1d0a19e1c

Did you ever solve this?

I sign with subkeys all the time, I don't think this is the issue.

@nemanjan00 if you still have an issue, then do keybase log send.  Unfortunately with PGP it can be one of a million things.

I would prefer reading log myself. Where is it stored?
On November 3, 2018 3:06:19 AM GMT+01:00, Maxwell Krohn<EMAIL_ADDRESS>wrote:

@nemanjan00 if you still have an issue, then do keybase log send.
Unfortunately with PGP it can be one of a million things.
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/keybase/client/issues/5939#issuecomment-435552459

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Ok, I have sent it... 9aafdf58bbcc6410651f1c1c

Ah, I didn't realize your PGP key is a yubikey.  We don't have support for pgp sign and pgp decrypt now when the key is in a yubikey.  Just use gpg in that case. You can still use keybase for keybase pgp select, that is, to associate your PGP key with your keybase account.


DCIM ForeignKey related_name fixups and related changes

Closes: #3066
What's Changed
See changelog fragments for details. In brief this:

renames a whole bunch of related_name strings for better self-consistency (#3066)
introduces a new ForeignKeyWithAutoRelatedName helper class that we can use on abstract base classes to get related_name values like console_port_templates instead of dcim_consoleporttemplate_related

[ ] I need to open an issue to update ConfigContextSchema to use this helper so we can rename its dcim_device_related and virtualization_virtualmachine_related related-names.

Converts dcim/tests/test_filters to use Gary's awesome generic_filter_tests for all filters that it currently can be applied to.
[ ] Currently the DeviceType YAML import test is failing as I haven't updated the test to account for the renamed fields on FrontPortTemplate and PowerOutletTemplate. This pair of changes breaks compatibility with the devicetype-library repository so I want to carefully consider our approach here.
Fixes a minor bug in the example-plugin banner code that showed up when running tests with --no-buffer
Fixes an intermittent failure in the extras test for the nautobot-server runjob command.
Fixes some incorrect logic in our generic filter code that was treating FloatFields and DecimalFields as if they were integer fields.

TODO

[x] Explanation of Change(s)
[x] Added change log fragment(s) (for more information see the documentation)
n/a Attached Screenshots, Payload Example
[x] Unit, Integration Tests
[x] Documentation Updates (when adding/changing features)
[x] Example Plugin Updates (when adding/changing features)
[x] Outline Remaining Work, Constraints from Design

Can we document the best practices that are related here? The ones I see are:

has_* format
the *_count format
Assurance that there is not multiple words without an underscore
Why have vlan_group and device_bay but not device_role?


Keep Non-Warn records for Job Center sites?

Our Job Center scrapers (#126) capture Non-WARN layoff notices in a number of states. In Arizona, the site displays WARN and Non-WARN notices, whereas in Kansas, these records are not displayed on a basic web search but the nature of our scraping approach manages to capture them regardless.
Our counts appear correct, i.e.:

there are no dupes
our count of WARN notices matches the expected count from the web search listings as well as the number captured by the current (legacy) scraper
a sampling of detail page links all work (i.e. are valid records)

The open question is whether we should provide these records to end users on the platform. Our export CSVs currently retain them, and it would be easy enough to document the need for end users to filter these records for stories focusing exclusively on WARN.
As part of this decision, we should put in a call to the Job Center to get a better understanding of these records and determine if there's a compelling a reason to not provide them to end users.

Flagging that current combined CSV doesn't retain this categorization.

@chriszs @palewire Dropping non-WARN from the data posted to the platform seems highly reasonable. Closing this ticket but feel free to re-open if you think it requires further discussion

Oh, no, sorry, I mean it retains the records, but not the category metadata. I think you do want to retain the records, because there's a large amount of layoff reporting that doesn't meet WARN.


Fix Windowfocus on resizing

When resizing a non-focused window, the previously focused Window got resized.
This patch grabs focus for the actually resized window, before starting with the resizing.
resolve #68239
resolve #62194 (in this case no other window was focused previously, so there was a console-error-spam)
alternative to #62281

Thanks!


[bug]

Describe the bug
Text is Hidden in the button on the top of the home page.
To Reproduce
No response
Expected Behavior
A clear view of the button
Screenshot/ Video

Additional context
No response

Expected a clear view of text in the button.

Hey @Priyansusahoo for me it is working perfectly fine in every device, can I know which browser you are using?

Hey @Priyansusahoo for me it is working perfectly fine in every device, can I know which browser you are using?

Firefox Version 106.0.2(64-bit)

I see can you try opening it in chrome?
Firefox is not allowing the font change as well I see.

yes, it works well in brave and chrome...my bad

yes, it works well in brave and chrome

The same goes for the youtube logo on the top right, works well with chrome but not with firefox


Feature/revocation

Revocation implementation. Also the API for the value sets

Hi @ryanbnl
Can you review this?

I'm going to dig in, so will hopefully be finished tomorrow :)

thanks @ryanbnl
Think I addressed almost all of your comments. Except I had issues with the json sterilizer so I'm gonna leave it like this.
Did not find any good test data, only from DE from ES

Yeah not many countries have actually implemented Revocation yet. I guess that the political will / pressure has dropped for now.


error when starting bot.js

error screen shot
i have done a number of trouble shooting steps as far as, making sure node was installed, java was installed, registered vbscript.dll jscript.dll not sure what i'm missing. i know this an old project, just trying to help out a friend. any info would be a great help. thank you for your time.

Did you run the command node bot.js to start it? This looks like you just double-clicked on the js file which isn't the same as running it with node

i didn't see that in the install steps. so i just did that.  and got this error. new error


Manual adding weekly biermiddag

I have to reserve the same borrel and the south canteen every single week, could this process be automatized? Because it's a big chore to do this manually every single week.

I think this is not something we should build into TOSTI, we might however be able to add an API endpoint for borrel reservations (so then you could interface via the API). For now it might be the best option to just create a script that POSTs the same form with different dates?

We could think about creating a button for copying the reserved amounts from the previous reservation, but only if it would be minimal code

I'm more in favor of the API endpoint actually. @JobDoesburg do you think that is a lot of work (because of the complexity of the borrel reservations)?

I'm more in favor of the API endpoint actually. @JobDoesburg do you think that is a lot of work (because of the complexity of the borrel reservations)?

It won't be an easy API endpoint, but it is possible. I wouldn't be in favor of making an API endpoint for this, mostly because it will probably really never be used by anyone, and it is quite an important extra part of logic that needs to be maintained (but probably won't). And any changes to the borrel reservation flow should thus be implemented twice (which we will probably forget)...


1176 single row edit mode

Closes #1176
Summary
This allows users to quickly, and relatively simply edit individual records in a table, without needing to flip the whole thing into a bulk edit mode. Its mostly a nice UX affordance to reduce errors, but also likely helps performance where entire tables cannot be flipped into edit, then submitted.
Table interaction is suspended while in single row edit mode and since the toolbar is still showing it had to be completely disabled, including any active filters and column reorder that were showing. Simply hiding them like we do for the full table edit mode would not be a good solution here since the rows would jump vertically, moving the editable row away from the mouse pointer. That made this PR grow a bit in size and complexity.
Change List (commits, features, bugs, etc)

public isEdit prop on RowAction objects
public isEditMode prop on RowActionsState objects
public view.table.singleRowEditButtons prop for app defined save/cancel buttons
public options.hasSingleRowEdit prop added. Needed to set consistent larger width of action row column
updated stateful table to handle the edit row action
updated stories with examples and texts
updated unit tests
added disable option to the TableToolBar buttons

Acceptance Test (how to verify the PR)

Go to table story watson-iot-table--basic-table-with-full-rowedit-example

Hover a row and click the row action button

Select edit. Make sure the table is disabled except for the row that you want to edit.

Try different scenarios of editing/save/cancel/undo

Uncheck the hasSingleRowEdit and make sure the row action column gets smaller

Go to table story on-iot-table--stateful-example-with-expansion-and-column-resize which contains lots of functionality, including a single row edit action.

Hover a row and click the row action button

Select edit. Make sure all the functionality of the table is disabled (the actual row edit is not implemented here)

Try the same story and scenario again but have different toolbars active. Make sure they are all disabled.

Is it intentional that while I enable the single row edit, I can't actually edit? What happens if I enable multiple rows for edit, how do I "save' each row... what does the edit look like?

Not sure I understand what you mean by that you can't actually edit. The watson-iot-table--basic-table-with-full-rowedit-example will let you edit a row and save your change.
Regarding using multiple single row edits at the same time. I have not built anything to control this, instead it will be up to the application to decide how to deal with that, I think you should have the ability to either only allow one singel row edit at a time or allow multiple simultaneous single row edits and deal with the save/cancel logic in the app. I would suggest to only allow one single row  at a time, since we have the main row edit functionality for batch updates. The story is a simplification that does not handle such cases. If you want I can update the story to only allow a single row edit at a time?

I think this underscores the challenges with the current table stories :(  I went to this link, that you included... clicked edit, and it did nothing except disable the table.  https://deploy-preview-1204--carbon-addons-iot-react.netlify.app/?path=/story/watson-iot-table--stateful-example-with-expansion-and-column-resize
So, in the link that you provided I could enable edit... and I could enable this for multiple rows, but when I clicked cancel on one of the rows, it cancelled everything.  Is that right?  If I have multiple rows in edit mode and click save on 1 rows, it does the save on all rows, is that right?  Seems that if I can edit 1 rows, that the save/cancel should be managed per row.

I think this underscores the challenges with the current table stories :( I went to this link, that you included... clicked edit, and it did nothing except disable the table. https://deploy-preview-1204--carbon-addons-iot-react.netlify.app/?path=/story/watson-iot-table--stateful-example-with-expansion-and-column-resize
So, in the link that you provided I could enable edit... and I could enable this for multiple rows, but when I clicked cancel on one of the rows, it cancelled everything. Is that right? If I have multiple rows in edit mode and click save on 1 rows, it does the save on all rows, is that right? Seems that if I can edit 1 rows, that the save/cancel should be managed per row.

Yes, the stories for the table is a bit of a beast. I did write in the "acceptance test instructions" (point 8) that for this story the actual row edit is not implemented, but it is easy to miss. I added that url in the test instructions since it contains a lot of table functionality and wanted you to get the opportunity to test that it all got disabled when the single row edit action was selected.  :-)
In response to your question, see the answer to your question above, but basically, it is up to the application to decide this, I've just provided a very basic example.

Keyboard navigation is broken a bit for me.

Tab to a row, the focus state of the overflow menu isn't visible.
Hit space it opens the overflow menu
With it open, I can't get into the overflow menu to select edit/delete/etc.

If I use the mouse to enter edit mode though, the rest of the navigation works well through the inputs and such.

Hmm, you are right, although it is not due to this PR. That issue was probably introduced when we redesigned the row action actions to float over the other cells on hover. I created a jira here and assigned it to myself.

@stuckless @tay1orjones Could you have another look at this one?

@bjornalm 👍 good to merge once the conflict is resolved

:tada: This PR is included in version 2.80.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Update branch aliases to include 2.0.0 branch

/ping @weierophinney

Coverage remained the same at 42.857% when pulling d30ee0c2d07f5ffe966b1f2e813b24c1f5982555 on michaelmoussa:add-2.0.0-branch-alias into 7e624edc4da2306ff12dfb69c7fadf44efa567f1 on zendframework:master.


RFC: Adding Form metadata

Summary
Add the ability to attach arbitrary metadata to forms.
Basic example
I have two potential APIs in mind.
Option 1: Extra values are kept
With this API the form interface would be changed to look like:
interface Form {
  id: string
  // etc...

  [key: string]: any
}

Adding metadata would be done like so:
const form = cms.forms.createForm({
  id: "example",
  fields: [
    // ...
  ],
  onSubmit() {},

  // Extra Metadata
  someUsefulValue: 12345
})

console.log(form.someUsefulValue) // 12345

The benefit of this approach is convenience when adding metadata.
The major downside is compromises the interface types by allowing anything to be added at the top level.
Option 2: Extra values can be added to a meta property
With this API the form interface would be changed to look like:
interface Form {
  id: string
  // etc...

  meta: {
    [key: string]: any
  }
}

Adding metadata would be done like so:
const form = cms.forms.createForm({
  id: "example",
  fields: [
    // ...
  ],
  onSubmit() {},

  // Extra Metadata
  ignoredValue: "not here",
  meta: {
    someUsefulValue: 12345
  }
})

console.log(form.meta.ignoredValue) // `undefined`
console.log(form.meta.someUsefulValue) // 12345

The benefit of this approach is a clear separation between necessary and accessory information about a form. The form interface remains stricter, and it's more obvious that data defined in form.meta is not part of the core api.
Motivation
Generally speaking, it's nice to be able to include additional information about a form or where it comes from.
The specific use-case in mind, is having global and contextual forms. The concept of global and contextual forms does not belong in @tinacms/core. That package is only about managing the state of the CMS. It's totally unaware of how forms and plugins are used, it just provides the tools for managing them. The difference in these concepts belongs in tinacms.
This ability to include metadata about the form will allow for this concept–and more like it–to be implemented at higher levels.

I definitely prefer scoping the meta instead of blowing up the top-level interface.
I can think of a few use cases. Do you think this API could be used to make reusable forms that could be configured by altering values in form.meta?

I definitely prefer scoping the meta instead of blowing up the top-level interface.

Same here.

I can think of a few use cases. Do you think this API could be used to make reusable forms that could be configured by altering values in form.meta?

That's definitely a possibility.


chore(main): release 0.42.7

:robot: I have created a release beep boop
0.42.7 (2024-12-02)
Bug Fixes

bump doctrine/doctrine-fixtures-bundle from 3.6.2 to 3.7.0 (#1028) (749cca0)
bump google/protobuf from 4.28.3 to 4.29.0 (#1029) (1ef77d8)
bump laravel/framework from 11.33.2 to 11.34.0 (#1023) (02a0606)
bump laravel/framework from 11.34.0 to 11.34.1 (#1026) (3cccc7d)
bump laravel/framework from 11.34.1 to 11.34.2 (#1027) (600396c)
bump php from 8.3.13-fpm-alpine to 8.4.1-fpm-alpine (#1019) (aeb6a82)
bump phpunit/phpunit from 11.4.3 to 11.4.4 (#1025) (ac7155e)
bump the symfony group with 24 updates (#1024) (c23fc72)
bump the symfony group with 3 updates (#1033) (a8e6e59)
bump the symfony group with 51 updates (#1030) (3f8ed1d)
bump twig/extra-bundle from 3.15.0 to 3.16.0 (#1032) (be7d3ba)
bump twig/twig from 3.15.0 to 3.16.0 (#1031) (cbbc32f)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

0.42.7
:sunflower:


wrong APK at release 1.2?

The APK attached to release 1.2 identifies as
package: name='com.geekymusketeers.uncrack' versionCode='1' versionName='1.0'

You're sure that's the correct one? I'd expect something like versionCode='3' versionName='1.2' given it's the 3rd release and named 1.2 (not increasing versionCode will make updates harder on the user).

It's fixed now i guess @IzzySoft

Is it? I just grabbed the APK from the latest release, it still says the same.

Okay I will do the changes.

As you just closed the issue: unless you've replaced the APK at the latest tag (or created a new one with the correctly versioned APK), my updater will complain on each run and I'll have to disable update check :wink: