Failing to serve shape log

As per this report on Discord, it seems that there is a bug in the sync service which causes it to pass a wrong last_offset to the get_log_stream function and thus fails to retrieve the shape log. This is the relevant part of the backend log:
electric-1  |
electric-1  | 19:49:21.801 [error] ** (Plug.Conn.WrapperError) ** (FunctionClauseError) no function clause matching in Electric.ShapeCache.Storage.get_log_stream/4
electric-1  |     (electric 0.2.7) lib/electric/shape_cache/storage.ex:128: Electric.ShapeCache.Storage.get_log_stream("69258598-1723664840890", LogOffset.new(78166000, 0), LogOffset.new(0, 0), {Electric.ShapeCache.CubDbStorage, %{db: :shape_db, file_path: "./shapes"}})
electric-1  |     (electric 0.2.7) lib/electric/plug/serve_shape_plug.ex:301: Electric.Plug.ServeShapePlug.serve_log_or_snapshot/2
electric-1  |     (electric 0.2.7) lib/electric/plug/serve_shape_plug.ex:1: Electric.Plug.ServeShapePlug.plug_builder_call/2
electric-1  |     (electric 0.2.7) deps/plug/lib/plug/router.ex:246: anonymous fn/4 in Electric.Plug.Router.dispatch/2
electric-1  |     (telemetry 1.2.1) /app/deps/telemetry/src/telemetry.erl:321: :telemetry.span/3
electric-1  |     (electric 0.2.7) deps/plug/lib/plug/router.ex:242: Electric.Plug.Router.dispatch/2
electric-1  |     (electric 0.2.7) lib/electric/plug/router.ex:1: Electric.Plug.Router.plug_builder_call/2
electric-1  |     (bandit 1.5.5) lib/bandit/pipeline.ex:124: Bandit.Pipeline.call_plug!/2
electric-1  |     (bandit 1.5.5) lib/bandit/pipeline.ex:36: Bandit.Pipeline.run/4
electric-1  |     (bandit 1.5.5) lib/bandit/http1/handler.ex:12: Bandit.HTTP1.Handler.handle_data/3
electric-1  |     (bandit 1.5.5) lib/bandit/delegating_handler.ex:18: Bandit.DelegatingHandler.handle_data/3
electric-1  |     (bandit 1.5.5) /app/deps/thousand_island/lib/thousand_island/handler.ex:411: Bandit.DelegatingHandler.handle_continue/2
electric-1  |     (stdlib 6.0.1) gen_server.erl:2163: :gen_server.try_handle_continue/3
electric-1  |     (stdlib 6.0.1) gen_server.erl:2072: :gen_server.loop/7
electric-1  |     (stdlib 6.0.1) proc_lib.erl:329: :proc_lib.init_p_do_apply/3
electric-1  |
electric-1  |

This is about this Elixir function from Storage which is not matching the call:
def get_log_stream(shape_id, offset, max_offset \\ LogOffset.last(), {mod, opts})
  when max_offset == :infinity or not is_log_offset_lt(max_offset, offset),
  do: mod.get_log_stream(shape_id, offset, max_offset, opts)

So, basically, get_log_stream fetches a portion from the log from offset till max_offset. Therefore, the guard checks that the max_offset is bigger or equal to the start offset (i.e. not lesser than is the same as bigger or equal than). However, somehow, the max_offset in the call is the very first log offset (0, 0). And thus this function does not match, hence, the error.
This Storage.get_log_stream/4 function is called by Electric.Shapes.get_log_stream/3 which fetches the offset and max_offset from the opts it gets:
def get_log_stream(config, shape_id, opts) do
  offset = Access.get(opts, :since, LogOffset.before_all())
  max_offset = Access.get(opts, :up_to, LogOffset.last())
  storage = Access.fetch!(config, :storage)
  Storage.get_log_stream(shape_id, offset, max_offset, storage)
end

This Electric.Shapes.get_log_stream/3 function is called in 2 places in the shape plug in Electric.Plug.ServeShapePlug.serve_log_or_snapshot/2. Both calls essentially fetch the offset and max_offset from the connection's assigns.offset and assigns.last_offset.
The assigns.last_offset is set initially when loading the shape info (when the request comes in) and updated in hold_until_change (i.e. only in live mode) when a new change comes in. I'm suspecting that there is a condition that triggers a shape rotation (that condition can only be a truncate?) which causes the latest offset to become (0, 0) and hold_until_change then updates the last_offset to (0, 0).  We should try to reproduce.

Do we have a reproduction for this @alco

Hey @KyleAMathews. I've only just started looking into it. I noticed that the function guard is incorrect when I first read the description, fix is pending in https://github.com/electric-sql/electric/pull/1557. Writing a regression test is up next on my list.

I haven't been able to reproduce this. When a table is truncated, the client gets the 409 response regardless of whether it sends a regular or a live request for the shape ID.
Closing this as a non-issue.


Address typo

What kind of changes does this PR include?

Minor content fixes (broken links, typos, etc.)

Description

What does this PR change?
- I noticed a typo while reading through documentation.
Did you change something visual? A before/after screenshot can be helpful.

Before

After

Thanks for this @ted-dino! Unfortunately, this is a page that gets automatically generated from this integration’s README, which lives here: https://github.com/withastro/astro/blob/main/packages/integrations/image/README.md
We’ll need to update the file in that repo instead of this one. I can still merge this, but it’ll get overwritten tomorrow 😅
Would you be up for making this same fix in that file instead?

Thanks for this @ted-dino! Unfortunately, this is a page that gets automatically generated from this integration’s README, which lives here: https://github.com/withastro/astro/blob/main/packages/integrations/image/README.md
We’ll need to update the file in that repo instead of this one. I can still merge this, but it’ll get overwritten tomorrow sweat_smile
Would you be up for making this same fix in that file instead?

meaning i have to redo my PR?


Fix: Wrong tar layout on Windows platform when exporting image by regctl

Fixes issue
fixes #786

Describe the change

Using / as path separator on tarball generation and index.json instead of platform specific separator.
How to verify it

Running the following commands on Windows, then verify the tar file.
.\regctl-windows-amd64.exe image export -p "linux/amd64" library/nginx:latest nginx-linux-amd64.tar

Changelog text

Fix: Wrong tar layout on Windows platform when exporting image by regctl

Please verify and check that the pull request fulfills the following requirements

[x] Tests have been added or not applicable
[x] Documentation has been added, updated, or not applicable
[x] Changes have been rebased to main
[x] Multiple commits to the same code have been squashed

Should be fixed by #788 , closed.


feat: implement Backoff Strategy

Fixed, Linear and Exponential backoff strategy implemented on this mr. I add the retry-attempt-count field on the kafka message header. And then each backoff strategy run own rule through retryCount and retryAttempCount. I will share the flow chart with you.
The users can configure easily like this;
`...
      cron: "*/1 * * * *"
      backOffStrategy: "exponential"
      duration: 1m
      concurrency: 1

`
Scenarious:

Linear Backoff: It involves linearly increasing the time between each retry attempt. (1, 2, 3, 4..)
Exponential Backoff: It involves exponentially increasing the time between each retry attempt. (1, 2, 4, 8..)
Fixed Backoff: In this strategy, the delay between retry attempts remains constant. This strategy is simple to implement but may not be suitable for all scenarios.

The initial value of the retry-attempt-count is 1.

Merged this pr instead of this one, for developing additional things
thank you <3


Publish 05/14/2021, 3:30 PM

Docs Build status updates of commit bba907c:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docset/winserver2016-ps/adfs/Remove-AdfsFarmNode.md
:warning:Warning
View (WindowsServer2016-ps)
Details

docset/winserver2016-ps/smbshare/Disable-SmbDelegation.md
:warning:Warning
View (WindowsServer2016-ps)
Details

docset/winserver2016-ps/smbshare/Enable-SmbDelegation.md
:warning:Warning
View (WindowsServer2016-ps)
Details

docset/winserver2016-ps/smbshare/Get-SmbBandwidthLimit.md
:warning:Warning
View (WindowsServer2016-ps)
Details

docset/winserver2016-ps/smbshare/Get-SmbDelegation.md
:warning:Warning
View (WindowsServer2016-ps)
Details

docset/winserver2016-ps/smbshare/Remove-SmbBandwidthLimit.md
:warning:Warning
View (WindowsServer2016-ps)
Details

docset/winserver2016-ps/smbshare/Set-SmbBandwidthLimit.md
:warning:Warning
View (WindowsServer2016-ps)
Details

docset/winserver2019-ps/adfs/Remove-AdfsFarmNode.md
:warning:Warning
View (WindowsServer2019-ps)
Details

docset/winserver2022-ps/adfs/Remove-AdfsFarmNode.md
:warning:Warning
View (WindowsServer2022-ps)
Details

docset/winserver2019-ps/smbshare/Set-SmbBandwidthLimit.md
:warning:Warning
View (WindowsServer2019-ps)
Details

docset/winserver2022-ps/smbshare/Set-SmbBandwidthLimit.md
:warning:Warning
View (WindowsServer2022-ps)
Details

docset/winserver2019-ps/smbshare/Get-SmbBandwidthLimit.md
:warning:Warning
View (WindowsServer2019-ps)
Details

docset/winserver2022-ps/smbshare/Get-SmbBandwidthLimit.md
:warning:Warning
View (WindowsServer2022-ps)
Details

docset/winserver2019-ps/smbshare/Enable-SmbDelegation.md
:warning:Warning
View (WindowsServer2019-ps)
Details

docset/winserver2022-ps/smbshare/Enable-SmbDelegation.md
:warning:Warning
View (WindowsServer2022-ps)
Details

docset/winserver2019-ps/smbshare/Get-SmbDelegation.md
:warning:Warning
View (WindowsServer2019-ps)
Details

docset/winserver2022-ps/smbshare/Get-SmbDelegation.md
:warning:Warning
View (WindowsServer2022-ps)
Details

docset/winserver2019-ps/smbshare/Disable-SmbDelegation.md
:warning:Warning
View (WindowsServer2019-ps)
Details

docset/winserver2022-ps/smbshare/Disable-SmbDelegation.md
:warning:Warning
View (WindowsServer2022-ps)
Details

docset/winserver2019-ps/smbshare/Remove-SmbBandwidthLimit.md
:warning:Warning
View (WindowsServer2019-ps)
Details

docset/winserver2022-ps/smbshare/Remove-SmbBandwidthLimit.md
:warning:Warning
View (WindowsServer2022-ps)
Details

docset/docfx.json
:white_check_mark:Succeeded

docset/docs-conceptual/mdop/get-started.md
:white_check_mark:Succeeded
View (win-mdop2-ps)

