GC: Beta Service Connector Feature

Description
Add the Beta Library. This PR is necessary to call the Beta features of Graph
This is the first Beta-Dependent PR.

Issue #2086 may prevent this and trailing packages from being merged into main.
Does this PR need a docs update or release note?

[x] 👍 Yes, added to the ChangeLog to note build time complications.

Type of change

[x] :sunflower: Feature

Issue(s)

related to  #2086
closes #2174

Test Plan

[x] :zap: Unit test

As Indicated in #2086, the CI fails when adding Beta.
2023-01-19T04:50:39.7179980Z # get<EMAIL_ADDRESS>200 OK (0.010s)
2023-01-19T04:50:39.7271998Z # get<EMAIL_ADDRESS>2023-01-19T04:50:39.7364679Z # get<EMAIL_ADDRESS>200 OK (0.009s)
2023-01-19T04:56:36.6372247Z ##[error]Process completed with exit code 143.
2023-01-19T04:56:36.6576876Z ##[error]The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
2023-01-19T04:56:36.9846498Z Cleaning up orphan processes

Local Tests:
go test ./...
ok  	github.com/alcionai/corso/src	0.221s
ok  	github.com/alcionai/corso/src/cli	1.650s
ok  	github.com/alcionai/corso/src/cli/backup	288.651s
ok  	github.com/alcionai/corso/src/cli/config	0.281s
ok  	github.com/alcionai/corso/src/cli/help	(cached)
?   	github.com/alcionai/corso/src/cli/options	[no test files]
ok  	github.com/alcionai/corso/src/cli/print	(cached)
ok  	github.com/alcionai/corso/src/cli/repo	22.027s
ok  	github.com/alcionai/corso/src/cli/restore	147.854s
ok  	github.com/alcionai/corso/src/cli/utils	0.239s
?   	github.com/alcionai/corso/src/cmd/factory	[no test files]
?   	github.com/alcionai/corso/src/cmd/factory/impl	[no test files]
?   	github.com/alcionai/corso/src/cmd/getM365	[no test files]
?   	github.com/alcionai/corso/src/cmd/mdgen	[no test files]
?   	github.com/alcionai/corso/src/cmd/purge	[no test files]
ok  	github.com/alcionai/corso/src/internal/common	(cached)
ok  	github.com/alcionai/corso/src/internal/connector	170.912s
ok  	github.com/alcionai/corso/src/internal/connector/discovery	0.249s
ok  	github.com/alcionai/corso/src/internal/connector/exchange	110.992s
ok  	github.com/alcionai/corso/src/internal/connector/exchange/api	7.205s
ok  	github.com/alcionai/corso/src/internal/connector/graph	4.711s
ok  	github.com/alcionai/corso/src/internal/connector/mockconnector	(cached)
ok  	github.com/alcionai/corso/src/internal/connector/onedrive	22.820s
ok  	github.com/alcionai/corso/src/internal/connector/sharepoint	17.752s
ok  	github.com/alcionai/corso/src/internal/connector/support	(cached)
ok  	github.com/alcionai/corso/src/internal/connector/uploadsession	(cached)
ok  	github.com/alcionai/corso/src/internal/data	(cached)
?   	github.com/alcionai/corso/src/internal/diagnostics	[no test files]
ok  	github.com/alcionai/corso/src/internal/events	(cached)
?   	github.com/alcionai/corso/src/internal/events/mock	[no test files]
ok  	github.com/alcionai/corso/src/internal/kopia	153.071s
?   	github.com/alcionai/corso/src/internal/kopia/mockkopia	[no test files]
ok  	github.com/alcionai/corso/src/internal/model	(cached)
ok  	github.com/alcionai/corso/src/internal/observe	(cached)
ok  	github.com/alcionai/corso/src/internal/operations	351.119s
?   	github.com/alcionai/corso/src/internal/stats	[no test files]
ok  	github.com/alcionai/corso/src/internal/streamstore	3.978s
?   	github.com/alcionai/corso/src/internal/tester	[no test files]
?   	github.com/alcionai/corso/src/internal/version	[no test files]
ok  	github.com/alcionai/corso/src/pkg/account	(cached)
ok  	github.com/alcionai/corso/src/pkg/backup	(cached)
ok  	github.com/alcionai/corso/src/pkg/backup/details	(cached)
?   	github.com/alcionai/corso/src/pkg/control	[no test files]
?   	github.com/alcionai/corso/src/pkg/credentials	[no test files]
ok  	github.com/alcionai/corso/src/pkg/filters	(cached)
?   	github.com/alcionai/corso/src/pkg/logger	[no test files]
ok  	github.com/alcionai/corso/src/pkg/path	(cached)
ok  	github.com/alcionai/corso/src/pkg/repository	1.483s
ok  	github.com/alcionai/corso/src/pkg/selectors	(cached)
ok  	github.com/alcionai/corso/src/pkg/services/m365	1.507s
ok  	github.com/alcionai/corso/src/pkg/storage	(cached)
ok  	github.com/alcionai/corso/src/pkg/store	(cached)
?   	github.com/alcionai/corso/src/pkg/store/mock	[no test files]

Approving to unblock, but we should evaluate whether we want both the beta and live libraries inside the binary before moving forward.

Evaluation complete. Both binaries are not desired.  Changes present in #2205 supersede this PR.


Using a compact URI for skos in <rdf:type rdf:resource="skos:ConceptScheme"/> seems to be an error

My RDF/XML isn't great, but it seems like you cannot use compact URIs as an XML attribute value: it doesn't translate to turtle properly.
I think you need the full IRI:
<rdf:type rdf:resource="http://www.w3.org/2004/02/skos/core#ConceptScheme"/>
(Needs fixing also for skos:Concept as a value for rdf:type)

Corrected with Version <IP_ADDRESS>. release


fix: vw no faas handle

Codecov Report
Base: 88.46% // Head: 88.37% // Decreases project coverage by -0.09% :warning:

Coverage data is based on head (f0e5ee9) compared to base (e2b211a).
Patch coverage: 50.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #301      +/-   ##
==========================================
- Coverage   88.46%   88.37%   -0.10%
==========================================
  Files          40       40
  Lines        4075     4077       +2
  Branches     1193     1193
==========================================
- Hits         3605     3603       -2
- Misses        432      435       +3
- Partials       38       39       +1

Impacted Files
Coverage Δ

packages/cli-plugin-package/src/utils.ts
85.12% <50.00%> (-1.92%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

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


Integrated angular 2 component library with angular/cli throws an error

Please provide us with the following information:

OS?

Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?)
Windows 10

Versions.

Please run ng --version. If there's nothing outputted, please run in a Terminal: node --version and paste the result here:
@angular/cli: 1.0.0-beta.32.3
node: 6.9.5

Repro steps.

Was this an app that wasn't created using the CLI? What change did you do on your code? etc.

The app was created with the cli, and his purpose is to present a library. And the purpose of the library
is work fine with the cli/webpack/systemjs
Clone this repository,
Run npm install and the npm run ng serve.
In the console you will receive the following error.

`ERROR in Ng2ToolsModule is not an NgModule`

If you enter in app.module.ts erase one module and add it again the application compiles fine.
And the error is lost, Biggest problem is that I cannot build the application.

Ng2ToolsModule is part of a library called ng2-tools created and published by me. Here is a link with the repository . Is this a cli bug or a library build bug ? Let me kow how I should change the build for the library to just work with the cli, if the problem comes from my build.
The log given by the failure.

Normally this include a stack trace and some more information.

Mention any other details that might be useful.

Thanks! We'll be in touch soon.

I think this is due to your lib not being AOT ready. Unfortunately there really aren't good instructions for that right now.
The best I can point you to is https://github.com/angular/angular-cli/issues/1692#issuecomment-285363067, it has a link to a WIP aot lib guide.


Node.js v18.x build error

I'm currently using Node.js v16 LTS for production but testing Node.js v18. I am seeing build errors under Node.js v18.x...  Any suggestions welcome?
[1/4] Resolving packages...
[2/4] Fetching packages...
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
[3/4] Linking dependencies...
warning "react-admin ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^4.0.0-rc.1".
warning "react-admin ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning "react-admin ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning "react-admin ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>[4/4] Building fresh packages...
success Saved lockfile.
Done in 129.12s.
yarn run v1.22.15
$ react-scripts build
node:internal/modules/cjs/loader:489
      throw e;
      ^

Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './lib/tokenize' is not defined by "exports" in /home/nmos-js/Development/node_modules/postcss-safe-parser/node_modules/postcss/package.json
    at new NodeError (node:internal/errors:372:5)
    at throwExportsNotFound (node:internal/modules/esm/resolve:440:9)
    at packageExportsResolve (node:internal/modules/esm/resolve:719:3)
    at resolveExports (node:internal/modules/cjs/loader:483:36)
    at Module._findPath (node:internal/modules/cjs/loader:523:31)
    at Module._resolveFilename (node:internal/modules/cjs/loader:925:27)
    at Module._load (node:internal/modules/cjs/loader:780:27)
    at Module.require (node:internal/modules/cjs/loader:1005:19)
    at require (node:internal/modules/cjs/helpers:102:18)
    at Object.<anonymous> (/home/nmos-js/Development/node_modules/postcss-safe-parser/lib/safe-parser.js:1:17) {
  code: 'ERR_PACKAGE_PATH_NOT_EXPORTED'
}

Node.js v18.0.0
error Command failed with exit code 1.

@rhastie @garethsb did you get this working?   The postcss issue suggested npm install postcss but that's not working for me with Node 19.

Nor with node.js v18.12.1, using corepack and yarn (and yarn add postcss)

In the meantime I've downgraded to v16.18.1 (with corepack 0.14.1 and yarn 3.2.4) and yarn start runs

Hey, @jonathan-r-thorpe, any thoughts on supporting Node v18+ ?

So I've just checked the same issue is happening with Node v20.x as well. Is there anything we can do as it potentially just looks like a new syntax issue with later versions of Node

@garethsb in the short term pragmatically updating incompatible library versions just enough to mitigate this issue, but not so much that it requires a complete overhaul of the codebase.  I'll schedule some time next week to take a look.


Fancy text

"Fancy" text, using OpenType fonts that are converted into vertices. I've preloaded 9 fonts (all free to use and distribute), but we could add/remove any as desired. Some additional features:

can choose to connect lines of text along "inside" or "outside"
alignment

Includes fix for #211.

This is great.

Are all these ttf fonts free and clear for our use? Do we need to attribute them somewhere?

The "outside" connection doesn't seem great to me. I can't seem to get it to do anything but swipe right through the words.
I think we should make the inside the default. WDYT?

Have you tried breaking up the words into characters to enforce the letter order? It seems to really like going right to left. And Garamond "Jeff" does the J before the f,f,e.

