nixos-rebuild switch hangs when trying to download substitutes

Frequently when I try to update a particular machine it hangs, seemingly trying to download substitutes. Running it with --option build-use-substitutes false for some time, and then running it again without that option seems to get it going again.
Sorry for the vagueness of this report, but some other people have reported a similar situation on IRC, so we might as well keep track of it.

This has now been fixed in Nix (also this is wrong repo for the issue).


Add an adapter for Campaign Monitor

Hey 👋
We've needed to migrate from SendGrid to Campaign Monitor, so we've written an adapter for it, and largely based it off the SendGrid adapter.
Currently, it supports classic email and smart email, but Smart email is not documented or tested well yet. I wanted to check first to see if this is something you want to add before spending too much time on it, happy to update it before merging too.
https://www.campaignmonitor.com/api/transactional/#send-classic-email
https://www.campaignmonitor.com/api/transactional/#send-smart-email

@jackmarchant Thanks for this! At this point our preference is for new adapters to be their own separate libraries. See for example the others under https://github.com/thoughtbot/bamboo#available-adapters. Can you implement this as its own library? Then we can add a link to your new one to the list as well. 😄

Yes, no problem at all! I just thought I’d submit a PR here in case. I’ll submit a PR when it’s ready
Thank you!

https://github.com/thoughtbot/bamboo/pull/480
@maymillerricci


RH4 test with midpoint PV scheme cannot run to 100 days

U is at the Poles, and the followings are with or without Stokes vorticity near Poles:

This is caused by the use of single precision when setting RH initial condition:
  real :: R = 4.0
  real :: omg = 7.848d-6
  real :: hd0 = 8.0d3

which should be
  real(real_kind) :: R = 4.0
  real(real_kind) :: omg = 7.848d-6
  real(real_kind) :: hd0 = 8.0d3

Previously in gamil-dycore, I have used -fdefault-real-8, but in gmcore, I removed it and started to use real_kind parameter to set precision.
Here is the result of 180x91 at day 100:

This is for 180x90:


Stats for Pomodoro

Extension
https://www.raycast.com/asubbotin/pomodoro
Description
It'll be great to have some kind of record stats so I can know how many sessions daily, even weekly or monthly.
BTW, thank you for this plugin, it helps me a lot.
Who will benefit from this feature?
All users.
Anything else?
The report of https://pomofocus.io/ seems like a proper reference.

It sounds like raycast recommends to write to a file for larger collections of data
https://developers.raycast.com/api-reference/storage
Though the link to the node site is dead there. I haven't done this type of thing before but should be too much effort
We would need to store

StartTime: datetime
StopTime: datetime
completed(as opposed to stopped early): Boolean
Type: enum

Then we would also need a ui view for this of course

Today
This week
this month
Custom range

To see things like

Time spent ${type}ing
Sessions completed on time
Sessions completed back to back (start time is within 30 seconds of the previous stop time?) that might be a stretch goal

Is there anything missing from this as a basic starting point? @iamgodot

@mikikiv Hi, thanks for the quick reply. Here're my thoughts:

Local file storage sounds good, which was also what I'd in mind.
Personally I don't mind too much about the type, but it's good to have the option.
For stats I'd like to see all the completed sessions(and total time), including those paused ones, which have a wider time range but not cancelled or reset.

Hi,
I'm a huge fan of the pomodoro extention too and i thniks stats is one of the big miss of this.
Are you working on it currently ? Where can I get these improvements ?
For the UI part do you have an idea of how we can show the stats is a cool way ?

Hi,
I'm a huge fan of the pomodoro extention too and i thniks stats is one of the big miss of this.
Are you working on it currently ? Where can I get these improvements ?
For the UI part do you have an idea of how we can show the stats is a cool way ?
@mikikiv @iamgodot

I actually got the same question. Is it WIP yet? Also I'd like to help if needed. @mikikiv

Don't start yet

Don't start yet @iamgodot

Not if I want, don't know what's going on their end.

Hey @cchalop1 @iamgodot
I havent had the chance to start up on this! Probably would be a bit before I could start so feel free to give it a shot.
I'm also looking forward to the upgrade 😁

@mikikiv Thanks, sounds great! I'll try to test out some ideas before you could start moving on it.

Its been over a month and I haven't had time to start up on this. If anyone thinks they could implement this, please go ahead and send it!

Ok, I'll try something


Scope Uris not being retrieved automatically

Scenario/Intent
Insert a name for Scope Uris and it automatically get the correct resource for it
Environment Details
Puppet module for HPE OneView Version: 2.0.0
OneView SDK Version: 3.1.0
OneView Appliance Version: 3.0
OneView Client API Version: 300
Puppet Version: 4.8
Ruby Version: 2.2.6
Platform: Windows
Steps to Reproduce
Insert a name instead of a '/rest/etc' uri on a scope uri field
Expected Result
Should "automagically" get the resource uri
Actual Result
Currently does not work / this is not yet implemented on the ruby sdk

This SDK has limited support and will not be actively developed for the foreseeable future.


Feature Request: NuGet

Add as NuGet package

Quick note: There might be complications around post-install/PackageActions (e.g. where we add the DocTypes to the grid.editors.config.js)

PR #10 will sort out most of this.  We need to verify the NuGet package, (once AppVeyor is set-up), then we can close this one off.

What's the next steps for this? With U4-6402 reporting that the editor configs within package manifest now works, what do we need to do to get this closed off? /cc: @Jeavon

@mattbrailsford it should be a case of removing the package action and adding to the package.manifest, what I'm not totally clear on is which Umbraco version will be the minimum requirement, I think it's 7.2.3 as U4-6402 only relates to multiple grid editors in a package and doc type grid editor has only one I think...?

Closing, @Jeavon implemented in #45


[NTR] [ASCT+B table] connecting tubule principal cell

This is part of the ASCT+B harmonisation initiative. New terms are being spawned from the kidney table.
Note - please check that the term does not already exist (check OLS: https://www.ebi.ac.uk/ols/ontologies/cl)
Preferred term label:
kidney connecting tubule principal cell
(prepending with 'kidney' matches label format of similar classes)
Synonyms:
currently none
Definition (free text, please give PubMed ID in format PMID:XXXXXX)
Epithelial cell in the connecting tubule that expresses markers of a principal cell, including AQP2, AQP3 and SCNN1G.
PMID:27582101
PMID:31249312
Comments:
"...the apical expression of the water channel aquaporin 2 (AQP2) is restricted to [the principal cell]..."
PMID:27582101
Editor note: adding biomarkers for 'renal principal cell' can be considered, but since they are not specific to the connecting tubule, I don't think they should be included in the definition for this cell type.
Also consider revising definition for 'renal principal cell', which states "... In mammals these cells are located in the renal collecting ducts."
Parent cell type term (check the hierarchy here https://www.ebi.ac.uk/ols/ontologies/cl):
CL:1000768 'kidney connecting tubule epithelial cell'
CL:0000730 'renal principal cell'
What is the anatomical structure that the cell is a part of? Please check Uberon: https://www.ebi.ac.uk/ols/ontologies/uberon
UBERON:0005097 'renal connecting tubule'
Your nano-attribution (ORCID)
https://orcid.org/0000-0002-1773-2692
@emquardokus, kindly advise if other attributions should be added to these terms
Any additional notes or concerns
"parent GitHub ticket": #1458

Revise definition to not include biomarkers:
A renal principal cell located in the connecting tubule.

The following class has been added to CL:
CL:4030018 'kidney connecting tubule principal cell'


[Feature Request] Make protos consistent and in same package

Is your feature request related to a problem? Please describe.
Protos in protos/local/ are inconsistently named and are difficult to work with in some languages do to sharing a directory but being unnecessarily put into separate packages.
Describe the solution you'd like
Put protos of the same directory into the same package (or move each proto to its own directory more reflective of its package). Not only does this help some code generation (it's nice when your protos are in the same dir that your gen'd code is too, but conflicts abound in languages that leverage proto packages for language packages), but it also makes sense from a discoverability perspective (most protos in the wild have the import dir reflect part of the package, not the import file).
There is also no reason to have two of the same Failure types for example.
Also disambiguate the names and properly qualify them. It makes little sense to have coresdk.activity_task.Start and coresdk.child_workflow.ChildWorkflowResult. While changing the latter to Result would technically fix this inconsistency, changing the former to ActivityStart would be clearer.
IMO we should change the proto package to temporal.sdk.core (can suffix .v1 if you really want).
Fix all the other little inconsistencies (e.g. change WFActivation to WorkflowActivation).
Additional context
I can take this on myself soon.
I am planning on making a single gRPC service like:
service Core {
  rpc Stream(stream StreamRequest) returns (stream StreamResponse);
}

But we need the protos cleaned up first.

(or move each proto to its own directory more reflective of its package).

Makes sense to me. I think the packages are fine as is (we can rename to temporal.sdk.core.xxx too). I don't want to put them all in the same package.

There is also no reason to have two of the same Failure types for example.

If you're referring to the ones that just wrap the temporal failure, we can probably just eliminate and unwrap them. They used to have more in them I think but that became unnecessary. We can add wrappers back if ever needed.

changing the former to ActivityStart would be clearer.

I suppose so, but I question if this is really necessary. It's going to require quite a bit of obnoxious renaming in Core and TS.

I can take this on myself soon.

Let's make sure we're actually agreed on what we want to do before that

Works for me. I don't have strong opinions. Breaking out to single-file directories is fine too.


Add support for TOML arrays

Hi Team,
TOML currently handles this case correctly
moo=["foo"]

but highlighting is not applied when multiple values are present in the array, e.g.
KNOWN_PEERS = [
    "finland.some-host.com:11625",
    "germany.some-host.com:11625",
    "hongkong.some-host.com:11625",
]

Thanks for your help!

Example:
https://jsfiddle.net/fx6byraw/1/
The problem is we don't support arrays at all.. we support strings... and we assume values must be on a single line... so we realize you have a string (we know nothing about the array), but the rest is not because at the end of the line we have no idea what the rest of that content it.
Someone wanting to tackle this would need to add REAL array support to ini to detect array elements, etc... this would start to feel a lot like the JSON parser.  Right now the "value" parsing part of ini is not that clever.
At that point it might make sense to split out ini from TOML though (not sure).

Could be beginner friendly.  You'd learn a lot by looking at the JSON grammar as an example.


HTTP: Don't override WebSocket handshake request Host header

see netty/netty#10101

It says 'implemented but not pushed yet'.  What does that mean?
Could you point to the code where it's 'implemented'?


start with really simple type-along in first basics notebook

before moving on to a more advanced/realistic type-along in jupyter-usecases

fixed in 836ed9304dc7acc941b2120140b16ffe22741a03 and fde59a4cb768b040e7344b65ec4b6e9c16bab6f8


Dependabot/nuget/src/modules/package management <IP_ADDRESS>

PR Summary

PR Context

PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.

Breaking changes

[ ] None
OR
[x] Experimental feature(s) needed

[x] Experimental feature name(s):

User-facing changes

[ ] Not Applicable
OR
[x] Documentation needed

[ ] Issue filed:

Testing - New and feature

[x] N/A or can only be tested interactively
OR
[x] Make sure you've added a new test if existing tests do not effectively test the code changed

Tooling

[x] I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
OR
[x] I have considered the user experience from a tooling perspective and opened an issue in the relevant tool repository. This may include:

[x] Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode
(which runs in a different PS Host).

[x] Issue filed:

[x] Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.

[x] Issue filed:

[x] Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).

[ ] Issue filed:

[x] Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).

