Explanation of "If you want to use a self-hosted agent, it must be running Windows Server version 1803 or newer."

What is special about self-hosted windows server agents that let them use this functionality?  Is there a limitation that prevents self-hosted linux agents from using it that the microsoft-hosted linux agents seem to get around?

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

ID: 7d1c794c-d676-fc7e-758e-3464f16a1554
Version Independent ID: 941de04a-2d34-ec82-8612-00e4070de673
Content: Service Containers - Azure Pipelines & TFS
Content Source: docs/pipelines/process/service-containers.md
Product: devops
Technology: devops-cicd
GitHub Login: @juliakm
Microsoft Alias: jukullam

@person Thank you for the question, assigning this to the author for review.
For issues that go beyond the scope of the referenced content, feel free to raise the issue with the product team here.
Or, for additional support options, see:

Azure DevOps Support
Azure DevOps on StackOverflow

@Beffyman Windows Server 1803 is no longer supported and this documentation is outdated. Thanks for flagging this! I'll update the docs shortly.


fix(12787): fix 20 qty limit on registered models

fixes: https://issues.redhat.com/browse/RHOAIENG-12787
showing with 26 total.
live

archived

Description
changed model registry list limit (via API call) to 99999 as the default was 20 and when we reached 20 we would not see any new model registries. there is a spike to followup by implementing server side filter/sort/pagination https://issues.redhat.com/browse/RHOAIENG-12800
How Has This Been Tested?
tested locally by adding more than 20 (combo of live and archived) model registries and making sure they are still visible and behavior properly in the table.
Test Impact
updated a test to make sure that the pageSize is included in the call. can't really test beyond that as we mock the data that comes as a response.
Request review criteria:
see more than 20 registered models in the table
Self checklist (all need to be checked):

[x] The developer has manually tested the changes and verified that the changes work
[x] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[x] The developer has added tests or explained why testing cannot be added (unit or cypress tests for related changes)

If you have UI changes:

[x] Included any necessary screenshots or gifs if it was a UI change.
[ ] Included tags to the UX team if it was a UI/UX change.

After the PR is posted & before it merges:

[ ] The developer has tested their solution on a cluster by using the image produced by the PR to main

I thought that we should add this line in all of our api endpoints?

added for artifacts and versions as well

I know I don't qualify yet, but lgtm

@YuliaKrimerman you qualify 😄

/retest


fix: discord link

Fixes: #14

Thanks @shyamtawli for the quick fix.  Appreciate it!

Welcome, anything on the frontend I am happy to learn and fix it.


Feature request: form action customisation

It would be nice to have the possibility to change the email form action to another one (custom form endpoint) than Formspree.
Added in a "general settings" section in the dashboard.
Vapid it's a very nice project, thank you!

@kevinruby Were you thinking about hosting the form processor yourself, or is there a Formspree alternative that you're considering? If it's just a matter of submitting the form to another endpoint, I could see us modifying the form directive, so it accepts an "action" parameter. i.e.,
{{#form action="https://example.com/form_processor"}}
  {{name}}
  {{email}}
  {{message long=true}}
{{/form}}

Also, thanks for the kind words about Vapid! And apologies for the slow reply—I'm on holiday right now, and behind on responding to issues.

@srobbin Hi, I'm thinking about hosting the form processor myself (a NodeJS backend for example). The "action" parameter would be nice and it's the easiest way.
For an alternative, it would be nice that form isn't just used to contact. It would be nice if we can one day to post comment form or anything saved in the DB. But it's an another feature.
Thank you for the answer.

@kevinruby Just issued a PR for this (#72). It'll go out in the next release. Thanks for the feedback and suggestion.


This turns out to be not backwards compatible.

The bot would revert this within 4 hours of merging. It's better to fix the upstream sources that it's checking, in this case the .version file in the download.

K i wasnt sure if it did that, I did update the .version.

Good, in that case the bot would make this change itself eventually. Merging now to speed up the process...


[Maintenance] Missing ALSA_ and SHOUT_ variables in Dockerfile

Those set of variables are just missing from the Dockerfile

Available in release 2023-01-15.1


Remove azure-template releases and tags

It is harder even for me to find 1.0 GA tag, because it is on 5th page.
The same must be for the customers - lots of noise in Releases/Tags: https://github.com/Azure/azure-sdk-for-cpp/releases

@danieljurek  @weshaggard I'm not sure what the practice is for all languages.  Should these be kept if the package isn't published all the way through to vcpkg?
Note, @antkmsft I agree there are lots of entries for template.  However at some point they'll be just as many for all the packages and it becomes just as hard.  Take a cruise through python, .net, java, js, go.  Even if you removed their template packages you'd be hard pressed to find the release b/c there are so many.

As you mention there are tons of tags in most of our repos and we don't treat template special in those cases as the tags all exist.
Unfortunately the github UI for tags is not very good but I think the thing to do here to teach folks how to find tags they are interested via commands like git tag -l azure-identity* that will list just the tags matching the pattern. Assuming they care about the tag at all. They can also use things like our package index at https://azure.github.io/azure-sdk/releases/latest/cpp.html to find the latest.

Our intention is that these template packages follow all the same patterns and rules as other packages.  Any special cases we introduce make them less of a template and therefore less useful when setting up new packages.
Please reactivate if you disagree with this reasoning.


[TC-PWRTL-2.1] only shows up under SDK Python Test under Python Testing Suite - Legacy but Power Topology is a new 1.3 cluster

Please follow the below template to file issues/concerns/feature enhancement against Test Scripts:
Summary Title:
[TC-PWRTL-2.1] only shows up under SDK Python Test under `Python Testing Suite - Legacy` but Power Topology is a new 1.3 cluster

Description:
The test script was hard to find since it only shows up under `Python Testing Suite - Legacy` - we were expecting it to show up under `Python Testing Suite`.

Steps to reproduce:
1. On the test harness  - click on the SDK Python Tests, In the search box type `PWRTL`
2. Observe that the test case is only found if you click on the `Python Testing Suite - Legacy` in the bottom part of the screen

Logs:
N/A
Additional Info:
Note Power Topology Cluster is new cluster in 1.3 -so not expecting this to be under Legacy.

Hi @jamesharrow Legacy suite refers to the test case that are not written in the expected template, even this test being a new one.

@fabiowmm lets re-word the categories to avoid confusion


Dialog out of parent widget context

Dialog have required context parameter (parent widget context)
And we expect this context be available under Dialog widgets.
But parent widget context is NOT available under Dialog widgets. - specially when we using child Router.
And we getting exceptions when tying to access parent widget context data.
It is BLoC's in certain states and other data so we could not just wrap Dialog in the same Inherited Widgets.

this workaround works for some specific cases - but it is not solution for BLoC's and etc:

Hi @zs-dima
Can you please provide your flutter doctor -v a minimal complete reproducible code sample along with the actual vs expected results?
Thank you

Solution quite simple:

@PlugFox @pedromassango thanks for looking into


chore(vc): add validator client keys to the node configuration

Overview
Add a configuration option to the node to run the validator client with its own signing key

closed by #7854


video inside of WebsiteTabs padding fix

Closes #1150
prevent global video rule from affecting videos inside of WebsiteTabs

Hey guys, @shixiedesign is out today so I was looking at this... I just read shixie's issue and don't see the fix:
(also made sure it wasn't a cache issue) Maybe I'm missing something.

I'm also still seeing the issue

Looks like videos in <tab> are fixed! 🎉 Still seeing this issue in videos in <do-dont-example> though.

I have it fixed in the do-dont-examples: https://github.com/carbon-design-system/carbon-website/pull/1166

@shixiedesign this is fixed now inside example components! will be visible when netlify finishes building
@marijohannessen — i have that fix here too, although we've done some different things with the Sass. in this PR i'm putting these overrides inside of _page.scss, alongside the global styles for .gatsby-resp-iframe-wrapper. wondering if you would like to follow this pattern, or if it would be better to follow your lead, and put these overrides for .gatsby-resp-iframe-wrapper inside of each component's Sass file that needs it.
(trying to think of best pattern for future maintainability as folks add new components—i also put up this issue for later discussion when releasing website-addons: https://github.com/carbon-design-system/carbon-website/issues/1167 @alisonjoseph )

@lovemecomputer @marijohannessen I had to create a new <Video/> component in my mdx PR, so eventually we can move styles there


pks hallucinates when used with experimental parser and constants are defined outside of the application

Examples:

Dependency violation: ::String belongs to ., but packs/domain/internal_users/package.yml does not specify a dependency on .

Architecture violation: ::Rails belongs to . (whose layer is application) cannot be accessed from packs/domain/geography (whose layer is domain)

Is this expected behavior? I mean, it is called "experimental".

Hey @exterm , thanks for opening an issue!
TLDR: This means that in the . pack, your application is monkey patching ::String and ::Rails.
Therefore, the experimental parser considers this to be a definition.
This document has all the info about what the experimental parser considers a definition.
https://github.com/alexevanczuk/packs/blob/main/EXPERIMENTAL_PARSER_USAGE.md
If you'd like to ignore this definition, the link above documents the API to do so!

Thanks, will look into it!

Can I somehow have pks output which file it resolved a constant to?

@exterm Definitely. Check out pks list-definitions! It was added for this specific purpose to make it easier to understand how each parser determined where a constant is defined.

Perfect!
After some reflection, it's really interesting to see this behavior. Packwerk doesn't fall for redefinitions / monkeypatching because it resolves constants like zeitwerk loads them, so it always resolves to the "main" definition. Ruby itself doesn't even have a "main" definition, that's pretty much a zeitwerk concept...
I hadn't thought about this before.
I can't currently come up with a way to fix this problem in packs without manual configuration, but I'll think a little more about it.


Enables live region support using internal VS API.

Enables live region support using internal VS API. This should be replaced with proper WPF support when that is added.
Simplifies status display in cookiecutter.
Fixes some missing help text properties.

👍


TrayIcon becomes unresponsive

Describe the bug
I have an application that defines a <TrayIcon> in App.axaml. It has an associated menu. I left it running overnight, and in the morning I found it to be very nearly unresponsive. Right-clicking on it displays the menu -- after a delay of about 25 seconds. I selected an option and several minutes later the application still has not received the associated Command activation. Upon restarting the application, the <TrayIcon> and associated menu are responsive once more.
To Reproduce
I don't have an isolated reproduction at this time. But, if my application is left running for a long time, eventually the behaviour becomes as described.
Expected behavior
The <TrayIcon> and associated menu should remain responsive & functional.
Avalonia version
c71d999
OS
Linux
Additional context
I am running on a C.I. build from PR #16024, because I need the bug fix for TrayIcon menu item crashes.

Fixed by https://github.com/AvaloniaUI/Avalonia/pull/16024

I haven't seen a recurrence of this, but it was originally observed with a C.I. build of #16024, i.e. already with the fix. Hopefully you're right, though, and it's a thing of the past :-) I'll keep an eye out for it.


Overriding tags.html does not output meta content

When I try to override the wagtailmetadata/parts/tags.html template I can display the content of my custom meta tags but all the default tags output content="" or content=" - "
Setup
django 2.0.3
wagtail 2.0
wagtail-metadata 2.0.0

You may need to look at your wagtail page settings, or the settings in your cms admin area. I'm using wagtail 2.10.2 and have overwritten the tags successfully.


Simplify renderHydrogen internal logic

Description
I need to separate RSC from SSR logic for a new RSC<>Vite approach. While doing that, I thought it could be helpful to extract part of the refactoring in this PR.
We had 3 functions that ran RSC independently, and 2 of them did SSR as well: hydrate, render and stream. This PR reduces this to runRSC and runSSR.
For bots, runSSR will buffer the response and transform the HTML. This also applies now when the user calls response.doNotStream().
I thought I had introduced a bug but it seems we already have it in main branch.
Is there anything I've missed? 🤔
Additional context
It might be easier to check the commits 1 by 1.

Before submitting the PR, please make sure you do the following:

[x] Read the Contributing Guidelines
[x] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123)
[ ] Update docs in this repository according to your change
[ ] Run yarn changeset add if this PR cause a version bump based on Keep a Changelog and adheres to Semantic Versioning

@blittle I wonder if these changes now make config#enableStreaming obsolete?
I think one could just do the same thing in App.server.jsx:
export default function App({request, response}) {
  if (request.headers.get('user-agent') === 'custom bot') response.doNotStream();

  return <>...</>
}

Hydrogen would now format the output HTML properly like we used to do in `render`.


add routes json

Add Routes JSON. I think this JSON structure serves the purpose for fetching Routes.

Awesome @naseemshah  Please update the data with the exact data from the excel

@rejahrehim @riginoommen please check the latest commit with the description from sheet.

@rejahrehim  @riginoommen updated illustration img urls with provisional links. @lespaceman will be uploading to the bucket in the given structure.


generic name for AWS provider ServiceAccount to generate IRSA upfront via IaC (for example Terraform)

What problem are you facing?
I am suing Terraform for initial creation of (master) EKS cluster. I noticed that adding AWS proivder the corresponding ServiceAccount is created and uses a random number as a suffix. This make sit impossible to create IRSA upfront,
My workflow is as follows
Terraform:

create cluster
create IRSA related stuff
Fluxv2 bootstrap cluster

Fluxv2

install crossplane via Helm chart via HelmRelease resource
install AWS provider via Kustomization

How could Crossplane help solve your problem?
If we have a hard-coded AWS provider SA name I can create the corresponding IAM role with correct trust policy upfront in Terraform. Then crossplane AWS provider could pickup this IAM role and creates the SA annotating it with the role ARN.

You can set StringLike Wildcard *

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Principal": {
        "Federated": "arn:aws:iam::${AWS_ACCOUNT_ID}:oidc-provider/${OIDC_PROVIDER}"
      },
      "Action": "sts:AssumeRoleWithWebIdentity",
      "Condition": {
        "StringLike": {
          "${OIDC_PROVIDER}:sub": "system:serviceaccount:${SERVICE_ACCOUNT_NAMESPACE}:provider-aws-*"
        }
      }
    }
  ]
}
EOF

