text:
Trying to deploy Function Bicep app via Pipeline

Im trying to deploy my function app that allows the user to pick their environment like staging or UAT, picking a location and the name of their storage account.
Im running into these errors above so not sure why I need to do

Please reach out. What is the actual error?

Also, @daradona10 - are you seeing any error information in vs code itself? Are any files marked in red or have any red squiggles? There should be more detail to the error message than what you are seeing I think.

Hi guys. sorry for the late reply and thanks for responding. I think I have it sorted now. I opened up another query about choosing to between an app service plan and consumption plan when deploying through pipelines but I can't figure it out yet.
#6298

authors: alex-frankel daradona10 pinakighatak

repo: Azure/bicep


text:
Deployment of Container Apps Managed Environment fails when the 'appLogsConfiguration' property uses conditions

Bicep version
Bicep CLI version 0.14.85 (f4a4d485ba)
Describe the bug
Trying to develop a module that deploys an Azure Container Apps Managed Environment. One of the properties of this service is to specify the appLogsConfiguration.
In this property, we can specify the 'destination' type. Although the documentation does not call out the supported types, using the Azure Portal, we determined there are three options that can be supported: ['', 'log-analytics', 'azure-monitor'].

Based on that we wanted to apply these options in the module. The below shows the bicep code:

@description('Required. Name of the Container Apps Managed Environment.')
param name string

@description('Optional. Location for all Resources.')
param location string = resourceGroup().location

@description('Conditional. Existing Log Analytics Workspace resource ID. Required if "logDestination" is set to "log-analytics".')
param logAnalyticsWorkspaceResourceId string = ''

@allowed([
  'azure-monitor'
  'log-analytics'
  ''
])
@description('Optional. Logs destination. Default value streams logs without storing them.')
param logsDestination string = ''

resource logAnalyticsWorkspace 'Microsoft.OperationalInsights/workspaces@2022-10-01' existing = if (!empty(logAnalyticsWorkspaceResourceId)) {
  name: last(split(logAnalyticsWorkspaceResourceId, '/'))!
  scope: resourceGroup(split(logAnalyticsWorkspaceResourceId, '/')[2], split(logAnalyticsWorkspaceResourceId, '/')[4])
}

resource managedEnvironment 'Microsoft.App/managedEnvironments@2022-10-01' = {
  name: name
  location: location
  properties: {
    appLogsConfiguration: !empty(logsDestination) ? {
      destination: logsDestination
      logAnalyticsConfiguration: logsDestination == 'log-analytics' ? {
        customerId: logAnalyticsWorkspace.properties.customerId
        sharedKey: logAnalyticsWorkspace.listKeys().primarySharedKey
      } : null
    } : {}
  }
}

In this template, we wrote a condition for the logAnalyticsConfiguration so that it is only used when the logAnalyticsWorkspaceResourceId is provided, but set to null if not.
When deploying this template with the following spec:

logsDestination = '' --> Success
logsDestination = 'azure-monitor' --> Success
logsDestination = 'log-analytics'  --> Fail and we get the below error:

Deployed failed with provisioning state [Failed]. Error Message: [The template deployment 'cinjzsv67eycm-test-amecom' is not valid according to the validation procedure. The tracking id is '352dfe6d-77bd-4248-9b96-fe5553ba4700'. See inner errors for details. (Code: InvalidTemplateDeployment) - Validation failed for a resource. Check 'Error.Details[0]' for more information. (Code: ValidationForResourceFailed)
   - Invalid request body for environment. Path: $.appLogsConfiguration. Does not conform to Managed Environment schema, please visit for more information https://docs.microsoft.com/azure/container-apps/azure-resource-manager-api-spec?tabs=arm-template#container-apps-environment (Code:ManagedEnvironmentInvalidSchema)

]. Please review the Azure logs of deployment [a-me-common-t1-20230303T1503488392Z] in scope [subscription] for further details.

What we noticed, is that conditions just don't work when they are near this property, so the only way we got this template to work is by only supporting one logDestination and that is log-analytics, like the below:

resource managedEnvironment 'Microsoft.App/managedEnvironments@2022-10-01' = {
  name: name
  location: location
  properties: {
    appLogsConfiguration: {
      destination: 'log-analytics'
      logAnalyticsConfiguration: {
        customerId: logAnalyticsWorkspace.properties.customerId
        sharedKey: logAnalyticsWorkspace.listKeys().primarySharedKey
      }
    }
  }
}

To Reproduce
Deploy the first template referenced in this issue, and set the logDestination to log-analytics and provide the logAnalyticsWorkspaceResourceId.
Additional context
We realize this may not be an issue related to bicep, but we thought of raising it here as a start and get guidance on the error related to the schema
" Invalid request body for environment. Path: $.appLogsConfiguration. Does not conform to Managed Environment schema"

Agreed that this is not a bicep specific issue. I would recommend opening a support case for this one, so it can be triaged by the container apps team.
It may also be helpful to open an issue here: https://github.com/microsoft/azure-container-apps

source: gharchive/issue

authors: ahmadabdalla alex-frankel

license: MIT

license_type: permissive

license_source: github-api


text:
Property name completions

Added completions for property names (includes discriminated object types)
Improved error recovery and coloring for malformed or incomplete object properties
Newlines are no longer part of object and object property nodes in the AST.
Added helpers for tracking syntax node parents
Added contextual/declared type tracking to the TypeAssignmentVisitor

Next steps:

Current declared type flowing logic relies on the type assignment visitor being called on the entire program even though the contract implies it is deferred until requested. This will be refactored in another PR.
Completions for property values, resource type names and versions, etc. are coming in subsequent PRs.

Completions inside a deeply nested object inside an array:

Missing discriminator:

Discriminator property set:

Properties inside:

Codecov Report

Merging #643 into master will decrease coverage by 0.14%.
The diff coverage is 98.86%.

@@            Coverage Diff             @@
##           master     #643      +/-   ##
==========================================
- Coverage   95.06%   94.92%   -0.15%
==========================================
  Files         248      251       +3
  Lines        9671     9944     +273
==========================================
+ Hits         9194     9439     +245
- Misses        477      505      +28

Flag
Coverage Δ

#dotnet
94.92% <98.86%> (-0.15%)
:arrow_down:

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

Impacted Files
Coverage Δ

src/Bicep.Core/Syntax/SyntaxBase.cs
76.00% <ø> (+1.92%)
:arrow_up:

src/Bicep.Core/Syntax/SyntaxVisitor.cs
96.85% <ø> (-0.05%)
:arrow_down:

....LangServer/Completions/BicepCompletionProvider.cs
97.24% <90.47%> (-2.76%)
:arrow_down:

...p.LangServer/Completions/BicepCompletionContext.cs
98.24% <94.11%> (-1.76%)
:arrow_down:

src/Bicep.Core/Parser/Parser.cs
94.65% <98.27%> (-0.10%)
:arrow_down:

src/Bicep.Core/TypeSystem/TypeAssignmentVisitor.cs
98.59% <98.58%> (-0.78%)
:arrow_down:

src/Bicep.Core.UnitTests/Parser/LexerTests.cs
100.00% <100.00%> (ø)

...Core.UnitTests/SemanticModel/SymbolContextTests.cs
88.23% <100.00%> (ø)

...icep.Core.UnitTests/Syntax/SyntaxHierarchyTests.cs
100.00% <100.00%> (ø)

...UnitTests/TypeSystem/TypeAssignmentVisitorTests.cs
100.00% <100.00%> (ø)

... and 38 more

Can this "right-side" menu that shows the types and enums be opened by default?

Should intellisense for properties open automatically when I input a newline? Right now I have to do ctrl + space. Maybe that could be a user setting. Glancing quickly at TS they do it in certain scenarios, but not all

It is interesting that for deploymentScripts, we ask for the discriminator (kind) first before even common properties like name. Is that a reflection of how the swagger is authored? I would have expected intellisense to show kind and all the common top level properties in one list. Does that make sense?

Can this "right-side" menu that shows the types and enums be opened by default?

I just looked into it and there doesn't appear to be a setting that controls this. Take a look at https://code.visualstudio.com/docs/editor/intellisense and search for "quick info". It appears that if you press Ctrl+Space while the completions list is open on the screen, it switches the two modes and remembers it for next time.
TypeScript does exactly what we're doing here. They populate the completion detail even though it gets cut off when the completion quick info is collapsed. OmniSharp doesn't seem to bother with detail at all and relies purely on the view being expanded. (OmniSharp also customizes the rendering of their completions a bit.)
I haven't spent much time on the TS side of the extension, but I suspect that we could completely take over the rendering of completions. A separate question is whether we should deviate from the typical VS code UX. @shenglol, thoughts? (Also probably out of scope for 0.2, but something we should figure out for future milestones.)

It is interesting that for deploymentScripts, we ask for the discriminator (kind) first before even common properties like name. Is that a reflection of how the swagger is authored? I would have expected intellisense to show kind and all the common top level properties in one list. Does that make sense?

That's a good point. Note that in the Bicep type system, the Bicep.Core.TypeSystem.DiscriminatedObjectType has no notion of 'common properties' unless we calculate them on demand. However the serialized equivalent (Bicep.SerializedTypes.Concrete.DiscriminatedObjectType) does store BaseProperties to save space. Perhaps we should consider supporting BaseProperties in the Bicep type system for this use case?

I agree, I think the experience would be better if we improve this part. I would want that to be fixed in the type system, though. I don't want IntelliSense to be making any decisions about consolidating types - it just needs to be querying the type system. The one thing we have to be careful about is whether they truly are the same properties. If the definition in the original swagger is shared between the discriminated schemas, then it's probably a safe assumption. But if there are properties with the same name and different definitions, we probably shouldn't treat them as the same (at least not initially).

Should intellisense for properties open automatically when I input a newline? Right now I have to do ctrl + space. Maybe that could be a user setting. Glancing quickly at TS they do it in certain scenarios, but not all

