handle account id in the ping request

receive aws account id of the host from deploy agent to teletraan agent server and record it in hosts table.

Updated devapp’s teletraan agent config to make sure it points to https://teletraan-dev1-agent.pinadmin.com/ and on the devapp it is running this related PR https://github.com/pinterest/teletraan/pull/1229;
Deployed the current PR to teletraan agent dev1.
Tested on the devapp via this command:
yaqinli@dev-yaqinli:~/code/teletraan/deploy-agent$ sudo bazel run deployd:deploy-agent -- --use-facter -f /etc/deployagent.conf
INFO: Analyzed target //deployd:deploy-agent (0 packages loaded, 0 targets configured).
INFO: Found 1 target...
Target //deployd:deploy-agent up-to-date:
  bazel-bin/deployd/deploy-agent
INFO: Elapsed time: 0.049s, Critical Path: 0.00s
INFO: 1 process: 1 internal.
INFO: Build completed successfully, 1 total action
INFO: Running command line: bazel-bin/deployd/deploy-agent --use-facter -f /etc/deployagent.conf
yaqinli@dev-yaqinli:~/code/teletraan/deploy-agent$

According to the log, it looks working well:
2023-08-11 00:45:51,039 deployd:120 INFO The deploy agent is starting.
2023-08-11 00:45:51,039 deployd.common.executor:54 DEBUG Executor configs have been updated: PING_INTERVAL=60, TIME_OUT=1800, MAX_RETRY=3
2023-08-11 00:45:51,039 deployd.client.client:55 INFO Use facter to get host info
2023-08-11 00:45:51,039 deployd.common.utils:207 INFO Fetching {'hostname', 'deploy_service_combined', 'ec2_local_ipv4', 'ec2_instance_id'} keys from facter
2023-08-11 00:45:52,753 deployd.common.utils:207 INFO Fetching {'ec2_placement_availability_zone', 'ec2_metadata.identity-credentials.ec2.info', 'deploy_service_stage_type', 'ec2_tags'} keys from facter
2023-08-11 00:45:54,456 deployd.client.client:190 INFO Host information is loaded. Host name: dev-yaqinli, IP: <IP_ADDRESS>, host id: i-0dd4b6ce5062c36f0, agent_version=1.2.40-pinterest-1.0.2, autoscaling_group: None, availability_zone: us-east-1d, stage_type: None, group: ['singer-prod-sidecar', 'envoy-devapp', 'tcollector-prod-sidecar', 'mcrouter-devapp', 'mcrouter-prod-sidecar', 'metrics-agent-prod-sidecar', 'zk_update_monitor-prod-sidecar'], account id:<PHONE_NUMBER>90
2023-08-11 00:45:54,459 urllib3.connectionpool:1018 DEBUG Starting new HTTPS connection (1): teletraan-dev1-agent.pinadmin.com:443
2023-08-11 00:45:54,533 urllib3.connectionpool:482 DEBUG https://teletraan-dev1-agent.pinadmin.com:443 "POST /v1/system/ping HTTP/1.1" 200 294
2023-08-11 00:45:54,534 deployd.client.client:225 DEBUG PingRequest(hostId=i-0dd4b6ce5062c36f0, hostName=dev-yaqinli, hostIp=<IP_ADDRESS>, agentVersion=1.2.40-pinterest-1.0.2, autoscalingGroup=None, availabilityZone=us-east-1d, stageType=None, groups=['singer-prod-sidecar', 'envoy-devapp', 'tcollector-prod-sidecar', 'mcrouter-devapp', 'mcrouter-prod-sidecar', 'metrics-agent-prod-sidecar', 'zk_update_monitor-prod-sidecar'], accountId=998131032990, reports=PingReport(deployId=yo63b11MQ_6Yj8sz5cc8zw, envId=nS2GIXkgQnK4pR9qG5ZpFg, deployStage=SERVING_BUILD, status=SUCCEEDED, errorCode=0), errorMessage=None, failCount=0, extraInfo=None, deployAlias=None),PingReport(deployId=KIWVKQpJSDu5_CX57jTuWg, envId=inbDfs6KQICpRRfuKQw_bQ, deployStage=SERVING_BUILD, status=SUCCEEDED, errorCode=0), errorMessage=None, failCount=0, extraInfo=None, deployAlias=None),PingReport(deployId=3zZuGjXbReqgsgwkAFcQPQ, envId=2XwshUOHR36DGEAH4PzBwg, deployStage=SERVING_BUILD, status=SUCCEEDED, errorCode=0), errorMessage=None, failCount=0, extraInfo=None, deployAlias=None),PingReport(deployId=sRyuuWtpRKmbbKH56zh49Q, envId=kwUx6aHWQo6R174lT-eawQ, deployStage=SERVING_BUILD, status=SUCCEEDED, errorCode=0), errorMessage=None, failCount=0, extraInfo=None, deployAlias=None),PingReport(deployId=4wjThV9dT1SG6dN3vjsevA, envId=typrFRIFR6-lDyaiNjAk9w, deployStage=SERVING_BUILD, status=SUCCEEDED, errorCode=0), errorMessage=None, failCount=0, extraInfo=None, deployAlias=None),PingReport(deployId=3jC7i1eNSl6959Nk7bNJOQ, envId=gu2DEmL4Tv2XOqDKFc7Axw, deployStage=SERVING_BUILD, status=SUCCEEDED, errorCode=0), errorMessage=None, failCount=0, extraInfo=None, deployAlias=None),PingReport(deployId=2opBs7wjQqmWJGdbBqlY5w, envId=7ib3xSHSR3unnLdN-ViGxw, deployStage=SERVING_BUILD, status=SUCCEEDED, errorCode=0), errorMessage=None, failCount=0, extraInfo=None, deployAlias=None),PingReport(deployId=wK80YoJTRaytsW6Ufyczkw, envId=pZwvW9faQTW7vD19ER72Gg, deployStage=SERVING_BUILD, status=SUCCEEDED, errorCode=0), errorMessage=None, failCount=0, extraInfo=None, deployAlias=None),PingReport(deployId=XgWTORkURUe0HXpkk7dmSw, envId=99xVHd7bSr608HSHqrCGbA, deployStage=SERVING_BUILD, status=SUCCEEDED, errorCode=0), errorMessage=None, failCount=0, extraInfo=None, deployAlias=None),PingReport(deployId=HWT8uaMbTNebUVUhFyGHkw, envId=tLWOA1CsQ4W2Nu_kMFyYVA, deployStage=SERVING_BUILD, status=SUCCEEDED, errorCode=0), errorMessage=None, failCount=0, extraInfo=None, deployAlias=None)) -> PingResponse(opCode=DELETE, deployGoal=DeployGoal(deployId=3zZuGjXbReqgsgwkAFcQPQ, envId=2XwshUOHR36DGEAH4PzBwg, envName=None, stageName=None, deployStage=SERVING_BUILD, build=None, deployAlias=None, agentConfig=None,scriptVariables=None, firstDeploy=False, isDocker=None))

And in the database, I see the account_id is recorded:
mysql> select * from hosts where host_name="dev-yaqinli";
+-------------+------------------------------------------------------+--------------+---------------+---------------+--------+---------------------+------------+--------------+
| host_name   | group_name                                           | ip           | create_date   | last_update   | state  | host_id             | can_retire | account_id   |
+-------------+------------------------------------------------------+--------------+---------------+---------------+--------+---------------------+------------+--------------+
| dev-yaqinli | envoy-devapp                                         | <IP_ADDRESS> |<PHONE_NUMBER>478 |<PHONE_NUMBER>478 | ACTIVE | i-0dd4b6ce5062c36f0 |          0 |<PHONE_NUMBER>90 |
| dev-yaqinli | envoy-devapp-production-us-east-1d                   | <IP_ADDRESS> |<PHONE_NUMBER>478 |<PHONE_NUMBER>478 | ACTIVE | i-0dd4b6ce5062c36f0 |          0 |<PHONE_NUMBER>90 |
| dev-yaqinli | mcrouter-devapp                                      | <IP_ADDRESS> |<PHONE_NUMBER>478 |<PHONE_NUMBER>478 | ACTIVE | i-0dd4b6ce5062c36f0 |          0 |<PHONE_NUMBER>90 |
| dev-yaqinli | mcrouter-devapp-production-us-east-1d                | <IP_ADDRESS> |<PHONE_NUMBER>478 |<PHONE_NUMBER>478 | ACTIVE | i-0dd4b6ce5062c36f0 |          0 |<PHONE_NUMBER>90 |
| dev-yaqinli | mcrouter-prod-sidecar                                | <IP_ADDRESS> |<PHONE_NUMBER>478 |<PHONE_NUMBER>478 | ACTIVE | i-0dd4b6ce5062c36f0 |          0 |<PHONE_NUMBER>90 |
| dev-yaqinli | mcrouter-prod-sidecar-production-us-east-1d          | <IP_ADDRESS> |<PHONE_NUMBER>478 |<PHONE_NUMBER>478 | ACTIVE | i-0dd4b6ce5062c36f0 |          0 |<PHONE_NUMBER>90 |
| dev-yaqinli | metrics-agent-prod-sidecar                           | <IP_ADDRESS> |<PHONE_NUMBER>478 |<PHONE_NUMBER>478 | ACTIVE | i-0dd4b6ce5062c36f0 |          0 |<PHONE_NUMBER>90 |
| dev-yaqinli | metrics-agent-prod-sidecar-production-us-east-1d     | <IP_ADDRESS> |<PHONE_NUMBER>478 |<PHONE_NUMBER>478 | ACTIVE | i-0dd4b6ce5062c36f0 |          0 |<PHONE_NUMBER>90 |
| dev-yaqinli | singer-prod-sidecar                                  | <IP_ADDRESS> |<PHONE_NUMBER>478 |<PHONE_NUMBER>478 | ACTIVE | i-0dd4b6ce5062c36f0 |          0 |<PHONE_NUMBER>90 |
| dev-yaqinli | singer-prod-sidecar-production-us-east-1d            | <IP_ADDRESS> |<PHONE_NUMBER>478 |<PHONE_NUMBER>478 | ACTIVE | i-0dd4b6ce5062c36f0 |          0 |<PHONE_NUMBER>90 |
| dev-yaqinli | tcollector-prod-sidecar                              | <IP_ADDRESS> |<PHONE_NUMBER>478 |<PHONE_NUMBER>478 | ACTIVE | i-0dd4b6ce5062c36f0 |          0 |<PHONE_NUMBER>90 |
| dev-yaqinli | tcollector-prod-sidecar-production-us-east-1d        | <IP_ADDRESS> |<PHONE_NUMBER>478 |<PHONE_NUMBER>478 | ACTIVE | i-0dd4b6ce5062c36f0 |          0 |<PHONE_NUMBER>90 |
| dev-yaqinli | zk_update_monitor-prod-sidecar                       | <IP_ADDRESS> |<PHONE_NUMBER>478 |<PHONE_NUMBER>478 | ACTIVE | i-0dd4b6ce5062c36f0 |          0 |<PHONE_NUMBER>90 |
| dev-yaqinli | zk_update_monitor-prod-sidecar-production-us-east-1d | <IP_ADDRESS> |<PHONE_NUMBER>478 |<PHONE_NUMBER>478 | ACTIVE | i-0dd4b6ce5062c36f0 |          0 |<PHONE_NUMBER>90 |
+-------------+------------------------------------------------------+--------------+---------------+---------------+--------+---------------------+------------+--------------+
14 rows in set (0.00 sec)

mysql>

if we deploy this change with the current version of deploy agent (without account id change in deploy agent), is there an issue?

if we deploy this change with the current version of deploy agent (without account id change in deploy agent), is there an issue?

Let me do a test.

if we deploy this change with the current version of deploy agent (without account id change in deploy agent), is there an issue?