Check also our Guide here https://github.com/crossplane/provider-aws/blob/master/AUTHENTICATION.md

@haarchri I have followed the AUTHENTICATION.md and provider-aws-* wildcard doesn't work. I've wasted quite a lot of time on this sadly. I don't use eksctl but have terraform module that all other irsa are generated with. Only setting the exact service account with generation number works otherwise provider-aws is unable to assume the identity. * doesn't work either.

You need to use StringLike

🐼 🤦


feat: model compression draft for review

This draft PR exists for reviewing the complete model compression feature. It and its series of commits are not designed to be merged into main; it comes from a branch that is a mostly-squashed snapshot of the feature.

Regarding the changes to .c and .h files:

Header files

Unit testing framework

Kernel unit tests

Reference kernels

Xtensa kernels

Reference decompression code

Xtensa decompression code

MicroInterpreter/MicroContext compression support

Generic Benchmark application

tensorflow/lite/micro/tools/benchmarking/generic_model_benchmark.cc
tensorflow/lite/micro/tools/benchmarking/metrics.cc
tensorflow/lite/micro/tools/benchmarking/show_meta_data.cc.template

CI test failure due to strict arena size

tensorflow/lite/micro/examples/micro_speech/micro_speech_test.cc
tensorflow/lite/micro/memory_arena_threshold_test.cc

Improved debug output

tensorflow/lite/micro/memory_planner/greedy_memory_planner.cc


Added support for de-referencing arrays

This should fix #331
I haven't added tests or docs yet, as I'm not sure the approach is correct, so I'd appreciate you guys having a look. Seems to work fine on my project with a pretty complex schema.

@glennjones @robmcguinness can you have a quick look at this?

@CatalinMustata a quick way for me to review is to run the test cases. mind adding them?

I will check it.


Task - Collection Object Filter - Data attribute match

Internal attribute matches:

[x] For collection object
[x] For collecting event

On co_filter branch

Duplicate of #1258


Complete gesture dispatch code for web platform

Currently gesture dispatch code is not completed.
Complete the code.

Almost done for touch and normal mouse gesture.
For mouseenter, mouseleave, and mouse move, need to implement OS X like tracking area api.


How to detect whether a parameter is unused via reflection api?

struct Camera
{
    float3 cameraPos;
    float pad0;
    float4x4 cameraTransform;
};

struct Scene
{
    Camera camera;
    StructuredBuffer<float4> vertexBuffers;
    StructuredBuffer<float4> instanceBuffers;
    StructuredBuffer<float4> useless;

    float scale;
    uint pad0;
    uint pad1;
    uint pad2;

    float4 getMagicNumber()
    {
        return instanceBuffers[0] + vertexBuffers[0] + camera.cameraPos.xyzz;
    }
};

Scene gScene;
Texture2D<float4> avatar;
RWTexture2D<float4> gOutput;

[numthreads(16, 16, 1)]
void main(uint3 dispatchThreadId : SV_DispatchThreadID)
{
    gOutput[dispatchThreadId.xy] = gScene.getMagicNumber() + avatar[dispatchThreadId.xy];
}

in gScene, the StructuredBuffer useless is unused. I need to know this via reflection api so that I can create a correct binding layout for DirectX12.

Sorry for the late reply to this issue.
The first thing to say is that Slangs layout is deterministic and depends (largely) on the ordering of declarations within your source file. Slang will keep the same layout even if a binding is not used - this is a design choice. There is more information about this here.
As it stands today there isn't a way to tell if a binding is used or not.
The current technical reason relates to how Slang performs layout - this is something that happens on the AST (Abstract Syntax Tree). The AST representation matches fairly closely to the source code. It doesn't take into account any of the nuance of the transformations that are later made for specific targets. So there is no way to ask the AST what binding is used - as that isn't known until it has been converted into target specific IR.
It would "in principal" be possible to take Slang reflection bindings and see if they used once IR was available for a target. For simple scenarios (like avatar in your example), this might be relatively straight forward. The use within Scene would be more complicated - because the binding isn't just a global variable, its a field of a type that is a global variable. You could imagine more complex binding scenarios again - such as arrays of structs and so forth. Depending on the transformation/s needed for the target, and how it relates back to the original source it could get quite complex.
It could be argued not knowing which bindings are used might leave some performance on the table - if the application knew which bindings were used it could vary what is set. In practice though in most scenarios this seems to be a false economy - as most things most of the time need to be set, and conditionally handling increases code complexity and has performance implications (such as branch prediction).
If you have examples where having this information would remain important for your usage, please let us know.

Yes, now I let unused variables reside in the binding layout, and the program works well. If unified memory or bindless programming model becomes the new trend, this will no longer be a problem.


Tail of SqlTools logs is cut off when the azure data studio exits

Azure Data Studio Version:
Version 1.1.3
Commit 9ca6200018fc206d67a47229f991901a8a453781
Date 2017-12-15T12:00:00.000Z
VS Code 1.26.1
Shell 2.0.9
Renderer 61.0.3163.100
Node 8.9.3
V8: 6.1.534.41
Architecture x64

Steps to Reproduce:

Configure sqltools logging by using the following in your usersettings.
"mssql.tracingLevel": "All",
"mssql.logFilesRemovalLimit": 100,
"mssql.logRetentionMinutes": 60,

Expand some nodes in object explorer and execute a query to generate log entries.

Observe the log entries in output pane (Ctrl-Shift-U) -> Log (SqlTools)

Observed:
The very tail of the log entries is cutoff. The entries at tail do not make it to the log file even upon process exit.
Expected:
While the tail being cutoff is expected due to buffering. This should eventually flush especially on process exit.

Closing older issues that aren't impacting user facing scenarios.


[WIP] - Feature/users and groups UI updates

User and Groups UI

@ShubhamThakre Do you mind posting screenshots here? Thanks!

Hi @jjoyce0510,
Apologies for not sharing the screenshots and other code issues.
The features I am working is still in progress, and @gabe-lyons ask me to raised the PR to follow my code progress.
Thanks for your comments. I will keep those in mind.
here is the short video for current updates, still its not completed and the work in progress.
https://user-images.githubusercontent.com/29713365/150907072-5a6f9d34-47c6-4b47-a0fe-7fe1cfa625e1.mp4


Improve the value of the "documentDescribes" field in a generated SPDX 2.3 SBOM

At the recent SPDX Docfest, it was pointed out that the value we provide in the SPDX 2.3 SBOM for the "documentDescribes" field is a self-reference to the SPDX Document, rather than the subject of the SBOM: SPDXRef-DOCUMENT .
It would be better to provide a filename (possibly even a PURL when available) to identify (describe?) the overall subject of the SBOM.    See attached.

I'm not sure we need to fill out the whole subset of the field, which might be imho redundant with the rest of the SBOM, but a concise "description" value would be nice.

