runtime: improper preempt points inserting in runtimeNano

Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (go version)?
Go 1.9.2
Does this issue reproduce with the latest release?
Yes.
What operating system and processor architecture are you using (go env)?
Linux AMD64
What did you do?
I find three improper functions located in runtime/time.go:302-311, and runtime/sema.go:608-611 in Go 1.9.2.
// time.go
//go:linkname poll_runtimeNano internal/poll.runtimeNano
func poll_runtimeNano() int64 {
	return nanotime()
}

//go:linkname time_runtimeNano time.runtimeNano
func time_runtimeNano() int64 {
	return nanotime()
}

and
// sema.go
//go:linkname sync_nanotime sync.runtime_nanotime
func sync_nanotime() int64 {
	return nanotime()
}

These two functions are used to implement runtimeNano in packages time and poll. While the nanotime is implemented in assembly, and this function does not have preempt points.
0000000000452c50 <runtime.nanotime>:
  452c50:	48 83 ec 18          	sub    $0x18,%rsp
  452c54:	48 89 6c 24 10       	mov    %rbp,0x10(%rsp)
  452c59:	48 8d 6c 24 10       	lea    0x10(%rsp),%rbp
  452c5e:	48 8b 05 3b 8f 10 00 	mov    0x108f3b(%rip),%rax        # 55bba0 <runtime.__vdso_clock_gettime_sym>
  452c65:	48 83 f8 00          	cmp    $0x0,%rax
  452c69:	74 2d                	je     452c98 <runtime.nanotime+0x48>
  452c6b:	bf 01 00 00 00       	mov    $0x1,%edi
  452c70:	48 8d 34 24          	lea    (%rsp),%rsi
  452c74:	ff d0                	callq  *%rax
  452c76:	48 8b 04 24          	mov    (%rsp),%rax
  452c7a:	48 8b 54 24 08       	mov    0x8(%rsp),%rdx
  452c7f:	48 69 c0 00 ca 9a 3b 	imul   $0x3b9aca00,%rax,%rax
  452c86:	48 01 d0             	add    %rdx,%rax
  452c89:	48 89 44 24 20       	mov    %rax,0x20(%rsp)
  452c8e:	48 8b 6c 24 10       	mov    0x10(%rsp),%rbp
  452c93:	48 83 c4 18          	add    $0x18,%rsp
  452c97:	c3                   	retq
  452c98:	48 8d 3c 24          	lea    (%rsp),%rdi
  452c9c:	31 f6                	xor    %esi,%esi
  452c9e:	48 8b 05 23 84 0d 00 	mov    0xd8423(%rip),%rax        # 52b0c8 <runtime.__vdso_gettimeofday_sym>
  452ca5:	ff d0                	callq  *%rax
  452ca7:	48 8b 04 24          	mov    (%rsp),%rax
  452cab:	8b 54 24 08          	mov    0x8(%rsp),%edx
  452caf:	48 69 d2 e8 03 00 00 	imul   $0x3e8,%rdx,%rdx
  452cb6:	48 69 c0 00 ca 9a 3b 	imul   $0x3b9aca00,%rax,%rax
  452cbd:	48 01 d0             	add    %rdx,%rax
  452cc0:	48 89 44 24 20       	mov    %rax,0x20(%rsp)
  452cc5:	48 8b 6c 24 10       	mov    0x10(%rsp),%rbp
  452cca:	48 83 c4 18          	add    $0x18,%rsp
  452cce:	c3                   	retq
  452ccf:	cc                   	int3

It makes sense. Because nanotime is used to get time in nano precision. But the time.runtimeNano, poll.runtime.Nano and sync.runtime_nanotime can not follow this. Because There three functions are inserted preempt points, which will make the nanotime measurament becomes unbelievable. For examples, time.runtimeNano is below:
0000000000443b60 <time.runtimeNano>:
  443b60:	64 48 8b 0c 25 f8 ff 	mov    %fs:0xfffffffffffffff8,%rcx
  443b67:	ff ff
  443b69:	48 3b 61 10          	cmp    0x10(%rcx),%rsp
  443b6d:	76 26                	jbe    443b95 <time.runtimeNano+0x35>
  443b6f:	48 83 ec 10          	sub    $0x10,%rsp
  443b73:	48 89 6c 24 08       	mov    %rbp,0x8(%rsp)
  443b78:	48 8d 6c 24 08       	lea    0x8(%rsp),%rbp
  443b7d:	e8 ce f0 00 00       	callq  452c50 <runtime.nanotime>
  443b82:	48 8b 04 24          	mov    (%rsp),%rax
  443b86:	48 89 44 24 18       	mov    %rax,0x18(%rsp)
  443b8b:	48 8b 6c 24 08       	mov    0x8(%rsp),%rbp
  443b90:	48 83 c4 10          	add    $0x10,%rsp
  443b94:	c3                   	retq
  443b95:	e8 16 bb 00 00       	callq  44f6b0 <runtime.morestack_noctxt>
  443b9a:	eb c4                	jmp    443b60 <time.runtimeNano>
  443b9c:	cc                   	int3
  443b9d:	cc                   	int3
  443b9e:	cc                   	int3
  443b9f:	cc                   	int3

Then I changes the code
From
//go:linkname time_runtimeNano time.runtimeNano
func time_runtimeNano() int64 {
	return nanotime()
}

To
//go:nosplit
//go:linkname time_runtimeNano time.runtimeNano
func time_runtimeNano() int64 {
	return nanotime()
}

Then, the assembly of time.runtimeNano becomes
0000000000443b60 <time.runtimeNano>:
  443b60:	48 83 ec 10          	sub    $0x10,%rsp
  443b64:	48 89 6c 24 08       	mov    %rbp,0x8(%rsp)
  443b69:	48 8d 6c 24 08       	lea    0x8(%rsp),%rbp
  443b6e:	e8 cd f0 00 00       	callq  452c40 <runtime.nanotime>
  443b73:	48 8b 04 24          	mov    (%rsp),%rax
  443b77:	48 89 44 24 18       	mov    %rax,0x18(%rsp)
  443b7c:	48 8b 6c 24 08       	mov    0x8(%rsp),%rbp
  443b81:	48 83 c4 10          	add    $0x10,%rsp
  443b85:	c3                   	retq
  443b86:	cc                   	int3
  443b87:	cc                   	int3
  443b88:	cc                   	int3
  443b89:	cc                   	int3
  443b8a:	cc                   	int3
  443b8b:	cc                   	int3
  443b8c:	cc                   	int3
  443b8d:	cc                   	int3
  443b8e:	cc                   	int3
  443b8f:	cc                   	int3

This kind of version of time.runtimeNano is quite closer to runtime.nanotime.

By "improper" do you just mean that this could be faster? Or is there a bug?
/cc @aclements

I think this could make it more accurate. It's not a bug.

Marking these nosplit would not help with their accuracy. For one, nothing's stopping the OS from preempting the process at any point, which could potentially throw off any measurements no matter what we do. Also, these functions aren't exposed to user code, and anything that does expose their results to user space (like time.Now()) has its own preemption points. Even supposing we propagated nosplit all the way up to exported functions, which is already getting a little ridiculous, it would be really hard to use from user code without introducing preemption points in the user code. The only way I can think of is doing a duration measurement of something that's very carefully written to not have it's own preemption points:
start := time.Now()
... something that doesn't have preemption points ...
duration := time.Now().Sub(start)

But this is so dependent on the details of the compiler, linker, and runtime that I really don't want to expose any of this (e.g., if the above code used time.Since it would be broken again). Especially since the OS could swoop in at any time and make it all irrelevant anyway.
Finally, there's the fact that we want to have a lot more preemption points, not fewer, to solve #10958.


Store and display date and time of when tasks are added

Currently, tasks can't be tracked with the date they were added on. Implement one such feature.

I would love to work on this


Topic/if

This change set contains IF / ELSE and nested structure changes to full fill issues:

https://github.com/robotframework/robotframework/issues/3074
https://github.com/robotframework/robotframework/issues/3079

After this change:

RF will have a native support for IF blocks
FOR loops and IFs can be used and nested together in a free order

Note about dryrun:
IF creates a "new" problem of recursive execution because if all branches are unconditionally all the time executed (as would be the case in dryrun) then we easily end up in recursive situations.
Validating keyword structure inside of IF is valuable. This is now solved so that if the same IF block is recursed to in dryrun mode the second level does not anymore execute the steps in the block.
This approach seams to generate a good result for the dryrun, where all the Robot Framework lines of code that can be touched by a test run will be checked through.

One positive (unexpected to me) improvement is that dryrun will now check keywords executed inside IFs.
Things to do:

[ ] Empty IF, ELSE IF and ELSE blocks should raise parsing error
[ ] Test for variable scope. For variable created inside IF block and used outside.
[ ] User Guide changes

  File "/Users/mkorpela/workspace/robotframework/src/robot/running/steprunner.py", line 98, in run
    condition_matched = self._run_if_branch(body, condition_matched, data, datacondition, first)
  File "/Users/mkorpela/workspace/robotframework/src/robot/running/steprunner.py", line 105, in _run_if_branch
    with StatusReporter(self._context, result, dry_run_lib_kw=not branch_to_execute):
  File "/Users/mkorpela/workspace/robotframework/src/robot/running/statusreporter.py", line 33, in __enter__
    self._context.start_keyword(self._result)
  File "/Users/mkorpela/workspace/robotframework/src/robot/running/context.py", line 176, in start_keyword
    self.output.start_keyword(keyword)
  File "/Users/mkorpela/workspace/robotframework/src/robot/output/output.py", line 63, in start_keyword
    LOGGER.start_keyword(kw)
  File "/Users/mkorpela/workspace/robotframework/src/robot/output/logger.py", line 220, in start_keyword
    logger.start_keyword(keyword)
  File "/Users/mkorpela/workspace/robotframework/src/robot/output/listenermethods.py", line 42, in __call__
    method(args.get_arguments(method.version))
  File "/Users/mkorpela/workspace/robotframework/src/robot/output/listenerarguments.py", line 29, in get_arguments
    self._version2 = self._get_version2_arguments(*self._arguments)
  File "/Users/mkorpela/workspace/robotframework/src/robot/output/listenerarguments.py", line 74, in _get_version2_arguments
    attributes.update(self._get_extra_attributes(item))
  File "/Users/mkorpela/workspace/robotframework/src/robot/output/listenerarguments.py", line 136, in _get_extra_attributes
    return {'args': args, 'type': self._types[kw.type]}

