'error' is not emited

Having this task
gulp.task('docs', function(){
	return gulp.src( path.lib + '**/*.js' )
		.pipe( docs.process({}) )
		.pipe( gulp.dest( path.docs ) )
		.on('end', function(){
			gutil.log( gutil.colors.green( 'Rebuild docs successfully done.' ) );
			browserSync.reload();
		})
		.on('error', function( error ){
			gutil.log( gutil.colors.red( 'Rebuild docs failed.' ), error );
			gutil.beep();
			throw error;
		});
});

the error handler is no called when a error is found.
This is the output form the task above with an error
Z:\js-lib>gulp docs
[19:24:16] Using gulpfile Z:\js-lib\gulpfile.js
[19:24:16] Starting 'docs'...
[Error: Don't know how to format @ngdoc: module]
[19:24:16] Rebuild docs successfully done.
[19:24:16] Finished 'docs' after 100 ms

will look into this now

It still doesn't work in 0.2.12 version
I tried different approaches. But it always fails.
Please check it if you have time
gulp.task(
	'ngdocs:silent',[],function(){
		function handleError(err){
			gutil.log('boobs!');
			this.emit('end');
		}

		return gulp.src(
			[
				'src/app/**/*.js'
			]
		).pipe(
				plumber({
					handleError: handleError
				})
		)
			.pipe(
			gulpDocs.process({
				html5Mode: false
			}).on('error',handleError)
		).on('error',handleError)
			.pipe(gulp.dest('./docs'));
	}
);

 throw new Error("Not a valid 'param' format: " + text + ' (found i
                  ^
Error: Not a valid 'param' format: s{string} url - description (found in:

It still doesn't work in the latest version.
@hellfrom are you able to get this working?

@GaryLengkong I don't watch this repository anymore. As solution, we decided to perform pre-build task before each commit. And in case someone brakes documentation he fixes it.


feat: Implement updated pull request comments (HTML and MD)

Pull Request
Description
The current PR contains significant updates on the pull request comments.
Changes cover HTML and MD comment formats.
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[X] Code cleanup/refactoring
[ ] Documentation update
[ ] This change requires a documentation update
[ ] CI system update
[X] Test Coverage update

Testing
Tested on the local environment.
Test PR: https://github.com/o-kopysov/LPVS/pull/2
Short view:

Full view:

Checklist:

[X] My code follows the style guidelines of this project
[X] My code meets the required code coverage for lines (90% and above)
[X] My code meets the required code coverage for branches (80% and above)
[X] I have performed a self-review of my own code
[X] I have commented my code, particularly in hard-to-understand areas
[ ] 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

Codecov Report
Attention: Patch coverage is 97.56098% with 3 lines in your changes missing coverage. Please review.

Project coverage is 93.74%. Comparing base (62d4c96) to head (e8f0d93).

Files
Patch %
Lines

...java/com/lpvs/entity/report/LPVSReportBuilder.java
98.30%
0 Missing and 2 partials :warning:

.../main/java/com/lpvs/service/LPVSGitHubService.java
80.00%
0 Missing and 1 partial :warning:

Additional details and impacted files
@@             Coverage Diff              @@
##               main     #578      +/-   ##
============================================
+ Coverage     93.57%   93.74%   +0.16%
- Complexity      583      602      +19
============================================
  Files            49       49
  Lines          2009     2110     +101
  Branches        234      244      +10
============================================
+ Hits           1880     1978      +98
- Misses           59       60       +1
- Partials         70       72       +2

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


What highlight groups are responsible for the text color on the dashboard?

I am trying to change this yellowish color for my "find file, find dotfiles", etc...,to something else but nothing seems to work. What can I use to change the color of the text? Here is what I currently doing to try and fix this         vim.api.nvim_set_hl(0, 'Normal', { fg = '#ffffff' }) -- Set normal text to white
vim.api.nvim_set_hl(0, 'String', { fg = '#ffffff' }) -- Set string text to white
vim.api.nvim_set_hl(0, 'MoreMsg', { fg = '#ffffff' }) -- Set "more" messages to white
vim.api.nvim_set_hl(0, 'Title', { fg = '#ffffff' }) -- Set titles to white
vim.api.nvim_set_hl(0, 'Search', { fg = '#ffffff' }) -- Set search text to white

Try with DashboardDesc. The highlight names are in the Highlight section in the README.


RC1 Update 1 release notes?

@danroth27 ?

I think he means that it would be nice if an announcement was made about RC1-Update 1 and what it fixed.

We did publish a note in the RC1 announcement blog post here: http://blogs.msdn.com/b/webdev/archive/2015/11/18/announcing-asp-net-5-release-candidate-1.aspx

I think at minimum the https://get.asp.net/ site should indicate rc1 update1 or maybe show a release date because for people like me who updated to rc1 when it first came out, there was no indication anywhere that the update1 was available. I knew it was coming from watching community standup and I found out it was available from someone on jabbr, but even now there is nothing on the get asp site to indicate that anything changed.

I can sort of second that ... I actually only heard about it b/c @davidfowl told someone in an issue to go get it. It had been out a week at that point.

@DamianEdwards @shirhatti regarding get.asp.net comment: https://github.com/aspnet/Home/issues/1151#issuecomment-162064799


IdentifierFactory should count digits as word breaks

Codecov Report

Merging #452 (93b0435) into master (3df1c28) will decrease coverage by 0.03%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #452      +/-   ##
==========================================
- Coverage   63.02%   62.99%   -0.04%
==========================================
  Files         157      157
  Lines       10756    10749       -7
==========================================
- Hits         6779     6771       -8
- Misses       3360     3362       +2
+ Partials      617      616       -1

Impacted Files
Coverage Δ

hack/generator/pkg/astmodel/identifier_factory.go
100.00% <100.00%> (ø)

...ted/pkg/reconcilers/azure_deployment_reconciler.go
58.21% <0.00%> (-1.12%)
:arrow_down:

hack/generated/pkg/testcommon/resource_namer.go
78.57% <0.00%> (+1.64%)
:arrow_up:

Continue to review full report at Codecov.

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


Release

Bump go to 1.19 in CI workflows

Codecov Report
Patch and project coverage have no change.

Comparison is base (cb6de8d) 20.40% compared to head (c9b0f6d) 20.40%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@           Coverage Diff           @@
##             main     #487   +/-   ##
=======================================
  Coverage   20.40%   20.40%
=======================================
  Files          31       31
  Lines        1926     1926
=======================================
  Hits          393      393
  Misses       1510     1510
  Partials       23       23

Flag
Coverage Δ

unittests
20.40% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Adding mlflow example

I have added two linear regression examples.

In linear_regression_local, all the metadata and artifacts would be stored in a local directory.
In linear_regression_remote, all the metadata and artifacts would be stored in mlflow-server stack .
Also, I have created upload_data_to_postgres.py file, to upload example dataset to local postgres databse and added instruction in README to how to do  so.

Hey @yatharthranjan, thanks for the review. I have made the mentioned changes. Let me know if anything else is needed.

Hey @yatharthranjan, thanks for the review. I have made the mentioned changes. Let me know if anything else is needed.


fix: The maximum number of rules per security group has been reached

Issue #, if available:
Fixes #39, the security group have less number of rules, so I trunk the new_ranges array by limit num and save to another security group.
If AWS officially relaxes the limit on the number of security groups, there won't be any problems that need to be fixed.
Description of changes:
I solved this problem by create multi security group to save the ip rules, if your security group is not enougth, alert " Groups is not enough, we need x at least!".
like this:

https://github.com/aws-samples/aws-cloudfront-samples/issues/39#issuecomment-674362254
Increment rules limit is a better choice!


How to change view?

How can I programmatically change view?
This is not working:
this.setState({ view: 'agenda' });

http://intljusticemission.github.io/react-big-calendar/examples/index.html#prop-defaultView

Thanks, defaultView works just fine for me, what I'm trying to do is change the view state from a custom function after the Calendar is rendered. Example being a custom button to change view, or another event that triggers a function to change the calendar view state.
That's where I'm trying to access the view state but it is not working.

You can use state. Make the defaultView take its value from the state (you can always use the useState hook if you don't want to use a class) and make your function change the state value because changing state will re-render the component.

I have tried this:
<Calendar
defaultView={myDefaultView}
^ this is getting set by constructor on initial render without issue.
But if I later call a function like this:
handleChangeView(){
this.setState({myDefaultView: 'agenda'})
}
...this changes the defaultView value, but does not re-render the component, or change the view.

I do this by using view and onView together, which sorta tells RBC that it's controlled. Internally, when a view is to change, it calls the method you apply through onView to change your state variable. If you change view programmatically elsewhere (like some external nav), it'll rerender the calendar view.

handleChangeView(){
   this.setState({myDefaultView: 'agenda'})
}

should be
handleChangeView(){
    this.setState({defaultView: 'agenda'})
}

you were inserting a new state value using the name of your variable?

handleChangeView(){
   this.setState({myDefaultView: 'agenda'})
}

should be
handleChangeView(){
    this.setState({defaultView: 'agenda'})
}

you were inserting a new state value using the name of your variable?

No, this doesn't work either. I truly wish it did, like every other React component on the planet, but no, this does not work.

I can't see how it wouldn't. This CodeboxSandbox Example shows the exact same principle in use, just using the useState hook and a function component, instead of a class component with setState. It's a quick example, but you'll see you can control the view state using the 'External View Changer' controls at the top of the interface.

, just using the useState hook and a function component, instead of a class component with setState.

And therein lies the difference. Hooks and functional components are not a direct replacement for class components and setState. They are completely different worlds. So, I remain unsurprised and very disappointed that this doesn't work. I've invested months into this calendar (and there is no going back now) and despite the very advanced calendar we've built for our app, we are lacking the ability to do the simplest of simple React things, because someone was obsessed with Hooks.

On a hunch I decided to try this one more time:
THIS finally worked:

default state for both:
this.state = {view: 'month', defaultView: 'month'}

function to change:

handleChangingView = (view) => {this.setState({view: view, defaultView: view})}

additional callback function for OnView event:

handleOnViewChange = e => {this.setState:({view: e, defaultView: e})}

What a mess.

http://intljusticemission.github.io/react-big-calendar/examples/index.html#prop-defaultView

404 NOt found

@RedNoo the repo changed ownership very recently, and these pasted links don't auto update. Here's the new link http://jquense.github.io/react-big-calendar/examples/index.html#prop-defaultView

http://intljusticemission.github.io/react-big-calendar/examples/index.html#prop-defaultView

https://jquense.github.io/react-big-calendar/examples/index.html#prop-defaultView


Menu builder edit item problem

Laravel: v5.8.35
Voyager: v1.2.7
PHP: 7.2
Database: mysql Ver 5.7.14, for Win64 (x86_64)

Description

After updating to the Voyager 1.2.6 version, in the menu builder, when editing an item, the values are not shown in their corresponding input, the type of route is displayed without selecting, same with target and the icon field is shown with the title instead of the icon class
Steps To Reproduce
Steps to reproduce the behavior:

Go to 'Tools'
Click on Menu Builder on Admin Menu
Select Edit any Item
See error

Screenshots

Duplicate of #4365.
Fix is already merged but I don't know when next version will be released.

thanks


Mark Version 509.0.0 as "Latest"

Description
Since version 509.0.0 was released a few days ago, so we need to mark it as the latest version.

Steps to Reproduce
No response

Tracked in Apple’s issue tracker as rdar://115644851

Oh, I swear I set the checkbox when creating the release tag. Thanks for reporting this, should be fixed now.


Move to Apollo 2.0

Apollo 2.0 has moved from Redux. Thus the current solution using redux-offline won't work with Apollo versions from 2.0 onwards.

Is a fix in the pipelines or should one remain with whatever version of apollo-client they're currently using (I'm running 1.9.2)?

@TheoMer Sadly, I am quite busy at the moment. So an apollo-offline version compatible with Apollo 2.0 might take some time. - Although I would very much appreciate every effort from the community to speed up this process!
Some first solutions for rudimentary offline support in v2.0 are discussed here.
This package might even be entirely replaced by apollo-link-offline in the future. Thoughts on the implementation can be found here.

@MLPXBrachmann Just checking here, do you have any interest (and availability) in picking that up for Apollo 2.0 or contribute to an hypothetical apollo-link-offline community repository?

@nicocrm I would love to be a part of any community-driven effort in this direction!
Right now I am quite occupied, but as soon as I have at least some spare time on my hands, I will try to put it to good use (see my response over in the apollo-link-offline discussion).

@MLPXBrachmann May I ask whether there's been any movement on this issue?

@TheoMer I'm afraid there hasn't (not from my side at least).
The discussion however continued here.

I'm not sure if this is still being maintained, but a modern solution with Apollo offline and redux-persist would be amazing. Is that achievable with this library?


Update Harvester pre-merge template

Update Harvester pre-merge template
Related Issue: harvester/harvester#1819

e2e is for the automation test and integration is the one that exist on the harvester repo https://github.com/harvester/harvester/tree/master/tests, we can tweak the label name in a separated PR if needed, thanks.


Update-AzDatabricksWorkspace command for updating Managed Services CMK and Managed Disk CMK fails

Prerequisites

[X] Write a descriptive title.
[X] Make sure you are able to repro it on the latest released version
[X] Search the existing issues.
[X] Refer to the FAQ.
[X] Refer to Differences between Windows PowerShell 5.1 and PowerShell.

Steps to reproduce
Hello I am from Azure Databricks PG team at Microsoft. You can reach me out at<EMAIL_ADDRESS>I am writing this issue since we have some anomalies while running the below commands.
Update-AzDatabricksWorkspace -SubscriptionId 7a9974b4-****-490d-a02d-b9b3a07332f6 -ResourceGroupName quickstart-template-validation -Name workspace456 -PrepareEncryption
Update-AzDatabricksWorkspace -SubscriptionId ead****-2100-4b4d-981a-3225eb77daa7 -ResourceGroupName lz-az-comm****-d-rg -Name lz-ncil01-d-db -EncryptionKeySource 'Microsoft.KeyVault' -ManagedServicesKeyVaultPropertiesKeyName 'cet-adb05-k01' -ManagedServicesKeyVaultPropertiesKeyVaultUri 'https://*-kv.vault.azure.net/' -ManagedServicesKeyVaultPropertiesKeyVersion ''
Update-AzDatabricksWorkspace -SubscriptionId eadb****-2100-4b4d-981a-3225eb77daa7 -ResourceGroupName lz-az-community-d-rg -Name lz-ncil01-d-db -EncryptionKeySource 'Microsoft.KeyVault' -ManagedDiskKeyVaultPropertiesKeyName '-adb05-k01' -ManagedDiskKeyVaultPropertiesKeyVaultUri 'https://-adb05-kv.vault.azure.net/' -ManagedDiskKeyVaultPropertiesKeyVersion '*****' -ManagedDiskRotationToLatestKeyVersionEnabled
Update-AzDatabricksWorkspace -SubscriptionId eadb9dfd-2100-4b4d-981a-3225eb77daa7 -ResourceGroupName lz-az-community-d-rg -Name lz-ncil01-d-db -EncryptionKeySource 'Microsoft.KeyVault' -EncryptionKeyVaultUri 'https://-adb05-kv.vault.azure.net/' -EncryptionKeyName '-adb05-k01' -EncryptionKeyVersion '****'
We are getting this error while we try to run any of the above commands. Also attaching the screenshot.

After checking our backend logs what we see is that while we run a simple update workspace (the first command) to set prepareEncryption true, the request payload also checks in managedServices key source set failing with the error message. Below is the screenshot and highlighted set which is being called, which is not something we are calling in the command.

Similar issue with other commands as well. As a workaround we saw that the commands run fine when the encryptionKeySource property parameter is removed from the commands. But ideally it should not create any problem / break to a request involving Managed Services or Managed Disk CMK. Below are the commands which work fine, after we remove the encryptionkeySource property parameter
Update-AzDatabricksWorkspace -SubscriptionId eadb****-2100-4b4d-981a-3225eb77daa7 -ResourceGroupName lz-az-community-d-rg -Name lz-ncil01-d-db -ManagedDiskKeyVaultPropertiesKeyName '-adb05-k01' -ManagedDiskKeyVaultPropertiesKeyVaultUri 'https://-adb05-kv.vault.azure.net/' -ManagedDiskKeyVaultPropertiesKeyVersion '*****' -ManagedDiskRotationToLatestKeyVersionEnabled
Update-AzDatabricksWorkspace -SubscriptionId ead****-2100-4b4d-981a-3225eb77daa7 -ResourceGroupName lz-az-comm****-d-rg -Name lz-ncil01-d-db -ManagedServicesKeyVaultPropertiesKeyName 'cet-adb05-k01' -ManagedServicesKeyVaultPropertiesKeyVaultUri 'https://*-kv.vault.azure.net/' -ManagedServicesKeyVaultPropertiesKeyVersion ''
Can you please take a look into this and help fix this?
Expected behavior
Command should run successfully

Actual behavior
Fails

Error details
Update-AzDatabricksWorkspace -Subscriptionld 7a9974b4-6ef3-490d-a02d-b9b3a07332f6 -ResourceGroupName quickstart-template-validation
AZ. Databricks . aldentity : The keysource is
specified as keyvault but keyvault details are not correctly provi ded.
At \OneDrive
Mi ndowspowershel 1 Databri cks\l. 2. cksWorkspace . PSI : 391 char :17
Az . Databri cks . pri vate\New-AzDatabr i cksWorks pace_CreateVi a
-Name workspace456
+ Categorylnfo
. ma um"
. Inval idoperation: ({ body = {
} [New-AzDatabrick... eateVi aldentity] , Exception
+ FullyQua1ifiedErrorId
. Inval idEncrypti onEntitiesKeyVau1 tVa1ue , Mi crosoft . Azure. PowerShe11 . Cmdl ets . Databri cks . Cmdl ets .

Environment data
Name                           Value
----                           -----
PSVersion                      5.1.22621.1778
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.22621.1778
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>

Visuals
Below error is while running 1st command i.e. $workSpace = Update-AzDatabricksWorkspace -Name workspace456 -ResourceGroupName quickstart-template-validation -PrepareEncryption .

Below error is while running 2nd command i.e. Update-AzDatabricksWorkspace -ResourceGroupName quickstart-template-validation -Name test-disk-workspace -EncryptionKeySource 'Microsoft.KeyVault' -ManagedServicesKeyVaultPropertiesKeyName 'keyc' -ManagedServicesKeyVaultPropertiesKeyVaultUri 'https://constantkv.vault.azure.net/' -ManagedServicesKeyVaultPropertiesKeyVersion 'a9c9a6da3f024f1a83bac2588faaaaad'

Below error is while running 3rd command i.e. Update-AzDatabricksWorkspace -ResourceGroupName quickstart-template-validation -Name test-disk-workspace -EncryptionKeySource 'Microsoft.KeyVault' -ManagedDiskKeyVaultPropertiesKeyName 'keyc' -ManagedDiskKeyVaultPropertiesKeyVaultUri 'https://constantkv.vault.azure.net/' -ManagedDiskKeyVaultPropertiesKeyVersion 'a9c9a6da3f024f1a83bac2588faaaaad' -ManagedDiskRotationToLatestKeyVersionEnabled

Hello we have customer also reporting this similar issue. While trying to update DBFS encryption using the below command it fails with InvalidEncryptionEntitiesKeyVaultValue.
Update-AzDatabricksWorkspace -SubscriptionId 7a9974b4-6ef3-490d-a02d-b9b3a07332f6 -ResourceGroupName quickstart-template-validation -Name test-workspace3-928 -EncryptionKeySource 'Microsoft.Keyvault' -EncryptionKeyVaultUri 'https://constantkv.vault.azure.net/' -EncryptionKeyName 'keyc' -EncryptionKeyVersion 'a9c9a6da3f024f1a83bac2588faaaaad'
Error message:
Az.Databricks.private\New-AzDatabricksWorkspace_CreateViaIdentity : The keysource is specified as keyvault but
keyvault details are not correctly provided.
At C:\Users\v-sgandamuni\OneDrive -
Microsoft\Documents\WindowsPowerShell\Modules\Az.Databricks\1.2.0\custom\Update-AzDatabricksWorkspace.ps1:391
char:17

...             Az.Databricks.private\New-AzDatabricksWorkspace_CreateVia ...

            ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

CategoryInfo          : InvalidOperation: ({ body = {
"...mium"
}
} }:<>f__AnonymousType7`1) [New-AzDatabrick...eateViaIdentity], Exception
FullyQualifiedErrorId : InvalidEncryptionEntitiesKeyVaultValue,Microsoft.Azure.PowerShell.Cmdlets.Databricks
.Cmdlets.NewAzDatabricksWorkspace_CreateViaIdentity

Here is the payload of the request we see in our logs when the above command is being invoked.
Request content: {"properties":{"encryption":{"entities":{"managedServices":{"keySource":"Microsoft.Keyvault","keyVaultProperties":{"keyVaultUri":"https://constantkv.vault.azure.net/","keyName":"keyc","keyVersion":"a9c9a6da3f024f1a83bac2588faaaaad"}},"managedDisk":{"keySource":"Microsoft.Keyvault","rotationToLatestKeyVersionEnabled":false}}},"managedResourceGroupId":"/subscriptions/7a9974b4-6ef3-490d-a02d-b9b3a07332f6/resourceGroups/databricks-rg-test-workspace3-928-v4gehmkk7v3ts","parameters":{"enableNoPublicIp":{"value":false},"natGatewayName":{"value":"nat-gateway"},"publicIpName":{"value":"nat-gw-public-ip"},"prepareEncryption":{"value":false},"encryption":{"value":{"keySource":"Microsoft.Keyvault","KeyName":"keyc","keyversion":"a9c9a6da3f024f1a83bac2588faaaaad","keyvaulturi":"https://constantkv.vault.azure.net/"}},"requireInfrastructureEncryption":{"value":false},"storageAccountName":{"value":"dbstoragen22d62mefbhki"},"storageAccountSkuName":{"value":"Standard_GRS"},"vnetAddressPrefix":{"value":"10.139"}},"authorizations":[{"principalId":"9a74af6f-d153-4348-988a-e2672920bee9","roleDefinitionId":"8e3af657-a8ff-443c-a75c-2fe8c4bcb635"}],"createdDateTime":"0001-01-01T00:00:00Z"},"sku":{"name":"premium"},"location":"eastus"}
If you see the above payload you can see that the managedDisk encryption property set is getting called and it is invalid, hence the command fails. The main concern is why is the managedDisk encryption property is being pushed here, while the command is to update DBFS encryption. Both of them are different scenarios.

This issue should be transferred to https://github.com/Azure/azure-powershell

Thanks for checking in Armaan ! Would you be able to transfer this internally or do you suggest us to file a ticket separately with Az PowerShell?


Editor options

Is it possible to have a sort of .editorconfig file to set spacing and tabbing and all that to match what you're currently using?
For example I have set my spacing for JS to 2 spaces and it formats EVERYTHING if I try to make a change..

Yep, if you're familiar with the best way to set that up, please feel free to do that and reformat everything along with the config change -- we'll stick with that going forward.

Alright. I found a tool that generates an .editorconfig based on the files in the project. Seems very basic but it'll do. I'll probably add a vscode workspace file which has a lot more options than the .editorconfig
Do you have a preference on this or should I just keep it like you've started it?

maybe we could adhere to the [classic] (https://crockford.com/javascript/code.html) style-guide?


CFR Form Reason - Always Showing as Mandatory Field

Describe the bug in current situation
While working through fee estimate test scenarios, found it confusing to see the CFR form reason as a selectable option - even when there is just the single CFR form.
CFR form reason should only need to be selected when a new form is created, and be able to be updated after the form is created - it should not always be present.
Link bug to the User Story
Impact of this bug
Impact of bug is medium - it may confuse users, as they may assume they need to take an action on that drop down when they may not
Chance of Occurring (high/medium/low/very low)
high - the drop down is always present on the CFR form
Pre Conditions: which Env, any pre-requesites or assumptions to execute steps?
Steps to Reproduce
Steps to reproduce the behavior:

Go to any general request in the fee estimate state or later, where only 1 CFR form exists.
Click on Call For Records form
See drop down for CFR form reason

Actual/ observed behaviour/ results
Expected behaviour
GIVEN a user is on the CFR form
WHEN they click on Create New Form
THEN they will be prompted to select a reason.
GIVEN a user has created a new CFR form
AND that form is NOT the orginal
WHEN they are on the CFR form
THEN they will see the reason for the new form
AND they can change the reason
Screenshots/ Visual Reference/ Source
If applicable, add screenshots to help explain your problem. You an use screengrab.

Followed steps to reproduce: When there is only a single CFR form the "Reason for Creating a New CFR Form" does not appear. When a user clicks on "Create New CFR" then the "Reason for Creating a New CFR Form" option appears.


Added 2 DSA problem

Can you please make a folder and naming it as JS program and then put your code inside that folder.


k8s ingress auth-tls-insecure annotation not working

Do you want to request a feature or report a bug?
Bug
Did you try using a 1.7.x configuration for the version 2.0?

[ ] Yes
[X] No

What did you do?
I am running traefik in a development environment with https endpoints enabled, using the default traefik SSL certificate.
I set up the following ingress definition:
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  annotations:
    ingress.kubernetes.io/auth-tls-insecure: "true"
    ingress.kubernetes.io/auth-type: forward
    ingress.kubernetes.io/auth-url: https://login.internal.local.mydomain.com/authorize
    ingress.kubernetes.io/is-development: "true"
    kubernetes.io/ingress.class: traefik
  labels:
    traffic-type: external
  name: test
  namespace: test
spec:
  rules:
  - host: test.local.mydomain.com
    http:
      paths:
      - backend:
          serviceName: test
          servicePort: http
        path: /

What did you expect to see?
I expect the forward auth request to succeed even with traefik's default SSL certificate since auth-tls-insecure is set to true.
What did you see instead?
time="2019-05-01T16:33:50Z" level=debug msg="Error calling https://login.internal.local.mydomain.com/authorize. Cause: Get https://login.internal.local.mydomain.com/authorize: x509: certificate is valid for ffe823de1a97908301ae47d48a08dc4a.64aa04c912381e9780ad2cda057623f6.traefik.default, not login.internal.local.mydomain.com"

Output of traefik version: (What version of Traefik are you using?)
1.7.10

What is your environment & configuration (arguments, toml, provider, platform, ...)?
logLevel = "DEBUG"

defaultEntryPoints = ["http", "https"]

InsecureSkipVerify = true

[entryPoints]
  [entryPoints.http]
  address = ":80"
  compress = true
    [entryPoints.http.redirect]
    entryPoint = "https"
  [entryPoints.https]
  address = ":443"
  compress = true
    [entryPoints.https.tls]
  [entryPoints.traefik]
  address = ":8080"

[api]
entrypoint = "traefik"

# Enable Kubernetes Ingress Provider.
[kubernetes]
labelselector = "traffic-type=external"

I'm running into the same issue with traefik 1.7.9.
Is there a way to provide a CA using a ingress definition? Would this solve the issue?

@tverhoeven @jwheeler-gs
	authURL := getStringValue(i.Annotations, annotationKubernetesAuthForwardURL, "")
	if len(authURL) == 0 {
		return nil, fmt.Errorf("forward authentication requires a url")
	}

	forwardAuth := &types.Forward{
		Address:             authURL,
		TrustForwardHeader:  getBoolValue(i.Annotations, annotationKubernetesAuthForwardTrustHeaders, false),
		AuthResponseHeaders: getSliceStringValue(i.Annotations, annotationKubernetesAuthForwardResponseHeaders),
	}

	authSecretName := getStringValue(i.Annotations, annotationKubernetesAuthForwardTLSSecret, "")
	if len(authSecretName) > 0 {
		authSecretCert, authSecretKey, err := loadAuthTLSSecret(i.Namespace, authSecretName, k8sClient)
		if err != nil {
			return nil, fmt.Errorf("failed to load auth secret: %s", err)
		}

		forwardAuth.TLS = &types.ClientTLS{
			Cert:               authSecretCert,
			Key:                authSecretKey,
			InsecureSkipVerify: getBoolValue(i.Annotations, annotationKubernetesAuthForwardTLSInsecure, false),
		}
	}

	return forwardAuth, nil
}

This is the code responsible for handling forwarded auth. It's quality is really low. I'm going to fix it tomorrow. Let's hope it will be merged asap.

Closed by #5319 and available in Traefik v1.7.15.


Reduce duplicate code in maven/gradle ProjectProperties

Part of Fixes #262, fixes #312.

This PR ended up getting bigger than I was hoping it would.


[BUG] Nvidia dgpu becomes unusable after using envycontrol, even after switching to hybrid mode/reset

Describe the bug
Nvidia dgpu becomes unusable after using envycontrol, even after switching to hybrid mode/reset
To Reproduce
Steps to reproduce the behavior:

Run sudo envycontrol -s integrated
Reboot
Run sudo envycontrol -s hybrid
Reboot
Try to play games using dgpu on Bottles/Steam

System Information:

Model: XPS 15 9570
Distro: Debian 12
Kernel: 6.9.7
DE/WM and Display Manager (if applicable): KDE/SDDM
EnvyControl version: 3.4.0
Nvidia driver version: 535.183.01
lspci output:

00:00.0 Host bridge: Intel Corporation 8th Gen Core Processor Host Bridge/DRAM Registers (rev 07)
00:01.0 PCI bridge: Intel Corporation 6th-10th Gen Core Processor PCIe Controller (x16) (rev 07)
00:02.0 VGA compatible controller: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630]
00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 07)
00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model
00:12.0 Signal processing controller: Intel Corporation Cannon Lake PCH Thermal Controller (rev 10)
00:14.0 USB controller: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller (rev 10)
00:14.2 RAM memory: Intel Corporation Cannon Lake PCH Shared SRAM (rev 10)
00:15.0 Serial bus controller: Intel Corporation Cannon Lake PCH Serial IO I2C Controller #0 (rev 10)
00:15.1 Serial bus controller: Intel Corporation Cannon Lake PCH Serial IO I2C Controller #1 (rev 10)
00:16.0 Communication controller: Intel Corporation Cannon Lake PCH HECI Controller (rev 10)
00:17.0 SATA controller: Intel Corporation Cannon Lake Mobile PCH SATA AHCI Controller (rev 10)
00:1b.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #17 (rev f0)
00:1c.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #1 (rev f0)
00:1c.4 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #5 (rev f0)
00:1d.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #9 (rev f0)
00:1f.0 ISA bridge: Intel Corporation Cannon Lake LPC Controller (rev 10)
00:1f.3 Audio device: Intel Corporation Cannon Lake PCH cAVS (rev 10)
00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10)
00:1f.5 Serial bus controller: Intel Corporation Cannon Lake PCH SPI Controller (rev 10)
01:00.0 3D controller: NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] (rev a1)
3b:00.0 Network controller: Intel Corporation Wireless-AC 9260 (rev 29)
3c:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01)
3d:00.0 Non-Volatile memory controller: SK hynix PC401 NVMe Solid State Drive 256GB

Additional context
I can't launch games/programs using the dgpu after using envycontrol. Only fully reinstalling the nvidia driver fixes the problem.
I have tried --reset and switching to hybrid and also rebuilding the initramfs myself.

I think the issue stems from flatpak removing the nvidia libs after a while (becomes unused)
nvidia-535-183-01                            org.freedesktop.Platform.GL32.nvidia-535-183-01                                        1.4                user
nvidia-535-183-01                            org.freedesktop.Platform.GL.nvidia-535-183-01                                          1.4                user

I went to check my logs and I can confirm that flatpak considers nvidia runtimes as unused in integrated mode. Flatpak on my system auto-updates and removes unused, so it kept deleting my nvidia runtimes in integrated mode. I would add a warning to not run flatpak uninstall --unused in integrated mode or to pin them.


[Question] The format of the alarmId value in the alarm message is incorrect and the message cannot be sent.

Question
我在使用最新版本（v1.4.2）测试告警时发现个问题，我使用的webhook接口，钉钉无法收到告警信息。排查如下：
查看webhook服务的log，发现告警信息确实可以收到，但是信息中alarmId数值不对，如：alarmId：2,104，正确格式应该是2104。

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑🤝🧑👫🧑🏿🤝🧑🏻👩🏾🤝👨🏿👬🏿

Question
I found a problem when using the latest version (v1.4.2) to test the alarm. The webhook interface I used, DingTalk could not receive the alarm information. The troubleshooting is as follows:
Check the log of the webhook service and find that the alarm information can indeed be received, but the alarmId value in the information is incorrect, such as: alarmId: 2,104. The correct format should be 2104.


CocoaPods Support

This HexFiend.podspec file allows the MAS-compatible version of HexFiend.Framework to be added as a CocoaPods dependency (which supports static linking).

It seems a little late in the game to add CocoaPods support to Hex Fiend since Xcode 11 will have native Swift Package Manager support, which I believe also works with Objective-C sources. Personally, I'm not a fan of CocoaPods since it changes so much how your project works, and I'd rather not add this just to let it go stale since I don't plan on maintaining it myself. Can we consider SPM instead?


Optimize CommonJS and module build

This PR will split our Rollup config in two: one for the CJS/ES build and one for UMD. This is a backwards compatible change. It will also address the minimized name issue that people experienced in Storybook 3+.
Bundled output (names link to the actual output):

lib - babelified source, stays the same
dist/reactstrap.cjs.js - unminified CommonJS build, pointed at from package.main
dist/reactstrap.es.js - unminified Module build, pointed at from package.module
dist/reactstrap.min.js - minified UMD build, to be included by users directly

The CJS/ES builds will not include any dependency and will not be minimized. These builds are going to be consumed by other bundlers and thus will be minimized when bundled for production (if the user chooses so). These bundles will be returned when require('reactstrap') or import Reactstrap from 'reactstrap';.
If you want to cherry pick only specific components:
With CommonJS: const Card = require('reactstrap/lib/Card');
With modules: import { Card } from 'reactstrap';
The UMD build is meant to be included directly on a webpage and will include the dependencies but not the peer dependencies. I've added a check so that when people add a peer dependency but not add it to the UMD globals object, it will fail the build.
This PR includes #474 as it was needed to generate correct builds.
CC @TheSharpieOne
Testing
To update source to run tests against the CommonJS build:
sed -i "" "s/\.\.\/\'/\.\.\/\.\.\/dist\/reactstrap.cjs'/" src/__tests__/*.spec.js

To update source to run tests against the module build:
sed -i "" "s/\.\.\/\'/\.\.\/\.\.\/dist\/reactstrap.es'/" src/__tests__/*.spec.js

To update source to run tests against the UMD build:
sed -i "" "s/\.\.\/\'/\.\.\/\.\.\/dist\/reactstrap.min'/" src/__tests__/*.spec.js

@balloob thanks! can you fix conflicts?

@eddywashere done.


[ci][schedule-run-ci]Fix ReferenceError: labeled is not defined

Fix https://github.com/AgoraIO-Extensions/Agora-Flutter-SDK/actions/runs/5241429159/jobs/9463512063

This needs to be merged directly since the pull_request_target only runs the workflow config base on the main branch, so the ci will be failed for this PR.


build.mk: improve reading version

Allow pass TAG_ID and REV_ID externally.
Suppress error output when git command failed to execute
Set the version to unknown if both of them are empty

For openwrt/packages#19998

Pushed: https://github.com/heiher/natmap/commit/25af14b662f9eae0d6ec99ee4314c3d91be41200
Thank you.


Products of contractible spaces are contractible

It's unfortunate that the mathse page The cartesian product of contractible spaces is contractible is marked as a duplicate, because it doesn't appear to be a strict duplicate. The page it's suppose to duplicate it about a product of two spaces, and this page is about arbitrary products.
This page at topospaces would be good, but "Fill this in later" appears at the bottom of the page.
Going to add some similar traits.

I changed the title of the mathse post to avoid the duplicate.  Hopefully enough people will vote to reopen the question.

I just wanted to add that the converse also holds. If $f: [0,1]\times \prod X_i \to \prod X_i$ is a contraction map of $\prod X_i$ and $p_n: \prod X_i \to X_n$ are the projection maps, then $p_n\circ f\restriction_{[0,1]\times X_n}$ is a contraction map of $X_n$.
I could find a stackexchange post about this though.

I just wanted to add that the converse also holds. If $f: [0,1]\times\prod X_i\to \prod X_i$ is a contraction map, $p_n: \prod X_i\to X_n$ is the projection and $i_n: X_n \to\prod X_i$ is an inclusion with $p_n\circ i_n = \text{id}$, then $p_n\circ f \circ (\text{id} \times i_n)$ is a contraction map of $X_n$.

@JoeF131 if you like, you could add this observation as a supplementary answer to https://math.stackexchange.com/questions/4463999/an-arbitrary-product-of-contractible-spaces-is-contractible or ask/answer the question there. Your proof would be more discoverable on the Stack Exchange network than a pi-Base PR that will be closed in a few days.

This looks good.  As a consequence of these, one could remove a few redundant traits.
Just as an example, now that we know the Hilbert cube is contractible, it is path connected.  And since it's also Hausdorff (via metrizable), it is necessarily arc connected.  Also we can probably remove the trait for indiscrete.
Not sure if we want to do this associated cleanup here or not.  In the mean time, I'll approve and leave the rest to you, including the squash and merge.


PST with square root trusted setup

Implemented the polynomial optimisation excluding the MIPP

Closing this and opening a PR with the full scheme.


Update Docs for bootstrap 4.0.0

Looks like this update was missed in 4ed40085b291c0b75e484ffc1e414b4c8d4cb152

Coverage remained the same at 86.505% when pulling c0227063f09d9d8c72e04f1fd5dd2181196fe8b3 on aprildh31:patch-1 into 1bf8f242e8fca8190ccfaae2e48439521284ec08 on zostera:master.

@aprildh31 thanks!


Misleading source info in "done() called multiple times" message

The error message "done() called multiple times" will be associated with whatever part of the test suite that's currently running. This can lead to a lot of confusion for the uninitiated developer.
For example, consider the following suite:
describe("a simple test suite", function () {
	beforeEach(function (done) {
		setTimeout(done, 150);
	});
	afterEach(function (done) {
		setTimeout(done, 50);
		setTimeout(done, 100);
	});
	it("has a simple test", function (done) {
		setTimeout(done, 100);
	});
	it("has another simple test", function (done) {
		setTimeout(done, 100);
	});
});

Running mocha done-message.js will result in:
  ․․

  1 passing (356ms)
  1 failing

  1) a simple test suite "before each" hook:
     Uncaught Error: done() called multiple times
      at multiple (/usr/local/lib/node_modules/mocha/lib/runnable.js:175:31)
      at done (/usr/local/lib/node_modules/mocha/lib/runnable.js:181:26)
      at null._onTimeout (/usr/local/lib/node_modules/mocha/lib/runnable.js:197:9)
      at Timer.listOnTimeout [as ontimeout] (timers.js:110:15)

Note how the "done() called multiple times" will be listed having the beforeEach hook as the point where it came from. This is of course wrong, the beforeEach simply happens to be the active code part when the second done() call is being run. Additionally, the second test gets marked as a failure, even though it did nothing wrong!
I don't know Mocha's internals, so I don't know whether this can be fixed easily at all.  Some ideas:

Pass a new done callback to the tests each time, that has the source information as a closure variable?
Change the error reporting so that the done error message is not associated to any code part at all?
Make it clear in the error message that this message can literally come from everywhere?
Make double-done-calling a fatal error that causes the entire suite to stop and tell the user that the second call to done can come from anywhere?

Tested with Mocha 1.15.1. This issue may or may not be related to #990.

More examples:
describe("a simple test suite", function () {
	beforeEach(function (done) {
		setTimeout(done, 150);
	});
	afterEach(function (done) {
		setTimeout(done, 200);
		done();
	});
	it("has a simple test", function (done) {
		setTimeout(done, 100);
	});
	it("has another simple test", function (done) {
		setTimeout(done, 100);
	});
});

This will cause the error to be associated to the second test.

describe("a simple test suite", function () {
	beforeEach(function (done) {
		setTimeout(done, 150);
	});
	afterEach(function (done) {
		done();
		done();
	});
	it("has a simple test", function (done) {
		setTimeout(done, 100);
	});
	it("has another simple test", function (done) {
		setTimeout(done, 100);
	});
});

This will result in no error at all, even though done gets called multiple times!

@gardner I used your fix for the same issue in relation to sailsjs and it has fixed my issue but is this correct or should I have done something else? Thanks.

I just stumbled into the same issue and wrote a little wrapper-class for the done-function:
/**
 * Wrapper-Class for done-function
 * @param {Function} fn
 * @class {Done}
 */
function Done(fn) {
    var self   = this;
    var called = false;

    /**
     *
     * @param {*} params...
     */
    this.trigger = function (params) {
        if(called) {
            console.warn("done has already been called");
            console.trace();

            return;
        }

        fn.apply(self, arguments);
        called = true;
    };
}

Usage:
it('should test', function (fn) {
    var doneWrap = new Done(fn);

    myAsyncFn(function () {
        // ...

        doneWrap.trigger();
    });
});

@gardner I'm seeing the same behavior with SailsJS, do you have a bug you can reference? I can't seem to find one.

There's a related mocha bug: https://github.com/mochajs/mocha/issues/1066
I can't find a sailsjs bug. It looks like issues are closed without much investigation on that project.

Still happening even today.

@CodeJjang How so?  Can you provide code?  I want to know if this hasn't been completely fixed.  Note that if you call done multiple times, you should get an error that done was called multiple times.

@boneskull of course that if you call it multiple times then you should get the message.
I had a done call in a timer in the before (before all) hook, in this manner:
.then(setTimeout(done, 50))

@CodeJjang That setTimeout is evaluated immediately and not as part of the .then flow. No wonder that does weird things

Yep, indeed my bad.
changed to
.then(() => {
				setTimeout(done, 4000);
				return Promise.resolve();
			})

and worked.

Using done and promise resolution in the same flow also seems wierd. You could just return your promise in your hook. That works equally well, without a done callback alltogether


Improvement points

Hi, first I want to congratulate you on this great library.
Previously I was using an older one https://pub.dev/packages/country_picker that had some great features that your library might benefit as well.

Factory to create countrycode
CountryCode.fromCountryCode(selectionItem.value!).localize(context)

Localization is not working for me.
I am changing the app locale in runtime and the picker language is still not updated

Allow to have no favorite icon. This is super useful and supported by the other library, you have no icon there but an elegant divider between the favorites on top and the remaining options

add kosovo country

expose flagUri in the country code instead of the flagImage  Widget type. Why ? Because the user might want to render it differently, like in the previous library you can get the Uri of the svg and render yourself for instance

Image.asset(
      countryInfo!.flagUri!,
      package: 'country_code_picker',
      width: 32,
    );

Hello 👋. I'll try to implement this.
I'm looking forward to this week.
Thanks for suggestion!

This issues are now addressed at commit 9f255cc.
Last thing, I'll just update the CHANGELOG and Readme files.
Thank you!

https://pub.dev/packages/fl_country_code_picker/versions/0.1.0
Update v0.1.0 🥳

feat: add support for localization
feat: exposed the flagUri for flag image customization
feat: add visibility flag for favorite icon
refactor: enable customization for modal's title
refactor: add Kosovo country

Thank you for using my package! 😊


Allow setting a default value in autocomplete component

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Summary 💡
Like other components, I should be able to set a default value in autocomplete.
Examples 🌈
No response
Motivation 🔦
No response

let me try.this bug

@Janpot maybe should close this pr


Search Field - Make the search field and the top banner responsive

Made a temporary workaround for search field responsiveness.


Replacement syntax for non-LaTeX text

Hi! I really love this plugin, and the LaTeX replacement feature is great, especially the ability to tab around between different placeholder sections.
However, I was wondering if it would be possible to expand this system to work in non-LaTeX sections too. Some examples of situations that this would come in really handy are:

Creating a custom command that allows replacing fractions with their unicode version, where typing 1/2 would bring up the suggestion to replace it with ½.
Creating custom template-style sections of frontmatter that you often use, where each line could have a replacement character in it so that you can quickly insert the section and then tab through the values that need to be set.

Of course, these are just two examples I came up with, but I think this system would be very useful outside of LaTeX environments overall.
I realize that this might be slightly out of scope of the "completion" theme that the plugin currently has. But I also think that it might be a nice fit due to the fact that some LaTeX replacement commands in the plugin already have an "input" syntax that is much simpler than the output that they generate, like all of the region-related commands.

Hey, thanks for your feedback! Definitely a cool idea to generalize this system.


Cannot compile statically

Hi!
Simple project with src/test.cr
require "llvm/lib_llvm"
require "llvm/enums"

puts "123"

Execute: docker run --rm -it -v $PWD:/app -w /app jrei/crystal-alpine crystal build --static --release src/test.cr
and gets:
/usr/lib/gcc/x86_64-alpine-linux-musl/8.3.0/../../../../x86_64-alpine-linux-musl/bin/ld: cannot find -lstdc (this usually means you need to install the development package for libstdc)++
collect2: error: ld returned 1 exit status
Error: execution of command failed with code: 1: cc "${@}" -o '/app/test'  -rdynamic -static  /usr/bin/llvm-config --libs --system-libs --ldflags --link-static 2> /dev/null -lstdc++ /usr/lib/libpcre.a /usr/lib/libgc.a /usr/lib/libpthread.a /usr/lib/crystal/core/ext/libcrystal.a /usr/lib/libevent.a /usr/lib/librt.a -L/usr/lib -L/usr/local/lib
And i think docker project page have broken description

Thanks @foi. g++ was removed because a C++ compiler wasn't needed, but libstdc++.a is present on this package. I can create a PR to https://github.com/alpinelinux/aports to move to a dedicated libstdc++-dev package.
For Docker, yes I've noticed they no longer support markdown code blocks, too bad.


[Bug]: snowflake_account resource error due to 2024_06 bundle change

Terraform CLI Version
1.8.5
Terraform Provider Version
0.94.1
Terraform Configuration
terraform {
  required_version = "1.8.5"
}

terraform {
  required_providers {
    snowflake = {
      source  = "Snowflake-Labs/snowflake"
      version = "0.94.1"
    }
  }
}

variable "snowflake_org_user" {
  type = string
}

variable "snowflake_org_account" {
  type = string
}

variable "admin_password" {
  type      = string
  sensitive = true
}

provider "snowflake" {
  user          = var.snowflake_org_user
  account       = var.snowflake_org_account
  role          = "ORGADMIN"
}

resource "snowflake_account" "this" {
  name           = "BUG_TEST"
  admin_name     = "TEST_ADMIN"
  admin_password = var.admin_password
  email          =<EMAIL_ADDRESS>  comment        = "Managed by Terraform"
  edition        = "STANDARD"
}

Category
category:sdk
Object type(s)
resource:account
Expected Behavior
Running terraform apply on the above configuration and confirming the plan should create a new account and complete without error.
Actual Behavior
As of 8/27, when I run terraform apply and confirm the plan, I get the following error:
Error: giving up after 5 attempts

  with snowflake_account.this,
  on main.tf line 33, in resource "snowflake_account" "this":
  33: resource "snowflake_account" "this" {

The account does get created, but the state isn't saved because of the error.
Steps to Reproduce
To reproduce the error:

Run SELECT SYSTEM$SHOW_ACTIVE_BEHAVIOR_CHANGE_BUNDLES(); to check that the 2024_06 bundle is enabled in your account.  If not, run SELECT SYSTEM$ENABLE_BEHAVIOR_CHANGE_BUNDLE('2024_06');
Run the provided code as a user with the org_admin role
Run terraform apply and confirm the plan

How much impact is this issue causing?
Medium
Logs
https://gist.github.com/sbrudz/363aedc61c209e86958e67d2aad3350a
Additional Information
The 2024_06 bundle became enabled by default on August 26-27.  This bundle changes the behavior of the SHOW ORGANIZATION ACCOUNTS command.
The workaround is to disable the 2024_06 bundle:
SELECT SYSTEM$DISABLE_BEHAVIOR_CHANGE_BUNDLE('2024_06');

It seems like this could be fixed by using SHOW ACCOUNTS instead of SHOW ORGANIZATION ACCOUNTS within the Accounts SDK.
Would you like to implement a fix?

[ ] Yeah, I'll take it 😎

Hey @sbrudz 👋
Thank you for reporting this issue. I'll change the SHOW command to the newer one. The fix should be present in the newest release.

Excellent! Thank you, @sfc-gh-jcieslak!

@sfc-gh-jcieslak thanks for the prompt response!
As far as you know, is there an official policy to align the release of this provider with the official Snowflake releases? I'm creating an internal process around Snowflake updates.

Hey @marcofunaro. You are right, there is no alignment currently. We will discuss the release's cadence after reaching a stable V1.

do you want me to open an issue for tracking purposes?

As a side note, we have also encountered this issue and it was very hard to debug.
It appears that the current implementation is swallowing the error and is not logging it in any way making it hard do understand the root cause. would be nice if we could have an error message here when retrying.

Hey all 👋
Yesterday, we released a new provider version (v0.95.0). Please upgrade and let us know if the issue disappeared.
@marcofunaro I think there's no need for that. We are aware of the issue and will communicate to you any decision we'll make on that most likely through GitHub discussions.
@asafcyclops Thank You for pointing this out, we already created a task for that and will try to address it as part of the next release.

Confirming that the issue is fixed for us after upgrading to v0.95.0.  Thank you, @sfc-gh-jcieslak!


Fix: Replace internal docs action

Description and Motivation

Docs were previously built by the internal docs action. Because this repo is now open-source, it cannot use internal (closed source) actions - this is enforced by GitHub and cannot be worked around.
Instead the docs publishing step has been replaced by a script which installs the internal docs parser as a package and manually packages and pushes up the built docs to Artifactory.
The script was added to a new tooling folder, necessary steps were added to Makefile and release workflow was updated.
Additional Context

Changes based on these PRs in dara:

PR 42
PR 44
PR 47

How Has This Been Tested?

Cannot be tested yet until new JFrog secrets are added to repo. Will test pushing a dev tag from this branch; unsure if this will suitably test the version bump commit when doing release from main branch as it has branch protection.
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Improvement (non-breaking change which improves functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Refactor (moving code around, general refactoring improvements)
[ ] Documentation (documentation)

PR Checklist:

[x] I have reviewed my own PR? (review the PR as you are reviewing someone else's PR)
[x] I have implemented all requirements? (see JIRA, project documentation)
[x] I am affecting someone else's work? If so: I have added those people as reviewers?
[x] I have added comments to all the bits that are hard to follow
[x] At a bare minimum, I tested this manually
[ ] I have added unit test(s)
[ ] Is this a bugfix? If so have I added a regression test?
[x] Does this PR satisfy the one PR, one concern rule?
[ ] If needed, documentation has been added/updated?
[x] I have updated the appropriate changelog with a line for my changes
[ ] If this PR breaks reproducibility, have I added a note in the changelog explaining the break in reproducibility
and its extent?

Screenshots (if appropriate):

@andrew-causalens Sorry this may be a naive question but why don't we just redirect / link the user to the open source docs instead of duplicating it in the internal?

@andrew-causalens Sorry this may be a naive question but why don't we just redirect / link the user to the open source docs instead of duplicating it in the internal?

The doc website is built from the packaged docs hosted on artifactory. I discussed this with @sam-causalens when we first started planning how to host the public docs and decided this was the simplest. This is also what Dara does too.

Looks good to me. You might want to revert the poetry.lock and pyproject.toml changes related to dev releases? But, no worries if not, the next release will override these.

I plan to release 0.1.1 from main so will leave.


New version WeakRefStrings: 0.6.0

Registering: WeakRefStrings
Repository: https://github.com/JuliaData/WeakRefStrings.jl
Version: v0.6.0
Commit: caf4ed477e493309d12502ab0984eec157120925
Proposed by: @quinnj
Reviewed by: @quinnj
Reference: https://github.com/JuliaData/WeakRefStrings.jl/commit/caf4ed477e493309d12502ab0984eec157120925#commitcomment-33285524

Consider enabling TagBot to make sure the release is persistent in your repo, see https://discourse.julialang.org/t/ann-tagbot-creates-tags-and-releases-for-your-julia-packages-when-theyre-registered/23084