@DennisClark
I've updated the SPDX SBOM generation code to populate the documentDescribes field with the SPDX ID of the Packages and Dependencies found in the codebase.
{
  "spdxVersion": "SPDX-2.3",
  "dataLicense": "CC0-1.0",
  "SPDXID": "SPDXRef-DOCUMENT",
  "name": "scancodeio_asdf",
  "documentNamespace": "https://scancode.io/spdxdocs/077c7103-d683-4f47-b5c3-349ae813cb7f",
  "creationInfo": {
    "created": "2022-12-09T20:10:40Z",
    "creators": [
      "Tool: ScanCode.io-32.0.0"
    ],
    "licenseListVersion": "3.18"
  },
  "packages": [
    {
      "name": "Django",
      "SPDXID": "SPDXRef-scancodeio-discoveredpackage-5286f46a-f62a-4b2e-bcae-282aee7e620e",
      "downloadLocation": "NOASSERTION",
      "licenseConcluded": "NOASSERTION",
      "copyrightText": "NOASSERTION",
      "filesAnalyzed": false,
      "externalRefs": [
        {
          "referenceCategory": "PACKAGE-MANAGER",
          "referenceType": "purl",
          "referenceLocator": "pkg:npm/Django"
        }
      ]
    },
   ...
  ],
  "documentDescribes": [
    "SPDXRef-scancodeio-discoveredpackage-5286f46a-f62a-4b2e-bcae-282aee7e620e",
    "SPDXRef-scancodeio-discoveredpackage-4a76f0fb-f146-4151-b9f7-6997f85204fc",
    "SPDXRef-scancodeio-discovereddependency-pkg:npm/eslint?uuid=aaefa02a-0326-471c-9003-18e0afb0ac34",
    "SPDXRef-scancodeio-discovereddependency-pkg:npm/grunt?uuid=2600e427-07ec-4490-87ca-8b5ddbd5f17e",
    "SPDXRef-scancodeio-discovereddependency-pkg:npm/grunt-cli?uuid=29ff8a00-435e-4ec5-af25-2db1a832bd7f",
    "SPDXRef-scancodeio-discovereddependency-pkg:npm/grunt-contrib-qunit?uuid=47f256ef-4251-45dc-a976-8854c3ba6811",
    "SPDXRef-scancodeio-discovereddependency-pkg:npm/puppeteer?uuid=8e16b4fa-8cf4-49d2-b9f9-361ca3ceb53f",
    "SPDXRef-scancodeio-discovereddependency-pkg:npm/qunit?uuid=fa60f617-27b0-45de-99a5-08600914d297",
    "SPDXRef-scancodeio-discovereddependency-pkg:pypi/argon2-cffi?uuid=b3fa402a-b986-4443-a993-82ed61e1f428",
    "SPDXRef-scancodeio-discovereddependency-pkg:pypi/argon2-cffi?uuid=f4abd865-58dc-4b26-b4bc-001c85c355ed",
    "SPDXRef-scancodeio-discovereddependency-pkg:pypi/asgiref?uuid=ed109be4-8a6c-4904-9e92-9eae2f55dbde",
    "SPDXRef-scancodeio-discovereddependency-pkg:pypi/asgiref?uuid=ce7bff4f-40d5-40f7-88c5-78bd8fecba8d",
    "SPDXRef-scancodeio-discovereddependency-pkg:pypi/backports-zoneinfo?uuid=c60fef1a-030e-42bc-9be2-1ee7915637d3",
    "SPDXRef-scancodeio-discovereddependency-pkg:pypi/backports-zoneinfo?uuid=692e1fb0-fd27-41a0-a990-a0c145e5cdab",
    "SPDXRef-scancodeio-discovereddependency-pkg:pypi/bcrypt?uuid=ec51c3dd-d80d-4a3e-85b8-e273b983033e",
    "SPDXRef-scancodeio-discovereddependency-pkg:pypi/bcrypt?uuid=5cf29eb4-7afb-475d-87d9-9124a4b14a62",
    "SPDXRef-scancodeio-discovereddependency-pkg:pypi/pyenchant?uuid=f8129dd9-d393-462b-8fc7-5fac305d5783",
    "SPDXRef-scancodeio-discovereddependency-pkg:pypi/sphinx?uuid=0dd97a6e-6e59-4733-b415-641687010a6b",
    "SPDXRef-scancodeio-discovereddependency-pkg:pypi/sphinxcontrib-spelling?uuid=0b295eba-a6e1-4058-b6c4-526f705bee4f",
    "SPDXRef-scancodeio-discovereddependency-pkg:pypi/sqlparse?uuid=8fcacf7d-79ba-4658-8963-e00a925a8908",
    "SPDXRef-scancodeio-discovereddependency-pkg:pypi/sqlparse?uuid=15463bb1-35ef-4a08-8e4e-fcca09b64f02",
    "SPDXRef-scancodeio-discovereddependency-pkg:pypi/tzdata?uuid=24724dac-00f4-4979-95ca-fd975855dad3",
    "SPDXRef-scancodeio-discovereddependency-pkg:pypi/tzdata?uuid=c740db9d-d3a8-4406-be3c-b1ba578bb35a"
  ],
  ...

Should we also include the SPDX IDs of the files in the codebase as well? My gut feeling is opposed to it because in the case of my test scan of django 4.1.4, we would have an extra ~9000 lines of SPDX IDs that do not provide additional value.

Hi @JonoYang   You certainly got the "hard part" right, and so you have resolved the issue from a technical point of view, with the SPDX ID for the embedded packages and dependencies, but it would be really nice if you could also provide some text in the first higher level "description" field (see the comments above).  It can be something simple like the name of whatever it was that was scanned.  Unless, of course, I am interpreting the spec incorrectly, in which case what you have done is fine.

@DennisClark
I think the description field is describing the data that should go into the documentDescribes field, rather than it describing the SPDX ID that is going into the field. The other fields in that snippet you posted also shows that the documentDescribes field is an array, where each item in the array is an SPDX ID string.

@JonoYang   OK, you convinced me!

done, merged.


MobileDets backbones

Any plan to add the backbones of these detectors to the model zoo?

@xonobo I looked at this briefly, the mobiledet CPU, GPU and TPU backbone could be added to the efficientnet generator w/ an extra block type (Tucker) and some tweaks, but it doesn't look significantly different from mobilenetv2/v3/mnasnset so I'm not prioritizing it.

With minimal supervision I should be able to work on this.
Please could I work on this?


Give postgres user permissions on auth

In the Supabase Cloud, the postgres role has access to the auth tables too. This PR grants this role the same permissions in this version of the DB.
I know that the roles are much different in general after https://github.com/orgs/supabase/discussions/9314 but I didn't migrate over to the latest role permissions from Supabase, mostly because they seem to be working on an overhaul of role management anyways and there is not enough documentation for me to do it in the time that I have. In any case, I hope that this PR at least offers a way for others who encountered permission issues.

Now, all database users are added.
https://github.com/supabase-community/supabase-on-aws/blob/main/src/supabase-stack.ts#L229-L238
Could you check it, please.


Replace custom fonts with system fonts

Is your feature request related to a problem? Please describe.
Right now, public and apply sites use custom web fonts - 'Nato-sans' and 'montserrat' which add an extra 1.3M download size to the page when loaded initially. It adds to the overall server cost and requires extra bandwidth for the end user.
Moreover,  it causes re-rendering of the page and adds a flickering effect to the site.
Describe the solution you'd like
Replace custom fonts with the fonts available on the user's system. The wagtail site now also uses the system-fonts; this will allow for a consistent look across the site and also a familiar font experience.
Popular websites use System Fonts, including:

GitHub
Ghost
Bootstrap
Booking.com

The new font stack will be, read more at https://flaviocopes.com/css-system-fonts/
-apple-system,BlinkMacSystemFont,Segoe UI,system-ui,Roboto,Helvetica
 Neue,Arial, sans-serif,Apple Color Emoji,Segoe UI Emoji,Segoe UI Symbol,Noto Color Emoji;

Describe alternatives you've considered

Load the fonts over cdn, bandwidth reduction, but not much
Use a JS-based font loader to avoid the flickering effect; display the content only after fonts are loaded.

Additional context
Screenshots from the mac-os rendering:

Priority

Low priority (annoying, would be nice to see)

Affected roles

Staff
Applicants
Reviewers
Partners
Developers
General public

Ideal deadline
ASAP

I believe "system-ui" is safe to use nowadays, https://caniuse.com/font-family-system-ui.

I believe "system-ui" is safe to use nowadays; https://caniuse.com/font-family-system-ui.

Yes. system-ui is supported well. I went ahead with what wagtail has to be safer with people still having an older browser version.
We can upgrade to use system-ui as the first font in the stack, while keeping -apple-system, BlinkMacSystemFont as a fallback.
or another option is to upgrade as the wagtail admin upgrades its font stack.

As discussed over the call, we would keep the 'Nato-sans' and 'montserrat' fonts for the public site.


camel-spring-redis extension

Describe the feature here
Users are asking for camel-spring-redis as a quarkus camel extension

Is it OK to add it in JVM-only extensions at first?

Is it OK to add it in JVM-only extensions at first?

Yeah, lets just make it available for folks to use and worry about native afterwards.


SAADC Implementation

Initial PR for my SAADC work, there are still a few things I need some advice/input on.

Reading VDD (Probably make a unit struct and implement channel for it)
Configuration is currently hardcoded with reasonable values, how should this be configured?
Only a single channel is utilised, and only one AIN can be read at a time, how should multiple be used? What about configurations for multiple values? How will values be returned when the sample task ends?
Calibration is probably not implemented correctly, make it optional when all the channels are known at creation?
Abuse of the Channel trait, any analog input can be connected to any channel's negative or positive side, this isn't well reflected in the current implementation

Squashing all the commits might also be a good idea, I made too many small changes.

There are 25 changed files in this commit, it looks like you have reformatted the existing code too, it is easier to review and if new commits and reformatting is not mixed in the same commit.

There are 25 changed files in this commit, it looks like you have reformatted the existing code too, it is easier to review and if new commits and reformatting is not mixed in the same commit.

Ah, my bad, I've dropped those commits and force pushed. I will address your comments now :)

@jamesmunns Is this what you had in mind for the config?


Add Proposal.

Codecov Report

Merging #58 (aeca269) into main (b7ace21) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #58   +/-   ##
=======================================
  Coverage   80.48%   80.48%
=======================================
  Files           1        1
  Lines         410      410
  Branches       89       89
=======================================
  Hits          330      330
  Misses          4        4
  Partials       76       76

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 b7ace21...aeca269. Read the comment docs.


Is it possible to hook info! etc and send to the console?

I'd like to be able to pipe all the standard bevy output to the console. Is there a way to do that?

Looks like it might be if Bevy provided a way to modify the tracing subscriber. At the moment, the only alternative is to provide a custom tracing subscriber.

It would be nice to have some sort of "hook" or multiple subscribers indeed

Some research here.
Bevy installs a tracing subscriber in bevy::log::LogPlugin. A tracing subscriber consists of layers, each of which get a chance to modify what is traced or how the trace is handled. Bevy's subscriber uses a fmt layer which outputs log Records to stdout. Bevy also uses LogTracer which directs log macros like info! to create tracing Records.
info! -> Record -> fmt Layer -> stdout
I believe tracing only supports one subscriber, so if you want to direct records to the console you need to install a layer. Once the subscriber is set, you can't add a new layer to it.
This means this task decomposes into:
Author a Subscriber & Layer similar to tracing_subscriber::fmt which handles Records for the console.
Modify Bevy to allow for third party layers prior to installation of the global default subscriber.

I had a go at making bevy able to inject extra log layers: https://github.com/bevyengine/bevy/pull/7682
The PR has some issues, because plugin build can't take ownership of their parameters at the moment.
The pr has an example which should get you pretty close to this however.
I'm not currently working on the PR, just thought I'd share if someone wants to pick it up.

While log layer support is being worked on, did anybody manage to at least redirect the regular println! to bevy-console?

FWIW, I think this is possible now.

I investigated this, looks like we're going to need a small adjustment that's in bevy main in order to direct custom subscriber events to the ECS. Then it will be easy to have a system that can scoop this into the console.

I think it is, I got an example working with a custom layer and a buffer resource

Oooo... Do you think you could share the code for it?

Yeah, I will likely put up a PR today


Files in /docs are empty

Please add some blueprint content into https://github.com/finos/software-project-blueprint/tree/main/docs
Take basic content from odp.finos.org

done!


Update sbt-microsites

Codecov Report

Merging #1089 into master will increase coverage by 0.04%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1089      +/-   ##
==========================================
+ Coverage   84.15%   84.19%   +0.04%
==========================================
  Files          76       76
  Lines        2436     2436
  Branches      184      186       +2
==========================================
+ Hits         2050     2051       +1
+ Misses        386      385       -1

Impacted Files
Coverage Δ

...rc/main/scala/io/circe/shapes/SizedInstances.scala
78.57% <0%> (-14.29%)
:arrow_down:

...rc/main/scala/io/circe/numbers/BiggerDecimal.scala
89.75% <0%> (-0.61%)
:arrow_down:

.../core/shared/src/main/scala/io/circe/Decoder.scala
90.53% <0%> (-0.3%)
:arrow_down:

...les/core/shared/src/main/scala/io/circe/Json.scala
79.11% <0%> (+0.63%)
:arrow_up:

...re/shared/src/main/scala/io/circe/JsonNumber.scala
93.75% <0%> (+5%)
:arrow_up:

Continue to review full report at Codecov.

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


deepcopying retinanet fails

🐛 Describe the bug
Deepcoping retinanet fails
from torchvision.models.detection.retinanet import retinanet_resnet50_fpn
from torchvision.models.resnet import ResNet50_Weights
from copy import deepcopy
from torch import nn

class RetinaNet(nn.Module):
    def __init__(self):
        super().__init__()
        self.weights_backbone = ResNet50_Weights.IMAGENET1K_V1
        self.model = retinanet_resnet50_fpn(weights=None, weights_backbone=self.weights_backbone)

if __name__ == '__main__':
    deepcopy(RetinaNet())

Error:
le "/Users/goku/Desktop/work/repos/lightning-bolts/build/tmp2.py", line 15, in <module>
    deepcopy(RetinaNet())
  File "/Users/goku/miniconda3/envs/lit_bolts/lib/python3.9/copy.py", line 172, in deepcopy
    y = _reconstruct(x, memo, *rv)
  File "/Users/goku/miniconda3/envs/lit_bolts/lib/python3.9/copy.py", line 270, in _reconstruct
    state = deepcopy(state, memo)
  File "/Users/goku/miniconda3/envs/lit_bolts/lib/python3.9/copy.py", line 146, in deepcopy
    y = copier(x, memo)
  File "/Users/goku/miniconda3/envs/lit_bolts/lib/python3.9/copy.py", line 230, in _deepcopy_dict
    y[deepcopy(key, memo)] = deepcopy(value, memo)
  File "/Users/goku/miniconda3/envs/lit_bolts/lib/python3.9/copy.py", line 172, in deepcopy
    y = _reconstruct(x, memo, *rv)
  File "/Users/goku/miniconda3/envs/lit_bolts/lib/python3.9/copy.py", line 264, in _reconstruct
    y = func(*args)
  File "/Users/goku/miniconda3/envs/lit_bolts/lib/python3.9/enum.py", line 384, in __call__
    return cls.__new__(cls, value)
  File "/Users/goku/miniconda3/envs/lit_bolts/lib/python3.9/enum.py", line 702, in __new__
    raise ve_exc
ValueError: Weights(url='https://download.pytorch.org/models/resnet50-0676ba61.pth', transforms=functools.partial(<class 'torchvision.transforms._presets.ImageClassification'>, crop_size=224), meta={'min_size': (1, 1), 'categories': ['tench', 'goldfish', 'great white shark', ...}}, '_docs': 'These weights reproduce closely the results of the paper using a simple training recipe.'}) is not a valid ResNet50_Weights