docset/docs-conceptual/winserver2012-ps/get-started.md
:white_check_mark:Succeeded
View (winserver2012-ps)

docset/docs-conceptual/winserver2012r2-ps/get-started.md
:white_check_mark:Succeeded
View (winserver2012r2-ps)

docset/docs-conceptual/winserver2016-ps/get-started.md
:white_check_mark:Succeeded
View (WindowsServer2016-ps)

docset/docs-conceptual/winserver2019-ps/get-started.md
:white_check_mark:Succeeded
View (WindowsServer2019-ps)

docset/docs-conceptual/winserver2022-ps/get-started.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/mapping/cabgenConfig.json
:white_check_mark:Succeeded

docset/winserver2016-ps/Microsoft.DiagnosticDataViewer/Disable-DiagnosticDataViewing.md
:white_check_mark:Succeeded
View (WindowsServer2016-ps)

docset/winserver2016-ps/Microsoft.DiagnosticDataViewer/Enable-DiagnosticDataViewing.md
:white_check_mark:Succeeded
View (WindowsServer2016-ps)

docset/winserver2016-ps/Microsoft.DiagnosticDataViewer/Get-DiagnosticData.md
:white_check_mark:Succeeded
View (WindowsServer2016-ps)

docset/winserver2016-ps/Microsoft.DiagnosticDataViewer/Get-DiagnosticDataTypes.md
:white_check_mark:Succeeded
View (WindowsServer2016-ps)

docset/winserver2016-ps/Microsoft.DiagnosticDataViewer/Get-DiagnosticDataViewingSetting.md
:white_check_mark:Succeeded
View (WindowsServer2016-ps)

docset/winserver2016-ps/Microsoft.DiagnosticDataViewer/Get-DiagnosticStoreCapacity.md
:white_check_mark:Succeeded
View (WindowsServer2016-ps)

docset/winserver2016-ps/Microsoft.DiagnosticDataViewer/Microsoft.DiagnosticDataViewer.md
:white_check_mark:Succeeded
View (WindowsServer2016-ps)

docset/winserver2016-ps/Microsoft.DiagnosticDataViewer/Set-DiagnosticStoreCapacity.md
:white_check_mark:Succeeded
View (WindowsServer2016-ps)

docset/winserver2016-ps/Microsoft.Windows.ServerManager.Migration/Disable-ServerManagerStandardUserRemoting.md
:white_check_mark:Succeeded

docset/winserver2016-ps/Microsoft.Windows.ServerManager.Migration/Enable-ServerManagerStandardUserRemoting.md
:white_check_mark:Succeeded

docset/winserver2016-ps/Microsoft.Windows.ServerManager.Migration/Export-SmigServerSetting.md
:white_check_mark:Succeeded

docset/winserver2016-ps/Microsoft.Windows.ServerManager.Migration/Get-SmigServerFeature.md
:white_check_mark:Succeeded

docset/winserver2016-ps/Microsoft.Windows.ServerManager.Migration/Get-WindowsFeature.md
:white_check_mark:Succeeded

docset/winserver2016-ps/Microsoft.Windows.ServerManager.Migration/Import-SmigServerSetting.md
:white_check_mark:Succeeded

docset/winserver2016-ps/Microsoft.Windows.ServerManager.Migration/Install-WindowsFeature.md
:white_check_mark:Succeeded

docset/winserver2016-ps/Microsoft.Windows.ServerManager.Migration/Microsoft.Windows.ServerManager.Migration.md
:white_check_mark:Succeeded

docset/winserver2016-ps/Microsoft.Windows.ServerManager.Migration/Receive-SmigServerData.md
:white_check_mark:Succeeded

docset/winserver2016-ps/Microsoft.Windows.ServerManager.Migration/Send-SmigServerData.md
:white_check_mark:Succeeded

docset/winserver2016-ps/Microsoft.Windows.ServerManager.Migration/ServerManager.md
:white_check_mark:Succeeded

docset/winserver2016-ps/Microsoft.Windows.ServerManager.Migration/Uninstall-WindowsFeature.md
:white_check_mark:Succeeded

docset/winserver2016-ps/activedirectory/ActiveDirectory.md
:white_check_mark:Succeeded
View (WindowsServer2016-ps)

This comment lists only the first 50 files in the pull request.

docset/winserver2016-ps/adfs/Remove-AdfsFarmNode.md

Line 0, Column 0: [Warning-link-out-of-scope] File 'winserver2016-ps/Microsoft.Windows.ServerManager.Migration/Uninstall-WindowsFeature.md' referenced by link '../Microsoft.Windows.ServerManager.Migration/Uninstall-WindowsFeature.md' will not be built because it is not included in build scope.

docset/winserver2016-ps/smbshare/Disable-SmbDelegation.md

Line 0, Column 0: [Warning-link-out-of-scope] File 'winserver2016-ps/Microsoft.Windows.ServerManager.Migration/Install-WindowsFeature.md' referenced by link '../Microsoft.Windows.ServerManager.Migration/Install-WindowsFeature.md' will not be built because it is not included in build scope.

docset/winserver2016-ps/smbshare/Enable-SmbDelegation.md

Line 0, Column 0: [Warning-link-out-of-scope] File 'winserver2016-ps/Microsoft.Windows.ServerManager.Migration/Install-WindowsFeature.md' referenced by link '../Microsoft.Windows.ServerManager.Migration/Install-WindowsFeature.md' will not be built because it is not included in build scope.

docset/winserver2016-ps/smbshare/Get-SmbBandwidthLimit.md

Line 0, Column 0: [Warning-link-out-of-scope] File 'winserver2016-ps/Microsoft.Windows.ServerManager.Migration/Install-WindowsFeature.md' referenced by link '../Microsoft.Windows.ServerManager.Migration/Install-WindowsFeature.md' will not be built because it is not included in build scope.

docset/winserver2016-ps/smbshare/Get-SmbDelegation.md

Line 0, Column 0: [Warning-link-out-of-scope] File 'winserver2016-ps/Microsoft.Windows.ServerManager.Migration/Install-WindowsFeature.md' referenced by link '../Microsoft.Windows.ServerManager.Migration/Install-WindowsFeature.md' will not be built because it is not included in build scope.

docset/winserver2016-ps/smbshare/Remove-SmbBandwidthLimit.md

Line 0, Column 0: [Warning-link-out-of-scope] File 'winserver2016-ps/Microsoft.Windows.ServerManager.Migration/Install-WindowsFeature.md' referenced by link '../Microsoft.Windows.ServerManager.Migration/Install-WindowsFeature.md' will not be built because it is not included in build scope.

docset/winserver2016-ps/smbshare/Set-SmbBandwidthLimit.md

Line 0, Column 0: [Warning-link-out-of-scope] File 'winserver2016-ps/Microsoft.Windows.ServerManager.Migration/Install-WindowsFeature.md' referenced by link '../Microsoft.Windows.ServerManager.Migration/Install-WindowsFeature.md' will not be built because it is not included in build scope.

docset/winserver2019-ps/adfs/Remove-AdfsFarmNode.md

Line 0, Column 0: [Warning-link-out-of-scope] File 'winserver2019-ps/Microsoft.Windows.ServerManager.Migration/Uninstall-WindowsFeature.md' referenced by link '../Microsoft.Windows.ServerManager.Migration/Uninstall-WindowsFeature.md' will not be built because it is not included in build scope.

docset/winserver2022-ps/adfs/Remove-AdfsFarmNode.md

Line 0, Column 0: [Warning-link-out-of-scope] File 'winserver2022-ps/Microsoft.Windows.ServerManager.Migration/Uninstall-WindowsFeature.md' referenced by link '../Microsoft.Windows.ServerManager.Migration/Uninstall-WindowsFeature.md' will not be built because it is not included in build scope.

docset/winserver2019-ps/smbshare/Set-SmbBandwidthLimit.md

Line 0, Column 0: [Warning-link-out-of-scope] File 'winserver2019-ps/Microsoft.Windows.ServerManager.Migration/Install-WindowsFeature.md' referenced by link '../Microsoft.Windows.ServerManager.Migration/Install-WindowsFeature.md' will not be built because it is not included in build scope.

docset/winserver2022-ps/smbshare/Set-SmbBandwidthLimit.md

Line 0, Column 0: [Warning-link-out-of-scope] File 'winserver2022-ps/Microsoft.Windows.ServerManager.Migration/Install-WindowsFeature.md' referenced by link '../Microsoft.Windows.ServerManager.Migration/Install-WindowsFeature.md' will not be built because it is not included in build scope.

docset/winserver2019-ps/smbshare/Get-SmbBandwidthLimit.md

Line 0, Column 0: [Warning-link-out-of-scope] File 'winserver2019-ps/Microsoft.Windows.ServerManager.Migration/Install-WindowsFeature.md' referenced by link '../Microsoft.Windows.ServerManager.Migration/Install-WindowsFeature.md' will not be built because it is not included in build scope.

docset/winserver2022-ps/smbshare/Get-SmbBandwidthLimit.md

Line 0, Column 0: [Warning-link-out-of-scope] File 'winserver2022-ps/Microsoft.Windows.ServerManager.Migration/Install-WindowsFeature.md' referenced by link '../Microsoft.Windows.ServerManager.Migration/Install-WindowsFeature.md' will not be built because it is not included in build scope.

docset/winserver2019-ps/smbshare/Enable-SmbDelegation.md

Line 0, Column 0: [Warning-link-out-of-scope] File 'winserver2019-ps/Microsoft.Windows.ServerManager.Migration/Install-WindowsFeature.md' referenced by link '../Microsoft.Windows.ServerManager.Migration/Install-WindowsFeature.md' will not be built because it is not included in build scope.

docset/winserver2022-ps/smbshare/Enable-SmbDelegation.md

Line 0, Column 0: [Warning-link-out-of-scope] File 'winserver2022-ps/Microsoft.Windows.ServerManager.Migration/Install-WindowsFeature.md' referenced by link '../Microsoft.Windows.ServerManager.Migration/Install-WindowsFeature.md' will not be built because it is not included in build scope.

docset/winserver2019-ps/smbshare/Get-SmbDelegation.md

Line 0, Column 0: [Warning-link-out-of-scope] File 'winserver2019-ps/Microsoft.Windows.ServerManager.Migration/Install-WindowsFeature.md' referenced by link '../Microsoft.Windows.ServerManager.Migration/Install-WindowsFeature.md' will not be built because it is not included in build scope.

docset/winserver2022-ps/smbshare/Get-SmbDelegation.md