I tested and didn't see any issue.
{"level":"INFO","logger":"com.pinterest.teletraan.resource.Pings","thread":"dw-24 - POST /v1/system/ping","message":"Receive ping request com.pinterest.deployservice.bean.PingRequestBean@346a405b[hostId=i-0dd4b6ce5062c36f0,hostName=dev-yaqinli,hostIp=<IP_ADDRESS>,autoscalingGroup=<null>,availabilityZone=us-east-1d,agentVersion=1.2.40-pinterest-1.0.2,stageType=<null>,groups=[envoy-devapp, zk_update_monitor-prod-sidecar, singer-prod-sidecar, mcrouter-prod-sidecar, tcollector-prod-sidecar, mcrouter-devapp, metrics-agent-prod-sidecar],accountId=<null>,reports=[com.pinterest.deployservice.bean.PingReportBean@31225678[deployId=yo63b11MQ_6Yj8sz5cc8zw,envId=nS2GIXkgQnK4pR9qG5ZpFg,deployStage=SERVING_BUILD,agentStatus=SUCCEEDED,errorCode=0,errorMessage=<null>,failCount=0,extraInfo=<null>,deployAlias=<null>], com.pinterest.deployservice.bean.PingReportBean@37370d22[deployId=s56akdx1RqChXzQi6yodqQ,envId=inbDfs6KQICpRRfuKQw_bQ,deployStage=RESTARTING,agentStatus=UNKNOWN,errorCode=0,errorMessage=<null>,failCount=0,extraInfo=<null>,deployAlias=<null>], com.pinterest.deployservice.bean.PingReportBean@565d4342[deployId=3zZuGjXbReqgsgwkAFcQPQ,envId=2XwshUOHR36DGEAH4PzBwg,deployStage=SERVING_BUILD,agentStatus=SUCCEEDED,errorCode=0,errorMessage=<null>,failCount=0,extraInfo=<null>,deployAlias=<null>], com.pinterest.deployservice.bean.PingReportBean@30d3a94a[deployId=sRyuuWtpRKmbbKH56zh49Q,envId=kwUx6aHWQo6R174lT-eawQ,deployStage=SERVING_BUILD,agentStatus=SUCCEEDED,errorCode=0,errorMessage=<null>,failCount=0,extraInfo=<null>,deployAlias=<null>], com.pinterest.deployservice.bean.PingReportBean@13e1a8be[deployId=4wjThV9dT1SG6dN3vjsevA,envId=typrFRIFR6-lDyaiNjAk9w,deployStage=SERVING_BUILD,agentStatus=SUCCEEDED,errorCode=0,errorMessage=<null>,failCount=0,extraInfo=<null>,deployAlias=<null>], com.pinterest.deployservice.bean.PingReportBean@1cb0f9fd[deployId=3jC7i1eNSl6959Nk7bNJOQ,envId=gu2DEmL4Tv2XOqDKFc7Axw,deployStage=SERVING_BUILD,agentStatus=SUCCEEDED,errorCode=0,errorMessage=<null>,failCount=0,extraInfo=<null>,deployAlias=<null>], com.pinterest.deployservice.bean.PingReportBean@20cbfe7a[deployId=2opBs7wjQqmWJGdbBqlY5w,envId=7ib3xSHSR3unnLdN-ViGxw,deployStage=SERVING_BUILD,agentStatus=SUCCEEDED,errorCode=0,errorMessage=<null>,failCount=0,extraInfo=<null>,deployAlias=<null>], com.pinterest.deployservice.bean.PingReportBean@dff8ad0[deployId=wK80YoJTRaytsW6Ufyczkw,envId=pZwvW9faQTW7vD19ER72Gg,deployStage=SERVING_BUILD,agentStatus=SUCCEEDED,errorCode=0,errorMessage=<null>,failCount=0,extraInfo=<null>,deployAlias=<null>], com.pinterest.deployservice.bean.PingReportBean@13c57789[deployId=XgWTORkURUe0HXpkk7dmSw,envId=99xVHd7bSr608HSHqrCGbA,deployStage=SERVING_BUILD,agentStatus=SUCCEEDED,errorCode=0,errorMessage=<null>,failCount=0,extraInfo=<null>,deployAlias=<null>], com.pinterest.deployservice.bean.PingReportBean@8a10b1d[deployId=HWT8uaMbTNebUVUhFyGHkw,envId=tLWOA1CsQ4W2Nu_kMFyYVA,deployStage=SERVING_BUILD,agentStatus=SUCCEEDED,errorCode=0,errorMessage=<null>,failCount=0,extraInfo=<null>,deployAlias=<null>]]]","timestamp":"2023-08-11T19:15:30.602+0000"}
{"level":"INFO","logger":"com.pinterest.deployservice.handler.PingHandler","thread":"dw-24 - POST /v1/system/ping","message":"Updating host dev-yaqinli with sharded group envoy-devapp-production-us-east-1d","timestamp":"2023-08-11T19:15:30.602+0000"}
{"level":"INFO","logger":"com.pinterest.deployservice.handler.PingHandler","thread":"dw-24 - POST /v1/system/ping","message":"Updating host dev-yaqinli with sharded group zk_update_monitor-prod-sidecar-production-us-east-1d","timestamp":"2023-08-11T19:15:30.602+0000"}
{"level":"INFO","logger":"com.pinterest.deployservice.handler.PingHandler","thread":"dw-24 - POST /v1/system/ping","message":"Updating host dev-yaqinli with sharded group singer-prod-sidecar-production-us-east-1d","timestamp":"2023-08-11T19:15:30.602+0000"}
{"level":"INFO","logger":"com.pinterest.deployservice.handler.PingHandler","thread":"dw-24 - POST /v1/system/ping","message":"Updating host dev-yaqinli with sharded group mcrouter-prod-sidecar-production-us-east-1d","timestamp":"2023-08-11T19:15:30.602+0000"}
{"level":"INFO","logger":"com.pinterest.deployservice.handler.PingHandler","thread":"dw-24 - POST /v1/system/ping","message":"Updating host dev-yaqinli with sharded group tcollector-prod-sidecar-production-us-east-1d","timestamp":"2023-08-11T19:15:30.602+0000"}
{"level":"INFO","logger":"com.pinterest.deployservice.handler.PingHandler","thread":"dw-24 - POST /v1/system/ping","message":"Updating host dev-yaqinli with sharded group mcrouter-devapp-production-us-east-1d","timestamp":"2023-08-11T19:15:30.602+0000"}
{"level":"INFO","logger":"com.pinterest.deployservice.handler.PingHandler","thread":"dw-24 - POST /v1/system/ping","message":"Updating host dev-yaqinli with sharded group metrics-agent-prod-sidecar-production-us-east-1d","timestamp":"2023-08-11T19:15:30.602+0000"}
{"level":"DEBUG","logger":"com.pinterest.deployservice.handler.PingHandler","thread":"dw-24 - POST /v1/system/ping","message":"Found the following envs [] associated with host dev-yaqinli and group [zk_update_monitor-prod-sidecar, mcrouter-prod-sidecar, envoy-devapp-production-us-east-1d, singer-prod-sidecar-production-us-east-1d, tcollector-prod-sidecar, mcrouter-devapp-production-us-east-1d, mcrouter-prod-sidecar-production-us-east-1d, envoy-devapp, tcollector-prod-sidecar-production-us-east-1d, singer-prod-sidecar, mcrouter-devapp, metrics-agent-prod-sidecar, metrics-agent-prod-sidecar-production-us-east-1d, zk_update_monitor-prod-sidecar-production-us-east-1d].","timestamp":"2023-08-11T19:15:30.621+0000"}
{"level":"DEBUG","logger":"com.pinterest.deployservice.handler.GoalAnalyst","thread":"dw-24 - POST /v1/system/ping","message":"GoalAnalyst process env 2XwshUOHR36DGEAH4PzBwg, report = com.pinterest.deployservice.bean.PingReportBean@565d4342[deployId=3zZuGjXbReqgsgwkAFcQPQ,envId=2XwshUOHR36DGEAH4PzBwg,deployStage=SERVING_BUILD,agentStatus=SUCCEEDED,errorCode=0,errorMessage=<null>,failCount=0,extraInfo=<null>,deployAlias=<null>], env = null and agent = com.pinterest.deployservice.bean.AgentBean@7533f0c1[host_id=i-0dd4b6ce5062c36f0,host_name=dev-yaqinli,env_id=2XwshUOHR36DGEAH4PzBwg,deploy_id=3zZuGjXbReqgsgwkAFcQPQ,deploy_stage=SERVING_BUILD,state=DELETE,status=SUCCEEDED,start_date=1691714754494,last_update=1691781282844,last_operator=system,last_err_no=0,fail_count=0,first_deploy=false,first_deploy_time=1691714754494,stage_start_date=1691781282844].","timestamp":"2023-08-11T19:15:30.657+0000"}
{"level":"DEBUG","logger":"com.pinterest.deployservice.handler.GoalAnalyst","thread":"dw-24 - POST /v1/system/ping","message":"Report status is SUCCEEDED, propose new agent state as NORMAL ","timestamp":"2023-08-11T19:15:30.657+0000"}
{"level":"INFO","logger":"com.pinterest.deployservice.handler.GoalAnalyst","thread":"dw-24 - POST /v1/system/ping","message":"Agent record for env_id 2XwshUOHR36DGEAH4PzBwg, deploy_id 3zZuGjXbReqgsgwkAFcQPQ on host i-0dd4b6ce5062c36f0 needs update","timestamp":"2023-08-11T19:15:30.657+0000"}
{"level":"DEBUG","logger":"com.pinterest.deployservice.handler.GoalAnalyst","thread":"dw-24 - POST /v1/system/ping","message":"GoalAnalyst case 3.1 - add an uninstall candidate to instruct host dev-yaqinli to remove the retired env 2XwshUOHR36DGEAH4PzBwg","timestamp":"2023-08-11T19:15:30.657+0000"}
{"level":"DEBUG","logger":"com.pinterest.deployservice.handler.GoalAnalyst","thread":"dw-24 - POST /v1/system/ping","message":"GoalAnalyst process env gu2DEmL4Tv2XOqDKFc7Axw, report = com.pinterest.deployservice.bean.PingReportBean@1cb0f9fd[deployId=3jC7i1eNSl6959Nk7bNJOQ,envId=gu2DEmL4Tv2XOqDKFc7Axw,deployStage=SERVING_BUILD,agentStatus=SUCCEEDED,errorCode=0,errorMessage=<null>,failCount=0,extraInfo=<null>,deployAlias=<null>], env = null and agent = com.pinterest.deployservice.bean.AgentBean@3d10058e[host_id=i-0dd4b6ce5062c36f0,host_name=dev-yaqinli,env_id=gu2DEmL4Tv2XOqDKFc7Axw,deploy_id=3jC7i1eNSl6959Nk7bNJOQ,deploy_stage=SERVING_BUILD,state=DELETE,status=SUCCEEDED,start_date=1691714754494,last_update=1691781282844,last_operator=system,last_err_no=0,fail_count=0,first_deploy=false,first_deploy_time=1691714754494,stage_start_date=1691781282844].","timestamp":"2023-08-11T19:15:30.658+0000"}
{"level":"DEBUG","logger":"com.pinterest.deployservice.handler.GoalAnalyst","thread":"dw-24 - POST /v1/system/ping","message":"Report status is SUCCEEDED, propose new agent state as NORMAL ","timestamp":"2023-08-11T19:15:30.658+0000"}
{"level":"INFO","logger":"com.pinterest.deployservice.handler.GoalAnalyst","thread":"dw-24 - POST /v1/system/ping","message":"Agent record for env_id gu2DEmL4Tv2XOqDKFc7Axw, deploy_id 3jC7i1eNSl6959Nk7bNJOQ on host i-0dd4b6ce5062c36f0 needs update","timestamp":"2023-08-11T19:15:30.658+0000"}
{"level":"DEBUG","logger":"com.pinterest.deployservice.handler.GoalAnalyst","thread":"dw-24 - POST /v1/system/ping","message":"GoalAnalyst case 3.1 - add an uninstall candidate to instruct host dev-yaqinli to remove the retired env gu2DEmL4Tv2XOqDKFc7Axw","timestamp":"2023-08-11T19:15:30.658+0000"}
{"level":"DEBUG","logger":"com.pinterest.deployservice.handler.GoalAnalyst","thread":"dw-24 - POST /v1/system/ping","message":"GoalAnalyst process env nS2GIXkgQnK4pR9qG5ZpFg, report = com.pinterest.deployservice.bean.PingReportBean@31225678[deployId=yo63b11MQ_6Yj8sz5cc8zw,envId=nS2GIXkgQnK4pR9qG5ZpFg,deployStage=SERVING_BUILD,agentStatus=SUCCEEDED,errorCode=0,errorMessage=<null>,failCount=0,extraInfo=<null>,deployAlias=<null>], env = null and agent = com.pinterest.deployservice.bean.AgentBean@33aa1636[host_id=i-0dd4b6ce5062c36f0,host_name=dev-yaqinli,env_id=nS2GIXkgQnK4pR9qG5ZpFg,deploy_id=yo63b11MQ_6Yj8sz5cc8zw,deploy_stage=SERVING_BUILD,state=DELETE,status=SUCCEEDED,start_date=1691714754494,last_update=1691781282844,last_operator=system,last_err_no=0,fail_count=0,first_deploy=false,first_deploy_time=1691714754494,stage_start_date=1691781282844].","timestamp":"2023-08-11T19:15:30.658+0000"}
{"level":"DEBUG","logger":"com.pinterest.deployservice.handler.GoalAnalyst","thread":"dw-24 - POST /v1/system/ping","message":"Report status is SUCCEEDED, propose new agent state as NORMAL ","timestamp":"2023-08-11T19:15:30.658+0000"}
{"level":"INFO","logger":"com.pinterest.deployservice.handler.GoalAnalyst","thread":"dw-24 - POST /v1/system/ping","message":"Agent record for env_id nS2GIXkgQnK4pR9qG5ZpFg, deploy_id yo63b11MQ_6Yj8sz5cc8zw on host i-0dd4b6ce5062c36f0 needs update","timestamp":"2023-08-11T19:15:30.658+0000"}
......
{"level":"DEBUG","logger":"com.pinterest.deployservice.handler.GoalAnalyst","thread":"dw-18 - POST /v1/system/ping","message":"GoalAnalyst process env inbDfs6KQICpRRfuKQw_bQ, report = com.pinterest.deployservice.bean.PingReportBean@75136f13[deployId=s56akdx1RqChXzQi6yodqQ,envId=inbDfs6KQICpRRfuKQw_bQ,deployStage=RESTARTING,agentStatus=UNKNOWN,errorCode=0,errorMessage=<null>,failCount=0,extraInfo=<null>,deployAlias=<null>], env = null and agent = com.pinterest.deployservice.bean.AgentBean@778ba10a[host_id=i-0dd4b6ce5062c36f0,host_name=dev-yaqinli,env_id=inbDfs6KQICpRRfuKQw_bQ,deploy_id=s56akdx1RqChXzQi6yodqQ,deploy_stage=RESTARTING,state=DELETE,status=UNKNOWN,start_date=1691714754494,last_update=1691781506434,last_operator=system,last_err_no=0,fail_count=0,first_deploy=false,first_deploy_time=1691714754494,stage_start_date=1691781506434].","timestamp":"2023-08-11T19:19:24.267+0000"}
{"level":"DEBUG","logger":"com.pinterest.deployservice.handler.GoalAnalyst","thread":"dw-18 - POST /v1/system/ping","message":"Report status is UNKNOWN, reuse the old agent state DELETE ","timestamp":"2023-08-11T19:19:24.267+0000"}
{"level":"DEBUG","logger":"com.pinterest.deployservice.handler.GoalAnalyst","thread":"dw-18 - POST /v1/system/ping","message":"Skip updating agent record for env_id inbDfs6KQICpRRfuKQw_bQ, deploy_id s56akdx1RqChXzQi6yodqQ on host i-0dd4b6ce5062c36f0","timestamp":"2023-08-11T19:19:24.267+0000"}
{"level":"DEBUG","logger":"com.pinterest.deployservice.handler.GoalAnalyst","thread":"dw-18 - POST /v1/system/ping","message":"GoalAnalyst case 3.1 - add an uninstall candidate to instruct host dev-yaqinli to remove the retired env inbDfs6KQICpRRfuKQw_bQ","timestamp":"2023-08-11T19:19:24.267+0000"}
{"level":"DEBUG","logger":"com.pinterest.deployservice.handler.PingHandler","thread":"dw-18 - POST /v1/system/ping","message":"Update 10 agent records for host dev-yaqinli.","timestamp":"2023-08-11T19:19:24.267+0000"}
{"level":"DEBUG","logger":"com.pinterest.deployservice.handler.PingHandler","thread":"dw-18 - POST /v1/system/ping","message":"Update agent beans with the following: [com.pinterest.deployservice.bean.AgentBean@16ed0eb5[host_id=i-0dd4b6ce5062c36f0,host_name=dev-yaqinli,env_id=2XwshUOHR36DGEAH4PzBwg,deploy_id=3zZuGjXbReqgsgwkAFcQPQ,deploy_stage=SERVING_BUILD,state=DELETE,status=SUCCEEDED,start_date=1691714754494,last_update=1691781564266,last_operator=system,last_err_no=0,fail_count=0,first_deploy=false,first_deploy_time=1691781564266,stage_start_date=1691781564266], com.pinterest.deployservice.bean.AgentBean@8524061[host_id=i-0dd4b6ce5062c36f0,host_name=dev-yaqinli,env_id=gu2DEmL4Tv2XOqDKFc7Axw,deploy_id=3jC7i1eNSl6959Nk7bNJOQ,deploy_stage=SERVING_BUILD,state=DELETE,status=SUCCEEDED,start_date=1691714754494,last_update=1691781564267,last_operator=system,last_err_no=0,fail_count=0,first_deploy=false,first_deploy_time=1691781564267,stage_start_date=1691781564267], com.pinterest.deployservice.bean.AgentBean@6ea6ee6e[host_id=i-0dd4b6ce5062c36f0,host_name=dev-yaqinli,env_id=nS2GIXkgQnK4pR9qG5ZpFg,deploy_id=yo63b11MQ_6Yj8sz5cc8zw,deploy_stage=SERVING_BUILD,state=DELETE,status=SUCCEEDED,start_date=1691714754494,last_update=1691781564267,last_operator=system,last_err_no=0,fail_count=0,first_deploy=false,first_deploy_time=1691781564267,stage_start_date=1691781564267], com.pinterest.deployservice.bean.AgentBean@448f8141[host_id=i-0dd4b6ce5062c36f0,host_name=dev-yaqinli,env_id=pZwvW9faQTW7vD19ER72Gg,deploy_id=wK80YoJTRaytsW6Ufyczkw,deploy_stage=SERVING_BUILD,state=DELETE,status=SUCCEEDED,start_date=1691714754494,last_update=1691781564267,last_operator=system,last_err_no=0,fail_count=0,first_deploy=false,first_deploy_time=1691781564267,stage_start_date=1691781564267], com.pinterest.deployservice.bean.AgentBean@3a69b7c3[host_id=i-0dd4b6ce5062c36f0,host_name=dev-yaqinli,env_id=typrFRIFR6-lDyaiNjAk9w,deploy_id=4wjThV9dT1SG6dN3vjsevA,deploy_stage=SERVING_BUILD,state=DELETE,status=SUCCEEDED,start_date=1691714754494,last_update=1691781564267,last_operator=system,last_err_no=0,fail_count=0,first_deploy=false,first_deploy_time=1691781564267,stage_start_date=1691781564267], com.pinterest.deployservice.bean.AgentBean@20a2a9a7[host_id=i-0dd4b6ce5062c36f0,host_name=dev-yaqinli,env_id=7ib3xSHSR3unnLdN-ViGxw,deploy_id=2opBs7wjQqmWJGdbBqlY5w,deploy_stage=SERVING_BUILD,state=DELETE,status=SUCCEEDED,start_date=1691714754494,last_update=1691781564267,last_operator=system,last_err_no=0,fail_count=0,first_deploy=false,first_deploy_time=1691781564267,stage_start_date=1691781564267], com.pinterest.deployservice.bean.AgentBean@79aef643[host_id=i-0dd4b6ce5062c36f0,host_name=dev-yaqinli,env_id=99xVHd7bSr608HSHqrCGbA,deploy_id=XgWTORkURUe0HXpkk7dmSw,deploy_stage=SERVING_BUILD,state=DELETE,status=SUCCEEDED,start_date=1691714754494,last_update=1691781564267,last_operator=system,last_err_no=0,fail_count=0,first_deploy=false,first_deploy_time=1691781564267,stage_start_date=1691781564267], com.pinterest.deployservice.bean.AgentBean@4113f5be[host_id=i-0dd4b6ce5062c36f0,host_name=dev-yaqinli,env_id=kwUx6aHWQo6R174lT-eawQ,deploy_id=sRyuuWtpRKmbbKH56zh49Q,deploy_stage=SERVING_BUILD,state=DELETE,status=SUCCEEDED,start_date=1691714754494,last_update=1691781564267,last_operator=system,last_err_no=0,fail_count=0,first_deploy=false,first_deploy_time=1691781564267,stage_start_date=1691781564267], com.pinterest.deployservice.bean.AgentBean@36b385f0[host_id=i-0dd4b6ce5062c36f0,host_name=dev-yaqinli,env_id=tLWOA1CsQ4W2Nu_kMFyYVA,deploy_id=HWT8uaMbTNebUVUhFyGHkw,deploy_stage=SERVING_BUILD,state=DELETE,status=SUCCEEDED,start_date=1691714754494,last_update=1691781564267,last_operator=system,last_err_no=0,fail_count=0,first_deploy=false,first_deploy_time=1691781564267,stage_start_date=1691781564267], com.pinterest.deployservice.bean.AgentBean@3e9fd10[host_id=i-0dd4b6ce5062c36f0,host_name=dev-yaqinli,env_id=inbDfs6KQICpRRfuKQw_bQ,deploy_id=s56akdx1RqChXzQi6yodqQ,deploy_stage=RESTARTING,state=DELETE,status=UNKNOWN,start_date=1691714754494,last_update=1691781564267,last_operator=system,last_err_no=0,fail_count=0,first_deploy=false,first_deploy_time=<null>,stage_start_date=1691781564267]]","timestamp":"2023-08-11T19:19:24.267+0000"}
{"level":"INFO","logger":"com.pinterest.deployservice.handler.PingHandler","thread":"dw-18 - POST /v1/system/ping","message":"Return uninstall response com.pinterest.deployservice.bean.PingResponseBean@62023c1b[opCode=DELETE,deployGoal=com.pinterest.deployservice.bean.DeployGoalBean@5bc5c76d[deployId=3zZuGjXbReqgsgwkAFcQPQ,deployType=<null>,envId=2XwshUOHR36DGEAH4PzBwg,envName=<null>,stageName=<null>,deployStage=SERVING_BUILD,build=<null>,deployAlias=<null>,agentConfigs=<null>,scriptVariables=<null>,firstDeploy=false,isDocker=<null>]] for host dev-yaqinli.","timestamp":"2023-08-11T19:19:24.304+0000"}