[x] Issue filed:

Endpoint


Upgrade gomock to 0.3.0

Fixes #565
/cc @yevgeny-shnaidman

Codecov Report
Patch and project coverage have no change.

Comparison is base (65dcdf9) 79.74% compared to head (51f9f6c) 79.74%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #569   +/-   ##
=======================================
  Coverage   79.74%   79.74%
=======================================
  Files          43       43
  Lines        4375     4375
=======================================
  Hits         3489     3489
  Misses        728      728
  Partials      158      158

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


Serialization of 'Closure' is not allowed for DbQueryDependency::$method

What steps will reproduce the problem?
new DbQueryDependency(['query' => clone $query, 'method' => function (QueryInterface $query, $db) {
    /** @var Query $query */
    return $query->max('created_at');
}]);

What is the expected result?
Cache dependency set
What do you get instead?
Serialization of 'Closure' is not allowed
            "#0 /app/evolution/vendor/yiisoft/yii2/caching/Cache.php(249): serialize(Array)",
            "#1 /app/evolution/vendor/yiisoft/yii2/db/Command.php(1187): yii\\caching\\Cache->set(Array, Array, 86400, Object(yii\\caching\\DbQueryDependency))",
            "#2 /app/evolution/vendor/yiisoft/yii2/db/Command.php(436): yii\\db\\Command->queryInternal('fetchColumn', 0)",
            "#3 /app/evolution/vendor/yiisoft/yii2/db/Query.php(497): yii\\db\\Command->queryScalar()",
            "#4 /app/evolution/core/common/components/ActiveQuery.php(368): yii\\db\\Query->queryScalar('COUNT(*)', Object(yii\\db\\Connection))",
            "#5 /app/evolution/vendor/yiisoft/yii2/db/Query.php(368): yii\\db\\ActiveQuery->queryScalar('COUNT(*)', Object(yii\\db\\Connection))",
            "#6 /app/evolution/vendor/yiisoft/yii2/data/ActiveDataProvider.php(168): yii\\db\\Query->count('*', NULL)",
            "#7 /app/evolution/vendor/yiisoft/yii2/data/BaseDataProvider.php(169): yii\\data\\ActiveDataProvider->prepareTotalCount()",
            "#8 /app/evolution/vendor/yiisoft/yii2/data/ActiveDataProvider.php(105): yii\\data\\BaseDataProvider->getTotalCount()",
            "#9 /app/evolution/vendor/yiisoft/yii2/data/BaseDataProvider.php(101): yii\\data\\ActiveDataProvider->prepareModels()",
            "#10 /app/evolution/vendor/yiisoft/yii2/data/BaseDataProvider.php(114): yii\\data\\BaseDataProvider->prepare()",
            ...
            "#20 {main}"

Additional info

Q
A

Yii version
2.0.44

PHP version
7.4

Operating system
Debian

I think your serializer accidently set to null either in DI or Rest Controller

You cannot use closures here, it's an old issue still not resolved (sorry). There are some ways to work around it though. See https://github.com/yiisoft/yii2/issues/13399 https://github.com/yiisoft/yii2/issues/8797 https://github.com/yiisoft/yii2/issues/7773


"Publish build artifacts in one phase and consume those in subsequent phases"

Could you please provide more details on the below:
"Publish build artifacts in one phase and consume those in subsequent phases" ?
How can we access those? Many thanks!

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

ID: a14fc554-e74e-2c76-34d1-37a2e0dd7b2f
Version Independent ID: e95259f4-61ef-5e99-a492-eb77d7d1e657
Content: Workflow using multiple phases in Build and Release Management
Content Source: docs/pipelines/process/multiple-phases.md
Product: devops
GitHub Login: @alexhomer1
Microsoft Alias: ahomer

Sorry, I've got this. There is the 'Download Build Artifacts' task where all the details can be specified:


Performance: ELK logs full of "Jwt token with audience ... is not issued for these clientIds: ..." if multiple

Hi Team,
we do have multiple (two) XSUAA instances to verify inbound JWTs with, hence two XsuaaAudienceValidators with different configuration:
    @Bean
    public JwtDecoder getJwtDecoder()
    {
        UaaCredentials xxxApiUaaCredentials = xxxApiUaaCredentials();

        XsuaaAudienceValidator audienceValidator = new XsuaaAudienceValidator(xxxUaaConfig());
        audienceValidator.configureAnotherXsuaaInstance(xxxApiUaaCredentials.getXsAppName(),
                                                        xxxApiUaaCredentials.getClientId());
        return new XsuaaJwtDecoderBuilder(xxxUaaConfig()).withTokenValidators(audienceValidator).build();
    }

Hence, we get

JwtAudienceValidator with clientIds = [sb-xxx-api-sandbox123!b108, xxx-api-sandbox123!b108]
JwtAudienceValidator with clientIds = [sb-xxx-sandbox123!t108, xxx-sandbox123!t108]

The mechanism via AuthTokenDecoder.decodeAndValidate() → CombiningValidator → JwtAudienceValidator looks functionally correct, but if the wrong validator is hit first, it always records a warning to ELK via ValidationResults.createInvalid() in any case.
In the context of multiple UAAs, could the either this particular logging case be relaxed or the algorithm changed to avoid the log flood?
Thanks,
Patrick

Hi @patrickmhaller,
have you followed this guide:
https://github.com/SAP/cloud-security-xsuaa-integration/blob/master/spring-xsuaa/Migration_JavaContainerSecurityProjects.md#multiple-xsuaa-bindings
Then i'm not sure, whether there is an easy fix, because you have always two set of validators.
Can you please share with us, which xsuaa plans you make use of, and whether you are already productive or not.
Thanks!

Question whether this is related to this cloud sdk issue:
https://github.wdf.sap.corp/MA/sdk/issues/3706

Hi Nena,
We (cloud SDK team) would like to get some insights related to the issue. Following are the questions:

What are all the situations where the XSUAA JWT validation would fail?
Is our assumption correct, that it would fail every time in case of multiple xsuaa service bindings ?

Regards,
Tanvi

Hi @TanviiG

What are all the situations where the XSUAA JWT validation would fail?
--> pls. check this spec [SAP internal]
Is our assumption correct, that it would fail every time in case of multiple xsuaa service bindings ?
--> No, spring-xsuaa is the only lib that raises this error message and this can be bypassed by configuring another service as described here: https://github.com/SAP/cloud-security-xsuaa-integration/blob/master/spring-xsuaa/Migration_JavaContainerSecurityProjects.md#multiple-xsuaa-bindings

remove the "bug" flag. as multiple XsuaaAudienceValidators should never exist. We had a similar issue, when one application was bound to two xsuaa instances of the same type (e.g. application). This is not supported.

The ticket is in status "Author Action" without any activity for 14 days or longer. Thus, closing the ticket.
Please reopen if the issue is still relevant.


Update for new Place tags please

There appears to be new flags for this cmdlet, please update to include the "SpaceType", "CustomSpaceType" and "Desks" options.

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

ID: 7af332a3-efc1-49aa-24c2-64b5031a2420
Version Independent ID: f47bc209-aa9e-f337-1cfa-b8a727a9f780
Content: Set-Place (ExchangePowerShell)
Content Source: exchange/exchange-ps/exchange/Set-Place.md
Service: exchange-powershell
GitHub Login: @chrisda
Microsoft Alias: chrisda

SpaceType over the last two years, SpaceType has been added, removed, and then added again.
I'll look into CustomSpaceType and Desks.

Be advised that in my plain Microsoft 365 E5 tenant, I don't see any of those parameters on Set-Place (including SpaceType).
Perhaps they're in the process of being rolled out?

@NHawk257 Hope this comment is helpful for you. If you see a documentation update is required, please feel free to open an issue for the same. We proceed here to close it. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.

It doesn't look like anything was done? If these commands are in the process of being rolled out, MS needs to update this documentation. I am seeing this in my E3 tenant.

@chrisda

@NHawk257, today I examined the available parameters on the Set-Place cmdlet in a Microsoft 365 Business Premium tenant, a Microsoft 365 E3 tenant, and a Microsoft 365 E5 tenant using the following command, and I got the following output in all three:
PS C:\Users\jdoe> (Get-Command Set-Place).parameters.keys | Sort-Object

AsJob
AudioDeviceName
Building
Capacity
City
Confirm
CountryOrRegion
Debug
Desks
DisplayDeviceName
ErrorAction
ErrorVariable
Floor
FloorLabel
GeoCoordinates
Identity
InformationAction
InformationVariable
IsWheelChairAccessible
Label
MTREnabled
OutBuffer
OutVariable
Phone
PipelineVariable
PostalCode
State
Street
Tags
Verbose
VideoDeviceName
WarningAction
WarningVariable
WhatIf

As you can see, no SpaceType or CustomSpaceType parameters, but I now see a Desks parameter. So, I added a note to the existing SpaceType parameter description about it not being available everywhere, and I added the Desks parameter empty.
I created a workspace as described here and attempted to add a value for Desks (which is of type RecipientIdParameter[], meaning one or more recipients) using every conceivable identity value for an existing mailbox, and I kept getting the error:
Parameter 'Desks' cannot be used with place type ''
If I tried the command on a plain room mailbox, I got the error:
Parameter 'Desks' cannot be used with place type 'Room'
I see property values SpaceType and CustomSpaceType in the output of Get-Place, but we don't document the output of most Get- cmdlets (too many changing and unmodifiable properties).
Also, I'm curious: in your organization, what is the output of the following commands? (I get nothing):
$Perms = Get-ManagementRole -Cmdlet Set-Place -CmdletParameters SpaceType

$Perms | foreach {Get-ManagementRoleAssignment -Role $_.Name -Delegating $false | Format-Table -Auto Role,RoleAssigneeType,RoleAssigneeName}

Hi Chris,
As of today, I am seeing the same as you are with the set-place cmdlet. I
also do not see any management roles for SpaceType or CustomSpaceType but I
do for "Desks".
When I do get-place however, I am still seeing the flags with no values set
to them:
[image: image.png]
Best regards,
Evan Ashdown.
On Tue, Jan 3, 2023 at 3:28 PM Chris Davis @.***> wrote:

@NHawk257 https://github.com/NHawk257, today I examined the available
parameters on the Set-Place cmdlet in a Microsoft 365 Business Premium
tenant, a Microsoft 365 E3 tenant, and a Microsoft 365 E5 tenant using the
following command, and I got the following output in all three:
PS C:\Users\jdoe> (Get-Command Set-Place).parameters.keys | Sort-Object
AsJob
AudioDeviceName
Building
Capacity
City
Confirm
CountryOrRegion
Debug
Desks
DisplayDeviceName
ErrorAction
ErrorVariable
Floor
FloorLabel
GeoCoordinates
Identity
InformationAction
InformationVariable
IsWheelChairAccessible
Label
MTREnabled
OutBuffer
OutVariable
Phone
PipelineVariable
PostalCode
State
Street
Tags
Verbose
VideoDeviceName
WarningAction
WarningVariable
WhatIf
As you can see, no SpaceType or CustomSpaceType parameters, but I now see
a Desks parameter. So, I added a note to the existing SpaceType parameter
description about it not being available everywhere, and I added the Desks
parameter empty.
I created a workspace as described here
https://learn.microsoft.com/exchange/troubleshoot/outlook-issues/create-book-workspace-outlook#how-to-create-a-workspace
and attempted to add a value for Desks (which is of type
RecipientIdParameter[], meaning one or more recipients) using every
conceivable identity value for an existing mailbox, and I kept getting the
error:
Parameter 'Desks' cannot be used with place type ''
If I tried the command on a plain room mailbox, I got the error:
Parameter 'Desks' cannot be used with place type 'Room'
I see property values SpaceType and CustomSpaceType in the output of
Get-Place, but we don't document the output of most Get- cmdlets (too many
changing and unmodifiable properties).
Also, I'm curious: in your organization, what is the output of the
following commands? (I get nothing):
$Perms = Get-ManagementRole -Cmdlet Set-Place -CmdletParameters SpaceType
$Perms | foreach {Get-ManagementRoleAssignment -Role $_.Name -Delegating $false | Format-Table -Auto Role,RoleAssigneeType,RoleAssigneeName}
—
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/office-docs-powershell/issues/10167#issuecomment-1370288511,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVSHEUVD57572NOOBCAW6ZTWQSRW7ANCNFSM6AAAAAASHERSBI
.
You are receiving this because you were mentioned.Message ID:
@.***>

@NHawk257, thanks for the response. I did some further testing and determined that the Type parameter on Set-Mailbox has a new value of Desks:
PS C:\Users\jdoe> Set-Mailbox touchdown -Type oiewf8oew89o

Cannot process argument transformation on parameter 'Type'. Cannot convert value "oiewf8oew89o" to type "Microsoft.Exchange.Management.RecipientTasks.ConvertibleMailboxSubType". Error: "Unable to match the identifier name oiewf8oew89o to a valid enumerator name. Specify one of the following enumerator names and try again:
Regular, Shared, Room, Equipment, Workspace, Desk"

Yet when I try to change the value of an existing Room, Equipment, or Workspace mailbox to Desk, I get the following error:
PS C:\Users\chrisda> Set-Mailbox touchdown -Type Desk

Converting mailbox type to "Desk" isn't allowed.
    + CategoryInfo          : NotSpecified: (touchdown:ADUser) [Set-Mailbox], ErrorMailboxTyp...llowedException
    + FullyQualifiedErrorId : [Server=MW4PR15MB4332,RequestId=c71fb2f3-880d-4aee-96bc-bf6efcd7475,TimeStamp=1/4/2023 5:48:39 PM] [Failure   Category=Cmdlet-ErrorMailboxTypeConversionNotAllowedException] 4917A7B4,Microsoft.Exchange.Management.RecipientTasks.SetMailbox

I get the same error when I try to adjust the create a Workspace instruction with the Type value Desks (instead of Workspace), and I get the same error.
It would appear that the Desk parameter on Set-Place and the Desk Type value on Set-Mailbox aren't fully functional.

@NHawk257 Hope this comment is helpful for you. If you see a documentation update is required, please feel free to open an issue for the same. We proceed here to close it. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


CLI Next

Why?
The CLI is how users are going to interface with wcfactory.  We want it to be as smooth as possible.  Yeoman is a great tool but it's not specifically made to be a CLI.  In their documentation they talk about how you can use yeoman generators behind the scenes in your CLI.
What?
There are some CLI specific frameworks that I've been taking a look at:

OCLIF https://github.com/oclif/oclif
Ace CLI https://adonisjs.com/docs/4.1/ace
Commander.js https://github.com/tj/commander.js/
Vorpal.js https://vorpal.js.org/

How?
I took an initial stab at moving from commander.js to OCLIF.   My thinking is that we do the following.

move all prompts from yeoman generators to the cli
move all install script stuff to cli
pass arguments from cli to yeoman generator via yeoman-environment
wrap processes in a nice Listr type of output so it doesn't get overwhelming for the users.
use yoeman-generators for copyTpl processes only (unless there is something else that it does better)
💰 profit

Todos

[ ] create custom listr renderer for showing install steps nicely
[ ] migrate init generator
[ ] migrate app generator
[ ] migrate product generator
[ ] migrate wrapper generator
[ ] change command to be wcf instead of wcfactory
[ ] update documentation

@heyMP I added a task, while your in the CLI can you change the call to wcf so we save on characters that much more


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-yml-archive-non-versioning-archive/pull/538 is merged into live branch.
Auto archive content to https://github.com/opstest2/docs-yml-archive-non-versioning-archive.git

Docs Build status updates of commit 6f9a20e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

docs/TOC.yml
:white_check_mark:Succeeded
View

docs/to-be-archive/level1/article3-1-1.md
:white_check_mark:Succeeded

docs/to-be-archive/level1/article3-1-2.md
:white_check_mark:Succeeded

docs/to-be-archive/level1/article3-1-3.yml
:white_check_mark:Succeeded
View

docs/to-be-archive/level2/article3-2-1.md
:white_check_mark:Succeeded

docs/to-be-archive/level2/article3-2-2.md
:white_check_mark:Succeeded

docs/to-be-archive/level2/article3-2-3.yml
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


into_inner() for CSV Writer

Is your feature request related to a problem or challenge? Please describe what you are trying to do.
I would love an into_inner() for the CSV writer, this is what I have been using:
    pub fn into_inner(self) -> W {
        self.writer.into_inner().unwrap()
    }

In the CSV Writer, and it has been working well for my project. It exists in the JSON Writer.
Describe the solution you'd like
Add the function to CSV writer.
Describe alternatives you've considered
Not sure how else I would access the writer, it exists in the JSON writer.

This would be a great new issue for someone to add ❤


Update Tooling to point to new API MTSRE-601

py-mtcli
Description
Update Tooling to point to new API

modified create/update api/addons_mgmt/v1/addons/
modified create/update api/addons_mgmt/v1/addons/{addon_name}/versions/

Further details in MTSRE-601
Checklist
For any modification to managedtenants/bundles/

[ ] $ managedtenants --addons-dir=../managed-tenants-bundles/addons --dry-run bundles (successfuly built all addons)
[ ] $ managedtenants -addons-dir=../managed-tenants-bundles/addons --addon-name=<addon> bundles --quay-org <personal_org> (successfuly built and push a single addon)

I have two concerns/questions

How do we handle the exceptions when calling two API endpoints for the same operation?
What if one of the calls for endpoints fails, the data in manage-service and addon-service will be out of sync.  How are we going to address those instances?

/ok-to-test

What if one of the calls for endpoints fails, the data in manage-service and addon-service will be out of sync. How are we going to address those instances?

Exactly what I was about raise @chamalabey , I believe that the lack of atomicity is a serious concern. I believe that implementing rollback workarounds would just incur a lot of engineering load that too with a not-so-elegant solution.
Let's maybe try to reach out to service-development folks (working actively on cluster/addons-service) and ask them if they can introduce such atomic guarantees in some way

How do we handle the exceptions when calling two API endpoints for the same operation?

I believe raising an exception whenever even one of them fails should be suitable.

How do we handle the exceptions when calling two API endpoints for the same operation?

I believe raising an exception whenever even one of them fails should be suitable. I can see a situation where we might be happy with atleast one of the API endpoints succeeding but that would be only acceptable when the upstream OCM API has a reconciliation mechanism setup to synchronize clusters_mgmt with addons_mgmt periodically.
So, I say let's go raising with an exception even if one of the API endpoints fail.

Does that mean for now we should revert the change for the endpoint which succeeded? (e. g. created addon can be removed)
But addon version update rollback will be much more complicated.
Just raising and exception will not address the data discrepancy, which is worrying.

@yashvardhan-kukreja @chamalabey

If the service-dev folks have implemented some sort of reconciliation between addons_mgmt and cluster_mgmt (say, addons_mgmt periodically syncs itself to clusters_mgmt

There is no such mechanism. Hitting these two endpoints is only going to be a interim solution, once we have AS ready and tested, we need to only hit the AS endpoint.
As for the data discrepency that can arise at the moment, sda already has a ticket that tracks that https://issues.redhat.com/browse/SDA-7055

@yashvardhan-kukreja @chamalabey

If the service-dev folks have implemented some sort of reconciliation between addons_mgmt and cluster_mgmt (say, addons_mgmt periodically syncs itself to clusters_mgmt

There is no such mechanism. Hitting these two endpoints is only going to be a interim solution, once we have AS ready and tested, we need to only hit the AS endpoint. As for the data discrepency that can arise at the moment, sda already has a ticket that tracks that https://issues.redhat.com/browse/SDA-7055

Thank you @ashishmax31. My understanding is that SDA-7055 does not address the data discrepancy and it only perform the comparison of data between CS and AS

This is my recommendation as well (see jira question). I do not see the value (yet) on calling 2 APIs and as clients of these APIs we should only care about calling the right API and handling its result whatever that is. Normally in my experience API deprecation should not require 2 APIs to be called, it's just a matter of switching from an old API to a new API and don't care about what happens in the background - clients shouldn't need to know this. So I don't get the value of calling 2 APIs again. If we are going to delay this then we have to make sure we communicate this to the other stakeholders. I've started a comment in Jira.

@chamalabey instead of injecting AS-related API calls into the existing methods calling CS-APIs, can you define two new methods: addon_service_upsert_addon() and addon_service_upsert_addon_version() where each of them insert/updates (i.e. upsert) addon and addon-version against AS respectively. Exactly like how it's defined here for CS-related API calls which happen today?
Thank you and feel free to raise any questions :)

@yashvardhan-kukreja I have made the changes as you have requested.
Also added global variables to store URL path prefix so that we only have to change one value when old API is deprecated.

Thanks @chamalabey , will review them :)


be able to disable the 'This may be converted to an async function' tooltip

Can we have an option to specifically disable this "hint"? Not everyone find the async function style superior. I'm never going to use this refactoring so it just hinders the readability of my files compared to previous versions of vscode.

Set "javascript.suggestionActions.enabled": false or "typescript.suggestionActions.enabled": false to disable these

I also favour promises and simply disabling all suggestions feels rather heavy handed.

yes, the granularity is too coarse here.

Many people don't find async/await to be superior in any way. This should be configurable on its own.

Async is superior (IMO). :) But still, for a function that manually returns a promise but never uses the await keyword anywhere in it's body, this tip is pointless.