In short this fails:
from copy import deepcopy
from torchvision.models.resnet import ResNet50_Weights

deepcopy(ResNet50_Weights.IMAGENET1K_V1)

Versions
Collecting environment information...
PyTorch version: 1.13.0
Is debug build: False
CUDA used to build PyTorch: None
ROCM used to build PyTorch: N/A

OS: macOS 11.6 (x86_64)
GCC version: Could not collect
Clang version: 13.0.0 (clang-13<IP_ADDRESS>)
CMake version: version 3.21.3
Libc version: N/A

Python version: 3.9.13 (main, Oct 13 2022, 16:12:30)  [Clang 12.0.0 ] (64-
Python platform: macOS-10.16-x86_64-i386-64bit
Is CUDA available: False
CUDA runtime version: No CUDA
CUDA_MODULE_LOADING set to: N/A
GPU models and configuration: No CUDA
Nvidia driver version: No CUDA
cuDNN version: No CUDA
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True

Versions of relevant libraries:
[pip3] numpy==1.23.4
[pip3] pytorch-lightning==1.8.0rc1
[pip3] torch==1.13.0
[pip3] torchmetrics==0.10.1
[pip3] torchvision==0.14.0
[conda] numpy                     1.23.4                   pypi_0    pypi
[conda] pytorch-lightning         1.8.0rc1                 pypi_0    pypi
[conda] torch                     1.13.0                   pypi_0    pypi
[conda] torchmetrics              0.10.1                   pypi_0    pypi
[conda] torchvision               0.14.0                   pypi_0    pypi

@rohitgr7 Thanks for raising this. I think what happens is deepcopy is trying to initialize the ResNet50_Weights enum by passing its value instead of its name. Is there a reason you are saving weights_backbone into the object? You won't be able to change its value after initialization. If it's for informational purposes, you could store its string value.
@pmeier Any idea if we can patch the original _Weights enum classes to handle more gracefully this scenario?

hey @datumbox, thank you for your reply.
this wasn't the actual use case where we got this issue. I just added a simple example to showcase the error.
In Lightning, we use LightningModule, which handles hyper-parameters, so as a user, I can save this as a hparam, but it's not possible right now. Of course, a string is a workaround.

That makes sense. Could you clarify if you are interested in storing the name or the value of the param in your real use-case? Both of the following work but I'm not sure if that's what you want:
from copy import deepcopy
from torchvision.models.resnet import ResNet50_Weights

deepcopy(ResNet50_Weights.IMAGENET1K_V1.value)
deepcopy(ResNet50_Weights.IMAGENET1K_V1.name)

so, we use jsonargparse for our cli and it tries to parse the defaults of the retinanet function, which we reported in https://github.com/omni-us/jsonargparse/issues/187 and got fixed on their side, but then I thought to get the end issue fixed on torchvision side.
The default here is: ResNet50_Weights.IMAGENET1K_V1, which is an enum .
so if deepcoping these enums is not possible, maybe change the default in the retinanet function to ResNet50_Weights.IMAGENET1K_V1.name? Atleast that will solve my issue partially. But again making then deepcopyable should be the actual fix.

@rohitgr7 Thanks for the clarifications. Let me sync with @pmeier when he is back to see what's the best option here.


Add digital cinema colorspaces to video Flow schema

A request was made via the AMWA Basecamp to add support to signal digital cinema colorspaces (ACES) in https://github.com/AMWA-TV/nmos-discovery-registration/blob/master/APIs/schemas/flow_video.json. At present only ITU colorspaces (starting BT...) are included.
The likely additions would be:
ST2065-1, ST2065-3, DCI-D65, DCI-D60

Schemas have been relaxed for this in v1.3-dev. Agreed values for these types could be defined in the parameter registers as a result.

I think this may be covered by reference to ST 2110-20 in the permitted values of colorspace in the Flow Attributes parameter register.


workflows.argoproj.io  is forbidden

kale: v0.7.0
kubeflow: v1.3
Run pipeline example from candies_sharing.ipynb
But got error:
Traceback (most recent call last):
  File "<string>", line 48, in <module>
  File "<string>", line 7, in sack
  File "/usr/local/lib/python3.6/dist-packages/kale/common/mlmdutils.py", line 533, in init_metadata
    mlmd_instance = MLMetadata()
  File "/usr/local/lib/python3.6/dist-packages/kale/common/mlmdutils.py", line 109, in __init__
    self.pod_namespace)
  File "/usr/local/lib/python3.6/dist-packages/kale/common/workflowutils.py", line 73, in get_workflow
    ARGO_WORKFLOWS_PLURAL, name)
  File "/usr/local/lib/python3.6/dist-packages/kubernetes/client/apis/custom_objects_api.py", line 931, in get_namespaced_custom_object
    (data) = self.get_namespaced_custom_object_with_http_info(group, version, namespace, plural, name, **kwargs)
  File "/usr/local/lib/python3.6/dist-packages/kubernetes/client/apis/custom_objects_api.py", line 1031, in get_namespaced_custom_object_with_http_info
    collection_formats=collection_formats)
  File "/usr/local/lib/python3.6/dist-packages/kubernetes/client/api_client.py", line 334, in call_api
    _return_http_data_only, collection_formats, _preload_content, _request_timeout)
  File "/usr/local/lib/python3.6/dist-packages/kubernetes/client/api_client.py", line 168, in __call_api
    _request_timeout=_request_timeout)
  File "/usr/local/lib/python3.6/dist-packages/kubernetes/client/api_client.py", line 355, in request
    headers=headers)
  File "/usr/local/lib/python3.6/dist-packages/kubernetes/client/rest.py", line 231, in GET
    query_params=query_params)
  File "/usr/local/lib/python3.6/dist-packages/kubernetes/client/rest.py", line 222, in request
    raise ApiException(http_resp=r)
kubernetes.client.rest.ApiException: (403)
Reason: Forbidden

HTTP response headers: HTTPHeaderDict({'Cache-Control': 'no-cache, private', 'Content-Type': 'application/json', 'X-Content-Type-Options': 'nosniff', 'Date': 'Mon, 31 May 2021 07:23:24 GMT', 'Content-Length': '441'})

HTTP response body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"workflows.argoproj.io \"candies-sharing-szcfg\" is forbidden: User \"system:serviceaccount:kubeflow-user-example-com:default-editor\" cannot get resource \"workflows\" in API group \"argoproj.io\" in the namespace \"kubeflow-user-example-com\"","reason":"Forbidden","details":{"name":"candies-sharing-szcfg","group":"argoproj.io","kind":"workflows"},"code":403}

Looks like permission is forbidden of  Custom Resource workflows  and API group argoproj.io .
Does anyone have any idea ?

