Location to do these tasks?

[Hello, Where should be the tasks run? on my desktop/laptop? on the machine using the product linked to Azure (SCCM Primary Server)]?
Thanks,
Dom

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

ID: 13086a23-13ee-bea9-c04b-39d8d1d3bc8d
Version Independent ID: 13f6b3cf-b946-cc46-2c15-b01e9d40a634
Content: Templates overview - Azure Resource Manager
Content Source: articles/azure-resource-manager/templates/overview.md
Service: azure-resource-manager
Sub-service: templates
GitHub Login: @mumian
Microsoft Alias: jgao

Hi Dom,
You can use them from where ever works best for you, as long as the device can reach Azure and you can authenticate it, either via UI or programmatically. The template is just a template- you'll need to use the portal, the CLI, or a deployment pipeline (most build server services should work fine) to actually connect to Azure and do the deployment. The Powershell tutorial might be a good way to get started: https://docs.microsoft.com/en-us/azure/azure-resource-manager/templates/template-tutorial-create-first-template?tabs=azure-powershell.
The best place for specific answers about implementations are going to be the Microsoft Q&A and Stack Overflow forums. We actively look through posts in the forums, and will do our best to get you going in the right direction!

Hello Samara,
Thanks for the clarification.
This is the link I am using https://docs.microsoft.com/en-us/azure/azure-resource-manager/templates/template-tutorial-create-first-template?tabs=azure-powershell.
It is where the confusion starts... :)
Thanks,
Dom

@DominiqueDuchemin - thanks for this feedback. I have added clarification that the tools for the tutorial should be installed on your local machine. Like @SamaraSoucy-MSFT mentioned, you can use any machine that can authenticate to Azure, but for most people the local machine is the most convenient.
The update should get published later today.