We do control this somewhat by specifying trigger characters (characters in addition to common identifier characters that trigger completions) and commit characters (non-standard characters that commit the selected completion - I'm using : in property names this way). I will try to see if newlines can be a trigger character.
Btw, I didn't see newlines triggering completions in TypeScript. In which scenario do they do it?

Btw, I didn't see newlines triggering completions in TypeScript. In which scenario do they do it?

I should have been more clear. I haven't seen it on newline, but do see it on dot-property access. I only meant that they have some rationale for showing it "automatically" in certain scenarios, but not all.

I should have been more clear. I haven't seen it on newline, but do see it on dot-property access. I only meant that they have some rationale for showing it "automatically" in certain scenarios, but not all.

The LSP protocol allows us to specify a global list of trigger characters (specific to bicep language). VS code uses identifier characters plus the set of trigger chars to automatically show completions. The rationale I believe should be, "does this character start something we have completions for?". My plan is to use these characters for triggers: :, space, tab, ., (, and ,.
We also have the ability to specify global and per-completion commit characters (in addition to enter or tab that seem to be controlled through VS code settings). For now, I'm not planning any global commit chars and I'm specifying : as a commit char on property name completions. The effect of this is that typing : when property name completions are visible, chooses that completion and types the colon afterward.

If the definition in the original swagger is shared between the discriminated schemas, then it's probably a safe assumption.

+1 to this. BaseProperties are only taken from shared base definitions in swagger.

I updated my trigger characters comment with a table of reasons.

Also looked into making space a trigger character right now. I think we will need to build up more accuracy in other places first before space becomes viable (was originally planning to add triggers at the end after all the PRs go in).
@alex-frankel if you want to play around with various triggers, it's easy to change BicepCompletionHandler similarly to this:

I don't know if there's a way to take over the rendering, and I doubt that's possible. Personally, I prefer not showing the types by default don't customize the behavior. My experience is that while typing I don't really care about types unless there are errors.

Do you think we should get rid of detail? TS seems to set it but OmniSharp does not.

Do you think we should get rid of detail? TS seems to set it but OmniSharp does not.

I think we should keep it. Although it may get cut off, it can hint users that there's information. Btw, the JetBrain IDEs do this, too.

source: gharchive/pull-request

authors: alex-frankel anthony-c-martin codecov-io majastrz shenglol


text:
Add case for header If-Modified-Since and If-Unmodified-Since

we could refer to real service https://github.com/search?q=repo%3AAzure%2Fazure-rest-api-specs+if-modified-since&type=code

fixed by https://github.com/Azure/cadl-ranch/pull/708

repo: Azure/cadl-ranch


text:
Private endpoint subnet present in online implementation when it is not in use

** Describe the bug **
have a Private  subnet in our RI even though it is not in use by any required resource
Expected behavior
Remove the Private subnet and its NSG from our RI

If we use ACR, then this should be needed

sound good

authors: hieumoscow mosabami


text:
Move roleHint to CallAdapter

What

This PR removes the prop roleHint from CallComposite and adds it to CallAdapterClientState .
Why

https://skype.visualstudio.com/SPOOL/_workitems/edit/3030206
How Tested

Tested on local calling sample
Process & policy checklist

[ ] I have updated the project documentation to reflect my changes if necessary.
[ ] I have read the CONTRIBUTING documentation.

Is this a breaking change?

[ ] This change causes current functionality to break.

Lets see if we could find a better solution of condtional compilation, other than that I am more than happy to approve this

authors: PorterNan mgamis-msft

repo: Azure/communication-ui-library


text:
[Bug]: System.NotSupportedException: Specified method is not supported [GraphQL]

What happened?
First I ran into that I could not have an entity named Query as that clashed with HotChocolate and was already registered.
After changing Query to QueryEntity I run into this error when using GraphQL, REST works fine
When trying to use the GraphQL endpoint I get this error:

I expected to get a 200 OK response.
Version
Happens on multiple versions, this is 0.13.0-rc
What database are you using?
Azure SQL
What hosting model are you using?
Container Apps
Which API approach are you accessing DAB through?
REST, GraphQL
Relevant log output
fail: Microsoft.AspNetCore.Server.Kestrel[13]
      Connection id "0HN3EHLT5ACMT", Request id "0HN3EHLT5ACMT:00000002": An unhandled exception was thrown by the application.
      System.NotSupportedException: Specified method is not supported.
         at ResolverTypeInterceptor.OnBeforeCompleteType(ITypeCompletionContext completionContext, DefinitionBase definition, IDictionary`2 contextData) in /_/src/Core/Services/ResolverTypeInterceptor.cs:line 67
         at HotChocolate.Configuration.AggregateTypeInterceptor.OnBeforeCompleteType(ITypeCompletionContext completionContext, DefinitionBase definition, IDictionary`2 contextData)
         at HotChocolate.Types.TypeSystemObjectBase`1.OnBeforeCompleteType(ITypeCompletionContext context, DefinitionBase definition, IDictionary`2 contextData)
         at HotChocolate.Types.TypeSystemObjectBase`1.CompleteType(ITypeCompletionContext context)
         at HotChocolate.Configuration.TypeInitializer.<CompleteTypes>g__CompleteType|27_0(RegisteredType registeredType)
         at HotChocolate.Configuration.TypeInitializer.ProcessTypes(TypeDependencyKind kind, Func`2 action)
         at HotChocolate.Configuration.TypeInitializer.CompleteTypes()
         at HotChocolate.Configuration.TypeInitializer.Initialize()
         at HotChocolate.SchemaBuilder.Setup.InitializeTypes(SchemaBuilder builder, IDescriptorContext context, IReadOnlyList`1 types, LazySchema lazySchema)
         at HotChocolate.SchemaBuilder.Setup.Create(SchemaBuilder builder, LazySchema lazySchema, IDescriptorContext context)
         at HotChocolate.SchemaBuilder.Create(IDescriptorContext context)
         at HotChocolate.SchemaBuilder.HotChocolate.ISchemaBuilder.Create(IDescriptorContext context)
         at HotChocolate.Execution.RequestExecutorResolver.CreateSchemaAsync(NameString schemaName, RequestExecutorSetup options, RequestExecutorOptions executorOptions, IServiceProvider serviceProvider, TypeModuleChangeMonitor typeModuleChangeMonitor, CancellationToken cancellationToken)
         at HotChocolate.Execution.RequestExecutorResolver.CreateSchemaServicesAsync(NameString schemaName, RequestExecutorSetup options, CancellationToken cancellationToken)
         at HotChocolate.Execution.RequestExecutorResolver.GetRequestExecutorNoLockAsync(NameString schemaName, CancellationToken cancellationToken)
         at HotChocolate.Execution.RequestExecutorResolver.GetRequestExecutorAsync(NameString schemaName, CancellationToken cancellationToken)
         at HotChocolate.Execution.RequestExecutorProxy.GetRequestExecutorAsync(CancellationToken cancellationToken)
         at HotChocolate.AspNetCore.HttpPostMiddlewareBase.HandleRequestAsync(HttpContext context, AllowedContentType contentType)
         at HotChocolate.AspNetCore.HttpPostMiddlewareBase.InvokeAsync(HttpContext context)
         at Microsoft.AspNetCore.Builder.EndpointRouteBuilderExtensions.<>c__DisplayClass12_0.<<UseCancellation>b__1>d.MoveNext()
      --- End of stack trace from previous location ---
         at Microsoft.AspNetCore.Routing.EndpointMiddleware.<Invoke>g__AwaitRequestTask|6_0(Endpoint endpoint, Task requestTask, ILogger logger)
         at Azure.DataApiBuilder.Core.Authorization.ClientRoleHeaderAuthorizationMiddleware.Invoke(HttpContext httpContext) in /_/src/Core/Authorization/ClientRoleHeaderAuthorizationMiddleware.cs:line 35
         at Microsoft.AspNetCore.Authorization.AuthorizationMiddleware.Invoke(HttpContext context)
         at Azure.DataApiBuilder.Core.AuthenticationHelpers.ClientRoleHeaderAuthenticationMiddleware.InvokeAsync(HttpContext httpContext) in /_/src/Core/AuthenticationHelpers/ClientRoleHeaderAuthenticationMiddleware.cs:line 139
         at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.Invoke(HttpContext context)
         at Azure.DataApiBuilder.Service.Startup.<>c__DisplayClass15_0.<<Configure>b__3>d.MoveNext() in /_/src/Service/Startup.cs:line 334
      --- End of stack trace from previous location ---
         at Swashbuckle.AspNetCore.SwaggerUI.SwaggerUIMiddleware.Invoke(HttpContext httpContext)
         at Azure.DataApiBuilder.Core.Services.PathRewriteMiddleware.InvokeAsync(HttpContext httpContext) in /_/src/Core/Services/PathRewriteMiddleware.cs:line 89
         at Azure.DataApiBuilder.Core.Services.CorrelationIdMiddleware.Invoke(HttpContext httpContext) in /_/src/Core/Services/CorrelationIdMiddleware.cs:line 53
         at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpProtocol.ProcessRequests[TContext](IHttpApplication`1 application)

Code of Conduct

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

Hi @seantleonard thanks for the swift reply,
The error message when I had an entity named Query was clear enough I would say.
The error message posted if after I changed my config to rename the "query" entity.
After the changes my config for the entity looks like this:
"QueryEntity": {
"source": {
"object": "srv.Queries",
"type": "table"
},
"graphql": {
"enabled": true,
"type": {
"singular": "QueryEntity",
"plural": "Queries"
}
},
"rest": {
"enabled": true
}
I do not have any references to the Query entity other places in the config, so I am quite puzzled by what is now wrong.

So now that you have your entity named "QueryEntity" you're still seeing the following error you originally reported?

Connection id "0HN3EHLT5ACMT", Request id "0HN3EHLT5ACMT:00000002": An unhandled exception was thrown by the application.
System.NotSupportedException: Specified method is not supported.

Can you provide your db table schema for srv.Queries + DAB config for that entity (entity + permissions) so I can ensure I'm getting exact repro of what you're experiencing?

Sorry for the slow reply. I semi forgot about this and was then sick for 1½ week.
I assume this is what you want for the table? (Its system versioned, if that matter anything)
CREATE TABLE [srv].[Queries](
[QueryId] [int] IDENTITY(1,1) NOT NULL,
[QueryName] varchar NOT NULL,
[ApplicationReference] [int] NOT NULL,
[DatasetReference] [int] NOT NULL,
[QueryDescription] varchar NULL,
[QueryType] varchar NOT NULL,
[QueryDefinition] varchar NULL,
[QueryParameters] varchar NULL,
[QueryGroup] varchar NULL,
[QueryEnabled] [bit] NOT NULL,
[Tag] varchar NULL,
[ValidFrom] datetime2 GENERATED ALWAYS AS ROW START HIDDEN NOT NULL,
[ValidTo] datetime2 GENERATED ALWAYS AS ROW END HIDDEN NOT NULL,
CONSTRAINT [PK_srv_Queries] PRIMARY KEY CLUSTERED
(
[QueryId] ASC
)WITH (STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, OPTIMIZE_FOR_SEQUENTIAL_KEY = OFF) ON [PRIMARY],
PERIOD FOR SYSTEM_TIME ([ValidFrom], [ValidTo])
) ON [PRIMARY] TEXTIMAGE_ON [PRIMARY]
WITH
(
SYSTEM_VERSIONING = ON (HISTORY_TABLE = [srv].[QueriesHistory])
)
GO
ALTER TABLE [srv].[Queries]  WITH CHECK ADD  CONSTRAINT [FK_srv_Queries_srv_Applications] FOREIGN KEY([ApplicationReference])
REFERENCES [srv].[Applications] ([ApplicationId])
GO
ALTER TABLE [srv].[Queries] CHECK CONSTRAINT [FK_srv_Queries_srv_Applications]
GO
ALTER TABLE [srv].[Queries]  WITH CHECK ADD  CONSTRAINT [FK_srv_Queries_srv_Datasets] FOREIGN KEY([DatasetReference])
REFERENCES [srv].[Datasets] ([DatasetId])
GO
ALTER TABLE [srv].[Queries] CHECK CONSTRAINT [FK_srv_Queries_srv_Datasets]
GO
config part for the entity looks like this:
"QueryEntity": {
"source": {
"object": "srv.Queries",
"type": "table"
},
"graphql": {
"enabled": true,
"type": {
"singular": "QueryEntity",
"plural": "Queries"
}
},
"rest": {
"enabled": true
},
"permissions": [
{
"role": "PlatformEngineer",
"actions": [
{
"action": "*"
}
]
},
{
"role": "PlatformOperator",
"actions": [
{
"action": "read"
}
]
},
{
"role": "DataAnalyst",
"actions": [
{
"action": "read"
}
]
},
{
"role": "PlatformEngineer",
"actions": [
{
"action": "read"
}
]
}
],
"relationships": {
"applications": {
"cardinality": "one",
"target.entity": "Application",
"source.fields": [
"ApplicationReference"
],
"target.fields": [
"ApplicationId"
]
},
"datasets": {
"cardinality": "one",
"target.entity": "Dataset",
"source.fields": [
"DatasetReference"
],
"target.fields": [
"DatasetId"
]
}
}
}
Let me know if you need anything else :)

authors: Kennedine seantleonard

repo: Azure/data-api-builder


text:
Wrong references for service connections in multi-tenant pipeline