Line 0, Column 0: [Warning-link-out-of-scope] File 'winserver2022-ps/Microsoft.Windows.ServerManager.Migration/Install-WindowsFeature.md' referenced by link '../Microsoft.Windows.ServerManager.Migration/Install-WindowsFeature.md' will not be built because it is not included in build scope.

docset/winserver2019-ps/smbshare/Disable-SmbDelegation.md

Line 0, Column 0: [Warning-link-out-of-scope] File 'winserver2019-ps/Microsoft.Windows.ServerManager.Migration/Install-WindowsFeature.md' referenced by link '../Microsoft.Windows.ServerManager.Migration/Install-WindowsFeature.md' will not be built because it is not included in build scope.

docset/winserver2022-ps/smbshare/Disable-SmbDelegation.md

Line 0, Column 0: [Warning-link-out-of-scope] File 'winserver2022-ps/Microsoft.Windows.ServerManager.Migration/Install-WindowsFeature.md' referenced by link '../Microsoft.Windows.ServerManager.Migration/Install-WindowsFeature.md' will not be built because it is not included in build scope.

docset/winserver2019-ps/smbshare/Remove-SmbBandwidthLimit.md

Line 0, Column 0: [Warning-link-out-of-scope] File 'winserver2019-ps/Microsoft.Windows.ServerManager.Migration/Install-WindowsFeature.md' referenced by link '../Microsoft.Windows.ServerManager.Migration/Install-WindowsFeature.md' will not be built because it is not included in build scope.

docset/winserver2022-ps/smbshare/Remove-SmbBandwidthLimit.md

Line 0, Column 0: [Warning-link-out-of-scope] File 'winserver2022-ps/Microsoft.Windows.ServerManager.Migration/Install-WindowsFeature.md' referenced by link '../Microsoft.Windows.ServerManager.Migration/Install-WindowsFeature.md' will not be built because it is not included in build scope.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


GoModJsonParser doesn't support correctly replace structure

Describe the bug
GoModJsonParser doesn't parse go.mod's replace structure correctly as it seems to crash always into the first replace item.
Example of go.mod: https://github.com/kubernetes/kops/blob/master/go.mod
Version of dependency-check used
The problem occurs using version 6.0.2+ of the cli
Note: PR #3111 is required for parsing the modules!
Log file
INFO] Checking for updates
[INFO] Skipping NVD check since last check was within 24 hours.
[INFO] Skipping RetireJS update since last update was within 24 hours.
[INFO] Check for updates complete (52 ms)
[INFO]

Dependency-Check is an open source tool performing a best effort analysis of 3rd party dependencies; false positives and false negatives may exist in the analysis performed by the tool. Use of the tool and the reporting provided constitutes acceptance for use in an AS IS condition, and there are NO warranties, implied or otherwise, with regard to the analysis or its use. Any use of the tool and the reporting provided is at the user’s risk. In no event shall the copyright holder or OWASP be held liable for any damages whatsoever arising out of or in connection with the use of this tool, the analysis performed, or the resulting report.

[INFO] Analysis Started
[INFO] Finished File Name Analyzer (0 seconds)
[WARN] Warnings from go go list -m: can't compute 'all' using the vendor directory
	(Use -mod=mod or -mod=readonly to bypass.)

[WARN] Switching to `go list -json -m -mod=readonly all`
[WARN] Warnings from go
[WARN] An error occurred while analyzing '/Users/foobar/Temp/kops/go.mod' (Golang Mod Analyzer).
[INFO] Finished Golang Mod Analyzer (0 seconds)
[INFO] Finished Dependency Merging Analyzer (0 seconds)
[INFO] Finished Version Filter Analyzer (0 seconds)
[INFO] Finished Hint Analyzer (0 seconds)
[INFO] Created CPE Index (1 seconds)
[INFO] Finished NPM CPE Analyzer (1 seconds)
[INFO] Created CPE Index (1 seconds)
[INFO] Finished CPE Analyzer (1 seconds)
[INFO] Finished False Positive Analyzer (0 seconds)
[INFO] Finished NVD CVE Analyzer (0 seconds)
[WARN] Unable to determine Package-URL identifiers for 1 dependencies
[INFO] Finished Sonatype OSS Index Analyzer (0 seconds)
[INFO] Finished Vulnerability Suppression Analyzer (0 seconds)
[INFO] Finished Dependency Bundling Analyzer (0 seconds)
[INFO] Analysis Complete (3 seconds)
[INFO] Writing report to: /Users/foobar/Temp/kops/./dependency-check-report.html
[ERROR] Error parsing stream

2021-01-29 22:24:33,940 org.owasp.dependencycheck.App:208
ERROR - Error parsing stream
2021-01-29 22:24:33,941 org.owasp.dependencycheck.App:209
DEBUG - unexpected error
org.owasp.dependencycheck.analyzer.exception.AnalysisException: Error parsing stream
        at org.owasp.dependencycheck.data.golang.GoModJsonParser.process(GoModJsonParser.java:86)
        at org.owasp.dependencycheck.processing.GoModProcessor.run(GoModProcessor.java:62)
        at java.base/java.lang.Thread.run(Thread.java:832)
        Suppressed: org.owasp.dependencycheck.analyzer.exception.AnalysisException: Error parsing stream
                ... 3 common frames omitted
        Caused by: javax.json.stream.JsonParsingException: Invalid token=EOF at (line no=1, column no=0, offset=-1). Expected tokens are: [CURLYOPEN, SQUAREOPEN, STRING, NUMBER, TRUE, FALSE, NULL]
                at org.glassfish.json.JsonParserImpl.parsingException(JsonParserImpl.java:450)
                at org.glassfish.json.JsonParserImpl.access$1100(JsonParserImpl.java:79)
                at org.glassfish.json.JsonParserImpl$NoneContext.getNextEvent(JsonParserImpl.java:438)
                at org.glassfish.json.JsonParserImpl.next(JsonParserImpl.java:376)
                at org.glassfish.json.JsonReaderImpl.readArray(JsonReaderImpl.java:128)
                at org.owasp.dependencycheck.data.golang.GoModJsonParser.process(GoModJsonParser.java:71)
                ... 2 common frames omitted
Caused by: javax.json.stream.JsonParsingException: Invalid token=COMMA at (line no=4036, column no=4, offset=145386). Expected tokens are: [STRING]
        at org.glassfish.json.JsonParserImpl.parsingException(JsonParserImpl.java:450)
        at org.glassfish.json.JsonParserImpl.access$1100(JsonParserImpl.java:79)
        at org.glassfish.json.JsonParserImpl$ObjectContext.getNextEvent(JsonParserImpl.java:511)
        at org.glassfish.json.JsonParserImpl.next(JsonParserImpl.java:376)
        at org.glassfish.json.JsonParserImpl.getObject(JsonParserImpl.java:335)
        at org.glassfish.json.JsonParserImpl.getValue(JsonParserImpl.java:182)
        at org.glassfish.json.JsonParserImpl.getArray(JsonParserImpl.java:328)
        at org.glassfish.json.JsonParserImpl.getArray(JsonParserImpl.java:164)
        at org.glassfish.json.JsonReaderImpl.readArray(JsonReaderImpl.java:129)
        at org.owasp.dependencycheck.data.golang.GoModJsonParser.process(GoModJsonParser.java:71)
        ... 2 common frames omitted
2021-01-29 22:24:33,941 org.owasp.dependencycheck.utils.Settings:751
DEBUG - Deleting ALL temporary files from `/var/folders/s1/f8pyrlws7hb2f134d_mmrxsx45s2vv/T/dctemp0d4a9ccd-5194-471d-9542-87761407aadc`
2021-01-29 22:24:33,962 org.owasp.dependencycheck.App:82
DEBUG - Exit code: -14

To Reproduce
Steps to reproduce the behavior:

Use PR #3110 (main branch is unable to list modules)
Clone kOPS: git clone https://github.com/kubernetes/kops.git
Analyze kOPS: dependency-check -l debug.log --cveValidForHours 24 --scan go.mod --enableExperimental --project kops
See stdout and debug.log

Expected behavior
Successful JSON parsing.

Had a quick look at the code and this one pointed out: https://github.com/jeremylong/DependencyCheck/blob/main/utils/src/main/java/org/owasp/dependencycheck/utils/JsonArrayFixingInputStream.java#L161-L162
//this only works because the output always
// has a \n following a closing brace..

Now, there's a comma instead of linefeed after the closing brace:
{
        "Path": "k8s.io/api",
        "Version": "v0.20.0",
        "Replace": {
                "Path": "k8s.io/api",
                "Version": "v0.20.0",
                "Time": "2020-12-08T21:01:33Z",
                "GoMod"<EMAIL_ADDRESS>                "GoVersion": "1.15"
        },
        "GoMod"<EMAIL_ADDRESS>        "GoVersion": "1.15"
}

Had a quick look at the code and this one pointed out: https://github.com/jeremylong/DependencyCheck/blob/main/utils/src/main/java/org/owasp/dependencycheck/utils/JsonArrayFixingInputStream.java#L161-L162
//this only works because the output always
// has a \n following a closing brace..

Now, there's a comma instead of linefeed after the closing brace:
{
        "Path": "k8s.io/api",
        "Version": "v0.20.0",
        "Replace": {
                "Path": "k8s.io/api",
                "Version": "v0.20.0",
                "Time": "2020-12-08T21:01:33Z",
                "GoMod"<EMAIL_ADDRESS>                "GoVersion": "1.15"
        },
        "GoMod"<EMAIL_ADDRESS>        "GoVersion": "1.15"
}

Created a test for GoModJsonParser.process with a full output go list -json -m --mod=readonly all of kOPS as input and it works fine. I just can't figure out, what's going on here. Maybe something related to ProcessReader?

Created a test for GoModJsonParser.process with a full output go list -json -m --mod=readonly all of kOPS as input and it works fine. I just can't figure out, what's going on here. Maybe something related to ProcessReader?

I just used the current snapshot version on the kOPS repo and it worked successfully. The issue with replace should have been resolved with #2987.

I just used the current snapshot version on the kOPS repo and it worked successfully. The issue with replace should have been resolved with #2987.

git clean -Xdf && mvn -s settings.xml install fixed the issue also for me. Both kubernetes and kops repositories works now out-of-the-box.
I also found out the issue on my local repo:
module github.com/foo/bar

go 1.15

replace github.com/prometheus-operator/prometheus-operator => github.com/prometheus-operator/prometheus-operator v0.43.0

require (
        github.com/prometheus-operator/prometheus-operator v0.0.0-00010101000000-000000000000
)