OK
Couldn't use data file '/Users/runner/work/robotframework/robotframework/.coverage': Error binding parameter 0 - probably unsupported type.
Error: Process completed with exit code 1.

As no objections. Merging.


add AffectsOverallServiceLevels field to Scorecard and ScorecardInput

Issues
#71
Changelog
Add AffectsOverallServiceLevels field to Scorecard and ScorecardInput structs

[X] List your changes here
[X] Make a changie entry

Tophatting
task test passes all tests

Gonna merge this and fixup the doc string later


Clean up sensor driver Kconfigs

Eliminate repetitive Kconfig "depends on" in sensor drivers
Remove redundant Kconfig "depends on SENSOR" in sensor drivers

Codecov Report

Merging #9952 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master   #9952   +/-   ##
======================================
  Coverage    52.5%   52.5%
======================================
  Files         213     213
  Lines       26078   26078
  Branches     5624    5624
======================================
  Hits        13691   13691
  Misses      10136   10136
  Partials     2251    2251

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 81b2721...e5c674b. Read the comment docs.


Step 49 of Statistics Calculator doesn't give useful hint if you are missing starting value of reduce

Describe the Issue
The step doesn't give a useful hint if you are missing the initial value of the reduce.
Affected Page
https://www.freecodecamp.org/learn/javascript-algorithms-and-data-structures-v8/learn-advanced-array-methods-by-building-a-statistics-calculator/step-49
Your code
const getVariance = (array) => {
  const mean = getMean(array);
  const differences = array.map(
    el => el - mean
  );
  const squaredDifferences = differences.map(
    el => el ** 2
  );
  const sumSquaredDifferences = squaredDifferences.reduce((acc, el) => acc + el);

}

Expected behavior
I would expect an hint that said that you are missing the starting value of the reduce.
Screenshots

System

Device: [e.g. iPhone 6, Laptop]
OS: [e.g. iOS 14, Windows 10, Ubuntu 20.04]
Browser: [e.g. Chrome, Safari]
Version: [e.g. 22]

Additional context
No response

Hi, I noticed task is currently unassigned, and I'd be interested in taking it on. Could you assign it to me so I can get started?
Thanks!

Hi, @AshishVyas03
Thanks for your interest in contributing.
This issue has not been triaged yet, and a solution has not been agreed upon. Once the issue is open for contribution, you are welcome to create a pull request to reflect the issue consensus. Please also note that we typically do not assign issues. Instead, we accept the first pull request that comprehensively solves the issue.

Does the hint and the test data taken from the related .md file, for example all hint and test data for step 49 is coming from the .md file having title : step 49

After doing my research I found that each challenge with an unique Id and title is present in the meta.json file and all the details and test data about that challenge are present in the Id.md file, where all the hint and code samples also present. Am i going in the right direction ?

Thanks for informing, I am new to open source and I was trying to understand the codebase, here is my break down :
The hint for the reduce callback that you mention in the issue resides in this file right : https://github.com/freeCodeCamp/freeCodeCamp/blob/main/curriculum/challenges/english/15-javascript-algorithms-and-data-structures-22/learn-advanced-array-methods-by-building-a-statistics-calculator/6352fcb156834128001ea945.md
And do you want a hint something like this when right arguments are not passed to the reduce callback,
Your reduce callback should have an initial value in the second argument.
assert.match(getVariance.toString(), /sumSquaredDifferences\s*=\s*squaredDifferences\.reduce\(\s*function\s*\(\s*acc\s*,\s*el\s*\)\s*\{\s*return\s*acc\s*\+\s*el\s*;\s*\}\s*)/);

Note: additional step were added to the project. Currently step 50 is affected by the issue.


Scarce memberships

have a limited number of memberships. Each membership would be an NFT probably. Users could resell their access to the membership on an open market.
Need to do more thinking on what happens if a person doesn't pay their subscription. Does it just burn the token? Does it send it back to the artist?

Did more thinking on this last night when I couldnt sleep. I think we change the whole subscription contract into an ERC-1155 contract. Then the subscription itself can be tokenized and scarce. ERC-1155 is basically a combination of ERC-20 and ERC-721. This means the subscriptions could be a fungible ERC-20 token and still allow the user to mint ERC-721 tokens and distribute them to subscribers. Need to do more digging into making the contract backwards compatible with ERC-721 standard
https://eips.ethereum.org/EIPS/eip-1155


provision: Verify reimaged machine OS

Signed-off-by: Zack Cerza<EMAIL_ADDRESS>

https://pulpito.ceph.com/zack-2023-05-26_19:52:57-smoke-main-distro-default-smithi/

Merge at will; just wanna do it during the week


Refactor/streaming v4

@ironman-machine go

Hello @LaurenSpiegel
Starting end to end procedure using the following payload:
{"REPO_NAME": "S3", "SCALITY_S3_BRANCH": "refactor/streamingV4", "DEFAULT_BRANCH": "master"}
Please follow http://ci.ironmann.io/gh/scality/Integration/8441 for CI status.

end to end passed here: http://ci.ironmann.io/gh/scality/Integration/8443


Global HTTP Batch endpoint is deprecated.

