VM Bootstrap extension provisioning failure,

Is your issue related to a Jumpstart scenario, ArcBox, or HCIBox?
ArcBox
Describe the bug
I'm deploying to an empty subscription. The VM creates and the "Bootstrap" extension kicks off. However, after many minutes, it returns with a vague error. I'm not sure if the bootstrap is failing to detect that the roles install simply requires a restart, if there's an errant/unexpected hash symbol in the script, or some output contains a hash unexpectedly. Either way, it stops here.
[
{
"code": "ComponentStatus/StdOut/succeeded",
"level": "Info",
"displayStatus": "Provisioning succeeded",
"message": ".Core\Alias\r\nPSIsContainer       : False\r\nReferencedCommand   : kubectl.exe\r\nResolvedCommand     : kubectl.exe\r\nDefinition          : C:\ProgramData\chocolatey\lib\kubernetes-cli\tools\kubernetes\client\bin\kubectl.exe\r\nOptions             : None\r\nDescription         : \r\nOutputType          : {System.String}\r\nName                : kubectl\r\nCommandType         : Alias\r\nSource              : \r\nVersion             : \r\nVisibility          : Public\r\nModuleName          : \r\nModule              : \r\nRemotingCapability  : PowerShell\r\nParameters          : \r\nParameterSets       : \r\nHelpUri             : \r\nResolvedCommandName : kubectl.exe\r\nDisplayName         : kubectl -> kubectl.exe\r\n\r\n\r\nPSPath              : Microsoft.PowerShell.Core\Alias::azdata\r\nPSDrive             : Alias\r\nPSProvider          : Microsoft.PowerShell.Core\Alias\r\nPSIsContainer       : False\r\nReferencedCommand   : \r\nResolvedCommand     : \r\nDefinition          : C:\Program Files (x86)\Microsoft SDKs\Azdata\CLI\wbin\azdata.cmd\r\nOptions             : None\r\nDescription         : \r\nOutputType          : \r\nName                : azdata\r\nCommandType         : Alias\r\nSource              : \r\nVersion             : \r\nVisibility          : Public\r\nModuleName          : \r\nModule              : \r\nRemotingCapability  : PowerShell\r\nParameters          : \r\nParameterSets       : \r\nHelpUri             : \r\nResolvedCommandName : \r\nDisplayName         : azdata -> C:\Program Files (x86)\Microsoft SDKs\Azdata\CLI\wbin\azdata.cmd\r\n\r\n\r\nHubsSidebarEnabled : 0\r\nPSPath             : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge\r\nPSParentPath       : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\r\nPSChildName        : Edge\r\nPSDrive            : HKLM\r\nPSProvider         : Microsoft.PowerShell.Core\Registry\r\n\r\n\r\nHideFirstRunExperience : 1\r\nPSPath                 : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge\r\nPSParentPath           : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\r\nPSChildName            : Edge\r\nPSDrive                : HKLM\r\nPSProvider             : Microsoft.PowerShell.Core\Registry\r\n\r\nRDP port number from configuration is \r\n\r\nActions            : {MSFT_TaskExecAction}\r\nAuthor             : \r\nDate               : \r\nDescription        : \r\nDocumentation      : \r\nPrincipal          : MSFT_TaskPrincipal2\r\nSecurityDescriptor : \r\nSettings           : MSFT_TaskSettings3\r\nSource             : \r\nState              : Ready\r\nTaskName           : MonitorWorkbookLogonScript\r\nTaskPath           : \\r\nTriggers           : {MSFT_TaskLogonTrigger}\r\nURI                : \MonitorWorkbookLogonScript\r\nVersion            : \r\nPSComputerName     : \r\n\r\n\r\nActions            : {MSFT_TaskExecAction}\r\nAuthor             : Microsoft Corporation\r\nDate               : \r\nDescription        : Task for launching Initial Configuration Tasks or Server Manager at logon.\r\nDocumentation      : \r\nPrincipal          : MSFT_TaskPrincipal2\r\nSecurityDescriptor : D:P(A;;FA;;;BA)(A;;FA;;;SY)(A;;FR;;;BU)\r\nSettings           : MSFT_TaskSettings3\r\nSource             : Server Manager\r\nState              : Disabled\r\nTaskName           : ServerManager\r\nTaskPath           : \Microsoft\Windows\Server Manager\\r\nTriggers           : {MSFT_TaskLogonTrigger}\r\nURI                : \Microsoft\Windows\Server Manager\ServerManager\r\nVersion            : 1.0\r\nPSComputerName     : \r\n\r\nInstalling Hyper-V and restart\r\nWARNING: Restart is suppressed because NoRestart is specified.\r\n\r\nPath   : \r\nOnline : True\r\n\r\nWARNING: Restart is suppressed because NoRestart is specified.\r\n\r\nPath   : \r\nOnline : True\r\n\r\n\r\nSuccess       : True\r\nRestartNeeded : Yes\r\nFeatureResult : {Hyper-V, Hyper-V Module for Windows PowerShell, Hyper-V GUI Management Tools, Hyper-V Management \r\n                Tools}\r\nExitCode      : SuccessRestartRequired\r\n\r\nWARNING: You must restart this server to finish the installation process.\r\nClean up Bootstrap.log\r\nTranscript stopped, output file is C:\ArcBox\Logs\Bootstrap.log\r\n\r\n\r\n"
},
{
"code": "ComponentStatus/StdErr/succeeded",
"level": "Info",
"displayStatus": "Provisioning succeeded",
"message": "'#' is not recognized as an internal or external command,\r\noperable program or batch file.\r\n"
}
]
To Reproduce

Start Arcbox IT deployment
Deploy to an empty subscription
Allow to execute for some time, then observe failure

Expected behavior
No failure :)
Environment summary
Deployed using Azure Portal click-through.
Have you looked at the Troubleshooting and Logs section?
Yes, I reviewed the c:\arcbox\logs\bootstrap.txt log. It verbosely mirrors what was output by the Bootstrap extension. There doesn't seem to be an actual error, and no mention of the errant hash.
Screenshots
Doesn't seem necessary. The text is succinct.
Additional context
Again, clean environment. Seems to be a problem in the application provisioning within the VM.

As an update, I created a 2nd RG and had another pass - same problem, same everything.

Hi @sqlmadhadr !
I am unable to repro the issue. I've deployed it successfully in EastUS. Could you please paste the actual azuredeploy.parameters.json file you are using?
Thanks!

I went extremely simple mode and used just the portal.
{   "id": "/subscriptions/3ed56da4-39e2-47f6-b8f8-xxxxxx1b7b42/resourceGroups/lr1-sbx-arcbox-it2/providers/Microsoft.Resources/deployments/Microsoft.Template-20230423231103",   "name": "Microsoft.Template-20230423231103",   "type": "Microsoft.Resources/deployments",   "properties": {     "templateLink": {       "uri": "https://raw.githubusercontent.com/microsoft/azure_arc/main/azure_jumpstart_arcbox/ARM/azuredeploy.json",       "contentVersion": "<IP_ADDRESS>"     },     "templateHash": "2788733936666099726",     "parameters": {       "sshRSAPublicKey": {         "type": "SecureString"       },       "spnClientId": {         "type": "String",         "value": "25a24e99-bc90-42fd-b80a-XxXxXxe56622"       },       "spnClientSecret": {         "type": "SecureString"       },       "spnTenantId": {         "type": "String",         "value": "b3c62499-ad8f-41a7-a455-xXxXXxa3adc"       },       "windowsAdminUsername": {         "type": "String",         "value": "b.franklin"       },       "windowsAdminPassword": {         "type": "SecureString"       },       "logAnalyticsWorkspaceName": {         "type": "String",         "value": "lr1-sbx-arcbox-it-law2"       },       "flavor": {         "type": "String",         "value": "ITPro"       },       "githubAccount": {         "type": "String",         "value": "microsoft"       },       "githubBranch": {         "type": "String",         "value": "main"       },       "deployBastion": {         "type": "Bool",         "value": false       },       "githubUser": {         "type": "String",         "value": "microsoft"       },       "addsDomainName": {         "type": "String",         "value": "jumpstart.local"       },       "guid": {         "type": "String",         "value": "c752"       },       "rdpPort": {         "type": "String",         "value": "3389"       },       "sshPort": {         "type": "String",         "value": "22"       }     },     "mode": "Incremental",     "debugSetting": {       "detailLevel": "None"     },     "provisioningState": "Failed",     "timestamp": "2023-04-24T03:28:31.1659681Z",     "duration": "PT17M25.1933101S",     "correlationId": "15b126c9-440f-484e-9a77-d4a164d204aa",     "providers": [       {         "namespace": "Microsoft.Resources",         "resourceTypes": [           {             "resourceType": "deployments",             "locations": [               null             ]           }         ]       }     ],     "dependencies": [       {         "dependsOn": [           {             "id": "/subscriptions/3ed56da4-39e2-47f6-b8f8-9bafa31b7b42/resourceGroups/lr1-sbx-arcbox-it2/providers/Microsoft.Resources/deployments/stagingStorageAccountDeployment",             "resourceType": "Microsoft.Resources/deployments",             "resourceName": "stagingStorageAccountDeployment"           },           {             "id": "/subscriptions/3ed56da4-39e2-47f6-b8f8-9bafa31b7b42/resourceGroups/lr1-sbx-arcbox-it2/providers/Microsoft.Resources/deployments/mgmtArtifactsAndPolicyDeployment",             "resourceType": "Microsoft.Resources/deployments",             "resourceName": "mgmtArtifactsAndPolicyDeployment"           },           {             "id": "/subscriptions/3ed56da4-39e2-47f6-b8f8-9bafa31b7b42/resourceGroups/lr1-sbx-arcbox-it2/providers/Microsoft.Resources/deployments/updateVNetDNSServers",             "resourceType": "Microsoft.Resources/deployments",             "resourceName": "updateVNetDNSServers"           }         ],         "id": "/subscriptions/3ed56da4-39e2-47f6-b8f8-9bafa31b7b42/resourceGroups/lr1-sbx-arcbox-it2/providers/Microsoft.Resources/deployments/ubuntuCAPIDeployment",         "resourceType": "Microsoft.Resources/deployments",         "resourceName": "ubuntuCAPIDeployment"       },       {         "dependsOn": [           {             "id": "/subscriptions/3ed56da4-39e2-47f6-b8f8-9bafa31b7b42/resourceGroups/lr1-sbx-arcbox-it2/providers/Microsoft.Resources/deployments/stagingStorageAccountDeployment",             "resourceType": "Microsoft.Resources/deployments",             "resourceName": "stagingStorageAccountDeployment"           },           {             "id": "/subscriptions/3ed56da4-39e2-47f6-b8f8-9bafa31b7b42/resourceGroups/lr1-sbx-arcbox-it2/providers/Microsoft.Resources/deployments/mgmtArtifactsAndPolicyDeployment",             "resourceType": "Microsoft.Resources/deployments",             "resourceName": "mgmtArtifactsAndPolicyDeployment"           }         ],         "id": "/subscriptions/3ed56da4-39e2-47f6-b8f8-9bafa31b7b42/resourceGroups/lr1-sbx-arcbox-it2/providers/Microsoft.Resources/deployments/ubuntuRancherDeployment",         "resourceType": "Microsoft.Resources/deployments",         "resourceName": "ubuntuRancherDeployment"       },       {         "dependsOn": [           {             "id": "/subscriptions/3ed56da4-39e2-47f6-b8f8-9bafa31b7b42/resourceGroups/lr1-sbx-arcbox-it2/providers/Microsoft.Resources/deployments/stagingStorageAccountDeployment",             "resourceType": "Microsoft.Resources/deployments",             "resourceName": "stagingStorageAccountDeployment"           },           {             "id": "/subscriptions/3ed56da4-39e2-47f6-b8f8-9bafa31b7b42/resourceGroups/lr1-sbx-arcbox-it2/providers/Microsoft.Resources/deployments/updateVNetDNSServers",             "resourceType": "Microsoft.Resources/deployments",             "resourceName": "updateVNetDNSServers"           }         ],         "id": "/subscriptions/3ed56da4-39e2-47f6-b8f8-9bafa31b7b42/resourceGroups/lr1-sbx-arcbox-it2/providers/Microsoft.Resources/deployments/clientVmDeployment",         "resourceType": "Microsoft.Resources/deployments",         "resourceName": "clientVmDeployment"       },       {         "dependsOn": [           {             "id": "/subscriptions/3ed56da4-39e2-47f6-b8f8-9bafa31b7b42/resourceGroups/lr1-sbx-arcbox-it2/providers/Microsoft.Resources/deployments/mgmtArtifactsAndPolicyDeployment",             "resourceType": "Microsoft.Resources/deployments",             "resourceName": "mgmtArtifactsAndPolicyDeployment"           }         ],         "id": "/subscriptions/3ed56da4-39e2-47f6-b8f8-9bafa31b7b42/resourceGroups/lr1-sbx-arcbox-it2/providers/Microsoft.Resources/deployments/addsVmDeployment",         "resourceType": "Microsoft.Resources/deployments",         "resourceName": "addsVmDeployment"       },       {         "dependsOn": [           {             "id": "/subscriptions/3ed56da4-39e2-47f6-b8f8-9bafa31b7b42/resourceGroups/lr1-sbx-arcbox-it2/providers/Microsoft.Resources/deployments/mgmtArtifactsAndPolicyDeployment",             "resourceType": "Microsoft.Resources/deployments",             "resourceName": "mgmtArtifactsAndPolicyDeployment"           },           {             "id": "/subscriptions/3ed56da4-39e2-47f6-b8f8-9bafa31b7b42/resourceGroups/lr1-sbx-arcbox-it2/providers/Microsoft.Resources/deployments/addsVmDeployment",             "resourceType": "Microsoft.Resources/deployments",             "resourceName": "addsVmDeployment"           }         ],         "id": "/subscriptions/3ed56da4-39e2-47f6-b8f8-9bafa31b7b42/resourceGroups/lr1-sbx-arcbox-it2/providers/Microsoft.Resources/deployments/updateVNetDNSServers",         "resourceType": "Microsoft.Resources/deployments",         "resourceName": "updateVNetDNSServers"       },       {         "dependsOn": [           {             "id": "/subscriptions/3ed56da4-39e2-47f6-b8f8-9bafa31b7b42/resourceGroups/lr1-sbx-arcbox-it2/providers/Microsoft.Resources/deployments/stagingStorageAccountDeployment",             "resourceType": "Microsoft.Resources/deployments",             "resourceName": "stagingStorageAccountDeployment"           },           {             "id": "/subscriptions/3ed56da4-39e2-47f6-b8f8-9bafa31b7b42/resourceGroups/lr1-sbx-arcbox-it2/providers/Microsoft.Resources/deployments/mgmtArtifactsAndPolicyDeployment",             "resourceType": "Microsoft.Resources/deployments",             "resourceName": "mgmtArtifactsAndPolicyDeployment"           },           {             "id": "/subscriptions/3ed56da4-39e2-47f6-b8f8-9bafa31b7b42/resourceGroups/lr1-sbx-arcbox-it2/providers/Microsoft.Resources/deployments/updateVNetDNSServers",             "resourceType": "Microsoft.Resources/deployments",             "resourceName": "updateVNetDNSServers"           }         ],         "id": "/subscriptions/3ed56da4-39e2-47f6-b8f8-9bafa31b7b42/resourceGroups/lr1-sbx-arcbox-it2/providers/Microsoft.Resources/deployments/aksDeployment",         "resourceType": "Microsoft.Resources/deployments",         "resourceName": "aksDeployment"       }     ],     "error": {       "code": "DeploymentFailed",       "message": "At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-deployment-operations for usage details.",       "details": [         {           "code": "DeploymentFailed",           "message": "At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-deployment-operations for usage details."         }       ]     },     "validationLevel": "Template"   },   "tags": {     "marketplaceItemId": "Microsoft.Template"   } }