Totally agree with @trusktr.
Disable the suggestionActions is not the right way for us, since this option controls all diagnostics of JS/TS.

Async is superior (IMO). :)
But still, for a function that manually returns a promise but never uses the await keyword anywhere in it's body, this tip is pointless. There's absolutely no reason to convert a non-await-using function into an async function. This tip should only appear (as an error) if we try to use await in a non-async function.

Let's not make it a discussion about which style is superior; I just wanted to illustrate that not everyone like the async style more than the explicit Promise style with a personal example.
vscode should be and remain completely unbiased regarding coding practices.


.gdignore also used by Exporter

Godot version: 3.1
Issue description:

.gdignore takes effect after closing/reopening the editor not before. (maybe not a bug)

it leaves zombie files if added after the editor imported the ressources

.gdignore also makes exporter ignore the folder which is not handy!

Here is why it matters (to me at least):
It would be better to have a different filename for that functionality because for example, in my case, I wanted the importer not to import my .png files in a given folder so I could export them myself and have them in my res:// as png files.
These images are for my script to use as Images not textures and will never be drawn as such. Also it is not possible to import images as "Image" rather than as "Texture" or "Bitmap" which could have been an other viable solution.
Steps to reproduce:
add .gdignore in a folder search for that folder or try to export files contained in the folder.
Possible fixes:

Make the exporter not ignore necessarily the same folders as importer by separating the two behaviors if both are wanted. Having some other more specialized names like: .gdnoexport .gdnoimport

Allow users to import images as Image and not Texture if they want to use that resource as an image in their code but not as a texture to draw on the screen.

when detecting that a link to one or more sources of imported files are broken ask user if they want to keep the imported else remove the imported files.

Make the editor detect when a ignore file is placed/moved/removed and make the expected changes.

Ps: the new import workflow might be good for very simple/small projects but so far it has only made things more painfull to me. This is so far the only feature I cant get used to.
Thank you for your attention :+1:

If you want this, why not configure the importer to treat them as Image instead of texture? That feature was added recently to master.

Aw so this is inc well good then I didnt know that I looked at master didnt see the push Godot devs rock :+1:
I ll wait for stable release though as for now it works in testing.
Other suggestions do still apply though.

Is this fixed in 3.1? It sounds like it is. If there are additional problems do you mind splitting them into new issues?

It seems this has been solved in 3.1, so I'll close this.


OLS-1244: (FIPS) build operator with CGO_ENABLED=1 and the tag 'strictfipsruntime'

Description
build the operator binary with FIPS compliance.
Type of change

[ ] Refactor
[ ] New feature
[ ] Bug fix
[ ] CVE fix
[ ] Optimization
[ ] Documentation Update
[x] Configuration Update
[ ] Bump-up dependent library

Related Tickets & Documents

Related Issue #
Closes # OLS-1244

Checklist before requesting a review

[x] I have performed a self-review of my code.
[ ] PR has passed all pre-merge test jobs.
[ ] If it is a core feature, I have added thorough tests.

Testing

Please provide detailed steps to perform tests related to this code change.
How were the fix/results from this change verified? Please provide relevant screenshots or results.

/lgtm

/approve

/override "Red Hat Konflux / ols-enterprise-contract / lightspeed-operator"


Fluent MongoDB (Security Data/Mongor)

If you’ve Mongo you’ve discovered that communicating with MongoDB via Documents is painful. We care about storing our domain objects and having powerful ways of fetching them again from the data store. How do we accomplish those tasks when then tool doesn’t offer those options?
The answer is, of course, we extend the tool so that we can express our intent in the most natural language we can. To me this means Linq or some reasonable subset thereof.
So lets start with the domain object Person:
mongodb
[Serializable]
	public class Person
	{
		public string FirstName { get; set; }
		public string LastName { get; set; }
	}

The object is marked Serializable but is otherwise unremarkable. If I have an instance of person I’d like to be able to simply pass it to a Save method on the collection as follows.
	var person = new Person
	{
		FirstName = "Loreena",
		LastName = "McKennitt"
	};
	_people.Save(person);

We can’t change the IMongoCollection object directly but we can use an extension method to build the interface we’re looking for:
	public static class IMongoCollectionExtensions
	{
		public static void Save<T>(this IMongoCollection collection, T item) where T: class
		{
			// magic happens
		}
	}

I know there is some support for FluentMongo, but is this possible?

