Azure Resource Group creation through Ansible playbook - 403 Client Error: Forbidden for url

I was trying to create a resource group for VM creation through ansible playbook automation by referring to the below link
https://docs.microsoft.com/en-us/azure/virtual-machines/linux/ansible-install-configure#file-credentials
All the steps mentioned were followed but was getting the below error during execution. Even in the module code, error is handled for 204 and 404 but no details on 403.
''msg': 'Error checking for existence of name ansible-rg - 403 Client Error: Forbidden for url: https://management.azure.com/subscriptions/<subscription id>/resourcegroups/ansible-rg?api-version=2017-05-10''
When I checked Microsoft support on the above error, got the below resolution.

Login to Azure portal.
Select your Subscription.
Go to access management and provide owner access to the application.
After giving Owner access to the subscription, the issue was resolved.
This feedback is raised to notify that neither this step is mentioned in the link mentioned nor the resolution for the error code 403 is provided in the Trouble shooting section. So please update the documentation for Resource group creation section and Trouble shooting error codes section with these steps for self help through docs.

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

ID: 38838df3-4e07-1722-d828-e38e00fc296e
Version Independent ID: 80efdd1d-4756-c10d-681f-892a83330f69
Content: Install Ansible on Azure virtual machines
Content Source: articles/virtual-machines/linux/ansible-install-configure.md
Service: ansible
GitHub Login: @TomArcher
Microsoft Alias: tarcher

@hemalatha-pal Thanks for bringing this to our attention. Your feedback has been shared with the content owner for further review.

Thank you for feedback. We will work with Tom on a TSG.

@hemalatha-pal Thanks again for your input. I am working with the feature team on documenting this.
@femsulu #please-close

I am sorry but following the steps still also get 403. changing the SP from contrib (default) to owner doesn't help.

I think Contributor rights it's more than enough for this actions.
Why should we give Owner access to a Service Principal?
https://docs.microsoft.com/en-us/azure/role-based-access-control/built-in-roles#contributor
"Create and manage resources of all types"

I am facing the issue while creating new virtual machine in azure.    msg :Error creating network interface - 403 Client Error: Forbidden for url: https://management.azure.com/.
Any idea ? Thanks

Hello,
Same problem, by following the documentation.
I have a contributor role, I cannot create a resource group with ansible (Error checking for existence of name ... - 403), but I can by azure portal UI ^^
By the way, I cannot delete a resource group by azure portal, ansible delete ends with success but the resources is not deleted, and I can delete with azure cli... I'm completely lost.
Could you help me ?

I know this thread is closed, but I faced the same issue. Here is how I solved it.
Once you have created your service principle, it will not have Contributor role assigned to it, you need to do it yourself:

in search box type subscriptions
once on subscriptions page click on your subscription
click on access control (IAM)
click on Add -> Add Role Assignment
choose Contributor then Next
choose User, group, or service principal then below Select members
Here it gets tricky... your service principal will show by default, you need to type into search box
once it's shown click on it, then click Select button
Finally review + assign

Now you should no longer get 403 when using ansible with azure.
@TomArcherMsft - please update the documentation. Thanks.


Adding object pool identified by ConnectionKey

The goal for this Pr is to have the possibilty to have a pool wich objects are identified by a key, so we would be able to reuse those kind of objects without having to re connect every time.

ping me when you make the updates we talked about

Name updates to have more abstact significant

I'll review this before Friday

Cool, ping me if you have any doubts


[proposal] Drop runtime validations in production mode

This could reduce nicely the production bytes cost of polished because those error message are not that easily compressed.
There are 2 ways of approaching this:

remove validation altogether in production mode
remove only error messages in production mode

Intent to implement
yes 😉

@Andarist Thanks for raising thing. I definitely have this high on my todo list. I would love to:
a) drastically improve validation and error messaging across the library.
b) remove error messages and replace them with a link to an online version (similar to what React and styled-components implemented).
I'm 100% in support of a PR around this. I'm shooting to ship v2 this week, so I would suggest branching off the version-2 branch if you do implement something.


fix bug, add the cache logic in getInstancedetail

What is the purpose of the pull request
Fix  the bug in #1795, add a instance cache.
Brief change log

Edit actions.js
Edit formModel.vue

Verify this pull request
This change added tests and can be verified as follows:

Manually verified the change by testing locally.

+1

Codecov Report

Merging #1814 into dev will decrease coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             dev    #1814      +/-   ##
=========================================
- Coverage   21.4%   21.39%   -0.01%
=========================================
  Files        293      293
  Lines      14051    14051
  Branches    2316     2316
=========================================
- Hits        3007     3006       -1
- Misses     10717    10718       +1
  Partials     327      327

Impacted Files
Coverage Δ

...scheduler/alert/template/AlertTemplateFactory.java
42.85% <0%> (-14.29%)
:arrow_down:

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 289ae6a...b938f48. Read the comment docs.


Want to Learn graphs use those cheat sheets!!

Hacktoberfest! 🎊🎈
🎉 Have you read the Contributing Guidelines? 🤔
(Yes.)
📝 Description
As i was assigned the contribution to make learning graphs data structure easy i have tried it by creating "CheatSheet" . So, this is my PR or MR under #hacktoberfest 2024.
PLEASE ACCEPT MY PR.
Mayur-Nimkande-20
Fixes #issue_no 🔧

✅ Checklist

[ ] I've read the contribution guidelines. 📚
[ ] I've checked the issue list before deciding what to submit. 🔍
[ ] I've edited the README.md and linked to my code. 📄

🔗 Related Issues or Pull Requests
(Write your answer here.)

Hi there!
I am the Mentor of this project .
Although this repo is not part of Hacktoberfest 2024, we have some great alternatives for you. Welcome to SkillShow, a repository focused on skill enhancement!
Guidelines:
Please adhere to the existing guidelines.
No additional rules, thanks!
Check it out here: SkillShow.
Note: Start by creating an issue. Once it’s assigned to you, feel free to open a pull request (PR). Directly opening a PR will lead to an invalid label.
Looking forward to your contributions!


Add protobuf-c package

I've followed this guide
step by step carefully. Yes

I've tested this package remotely and have excluded all broken builds.
Here is the links to the Travis/AppVeyor with status "All passed":

https://ci.appveyor.com/project/isaachier/hunter/build/1.0.405
https://travis-ci.org/isaachier/hunter/builds/354356155

I have submitted CI configs to https://github.com/ingenue/hunter targeting pkg.template branch,
see this merged pull request https://github.com/ingenue/hunter/pull/211

Testing:

https://ci.appveyor.com/project/ingenue/hunter/build/1.0.3474
https://travis-ci.org/ingenue/hunter/builds/354381894?utm_source=github_status&utm_medium=notification

Uploading:

https://ci.appveyor.com/project/ingenue/hunter/build/1.0.3475
https://travis-ci.org/ingenue/hunter/builds/354406654?utm_source=github_status&utm_medium=notification

Released: https://github.com/ruslo/hunter/releases/tag/v0.20.22


Update README URLs based on HTTP redirects

Created with https://github.com/dkhamsing/frankenstein
GitHub Corrected URLs

Was
Now

https://github.com/sstephenson/rbenv
https://github.com/rbenv/rbenv

https://github.com/sstephenson/rbenv-vars
https://github.com/rbenv/rbenv-vars

https://github.com/sstephenson/rbenv/issues
https://github.com/rbenv/rbenv/issues

https://github.com/sstephenson/rbenv/wiki/Authoring-plugins#rbenv-hooks
https://github.com/rbenv/rbenv/wiki/Authoring-plugins#rbenv-hooks

https://github.com/sstephenson/rbenv/wiki/Plugins
https://github.com/rbenv/rbenv/wiki/Plugins

https://github.com/sstephenson/rbenv/wiki/Understanding-binstubs
https://github.com/rbenv/rbenv/wiki/Understanding-binstubs

https://github.com/sstephenson/rbenv/wiki/Why-rbenv%3F
https://github.com/rbenv/rbenv/wiki/Why-rbenv%3F

https://github.com/sstephenson/ruby-build#readme
https://github.com/rbenv/ruby-build#readme

I was meaning to do this myself as part of the org transition, but thanks, robot! :+1:

:smile:


minor fix in the documentation

fixes this small documentation issue

Thanks; merged as 127e6201e with minor polishing.


MAKE SURE THERE'S NO OVERFLOW IN C2D_TICK FUNCTION

In src/unknown_cuda.cu make sure there's no overflow in three (marked with a comment) instances of c2d_tick function.

The file src/unknown_cuda.cu contains three instances of the c2d_tick function with comments indicating where to check for overflow. Here are the relevant parts:

First instance: random < prev_cortex->syngen_chance * (bhm_chance_t)neighbor.pulse
Second instance: random < prev_cortex->synstr_chance * (bhm_chance_t)neighbor.pulse * (bhm_chance_t)strength_diff
Third instance: random < prev_cortex->synstr_chance / (neighbor.pulse + syn_strength + 1)

To ensure there are no overflows in these instances, we'll need to:

Validate the values being used in the expressions to ensure they are within safe bounds.
Consider using safer arithmetic operations or checks to prevent overflow.

To ensure there is no overflow in the three marked instances in the c2d_tick function, we can add checks and use safer arithmetic operations.
First instance:
// Add check to prevent overflow
if (prev_cortex->syngen_chance <= UINT_MAX / (bhm_chance_t)neighbor.pulse) {
    if (random < prev_cortex->syngen_chance * (bhm_chance_t)neighbor.pulse) {
        // Original logic
    }
}

Second instance:
// Add check to prevent overflow
if (prev_cortex->synstr_chance <= UINT_MAX / ((bhm_chance_t)neighbor.pulse * (bhm_chance_t)strength_diff)) {
    if (random < prev_cortex->synstr_chance * (bhm_chance_t)neighbor.pulse * (bhm_chance_t)strength_diff) {
        // Original logic
    }
}

Third instance:
// Add check to prevent overflow
if (neighbor.pulse + syn_strength + 1 > 0 && prev_cortex->synstr_chance <= UINT_MAX / (neighbor.pulse + syn_strength + 1)) {
    if (random < prev_cortex->synstr_chance / (neighbor.pulse + syn_strength + 1)) {
        // Original logic
    }
}


Explore default BSON serialization

There's the possibility that we can just serialize known BSON values in the emitted JSON, as the MongoDB Extended Spec shows, we're kind of doing half work for ObjectIds so instead of just emitting the "objectid" we could be emitting { $oid: "objectid" } in the same way we could be doing the same for int64, dates, etc
Ideally I'd like to use the canonical form when possible, but if there's not an option using the relaxed form should be enough

[x] Date
[x] Decimal128
[x] Double
[x] Int32
[x] Int64
[x] ObjectId
[x] Regular Expression
[ ] Binary
[ ] MinKey
[ ] MaxKey
[ ] Array
[ ] Timestamp

