Exporting scan result, vulnerable, overview in PDF, Excel, CSV file

Problem: I want to show devs vulnerability in their image but don't want to give them access to the dashboard nor screen shot ( Screen shot when having more then 100 vul is tedious) and also printing hard copy
Suggestion: An export file to pdf, csv, html to show report

Hi @GKMAN781, thanks a lot for the great suggestion. Will it be helpful to add an export button to each screen (Applications, Resources, Packages, Vulnerabilities) that will export all the presented entries (with entries from all pages in pagination)?
Is there specific information required from the drill down to be included which is not in table's columns?
Is there a specific format that is more preferable than the other's (e.g. csv)?
Thanks!

I am suggesting having a button for creating a form, which should have an overview part, next is a custom table where user can choose which content they want to export, like application with high vul or package that must be update, etc.
For information which need to be drill down not in table columns is some graph for general information and suggestion
Specific format if most preferable is Excel or PDF. PDF should be easier to integrate but Excel is more widely use when you need a copy or filter down vul.
That should be all but i am also give you guys a general graph about some ui brief about the export form

This will be a great feature

Agree, we love using the tool but have issues sharing results since there is no export. Even a simple CSV with the vulnerabilities found would be a useful start

Is there a way to reopen this?

reopen please - this feature is needed


Sprite: Fix picking when angle is not zero

See https://forum.babylonjs.com/t/should-sprite-picking-work-with-rotation-angle/40768

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

Snapshot stored with reference name:
refs/pull/13860/merge
Test environment:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/13860/merge/index.html
To test a playground add it to the URL, for example:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/13860/merge/index.html#WGZLGJ#4600
Links to test babylon tools with this snapshot:
https://playground.babylonjs.com/?snapshot=refs/pull/13860/merge
https://sandbox.babylonjs.com/?snapshot=refs/pull/13860/merge
https://gui.babylonjs.com/?snapshot=refs/pull/13860/merge
https://nme.babylonjs.com/?snapshot=refs/pull/13860/merge
To test the snapshot in the playground with a playground ID add it after the snapshot query string:
https://playground.babylonjs.com/?snapshot=refs/pull/13860/merge#BCU1XR#0

Visualization tests for webgl1 have failed. If some tests failed because the snapshots do not match, the report can be found at
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/13860/merge/testResults/webgl1/index.html
If tests were successful afterwards, this report might not be available anymore.

Visualization tests for webgl2 have failed. If some tests failed because the snapshots do not match, the report can be found at
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/13860/merge/testResults/webgl2/index.html
If tests were successful afterwards, this report might not be available anymore.

I trust you on the Maths, just validating the code :-)

:)
The ray was already rotated, so we didn't need to rotate it again in _checkTextureAlpha.
However, the ray was rotated with the wrong angle, so we need to take -angle to transform the ray into the correct coordinate system (this is the same as transforming a ray with the inverse world transformation when we want to test a ray-mesh intersection in the local coordinate system of the mesh).


TrustedMaterial method naming

Description

Before a major release, I'd like to change the names of the interface methods so that each is not called an Authority. Overuse of Authority is going to lead to confusion since transparency logs are never referred to as authorities in any literature. I'd like to make the following changes:

TSACertificateAuthorities() -> TimestampingAuthorities() (or TimestampAuthorities(), but the former is the RFC3161 name)
TlogAuthorities() -> RekorLogs() (Specifying Rekor because this refers only to the Rekor personality and wouldn't work with some generic representation of a log)
CTlogAuthorities -> CTLogs()
The TlogAuthority struct -> TransparencyLog

A last change I am debating is changing FulcioCertificateAuthorities to CodesigningCertificateAuthorities. I don't think it's the right thing to do, but wanted to note my thoughts. By using Fulcio, we're stating a requirement for a specific certificate profile. "Codesigning" would allow BYO PKI scenarios. However, there are many assumptions made in the codebase around the structure of the certificate - short lived certificates, certain extensions, identities, etc. I think the better approach is to keep FulcioCertificateAuthorities and later add a separate type for a generic code-signing CA which relaxes many of the constraints. We were thinking something along these lines for Cosign, having a dedicated CLI namespace for BYO PKI.

To me, the import path trusted_root and struct TrustedRoot should be sufficient, defining that these are trusted entities. Also calling them logs should denote a service rather than an untrusted entity like an entry. Is there an example you're thinking of where there might be confusion between the two?

To me, the import path trusted_root and struct TrustedRoot should be sufficient, defining that these are trusted entities.

Fair enough!
My only remaining hesitation is that in the bundle protobuf we call it tlogs instead of RekorLogs, but RekorLogs is definitely less confusing that tlogs and ctlogs.


(autohotkey.install) Packages version 2.0.15, 2.0.16 and 2.0.17 are  failing verification

Checklist

[X] I have verified that this is the correct repository, and the package is maintained by the chocolatey-community user.
[X] I have verified that this is happening in the latest available version of the package.

Chocolatey Version
2.3.0
Chocolatey License
None
Package Version
2.0.15 to 2.0.17
Current Behaviour
Packages are failing Package Verifier.
Installing 2.0.17 it onto a VM showed this box.

Expected Behaviour
Packages pass Package Verifier.
Steps To Reproduce
choco install autohotkey.install --version 2.0.17.
Environment
- Operating System: Windows 10
- PowerShell Version: 5.1
- Shell: Windows PowerShell

Chocolatey Log
See the [gist for 2.0.17](https://gist.github.com/choco-bot/8b6298984b1b376f7d69b9e7ef2c6616).

Anything else?
No response

Duplicate of #2472

I did search the repository for autohotkey before raising the issue and didn't get a result.  Apologies.


Update clang format 18

It's OK to re-apply the format, but it should be done in a standalone PR.

I'm trying to figure out the options to make the least changes in a reformat.

@mtaillefumier could you please check if this is consistent with clang-format of llvm 17?

I wil ldo that right away


[BUG][2.0] When handling multiple databases, tables can be created to different database

Reproduction steps:

Create "a" database
Create "b" database
Select second tab ("b" database's interface)
Trying to create "1" table in database "b", the table will be created in database "a" instead of "b"

Expecting results:
When creating a table in a database's interface, the table must be created in that database

This should be fixed with commit 52a5804fa79b82f6bef08380d5348d1797653a7f.


MSID: 98449 Version: 2 DOI: 10.1101/2<IP_ADDRESS>5747

MSID: 98449
Version: 2
Preprint DOI: https://doi.org/10.1101/2<IP_ADDRESS>5747
Step 1. Awaiting reviews
Editorial to post reviews via hypothesis
Useful links:

DocMap: https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v2/by-publisher/elife/get-by-manuscript-id?manuscript_id=98449
New model tracking: https://docs.google.com/spreadsheets/d/1_fHaoOy7hjyocptKtVJRijeNpUY4hBS7Ck_aVmx6ZJk/
Reviews on sciety: https://sciety.org/articles/activity/10.1101/2<IP_ADDRESS>5747

For trouble shooting (e.g. no Docmaps available):

DocMap issue addressing: https://miro.com/app/board/uXjVNCwK6EI=/
Explore DataHub DocMaps API: https://lookerstudio.google.com/reporting/4c2f0368-babb-4beb-b5b3-497e7e7b0f08/page/ejphD
Unmatched submissions and preprints: https://lookerstudio.google.com/u/0/reporting/9f86204f-3bf7-477c-9b18-5c5ef141bf69/page/p_gxi57ha93c
Unmatched manuscripts spreadsheet: https://docs.google.com/spreadsheets/d/15QcK8w-ssB7109RQEDtFpJPZ0J5HTGxoHa_2TtpMBbg/edit#gid=1336081641

Step 2. Preview reviewed preprint
Production QC content ahead of publication
Instructions:

QC preview: https://prod--epp.elifesciences.org/previews/98449v2
Update ticket with any problems (add blocked label)
When QC OK, add QC OK label to ticket and add publication date and time to https://docs.google.com/spreadsheets/d/1amAlKvdLcaDp5W8Z8g77NmkwbMF5n_u89ArSqPMO8jg
Move card to next column
(At end of the day post link in #enhanced-preprint and ask for PDF to be generated)

Useful links:

Preprint DOI :  https://doi.org/10.1101/2<IP_ADDRESS>5747
Confirm reviews returned by EPP: https://prod--epp.elifesciences.org/api/reviewed-preprints/98449/v2/reviews
To update the MECA path in the docmap: https://docs.google.com/spreadsheets/d/1mctCQuNFBjSn97Lihy7_vBO6z7-N-oqyLv4clyi6zHg

Step 3: Awaiting search reindex
This step adds the reviewed preprint to the homepage: https://elifesciences.org
The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.
Useful links:

Jenkins pipeline to reindex search can be triggered sooner or monitored here: https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 4: Published! PDF requested
Waiting for PDF to be generated
Useful links:

PDF tracking: https://docs.google.com/spreadsheets/d/106_XeDjmuBae7gexOTNzg60lapeqjl2aRn9DzupGyS8/

Step 5: Introduce PDF to data folder and git repo
Upload PDF to relevent folder in git repo https://github.com/elifesciences/enhanced-preprints-data/
Step 6: Done!

[ ] Kettle is on!


Minimum permissions to run indexoptimize

I have your database maintenance script installed in azure's sql db's solution. It seems the only role that works is db_owner. I've tried assigning db_datawriter/db_datareader, and GRANT execute on the security context via role (db_executor), however, one of these security roles allows for running the stored procedure.

Thanks in advance!!

The minimum permissions are:
EXECUTE on dbo.IndexOptimize
VIEW DEFINITION on dbo.CommandExecute
VIEW DEFINITION on dbo.CommandLog
VIEW SERVER STATE
db_owner on all target databases


Issue with data-sizes="auto"?

I'm at a loss to understand why this is happening... thought I would turn to the community here and see if anyone has an idea.
You can see a video of the issue here as the page is reloaded – I'd obviously like to see the text not jump up and down, seeming completely unaware of the height it will eventually come to occupy.
https://dl.dropboxusercontent.com/u/542183/strange_gap.mp4
You can see the sample code here.
https://gist.github.com/kerns/b6d94013b77940afe7c2

Can you provide a fiddle. This way it is easier to debug.


Upvote Election: Dashboard

As a DAO User
I would like to be able to have UpVote Election Dashboard
So that I can manage to whole process in the one place.
Design
Upvote Election Dashboard should be new screen/route
the screens should change automatically based on the timer

[ ] add sing-up voting screen

[ ] add round/rounds voting screen

[ ] add chief delegate round screen

[ ] add head delegate round screen

[ ] add voting result screen

@arsenijesavic for this we should create new badges? Voter and Delegate right?

@evgenibir Yes they will be available on backend here:
https://github.com/hypha-dao/dho-web-client/issues/1947
https://github.com/hypha-dao/dho-web-client/issues/1948
do you need any additional specs ?

No, thanks


Compatibility with browserify

In a browserify package, this will refer to a node-style exports object, not
window. So just reference window directly.

Is this fix in a particular release? still seeing the issue in 0.7.5


[4.0.0-preview]GetItemQueryStreamIterator returns only the first response value

Describe the bug
GetItemQueryStreamIterator returns only the first response value.
If I use await foreach or while...MoveNextAsync(), iteration will only occur once, while the result surely should return more than one entry.
If I use await ...ToListAsync() from System.Linq.Async, the result yields list with correct length(matching the number of items it should return), but with the first item given the right value whilst others with null.
To Reproduce
var container = client.GetDatabase(dbName).GetContainer(containerName);
var testResponse = await container.GetItemQueryStreamIterator(new QueryDefinition("select * from c")).ToListAsync();

Or
        var testResponseEnumerator = container.GetItemQueryStreamIterator(new QueryDefinition("select * from c")).GetAsyncEnumerator();

	while (await testResponseEnumerator.MoveNextAsync() == true)
	{
		var temp = testResponseEnumerator.Current;

		if (temp?.ContentStream != null)
		{
			var b = new StreamReader(temp.ContentStream).ReadToEnd();
		}
	}

Or
        var testResponse = container.GetItemQueryStreamIterator(new QueryDefinition("select * from c"));
	await foreach (var response in testResponse)
	{
		if (response?.ContentStream != null)
		{
			var b = new StreamReader(response.ContentStream).ReadToEnd();
		}
	}

Expected behavior
The snippet should iterate through the entries in the database.
Actual behavior
Iteration only occurs once.
As for ToListAsync, I have this:

Environment summary
SDK Version: 4.0.0-preview
.NET SDK Version: .NET Core 3.1
OS Version (e.g. Windows, Linux, MacOSX): Win10-x64

Dumb me, all items are returned in one response


Cudnn params_to_canonical failed

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Linux Ubuntu 16.04
TensorFlow installed from (source or binary): source
TensorFlow version (use command below): 1.3.0-rc2
Python version: 3.5.2
Bazel version (if compiling from source): 0.52
CUDA/cuDNN version: 8.0/6.0.21
GPU model and memory:  Tesla K80/11.17GiB
Exact command to reproduce:

sess = tf.Session(config=tf.ConfigProto(allow_soft_placement=True))

# Works
cell = cudnn_rnn_ops.CudnnGRU(1, 5, 5, input_mode="linear_input")
sess.run(cell.params_to_canonical(tf.zeros([cell.params_size()])))

# aborts with "Check failed"
cell = cudnn_rnn_ops.CudnnGRU(1, 5, 5, input_mode="skip_input")
sess.run(cell.params_to_canonical(tf.zeros([cell.params_size()])))

Describe the problem
If input_mode is "skip_input", params_to_canonical fails with a "Check failed" error for at least CudnnGRU
Logs
2017-08-15 03:05:45.807704: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:893] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2017-08-15 03:05:45.808201: I tensorflow/core/common_runtime/gpu/gpu_device.cc:955] Found device 0 with properties:
name: Tesla K80
major: 3 minor: 7 memoryClockRate (GHz) 0.8235
pciBusID 0000:00:1e.0
Total memory: 11.17GiB
Free memory: 11.11GiB
2017-08-15 03:05:45.808229: I tensorflow/core/common_runtime/gpu/gpu_device.cc:976] DMA: 0
2017-08-15 03:05:45.808241: I tensorflow/core/common_runtime/gpu/gpu_device.cc:986] 0:   Y
2017-08-15 03:05:45.808261: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1045] Creating TensorFlow device (/gpu:0) -> (device: 0, name: Tesla K80, pci bus id: 0000:00:1e.0)
2017-08-15 03:05:46.543863: F tensorflow/contrib/cudnn_rnn/kernels/cudnn_rnn_ops.cc:627] Check failed: size == width * height Params size mismatch. Expected 25, got 0
Aborted (core dumped)