References are using non-existent variables
https://github.com/Azure/enterprise-azure-policy-as-code/blob/main/StarterKit/Pipelines/AzureDevOps/multi-tenant-pipeline.yml
There was a resource authorization issue: "The pipeline is not valid. Job planJob: Step planStep input ConnectedServiceNameARM references service connection $(tenantPlanServiceConnection) which could not be found. The service connection does not exist or has not been authorized for use. For authorization details, refer to https://aka.ms/yamlauthz. Job planJob: Step planStep input ConnectedServiceNameARM references service connection $(tenantPlanServiceConnection) which could not be found. The service connection does not exist or has not been authorized for use. For authorization details, refer to https://aka.ms/yamlauthz."
I assume those shall be refering to tenant $(tenantXPlanServiceConnection) instead

Correct. Currently, I do not have a multi-tenant environment at my disposition which makes it hard to tesr. Thank you for finding the issues. I will add it to the next minor release. Probably v6.1.1

Fixed starter kit in v6.1.1

authors: artisticcheese techlake

repo: Azure/enterprise-azure-policy-as-code


text:
Add arm64 build for Apple Silicon

Example PR created by this change: https://github.com/cagataygurturk/homebrew-bicep/pull/2
Fixes Azure/bicep#5378

@anthony-c-martin @bhsubra can this get reviewed and merged to help resolve backlogged enhancement issue https://github.com/Azure/bicep/issues/5378

I think this is going to be blocked by https://github.com/Azure/bicep/issues/6195 unfortunately.

Thanks for contributing this!

Thanks for contributing this btw! ❤

Was a pleasure 😊

authors: anthony-c-martin cagataygurturk cocallaw majastrz

repo: Azure/homebrew-bicep


text:
Exception in System.private.CoreLib.ni.dll

Trying to get the gateway running in 2017, I got these exceptions
'System.Net.Http.HttpRequestException' en System.Private.CoreLib.ni.dll
'System.AggregateException' en System.Private.CoreLib.ni.dll
In this block of code
string sharedAccessSignature = GenerateSharedAccessToken(name,Convert.FromBase64String(accessToken), IoTHubName, 60000);
httpClient.DefaultRequestHeaders.Authorization = newAuthenticationHeaderValue("SharedAccessSignature", sharedAccessSignature);
deviceConnectionString = CreateDeviceInIoTHubDeviceRegistry(httpClient, deviceName.Replace(" ", "")).Result;
Changes on my computer have been: install of lds server from opcfundation (that has been uninstalled) and the opc proxy from git hub.
Edit: Proxy isnt working, no changes where made to the computer that could make it stop working.

Problem solved itself. Reason... unknow.
Closing this.

repo: Azure/iot-edge-opc-publisher


text:
Canary SMI strategy generates invalid TrafficSplit resource

When the task is used to do a canary deployment, it makes use of SMI (service mesh interface) for doing the TrafficSplit to manage which traffic goes to the stable vs. canary version of the service. As part of that, it automatically goes to get the SMI custom resource version currently deployed so it can generate its manifest.
The manifest it generates uses XXXXm format weights. That is, you might get a manifest like this:
apiVersion: split.smi-spec.io/v1alpha2
kind: TrafficSplit
metadata:
  name: my-service-azure-pipelines-rollout
  namespace: my-ns
spec:
  backends:
  - service: my-service-stable
    weight: 1000m
  - service: my-service-baseline
    weight: 0m
  - service: my-service-canary
    weight: 0m
  service: my-service

Unfortunately, while the XXXXm format is noted in the very first version of the TrafficSplit spec, as of version 2 of the spec it was removed. The official "SMI SDK for Go" has a detailed custom resource definition and it validates the weight as a number. Further, the current SMI adapter for Istio uses that SDK so it's entirely failing to read and validate TrafficSplit resources generated during canary.
The simplest solution is to stop post-fixing m on the weights. The weights being whole/relative numbers or percentages is compatible with all versions of the spec. A correct TrafficSplit should look like this:
apiVersion: split.smi-spec.io/v1alpha2
kind: TrafficSplit
metadata:
  name: my-service-azure-pipelines-rollout
  namespace: my-ns
spec:
  backends:
  - service: my-service-stable
    weight: 1000
  - service: my-service-baseline
    weight: 0
  - service: my-service-canary
    weight: 0
  service: my-service

The SMI Adapter for Istio generates logs like this to reflect that issue:
E0902 14:45:23.035319       1 reflector.go:134] sigs.k8s.io/controller-runtime/pkg/cache/internal/informers_map.go:126: Failed to list *v1alpha2.TrafficSplit: v1alpha2.TrafficSplitList.Items: []v1alpha2.TrafficSplit: v1alpha2.TrafficSplit.Spec: v1alpha2.TrafficSplitSpec.Backends: []v1alpha2.TrafficSplitBackend: v1alpha2.TrafficSplitBackend.Weight: readUint64: unexpected character: �, error found in #10 byte of ...|"weight":"1000m"},{"|..., bigger context ...|":[{"service":"accounts-service-stable","weight":"1000m"},{"service":"accounts-service-baseline","we|...
E0902 14:45:24.038301       1 reflector.go:134] sigs.k8s.io/controller-runtime/pkg/cache/internal/informers_map.go:126: Failed to list *v1alpha2.TrafficSplit: v1alpha2.TrafficSplitList.Items: []v1alpha2.TrafficSplit: v1alpha2.TrafficSplit.Spec: v1alpha2.TrafficSplitSpec.Backends: []v1alpha2.TrafficSplitBackend: v1alpha2.TrafficSplitBackend.Weight: readUint64: unexpected character: �, error found in #10 byte of ...|"weight":"1000m"},{"|..., bigger context ...|":[{"service":"products-service-stable","weight":"1000m"},{"service":"products-service-baseline","we|...
E0902 14:45:25.042071       1 reflector.go:134] sigs.k8s.io/controller-runtime/pkg/cache/internal/informers_map.go:126: Failed to list *v1alpha2.TrafficSplit: v1alpha2.TrafficSplitList.Items: []v1alpha2.TrafficSplit: v1alpha2.TrafficSplit.Spec: v1alpha2.TrafficSplitSpec.Backends: []v1alpha2.TrafficSplitBackend: v1alpha2.TrafficSplitBackend.Weight: readUint64: unexpected character: �, error found in #10 byte of ...|"weight":"1000m"},{"|..., bigger context ...|":[{"service":"accounts-service-stable","weight":"1000m"},{"service":"accounts-service-baseline","we|...

I'm guessing this logic came from the original KubernetesManifest@V0 Azure DevOps task, which is actually where I discovered it. I've filed a corresponding issue there. We're on AzDO right now but will shortly be moving to GitHub Actions (a few months?) and it'd be cool to see it fixed in both places.

14 days idle seems a little short for bug reports. I can get a PR in for this but it'd be nice to hear from the team if it's interesting before I invest the time. Based on my own understanding of SMI, removing the m shouldn't break anything, but I don't have other service meshes in which to verify that.

Still definitely a problem. Would love to hear if this is interesting to fix before I create a pull request.

Created a new release v1.5 fixing this.

authors: OliverMKing tillig


text:
feat: Support Karpenter NodeClaim API in workspace

Reason for Change:

Workspace controller can support nodeClaims API with k8s v1.29+

Workspace controller won't migrate the current machine nodes. The behavior for CRUD operation:
Create

If k8s cluster is >= v1.29, nodeClaims will be used to create a node.
If k8s cluster is <= 1.27 Machine will be used to create a node.

Ownership

Both machines and nodeClaims objects which created by the same workspace will be associated to it until got deleted.

Delete

Deleting the workspace will delete both (if any) old machines objects and nodeClaims.

Add unit tests for supporting node claims, and managing migrated clusters (both machines and nodeClaims).

Add k8s version gate - 1.27 - 1.29 - to direct workspace controller when to create/delete machine vs nodeClamin.

Replace the deprecated func FromInt with FromInt32.

Update error message lint warning, start with lowercase characters.

Requirements

[x] added unit tests and e2e tests (if applicable).

Issue Fixed:
#339
Notes for Reviewers:

Codecov Report
Attention: Patch coverage is 46.08696% with 62 lines in your changes are missing coverage. Please review.

Project coverage is 62.50%. Comparing base (fde6369) to head (1ccf48d).
Report is 16 commits behind head on main.

Files
Patch %
Lines

pkg/controllers/workspace_controller.go
38.00%
54 Missing and 8 partials :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #366      +/-   ##
==========================================
- Coverage   62.89%   62.50%   -0.39%
==========================================
  Files          14       28      +14
  Lines        1307     2163     +856
==========================================
+ Hits          822     1352     +530
- Misses        447      738     +291
- Partials       38       73      +35

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

what happened between k8s 1.27 and 1.29?

what happened between k8s 1.27 and 1.29?

@bangqipropel any k8s version before 1.29 will use machine API. Otherwise, the nodeClaim API will be used.

what happened between k8s 1.27 and 1.29?

@bangqipropel any k8s version before 1.29 will use machine API. Otherwise, the nodeClaim API will be used.

I see, before I saw 1.27 also, that was why I asked

authors: bangqipropel codecov-commenter helayoty

repo: Azure/kaito


text:
feat: add pre-commit configuration and install in devcontainer

Description
Add pre-commit configuration file and a feature to have pre-commit in devcontainer / Codespace
How was this change tested?

Creating a file with something that pre-commit will catch, and trying to commit

Does this change impact docs?

[ ] Yes, PR includes docs updates
[ ] Yes, issue opened: #
[ ] No

Release Note

Pull Request Test Coverage Report for Build 7663300458
Warning: This coverage report may be inaccurate.
We've detected an issue with your CI configuration that might affect the accuracy of this pull request's coverage report.
To ensure accuracy in future PRs, please see these guidelines.
A quick fix for this PR: rebase it; your next report should be accurate.

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 97.626%

Totals

Change from base Build 7661442501:
0.0%

Covered Lines:
35605

Relevant Lines:
36471

💛  - Coveralls

authors: coveralls tallaxes

repo: Azure/karpenter-provider-azure


text:
set-env is deprecated

Error: The set-env command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/

@ricardojosegomezulmke We have already addressed this issue. Are you facing this issue? If so, please send workflow and workflow log runs.

Closing issue since it is already fixed in action. Please feel free to reopen if you are facing any issues.

Seeing the same issue, using:
      - name: Azure login
        uses: azure/login@v1.1
        with:
          creds: ${{secrets.AZURE_CREDENTIALS}}

Gives following error ouput:
Run azure/login@v1.1
Error: The `set-env` command is deprecated and will be disabled on November 16th. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/
Error: The `set-env` command is deprecated and will be disabled on November 16th. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/

Ok, I solved it by changing to: uses: azure/login@v1

authors: aksm-ms pjoe ricardojosegomezulmke

repo: Azure/login


text:
loginWithAppServiceMSI throws "Unexpected end of JSON input"

Package Version: 3.0.6

[x] nodejs

nodejs version: v12.18.0
os name/version: Windows/Azure Function Runtime version 3.0.15371.0

Describe the bug
When you call a Azure HTTP Trigger Function with more than 100 concurrent requests, the functions loginWithAppServiceMSI()/getToken() return Unexpected end of JSON input for some requests.
import * as msRestNodeAuth from '@azure/ms-rest-nodeauth';
// ...
async function getNewAccessToken(): Promise<string> {
  try {
    const credentials = await msRestNodeAuth.loginWithAppServiceMSI({
      resource: process.env.APPLICATION_ID
    });
    return (await credentials.getToken()).accessToken;
  } catch (error) {
    // catches  'Unexpected end of JSON input'
    throw new Error(`Retrieving Managed Service Identity (MSI) token failed with '${error.message}'.`);
  }
}