I tried running the wdl-runner example described here: https://github.com/broadinstitute/wdl-runner/tree/master/wdl_runner in GCP cloud shell and got the exception which is included below.
I tried with the existing Dockerfile, as well as, an edited Dockerfile using cromwell-52.jar - both had the same result.
Looks like there is a description of the updates that are needed are described here: https://g.co/cloud/global-batch-deprecation
The error output:
2020/08/06 22:47:58 Listening on [::]:22...
2020-08-06 22:47:58,194 sys_util INFO: CROMWELL->/cromwell/cromwell.jar
2020-08-06 22:47:58,194 sys_util INFO: CROMWELL_CONF->/cromwell/jes_template.conf
2020-08-06 22:47:58,429 cromwell_driver INFO: Started Cromwell
2020-08-06 22:47:58,429 wdl_runner INFO: starting
2020-08-06 22:48:00,107  INFO  - Running with database db.url = jdbc:hsqldb:mem:${slick.uniqueSchema};shutdown=false;hsqldb.tx=mvcc
2020-08-06 22:48:03,442 cromwell_driver INFO: Failed to connect to Cromwell (attempt 1): HTTPConnectionPool(host='localhost', port=8000): Max retries exceeded with url: /api/workflows/v1 (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f09f9035150>: Failed to establish a new connection: [Errno 111] Connection refused',))
2020-08-06 22:48:08,451 cromwell_driver INFO: Failed to connect to Cromwell (attempt 2): HTTPConnectionPool(host='localhost', port=8000): Max retries exceeded with url: /api/workflows/v1 (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f09f8fed990>: Failed to establish a new connection: [Errno 111] Connection refused',))
2020-08-06 22:48:11,067  INFO  - Running migration RenameWorkflowOptionsInMetadata with a read batch size of 100000 and a write batch size of 100000
2020-08-06 22:48:11,088  INFO  - [RenameWorkflowOptionsInMetadata] 100%
2020-08-06 22:48:11,300  INFO  - Running with database db.url = jdbc:hsqldb:mem:${slick.uniqueSchema};shutdown=false;hsqldb.tx=mvcc
2020-08-06 22:48:12,491  INFO  - Slf4jLogger started
2020-08-06 22:48:12,812 cromwell-system-akka.dispatchers.engine-dispatcher-9 INFO  - Workflow heartbeat configuration:
{
"cromwellId" : "cromid-53d5d95",
"heartbeatInterval" : "2 minutes",
"ttl" : "10 minutes",
"failureShutdownDuration" : "5 minutes",
"writeBatchSize" : 10000,
"writeThreshold" : 10000
}
2020-08-06 22:48:13,007 cromwell-system-akka.dispatchers.service-dispatcher-16 INFO  - Metadata summary refreshing every 1 second.
2020-08-06 22:48:13,045 cromwell-system-akka.actor.default-dispatcher-8 INFO  - KvWriteActor configured to flush with batch size 200 and process rate 5 seconds.
2020-08-06 22:48:13,047 cromwell-system-akka.dispatchers.service-dispatcher-13 INFO  - WriteMetadataActor configured to flush with batch size 200 and process rate 5 seconds.
2020-08-06 22:48:13,058 cromwell-system-akka.dispatchers.engine-dispatcher-27 INFO  - JobStoreWriterActor configured to flush with batch size 1000 and process rate 1 second.
2020-08-06 22:48:13,083 cromwell-system-akka.dispatchers.engine-dispatcher-12 INFO  - CallCacheWriteActor configured to flush with batch size 100 and process rate 3 seconds.
2020-08-06 22:48:13,096  WARN  - 'docker.hash-lookup.gcr-api-queries-per-100-seconds' is being deprecated, use 'docker.hash-lookup.gcr.throttle' instead (see reference.conf)
2020-08-06 22:48:13,458 cromwell_driver INFO: Failed to connect to Cromwell (attempt 3): HTTPConnectionPool(host='localhost', port=8000): Max retries exceeded with url: /api/workflows/v1 (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f09f8fed890>: Failed to establish a new connection: [Errno 111] Connection refused',))
2020-08-06 22:48:13,601 cromwell-system-akka.dispatchers.engine-dispatcher-29 INFO  - JobExecutionTokenDispenser - Distribution rate: 50 per 1 seconds.
2020-08-06 22:48:13,656 cromwell-system-akka.dispatchers.backend-dispatcher-33 INFO  - Running with 3 PAPI request workers
2020-08-06 22:48:13,656 cromwell-system-akka.dispatchers.backend-dispatcher-33 INFO  - 'resetAllWorkers()' called to fill vector with 3 new workers
2020-08-06 22:48:14,172 cromwell-system-akka.dispatchers.backend-dispatcher-33 INFO  - Request manager PAPIQueryManager created new PAPI request worker PAPIQueryWorker-27977f59-f7e1-4f0b-a896-8863755ef83b with batch interval of 33333 milliseconds
2020-08-06 22:48:14,189 cromwell-system-akka.dispatchers.backend-dispatcher-33 INFO  - Request manager PAPIQueryManager created new PAPI request worker PAPIQueryWorker-a5bc6f16-fa17-455e-8c67-8683b3eaa846 with batch interval of 33333 milliseconds
2020-08-06 22:48:14,190 cromwell-system-akka.dispatchers.backend-dispatcher-33 INFO  - Request manager PAPIQueryManager created new PAPI request worker PAPIQueryWorker-0a1e6731-f4fa-4184-9b0f-edcea21c49d7 with batch interval of 33333 milliseconds
2020-08-06 22:48:15,936 cromwell-system-akka.dispatchers.engine-dispatcher-9 INFO  - Cromwell 49 service started on <IP_ADDRESS>:8000...
2020-08-06 22:48:18,601 cromwell-system-akka.dispatchers.engine-dispatcher-9 INFO  - Not triggering log of token queue status. Effective log interval = None
2020-08-06 22:48:18,992 cromwell-system-akka.dispatchers.api-dispatcher-37 INFO  - Unspecified type (Unspecified version) workflow 182bfb5c-04c0-47e6-a7ce-8b6f3b00a26e submitted
2020-08-06 22:48:19,185 cromwell_driver INFO: Job submitted to Cromwell. job id: 182bfb5c-04c0-47e6-a7ce-8b6f3b00a26e
2020-08-06 22:48:34,802 cromwell-system-akka.dispatchers.engine-dispatcher-12 INFO  - 1 new workflows fetched by cromid-53d5d95: 182bfb5c-04c0-47e6-a7ce-8b6f3b00a26e
2020-08-06 22:48:34,807 cromwell-system-akka.dispatchers.engine-dispatcher-29 INFO  - WorkflowManagerActor Starting workflow UUID(182bfb5c-04c0-47e6-a7ce-8b6f3b00a26e)
2020-08-06 22:48:34,843 cromwell-system-akka.dispatchers.engine-dispatcher-29 INFO  - WorkflowManagerActor Successfully started WorkflowActor-182bfb5c-04c0-47e6-a7ce-8b6f3b00a26e
2020-08-06 22:48:34,844 cromwell-system-akka.dispatchers.engine-dispatcher-29 INFO  - Retrieved 1 workflows from the WorkflowStoreActor
2020-08-06 22:48:34,877 cromwell-system-akka.dispatchers.engine-dispatcher-31 INFO  - WorkflowStoreHeartbeatWriteActor configured to flush with batch size 10000 and process rate 2 minutes.
2020-08-06 22:48:35,157 cromwell-system-akka.dispatchers.engine-dispatcher-12 INFO  - MaterializeWorkflowDescriptorActor [UUID(182bfb5c)]: Parsing workflow as WDL draft-2
2020-08-06 22:48:35,967 cromwell-system-akka.dispatchers.engine-dispatcher-12 INFO  - MaterializeWorkflowDescriptorActor [UUID(182bfb5c)]: Call-to-Backend assignments: ga4ghMd5.md5 -> JES
2020-08-06 22:48:38,459 cromwell-system-akka.dispatchers.engine-dispatcher-28 INFO  - WorkflowExecutionActor-182bfb5c-04c0-47e6-a7ce-8b6f3b00a26e [UUID(182bfb5c)]: Starting ga4ghMd5.md5
2020-08-06 22:48:38,624 cromwell-system-akka.dispatchers.engine-dispatcher-27 INFO  - Assigned new job execution tokens to the following groups: 182bfb5c: 1
2020-08-06 22:48:39,729 cromwell-system-akka.dispatchers.backend-dispatcher-33 INFO  - PipelinesApiAsyncBackendJobExecutionActor [UUID(182bfb5c)ga4ghMd5.md5:NA:1]: /bin/my_md5sum /cromwell_root/ga4gh-tool-execution-challenge/phase1/md5sum.input
2020-08-06 22:48:40,569 cromwell-system-akka.dispatchers.backend-dispatcher-33 INFO  - PipelinesApiAsyncBackendJobExecutionActor [UUID(182bfb5c)ga4ghMd5.md5:NA:1]: To comply with GCE custom machine requirements, memory was adjusted from 512 MB to 1024 MB
2020-08-06 22:48:48,067 cromwell-system-akka.dispatchers.backend-dispatcher-47 INFO  - PipelinesApiAsyncBackendJobExecutionActor [UUID(182bfb5c)ga4ghMd5.md5:NA:1]: job id: projects/572979331914/locations/us-central1/operations/5470557859033439857
2020-08-06 22:49:20,997 cromwell-system-akka.dispatchers.backend-dispatcher-47 INFO  - PipelinesApiAsyncBackendJobExecutionActor [UUID(182bfb5c)ga4ghMd5.md5:NA:1]: Status change from - to Running
2020-08-06 22:52:41,294 cromwell-system-akka.dispatchers.backend-dispatcher-46 INFO  - PipelinesApiAsyncBackendJobExecutionActor [UUID(182bfb5c)ga4ghMd5.md5:NA:1]: Status change from Running to Success
2020-08-06 22:53:50,588 cromwell-system-akka.dispatchers.engine-dispatcher-9 INFO  - WorkflowManagerActor Workflow 182bfb5c-04c0-47e6-a7ce-8b6f3b00a26e failed (during ExecutingWorkflowState): cromwell.engine.io.IoAttempts$EnhancedCromwellIoException: [Attempted 5 time(s)] - GcsBatchFlow.BatchFailedException: com.google.api.client.http.HttpResponseException: 404 Not Found
Global HTTP Batch endpoint is deprecated. See https://g.co/cloud/global-batch-deprecation for info and migration steps.
Caused by: cromwell.engine.io.gcs.GcsBatchFlow$BatchFailedException: com.google.api.client.http.HttpResponseException: 404 Not Found
Global HTTP Batch endpoint is deprecated. See https://g.co/cloud/global-batch-deprecation for info and migration steps.
at cromwell.engine.io.gcs.GcsBatchFlow.executeBatch(GcsBatchFlow.scala:123)
at cromwell.engine.io.gcs.GcsBatchFlow.$anonfun$flow$2(GcsBatchFlow.scala:68)
at akka.stream.impl.fusing.StatefulMapConcat$$anon$47.onPush(Ops.scala:2035)
at akka.stream.impl.fusing.GraphInterpreter.processPush(GraphInterpreter.scala:523)
at akka.stream.impl.fusing.GraphInterpreter.processEvent(GraphInterpreter.scala:480)
at akka.stream.impl.fusing.GraphInterpreter.execute(GraphInterpreter.scala:376)
at akka.stream.impl.fusing.GraphInterpreterShell.runBatch(ActorGraphInterpreter.scala:606)
at akka.stream.impl.fusing.GraphInterpreterShell$AsyncInput.execute(ActorGraphInterpreter.scala:485)
at akka.stream.impl.fusing.GraphInterpreterShell.processEvent(ActorGraphInterpreter.scala:581)
at akka.stream.impl.fusing.ActorGraphInterpreter.akka$stream$impl$fusing$ActorGraphInterpreter$$processEvent(ActorGraphInterpreter.scala:749)
at akka.stream.impl.fusing.ActorGraphInterpreter$$anonfun$receive$1.applyOrElse(ActorGraphInterpreter.scala:764)
at akka.actor.Actor.aroundReceive(Actor.scala:539)
at akka.actor.Actor.aroundReceive$(Actor.scala:537)
at akka.stream.impl.fusing.ActorGraphInterpreter.aroundReceive(ActorGraphInterpreter.scala:671)
at akka.actor.ActorCell.receiveMessage(ActorCell.scala:612)
at akka.actor.ActorCell.invoke(ActorCell.scala:581)
at akka.dispatch.Mailbox.processMailbox(Mailbox.scala:268)
at akka.dispatch.Mailbox.run(Mailbox.scala:229)
at akka.dispatch.Mailbox.exec(Mailbox.scala:241)
at akka.dispatch.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260)
at akka.dispatch.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339)
at akka.dispatch.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979)
at akka.dispatch.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)
Caused by: com.google.api.client.http.HttpResponseException: 404 Not Found
Global HTTP Batch endpoint is deprecated. See https://g.co/cloud/global-batch-deprecation for info and migration steps.
at com.google.api.client.http.HttpRequest.execute(HttpRequest.java:1094)
at com.google.api.client.googleapis.batch.BatchRequest.execute(BatchRequest.java:233)
at cromwell.engine.io.gcs.GcsBatchFlow.$anonfun$executeBatch$3(GcsBatchFlow.scala:122)
at scala.runtime.java8.JFunction0$mcV$sp.apply(JFunction0$mcV$sp.java:23)
at scala.util.Try$.apply(Try.scala:213)
at cromwell.engine.io.gcs.GcsBatchFlow.executeBatch(GcsBatchFlow.scala:122)
... 22 more
2020-08-06 22:53:50,589 cromwell-system-akka.dispatchers.engine-dispatcher-27 INFO  - WorkflowManagerActor WorkflowActor-182bfb5c-04c0-47e6-a7ce-8b6f3b00a26e is in a terminal state: WorkflowFailedState
ERROR: Status of job is not Submitted, Running, or Succeeded: Failed