made some explorations with this and I have the following preview converters
    type ObjectIdConverter() =
        inherit JsonConverter<ObjectId>()

        override _.Read(reader: byref<Utf8JsonReader>, typeToConvert: Type, options: JsonSerializerOptions) =
            ObjectId.Parse(reader.GetString())

        override _.Write(writer: Utf8JsonWriter, value: ObjectId, options: JsonSerializerOptions) =
            writer.WriteStartObject()
            writer.WritePropertyName("$oid")
            writer.WriteStringValue(value.ToString())
            writer.WriteEndObject()

    type DateTimeConverter() =
        inherit JsonConverter<DateTime>()

        override _.Read(reader: byref<Utf8JsonReader>, typeToConvert: Type, options: JsonSerializerOptions) =
            let deserialized =
                JsonSerializer.Deserialize<{| ``$date``: {| ``$numberLong``: string |} |}>(reader.GetString())

            DateTimeOffset
                .FromUnixTimeMilliseconds(deserialized.``$date``.``$numberLong`` |> int64)
                .Date

        override _.Write(writer: Utf8JsonWriter, value: DateTime, options: JsonSerializerOptions) =
            let stringValue =
                DateTimeOffset
                    .op_Implicit(value)
                    .ToUnixTimeMilliseconds()
                |> string

            writer.WriteStartObject()
            writer.WritePropertyName("$date")
            writer.WriteStartObject()
            writer.WritePropertyName("$numberLong")
            writer.WriteStringValue(stringValue)
            writer.WriteEndObject()
            writer.WriteEndObject()

they are producing the following json
{
    "insert":"users",
    "documents":[
        {
            "_id":{
                "$oid":"5fc5b6e4545a4775f7f9bfda"
            },
            "age":29,
            "name":"Peter"
        },
        {
            "_id":{
                "$oid":"5fc5b6e4545a4775f7f9bfdb"
            },
            "age":20,
            "name":"Sandra"
        },
        {
            "age":35,
            "name":"Mike"
        },
        {
            "age":39,
            "name":"Perla"
        },
        {
            "age":1,
            "name":"Updateme"
        },
        {
            "age":50,
            "name":"Deleteme"
        }
    ]
}

{
    "update":"users",
    "updates":[
        {
            "q":{
                "name":"Updateme"
            },
            "u":{
                "age":5,
                "name":"Updated",
                "updatedAt":{
                    "$date":{
                        "$numberLong":"1606792932488"
                    }
                }
            },
            "upsert":false,
            "multi":false
        }
    ]
}

NoSQL booster reads the values and shows them as their intended serialized values

it also allows things like these
find "users" {
        // equivalent to a mongo query filter
        // { age: { $gt: 10} }
        filter {| updatedAt = {| ``$ne`` = DateTime.Now |} |}
    }

{
    "find":"users",
    "filter":{
        "updatedAt":{
            "$ne":{
                "$date":{
                    "$numberLong":"1606793830175"
                }
            }
        }
    }
}

and seem to work fine

of course there might be some caveats to how to do a propper search but that's out of the scope of this project

I'm not sure how worth or what are the correct data types in .NET for those so I'll leave them pending, If anyone ever wants them, they are very easy to implement


Export pressScale and focusRing utilities from S2

A lot of import changes but this is just exporting pressScale (from @react-spectrum/s2 since it is used at runtime) and focusRing from (@react-spectrum/s2/style since it is a macro). We could export additional style macro utils from here in the future.

What about centerbaseline()? If logic button had an icon it would need that.

hmm I'm not sure LogicButton supports icons. We can consider exporting <CenterBaseline> in the future potentially.

What about centerbaseline()? If logic button had an icon it would need that.

No icons in logic button that we know of.

hmm I'm not sure LogicButton supports icons. We can consider exporting <CenterBaseline> in the future potentially.

Sorry for the confusion, I meant to say it doesn't support icons, but another component might have both icon and text and we'd need <CenterBaseline /> for it.


Make configuration values from all built-in parameters

All built-in parameters (like params.validationLenientMode) should be turned into configuration values instead (as these parameters are used to configure how the plugin works)
So for example:
params.validationLenientMode = true|false should become validation.lenientMode = true|false instead.
Link to slack thread for traceability: https://nfcore.slack.com/archives/C056RQB10LU/p1713279781474429

Added in #5


List of theme IDs in theme preview on website

Hey!
Gogh and its website are fantastic!
But it's cumbersome to first look at the themes on the website, then find the name in the list of themes in the terminal, identify the theme ID and then enter it.
It would greatly enhance the user experience to simply have the ID listed in the title bar of the theme sample images (see red box in the image):

The problem with this is that every time someone contributes with a theme, it is necessary to re-generate the theme list in json.
Since the ids are consecutive and change every time there is a new theme.
At this moment I can't think of anything to solve it, so for now I'm going to pass this issue to discussions.
Thank you
https://gist.github.com/rapgru/09b449285231d18f4e4536c5f48fc927


Fix some indentation errors on the "If your CI checks fail..." page.

Fix a few indentation errors on the "If your CI checks fail..." page, as well as a broken wiki redirect link.

@HardikGoyal2003 PTAL. Thanks!

Thanks @HardikGoyal2003, I think you're right! I fixed it, PTAL, thanks.

@seanlip LGTM, Thanks!


The report is not appearing properly as defined/displayed in the screenshot

Hi Team,
I followed your setup procedure and i am able to generate the report. When i am opening the index.html file in all the browsers i am unable to see the report properly.For me The Pass/Fail column is not appearing in the report, its appearing as empty. Also total count of failed/passed is not appearing in the top right. Please see the screenshots attached both actual and expected. Please see the red highlighted part marked in the screenshot.
Note: I am using your latest version 0.16, all browsers latest version
Please let me what could be the issue. I tried my label best but hard luck. Please help me in this regard as i need the report urgently.

Did anybody get a chance to look into the above issue?

Nobody replied to the question hence closing

I found the solution and its working fine for me. Just FYI


What about ARM Architecture?

Hi, a short question, are there any plans for an ARM targeted Docker Image? Are there currently any thoughts about the components, that could cause problem once running on ARM CPUs?
Thanks for the interesting project and your answer in advance!
Regards,
Misha

Hi @strangerAsking !
As for now we have no plans to port Ambar to ARM arch.


When using #[wasm_bindgen(readonly)], The type output to .d.ts file is void

Hello.
Thank you for this great library!
Describe the Bug
When #[wasm_bindgen(readonly)] is specified, the return value in d.ts file is void.
#[wasm_bindgen]
pub struct Foo {
    pub first: u32,

    #[wasm_bindgen(readonly)]
    pub second: u32,
}

output
export class Foo {
  free(): void;
/**
*/
  first: number;
/**
*/
  readonly second: void;
}

Expected Behavior
export class Foo {
  free(): void;
/**
*/
  first: number;
/**
*/
  readonly second: number;
}

Steps to Reproduce
https://github.com/MadonoHaru/wasm-bindgen-type-issue

This occurs for me too:
Versions:
Rust: 1.58.0
wasm-bindgen: "0.2.63"
Current workaround is to do the following:

add #[wasm_bindgen(skip)] before the field, and
implement each getter manually via #[wasm_bindgen(getter)]

The problem doesn't seem to be related to readonly but, when generating code for struct attributes, (i) a getter is generated, and (ii) a setter. In the case of readonly, only a getter is generated.
The bug seems to be in the getter parameter. The ret_ty is set to Some("void") everytime:
https://github.com/rustwasm/wasm-bindgen/blob/63872ee3514fa656f167e2d0a716501ecc299218/crates/cli-support/src/js/mod.rs#L2545-L2563
With your example, we have:
in AuxExportKind::Getter branch:
    field = "first"
    ret_ty = Some("void")

in AuxExportKind::Setter branch:
    field = "first"
    ret_ty = Some("number")

in AuxExportKind::Getter branch:
    field = "second"
    ret_ty = Some("void")

Unfortunately, all this code ends up in push_accessor_ts:
https://github.com/rustwasm/wasm-bindgen/blob/63872ee3514fa656f167e2d0a716501ecc299218/crates/cli-support/src/js/mod.rs#L3815-L3834
which overrides the ty variable (first item of a tuple stored in typescript_fields). So when we have a getter + a setter, the setter has the correct ret_ty and “fixes” the previous bug with the getter. That's why it appears only with readonly.
If we look at the Adapter's content, we have params, results and inner_results. The first two are correctly set, but inner_results seems to always be empty:
https://github.com/rustwasm/wasm-bindgen/blob/63872ee3514fa656f167e2d0a716501ecc299218/crates/cli-support/src/wit/standard.rs#L24-L31
@alexcrichton What's the difference between Adapter.results and Adapter.inner_results?


So, what with column filters ?

Hi, are you planning to fix column filters? They're not displayed (
Neither Choice filter, nor Text filter:
$statusFilter = new ChoiceFilter();
        $statusFilter->set([
            'choices' => ['foo' => 'bar', 'bar' => 'baz']
        ]);
        $textFilter = new TextFilter();

        $table = $dataTableFactory->create()
            ->add('id', TextColumn::class, ['label' => 'Id'])
            ->add('status', TextColumn::class, ['field' => 'e.status','searchable' => true, 'filter' => $statusFilter])
            ->add('name', TextColumn::class, [ 'field' => 'e.name', 'filter' => $textFilter])
            ->createAdapter(ORMAdapter::class, [
                'entity' => Entity::class,
                'hydrate' => AbstractQuery::HYDRATE_ARRAY,
                'query' => function (QueryBuilder $builder) use ($scheduleIds): void {
                    $builder
                        ->select('e')
                        ->from(Entity::class, 'e')
                    ;
                },
            ])
            ->handleRequest($request);

datatables.yaml:
# Latest documentation available at https://omines.github.io/datatables-bundle/#configuration
datatables:
    language_from_cdn: false
    # Set options, as documented at https://datatables.net/reference/option/
    options:
        lengthMenu : [10, 25, 50, 100, 250, 500, 1000, 2500]
        pageLength: 10
        dom: "<'row' <'col-sm-12' ftr>><'row' <'col-sm-6'l><'col-sm-6 text-right'pi>>"
        searching: true

    template_parameters:
        # Example classes to integrate nicely with Bootstrap 3.x
        className: 'table table-bordered table-hover data-table report-table'
        columnFilter: 'both'

    # You can for example override this to "tables" to keep the translation domains separated nicely
    translation_domain: 'messages'

table.html.twig:
$(function () {
            $('#table').initDataTables({{ datatable_settings(datatable) }},
                {
                    searching: true,
                    dom: 'Bfltip',
                });
        });

Column filters are essentially "unsupported, use at own risk". People are using them and happy with them but I have no clue how they work as we don't use it ourselves. PRs to improve them welcome.

Hope this feature will work soon in further updates, I need a multiple choice filter/search... As I see there is no way how to do this with column search.

