The module_test_ios flakes, crashing at dart::SimpleHashMap::Lookup > dart::TimelineEventRecorder::AddAsyncTrackMetadataBasedOnEvent

Both Mac module_test_ios and Mac_arm64_ios module_test_ios are severely flaky with 6 and 5 flakes each from recent 30 runs.
Examples:
https://ci.chromium.org/ui/p/flutter/builders/prod/Mac module_test_ios/12040/overview
https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_arm64_ios module_test_ios/5367/overview
[2023-04-21 13:18:36.230191] [STDOUT] stdout: Test Case '-[FlutterUITests testHybridViewWarm]' passed (11.399 seconds).
[2023-04-21 13:18:36.230598] [STDOUT] stdout: Test Suite 'FlutterUITests' failed at 2023-04-21 13:18:36.226.
[2023-04-21 13:18:36.230650] [STDOUT] stdout: 	 Executed 5 tests, with 1 failure (0 unexpected) in 63.441 (63.443) seconds
[2023-04-21 13:18:36.232730] [STDOUT] stdout: Test Suite 'FlutterUITests.xctest' failed at 2023-04-21 13:18:36.227.
[2023-04-21 13:18:36.232786] [STDOUT] stdout: 	 Executed 5 tests, with 1 failure (0 unexpected) in 63.441 (63.445) seconds
[2023-04-21 13:18:36.232820] [STDOUT] stdout: Test Suite 'All tests' failed at 2023-04-21 13:18:36.228.
[2023-04-21 13:18:36.232854] [STDOUT] stdout: 	 Executed 5 tests, with 1 failure (0 unexpected) in 63.441 (63.446) seconds
[2023-04-21 13:18:36.675545] [STDOUT] stderr: 2023-04-21 13:18:36.675 xcodebuild[42059:798874]  IDETestOperationsObserverDebug: Failure collecting logarchive: Error Domain=NSCocoaErrorDomain Code=4099 "The connection to service named com.apple.testmanagerd.control was invalidated: failed at lookup with error 3 - No such process." UserInfo={NSDebugDescription=The connection to service named com.apple.testmanagerd.control was invalidated: failed at lookup with error 3 - No such process.}
[2023-04-21 13:18:43.522143] [STDOUT] stderr: 2023-04-21 13:18:43.521 xcodebuild[42059:794082] [MT] IDETestOperationsObserverDebug: 72.501 elapsed -- Testing started completed.
[2023-04-21 13:18:43.522241] [STDOUT] stderr: 2023-04-21 13:18:43.521 xcodebuild[42059:794082] [MT] IDETestOperationsObserverDebug: 0.000 sec, +0.000 sec -- start
[2023-04-21 13:18:43.522284] [STDOUT] stderr: 2023-04-21 13:18:43.521 xcodebuild[42059:794082] [MT] IDETestOperationsObserverDebug: 72.501 sec, +72.501 sec -- end
[2023-04-21 13:18:43.529354] [STDOUT] stdout:
[2023-04-21 13:18:43.529438] [STDOUT] stdout: Test session results, code coverage, and logs:
[2023-04-21 13:18:43.529481] [STDOUT] stdout: 	/opt/s/w/ir/x/t/flutter_module_test_ios_xcresult.No1wOx/result
[2023-04-21 13:18:43.529520] [STDOUT] stdout:
[2023-04-21 13:18:43.529560] [STDOUT] stderr: Failing tests:
[2023-04-21 13:18:43.529611] [STDOUT] stderr: 	-[FlutterUITests testDualCold]
[2023-04-21 13:18:43.529650] [STDOUT] stderr:
[2023-04-21 13:18:43.529688] [STDOUT] stderr: ** TEST FAILED **

When the test failed the app wasn't running:

(screenshots are in the xcresult log links)

However it didn't find a crash log?  This recent flaking corresponded to the recent Xcode version/simulator bump.
cc @vashworth

https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_arm64_ios module_test_ios/5367/overview shows crash logs in the xcresult:
crash_log.txt
Crashing thread:
Thread 31 Crashed:: io.flutter.3.ui
0   libsystem_kernel.dylib        	       0x1b0549e60 __pthread_kill + 8
1   libsystem_pthread.dylib       	       0x1b059c3c0 pthread_kill + 256
2   libsystem_c.dylib             	       0x180129e28 abort + 124
3   libsystem_malloc.dylib        	       0x18019b284 malloc_vreport + 912
4   libsystem_malloc.dylib        	       0x18019b500 malloc_zone_error + 96
5   libsystem_malloc.dylib        	       0x1801841a0 free_small_botch + 36
6   Flutter                       	       0x1092804d4 dart::SimpleHashMap::Lookup(void*, unsigned int, bool) + 340
7   Flutter                       	       0x10945cd38 dart::TimelineEventRecorder::AddAsyncTrackMetadataBasedOnEvent(dart::TimelineEvent const&) + 108
8   Flutter                       	       0x10945da6c dart::TimelineEventFixedBufferRecorder::CompleteEvent(dart::TimelineEvent*) + 36
9   Flutter                       	       0x10945958c dart::TimelineEvent::Complete() + 32
10  Flutter                       	       0x1096659e8 Dart_TimelineEvent + 484
11  Flutter                       	       0x108f8e0b8 flutter::Pipeline<flutter::LayerTreeItem>::ProducerContinuation::ProducerContinuation(std::_LIBCPP_ABI_NAMESPACE::function<flutter::PipelineProduceResult (std::_LIBCPP_ABI_NAMESPACE::unique_ptr<flutter::LayerTreeItem, std::_LIBCPP_ABI_NAMESPACE::default_delete<flutter::LayerTreeItem> >, unsigned long)> const&, unsigned long) + 80

This recent flaking corresponded to the recent Xcode version/simulator bump.

Or not, this is a dart crash.  Looking to see when this started.

Flakes started on the same engine roll 7f11020c5572b578a258647aaa473d17b907a42b which contained dart roll https://dart.googlesource.com/sdk.git/+log/50b96abe9f6f..4cc2e637a315
https://ci.chromium.org/ui/p/flutter/builders/prod/Mac module_test_ios/12023/overview
https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_arm64_ios module_test_ios/5359/overview
cc @chinmaygarde engine sheriff

This recent flaking corresponded to the recent Xcode version/simulator bump.

The recent xcode bump happened on host only bots. I would not expect this devicelab task affected though.

AsyncTimelineTrackMetadata was added in https://github.com/dart-lang/sdk/commit/6fb71e7237de3e0a38619515b21f2a219b9b2406 was in https://github.com/flutter/engine/pull/41379 and https://github.com/flutter/flutter/pull/125271

https://dart-review.googlesource.com/c/sdk/+/297821 to turn off SUPPORT_PERFETTO is in dart 3.1.0-39.0.dev, should be picked up in the next dart -> engine roll.

Turning off SUPPORT_PERFETTO is in https://github.com/flutter/engine/pull/41475 - https://github.com/flutter/flutter/pull/125472.  Will mark these tests as unflaky.  Downgrading priority while @derekxu16 investigates.

I have landed a CL that fixes the crash and re-enables Perfetto-related features: https://github.com/dart-lang/sdk/commit/c4f31a9108fcfa7c9ccc3715677c368ee453895f.

Fix in dart -> engine roll https://github.com/flutter/engine/pull/41654

Fix is in https://github.com/flutter/flutter/pull/125858, thanks @derekxu16. Closing.


Add arbitrary data to each broadcast

Component
Forge
Describe the feature you would like
It would be useful for processes that manage broadcast log files if each tx could have arbitrary data attached. My use case is giving names to deployed contracts.
The interface could look like this:
function broadcast(bytes calldata) external;
function broadcast(address, bytes calldata) external;
function broadcast(uint256, bytes calldata) external;

and be used like this:
vm.broadcast(bytes("BetterContract"));
new Contract();

// struct TxInfo({uint version; string message;})
vm.broadcast(abi.encode(TxInfo({version: 2, message: "updating the oracle"})));
oracle.update();

The resulting JSON would look like this:
{
  "transactions": [
    {
      "hash": "0x16cd3c8ce4f1f3d03582e1d1132c90297469b36e5ee74fc9957cdceb4e3f51f6",
      "transactionType": "CREATE",
      "memo": <arbitrary bytes>
     }
   ]
 }

Or, to be easier to read in the JSON by default, just allow a string:
function broadcast(string calldata) external;
function broadcast(address, string calldata) external;
function broadcast(uint256, string calldata) external;

Additional context
No response

IIUC these feature requests sound like things that fit within the scope of #3911, i.e. we probably don't want to hack these into forge script — my impression of this issue is that it's a way to help manage deploy scripts/pipelines over the lifetime of a project, so going to close this as a result


Added linked list,Stack,queue,circular queue

Assigned Issue Number ?
#007
Language Opted ?
C/C++/Python/Java/...
Number of files added or updated ?
1/2/3/4/...
Name of these files ?
main folder => sub_folder => ... => ... => ... file.py
example :
Algorithm => Search_Algorithm => Linear_Search => Linear_Search.py
Checklist

[x] I've read the contribution guidelines.
[ ] I've referred the correct issue number.
[x] I've fill up this entire template correctly.
Added linked list,stack,queue,circular queue in C++

Added linked list,stack,queue,circular queue in C++


HTTP Client panics with type cast error when calling an endpoint

Description
The HTTP client panics when an SSL error occurs. Following is the log:
error: {ballerina}TypeCastError message=incompatible types: 'error' cannot be cast to 'http:Response|http:FailoverAllEndpointsFailedError|http:FailoverActionFailedError|http:UpstreamServiceUnavailableError|http:AllLoadBalanceEndpointsFailedError|http:AllRetryAttemptsFailed|http:IdleTimeoutError|http:AuthenticationError|http:AuthorizationError|http:InitializingOutboundRequestError|http:WritingOutboundRequestHeadersError|http:WritingOutboundRequestBodyError|http:InitializingInboundResponseError|http:ReadingInboundResponseHeadersError|http:ReadingInboundResponseBodyError|http:UnsupportedActionError|http:Http2ClientError|http:MaximumWaitTimeExceededError|http:SslError|http:GenericClientError|http:CookieHandlingError'
	at ballerina.http:externExecuteClientAction(http_client.bal:235)
	   ballerina.http.HttpClient:get(http_client.bal:109)
	   ballerina.http:invokeEndpoint(http_commons.bal:303)
	   ballerina.http.resiliency.http_retry_client:performRetryAction(resiliency/http_retry_client.bal:304)
	   ballerina.http.RetryClient:get(resiliency/http_retry_client.bal:188)
	   ballerina.http.Client:get(client_endpoint.bal:139)

Even when we remove the retry configs, the error remains the same with the following log:
error: {ballerina}TypeCastError message=incompatible types: 'error' cannot be cast to 'http:Response|http:FailoverAllEndpointsFailedError|http:FailoverActionFailedError|http:UpstreamServiceUnavailableError|http:AllLoadBalanceEndpointsFailedError|http:AllRetryAttemptsFailed|http:IdleTimeoutError|http:AuthenticationError|http:AuthorizationError|http:InitializingOutboundRequestError|http:WritingOutboundRequestHeadersError|http:WritingOutboundRequestBodyError|http:InitializingInboundResponseError|http:ReadingInboundResponseHeadersError|http:ReadingInboundResponseBodyError|http:UnsupportedActionError|http:Http2ClientError|http:MaximumWaitTimeExceededError|http:SslError|http:GenericClientError|http:CookieHandlingError'
	at ballerina.http:externExecuteClientAction(http_client.bal:235)
	   ballerina.http.HttpClient:get(http_client.bal:109)
	   ballerina.http.Client:get(client_endpoint.bal:139)