It has been 14 days with no activity and this issue has an assignee.Please update the label and/or status accordingly.

Is this still an issue for you?

For me, the error still occurs on tensorflow 1.4. Personally, I am not using the skip_input mode so this bug is not an issue.

skip_input is not compatible with regular TF RNN layers and we plan to not expose it in later revisions.
Btw, you'd try tf 1.5 or later, it has CuDNN RNN layers which manages vars for you. (but this is orthogonal to ur question.)


Firebase Analytics

Hello tell me how you can use Firebase Analytics with this SDK
SPM

I don't know what do you say?
it is fully compatible with firebase. Thank you!

Hello tell me how you can use Firebase Analytics with this SDK
SPM

I don't know what do you say?
it is fully compatible with firebase. Thank you!


GCM initialisation vector length

mbed TLS does not check if the initialisation vector length is zero (which is an invalid value).
Found by roberto, and reported on the mbed TLS forum.

ARM Internal Ref: IOTSSL-1118

Merged PR's, #727, #790, and #793. Issue is resolved and can be closed.


set_bg doesn't appear to be working when compiling to Wasm

ctx.set_bg doesn't appear to do anything when I compile a game to wasm and run it in the browser. For an example see the wasm app from this chapter of the tutorial: https://bfnightly.bracketproductions.com/rustbook/wasm/chapter-10-ranged/
Rltk: 0.7.0
Rust: 1.42.0
OS: OSX 10.15.1
Browser: Firefox 74.0, Chrome 80.0.3987.149

I'll double-check, but I believe that has been fixed in the current master of RLTK/bracket-lib. I have a few more things to stabilize before it becomes the crate release (including I need to update initialization in the tutorial versions).

Here we go: the walking example has been updated to use set_bg to leave a trail. Works in WASM now: http://bfnightly.bracketproductions.com/wasmtest/walking/
Thanks! Glad this is one I'd already found. :-)

Great! do you recommend switching to use master as a dependency for the time being? are there any breaking changes?

I'll be updating the tutorial very soon (hopefully today). There is one breaking change, the initialization setup now uses Rust's Result system for error handling.


Reduce the load on API server for bulk requests

This commit enables Cerberus to handle bulk requests in chunks
instead of a single go as it can generate a very large response
when there are thousands of objects running in the cluster and
overload the server by consuming a large amount of resources.
The chunk size is set to 250 by default to break the large request
while still preserving the consistency of the total request and
improve responsiveness.

/rerun all

/rerun all

/rerun all

Results for cerberus_jjb

Test
Result
Duration (HH:MM:SS)

test_daemon_disabled
Pass
00:00:24

test_detailed_data_inspection
Pass
00:00:44

test_slack_integration
Pass
00:00:57

The change itself looks good.   Trying to do some additional testing today to measure the impact.

Use of chunk-size does not measurably impact get pods -o json for a namespace with 5K pods.   But, there is no reason not to add the tune-able in case there are future scenarios where it helps.
@chaitanyaenr There is a build failure, but I can't see the details.  Recommend taking a look at that prior to merge.

@mffiedler Thanks for testing it. Think the build failure is a stale one from before when we were experimenting with the functional tests.


Improve TypeScript support

Is there any plan to add in this plugin features like:

syntax highlighting
code duplications

as described in https://docs.sonarqube.org/display/DEV/Supporting+New+Languages?

I'd like to support both, but certainly the first would require me to write and maintain a TypeScript parser to do the highlighting which is an order of magnitude more overhead than I'm willing to take on.
Duplications I think you can do without a parser though, or at least have a decent bash at.

@Pablissimo maybe you could use some libraries from typescript itself? Microsoft tries to make reusable instruments, like ie. language-server.
Java can run javascript through nashorn.
Duplications typically need a lexer output. It's not hard to write own (~50 LOC or so + separeted small channel for string literals), but i hope something can be found at MS side

Worth looking at for sure - having access to the language service stuff underpinning the actual TS compiler would also allow better parsing of LCOV coverage data, avoiding flagging non-executable lines as covered or not which relates to another issue around here somewhere...

For duplication, the project below use JSCPD: https://github.com/kucherenko/jscpd
https://github.com/groupe-sii/sonar-web-frontend-reporters
https://github.com/groupe-sii/sonar-web-frontend-plugin
Worth a look. A collaboration would be nice as they don't support Sonar 6.
But it is fully featured so we are using it with Sonar 4.5 and get all reports including test coverage for Typescript.

@Pablissimo just want to point you to https://github.com/SonarSource/SonarTS-Plugin/commits/master
~it's alive!~ some commits included

Thanks! Sorry, been away from non-work development for a bit. Indeed - I need to have a chat with them and see what their roadmap is.


[move-compiler] revised hlir lowering

Description
This revises how HLIR lowering proceeds to be more like typical context normalization. In doing so, it elides a fair bit of code that was being previously generation around effects in value position.
Test Plan
The tests mostly all work, and a few have been updated with additional errors.

If your changes are not user-facing and not a breaking change, you can skip the following section. Otherwise, please indicate what changed, and then add to the Release Notes section as highlighted during the release process.
Type of Change (Check all that apply)

[ ] protocol change
[x] user-visible impact
[ ] breaking change for a client SDKs
[ ] breaking change for FNs (FN binary must upgrade)
[ ] breaking change for validators or node operators (must upgrade binaries)
[ ] breaking change for on-chain data layout
[ ] necessitate either a data wipe or data migration

Some new errors will be generated.
Release notes

user-visible impact

If we check this box we will need to fill out the release notes section. Not needed for this PR, but just flagging for when the branch comes into main :)

Unused return did not make it into this PR. It is actually quite explicitly avoided. I will add it in a small follow-on.


CAN'T CREATE A DOCKER CONTAINER

PLEASE DO NOT INCLUDE ANY PASSWORDS OR TOKENS IN YOUR ISSUE!!!
Describe the issue
I have been able to create containers before, but now i get the same error when i try to create a container.
Scripts used to create container and cause the issue
PS C:\Users\bab> cd "C:\Users\bab\Documents\AL\EQM365\PowerShell_Scripts"                                                                   PS C:\Users\bab\Documents\AL\EQM365\PowerShell_Scripts> .\CreateBcContainer.ps1
Latest BcContainerHelper is installed.
BcContainerHelper version 6.0.0
BC.HelperFunctions emits usage statistics telemetry to Microsoft

Choose a localization ( W1, NO, DK or US ): NO

Enter Container Name: UCOARM21

Full output of scripts
Downloading EQM license to C:\Users\bab\Documents\AL\EQM365\PowerShell_Scripts\eqm_365_license.flf
EQM license downloaded.

BcContainerHelper is version 6.0.0
BcContainerHelper is running as administrator
HyperV is Enabled
UsePsSession is True
Host is Microsoft Windows 11 Pro - 10.0.22631.2506
Docker Client Version is 24.0.6
Docker Server Version is 24.0.6
Removing Desktop shortcuts
Fetching all docker images
Fetching all docker volumes
Using image mcr.microsoft.com/businesscentral:10.0.20348.2031
Creating Container UCOARM21
Style: onprem
Multitenant: No
Version: 21.6.54874.0
Platform: 21.0.54828.0
Generic Tag: <IP_ADDRESS>
Container OS Version: 10.0.20348.2031 (ltsc2022)
Host OS Version: 10.0.22631.2506 (Unknown/Insider build)
Using process isolation
Using locale nb-NO
Disabling the standard eventlog dump to container log every 2 seconds (use -dumpEventLog to enable)
Using license file C:\Users\bab\Documents\AL\EQM365\PowerShell_Scripts\eqm_365_license.flf
Files in C:\ProgramData\BcContainerHelper\Extensions\UCOARM21\my:
- AdditionalOutput.ps1
- license.flf
- MainLoop.ps1
- SetupVariables.ps1
- updatehosts.ps1
Creating container UCOARM21 from image mcr.microsoft.com/businesscentral:10.0.20348.2031
New-BCContainer Telemetry Correlation Id: 2a72e496-329f-4b42-b264-10d612d2e3d9
docker: Error response from daemon: hcsshim::ExpandScratchSize failed in Win32: The semaphore timeout period has expired. (0x79).
See 'docker run --help'.
ExitCode: 125
Commandline: docker run --volume "c:\bcartifacts.cache:c:\dl" --label nav= --env isBcSandbox=N --label version=21.6.54874.0 --label platform=21.0.54828.0 --label country=no --env artifactUrl=https://bcartifacts.azureedge.net/onprem/21.6.54874.0/no --env licenseFile="c:\run\my\license.flf" --name UCOARM21 --hostname UCOARM21 --env auth=NavUserPassword --env username="admin" --env ExitOnError=N --env locale=nb-NO --env databaseServer="" --env databaseInstance="" --volume "C:\ProgramData\BcContainerHelper:C:\ProgramData\BcContainerHelper" --volume "C:\ProgramData\BcContainerHelper\Extensions\UCOARM21\my:C:\Run\my" --isolation process --restart unless-stopped --env filesOnly=False --env enableApiServices=Y --env useSSL=N --volume "c:\windows\system32\drivers\etc:C:\driversetc" --env securePassword=76492d1116743f0423413b16050a5345MgB8AFEAeAA2AHMAZwB0AGwAQwBlAGgAYgBTAEkANwBRAG0ARAA1AHIASQAwAGcAPQA9AHwAMAA3ADIAOQBiAGEAZgBiADEAZgBiADAAZQA0ADMAMwAwADQAMQAwAGUANwA3AGUANgAwADMAYwA4ADkAOABjAA== --env passwordKeyFile="c:\run\my\aes.key" --env removePasswordKeyFile=Y --env accept_eula=Y --env accept_outdated=Y --detach mcr.microsoft.com/businesscentral:10.0.20348.2031