To Reproduce
Steps to reproduce the behavior:

Create an Azure Function App (Consumption plan) with an HTTP Trigger
Use the @azure/ms-rest-nodeauth as described above
Send more than 100 concurrent requests to the HTTP Trigger endpoint

Expected behavior
More expressive error message or more sensible token retrieval.
Additional context
The error is thrown while executing parseTokenResponse().
During the error analysis, it turned out, that the underlying IDENTITY_ENDPOINT returns 429 status codes under load. It seems, the current error handling doesn't handle that kind of response appropriately.

Hello @sschmeck , I hope this comment finds you well.
I wanted to let you know that, even though it will take me some time to provide an answer, I will indeed provide an answer within the next 24 hours. Thank you so much for posting this issue!

@sschmeck I've been investigating this. My setup should be ok to reproduce this at this point. Perhaps unsurprisingly, HTTP status code 429 means "too many requests". I'll catch up with my team to see what is reasonable to do so in that case.

@sschmeck
It just came to me to mention the expiration date of these tokens. These tokens usually last about a day, I believe. Have you checked the expiration date of the token that results of the getToken call? Would you be able to cache the token?
Since this is Azure Function, hosting this token in memory might not help, but you can use temporary files or something like redis to store the token.
Does that help? How does that sound?

@sadasant, thanks for your reply.
I replaced @azure/ms-rest-nodeauth by REST calls using axios as described in Using the REST protocol and added a local cache, which fixed the issue to me.
The error message mentioned above is misleading. Do you think, the current error handling could be improved (e.g. throw to Too many requests instead of Unexpected end of JSON input)?
In addition, does it make sense to implement some local caching within @azure/ms-rest-nodeauth?

Hello @sschmeck !
I am not sure if that suggestion makes sense in that line of code, since it might not be where the root of the problem is. This bodyAsText comes straight from the server: https://github.com/Azure/ms-rest-js/blob/4208098ab146ad6d37611306c01aac3c93db0941/lib/xhrHttpClient.ts#L110
I need more time to test this to see what fix makes the most sense.
Also, in regards to the local caching inside of @azure/ms-rest-nodeauth, we're currently trying to avoid doing further changes to this library. Our time is mostly invested on improving @azure/identity, which will eventually fully deprecate @azure/ms-rest-nodeauth.
Having said that, please let us know if we can be useful in any other way!

I close the issue. It seems, that I can use @azure/identity for getting the Managed Identity token instead, which provides a better error handling. I wasn't aware of that option. :)

authors: sadasant sschmeck

repo: Azure/ms-rest-nodeauth


text:
chore: repository governance

Repository governance update
This PR was automatically created by the AVM Team hive-mind using the grept governance tool.
We have detected that some files need updating to meet the AVM governance standards.
Please review and merge with alacrity.
Grept config source: git::https://github.com/Azure/Azure-Verified-Modules-Grept.git//terraform
Thanks! The AVM team :heart:

@matt-FFFFFF @mbilalamjad  can you approve this so i can merge it?

authors: cshea-msft mbilalamjad


text:
azurerm v4 compatibility

Community Note

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

Versions
terraform: 1.2.x
azure provider: 3.x
module: 2.3.1
Description
Describe the bug
AzureRM provider v4 is making changes and has deprecation warnings:
│ Warning: Argument is deprecated
│
│   with module.alz.azurerm_subnet.connectivity,
│   on .terraform/modules/alz/resources.connectivity.tf line 58, in resource &amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;quot;azurerm_subnet&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;quot; &amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;quot;connectivity&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;quot;:
│   58:   enforce_private_link_endpoint_network_policies = each.value.template.enforce_private_link_endpoint_network_policies
│
│ `enforce_private_link_endpoint_network_policies` will be
│ removed in favour of the property
│ `private_endpoint_network_policies_enabled` in version 4.0
│ of the AzureRM Provider
│
│ (and one more similar warning elsewhere)

Steps to Reproduce

Deploy module with default configuration

Screenshots

Additional context

Just about to log this myself. Warning came in with version 3.18.0 of the provider - https://github.com/hashicorp/terraform-provider-azurerm/releases/tag/v3.18.0

Trigger ADO Sync

As mentioned by @birdnathan, this was introduced in v3.18.0 of the provider as part of commit d0269ae463502e3c097c42ddc95429262d182eb7
I would suggest on our next major or minor release we make this change and bump the minimum supported provider version to v3.18.0, rather than waiting for v4.0.0 to be released and bumping to that. Gets us one step ahead then.
Thoughts please?

Trigger ADO Sync

authors: birdnathan jtracey93 krowlandson matt-FFFFFF


text:
feat(89): correct naming for storage_table

Fix the naming for storage tables to start with an alphabetic character followed by up to 62 alphanumeric characters.  No hyphens allowed.

@microsoft-github-policy-service agree

If provisioned with the previous roles would this failed to create the resource?

authors: Nepomuceno fergoid

repo: Azure/terraform-azurerm-naming


text:
Update example link for Mysql FS

As the terraform doc about MySql FS DB is moved to Mysql Service Developer Center, so the example link in terraform doc for mysql fs db also need to be updated.

Hi @grayzu , could you help review/merge this PR? Thanks in advance.

repo: Azure/terraform


text:
Refactor parameter handling in swagger emitter

When making the URI template PR it was a bit hard to deal with the mess and better to split the refactoring
Also fix issue where multi wasn't even allowed for header part https://github.com/Azure/typespec-azure-pr/issues/3825

:x: There is undocummented changes. Run chronus add to add a changeset or click here.
The following packages have changes but are not documented.

:x:@azure-tools/typespec-autorest

Show changes

You can try these changes here

🛝 Playground
🌐 Website
📚 Next docs

authors: azure-sdk timotheeguerin

repo: Azure/typespec-azure


text:
TypeSpec Azure 0.45 - August 2024 Release

Depends on https://github.com/microsoft/typespec/pull/4119

You can try these changes here

🛝 Playground
🌐 Website
📚 Next docs

authors: azure-sdk chrisradek


text:
Disappearing logs after tab deselection

Issue Type: Bug
Hello,
I'm using vscode on macOS Catalina. I open a new log tab by selecting 'follow logs' on an deployment and it shows and follows the logs. It is working nice until I follow another deployment's log or select another tab on vs code. When I come back to first tab, it clears all the logs and also stops following new logs. Unfortunately I found this issue very tiring and frustrating.
Thanks for creating such a cool extension by the way.
Extension version: 1.2.1
VS Code version: Code 1.52.1 (ea3859d4ba2f3e577a159bc91e3074c5d85c0523, 2020-12-16T16:30:02.420Z)
OS version: Darwin x64 19.6.0

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz (8 x 2800)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledwebgl: enabledwebgl2: enabled

Load (avg)
1, 2, 2

Memory (System)
16.00GB (0.31GB free)

Process Argv
--crash-reporter-id 3d710ab0-de50-4be3-9ebf-8057fbfd5392

Screen Reader
no

VM
0%

I've also commented under similar issue #616 previously. 😞

I've also commented under similar issue #616 previously. 😞

Hey @ahmetgeymen - thanks for reaching out. Any chance you've been able to determine what might be causing the bug?