Hi! Thanks for all that info. I've deployed it again in EastUS and it worked. I have the following questions:

Which is the subscription type you are using? (please, share a screenshot)
Could you try to deploy it in a different subscription?
Which region are you using?
Do you have enough quota in that region?

Hi! Sorry, but I cannot reproduce your issue, my deployment was successful. Please, could you try to deploy it via Azure CLI? Thanks!

Closing due to lack of response.


Need solutions for sorting algorithm challenges in Coding Interview Prep/Algorithms

Describe your problem and how to reproduce it:
Located in the English coding challenges, under Coding Interview Prep, under Algorithms, the sorting algorithms have no solutions.
Add a Link to the page with the problem:
https://github.com/freeCodeCamp/freeCodeCamp/tree/master/curriculum/challenges/english/08-coding-interview-prep/algorithms
Tell us about your browser and operating system:

Browser Name: Chrome
Browser Version:
Operating System: Mac OS

If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box):

Forgot to mention that I'm super happy to just tackle this issue!

Feel free to add full working solutions to for these challenges.  Please put them on a single PR.  Thank you.


Document [contenthash]

Hi!
Support for a new [contenthash] template parameter was added in webpack/webpack/pull/6839, however it's not yet documented on any of:
https://webpack.js.org/configuration/output/#output-filename
https://webpack.js.org/guides/caching/#output-filenames

I will pick this one up

#2085


Add liveness/readiness/health endpoints

Add dedicated endpoints for monitoring the status of tilegroxy 1) is it up 2) is it ready to accept requests 3) has anything concerning happened.  Currently you have to hit a tile endpoint for this purpose.
Routes should be configurable and disable-able to faciliate keeping the endpoints private. Consider allowing it on secondary port.

Implemented


BCMOHAD-21366 - Allowing multiple Supplemental Team member

Description
BCMOHAD-21366 Allowing multiple Supplemental Team member added for Case and Referral
Fixes # (BCMOHAD-21366)
Type of change

[X] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[X] My code follows the style guidelines of this project
[X] I have performed a self-review of my own code
[X] I have commented my code, particularly in hard-to-understand areas
[X] I have made corresponding changes to the documentation
[X] My changes generate no new warnings
[X] I have added tests that prove my fix is effective or that my feature works
[X] New and existing unit tests pass locally with my changes
[X] Any dependent changes have been merged and published in downstream modules

@cgijeffolsen @NataliaNikishina additional Commit added to allow addition of same team member after revoking existing one if members exists already and only for PL and admin .Please Review and Merge


Update community.yml

fixed link

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

File
Status
Preview URL
Details

Community/community.yml
:warning:Warning
View
Details

Community/community.yml

Line 60: [Warning] Invalid file link: 'changing-teams-from-private-to-public-what-to-expect-in-sharepoint'.

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


bin/repl: run NodeJS REPL with initialised container

Example use:
./lib/bin/repl
Available vars: Actees, Actors, Analytics, Assignments, Audits, Auth, Blobs, ClientAudits, Comments, Configs, Datasets, Entities, FieldKeys, FormAttachments, Forms, Keys, Projects, PublicLinks, Roles, Sentry, Sessions, SubmissionAttachments, Submissions, Users, all, db, enketo, env, mail, maybeOne, maybeOneFirst, one, oneFirst, run, s3, sql, stream, with, xlsform
> await db.any(sql`SELECT * FROM blobs`)
[]

Ooh I like this idea a lot! It'd help with troubleshooting on servers.

I've got my hands full with regression testing and such, but I'll take a look at this once the release is out!


VideoCapture.get(cv2.CAP_PROR_FPS) return None

Hello, thanks for your great job.
When I used the get() method of the VideoCapture class with a FLIR camera, I got unexpected value.
>> vc = EasyPySpin.VideoCapture(0)
>> vc.set(cv2.CAP_PROP_FPS, 20)
True

# 20 is expected. But actually None is back
>> vc.get(cv2.CAP_PROR_FPS)
None

I found this,
https://github.com/elerac/EasyPySpin/blob/ea1aa5b116efb3569ca945bb7590169864262d0f/EasyPySpin/videocapture.py#L377-L380
so debugged "AcquisitionFrameRate" and "ExposureTime", but the exposure time is less than the frame time.
# debug
>> self.get_pyspin_value("AcquisitionFrameRate")
19.999350421098324  # 20fps -> frame time: 0.05sec
>> self.get_pyspin_value("ExposureTime")
15002.0 # micro sec -> 0.015 sec

I checked self.cam of VideoCapture class, but self.cam doesn't have an attribute "ResultingFrameRate". In fact, this get_pyspin_value() method called here also returns None by the following processing.
https://github.com/elerac/EasyPySpin/blob/ea1aa5b116efb3569ca945bb7590169864262d0f/EasyPySpin/videocapture.py#L632-L635
However, self.cam has "AcquisitionResultingFrameRate". Is this considered the same as the "ResultingFrameRate" in the original code ?
# debug
>> self.get_pyspin_value("AcquisitionFrameRate")
19.999350421098324
>> self.get_pyspin_value("AcquisitionResultingFrameRate")
19.999350401098972  # Approximately the same value as "AcquisitionFrameRate" is returned

Thanks for your helping

Hi @Umblife !
Thanks for your great report!
As you say, "ResultingFrameRate" returns None, and "AcquisitionResultingFrameRate" is correct.
I have completed the fix. Please check it.


checked doesn't work as expected with floating point

Seems odd that checked floating point code that overflows will quietly generate a Nan instead of throwing an exception. Needs to be documented.

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

ID: dbbcec4d-d8ff-d906-57ec-378689eb99a5
Version Independent ID: 88e4ead1-3745-2be6-9cfb-0f02eeacf9c1
Content: checked keyword - C# Reference
Content Source: docs/csharp/language-reference/keywords/checked.md
Product: dotnet-csharp
GitHub Login: @BillWagner
Microsoft Alias: wiwagn

@daveyostcom, checked applies only to arithmetic operations and conversions with integers; it does not apply to floating-point operations. I'll close this issue.

Yeah, I noticed that when I actually read all of the words. ;-)


[Text] Fix color defaults for light/dark mode

Please select one of the following

[ ] I am removing an existing difference between facebook/react-native and microsoft/react-native-macos :thumbsup:
[ ] I am cherry-picking a change from Facebook's react-native into microsoft/react-native-macos :thumbsup:
[x] I am making a fix / change for the macOS implementation of react-native
[ ] I am making a change required for Microsoft usage of react-native

Summary
Currently we are not using dynamic system colours for our text needs. Either it was hardcoded (such as RCTUITextView’s default placeholder colour) or it was implicitly using black as that’s the default for attributed strings (which you can find on slide 231 of this WWDC deck)
Changelog
[macOS] [Fixed] - Use text color defaults that respect light/dark mode settings
Test Plan
Placeholders
Before

After

Text
Before

After

Microsoft Reviewers: Open in CodeFlow

Refs #402 & #403

Hey @Simek, thanks for pointing those out! I was under the understanding that those PRs addressed different issues 🤦 Having said that, I don’t quite see why it would be bad to address this on the native side. My understanding from Apple’s messaging about this issue is that the correct way to use NSAttributedString instances in text views is to explicitly set a foreground color (see the WWDC slide in my OP).
I’m inclined to leave this as-is and focus on getting the v0.62 release out. We can always revisit this later, as it won’t be until we have v0.63 pulled in that we’ll be moving this change upstream.
I’ll have to see if #403 is still needed after this.

Alright, going for it :shipit:


Icon Type

[ ] Folder
[X] File

Folder names
No response
File names

*.deb

Graphic ideas
Official Debian logo from https://www.debian.org/logos:

https://www.debian.org/logos/openlogo-nd.svg
Maybe a box icon with the Debian logo or just a pink box
Additional context
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Added in #2694