Screenshots

I haven't seen this before, but I would say that it looks like a problem on your computer.
If you have enought memory and disk space available, you could try the cleanup process described here: https://freddysblog.com/2018/12/11/clean-up-after-yourself-docker-your-mom-isnt-here/ or a re-install of docker and/or OS.


BUG - i18n Translations Failing to Load and incorrectly adding scripts to package.json, resulting in test failures

Description
i18n Translations not loading correctly and adding translated scripts to package.json.
Solution would be to ensure that i18n translations are fully loaded and initialised before any dependent functionality is executed.
Expected results
i18n translations should load correctly and be available readily.
Actual Behavior:
i18n translations intermittently fail to load, causing localisation to break as a result start scripts are included in package json as below
"start": "echo \\\"info.mockOnlyWarning\\\"",

Fixed with https://github.com/SAP/open-ux-tools/pull/2050


The example "Ten and a half million" does not work

Yet to go over the code but that specific example does not yield a result

yep. Noticed this as well. But I've not made it to numbers yet.
However I noticed the fact that this bug is not because of 'rules':
There are several returns in the function preventing the function to run until the last word.

Found the bug:

The rules containing 'half' and 'quarter' are handled just once and just for the beginning of the string (^)
The word 'and' is just silent (continue;) - but the rules would have to run again [until next 'and' or end].

Bugfix:
"Split" the module.exports into two functions:
The first would split the string by 'and's and run the second (parsing) function.
Push each split-result in an array and when all words are done, sum up the array.

thanks!

just a note:
according to my very old copy of the AP stylebook we should also accept "one-half" like in
"Five and one-half percent"
and this leads me to a next question:
I'd find it superuseful if it could also detect the units - maybe set by options (?)
nlp.value('Five and one-half percent').number({units: true})

-->
{value: 5.5, units: '%'}

hey, yes absolutely. that feature would be lovely and requires a bit of work.
i'd prefer nlp.value('text', {options}) i think

Ah - funny most numerals rules of the expensive AP stylebook are here for, well "free" :
http://www.grammarbook.com/numbers/numbers.asp

You can see the fix above.
Be aware of the dependencies to the numbers(data) module and the cache module.

all tests (plus the new 2) do pass, but
this was written by the opposite of a mathematician - so it NEEDS REVIEW.

nice. checked it out and seems sensible

might be closed (?)

i thought you were making a new branch and pull request for this?