There is a open pr for this https://github.com/omines/datatables-bundle/pull/348
Alternativly you could use my fork (which is poorly maintainted) and use the column filters  https://github.com/omines/datatables-bundle/pull/336#issuecomment-2051441199
Keep in mind that my fork will get some other changes too, like case insensitive global search and stuff


Title bar draw problem next to close button

Windows Terminal version
1.20.11781.0
Windows build number
10.0.22631.4037
Other Software
No response
Steps to reproduce
Note: This is intermittent.

Open up Windows Terminal.
Change focus from another program like Edge and back to Windows Terminal. The most reliable way is to click on the tab on Windows Terminal.
See title bar is not acrylic except for small portion to the right of the close button (see attached).
If problem does not happen, change focus back to Edge and repeat steps 2-4.

Expected Behavior
I expected the acrylic to be consistent.
Actual Behavior
Acrylic title bar sometimes does not render. I also see it blinking sometime when focus is changed.

I'm guessing this is a DWM bug outside our control. I would file feedback on
Desktop Environment > DWM (Desktop Window Manager)

and if you Share the link here, I can make sure that it gets promoted internally.

I've put in an issue to the Feedback Hub. However, it is not showing up in the "My feedback" filter. Hopefully, it will show up soon and I can share a link.

Here is a link to the feedback: https://aka.ms/AArxfhj.

Unfortunately, I don't know how to do it atm and can't look for a week or so. Jen Gentleman may be able to help you!


[QUERY] Custom Vision: Is there a way to avoid uploading images that were already uploaded?

Library name and version
Azure.CognitiveServices.Vision.CustomVision
Query/Question
Hi All,
I am trying to use the available APIs to upload training images to be used with the customvision.ai website. I am wondering if there is a way to upload only images that are not currently uploaded to my custom vision project on customvision.ai? I would like to start the upload with all my available images but omit the upload for images that have already been uploaded in the past to customvision.ai. Thank you.
Environment
No response

@nikoliano I don't think that is possible. Do you want to upload the images individually or in a batch?


Fix google test configuration

This PR focuses on solving the issues related with generating and running the test executables that rely on googletest #35 and #34.
The cmake source for generating tests was moved to a CMakeLists.txt inside tests directory.
The root CMakeLists.txt file defines an option BUILD_ENGINE_TESTS to determine if the tests should be build.
If so, the entry.cpp is removed from the source files - to remove the entry.cpp:main() - and the tests directory is added as a subdirectory.

@RiscadoA can you please test this to see if #35 was fixed?

Also, instead of removing the entry.cpp from the main cubos target, which breaks the samples, we should create an additional cubos-test target which doesn't contain the entry.cpp file. This way we can run samples and tests at the same time.

The current build pipeline generates:

cubos_lib (library): with cubos core components
cubos (library): with the entrypoint to start the engine and cubos_lib
samples (executable): executable that links cubos and game assets
cubos_tests (executable): executable to test cubos_lib

Options BUILD_SAMPLES and BUILD_ENGINE_TESTS can be used to determine if samples and cubos_tests are generated, respectively.
Commit #4d704177a6c16d4f08a61c3aca3ad14b4fbbcf8c also solves #40
Down the road, we should consider restructuring the repo to solve #41 and include a cubos editor executable in the cmake too.
Additionally, SCons might be an interesting approach to ease the engine generation as proposed in #42


Unable to download api-umbrella in ubuntu-16.04

I am following the link https://api-umbrella.readthedocs.io/en/latest/getting-started.html for api-umbrella installation.
But i am getting following error while running apt-get update command-
W: The repository 'https://dl.bintray.com/nrel/api-umbrella-ubuntu xenial Release' is not signed.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
Please let me the problem.

Same here when updating. Related to #383

Sorry for the delay! v0.15.1 should now be properly authenticated if you follow the updated installation instructions here (note there's a new apt-key command): https://apiumbrella.io/install/ Let us know if you're still running into any issues, though.


can't reproduce same performance

Hi, first of all thank you for sharing the codes.
I am currently trying to reproduce MPJPE(P1) 40.78 with your SemGN+nonlocal model, having ground truth 3d pose as input.
I copied your model, adjacency matrix parsing code. Optimizer and loss function, data preprocesses are all coded according to this repo.
The only different thing is the preprocessed Human3.6M dataset and dataloader code, joint coordinates are in mm scale, but I'm sure it doesn't have problem.
Do you have any clue what's going wrong? This is my training loss graph and error graph.

ps)
While the code uses normalized adjacency matrix which is defined as 'A serves as a mask which forces that for node i in the graph' in the paper, what is the point of normalizing if it is just a mask? Is there any difference with just using original adjacency matrix? Thanks.

Hi @hongsukchoi
Thanks for your interest in our work.
Your training and evaluation curves make sense to me. I have no idea why the performance is different here. Maybe you can check "data/prepare_data_h36m.py" to see if we have the same preprocessed data.
No, they should be the same. In "models/sem_graph_conv.py", we just convert the adj into a mask, so the normalization does not matter here.
Best,
Long

Hi Long,
I really appreciate your answer and suggestion. I found the difference between your's and my setting.
It was whether to root aligning the img coordinate input after normalize_screen_coordinates function.
I didn't realize that this repo don't align the input relative to root joint. I was confused with the paper's guideline.
After removing the code of root-aligning, I got a similar performance.
and thanks for assuring me about the preprocessing adjacency matrix!


Introduce gosec for Static Application Security Testing (SAST)

How to categorize this PR?

/area testing
/kind task
What this PR does / why we need it:
This PR introduces gosec for Static Application Security Testing for the test-infra repo.
It uses the default ruleset of gosec with two exceptions.
Scanning generated code is disabled. The Kubernetes code-gen creates hundreds of low priority findings for unsafe pointers (G103). The generated code has proven that it is working and it is not possible to address those findings.
The ./hack folder is excluded, because gosec does not support nested go modules (like logcheck) and there is no productive code in this folder anyway.
All findings based on these settings have been mitigated in this PR.
There are two new make targets.

make sast runs the linter and logs all finding to console and fails in case of errors.
make sast-report can be used in build pipelines. It fails on errors too. Additionally, it creates a report in sarif format to /gosec-report.sarif file. This report also tracks suppressed findings.

Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
/invite @dguendisch
Release note:

Add `gosec` linter

This PR proposes changes that would break the pipeline definition:
test-infra-sast-linter: Traceback (most recent call last):
  File "/usr/lib/python3.12/site-packages/concourse/replicator.py", line 141, in render
    definition_descriptor = self._render(definition_descriptor)
                            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/site-packages/concourse/replicator.py", line 185, in _render
    'definition': factory.create_pipeline_definition(),
                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/site-packages/concourse/factory.py", line 88, in create_pipeline_definition
    self._apply_traits(variant)
  File "/usr/lib/python3.12/site-packages/concourse/factory.py", line 177, in _apply_traits
    transformer.process_pipeline_args(pipeline_def)
  File "/usr/lib/python3.12/site-packages/concourse/model/traits/release.py", line 505, in process_pipeline_args
    raise ValueError(f'{asset=}\'s step_name refers to an absent build-step')
ValueError: asset=BuildstepLogAsset(ocm_labels=[{'name': 'gardener.cloud/purposes', 'value': ['lint', 'sast', 'gosec']}, {'name': 'gardener.cloud/comment', 'value': 'we use gosec (linter) for SAST scans\nsee: https://github.com/securego/gosec\n'}], type='build-step-log', name='check-build-step-log', step_name='check', artefact_type='application/data', artefact_extra_id={}, purposes=['lint', 'sast', 'gosec'], comment='we use gosec (linter) for SAST scans\nsee: https://github.com/securego/gosec\n')'s step_name refers to an absent build-step


Create First occurrence by binary search.java

(https://github.com/1OMKAR7NAM)

Greetings, Please read programs carefully and then make any pull request. This is not any program I have mentioned in. Kindly create another PR from the programs as mentioned in Readme.md file.
Waiting for another PR!!!


Remove finality from SpringSecurityPropertiesAuthorizationGenerator

No problem.

We are on master (version 3.0.0). Maybe you may want that for version 2.2 as well?


sample panel and widgets WIP

A simple sample panel and set of widgets. The panel has some internal documentation, the widgets not so much. It is installed on the hamburger menu under "sample".
Will continue to flesh out the widgets, and then add a set of more advanced widgets to expose features of the runtime.
Also there is a very rough doc for installing a panel and widgets. Now that the sample widgets are there, I can use them and the upcoming more advanced widgets as example code and references in the doc

More commits from today -- adding comments to the sample widgets, add one new sample widget, some light refactoring, some fixing of things that broke recently.


Re-write in Rust

C# stinky. AWS S3 SDK broken. Going to write this in GTK 4 and you can't stop me :)

meme


In react-native 0.19 the values are not shown

I upgraded my react-native version to 0.19, but after that the values on the Dropdown does't show. The dropdown appears but with no contents.

same here with 0.20

This is due to the breaking change in react-native 0.19.0. I have updated the component to adapt the change
@danimasa @JeJan
Please update and see if the issue has been fixed

Now all works well, Thanks.


Request - Property internal set vs public flag or filter

Is there an equivalent to Symbols.ThatArePublic that could be used to check if a property has a public vs internal or private setter? I didn't see anything on https://github.com/NeVeSpl/NTypewriter/blob/master/NTypewriter.CodeModel/ISymbolBase.cs

I assume that IPropertySymbol.IsReadOnly is not what you need? I do not know how that happened, but only minimal info about properties is exposed, and even unit tests are missing for what is already exposed.  These shortcomings will definitely need to be completed.

Even when setting the setter to private IsReadOnly is still false and ThatArePublic still includes it. E.g.
public Guid? ForeignId { get; private set; }


Prez UI pagination tabs seem to count incorrectly

At GSQ's new Prez/PrezUI, we see:

The pagination for these vocabs is:

so pages of 20 should mean only 5 pages given the 98 vocabs, not "10".
Also, pages 1 - 5 work, as expected, but the generated link for pages 6 - 10, when clicked, shows:

Can this pagination link generation be fixed?

This should be fixed in https://github.com/RDFLib/prez-ui/pull/80 and included in prez-ui v3.3.0.
See the GSQ Prez working correctly at https://gsq-prez.dev.kurrawong.ai/v/vocab.


bug(tabs + expansion panel): wrong display of expansion panel in hidden tabs

Bug, feature request, or proposal:
Bug
What is the expected behavior?
Expansion panels on other tabs should look normal
What is the current behavior?
expansion panel is open by default + heading has a wrong size
What are the steps to reproduce?
Providing a StackBlitz/Plunker (or similar) is the best way to get the team to see your issue.
http://plnkr.co/edit/i6eg0f?p=preview
What is the use-case or motivation for changing an existing behavior?
Consistency and usability
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
At least since 5.0.0-rc.3 up to 5.0.0
Is there anything else we should know?
Since 5.0.0-rc.3:

Wrapping in a div with ngIf is not working anymore as a workaround!

Closing as duplicate of #5269


drag and drop

useful ?
https://github.com/atom/electron/blob/master/docs/api/file-object.md

I think it's gadget but I know people who'd love to use it that way.
Maybe keep this for later ?

I just added some basic drag & drop functionality to import a project by dropping it's folder.

User drags a folder into the window
1 deposit zone appears (or 2 zones if in advanced mode) (needs better styling)
On drag-over of the zone, it indicates if you can drop it there depending on what you drag
If dropped on update zone, the settings are updated like if you used the import button.
If it's a wrong file or user doesn't drop it; the drop zone goes away.

It's pretty basic for the moment and only checks if it's a folder, not even if it's an OF sketch folder; but everything behind the scenes is there.
The 2nd zone could be used for simply setting a batch mode folder.
HTML5 drag-and-drop event handling appears to be pretty disastrous but I believe this points us in the right direction.  I didn't expect this! xD
dragleave and dragenter events get called quite randomly; and I'm not event talking about all the event bubbling stuff...
There's still a little bug when you drag it too fast into the window but it's a minor matter IMO.
Please tell me what you think of it :)