{
	"Path": "github.com/prometheus-operator/prometheus-operator",
	"Version": "v0.0.0-00010101000000-000000000000",
	"Replace": {
		"Path": "github.com/prometheus-operator/prometheus-operator",
		"Version": "v0.43.0",
		"Time": "2020-10-27T08:04:46Z",
		"Dir"<EMAIL_ADDRESS>		"GoMod"<EMAIL_ADDRESS>	},
	"Dir"<EMAIL_ADDRESS>	"GoMod"<EMAIL_ADDRESS>
The dummy version v0.0.0-00010101000000-000000000000 that's going to be replaced is the culprit and using a proper version string seems to fix the analyzer as well.

git clean -Xdf && mvn -s settings.xml install fixed the issue also for me. Both kubernetes and kops repositories works now out-of-the-box.
I also found out the issue on my local repo:
module github.com/foo/bar

go 1.15

replace github.com/prometheus-operator/prometheus-operator => github.com/prometheus-operator/prometheus-operator v0.43.0

require (
        github.com/prometheus-operator/prometheus-operator v0.0.0-00010101000000-000000000000
)

{
	"Path": "github.com/prometheus-operator/prometheus-operator",
	"Version": "v0.0.0-00010101000000-000000000000",
	"Replace": {
		"Path": "github.com/prometheus-operator/prometheus-operator",
		"Version": "v0.43.0",
		"Time": "2020-10-27T08:04:46Z",
		"Dir"<EMAIL_ADDRESS>		"GoMod"<EMAIL_ADDRESS>	},
	"Dir"<EMAIL_ADDRESS>	"GoMod"<EMAIL_ADDRESS>
The dummy version v0.0.0-00010101000000-000000000000 that's going to be replaced is the culprit and using a proper version string seems to fix the analyzer as well.


RC2 : EF6.1.3 tooling

Hi,
I'd like to use code first migrations from EF6.1.3 toolings.
But even if I have the EF package in my project, the package manager console tells me this
The EntityFramework package is not installed on project 'TreeViewBuilder.Data'.
Have the same usage of EF on other projects (WPF for instance) and it works perfectly. Is there a workaround ?

Could you file this bug in https://github.com/aspnet/EntityFramework?

In that case, http://entityframework.codeplex.com/ would be the place to post this question.


Don't block indefinitely when running non-criterion benchmarks.

Ok, I've tested this on Linux and MacOS. It's not pretty but it works.
I still can't get the integration tests working on either Linux or MacOS, though.


NBEP 2 (Extension API) Discussion

This issue is for tracking discussion of the NBEP 2 draft (from PR #1307) here:
http://numba.pydata.org/numba-doc/dev/proposals/extension-points.html

It might be helpful to develop an example outside the Numba source tree that uses the new extension along with the NBEP.  I would vote for something a little tricky, like partial support for passing Pandas DataFrames into Numba functions.
(Not with complete coverage of DataFrames, obviously, but just enough to exercise all the important parts of the NBEP.)

I just noticed that it did not mention the magic attribute _numba_type_ that is used in typeof (https://github.com/numba/numba/blob/b23166255d97b5164a217d569d1cf8622b2a522e/numba/typing/typeof.py#L49) so that value can specify their numba type.
In the JIT classes PoC, I added a fastpath to the compute_fingerprint that looks at numba_type and uses it to generate the fingerprint.

I think this can be closed now.


Auto detect missing runtime and do a fresh xcode install

When a new xcode version is added to the CI via a pull request, it is very likely that people push new commits to the PR. This will cause existing builds canceled.
If a build is running xcode installation, this cancellation will cause incomplete xcode (like missing runtime) remaining in the cache and cause test failures.
We should have an automatic way to detect missing runtime and do a cleanup and fresh xcode re-installation if detected.

this cancellation will cause incomplete xcode (like missing runtime) remaining in the cache and cause test failures.

Instead can we avoid writing to the cache until the installation succeeds?

This somehow will not solve the problem. Copying over xcode/runtime (if we install somewhere else we need to copy them to cache) is also expensive, and canceling a build when copying will also hit same issue.
I would not expect we hit this issue much. This logic might only needed when we bump an xcode version.

Some context for CIPD install.
CIPD caches installation state, which means it assumes that anything it installed is still installed. We need to handle the incomplete installations on our side (for now). One way is to delete .cipd to force a reinstall. (related bug: https://crbug.com/1176408)

Dig further, we may want an upstream fix from mac_toolchain. They have some shortcuts to skip re-install xcode, and unluckily we hit some corner cases.
Filed https://crbug.com/1435582 to track.
/cc @godofredoc

Filed https://crbug.com/1435582 to track.

From that issue it was suggested to do:
maybeInstall:
  if !exists sentinel:
    -- previous install is OK
    if version files on disk == desired version:
      return  -- current install is OK and the right version
  doInstall

doInstall:
  write sentinel
  cipd ensure ....
  delete sentinel

but IMO I would just do

maybeInstall:
  cipd ensure ...

This will already skip expensive file operations if the state on the disk matches what the ensure file requested, and is the way that cipd is intended to be used.

cc @vashworth @cyanglaz

https://flutter-review.googlesource.com/c/recipes/+/42900 landed to clean up polluted xcode. If no regression (didn't expect to happen), I will close this bug.

Thanks @keyonghan!

Reopen as this is still happening: https://github.com/flutter/flutter/issues/126092
We hit the case where: xcode exists, the default runtime path exists as well under Copy runtime to XCode.app/Contents/Developer/Platforms/iPhoneOS.platform/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS.simruntime, but xcrun simctl list doesn't show the runtime.
Likely this is due to incomplete copy of the runtime.

This affects devicelab xcode as well: https://github.com/flutter/flutter/issues/126025.
Use this bug to track xcode cache cleanup for both devicelab and host only. (as we are consolidating osx_sdk and devicelab_osx_sdk modules, it makes sense to use a shared cleanup logic)

Instead of checking xcode and runtime paths (which misses the case where both paths exist but there are still missing files that are not copied over, resulting xcrun simctl list no runtime output), we can check the output of xcrun simctl list runtimes directly. If no runtime, then we are sure the xcode is not in a complete state.

The issue should be resolved in https://flutter-review.googlesource.com/c/recipes/+/44761. Closing.
@vashworth @cyanglaz please let me know if you hit this again when bumping the next xcode version. Hopefully not:-)

Despite this update, I'm still seeing this occur on CI as-of 2023-08-15:
https://ci.chromium.org/ui/p/flutter/builders/try/Mac Engine Drone/331151/overview

I just uploaded a new Xcode version in CIPD yesterday, maybe that triggered it

Why does uploading a new version cause CI workers to fail, shouldn't those two bits be isolated?

Despite this update, I'm still seeing this occur on CI as-of 2023-08-15:
https://ci.chromium.org/ui/p/flutter/builders/try/Mac Engine Drone/331151/overview

Runtime does show up: https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8772653137004135969/+/u/list_simulators/stdout

@keyonghan That link also shows iOS 16.4 runtime as missing
Unavailable: com.apple.CoreSimulator.SimRuntime.iOS-16-4 --

The existing logic just makes sure there is some runtime installed, but doesn't enforce a check on every runtime, which misses this corner case.
https://flutter-review.googlesource.com/c/recipes/+/49482 to fix.

Thanks @keyonghan!

Recipes CL landed, and the issue should be resolved now. Please reopen you you still see the issue.


NCSDK-3401 Fix soc_flash_nrf sample.

Added harness config to sample in order for the sanitycheck tool
to run and understand whether the samples output is as expected.
Signed-off-by: Łukasz Hejnak<EMAIL_ADDRESS>

Some checks failed. Please fix and resubmit.
Gitlint issues
1: UC3 Title does not follow [subsystem]: [subject] (and should not start with literal subsys:): "NCSDK-3401 Fix soc_flash_nrf sample."
Tip: The bot edits this comment instead of posting a new one, so you can check the comment's history to see earlier messages.

DNM until https://github.com/NordicPlayground/fw-nrfconnect-zephyr/pull/255 is in

Added one more correction to also pass for nrf9160.

I would have a more descriptive commit title if possible. The NCS JIRA task is not too useful when reading git shortlog, and neither is "fix sample". I suggest moving the NCS JIRA in the commit message, and use a more descriptive commit title e.g.: samples: drivers: soc_flash_nrf: add test harness.

History in this repository has been rewritten. Please rebase this PR.

Rebased and updated commit message as suggested by @lemrey

Can I ask why this is noup? Looking at the patch, can't we merge it upstream?

@mbolivar You're right. We initially assumed that it won't be useful for anyone outside Nordic, but upon further consideration it has some valid use cases in upstream as well.
I updated the tag as you can see, I will also prepare a PR to upstream in a moment.

I updated the tag as you can see, I will also prepare a PR to upstream ~in a moment~:
zephyrproject-rtos/zephyr#21919

Thank you!


[std.regex] Fix unsafe casts to bool

These are disallowed in @safe code with https://github.com/dlang/dmd/pull/16558.

Sorry, turns out cast(bool) someInteger is actually OK - it doesn't reinterpret the lower byte. But this pull should be fine anyway.


Sign in check issue

Ok I get null reference exception when I use xboxlive.issigned. Is there any other way to check whether user is signed in?

I have used: XboxLiveUserManager.Instance.AvailableXboxLiveUsers[i].User.IsSignedIn when I have multiple users were 'i' is the one I am checking.
I imagine that if you have only one user that you can check XboxLiveUser.User.IsSignedIn from the UserProfile prefab.
Regardless, I would check if both XboxLiveUser != null and XboxLiveUser.User != null before checking the IsSignedIn member of User.  The UserProfile script seems to do so and, since I think some of the values are set in separate threads, you may not know when it has been set.  I haven't have problems when checking this way.
If you sign out the user while the game is running, at least with multiple users, I think the User member may become null.  Don't quote me on that though :).

xboxliveuser != null always returns null!

How are you trying to access it?  Is it through the UserProfile prefab/script?  What do you have in your current scene?

here is what I got on my script.
`public Class UIManager, Monbehaviour;
{
public XboxLiveUser User;
public void Check(){
if (User.IsSignedIn)
{"blah blah" }}
}`

I am doing a similar thing with my own script and not using the UserProfile.cs script.   However, I used it as a starting point to see how they did it.
Take a look at how it is done in UserProfile.cs.  There is a bunch of initialization that occurs before you can access the associated XboxLiveUser.  There is some general initialization in the Awake and Start functions.  The Update function seems to have a two-step process of initializing an XboxLiveUser, including initializing the actual XboxLiveUser variable in the UserProfile class and starting the signin process.
Maybe the easiest solution for you would be to add a UserProfile prefab to your scene. You may need to add some other prefabs, such as the XboxLiveUser prefab and the XboxLiveServices prefab to your scene. to make it work or get rid of some debug messages about adding them.
Once you add the UserProfile prefab, then your UIManager can get a reference to it.  You should then be able to access the xbox user through that.  You may still need to check if it is initialized, but it would at least provide a path to have a user sign in so that when you get to your "if (User.IsSignedIn{"blah blah" }" section, that User variable will be valid.

Hi ayubhassan,
We do recommend checking out the UserProfile.cs script for the initializations that need to happen for XboxLiveUser. Without that initialization, the User will remain null resulting in exceptions.
Do let us know how this worked out for you and if you need any more help.


NEW Adding constructor auto-DI for classes resolved through Injector

I can RFC whether this is a feature that the core team is interested in for 4.4 if wanted.
This adds auto-DI for constructors of classes resolved through Injector. This works by checking the constructor docblock for a tag @Injectable and then using typehint reflection to resolve dependecies. There's some docs in the PR.
Having dependencies expressed in the constructor is a good way to indicate a classes dependencies in a clear way - producing expressive and testable classes. I think we should be encouraging this sort of DI, and perhaps make the @Injectable tag not required in 5.0

My main concern with this would be performance impact – Injector creation can be used 10,000s of times on a single request. Have we done any profiling?

It adds time, but we're talking <1s on >1 million instantiations. Every little bit counts though - I'll add some caching per class constructor that should alleviate most concerns.

One Thousand Milliseconds is a lot of time! :-P
Can we get a bit of data on, say, one of the expensive /treeview renders that we were using for testing our CMS NFRs

How long it took before
How long it took after
How many Injector-based creates are being called
Perhaps a synthetic test to see how long that many injector-based creates would take

If we introduce caching we'd probably need to understand how many different cache entries are used in the above

@ScopeyNZ Did you have a change to have another look at this?

@ScopeyNZ Did you have a change to have another look at this?

Haha it's on my list of "before 4.4 is feature-frozen" - So I will endeavour to look over it within the next couple of weeks.

ping @dnsl48, we were talking about SilverStripe DI earlier =D

yeah, I definitely love the idea! Though, as already discussed above, needs some polishing :)

Worked on this a little on hackday - going off the suggestion from @tractorcow to have an annotation based config transformer. PRs open on config and framework for that. This has been rebased onto the framework PR (#9006).
Still need to run through docs again and do some performance testing.

@ScopeyNZ Is this something you're still keen to push across the line? Looks like PHP 8 will have native attributes, so it could be worth awaiting and exploring those?

Yeah as far as this is concerned it was pretty much good to go when I left it. There was a case for showing some proof that there's no significant effect on performance, which I haven't done. I'll run through this stuff when I get some time and put updates on it.
PHP 8 native attributes are definitely nice - and a great feature for this PR, but considering how long it took for PHP 7 to be a requirement, it would be frustrating to have something similar blocking this feature.

I haven't done a detailed review, but I'm happy to approve the approach in principal.
@brynwhyman I think this is a high value PR and that a lot of work as gone into implementing it. If the rest of the Core Committers agree this new API is worthwhile, I think it would be worth adding this the the CMS Squad board to take it over the line.

I like the idea and I think the DI system in Silverstripe could use some attention.
I'm not super sold on using annotations for this. One reason is that it's not really part of the API, rather comments. Another reason is that IDEs probably won't autocomplete class names when you're using annotations.

The annotations are there as a "switch" to enable auto-DI for constructors, as I wasn't sure that suddenly doing this for any class resolved from the container was safe. Thinking about it now though, I think Injector will just error if you don't provide a required dependency? The problem would be how we tell Injector that it's safe to inject an optional dependency.
The other purpose of the annotations is to inject objects in the container that have a specific tag. Not really sure of any other appropriate way to do this. Some frameworks (eg Laravel) don't let you do this.

Note: The documentation portion should not be merged here. I have started the process of migrating docs to a new repository so the docs will need to be removed from this PR and a new PR raised in the new repo instead.

I'm going to close this - I think if we were to ever merge something like this today it would be using attributes rather than annotations


AutoPlay not work after Touch the view around 2 second

Which OS ?
Version
Which versions are you using:
Android , ios

react-native-swiper 1.5.13
react-native v0.56.0

Expected behaviour
When user touch the view, the swiper will stop the autoPlay, after user move out the finger, the autoPlay should be start by itself again.
Actual behaviour
When i touch the view around 2 second, the swiper will stop the autoPlay, after i move out the finger, it will not autoPlay again, until i scroll to other page.
How to reproduce it>
To help us, please fork this component, modify one example in examples folder to reproduce your issue and include link here.
Steps to reproduce

It seems that if i touch the view longer than the autoPlayTimeout, the swiper will stop the autoScroll.

1，Can it be solved?

i solved like this:
android use onMomentumScrollEnd;
iOS use onResponderRelease;
if you touch longer than autoplayTimeout, onMomentumScrollEnd(iOS) will call many times, onMomentumScrollEnd(Android) will call once, they are different in iOS and Android; And onResponderRelease only works on iOS, call once;
触摸时间过长，onMomentumScrollEnd(iOS) 会调用多次，onMomentumScrollEnd(Android)调用1次
onResponderRelease(iOS)调用1次，onResponderRelease(Android)没反应
`
                onMomentumScrollEnd={(e: any, state: any, swpier: any) => {
                    if (!isAndroid) return;

                    // 延迟一秒执行，滚动动画时间内swpier.internals.isScrolling 为true，会导致autoplay方法直接return， 需要等待滚动动画结束
                    setTimeout(() => {
                        if (swpier && swpier.autoplay) {
                            swpier.autoplay()
                        }
                    }, 1000);
                }}

                 onResponderRelease={(e: any, state: any, swpier: any) => {
                    if (isAndroid) return;

                    // 延迟一秒执行，滚动动画时间内swpier.internals.isScrolling 为true，会导致autoplay方法直接return， 需要等待滚动动画结束
                    setTimeout(() => {
                        if (swpier && swpier.autoplay) {
                            swpier.autoplay()
                        }
                    }, 1000);
                }}

`


map matching 'quality' test suite

As discussed here it'd be good to have a way of testing how 'good' our map matching is by comparing it with known results. (I.e. our map-matching on a GPX track gives a certain route, and how close does that align to the actual known route taken?)
Considerations/comments (to direct a PR):

where do we get data of known routes? @stefanholder pointed out one example - do we want others? Do we want users to be able to test their own data sets?
we should see how map matching performs not only with the given GPX track, but also as we continually down-sample it.
how do we compare with the known route? Compare total distances of each? Or the proportion of the distance which they share common edges on?
how will we add this functionality? I think it is very similar to the Measurement suite (#73) in how it'll be used (and we could, I guess, put it in there if we wanted). Or we could build it into unit tests somehow (e.g. require that the match is sufficiently high.)
do we want to store historical trends in accuracy (as opposed to e.g. just comparing with the last commit) - and if so, how?

There are many taxi tracks from NYC http://www.nyc.gov/html/tlc/html/about/trip_record_data.shtml and there are many on OSM itself: http://wiki.openstreetmap.org/wiki/Planet.gpx or GPSies

The performance test suite could be also used for this. E.g. counting the errors and differences of the random routes or using different randomness etc

how do we compare with the known route? Compare total distances of each? Or the proportion of the distance which they share common edges on?

We should check to which degree the matched route goes through the same sequence of edge/nodes as the expected route. To this end we could compute the Levenshtein distance between the expected and the actual node/edge sequence.

To this end we could compute the Levenshtein distance

Newson & Krumm suggest a different metric in Chapter 5, which is simpler but probably still sufficient:
map matching error = (d_minus + d_plus) / d0

d_minus: total length of road segments that are in the ground truth route but not in the matched route
d_plus: total length of road segments that are in the matched route but not in the ground truth route
d0: length of the ground truth route

With this definition it is possible to have an error greater than 1. But I don't think that this is a real problem.
Another useful variant would be to use the number of road segments for d_minus, d_plus and d0 instead of their length.

Agreed that, assuming 'normal' behaviour, it is probably fine. If it's not 'normal' - e.g. non-sequential - then this could be a very poor metric. A Levenshtein approach may handle these cases better.
That said, we may need to write something similar to, but not, Levenshtein. For example, transpositions are allowed (with the same cost as adding/removing). This makes sense in e.g. spelling detection, but probably not in routes - edges have the additional constraint of connectivity (which words largely don't - I think). So we'd either need to not consider transitions, or treat them differently. Similar applies for changing edges. So, it's possibly that our Levenshtein could end up only really considering additions/subtractions (in the 'normal' case) which is equivalent to the @karussell's suggestion.
As an aside - if we do go with Levenshtein, we should weight be edge length, not just counts.
Another thought - what about the area between the curves? We'd probably have time as a dimension (so area includes differences in time), so that even being at the point isn't necessarily good (unless you're also there at the same time). (Actually, the latter is something we'd need to consider in the above approaches too.) In terms of calculating the area, we can probably come up with a suitable proxy similar to numerical integration - e.g. if both route and ground truth had 100 nodes, we'd just sum up the difference (including time) of each node pair.


Remove libc dependencies

Replace libc crate with std::ffi
Remove realloc and memcpy workaround https://github.com/ros2-rust/ros2_rust/issues/215#issuecomment-1279723455

@Tacha-S this is looking great, thanks! Let us know when it's ready for review

I was developing with 1.64.
But unfortunately 1.63(CI version) requires core::ffi instead of std::ffi.
https://doc.rust-lang.org/src/std/ffi/mod.rs.html#157
Which version should be support?

I don't fully understand – the compiler error sounds like 1.63 has core::ffi, but the release notes and core::ffi docs look like that module was introduced with 1.64? Maybe these types were available but experimental in 1.63.
Either way, I think it would be nice to support 1.63 if it's not too ugly. Maybe that requires using std::os::raw after all.

core::ffi was unstable before 1.64.0.


Spacing between  elements

I have a bunch of rectangles in which reside numbered lists as text. The issue I'm having is that elements are way too close to each other, and there seems to be no feasible way to specify a certain spacing between them.
It would be good in the properties tab on the left to have a field for this.
Or, at the very least, document a way of achieving it. In HTLM <li> elements can be spaced out by setting something like this in CSS:
li {
  margin: 10px 0;
}

Currently, the only way to do something similar is to:

Change the line height property, BUT if the element is on multiple lines than the effect is ugly to say the least
Add a blank line at the end of the text with Shift+Enter

You can add CSS to the <li> elements by clicking the HTML button while editing. The CSS of the first element will be used in new elements:


bug: 4.6.0 missing scss files

Bug Report
Ionic version:

[x] 4.6.0
Current behavior:
In this build, all scss files (from themes dir, component dir or any other var file) are missing.
Expected behavior:
They should be present in @ionic/core/dist.
Steps to reproduce:
Just install latest version, @ionic/core is missing those files.
Ionic info:
4.6.0

Hi there,
Thanks for the issue! Can you provide a repository with the code required to reproduce this issue? Also, can you provide the output of running ionic info from your project's directory?
Thanks!

remove node_modules then install again

Same issue here.

Please provide more details for us to look into this. What framework are you using? How are you building the app? Where are you seeing the errors?
There are some details missing from ionic info on this page. Please run it in a terminal, you should get something like the following if inside of an Angular app:
Ionic:
   Ionic CLI                     : 5.1.1
   Ionic Framework               : @ionic/angular 4.6.0
   @angular-devkit/build-angular : 0.13.9
   @angular-devkit/schematics    : 7.3.9
   @angular/cli                  : 7.3.9
   @ionic/angular-toolkit        : 1.5.1

Thank you!

@brandyscarney @liamdebeasi Just npm install<EMAIL_ADDRESS>- you will see, that in dependent package @ionic/core, there are are no scss files - AT ALL. No themes directory in dist/collection and in every single component directory (dist/collection/components/*) there are only css files, no scss files.
Have a look what is downloaded from npm - extract and you will not find any scss file:
<EMAIL_ADDRESS>Missing scss files breaks build of the apps, that were including e.g. vars scss files (like themes or component vars).
It seems that during the build process of ionic/core package, scss files were excluded.
Build of @ionic/core#4.5.0 was fine, all scss were present.

Thanks @MarkChrisLevy! I was mistakenly reading this as css. The scss files were never meant to be or documented as a part of our public API. We've never recommended importing Sass variables or mixins from Ionic as of Ionic 4 because we may change them at any time and since they are not documented it would be a breaking change in your application and up to you to look for the change in latest. We recommend including any mixins or variables you use in your application directly. We can add this back for now, but it will be something that is removed for the next major version. Please work on migrating to use CSS variables for theming and including any mixins that you need in your app. If we're misunderstanding the use case for always including scss files please let us know. Thank you!

I can confirm, same issue here. White screen on upgrade to 4.6.0. The DOM is there, the application is running without errors, but nothing shows up. I don't believe I've included any non-standard scss files directly.
I used the ionic to generate command to start a new app, and these were included by that:
@import<EMAIL_ADDRESS>@import<EMAIL_ADDRESS>@import<EMAIL_ADDRESS>@import<EMAIL_ADDRESS>
@import<EMAIL_ADDRESS>@import<EMAIL_ADDRESS>@import<EMAIL_ADDRESS>@import<EMAIL_ADDRESS>@import<EMAIL_ADDRESS>

@brandyscarney I'm confused. Is the above set of includes what you're saying is problematic? Can you elaborate on the changes that will be required to migrate from CSS to CSS variables for theming, specifically? How are we supposed to include the ionic styles if we don't include the CSS files? E.g. how do we move forward and get things working again?

Ah, I think I misread CSS/SCSS as well, still though, I'm confused as to what's wrong?

@brandyscarney In my case I use scss in building custom components, that are more or less based on ionic components (e.g. my own select component or date picker). I'm not saying it is a must to use scss files, but I wasn't aware that is not part of public API (scss files were public in previous versions, so maybe that is way I'm using them).

@lincolnthree There should not be any issues with including the css files that way. That is our recommended project setup. You may be running into a different issue if you're not directly importing any scss files. I tried creating a new app using the following commands:
$ ionic -v
5.1.1

$ ionic start myApp

> tabs

$ cd myApp
$ ionic serve

I am not seeing any issues with the CSS in Chrome or Safari. Could you try removing node_modules completely and doing a fresh install? Or are you seeing it in a different browser/device?
rm -rf ./node_modules
npm i

If you're still seeing issues after this can you open a new issue please. 🙂

@MarkChrisLevy We likely didn't do a great job explaining the move away from Sass as a public API with all of the changes in Ionic 4. When we moved to Ionic 4 with web components it allowed us to remove the requirement of rebuilding all of Ionic's Sass every time a change was made by a developer in their app. This meant that the Sass variables were no longer available by default in an app but it also improved build times. We chose to use CSS variables to replace the Sass variables for theming because they allow runtime changes and can work with Shadow DOM. There are many places where we're actually not even using the defined Sass variables anymore in Ionic which could cause issues if you're importing them and wanting them to match our design. Since Sass became an internal tool of Ionic we decided it wouldn't be a public facing API because our internals around design change rapidly and with the move to follow SemVer it would be hard to not introduce breaking changes related to Sass changes.
We'll add the Sass files back for a hotfix 4.6.1 release (planning on tomorrow if all goes well) but it is planned to be removed for Ionic 5. Do you foresee any issues with relying on the CSS variables? We've had this issue open for awhile that I think would be helpful for reusing some of Ionic's variables: https://github.com/ionic-team/ionic/issues/15229. We're open to feedback if you think there is a definite need for keeping the files at the risk of breaking changes.

@brandyscarney White page seems to be due to the root <html> element never receiving the "hydrated" class. No errors. I will open a new issue when I find the cause (if it's a bug.)

@brandyscarney I really appreciate that you will restore scss files - it will give me the time to switch to css variables or not to use ionic variables at all. I always support your (ionic's) decisions to move forward, even if it means a bit of additional work. Once again - thanks!

Linking the issue by @lincolnthree for the white screen: https://github.com/ionic-team/ionic/issues/18649
It seems to be related to having multiple copies of Stencil installed. We are looking into it.

@brandyscarney Oops! Thanks, I thought I put a link in there! Too many edits :)

Where you importing the SCSS exactly from? which path? can yo provide a code example?

@manucorporat As I wrote, I build my own components and I'm using *.vars.scss, e.g. components/select/select.vars.scss

It is fixed in 4.6.1. Thanks @brandyscarney!


Missing test coverage from pull request #1511?

As part of pull request #1511, the changes may have fixed a bug related to native type rendering for iterator; it could be worth adding test coverage related to that.
Before #1511, the code was calling itertools.islice(values, 2) to retrieve the head elements from a values collection (potentially of an iterator type) and then using itertools.chain(head, values) to subsequently produce output.
In the case where values is an iterator, I think that works correctly.  But in cases where values is not an iterator, it can result in output duplication (something that I think #1511 indirectly resolves with this check).
For example:
>>> from itertools import islice
>>> values = [1,2,3,4]
>>> head = islice(values, 2)
>>> from itertools import chain
>>> list(chain(head, values))
[1, 2, 1, 2, 3, 4]

(note: opened this as a separate issue thread since the existing thread(s) have been locked)

Happy to consider a PR that fixes this or adds tests.

Work-in-progress at https://github.com/openculinary/jinja/tree/issue-1806/pr-1511-additional-test-coverage:

[x] Test coverage to demonstrate that a problem could have occurred during async rendering of templates containing native types
[ ] Enable async support for pytest and tox

Does the test coverage offered in #1807 seem reasonable for this?  (that's one of my pull requests, and I'm trying to close/refresh a few that have been open for a while)

Seems fine, just haven't had time to get to merges here.


Issue 955: use readline to get commit messages

Fixed #955

Looks great! 👍

Can you update the CHANGELOG as well?


Use JsSourceParser as default parser for AstAnalyser class

The parser argument in the constructor of AstAnalyser class is currently required:
https://github.com/NodeSecure/js-x-ray/blob/master/src/AstAnalyser.js#L18
For me we should make it optional and assign new JsSourceParser() by default.

Hi, I would like to work on it! Could you please assign it to me?

Go for it Madina, I think the issue is quite simple.


ERC721 transaction

added a contract code, which was taken from https://solidity-by-example.org/app/erc721/

This PR duplicating https://github.com/ledgerwatch/automated-testing/pull/12 which has more updates.


FGT integration

From #21

We would like to make the Product Status availability from FGT? (check 4) actually a real on-line check.  Is it possible to integrate this now or soon from the FGT environment?

Although current ePI and FGT environments are lead by distinct teams, and have no common products and batches, it should be possible to write a small demo.
Proposal: On the detailed information of a particular scan event, ( URL https://acdc-dev.pharmaledger.pdmfc.com/backoffice/event/ae06686e-d142-4212-9328-f8b7a6df2c48 ) , add an extra option that calls an traceability request on one of FGT MAH's REST services API.

Bump version to v0.9.0 on all acdc-components/ modules, specially to illustrate a need for DB upgrade.

Architecture and sequence diagram for internal review.

Deploy to acdc-dev complete.


There are two license types listed.

[Enter feedback here]
In the following URL, the license type for Google Workspace is listed as "Google Workspace Business or Enterprise preferred" and "
Google Workspace Enterprise (minimally)".
I think this is an error, so could you please correct it?

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

ID: a1f41e1e-2541-8773-efc2-eeb83a403a15
Version Independent ID: 2f2d0316-9e75-44d6-0ab6-a56b1352a1e2
Content: Connect Google Workspace to Cloud App Security
Content Source: CloudAppSecurityDocs/connect-google-workspace-to-microsoft-cloud-app-security.md
Service: cloud-app-security
GitHub Login: @dcurwin
Microsoft Alias: dacurwin

Thank you for your comment. We'll investigate and get back to you.

@Katakahashi0  - Thanks for your feedback. The page has been updated.


Feature request - Remote AD Group for AKS Admin Groups

Is there an existing issue for this?

[X] I have searched the existing issues

Community Note

Please vote on this issue by adding a :thumbsup: reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description
Need support for adding an AD Group in a remote landing zone as an administrator on an AKS Cluster. Currently, only a group in the same landing zone can be used:
https://github.com/aztfmod/terraform-azurerm-caf/blob/6054c167fb977e7aa6267c5eccc171f531a81563/aks_clusters.tf#L20-L25
New or Affected Resource(s
azurerm_kubernetes_cluster
Potential Configuration file
...
admin_groups = {
  lz_key             = "remote_lz"
  azuread_group_keys = ["non_prod_aks_admins"]
}
...

References
No response

@arnaudlh
Bug fix: https://github.com/aztfmod/terraform-azurerm-caf/pull/1318/commits/5026d51504f88181fc2c3dfdaf29b1c1fa5319c1


MF-272: Record Patient Relatives

issue: https://issues.openmrs.org/browse/MF-272
Issues to look at:

The css file for autosuggest is added but currently not working probably needs to be added to the styles guide.
The patient summary chart not able to fetch the relationships( will be checking it out to figure it out)
Otherwise the relationships are being saved as expected to the back end as seen via a rest call
@mks-d @dkayiwa @nickjhill14

Thanks for the PR @reagan-meant, I'll begin reviewing it asap

This talk post explains why the patient chart is not rendering the patient relationships yet


log checks do not work on darwin

I noticed while using nixpkgs-review-checks that hammerings log features do not work on darwin:
$ nix-build -A wrangler
/nix/store/y87ga2kkrdb8xq9fpc6zbmk25h4k8bp4-wrangler-1.13.0
$ nixpkgs-hammer wrangler
When evaluating attribute ‘wrangler’:
warning: EvalError
Cannot evaluate attribute ‘wrangler’ in ‘/nix/store/06qbd3qw844pq525489ki17xnyb1jlpf-nixpkgs’.
notice: no-build-output
‘wrangler’ has not yet been built. Checks that rely on the presence of build logs are skipped.
$ nix log /nix/store/y87ga2kkrdb8xq9fpc6zbmk25h4k8bp4-wrangler-1.13.0
...

I am not sure what I am doing wrong here. If this is not a bug we should add a few words to get it working.

Yeah, that looks off, for sure. Especially the 'EvalError'. Do you have any examples where it doesn't show the EvalError and the log checks still fail by chance?

The issue is that it does not evaluate. Could you check if running with --do-not-catch-errors from https://github.com/jtojnar/nixpkgs-hammering/pull/88 gives any useful info?

This happens for wranger and git.
command nix run -f https://github.com/jtojnar/nixpkgs-hammering/archive/61a2da5490edceda98626e40f656f5b5c36c4cd9.tar.gz -c nixpkgs-hammer --do-not-catch-errors wrangler
error: --- ThrownError ----------------------------------------------------------------------------------------------------------------------------------------------------- nix-instantiatePackage ‘qt-4.8.7’ in /Users/user/nixpkgs/pkgs/development/libraries/qt-4.x/4.8/default.nix:233 is not supported on ‘x86_64-darwin’, refusing to evaluate.

a) To temporarily allow packages that are unsupported for this system, you can use an environment variable
   for a single invocation of the nix tools.

     $ export NIXPKGS_ALLOW_UNSUPPORTED_SYSTEM=1

b) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

c) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

(use '--show-trace' to show detailed location information)
Traceback (most recent call last):
  File "/nix/store/2yy82yl5wkzm7kxqlir5lk58dx6kvd4a-nixpkgs-hammer/bin/.nixpkgs-hammer-wrapped", line 407, in <module>
    main(args)
  File "/nix/store/2yy82yl5wkzm7kxqlir5lk58dx6kvd4a-nixpkgs-hammer/bin/.nixpkgs-hammer-wrapped", line 328, in main
    overlay_data = nix_eval_json(all_messages_nix, args.show_trace)
  File "/nix/store/2yy82yl5wkzm7kxqlir5lk58dx6kvd4a-nixpkgs-hammer/bin/.nixpkgs-hammer-wrapped", line 136, in nix_eval_json
    json_text = subprocess.check_output(args, text=True, input=expr)
  File "/nix/store/xf3244kbn36z04yw98mpgvvsgdcbz438-python3-3.8.8/lib/python3.8/subprocess.py", line 415, in check_output
    return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
  File "/nix/store/xf3244kbn36z04yw98mpgvvsgdcbz438-python3-3.8.8/lib/python3.8/subprocess.py", line 516, in run
    raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['nix-instantiate', '--strict', '--json', '--eval', '-']' returned non-zero exit status 1.

Maybe from https://github.com/jtojnar/nixpkgs-hammering/blob/b59787fea072a9a09c5bc22b9fec0ac1272d81f0/overlays/build-tools-in-build-inputs.nix#L72

Yeah. And also automoc4, breakpointHook, gogUnpackHook and sudo according to nix-instantiate --argstr system x86_64-darwin -A "antlr"  … --show-trace.
Perhaps we should use allowUnsupportedSystem = true. Or just filter these like we do for darwin.cctools Linux?

Or just filter these like we do for darwin.cctools Linux?

That wouldn't be future proof.
Also found another issue on linux:
$ command nix run -f https://github.com/jtojnar/nixpkgs-hammering/archive/61a2da5490edceda98626e40f656f5b5c36c4cd9.tar.gz -c nixpkgs-hammer --do-not-catch-errors git
error: --- ThrownError ----------------------------------------------------------------------------------------------------------------------------------------------------- nix-instantiateurllib3-1.26.3 not supported for interpreter python2.7
(use '--show-trace' to show detailed location information)
Traceback (most recent call last):
  File "/nix/store/pj7qk83bqgy33b8fxx077rn9h6jdrmp7-nixpkgs-hammer/bin/.nixpkgs-hammer-wrapped", line 407, in <module>
    main(args)
  File "/nix/store/pj7qk83bqgy33b8fxx077rn9h6jdrmp7-nixpkgs-hammer/bin/.nixpkgs-hammer-wrapped", line 328, in main
    overlay_data = nix_eval_json(all_messages_nix, args.show_trace)
  File "/nix/store/pj7qk83bqgy33b8fxx077rn9h6jdrmp7-nixpkgs-hammer/bin/.nixpkgs-hammer-wrapped", line 136, in nix_eval_json
    json_text = subprocess.check_output(args, text=True, input=expr)
  File "/nix/store/yl69v76azrz4daiqksrhb8nnmdiqdjg9-python3-3.8.8/lib/python3.8/subprocess.py", line 415, in check_output
    return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
  File "/nix/store/yl69v76azrz4daiqksrhb8nnmdiqdjg9-python3-3.8.8/lib/python3.8/subprocess.py", line 516, in run
    raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['nix-instantiate', '--strict', '--json', '--eval', '-']' returned non-zero exit status 1.


SQL MI Connection

while using User name Password connective via service account getting error DFM_ALTERNATIVE_CONNECTION_STRING-user-id not provided. please expline the environment field name DFM_ALTERNATIVE_CONNECTION_STRING usage while connecting to SQL MI for the Monitoring.
### Tasks

Hello @saranb92 ,
As documented:

, to monitor Task Hubs managed by Durable Task SQL Provider you need to use DfMon for Durable Task SQL Provider. See detailed instructions there on how to configure it.
DFM_ALTERNATIVE_CONNECTION_STRING_XXX settings are only intended and only supported for the default, Azure Storage-based durability provider. Don't use them with MSSQL storage.
An alternative (and the easiest) way of monitoring all supported durability providers (Azure Storage, MSSQL and Netherite) is to use DfMon-as-a-VsCode-Extension.


Merge origin/develop

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

v1.2.1
GitHub release

Your semantic-release bot :package::rocket:


Implement Statistics and Estimation category

Migrate all flags, notes, and links over from the v6 PDF and the POC Markdown repo into the Stats and Est page.

Work complete, closing issue.


Share the same host device from the host through several containers

Let's say we have a container A relying on the device /dev/loop0 from the host. This device will be hotplugged into the VM and used by the agent.
Now, we need a container B to run on the same pod to access the same device. The way it works today, we will duplicate the hotplugging of the same device and it will appear as a different one inside the agent. This also means that a modification on the device from the container A is not reported to the device seen by container B.
The way to properly handle this would be to hold a list of the host devices already passed through the VM and what is their address on the host. This would prevent virtcontainers code from hotplugging a new device, but instead, the agent would know which device needs to be mounted into the container B.
This would be the clean way to share a device between several containers inside the same pod (VM).

@WeiZhang555 I think you fixed this, right?


Turn _SSL_SRV_RESPECT_CLIENT_PREFERENCE config opt to a runtime opt

Signed-off-by: TRodziewicz<EMAIL_ADDRESS>Description
The configuration option MBEDTLS_SSL_SRV_RESPECT_CLIENT_PREFERENCE allows during TLS handshake to select the ciphersuite according to the client's preferences rather than the server's preferences. Change it into runtime option available as an API function.
Fixes #4398
Status
IN DEVELOPMENT
Requires Backporting
NO
Migrations
NO
Todos

[x] Tests
[x] Documentation
[x] Changelog updated

When @hanno-arm accepts suggestions from @gilles-peskine-arm then the changes are already commited. If not, a new cycle is required.


tf.train.MonitoredTrainingSession get error when data is large

Please go to Stack Overflow for help and support:
https://stackoverflow.com/questions/tagged/tensorflow
If you open a GitHub issue, here is our policy:

It must be a bug, a feature request, or a significant problem with documentation (for small docs fixes please send a PR instead).
The form below must be filled out.
It shouldn't be a TensorBoard issue. Those go here.

Here's why we have that policy: TensorFlow developers respond to issues. We want to focus on work that benefits the whole community, e.g., fixing bugs and adding features. Support only helps individuals. GitHub also notifies thousands of people when issues are filed. We want them to see you communicating an interesting problem, rather than being redirected to Stack Overflow.

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): no
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Mac 10.13.5
TensorFlow installed from (source or binary): pip install --upgrade tensorflow
TensorFlow version (use command below): 1.8.0
Python version:  2.7.10
Bazel version (if compiling from source):
GCC/Compiler version (if compiling from source):
CUDA/cuDNN version:
GPU model and memory:
Exact command to reproduce:
with tf.train.MonitoredTrainingSession(master=server.target, is_chief=(FLAGS.task_index == 0),
hooks=[saver_hooks],
config=tf.ConfigProto(gpu_options=gpu_options, allow_soft_placement=True,
log_device_placement=True)) as sess:

You can collect some of this information using our environment capture script:
https://github.com/tensorflow/tensorflow/tree/master/tools/tf_env_collect.sh
You can obtain the TensorFlow version with
python -c "import tensorflow as tf; print(tf.GIT_VERSION, tf.VERSION)"
Describe the problem
Describe the problem clearly here. Be sure to convey here why it's a bug in TensorFlow or a feature request.
It is a distributed model, there are 1 ps and 10 worker.
When train with low-dimensional model, everything is fine.
But if trained with high-dimensional model, the error occur and traceback shows it happen in tf.train.MonitoredTrainingSession.
Source code / logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached. Try to provide a reproducible test case that is the bare minimum necessary to generate the problem.
18/07/10 18:44:02 INFO XLearningContainer: weights/truncated_normal/mean: (Const): /job:worker/replica:0/task:2/device:CPU:0
18/07/10 18:44:02 INFO XLearningContainer: weights/truncated_normal/shape: (Const): /job:worker/replica:0/task:2/device:CPU:0
18/07/10 18:44:02 INFO XLearningContainer: weights/random_uniform/max: (Const): /job:worker/replica:0/task:2/device:CPU:0
18/07/10 18:44:02 INFO XLearningContainer: weights/random_uniform/min: (Const): /job:worker/replica:0/task:2/device:CPU:0
18/07/10 18:44:02 INFO XLearningContainer: weights/random_uniform/shape: (Const): /job:worker/replica:0/task:2/device:CPU:0
18/07/10 18:44:02 INFO XLearningContainer: input/Placeholder_1: (Placeholder): /job:worker/replica:0/task:2/device:CPU:0
18/07/10 18:44:02 INFO XLearningContainer: input/Placeholder: (Placeholder): /job:worker/replica:0/task:2/device:CPU:0
18/07/10 18:44:02 INFO XLearningContainer: train/Adagrad/value: (Const): /job:ps/replica:0/task:0/device:CPU:0
18/07/10 18:44:02 INFO XLearningContainer: global_step/Initializer/zeros: (Const): /job:ps/replica:0/task:0/device:CPU:0
18/07/10 18:44:02 INFO XLearningContainer: Traceback (most recent call last):
18/07/10 18:44:02 INFO XLearningContainer:   File "location_embedding_tf.py", line 203, in
18/07/10 18:44:02 INFO XLearningContainer:     tf.app.run(main=main)
18/07/10 18:44:02 INFO XLearningContainer:   File "/usr/lib/python2.7/site-packages/tensorflow/python/platform/app.py", line 126, in run
18/07/10 18:44:02 INFO XLearningContainer:     _sys.exit(main(argv))
18/07/10 18:44:02 INFO XLearningContainer:   File "location_embedding_tf.py", line 90, in main
18/07/10 18:44:02 INFO XLearningContainer:     log_device_placement=True)) as sess:
18/07/10 18:44:02 INFO XLearningContainer:   File "/usr/lib/python2.7/site-packages/tensorflow/python/training/monitored_session.py", line 370, in MonitoredTrainingSession
18/07/10 18:44:02 INFO XLearningContainer:     stop_grace_period_secs=stop_grace_period_secs)
18/07/10 18:44:02 INFO XLearningContainer:   File "/usr/lib/python2.7/site-packages/tensorflow/python/training/monitored_session.py", line 816, in init
18/07/10 18:44:02 INFO XLearningContainer:     stop_grace_period_secs=stop_grace_period_secs)
18/07/10 18:44:02 INFO XLearningContainer:   File "/usr/lib/python2.7/site-packages/tensorflow/python/training/monitored_session.py", line 539, in init
18/07/10 18:44:02 INFO XLearningContainer:     self._sess = _RecoverableSession(self._coordinated_creator)
18/07/10 18:44:02 INFO XLearningContainer:   File "/usr/lib/python2.7/site-packages/tensorflow/python/training/monitored_session.py", line 1002, in init
18/07/10 18:44:02 INFO XLearningContainer:     _WrappedSession.init(self, self._create_session())
18/07/10 18:44:02 INFO XLearningContainer:   File "/usr/lib/python2.7/site-packages/tensorflow/python/training/monitored_session.py", line 1007, in _create_session
18/07/10 18:44:02 INFO XLearningContainer:     return self._sess_creator.create_session()
18/07/10 18:44:02 INFO XLearningContainer:   File "/usr/lib/python2.7/site-packages/tensorflow/python/training/monitored_session.py", line 696, in create_session
18/07/10 18:44:02 INFO XLearningContainer:     self.tf_sess = self._session_creator.create_session()
18/07/10 18:44:02 INFO XLearningContainer:   File "/usr/lib/python2.7/site-packages/tensorflow/python/training/monitored_session.py", line 509, in create_session
18/07/10 18:44:02 INFO XLearningContainer:     max_wait_secs=self._max_wait_secs
18/07/10 18:44:02 INFO XLearningContainer:   File "/usr/lib/python2.7/site-packages/tensorflow/python/training/session_manager.py", line 421, in wait_for_session
18/07/10 18:44:02 INFO XLearningContainer:     "Session was not ready after waiting %d secs." % (max_wait_secs,))
18/07/10 18:44:02 INFO XLearningContainer: tensorflow.python.framework.errors_impl.DeadlineExceededError: Session was not ready after waiting 7200 secs.
18/07/10 18:44:03 ERROR XLearningContainer: XLearningContainer run failed!

Nagging Assignee @angersson: It has been 15 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

This question is better asked on StackOverflow since it is not a bug or feature request. There is also a larger community that reads questions there.
If you think we've misinterpreted a bug, please comment again with a clear explanation, as well as all of the information requested in the issue template. Thanks!

I meet the same requestion, did you resole it ?


[Request - Product] Envoy Proxy

Full and short name of product
Envoy Proxy.
Does this product have LTS versions? What are the intervals between each LTS version?
No.
What is the website for the product and for its version information?
https://github.com/envoyproxy/envoy/releases
https://github.com/envoyproxy/envoy/blob/main/RELEASES.md#major-release-schedule
Additional context
Add any other context or screenshots about the product which you want us to add endoflife.date

Hi @slonka, thanks for the suggestion. The page has been added by @captn3m0 and is now available at https://endoflife.date/envoy.

Thanks @marcwrobel 🎉


Allow the registration of new axes/metadata IDs (such as Strain)

Improvement Description
A plugin should be able to register a new identifier for the ID column of metadata. For example, NextStrain uses "Strain" consistently, there's no particular reason we couldn't recognize that if a plugin had a way to describe new axes.
Proposed Behavior
There should be an API such as:
plugin.register_new_axis("Strain")

Questions

Are there additional arguments to this? What else would be useful if we were to generalize axes?

Some additional notes from our discussion about this back in May 2020:

q2-types would probably become the new home for the sample and feature axis labels (after ripping those hardcoded values out of the framework)
the registration should include some mechanism for indicating aliases of a particular axis type (sample-id vs #SampleID vs ...)
the framework will need to query the plugin manager to learn what kinds of axes exist in a deployment
do we need to think about exposing the axis type in action signatures? as in, should Metadata[Features] or something like that exist? if so, how can the view function interact with that, if necessary?

It may be pleasant to support a is_unique argument. In the strain example, it is plausible to have a scenario like:
Strain condition_A condition_B
foo 5 10
foo 6 100
...

...where the strain identifier may not be unique. This can also occur if "time" were registered as an axis:
Time subject event
01-01-2020 A given-treatment
01-01-2020 B given-placebo
...

Separate, would it be useful to attempt to describe axis relationships? Samples contain features, for example.

An is_unique constraint would add an entirely new level of expressive power to this. That sounds pretty excellent to me. Although... Doesn't the lack of uniqueness imply an ID exists and so could be re-oriented in terms of IDs? Or are there definitely situations where it looks like an un-pivoted/unmelted table?

A row-ID could be established if needed, and may be necessary for internal relationships, but it may be nice to not require the user resolve that. In the time example, I don't think an ID naturally exists without a user or system assigning one. In SQL (or at least postgres), it is possible to create a table without a primary key:
ag_test=# create table foo (bar integer);
CREATE TABLE
ag_test=# \d foo
      Table "public.foo"
 Column |  Type   | Modifiers
--------+---------+-----------
 bar    | integer |

ag_test=# insert into foo values (1);
INSERT 0 1
ag_test=# insert into foo values (1);
INSERT 0 1
ag_test=# insert into foo values (1);
INSERT 0 1
ag_test=# insert into foo values (1);
INSERT 0 1
ag_test=# select * from foo;
 bar
-----
   1
   1
   1
   1
(4 rows)


chore(expectedConditions): change the class name to appear on the website

after investigation, ExpectedConditions_ as a class name does not appear on the website
added an @alias so Expected_Conditions shows up as ExpectedConditions

Somehow this PR is not updating... Closing and creating a new one.


Data Table Enhancement: Compound Expansion

This closes issue #721.
The example of a data table with compound expansion has been added to the list of examples. Inside of an expandable row, a <td> can expand holding another table.

Deploy preview for pf-next ready!
Built with commit 75a44334533c0d56fc42048a8a3f922e06f22489
https://deploy-preview-970--pf-next.netlify.com


fix: Owner being replaced in github actions

PR Checklist

[X] Addresses an existing open issue: fixes #1043
[X] That issue was marked as status: accepting prs
[X] Steps in CONTRIBUTING.md were taken

Overview
This PR should fix #1043 by using a callback function to determine if the string matched by the regex for replacement contains any of the elements in the new excludedFromReplacements array. If there's a match we don't want to replace it so we return the original match, else we return the options.owner property.
This also updates the updateLocalFiles.test.ts accordingly.
There's probably a more elegant way to do this but here's my newbie version. 🤓

Yikes.. I'll need help understanding why it fails on the initialization script test.

I agree. I don't like this solution either.
I tried coming up with a solution using the callback which should work but I couldn't figure out the correct regex to use.
I know my problem was that I change the regex to match /JoshuaKGoldberg/g only so the function was always false.
This , along with a new excludedFromReplacements variable, was my original attempt. A clever regex should make this work right?
[
/JoshuaKGoldberg/g,(match: string) =>
excludedFromReplacements.some((e) =>
match.includes(e))
? Match
: options.owner,
]

Sorry. I get and F on this one. I've tried but got nowhere. Feel free to close this PR

You got it - thanks for trying though! I really appreciate you putting the effort in. ❤


No backend selected with static libraries

On 18.05, the static .a libraries are not equivalent to the .so libraries.
If I compile my own graph application using shared libraries with something like:
MYLDFLAGS = -Lbuild -lpthread -larm_compute_graph -larm_compute -larm_compute_core
I can execute my own application.
If I compile my own graph application using static libraries with something like:
MYLDFLAGS = -Lbuild -lpthread -larm_compute_graph-static -larm_compute-static -larm_compute_core-static
I can execute my own application but I get an immediate error: No backend exists!
from src/graph/Utils.cpp line 53.
Is this a bug or should I do something different when statically linking my graph application to indicate the backend (aka. Neon in my case)? Why would that be different when statically or dynamically linking?

Hi @gregoiregentil
Could you please share the command that you used to build the library in both cases?

I haven't compiled twice ComputeLibrary, only once with this command:
scons arch=arm64-v8a Werror=0 debug=0 asserts=0 neon=1 opencl=0 build=native -j2
If I run my app with the dynamic libraries, it works. If I run my app statistically, I have the problem.
This is also true if I download and use the binaries.

Hello @gregoiregentil,
Graph backend uses compile time self-registration, thus I assume that when linking statically these are stripped. Can you try  -Wl,--whole-archive -larm_compute_graph-static -Wl,--no-whole-archive when linking statically the graph library?

@gregoiregentil did the above solved you problem?