Upgrade to latest Sphinx 5.1.1 and fix the top Edit on Github link

"Edit on Github" link wasn't working and pointing to a non-existent "index" file. This was most likely because we override the index.html template, so the  source renderer doesn't know what to link it to. Instead opt to make the top level "Edit on Github" point the docs readme page. Individual doc pages will point to their respective source pages.
In addition, we were quite a bit behind on on the sphinx version 1.5 vs 5.1.1 this has caused quite a bit of headaches over the years as we had to pin jinja2, docutils and other libraries versions to avoid breaking things.
The main issue after the upgrade was that the http domain became a bit more strict. After vendoring it in, we had to make a few multipart http examples use plaintext. On the positive side, it found broken references in the admin guide, so those were fixed. Since we're using the latest 5.1.1 opt to just use a python3 venv with a short setup.sh script. That should make it easier for contributors to build docs locally.

The rendered example of this PR is at https://docs.couchdb.org/en/try-to-fix-docs-edit-link/

only a small question: could we add httpdomain from sphinxcontrib over pip to easier update this extension?

good idea, @big-r81, I'll give that a try

@big-r81 great suggestion! httpcontrib now come from pip


[BUG] Get-PnPFileSharingLink and Get-PnPFolderSharingLink does not return anything for shared files/folders

Reporting an Issue or Missing Feature
Get-PnPFileSharingLink
and
Get-PnPFolderSharingLink
does not return anything even when files/folders are shared
Expected behavior
When calling the cmdlets
Get-PnPFileShareingLink
and
Get-PnPFolderSharingLink
I expected to get sharing link kinds for the files/folders (including LinkKind for review sharing according to feature #2949 )
When I call the [Microsoft.SharePoint.Client.ObjectSharingInformation]::GetObjectSharingInformation(..) I get the 5 standard sharing links.
What am I doing wrong?
Actual behavior
Nothing is returned when calling the cmdlets. If I call the cmdlets with invalid data, they return "Item not found" (expected)
Steps to reproduce behavior
connect-pnponline -url "https://contoso.sharepoint.com/sites/test" -interactive
get-pnplistitem -List Documents | % { Get-PnPFileSharingLink -FileUrl $_["FileRef"]}

(nothing is returned even though several files in the doclib are shared)
If I instead call the static method GetObjectSharingInformation(..) i get the link (and all other data left out for this example for brevity)
$ctx = Get-PnPContext
get-pnplistitem -List Documents | ? { $_["FSObjType"] -eq 0 } | % {
$SharingInfo = [Microsoft.SharePoint.Client.ObjectSharingInformation]::GetObjectSharingInformation($Ctx, $_, $false, $false, $false, $true, $true, $true, $true)
        $ctx.Load($SharingInfo)
        $ctx.ExecuteQuery()
$SharingInfo.SharingLinks | % { $_.Url }}

Example output that shows links are shared:
https://contoso.sharepoint.com/:i:/r/sites/test/Shared%20Documents/breach.png?csf=1&web=1
https://contoso.sharepoint.com/:w:/r/sites/test/Shared%20Documents/Document.docx?d=w584a9b0646104a9a95bdc58c446262e8&csf=1&web=1
https://contoso.sharepoint.com/:w:/r/sites/test/Shared%20Documents/Document1.docx?d=wb9ccccfd34d942ba8d0586671fd4e66b&csf=1&web=1

for the folder version, it is the same. If i use the above code, a link is shared
get-pnplistitem -List Documents | ? { $_["FSObjType"] -eq 1 } | % { Get-PnPFolderSharingLink -Folder $_["FileRef"]}
(nothing is returned even though folders are shared)
What is the version of the Cmdlet module you are running?
2.4.44     nightly    PnP.PowerShell
PSVersion                      7.4.2
Which operating system/environment are you running PnP PowerShell on?

[ x] Windows
[ ] Linux
[ ] MacOS
[ ] Azure Cloud Shell
[ ] Azure Functions
[ ] Other : please specify

Hmm , not sure.
Works for me :

Also, I am using the "new" Share dialog to share files and folders like this:

This cmdlet to retrieve information for the links generated via this dialog.
Does that clear things ? Maybe try it this way for a certain file and check ?

@AndersRask , the Get-PnPFileSharingLink and Get-PnPFolderSharingLink return info only when there is an actual link, the format is different, if you go to the "Manage Access" , there will be a links, otherwise it does not return anything if there are no links, although it might have created unique permissions for the file or folder. I started looking into it only 2 weeks ago and not sure whether behaviour changed over the past. I am pondering on the best way to report sharing information.

MS changed the way how files are shared, MC706173. Now when you invite a user to access the file. This gets direct permissions instead of creating a shared link.
Maybe that's your case?

Thanks @Barbarur : I don't use sharing that much except and was re exploring after a couple of years to understand functionality and clearly I missed the update MC706173. It makes more sense.

@AndersRask : I have updated my blog post https://reshmeeauckloo.com/posts/powershell-get-sharing-links-sharepoint/ to include a comparison using CSOM, the PnP cmdlets and REST endpoint. However CSOM only returns all sharing information unfortunately.

@reshmee011 it's even more weird actually. The new sharing is when you use click on "Share" and then "Invite". But if you use the "Copy link" function, the classic sharing link is still created.
So depending on how you share. User gets direct permissions or through the Shared Link.

@Barbarur , thanks for explaining the new sharing versus classic sharing. Wonder if it is a feature MS needs to work on to stop the sharing links being created.

MS changed the way how files are shared, MC706173. Now when you invite a user to access the file. This gets direct permissions instead of creating a shared link. Maybe that's your case?

Hi @Barbarur
you are exactly right!
It works fine when I explicitly use the link.
Microsoft managed to get people even more confused than before with that update :)
this ticket can be closed

I was getting access denied when trying to fetch sharing links for a customer.
Tracking down the code it led me to the List shared method in REST API. Here I noticed that application access is not supported!
https://learn.microsoft.com/en-us/graph/api/insights-list-shared?view=graph-rest-1.0&tabs=http

I made a feature request on their repo, but I think this would be a good thing to add to the documentation!
Issue:
https://github.com/microsoftgraph/msgraph-sdk-powershell/issues/2785


Update PFI Docs

Summary

[x] Update PFI to use new API
[x] Add instructions on how to use PFI with AutoML

Preview Links

File Type
File Name
Published Url

content
docs/machine-learning/how-to-guides/explain-machine-learning-model-permutation-feature-importance-ml-net.md
https://review.learn.microsoft.com/en-us/dotnet/machine-learning/how-to-guides/explain-machine-learning-model-permutation-feature-importance-ml-net?branch=pr-en-us-32900

content
docs/machine-learning/how-to-guides/how-to-use-the-automl-api.md
https://review.learn.microsoft.com/en-us/dotnet/machine-learning/how-to-guides/how-to-use-the-automl-api?branch=pr-en-us-32900

@IEvangelist this is ready for review when you get a chance. Thanks!


Add C# Client Docs

Add a basic developer start-up doc to the dot_net folder to get the process of documentaition started.

Closed by #985 and #1080


Error when adding item

Error Message: AADSTS90014: The request body must contain the following parameter: 'client_secret or client_assertion'.
I did follow the instructions and my app is set as native application.
Do you have any idea what can be?
thank you

we cannot repro this issue


editor: fix hover syntax reveal

fixes https://github.com/lockbook/lockbook/issues/2236 (by removing the debounce)
PR is in draft because I haven't totally decided if this is the right direction (alternative: https://github.com/lockbook/lockbook/pull/2683)
https://github.com/lockbook/lockbook/assets/6198756/35af929b-022b-4e1d-b35c-32cba776d3c5

https://github.com/lockbook/lockbook/pull/2686


error CS1061: 'HttpClient' does not contain a definition for 'PostAsJsonAync'

I tried this example : https://docs.microsoft.com/en-us/azure/app-service/tutorial-auth-aad?pivots=platform-linux
and failed on step "Modify the Front-End-Codes"
Next, find the method that's decorated with [HttpPost] and replace the code inside the curly braces with:

var response = await _client.PostAsJsonAsync($"{_remoteUrl}/api/Todo", todoItem);
var data = await response.Content.ReadAsStringAsync();
return Content(data, "application/json");`

after this build fail with this error. If have tried some stackoverflow answer, but it does't worked for me. One of them let it build it doesn't work.
Controllers/TodoController.cs(65,33): error CS1061: 'HttpClient' does not contain a definition for 'PostAsJsonAync' and no accessible extension method 'PostAsJsonAync' accepting a first argument of type 'HttpClient' could be found (are you missing a using directive or an assembly reference?)

Can someone help me to fix it?
I used the same configuration as in the example and cloned the repository  on 20th May 2021  14:00 CET.

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

ID: 28fe407c-980d-6dfc-305c-63202534bf48
Version Independent ID: 09bed06c-ca37-a511-b4a4-0028e76f8919
Content: Tutorial: Authenticate users E2E - Azure App Service
Content Source: articles/app-service/tutorial-auth-aad.md
Service: app-service
GitHub Login: @cephalin
Microsoft Alias: cephalin

@lampeTechnidoo, Thanks for the feedback! We are taking a look into this and will get back to you soon.

if there are importand dependecies get an oldersource version versio, where this problem is not actual could be a fast way to fix this problem.
If all what this sample should show works then this workaround is ok for me.

@lampeTechnidoo I was able to perform all the mentioned steps till the Modify front-end code section from the tutorial without any errors.
Please ensure you have the following:

A reference to the Microsoft.AspNet.WebApi.Client package in TodoApi.csproj file, and
using System.Net.Http; in the ToDoController.cs file

I have checked-in the working copy here: https://github.com/BhargaviAnnadevara-MSFT/dotnet-core-api.
Please try running it as is and let me know if you still see issues.

@lampeTechnidoo Hope the above inputs help. Do let us know if you have further questions here.
We will now proceed to close this thread, but if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.


增加刷卡支付基础功能

There were the following issues with your Pull Request

Commit: acf33a0438cd8c8d324b5e29af6134b5347d698d

Commits must be in the following format: %{type}(%{scope}): %{description}

Commit: 9aff877d993024cded0048a206bd0517fbb3f920

Commits must be in the following format: %{type}(%{scope}): %{description}

Commit: 27416d37381e00646cf91612d704592ebab1d08c

Commits must be in the following format: %{type}(%{scope}): %{description}

Commit: 4b7209e72db7478ebcdb7e6f6d6d91cfbea257c2

Commits must be in the following format: %{type}(%{scope}): %{description}

Commit: ab83459f477930be3a5fab36c19132033e46a911

Commits must be in the following format: %{type}(%{scope}): %{description}

Commit: 76ad80368e3f90704dfb8bcb646ddb577c5d4400

Commits must be in the following format: %{type}(%{scope}): %{description}

Commit: d7605e65217eaee61ce3294bfaefa7677d764f65

Commits must be in the following format: %{type}(%{scope}): %{description}

Guidelines are available at https://github.com/jxtech/wechatpy/blob/master/CONTRIBUTING.md

This message was auto-generated by https://gitcop.com

谢谢，稍后我会 review 您的代码。
发自我的 iPhone

在 2015年11月5日，10:02，林十四<EMAIL_ADDRESS>写道：
You can view, comment on, or merge this pull request online at:
https://github.com/jxtech/wechatpy/pull/97
Commit Summary
Create micropay.py
Delete micropay.py
Create micropay.py
Update init.py
Update init.py
Update micropay.py
Update init.py
File Changes
M wechatpy/pay/init.py (2)
M wechatpy/pay/api/init.py (1)
A wechatpy/pay/api/micropay.py     (65)
Patch Links:
https://github.com/jxtech/wechatpy/pull/97.patch
https://github.com/jxtech/wechatpy/pull/97.diff
—
Reply to this email directly or view it on GitHub.

There were the following issues with your Pull Request

Commit: acf33a0438cd8c8d324b5e29af6134b5347d698d

Commits must be in the following format: %{type}(%{scope}): %{description}

Commit: 9aff877d993024cded0048a206bd0517fbb3f920

Commits must be in the following format: %{type}(%{scope}): %{description}

Commit: 27416d37381e00646cf91612d704592ebab1d08c

Commits must be in the following format: %{type}(%{scope}): %{description}

Commit: 4b7209e72db7478ebcdb7e6f6d6d91cfbea257c2

Commits must be in the following format: %{type}(%{scope}): %{description}

Commit: ab83459f477930be3a5fab36c19132033e46a911

Commits must be in the following format: %{type}(%{scope}): %{description}

Commit: 76ad80368e3f90704dfb8bcb646ddb577c5d4400

Commits must be in the following format: %{type}(%{scope}): %{description}

Commit: d7605e65217eaee61ce3294bfaefa7677d764f65

Commits must be in the following format: %{type}(%{scope}): %{description}

Commit: 206f71cfcddf7cafd36349251b44ff527e3310b5

Commits must be in the following format: %{type}(%{scope}): %{description}

Guidelines are available at https://github.com/jxtech/wechatpy/blob/master/CONTRIBUTING.md

This message was auto-generated by https://gitcop.com

谢谢你的指正。

Thanks!


Could not start tunnel, max retries reached

Please confirm that you have:

[X] Searched existing issues to see if your issue is a duplicate. (If you’ve found a duplicate issue, feel free to add additional information in a comment on it.)
[X] Reproduced the issue in the latest CLI version.

In which of these areas are you experiencing a problem?
App
Expected behavior
Kindly help
Actual behavior
Could not start tunnel, max retries reached                                 │
│                                                                              │
│  To investigate the issue, examine this stack trace:                         │
│    at pollTunnelStatus (@shopify/app/src/cli/services/dev/urls.ts:106)       │
│      if (result.status === 'error') return reject(new                        │
│      BugError(result.message))                                               │
│    at (@shopify/app/src/cli/services/dev/urls.ts:120)                        │
│      pollTunnelStatus()                                                      │
│    at new Promise                                                            │
│    at pollTunnelURL (@shopify/app/src/cli/services/dev/urls.ts:101)          │
│      return new Promise((resolve, reject) => {                       │
│    at generateFrontendURL (@shopify/app/src/cli/services/dev/urls.ts:89)     │
│      const url = await pollTunnelURL(options.tunnelClient)                   │
│    at dev (@shopify/app/src/cli/services/dev.ts:123)                         │
│      generateFrontendURL({                                                   │
│    at run (@shopify/app/src/cli/commands/app/dev.ts:106)                     │
│      await dev({                                                             │
│
Verbose output
-

Reproduction steps
1.npm run dev
2.
3.
Operating System
MacOS Ventura
Shopify CLI version (check your project's package.json if you're not sure)
3.0
Shell
No response
Node version (run node -v if you're not sure)
v20
What language and version are you using in your application?
node

i have the same your bug, when i user npm run dev then have an error, I user shopify/cli": "^3.46.0 and nodejs v16.16.0 :((

I found the solution today. I used cloudfare. Follow below steps:
Step 1: Run "cloudflared tunnel --url http://localhost:3000".
Step 2: One URL will be generated in the CMD for example "https://example.trycloudflare.com". Copy that and use it in Step 3.
Step 3: sudo npm run dev -- --tunnel-url https://example.trycloudflare.com:3000.
Hope it helps. Cheers :)

i try your solution to config cloudflared tunnel url, but i still have error, so what should i do?

Any more movement here? I'm running into this issue too on a fresh shopify app template install.

reopened https://github.com/Shopify/cli/issues/2170


Update of Tuya Wireless Scene Switch TS0041

My Tuya switches have an additional manufacturer string. With the new string the switch gets recognized and works

Codecov Report

Merging #879 (3b3f180) into dev (833c1b9) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev     #879   +/-   ##
=======================================
  Coverage   82.50%   82.50%
=======================================
  Files         185      185
  Lines        4589     4589
=======================================
  Hits         3786     3786
  Misses        803      803

Impacted Files
Coverage Δ

zhaquirks/tuya/ts0041.py
100.00% <ø> (ø)

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 833c1b9...3b3f180. Read the comment docs.

Pull Request Test Coverage Report for Build 817494444

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

Totals

Change from base Build 788931381:
0.0%

Covered Lines:
3786

Relevant Lines:
4589

💛  - Coveralls


chore: use CA certificates chart 0.0.3

Update the helm chart used to insert self-signed CA certificates to the latest version. This latest version can run as non-root.
/deploy #persist

You can access the deployment of this PR at https://renku-ci-nb-1132.dev.renku.ch


Update participant guide

update https://ioos.github.io/ioos-code-sprint/resources/participant-guide/
I would like to have it include:

information about how to propose a topic (probably just copy this)
how to contribute/sign-up to a topic beforehand (ideally by commenting in the GitHub issue)
clean up language about zoom and virtual only.

Include information about Topic Lead collaboration software:
For Topic Leads:
Topic leads will have the flexibility to use the collaboration software of their choosing. Leads need to communicate to potential contributors on how they intend to facilitate collaboration. The default services we will be providing during the Code Sprint include:

Slack
Google Hangouts

https://github.com/ioos/ioos-code-sprint/commit/df1119f5ddfaa0ff97894cefc5801aae9038468b


Parents page v2

Removes some old Vue routes that are for ozaria only
Adds new parents-v2 route for new parent page design
Adds a basic parents page with CTA hooks in place
Adds a BackboneModalHarness Vue component to allow us to use Backbone modals in Vue

@AndrewJakubowicz thanks!  no risk right now it's on its own isolated URL


Query designer bug with variable names for joins on intermediate class

I built the following query on the IMDB dataset in the demo query designer:

When inspecting the generated SPARQL you can see the variable name for the intermediate Performance class is named ?Actor_performance when referred to from the ?Actor and ?Film_performance from the ?Film.
As a result the query does not join the actor and film around the shared performance node and instead returns all actors matched to every film that has a performance.
PREFIX prf1: <http://data.linkedmdb.org/resource/movie/>
PREFIX dcterms: <http://purl.org/dc/terms/>

SELECT DISTINCT ?Actor_actor_name ?Film_title
WHERE {
	?Actor a prf1:actor.
		?Actor prf1:actor_name ?Actor_actor_name.
		?Actor prf1:performance ?Actor_performance.
	?Film_performance a prf1:performance.
	?Film a prf1:film.
		?Film prf1:performance ?Film_performance.
		?Film dcterms:title ?Film_title.
}

The issue seems to be with two inbound links to a certain entity class.

Hello jaw111,
Could you save the query in the designer and send me a link in order to investigate the issue?
Best,
Dimitris Papaspyros

Here it is:
http://linda.epu.ntua.gr/query-designer/171/

Dear jaw111,
Thank you very much for finding this bug out. Your input is appreciated!
We're very sorry for the delayed response on this issue. Please verify that the correct query is now constructed.
Looking forward to hearing from you if you have any further questions or need any help about LinDA.
Best,
Dimitris Papaspyros
Decision Support Systems Laboratory, NTUA, Greece

Yes, that has solved the issue, thanks!


⚠ Bofrost.si has degraded performance

In 234b8dc, Bofrost.si (https://www.bofrost.si) experienced degraded performance:

HTTP code: 200
Response time: 3106 ms

Resolved: Bofrost.si performance has improved in e7e67f3 after 9 minutes.


Handle strange Windows usernames

To cope with strange characters in Windows usernames,
in /iis/wix/list_dependencies.bat
line 25 should be quoted:
SET log_file="%TEMP%"\ModSecurityIIS-depedencies-%log_file:~-5%.TXT

Sadly they have washed their hands from windows


feat: Fourier integral of Gaussians on inner product spaces

Also rename (and deprecate) a few statements by changing fourierTransform to fourierIntegral: the Fourier transform for general L^2 functions is not given by the Fourier integral, so we should separate cleanly the two of them.

I'm not sure I entirely get the argument about renaming – the Fourier transform is given by the integral for L^1 functions, and Gaussians are about the most L^1 function you can imagine! But if you really want to rename the lemmas then go ahead, I'm not fanatically attached to the old names.
As for the inner-product space results: would it be significantly harder to treat the more general case of "ellipsoidal" rather than "spherical" Gaussians, i.e. exp(-∑ i, b i * (v i : ℂ) ^ 2 + ...) for some b : ι → ℂ, and then derive the case of constant b as a consequence? It seems to me that the proof you use would extend immediately to this case as well.

About the naming, I expect that in the not so distant future we will define the Fourier transform of a general function f : E -> ℂ, maybe as follows: if f is integrable against any Schwartz function and there exists a measurable g such that ∫ f ⬝ 𝓕 φ = ∫ g • φ for all Schwartz function, then use this g (or, better, if there is such a g which is continuous, then use the continuous version, and otherwise use the measurable one). This is what I would like to call the Fourier transform (in particular, it would work fine on L^2), and anticipating on this one I would like to use fourierTransform for lemmas about this one, and fourierIntegral for lemmas about the Fourier integral. I agree it's not essential, but planning a little bit ahead can help having a nice library.
Let me try to do the ellipsoidal Gaussian.

Ellipsoidal case done.

Looks great! We should probably change the section title
/-! ## Fourier transform of the Gaussian integral
-/

to something like "Fourier integral of the Gaussian function" for consistency with the lemma renamings (the original title is clearly a mistake anyway). Other than that I have nothing further to add.

Good remark. I've changed the section title accordingly, to Fourier integral of Gaussian functions.


[AIFlow][chart] Add AIFlow webserver deployment to helm chart

What is the purpose of the change
Add AIFlow webserver deployment to helm chart
Brief change log
Add AIFlow webserver deployment to helm chart
Verifying this change
Manually test

LGTM.


Create Compliance Report and Intro

#1156 #1157 #1158
Added the compliance report list page and create button
Changelog:

Compliance Report list page
Added button for creating Compliance Reports
Added Compliance Report Intro page
Removed a configuration from front-end (can just calculate it)

 Compliance Report | Create new Compliance Report |3|

 Compliance Report | Introduction Page |2|

 Compliance Report | View Compliance Reporting Materials |5|


Support for AWS BedRock

I would like to know how to add AWS Bedrock support to Semantic kernel

Hi @VenkateshSrini !
We have an example how to add your own implementation of AI Connector here:
https://github.com/microsoft/semantic-kernel/blob/main/dotnet/samples/KernelSyntaxExamples/Example16_CustomLLM.cs
We also have a couple of implemented AI Connectors, which you can use as a reference:
https://github.com/microsoft/semantic-kernel/tree/main/dotnet/src/Connectors/Connectors.AI.HuggingFace
https://github.com/microsoft/semantic-kernel/tree/main/dotnet/src/Connectors/Connectors.AI.Oobabooga
https://github.com/microsoft/semantic-kernel/tree/main/dotnet/src/Connectors/Connectors.AI.OpenAI
One note: at the moment we are not adding new Connectors to this repository. We encourage to create separate repositories for SK Connectors and share it with us - so we will be able to add it to our README file as a reference.
Please let me know if you have any other questions. Thanks a lot!

Can you give me some links on step by step process to create connectors please @dmytrostruk ?

@VenkateshSrini I'm not sure if we have a step-by-step guideline how to create Connectors. I would be happy to provide answers if you have some specific questions.
If you are interested in implementing C# Connector, then you will have to create your C# class and implement ITextCompletion interface, which is mandatory to be able to inject your connector in Kernel. In case AI provider supports Chat API, then your class can also implement IChatCompletion interface.
C# implementation example:
https://github.com/microsoft/semantic-kernel/blob/main/dotnet/src/Connectors/Connectors.AI.OpenAI/ChatCompletion/AzureChatCompletion.cs
If you want to implement AI Connector in SK Python version, you will need to create Python class, which inherits from ChatCompletionClientBase, TextCompletionClientBase base classes.
Python implementation example:
https://github.com/microsoft/semantic-kernel/blob/main/python/semantic_kernel/connectors/ai/open_ai/services/open_ai_chat_completion.py
As mentioned in previous comment, we encourage to create new Connectors in your own repositories and share link with us - so we will be able to share your link in our README file as useful reference.
Please let me know if this information is helpful. Thank you!

Thank you

@dmytrostruk, did I understand correctly that there exists a README file listing connectors from 3rd party repositories? I didn't find it, but maybe I didn't search long enough 😅


Unable to close a requested stream before it opens.

Description
When using Streamlink you're unable to kill a stream that's currently being opened with the close stream button in the pop-up dialogue box.
Expected / Actual behavior
Pressing the close stream button closes the dialogue box and ends the connection, preventing the stream from being opened.
...
Pressing the close stream button closes the dialogue box but does not prevent the stream from being opened.
Reproduction steps

Select Streamlink.exe as the livestreamer executable.
Attempt to open any stream.
X out of the dialogue box before the requested stream has been opened.

Environment details (operating system, etc.)
Windows 7 x64
Livestreamer GUI 0.16.0

This is a bug related to Streamlink (or Livestreamer when installed via pip)
See https://github.com/bastimeyer/livestreamer-twitch-gui/issues/331#issuecomment-255597522 and the following comments.

Fixed in the streamproviders branch that splits the old livestreamer structure into streamlink, livestreamer and livestreamer-standalone (Windows installer).
Streamlink and Livestreamer will now be launched directly via the python executable (pythonw.exe on Windows) instead of relying on the shebang inside the python scripts which were used previously. This removes the cmd window on Windows while using Streamlink or Livestreamer when installed via pip.
I'm going to close this issue once the branch has been merged into master.

Are there going to be a new release any time soon?

I don't have planned anything yet. I want the next release to be the last one with the current name. There's still some work to do, so that the transition can be smooth.
If the cmd window issue with Streamlink on Windows annoys you, just switch back to Livestreamer (which is still working fine thanks to the workarounds in the GUI) or build the application off the master branch and help testing it, so I can be sure that I haven't missed a bug. 😃

I have tried to build it, but I always get the same error:

Running "webpack:dev" (webpack) task                         events.js:160
throw er; // Unhandled 'error' event
^

Error: This socket is closed
at WriteStream.Socket._writeGeneric (net.js:683:19)
at WriteStream.Socket._write (net.js:734:8)
at doWrite (_stream_writable.js:334:12)
at writeOrBuffer (_stream_writable.js:320:5)
at WriteStream.Writable.write (_stream_writable.js:247:11)
at WriteStream.Socket.write (net.js:661:40)
at Log._write (C:\Users\XYZ\livestreamer-twitch-gui\node_modules\grunt-legacy-log\index.js:161:26)
at Log.wrapper [as _write] (C:\Users\XYZ\livestreamer-twitch-gui\node_modules\grunt-legacy-log\node_modules\lodash\index.js:3095:19)
at Log._writeln (C:\Users\XYZ\livestreamer-twitch-gui\node_modules\grunt-legacy-log\index.js:166:8)
at Log.wrapper [as _writeln] (C:\Users\XYZ\livestreamer-twitch-gui\node_modules\grunt-legacy-log\node_modules\lodash\index.js:3095:19)
at Log.writeln (C:\Users\XYZ\livestreamer-twitch-gui\node_modules\grunt-legacy-log\index.js:177:8)
at Log.wrapper (C:\Users\XYZ\livestreamer-twitch-gui\node_modules\grunt-legacy-log\node_modules\lodash\index.js:3095:19)
at writeln (C:\Users\XYZ\livestreamer-twitch-gui\node_modules\grunt\lib\grunt\fail.js:30:13)
at Object.fail.fatal (C:\Users\XYZ\livestreamer-twitch-gui\node_modules\grunt\lib\grunt\fail.js:46:3)
at process.uncaughtHandler (C:\Users\XYZ\livestreamer-twitch-gui\node_modules\grunt\lib\grunt.js:121:10)
at emitOne (events.js:96:13)
at process.emit (events.js:188:7)
at process._fatalException (bootstrap_node.js:292:26)

I don't know what you're doing, but please follow the contributing guide and use the latest stable versions of git, nodejs, npm and bower and make sure that all dependencies are installed correctly.

https://github.com/streamlink/streamlink-twitch-gui/releases/latest


Stream aliases

Which version are you using?
v0.9.10
Describe the problem
It might be useful to provide alternative paths for the same stream, without creating a new entry in the config (depending on the implementation this may save some memory/cpu too).

Hello, there is a pending PR that implements wildcard paths; i'm waiting for the author to do some changes, otherwise after a while i'll implement the feature myself.

Paths with regular expressions have been implemented into master; this does not allow stream aliases but allows to share a configuration between two paths.

Good enough! The main concern was to not duplicate the processing on the backend so regexps work.

added in v0.10.0


Feature Request: F.as_strided

For #5036, backward-compatible as_strided is necessary.
I'm going on implementation of that, and I'll be able to make a PR for it in a few days.

Thanks!


Current directory not correctly set when debugging

I see an odd behavior when debugging bazel targets from CLion. The current working directory is set to the project root directory. This is different from when bazel run is used directly, where the current directory is in the runfiles tree. This is causing problems finding resources in the runfiles tree using relative paths.
For example
bazel run  OR run it directly from CLion:
CWD is /home/dag/.cache/bazel/_bazel_dag/4254edf45eea7a9dd5daebbc8928ade6/execroot/werkstatt/bazel-out/k8-dbg/bin/platform/fashion/tests/unit/test.runfiles/testproj/
But when running debug from CLion:
CWD is /home/dag/Dev/testproj
The expected behavior that the launched process would have the same working directory in both cases, in the runfiles tree.
CLion version: 173.4674.29
CLion Bazel Plugin version: 2<IP_ADDRESS>.4

To put it in a different way, the correct way would be to invoke the debuggee with the same current directory and arguments as can be seen in run.sh in this example:
bazel run -c dbg --script_path=run.sh //some_target

I'm seeing this same undesired behavior in PyCharm. Any suggested workarounds?


Improve compliance with repolinter

Fix link in SECURITY.md and add missing license and copyright notices.
To check, run repolinter --rulesetUrl https://github.com/hyperledger-labs/hyperledger-community-management-tools/raw/main/repo_structure/repolint.json
Signed-off-by: Arnaud J Le Hors<EMAIL_ADDRESS>

Sorry @lehors this has been sitting here for too long, spotted the issues - and it's with the comments in the cli.js file - it's a executable, so the comments needs to come after the shebang


[BEAM-4028] Address cleanup TODOs

I happened to notice these TODOs while reviewing Python worker code and decided to go ahead and clean them up.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @pabloem

LGTM!

feel free to merge : )

It looks like this breaks Python precommit, probably we need to build a new Dataflow worker with the internal change


KDE 5 applications are slow

The KDE 5 tests on Hydra regularly time-out due to KDE 5 applications being so slow. This is mainly due to searching so many paths in XDG_DATA_DIRS, as @edolstra pointed out here. I thought it would be more appropriate to open a ticket for this issue because it has come up in different contexts. Let me review the problem itself and possible solutions.
Cause
This problem affects all KDE 5 applications, but the application in particular which triggered this issue was Dolphin, so I will address it specifically. Dolphin is slow because loading icons requires searching every directory in XDG_DATA_DIRS for icons. Dolphin renders many icons, so this issue hits harder than other applications. kdeWrapper adds many paths to this list so that Dolphin and all the libraries it depends on may find their runtime dependencies. The wrapper allows the dependencies to be resolved whether the application is installed in the user or the system profile and it allows the application to run cleanly from the Nix store. It is also necessary to allow installation of applications depending on different versions of KDE Frameworks or even Qt.
Solution (-1): symlink farming
Until recently, kdeWrapper worked by creating a symlink farm for all the runtime dependencies and adding that path to XDG_DATA_DIRS. This is theoretically nice: a filesystem is a tree, so this basically amounts to creating a lookup tree for all the runtime dependencies. The problem is, every symlink takes up one filesystem block; at 4 KB each, that adds up. As @edolstra pointed out in #20433, this can add up to ~50 MB per application and up to ~400 MB for a typical KDE 5 installation. This is obviously unacceptable!
Solution 0: KDE unwrapped
If we remove the wrappers and resort to propagatedUserEnvPkgs, we gain the speed of symlink farming without the overhead. However, it will no longer be possible to run KDE 5 applications from the Nix store. As @abbradar pointed out, this will resurrect the long-standing problem of Qt applications "poisoning" the system against applications using other Qt versions. As a result, it will probably be impossible to install KDE 5 applications using nix-env. It will also break KDE 5 applications running outside of KDE, except by an obscure workaround.
Solution 1: dynamic symlink farming
The problem with symlink farming is the filesystem block occupied by each symlink. Placing the symlinks on a block-less filesystem like tmpfs removes this overhead! This would require creating the symlink farm dynamically. That is non-negligible overhead, but in principle it only needs to be done once per store path per boot, so it may be an acceptable compromise. Unfortunately, it would be a security nightmare: it would essentially be possible for a non-privileged user to modify the XDG_DATA_DIRS of any running application at any time!
Since the only remotely-acceptable solution on this list is "just let KDE be slow," I'm open to any suggestions!

Just my humble opinion (again, I'm not even using KDE!) but although all those options seem bad, I'd go with -1 instead of status quo -- disk space is much cheaper than our time that we spend waiting applications to load. 400 MB is bad but not as bad, and (as I've already mentioned in another comment) times would be much, much worse for people with spinning drives.

times would be much, much worse for people with spinning drives.

I have spinning drives; it's not noticeable because of the filesystem cache, but on the virtual machine, the extra cache pressure causes a cascading failure.
Ironically, the huge size increase doesn't affect the graphical installer because squashfs is block-less! Now, if only there was a way to get a bunch of squashfs images mounted into the Nix store...

@ttuegel Hm, sounds good but relying on cache still seems flaky to me. How long are cold boot times?
On the other hand my worries may be entirely ungrounded indeed -- let's bring in some data! I'll try to measure time of cold-booting Dolphin on my host and in a VM (with SSD). I don't have KDE so it would be a more or less good measure. Test plan: use xdotool to wait for window and close it, measure overall process time.

@abbradar Before you run any tests, let me check something about the symlink farm overhead. I think I can reduce it significantly because I was doing something wrong before.

@ttuegel It's too late, I was interested in how to measure this ~_^.
Here's my script:
#!/bin/sh

for i in `seq 1 10`; do
  echo 3 | sudo tee /proc/sys/vm/drop_caches >/dev/null
  time -f 'ELAPSED: %e' result/bin/dolphin >/dev/null &
  while true; do
    win=$(xdotool getactivewindow)
    if xdotool getwindowname $win | grep -q Dolphin; then
      break
    fi
    sleep 0.05
  done
  killall -9 dolphin
done

Results for my machine:
ELAPSED: 1.91
ELAPSED: 1.77
ELAPSED: 1.79
ELAPSED: 1.87
ELAPSED: 1.78
ELAPSED: 1.78
ELAPSED: 1.87
ELAPSED: 1.87
ELAPSED: 1.87
ELAPSED: 1.88

This is big but manageable if this is a cold boot. I'll postpone measurements in a VM until your experiment with symlink farm. Notice that this is still a very crude measurement (sleep 0.1 is used to wait).

I have a patch for smaller symlink farms now; ~10MB instead of ~50MB. I get these timings before:
ELAPSED: 6.46
ELAPSED: 6.75
ELAPSED: 5.95
ELAPSED: 6.27
ELAPSED: 6.58
ELAPSED: 6.52
ELAPSED: 6.49
ELAPSED: 6.27
ELAPSED: 6.45
ELAPSED: 6.47

and these timings after
ELAPSED: 4.08
ELAPSED: 4.63
ELAPSED: 4.45
ELAPSED: 4.64
ELAPSED: 4.87
ELAPSED: 4.60
ELAPSED: 4.35
ELAPSED: 4.86
ELAPSED: 4.63
ELAPSED: 4.67

That is a significant speed improvement!
@edolstra Is a ~10MB per-application overhead acceptable for a ~30% improvement in startup time?

kdeWrapper is now used for each application. Would it make sense to instead say one would like to have an environment with certain KDE applications, and then symlink everything that is needed for that environment (kde5.withPackages). If you will have only one application in an env, the size increase will remain the same. If you have multiple applications in an env, I would expect a smaller size increase because libraries are symlinked only once.

How about considering an env with KDE5 applications, and symlink everything that is needed for that environment (kde5.withPackages). If you will have only one application in an env, the size increase will remain the same. If you have multiple applications in an env, I would expect a smaller size increase because libraries are symlinked only once.

@FRidh This is possible. It is essentially what we do already for the Plasma desktop. Plasma consists of a collection of applications; rather than wrapping them individually, we wrap them into a single desktop. We can make this wrapper more expansive, but that will break application installation by nix-env.

What about a hybrid approach? Make individually wrapped applications visible and installable in nix-env but also add kde5.withPackages :: (PackageSet -> [Package]) -> Package and promote it to be used in NixOS configurations?

Maybe do it like this:

kde5.foobar -- application foobar which is defined as: foobar = wrapPackage (callPackage ./foobar.nix { });;
wrapPackage adds passthrough attribute unwrapped;
withPackages takes a list of wrapped packages and re-wraps their unwrapped versions in a one big environment.

This way everybody can use kde5.foobar and those that want more optimized approach can throw it with other packages into withPackages and it will do the right thing.

withPackages takes a list of wrapped packages and re-wraps their unwrapped versions in a one big environment.

How should withPackages know which targets to wrap?

@ttuegel I'm sorry but I'm not sure what do you mean by targets -- maybe outputs? If yes then IIUC for applications we want bin or out, similarly to what we already do in environment.systemPackages.

I'm sorry but I'm not sure what do you mean by targets -- maybe outputs?

kdeWrapper doesn't wrap every executable in the bin output, but only specific ones. Some packages have utilities programs that aren't intended to be user-accessible; it doesn't make sense to wrap these. I don't see how to make withPackages aware of application-specific logic like this.
kdeWrapper also does application-specific cycle breaking. For example, dolphin-plugins provides plugins for the Dolphin file manager. Building the plugins requires headers and libraries provided by the Dolphin build. The unwrapped Dolphin build cannot depend on the plugins, but the Dolphin wrapper needs to include the plugins! We can do this because the Dolphin expression has application-specific wrapper logic. If we defer making the wrapper to withPackages, I don't know how to communicate that logic.

Ah, I see. What about just exposing targets and paths as passthru arguments? Then we have wrapPackages packages = kdeWrapper { targets = concatMap (p: p.targets) packages; paths = concatMap (p: p.paths) packages); }, and all the custom logic should apply (it's already collected in kdeWrapper and activated by having specific targets/paths, correct?).

Hm, and even better: we can get rid of wrapPackages completely! In pseudo-code:
kdeWrapPackages pkgs =
  let targets = concatMap (p: p.targets) pkgs;
      paths = concatMap (p: p.paths) pkgs;
  in stdenv.mkDerivation {
    ...
    passthru = { inherit targets paths; };
  };

This way you can re-wrap packages endlessly:
kdeWrapper [(kdeWrapper [a]) (kdeWrapper [b])] = kdeWrapper [a b]

This way you can re-wrap packages endlessly:

Not quite; each additional wrapper adds another level of symlink indirection! But your point is well taken: because Nix is not typed, we can essentially overload kdeWrapper :: [Package] -> Package with kdeWrapper :: Package -> Package.

@abbradar That's exactly my though, pass through the unwrapped derivation as well as the arguments for the wrapper.

Not quite; each additional wrapper adds another level of symlink indirection!

Why? If I understand correctly what @abbradar wrote and how I see it as well, is that only for the eventual environment (and that consist of multiple packages or a single) you create the symbolic links.
In kdeWrapper [(kdeWrapper [a]) (kdeWrapper [b])] = kdeWrapper [a b] the only derivations built would be the unwrapped, and the eventual env with symbolic links/wrappers, right?

I think there is misunderstanding of my idea, or I don't fully get how kdeWrapper works now. Sorry and please bear with me!
Let's define a KDE package (in some pseudo-typed Nix):
type KDEPackage = { targets :: [String], paths :: [Package] }

That is, a package (for the purposes of kdeWrapper) is two sets: of paths (that is, Nix packages) that we need to link and of targets (that is, names of binaries inside those paths).
To get a wrapped Nix package, we'd define a function:
kdeWrapper :: KDEPackage -> Package

What I say is that we can define an operation of combining two KDEPackages:
mappend :: KDEPackage -> KDEPackage -> KDEPackage
mappend a b = { targets = a.targets ++ b.targets; paths = a.paths ++ b.paths; }

Notice that there's no symlinks involved -- we have just made a "package" consisting of merged sets of two packages.
Now, we'd like to allow Package result of kdeWrapper to be used as KDEPackage -- we can do that by means of passthru, exposing targets and paths. At this point we can merge Package using the same mappend, getting new KDEPackages -- again, no symlinks, we merge initial sets of paths!
Finally let's combine mappend and kdeWrapper for convenience:
kdeWrapper :: [KDEPackage] -> Package
kdeWrapper pkgs =
  let targets = concatMap (p: p.targets) pkgs;
      paths = concatMap (p: p.paths) pkgs;
  in stdenv.mkDerivation {
    ...
    passthru = { inherit targets paths; };
  };

Notice that you can pass both manually-constructed KDEPackages (like one defined in dolphin.nix) and results of previous kdeWrappers (because of passthru) in that list -- all the targets and paths will be combined, and no symlinks are involved!

Notice that you can pass both manually-constructed KDEPackages (like one defined in dolphin.nix) and results of previous kdeWrappers (because of passthru) in that list -- all the targets and paths will be combined, and no symlinks are involved!

I appreciate the time it took to write out this Haskell pseudo-code, but your example won't typecheck: the result of kdeWrapper is a Package not a KDEPackage. KDEPackage is not a Nix derivation, but merely an attribute set; it's not something you can install and it's not something you can put in the paths list. Now, you can create a Package from a KDEPackage, but that creates an extra build in the Nix store whose only purpose is to serve as an indirection.
It's still a good idea to allow kdeWrapper to take a list of packages! It's just not a semigroup because it's not associative.

Hm, I still feel that there is some misunderstanding. My idea is to allow Package (Nix derivation) to pose as KDEPackage (attribute set with targets and paths) via passthru. Let's name something else, InstallableKDEPackage -- a Package that also contains targets and paths attributes taken directly from converted KDEPackage. Now, we have a way to "lift" KDEPackage (a mere attribute set) to InstallableKDEPackage (Nix derivation with passed through targets and paths from the original KDEPackage):
lift :: KDEPackage -> InstallableKDEPackage
lift attrs = stdenv.mkDerivation {
  ...
  passthru = attrs;
}

AKA kdeWrapper. Notice again that this resulting InstallableKDEPackage would have the same targets and paths copied from original KDEPackage!
Now we have a semigroup:
mappend :: InstallableKDEPackage -> InstallableKDEPackage -> InstallableKDEPackage
mappend pkg1 pkg2 = lift { paths = pkg1.paths ++ pkg2.paths; targets = pkg1.targets + pkg2.targets; }

I should have introduced InstallableKDEPackage in the first post but I was afraid it'd complicate the whole idea. Now I see that I shouldn't leave the types out when describing ~_^.
Now, Nix is not really static-typed so we can combine lift with mconcat and get the resulting kdeWrapper example of which I've posted above.

I've implemented this idea in https://github.com/abbradar/nixpkgs/commit/dc17b9b4b01f8be2fa7ac62b675be4e4ddab1e29. This is not ideal (/share contains everything from paths, not just from unwrapped) but close to what I envisioned. You can compare:
nix-build -A kde5.okular
and
nix-build -E 'with import <nixpkgs> {}; kde5.kdeWrapper (with kde5; [ okular konsole ])'
Notice that in second case there won't be an extra symlink layer.

@abbradar nice!
I guess the next step is to apply this to the packages that are put in environment.systemPackages at https://github.com/NixOS/nixpkgs/blob/master/nixos/modules/services/x11/desktop-managers/kde5.nix
. I think it would be good to have an kde5.extraPackages option that adds those to the env before adding the env to environment.systemPackages.

@ttuegel Your thoughts on this? If this seems a good idea overall I can make a PR.

@abbradar It sounds good to me. Please do that!

Can we close this now?

Yes, everything should be fine now. Thanks!

Starting okular 5 is still slow and stats a zillion files. 2-4 seconds with SSD disk.
Running strace and grepping for "stat(.*icon" i get 433078 stat calls. (XDG_DATA_DIRS have 9 entries)
https://woboq.com/blog/qicon-reads-gtk-icon-cache-in-qt57.html mentions something about an optimization for icon lookup using the gtk icon cache

How do I make sure the cache is used?
Every time you install an application that adds or removes icons from one of the themes, the cache needs to be updated. Qt looks at the modification time of the directories, if any directory is newer than the cache, the cache will not be used. You need to run gtk-update-icon-cache after installing new icons, but most distributions take care of this for you.

I am still seeing quite long start-up time due to icon searching on NixOS 20.09:
$ nix run nixpkgs.kdeApplications.kate -c strace --summary --timestamps=unix,ms -o log kate
$ tail log
...
% time     seconds  usecs/call     calls    errors syscall
------ ----------- ----------- --------- --------- -------------------
 84.58    1.125760           4    251142    250137 access
  4.81    0.063955           4     14939     10959 statx
  2.17    0.028833           4      6838       747 stat
  2.00    0.026677           5      4526      2667 openat
  1.59    0.021119           3      5753         8 lstat
  1.52    0.020274          10      1879           close
  0.65    0.008661           7      1107       212 futex
...

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/benchmarking-why-nixos-higher-average-cpu-usage/13248/1

I'm also seeing this with multiple machines on 22.05pre365448.1063244793d.
kate:
% time     seconds  usecs/call     calls    errors syscall
------ ----------- ----------- --------- --------- -------------------
 68.96    0.524305           2    212286    198879 statx
  9.22    0.070089           2     32874     30061 readlink
  6.62    0.050304           3     16336      1420 newfstatat
  4.01    0.030460           3      9786      4088 access
  2.47    0.018805           2      7003      4120 openat
  2.34    0.017766           5      3094         2 read
  1.92    0.014630        4876         3           wait4
  0.91    0.006915           5      1350       289 futex
  0.80    0.006065           2      2919           close

konsole:
% time     seconds  usecs/call     calls    errors syscall
------ ----------- ----------- --------- --------- -------------------
 36.86    0.032791           2     13091     12020 statx
 12.89    0.011472           2      4084      3359 openat
  9.37    0.008339        8339         1           wait4
  4.91    0.004372           3      1457      1163 access
  4.78    0.004254           1      2217      1372 newfstatat
  4.62    0.004108           9       449       128 futex
  4.51    0.004013           2      1891      1674 readlink
  4.12    0.003670           3      1034           mmap
  2.77    0.002465           1      1650           getpid

I suspect this is related to XDG_DATA_DIRS which is 6398 characters long. With konsole, clearing it reduces the amount of statx calls to 5656 (and starts faster). The konsole wrapper itself adds another 3345 characters, bringing the total to 9743.
This is almost certainly related to https://github.com/NixOS/nixpkgs/issues/126590


MB-2757 Add expected payload to webhook client and support endpoint

Description

Updates support endpoint /webhook-notify to accept the expected payload.
Updates post-webhook-notify command in the webhook client to work with the expected payload
User can now pass post-webhook-notify a json file and the support endpoint will log the payload/response to the console.

Reviewer Notes
In order to run the unit test, it needs a test data file. I've added one (temporarily?) -- let me know if there's a better way to handle testing or if this okay.
To run the tests:
$ go test ./cmd/webhook-client/ -v

Example test payload:
{
  "id": "290f86e7-fbef-4441-bd0c-ea6cdffc469e",
  "eventName": "paymentRequest.Created",
  "triggeredAt": "1995-09-07T10:40:52Z",
  "objectType": "paymentRequest",
  "object": "{\r\n\u00A0\"id\": \"c56a4180-65aa-42ec-a945-5fd21dec0538\",\r\n\u00A0\"isFinal\": false,\r\n\u00A0\"moveTaskOrderID\": \"c56a4180-65aa-42ec-a945-5fd21dec0538\",\r\n\u00A0\"rejectionReason\": \"documentation was incomplete\",\r\n\u00A0\"status\": \"PENDING\",\r\n\u00A0\"paymentRequestNumber\": \"1234-5678-1\",\r\n\u00A0\"proofOfServiceDocs\": {},\r\n\u00A0\"paymentServiceItems\": [\r\n\u00A0\u00A0\u00A0{\r\n\u00A0\u00A0\u00A0\u00A0\u00A0\"id\": \"c56a4180-65aa-42ec-a945-5fd21dec0538\",\r\n\u00A0\u00A0\u00A0\u00A0\u00A0\"paymentRequestID\": \"c56a4180-65aa-42ec-a945-5fd21dec0538\",\r\n\u00A0\u00A0\u00A0\u00A0\u00A0\"mtoServiceItemID\": \"c56a4180-65aa-42ec-a945-5fd21dec0538\",\r\n\u00A0\u00A0\u00A0\u00A0\u00A0\"status\": \"REQUESTED\",\r\n\u00A0\u00A0\u00A0\u00A0\u00A0\"priceCents\": 0,\r\n\u00A0\u00A0\u00A0\u00A0\u00A0\"rejectionReason\": \"documentation was incomplete\",\r\n\u00A0\u00A0\u00A0\u00A0\u00A0\"paymentServiceItemParams\": [\r\n\u00A0\u00A0\u00A0\u00A0\u00A0\u00A0\u00A0{\r\n\u00A0\u00A0\u00A0\u00A0\u00A0\u00A0\u00A0\u00A0\u00A0\"id\": \"c56a4180-65aa-42ec-a945-5fd21dec0538\",\r\n\u00A0\u00A0\u00A0\u00A0\u00A0\u00A0\u00A0\u00A0\u00A0\"paymentServiceItemID\": \"c56a4180-65aa-42ec-a945-5fd21dec0538\",\r\n\u00A0\u00A0\u00A0\u00A0\u00A0\u00A0\u00A0\u00A0\u00A0\"key\": \"CanStandAlone\",\r\n\u00A0\u00A0\u00A0\u00A0\u00A0\u00A0\u00A0\u00A0\u00A0\"value\": 3025,\r\n\u00A0\u00A0\u00A0\u00A0\u00A0\u00A0\u00A0\u00A0\u00A0\"type\": \"STRING\",\r\n\u00A0\u00A0\u00A0\u00A0\u00A0\u00A0\u00A0\u00A0\u00A0\"origin\": \"PRIME\",\r\n\u00A0\u00A0\u00A0\u00A0\u00A0\u00A0\u00A0\u00A0\u00A0\"eTag\": \"string\"\r\n\u00A0\u00A0\u00A0\u00A0\u00A0\u00A0\u00A0}\r\n\u00A0\u00A0\u00A0\u00A0\u00A0],\r\n\u00A0\u00A0\u00A0\u00A0\u00A0\"eTag\": \"string\"\r\n\u00A0\u00A0\u00A0}\r\n\u00A0],\r\n\u00A0\"eTag\": \"string\"\r\n}"
}

You'll notice that the object field is an encoded JSON string. If testing other sample objects, make sure to encode them as a string first.
Setup

Create a test file with a sample payload as shown above.
Use the commands below to make a request

// Build the client
$ rm -rf bin/webhook-client && make bin/webhook-client

// Run the command
$ webhook-client post-webhook-notify --insecure --filename data.json

Code Review Verification Steps

[ ] Have the Jira acceptance criteria been met for this change?

References

Jira story for this change

Messages

:book:
:link: MB-2757

  Generated by :no_entry_sign: dangerJS against e78456a8749989558bb7a522449cbde8a0c492b2


Floating point math issue

Hi, thanks for the awesome plugin! Really useful for work hour tracking for example..
I have noticed an issue, not sure if with this plugin or Joplin, but it has some troubles with floating point additions. That old chestnut..

Edit: A possible solution: https://www.thewebflash.com/solution-for-floating-point-problems-in-javascript/

It is not possible to control the computing operations from the Joplin plugin level. All calculations are performed by https://github.com/handsontable/formula-parser

Thank you for the response. I understand that it's not something you can fix. I might submit an issue with the formula-parser repository.. :)


ts-web/core: Run playground e2e in nodejs

In case we want to ensure ts-web/core works in nodejs too (with xhr2 polyfill)

Ah, nevermind, it breaks at crypto is not defined

node 18 says:
Error: callUnary method http://localhost:42280/oasis-core.NodeController/WaitReady: RpcError: Http response at 400 or 500 level, http status code: 0

is that on public node? public node doesn't allow Wait* calls

nope http://localhost:42280/oasis-core.NodeController/WaitReady

does xhr have a debug mode? grpc-web is bad about always saying "400 or 500 level" even when it's not that :slightly_frowning_face:

does the WaitReady work in local testing?

oh it's complaining about stakingDelegationsTo now, weird

HTTP 1937: SOCKET ERROR: connect ECONNREFUSED <IP_ADDRESS>:42280 Error: connect ECONNREFUSED <IP_ADDRESS>:42280

why :skull:

[2023-05-09 21:01:49.358][1833][critical][main] [source/server/server.cc:131] error initializing configuration 'sample-envoy.yaml': Protobuf message (type envoy.config.bootstrap.v3.Bootstrap reason INVALID_ARGUMENT:(route_config.virtual_hosts[0].routes[1]) prefix: Cannot find field.) has unknown fields
[2023-05-09 21:01:49.358][1833][info][main] [source/server/server.cc:980] exiting
Protobuf message (type envoy.config.bootstrap.v3.Bootstrap reason INVALID_ARGUMENT:(route_config.virtual_hosts[0].routes[1]) prefix: Cannot find field.) has unknown fields

oh shoot there's stuff in the start proxy step

idk
start proxy shouldn't matter, because cypress was passing. I can reenable cypress to show the api works

unless cypress tests have been a lie all along

start proxy shouldn't matter, because cypress was passing.

from this one? no "start proxy" complaints in this one
https://github.com/oasisprotocol/oasis-sdk/actions/runs/4812687701/jobs/8568248031

oh. Cypress is failing too! https://github.com/oasisprotocol/oasis-sdk/actions/runs/4941702070/jobs/8834600915

okay, summary time:

before bded9eb030e7eba0b06e9e77e1936f1c4b69d822: cypress passed, nodejs 14 passed until crypto was needed
bded9eb030e7eba0b06e9e77e1936f1c4b69d822: cypress passed, nodejs 18 immediately failed
ba55f87bf425f3a869aea675983921a525798326: i removed cypress in case it's requests broke the API. They didn't
662ab03154dc09476ebdd68493343f36634c3191: nodejs 18 worked against public grpc :shrug:
e2918ee11018a8bc345114e485c250967ebb824c: i attempted to upgrade envoy. I probably broke it. And I didn't have cypress to tell me
1b9862d09c12565835c56f1e9ffb6be6f2c959e2: enabled nagle's algorithm (defaulted to disabled in nodejs16). Doesn't seem to matter
f94f88a76bb7daabc690cb9c7766280d53b12895: --dns-result-order=ipv4first (defaulted to verbatim in nodejs17). This would have worked if I didn't break envoy earlier.

175a05dd4c00708c399423373a7ed472ac7a486d --dns-result-order=ipv4first works because I guess envoy doesn't like ipv6. And all of it would have worked against public grpc since the beginning

update: https://github.com/oasisprotocol/oasis-sdk/pull/1246/commits/9d74cd5645e90afd731495cc5508e2e083fc39c0 nodejs 18 only passed until crypto was needed :facepalm:

oh shoot, the envoy config specifically says the ipv4 address <IP_ADDRESS>. maybe we should change localhost in the test to <IP_ADDRESS>


New Interest Math

Changes how interest is accrued in Goalz

The failing tests is fixed in https://github.com/mikeghen/goalz/compare/deposit-save-token


Log InsertRowsNode in WAL

Description
This PR is adding a new InsertNode type InsertRowsNode in WAL. In previous versions, the InsertRecords request will split to InsertRowNode and then log into the WAL. However, we can group some InsertRowNodes to a large InsertRowsNode. The efficiency of WAL will increase after this optimization.
Details see https://apache-iotdb.feishu.cn/docx/FSXodTETyolOOtxdSiFcMfuznbe

It's better to add some tests about getting InsertRowsNode in the ConsensusReqReaderTest.

All done. PTAL


Get notifications of CloudFront 4xx errors in Slack

Required for #1878. Give us more visibility into when we've accidentally deleted a bunch of objects from the Loris S3 bucket. 🙈
It's a bit of a faff, because CloudFront (and thus CloudFront metrics) all live in us-east-1, whereas the rest of our infra lives in eu-west-1. The monitoring stack isn't planning/applying cleanly, because Terraform can't seem to import resources that live in a different region.
Possibly we should just count ALB metrics instead?

Okay, with the multiple providers stuff, it’s applying cleanly now.


Improve the help given by the CLI

Coverage remained the same at 100.0% when pulling d24055cb975359e23fce37fd1a504306b2a79b99 on juanjoDiaz:improve_cli_info into 28f8f5d5a79fcb128b41510f20616090b2a381f9 on zemirco:master.


Provide de-facto version of existing tasks similar to new tasks

Can there be made available an already processed json file for both the zero shot dataset, and with few shot prompting for the existing and new tasks? My understanding is this exists for the new tasks but not the existing?
As a result of trying to run the preprocessing scripts I've run into the following issues so far:

The same issues here https://github.com/google-research/arcade-nl2code/pull/1 and here https://github.com/google-research/arcade-nl2code/pull/2.
One of the kaggle dataset versions was not available so had to update from version 1 to version 2 sasikaamarasinghe/student-performance-gce-al-exam-2020-sri-lanka,https://www.kaggle.com/datasets/sasikaamarasinghe/student-performance-gce-al-exam-2020-sri-lanka,2
Was using python version 3.11 which ran into some issues with dataclasses when running one of the processing steps. Required re-installing all packages from a conda python 3.9 environment
The faketime library being referred to wasn't the pypi library with the same name. Ended up running brew install libfaketime to install the correct binary

Same here. It's almost impossible to preprocess the dataset, even if I followed each step very carefully.


Requires pre-inited .ipfs repo

Starting a pre-built Orbit.app fails cryptically with the following errors. It seems that it requires:

an existing ipfs repo to exist in ~/.ipfs

This shouldn't be case anymore, fixed in pubsub branch.


feat: add 'title' and 'url' to common fields for project item content

Closes https://github.com/gr2m/github-project/issues/19
I confirmed the GraphQL api has these two properties listed as required strings. Not sure if you have a process to automatically update the fixture data, but I went ahead and added the properties manually so the tests would pass.

@all-contributors add @mikesurowiec for code and test


Chart.js v2 compatibility

Are there any plans to make this addon compatible with the upcoming v2 release of Chart.js? I'm specifically looking forward to using their time-series charts.

<EMAIL_ADDRESS>is now released https://github.com/nnnick/Chart.js/releases/tag/v2.0.0

👍

@aomran update ? :)

Yes I will be updating the addon to use v2 as soon as I can. I'm really looking forward to the auto-updating charts because that'll remove some code we had to add here.

Needing Chartjs 2 a lot now. They have added some great features

https://github.com/aomran/ember-cli-chart/pull/54

Thank you very much for your hard work!! :D

Just another party interested to see ember-cli-chart support ChartJS v2. How can we help? Thanks for your work on this! :)

note that #54 was merged so version 3 is now available on npm


Fix loading of >1 dim netcdf datasets from netcdf to DataSetinmem

The wrong from of meshgrid was being used

[ ] Newsfragment
[x] Test for 3d?

@astafan8 ready for a first review I think. Will add a newsfragment before merging


M1 MacBook - unable to "make docker"  when preparing the network (chapter 4, page 129)

I hope someone can help me with this. Thanks!
I followed the instruction up to step 6, page 129, $cd fabric-ca $make docker (after cloning fabric-ca release-1.4 to go/src/github.com/hyperledger/) to build docker image. I'm getting error:

dev@ubuntusx2004:~/go/src/github.com/hyperledger/fabric-ca$ make docker
Building build/docker/bin/fabric-ca-client
Unable to find image 'hyperledger/fabric-baseimage:arm64-0.4.21' locally
docker: Error response from daemon: manifest for hyperledger/fabric-baseimage:arm64-0.4.21 not found: manifest unknown: manifest unknown.
See 'docker run --help'.
make: *** [Makefile:124: build/docker/bin/fabric-ca-client] Error 125

Below are $PATH, and Docker version and images on my system
Path

/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/usr/local/go/bin:/home/deve/go/bin:/home/deve/go/src/github.com/hyperledger/fabric/build/bin:/opt/jdk-17/bin

Docker
Docker version 20.10.14, build a224086

Docker Images on the system
REPOSITORY                   TAG                              IMAGE ID       CREATED        SIZE
hyperledger/fabric-tools     2.2                              f9a652b12c24   9 hours ago    439MB
hyperledger/fabric-tools     2.2.5                            f9a652b12c24   9 hours ago    439MB
hyperledger/fabric-tools     arm64-2.2.5-snapshot-4ab905936   f9a652b12c24   9 hours ago    439MB
hyperledger/fabric-tools     latest                           f9a652b12c24   9 hours ago    439MB
<none>                       <none>                           ab23e83b7078   9 hours ago    780MB
<none>                       <none>                           e29d6fb8cce3   9 hours ago    704MB
hyperledger/fabric-peer      2.2                              ad4c26b64b24   9 hours ago    51.9MB
hyperledger/fabric-peer      2.2.5                            ad4c26b64b24   9 hours ago    51.9MB
hyperledger/fabric-peer      arm64-2.2.5-snapshot-4ab905936   ad4c26b64b24   9 hours ago    51.9MB
hyperledger/fabric-peer      latest                           ad4c26b64b24   9 hours ago    51.9MB
<none>                       <none>                           0ec779e71ead   9 hours ago    625MB
hyperledger/fabric-orderer   2.2                              552df759ab58   9 hours ago    33.4MB
hyperledger/fabric-orderer   2.2.5                            552df759ab58   9 hours ago    33.4MB
hyperledger/fabric-orderer   arm64-2.2.5-snapshot-4ab905936   552df759ab58   9 hours ago    33.4MB
hyperledger/fabric-orderer   latest                           552df759ab58   9 hours ago    33.4MB
hyperledger/fabric-ccenv     2.2                              71d2203495c9   9 hours ago    512MB
hyperledger/fabric-ccenv     2.2.5                            71d2203495c9   9 hours ago    512MB
hyperledger/fabric-ccenv     arm64-2.2.5-snapshot-4ab905936   71d2203495c9   9 hours ago    512MB
hyperledger/fabric-ccenv     latest                           71d2203495c9   9 hours ago    512MB
hyperledger/fabric-baseos    2.2                              faf4c9cedc23   9 hours ago    6.66MB
hyperledger/fabric-baseos    2.2.5                            faf4c9cedc23   9 hours ago    6.66MB
hyperledger/fabric-baseos    arm64-2.2.5-snapshot-4ab905936   faf4c9cedc23   9 hours ago    6.66MB
hyperledger/fabric-baseos    latest                           faf4c9cedc23   9 hours ago    6.66MB
alpine                       3.14                             ac73e934f311   9 days ago     5.34MB
golang                       1.17.5-alpine3.14                5d548a459734   4 months ago   312MB
golang                       1.17.5-alpine                    939b513d7ff8   4 months ago   313MB

I found a solution. I needed to add binutils-gold Dockerfile both images/tools/ and images/peer/

I found a solution to this issue. I need to clone fabric baseImage, check out branch v0.4.21, and build the arm64 base image. After that, make docker image for fabric-ca.

@jdtProg Sorry, I haven't had the time to check this repository in a while. And yes, you will need to jump through some hoops to build base images for non-standard platforms. Glad you were able to get it working. I'll close this issue now.


Fix Compatibility Information & Add Code Sample for Raspberry Pi

Added that the sensor is functional in Raspberry Pi after tests
Added a code sample

Any update?

I don't think they ever merge any pull requests 🤷♂

They actually merged previous requests, don't know what happened with this
one. Regards.

Fernando Ribeiro
On Thu, Mar 12, 2020, 12:19 AM Toby56<EMAIL_ADDRESS>wrote:

I don't think they ever merge any pull requests 🤷♂
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/SeeedDocument/wiki_english/pull/15#issuecomment-597986253,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABEEISGGEQPZ3SJ4QVEHUTRHBIFPANCNFSM4GE6MSUA
.


About textured mesh

How can i get textured mesh(.obj)

Hi, @Snow-02
We are still preparing the code for mesh reconstruction and expect to publish it within 2 weeks. You can right now refer to https://github.com/xxlong0/Wonder3D to get textured mesh.


Add: help menu using '?' key

Sorry it took so long I forgot. the release reminded me.
I tried making the UI similar to lazygit With the green keybind menu and blue keybinds text on the bottom of the screen and i updated the readme.
This pull request isn't really meant to be accepted right now. just checking if there's any problems with the code or UI and also I need to blue keybind text to update based on context and you can't move in the help menu using the 'j' and 'k' keys.

You shouldn't add the binary, BTW

Thanks for removing the binary. Maybe it should be added to .gitignore file

Thanks for removing the binary. Maybe it should be added to .gitignore file

Am not really for or against the idea. Though it was a mistake on my part

Just got to clean up the help status string since it a bit unreadable in the table view

Is it possible that the modal shows up a tview.Table with borders showing the keymaps? it will make it navigable by default and i think it is prettier, but that's personal.

I'll try doing it

Just Looked over it and since I don't see any problems with it. I'll just finish feature here.

The last force-pushed was for fixing the wrong email address on the commits.

I may close this pull request and make new one based on current main and readd my changes from there since. It seems easier and less likely for me to make mistake than fixing conflicts using the GitHub website UI.


Qbft RPCs should be disabled after starting with or switching to use validator contract

PR description
Qbft RPCs should be disabled after starting with or switching to use validator contract
Signer metrics and getValidatorsByBlock... should remain enabled.
Fixed Issue(s)
Related to https://github.com/hyperledger/besu/issues/2795
Changelog

[x] I thought about the changelog and included a changelog update if required.

Split out the transition bug onto another issue https://github.com/hyperledger/besu/issues/2868


issue:#42 Readme file updation

closes issue:#42
This PR updates the README.md file

@gatlanagaprasanna First thing first
As per given in #42 , firstly contributors interested in issue would show what all updates they would love to do. Then if I find it worth then only I will assign them issue. This is in place because these days many contributors just edit 1-2 lines in readme file and expect them to be merged. Now secondly you didn't show the updates which you propose to do.  Now lastly you just updated the readme with the last commit which I had done(I have removed that for a reason).
Kindly go through the contributor guidances as such thing won't benefit.


Port ratio/proportional cv fix from hds and add tests

Pull requests into cqm-parsers require the following. Submitter and reviewer should :white_check_mark: when done. For items that are not-applicable, note it's not-applicable ("N/A") and :white_check_mark:.
Submitter:

[x] This pull request describes why these changes were made.
[ ] Internal ticket for this PR:
[ ] Internal ticket links to this PR
[ ] Code diff has been done and been reviewed
[ ] Tests are included and test edge cases
[ ] Tests have been run locally and pass

Reviewer 1:
Name:

[ ] Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
[ ] The tests appropriately test the new code, including edge cases
[ ] You have tried to break the code

Reviewer 2:
Name:

[ ] Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
[ ] The tests appropriately test the new code, including edge cases
[ ] You have tried to break the code

Codecov Report

Merging #48 into bonnie_version will not change coverage.
The diff coverage is 100%.

@@               Coverage Diff               @@
##           bonnie_version      #48   +/-   ##
===============================================
  Coverage           82.35%   82.35%
===============================================
  Files                  69       69
  Lines                4314     4314
===============================================
  Hits                 3553     3553
  Misses                761      761

Impacted Files
Coverage Δ

...rser/cql/document_helpers/doc_population_helper.rb
98.86% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Handle circular refs

@drewbanin were you able to make any headway on this?

@cmcarthur not yet, but planning on carving out some time today. I think we're close!

I think I've narrowed this down to a bug in networkx v1.11. Check this out:
> /Users/drew/fishtown/dbt/dbt/linker.py(44)find_cycles()
     34         try:
     35             # cycles = nx.algorithms.find_cycle(self.graph) # Old approach
     36             cycles = list(nx.simple_cycles(self.graph)) # Potential new approach
     37
     38         except nx.exception.NetworkXNoCycle:
     39             return None
     40
     41         import ipdb; ipdb.set_trace()
     42
---> 43         if cycles:
     44             return " --> ".join([".".join(node) for node in cycles])

ipdb> cycles
[['model.project.model_1', 'model.project.model_2']]
ipdb> nx.algorithms.find_cycle(self.graph)
*** networkx.exception.NetworkXNoCycle: No cycle found.
ipdb>

So, nx.simple_cycles finds the cycle, but nx.algorithms.find_cycle does not! The fix is provided here, but I think that would require us to upgrade to version 2.x of networkx. We should do that eventually, but I might reswizzle this to use nx.simple_cycles in the meantime

I've tested this change with a bunch of our Fishtown jobs that failed in Sinter due to a cycle which wasn't correctly reported. It picked up on all of them! I'll feel really good about merging this once the tests pass

aw yeah! nice find

This was due to a Networkx bug. More info here: https://github.com/networkx/networkx/pull/2473


Documentation/db api swagger

Test fix for https://github.com/arangodb/arangodb/pull/12221#issuecomment-658402526

Confirmed to be working:
https://5f0eed22253892000806ad02--zealous-morse-14392b.netlify.app/docs/3.8/aql/functions-miscellaneous.html#in_range
Downside of <!-- separator --> for distinct example blocks: they remain in the generated HTML.


Update blender-daily to 2.79-b07dcb8fb06

After making all changes to the cask:

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

Additionally, if updating a cask:

[ ] sha256 changed but version stayed the same (what is this?).
I’m providing public confirmation below.

Hmmm, every time I merge I get this basically
$ brew cask install --force blender-daily
==> Satisfying dependencies
==> Downloading https://builder.blender.org/download/blender-2.79-b07dcb8fb06-OSX-10.6-x86_64.zip
Already downloaded: /Users/rw/Library/Caches/Homebrew/Cask/blender-daily--2.79-b07dcb8fb06.zip
==> Verifying checksum for Cask blender-daily
==> Installing Cask blender-daily
Warning: It seems there is already an App at '/Applications/Blender.app'; overwriting.
==> Removing App '/Applications/Blender.app'.
Error: It seems the App source '/usr/local/Caskroom/blender-daily/2.79-b07dcb8fb06/Blender.app' is not there.
Error: Install incomplete.

Also this updates daily, and older daily builds get removed from the blender website, so I guess this build breaks everyday anyway.  Any way to tackle this?  I guess we can look at info from their webstite and parse that, but I'm unsure if brew allows that.
CC @fanquake @commitay (im not sure who is the maintainer here?)

Also this updates daily, and older daily builds get removed from the blender website, so I guess this build breaks everyday anyway. Any way to tackle this? I guess we can look at info from their webstite and parse that, but I'm unsure if brew allows that.

url do but in this case it won't work because the apps are inside a folder with an expanded "version".
'blender-2.79.0-git20170827.b07dcb8fb06-x86_64/blender.app'

Removing this because it will break constantly.


docs: clarify installation and usage instructions

It took some piecing together of various forum comments in order to get this working for me. The instructions in the README.md didn't work for me at all (with Heroku), but the ones I have added worked perfectly. Additionally, I'm happy to take any extra information in to consideration in order to help clarify this documentation as this is a pretty great package to have around.

Thanks for this PR and sorry for late merge.


docs: add WithDisableHeaderNamesNormalizing option

What type of PR is this?
docs

Check the PR title.

[x] This PR title match the format: <type>(optional scope): <description>
[x] The description of this PR title is user-oriented and clear enough for others to understand.

(Optional) Translate the PR title into Chinese.
(Optional) More detailed description for this PR(en: English/zh: Chinese).

zh(optional): 添加 WithDisableHeaderNamesNormalizing 选项
(Optional) Which issue(s) this PR fixes:

https://github.com/cloudwego/hertz/issues/957

@Skyenought


Davinci proposal for new "start of encounter" hook

Hey @lmckenzi , overall, looks great!

Note that there can be multiple 'starts' for the same encounter as each user becomes engaged.  For example, when a scheduled encounter is presented at the beginning of the day for planning purposes, when the patient arrives, when the patient first encounters a clinician, etc.  Hooks may present different information depending on user role and Encounter.status.

Within the shoes of a CDS Client implementer, this description, while informative, is a bit loosey-goosey.
Do you think it's possible to more tightly specify the workflow or user type?  It may be the case that we're not sure yet and more implementer feedback is needed to see if a tighter spec is possible. And that's okay.

It could be relevant for multiple types of users - admissions clerk/receptionist, nurse, physician.  Each would have an interest in/influence on what tasks need to be done during the encounter and might have responsibility for following particular protocols, ensuring clinical trial requirements and/or payor requirements are met, etc.  It would be up to the service to determine what sort of information to display based on user role.  The timing of the hook is essentially when a user first deals with the encounter (or at least when they're in the early stages of dealing with the encounter).  I'm not really sure how to nail it down much more than that with general applicability, though it's possible that EHR implementers might be able to tighten it a bit more if there's more concrete consistent implementation aspects we can tie it to.

Since we have consensus on the reviews, I'm going to merge this PR in. This is still in draft state and I expect the discussion to continue around this hook.
Thanks @lmckenzi for putting this hook together!


added instructions to compile under macos and modified makefile

I'm going to try to improve performance on mac if possible


Run tests for Python 3.11 in GitHub Actions.

Assuming that we support Python 3.11, it is beneficial to run the tests for this version too.

@all-contributors add @imankulov for tests

Thanks for updating the test matrix! 💯


new error message in prod logs

mongodb 3.2
replication protocol 1
reactivemongo 0.11.9
2016-01-08 17:43:49,767 [ERROR] r.c.a.MongoDBSystem oups. 18073267 not found! complete message is Response(MessageHeader(36,469536914,18073267,1),Reply(8,0,0,0),LittleEndianHeapChannelBuffer(ridx=36, widx=36, cap=36),ResponseInfo(1196412026))
2016-01-08 19:45:30,612 [ERROR] r.c.a.MongoDBSystem oups. 38130795 not found! complete message is Response(MessageHeader(10505,882953,38130795,1),Reply(8,14469080318,0,101),LittleEndianHeapChannelBuffer(ridx=36, widx=10505, cap=10505),ResponseInfo(-2141655548))
2016-01-08 21:40:27,103 [ERROR] r.c.a.MongoDBSystem oups. 55927595 not found! complete message is Response(MessageHeader(443,514797163,55927595,1),Reply(8,0,0,1),LittleEndianHeapChannelBuffer(ridx=36, widx=443, cap=443),ResponseInfo(2138265431))
2016-01-08 22:31:56,000 [ERROR] r.c.a.MongoDBSystem oups. 63843084 not found! complete message is Response(MessageHeader(275,524318057,63843084,1),Reply(8,0,0,1),LittleEndianHeapChannelBuffer(ridx=36, widx=275, cap=275),ResponseInfo(-3260572))

Any idea what that could mean?

Weird, it got response for request it hasn't sent.
Would not to check whether it's related to a protocol change.

doesn't look like it's reactivemongo's fault.

@ornicar Did you found the source of the error?

I don't think I did.

Im getting the same error when using akka streams to bash updates to mongodb, im using  "play2-reactivemongo" % "0.12.6-play26"


Generated modular alert_actions.conf does not contain icon_path by default

If globalConfig.json has an alert configuration, ucc-gen should create alert_actions.con file providing default alert icon. Otherwise, Appinspect CLI complains about missing icon_path.

:tada: This issue has been resolved in version 5.8.2 :tada:
The release is available on:

v5.8.2
GitHub release

Your semantic-release bot :package::rocket:


Add manifest overrides.

Need to bikeshed names for the various overrides.

@dlongley ready for another pass.


Package request: Bitfocus Companion

Bitfocus Companion enables the reasonably priced Elgato Streamdeck to be a professional shotbox surface for an increasing amount of different presentation switchers, video playback software and broadcast equipment.

Bitfocus Companion let's you turn your Elgato Stream Deck into a supercharged macro keyboard. It even let's you do more things with it than the official Stream Deck software on Windows does.
Metadata

homepage URL: https://bitfocus.io/companion
source URL: https://github.com/bitfocus/companion
license: mit, "Bitfocus Individual Contributor License Agreement for companion"
platforms: linux

I attempted to package this app, but encountered some problem when vite needs a display server and cannot be run in a nix build sandbox, which is a headless environment.

AFAIK the aur package installs as headless only, so I wouldn't mind if the NixOS one does as well.
The only thing that would be nice to have is a module that starts companion via a service and has a config option to define the directory where development companion-modules are. I believe the companionship-pi could serve as reference here.

I attempted to package this app, but encountered some problem when vite needs a display server and cannot be run in a nix build sandbox, which is a headless environment.
Turns out the vite I tried to use was different from the vite that is downloaded in the package, so this is a non-issue.

AFAIK the aur package installs as headless only, so I wouldn't mind if the NixOS one does as well. The only thing that would be nice to have is a module that starts companion via a service and has a config option to define the directory where development companion-modules are. I believe the companionship-pi could serve as reference here.

The companion-pi package downloads the prebuilt binary from the bitfocus website, which works fine in an FHS environment, but it's not an ideal solution. I attempted to follow the build instructions provided in the companion package, which can build the headless version alone, and it builds fine with yarn in an FHS environment. However, the yarn build steps pull in way too many dependencies to work with a pure environment. I guess FOD is the way to go?

I am also quite interested in this and would like to know the status of this.
I have tried to do this with nix-shell but am running into a dependency on libX11 which I cannot seem to solve.
{ pkgs ? import <nixpkgs> {} }:
(pkgs.buildFHSUserEnv {
  name = "pipzone";
  targetPkgs = pkgs: (with pkgs; [
    glib
    nss
    nspr
    dbus
    atk
    cups
    libdrm
    gtk3
    pango
    cairo
    #xorg
    #libX11
]);
  runScript = "bash";
      profile = ''
       export LD_LIBRARY_PATH=${pkgs.glibc}/lib
     '';
}).env

I am also quite interested in this and would like to know the status of this.
I have tried to do this with nix-shell but am running into a dependency on libX11 which I cannot seem to solve.
[...]
This is the error I am getting right now:
└─Δ ./companion-launcher
./companion-launcher: error while loading shared libraries: libX11.so.6: cannot open shared object file: No such file or directory

Thanks for this idea, I went ahead and managed to resolve any further dependencies with this:
{ pkgs ? import <nixpkgs> {} }:
(pkgs.buildFHSUserEnv {
  name = "pipzone";
  targetPkgs = pkgs: (with pkgs; [
    glib
    nss
    nspr
    dbus
    atk
    cups
    libdrm
    gtk3
    pango
    cairo
    xorg.libX11
    xorg.libXcomposite
    xorg.libXdamage
    xorg.libXext
    xorg.libXfixes
    xorg.libXrandr
    xorg.libxcb
    libxkbcommon
    libudev-zero
    libusb1
    fontconfig
    alsaLib
    mesa
    expat
]);
  runScript = "bash";
      profile = ''
       export LD_LIBRARY_PATH=${pkgs.glibc}/lib
     '';
}).env

to run it works either to run the companion-launcher or the companion_headless.sh scripts.
For the headless version you can use these flags:
--list-interfaces, 'List the available network interfaces that can be passed to --admin-interface'
--admin-port <number>, 'Set the port the admin ui should bind to, 8000
--admin-interface <string>', 'Set the interface the admin ui should bind to. The first ip on this interface will be used'
--admin-address <string>, 'Set the ip address the admin ui should bind to (default: "<IP_ADDRESS>")
--config-dir <string>', 'Use the specified directory for storing configuration. The default path varies by system, and is different to 2.2 (the old path will be used if existing config is found)'
--extra-module-path <string>, 'Search an extra directory for modules to load'
--machine-id <string>, 'Unique id for this installation'
--log-level <string>, 'Log level to output to console'


Gravity breaks revolute joint's angle limits

In 3D in a chain of multiple dynamic bodies connected via revolute joints with specified angle limits (in a setup similar to crates/avian3d/examples/chain_3d.rs where the first body kinematic), the bodies that "carry" other bodies connected to them break out of their joint's limits.
For example, in a setup with 10 bodies and angle limit set to a const PI / 4.0 (same in min and max) this happens:

When the gravity is switched off the bodies settle in a circle as expected (note that 2 bodies are overlapping here):

Changing the density of the bodies doesn't seem to have any effect, but change in gravity does. In here it's increased from the first screenshot, which forces the bodies break out further out of their limits:

edit: all the joints have compliance set to 0.0

My temporary hacky workaround is to multiply correction calculated in fn apply_angle_limits by some constant > 1 so that it "overpowers" the gravity


I'm looking for version 0.3.0-rust-1.46.0

If you don't find the version you're looking for, please open a new github issue to publish one

Since we are going from 1.45 directly to 1.51 (https://github.com/softprops/lambda-rust/pull/87/files) closing this.


flutter attach - Oops; flutter has exited unexpectedly.

Steps to Reproduce
Running flutter attach from android studio terminal not working. Showing error Oops; flutter has exited unexpectedly.
Logs
flutter attach
Checking for advertised Dart observatories...

Oops; flutter has exited unexpectedly.
Sending crash report to Google.
Crash report sent (report ID: 50ca8df4de508ad3)

Crash report written to /Users/johnnykuttymathew/Documents/Work/Code/<project>/flutter_04.log;

Log file flutter_04.log

$ flutter doctor -v
[✓] Flutter (Channel stable, v1.5.4-hotfix.2, on Mac OS X 10.14.4 18E226, locale en-DE)
    • Flutter version 1.5.4-hotfix.2 at /usr/local/custom/flutter
    • Framework revision 7a4c33425d (3 weeks ago), 2019-04-29 11:05:24 -0700
    • Engine revision 52c7a1e849
    • Dart version 2.3.0 (build 2.3.0-dev.0.5 a1668566e5)

[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
    • Android SDK at /Users/johnnykuttymathew/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-28, build-tools 28.0.3
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1248-b01)
    • All Android licenses accepted.

[✓] iOS toolchain - develop for iOS devices (Xcode 10.2)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 10.2, Build version 10E125
    • ios-deploy 1.9.4
    • CocoaPods version 1.6.1

[✓] Android Studio (version 3.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 34.0.1
    • Dart plugin version 182.5215
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1248-b01)

[!] IntelliJ IDEA Ultimate Edition (version 2019.1.1)
    • IntelliJ at /Applications/IntelliJ IDEA.app
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    • Dart plugin version 191.7019
    • For information about installing plugins, see
      https://flutter.dev/intellij-setup/#installing-the-plugins

[✓] Connected device (1 available)
    • iPhone Xʀ • 98882BC0-AF96-4B19-B530-78A7EFAA5DFF • ios • com.apple.CoreSimulator.SimRuntime.iOS-12-2 (simulator)

! Doctor found issues in 1 category.

Here I have a fresh installation of android studio new version and flutter new version.I have the same problem but with flutter doctor --android-licenses command. Any help would be appreciated.
flutter_04.log

For me,
Stable channel failing, but master channel working fine.

On 23-May-2019, at 3:53 AM, jjarral<EMAIL_ADDRESS>wrote:
Here I have a fresh installation of android studio new version and flutter new version.I have the same problem but with flutter doctor --android-licenses command. Any help would be appreciated.
flutter_04.log
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

How can i switch between channels? I think I’ve stable channel here for me..

@jjarral type flutter channel master in terminal.

terminal in android studio or the terminal of ubuntu itself?

Anywhere

I am still getting this problem...

error too, channel is stable, when i switch to dev, it fine.

Do you still experience it? That dev is far ago in stable.

Without additional information, we are unfortunately not sure how to resolve this issue. We are therefore reluctantly going to close this bug for now. Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.