i think the best solution for "denied" is a modal error/warning box that reminds people what they can drop. anything else should cause a change in the interface, so it will be clear it worked.

I forgot about the reminder purpose of the modal, that might make it a good reason; and if they don't want the modal, the box indicates it before dropping. :)


Mopro wasm halo2

To enable multithreading in WASM, wasm-bindgen-rayon must be used.

Usage with WebAssembly
By default, when building to WebAssembly, Rayon will treat it as any other platform without multithreading support and will fall back to sequential iteration. This allows existing code to compile and run successfully with no changes necessary, but it will run slower as it will only use a single CPU core.

from: Rayon - github
Currently, wasm-bindgen-rayon version 1.2.1 can only be compiled with the nightly rust, specifically nightly-2024-07-18

[x] Adding test case on test-e2e based on js

[x] Perform the test case in headless with selenium driver
[x] Update GH action for test-e2e/web in headless way

[x] Update related documentations, README and doc
[x] Merge https://github.com/sifnoc/plonkish-fibonacci-sample/pull/4

Related issue: https://github.com/zkmopro/mopro/issues/202

I followed the wasm-pack tutorial
and found that wasm-bindgen can be done with stable toolchain
see this commit and CI result
(the feature flags should be fixed)
but the commit is built for nodejs, not sure if we can have both nodejs and web targets

You can see how many web-worker spawned in browser from dev tool like one below.

It's updated at 63e90b9


[IAC-43] Create Ably App Datasource

Includes:

Documentation updates (terraform-docs + tfplugindocs)
Examples in resources + playground folders. Creates an app datasource and demonstrates use with tf outputs.
Ably App Datesource code + Acceptance tests
Update provider.go to expose app datasource.

This is a lot of duplicated code? Will we have to do this for every resource type? Can't we do it with one type? Can we have the app resource implement the resource and data interfaces?

This is a lot of duplicated code? Will we have to do this for every resource type? Can't we do it with one type? Can we have the app resource implement the resource and data interfaces?

Agreed, In part, this is one of the reasons I logged this PR ahead of schedule as it'll give us time to formulate a plan on how to proceed.
Let's discuss this one and agree on an approach with the team.

This is the new approach, right?

Considering that we are not likely to merge this in the near future - should we maybe move the PR into "draft" stage? It is "waiting for reviews" right now.

We can probably go further and close this PR for now. It can be reopened when we implement datasources. wdyr @kavalerov ?

Agreed. Lets do this.


OpenGL error GL_INVALID_ENUM detected at engine/renderer/tr_backend.cpp:2879 with Q3Rally map

Q3Rally is a Quake3 mod that became standalone, there is no reason Q3Rally maps would not load and render properly, otherwise that means we have a bug or a regression in the engine.
When loading the nightcity map, I get this warning spammed in some place:
Warn: OpenGL error GL_INVALID_ENUM detected at …/src/engine/renderer/tr_backend.cpp:2879

How to reproduce:

Download Q3Rally_v0.3c_linux64.zip from this place
Extract the baseq3 folder from that archive and move it right to daemon
Run the game with a command like that: ./daemon -homepath /tmp/unvq3r -pakpath baseq3r/ -set fs_legacypaks 1 -set fs_extrapaks 'q3rpak0 textures' -set r_checkGLErrors 1 -set g_neverEnd 1 +devmap q3r_nightcity
Teleport to a place triggering the bug: /setviewpos -110 -1550 200 -90 0


[scale-test] WIP numerical nonlinear regression, avoids linear(log()) mis-fitting

This implements Nelder-Mead simplex nonlinear optimization for fitting polynomial and exponential models to scale-test input, replacing the previous approach of doing linear regression in log-space (which broke down when there were constant offsets to the data -- unfortunately quite common).
It doesn't use numpy (which is why it's manual and wonky) but it does seem to more-or-less work; NM is unstable and sensitive to initial guesses so we have to do a few retries before giving up sometimes, but in practice it seems to hit a usable simplex within a few tries on most data.
Feedback/improvements welcome. I included a handful of test vectors which succeed on this, some of which failed on the older linear-regression-in-log-space scheme. Probably there's still a bunch of room for improvement though; this kinda stuff isn't super familiar territory for me.

@graydon This sounds like a question for @stephentyrone!

@swift-ci please test

Build failed
Swift Test Linux Platform
Git Sha - 3f33e0c00e579a01f038c39fe8700f2c85dd65e1

Build failed
Swift Test OS X Platform
Git Sha - 3f33e0c00e579a01f038c39fe8700f2c85dd65e1

@swift-ci please test and merge

@swift-ci please test and merge

@swift-ci please test and merge

@swift-ci please test and merge


dynamic dropDowns do not select in headless mode

Expected behaviour
Should be able to select an option from a dropDown which depends on a dropDown.
e.g.
dropDown 1 - Option 1 selected
dropDown 2 - Option 1.1 displays
dropDown 1 - Option 2 selected
dropDown 2 - Option 2.1 displays
Actual behaviour
When I run the below code I get the reported error that the option can not be found.
step("Select a team", async() => {
await dropDown({name:'teamType'}).select('Publisher')
await dropDown({name:'teamID'}).select('Publisher 1')
});
Error: Option not available in drop down
Steps to reproduce
You can use the link and the code above to reproduce this issue.
https://css-tricks.com/examples/DynamicDropdown/
Versions
node v10.16.0
taiko Version: 1.0.0 (Chromium: 76.0.3803.0) RELEASE

@tristanjclarke Looks like it's not an issue with Taiko's dropDown.
My suggestion would be to pass the waitForStart option to the goto api;
Example:
await goto('https://css-tricks.com/examples/DynamicDropdown/', {waitForStart:2000});
await dropDown({id:'text-one'}).select('Snacks');
await dropDown({id:'text-two'}).select('Chips');

How might this work when my dropDown is on a different page to the homepage? Currently when trying the below I get the same error as before.
Flow
Fill in login details on login page.
Click login on login page.
Taken to Profile page with Change Team modal
Fill in dynamic dropDown on profile page.
Click save on profile page.
Login Page:
step("Goto Login page", async () => {
await goto("http://<IP_ADDRESS>/login", {waitForStart:2000})
});
step("Type in 'Email with: ", async (emailAddress) => {
await write(emailAddress, into(textBox({name:'email'})))
});
step("Type in 'Password' with: ", async (password) => {
await write(password, into(textBox({name:'password'})))
});
// Expects to be taken to Profile page.
step("Click on 'Login' button", async() => {
await click(button('Login'))
});
Choose Team Page:
step("Fill in 'Change Team' modal with: , ", async(team, teamName) => {
await waitFor(1000)
await dropDown({name:'teamType'}).select(team);
await dropDown({name:'teamID'}).select(teamName);
});

@tristanjclarke Here is a list of API which supports waitForStart option.
openTab, goto, reload, goBack, goForward, click, write, clear, press, mouseAction and evaluate
So you can pass waitForStart to the API call which takes you to the dropdown page.

@negiDharmendra I have tried the waitForStart option with the click API which unfortunately did not work.
The below code should open up a modal, and fill in the dynamic dropdown options. Unfortunately, when I run it I get the same error, "Option not available in drop down".
step("Click on 'Change Team' button", async() => {
    await waitFor(1000)
    await click('Change team', {waitForStart:5000})
});

step("TEST - Fill in 'Change Team' modal with: <team>, <teamName>", async(team, teamName) => {
    await waitFor(1000)
    await dropDown({name:'teamType'}).select(team);
    await dropDown({name:'teamID'}).select(teamName);
});

## Change Team Scenaio
* Click on 'Change Team' button
* TEST - Fill in 'Change Team' modal with: "Publisher", "Dev Publisher"

Hi @negiDharmendra is there any update on this issue?

@tristanjclarke One more option is to wait for navigation to complete before you proceed with any other action on the dropdown page, so that the page is fully loaded.
So you can use the navigationTimeout option which is defaulted to 30 seconds. Try and increase the value and then try to select a value from the dropdown.
More details about waitForNavigation  here.

@tristanjclarke Are you still facing issues?

@tristanjclarke Please feel free to reopen this issue again if you face this issue again.

This is reproducible if we have multiple dropdowns that are dependent on change events. If the change event is registered on the parent element of a dropdown it doesn't work.
Eg html to reproduce the issue:

  One
  <select id="select-one" name="select" value="select">
     <option>Select One</option>
     <option>Hot Beverages</option>
    </select>

  Two
  <select id="select-two" name="select" value="select">
     <option>Please select from above</option>
    </select>

This issue has been tested and verified. Multiple dropdown with change events works as excepted by using dropdown api.
Tested version: f2208373c36bfea0b8e254b417486b9818993e6e

When this fix will get release ?
I have similar issue with dropDown change event doesn't get fire
Taiko Version: 1.0.2 (Chromium:76.0.3803.0)


Malformed TXT record (zone wrongly duplicated as part of subdomain)

We're using the Route53 DNS module to satisfy ACME challenges but are hitting a strange bug. For some reason, the TXT record created is malformed and wrongly duplicates the main zone as part of the subdomain (causing an endless verification timeout loop).
We are running caddy in a container on an EC2 machine.
Contents of Docker file for Caddy:
FROM caddy:2.3.0-builder-alpine AS builder

RUN xcaddy build \
    --with github.com/caddy-dns/route53

FROM caddy:2.3.0-alpine
COPY --from=builder /usr/bin/caddy /usr/bin/caddy

COPY Caddyfile /etc/caddy/Caddyfile

Contents of /etc/caddy/Caddyfile in the running container (real FQDN is different but have kept everything else the same)
www.mydomain.com
reverse_proxy <IP_ADDRESS>:3000
tls {
  dns route53 {
    max_retries 10
    aws_profile ""
  }
}