2020-08-06 22:48:15,936 cromwell-system-akka.dispatchers.engine-dispatcher-9 INFO - Cromwell 49 service started on <IP_ADDRESS>:8000...
From the logs....you still seem to be using older version of Cromwell. Make sure to upgrade to 52 version.
PS: I am not from cromwell team

Hi Tom,
Yes versions of Cromwell prior to 52 will have that error with the Google Global HTTP Batch endpoint, and as pointed out above it looks like you're using version 49.

Looks like I didn't update wdl_pipeline.yaml to point to my freshly built docker.
I tried again and it does work with 52.
I'll close this.

This actually should be still an open issue because updates need to be added to support version 52.

Repo has been updated with 53 now if you want to give it a try again.


Doc on using regions.

also addresses #492

Coverage remained the same at 75.489% when pulling 29c9f613724fa5dd37a117311c83674aba3b3cdd on sushobhana:regiondocs into bf6673933bb6bd01e6bef55f083b7c364dbf289c on radio-astro-tools:master.


Changed force_text() to force_str()

force_text() will be removed in Django 4.0 and is deprecated in favor of force_str()

@JayantGoel001 thank you for your 2cts, I feel like @claudep comments are legit, @smithdc1 would you be willing to update your PR or shall we do it?

Sorry I've not had time this week to come back to this.
Just removing the code works, but I've not yet had chance to understand it in more detail. If you are more comfortable with the change and have time then please do carry on.


updating the schema version for the ui_element entity and refactoring…

… tests to be descriptive

looks awesome. Can we also export the models in the index? I was going to look into doing this but maybe this review can have that? cody-music exports the models and apis in the index.ts like this...
export * from "./lib/apis";
export {
Album,
Artist,
CodyResponse,
CodyResponseType,
PlayerName,
Track,
TrackStatus,
PaginationItem,
PlayerDevice,
PlayerContext,
PlaylistItem,
SpotifyAudioFeature,
PlayerType,
PlaylistTrackInfo,
CodyConfig,
SpotifyAuthState
} from "./lib/models";
Then the implementing client can then import them...
import {
PlaylistItem,
PlayerName,
PlayerDevice,
playSpotifyDevice,
} from "cody-music";

That makes sense.   I was looking at the vscode implementation and noticing some intermediate objects that were created to organize the data, but were very duplicative of these models.
Can do


nixos/tests: Use a patched QEMU for testing

Our NixOS test runner is using virtio to make the store available to the VMs within the test. Since NixOS/nix@5e51ffb1c265e16486fcdd888ce4a04db9e5552b we now build with user namespaces and we have a mapping from the uid/gid of the current build user to a uid/gid within the newly created user namespace. In NixOS/nix#1131 this is going to be 0/0 again but even using 1000/100 before (in NixOS/nix@ff0c0b645cc1448959126185bb2fafe41cf0bddf) doesn't avoid the following problem.
So the problem here is that the bind-mounted file systems within the build process will have a different uid/gid mapping and this in turn leads to test failures like these:

https://headcounter.org/hydra/build/1436479/nixlog/3/raw
https://headcounter.org/hydra/build/1454600/nixlog/1/raw

What happens here is that the programs tested here (sudo and cups) are doing strict permission checks and bail out because the paths that are mounted within the builder sandbox now have uid/gid 65534 and thus don't match with the user that the process is running (uid/gid 0) as.
From the perspective of namespacing this makes sense, because the uid 0 within the user namespace isn't the same as uid 0 from the upper namespace.
Right now it seems that the official Hydra doesn't yet run with a recent enough Nix version to be hitting this problem, but it will eventually get there as well.
So the following options come in mind to address this:

Patch programs like sudo and cups to not do restrictive checks on paths within the Nix store.
Use something like bindfs to override the uid/gid (very slow, because it's implemented as FUSE).
Prevent the Nix builder from creating user namespaces on a selective basis (this however also prevents relocated stores).
Patch qemu to always report uid 0 and gid 0 to the VM on stat().

With this PR I've chosen the latter, because it's the most generic and least invasive approach. However we still need to fix build failures of some programs (for example go's tests fail because of this https://headcounter.org/hydra/build/1455527/nixlog/1/raw, but I haven't looked into it in detail yet).
Cc: @edolstra

Cc: @domenkozar because this should surface on Hydra deployments in the wild with #19396.

Also I'm open for ideas to solve this in a better way.

Well, the easy solution is not to use user namespaces. I'd prefer not to have to patch qemu (and who knows how many other packages) to work around bugs caused by user namespaces.

@edolstra: These problems are not only surfacing with user namespaces but also on non-NixOS without user namespaces. I guess the reason we didn't get bug reports yet is that the amount of people running NixOS tests on non-NixOS systems is close to zero. For the issue related to go, I expect it to surface in a few days or weeks.

@edolstra: Also, there is another option to fix this in a generic way, which I forgot above: Use seccomp to force st_uid/st_gid to be 0 on *stat() in NixOS/nix#1131.

Why does it have to be 0 only for store paths? Can't we force everything to be 0?

@edolstra: Hm, good point... going to implement it.

@edolstra: Okay, this is very tricky to implement, because if we want to emulate the stat syscall, we need to use either SIGSYS or ptrace to intercept the call from seccomp. Unfortunately using SIGSYS we can't really do this properly, because we need to call the real stat syscall from within the signal handler which in turn is limited by seccomp.
This would lead to an infinite recursion, but usually the way to properly implement this with seccomp is to match only on specific arguments of stat, but we do have two pointers here which we can't dereference via the seccomp BPF program, so there is no way to avoid this recursion.
If we go for the second implementation, we could use a tracer to pause and re-inject the emulated syscall from outside the sandbox. But having a tracer attached to each process not only has an impact on performance but also can cause side-effects in terms of ptrace.
Both methods however have another big drawback: We'd lose cross-platform compatibility of libseccomp, because we need to alter the syscalls registers ourselves so it gets even more complicated: For example on x86_64we need to call stat based on the values ofRDI, RSI, de-reference RSI, write the altered struct statinto it, write the new return code toRAXand also take care oferrno(as in restoring it to the value just afterstat`).
On 32bit x86 we can just swap R* with E*, but on other platforms this is much more complicated (for example MIPS has indirect syscalls).
And on top of all that, we still have a build environment that's different than we have in older Nix, so we will see builds failing on newer Nix where they have succeeded in older Nix versions.
So all in all, I think this is not worth it, so it might be a good idea to either remove user namespaces altogether or make it the new standard for Nix builders (which also means, that we need to do patches like this very PR).
Speaking of builders, using user namespaces indeed has one particular advantage: We could implement a real nix-shell --pure which ends up in a real builder environment.


[no-release-notes] fix memo gen

Running go generate ./... on this branch creates 3 changed files. I think those should be included in this PR.

i see one import format change in sql/analyzer/memo.og.go. what do you see?

note the generator is poorly isolated from the source files. i have been slowly fixing these, but currently you have to install to regen.

I'm seeing these changes:


Proposal: Add color to output

I got forwarded here from Microsoft/TypeScript#6363:

It's currenty hard to read TypeScript errors in VS Code:

There is a --pretty option for TypeScript, but AFAIK it can't be used when using gulp-typescript.
So I'd like to suggest to add color to the output of gulp-typescript.

I'd like to suggest to give colors so the message and code positions can easily be read, too (not just the - rather uninformative - constant word "error", like it is output by tsc when applying the --pretty compiler option):

(Suggested colors are: green for code position, red for error keyword/code and dark yellow for the error message.)

Errors are already colored in gulp-typescript, though it seems VSCode ignores these. I'm not sure why, but you can try to add the --color flag (like gulp --color tscProject).
For a better integration between gulp and VSCode, you could also use a problem matcher, see Using VSCode with gulp-typescript.

You are absolutely right. After giving it another thought today I realized that coloring the errors in the Output panel is a sole task of VS Code's Problem Matcher functionality.
So I amended my corresponding suggestion at Microsoft/vscode#1801 a few minutes ago.


Functionality

Hey I ran in to your app and it seems to look beautiful and I finally I'll be able to replace my stock moto compass app.I hope you could add a few functionality in your free time. I'll attach two screenshots of how the moto compass app looks for your reference.

I'm gonna download the moto compass to take a look at it and see what I should add.
I want to add these as I presume they're lat/lon but I'm not entirely sure what they are.

If there's anything else specific you'd like to see added can you list them here? I'd appreciate that.

The bubble level options in the  moto compass app is handy feature that could be implemented. But it's up to you guys to decide it. I'm happy that you guys have made something beautiful that is open source that could replace my stock app.. so take your time in implementing anything that you guys like.

Just a quick update here, I've spent the past few months trying to get my hands on an APK to deobfuscate and/or install to take a closer look. That, or a moto phone. But, as it stands that probably won't happen for some time. Absolutely going to add the Lat/Lon and a few basic options but aside from that there isn't a whole lot more I can do right now. My schedule's tight so I'm trying to fit what I can in.
I really appreciate the patience <3


Fixed build of hiptail example

I assume the API changed at some point, and this wasn't caught.

ty


use terraform override.tf to ensure that master IPs and ELB tf output…

… stays the same even if that got changed upstream

no breaking changes

no, sorry left it after testing, fixed in it new commit, thanks for spotting it


Fix dependencies

Some dependencies are not fixed and they should to avoid an update breaks the package. We have CI now in place to update them automatically if the package still works.

Should the linter enforce pinned versions?

Does update_dependencies from the Python script already update all choco dependency updates, e.g. after changes from #136?


[Improvement] support build thirdparty and BE using clang

Support build thirdparty and BE using clang
User could export CC and CXX env  to switch the compiler from clang to gcc
If user not set CC and CXX env, then it will use gcc from DORIS_GCC_HOME or the system's default gcc.

In the future, I think we should only support Clang.

#7590

I think we need to document to explain when and how to use clang or gcc.


What about Azure Resource Mover?

Wouldn't it be a good idea to mention the new Resource mover hub and features to move resources? Its in preview but should be mentioned in a couple of places to make the move easier and help to choose the right move tool.
https://docs.microsoft.com/en-us/azure/resource-mover/select-move-tool

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

ID: 06391912-66bd-8905-d50e-8b06307fd2e9
Version Independent ID: e807a790-2b7a-faac-eba4-692a8936fdc7
Content: Transitioning existing Azure environments to enterprise-scale - Cloud Adoption Framework
Content Source: docs/ready/enterprise-scale/transition.md
Service: cloud-adoption-framework
Sub-service: ready
GitHub Login: @BrianBlanchard
Microsoft Alias: brblanch

Thanks for reporting - this issue is under review.  This is a Microsoft Internal DevOps Bug ID AB#325507

The context we are speaking to in the transition article is transition of resources in subscriptions to other subscriptions (not regions) and subscription moves to a new AD Tenant for transferring billing ownership. Our context is mostly on alignment with organizing subscriptions into management groups. It seems to me the Azure Resource Mover tools focus on moving resources across regions. I don’t think this is prescriptive to a specific scenario we observe in enterprise scale landing zone.
Thank you for your feedback.


home-page changes

George is this merge the same as the one up and running at geochoros domain url???
The commit + merge seems fine to me and the code includes all latest changes but I think there is something missing from the production.

It should be. Maybe something is cached from the previous version? What's missing?

Start form here --> http://geochoros.survey.ntua.gr/walkandthecitycenter/home
If pressing map link you are redirected to the map component.
The page looks fine. However there is a small gap on the right hand side.-->

This was supposed to be solved by adding this line of code this_.map.updateSize(); line 103 at map.compononet.ts

@gpanag  I have updated production with your latest merge and seems to work as expected. Your probably updated production before merging.

Awesome!


Claiming failed with error : Claim init failed (MEGH-4373)

Answers checklist.

[X] I have read the Rainmaker documentation and the issue is not addressed there.
[X] I have updated my IDF branch (release/vX.Y) to the latest version and checked that the issue is present there. This is not applicable if you are using Rainmaker with Arduino.
[X] I have searched the Rainmaker forum and issue tracker for a similar issue and not found a similar issue.

IDF / ESP32-Arduino version.
Arduino Ide 2.0.3
Operating System used.
Windows
How did you build your project?
Arduino IDE
Development Kit.
Esp32 DevKit V1
What is the expected behavior?
i want to connect my esp to the rainmaker app. in my new esp32.,
What is the actual behavior?
I'm getting
Claiming failed with error : Claim init failed
error in the app, after scanning the qr code. it never happened before.
Someone please help me.

Steps to reproduce.

Step
Step
Step
...

Build Logs.
Reset Button Pressed!
ets Jul 29 2019 12:21:46

rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:1
load:0x3fff0030,len:1344
load:0x40078000,len:13864
load:0x40080400,len:3608
entry 0x400805f0

Starting ESP-RainMaker

Provisioning Started with name "PROV_TechStudyCeooalll" and PoP "TSC123RFV332" on BLE
Scan this QR code from the ESP RainMaker phone app.

  █▀▀▀▀▀���   █ ▄▄█▀▀▀▄▀  █▀▄▀▄█▀ █▀���▀▀▀█
  █ ███ █ █▀█▄▄▄█▀���  ▀▄██  ▄█▄  █ ███ █
  █ ▀▀��� █ █▄██▀▀▀▄▄██▀▀▀▀ ▄▄▄���█ █ ▀▀▀ █
  ▀▀▀▀▀▀▀ █▄█▄��� ▀▄█ █ █▄▀▄▀ ▀▄▀ ▀▀▀▀▀▀��
  █ ▀█▀█▀▄ ▄▀█▀▄▀▄▄▀█▄ ▄▀▄  ███▄██▀█▀▄
   ▀▀  ▄��██▄▀▀    ▄▀▀ ▄█▀▄█ █▀▀▀▀ ��▀▀▀▀
  █▀██▄ ▀█▄▀ ▀███ ��▀▄▄▄▄▀  ▀ ▀▄▄▀█▀ ▀ ▀
  █▄ █ ▀▀▄▄▄▄█▀█▀█▄▀█ ██▄▄ ▀���▀▄▀█ ▀▀▀ █
  █ ▄▀██▀▀ █��▀ ▀ ▄ ▀▄▄█▄▀██▀▄ ▀██ ▀█▀���
  █▄▄█ ▄▀█▀▄▄▄ █▀██  ▄ ���█ ▀▀ ▀ ▄█ █▀ ▄▀
  ▀ ▄ █▀▀ �� ▀▀  █ ▄▀▄▄█ ▀▀▀▀▄▀▄ ▀ ▀▀��
  █▀█ █ ▀ █  ▀▀███▄▀█ ▄▄���▄█▀▄▀ ▄▀ █   ▀
  ▄▄▄█▀ ▀▄���▀█▀▀▄▀ ██▄▄█▄█▄██▄▀▀▀���▀▀ █▄▀
  █ █▀█ ▀▀ ▄  █▄█▀ ▀ ▄█▄▄▄█▀ █▀ ▀ ▀ ▀█▀
  ▀ ��  ▀▀ █▄▄ ▀▀ ▀▄█▄██▄▀  ▀ ██���▀▀█▄▀ ▀
  █▀▀▀▀▀█ ▄▄█    ���▀ ▄▄▀▄▄ █▀▄▄█ ▀ ██▀ █
  �� ███ █ █▄▄    ▀ █▄▄▄ █▄█▀▄█���▀████▀█▄
  █ ▀▀▀ █ ▀█  ▀ ���██▀   █ ▄█▀  █ ▄ ▄█ ▀█
  ▀▀���▀▀▀▀ ▀ ▀ ▀▀ ▀ ▀  ▀▀▀   ▀▀ ▀   ▀▀▀▀

If QR code is not visible, copy paste the below URL in a browser.
https://rainmaker.espressif.com/qrcode.html?data={"ver":"v1","name":"PROV_TechStudyCeooalll","pop":"TSC123RFV332","transport":"ble"}

More Information.
No response

same here.

Hi @shahpiyushv !
I have this version of APP installed and there's no way to configure my ESP32-Wrover IE with basic example.
I tried on tablet and smartphone.
When I managed to connect to board it says no network found, placing the SSID and password manually doesn't solve.
Almost all time the APP freezes in QR code scan.
Best regards.

@FernandoGarcia since this sounds like a different issue, can you file it separately? The default issue form will also help us get more information about it. Please also mention what phone OS you are using while filing the new issue.

Done.

I found an error from my side while placing SSID and password manually.
I had  an extra space at the end of SSID added by auto complete from keyboard.
I have reported it here.


fix: publish workflow

#5  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @lewxdev and the rest of your teammates on  Graphite


Fix Build Errors From Clean Build

Please make sure to run build.py -clean as a sanity check before commits.

Looks like I had changes that weren't properly staged when build.py -clean was ran, this has been fixed through 8614c51 since there are already changes ready to be pushed.


Ensure that N2J_NetworkInfo uses Make function with Channel and PAN ID

Currently this JNI conversion is using the NetworkInfo.Make() overload which does not take in a channel and PAN ID. Unfortunately, JNI doesn't complain if you pass too many arguments with the invocation, so the channel and PAN ID were being ignored. Additionally, although the ThreadChannel is only a uint_8, the method is declared in Java as an integer, so changed the cast to a jint instead.

Codecov Report

Merging #285 into master will increase coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #285      +/-   ##
==========================================
+ Coverage   54.29%   54.29%   +<.01%
==========================================
  Files         289      289
  Lines       56108    56108
==========================================
+ Hits        30462    30463       +1
+ Misses      25646    25645       -1

Impacted Files
Coverage Δ

src/lib/profiles/security/WeaveCert.cpp
84.09% <0%> (+0.32%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 1eea311...6c6aea3. Read the comment docs.


Port to C++: Masking

Is your feature request related to a problem? Please describe.
Current contents and implementation of masking is in Python. As discussed in the thread, it is needs to port to C++.
Describe the solution you'd like

Implement the masking operations using necessary OpenCV C++ API methods.
Create Makefile to compile and build the executables.
Add a .md file explaining the concepts and instructions for running the executables.

I would like to work on this issue.

I would like to port this


Last changed after restart ?

After I restart HA, the door sensors shows the restart time. How can I resolve this ? I searched alot on google but i dont understand how can I do that.

This is a current limitation of Home Assistant. The last_changed gets updated when there is a restart.
There is a feature request to change this behavior you can track if you'd like to follow its progress: https://community.home-assistant.io/t/retain-last-state-change-data-of-a-sensor-after-reboot/125148


fabric8:debug - Enable JAVA_DEBUG_ENABLED on all containers of a pod (since the application needs to be the first one)

[merge]


chore(release): v1.1.0 🎉

:robot: I have created a release beep boop
1.1.0 (2023-07-16)
Features

init: initialize based on simple-localstorage-cache (dd78966)

Bug Fixes

deploy: bump to overcome ghost npm version (db154a7)
deploy: bump to overcome ghost release version (83293d6)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/ehmpathy/simple-async-tasks/releases/tag/v1.1.0 :sunflower:


UI fix of NavItem highlighting

in ACM 2.5+, when opening the "clusters" menu tab (sub-item of Infrastructure), the opened URL does not end with /clusters, therefore the isActive member of NavItem would always return false.  In ACM 2.5 line 338's isActive check was the same as in 335 and 344, which was fixed in ACM 2.6+. The bug persists for NavItem's that are either a group or not children of a group. The suggested PR is a fix for the above.
steps to reproduce the bug:

Expand Infrastructure NavItem
Open clusters sub-NavItem
Close Infrastructure NavItem

Bugged behavior:
Infrastructure NavItem is not highlighted
Wanted behavior:
Infrastructure NavItem is highlighted (same as all other cases, e.g., Welcome).
This bug exists also in upstream.

https://user-images.githubusercontent.com/19717747/221602432-c02e83c1-7d1e-4666-806b-d4ee5c4ec86b.mov

@nirrozenbaum Thanks for the fix. For 2.7+, this code is only used for development. Do you feel its important to fix in 2.5 and 2.6?

@KevinFCormier personally I would fix it for consistent UI behavior.
if the underneath code is extremely good but users see UI bugs, they might get the wrong impression that code is buggy.
the fix is also very simple and straight forward.
up to you of course :)

/test unit-tests-sonarcloud

/test unit-tests-sonarcloud

/lgtm


chore(master): release 2.0.0

:robot: I have created a release beep boop
2.0.0 (2024-11-07)
⚠ BREAKING CHANGES

Refactored topic structure for more granular flow and access (#26)

Features

Refactored topic structure for more granular flow and access (#26) (6f2a5ed)

Bug Fixes

make release please trigger other workflows (using a PAT) (c27263c)
mqtt: require userClient in topic for all scene messages (#32) (4f93e84)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/arenaxr/arena-persist/releases/tag/v2.0.0 :sunflower:


Add removeGlobalScope() option to HasGlobalScopes trait

This PR adds removeGlobalScope() and removeGlobalScopes() to the HasGlobalScopes trait. It allows to remove global scopes from a model until it is turned back on.
I have a situation where I need to remove a global scope for multiple queries. This new function allows me to remove a scope until I turn it back on.
In my situation I need to remove a global scope (e.g. softdelete) when executing multiple queries from an external package (Model::fixTree() from NestedSet in my case). In this case I could use:
Content::removeGlobalScope('active_scope');
Content::fixTree();
Content::addGlobalScope('active_scope', function ($query) {
    $query->where('active', 1);
});

First time PR so I'm not sure if everything is correct.

Suggestion to improve this a little bit: Maybe this could be implemented like the withoutSyncing method for Laravel Scout.
https://laravel.com/docs/8.x/scout#pausing-indexing


Feat: add theme switching to storybook

Add theme switching using the same themes used in https://style.monday.com/?path=/story/welcome--page
closes #50
dark theme

black theme

hacker theme

light theme

changes made as requested


Google Oauth Keys should not be visible in settings.py

No longer visible. Changed keys, see discord for them.

No longer visible. Changed keys, see discord for them.


Can you make excluded folders less noticeable

At the moment they are highlighted in such a way as if they are main focus:

Maybe better to gray them out or something.

Please update the plugin and tell me if this is what you implied

I updated to version 0.3.3 But don't see any difference. Excluded directories still have highlighted background.

Ah i understand, but this has nothing to do with the plugin, instead you have to go to Settings > Appearance and behavior > File Colors. There you will see that excluded files have that tinted yellow color, and you can edit or remove it if you need to.
--
Elior
On Apr 9, 2017, 19:46 +0300, WiseBird<EMAIL_ADDRESS>wrote:

I updated to version 0.3.3 But don't see any difference. Excluded directories still have highlighted background.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub (https://github.com/mallowigi/material-theme-jetbrains/issues/8#issuecomment-292797279), or mute the thread (https://github.com/notifications/unsubscribe-auth/AEyIzK74Gl_PPcWuDVYInO-_JBuBdBPdks5ruQtngaJpZM4M0qhz).

Big thanks! Sorry for bothering you.


COVID-19 WEBSITE with HTML,CSS AND JAVASCRIPT

I am a GSSOC'21 Participant. I would like to add  COVID-19 WEBSITE on your project Page. This website aware us like what are the symptoms of Corona ..... How to fight with Corona......
@ridsuteri @991rajat @harshgupta20 PLEASE have a look on this issue..
PLEASE ASSIGN ME THIS ISSUE.....

sounds great @Mrinal81 ! go ahead with it :)

@ridsuteri kindly have a look on PR #1254

I made a PR OF Restaurant website...kindly have a look on it..

@Mrinal81 done :)

@ridsuteri @991rajat @harshgupta20 ...... Please have a look on PR #1300 ...........
Please add Level Tag as well as GSSOC'21 Tag if everything is ok..........


OIDC self signed certificate

I'm having this issue with self signed certificates for my oidc, I tried to put the CA on every known location on alpine but it keep ignore it. I started debugging the code until i found out that certifi package using its own custom CA file, my work around for that is adding this to docker-compose.yml:
volumes:
      - "/etc/pki/ca-trust/source/anchors/cacert.pem:/usr/lib/python3.8/site-packages/certifi/cacert.pem"

Is there any, more legitimate, way to use self signed certificates rather than changing the cacert in python site-package, and anyway, i think we should at least mention that in the wiki so more people can easily overcome this problem.

As I remember I faced this issue during some tests in the past. Unless I manually edit the authlib code, I have to use a trusted certificate for OpenID server.

I am using the environment variable AUTHLIB_INSECURE_TRANSPORT set to true in order to instruct the authlib NOT to check the OIDC provider certificate

Hello,
I am using something slightly different. Some packages will populate or override their SSL trust store from specific ENV variables.
As such variables like REQUESTS_CA_BUNDLE or CURL_CA_BUNDLE may allow to pass a specific CA bundle without altering the code.
So trusting the cert on the host machine - so that the ca-certificates.crt bundle file contains the self-signed CA - and then adding the following into the docker-compose file may help:
volumes:
  - /etc/ssl/certs/ca-certificates.crt:/etc/tls/cacert.crt
environment:
  - REQUESTS_CA_BUNDLE=/etc/tls/cacert.crt

Otherwise I also believe that some part of authlib functions can handle parameters passed down to the request function, but I could not find any clear documentation and it would require some code changes I guess.

I tried every mentioned solution to this, but unfortunately without luck.
Is there any other way to achieve this or maybe a hint someone can give me?
I mounted a cacert.pem to /usr/lib/python3.8/site-packages/certifi/ with our own CA, but i still see the error.
Even when I set AUTHLIB_INSECURE_TRANSPORT it doesn't work, but maybe because I run this in a container and the variable is not in the legal_envvars?
Thanks!

Hello,
Not really sorry... Have you tried mine and then try to curl from the container to see if the env-var is at least taken into account?
Best,


<EMAIL_ADDRESS>decompress error

Updating 'gimp' (2.10.38 -> 2.10.38-1)
Downloading new version
Loading gimp-2.10.38-setup-1.exe from cache.
Checking hash of gimp-2.10.38-setup-1.exe ... ok.
Uninstalling 'gimp' (2.10.38)
Installing 'gimp' (2.10.38-1) [64bit] from 'extras' bucket
Loading gimp-2.10.38-setup-1.exe from cache.
Extracting gimp-2.10.38-setup-1.exe ... ERROR Exit code was 1!
Failed to extract files from C:\Users\nz6nkj\scoop\apps\gimp\2.10.38-1\gimp-2.10.38-setup-1.exe.
Log file:
~\scoop\apps\gimp\2.10.38-1\innounp.log
Please try again or create a new issue by using the following link and paste your console output:
https://github.com/ScoopInstaller/Extras/issues/new?title=gimp%402.10.38-1%3A+decompress+error

I had a similar issue, except my innoup.log was (very slightly) different:
Signature detected: Inno Setup Setup Data (6.3.0)
This is not directly supported, but i'll try to unpack it as version 5602
; Version detected: 6300
Critical error: The setup files are corrupted. Please obtain a new copy of the program.

This is what the log shows for my installation error:
Signature detected: Inno Setup Setup Data (6.3.0)
This is not directly supported, but i'll try to unpack it as version 5602
; Version detected: 6300
Critical error: The setup files are corrupted. Please obtain a new copy of the program.
Signature detected: Inno Setup Setup Data (6.3.0)
This is not directly supported, but i'll try to unpack it as version 5602
; Version detected: 6300
Critical error: The setup files are corrupted. Please obtain a new copy of the program.

I even cleaned the scoop cache to redownload the file, and got the same error message.
scoop cache rm *

Relates to #13444.
With scoop v0.5.0+:
scoop bucket add versions
scoop install versions/innounp-unicode

as a workaround.

Also - is there a plan for an eventual non-workaround fix, that will "just work"?  Changing the requirements to explicitly list innounp-unicode instead of innounp, or somehow making innounp-unicode an official replacement/upgrade for innounp?

@pmolodo innounp is an Inno Setup Unpacker. The one in the versions bucket is newer, and is a unicode variant. The whole point of the versions bucket` is to provide "alternative" versions of packages, including development versions and pinned versions. See the linked description.
Output of scoop info main/innounp on my machine (after running scoop update to retrieve the latest digests):
Name        : innounp
Description : Inno Setup Unpacker
Version     : 0.50
Bucket      : main
Website     : https://innounp.sourceforge.net
License     : GPL-3.0-only
Updated at  : 2023-03-09 19:33:29
Updated by  : StarsbySea
Installed   : 0.50 *global*
Binaries    : innounp.exe

Output of scoop info versions/innounp-unicode:
Name        : innounp-unicode
Description : Inno Setup Unpacker (Unicode)
Version     : 1.73
Bucket      : versions
Website     : https://www.rathlev-home.de/tools/prog-e.html#unpack
License     : GPL-3.0-only
Updated at  : 2024-10-10 3:57:12
Updated by  : github-actions[bot]
Binaries    : innounp.exe

So yeah, quite a bit newer.

why does main/innounp not receive an update when it's so old and already causing problems?

I don't know, I just wrote what I know after first running into this problem myself this morning.

Is there any chance to getting this MR merged so we can stop getting this error (and stop new tickets for this issue from being created repeatedly)?
https://github.com/ScoopInstaller/Main/pull/6261
(Thanks @Daviteusz !)


[NoQA] Bump ESLint version to add prefer-at condition

Details
Bump ESLint version to add prefer-at condition.
Fixed Issues
$ https://github.com/Expensify/App/issues/43055
PROPOSAL: https://github.com/Expensify/App/issues/43055#issuecomment-2148253314
PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

@ShridharGoel The ESLint PR was merged, could you prioritize work on this one? Thanks 🙏

WDYT about asking for a full regression test here?

We can do that, but let's do it on one platform only to save time and money

@ShridharGoel Any updates here?

@ShridharGoel Any updates on this?

I think tests don't matter as much. If excluding them from this rule helps get this PR merged sooner, I'm all for it 👍

@ShridharGoel When do we expect to have updates here?

@ShridharGoel Any updates?

Will be updating completely in the next 1-2 days.
Sorry but you didn't respond any of Fabio's comments, almost all checks are failing now + this PR is one month old 😢

Given these, can we plan for this PR to be ready to merge in 1-2 days?

@ShridharGoel We got conflicts in the PR. Please address them together with the workflow failures (except Changed files ESLint check, let's ignore this one for now)

@ShridharGoel By looking at the workflow result, it seems to be only these ones:

src/pages/Search/SearchTypeMenuNarrow.tsx
src/components/DistanceRequest/DistanceRequestFooter.tsx
src/pages/home/report/ReportTypingIndicator.tsx

@ShridharGoel There is a section about your error (Invalid nesting in program blocks or scopes) in REACT_COMPILER.md

@ShridharGoel This issue has been reassigned, please check this https://github.com/Expensify/App/issues/43055#issuecomment-2363363294. So, I think this PR will be on hold.


AttributeError: module 'pycocotools' has no attribute 'version'

Hi,  I installed mmdet according to the instructions, but I still encountered this problem.
File "/home/lijiale/mmdet_install/mmdetection/mmdet/datasets/coco.py", line 19, in
assert pycocotools.version >= '12.0.2'
AttributeError: module 'pycocotools' has no attribute 'version'
I also tried to install pycocotools from open-mmlab/cocoapi, but I found that it installed mmpycocotools.  When I run pip list | grep pycocotools, I found that there are two pycocotools.
(open-mmlab) lijiale@ImageLab:~/mmdet_install/mmdetection3d$ pip list | grep pycocotools
mmpycocotools          12.0.2
pycocotools            2.0.2
Maybe this is the problem, but I don't know the specific reason. Could someone help me?

pip uninstall pycocotools

Please use the mmlab maintained pycocotools. To do that, you should first pip uninstall pycocotools and pip install mmpycocotools.

import pycocotools   pycocotools.file, to locate the pycocotools path which is used in current python environment. Then uninstall it.

Hey @ZwwWayne, when I install mmpycocotools, I get back the error ModuleNotFoundError: No module named 'pycocotools'
Would be great if you can help me out.

Hey @ZwwWayne, when I install mmpycocotools, I get back the error ModuleNotFoundError: No module named 'pycocotools'
Would be great if you can help me out.

Hey, I got this problem too. I solved it by uninstall mmpycocotools, and install it again.
Hope can help you!

Hey @ZwwWayne, when I install mmpycocotools, I get back the error ModuleNotFoundError: No module named 'pycocotools'
Would be great if you can help me out.

Hey, I got this problem too. I solved it by uninstall mmpycocotools, and install it again.
Hope can help you!

it works for me! thx

Hey @ZwwWayne, when I install mmpycocotools, I get back the error ModuleNotFoundError: No module named 'pycocotools'
Would be great if you can help me out.

Hey, I got this problem too. I solved it by uninstall mmpycocotools, and install it again. Hope can help you!

it worked for me

Hey @ZwwWayne, when I install mmpycocotools, I get back the error ModuleNotFoundError: No module named 'pycocotools'
Would be great if you can help me out.

Hey, I got this problem too. I solved it by uninstall mmpycocotools, and install it again. Hope can help you!

it works for me .  But I have a new bug.
FileNotFoundError: CocoDataset: [Errno 2] No such file or directory: 'data/nuimages/annotations/nuimages_v1.0-train.json'
I can't find this josn file.  Could someone help me ?


Generate usage info

Provide usage file with API calls count

https://github.com/keboola/darksky-augmentation/issues/2


PDF missing parts

Link to PDF file (or attach file here): http://www.liikennevirasto.fi/documents/20473/23384/Rataverkkokartta+2015/f1800f35-d3f7-4723-bb6e-c0091a75cff3
Configuration:

Web browser and its version: Firefox Nightly 50.0a1 (2016-07-21)
Operating system and its version: Ubuntu 16.04
PDF.js version: PDF.js: 1.5.337
Is an extension: No

Steps to reproduce the problem:

Open PDF
PDF is missing parts

What is the expected behavior? (add screenshot)

What went wrong? (add screenshot)

Link to a viewer (if hosted on a site other than mozilla.github.io/pdf.js or as Firefox/Chrome extension):
https://nightly.mozilla.org/

This might be a duplicate of #7486.

The fix for the referenced bug landed today, so it will probably be in today's or tomorrow's Nightly. @gitarra Could you confirm if upstream fixed this bug in that Nightly?

Well how did I miss that.. I will check if its fixed and report back.

Based on the result of mozregression, see http://mozilla.github.io/mozregression/, I'm closing this as a duplicate of issue #7498.


(JS-0458) Definitions for unused states detected

Description
You should avoid defining states that are not being used because unused states might affect while refactoring the codebase and introduces unnecessary operations by ReactJS. It is recommended to plan the behavior and operation of the component.
Occurrences
There are 9 occurrences of this issue in the repository.
See all occurrences on DeepSource → deepsource.io/gh/appsmithorg/appsmith/issue/JS-0458/occurrences/

@Rishabh-Rathod I would like to work on this issue. Please assign me this!

@Rishabh-Rathod i will like to work on this

@evergreenx
Thank you for showing interest in Appsmith.
Sorry, this issue has already been claimed. I would request you to please look at some of our other Good First Issues

I am interested for this issue, would you assign me ?

@ampatzidhs  thanks for showing interest 🎉 , This is all yours. Assigning this to you now.
Please don't forget to read the Contribution Guidelines. Would appreciate it if you can open a PR within the next 4 days.

@Rishabh-Rathod can you please assign this to me?

@priyanka-mahour  Greetings, thanks for showing interest 🎉 , This is all yours. Assigning this to you now.
Please don't forget to read the Contribution Guidelines. Would appreciate it if you can open a PR within the next few days.

Hello @Rishabh-Rathod
I noticed that this issue is still open and the previous PR that was opened for the issue was closed. The unused states still persist. I'd like to raise a PR fixing this, could you please assign me the issue?

Hi @rishabhrathod01  , can I work on this issue.

Hey @rishabhrathod01 is this issue is still open, i'd like to work on this

Hi! I noticed this issue is still open and would love to contribute. Is it okay if I work on this?


Track not-found items as skipped in Exchange

Issue
OneDrive was updated to track not-found items as skipped.  Exchange should do the same.  Currently we quietly drop not-found items.

Closing - decided not to mark not-found items as skipped.


Update table component to allow users to show more rows

The current data table component defaults to showing 10 rows. However, in the current Angular production version of the Platform, we allow users to see 10, 25, 50, or 100 rows.
Can we please update the table component to allow users to view more than 10 rows at once?

Also, if we plan to use the same data table component on the association page heat map, we may want to allow users to see up to 500 rows as we currently allow that in the Angular production version.

As discussed, we want the default behaviour to allow the table to expand to show all requested rows. This will allow the user to observe a longer list of entries without extra interaction. Also the scrolling solution has some unintended consequences, such as when users scroll the page and fall into a nested scrolling.

Ticket closed as work completed and pushed to alpha branch


Fix LICENSE and NOTICE handling

Maven doesn't like direct references to files outside the project.  This include references to the LICENSE and NOTICE files in the parent project.  The m2e plugin included with Mars reports this as an error. Previous attempts to fix this (replacing .. with ${project.parent.basedir} stopped m2e from complaining, but did not copy the files as expected.
This change moves the LICENSE and NOTICE files from the parent pom to jaggr-core and uses the maven-dependency-plugin to copy the files from jaggr-core into the other projects.

@ddumont added LICENSE and NOTICE file pointers to root project

lgtm


Update docs

Missing hasPermission() and hasRole() method to be add to documentation.

I have a plan: the docs in this repository will move to GitHub page in the same repo but different branch. Why? Because the docs (setup until advance setup) is too long to store in README.

All clear!


Loading remote data

can not be choosed .  why? who can help me, Data has shown that out.

This appears to be more of a usage question than a bug report or common feature request.  As we continue to keep the Select2 issue tracker geared towards these two areas, bug reports and common feature requests, we are redirecting usage questions to other communities such as the mailing list, IRC, or Stack Overflow.


feat(security): implement secrets-config proxy tls

Add implementation for secrets-config: proxy tls subcommand
It uploads the user-provided Kong TLS certificate/key pair to proxy server.
Closes: #2866
Signed-off-by: Jim Wang<EMAIL_ADDRESS>PR Checklist
Please check if your PR fulfills the following requirements:

[X ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

If your build fails due to your commit message not passing the build checks, please review the guidelines here: https://github.com/edgexfoundry/edgex-go/blob/master/.github/Contributing.md.
What is the current behavior?

Issue Number: #2866
What is the new behavior?
Added new implementation of proxy tls into secrets-config to upload the kong tls cert
Does this PR introduce a breaking change?

[ ] Yes
[X ] No

New Imports

[ ] Yes
[X ] No

Specific Instructions
Are there any specific instructions or things that should be known prior to reviewing?
Other information

Codecov Report

Merging #2930 (0b250cd) into master (7f9dd25) will increase coverage by 0.21%.
The diff coverage is 74.25%.

@@            Coverage Diff             @@
##           master    #2930      +/-   ##
==========================================
+ Coverage   40.27%   40.48%   +0.21%
==========================================
  Files         170      170
  Lines       13987    14081      +94
==========================================
+ Hits         5633     5701      +68
- Misses       7987     8002      +15
- Partials      367      378      +11

Impacted Files
Coverage Δ

...ernal/security/config/command/proxy/tls/command.go
77.39% <73.19%> (-22.61%)
:arrow_down:

...l/security/config/command/proxy/adduser/command.go
58.62% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7f9dd25...0b250cd. Read the comment docs.

Ok.  The code is uploading the cert but not making it active.
 openssl s_client -connect localhost:8443

should output the TLS cert that we uploaded.  It is currently returning the default cert.

Ok. The code is uploading the cert but not making it active.
 openssl s_client -connect localhost:8443

should output the TLS cert that we uploaded. It is currently returning the default cert.
Looks like the SNIs parameter is required and it won't take '*'

Added SNIS association, now the command line: openssl s_client -servername localhost -connect localhost:8443 responds with the user-provided TLS cert.

To test this locally on docker-based Kong, do the following steps:

git clone this PR
build codes by make build
copy the temporary res/ directory from security-proxy-setup's:    cp -r cmd/security-proxy-setup/res cmd/secrets-config/

open another terminal and go to developer-scripts master branch and change directory to compose-builder
run the edgex docker stack by make run
wait for few seconds to let the whole stack up and running
go back to the previous terminal that has edgex-go, and change directory to secrets-config:  cd cmd/secrets-config/

run the executable proxy tls  subcommand by:  ./secrets-config proxy tls --incert <Path_to_Your_Cert_In_Encoded_PEM_Format>yourcert.pem --inkey <Path_to_Your_Cert_Private_Key_In_PEM_Format>yourprivatekey

You should see no error in the console prompt after  you run that subcommand.
You can also verify the certificate being used against the running edgex docker-stack via curl command or openssl provided by Bryon's:

   openssl s_client -servername localhost -connect localhost:8443

Please update README.md with new command line option.


Can I assign EIPs to pods?

Is it possible to end up with EIPs assigned to pods? If so, can you provide me with some general pointers to what is involved?

you mean EIP on multus interfaces? if its not multus then you usually do via ALB or NLB with EIP

I do mean on multus interfaces. I do not want either type of load balancer involved.

yes its possible, in that case, code enhancement needed to assign and reassign the elastic IP on multus interfaces in the init/sidecar container code

Oh, I see! Thanks for the confirmation.


Benefit from updates to CA bundles

Took myself out as a reviewer of this PR since I'll be on vacation for the next few weeks.

Took myself out as a reviewer of this PR since I'll be on vacation for the next few weeks.

I'm not in a hurry. If I need this, I'll merge.

My point was to not get notified about this at all :stuck_out_tongue:


refactor: fixups based on experiences using the component in Enarx

    refactor: root `Ledger` to zero address

    Having start and end addresses for the `Ledger` adds complexity but is
    in-fact useless because they are not usually known before an application
    is running. Root ledger's start address to zero. This makes it fully
    compatible with static initialization and simplifies implementing the
    internals.

    Signed-off-by: Jarkko Sakkinen<EMAIL_ADDRESS>

Just tuned the commit message (2nd push).

Everybody will be better off by all practical means with zero-rooted ledger. One knob less to adjust and verify that it is correct.

@npmccallum fixing the remaining tests. the old find was not working well in mmap so I decided to make super clean implementation and separate functions. I need this for heap/enarx (once is fixed).

@npmccallum please pull asap, needed for https://github.com/enarx/enarx/pull/1596
All these tests did not pass with earlier find and in general two separate clean functions instead of combined multi-function is here better even if some redundancy.

I reject a zero-rooted ledger. A system may manage different sections of the address space with different ledgers. They must not overlap. That will lead to hard to debug issues.
All ledgers must define their region and reject all records that do not belong in that region.

I reject a zero-rooted ledger. A system may manage different sections of the address space with different ledgers. They must not overlap. That will lead to hard to debug issues.
All ledgers must define their region and reject all records that do not belong in that region.

Please show me a use case where this matters.

I reject a zero-rooted ledger. A system may manage different sections of the address space with different ledgers. They must not overlap. That will lead to hard to debug issues.
All ledgers must define their region and reject all records that do not belong in that region.

Please show me a use case where this matters.

The base address is in all possible situations stored elsewhere than the ledger. Ledger carries relative addresses, not absolute.

I'll drop that commit, not a high priority. Just don't see any use for it.

@npmccallum it's now rebased.

Squashed into single commit.

@npmccallum I'll update shim-sgx once this has been merged.

Actually, I can update shim-sgx already since Cargo.toml points to this branch. No need to hold on that.

https://github.com/enarx/enarx/pull/1595 has been update accordingly.


[ToggleButton][ToggleButtonGroup] Create ToggleButton and ToggleButtonGroup

Closes https://github.com/mui/base-ui/issues/11
Closes https://github.com/mui/base-ui/issues/31
Docs:

ToggleButton https://deploy-preview-763--base-ui.netlify.app/components/react-toggle-button
ToggleButtonGroup https://deploy-preview-763--base-ui.netlify.app/components/react-toggle-button-group

@colmtuite just pinging you for a review 🙏

This PR is up to date with all the library changes since it was opened, pinging @colmtuite again for a review 🙏

Docs don't mention the disabled prop on ToggleGroup.
Missing orientation?
Missing loop?
ToggleGroup docs content not updated with recent changes (Anatomy etc.).

Docs don't mention the disabled prop on ToggleGroup.
Missing orientation?
Missing loop?
ToggleGroup docs content not updated with recent changes (Anatomy etc.).

@colmtuite I double checked and the props are all here, also fixed the docs content (anatomy)
I think there is an issue on master right now causing the props table to not generate correctly, so they appear missing from the docs in the deploy preview, I'll investigate this separately


Linking error

https://helpx.adobe.com/analytics/kb/troubleshoot-billing.html
links to
Issue in ./help/admin/c-server-call-usage/overage-overview.md

@gigazelle

Hi Daniel, can you please elaborate what the issue is? We retired the helpx domain several years ago, and moved all the content to Experience League.

Hi, the problem was that I had a billing issue for my CC subscription and the help text that I've found that should link to that content was gone. I could resolve the billing issue, but you might want to check your help system for missing links on this topic.


Documentation update

Updated documents to include the default name of the config file, and indicate it must be in the root of where the docker-compose is run

Docker Image for build 1 is available on DockerHub as jc21/nginx-proxy-manager:github-pr-345

Docker Image for build 2 is available on DockerHub as jc21/nginx-proxy-manager:github-pr-345


rename coinstac-ui to coinstac-desktop-client

Please check if the PR fulfills these requirements

[ ] Have you checked to ensure there aren't other open Pull Requests for the same update/change?
[ ] Passes e2e testing

What is the current behavior?
closes issue #

@rssk There are some references to external docker images that have been changed with the rename. How can we rename those external dependencies to reflect the new name?


Create brezova

@honzakucera I am sorry, this request remains unanswered for a while. I have to close it without merging. Please reopen and comment if you have an update regarding the abovementioned issue. Thank you for the understanding!


Translocator <IP_ADDRESS> (MC 1.7.10) Thermal Expansion duplication glitch.

Not sure if still persistent.
To reproduce:
1. Place down a crafting grid.
2. Place any (non-basic) Thermal Expansion machine in the center.
3. Pick up your crafting materials using C on the crafting grid.
4. Duped.
http://i.imgur.com/kWQW1Os.gifv

Seems to be related to #18