Increase the allocated buffer size for names of loaded PPDs (Issue #4860)

Having 128 characters is probably enough in most systems, but in Endless
we have a custom system in place to automatically download printer drivers
that will be accessible from long paths under /usr/share/ppd/eos-config-printer
(e.g. /usr/share/ppd/eos-config-printer/epson-inkjet-printer-201301w_ppds_Epson)
As this path will become part of the virtual path for the PPD, this limit
will cause trouble in cases where the full PPD name exceeds it, since the
path CUPS will try to open will not exist, as it will be truncated.

[master 4a971b9] Update cups-driverd and spec-ipp to be consistent about supporting name(255) values for the "ppd-name" attribute (PR #4860)


Check for changes looks at newValue, not items

Potentially causes more re-rendering than strictly necessary.

Picked up by @vaclavpavlicek


docker/pusher: handle location string containing path and query

Fix #2385
Signed-off-by: Bin Du<EMAIL_ADDRESS>

Codecov Report

Merging #2386 into master will decrease coverage by 8.02%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master    #2386      +/-   ##
==========================================
- Coverage   49.28%   41.26%   -8.03%
==========================================
  Files          84       66      -18
  Lines        7455     7850     +395
==========================================
- Hits         3674     3239     -435
- Misses       3101     4103    +1002
+ Partials      680      508     -172

Flag
Coverage Δ

#linux
?

#windows
41.26% <0%> (?)

Impacted Files
Coverage Δ

remotes/docker/pusher.go
0% <0%> (ø)
:arrow_up:

snapshots/native/native.go
1.8% <0%> (-52.08%)
:arrow_down:

oci/spec.go
0% <0%> (-50%)
:arrow_down:

metadata/snapshot.go
21.53% <0%> (-33.23%)
:arrow_down:

archive/tar.go
16.85% <0%> (-33.15%)
:arrow_down:

archive/compression/compression.go
43.93% <0%> (-8.9%)
:arrow_down:

content/local/writer.go
51.57% <0%> (-8.43%)
:arrow_down:

oci/spec_opts.go
58.46% <0%> (-7.58%)
:arrow_down:

metadata/containers.go
47.97% <0%> (-6.62%)
:arrow_down:

metadata/images.go
58.46% <0%> (-4.7%)
:arrow_down:

... and 80 more

Continue to review full report at Codecov.

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

LGTM

LGTM


Why its download 100 comments only ?

Hi,
It's a really nice script but, when we run it for a particular video,  script is not able to collect  total number of comments present for a given video.
It always download approx 100 videos. How can we fix it?
Thanks

Hello @VinayChaudhari1996,
I set the default download limit to 100. That's why it happened.
You can change it. I updated the script.
Please check line number 41 in the script  ytb_comment_scraper.py,
set the value of the variable "COMMENT_LIMIT" as you wish.
Please let me know if anything is needed.
Thanks

Thanks lots 😇 @ahmedshahriar

Thanks lots 😇 @ahmedshahriar

Pleasure 😀

Hello @VinayChaudhari1996,
I set the default download limit to 100. That's why it happened.
You can change it. I updated the script.
Please check line number 41 in the script ytb_comment_scraper.py,
set the value of the variable "COMMENT_LIMIT" as you wish.
Hopefully, the issue will be resolved after this. I'm closing this issue.
Please let me know if anything is needed.
Thanks

Hello @VinayChaudhari1996,
I set the default download limit to 100. That's why it happened.
You can change it. I updated the script.
Please check line number 41 in the script ytb_comment_scraper.py,
set the value of the variable "COMMENT_LIMIT" as you wish.
Hopefully, the issue will be resolved after this. I'm closing this issue.
Please let me know if anything is needed.
Thanks

Now , There is one more issue again , number of comments downloading mismatch.

Hello @VinayChaudhari1996,
I set the default download limit to 100. That's why it happened.
You can change it. I updated the script.
Please check line number 41 in the script ytb_comment_scraper.py,
set the value of the variable "COMMENT_LIMIT" as you wish.
Hopefully, the issue will be resolved after this. I'm closing this issue.
Please let me know if anything is needed.
Thanks

Hello @VinayChaudhari1996,
I set the default download limit to 100. That's why it happened.
You can change it. I updated the script.
Please check line number 41 in the script ytb_comment_scraper.py,
set the value of the variable "COMMENT_LIMIT" as you wish.
Hopefully, the issue will be resolved after this. I'm closing this issue.
Please let me know if anything is needed.
Thanks

Now , There is one more issue again , number of comments downloading mismatch.

All should be cleared by now. Please check


Add exists function to engine_traits

What problem does this PR solve?
This is another step toward deleting the engine crate. Add an exists method to MiscExt in engine_traits, and use that in the config module. The old db_exist function is still used internally, so mark it deprecated for now.
What is changed and how it works?
Related changes
https://github.com/tikv/tikv/issues/6402
Check List
Release note

No release note.

/merge

What happened to the idc-jenkins-ci-tikv/integration-common-test?

/merge

/run-integration-ddl-test

/merge


Brightness problem with H6199

Hi,
First thank you very much for all your work on this integration.
Now, I have many Govee lights and one of them, H6199 (Hardware version: 3.02.01 Firmware: 1.09.12) was working fine with an old integration but with this one, if I try to set the brightness with something like "brightness_pct: 75" or "brightness: 192" when calling the light.turn_on service, it show as 100% in the Govee app and the led color flicker randomly like it was a scene but still kind of react to the camera.
If, in the Govee app, I set the brightness back to anything (even 100%), the flickering stop and everything go back to normal.
I did some testing with differents brightness levels and also did try to turn on first then wait a second before setting the brightness but it dosen't change anything.
Any idea?
Home Assistant (blue) 2022.12.8
Supervisor 2022.12.1
Operating System 9.4
Thank you

Can you try turning on debugging to see if there is anything useful in the logs from both around startup (when the devices are discovered) and around the time you try to change the brightness of the lights?  Putting this in your homeassistant configuration.yml and then restarting home assistant will make that take effect:
logger:
  logs:
    custom_components.govee_lan: debug
    govee_led_wez: debug

If the LAN API is being used, there's not really a lot that could go wrong from the client side, as it is essentially just sending the brightness value directly to the device; it's possible that it is a problem with the implementation of the LAN API on the device itself, in which case reaching out to Govee is probably the thing to do.
I don't have an H6199, but I do have an H610A that got into a similar sounding state once when I was mixing and matching bluetooth control from the govee app (to play with a scene), with subsequent LAN control from an automation in hass.  Power-cycling the device sorted it out for me.

Hi,
Sorry for the late late reply...
Actually I did change for the T2 and it is working fine.
Thank you

Actually I did change for the T2 and it is working fine.

I'm not sure what you mean by this.  Are things working fine for you now?

Sorry, yes, I had the problem with the Dreamview T1 and since, I've got the T2 and no problem anymore...
Thank you

Sorry, yes, I had the problem with the Dreamview T1 and since, I've got the T2 and no problem anymore...
Thank you


Update total finder app

included sudo:  true since the uninstaller is requiring sudo to run it headles

Ref . #32014
After Updating
$ brew cask uninstall totalfinder.rb
==> Running uninstall process for totalfinder; your password may be necessary
==> Running uninstall script TotalFinder Uninstaller.app/Contents/MacOS/TotalFinder Uninstaller
Password:
==>   shutdown TotalFinderCrashWatcher ...
==>     TotalFinderCrashWatcher was not running
==>   shutdown TotalFinder agent ...
==>     TotalFinder agent was not running
==>   shutdown Finder ...
==>   remove TotalFinder.app from login items ...
==>   removing the old TotalFinder files (0.8.2 and earlier) ...
==>   unload TotalFinder.kext ...
==>     TotalFinder.kext not loaded
==>   remove TotalFinder.app ...
==>   remove TotalFinder.kext ...
==>   remove TotalFinder.osax ...
==>   enable Finder animations again ...
==>   hide system files in Finder again ...
==>   relaunch Finder ...
==> TotalFinder uninstallation done.
==> Uninstalling packages:
com.binaryage.pkg.totalfinder.app

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} reports no offenses.
[x] The commit message includes the cask’s name and version.

Thank you @gobinathm.


The eslint of this project is not working in vscode.

I'm sorry, but I've tried for a long time and for some reason, ESLint doesn't work when using this project in vscode, and there is no automatic fix when saving.

Delete eslint.options.extensions in the User/settings.json
从你的 ‼用户目录‼/settings.json 中，删除 eslint.options.extensions
在 MacOS 中，一般这个位置是

We temporarily closed this due to the lack of enough information. We could not identify whether it was a bug or a userland misconfiguration with the given info.
Please provide a minimal reproduction to reopen the issue.
Thanks.

Why reproduction is required


Shifter: Foot component: Have some orientation limitations

At this time,
we have to model certain limbs at fixed orientaons
as far as legs goes and such,
otherwise the foot roll solvers will be slanted and FKs's not oriented to they would be expected
to be. We cannot generate a viable rig if someone has legs at any angle that is not aiming
directly at the go

This issue was moved to mgear-dev/shifter_classic_components#5


NAS-129825 / 24.10 / Capture iommu groups directory tree in debug

Context
Add iommu group directory tree in debug to capture how the iommu groups are laid out to better help in debugging issues related to passthrough.

Jira URL: https://ixsystems.atlassian.net/browse/NAS-129825

Jira URL: https://ixsystems.atlassian.net/browse/NAS-129825

This PR has been merged and conversations have been locked.
If you would like to discuss more about this issue please use our forums or raise a Jira ticket.


[FEAT] Add theme toogle

As a user, If you want to be able to switch between light and dark themes on the website/app, so that you can choose the one that is easier on my eyes or fits your preferences.
To implement this feature, we will need to add a button or switch somewhere on the page that the user can click or tap to toggle the theme. When the user switches the theme, we will need to update the CSS styles accordingly to apply the appropriate colors, fonts, and other design elements.
In addition, we should consider storing the user's preference for the theme in a cookie or local storage, so that it persists across page reloads and sessions.
By adding this functionality, we can improve the user experience and make the website/app more accessible and customizable for our users.

I am working on this feature

It's Tailwind CSS btw

Yes

I am using context api

Are you familiar with Shadcn-ui. Try that


Implementing tooltipStateChanged and exporting the directive

implemented state changed event for tooltip
exposed the directive so it can be used in the template

Should fix #807 and #883.

Current coverage is 90.39% (diff: 100%)

Merging #939 into development will not change coverage

@@           development       #939   diff @@
=============================================
  Files               26         26
  Lines              781        781
  Methods            142        142
  Messages             0          0
  Branches           115        115
=============================================
  Hits               706        706
  Misses              75         75
  Partials             0          0

Powered by Codecov. Last update b5c8448...35225be

@adrianfaciu thanks! all awesome as usual


Pract.05: Add 07-09 | Nikolina Madzharova

Nikolina Madzharova
SI 4 0MI0600464

Please follow the github workflow. You can ask for help in the Practicum lessons if needed


Support Alibaba OSS as an external blobstore for bosh

As of today there is no native integration of the Alibaba Storage (OSS) in BOSH.
This issue aims to implement that integration.
It requires to:

implement a storage cli for Alibaba OSS
auto bump the storage cli
integrate the cli into bosh
add the storage cli into the stemcell builder
update the stemcell ci
and update the documentation finally

This issue should provides the required transparency.

The storage cli will be implemented in: https://github.com/cloudfoundry/bosh-ali-storage-cli
There is already a PR that provides the the initial version: https://github.com/cloudfoundry/bosh-ali-storage-cli/pull/1

A very similar integration of the azure-storage-cli into bosh was already done in https://github.com/cloudfoundry/bosh/issues/2457

The CI integration for azure-storage-cli will be added with:

https://github.com/cloudfoundry/bosh-ali-storage-cli/pull/3
https://github.com/cloudfoundry/bosh-ali-storage-cli/pull/4

@mvach are you still working on this?

Hi @rkoster,
because of priorities, the bosh director integration of this cli is currently on hold.
Currently I cannot estimate when we will continue with it.


compliting problem

Describe your bug here.
the terminal say error with file hxcpp.pch
Command Prompt/Terminal logs (if existing)
Creating C:/Users/Lenovo/Documents/Source Codes/OTSOSONIK FUNKIN/export/release/windows/obj/obj/msvc1964-nc/__pch/haxe/hxcpp.pch...
Error: Could not create PCH
hxcpp.cpp

Are you modding a build from source or with Lua?
Source
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
no

#10756


[Hub Generated] Review request for Microsoft.Kusto to add version stable/2022-02-01

This is a PR generated at OpenAPI Hub. You can view your work branch via this link.
Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[x] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
If updating an existing version, please select the specific langauge SDKs and CLIs that must be refreshed after the swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[ ] No refresh required for updates in this PR

Contribution checklist:

[x] I commit to follow the Breaking Change Policy of "no breaking changes"
[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[x] Check this box if any of the following apply to the PR so that label "WaitForARMFeedback" will be added automatically to begin ARM API Review. Failure to comply may result in delays to the manifest.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits.

[x] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in a stable version
[ ] Removing properties in a stable version
[ ] Removing API version(s) in a stable version
[x] Updating API in a stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

According to log info, there is unproper definition:
fatal   | Process() cancelled due to failure
error   |   Error: $ref to original location 'file:///_/azure-rest-api-specs/specification/azure-kusto/resource-manager/Microsoft.Kusto/stable/2022-02-01/kusto.json#/parameters/SubscriptionIdParameter' is not found in the new refs collection

@msyyc The SubscriptionIdParameter is defined in the swagger in line 6102. What am I missing? It was not change in the version.
The only thing that was changed that I added x-ms-path, maybe it is because of that?

SubscriptionIdParameter

Yes, the error is caused by x-ms-path. But the error is reported by autorest.core, not autorest.python. You could ask help from @timotheeguerin

That error does seem to be this issue that is quite old and has been fixed https://github.com/Azure/autorest/issues/3546
Not sure which job is having this issue but it is most likely using an old version of @autorest/core and should be updated. If this is is still happening with the latest please create an issue in the autorest repo.

@msyyc did you see @timotheeguerin comment? Is it possible to upgrade the autorest-core version in the tests?

Java is on 3.6.6 (and the bug above is fixed in 3.0.6339)

Hi @docohe @timotheeguerin
Python is same with Java. Upgrading autorest.core does not solve the problem: https://github.com/Azure/azure-rest-api-specs/pull/17197#issuecomment-1005450932

@msyyc could you please open an issue to the autorest-core?

@docohe @msyyc found the issue. There is a typo in the spec you are using x-ms-path instead of x-ms-paths so in the Swagger-> OpenAPI 3 converter it doesn't convert x-ms-path to OpenAPI3 including the ref but then down the line it will try to replace all the $ref it find in the document which include that one being #/parameters/SubscriptionId instead of #/components/parameters/SubscriptionId.
If you change to the correct name you'll have some other validation error as some things are defined incorrectly in that operation.
I'll see if I can improve something so autorest can give a better error in cases like that.

@timotheeguerin could you please refer me to a swagger that has 'x-ms-paths' I cannot see what I'm doing wrong. I've looked in this repo and couldn't find anything.
Do I need to use different parameters in the x-ms-paths? Not sure I understand the issue.

@docohe what is the current error you are having, x-ms-paths is the same as paths it just gets merged together.
Samples https://github.com/Azure/autorest.testserver/blob/0779a7f2a6a92b76be4bd8e6c57dd72897400323/swagger/paging.json#L535

@timotheeguerin @msyyc maybe one of you could help me. When I am using the following path in the x-ms-paths /subscriptions/{subscriptionId}/providers/Microsoft.Kusto/locations/{location}/operationresults/{operationId}?operationResultResponseType={operationResultResponseType}
The semantic validation fails because it thinks that there is another path parameter named operationResultResponseType which is not defined. However, operationResultResponseType is a query parameter. Do you know how to help me with?
When I use the following path:
/subscriptions/{subscriptionId}/providers/Microsoft.Kusto/locations/{location}/operationresults/{operationId}
and mention the query parameter in the parameters list, it says that it has a conflict.

@docohe can we step back and understand what you are trying to achieve? What is this new API supposed to return?
I am actually not sure you can use x-ms-paths like that with a query param that is not a fixed value. If it worked  you might need to make the parameter a path param not a query param then.

@weidongxu-microsoft we are almost ready for merge.
We have four test that are still failing:

Api readiness - we are deploying our manifest with the new Feb API-version. The rollout of the manifest is about week, so this should be done by next week.
Cross-Version Breaking Changes - I've added the tag 'BreakingChangeReviewRequried' did someone review this? Can you tag the person who should approve this? We add a default value to a property, it had default value in the backend from day one, so there is no really breaking change here. We just forgot to add it in the swagger and it was caught by S360
~[Staging] Cross-Version Breaking Changes - is the same is 2. Please correct me if I'm wrong
Swagger SDK Breaking Change Tracking - I'm not familiar with this test and I'm not sure what to do with. The error message tells me nothing.

We really would like to be able to release this API version next week.

@docohe

"api readyness" You can leave it there. If urgent, we can merge the PR before service rollout. If not urgent, we can re-run this after rollout.
"corss-version breaking changes" It seems the only change is the default value of one property (that is missing from previous version). You may ping JeffreyRichter for a quick approve.
"sdk breaking changes" @ArcturusZhang for double check on Go SDK breaking change.
You can ignore the [staging] CI

@docohe
Do you have new API (there is too many commits in this PR)? If yes, you also need ARM review.

@weidongxu-microsoft yes there is new api-version in the PR.
There are a lot of files in this PR, but most of them changed because of the json prettify, you can tell the diff to ignore space changes.
In addition, I'll get the breaking change approval

@docohe, couple of things are needed before your PR is ready for ARM review:

Please study the materials described in the submission form and attest to that by checking the box: [ ] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.
Please create a new PR following this item (and check the box when you submit):
[ ] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits.
Ensure the files for the current API version are copied without modification to the new API version folder for the first commit, then apply changes in subsequent commits. This is required for ARM review.

@mentat9 I've done what I've asked on this PR using force -f. Could you please take a look?

"/subscriptions/{subscriptionId}/providers/Microsoft.Kusto/locations/{location}/operationresults/{operationId}?operationResultResponseType=Location": {

operationResults (casing)?

Refers to: specification/azure-kusto/resource-manager/Microsoft.Kusto/stable/2022-02-01/kusto.json:3585 in 93d336b. [](commit_id = 93d336bb77125cc818f68e847161b51bd4c023de, deletion_comment = False)

      "default": "Disabled"

This is a cross-version breaking change. Clients on the previous version who take the default will start getting different behavior after you switch to the new API version.
I see you got a breaking change approval. Did it cover this change?

Refers to: specification/azure-kusto/resource-manager/Microsoft.Kusto/stable/2022-02-01/kusto.json:3775 in 93d336b. [](commit_id = 93d336bb77125cc818f68e847161b51bd4c023de, deletion_comment = False)

    "allowMultiDatabase": {

ARM recommends string enums over boolean. Generally enums make better properties than booleans. They are more descriptive, flexible and future-proof while being easier for customers to discover, understand and use. Ref: https://armwiki.azurewebsites.net/rp_onboarding/process/api_review_best_practices.html?q=boolean#common-issues-found-in-review.
Best approach is to choose a better property (e.g. databaseRoutingPolicy: { "Single", "Multiple" } or similar). This type of property is generally easier for customers to understand and use.
You can also have a string enum with True/False (or Enabled/Disabled, etc.) values which is still better than boolean, since modelAsString enums allow adding values later without requiring a new API version (e.g. "Unknown", "Default", etc.).

Refers to: specification/azure-kusto/resource-manager/Microsoft.Kusto/stable/2022-02-01/kusto.json:4295 in 93d336b. [](commit_id = 93d336bb77125cc818f68e847161b51bd4c023de, deletion_comment = False)

    "allowMultiDatabase": {

Similar consideration here and in the EventGridConnectionProperties definition below.

Refers to: specification/azure-kusto/resource-manager/Microsoft.Kusto/stable/2022-02-01/kusto.json:4340 in 93d336b. [](commit_id = 93d336bb77125cc818f68e847161b51bd4c023de, deletion_comment = False)

@mentat9 I've done what I've asked on this PR using force -f. Could you please take a look?

Thank-you @docohe, much appreciated.

Signed off from ARM perspective.

@weidongxu-microsoft could you please merge?


Version alignment between Worker and Webjobs package.

Confirm if the following is true: Every time they release a new webjobs version we have to first release a new version of our extension package, and then after that's published generate and release a new version of the worker package?
How important is it to align the worker package and webjobs package. Can we make sure there are no breaking changes and still maintain the majorVersion.* pattern for the worker? What are the disadvantages with it.

Closing this post discussion with AF folks - the gist is "we want to maintain same behavior using a particular version of bundles/worker, introducing a dynamic dependency can change this by introducing new behaviors for the same version! We would want to avoid this for easier troubleshooting and addressing fixes."


Fix proxy rdpdr/smartcard handling

This PR fixes two issues with proxy device/smartcard redirection:

rdpdr client might receive a server capabilities request while in running state (i.e. seen this when server redirects).
stream in smartcard redirection was checked for remaining length before its position was reset

General remark: don't we have to do a global reset of all proxy channel states during a resize or a redirection from the backend ? And so that introduce the question to forward that reset to the front client (like in the resize case)...

@hardening Yes - that's what I also noted ... as far as I can tell (at least regarding the rdpdr code) we only reset the proxy's client side channel, but the server backend currently won't even get notified in case of such an event.


Multiple package manager

Hi,
How to deal with multiple package manager ? Example bun and npm.

I made a fork, check this if interested:
https://github.com/rharkor/only-allow-many


Transparency Controll

What feature or improvement do you think would benefit Files?

It would be nice to have the transparency control over the main window.
It would be nice to have the icon size control of the left hand side folder menu.
It would be nice to have an easy method to pay a subscription fee or one time payment in order to support the development of this product.

Otherwise Files is just beautiful. Thank you :-)
Requirements

This proposal will accomplish easier utilization for people with eyes problems

Files Version
V. <IP_ADDRESS>
Windows Version
Windows 11 Home 10.0.22621
Comments
Awesome product!

It would be nice to have the transparency control over the main window.

This isn't supported in WinAppSdk but we'll look into adding support if it becomes available.

It would be nice to have the icon size control of the left hand side folder menu.

A similar request recently came in, we're tracking this in #11370

It would be nice to have an easy method to pay a subscription fee or one time payment in order to support the development of this product.

The best way to support the project is to purchase the app on the Microsoft Store, but you can also sponsor us through GitHub. Thank you for the feedback 🙂

The best way to support the project is to purchase the app on the Microsoft Store, but you can also sponsor us through GitHub. Thank you for the feedback 🙂
<<< I've tried purchase it on MS Store but no luck. The process gets broken somehow for some reason.
On 2/23/2023 7:33:39 PM, Yair @.> wrote:
It would be nice to have the transparency control over the main window.
This isn't supported in WinAppSdk but we'll look into adding support if it becomes available.
It would be nice to have the icon size control of the left hand side folder menu.
A similar request recently came in, we're tracking this in #11370 [https://github.com/files-community/Files/issues/11370]
It would be nice to have an easy method to pay a subscription fee or one time payment in order to support the development of this product.
The best way to support the project is to purchase the app on the Microsoft Store, but you can also sponsor us through GitHub. Thank you for the feedback 🙂
—
Reply to this email directly, view it on GitHub [https://github.com/files-community/Files/issues/11435#issuecomment-1442170812], or unsubscribe [https://github.com/notifications/unsubscribe-auth/A52XQYW5GUKUJ2734OG6UCDWY6NPHANCNFSM6AAAAAAVF5F2PY].
You are receiving this because you authored the thread.Message ID: @.>


Limit DNS resolution to IPv4

If we use RestClient or cURL to send a GET request to one of our hosts, it is really slow:
$ time curl <host>
[...]
real    0m5.531s
user    0m0.000s
sys     0m0.006s

s = Time.now
RestClient.get("<host>")
puts Time.now - s # 5.627323704

We found out that the requests are much faster if we only use IPv4 to resolve the DNS:
$ time curl -4 <host>
[...]
real    0m0.017s
user    0m0.005s
sys     0m0.000s

-4, --ipv4
       If curl is capable of resolving an address to multiple  IP  ver‐
       sions  (which  it  is  if it is IPv6-capable), this option tells
       curl to resolve names to IPv4 addresses only.

Is there a way to do this with RestClient?

Was this DNS resolution issue or IP protocol version routing issue? I wonder if one bright day in the future ruby will get proper IPv6 fallback support https://bugs.ruby-lang.org/issues/17525


Error pops up when resizing the window

Error executing lua callback: ...ocal/share/nvim/lazy/dashboard.nvim/lua/dashboard/ui.lua:39: Invalid buffer id: 1
stack traceback:
	[C]: in function '__newindex'
	...ocal/share/nvim/lazy/dashboard.nvim/lua/dashboard/ui.lua:39: in function 'load'
	...al/share/nvim/lazy/dashboard.nvim/lua/dashboard/init.lua:46: in function <...al/share/nvim/lazy/dashboard.nvim/lua/dashboard/init.lua:45>

Apparently, the bufnr passed to  load in ui.lua is wrong?
Context: This happens when I'm just editing, the dashboard i not opened

Can you update the plugin and see if the error persists?
There was a somewhat recent update that should prevent this: https://github.com/MeanderingProgrammer/dashboard.nvim/commit/4a0fe3ad97ae29859ee02fad61dc203c9d3e5f76. Based on the line numbers in your error message you're on a version before this update.
If you still get the error can you describe what you do to trigger it, i.e.:

Open neovim dashboard
Click key to open project
Open any file in project
Resize neovim

Something to that effect.

I can't reproduce it anymore on 4a0fe3a. I thought I did update already and still had the issue on 4a0fe3a, but apparently not?
Thanks for fixing it and making this plugin available :) Happy editing.


Coreutils Cleanup and Run Automation

As we have discussed, we will use Coreutils -6.10 instead of scalability folder. In this PR, I have removed Coreutils-6.11 and build Coreutils -6.10 based on http://klee.github.io/tutorials/testing-coreutils/ step 1 and step 2.
To generate .bc files from Coreutils -6.10, I add folder whole-program-llvm. The steps are:
cd coreutils-6.10/obj-llvm/src
/klee-examples/whole-program-llvm/extract-bc <filename>

Then, it would generate .bc file for specific program and we can run tracer-x to execute this .bc file.
@domainexpert  I actually plan to create a Makefile in coreutils-6.10/obj-llvm/src for auto-generating .bc file and run it with tracer-x. But, there is also a Makefile inside the folder. Do you have any suggestion?

@feliciahalim Regarding your question, I would suggest for now the use of shell scripts. We can create a new folder called scripts and put bash scripts there, say, scripts/run-coreutils, When scripts/run-coreutils is executed, it will build and execute coreutils-6.10. If you agree to go ahead with scripts, please do not forget to put some explanation on their usage in README.md.

@feliciahalim Thank you! I think it is best not to include the built Coreutils 6.10, but instead use a shell (bash) script to build it, and then extract the llvm bc. Also, instead of including whole-program-llvm in this repository, we could get the shell script to clone it for us, and then extract the bc for all programs in the coreutils, all done automatically. A shell script essentially command lines to be executed by the shell. An example is https://github.com/tracer-x/tracer/blob/master/dist/tracer. The first line of the command is usually #!/bin/bash which specifies the interpreter that executes the script.

@feliciahalim An alternative to script is to move coreutils-6.10 directory within another directory that contains a Makefile, perhaps named just coreutils. So here we could create a new Makefile that would build Coreutils 6.10, clone whole-program-llvm, and extract the bitcode. I think this solution may be better than using scripts as it is more conforming to how other subdirectories are handled (using Makefile).

@domainexpert  Thank you very much for the feedback. I followed your suggestion by moving coreutils-6.10 into coreutils and creating Makefile in there. I actually did not clone the whole-program-llvm by using Makefile, but provided whole-program-llvm together in the coreutils. The reason is if the clone process of whole-program-llvm takes place when executing Makefile. It's quite hard to check whether the clone was successful because sometimes the clone process might not successful because of internet connection. I also avoiding to clone whole-program-llvm several times. I have explained in the README file inside coreutils folder that indicates whole-program-llvm is a wrapper script.
To try the Makefile, please use this new branch: https://github.com/tracer-x/klee/tree/cat . I use cat instead of echo because last time my computer freeze when I executed echo.
Please let me know what you think.

@feliciahalim I still need to look some more, but my first comment is that I think we could probably do away with the top-level Coreutils, coreutils-6.10, and whole-program-llvm directories.

@feliciahalim I think coreutils/Makefile~ need not be included in the commit.

@feliciahalim coreutils/whole-program-llvm is empty. In any case, I think it is best to make it the responsibility of the user to clone whole-program-llvm themselves, and have the user specify its location in the Makefile.

@feliciahalim If there isn't much to write in coreutils/README, I suggest moving its content to the top-level README.md under a new coreutils item in the listed subdirectories.

@feliciahalim In the top-level README.md, I suggest renaming coreutils-6.10 to the new coreutils item and remove the item coreutils-6.11.

@domainexpert Thank you for the feedback. I agree to remove whole-program-llvm from coreutils folder and make it the responsibility of the user to clone whole-program-llvm by adjusting the Makefile. I noted it as a prerequisite in the README file. I have also removed top-level Coreutils, coreutils-6.10, and whole-program-llvm directories.

@feliciahalim Thank you! Again I think it would be good to add a little fix to the top-level README.md to synchronize it with the new directory structure, as I mentioned before. Maybe like renaming 'coreutils-6.10' to 'coreutils' in the list of subdirectories and remove the list item for 'coreutils-6.11'.

@feliciahalim I think the variable KLEE_EXAMPLES is not needed in coreutils/Makefile as in README.md we asked the user to run make after changing the current directory to a subdirectory (e.g., coreutils). So the Makefile will be executed with current directory coreutils anyway, and in the cat target, we can replace cd ${KLEE_EXAMPLES}/${COREUTILS}/... with just cd ${COREUTILS}/....

@feliciahalim Thank you so much for the awesome work. I have added just a small polish to the build system of coreutils. In particular, I have moved the instruction from coreutils/README to README.md so that the instruction is harder to miss, with additonal information on older GNU Texinfo in case the user needs it. Also, I have made most things to be configurable in Makefile.common. Note that by setting KLEE_HOME in Makefile.common, various KLEE tools will be found without the need for setting KLE, KLEE_STATS, etc.

@feliciahalim With the latest commits, make cat will automatically build obj-lllvm and obj-gcov only when they are nonexistent.

@feliciahalim Whenever you have time, would you please check that the latest commits work for you. Especially, in this version,  you or any user should only need to edit Makefile.common to suit your environment. Please in particular confirm that make successfully runs cat in coreutils subdirectory with the latest commits of tracer-x/klee#87. I'm happy for this branch to be merged already if it passed your test.

@domainexpert Thank you very much for your work. I have updated with little fix in the remove directory command at make cat. Moreover, In the last page of http://klee.github.io/docs/coreutils-experiments/, there's recommended sym-args for each coreutils program. Therefore, I have updated the Makefile, so the current Makefile should work for all coreutils program with specific sym-args. Please let me know what you think. Thank you very much.

@domainexpert I have also added a new target for running coreutils with KLEE STP solver. Please note in the make target I put re-assignment for some variables like this:
#$(eval KLEE = /home/felicia/git/original/klee/Release+Asserts/bin/klee)
	#$(eval KLEE_STATS= /home/felicia/git/original/klee/Release+Asserts/bin/klee-stats)
	#$(eval KLEE_REPLAY= /home/felicia/git/original/klee/Release+Asserts/bin/klee-replay)
#$(eval KTEST_TOOL= /home/felicia/git/original/klee/Release+Asserts/bin/ktest-tool)

This assignment is because I separate source code of original KLEE and Tracer-x. By default, the variables are point to Tracer-X and I need to re-assign them to point to the source code of original KLEE. However, it might be different in your case. Therefore, I leave these lines commented.
I also put $(eval EXTRA_OPTIONS = ) which basically remove the -interpolation-stat flag since KLEE does not has the option.

@feliciahalim Thank you for a very useful modification! I've just made some polishing to simplify the Makefile and also so that we could conveniently use the sandbox and the minimalistic environment test.env mentioned in http://klee.github.io/docs/coreutils-experiments. The new usage instruction is quite similar to the usage for basic tests, and described in the README.md. That is, to run echo, for example, one executes make echo.klee. And to run KLEE/STP (non-Tracer-X) one simply executes make echo.stpklee. Please note that there is no need to have a separate installation for KLEE/STP as Tracer-X KLEE will run in KLEE/STP mode when --select-solver=stp is provided, Also, when --select-solver=stp is provided, -interpolation-stat will be ignored anyway, so there is no need to worry that the option is not supported.
There are some questions remain:

It is strange that the Coreutils [ program, for example, has no .bc, I think we need to figure out why and ask klee-dev about it if we could not obtain the bitcode file ourselves.
We may be able to use llvm-cov instead of gcov so that we do not need to do a second build of Coreutils in the obj-gcov subdirectory.

@feliciahalim I forgot to add that in coreutils/Makefile, one could opt to use the run options recommended in http://klee.github.io/docs/coreutils-experiments, by commenting/removing the second definition of KLEE_COREUTILS_OPTIONS.

@domainexpert Thank you very much for very significant improvements. On your question, [ program has no .bc, we could work with the rest coreutils program first and  ask klee-dev mailing list later. I think gcov is also fine since it's recommended way in KLEE instruction. We could use llvm-cov for programs other than coreutils.
I also have added coverage log in the makefile. Thank you.

@feliciahalim I think let's not use -output-tree for the first definition of KLEE_COREUTILS_OPTIONS for two reasons: 1) It no longer match what is given in http://klee.github.io/docs/coreutils-experiments which are the options closest to the options KLEE were run with for the experiments reported in 2008 OSDI paper, and 2) 3600 seconds (1 hour) run will likely to generate a huge tree beyond displaying.

@feliciahalim I would also suggest to remove --output-tree even for the second definition of KLEE_COREUTILS_OPTIONS with the 60 seconds run, but to provide the third alternative definiton for KLEE_COREUTILS_OPTIONS with --max-time=10. --output-tree options, so we only output the three for the 10s runs.

@feliciahalim I suggest renaming CoverageLog.txt to GcovLog.txt to make it clear which program produces the coverage information.

@domainexpert coreutils run on 10s currently does not produce any subsumption. While, actually we need the tree to show subsumption. I am still experimenting the number of max-time which is still small enough for manageable display tree and also able to give subsumption. I will rename coverage log.

@feliciahalim Ok, in that case let's not add the third definition of KLEE_COREUTILS_OPTIONS. And maybe let's use --output-tree for the second definiton (with 60s timeout).

@feliciahalim I suggest changing Create SVGs from *.dot files ... in coreutils/Makefile to Create SVG from tree.dot ...

The suggested renaming of CoverageLog.txt to GcovLog.txt is actually implemented in PR #42 .


BrickPi python + gyroSensor

System information:

I am using:

RaspberryPi  3 Model B v1.2
BrickPi (old model (maybe HW v1.7.3) but FW upgraded to 2.0)
NXT motors and sensors
EV3 gyro sensor

I installed ev3dev using this image file: ev3dev-jessie-rpi2-generic-2016-12-21.img

My kernel version is: 4.4.32-17-ev3dev-rpi2

My host computer is running: Windows10 pro

My IDE: *PyCharm 2016.3

I am connecting using: wifi

My changes to config.txt (only enabled options):*

dtoverlay=brickpi
init_uart_clock=32000000
dtparam=brickpi_battery=okay
dtoverlay=pi3-disable-bt
dtparam=brickpi_led1_trigger=none,brickpi_led2_trigger=none

My issue:
I tried to test gyroSensor:
import ev3dev.brickpi as ev3

p = ev3.LegoPort(ev3.INPUT_2)
p.mode = "ev3-uart"
p.set_device = "lego-ev3-gyro"

gs = ev3.GyroSensor(ev3.INPUT_2)

units = gs.units
while True:
	angle = gs.value()
	print(str(angle)+ " " + units)

This returns all 0 but sometimes I got random ones when shaking gyro.

Still an issue on latest kernel?

I moved on with my life 😄 since then. I don't have time to check and I abandoned that project a year ago.


Fix jasmine-core paths in  jasmine-testing-101

If you want to use jasmine-core instead of jasmine, the paths are different.

There is another file on the guide with the same issue. Updated it as well.

:+1: This is a really simple fix that needs merged so that the testing story can be actually useful.

Agreed. What was I thinking/doing?  Please accept

thank you!


FastAPI specification auto generated with strawberry

Feature Request Type

[ ] Core functionality
[x] Alteration (enhancement/optimization) of existing feature(s)
[ ] New behavior

Description
I'm using fastapi with strawberry and figure out the graphiql endpoint is displayed in the documentation generated by fastapi even if the graphiql option is deactivated in the GraphQLRouter. If you think that change is relevant, it seems quite easy to change in strawberry.

I found an issue by introducing a include_in_schema parameter in get endpoint (https://github.com/strawberry-graphql/strawberry/pull/2736) open. You folks can let me know what you think of it.

Closing this issue, pr is merged. Thanks @patrick91


Add support for reloading the plugin

With SpongeAPI, plugins may be reloaded by listening to GameReloadEvent. What would be reloaded in this plugin is the configuration and possibly registrations of skills and event handlers. An event would need to be added to the API to allow plugins to re-register event handlers and skills that would have been lost during reloading.

Being an implementation detail, a new event will not be added to the API, rather, plugins will not experience any change in behaviour (depending on the implementation - some may though). Only event handlers and skills added by the API/implementation and the configuration will be re-registered and plugins may not necessarily notice a difference (except when it comes to configuration).


Fixed #30039 -- Inconsistency error after unapplying squash migration.

https://code.djangoproject.com/ticket/30039

Closing per ticket (no tests or steps to reproduce the problem).


Elements on non-active views should not be focusable with tabbing

[x] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior
When a view is active, it should not allow keyboard-navigation tabbing to focus elements on other, non-visible views.
Current Behavior
When I have focusable elements in my views (such as form elements), it lets me tab-focus into these elements despite being unable to see/interact with them.
Steps to Reproduce (for bugs)

Code sandbox link
Open the browser console
Attempt to tab through the elements on the page
Observe that the tab focus is focusing elements that should be "non-existent" because they are not on the current active view

Context
I'm using swipeable-views to animate pages of a form. Due to this bug, the form is not accessible to a user who is using keyboard-only nav because they keyboard focus winds up on elements that are not visible or interactable on the page

I believe this is the underlying issue behind https://github.com/oliviertassinari/react-swipeable-views/issues/636

You can get around this if you keep track of the index you are using, and use that index in the slideRenderer function to conditionally set the style of the slide based on whether the index is the active one. For example,
 const slideRenderer = ({index, key}: SlideRenderProps) => (
    <div key={key} style={index !== activeStep ? {display: 'none'} : {width: '100%'}}>
...

@aloverso Add the following to the classname of  or its parent. This will resolve the issue.
"& div[aria-hidden='true']": {
			visibility: 'hidden'
		}


Fix reorder-ctor warnings

When building, I get all these warnings regarding the ordering of the member variable initialization being different to the order of declaration. This pull request fixes some of them (for the files we are building).

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Thanks for catching this, and submitting the fix.
Because they don't include the -Wreorder warning, I assume you were able to catch this because you're not using the Xcode projects to build MoltenVK?
Once I pull this in, I'll add -Wreorder to the Xcode projects, so we can keep constructors aligned for all build environments in real-time in the future.

Thanks for merging so quickly. Yes, we are using cmake.

You're welcome. Thanks for the fix.
I've also added PR #1604 to add the -Wreorder warning in the Xcode project...so that any future changes to member orders will be detected immediately by Xcode builds.


Error when answering via ReplyKeyboard button

I impemented the example using the ReplyKeyboardMarkup, but an exception occurs when the user answers with one of the buttons.
telegram_bot.rb:74:in `block (2 levels) in start': undefined local variable or method `command' for BlaettleBot:Class (NameError)
    from /home/fred/.rvm/gems/ruby-2.3.3@sblaettle/gems/telegram-bot-ruby-0.7.2/lib/telegram/bot/client.rb:38:in `block in fetch_updates'
    from /home/fred/.rvm/gems/ruby-2.3.3@sblaettle/gems/telegram-bot-ruby-0.7.2/lib/telegram/bot/client.rb:33:in `each'
    from /home/fred/.rvm/gems/ruby-2.3.3@sblaettle/gems/telegram-bot-ruby-0.7.2/lib/telegram/bot/client.rb:33:in `fetch_updates'
    from /home/fred/.rvm/gems/ruby-2.3.3@sblaettle/gems/telegram-bot-ruby-0.7.2/lib/telegram/bot/client.rb:25:in `listen'
    from telegram_bot.rb:53:in `block in start'
    from /home/fred/.rvm/gems/ruby-2.3.3@sblaettle/gems/telegram-bot-ruby-0.7.2/lib/telegram/bot/client.rb:18:in `run'
    from /home/fred/.rvm/gems/ruby-2.3.3@sblaettle/gems/telegram-bot-ruby-0.7.2/lib/telegram/bot/client.rb:8:in `run'
    from telegram_bot.rb:52:in `start'
    from telegram_bot.rb:99:in `<main>'

I think it has something to do with Bot API 3.0 changes?

Sorry, I was blind.
This had nothing to do with this gem.


Feat/filter connections by programme

I have also changed the bulk update connection icon and tooltip in this PR following feedback in UR sessions.
TIS21-4635: Reval Connections MVP: Filtering by programme name

I'm kind of okay with that duplication, you could refactor it out into a generic "filters tests" folder but then that makes the test structure a bit more confusing, what do you think?


[WIP] Cleanup test code

Pull Request Test Coverage Report for Build 753

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

Totals

Change from base Build 750:
0.0%

Covered Lines:
751

Relevant Lines:
807

💛  - Coveralls


Recommendations in Snap Templates

With Snap Templates we need to be able to display recommendations in a number of places within the template components. We should be able to do this without needing to create controllers separately and linking them in complicated ways.
For example, in the Search Template, when no results occur, it is common to show a recommendation profile (popular products, etc...). Another use case is showing recommendations inside of an Autocomplete Template when showing popular terms (when input has been focused and nothing has been typed).
An ideal solution to this problem would be to create a fully contained component - meaning, the component would handle creation of the controller internally.
Suggested props:

profile (or tag name)
component name (to utilize the mapping found in SnapConfig)

Alternatively, we may be able to leverage the recommendation instantiator - it looks for script tags on the page and injects into them. This could cause problems due to re-renders and weirdness with targeting rendered content, but may also work fine... probably worth exploring first.

Recommendations Ideas:

Using the instantiator

utilize instantiator ability to create controllers on the fly

wonky unreliable targeting / re-targeting
bad idea to target component elements
not happening

Controller Instantiator Component

create controller only when needed (inside other components)
provide component / theme details as props

circular dependencies; Snap Preact > Snap Preact Components OR Store > Snap Preact Components
no reference to created controller (unless using Snap object) - making it difficult to debug
? how to get these controllers/components into the NoResults component

Use Snap Templates

create controllers of known recommendations during construction (no-results, autocomplete)
in order to handle running the recommendation search at the right time, we could add middleware in afterSearch for example, looking for no-results conditions

creating controllers when not necessary (not just in time)
? how to get these controllers/components into the NoResults component

Controllers in Controllers

search controller creates "no-results" recommendation controller
autocomplete controller creates "trending" recommendation controller

controllers in controllers is not current functionality
creating controllers when not necessary (not just in time)
? how to get these controllers/components into the NoResults component

Merged into templates.
https://github.com/searchspring/snap/pull/993


feat: support secrets from bundle

Description of the change:
PR adds support for OLM generating secrets from a user-bundle.
Motivation for the change:
Reviewer Checklist

[ ] Implementation matches the proposed design, or proposal is updated to match implementation
[ ] Sufficient unit test coverage
[ ] Sufficient end-to-end test coverage
[ ] Docs updated or added to /docs
[ ] Commit messages sensible and descriptive

/retest

/retest

/retest

/retest

/retest

PR is ready to go in but with automatic rebasing turned off will rebase manually.

/lgtm

/lgtm

Passed upstream e2e


Fix capture for updated threejs version

Changes:

For current version of threejs <boxBufferGeometry />  is deprecated so I've updated it to <boxGeometry /> to make capture work again
And also added playground for capturing (check the video below)

https://github.com/user-attachments/assets/a6c4e8a1-56f1-4459-8715-000d70ccf1f9

Thanks for the fix guys <3


Update _filter.xml to exclude Microsoft.Build.Framework.OperatingSystem

@v-alje  Is this the right way to filter out/hide the specific type OperatingSystem in Microsoft.Build.Framework while including all other APIs in Microsoft.Build.Framework ?

@ghogen Yes, your change should filter out the OperatingSystem type in the Microsoft.Build.Framework namespace, any others that have not been previously filtered out should be retained.


test for nrp

@oeoloyede reminder to correct your test case error

@oeoloyede you still need to correct the test case errors.  The issue is your expected string does not match the actual string.


Use joblib hashing to generate cache key to ensure repeatability

TL;DR
Thanks to @bethebunny for finding/fixing this.
When the type of a literal is a dict or Dict (i.e. no type specified for the value), the type engine converts it to a protobuf struct.  If the protobuf struct contains more than one field, then the cache key generated under the old code which ran base64 encoded a cloudpickle dump would sometimes change between calls, which led to local caching not working.
Type

[x] Bug Fix
[ ] Feature
[ ] Plugin

Are all requirements met?

[x] Code completed
[x] Smoke tested
[x] Unit tests added
[ ] Code documentation added
[ ] Any pending items have an associated Issue

Complete description
How did you fix the bug, make the feature etc. Link to any design docs etc
Tracking Issue
https://github.com/flyteorg/flyte/issues/
Follow-up issue
NA
OR
https://github.com/flyteorg/flyte/issues/

nm ignore this for now.  need to add more to this.

@eapolinario can you take a look at this when you get a chance please?  I don't understand the unit tests that are failing and can't find any references to explain what's happening.  Why do we not want ints to cache?


Bugfixes and improvements

Sourced from https://github.com/aschampion/schemer/issues/18.

I opened this PR with the exact commits from the fork-of-schemer. I'm now going to rebase them on our main to fix merge conflicts, and adjust the commits as necessary to document them appropriately.

Rebased on main to handle merge conflicts due to our fork.

Force-pushed to add changelog entries for each commit that alters the public API.


index.html

User story:
AS A marketing agency
I WANT a codebase that follows accessibility standards
SO THAT our own site is optimized for search engines
Acceptance criteria:
GIVEN a webpage meets accessibility standards
WHEN I view the source code
THEN I find semantic HTML elements
WHEN I view the structure of the HTML elements
THEN I find that the elements follow a logical structure independent of styling and positioning
WHEN I view the icon and image elements
THEN I find accessible alt attributes
WHEN I view the heading attributes
THEN they fall in sequential order
WHEN I view the title element
THEN I find a concise, descriptive title

acceptance criteria met to the best of my knowledge


Issue setting Pull Request comments on organization repo

Hi there!
Thank you for your work! It's wonderful and I really like it. Nevertheless, I'm trying to setup a laravel-harbor workflow and have been following the steps from the docs. I have this error whenever i use the github comment notifications
INFO    Including the site information to the pull request.
FAIL    ---> {"message":"Resource not accessible by integration","documentation_url":"https://docs.github.com/rest/issues/comments#create-an-issue-comment","status":"403"}

   Laravel\Forge\Exceptions\ValidationException

  The given data failed to pass validation.

  at /composer/vendor/illuminate/support/helpers.php:330
    326▕     function throw_if($condition, $exception = 'RuntimeException', ...$parameters)
    327▕     {
    328▕         if ($condition) {
    329▕             if (is_string($exception) && class_exists($exception)) {
  ➜ 330▕                 $exception = new $exception(...$parameters);
    331▕             }
    332▕
    333▕             throw is_string($exception) ? new RuntimeException($exception) : $exception;
    334▕         }

I tried to change github.token to secrets.GITHUB_TOKEN, and tried to open an issue before opening a pull request, still the same error each time with a 403 (authorization error maybe ?).
Here is my code :
harbor-provision:
    needs: laravel-tests
    runs-on: ubuntu-latest
    container:
      image: kirschbaumdevelopment/laravel-test-runner:8.1
    steps:
      - name: Install Harbor via Composer
        run: composer global require mehrancodes/laravel-harbor -q
      - name: Start Provisioning
        env:
          INERTIA_SSR_ENABLED: true
          FORGE_TOKEN: ${{ secrets.FORGE_API_TOKEN }}
          FORGE_SERVER: ${{ secrets.FORGE_SERVER_ID }}
          FORGE_GIT_REPOSITORY: ${{ github.repository }}
          FORGE_GIT_BRANCH: ${{ github.head_ref }}
          FORGE_DOMAIN: example.com
          FORGE_SUBDOMAIN_PATTERN: '/(?:feat\/|fix\/)?(.*)/'
          FORGE_DEPLOY_SCRIPT: ${{ vars.LARAVEL_DEPLOY_SCRIPT }}
          GIT_COMMENT_ENABLED: true
          GIT_TOKEN: ${{ github.token }}
          GIT_ISSUE_NUMBER: ${{ github.event.number }}
        run: harbor provision

I have linked my github account with forge, I have admin access to the org, i did grant access to forge also, so i don't know what's going on. Is there any configuration steps i'm missing?
PS: The provisioning and the teardown works perfectly

Hi @hkellou-vitalcare, the workflow looks good, but there may have been some permission changes in your organization that are preventing The Harbor from posting (writing) on the PRs. This GitHub link might help you figure out the issue: https://docs.github.com/en/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#managing-github-actions-permissions-for-your-organization.

Closing this for now since there's been no activity. If you run into this issue again, feel free to open a new PR!


docker-compose.yml not working with lasest docker mac

Updated docker_compose.yml with the following changes to scheduler:
- SINGULARITY_MAX_HEAP=2048m         //would complain out of memory without this
- SINGULARITY_HOSTNAME=localhost    //would complain can't find hostname without this

scheduler:
  image: hubspot/singularityservice:0.17.0
  net: host
  environment:
    - DOCKER_HOST
    - LOAD_BALANCER_URI=http://localhost:8080/baragon/v2/request
    - SINGULARITY_MAX_HEAP=2048m
    - SINGULARITY_HOSTNAME=localhost

However, still errors out with the following even after those changes:
scheduler_1       | Failed to obtain the IP address for 'linuxkit-025000000001'; the DNS service may not be able to resolve it: Name or service not known

Running:
Docker CE Version 17.11.0-ce-mac40 (20561)
Thanks,
Jim

We are aware of issues when using docker for mac since the current compose setup runs with host networking mode. Closing as a dupe of https://github.com/HubSpot/Singularity/issues/1313


Email Sending Option

I wish we could work on sending email directly form our mit app as it proceed to gmail first then it sends email.

can i work on this

can i work on this

Sure. We both can if you want.

Sure. We both can if you want.

can i work on this too?

can i work on this too?


Unpausing a scene causes a PinJoint2D to disconnect

Godot version
v4.0.alpha.custom_build [de53e91b8]
System information
Windows 10
Issue description
I have a scene that contains a PinJoint2D, allowing a RigidDynamicBody2D to rotate around a StaticBody2d. When I pause the scene and then enable it later (see code below), the RigidDynamicBody2D is no longer connected to the StaticBody2d, and just falls away.
My expectation is that the RigidDynamicBody2D will remain pinned to the StaticBody2d and resume rotating.
Steps to reproduce
To reproduce the issue, play the attached project. Observe that the lever initially rotates around the pin joint for two seconds, then pauses. After two more seconds, the scene is unpaused, and instead of resuming rotation, the lever just falls away from the joint.
Scene tree layout:

Attached script:
extends Node2D

func _ready():
	await get_tree().create_timer(2.0).timeout
	process_mode = Node.PROCESS_MODE_DISABLED
	await get_tree().create_timer(2.0).timeout
	process_mode = Node.PROCESS_MODE_INHERIT

Minimal reproduction project
Unpaused_Joint2d_Failure.zip

Apparently this happens only when the RigidDynamicBody2D's disable_mode is set to the default DISABLE_MODE_REMOVE; a workaround is to set the disable_mode to DISABLE_MODE_MAKE_STATIC.

The suggested workaround does work for my particular case, but I can easily imagine other cases where DISABLE_MODE_REMOVE is preferred along with restoring the joint when the simulation is resumed. Thanks for bringing the disable_mode to my attention.
Perhaps it is arguable if this is actually a bug?  I could see it argued either way.

I think it should be classified as a bug. Actually I'm pretty sure I already fixed this once before, but I will have a look again.

What I looked at before was exiting and entering the scene tree; this is different. Anyway, I found the reason for the bug.
When pausing with DISABLE_MODE_REMOVE, CollisionObject2D::_apply_disabled changes the object's space to RID():
https://github.com/godotengine/godot/blob/cc35a8723c4cf07bc26032f4f21d6a93f9997d20/scene/2d/collision_object_2d.cpp#L213-L223
This is great, except that changing the space also clears the constraints in the previous space:
https://github.com/godotengine/godot/blob/cc35a8723c4cf07bc26032f4f21d6a93f9997d20/servers/physics_2d/godot_physics_server_2d.cpp#L525-L540
When unpausing, CollisionObject2D::_apply_enabled will set the space back, but the constraints will have been cleared.
Currently, constraints are added only when the GodotJoint2D is constructed in the physics server, and this is done by the Joint2D node e.g. when the Joint2D node itself or one of the bodies enters the scene tree, or when node_a or node_b are set.
I'm not sure how the issue should be fixed.


After scan v1.5

Merge 1.5 to master
master to become the main branch

This is a test

Forced merge as I cannot approve my own changes

Again


feat: Shortest path

Value add:

capabilities to calculate the shortest path between one start and one end vertex
calculation for unweighted graphs; weighted graphs will be addressed in a follow-up PR

@bobluppes any idea why codecov does not catch the closing curly bracket here? Building and testing runs flawlessly

@bobluppes any idea why codecov does not catch the closing curly bracket here? Building and testing runs flawlessly

This seems to be a weird quirck of lcov, I will see if we can configure the tool differently.
Currently the codecov CI does not block from merging so for this PR we can leave it as-is. In a follow-up I will configure the CI such that we don't need 100% coverage for it to pass, as I think 95% should also be fine.


Use name cray-mpich instead of cray-mpich-binary

Some packages and compiler toolchains explicitly check the name of the MPI implementation, e.g. openmpi, mvapich2 and so on.
The cray-mpich-binary name can cause spack to generate errors in these test.
Investigate whether the cray-mpich-binary package can be renamed cray-mpich, which would replace the cray-mpich provided by spack.

This is one example, which breaks cosma +scalapack: spack/lib/spack/spack/build_systems/intel.py#L830-L867