This seems like an issue when returning an error from the native code, which isn't an HTTP:ClientError. Ideally, this should return an HTTP:ClientError
Steps to reproduce
This was encountered while the Ballerina Standard Library build process. Try the following code: (May need to provide a GITHUB_ACCESS_TOKEN value).
import ballerina/http;

http:Client httpClient = new ("https://api.github.com/repos/ballerina-platform");

public function main() {

    http:Request request = ();
    request.setHeader("Accept", "application/vnd.github.v3+json");
    request.setHeader("Authorization", "bearer <GITHUB_ACCESS_TOKEN>");

    var result = httpClient->get("/module-ballerina-io/actions/workflows/build-master.yml/runs?per_page=1", request);
}

This get() call sometimes panic due to the aforementioned issue.
Affected Versions
Ballerina 1.2.9

Root cause:
The response is received at the transport but an SSLException occurs when the channel gets closed. Due to that error, the exception is thrown from the external client action.
USER_EVENT: SslCloseCompletionEvent(java.nio.channels.ClosedChannelException)
This exception could occur if the connection was closed before finishing the SSL handshake, but as per the tracelog, the response is already received to the client.
Tested the same with { http1Settings : { keepAlive: http:KEEPALIVE_NEVER }} config to close the connection after the request/response completion to avoid connection reuse, but still getting the same exception.
[2020-11-03 15:44:04,069] TRACE {http.tracelog.upstream} - [id: 0xe66dfbb4, correlatedSource: n/a, host:/<IP_ADDRESS>:58420 - remote:api.github.com/<IP_ADDRESS>:443] READ COMPLETE
[2020-11-03 15:44:04,093] TRACE {http.tracelog.upstream} - [id: 0xe66dfbb4, correlatedSource: n/a, host:/<IP_ADDRESS>:58420 - remote:api.github.com/<IP_ADDRESS>:443] OUTBOUND: DefaultHttpRequest(decodeResult: success, version: HTTP/1.1)
GET /repos/ballerina-platform/module-ballerina-io/actions/workflows/build-master.yml/runs?per_page=1 HTTP/1.1
Authorization: Bearer <GITHUB_ACCESS_TOKEN>
host: api.github.com
user-agent: ballerina
connection: keep-alive
[2020-11-03 15:44:04,101] TRACE {http.tracelog.upstream} - [id: 0xe66dfbb4, correlatedSource: n/a, host:/<IP_ADDRESS>:58420 - remote:api.github.com/<IP_ADDRESS>:443] OUTBOUND: DefaultLastHttpContent(data: UnpooledByteBufAllocator$InstrumentedUnpooledUnsafeHeapByteBuf(ridx: 0, widx: 0, cap: 0), decoderResult: success), 0B
[2020-11-03 15:44:04,101] TRACE {http.tracelog.upstream} - [id: 0xe66dfbb4, correlatedSource: n/a, host:/<IP_ADDRESS>:58420 - remote:api.github.com/<IP_ADDRESS>:443] FLUSH
[2020-11-03 15:44:04,515] TRACE {http.tracelog.upstream} - [id: 0xe66dfbb4, correlatedSource: n/a, host:/<IP_ADDRESS>:58420 - remote:api.github.com/<IP_ADDRESS>:443] READ COMPLETE
[2020-11-03 15:44:04,526] TRACE {http.tracelog.upstream} - [id: 0xe66dfbb4, correlatedSource: n/a, host:/<IP_ADDRESS>:58420 - remote:api.github.com/<IP_ADDRESS>:443] INBOUND: DefaultHttpResponse(decodeResult: success, version: HTTP/1.1)
HTTP/1.1 200 OK
Date: Tue, 03 Nov 2020 10:14:04 GMT
Content-Type: application/json; charset=utf-8
Content-Length: 11966
Server: GitHub.com
Status: 200 OK
Cache-Control: private, max-age=60, s-maxage=60
Vary: Accept, Authorization, Cookie, X-GitHub-OTP
ETag: "862a6613b342706f9a6100c58c8ea0b74c9a8eb9ff8ca15e22a22bece59d5661"
X-OAuth-Scopes: admin:enterprise, admin:gpg_key, admin:org, admin:org_hook, admin:public_key, admin:repo_hook, delete:packages, delete_repo, gist, notifications, read:packages, repo, user, workflow, write:discussion, write:packages
X-Accepted-OAuth-Scopes:
X-GitHub-Media-Type: github.v3; format=json
Link: <https://api.github.com/repositories/288615254/actions/workflows/build-master.yml/runs?per_page=1&page=2>; rel="next", <https://api.github.com/repositories/288615254/actions/workflows/build-master.yml/runs?per_page=1&page=198>; rel="last"
X-RateLimit-Limit: 5000
X-RateLimit-Remaining: 4992
X-RateLimit-Reset:<PHONE_NUMBER>
X-RateLimit-Used: 8
Access-Control-Expose-Headers: ETag, Link, Location, Retry-After, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Used, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval, X-GitHub-Media-Type, Deprecation, Sunset
Access-Control-Allow-Origin: *
Strict-Transport-Security: max-age=31536000; includeSubdomains; preload
X-Frame-Options: deny
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
Referrer-Policy: origin-when-cross-origin, strict-origin-when-cross-origin
Content-Security-Policy: default-src 'none'
Vary: Accept-Encoding, Accept, X-Requested-With
Vary: Accept-Encoding
X-GitHub-Request-Id: 0B8E:11D7:5050C2:6772B9:5FA12D6B
[2020-11-03 15:44:04,566] TRACE {http.tracelog.upstream} - [id: 0xe66dfbb4, correlatedSource: n/a, host:/<IP_ADDRESS>:58420 - remote:api.github.com/<IP_ADDRESS>:443] CLOSE
[2020-11-03 15:44:04,598] TRACE {http.tracelog.upstream} - [id: 0xe66dfbb4, correlatedSource: n/a, host:/<IP_ADDRESS>:58420 - remote:api.github.com/<IP_ADDRESS>:443] INBOUND: DefaultHttpContent(data: PooledSlicedByteBuf(ridx: 0, widx: 1370, cap: 1370/1370, unwrapped: PooledUnsafeDirectByteBuf(ridx: 1370, widx: 1370, cap: 1399)), decoderResult: success), 1370B
{"total_count":198,"workflow_runs":[{"id":343318360,"node_id":"MDExOldvcmtmbG93UnVuMzQzMzE4MzYw","head_branch":"master","head_sha":"66fbb060fc847e741cf43acda4c453951b6a0665","run_number":198,"event":"repository_dispatch","status":"completed","conclusion":"success","workflow_id":2406342,"check_suite_id":1442375125,"check_suite_node_id":"MDEwOkNoZWNrU3VpdGUxNDQyMzc1MTI1","url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/actions/runs/343318360","html_url":"https://github.com/ballerina-platform/module-ballerina-io/actions/runs/343318360","pull_requests":[],"created_at":"2020-11-03T09:40:00Z","updated_at":"2020-11-03T09:41:58Z","jobs_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/actions/runs/343318360/jobs","logs_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/actions/runs/343318360/logs","check_suite_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/check-suites/1442375125","artifacts_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/actions/runs/343318360/artifacts","cancel_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/actions/runs/343318360/cancel","rerun_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/actions/runs/343318360/rerun","workflow_url":"https://api.github.com/re
[2020-11-03 15:44:04,605] TRACE {http.tracelog.upstream} - [id: 0xe66dfbb4, correlatedSource: n/a, host:/<IP_ADDRESS>:58420 - remote:api.github.com/<IP_ADDRESS>:443] INBOUND: DefaultHttpContent(data: PooledSlicedByteBuf(ridx: 0, widx: 1370, cap: 1370/1370, unwrapped: PooledUnsafeDirectByteBuf(ridx: 1370, widx: 1370, cap: 1399)), decoderResult: success), 1370B
pos/ballerina-platform/module-ballerina-io/actions/workflows/2406342","head_commit":{"id":"66fbb060fc847e741cf43acda4c453951b6a0665","tree_id":"3b050ada9e6fdb8f625733f8afe8bf027363e4d2","message":"Merge pull request #32 from ballerina-platform/update-repository-dispatch-path\n\nUpdate repository dispatch path for dependent module builds","timestamp":"2020-11-03T05:33:05Z","author":{"name":"Thisaru Guruge","email":"thisaru@wso2.com"},"committer":{"name":"GitHub","email":"noreply@github.com"}},"repository":{"id":288615254,"node_id":"MDEwOlJlcG9zaXRvcnkyODg2MTUyNTQ=","name":"module-ballerina-io","full_name":"ballerina-platform/module-ballerina-io","private":false,"owner":{"login":"ballerina-platform","id":34733518,"node_id":"MDEyOk9yZ2FuaXphdGlvbjM0NzMzNTE4","avatar_url":"https://avatars2.githubusercontent.com/u/34733518?v=4","gravatar_id":"","url":"https://api.github.com/users/ballerina-platform","html_url":"https://github.com/ballerina-platform","followers_url":"https://api.github.com/users/ballerina-platform/followers","following_url":"https://api.github.com/users/ballerina-platform/following{/other_user}","gists_url":"https://api.github.com/users/ballerina-platform/gists{/gist_id}","starred_url":"https://api.github.com/users/ballerina-platform/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ballerina-platform/subscription
[2020-11-03 15:44:04,609] TRACE {http.tracelog.upstream} - [id: 0xe66dfbb4, correlatedSource: n/a, host:/<IP_ADDRESS>:58420 - remote:api.github.com/<IP_ADDRESS>:443] INBOUND: DefaultHttpContent(data: PooledSlicedByteBuf(ridx: 0, widx: 1370, cap: 1370/1370, unwrapped: PooledUnsafeDirectByteBuf(ridx: 1370, widx: 1370, cap: 1399)), decoderResult: success), 1370B
s","organizations_url":"https://api.github.com/users/ballerina-platform/orgs","repos_url":"https://api.github.com/users/ballerina-platform/repos","events_url":"https://api.github.com/users/ballerina-platform/events{/privacy}","received_events_url":"https://api.github.com/users/ballerina-platform/received_events","type":"Organization","site_admin":false},"html_url":"https://github.com/ballerina-platform/module-ballerina-io","description":"Ballerina io Module","fork":false,"url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io","forks_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/forks","keys_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/keys{/key_id}","collaborators_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/collaborators{/collaborator}","teams_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/teams","hooks_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/hooks","issue_events_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/issues/events{/number}","events_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/events","assignees_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/assignees{/user}","branches_url":"https://api.github.
[2020-11-03 15:44:04,615] TRACE {http.tracelog.upstream} - [id: 0xe66dfbb4, correlatedSource: n/a, host:/<IP_ADDRESS>:58420 - remote:api.github.com/<IP_ADDRESS>:443] INBOUND: DefaultHttpContent(data: PooledSlicedByteBuf(ridx: 0, widx: 1370, cap: 1370/1370, unwrapped: PooledUnsafeDirectByteBuf(ridx: 1370, widx: 1370, cap: 1399)), decoderResult: success), 1370B
com/repos/ballerina-platform/module-ballerina-io/branches{/branch}","tags_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/tags","blobs_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/git/blobs{/sha}","git_tags_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/git/tags{/sha}","git_refs_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/git/refs{/sha}","trees_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/git/trees{/sha}","statuses_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/statuses/{sha}","languages_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/languages","stargazers_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/stargazers","contributors_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/contributors","subscribers_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/subscribers","subscription_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/subscription","commits_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/commits{/sha}","git_commits_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/git/commits{/sha}","comments_url":"ht
[2020-11-03 15:44:04,619] TRACE {http.tracelog.upstream} - [id: 0xe66dfbb4, correlatedSource: n/a, host:/<IP_ADDRESS>:58420 - remote:api.github.com/<IP_ADDRESS>:443] INBOUND: DefaultHttpContent(data: PooledSlicedByteBuf(ridx: 0, widx: 1370, cap: 1370/1370, unwrapped: PooledUnsafeDirectByteBuf(ridx: 1370, widx: 1370, cap: 1399)), decoderResult: success), 1370B
tps://api.github.com/repos/ballerina-platform/module-ballerina-io/comments{/number}","issue_comment_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/issues/comments{/number}","contents_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/contents/{+path}","compare_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/compare/{base}...{head}","merges_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/merges","archive_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/{archive_format}{/ref}","downloads_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/downloads","issues_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/issues{/number}","pulls_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/pulls{/number}","milestones_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/milestones{/number}","notifications_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/notifications{?since,all,participating}","labels_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/labels{/name}","releases_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/releases{/id}","deployments_url":"https://api.github.
[2020-11-03 15:44:04,620] TRACE {http.tracelog.upstream} - [id: 0xe66dfbb4, correlatedSource: n/a, host:/<IP_ADDRESS>:58420 - remote:api.github.com/<IP_ADDRESS>:443] READ COMPLETE
[2020-11-03 15:44:04,622] TRACE {http.tracelog.upstream} - [id: 0xe66dfbb4, correlatedSource: n/a, host:/<IP_ADDRESS>:58420 - remote:api.github.com/<IP_ADDRESS>:443] USER_EVENT: SslCloseCompletionEvent(java.nio.channels.ClosedChannelException)
[2020-11-03 15:44:04,628] TRACE {http.tracelog.upstream} - [id: 0xe66dfbb4, correlatedSource: n/a, host:/<IP_ADDRESS>:58420 - remote:api.github.com/<IP_ADDRESS>:443] INACTIVE
[2020-11-03 15:44:04,629] TRACE {http.tracelog.upstream} - [id: 0xe66dfbb4, correlatedSource: n/a, host:/<IP_ADDRESS>:58420 - remote:api.github.com/<IP_ADDRESS>:443] CLOSE
[2020-11-03 15:44:04,630] TRACE {http.tracelog.upstream} - [id: 0xe66dfbb4, correlatedSource: n/a, host:/<IP_ADDRESS>:58420 - remote:api.github.com/<IP_ADDRESS>:443] UNREGISTERED

Root cause:
The response is received at the transport but an SSLException occurs when the channel gets closed. Due to that error, the exception is thrown from the external client action.
USER_EVENT: SslCloseCompletionEvent(java.nio.channels.ClosedChannelException)
This exception could occur if the connection was closed before finishing the SSL handshake, but as per the tracelog, the response is already received to the client.
Tested the same with { http1Settings : { keepAlive: http:KEEPALIVE_NEVER }} config to close the connection after the request/response completion to avoid connection reuse, but still getting the same exception.
[2020-11-03 15:44:04,069] TRACE {http.tracelog.upstream} - [id: 0xe66dfbb4, correlatedSource: n/a, host:/<IP_ADDRESS>:58420 - remote:api.github.com/<IP_ADDRESS>:443] READ COMPLETE
[2020-11-03 15:44:04,093] TRACE {http.tracelog.upstream} - [id: 0xe66dfbb4, correlatedSource: n/a, host:/<IP_ADDRESS>:58420 - remote:api.github.com/<IP_ADDRESS>:443] OUTBOUND: DefaultHttpRequest(decodeResult: success, version: HTTP/1.1)
GET /repos/ballerina-platform/module-ballerina-io/actions/workflows/build-master.yml/runs?per_page=1 HTTP/1.1
Authorization: Bearer <GITHUB_ACCESS_TOKEN>
host: api.github.com
user-agent: ballerina
connection: keep-alive
[2020-11-03 15:44:04,101] TRACE {http.tracelog.upstream} - [id: 0xe66dfbb4, correlatedSource: n/a, host:/<IP_ADDRESS>:58420 - remote:api.github.com/<IP_ADDRESS>:443] OUTBOUND: DefaultLastHttpContent(data: UnpooledByteBufAllocator$InstrumentedUnpooledUnsafeHeapByteBuf(ridx: 0, widx: 0, cap: 0), decoderResult: success), 0B
[2020-11-03 15:44:04,101] TRACE {http.tracelog.upstream} - [id: 0xe66dfbb4, correlatedSource: n/a, host:/<IP_ADDRESS>:58420 - remote:api.github.com/<IP_ADDRESS>:443] FLUSH
[2020-11-03 15:44:04,515] TRACE {http.tracelog.upstream} - [id: 0xe66dfbb4, correlatedSource: n/a, host:/<IP_ADDRESS>:58420 - remote:api.github.com/<IP_ADDRESS>:443] READ COMPLETE
[2020-11-03 15:44:04,526] TRACE {http.tracelog.upstream} - [id: 0xe66dfbb4, correlatedSource: n/a, host:/<IP_ADDRESS>:58420 - remote:api.github.com/<IP_ADDRESS>:443] INBOUND: DefaultHttpResponse(decodeResult: success, version: HTTP/1.1)
HTTP/1.1 200 OK
Date: Tue, 03 Nov 2020 10:14:04 GMT
Content-Type: application/json; charset=utf-8
Content-Length: 11966
Server: GitHub.com
Status: 200 OK
Cache-Control: private, max-age=60, s-maxage=60
Vary: Accept, Authorization, Cookie, X-GitHub-OTP
ETag: "862a6613b342706f9a6100c58c8ea0b74c9a8eb9ff8ca15e22a22bece59d5661"
X-OAuth-Scopes: admin:enterprise, admin:gpg_key, admin:org, admin:org_hook, admin:public_key, admin:repo_hook, delete:packages, delete_repo, gist, notifications, read:packages, repo, user, workflow, write:discussion, write:packages
X-Accepted-OAuth-Scopes:
X-GitHub-Media-Type: github.v3; format=json
Link: <https://api.github.com/repositories/288615254/actions/workflows/build-master.yml/runs?per_page=1&page=2>; rel="next", <https://api.github.com/repositories/288615254/actions/workflows/build-master.yml/runs?per_page=1&page=198>; rel="last"
X-RateLimit-Limit: 5000
X-RateLimit-Remaining: 4992
X-RateLimit-Reset:<PHONE_NUMBER>
X-RateLimit-Used: 8
Access-Control-Expose-Headers: ETag, Link, Location, Retry-After, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Used, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval, X-GitHub-Media-Type, Deprecation, Sunset
Access-Control-Allow-Origin: *
Strict-Transport-Security: max-age=31536000; includeSubdomains; preload
X-Frame-Options: deny
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
Referrer-Policy: origin-when-cross-origin, strict-origin-when-cross-origin
Content-Security-Policy: default-src 'none'
Vary: Accept-Encoding, Accept, X-Requested-With
Vary: Accept-Encoding
X-GitHub-Request-Id: 0B8E:11D7:5050C2:6772B9:5FA12D6B
[2020-11-03 15:44:04,566] TRACE {http.tracelog.upstream} - [id: 0xe66dfbb4, correlatedSource: n/a, host:/<IP_ADDRESS>:58420 - remote:api.github.com/<IP_ADDRESS>:443] CLOSE
[2020-11-03 15:44:04,598] TRACE {http.tracelog.upstream} - [id: 0xe66dfbb4, correlatedSource: n/a, host:/<IP_ADDRESS>:58420 - remote:api.github.com/<IP_ADDRESS>:443] INBOUND: DefaultHttpContent(data: PooledSlicedByteBuf(ridx: 0, widx: 1370, cap: 1370/1370, unwrapped: PooledUnsafeDirectByteBuf(ridx: 1370, widx: 1370, cap: 1399)), decoderResult: success), 1370B
{"total_count":198,"workflow_runs":[{"id":343318360,"node_id":"MDExOldvcmtmbG93UnVuMzQzMzE4MzYw","head_branch":"master","head_sha":"66fbb060fc847e741cf43acda4c453951b6a0665","run_number":198,"event":"repository_dispatch","status":"completed","conclusion":"success","workflow_id":2406342,"check_suite_id":1442375125,"check_suite_node_id":"MDEwOkNoZWNrU3VpdGUxNDQyMzc1MTI1","url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/actions/runs/343318360","html_url":"https://github.com/ballerina-platform/module-ballerina-io/actions/runs/343318360","pull_requests":[],"created_at":"2020-11-03T09:40:00Z","updated_at":"2020-11-03T09:41:58Z","jobs_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/actions/runs/343318360/jobs","logs_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/actions/runs/343318360/logs","check_suite_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/check-suites/1442375125","artifacts_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/actions/runs/343318360/artifacts","cancel_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/actions/runs/343318360/cancel","rerun_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/actions/runs/343318360/rerun","workflow_url":"https://api.github.com/re
[2020-11-03 15:44:04,605] TRACE {http.tracelog.upstream} - [id: 0xe66dfbb4, correlatedSource: n/a, host:/<IP_ADDRESS>:58420 - remote:api.github.com/<IP_ADDRESS>:443] INBOUND: DefaultHttpContent(data: PooledSlicedByteBuf(ridx: 0, widx: 1370, cap: 1370/1370, unwrapped: PooledUnsafeDirectByteBuf(ridx: 1370, widx: 1370, cap: 1399)), decoderResult: success), 1370B
pos/ballerina-platform/module-ballerina-io/actions/workflows/2406342","head_commit":{"id":"66fbb060fc847e741cf43acda4c453951b6a0665","tree_id":"3b050ada9e6fdb8f625733f8afe8bf027363e4d2","message":"Merge pull request #32 from ballerina-platform/update-repository-dispatch-path\n\nUpdate repository dispatch path for dependent module builds","timestamp":"2020-11-03T05:33:05Z","author":{"name":"Thisaru Guruge","email":"thisaru@wso2.com"},"committer":{"name":"GitHub","email":"noreply@github.com"}},"repository":{"id":288615254,"node_id":"MDEwOlJlcG9zaXRvcnkyODg2MTUyNTQ=","name":"module-ballerina-io","full_name":"ballerina-platform/module-ballerina-io","private":false,"owner":{"login":"ballerina-platform","id":34733518,"node_id":"MDEyOk9yZ2FuaXphdGlvbjM0NzMzNTE4","avatar_url":"https://avatars2.githubusercontent.com/u/34733518?v=4","gravatar_id":"","url":"https://api.github.com/users/ballerina-platform","html_url":"https://github.com/ballerina-platform","followers_url":"https://api.github.com/users/ballerina-platform/followers","following_url":"https://api.github.com/users/ballerina-platform/following{/other_user}","gists_url":"https://api.github.com/users/ballerina-platform/gists{/gist_id}","starred_url":"https://api.github.com/users/ballerina-platform/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ballerina-platform/subscription
[2020-11-03 15:44:04,609] TRACE {http.tracelog.upstream} - [id: 0xe66dfbb4, correlatedSource: n/a, host:/<IP_ADDRESS>:58420 - remote:api.github.com/<IP_ADDRESS>:443] INBOUND: DefaultHttpContent(data: PooledSlicedByteBuf(ridx: 0, widx: 1370, cap: 1370/1370, unwrapped: PooledUnsafeDirectByteBuf(ridx: 1370, widx: 1370, cap: 1399)), decoderResult: success), 1370B
s","organizations_url":"https://api.github.com/users/ballerina-platform/orgs","repos_url":"https://api.github.com/users/ballerina-platform/repos","events_url":"https://api.github.com/users/ballerina-platform/events{/privacy}","received_events_url":"https://api.github.com/users/ballerina-platform/received_events","type":"Organization","site_admin":false},"html_url":"https://github.com/ballerina-platform/module-ballerina-io","description":"Ballerina io Module","fork":false,"url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io","forks_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/forks","keys_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/keys{/key_id}","collaborators_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/collaborators{/collaborator}","teams_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/teams","hooks_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/hooks","issue_events_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/issues/events{/number}","events_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/events","assignees_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/assignees{/user}","branches_url":"https://api.github.
[2020-11-03 15:44:04,615] TRACE {http.tracelog.upstream} - [id: 0xe66dfbb4, correlatedSource: n/a, host:/<IP_ADDRESS>:58420 - remote:api.github.com/<IP_ADDRESS>:443] INBOUND: DefaultHttpContent(data: PooledSlicedByteBuf(ridx: 0, widx: 1370, cap: 1370/1370, unwrapped: PooledUnsafeDirectByteBuf(ridx: 1370, widx: 1370, cap: 1399)), decoderResult: success), 1370B
com/repos/ballerina-platform/module-ballerina-io/branches{/branch}","tags_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/tags","blobs_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/git/blobs{/sha}","git_tags_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/git/tags{/sha}","git_refs_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/git/refs{/sha}","trees_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/git/trees{/sha}","statuses_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/statuses/{sha}","languages_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/languages","stargazers_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/stargazers","contributors_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/contributors","subscribers_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/subscribers","subscription_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/subscription","commits_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/commits{/sha}","git_commits_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/git/commits{/sha}","comments_url":"ht
[2020-11-03 15:44:04,619] TRACE {http.tracelog.upstream} - [id: 0xe66dfbb4, correlatedSource: n/a, host:/<IP_ADDRESS>:58420 - remote:api.github.com/<IP_ADDRESS>:443] INBOUND: DefaultHttpContent(data: PooledSlicedByteBuf(ridx: 0, widx: 1370, cap: 1370/1370, unwrapped: PooledUnsafeDirectByteBuf(ridx: 1370, widx: 1370, cap: 1399)), decoderResult: success), 1370B
tps://api.github.com/repos/ballerina-platform/module-ballerina-io/comments{/number}","issue_comment_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/issues/comments{/number}","contents_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/contents/{+path}","compare_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/compare/{base}...{head}","merges_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/merges","archive_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/{archive_format}{/ref}","downloads_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/downloads","issues_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/issues{/number}","pulls_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/pulls{/number}","milestones_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/milestones{/number}","notifications_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/notifications{?since,all,participating}","labels_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/labels{/name}","releases_url":"https://api.github.com/repos/ballerina-platform/module-ballerina-io/releases{/id}","deployments_url":"https://api.github.
[2020-11-03 15:44:04,620] TRACE {http.tracelog.upstream} - [id: 0xe66dfbb4, correlatedSource: n/a, host:/<IP_ADDRESS>:58420 - remote:api.github.com/<IP_ADDRESS>:443] READ COMPLETE
[2020-11-03 15:44:04,622] TRACE {http.tracelog.upstream} - [id: 0xe66dfbb4, correlatedSource: n/a, host:/<IP_ADDRESS>:58420 - remote:api.github.com/<IP_ADDRESS>:443] USER_EVENT: SslCloseCompletionEvent(java.nio.channels.ClosedChannelException)
[2020-11-03 15:44:04,628] TRACE {http.tracelog.upstream} - [id: 0xe66dfbb4, correlatedSource: n/a, host:/<IP_ADDRESS>:58420 - remote:api.github.com/<IP_ADDRESS>:443] INACTIVE
[2020-11-03 15:44:04,629] TRACE {http.tracelog.upstream} - [id: 0xe66dfbb4, correlatedSource: n/a, host:/<IP_ADDRESS>:58420 - remote:api.github.com/<IP_ADDRESS>:443] CLOSE
[2020-11-03 15:44:04,630] TRACE {http.tracelog.upstream} - [id: 0xe66dfbb4, correlatedSource: n/a, host:/<IP_ADDRESS>:58420 - remote:api.github.com/<IP_ADDRESS>:443] UNREGISTERED

My concern is that even if the channel gets closed, we should return a proper http:ClientError. But in this case, the client panics. We need to avoid that. If this is a proper http:ClientError, that can be handled by the client (or the user) using resiliency stuff. Here, it just panics.

Fixed via commit, Hence closing the issue


OFFI-101: Frontend server support and interactive mode improvements

OFFI-101

Instead, I think a sample should be created in a separate OSOCE issue.


Is there an option that allows internalConsole to only output the results of the program?

Like the image above, I want only one word "false", but there are a lot of information in the internalConsole that is not important to me (yellow word) ), is there an option that allows me to turn off these unimportant information output and only show the results of the program?

You cannot reduce the output to zero, but many of the outputs can be disabled by setting 'logging' options in launch.json.

您不能将输出减少到零，但可以通过在 launch.json 中设置'logging'选项来禁用许多输出。

If I only want to output the program results, what should I fill in the logging?

@jiayaoO3O here is the documentation: https://github.com/OmniSharp/omnisharp-vscode/blob/master/debugger-launchjson.md#logging
VS Code will also give you intellisense if you just start typing and show you the available options.


Can't get it work

Have the exact lines from your example in my .vimrc and it's not showing open buffers. Any insight?
my .vimrc:
" lightline-bufferline integration
let g:lightline#bufferline#unnamed	= '[No Name]'
let g:lightline						= {}
let g:lightline.tabline				= {'left': [['buffers']], 'right': [['close']]}
let g:lightline.component_expand	= {'buffers': 'lightline#bufferline#buffers'}
let g:lightline.component_type		= {'buffers': 'tabsel'}

my Vim window:

That fixed it, thanks. Is there a way to make it match the status line in color? The bright white by default is too much.

You are using the default lightline colorscheme powerline. Changing it towombat or one should improve the colors:
let g:lightline.colorscheme = "one"

Guessing from your screenshots it looks like you might be using gruvbox as editor colorscheme.
In case you have https://github.com/morhetz/gruvbox installed you can change the lightline colorscheme to gruvbox using the following settings in your .vimrc:
set background=dark
colorscheme gruvbox
let g:lightline.colorscheme = "gruvbox"

I am using gruvbox, thank you!
On Tue, Sep 25, 2018, 3:13 PM Markus Engelbrecht<EMAIL_ADDRESS>wrote:

You are using the default lightline colorscheme powerline. Changing it to
wombat or one should improve the colors:
let g:lightline.colorscheme = "one"
Guessing from your screenshots it looks like you might be using gruvbox
as editor colorscheme.
In case you have https://github.com/morhetz/gruvbox installed you can
change the lightline colorscheme to gruvbox using the following settings in
your .vimrc:
set background=darkcolorscheme gruvboxlet g:lightline.colorscheme = "gruvbox"
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mgee/lightline-bufferline/issues/24#issuecomment-424466394,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACiUlv_0LJRVNdAcbDGGzjMY5BowP4DCks5ueoBvgaJpZM4W3F7D
.


make METRICS_DOMAIN optional when backend is not OpenCensus

Related to https://github.com/knative/pkg/pull/2614
We currently panic when METRICS_DOMAIN isn't set but this setting is only needed when using OpenCensus

/assign @jonathan-innis @k4leung4

/lgtm


Add Django tests

At minimum "the page loads without error".
Can use https://docs.djangoproject.com/en/3.2/howto/initial-data/#initial-data-via-fixtures like in https://github.com/open-contracting/covid-19-procurement-explorer-admin

Update: Most of the controller project is tested. Once #77 is done, the remaining views in the api project should be ported over. That will leave the exporter project, but we might not want to test it yet (#112).


Fixes #99

Changes the parser to recognize that svg elements are themselves in the
svg namespace and thus follow xml self-closing rules. In particular,
it is allowed to have a self-closing empty svg tag. Previously, this
would attempt to parse the rest of the document as internal the svg tag.

Thanks @winstonewert!


Reject a request to create a new workflow if a project is live and approved

LInked to https://github.com/zooniverse/Panoptes-Front-End/issues/274#issuecomment-112741781
If a project is live and has been approved for beta/launch by the zooniverse and a team member tries to add a new workflow it should reject the request. Modifying a live project should only be allowed under certain conditions and in consultation with the zooniverse team.

@edpaget should we disable modification to existing workflows as well? Ala, https://github.com/zooniverse/Panoptes-Front-End/pull/751

Will modifications to the Help text of an existing workflow will be allowed?

@vrooje we could allow certain updates and reject others like add a task, etc. What should be allowed?

As long as modifying help text is still tracked with a 0.x change in workflow, I think it should be fine to modify that. I think adding main text or tasks, or changing the order of tasks, should require confirmation/permission.
Am tagging @chrislintott as he may have a different opinion on the potential impact of changing help text mid-project.

I agree with @vrooje on this. While making changes to the help-text mid project might improve volunteer accuracy, I feel like those impacts would be relatively minor.

:+1: agree with @vrooje and @aliburchard - if you can track the minor version in the workflow, you could even evaluate the impact of the changes if you wanted :-)

Working on this now.

Oops -- now that I see it's coming together -- I think the ability to change the subject sets associated with the workflow should also be allowed.

A live workflow is locked for editing. Data can be added to a subject set.
@vrooje can you please open a new issue for editing a live workflow?

closed by #1022


add delete cache and get cache size function

Hey @YouHan26 I just pushed a new version that uses react-native-fetch-blob in place of react-native-fs as the author seems to have stop maintaining it.
This will probably cause conflicts with your version, if you want to resolve them and re-commit that'd be great.
If not, I can do it, no worries

yeah, I will re-commit later

Thanks @YouHan26 :)


Can you improve the ui

I love the them..I think is the best color scheme ever, I don't get tired of using it.
I was wondering if you planned to change the vscode ui to make it more in line with the theme colors?
something like this...I'm a terrible  designer...

Thanks!!

I've thought about it in the past but there's no chance that I would have any time these days. Microsoft won't even let me update the theme in the VS marketplace anymore because somehow my account got flagged and I was never able to log back in.
I'd also have to take a lot of liberties with modifying the UI. For the editor theme, I tried to remain 100% faithful to the emacs theme by @jasonm23 but there's no template for me to follow for the UI. I'd be more than happy if someone else decided to tackle the UI but like I said, I don't know if I could ever get my account re-enabled by Microsoft in order to update the package.

Not sure how easy it is to get your account unflagged but I might be able to help if you get stuck.

it would be great if Jason could help you recover your account, since it is unfair, and that you can or by helping you, improve the UI part of the theme that deserves it ... I love it ... regarding the template I can spend a fairly complete and You work on her.

@Poorchop if you email me we can work out if I can assist.

@jasonm23
If you help me we can create an improved version ...

Forgot to post here - I don't have your email Jason and I'm unlikely to have any free time for the next 4 months aside from a few hours here and there. If tate is willing to help out in the meantime, I think that would be great.

I'm email reachable via the Gmail domain.


Release EKS Go: v1.19.13-13

Increment release file to publish new EKS Go artifacts for v1.19.13-13

This is an incorrect duplicate of #1238


Replace NSURLConnection with NSURLSession.

Please replace NSURLConnection with NSURLSession.
The NSURLConnection class is DEPRECATED.
The NSURLConnection class should no longer be used.  NSURLSession is the replacement for NSURLConnection.
Some delegate methods don't work anymore.

PR: https://github.com/RestKit/RestKit/pull/2551


chore: update otel-collector to 0.36.0

Collector bumped to 0.36.0
Additional compatibility changes:

insecure relocated as per https://github.com/open-telemetry/opentelemetry-collector/pull/4063
mem-ballast-size-mib removed as per open-telemetry/opentelemetry-collector#3626

@bbeattie-phxlabs thanks for updating it, but I believe there must be more interface changes:

ballast_size_mib memory_memory option should be moved to ballast extension
may be required to switch base image to contrib because of jaeger and zipkin receivers added by default

Also please sign the CLA

Also looks like 0.36.0 wasn't pushed to dockerhub yet. So probably we should upgrade to 0.35.0 for now


Html blocks not wrapped in  when escapeHtml set to true

I'm using the Parser/HtmlRenderer combo with escapeHtml(true), but this leaves html blocks without being wrapped in a paragraph tag. Please see the following example. It seems like incorrect behaviour to me.
Parsing code
public String render(String text) {
    Parser parser = Parser.builder().build();
    HtmlRenderer renderer = HtmlRenderer.builder().escapeHtml(true).build();
    Node document = parser.parse(text);
    return renderer.render(document);
}

Input
This is a paragraph.

This is a paragraph.

html here

This is a paragraph.

This is a paragraph.

html here

This is a paragraph.

This is a paragraph.

html here

This is a paragraph.

Expected output

This is a paragraph.

This is a paragraph.

<div>html here</div>

This is a paragraph.

This is a paragraph.

<strong>html here</strong>

This is a paragraph.

This is a paragraph.

<p>html here</p>

This is a paragraph.

Actual output

This is a paragraph.

This is a paragraph.

<div>html here</div>

This is a paragraph.

This is a paragraph.

<strong>html here</strong>

This is a paragraph.

This is a paragraph.

<p>html here</p>

This is a paragraph.

Note that the line html here actually is wrapped, but the other two aren't.

This is a good point, thanks for raising this issue.
There is an explanation for why  gets wrapped in a
, it's because ... is what's called raw HTML in the spec or inline HTML, which is something that can be a part of a paragraph. To make this more obvious, you can also add some text before or after the strong element.
The
 however is a HTML block.
I think it makes sense to wrap escaped HTML blocks in a paragraph. I'll implement that in the next couple of days unless someone speaks up about it :). Or if you'd like to have a stab at it yourself, the code to change would be in the CoreHtmlNodeRenderer.

Just pushed a commit to implement this. It will be in the next release.


refactor: clean up API for removal policy across the library

Normalize how deletion policy is configured for stateful resources across the AWS Construct Library. - Simplify the model by removing the future-proofing of "RemovalPolicy.Forbid".
When RemovalPolicy.Destory is used, explicitly specify DeletionPolicy: Delete in CloudFormation (as oppose to relying on the fact the "Delete" is the default).

BREAKING CHANGE: multiple modules have been changed to use cdk.RemovalPolicy
to configure the resource's removal policy.

core: applyRemovalPolicy is now CfnResource.applyRemovalPolicy.
core: RemovalPolicy.Orphan has been renamed to Retain.
core: RemovalPolicy.Forbid has been removed, use Retain.
ecr: RepositoryProps.retain is now removalPolicy, and defaults to Retain instead of remove since ECR is a stateful resource
kms: KeyProps.retain is now removalPolicy
logs: LogGroupProps.retainLogGroup is now removalPolicy
logs: LogStreamProps.retainLogStream is now removalPolicy
rds: DatabaseClusterProps.deleteReplacePolicy is now removalPolicy
rds: DatabaseInstanceNewProps.deleteReplacePolicy is now removalPolicy

Pull Request Checklist

[ ] Testing

Unit test added (prefer not to modify an existing test, otherwise, it's probably a breaking change)
CLI change?: coordinate update of integration tests with team
cdk-init template change?: coordinated update of integration tests with team

[ ] Docs

jsdocs: All public APIs documented
README: README and/or documentation topic updated
Design: For significant features, design document added to design folder

[ ] Title and Description

Change type: title prefixed with fix, feat and module name in parens, which will appear in changelog
Title: use lower-case and doesn't end with a period
Breaking?: last paragraph: "BREAKING CHANGE: <describe what changed + link for details>"
Issues: Indicate issues fixed via: "Fixes #xxx" or "Closes #xxx"

[ ] Sensitive Modules (requires 2 PR approvers)

IAM Policy Document (in @aws-cdk/aws-iam)
EC2 Security Groups and ACLs (in @aws-cdk/aws-ec2)
Grant APIs (only if not based on official documentation with a reference)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license.

When RemovalPolicy.Destory is used, explicitly specify DeletionPolicy: Delete in CloudFormation (as oppose to relying on the fact the "Delete" is the default).

Why?

When RemovalPolicy.Destory is used, explicitly specify DeletionPolicy: Delete in CloudFormation (as oppose to relying on the fact the "Delete" is the default).

I think it's a better practice to be explicit about deletion of stateful resources.

I think it's a better practice to be explicit about deletion of stateful resources.

You're being explicit about it in a place where no-one should ever or is ever going to look, and even if they were the semantics are well-defined and well-understood. I don't really see the point. But if it makes you happy, not a big deal.


set correct port for sauceSeleniumAddress for HTTP protocol

when sauceSeleniumUseHttp is true, it should set the port to 80 instead of 443

signed CLA


Good first issues

New features:
- Users can now paste Npub as well as Hex formats.
- Nostr NIP-07 Login
- Users can now download all avatar images in a zip file.
- Optional image download
- Calendar Date range selection
- User profile displays with banner and avatar.

Added new constants and variables:

corsProxy for handling CORS issues
zapSendersResults to store fetched zap senders data

New functions:

convertToHexIfNpub: Converts npub to hex format
loadImage: Loads images with CORS proxy
downloadImageResult: Creates and downloads a PNG image of the zap senders grid
downloadAvatars: Downloads all avatar images as a ZIP file
login: Handles user login with Nostr extension
logout: Handles user logout
fetchUserProfile: Fetches and displays user profile information
updateLoginState: Updates UI based on login state

Modified existing functions:

getZapSenders: Now uses a date range instead of a fixed time range
fetchZapSenders:

Now uses date range input instead of time range
Stores results in zapSendersResults
Shows/hides download buttons based on results
Displays user avatars and names in a grid

New UI elements and interactions:

Added date range picker (Flatpickr) for selecting zap time range
Added "Download Result as Image" button
Added "Download Avatars as ZIP" button
Added login/logout functionality
Added user profile display

Event listeners:

Added listeners for new buttons (download image, download avatars, login, logout)

Styling changes:

Added styles for user profile display
Updated styles for the zap senders grid

External libraries:

Added Flatpickr for date range selection
Added JSZip and FileSaver for ZIP file creation and download

Error handling:

Improved error handling and messaging throughout the script

CORS handling:

Implemented CORS proxy for loading images from various sources

Code structure:

Reorganized code for better readability and maintainability
Implemented more modular approach with separate functions for different features

Logged Out

Logged In

Not sure if you need me to look at previous PRs, just this branch appears like this on firefox
A few notes:

Can we please revert back to dark mode instead of white background.
Download as image working, placeholders render as oval
Download html or zip not working.

Sharp module missing in package.json, added to this branch

Not sure if you need me to look at previous PRs, just this branch appears like this on firefox A few notes:

Can we please revert back to dark mode instead of white background.
Download as image working, placeholders render as oval
Download html or zip not working. (oddly zip download works on logout of profile, might just have taken a while? )

Darkmode enabled

Download image working (Default avatar changed, still apears ovaled but looks a bit better)

Download html working

ok gonna try to squeeze in time and test this today.

Looks grrrrreat! merging in.
open issues we can leave:

oval images
an option to add html file with local file referenced to the zip file


I'll fix this (if not tonight, then tomorrow). It's an easy fix.


Added temp images for handsfree

Docs Build status updates of commit be55338:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

mixed-reality-docs/images/models_icon_voicecommanding_100x100.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/models_icon_voicecommanding_200x200.png
:white_check_mark:Succeeded
View

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


Release 2.48.0

Thanks for the quick reviews! I'll make sure everything is good to go and then release first thing tomorrow morning.


Unbound DNS > Domain Overrides | Deleting multiple selected

When deleting multiple entries from the "Unbound DNS: Domain Overrides" only (top) one gets the deleted.
Not noticed it in previous versions.
To Reproduce

Goto: OPNsense > Services > Unbound DNS > Overrides > [Domain Overrides]
Have a couple of entries added if there are none.
Select all entries en click the 'trashcan' at the bottom right of the list.
Accept for deleting all entries.

Issue
Only the entry at the top of the list gets deleted.
Expected behavior
All selected entries should be removed at once.
Describe alternatives you considered
Tried with two and three entries, both cases deleting is from top down one entry at a time.
Environment
OPNsense-Business (DEC750) 23.4.1-8a631aed2

https://github.com/opnsense/core/commit/4e1562af51a54e9d7d810bda00d46d3d84f711eb should fix this, to try locally:
opnsense-patch 4e1562a

@arnocs Thanks for the report!

@arnocs thanks! we'll try to push it in the next release.


Add README for new conformance test suite.

Description of changes:
Here's a fairly complete user-guide for the proposed conformance testing DSL.  This is derived from the DSL that evolved from testing the denotational semantic model, extended significantly by ideas from @popematt to allow text and binary inputs.
This is formatted to render nicely on GitHub.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Do you have any thoughts about writer-focused tests? Currently, we test the writers by making sure that we can send data through round-trips of being serialized in different ways, and then deserialized back into the original values.

I don't, other than having the test framework perform serialization under various configurations, then parsing and verifying the expectations.
When combined with strong coverage of text and binary inputs (including erroneous/signals cases), that feels pretty good.  At very least, it's better than what we have currently.

It appears I don't have commit-rights on this repository; can somebody grant them and/or merge this?


Add functional arrilot/laravel-widgets

I liked the arrilot/laravel-widgets functionality.
Roughly add widgets through the module:

class ModuleServiceProvider

use Illuminate\Support\Facades\View;

function boot()

$widgets  = app_path().'/Modules/'.$module.'/Widgets';

if ($this->files->isDirectory($widgets)){
	$directories = $this->files->directories($widgets);
	foreach($directories as $Widjet){
		$WidjetViews = $Widjet."/Views";
		if ($this->files->isDirectory($WidjetViews)) {
			View::addNamespace('Module.'.$module.'.Widget', $WidjetViews);
		}
		$controllerList = $this->files->files($Widjet);
		foreach($controllerList as $controller){
			include_once($controller->getPathname());
		}
	}
}

laravel-project/
    app/
    └── Modules/
        └── FooBar/
            └── Widgets/
                └── Widget/
                     └── Views/
                          └── bar.blade.php
                     Bar.php

view('Module.FooBar.Widget::bar')

Hi @yanzlatov
I have no idea what the "arrilot/laravel-widgets" package is about and what the issue is here.
However, I'm about to release a v2. A lot of functionality (mainly generators) will be added.

Hi @yanzlatov
I have no idea what the "arrilot/laravel-widgets" package is about and what the issue is here.
However, I'm about to release a v2. A lot of functionality (mainly generators) will be added.

Package : https://github.com/arrilot/laravel-widgets/
No problems.
The implementation of the arrilot/laravel-widgets functions, the directory with the module (your package) is convenient for me.
For example, I’m doing a Blog module, it has a folder with widgets: the latest comments, the latest news, bookmarks, etc., which specifically relates to this module.

Ok, I see.
I will take al closer look at the widgets package and think about its general usability. For the time being I can not say if this will be implemented.
Anyways, thanks for your suggestion.

Ok, I see.
I will take al closer look at the widgets package and think about its general usability. For the time being I can not say if this will be implemented.
Anyways, thanks for your suggestion.

Ideally combine them in one package.
An example of the implementation of the interaction of two packages was thrown off by the code in the first message.


Arm after closing After deactivation of ALL door sensors,

Proposal
Within the door device type sensor there is a awesome option for 'Arm after closing After deactivation of this sensor, the remaining exit delay will automatically be skipped' I think it would be good if there was a feature that looked at all door sensors being closed then skipping the rest of the exit delay and turning system to armed.
use case: I have two doors and both are opened at time of arming. I start the arming process and close one door, once i proceed to close last door the system will arm and exit delay skipped. I think this would be common.

The behaviour could be changed, but I think it would be a step backwards.
I designed the behaviour with the expectation that 'all but one' door would be closed prior to arming, I think this is what most people would do (especially if you have an alarm panel at the entry).
I don't understand why you would arm your alarm before closing doors which are not used for exiting.
The problem with changing as you propose, is that in case a (second) door is unintentionally left open, the user would be informed of this after passing the entire exit delay.
I don't see a way to implement what you're asking without this side effect.

No problems I have two entries at back and front which we can enter/exit our property so was hoping for some logic to manage this. Appreciate response anyway. Awesome product
Dominic Borg
Head of IT, Asia Pacific | NEP Australia
NEP Broadcast Services | Australia
O:+61 2 9690 8125 | M:+61 499 370 408
@.***
www.nepgroup.com.auhttp://www.nepgroup.com.au
[cid:nep-logo-fc-grey-rgb-155x82_c3150264-3d19-4874-aa03-adb483ef3756.png]
We bring content to life.
CONFIDENTIALITY NOTICE & DISCLAIMER: This email may contain confidential, proprietary, or privileged information. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.
From: Niels Faber @.>
Sent: Tuesday, 2 August 2022 8:06 PM
To: nielsfaber/alarmo @.>
Cc: Dominic Borg @.>; Author @.>
Subject: Re: [nielsfaber/alarmo] Arm after closing After deactivation of ALL door sensors, (Issue #540)
EXTERNAL: This email originated from outside of the organization
The behaviour could be changed, but I think it would be a step backwards.
I designed the behaviour with the expectation that 'all but one' door would be closed prior to arming, I think this is what most people would do (especially if you have an alarm panel at the entry).
I don't understand why you would arm your alarm before closing doors which are not used for exiting.
The problem with changing as you propose, is that in case a (second) door is unintentionally left open, the user would be informed of this after passing the entire exit delay.
I don't see a way to implement what you're asking without this side effect.
—
Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https:/github.com/nielsfaber/alarmo/issues/540*issuecomment-1202282841__;Iw!!Ji65QoKJ03PKJY7K!EyU_S7Ip8a2xhq9FJrITfbihfUtiZz8ycEU0Qfntseq7GVC3zUV6yv_pvKSV-PxBPNG7fUpJ1zM9h1q3NOou1jQ$, or unsubscribehttps://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/A2EQOTNV4IJPZHKTQSOQEILVXDXHPANCNFSM55KJJSVA__;!!Ji65QoKJ03PKJY7K!EyU_S7Ip8a2xhq9FJrITfbihfUtiZz8ycEU0Qfntseq7GVC3zUV6yv_pvKSV-PxBPNG7fUpJ1zM9h1q3TDbhHiM$.
You are receiving this because you authored the thread.Message ID<EMAIL_ADDRESS>

"I have two doors and both are opened at time of arming. I start the arming process and close one door, once i proceed to close last door the system will arm and exit delay skipped. I think this would be common"
I have a similar setup, door 1 and 2 are open on arming, i then always close door 1 then finally door 2.
I simply set both door 1 & door 2 to use exit delay (therefore they can both be open when arming is initiated. But i only set door 2 to arm after closing, therefore working exactly as you wanted or am I missing something?

Pretty close but with your use case: I simply set both door 1 & door 2 to use exit delay (therefore they can both be open when arming is initiated. But I only set door 2 to arm after closing, therefore working exactly as you wanted or am I missing something?
We sometimes exit through door 1 or sometimes door 2 as my property allows entry/exit from both front and back. Probably not that common 😊
Dominic Borg
Head of IT, Asia Pacific | NEP Australia
NEP Broadcast Services | Australia
O:+61 2 9690 8125 | M:+61 499 370 408
@.***
www.nepgroup.com.auhttp://www.nepgroup.com.au
[cid:nep-logo-fc-grey-rgb-155x82_c3150264-3d19-4874-aa03-adb483ef3756.png]
We bring content to life.
CONFIDENTIALITY NOTICE & DISCLAIMER: This email may contain confidential, proprietary, or privileged information. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.
From: Pico @.>
Sent: Wednesday, 3 August 2022 8:33 AM
To: nielsfaber/alarmo @.>
Cc: Dominic Borg @.>; Author @.>
Subject: Re: [nielsfaber/alarmo] Arm after closing After deactivation of ALL door sensors, (Issue #540)
EXTERNAL: This email originated from outside of the organization
"I have two doors and both are opened at time of arming. I start the arming process and close one door, once i proceed to close last door the system will arm and exit delay skipped. I think this would be common"
I have a similar setup, door 1 and 2 are open on arming, i then always close door 1 then finally door 2.
I simply set both door 1 & door 2 to use exit delay (therefore they can both be open when arming is initiated. But i only set door 2 to arm after closing, therefore working exactly as you wanted or am I missing something?
—
Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https:/github.com/nielsfaber/alarmo/issues/540*issuecomment-1203277753__;Iw!!Ji65QoKJ03PKJY7K!FIjOH2-6SA5Yn1mJz04YP-qzvKjAbAIXgXuwgpriqr5wJYQXboSLKo7fvTnW7fupEnQWsgp2htOQlNjL03dxru8$, or unsubscribehttps://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/A2EQOTLYU6CLOEOHVSXKR4LVXGOZ7ANCNFSM55KJJSVA__;!!Ji65QoKJ03PKJY7K!FIjOH2-6SA5Yn1mJz04YP-qzvKjAbAIXgXuwgpriqr5wJYQXboSLKo7fvTnW7fupEnQWsgp2htOQlNjLfo9DMW4$.
You are receiving this because you authored the thread.Message ID<EMAIL_ADDRESS>


I want to create lookup script filter IN

hello I want to create lookup script filter IN
select Label from Ref where Parent_ID IN (select ID_Ref from Ref where Code='Ram')

Lookups don't take parameters.


proxy.config.ssl.server.TLSv1_3.cipher_suites don't really work

what's the point of that config setting when it does nothing?

Trafficserver 8.0.1:
CONFIG proxy.config.ssl.server.honor_cipher_order INT 1
CONFIG proxy.config.ssl.server.TLSv1_3.cipher_suites TLS_AES_128_GCM_SHA256:TLS_AES_256_GCM_SHA384:TLS_AES_128_CCM_SHA256:TLS_AES_128_CCM_8_SHA256:TLS_CHACHA20_POLY1305_SHA256
Firefox (show page informations): TLS_AES_256_GCM_SHA384, TLS1.3

httpd:
SSLHonorCipherOrder On
SSLCipherSuite TLSv1.3 TLS_AES_128_GCM_SHA256:TLS_AES_256_GCM_SHA384:TLS_AES_128_CCM_SHA256:TLS_AES_128_CCM_8_SHA256:TLS_CHACHA20_POLY1305_SHA256
Firefox (show page informations): TLS_AES_128_GCM_SHA256, TLS1.3

I tried your settings with ats-8.0.1 and firefox-66.0.2, but it looks like the config is working correctly. Also, I checked ServerHello TLS msg via Wireshark, ATS looks honer the settings.
Could you try again?

i restarted ATS multiple times and cleared cache

Restarting ATS should load the config. Do you have any error message like "invalid tls server cipher suites in records.config" ?
https://github.com/apache/trafficserver/blob/3b95fffa07c212e35218c024f33ed3321758c8b5/iocore/net/SSLUtils.cc#L1850

no, only WARNING: Unrecognized configuration value 'proxy.config.ssl.TLSv1_3' which is clear because 8.0.1 don't have that setting but sadly everything after 8.0.1 is completly ususable (https://github.com/apache/trafficserver/issues/4921#issuecomment-473451304)
fact is i have the same AES-256 ciphers as without the confgi setting at all on port 8443 while port 443 with the httpd-orgini directly perfeers the desired AES-128 one as both did before TLS 1.3 with the old cipher settings
[root@testserver:/var/log/trafficserver]$ cat diags.log
[Apr  9 03:17:03.220] {0x7f315c9ae6c0} STATUS: opened /var/log/trafficserver/diags.log
[Apr  9 03:17:03.220] {0x7f315c9ae6c0} NOTE: updated diags config
[Apr  9 03:17:03.252] {0x7f315c9ae6c0} NOTE: ip_allow.config updated, reloading
[Apr  9 03:17:03.257] {0x7f315c9ae6c0} NOTE: logging initialized[3], logging_mode = 1
[Apr  9 03:17:03.257] {0x7f315c9ae6c0} NOTE: loading plugin '/usr/lib64/trafficserver/plugins/compress.so'
[Apr  9 03:17:03.260] {0x7f315c9ae6c0} NOTE: loading plugin '/usr/lib64/trafficserver/plugins/header_rewrite.so'
[Apr  9 03:17:03.265] {0x7f315c9ae6c0} NOTE: loading /etc/trafficserver/ssl_server_name.yaml
[Apr  9 03:17:03.265] {0x7f315c9ae6c0} WARNING: /etc/trafficserver/ssl_server_name.yaml is empty
[Apr  9 03:17:03.265] {0x7f315c9ae6c0} NOTE: ssl_server_name.yaml done reloading!
[Apr  9 03:17:03.265] {0x7f315c9ae6c0} NOTE: loading SSL certificate configuration from /etc/trafficserver/ssl_multicert.config
[Apr  9 03:17:03.343] {0x7f315c9ae6c0} NOTE: ssl_multicert.config done reloading!
[Apr  9 03:17:03.372] {0x7f314ee23700} NOTE: recovery clearing offsets of Vol /var/cache/trafficserver/cache.db 16384:4094 : [2277376, 10665984] sync_serial 43 next 44
[Apr  9 03:17:03.373] {0x7f315c9ae6c0} WARNING: Unrecognized configuration value 'proxy.config.ssl.TLSv1_3'
[Apr  9 03:17:03.375] {0x7f3156ce1700} NOTE: cache enabled
[Apr  9 03:17:03.377] {0x7f315c9ae6c0} NOTE: traffic server running
[root@testserver:/var/log/trafficserver]$

nevermind
CONFIG proxy.config.ssl.server.TLSv1_3.cipher_suites TLS_AES_128_GCM_SHA256:TLS_AES_256_GCM_SHA384:TLS_AES_128_CCM_SHA256:TLS_AES_128_CCM_8_SHA256:TLS_CHACHA20_POLY1305_SHA256
versus
CONFIG proxy.config.ssl.server.TLSv1_3.cipher_suites STRING TLS_AES_128_GCM_SHA256:TLS_AES_256_GCM_SHA384:TLS_AES_128_CCM_SHA256:TLS_AES_128_CCM_8_SHA256:TLS_CHACHA20_POLY1305_SHA256
that is something ATS really could warn when the third column is not a valid type!

It warns for me.
Apr 27 08:37:15 s_sys@myhostname traffic_manager[17394]: {0x7fa412d08780} WARNING: Could not parse line at '/opt/bazinga/etc/trafficserver/records.config:169' -- skipping line: 'CONFIG proxy.config.ssl.server.cipher_suite ECDHE-ECDSA-AES1     28-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES256-SHA:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES128-SHA2     56:ECDHE-RSA-AES128-SHA256:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES128-SHA:DHE-RSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES256-SHA256:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA:AES256-SHA:AES128-SHA256:AES256-SHA256'


chore: preview config migration clean-up

chore: preview config migration clean-up
This PR:

fixes migration to not preserve usePrettyRefs at top level

usePrettyRefs for publishing resides in site config so it should be unset with the migration.

fixes issue with migration not unsetting keys that are listed in DEPRECATED_PATHS
updates dendron.yml in test-workspace

Manual testing

[x] Migration logic works as intended
[x] Preview and publishing configs correctly untangled

[x] Preview related configs honor the new preview.* namespae
[x] Publishing configs honor existing preserved keys

Pull Request Checklist
You can go to dendron pull requests to see full details for items in this checklist.
General
Quality Assurance

[~] Add a test for the new feature
[x] Make sure all the existing tests pass
[x] Do a spot check by running your feature with our test workspace
[x] If your tests involve running [[manual Testing|dendron://dendron.dendron-site/dendron.dev.qa.test#manual-testing]], make sure to update [[Test Workspace|dendron://dendron.dendron-site/dendron.dev.ref.test-workspace]] with any necessary notes/additions to perform manual test ^9jtWc6ov340p
[ ] After you submit your pull request, check the output of our integration test and make sure all tests pass

NOTE: If you running MacOS or Linux, pay special attention to the Windows output and vice versa if you are developing on Windows

Special Cases

[x] If your tests changes an existing snapshot, make sure that snapshots are updated
[~] If you are adding a new language feature (graphically visible in VS Code/preview/publishing), make sure that it is included in test-workspace. We use this to manually inspect new changes and for auto regression testing

Docs

[x] Make sure that the PR title follows our commit style
[x] Please summarize the feature or impact in 1-2 lines in the PR description
[x] If your change reflects documentation changes, also submit a PR to dendron-site and mention the doc PR link in your current PR

Special Cases
Git

[x] Make sure your branch names adhere to our commit style [[#^6zdCscSXs1MM]]

All PRs should start with [feat|fix|enhance|]/[{description-of-pr-in-kebab-case}]

eg. feat/add-thisthing

Github Issue

[~] If this pull request is addressing an existing issue, make sure to link this PR to the issue that it is resolving.
[~] If the resolution comes with a document update, link the docs PR to the issue as well.

DOCS: https://github.com/dendronhq/dendron-site/pull/287

exhaustive list of changes in config for reference
- useFMTitle?: boolean;
  - Renamed to `enableFMTitle` in preview namespace.
  - `enableFMTitle` now explicitly defaults to `true`.
  - Key is preserved until publishing related configurations are migrated.
  - Publishing still references `useFMTitle`.
- useNoteTitleForLink?: boolean;
  - Renamed to `enableNoteTitleForLink` in preview namespace.
  - `enableNoteTitleForLink` now explicitly defaults to `true`.
  - Key is preserved until publishing related configurations are migrated.
  - Publishing still references `useNoteTitleForLink`.
- mermaid?: boolean;
  - Renamed to `enableMermaid` in preview namespace.
  - `enableMermaid` now explicitly defaults to `true`.
  - Key is preserved until publishing related configurations are migrated.
  - Publishing still references `mermaid`.
- useNunjucks?: boolean;
  - This key is not deprecated.
- usePrettyRefs?: boolean;
  - Renamed to `enablePrettyRefs` in preview namespace.
  - `enablePrettyRefs` now explicitly defaults to `true`.
- useKatex?: boolean;
  - Renamed to `enableKatex` in preview namespace.
  - `enableKatex` now explicitly defaults to `true`.
  - Key is preserved until publishing related configurations are migrated.
  - Publishing still references `useKatex`.
- noLegacyNoteRef?: boolean;
  - This key is now deprecated.
  - Legacy note references are no longer supported.
- lookupDontBubbleUpCreateNew?: boolean;
  - Renamed to `bubbleUpCreateNew`.
  - Now part of `commands.lookup.note` namespace.
  - Now explicitly defaults to `true`.

Looks like we have some test failures

test and merge conflict fixed @kevinslin


Add a few lines on how to run Cypress

In our projects we usually have three Makefile commands:
make start-test-backend
make start-test-frontend
make start-test
```

Shall we add them to Volto core as well and document this here?

@tisto Volto's Makefile has them also. I'll adjust the doc to include them.


⚠ Mobitopup has degraded performance

In 9a45d5a, Mobitopup (https://napcard.voz.tech) experienced degraded performance:

HTTP code: 200
Response time: 5647 ms

Resolved: Mobitopup performance has improved in fd20321.


Implement Nlmsghdr builder

This PR adds builder for Nlmsghdr struct so that it would be a bit more ergonomic to create netlink packets. If you like the idea I'd be happy to implement something similar for other types as well.
This PR doesn't contain any breaking changes but I made some changes to Nlmsghdr based on your your comments in issues #83 and #86. You can find those changes in this commit https://github.com/ollipa/neli/commit/91843b3860a5f40ff899a2767bd0f2d0568b4adb (note that the code doesn't compile). I wonder if this is the way you were planning to change the API.

While I'm not opposed to the builder pattern, I'm not sure it's the best pattern for neli. I'm still considering it, but given that so many of the arguments are required, I don't see a huge benefit in the builder pattern over a new method for all of the structs that need them. While it is idiomatic in Rust, I see the main advantage being for structs that have a lot of optional arguments. If I eventually move in the direction of more optional arguments, I would be far more open to the builder pattern. What are your thoughts?

The way I see it, builder would make the API nicer to use and the code more readable especially when there are multiple Options passed to the struct like in Nlmsghdr. Maybe it would make sense to remove nl_len, nl_seq, and nl_pid from the constructor and provide setter methods for them instead?
Anyway, feel free to close this PR if you are not planning to add builders yet. Also, thank you for your work with the crate! I'm going to test out v0.5 soon and looking forward for more improvements :slightly_smiling_face:

I'm not opposed to discussing this, but before I'd be willing to merge this, I'd have to see a case for this being applicable for the other structs in neli too. I can imagine a few different patterns that could be useful in this context and when I release v0.6.0, I just want to make sure that the pattern is uniform. For example, I would need to look at the rtnl.rs module in particular to see how many of those structs have reasonable defaults for fields. If you can make the case for most of the structs in neli having reasonable defaults for at least some of the fields, this could absolutely be an improvement, but if not, I'd prefer to take the approach of covering the majority of common defaults each with an appropriately named method such as this method in libnl but for message construction as opposed to sending. Providing a set of methods that fill in defaults for common use cases like that method may also be an option and I want to make sure that we discuss it in more detail before deciding. Given that this is targeting v0.6.0, it may be a while until I make a decision, but I'd love to keep chatting about it until then!

Okay, got it! It is definitely a good idea to keep the API consistent. I'll update my project to neli 0.5 and then try to think how builder pattern (or some alternative approach) could work with other structs.

Perfect! Please do keep me posted because if we can implement a consistent builder pattern, that could absolutely be an improvement. I'd love to work with you on this so feel free to update me with any future ideas or proposals in issue #83. I think that's the appropriate place to follow up on any planning.


added python-pyaudio

for speech recognition using http://mary.dfki.de/index.html

I added debian and fedora rules:
https://apps.fedoraproject.org/packages/pyaudio/
https://packages.debian.org/jessie/python-pyaudio
http://packages.ubuntu.com/trusty/python-pyaudio


sdk(sync-agent): remove unneeded operations on Member

Why we need to update a member that aren't being used?

we can know that the member is "being used" if it is in the members record, since when you get it, we create a record for it.

actually, let's keep it for now, its way easy to create a mental model and find some bugs


Fix broken link in README

Update API documentation location

This change is

Thanks for the PR @rhwood !


Mobs doesn't increase their lvl

Hi im playing wit h my friends on minecraft server in 1.19.2, and we have a problem. Mobs stopped increasing their lvl at 31

Yes, by default the mobs max strength increase is tripple, check out the config settings, something with max


iot2050setup: Update default setup and hold time for advanced board

the usb-serial we are using is cp2102n, when set to rs485 mode, setup time and hold time should refer the transceiver's datasheet (sp339e https://assets.maxlinear.com/web/documents/sp339e.pdf)
Discuss with FAE,Setup time should be over tDZH 1us,hold time should be over tDPLH 1us.
Currently, default value is 0xaa, this time is too long for the hold and setup time. This will affect the efficiency of communication and cause data loss.
And according to the field feedback, this default value set to 0x05 us meets most of the scenarios.
Signed-off-by: chao zeng<EMAIL_ADDRESS>

How does this go along with switchserialmode? Shouldn't such parameter also be (or become) defaults on the command line?

Seems induOs just use this tool to configure the serial port?
integrate this change the switchserialmode tool seems more reasonable.
I would refine this PR.

Yes, iot2050setup is not used in Industrial OS.
I would keep the times configurable via switchserialport and possibly iot2050setup, but known-to-work default values should then indeed come already via switchserialmode.

Currently, the default value is set by switchserialmode. and in the iot2050setup also can change this value.

Better to follow the 52/70 rule for the commit message.
For VS Code, rewrap saves my life.

Better to follow the 52/70 rule for the commit message.
For VS Code, rewrap saves my life.

I will try this useful tool


virtctl: Do not log wrapped ssh command by default

What this PR does / why we need it:
This changes the verbosity of the wrapped ssh command to 3 so it is no
longer logged by default.
Release note:

virtctl: Do not log wrapped ssh command by default

Thanks for the improvement.
cc @geetikakay

/lgtm

/retest


Fix standalone validation + progress bars

fix https://github.com/NeurodataWithoutBorders/nwb-guide/issues/860#issuecomment-2168528690
This PR fixes the issue we saw on standalone validation by using the same /inspect function for all file and folder selection combinations. This also allows uniform rendering of progress bars—which is fixed here as well.

@garrettmflynn Tests are failing

LGTM, thanks!


VirtualBox: Delete machine in 'PAUSED' state

fixed #2335

I changed code so i reply to @dgageot here...
I think other state have a worth to try kill.
i'm sure about 'Stopping' State but in the stop function. after send command still state.Running used for check stopped or not. so may be state.Stopping is not used for virtual box.
	if err := d.vbm("controlvm", d.MachineName, "acpipowerbutton"); err != nil {
		return err
	}
	for {
		s, err := d.GetState()
		if err != nil {
			return err
		}
		if s == state.Running {
			time.Sleep(1 * time.Second)
		} else {
			break
		}
	}

	d.IPAddress = ""

	return nil
}

LGTM. @jeanlaurent PTAL

LGTM please provide a test next time.


Pluging won't work anymore with next 13.3.1 (tested with up to canary 17)

Maybe related to #39
I've opened a similar issue yesterday for https://github.com/blitz-js/next-superjson-plugin/issues/76 that has been fixed by https://github.com/blitz-js/next-superjson-plugin/pull/77

Yes, it's duplicate of https://github.com/lingui/swc-plugin/issues/39


getline available?

Hi,
Is the awk's function getline somehow available?
I'm researching the tools that I can use for this,
https://groups.google.com/d/msg/golang-nuts/tf4aDQ1Hn_c/pemlt7brBAAJ
and am thinking that your awk package might be the only viable option for me now, to parse my xml by awk.
However, I do badly need the awk's  getline function, because "when I'm at a certain token, and want to print out the entire raw xml as-is, the standard encoding/xml lib doesn't even allow me to" (from above url).
So I badly need to supply my own loop on meeting certain xml tokens, reading/modifying/dumping lines until the end xml tag is met.
Can you provide an example on how to do self getline loop please?
Thanks

I think the funtionality of getline is there already, we just need to expose it as Getline for the time being, I meant, the funtionality of getline also includes reading from another file, which is nice to have, as I'm using it in my other awk script now.
Thanks again.

Hm?
Project abandoned?

On 12/01/2015 09:55 AM, suntong wrote:

Hm?
Project abandoned?

Working on getline…be patient.
— Scott

Oh, that's great news. Sorry to have been impatient because I didn't know.
Thanks for the effort!

I believe I have getline working as of the latest commit (81db0f4).  The new Script.GetLine method is intended to follow the semantics of AWK's getline fairly closely.
— Scott

Excellent!!! I'll try it out right away. Thanks a lot!

FTA, forgot to mention that I've tested with my example on 2 Dec 2015.

Glad to hear that everything's working.  Thanks for letting me know.
— Scott


[BACKLOG-18169] Added pentaho server to run configuration

Build Completed
:x: This pull request has errors. They will need to be addressed before it can be accepted. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
mvn -B -fn -f 'pom.xml' -pl 'plugins/engine-configuration/ui,plugins/engine-configuration/impl,plugins/engine-configuration/api' -P '!assemblies' -amd clean install && mvn -B -f 'pom.xml' -pl 'plugins/engine-configuration/ui,plugins/engine-configuration/impl,plugins/engine-configuration/api' -P '!assemblies' -amd site

Cleanup Commands
mvn -B -f 'pom.xml' -pl 'plugins/engine-configuration/ui,plugins/engine-configuration/impl,plugins/engine-configuration/api' -P '!assemblies' -amd build-helper:remove-project-artifact

Changed files
  plugins/engine-configuration/api/pom.xml
  plugins/engine-configuration/api/src/main/java/org/pentaho/di/engine/configuration/api/RunConfiguration.java
  plugins/engine-configuration/api/src/main/java/org/pentaho/di/engine/configuration/api/RunConfigurationDialog.java
  plugins/engine-configuration/api/src/main/java/org/pentaho/di/engine/configuration/api/RunConfigurationUI.java
  plugins/engine-configuration/impl/pom.xml
  plugins/engine-configuration/impl/src/main/java/org/pentaho/di/engine/configuration/impl/pentaho/DefaultRunConfiguration.java
  plugins/engine-configuration/impl/src/main/java/org/pentaho/di/engine/configuration/impl/pentaho/DefaultRunConfigurationExecutor.java
  plugins/engine-configuration/impl/src/main/java/org/pentaho/di/engine/configuration/impl/pentaho/DefaultRunConfigurationUI.java
  plugins/engine-configuration/impl/src/main/java/org/pentaho/di/engine/configuration/impl/pentaho/scheduler/SchedulerRequest.java
  plugins/engine-configuration/impl/src/main/java/org/pentaho/di/engine/configuration/impl/pentaho/scheduler/SpoonUtil.java
  plugins/engine-configuration/impl/src/main/java/org/pentaho/di/engine/configuration/impl/spark/SparkRunConfiguration.java
  plugins/engine-configuration/impl/src/main/java/org/pentaho/di/engine/configuration/impl/spark/SparkRunConfigurationUI.java
  plugins/engine-configuration/impl/src/main/resources/org/pentaho/di/engine/configuration/impl/pentaho/messages/messages_en_US.properties
  plugins/engine-configuration/impl/src/main/resources/org/pentaho/di/engine/configuration/impl/spark/messages/messages_en_US.properties
  plugins/engine-configuration/ui/src/main/java/org/pentaho/di/engine/ui/RunConfigurationDialog.java
  plugins/engine-configuration/ui/src/main/resources/org/pentaho/di/engine/ui/messages/messages_en_US.properties

Unit test coverage change
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.
org.pentaho.di.engine.configuration.impl.pentaho.DefaultRunConfiguration

Complexity Change: -3.85%:small_red_triangle_down:
Instruction Change: -4.50%:small_red_triangle_down:
Line Change: -2.27%:small_red_triangle_down:
Method Change: -3.85%:small_red_triangle_down:

org.pentaho.di.engine.configuration.impl.pentaho.DefaultRunConfigurationExecutor

Branch Change: -20.83%:small_red_triangle_down:
Complexity Change: -19.05%:small_red_triangle_down:
Instruction Change: -12.79%:small_red_triangle_down:
Line Change: -14.08%:small_red_triangle_down:

org.pentaho.di.engine.configuration.impl.spark.SparkRunConfiguration

Complexity Change: -8.18%:small_red_triangle_down:
Instruction Change: -11.50%:small_red_triangle_down:
Line Change: -5.64%:small_red_triangle_down:
Method Change: -8.18%:small_red_triangle_down:

org.pentaho.di.engine.configuration.impl.spark.SparkRunConfigurationExecutor

Branch Change: -4.55%:small_red_triangle_down:
Complexity Change: -7.14%:small_red_triangle_down:
Instruction Change: -.57%:small_red_triangle_down:

Checkstyle violations
The code submitted is not complying with one or more of our guidelines. To perform these checks locally, please use this tool.
/home/buildguy/project/plugins/engine-configuration/impl/src/main/java/org/pentaho/di/engine/configuration/impl/pentaho/DefaultRunConfiguration.java

:heavy_exclamation_mark: Unused import - org.eclipse.swt.widgets.Composite. at Line: 27 Column: 8

/home/buildguy/project/plugins/engine-configuration/impl/src/main/java/org/pentaho/di/engine/configuration/impl/pentaho/DefaultRunConfigurationExecutor.java

:heavy_exclamation_mark: Unused import - java.io.UnsupportedEncodingException. at Line: 27 Column: 8

:heavy_exclamation_mark: Unused import - java.util.Base64. at Line: 28 Column: 8

:heavy_exclamation_mark: Unused import - org.apache.http.client.HttpClient. at Line: 29 Column: 8

:heavy_exclamation_mark: Unused import - org.apache.http.client.methods.HttpPost. at Line: 30 Column: 8

:heavy_exclamation_mark: Unused import - org.apache.http.entity.StringEntity. at Line: 31 Column: 8

:heavy_exclamation_mark: Unused import - org.apache.http.impl.client.HttpClients. at Line: 32 Column: 8

:heavy_exclamation_mark: Unused import - org.pentaho.di.ui.spoon.Spoon. at Line: 44 Column: 8

Build Completed
:fire: This pull request has some issues. It would be preferable to fix them in order for it to be just perfect. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
mvn -B -fn -f 'pom.xml' -pl 'plugins/engine-configuration/ui,plugins/engine-configuration/impl,plugins/engine-configuration/api' -P '!assemblies' -amd clean install && mvn -B -f 'pom.xml' -pl 'plugins/engine-configuration/ui,plugins/engine-configuration/impl,plugins/engine-configuration/api' -P '!assemblies' -amd site

Cleanup Commands
mvn -B -f 'pom.xml' -pl 'plugins/engine-configuration/ui,plugins/engine-configuration/impl,plugins/engine-configuration/api' -P '!assemblies' -amd build-helper:remove-project-artifact

Changed files
  plugins/engine-configuration/api/pom.xml
  plugins/engine-configuration/api/src/main/java/org/pentaho/di/engine/configuration/api/RunConfiguration.java
  plugins/engine-configuration/api/src/main/java/org/pentaho/di/engine/configuration/api/RunConfigurationDialog.java
  plugins/engine-configuration/api/src/main/java/org/pentaho/di/engine/configuration/api/RunConfigurationUI.java
  plugins/engine-configuration/impl/pom.xml
  plugins/engine-configuration/impl/src/main/java/org/pentaho/di/engine/configuration/impl/pentaho/DefaultRunConfiguration.java
  plugins/engine-configuration/impl/src/main/java/org/pentaho/di/engine/configuration/impl/pentaho/DefaultRunConfigurationExecutor.java
  plugins/engine-configuration/impl/src/main/java/org/pentaho/di/engine/configuration/impl/pentaho/DefaultRunConfigurationUI.java
  plugins/engine-configuration/impl/src/main/java/org/pentaho/di/engine/configuration/impl/pentaho/scheduler/SchedulerRequest.java
  plugins/engine-configuration/impl/src/main/java/org/pentaho/di/engine/configuration/impl/pentaho/scheduler/SpoonUtil.java
  plugins/engine-configuration/impl/src/main/java/org/pentaho/di/engine/configuration/impl/spark/SparkRunConfiguration.java
  plugins/engine-configuration/impl/src/main/java/org/pentaho/di/engine/configuration/impl/spark/SparkRunConfigurationUI.java
  plugins/engine-configuration/impl/src/main/resources/org/pentaho/di/engine/configuration/impl/pentaho/messages/messages_en_US.properties
  plugins/engine-configuration/impl/src/main/resources/org/pentaho/di/engine/configuration/impl/spark/messages/messages_en_US.properties
  plugins/engine-configuration/ui/src/main/java/org/pentaho/di/engine/ui/RunConfigurationDialog.java
  plugins/engine-configuration/ui/src/main/resources/org/pentaho/di/engine/ui/messages/messages_en_US.properties

Unit test coverage change
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.
org.pentaho.di.engine.configuration.impl.pentaho.DefaultRunConfiguration

Complexity Change: -3.85%:small_red_triangle_down:
Instruction Change: -4.50%:small_red_triangle_down:
Line Change: -2.27%:small_red_triangle_down:
Method Change: -3.85%:small_red_triangle_down:

org.pentaho.di.engine.configuration.impl.pentaho.DefaultRunConfigurationExecutor

Branch Change: -20.83%:small_red_triangle_down:
Complexity Change: -19.05%:small_red_triangle_down:
Instruction Change: -12.79%:small_red_triangle_down:
Line Change: -14.08%:small_red_triangle_down:

org.pentaho.di.engine.configuration.impl.spark.SparkRunConfiguration

Complexity Change: -8.18%:small_red_triangle_down:
Instruction Change: -11.50%:small_red_triangle_down:
Line Change: -5.64%:small_red_triangle_down:
Method Change: -8.18%:small_red_triangle_down:

org.pentaho.di.engine.configuration.impl.spark.SparkRunConfigurationExecutor

Branch Change: -4.55%:small_red_triangle_down:
Complexity Change: -7.14%:small_red_triangle_down:
Instruction Change: -.57%:small_red_triangle_down:


Azure PowerShell deployment

incorrect powershell  in codeblock
missing example

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

ID: f7fd1350-6158-4eb0-b41b-5c7b9a776e96
Version Independent ID: 713b91b9-d810-aca5-0ab4-00e0a4ee0fed
Content: Azure Key Vault VM Extension for Linux - Azure Virtual Machines
Content Source: articles/virtual-machines/extensions/key-vault-linux.md
Service: virtual-machines
Sub-service: extensions
GitHub Login: @msmbaldwin
Microsoft Alias: mbaldwin

@meightymike
Thanks for the feedback! I have assigned the issue to content author to check and update the document as appropriate.

@msmbaldwin
Can you please check and add your comments on this doc update request as applicable.

Thanks for your dedication to our documentation. Unfortunately, at this time we have been unable to review your issue in a timely manner and we sincerely apologize for the delayed response. We are closing this issue for now, but if you feel that it's still a concern, please respond and let us know. If you determine another possible update to our documentation, please don't hesitate to reach out again. #please-close