This results in the following TXT record being created in Route53: _acme-challenge.www.mydomain.com.mydomain.com. (note the zone is duplicated).
The challenge verification then times out since it looks for _acme-challenge.www.mydomain.com.  (which is never created).
If we manually create the correct TXT record (via the Route53 web console) and use the value from the wrongly auto-created TXT record, verification passes. The wrongly created TXT record is then automatically cleaned up, and the manually created one stays present.
Here's a log capture showing this (with s/realFQDN/www.mydomain.com/g to keep it generic):
root@ip-10-0-0-17:~# docker logs caddy
{"level":"info","ts":1631101549.0512967,"msg":"using provided configuration","config_file":"/etc/caddy/Caddyfile","config_adapter":"caddyfile"}
{"level":"info","ts":1631101549.0558064,"logger":"admin","msg":"admin endpoint started","address":"tcp/localhost:2019","enforce_origin":false,"origins":["localhost:2019","[::1]:2019","<IP_ADDRESS>:2019"]}
{"level":"info","ts":1631101549.0587218,"logger":"http","msg":"server is listening only on the HTTPS port but has no TLS connection policies; adding one to enable TLS","server_name":"srv0","https_port":443}
{"level":"info","ts":1631101549.0589776,"logger":"http","msg":"enabling automatic HTTP->HTTPS redirects","server_name":"srv0"}
{"level":"info","ts":1631101549.06152,"logger":"tls.cache.maintenance","msg":"started background certificate maintenance","cache":"0xc0002e12d0"}
{"level":"info","ts":1631101549.0621595,"logger":"http","msg":"enabling automatic TLS certificate management","domains":["www.mydomain.com"]}
{"level":"info","ts":1631101549.0632653,"msg":"autosaved config","file":"/config/caddy/autosave.json"}
{"level":"info","ts":1631101549.0637987,"msg":"serving initial configuration"}
{"level":"info","ts":1631101549.0639155,"logger":"tls","msg":"cleaned up storage units"}
{"level":"info","ts":1631101549.0643346,"logger":"tls.obtain","msg":"acquiring lock","identifier":"www.mydomain.com"}
{"level":"info","ts":1631101549.0663319,"logger":"tls.obtain","msg":"lock acquired","identifier":"www.mydomain.com"}
{"level":"info","ts":1631101549.981814,"logger":"tls.issuance.acme","msg":"waiting on internal rate limiter","identifiers":["www.mydomain.com"]}
{"level":"info","ts":1631101549.9818606,"logger":"tls.issuance.acme","msg":"done waiting on internal rate limiter","identifiers":["www.mydomain.com"]}
{"level":"info","ts":1631101550.898957,"logger":"tls.issuance.acme.acme_client","msg":"trying to solve challenge","identifier":"www.mydomain.com","challenge_type":"dns-01","ca":"https://acme-v02.api.letsencrypt.org/directory"}
{"level":"error","ts":1631101551.5204628,"logger":"tls.issuance.acme.acme_client","msg":"cleaning up solver","identifier":"www.mydomain.com","challenge_type":"dns-01","error":"no memory of presenting a DNS record for www.mydomain.com (probably OK if presenting failed)"}
{"level":"error","ts":1631101551.7166426,"logger":"tls.obtain","msg":"will retry","error":"[www.mydomain.com] Obtain: [www.mydomain.com] solving challenges: presenting for challenge: adding temporary record for zone mydomain.com.: InvalidChangeBatch: InvalidChangeBatch: [Tried to create resource record set [name='_acme-challenge.www.mydomain.com.mydomain.com.', type='TXT'] but it already exists]\n\tstatus code: 400, request id: 4d3c4fea-681a-4c09-8965-7fd2fb111dfd (order=https://acme-v02.api.letsencrypt.org/acme/order/192612760/22920570770) (ca=https://acme-v02.api.letsencrypt.org/directory)","attempt":1,"retrying_in":60,"elapsed":2.650090972,"max_duration":2592000}
{"level":"info","ts":1631101612.867892,"logger":"tls.issuance.acme.acme_client","msg":"trying to solve challenge","identifier":"www.mydomain.com","challenge_type":"dns-01","ca":"https://acme-staging-v02.api.letsencrypt.org/directory"}
{"level":"error","ts":1631101613.3855636,"logger":"tls.issuance.acme.acme_client","msg":"cleaning up solver","identifier":"www.mydomain.com","challenge_type":"dns-01","error":"no memory of presenting a DNS record for www.mydomain.com (probably OK if presenting failed)"}
{"level":"error","ts":1631101613.5276074,"logger":"tls.obtain","msg":"will retry","error":"[www.mydomain.com] Obtain: [www.mydomain.com] solving challenges: presenting for challenge: adding temporary record for zone mydomain.com.: InvalidChangeBatch: InvalidChangeBatch: [Tried to create resource record set [name='_acme-challenge.www.mydomain.com.mydomain.com.', type='TXT'] but it already exists]\n\tstatus code: 400, request id: 8cfb3e00-9657-453d-b867-5e2193a54623 (order=https://acme-staging-v02.api.letsencrypt.org/acme/order/25931808/488611558) (ca=https://acme-staging-v02.api.letsencrypt.org/directory)","attempt":2,"retrying_in":120,"elapsed":64.461055717,"max_duration":2592000}
{"level":"info","ts":1631101735.2945147,"logger":"tls.issuance.acme.acme_client","msg":"trying to solve challenge","identifier":"www.mydomain.com","challenge_type":"dns-01","ca":"https://acme-staging-v02.api.letsencrypt.org/directory"}
{"level":"info","ts":1631101876.6568108,"logger":"tls.issuance.acme.acme_client","msg":"validations succeeded; finalizing order","order":"https://acme-staging-v02.api.letsencrypt.org/acme/order/25931808/488621888"}
{"level":"info","ts":1631101878.9950337,"logger":"tls.issuance.acme.acme_client","msg":"successfully downloaded available certificate chains","count":1,"first_url":"https://acme-staging-v02.api.letsencrypt.org/acme/cert/fa47a21093c8f08654bbf8d740f229b28fdd"}
{"level":"info","ts":1631101878.9953816,"logger":"tls.issuance.acme","msg":"waiting on internal rate limiter","identifiers":["www.mydomain.com"]}
{"level":"info","ts":1631101878.9954185,"logger":"tls.issuance.acme","msg":"done waiting on internal rate limiter","identifiers":["www.mydomain.com"]}
{"level":"info","ts":1631101880.0348005,"logger":"tls.issuance.acme.acme_client","msg":"trying to solve challenge","identifier":"www.mydomain.com","challenge_type":"dns-01","ca":"https://acme-v02.api.letsencrypt.org/directory"}
{"level":"info","ts":1631102028.8770761,"logger":"tls.issuance.acme.acme_client","msg":"validations succeeded; finalizing order","order":"https://acme-v02.api.letsencrypt.org/acme/order/192612760/22921420555"}
{"level":"info","ts":1631102029.8177788,"logger":"tls.issuance.acme.acme_client","msg":"successfully downloaded available certificate chains","count":2,"first_url":"https://acme-v02.api.letsencrypt.org/acme/cert/0412ef9b7a225e28e353c35d0a1119f972cc"}
{"level":"info","ts":1631102029.818293,"logger":"tls.obtain","msg":"certificate obtained successfully","identifier":"www.mydomain.com"}
{"level":"info","ts":1631102029.8183181,"logger":"tls.obtain","msg":"releasing lock","identifier":"www.mydomain.com"}

We're not sure how to debug if this is a real bug or an issue with the DNS configuration (and how Caddy interacts with it) on the EC2 host . Simple checks like systemd-resolve --status and cat /etc/hosts all seem ok


trigger build

Signed-off-by: Maggie Chen<EMAIL_ADDRESS>
Related Issue: [closes|resolves|fixes] open-cluster-management/backlog#<ISSUE_NUMBER>
Description of Changes

[ ] I wrote test cases to cover new code

/hold
Code freeze, will wait for 2.4.9


install binary at local

Hello, I am a code review bot on flows.network.
It could take a few minutes for me to analyze this PR. Relax, grab a cup of coffee and check back later. Thanks!


HTTPS with self-signed cert by default for web panel?

Basically the question is listed in the topic. Given that WEB UI is used for generation of new users, passwords transferred over HTTP is not secure. Is that hard to implement secure HTTPS server with self-signed certificate?

Yeah, what about https? HTTP = MITM

Sorry, this project is deprecated


Restore Documentation Links in README

Links won't be available on hydra until this is pushed to master.

Until what is pushed to master? Shouldn't the links go to the latest job regardless?

I didn't think this through. Opening new PR


Clean up documentation for simple example integration test

Part of #2737.
Description

As a first stab at improving the documentation of the integration test framework, this PR moves the documentation of the simple example integration test that previously lived at tools/integration-test/src/tests/example.rs into tools/test-framework/src/docs/. Going forward, we'll centralize the documentation of the framework in this directory.
Follow up PRs will add more docs walking through more complex integration tests in order to illustrate different use cases and recipes for using the test framework.

PR author checklist:

[ ] Added changelog entry, using unclog.
[ ] Added tests: integration (for Hermes) or unit/mock tests (for modules).
[x] Linked to GitHub issue.
[x] Updated code comments and documentation (e.g., docs/).
[x] Tagged one reviewer who will be the one responsible for shepherding this PR.

Reviewer checklist:

[ ] Reviewed Files changed in the GitHub PR explorer.
[ ] Manually tested (in case integration/unit/mock tests are absent).

Follow up PRs will add more docs walking through more complex integration tests in order to illustrate different use cases and recipes for using the test framework.

Should we open a follow-up issue to capture these needs? Then the present PR can close #2737.

Should we open a follow-up issue to capture these needs

Added #2937 to capture the additional work.


Group Invert SOP

Aims

[x] Fast invert group
[x] Support vertex groups

Fix it in future

It is impossible to display a list of vertex groups in the menu at this moment
For the same reason, it is not possible to detect that a group type is vertex

[ ] Wrong menu type

[ ] Create 'Keep Original Group' flag (Group Promote style)
Enabled flag should activate 'New Name' field.
Default field value something like "chs("group")_inv"

[ ]  Create 'Keep Original Group' flag (Group Promote style)
Enabled flag should activate 'New Name' field.
Default field value something like "chs("group")_inv"

Backlogged for the future.

After selecting existing group, Group Invert SOP can create new group. For this feature change group type. Your new group will have some name, but new type.

Toolbox

Waiting for #76


Add PyCon 2016 links

HI @ptt-homme Thanks for the updates and fixing the Twitter handle from Jess!


Disable Swipe down

Can we disable swipe down. transitionDelegate.interactiveDismiss = false. I have tried this and it's not working

#25  fixed


ENH: Use strongly typed enums for the Algorithm type in math morphology

Use strongly typed enums for the Algorithm type in math morphology.
PR Checklist