@spencermountain ok. sorry for delay. malaria stroke back last days (<40°C) but >40°C sun. Yep. I'll do soon. Referenced it already above.
btw: Completely rewrote the date parser (then I'll push). It should parse multiples, ranges, multiple ranges, slang and much more now. It has less lines (for now) but I'm thinking about dates a while longer.

cool, cool.
On Sat, 11 Jul 2015 at 10:47 redaktor<EMAIL_ADDRESS>wrote:

@spencermountain https://github.com/spencermountain ok. sorry for
delay. malaria stroke back last days (<40°C) but >40°C sun. Yep. I'll do
soon. Referenced it already above.
btw: Completely rewrote the date parser (then I'll push). It should parse
multiples, ranges, multiple ranges, slang and much more now. It has less
lines (for now) but I'm thinking about dates a while longer.
—
Reply to this email directly or view it on GitHub
https://github.com/spencermountain/nlp_compromise/issues/54#issuecomment-120626778
.

and just btw: Just corrected something in the referenced commit above:
The checkWords loop had a return in the end. This should be removed.
It would parse within any sentence and should not be stopped.
Basically both to_number and to_date could then also become a .pos 'sugar' method.
In general I am thinking if it wouldn't be useful to somehow combine the pos and its 'sugar' methods.
Basically I'd like to know from these sugar methods which tokens are this (or from .pos what is this token) - but maybe it would be enough to simply include an index array with the sugar,
like { result: 'Tony Danza', tokens: [0,1] }
Not sure what's best option.

yeah, i know what you mean. That or a circular reference to the token itself.
but don't change the api right now. Let's keep these bugfixes light.
I can look at this issue if you think you'll be more than a few days

but don't change the api right now

Hm, thats hard :
All "value" methods should return arrays as well (like the other methods). Look at the existing code:
If it finds any date it won't parse any numbers and stops and if it finds a 'first' number it stops.
And they don't interact. Think of "Fourth of July".
The array thing is the only breaking change.
E. g. .date would parse all dates in a sentence. I tested with an AirBerlin mail because they are really good in concatting multiple dates to a readable monster sentence ;)
I did not write more tests yet. I should do. The empty arrays are really invalid like Feb. 29 in a non-leap. It is doing relative dates as well and much more.
It looks now like
 [ { text: '1993',
      day: false,
      month: false,
      year: 1993,
      weekDay: false,
      Date: Wed Dec 01 1993 01:00:00 GMT+0100 (CET),
      to: false,
      localized: 'Wednesday, December 1, 1993' } ],
  [ { text: '4. 6. 2015',
      day: 4,
      month: 6,
      year: 2015,
      weekDay: 4,
      Date: Thu Jun 04 2015 02:00:00 GMT+0200 (CEST),
      to: false,
      localized: 'Thursday, June 4, 2015' } ],
  [ { text: '6/4/2015',
      day: 4,
      month: 6,
      year: 2015,
      weekDay: 4,
      Date: Thu Jun 04 2015 02:00:00 GMT+0200 (CEST),
      to: false,
      localized: 'Thursday, June 4, 2015' } ],
  [ { text: 'March 7th',
      day: 7,
      month: 3,
      year: 1987,
      weekDay: 6,
      Date: Sat Mar 07 1987 01:00:00 GMT+0100 (CET),
      to:
       { text: '11th 1987',
         day: 11,
         month: 3,
         year: 1987,
         weekDay: 3,
         Date: Wed Mar 11 1987 01:00:00 GMT+0100 (CET) },
      localized: 'Saturday, March 7, 1987' } ],
  [ { text: 'June 1st',
      day: 1,
      month: 6,
      year: 1999,
      weekDay: 2,
      Date: Tue Jun 01 1999 02:00:00 GMT+0200 (CEST),
      to:
       { text: '11th 1999',
         day: 11,
         month: 6,
         year: 1999,
         weekDay: 5,
         Date: Fri Jun 11 1999 02:00:00 GMT+0200 (CEST) },
      localized: 'Tuesday, June 1, 1999' } ],
  [ { text: '28th of September',
      day: 28,
      month: 9,
      year: 2008,
      weekDay: 0,
      Date: Sun Sep 28 2008 02:00:00 GMT+0200 (CEST),
      to:
       { text: '5th of October 2008',
         day: 5,
         month: 10,
         year: 2008,
         weekDay: 0,
         Date: Sun Oct 05 2008 02:00:00 GMT+0200 (CEST) },
      localized: 'Sunday, September 28, 2008' } ],
  [ { text: '2nd of January',
      day: 2,
      month: 1,
      year: 2008,
      weekDay: 3,
      Date: Wed Jan 02 2008 01:00:00 GMT+0100 (CET),
      to:
       { text: '5th of October 2008',
         day: 5,
         month: 10,
         year: 2008,
         weekDay: 0,
         Date: Sun Oct 05 2008 02:00:00 GMT+0200 (CEST) },
      localized: 'Wednesday, January 2, 2008' } ],
  [ { text: 'March 7th',
      day: 7,
      month: 3,
      year: 1987,
      weekDay: 6,
      Date: Sat Mar 07 1987 01:00:00 GMT+0100 (CET),
      to:
       { text: 'june 11th 1987',
         day: 11,
         month: 6,
         year: 1987,
         weekDay: 4,
         Date: Thu Jun 11 1987 02:00:00 GMT+0200 (CEST) },
      localized: 'Saturday, March 7, 1987' } ],
  [ { text: 'April 17th',
      day: 17,
      month: 4,
      year: 1981,
      weekDay: 5,
      Date: Fri Apr 17 1981 02:00:00 GMT+0200 (CEST),
      to:
       { text: 'september 11th 1981',
         day: 11,
         month: 9,
         year: 1981,
         weekDay: 5,
         Date: Fri Sep 11 1981 02:00:00 GMT+0200 (CEST) },
      localized: 'Friday, April 17, 1981' } ],
  [ { text: 'June 1st',
      day: 1,
      month: 6,
      year: 2016,
      weekDay: 3,
      Date: Wed Jun 01 2016 02:00:00 GMT+0200 (CEST),
      to:
       { text: 'June 11th 2016',
         day: 11,
         month: 6,
         year: 2016,
         weekDay: 6,
         Date: Sat Jun 11 2016 02:00:00 GMT+0200 (CEST) },
      localized: 'Wednesday, June 1, 2016' } ],
  [ { text: '13 February',
      day: 13,
      month: 2,
      year: 1945,
      weekDay: 2,
      Date: Tue Feb 13 1945 01:00:00 GMT+0100 (CET),
      to:
       { text: '15 February 1945',
         day: 15,
         month: 2,
         year: 1945,
         weekDay: 4,
         Date: Thu Feb 15 1945 01:00:00 GMT+0100 (CET) },
      localized: 'Tuesday, February 13, 1945' } ],
  [ { text: 'March 7th',
      day: 7,
      month: 3,
      year: 1987,
      weekDay: 6,
      Date: Sat Mar 07 1987 01:00:00 GMT+0100 (CET),
      to:
       { text: 'june 11th 1987',
         day: 11,
         month: 6,
         year: 1987,
         weekDay: 4,
         Date: Thu Jun 11 1987 02:00:00 GMT+0200 (CEST) },
      localized: 'Saturday, March 7, 1987' } ],
  [ { text: 'March 1st 1987',
      day: 1,
      month: 3,
      year: 1987,
      weekDay: 0,
      Date: Sun Mar 01 1987 01:00:00 GMT+0100 (CET),
      to: false,
      localized: 'Sunday, March 1, 1987' } ],
  [ { text: 'June 22nd 2016',
      day: 22,
      month: 6,
      year: 2016,
      weekDay: 3,
      Date: Wed Jun 22 2016 02:00:00 GMT+0200 (CEST),
      to: false,
      localized: 'Wednesday, June 22, 2016' } ],
  [ { text: 'June 22nd 1997',
      day: 22,
      month: 6,
      year: 1997,
      weekDay: 0,
      Date: Sun Jun 22 1997 02:00:00 GMT+0200 (CEST),
      to: false,
      localized: 'Sunday, June 22, 1997' } ],
  [ { text: '3rd of March 1969',
      day: 3,
      month: 3,
      year: 1969,
      weekDay: 1,
      Date: Mon Mar 03 1969 01:00:00 GMT+0100 (CET),
      to: false,
      localized: 'Monday, March 3, 1969' } ],
  [ { text: '2nd of April 1929',
      day: 2,
      month: 4,
      year: 1929,
      weekDay: 2,
      Date: Tue Apr 02 1929 02:00:00 GMT+0200 (CEST),
      to: false,
      localized: 'Tuesday, April 2, 1929' } ],
  [ { text: 'March 18th',
      day: 18,
      month: 3,
      year: false,
      weekDay: 3,
      Date: Wed Mar 18 2015 01:00:00 GMT+0100 (CET),
      to: false,
      localized: 'Wednesday, March 18, 2015' } ],
  [ { text: 'August 28th',
      day: 28,
      month: 8,
      year: false,
      weekDay: 5,
      Date: Fri Aug 28 2015 02:00:00 GMT+0200 (CEST),
      to: false,
      localized: 'Friday, August 28, 2015' } ],
  [ { text: '18th of March',
      day: 18,
      month: 3,
      year: false,
      weekDay: 3,
      Date: Wed Mar 18 2015 01:00:00 GMT+0100 (CET),
      to: false,
      localized: 'Wednesday, March 18, 2015' } ],
  [ { text: '27th of March',
      day: 27,
      month: 3,
      year: false,
      weekDay: 5,
      Date: Fri Mar 27 2015 01:00:00 GMT+0100 (CET),
      to: false,
      localized: 'Friday, March 27, 2015' } ],
  [ { text: '3rd',
      day: 3,
      month: 3,
      year: 1969,
      weekDay: 1,
      Date: Mon Mar 03 1969 01:00:00 GMT+0100 (CET),
      to:
       { text: '5th of March 1969',
         day: 5,
         month: 3,
         year: 1969,
         weekDay: 3,
         Date: Wed Mar 05 1969 01:00:00 GMT+0100 (CET) },
      localized: 'Monday, March 3, 1969' } ],
  [ { text: '2012',
      day: false,
      month: false,
      year: 2012,
      weekDay: false,
      Date: Sat Dec 01 2012 01:00:00 GMT+0100 (CET),
      to:
       { text: '2016',
         day: false,
         month: false,
         year: 2016,
         weekDay: false,
         Date: Thu Dec 01 2016 01:00:00 GMT+0100 (CET) },
      localized: 'Saturday, December 1, 2012' } ],
  [ { text: '1997',
      day: false,
      month: false,
      year: 1997,
      weekDay: false,
      Date: Mon Dec 01 1997 01:00:00 GMT+0100 (CET),
      to:
       { text: '1998',
         day: false,
         month: false,
         year: 1998,
         weekDay: false,
         Date: Tue Dec 01 1998 01:00:00 GMT+0100 (CET) },
      localized: 'Monday, December 1, 1997' } ],
  [ { text: '1998',
      day: false,
      month: false,
      year: 1998,
      weekDay: false,
      Date: Tue Dec 01 1998 01:00:00 GMT+0100 (CET),
      to: false,
      localized: 'Tuesday, December 1, 1998' } ],
  [ { text: '1672',
      day: false,
      month: false,
      year: 1672,
      weekDay: false,
      Date: Thu Dec 01 1672 01:00:00 GMT+0100 (CET),
      to: false,
      localized: 'Thursday, December 1, 1672' } ],
  [ { text: '2015',
      day: false,
      month: false,
      year: 2015,
      weekDay: false,
      Date: Tue Dec 01 2015 01:00:00 GMT+0100 (CET),
      to: false,
      localized: 'Tuesday, December 1, 2015' } ],
  [ { text: '1969',
      day: false,
      month: 3,
      year: 1969,
      weekDay: false,
      Date: Sat Mar 01 1969 01:00:00 GMT+0100 (CET),
      to: false,
      localized: 'Saturday, March 1, 1969' },
    { text: 'March',
      day: false,
      month: 3,
      year: false,
      weekDay: false,
      Date: Sun Mar 01 2015 01:00:00 GMT+0100 (CET),
      to: false,
      localized: 'Sunday, March 1, 2015' } ],
  [ { text: '1921',
      day: false,
      month: 1,
      year: 1921,
      weekDay: false,
      Date: Sat Jan 01 1921 01:00:00 GMT+0100 (CET),
      to: false,
      localized: 'Saturday, January 1, 1921' },
    { text: 'jan',
      day: false,
      month: 1,
      year: false,
      weekDay: false,
      Date: Thu Jan 01 2015 01:00:00 GMT+0100 (CET),
      to: false,
      localized: 'Thursday, January 1, 2015' } ],
  [ { text: '13 February',
      day: 13,
      month: 2,
      year: 1945,
      weekDay: 2,
      Date: Tue Feb 13 1945 01:00:00 GMT+0100 (CET),
      to:
       { text: '15 February 1945',
         day: 15,
         month: 2,
         year: 1945,
         weekDay: 4,
         Date: Thu Feb 15 1945 01:00:00 GMT+0100 (CET) },
      localized: 'Tuesday, February 13, 1945' } ],
  [ { text: 'january 5th',
      day: 5,
      month: 1,
      year: 2015,
      weekDay: 1,
      Date: Mon Jan 05 2015 01:00:00 GMT+0100 (CET),
      to: false,
      localized: 'Monday, January 5, 2015' },
    { text: '6th 2015',
      day: 6,
      month: 1,
      year: 2015,
      weekDay: 2,
      Date: Tue Jan 06 2015 01:00:00 GMT+0100 (CET),
      to: false,
      localized: 'Tuesday, January 6, 2015' } ],
  [ { text: '12/20/2015',
      day: 20,
      month: 12,
      year: 2015,
      weekDay: 0,
      Date: Sun Dec 20 2015 01:00:00 GMT+0100 (CET),
      to: false,
      localized: 'Sunday, December 20, 2015' },
    { text: '12 / 21 / 2015',
      day: 21,
      month: 12,
      year: 2015,
      weekDay: 1,
      Date: Mon Dec 21 2015 01:00:00 GMT+0100 (CET),
      to: false,
      localized: 'Monday, December 21, 2015' },
    { text: '12/23/2015',
      day: 23,
      month: 12,
      year: 2015,
      weekDay: 3,
      Date: Wed Dec 23 2015 01:00:00 GMT+0100 (CET),
      to: false,
      localized: 'Wednesday, December 23, 2015' } ],
  [ { text: 'february 10th',
      day: 10,
      month: 2,
      year: false,
      weekDay: 2,
      Date: Tue Feb 10 2015 01:00:00 GMT+0100 (CET),
      to: false,
      localized: 'Tuesday, February 10, 2015' } ],
  [],
  [ { text: '1999-01-01',
      day: 1,
      month: 1,
      year: 1999,
      weekDay: 5,
      Date: Fri Jan 01 1999 01:00:00 GMT+0100 (CET),
      to: false,
      localized: 'Friday, January 1, 1999' } ],
  [ { text: '01-01-1999',
      day: 1,
      month: 1,
      year: 1999,
      weekDay: 5,
      Date: Fri Jan 01 1999 01:00:00 GMT+0100 (CET),
      to: false,
      localized: 'Friday, January 1, 1999' } ],
  [],
  [ { text: 'within next 3 days',
      day: 19,
      month: 7,
      year: 2015,
      weekDay: 0,
      Date: Sun Jul 19 2015 02:00:00 GMT+0200 (CEST),
      to:
       { text: 'within next 3 days',
         day: 22,
         month: 7,
         year: 2015,
         weekDay: 3,
         Date: Wed Jul 22 2015 02:00:00 GMT+0200 (CEST) },
      localized: 'Sunday, July 19, 2015' } ]

ha, dude. i thought you were fixing this 'and a half' bug.  ;)
leap years and stuff need to be a seperate PR. Breaking API changes definetly need to be a seperate PR!

i thought you were fixing this 'and a half' bug. ;)

but this is fixed by the commit 26 days ago above.

The date and number parser should interact ...
should return arrays (aka all values in the sentence)
tried to base them on the gregorian and metric systems
I'll commit a sneak preview of what I mean now.

why don't you make a pr for that then
https://github.com/redaktor/nlp_compromise/commit/7f95fdfe766a4a8442daa8b6de5b72db2666eacc

because of the last sentence
'both files WIP - for this night ;)'
'Doing this stuff right' (aka most user friendly) feels a bit complicated and
currently it should have the last step of the same logic in both:

numeric ranges

and to make it possible for any user to build his own wolframalpha I am working on unit detection at least for the metric system (Obelix: "These britains are crazy"). File size matters here, I think.

i'm gonna go ahead and fix this then

ok cool.
posted a sneak preview.
just played around with mixed date / number sentences a bit, like
var nlp = new NLP();
var val = nlp.value("possible travel dates are 12/20/2015, 12 / 21 / 2015 or 12/23/2015 and now I eat three bananas.");
var date = val.date();
console.log( val, date, date.text() );

btw:
if you look into the code: It also parses a wide range of relative dates but it needs a {now: new Date()} in the options - are there better alternatives?

i've removed this example from the readme, given its ambiguous use.


Feature/dock 1548/cwl import and include

Description
This draft PR implements changes to the webserver CWL parsing logic to handle all $include/$import/$mixin directives correctly and to properly identify tools in CWLs that have a file structure more than two levels deep.
The solution within is very rough, and not intended to be the final product.  I would like high-level feedback on the overall solution.  Specifically, I'm looking for answers to the following questions:

Is it appropriate to fully expand the CWL and parse it, recursively if necessary?
If the workflow is incomplete, meaning a file that the workflow includes does not exist, is it ok to display an informative error message and no tools, rather than partial results?  The implemented behavior is the former.

Please don't examine for low-level correctness: bugs need to be fixed, debugging cruft needs to be removed, tests need to be written, code needs to be primped, include cycles need to be detected, etc.
I've been testing by manually registering the following repo, which is a fork of the repo noted in the ticket:
https://github.com/svonworl/multi-step-cwl
The solution is two-pronged.  First, I implemented a preprocessor that expands $include/$import/$mixin and "run: " directives, which solves the first part of the problem when parsing the CWL from the above repo, wherein the existing code fails because it does not understand the "{$import" in the "label" field.  Then, I changed CWLHandler.getContent() to examine the proprocessed/expanded CWL and recursively descend through workflows and their subworkflows to find the tools within.  As Walt mentions in the ticket, the existing code "only goes one subworkflow level down".
The preprocessing step is prescribed by the CWL spec:
https://www.commonwl.org/v1.2/Workflow.html#Document_preprocessing
My solution currently supports $mixin, which was in a previous version of the spec, but has since been dropped.
Issue
https://ucsc-cgl.atlassian.net/browse/DOCK-1548

