RPM for CasperJS 1.1-beta3

http://inside-out.xyz/technology/rpm-for-casperjs-1-1-beta3.html
I have create RPMs following Centos6 and Centos7 guidelines.  Add this repo, then do yum install casperjs and it will install it with all deps.
Enjoy

Thank you!
Would you like to create a PR to add it in the documentation?

Yes, I will. Let me review where. I am not very good with git

RPM build scripts are already in the repo: https://github.com/n1k0/casperjs/tree/master/rpm
@mickaelandrieu @n1k0 @paazmaya I am not sure if we want to start / keep publishing beta releases as rpm too.
Closing for the moment. Feel free to re-open when we have a maintainer for rpm and other packages.


Need to replace tendermint/tendermint to cometbft/cometbft

Summary
ref. https://github.com/tendermint/tendermint/issues/9972

Problem Definition

Proposal

For Admin Use

[x] Not duplicate issue
[x] Appropriate labels applied
[ ] Appropriate contributors tagged
[ ] Contributor assigned/self-assigned

There has been an official announcement to switch from Tendermint Core to CometBFT. This includes changes to Tendermint peripheral modules, such as tm-db → cometbft-db. Future Ostracon should also consider plans to change its codebase to CometBFT.
https://github.com/cometbft/cometbft
https://medium.com/the-interchain-foundation/cosmos-meet-cometbft-d89f5dce60dd
This may be worked on later than Finschia α#2.

@tkxkd0159
What are the discussion points? I think we should follow cometbft/cometbft as well. Basically, we forked/followed-up the based on tendermint-v0.34.19. It means the compatibility between cometbft and ostracon.
It's possible to replace the below:

Replace tendermint/tendermint to cometbft/cometbft in go.mod
Replace tendermint/tm-db to cometbft/cometbft-db in go.mod


Following the installation tutorial leads to error

I have been trying it set the navigation up like this: https://github.com/airbnb/native-navigation#installation
Here is my AppDelegate.h:
#import <UIKit/UIKit.h>
#import <React/RCTBridge.h>
@import NativeNavigation;

@interface AppDelegate : UIResponder <UIApplicationDelegate, RCTBridgeDelegate, ReactNavigationCoordinatorDelegate>

@property (nonatomic, strong) UIWindow *window;

@end

I'm getting error: Module NativeNavigation not found. How can I fix this?

Do you open a .xcworkspace file?

Have the same issue, swift upgraded to 4. Any ideas how to pass compilation step on iOS?


Stack Corruption during NoFinancialModelModuleAndInverterModels test

During NoFinancialModelModuleAndInverterModels test in CMPvsamv1PowerIntegration, when module model is set to 2 for CEC User-Entered, there is an error:

Run-Time Check Failure #2 - Stack around the variable 'm' was corrupted.

'm' here refers to line 306 in lib_pv_io_manager.cpp:
//convert from % to derate
for (size_t m = 0; m < monthlySoiling.size(); m++)
	monthlySoiling[m] = 1.0 - monthlySoiling[m] / 100.0;

To Reproduce
Debug the test in Debug Mode in x64. Does not show up in Win32. Bug is present in both develop and release.

Thanks for noting @dguittet , my guess is there are still some variables being used before they are allocated or defined.

@nickdiorio I've been digging into it and I think it's unrelated to our code... The exception is being thrown during VS debugger's _RTC_CheckStackVars function. It says the stack location that is corrupted is a variable in m:
module6par m(tech_id, Vmp, Imp, Voc, Isc, beta, alpha, gamma, nser, 298.15);
but I've looked and the value there is correctly stored and not modified. Actually, I'm getting warnings that the compiled shared.lib is different from the source code, and I think it's the fact that the debugger is expecting different behavior to be the error.

Even after cleaning, rebuilding, relinking, I'm still getting this warning... If nobody else has this stack corruption problem, it might just be me. I think it's fine to close this one since SSC logic is ok.


using GPU

hi, thank you for sharing you code, and I wonder to know whether this code can run with GPU. I build env for tensorflow GPU, but I find it cannot use GPU.
thank you

Hi, I meet the same problem. I tried many times but I could not use the tensorflow-gpu.
Looking forward to your reply.
Thank you


Policy Server security configuration.

Description
Adds in the Policy Server CRD the "security" field. This field can be used to define the "securityContext" of the pod and containers where the policy server is run.
Fix #386
Fix #387

@flavio @viccuad I've added a default securityContext for the pod as well. It will only set the RunAsNonRoot to true.

I think this can be merged, once rebased. I'm fine with the change


Monitor privatelinkscopes accessmodesettings - api version 2021-07 preview

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Please ensure to add changelog with 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 you are targeting to deploy new service/feature to public regions? Please provide date, or month to public if date is not available yet.
When you expect to publish swagger? Please provide date, or month to public if date is not available yet.
If it's an update to existing version,  please select SDKs of specific language and CLIs that require refresh after swagger is published.

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

Contribution checklist:

[x] I commit to follow the Breaking Change Policy of "no breaking changes"
[x] 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

[ ] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
[x] Ensure to copy the existing version into new directory structure for first commit (including refactoring) and then push new changes including version updates in separate commits. This is required to review the changes efficiently.
Adding a new service

[x] Please 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.

[x] 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 there are following updates in the PR, ensure to request an approval from Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[ ] Updating API in 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.

@arolshan please follow the openapi bot instructions and get this reviewed by the breaking changes board.

What do I need to do exactly?
Get Outlook for iOShttps://aka.ms/o0ukef