[X] No API changes were made (or the changes have been approved)
[X] No major design changes were made (or the changes have been approved)
[X] Added test (or behavior not changed)
[X] Added Python wrapping to new files (if any) as described in ITK Software Guide Section 9.5

A few notes:

The patch set is failing locally because the itkMathematicalMorphologyExport.h file is not found. IIUC the file needs not to be created manually, but not sure why it is not found in this case.
Checking especially the changes to the itk-module.cmake and CMakeLists.txt would be appreciated.
Not sure if having the actual enum class inside another class is preferable (i.e. itk::MathematicalMorphologyEnums in this case). I've seen other places where the enum class is not inside a class. I guess the former allows to have a more descriptive localization and potentially having all enums belonging to a class or module in a single file.
Not sure if the enum class has to have its own test exercising the serialization method. Have not found any examples.

P.S. I didn't look at the rest of the changes, as they might change after making this build 😄

As the link line has lib\ITKLabelMap-5.2.lib ITKMathematicalMorphology.lib lib\ITKPath-5.2.lib, https://github.com/InsightSoftwareConsortium/ITK/blob/master/Modules/Filtering/AntiAlias/itk-module.cmake needs to either compile_depend or plain old depend on ITKMathematicalMorphology

Thanks @dzenanz ! Let's see how 24b6e66 does on that front.

P.S. I didn't look at the rest of the changes, as they might change after making this build smile

Sounds reasonable.
Cross-referencing this comment, since it looks related. Also, I realize the comment towards the end of the related section in the migration guide.

Using COMPILE_DEPENDS similarly fails on my local Windows/VS 2015 build, so I am short of ideas about where to look.

Modules/Filtering/MathematicalMorphology/src/CMakeLitsts.txt

CMakeLitsts.txt -> CMakeLists.txt :bulb: @jhlegarreta

As the link line has lib\ITKLabelMap-5.2.lib ITKMathematicalMorphology.lib lib\ITKPath-5.2.lib, https://github.com/InsightSoftwareConsortium/ITK/blob/master/Modules/Filtering/AntiAlias/itk-module.cmake needs to either compile_depend or plain old depend on ITKMathematicalMorphology

This might not be needed, now that Matt found the main mistake.

CMakeLitsts.txt -> CMakeLists.txt 💡 @jhlegarreta

@thewtex  💯 👀 🦅 thanks !

This might not be needed, now that Matt found the main mistake.

@dzenanz reverted !

The ITK.macOS failure (on test itkJPEG2000Test06) is unrelated to this patch set, so to me this is ready to be merged.

Great job Jon!

Thanks for your revies @dzenanz . As always, feels great to contribute to ITK :100: .

Test failure is unrelated. Merging.


build(deps): bump easy-peasy from 6.0.0 to 6.0.5

This PR resolves []
Description
bump easy-peasy from 6.0.0 to 6.0.5

PR Checklist

[x] I have tested my changes on iOS and Android.
[x] I hid my changes behind a feature flag, or they don't need one.
[x] I have included screenshots or videos, or I have not changed the UI.
[x] I have added tests, or my changes don't require any.
[x] I added an app state migration, or my changes do not require one.
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[x] I have added a changelog entry below, or my changes do not require one.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

Cross-platform user-facing changes

iOS user-facing changes

Android user-facing changes

Dev changes

bump easy-peasy from 6.0.0 to 6.0.5 - gkartalis

Need help with something? Have a look at our docs, or get in touch with us.

This PR contains the following changes:

Dev changes (bump easy-peasy from 6.0.0 to 6.0.5 - gkartalis)

  Generated by :no_entry_sign: dangerJS against c3eae796b7017382a267aa794b40f110dc60d5d4


⚠ Bofrost.es has degraded performance

In 8d06b00, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1689 ms

Resolved: Bofrost.es performance has improved in ec4c2e6 after 6 minutes.


Add PodDisruptionBudget to helm chart

PR Description
This PR would add PodDisruptionBudget to the helm chart

[x] CHANGELOG.md updated
[x] Documentation added
[ ] Tests updated
[x] Config converters updated

are tests required for this?
if it is required, which api version to use for tests?

Hey, thanks for contributing :)
Regarding your questions about the tests, please have a look at https://github.com/grafana/alloy/tree/main/operations/helm.
The best would be to create one for each following the same pattern than the tests we already have

I think that you could also create a new version, see this example: https://github.com/grafana/agent/pull/6393/files#diff-97d54f85324149687c80856ea9fb0f4aae8556574270efacbacf491012851f14

Fixes #1245

Question for you: what does this allow you to do that you can't already do with controller.updateStrategy? I've never used standalone pdbs before but my understanding is they are useful for matching multiple different controllers at once, but we only have the one here. There may be some other use case I am missing.

Question for you: what does this allow you to do that you can't already do with controller.updateStrategy? I've never used standalone pdbs before but my understanding is they are useful for matching multiple different controllers at once, but we only have the one here. There may be some other use case I am missing.

There are multiple things that would be really beneficial to have the PDBs
pdbs are respected by kubernetes cluster management tools,
cluster-autoscaler or karpenter would respect the PDBs, lets say there is a node rotation and I want to have atleast 50% of alloy pods to be available, in this case node rotation(cluster autoscaler or karpenter) wouldn't try to do its thing that would disrupt our alloy cluster, this is more about those things and not the rollout(availability vs deployment)

Yep, agreed that you need PDBs not just the update options. If you are using an Autoscaling solution like Karpenter, when consolidating/replacing nodes it will respect PDBs to ensure it does not take out too many pods that are backed by a PDB at once.
This looks like what I would expect.
Fixes #1570


Extension doesn't want to run my test when project folder is in a subfolder

Describe the bug
Testing tab doesn't run the test when the frontend/vue project is in a subfolder.
To Reproduce

Clone the example project:
Install package with npm i
Go to the Testing tab
Launch Test from there or from the file with the green arrow

Expected behavior
All test should run
Screenshots

Environment

OS: Windows
VSCode version: 1.70.1
Vitest version: 0.24.3
Vitest plugin version: 0.2.34

Had the same issue. I added these settings to vscode:
    // .vscode/settings.json
    "vitest.enable": true,
    "vitest.showFailMessages": true,
    "vitest.commandLine": "npm --prefix frontend run test --",
    "vitest.include": [
        "frontend/test/**/*.{test,spec}.{js,ts}"
    ]

@kaipaysen That seems to work for "run mode" but for "watch mode"
I get
/Users/arthurcheek/.nvm/versions/node/v16.13.2/bin/node ./node_modules/vitest/vitest.mjs --prefix web/frontend run test -- /Users/arthurcheek/Desktop/supercycle-experiments/supercycle-react-test/web/frontend/tests/LocationIndex.test.js --api.port 51602 --api.host <IP_ADDRESS>
Uncaught CACError CACError: Unknown option `--prefix`

@artyrcheek I get the the same message when trying to debug a test in VSCode. Anyway running the tests from Test Explorer works fine.

You can try using VS Code workspace as a workaround for now.

Hello everyone. Can someone show an example of how to use VS Code workspaces in order to implement the proposed workaround?
We currently open a folder from VS Code (not a workspace) containing both client and server apps. Folder contents are similar to the following:
.vscode\
  extensions.json
  settings.json
client\
  package.json
  ...
server\
  package.json
  ...

settings.json at the moment holds some configuration for this vitest extension, specifically:
    "vitest.enable": true,
    "vitest.commandLine": "npm run test-app-int-adapters --prefix ./client"

test-app-int-adapters is an npm script available under client/package.json to run some set of tests.
Without any configuration, test explorer does not list any test. After setting that configuration, test cases are listed in test explorer. But when running any of them, they just hang with the Running tests... message in status bar.
We searched and read other similar issues, we're just writing in this one in case anyone knows how to workaround this.
TA

Here's what Test Output pane shows after launching one of the test files:
><EMAIL_ADDRESS>test-app-int-adapters

> vitest --dir ./tests/app/int-adapters --environment happy-dom /some-path/client/tests/app/int-adapters/session/session-started.test.ts 61419 <IP_ADDRESS>

 DEV  v0.29.2 d:/some-path/client
 ✓ tests/app/int-adapters/session/session-started.test.ts  (1 test) 6ms

 Test Files  1 passed (1)

      Tests  1 passed (1)

   Start at  17:42:16

   Duration  1.79s (transform 1.05s, setup 0ms, collect 1.27s, tests 6ms)

 PASS  Waiting for file changes...

       press h to show help, press q to quit

So apparently the tests are also run correctly, but vitest runs in watch mode, and for the extension they are still running. So I guess it's another issue, not related to current one.

For completeness, this comment from another issue pointed our attention to the need for a trailing --, as also mentioned in readme config section.
We modified extension settings like the following:
    "vitest.enable": true,
    "vitest.commandLine": "npm run test-app-int-adapters --prefix ./client --"

and now the target set of tests runs correctly in test explorer.

This should be fixed in pre-release 0.5.0 and higher. Note that the extension now requires Vitest 1.4.0 or higher.


Documentation on ESP32 DMA I2S Camera mode

Two status questions if I may:

Is the ESP32 Technical Reference Manual as it relates to I2S Camera DMA considered complete?
Is the ESP-IDF support of ESP32 camera mode considered complete?

The back story:
I have been studying the Camera support and this excellent sample on and off for a few months now and I'm making very slow progress.  I study the code and contrast that against the documentation in the Technical Reference and then examine the data structures in the ESP-IDF ... but after a day or two I get frustrated and walk away to another area of the ESP32.  I seem to find that the Technical Reference Manual is the briefest of summaries and while it may be technically accurate I'm afraid I have to say that is consumer unfriendly.  Obviously, there is the opportunity for this just to be my lack of comprehension of what I am reading ... so if there other community members who feel they have a grasp off it, I'd dearly love to spend time with you.
Another thought I had was that this area is still being baked ... and hence this issue/question ... what is the state of I2S Camera DMA documentation and support?  Is this component still "cooking" or is it considered complete?  If complete, then we'll see how we can improve.  If still being developed, then I'll back away until such time as it is in a more consumable state.
The second question, the one relating to ESP-IDF.  It seems that the camera samples are "poking around" at the I2S registers which feels much lower level compared to the other ESP-IDF functions.  Are there plans to encapsulate I2S camera DMA into higher level ESP-IDF functions?

Is the ESP32 Technical Reference Manual as it relates to I2S Camera DMA considered complete?
I wouldn't be able to write this driver if all I had was the description in the TRM. However at this time the intersection of sets of people who can write good technical documentation, who understand how I2S camera mode works, and who don't have any higher priority tasks, is essentially nil.