Thanks for the comments.   In the existing code, I believe that processImports, which reads the secondary files referenced by $import/etc, is implemented mostly correctly (it needs some code to prevent dying if there's a cycle, I think).  So, the secondary files are all retrieved properly, but they're processed incorrectly later: that is, when we try to parse a workflow in getContent, if there's an $import statement somewhere other than one of the few places we've bandaided, the code fails.  Thus, the preprocessing step, which uses the set of secondary files retrieved earlier, rather than pulling anything from github itself.  Does that make sense?

As we subsequently discussed via Slack, I had in my mind that we weren't creating SourceFile's for "imports" in many cases, but it seems I was wrong.
@NatalieEO, I recall you running into issues when getting checksums for Docker images for CWL and may have leapt to the wrong conclusion as to the cause, but if you have any more details...

As we subsequently discussed via Slack, I had in my mind that we weren't creating SourceFile's for "imports" in many cases, but it seems I was wrong.

Haven't looked at the code yet, but reading comments to understand the context. I think we create SourceFile's for local imports but not for http imports. Or at least that was the goal,. I'm not sure if's actually working in all cases.


Update commands should set ms.date metadata to current date

Summary of the new feature / enhancement
The update commands:

Update-CommandHelp
Update-MarkdownCommandHelp
Update-MarkdownModuleFile

Should update the ms.date frontmatter metadata to the current date.
Proposed technical implementation details (optional)
No response

Fixed in OPS10


Recursive data structure unmarshalling gives error "cannot parse invalid wire-format data"

What version of protobuf and what language are you using?
Version:  go1.18.1 linux/amd64, github.com/golang/protobuf v1.5.2
What did you do?
I am trying to use recursive proto definitions.
.proto file
message AsyncConsensus {
  int32 sender = 1;
  int32 receiver = 2;
  string unique_id = 3; // to specify the fall back block id to which the vote asyn is for
  int32 type = 4; // 1-propose, 2-vote, 3-timeout, 4-propose-async, 5-vote-async, 6-timeout-internal, 7-consensus-external-request, 8-consensus-external-response, 9-fallback-complete
  string note = 5;
  int32 v = 6 ; // view number
  int32 r = 7;// round number
  message Block {
    string id = 1;
    int32 v = 2 ; // view number
    int32 r = 3;// round number
    Block parent = 4;
    repeated int32 commands = 5;
    int32 level = 6; // for the fallback mode
  }
  Block blockHigh = 8;
  Block blockNew = 9;
  Block blockCommit = 10;
}

The following is how I Marshal and Un-Marshal
func (t *AsyncConsensus) Marshal(wire io.Writer) error {
	data, err := proto.Marshal(t)
	if err != nil {
		return err
	}
	lengthWritten := len(data)
	var b [8]byte
	bs := b[:8]
	binary.LittleEndian.PutUint64(bs, uint64(lengthWritten))
	_, err = wire.Write(bs)
	if err != nil {
		return err
	}
	_, err = wire.Write(data)
	if err != nil {
		return err
	}
	return nil
}

func (t *AsyncConsensus) Unmarshal(wire io.Reader) error {

	var b [8]byte
	bs := b[:8]
	_, err := io.ReadFull(wire, bs)
	if err != nil {
		return err
	}
	numBytes := binary.LittleEndian.Uint64(bs)
	data := make([]byte, numBytes)
	length, err := io.ReadFull(wire, data)
	if err != nil {
		return err
	}
	err = proto.Unmarshal(data[:length], t)
	if err != nil {
		return err
	}
	return nil
}

func (t *AsyncConsensus) New() Serializable {
	return new(AsyncConsensus)
}

What did you expect to see?
When marshaled and sent to the same process via TCP, it should correctly unmarshal and produce correct data structures.
What did you see instead?
error "cannot parse invalid wire-format data"
Anything else we should know about your project / environment?
I tried with non-recursive .proto definitions, and never had this issue

This is a transient error; happens ones every 1000 messages or so. To reproduce, it requires to send a lot (I reproduced this with 2000 back to back messages) of messages

A transient error like this suggests that there is possibly a race condition in your program. Have you tried building with -race and running the program?

Have you tried locking the Marshal and Unmarshal in a mutex? While the individual writes are guaranteed to be atomically written to the TCP socket, there’s no guarantee that two writes will happen sequentially without further synchronization.
Since this only happens intermittently, this is a strong possibility. If two lengths were written one after the other, and I’m very sure that you’re not writing 64 pebibytes of data, the first byte of each length should be 0x00, which contains an invalid field number: 0.

@puellanivis
I use locking for each invocation of Marshal and Unmarshal
To check my hypothesis, I check what happens for non-recursive .proto structs, it I can verify that this transient error never occurs.

It isn't enough that every call of Unmarshal is locked. It is still possible that the inputs to those methods are being concurrently mutated.

@dsnet
Thank you.

i am facing same issue. and i am serializing in python code and unmarshalling in golang code so obvoiusly there is no race condition in my case. can anybody tell what possible issue in my case ?

@mohd-arif since your problem does not appear to be related to synchronization of marshal/unmarshal, could you please start your own issue, so we can address your issues directly?
When you do so, could you please post a hexdump of the protobuf you’re trying to unmarshal, or at least the actual protobuf definition?


Validation: Expected 5 healthy nodes; found 0. (660s elapsed)

hey
so getting thru deploying this in a secured work environment with VCSA 6.5.1, and vSphere in 5.5u3, using vDS in this particular instance.
i get the cluster and nodes deployed but get to a point where it goes to discover nodes and master ; and ; never finds a thing, not a master, not a node, zilcho, all i get is an infinite supply of Validation: Expected 5 healthy nodes; found 0. (xxxxxxxs elapsed)
what action is occuring when its doing this and can i manually try to invoke it?
thanks heaps

note, i can get on the master, and, ping everything just fine - no issues - via normal net OR via flannel - so i know connectivity is there and a happening thing.
of note i can deploy the same in my lab in the exact same way with no issue whatsoever.

@psyolent we can help.
Can you login to the master node and see api server is running?
root@master [ ~ ]# docker ps | grep "hyperkube apiserver"
601f654723ce        3b32bac67a2f                                   "/hyperkube apiserver"   12 hours ago        Up 12 hours                             k8s_kube-apiserver_kube-apiserver-master_kube-system_c59930d330f33cbcff09be57d5ec067a_1
root@master [ ~ ]#

Can you grab API server logs and attach to this issue?

One more thing to check is kubeconfig.json file in your kubernetes-anywhere container.
Can you ping the Server IP address mentioned in the /opt/kubernetes-anywhere/phase1/vsphere/.tmp/kubeconfig.json from your container?
@BaluDontu @tusharnt @rohitjogvmw @luomiao

hey, very appreciated.
no its not running on the master mate.  ; ie: the PS just returns empty - so that could be something of a problem :)
now for the logs.
in the log location ie: /var/lib/docker/containers/ , theres a mass of directories for different things.
the log file in each of them ends with {"log":"Error: failed to run Kubelet: could not init cloud provider "vsphere": 2:25: unknown escape sequence\n","stream":"stderr","time":"2017-08-12T04:01:16:186486095Z"}
they are all the same
yes, the refer in the kubeconfig to that IP pings just fine

@psyolent
Problem could be in the vsphere.conf file. Look at  /etc/kubernetes/vsphere.conf
We need to escape special characters in vsphere.conf file.
Recently @jck-ccl has fixed the issue - https://github.com/kubernetes/kubernetes-anywhere/pull/416
If you are using cnastorage/kubernetes-anywhere:latest image to deploy kubernetes cluster then we need to include this change in the image.
Meanwhile you can try deploying cluster using cnastorage/kubernetes-anywhere:vmc image.
docker pull cnastorage/kubernetes-anywhere:vmc
docker run -it --rm --env="PS1=[container]:\w> " --net=host cnastorage/kubernetes-anywhere:vmc /bin/bash

Let us know if the issue persist with this new image as well.

excellent. that build went thru successfully. thanks divyen!
now to deal with this 'unauthorized' issue when i go to the Kubernetes Master.
cheers, Greg

@psyolent you can close this issue and open a new issue for 'unauthorized' error on the master node with more detail.

Any movement on getting this into master yet?  Having the same problem here with vCenter 6 managing a vSphere 6 cluster with both a vDS and a SDRS storage datastore, though it results in it getting stuck repeating "found 1" instead of "found 0".   Resources: 22 added, 0 changed, 0 destroyed.

Which results in the final result...
Validation: Expected 5 healthy nodes; found 1. (10s elapsed)
Validation: Expected 5 healthy nodes; found 1. (20s elapsed)
Validation: Expected 5 healthy nodes; found 1. (30s elapsed)
Validation: Expected 5 healthy nodes; found 1. (40s elapsed)
Validation: Expected 5 healthy nodes; found 1. (50s elapsed)
Validation: Expected 5 healthy nodes; found 1. (60s elapsed)
Validation: Expected 5 healthy nodes; found 1. (70s elapsed)
Validation: Expected 5 healthy nodes; found 1. (80s elapsed)
Validation: Expected 5 healthy nodes; found 1. (90s elapsed)
Validation: Expected 5 healthy nodes; found 1. (100s elapsed)
Validation: Expected 5 healthy nodes; found 1. (110s elapsed)
Validation: Expected 5 healthy nodes; found 1. (120s elapsed)
Validation: Expected 5 healthy nodes; found 1. (130s elapsed)
Validation: Expected 5 healthy nodes; found 1. (140s elapsed)

Which lasts indefinitely.

An update to my previous post:
This issue, for me at least, appears to be due to choosing too small of a management network size for the cluster.  This is my first time messing with Kubernetes, I am attempting to create a cluster to migrate machines to from our existing Rancher cluster in prep for the release of Rancher 2.0.  I did not realize that Kubernetes requires a /24 for each node, so I had just allocated a single /24 to the whole cluster when prompted during make config.
I was reading about the networking in prep for trying a manual install since this hasn't been working when I stumbled across that requirement.
It should probably be mentioned during the config process, or better yet, an error displayed if you choose a network size too small for the number of nodes you've selected.

@edqallen Thanks for trying out this stuff will add a help message to config process

I am also having an issue deploying to my vsphere cluster but the issue seems to be coming from a different source, on startup of the kubelet container, I get the error:
Dec 13 09:43:27 kubernetes-master docker[826]: Error: unknown flag: --api-servers
vsphere environment (managed via vcenter)
Server vsphere 6.0.0 (machine image 10)
Client vsphere 6.0.0
Kubernetes version attempted to deploy: v1.8.5
OVA: OVA For vSphere 5.5 with Virtual Machine Hardware Version 10  (tried vSphere 6.0+ OVA but cluster refused to deploy it)
Ignite: docker.io/cnastorage/k8s-ignition:v2
docker_registry: docker.io/googlecontainer
Anything I'm missing?

@D3nn For 1.8 kubernetes releases you can use this new ignition image cnastorage/k8s-ignition:v1.8-dev-release This ignition image uses new kubelet flags for 1.8 releases.


Windows cannot install with Node.js 20.18.2 security patch breaks child_process.spawn()

Note
Before you submit your issue, make sure that:

You're using the latest version of Salesforce CLI.
You've searched both open and closed issues for related posts.
You've used the doctor command to diagnose common issues.
You understand that GitHub Issues don't adhere to any agreement or SLA.

If you require immediate assistance, use official channels such as Salesforce Customer Support.

Summary
https://nodejs.org/en/blog/vulnerability/april-2024-security-releases-2
yarn global add @salesforce/cli
Corepack is about to download https://registry.yarnpkg.com/yarn/-/yarn-1.22.22.tgz.

Do you want to continue? [Y/n] y
yarn global v1.22.22
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
warning "@salesforce/cli > @salesforce/plugin-info ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^2.0.0".
warning Workspaces can only be enabled in private projects.
warning Workspaces can only be enabled in private projects.
[4/4] Building fresh packages...
[3/3] ⠂ @salesforce/cli
[-/3] ⠂ waiting...
error C:\Users\xx\AppData\Local\Yarn\Data\global\node_modules\@salesforce\cli: Command failed.
Exit code: 1
Command: node ./scripts/post-install-release-notes.js
Arguments:
Directory: C:\Users\xx\AppData\Local\Yarn\Data\global\node_modules\@salesforce\cli
Output:
node:internal/child_process:421
    throw new ErrnoException(err, 'spawn');
          ^