From: Marcin Jastrzebski @.>
Sent: Friday, July 23, 2021 4:46:11 AM
To: Azure/azure-rest-api-specs @.>
Cc: Arik Olsh @.>; Mention @.>
Subject: Re: [Azure/azure-rest-api-specs] Monitor privatelinkscopes accessmodesettings - api version 2021-07 preview (#15246)
@arolshanhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Farolshan&data=04|01|Arie.Olshanezky%40microsoft.com|5a4fbd7afcf4402df6d508d94d7ba662|72f988bf86f141af91ab2d7cd011db47|1|0|637626015756884901|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=xzGkXI3M8HPcHokbP1GIs5oNVapIsaTpRfMbdW8El10%3D&reserved=0 please follow the openapi bot instructions and get this reviewed by the breaking changes board.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2Fazure-rest-api-specs%2Fpull%2F15246%23issuecomment-885345087&data=04|01|Arie.Olshanezky%40microsoft.com|5a4fbd7afcf4402df6d508d94d7ba662|72f988bf86f141af91ab2d7cd011db47|1|0|637626015756894897|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=31xaFFN%2B0V%2FYpqPq8kN%2BSCJiDi4AM8C0P8CGIiFPCy4%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FALHNW5L5ZQMKSW7YGCKUBQDTZDCWHANCNFSM5AR6DEPA&data=04|01|Arie.Olshanezky%40microsoft.com|5a4fbd7afcf4402df6d508d94d7ba662|72f988bf86f141af91ab2d7cd011db47|1|0|637626015756904888|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=mKTSyXqHR%2B9fp3B65jIExJKEvZtdyV3QWH40TZpuICw%3D&reserved=0.

https://github.com/Azure/azure-rest-api-specs/pull/15246#issuecomment-884599373

What do I need to do exactly?

Is this a new procedure?
Why do I need to go through all of this just from adding a new property?
From: Marcin Jastrzebski @.>
Sent: Friday, July 23, 2021 9:08 AM
To: Azure/azure-rest-api-specs @.>
Cc: Arik Olsh @.>; Mention @.>
Subject: Re: [Azure/azure-rest-api-specs] Monitor privatelinkscopes accessmodesettings - api version 2021-07 preview (#15246)
What do I need to do exactly?
[image]https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fuser-images.githubusercontent.com%2F22460039%2F126743330-45e0e8ff-7873-4cc8-9287-01ee8ca6bd14.png&data=04|01|Arie.Olshanezky%40microsoft.com|e47864f3acac402fa84a08d94da03baa|72f988bf86f141af91ab2d7cd011db47|1|0|637626172882225201|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=Elid8S0j%2BbFCPIM9r5hVFlAtQ50l5LY19dqYqD1i0tA%3D&reserved=0

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2Fazure-rest-api-specs%2Fpull%2F15246%23issuecomment-885421654&data=04|01|Arie.Olshanezky%40microsoft.com|e47864f3acac402fa84a08d94da03baa|72f988bf86f141af91ab2d7cd011db47|1|0|637626172882235210|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=hAUTeJFMWoQYdoofUXyR%2BjwkcRJWsO1%2BlKJx5CwSGmA%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FALHNW5ME76TKK6HGKDVGEXTTZEBMHANCNFSM5AR6DEPA&data=04|01|Arie.Olshanezky%40microsoft.com|e47864f3acac402fa84a08d94da03baa|72f988bf86f141af91ab2d7cd011db47|1|0|637626172882235210|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=iS%2B%2FwDlOWpIcOq5URW20ZwPon1nupW0N9Rd2FW%2FCB0g%3D&reserved=0.

Please review breaking change report https://msazure.visualstudio.com/One/_workitems/edit/10420715/

Hi,
I created the breaking change work item
https://msazure.visualstudio.com/One/_workitems/edit/10420715/
Can someone please review?
Thanks, Arik.
From: openapi-workflow-bot[bot] @.>
Sent: Friday, July 23, 2021 9:40 AM
To: Azure/azure-rest-api-specs @.>
Cc: Arik Olsh @.>; Mention @.>
Subject: Re: [Azure/azure-rest-api-specs] Monitor privatelinkscopes accessmodesettings - api version 2021-07 preview (#15246)
Hi @arolshanhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Farolshan&data=04|01|Arie.Olshanezky%40microsoft.com|99a63b2ed7074a091dfc08d94da4a2e9|72f988bf86f141af91ab2d7cd011db47|1|0|637626191786692208|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=K8TOYQVSwbolpuCzjlNK9tinY9%2BEysTSeTOfc8%2FsW14%3D&reserved=0, Your PR has some issues. Please fix the CI sequentially by following the order of Avocado, semantic validation, model validation, breaking change, lintDiff.
Task
How to fix
Priority
Support (Microsoft alias)
Avocado
Fix-Avocadohttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2Favocado&data=04|01|Arie.Olshanezky%40microsoft.com|99a63b2ed7074a091dfc08d94da4a2e9|72f988bf86f141af91ab2d7cd011db47|1|0|637626191786702202|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=JzPBFHlMPCZbFcFPv9Z1n8zt71W0OcYjsn15vRn%2BGrs%3D&reserved=0
High
ruowan
Semantic validation
Fix-SemanticValidation-Errorhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2Fazure-rest-api-specs%2Fblob%2Fmaster%2Fdocumentation%2Fci-fix.md%23semantic-validation&data=04|01|Arie.Olshanezky%40microsoft.com|99a63b2ed7074a091dfc08d94da4a2e9|72f988bf86f141af91ab2d7cd011db47|1|0|637626191786712196|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=3WvDIu0%2FTfAE2K5vCMoleWe8j%2FImPgeCDMV%2B2MReenM%3D&reserved=0
High
raychen, jianyxi
Model validation
Fix-ModelValidation-Errorhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2Fazure-rest-api-specs%2Fblob%2Fmaster%2Fdocumentation%2Fci-fix.md%23model-validation&data=04|01|Arie.Olshanezky%40microsoft.com|99a63b2ed7074a091dfc08d94da4a2e9|72f988bf86f141af91ab2d7cd011db47|1|0|637626191786712196|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=bP4O%2BTnw0C6EUJN0hFdh%2B1e1skIBE0rt5h7FM0NnBxM%3D&reserved=0
High
raychen,jianyxi
LintDiff
Fix-LintDiffhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2Fazure-rest-api-specs%2Fblob%2Fmaster%2Fdocumentation%2Fci-fix.md%23linter-validation&data=04|01|Arie.Olshanezky%40microsoft.com|99a63b2ed7074a091dfc08d94da4a2e9|72f988bf86f141af91ab2d7cd011db47|1|0|637626191786722190|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=SOPi73xoa%2BGaQusCoC0ZIP0ZtmsbYC8tMONfEsm2j7c%3D&reserved=0
high
jianyxi, ruoxuan
If you need further help, please feedback via swagger feedbackhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Faka.ms%2Fswaggerfeedback&data=04|01|Arie.Olshanezky%40microsoft.com|99a63b2ed7074a091dfc08d94da4a2e9|72f988bf86f141af91ab2d7cd011db47|1|0|637626191786722190|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=M0gdQ%2BlCCpUSjiSti9jVBhOOtyfo5ly3NRE3e8KsoRQ%3D&reserved=0."

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2Fazure-rest-api-specs%2Fpull%2F15246%23issuecomment-885433436&data=04|01|Arie.Olshanezky%40microsoft.com|99a63b2ed7074a091dfc08d94da4a2e9|72f988bf86f141af91ab2d7cd011db47|1|0|637626191786732187|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=d0ZkK9C9dM%2FAH6O%2B1Q2HQuI2cfe9m3ecDnadpY0NxQo%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FALHNW5MLEZ5VAS4Q33J5CG3TZEFCNANCNFSM5AR6DEPA&data=04|01|Arie.Olshanezky%40microsoft.com|99a63b2ed7074a091dfc08d94da4a2e9|72f988bf86f141af91ab2d7cd011db47|1|0|637626191786732187|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=nVLrSWfhsORmZVc1IlxOx4iXhwBrdxmj2EEwawglLnI%3D&reserved=0.

Once the review is done, please work with @j5lim to finish the review or the next week's reviewer.


chore: update dependencies

Description

Workspace

update to latest Nx v15
update to latest Angular v14

Note: all changes in files other than package.json are due to Nx migrations
References

N/A

Codecov Report

Merging #1074 (5f67b66) into main (3c01078) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #1074   +/-   ##
=======================================
  Coverage   69.17%   69.17%
=======================================
  Files          18       18
  Lines         266      266
  Branches       25       25
=======================================
  Hits          184      184
  Misses         72       72
  Partials       10       10

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


If I use checkbox and dnd plugin cannot drag checked elements

I can drag unchecked elements but cannot drag cheked ones.
So I have to uncheck a checked element, then I can start dragging and at the end check it again.
Is this a known issue or something I´m doing wrong?

I can not reproduce the issue:
http://jsfiddle.net/DGAF4/2275/
Please update this fiddle so that the issue can be reproduced and I will reopen.

Here is my fiddle, hope you can see what im doing bad.
http://jsfiddle.net/DGAF4/2277/
Thanks in advance

I have absolutely no issue with dragging the selected elements. The drag is always initiated. Keep in mind by default jstree will drag the whole selection if a selected node is dragged - you may need to set this option to false (depending on your needs):
https://www.jstree.com/api/#/?q=drag&f=$.jstree.defaults.dnd.drag_selection
If this is not it - please describe the problem - what is happening and what do you expect to happen? Which browser are you using? Do you see any errors in the console?

seting this:
{"drag_selection":false},
as you reccomend solve my problem in my especific tree
Thank you very much.


[WIP] Self-referential links in markdown view

Resolves #261
Updates npm package react-markdown for self-referential link functionality
However, version 7 breaks the existing MLX UI code. We need to either find an older version that is compatible with MLX and has support for anchor IDs, or, change the MLX UI code to work with the latest version of react-markdown

Closing this in favor of PR #306


Misc cleanups to fwd.go

implement  gRPC server
remove logging

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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 68.951%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
3169

Relevant Lines:
4596

💛  - Coveralls


Using secret service in KDE Plasma5

Hello. Currently on KDE Plasma5 the secret service is not implemented by kwallet and I use KeePassXC feature for that purpose (apps like vscode, skype... need it for storing credentials). My question is can I implement such a service using your library? If not do you know the right library if exists. And if it is possible with your library can you provide a link to sample usage or a code sample. Thanks in advance.

As I understood your library is for client side of secret service. I need the server side.


feature Cache double deletion strategy

feature Cache double deletion strategy

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 91.25%.  Consider uploading reports for the commit da54ae7 to get more accurate results

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##           master      #11      +/-   ##
==========================================
+ Coverage   91.18%   91.25%   +0.07%
==========================================
  Files          22       23       +1
  Lines         465      469       +4
  Branches       86       87       +1
==========================================
+ Hits          424      428       +4
  Misses         19       19
  Partials       22       22

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


Authentication Error

I'm trying to run Ensta off of a PythonAnywhere server (Python 3.10.5) but I'm encountering this issue:
ensta.lib.Exceptions.AuthenticationError: Either user doesn't exist or your password is too weak (change it to a stronger one).
I've tried changing my password and using email, but it only seems to raise this issue on one specific server for one specific account. Is this a bug?

I'm not entirely sure why but the issue appears to have resolved itself.

If this issue persists, you'll have to use residential proxies.


Provide many sizes to counter

Re-factor css to resize counter,
and provide for exmaple 3 options:
Large, normal, small

Flipdown already supports two sizes, a regular and small variant. I'd appreciate a PR if you'd like to add more sizing options.


Fix download for container 0.17.36+

Hi all maintainers of this docker container.
Since 0.17.33 the website does not correctly represent the current version mentioned in the Dockerfile.
When I try to download the new version (docker pull dtandersen/factorio:0.17.36 it says it cannot find that image). although the dockerfile does seem to point to 0.17.36
Error:
$ sudo docker pull dtandersen/factorio:0.17.36
Error response from daemon: manifest for dtandersen/factorio:0.17.36 not found
Please correct the problem so we all can update... :)
Love the work, container is very stable and proper, just stuck now on 0.17.33...
Regards,   Stefan L

https://github.com/dtandersen/docker_factorio_server/issues/229#issuecomment-488607081


Adding support to ContainerizedVM

This PR adds the ContainerizedDebian class, which allows anyone to run benchmarks within a Ubuntu docker container. Every call to RemoteCommand runs within the Docker container via docker exec, whereas any call to RemoteHostCommand is guaranteed to run the command in the VM, outside the container.
This was only tested in GCE so far.

@ehankland

test this please.

("test this please" triggers our integration/unit tests)

Looks like our linter failed - can you please run "flake8" locally and fix the errors it gives you?

test this please.

@ehankland

test this please.

Fixed the issues from yesterday @ehankland

Thanks - seems to be working on a windows controller. One last question - are there any benchmarks that this doesn't work on? Or does it work for everything?

Awesome. I tested everything that doesn't require a .boto file (we weren't
very interested in that so I didn't spend time configuring that). It works
on all benchmarks but bonnie++ because it can't run as root by default. The
workaround for Bonnie++ is to add -u root but my adviser said this was
likely not a long term solution so I left it out of the PR.
On Friday, June 26, 2015, ehankland<EMAIL_ADDRESS>wrote:

Thanks - seems to be working on a windows controller. One last question -
are there any benchmarks that this doesn't work on? Or does it work for
everything?
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/PerfKitBenchmarker/pull/333#issuecomment-115826536
.

Can you document that you can't run bonnie++ with that VM type? Other than that, LGTM.


Make in browser version for testing

https://getpsalm.org
https://phpstan.org

Will be Rector CI :)
https://github.com/rectorphp/rector-ci


unable to compile example

Hi,
Thanks for your example. I have been unable to compile, and receive following error:
Showing Recent Messages
:-1: Multiple commands produce '/Users/brian/Library/Developer/Xcode/DerivedData/MapViewPlus-cqabsqclifgkyqgnhukrshycpcez/Build/Products/Debug-iphoneos/MapViewPlus/MapViewPlus.framework/.gitkeep':

Target 'MapViewPlus' (project 'Pods') has copy command from '/Users/brian/Documents/MapViewPlus/MapViewPlus/Assets/.gitkeep' to '/Users/brian/Library/Developer/Xcode/DerivedData/MapViewPlus-cqabsqclifgkyqgnhukrshycpcez/Build/Products/Debug-iphoneos/MapViewPlus/MapViewPlus.framework/.gitkeep'
Target 'MapViewPlus' (project 'Pods') has copy command from '/Users/brian/Documents/MapViewPlus/MapViewPlus/Classes/.gitkeep' to '/Users/brian/Library/Developer/Xcode/DerivedData/MapViewPlus-cqabsqclifgkyqgnhukrshycpcez/Build/Products/Debug-iphoneos/MapViewPlus/MapViewPlus.framework/.gitkeep'

I attempted to reinstall the Pod, compile the example. Tried removing derived data.
What is the process to clone the project and compile?
THanks,
Brian

I've just tried and been able to compile the example. I've just downloaded it as a zip (you can also run  git clone in terminal or clone it in your own way) and then double clicked the xcworkspace file and run the project.

Please delete your Derived Data folder and try again.


chore(Order/Birkhoff): remove unnecessary assumption

Remove the assumption that the type be a distributive lattice when partial order suffices in Birkhoff's representation theorem.
Co-authored by : Sam van Gool @samvang

Thanks!
bors merge


Use MVEL for rule evaluation (WIP - Not for review)

Description
We need to remove j-easy-rules to close #527. This PR demonstrates how trino gateway can use MVEL directly. It is only intended as a POC at this point. If the maintainers agree on this direction this work will be expanded to provide a replacement for RuleReloadingRoutingGroupSelector. Database support will be added as a follow up.
Note that the intent is only to replace the simple priority based control offered by easy-rules. Composite rules will not be supported.

Additional context and related issues

Release notes
( ) This is not user-visible or is docs only, and no release notes are required.
( ) Release notes are required. Please propose a release note for me.
(x ) Release notes are required, with the following suggested text:
TBD

Have not looked but removing one layer of indirection that just adds security issues and a bunch of syntax sugar seems like a good idea.

Can you ask in the maintainers group about any potential suggestion or preference for a rules engine

I agree to remove the unmaintained easy-rules and the support for composite rule.
However, I think the abstraction for multi-engine support is overkill at this moment.
It's difficult to make a good abstraction when we only have one case to support.
We can add an abstraction later when we decided to add another engine.

Do the rest of the examples and rules are taken care by your 'MVEL adapter'?

@vishalya it is tested with all the rules in https://github.com/willmostly/trino-gateway/tree/will/mvel-rules/gateway-ha/src/test/resources/rules. I think your issue is that trinoRequestUser.getUser() returns an Optional, so that condition will always be false. You can use trinoRequestUser.userExistsAndEquals(\"will\") instead.

@oneonestar ptal, I've refactored to remove abstractions for multi-engine support, with the exception of an interface to define the form of a rule.


[7.x.x] Bump Dependencies #4773483150

Bumps dependencies for product-is. Link : https://github.com/wso2/product-is/actions/runs/4773483150

 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.jenkins-is-staging seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

duplicate of https://github.com/wso2/product-is/pull/15767


Validate IDs for feedback API calls beyond demonstrations

In #343, we started validating that demonstrations apply to valid inferences. We can extend the same logic to other types of feedback.
In #599, we added validation for all inferences. Now we're missing validation for episodes.

Hi,
I would like to pick this up.
Can you please elaborate the exact feature request and some pointers for me to explore?

Great @hk1997!
In gateway/src/endpoints/feedback.rs, you'll see what write_demonstration has get_function_name_from_inference_id. This function throws an error if the inference ID doesn't exist.
We'd like to do the same for other types of feedback (boolean metrics, float metrics, comments).
(Later, we'll also want validation for episode IDs, but let's make that incremental on a separate PR, since it'll likely require a database migration which will be more complex.)

@GabrielBianconi Thanks for the detailed response.
A common worklfow for other types looks as follows:
  1. We need to validate if inferenceid is valid by checking that the function name exists.
  2. Check that the MetricConfigLevel is Inference?

Am I understanding it correctly?

@hk1997 The logic should be something like:
if MetricConfigLevel is Inference {
    // make sure that inference ID exists...
    // (can reuse `get_function_name_from_inference_id` or do something similar)
} else {
    // TODO: skip for now (later we'll want to verify episode IDs but I think that'll require a DB migration)
}

(Demonstrations always correspond to inferences, so that code path doesn't have the "if" right now.)

Where can I find all the tables in tensorzero?
I'm looking if a table exists for Episodes similar to that of inferences (InferenceById).
I'm thinking about building a common utility function that will return something similar to function_name for an episode as well at a later stage.

@hk1997 https://www.tensorzero.com/docs/gateway/data-model
We don't have an EpisodeById materialized view yet. For the second piece (validating episodes), we'll need that. Below is the migration that created InferenceById, so we'll need the same for episodes:
https://github.com/tensorzero/tensorzero/blob/main/gateway/src/clickhouse_migration_manager/migrations/migration_0001.rs
It probably makes sense to split this issue into 2-3 incremental PRs: validate all inferences → migration for EpisodesById → validate all episodes.

@GabrielBianconi How can I insert dummy data in InferenceById table during unit tests.
I'm building this utility method which will be called from all other handlers.
// Validates the target id and returns the identifier for the target.
// The identifier will be function name for inference level metrics.
async fn get_target_identifier(connection_info: &ClickHouseConnectionInfo, metric_config_level: &MetricConfigLevel, target_id: &Uuid)-> Result<String, Error>{
    match metric_config_level {
        MetricConfigLevel::Inference => {
            let query = format!(
                "SELECT function_name FROM InferenceById WHERE id = '{}'",
                target_id
            );
            let function_name = connection_info.run_query(query).await?.trim().to_string();
            if function_name.is_empty() {
                return Err(Error::new(ErrorDetails::InvalidRequest { message: format!(
                    "Inference ID: {target_id} does not exist"
                )})).into();
            };
            return Ok(function_name);
        }
        MetricConfigLevel::Episode => {
            // TODO: Implement this later as it might require db migrations.
            return Ok("".to_string());
        }
    }
}

Some of the UTs are failing as the InferenceById table won't be populated.

hey @hk1997 we don't assume access to ClickHouse for unit tests because we want them to be something that you can run in the binary at all times (precommit, etc).
So in order to actually test the ClickHouse integration you'll have to write an e2e test instead that runs an inference before trying to do feedback. We currently do this here for demonstrations and I believe you should be able to test the other types of metric by adding similar tests for inferences with float, comment, and bool feedback.
One thing we don't test right now (and should!) is that the feedback requests are rejected with 400 if the ID doesn't exist. It would be worth doing this as well (as in, try a feedback request, make sure it fails, run an inference, then apply feedback to that inference).
Let me know if you have any questions!

How can I run integration tests locally?

@hk1997 We need to document things like this better for future contributors... apologies.

Launch the test ClickHouse instance:

docker compose -f gateway/tests/e2e/docker-compose.yml up --wait

Set the relevant environment variable:

export CLICKHOUSE_URL="http://localhost:8123/tensorzero"

Launch the gateway

cargo run-eye

Run the E2E tests

cargo test-e2e

The above will run all of them, which will require every possible API key. You can run a small subset like cargo test-e2e xyz, which will run all tests that include xyz in the test name.

Let me know if you have any issues.

When trying to run:
cargo run-e2e xyz

It is still asking me to configure all API keys.
How do I avoid this?

@hk1997 Ah true, it'll check if they are set when you launch the gateway because you've defined those providers.
You have to set all the provider environment variables below. If you're not using those providers (skipping the relevant tests), you can set them to anything (e.g. OPENAI_API_KEY="none").
https://github.com/tensorzero/tensorzero/blob/main/examples/production-deployment/.env.example

Oh the error might be about GCP Vertex AI (since it's a file).
I just drafted a small developer guide here: #574
I also just set up the repo from scratch using the following variables (in .envrc):
export CLICKHOUSE_URL="http://localhost:8123/tensorzero"

export ANTHROPIC_API_KEY="none"
export AWS_ACCESS_KEY_ID="none"
export AWS_REGION=us-east-1
export AWS_SECRET_ACCESS_KEY="none"
export AZURE_OPENAI_API_KEY="none"
export FIREWORKS_API_KEY="none"
export GCP_VERTEX_CREDENTIALS_PATH=".credentials/credentials.json"
export GOOGLE_AI_STUDIO_API_KEY="none"
export HYPERBOLIC_API_KEY="none"
export MISTRAL_API_KEY="none"
export OPENAI_API_KEY="none"
export TOGETHER_API_KEY="none"
export VLLM_API_KEY="none"
export XAI_API_KEY="none"

And added the following fake credentials file to .credentials/.credentials.json:
{
  "type": "service_account",
  "project_id": "none",
  "private_key_id": "none",
  "private_key": "-----BEGIN RSA PRIVATE KEY-----\nMIICXAIBAAKBgQDAKxbF0dfne7PmPwpFEcSi2JFBeO98DXW7bimAPE6dHHCkDvoU\nlD/fy8svrPU6xsCYxM3LfKY/F+s/P+FizXUQ6eDu5ipYCRfweiQ4gqms+zROeORA\nJez3zelPQ7vY/MYCnp0LYYCH2HTyBeMFIX+Rgwjral495j0O6uV7cjgneQIDAQAB\nAoGAOXcpMjLUS6bUX1AOtCTiFoiIt3mAtCoaQNhqlKx0Hct5a7YG1syWZUg+FJ22\nH8N7qLOBjw5RcKCoepuRvMgP71+Hp03Xt8WSpN1Evl6EllwtmTtVTTeVS8fjP7xL\nhc7XemtDPY/81cBuj+HCit9/+44HZCT9V3dV6D9IWWnc3mECQQD1sTvcNAsh8idv\nMS12jmqdaOYTnJM1kFiddRvdkfChADq35x5bzV/oORYAmfurjuPN7ssHvrEEjmew\nbvi62MYtAkEAyDsAKrWsAfJQKbraTraJE7r7mTWxvAAYUONKKPZV2BXPzrTD/WMI\nn7z95pUu8x7anck9qqF6RYplo4fFLQKh/QJBANYwsszgGix33WUUbFwFAHFGN/40\n7CkwM/DhXW+mgS768jXNKSxDOS9MRSA1HbCMm5C2cw3Hcq9ULpUjyXeq7+kCQDx1\nvFYpJzgrP9Np7XNpILkJc+FOWk2nRbBfAUyfHUqzQ11qLef8GGWLfqs6jsOwpFiS\npIE6Yx5ObORVIc+2hM0CQE/pVhPEZ3boB8xoc9+3YL+++0yR2uMHoTY/q6r96kPC\n6C1oSRcDX/MUDOzC5HCUuwTYhNoN3FYkB5fov32BUbQ=\n-----END RSA PRIVATE KEY-----\n",
  "client_email": "none",
  "client_id": "114469363779822440226",
  "auth_uri": "https://accounts.google.com/o/oauth2/auth",
  "token_uri": "https://oauth2.googleapis.com/token",
  "auth_provider_x509_cert_url": "https://www.googleapis.com/oauth2/v1/certs",
  "client_x509_cert_url": "https://www.googleapis.com/robot/v1/metadata/x509/vertex%40tensorzero-public.iam.gserviceaccount.com",
  "universe_domain": "googleapis.com"
}

Everything worked for me with this setup. Let me now if you have any issues.

This is quite painful so we'll work towards smoothening this experience: #575 - sorry about that!

That's okay, probably this bug will be blocked on that issue.
Can I pick that up first, and later return to this issue?

Thanks @GabrielBianconi , it works with the suggestions in https://github.com/tensorzero/tensorzero/issues/350#issuecomment-2561273330

In #599, @hk1997 added validation for all inferences. :)
Now we're only missing validation for episode IDs.

Yes,
We may need to build a table for episode ids, can you provide more details on how an episode is different from inference for tensorzero?

An episode is a collection of inferences:
https://www.tensorzero.com/docs/gateway/guides/episodes
The next step would be to build an EpisodesById materialized view.
It'll be similar to InferenceById but will be a lot more complex due to the aggregations.
We should store the data required for this upcoming view:
https://v0.dev/chat/Wm09BBMvtxp?b=b_PfOppYLYmpk
This will likely require an AggregatingMergeTree in ClickHouse to be computed efficiently:
https://clickhouse.com/docs/en/engines/table-engines/mergetree-family/aggregatingmergetree
For that, we'll need a migration, similar to:
https://github.com/tensorzero/tensorzero/blob/main/gateway/src/clickhouse_migration_manager/migrations/migration_0001.rs
Before you implement it fully, it might be best to just write out the SQL queries for ClickHouse for us to confirm we're all on the same page. And then write out the migration. We'll need extensive tests since it's pretty complex.
(@virajmehta was also planning to write this migration in the next week or two since we'll need it for the UI, in case you prefer to wait for that.)

@GabrielBianconi @hk1997 I think it would be best if I tackled this one — ClickHouse is pretty tricky and we have to do a lot of different kinds of testing to make sure things are nailed down. I can tackle this in the next day or rwo

Sounds good, @virajmehta will write the migration and @hk1997 can resume this issue after that merges.

thanks @virajmehta

@hk1997 the migration was just merged -- feel free to keep on chugging on validating episodes. One thing to note is: we realized the sleeping till inference writes was a bad interface design to put on the developer, so in this PR we added a fix for that. I think you should be able to easily use the same solution for your next PR by taking advantage of throttled_get_target_identifier in your code too.


[core] rlImGUI needs a way to consume input

Issue description
When you click inside an ImGui window, that click should be "consumed" by ImGUI and not delivered to the app (ie: IsMouseButtonPressed() should return false after that, GetMousePosition() should stop updating).
The current Raylib API doesn't allow this.
Corresponding issue in rlImGui: https://github.com/raylib-extras/rlImGui/issues/63

@JeffM2501 you implemented rlImGUI example, did you find some way to address this issue?

This is no how ImGui works. you are supposed to check ImGui if it wants the device input or not. The IO has want key and want mouse fields. If ImGui wants the device, it's your job not to check the underlying platform. It's not the job of rlImGui to change event states in the underlying platform. ImGui does not assume that the underlying platform even has events.
This is a user error issue not a missing feature in raylib.

@albertvaka I have a working version of rlImGui but I don't know if it suffers from this disease...


Depth map inpainting

Thanks for your work, I was reading the ”DepthLab“ paper and was curious about the Fig.3 depth results, e.g. how is depth anyting v2 used to implement the depth complementation task? Is there any comparison made if the depth is predicted directly using RGB image, which as usual will have better smoothed boundaries?

Thank you very much for your interest in our work. In fact, traditional monocular depth estimators do not possess the ability to complete depth information. Therefore, their pipeline involves monocular depth estimation followed by alignment based on scale. In the visualization results, we have reattached the known areas to better demonstrate their discontinuities. That is to say, even after alignment, there are still discontinuities with the true depth, which is one of the significances of our work.

Thank you for your reply, can you please provide the corresponding inference code? I'd like to test the results and it will help me in my future work.


Add overlay

This PR makes the library useable as an overlay.
It also enables aarch64 runs with flake-utils.
I did however not test aarch64 as i don't have a strong aarch64-linux system handy.
My intention to have an overlay is more of

being able to use this without flakes
inside a flake that already uses overlays, just inject this one too instead of having it import nixpkgs another time

Please let me know what you think.

It seems like the aarch64 versions don't work because some packages are even unsupported. Please let me know if the overlay thingy is acceptable at all. If yes, then this is worth fixing by at least disabling what can't work in the CI and i'll do it.

I'm also fine with this, but we should drop the second commit. Quoting "archives.fedoraproject.org":

Note: The Fedora releases here are no longer supported or maintained, so they do not receive bug fixes or security updates. We do not recommend using these releases any more. To obtain the latest, supported version of Fedora, please refer to the main download page.

I'm also fine with this, but we should drop the second commit. Quoting "archives.fedoraproject.org":

Note: The Fedora releases here are no longer supported or maintained, so they do not receive bug fixes or security updates. We do not recommend using these releases any more. To obtain the latest, supported version of Fedora, please refer to the main download page.

I added this PR because the old URL doesnt work any longer. I am however happy to drop this commit and add either another one or rebase onto a fixed main branch.

@zimbatm I added the overlay in the overlays attribute and dropped flake-utils all along as it currently only correctly evaluates on intel machines anyway.
@picnoir plz forget what i said about the download mirror. I swear, yesterday the old url gave me 404 errors and when i browsed to it, the readme in the server's folder refered me to the other URL. And today it all just works again. However, i dropped the commit and everything works fine.

@zimbatm I am happy to update the documentation, although i am not sure how to do that best.
The README you mentioned does not really show how to use it all, so i would add an example under docs/? If yes, would you like an extra paragraph in the existing docs or its own document that contains an example with/without flakes that uses the overlay?

yeah, I think an extra paragraph in the getting started section would be good enough. Flake is the main use-case, but by the way, if you're not, here is a side-note on how to use it.

@zimbatm done

This should probably be in the reference, the getting started section is meant to be read from top to bottom in a interactive way.
But let's address that in a subsequent commit.

But let's address that in a subsequent commit.


Really nice didactic resource

Hi,
I am using this "issue" to actually just say thank you. I've skimmed through and to me this feels a more didactic and pleasant resource than the current Wix3 tutorial for newcomers.
Well done.

Hi @jmp75,
Thank you for your kind comments. From my experience, it is not easy to find good how-to guides on various things related to WiX, so I wanted to contribute something in this area based on my experience with WiX. While I did not cover a lot of things WiX can do, I am glad that the things I did cover people find useful.
Thank you once again.

+1
I have to say this is way more beginner friendly than the actual documentation which does not really explain how to do simple things. I watched so many videos of people just using some GUI version of wix but this actually explains what the Tags and Attributes do.
Thanks!!

This was indeed extremely helpful for me, thank you! A few suggestions:

Update the schema and tutorial 00 to v4
Cover common MSI options like Start Menu and Desktop shortcuts, preventing installing multiple of the same MSIs.


 It's insane to see how much has been pulled off since the last time I checked the project couple months ago.
I do have a remark. When I run npm init for the first time, it is not obvious to me what the different choices are.
[jlengrand@juliens-MacBook-Pro:~/IdeaProjects]$ npm init @open-wc
npx: installed 27 in 1.326s
What would you like to do today?
  > Scaffold a new project
What would you like to scaffold?
Note: Content will be written in a new folder.
    Barebone App
    Starter App
  > Enterprise App (if you feel lost use the Starter App first)
    Lit Element Web Component
    Mono Repo for web components

Even having worked with open-wc a little bit in the past, I am not sure what the difference is for example between the barebone app and the Lit Element Web Component.
I've been browsing around the website, but could not find a place where those are described in an obvious manner.
I might have missed it, but I'd appreciate something like

Starter app : perfect if you have a simple side-project, ......
Lit element Web Component : Use this if you want to create a single component. No router will be added, ....

Basically, when do I choose what?
Great job folks, keep it up :).

The purpose of each individual generator is described here: https://open-wc.org/developing/create.html#usage
But I do agree we could improve on the experience of the generator a little bit. (e.g.: there's also an option for Enterprise App that doesn't even exist yet). So there's some work to be done there. I can take a look when I come back from my vacation, or anybody else can pick this up and make a PR if they want :-)
Maybe we can even add a link to that page, actually. Something like: "Want to learn more about what the generators do? Visit open-wc.org/developing/create" or something.

Hey that looks exactly like what I was searching for.
Adding a link to the command line tool to help people would be enough I feel. I'll check how fast I'm done with my stuff today and come back to it if I have time. No promises though <3.
Enjoy Twitch Conf!

Alright, just spent some time trying to implement this. However, I can't run the tests locally (getting hundreds of errors about missing files in packages
ERROR in ./packages/testing-helpers/test/lit-html.test.js
Module not found: Error: Can't resolve '@bundled-es-modules/chai' in '/Users/jlengrand/IdeaProjects/open-wc/packages/testing-helpers/test'

is a small example.
Given that I cannot run the tests, nor have any idea how to locally run the altered cli I do not feel confident implementing it, no matter how simple it is.

did you install with npm i? we require yarn install as we use yarn workspaces in combination with lerna...
oh now that I see it - we definitely need to update the contribution guide 🙈

Yeah I've ben fighting quite a bit with your setup.
Now still blocked on multiple dependencies that are required in global scope (mocha, eslint, ....) and that prevent me from committing :P.
If I ever get past through your pre-commit hooks I might be able to send a PR :)

You are really not making my work easy :).

that should be all you need
git clone git@github.com:open-wc/open-wc.git
cd open-wc
yarn install
yarn test

to get up and running... 😬
hehe yeah... unfortunately a necessary evil 😅

We need lots of tooling to give people a (as much as possible) tooling free dev setup. It's quite ironic.

Looking into it @daKmoR .

Alright, you are correct @daKmoR . I had an old version of yarn and used npm install instead to save some time. Looks like I didn't in the end.
Everything works fine using yarn.

Fixed by https://github.com/open-wc/open-wc/pull/375

fixed with the new generator flow 💪
it's still not 100% clear as with the feature options now there is not much difference between starter-app / barebone-app / web component... would be nice to converge and bring needed options just to the feature selection... => but that's a task for another time

Hum well if it's not 100% clear then you have to explain me how the issue
is fixed 😂
On Wed, 17 Apr 2019, 12:40 AM Thomas Allmer<EMAIL_ADDRESS>wrote:

fixed with the new generator flow 💪
it's still not 100% clear as with the feature options now there is not
much difference between starter-app / barebone-app / web component... would
be nice to converge and bring needed options just to the feature
selection... => but that's a task for another time
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/open-wc/open-wc/issues/370#issuecomment-483870139,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA4QQvO-copOWN9AlDb9GqIpVATI8oyqks5vhlE_gaJpZM4crnu7
.

iirc we added a link to the docs in the generator right? People can find more info about individual generators there

Alright I know this is closed already but I finally took the time to update and check and yes, it is pretty obvious now what is what.
Great job!


update python config guide

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[ ] 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

[ ] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
Adding a new service

[ ] Please 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 there are following updates in the PR, ensure to request an approval from API Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[ ] Updating API in stable version with Breaking Change Validation errors
[ ] Updating API(s) in preview over 1 year

Please follow the link to find more details on PR review process.

/azp run automation - sdk

HI @msyyc,  can you sign off this PR?
Hi @changlong-liu , you may need to reply @qiaozha 's comments

HI @msyyc,  can you sign off this PR?
Hi @changlong-liu , you may need to reply @qiaozha 's comments

yes, updated in latest commit. @qiaozha , @msyyc, @akning-ms

yes, updated in latest commit. @qiaozha , @msyyc, @akning-ms

LGTM

LGTM

looks there some conflict, @changlong-liu can you resolve it first?

Hi @akning-ms , the conflict resolved. Shall we merge this PR? Thanks.


[Enhancement]: Eliminate several issues of com.datasophon.api.master.ActorUtils

Which chapter do you think needs improvement?
1、remove unnecessary imports.
2、provide a private no-argument constructor.
3、"seconds" should be eliminate.
What information do you think needs to be added?
No response

1


Feature Hierarchy Condensing / Improvements

When setting up feature relationships, it would be good to have a way to do a mass amount of relationships at once, rather than needing a unique utility combo for every relationship.
Once such example: I have been using utility features to create hierarchy relationships to make setting further utility relationships easier. One utility feature is "Infinite mana", which is intended to encompass all infinite mana results that are unconditional, such as infinite colored mana, infinite red mana, infinite blue mana etc. This way, I can set a single utility combo requiring infinite mana versus needing a separate combo for each infinite mana result. As an example, "Infinite mana + Myr Turbine -> Infinite creature tokens + Infinite ETB" versus needing one for infinite white, infinite blue, etc.
The issue with this is denoting that all of the infinite mana results are included in the infinite mana feature. Currently, I have to make individual utility combos to do this. So "Infinite white mana -> Infinite mana", "Infinite black mana -> Infinite mana" and so forth. It'd be good to make one place that will establish all of these relationships. This has several benefits. First, it's much easier to update them all at once if they are all in the same place. Second, it keeps the number of utility combos down, making them easier to manage. Third, it saves on memory and database storage, only needing at most one combo as opposed to dozens.
I have two ideas how to do this:

We add a new list to the Feature page which allows us to set "child" features. So on the "Infinite mana" feature page, I could set the children to be "Infinite white mana", "Infinite blue mana" and so forth. Then the program would automatically add all parent features to any combo the children are produced, essentially acting as a utility combo but without needing to set up a utility combo. I think this is probably the easier of the two options, both for programming sake and for UI sake. We can just edit the list on this page as necessary.
We create a utility combo with the ability to state that only one of the provided features are required for the relationship to be true. This can be done via a toggleable setting or possibly by a new classification of combos that tell the generator to do this. So we would list every possible "included" result in the Features required section, and then toggle the setting or classify it, and the program would essentially break it down into the separate instances. So I could specify "Infinite white mana" and "Infinite blue mana" as the required features, with "Infinite mana" as the produced feature, and the program would recognize that both "Infinite white mana" or "Infinite blue mana" independently produce infinite mana.

One thing I thought about after typing is multi-level hierarchies, but I don't see where supporting a multi-level hierarchy would provide us a massive benefit.
Example: "Infinite mana" is the parent of "Infinite colored mana". "Infinite colored mana" is the parent of "Infinite white mana", "Infinite blue mana" and so forth. While this is technically a hierarchial relationship, we track these results separately on the site, so we can't lump it together. Therefore we can't establish a multi-level hierarchy here.
So unless someone comes up with a tangible example of a multi-level hierarchy that we can't work around, we should only need to look one layer deep, i.e. parent -> child, instead of needing to do parent -> child -> child of child...


The allowlist ids are not stable

Our daily security scan for our Node.js projects failed today because the ids in our .audit-ci.json files no longer match the ids of the NPM advisory/GitHub vulnerability database.
A good example is CVE-2020-15168. We we added the allowlist entry for this vulnerability on Nov 4, the id was 1003055. Today it's failing because the id is now 1005560.
I'm guessing this is a side effect of the recent move to use the GitHub Advisory Database as the backend for npm audit.
Maybe it would be better to identify the vulnerabilities by CVE, which is a more stable identifier?

We've also been bit by the IDs changing a few times since GitHub's ownership change now.
Does every vulnerability in the database have a CVE? It looks like here's maybe a few examples of ones that don't have CVEs: https://github.com/advisories/GHSA-r8hm-w5f7-wj39, https://github.com/advisories/GHSA-pjwm-rvh2-c87w, https://github.com/advisories/GHSA-xx4c-jj58-r7x6 So with GitHub's ownership, would using the github_advisory_id (eg, GHSA-xx4c-jj58-r7x6) as a stable identifier be better?
I'm not sure if these NPM IDs changing is expected behavior now, but if extra context helps, here is a specific example of how these IDs have changed for CVE-2021-33623:

~ 2021-10-08: 1753 became 1002624
~ 2021-11-18: 1002624 became 1005151
~ 2021-12-03: 1005151 became 1006754

Note that only the original and latest IDs seem to work at the https://npmjs.com/advisories/* URLs (and the ones in between now result in 404s).

I started with a rough PullRequest #217
But that change would be a breaking one, so only for a major version change in my opinion!

Maintainer here! I agree that this should be resolved, and I like the proposal for using the GitHub identifiers. I would accept a PR that added support for GitHub identifiers. I may find some time in the next coming weeks to resolve the issue myself if a PR is unavailable.

I am fairly naive to these, but it seems like the created date keeps getting updated to today's date, while the updated date stays constant? And that generates a new id. That's weird and confusing!

FYI change to use GitHub-advisory-ids was merged and will be in 6.0.0 #217

Closing since I am releasing 6.0.0 ASAP and have a few RCs in the meantime 👍🏻


Push Notifications

Wondering if there is any documentation or help with integrating push notifications.  Thanks!
Help us reproduce - tell us about your environment

Steps to reproduce

Expected result

Actual result

[Screenshot, logs]

You could try the Expo docs


Bug: Nothing happen when clicking on "Import Device List"

Expected Behavior
When I want to import a device list, i should have a popup to select my csv file.
Current Behavior
Nothing happen when I click on it.
Context (Environment)
Portal version: 4.13.0

@adcoly please try the hotfix released in version v4.13.1.


[2.0-next] Replace lumber with log from stdlib

Lumber (https://github.com/jcelliott/lumber) seems to be pretty much dead in
the water. The last commit to master was from 2016.
Golangs stdlib logger pretty much provides everything we need out of the box,
so we should get rid of lumber and use log instead.

Fixed by #409


add notes param to known_failure

Small addition to the known_failure decorator. Just adds a freeform 'notes' attribute; it's not used in a meaningful way yet, but could be in the future, and might be better than comments for adding metadata like "this fails on 3.0+", which we can't handle at the moment.
@ptnapoleon to review.

Travis is mad for reasons unrelated to this PR:
https://travis-ci.org/riptano/cassandra-dtest/builds/96353608#L114

+1. I fixed the travis complaint, fyi.

Cheers!


No way to trigger signature help

The "overloads panel" is a thing, and so is "quick info", but there doesn't appear to be a way to trigger signature help manually without adding a set of parens.
Signature help as it exists is way more helpful to me than the overloads panel, and there's also no way to get signature help when typing out a tagged template.
We may also consider subsuming the overloads panel with the signature help popover.

It is added in master at e1bcaaf0980d8e09aa2ec9b9ae073b343e97f520. Try search for the command: "TypeScript: SignatureInfo"


Auto Apply FR Labels (enhancement) to this Issue Template.

Checklist

[X] I have filled out the template to the best of my ability.
[X] This only contains 1 feature request (if you have multiple feature requests, open one feature request for each feature request).
[X] This issue is not a duplicate feature request of previous feature requests.

Is your feature request related to a problem? Please describe.
I'm always frustrated manually applying FR labels.
Describe the solution you'd like
Labels automatically applying to this FR form.
Describe alternatives you've considered
Manually applying them. However, manual == prone to error.
Additional context
It appears that this form already has the label assigned to it. However, it does not populate it. I suspect the + is an unsupported char?   I fixed where I use this from to use enhancement but figured I should report upstream.

This is not upstream, this is an example.

Understood. It is a fantastic example.
Just pointing out that labels is not working as intended.


nbdev_update creates a new cell, instead of updating the original code

nbdev_update does not work as intended. It will create a new code cell, instead of updating the original code.
My use case:

python_module

a.py
b.py
...

nbs

a.ipynb
b.ipynb
...

If I make changes in a.py, and run nbdev_update, it will create a new code cell in a.ipynb, rather than updating code in this notebook.
version: 2.1.1

Thanks for reporting this.  I'm getting a different error: the code gets updated into the same cell, but it becomes a markdown cell without any directives.
@BirkhoffG do you mind sharing a repo or minimal example

Hi @hamelsmu, here is my repo:
https://github.com/BirkhoffG/counternet_jax
To reproduce the error:

make some changes in CounterNetTrainingModule in cfnet/training_module.py.
cd cfnet
nbdev_update training_module.py

@BirkhoffG I your project is a nbdev v1 repo.  Have you tried migrating this project to nbdev v2 yet?  Here is a migration guide: https://nbdev.fast.ai/migrating.html
Can you please try that and let us know if that helps?

Yes, at the time I reported the bug, I was using the v2 nbdev. I manually downgrade to v1 for now as this bug persists.
The snyc module in v2 seems to have some problems (e.g., #769), so I downgrade to v1 for now.

@BirkhoffG I believe your project is a nbdev v1 repo. Have you tried migrating this project to nbdev v2 yet? Here is a migration guide: https://nbdev.fast.ai/migrating.html
Can you please try that and let us know if that helps?

Yes, at the time I reported the bug, I was using the v2 nbdev. I manually downgrade to v1 for now as this bug persists.
The snyc module in v2 seems to have some problems (e.g., #769), so I downgrade to v1 for now.

To replicate the issue reported, go to the refactor branch, which is using nbdev v2.


Rna ingestion updates

This updates the parsing module to facilitate the ingestion of RNA data.
There are also minor updates, renaming some functions, rewriting some docstrings, and replacing instances of "sequence_<field>" to "sequencing_<field>", or "sequence" to "assay".

Any RNA samples / assays ingested should have four fields added to their sequencing group's meta.

Sequencing facility - sequencing_facility ('VCGS', 'KCCG', etc.)
Sequencing library - sequencing_library ('TSStrmRNA', 'TSStrtRNA', etc.)
Read end type - read_end_type ('paired', 'single')
Read length - read_length (some integer, almost all will be 150 or 151)

Exome samples / assays should also have the sequencing facility and library present in their sequencing group's meta, however this won't be enforced for the time being.

The main code changes:
sample_file_map_parser.py

Added the four above fields as optional columns in the sample file map
Added click optional args for those fields to provide default values
Added verbose option to print or not print the final json that gets ingested

generic_metadata_parser.py

Added get functions for the four fields which gets values from the columns in the sample file map being parsed, or from the parser defaults if set with the click options.
Updated get_assays_from_group function to add required fields tocollapsed_assay_meta, for exomes and RNA assays.
Added line that calls get_sequencing_group_meta_from_assays to add the assay meta fields to the sequencing group meta.

generic_parser.py

Added function get_sequencing_group_meta_from_assays - checks the assay.meta for the four fields and adds them to the sequencing_group.meta
Added get functions for the four fields which gets values from the parser defaults where needed
Added function prepare_detail - uses tabulate to print each sample being added, it's sequencing type, and how many assays are being ingested. This will be printed in favour of the json dump when verbose=false, e.g.:

+---------------+--------------+-------------------+----------+
| Participant   | Sample       | Sequencing Type   |   Assays |
+===============+==============+===================+==========+
|               | <sample-id>  | polyarna          |        1 |
+---------------+--------------+-------------------+----------+
|               | <sample-id2> | totalrna          |        1 |
+---------------+--------------+-------------------+----------+

Rename group_assays function to get_sample_sequencing_groups - since this function groups all sequencing groups for a sample based on the get_sequencing_group_key value, the old name did not really fit.

test_parse_file_map.py

Added test for valid RNA file map rows
Added test for invalid RNA file map rows
Added test for RNA file map rows where the field values for facility, library, end_type, and read_length are not present in the file map, but instead instantiated with the default field value parser options.

requirements.txt

Add tabulate package requirement (for printing the "detail" view which summarises each sample/participant row being ingested)

Codecov Report
Attention: 22 lines in your changes are missing coverage. Please review.

Comparison is base (08795fa) 68.68% compared to head (59715d3) 69.10%.

Files
Patch %
Lines

metamist/parser/generic_parser.py
83.58%
11 Missing :warning:

metamist/parser/generic_metadata_parser.py
93.42%
5 Missing :warning:

metamist/parser/sample_file_map_parser.py
82.35%
3 Missing :warning:

scripts/parse_ont_sheet.py
57.14%
3 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##              dev     #676      +/-   ##
==========================================
+ Coverage   68.68%   69.10%   +0.41%
==========================================
  Files         131      131
  Lines       10255    10413     +158
==========================================
+ Hits         7044     7196     +152
- Misses       3211     3217       +6

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

Merging this into dev now. I'll see about adding a bumpversion commit and triggering a release next week, don't want to cause any issues on Friday afternoon. Cheers


Duplicate interface definition for class 'MSAbstractLog'

I integrated the frameworks in Objective-C and get error messages about duplicate MSAbstractLog, MSService, and MSServiceAbstract. They are present both in AppCenterCrashes.frameworks, AppCenterAnalytics.framework and/or AppCenter.framework.

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

ID: 2da79c5d-1cef-5ed1-9ea2-8fd7e8940ec7
Version Independent ID: 81f0e749-1909-072c-b84d-6e9c2ce1cfae
Content: HockeySDK for macOS Migration - Visual Studio App Center
Content Source: docs/transition/macos-sdk-migration.md
Service: vs-appcenter
GitHub Login: @elamalani
Microsoft Alias: emalani

We are taking a look to this.

Hi there @synalysis sorry for the delay! I can't see the errors you mentioned, could you please elaborate: what are you trying to do? Build, archive, run?
Please also share your environment details and project xcconfig would also be good to look at.

The problem occurs when I import headers from different frameworks like this:
#import <AppCenterCrashes/MSCrashes.h>
#import <AppCenterAnalytics/MSAnalytics.h>
The error is issued by the compiler.
Here you find more info about this issue: https://github.com/microsoft/appcenter-sdk-apple/issues/1734

Ok I see you my colleague already answered you there. Let's close this duplicate issue then, sorry for bothering!


all: update Go to v1.18.8

This PR release the docker base images on docker hub to have them generally available.
Release 22.11.01

all: update Go to v1.18.8
darwin-image: update LLVM and clang to v14

Images
The following images have been tagged and released on docker hub for testing:
1.3-android-2022.11.01
1.3-base-2022.11.01
1.3-base-freebsd-2022.11.01
1.3-base-llvm-2022.11.01
1.3-freebsd-amd64-2022.11.01
1.3-freebsd-arm64-2022.11.01
1.3-linux-386-2022.11.01
1.3-linux-arm-2022.11.01
1.3-linux-arm64-2022.11.01
1.3-web-2022.11.01
1.3-windows-2022.11.01

Note: the latest tag will tagged and pushed to docker hub as usual once approved

I have tested the web and linux(s) image. It does work for my tests.

The latest tag has been pushed to docker hub


fix:correct the JSON.SET command Arity

a tiny fix
in command.go there is :
`
jsonsetCmdMeta = DiceCmdMeta{
	    Name: "JSON.SET",
	    Info: `JSON.SET key path json-string
	    Sets a JSON value at the specified key.
	    Returns OK if successful.
	    Returns encoded error message if the number of arguments is incorrect or the JSON string is invalid.`,
	    Eval:     evalJSONSET,
	    Arity:    3,
	    KeySpecs: KeySpecs{BeginIndex: 1},

`
but we could add NX or XX so  the Arity should be -3
such as below:
JSON.SET user $ '{"name":"HuYiDao","age":18,"language":["java","python","go"]}'

JSON.SET user $.amount '1.26' XX

the ci fialed becasue in eval.go , the RESP_MINUS_2 and RESP_MINUS_1 has been deleted in #313 fixed , now it has been corrected in pr #315 .

Thanks a lot for the fix @jujiale. Could you please rebase on the latest master, the failing checks will automatically pass.

Thanks a lot for the fix @jujiale. Could you please rebase on the latest master, the failing checks will automatically pass.

ok ,I will do this


panic: token map different size to token ring: got 1536 expected 2048

Please answer these questions before submitting your issue. Thanks!
What version of Scylla or Cassandra are you using?
Scylla 4.1
What version of Gocql are you using?
github.com/scylladb/gocql v1.4.0
What did you do?
I enabled TokenAwareHostPolicy like it says in the readme to see if performance would improve. On my test cluster it worked fine, but when I deployed it to production all my servers panicked with this error:
panic: token map different size to token ring: got 1536 expected 2048
goroutine 1 [running]:
github.com/gocql/gocql.(*networkTopology).replicaMap(0xc00051c088, 0xc000598380, 0xc00051c088, 0x0, 0x0)
        /home/wim/Documents/workspace/go/pkg/mod/github.com/scylladb/gocql@v1.4.0/topology.go:273 +0x186d
github.com/gocql/gocql.(*tokenAwareHostPolicy).updateReplicas(0xc0001c2380, 0xc0003ca3a0, 0xc000023750, 0xa)
        /home/wim/Documents/workspace/go/pkg/mod/github.com/scylladb/gocql@v1.4.0/policies.go:457 +0x25f
github.com/gocql/gocql.(*tokenAwareHostPolicy).KeyspaceChanged(0xc0001c2380, 0xc000023750, 0xa, 0x0, 0x0)
        /home/wim/Documents/workspace/go/pkg/mod/github.com/scylladb/gocql@v1.4.0/policies.go:442 +0x99
github.com/gocql/gocql.(*Session).init(0xc000180700, 0xc0001a0380, 0x0)
        /home/wim/Documents/workspace/go/pkg/mod/github.com/scylladb/gocql@v1.4.0/session.go:280 +0x5ca
github.com/gocql/gocql.NewSession(0xc00024f260, 0x3, 0x3, 0xb01191, 0x5, 0x0, 0x2540be400, 0x12a05f200, 0x23b6, 0xc000023750, ...)
        /home/wim/Documents/workspace/go/pkg/mod/github.com/scylladb/gocql@v1.4.0/session.go:166 +0x809
github.com/gocql/gocql.(*ClusterConfig).CreateSession(...)
        /home/wim/Documents/workspace/go/pkg/mod/github.com/scylladb/gocql@v1.4.0/cluster.go:194

This actually brought the site down for a few minutes.

If you are having connectivity related issues please share the following additional information
Describe your Cassandra cluster
please provide the following information

output of nodetool status

Datacenter: eu-de
=================
Status=Up/Down
|/ State=Normal/Leaving/Joining/Moving
--  Address         Load       Tokens       Owns    Host ID                               Rack
UN  <IP_ADDRESS>  1.39 GB    256          ?       886551b1-7dbb-4ba3-8fe1-c388bd2fed53  rack1
UN  <IP_ADDRESS>  1.21 GB    256          ?       d8632268-2ec5-4f8a-bc33-5a20d8d8379d  rack1
UN  <IP_ADDRESS>     1.3 GB     256          ?       ce75f822-c8ec-4b81-9451-c6877b20ca3e  rack1
Datacenter: us-central
======================
Status=Up/Down
|/ State=Normal/Leaving/Joining/Moving
--  Address         Load       Tokens       Owns    Host ID                               Rack
UN  <IP_ADDRESS>    1.44 GB    256          ?       b1b386a7-9997-4ba6-a79f-b24c9efa43c9  rack1
UN  <IP_ADDRESS>  1.17 GB    256          ?       a9027bea-5f82-4380-bede-892f882d9d17  rack1
Datacenter: us-west
===================
Status=Up/Down
|/ State=Normal/Leaving/Joining/Moving
--  Address         Load       Tokens       Owns    Host ID                               Rack
UN  <IP_ADDRESS>     1.53 GB    256          ?       ac84d564-01b3-4e04-9161-83b14cad1cca  rack1
UN  <IP_ADDRESS>     1.53 GB    256          ?       7b5b00fe-b7b6-4f0c-a896-5f59fef09bb2  rack1
UN  <IP_ADDRESS>     1.57 GB    256          ?       4b4bb1de-bb90-4dc9-b879-2b6f730a565e  rack1

output of SELECT peer, rpc_address FROM system.peers

 peer           | rpc_address
----------------+----------------
    <IP_ADDRESS> |    <IP_ADDRESS>
 <IP_ADDRESS> | <IP_ADDRESS>
    <IP_ADDRESS> |    <IP_ADDRESS>
    <IP_ADDRESS> |    <IP_ADDRESS>
   <IP_ADDRESS> |   <IP_ADDRESS>
 <IP_ADDRESS> | <IP_ADDRESS>
 <IP_ADDRESS> | <IP_ADDRESS>

rebuild your application with the gocql_debug tag and post the output
Is this necessary?

From the numbers you have 8 nodes so the expectation 2048 is correct 1536 corresponds to 6 nodes.
Something happened to us-central?
Does it reproduce?
The panic comes from networkTopology, does it reproduce with other settings?

rebuild your application with the gocql_debug tag and post the output
Is this necessary?

That would hopefully allow to see what gocql is doing.

I have removed the us-central nodes from the cluster as I wasn't really using them. Now it seems to work. Before removing the nodes I ran nodetool repair -pr on both and they seemed okay, so that's strange. There are some other nodes in the cluster where repair didn't finish and returned an error instead. Still trying to figure out what happened there.
I think it might be using the fallback method now because in Grafana the "Non-token aware queries" number is still the same.

Anyway, the panic doesn't happen anymore, so I guess the issue can be closed.


No-op PR to trigger CI

My other PR #806 is failing in the Python 3.7 build and I'm unable to reproduce the failure locally, just creating a clean PR to verify that the CI build is good.

hey @alexholmes it seems the error is caused by this
Traceback (most recent call last):
  File "setup.py", line 22, in <module>
    from setuptools import setup, find_packages
  File "/home/travis/virtualenv/python3.7.1/lib/python3.7/site-packages/setuptools/__init__.py", line 18, in <module>
    from setuptools.dist import Distribution
  File "/home/travis/virtualenv/python3.7.1/lib/python3.7/site-packages/setuptools/dist.py", line 34, in <module>
    from ._importlib import metadata
  File "/home/travis/virtualenv/python3.7.1/lib/python3.7/site-packages/setuptools/_importlib.py", line 28, in <module>
    disable_importlib_metadata_finder(metadata)
  File "/home/travis/virtualenv/python3.7.1/lib/python3.7/site-packages/setuptools/_importlib.py", line 12, in disable_importlib_metadata_finder
    import importlib_metadata
  File "/home/travis/virtualenv/python3.7.1/lib/python3.7/site-packages/importlib_metadata/__init__.py", line 471, in <module>
    __version__ = version(__name__)
  File "/home/travis/virtualenv/python3.7.1/lib/python3.7/site-packages/importlib_metadata/__init__.py", line 438, in version
    return distribution(package).version
  File "/home/travis/virtualenv/python3.7.1/lib/python3.7/site-packages/importlib_metadata/__init__.py", line 411, in distribution
    return Distribution.from_name(package)
  File "/home/travis/virtualenv/python3.7.1/lib/python3.7/site-packages/importlib_metadata/__init__.py", line 179, in from_name
    dists = resolver(name)
  File "/home/travis/virtualenv/python3.7.1/lib/python3.7/site-packages/setuptools/_vendor/importlib_metadata/__init__.py", line 886, in find_distributions
    found = self._search_paths(context.name, context.path)
AttributeError: 'str' object has no attribute 'name'

I've created https://github.com/combust/mleap/pull/808 in an attempt to fix the build, i'm not too sure if it's the right way to solve it, so i'll wait for @jsleight to review. sorry for this, will take a look at https://github.com/combust/mleap/pull/806 as soon as the build is green

Thanks so much @ancasarb - your fix seems to have done the trick!

I shipped and merged Anca's branch, so let's close this PR and then you can rebase on master in #806


Add autoinstrumentation doc

Contributes to https://github.com/open-telemetry/opentelemetry.io/issues/972
I also tweaked the document order here. I thought it was weird that Context Propagation and Span Events came before Manual Instrumentation. Perfectly happy to revert that change and any other little tweaks I made though.

@cartermp Thank you for this contribution!
We (@robbkidd and I) decided to defer writing up documentation for customizing automatic instrumentation libraries when coming up with our initial draft because we thought it would be best to drive our users towards the goal of minimal customization to start. We also felt providing details about customizations up front would make this burdensome for our users.
We also tried to steer folks away from Manual Instrumentation, since we hope that the experience of using the SDK + auto-instrumentation would lead to generating insights quickly without requiring manual intervention from developers. Less code + deeper insights == win!
With that in mind we chose Context Propagation as the next step since it would flow into being able to provide our users with what we unlocks the power of OTEL Distributed Tracing.
Unlike the auto-instrumentation libraries, Span Events are part of the stable API and we hope to steer our users towards preferring them over other signals clears throat logs.
All that being said, I personally still feel like we need an "advanced configuration" section, where users who are comfortable adjusting the SDK configuration could use as a reference guide.
So my personal preference here would be to keep the original flow we had in place but incorporate the updates you have submitted as part of this PR in a "Advanced Configuration" section of sorts.
Thoughts?

@arielvalentin Happy to adjust as per preferences here. I will do the following:

Revert the structural tweaks
Make sure the Getting Started guide links to this new document, and in the context of "to learn more about how to configure automatic instrumentation, see ..." or something like that

Does that work?

Also, I'd like to start a discussion about future contributions:
This isn't squarely a otel-ruby problem, but in my work the number one issue being raised by our sales and customer success teams is that opentelemetry docs - specifically on how to do various things with different languages - is extremely sparse. This has been consistently the number one problem for a few months now. So, I wanna help solve that problem!
The major theme is that content and a sprinkling of guidance is just missing, or hard to find, or not linked to samples, or using an example that doesn't make sense. Some of that problem does come down to docs organization and preferences around guidance. I have my own opinions about that, but I'm more focused on making sure there is adequate conceptual content with code examples for major topics (auto instrumentation, getting current span, adding attributes to span, starting new span, starting nested span, getting/setting a trace properly, adding a span link, adding a span event, setting baggage, sampling, some config, etc.) - and figuring out the "how do we organize this?" problem incrementally.
So before I try and throw a bunch more PRs your way, maybe it's good to cover generally what I'd like to propose, and see where we align, so myself (and hopefully others!) can just get cranking on some more contributions.

@cartermp thank you very much for stepping in to help! When we started working on our initial documentation, @robbkidd and I struggled with writing just enough documentation and writing Head First OpenTelemetry and based on feedback you've been hearing it seems like we are still coming up short to consider it to be just enough.

figuring out the "how do we organize this?" problem incrementally

Although I agree that we will provide our users with a better experience by providing more content, I think it would be a good idea to engage folks as soon as possible in the docs repository to produce an outline or template for each language implementation to create a consistent experience for our users.
Does that sound reasonable?
cc: https://github.com/open-telemetry/opentelemetry-ruby/issues/775

@arielvalentin all feedback accounted for!

based on feedback you've been hearing it seems like we are still coming up short to consider it to be just enough.

Heh, well the good news is that it's pretty universal 😆 😭
I can make this a discussion item in this week's docs SIG. We have some items being tracked that hint at a general approach for each language SDK (e.g., https://github.com/open-telemetry/opentelemetry.io/issues/964) but no concrete proposal along the lines of "these are each of the major topics that are covered in each language SDK section and here's how they are roughly organized". I can propose that upstream and tag you and others.
In the interim, provided it's just in small-ish increments (and not messing with the existing structure here), would you be comfortable still taking PRs? For example, adding a small section in the manual instrumentation doc that shows how to create a nested span, or a span link.

Thanks @cartermp for following up with the docs SIG 🎉

ty for the awesome work here @cartermp

Looks like this one is passing CI - anything holding up a merge?

@cartermp no not really just a lot of PTO / OOO from folks here, we'll be sure to get this merged when everyone is back in action 2022


allow scrolling past last entry / first entry

watch the video

regular scrolling and tab scrolling NEEDS to be separated, without separation, we wont be able to properly handle subdir cases
Type of Change

[x] New feature

Description
wraps the user to the top of the list or to the bottom of the list depending on where they are at
example:
https://github.com/user-attachments/assets/567753aa-7725-4cce-b83c-966a868ea207

You missed 2, @lj3954

You missed 2, @lj3954

No, those are wrong. The item list can be empty if a search term not matching anything is entered. You should get a panic with those changes applied in that case.

Absolutely not. The item list can be empty, since a search can come up with no results. Only the tab list should be expected not to be empty.

Absolutely not. The item list can be empty, since a search can come up with no results. Only the tab list should be expected not to be empty.

idk bro just dmed me saying hes high

@nnyyxxxx i meant tall, not high. sorry.


[NVIDIA] Fix F16 -> F32 upcasting to support Pascal GPUs

Hello!
Despite knowing that compute capabilities below 7.0 are not officially supported, I kindly request the acceptance of this PR. It addresses a minor issue allowing open-source enthusiasts with older, more affordable server GPUs (such as the NVIDIA Tesla P40/P100) to utilize modern applications.
I understand there's no expectation for official support for these older GPUs, but perhaps it could be something like community support.
In addition, pytorch still supports Pascal GPUs, and pytorch depends on triton.
This PR fixes:
Unsupported conversion from f16 to f16
LLVM ERROR: Unsupported rounding mode for conversion.
There will be another small PR fixing the IR -> PTX compilation, which would be based on this commit (related issue: llvm/llvm-project#90421).
Here's the patched triton for the current release (2.3.0) if you want to explore, or backport/cherry-pick to 2.4.0 (as I understand it, the current main is something like triton 3.0.0). It only has two patches (one of which is this PR), and it completely works on the NVIDIA Tesla P40:
https://github.com/sasha0552/triton/tree/release/2.3.x%2Bpascal

Demonstration

This PR is based on the code provided by @wkpark in openai/triton#2780.
Related issues/PRs: vllm-project/vllm#2635, vllm-project/vllm#4290, vllm-project/vllm#4409, vllm-project/vllm#4438.
Thank you in advance.

I daunt we want to support Pascal

NVIDIA GPUs (Compute Capability 7.0+)

In principle I am not opposed to fixing up pascal issues if the added complexity is minimal, but here could you elaborate a little bit more on why the default code path is failing?

First, Pascal GPUs have very poor performance in fp16. (I think maybe it's important).
The crash happens in tl.dot, which generates tt.fp_to_fp (I think because of out_dtype=float32). There is no support for fp16 -> fp32 upcasting in this function.
https://github.com/openai/triton/blob/a263360050e1887a2cda0c2cac811ddd3ccaab1e/python/triton/language/core.py#L1505
As for the fpext that @ThomasRaoux mentioned, I think it's not used because there is simply no fp16 -> fp32, only bf16 -> fp32
https://github.com/openai/triton/blob/a263360050e1887a2cda0c2cac811ddd3ccaab1e/third_party/nvidia/lib/TritonNVIDIAGPUToLLVM/ElementwiseOpToLLVM.cpp#L698-L719
I'll try adding the conversion here instead of what was suggested in this PR and report back.

Code
import torch

import triton
import triton.language as tl

@triton.jit
def test_dot_kernel():
    t1 = tl.zeros([16, 16], dtype=tl.float16)
    t2 = tl.zeros([16, 16], dtype=tl.float16)
    d = tl.dot(t1, t2)
    tl.device_print("dot:", d)

grid = lambda meta: (1, )
kernel = test_dot_kernel[grid]()

Generated IR (?)
#blocked = #triton_gpu.blocked<{sizePerThread = [1, 1], threadsPerWarp = [2, 16], warpsPerCTA = [4, 1], order = [1, 0]}>
module attributes {"triton_gpu.num-ctas" = 1 : i32, "triton_gpu.num-warps" = 4 : i32, triton_gpu.target = "cuda:61", "triton_gpu.threads-per-warp" = 32 : i32} {
  tt.func public @test_dot_kernel() attributes {noinline = false} {
    %cst = arith.constant dense<0.000000e+00> : tensor<16x16xf32, #blocked> loc(#loc1)
    %cst_0 = arith.constant dense<0.000000e+00> : tensor<16x16xf16, #triton_gpu.dot_op<{opIdx = 0, parent = #blocked}>> loc(#loc1)
    %cst_1 = arith.constant dense<0.000000e+00> : tensor<16x16xf16, #triton_gpu.dot_op<{opIdx = 1, parent = #blocked}>> loc(#loc1)
    %0 = tt.fp_to_fp %cst_0 : tensor<16x16xf16, #triton_gpu.dot_op<{opIdx = 0, parent = #blocked}>> -> tensor<16x16xf32, #triton_gpu.dot_op<{opIdx = 0, parent = #blocked}>> loc(#loc2)
    %1 = tt.fp_to_fp %cst_1 : tensor<16x16xf16, #triton_gpu.dot_op<{opIdx = 1, parent = #blocked}>> -> tensor<16x16xf32, #triton_gpu.dot_op<{opIdx = 1, parent = #blocked}>> loc(#loc2)
    %2 = tt.dot %0, %1, %cst, inputPrecision = tf32 : tensor<16x16xf32, #triton_gpu.dot_op<{opIdx = 0, parent = #blocked}>> * tensor<16x16xf32, #triton_gpu.dot_op<{opIdx = 1, parent = #blocked}>> -> tensor<16x16xf32, #blocked> loc(#loc2)
    tt.print " dot: " {hex = false} : %2 : tensor<16x16xf32, #blocked> loc(#loc3)
    tt.return loc(#loc4)
  } loc(#loc)
} loc(#loc)
#loc = loc("/tmp/repro-1.py":7:0)
#loc1 = loc(unknown)
#loc2 = loc("/tmp/repro-1.py":10:19)
#loc3 = loc("/tmp/repro-1.py":11:28)
#loc4 = loc("/tmp/repro-1.py":11:4)

Stacktrace
Unsupported conversion from f16 to f16
LLVM ERROR: Unsupported rounding mode for conversion.
*** SIGABRT received at time=1715319299 on cpu 0 ***
PC: @     0x787e96bdb32c  (unknown)  (unknown)
    @     0x787e96b8a770      31888  (unknown)
    @     0x5dd359f26fb0  (unknown)  (unknown)
[2024-05-10 05:34:59,869 E 1941 2481] logging.cc:365: *** SIGABRT received at time=1715319299 on cpu 0 ***
[2024-05-10 05:34:59,870 E 1941 2481] logging.cc:365: PC: @     0x787e96bdb32c  (unknown)  (unknown)
[2024-05-10 05:34:59,871 E 1941 2481] logging.cc:365:     @     0x787e96b8a770      31888  (unknown)
[2024-05-10 05:34:59,872 E 1941 2481] logging.cc:365:     @     0x5dd359f26fb0  (unknown)  (unknown)
Fatal Python error: Aborted

Stack (most recent call first):
  File "/mnt/ml/vllm/venv/lib/python3.11/site-packages/triton/backends/nvidia/compiler.py", line 212 in make_llir
  File "/mnt/ml/vllm/venv/lib/python3.11/site-packages/triton/backends/nvidia/compiler.py", line 302 in <lambda>
  File "/mnt/ml/vllm/venv/lib/python3.11/site-packages/triton/compiler/compiler.py", line 282 in compile
  File "/mnt/ml/vllm/venv/lib/python3.11/site-packages/triton/runtime/jit.py", line 662 in run
  File "/mnt/ml/vllm/venv/lib/python3.11/site-packages/triton/runtime/jit.py", line 345 in <lambda>
  File "/mnt/ml/vllm/vllm/attention/ops/prefix_prefill.py", line 744 in context_attention_fwd
  File "/mnt/ml/vllm/venv/lib/python3.11/site-packages/torch/utils/_contextlib.py", line 115 in decorate_context
  File "/mnt/ml/vllm/vllm/attention/ops/paged_attn.py", line 177 in forward_prefix
  File "/mnt/ml/vllm/vllm/attention/backends/xformers.py", line 236 in forward
  File "/mnt/ml/vllm/vllm/attention/layer.py", line 48 in forward
  File "/mnt/ml/vllm/venv/lib/python3.11/site-packages/torch/nn/modules/module.py", line 1541 in _call_impl
  File "/mnt/ml/vllm/venv/lib/python3.11/site-packages/torch/nn/modules/module.py", line 1532 in _wrapped_call_impl
  File "/mnt/ml/vllm/vllm/model_executor/models/llama.py", line 167 in forward
  File "/mnt/ml/vllm/venv/lib/python3.11/site-packages/torch/nn/modules/module.py", line 1541 in _call_impl
  File "/mnt/ml/vllm/venv/lib/python3.11/site-packages/torch/nn/modules/module.py", line 1532 in _wrapped_call_impl
  File "/mnt/ml/vllm/vllm/model_executor/models/llama.py", line 233 in forward
  File "/mnt/ml/vllm/venv/lib/python3.11/site-packages/torch/nn/modules/module.py", line 1541 in _call_impl
  File "/mnt/ml/vllm/venv/lib/python3.11/site-packages/torch/nn/modules/module.py", line 1532 in _wrapped_call_impl
  File "/mnt/ml/vllm/vllm/model_executor/models/llama.py", line 291 in forward
  File "/mnt/ml/vllm/venv/lib/python3.11/site-packages/torch/nn/modules/module.py", line 1541 in _call_impl
  File "/mnt/ml/vllm/venv/lib/python3.11/site-packages/torch/nn/modules/module.py", line 1532 in _wrapped_call_impl
  File "/mnt/ml/vllm/vllm/model_executor/models/llama.py", line 364 in forward
  File "/mnt/ml/vllm/venv/lib/python3.11/site-packages/torch/nn/modules/module.py", line 1541 in _call_impl
  File "/mnt/ml/vllm/venv/lib/python3.11/site-packages/torch/nn/modules/module.py", line 1532 in _wrapped_call_impl
  File "/mnt/ml/vllm/vllm/worker/model_runner.py", line 809 in execute_model
  File "/mnt/ml/vllm/venv/lib/python3.11/site-packages/torch/utils/_contextlib.py", line 115 in decorate_context
  File "/mnt/ml/vllm/vllm/worker/worker.py", line 254 in execute_model
  File "/mnt/ml/vllm/venv/lib/python3.11/site-packages/torch/utils/_contextlib.py", line 115 in decorate_context
  File "/mnt/ml/vllm/vllm/worker/worker_base.py", line 137 in execute_method
  File "/usr/lib/python3.11/concurrent/futures/thread.py", line 58 in run
  File "/usr/lib/python3.11/concurrent/futures/thread.py", line 83 in _worker
  File "/usr/lib/python3.11/threading.py", line 982 in run
  File "/usr/lib/python3.11/threading.py", line 1045 in _bootstrap_inner
  File "/usr/lib/python3.11/threading.py", line 1002 in _bootstrap

Extension modules: numpy.core._multiarray_umath, numpy.core._multiarray_tests, numpy.linalg._umath_linalg, numpy.fft._pocketfft_internal, numpy.random._common, numpy.random.bit_generator, numpy.random._bounded_integers, numpy.random._mt19937, numpy.random.mtrand, numpy.random._philox, numpy.random._pcg64, numpy.random._sfc64, numpy.random._generator, torch._C, torch._C._fft, torch._C._linalg, torch._C._nested, torch._C._nn, torch._C._sparse, torch._C._special, charset_normalizer.md, yaml._yaml, psutil._psutil_linux, psutil._psutil_posix, sentencepiece._sentencepiece, msgpack._cmsgpack, google._upb._message, setproctitle, uvloop.loop, ray._raylet, ujson, regex._regex, scipy._lib._ccallback_c, numba.core.typeconv._typeconv, numba._helperlib, numba._dynfunc, numba._dispatcher, numba.core.runtime._nrt_python, numba.np.ufunc._internal, numba.experimental.jitclass._box, markupsafe._speedups, PIL._imaging, scipy.linalg._fblas, scipy.linalg._flapack, scipy.linalg.cython_lapack, scipy.linalg._cythonized_array_utils, scipy.linalg._solve_toeplitz, scipy.linalg._decomp_lu_cython, scipy.linalg._matfuncs_sqrtm_triu, scipy.linalg.cython_blas, scipy.linalg._matfuncs_expm, scipy.linalg._decomp_update, scipy.sparse._sparsetools, _csparsetools, scipy.sparse._csparsetools, scipy.sparse.linalg._dsolve._superlu, scipy.sparse.linalg._eigen.arpack._arpack, scipy.sparse.linalg._propack._spropack, scipy.sparse.linalg._propack._dpropack, scipy.sparse.linalg._propack._cpropack, scipy.sparse.linalg._propack._zpropack, scipy.sparse.csgraph._tools, scipy.sparse.csgraph._shortest_path, scipy.sparse.csgraph._traversal, scipy.sparse.csgraph._min_spanning_tree, scipy.sparse.csgraph._flow, scipy.sparse.csgraph._matching, scipy.sparse.csgraph._reordering, scipy.optimize._minpack2, scipy.optimize._group_columns, scipy._lib.messagestream, scipy.optimize._trlib._trlib, scipy.optimize._lbfgsb, _moduleTNC, scipy.optimize._moduleTNC, scipy.optimize._cobyla, scipy.optimize._slsqp, scipy.optimize._minpack, scipy.optimize._lsq.givens_elimination, scipy.optimize._zeros, scipy.optimize._highs.cython.src._highs_wrapper, scipy.optimize._highs._highs_wrapper, scipy.optimize._highs.cython.src._highs_constants, scipy.optimize._highs._highs_constants, scipy.linalg._interpolative, scipy.optimize._bglu_dense, scipy.optimize._lsap, scipy.spatial._ckdtree, scipy.spatial._qhull, scipy.spatial._voronoi, scipy.spatial._distance_wrap, scipy.spatial._hausdorff, scipy.special._ufuncs_cxx, scipy.special._cdflib, scipy.special._ufuncs, scipy.special._specfun, scipy.special._comb, scipy.special._ellip_harm_2, scipy.spatial.transform._rotation, scipy.optimize._direct, httptools.parser.parser, httptools.parser.url_parser, websockets.speedups, cuda_utils (total: 104)

Unfortunately, this is precisely the kind of workarounds we meant to avoid when we dropped support for pre-A100 GPUs. On all GPUs supported by Triton, dot should not implicitly upcast its operands to float32. I am sure that there are many, many other rough edges for pascal (especially when it comes to transpositions), and we can't commit to accepting all the PRs that fix them. Thanks for your understanding!


Fix kogito-apps/ui-packages build

ui-packages build is failing silently due to Cypress failure.
There are missing system libraries that Cypress requires.

Fixed via apache/incubator-kie-kogito-pipelines#1111


Monitor requires standard input to be attached to TTY (IDFGH-13306)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

IDF version.
https://github.com/espressif/esp-idf/releases/tag/v5.2.2
Operating System used.
Windows
How did you build your project?
CLion IDE
If you are using Windows, please specify command line type.
None
What is the expected behavior?
The COM port will be read
What is the actual behavior?
An error is coming out
Steps to reproduce.

ESPPORT COM5
flash build
monitor build

Build or installation Logs.
====================[ Build | monitor | Debug ]=================================
"D:\CLion 2024.1.4\bin\cmake\win\x64\bin\cmake.exe" --build D:\ESP32EDF\ESP32Project\NewProject\hello_world\cmake-build-debug --target monitor -j 14
[0/1] C:\WINDOWS\system32\cmd.exe /C "cd /D D:\ESP32EDF\ESP32CLINE\esp-idf-v5.2.2\components\esptool_py && "D:\CLion 2024.1.4\bin\cmake\win\x64\bin\cmake.exe" -D IDF_PATH=D:/ESP32EDF/ESP32CLINE/esp-idf-v5.2.2 -D SERIAL_TOOL=python;-m;esp_idf_monitor -D SERIAL_TOOL_ARGS=--target;esp32;--revision;0;D:/ESP32EDF/ESP32Project/NewProject/hello_world/cmake-build-debug/hello_world.elf -D WORKING_DIRECTORY=D:/ESP32EDF/ESP32Project/NewProject/hello_world/cmake-build-debug -P run_serial_tool.cmake"
error: Monitor requires standard input to be attached to TTY
CMake Error at run_serial_tool.cmake:66 (message):
  python;-m;esp_idf_monitor failed.

FAILED: CMakeFiles/monitor D:/ESP32EDF/ESP32Project/NewProject/hello_world/cmake-build-debug/CMakeFiles/monitor
C:\WINDOWS\system32\cmd.exe /C "cd /D D:\ESP32EDF\ESP32CLINE\esp-idf-v5.2.2\components\esptool_py && "D:\CLion 2024.1.4\bin\cmake\win\x64\bin\cmake.exe" -D IDF_PATH=D:/ESP32EDF/ESP32CLINE/esp-idf-v5.2.2 -D SERIAL_TOOL=python;-m;esp_idf_monitor -D SERIAL_TOOL_ARGS=--target;esp32;--revision;0;D:/ESP32EDF/ESP32Project/NewProject/hello_world/cmake-build-debug/hello_world.elf -D WORKING_DIRECTORY=D:/ESP32EDF/ESP32Project/NewProject/hello_world/cmake-build-debug -P run_serial_tool.cmake"
ninja: build stopped: subcommand failed.

More Information.
No response

Hi @EvgeniyVol, can you please provide some more details? How are you executing the monitor? Are you using some IDE shortcut? Or are you executing the command in the integrated terminal of IDE?
If you are using some button in the IDE to execute the monitor, please make sure that you have followed the installation guide on the Clion website: https://www.jetbrains.com/help/clion/esp-idf.html
Please ensure you can execute the monitor using the idf.py monitor or python -m esp_idf_monitor command. Note that both commands need to be run in the ESP-IDF environment. Both the command line and PowerShell should work in this case.

IDE CLion 2024.1.4
I use the configuration in the upper right corner and the build button
Everything works in IDE terminal
I did as it says it doesn't work https://www.jetbrains.com/help/clion/esp-idf.html
In command line everything works

If everything works in the terminal, I am afraid that we cannot do anything about that from the ESP-IDF side. Please report the bug to CLion.

It is interesting that the linked page has a video tutorial and this issue is not happening there. IDF Monitor requires STDIN to be connected to it from the very beginning because it is an interactive tool and is not just receiving but also sending characters to the ESP. So I guess something must have changed on the Clion side. I agree that this should be address on their side.
However, we might think about to add a non-interactive mode for IDF Monitor in the future when it won't send anything and those related features would be disabled.

Maybe it will help someone, https://youtrack.jetbrains.com/issue/CPP-34647/ESP-IDF-Monitor-error-Monitor-requires-standard-input-to-be-attached-to-TTY. I have checked this method works


ISPN-12864 test driver should be test scope

https://issues.redhat.com/browse/ISPN-12864

Thanks @karesti