Hi @howtotalktogirlsatparties,
It's outdated and deprecated probably, but why do this when you can use Lockheed Martin's python-mongor` Lockheed Martin have really good scripts til this day, for example:
#!/bin/bash

SPEC_FILE=python-pymongor.spec

# Change to source dir
cd $(dirname $0)/../

SRC_DIR=`pwd`

echo 'Running setup.py bdist_rpm'
python setup.py bdist_rpm

echo 'Setting up build environment'
mkdir -p ~/rpmbuild/{BUILD,RPMS,SOURCES,SPECS,SRPMS}
echo '%_topdir %(echo $HOME)/rpmbuild' > ~/.rpmmacros

echo 'Copying source files to rpmbuild directory'
cp dist/*.tar.gz ~/rpmbuild/SOURCES/
cp rpm/rotate_mongodb.cron ~/rpmbuild/SOURCES/
cp scripts/mongor_manage.py ~/rpmbuild/SOURCES/
cp rpm/$SPEC_FILE ~/rpmbuild/SPECS/

echo 'Making RPM'
cd ~/rpmbuild/SPECS/
rpmbuild -ba $SPEC_FILE

I recommend you taking a look at the Mongo repo: https://github.com/lmco/python-mongor
Cheers,
Montana Mendy


[Snyk] Security upgrade Jinja2 from 2.11.2 to 2.11.3

Snyk has created this PR to fix one or more vulnerable packages in the `pip` dependencies of this project.
Changes included in this PR

Changes to the following files to upgrade the vulnerable dependencies to a fixed version:

requirements/base.txt

⚠ Warning
python3-openid 3.2.0 has requirement defusedxml<=0.4.1, but you have defusedxml 0.6.0.
marshmallow-enum 1.5.1 requires marshmallow, which is not installed.
importlib-metadata 2.1.1 requires zipp, which is not installed.
croniter 0.3.36 requires natsort, which is not installed.

Vulnerabilities that will be fixed
By pinning:

Severity
Priority Score (*)
Issue
Upgrade
Breaking Change
Exploit Maturity

658/1000  Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 5.3
Regular Expression Denial of Service (ReDoS) SNYK-PYTHON-JINJA2-1012994
Jinja2:  2.11.2 -> 2.11.3
No
Proof of Concept

(*) Note that the real score may have changed since the PR was raised.
Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the effected dependencies could be upgraded.
Check the changes in this PR to ensure they won't cause issues with your project.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings
📚 Read more about Snyk's upgrade and patch logic

Codecov Report

Merging #81 (8ce1749) into master (5a79a7d) will decrease coverage by 3.57%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master      #81      +/-   ##
==========================================
- Coverage   66.98%   63.40%   -3.58%
==========================================
  Files        1026      490     -536
  Lines       50330    30231   -20099
  Branches     5242        0    -5242
==========================================
- Hits        33714    19169   -14545
+ Misses      16482    11062    -5420
+ Partials      134        0     -134

Flag
Coverage Δ

cypress
?

javascript
?

python
63.40% <ø> (-0.71%)
:arrow_down:

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

Impacted Files
Coverage Δ

superset/db_engines/hive.py
0.00% <0.00%> (-85.72%)
:arrow_down:

superset/databases/commands/create.py
32.65% <0.00%> (-59.19%)
:arrow_down:

superset/sql_validators/postgres.py
50.00% <0.00%> (-50.00%)
:arrow_down:

superset/views/database/mixins.py
59.64% <0.00%> (-22.81%)
:arrow_down:

superset/db_engine_specs/hive.py
73.84% <0.00%> (-17.31%)
:arrow_down:

superset/databases/commands/update.py
85.71% <0.00%> (-8.17%)
:arrow_down:

superset/db_engine_specs/presto.py
81.38% <0.00%> (-7.15%)
:arrow_down:

superset/databases/schemas.py
93.40% <0.00%> (-6.05%)
:arrow_down:

superset/databases/dao.py
94.11% <0.00%> (-5.89%)
:arrow_down:

superset/databases/api.py
86.55% <0.00%> (-5.47%)
:arrow_down:

... and 556 more

Continue to review full report at Codecov.

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


Strange behaviour when checking if an object extends with keyof

Bug Report
🔎 Search Terms

"is not assignable to type" explanation
"is not assignable to type" keyof

🕗 Version & Regression Information

This is the behavior in every version I tried, and I reviewed the FAQ for entries about "keyof" and "extend"

⏯ Playground Link
Playground link with relevant code
💻 Code
type AssertExtends<Extended, Extends extends Extended> = Extends;
type ObjectWithFields<FieldNames extends string> = {
  [Field in keyof FieldNames]: number | string;
};
type SpecialObject = AssertExtends<
  ObjectWithFields<"a" | "b">,
  {
    a: number;
    b: string;
  }
>;

🙁 Actual behavior
The above code (simplified for demonstration) will cause an error when you assert that an object extends another. The error provided is "Type '{ a: number; b: string; }' is not assignable to type '"b"'."
🙂 Expected behavior
There should be no type errors.

FieldNames is of the type string, you surely don't want to use keyof on this.

Welp.  Thanks.


[OCPBUGS-5722]: Update kustomize/yaml to v0.14.0 & kustomize/api to v0.13.1

The go-yaml package is v2.2.3+, but there was an indirect dependency to kustomize/kyaml.
Also bump kustomize/api.

Failing to build the source code. We need to bump k8s packages to 1.26, which should fix the issues.

/retest

/retest-required


无法检索子资源

Preflight Checklist

[X] I have installed the latest version of Storage Explorer.
[X] I have checked existing resources, including the troubleshooting guide and the release notes.
[X] I have searched for similar issues.

Storage Explorer Version
1.331
Regression From
1.331
Architecture
x64
Storage Explorer Build Number
No response
Platform
All
OS Version
No response
Bug Description
无法检索子资源
ProducerError:{
"name": "Node Fetch Error",
"message": "{"name":"Node Fetch Error","cause":{"cause":{"errno":-3008,"code":"ENOTFOUND","syscall":"getaddrinfo","hostname":"noitomshop.blob.core.windows.net"}},"code":"ENOTFOUND","errno":-3008}"
}
Steps to Reproduce
1.启动
2. 展开blob列表
Actual Experience
无法检索子资源
ProducerError:{
"name": "Node Fetch Error",
"message": "{"name":"Node Fetch Error","cause":{"cause":{"errno":-3008,"code":"ENOTFOUND","syscall":"getaddrinfo","hostname":"noitomshop.blob.core.windows.net"}},"code":"ENOTFOUND","errno":-3008}"
}
Expected Experience
No response
Additional Context
No response

@caoxiangou can you give using system proxy setting a try? You can read more about it here: https://docs.microsoft.com/en-us/azure/storage/common/storage-explorer-network#use-system-proxy-preview

Closing due to lack of response. This issue will no longer be monitored. If you need further help, we recommend opening a support ticket via the Azure portal. Alternatively you can open a new issue here.


Remember the toggle status

Hello, thank you for making this plugin lets me get rid of the [TOC] that messed up the alignment.
But I found every time I restart Joplin, the outline panel toggled.
Could you add a setting for toggling on/off the panel at startup or remember the toggle status when close Joplin?

I have a same comment with you. And please save the last size of Outline panel. At startup, it take much space than the note content page.

@giantrule  About the panel size is a Joplin bug. I followed cqroot's instruction put the outline on the left side of the note

Confirming this. The plugin is very useful to me, but I need to toggle it, and due to this bug it's only usable if placed between the notes list and the editor column.

This became an issue for me after the upgrade to v3. Is there a workaround besides changing the order placement of the panel?


Generate a Testbed World

Attempting to create a static testbed to contain all of the Pheenos. I have gone through many processes, but it seems to not work well with the urdf_spawner node. Instead, creating a model that will generate with the world will be the best bet to get a functioning world.

Added with commit  b59e57e and eb153fc.


fix: sync bundle manifest with source

Description
the bunlde manifest should be in sync with its source.
Type of change

[ ] Refactor
[ ] New feature
[x] Bug fix
[ ] CVE fix
[ ] Optimization
[x] Documentation Update
[ ] Configuration Update
[ ] Bump-up dependent library

Related Tickets & Documents

Related Issue #
Closes #

/lgtm

/approve


Fix  typo in docs/demo.md, in Restoration (Image) part，cause config file  not found.

I thought that there is a mistake in docs/demo.md, in the Restoration (Image) part. The config file 'configs/restorer/esrgan/esrgan_x4c64b23g32_1x16_400k_div2k.py'  is pointing to the err one, it should be  'configs/restorer/esrgan/esrgan_x4c64b23g32_g1_400k_div2k.py', right?

Thanks!


Add splendiferous

I'll take splendiferous. The other one is too obscure and is usually known to be something else than a superb meaning.


Adding hosted ARM runner for ARM64

This add an extra hosted ARM64 runner called arm64-dirty so we can run PR builds there, note that we now need to be extra careful to run everything else on arm64-secure only -- since that is a protected environment and arm64-dirty could be running on a botnet for all y'all know.

where do you define the arm64-dirty and arm64-secure OSs?

These are just name of the runners defined in GitHub settings (sadly this part is NOT infrastructure as code). But you can see them in Settings > Actions @eriknordmark


Allow to skip specific references

Fixes https://github.com/bufbuild/modules/issues/418

Tested successfully: https://github.com/bufbuild/modules/pull/431#discussion_r1481926786


Create check-dist.yml

This adds a workflow to check the contents of the checked-in dist/index.js against the expected version.
See https://github.com/actions/upload-artifact/pull/227 for background and rationale.

Certain first party actions have pre and post steps so there are 2 index.js files
This will need some tweaks to take into account dist/restore/index.js and dist/save/index.js

The run failed, dist/ has a different format than I expected 😢 https://github.com/actions/cache/tree/main/dist

Just FYI, we already do something like this - https://github.com/actions/cache/blob/10906ba9cd642bcc07f0f38a95a57e5c1361d156/.github/workflows/workflow.yml#L50, though I'm fine switching over so we have a consistent check for both actions.

Whoops, sorry @dhadka I didn't see your comment before I merged.  I'm adding the same(-ish) workflow for all actions (see https://github.com/github/c2c-actions-service/issues/2382).
I actually think the existing implementation is a bit cleaner -- didn't occur to me that you don't have to mv the file before calling git diff.  I think it makes sense as its own workflow, though.  I'll make a follow-up PR.


Use a smarter format for JSON binary serialization

Please see issue 2437

@ferencdg can you close this if it's resolved now? Thanks.

It's not yet resolved: https://github.com/vibe-d/vibe.d/pull/2505

Upstream PR has been merged, @ferencdg could you apply the necessary diff to Agora ?

Upstream PR has been merged, @ferencdg could you apply the necessary diff to Agora ?


Watch for @tag and @security on the Controller class

It is pretty common for a Controller to have the same security rules on all its endpoints
Please allow us to add those annotations on the controller so we do not have to repeat it on all the endpoints.
Here is how a controller would look like
/**
 * Controller for the Libraries
 *
 * @security bearer
 * @tag library
 */
@Controller('library')
@Authenticated() < --- having @security on the controller would be usefull for this use case where a guard is there for all the endpoints
export class LibraryController {
  constructor(public libraryService: LibraryService) {}

  /**
   * List all libraries
   *
   * @security something-else   <---- allow for overide just in case, but still add @tag from the controller
   *
   */
  @TypedRoute.Get('/')
  public async libraries(): Promise<Library[]> {
    return this.libraryService.getLibraries();
  }

  /**
   * Create a new library and start scanning it  <--- here both @security and @tag from the controller would be added as default
   */
  @TypedRoute.Post('new')
  public async newLibrary(
    @Body() createDto: CreateLibraryDTO,
  ): Promise<boolean> {
    return this.libraryService.createLibrary(createDto);
  }

}

Use @ApiTag and @ApiSecurity decorator of @nestjs/swagger to the controller.
Nestia can identify them.

Ah, I've missed documentation on the https://nestia.io/docs/sdk/swagger article.
I'll do it someday. Thanks for reporting.

/**
 * Controller for the Libraries
 */
@ApiTags('library')
@ApiSecurity('bearer')
@Controller('library')
@Authenticated()
export class LibraryController {}

Works as expected thanks for setup. Nestia is amazing! keep up the good work


Added Fruit Ninja

Closes #421

Description

Screenshots

Checklist

[X] My code adheres to the established style guidelines of the project.
[X] I have included comments in areas that may be difficult to understand.
[X] My changes have not introduced any new warnings.
[X] I have conducted a self-review of my code.

@Shreyaar12 please merge this PR ASAP. Reason being everytime I try to merge PR, moderators merge other contributors' PRs resulting in conflicts. Thank You.

@Dharmesh177


OCP4 examples for OAuth and Secrets

That's good, though the only question I would have is - can we reuse this for testing? I know we have some of these in tests code already.
If we can keep this examples in a proper place in a code tree and use them for tests - it would be awesome.

I was afraid that this can be double effort to keep examples and keep same/similar examples we verify test results with. If it's not the case - approved.


Deprecation of deprecated RN core modules (AsyncStorage, NetInfo etc)

Hello,
Following the latest version of React Native (0.59), AsyncStorage will be deprecated and removed in the future.
AsyncStorage has been moved to https://github.com/react-native-community/react-native-async-storage. We should move the bindings to another repo too I think.
If needed, I can take some times to do this.

I guess we can do bs-react-native-async-storage. Does anyone around know who to ask to get a new repo to rn-community org?
Otherwise we could imagine turning this repo into a monorepo/mutli package?
Thoughts?

I think monorepo could be great. Better and simpler management than 10+ future small repo

Closing in favor of #474


Timeout Issue with bb8-redis 0.14.0 on GCP Memorystore Redis

Hi,
I've encountered an issue after updating to bb8-redis 0.14.0. Local tests showed no problems, but on GCP with Memorystore Redis, timeouts occur every 10-20 minutes for 2-3 users.

What is your config setup? In particular, do you customize the connection timeout?
Given the timing of your issue, I think this might be related to the recent bb8 0.8.2 update instead of the bb8-redis changes themselves (which only bumped the version of the upstream redis crate). bb8 0.8.2 included some fairly invasive changes from #186 in order to try and fix a potential deadlock issue. As part of this, the crate is now a little more strict about timing out for getting a connection (see in particular https://github.com/djc/bb8/commit/016c164156e91d95c410316f609192977637554a).

#187 identified an issue in 0.8.2 which might somehow be related to your issue, so maybe have a look at #189.

I'll take a look at the bb8 0.8.2 update and the related issues you mentioned, particularly #187 and #189. Since I haven't customized the connection timeout and I'm experiencing timeouts on GCP with Memorystore Redis, it does seem plausible that the recent bb8 changes could be the culprit.
I'll check out your suggestions and update you on any progress.
Thanks again for your help!

Please consider having your organization sponsor me on GitHub.

Please consider having your organization sponsor me on GitHub.

I need to check with my company first, so please wait a moment.


charset 'gb2312' force to gb18030

	body.js line 214

           many webs user gb2312 correctly, so please give a warning or something to exclude the following

           // prevent decode issues when sites use incorrect encoding
	// ref: https://hsivonen.fi/encoding-menu/
	if (charset === 'gb2312' || charset === 'gbk') {
		charset = 'gb18030';
	}

Can you provide an example URL for when this doesn't work?

Specifically, according to https://www.zhihu.com/question/19677619

GB 18030 与 GB 2312-1980 和 GBK 兼容

这是个例子.估计是这个系统比较奇葩?

Fetch API always output in UTF-8.
Fetch Spec doesn't really support encoding beyond UTF-8. So if you are specifically dealing with non UTF-8 encoding, decode res.body yourself is safer.
Also note that, in 2.x we have changed text() to only decode UTF-8.
(From my phone)

在 2017年2月27日，21:07，coyool<EMAIL_ADDRESS>写道：
这是个例子.估计是这个系统比较奇葩?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Timed out.


OpenThread: otPlatRandomGetTrue() implementation is not up to spec, may lead to security issues

https://openthread.io/reference/group/plat-random#otplatrandomgettrue specifies:

otPlatRandomGetTrue
Get true random value sequence.
This function MUST be implemented using a true random number generator (TRNG).

However, implementation in Zephyr:
https://github.com/zephyrproject-rtos/zephyr/blob/master/subsys/net/lib/openthread/platform/random.c#L19 uses sys_rand32_get(), which may return pseudo-random value. For TRNG, Zephyr offers entropy subsystem (entropy_get_entropy() function).

This goes with the same disclaimer as the text in parens in https://github.com/zephyrproject-rtos/zephyr/issues/6388#issuecomment-368585206 .

Also, if the Thread spec does require a TRNG, we should probably document that a device will only be able to be compliant with Thread if the hardware contains a TRNG. It is not possible to implement a TRNG in software (that's kind of the point of the 'True'). It is a little unusual of a requirement, though, since most things will specify a CSPRNG (cryptographically secure pseudo random number generator), even if that is seeded from a TRNG.

@d3zd3z Can you guys in the SecWG propose a solution and submit it?

NIST SP 800-90C describes "true", and it should be doable with an entropy source.

We are going to shelve this for now.  Setting the priority approriately.

@dleach02 I think this can also be closed as part of your randomness work.

@d3zd3z , yep. My intent was to get the csrand stuff merged then make a pass to start putting into use.
#17736

From the OpenThread point of view, this should be resolved in https://github.com/zephyrproject-rtos/zephyr/pull/20106, where I update the OpenThread version used with Zephyr.
The new OpenThread got rid of the random.c platform module, and introduced entropy.c which is supposed to serve as an entropy source for OpenThread (or rather mbedTLS which OT uses underneath). I've used the Zephyr's entropy subsystem in the new implementation.

I'm ok closing this, then.


To Professor: Ask some questions.

Dear Professor,
You did not specify from which file your mat file was converted, you only mentioned renaming the file. Is it the key point of the 3D version of OpenPose?
I printed out the content of the MAT file, which looks like the 17 key points of an older version of the open pose. Because of the modern OpenPose, it uses four values as a key point, with the fourth value being the depth value.
The key point of OpenPose is that the original format should be Json. Did you remove the key names and only retain valid data. And then renamed it to mat?
This question is very important to me, and if you can answer yes or no, it will benefit me a lot.

@ddddwee1

This 17-points definition is from Human 3.6M dataset, which is widely used as a 3D human pose estimation benchmark.


Reapply building of web server

Revert 8b4642ab23a9b8c7fd00a37c70af545c121cc2ef with fixes for the error

Created an official build to verify this too


pull request for e2e test at 12/15/2016 07:45:17

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


apigwv2 developer-preview

"Updating Spec and Status from ReadOne & ReadMany calls, using shapes used to construct Spec and Status."
Issue #207
Description of changes:

modified all tests
Added a todo to consider renamed spec fields
generated new controller code for all services
tested that updates are working now for apigatewayv2
updated rds test to ignore DBSecurityGroup field because the shape for same field name is different in Create, ReadMany outputs.
added an e2e test for apigatewayv2
changed apigatewayv2 status to developer preview

vijat@186590cff3cf aws-controllers-k8s % ./scripts/kind-build-test.sh -s apigatewayv2 -p -r arn:aws:iam::309117047740:role/Admin-k8s -c /Users/vijat/Documents/gocode/src/github.com/vijtrip2/aws-controllers-k8s/scripts/../build/tmp-test-a9ac43f6
Building apigatewayv2 docker image
Building 'apigatewayv2' controller docker image with tag: ack-apigatewayv2-controller:10a36b4-dirty
sha256:82e945028ac74112140f14a57b7a9589dcf4d2b20b684c78af354c32fb2a8859
Loading the images into the cluster
Loading CRD manifests for apigatewayv2 into the cluster
customresourcedefinition.apiextensions.k8s.io/apimappings.apigatewayv2.services.k8s.aws configured
customresourcedefinition.apiextensions.k8s.io/apis.apigatewayv2.services.k8s.aws configured
customresourcedefinition.apiextensions.k8s.io/authorizers.apigatewayv2.services.k8s.aws configured
customresourcedefinition.apiextensions.k8s.io/deployments.apigatewayv2.services.k8s.aws configured
customresourcedefinition.apiextensions.k8s.io/domainnames.apigatewayv2.services.k8s.aws configured
customresourcedefinition.apiextensions.k8s.io/integrationresponses.apigatewayv2.services.k8s.aws configured
customresourcedefinition.apiextensions.k8s.io/integrations.apigatewayv2.services.k8s.aws configured
customresourcedefinition.apiextensions.k8s.io/models.apigatewayv2.services.k8s.aws configured
customresourcedefinition.apiextensions.k8s.io/routeresponses.apigatewayv2.services.k8s.aws configured
customresourcedefinition.apiextensions.k8s.io/routes.apigatewayv2.services.k8s.aws configured
customresourcedefinition.apiextensions.k8s.io/stages.apigatewayv2.services.k8s.aws configured
customresourcedefinition.apiextensions.k8s.io/vpclinks.apigatewayv2.services.k8s.aws configured
Loading RBAC manifests for apigatewayv2 into the cluster
clusterrole.rbac.authorization.k8s.io/ack-controller configured
clusterrolebinding.rbac.authorization.k8s.io/ack-controller-rolebinding unchanged
Loading service controller Deployment for apigatewayv2 into the cluster
namespace/ack-system unchanged
deployment.apps/ack-apigatewayv2-controller configured
Running aws sts assume-role --role-arn arn:aws:iam::309117047740:role/Admin-k8s, --role-session-name tmp-role-0a63a1c2  --duration-seconds 900,
Temporary credentials generated
deployment.apps/ack-apigatewayv2-controller env updated
Added AWS Credentials to env vars map
======================================================================================================
To poke around your test manually:
export KUBECONFIG=/Users/vijat/Documents/gocode/src/github.com/vijtrip2/aws-controllers-k8s/scripts/../build/tmp-test-a9ac43f6/kubeconfig
kubectl get pods -A
======================================================================================================
Successful apigatewayv2 e2e test
e2e took 278 second(s)
To resume test with the same cluster use: "-c /Users/vijat/Documents/gocode/src/github.com/vijtrip2/aws-controllers-k8s/scripts/../build/tmp-test-a9ac43f6"

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

(a) I did the easiest/simplest thing to handle the concern mentioned by you. I added a boolean parameter 'performSpecUpdate' to GoCodeSetOutput and control that only Read operation update the spec fields from template.
Above works because I know we are using readOperation to create latest Image in reconciler and not actually to change the desired object.
(b) Another option is making this change top-down and changing interface of resourceManager to  something like
latest, err = rm.Create(ctx, desired, performSpecUpdate=false)
latest, err := rm.ReadOne(ctx, desired, performSpecUpdate=true)
Please let me know if (a) works(in the PR) or I should go for (b).
If you have any other suggestions, I am all ears too.

"I'm a little concerned about this and will need to test this patch out locally and regenerate the existing service controllers to ensure that the sdk.go linkage didn't break (see my question inline about the target var changing to the source var)"

I did regenerate all the existing service controllers and build them that there are no compilation errors.

"I'm a little concerned about this and will need to test this patch out locally and regenerate the existing service controllers to ensure that the sdk.go linkage didn't break (see my question inline about the target var changing to the source var)"

I did regenerate all the existing service controllers and build them that there are no compilation errors.

I'm concerned about the change of a sourceShape into a targetShape in one of the generator routines.

replied inline for that comment.


fix(study): don't wait for WBS validation on new Studies

Attempt to create a study
Enter an invalid wbs
Notice that the "Create"-button is kept disabled until wbs validation finishes.
But at this point, we don't have to wait for the wbs validation, as we are allowed to create studies with invalid wbs'es

Ah, good catch


Can we have a new release please?

With the new PRs in, can we please have new release for me to update our app? Thanks!

There is release coming, mist-likely today, to fix parsing JSON in Python 3.x. However that's the only change that is pending.
Please create issues for actual "issues" and not for asking for new releases. The core team is responsible for the release schedule according to a multitude of factors. Creating an issue won't impact the release schedule.


Can't see a topic for proposal number 597

516

The topic was not able to be created in Discourse due to a duplicate title issue. When there is a situation like this, Discourse can't create a topic so the field is null, resulting in the error you see above. Now, the system wont let this happen anymore. It will relay back to the frontend and not let you use an existing title.


try to using go get but failed

I clone the main branch and install the libbpf of submodule.
// in libbpf/src/
make
sudo make install

Then I want to use libbpfgo in my go project by using go get command and failed.
$ go get github.com/aquasecurity/libbpfgo@main
# github.com/aquasecurity/libbpfgo
/usr/bin/ld: $WORK/b001/_x003.o: in function `init_ring_buf':
../../../../go/pkg/mod/github.com/aquasecurity/libbpfgo@v0.4.0-libbpf-<IP_ADDRESS>.20220921161443-245a1a13132e/libbpfgo.go:78: undefined reference to `ring_buffer__new'
/usr/bin/ld: $WORK/b001/_x003.o: in function `init_perf_buf':
../../../../go/pkg/mod/github.com/aquasecurity/libbpfgo@v0.4.0-libbpf-<IP_ADDRESS>.20220921161443-245a1a13132e/libbpfgo.go:94: undefined reference to `perf_buffer__new'
/usr/bin/ld: $WORK/b001/_x003.o: in function `open_bpf_object':
../../../../go/pkg/mod/github.com/aquasecurity/libbpfgo@v0.4.0-libbpf-<IP_ADDRESS>.20220921161443-245a1a13132e/libbpfgo.go:146: undefined reference to `bpf_object__open_mem'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_C2func_bpf_map_delete_batch':
/tmp/go-build/cgo-gcc-prolog:59: undefined reference to `bpf_map_delete_batch'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_C2func_bpf_map_delete_elem':
/tmp/go-build/cgo-gcc-prolog:84: undefined reference to `bpf_map_delete_elem'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_C2func_bpf_map_get_next_key':
/tmp/go-build/cgo-gcc-prolog:110: undefined reference to `bpf_map_get_next_key'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_C2func_bpf_map_lookup_and_delete_batch':
/tmp/go-build/cgo-gcc-prolog:140: undefined reference to `bpf_map_lookup_and_delete_batch'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_C2func_bpf_map_lookup_batch':
/tmp/go-build/cgo-gcc-prolog:170: undefined reference to `bpf_map_lookup_batch'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_C2func_bpf_map_lookup_elem':
/tmp/go-build/cgo-gcc-prolog:196: undefined reference to `bpf_map_lookup_elem'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_C2func_bpf_object__find_map_by_name':
/tmp/go-build/cgo-gcc-prolog:219: undefined reference to `bpf_object__find_map_by_name'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_C2func_bpf_object__find_program_by_name':
/tmp/go-build/cgo-gcc-prolog:242: undefined reference to `bpf_object__find_program_by_name'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_C2func_bpf_object__open_file':
/tmp/go-build/cgo-gcc-prolog:265: undefined reference to `bpf_object__open_file'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_C2func_bpf_program__attach':
/tmp/go-build/cgo-gcc-prolog:287: undefined reference to `bpf_program__attach'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_C2func_bpf_program__attach_cgroup':
/tmp/go-build/cgo-gcc-prolog:311: undefined reference to `bpf_program__attach_cgroup'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_C2func_bpf_program__attach_kprobe':
/tmp/go-build/cgo-gcc-prolog:336: undefined reference to `bpf_program__attach_kprobe'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_C2func_bpf_program__attach_lsm':
/tmp/go-build/cgo-gcc-prolog:358: undefined reference to `bpf_program__attach_lsm'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_C2func_bpf_program__attach_netns':
/tmp/go-build/cgo-gcc-prolog:382: undefined reference to `bpf_program__attach_netns'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_C2func_bpf_program__attach_perf_event':
/tmp/go-build/cgo-gcc-prolog:406: undefined reference to `bpf_program__attach_perf_event'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_C2func_bpf_program__attach_raw_tracepoint':
/tmp/go-build/cgo-gcc-prolog:429: undefined reference to `bpf_program__attach_raw_tracepoint'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_C2func_bpf_program__attach_tracepoint':
/tmp/go-build/cgo-gcc-prolog:453: undefined reference to `bpf_program__attach_tracepoint'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_C2func_bpf_program__attach_uprobe':
/tmp/go-build/cgo-gcc-prolog:480: undefined reference to `bpf_program__attach_uprobe'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_C2func_bpf_program__attach_xdp':
/tmp/go-build/cgo-gcc-prolog:504: undefined reference to `bpf_program__attach_xdp'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_Cfunc_bpf_link__destroy':
/tmp/go-build/cgo-gcc-prolog:551: undefined reference to `bpf_link__destroy'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_Cfunc_bpf_link(float, double)':
/tmp/go-build/cgo-gcc-prolog:570: undefined reference to `bpf_link(float, double)'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_Cfunc_bpf_link__pin':
/tmp/go-build/cgo-gcc-prolog:590: undefined reference to `bpf_link__pin'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_Cfunc_bpf_link__unpin':
/tmp/go-build/cgo-gcc-prolog:609: undefined reference to `bpf_link__unpin'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_Cfunc_bpf_map(float, double)':
/tmp/go-build/cgo-gcc-prolog:628: undefined reference to `bpf_map(float, double)'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_Cfunc_bpf_map__is_pinned':
/tmp/go-build/cgo-gcc-prolog:647: undefined reference to `bpf_map__is_pinned'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_Cfunc_bpf_map__key_size':
/tmp/go-build/cgo-gcc-prolog:666: undefined reference to `bpf_map__key_size'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_Cfunc_bpf_map__lookup_elem':
/tmp/go-build/cgo-gcc-prolog:690: undefined reference to `bpf_map__lookup_elem'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_Cfunc_bpf_map__max_entries':
/tmp/go-build/cgo-gcc-prolog:709: undefined reference to `bpf_map__max_entries'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_Cfunc_bpf_map__name':
/tmp/go-build/cgo-gcc-prolog:727: undefined reference to `bpf_map__name'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_Cfunc_bpf_map__pin':
/tmp/go-build/cgo-gcc-prolog:747: undefined reference to `bpf_map__pin'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_Cfunc_bpf_map__pin_path':
/tmp/go-build/cgo-gcc-prolog:765: undefined reference to `bpf_map__pin_path'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_Cfunc_bpf_map__set_max_entries':
/tmp/go-build/cgo-gcc-prolog:786: undefined reference to `bpf_map__set_max_entries'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_Cfunc_bpf_map__set_pin_path':
/tmp/go-build/cgo-gcc-prolog:806: undefined reference to `bpf_map__set_pin_path'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_Cfunc_bpf_map__set_type':
/tmp/go-build/cgo-gcc-prolog:827: undefined reference to `bpf_map__set_type'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_Cfunc_bpf_map__set_value_size':
/tmp/go-build/cgo-gcc-prolog:848: undefined reference to `bpf_map__set_value_size'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_Cfunc_bpf_map__type':
/tmp/go-build/cgo-gcc-prolog:867: undefined reference to `bpf_map__type'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_Cfunc_bpf_map__unpin':
/tmp/go-build/cgo-gcc-prolog:887: undefined reference to `bpf_map__unpin'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_Cfunc_bpf_map__value_size':
/tmp/go-build/cgo-gcc-prolog:906: undefined reference to `bpf_map__value_size'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_Cfunc_bpf_map_create':
/tmp/go-build/cgo-gcc-prolog:932: undefined reference to `bpf_map_create'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_Cfunc_bpf_map_delete_batch':
/tmp/go-build/cgo-gcc-prolog:955: undefined reference to `bpf_map_delete_batch'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_Cfunc_bpf_map_delete_elem':
/tmp/go-build/cgo-gcc-prolog:976: undefined reference to `bpf_map_delete_elem'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_Cfunc_bpf_map_get_next_key':
/tmp/go-build/cgo-gcc-prolog:998: undefined reference to `bpf_map_get_next_key'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_Cfunc_bpf_map_lookup_and_delete_batch':
/tmp/go-build/cgo-gcc-prolog:1024: undefined reference to `bpf_map_lookup_and_delete_batch'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_Cfunc_bpf_map_lookup_batch':
/tmp/go-build/cgo-gcc-prolog:1050: undefined reference to `bpf_map_lookup_batch'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_Cfunc_bpf_map_lookup_elem':
/tmp/go-build/cgo-gcc-prolog:1072: undefined reference to `bpf_map_lookup_elem'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_Cfunc_bpf_map_lookup_elem_flags':
/tmp/go-build/cgo-gcc-prolog:1095: undefined reference to `bpf_map_lookup_elem_flags'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_Cfunc_bpf_map_update_batch':
/tmp/go-build/cgo-gcc-prolog:1119: undefined reference to `bpf_map_update_batch'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_Cfunc_bpf_map_update_elem':
/tmp/go-build/cgo-gcc-prolog:1142: undefined reference to `bpf_map_update_elem'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_Cfunc_bpf_object__find_map_by_name':
/tmp/go-build/cgo-gcc-prolog:1173: undefined reference to `bpf_object__find_map_by_name'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_Cfunc_bpf_object__find_program_by_name':
/tmp/go-build/cgo-gcc-prolog:1192: undefined reference to `bpf_object__find_program_by_name'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_Cfunc_bpf_object__load':
/tmp/go-build/cgo-gcc-prolog:1211: undefined reference to `bpf_object__load'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_Cfunc_bpf_object__next_map':
/tmp/go-build/cgo-gcc-prolog:1230: undefined reference to `bpf_object__next_map'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_Cfunc_bpf_object__next_program':
/tmp/go-build/cgo-gcc-prolog:1249: undefined reference to `bpf_object__next_program'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_Cfunc_bpf_object__open_file':
/tmp/go-build/cgo-gcc-prolog:1268: undefined reference to `bpf_object__open_file'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_Cfunc_bpf_program__attach':
/tmp/go-build/cgo-gcc-prolog:1330: undefined reference to `bpf_program__attach'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_Cfunc_bpf_program__attach_cgroup':
/tmp/go-build/cgo-gcc-prolog:1350: undefined reference to `bpf_program__attach_cgroup'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_Cfunc_bpf_program__attach_kprobe':
/tmp/go-build/cgo-gcc-prolog:1371: undefined reference to `bpf_program__attach_kprobe'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_Cfunc_bpf_program__attach_lsm':
/tmp/go-build/cgo-gcc-prolog:1389: undefined reference to `bpf_program__attach_lsm'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_Cfunc_bpf_program__attach_netns':
/tmp/go-build/cgo-gcc-prolog:1409: undefined reference to `bpf_program__attach_netns'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_Cfunc_bpf_program__attach_perf_event':
/tmp/go-build/cgo-gcc-prolog:1429: undefined reference to `bpf_program__attach_perf_event'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_Cfunc_bpf_program__attach_raw_tracepoint':
/tmp/go-build/cgo-gcc-prolog:1448: undefined reference to `bpf_program__attach_raw_tracepoint'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_Cfunc_bpf_program__attach_tracepoint':
/tmp/go-build/cgo-gcc-prolog:1468: undefined reference to `bpf_program__attach_tracepoint'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_Cfunc_bpf_program__attach_uprobe':
/tmp/go-build/cgo-gcc-prolog:1491: undefined reference to `bpf_program__attach_uprobe'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_Cfunc_bpf_program__attach_xdp':
/tmp/go-build/cgo-gcc-prolog:1511: undefined reference to `bpf_program__attach_xdp'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_Cfunc_bpf_program(float, double)':
/tmp/go-build/cgo-gcc-prolog:1530: undefined reference to `bpf_program(float, double)'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_Cfunc_bpf_program__name':
/tmp/go-build/cgo-gcc-prolog:1548: undefined reference to `bpf_program__name'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_Cfunc_bpf_program__pin':
/tmp/go-build/cgo-gcc-prolog:1568: undefined reference to `bpf_program__pin'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_Cfunc_bpf_program__section_name':
/tmp/go-build/cgo-gcc-prolog:1586: undefined reference to `bpf_program__section_name'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_Cfunc_bpf_program__set_attach_target':
/tmp/go-build/cgo-gcc-prolog:1608: undefined reference to `bpf_program__set_attach_target'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_Cfunc_bpf_program__set_autoload':
/tmp/go-build/cgo-gcc-prolog:1629: undefined reference to `bpf_program__set_autoload'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_Cfunc_bpf_program__set_expected_attach_type':
/tmp/go-build/cgo-gcc-prolog:1650: undefined reference to `bpf_program__set_expected_attach_type'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_Cfunc_bpf_program__set_type':
/tmp/go-build/cgo-gcc-prolog:1671: undefined reference to `bpf_program__set_type'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_Cfunc_bpf_program__type':
/tmp/go-build/cgo-gcc-prolog:1690: undefined reference to `bpf_program__type'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_Cfunc_bpf_program__unpin':
/tmp/go-build/cgo-gcc-prolog:1710: undefined reference to `bpf_program__unpin'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_Cfunc_bpf_tc_attach':
/tmp/go-build/cgo-gcc-prolog:1730: undefined reference to `bpf_tc_attach'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_Cfunc_bpf_tc_detach':
/tmp/go-build/cgo-gcc-prolog:1750: undefined reference to `bpf_tc_detach'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_Cfunc_bpf_tc_hook_create':
/tmp/go-build/cgo-gcc-prolog:1769: undefined reference to `bpf_tc_hook_create'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_Cfunc_bpf_tc_hook_destroy':
/tmp/go-build/cgo-gcc-prolog:1788: undefined reference to `bpf_tc_hook_destroy'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_Cfunc_bpf_tc_query':
/tmp/go-build/cgo-gcc-prolog:1808: undefined reference to `bpf_tc_query'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_Cfunc_libbpf_probe_bpf_map_type':
/tmp/go-build/cgo-gcc-prolog:1881: undefined reference to `libbpf_probe_bpf_map_type'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_Cfunc_libbpf_probe_bpf_prog_type':
/tmp/go-build/cgo-gcc-prolog:1902: undefined reference to `libbpf_probe_bpf_prog_type'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_Cfunc_libbpf_set_strict_mode':
/tmp/go-build/cgo-gcc-prolog:1922: undefined reference to `libbpf_set_strict_mode'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_Cfunc_perf_buffer__poll':
/tmp/go-build/cgo-gcc-prolog:1977: undefined reference to `perf_buffer__poll'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_Cfunc_ring_buffer__poll':
/tmp/go-build/cgo-gcc-prolog:2010: undefined reference to `ring_buffer__poll'
/usr/bin/ld: $WORK/b001/_x003.o: in function `set_print_fn':
../../../../go/pkg/mod/github.com/aquasecurity/libbpfgo@v0.4.0-libbpf-<IP_ADDRESS>.20220921161443-245a1a13132e/libbpfgo.go:67: undefined reference to `libbpf_set_print'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_Cfunc_bpf_object__close':
/tmp/go-build/cgo-gcc-prolog:1157: undefined reference to `bpf_object__close'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_Cfunc_perf_buffer(float, long double,...)(...)':
/tmp/go-build/cgo-gcc-prolog:1959: undefined reference to `perf_buffer(float, long double,...)(...)'
/usr/bin/ld: $WORK/b001/_x003.o: in function `_cgo_0b4893bce39f_Cfunc_ring_buffer(float, long double,...)(...)':
/tmp/go-build/cgo-gcc-prolog:1992: undefined reference to `ring_buffer(float, long double,...)(...)'
collect2: error: ld returned 1 exit status

Hi @Songrui625. I would recommend to follow the make rules from the main libbpfgo Makefile.
If you want to run go get directly you should set the CGO env vars like this: https://github.com/aquasecurity/libbpfgo/blob/245a1a13132ec0afc4a1d0f53b9317464980bcb6/Makefile#L58

Thanks @geyslan. I try to make libbpfgo as a submodule of my go project now. And seems like we must use Makefile to build projects.

Closing this. @Songrui625 anything, please let us know.


Add StreamMessage.timeout()

Motivation:
Currently, the aggregate() and subscribe() methods of StreamMessage do not have the ability to set a timeout. This provides the ability to detect when a client or server has not responded for a period of time and handle it appropriately. Additionally, the timeout API can be used to detect idle streams by setting a timeout until the next message.
Modifications:

Added the TimeoutStreamMessage class

Wrap a StreamMessage to provide timeout functionality
You can set a timeout feature by adding the timeout() method to the StreamMessage interface.

Added the TimeoutSubscriber class

Schedule a timeout for each message.
StreamTimeoutMode allows you to set different timeout modes.

Added StreamTimeoutMode enumeration

Defines the UNTIL_FIRST, UNTIL_NEXT, and UNTIL_EOS modes.

Added a timeout method

Added the timeout method to the StreamMessage, HttpResponse, and HttpRequest interfaces to provide the ability to set a timeout.

Result:

Closes #5744
This change adds timeout functionality to the aggregate() and subscribe() methods of StreamMessage and HTTP requests/responses.
This allows idle streams to be detected and handled appropriately.
You can use StreamTimeoutMode to set the timeout between the arrival of the first message, the arrival of the next message, or the end of the stream.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.jeong-yong-shin seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Some of the descriptions in the Modifications field contain Korean.

Added StreamTimeoutMode enumeration
UNTIL_FIRST, UNTIL_NEXT, UNTIL_EOS 모드를 정의합니다.

p.s. It's an interesting feature, so I'm watching with interest

Some of the descriptions in the Modifications field contain Korean.

Added StreamTimeoutMode enumeration
UNTIL_FIRST, UNTIL_NEXT, UNTIL_EOS 모드를 정의합니다.

p.s. It's an interesting feature, so I'm watching with interest

Thank you for your interest.

Last but not least, please sign the ICLA.

Last but not least, please sign the ICLA.

I checked, thank you for your review.


app - style improvements

Basic style improvements to make the web map a bit more functional:

generalized stream layer as per #218 (visible on page open)
show PSCIS barriers on modelled habitat (or some other priority indicator) at lower zoom levels (as above, so something is shown on page open)
add observations and barriers, symbolizing barriers by length of stream upstream, as per WCRP page
add species specific styles and a button to switch between them
try symbolizing based on the spawning/rearing potential modelling
tidy crossing info popup

Adding observations and natural barriers may make a layer toggle desirable.
Hopefully some smart scale dependency choices can make this unnecessary.


Check the Documentation

Under Usage,
You can use it in your Projects (you made it prpjects)

Thanks. Will Fix


Write Documentation

Project needs documentation and explanation of intended usage of contracts implemented.

Is there any process on this issue? I am trying to figure out how to verify a BGLS aggregate signature using BGLS.sol, but to me it seems like the current version is not able to do it yet as there is no way to compute the product of pairings. In the Go counterpart we have a method PairingProduct that does this. Am I seeing this correctly?


Could not load file or assembly 'Microsoft.Graph.Communications.Calls.Media'

When adding Microsoft.Graph.Communications.Calls.Media through nuget to a asp.net web API, on run I'm seeing:
Could not load file or assembly 'Microsoft.Graph.Communications.Calls.Media' or one of its dependencies. An attempt was made to load a program with an incorrect format.

Version <IP_ADDRESS>6

I've got used to .net core and kestrel - forgetting that IIS express runs by default in 32 bit, even if debug in VS is set to x86. Options, Projects, Web, Use x64 IIS Express.


Log messages on robot connection and disconnection

When using the ROS2 driver with external-control URCap I would expect that the ROS2 driver terminal should output log messages once the robot is connected to the driver, currently this is not the case. Currently when the robot connects to the driver no log message is printed, meaning that it is actually not possible to see in the driver terminal that the robot has connected to the driver. If the robot disconnects it also not possible to see that the robot has disconnected in the terminal.
I would expect an output similar to below terminal output, this is the terminal output from the ROS driver, when the robot connects to the ROS driver.
[ INFO] [1620633422.400343214]: Robot requested program
[ INFO] [1620633422.400784839]: Sent program to robot
[ INFO] [1620633422.418806644]: Robot connected to reverse interface. Ready to receive control commands.

I think this is related to that only error and warning messages are currently printed from the client library in the ROS2 driver. Because I can see error and warning messages from the client library in the ROS2 drivers terminal output, but not any log messages above warning level.

Ok this is rather weird. According to the launch files  the input of the client library should be forwarded to the screen. When adding std::out to the client library code the get printed as well but somehow it seems the UR logging is not captured correctly

I think it is related to that currently the client library uses console bridge when logging messages, if console bridge is found in the system when building. See description in the client library. As default log level is set to warning in the console bridge.
A quick fix could be to change the log level to INFO, when using console bridge.
console_bridge::setLogLevel(console_bridge::CONSOLE_BRIDGE_LOG_INFO);

I think that the best solution is to use the loghandler interface to create a log handler to translate the log messages from the client library into ROS2 log messages. I will be happy to look into this, as I will most likely be implementing something similar in the ROS driver, when I have the time.

Closed in #126


Add year introduced and year stopped being supported fields

I'm eager to contribute to this repository; I believe it's an excellent project idea for newcomers! 😁 Regarding this issue, could you provide more details on how to incorporate the 'year introduced' and 'year stopped being supported' fields into the data.json?

I'm eager to contribute to this repository; I believe it's an excellent project idea for newcomers! 😁 Regarding this issue, could you provide more details on how to incorporate the 'year introduced' and 'year stopped being supported' fields into the data.json?

This would involve adding two optional fields in each item in data.json, year_created, and year_deprecated.
The value of the fields would be number, such as 2018, 2023.
The first PR should come with updates to the scripts to display this information. For example:

jQuery - Library (1999 - now)
BEM - CSS Methodologies (2008 - 2020)

(Above is just an example of format, not real data, you need to include sources for the data)

closed via #4


Strange behavior with auth transform

Example below:
type Redemption
  @model (subscriptions: { level: public })
  @auth(rules: [
    {allow: groups, groups: ["Admins"], operations: [update, create]},
    {allow: private, provider: iam, operations: [update, create]},
    {allow: owner, ownerField: "redemptionUserId", operations: [update, create]},
  ])
{
  id: ID!
  createdAt: String
  updatedAt: String

  redemptionUserId: ID!
  redemptionPromotionId: ID!
  redemptionCampaignId: ID!

  promotion: Promotion @connection
}

type User
  @model (subscriptions: { level: public })
  @auth(rules: [
    {allow: owner, ownerField: "id", operations: [update, create]},
    {allow: groups, groups: ["Admins"], operations: [update, create]},
    {allow: private, provider: iam, operations: [update, create]},
  ])
{
  id: ID!
  legacyId: String
  displayName: String
  createdAt: String
  updatedAt: String
  agreedToTermsAt: String
  notifyViaEmailOnAll: Boolean
  notifyViaPushOnAll: Boolean
  notifyViaEmailOnLongshot: Boolean
  notifyViaPushOnLongshot: Boolean
  notifyViaEmailOnTeam: Boolean
  notifyViaPushOnTeam: Boolean
  notifyViaEmailOnSport: Boolean
  notifyViaPushOnSport: Boolean
  agreedToCcTermsAt: String

  userSportId: ID
  userTeamId: ID

  sport: Sport @connection(name: "SportUsers", sortField: "createdAt")
  team: Team @connection(name: "TeamUsers", sortField: "createdAt")
}

Then if we run the generated queries in AppSync console:
Redemptions (Unauthorized)
Users (Works just fine)
Default auth is user pools. Secondary is IAM

Hello @CodySwannGT Are you still running into this issue?
I see that you are trying the redemptions query using iam auth, though in your schema those with iam are not granted auth access on read (get/list).

So I’m not sure. Unfortunately, we don’t have the luxury of waiting on fixes so we went another direction.
As to your question, though, I’m 99% sure the docs say if you don’t specify who has read access then all have read access.
The docs were very confusing on this point though so I could be wrong.

Yes though when using iam auth it grants access if it's specified.
In this case {allow: private, provider: iam, operations: [update, create]}, creates policies for the authorized role to allow update and create mutations.
https://aws-amplify.github.io/docs/cli-toolchain/graphql#combining-authorization-rules

@CodySwannGT Closing this issue. Please let me know if you have more questions around this.


Add SMS delivery of envelope

other changes:

Format validation errors as JSON
Shorten the envelope custom field suffix to accommodate longer custom field names

When submitting a connector, please make sure that you follow the requirements below, otherwise your PR might be rejected. We want to make you have a well-built connector, a smooth certification experience, and your users are happy :)
If this is your first time submitting to GitHub and you need some help, please sign up for this session.

[x ] I attest that the connector doesn't exist on the Power Platform today. I've verified by checking the pull requests in GitHub and by searching for the connector on the platform or in the documentation.
[x ] I attest that the connector works and I verified by deploying and testing all the operations.
[x ] I attest that I have added detailed descriptions for all operations and parameters in the swagger file.
[ x] I attest that I have added response schemas to my actions, unless the response schema is dynamic.
[ x] I validated the swagger file, apiDefinition.swagger.json, by running paconn validate command.
[x ] If this is a certified connector, I confirm that apiProperties.json has a valid brand color and doesn't use an invalid brand color, #007ee5 or #ffffff. If this is an independent publisher connector, I confirm that I am not submitting a connector icon.

If you are an Independent Publisher, you must also attest to the following to ensure a smooth publishing process:

[ ] I have named this PR after the pattern of "Connector Name (Independent Publisher)" ex: HubSpot Marketing (Independent Publisher)
[ ] Within this PR markdown file, I have pasted screenshots that show: 3 unique operations (actions/triggers) working within a Flow. This can be in one flow or part of multiple flows. For each one of those flows, I have pasted in screenshots of the Flow succeeding.
[ ] Within this PR markdown file, I have pasted in a screenshot from the Test operations section within the Custom Connector UI.
[ ] If the connector uses OAuth, I have provided detailed steps on how to create an app in the readme.md.

Hello @sriharip-docusign,
Congratulations, your Pull Request is approved and merged. Please update your submission in ISV Studio by using the latest commit ID.
Let us know if you have any questions.