if we deploy this change with the current version of deploy agent (without account id change in deploy agent), is there an issue?

The above log is on agent server side.
Here is the log on deploy agent side:
2023-08-11 19:12:28,768 deployd:120 INFO The deploy agent is starting.
2023-08-11 19:12:28,768 deployd.common.executor:54 DEBUG Executor configs have been updated: PING_INTERVAL=60, TIME_OUT=1800, MAX_RETRY=3
2023-08-11 19:12:28,768 deployd.client.client:53 INFO Use facter to get host info
2023-08-11 19:12:28,768 deployd.common.utils:207 INFO Fetching {'ec2_local_ipv4', 'hostname', 'ec2_instance_id', 'deploy_service_combined'} keys from facter
2023-08-11 19:12:30,430 deployd.common.utils:207 INFO Fetching {'deploy_service_stage_type', 'ec2_tags', 'ec2_placement_availability_zone'} keys from facter
2023-08-11 19:12:32,151 deployd.client.client:177 INFO Host information is loaded. Host name: dev-yaqinli, IP: <IP_ADDRESS>, host id: i-0dd4b6ce5062c36f0, agent_version=1.2.40-pinterest-1.0.2, autoscaling_group: None, availability_zone: us-east-1d, stage_type: None, group: ['singer-prod-sidecar', 'envoy-devapp', 'tcollector-prod-sidecar', 'mcrouter-devapp', 'mcrouter-prod-sidecar', 'metrics-agent-prod-sidecar', 'zk_update_monitor-prod-sidecar']
2023-08-11 19:12:32,155 urllib3.connectionpool:1018 DEBUG Starting new HTTPS connection (1): teletraan-dev1-agent.pinadmin.com:443
2023-08-11 19:12:32,272 urllib3.connectionpool:482 DEBUG https://teletraan-dev1-agent.pinadmin.com:443 "POST /v1/system/ping HTTP/1.1" 200 294
2023-08-11 19:12:32,272 deployd.client.client:211 DEBUG PingRequest(hostId=i-0dd4b6ce5062c36f0, hostName=dev-yaqinli, hostIp=<IP_ADDRESS>, agentVersion=1.2.40-pinterest-1.0.2, autoscalingGroup=None, availabilityZone=us-east-1d, stageType=None, groups=['singer-prod-sidecar', 'envoy-devapp', 'tcollector-prod-sidecar', 'mcrouter-devapp', 'mcrouter-prod-sidecar', 'metrics-agent-prod-sidecar', 'zk_update_monitor-prod-sidecar'], reports=PingReport(deployId=yo63b11MQ_6Yj8sz5cc8zw, envId=nS2GIXkgQnK4pR9qG5ZpFg, deployStage=SERVING_BUILD, status=SUCCEEDED, errorCode=0), errorMessage=None, failCount=0, extraInfo=None, deployAlias=None),PingReport(deployId=s56akdx1RqChXzQi6yodqQ, envId=inbDfs6KQICpRRfuKQw_bQ, deployStage=RESTARTING, status=UNKNOWN, errorCode=0), errorMessage=None, failCount=0, extraInfo=None, deployAlias=None),PingReport(deployId=3zZuGjXbReqgsgwkAFcQPQ, envId=2XwshUOHR36DGEAH4PzBwg, deployStage=SERVING_BUILD, status=SUCCEEDED, errorCode=0), errorMessage=None, failCount=0, extraInfo=None, deployAlias=None),PingReport(deployId=sRyuuWtpRKmbbKH56zh49Q, envId=kwUx6aHWQo6R174lT-eawQ, deployStage=SERVING_BUILD, status=SUCCEEDED, errorCode=0), errorMessage=None, failCount=0, extraInfo=None, deployAlias=None),PingReport(deployId=4wjThV9dT1SG6dN3vjsevA, envId=typrFRIFR6-lDyaiNjAk9w, deployStage=SERVING_BUILD, status=SUCCEEDED, errorCode=0), errorMessage=None, failCount=0, extraInfo=None, deployAlias=None),PingReport(deployId=3jC7i1eNSl6959Nk7bNJOQ, envId=gu2DEmL4Tv2XOqDKFc7Axw, deployStage=SERVING_BUILD, status=SUCCEEDED, errorCode=0), errorMessage=None, failCount=0, extraInfo=None, deployAlias=None),PingReport(deployId=2opBs7wjQqmWJGdbBqlY5w, envId=7ib3xSHSR3unnLdN-ViGxw, deployStage=SERVING_BUILD, status=SUCCEEDED, errorCode=0), errorMessage=None, failCount=0, extraInfo=None, deployAlias=None),PingReport(deployId=wK80YoJTRaytsW6Ufyczkw, envId=pZwvW9faQTW7vD19ER72Gg, deployStage=SERVING_BUILD, status=SUCCEEDED, errorCode=0), errorMessage=None, failCount=0, extraInfo=None, deployAlias=None),PingReport(deployId=XgWTORkURUe0HXpkk7dmSw, envId=99xVHd7bSr608HSHqrCGbA, deployStage=SERVING_BUILD, status=SUCCEEDED, errorCode=0), errorMessage=None, failCount=0, extraInfo=None, deployAlias=None),PingReport(deployId=HWT8uaMbTNebUVUhFyGHkw, envId=tLWOA1CsQ4W2Nu_kMFyYVA, deployStage=SERVING_BUILD, status=SUCCEEDED, errorCode=0), errorMessage=None, failCount=0, extraInfo=None, deployAlias=None)) -> PingResponse(opCode=DELETE, deployGoal=DeployGoal(deployId=3zZuGjXbReqgsgwkAFcQPQ, envId=2XwshUOHR36DGEAH4PzBwg, envName=None, stageName=None, deployStage=SERVING_BUILD, build=None, deployAlias=None, agentConfig=None,scriptVariables=None, firstDeploy=False, isDocker=None))