Disable NewSessionTicket message in TLSv1.3

According to the draft:

4.6.1.  New Session Ticket Message
At any time after the server has received the client Finished
message, it MAY send a NewSessionTicket message.

In previous versions, I could use SSL_OP_NO_TICKET to disable session tickets but I can't find such option for TLSv1.3.
Is it supported and I just failed to find it?
If not, will it be supported or I should add my own code?

It isn't currently supported. There is a TODO around this in the code in ssl/statem/statem_srvr.c:
    case TLS_ST_SR_FINISHED:
        /*
         * Technically we have finished the handshake at this point, but we're
         * going to remain "in_init" for now and write out the session ticket
         * immediately.
         * TODO(TLS1.3): Perhaps we need to be able to control this behaviour
         * and give the application the opportunity to delay sending the
         * session ticket?
         */
        st->hand_state = TLS_ST_SW_SESSION_TICKET;
        return WRITE_TRAN_CONTINUE;

PRs to address this are welcome

I have seen this TODO, but it says only delay and not to totally disable so I guessed wrong that it's not relevant to me.
Should I create the PR?

Should I create the PR?

If you feel able, please go ahead. You will need to have a CLA on file before it could be accepted (but that doesn't stop you from creating it first).

Sure, I will happily do it.
Should I only add the ability to disable the NewSessionTicket or as the TODO implicates I should add the ability to delay? If so who should I get requirements from?


Fix version of nexus-staging-maven-plugin plugin to 1.6.8

This PR sets the version of nexus-staging-maven-plugin to 1.6.8 instead of using the latest version because 1.6.10 has an issue with publishing to Maven.

If we specify the version here... do we think we'll need to bump this version in the future? Or is pinning to 1.6.8 fine.

We'll remove the hardcoded version after a newer version of the nexus plugin is released fixing the bug.

/check-enforcer override


CsgSimplex.pm: fix double def of get_convergence_value

Hi, not much to review, but yes it was a double definition (survived since version 1.3 at least, apparently).
Andrey


Fix link

See here where the link is broken. I think this'll fix it.

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @steveklabnik (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. The way Github handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see the contribution instructions for more information.

I opened https://github.com/rust-lang/cargo/pull/1879 two days ago, but with no review, it didn't land. But I can review this version, bwahaha

@bors: r+

:pushpin: Commit 5cf3495 has been approved by steveklabnik

Ha. Made me laugh.

:hourglass: Testing commit 5cf3495 with merge c033770...

:sunny: Test successful - cargo-linux-32, cargo-linux-64, cargo-mac-32, cargo-mac-64, cargo-win-gnu-32, cargo-win-gnu-64, cargo-win-msvc-32, cargo-win-msvc-64


[Feature]: Refactor gh workflow

Split into multiple workflows based on function
Added build file check. Run the build command in CI to check whether the resource files are synchronized. For example, whether crd is outdated and whether it is synchronized to helm.

ref: https://github.com/zncdatadev/trino-operator/issues/199


fix(template) Bug fix in new monetary amount support + one more test

Signed-off-by: Jerome Simeon<EMAIL_ADDRESS>

Coverage remained the same at 90.874% when pulling e6d5f7d3909bbfa67fe7233d8673460fc1a6fec2 on parserv2 into a0176684874bbce65c252694b2c0910acff24706 on master.


[Fix][CI] fix the ci error of E2E-K8S-Execute

Purpose of the pull request
fix CI error

Brief change log

Verify this pull request

This pull request is code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:

(or)
If your pull request contain incompatible change, you should also add it to docs/docs/en/guide/upgrede/incompatible.md

PTAL @ruanwenjun @SbloodyS @caishunfeng @Radeity

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 40.59%. Comparing base (7b7a333) to head (ae7dc04).

Additional details and impacted files
@@            Coverage Diff            @@
##                dev   #16031   +/-   ##
=========================================
  Coverage     40.58%   40.59%
+ Complexity     5216     5215    -1
=========================================
  Files          1380     1380
  Lines         46056    46029   -27
  Branches       4916     4892   -24
=========================================
- Hits          18693    18685    -8
+ Misses        25437    25417   -20
- Partials       1926     1927    +1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

Looks like #15922 attempted to make datasource configurable but forgot to add default values of profile in values.yaml, which causes CI to fail. What about add default profile values in values.yaml?

Looks like #15922 attempted to make datasource configurable but forgot to add default values of profile in values.yaml, which causes CI to fail. What about add default profile values in values.yaml?

Sure, I've added datasource.profile in values.yaml

Update deploy/kubernetes/dolphinscheduler/README.md

Hi @ruanwenjun , would you like to help check the failed UT?

Hi @ruanwenjun , would you like to help check the failed UT?

This might cause by the
block-until-connected: 600ms

is too small


Continuous Integration

@Zuzu-Typ, I have set up basic continuous integration using Travis CI.  All the tests are passing for both a macOS and a Windows environment.
Do you have access to the Travis CI configuration?  Assuming you do, if you have the time, do you have any comments on the set up?  Would you do anything differently?
Cheers,
Matthew

I've updated the config to first test PyOgg and if it has a new version tag here on GitHub, it will build binaries for Windows, Linux and MacOS and upload them to GitHub and PyPI automatically.
I'm not sure if everything works as I would need to publish a new version to test it.
Time will tell (:
Cheers
--Zuzu_Typ--


Installation instructions for Windows

Just a note/hint: The installation instructions presented for Linux users here:
https://juglab.github.io/napari-n2v/installation.html
... also work for me on Windows. I do have an NVidia GPU though.

Great! Then I added the mention in https://github.com/juglab/napari-n2v/commit/eb889e65c12eb6721eb7a227a92bc75b785384a6.


Access Violation in debugging when attempting to read a very long string

Describe the bug
Attempting to step through reading a very long string and setting to a variable causes an "Access Violation" and the debugging stops.  This currently does not happen in VLIDE.
To Reproduce
Steps to reproduce the behavior:

Point the "Crash.lsp" to where the "ReallyBigFile.txt" is located
Start debugging "Crash.lsp" with a breakpoint on the "(setq ReallyLongString (read-line OpenFile))"
Issue the command "CrashFunc" and AutoCAD will instantly generate an access violation error and quit debugging.

Expected behavior
In VLIDE the process takes approximately 3 minutes to complete (on my system) but does not cause an access violation and continues debugging.  If that's not possible a more descriptive error would be desirable as it was very difficult to narrow down.
Screenshots

Desktop (please complete the following information):

OS: Windows 10 64-Bit
Version 21H2

Additional context
(defun c:CrashFunc ( / )
  (progn
    (setq FileName "C:\\Projects\\ReallyBigFile.txt")
    (setq OpenFile (open FileName "r"))
    (setq ReallyLongString (read-line OpenFile))
    (close OpenFile)
    (princ "Test Complete")
  )
)

ReallyBigFile.zip

This may be related to JDSComm's comment in ticket #182

This is only one way to trigger this error.  It happens so often that the debug is essentially useless to me and I still rely on VLIDE.  I'd be happy to run any tests or send any log files that might be useful for this.

See the attached file.
First to get VSCode working again perform the steps in "SOLUTION 2".
Then, If this ever happens again, all you have to do is "SOLUTION 3" or "SOLUTION 3 Update".
Hope this works for you as well.
I was about to give up on VSCode because of this but now I'm not having any issues with it.
VSCode - Unwind skipped on exception error if breakpoint in code.txt


Kibana Customization - Cannot replace icons that have euiIcon class

I am trying to use custom brandings and I could replace quite a lot of assets but I am not able to change the Kibana icons that appear at places where euiIcon or related classes are used.

@dhanesh95 please do follow this.

We are doing some "spring cleaning in the fall", and to make sure we focus our energies on the right issues and we get a better picture of the state of the repo, we are closing all issues that we are carrying over from the ODFE era (ODFE is no longer supported/maintained, see post here).
If you believe this issue should still be considered for current versions of OpenSearch, apologies! Please let us know by re-opening it.
Thanks!


More initial docs

Here:

a little more structure
started porting a couple of section of the Readme (with jbang checks etc.)
ported the initial Blog we wrote for Java Advent

Next:

more structure
a more scalable way to test the docs
port the rest of the Readme

Going to see why cloudflare didn't build this preview branch. I suspect because because this is a fork.

Probably the preview doesn't work on PRs from forks.
I think you can trust me this time as it's really an in progress work, I'll push to the main repo next time.

I don't see the site being updated after the merge, @bhelx I think I need your intervention here 🙏

Seems that the build failed because some updates to yarn.lock weren't checked in. will see if i can fix:
<pre class="c_np c_bv c_mo c_mp c_hp c_hq c_dd c_qv c_qw c_qx c_qy c_gp c_gq c_qj c_bx c_qz">
15:55:49.937 | ➤ YN0000: └ Completed in 0s 241ms
-- | --
15:55:50.000 | ➤ YN0000: ┌ Post-resolution validation
15:55:50.000 | ➤ YN0028: │ The lockfile would have been modified by this install, which is explicitly forbidden.
15:55:50.000 | ➤ YN0000: └ Completed
15:55:50.000 | ➤ YN0000: Failed with errors in 0s 313ms
15:55:50.021 | Error: Exit with error code: 1
15:55:50.021 | at ChildProcess.<anonymous> (/snapshot/dist/run-build.js)
15:55:50.022 | at Object.onceWrapper (node:events:652:26)
15:55:50.022 | at ChildProcess.emit (node:events:537:28)
15:55:50.022 | at ChildProcess._handle.onexit (node:internal/child_process:291:12)
15:55:50.030 | Failed: build command exited with code: 1
15:55:51.490 | Failed: error occurred while running build command

I had to delete yarn.lock. should be deployed and working again.

Looks good! Thanks for looking into this quickly and sorry for the noise.
We should put yarn.lock in the .gitignore file, I'll follow up tomorrow.


drbg: allow the ctr derivation function to be disabled in FIPS mode

Word from the lab is:

The use of the derivation function is optional if either an approved RBG or an entropy source provides full entropy output when entropy input is requested by the DRBG mechanism. Otherwise, the derivation function shall be used.

So our disallowing it's use was more than required.
Note that the use of the derivation function remains on by default.

[x] documentation is added or updated
[x] tests are added or updated

Second opinion may be required.

If we hadn't mis-interpreted the standards, this would have been included for sure.
It also simplifies the code a little.

Given this removes a public macro it might be better to formally ACK it by OTC.

Removing stuff like this requires OTC signoff. You could have implemented without removal - although removal is probably the right choice. But when we take away header file visible items post-beta it needs OTC approval.

Leaving the newly introduced error message around but unused is a fallback I guess.  It didn't seem all that sensible.

24 hours has passed since 'approval: done' was set, but as this PR has been updated in that time the label 'approval: ready to merge' is not being automatically set.  Please review the updates and set the label manually.

OTC: This PR is ok to merge.

merged.


EASEY UI: Global Navigation

Tasks

[x] Develop a plan and a layout that shows where the EASEY-In platform will live on epa.gov and how users of both EASEY-In and -Out will navigate between the two platforms.

Outcomes

[x] Visual artifact resolving EASEY navigation
[x] Internal review with EPA PO

@karenhwwoo and @MoAdeyoju — Here's the global navigation user path document for your review: https://xd.adobe.com/view/f1f6e252-0782-4bd0-9f91-b78d4d5877d0-a4a5/
This document shows the two main paths a user would take to "end up" where we are in the wireframes (EASEY-In Dashboard > Workspace > Monitoring Plans). It also gives a draft outline of some of the levels and steps along the way. I'm hoping it will help start the conversation about the interplay between the two apps and where they live in the EPA ecosystem.
Please feel free to reach out with questions or you can comment directly in the XD document.
CC @staceyrenner

Looks good to me, @cvp-alexrobinson but I will defer to @karenhwwoo for more specific feedback. Lets plan to show (or discuss with) @chrisgitsit and @ibarra-michelle the WIP during the UX weekly meeting on 12/14

Thanks, @MoAdeyoju

This document has been uploaded to Teams under TheEmissioners > 00 Miscellaneous > EPA EASEY Suite User Paths.pdf


feat(codec): Configure max request message size

Motivation
In gRPC specs, by default there is a limit for the length of messages(4MB). Actually, Tonic Codec doesn't  set a limit which could cause security concerns. If an attacker decides to send us heavy messages, It'll be decoded and could fill all available RAM.
See #1097
Solution
Support changing the max message size via a configuration. Set the limit to 4MB by default.
resolves #1097

Hi @aoudiamoncef,
I have an issue with tonic-build client, I added the two parameters to the client config, but I got an error when I tried to add it in the generator side.

@aoudiamoncef commented I think those two lines in the client.rs of tonic-build need to just remove the self.inner = part and it should work?

@aoudiamoncef commented I think those two lines in the client.rs of tonic-build need to just remove the self.inner = part and it should work?

I tired a couple of things without success. It's strange, as we have similar code above

@aoudiamoncef I think you need to call the fn on Grpc?
Like this

@aoudiamoncef I think you need to call the fn on Grpc?

 In my head, it's was the same integration as the server.rs

Also you will need to rebase your branch and run cargo test --all and commit the generated code for the sub libraries.

I wrote some instructions here https://github.com/hyperium/tonic/blob/master/CONTRIBUTING.md#generated-code

@LucioFranco, I corrected all the typos, tests passes locally and I tested the new feature in my projet with success 💯

The CI is green https://github.com/hyperium/tonic/actions/runs/4198616103
I just rebased from master to include the changes in the contributing file.

hi @LucioFranco, sorry for bother you in a merged PR, here's I want to ask a short but essential question.  I want to know does this change have any document or explain about how I can configure when I create an tonic grpc client?

I'll try to write an example to show the usage of this feature


Add integration tests for IP-per-Task support

This wasn't done at the time that IP-per-Task support was added, because it wasn't clear how to start a Mesos cluster with IP-per-Task support.
Since DC/OS will ship with overlay networking out of the box, we should make sure that this functionality is covered by a Marathon or a DC/OS integration test.

Pretty sure that someone wrote a dc/os integration test for this. I've forwarded this to Avinash for feedback

https://github.com/dcos/dcos/commit/1ad4d55979c342a5da21bde57f3dba4176f500a6

Note: This issue has been migrated to https://jira.mesosphere.com/browse/MARATHON-2043. For more information see https://groups.google.com/forum/#!topic/marathon-framework/khtvf-ifnp8.

Note: This issue has been migrated to https://jira.mesosphere.com/browse/MARATHON-2043. For more information see https://groups.google.com/forum/#!topic/marathon-framework/khtvf-ifnp8.


BCStyle default lookup table is wrong

BCStyle contains
DefaultLookUp.put("jurisdictionCountry", JURISDICTION_C);
DefaultLookUp.put("jurisdictionState", JURISDICTION_ST);
DefaultLookUp.put("jurisdictionLocality", JURISDICTION_L);

but this is wrong, the keys has to be lowercase jurisdictioncountry instead of jurisdictionCountry,...
I tested a simple fix in my application with
    public static class MyStyle extends BCStyle {

        public MyStyle() {
            super();
            this.defaultLookUp.put("jurisdictioncountry", JURISDICTION_C);
            this.defaultLookUp.put("jurisdictionstate", JURISDICTION_ST);
            this.defaultLookUp.put("jurisdictionlocality", JURISDICTION_L);
        }

    }

whcih works perfectly. all ohter default lookups are lowercase only the 3 jurisitcations are not.
the probm is the IETFUtils decodeAttrName whcih seams to not work wrok if the lookup contains upcates chars
public class ScratchTest {

    @Test
    void myStyle() { // this works
        var name1 = new MyStyle().attrNameToOID("jurisdictionstate");
        Assertions.assertNotNull(name1);
        var name2 = new MyStyle().attrNameToOID("jurisdictionState");
        Assertions.assertNotNull(name2);
    }

    @Test // this fails
    void bcStyle() {
        var name = BCStyle.INSTANCE.attrNameToOID("jurisdictionstate");

        Assertions.assertNotNull(name);
    }

    public static class MyStyle extends BCStyle {

        public MyStyle() {
            super();
            this.defaultLookUp.put("jurisdictioncountry", JURISDICTION_C);
            this.defaultLookUp.put("jurisdictionstate", JURISDICTION_ST);
            this.defaultLookUp.put("jurisdictionlocality", JURISDICTION_L);
        }

    }
}

`

Thanks for the report. Now fixed, should appear on github shortly and in the next beta release.


delivery report timestamps are incorrect

delivery report timestamps should reflect the time the message was produced but they are @ some time during the year 1970. The problem is the timestamp is being errantly dividing 1000 in the Producer.DeliveryReportCallbackImpl method. Timestamps actually produced to Kafka are correct.

same problem on the consumer (SafeKafkaHandle.ConsumerPoll) - the unix millisecond time returned by kafka is interpreted as seconds.. and then this value interpreted as milliseconds. Remove / 1000 to fix.

resolved in master


Add etcd filestore

Heavily based on the LevelDB2 filestore code, just changed the KV store from LevelDB to etcd.
For now, there's no SSL support, but may be added some day.
Hope it helps.

somehow the build failed

@divinerapier this seems related to go mod https://github.com/chrislusf/seaweedfs/pull/1021 maybe you can help a bit?


Revisit handling of default priors

Default priors are currently handled by small helper functions that have custom names. This seems surprisingly clunky given the rest of the code base.
Whilst I agree default priors in structs could be dangerous in the hands of some users I also think providing opinionated priors can be very helpful and also guide practice.
Personally I would vote for default priors in the structs but open to other suggestions?

My view is that if we can close #133 in such a way that all priors have defaults for their constructor; then this is closed too.

I think this is now resolved? (checked and yes)


Outlook 2000/2003 Retina Background Not Working

Versions 2000, 2002, 2003 of Outlook don't seem to be scaling the background image to half the width.

Hi Thomas,
Retina background works fine in Outlook 2003, I just re-tested to make sure. Acorn isn't tested with Outlook 2000/2002 though, so they're not listed in the compatibility table. There are no plans to support those clients.
Here's a quick render test, compared to how it looks like in Apple Mail for reference. I used a 1200x800 background image with the default background image example, which is a 600x400 container. As you can see, the image fits as expected in Outlook 2003.
Outlook 2003

Apple Mail

Code used
I only changed the image source in the default example:

Overlayed Text

CAN BE ANY HTML YOU NEED


How to Schedule ModelSaver after X iterations not X epochs?

I'm trying to use the ILSVRC 2012 dataset on Tensorpack and I want to see Tensorboard image summaries while the network is learning but since there are so many images I can't wait for PeriodicCallback to call ModelSaver() after each epoch and I want to check the outputs every X iterations (for example after a hundred iterations).
is this possible?

You can use
step_per_epoch=500

Then the callbacks will be trigger. This is also related to #39

Great! Thanks...
by the way, I wanted to use steps_per_epoch so that I could see the image summaries in Tensorboard but this ends up pretty costly... for example after every 5 epochs the logfile events.out.tfevents.148441180.... gets updated with the summaries but we also end up with huge model files like model-5.data-00000-of-00001 which is in my case a 670MB file... now this gets repeated and after 10 epochs we have 10x670MB less storage...
can we update the summaries just fine while just overwriting the model file so that in the end we end up with one model instead of one for every step of the way?

How many images do you want to dump after each epoch?
I use something related in my private examples to generate an animation from image files.
There is a small writeup how I export Images directly to JPEG without tf.summary in  OnlineExporter. There are two ways:

preload some images
use another dataflow instance

@Neltherion You can use for example PeriodicCallback(ModelSaver(), 10) to let ModelSaver get triggered less frequently.
A better solution will be there after step-callbacks are ready.

A better solution will be there after step-callbacks are ready.

Then I'll be waiting... Thanks!

@Neltherion  Now you can use PeriodicTrigger(ModelSaver(), every_k_steps=100, every_k_epochs=1) to trigger the saver every epoch, and also every 100 steps (the counter was reset every epoch).
Also, ModelSaver has some other options to automatically delete old checkpoints to save disk space.


findMany with a select argument errors out with models with self-relations (sometimes)

Bug description
The "sometimes" is dependent on the order of scalars with respect to the self relation in the select argument. Details follow.
@kunovsky originally discovered this in their schema, I've managed to narrow down the problem.
How to reproduce

In a new folder, place this schema:

generator client {
  provider = "prisma-client-js"
}

datasource db {
  provider = "postgresql"
  url      = "postgresql://siddhant@localhost:5432/throwaway"
}

model User {
  id                  String   @default(cuid()) @id
  createdAt           DateTime @default(now())
  updatedAt           DateTime @updatedAt
  updatedBy           String?
  updatedByUser       User?    @relation("UserUpdatedByToUser", fields: [updatedBy], references: [id])
  active              Boolean  @default(true)
  email               String   @unique
  name                String?
  registryAccessToken String   @unique
  User                User[]   @relation("UserUpdatedByToUser")
}

(Note that the User field was automatically added by the VSCode extension)

Run prisma migrate save --experimental && prisma migrate up --experimental
In an index.ts file in the folder, paste this:

Expand
import { PrismaClient } from "@prisma/client";

const prisma = new PrismaClient();

const main = async () => {
  console.log(
    await prisma.user.create({
      data: {
        email<EMAIL_ADDRESS>        registryAccessToken: "",
      },
    })
  );

  console.log(
    await prisma.user.findMany({
      first: 100,
      select: {
        updatedBy: true,
        updatedByUser: true,
        active: true,
      },
    })
};

main()
  .catch(async (e) => console.log(e))
  .finally(async () => await prisma.disconnect());

Run the script using ts-node index.ts.
You should see this error:

PrismaClientUnknownRequestError:
Invalid `prisma.user.findMany()` invocation in
/Users/siddhant/Code/Tests/tmp/index.ts:16:23

  12   })
  13 );
  14 console.log(
→ 15   await prisma.user.findMany(Attempted to serialize scalar 'null' with incompatible type 'String'
    at PrismaClientFetcher.message (/Users/siddhant/Code/Tests/tmp/node_modules/@prisma/client/src/runtime/getPrismaClient.ts:649:46)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)

Okay I needed you to copy & paste the script above because the issue seems to only happen when a scalar field is after the self-relation in the select argument. Yeah...
A few other things of value:

If you remove the select argument entirely, then the script does not crash
If you remove the select.updatedByUser argument, then the script does not crash
If you remove the select.updatedBy argument, then the script does not crash
If you move the select.registryAccessToken argument above the select.updatedByUser argument, then the script does not crash :P
If you replace select.registryAccessToken with select.name or select.active, then the script DOES crash, albeit with a different error message (it looks similar though).
This only happens with self-relations. I tried doing the same thing with two models and they behave as expected.

Here are the GraphQL queries generated:

For select: { updatedBy: true, updatedByUser: true, active: true } (Crashes)

query {
  findManyUser(first: 100) {
    updatedBy
    updatedByUser {
      id
      createdAt
      updatedAt
      updatedBy
      active
      email
      name
      registryAccessToken
    }
    active
  }
}

For select: { updatedBy: true, updatedByUser: true, active: true } (Scalar before relation, does not crash)

query {
  findManyUser(first: 100) {
    updatedBy
    active
    updatedByUser {
      id
      createdAt
      updatedAt
      updatedBy
      active
      email
      name
      registryAccessToken
    }
  }
}

For select: { updatedBy: true, active: true } (Removed relation, does not crash)

query {
  findManyUser(first: 100) {
    updatedBy
    active
  }
}

Expected behavior

The script should not crash
The order of select arguments should not determine if the script crashes or not

Environment & setup

OS: macOS
Database: Postgres
Prisma version:

@prisma/cli          : 2.0.0-beta.5
Current platform     : darwin
Query Engine         : query-engine 0c2ec197653b278b2978845ef958db88824cd82e
Migration Engine     : migration-engine-cli 0c2ec197653b278b2978845ef958db88824cd82e
Introspection Engine : introspection-core 0c2ec197653b278b2978845ef958db88824cd82e
Format Binary        : prisma-fmt 0c2ec197653b278b2978845ef958db88824cd82e

Node.js version: v12.16.3

Thanks for the detailed write up Sid! I can confirm this.

Please add the SQL to the issue, so usage of Migrate is not required to reproduce this.

CREATE TABLE "public"."User" (
"active" boolean  NOT NULL DEFAULT true,"createdAt" timestamp(3)  NOT NULL DEFAULT CURRENT_TIMESTAMP,"email" text  NOT NULL ,"id" text  NOT NULL ,"name" text   ,"registryAccessToken" text  NOT NULL ,"updatedAt" timestamp(3)  NOT NULL ,"updatedBy" text   ,
    PRIMARY KEY ("id"))

CREATE UNIQUE INDEX "User.email" ON "public"."User"("email")

CREATE UNIQUE INDEX "User.registryAccessToken" ON "public"."User"("registryAccessToken")

ALTER TABLE "public"."User" ADD FOREIGN KEY ("updatedBy")REFERENCES "public"."User"("id") ON DELETE SET NULL  ON UPDATE CASCADE

Fixed with 2.0.0-alpha.1205 onwards.


Implement traffic light detection.

Traffic Light Detection and Recognition
🚦 Implement traffic light detection. Using the camera vision on the front view of the AEVX, detect traffic lights, recognize the traffic light, and behave as the traffic light giving orders.  🚦 📷 🚗

The traffic light algorithm must be tested well on the field and check if the traffic light behaves properly and if the algorithm is stable or not. 🚦 🚦 🚦


move tooltip when no space is left on the screen to opposite side of cusor

Moves the tooltip so it can no longer land under the mouse.
fixes #1683
And it looks something like this:

I would prefer it to keep the links to the right always like they currently are done instead of flipping them to the right when there's no space.
Like this:
https://i.nuuls.com/2mLX9.mp4

I updated the behaviour and updated the gif in the original post. Now it will stick to the right like before but flip up once no space is left

Could you reduce the blinking/switching behavior while viewing the same link.
Like make it not use the position of sticking middle of toolbar side to the mouse? But again, questionable, could use sides if not much vertical space.
To preferably use corners, on no space slide on bottom/top side of toolbar?
Also not to render if no space at current chosen position.

I could look into that in a seperate PR. The way tooltips are rendered and updated would probably have to reworked quite a bit.


fix: Fix bug with equipment group survey scaling

Pull Request Key Information
Reason for change
Survey times and cost were not being properly proportionally propagated down when using equipment groups. This resulted in inflated survey times and costs when using equipment groups.
What was changed
Survey times and costs are now properly scaled down when using equipment groups. This is done by scaling the survey times and costs of the equipment group by the number of equipment groups.
Intended Purpose
Equipment group survey times and costs are now fixed and properly functioning.
Level of version change required
Patch to next patch version
Testing Completed
Manual testing.
All unit tests passing:
unit_test_results.txt
Target Issue
N/A
Additional Information
N/A

Manual testing after rebase remained successful
Unit testing after rebase all passes:
unit_test_results.txt


Fix OpenBSD service checks

This puts back the change that 159b463a reverted to use rcctl as the enabled check didn't work at all for any service I've tried on 5.7. However the invocation should be rcctl get foo status rather than rcctl status foo.

@vxnick How do you think about this PR ? I'm afraid this PR does not work with the versions prior to 5.7.

If it's possible to make it work on < 5.7 and >= 5.7 then I'm happy to do that, however I checked an older 5.6 host and none of the /etc/rc.d/* scripts respond to status there either so I'm not sure where the logic came from.

If it's possible to make it work on < 5.7 and >= 5.7 then I'm happy to do that

Please use the code supporting Fedora as a reference.
https://github.com/mizzy/specinfra/tree/master/lib/specinfra/command/fedora

however I checked an older 5.6 host and none of the /etc/rc.d/* scripts respond to status there either so I'm not sure where the logic came from.

@vxnick, How about this ? I appreciate if you answer this question.

Done. I've tested my fork with a 5.7 VM and the service checks work there so I think I got the logic right.
I'm happy to add tests for these however I couldn't work out how to write working ones for the check_is_{enabled,running}() methods, I couldn't see any examples of them for other platforms in the existing tests.

Thanks!

I'm happy to add tests for these however I couldn't work out how to write working ones for the check_is_{enabled,running}() methods, I couldn't see any examples of them for other platforms in the existing tests.

Please use these tests as references.
https://github.com/mizzy/specinfra/blob/master/spec/command/redhat/service_spec.rb
https://github.com/mizzy/specinfra/blob/master/spec/command/redhat7/service_spec.rb

Yeah, I saw those tests for testing how a service is actually started/stopped but I couldn't see any example of how to test that when I have something like this in my serverspec:
describe service('httpd') do
  it { should be_enabled }
end

That the commands that get run are e.g. rcctl get httpd status on OpenBSD 5.7+. I tried to add a test like this:
describe get_command(:check_service_is_running, 'httpd') do
  it { should eq 'rcctl get httpd status' }
end

but I couldn't get that or any variant to work. Is that something that should work?

Ah, I see the Specinfra::Command::Module::Service::* modules. Presumably if I add something like Specinfra::Command::Module::Service::Rcctl and refactor to use that then I can add some tests to spec/command/module/service/rcctl_spec.rb.
I've just realised, actually enabling/disabling/starting/stopping services probably doesn't work on OpenBSD as if I understand correctly it will try and use chkconfig & service which are used by the init service module and they don't exist on OpenBSD. There are more rcctl options to do all of that so I will add those and some tests.

Modules under Specinfra::Command::Module::Service::* are used in wide variety of OSes/distributions, but rcctl is only used in OpenBSD 5.7, isn't it ? So you should not create Specinfra::Command::Module::Service::Rcctl .

Only you have to do is add specs like this commit.
https://github.com/mizzy/specinfra/commit/4abc33d177ca118815ba8eeae12a4e66e59e6764

I'm sure I tried that but it didn't work, however it works fine now :smile:

:+1:

Released as v2.42.1.


fix(gopls): networking mode depending on runtime

Fixes the networking part of #68

Yes, slirp4netns is the default value for rootless containers and bridge is the default for rootful containers according to the podman man page.

Got it - okay cool. I recently installed podman and am starting to play to understand how it works. Now that I have a better idea already I think I can make sense of this. I also wanted to note this ticket: https://github.com/lspcontainers/lspcontainers.nvim/issues/84 which should address these types of settings easier.


Add insertReturnId() for databases that support lastInsertId().

@duskwuff does this look sane?

This will target v2.5.0, the other changes today can either be released earlier as v2.4.1 or we can just do v2.5.0 all at once.

This new API is disabled for PostgreSQL. We can disable it for other drivers if need be, down the line. I'm going to tag/sign 2.5.0 today.


FIX Don't try to save blocks in a readonly elemental area

Turns out when the field is read-only we don't have the schema data - but even if we did, we shouldn't try to save data for a read-only field.
Note this fixes two separate issues - please test both of them to ensure the fix works as expected in both scenarios.
Issues

https://github.com/silverstripe/silverstripe-elemental/issues/1290
https://github.com/silverstripe/silverstripe-versioned-admin/issues/378

Tested both scenarios, both are fixed by this PR

Hi Guy,
this mr fixed an issue I had with the combination of elemental and advanced-workflow, where clicking the approve button failed with a JS error in the onbeforesubmitform hook, due to the form being readonly.
However I wonder if the onmatch hook needs the same treatment: it is triggering the same problem (accessing the the data-schema attribute, which is absent in the readonly form), hence showing an error in the console, though not having any negative impact on submitting of the form.
Andy

I wonder if the onmatch hook needs the same treatment: it is triggering the same problem (accessing the the data-schema attribute, which is absent in the readonly form), hence showing an error in the console, though not having any negative impact on submitting of the form.

If there's no actual problem other than an error in the console log, then yes technically it is a bug that should be fixed but the priority is too low for me to personally create a PR for it.


FR : Capture text snippets

Hello
i'have tested this code
`from machine.plugins.base import MachineBasePlugin
from machine.plugins.decorators import process
class testevents(MachineBasePlugin):
@process("file_created")
def testFileUploadDetection(self, event):
self.say('ok')`
and nothing happen when added a file to my slack team

Hello
I've made it work  , but i needed to import slack client , which is not optimal
here is the code of my plugins , can you help me doing everythong with slack machine ?
class testevents(MachineBasePlugin):     @process("file_shared")     def testFileUploadDetection(self, event):         token = self.settings['SLACK_API_TOKEN']         sc = SlackClient(token)         snippet_id = event['file_id']         request = sc.api_call("files.info", file=snippet_id)         if request['ok']:             titre = request['file']['title']             text = request['file']['preview']             contenu = request['content']             #commentaire = request['comments']             self.say('general', titre + ' ' + ' ' +                      text + ' ' + contenu)

You will only ever get the 'preview' from the files.info.
The full 'preview' contents are actually sent via a 'Message" event that looks like this.
The distinguishing factor is that it will have a files list in the event.
   'type':'message',
   'text':'',
   'files':[
      {
         'id':'FJ4MJEBE1',
         'created':1556079783,
         'timestamp':1556079783,
         'name':'-.pl',
         'title':'Untitled',
         'mimetype':'text/plain',
       ----cut-----

So you could have a generic watch on message types, query for files inside, and pull the preview from there, but the preview will be just that, a small preview.   If you want the full file, then you will need to get the file, at the url in url_private_download field in the event data.
You will need to fetch it with something like requests, and provide the slack api token in the header.
Here is a snip of how I do it
            _req = requests.get(
                _file_external_url,
                allow_redirects=True,
                headers={"Authorization": f"Bearer {self.settings['SLACK_API_TOKEN']}"},
            )
            if _req.status_code != 200:
                raise NotFoundError(
                    "Unable to get file from Slack - {_req.status_code}"
                )
           _body = _req.text

_body is the actual raw contents of the snippet.
It could be implemented as a special feature of slack-machine I suppose, but until then, this could be a workable solution for you.
FYI - in my use case, when the user is about to send a snippet for the bot to work on, I just also have them put in the "Add Message" box, a respond_to / listen_to trigger phrase.   That way I don't have to setup special event processing, I just use respond_to / listen_to, and the files collection will be in the message._msg_event['files'] list.

Hi
Thx for your answer , it helps me a lot
Here is the final code for the moment , i wiil plug it later with a sms alerting system
class testevents(MachineBasePlugin):     @listen_to(r"alerte")     def testAlertmsg(self, msg):         testFile = msg._msg_event.get('files', None)         if testFile is not None:             for f in msg._msg_event['files']:                 if f['mode'] == "snippet":                     _file_external_url = f['url_private']                     titre_snip = f['title']                     token = self.settings['SLACK_API_TOKEN']                     _req = requests.get(_file_external_url,                                         allow_redirects=True,                                         headers={                                             'Authorization': 'Bearer ' + token}                                         )                     if _req.status_code != 200:                         raise ValueError(                             "Unable to get file from Slack - " +                             {_req.status_code}                         )                     texte_snip = _req.text                     print(titre_snip + ' ' + texte_snip)


Not every keras.metrics.* accept from_logits=True

System information

Have I written custom code: Yes
OS Platform and Distribution: Linux Ubuntu 18.04.3
TensorFlow installed from: binary (Docker Image tensorflow:2.3.0-gpu)
TensorFlow version: v2.3.0-rc2-23-gb36436b087 2.3.0
Python version: 3.6.9
CUDA/cuDNN version: CUDA10.2
GPU model and memory: RTX 2080 8GB

Describe the current behavior
The issue is the same as described by MeghnaNatraj in ticket 37103. The mentioned ticket states the problem has been solved. I was requested to open a new ticket.
If I have a model with an output layer of one neuron and 'sigmoid' activation function and using BinaryCrossentropy(from_logits=False), then the model.fit() function accepts any metrics (e.g. Precision)
If I have the same model as before but without activation function and BinaryCrossentropy(from_logits=True), then model.fit() function will return an error.
Describe the expected behavior

Having a model, which has an output layer without an activation function: keras.layers.Dense(1) # Output range is [-inf, +inf]
Loss function of the model working with logits: BinaryCrossentropy(from_logits=True)
Accepting metrics during fitting like keras.metrics.Precision

Standalone code to reproduce the issue
I have copied the same test code by MeghnaNatraj in ticket 37103
# INITIALIZE

import tensorflow as tf
import numpy as np
# define dataset
dataset = np.array([[6,148,72,35,0,33.6,0.627,50,1],
[1,85,66,29,0,26.6,0.351,31,0],
[8,183,64,0,0,23.3,0.672,32,1],
[1,89,66,23,94,28.1,0.167,21,0],
[0,137,40,35,168,43.1,2.288,33,1]])
# split into input (X) and output (y) variables
X = dataset[:,0:8]
y = dataset[:,8]

# WORKS: Model output is in range [0, 1]
# define the keras model
model = tf.keras.models.Sequential([tf.keras.layers.Dense(12, input_dim=8, activation='relu'),
                                    tf.keras.layers.Dense(1, activation='sigmoid')])
# compile the keras model
model.compile(loss=tf.keras.losses.BinaryCrossentropy(),
              optimizer=tf.keras.optimizers.RMSprop(),
              metrics=[tf.keras.metrics.Accuracy(name='accuracy'),
                       tf.keras.metrics.Precision(name='precision'),
                       tf.keras.metrics.TruePositives(name='tp')])
# fit the keras model on the dataset
model.fit(X, y, epochs=10, batch_size=10, verbose=0)

# DOES NOT WORK: Model output is in range [-inf, inf]
# define the keras model
model = tf.keras.models.Sequential([tf.keras.layers.Dense(12, input_dim=8, activation='relu'),
                                    tf.keras.layers.Dense(1)])
# compile the keras model
model.compile(loss=tf.keras.losses.BinaryCrossentropy(from_logits=True),
              optimizer=tf.keras.optimizers.RMSprop(),
              metrics=[tf.keras.metrics.Accuracy(name='accuracy'),
                       tf.keras.metrics.Precision(name='precision'),
                       tf.keras.metrics.TruePositives(name='tp')])
# fit the keras model on the dataset
model.fit(X, y, epochs=10, batch_size=10, verbose=0)

InvalidArgumentError: 2 root error(s) found.
  (0) Invalid argument:  assertion failed: [predictions must be <= 1] [Condition x <= y did not hold element-wise:] [x (sequential_8/dense_17/BiasAdd:0) = ] [[22.0911655][62.7297783][35.2793274]...] [y (metrics/precision/Cast_3/x:0) = ] [1]
	 [[{{node metrics/precision/assert_less_equal/Assert/AssertGuard/else/_11/Assert}}]]
	 [[metrics/tp/assert_greater_equal/Assert/AssertGuard/pivot_f/_31/_61]]
  (1) Invalid argument:  assertion failed: [predictions must be <= 1] [Condition x <= y did not hold element-wise:] [x (sequential_8/dense_17/BiasAdd:0) = ] [[22.0911655][62.7297783][35.2793274]...] [y (metrics/precision/Cast_3/x:0) = ] [1]
	 [[{{node metrics/precision/assert_less_equal/Assert/AssertGuard/else/_11/Assert}}]]
0 successful operations.
0 derived errors ignored. [Op:__inference_distributed_function_12253]

Function call stack:
distributed_function -> distributed_function

Traceback (most recent call last):
  File "<stdin>", line 2, in <module>
  File "/usr/local/lib/python3.6/dist-packages/tensorflow/python/keras/engine/training.py", line 108, in _method_wrapper
    return method(self, *args, **kwargs)
  File "/usr/local/lib/python3.6/dist-packages/tensorflow/python/keras/engine/training.py", line 1098, in fit
    tmp_logs = train_function(iterator)
  File "/usr/local/lib/python3.6/dist-packages/tensorflow/python/eager/def_function.py", line 780, in __call__
    result = self._call(*args, **kwds)
  File "/usr/local/lib/python3.6/dist-packages/tensorflow/python/eager/def_function.py", line 840, in _call
    return self._stateless_fn(*args, **kwds)
  File "/usr/local/lib/python3.6/dist-packages/tensorflow/python/eager/function.py", line 2829, in __call__
    return graph_function._filtered_call(args, kwargs)  # pylint: disable=protected-access
  File "/usr/local/lib/python3.6/dist-packages/tensorflow/python/eager/function.py", line 1848, in _filtered_call
    cancellation_manager=cancellation_manager)
  File "/usr/local/lib/python3.6/dist-packages/tensorflow/python/eager/function.py", line 1924, in _call_flat
    ctx, args, cancellation_manager=cancellation_manager))
  File "/usr/local/lib/python3.6/dist-packages/tensorflow/python/eager/function.py", line 550, in call
    ctx=ctx)
  File "/usr/local/lib/python3.6/dist-packages/tensorflow/python/eager/execute.py", line 60, in quick_execute
    inputs, attrs, num_outputs)
tensorflow.python.framework.errors_impl.InvalidArgumentError: 2 root error(s) found.
  (0) Invalid argument:  assertion failed: [predictions must be <= 1] [Condition x <= y did not hold element-wise:] [x (sequential/dense_1/BiasAdd:0) = ] [[28.8497276][37.4658966][48.6209221]...] [y (Cast_5/x:0) = ] [1]
         [[{{node assert_less_equal/Assert/AssertGuard/else/_11/assert_less_equal/Assert/AssertGuard/Assert}}]]
         [[assert_less_equal_1/Assert/AssertGuard/pivot_f/_41/_81]]
  (1) Invalid argument:  assertion failed: [predictions must be <= 1] [Condition x <= y did not hold element-wise:] [x (sequential/dense_1/BiasAdd:0) = ] [[28.8497276][37.4658966][48.6209221]...] [y (Cast_5/x:0) = ] [1]
         [[{{node assert_less_equal/Assert/AssertGuard/else/_11/assert_less_equal/Assert/AssertGuard/Assert}}]]
0 successful operations.
0 derived errors ignored. [Op:__inference_train_function_1165]

Was able to reproduce the issue with TF v2.2, TF v2.3 and TF-nightly. Please find the attached gist. Thanks!

any one is working on this?

Would also like to know if there is any progress on this issue.

Looking at the source code for tf.keras.metrics.Precision, one can see that there is an assertion that thresholds are between 0 and 1. See trail of links below:
https://github.com/tensorflow/tensorflow/blob/4ef28c5f287cd0a96daad3e7634b570de7e1f496/tensorflow/python/keras/metrics.py#L1256
https://github.com/tensorflow/tensorflow/blob/4ef28c5f287cd0a96daad3e7634b570de7e1f496/tensorflow/python/keras/utils/metrics_utils.py#L178
https://github.com/tensorflow/tensorflow/blob/4ef28c5f287cd0a96daad3e7634b570de7e1f496/tensorflow/python/keras/utils/metrics_utils.py#L169
https://github.com/tensorflow/tensorflow/blob/4ef28c5f287cd0a96daad3e7634b570de7e1f496/tensorflow/python/keras/utils/metrics_utils.py#L171
Further to change this, it seems like there has to be made a change here: https://github.com/tensorflow/tensorflow/blob/4ef28c5f287cd0a96daad3e7634b570de7e1f496/tensorflow/python/keras/utils/metrics_utils.py#L336-L345

would like some resolution on this!

Also running into this problem at the moment.

run into this problem for a combination use of tf.keras.losses.BinaryCrossentropy(from_logits=True) (for a numerically stable loss computation) and tf.keras.metrics.AUC

This issue also arises when trying to add metrics to classify text with bert tutorial

Thank you very much, @barskern. It works perfectly!
I did find a more compact way to express your solution. Thought Id share it:
class FromLogitsMixin:
  def __init__(self, from_logits=False, *args, **kwargs):
    super().__init__(*args, **kwargs)
    self.from_logits = from_logits

  def update_state(self, y_true, y_pred, sample_weight=None):
    if self.from_logits:
      y_pred = tf.nn.sigmoid(y_pred)
    return super().update_state(y_true, y_pred, sample_weight)

class AUC(FromLogitsMixin, tf.metrics.AUC):
  ...

class BinaryAccuracy(FromLogitsMixin, tf.metrics.BinaryAccuracy):
  ...

class TruePositives(FromLogitsMixin, tf.metrics.TruePositives):
  ...

class FalsePositives(FromLogitsMixin, tf.metrics.FalsePositives):
  ...

class TrueNegatives(FromLogitsMixin, tf.metrics.TrueNegatives):
  ...

class FalseNegatives(FromLogitsMixin, tf.metrics.FalseNegatives):
  ...

class Precision(FromLogitsMixin, tf.metrics.Precision):
  ...

class Recall(FromLogitsMixin, tf.metrics.Recall):
  ...

class F1Score(FromLogitsMixin, tfa.metrics.F1Score):
  ...

@lucasdavid That looks a lot cleaner! Thank you for the improvements 😁

I was  able to reproduce this issue on TF nightly ,please check the gist here ..Thanks !

F1Score based on @barskern's code:
class F1Score(tf.keras.metrics.Metric):
    def __init__(self, name="f1", from_logits=False, **kwargs):
        super(F1Score, self).__init__(name=name, **kwargs)
        self.precision = Precision(from_logits)
        self.recall = Recall(from_logits)

    def update_state(self, y_true, y_pred, sample_weight=None):
        self.precision.update_state(y_true, y_pred, sample_weight)
        self.recall.update_state(y_true, y_pred, sample_weight)

    def result(self):
        p = self.precision.result()
        r = self.recall.result()
        return (2 * p * r) / (p + r + tf.keras.backend.epsilon())

    def reset_states(self):
        self.precision.reset_states()
        self.recall.reset_states()

Closing this issue as it is fixed in latest version of TensorFlow. Please feel free to reopen the issue if you still have a concern. Thanks!

Closing this issue as it is fixed in latest version of TensorFlow. Please feel free to reopen the issue if you still have a concern. Thanks!

Closing this issue as it is fixed in latest version of TensorFlow. Please feel free to reopen the issue if you still have a concern. Thanks!

Hi @sushreebarsa, I believe this issue is not solved yet, at least not completely. Please see my post in the TensorFlow forum below.
https://discuss.tensorflow.org/t/metrics-related-predictions-must-be-1-error/6144/9
Would you reopen the issue or should I create a new one?

Hi @raftAtGit ,
Please create a new issue on keras-team/keras repo.
To know more see;
https://discuss.tensorflow.org/t/keras-project-moved-to-new-repository-in-https-github-com-keras-team-keras/1999
Thank you!

f self._from_logits:
            super(FalseNegatives, self).update_state(y_true, tf.nn.sigmoid(y_pred), sample_weight)
        else:
            super(FalseNegatives, self).update_state(y_true, y_pred, sample_weight)

class Precision(tfm.Precision):
    def __init__(self, from_logits=False, *args, **kwargs):
        super().__init__(*args, **kwargs)
        self._from_logits = from_logits

    def update_state(self, y_true, y_pred, sample_weight=None):
        if self._from_logits:
            super(Precision, self).update_state(y_true, tf.nn.sigmoid(y_pred), sample_weight)
        else:
            super(Precision, self).update_state(y_true, y_pred, sample_weight)

class Recall(tfm.Recall):
    def __init__(self, from_logits=False, *args, **kwargs):
        super().__init__(*args, **kwargs)
        self._from_logits = from_logits

    def update_state(self, y_true, y_pred, sample_weight=None):
        if self._from_logits:
            super(Recall, self).update_state(y_true, tf.nn.sigmoid(y_pred), sample_weight)
        else:
            super(Recall, self).update_state(y_true, y_pred, sample_weight)

@lucasdavid can you explicitly write out what ...mean under each class? an example will be helpful. Thanks

This issue also arises when trying to add metrics to classify text with bert tutorial

yep! I met with the same issue. How did you solve it? It would be nice if you can show me some hints to solve this! I've tried the tricks mentioned above ,but they dont work

@wjlgatech, my sincere apologies for taking so long to answer. I must have missed your question. You probably don't need it anymore, but I'll explain it for documentation purposes: The ellipses operator is a modern alternative (but equivalent) to command "pass" in this example. It's just used to state that that context has no additional statements. So for the AUC class:
class AUC(FromLogitsMixin, tf.metrics.AUC):
  ...

I'm saying "This class inherits from both FromLogitsMixin and tf.metrics.AUC, and has no other properties/methods.


feat: Improve CLI Output

Tell us about the problem you're trying to solve
As a user, I want to see better-formatted output from CLI
Describe the solution you’d like
Metrics information will be shown as a table in CLI.
We will use the rich library to build and show the table in the command line.

Fixed with #58


Assertion failure for tdigest_percentile

I was testing tdigest with Citus extension to prepare Citus for PG14 release. I hit an assertion fail and noticed that it isn't related to Citus. This assertion might have problems when this is run on a production environment.
This should either

allow zero count's to be added
provide a runtime error that zero's can't be added

Postgres version: 14beta3  -- (then tried with 13.0, it fails as well)
The failure is happening in tdigest_add_double_count
Exaclty here: https://github.com/tvondra/tdigest/blob/d14642eb573ddd80623b1dc8392587cf3ee2bb43/tdigest.c#L1172
Example:
create extension tdigest;
CREATE TABLE t (a int, b int, c double precision);
INSERT INTO t values(0, 0, 0.0);
SELECT tdigest_percentile(t.c, t.a, 100, 0.95) FROM t;

Here is the backtrace:
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
#1  0x00007fab130e6921 in __GI_abort () at abort.c:79
#2  0x000055a03540314f in ExceptionalCondition (conditionName=conditionName@entry=0x7fab076b7c5b "count > 0",
    errorType=errorType@entry=0x7fab076b7c07 "FailedAssertion", fileName=fileName@entry=0x7fab076b7bfd "tdigest.c",
    lineNumber=lineNumber@entry=1172) at assert.c:69
#3  0x00007fab076b57d0 in tdigest_add_double_count (fcinfo=0x55a036eec708) at tdigest.c:1172
#4  0x000055a0350eae97 in ExecAggPlainTransByVal (setno=<optimized out>, aggcontext=<optimized out>,
    pergroup=0x55a036ee04d0, pertrans=<optimized out>, aggstate=<optimized out>) at execExprInterp.c:4315
#5  ExecInterpExpr (state=0x55a036eec7f8, econtext=0x55a036eded80, isnull=0x7fffceca85d7) at execExprInterp.c:1713
#6  0x000055a0350e608e in ExecInterpExprStillValid (state=0x55a036eec7f8, econtext=0x55a036eded80,
    isNull=0x7fffceca85d7) at execExprInterp.c:1824
#7  0x000055a035103287 in ExecEvalExprSwitchContext (isNull=0x7fffceca85d7, econtext=<optimized out>,
    state=<optimized out>) at ../../../src/include/executor/executor.h:339
#8  advance_aggregates (aggstate=aggstate@entry=0x55a036ede948) at nodeAgg.c:842
#9  0x000055a0351074f3 in agg_retrieve_direct (aggstate=aggstate@entry=0x55a036ede948) at nodeAgg.c:2454
#10 0x000055a035107752 in ExecAgg (pstate=0x55a036ede948) at nodeAgg.c:2179
#11 0x000055a0350f7118 in ExecProcNodeFirst (node=0x55a036ede948) at execProcnode.c:463
#12 0x000055a0350eeffc in ExecProcNode (node=0x55a036ede948) at ../../../src/include/executor/executor.h:257
#13 ExecutePlan (estate=estate@entry=0x55a036ede710, planstate=0x55a036ede948, use_parallel_mode=<optimized out>,
    operation=operation@entry=CMD_SELECT, sendTuples=sendTuples@entry=true, numberTuples=numberTuples@entry=0,
    direction=ForwardScanDirection, dest=0x55a036ee1840, execute_once=true) at execMain.c:1551
#14 0x000055a0350efc97 in standard_ExecutorRun (queryDesc=0x55a036e3b670, direction=ForwardScanDirection, count=0,
    execute_once=<optimized out>) at execMain.c:361
#15 0x000055a0350efd62 in ExecutorRun (queryDesc=queryDesc@entry=0x55a036e3b670,
    direction=direction@entry=ForwardScanDirection, count=count@entry=0, execute_once=<optimized out>)
    at execMain.c:305
#16 0x000055a0352bb8b4 in PortalRunSelect (portal=portal@entry=0x55a036e80df0, forward=forward@entry=true, count=0,
    count@entry=9223372036854775807, dest=dest@entry=0x55a036ee1840) at pquery.c:919
---Type <return> to continue, or q <return> to quit---
#17 0x000055a0352bd304 in PortalRun (portal=portal@entry=0x55a036e80df0, count=count@entry=9223372036854775807,
    isTopLevel=isTopLevel@entry=true, run_once=run_once@entry=true, dest=dest@entry=0x55a036ee1840,
    altdest=altdest@entry=0x55a036ee1840, qc=0x7fffceca8990) at pquery.c:763
#18 0x000055a0352b91d2 in exec_simple_query (
    query_string=query_string@entry=0x55a036e1a0c0 "SELECT tdigest_percentile(t.c, t.a, 100, 0.95) FROM t;")
    at postgres.c:1214
#19 0x000055a0352bb2fe in PostgresMain (argc=argc@entry=1, argv=argv@entry=0x7fffceca8b90, dbname=<optimized out>,
    username=<optimized out>) at postgres.c:4486
#20 0x000055a035213a94 in BackendRun (port=port@entry=0x55a036e3e790) at postmaster.c:4506
#21 0x000055a035216d25 in BackendStartup (port=port@entry=0x55a036e3e790) at postmaster.c:4228
#22 0x000055a035216f6a in ServerLoop () at postmaster.c:1745
#23 0x000055a035218515 in PostmasterMain (argc=3, argv=<optimized out>) at postmaster.c:1417
#24 0x000055a035153e02 in main (argc=3, argv=0x55a036e11be0) at main.c:209

Thanks for the report. Well, the assert is triggered because the table contains rows like this:
 a | b |         c
---+---+--------------------
 0 | 4 | 0.5139344756720483
 0 | 5 | 0.9749701220118325
 0 | 4 | 0.2685794689591283
(3 rows)

And we simply don't allow adding values with 0 (or negative) counts - because what would that do?
But it certainly seems a bit bogus to handle that using an assert - it's a user-supplier value, not some internal parameter, so it needs to be checked even on production builds without assert. I'll change that to an elog(ERROR).
An alternative would be to just ignore those values, but that seems rather dangerous and might easily mask issues.

Should be fixed by a75271b943561418bb4ce9c06008601c56cb21e7 - instead of crashing it should report ERROR.

Thank you!


Implement Confluent Connectors as Resource Type

Based on recent additions in the base library, https://github.com/cgroschupp/go-client-confluent-cloud, this change adds Confluent Connectors (and an Acceptance Test)  as Resources to the Terraform Provider.
This still uses the "inofficial" API of Confluent, not the new "official" API, as otherwise there would have been two ways of interacting with Confluent, and users would have to provide username / password and API Key / Secret.
There is one minor drawback in the implementation, due to Confluent Cloud API limitations: If only the Kafka API Key and Secret changes in the Terraform config for the Connector, this is not detected as an applicable change (because the API does not report the "old" API Key used, only asterisks).  So everyone wanting to update only this information for a Connector must update some other config field as well, or forcefully recreate that resource.

I noticed the acceptance tests fail, as there's no topic for test-datagen-data. I'll need to fix that before cutting a new release.


AWS Amplify : TypeError: Cannot read properties of null (reading 'tagName')

Before opening, please confirm:

[X] I have checked to see if my question is addressed in the FAQ.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting questions.
[X] I have removed any sensitive information from my code snippets and submission.

App Id
d1ry10q859508
AWS Region
us-east-1
Amplify Hosting feature
Frontend builds
Question
My website runs great locally and shows no errors in the console. However when I try and build it I get "TypeError: Cannot read properties of null (reading 'tagName')"
I don't have tagName explicitly anywhere in my code so I'm sure it's referring to something else but I do not know what since AWS Amplify doesn't give me much more information about the error.
Amplify Error :
 # Starting phase: preBuild
# Executing command: npm ci
2023-08-02T20:41:32.787Z [WARNING]: npm
2023-08-02T20:41:32.789Z [WARNING]: WARN deprecated<EMAIL_ADDRESS>Modern JS already guarantees Array#sort() is a stable sort, so this library is deprecated. See the compatibility table on MDN: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort#browser_compatibility
                                    npm WARN deprecated<EMAIL_ADDRESS>See https://github.com/lydell/source-map-url#deprecated
2023-08-02T20:41:33.067Z [WARNING]: npm WARN deprecated<EMAIL_ADDRESS>Please see https://github.com/lydell/urix#deprecated
2023-08-02T20:41:33.410Z [WARNING]: npm WARN deprecated
2023-08-02T20:41:33.411Z [WARNING]<EMAIL_ADDRESS>https://github.com/lydell/resolve-url#deprecated
2023-08-02T20:41:33.628Z [WARNING]: npm WARN
2023-08-02T20:41:33.629Z [WARNING]: deprecated<EMAIL_ADDRESS>See https://github.com/lydell/source-map-resolve#deprecated
2023-08-02T20:41:33.692Z [WARNING]: npm WARN deprecated
2023-08-02T20:41:33.693Z [WARNING]<EMAIL_ADDRESS>This package has been deprecated and is no longer maintained. Please use @rollup/plugin-terser
2023-08-02T20:41:33.729Z [WARNING]: npm WARN deprecated<EMAIL_ADDRESS>Use your platform's native performance.now() and performance.timeOrigin.
2023-08-02T20:41:34.011Z [WARNING]: npm WARN deprecated
2023-08-02T20:41:34.011Z [WARNING]<EMAIL_ADDRESS>Please use @jridgewell/sourcemap-codec instead
2023-08-02T20:41:36.076Z [WARNING]: npm WARN deprecated
2023-08-02T20:41:36.078Z [WARNING]<EMAIL_ADDRESS><EMAIL_ADDRESS>2023-08-02T20:41:37.052Z [WARNING]: npm WARN deprecated<EMAIL_ADDRESS>support for ECMAScript is superseded by `uglify-js` as of v3.13.0
2023-08-02T20:41:37.252Z [WARNING]: npm WARN deprecated<EMAIL_ADDRESS>This SVGO version is no longer supported. Upgrade to v2.x.x.
2023-08-02T20:41:43.973Z [INFO]: added 1942 packages, and audited 1943 packages in 24s
2023-08-02T20:41:43.978Z [INFO]: 253 packages are looking for funding
                                 run `npm fund` for details
2023-08-02T20:41:43.979Z [INFO]: 6 high severity vulnerabilities
                                 To address all issues (including breaking changes), run:
                                 npm audit fix --force
                                 Run `npm audit` for details.
2023-08-02T20:41:44.004Z [INFO]: # Completed phase: preBuild
                                 # Starting phase: build
2023-08-02T20:41:44.006Z [INFO]: # Executing command: npm run build
2023-08-02T20:41:44.345Z [INFO]: ><EMAIL_ADDRESS>build
                                 > react-scripts build
2023-08-02T20:41:45.813Z [INFO]: Creating an optimized production build...
2023-08-02T20:42:27.882Z [INFO]: Failed to compile.
2023-08-02T20:42:27.884Z [INFO]: TypeError: Cannot read properties of null (reading 'tagName')
2023-08-02T20:42:27.946Z [ERROR]: !!! Build failed
2023-08-02T20:42:27.947Z [ERROR]: !!! Non-Zero Exit Code detected
2023-08-02T20:42:27.947Z [INFO]: # Starting environment caching...
2023-08-02T20:42:27.947Z [INFO]: # Environment caching completed
Terminating logging...
2023-08-02T20:40:37.361Z [INFO]: # Cloning repository: git@github.com:gamalabdu/trash.git
2023-08-02T20:40:40.616Z [INFO]:
2023-08-02T20:40:40.719Z [INFO]: Cloning into 'trash'...
2023-08-02T20:40:40.720Z [INFO]: # Switching to commit: fc34badc6e4fb5d3ea471aa07dc4f3c697a09d37
2023-08-02T20:40:41.083Z [INFO]: Note: switching to 'fc34badc6e4fb5d3ea471aa07dc4f3c697a09d37'.
                                 You are in 'detached HEAD' state. You can look around, make experimental
                                 changes and commit them, and you can discard any commits you make in this
                                 state without impacting any branches by switching back to a branch.
                                 If you want to create a new branch to retain commits you create, you may
                                 do so (now or later) by using -c with the switch command. Example:
                                 git switch -c <new-branch-name>
                                 Or undo this operation with:
                                 git switch -
                                 Turn off this advice by setting config variable advice.detachedHead to false
                                 HEAD is now at fc34bad clean up some more
2023-08-02T20:40:41.124Z [INFO]: Successfully cleaned up Git credentials
2023-08-02T20:40:41.124Z [INFO]: # Checking for Git submodules at: /codebuild/output/src2611854775/src/trash/.gitmodules
2023-08-02T20:40:41.130Z [INFO]: # Retrieving environment cache...
2023-08-02T20:40:41.170Z [WARNING]: ! Unable to write cache: {"code":"ERR_BAD_REQUEST","message":"Request failed with status code 404"})}
2023-08-02T20:40:41.170Z [INFO]: ---- Setting Up SSM Secrets ----
2023-08-02T20:40:41.170Z [INFO]: SSM params {"Path":"/amplify/d1ry10q859508/master/","WithDecryption":true}
2023-08-02T20:40:41.200Z [WARNING]: !Failed to set up process.env.secrets
2023-08-02T20:40:41.205Z [INFO]: No live updates for this build run
2023-08-02T20:40:41.208Z [INFO]: # Retrieving cache...
2023-08-02T20:40:41.246Z [INFO]: # Retrieved cache
                                 # Starting phase: preBuild
                                 # Executing command: npm ci
2023-08-02T20:41:32.787Z [WARNING]: npm
2023-08-02T20:41:32.789Z [WARNING]: WARN deprecated<EMAIL_ADDRESS>Modern JS already guarantees Array#sort() is a stable sort, so this library is deprecated. See the compatibility table on MDN: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort#browser_compatibility
                                    npm WARN deprecated<EMAIL_ADDRESS>See https://github.com/lydell/source-map-url#deprecated
2023-08-02T20:41:33.067Z [WARNING]: npm WARN deprecated<EMAIL_ADDRESS>Please see https://github.com/lydell/urix#deprecated
2023-08-02T20:41:33.410Z [WARNING]: npm WARN deprecated
2023-08-02T20:41:33.411Z [WARNING]<EMAIL_ADDRESS>https://github.com/lydell/resolve-url#deprecated
2023-08-02T20:41:33.628Z [WARNING]: npm WARN
2023-08-02T20:41:33.629Z [WARNING]: deprecated<EMAIL_ADDRESS>See https://github.com/lydell/source-map-resolve#deprecated
2023-08-02T20:41:33.692Z [WARNING]: npm WARN deprecated
2023-08-02T20:41:33.693Z [WARNING]<EMAIL_ADDRESS>This package has been deprecated and is no longer maintained. Please use @rollup/plugin-terser
2023-08-02T20:41:33.729Z [WARNING]: npm WARN deprecated<EMAIL_ADDRESS>Use your platform's native performance.now() and performance.timeOrigin.
2023-08-02T20:41:34.011Z [WARNING]: npm WARN deprecated
2023-08-02T20:41:34.011Z [WARNING]<EMAIL_ADDRESS>Please use @jridgewell/sourcemap-codec instead
2023-08-02T20:41:36.076Z [WARNING]: npm WARN deprecated
2023-08-02T20:41:36.078Z [WARNING]<EMAIL_ADDRESS><EMAIL_ADDRESS>2023-08-02T20:41:37.052Z [WARNING]: npm WARN deprecated<EMAIL_ADDRESS>support for ECMAScript is superseded by `uglify-js` as of v3.13.0
2023-08-02T20:41:37.252Z [WARNING]: npm WARN deprecated<EMAIL_ADDRESS>This SVGO version is no longer supported. Upgrade to v2.x.x.
2023-08-02T20:41:43.973Z [INFO]: added 1942 packages, and audited 1943 packages in 24s
2023-08-02T20:41:43.978Z [INFO]: 253 packages are looking for funding
                                 run `npm fund` for details
2023-08-02T20:41:43.979Z [INFO]: 6 high severity vulnerabilities
                                 To address all issues (including breaking changes), run:
                                 npm audit fix --force
                                 Run `npm audit` for details.
2023-08-02T20:41:44.004Z [INFO]: # Completed phase: preBuild
                                 # Starting phase: build
2023-08-02T20:41:44.006Z [INFO]: # Executing command: npm run build
2023-08-02T20:41:44.345Z [INFO]: ><EMAIL_ADDRESS>build
                                 > react-scripts build
2023-08-02T20:41:45.813Z [INFO]: Creating an optimized production build...
2023-08-02T20:42:27.882Z [INFO]: Failed to compile.
2023-08-02T20:42:27.884Z [INFO]: TypeError: Cannot read properties of null (reading 'tagName')
2023-08-02T20:42:27.946Z [ERROR]: !!! Build failed
2023-08-02T20:42:27.947Z [ERROR]: !!! Non-Zero Exit Code detected
2023-08-02T20:42:27.947Z [INFO]: # Starting environment caching...
2023-08-02T20:42:27.947Z [INFO]: # Environment caching completed
Terminating logging...

Amplify.yaml :
version: 1
frontend:
  phases:
    preBuild:
      commands:
        - npm ci
    build:
      commands:
        - npm run build
  artifacts:
    baseDirectory: build
    files:
      - '**/*'
  cache:
    paths:
      - node_modules/**/*

Does anyone know where I can begin to search for this error or what it is referring too?

This looks like an error coming from Next.js. This discussion in their repository seems related: vercel/next.js#12830

Thank you, I took a look but it is different in my case as I don't see any errors in my console when I run it locally. This error only happens when building in Amplify.

Anyone have any idea's on where to start touble shooting this issue?

Hi @gamalabdu 👋 , it seems that the Amplify app d1ry10q859508 has been deleted and thus we won't be able to review the build logs for it from our end.
Are you still running into this build issue? If yes, can you share your new app id and some steps for us to reproduce this behavior?


Fix GitHub release asset upload

ghr only looks at immediate descendents of the path it is provided, so we need to ensure that ghr-dist/ is flattened.
Fixes: #2113
NONE

The file .circleci/config.yml is in the blocklist for external contributors. Hence, these changes are not tested by the CI pipeline active until the build is re-triggered by a core committer or the PR is merged. Please be careful when reviewing it.
/cc @mattermost/core-security @mattermost/core-build-engineers

Hello @elyscape,
Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.

@amyblais Will cherry-pick this over to v5.1 for any future dot releases.

Cherry pick is scheduled.


Heads up on ID's and UID's.

I had to add the following to formatMessage:
'id'       =>  $id,
Please note if you are unable to get a function to work alternate between the UID & ID... this isnt documented.

You could possibly add an "isset" function to check for both variants.
On 25 Nov 2015 07:43, "Aaron Smith"<EMAIL_ADDRESS>wrote:

I had to add the following to formatMessage:
'id' => $id,
Please not if you are unable to get a function to work alternate between
the UID & ID... this isnt documented.
—
Reply to this email directly or view it on GitHub
https://github.com/SSilence/php-imap-client/issues/26.

Thank you for your work.


Add requirements.txt?

Would it be possible to include a requirements.txt to make for faster invocations of pip install dolma?
When I spin up a new machine and try to install Dolma from a clean python environment, there are many packages that need to have multiple versions downloaded to determine compatibility with the other requirements:
e.g., I get many messages in pip like
INFO: pip is looking at multiple versions of <PACKAGE> to determine which version is compatible with other requirements. This could take a while.
And even the dreaded:
INFO: This is taking longer than usual. You might need to provide the dependency resolver with stricter constraints to reduce runtime. If you want to abort this run, you can press Ctrl + C to do so. To improve how pip performs, tell us what happened here: https://pip.pypa.io/surveys/backtracking

I'm pretty sure all of this could be ameliorated with a requirements.txt

Okay, made a PR with a requirements.txt
I suppose a better option would be to additionally update the pyproject.toml, but I really just wanted a requirements file.


Escaping Literal Quotes in Strings

Challenge  Escaping Literal Quotes in Strings  https://www.freecodecamp.com/challenges/escaping-literal-quotes-in-strings#?solution= var myStr   I am a double quoted string inside double quotes . %3B%3B%2F%2F Change this line   has an issue. User Agent is%3A code>Mozilla%2F5.0  Windows NT 10.0%3B WOW64%3B rv%3A51.0  Gecko%2F20100101 Firefox%2F51.0 %2Fcode>. Please describe how to reproduce this issue%2C and include links to screenshots if possible. My code%3A    javascript var myStr = I am a double quoted string inside double quotes . %3B%3B%2F%2F Change this line

@InquisitiveDev2016 Thank you for reporting this issue.
This is a standard message notifying you that this issue seems to be a request for help. Instead of asking for help here, please click the "help" button on the challenge on Free Code Camp, which will take you to the help chatroom for that specific challenge. You can also view our full list of official chatrooms.
If you think I'm wrong in closing this issue, please reopen it and add further clarification. Thank you, and happy coding!


Use latest version of tests

@psturc FYI this is related to the devfile PR in the test repo that @stuartwdouglas just merged

/test jvm-build-service-in-repo-with-pruning-e2e

/test jvm-build-service-in-repo-with-pruning-e2e

apparent tool install flake still with the pruning e2e ... will
/retest
one more time and if it still occurs, must be some diff in the different jobs where something broke?


Fix project access on time tracking

Notion: https://www.notion.so/saeloun/Unable-to-remove-a-team-member-from-a-project-345c86358a1c443da44369814ace6ef5?pvs=4
Why: Even when member was removed from project, he was getting that project name listed on time tracking page.
What: Fixed the function which returns the list of user project by considering project members so that user won't see any project from which he is removed

@shalapatil Please check why the build is failing on this PR and then assign it to Vipul for review.


update version pinning of cloudposse/utils

what
Update the pinning of upstream cloudposse/utils to <2.0.0
why
We previously added this pinning because we mistakenly released some changes to the provider without testing backward compatibility and left customers in a broken state. In future releases of cloudposse/utils we will release any potential breaking changes as 2.0.0. Pinning to <2.0.0 will allow us to continue to take advantage of bug fixes in the 1.x.x versions and allow the caller to specify a pinned version in their root module if desired.

/test all

/terratest