Live

Update feed.atom (#7146)

[Doc Improvement][Add sso command bot code snippet for teamsfx sdk][2665913] (#7051)

Add sso command bot code snippet

Fix typo

Update link

docs: add sso for message extension api director

.

.

.

.

.

.

.

coding tag updated

Co-authored-by: turenlong<EMAIL_ADDRESS>Co-authored-by: wenyutang-ms<EMAIL_ADDRESS>Co-authored-by: v-vpaliwal<EMAIL_ADDRESS>Co-authored-by: v-sdhakshina<EMAIL_ADDRESS>Co-authored-by: v-habibaumme<EMAIL_ADDRESS>

[Doc Issue][Describe how to handle status codes from bot APIs][2466522] (#6335)

got issue

Adding status codes

Minor edits

Minor edits

Minor edits

Minor edits

Minor edits

Adding status codes

minor edits

adding status codes

Adding codes

minor edits

Minor update

minor edits

Status code update

Minor edits

Minor edits

Update conversation-messages.md

Minor edits

Minor edits

Minor edits

Minor edits

Minor edits

Minor updates

Minor updates

Update conversation-messages.md

Updates

Update conversation-messages.md

Update conversation-messages.md

Updates

Update conversation-messages.md

Co-authored-by: v-habibaumme<EMAIL_ADDRESS>Co-authored-by: v-npaladugu<EMAIL_ADDRESS>

[Doc Improvement][UI updates on create tab][2668497] (#7145)

updates as per testing

minor edits

minor edits

minor edits

[]Doc Improvement][Update provision in cloud resources][2668619] (#7150)

update-provision-cloud-resources

Interchanged Use an existing Azure AD app for your bot to Use an existing Azure AD app for your Teams app. and
Use an existing Azure AD app for your Teams app to  Use an existing Azure AD app for your bot.

Update provision.md

updated for Visual studio code and Visual studio

Update publish.md

[Doc Improvement][Collaboration control review][2658603] (#7119)

Update collaboration-control.md

Update collaboration-control.md

Update collaboration-control.md

Doc improvement

Update app-with-collaboration-controls.md

Update collaboration-control.md

Update collaboration-control.md

Update collaboration-control.md

Update install-collaboration-control.md

Update install-collaboration-control.md

Update app-with-collaboration-controls.md

Update app-with-collaboration-controls.md

Worked on as per the standards

Update collaboration-control-power-automate.md

Working on editing the content as per the standards
Co-authored-by: v-spharish<EMAIL_ADDRESS>Co-authored-by: v-habibaumme<EMAIL_ADDRESS>

Update submission-checklist.md

[Doc Improvement][Remove deprecated "packageName" value from app manifest schema article][2651838] (#6959)

Updated the article

Edited and removed the occurrence of packageName in the article.

Co-authored-by: v-jganga<EMAIL_ADDRESS>Co-authored-by: v-vpaliwal<EMAIL_ADDRESS>
minor updates (#7169)

Co-authored-by: v-habibaumme<EMAIL_ADDRESS>
Doc improvement (#7166)

Co-authored-by: v-habibaumme<EMAIL_ADDRESS>

[Doc Improvement][Adding space after see Virtual Assistant and skills architecture] (#7178)

Doc improvement

Doc improvement

Doc improvement

Doc improvement

minor changes

[Doc Improvement][Spell check] (#7184)

Spell check

Update removal-page.md

Co-authored-by: v-habibaumme<EMAIL_ADDRESS>

[Doc Improvement][Typo fix tools and SDK] (#7182)

Update build-environments.md

updates

updates

[Doc issue][Update deep link article- Auto trigger] (#7136)

update-deep-link-article

Added content about Generate a deep link to share content to stage in meetings.

Update deep-links.md

added dev preview note to the article

Updated the article

Updated the QA comments.

Updated

Updated the QA comments

Update deep-links.md

Updated the QA comments

Update deep-links.md

Updated the note and description

Update whats-new.md

updated what's new page
Co-authored-by: Ajith kumar<EMAIL_ADDRESS>

October 2022 M365 apps platform updates (#7165)

Piecemeal updates

Initial updates for latest feature support

Add LU screenshot, code sample

Build warning

Address review feedback

Review feedback

Latest updates

Update overview.md

adding table heading

M365 apps

Minor edits
Co-authored-by: v-habibaumme<EMAIL_ADDRESS>

[Doc Improvement][Update generate deep link to share content to stage] (#7197)

update-generate-depp-link-to-share-content-to-stage

Moved  Generate a deep link to share content to stage in meetings from Deep links article to Enable and configure apps in Teams meetings as per the comment by the PM in the PR #7136

Update enable-and-configure-your-app-for-teams-meetings.md

updated link

Live Share Ignite 2022 Updates (#7162)

Added Live Share canvas docs

Updated references to TeamsFluidClient

PR feedback

Separated each canvas tool into separate section with GIFs

PR feedback

Updated import style for teams-js in live share

Updated audio ducking docs and changed eraser gif

Updated overview page

Changed video format

Updated media feature image

Updated live share core capabilities page

Updated capabilities page images

Updated description

Update msteams-platform/apps-in-teams-meetings/teams-live-share-canvas.md

Co-authored-by: Corina<EMAIL_ADDRESS>
Update msteams-platform/apps-in-teams-meetings/teams-live-share-canvas.md

Co-authored-by: Corina<EMAIL_ADDRESS>
Update msteams-platform/apps-in-teams-meetings/teams-live-share-canvas.md

Co-authored-by: Corina<EMAIL_ADDRESS>

Changed default color for highlighter in UI

Updated docs to use LiveShareClient

Fixed video lint formatting bug

Fixed incorrect live share canvas link on overview

Update msteams-platform/apps-in-teams-meetings/teams-live-share-canvas.md

Co-authored-by: Corina<EMAIL_ADDRESS>
Update msteams-platform/apps-in-teams-meetings/teams-live-share-overview.md

Co-authored-by: Corina<EMAIL_ADDRESS>
Update msteams-platform/apps-in-teams-meetings/teams-live-share-overview.md

Co-authored-by: Corina<EMAIL_ADDRESS>
Update msteams-platform/apps-in-teams-meetings/teams-live-share-canvas.md

Co-authored-by: v-ypalikila<EMAIL_ADDRESS>
Update msteams-platform/apps-in-teams-meetings/teams-live-share-capabilities.md

Co-authored-by: v-ypalikila<EMAIL_ADDRESS>
Update msteams-platform/apps-in-teams-meetings/teams-live-share-canvas.md

Co-authored-by: v-ypalikila<EMAIL_ADDRESS>
Update msteams-platform/apps-in-teams-meetings/teams-live-share-canvas.md

Co-authored-by: v-ypalikila<EMAIL_ADDRESS>
Update msteams-platform/apps-in-teams-meetings/teams-live-share-canvas.md

Co-authored-by: v-ypalikila<EMAIL_ADDRESS>
Update msteams-platform/apps-in-teams-meetings/teams-live-share-canvas.md

Co-authored-by: v-ypalikila<EMAIL_ADDRESS>
Update msteams-platform/apps-in-teams-meetings/teams-live-share-canvas.md

Co-authored-by: v-ypalikila<EMAIL_ADDRESS>
Update msteams-platform/apps-in-teams-meetings/teams-live-share-overview.md

Co-authored-by: v-ypalikila<EMAIL_ADDRESS>
Update msteams-platform/apps-in-teams-meetings/teams-live-share-overview.md

Co-authored-by: v-ypalikila<EMAIL_ADDRESS>
Update msteams-platform/apps-in-teams-meetings/teams-live-share-capabilities.md

Co-authored-by: v-ypalikila<EMAIL_ADDRESS>

Fixed formatting

Updated install scripts with next tag

Update msteams-platform/apps-in-teams-meetings/teams-live-share-canvas.md

Co-authored-by: v-ypalikila<EMAIL_ADDRESS>
Update msteams-platform/apps-in-teams-meetings/teams-live-share-tutorial.md

Co-authored-by: v-ypalikila<EMAIL_ADDRESS>
Update msteams-platform/apps-in-teams-meetings/teams-live-share-tutorial.md

Co-authored-by: v-ypalikila<EMAIL_ADDRESS>
Fixed link

Co-authored-by: Corina<EMAIL_ADDRESS>Co-authored-by: v-ypalikila<EMAIL_ADDRESS>

[Doc Improvement][Correct CDN import example][2654714] (#6872)

Correct CDN import example

More sample code updates

Address PR review feedback.

.

Update msteams-platform/apps-in-teams-meetings/teams-live-share-tutorial.md

Co-authored-by: v-abirade<EMAIL_ADDRESS>

Incorporate PR review suggestions

.

.

Update teams-live-share-tutorial.md

.

Update teams-live-share-tutorial.md

.

.

Co-authored-by: v-ksar<EMAIL_ADDRESS>Co-authored-by: v-abirade<EMAIL_ADDRESS>Co-authored-by: v-vpaliwal<EMAIL_ADDRESS>Co-authored-by: v-jganga<EMAIL_ADDRESS>

[Doc Improvement][Update live share canvas alt-text] (#7205)

update-live-share-canvas

Updated image alt-text as per guidelines.
Implemented few Acrolinx suggestions.
Update what's new and landing page.
Updated the Toc entry form inking & cursors to Canvas.

Update whats-new.md

minor edit

Update teams-live-share-capabilities.md

updated Acrolinx

Update teams-live-share-canvas.md

minor edits

Update teams-live-share-canvas.md

minor edits

Update how-to-custom-azure-fluid-relay.md

minor edit

[Doc Feature][Update teams store validation guidelines][2495465] (#6352)

Update teams-store-validation-guidelines.md

As per the instructions in the doc, removed Old/Currently Live Guideline to be removed.

Update teams-store-validation-guidelines.md

Added new content to validation guidelines.

Update teams-store-validation-guidelines.md

fixed Acrolinx errors

Update teams-store-validation-guidelines.md

fixed heading errors

update-validatoin-guidelines

minor edits

Update teams-store-validation-guidelines.md

minor edits

Update teams-store-validation-guidelines.md

minor edits

Update teams-store-validation-guidelines.md

Fixed minor errors.

Update teams-store-validation-guidelines.md

minor edits

Update teams-store-validation-guidelines.md

Update teams-store-validation-guidelines.md

Update teams-store-validation-guidelines.md

Update teams-store-validation-guidelines.md

minor edits

Update teams-store-validation-guidelines.md

minor edits

update-teams-store-validation-guidelines

added app icons for new updated content.

update-store-validation-guidelines

updated images

Update crypto-currency-based-apps-icon.png

updated image text

Update teams-store-validation-guidelines.md

minor edits

Update teams-store-validation-guidelines.md

updated article based on new updated from Rajarshi.

Update teams-store-validation-guidelines.md

minor edits

validation-guideline

updated images shared by graphic designer.

Update teams-store-validation-guidelines.md

updated image indentation

updated-validation-images

Updated the validation images that had issues in set 1 with new images.

update-store-validation-images

updated images for 1st set.

update-store-validation-images

updated images.

updated-validation-images

updated images for validation set 1. final.

Update validation-bot-no-welcome-message-in-personal-scope.png

updated image

updated images

updated 3 images 1st set

validation-guidelines

updated images in 2nd set.

validation-guideline-images

updated image corrections

upate-images-validation-guidelines

updated 14 images from set 3

update-validation-guidelines-images

added 10 more images as part of 3rd set of images shared by lucky.

update-validation-guidelines

updated 9 images as part of 3rd set.

update-validation-guidelines-icons

updated bot and app listing Icons.

update-validation-guidelines

updated 16 icon images and also removed alt-text for icons as per guidelines.
Updated the icon image tag.

update-validation-images

updated images as per feedback from shalini.

updated-validation-giudeliens

updated 6 images as part of final review for images.

Update teams-store-validation-guidelines.md

Fixed Acrolinx errors.

update-validation-guidelines-images

updated changes to images as part for changes 4 zip file.

update-validation-guidelines

Updated the final 11 images shared by lucky as part for changes 4.

Update validation-app-description-microsoft-abbreviated.png

updated validation-app-description-microsoft-abbreviated.png image.

update-validation-guidelie-images

updated certificate icon.
Co-authored-by: v-habibaumme<EMAIL_ADDRESS>

[Doc Improvement][Teams 1-1 calls in GA and PSTN, end-end call apps update][2689783] (#7204)

Update teams-apps-in-meetings.md

updates

Update whats-new.md

minro edits

Update whats-new.md

minor edit

Updates

Update whats-new.md

Co-authored-by: v-habibaumme<EMAIL_ADDRESS>

Update publish.md (#7179)

Update publish.md

Update submission-checklist.md

Update update-apple-store-team-connect-id.md

Update resolve-submission-issues.md

Update overview.md

Update teams-store-ranking-parameters.md

Update common-reasons-for-app-validation-failure.md

Update TOC.yml

[Doc Feature][Overwrite the back button in the app, support more than two action from the top menu][2559298, 2559304] (#6801)

Article update

Added the new features for dev

Minor update

Updated the See also

Update personal-apps.md

Update personal-apps.md

Added feature

updated the back button featurefeature

Updated the article

Updated the article

Updated the doc

Updated the doc

Minor update

Minor update

Updated the doc

Updated the doc for or flesch score

Updated the doc

Updated the doc

Updated the article

Updated the article

Added the features

Edited and updated the features

Updated what's new

Updated what's new

Updated what's new

Updated what's new

Updated the article

Updated the article for peer review comments

Updated the article

Updated the article

Updated what's new

Updated what's new

Updated the article

Updated for peer review comments

Updated the images

Updated the images

Updated

Updated the description

Updated the article

Updated the article

Updated the infographic

Updated the infographic
Co-authored-by: v-habibaumme<EMAIL_ADDRESS>

[Doc Improvement][Apps support update for channel meetings] (#7219)

Update teams-apps-in-meetings.md

Update teams-apps-in-meetings.md

Update teams-apps-in-meetings.md

Update teams-apps-in-meetings.md

Update teams-apps-in-meetings.md

[Doc Improvement][Tab/Bot app display behavior in mobile(iOS/Android)][2678646] (#7190)

Doc improvement

minor changes

minor changes

minor changes

Update tabs-mobile.md

Co-authored-by: v-habibaumme<EMAIL_ADDRESS>

[Doc Improvement][Using Fluid with Microsoft Teams][2589853] (#6765)

port fluid doc

fix links

fix links

fix links

fix links

final fix for links

Update TOC.yml

.

.

Update using-fluid-msteam.md

converted note to a bulleted prerequisite
rewrote the second bullet of 'Create the project' into a more explicit tone
updated two dontnetcli code blocks to cmd
replaced the word 'married' with 'integrated' in the 'Create React component for Fluid view and data' section
upgraded a Note tag to Important
omit bash devlang tag
fixed JavaScript link
fixed warning message about bookmark

Update using-fluid-msteam.md

fix h1 error

Update using-fluid-msteam.md

tweaked verbiage of prerequisites opening sentence and last bullet
added 'see also' section

fixing TOC spacing issue

fixing TOC spacing issue

Update msteams-platform/tabs/how-to/using-fluid-msteam.md

Co-authored-by: Rick Kirkham<EMAIL_ADDRESS>
Update msteams-platform/tabs/how-to/using-fluid-msteam.md

Co-authored-by: Rick Kirkham<EMAIL_ADDRESS>
Update msteams-platform/tabs/how-to/using-fluid-msteam.md

Co-authored-by: v-abirade<EMAIL_ADDRESS>
Update msteams-platform/tabs/how-to/using-fluid-msteam.md

Co-authored-by: v-abirade<EMAIL_ADDRESS>
Update msteams-platform/tabs/how-to/using-fluid-msteam.md

Co-authored-by: v-abirade<EMAIL_ADDRESS>
Update msteams-platform/tabs/how-to/using-fluid-msteam.md

Co-authored-by: v-abirade<EMAIL_ADDRESS>
updates suggested by Rick-Kirkham and v-abirade

updates to Defining Fluid functions and parameters and Refactor content page to reflect Fluid application

update prereq button and ident list

fix indentation issue

fix indentation issue

fix indentation issue

.

.

.

.

.

Co-authored-by: v-ksar<EMAIL_ADDRESS>Co-authored-by: Rick Kirkham<EMAIL_ADDRESS>Co-authored-by: v-abirade<EMAIL_ADDRESS>Co-authored-by: v-vpaliwal<EMAIL_ADDRESS>

[Doc Fix][Video link fix] (#7234)

Update add-incoming-webhook.md

Update add-incoming-webhook.md

[Doc Improvement][Fix link to installing Teams Toolkit] (#7187)

Fixed a broken link to the section of installing Teams Toolkit in VSCode.

[Doc Issue][Teams Toolkit Doc bug-fix, use formal Azure service name][2697174] (#7192)

use formal Azure service name

"Azure functions" => "Azure Functions"
"Azure storage" => "Azure Storage"
"Azure app service" => "Azure App Service"

Update deploy.md

Update deploy.md

Minor edits
Co-authored-by: v-habibaumme<EMAIL_ADDRESS>Co-authored-by: v-ypalikila<EMAIL_ADDRESS>

[Doc Improvement][Revamp meeting extensibility public docs][2557380] (#6722)

revamp meeting extensibility

minor edits

minor edits

minor edits

minor edits

minor edits

minor edits

minor edits

minor edits

minor edits

minor edits

Update build-apps-for-teams-meeting.md

Update build-extensible-conversation-for-meeting-chat.md

minor edits

Update teams-apps-in-meetings.md

alt text update

minor edits

minor edits

minor edits

minor edits

minor edits

minor edits

minor edits

minor edits

minor edits

minor edits

minor edits

minor edits

minor edits

minor edits

minor edits

minor edits

minor edits

minor edits

minor edits

minor edits

minor edits

minor edits

minor edits

screenshot updates

minor edits

minor edits

minor edits

minor edits

minor edits

minor edits

minor edits

minor edits

minor edits

minor edits

minor edits

link update

minor edits

minor edits

review comments updated

minor edits

minor edits

minor edits

minor edits

review comments updated

review comments updated

minor edits

minor edits

minor edits

minor edits

minor edits

minor edits

minor edits

minor edits

minor edits

minor edits

Reorganize information for anonymous users

Remove unnecessary bullet point from Note

minor edits

minor edits

content added

minor edits

minor edits

minor edits

Co-authored-by: v-habibaumme<EMAIL_ADDRESS>Co-authored-by: Adrian Solis (TEAMS<EMAIL_ADDRESS>

[Doc Improvement][Broken link fixed and deep link to share stage content removed] (#7247)

link update and deep link content removed

Deep link content removed and broken link fixed

minor edits

Update .openpublishing.redirection.json

[Doc Improvement][Minor changes] (#7251)

space issue updated

minor edits

Update teams-toolkit-fundamentals.md (#7250)

Follow doc guidance and move image below text.
Co-authored-by: v-amprasad<EMAIL_ADDRESS>

Update overview.md

[Doc Improvement][Developer portal for GCC][2687666] (#7198)

GCC update

minor edits

minor edits

minor edits

minor edits

minor edits

minor edits

review comments updated

review comments updated

date update in whats new page

Update in-meeting-notification-for-meeting.md

Update .openpublishing.redirection.json

Update .openpublishing.redirection.json

Co-authored-by: Wajeed-msft<EMAIL_ADDRESS>Co-authored-by: rentu<EMAIL_ADDRESS>Co-authored-by: turenlong<EMAIL_ADDRESS>Co-authored-by: wenyutang-ms<EMAIL_ADDRESS>Co-authored-by: v-vpaliwal<EMAIL_ADDRESS>Co-authored-by: v-sdhakshina<EMAIL_ADDRESS>Co-authored-by: v-habibaumme<EMAIL_ADDRESS>Co-authored-by: v-silakshmi<EMAIL_ADDRESS>Co-authored-by: v-npaladugu<EMAIL_ADDRESS>Co-authored-by: v-sdhakshina<EMAIL_ADDRESS>Co-authored-by: v-ypalikila<EMAIL_ADDRESS>Co-authored-by: v-spharish<EMAIL_ADDRESS>Co-authored-by: v-ajiths<EMAIL_ADDRESS>Co-authored-by: v-ksar<EMAIL_ADDRESS>Co-authored-by: v-jganga<EMAIL_ADDRESS>Co-authored-by: Ajith kumar<EMAIL_ADDRESS>Co-authored-by: Erika Doyle Navara<EMAIL_ADDRESS>Co-authored-by: Ryan Bliss<EMAIL_ADDRESS>Co-authored-by: Corina<EMAIL_ADDRESS>Co-authored-by: v-abirade<EMAIL_ADDRESS>Co-authored-by: Michael Obajemu<EMAIL_ADDRESS>Co-authored-by: Rick Kirkham<EMAIL_ADDRESS>Co-authored-by: Haneen Mahdin<EMAIL_ADDRESS>Co-authored-by: summzhan<EMAIL_ADDRESS>Co-authored-by: Adrian Solis (TEAMS<EMAIL_ADDRESS>Co-authored-by: John Miller<EMAIL_ADDRESS>Co-authored-by: v-amprasad<EMAIL_ADDRESS>

Learn Build status updates of commit 9354dd4:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

For more details, please refer to the build report.
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.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel


add node parsing/encoding/decoding utils and tests

How was it fixed?
Add binary trie node parsing/encoding/decoding utilities and tests
Cute Animal Picture

added test cases with valid input
or they can be combined into one test case like

@pytest.mark.parametrize(
    'valid_node,invalid_node',
    (
        (b"\x02value", b"\x02"),
    ),
)
def test_binary_trie_node_parsing(valid_node, invalid_node)

for cleanliness

added constant node type prefix and change arrangement of returned data of parse_node

@pipermerriam test suites updated. Requesting a review. Thanks


fix(driver): block subsequent destroy calls instead of returning immediately

fixes: https://github.com/zwave-js/zwavejs2mqtt/issues/998
(hopefully)

@zwave-js-bot pack this


AUI-2072 Source Formating

@mairatma, I'm sending directly to you because @thiago-rocha have already checked the code.

Just started reviewing :) :octocat: Sent from GH.

Just started reviewing :) :octocat: Sent from GH.


Improve validators over input/output files

Files could have validators to check if it is:

[ ] correct file size
[ ] correct file extension

This may be related with #42


HAProxy Load Balancer Configuration

I have bamboo/haproxy deployed on a set of mesos worker nodes using Marathon.
What I can figure out is how to put a haproxy server in front of them as a load balanacer.
The one I have will forward onto a haproxy on the work node, but I keep getting 400 (bad request) errors, and I'm not sure if there is something I'm missing on the haproxy load balancer configuration. Does anyone have a example haproxy configuration file used as a load balancer that I could compare mine too?

@parker20121 @Zariel @rasputnik @MiLk @activars
I am getting the below error repeatedly while connecting to the URL. I have bamboo/haproxy deployed on a set of mesos worker nodes using Marathon. Any thoughts?
Lost connection to server at couchbase.xxx.com. Repeating in 1 seconds.
#curl -IS couchbase.xxx.com
HTTP/1.0 503 Service Unavailable
Cache-Control: no-cache
Connection: close
Content-Type: text/html

503 Service Unavailable

No server is available to handle this request.

Can you run curl in verbose mode?
Did it forward to the right machine? Looks like it can find the right port.

@parker20121 Here is the verbose mode output. When we it the URL on browser it is forwarding to the correct haproxy. The webpage loads, and I am able to login but within couple of seconds it throws out "503 Service Unavailable" error.
curl -vIS http://couchbase.xxx.com/index.html
* Hostname was NOT found in DNS cache
*   Trying xx.xxx.x.xx...
* Connected to couchbase.xxx.com (xx.xxx.x.xx) port 80 (#0)
> HEAD /index.html HTTP/1.1
> User-Agent: curl/7.37.1
> Host: couchbase.xxx.com
> Accept: */*
>
< HTTP/1.1 200 OK
HTTP/1.1 200 OK
* Server Couchbase Server is not blacklisted
< Server: Couchbase Server
Server: Couchbase Server
< Pragma: no-cache
Pragma: no-cache
< last-modified: Tue, 01 Dec 2015 17:06:47 GMT
last-modified: Tue, 01 Dec 2015 17:06:47 GMT
< Date: Sat, 16 Apr 2016 18:31:09 GMT
Date: Sat, 16 Apr 2016 18:31:09 GMT
< Content-Type: text/html; charset=utf8
Content-Type: text/html; charset=utf8
< Content-Length: 204441
Content-Length: 204441
< Cache-Control: must-revalidate
Cache-Control: must-revalidate
< Connection: close
Connection: close

I'm not a coachbase expert. After you login,  is it forwarding onto another machine through haproxy?


Implement result visualization

Will not be done, since we will focus on developing the nf-core/circrna pipeline


A (probably) known slur is still possible (kike)

While I don't want to come off as SJW/white knight, and am happy that three of the more well-known slurs are disallowed, there's still the word "kike" (ethnic slur used to refer to Jewish people). I just wanted to say it.
Note: Am not Jewish myself.

Thanks for bringing this to my attention! Trying to block every potentially hurtful word is of course a losing battle but I do like to catch them when I can. I'm reimplementing the Easter eggs for the new beta version now and I'll add it there.


Cite relevant codebases in JOSS paper

This is a quick issue relating to the JOSS review comments at: https://github.com/openjournals/joss-reviews/issues/5411#issuecomment-1548163405
I am not familiar with the literature on sleep-staging with ECG, but I do see there are one or two open source codebases that claim to enable ecg-based sleep staging. I wonder whether these should be briefly mentioned?
e.g. should comparisons be made to https://github.com/bdsp-core/ecg_respiration_sleep_staging? The repo doesn't look completely baked (e.g. "training_code_still_messy)", so perhaps it reinforces your point that "either the processing pipeline or the dataset used to generate the published results are not publicly available."

I agree with both points that we should probably mention related packages and that these are not as readily usable and as open as SleepECG. I don't want to start a discussion on the pros and cons of each package, so maybe briefly mention that there are other packages out there should be sufficient.
Do you have any additional packages that you found other than the one you mentioned?

I don't want to start a discussion on the pros and cons of each package, so maybe briefly mention that there are other packages out there should be sufficient.

I agree, just some quick pointers to existing repos would be enough.

Do you have any additional packages that you found other than the one you mentioned?

Like you say, there doesn't seem to be much around. The repos that I came across during a quick search included:

https://github.com/Acrophase/Sleep_Staging_KD
https://github.com/pickus91/ECG-Sleep-Stage-Classification
https://github.com/ojwalch/sleep_classifiers
https://github.com/bzhai/multimodal_sleep_stage_benchmark

I'll leave you to decide which of these are worth mentioning, if any!

I've mentioned all but the second one (which does not really contain anything substantial).


Add spotbugs and findsecbugs

Add spotbugs and findsecbugs to Stapler as part of the long, ongoing effort to improve static code analysis. Stapler didn't even have standard spotbugs configured so this PR contains findings relating to general items and to security.
I took it to the Medium level (threshold), which seems to be about right for Stapler. This corrects or points out areas that might be of concern but isn't getting too esoteric.
I suppose there could be an argument that it isn't worthwhile to make these improvements in Stapler, because it isn't in active development. But, we sure seem to make a lot of changes to Stapler. I find that having spotbugs helps us to avoid introducing yet more issues, such as further instances of the public, non-final flag. And it brings better awareness to areas that could be an issue or where we need to tread carefully. Therefore, I believe it is better to introduce this analysis to help better support future work.

@jvz @daniel-beck @Wadeck

Not really sure what to do about these two new findings that were introduced in the recently merged PR introducing a new cache. @jglick any ideas?

two new findings that were introduced in the recently merged PR introducing a new cache

Oh I see, new PATH_TRAVERSAL_INs to suppress (reading files from plugin code not users).

Builds fully again with another new suppression.

It seems the PR is already reviewed by two persons, so I do not plan to add another review.

Hmm ... it's passing locally. Let's see what a rebuild does.

Build is passing now.


SQL MAX function

A small article about SQL MAX function. The examples were based on the examples of sql-where-clause article.

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

Closed and Reopened this PR to attempt to resolve a specific Travis build failure.

Closed and Reopened this PR to attempt to resolve a specific Travis build failure.

Which is the build failure?


Make linalg easy again

DISCLAIMER : Any similarity to anyone's presidential campaign slogan is purely coincidental.
tl;dr:
(1) what the hell is going on
(2) now the days have changed
(3) get rid of that ugly {{...}} guy.
(4) It would be a great opportunity
Guys, me and @karlnapf had a discussion to clean up linalg lib a bit. Here are a few bits and pieces of that discussion

We have to stop supporting linalg back-end switch Shogun-wise. Earlier it seemed like a useful idea. But now it looks like a {{insert swear words}} feature to keep supporting. It's super easy to break the build with this because it's super easy to overlook the technical details that are involved to bring this feature alive.  And in reality, we hardly think that it would cater for any greater good for the lib.

We have to stop automatic type conversion from CPU-type to GPU-type in the linalg methods. The data transfer involves some cost, which, if hidden under the hood, can go unnoticed. The devs should know when they want a GPU type.

We have to separate hardware requirements (whether GPU is available or not) from software requirements (which third-party library is available). Earlier Eigen3 wasn't a hard requirement, so in designing libalg, we had to assume the possibility that Eigen3 is not there. But now the days have changed (2). It's time we rethink some of these stuffs. We may also give support for CUDA in future.

So, here are the plans for how we're gonna do it.

A user of linalg would ask a GPU factory for a GPU type (data transfer from CPU --> GPU happens here).

// cpu_type = SGMatrix<T> or SGVector<T>
// in future, maybe even SGSparseVector<T> and SGSparseMatrix<T>
auto gpu_type = linalg::GPUFactory::get_gpu_type(cpu_type);
auto result = linalg::foo(gpu_type);

This makes it explicit - the dev knows that there is a cost involved (we could make it more explicit by naming it pretty_please_put_data_on_gpu_if_possible_and_yes_I_know_it_is_costly(...)). Plus, it makes it easier to code for this thing. Plus it helps us to get rid of that ugly linalg::Backend::FOOBAR guy (3) at the time of calling. (if we want anything to be under the hood, it's this guy).

In the above example, we can consider the following cases:

GPU is available and ViennaCL is there (our default GPU lib) : returns a ViennaCL type
GPU is available and CUDA is there : returns a CUDA type (yet to be born in Shogun)
GPU is not available but ViennaCL is there : returns a ViennaCL type
GPU is not available and ViennaCL is not there : returns the same cpu_type.
GPU is available and ViennaCL and CUDA both are there : TODISCUSS

So, even in a platform where GPU/ViennaCL is not present, it doesn't break the build. It's like an advice to the algorithm: use GPU if there is any; otherwise, go on do your thing on CPU.

Now, a linalg dev would just have to write a bunch of overloaded methods (in a recent issue, we saw that the wrappers can slow it down). It would be a great opportunity (4) to encourage the devs to populate linalg with useful methods instead of scaring them off with template <template <class> class ....

We will still have a ViennaCL build. But that won't set the backend for all linalg methods in Shogun. It would just make the GPU-type as a VCL type, which would only be used wherever that factory is used. In short, it won't break anything.

We can also have a CUDA build in future, similar to ViennaCL build.

Here is a sample gist of how the factory thing should work. And this is how it is used.
Would love to hear comments from @lisitsyn @vigsterkr @besser82 @sonney2k @yorkerlin. I think this should be done quickly (I can do it myself), before we get too many patches for linalg. Thoughts?

Few more ideas, while we're at this:

If a shogun user has GPU, but wants to use CPU version instead (let's say, because the GPU is useless), there should be a cmake switch -DTURN_OFF_GPU or something. Essentially, this would just make the GPU factory to return a CPU type instead.
API should look cool. For normal operations, it would be just like I mentioned. But for element-wise, row-wise, col-wise, I'd love to have something like

linalg::elementwise(m).product(n);
linalg::elementwise(m).sin();
// NATIVE case handled here
linalg::elementwise(m).custom([](auto& v) { v = something_fun(v); });
// ViennaCL kernel case handled here
linalg::elementwise(gpu_m).custom("v = something_fun(v);");

// similar for rowwise and colwise.
linalg::colwise(m).sum();
linalg::colwise(m).custom(/* write a lambda for cpu/string for vcl */);

This has my strong +1

@lambday ok so can i ask a simple question: why do we need a yet another CUDA backend?

and btw all these things should be runtime optimized and not user wise optimized... it makes everything much more easier for the user.

CUDA backend? The idea is more to have linalg operations that are independent of the library used. So that the algorithm code is free from explicit library calls (CUDA/openCL/etc).  Imagine CUDA now does things much better than ViennaCL in the future -- then we can easily change without touching the algorithm code
I don't agree on doing CPU vs GPU under the hood. I was of your opinion before, but changed it after I saw what can happen.
This is extremely difficult to infer as it heavily depends on the use-case. We decided to make the GPU/CPU decision explicit to avoid the massive performance drops that we observed in benchmarks. Following the Python zen, muhahahah ;)

i completely disagree with you @karlnapf about being extremely difficult: magma does this pretty good.

statically compiling in a library options is so f**ing 90s ;) it's 2016 now, nobody wants to create 10 different compilation just because the lab has 10 different machines in the cluster. you want to have one blob (or blobs if we do shared libs fw one day) and that's what you wanna distribute among the machines in your cluster/lab/toasters

@vigsterkr I think we're again going back to the same question : should it be the user who decide to put the data on GPU or should it be the Shogun devs. This design that I proposed, it lets the devs take that decision, since what's happening under the hood is transparent from the user and the user usually won't have an idea of the impl details to take a good decision.
About that TURN_OFF_GPU thing, I think there can be another way to achieve this. You want a user to set that in a shogun program. So if I can make a POC for that to work, we should be good to go I guess :)

@lambday it should be neither.. it should be decided based on simplre rules.

@vigsterkr questions : (1) how good are those rules (2) how time/effort consuming would it be to implement those rules for shogun linalg, provided the limited (manpower) resources we have. Do we need to recreate the magic that magma does? (haven't checked that yet, but guessing that it has the answers for "what those rules should be")
If the devs decide to use GPU, it is usually a conscious/well-informed decision, based on benchmarking and testing.

and if the user is not happy, he can anyway turn GPU off with "turn_gpu_off" thing (let's assume that we come up a way to do that).

those conscious/well informed decisions are actually can be compiled into rules.
the rules are as good as the one who defines them :) (just to be an a**hole here, and i couldn't let this hanging).
the turn off gpu should be in worst case an env/config option, but not a compile time option

@vigsterkr let's use Shogun to learn those rules :D kidding

and the reasoning for doing semi-optimal solutions just because of less manpower i would assume never ended up in a nice place... and this (shogun) we all do (in our spare time) because we are for some magical reason enthusiastic about it (still)... doing a half/semi-optimal solution that you do because of feelings.... well that is just a broken dream.

@vigsterkr  let's talk about about the complexity of those rules - propositional? first-order? horn-clauses? please let me know if I should be looking at anything in particular inside magma.
about half/semi optimal solutions, well, it's always constrained optimization problem :) given the constraints, I believe we sometimes have to stick with those. but if a better alternative is out there that doesn't violate those constraints, I'd love to take the optimal path. and that's exactly why I wanted to hear from you on this issue. question is : how optimal are we talking about exactly, if we do the things the way magma does? can you give me a brief summary of how those rules should be? just to get an idea.

@vigsterkr we do quite a bit of GPU programming at my institute -- my opinion that it is hard to decide when/if/how to transfer data to the GPU comes from that. Also, there are quite a few papers out there where people specifically design (known) algorithms for GPUs. The architecture of the algorithms often fundamentally changes, and these changes cannot be inferred automatically in general, but only for a subset of simple design patterns. Being explicit, especially in the messy Shogun code, in my eyes therefore is better.
I agree with you on making something as good as possible, so happy to discuss. About compile/runtime -- we had very clearly speaking benchmarks on this iirc.

Done by @OXPHOS in GSoC16. Closing.


[VM] [Hexagon] Add buffers to dma_wait builtin

While introducing dma operations at graph level, relax KillAfterLastUse pass introduces kill_tensor operation after dma_copy. This leads to memory being deallocated when asynchronous copy operation is in progress. Hence, moving the input/output buffers to dma_wait to ensure kill_tensor is introduced after dma_wait at the graph level.
Also, the logic for size calculation is updated to use GetDataSize function.
The test case is updated to use offsets instead of allocating different storage in VTCM.

cc: @Hzfengsy @quic-sanirudh


feat: remove auto_publish from migration

Reason for Change

There is a preference to publish all migration revisions at once, after manual review by curators. This change cleans up migration code by removing the option to publish revisions as soon as one finishes migration, which also involved some logic to determine which types of collections should be allowed to auto-publish.

Changes

renamed all infra and functions referring to CollectionPublish or publish_and_cleanup to CollectionCleanup and log_errors_and_cleanup
removed can_publish / auto_publish parameters passed into SFN outputs or migration functions
removed logic in gather_collections relating to determining which collections can be auto published
renamed tests and test fixtures, and removed now unnecessary tests

Testing steps

unit tests + integration test

What else do you plan on adding?


tinycbor: Fix cmp return value from readers

cmp functions are used as IteratorFunc and expected behaviour is to
return non-zero value on success so the opposite of what memcmp-like
function do.

for reference, original implementation in tinycbor: https://github.com/intel/tinycbor/blob/master/src/cborparser.c#L1066


Data is being stored inefficiently

We are storing the data and other information as serialised strings. This has cascading effects with deletion etc. which mean multiple versions need to kept. This has meant that the database is growing extremely quickly, which probably isn't feasible when more users come on board. Need to replace with proper database schema via django.

It's actually not that bad, let me explain. Apologies for the wall-of-text.

Users create an analysis. This is stored in the Analysis model.

For every data type (transcriptomics, proteomics, metabolomics, reactions, pathways), an AnalysisData model is created.

An AnalysisData is linked to an Analysis .
Each AnalysisData also has a parent AnalysisData that it originates from (set to None if it's the first after uploading), as well as other fields like the data type (transcript, protein, metabolite etc), the inference type that creates it, metadata, timestamp etc.
Additionally the entire dataframe associated with this AnalysisData is stored in the json_data field in a serialised JSON format.

When users or system runs an inference, an entire new AnalysisData for that data type is created. Depending on the inference task, the new results can be stored either in the json_data (as part of the dataframe) or in the metadata field. For example, the t-test inference task stores the p-value and the fold-change in the dataframe, while clustergrammer stores the cluster info in the metadata.

By design each time a AnalysisData is created, we try to make sure that it contains all the data copied from the parent in the json field or in the metadata, PLUS any additional new data that we are adding. No information is lost as the latest AnalysisData contains everything we need. This is where data duplication happens.
On the front-end, only the latest AnalysisData is shown to the user.
Pros of this design: no joins (fast to retrieve), easy to undo inference (just by deleting one record in the db), easy to retrieve results for analysis outside in e.g. notebooks (just load the dataframe from the db).
Cons of this design: uses up a lot of storage if we are tracking all the histories.
Why not turn all these into a full relational data instead of just dumping the entire df into JSON? Because joins are slow, and the data never changes. I suppose we can create (database) views to speed things up, but that's still some work to assemble database query results into a dataframe for use in analysis.

A quick workaround that balances above pros/cons:

Don't store the big stuff (dataframe, metadata) in the parents, only store them in the latest AnalysisData.
Or we can simply get rid of this parent-child relationship in AnalysisData and retains only the last one. What do you think?

Here are the possible problems as I see them (they might not be actual problems when running):

We are repeatedly re-storing data after every inference. This will give us storage requirements in O(n^2), which is not feasible. I feel this definitely has to change in some way.
We are storing data in a non-efficient format, as serialised objects. I'm not sure what the overhead of this is, I'd have to look into it a bit more.
We are storing blobs of data in an RDBMS. For performance reasons, it might be more beneficial to store the blobs directly on the filesystem.

Quick question, what would happen if we wanted to delete an inference further back the chain. E.g. if there are 5 inferences and we want to delete number 2 and keep the rest, does the current model work okay?

Can we have AnalysisData simply store each inference and have everything merged when performing the view. If we guarantee that the order of items doesn't change, then it would be equivalent to concatenating columns which is very quick. We could also easily delete an inference.

Quick question, what would happen if we wanted to delete an inference further back the chain. E.g. if there are 5 inferences and we want to delete number 2 and keep the rest, does the current model work okay?

No. 2 will disappear from the list of past inferences (from the Inference tab). However its results are already carried forward as part of no. 3, 4 and 5.

Can we have AnalysisData simply store each inference and have everything merged when performing the view. If we guarantee that the order of items doesn't change, then it would be equivalent to concatenating columns which is very quick. We could also easily delete an inference.

I like this suggestion! Let's go with this 😀

It doesn't need to be a chain anymore though, it would be a set I think. Which makes maintenance of everything much easier.

Possibility to compress serialised objects? Don't know if this would store okay in database. Does sqlLite have a binary type?

There's a JSON extension for sqlite, but for backward compatibility, it still stores things as text anyway in the database.
At the moment, we're using this to store the JSON in a database-independent way.

Fixed in https://github.com/glasgowcompbio/WebOmics/pull/71

I think we really need the delete functionality. I'm going to have a look over things to see what's possible.

get_updated_json_data seems to merge results in json data. Is this very slow? If not, then this could work on the fly.

Will do some timing later to determine how fast get_updated_json_data runs (seems like it should be pretty fast?). That works for t-tests, limma, deseq.
For pathway stuff (PLAGE, ORA, GSEA), the equivalent of get_updated_json_data is update_pathway_analysis_data.
For Reactome analysis, the results are instead stored in the metadata field of the AnalysisData model (together with clustergrammer results, which is unchanged once it's initialised).
If we want to do this, I think we can still keep the base results (initial dataframe + metadata) in the json_data and metadata fields of AnalysisData. Then we store the individual inference results in the AnalysisHistory model. Finally we need a merge procedure that brings the base results + individual results together. I'll give that a try later.

Yes, instead of storing in AnalysisData after inference, we store in AnalysisHistory. Then at fetch, we iterate over inferences for species, pathways and Reactome and merge. Just a thought, currently the individual results are not jsonified, I guess this would have to happen to store in database - still should be quick to pull out and put in overall json_data.

Just wondering, why is the pathway stuff separate - is it because there is no idea of fold change?

It's because PALS produce output in a different format than what the other inference methods (e.g. t-test, limma) produce. Also yeah there's no fold change column in the PALS output.

Yes, instead of storing in AnalysisData after inference, we store in AnalysisHistory. Then at fetch, we iterate over inferences for species, pathways and Reactome and merge. Just a thought, currently the individual results are not jsonified, I guess this would have to happen to store in database - still should be quick to pull out and put in overall json_data.

Submitted a big pull request #74 for this


Merging in react components and exploratory API calls

Coverage decreased (-0.13%) to 91.33% when pulling 77ddf6c1bc040a5114adf436d91a50fecf646c32 on json-ld2 into c09eec0baf70076a79d24fb82ed34b0867a3d432 on master.


TechPowerUp.GPU-Z version 2.5.6

[ ] Have you signed the Contributor License Agreement?
[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] This PR only modifies one (1) manifest
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.5 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Wrong program version. Need to edit and resubmit.

Wrong program version. Need to edit and resubmit.


hex

Hi, let me suggest to make a build using mix for Elixir users, and register on http://hex.pm with bigdata tags.

Hi, I've no objections, what is need for that?

only to help elixir developers to find the avro lib easily. hex.pm is becoming a main point to search for libs

I know about hex.pm. I asked about what should I add to eavro to have it available on hex.pm?
Can you provide a pull request ?

:+1:

Hi, any chance you've been able to figure this out? I'm working on a library that depends on this one, and I'm currently not able to publish it with eavro listed as a dependency since it's not on Hex :(

Tried to do that, but faced with strange problem:
$ rebar3 hex publish
===> Verifying dependencies...
===> Can not publish package because the following deps are not available in hex: jsx, ranch, zlists

All these packages are in hex, but can't figure out what is wrong.
Do you have any idea?

@ates I think it has to do with your rebar.lock file. Since the dependencies are already resolved to github, it isn't even looking for them on hex. This issue seems to indicate that if you delete the lockfile and publish, it should (hopefully) work.

Thanks, now it's works, but got another problem with zlists package, I will contact maintainer of this packages to resolve issue

Done. https://hex.pm/packages/eavro


TFS new custom states.

Hi.
I create new statuses in my User Story WIT with transition update.
The problem is that, when i change status e.g. from "Active" to "New Custom Status" TFS will move this US to some kind of limbo. Also, at kanban table, when I add new column and try to map column to Status, there are only the old one :/
How make TFS to detect new statuses?

@Szczepanek - Thank you for your inquiry. I recommend you contact the Developer Community or Support.


examples are not included...

Joi.string().example("hapi-swagger")

Any update on this? I'd love for my response schemas to have example values in them.

+1

As of December 2015 the plug-in move over to v2 Swagger UI and now supports both example and default values. Swagger v2 does not display examples every where you think it could, but it is very good when displaying example output from an endpoint. Sorry it took so long to add this.


LogVariant

In api you can easily get/set stone variant using StoneVariant, but why there is no LogVariant for logs?

nvm, fount it - TreeType.


Bug ? Secret door spotting

Hi, I'm testing the invisible spotting feature and tried some things with a secret door and found out that :

The spotting range doesn't seem to work, token can spot the door with no range limit
The token respot the door at each movement (if the door is already spot it shouldn't respot it I think, and it has failed the passive check once it shouldn't give another chance for each square moved I guess)
The "spotted by" section is not filled with the name of the actor who has spot the door.
I'm using Foundry v11 315, last module version and Pf2e 5.12.3

I think i have identified the problem. What is your world setting "Apply ranges" set to? Should it be set to never that would explain the behaviour and the behaviour would almost be expected (except for the spamming the found message again and again part)

The bug should now be fixed with v3.1.14, assuming the above to be true. I will leave it open for now in case my assumption was wrong

Yeah I missed this setting, sorry, the range works fine now.
I made the update and found out some new things :

The message was not sent when the token spotted the door and the actor is not mentionned in the "spotted by" section
For each movement the door is "refreshed" for the token making it flashes (only when it has been spotted with passive perception, active perception works fine)
I guess the passive eprception it no rolled for each movement if it failed once, at least I tried to move a lot in a passive DC that I didn't pass the first time and never get it passed.
Is it intended that a spotted door is only visible within the spotting range even when already spotted ? The token who knows where the door is may be able to remember where it is even when leaving the spotting range (maybe as a setting ?)

Only tokens that have actively spotted a door are mentioned in the "Spotted by" section
The token refresh is a visual bug based on the way foundry renders the scene, i have not yet found a way to prevent it.
The door only being visible within the passive range, even when spotted actively is currently a limitation of the implementation, there is a way i could decouple it but that would come at somewhat of a performance hit. I am currently considering a way to rewrite it without costing performance but that will take a bit of time.

I remember arms reach I believe having the same issue with door flashing but I couldn't find back my issue at the time to see if it could help you.
For the spotted by, is that on purpose ? Is the button to reset spotted by supposed to hide the door again for everyone who spotted it ? Because when I tried it with a door spotted by passive the token could still see it so for ym tests I needed to delete and recreate a door

The "reset spotted by" button should make the door invisible to all tokens that have spotted the door via active rolls (assuming they can't spot the door via passive perception)

The door was passively spotted so I guess it's normal then, but that would be cool if both worked with passive spotting too
the passive perception is the main feature for me because it saves a lot of time in comparison with needing to place monk's active tile everywhere
so if that's not an issue but a feature request I guess this issue is completed, thanks for the quick fix

I was planning on improving the spotting for doors in a similar way anway, so i will add that to it. May take a week or two though

Secret doors will no longer become normal doors when clicked whille being spotted with v3.2.0 (unless the appropiate setting is activated)


Adding ability to overwrite the default processFn method with a custom one.

Summary
This PR allows a developer to define a custom processFn method to overwrite the default behaviour of inlining the policy into the head of the document we're currently processing.
Covers a request from https://github.com/slackhq/csp-html-webpack-plugin/pull/44, and an issue raised in https://github.com/slackhq/csp-html-webpack-plugin/issues/57
Implementation Details

Moved the current processing into a defaultProcessFn function, and made it the default behaviour so as to be backwards compatible.
Allowed the developer to overwrite this function with a custom function defined in either the CspHtmlWebpackPlugin additionalOpts object, or from the HtmlWebpackPlugin instance cspPlugin object. This can allow for different processing functions per HtmlWebpackPlugin instance
Added tests
Updated readme

Awesome! Thanks!

Nice! Give the people what they want! One little nit, but otherwise looks good. +1

I've now merged this and bumped the npm package version - thanks for the reviews!


"GETTING_STARTED.md" mismatch with the angular-cli@webpack

Bug, feature request, or proposal:
bug
What is the expected behavior?
What is the current behavior?
there is no "angular-cli-build.js" file in a latest angular-cli new project. so please update this file to  match it . it seems the pr #1002  does not working too
What are the steps to reproduce?
Providing a Plunker (or similar) is the best way to get the team to see your issue.
Plunker template: http://plnkr.co/edit/o077B6uEiiIgkC0S06dd
What is the use-case or motivation for changing an existing behavior?
Which versions of Angular, Material, OS, browsers are affected?
angular:  rc5
angular-cli: 1.0.0-beta.11-webpack.2
node: 5.12.0
os: darwin x64
material: ^2.0.0-alpha.7-2
Is there anything else we should know?

You can skip: Add components to vendor bundle andConfigure SystemJS from "GETTING_STARTED.md"
The only thing which I noticed is not working is Additional setup for md-menu and md-tooltip
Angular-cli webpack is just not creating a vendor for this. I don't have any idea how to fix this

@hansl can you make sure the getting started guide is good to go for alpha.8 + RC6 + webpack cli?

AFAIK the getting started should be totally up to date with angular-cli at this point.


dhcpcd: 10.0.3 -> 10.0.6

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/NetworkConfiguration/dhcpcd/releases.
meta.description for dhcpcd is: A client for the Dynamic Host Configuration Protocol (DHCP)
meta.homepage for dhcpcd is: https://roy.marples.name/projects/dhcpcd
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 10.0.6 with grep in /nix/store/880r5a5d0igq08qxy18051xf3gg3fd24-dhcpcd-10.0.6
found 10.0.6 in filename of file in /nix/store/880r5a5d0igq08qxy18051xf3gg3fd24-dhcpcd-10.0.6

Rebuild report (if merged into master) (click to expand)

1266 total rebuild path(s)

1266 package rebuild(s)

First fifty rebuilds by attrpath
CHOWTapeModel
ChowKick
CuboCore.coretoppings
abracadabra
activitywatch
adapta-gtk-theme
adwaita-qt6
aegisub
airgeddon
akkoma
albert
alfis
alice-tools-qt6
almanah
amule
amule-daemon
amule-gui
amule-web
anki
ao
apache-directory-studio
apostrophe
appgate-sdp
archi
asc
asn1editor
astroid
audacity
ausweisapp
autosuspend
aw-qt
aws-workspaces
ayatana-indicator-messages
badwolf
balsa
bambootracker-qt6
bambu-studio
beamerpresenter
beamerpresenter-mupdf
beamerpresenter-poppler
bespokesynth
bespokesynth-with-vst2
birdfont
bloom
blueberry
blueman
bochs
boinc
bookworm
bossa

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/880r5a5d0igq08qxy18051xf3gg3fd24-dhcpcd-10.0.6 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A dhcpcd https://github.com/r-ryantm/nixpkgs/archive/bc08997f00d1262b5a1cf2808d6cb046c4d0c4cb.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/bc08997f00d1262b5a1cf2808d6cb046c4d0c4cb#dhcpcd

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/880r5a5d0igq08qxy18051xf3gg3fd24-dhcpcd-10.0.6
ls -la /nix/store/880r5a5d0igq08qxy18051xf3gg3fd24-dhcpcd-10.0.6/bin

Pre-merge build results
NixPkgs review skipped

Maintainer pings
cc @edolstra for testing.

@ofborg eval


Update backup-support-matrix.md

When I google "Azure Backup vault supported services", this page is the first result I get. This section hasn't explained backup vault (it implies as if there is only ARS vault, but not backup vault) and this whole page barely mentions Backup vault. Also, for some reason, the FAQ which has answered the question, isn't among first google results. This is confusing to say the least. Every time I'm looking for difference between supported resources fort ARS vault vs Backup vault, I've to repeat this confusing and frustrating process. Also, it seems to me that difference and clarification between ARS vault vs Backup vault is a bit disjointed in some part of the documentation. Maybe because it's a new service? Anyway, I've added the following following reference to help readers navigate this process easier, and early on, can understand which vault is for what.

@AbhishekMallick-MS
Can you review the proposed changes?
Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

I sent an email to the content owner today.
@MicrosoftDocs/public-repo-pr-review-team

Hi @azarboon - thanks for sharing the update. I have added this update from my end to make minor changes, it will be live soon. As the doc updates are incorporated, closing this PR. #please-close


Make the readme badge round

Weren't you on vacations on Friday? This can clearly wait for your return, I'm sorry I wasn't clear on this.
Thanks for the review! I hope you are now disconnecting and you won't get this notification. :)


Should examples of logged strings be inside quotes?

Describe the Issue
Currently, the description for Step 5 states:
The console allows you to print and view JavaScript output. You can send information to the console using console.log(). For example, this code will print "Naomi" to the console:
let developer = "Naomi";
console.log(developer);

Affected Page
https://www.freecodecamp.org/learn/javascript-algorithms-and-data-structures-v8/learn-introductory-javascript-by-building-a-pyramid-generator/step-5
Your code

Expected behavior
The provided code will print Naomi without quotes to the console. Since this is part of the introductory Javascript course, some users might expect the quotes to be part of the print statement. To clarify, specify that it prints "Naomi" without the quotes or state it prints Naomi.
Screenshots
No response
System
N/A
Additional context
No response

We should probably remove the quotes from logged string values in examples. Seeing as the value that is logged does not have quotes.
We should use quoted strings for string values when asking for value assignments, or DOM string values (like attributes). Not for showing the output of console logs of strings. That is, unless it is logging a quoted value console.log('"test"').
I'm not sure how consistent we are now, but I suspect we are showing quoted values, at least it looks like it.

As an aside, the browser console uses syntax highlighting to distinguish between strings and numbers. It would be cool if our console did the same. It is handy that you can see if a value is a string or a number.

I changed the title, seeing as this isn't isolated to just this challenge step.

We can give more information like String has to be passed with single/double quotes then that will consider and print as a normal string or sequence of characters. The rest we can pass without quotes like Numbers and Booleans.

I would say there should not be quotes in descriptions like this.


Delayed trains are not in the order of arrival

When trains are delayed they might run in different order than their scheduled order. It would be more convenient to show them ordered by their actual predicted arrival time. See attached image

And, once again, huge thanks and props for this awesome service Ossi! <3

Personally I prefer that the trains do not swap positions on the listing, even if the estimated times made them arrive in a different order. So I am not sure which one is "the way" to go. Also worth noting: the current (scheduled time as the sorting criterion) also works when some trains are cancelled and don't have an estimate.

It is indeed nice that the cancelled trains are shown at the expected departure time on the list. Thus, for consistent user experience, it probably makes sense to have the delayed trains too like they are now. Maybe the "real-life expected departure time sorting" might work as a configuration option.
Anyways, I'm not disagreeing with you, so I'll close the issue. Thanks for commenting!


modify welcome message

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign kzwolenik95
You can assign the PR to them by writing /assign @kzwolenik95 in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[jx-info] Hi, we've detected that the pipelines in this repository are using a syntax that will soon be deprecated.
We'll continue to update you through PRs as we progress. Please check #8589 for further information.

@kzwolenik95: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

pr
8aab912719e83cfe5630329fb1661d7bf0f30ecc
link
/test pr

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

/test pr

@kzwolenik95: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

pr
8aab912719e83cfe5630329fb1661d7bf0f30ecc
link
/test pr

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

/test pr

:star: PR built and available in a preview jx-integrated-jenkinsx-node-lab-pr-1 here

:star: PR built and available in a preview jx-integrated-jenkinsx-node-lab-pr-1 here

/approve

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: kzwolenik95
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [kzwolenik95]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Add Render Template API

Closes #6046
Checklist

[x] By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and subject to the Developers Certificate of Origin.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@rursprung: Let me know if you want any additional information that isn't capture in this PR.

@msfroh: Mind looking at this one?

This PR passed tech review offline.

A couple of nits. Question: Should we group the search APIs under a "Search API" category?

Yes. However, should we wait until we have a method for canonical links first?

A couple of nits. Question: Should we group the search APIs under a "Search API" category?

Yes. However, should we wait until we have a method for canonical links first?

I think this is ok since there is no change to a collection or permalink, but let's check with @kolchfa-aws.

@Naarcha-AWS @hdhalter Go ahead with all the changes (and let me know what they are) until I implement this. It is easier to make all the changes beforehand. Thanks.


Segmentation fault on CentOS 7.6

Hi,
OS: CentOS Linux release 7.6.1810 (Core)
I'm able to successfully build from git source (as per https://github.com/davehorton/drachtio-server), and have downloaded the example config file (https://github.com/davehorton/drachtio-server/blob/master/drachtio.conf.xml).
When I run drachtio (installed to /usr/local/bin/) with this example config file (saved to /etc/ without any changes) I get a "Segmentation fault":
# drachtio
Segmentation fault

I get the following in /var/log/messages:
segfault at 0 ip<PHONE_NUMBER>47c0c4 sp 00007ffd4ffd50f0 error 4 in drachtio[400000+23f000]

Any advice on how to troubleshoot this?

gcc --version
gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-36)
Copyright (C) 2015 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Sorry, only just realised that https://github.com/davehorton/drachtio-server/issues/69 is basically the same issue.
I upgrade gcc to 4.9 - as per https://stackoverflow.com/questions/47175706/how-to-install-gcc-4-9-2-on-rhel-7-4
yum install centos-release-scl-rh
yum install devtoolset-3-gcc devtoolset-3-gcc-c++
update-alternatives --install /usr/bin/gcc-4.9 gcc-4.9 /opt/rh/devtoolset-3/root/usr/bin/gcc 10
update-alternatives --install /usr/bin/g++-4.9 g++-4.9 /opt/rh/devtoolset-3/root/usr/bin/g++ 10

and
scl enable devtoolset-3 bash

Compiled drachtio from scratch again and this time there is no segmentation fault when running it.

Hi,
I've tried Drachtio locally with docker and then on Digital Ocean, in a Debian VM, installing Drachtio from source, following the instructions you provided in Drachtio site. Everything works fine and my PoC is finished. It's now time to start developing real apps.
Afterward I've installed Drachtio server on our development environment. We use CentOS 7 and during the installation a lot of issues appeared and it's getting harder to resolve.
In the last try I've compiled it with gcc 4.9.2 (installed from source) but when I tried to start Drachtio I always get a segmentation fault:
[alex@sbc02 ~]$ drachtio
Segmentation fault (core dumped)

The Drachtio logs are:
2020-05-14 17:45:16.286683 Starting drachtio version v0.8.4-10-g0738b0b
2020-05-14 17:45:16.286763 Logging threshold:                     4
2020-05-14 17:45:16.286783 DrachtioController::run listening for applications on tcp port 9022 and tls port 0
2020-05-14 17:45:16.287075 responding to Prometheus on <IP_ADDRESS>:8088

There aren't any logs in /var/log/messages related to Drachtio server.
Any advice?

It does sound suspiciously like that issue with gcc support of regex to me....can you run it in gdb and get a stack trace?

Hi @davehorton,
In my last comment I wrote that I had already compiled Drachtio with gcc 4.9, but I just realised  that the old gcc hasn't been replaced.
I compiled it again, this time with gcc 4.9.4
[alex@sbc02 ~]$ gcc --version
gcc (GCC) 4.9.4
Copyright (C) 2015 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Here is the output of the gdb command:
[root@sbc02 build]# gdb /usr/local/bin/drachtio
GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-115.el7
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/local/bin/drachtio...done.
(gdb) r
Starting program: /usr/local/bin/drachtio
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
warning: File "/usr/local/lib64/libstdc++.so.6.0.20-gdb.py" auto-loading has been declined by your `auto-load safe-path' set to "$debugdir:$datadir/auto-load:/usr/bin/mono-gdb.py".
To enable execution of this file add
	add-auto-load-safe-path /usr/local/lib64/libstdc++.so.6.0.20-gdb.py
line to your configuration file "/root/.gdbinit".
To completely disable this security protection add
	set auto-load safe-path /
line to your configuration file "/root/.gdbinit".
For more information about this security protection see the
"Auto-loading safe path" section in the GDB manual.  E.g., run from the shell:
	info "(gdb)Auto-loading safe path"

Program received signal SIGSEGV, Segmentation fault.
0x0000000000488804 in drachtio::parseSipUri (uri=..., scheme=..., userpart=..., hostpart=..., port=..., params=...)
    at ../src/drachtio.cpp:276
276	            DR_LOG(log_error) << "parseSipUri - regex error: " << e.what();
Missing separate debuginfos, use: debuginfo-install cyrus-sasl-lib-2.1.26-23.el7.x86_64 glibc-2.17-292.el7.x86_64 keyutils-libs-1.5.8-3.el7.x86_64 krb5-libs-1.15.1-37.el7_7.2.x86_64 libcom_err-1.42.9-16.el7.x86_64 libcurl-7.29.0-54.el7.x86_64 libidn-1.28-4.el7.x86_64 libselinux-2.5-14.1.el7.x86_64 libssh2-1.8.0-3.el7.x86_64 nspr-4.21.0-1.el7.x86_64 nss-3.44.0-4.el7.x86_64 nss-softokn-freebl-3.44.0-5.el7.x86_64 nss-util-3.44.0-3.el7.x86_64 openldap-2.4.44-21.el7_6.x86_64 openssl-libs-1.0.2k-19.el7.x86_64 pcre-8.32-17.el7.x86_64 zlib-1.2.7-18.el7.x86_64
(gdb)

As far as I can understand, your suspect about the regex is right. I don't see a full stack trace, only this ../src/drachtio.cpp:276.
Do you want me to try anything else?

Hi @davehorton ,
I am facing same issue as above while installing Drachito server. Can you please let me know what can I try to resolve this issue. I am trying to install on CentOS 7 too.
[root@dev-fs-ho-001.uci.comcast.com:/usr/local/src/drachtio-server/build]# gdb /usr/local/bin/drachtio
GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-120.el7
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/...
Reading symbols from /usr/local/bin/drachtio...done.
(gdb) r
Starting program: /usr/local/bin/drachtio
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Program received signal SIGSEGV, Segmentation fault.
0x000000000048bf74 in drachtio::parseSipUri (uri="sip:<IP_ADDRESS>;transport=udp,tcp",
scheme="", userpart="", hostpart="", port="",
params=std::vector of length 0, capacity 0) at ../src/drachtio.cpp:276
276	            DR_LOG(log_error) << "parseSipUri - regex error: " << e.what();
Missing separate debuginfos, use: debuginfo-install cyrus-sasl-lib-2.1.26-23.el7.x86_64 glibc-2.17-326.el7_9.x86_64 keyutils-libs-1.5.8-3.el7.x86_64 krb5-libs-1.15.1-55.el7_9.x86_64 libcom_err-1.42.9-19.el7.x86_64 libcurl-7.29.0-59.el7_9.1.x86_64 libgcc-4.8.5-44.el7.x86_64 libidn-1.28-4.el7.x86_64 libselinux-2.5-15.el7.x86_64 libssh2-1.8.0-4.el7.x86_64 libstdc++-4.8.5-44.el7.x86_64 nspr-4.19.0-1.el7_5.x86_64 nss-3.36.0-7.1.el7_6.x86_64 nss-softokn-freebl-3.36.0-5.el7_5.x86_64 nss-util-3.36.0-1.1.el7_6.x86_64 openldap-2.4.44-21.el7_6.x86_64 openssl-libs-1.0.2k-25.el7_9.x86_64 pcre-8.32-17.el7.x86_64 zlib-1.2.7-20.el7_9.x86_64

what version of gcc are you running?  I really cant provide much support for centos as I do not use it myself

Its 4.8.5
gcc --version
gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-44)
Copyright (C) 2015 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE

ok well you can see from this thread that is your problem.  Upgrade to 4.9 or above.


NaN Region Data for guilds

This is referring to the string produced by Guild.region
It was reported to me today by one of my bots EU users that their server region reports as "NaN"
This is whats known:
Only reported so far on eu-central servers Edit: (Now getting reports of it happening to all regions)
Newly created or region changed servers report region correctly, but after some time region data changes to NaN.
If a NaN  server changes their discord region to something else, and back again the region now reports correctly for some time. After a short while the server becomes NaN again.
Further details:

discord.js version: 11.1 Master

node.js version: 7.11.00

Operating system: Server 2012 / Windows 10

Priority this issue should have – please be realistic and elaborate if possible: This issue should be medium / high. In my usage region data is used heavily to determain scheduled event times, and weekly Database updates. (EU vs NA)

[ ] I have also tested the issue on latest master, commit hash:
--note have not tested absolute latest commit yet, im about 2 days behind. _ will test when my EU-Central test server changes back to NaN

i'm not sure why it would be NaN but server regions sometimes get borked

ok so here's the deal. this is a discord issue, but we can technically abstract it away BUT i'm going to need you @gmedeadlystrike to do some console.loging  and tell us what data gets passed in the Guild#patch method when the region goes to NaN
node_modules/discord.js/src/structures/Guild.js in the patch method add a console.log for data.region and then report back after you get some data

@gmedeadlystrike any update on that?

@iCrawl - I have not seen this issue pop up sense


Starter Kit installer doesn't enable correct framework

Note: I clicked the GitHub button on the Astro docs install page and blindly posted this bug here in docs. It should probably be moved to the correct place. Sorry.
Description
It seems like the installer isn't actually adding the correct JS framework for the generic starter.
Versions
<EMAIL_ADDRESS>Node v17.3.0
pnpm 6.32.9
Steps to Reproduce

pnpm create astro@latest
Create app directory: ./test
Select Starter Kit (Generic)
Select Solid.js
Install pnpm: Y
Run pnpm dev

Observe that Solid isn't installed in package.json nore is the astro.config.mjs file setup with the correct package.
I'm able to reproduce the same issue for React and the other frameworks.

Maybe it's because you're using npm and I'm using pnpm?

Once I pass that step and setup Solid integration manually I get a further error (which I could post separately but seems related):
Failed to resolve force included dependency: solid-js
9:42:19 p.m. [vite] Error when evaluating SSR module @astrojs/solid-js/server.js:
Error: Cannot find module 'solid-js/web' imported from

pnpm still seems to work for me? Do you see anything here?

Nope, you know what this is a none issue. This is what happens when we don't read instructions. lol.
So I was installing with NO frameworks to begin with and didn't even realise it.
Can I suggest a step be added after selecting the framework? If a user doesn't specify from the list perhaps catch them before they continue? ie. We noticed you didn't add a framework, would you like to continue? (If you selected a framework make sure you use space bar to actually selected it).
I think this is the type of interaction where the user feels confident enough to just pick and go without actually reading the copy. It tripped me up a bit and could be easily resolved.

I'll make a note! It's already on my list to update the instructions re: the create-astro walk through because this wizard has changed a little since the current docs were written. So, I'll be SURE to make it clear what to do in docs... and I'll ping engineering about the wizard itself.

I'm closing this issue because the next page on my list to rewrite is the instructions following create-astro, since the wizard has just been updated with new steps! So, I will keep this in mind as I document the process. Thanks again for your suggestions!


Formula params enhancement

This PR will implement the imaginary part of the power in fractal formula.
The detailed implementation described in words in #31 issue.
This PR will solve the issue:

[x] #31

Closing this as we will add some enhancement in the GreatWall implementation and then how to use it to generate fractal.


Converse: Strengthen locking in node reductions

It is possible for node reduction messages to arrive at the root before
it has completed its own CmiNodeReduce* call. Therefore, lock around
all accesses of _nodereduce_info.

This is needed to fix autobuild.

I set autobuild to run on this branch and issues seen previously are resolved.

Something went wrong with LGTM, like it didn't receive any notification from GitHub when I updated the branch from the web interface, and it's blocking the merge. I can't find anything to help with this on lgtm.com.

Something went wrong with LGTM, like it didn't receive any notification from GitHub when I updated the branch from the web interface, and it's blocking the merge. I can't find anything to help with this on lgtm.com.

I made LGTM optional for now.


拉取原作者最新代码

Please make sure these boxes are checked before submitting your PR, thank you!

[ ] Make sure you follow Element's contributing guide (中文 | English | Español | Français).
[ ] Make sure you are merging your commits to dev branch.
[ ] Add some descriptions and refer relative issues for you PR.

拉取原作者最新代码

拉取原作者最新代码


Support PortalEntry display priorities

I use the portal to implement a widget that is displayed only when hovering, and when I right-click on the widget I need to display the context menu, but the context menu is displayed at a level below the hovering widget.
I would like to be able to configure the priority.

Sounds like duplicate of https://github.com/rrousselGit/flutter_portal/issues/39


using state class 'measurement' which is impossible considering device class ('monetary')

Hi Jacco: FYI.
Logger: homeassistant.components.sensor
Source: components/sensor/init.py:570
integration: Sensor (documentation, issues)
First occurred: May 19, 2024 at 10:40:52 PM (10 occurrences)
Last logged: May 19, 2024 at 10:40:53 PM
Entity sensor.entso_highest_energy_price_today (<class 'custom_components.entsoe.sensor.EntsoeSensor'>) is using state class 'measurement' which is impossible considering device class ('monetary') it is using; expected None or one of 'total'; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/JaccoR/hass-entso-e/issues
Entity sensor.entso_average_electricity_price_today (<class 'custom_components.entsoe.sensor.EntsoeSensor'>) is using state class 'measurement' which is impossible considering device class ('monetary') it is using; expected None or one of 'total'; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/JaccoR/hass-entso-e/issues
Entity sensor.entso_current_percentage_of_highest_electricity_price_today (<class 'custom_components.entsoe.sensor.EntsoeSensor'>) is using state class 'measurement' which is impossible considering device class ('monetary') it is using; expected None or one of 'total'; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/JaccoR/hass-entso-e/issues
Entity sensor.entso_time_of_highest_price_today (<class 'custom_components.entsoe.sensor.EntsoeSensor'>) is using state class 'measurement' which is impossible considering device class ('timestamp') it is using; expected None; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/JaccoR/hass-entso-e/issues
Entity sensor.entso_time_of_lowest_price_today (<class 'custom_components.entsoe.sensor.EntsoeSensor'>) is using state class 'measurement' which is impossible considering device class ('timestamp') it is using; expected None; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/JaccoR/hass-entso-e/issues

Seeing the same thing here since yesterday.
2024-06-08 10:28:17.342 DEBUG (MainThread) [custom_components.entsoe.coordinator] Fetching ENTSO-e data
2024-06-08 10:28:17.342 DEBUG (MainThread) [custom_components.entsoe.coordinator] NL
2024-06-08 10:28:18.210 DEBUG (MainThread) [custom_components.entsoe.coordinator] Finished fetching ENTSO-e coordinator data in 0.869 seconds (success: True)
2024-06-08 10:28:18.216 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.entso_current_electricity_market_price (<class 'custom_components.entsoe.sensor.EntsoeSensor'>) is using state class 'measurement' which is impossible considering device class ('monetary') it is using; expected None or one of 'total'; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/JaccoR/hass-entso-e/issues
2024-06-08 10:28:18.223 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.entso_next_hour_electricity_market_price (<class 'custom_components.entsoe.sensor.EntsoeSensor'>) is using state class 'measurement' which is impossible considering device class ('monetary') it is using; expected None or one of 'total'; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/JaccoR/hass-entso-e/issues
2024-06-08 10:28:18.229 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.entso_lowest_energy_price_today (<class 'custom_components.entsoe.sensor.EntsoeSensor'>) is using state class 'measurement' which is impossible considering device class ('monetary') it is using; expected None or one of 'total'; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/JaccoR/hass-entso-e/issues
2024-06-08 10:28:18.234 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.entso_highest_energy_price_today (<class 'custom_components.entsoe.sensor.EntsoeSensor'>) is using state class 'measurement' which is impossible considering device class ('monetary') it is using; expected None or one of 'total'; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/JaccoR/hass-entso-e/issues
2024-06-08 10:28:18.273 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.entso_average_electricity_price_today (<class 'custom_components.entsoe.sensor.EntsoeSensor'>) is using state class 'measurement' which is impossible considering device class ('monetary') it is using; expected None or one of 'total'; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/JaccoR/hass-entso-e/issues
2024-06-08 10:28:18.282 WARNING (MainThread) [custom_components.entsoe.sensor] Unable to update entity due to data processing error: None and error: min() iterable argument is empty
2024-06-08 10:28:18.283 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.entso_current_percentage_of_highest_electricity_price_today (<class 'custom_components.entsoe.sensor.EntsoeSensor'>) is using state class 'measurement' which is impossible considering device class ('monetary') it is using; expected None or one of 'total'; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/JaccoR/hass-entso-e/issues
2024-06-08 10:28:18.294 WARNING (MainThread) [custom_components.entsoe.sensor] Unable to update entity due to data processing error: None and error: min() iterable argument is empty
2024-06-08 10:28:18.294 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.entso_time_of_highest_price_today (<class 'custom_components.entsoe.sensor.EntsoeSensor'>) is using state class 'measurement' which is impossible considering device class ('timestamp') it is using; expected None; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/JaccoR/hass-entso-e/issues
2024-06-08 10:28:18.303 WARNING (MainThread) [custom_components.entsoe.sensor] Unable to update entity due to data processing error: None and error: min() iterable argument is empty
2024-06-08 10:28:18.303 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.entso_time_of_lowest_price_today (<class 'custom_components.entsoe.sensor.EntsoeSensor'>) is using state class 'measurement' which is impossible considering device class ('timestamp') it is using; expected None; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/JaccoR/hass-entso-e/issues

Yesterday there was indeed no data to be had so it makes sense that the entities would be empty, but as of an hour ago the platform has filled in the missing data and we now do get the correct prices, so the entities should be properly populated again.

I figured out a workaround:
the file config/.storage/core.restore_state contains all the old values for the entso integration.
Removing all the objects that mention the current entso-e sensors while HA is stopped makes the integration work again.
It is important that HA is not running at the time, or it will reinsert your removed entities again on the next reboot.

It is important that HA is not running at the time, or it will reinsert your removed entities again on the next reboot.

Weird question, but how do you manage to do that? Is there a way to shutdown HA while still being able to edit files? I'm logged in through SSH but I don't see an option to shutdown HA while not shutting down the system

@DutchessNicole  and @Fidelity88  thanks both. this solved it for me.

I use SSH as well, and in the HA command line you can just issue the ha core stop command to stop the HA core container. Then you can edit the files, since SSH will still run.

Thanks, this fixed it for me too.

I use SSH as well, and in the HA command line you can just issue the ha core stop command to stop the HA core container. Then you can edit the files, since SSH will still run.

Thanks this worked for me!
A Pointer to others struggling with this:
I only needed to remove the object that is used in the graphs, which in my case was called sensor.[whatever name you use for your ensoe config]_average_electricity_price_today. It included all the old today and tomorrow prices (all nested in this object).
All other objects with sensor.[whatever name you use for your ensoe config]_* I did not remove.
After a restart ha core start the prices and graphs came back to life, almost immediately.
It would be nice if the cause of this was fixed.

Thanks! This is an excellent procedure. Only removing the object _average_electricity_price_today and leaving all other entsoe objects intact worked for me as well.
Agree that a true fix is still required.

v0.4.0 is released this version contains fixes that solve a lot of warnings and known issues. This issue is probably also solved.
Please update to the latest version.
Closing this issue for now. If you still have issue please feel free to open a new issue.


Provide a way to skip the templating for torrc

Added the new SKIP_TEMPLATE environment variable: when set to any value, the templating of the torrc file will be skipped by the wrapper script and the /etc/tor/torrc file will be used verbatim (either the default one coming from the Tor project or one mounted by the user).

Resolves #163


SelectList can not use list_name= while using Materializecss select dropdown

Hi Cheezy,
I am using Materializecss for my web, and I have a select dropdown list whose options are added by jQuery. I can print out the options text using list_name_options, however, I don't know why I can't set the selected value using list_name=.

The list_name= setter will only work with native select elements. From what I can tell from the demo site (https://materializecss.com/select.html), the default is not a native select. It's actually a text field with ul/lis.
You'll need to interact with the user visible fields - eg:

Type into the text field
Click the span with matching text

If you need help with doing this, please let me know.


webhook format for GraphQL fields

Overview
For webhooks created via GraphQL, webhook data is still in REST format instead of
https://shopify.dev/api/admin-graphql/2022-04/objects/Product#fields
eg product has created_at instead of createdAt, body_html instead of descriptionHtml, no media list (but has images)
Proposal: have a new format at WebhookSubscriptionFormat
such as JSON_GRAPHQL, which will send webhooks data in format matching
https://shopify.dev/api/admin-graphql/2022-04/objects/Product#fields
Type

[ ] New feature
[x] Changes to existing features

Motivation

What inspired this feature request? What problems were you facing?

Using GraphQL and being consistent in handling data
Area

[ ] Add any relevant Area: <area> labels to this issue

Checklist

[x] I have described this feature request in a way that is actionable (if possible)

when do we expect this issue will be resolved? I need a media list on the webhook

Hi! I see this issue is quite old. Was anyone able to figure this out? I'm using graphQl to generate my pages using NextJS. However, when I trigger a webhook revalidation, the returned key for decription is description_html and not descriptionHtml like it is in graphQl. How can I handle this in my code?


Add additional_build_args to docker build command

In the docker build line https://github.com/seek-oss/docker-ecr-publish-buildkite-plugin/blob/master/hooks/command#L131
It would be very useful to copy the great idea used in the cache plugin to specify additional arguments to docker build, see https://github.com/seek-oss/docker-ecr-cache-buildkite-plugin/blob/master/hooks/pre-command#L196
The main use case is passing --progress=plain for setting DOCKER_BUILDKIT=1 (see https://docs.docker.com/develop/develop-images/build_enhancements/#new-docker-build-command-line-build-output)

I would appreciate any feedback or comments on #17

Blocked by #18 unfortunately

Published as v1.4.0


Rename temperature metric

Fix a typo in temperature metric name and conform to standards set by official Prometheus exporters by shortening temperature to temp.
bsbmp_temperature_celcius -> bsbmp_temp_celsius
One can't mistake temp (temperature) for temporary as there is celsius in metric name.
Resolves #15

LGTM, Thanks.


perf problems with require.context

@sokra this issue is very much alive in webpack5 and also affects dynamic require() and import() calls. I created another repro, although probably @ericpitcher's is just as good: https://github.com/tmeasday-shopify/webpack-require-context-repro
We are very interested about this for Storybook in large code bases because we rely on require.context() or some other globbing mechanism to import story files.
Would you like me to open a new ticket or can this ticket be reopened?
Originally posted by @tmeasday in https://github.com/webpack/webpack/issues/6093#issuecomment-868293507

@tmeasday yep, I think we have critical bug here

Thanks @alexander-akait. Happy to help with a solution once the path forward is known.

Yes, problems in that we need scan whole directory (include nested) for each build, otherwise we can't catch new/deleted files...

This problem was already solved several years ago in the Jest, and jest-haste-map was made especially for this. It would be great to use it for such cases, but the problem is that it is not well documented.

Anyone have any ideas on this? It takes literally minutes to reload an app that has 4000 small images :(


Minor README.md update

Minor update to one of the commands in the README which pulled a fragment from the previous command.

Thanks @akhilravidas :)


Make other language support more obvious

This tool is correctly advertised as working for all languages but out of the box works only with Japanese and it's not obvious how to use it for other languages. This will make the tool more accessible to all language learners. Suggested changes:

Add an option to UI settings to select a language for OCR

OR

Add documentation to make it more obvious how the user can do the same manually. Here's my attempt:
In config.ini, change values according to https://tesseract-ocr.github.io/tessdoc/Data-Files-in-different-versions.html and replace them in these lines

tesseract_language = jpn
ocr_space_language = jpn

Download XYZ.traineddata for your language from https://github.com/tesseract-ocr/tessdata_best/ (OR https://github.com/tesseract-ocr/tessdata) and put it in the game2text\resources\bin\win\tesseract\tessdata folder

How does one actually use it for other languages?

@drewboardman You should be able to follow the instructions in my comment above (after Here's my attempt: part). This worked for me with non-Japanese language at the time of writing the comment


Use static export from next.js

The is more of a security issues because next.js exposes various useless endpoints. When we export , the assets page is not working anymore. For some reason next.js wants to create all the page urls from the beginning so /asset/{did} is not working.

Closing, next.js doesn't really support our need


Fixed Storybook configuration for add-ons

As promised in #2890, this is our configuration to use storybook in add-ons. It works in a project that is a few months old, can't remember the exact version but I can explore it further if this doesn't work.
I am creating this as a Draft for now, even if it could be final, because it needs a few tests with the generator that I can't do today.

Tried it out, works like a charm... @pnicolli Thanks a lot for sharing!


how can i make it work with display:flex?

Hey,
i have some issues with lazy loading within a display:flex container.
Here is the modified example code:
index.jsx
`import React, { Component } from 'react';
import LazyLoad from 'react-lazy-load';
import './style.css'
class Application extends Component {
render() {
return (

{'sdf'}

Scroll to load images.

{'sdf'}

);
}
}
export default Application;
`
template.ejs:
`

React Lazy Load basic example

`
Does anyone have some experience with this?
Thanks in advance.
PS: how can i make the code look like code? :)

The way I did it is that I had a container div with the wrapped lazy loaded components inside. This container has the flex css (display: flex, etc.). Then I overwrote the display css for the .LazyLoad class to display: inline-block (instead of display: block for divs). My components wrapped in the LazyLoad component have the flex styling flex: 1. Let me know if that helps!

This should now work properly since I switched over to IntersectionObserver. The example includes a flex example with horizonta loading.


ModuleNotFoundError: No module named 'special_characters'

I absolutely love what you are trying to achieve here. I'm pretty much in need of the same thing. Especially your support of embedded content [[like this]] is amazing.
However, executing converter.py just gives me:
Straightforward-Obsidian2Latex-main\src\embedded_notes.py", line 11, in <module>
    from special_characters import *
ModuleNotFoundError: No module named 'special_characters'

I assume you're missing a file "special_characters.py" in your main branch?

Hello!
Thank you for your appreciation! Exactly, this is one of the main reasons I created this repo!
Yes, you are right, there was an issue with this file and it was not in the branch, now it is.
I have made a few additions those last few days, so I need to update the example vault (the code is updated).


ui-grid: Fixed row getters in selection API.

See: http://ui-grid.info/docs/#/api/ui.grid.selection.api:PublicApi
getSelectedGridRows should return uiGrid.IGridRow, not the uiGrid.selection.IGridRow interface which only has the selection-specific properties.
getSelectedRows returns the selected entities, not grid rows.
Also, IGridInstance.scrollTo takes an object in the gridOptions.data array as parameter, not an IGridRow. Both parameters are optional. See https://github.com/angular-ui/ui-grid/blob/a42dab24532fb896725b9fc8359e4526e436c891/src/js/core/factories/Grid.js#L2419-L2440

ui-grid/ui-grid.d.ts
to author(@btesser). could you review this PR?
:+1: or :-1:?
check list

[ ] pass the Travic-CI test?

@baltie Thanks for the submission.
@vvakame LGTM

@vvakame  @baltie Looks good except for 1 very minor change.  In the tests we are using the convention of single quotes not double quotes.  Change that and this PR can be merged as far as I'm concerned

Thanks for the feedback, @btesser. I've changed the quotes to single quotes.

@vvakame @baltie Thanks.  Everything looks good now

@btesser thanks!
@baltie thanks mate!

Thanks @vvakame! :)