Problem Renaming Repos

Description
When a repo is renamed it does not appear to be changing both the database and the filesystem correctly.  It appears to work temporarily, but then it's almost like there is a reversion afterward.
If the bug can be replicated, update the estimate to reflect time to fix.

More information:
Hi Jesse! Sorry for bothering you again. But I got error 500 again. This time I uploaded repo from tS, then transferred ownership to WA_Eurasia organization, and when I tried to rename it I got error 500 and now that repo is unreachable.
https://git.door43.org/WA_Eurasia/ru_luk_text_ulb
it should be https://git.door43.org/WA_Eurasia/ru_luk_text_ulb_L1

Is there anyway to see the logs for the 500 error?

I don't see anything getting logged for it.  Here is the filesystem tree for that org:
wa_eurasia/
├── ru_luk_text_ulb_l1.git
├── ru_luk_text_ulb_l2.git
├── ru_mat_text_ulb_l1.git
├── ru_mat_text_ulb_l2.git
├── ru_mrk_text_ulb_l1.git
├── ru_mrk_text_ulb_l2.git
├── ru_rev_text_ulb_l1.git
├── ru_rev_text_ulb_l2.git
├── ru-ta-translate-vol1.git
├── ru-ta-translate-vol2.git
├── ru-tq.git
└── ru-tw.git

The error in the log that is being returned when you try to rename it from ru_luk_text_ulb to ru_luk_text_ulb_l1 is:
[root@ip-172-31-38-86 wa_eurasia]# 2017/05/22 14:10:40 [...ters/repo/setting.go:74 SettingsPost()] [E] NewRepoRedirect: Error 1062: Duplicate entry '4746-ru_luk_text_ulb' for key 'UQE_repo_redirect_S'
It looks like an primary key issue, yet it is still trying to save the old name.

The problem seems to lie in how when you rename a repo, it creates a redirect to the new repo (for example git.door43.org/richmahn/test renamed to git.doro43.org/richmahn/test2 will still allow someone to go to richmahn/test and it will redirect to test2). It looks like before the site update the  old name of a renamed repo got used again, and then when wanting to rename that one, it caused two repos to have the same redirect. Can't reproduce it now so looks like when a new repo is created with an old name (but no longer exists) that redirect gets removed.
I have cleared the repo_redirect table. I tried to reproduce by making a repo, e.g. testrepo, rename it, e.g. testreponew, make a new repo with the old name, e.g. testrepo, and renaming that one, e.g. testreponew2....all works well.

Restored redirects for Door43 and Door43-Catalog repos due to hyphen in name change. I guess this redirect is a new feature and was caused by a primary key issue, but wasn't able to reproduce with a new repo. User who had this problem reports there are no problems now.

Restored redirects for Door43 and Door43-Catalog repos due to hyphen in name change. I guess this redirect is a new feature and was caused by a primary key issue, but wasn't able to reproduce with a new repo. User who had this problem reports there are no problems now.


Another improvement to highligh

Add level and height arguments so that the difference between bottom bar and highlight patch is only a convenience layer. This would:

disable (or raise warning) when both bottom_bar=True and level is not None
lead to calling highlight second time internally with different level and height (and alpha) if bottom_bar=True
allow for much higher flexibility if bottom bars of different colors and at different levels are needed

Soon highlight could be moved to borsar.

Now the main function highlight works the way it did before, but there is also a lower-level function (used by highlight internally) that is called highlight_bar which allows more control over the placement of the color bars (useful when there are for example two kind of comparisons where significant differences should be highlighted).
TODOs:

[ ] add docs to highlight_bar
[ ] change axis input arg to ax
[ ] x_values can be None if ax is passed and the axis contains lines (x values are extracted from the lines objects)


Button are not visible properly

I want to fix these buttons so that they are properly visible.

I can fix it for you. You can assign it to me.

@RiyaGupta89  It's resolved


bug: cody.useContext config option does not work

Version
v1.0.1 - v1.0.5
Describe the bug
Reported by Corey Hill on slack: https://sourcegraph.slack.com/archives/C05AGQYD528/p1704736089086349

I need a way to reliably force Cody chat to exclusively use Symf or local embeddings.  I know in the settings there is a way to select context source, but I am not convinced that is doing anything.

Expected behavior
Users should be able to config the type of enhanced context used via the cody.useContext config option
Additional context
No response

Sorry to recomment on this but it seems the problem might still be present, 1.23.1718772677, I'm experiencing embeddings indexing on any codebase even if in settings.json "cody.useContext": "none" is present.
Can anyone confirm this is still happening or that it's just my local install please?


✨ Get stdout and stderr in a single call

What are you trying to do?
Currently it's pretty awkward to fetch all output from an exec, this could be made simpler:
withExec().stdAll() or withExec().output()
Why is this important to you?
No response
How are you currently working around this?
No response

Duplicate of #3496


Compressed matrices leads to sample_size not defined

If the matrix type is CM, then the sample_size assertions will fail because we never set sample_size.
Not sure what the sample_size is for CM, or whether it should simply complain?
Either way I'm happy to make a pull request.

Hi
accepting RichMans pull request solved the issue.
thanks

@hajix can you give me a hint which kaldi class it is? In the copy-feats.cc I only see compressed and sequential matrices, with the exception of htk and sphinx matrices the current script should support all common matrix types.

Hi, is there still the problem? (recently I merged the reading of CM matrices to main branch...)
The BDM matrices are supported too (these are not compressed, but stored with 'double' elements).
K.


"Hide unoccupied" workspaces doesn't work

Describe the bug
"Hide unoccupied" workspaces option doesn't work.
To Reproduce
Set the "Hide unoccupied" workspaces option to "true"
Expected behavior
Unoccupied workspaces should be hidden
Screenshots
n/a
Desktop (please complete the following information):

Distribution: Arch Linux
Window Manager/Desktop Environment: Hyprland

Additional context
n/a

There is an option called 'Total Workspaces' that will always cause the panel to show N number of workspaces at all times. You can change that to 0 to always hide unoccupied workspaces.

That's totally my bad, sorry. Didn't realize that.

I just stumbled upon this same thing. Going through the code I noticed the hideUnoccupied setting seems to be unused now because of the Total workspaces behavior - maybe it could be removed? https://github.com/search?q=repo%3AJas-SinghFSU%2FHyprPanel+hideUnoccupied&type=code


CONTENT-54: Support delete of repositories

For testing:
export `cat .env`
go run cmd/dbmigrate/main.go seed
go run cmd/content-sources/main.go
curl http://localhost/api/content_sources/v1.0/respoitories/ | python -m json.tool   #grab a uuid, notice the total count
curl -X DELETE http://localhost/api/content_sources/v1.0/respoitories/UUID
curl http://localhost/api/content_sources/v1.0/respoitories/ | python -m json.tool   #total count should be 1 less


add rlens and IsLabel instance for lenses