I found one bug while playing around, but it wasn't related to the fancy text. I will push it here anyway, since it is a tiny bug. I had a long path, I changed the preview slider to the right, and then I added a shorter layer and deleted the longer one, and the page crashes.

As long as the fonts are clear, and you don't want to play with the letters, you can merge this.
Is there anything else you'd like to see in a release?

Are all these ttf fonts free and clear for our use? Do we need to attribute them somewhere?

Free and clear. I will add attribution.

The "outside" connection doesn't seem great to me. I can't seem to get it to do anything but swipe right through the words.
I think we should make the inside the default. WDYT?

Inside is probably a better default, but outside works fine for me. I cannot reproduce what you are seeing. I can't reproduce your ordering issues, either. It does break it up letter by letter, and always goes left to right. Can you check and see if you've accidentally set fine-tuning to rotate your starting point - that can cause what you are seeing.

As long as the fonts are clear, and you don't want to play with the letters, you can merge this.
Is there anything else you'd like to see in a release?

@jeffeb3 There are some "pesky" bugs introduced with the previous caching refactor. I see occasional crashing, and in addition, layers are not always rendered faithfully. It's inconsistent. I want/need to dig into this prior to a new release. I don't have anything else currently active, so we could consider a release after that?

As long as the fonts are clear, and you don't want to play with the letters, you can merge this.
Is there anything else you'd like to see in a release?

@jeffeb3 There are some "pesky" bugs introduced with the previous caching refactor.

@jeffeb3 Ok, I pushed fixes for a few things: a faulty selector was causing issues with redraws when effect layers were added. Also, shapes were being drawn every time a font was loaded (9x), which results in a huge slow down. To fix this, I had to re-structure the entire redux store. It's not actually that big of a change, but it required a lot of refactoring. I actually like the new selectors better - they protect us against future changes a bit more. Anyway, this means that I would ask you to do more than usual amount of testing before approving this PR. Thanks.

I'm still seeing it draw the letters right to left. To reproduce:

I deleted all the local storage
I refreshed the page
I changed the shape type to fancy text. I left the defaults (see the screenshot).
I changed the preview slider to show it was drawing from right to left.

The letter order is also causing the "outside" connecting rows to be wrong. If it had ended on the right and started on the left, it would be fine.

This is the same test setup, but I added a second row of "Sandify" and then changed it to outside.

I opened it in chromium, and it is drawing left to right. How is that possible?

I have ran out of time this morning. But I narrowed it down to this:
Object.keys(graph)

In chromium, it is an array of length 7, containing ['0', '1', '3', '4', '6', '8', '9']. In firefox, it is [ "9", "8", "6", "4", "3", "1", "0" ]. So it must just be storing the keys in a different order. I guess we should sort that array before doing the sort?

So, sorting it again makes no sense... The sort should put them in the right order no matter what order they come in as (although I am still not sure why they are in reverse order on firefox). But looking at the doc for the sort function on Array: https://www.w3schools.com/jsref/jsref_sort.asp
It takes two arguments, and returns the difference. So I have a fix that makes sense to me, and works in my two browsers. I will push it in a minute But here is the sort function I am using:
    return Object.keys(graph).sort(
      (leftIndex, rightIndex) => {
        const leftPoints = graph[leftIndex].points
        const rightPoints = graph[rightIndex].points
        return Math.min(...leftPoints.map(pt => pt.x)) - Math.min(...rightPoints.map(pt => pt.x))
      })
    .map(key => graph[key])


workaround for startup delay when debugging

How do you actually debug an aspire application in the first place? I have created a new project using the aspire-starter dotnet new template but my breakpoints will only get hit in the app host project and not in any of the other projects (says the symbols are missing). Is there some IDE side setup required to enable proper debugging in Aspire projects?

@jack775544 are you debugging using Visual Studio 2022 17.9 Preview 1? The Visual Studio tooling for Aspire (including automatic multiple service debugging) is only available in 17.9 Preview builds currently, not the 17.8 GA release.

@danegsta Ahh that would make sense. I was using 17.8, I didn't realise debugging would require a newer version of Visual Studio as well.
On that note, is there any workaround for people not using Visual Studio (eg. using VSCode or Rider) or is debugging Aspire applications going to have to be explicitly supported by the IDE for it to work.

Debugger support requires work in the IDE https://github.com/dotnet/aspire/blob/main/docs/specs/IDE-execution.md

@jack775544 I opened https://github.com/dotnet/aspire/issues/845 to address your feedback. thanks!

@vijayrkn Can you follow up on this issue and close this bug if there's nothing else we need to do?

@vijayrkn ?

@danmoseley the VS bug on this was fixed by @auott in 17.9.


New transactions don't show up

Describe the bug
A clear and concise description of what the bug is.
To Reproduce

Post new tx to tx service -> https://safe-transaction.rinkeby.gnosis.io/api/v1/safes/0xaE3c91c89153DEaC332Ab7BBd167164978638c30/multisig-transactions/ has some not executed txs.

They don't show up at https://safe-client.rinkeby.gnosis.io/v1/safes/0xaE3c91c89153DEaC332Ab7BBd167164978638c30/transactions/queued/
Expected behavior

https://safe-client.rinkeby.gnosis.io/v1/safes/0xaE3c91c89153DEaC332Ab7BBd167164978638c30/transactions/queued/ returns the txs waiting for confirmations / execution

Desktop (please complete the following information):

OS: MacOS
Browser: Firefox

@rmeissner @jpalvarezl is this related to the caching issues? If yes, could you please invalidate the cache for my Safe?

Seems to be. I invalidated the cache and now some transactions are returned. This is a bit weird, as yesterday we rolled back the gateway to v1.8.3 but it seems it was only mainnet. I checked the about endpoint for rinkeby and xdai and the version is still v1.9.0. Today we plan on releasing a hotfix to all prod environments, so all production networks should have the same deployed version again.

Thanks!


Update storage-blob-readme.md

I created a sample project using azure blob SDK and I getting an error on this part, does the url + sas seem wrong or I am the one who is wrong? I added, "/?" on my sample project, and its works successfully.

Docs Build status updates of commit 43b7506:
:clock10: Pending: waiting for processors (20 builds ahead of you)
:warning: Docs Build is busy, currently there are 20 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 43b7506:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-FailedToRestoreDependentRepository]

