http: proxy error: context canceled

I've been seeing this error http: proxy error: context canceled crop up when I run a test.  The tests even pass.  I'm just wondering why it pops up
selenoid_1     | 2018/10/31 18:32:17 [-] [NEW_REQUEST] [unknown] [<IP_ADDRESS>]
selenoid_1     | 2018/10/31 18:32:17 [-] [NEW_REQUEST_ACCEPTED] [unknown] [<IP_ADDRESS>]
selenoid_1     | 2018/10/31 18:32:17 [9150] [LOCATING_SERVICE] [chrome] [69.0]
selenoid_1     | 2018/10/31 18:32:17 [9150] [USING_DOCKER] [chrome] [69.0]
selenoid_1     | 2018/10/31 18:32:17 [9150] [CREATING_CONTAINER] [selenoid/chrome:69.0]
selenoid_1     | 2018/10/31 18:32:17 [-] [NEW_REQUEST] [unknown] [<IP_ADDRESS>]
selenoid_1     | 2018/10/31 18:32:17 [-] [NEW_REQUEST_ACCEPTED] [unknown] [<IP_ADDRESS>]
selenoid_1     | 2018/10/31 18:32:17 [9151] [LOCATING_SERVICE] [chrome] [69.0]
selenoid_1     | 2018/10/31 18:32:17 [9151] [USING_DOCKER] [chrome] [69.0]
selenoid_1     | 2018/10/31 18:32:17 [9151] [CREATING_CONTAINER] [selenoid/chrome:69.0]
selenoid_1     | 2018/10/31 18:32:17 [-] [NEW_REQUEST] [unknown] [<IP_ADDRESS>]
selenoid_1     | 2018/10/31 18:32:17 [-] [NEW_REQUEST_ACCEPTED] [unknown] [<IP_ADDRESS>]
selenoid_1     | 2018/10/31 18:32:17 [-] [NEW_REQUEST] [unknown] [<IP_ADDRESS>]
selenoid_1     | 2018/10/31 18:32:17 [-] [NEW_REQUEST_ACCEPTED] [unknown] [<IP_ADDRESS>]
selenoid_1     | 2018/10/31 18:32:17 [9152] [LOCATING_SERVICE] [chrome] [69.0]
selenoid_1     | 2018/10/31 18:32:17 [9152] [USING_DOCKER] [chrome] [69.0]
selenoid_1     | 2018/10/31 18:32:17 [9152] [CREATING_CONTAINER] [selenoid/chrome:69.0]
selenoid_1     | 2018/10/31 18:32:17 [9153] [LOCATING_SERVICE] [chrome] [69.0]
selenoid_1     | 2018/10/31 18:32:17 [9153] [USING_DOCKER] [chrome] [69.0]
selenoid_1     | 2018/10/31 18:32:17 [9153] [CREATING_CONTAINER] [selenoid/chrome:69.0]
selenoid_1     | 2018/10/31 18:32:17 [-] [NEW_REQUEST] [unknown] [<IP_ADDRESS>]
selenoid_1     | 2018/10/31 18:32:17 [-] [NEW_REQUEST_ACCEPTED] [unknown] [<IP_ADDRESS>]
selenoid_1     | 2018/10/31 18:32:17 [9154] [LOCATING_SERVICE] [chrome] [69.0]
selenoid_1     | 2018/10/31 18:32:17 [9154] [USING_DOCKER] [chrome] [69.0]
selenoid_1     | 2018/10/31 18:32:17 [9154] [CREATING_CONTAINER] [selenoid/chrome:69.0]
selenoid_1     | 2018/10/31 18:32:17 [-] [NEW_REQUEST] [unknown] [<IP_ADDRESS>]
selenoid_1     | 2018/10/31 18:32:17 [-] [NEW_REQUEST_ACCEPTED] [unknown] [<IP_ADDRESS>]
selenoid_1     | 2018/10/31 18:32:17 [9155] [LOCATING_SERVICE] [chrome] [69.0]
selenoid_1     | 2018/10/31 18:32:17 [9155] [USING_DOCKER] [chrome] [69.0]
selenoid_1     | 2018/10/31 18:32:17 [-] [NEW_REQUEST] [unknown] [<IP_ADDRESS>]
selenoid_1     | 2018/10/31 18:32:17 [-] [NEW_REQUEST_ACCEPTED] [unknown] [<IP_ADDRESS>]
selenoid_1     | 2018/10/31 18:32:17 [9156] [LOCATING_SERVICE] [chrome] [69.0]
selenoid_1     | 2018/10/31 18:32:17 [9155] [CREATING_CONTAINER] [selenoid/chrome:69.0]
selenoid_1     | 2018/10/31 18:32:17 [9156] [USING_DOCKER] [chrome] [69.0]
selenoid_1     | 2018/10/31 18:32:17 [9156] [CREATING_CONTAINER] [selenoid/chrome:69.0]
selenoid_1     | 2018/10/31 18:32:17 [9150] [STARTING_CONTAINER] [selenoid/chrome:69.0] [fdca096a393f0aabdb47ca3d81888ced6e70060bed78fb005769fdf445fbafaf]
selenoid_1     | 2018/10/31 18:32:18 [9151] [STARTING_CONTAINER] [selenoid/chrome:69.0] [4343aed76b0ecf099255bb344f5042cb0d2b1bb305f63a02d6fbe1780aa925f7]
selenoid_1     | 2018/10/31 18:32:18 [9152] [STARTING_CONTAINER] [selenoid/chrome:69.0] [11773aba44b9de304409e341c6266b1403ef0657ab60ac574f0548691208dee9]
selenoid_1     | 2018/10/31 18:32:18 [9153] [STARTING_CONTAINER] [selenoid/chrome:69.0] [972e378176f60e7af0f8d721f12552aa14a50ba15deb9f215a1eb0e536401e2c]
selenoid_1     | 2018/10/31 18:32:18 [9154] [STARTING_CONTAINER] [selenoid/chrome:69.0] [b9322352203f624b5fc2485f75f8a86aa04b1aa45781c26790ec7dd9ecd144e3]
selenoid_1     | 2018/10/31 18:32:18 [9155] [STARTING_CONTAINER] [selenoid/chrome:69.0] [ed9f2d802084d0d2ffa54f0c68a3e083c295f62ffefbf398aa9020354ef3bce3]
selenoid_1     | 2018/10/31 18:32:18 [9156] [STARTING_CONTAINER] [selenoid/chrome:69.0] [72e3cb20ed9b60235729a952db1c0fc814777aec343d3ff37b0ee49e95d9a422]
selenoid_1     | 2018/10/31 18:32:18 [9150] [CONTAINER_STARTED] [selenoid/chrome:69.0] [fdca096a393f0aabdb47ca3d81888ced6e70060bed78fb005769fdf445fbafaf] [0.35s]
selenoid_1     | 2018/10/31 18:32:18 [9151] [CONTAINER_STARTED] [selenoid/chrome:69.0] [4343aed76b0ecf099255bb344f5042cb0d2b1bb305f63a02d6fbe1780aa925f7] [0.40s]
selenoid_1     | 2018/10/31 18:32:18 [9150] [SERVICE_STARTED] [selenoid/chrome:69.0] [fdca096a393f0aabdb47ca3d81888ced6e70060bed78fb005769fdf445fbafaf] [0.10s]
selenoid_1     | 2018/10/31 18:32:18 [9150] [PROXY_TO] [fdca096a393f0aabdb47ca3d81888ced6e70060bed78fb005769fdf445fbafaf] [http://<IP_ADDRESS>:4444/]
selenoid_1     | 2018/10/31 18:32:18 [9150] [SESSION_ATTEMPTED] [http://<IP_ADDRESS>:4444/] [1]
selenoid_1     | 2018/10/31 18:32:18 [9151] [SERVICE_STARTED] [selenoid/chrome:69.0] [4343aed76b0ecf099255bb344f5042cb0d2b1bb305f63a02d6fbe1780aa925f7] [0.10s]
selenoid_1     | 2018/10/31 18:32:18 [9151] [PROXY_TO] [4343aed76b0ecf099255bb344f5042cb0d2b1bb305f63a02d6fbe1780aa925f7] [http://<IP_ADDRESS>:4444/]
selenoid_1     | 2018/10/31 18:32:18 [9151] [SESSION_ATTEMPTED] [http://<IP_ADDRESS>:4444/] [1]
selenoid_1     | 2018/10/31 18:32:18 [9152] [CONTAINER_STARTED] [selenoid/chrome:69.0] [11773aba44b9de304409e341c6266b1403ef0657ab60ac574f0548691208dee9] [0.63s]
selenoid_1     | 2018/10/31 18:32:18 [9153] [CONTAINER_STARTED] [selenoid/chrome:69.0] [972e378176f60e7af0f8d721f12552aa14a50ba15deb9f215a1eb0e536401e2c] [0.76s]
selenoid_1     | 2018/10/31 18:32:18 [9152] [SERVICE_STARTED] [selenoid/chrome:69.0] [11773aba44b9de304409e341c6266b1403ef0657ab60ac574f0548691208dee9] [0.21s]
selenoid_1     | 2018/10/31 18:32:18 [9152] [PROXY_TO] [11773aba44b9de304409e341c6266b1403ef0657ab60ac574f0548691208dee9] [http://<IP_ADDRESS>:4444/]
selenoid_1     | 2018/10/31 18:32:18 [9152] [SESSION_ATTEMPTED] [http://<IP_ADDRESS>:4444/] [1]
selenoid_1     | 2018/10/31 18:32:19 [9153] [SERVICE_STARTED] [selenoid/chrome:69.0] [972e378176f60e7af0f8d721f12552aa14a50ba15deb9f215a1eb0e536401e2c] [0.11s]
selenoid_1     | 2018/10/31 18:32:19 [9153] [PROXY_TO] [972e378176f60e7af0f8d721f12552aa14a50ba15deb9f215a1eb0e536401e2c] [http://<IP_ADDRESS>:4444/]
selenoid_1     | 2018/10/31 18:32:19 [9153] [SESSION_ATTEMPTED] [http://<IP_ADDRESS>:4444/] [1]
selenoid_1     | 2018/10/31 18:32:19 [9154] [CONTAINER_STARTED] [selenoid/chrome:69.0] [b9322352203f624b5fc2485f75f8a86aa04b1aa45781c26790ec7dd9ecd144e3] [0.86s]
selenoid_1     | 2018/10/31 18:32:19 [9154] [SERVICE_STARTED] [selenoid/chrome:69.0] [b9322352203f624b5fc2485f75f8a86aa04b1aa45781c26790ec7dd9ecd144e3] [0.05s]
selenoid_1     | 2018/10/31 18:32:19 [9154] [PROXY_TO] [b9322352203f624b5fc2485f75f8a86aa04b1aa45781c26790ec7dd9ecd144e3] [http://<IP_ADDRESS>:4444/]
selenoid_1     | 2018/10/31 18:32:19 [9154] [SESSION_ATTEMPTED] [http://<IP_ADDRESS>:4444/] [1]
selenoid_1     | 2018/10/31 18:32:19 [9156] [CONTAINER_STARTED] [selenoid/chrome:69.0] [72e3cb20ed9b60235729a952db1c0fc814777aec343d3ff37b0ee49e95d9a422] [1.10s]
selenoid_1     | 2018/10/31 18:32:19 [9155] [CONTAINER_STARTED] [selenoid/chrome:69.0] [ed9f2d802084d0d2ffa54f0c68a3e083c295f62ffefbf398aa9020354ef3bce3] [1.32s]
selenoid_1     | 2018/10/31 18:32:19 [9156] [SERVICE_STARTED] [selenoid/chrome:69.0] [72e3cb20ed9b60235729a952db1c0fc814777aec343d3ff37b0ee49e95d9a422] [0.30s]
selenoid_1     | 2018/10/31 18:32:19 [9156] [PROXY_TO] [72e3cb20ed9b60235729a952db1c0fc814777aec343d3ff37b0ee49e95d9a422] [http://<IP_ADDRESS>:4444/]
selenoid_1     | 2018/10/31 18:32:19 [9156] [SESSION_ATTEMPTED] [http://<IP_ADDRESS>:4444/] [1]
selenoid_1     | 2018/10/31 18:32:19 [9155] [SERVICE_STARTED] [selenoid/chrome:69.0] [ed9f2d802084d0d2ffa54f0c68a3e083c295f62ffefbf398aa9020354ef3bce3] [0.23s]
selenoid_1     | 2018/10/31 18:32:19 [9155] [PROXY_TO] [ed9f2d802084d0d2ffa54f0c68a3e083c295f62ffefbf398aa9020354ef3bce3] [http://<IP_ADDRESS>:4444/]
selenoid_1     | 2018/10/31 18:32:19 [9155] [SESSION_ATTEMPTED] [http://<IP_ADDRESS>:4444/] [1]
selenoid_1     | 2018/10/31 18:32:20 [9150] [SESSION_CREATED] [f36e785e40155fe500e275681b4aafa2] [1] [2.50s]
selenoid_1     | 2018/10/31 18:32:20 [9151] [SESSION_CREATED] [1f22925fb3de33909023a37e90bd4acf] [1] [2.55s]
selenoid_1     | 2018/10/31 18:32:21 [9152] [SESSION_CREATED] [5e767156b386700d943c16bec39d347f] [1] [3.73s]
selenoid_1     | 2018/10/31 18:32:21 [9154] [SESSION_CREATED] [fccfa9adda9974fd705bae4fc7f07c22] [1] [3.80s]
selenoid_1     | 2018/10/31 18:32:21 [9153] [SESSION_CREATED] [3c73c9c7b25705bb3abb2dd27c75d76d] [1] [3.86s]
selenoid_1     | 2018/10/31 18:32:22 [9156] [SESSION_CREATED] [1224943a6af7aa3b4a253dba1ffd50e0] [1] [4.62s]
selenoid_1     | 2018/10/31 18:32:22 [9155] [SESSION_CREATED] [ebdc32022ac982b93a4b8d0793627f4f] [1] [4.69s]
selenoid_1     | 2018/10/31 18:33:03 http: proxy error: context canceled
selenoid_1     | 2018/10/31 18:33:13 http: proxy error: context canceled
selenoid_1     | 2018/10/31 18:33:34 http: proxy error: context canceled
selenoid_1     | 2018/10/31 18:33:48 http: proxy error: context canceled
selenoid_1     | 2018/10/31 18:33:50 http: proxy error: context canceled
selenoid_1     | 2018/10/31 18:34:32 http: proxy error: context canceled
selenoid_1     | 2018/10/31 18:35:02 http: proxy error: context canceled
selenoid_1     | 2018/10/31 18:35:23 http: proxy error: context canceled
selenoid_1     | 2018/10/31 18:35:24 http: proxy error: context canceled
selenoid_1     | 2018/10/31 18:35:35 http: proxy error: context canceled
selenoid_1     | 2018/10/31 18:35:40 [16520] [SESSION_DELETED] [1f22925fb3de33909023a37e90bd4acf]
selenoid_1     | 2018/10/31 18:35:41 [9151] [REMOVING_CONTAINER] [4343aed76b0ecf099255bb344f5042cb0d2b1bb305f63a02d6fbe1780aa925f7]
selenoid_1     | 2018/10/31 18:35:42 [9151] [CONTAINER_REMOVED] [4343aed76b0ecf099255bb344f5042cb0d2b1bb305f63a02d6fbe1780aa925f7]
selenoid_1     | 2018/10/31 18:35:49 [16873] [SESSION_DELETED] [fccfa9adda9974fd705bae4fc7f07c22]
selenoid_1     | 2018/10/31 18:35:49 [9154] [REMOVING_CONTAINER] [b9322352203f624b5fc2485f75f8a86aa04b1aa45781c26790ec7dd9ecd144e3]
selenoid_1     | 2018/10/31 18:35:50 [16883] [SESSION_DELETED] [5e767156b386700d943c16bec39d347f]
selenoid_1     | 2018/10/31 18:35:50 [9152] [REMOVING_CONTAINER] [11773aba44b9de304409e341c6266b1403ef0657ab60ac574f0548691208dee9]
selenoid_1     | 2018/10/31 18:35:51 [9154] [CONTAINER_REMOVED] [b9322352203f624b5fc2485f75f8a86aa04b1aa45781c26790ec7dd9ecd144e3]
selenoid_1     | 2018/10/31 18:35:51 [9152] [CONTAINER_REMOVED] [11773aba44b9de304409e341c6266b1403ef0657ab60ac574f0548691208dee9]
selenoid_1     | 2018/10/31 18:35:54 [17032] [SESSION_DELETED] [ebdc32022ac982b93a4b8d0793627f4f]
selenoid_1     | 2018/10/31 18:35:54 [9155] [REMOVING_CONTAINER] [ed9f2d802084d0d2ffa54f0c68a3e083c295f62ffefbf398aa9020354ef3bce3]
selenoid_1     | 2018/10/31 18:35:55 [9155] [CONTAINER_REMOVED] [ed9f2d802084d0d2ffa54f0c68a3e083c295f62ffefbf398aa9020354ef3bce3]
selenoid_1     | 2018/10/31 18:35:55 [17073] [SESSION_DELETED] [f36e785e40155fe500e275681b4aafa2]
selenoid_1     | 2018/10/31 18:35:55 [9150] [REMOVING_CONTAINER] [fdca096a393f0aabdb47ca3d81888ced6e70060bed78fb005769fdf445fbafaf]
selenoid_1     | 2018/10/31 18:35:57 [9150] [CONTAINER_REMOVED] [fdca096a393f0aabdb47ca3d81888ced6e70060bed78fb005769fdf445fbafaf]
selenoid_1     | 2018/10/31 18:35:59 [17138] [SESSION_DELETED] [1224943a6af7aa3b4a253dba1ffd50e0]
selenoid_1     | 2018/10/31 18:35:59 [9156] [REMOVING_CONTAINER] [72e3cb20ed9b60235729a952db1c0fc814777aec343d3ff37b0ee49e95d9a422]
selenoid_1     | 2018/10/31 18:36:00 [9156] [CONTAINER_REMOVED] [72e3cb20ed9b60235729a952db1c0fc814777aec343d3ff37b0ee49e95d9a422]
selenoid_1     | 2018/10/31 18:36:06 [17260] [SESSION_DELETED] [3c73c9c7b25705bb3abb2dd27c75d76d]
selenoid_1     | 2018/10/31 18:36:07 [9153] [REMOVING_CONTAINER] [972e378176f60e7af0f8d721f12552aa14a50ba15deb9f215a1eb0e536401e2c]
selenoid_1     | 2018/10/31 18:36:07 [9153] [CONTAINER_REMOVED] [972e378176f60e7af0f8d721f12552aa14a50ba15deb9f215a1eb0e536401e2c]

Running on Mac OS High Sierra, dockerized selenoid aerokube/selenoid:1.8.0, using docker compose

@snackattas that means "client disconnected". Not sure whether we can suppress this message (it comes from Golang standard library).

Is it any cause for alarm? Or is it then a standard, run of the mill error?

Oops closed by accident

@snackattas I don't see any SESSION_TIMED_OUT messages in your log but this could be a signal that your tests disconnect from Selenoid during test run. Normally in that case you should have broken tests and somewhere later in Selenoid log (depending on -timeout flag value) there should be [SESSION_TIMED_OUT] lines.

Yes, there were no SESSION_TIMED_OUT messages, and the tests still did pass.  But a subsequent run did not pass.  I do have the -timeout set to 3 minutes, thats perhaps why it fails inconsistently.
But as to the reason it happens, it's because

@snackattas I would take a look at host system metrics such as load average, memory usage and disk usage (including iowait).

@vania-pooh Did you figure out any way to silence the message? I'm having similar issues on my own project (unrelated from selenoid) and starting to realize that it's probably not harmful -- albeit pretty annoying to see in the logs daily.

@HaraldNordgren you have to override the following ReverseProxy field:
	// ErrorHandler is an optional function that handles errors
	// reaching the backend or errors from ModifyResponse.
	//
	// If nil, the default is to log the provided error and return
	// a 502 Status Bad Gateway response.
	ErrorHandler func(http.ResponseWriter, *http.Request, error)

Btw, let's do this for Selenoid and close the issue.


Revert "Concurrent Append (#10279)"

/azp run automation - sdk

Can one of the admins verify this patch?


Changes being committed for #2071

Description
Updated code to display the proper error message when invalid arguments provided.
Bug Tiltle : Error and Help message for incorrect args need to be improved
#2071
https://github.com/microsoft/vstest/issues/2071

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: DineshChirnanchu sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


[BUG] Upgrade v1.2.1->v1.2.2 stuck at Pre-drained node due to certificates expiration

Describe the bug

To Reproduce
Steps to reproduce the behavior:

Upgrade harvester from v1.2.1 to v1.2.2

Expected behavior

Cluster should be upgraded successfully
Support bundle

hvst-upgrade-hjw2p-upgradelog-archive-2024-05-17T07-59-36Z.zip
Environment

Harvester ISO version: v1.2.2
Underlying Infrastructure (e.g. Baremetal with Dell PowerEdge R630): Baremetal with Dell PowerEdge R730

Additional context
Add any other context about the problem here.

@ibrokethecloud noticing:
Already installed harvester-seeder
+ [[ helm_v3 == \h\e\l\m\_\v\3 ]]
+ helm_v3 mapkubeapis harvester-seeder --namespace harvester-system
2024/05/17 07:20:28 Release 'harvester-seeder' will be checked for deprecated or removed Kubernetes APIs and will be updated if necessary to supported API versions.
2024/05/17 07:20:28 Get release 'harvester-seeder' latest version.
2024/05/17 07:20:28 Check release 'harvester-seeder' for deprecated or removed APIs...
2024/05/17 07:20:28 Finished checking release 'harvester-seeder' for deprecated or removed APIs.
2024/05/17 07:20:28 Release 'harvester-seeder' has no deprecated or removed APIs.
2024/05/17 07:20:28 Map of release 'harvester-seeder' deprecated or removed APIs to supported versions, completed successfully.
+ echo 'Upgrading helm_v3 chart'
+ echo 'Upgrading harvester-seeder'
+ shift 1
Upgrading harvester-seeder
+ helm_v3 upgrade --repo http://harvester-cluster-repo.cattle-system.svc/charts --version 0.1.0 harvester-seeder harvester-seeder --values /config/values-01_HelmChart.yaml
Error: chart "harvester-seeder" version "0.1.0" not found in http://harvester-cluster-repo.cattle-system.svc/charts repository

Specifically, the error about 6/7 times in: harvester-system.helm-install-harvester-seeder-9gccc.helm.20240517.log (extracted from .gz)
But the pre-drain on dc-0 looks to be successful:
nvim harvester-system.hvst-upgrade-hjw2p-pre-drain-harvester-dc-0-xsdr2.apply.20240517.log

With the tail-end being:
Volume pvc-bf6c793f-7597-4dcb-9842-a9e862d05d72 is healthy.
Checking running engine pvc-fd1960b3-ef2c-4bcb-9c45-72322945648a-e-ec25015f...
+ echo Checking running engine pvc-fd1960b3-ef2c-4bcb-9c45-72322945648a-e-ec25015f...
+ '[' true ']'
+ '[' 4 -gt 2 ']'
++ kubectl get volumes.longhorn.io/pvc-fd1960b3-ef2c-4bcb-9c45-72322945648a -n longhorn-system -o 'jsonpath={.status.robustness}'
+ robustness=healthy
+ '[' healthy = healthy ']'
+ echo 'Volume pvc-fd1960b3-ef2c-4bcb-9c45-72322945648a is healthy.'
Volume pvc-fd1960b3-ef2c-4bcb-9c45-72322945648a is healthy.
+ break
+ read -r lh_engine lh_volume
+ upgrade-helper vm-live-migrate-detector harvester-dc-0 --shutdown
time="2024-05-17T07:14:02Z" level=info msg="Starting VM Live Migrate Detector"
time="2024-05-17T07:14:02Z" level=info msg="Non-migratable VM(s): []"
+ kubectl taint node harvester-dc-0 --overwrite kubevirt.io/drain=draining:NoSchedule
node/harvester-dc-0 modified
+ wait_vms_out_or_shutdown
+ local vm_count
+ '[' true ']'
++ get_running_vm_count
++ local vmioutput=/tmp/vmioutput.yaml
++ rm -f /tmp/vmioutput.yaml
++ local EXIT_CODE=0
++ kubectl get vmi -A -l kubevirt.io/nodeName=harvester-dc-0 -o yaml
++ [[ 0 -eq 0 ]]
+++ yq e '.items |  map(select(.status.phase!="Succeeded")) | length' /tmp/vmioutput.yaml
++ local count=0
++ echo 0
++ rm -f /tmp/vmioutput.yaml
+ vm_count=0
+ '[' 0 = 0 ']'
+ break
+ echo 'all VMs on node harvester-dc-0 have been live-migrated or shutdown'
+ wait_evacuation_pdb_gone
all VMs on node harvester-dc-0 have been live-migrated or shutdown
+ kubectl get pdb -o name -A
+ grep kubevirt-migration-pdb-kubevirt-evacuation-
+ patch_logging_event_audit
+ detect_upgrade
++ kubectl get upgrades.harvesterhci.io hvst-upgrade-hjw2p -n harvester-system -o yaml
+ upgrade_obj='apiVersion: harvesterhci.io/v1beta1

Hi @W0n9,
Could you also generate a support bundle for investigation?
Ref: https://docs.harvesterhci.io/v1.2/troubleshooting/harvester/#generate-a-support-bundle

Here is my support bundle @Vicente-Cheng
Yesterday, after upgrade failed:
supportbundle_7e8aefe3-479a-4fa4-97d8-af2f283e4577_2024-05-17T09-01-49Z.001.zip
supportbundle_7e8aefe3-479a-4fa4-97d8-af2f283e4577_2024-05-17T09-01-49Z.002.zip
Today, after some fix but failed again:
supportbundle_7e8aefe3-479a-4fa4-97d8-af2f283e4577_2024-05-18T02-54-16Z.001.zip
supportbundle_7e8aefe3-479a-4fa4-97d8-af2f283e4577_2024-05-18T02-54-16Z.002.zip

Hi @W0n9,
Could you also provide the command to unzip this?
I use 7-zip, but it looks like it is not correct.
If the SB is too large to upload, you could send the bundle to<EMAIL_ADDRESS>with this issue ID.
Thanks!

Hi, @Vicente-Cheng
You can try to rename it from file_name.001.zip to file_name.zip.001 .
Or I send the e-mail to you later.

Hi @W0n9, I couldn't find any YAML files in the support bundle files you provided, so it's hard to determine the cluster's precise state. Did you ever change the support-bundle-namespaces setting before generating the support bundle file?
Under the Advanced -> Settings page of the dashboard:

Please also help provide the Upgrade and Setting CRs. You could run the following commands and get the output:
kubectl -n harvester-system get upgrades.harvesterhci -o yaml
kubectl get settings.harvesterhci -o yaml

From the rancher logs (supportbundle_7e8aefe3-479a-4fa4-97d8-af2f283e4577_2024-05-17T09-01-49Z/logs/cattle-system/rancher-654c45c575-zrmkv/rancher.log) we found the following line was repeated again and again:
024-05-17T08:55:00.616288694Z 2024/05/17 08:55:00 [INFO] [planner] rkecluster fleet-local/local: configuring bootstrap node(s) custom-fb4dda4acb64: waiting for probes: kube-controller-manager, kube-scheduler

It might be related to certificates expiration. Perhaps you could check if this works for you. Thanks.

Hi @W0n9,
Could you also check the suggestion from @starbops

It might be related to certificates expiration. Perhaps you could check if https://github.com/harvester/harvester/issues/3863#issuecomment-1539681311 works for you. Thanks.

Hi @Vicente-Cheng ,
I have tried https://github.com/harvester/harvester/issues/3863#issuecomment-1539681311 in my 2 long-running harvester cluster, and it works.
Thanks

cert rotate is implemented in v1.3.0, @starbops can you help add this (https://docs.harvesterhci.io/v1.3/upgrade/v1-1-2-to-v1-2-0#7-upgrade-stuck-in-the-upgrading-system-service-state) and seeder one to the known issue sections of 1.2.2 upgrade page? Thanks.

Close the issue as #harvester/docs#585 has been merged. Thank you.


autodetect IP address on the best route to cluster master

this make calico autodetect the correct interface to announce BGP changes. Without, always the first interface is used, even if it's not the correct one.

calico_ip_auto_method fixes that.
Closing


Stop git handling binary images files as text

When cloning the repository from scratch, 4 files are coming up as modified and attempting to run checkout to get to a clean state fails due to the rule in this file setting all files (*) to be processed by Git as text with automatic EOL processing. See the below for what happens:
Initial clone results in dirty status and CRLF conversion warnings on PNG files
davidalger:05:13 PM:/server/proj$ git clone https://github.com/stefanprodan/dockprom
Cloning into 'dockprom'...
remote: Enumerating objects: 605, done.
remote: Total 605 (delta 0), reused 0 (delta 0), pack-reused 605
Receiving objects: 100% (605/605), 1.49 MiB | 328.00 KiB/s, done.
Resolving deltas: 100% (343/343), done.
davidalger:05:14 PM:/server/proj$ cd dockprom/
warning: CRLF will be replaced by LF in screens/Grafana_Docker_Containers.png.
The file will have its original line endings in your working directory
davidalger:05:14 PM:/server/proj/dockprom (master *) $ git status
On branch master
Your branch is up to date with 'origin/master'.

Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git checkout -- <file>..." to discard changes in working directory)

	modified:   screens/Grafana_Docker_Containers.png
	modified:   screens/Grafana_Docker_Host.png
	modified:   screens/Grafana_Prometheus.png
	modified:   screens/Slack_Notifications.png

no changes added to commit (use "git add" and/or "git commit -a")
warning: CRLF will be replaced by LF in screens/Grafana_Docker_Containers.png.
The file will have its original line endings in your working directory
davidalger:05:14 PM:/server/proj/dockprom (master *) $ git checkout .
Updated 4 paths from the index
warning: CRLF will be replaced by LF in screens/Grafana_Docker_Containers.png.
The file will have its original line endings in your working directory
davidalger:05:14 PM:/server/proj/dockprom (master *) $ git status
On branch master
Your branch is up to date with 'origin/master'.

Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git checkout -- <file>..." to discard changes in working directory)

	modified:   screens/Grafana_Docker_Containers.png
	modified:   screens/Grafana_Docker_Host.png
	modified:   screens/Grafana_Prometheus.png
	modified:   screens/Slack_Notifications.png

no changes added to commit (use "git add" and/or "git commit -a")
warning: CRLF will be replaced by LF in screens/Grafana_Docker_Containers.png.
The file will have its original line endings in your working directory

Setting binary mode on image file types corrects the problem
davidalger:05:14 PM:/server/proj/dockprom (master *) $ vi .gitattributes
davidalger:05:14 PM:/server/proj/dockprom (master *) $ git checkout screens/
Updated 4 paths from the index
davidalger:05:14 PM:/server/proj/dockprom (master *) $ git status
On branch master
Your branch is up to date with 'origin/master'.

Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git checkout -- <file>..." to discard changes in working directory)

	modified:   .gitattributes

no changes added to commit (use "git add" and/or "git commit -a")
davidalger:05:14 PM:/server/proj/dockprom (master *) $

I've actually recently come across this on my Windows Dev machine and needed to adjust this, thanks!

Thanks @nightah!


make publish action great again

refactor of current action to split it in packages (no functionality changed)
changed deb packages publish to not be split by arch and OS and only mirror once for all archs and improve performance (https://github.com/newrelic/infrastructure-publish-action/pull/112/files#diff-5883b912ed6041a10ef7bf26c1c5cf26b963af5be1d06034d960f39314fb0a77R196)

Can you provide some context/info regarding the PR?

Can you provide some context/info regarding the PR?

Sorry @paologallinaharbur for the lack of description, added you too today in standup as @brushknight and I worked together on this. Added summary.

(PS: the PR name is precious 🤣 )

Credit to @brushknight ;-)


Building web application with Kotlin and Typescript

Article checklist
Formatting and structure checks

[X] Have you used the correct folder and file structure? - see Contribution Guidelines

[X] Is your article properly formatted in Markdown? - see Github Markdown guide

[X] Have you used our preferred heading structure? - H3 (###) and up

[X] Does your article follow any of the suggested structure formats? - see example formats

[X] Is your article over 750 words? - Tool: Wordcounter.net

[X] Is the article you are submitting an in-depth and unique article? Does it go beyond what is in the official docs and what is covered in other blog sites. See these articles as examples.

[X] Does your article provide enough value and detail about your topic? - Articles should be clear, accurate, and fully explained.

[X] Can your article be understood by beginners? - Assume the audience is smart but has no prior exposure to the common terminology in your article.

[X] Have you included a hero image that is 600x400 pixels, under 300KB in size, and have the copyright to use it? - Tools: Pixlr Image Editor for resizing and Unsplash for Creative Commons images

Grammar & plagiarism checks

[X] Have you spellchecked and grammar checked your article? - Tools: Write&Improve - ProWritingAid - Grammarly
[X] Please place your article through a 3rd party plagiarism checker. We suggest using Quetext, this tool is free and has a daily limit. We typically accept articles with 10% or less.
[X] Have you checked your article for readability? - Tool: Hemmingway
[ ] Have you added sources for quotes and images that aren't yours?

Technical checks

[X] Are your code snippets properly formatted for syntax highlighting - see Syntax guide
[X] Have you checked your code runs correctly and you've highlighted all necessary dependencies for installation?
[X] Are the software programs and packages you're highlighting in your article up to date, using current versions and not deprecated?

Topic suggestion this closes
This closes #4920

Good afternoon and thank you for submitting your article for publishing.
With the recent increase in article volume out team has been working diligently to review every article. Your article has been entered into our queue and should be reviewed (and published pending any changes) as soon as a peer reviewer is finished with the ones in the queue before it. 🚀
Thank you.

@ahmadmardeni1  hello 👋
Its been 5 days and no peer reviewer has been assigned on this.
Thanks ☺

@ahmadmardeni1 @07BLAIZER picking up this.

The plagiarism percentage is way greater than what we typically accept. I will be closing this PR for now. Feel free to make the changes outside of the queue and submit a new PR.
Uploading Building web application with Kotlin and Typescript #5466.pdf…


what is the reason of this error? thx

when I run "npm start" command, there are some errors:
root@ubuntu:~/ulord-node-stratum-pool# npm start

<EMAIL_ADDRESS>start /root/ulord-node-stratum-pool
node init.js

fs.js:1236
throw error;
^
Error: watch /root/ulord-node-stratum-pool/web/ulordrig.exe ENOENT
at exports._errnoException (util.js:907:11)
at FSWatcher.start (fs.js:1234:19)
at Object.fs.watch (fs.js:1262:11)
at Object. (/root/ulord-node-stratum-pool/libs/apiEx.js:33:4)
at Module._compile (module.js:409:26)
at Object.Module._extensions..js (module.js:416:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Module.require (module.js:353:17)
at require (internal/module.js:12:17)
npm ERR! Linux 4.4.0-128-generic
npm ERR! argv "/root/.nvm/versions/node/v4.8.7/bin/node" "/root/.nvm/versions/node/v4.8.7/bin/npm" "start"
npm ERR! node v4.8.7
npm ERR! npm  v2.15.11
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>start: node init.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script 'node init.js'.
npm ERR! This is most likely a problem with the ulord-pool package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node init.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs ulord-pool
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!
npm ERR!     npm owner ls ulord-pool
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     /root/ulord-node-stratum-pool/npm-debug.log
what is the reason?
Thanks

I'm sorry.This file is used to verify the miner MD5.I fixed it.Please download the newest code.

Thank you very much.
I just use the command: git clone https://github.com/UlordChain/ulord-node-stratum-pool.git ulord-node-stratum-pool
to get the code, isn't it the newest one? I am not so familiar with the git, How can I get the newest code?
Thank you very much!
086-186-1198-2760
在2018年08月17 16时55分, "Zyan<EMAIL_ADDRESS>I'm sorry.This file is used to verify the miner MD5.I fixed it.Please download the newest code.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I have used the "git pull" command updated the local code.
but the errors comes again, like that:
root@ubuntu:~/ulord-node-stratum-pool# npm start

<EMAIL_ADDRESS>start /root/ulord-node-stratum-pool
node init.js

2018-08-17 08:23:43 [POSIX][Connection Limit] (Safe to ignore) POSIX module not installed and resource (connection) limit was not raised
2018-08-17 08:23:43 [Master][ulord_example.json] Pool has same configured coin file coins/ulord.json as ulord.json pool
npm ERR! Linux 4.4.0-128-generic
npm ERR! argv "/root/.nvm/versions/node/v4.8.7/bin/node" "/root/.nvm/versions/node/v4.8.7/bin/npm" "start"
npm ERR! node v4.8.7
npm ERR! npm  v2.15.11
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>start: node init.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script 'node init.js'.
npm ERR! This is most likely a problem with the ulord-pool package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node init.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs ulord-pool
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!
npm ERR!     npm owner ls ulord-pool
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     /root/ulord-node-stratum-pool/npm-debug.log
could you please tell me the reason?
Thank you very much!
086-186-1198-2760
在2018年08月17 16时55分, "Zyan<EMAIL_ADDRESS>I'm sorry.This file is used to verify the miner MD5.I fixed it.Please download the newest code.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Emm,it maybe ulord_example.json and ulord.json has the same configurations.You can delect one of them.A same port can't appear in config files.

Install node-pre-gyp will fix your issue
$ apt install node-pre-gyp


Scott

@bitscott1102 Please make sure your binary heap files are in the right folder (4.1 not 4.3)


Blank screen after successful installation

After successful installation, the server only supplies a blank page when a client attempts to access it using the correct port and hostname.
Steps to reproduce the behavior:

Clone the main repository
Create a user for network maps
Chown -R user:user /path/to/networkmaps/
Create /var/lib/networkmaps (and all sub dirs)
Chown -R user:user /var/lib/networkmaps/
Edit the configuration accordingly
/path/to/networkmaps/server.js (verify there are no errors)

I'm expecting the software to bring up a login screen, but instead a completely empty page appears.

OS: Tried Windows Server 2016 and Linux Mint 19.2
Browser Google Chrome - latest

This is the most basic I can describe the issue, however for more details, here is my configuration file with censored credentials:
{
    "socket": {
        "address": "<IP_ADDRESS>",
        "port": 3000
    },
    "sendmail": {
        "server": "*******************",
        "port": 587,
        "is_secured": true,
        "user": "*********",
        "password": "**********",
        "from": "***********"
    },
    "users": {
        "admin_username": "admin",
        "admin_password": "**********"
    }
}

I've noticed in the "Preview" of my comment that the configuration file looks flat, it is not and I have tested it with json lint.
Thanks!

Hello.
Thanks for reporting the issue.
Can you provide the url your client is trying to access? Is it http://<IP_ADDRESS>:3000 or are you trying to access it by hostname?
Also, can you provide the source code (html) of the blank page he is getting?
Regards,
Pablo.

Hi Pablo!
Sorry I didn't see the notification for this. I was indeed connecting to http://<IP_ADDRESS>:3000/, the HTML looks like this:
https://imgur.com/a/st2PJNd Sorry I had to use VNC to access a machine on the network quickly I can copy and paste the direct code tomorrow.
Thank you for your time!

Thanks for your response. Can you also check one more thing?
In the console of your browser (you can access it via dev tools CTRL+SHIFT+J), can you check if you have any error?
And also, can you paste the logs from the server.

 (Chown -R networkmaps:networkmaps to each was performed on multiple occasions).
Thanks!

Aug 18 11:16:11 NetworkMaps node[121]: GET /static/js/index.js HOST:<IP_ADDRESS>:3000 USER AGENT:Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like G
Aug 18 11:16:11 NetworkMaps node[121]: 404

These log entries are telling me that the server is unable to find the static files.
On the systemd service file can you try to add the following entry under the [Service] section:
WorkingDirectory=/opt/networkmaps
This should be enough for the server to be able to find the static files (these files should be on /opt/networkmaps/html/static).
Let me know if this fixes your issue.

Well that was incredibly embarassing. For some reason my logic was that NetworkMaps would already know its working directory because of its launch location.
Thanks Pablo that worked like a charm! I appreciate your time and support with this issue, sorry it was so simple.
Additionally, I'd like to thank you for investing so much time into developing this project and MaSSHandra which I still use on a number of workstations!
Tmanok


"mas upgrade" command

Instead of:
❯ mas outdated
747648890 Telegram (1.90)
557168941 Tweetbot for Twitter (2.1)

❯ mas install 747648890
==> Downloading Telegram
==> Installed Telegram

❯ mas install 557168941
==> Downloading Tweetbot for Twitter
==> Installed Tweetbot for Twitter

just something like ...
❯ mas upgrade
The following applications are outdated: Telegram (1.90), Tweetbot for Twitter (2.1)
==> Downloading Telegram
==> Installed Telegram
==> Downloading Tweetbot for Twitter
==> Installed Tweetbot for Twitter

OOOH. Thanks @frdmn for letting me know about this program, I can now swap out my horrible hacky implementation at https://github.com/mattly/bork/blob/master/types/macstore.sh with bindings for mas.


Importing existing k8s resources into a release

I would like to import existing resources into my release.
This new helm feature allows you to adopt existing resources by annotating them: https://github.com/helm/helm/pull/7649
I was thinking of implementing this using the new Kustomize feature https://github.com/roboll/helmfile/pull/1172 but I couldn't get it to work.
Is it possible to use this feature just for patching existing k8s resources? If not, is there a different way to achieve this?
Thanks

@dudicoco Hey! Sorry but I don't get it. For example, how would you expect your helmfile.yaml to look like when importing existing k8s resources? That may help me understanding what you are trying to.
Anyway, I was thinking that you would just manually modify your existing resources with kubectl annotate and then run helmfile apply as usual, so that helmfile/helm will adopt resources like explained in helm/helm#7649. Im not sure how Helmfile can helm that.

Hey @mumoshu, thanks for the reply! The helmfile.yaml will look like this:
releases:
- name: foo
  chart: my-repo/foo
  version: 1.0.0
  namespace: default
  installed: true
  jsonPatches:
  - target:
      version: v1
      kind: Deployment
      name: foo
      namespace: default
    patch:
    - op: replace
      path: /metadata/annotations
      value:
      - meta.helm.sh/release-name=foo
      - meta.helm.sh/release-namespace=default
    - op: replace
      path: /metadata/labels
      value:
      - app.kubernetes.io/managed-by=Helm

Obviously I could patch the resources manually, but I would like the process to be automated with infrastructure as code.
When creating a new cluster with AWS EKS (and I assume with other providers as well) there are many resources that are created by default, such as aws-node and coredns which I would like to manage using helm. A manual step during the provisioning process is less ideal.

@dudicoco Thanks!
I believe you need another mechanism that jsonPatches for that. jsonPatches in helmfile works by patching "desired" resources to be applied. On the other hand, what you need to let helm adopt existing resources to patch existing/live resources.
I do understand your use-case.  But implementing that in Helmfile seems to bloat Helmfile's scope? 🤔 WDYT?

@mumoshu I wonder if this feature would provide the solution:
https://github.com/roboll/helmfile/pull/746
Not sure how it works exactly.

Please let met me dive into my memory... anyway,  I might have possibly missed porting that feature in #1172 so it may not work now

#746 was intended to work by importing existing resources before the first helm upgrade --install run, and the imported resources are specified via a list of NAMESPACE/KIND/NAME entries.
Would that work for you if it worked as advertised?

I thought it was used like this:
releases:
- name: aws-auth
   chart: ...
   adopt:
   - kube-system/configmap/aws-auth

@mumoshu i'm getting the following error: Error: unknown flag: --adopt
Perhaps using the helm-x binary is needed for this feature to work?
Regarding patching via terraform, this is not possible at the moment:
https://github.com/terraform-providers/terraform-provider-kubernetes/issues/723

Yes, I believe you're correct. But on the other hand I thought helm x --adopt supported Helm 2. Probably I need to rework on that.
Otherwise letting Helmfile to leverage helm 3's ability to adopt resources would be nice as well.

Thanks @mumoshu.
Do you think this feature might be added any time soon?
In the meantime, I have found a workaround using hooks:
  hooks:
  - events:
    - presync
    showlogs: true
    command: kubectl
    args:
    - --context={{ $kubecontext }}
    - --namespace={{ $namespace }}
    - annotate
    - serviceaccount
    - my-svc
    - meta.helm.sh/release-name={{ .name }}
    - meta.helm.sh/release-namespace={{ $namespace }}
  - events:
    - presync
    showlogs: true
    command: kubectl
    args:
    - --context={{ $kubecontext }}
    - --namespace={{ $namespace }}
    - label
    - serviceaccount
    - my-svc
    - app.kubernetes.io/managed-by=Helm

This is working as expected, however I have a problem - as part of our CI we are running helmfile apply --args "--dry-run".
This command will actually trigger the hook during the CI test, a solution for that would be to add an if block to not include the hook during a dry run, but then helm would fail on conflict with existing resources: Error: rendered manifests contain a resource that already exists..
Do you have an advise on how to handle this chicken and egg problem?

Would love to follow up on this. I'd like to see a way to modify resources like the EKS installed coredns

@abatilo i've ended up importing the resources with a script on all of our existing clusters (just annotate and add labels to the resources).
I've also created a script which deletes the EKS resources (coredns, kube-proxy, aws-node) on new clusters prior to installing these components with helmfile.

I’m a bit confused as this seems to automagically work for me already. I migrated the storage for some of my releases (and will soon write a blog post about that, can link it here if anybody is interested).
During that, I deleted the PVC resource and later recreated it (for the new PV where the data was migrated to) without the labels helm uses to denote ownership (managed-by etc.).
After that, I had a PVC with the same name as the old one, but without the labels/annotations for helm.
I then executed helmfile diff which came back empty as the helm release did not change (but the cluster state did).
To then rectify the missing labels, I ran helmfile sync, after which the labels were present (and still are).
I have a gut feeling that this has to do with https://github.com/helm/helm/pull/7649, but if somebody can clarify why that worked for me, I’d be really happy!
I’m running:

helm v3.4.2
helmfile v0.135.0

I’m a bit confused as this seems to automagically work for me already. I migrated the storage for some of my releases (and will soon write a blog post about that, can link it here if anybody is interested).
During that, I deleted the PVC resource and later recreated it (for the new PV where the data was migrated to) without the labels helm uses to denote ownership (managed-by etc.).
After that, I had a PVC with the same name as the old one, but without the labels/annotations for helm.
I then executed helmfile diff which came back empty as the helm release did not change (but the cluster state did).
To then rectify the missing labels, I ran helmfile sync, after which the labels were present (and still are).
I have a gut feeling that this has to do with https://github.com/helm/helm/pull/7649, but if somebody can clarify why that worked for me, I’d be really happy!
I’m running:

helm v3.4.2
helmfile v0.135.0

I’m a bit confused as this seems to automagically work for me already. I migrated the storage for some of my releases (and will soon write a blog post about that, can link it here if anybody is interested).
During that, I deleted the PVC resource and later recreated it (for the new PV where the data was migrated to) without the labels helm uses to denote ownership (managed-by etc.).
After that, I had a PVC with the same name as the old one, but without the labels/annotations for helm.
I then executed helmfile diff which came back empty as the helm release did not change (but the cluster state did).
To then rectify the missing labels, I ran helmfile sync, after which the labels were present (and still are).
I have a gut feeling that this has to do with https://github.com/helm/helm/pull/7649, but if somebody can clarify why that worked for me, I’d be really happy!
I’m running:

helm v3.4.2
helmfile v0.135.0

I’m a bit confused as this seems to automagically work for me already. I migrated the storage for some of my releases (and will soon write a blog post about that, can link it here if anybody is interested).
During that, I deleted the PVC resource and later recreated it (for the new PV where the data was migrated to) without the labels helm uses to denote ownership (managed-by etc.).
After that, I had a PVC with the same name as the old one, but without the labels/annotations for helm.
I then executed helmfile diff which came back empty as the helm release did not change (but the cluster state did).
To then rectify the missing labels, I ran helmfile sync, after which the labels were present (and still are).
I have a gut feeling that this has to do with https://github.com/helm/helm/pull/7649, but if somebody can clarify why that worked for me, I’d be really happy!
I’m running:

helm v3.4.2
helmfile v0.135.0

- --context={{ $kubecontext }}
Does anyone know, how can i get kubecontext value from environment?
similar to name and namespace:
- meta.helm.sh/release-name={{`{{ .Release.Name }}`}}
- meta.helm.sh/release-namespace={{`{{ .Release.Namespace }}`}}


BelongsToManyMultiSelect default not selected, results in double selection if select again

Package
filament/forms
Package Version
v2.8.0
Laravel Version
latest
Livewire Version
latest
PHP Version
PHP 8.0.0
Bug description
Same issue as:
https://github.com/laravel-filament/filament/pull/1114/commits/ffb87a609a72f471884dc49fcd26de9cf2247931
Tested the above changes and it fixes the issue.
Steps to reproduce
No response
Relevant log output
No response

Fixed by #1128.


Docs fix for mounting bpf fs

Signed-off-by: Nate Sweet<EMAIL_ADDRESS>Please ensure your pull request adheres to the following guidelines:

[x] For first time contributors, read Submitting a pull request
[x] All code is covered by unit and/or runtime tests where feasible.
[x] All commits contain a well written commit description including a title,
description and a Fixes: #XXX line if the commit addresses a particular
GitHub issue.
[x] All commits are signed off. See the section Developer’s Certificate of Origin
[x] Provide a title or release-note blurb suitable for the release notes.
[x] Thanks for contributing!

Attempting to mount the bpf file system twice will result in error messages.
These messages confuse users into thinking they've done something incorrect.
A note of warning is added to the documentation so that users know when
they can skip mounting the bpf file system.
Fixes: #10955

Coverage decreased (-0.01%) to 46.774% when pulling 1b00d88f718d5b8923d7d11b0f580547ea4c2839 on pr/nathanjsweet/bpf-fs-note into 263fbd5df44632498aad9984c51b263083e69386 on master.

test-me-please

@nathanjsweet FYI docs-only changes should not require test-me-please. The "Documentation Updates" check should be sufficient.


${bookarray} should include "Psalms" instead of "Psalm"

I think "Psalms" would be a better choice.

I fixed that now, thanks!


[Vue] TypeScript inferred prop types fail build

Current Behavior

It seems, that if you use a typed property in a TypeScript Vue component:
import { defineComponent } from 'vue';

export default defineComponent({
  name: 'NotifCardBase',
  props: {
    soundUrl: {
      type: String
    },
  },
  setup(props) {
    function test(val: string) {return val};

    test(props.soundUrl);
  }
})

It will throw an error
Expected Behavior

This should not throw an error. In the minimal reproduction I provided (see below), I confirmed that the exact same Vue component does now throw an error and both serves and builds perfectly fine.
This issue also only occurs on<EMAIL_ADDRESS>When using<EMAIL_ADDRESS>there are no problems.
I believe this may be due to a change made upstream. When looking at the changelog of 3.0.8, the only change that relates to TypeScript originates from this PR:
https://github.com/vuejs/vue-next/pull/3119
This PR also changes types directly associated with props, which increases my suspicion.
Steps to Reproduce

https://github.com/oceanbit/nx-plus-vue-ts-infer-bug (includes instructions and both vue-cli [with no problems] as well as freshly nx generated project [with error])
Failure Logs

  App running at:
  - Local:   http://localhost:8080/
  - Network: http://<IP_ADDRESS>:8080/

  Note that the development build is not optimized.
  To create a production build, run nx build my-app --prod.

ERROR in apps/my-app/src/NotifCardBase.vue:31:12
TS2345: Argument of type 'unknown' is not assignable to parameter of type 'string'.
    29 |       function test(val: string) {return val};
    30 |
  > 31 |       test(props.soundUrl);
       |            ^^^^^^^^^^^^^^
    32 |     }, {
    33 |       immediate: true
    34 |     });

Terminate batch job (Y/N)? Y

Environment

Plugin name and version:

>  NX  Report complete - copy this into the issue template

  Node : 14.17.3
  OS   : win32 x64
  npm  : 6.14.13

  nx : Not Found
  @nrwl/angular : Not Found
  @nrwl/cli : 12.0.0
  @nrwl/cypress : 12.0.0
  @nrwl/devkit : 12.0.0
  @nrwl/eslint-plugin-nx : 12.0.0
  @nrwl/express : Not Found
  @nrwl/jest : 12.0.0
  @nrwl/linter : 12.0.0
  @nrwl/nest : Not Found
  @nrwl/next : Not Found
  @nrwl/node : Not Found
  @nrwl/react : Not Found
  @nrwl/schematics : Not Found
  @nrwl/tao : 12.0.0
  @nrwl/web : Not Found
  @nrwl/workspace : 12.0.0
  @nrwl/storybook : Not Found
  @nrwl/gatsby : Not Found
  typescript : 4.1.6

Thanks for reporting this and great details!
I discovered while playing around in your repro that setting "strict": true in the my-app project's local tsconfig.json fixed the issue. I think that should be our default because of this, #185, and it's the default in Vue CLI.
Would you like to contribute the fix? You'd need to make the change for the app and library schematics.

Oh! Awesome!
I actually would love to make this contribution!
Is this also something that we could update with a nx upgrade schematic as well? Hopefully that way other consumers won't run into similar issues

Thanks!
I don't think a migration schematic should be paired with this because it can result in many other errors that would break builds. I imagine user frustrations similar to this.


Consider removing ack_id() from *AckHandler mocks

These functions do not exit in the base class, but removing them may be a breaking change.

This is slightly annoying, but not worth a taking a breaking change for such a small cleanup. Closing.


unhashable type: 'ColouredText'

Describe the bug
The new ColouredText class (which is super nice btw) that a lot of the widgets can now use is sometimes directly passed to wcwidth in the Frame class which casues the exception TypeError: unhashable type: 'ColouredText'.
This seems to only affect certain widgets like the ListBox.
https://github.com/peterbrittain/asciimatics/blob/476159c95c5b6e34a782ea97503785ad95683805/asciimatics/widgets.py#L2776
The solution seems to be something like this line where str() is called on the ColouredText object.
https://github.com/peterbrittain/asciimatics/blob/476159c95c5b6e34a782ea97503785ad95683805/asciimatics/widgets.py#L2919
But I'm not sure if this fixes it in all cases or if there are any other issues doing it this way.
To Reproduce
from asciimatics.widgets import Frame, ListBox, Layout, Divider, Button, Widget
from asciimatics.scene import Scene
from asciimatics.screen import Screen
from asciimatics.exceptions import ResizeScreenError, StopApplication
from asciimatics.parsers import AsciimaticsParser
import sys

class ListTestView(Frame):
    def __init__(self, screen):
        super(ListTestView, self).__init__(screen,
                                           screen.height * 2 // 3,
                                           screen.width * 2 // 3,
                                           hover_focus=True,
                                           can_scroll=False,
                                           title="Test List")

        self._running_test_list_view = ListBox(
            Widget.FILL_COLUMN,
            [(r'${15}● Test 1', 1)], # <- inserted color code
            name="running tests",
            parser=AsciimaticsParser(), # <- color code parser
            add_scroll_bar=True)

        # 1st layout
        layout = Layout([100], fill_frame=True)
        self.add_layout(layout)
        layout.add_widget(self._running_test_list_view, 0)
        layout.add_widget(Divider(), 0)

        # 2nd layout
        layout2 = Layout([1, 1])
        self.add_layout(layout2)
        layout2.add_widget(Button("Quit", self._quit), 1)
        self.fix()

    @staticmethod
    def _quit():
        raise StopApplication("User pressed quit")

def menu(screen, scene):
    scenes = [
        Scene([ListTestView(screen)], -1, name="Main"),
    ]
    screen.play(scenes, stop_on_resize=True, start_scene=scene, allow_int=True)

last_scene = None
while True:
    try:
        Screen.wrapper(menu, arguments=[last_scene])
        sys.exit(0)
    except ResizeScreenError as e:
        last_scene = e.scene

Expected behavior
No exception.
System details (please complete the following information):

OS and version: Ubuntu 20.04
Asciimatics version: master branch (commit 476159c)

Additional context

Full Traceback
$ python3.8 broken.py
Traceback (most recent call last):
  File "broken.py", line 53, in <module>
    Screen.wrapper(menu, arguments=[last_scene])
  File ".venv/ces-soc-cc-user_client/lib/python3.8/site-packages/asciimatics/screen.py", line 1379, in wrapper
    return func(screen, *arguments)
  File "broken.py", line 47, in menu
    screen.play(scenes, stop_on_resize=True, start_scene=scene, allow_int=True)
  File ".venv/ces-soc-cc-user_client/lib/python3.8/site-packages/asciimatics/screen.py", line 1548, in play
    self.draw_next_frame(repeat=repeat)
  File ".venv/ces-soc-cc-user_client/lib/python3.8/site-packages/asciimatics/screen.py", line 1651, in draw_next_frame
    effect.update(self._frame)
  File ".venv/ces-soc-cc-user_client/lib/python3.8/site-packages/asciimatics/effects.py", line 71, in update
    self._update(frame_no)
  File ".venv/ces-soc-cc-user_client/lib/python3.8/site-packages/asciimatics/widgets.py", line 462, in _update
    layout.update(frame_no)
  File ".venv/ces-soc-cc-user_client/lib/python3.8/site-packages/asciimatics/widgets.py", line 1255, in update
    widget.update(frame_no)
  File "/.venv/ces-soc-cc-user_client/lib/python3.8/site-packages/asciimatics/widgets.py", line 2776, in update
    paint_text += " " * (width - self.string_len(paint_text))
  File ".venv/ces-soc-cc-user_client/lib/python3.8/site-packages/wcwidth/wcwidth.py", line 245, in wcswidth
    wcw = wcwidth(char, unicode_version)
TypeError: unhashable type: 'ColouredText'

Yeah - that is still new codd that needsmore field hardening.  You're right - ColouredText must not be passed dirdctly to wcwidth.  Instead it should be converted to an ordinary string first.  I'm happy to take a PR to fix this if you've already done it.

Yes, I'll submit one today.
Thanks for keep up with this awesome project.

Thanks.


Add option to load config from file

Description
Add option to load config from file. Support both YAML and JSON files (detects dynamically). Configure options:

Enable loading style from environment variable via version.WithPrettyStyleFromEnv("ENV_NAME_FOR_FILE_PATH"),
Load a style file directly using Go function, version.WithPrettyStyleFile.

Reasons
It enables dynamic styling without the need to know/use Go.

is this available to pick up?

Hi, yes,
IMO we can also support only YAML in the first stage. Later we can "port" NewYAMLOrJSONDecoder :)
for loading the style configuration, you can take a look on https://github.com/charmbracelet/glamour#styles as they do exactly this :)

sounds good, I'll take a look, sorry for the late responses


feat: add an option to disable the session_cache

Adds the configurable option "enable_tokenwhitelist" (default false) that when enabled, requires tokens to be issued by the exact nakama instance. This is the current Nakama behaviour and some users (including me) complained about it, since a Server Reboot resulting in all clients had to manually reauthorize (i.e. login via the external auth provider).
Setting the config value "enable_tokenwhitelist" to false will skip all the checks to the so called "sessionCache" meaning tokens will be accepted by the server as long as they are valid (reboot safe).

🔥🔥🔥

Should now be resolved in v3.18.0. Rather than a configurable option, we've changed the nature of the cache itself to rely more heavily on the semantics of JWTs.


Fixed #1628: kube-down should not delete multi-user.target.wants dir

On Centos, there are some other service in multi-user.target.wants directory, so we should not just delete it.

This change is

https://github.com/kubernetes/contrib/issues/1628


opt,sql: disallow column references in ROWS/RANGE

PR: https://github.com/cockroachdb/cockroach/pull/40832
From release notes:

Column references are no longer allowed in ROWS and RANGE clauses in window functions. [#40832][#40832] {% comment %}doc{% endcomment %}

@rmloveland Assigning to you, per our discussion earlier.

@justinj (see https://github.com/cockroachdb/docs/pull/5790).
Our behavior before this change was undocumented and not postgres-like. I don't think we should document this change.


Allow ignoring enum variants in To/FromVariant

Note: In this issue, I will discuss both rust's enum variants, and Godot's Variants. To avoid confusion I will use an upper case V for Godot's as it is a class, and lowercase v for rust's enums.
Problem
Currently, we can derive ToVariant: https://docs.rs/gdnative/0.9.3/gdnative/core_types/trait.ToVariant.html. This works well, and for the cases where it isn't perfect, we can add #[variant(...)] attributes to specify how the macro should process certain pieces of data. One group of these attributes is #[variant(skip_to_variant|skip_from_variant|skip)]. As the name implies, this will skip a field when converting to/from a Variant. Currently, this must be placed on a struct's field:
#[derive(ToVariant, FromVariant)]
struct MyStruct {
  converted_field: u8,
  #[variant(skip)]
  skipped_field: u8,
}

One area this could be expanded is to skipping enum variants. For example, the following currently results in a compiler error:
#[derive(ToVariant, FromVariant)]
enum MyEnum {
   VariantA,
  #[variant(skip)]
  VariantB(NonToVariantType),
}

In this example, the variant(skip) is ignored, and because VariantB contains a non-ToVariant field, this fails to compile.
Proposal
Allow #[variant(skip)] (and its siblings) to be placed on enum variants. This does pose the following issues:

What if we try to call from_variant with a skipped variant?: We should consider this a failure and return an Err as if we called from_variant with a Dictionary that isn't a variant.
What if we try to call to_variant with a skipped variant?: There are a couple possibilities:

Return Nil or possible empty dict. Benefits are no crashing, disadvantages is that there may be silent bugs.
panic. Benefits are that we are bringing the issues up to the developer immediately, disadvantage is that panic is not really rusty when it could be better represented as an Result or something.

Why bother ignoring certain variants?: This admittedly comes from a specific use case I have, but I believe it would be good to expand the use of variant(skip). There may be cases where we need to convert a subset of enum variants to Variants while still retaining the non-To/FromVariant variants. My solution in the short-term will be to add #[variant(skip)] to the fields in my variant that are non-To/FromVariant.

Question 2 is an interesting one: originally the ToVariant trait was only meant to be implemented for simple types that are easily converted to Variant representations, which is I assume why it was designed to be infallible. This made features like this hard to support though, and I wonder if it's best to redesign the trait to return Result instead, possibly with a provided panicking method for convenience.

This is an interesting topic that I also came across during GDExtension development. In my case, the type in question was u64. I didn't want to use GDNative's behavior where values are silently cast to signed -- but it would be possible to support conversion from the "valid range" of u64, namely the first half of values, which remain the same value when converted to i64.
Since every other conversion was infallible, I decided for now that it was more type-safe to disallow u64 (and leave casts to explicit user code), and to make ToVariant always succeed if it can be implemented.
This example shows though that there may be other use cases. The trade-off I don't like here is that 99% of ToVariant cases are indeed infallible. Introducing Result would weaken API expressivity and introduce tons of unwrap()s all over the place --  a problem that godot-rust already suffers from.
An alternative might be two separate traits, similar to From and TryFrom, but this also adds a lot of complexity and the orphan rule might not be happy with it, either...


Removed PK in JS SDK and tested all code samples

Removed private key values in JS SDK and tested all code samples.

@kailash-manasarovar please approve

@kailash-manasarovar please approve

Morning @krofax you changed a fair bit of code here. Please get a tech review first.


Improvements to documentation

Are there any docs mentioning how to configure the core library (type factories, property factories etc.)


defer option?

Hi,
What does the defer option do please? If its set to true do we need to manually call csrf_check() ?
Thanks

It prevents csrf-magic from automatically executing csrf_check().


Click to select should be exclusive

Is the current behavior where click-to-select adds to current selection intentional? AFAIK in all other apps, you need to hold down ctrl/shift to add to selection.
I propose we use a modifier for that.
Affinity Designer uses Shift. Not sure what the standard is on this.

Agreed, I don't think it's intentional. I believe that usually shift is for adding, ctrl is for inverting (if selected, remove it, otherwise add).
I think that the issue is that the logic is done onmousedown where you don't have enough context to make a good decision. We'll need to check if we are clicking onmouseup and check if we haven't moved.

I think that the issue is that the logic is done onmousedown where you don't have enough context to make a good decision.

IMO not necessary since we don't support drag-select when clicking inside an element, thus we can already determine the desired behavior in mousedown event, if I'm not mistaken.


Single object queries to use include and keys

Allow queries on specific objects to use the include and keys query parameters.

Current coverage is 93.02%

Merging #1280 into master will increase coverage by +0.02% as of a56fe21

@@            master   #1280   diff @@
======================================
  Files           84      84
  Stmts         5275    5289    +14
  Branches       960     962     +2
  Methods          0       0
======================================
+ Hit           4906    4920    +14
  Partial         11      11
  Missed         358     358

Review entire Coverage Diff as of a56fe21

Powered by Codecov. Updated on successful CI builds.

This code looks good, but would you mind added a test case for it? In spec/ParseQuery.spec.js

Yeah, I will ASAP.

Added the test cases.

@drew-gross @flovilmart when will this be released to the npm package? Thanks


Create new study functionality implemented

Create new study and real-time display functions:

https://github.com/user-attachments/assets/2ffb02b0-0ef6-457a-9981-a045d72aee26

Only admin can input IRB number:

https://github.com/user-attachments/assets/ec40864a-4eef-4fdf-a708-a1db083e277b

Individual study pages for each organization:

https://github.com/user-attachments/assets/513d8f5a-2189-42af-906b-67dbe7c598a5

Looks good, thank you!


tab completion generates "command not found" errors

On a macOS host (v10.13.2), with the macOS copy of bash (in /bin/bash), attempting to tab-complete an appcenter command can lead to "command not found" errors.
Steps to reproduce:

install appcenter cli, via npm install -g appcenter-cli
setup tab completion for appcenter, via appcenter setup-autocomplete
start a new copy of bash
type in appcenter  (with the trailing space), then press tab

Observed results:
davidl@Wart ~ $ appcenter bash: _get_comp_words_by_ref: command not found
bash: __ltrim_colon_completions: command not found

Expected result: no errors are displayed.
Additional notes: pressing tab again will display possible values.  Each additional tab press will also display these, albeit, prefixed with errors.  For example:
davidl@Wart ~ $ appcenter bash: _get_comp_words_by_ref: command not found
bash: __ltrim_colon_completions: command not found
bash: _get_comp_words_by_ref: command not found
bash: __ltrim_colon_completions: command not found

analytics           codepush            help                orgs                telemetry
apps                crashes             login               profile             test
build               distribute          logout              setup-autocomplete  tokens
davidl@Wart ~ $ appcenter bash: _get_comp_words_by_ref: command not found
bash: __ltrim_colon_completions: command not found

analytics           codepush            help                orgs                telemetry
apps                crashes             login               profile             test
build               distribute          logout              setup-autocomplete  tokens
davidl@Wart ~ $ appcenter bash: _get_comp_words_by_ref: command not found
bash: __ltrim_colon_completions: command not found

analytics           codepush            help                orgs                telemetry
apps                crashes             login               profile             test
build               distribute          logout              setup-autocomplete  tokens
davidl@Wart ~ $ appcenter

Appcenter CLI version is reported as 1.0.6:
davidl@Wart ~ $ appcenter --version
appcenter version 1.0.6
davidl@Wart ~ $

Hey @DavidLudwig, thanks for reporting this bug. We've recorded it and working on it in the next sprint. Will update again when it's fixed

Hi @DavidLudwig ! The bug is now fixed in CLI v1.1.14

Hi @DavidLudwig, the bug fix is now deployed in CLI v1.1.14! Please download a new version of the CLI by running npm install -g appcenter-cli, and test this out. Let us know if you run into any issues!


Economy of scale

From what I can see, for every new deployment that needs to be scaled down to zero, there are two additional deployments that occur:

Interceptor
External scaler

As these deployments are not scaled down to zero and take resources from the cluster, the benefits of scale to zero are greatly reduced at best (if the user deployment takes equal or more resources than the interceptor and external scaler combined) or completely negated at worst (if the user deployment takes less resources than the interceptor and external scaler combined).
In addition, when the app is not scaled to zero, the interceptor and external scaler when deployed for every app will take resources from the cluster that could otherwise be used to schedule new deployments, and are sitting idle unless scale to zero occurs.
These insights rely on the design doc and my understanding of the code after a brief overview, so excuse misunderstandings.
/cc @tomkerkhove

@yaron2 are you interested in making a change? It would be certainly possible to make the interceptor and scaler multi-tenant if you're interested in that.

I am certainly interested in that, but I'm not sure it's "me" being interested in that as much as its about every user should be interested in that, because without a multi-tenant interceptor and external scaler I don't see any real benefit to running the HTTP add-on, again, unless I am missing something obvious?

Autoscaling your HTTP workloads would be one major benefit that persists even though you can't (currently) scale the interceptor or external scaler to zero. Regardless, yes, it would certainly be more resource efficient to run multi-tenant interceptors and scalers.

Autoscaling your HTTP workloads would be one major benefit that persists even though you can't (currently) scale the interceptor or external scaler to zero. Regardless, yes, it would certainly be more resource efficient to run multi-tenant interceptors and scalers.

Yeah I'm talking specifically about the scale to zero part. I didn't see 1:N autoscaling so far, but that can be achieved with the Prometheus scaler today, albeit in a more cumbersome way.

got it. yea, if you're looking to truly scale resources to zero on your cluster, you couldn't use the HTTP addon. Would you be interested in helping design and/or build these multi-tenant components?

got it. yea, if you're looking to truly scale resources to zero on your cluster, you couldn't use the HTTP addon, yea. Would you be interested in helping design and/or build these multi-tenant components?

I could probably help with design, for sure.

Yeah I'm talking specifically about the scale to zero part. I didn't see 1:N autoscaling so far, but that can be achieved with the Prometheus scaler today, albeit in a more cumbersome way.

@yaron2 We want to support 1:N scaling as well because we don't want to force people to use Prometheus. For example, my customers always use Azure Monitor and should not have to run Prometheus because of that.

I haven't thought about it from that angle and that definitely makes sense, we should go multi-tenant for sure.

Yeah I'm talking specifically about the scale to zero part. I didn't see 1:N autoscaling so far, but that can be achieved with the Prometheus scaler today, albeit in a more cumbersome way.

@yaron2 We want to support 1:N scaling as well because we don't want to force people to use Prometheus. For example, my customers always use Azure Monitor and should not have to run Prometheus because of that.

Yeah I understand, I totally support doing 1:N scaling. we should just make sure this is done in a way that isn't too costly on cluster resources.

@yaron2 I've begun a draft design doc: https://hackmd.io/@arschles/mutitenant-keda-http-addon
there are a few places where it's a bit rough - the biggest one is pushing routing table updates to interceptors and verifying that they've updated their in-memory copy.
let me know what you think

@ajanth97 Raised a concern about the isActive methods in the external scaler interface that will probably be addressed in this too. I'm just waiting for an issue to be created so we can track that down

@yaron2 I've begun a draft design doc: hackmd.io/@arschles/mutitenant-keda-http-addon
there are a few places where it's a bit rough - the biggest one is pushing routing table updates to interceptors and verifying that they've updated their in-memory copy.
let me know what you think

@arschles added a few comments on the document too, see if they're helpful

Thanks @khaosdoctor !


【question】May I ask if there is a performance comparison for flash_ attention 3？

Yes, checkout our paper for comparisons: https://arxiv.org/abs/2410.20399


Update android tools versions

Closes #11

Could you please merge this so i can use the main version instead of a fork? thanks.

This has been released with v0.2.1 on pub.dev
@eric-nextsense Thanks for your contribution. Check yourself in README!


add node-manager chart

Initialize Node Manager code.
Add Ksmtuned Controller manage KSM of node.

Related issue
https://github.com/harvester/harvester/issues/2302
Dependency PR
https://github.com/harvester/node-manager/pull/1

Image repo and tags are used temporarily.


Add playback for manual tuning

After a WebVTT file is generated, it probably is only 80% ish accurate.  Now need to add capability to playback the final video along with the VTT file next to it synced to the time-codes so you can easily edit the sections and save the edited version.

Could possibly use this - it's all in-browser: https://testdrive-archive.azurewebsites.net/Graphics/CaptionMaker/Default.html


Fix typos in ModalGallery example comments

Code uses img for routes but comments use images for them.

Thanks!


Grey Screen on app release

it is running fine in app debug but it is showing grey screen on apk release

Note sure if you resolved this @safwanidrees but I thought this may help:
https://stackoverflow.com/questions/61615866/flutter-app-show-grey-screen-in-release-mode-but-works-fine-in-debug-mode-instan?rq=1

Note sure if you resolved this @safwanidrees but I thought this may help:
https://stackoverflow.com/questions/61615866/flutter-app-show-grey-screen-in-release-mode-but-works-fine-in-debug-mode-instan?rq=1


Initialize contribution guidelines

Reference taken from:

https://github.com/signalapp/Signal-Desktop/blob/master/CONTRIBUTING.md
https://github.com/ethereum/go-ethereum/wiki/Developers'-Guide

@gaieges I moved the developer setup to README. Separated them by run being in README and tests stuff in CONTRIBUTING.


Metadata version mismatch after 3.2.2

Hi,
I am learning Ionic so if I missed something obvious please excuse me.
Per this ticket:
https://github.com/arielfaur/ionic-audio/issues/159
After updating the plugin to 3.2.2, while the problem of repeating onTrackFinished was fixed, when running "ionic cordova build android --prod"
I get this error:
Error: Metadata version mismatch for module /Applications/MAMP/htdocs/myapp/node_modules/ionic-audio/dist/ionic-audio-interfaces.d.ts, found version 4, expected 3     at StaticSymbolResolver.getModuleMetadata (/Applications/MAMP/htdocs/myapp/node_modules/@angular/compiler/bundles/compiler.umd.js:25755:34)     at StaticSymbolResolver._createSymbolsOf (/Applications/MAMP/htdocs/myapp/node_modules/@angular/compiler/bundles/compiler.umd.js:25543:46)     at StaticSymbolResolver.getSymbolsOf (/Applications/MAMP/htdocs/myapp/node_modules/@angular/compiler/bundles/compiler.umd.js:25524:14)     at /Applications/MAMP/htdocs/myapp/node_modules/@angular/compiler/bundles/compiler.umd.js:24381:30     at Array.forEach (<anonymous>)     at extractProgramSymbols (/Applications/MAMP/htdocs/myapp/node_modules/@angular/compiler/bundles/compiler.umd.js:24380:79)     at AotCompiler.analyzeModulesAsync (/Applications/MAMP/htdocs/myapp/node_modules/@angular/compiler/bundles/compiler.umd.js:23936:47)     at CodeGenerator.codegen (/Applications/MAMP/htdocs/myapp/node_modules/@angular/compiler-cli/src/codegen.js:32:14)     at Function.NgTools_InternalApi_NG_2.codeGen (/Applications/MAMP/htdocs/myapp/node_modules/@angular/compiler-cli/src/ngtools_api.js:73:30)     at Object.doCodegen (/Applications/MAMP/htdocs/myapp/node_modules/@ionic/app-scripts/dist/aot/codegen.js:6:51)
My search shows it has to do with dependencies and package.json.
Is this something wrong with my environment setup or something in 3.2.2? I restored an backup and the issue don't seem to exist with 3.2.0.

@rdai I am not sure what's wrong with your environment. I am able to build with --prod with 3.2.2.
Can you run ionic info and paste the results?

Thank you for the quick reply. Here is my Ionic info.
cli packages: (/usr/local/lib/node_modules)
@ionic/cli-utils  : 1.19.1
ionic (Ionic CLI) : 3.19.1

global packages:
cordova (Cordova CLI) : 8.0.0

local packages:
@ionic/app-scripts : 3.0.1
Cordova Platforms  : android 7.0.0 ios 4.5.3
Ionic Framework    : ionic-angular 3.8.0

System:
Node  : v8.3.0
npm   : 5.6.0
OS    : macOS High Sierra
Xcode : Xcode 9.2 Build version 9C40b

Environment Variables:
ANDROID_HOME : /usr/local/Cellar/android-sdk/24.4.1/

Misc:
backend : pro

You should update your project to Ionic 3.9.2. That will also update your app-scripts and typescript libraries. Check the ionic changelog for the upgrade instructions.

Ok, I tried it after 3.9.2, still the same thing, works when I did "npm install --save<EMAIL_ADDRESS>breaks as soon as I did "npm install --save<EMAIL_ADDRESS>I certainly don't expect you to fix an issue on my end if it works for you.

@rdai One more thing, have you also updated your @ionic/app-script package?

I just updated it after your message, still no good, my iconic info now is
`cli packages: (/usr/local/lib/node_modules)
@ionic/cli-utils  : 1.19.1
ionic (Ionic CLI) : 3.19.1

global packages:
cordova (Cordova CLI) : 8.0.0

local packages:
@ionic/app-scripts : 3.1.8
Cordova Platforms  : android 6.3.0 ios 4.5.3
Ionic Framework    : ionic-angular 3.9.2

System:
Node  : v8.3.0
npm   : 5.6.0
OS    : macOS High Sierra
Xcode : Xcode 9.2 Build version 9C40b

Environment Variables:
ANDROID_HOME : /usr/local/Cellar/android-sdk/24.4.1/

Misc:
backend : pro`

Thanks again, no worries.

I ran out of ideas 😃

I have good news! I realized the problem is 3.2.2 is on Angular 5 and since I started the project last year, my Angular is still 4. Efforts to upgrade the existing project has not been successful so instead of putting new wine in the old wineskin, I just started a brand new project and noticed the Angular is automatically set to 5, installed 3.2.2 and copy/pasted some of my code and it is working just fine! So it definitely was my environment and not your code.
Luckily your plugin is the central piece of what I am building so I should be able to migrate the rest with little effort and have myself a working app.
Just FYI. Thanks!


Support new cl.exe dependency report files

In the cl.exe compiler shipped with Visual Studio 16.7 Preview 3, cl.exe will have a new switch /sourceDependencies [json file name].
Which produces a json file in the following format
{
“Version”: “1.0”
“Data”: [
{
"Source": "c:\Full\Path\To\SourceFile1.cpp",
"Includes": [
" c:\Full\Path\To\Header1.h",
" c:\Full\Path\To\Header2.h"
]
“TlbImports”: [] // #imports
“Modules” : [] // used ifcs
}
]
}
This would be an alternative to the /showIncludes flag currently used for dependency checking.
@jhasse we would like to contribute a PR for this. Does this sound like something that would be accepted?

I'm not a maintainer of the ninja project, but I can't imagine that a PR to add support for this file format would be rejected. It sounds like an excellent feature.
How will you approach the json parsing?
Personally, I recommend adding a dependency on one of the large json handling libraries. One example is the nlohmann::json library.

Thank you. I'm open to suggestions for which json library we want to take a dependency on.

I do recommend that you hide the specific implementation of the json parsing behind some interface, so it doesn't infect any of the existing code inside of ninja.

Sounds good, although I'm not sure if going through the filesystem won't actually be slower than the current solution.
Why should the json parsing infect any of the existing code inside of ninja?
Since you're on Windows, you might try https://docs.microsoft.com/en-us/dotnet/api/system.web.script.serialization.javascriptserializer?view=netframework-4.8, but good luck coming up with the boilerplate code for calling C# from C++.

Why should the json parsing infect any of the existing code inside of ninja?

It definitely should not, but making sure to hide it behind some kind of interface makes it more difficult for the thing that shouldn't happen to happen :-)

The Visual C++ team is also interested in this because it would fix #1766 . I'm not familiar with json parsing options for C++ but we would look for a minimalist library as much as possible when implementing this, in the spirit of the ninja project.

The 3 C++ json libraries that I'm aware of are:
RapidJSON
nlohmann::json
Boost.Json
There are also several c-language JSON libraries, but It's not clear to me that there's any benefit to using C over C++, so I'm not sure they should be considered.

I would argue that it is not difficult to write a simple and fast limited JSON parser in C++ for a fixed schema like this one, that could be integrated directly into Ninja, with an option to link to another library like SIMDJson for performance if this really matters (I doubt it would). As long as the exact implementation details are hidden from the rest of the Ninja source code, support for external JSON libraries could be added as a build option. Just be sure to have an extensive unit-test suite that could be checked against any implementation.

I also notice that /sourceDependencies seems to generate a JSON file whose schema is not officially specified. Unlike /scanDependencies which uses standard schema P1689r3.
Anyone knows where to find a schema for /sourceDependencies then?

I previously wrote some code to parse /sourceDependencies, using cJSON library.
Indeed it used intermediate json files (at the time, I wanted to use /MP but still collect the per-translation-unit dependencies, and exporting to a directory is the only way to do that), however it should be noted that both /sourceDependencies and /scanDependencies support outputting to stdout instead of files (see the msdn docs). As Ninja doesn't support /MP anyway, it seems like maybe a better path for Ninja to use (@jhasse comment above).
I doubt you will find any well-defined spec for /sourceDependencies apart from the example on the msdn page. AFAIK it can be considered an "alpha" rollout of /scanDependencies. which itself implements a standard that is only in proposal stage. Is there a reason you want to use /sourceDependencies over /scanDependencies?

If useful: I think that the last time I checked these flags out they were only for module dependencies, rather than the normal header inclusion you'd need for #1766 and #613?


Change to UDL

😄 Hi,
Just change the source to UDL

I've added UDL during the last enhancement of the project as an alternative source code. Original XML is kept for people on older versions of Caché / Ensemble.


Issue with rapidjson when building

Hi, really nice library! ☄
When building the project I got the following error from cmake:
fatal: could not create work tree dir '/rapidjson': Read-only file system
/usr/bin/cd: line 4: cd: /rapidjson: No such file or directory
CMake Error at /usr/local/lib/cmake/vrslib/cmake/FindRapidjsonLib.cmake:33 (message):
  Could not setup rapidjson external dependency at /rapidjson
Call Stack (most recent call first):
  /usr/local/lib/cmake/vrslib/cmake/LibrariesSetup.cmake:29 (find_package)
  /usr/local/lib/cmake/vrslib/vrslibConfig.cmake:45 (include)
  /Users/x/.../CMakeLists.txt:20 (find_package)

After reading a bit of the cmake code and the python library I realized what was missing is the following line:
set(EXTERNAL_DEPENDENCIES_DIR "${CMAKE_BINARY_DIR}/external")

It looks like it is either something specific to my environment (MacOS) or something missing from the docs. Also currently the make files triggers a git clone on clean build, it'd be nice if that could be changed as it slows down builds and adds a networking dependency 🙏

EXTERNAL_DEPENDENCIES_DIR should always end up being set by this code , which is at the top of the cmake code. I'm not sure how it's not set for you, but you need to make sure to include that top cmake file, that's a requirement. The other cmake lists should not be accessed directly.

Hey, thanks for the reply!
So my flow was as mentioned here:
I compiled and installed the library locally, I then added find_package(vrslib REQUIRED) to my cmake file. That line failed with the above mentioned error. So reading your response, do you think I should have imported that CMakeLists.txt file manually because for some reason it wasn't included on its own?

The code I pointed to sets EXTERNAL_DEPENDENCIES_DIR if it's not set externally, which is an optional customization option given to the users of the library. You need to debug why it's not happening for you, because you should not get to the FindRapidjsonLib.cmake file without going through that code first.
I'm not sure I understand your question. The only CMakeLists.txt in the vrs project you should use directly is the top one, in the main folder.

Alright, I wasn't aware that cmake is supposed to import a library's CMakeLists.txt in find_package but I only recently started working with it so that makes perfect sense. If that's the case then this sounds like this is an issue in my specific environment
Feel free to close, in any case it might be helpful to anyone seeing the same error


Enable more material and cupertino tests on the Web

Description
Enable the following tests on the Web:

test/material/text_form_field_test.dart
test/cupertino/dialog_test.dart
test/cupertino/nav_bar_test.dart
test/cupertino/switch_test.dart
test/cupertino/date_picker_test.dart
test/cupertino/slider_test.dart
test/cupertino/text_field_test.dart
test/cupertino/segmented_control_test.dart
test/cupertino/activity_indicator_test.dart

Gold has detected one or more untriaged digests on patchset 1.
Please triage them at https://flutter-gold.skia.org/search?issue=52961.

Gold has detected one or more untriaged digests on patchset 1.
Please triage them at https://flutter-gold.skia.org/search?issue=52961.


Add Fly.io /postgres-volume to path

Update the directory path to use /postgres-volume/run/postgresql/data/ to maintain consistency with the path used in our alpine-postgresql-setup-and-start.sh script.

Let's be careful when we release a new version with these changes, because these cause us to rely on the new path (so this new path needs to be updated everywhere)


Automated Package Upgrade

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[Impeller] vulkan golden tests do not report validation layer errors

The vulkan context used in playground tests (golden and interactive tests) is generated in PlaygroundImplVK::InitGlobalVulkanInstance, it doesn't appear to be setting up a handler for validation errors.  That typically happens in debug_report_vk.cc.

The following patch turns them on
--- a/impeller/golden_tests/vulkan_screenshotter.mm
+++ b/impeller/golden_tests/vulkan_screenshotter.mm
@@ -66,8 +66,10 @@ std::unique_ptr<Screenshot> ReadTexture(

 VulkanScreenshotter::VulkanScreenshotter() {
   FML_CHECK(::glfwInit() == GLFW_TRUE);
+  PlaygroundSwitches playground_switches;
+  playground_switches.enable_vulkan_validation = true;
   playground_ =
-      PlaygroundImpl::Create(PlaygroundBackend::kVulkan, PlaygroundSwitches{});
+      PlaygroundImpl::Create(PlaygroundBackend::kVulkan, playground_switches);
 }


Increase kubernetes timeout from 10 seconds to 120 seconds.

Changes proposed in this PR

Increase the timeout

Why are we making these changes?
Avoid a lot of log spam

internal green?


Add docker file support for deploy

Fixes https://github.com/dotnet/tye/issues/146
Adds a new type that represents a DockerFile (so it gets ports and stuff).

Is the idea that we'll generate a k8s deployment/service for a dockerfile pretty much the same we we would for a project? SPICY.

Yep, only for files that have a docker file though, not just random images.

Is the idea that we'll generate a k8s deployment/service for a dockerfile pretty much the same we we would for a project? SPICY.

I'm worried about the versioning/tagging.


send_page_view parameter should be true as default, shouldn't?

Hello.
I think send_page_view parameter should be true as default to avoid duplicate page tracking.
Could anyone tell me what kind of the use cases there are for setting send_page_view to false?

Interested in this as well


add sudo to avoid error out with UMASK set to 027

Issue #, if available:
When source_ami is using With UMASK set to 027, kubelet and aws will error out with permissions issue.
The following is what I have for both kubelet and aws
amazon-ebs: -rwxr-x---. 1 root root 120671264 Nov 7 09:14 /usr/bin/kubelet
amazon-ebs: -rwxr-x---. 1 root root 6692768 Nov 13 20:11 /usr/local/aws-cli/v2/2.13.34/dist/aws

Errors I had:
==> amazon-ebs: Provisioning with shell script: /work/amazon-eks-ami/scripts/generate-version-info.sh
    amazon-ebs: /home/ec2-user/script_5180.sh: line 19: /usr/bin/kubelet: Permission denied
==> amazon-ebs: Provisioning step had errors: Running the cleanup provisioner, if present...

Description of changes:
Add 'sudo' in front of both commands, which will avoid errors listed above
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Testing Done
Tested with UMASK 027 images with 'sudo', worked as expected.
Tested with vanilla AWS AL2 latest image, worked as expected.

Is a different ssh_username an option for you?

No, the test I have done set  "ssh_username": "ec2-user".
Best Regards,
Leo Li
On Wed, Nov 15, 2023 at 3:06 PM Carter @.***> wrote:

Is a different ssh_username an option for you?
—
Reply to this email directly, view it on GitHub
https://github.com/awslabs/amazon-eks-ami/pull/1513#issuecomment-1811775996,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACOYINU2D3WXR56KHXVDSULYEQ5SVAVCNFSM6AAAAAA7KM3332VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJRG43TKOJZGY
.
You are receiving this because you authored the thread.Message ID:
@.***>

Is a different ssh_username an option for you?

@cartermckinnon
As you could see that we are restricting /usr/ folder which is access only to 'root', see the folder permissions
amazon-ebs: -rwxr-x---. 1 root root 120671264 Nov 7 09:14 /usr/bin/kubelet amazon-ebs: -rwxr-x---. 1 root root 6692768 Nov 13 20:11 /usr/local/aws-cli/v2/2.13.34/dist/aws
By adding sudo, it will solve my issue, also I believe adding sudo will not introduce any harm to the existing code at all.

@cartermckinnon
looks like there is another case:
https://github.com/awslabs/amazon-eks-ami/commit/967fb36528818af12a9cf2dcfc4097dec2e1e2b3

As you could see that we are restricting /usr/ folder which is access only to 'root', see the folder permissions

Sure; my suggestion is to just build the AMI as root. Set the username to root in your Packer template.

Hi @cartermckinnon
Thanks for your reply, and the suggestion is valid, if we have to build the AMI as root, it's kind of missing the point that we could specify a user to back AMI unless only root will be able to back the AMI in the road map which is the the way we are heading to.
I am also curious what harm it will introduce if we add 'sudo' ?
CC @varun-armis


Feature: added an extra field to the skill calculator so you can calculate custom xp actions

have a screenshot?

and an issue?

What is this change trying to achieve? I dont understand how is this useful at all

It does with super glass make but that's besides the point.
The skill calculator can't possibly cover every edge case xp drop and this allows people to calculate things that aren't on there.
Is it the feature you don't like or the form it takes. I could try and think of a different appearance that doesn't leave that extra field just dangling below.

To be honest, the xp remaining pr will probably make this near useless.

To be honest, the xp remaining pr will probably make this near useless.

How so? Wouldn't a user still have to grab the calculator themselves if they knew the xp remaining. Isn't the point of the tab to have it calculated for you

Maybe it's better to add "Goal"'s to the 'XP tracker' plugin - which can show actions, experience and time left.


[RFC] Add AuthoritySignedData type

SuiDataStore currently contains these two tables:

signed_transactions which maps from transaction digest to SignedTransaction.
signed_effects which maps from transaction digest to SignedTransactionEffects.

If we want to reuse SuiDataStore in Gateway or other non-authority nodes, we will want to use the above two tables to store non-signed transaction and effects.
This PR attempts to do that:

Added a generic type AuthoritySignedData which wraps an authority signed data. This type derives SignedTransaction and SignedTransactionEffects as two instantiations of AuthoritySignedData. One nice thing about this is that if we ever want to add more common code on authority signed types, this will come in handy.
In SuiDataStore, introduce a new enum called RawOrSignedData, which wraps the data type as well as a const generic type indicating whether this is used by authority. Added conversions between RawOrSignedData and AuthoritySignedData. Since there is no use of the non-authority case yet, I didn't add the false case for now, but you can see where it's going.
Both signed_transactions table and signed_effects table will be converted to store RawOrSignedData.

Review tips: Start from message.rs to review AuthoritySignedData,  and then go to authority_store to review RawOrSignedData. The rest are mechanical changes.

Ah I guess type alias doesn't work with serde. @huitseeker any suggestions?

Ok @lxfind just to detail my idea a little more:  here is a design which forces the same type of signature for both effects and transactions and is more ergonomic I believe.  IE there is no possibility of two different values, which is the point of an enum, which I believe you don't really want.
trait Signature { .... }
struct EmptySig {}
impl Signature for EmptySig {}
struct AuthoritySignature {
    authority_name: Vec<u8>,
    authority_sig: Vec<u8>,
}
impl Signature for AuthoritySignature {}

struct Effects<S: Signature> {
   ... other fields
    sig: S,
}

struct Transaction<S: Signature> {
     ... other fields
     sig: S,
}

struct SuiDataStore<S: Signature, ...> {
     effects: BTreeMap<Digest, Effects<S>>,
    transactions: BTreeMap<Digest, Transaction<S>>,
}

More for @lxfind
I don't think it's a huge refactoring, or any bigger than your PR, as you are already renaming lots of things.   I would say to make it easier you can do the following:

Leave Transaction and TransactionEffects alone
Define a new TransactionEnvelope and EffectsEnvelope which has the signature I suggested- ie TransactionEnvelope<S: Signature>
Then, redefine SignedTransaction to just be TransactionEnvelope<AuthoritySignature>, and RawTransaction to be TransactionEnvelope<EmptySignature>

Closing in favor of https://github.com/MystenLabs/sui/pull/1071


Added interfaces and implementations for SHL scanning

IMPORTANT: All PRs must be linked to an issue (except for extremely trivial and straightforward changes).
Fixes #[issue number]
Description
Added interfaces and implementations for the scanning of Smart Health Link QR codes, along with unit tests.
Alternative(s) considered
Have you considered any alternatives? And if so, why have you chosen the approach in this PR?
Type
Choose one: Feature
Screenshots (if applicable)
Checklist

[x] I have read and acknowledged the Code of conduct.
[x] I have read the Contributing page.
[x] I have signed the Google Individual CLA, or I am covered by my company's Corporate CLA.
[x] I have discussed my proposed solution with code owners in the linked issue(s) and we have agreed upon the general approach.
[x] I have run ./gradlew spotlessApply and ./gradlew spotlessCheck to check my code follows the style guide of this project.
[x] I have run ./gradlew check and ./gradlew connectedCheck to test my changes locally.
[x] I have built and run the demo app(s) to verify my change fixes the issue and/or does not break the demo app(s).

Closing


Remove flatten_records kwarg for reducers

Removed in awkward v2.0.3

Codecov Report

Merging #139 (f75a6f1) into main (78e5712) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main     #139   +/-   ##
=======================================
  Coverage   95.72%   95.72%
=======================================
  Files          18       18
  Lines        1754     1754
=======================================
  Hits         1679     1679
  Misses         75       75

Impacted Files
Coverage Δ

src/dask_awkward/lib/reducers.py
96.11% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Add support for component hdfs2

http://camel.apache.org/hdfs2.html

No user posts in 2016, but plenty in 2015


python312Packages.boto3-stubs: 1.34.151 -> 1.34.152,  python312Packages.botocore-stubs: 1.34.151 -> 1.34.152

Description of changes

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

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

14 packages built:

aws-sam-cli
aws-sam-cli.dist
python311Packages.boto3-stubs
python311Packages.boto3-stubs.dist
python311Packages.botocore-stubs
python311Packages.botocore-stubs.dist
python311Packages.types-aiobotocore
python311Packages.types-aiobotocore.dist
python312Packages.boto3-stubs
python312Packages.boto3-stubs.dist
python312Packages.botocore-stubs
python312Packages.botocore-stubs.dist
python312Packages.types-aiobotocore
python312Packages.types-aiobotocore.dist