Error: spawn EINVAL
    at ChildProcess.spawn (node:internal/child_process:421:11)
    at spawn (node:child_process:761:9)
    at file:///C:/Users/xx/AppData/Local/Yarn/Data/global/node_modules/@salesforce/cli/scripts/post-install-release-notes.js:24:17
    at new Promise (<anonymous>)
    at main (file:///C:/Users/xx/AppData/Local/Yarn/Data/global/node_modules/@salesforce/cli/scripts/post-install-release-notes.js:14:9)
    at file:///C:/Users/xx/AppData/Local/Yarn/Data/global/node_modules/@salesforce/cli/scripts/post-install-release-notes.js:44:7 {
  errno: -4071,
  code: 'EINVAL',
  syscall: 'spawn'
}

Steps To Reproduce

install nodejs 20.18.2
attempt to install @salesforce/cli via npm or yarn

IMPORTANT
Provide a repository that's configured to reproduce the issue. If you are unable to provide a repo, please explain why not. The more info we have from the start, the faster we can resolve your issue.
We may close your issue if you don't include proper instructions.

Generate a project with sf project generate or fork dreamhouse-lwc.
Provide detailed step-by-step instructions on how to reproduce the issue.

Expected result

Actual result

System Information

{}

Additional information

duplicate of https://github.com/forcedotcom/cli/issues/2822 (pinned issue).


Peer review - Ty

Dear Ty, I would like you to have a look at my app and leave two pieces of constructive feedback for potential improvement of the app.
Here's the link to the deployed app:
https://suicides-analysis.onrender.com/
Thank you

Nice work, a couple things that could be improved:

The pie chart has two separate instances of each age group, on hover you can see multiple orange slices with different numbers that presumably sum to the total number of suicides. Looking at the code I can't quite tell where the altair code is doing it.  May be a data parsing issue that some entries of age range aren't EXACTLY the same so maybe stripping white spaces etc. could be tried.
On your slider, you're missing the step argument so it's allowed to input fractional year values, hence the plots arent' updating for a lot of data points being seen as "missing" when in fact it's just the slider. Just add in step = 1 and it should be good to go!
I would consider removing the y-axis label of "Gender" on the male/female plot as those speak for themselves and also I'd make the plot a bit taller just as visually it's a bit under represented.

Thank you Ty. I have updated the slider steps as per your suggestion. It works better now

I had great pleasure using and reviewing the application created by Qurat. A couple of improvements that you could consider:

It is worth considering making the pie-chart more interactive where you could select/un-select the specific age group and and get the suicide percentage of total number of population. You could also add extra flexibility to your user by doing this.
While keeping the number of suicides in the tooltip, I would also consider calculating the percentages and displaying them on each corresponding slice of a pie chart. This would make it easier for the user to see the statistics.
It might be useful to include a third chart that shows the trend in suicide rates over time for the selected country. This would provide a more complete picture of how the suicide rates have changed.

I hope to see further improvement and iterations on this project resulting in a more polished and effective tool. Great job!


Unable to make predictions using pgml.predict

After successful training,
Issue #1 ---- On trying to predict from data, i am getting the error: function pgml.predict(unknown, numeric[]) is not unique

On querying from routines, i see that there are multiple predict functions. Is there an issue with the installation?

Isssue #2 ---- when there is a categorical field as input for regression, I am getting below error (een though training was complete successfully):

You'll need to cast your ARRAY[...] to a float4[], e.g. ARRAY[1,2,3,4]::float4[]

Hi, this is the description of the data.. Its the usual Iris dataset:

Hi, this is the description of the dataset. its the usual Iris dataset

The issue here is a limitation of Postgres ARRAY types. They must be homogenous. What if you pass a heterogenous tuple type instead? e.g.
SELECT pgml.predict('205_810', ("Class", "Sepalwidth", "Petallength", "Petalwidth"))
FROM iris_new
LIMIT 10;

For the given predict function, I am getting below error

Any way we could ensure the errors displayed are more readable?


Create AD B2C custom policies and allow app developers to edit the settings in App Center

Identity MVP Technical Specification
In the month of Apr, we are working on creating AD B2C custom policies and allow app developers to edit the settings in App Center.
Let us know if you have any feedback, or would like to be a part of our private preview!
Here are some designs:

Closing this issue - we reduced the scope and did not implement this in our public preview. If you have any feedback, please let us know. You can learn more about Auth!


symbol issue

Hi
When I am trying to use this I am getting the following error on an Ubuntu box:
ImportError: /home/aaron/.virtualenvs/rules2/local/lib/python2.7/site-packages/rules.so: undefined symbol: redisFormatCommandArgv
Any ideas what could be wrong here?

Hi, thanks for the feedback. Let me look into this. I'll get back to you soon.

This should work now. I just tried it using an AWS instance. To get this to work I changed:

Passed the right compiler options in setup.py
Compiled rules and hiredis into a single library
Changed the order of arguments in pyBindRuleset (to workaround a bug in PyArg_ParseTuple


how are badging requirements vetted

Hi guys,
I couldn't find anything on the badging website or on here (https://github.com/coreinfrastructure/best-practices-badge/blob/master/doc/other.md) about how all these requirements for silver badging are being verified and by who exactly.  I can see cii score on the linked GitHub repo being updated in realtime as I fill out the questionnaire on the badging website but how are they checked and what is the approximate timeframe for getting feedback.
So basically how does the project ascertain that it has reached the silver badging status that it applied for.  We want to be thorough and make sure we don't fudge anything unintentionally.

I'll give a specific example.  Looking at TUF (https://bestpractices.coreinfrastructure.org/en/projects/1351?criteria_level=1#security), the response to
"The project results MUST check all inputs from potentially untrusted sources to ensure they are valid (a whitelist), and reject invalid inputs, if there are any restrictions on the data at all. [input_validation]  Show details "
is
'The project strives to validate all input to functions.'
Does this qualify as satisfying the requirement or are other additonal parts of the response not visible to public.

@idvoretskyi can you please help here?

The presentation Core Infrastructure Initiative (CII) Best Practices Badge in 2019 briefly discusses vetting on slide 2 (starting from 0). (This was a presentation at the Linux Foundation's Open Source Leadership Summit 2019 in Half Moon Bay, CA.)
The approach is based on self-certification.  There are literally millions of OSS projects (we counted), and we think requiring fees for every OSS project would mean the vast majority of projects would not participate.  In addition, we focused on "what is important" regardless of whether or not it's easy to automate (though we prefer criteria that can be automatically determined where that is reasonable).
The problems of self-certification are well-known, so we have various mechanisms to mitigate its problems:

Automation.  We work to automatically determine answers, and we will not accept answers where can confirm with high confidence that the answer is false.  E.g., if you use "http://" for your project or repo URLs, your project fails the 'requires https' criterion.  That means that the badge is not strictly self-certification, we're merely based on it.  In the long term we hope to implement more automation. The file criteria/criteria.yml documents how we think various criteria could be automated. Patches to improve automation are joyfully welcomed.
Public display of answers (for criticism).
Spot-checks.  In particular, we get notifications of various events or suspicious claims for review.
Answers can be overridden if false.

I hope that helps!

We greatly appreciate your desire to "not fudge the answers" - please keep doing that :-) !  First check the details - we try to answer your questions in the details.  If you still have questions, filing an issue is a good way to get an answer. I'll email TUF, that is a somewhat lame answer & I'm pretty confident that they can do a better job answering the question :-).

Thanks David, that helps.  We will try to be as thorough has possible with the answers.

Very good.  We've added a new page on vetting and linked to it from the README.  That should help answer others' questions in the future.  I'm closing this issue, let me know if it should be reopened.


seq: remove --terminator/-t option

Remove the --terminator option to seq. This option does not exist in
the GNU version of seq.
See comment https://github.com/uutils/coreutils/pull/2615/files#r707837373

On the other hand, freebsd does support --terminator according to their man page, so I'm inclined to keep this flag.

Hmm. FreeBSD's implementation of --terminator (and --separator) supports escape codes, like \0, \t and \xFF. GNU's implementation of --separator doesn't though.

If there's no consensus on removing this, then I'll just close this for now. I'll create a new pull request with the change suggested by https://github.com/uutils/coreutils/pull/2615#discussion_r706598679


NVIDIA GPU Driver Extension Documentation Out of Date

The Documentation for the NVIDIA GPU Driver is out of date. When I try to install the NVIDIA GPU Driver, it fails to download some packages, not because it can't access the internet like the documentation suggests, but rather because it's not possible to download the list of packages required by the extension anymore. This would suggest the extension is out of date.
Here's the exact error I get:
"""
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
cuda-drivers : Depends: cuda-drivers-545 (= 545.23.06-1) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
"""
The troubleshooting documentation has no suggestions about how to go about solving this issue.
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: f1ac786e-9654-aa34-f910-e61863fed4e4
Version Independent ID: 6b7dbdfb-09a3-19ef-4901-36c10f0a28d8
Content: Troubleshoot GPU extension issues for GPU VMs on Azure Stack Edge Pro GPU
Content Source: articles/databox-online/azure-stack-edge-gpu-troubleshoot-virtual-machine-gpu-extension-installation.md
Service: databox
Sub-service: edge
GitHub Login: @v-dalc
Microsoft Alias: alkohli

@mcrchopra
Thanks for your feedback! We will investigate and update as appropriate.

@mcrchopra
I've delegated this to @alkohli, a content author, to review and share their valuable insights.


Windows Application Translator

Description of the new feature / enhancement
The idea would be to translate any application in Windows in real time with subtitles or audio would be very useful and I don't see any programme that does this in an effective way, of course, it has to be available for several languages including Brazilian Portuguese, even within applications that don't have languages available or in games, I see many people wanting this type of application.
Scenario when this would be used?
For applications that have other languages, with this idea the user will be able to translate in real time by moving the mouse or dragging on it, and a subtitle or audio will appear for the person's language to understand how the application works.
Supporting information
No response

/dup #18014


Incorrect decompilation output (hello world with message boxes)

I create simple hello world project and can't get correct decompilation output with latest retdec!
Input code:
#include <Windows.h>
void MessageBoxA_test1(const char* message, const char* header)
{
	MessageBoxA(0, message, header, 0);
}
int main()
{
	MessageBoxA_test1("Hello", "World");
	MessageBoxA_test1("World", "Hello");
}

Retdec output : https://pastebin.com/bsnT1Ecb
1. I can't find main function
2. I can't find MessageBoxA_test1("Hello", "World") call
3. No 'Hello' and 'World' lines in output;
For compare snowman output: https://pastebin.com/7pHj1z6C
1. I see correct main func
2. I see correct MessageBoxA_test1("Hello","World") calling!
uint32_t fun_14001118b(int64_t rcx, int64_t rdx, int64_t r8) {
    int32_t ecx4;

    ecx4 = 58;
    while (ecx4) {
        --ecx4;
    }
    fun_140011082(0x140020012);
    fun_140011208("Hello", "World");
    fun_140011208("World", "Hello");
    return 0;
}

And input binary (x64 Windows, build Visual Studio 2019) :
TestRetdec2.zip

@s3rvac, you don't know, this is error in retdec or not ?