Failed to restore dependent repository from URL 'https://github.com/Microsoft/templates.docs.msft', branch 'master' into folder '_themes'. Please open a ticket in https://SiteHelp and include exception details: System.TimeoutException: Git operation '-c http.extraheader="Authorization: *****" pull origin --no-edit' timed out. Details: git.exe (argument: -c http.extraheader="Authorization: *****" pull origin --no-edit, working directory: W:\olty-s\_themes) didn't exit in 180000 ms. Forced to exit..
   at Microsoft.OpenPublishing.Build.Common.ProcessUtility.ExecuteExeCore(ProcessExecutionInfo executionInfo, Action`1 outputAction, StreamWriter stderrStreamWriter, Int32 timeoutInMilliseconds, CancellationToken cancellationToken)
   at Microsoft.OpenPublishing.Build.Common.ProcessUtility.ExecuteExe(ProcessExecutionInfo executionInfo, StreamWriter stdoutStreamWriter, StreamWriter stderrStreamWriter, Int32 timeoutInMilliseconds, CancellationToken cancellationToken)
   at Microsoft.OpenPublishing.Build.DataAccessor.Git.ExternalGitAccessor.RunGitExeAndProcessOutputStream(String argument, String workingDirectory, Uri repositoryUrl, String branchName, Action`1 outPutStreamAction, Boolean silentException, Int32 timeout, Boolean retryOnTimeout)
   at Microsoft.OpenPublishing.Build.DataAccessor.Git.ExternalGitAccessor.PullCore()
   at Microsoft.OpenPublishing.Build.DataAccessor.Git.BaseGitAccessor.Pull()
   at Microsoft.OpenPublishing.Build.Applications.InitializeCRRTool.Program.InitializeDependentRepository(String dependentRepoPath, String cloneAccessToken, Boolean isCopiedFromCachedRepo, Boolean isPreservedTemplateFolder, Options options, DependentRepository dependentRepository)
   at Microsoft.OpenPublishing.Build.Applications.InitializeCRRTool.Program.InitializeCRRCore(String dependentRepoPath, String cloneAccessToken, Boolean isPreservedTemplateFolder, Boolean isCopiedFromCachedRepo, String branch, Options options, DependentRepository dependentRepository, List`1 lastDependencyStatus)
   at Microsoft.OpenPublishing.Build.Applications.InitializeCRRTool.Program.<InitializeCRRCoreAsync>d__8.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.OpenPublishing.Build.Applications.InitializeCRRTool.Program.<InitializeCRRAsync>d__5.MoveNext()

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

@jbmarvin24 Thanks for the contribution! This definitely looks like a reasonable adjustment. I mirrored your update over to the source of this repo.

Hey @jbmarvin24 it looks like the sample is just written to work with the SAS token that is generated form the azure portal. When you grab the SAS from azure it'll have the ?sv= already appended.

I think given that, the sample is probably ok.


VSTS agent task failing with exit code 102

Having issue with YAML?
Please log an issue at Azure-Pipelines-YAML. Over there we discuss YAML templates, samples for Azure Pipelines, and designs for upcoming YAML features. Also a place for the community to share best practices, ideas, and so on. File suggestions and issues here if they're specific to YAML pipelines.
Having issue with Tasks?
Log an issue at Azure-Pipelines-Tasks. It contains all of the in-box tasks we ship with Azure-Pipelines/VSTS/TFS. If you're having issues with tasks in Build/Release jobs (e.g. unreasonable task failure) please log an issue there.
Having issue with software on Hosted Agent?
Log an issue at Hosted Agent Image Repository. It contains the VM image used in the Azure Pipelines Hosted Agent Pool. If you're having Build/Release failures that seems like they are related to software installed on the Hosted Agent (e.g. the dotnet SDK is missing or the Azure SDK is not on the latest version) please log an issue there.
Having generic issue with Azure-Pipelines/VSTS/TFS?
Please report it on Developer Community
Have you tried troubleshooting?
Troubleshooting doc
Agent Version and Platform
Version of your agent? vsts-agent-win-x64-2.164.6
OS of the machine running the agent? OSX/Windows/Linux/...
Windows
Azure DevOps Type and Version
dev.azure.com (formerly visualstudio.com) or on-premises TFS/Azure DevOps Server
dev.azure.com
If on-premises, which release? 2015.0, 2017.1, 2019 RC2, etc.
If dev.azure.com, what is your organization name? https://dev.azure.com/{organization} or https://{organization}.visualstudio.com
What's not working?
My Task simply execute a powershell command in my local windows environment, if i run the script manually it works fine, but when the call flow comes through agent i am getting process exited with exit code 102.
Please include error messages and screenshots.
Agent and Worker's Diagnostic Logs
Agent
2020-01-25 19:56:59Z INFO MessageListener] Message '3' received from session 'a0d470f3-c217-441f-a470-ffc0a61f7e45'.
[2020-01-25 19:56:59Z INFO JobDispatcher] Job request 5 for plan b0143c9d-a025-4dae-bfc5-c5965bcd0436 job 275f1d19-1bd8-5591-b06b-07d489ea915a received.
[2020-01-25 19:56:59Z INFO JobDispatcher] Job request 275f1d19-1bd8-5591-b06b-07d489ea915a processed succeed.
[2020-01-25 19:56:59Z INFO Terminal] WRITE LINE: 2020-01-25 19:56:59Z: Running job: Agent job 1
[2020-01-25 19:56:59Z INFO JobDispatcher] Start renew job request 5 for job 275f1d19-1bd8-5591-b06b-07d489ea915a.
[2020-01-25 19:56:59Z INFO JobDispatcher] Successfully renew job request 5, job is valid till 1/25/2020 8:06:59 PM
[2020-01-25 19:56:59Z INFO HostContext] Well known directory 'Bin': 'C:\D\agent\vsts-agent-win-x64-2.164.6\bin'
[2020-01-25 19:56:59Z INFO ProcessInvokerWrapper] Starting process:
[2020-01-25 19:56:59Z INFO ProcessInvokerWrapper]   File name: 'C:\D\agent\vsts-agent-win-x64-2.164.6\bin\Agent.Worker.exe'
[2020-01-25 19:56:59Z INFO ProcessInvokerWrapper]   Arguments: 'spawnclient 3660 3648'
[2020-01-25 19:56:59Z INFO ProcessInvokerWrapper]   Working directory: 'C:\D\agent\vsts-agent-win-x64-2.164.6\bin'
[2020-01-25 19:56:59Z INFO ProcessInvokerWrapper]   Require exit code zero: 'False'
[2020-01-25 19:56:59Z INFO ProcessInvokerWrapper]   Encoding web name:  ; code page: ''
[2020-01-25 19:56:59Z INFO ProcessInvokerWrapper]   Force kill process on cancellation: 'True'
[2020-01-25 19:56:59Z INFO ProcessInvokerWrapper]   Redirected STDIN: 'False'
[2020-01-25 19:56:59Z INFO ProcessInvokerWrapper]   Persist current code page: 'False'
[2020-01-25 19:56:59Z INFO ProcessInvokerWrapper]   Keep redirected STDIN open: 'False'
[2020-01-25 19:56:59Z INFO ProcessInvokerWrapper]   High priority process: 'True'
[2020-01-25 19:56:59Z INFO ProcessInvokerWrapper] Process started with process id 15436, waiting for process exit.
[2020-01-25 19:56:59Z INFO JobDispatcher] Send job request message to worker for job 275f1d19-1bd8-5591-b06b-07d489ea915a (19 KB).
[2020-01-25 19:57:00Z INFO JobDispatcher] Took 856 ms to send job message to worker
[2020-01-25 19:57:00Z INFO JobNotification] Entering JobStarted Notification
[2020-01-25 19:57:00Z INFO JobNotification] Entering StartMonitor
[2020-01-25 19:57:28Z INFO ProcessInvokerWrapper] STDOUT/STDERR stream read finished.
[2020-01-25 19:57:28Z INFO ProcessInvokerWrapper] STDOUT/STDERR stream read finished.
[2020-01-25 19:57:28Z INFO ProcessInvokerWrapper] Exited process 15436 with exit code 102
[2020-01-25 19:57:28Z INFO ProcessInvokerWrapper] Finished process 15436 with exit code 102, and elapsed time 00:00:29.5437729.
[2020-01-25 19:57:28Z INFO JobDispatcher] Worker finished for job 275f1d19-1bd8-5591-b06b-07d489ea915a. Code: 102
[2020-01-25 19:57:28Z INFO JobDispatcher] finish job request for job 275f1d19-1bd8-5591-b06b-07d489ea915a with result: Failed
[2020-01-25 19:57:28Z INFO Terminal] WRITE LINE: 2020-01-25 19:57:28Z: Job Agent job 1 completed with result: Failed
[2020-01-25 19:57:28Z INFO JobDispatcher] Stop renew job request for job 275f1d19-1bd8-5591-b06b-07d489ea915a.
[2020-01-25 19:57:28Z INFO JobDispatcher] job renew has been canceled, stop renew job request 5.
[2020-01-25 19:57:28Z INFO JobNotification] Entering JobCompleted Notification
[2020-01-25 19:57:28Z INFO JobNotification] Entering EndMonitor
Logs are located in the agent's _diag folder. The agent logs are prefixed with Agent_ and the worker logs are prefixed with Worker_. All sensitive information should already be masked out, but please double-check before pasting here.

I'm having a similar problem, see here:
https://github.com/MicrosoftDocs/vsts-docs/issues/7324
Yet I don't know what is the exact issue and where to attach this question to, but the only specific indication towards an error is this in the agent log:
INFO ProcessInvokerWrapper] Exited process 9447 with exit code 102
Is there an explanation of these error codes somewhere?
This happens in a publish Pipeleine Artifact step. The same is running on anothre agent.

I also have the same issue, getting exit code 102 but no additional details. Was this issue resolved?

We are now using agent version 2.165.0, the issue is still there. I use the following workaround:
For Artifact uploads I use the PublishBuildArtifacts task, for Download I use the DownloadPipelineArtifact task.
I can Use publishPipelineartifacts for Upload, But the the Download as PipelineArtifact fails.
My guess there is some issue with the connection through a proxy, but I don't get reasonable information about the failure.

Hi @ThKaufmann-PG could you please set VSTSAGENT_TRACE pipeline variable as 'true' and gather agent logs again?

Hi @ThKaufmann-PG is this issue still actual for you?

@ledzep70 @ThKaufmann-PG  @gksanam I'm closing this due to inactivity at the moment - please let us know if it is still actual for you.


fix(i18n):update intro text for event hub lab

Checklist:

[x] I have read and followed the contribution guidelines.
[x] I have read and followed the how to open a pull request guide.
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Closes #56869

Hi @Subas-mohanty. Congrats on your first pull request (PR)! 🎉
Thank you for your contribution to the page! 👍
We are happy to accept these changes and look forward to future contributions. 📝


Headset for running

Because sometimes I feel spending hours without doing anything other than running might be waste, listening might be an option to amend the situation and give blast to the running. No need to listen to music, I'd rather listen to speech/news.
Requirement (came up without doing research):

Wirelessly connect to my Android device.
Both earbuds are wired (to reduce risk of losing)
Minimum a few hours of battery?
Chargeable via Micro USB
< $150
Waterproof
Heart rate synchronizable with Google Fit
(nice to have) Special consideration for ambient sound

12 of the Best Wireless Headphones for Running from runnersworld.com (Apr 2017)
Maybe I need to try on some products. Will go to Fleet Feet.

Choices that pass all I required may be these 2:

Under Armour Headphones Wireless Heart Rate

Amazon's review is way too low where issues look like audio volume and Bluetooth connectivity. No go.

Bose SoundSport Pulse

Amazon's review: 3.9/5. Issues seem to be too bulky, wind noise. I haven't found so many users who run long distance.

Also found others by mainly searching heart-rate tracking headphones/earbuds that are compatible with Google Fit, but their review on Amazon all fall short to Bose, so deal.


cannot build from CLI or VS Code

First of all, thank you for this beautiful little piece of technology!
When I try to compile and run the sample using the VS Code or using the dotnet cli directly
dotnet run --project Samples/Samples.csproj

I get the below error.

C:\Users\bitbonk.nuget\packages\xamarin.forms\<IP_ADDRESS>779\build\netstandard1.0\Xamarin.Forms.targets(51,3): error MSB4062: The "Xamarin.Forms.Build.Tasks.FixedCreateCSharpManifestResourceName" task could not be loaded from the assembly C:\Users\bitbonk.nuget\packages\xamarin.forms\<IP_ADDRESS>779\build\netstandard1.0\Xamarin.Forms.Build.Tasks.dll. Could not load file or assembly 'Microsoft.Build.Utilities.v4.0, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. The system cannot find the file specified. Confirm that the  declaration is correct, that the assembly and all its dependencies are available, and that the task contains a public class that implements Microsoft.Build.Framework.ITask. [c:\temp\Ooui\Ooui.Forms\Ooui.Forms.csproj]
The build failed. Please fix the build errors and run again.

When I build and run from Visual Studio 2017, everything works fine.
This issue might be related.
Also: this.

Yes I have run into this too, but so far only on Linux.
I filed a bug against Xamarin Forms for including an SDK reference in a .NET Standard project instead of the nuget reference.
https://bugzilla.xamarin.com/show_bug.cgi?id=60705
As a workaround, I build the app with mono's msbuild. And then I run with dotnet run --no-build
Obviously this is not great. I'll see if we can get Xamarin to fix their build.

Looks like there is a Xamarin Forms PR to fix this: https://github.com/xamarin/Xamarin.Forms/pull/1284

@bitbonk if you are interested in vs code settings to use while we wait for the PR to be merged check out my referenced commit in my fork. Since this is going to be fixed soon I'm not planning to submit a PR but the settings work for me on linux for compiling and debugging

Looks like a fix got merged. Just have to wait for a release to include it.

I tried with <IP_ADDRESS>203 and it's still failing: https://github.com/xamarin/Xamarin.Forms/issues/1777

Did 3.0 work?

Can't see <IP_ADDRESS> on Nuget?
I've removed Xamarin.Forms for now and am just using the OOui elements, which are fine for what I'm doing.

Make sure you check the box to see pre-release. It’s unfortunate, but we’re all stuck waiting for it to come out.

On Apr 19, 2018, at 1:50 AM, Harry McIntyre<EMAIL_ADDRESS>wrote:
Can't see <IP_ADDRESS> on Nuget?
I've removed Xamarin.Forms for now and am just using the OOui elements, which are fine for what I'm doing.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/praeclarum/Ooui/issues/26#issuecomment-382659897, or mute the thread https://github.com/notifications/unsubscribe-auth/AATv3Mz69qxBKGZxlLjG1T8_SEcG9GEEks5tqE_YgaJpZM4QgbQc.

Yep, I tried <IP_ADDRESS>4232-pre3 which is a prerelease. I'll give it another go, maybe something went wrong with my push to bitbucket/azure.

I’m pushing OouiChat to Azure, maybe checkout my settings and versions.
https://github.com/praeclarum/OouiChat https://github.com/praeclarum/OouiChat

On Apr 19, 2018, at 9:06 AM, Harry McIntyre<EMAIL_ADDRESS>wrote:
Yep, I tried <IP_ADDRESS>4232-pre3 which is a prerelease. I'll give it another go, maybe something went wrong with my push to bitbucket/azure.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/praeclarum/Ooui/issues/26#issuecomment-382791649, or mute the thread https://github.com/notifications/unsubscribe-auth/AATv3Hw_O0LxAUNrHITlbDYEB_kn0j8aks5tqLXsgaJpZM4QgbQc.


fid format <vid>/<fid><key>  doesn't work for upload

# curl -F<EMAIL_ADDRESS>http://<IP_ADDRESS>:18080/7,224d7bc02e
{"name":"start_volume.sh","size":279}
# curl -F<EMAIL_ADDRESS>http://<IP_ADDRESS>:18080/7/224d7bc02e
{"error":"Invalid key and hash:0/7/224d7bc02e"}

the "nicer" url format is for reading requests. Write requests, and many other places, are using the canonical file key format.

ok. It's better to mention this in the doc 😊

right.


Don't specify any default templates, use the default button text

I think that by default you shouldn't mess with the button content. If anything provide an easy way to specify a loading icon (with position).

Thank you for comment. My philosophy is to keep default to match majority
of use cases and then, if needed, to provide ways to override it.
I think intention of current default is to have simple way to make ready to
use button without repeating myself. Since you're the first one who wants
to change it, I'm keeping it as it now.
You are of course free to make patch that provide override, I'll be happy
to merge it.
Dne 20. 3. 2015 17:11 "Blake Niemyjski"<EMAIL_ADDRESS>napsal(a):

I think that by default you shouldn't mess with the button content. If
anything provide an easy way to specify a loading icon (with position).
—
Reply to this email directly or view it on GitHub
https://github.com/DocX/ng-promise-button/issues/2.


Prevent stopScan to be called on timeout

Prevent stopScan to be called on startScan timeout if scan has already been stoped

Great work!


add pushing to PyPi to GH Action

See Slack. While waiting for the new CCL release to make it to PyPi and ultimately conda-forge, @EiffL noted this was an automated process when using Travis-CI, which is now disabled. This bit could be added your existing GH workflow - right? That way, no one need worry about this again hopefully :)

Thanks Heather for following up on this, I actually just found just the thing we need :-D
https://packaging.python.org/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows/

This was closed by #948


Documentation site is down

Bug Report
The documentation site is down
What did you do?
Attempted to visit the documentation site.
What did you expect to see?
The documentation site.
What did you see instead?

Output of controller log: (What version of Traefik Mesh are you using?)
N/A
What is your environment & configuration (arguments, provider, platform, ...)?
N/A
If applicable, please paste the yaml objects required to reproduce your issue
N/A

Hello, thank you for reporting this issue.
As a workaround, you can use https://traefik.github.io/mesh/

Hello @farmdawgnation,
Thanks for the report.
The site is back in the game. It was a DNS issue.


GPUParticles2D#emit_particle's color parameter doesn't work

Tested versions
4.3.dev5
System information
Windows10 - Vulkan
Issue description
The color argument appears to be ignored in GPUParticles2D's emit_particle method, despite passing the EmitFlags.EMIT_FLAG_COLOR flag.
Steps to reproduce
See MRP
Minimal reproduction project (MRP)
particlestest.zip

Thank you for your report, consolidating in:

https://github.com/godotengine/godot/issues/76360


Add property with Drools version

New property added that enables TCK runs with different Drools versions.

@etirelli can you please review this?


Keycloak URLs missing complete certificate chain

Background:
Information provided by @WadeBarnes
If I run a curl from a machine that does not have the the correct set of CA and intermediate certificates I get the following:
curl -v https://sso-dev.pathfinder.gov.bc.ca/auth/realms/sbtyffu4/.well-known/openid-configuration
*   Trying <IP_ADDRESS>...
* TCP_NODELAY set
* Connected to sso-dev.pathfinder.gov.bc.ca (<IP_ADDRESS>) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (OUT), TLS alert, unknown CA (560):
* SSL certificate problem: self signed certificate in certificate chain
* Closing connection 0
curl: (60) SSL certificate problem: self signed certificate in certificate chain
More details here: https://curl.haxx.se/docs/sslcerts.html

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.

 That way clients don't have to ensure they have the correct certificates installed on their machines.
Since the sso routes are just using the default, the issue is at the level where that certificate is specified.
Plan:

will install all required cert chain for new sso services
explore on how to fix the current issue as using default pathfinder route

When I browse to the site from the same machine the certificate path does not resolve all the way to the CA;

I've confirmed it only goes part way up the chain;

https://entrust.ssllabs.com/analyze.html?d=sso-dev.pathfinder.gov.bc.ca

Any update available?

Hey Wade, so now when I curl it, a complete handshake toke place:
curl -v https://dev.oidc.gov.bc.ca/auth/realms/idir/.well-known/openid-configuration
*   Trying <IP_ADDRESS>...
* TCP_NODELAY set
* Connected to dev.oidc.gov.bc.ca (<IP_ADDRESS>) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/cert.pem
  CApath: none
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Client hello (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS change cipher, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
* ALPN, server did not agree to a protocol
* Server certificate:
*  subject: C=CA; ST=British Columbia; L=Victoria; O=Government of the Province of British Columbia; CN=dev.oidc.gov.bc.ca
*  start date: Apr  2 17:25:36 2020 GMT
*  expire date: Apr  3 17:55:36 2021 GMT
*  subjectAltName: host "dev.oidc.gov.bc.ca" matched cert's "dev.oidc.gov.bc.ca"
*  issuer: C=US; O=Entrust, Inc.; OU=See www.entrust.net/legal-terms; OU=(c) 2012 Entrust, Inc. - for authorized use only; CN=Entrust Certification Authority - L1K
*  SSL certificate verify ok.
> GET /auth/realms/idir/.well-known/openid-configuration HTTP/1.1
> Host: dev.oidc.gov.bc.ca
> User-Agent: curl/7.54.0
> Accept: */*
>

Is there still issue with this?

Looks like it's fine now.  Ran curl on the affected server and the handshake completed successfully.  I'll confirm the related issue with the application is resolved.

We've confirmed the issue is resolved.


[analyzer] Stack overflow error if library tries to augment itself

The following code crashes the analyzer
// main_lib.dart
library augment 'main_lib.dart';
import augment 'main_lib.dart';

main() {}

According to the https://github.com/dart-lang/language/issues/3646 it should be a compile-time error
Tested using Dart SDK version: 3.4.0-edge.dfe0457f84352a402c7fe590c743cef3e2280509 (main) (Tue Mar 12 00:50:43 2024 +0000) on "linux_x64"

@scheglov


Add support for SLC6

Hi,
SLC6 can be supported too.
It is basically Scientific Linux CERN (it is CenOS fork) and the module is completely compatible.
Just the following needs to be added to the metadata:
{
"operatingsystem": "SLC",
"operatingsystemrelease": [
"6"
]
},

Hey,
Sorry for the late reply =>
There is no SLC7 anymore.
It was moved to CERN CentOS7, which facter recognizes as CentOs 7

There is however Scientific Linux 7, which is now maintained by fermilab and is different than the CERN fork of CentOS 7.


Monster widget capture icon shows for non capturable monster

Afflicted monster is non-capturable monster, but capture icon had showed.
It is confusing what viewed a capture icon draw on normal monster icon.

Fixed on #259


on-link needs a description

The print command often lists the gateway as 'on-link'. This needs defining.

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

ID: b5298689-e441-3788-b31d-967dbce4f735
Version Independent ID: 5b078c74-5b82-3b35-5842-8ce6142b2152
Content: route_ws2008
Content Source: WindowsServerDocs/administration/windows-commands/route_ws2008.md
Product: windows-server
Technology: manage-windows-commands
GitHub Login: @coreyp-at-msft
Microsoft Alias: coreyp

We hugely appreciate your contribution, feedback, and support to our technical documentation.
We’ve phased out GitHub Issues on this repository as the feedback mechanism for content and have replaced it with a new feedback system. For more information see, Content User Feedback. As part of this rollout, we are migrating your issue where our team will use your comments to improve the documentation experience. Unfortunately, this does mean you won't be able to access this issue after the migration is complete.
All issues will be migrated by Thursday 29th August 2024.
Once again, thank you for your valuable feedback, we hope you’ll continue to contribute using our new feedback system.


electrum server install ImportError

I have a trouble when i install the electrum server.The electrum server install document reference(https://github.com/spesmilo/electrum-server/blob/master/HOWTO.md).everything has been done before run "electrum-server start" command to launch electrum server.but it print an error: "ImportError: /home/bitcoin/.python-eggs/plyvel-0.9-py2.7-linux-x86_64.egg-tmp/plyvel/_plyvel.so: undefined symbol: _ZN6snappy13RawUncompressEPKcmP".
I have google with the keyword "_ZN6snappy13RawUncompressEPKcmP". i found a reference in this page("https://github.com/wbolster/plyvel/issues/5"). I do as this page said, but finally still failed. my leveldb is 1.9, i install the liblevedb1,libleveldb-dev,plyvel. can anybody help me to solve this big problem.thanks a lot!

have you installed leveldb?

look bitcoind debug ...maybe there were headers only not blocks.....
you need to resync bitcoind.

Yes the installation steps are broken, the easiest way to reproduce is just start clean Ubuntu 16.04 and go step by step with HOWTO doc. I was able to fix the issue by installing various python dev related stuff, cannot tell with exactly was the case. This is quite sad the issue was not resolved since 2014. There could be a CI setup to start electrum-server in regtest mode.


Progress is flickering

When progress is shown in compute client (e.g. new-Catlet) the progress is flickering, see this gif:

AB#686

After some investigation, I have not found any good solution to prevent the flickering. Some general notes:

Powershell 7 supports two rendering modes: Classic and Minimal:

Minimal is the default and shows one-line progress at the bottom
Classic has the same behavior as Powershell 5 and shows an overlay at the top

For performance reasons, Powershell renders progress updates only when a timer expires or an activity is completed. See https://github.com/PowerShell/PowerShell/blob/b428e1a393242ce15e54f24c6fcd9d8bae97ada2/src/Microsoft.PowerShell.ConsoleHost/host/msh/ConsoleHostUserInterfaceProgress.cs#L99. Hence, the amount and timing of render updates is hard to predict.
The Classic mode flickers in both Powershell 5 and 7 when using the new Windows Terminal (checked with version 1.21). I was able to reproduce the flickering with a minimal example which just starts and completes child activities in a loop.

The Windows Terminal currently has quite few open issues related to flickering and other rendering issues. We should postpone this issue for now as the root cause is most likely the rendering of Windows Terminal.


Update packages.yml

Fixing typo of minimum version of dbt_utils required

:oof: our bad!
Thank you


⚠ ClamAV has degraded performance

In a58d18b, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 555 ms

Resolved: ClamAV performance has improved in e6f98c1 after 5 minutes.


adds revision_override option

Allows for installing different C* versions on different hosts. I've been running cstar_perf_stress with the following file as input to confirm that it works:
https://gist.githubusercontent.com/mambocab/14fd5367ccd46eacc006/raw/745306fc4a1fdba7dccdec2ebd339592c54faaae/revision_overrides.json
You can look at the output section in the nodetool report for resulting stats file to confirm that the different nodes are running different versions of C*.
As far as I could tell, the return value from the changed bootstrap function isn't used anywhere, so I don't think changing the return type will break anything.

Ready for further review. Now uses a dict to express the expected and actual mappings from hosts to SHAs.

+1 looks great

Please don't merge yet. I made some errors on the code path with no overrides.

Ok, should be ready for merge now. Thanks!


[BUILD] Upgrade protobuf-java to 4.29.1

What changes were proposed in this pull request?

Why are the changes needed?

Does this PR introduce any user-facing change?

How was this patch tested?

Was this patch authored or co-authored using generative AI tooling?

Test first

Thanks @dongjoon-hyun


CHANGELOG for new release

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Plan for release:

Work down the currently open PRs (except #436 and #459, which need more work). Here, #438 is most important
Use this PR for the new release


WIP 631 log path

(need to update tests still)
Overview
Uses log-path flag for logging in places that were previously using fmt.Printf, or logging to stderr.
Fixes #
Pull request checklist

[ ] I have read the contributing guide.
[ ] I have agreed to the Contributor License Agreement.
[ ] I have updated the documentation.
[ ] I have resolved any merge conflicts.
[ ] I have included tests that cover my changes.
[ ] All new and existing tests pass.

Code review checklist
This is the checklist that the reviewer will follow while reviewing your pull request. You do not need to do anything with this checklist, but be aware of what the reviewer will be looking for.

[ ] Ensure that any changes to external docs have been included in this pull request.
[ ] If the changes require that minor/major versions need to be updated, tag the PR appropriately.
[ ] Ensure the new code is properly commented and follows Idiomatic Go.
[ ] Check that tests have been written and that they cover the new functionality.
[ ] Run tests and ensure they pass.
[ ] Build and run the code, performing any applicable integration testing.

It seems some tests fail, not sure because of the changes in this PR, will check:
./holder_test.go:420: not enough arguments in call to h.Holder.Open
	have ()
	want (io.Writer)
./holder_test.go:442: not enough arguments in call to h.Holder.Open
	have ()
	want (io.Writer)
FAIL	github.com/pilosa/pilosa [build failed]
# github.com/pilosa/pilosa/ctl
ctl/backup_test.go:193: not enough arguments in call to h.Holder.Open
	have ()
	want (io.Writer)
ok  	github.com/pilosa/pilosa/cmd	0.051s
?   	github.com/pilosa/pilosa/cmd/pilosa	[no test files]
FAIL	github.com/pilosa/pilosa/ctl [build failed]

Thanks @yuce - I haven't yet updated tests to match new function signatures. I'm sure that's at least part of the problem.


C++ API Docs ?

Hi Team,
Is there any C++ API usage docs.
https://erthink.github.io/libmdbx/group__cxx__api.html
Is there any estimation of when will it be made available ?

A simple example would suffice too.
I tried this to test db file creation:
#include <iostream>
#include "mdbx/mdbx.h++"
#include <string>

using namespace mdbx;

int main(int, char**) {
    std::cout << "Starting mdbx app!"<< std::endl ;

    env::geometry db_geometry;

    env_managed::create_parameters create_param;
    create_param.geometry=db_geometry;

    mdbx::env::operate_parameters operator_param;

    std::string&& db_file_path="./my-db";

    mdbx::env_managed env1 = mdbx::env_managed(db_file_path,create_param, operator_param);

    env1.close();

}

 but it gives me error: MDBX_TOO_LARGE

Seems this is a bug.

Briefly:

By default, the upper limit of a database is set to the maximum possible value supported by MDBX (≈128.0 TiB for 64-bit platforms), which is too large for most of machines.
Therefore, this leads to an error, but which exactly one depends on the OS and the MDBX version (MDBX_TOO_LARGE for last releast, MDBX_ENOMEM for current master, ERROR_OUTOFMEMORY/ERROR_NOT_ENOUGH_MEMORY/ERROR_INSUFFICIENT_RESOURCE_FOR_SPECIFIED_SHARED_SECTION_SIZE/ERROR_DISK_FULL/ERROR_FILE_TOO_LARGE, etc on Windows);
I need to think about how to fix this rationally and reasonable.

a@anuragvohraec, thanks for reporting this flaw.
The problem went unnoticed, because in the current usage scenarios and tests, the by-default values of some parameters are not used.


Make ruff configuration more strict

Enable all ruff rules that don't cause any trouble in the current code.
Resolve the reported violations.

Damn, lintje failed.

Damn, lintje failed. Something about changeset?

The changeset one is a hint, but for this change it's not necessary. We use it to build our changelogs.
The error is that you made a commit without starting the subject with an uppercase letter. The rests are just hints.


tests: Add assert_in_success_response in ZulipTestCase.

Clean up the instances of self.assertIn("string", result.content.decode("utf-8")),
and replace them with self.assert_in_response("string").
Fixes: #2313

Automated message from Dropbox CLA bot
@calvinleenyc, thanks for the pull request! It looks like you haven't yet signed the Dropbox CLA. Please sign it here.

Automated message from Dropbox CLA bot
@calvinleenyc, thanks for signing the CLA!

This looks great.  Merged, thanks @calvinleenyc!


fix: read context file sync way when calling context model

Fixes https://github.com/asyncapi/cli/issues/751

now oclif.manifest.json is also generated on local. Git ignored, but it will be published to npm as it is explicitly mentioned in package.json files
we read context file using node sync method as the parent function cannot run inside async function

@Souvikns @magicmatatjahu easy merge


[Doc] Mention quarters in quickstart.ipynb

Resolves #247 by explaining assignment of tpf variable.

Codecov Report

Merging #292 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #292   +/-   ##
=======================================
  Coverage   88.13%   88.13%
=======================================
  Files          26       26
  Lines        3674     3674
=======================================
  Hits         3238     3238
  Misses        436      436

Continue to review full report at Codecov.

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


Fix ES256K-R/EcdsaSecp256k1RecoverySignature2020 hashing

EcdsaSecp256k1RecoverySignature2020 and ES256K-R JWS algorithm are supposed to use SHA-256 as the digest algorithm, but were instead using Keccak digest. This PR fixes that.
Testing is added using the test vector verifiable credential from the specification repo / reference implementation (https://github.com/decentralized-identity/EcdsaSecp256k1RecoverySignature2020/).
This PR includes testing the original verifiable credential (https://github.com/decentralized-identity/EcdsaSecp256k1RecoverySignature2020/blob/c5f431472c0cf1fb9279249bf6a6ce01b01c70e6/docs/verifiableCredential.json) and a modified one which has been submitted as a bug fix (https://github.com/decentralized-identity/EcdsaSecp256k1RecoverySignature2020/pull/21). The test vector's JSON-LD context is changed to avoid having to bundle an additional context file, but you can compare the signatures in the proof jws properties.
Should support be kept for the old way, EcdsaSecp256k1RecoverySignature2020/ES256K-R using Keccak, for backwards compatibility?

Rebasing and merging


RT and resources deletion request (Stage and Production)

Following on previous request in #2805 , requesting the deletion of additional RTs and one resource.
Resource deletion request (Stage)

https://api.stage.sinopia.io/resource/09aff382-c06e-4a79-b001-c4ddd21af40d

RT deletion requests (Production)

https://api.sinopia.io/resource/my:primer:plantilla
https://api.sinopia.io/resource/WAU:RT:BF2:ContributionRoleLiteral
https://api.sinopia.io/resource/WAU:RT:BF2:ContributionAgentLiteral
https://api.sinopia.io/resource/WAU:RT:MADS:Authority
https://api.sinopia.io/resource/WAU:RT:BF2:ContributionLiterals
https://api.sinopia.io/resource/wau:RT:bf2:Monograph:Work

Please let me know if any additional information is needed. Thank you!
CC @CECSpecialistI

@briesenberg07 and @CECSpecialistI
Resource https://api.stage.sinopia.io/resource/09aff382-c06e-4a79-b001-c4ddd21af40d on stage is now deleted.
Deleted Production templates:

https://api.sinopia.io/resource/my:primer:plantilla
https://api.sinopia.io/resource/WAU:RT:BF2:ContributionRoleLiteral
https://api.sinopia.io/resource/WAU:RT:BF2:ContributionAgentLiteral
https://api.sinopia.io/resource/WAU:RT:MADS:Authority
https://api.sinopia.io/resource/WAU:RT:BF2:ContributionLiterals
https://api.sinopia.io/resource/wau:RT:bf2:Monograph:Work


Extract Deity information

Please extract deity information as well.

Should be good to go with Release 1.0.7

Does not seem to work.
I updated to version 1.0.8,
then ran "5e-convert.cmd --index -v -s"`*" -o WF .\5etools-mirror-1.github.io\data
This did not produce any deity files. (output1)
Copied the deities.json from the data directory,
then ran "5e-convert.cmd --index -o tt -v -s"`*" deities.json"
This did not produce any deity files. (output2)
Tried again using a source known to contain at least one deity (MTF)
PS D:\Temp\test> 5e-convert.cmd --index -o tt -v -s MTF deities.json
Again, no luck.
The index-files DO contain the deities, so there's that.
out1.txt
out2.txt
tt-json.zip

Give this a go... 1.0.9
jbang app install --name 5e-convert --force --fresh https://jitpack.io/dev/ebullient/json5e-convert-cli/1.0.9/json5e-convert-cli-1.0.9-runner.jar


tried this and error received, checked user and password provided by protonvpn

[!] Please make sure that your Username and Password is correct.
Device "proton0" does not exist.
Failed to bring up VPN :(```

Nevermind, it works with a protonvpn unlimited plan, not just mail plus.


Preventing crash when running on AWS Lambda

AWS Lambda functions are run in a readonly directory, which causes an OSError with icalevents as described in #65. Catching this error and calling httplib2 without cache fixes the problem.

Could you add a test as well as a log entry when this happens?
Wouldn't want it to silently happen undetectable for users who do want the cache.

To be honest, it's kinda hard to write an automated unit test for an absolute edge case with a readonly working directory. If you have an idea how this can be achieved easily, please give me a hint. As for the logging, of course its possible to add some print or stuff like that as icalevents doesnt seem to use the logging library yet. I'll do that in a few minutes.

To be honest, it's kinda hard to write an automated unit test for an absolute edge case with a readonly working directory. If you have an idea how this can be achieved easily, please give me a hint. As for the logging, of course its possible to add some print or stuff like that as icalevents doesnt seem to use the logging library yet. I'll do that in a few minutes.

You could set up a test where you set the permission to read only (e.g. 550) and revert it after the test finished, during this test you would assert that the expected log message would be outputted.
It also would be beneficial to use the logging module over print so output can be configured by the user more easily.

Well thats of course correct, but honestly I'm not going to change half of the whole project for a Pull Request that just adds half a line of code and is more of a hotfix for everyone that encounters this problem. The test should have already been in place before as I only added a catch for another error that is caused by the same issue. So I'm not going to be the one fixing the problems of others. I'm just a user that encountered this problem and wanted to provide the fix for everyone. If there is a problem with this approach of mine, feel free to close my PR as I already fixed the stuff sufficiently for me to use it in my projects. Everyone else, like John from #65, has to fix it for themselves then I guess.

No worries, I'm just a user as well. I'm just worried that if we don't make sure to improve the testing with every patch library will deteriorate, and I wouldn't wan't silent failures for things like non writable file systems.

This impacts Azure as well as AWS, and the fix looks like it would fix both.

I ran into this issue as well. Just posting my workaround in case it helps anyone. AWS Lambda provides a /tmp mount that is writable, so just change to that directory first.
os.chdir("/tmp")
calendar_events = icalevents.events(string_content=calendar, start=start, end=end)

I ran into this issue as well. Just posting my workaround in case it helps anyone. AWS Lambda provides a /tmp mount that is writable, so just change to that directory first.
os.chdir("/tmp")
calendar_events = icalevents.events(string_content=calendar, start=start, end=end)

I’m happy to merge this If someone is willing to write proper tests for the functionality.

I’m happy to merge this If someone is willing to write proper tests for the functionality.

I'm working on a test right now as this seems to affect a lot of users, guess I'll get it done today

I'm working on a test right now as this seems to affect a lot of users, guess I'll get it done today

Since the latest ci run failed, i looked into it and it seems that python needs sudo rights to perform os.chmod() commands. The travis config specifically says that the job should run without sudo. Not sure what to do here now.

Since the latest ci run failed, i looked into it and it seems that python needs sudo rights to perform os.chmod() commands. The travis config specifically says that the job should run without sudo. Not sure what to do here now.

Since the latest ci run failed, i looked into it and it seems that python needs sudo rights to perform os.chmod() commands. The travis config specifically says that the job should run without sudo. Not sure what to do here now.

Try using a tmp directory, should allow you to set whichever permissions. Chmod should work fine without sudo if you own the directory.

Since the latest ci run failed, i looked into it and it seems that python needs sudo rights to perform os.chmod() commands. The travis config specifically says that the job should run without sudo. Not sure what to do here now.

Try using a tmp directory, should allow you to set whichever permissions. Chmod should work fine without sudo if you own the directory.

@Mueller-Patrick I merged your change. I don't have the credentials to cut a new release on pypi so we'll have to wait on @irgangla for that.

@Mueller-Patrick I merged your change. I don't have the credentials to cut a new release on pypi so we'll have to wait on @irgangla for that.


Brightroll - enable adapter

Enabling adapter for integration testing.
Is this a required change? or will it enable by any other settings on Prebid server. I need this change for local testing. So hope it is needed change for production as well. Please confirm.
@rpanchyk , @DGarbar

@rpanchyk , @DGarbar Is this change needed to start integration testing ? Or will it already enabled or automatically enabled when released to production?
If it is needed , can you please include this along with cookie sync config change push PR #682 (https://github.com/rubicon-project/prebid-server-java/pull/682)

Actually, this change is not required.
We've already enabled Brightroll in Prebid production.

cool. thanks for letting me know. I will close this PR in that case.


Website is outdated

Some functions are missing from the said .org, such as PMT. I spent some time writing that function into the library only to notice later it's already there, but not in the "official" docs.
Please update it :(
Suggestion: make it a simple GHPage based on the README. Much better than leaving both out of sync (and making a markdown file seem like a HTML thing)

PMT is on the github README file. Re: the .org site, I no longer own the domain; therefore, I am unfortunately unable to make any updates at this time. I am working on removing all references to the .org site.

Omg! That's bad x_x
Push a GHPages site, based on the readme, and use it instead :)
Igor Santos
-- Desenvolvedor Web
[enviado do meu celular]
On Jan 22, 2017 21:29, "Essam Joubori"<EMAIL_ADDRESS>wrote:

PMT is on the github README file. Re: the .org site, I no longer own the
domain; therefore, I am unfortunately unable to make any updates at this
time. I am working on removing all references to the .org site.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/essamjoubori/finance.js/issues/24#issuecomment-274369323,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAgfS-8QTUzBNgfeDiXwiwoD44GHoKVQks5rU-ZOgaJpZM4LpQij
.


Mocked interface cannot be added to HashSet

This issue happens on master, but doesn't happen on 2.0.5.
Here is an example:
Interface Foo {
    String name();
}

@Test public void testMockFoo() {
    Set<Foo> foos = new LinkedHashSet<>();
    Foo foo = Mockito.mock(Foo.class);
    foos.add(foo);
}

It will blow up with
......Error: signal 11:
0   tests_j2objc_test_executable_lipobin 0x0000000104763c9c signalHandler + 39
1   libsystem_platform.dylib            0x0000000108dbaf5a _sigtramp + 26
2   libobjc.A.dylib                     0x0000000107e46802 _ZL14_mapStrIsEqualP11_NXMapTablePKvS2_ + 38
3   tests_j2objc_test_executable_lipobin 0x00000001049f096e -[JavaUtilHashSet addWithId:] + 40

This was caused by the recent Proxy change to support Object.equals(), hashCode() and toString() methods to be forwarded to the proxy's invocation handler (the Objective C runtime doesn't call respondsToSelector: to see if the message should be sent to forwardInvocation:, presumably because all objects respond to those methods' selectors). I'm working on a rewrite of that change, but it's proving to be too fragile (crash-prone) to use so far.

Fixed in current source.


Error loading Plaid null appears to be back in v2.2.3

I'm receiving the same Error loading Plaid null that appears to be reported in issue #86 when upgrading to v2.2.3.
It does appear react-script-hook was upgraded to v1.1.0 in v2.2.3, I haven't dug in to see if that could be causing the issue or not.
If I navigate away and back, everything works and there is no error.
I downgraded to v2.2.1 and it works fine.

I'm seeing this too but it's not consistently reproducible, it just seems to happen occasionally to some users.

I am experiencing this as well. It is (somewhat) consistent to reproduce if you have multiple components using the usePlaidLink hook loading at the same time. I have a use case where I want to have one PlaidLink control on the page for the user to link new institutions, and another PlaidLink control on the same page that will open Plaid in update mode for an existing institution link. In this scenario, I can keep refreshing the page, and about 50% - 75% of the time I will encounter this error which prevents one or the two controls from working.

I am experiencing this as well. It is (somewhat) consistent to reproduce if you have multiple components using the usePlaidLink hook loading at the same time. I have a use case where I want to have one PlaidLink control on the page for the user to link new institutions, and another PlaidLink control on the same page that will open Plaid in update mode for an existing institution link. In this scenario, I can keep refreshing the page, and about 50% - 75% of the time I will encounter this error which prevents one of the two controls from working.

Experiencing the same issue, @zsidnam were you ever able to figure out a solution?

@wnamen Unfortunately, I was not able to find a good solution for this. However, I added <script src="https://cdn.plaid.com/link/v2/stable/link-initialize.js"> into my index.html as one user suggested in the comments at the bottom of #86 and this "fixed" the issue for us by making sure the script was loaded before the hooks get run. Not a permanent solution but it got us up and running until this issue gets resolved.

Also experiencing this for production users using v3.0.0. I had previously had issues with the link declaring more than once, but that was solved in #109, not sure if that fix unintentionally caused this as well

What is the latest on this??

Experiencing this issue as well, pretty regularly

We're seeing this issue too. Any update?

We're seeing this issue too. Any update?

I'm seeing this in 3.1.0.  For me the issue is highly reproducible when I use multiple "link" buttons on the page. On initial load / page refresh one button usually loads correctly while the other buttons often (but not always) fail. When one fails it remains disabled and there is a stack trace like the below. Sometimes (but not always) they all load correctly.

I added

This is happening to me as well. I have a use case where I need multiple link buttons on one page, and get this error every time on page load. I'm on version 3.1.0 using usePlaidLink hook.
Error loading Plaid null
For now, also using the workaround by adding

I can confirm as well this is still happening. @ipam73 solution works for now as a workaround. It would be great when this is fixed within the lib.

Interesting I thought we fixed this in 3.1.0 via #164. I'll have to take another look at the case where there are multiple link instances being initialized at the same time.

we using 3.1.0 and still getting
Error loading Plaid null in some case
the one case that this will always happen is if the first page the user see is using plaid hook

This is still an issue on v.3.2.0.  Any plans to fix it?

Guys, is any minor release planned? npm says that last updated was 5 months ago, so the fix above is not delivered yet.
This issue is too unexpected as it blocks the whole integration with Plaid.

@SnapeEye I just published 3.2.2 which includes this fix, sorry for the delay!


[Docs] Feature: Automatically unroll function inputs and outputs

Problem solved
Previously we made no attempt to unroll function inputs and outputs in the docs. This made things difficult to quickly scan since every function has a typed input and output object you would have to navigate to.
This PR is a first attempt at basic unrolling functionality of these typed inputs and outputs.
Before:

After:

As an additional readability bonus, the input and output sections now start as an open accordion.
Note: There are still improvements to be made especially on functions with more complex types. These functions' interfaces should be simplified in future versions.
Next Steps
Future features should add nested input descriptions (supported by typedoc but not typedoc-better-json). Future SDK versions should use simpler, explicitly typed inputs and outputs to simplify the unrolling process (and easier LSP support for users).
To Test
Open the preview URL, click around to various functions and inspect the parameter and return types

PR-Codex overview
This PR updates transaction handling and TypeScript documentation rendering.
Detailed summary

Added fetchDocBySlug function to fetch TypeScript docs by slug
Modified SendTransactionOptions to use interface instead of type
Updated TypeScript documentation rendering to include interface docs for return types and parameter types

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

doesn't seem to work reliably?: https://docs-v2-bt6g06ruj.thirdweb-preview.com/references/typescript/v5/BuyDirectListingButton (just one example, click around in the reference its most (?) things)
random concerns:

this loses the actual type name which may be relevant to import for users?
ideally we'd do something like https://shikijs.github.io/twoslash/ which gives us best of both worlds here?

We keep the type name in the function signature section.
What's wrong with the example you sent? We can't drill all the way down for union types (at least not without modifying the typedoc json converter, which is a bigger lift), but we can't at least get the main arguments so they have some idea of what to put. This essentially shows what they would see if they clicked into the type name, but on the same page.
twoslash looks nice, but it wouldn't solve the underlying problem, which is deeply abstracted types that we don't parse all the way down.

oh, I assumed it would unfurl it everywhere - that seems OK then


Add an snapshot_encoding argument

Please see https://github.com/joseph-roitman/pytest-snapshot/issues/24 for the discussion

No need for this.

No need for this.


Add script to repo to remove a dependency from a package

Lerna currently doesn't have support for removing packages from the root, this is a big pain as you basically need to manually remove stuff and then regenerate the lockfile afterwards atm.
One way we could get around this for now is to write a script we can use to do so ourselves. That said, it might be better to just open a PR on lerna to get this working.

Look into support in Lerna 2


Request extra scope for full API access

Also fix some missing newlines.
Shouldn't be merged until corresponding backend changes are merged :).

Extra context: lack of newlines were annoying me, since zsh warns about it :D


Small docstring fixes

[x] passes git diff upstream/master -u -- "*.py" | flake8 --diff

Thanks!


MINOR: StreamsConfig upgrade.from should not be in list of deprecated configs

\cc @bbejeck @vvcephei

Java 8 failed on unrelated test
retest this please

Merged to 0.11.0.


First google result for dat.gui is the deprecated Google Code repo

https://code.google.com/p/dat-gui/ is the first google result for dat.gui.
And as seen on this page 'Google Code will be turning read-only on August 25th.'.
I would suggets to change the content of the https://code.google.com/p/dat-gui/ homepage to link to this GitHub repo.

Also if you visit http://dataarts.github.com/dat.gui as mentioned in the source files it will redirect to the code.google.com page.

+1

Thanks for bringing this to our attention.  I've fixed the redirect that you mentioned @kribblo, it will now take people to the GitHub repo.
The Google Code page is now far down on search results, and I've requested to have the archive removed once and for all.

Okay, Google Code page is now officially gone.


[BUG] Why i can't put the code/script into the Export JSON?

Acknowledgement of preliminary instructions

[X] I have read the preliminary instructions, and I am certain that my problem has not already been addressed.
[X] My answer given in the checkbox above is a lie.

What problem did you encounter?
plz help

my face when "My answer given in the checkbox above is a lie"
seriously man

what i want you to do is the following:

next time you open an issue, read the preliminary instructions to make sure the bug is NOT known
when you do open one, actually explain your issue, instead of saying "plz help"
next time this topic is brought up, call them FastFlags (or FFlags for short), not "codes" or "scripts"

actual solution to the issue
when you export your flag list as a JSON, it gets put on your clipboard, hold the Start button, and press V to see it, if you for some reason that not even God knows, you have it disabled, please, for the sake of us, enable it
if it is enabled, you can click it while a text box is selected to paste it in there, here's an example list with my personal FFlag choice
{
  "FFlagRenderCheckThreading": "True",
  "FLogNetwork": "7",
  "DFIntDebugFRMQualityLevelOverride": "2",
  "FFlagDebugGraphicsDisableVulkan": "False",
  "DFFlagDebugRenderForceTechnologyVoxel": "True",
  "FFlagDebugGraphicsDisableVulkan11": "True",
  "FFlagDebugGraphicsPreferVulkan": "True",
  "FFlagRenderVulkanFixMinimizeWindow": "True",
  "FFlagEnableBetterHapticsResultHandling": "True"
}

Issue will be reopened once clearer, more helpful details are given


Remove download link from pre-refactor UI

When you click on a folder or item, don't show the download link

Why it shouldn't be visible for an item?
Also see #274


add AVS 2022-05-01 API

A prior internal review was completed in https://github.com/Azure/azure-rest-api-specs-pr/pull/5032 .
ARM API Information (Control Plane)
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Azure 1st Party Service can try out the Shift Left experience to initiate API design review from ADO code repo.  If you are interested, may request engineering support by filling in with the form https://aka.ms/ShiftLeftSupportForm.
Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

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

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
By default, Azure SDKs of all languages (.NET/Python/Java/JavaScript for both management-plane SDK and data-plane SDK, Go for management-plane SDK only ) MUST be refreshed with/after swagger of new version is published. If you prefer NOT to refresh any specific SDK language upon swagger updates in the current PR, please leave details with justification here.

Contribution checklist (MS Employees Only):

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

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

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

Change to data plane APIs
Adding new properties
All removals

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

[x] Check this box if any of the following apply to the PR so that the label "ARMReview" and "WaitForARMFeedback" will be added by bot to kick off ARM API Review.  Missing to check this box in the following scenario may result in delays to the ARM manifest review and deployment.

Adding a new service
Adding new API(s)
Adding a new API version
-[x] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits. You can use OpenAPIHub to initialize the PR for adding a new version. For more details refer to the wiki.

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

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

Breaking Change Review Checklist
If you have any breaking changes as defined in the Breaking Change Policy, request approval from the Breaking Change Review Board.
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Additional details on the process and office hours are on the Breaking Change Wiki.
NOTE: To update API(s) in public preview for over 1 year (refer to Retirement of Previews)
Please follow the link to find more details on PR review process.

        "description": "The sku to check for trail availability",

trial

Refers to: specification/vmware/resource-manager/Microsoft.AVS/stable/2022-05-01/vmware.json:353 in ba95e1b. [](commit_id = ba95e1be0317f6b2c74653f9d5037a9b3df23a6a, deletion_comment = False)

        "$ref": "../../../../../common-types/resource-management/v1/types.json#/parameters/SubscriptionIdParameter"

Recommend moving to v3 common types. Comment applies everywhere in added sections of this PR.

Refers to: specification/vmware/resource-manager/Microsoft.AVS/stable/2022-05-01/vmware.json:1075 in ba95e1b. [](commit_id = ba95e1be0317f6b2c74653f9d5037a9b3df23a6a, deletion_comment = False)

"/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.AVS/privateClouds/{privateCloudName}/workloadNetworks/default": {

Currently recommending using string enum parameter instead of hard-coding the path segment. Look here for an example: https://github.com/Azure/azure-rest-api-specs/blob/fa581bd5f31cbc6f6882b254ce5b0f5c20d84648/specification/dns/resource-manager/Microsoft.Network/stable/2018-05-01/dns.json#L66

Refers to: specification/vmware/resource-manager/Microsoft.AVS/stable/2022-05-01/vmware.json:1959 in ba95e1b. [](commit_id = ba95e1be0317f6b2c74653f9d5037a9b3df23a6a, deletion_comment = False)

          "$ref": "#/definitions/WorkloadNetworkSegmentsList"

Looks like this should be WorkloadNetworkList.

Refers to: specification/vmware/resource-manager/Microsoft.AVS/stable/2022-05-01/vmware.json:2029 in ba95e1b. [](commit_id = ba95e1be0317f6b2c74653f9d5037a9b3df23a6a, deletion_comment = False)

    "nsxPublicIpQuotaRaised": {

Consider easier/more discoverable enum values, maybe something more like: nsxPublicIpQuota: { Basic64 (or Default64?), Extended1024 }. This also allows adding different quota settings in future (e.g. Default, Standard, Large, Medium, ...).

Refers to: specification/vmware/resource-manager/Microsoft.AVS/stable/2022-05-01/vmware.json:6020 in ba95e1b. [](commit_id = ba95e1be0317f6b2c74653f9d5037a9b3df23a6a, deletion_comment = False)

    "vCenter": {

vCenterResourceId?

Refers to: specification/vmware/resource-manager/Microsoft.AVS/stable/2022-05-01/vmware.json:6313 in ba95e1b. [](commit_id = ba95e1be0317f6b2c74653f9d5037a9b3df23a6a, deletion_comment = False)

  "properties": {}

Don't include an empty property bag. If there are no RP properties, just leave it out.

Refers to: specification/vmware/resource-manager/Microsoft.AVS/stable/2022-05-01/vmware.json:6820 in ba95e1b. [](commit_id = ba95e1be0317f6b2c74653f9d5037a9b3df23a6a, deletion_comment = False)

  "x-ms-enum": {

You can add per-member descriptions as part of this extension. Seems like it would be helpful for this one and AzureHybridBenefitType.

Refers to: specification/vmware/resource-manager/Microsoft.AVS/stable/2022-05-01/vmware.json:7882 in ba95e1b. [](commit_id = ba95e1be0317f6b2c74653f9d5037a9b3df23a6a, deletion_comment = False)

    "uri": {

supportUri or companySupportUri?

Refers to: specification/vmware/resource-manager/Microsoft.AVS/stable/2022-05-01/vmware.json:7918 in ba95e1b. [](commit_id = ba95e1be0317f6b2c74653f9d5037a9b3df23a6a, deletion_comment = False)

@mentat9, thanks for the review. I fixed the majority of issues you brought up. I like the property rename suggestions for nsxPublicIpQuotaRaised, vCenter and uri, but would prefer not to delay shipping this API.
A breaking change showed up today for "1047 - XmlEnumChanged" related to a646bc32442446f8319114b2f74aa7ffe1028213. I added them in the first place because an error saying they were needed. Should I keep those changes or revert them?

@mentat9, thanks for the review. I fixed the majority of issues you brought up. I like the property rename suggestions for nsxPublicIpQuotaRaised, vCenter and uri, but would prefer not to delay shipping this API.

OK, not blocking ARM signoff on those suggestions. Please consider the feedback for future Azure API specs.

A breaking change showed up today for "1047 - XmlEnumChanged" related to https://github.com/Azure/azure-rest-api-specs/commit/a646bc32442446f8319114b2f74aa7ffe1028213. I added them in the first place because an error saying they were needed. Should I keep those changes or revert them?

Odd. I don't think that should be a breaking change, but the SDK team would be the ones that know about it. @qiaozha - Is any change required for this?

@tadelesh Can you help take a look at the Go SDK breaking change error ?

@msyyc Can you help take a look at the Python SDK breaking change ? Thanks

@jianyexi Can you help take a look at the staging lint diff error ?

/azp run

approved for python breaking

The  staging lintDiff error at https://github.com/Azure/azure-rest-api-specs/pull/20873/checks?check_run_id=8608952837 should also be fixed as many as possible if there would be no breaking change when fixing it

When did Staging LintDiff errors become required? My approach will be to:

Update to use suppressions config.
Suppress all errors and warnings.
Fix one error code at a time.
Get a suppression review when complete.

This will take a few commits. Here are the error codes that I will need to work through:

code: ConsistentPatchProperties
code: DefinitionsPropertiesNamesCamelCase
code: DeleteOperationAsyncResponseValidation
code: IgnoredPropertyNextToRef
code: LroLocationHeader
code: LroPatch202
code: PatchSkuProperty
code: RequiredReadOnlySystemData
code: UnSupportedPatchProperties
code: XmsLongRunningOperationOptions

I'm going to mark this as draft while I work on these changes.

The ConsistentPatchProperties fix b88a2c064b31198844432c06142212ab8cd92d7d results in breaking changes, so will revert and suppress.

I submitted a Swagger Suppression Request just now.

AFAICT, those are all flagging existing APIs, not APIs newly added in this PR. There appear to be many issues with this spec from ARM perspective, but the current review only covers the changes in this PR, not the entire API surface.

That is correct. These suppressions are for existing APIs, not newly added APIs. Most are documented at:
https://github.com/Azure/azure-openapi-validator/tree/develop/docs

/azp run

Review has already been signed off from ARM. Please remove "ARMSignedOff" and add "WaitForARMFeedback" if you need us to take another look

@jianyexi @josefree could you help to take a look at the suppression request?

@qiaozha, can you merge this now that suppression has been approved?


Dev to main

When we confirm this PR, we will make a new version branch from main

when we confirm this pr @Andrew-Clappison will made a 'back-up' brach of main


Please make junit a test-scoped dependency

This stops the dependency leaking into other projects when they depend on the library.
It also helps stop you using JUnit classes in production code.
You can read more about test scopes in the Maven documentation:
https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Scope

Thank you! I love maven ... not. ;-)


Caused by: java.lang.ClassNotFoundException: net.minecraftforge.client.model.generators.ModelFile

Seems like there's some missing files in the latest build.
9/10 times won't launch, 1/10 times it will but idk why it will sometimes and won't sometimes?
crash-2023-03-22_14.11.06-client.txt

I'd check Create Crafts and Additions, make sure you haven't accidently installed the Forge version, seems to be a crash related to that not Create

Turns out Create (not the additions version) just isn't fully ready for Fabric 0.14.17, cuz it works perfectly on 0.14.16.

Noticing this issue on Quilt too.

duplicate of #845


[Docs] New page for installation of Meshery on Openshift

Current State
Meshery Docs has a number of installation instructions for individual Kubernetes distributions - https://docs.meshery.io/installation
While much of the installation process is the same across distribution, on occasion, there are small differences. There is no specific set of instructions for installing Meshery on Openshift (https://docs.openshift.com).
Desired State
Create a new page with instructions for installing Meshery on Openshift. Use the same format as other Kubernetes installation pages and use include to reuse common instructions.

Contributor Guides and Handbook

📚 Instructions for contributing to documentation

Meshery documentation site and source

🛠 Meshery Build & Release Strategy
🎨 Wireframes and designs for Meshery UI in Figma (open invite)
🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack

@leecalcote assign this to me also


ContributorsPage

Added ContributorsPage, i.e. Populated with static Data in Contributor.swift.

ContentTile from existing Components.
Placeholder HeaderView  from @SwiftyAlex ( shall be replaced by the original component from @kannanprasad87

My only thought @luckyagarwal  - it would be great to add a header ( steal the one from the sponsors section ), so that accessibility users get "Contributors" read out before the list?

Well, It has been added.


Missig CesiumRuntime, CesiumEditor

Hi. I use Unreal Engine 4.26.2 in Ubuntu 20.04, i built Cesium for Unreal from source without errors, when i use it in project, i have error, Missing modules: The following modules are missing or built with a different engine version:
CesiumRuntime
CesiumEditor
Engine modules cannot be compiled at runtime. Please build through your IDE

.
Please help.How to fix it?

Have you looked at the Unreal Engine packaging step for the plugin that builds the modules? See the Linux command under https://github.com/CesiumGS/cesium-unreal/blob/main/Documentation/packaging-guide.md

Great Thanks, @shehzan10 !
Module is working fine!


Documentation: add the ability to create an alsa ucm profile and send alsa hints to specific cards

Problem
context: https://discourse.nixos.org/t/needing-help-for-getting-custom-alsa-profiles-with-alsa-hints-to-work/37261
basically there is no way to add an alsa profile something like
[General]
auto-profiles = yes

[Mapping headphones]
device-strings= hw:0,2
channel-map = left,right
paths-output = behe-headphones
paths-input = analog-input-headphone-mic analog-input-headset-mic
priority = 20

[Mapping speaker]
device-strings= hw:0,0
channel-map = left,right
paths-output = behe-speaker
paths-input = analog-input-front-mic analog-input-rear-mic analog-input-internal-mic analog-input-dock-mic analog-input analog-input-mic analog-input-linein analog-input-aux analog-input-video analog-input-tvtuner analog-input-fm analog-input-mic-line analog-input-headphone-mic analog-input-headset-mic
priority = 18

[Profile help]
input-mappings = speaker headphones
output-mappings = speaker headphones
description = both_both_is_good
skip-probe = yes
priority = 100

.include 9999-custom.conf

in /usr/share/alsa-card-profile/mixer/profile-sets/
or alsa hints (I don't really know how to create them since I used hdajackretask when I was on arch but its broken on nix)
maintainers
@L-as
@AndersonTorres
so update
so that seems like an alsa config profile I guess and not a ucm one
but my stance is still there if I can't do this using ucm profile
(I have no idea how to test this or make a temporary directory or something to test my ucm profile)
and there is still the problem of creating an alsa hint
adding the modprobe option part is easy since boot.extraModprobeConfig exists but I need to add stuff to /lib/firmware
so adding an option to automate this process would be nice to be hoenst at least the alsa hints like indep_hp=1
anyway I'm gonna tag pipewire maintainer cause well he probably knows more and this issue has been waiting for 3 days and well why not
Add a :+1: reaction to issues you find important.

anyway maintainer of alsa-ucm-conf: @roastiek
and maintainer of pipewire: @Kranzes and @K900
and yeah sorry for tagging you

I have looked around briefly as i never have work with this.
alsa-card-profile is part of pipewire, not alsa (by find /nix -name alsa-card-profile). One way would be patching pipewire package directly. However using /etc/alsa-card-profile/... should by fine too, infered from souce https://github.com/PipeWire/pipewire/blob/4ef891b047023c0380ca3fc67cce91d858ee863d/spa/plugins/alsa/acp/compat.c#L279 (Modifying anything under /usr/ directory is always suspicious.)
And for hdajackretask maybe this https://discourse.nixos.org/t/fixing-audio-on-asus-strix-scar-17-g733qs/12687

well why would it be suspisious if its only allowed by a configuration option
also its in the official documentation: https://www.freedesktop.org/wiki/Software/PulseAudio/Backends/ALSA/Profiles/
and well I made this issue since well if this can be added natively and not having to create a systemd service for this
but anyway thanks


fix(table): amend shadow to false for gux-all-row-select, gux-row-select

A bug was found in the gux-all-row-select and gux-row-select internal components in new versions of safari 16+. The root cause of this issue was from enabling shadow on these components during v4 developments. I have now set shadow to false on these components for the time being.
https://inindca.atlassian.net/browse/COMUI-2582

Where are we currently with this PR? Is it waiting for further review, or should we close this PR for now and revisit it with other future table work?

Where are we currently with this PR? Is it waiting for further review, or should we close this PR for now and revisit it with other future table work?

Will close this off and add it back to the backlog, hopefully a newer version of safari may fix this on its own.


[Enhancement]: Add a refresh score button in the rock paper scissor game.

Do you want to have the enhancement of existing game ? 😀 Describe yourself..
A refresh score button in the game, on click will change all the scores back to zero so that the game can be started from the beginning.
Describe the solution you'd like
I can create this button using HTML,CSS and its implementation using JavaScript which on click will revert all the scores back to zero.
Select program in which you are contributing
GSSoC24
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

Hey @meetarora10 !
Thank you for raising an issue 💗
You can self assign the issue by commenting /assign in comment 😀
Make sure you follow CODE OF CONDUCT and CONTRIBUTING GUIDELINES 🚀
Don’t Forget to ⭐ our GameZone🎮
Make sure you join our Discord🕹

/assign

Hey @meetarora10 ! Thank you so much for your raising the issue💗
It’s all yours, you can come anytime again and make some contributions! 🚀
Alone, we can do little, but together we can do so much! 😇


Add support for lix/haxeshim

FD relies on parsing the Haxe SDK CHANGES.txt file to determine the SDK version. This breaks when trying to add haxeshim as the Haxe SDK.
Proposed changes: When adding an SDK:

run haxe --run show-version (haxeshim feature) to check for haxeshim
if failed, run haxe -version (haxe feature) to get the version
if failed, try to get the version from CHANGES.txt
Another option - check if project has a .haxerc file to detect haxeshim

FD relies on haxelib to get the standard library path and to resolve other libraries. This breaks if the project uses haxeshim/lix for haxe version management and library management, respectively.
Proposed changes:

if the selected SDK is actually haxeshim, use features provided by it to resolve libraries
otherwise, use haxelib

Just sharing my setup here. I have lix installed locally in the project.
I use this as "prebuild command-line":
$(ProjectDir)\node_modules\.bin\haxe.cmd --run resolve-args build-$(BuildConfig).hxml > haxedevelop.hxml
$(ProjectDir)\node_modules\.bin\haxe.cmd $(OutputFile)

I use haxedevelop.hxml as hxml config:

This all works nicely, but I only need to configure the SDK.
I tried this, but this doesn't work:

To support lix  it would be nice if this could be supported (or we should know what path to enter here)

@markknol I would appreciate if you can test the PR (with haxeshim/lix project as well as a regular project).
I tested with a sample Haxe-JS project.

Add an SDK pointing to your %APPDATA/npm, where haxeshim's haxe.exe resides.
Add your library names to libraries list in the project properties (e.g. tink_core, etc.)
Nothing else should be necessary.

That assumes lix/haxeshim is installed globally? Is it also possible with local installed versions?
How can I test this version? Is there a binary available or something?

I tested with a global installation, but you can try to add a locally installed SDK (FlashDevelop properties, HaxeContext, Installed SDKs) and see if it works. In theory it might :)
Here's a direct link to the build: https://ci.appveyor.com/api/buildjobs/9urt84p92t91a0yh/artifacts/FlashDevelop%2FInstaller%2FBinary%2FFlashDevelopPR_2112.zip
Tip: you can find a build for any open Pull Request:

Open the PR link, e.g. in this case it's https://github.com/fdorg/flashdevelop/pull/2112
Scroll down to "All checks have passed", and click "Show all checks" on the right, you will see AppVeyor build, click "Details"
On the right side, click "ARTIFACTS", there will be a link to a Zip you can download and test

@back2dos maybe you can also take a look together with @Neverbirth to check what is wrong, which features are missing etc?

So, it works for globally installed lix! :)
But:

the version detection logic derails somewhat if you have the latest haxe (probably because haxe -version yields 4.0.0 (git build development @ 3018ab109) which is what haxe --run resolve-args prints).
if I try to use node_modules\.bin I get "this project doesn't have a proper SDK defined". That one contains only a haxe.cmd, although I could dump an exe there on windows if it helps?

@back2dos
https://ci.appveyor.com/api/buildjobs/66cb8x8qxhvun2hv/artifacts/FlashDevelop%2FInstaller%2FBinary%2FFlashDevelopPR_2112.zip
The two issues you reported should be resolved now. Please try it :)

Ok, seems to work fine.