Hi @dommgifer,
The steps need permissions to get their workflow. Try updating the permissions of the service account default-editor (that's the one your pods use) accordingly.

Hi @dommgifer,
The steps need permissions to get their workflow. Try updating the permissions of the service account default-editor (that's the one your pods use) accordingly.

@elikatsis Hi, I'm not familiar with K8s. Could you kindly specify how to update default-editor 's permissions?

@dommgifer @elikatsis @fengredrum I'm having the same issue using KFP 1.7: https://github.com/kubeflow-kale/kale/issues/367

This can be solved by first creating a Role that allows access to the apigroup and then assigning the role to the default-editor serviceaccount:
---
apiVersion: rbac.authorization.k8s.io/v1
kind: Role
metadata:
  name: workflow-role-kale-ns
rules:
- apiGroups: ["argoproj.io"]
  resources: ["pods", "workflows"]
  verbs: ["get", "watch", "patch"]

---

apiVersion: rbac.authorization.k8s.io/v1
# This role binding allows "jane" to read pods in the "default" namespace.
# You need to already have a Role named "pod-reader" in that namespace.
kind: RoleBinding
metadata:
  name: kale-ns
  namespace: YOUR-NS-HERE
subjects:
- kind: ServiceAccount
  name: default-editor

roleRef:
  # "roleRef" specifies the binding to a Role / ClusterRole
  kind: Role #this must be Role or ClusterRole
  name: workflow-role-kale-ns # this must match the name of the Role or ClusterRole you wish to bind to
  apiGroup: rbac.authorization.k8s.io

---

I faced the same problem. Have you fix this yet? @dommgifer


Unclear that 'update' only touches Lambda code, not API Gateway Routes

I've setup the following routes
@app.route('/', methods=['GET'])
def api_root():
    data = {
        'hello': 'root'
    }
    json_data = json.dumps(data)
    resp = Response(json_data, status=200, mimetype='application/json')
    return resp

@app.route('/hello', methods=['GET'])
def hello():
    data = {
        'hello': 'world'
    }
    json_data = json.dumps(data)
    resp = Response(json_data, status=200, mimetype='application/json')
    return resp

@app.route('/hello/<name>', methods=['GET'])
def hello_name(name):
    data = {
        'hello': name
    }
    json_data = json.dumps(data)
    resp = Response(json_data, status=200, mimetype='application/json')

    return resp

This produces the following in API Gateway

This / and /hello routes works just fine, but when I hit /hello/myname, I get a 404 testing it out. I tested it straight in AWS console. When I run the Flask app locally om my machine, the /hello/myname route works.
Execution log for request test-request
Tue Jul 19 11:15:07 UTC 2016 : Starting execution for request: test-invoke-request
Tue Jul 19 11:15:07 UTC 2016 : HTTP Method: GET, Resource Path: /{parameter_1}
Tue Jul 19 11:15:07 UTC 2016 : Method request path: {parameter_1=myname}
Tue Jul 19 11:15:07 UTC 2016 : Method request query string: {}
Tue Jul 19 11:15:07 UTC 2016 : Method request headers: {}
Tue Jul 19 11:15:07 UTC 2016 : Method request body before transformations: null
Tue Jul 19 11:15:07 UTC 2016 : Endpoint request URI: https://lambda.eu-west-1.amazonaws.com/2015-03-31/functions/arn:aws:lambda:eu-west-1:551002378602:function:dev-bjorn-api-zappa-test-flask-app-dev-api/invocations
Tue Jul 19 11:15:07 UTC 2016 : Endpoint request headers: {x-amzn-lambda-integration-tag=test-request, Authorization=*******************************************************************************************************************************************************************************************************************************************************************************************************55532f, X-Amz-Date=20160719T111507Z, x-amzn-apigateway-api-id=jgqkdnvp4m, Accept=application/json, User-Agent=AmazonAPIGateway_jgqkdnvp4m, X-Amz-Security-Token=AgoGb3JpZ2luELf//////////wEaCWV1LXdlc3QtMSKAApRj/inYf+zQL8eBgc/ZPRg8/A4h1TY+5d0gowys57PHIZOr/vsDMxVrc1ozR/2nHVykc0GFNLePqcOoxXOaTRj07nJzIG73JidN1LImHLe8uWF7SBIMI7GjPjuEkmQUNe8ihY+2VSspnp9duKqdzPfSfzdnN6qBToVutWz1oifmNHjaIAhYvU5khqtGwejQ3I/mHg0pXF5nBZjv1hBlFBI5Wv48YNTHS7nKpWAfnzKStSFv2gVT1zg8iciRHvdypXQ1XyqXBp+H/e0Gokvlr799xrCv7ZcJWNKWsEGguSZFZ0FjntCqD4Wt1TNf1gelHXjQMv5vCMdrzStON5WtjvEq8QII7P//////////ARAAGgw1NTEwMDIzNzg2MDIiDOt1ZtvrBXeHKMhLdirFAj0z5B6oP8ZMmCFWWtuyaxpUJCI/Wy3bH9Gt [TRUNCATED]
Tue Jul 19 11:15:07 UTC 2016 : Endpoint request body after transformations: {
  "body" : "e30=",
  "headers": {
      },
  "method": "GET",
  "params": {
        "parameter_1": "myname"
      },
  "query": {
      }
}
Tue Jul 19 11:15:07 UTC 2016 : Endpoint response body before transformations: {"stackTrace": [["/var/task/handler.py", 249, "lambda_handler", "return LambdaHandler.lambda_handler(event, context)"], ["/var/task/handler.py", 107, "lambda_handler", "return cls().handler(event, context)"], ["/var/task/handler.py", 224, "handler", "raise e"]], "errorType": "LambdaException", "errorMessage": "PCFET0NUWVBFIGh0bWw+NDA0PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDMuMiBGaW5hbC8vRU4iPgo8dGl0bGU+NDA0IE5vdCBGb3VuZDwvdGl0bGU+CjxoMT5Ob3QgRm91bmQ8L2gxPgo8cD5UaGUgcmVxdWVzdGVkIFVSTCB3YXMgbm90IGZvdW5kIG9uIHRoZSBzZXJ2ZXIuICBJZiB5b3UgZW50ZXJlZCB0aGUgVVJMIG1hbnVhbGx5IHBsZWFzZSBjaGVjayB5b3VyIHNwZWxsaW5nIGFuZCB0cnkgYWdhaW4uPC9wPgo="}
Tue Jul 19 11:15:07 UTC 2016 : Endpoint response headers: {x-amzn-Remapped-Content-Length=0, x-amzn-RequestId=0cf54540-4da2-11e6-8932-074ba4f5559e, Connection=keep-alive, Content-Length=650, X-Amz-Function-Error=Unhandled, Date=Tue, 19 Jul 2016 11:15:07 GMT, Content-Type=application/json}
Tue Jul 19 11:15:07 UTC 2016 : Method response body after transformations: <!DOCTYPE html>404<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<title>404 Not Found</title>

Not Found

The requested URL was not found on the server.  If you entered the URL manually please check your spelling and try again.

Tue Jul 19 11:15:07 UTC 2016 : Method response headers: {X-Frame-Options=, Status=, Set-Cookie=, Content-Type=, Location=}
Tue Jul 19 11:15:07 UTC 2016 : Successfully completed execution
Tue Jul 19 11:15:07 UTC 2016 : Method completed with status: 404

Hi, have you tried to increase parameter_depth? I guess that parameter_depth: 3 should be fine.

I'm testing quickly @jotes. I'll get back to you soon

@jotes I changed the parameter_depth and ran zappa update. It didn't work and found that the update command only touches the actual lambda function itself and not API Gateway routes too. https://github.com/Miserlou/Zappa/blob/master/zappa/cli.py#L238. I had to undeploy and redeploy with the new parameter settings. Of course, this worked because the deploy function creates the API Gateway routes https://github.com/Miserlou/Zappa/blob/master/zappa/cli.py#L171.
With this discovery, I found the answer to an earlier question #187 I posted

@bjorntheart so, in the end you changed parameter_depth to 3 and everything works, am I right?

Yes

Is there an interface/behavior that needs to change with this bug? Or can it be marked as resolved?
It's hard for us to detect changes to API GW without holding a bunch of local state, so marking the difference between 'deploy' and 'update' might be a documentation bug?

Here is the behaviour I expect that would make sense to me.

zappa deploy myapp - Flask

add new route in myapp /hello/something

@api.route('/hello/something')
def hello_something():
    pass

zappa update myapp - Currently Zappa updates my function, but leaves the API GW routes untouched and out of sync with the routes in my Flask code. I desire the API GW routes to be updated with the new route. That way we kKeep the routes in the function in sync with API GW routes. Maybe we recreate the API GW routes here when issuing a zappa update. One thing to note though is the API GW endpoint_url has to remain the same to not break DNS configuration with the endpoint_url.
curl http://endpoint_url/hello/something

This ticket is no longer relevant, as update now updates APIGW as well.

@Miserlou: I was surprised to see you say update now updates APIGW as well. Does that mean that the current documentation for update is out-of-date?

This creates a new archive, uploads it to S3 and updates the Lambda function to use the new code, but doesn't touch the API Gateway routes.


Context Needed - Join the Domain

Some context is needed in the section of the article "Join the Domain".
"Remotely connect to the virtual machine using the BUILTIN\DomainAdmin account." <-- this does not have any instructions on how to or setup of the Builtin\DomainAdmin account.

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

ID: 9efea3fe-99fe-4559-3d4b-5cf6aa53614e
Version Independent ID: 27bf731e-0e5f-fe30-69aa-7dec7684a8df
Content: Tutorial: Prerequisites for a single-subnet availability group - SQL Server on Azure VMs
Content Source: azure-sql/virtual-machines/windows/availability-group-manually-configure-prerequisites-tutorial-single-subnet.md
Service: virtual-machines-sql
Sub-service: hadr
GitHub Login: @tarynpratt
Microsoft Alias: tarynpratt

@PrometheusRising1
Thanks for your feedback! We will investigate and update as appropriate.

@PrometheusRising1
I'm going to assign this to the document author so they can take a look at it accordingly.
@tarynpratt
Can you please check and add your comments on this doc update request as applicable.


Transact rewrite

@rnewman okay, first commit here is ready for first review.  Still lots to do, but it's a start.  I'm happy to land something like this as a first step, mostly so you can use the bits here to generate test data; or I'm happy to build it up further before landing.
Some of the stuff I'll be working on next, some of which are noted with TODOs:

[ ] Implement parts, or revert to DataScript-like negative integers.
[ ] Persist idents, parts, entity id counters, transaction indices in SQLite.
[ ] Implement :db/value type checks throughout.
[ ] Implement lookup refs for real.
[ ] Finish implementing map properties (reverse refs, sequential values, etc).
[ ] Set :db/txInstant correctly; ensure tx timestamps are reasonable.
[ ] Work out the story around using #dm/id[:db.part/tx] to refer to the current transaction, or revert to DataScript-like ":db/currentTx".

One thing I wanted to note, before even getting to the PR: the clock for txInstant and otherwise should be an input to the system. Needed for testing/mocking/smart drift handling/etc.

One thing I wanted to note, before even getting to the PR: the clock for txInstant and otherwise should be an input to the system. Needed for testing/mocking/smart drift handling/etc.

I concur.  One way this could be handled is to allow setting :db/txInstant directly; alternately, we supply a clock (which I've stubbed in for now).

Wow, there's a lot of code here. Lots of TODOs, too. Happy for this to land in-tree and iterate there. Nice.

(Also that was a super-skim review 'cos I'm heading afk. More thoroughness next week.)

I pushed this to https://github.com/ncalexan/datomish/tree/master; we'll keep working there.

To summarize:

Implement parts, or revert to DataScript-like negative integers.

This isn't done.

Persist idents, parts, entity id counters, transaction indices in SQLite.

Idents and transaction indices are done; entity IDs are not done (those are under the banner of parts above).

Implement :db/value type checks throughout.

Done!

Implement lookup refs for real.

Not done.  This is somewhat orthogonal to the rest of the work; it's a nice to have.

Finish implementing map properties (reverse refs, sequential values, etc).

Done!

Set :db/txInstant correctly; ensure tx timestamps are reasonable.

Done.

Work out the story around using #dm/id[:db.part/tx] to refer to the current transaction, or revert to DataScript-like ":db/currentTx".

I ended doing a DS-like :db/tx rather than copy Datomic's :db.part/tx, which seemed to me very inconsistent.


Feature Request: Enable Disabling Linters via Source

SCSS-lint has the ability to disable the linters within the source files
https://github.com/brigade/scss-lint#disabling-linters-via-source
This is unfortunately important for my project's workflow :)

I'm sorry to hear that :stuck_out_tongue_closed_eyes:
This isn't a high priority at the moment with a slew of rules that need to be written and some bugs to be squashed, but I'd be happy to take a PR for it. I'd expect the abstraction for determining if a rule should be enabled/disabled to live in helpers

Yeah, this would be hugely useful for the large project I'm working on. We've only recently started linting our scss files (I know!) and we've been using scss-lint, peppering all of our current files with overrides to get them to pass for now (as described by mherchel above).
As we're moving from scss-lint to sass-lint (ditching as much ruby stuff as possible), it would be great to have this functionality. Otherwise I can see needing to create multiple rulesets for different sets of files (being loose with everything already in production and tight with all new stuff).
I think there's going to be a bit move away from all the ruby based stuff (ruby-sass, compass, scss-lint, etc.), so this will be more and more of a 'requirement' for folks to ease the transition.
So, +1 from me!

This is definitely something that should be saved for when we majorly restructure the code to perform a single traversal of the AST (see #5)

Also, useful if you want people to use this package while gonzales-pe is trying to figure out how to solve #321 without having to ignore the whole file. I have the same issue using other tools that rely on it, but they provide a way to disable/enable sections of the source code. I've been waiting for interpolation to be fixed in gonzales-pe for a while.

I'm afraid this wouldn't solve that problem @ctumolosus. The issue is is that even with this feature gonzales-pe would still throw an error on interpolated code even if it was set to be ignored.  The way you are looking at this working to ignore interpolation would actually need to be a gonzales-pe feature to ignore code as it parses it.

FWIW, I'm another sass-lint user in desperate need of this feature.
Glad to see it's being worked on / considered.

:+1:, currently needing to manually comment out lines with !important flags in order to run linter, which is a blocker for integrating it fully into pre-commit hooks + build scripts

I'm waiting this feature desperately too. I can help testing :)

Big +1 for this. Also willing to help with the implementation if steered into the right direction

I'm working on this today, should have a pull by 5pm MST

Ha, i've been working on this too, had a few bits working but the amount of tests needed here will be quite extensive and also some of the line numbers seem to cause issues also.

Get talking guys! We don't want any wasted effort 😛

So the way i was approaching it was to have a rule setup similar to the comments rule, it would make a note of which context to ignore and keep a copy of the line number and then before the results are output it would filter through the results object and remove any of the results that matched those from the ignore rule.
It was also taking into account enabling and disabling rules between two blocks such as with scss-lint which worked the same way essentially as above but the different contexts were tough to get exactly right.

Happy for you to carry on with this if you can though as I've not had the time recently.

What do you think of https://github.com/donabrams/sass-lint/blob/feature/toggle-rules-in-src/docs/options/toggle-rules-in-src.md and https://github.com/donabrams/sass-lint/blob/feature/toggle-rules-in-src/docs/rules/doc-disabled-rules.md ?

I like the extra rule there to enforce the use of documented comments with them. As for the implementation this exactly matches the way scss-lint handles it right?

The approach I have definitely relies on correct line numbers to be reported from rules (I'm sure a bunch of bugs will follow).
I deviated from scss-lint's approach by allowing per-line (like eslint) and making the block syntax more explicit.
Gist of approach: run a rule that returns a mapping of where rules are disabled (both globally and per rule). Filter the results for each "file" via that mapping.

Pretty much how I had it yes, I tell you what, lets have a specific feature branch here, I'll create a new branch off of develop for this in the main repo, we should then branch off of that, we can then give this a bit of collaborative testing and tweaking and keep it up to date with develop without directly relying on it. That ok with you?

Maybe with this much developer attention on this issue, now is the time to move to the single-traversal approach to our core functionality.
I'm not sure how you could disable certain rules on certain lines right now without modifying all rules to check for comments or having to process all lint warnings after all the rules have run. If we perform a single traversal like eslint, we can simply track which rules are enabled and disabled as we traverse.

Ok branch off of this branch feature/disable-lintershttps://github.com/sasstools/sass-lint/tree/feature/disable-linters rather than develop.

I was hoping to have this by next Wednesday (linting cleanup "party" for the team). Obviously not a reason to rush something nasty, but what's the scope here? The only scope I'm worrying about not being able to get done is making sure existing rules return the right line numbers for start/end.

@benthemonkey I'd keep this feature independent of rules. Just work off of results the rules return. Not the most optimal performance, but we def don't want to make writing rules any harder.

@donabrams & @benthemonkey agreed, filtering results for now will provide the most straightforward way here. For 2.0 I know @Snugug is keen to refactor all of the rules to allow a more eslint style way of having pluggable rules etc, this will then be able to hook into this disabling linters functionality which will become a core method really.. We should hold back on the single traversal until we reach that point I think as we'll be doubling our work otherwise.
If we submit PR's into that feature branch I set up then we'll be able to work collaboratively on this and everyone will be able to chip in with tests issues and examples while allowing us to move forward with our current release pipeline.

OK, so verifying existing rules is in scope for this branch to be integrated?

I honestly don't think the refactor to single-traversal is particularly difficult. Instead of calls to "traverseByType" in each rule, we specify which nodes we'd like to hook into and the core code does one call to "traverse", checking for comments and calling rule files as it goes. I honestly think that it would take as long to move to single traversal AND add disabling linters via comments then to write a version of disabling linters via comments that works with the existing core. Just my thought.

If it's crucial to the implementation you've started then yes, if however the line numbers are purely an AST problem then no.
I'm not sure there's issues with line numbers in any rule except indentation which I'm not too fussed about right now while we wait for a stable new version of the AST to release.
@benthemonkey that's a significant change in functionality though, i agree it's probably not a massive change but it's one we don't want to take lightly and would rather we all agree on a way forward for it rather than it get tackled individually we want to make sure our move to pluggable rules and a custom API for distributable rule modules is taken into account.

OK, thats sounds fine then. I'll help review your code code and tests. I would be interested to know what the timeline is for eventually getting to single traversal though... @Snugug is there a roadmap to 2.0?

Lets open a separate issue up for 2.0 discussion.

I like the approach @donabrams is taking and am confident it will work with both the multi traversal we have now and the future single traversal.
Single pass is something we're waiting to implement for 2.0 and should not be part of this PR. Each PR should solve a single issue.
2.0 roadmap can be tracked in https://github.com/sasstools/sass-lint/issues/400

What is the status of this issue? Is the temporary enabling and disabling of specific rules only going to be addressed in 2.0 or will this feature land in 1.x at some point in the near future?

It's under way in #402 just haven't had the time to get round to it recently

Great news, thanks for the update. Appreciate all the work that's going into this. Thanks for everyones work on this great tool :+1:

Hey, so finally have time to finish this feature. What needs to be done to close this up?

Hey @donabrams There's been some big AST changes so it looks like we just need to go through and check everything again, Sass format should now be a bit more stable with its interpretations of blocks so once that format is working correctly we can review what's been done. I intended to get a bit of extra work done on this recently but as usual time is swallowed up elsewhere.
I merged all of your existing progress into our disable linters branch and opened up #677 into develop to keep the progress in check. So all new PR's should be opened into the disable-linters branch and this will update accordingly.

+1. Excited to switch over to this linter in the near future but this issue is blocking for our team. Thanks for all the hard work.

Hey guys,
I'm running<EMAIL_ADDRESS>and linter toggle via comment doesn't seem to be working. I've gone through the issues and pull requests and I cannot tell whether it's been implemented or still WIP?
Could someone please let me know?
Thanks! 👍

It's not been released yet, still WIP in #677 hoping to find some time soon to look into it...

@DanPurdy ok thanks

See [http://stackoverflow.com/questions/35136098/have-sass-lint-ignore-a-certain-line] for a thread on this as well
For me, I need to import Google Material Design icons, but the documented css logic causes no-duplicate-properties and no-vendor-prefixes to fire. I therefore want to keep those rules for every other file in my tree except my font.scss file
// http://google.github.io/material-design-icons/
@font-face {
  font-family: 'Material Icons';
  font-style: normal;
  font-weight: 400;
  src: url('~material-design-icons/iconfont/MaterialIcons-Regular.eot'); // IE
  src: local('Material Icons'),
  local('MaterialIcons-Regular'),
  url('~material-design-icons/iconfont/MaterialIcons-Regular.woff2') format('woff2'),
  url('~material-design-icons/iconfont/MaterialIcons-Regular.woff') format('woff'),
  url('~material-design-icons/iconfont/MaterialIcons-Regular.ttf') format('truetype');
}

.material-icons {
  // Firefox
  -moz-osx-font-smoothing: grayscale;
  // WebKit
  -webkit-font-smoothing: antialiased;
  direction: ltr;
   ...
}

Hi guys, this issue seems to have a long story behind and it does not look like it will be fixed in the closest future.
Is there a way to use a beta / alpha / whatever version? I would be totally fine with that.

+1 for this feature!

@jackblackCH please see #677 should be available in the next release
@smnbbrv if you want to point your package file at the branch in #677 you can use this functionality right now and we'd appreciate the testing feedback also.


Fix IntelliJ IDEA inspection warnings

Fixed various inspection warnings which showed up since we updated our
inspection profile.
Notable changes:

Fixed mismatching number of arguments for some log messages
Added missing @Nullable annotations

Given this is of mostly mechanical changes and thus will be very tedious to review. I'll merge this once CI passes.


⚠ Bofrost.lu has degraded performance

In 6f5cd20, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 2164 ms

Resolved: Bofrost.lu performance has improved in 66fdc11 after 1 hour, 23 minutes.


feat: Add support for Blake2b/2s/3 hash functions

This is a result of this Twitter discussion: https://twitter.com/hdevalence/status/1715765138547212689

Specifically what is your use case for adding blake3? As you say, there's no official support in golang right now. This would mean that any chain using blake3 for its tree will not be able to connect to a cosmos-sdk chain, since we will use the go package of ICS23 that doesn't support this hash function. Seems strange to add a hash function that is incompatible with the vast majority of deployed ibc chains

@AdityaSripal This is true. There are two options: 1) use one of the unofficial Go implementations, or 2) create a Wasm light client based on the Rust ICS-23. In fact I'm now leaning towards a Wasm client that uses a custom proof format, so whether this PR gets accepted will not impact my project. Your call.

@AdityaSripal This is true. There are two options: 1) use one of the unofficial Go implementations, or 2) create a Wasm light client based on the Rust ICS-23. In fact I'm now leaning towards a Wasm client that uses a custom proof format, so whether this PR gets accepted will not impact my project. Your call.

I messaged our Golang cryptography expert and this is what he says:

There's little appetite for adding BLAKE3 to the standard library (x/crypto or otherwise) as of now, because it's not needed by anything else in the stdlib, it's not trivial to maintain, it needs to be heavily optimized (because why use BLAKE3 otherwise), and there are good 3rd party modules for it. I have not reviewed it extensively, but lukechampine.com/blake3 is by a known author, looks well maintained, and its use of Avo, its tests, and its API are reassuring.

So we could the implementation that he recommends. What do you think, @AdityaSripal?

Hey guys, just want to clarify that I'm now leaning towards using my own custom proof format + Wasm light client. So, if you don't feel like supporting Blake in this implementation for any reason, it will not impact my project.

I think i'd prefer not supporting blake3 in go until its official. I think requiring golang chains to use wasm light clients if they need to connect to a state tree that uses blake3 is acceptable.
@larry0x is there a reason you want to go with a custom proof format over ICS23 beyond the fact this isn't released yet?

is there a reason you want to go with a custom proof format over ICS23 beyond the fact this isn't released yet?

For my case a custom proof format can be more compact and probably cheaper to run, especially when it comes to non-existent proofs, because my tree is a radix tree, I only need to show that a node doesn't have a certain children, I don't need to show that two siblings both exist as is how ICS23 works. @AdityaSripal

The Rust code looks good to me. Thanks for adding tests @crodriguezvega! 🙏


local.adguard.org problem when cached with ServiceWorker

local.adguard.org points to non-working IP, as designed.
However, caching by ServiceWorkers are problem in this case, because when AdGuard protection is off, such sites can load infinitely, waiting for local.adguard.org.
We should detect this situation and add some hooks to prevent content with local.adguard.org from caching.

We're going to change the way local.adguard.org works and make it reset connection instead of dropping packets. It should help.

This one is resolved, it now resets the connection


remove definer from mysqldump so that no errors can occur

Possible solutions:
https://stackoverflow.com/questions/9446783/remove-definer-clause-from-mysql-dumps
possible add this into the sync command:
sed -i 's/DEFINER=[^*]*\*/\*/g' mydump.sql

Is already implemented. Here an example:
$globalConfig->addAppInstance('staging', 'host', '/the-path/')
    ->setCompressions(new GzipCompression())
    ->addDatabase('app', 'db', 'root', 'root', 'phpsu_mysql_1')
    ->setRemoveDefinerFromDump(true)
    ->executeInDocker(true)
;

As reference see: PHPSu\Command\DatabaseCommand:387

@ChrisB9 so you have an Problem If we enablebit by Default?

That sounds like a breaking-ish change to me. I don't mind enabling it by default but I have no idea whether it will cause no harm


Missing Type Annotations

There are missing type annotations for some functions in this library.
The typing module does not exist on CircuitPython devices so the import needs to be wrapped in try/except to catch the error for missing import. There is an example of how that is done here:
try:
    from typing import List, Tuple
except ImportError:
    pass

Once imported the typing annotations for the argument type(s), and return type(s) can be added to the function signature. Here is an example of a function that has had this done already:
def wrap_text_to_pixels(
    string: str, max_width: int, font=None, indent0: str = "", indent1: str = ""
) -> List[str]:

If you are new to Git or Github we have a guide about contributing to our projects here: https://learn.adafruit.com/contribute-to-circuitpython-with-git-and-github
There is also a guide that covers our CI utilities and how to run them locally to ensure they will pass in Github Actions here: https://learn.adafruit.com/creating-and-sharing-a-circuitpython-library/check-your-code In particular the pages: Sharing docs on ReadTheDocs and Check your code with pre-commit contain the tools to install and commands to run locally to run the checks.
If you are attempting to resolve this issue and need help, you can post a comment on this issue and tag both @foamyguy and @kattni or reach out to us on Discord: https://adafru.it/discord in the #circuitpython-dev channel.
The following locations are reported by mypy to be missing type annotations:

[ ] simpleio.py:37
[ ] simpleio.py:72
[ ] simpleio.py:89
[ ] simpleio.py:119
[ ] simpleio.py:196
[ ] simpleio.py:206
[ ] simpleio.py:218
[ ] simpleio.py:228
[ ] simpleio.py:232

Working on this for pycon2023


[RFC] Deprecate amp_level in favour of ApexMixedPrecisionPlugin(amp_level=...)

Proposed refactor
Deprecate amp_level and let users choose a different amp_level by passing Trainer(..., plugins=[ApexMixedPrecisionPlugin(amp_level=...)].
Previous discussion: https://github.com/PyTorchLightning/pytorch-lightning/issues/9956#issuecomment-1091645295
Motivation

Currently, amp_level is used only when precision=16 and amp_backend='apex' i.e it's only relevant for only one type of configuration and is generally not required.
Users can easily choose it by setting Trainer(..., plugins=[ApexMixedPrecisionPlugin(amp_level=...)] which IMO makes more sense since it now reflects that amp_level is only relevant for ApexMixedPrecisionPlugin.
Pitch

Deprecate in v1.6 and remove in v1.8.
Additional context

If you enjoy Lightning, check out our other projects! ⚡

Metrics: Machine learning metrics for distributed, scalable PyTorch applications.

Lite: enables pure PyTorch users to scale their existing code on any kind of device while retaining full control over their own loops and optimization logic.

Flash: The fastest way to get a Lightning baseline! A collection of tasks for fast prototyping, baselining, fine-tuning, and solving problems with deep learning.

Bolts: Pretrained SOTA Deep Learning models, callbacks, and more for research and production with PyTorch Lightning and PyTorch.

Lightning Transformers: Flexible interface for high-performance research using SOTA Transformers leveraging Pytorch Lightning, Transformers, and Hydra.

cc @justusschock @awaelchli @rohitgr7 @tchaton @kaushikb11 @borda

I am in favor of this. Note this was also proposed in #11814, but I think the precision argument should stay on the Trainer. Hence I prefer this proposal here more over the aggressive one in #11814.


toHTML of Pretty Pills cannot handle int.

Can we just wrap in a String(value).replace...?

Fixed by #5596.


field errors dont go after doing ajax submit on form with validation.

all the field errors which were generated while trying to fill a form styled with bootstrap dont disappear after doing ajax submit on the form .
But using normal xhtml form , it works as expeced

Can you please try with latest version? The field errors are shown to me in my tests.

Fixed in latest available version.


Add Python 3.8 support

Signed-off-by: Gábor Lipták<EMAIL_ADDRESS>

Build fails with
taskcat/_cli_modules/test.py:33:5: C901 'Test.run' is too complex (12)

although the file wasn't updated

/do-e2e-tests


Docker: Very minor documentation update

Use the latest tag which is always moved with the latest build.
The master tag used for the initial build is a fallback because it wasn't a tag. In the future when a release is created the image will share the release version (eg: v1.60.0) and latest.

Sweet, thanks! Hoping to have an actual release out soon :)


Support API v2

This package appears to only support version 1 of the DNSimple API, which is currently scheduled to be discontinued on October 1, 2017.  Support for version 2 of the API is needed instead.

This was fixed with #27


Stack 1.13

Related to #733
#738 should be merged first
refactor amp stack to use Docker 1.13 way of managing them.
to test:

amp pf stop amp (stop amp old way)

make install (clean before could be required)

make TAG=local build-image

amp pf start --local all

amp pf monitor (in the separated console)

amp pf start --local -> start only ampcore

amp logs -> error

amp pf start amplog --local (wait for stack started)

amp logs --infra -> a lot of logs...

amp pf stop amplog

amp stats -> error

amp pf start ampmonitor --local (wait for stack started, and wait a while to have some data)

amp stats -> a lot of metrics

amp pf stop ampmonitor

amp pf start ampfunction --local

cd examples/functions/demo-function

make image

amp fn create test appcelerator/amp-demo-function

cat Makefile | curl fn.ampfunction.local.appcelerator.io/test --data-binary @-

-> function executed

amp pf stop ampfunction

cd ../../.. (back to amp home)

amp pf start ampadmin --local (wait stack is started)

amp node ls -> see your host information

amp node count -> see your stopped container

amp node purge --container -> container deleted

amp node count -> see you don't have stopped container anymore

amp pf stop ampadmin

amp stack up test -c api/rpc/stack/test_samples/sample-03.yml (wait stack is started)

curl www.test.local.appcelerator.io/ping -> pong

amp stack ps test  -> list task

amp stack services test -> list services

amp stack rm test

amp stack ps ampcore -> see it's working also for infra stack

amp stack services ampcore -> same

autmated tests:

amp pf stop (wait all is down)

amp pf start all --local -v  (wait all is up)

make test

@freignat91 I will start to review, but we have a convention for the team that we have discussed in the past. To make dealing with vendoring easier (as well as to make the GitHub review for your specific PR easier since vendor updates includes 1000's of files), we submit a separate PR for the proposed vendor updates, followed by the PR with the code updates. I'll be looking at some of the vendor update conflicts later today that I had noticed previously, so I might be able to submit the vendor PR for you. I'll let you know.

ok, no problem

@freignat91 This is looking good. We still have a bunch of work to get this integrated with the new build system. I just a pushed a commit that merges this with the latest of all the vendor updates (from #738) and includes a number of other changes and fixes. Also, I took the liberty of renaming amp.var to amp.manifest, which is what I asked for.
You forgot that I wanted your PR to be submitted against stackv3, not master. It looks like someone deleted the branch, so I just recreated it again. Please update this PR to merge against stackv3. Thanks.

ok, i close this one and open a new one

Will reopen the PR when based against stackv3 branch as requested.


Fix default dockerignore

Changes

Current dependencies on/for this PR:

main

PR #447   👈

This stack of pull requests is managed by Graphite.


ttorrent not working: connection timed out for all peers

Does anyone have ttorrent working right now? I started to build a framework around it without testing it out, but now I'm trying to download a torrent with it, and it's stalled on every peer. Here's the type warning messages I'm getting:
18:45:20.514 [bt-announce(..376131)] WARN  c.t.t.client.announce.Announce - No response or unreachable tracker!

18:43:24.690 [bt-connect-12] WARN  com.turn.ttorrent.client.Client - Could not connect to peer://<IP_ADDRESS>:12370/? [Ci|Ci|0]: No route to host.

18:43:24.799 [bt-connect-8] WARN  com.turn.ttorrent.client.Client - Could not connect to peer://<IP_ADDRESS>:57351/? [Ci|Ci|0]: Handshake size read underrrun.

18:43:25.108 [bt-connect-8] WARN  com.turn.ttorrent.client.Client - Could not connect to peer://<IP_ADDRESS>:13881/? [Ci|Ci|0]: Connection refused.

18:45:31.778 [bt-connect-5] WARN  com.turn.ttorrent.client.Client - Could not connect to peer://<IP_ADDRESS>:51413/? [Ci|Ci|0]: Connection timed out.

I tried using deluge to download the same file, which uses libtorrent, and that's having no problems.

I'm seeing people with similar issues in #43 and #85

I just verified that the issue with the previous torrent was that for some reason ttorrent doesn't work with very large files, over 1GB.
I'm also finding that download resuming doesn't appear to work. I'm going to split these into separate issues.

Thanks; closing this issue in favor of the other ones.


Error when running release 1.4.1

Hi,
Marc from Tübingen, Germany here.
When I update our installation from 1.3.2 to 1.4.1 I get the following error when starting the service:

Do you have any idea what the problem is?
BTW, for release 1.3.4 there is no JAR file.
Best,
Marc

I fixed it by adding ?useSSL=false to the spring.datasource.url


navigator simpler cruising speed handling

We don't need to store separate cruising speeds for MC/FW. The custom speed/throttle only applies within a mission session after the command is executed.

@PX4TestFlights can we do a simple test on a FW, MC and a VTOL? Thanks

@dagar can you rebase?

@sanderux are you still using DO_CHANGE_SPEED? If so could you verify this PR?

everything here needs to be implemented on cruise_throttle logic too.
also this needs to be addressed: https://github.com/PX4/Firmware/issues/8073

Continued in https://github.com/PX4/Firmware/pull/8085


Parser for filters

Codecov Report
Patch coverage: 92.77% and project coverage change: +3.42 :tada:

Comparison is base (1392319) 81.17% compared to head (b43204a) 84.59%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #44      +/-   ##
==========================================
+ Coverage   81.17%   84.59%   +3.42%
==========================================
  Files          78       81       +3
  Lines         393      474      +81
  Branches        8       15       +7
==========================================
+ Hits          319      401      +82
+ Misses         69       64       -5
- Partials        5        9       +4

Impacted Files
Coverage Δ

Tseesecake/Querying/Filters/FilterFactory.cs
75.00% <75.00%> (ø)

Tseesecake/Parsing/Grammar.cs
100.00% <100.00%> (ø)

Tseesecake/Parsing/Keyword.cs
100.00% <100.00%> (ø)

Tseesecake/Parsing/Predicate.cs
100.00% <100.00%> (ø)

Tseesecake/Parsing/Query/ExpressionParser.cs
100.00% <100.00%> (+8.33%)
:arrow_up:

Tseesecake/Parsing/Query/FilterParser.cs
100.00% <100.00%> (ø)

Tseesecake/Parsing/Query/QueryParser.cs
100.00% <100.00%> (ø)

Tseesecake/Querying/Filters/AfterTemporizer.cs
66.66% <100.00%> (+66.66%)
:arrow_up:

... and 2 files with indirect coverage changes

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


Suggestion: integration with nvim-ts-rainbow

Awesome plugin :tada:
Would be great if colored brackets from nvim-ts-rainbow could be disabled in the dimmed regions. At the moment it looks as follows for me:

I just pushed a fix where I set a higher priority for the dimming extmarks. This prevents the rainbow delims to bleed through.


Delete app password confirmation uses browser alert instead of "nice" dialogue

Fixes https://github.com/bluesky-social/social-app/issues/714
Demo web
https://jam.dev/c/8d71cf83-6681-423a-af50-020c0d8babaa
Demo mobile
https://jam.dev/c/bbb7f277-7d71-4db6-995c-f04d72335662

This code was written and reviewed by GitStart Community. Growing great engineers, one PR at a time.

Is this PR ready for review?


Instructions for RKE install using Homebrew

@dnoland1 can you rebase? we moved v0.1.x to latest for RKE.

@deniseschannon I've rebased. Can you review/merge? Thanks!


Windows Copilot is actually Edge

Microsoft PowerToys version
0.84.0
Installation method
Microsoft Store
Running as admin
No
Area(s) with issue?
Workspaces
Steps to reproduce
Make a workspace however you want.
Select any windows and Copilot.
Save.
Close everything and activate the Workspace.
✔ Expected Behavior
Open all my programs as usual (VSCode left side, Chrome and Copilot 50/50 right side).
❌ Actual Behavior
Everything opened correctly and to the desired width&height. However Copilot apparently runs through some special code in Edge so it's not considered an application (I've tried making a shortcut for it but there's no exe). So when I ran the Workspace it opened just a new tab in Edge insted of the Copilot window.
Other Software
Microsoft Copilot desktop app, newest.

PowerToysReport_2024-09-04-17-12-46.zip

forgot the bug report file.

/dup #34572


open-vm-tools fails to compile on nixos-unstable

Issue description
open-vm-tools fails to build on nixos-unstable
Fails with a lot of 'Bool' does not name a type messages:
/tmp/nix-build-open-vm-tools-9.10.0-2476743.drv-0/open-vm-tools-9.10.0-2476743/lib/include/unicodeTypes.h:476:1: error: 'Bool' does not name a type

Steps to reproduce

Set services.vmwareGuest.enable = true;
nixos-rebuild test

Technical details

System: 16.09pre79453.32b7b00 (Flounder)
Nix version: nix-env (Nix) 1.11.2
Nixpkgs version: "16.09pre79453.32b7b00"

Due to gtkmm being bumped, we also need to bump open-vm-tools: https://github.com/vmware/open-vm-tools/releases

I have actually tried getting the latest 10.0.7 to compile, but it's currently blowing up and I didn't have time to look into it any further. Should we just depend on an older gtkmm in the mean time?

Looks like this was fixed in #14911

Confirmed it builds on master.


Blog description lsp root

I know this issue is not really a part of the GitHub repo per se. However, I couldn't find a way to leave a comment on your blog entry describing how to set up Emacs for unity.
Anyhow, I got quite stuck on when trying to set everything up because lsp-mode auto-guessed the root folder wrongly. Essentially, I had to manually set it to the root of the unity project to get it working (unfortunately not using git as version control for my project). It would be very nice if this was added to the instructions. Otherwise, lovely instructions to get everything up and running. Thanks a lot for sharing it.

Hi, thank you for your feedback! (The blog is hosted on github static pages, actually; I ought to link to the issues page in the blog as a sort of "comments" section)
I've been meaning to do a part 2 of that article with some of the new (and frustratedly exciting) issues I've continued to encounter with unsupported editors in Unity, and I'll be sure to include this tip in the post when I get around to it.

Made a new post! https://eliza.sh/2022-07-31-using-unity-editor-with-emacs-(part-2).html

Looks nice, just one comment: I’m quite sure that the reason lsp-mode doesn’t find the project root is that it doesn’t recognise plastic scam version control. I say quite sure because more or less the first thing I usually do is to set up the appropriate version (usually git but to my knowledge, unity uses quite a lot of binary files which makes git less preferable when it lacks locking). However, in this case I’m not 100% sure because I played around with a few version control systems before deciding to try plastic scm for this project.
Anyhow, point is that it might be worth mentioning that plastic scm might not be recognised as a project root.


Recognize individual files to process from CLI

Hello,
First and most important, thank you for your work on this project and making it public for others to use!
Recent refactor of code introduced a regression: provide individual files to CLI resulted in all *.cr files being processed instead, so given file was ignored.
This change restores the original behavior that allows more fine grained execution.
Once again, thank you for your work and hopefully you accept this contribution.
Cheers.
❤ ❤ ❤

@luislavena oh, sorry for this dummy mistake and thanks for fixing it :)
Actually, one of the rules planned to be added is a "useless variable assignment", which should catch such kind of things. It is not easy to do but doable ;)

Thanks @veelenga for merging!
I was thinking if you have plans for code complexity rules? (ie. Flog) or other code smells like feature envy? (ie. Reek)?
If that is the case, I might be willing to contribute some small rules 😄
Cheers!

@luislavena I was inspired by rubocop and credo (afaik Flog and Reek more or less are alternatives to Rubocop) and currently have a priority for code smell rules rather than code style consistency stuff, but the last ones are also acceptable.
Regarding code complexity rules, that may also be interesting. Personally, I have never used Flog, so I can't say how valuable it is.
I would love to see new contributions, especially looking forward for the new rules 💚. The tool requires a lot of work to be done and has a big TODO list. I might have to prepare some roadmap to involve more people into the work 😼


Restructure config

As currently written, Stump's global state is stored in environment variables. For example, in thumbnail.rs, generate_thumbnail() gets thumbnail_path from config::get_thumbnails_dir(), which is defined as follows:
/// Gets the Stump config directory. If the directory does not exist, it will be created. If
/// the path is not a directory (only possible if overridden using STUMP_CONFIG_DIR) it will
/// panic.
pub fn get_config_dir() -> PathBuf {
	let config_dir = std::env::var("STUMP_CONFIG_DIR")
		.map(|val| {
			if val.is_empty() {
				home().join(".stump")
			} else {
				PathBuf::from(val)
			}
		})
		.unwrap_or_else(|_| home().join(".stump"));

	check_configuration_dir(&config_dir);

	config_dir
}

// [omitting unrelated code]

pub fn get_thumbnails_dir() -> PathBuf {
	let thumbnails_dir = get_config_dir().join("thumbnails");

	check_configuration_dir(&thumbnails_dir);

	thumbnails_dir
}

Basically, any time a configuration variable is needed, an std::env::var call is used to extract the variable from the environment and then that value is used. Because of this, Stump must read configuration variables from the config TOML file at startup and then write them into the environment to ensure that they will be accessible when such calls are made.
This strikes me as suboptimal because it makes most functions nondeterministic based on their inputs. If the environment variables were to be changed (for whatever reason) while Stump is running then they would behave differently, even with the same input variables. I think that, ultimately, this is an antipattern, and it is one that will become increasingly difficult to undo as development continues.
My proposal is to rewrite the configuration of Stump so that it behaves the same way that it does now (i.e., loaded from the TOML file and then from the environment at startup) but instead stores the config in a struct which the program holds onto throughout its runtime and passes to the appropriate functions when they are called. Given that this is not a difficult task, just a laborious one, I'd of course be willing to work on it myself, but I want to open the floor to discussion before starting. Any and all thoughts (including reasons that this may not be as good an idea as I think) would be appreciated.

Hey 👋 thanks for writing this up! Sorry I'm only just now getting to it:

This strikes me as suboptimal because it makes most functions nondeterministic based on their inputs. If the environment variables were to be changed (for whatever reason) while Stump is running then they would behave differently, even with the same input variables. I think that, ultimately, this is an antipattern, and it is one that will become increasingly difficult to undo as development continues.

I think this is the strongest argument for your proposed changes 👍 I don't think I have any objections, dealing with a proper config struct will be more maintainable in the long run IMO. One thought is that clap might be able to be used to aid in this refactor, where you could try and make the config clap-compatible (see the cli crate in this monorepo) and default to environment variables.