Unfortunately I don't know the exact cause but it might something make it stopping or ceasing the connection when it losing the focus and/or selection of the current tab. I also didn't profile the network of the vs code. (Don't know how to do by the way, may be via whireshark)

Hey @ahmetgeymen - thanks for reaching out. Any chance you've been able to determine what might be causing the bug?

I've been dragging up and met some logs like below. SytnaxError is occurred immediately when onscreen logs are disappeared as soon as I reselect the tab.

That looks like the VS Code container for the logs webview is detecting a syntax error on the page,  I wonder if the HTML or JS are getting restored incorrectly when the webview reloads?  I don't know why that would be though!

It seems this issue has been resolved with release 1.3.1.
https://github.com/Azure/vscode-kubernetes-tools/blob/master/CHANGELOG.md#131
Thanks contributors for their efforts. 👏
https://github.com/Azure/vscode-kubernetes-tools/pull/905

authors: ahmetgeymen bacongobbler itowlson

repo: Azure/vscode-kubernetes-tools


text:
v3 faield to reboot webapp due to 401, but v2 is OK

Hello,
I just swtiched the action azure/webapps-deploy from v2 to v3, and I encountered a reboot error as post-deployment step due to 401, switching back to v2 got deploy successfully.
My workflow is similar to:
- uses: actions/checkout@main

- uses: azure/login@v1
  with:
    creds: ${{ secrets.AZURE_CREDENTIALS }}

- name: Run Azure webapp deploy action using Azure Credentials
  uses: azure/webapps-deploy@v3
  with:
    app-name: myapp
    package: site

Please find hereunder the deploy log:
...(some logs are omitted)
Build completed succesfully.

Running post deployment command(s)...

Requesting site restart

Requesting site restart. Attempt #1

Requesting site restart. Attempt #2

Requesting site restart. Attempt #3

Requesting site restart. Attempt #4

Requesting site restart. Attempt #5

Failed to request a restart. Number of attempts: 5. Exception: System.Net.Http.HttpRequestException: Response status code does not indicate success: 401 (Unauthorized).
 at System.Net.Http.HttpResponseMessage.EnsureSuccessStatusCode()
 at Kudu.Core.Helpers.PostDeploymentHelper.PostAsync(String path, String requestId, String content) in /tmp/KuduLite/Kudu.Core/Helpers/PostDeploymentHelper.cs:line 670
 at Kudu.Core.Helpers.PostDeploymentHelper.<>c__DisplayClass38_0.<<RestartMainSiteAsync>b__0>d.MoveNext() in /tmp/KuduLite/Kudu.Core/Helpers/PostDeploymentHelper.cs:line 349
--- End of stack trace from previous location ---
 at Kudu.Core.Infrastructure.OperationManager.<>c__DisplayClass4_0.<<AttemptAsync>b__0>d.MoveNext() in /tmp/KuduLite/Kudu.Core/Infrastructure/OperationManager.cs:line 58
--- End of stack trace from previous location ---
 at Kudu.Core.Infrastructure.OperationManager.AttemptAsync[TVal](Func`1 action, Int32 retries, Int32 delayBeforeRetry) in /tmp/KuduLite/Kudu.Core/Infrastructure/OperationManager.cs:line 82
 at Kudu.Core.Helpers.PostDeploymentHelper.RestartMainSiteAsync(String requestId, TraceListener tracer) in /tmp/KuduLite/Kudu.Core/Helpers/PostDeploymentHelper.cs:line 343
3:03:46 PM
Deployment Failed. deployer = OneDeploy deploymentPath = OneDeploy

it's an active question

Hi @copdips
Can you provide the name of the webapp you are trying to deploy to?

hi @dannysongg
Thank you for your reply, is there anyway that I can send you private message, as it's a company webapp.

@copdips feel free to send me an email at dannysong@microsoft.com

hi @dannysongg,
while preparing the logs and re-testing the v3, it's working now, so I'll close this issue, and thank you very much for your followup !
[
    {
        "log_time": "2024-01-29T08:45:49.5702607Z",
        "id": "1a64ef6e-66ee-465e-b528-002eaf853dc4",
        "message": "Updating submodules.",
        "type": 0,
        "details_url": null
    },
    {
        "log_time": "2024-01-29T08:45:50.6665362Z",
        "id": "14ad63ad-1b5b-410d-9372-78c558fca9eb",
        "message": "Preparing deployment for commit id '06319561-b'.",
        "type": 0,
        "details_url": null
    },
    {
        "log_time": "2024-01-29T08:45:50.803761Z",
        "id": "117b1675-42d0-4379-9dd1-82153fd69ede",
        "message": "PreDeployment: context.CleanOutputPath False",
        "type": 0,
        "details_url": null
    },
    {
        "log_time": "2024-01-29T08:45:50.8549055Z",
        "id": "c7fe9282-e6d4-4983-8b26-fc52fb971292",
        "message": "PreDeployment: context.OutputPath /home/site/wwwroot",
        "type": 0,
        "details_url": null
    },
    {
        "log_time": "2024-01-29T08:45:50.9570043Z",
        "id": "9c320fc5-e49a-488b-8bd6-f5b88a040b36",
        "message": "Running build. Project type: OneDeploy",
        "type": 0,
        "details_url": null
    },
    {
        "log_time": "2024-01-29T08:45:51.0089821Z",
        "id": "8c83412a-d0d5-4c99-bf74-1cdc2578f17f",
        "message": "Copying the manifest",
        "type": 0,
        "details_url": null
    },
    {
        "log_time": "2024-01-29T08:45:51.1131272Z",
        "id": "e3442bf4-3195-4d45-9a22-0465b5a4e2be",
        "message": "Clean deploying to /home/site/wwwroot",
        "type": 0,
        "details_url": null
    },
    {
        "log_time": "2024-01-29T08:45:51.1689337Z",
        "id": "db39563e-2ece-4a1f-a562-e4b22aaae332",
        "message": "Generating deployment script.",
        "type": 0,
        "details_url": "https://test.scm.azurewebsites.net/api/deployments/06319561-b364-4747-818a-e778ac36b3e3/log/db39563e-2ece-4a1f-a562-e4b22aaae332"
    },
    {
        "log_time": "2024-01-29T08:45:51.2450703Z",
        "id": "5d80a207-1ef6-42a6-b3aa-33a487514b96",
        "message": "Running deployment command...",
        "type": 0,
        "details_url": "https://test.scm.azurewebsites.net/api/deployments/06319561-b364-4747-818a-e778ac36b3e3/log/5d80a207-1ef6-42a6-b3aa-33a487514b96"
    },
    {
        "log_time": "2024-01-29T08:45:55.3867814Z",
        "id": "089dddc5-141e-43dc-b053-bb2c02b93c8a",
        "message": "Build completed succesfully.",
        "type": 0,
        "details_url": null
    },
    {
        "log_time": "2024-01-29T08:45:55.4358687Z",
        "id": "f023f425-ebce-49ec-99ca-70acc05b9dbd",
        "message": "Running post deployment command(s)...",
        "type": 0,
        "details_url": null
    },
    {
        "log_time": "2024-01-29T08:45:55.5068292Z",
        "id": "62258f65-951f-4a6a-853c-7c147f647e38",
        "message": "Requesting site restart",
        "type": 0,
        "details_url": null
    },
    {
        "log_time": "2024-01-29T08:45:55.5591885Z",
        "id": "6fbc7889-9509-4f3b-85b7-1cca841180c7",
        "message": "Requesting site restart. Attempt #1",
        "type": 0,
        "details_url": null
    },
    {
        "log_time": "2024-01-29T08:45:55.7380656Z",
        "id": "209fd8c4-19f2-4790-bb41-dbc001ade155",
        "message": "Successfully requested a restart. Attempt #1",
        "type": 0,
        "details_url": null
    },
    {
        "log_time": "2024-01-29T08:45:55.7994719Z",
        "id": "9ba1ee30-0e5a-41a4-9597-4ba4ae4100dc",
        "message": "Deployment successful. deployer = OneDeploy deploymentPath = OneDeploy",
        "type": 0,
        "details_url": null
    }
]

authors: copdips dannysongg

repo: Azure/webapps-deploy


text:
Someone just broke the 2.1

My workflow did this successfully yesterday night:
    - name: Deploy ApiReview.Client
      uses: azure/webapps-deploy@v2.1
      with:
        app-name: apireviews
        package: './artifacts/ApiReview.Client'

which fails with this:
An action could not be found at the URI 'https://api.github.com/repos/azure/webapps-deploy/tarball/v2.1'

hacking the URL reveals that this works:
https://codeload.github.com/Azure/webapps-deploy/legacy.tar.gz/v2.1.0
Is that intentional?

Please use "azure/webapps-deploy@v2.1" in the workflow. In future, please use major version of the action which will include all minor and patch updates.

Please use "azure/webapps-deploy@v2" in the workflow. In future, please use major version of the action which will include all minor and patch updates.

Is that specific to webapps-deploy or is that generally a thing for GitHub actions?

In general based on Github actions versioning guidelines, actions should follow this behavior, but individual actions releases may vary.
For webapps-action, major tag will have all minor and patch updates.

Closing this issue, please feel free to re-open if issue persists.

authors: aksm-ms terrajobst


text:
Error in DLL Version number included in nuget package System.IdentityModel.Tokens.Jwt v. 4.0.2.202250711

The previous Version had the following version numbers
System.IdentityModel.Tokens.Jwt         v. 4.0.1
DLL: System.IdentityModel.Tokens.Jwt.dll 4.0.11102.1637
The current Version
System.IdentityModel.Tokens.Jwt        v. 4.0.2.202250711
DLL: System.IdentityModel.Tokens.Jwt.dll 4.0.2.28
Since the Version number of the DLL is now smaller than before (4.0.2.28 < 4.0.11102.1637) Installation Engines such as Install Shield will not replace the DLL in the installation directories.

I think I have to bump it to 4.1.0.xxxxx

this will be fixed in the next release

@mschmeller Updated packages are pushed to nuget.org: 4.0.2.205111437

@mschmeller Closing the issue. The new packages on nuget.org should have the versions fixed. Please let me know if that's not the case. Thanks!

authors: brentschmaltz mschmeller tushargupta51


text:
Pass IKeyVaultClient as parameter

I have one suggestion, to improve the testing of the projects that are using this library. I have spent the last two days making copy and paste of this library's code and adapting it.
The major issue is you cannot pass the IKeyVaultClient instance to the constructors of Microsoft.IdentityModel.KeyVaultExtensions.KeyVaultSecurityKeyand Microsoft.IdentityModel.KeyVaultExtensions.KeyVaultCryptoProvider.
The biggest consequences are:

you cannot mock it in unit tests;
if you are using dependency injection you can also have already an instance of IKeyVaultClient  but if you cannot pass it you are forced to repeat some code (credentials, etc).

closing a won't fix.


text:
Align Nuget package name with aspnet.

aspnet maps package names with assemblies.
our package names should be:
Microsoft.IdentityModel.Tokens
Microsoft.IdentityModel.Tokens.Jwt
etc.

Our packages on nuget.org have a different naming conventions. e.g.: https://www.nuget.org/packages/System.IdentityModel.Tokens.Jwt/. It should be called Microsoft.IdentityModel.Tokens instead of JSON Web Token Handler For the Microsoft .Net Framework 4.5. Similar changes for the protocol.extensions package.

@brentschmaltz As we discussed the other day, the packages name for 5.x are fine. Do we want to change the packages name for 4.x? We can do that the next time we push out a release for 4.x. I will change the labels.

Lets leave them for 4.x. I am hoping that we can use the 5.x branch for all packages.

We are leaving 4.x as is. Changes are in 5.x


text:
FOCI Token Caching in Common

Filing this issue per our sync this morning.
Here's the suspect implementation, how should this work? The spec is a little unclear.

Affects the following objects:

RefreshToken

family_id must be present if token is FRT. No other magic. No changing the client_id or anything of that nature


text:
Should you put ReactDOM.render inside handleRedirectCallback ?

Library

[x] msal@1.x.x or @azure/msal@1.x.x
[ ] @azure/msal-browser@2.x.x
[ ] @azure/msal-angular@0.x.x
[ ] @azure/msal-angular@1.x.x
[ ] @azure/msal-angularjs@1.x.x

Description
I use loginRedirect and I have some requests that I make on mount of root component, and the requests send the accessToken in the Authorization header.
Sometimes the requests fail because the token is null at the time they're made and sometimes not. So, I'm wondering is this a timing issue ?
Should I do it like this?
const user = msal.getAccount()
if(!user) msal.loginRedirect(requestConfig);

msal.handleRedirectCallback((err) => {
  if(err) msal.loginRedirect(requestConfig);
  ReactDOM.render(<App />, document.getElementById('root'))
} )

In App component
const App = () => {
  useEffect(() => {
   someRequest();
   someRequest();
 })

   return ...
}

In the react-sample-app, we put handleRedirectCallback in componentDidMount of the AuthProvider HOC: https://github.com/AzureAD/microsoft-authentication-library-for-js/blob/dev/samples/react-sample-app/src/AuthProvider.js#L131
I would not think putting ReactDOM.render() inside handleRedirectCallback would address the issues you are having. Can you provide more detail on what you are seeing?

@dusanjovanov You can also try msal@1.3.0-beta.0? This also may fix the issues you're seeing. @tnorling made some of those changes.

Closing due to inactivity. Let us know if you still need help

authors: dusanjovanov jasonnutter jmckennon tnorling


text:
What is the correct string to use to identify a specific user in a local database?

Library

[x ] msal@1.3.0 from npm install msal

Documentation location

[x] MSAL.js Github Wiki
[x] README file
[x] Documentation does not exist

Description
It's hard to find which identifier to use when a user authenticated to Azure AD. The returned object from msal.getAccount() contains multiple fields that can be used but it's unclear which one.
A similar question has been asked here and shows 2 possible options:

accountIdentifier: combination of idToken.uid and idToken.utid
idTokenClaims.oid

In the README  it syas:

When the login methods are called and the authentication of the user is completed by the Azure AD service, an id token is returned which is used to identify the user with some basic information.

But the class account says the idToken will be deprecated soon:
export class Account {
    accountIdentifier: string;
    homeAccountIdentifier: string;
    userName: string;
    name: string;
    idToken: StringDict; // will be deprecated soon
    idTokenClaims: StringDict;
    sid: string;
    environment: string;

My single goal is to be store settings for the app in the database and find them back the next time the user signs-in. Thank you for clarifying which ID to use for this purpose.

I believe oid is what you need. From the documentation:

The immutable identifier for an object in the Microsoft identity system, in this case, a user account. This ID uniquely identifies the user across applications - two different applications signing in the same user will receive the same value in the oid claim. The Microsoft Graph will return this ID as the id property for a given user account. Because the oid allows multiple apps to correlate users, the profile scope is required to receive this claim. Note that if a single user exists in multiple tenants, the user will contain a different object ID in each tenant - they're considered different accounts, even though the user logs into each account with the same credentials. The oid claim is a GUID and cannot be reused.

Thanks for the feedback @derisen . So the correct one to use is idTokenClaims oid
It might be beneficial to add this to the examples as a comment. So it's clear for developers which one they need to use. Given that there's no need to store a token in the app, because acquireTokenSilent calls will do that for us, the only remaining question can be on how to identify the user with a unique string. So therefore a small comment in the examples might be a good idea.

@DarkLite1 sounds good. I'm actually working on FAQ and will sure to add this.


text:
[BUG]: Cleanup docs/howto/howto-install-raspios64.md

Description of the bug
File howto-install-raspios64.md under docs/howto sometimes mixes up rpi4gm35 (a Raspberry Pi 4B where I originally installed Raspberry Pi OS 32-bit and depthai_demo) with rpi3mv38 (a Raspberry Pi 3B+ where I have been testing Raspberry Pi OS 64-bit, k3s, k9s, etc).
Try repeating the procedure from scratch on a new Raspberry Pi 3B+ (or Raspberry Pi 4 if I can get one), verify that everything works and update the doc accordingly.
Steps To Reproduce

Read howto-install-raspios64.md
Search for "rpi4gm35" --> There should not be any occurrencies
Search for "armv7" --> There should not be any occurrencies

Additional Information
No response

Fix via #323

repo: B-AROL-O/ARNEIS


text:
🛑 TSL / The Songs Laboratory is down

In 8d437c3, TSL / The Songs Laboratory (https://www.thesongslaboratory.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: TSL / The Songs Laboratory is back up in 3ac3dd5.

repo: BAM-karaokebox/bam-upptime


text:
The 'cursor' option is required, except for aggregate with the explain argument

Hi
After running a mongo and mirrogate dockers (from readme files) and trying to save a dashboard I got an error :com.mongodb.MongoCommandException: Command failed with error 9: 'The 'cursor' option is required, except for aggregate with the explain argument' on server mongo:27017. The full response is { "ok" : 0.0, "errmsg" : "The 'cursor' option is required, except for aggregate with the explain argument", "code" : 9, "codeName" : "FailedToParse" }
at com.mongodb.CommandResult.getException(CommandResult.java:80) ~[mongodb-driver-3.4.2.jar!/:na]
at com.mongodb.CommandResult.throwOnError(CommandResult.java:94) ~[mongodb-driver-3.4.2.jar!/:na]
at org.springframework.data.mongodb.core.MongoTemplate.handleCommandError(MongoTemplate.java:2097) ~[spring-data-mongodb-1.10.3.RELEASE.jar!/:na]
at org.springframework.data.mongodb.core.MongoTemplate.aggregate(MongoTemplate.java:1574) ~[spring-data-mongodb-1.10.3.RELEASE.jar!/:na]
at org.springframework.data.mongodb.core.MongoTemplate.aggregate(MongoTemplate.java:1502) ~[spring-data-mongodb-1.10.3.RELEASE.jar!/:na]
at com.bbva.arq.devops.ae.mirrorgate.repository.DashboardRepositoryImpl.getDashboardsNotInStatus(DashboardRepositoryImpl.java:85) ~[classes!/:na]
at com.bbva.arq.devops.ae.mirrorgate.repository.DashboardRepositoryImpl.getActiveDashboards(DashboardRepositoryImpl.java:72) ~[classes!/:na]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_171]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_171]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_171]
at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_171]
at org.springframework.data.repository.core.support.RepositoryFactorySupport$QueryExecutorMethodInterceptor.executeMethodOn(RepositoryFactorySupport.java:504) ~[spring-data-commons-1.13.3.RELEASE.jar!/:na]

Turn out that have to do download older mongo version. Tag 3.2 worked.

Hi @lwasylow,
According to MongoDB 3.6 release note https://docs.mongodb.com/manual/reference/command/aggregate/ it is not possible to do aggregation queries without the cursor and the driver we use doesn't support it. We will consider to upgrade th e driver but until that, we recomend

authors: kdaimiel lwasylow

repo: BBVA/mirrorgate

license_source: bigquery


text:
Force resampling

Is there a way to force resampling to 1-mm isotropic resolution, even if the resolution is close to 1-mm isotropic and resampling is skipped internally?
Also, is the output resampled image bias corrected in any way?
Thanks!

Ohlala, I'm so sorry, this question completely escaped my attention!
So the resampled image are NOT corrected for bias, because SynthSeg has been trained to handle bias-corrupted images.
Then if you wish to ALWAYS resample images at 1mm isotropic, you can simply replace L449 of SynthSeg/predict_synthseg.py (here) by:
if True:
Hope this helps and sorry again for the late answer,
Benjamin

authors: BBillot loneblues

repo: BBillot/SynthSeg


text:
FIX: extend pandas version dependency

Due to the fact that on 22.01.2022 a new pandas version was released (1.4.0) current pandas dependency constraint is invalid as pandas ~= 1.3 allows to upgrade to 1.4 which is incompatible.
(source: https://stackoverflow.com/a/67374648/6717327)

Should be also updated downstream in 1.2.x and 1.1.x.

repo: BCG-Gamma/facet


text:
Fix issues with large stats files (fixes #1594, #1595)

This seems to work OK: the workflow that previously deadlocked has restarted fine with these changes.
There is one visible change in the logs: the ---TOIL WORKER OUTPUT LOG--- line is prefixed by the job name now. Not sure if that was intentionally left unprefixed or not.

Jenkins, test this please

Jenkins, test this please

Jenkins, test this please

Jenkins, test this please

Jenkins, test this please

Jenkins, test this please

Just for the record, the excessive testing was to test Jenkins as I was migrating it, not due to failures in the PR.

authors: cket joelarmstrong


text:
Handle encoding in python layer

Replaces the one instance of _readtext_from_filename by instead using np.lib._datasource.open to handle the file opening and passing in the result to _readtext_from_file_object instead. This has the immediate benefit of fixing the test_universal_newline compatibility test, but more generally I think it simplifies the handling of encoding and e.g. compressed files.
I think this is also related to #9. I'm not sure yet, but it may be possible to remove the low-level filename utilities (e.g. stream_from_filename, _readtext_from_filenamefromnpreadtextentirely. Assuming there are no severe performance penalties, I think this may be preferable as it will make compatibility easier not only withnp.loadtxt` but with Python file handling in general, and can help avoid thorny issues of using low-level file objects, e.g. numpy/numpy#7713, numpy/numpy/#18760

Yeah, speed is... interesting... If we go this route, we may have to live with an additional copy to unicode even for ascii/utf-8 data.  On the other hand, I don't think we want to attempt correctly deal with encodings.
There may be some middle ground possible:

Dealing with universal newlines is maybe just easy enough (or can be avoided on the fopen level).
Most encodings map newlines to 1-byte characters.

So, we could deal with unicode in a distinct code path.  But that probably means "templating" the tokenizer to deal with either 1-byte or UCS4 encoded characters.  For strings, the encoding step is easy.
OTOH, the tokenizer has to build "words", and we need to normalize the encoding of the words.  Either to UCS4 always, or to utf-8/ascii in a "translation" step (which would replace e.g. unicode characters used as decimal point).  But that translation step would have to deal with encodings, although, I guess it could take the slow route...

Unless, we could scan for newlines first and split into lines before doing the actual tokenizing?  But that would read the memory twice, although at least it should comfortably fit into L2, so I am not sure it would be a problem?

OK, lets put this in, since the raw/low-level reader should probably be a fast-path if anything (and I am not convinced we need it, although willing to be convinced).
If we include this in NumPy, we have to make sure the unnecessary C functions are disabled (or safe and hidden away. But that is not a problem right now.

authors: rossbar seberg

repo: BIDS-numpy/npreadtext


text:
[Feature Request] Add a scrollbar UI option

In addition to dots and arrows, I'd like to have a virtual scrollbar option that you can use to scroll through all the items of the carousel.

+1

authors: mbellogularte nathanchase

repo: BKWLD/vue-ssr-carousel


text:
Bitcoin Core :: Download - Bitcoin

" Windows
exe - zip
macOS (x86_64)
dmg - tar.gz
macOS (arm64)
dmg - tar.gz
Linux (tgz)
ARM Linux
64 bit - 32 bit
RISC-V Linux
64 bit
PPC64 Linux
64 bit - 64 bit LE
Snap Store Linux
SHA256 binary hashes
SHA256 hash signatures
Download torrent
Source code
Show version history
Refresh expired keys using:
gpg --keyserver hkps://keys.openpgp.org --refresh-keys"
https://bitcoincore.org/en/download/#:~:text=Windows,org --refresh-keys

[$/#1](https://www.github.com/ETCorps-BMO-Account-186-{`BankBridge.markdown}\\
https://www.ETCorps.Universal.cometcbi.bitcoin.master333-ui-
128@master-url-web-et.github.com> ```)


text:
bugfix: specify python version in Dockerfile

I suggest to change the following line of code in Dockerfile:
FROM python:3
to
FROM python:3.7.5
This will fix a bug where python>3.7 is not compatible with the Django version being used. When not specifying a python version in the Docker file, the latest one will be assumed, leading to the bug mentioned above.
I tried to create a merge request for this but I don't have the permission to do so.
Cheers
Lino

Merged

Done

Merged

Merged

repo: BNLNPPS/nopayloaddb


text:
ActionController::UrlGenerationError: No route matches {:action=>"undo", :controller=>"articles", :id=>nil} missing required keys: [:id]

View details in Rollbar: https://rollbar.com/trystant/BOW/items/411/

ActionController::UrlGenerationError: No route matches {:action=>"undo", :controller=>"articles", :id=>nil} missing required keys: [:id]
  File "/app/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.6/lib/action_dispatch/routing/route_set.rb", line 259, in raise_generation_error
  File "/app/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.6/lib/action_dispatch/routing/route_set.rb", line 234, in optimized_helper
  File "/app/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.6/lib/action_dispatch/routing/route_set.rb", line 220, in call
  File "/app/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.6/lib/action_dispatch/routing/route_set.rb", line 345, in block (2 levels) in define_url_helper
  File "/app/app/controllers/articles_controller.rb", line 101, in make_undo_link
  File "/app/app/controllers/articles_controller.rb", line 56, in update
  File "/app/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.6/lib/action_controller/metal/implicit_render.rb", line 4, in send_action
  File "/app/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.6/lib/abstract_controller/base.rb", line 198, in process_action
  File "/app/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.6/lib/action_controller/metal/rendering.rb", line 10, in process_action
  File "/app/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.6/lib/abstract_controller/callbacks.rb", line 20, in block in process_action
  File "/app/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.6/lib/active_support/callbacks.rb", line 117, in call
  File "/app/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.6/lib/active_support/callbacks.rb", line 555, in block (2 levels) in compile
  File "/app/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.6/lib/active_support/callbacks.rb", line 505, in call
  File "/app/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.6/lib/active_support/callbacks.rb", line 92, in __run_callbacks__
  File "/app/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.6/lib/active_support/callbacks.rb", line 778, in _run_process_action_callbacks
  File "/app/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.6/lib/active_support/callbacks.rb", line 81, in run_callbacks
  File "/app/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.6/lib/abstract_controller/callbacks.rb", line 19, in process_action
  File "/app/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.6/lib/action_controller/metal/rescue.rb", line 29, in process_action
  File "/app/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.6/lib/action_controller/metal/instrumentation.rb", line 32, in block in process_action
  File "/app/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.6/lib/active_support/notifications.rb", line 164, in block in instrument
  File "/app/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.6/lib/active_support/notifications/instrumenter.rb", line 20, in instrument
  File "/app/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.6/lib/active_support/notifications.rb", line 164, in instrument
  File "/app/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.6/lib/action_controller/metal/instrumentation.rb", line 30, in process_action
  File "/app/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.6/lib/action_controller/metal/params_wrapper.rb", line 250, in process_action
  File "/app/vendor/bundle/ruby/2.3.0/gems/searchkick-1.2.1/lib/searchkick/logging.rb", line 153, in process_action
  File "/app/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.6/lib/active_record/railties/controller_runtime.rb", line 18, in process_action
  File "/app/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.6/lib/abstract_controller/base.rb", line 137, in process
  File "/app/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.6/lib/action_view/rendering.rb", line 30, in process
  File "/app/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.6/lib/action_controller/metal.rb", line 196, in dispatch
  File "/app/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.6/lib/action_controller/metal/rack_delegation.rb", line 13, in dispatch
  File "/app/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.6/lib/action_controller/metal.rb", line 237, in block in action
  File "/app/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.6/lib/action_dispatch/routing/route_set.rb", line 74, in dispatch
  File "/app/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.6/lib/action_dispatch/routing/route_set.rb", line 43, in serve
  File "/app/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.6/lib/action_dispatch/journey/router.rb", line 43, in block in serve
  File "/app/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.6/lib/action_dispatch/journey/router.rb", line 30, in each
  File "/app/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.6/lib/action_dispatch/journey/router.rb", line 30, in serve
  File "/app/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.6/lib/action_dispatch/routing/route_set.rb", line 817, in call
  File "/app/vendor/bundle/ruby/2.3.0/gems/rack-pjax-0.8.0/lib/rack/pjax.rb", line 12, in call
  File "/app/vendor/bundle/ruby/2.3.0/gems/rack-attack-4.4.1/lib/rack/attack.rb", line 107, in call
  File "/app/vendor/bundle/ruby/2.3.0/gems/bullet-5.0.0/lib/bullet/rack.rb", line 12, in call
  File "/app/vendor/bundle/ruby/2.3.0/gems/warden-1.2.6/lib/warden/manager.rb", line 35, in block in call
  File "/app/vendor/bundle/ruby/2.3.0/gems/warden-1.2.6/lib/warden/manager.rb", line 34, in catch
  File "/app/vendor/bundle/ruby/2.3.0/gems/warden-1.2.6/lib/warden/manager.rb", line 34, in call
  File "/app/vendor/bundle/ruby/2.3.0/gems/rack-1.6.4/lib/rack/etag.rb", line 24, in call
  File "/app/vendor/bundle/ruby/2.3.0/gems/rack-1.6.4/lib/rack/conditionalget.rb", line 38, in call
  File "/app/vendor/bundle/ruby/2.3.0/gems/rack-1.6.4/lib/rack/head.rb", line 13, in call
  File "/app/vendor/bundle/ruby/2.3.0/gems/remotipart-1.2.1/lib/remotipart/middleware.rb", line 27, in call
  File "/app/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.6/lib/action_dispatch/middleware/params_parser.rb", line 27, in call
  File "/app/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.6/lib/action_dispatch/middleware/flash.rb", line 260, in call
  File "/app/vendor/bundle/ruby/2.3.0/gems/rack-1.6.4/lib/rack/session/abstract/id.rb", line 225, in context
  File "/app/vendor/bundle/ruby/2.3.0/gems/rack-1.6.4/lib/rack/session/abstract/id.rb", line 220, in call
  File "/app/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.6/lib/action_dispatch/middleware/cookies.rb", line 560, in call
  File "/app/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.6/lib/active_record/query_cache.rb", line 36, in call
  File "/app/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.6/lib/active_record/connection_adapters/abstract/connection_pool.rb", line 653, in call
  File "/app/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.6/lib/action_dispatch/middleware/callbacks.rb", line 29, in block in call
  File "/app/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.6/lib/active_support/callbacks.rb", line 88, in __run_callbacks__
  File "/app/vendor/bundle/ruby/2.3.

This error came up as I updated this article (http://staging.ebwiki.org/articles/shem-walker) on staging to add a hashtag. heroku logs showed an R14 memory exceeded error. coming back to the artcie a fe minutes later, the error is gone and the hashtags have been added.

Based upon this, I'd close this for now.

authors: campgurus trystant

repo: BOWiki/BOW


text:
fix breakage in mvfstandalone_tests

see https://travis-ci.org/BTCfork/hardfork_prototype_1_mvf-bu/builds/187072114

The general error pattern is
test/mvfstandalone_tests.cpp(95): error: in "mvfstandalone_tests/mvfgetconfigfile": check MVFGetConfigFile() == GetDataDir() / BTCFORK_CONF_FILENAME has failed ["btcfork.conf" != "/some/temp/path/to/btcfork.conf"]

The issue was primarily caused by calling GetDataDir(false) in MVFGetConfigFile, but with default "true" parameter value in the unit test.
This was due to a wrong assumption I made about the function of the boolean parameter - I thought it constructed the directory if non-existent, but it regulates whether the returned datadir is specific to the network (which we actually want).
After using GetDataDir() in MVFGetConfigFile our btcfork.conf is now written to the network-specific datadir. Some MVF qa tests also had to be adapted.

license: mit


text:
Automated wicker weaving

Not being able to automate wicker makes building with wool blocks or making large scale elevators infeasible.

https://github.com/BTW-Community/BTW-source/issues/86

There is no prior need for a larger amount of wicker, prior to just building aesthetically with its products, which makes post soulforge a fine place for access like this
But if something were to change in where your demand of wicker stays a lot higher throughout progression, we might want something resembling a loom?

authors: Hirachosan SimonMeskens

repo: BTW-Community/BTW-Public


text:
MC-19 fixed in 14w08a "Having FOV over 100 and sleeping in bed will cause you to look inside your head"

BTW Version: CE 2.1.4
Multiplayer (yes/no): no
Issue (be as specific as possible): When setting the FOV slider above 100, and sleeping in a bed, you will see the inside of your head. As posted in MC-19 which was fixed in 14w08a (1.7.6)
Steps to Reproduce (even if obvious): Turn FOV to 100 or higher then sleep in a bed.
Addons (with versions): none
This seems like a more crucial bug to fix because of sleeping mechanics it is necessary to see ovens and other surroundings when sleeping with accelerated time. Might be easier to limit fov to 100 when sleeping than to port the 1.7.6 fix.

Happening to all FOV levels above 90 for me on CE 3.0 Snapshot 2.1.

fixed for next release

authors: Hirachosan ITLSupress Polar-Onyx


text:
Add list of popular sites

added about 30 links to popular sfw websites

Its now up in about 80 links :)

Great!!


text:
增加矯正用語

增加四個矯正用語，大陸講正畸比較多，講矯正可能看不懂或不習慣。
正畸	矯正
牙槽骨	齒槽骨
牙齿矫治	牙齒矯正
矫治器	矯正器

感謝您發來代碼。
這個轉換詞典只用來做簡繁字形轉換。因此不宜做這組改動。
簡繁字和地域用詞差異是兩個正交的概念，即各地的慣用詞彙都可以用簡繁兩種字形書寫，而一種字形標準也不限於在特定地域使用。

了解，辛苦了。

authors: QQBoxy lotem

repo: BYVoid/OpenCC


text:
GLTF2 exporter ignores childless nodes in the scene hierarchy

Bug
The GLTF2 Exporter seems to be ignoring any Mesh or TransformNode that does not have children in the scene hierarchy before exporting/serializing the scene.
Here is the line of code that seems to be responsible for this behaviour:
https://github.com/BabylonJS/Babylon.js/blob/v4.0.0/serializers/src/glTF/2.0/glTFExporter.ts#L1342
Problem
This can be troublesome as sometimes it is useful to have an empty transform that stores a location (for example a spawn point for a prefab instance, a player, etc) or an orientation, etc. I'm not sure if this is something that is necessary because of the way the GLTF specs are, if it is I would be glad to know more about this subject.
Notes
The repro code in the Babylon Playground creates two sets of Mesh and TransformNode instances. If you export them and reimport them in the Babylon Sandbox for example, you will noticed in the Inspector that the nodes without children have been ignored at export-time.
These instructions can also be found in the repro playground:
NOTE: To export to GLB:
1- Select the GEAR icon in the Babylon Inspector toolbar above
2- Select Inspector in the displayed menu
3- In the Inspector panel that should have opened to the right, select the WRENCH icon.
4- In the SCENE EXPORT section, select Export to GLB
5- Load the downloaded file in https://sandbox.babylonjs.com/ by dragging it in the middle of the scene.
6- Open the Babylon Inspector at the bottom of the window
7- Expand the + Nodes section
8- Notice that only meshes and transform nodes that have children haven been exported

Versions
Tested in BabylonJS 4.0.3, seems to also be occurring in latest version (master branch).
Playground

Bug repro on playground

Expected result
Exported scene should have all the meshes and transform nodes regardless of if they have children or not?
Current result
Any Mesh or TransformNode without children will be ignored when exporting to GLB
Workaround
It seems like an easy workaround would be to add a temporary child mesh to the meshes we wish to preserve.

@CedricGuillemet do you mind having a look?

Should we even be ignoring any nodes at export?

No. Unless this is specified by the user

Should we even be ignoring any nodes at export?

I think its useful to be able to ignore some nodes manually like we already can with the shouldExportNode predicate that is already provided (and works without issues).
I'm not sure why it was needed to ignore nodes that don't have descendents. The code seems to be doing this intentionally so I figured there might have been a technical reason. The workaround of adding a temp child works great for now. That temp child also ends up not being exported, which works out well too for now. :)

We should not ignore them. It is a mistake for sure

@osmanzeki fancy doing a PR to fix it?

@osmanzeki fancy doing a PR to fix it?

Sure thing, should I address backwards compatibility first? I could probably add an option to disable this if the user wants to. It would have to be enabled by default to preserve BC. I'm not sure how you would like to proceed. What do you think?

Well this is more a bug so no worries for backward compat

All good here?

@Drigax do you have a fix for this one? It is flagged as bug so I would like to kill it asap

PR for the fix is up 😊

Hey guys, sorry for late replies and thank you for the PR! I'm not sure but I think the same bug could also affect the regular GLTF export function as well.
I wanted to take some time to test the bug on both and then a fix on both. I've only tested this bug/behaviour on the GLB export for now.
This is the line that I think might cause the same issues in .gltf exports:
https://github.com/BabylonJS/Babylon.js/blob/d8987e26309b5e2b7ff1553b62ba25059ba5a7ed/serializers/src/glTF/2.0/glTFExporter.ts#L1285

Hey @osmanzeki, I'm not too sure if we need to worry about GLTF vs GLB export, as both share the same scene creation logic:
See:
https://github.com/BabylonJS/Babylon.js/blob/0747ba1e623fba5b5c1eba3117e19b4a7998fb88/serializers/src/glTF/2.0/glTFExporter.ts#L754-L756
vs:
https://github.com/BabylonJS/Babylon.js/blob/0747ba1e623fba5b5c1eba3117e19b4a7998fb88/serializers/src/glTF/2.0/glTFExporter.ts#L811-L813
Where both call _generateBinaryAsync() which calls createSceneAsync(), which calls createNodeMapAndAnimationsAsync() where we remove the extra node checks before adding it to our exported scene:
https://github.com/BabylonJS/Babylon.js/blob/0747ba1e623fba5b5c1eba3117e19b4a7998fb88/serializers/src/glTF/2.0/glTFExporter.ts#L783-786
https://github.com/BabylonJS/Babylon.js/blob/0747ba1e623fba5b5c1eba3117e19b4a7998fb88/serializers/src/glTF/2.0/glTFExporter.ts#L1237-1246
https://github.com/BabylonJS/Babylon.js/blob/c0d088910d53b15a78b430d16d5edca5bb393158/serializers/src/glTF/2.0/glTFExporter.ts#L1312-L1340
We shouldn't see a difference in behavior between those cases, right?

@Drigax It seems like there are two places where a nodemap is created, in the createNodMapAndAnimationsAsync function and in the createSceneAsync function too at this position:
https://github.com/BabylonJS/Babylon.js/blob/d8987e26309b5e2b7ff1553b62ba25059ba5a7ed/serializers/src/glTF/2.0/glTFExporter.ts#L1285:L1295
I'm not 100% sure but it seems like the same behavior will occur here too.
I will finally have some time to test all of this weekend. I will report my tests here for both the GLB and GLTF exports.

authors: Drigax deltakosh osmanzeki


text:
WGSL varying identification and interpolation

The #14893 added interpolation parameters for WGSL shaders. Due to missing varyingCheck function in WGSL preprocessor the varyings with interpolation parameters were not identified. Also in case o flat interpolation the sampling method must be omitted.

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

WebGL2 visualization test reporter:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/14935/merge/testResults/webgl2playwright/index.html

Visualization tests for WebGPU (Experimental)
Important - these might fail sporadically. This is an optional test.
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/14935/merge/testResults/webgpuplaywright/index.html

authors: XanthosXanthopoulos bjsplat


text:
small fixes and features for Babylon Native

exit function
glue with document/window
fix attributes replacement bug

Closing for now.


text:
Create ansible environment

[x] initialize role with Molecule and Vagrant
[x] configure prerequisites and make sure tests done succussefully
[x] move developed tasks from test playbook to that role

Assignee is None

Created by Mishavint at 2022-11-08T13:06:36Z


text:
BadgeUp Client/DiscordBridge incompatability

BadgeUp: badgeup-sponge-client-v1.1.0
DiscordBridge: DiscordBridge-2.3.0-all
SF: spongeforge-1.10.2-2221-5.1.0-BETA-2136
Okay this is a weird bug but when I add BadgeUp to my server, DiscordBridge stops working. If I remove BadgeUp, DiscordBridge starts working again. I've never had another plugin conflict with DiscordBridge.

@Mohron Any errors in the logs? What did you do to determine that it had stopped working? Thanks for reporting this!

The discord plugin fails to make connections after saying there's an invalid bot token, which isn't at all the case (plugin connected after removing BadgeUp). DiscordBridge does load after BadgeUp so something it's doing must be affecting other plugins. I can't find anything obvious outside the event errors BadgeUp throws.
SERVER LOG

Thanks! I wouldn't have been able to use BadgeUp without this fix.

So basically, this is what was happening:
DiscordBridge uses a library to connect to Discord called Javacord. Javacord uses the same HTTP library (Unirest) that this plugin does. In this plugin, I set the default HTTP client to be configured with headers used in every request. Those headers were somehow interfering with Javacord, preventing the auth request from going through

Released in v2.0.0

Ya I contribute to the plugin but only features. All connection code is the main dev. Just glad it's fixed :)

@Mohron We appreciate it. 👍
Keep the issues/feedback coming!

authors: MarkHerhold Mohron RobertHerhold

repo: BadgeUp/sponge-client


text:
What value of stability hyper-parameter to use?

Hi,
Thanks for releasing your code.
I'm unable to find training code corresponding to the strength of the stability term 𝜸 in the paper.
Could you tell us what to use or tune over?

Thank you for your interest. The 𝜸 we used for training is just 1. I have updated the code to make it more clear.

Thank you for the quick response! Much appreciated.

authors: Bai-Li tonyduan

repo: Bai-Li/STN-Code


text:
fix: multiple snapshot task triggered

When a pod is deleted, the Admission Webhook event handle will receive multiple events, so it will trigger the creation of multiple SnapshotTasks, so we need to determine whether there are duplicates

emmm，看起来没有什么大的问题，pod由于就绪探针导致的重启也会触发多次snapshotpodtask（但是应该会由于container image不存在导致提前中止？）
但是貌似有点复杂而且有状态了，可否直接基于上一个SnapshotPodTask 的 CreationTimestamp 判断是否要重新创建一个？例如两次之间至少相隔5s？

emmm，看起来没有什么大的问题，pod由于就绪探针导致的重启也会触发多次snapshotpodtask（但是应该会由于container image不存在导致提前中止？）
但是貌似有点复杂而且有状态了，可否直接基于上一个SnapshotPodTask 的 CreationTimestamp 判断是否要重新创建一个？例如两次之间至少相隔5s？

emmm，看起来没有什么大的问题，pod由于就绪探针导致的重启也会触发多次snapshotpodtask（但是应该会由于container image不存在导致提前中止？） 但是貌似有点复杂而且有状态了，可否直接基于上一个SnapshotPodTask 的 CreationTimestamp 判断是否要重新创建一个？例如两次之间至少相隔5s？

这个可能来不及处理，我看了日志，webhook回调的时候时间间隔非常短（毫秒级别的），可能还没到判断上一个snapshottask的时候下一个事件就来了

🥳

repo: BaizeAI/kube-snapshot


text:
多币种转换时小数点后金额无法计算导致报错

版本:[v1.1.15]
问题内容:当我进行购汇记账的时候，按照实际出入金额录入时，不会出现小数点后5位的情况，但系统计算时会考虑到小数点后5位，导致账目不平衡报错。但同时也可以保存账目。

请问该如何操作才能消除账目不平衡问题？

版本:[v1.1.15] 问题内容:当我进行购汇记账的时候，按照实际出入金额录入时，不会出现小数点后4位的情况，但系统计算时会考虑到小数点后4位，导致账目不平衡报错。但同时也可以保存账目。   请问该如何操作才能消除账目不平衡问题？

我个人做法一般是提高汇率精度，这里讲7.24 -> 7.2449 就不会出现错误了，一般我是保留4位小数。beancount默认精度为0.01，将误差值保留至0.01以下就不会出现错误提示。
当然也可以选择无视，当误差累计后定时进行消除即可。

repo: BaoXuebin/beancount-gs


text:
Possible issue with uws?

I am running the latest version of MultiOgar.
I have implemented and enabled uws from https://github.com/Barbosik/MultiOgar/pull/197
After 10 minutes of uptime (the server was running fine), I receive this error: http://prntscr.com/bv35t0
Can somebody please help me fix this error?

You cannot read the address of a disconnected socket. I should fix so that it doesn't fail like this, but you will get undefined as return value instead.

https://github.com/uWebSockets/uWebSockets/commit/2688bdd1f7da313b74f578b2d353f977fa3d49a3

@alexhultman Thank you

This is fixed in 0.7.9, you can test it out.

Hi,
Thank you for your reply.
I'm not sure how I upgrade mysql modules, so I implemented fixes from https://github.com/michaelmcmillan/LittList/issues/53
It seems like those mysql queries solved my issue. But there is a new issue. When I ran my servers tonight, and as soon as I woke up in the morning; only one of the servers was running.
Here is the new error I'm getting:
http://prntscr.com/bvotbx
Can you help me solve this one as well? I'll pay you money if you're interested, even though I look at coding as art.
Thanks.
Yours sincerely,
Jamie Isaksen
Sent from Mailbird [http://www.getmailbird.com/?utm_source=Mailbird&utm_medium=email&utm_campaign=sent-from-mailbird]
On 21.07.2016 09.45.18, Alex Hultman notifications@github.com wrote:
This is fixed in 0.7.9, you can test it out.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub [https://github.com/Barbosik/MultiOgar/issues/219#issuecomment-234180935], or mute the thread [https://github.com/notifications/unsubscribe-auth/AQ_ckPKGzckf6wqUZkNMsyIWLZ_oiDK3ks5qXyOGgaJpZM4JQaf_].

This is unrelated to uws right?

Well, I'm running my server with uws. So I suppose it might be related.
Thanks
21. jul. 2016 15:54 skrev Alex Hultman notifications@github.com:This is unrelated to uws right?
—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or mute the thread.

Sure but a lost mysql connection should be unrelated. They are completely separate. Unless more people are getting the same problem I wouldn't suspect uws.

Hmm, okay.
Even if the problem might not be related with uws, can you help me fix it?
Thanks.
21. jul. 2016 16:03 skrev Alex Hultman notifications@github.com:Sure but a lost mysql connection should be unrelated. They are completely separate. Unless more people are getting the same problem I wouldn't suspect uws.
—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or mute the thread.

What happens if you run it with ws instead? That would be first step of all. If you can reproduce it with ws then obviously theres no relation to uws.

I have never tried that.. Last night I started both of my servers with uws, then when I woke up this morning, one of them was down.
Should I use ws on the other server? Then I restart the servers and check how long until one of them crashes?
Thanks.
21. jul. 2016 4:53 p.m. skrev Alex Hultman notifications@github.com:What happens if you run it with ws instead? That would be first step of all. If you can reproduce it with ws then obviously theres no relation to uws.
—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or mute the thread.

you need to monitoring for mysql connection and reconnect when it's disconnected.

authors: Barbosik TheGoldenXY alexhultman

repo: Barbosik/MultiOgar


text:
🛑 Executive and Indigenous Affairs is down

In 48d22c1, Executive and Indigenous Affairs (https://www.eia.gov.nt.ca) was down:

HTTP code: 503
Response time: 14677 ms

Resolved: Executive and Indigenous Affairs is back up in eceddf8 after 6 hours, 13 minutes.

repo: Barctic/gnwt-monitor


text:
🛑 Lands is down

In 73a66b6, Lands (https://www.lands.gov.nt.ca) was down:

HTTP code: 503
Response time: 10258 ms

Resolved: Lands is back up in b597902 after 8 minutes.


text:
🛑 Education Culture and Employment is down

In ae1bfb0, Education Culture and Employment (https://www.ece.gov.nt.ca) was down:

HTTP code: 403
Response time: 432 ms

Resolved: Education Culture and Employment is back up in 9b06502.


text:
🛑 Lands is down

In 7667f98, Lands (https://www.lands.gov.nt.ca) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Lands is back up in abd174e.


text:
🛑 Legislative Assembly is down

In 8894533, Legislative Assembly (https://www.ntassembly.ca) was down:

HTTP code: 403
Response time: 284 ms

Resolved: Legislative Assembly is back up in e8bceba.


text:
🛑 Lands is down

In f0917c1, Lands (https://www.lands.gov.nt.ca) was down:

HTTP code: 504
Response time: 318 ms

Resolved: Lands is back up in a1b6fb8 after 8 minutes.


text:
🛑 Municipal and Community Affairs is down

In 5188c03, Municipal and Community Affairs (https://www.maca.gov.nt.ca) was down:

HTTP code: 504
Response time: 288 ms

Resolved: Municipal and Community Affairs is back up in 49127bd after 10 minutes.


text:
🛑 QBitTorrent webUI is down

In 905753f, QBitTorrent webUI (https://qbittorrent.jonthan.xyz) was down:

HTTP code: 404
Response time: 485 ms

Resolved: QBitTorrent webUI is back up in ded0c7d after 7 minutes.

repo: Baronhez/upptime


text:
🛑 QBitTorrent webUI is down

In 60ea908, QBitTorrent webUI (https://qbittorrent.jonthan.xyz) was down:

HTTP code: 404
Response time: 758 ms

Resolved: QBitTorrent webUI is back up in d35022a after 7 minutes.


text:
🛑 QBitTorrent webUI is down

In 20b28ed, QBitTorrent webUI (https://qbittorrent.jonthan.xyz) was down:

HTTP code: 404
Response time: 486 ms

Resolved: QBitTorrent webUI is back up in b5af550 after 6 minutes.


text:
🛑 QBitTorrent webUI is down

In 750ca1b, QBitTorrent webUI (https://qbittorrent.jonthan.xyz) was down:

HTTP code: 404
Response time: 779 ms

Resolved: QBitTorrent webUI is back up in 913cec4 after 6 minutes.


text:
feat(docs): add security to docs

Types of changes

[ ] Bug fix (a non-breaking change which fixes an issue)
[x] New feature (a non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

This allows to deploy docs with Nuxt Security enabled.
This is a first step towards obtaining a security score that can be displayed on the site: see #446
Description

Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes (if not applicable, please state why)

Docs now deployed with security headers

securityheaders.com score: A+

mozilla observatory score: A+

Great piece of work Sebastien! I am glad thatwe will have this as a part of our docs!
You cans afely merge right now to the RC branch :)

Will do now
Can you change the Vercel deploy settings to disable the Live Comments ?
Reason is: this feature injects a post-build script which is not SRI-protected. Removing the script will improve our Mozilla score

repo: Baroshem/nuxt-security