Well, I cannot tell from the C output only, but as you have suggested, this may be caused by the wrong convention being used. This is mainly caused because the signature of the function is not known as the function was not recognized and the fallback convention is used. We are currently working on letting users specify info (among which is calling convention) by various methods (for example, some third party frontend), which might help to solve this issue for you.

@xkubov in this 'hello world' i use default calling convention. And i no enter calling convention in snowman decompiler, and got correct result.

Well, even the default convention might not be the same as the fallback convention in RetDec analysis. I am grateful for your remarks and we will certainly benefit from it.
When it comes to the global strings, the most definitely were discarded by the used LLVM optimizations. Generally in compilers when some code is not being used it is discarded. This sometimes helps as it discards lot of garbage on output but also in some cases (like yours) it may discard some important strings when the decompiler failed in some analysis (like analysis of calling convention).

@xkubov I see 'Hello' and 'World' strings in 'TestRetdec2.exe.dsm' and in 'TestRetdec2.exe.ll' files.

But strange.... I can't find any references for this strings in these files....

@xkubov @s3rvac i found! This is error in '-register-localization' (this cause lost global vars)

Thank you for the analysis but the problem is not in the register localization. The real problem was as I said is in the analysis of parameters.
On x64 architecture, there is a difference between the Microsoft x64 and Unix ABI. In RetDec there was a wrong condition for detection of Microsoft x64 ABI. I have managed to correct this condition and get the following output:
  int64_t function_140011780(void) {
      // 0x140011780
      int64_t v1; // bp-248, 0x140011780
      __asm_rep_stosd_memset((char *)&v1, -0x33333334, 58);
      function_140011082(&g53);
      function_140011208("Hello", "World");
      function_140011208("World", "Hello");
      return 0;
  }

As you can see it is more what you would expect to get.
As a side note: I played with the RetDec radare2 plugin with this binary and got an even better result by altering names and so on:
void main_wrap(int32_t a, int32_t b) {
    // 0x140011780
    int64_t v1; // bp-248, 0x140011780
    __asm_rep_stosd_memset((char *)&v1, -0x33333334, 58);
    unkown((int32_t)&g1, b);
    MessageBoxA_test1("Hello", "World");
    MessageBoxA_test1("World", "Hello");
}

I will run the changes on our test set and will provide you with details when the changes are merged into master. Thank you for your input on x64 binaries.

So, your error should be solved by 6cc12004. I've managed to get all expected parameters of the function, as can be seen above. If you find another place where we could improve the decompilation of x64 binaries feel free to open a new issue.

@xkubov thanks!!!

@xkubov i download latest TeamCity build Time Date Stamp:              	5E4419B5h  -> 12/02/2020  18:28:53
But see same problem.
int64_t function_140011780(int64_t a1) {
    // 0x140011780
    int64_t v1; // bp-248, 0x140011780
    __asm_rep_stosd_memset((char *)&v1, -0x33333334, 58);
    bool v2; // 0x140011780
    function_140011082((v2 ? -232 : 232) + (int64_t)&v1);
    function_140011208();
    function_140011208();
    return 0;
}

Now even 'system' function call is lost!!!

Did you try this build? https://retdec-tc.avast.com/viewLog.html?buildId=3477&buildTypeId=Retdec_WinBuild&tab=artifacts
This should be the latest working version. I have checked on a clean build (on macOS) and the output was the same as above.

Time Date Stamp:              	5E442346h  -> 12/02/2020  19:09:42
// Address range: 0x140011780 - 0x1400117dc
int64_t function_140011780(void) {
    // 0x140011780
    int64_t v1; // bp-248, 0x140011780
    __asm_rep_stosd_memset((char *)&v1, -0x33333334, 58);
    function_140011082(&g53);
    function_140011208("Hello", "World");
    function_140011208("World", "Hello");
    return 0;
}

@xkubov now all works


bug: npm deps check runs when we have deps

Not sure how this occurs; asking for users who see it to help me diagnose https://discord.com/channels/1186394868336038080/1186421052071477428/1261464957791244308

#195


Adding squeeze and unsqueeze tests

Adding squeeze and unsqueeze tests

@chandrasekaranpradeep @nvukobratTT Removed decompose of unsqueeze and squeeze. Please review.


Mobile "Home Screen" app not updating

Are you aware of any different behavior when a PWA (using offline-plugin) is added to the home screen using "Add to Home Screen" on Chrome/Android or Safari/iOS?
I'm having problems with the app getting stuck using the cached version when it was installed and never updating.
I even have offline-plugin responseStrategy set to network-first but it seems to always use the cached version after adding to the home screen.
The service worker is updating fine in Chrome on both Windows and Android.
I expect the app to check for a new service worker every time the app has a clean start and switch to the new service worker after relaunching the app and/or rebooting the phone.  But after a few days of testing and several restarts it's still stuck on the old version.

I discovered that this issue seems to be related to having both AppCache and Service Worker enabled.
It seems that when a web app is added to the home screen on an Android the service worker does not function and the app cache takes over (contrary to what happens in Chrome).  Or maybe neither was used and Android activated some other caching mechanism!
When I did a series of test deployments which excluded AppCache, the Service Worker worked correctly and updated as expected.
I'm not sure if this is a bug in offline-plugin or Android.  I haven't done any testing using vanilla javascript.
Since iOS now supports service workers, I don't really need AppCache as a fallback so I'm just going to leave it disabled!

@mattgaspar thanks for your investigation and for sharing your results
After reading up on this issue, there seems to be a couple of issues regarding appcache and adding a page to the home screen, such as having to wait for the appcache to cache assets for a prelonged time as well as some hacky code to add it to the registry. I would guess we will not focus on this since there is a working solution that is more or less future proof (using service worker).
Will close this for now, please let me know if you think othervise @NekR

Tip for anyone else running into this issue:
After disabling appCache in your webpack.config, you should also add an invalid manifest URL to your home page (index.html)
<html manifest="disabled.appcache">
Without this the Android devices seemed to remain stuck with the old cached files.  This seemed to invalidate the app cache and remove the files.  Leave this in-place until you think all Android devices have loaded the updated version.
@GGAlanSmithee and @NekR,
I haven't looked at the offline plugin source code but I'm guessing there is some type of feature detection to determine whether to use appCache or Service Worker.  It seems like there may be a problem with the detection when used as a home screen app since appCache should not have been enabled in the first place on these devices.
I noticed that the Android devices did have the service worker running but maybe serving files from appCache?
FYI - My app has other app specific code in the service worker file, so it may have been activated by the register code in the app.  It would have also been activated by initially running the app in Chrome before adding to the home screen.
(The webapp-manifest has a display type of standalone.)

@mattgaspar interesting. Kind of a edge-case I guess, but might still be warrented to atleast add to the docs. Or maybe even to handle this in the code.
Seems like
if (window.navigator.standalone) {
    // fullscreen mode

}

can be used to feature detect wether the app is run from the home screen.

Maybe remove appCache at all in future versions? :)

WKWebView does not support Service Workers yet. So when running your javascript inside a WKWebView and you want to use caching, you still need the AppCache to work.

Good point @bjornbos


OCPBUGS-42974: [release-4.17] Do not send traffic to local audit-webhook through konnectivity