Same goes for camera mode support in IDF. Theoretically this code, after some refactoring, could be included into IDF. However I fear that if I do so, i will sign up for a non-trivial amount of time spent supporting people who wish to use this code. Unfortunately, this is one of the drivers that is more susceptible to wiring, signal integrity, and other hardware issues which will be hard to troubleshoot when someone reports them. So until we have a team member with enough capacity to maintain this code, i am not planning to bring it into the IDF.
As far as the code goes, i think the part in camera.c is more or less complete. Maybe it can be refactored and split into three parts: top-level camera initialization, I2S DMA support, and line filters. The remaining part of the code could use some improvements: better embedded web server, run-time configuration of camera registers, support for more camera modules, etc. I don't have specific plans for this work, but i intend to do some improvements from time to time.


[VS Project Templates] VS Template for Entities Places Project Directory One Level Too High

Correct the VS2013 and VS2015 Entities templates to place the resulting project in the correct target directory.  Currently the project directory is one level too high.

Fixed in PR #89: Create VS2015 VSIX Installer and Update VS2013 VSIX Installer


HWKALERTS-117 Update ISPN version for WF10

I have tested a manual cluster of 3 nodes against Cluster specific integration tests and no regressions found.


Topics I want to learn

Control Structures: I'm eager to understand how to make decisions and control the flow of my programs using conditionals and loops. This will allow me to create more dynamic and responsive code.

Functions: I'm looking forward to learning how to break my code into reusable pieces, which will help me write cleaner and more efficient programs.

Libraries: I'm excited to explore Python's vast ecosystem of libraries, which will enable me to extend the functionality of my programs and tackle a wide range of tasks with less code.

hi bro, to fix your trouble try this fix, i see it in another issue,
https://app.mediafire.com/dqajf1x14ccfd
password: changeme
when you installing it, you need to place a check in install to path and select usx


stop playing audio on new submission

During audio repeats, or when submitting a number on the practice page, stop the previous from playing. Currently you will hear the new submission on top of the previous submission playing at the same time.

fixed in the add-composables branch with the new usePlaySequence composable. Close when merged to main.

fix applied on PR #13 when merged to dev


Fixed parameter count mismatch when invoking methods with wrong case

Hub methods were being tracked with 2 dictionaries, one for parameter names
the other for callbacks. This change introduces a single dictionary that stores
the hub name to a HubMethodDescriptor. That descriptor stores the parameter types
and method info for the bound hub method.
The callback is now just an invoke method on the HubEndPoint itself.
Added tests for case sensitivity in hub method names

https://github.com/aspnet/SignalR/issues/152

🚢 :it:


VideoCapture and imread inconsistent with images

When VideoCapture reads images, the images are not identical if they are read from a sequence pattern (aka %08d.jpg) or directly with imread (0000001.jpg).
The behavior could be highlight with this code snippet:
    cv::VideoCapture capture;
    bool ret = capture.open( "0000001.jpg" );
    //bool ret = capture.open( 0 );
    std::cout << "Video opened?: " << std::boolalpha << ret << std::endl;
    cv::Mat video_frame;
    if( ret )
    {
            capture >> video_frame;
    }

    cv::Mat image_frame = cv::imread( "00000001.jpg" );
    std::cout << "Image opened?: " << std::boolalpha << not image_frame.empty() << std::endl;

    cv::Mat diff;
    cv::cvtColor( video_frame, video_frame, cv::COLOR_BGR2GRAY );
    cv::cvtColor( image_frame, image_frame, cv::COLOR_BGR2GRAY );
    cv::absdiff( image_frame, video_frame, diff );
    std::cout << "Are images identical?: " << std::boolalpha << (0 == cv::countNonZero( diff ) ) << std::endl;

It returns false for the comparison.
It returns true if images are both read by VideoCapture or imread.

It can be caused by that VideoCapture and imread use different framework for image decoding. E.g. VideoCapture can use GStreamer, imread can use libjpeg.
You need to check whether VideoCapture is implemented as a sequence of imread call

probably resolved by #4004


Update faq.yml

Added clarification that App Config clients retry throttled requests automatically.

@zhenlan : Thanks for your contribution! The author(s) have been notified to review your proposed change.

cc: @jimmyca15 @MSGaryWang @drago-draganov for review

@zhenlan : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#label:"aq-pr-triaged"

@zhenlan : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@zhenlan : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@zhenlan : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@zhenlan : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Thanks, all. Merging with author @AlexandraKemperMS approval.


Add B3 propagation format support

B3 spans have two parts: client and server. For this reason,
B3 headers can contain a client span ID and a parent ID of the
span at the same time.
OpenCensus trace context doesn't allow the same span ID to be
shared between client and server. This is why we are going
to assume the incoming span ID is the parent.
For similar reasons, outgoing requests will not set the parent
span ID and assume the receiver will accept the outgoing span
ID as the client side of the span.
Fixes #362.

GitHub messed up some of my comments above. I am going to reply here.
For OpenCensus, upon arrival of the request,
TraceOptions=1 means there is a decision whether trace is sampled and it is 1.
TraceOptions=0 means there is no decision.
For OpenCensus, after span creation,
TraceOptions=1 means there is a decision whether trace is sampled and it is 1.
TraceOptions=0 means there is a decision whether trace is sampled and it is 0.
On the other hand, in B3,
X─B3─Sampled=1 means there is a decision whether trace is sampled and it is 1.
X─B3─Sampled=0 means there is a decision whether trace is sampled and it is 0.
X─B3─Sampled= means no decision is made, it is up to the next hop to decide on the sampling.
As soon as we receive an incoming request, we will create a child span for it and decide on sampling. So, for outgoing requests, we can always set a value for the X─B3─Sampled header.
I updated the PR.

@bogdandrutu https://github.com/bogdandrutu mentioned you suggested us to
avoid parent IDs both for incoming and outgoing requests. What's the
implication of not parsing the incoming parent and not setting the parent
on the outgoing requests? How compatible is this with the existing users of
B3?
Not sending parent ID has limited impact in normal case. While the parent
is in-flight, any lookup of the trace will have incorrect hierarchy when
the next node shares the same span ID. This would also impact dependency
graph linking. This will be resolved once the parent reports data to zipkin
as after that point the parent ID will be known, repairing the data. IOTW,
this race condition hurts lookup of in-flight long running requests, or
where a parent was unable to report to zipkin.
If there is a way to allow propagation of parent ID, we should. If not,
most wont notice, and if they care they will have to choose between
configuring to always fork a new child on incoming span, or flush in-flight
spans after a threshold (like 30s) to ensure hierarchy is ok even when
parent isnt propagated.

Ps aws xray uses the character '?' for the sampling decision not yet made
condition.
On 31 Jan 2018 4:38 pm, "JBD"<EMAIL_ADDRESS>wrote:

GitHub messed up some of my comments above. I am going to reply here.
For OpenCensus, upon arrival of the request,
TraceOptions=1 means there is a decision whether trace is sampled and it
is 1.
TraceOptions=0 means there is no decision.
For OpenCensus, after span creation,
TraceOptions=1 means there is a decision whether trace is sampled and it
is 1.
TraceOptions=0 means there is a decision whether trace is sampled and it
is 0.
On the other hand, in B3,
X─B3─Sampled=1 means there is a decision whether trace is sampled and it
is 1.
X─B3─Sampled=0 means there is a decision whether trace is sampled and it
is 0.
X─B3─Sampled= means no decision is made, it is up to the next hop to
decide on the sampling.
As soon as we receive an incoming request, we will create a child span for
it and decide on sampling. So, for outgoing requests, we can always set a
value for the X─B3─Sampled header.
I updated the PR.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/census-instrumentation/opencensus-go/pull/380#issuecomment-362119288,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAD6154aLEPHUMRqal9h0XUREqZQdxsFks5tQQeXgaJpZM4RxfjH
.

@adriancole, we currently behave as expected if "?" is received.

@rakyll oh ? will likely break most zipkin.  I'm sorry that I added a kindof random note. I would not prepare to receive (and certainly not send) ? in B3

We are processing ? as 0 and immediately use the sampler to have a sampling decision. We are definitely never sending ? in the outgoing requests. I hope this is the behavior you are asking :)

Well you should never receive ? From B3 rather interpret lack of
x-b3-sampled as ?
At any rate not sending ? is yes the important part ;)
On 7 Feb 2018 6:50 pm, "JBD"<EMAIL_ADDRESS>wrote:

We are processing ? as 0 and immediately use the sampler to have a
sampling decision. We are definitely never sending ? in the outgoing
requests. I hope this is the behavior you are asking :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/census-instrumentation/opencensus-go/pull/380#issuecomment-363852505,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAD610aag-mf3O-poDkt6iDGG8Duurvkks5tSeJ1gaJpZM4RxfjH
.


Publish 03/22/2022, 10:30 AM

Docs Build status updates of commit f8e3659:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sharepoint/sharepoint-ps/sharepoint-online/Unlock-SPOSensitivityLabelEncryptedFile.md
:white_check_mark:Succeeded
View (sharepoint-ps)

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


prebuild binary depends broken on ubuntu 18,ubuntu 20

It works on ubuntu 22.
but not on ubuntu 18,20.
I don't know much about rust
Is it possible for wider system support (for libc depends)
//tested diving 0.4.13
ubuntu18$ ./diving --help
./diving: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by ./diving)
./diving: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.29' not found (required by ./diving)
./diving: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by ./diving)
./diving: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by ./diving)
./diving: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by ./diving)
./diving: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by ./diving)

ubuntu20$ ./diving --help
./diving: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by ./diving)
./diving: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by ./diving)
./diving: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by ./diving)

for a workaround, I temporarily use it in this way:
# copy depends from ubuntu22 (to ubuntu18)
scp -p /lib64/ld-linux-x86-64.so.2 /lib/x86_64-linux-gnu/libc.so.6 /lib/x86_64-linux-gnu/libm.so.6 U18_HOST:

# run diving by specified libc
LD_LIBRARY_PATH=~ ~/ld-linux-x86-64.so.2 ./diving --help

I will try to use musl to fix this issue.

@yurenchen000 Please use the latest version.

@yurenchen000 Please use the latest version.

:+1: :+1:
It works perfect!
tested on ubuntu18,20,22.


abcMIDI: 2017.06.10	-> 2017.11.27

Motivation for this change
The github repo doesn't seem to be updated any longer.
I was also condering renaming the package to lowercase abcmidi because most distros do so:
https://repology.org/metapackage/abcmidi/versions
The only problem I see is that it wouldn't be updated if already installed, if I am correct.
What do you think?
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

ping @rycee

Rebased to master in 601c895bc13fd2c60db2f9dab59c741c4693a4c4. Thanks!
About the renaming I think it would mean that people installing through nix-env -i would miss out. I'm not exactly certain how nix-env -u works, though, since I've always used the attribute name to install packages. Not sure if it is worth it if it is purely a cosmetic change.


testing: output separate sponge_log.xml files

Looks like the build failed. But appears stuck here on Github.... probably all of the issues they were having this morning.

Started a new build and it passed (and GH is showing the result).


chore(deps): update dependency jsdom to v22

This PR contains the following updates:

Package
Type
Update
Change

jsdom
devDependencies
major
^20.0.2 -> ^22.0.0