Inspired by the Rawr package (https://hackage.haskell.org/package/rawr), this PR adds:

an rlens function that generates a lens from a record label
an instance of IsLabel for lenses, so you can write julian ^. #age and julian & #age .~ 29 by using the field labels directly as lenses and get all the goodies of you favourite lens library.

This does not add a dependency on a lens library, although the lenses are compatible with lens and microlens packages. Unfortunately without adding a dependency on one of these libraries I can't add doctests for the added functions.
Apparently the IsLabel instance is an orphan, so I have suppressed that warning.

I have moved lensy stuff to Bookkeeper.Lens and figured out how to import microlens for the doctests only

Interesting, the doctests pass here as-is. I will remove them a bit later tonight as they are failing on CI.

Thanks!

Released as version 0.2.4.


Parsing included file '/usr/synopsys/vcs2018.09/vcs/O-2018.09-SP2/etc/uvm-1.2/uvm_macros.svh'.
Back to file '/home/jamesning/work/reggen/rggen-sample-testbench/env/tvip-apb/src/tvip_apb_pkg.sv'.
Parsing included file '/home/jamesning/work/reggen/rggen-sample-testbench/env/tue/src/tue_macros.svh'.
Back to file '/home/jamesning/work/reggen/rggen-sample-testbench/env/tvip-apb/src/tvip_apb_pkg.sv'.
Parsing included file '/home/jamesning/work/reggen/rggen-sample-testbench/env/tvip-apb/src/tvip_apb_types.svh'.
Back to file '/home/jamesning/work/reggen/rggen-sample-testbench/env/tvip-apb/src/tvip_apb_pkg.sv'.
Parsing included file '/home/jamesning/work/reggen/rggen-sample-testbench/env/tvip-apb/src/tvip_apb_configuration.svh'.
Back to file '/home/jamesning/work/reggen/rggen-sample-testbench/env/tvip-apb/src/tvip_apb_pkg.sv'.
Parsing included file '/home/jamesning/work/reggen/rggen-sample-testbench/env/tvip-apb/src/tvip_apb_status.svh'.
Back to file '/home/jamesning/work/reggen/rggen-sample-testbench/env/tvip-apb/src/tvip_apb_pkg.sv'.
Parsing included file '/home/jamesning/work/reggen/rggen-sample-testbench/env/tvip-apb/src/tvip_apb_item.svh'.
Back to file '/home/jamesning/work/reggen/rggen-sample-testbench/env/tvip-apb/src/tvip_apb_pkg.sv'.
Parsing included file '/home/jamesning/work/reggen/rggen-sample-testbench/env/tvip-apb/src/tvip_apb_monitor_base.svh'.
Back to file '/home/jamesning/work/reggen/rggen-sample-testbench/env/tvip-apb/src/tvip_apb_pkg.sv'.
Parsing included file '/home/jamesning/work/reggen/rggen-sample-testbench/env/tvip-apb/src/tvip_apb_master_monitor.svh'.
Back to file '/home/jamesning/work/reggen/rggen-sample-testbench/env/tvip-apb/src/tvip_apb_pkg.sv'.
Parsing included file '/home/jamesning/work/reggen/rggen-sample-testbench/env/tvip-apb/src/tvip_apb_master_sequencer.svh'.
Back to file '/home/jamesning/work/reggen/rggen-sample-testbench/env/tvip-apb/src/tvip_apb_pkg.sv'.
Parsing included file '/home/jamesning/work/reggen/rggen-sample-testbench/env/tvip-apb/src/tvip_apb_master_driver.svh'.
Back to file '/home/jamesning/work/reggen/rggen-sample-testbench/env/tvip-apb/src/tvip_apb_pkg.sv'.
Parsing included file '/home/jamesning/work/reggen/rggen-sample-testbench/env/tvip-apb/src/tvip_apb_master_agent.svh'.
Back to file '/home/jamesning/work/reggen/rggen-sample-testbench/env/tvip-apb/src/tvip_apb_pkg.sv'.
Parsing included file '/home/jamesning/work/reggen/rggen-sample-testbench/env/tvip-apb/src/tvip_apb_master_ral_adapter.svh'.
Back to file '/home/jamesning/work/reggen/rggen-sample-testbench/env/tvip-apb/src/tvip_apb_pkg.sv'.
Parsing included file '/home/jamesning/work/reggen/rggen-sample-testbench/env/tvip-apb/src/tvip_apb_master_ral_predictor.svh'.
Back to file '/home/jamesning/work/reggen/rggen-sample-testbench/env/tvip-apb/src/tvip_apb_pkg.sv'.
Parsing design file '/home/jamesning/work/reggen/rggen-sample-testbench/rtl/rggen-sv-rtl/rggen_backdoor_if.sv'
Parsing design file '/home/jamesning/work/reggen/rggen-sample-testbench/rtl/rggen-sv-rtl/rggen_backdoor_pkg.sv'
Parsing design file '/home/jamesning/work/reggen/rggen-sample-testbench/rtl/rggen-sv-rtl/rggen_backdoor.sv'
Parsing design file '/home/jamesning/work/reggen/rggen-sample-testbench/rtl/rggen-sv-rtl/rggen_rtl_pkg.sv'
Parsing design file '/home/jamesning/work/reggen/rggen-sample-testbench/rtl/rggen-sv-rtl/rggen_apb_if.sv'
Parsing design file '/home/jamesning/work/reggen/rggen-sample-testbench/ral/rggen-sv-ral/rggen_ral_backdoor_pkg.sv'
Parsing included file '/usr/synopsys/vcs2018.09/vcs/O-2018.09-SP2/etc/uvm-1.2/uvm_macros.svh'.
Back to file '/home/jamesning/work/reggen/rggen-sample-testbench/ral/rggen-sv-ral/rggen_ral_backdoor_pkg.sv'.
Parsing design file '/home/jamesning/work/reggen/rggen-sample-testbench/ral/rggen-sv-ral/rggen_ral_pkg.sv'
Parsing included file '/usr/synopsys/vcs2018.09/vcs/O-2018.09-SP2/etc/uvm-1.2/uvm_macros.svh'.
Back to file '/home/jamesning/work/reggen/rggen-sample-testbench/ral/rggen-sv-ral/rggen_ral_pkg.sv'.
Parsing included file '/home/jamesning/work/reggen/rggen-sample-testbench/ral/rggen-sv-ral/rggen_ral_macros.svh'.
Back to file '/home/jamesning/work/reggen/rggen-sample-testbench/ral/rggen-sv-ral/rggen_ral_pkg.sv'.
Parsing included file '/home/jamesning/work/reggen/rggen-sample-testbench/ral/rggen-sv-ral/rggen_ral_utils.svh'.
Back to file '/home/jamesning/work/reggen/rggen-sample-testbench/ral/rggen-sv-ral/rggen_ral_pkg.sv'.
Parsing included file '/home/jamesning/work/reggen/rggen-sample-testbench/ral/rggen-sv-ral/rggen_ral_field.svh'.
Back to file '/home/jamesning/work/reggen/rggen-sample-testbench/ral/rggen-sv-ral/rggen_ral_pkg.sv'.
Parsing included file '/home/jamesning/work/reggen/rggen-sample-testbench/ral/rggen-sv-ral/rggen_ral_rowo_field.svh'.
Back to file '/home/jamesning/work/reggen/rggen-sample-testbench/ral/rggen-sv-ral/rggen_ral_pkg.sv'.
Parsing included file '/home/jamesning/work/reggen/rggen-sample-testbench/ral/rggen-sv-ral/rggen_ral_rwe_rwl_field.svh'.
Back to file '/home/jamesning/work/reggen/rggen-sample-testbench/ral/rggen-sv-ral/rggen_ral_pkg.sv'.
Parsing included file '/home/jamesning/work/reggen/rggen-sample-testbench/ral/rggen-sv-ral/rggen_ral_w0trg_w1trg_field.svh'.
Back to file '/home/jamesning/work/reggen/rggen-sample-testbench/ral/rggen-sv-ral/rggen_ral_pkg.sv'.
Parsing included file '/home/jamesning/work/reggen/rggen-sample-testbench/ral/rggen-sv-ral/rggen_ral_row0trg_row1trg_field.svh'.
Back to file '/home/jamesning/work/reggen/rggen-sample-testbench/ral/rggen-sv-ral/rggen_ral_pkg.sv'.
Parsing included file '/home/jamesning/work/reggen/rggen-sample-testbench/ral/rggen-sv-ral/rggen_ral_custom_field.svh'.
Back to file '/home/jamesning/work/reggen/rggen-sample-testbench/ral/rggen-sv-ral/rggen_ral_pkg.sv'.
Parsing included file '/home/jamesning/work/reggen/rggen-sample-testbench/ral/rggen-sv-ral/rggen_ral_reg.svh'.
Back to file '/home/jamesning/work/reggen/rggen-sample-testbench/ral/rggen-sv-ral/rggen_ral_pkg.sv'.
Parsing included file '/home/jamesning/work/reggen/rggen-sample-testbench/ral/rggen-sv-ral/rggen_ral_reg_file.svh'.
Back to file '/home/jamesning/work/reggen/rggen-sample-testbench/ral/rggen-sv-ral/rggen_ral_pkg.sv'.
Parsing included file '/home/jamesning/work/reggen/rggen-sample-testbench/ral/rggen-sv-ral/rggen_ral_indirect_reg.svh'.
Back to file '/home/jamesning/work/reggen/rggen-sample-testbench/ral/rggen-sv-ral/rggen_ral_pkg.sv'.
Parsing included file '/home/jamesning/work/reggen/rggen-sample-testbench/ral/rggen-sv-ral/rggen_ral_block.svh'.
Back to file '/home/jamesning/work/reggen/rggen-sample-testbench/ral/rggen-sv-ral/rggen_ral_pkg.sv'.
Parsing included file '/home/jamesning/work/reggen/rggen-sample-testbench/ral/rggen-sv-ral/rggen_ral_map.svh'.
Back to file '/home/jamesning/work/reggen/rggen-sample-testbench/ral/rggen-sv-ral/rggen_ral_pkg.sv'.
Parsing design file '/home/jamesning/work/reggen/rggen-sample-testbench/ral/block_0_ral_pkg.sv'
Parsing included file '/usr/synopsys/vcs2018.09/vcs/O-2018.09-SP2/etc/uvm-1.2/uvm_macros.svh'.
Back to file '/home/jamesning/work/reggen/rggen-sample-testbench/ral/block_0_ral_pkg.sv'.
Parsing included file '/home/jamesning/work/reggen/rggen-sample-testbench/ral/rggen-sv-ral/rggen_ral_macros.svh'.
Back to file '/home/jamesning/work/reggen/rggen-sample-testbench/ral/block_0_ral_pkg.sv'.
Parsing design file '/home/jamesning/work/reggen/rggen-sample-testbench/ral/block_1_ral_pkg.sv'
Parsing included file '/usr/synopsys/vcs2018.09/vcs/O-2018.09-SP2/etc/uvm-1.2/uvm_macros.svh'.
Back to file '/home/jamesning/work/reggen/rggen-sample-testbench/ral/block_1_ral_pkg.sv'.
Parsing included file '/home/jamesning/work/reggen/rggen-sample-testbench/ral/rggen-sv-ral/rggen_ral_macros.svh'.
Back to file '/home/jamesning/work/reggen/rggen-sample-testbench/ral/block_1_ral_pkg.sv'.
Parsing design file '/home/jamesning/work/reggen/rggen-sample-testbench/env/env_pkg.sv'
Parsing included file '/usr/synopsys/vcs2018.09/vcs/O-2018.09-SP2/etc/uvm-1.2/uvm_macros.svh'.
Back to file '/home/jamesning/work/reggen/rggen-sample-testbench/env/env_pkg.sv'.
Parsing included file '/home/jamesning/work/reggen/rggen-sample-testbench/env/tue/src/tue_macros.svh'.
Back to file '/home/jamesning/work/reggen/rggen-sample-testbench/env/env_pkg.sv'.
Parsing included file '/home/jamesning/work/reggen/rggen-sample-testbench/ral/rggen-sv-ral/rggen_ral_macros.svh'.
Back to file '/home/jamesning/work/reggen/rggen-sample-testbench/env/env_pkg.sv'.
Parsing included file '/home/jamesning/work/reggen/rggen-sample-testbench/env/env_configuration.svh'.
Back to file '/home/jamesning/work/reggen/rggen-sample-testbench/env/env_pkg.sv'.
Parsing included file '/home/jamesning/work/reggen/rggen-sample-testbench/env/env_ral_model.svh'.
Back to file '/home/jamesning/work/reggen/rggen-sample-testbench/env/env_pkg.sv'.
Parsing included file '/home/jamesning/work/reggen/rggen-sample-testbench/env/env_ral_monitor.svh'.
Back to file '/home/jamesning/work/reggen/rggen-sample-testbench/env/env_pkg.sv'.
Parsing included file '/home/jamesning/work/reggen/rggen-sample-testbench/env/env_sequencer.svh'.
Back to file '/home/jamesning/work/reggen/rggen-sample-testbench/env/env_pkg.sv'.
Parsing included file '/home/jamesning/work/reggen/rggen-sample-testbench/env/env.svh'.
Back to file '/home/jamesning/work/reggen/rggen-sample-testbench/env/env_pkg.sv'.
Parsing included file '/home/jamesning/work/reggen/rggen-sample-testbench/env/ral_test.svh'.
Back to file '/home/jamesning/work/reggen/rggen-sample-testbench/env/env_pkg.sv'.
Parsing design file '/home/jamesning/work/reggen/rggen-sample-testbench/env/apb_env_pkg.sv'
Parsing included file '/usr/synopsys/vcs2018.09/vcs/O-2018.09-SP2/etc/uvm-1.2/uvm_macros.svh'.
Back to file '/home/jamesning/work/reggen/rggen-sample-testbench/env/apb_env_pkg.sv'.
Parsing included file '/home/jamesning/work/reggen/rggen-sample-testbench/env/tue/src/tue_macros.svh'.
Back to file '/home/jamesning/work/reggen/rggen-sample-testbench/env/apb_env_pkg.sv'.
Parsing design file '/home/jamesning/work/reggen/rggen-sample-testbench/env/apb_top.sv'
CPU time: .877 seconds to compile
vcs -full64 -ntb_opts uvm-1.2 -l vcs.log -top top
Chronologic VCS (TM)
Version O-2018.09-SP2_Full64 -- Thu Aug 31 19:24:52 2023
Copyright (c) 1991-2018 by Synopsys Inc.
ALL RIGHTS RESERVED
This program is proprietary and confidential information of Synopsys Inc.
and may be used and disclosed only as authorized in a license agreement
controlling such use and disclosure.
Parsing design file '/usr/synopsys/vcs2018.09/vcs/O-2018.09-SP2/etc/uvm-1.2/uvm_pkg.sv'
Parsing included file '/usr/synopsys/vcs2018.09/vcs/O-2018.09-SP2/etc/uvm-1.2/uvm_macros.svh'.
Parsing included file '/usr/synopsys/vcs2018.09/vcs/O-2018.09-SP2/etc/uvm-1.2/macros/uvm_version_defines.svh'.
Back to file '/usr/synopsys/vcs2018.09/vcs/O-2018.09-SP2/etc/uvm-1.2/uvm_macros.svh'.
Parsing included file '/usr/synopsys/vcs2018.09/vcs/O-2018.09-SP2/etc/uvm-1.2/macros/uvm_global_defines.svh'.
Back to file '/usr/synopsys/vcs2018.09/vcs/O-2018.09-SP2/etc/uvm-1.2/uvm_macros.svh'.
Parsing included file '/usr/synopsys/vcs2018.09/vcs/O-2018.09-SP2/etc/uvm-1.2/macros/uvm_message_defines.svh'.
Back to file '/usr/synopsys/vcs2018.09/vcs/O-2018.09-SP2/etc/uvm-1.2/uvm_macros.svh'.
Parsing included file '/usr/synopsys/vcs2018.09/vcs/O-2018.09-SP2/etc/uvm-1.2/macros/uvm_phase_defines.svh'.
Back to file '/usr/synopsys/vcs2018.09/vcs/O-2018.09-SP2/etc/uvm-1.2/uvm_macros.svh'.
Parsing included file '/usr/synopsys/vcs2018.09/vcs/O-2018.09-SP2/etc/uvm-1.2/macros/uvm_object_defines.svh'.
Back to file '/usr/synopsys/vcs2018.09/vcs/O-2018.09-SP2/etc/uvm-1.2/uvm_macros.svh'.
Parsing included file '/usr/synopsys/vcs2018.09/vcs/O-2018.09-SP2/etc/uvm-1.2/macros/uvm_printer_defines.svh'.
Back to file '/usr/synopsys/vcs2018.09/vcs/O-2018.09-SP2/etc/uvm-1.2/uvm_macros.svh'.
Parsing included file '/usr/synopsys/vcs2018.09/vcs/O-2018.09-SP2/etc/uvm-1.2/macros/uvm_tlm_defines.svh'.
Parsing included file '/usr/synopsys/vcs2018.09/vcs/O-2018.09-SP2/etc/uvm-1.2/tlm1/uvm_tlm_imps.svh'.
Back to file '/usr/synopsys/vcs2018.09/vcs/O-2018.09-SP2/etc/uvm-1.2/macros/uvm_tlm_defines.svh'.
Back to file '/usr/synopsys/vcs2018.09/vcs/O-2018.09-SP2/etc/uvm-1.2/uvm_macros.svh'.
Parsing included file '/usr/synopsys/vcs2018.09/vcs/O-2018.09-SP2/etc/uvm-1.2/macros/uvm_sequence_defines.svh'.
Back to file '/usr/synopsys/vcs2018.09/vcs/O-2018.09-SP2/etc/uvm-1.2/uvm_macros.svh'.
Parsing included file '/usr/synopsys/vcs2018.09/vcs/O-2018.09-SP2/etc/uvm-1.2/macros/uvm_callback_defines.svh'.
Back to file '/usr/synopsys/vcs2018.09/vcs/O-2018.09-SP2/etc/uvm-1.2/uvm_macros.svh'.
Parsing included file '/usr/synopsys/vcs2018.09/vcs/O-2018.09-SP2/etc/uvm-1.2/macros/uvm_reg_defines.svh'.
Back to file '/usr/synopsys/vcs2018.09/vcs/O-2018.09-SP2/etc/uvm-1.2/uvm_macros.svh'.
Parsing included file '/usr/synopsys/vcs2018.09/vcs/O-2018.09-SP2/etc/uvm-1.2/macros/uvm_deprecated_defines.svh'.
Back to file '/usr/synopsys/vcs2018.09/vcs/O-2018.09-SP2/etc/uvm-1.2/uvm_macros.svh'.
Back to file '/usr/synopsys/vcs2018.09/vcs/O-2018.09-SP2/etc/uvm-1.2/uvm_pkg.sv'.
Error-[SE] Syntax error
Following verilog source has syntax error :
"/usr/synopsys/vcs2018.09/vcs/O-2018.09-SP2/etc/uvm-1.2/uvm_pkg.sv", 32:
token is ';'
package uvm_pkg;
^
1 error
CPU time: .162 seconds to compile
make[2]: Leaving directory '/home/jamesning/work/reggen/rggen-sample-testbench/sim/apb/verilog'
make[1]: Leaving directory '/home/jamesning/work/reggen/rggen-sample-testbench/sim/apb/verilog'

This TB also supports VHDL so VSC MX is required.
To run the TB on your side, you need to create your own execution script.

Hi Taichi，
I have modified the file vcs.mk script and it can work with VCS O-2018.09-SP2 version without vcs-mx. I haven't tried it with VHDL yet.
The script is as follwing, show you for reference.


Multi-Repo Support

Any chance for Multi-Repo support (perhaps a drop-down box that selects a repo via something like /admin/repo to /admin/ldaprepo or so?  I have an Ecto Repo for Postgre, an Ecto Repo for LDAP (as well as direct access via erlang's library so if I had to write it in to ex_admin directly somehow if you have a pluggable area for that, that would work), and I might have to add in a nosql store Repo later as well...

I’ll have to think about this. Multiple SQL repos should not be too difficult. They could be defined in the resource file. Does LDAP repo work today? I’ve never tried it. Nor have I tried no-sql repos either.

On Jun 7, 2016, at 10:52 AM, OvermindDL1<EMAIL_ADDRESS>wrote:
Any chance for Multi-Repo support (perhaps a drop-down box that selects a repo via something like /admin/repo to /admin/ldaprepo or so? I have an Ecto Repo for Postgre, and Ecto Repo for LDAP (as well as direct access via erlang's library so if I had to write it in to ex_admin directly somehow if you have a pluggable area for that, that would work), and I might have to add in a nosql store Repo later as well...
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/smpallen99/ex_admin/issues/138, or mute the thread https://github.com/notifications/unsubscribe/AA2YpaBNu7QH2XwDKEa47x1vSMq3jP0Uks5qJYXEgaJpZM4IwAue.

There is an ecto_ldap adapter for ecto 1, I am currently in the process of rewriting it to ecto 2 (with some additional overhauls).  LDAP is exposed very much like a KV store, like mongo or so, however it has better lookup options that is more SQL'ish without the joins and such.

+1 for multi-repo support. I'm currently experimenting with building an umbrella project with 2 SQL Repos (each in a separate OTP app) and being able to manage both from ExAdmin would be a nice addition.

is there a wip about this?, I'd like to contribute

I too would like to contribute to this.
I'm presuming the recent-ish updates to Ecto might make this a bit easier.


Blank screen when Sam is down

If any service can't be reached (Rawls, Sam, Leo) should we show a helpful error message? I imagine an error banner or popup with a link to pingdom.

This will be largely solved by #127

Fixed by #127 (you will now get an error message)


Problem with configuring driver with local and remote clusters

@przem123 commented on Wed Dec 11 2019
I created a configuration for CSI driver with local and remote cluster.<PHONE_NUMBER>4479190260 and gpfs0 are local id and filesystem.<PHONE_NUMBER>880872527 is my remote cluster.
apiVersion: csi.ibm.com/v1
kind: CSIScaleOperator
metadata:
  labels:
    app.kubernetes.io/instance: ibm-spectrum-scale-csi-operator
    app.kubernetes.io/managed-by: ibm-spectrum-scale-csi-operator
    app.kubernetes.io/name: ibm-spectrum-scale-csi-operator
  name: ibm-spectrum-scale-csi
  release: ibm-spectrum-scale-csi-operator
  namespace: ibm-spectrum-scale-csi-driver
spec:
  clusters:
    - id: '17399599334479190260'
      primary:
        primaryFs: gpfs0
        primaryFset: csifset
      restApi:
        - guiHost: <IP_ADDRESS>
      secrets: csisecret-local
      secureSslMode: false
    - id: '4473793006880872527'
      restApi:
        - guiHost: <IP_ADDRESS>
      secrets: csisecret-remote
      secureSslMode: false
  scaleHostpath: /mnt/gpfs0
status: {}

The driver and other items are in ibm-spectrum-scale-csi-drivernamespace.
[root@worker01 operator]# oc get all -n ibm-spectrum-scale-csi-driver
NAME                                                   READY   STATUS    RESTARTS   AGE
pod/ibm-spectrum-scale-csi-attacher-0                  1/1     Running   0          5h12m
pod/ibm-spectrum-scale-csi-kjcs6                       2/2     Running   0          4h46m
pod/ibm-spectrum-scale-csi-nxmkg                       2/2     Running   0          4h46m
pod/ibm-spectrum-scale-csi-operator-75f65c5999-9wnk2   2/2     Running   0          5h58m
pod/ibm-spectrum-scale-csi-provisioner-0               1/1     Running   0          5h12m

NAME                                              TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)    AGE
service/ibm-spectrum-scale-csi-operator-metrics   ClusterIP   <IP_ADDRESS>   <none>        8383/TCP   5h58m

NAME                                    DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR   AGE
daemonset.apps/ibm-spectrum-scale-csi   2         2         2       2            2           <none>          5h12m

NAME                                              READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/ibm-spectrum-scale-csi-operator   1/1     1            1           5h58m

NAME                                                         DESIRED   CURRENT   READY   AGE
replicaset.apps/ibm-spectrum-scale-csi-operator-75f65c5999   1         1         1       5h58m

NAME                                                  READY   AGE
statefulset.apps/ibm-spectrum-scale-csi-attacher      1/1     5h12m
statefulset.apps/ibm-spectrum-scale-csi-provisioner   1/1     5h12m

Unfortunately, I cannot use it dynamic povisioning for local and remote fs:
[root@worker01 operator]# oc describe pvc scale-remotefset-pvc
Name:          scale-remotefset-pvc
Namespace:     default
StorageClass:  ibm-spectrum-scale-csi-remotefs
Status:        Pending
Volume:
Labels:        <none>
Annotations:   volume.beta.kubernetes.io/storage-provisioner: ibm-spectrum-scale-csi
Finalizers:    [kubernetes.io/pvc-protection]
Capacity:
Access Modes:
VolumeMode:    Filesystem
Events:
  Type       Reason                Age                      From                         Message
  ----       ------                ----                     ----                         -------
  Normal     ExternalProvisioning  109s (x1191 over 4h51m)  persistentvolume-controller  waiting for a volume to be created, either by external provisioner "ibm-spectrum-scale-csi" or manually created by system administrator
Mounted By:  <none>

Any idea how to solve it ?

@yadaven commented on Thu Dec 12 2019
I think in storage class we are not using correct provisioner name. Recently it has been changed to spectrumscale.csi.ibm.com instead of ibm-spectrum-scale-csi

@mew2057 commented on Thu Dec 12 2019
@yadaven @smitaraut  Has the documentation in the GitHub Repo and KC been verified to match the provisioner name change? Moving this issue to driver repo.

We should probably design a test case that emulates this environment. Going to roll  into CI/CD component.

Just reread this, this might  have been fixed already. @przem123 are you still encountering  this issue?

Fixed and Verified.


webextension cannot communicate with native app (ERR_WEBEID_NATIVE_UNAVAILABLE) in Fedora

Hi guys!
thx for the great work you're doing here!
I'm trying to get the stack running on a Fedora 36 system.
I've successfully compiled and installed the web-eid-app following the instructions given in https://github.com/web-eid/web-eid-app/pull/173 (https://github.com/web-eid/web-eid-app/pull/173#issuecomment-1018874023)
Running the python tests as stated in the input-output mode-section in the README also succeeds.
However, communication to the native app via the browser extensions fails. I'm using https://web-eid.eu/ to test the flow. This is the error I'm shown:

If that helps in any way, this is the line that throws:

@eidins maybe you can bring some light to this?

Hi @mrts,
thx for your help!
It's working now. eu.webeid.json was indeed the file causing trouble. It was and is present in one of the paths mentioned in MDN (/usr/lib64/mozilla/native-messaging-hosts/eu.webeid.json)
I didn't have to set any symlinks but the path key held a false value: /usr/local/bin/web-eid while a call to which web-eid revealed the binary sitting in /usr/bin/web-eid. Correcting that value solved the issue.
I'd contribute a fix but unfortunately it's not clear to me how to exactly this needs to be fixed (not really familiar with cmake). It seems like CMAKE_INSTALL_FULL_BINDIR is not holding the correct value in my case.

@mrtnschltr, thank you! This will however unfortunately break Ubuntu.
There is another way by specifying -DCMAKE_INSTALL_PREFIX=/usr during build. Can you please if https://github.com/web-eid/web-eid-app/pull/223/files works?

Yes that does the trick!

Thank you for testing!


Reserve multicodec for filecoin compact serialization format

Ref: https://github.com/filecoin-project/specs/pull/131
Note that we're only using one multicodec here, not one per object type.

https://github.com/multiformats/multicodec/pull/161#issuecomment-627152617


WIP: Windows fixes: RegEx(es) & replacing pool.map

Summary
This PR solves two issues observed when executing the extension in Windows OS (7, 10). They are related to RegEx expressions used to parse pip show info and when getting the IBMQ Devices' status (#2)
Details and comments
Initially, the PR is tagged as WIP due we need to test the changes on Windows before the merge. Don't approve/merge it before these tests.

Tested on Windows, the foor loop works smooth and avoids the previous errors. Removing WIP from the title


Multiple Hubs

Describe the bug
Multiple hubs does not work using this template...
"platforms": [
{
"platform": "HarmonyHubWebSocket",
"name": "HubName",
"hubIP": "192.168.1.XX",
"otherPlatforms": [{
"name": "OtherHubName",
"hubIP": "192.168.1.YY"
}]
}
]
To Reproduce
Use the template
Expected behavior
Two hubs in homekit... you see two hubs in the Homebridge UI, but not in home kit....
Screenshots
None
IOS (please complete the following information):
Latest
Logs
None
Config
Additional context
Using this config in the JSON works...
    {
        "platform": "HarmonyHubWebSocket",
        "name": "Harmony-Lounge",
        "hubIP": "10.173.45.XX",
        "mainActivity": "Lounge Sky TV"
    },
    {
        "platform": "HarmonyHubWebSocket",
        "name": "Harmony-Kitchen",
        "hubIP": "10.173.45.XX",
        "mainActivity": "Kitchen SKy TV"
    },

Hi,
you have to add the second one manuallay in home app, as explained in the log and README, since second one will be necessary exposed as an external accessory . (It is in order to make both available in remote app in control center)
https://twitter.com/dujnic/status/1110644949027041282?s=21.

Hi,
you have to add the second one manuallay in home app, as explained in the log and README, since second one will be necessary exposed as an external accessory . (It is in order to make both available in remote app in control center)
https://twitter.com/dujnic/status/1110644949027041282?s=21.

@nicoduj Thanks, OK, so I deleted the plugin in and code, cleaned the cache, reinstalled the plugin and then entered the below config... the first HUB and TV appear fine.... when I go to "Add Accessory" nothing appears to add (I'm trying to add a 2nd Harmony Hub and TV), can you let me know what I have done wrong?
    {
        "platform": "HarmonyHubWebSocket",
        "name": "Harmony-Kitchen",
        "hubIP": "<IP_ADDRESS>",
        "mainActivity": "Kitchen Sky TV",
        "TVAccessory": true,
        "publishAllTVAsExternalAccessory": true
    },

I'm confused by the fact you show code for two hubs, but you say don't use that code?

OK, worked it out... so you do use the two hub code, then add manually.. simple.... the instructions were a little confusing.... but thanks for the support, love the app.
Code I used
    {
        "platform": "HarmonyHubWebSocket",
        "name": "Harmony-Kitchen",
        "hubIP": "10.173.XX.XX",
        "mainActivity": "Kitchen Sky TV",
        "otherPlatforms": [
            {
                "name": "Harmony-Lounge",
                "hubIP": "10.173.XX.XX",
                "mainActivity": "Lounge Sky TV"
            }
        ]
    },

Feel free to make a pull request on the readme if you think you can describe better how to do it :)
Sent with GitHawk

Feel free to make a pull request on the readme if you think you can describe better how to do it :)
Sent with GitHawk

No idea how to do that... some working
INSTALLATION FOR MULTIPLE HUBS
Firstly use the following code, ensuring that you have fixed IP address applied to your hubs. Then once you have the config in the JSON, restart home bridge.. NOTE - Only the RV for the first hub will appear in Homebridge, the 2nd one, 3rd etc will need you to click ADD ACCESSORY in homekit and add them manually.  (the manual addition is done after the jason and homebridge restart within the homekit app.


MostRequestedPriority is still mentioned in documentation, but seems to be gone many releases ago

The documentation of strategy HighNodeUtilization states that it must be used in conjunction with MostRequestedPriority.
But MostRequestedPriority is gone and nowhere documented. It would suggest to remove it from the docs

Thanks @omichels, it does look like that plugin was removed and we didn't update it. The NodeResourcesMostAllocated plugin has also been deprecated, so it looks like the replacement is now to use NodeResourcesFit with the MostAllocated scoring strategy based on these docs https://kubernetes.io/docs/reference/scheduling/config/#scheduling-plugins
The idea still stands, that with HighNodeUtilization you should have some sort of bin-packing plugin enabled in the scheduler otherwise you'll get an eviction loop due to the conflict of what the scheduler wants vs what the descheduler wants.
/kind documentation

So, in order to avoid a conflict (pods get evicted by the descheduler and then scheduled on that same node by the scheduler), i need a non-default scheduler configuration?
Do you happen to have a configuration example?

@omichels yes, by default the scheduler will try to place pods evenly spread according to their resource consumption on the nodes to achieve the lowest resource consumption on all nodes. With HighNodeUtilization, the descheduler is assuming that you want the pods packed as tightly as possible to target high resource consumption on the fewest nodes.
I don't have an exact example, so you might need to tweak this, but your scheduler config would look something like this (in k8s 1.23 we have multiPoint, in earlier versions you'll use v1beta2 and disable BalancedAllocation in preScore and Score individually, see kind of an example in https://kubernetes.io/docs/reference/scheduling/config/#multiple-profiles):
apiVersion: kubescheduler.config.k8s.io/v1beta3
kind: KubeSchedulerConfiguration
profiles:
  - schedulerName: default-scheduler
    plugins:
      multiPoint:
        disabled:
        - name: "NodeResourcesBalancedAllocation"
    pluginConfig:
    - name: "NodeResourcesFit"
      args:
        scoringStrategy:
          type: "MostAllocated"

There's an example for using NodeResourcesFit in the k8s docs on scheduler config as well https://kubernetes.io/docs/reference/scheduling/config/#scheduler-configuration-migrations

@damemi

What is the relationship/interaction between LowNodeUtilization & HighNodeUtilization? Can they be used together so that pods are packed into the least possible nodes, as evenly as possible? Or should only one be enabled?
Is there an option to ensure a pod is only restarted if it is of a minimum age (say 1h) so that if the scheduler and descheduler do have a different opinion on how to pack pods, the eviction loop is at least slowed down?

Thanks

@day1118 LowNodeUtilization and HighNodeUtilization are polar opposite strategies, so there's no use in enabling them both. The thresholds in each strategy are for you to define "how" tightly (or loosely) you want each node to be packed.
LowNodeUtilization looks at nodes with usage higher than the set threshold and evicts pods from those nodes, with the assumption that the scheduler will have the same resource-spreading strategy enabled.
HighNodeUtilization finds nodes with a usage that's lower than the threshold and evicts from those nodes, again hoping that the scheduler has the same intent set up and will place these pods onto the more tightly-packed nodes.
Running both of these strategies (or running a strategy that conflicts with the scheduler's config) is kind of like pressing the gas and the brake at the same time. So, we don't offer a way to slow down the eviction loop because that is counter to the purpose of the descheduler. You would ultimately never see the cluster reach the desired state, which is the cause for the loop. (If you really want, you can achieve slowing that down by just tweaking the run interval of the descheduler but again, there is no point to this.)
Hope this helps clear up the distinction

@damemi @omichels I can work on updating the docs w..r.t removing MostRequestedPriority. Kindy let me know if that's okay and it's not already been worked upon 🙂 and will create a PR otherwise.

@pravarag yeah, if you would like to help clarify the docs around this with the new Plugin settings that would be awesome

@pravarag bump :) ... were you still planning to open a docs PR to update this?

/assign  i will open a docs pr to update now

/assign


Please add dependency list clearly.

E.G -
devise-4.2.0 requires ruby version >= 2.1.0, which is incompatible with the current version, ruby 2.0.0p648

@bugwrangler Sorry for incorrect dependency version. Quick fix would be use ruby 2.3.0 for project. You can easily run by rvm install ruby-2.3.0 and rvm use 2.3.0
I'll add ruby version to Gemfile.
Thanks for creating an issue.

pg_config fails.
Added SS to rectify.

I think I'm having the same issue however I'm not sure what needs to be set to use 2.3.1 instead of 2.0. I just installed ruby & rbenv on my mac and this is the result I get when trying to bundle install.

I have updated ruby version to 2.3.0 and fixed docker issues in #44 This should fix the issue.
Apologies for delay in response. Thanks for trying tool


fix(openchallenges): change paginator variable to dynamic rendering

fixes #2425

As we added a new condition to not the paginator element f no data found, the variable of paginator is undefined initially as it is static, which caused the error.
Changelogs

Change the paginator to dynamic, so its value will be set after the content is fully initialized

Noticed a new bug related to the paginator.
copy and paste the pagination in url does not reflect the page number changes on the paginator UI. For example, entering http://localhost:4200/challenge?pageNumber=6 should show page number 5.


Export of symbols for test resets?

Problem
I am probably doing something weird to have a wrapper defined in an NX monorepo & have it tested like this, but so far this is the most concise test I could make.
The issue stems from trying to check if the ApolloClient in the context has the correct link URL, since this lib at the moment seems to store state in the global.window, the only way for me to make more than 1 test work is by resetting the content of the variables this library sets in window.
2 things I want to ask:

Why does this need to store the state in the window?
Can we export those symbols for type safety? redeclaring them myself as well as the type definition in the window interface is bound to be error prone.

The specific file where I got the symbols from: package/src/ssr/ApolloRehydrateSymbols.tsx

Hi @luchillo17, good point, this needs some way to reset in tests.
I don't want to expose the symbols though - this is an implementation detail and can change in future versions. Instead, I've added a resetNextSSRApolloSingletons function in #35.
You can use it like
afterEach(resetNextSSRApolloSingletons);

As for your question

Why does this need to store the state in the window?

These singletons are needed to transport data from SSR into the browser - as the Client in the browser already starts up before the SSR pass finishes, we need to continuously push data from the server into the browser client.
Next.js actually does something very similar to this, take a look at window.__next_f.

A 0.2.0 release with this will be available in a moment :)

Awesome, will try it ASAP.

Not working unfortunatelly, these are your resets:
    delete window[ApolloRehydrationCache];
    delete window[ApolloResultCache];
    delete window[ApolloSSRDataTransport];

And these are mine:
    delete window[ApolloResultCache];
    delete window[ApolloClientSingleton];
    delete window[SuspenseCacheSingleton];

@phryneas can we re-open this? the resets you put were not enough in my test...

Hi @luchillo17 I'm sorry for the delay - I'll put out a fix for this in a bit.

Released with https://github.com/apollographql/apollo-client-nextjs/releases/tag/v0.2.2 - if there's anything else, please reopen, or create a new issue :)

Working perfectly, thanks.


Avoid reinstalling the same PGP key over and over again.

The current command repeatedly installs the exact same key over and over and over again. Furthermore, it causes the Chef run to
fail whenever the SKS OpenPGP keyserver is offline. This avoids that problem while still installing the key if available.

Closing due to inactivity.
If this is still an issue please reopen or open another PR.
Alternatively drop by the #sous-chefs channel on the Chef Community Slack and we'll be happy to help!
Thanks,
Sous-Chefs

Closing due to inactivity.
If this is still an issue please reopen or open another PR.
Alternatively drop by the #sous-chefs channel on the Chef Community Slack and we'll be happy to help!
Thanks,
Sous-Chefs


Add in unit tests for code added so far

Add in unit tests for code added so far

Hello! I've created some basic unit tests within a unit test project, and resolved a nuget package error with cosmos-toolbox-app.csproj.
Is this task still available for work?


update  SDK to typescript version

all the temp commits should be properly rebased

Done.

Web wallet:

Transaction/ Coin details: sort by In / Out - not working

Error with switching currencies, as on the develop branch

Top-up invite link/claim back - failed

I can't send FT even if I have them on my balance, Max function with FT also is not working

Tip in tx detail is broken

After refreshing a page:

The last account (7) in my wallet was not visible although there are ae tokens on balance (0.10 ae)
Notifications are loading slowly

Extension:

if I enter 0,1 in the amount input field it will be counted as 0 (in extension)
issue when changing currency
Can't connect to the superhero.com
connection to dex - pop-up is opening in the web window

When we are trying to use CompilerHttp from sdk
UnsupportedVersionError: Unsupported compiler version 6.1.0. Supported: >= 7.0.1 < 8.0.0     at Object.sendRequest (autorest.mjs?0778:91:1)     at async Object.sendRequest (autorest.mjs?0778:66:1)     at async CompilerHttp.sendOperationRequest

There are no such thing as Schema, so it should be also replaced with Tag in the e2e test other.

@Liubov-crypto fixed the default name issue.
FT balances bug I observed in the develop and 1.0.2 branch too. Please confirm.

feat-sdk12.wallet.z52da5wt.xyz

@Liubov-crypto fixed the default name issue.
FT balances bug I observed in the develop and 1.0.2 branch too. Please confirm.

The default name issue has been fixed.
FT balances issue is also reproducible on develop branch.


Move Linux kitchen tests from US North to other regions

Motivation
This is a workaround. In US North Azure VMs, sudo complains with:
sudo: unable to resolve host dd-agent-testing-debian-10-azure: Name or service not known

Which breaks our parsing of the agent status because we call sudo datadog-agent status -j 2>&1
The better fix would be to not redirect stderr to stdout on that command.

Test pipeline: https://gitlab.ddbuild.io/DataDog/datadog-agent/pipelines/4906662


ProtectedBranches: log pushed_refs in debug mode

This will help in debugging #271.

Going to close this since the original issue seems quiet, and I'd rather not commit something to master to help what appears to be a user hitting an edge case of some sort, given @jawshooah's difficulty in reproducing the issue.


How can we break the loops in the Protractor?

Hi, I'm not able to find a way to break the while loop in the protractor.
Can any one share the comments how to acheive it.

It's just javascript, so you can still use break;'


Miscellaneous fixes

A collection of minor fixes.

It turns out git archive strips out the 'v' of the tag inside the zip file. I've fixed this now and we will be setting ref to release versions (or 'master' for development, which works).
Other than adding the appveyor badge, I want the see the tests green on master so I'm merging now.


[MINOR][CORE] Process bar should print new line to avoid polluting logs

What changes were proposed in this pull request?

Use println() instead of print() to show process bar in console.
Why are the changes needed?

Logs are polluted by process bar:

This is easy to reproduce:

start ./bin/spark-shell
sc.setLogLevel("INFO")
run: spark.range(100000000).coalesce(1).write.parquet("/tmp/result")

Does this PR introduce any user-facing change?

Yeah, more friendly format in console.
How was this patch tested?

Tested manually.

Merged build finished. Test PASSed.

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

Test build #115991 has started for PR 27061 at commit 91217ef.

You can disable it with spark.ui.showConsoleProgress in this case.
But adding a line feed will cause it to print each update on a newline, won't it? it's meant to print over itself. Did you mean to add one CR/LF before or after the loop?

Test build #115991 has finished for PR 27061 at commit 91217ef.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

But adding a line feed will cause it to print each update on a newline, won't it? it's meant to print over itself.

Oh, yes, you're right.

Did you mean to add one CR/LF before or after the loop?

Ah, I don't understand well. But I just want to add a new line for following logs.

What if instead you print(CR + bar + CR)?

What if instead you print(CR + bar + CR)?

This works after I quickly tried locally. But I didn't see progress bar move on(possibly due to the job is too small) to validate it still print over itself.

The change I suggested ought to be OK. Note that it does print a CR already when it is clear()ed, so i guess this happens while logs occur during progress? In that case the progress bar prints over the log I guess, but, that always happened.
It would be worth just making a bigger dummy test to verify it prints over itself as usual with that change, if you want to proceed.

@srowen I did another manually test by inserting/modifying some code into ConsoleProgressBar and the behavior looks good.
Did you ask for a unit test?

Test build #116241 has started for PR 27061 at commit 9146482.

Merged build finished. Test PASSed.

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

Test build #116241 has finished for PR 27061 at commit 9146482.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

Jenkins retest this please

Test build #116246 has started for PR 27061 at commit 9146482.

Merged build finished. Test PASSed.

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

Test build #116246 has finished for PR 27061 at commit 9146482.

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

Merged build finished. Test PASSed.

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

Merged to master

Thanks!


[WIP] [Storage] Add tests for credentials from @azure/identity

I couldn't get all of the credentials working.
Added findings in inline comments mentioning the behaviour of each of the Credentials from @azure/identity in node and browser and the issues that I have encountered with each of them.
New environment variables needed in the CI(and locally)
  "AZURE_TENANT_ID",
  "AZURE_CLIENT_ID",
  "AZURE_CLIENT_SECRET",
  "ACCOUNT_USERNAME",
  "ACCOUNT_PASSWORD"

Since many of these have to be manual/interactive. It makes more sense to make them samples.  What do you think?

Yep, making them samples might be more appropriate and also more useful for users.

@HarshaNalluru thank you so much for going through this!
In all of the languages we support, we try our best to ensure that only one credential needs to be tested from each client's independent tests. This should be fine since they all end up working with AAD, and the services don't vary in their behavior based on which AAD credential their consumers use.
I chatted with you about this already and you pointed out at your experience trying to work with this credentials and how we should provide a better experience for people adopting Identity, and I agree! We can improve documentation-wise just by reading your experience through and ensuring we have more in-depth samples in our code with answers to similar questions. For that reason I've made this issue: https://github.com/Azure/azure-sdk-for-js/issues/13839
I'll close this PR for now! Thank you Harsha!


Add Ruby-based embulk-guess-csv_verify plugin to compare the old Ruby-based CSV guess v.s. the new Java-based CSV guess

This is an "experimental" Ruby-based plugin to compare the old Ruby-based CSV guess v.s. the new Java-reimplemented CSV guess. This as a guess plugin returns the result from the old Ruby-based implementation as its own restult.
With Embulk v0.10.29+ (to be released with this), users should be able to check whether they return the same guess results by a partial configuration like below:
exec:
  exclude_guess_plugins: ['csv']
  guess_plugins: ['csv_verify']
in:
  type: file
  path_prefix: "..."

Thanks!


No output from Hugo

Hi,
I've added hugo to my application. However, I don't have any output from hugo. I am not using retrolambda or similar and I can't identify any potential problem.
Here is my build.gradle from project:
buildscript {
    repositories {
        jcenter()
    }
    dependencies {
        classpath 'com.android.tools.build:gradle:1.5.0'
        classpath 'com.neenbedankt.gradle.plugins:android-apt:1.8'
        classpath 'com.jakewharton.hugo:hugo-plugin:1.2.1'
    }
}

allprojects {
    repositories {
        jcenter()
        maven { url "https://jitpack.io" }
    }
}

task clean(type: Delete) {
    delete rootProject.buildDir
}

and build.gradle from module:
apply plugin: 'com.android.application'
apply plugin: 'com.neenbedankt.android-apt'
apply plugin: 'com.jakewharton.hugo'

android {
    compileSdkVersion 23
    buildToolsVersion "23.0.2"

    defaultConfig {
        applicationId "pl.hydroid.android.podcatcher"
        minSdkVersion 15
        targetSdkVersion 23
        versionCode 1
        versionName "1.0"
    }

    buildTypes {
        release {
            minifyEnabled false
            proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
        }
    }

    packagingOptions {
        exclude 'META-INF/NOTICE.txt'
        exclude 'META-INF/LICENSE.txt'
    }

    dataBinding {
        enabled = true
    }
}

dependencies {
    compile fileTree(dir: 'libs', include: ['*.jar'])
    testCompile 'junit:junit:4.12'
    compile 'com.android.support:appcompat-v7:23.0.1'
    compile 'com.android.support:design:23.0.1'
    compile 'com.android.support:support-v4:23.+'
    compile 'com.google.dagger:dagger:2.0.2'
    apt 'com.google.dagger:dagger-compiler:2.0.2'
    provided 'org.glassfish:javax.annotation:10.0-b28'
    compile 'com.android.support:recyclerview-v7:23.+'
    compile 'org.apache.commons:commons-lang3:3.4'
    compile 'joda-time:joda-time:2.8.+'
    compile 'com.squareup.retrofit:retrofit:1.9.0'
    compile 'com.squareup.okhttp:okhttp-urlconnection:2.0.0'
    compile 'com.squareup.okhttp:okhttp:2.0.0'
    compile 'com.jakewharton:butterknife:7.+'
    compile 'com.marshalchen.ultimaterecyclerview:library:+'
    compile 'com.android.support:cardview-v7:23.+'
    compile 'com.facebook.fresco:fresco:0.9.+'
    compile 'com.github.dmytrodanylyk:android-morphing-button:e271da6fd524d8f8855d1016d72f6b69dfcbae8c'
}

All required elements of hugo are present, so I don't know what might be problematic here.

I'm having the same issue, configured everything as documented, but don't see any output. So +1 for this issue.

1.Do you use a debug build?
2. Do you use it with other Annotation?

@tinybright, to answer your questions for my project

Yes, I use a debug build.
Other libs I use annotations for in my project: Realm, Retrofit, OkHttp.

Can you provide a screenshot of your logcat?

See these two screenshots. What are you expecting to see in the logcatscreen?

 Indeed didn't put logging to verbose. Thank you!
@connexion2000: Don't know if this 'solved' your problem, if not: sorry for hijacking your thread..

I'm having the same issue, configured everything as documented, but don't see any output about hugo. I have put put logging to verbose,it is useless。please help me...


“Class Relationships” integrity check doesn’t take account for sub-types

“Class Relationships” integrity check doesn’t take account for sub-types

There are currently 29 relationship failures in each branch:

These are sub types so need removing before we migrate.

I don't think this is fixed as there are still 29 issues:

This will work on any of the DD versions that I've previously imported.  It won't work on the existing branches because of a branching issue which is now resolved.  It will work on any new branches created, and when we re-create the test branches, it'll work on those too.

Will be tested when we have new models / branches.

I checked the March 2022 release and there is now only one that has failed:

@jamesrwelch - this looks the same in Together as other similar items such, Nurse and Midwife. Do you have any idea why this has failed?
Now the failures have reduced from 29 to 1, I am happy to say this is fixed. We just need to understand how to fix OPTOMETRIST. I will speak to James about this.


Latest release is 4.0.0 from February

(First of all, thanks to all who contribute to this awesome library!)
Not sure if I'm missing something but the latest release is 4.0.0 which is quite old. Is it expected that people use master in general? Or is it common to use the latest release?
Thanks

I use master ;)
I tend to release when master has really diverged or has taken breaking changes. I am open to changes in the release process.
Thanks!


Error in EQRS calculation for updated oxygen debt indicator

The updated the configuration file for 2016-2021 with the corrected oxygen debt results (with now missing results for 2020 and 2021 as no nitrogen data are available for these years) is not producing the EQRS values. The EQRS calculation works OK with the full results (i.e. with 2020 and 2021 ES included). I am not getting any errors in R for this, but the EQRS value and maps for this indicator are simply blank. If these work for you @HjalteParner , I'll need to look where the error stems from at my end.

@Ikaikkonen, issue has been resolved now by deleting the 2020 and 2021 empty results mistakenly (by me) reported in the default configuration file.


Add permissions for github-autostatus plugin

Description
Adding permission for new plugin hosted at https://github.com/jenkinsci/github-autostatus-plugin, hosting request https://issues.jenkins-ci.org/browse/HOSTING-435

Submitter checklist for changing permissions

Always

[x] Add link to plugin/component Git repository in description above

For a newly hosted plugin only

[x] Add link to resolved HOSTING issue in description above

For a new permissions file only

[x] Make sure the file is created in permissions/ directory
[x] artifactId (pom.xml) is used for name (permissions YAML file).
[x] groupId / artifactId (pom.xml) are correctly represented in path (permissions YAML file)
[x] Check that the file is named plugin-${artifactId}.yml for plugins

When adding new uploaders (this includes newly created permissions files)

[ ] Make sure to @mention an existing maintainer to confirm the permissions request, if applicable
[x] Use the Jenkins community (LDAP) account name in the YAML file, not the GitHub account name
[x] All newly added users have logged in to Artifactory at least once

@jenkinsci/hacktoberfest


Ethernet OTA error when image file size is larger than hollow-word.bin (IDFGH-2016)

Environment

Development Kit:      [ESP32-Ethernet-kit-A]
Kit version (for WroverKit/PicoKit/DevKitC): [v1.1]
Module or chip used:  [ESP32-WROVER-B]
IDF version (run git describe --tags to find it):
v4.0-beta1-180-ga21eb04cc
Build System:         [Make]
Compiler version (run xtensa-esp32-elf-gcc --version to find it):
xtensa-esp32-elf-gcc (crosstool-NG esp32-2019r1) 8.2.0
Operating System:     [Linux]
Power Supply:         [USB]

Problem Description
Hi
I added OTA features to my esp32 ethernet project and have a problems I have installed the Ethernet driver correctly and got the local IP (DHCP succeeded)):
When I use Hello word.bin (file size is 150kb), I can successfully implement OTA(Almost every test was a success), however when I use my own project's .bin file (file size is 1.2MB),  OTA  always failed and  always return the errors :
[15:05:53:726] <0x1b>[0;32mI (1085052) esp_https_ota: Starting OTA...<0x1b>[0m␍␊
[15:05:53:726] <0x1b>[0;32mI (1085052) esp_https_ota: Writing to partition subtype 17 at offset 0x200000<0x1b>[0m␍␊
[15:06:33:788] <0x1b>[0;31mE (1125122) esp-tls: read error :-76:<0x1b>[0m␍␊
[15:06:33:804] <0x1b>[0;31mE (1125122) TRANS_SSL: esp_tls_conn_read error, errno=No more processes<0x1b>[0m␍␊
[15:06:38:860] <0x1b>[0;32mI (1130182) esp_https_ota: Connection closed, all data received<0x1b>[0m␍␊
[15:06:38:860] <0x1b>[0;32mI (1130182) esp_image: segment 0: paddr=0x00200020 vaddr=0x3f400020 size=0x33b7c (211836) map<0x1b>[0m␍␊
[15:06:38:988] <0x1b>[0;32mI (1130302) esp_image: segment 1: paddr=0x00233ba4 vaddr=0x3ffbdb60 size=0x03858 ( 14424) <0x1b>[0m␍␊
[15:06:38:988] <0x1b>[0;32mI (1130312) esp_image: segment 2: paddr=0x00237404 vaddr=0x40080000 size=0x00400 (  1024) <0x1b>[0m␍␊
[15:06:39:004] <0x1b>[0;32mI (1130312) esp_image: segment 3: paddr=0x0023780c vaddr=0x40080400 size=0x08804 ( 34820) <0x1b>[0m␍␊
[15:06:39:020] <0x1b>[0;31mE (1130342) esp_image: invalid segment length 0xffffffff<0x1b>[0m␍␊
[15:06:39:020] <0x1b>[0;31mE (1130342) main: Firmware Upgrades Failed 5379, 0x00001503<0x1b>[0m␍␊
[15:06:39:036] <0x1b>[0;31mE (1130342) main: ota 1st fail!,again<0x1b>

Same hardware, same server, different image file sizes,the small image can succeed, but the larger image is not successful, so I guess this is not the HTTP server fault, but the defect of ESP IDF.
I made more tests to test my conjecture, to switch the network mode to WiFi STA, retest the OTA, and compare the two images:

hollow-word.bin(150KB)   Test 5 times, successful 5 .
myself.bin(1.2MB)   Test 5 times, successful 1 .

I'd like to know if you have tested the OTA when the firmware size is larger than hello word.bin (for example, the image size is larger than 1.5 MB).In particular, have you tested the OTA situation when using ip101(ethernet mode) for network communication?

HI,
I have solved this problem. There should be a problem with the default settings of ESP IDF.
Thanks！

Hi @aa1622296203 ,
Glad you found a fix.

There should be a problem with the default settings of ESP IDF.

Can you explain what setting you had to change to make this work?
We have seen reports of similar errors when the server truncated the file (ie did not send all bytes).
Angus

Use larger DMA buffer,default is 512 Bytes ,change to 2048,itworks well

not 2048, 1600 is correct

Hi @aa1622296203 ,
can you explain how to change the DMA buffer size using arduino.

i am also trying to doing ota using ethernet its working with wifi but not working with ethernet, below are the logs can you suggest some soultion
E (395143) esp-tls: couldn't get hostname for :beta.alitersolutions.com:
E (395143) esp-tls: Failed to open new connection
E (395153) TRANS_SSL: Failed to open a new connection
E (395153) HTTP_CLIENT: Connection failed, sock < 0
E (395163) esp_https_ota: Failed to open HTTP connection: ESP_ERR_HTTP_CONNECT
E (395173) esp_https_ota: Failed to establish HTTP connection


ValueError: invalid literal for int() with base 10:

Getting this in line 39:
running USER_ID = int(os.environ.get('TELEGRAM_USER_ID'))
I presume I am entering the telegram user ID incorrectly. Is there a specific format we need to enter the user ID in?

It's strange, when you print(USER_ID), it seems to be correct, but the bot will authorize if you hardcode it with your id.
USER_ID = 4564656

is there a way to authorize multiple users?


🐛 | Status LED is not switched on

Bug
What I did
I installed the raspberry pi with above mentioned buster image and ran the installer script
Later-on, I re-ran the installation to have GPIO service enabled.
What happened
There is no voltage between a GND pin and pin 32.
I expected this to happen
Pin 32, according the https://github.com/MiczFlor/RPi-Jukebox-RFID/wiki/Using-GPIO-hardware-status-led is said to be lit as soon as the Pi is booted an supported out of the box.
However, this is not the case: between pins 32 and 30, there is 0 V.
Further information that might help
I am able to get 3,3V between pin 32 and GND when I activate the pin manually, like so:
import RPi.GPIO as GPIO
GPIO.setmode(GPIO.BOARD)
GPIO.setup(32, GPIO.OUT)
GPIO.output(32, 1)

Software
Base image and version
2020-12-02-raspios-buster-armhf-lite
PRETTY_NAME="Raspbian GNU/Linux 10 (buster)"
NAME="Raspbian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"
Branch / Release
master
Installscript
scripts/installscripts/buster-install-default.sh
Hardware
OnOffShim with unmodified standard installation
RaspberryPi version
3 B+
RFID Reader
ID 413d:2107
Soundcard
ID 8086:0808 Intel Corp.
  iManufacturer           1 C-Media Electronics Inc.
  iProduct                2 USB PnP Sound Device

Other notable hardware
Note: the Github issue template says:
i.e. post your GPIO pin settings from `RPi-Jukebox-RFID/scripts/gpio-buttons.py`:

This file is missing on my Pi, as it is also in the current git master.

Since 2.1 we use GPIO control, unfortunately the wiki page for status LED is not updated yet.
please check the description and see here https://github.com/MiczFlor/RPi-Jukebox-RFID/blob/develop/components/gpio_control/example_configs/gpio_settings_rotary_and_led.ini for examples.

Using GPIO control, it works as expected. Thanks!