What this PR does / why we need it:
In managed services, a local audit-webhook service is used to forward audit logs externally. This traffic should not be routed through konnectivity since it goes to a local service in the control plane.
Backport of https://github.com/openshift/hypershift/pull/4864
Which issue(s) this PR fixes (optional, use fixes #<issue_number>(, fixes #<issue_number>, ...) format, where issue_number might be a GitHub issue, or a Jira story:
Fixes #
Checklist

[ ] Subject and description added to both, commit and PR.
[ ] Relevant issues have been referenced.
[ ] This change includes docs.
[ ] This change includes unit tests.

/jira cherrypick OCPBUGS-42873

/jira refresh

/lgtm

/test e2e-kubevirt-aws-ovn-reduced

/cherry-pick release-4.16


Please allow OpenCL and HIP users to shared  on the same system

Please allow OpenCL and HIP users to shared  on the same system, and not require separate systems for miopen-OpenCL and miopen-HIP.  Also, currently each dedicated miopen-opencl and miopen-hip  system requires a GPU.
"Installing MIOpen with pre-built packages
MIOpen can be installed on Ubuntu using apt-get.
For OpenCL backend: apt-get install miopen-opencl
For HIP backend: apt-get install miopen-hip
Currently both the backends cannot be installed on the same system simultaneously. If a different backend other than what currently exists on the system is desired, please remove the existing backend completely and then install the new backend."

Thanks for this feature request. Can you please explain why and when would you want both the backends to co-exist at the same time?

Reference: #1664


Release v207

https://github.com/heroku/heroku-buildpack-python/compare/v206...7ba51407953e926b44c125adf9b40611136b92a4
GUS-W-10857615.

$ make publish
Deploy as version: v207 [y/n]? y

Tagging commit 71ee4eea8fa6c31152ce3aeb53e12b29abe25242 with v207...
Username for 'https://github.com': edmorley
Password for<EMAIL_ADDRESS>Total 0 (delta 0), reused 0 (delta 0), pack-reused 0
To https://github.com/heroku/heroku-buildpack-python
 * [new tag]         v207 -> v207

Publishing to the buildpack registry...
Two-factor code: ********************************************
Publishing buildpack heroku/python... done
Publishing buildpack was successful

Version  Released At               Status
───────  ────────────────────────  ─────────
207      2022-03-16T22:33:13.117Z  published

https://devcenter.heroku.com/articles/python-support#supported-runtimes
https://devcenter.heroku.com/articles/python-runtimes#selecting-a-runtime
https://devcenter.heroku.com/changelog-items/2367


Snippet Converted Not Working for literal Dollar Sign in Sublime Snippets

From @digitaldrummerj on February 22, 2016 4:55
In sublime snippets, if you want to have a literal $ show up as part of the text the snippet inserts, you have to escape it with a backslash.  When the snippet conversion runs as part of yeoman extension generator, it changes the $ that to a \$ so when you use the snippet in VSCode, you get a $ inserted into your code of just the $.
Sublime Snippet
<snippet>
  <content><![CDATA[
\$scope.\$broadcast('scroll.infiniteScrollComplete');
]]></content>
  <!-- Optional: Set a tabTrigger to define how to trigger the snippet -->
  <tabTrigger>ionicbroadcastinfinitescroll</tabTrigger>
  <!-- Optional: Set a scope to limit where the snippet will trigger -->
  <scope>source.js</scope>
</snippet>

VS Code Converted Snippet
"ionicbroadcastinfinitescroll": {
		"prefix": "ionicbroadcastinfinitescroll",
		"body": "\n\\$scope.\\$broadcast('scroll.infiniteScrollComplete');\n",
		"description": "",
		"scope": "source.js"
	}

When Used in VS Code (Notice the $ instead of just $
\$scope.\$broadcast('scroll.infiniteScrollComplete');

Copied from original issue: Microsoft/vscode-generator-code#32

From @bpasero on February 29, 2016 9:6
@aeschli fyi


SPO alignment

Create the list of SPO's to participate in beta launch
Get the commitment from SPO's
Internal alignment with IOG SPO's


Restrict CI and release task to r2dbc/r2dbc-spi repo

I just updated my fork of r2dbc-spi, and I got failure emails from GitHub Actions triggered on my fork due to unavailable credentials for the Sonatype repository. This change will restrict those actions to only run on the main repository (r2dbc/r2dbc-spi).

Thanks. I wasn't even aware how GitHub actions affect forks.

Yeah, I also wasn't aware until we had some fun in the Firebird project when one of our actions to update timezone information opened PRs on all forks ;).
BTW: I don't have the r2dbc-proxy, r2dbc-pool and r2dbc-h2 projects forked, but they also seem to be affected. If you want me to, I can fork them and create pull requests to fix those projects too.

What works for you best. Probably creating an issue is almost the same effort as submitting a PR


yosys: 0.32 -> 0.33

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/yosys/versions.
meta.description for yosys is: Open RTL synthesis framework and tools
meta.homepage for yosys is: https://yosyshq.net/yosys/
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.33 with grep in /nix/store/l4qpidljgxbq21dbhwwhzr5p84pvfvyl-yosys-0.33
found 0.33 in filename of file in /nix/store/l4qpidljgxbq21dbhwwhzr5p84pvfvyl-yosys-0.33

Rebuild report (if merged into master) (click to expand)

17 total rebuild path(s)

17 package rebuild(s)

First fifty rebuilds by attrpath
fusesoc
glasgow
mcy
openroad
python310Packages.amaranth
python310Packages.amaranth-boards
python310Packages.amaranth-soc
python310Packages.edalize
python311Packages.amaranth
python311Packages.amaranth-boards
python311Packages.amaranth-soc
python311Packages.edalize
silice
symbiyosys
yosys
yosys-bluespec
yosys-ghdl

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/l4qpidljgxbq21dbhwwhzr5p84pvfvyl-yosys-0.33 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A yosys https://github.com/r-ryantm/nixpkgs/archive/3cbd7784390886691a7df96324b1b3dfa6a122d0.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/l4qpidljgxbq21dbhwwhzr5p84pvfvyl-yosys-0.33
ls -la /nix/store/l4qpidljgxbq21dbhwwhzr5p84pvfvyl-yosys-0.33/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package failed to build:

openroad

16 packages built:

fusesoc
glasgow
mcy
python310Packages.amaranth
python310Packages.amaranth-boards
python310Packages.amaranth-soc
python310Packages.edalize
python311Packages.amaranth
python311Packages.amaranth-boards
python311Packages.amaranth-soc
python311Packages.edalize
silice
symbiyosys
yosys
yosys-bluespec
yosys-ghdl

Maintainer pings
cc @VShell @thoughtpolice @emilazy for testing.

Closing in favour of #254765, which fixes the build failure on Darwin.


Markdown: Fix captures for link-ref-shortcut

Markdown text between square brackets has mismatching bracket colours with some themes.
For example, the phrase [text] with the Quiet Light theme appears as:

The problem is likely because link-ref-shortcut, defined in markdown.tmLanguage, is looking for a fourth capture when there are only three.
This PR should fix this.

We pull our markdown grammar from this repo: https://github.com/Microsoft/vscode-markdown-tm-grammar
Can you please make the change against the repo instead. I'll pull the fix in to VS Code once the pr is merged upstream


Create a common vscode workspace settings

I suggest creating a checklist of configurations we want to have in our workspace:

Default extensions
Linters & formatters:

c++
python
xml
cmake
yaml
...

This depends on the discussion in https://github.com/open-br/ros_ws/issues/8


[SAGE-619] make list and table rows clickable

Description

[x] update the click target of the primary link in the catalog item and table components
[x] updated the z-index of all nested interactive elements to sit above the expanded hitbox

Screenshots
Catalog Item (Rails)

Before
After

Table (Rails)

Before
After

Table (React)

Before
After

Testing in sage-lib

Verify that the entire row is the interactive trigger instead of only the primary link:

Catalog Item (Rails)
Table (Rails)
Table (React)

Testing in kajabi-products

(HIGH) Changes the click target of Catalog Items and Tables to be the entire row.

Related

Closes SAGE-619

Closed in favor of https://github.com/Kajabi/sage-lib/pull/1532


Cannot run 'func' command

Everytime I run npm install --global azure-functions-core-tools@core and then try just running func I get the following error:
PS C:\Users\JayJain\Documents\Code\hl7-recv> func
func : The term 'func' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ func
+ ~~~~
    + CategoryInfo          : ObjectNotFound: (func:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

System:
Node: v8.11.4
Npm: 5.6.0
VSCode Version: 1.33.1 (user setup)
Node.js: 10.2.0
V8: 6.6.346.32
OS: Windows_NT x64 10.0.18362

I have also already restarted my shell, application and machine

@wookiee89 can you try this instead:
npm install --global azure-functions-core-tools@2

The "core" tag is no longer maintained or kept up-to-date as far as I'm aware.

Tried this:
PS C:\Users\JayJain\Documents\Code\hl7-recv> npm install --global azure-functions-core-tools@2
C:\Users\JayJain\AppData\Roaming\npm\azurefunctions -> C:\Users\JayJain\AppData\Roaming\npm\node_modules\azure-functions-core-tools\lib\main.js
C:\Users\JayJain\AppData\Roaming\npm\func -> C:\Users\JayJain\AppData\Roaming\npm\node_modules\azure-functions-core-tools\lib\main.js
C:\Users\JayJain\AppData\Roaming\npm\azfun -> C:\Users\JayJain\AppData\Roaming\npm\node_modules\azure-functions-core-tools\lib\main.js

><EMAIL_ADDRESS>postinstall C:\Users\JayJain\AppData\Roaming\npm\node_modules\azure-functions-core-tools
> node lib/install.js

attempting to GET "https://functionscdn.azureedge.net/public/2.6.666/Azure.Functions.Cli.win-x<IP_ADDRESS>6.zip"
[==================] Downloading Azure Functions Core Tools
+<EMAIL_ADDRESS>updated 4 packages in 6.48s
PS C:\Users\JayJain\Documents\Code\hl7-recv> func

Same issue:
PS C:\Users\JayJain\Documents\Code\hl7-recv> func
func : The term 'func' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ func
+ ~~~~
    + CategoryInfo          : ObjectNotFound: (func:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

Alright it sounds like npm packages aren't in your path for some reason. You could try manually running npm uninstall --global azure-functions-core-tools and re-install with the above command to see if that "resets" it. Here's a few other resources regarding npm path issues:

This issue has a few ideas to check your PATH and npm global prefix: https://github.com/npm/npm/issues/16313
You could also try manually editing your path as described here: https://stackoverflow.com/questions/9587665/nodejs-cannot-find-installed-module-on-windows

Running npm config set prefix 'C:\Program Files\nodejs' resolved my issue.
Thanks @EricJizbaMSFT for pointing this out to me!


Add increasingFromRanges("property_name", 1, 7, 9, 11)

Populates objects increasingly from 1 to 7, and 9 to 11. If there are more objects, than it will start from the beginning.
This is straight forward for integer values.
Consider adding "step" property which will say how much the previous value should be incremented for. This is useful for Date and double values.

This feature could be useful for testing aggregation queries, because it's (relatively) easy to predict what the sum of values of certain property (which is aggregated) is.

Implemented as circular value and circular range value.


Percy

cleanup of stuff that isn't contributing to a stable build.
Use Percy to so visual builds of the website.  (https://percy.io/a6bbdd63/gray.digital/builds/14036805?utm_content=approved&utm_source=slack&utm_term=link). slack channel #dev-gd-home-percy
Adds a script called trunk which is just a linter I like.  (https://docs.trunk.io/)

Thanks for approving.
Will tackle this some more over the weekend.  Something is breaking the build command, so going to remove all the extraneous libraries to pint point.
Also added you to the readme 🚀
Will send back your way when I get it working.

combined with #101


python's pkgconfig and recent breakages (pycapnp, pyvips, ...)

The issue
Moving pkgconfig to nativeBuildInputs broke a few python packages.
I noticed it with pycapnp, (#170796, #171139), but looking elsewhere it seems pyvips was similarly broken in 646b9a7dbc499e31d4ec57555c3b02a15af8e95e .
These changes are maybe correct in that build-time-only python deps belong in nativeBuildInputs, according to our docs and AFAICT, in practice.
What's going on with pkgconfig?
pkgconfig seems special, and needs to be a "buildInput".
Looking into the issue a bit further:
pkgconfig needs pkg-config and for pkg-config to be able to find packages reliably.
I think what's going wrong here is explained by:
1.) pkg-config (native tool) in pkgconfig (python package) is listed in propagatedNativeBuildInputs.  This was done here: 3f7e683741583da08d2af51849eaf3132cd4d30d , and here's it in master:
https://github.com/NixOS/nixpkgs/blob/84e8005e4dab135215ddab5f4e7d85f1efafea43/pkgs/development/python-modules/pkgconfig/default.nix#L21
2.) This snippet form our docs about propagatedNativeBuildInputs:

The propagated equivalent of nativeBuildInputs. This would be called depsBuildHostPropagated but for historical continuity. For example, if package Y has propagatedNativeBuildInputs = [X], and package Z has buildInputs = [Y], then package Z will be built as if it included package X in its nativeBuildInputs. If instead, package Z has nativeBuildInputs = [Y], then Z will be built as if it included X in the depsBuildBuild of package Z, because of the sum of the two -1 host offsets.

So what we want, probably, is for pkg-config to end up as a nativeBuildInput of packages that use it as a dependency (even if the tool is found, getting these levels "right" is important for how various search paths are put together/plumbed).
From the above language, we see that this only happens when pkgconfig is in buildInputs (since pkg-config is in propagatedNativeBuildInputs).

What to do?

Put pkgconfig back into buildInputs everywhere.  This is maybe wrong in principle and maybe in practice, but also worked previously and AFAIK hasn't caused issues.  Someone more familiar may know why this is a bad idea.

I think we could put pkg-config in propagatedBuildInputs instead -- those get propagated to the same 'level' as the package itself IIRC, and so if we want pkgconfig to be a nativeBuildInput and for that to bring pkg-config to nativeBuildInputs then this should work.  It may change some things, like how it behaves when pkgconfig is a buildInput (esp propagatedBuildInput) particularly when cross-compiling.  I haven't checked/investigated/thought it through yet.

Anyway given these breakages wanted to at least get folks looking at this issue and maybe we can come up with a fix + understanding :).

The main issue has been fixed.


Update to 0.6

Hi, excellent crate!
There is any planning to update to bevy 0.6?

Sorry, I would want to open the issue in bevy_spicy_aseprite 😅


Multicast Support

Would it be possible to add a checkbox for multicast support ?

Multicast (both L3 & L2 [with an overlay like vxlan]) can be performed over a vpn tunnel.
Switches need to be able to send multicast data to broadcast domain of multicast configured router.
If you’re experimenting with multicast, and you have a 2byte ASN check out IPv4 GLOP address space.
Each 2byte ASN is allocated a GLOP IPv4 range for multicast.
There’s no need to coordinate with RIR’s, just get your ASN binary equiv to find your Glop IP range in <IP_ADDRESS>/8.
Adam  (airgapped)

On Nov 15, 2022, at 1:21 AM, Pure Manufacturing @.***> wrote:
Would it be possible to add a checkbox for multicast support ?
—
Reply to this email directly, view it on GitHub https://github.com/donaldzou/WGDashboard/issues/206, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANMJRYTZIH4GXVXYNJMU6K3WINBYRANCNFSM6AAAAAASAVBXOU.
You are receiving this because you are subscribed to this thread.

Thanks, but that is beyond my knowledge / capabilities, I am just looking to be able to discover over the wireguard connection.
I thought it was a case of:
PostUp = ip link set wg0 multicast on

We are 2 years further, how is the status?


update to add the Crestron controller

Crestron is a key partner and this device is being used widely.

@nenonix @JohanFreelancer9 Copy editing is needed for this PR. Thanks.

@LanaChin PR has been copyedited and is ready for final review, could you please check and merge? Thanks!