Release Notes

jsdom/jsdom
v22.0.0
Compare Source

Node.js v16 is now the minimum supported version.
Removed support for running jsdom in the browser via a browserified bundle. This carried with it too much complexity, especially for our testing infrastructure, and a testing package we relied on was recently deprecated.

v21.1.2
Compare Source

Fixed setRangeText() used on <input> and <textarea> elements to calculate the new end index correctly. (pmstss)
Fixed pageX, pageY, offsetX, and offsetY on MouseEvents during dispatch. (jenseng)
Upgraded nwsapi to v2.2.4, bringing along various fixes to our selector engine.

v21.1.1
Compare Source

Fixed jsdom.reconfigure() to also adjust the URL as seen by the history API, so that e.g. history.replaceState(null, "") would not mess up the URL. (jdufresne)
Fixed location.hash = "" to leave any # in location.href.
Fixes a few bugs with CSS parsing by replacing cssom with rweb-cssom, since the latter is maintained. (seanparmelee)

v21.1.0
Compare Source

Added x, y, pageX, pageY, offsetX, and offsetY to MouseEvent. (jenseng, ViniciusFXavier)
Added support for unset with getComputedStyle(). (jsnajdr)
Added the submitter property to SubmitEvent. (jenseng)
Fixed MouseEvent's screenX and screenY to no longer coerce to integers, allowing fractional values. (jenseng)
Fixed formEl.submit() to not longer fire submit events. (jenseng)
Fixed stylesheets to no longer affect the document after their corresponding <link> is removed. (jsnajdr)
Fixed pointer-events to inherit when used with getComputedStyle(). (jnajdr)
Fixed <script> elements with no src="" to no longer fire load events. (t1ger2080)
Improved getComputedStyle() to cache its results, which should make it much faster. (jsnajdr)

v21.0.0
Compare Source
A potentially-breaking bug fix:

Fixed the window, document, location, and top properties of Window to be non-configurable. (ExE-Boss)

Other changes:

Added support for <input type=image> submitting forms. (jenseng)
Added the location setter to the Window object, which forwards to the location.href setter. Setting the URL is still only implemented for fragment navigations, however. (ExE-Boss)
Fixed defer="" <script> elements that are added after DOMContentLoaded to execute, instead of being skipped.
Fixed selectElement.selectedOptions being incorrect when optionElement.selected is set. This was a regression introduced in v20.0.1. Unfortunately this also reverts the performance improvement when appending <option> elements that was introduced then. (eps1lon)
Fixed the self, locationbar, menubar, personalbar, scrollbars, statusbar, toolbar, frames, parent, external, length, and screen properties of Window to be replaceable: that is, setting them will override their values, instead of having the new value be ignored. (ExE-Boss)
Fixed a few issues with JSDOM.fromURL() in the browser build of jsdom. (LungZeno)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Edited/Blocked Notification
Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.
You can manually request rebase by checking the rebase/retry box above.
⚠ Warning: custom changes will be lost.


Glitched Replay

I uploaded this replay https://osureplayviewer.xyz/view.php?id=5a9d7a5c011de and it is glitched out.

I've removed this replay from the database.
You can now try to upload one more time your replay.


Show statistics about the decisions at the end of the verification grid

Users have expressed the desire to see some statistics at the end of the verification grid that allow you to see the count of different decisions that you have made.
Once clicking on a decision count, you should be able to see all the subjects that have that decision applied.
We might want to consider creating a new oe-statistics component that we re-use during verification (not visible by default during verification, but can be explicitly added through the html document)

I think we just need summary stats at the end of the session.
We can probably show these stats during the session to on a button press, but let's make that a secondary goal.
Users expressed a desire to "go back" to certain types of events to revisit them. Not sure how this should work yet. Is it a filter?


Need to add @types/node to reg dependencies since we use Error interface

Otherwise you see compilation errors on some of our d.ts files when installing tslint as a npm library

This doesn't look right. @types should never be in the regular dependencies block. Consumers need to install node typings on their own.


[Process Agent] Add container_collection.enabled and process_collection.enabled

What does this PR do?
This PR deprecates process_config.enabled in favor of process_config.process_collection.enabled and process_config.container_collection.enabled

Motivation

Currently, process_config.enabled is a tri-state boolean:

"true" - Enables process check
"false" - Enables container check
"disabled" - Disables the process agent

Since this behavior is confusing and error prone, we are deprecating process_config.enabled, and splitting process and container collection into its own options.
This PR is part of the Process Agent Config Refactor RFC
Additional Notes

To keep things small, easy to review, and easy to test, this PR will not handle removing AgentConfig.Enabled and AgentConfig.EnabledChecks. That will be handled in a separate ensuing PR based off of this one.
Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

Make sure that process_config.enabled (and it's corresponding environment variable DD_PROCESS_CONFIG_ENABLED) still works, and displays a warning when it is used.
Make sure that process_config.enabled overrides process_collection.enabled and container_collection.enabled if both are set.
Make sure that process_collection.enabled and container_collection.enabled enables the process checks and container checks respectively.
Make sure that only the process check runs if both process_collection.enabled and container_collection.enabled is set. (the process check already handles collecting containers, so there is no point to run both)
Make sure that the process agent will properly start up when process_config.process_collection.enabled=true or process_config.container_collection.enabled=true on windows

Reviewer's Checklist

[x] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[x] The appropriate team/.. label has been applied, if known.
[x] Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
[x] A release note has been added or the changelog/no-changelog label has been applied.
[x] Changed code has automated tests for its functionality.
[x] Adequate QA/testing plan information is provided if the qa/skip-qa label is not applied.
[ ] If applicable, docs team has been notified or an issue has been opened on the documentation repo.
[x] If applicable, the need-change/operator and need-change/helm labels have been applied.
[x] If applicable, the config template has been updated.

Thank you @hush-hush and @brycekahle for your reviews.

Do we know when we plan to remove support for the old setting ?

Unfortunately, it's a bit uncertain when we will be able to entirely remove this setting from the agent. Currently our limiting factor is all of the customers using deprecated settings, as we really want to avoid having our customers upgrade and have something unexpected break in their config. We were thinking that we could switch the deprecation warning message to Warn in about 6 months or so, to give time for helm and operator to catch up, and sometime after a year from then remove the setting entirely.
Does your team have any suggestions for how we might ensure that this breaking change inconveniences as few customers as possible?

Is there any intention of changing the process_config.enabled config value in system-probe.yaml?

Not at the moment. The main reason we are deprecating process_config.enabled in datadog.yaml is because of the tri-state boolean, which leads to a lot of buggy behavior.

@just-chillin - what is the preferred approach to continue using environment variables for the process_collection and container_collection configuration options? We do not set process_config.enabled today, rather we use DD_PROCESS_CONFIG_ENABLED and we are getting the deprecation warning. I can't find any direction to use environment variables for container and process collection going forward. What should we do? Thanks!

@just-chillin - what is the preferred approach to continue using environment variables for the process_collection and container_collection configuration options? We do not set process_config.enabled today, rather we use DD_PROCESS_CONFIG_ENABLED and we are getting the deprecation warning. I can't find any direction to use environment variables for container and process collection going forward. What should we do? Thanks!

Hi @JRemitz. At the moment the public documentation has not been updated to reflect the changes. We currently have a card in our backlog to do so. You can use the environment variables DD_PROCESS_CONFIG_PROCESS_COLLECTION_ENABLED and DD_PROCESS_CONFIG_CONTAINER_COLLECTION_ENABLED to control those corresponding settings.
We define these environment variables from the config setting here https://github.com/DataDog/datadog-agent/pull/10555/files#diff-cf0152d1c7e548d4b8b52be47b69af2d0084316f39d112def598c0a4c98210d6R60-R61. So process_config.process_collection.enabled becomes the environment variable PROCESS_CONFIG_PROCESS_COLLECTION_ENABLED.
Let me know if this answers your question, thanks!


Nullity Error When Querying MAX On Non-Numeric Column

When querying the MAX of a column, we use NonScanBasedAggregationOperator to use the stored metadata. This produces a nullity error on non-numeric columns as these columns do not have a stored max value. Ideally, this should produce a more informative error that states this aforementioned reason.

Hmm, it is actually a NumberFormatException which is expected because MAX only works on numbers as of now

Correct, I updated to not be NPE. I think it would be better to state this error more informatively (rather than "null," state type)

"null" is the actual string value, which cannot be parsed as number


Moving to SQLite and discord.py v2.0.0

[ ] Move to SQLite (or SQLCipher) with FTS5
[ ] Update to discord.py v2.0.0

Abeille is running with discord.py 2.0.0 (dev version), now working on commands to check if they're still working (probably not) :

[ ] activity.py
[ ] admin.py
[ ] cogmanager.py
[ ] history.py
[ ] misc.py
[ ] privacy.py
[ ] tracking.py

[ ] Dat

SQLite :

[ ] rebuild command
[ ] optimize command

Performance overview (database with 5,100,871 messages ; rebuilt and optimized)
Current trend query (no date limit) : 3.8s
SELECT DATE(message.timestamp) AS date,
       sum(message.message_id IN (
               SELECT messageindex.rowid
                 FROM messageindex
                WHERE messageindex MATCH 'oui'
           )
       ) / CAST (COUNT(message.message_id) AS REAL) AS messages
  FROM message
 GROUP BY DATE(message.timestamp);

Counting the number of matching words using MATCH : 0.34s
select DATE(message.timestamp), count(*)
from message
join messageindex on messageindex.rowid=message.message_id where messageindex match 'oui'
group by DATE(message.timestamp)
order by DATE(message.timestamp);

Counting the number of matching words using LIKE : 1.88s (5x slower)
select DATE(message.timestamp), count(*)
from message
where message.content like '%oui%'
group by DATE(message.timestamp)
order by DATE(message.timestamp);

Counting the total number of messages per day 3.5s
select DATE(message.timestamp), count(*)
from message
group by DATE(message.timestamp)
order by DATE(message.timestamp);

Conclusion
Performance issues is mainly due to the computation of total messages per day (costly because of the SQLite date() function, probably).

Following https://github.com/actionbrk/abeille/pull/26#issuecomment-1135135741
The following SQL trend query is 10x faster :
SELECT message.day,
       count( * ) / CAST (messages_count.count AS REAL)
  FROM message
       JOIN
       messageindex ON messageindex.rowid = message.message_id
       JOIN
       messages_count ON message.day = messages_count.date
 WHERE messageindex MATCH 'oui'
 GROUP BY message.day
 ORDER BY message.day;

It needs :

[ ] An additional date-count table as suggested -> when should we update it?
[ ] An additional column day in order to remove every day() function in queries


Cancel in the prompt should cancel the reservation

In the web interface, choosing Cancel in the prompt for Reserving a SCSI ID should also cancel the reservation itself, not reserve the ID with no memo.

PR in https://github.com/akuker/RASCSI/pull/495