Update FreeCEN Handbook on line and add sample completed spreadsheet.

I have sent Anne 2 files.
One is an updated version of the March Handbook. It has an extra paragraph which addresses a new transcribers query.
The second is a csv spreadsheet for 1881. It is a sample that new transcribers can look at to see how their spreadsheet should look. It does not have an existing link in the Handbook section of Your Actions, so that will need to be created.
Geoff

HI @geoffj-FUG if you tell me the text and position, I'll add it (with the link to the spreadsheet).

Info sent by email

I now have a rewrite of the web page and 2 additional parts of the Handbook to upload as well. Will send in the next few days.
Geoff

This is now with @PatReynolds for upload

If this is reassigned in the handover, ask Geoff to re-send the handbook to whoever get it.

@geoffj-FUG to send bundle to Denise

Text is now ready for proofing on Test3.  Please notes, links have not yet been made on the document.  Cou,d you proof, please, @geoffj-FUG

Links are now live.

Pat
The version on test3 is an older version. It is the one that I updated again.
The set we need to upload has the attached document as the text.  The associated documents will be dated June 2022.
Geoff
From: PatReynolds @.>
Sent: Wednesday, 10 August 2022 10:12 PM
To: FreeUKGen/FreeCENMigration @.>
Cc: geoffj-FUG @.>; Mention @.>
Subject: Re: [FreeUKGen/FreeCENMigration] Update FreeCEN Handbook on line and add sample completed spreadsheet. (Issue #1427)
Text is now ready for proofing on Test3. Please notes, links have not yet been made on the document. Cou,d you proof, please, @geoffj-FUG https://github.com/geoffj-FUG
—
Reply to this email directly, view it on GitHub https://github.com/FreeUKGen/FreeCENMigration/issues/1427#issuecomment-1210586196 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AKCPIFPSORF7IRT4KDPHX63VYOL75ANCNFSM5WRCDN6Q .
You are receiving this because you were mentioned.  https://github.com/notifications/beacon/AKCPIFOLQJIJL6UI5J7VX2LVYOL75A5CNFSM5WRCDN62YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOJAUBIVA.gif Message ID: @.*** @.***> >

Items on test3 are still out of date.
The updated items were sent to Denise.
Geoff

Refinery page to check: https://test3.freecen.org.uk/cms/freecen-handbook/draft-freecen-handbook-june-2022

I have checked all the links and they are OK.
Content is OK except an unwanted indent part way down at Abbreviated Handbook.
This can be deployed once the indent is fixed.
Geoff

@DeniseColbert Allow me to fix the markup that has gone awry (in more than one place, as it happens).

@DeniseColbert @geoffj-FUG
Markup fixed. Whilst fixing it I noted some issues that will need resolving, either before publication or as soon as is feasible:
1. the example spreadsheet is not a CSV file, as stated: it has the file ending .xls
2. some downloads are set to open in a new tab, some are not — which do we want?
3. the tone and implied audience of the text is highly variable
In addition, I suggest we remove the date from the page name (so that incoming navigation is not broken) and record the revision date within the body of the page.

Cc to Denise for file.
Alison
I have attached the csv version. Perhaps we should include both versions as the xls version has the markup which is lost in the csv version.
Geoff
From: AlOneill @.>
Sent: Saturday, 10 September 2022 9:49 PM
To: FreeUKGen/FreeCENMigration @.>
Cc: geoffj-FUG @.>; Mention @.>
Subject: Re: [FreeUKGen/FreeCENMigration] Update FreeCEN Handbook on line and add sample completed spreadsheet. (Issue #1427)
@DeniseColbert https://github.com/DeniseColbert  @geoffj-FUG https://github.com/geoffj-FUG
Markup fixed. Whilst fixing it I noted some issues that will need resolving, either before publication or as soon as is feasible:

the example spreadsheet is not a CSV file, as stated: it has the file ending .xls
some downloads are set to open in a new tab, some are not — which do we want?
the tone and implied audience of the text is highly variable

In addition, I suggest we remove the date from the page name (so that incoming navigation is not broken) and record the revision date within the body of the page.
—
Reply to this email directly,  https://github.com/FreeUKGen/FreeCENMigration/issues/1427#issuecomment-1242712587 view it on GitHub, or  https://github.com/notifications/unsubscribe-auth/AKCPIFLAEDBJMQA352SLOPDV5RYTTANCNFSM5WRCDN6Q unsubscribe.
You are receiving this because you were mentioned.  https://github.com/notifications/beacon/AKCPIFN7EYZA6PSBGD2G7VTV5RYTTA5CNFSM5WRCDN62YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOJIJEUCY.gif Message ID: < @.> @.>

@AlOneill what do you recommend for downloads- new/same tab?
I think it would be fine for you to standardise the tone/audience if you're happy to?

@geoffj-FUG I will include both the CSV and the .xls versions, with a brief explanation of the differences.
@DeniseColbert My recommendation for links to downloads is to follow the guidelines that apply to all links, adding the file size to the link text. So, open in the same tab, state the file format and size.
OK: I will attempt to standardise the tone, and address the text primarily to transcribers.

Alison
Open in new tab please. These are instructions so volunteers refer to them. If they open in same tab then it will use their workspace.
Geoff
From: AlOneill @.>
Sent: Tuesday, 13 September 2022 7:30 AM
To: FreeUKGen/FreeCENMigration @.>
Cc: geoffj-FUG @.>; Mention @.>
Subject: Re: [FreeUKGen/FreeCENMigration] Update FreeCEN Handbook on line and add sample completed spreadsheet. (Issue #1427)
@geoffj-FUG https://github.com/geoffj-FUG  I will include both the CSV and the .xls versions, with a brief explanation of the differences.
@DeniseColbert https://github.com/DeniseColbert  My recommendation for links to downloads is to follow the guidelines that apply to all links, adding the file size to the link text. So, open in the same tab, state the file format and size.
OK: I will attempt to standardise the tone, and address the text primarily to transcribers.
—
Reply to this email directly, view it on GitHub https://github.com/FreeUKGen/FreeCENMigration/issues/1427#issuecomment-1244511750 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AKCPIFMFSQNIVZO4XNX3DWTV56OF3ANCNFSM5WRCDN6Q .
You are receiving this because you were mentioned.  https://github.com/notifications/beacon/AKCPIFLXWI65Z37CZEOFUQ3V56OF3A5CNFSM5WRCDN62YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOJIW34BQ.gif Message ID: @.*** @.***> >

@geoffj-FUG
This is about user control and choice. If we set a link to open in a new tab, then that is what will happen — the user cannot override the setting. However, if a link is set to open in the same tab, the default behaviour, then each user can choose to open it either in the same tab or in a new tab (or window) by way of the context menu: the mechanics of this vary but it is a right-click on a typical Windows desktop setup using a mouse.
Web usability guidelines recommend that links be set to open in the same tab unless there is an overriding reason to do otherwise. FUK Genealogy policy is that the Scrum can decide to force a link to open in a new tab only if there is an overwhelming reason to do so.

I've nearly finished tweaking the Handbook page. This part is not clear for the literal part of my brain:
"Complete FreeCEN Handbook (now obsolete for Transcribers, Proofreaders, Validators and Coordinators)
"This is the original comprehensive guide to working with FreeCEN2. It will gradually be replaced by parts 1 to 4 of the Handbook. Most of this Handbook has now been replaced by the above documents (which are more up to date). If you download this version we suggest that you save the Handbook to your computer. It is quite large, so printing is probably not a viable option."
@geoffj-FUG If the Complete Handbook is now obsolete for "Transcribers, Proofreaders, Validators and Coordinators", who does that leave needing or wanting to use it? Does the punctuation need adjusting to clarify the meaning?
I can see parts 1 to 3 of the Handbook, but not part 4: what will it contain and who will use it? Is it currently part of the Complete Handbook or will it be new material?
Thank you!

Alison,
I still have the data manager part to write. I also have Part 1 for Scotland and Ireland to make available. These are all covered in the complete Handbook.
Scotland has been reviewed by Margaret Singleton so I will be able to include part 1B soon. Part 1C Ireland is written but I still need to do my final proof read.
Once all the parts are written and available then I will have the Full Handbook removed.
Geoff
From: AlOneill @.>
Sent: Tuesday, 20 September 2022 10:07 PM
To: FreeUKGen/FreeCENMigration @.>
Cc: geoffj-FUG @.>; Mention @.>
Subject: Re: [FreeUKGen/FreeCENMigration] Update FreeCEN Handbook on line and add sample completed spreadsheet. (Issue #1427)
I've nearly finished tweaking the Handbook page. This part is not clear for the literal part of my brain:
"Complete FreeCEN Handbook (now obsolete for Transcribers, Proofreaders, Validators and Coordinators)
"This is the original comprehensive guide to working with FreeCEN2. It will gradually be replaced by parts 1 to 4 of the Handbook. Most of this Handbook has now been replaced by the above documents (which are more up to date). If you download this version we suggest that you save the Handbook to your computer. It is quite large, so printing is probably not a viable option."
@geoffj-FUG https://github.com/geoffj-FUG  If the Complete Handbook is now obsolete for "Transcribers, Proofreaders, Validators and Coordinators", who does that leave needing or wanting to use it? Does the punctuation need adjusting to clarify the meaning?
I can see parts 1 to 3 of the Handbook, but not part 4: what will it contain and who will use it? Is it currently part of the Complete Handbook or will it be new material?
Thank you!
—
Reply to this email directly, view it on GitHub https://github.com/FreeUKGen/FreeCENMigration/issues/1427#issuecomment-1252259959 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AKCPIFMC4CWR4JV6JD2KZU3V7GSFFANCNFSM5WRCDN6Q .
You are receiving this because you were mentioned.  https://github.com/notifications/beacon/AKCPIFJOHHTC6BFCAQVBTNDV7GSFFA5CNFSM5WRCDN62YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOJKR7Q5Y.gif Message ID: @.*** @.***> >

The DRAFT FreeCEN Handbook page is now ready for review.

Alison
This looks good.
However, can you amend
Once you get going, please use Part 1 of the FreeCEN2 Handbook for England and Wales or Dave's Guide for New Transcribers.
To
This can be used in conjunction with Dave's Guide for New Transcribers. Once you get going please use Part 1 of the FreeCEN2 Handbook for England and Wales.
Amend
This page has download links for the various guides that help Transcribers, Proofreaders, Validators and Coordinators in the transcription of census documents.
Introduction to FreeCEN for New Transcribers
Dave’s FreeCEN2 New Transcriber Guide
FreeCEN2 Handbook —
Part 1 — Transcriber and Proofreader Handbook, for England and Wales
Part 2 — Validator Handbook
Part 3 — Coordinator Handbook
Last updated for June 2022
Introduction to FreeCEN for New Transcribers (England and Wales)
This Introduction is suitable for New Transcribers: it is a simple guide to get you started. Once you get going, please use Part 1 of the FreeCEN2 Handbook for England and Wales or Dave's Guide for New Transcribers.
Download the Introduction Guide (PDF, 258 KB)
The Guide will appear on your Screen in Acrobat Reader (or in the browser on a Mac):
select the Download Icon (an underlined downward arrow)
you will be asked where you want to Save the Guide. Save it.
open the Guide in Acrobat Reader (or in Preview on a Mac)
select the Print Icon (or File … Print)
select your Printer
set Pages to ‘Print to All’
select ‘Booklet’
set Booklet option to ‘both sides’
set the Orientation to Portrait
select Print
The Guide will now print on 4 pieces of A4 paper back to back. These can be folded into an A5 booklet.
The various guides and Handbooks are PDF (Portable Document Format) files. Most browsers can show the contents of a PDF file directly: if not, you’ll see a dialogue box rather than the Handbook itself. Follow the instructions from step two.
Dave’s FreeCEN2 New Transcriber Guide
This Guide was written by Dave as he learnt to Transcribe for FreeCEN. It aims to explain things from the point of view of the Transcriber.
Download Dave’s FreeCEN2 New Transcriber Guide (PDF, 4.71 MB)
select the Download Icon (an underlined downward arrow)
you will be asked where you want to Save the Guide. Save it.
open the Guide in Acrobat Reader (or in Preview on a Mac)
select the Print Icon (or File … Print) (it will print on about 15 sheets of A4 back to back)
select your Printer
set Pages to Print to All
select Back-to-back (flip on long side)
set the Orientation to Portrait
select Print
Sample Completed Spreadsheet
This is the beginning of a sample transcription (about 6 pages of images). It contains a range of entries so that you, as a new transcriber, can see what a completed spreadsheet looks like.
If your spreadsheet software can open Microsoft Excel format files, .xls, then we recommend looking at that one. It has some formatting that makes it nicer to look at and so easier to read than the CSV file. In particular, the first row of every census page has been given a yellow background as per Dave’s suggestion.
Download Sample Spreadsheet (.xls, 54 KB)
or
Download Sample Spreadsheet (CSV, 12.2 KB)
Depending on your operating system and browser, you might find that you are starting at step two rather than step one:
select the Download Icon (an underlined downward arrow)
you will be asked where you want to Save the spreadsheet — save it
open the spreadsheet using your spreadsheet software (any spreadsheet software can open a .csv file)
FreeCEN2 Handbook part 1 — Transcription —
To
FreeCEN2 Handbook part 1
I will align the Titles with parts 2 and 3 when I produce the next version of part 1.
Otherwise I am very happy with this.
I will still argue that these should open in a new tab. My computer is set up to open pdf's within Google Chrome. The download file therefore overwrites the FreeCEN page. If I was not wise to the system I might get very annoyed as a new transcriber if I had to go back and  find FreeCEN every time that I downloaded my instructions. It is more friendly to open the instructions in a new tab next to my FreeCEN menu.
Geoff

@geoffj-FUG
OK, but I will change some clauses back from the passive to the active voice and substitute some words and phrases with an unusual vocabulary or usage — most of our Transcribers are Brits but not all have English as their everyday language. The passive voice sounds unfriendly to many (which is off-putting) and is harder to take in if you are not accustomed to it.
As for forcing the downloads to open in a new tab, that is a decision for the Scrum. Maybe we need to point out to the user that they have a choice, describing the basics of how to open a link in a new tab if they wish to do so. (Education is empowering, yes.) I would be against taking away that choice — that would annoy me! (It would also clutter the link text with the required warning.)

Alison
It didn’t used to be a problem when all pdfs opened in Acrobat or similar. The opening within a Google etc tab has created the problem.
If only things remained the same!
Geoff
From: AlOneill @.>
Sent: Saturday, 24 September 2022 7:43 PM
To: FreeUKGen/FreeCENMigration @.>
Cc: geoffj-FUG @.>; Mention @.>
Subject: Re: [FreeUKGen/FreeCENMigration] Update FreeCEN Handbook on line and add sample completed spreadsheet. (Issue #1427)
@geoffj-FUG https://github.com/geoffj-FUG
OK, but I will change some clauses back from the passive to the active voice and substitute some words and phrases with an unusual vocabulary or usage — most of our Transcribers are Brits but not all have English as their everyday language. The passive voice sounds unfriendly to many (which is off-putting) and is harder to take in if you are not accustomed to it.
As for forcing the downloads to open in a new tab, that is a decision for the Scrum. Maybe we need to point out to the user that they have a choice, describing the basics of how to open a link in a new tab if they wish to do so. (Education is empowering, yes.) I would be against taking away that choice — that would annoy me! (It would also clutter the link text with the required warning.)
—
Reply to this email directly, view it on GitHub https://github.com/FreeUKGen/FreeCENMigration/issues/1427#issuecomment-1256925815 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AKCPIFPZQFRJYVD7UVY7HRDV73EK3ANCNFSM5WRCDN6Q .
You are receiving this because you were mentioned.  https://github.com/notifications/beacon/AKCPIFLMBQKZM26YV6SGG7DV73EK3A5CNFSM5WRCDN62YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOJLVSU5Y.gif Message ID: @.*** @.***> >

The DRAFT FreeCEN Handbook page text has been updated as per Geoff's requests (as I understand them) and is ready for review. It now includes an info box on opening links in a new tab so that users know why things have changed: Windows users with a mouse, the largest and (dare I say it?!) neediest group, have the full SP.

@geoffj-FUG could you check this please?

Alison
We are at cross purposes.
The Handbook Action should open the Handbooks page in the same tab. The Download link should be where the volunteer makes their choices.
So I think we are on the same page.
Geoff
The links should open the document in a new tab. It can then be downloaded if the volunteer chooses.
From: AlOneill @.>
Sent: Tuesday, 13 September 2022 6:54 PM
To: FreeUKGen/FreeCENMigration @.>
Cc: geoffj-FUG @.>; Mention @.>
Subject: Re: [FreeUKGen/FreeCENMigration] Update FreeCEN Handbook on line and add sample completed spreadsheet. (Issue #1427)
@geoffj-FUG https://github.com/geoffj-FUG
This is about user control and choice. If we set a link to open in a new tab, then that is what will happen — the user cannot override the setting. However, if a link is set to open in the same tab, the default behaviour, then each user can choose to open it either in the same tab or in a new tab (or window) by way of the context menu: the mechanics of this vary but it is a right-click on a typical Windows desktop setup using a mouse.
Web usability guidelines recommend that links be set to open in the same tab unless there is an overriding reason to do otherwise. FUK Genealogy policy is that the Scrum can decide to force a link to open in a new tab only if there is an overwhelming reason to do so.
—
Reply to this email directly, view it on GitHub https://github.com/FreeUKGen/FreeCENMigration/issues/1427#issuecomment-1245102393 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AKCPIFIWSQS5BWMJTT67RO3V6A6LFANCNFSM5WRCDN6Q .
You are receiving this because you were mentioned.  https://github.com/notifications/beacon/AKCPIFMMN2LFRLXXXLITLL3V6A6LFA5CNFSM5WRCDN62YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOJI3MCOI.gif Message ID: @.*** @.***> >

@DeniseColbert to explore tab issue with Alison

This is still waiting. I understand the protocol involved in the use of tabs and the undesirability of systems opening strings of tabs across the screen.
When pdfs were automatically opened within Acrobat that was a reasonable policy. Opening in Acrobat meant that there was an additional programme in use and therefore the opened file was isolated from FreeCEN. However Acrobat is now a programme that is in its final decline as far as the generic user is concerned.
Today users are more likely to open pdf files in Microsoft Edge or Google Chrome. In fact the use of the browsers is encouraged by the Browser vendors.
If our Handbook documents open in the same tab as the open FreeCEN tab then the access to FreeCEN is overwritten. A user can have either FreeCEN or the Handbook. As they are using the Handbook to assist them to use FreeCEN this is not a practical situation.
It is imperative that the Handbook opens in a new tab so that FreeCEN access is not overwritten. This documentation must be deployed to use new tabs.
The work to update FreeCEN with these Handbook documents was done some time ago. It is now urgent as people are working from old guidelines. I have therefore upgraded this story to Ungent.
Geoff

@geoffj-FUG Alison will make it clear on the Handbook page in Refinery (so that transcribers will see it at the right point) how to open any link in a new tab and how to get back to the list of actions. She's also let them know that it would be easier for the handbook to be opened in a new tab. This will give users the most control and will add to their repertoire of internet skills: useful for transcribing on our websites!

@DeniseColbert @geoffj-FUG
I have edited the guidance on the Draft FreeCEN Handbook page in Refinery as per the above comment. The text now reads:
"What has changed?
"We have set nearly all the links on this site to open in the same browser tab rather than a new one. This puts you in control and makes it easier for all users to understand what has happened when they select a link.
"You are in control
"Sometimes, it makes sense to get a link to open in a new tab: you can choose to do exactly that. The details will depend on your OS (Operating System) and how you move around the page. For example, a Windows user with a mouse will right-click on the link to get a context menu. They can then choose “Open link in new tab” or “Open link in new window”.
"Keeping a useful page available
"The items in the main menu are links. The list of Actions on the ‘Your Actions’ page look like buttons, but they too are links. You can open a link in a new tab at will. For instance, you can open this page in a new tab from the Your Actions page; you can open any of the Handbook links on this page in a new tab. Your decision.
"Please note that the ‘Report a problem’ buttons are buttons — you cannot choose to open a new tab with them."
I hope this is now acceptable. (Specific suggestions for improvement are welcome, as ever.)

Alison
Please go ahead. We can then review if we have any issues with the outcome.
Geoff

@geoffj-FUG @DeniseColbert
Updated draft published on t3 and made sync-ready.

Alison
I view of the changes that have happened with pdf files appearing in Google Chrome and Microsoft Edge can we change:
In Introduction for New Transcribers.
The Guide will appear on your Screen in Acrobat Reader (or in the browser on a Mac):
To
The Guide may appear on your screen in Acrobat Reader or in your Browser:
Can we move the You are in control box to either above the Introduction to FreeCEN for New transcribers or to the Left of it? That way people see it first and are less likely to go ahead and just read the instructions.
That way it becomes more prominent.
I am also going to copy your box into the next version of the Handbook.
In Handbook Part 3 can we change Download the Handbook to Download the Coordinator Handbook?
(Mea Culpa)
I am happy then for this to go live. I am away for  week so just go ahead.
Geoff
From: AlOneill @.>
Sent: Saturday, 26 November 2022 10:45 PM
To: FreeUKGen/FreeCENMigration @.>
Cc: Geoff J @.>; Mention @.>
Subject: Re: [FreeUKGen/FreeCENMigration] Update FreeCEN Handbook on line and add sample completed spreadsheet. (Issue #1427)
@geoffj-FUG https://github.com/geoffj-FUG  @DeniseColbert https://github.com/DeniseColbert
Updated draft published on t3 and made sync-ready.
—
Reply to this email directly, view it on GitHub https://github.com/FreeUKGen/FreeCENMigration/issues/1427#issuecomment-1328040030 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AKCPIFIFRVUU5WO442PAWETWKIA3DANCNFSM5WRCDN6Q .
You are receiving this because you were mentioned.  https://github.com/notifications/beacon/AKCPIFIPG7YEKV77UNWWF53WKIA3DA5CNFSM5WRCDN62YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOJ4UEQXQ.gif Message ID: @.*** @.***> >

@geoffj-FUG
I have made the text changes you requested on t3. They will appear on the live site when the two are synced.
As for moving some or all of the contents of "Links and tabs" (I am not sure exactly how much you mean), I am reluctant to do so. The information belongs together; the blue background makes it prominent — it would be easy to change the colour if required; nothing is actually broken if they ignore it; once read and understood I believe that many users would find it annoying for the box to be always in the way as they scroll to reach a download link. As a compromise, I will place a short reminder to read the information ahead of "Introduction to FreeCEN for new transcribers".
Moving any or all of the information would be a decision for the Scrum.

Alison
The short reminder will help. Having the Handbooks available is critical.
I will put a short item in Chris’ next newsletter as well.
Geoff
From: AlOneill @.>
Sent: Sunday, 27 November 2022 10:01 PM
To: FreeUKGen/FreeCENMigration @.>
Cc: Geoff J @.>; Mention @.>
Subject: Re: [FreeUKGen/FreeCENMigration] Update FreeCEN Handbook on line and add sample completed spreadsheet. (Issue #1427)
@geoffj-FUG https://github.com/geoffj-FUG
I have made the text changes you requested on t3. They will appear on the live site when the two are synced.
As for moving some or all of the contents of "Links and tabs" (I am not sure exactly how much you mean), I am reluctant to do so. The information belongs together; the blue background makes it prominent — it would be easy to change the colour if required; nothing is actually broken if they ignore it; once read and understood I believe that many users would find it annoying for the box to be always in the way as they scroll to reach a download link. As a compromise, I will place a short reminder to read the information ahead of "Introduction to FreeCEN for new transcribers".
Moving any or all of the information would be a decision for the Scrum.
—
Reply to this email directly, view it on GitHub https://github.com/FreeUKGen/FreeCENMigration/issues/1427#issuecomment-1328231271 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AKCPIFNRRRW2GHRVKFJVKHLWKNERRANCNFSM5WRCDN6Q .
You are receiving this because you were mentioned.  https://github.com/notifications/beacon/AKCPIFLQJSF7DJLJYWNBHYDWKNERRA5CNFSM5WRCDN62YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOJ4VTGZY.gif Message ID: @.*** @.***> >


Timeout reference table is wrong for premium V1

This table has an incorrect value for the Premium SKU on V1:
https://docs.microsoft.com/en-us/azure/azure-functions/functions-scale#timeout
It says that the default timeout is 30 minutes but in fact no default timeout is applied in V1 unless the app is in the consumption SKU:
https://github.com/Azure/azure-functions-host/blob/v1.x/src/WebJobs.Script/Host/ScriptHost.cs#L1675-L1693
PR is here:
https://github.com/MicrosoftDocs/azure-docs-pr/pull/156021

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

ID: 06436739-8586-23b1-6b69-1960e93c26be
Version Independent ID: 8f7abfae-cf6d-56cb-1d20-f02041a6f6d9
Content: Azure Functions scale and hosting
Content Source: articles/azure-functions/functions-scale.md
Service: azure-functions
GitHub Login: @ggailey777
Microsoft Alias: glenga

Thank you @paulbatum.


Fix grammar

(new commit / PR) Ah, ok, I was confused by the "it" anyway :)

:+1:

Pushed to the original repo as well :)
https://github.com/sindresorhus/np/pull/5


Problem about Windows running client

I run the server through docker and deployed it on a server. I run client on my PC like this:
from whisper_live.client import TranscriptionClient
client = TranscriptionClient(
  "<IP_ADDRESS>",
  9090,
  lang="zh",
  translate=False,
  model="small",
  use_vad=False,
)

client("./output_recording.wav")

It returns Error:
[INFO]: * recording
[INFO]: Opened connection
[INFO]: Server Running with backend faster_whisper
[INFO]: Waiting for server ready ...
[INFO]: Server Ready!
Traceback (most recent call last):
  File "D:\Project\python\WhisperLive\test.py", line 11, in <module>
    client("./output_recording.wav")
  File "D:\miniconda\envs\zhipu\lib\site-packages\whisper_live\client.py", line 329, in __call__
    resampled_file = utils.resample(audio)
  File "D:\miniconda\envs\zhipu\lib\site-packages\whisper_live\utils.py", line 61, in resample
    ffmpeg.input(file, threads=0)
  File "D:\miniconda\envs\zhipu\lib\site-packages\ffmpeg\_run.py", line 313, in run
    process = run_async(
  File "D:\miniconda\envs\zhipu\lib\site-packages\ffmpeg\_run.py", line 284, in run_async
    return subprocess.Popen(
  File "D:\miniconda\envs\zhipu\lib\subprocess.py", line 951, in __init__
    self._execute_child(args, executable, preexec_fn, close_fds,
  File "D:\miniconda\envs\zhipu\lib\subprocess.py", line 1436, in _execute_child
    hp, ht, pid, tid = _winapi.CreateProcess(executable, args,
FileNotFoundError: [WinError 2] 系统找不到指定的文件。

the audio file "output_recording.wav" does exist in the same path. I run the client like this:
from whisper_live.client import TranscriptionClient
client = TranscriptionClient(
  "<IP_ADDRESS>",
  9090,
  lang="zh",
  translate=False,
  model="small",
  use_vad=False,
)

client()

It can run without problem, recording my voice and return the words. Why do I meet up with problem when processing an audio file?

This is done, I just install ffmpeg to fix this.


[apostrophe-images] Chooser template needs search ability (filters), bottomless hooked up, etc.

I think you mean the manager template? But doesn't it have those things
already?
The chooser is only displaying what has already been chosen so pagination
is not an issue?
On Wed, Apr 13, 2016 at 4:23 PM, Jimmy Harrison<EMAIL_ADDRESS>wrote:

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/punkave/apostrophe/issues/500

--
*THOMAS BOUTELL, *DEV & OPS
P'UNK AVENUE |<PHONE_NUMBER>  |  punkave.com

Specifically talking about the images chooser here, and there is currently an issue with filters displaying on managers which are slidable (like choosers). The idea is to eventually have bottomless hooked up on the images manager. Maybe these are separate issues though.

Okay, that makes sense. Just making sure the chooser wasn't escaping its
intended scope (:
On Thu, Apr 14, 2016 at 10:59 AM, Jimmy Harrison<EMAIL_ADDRESS>wrote:

Specifically talking about the images chooser here, and there is currently
an issue with filters displaying on managers which are slidable (like
choosers). The idea is to eventually have bottomless hooked up on the
images manager. Maybe these are separate issues though.
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/punkave/apostrophe/issues/500#issuecomment-209987066

--
*THOMAS BOUTELL, *DEV & OPS
P'UNK AVENUE |<PHONE_NUMBER>  |  punkave.com

@mcoppola I've currently implemented a stopgap here by bringing traditional paging back in the grid view of images. Unless you particularly need filtering for your training, I think I'll probably this one back a sprint in order to prioritize other issues, is that cool?


Better solution for multiple fuel-core error

This error is clear, but I think the SDK should provide more help as to how the right way to resolve this should be or documentation as to how to resolve it.
i.e. here is what is wrong, here is how you can resolve it.
found more than one 'fuel-core' binary in PATH, using '/Users/nick/.fuelup/bin/fuel-core'
thread 'tokio-runtime-worker' panicked at 'error: Could not connect to fuel core server.', /Users/nick/.cargo/registry/src/github.com-1ecc6299db9ec823/fuels-test-helpers-0.43.0/src/node.rs:335:9
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: RecvError(())', /Users/nick/.cargo/registry/src/github.com-1ecc6299db9ec823/fuels-test-helpers-0.43.0/src/node.rs:320:14

@SilentCicero "found more than one fuel-core" doesn't cause an error. It is a warning message (should probably be moved to a log instead of being in stderr) introduced after we wasted a couple of hours debugging with the wrong fuel-core binary. It is there mainly to inform the user as to which binary was chosen.
The real error is that we couldn't connect to the node. And there we should have some more info surrounding why (presumably) the node closed unexpectedly.


mgmt, codegen on machinelearning

Description
Please add an informative description that covers that changes made by the pull request and link all relevant issues.
If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
All SDK Contribution checklist:

[ ] The pull request does not introduce [breaking changes]
[ ] CHANGELOG is updated for new features, bug fixes or other significant changes.
[ ] I have read the contribution guidelines.

General Guidelines and Best Practices

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

/azp run prepare-pipelines

/azp run java - machinelearning - ci

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-resourcemanager-machinelearning


remove deleted file from Dockerfile

File was removed in https://github.com/openshift/ansible-service-broker/pull/121. 👍


Update optional 'unocss' dependency to '^0.58.6' in @formkit/themes

Currently, @formkit/themes has a pinned optional dependency of unocss set to a version from 2 years ago, which presents challenges with conflicting dependencies when installing other packages that depend on it.
This pull request updates the optional dependency to the current latest version of unocss for review/checks primarily.

Thanks @danielward! Would you mind bumping the lockfile (pnpm install) and re-committing? Thanks!

Thanks @danielward! Would you mind bumping the lockfile (pnpm install) and re-committing? Thanks!

Done. What I'm less sure of is whether pinning to the latest version then causes an issue the other way round whereby other packages have dependencies for older versions. One workaround could be to pin it at "^^0.58.0" or earlier, though you likely have far more experience here than I do!


pip installation LD_LIBRARY_PATH order

Click to expand!
Issue Type
Documentation Bug
Have you reproduced the bug with TF nightly?
Yes
Source
binary
Tensorflow Version
tf 2.12
Custom Code
No
OS Platform and Distribution
No response
Mobile device
No response
Python version
No response
Bazel version
No response
GCC/Compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current Behaviour?
In the official pip install documentation $LD_LIBRARY_PATH is updated via conda activation.
Following instructions on clean machine for library linking works perfectly
However if the machine has a native CUDA library setting, TF will load the system library ahead of virtual environment one.
Suggest to load conda path ahead of system one:
echo 'CUDNN_PATH=$(dirname $(python -c "import nvidia.cudnn;print(nvidia.cudnn.__file__)"))' >> $CONDA_PREFIX/etc/conda/activate.d/env_vars.sh
echo 'export LD_LIBRARY_PATH=$CONDA_PREFIX/lib/:$CUDNN_PATH/lib:$LD_LIBRARY_PATH' >> $CONDA_PREFIX/etc/conda/activate.d/env_vars.sh

Standalone code to reproduce the issue
echo 'export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$CONDA_PREFIX/lib/:$CUDNN_PATH/lib' >> $CONDA_PREFIX/etc/conda/activate.d/env_vars.sh

Relevant log output
2023-06-01 15:58:54.130390: E tensorflow/compiler/xla/stream_executor/cuda/cuda_dnn.cc:417] Loaded runtime CuDNN library: 8.1.1 but source was compiled with: 8.6.0.  CuDNN library needs to have matching major version and equal or higher minor version. If using a binary install, upgrade your CuDNN library.  If building from sources, make sure the library loaded at runtime is compatible with the version specified during compile configuration.
2023-06-01 15:58:54.131265: W tensorflow/core/framework/op_kernel.cc:1830] OP_REQUIRES failed at conv_ops.cc:1068 : UNIMPLEMENTED: DNN library is not found.

Can you send a PR, please?

@jackyko1991,
The related PR #https://github.com/tensorflow/docs/pull/2230 has been closed and also the issue happened on 2.12 which is pretty old. Could you please try with the latest stable version 2.12 where most of the bugs were resolved in the latest version.
https://www.tensorflow.org/install/pip
Thank you!


[Beta] - Nested objects get serialised as "[object Object]" again

Hi,
We are using winston logging + application insights beta.
v beta.12 is failing to serialise nested objects

v beta.11 still works

Similar to the last time in behaviour: https://github.com/microsoft/ApplicationInsights-node.js/issues/1169
Dependencies which work:
        "@opentelemetry/api": "^1.8.0",
        "@opentelemetry/instrumentation": "^0.50.0",
        "@opentelemetry/instrumentation-express": "^0.37.0",
        "@opentelemetry/instrumentation-graphql": "^0.39.0",
        "@opentelemetry/instrumentation-ioredis": "^0.39.0",
        "@opentelemetry/instrumentation-tedious": "^0.9.0",
        "@opentelemetry/instrumentation-winston": "^0.36.0",
        "@opentelemetry/sdk-trace-node": "^1.23.0",
        "@opentelemetry/semantic-conventions": "^1.23.0",
        "@opentelemetry/winston-transport": "^0.2.0",
        "applicationinsights": "3.0.0-beta.11",

Using the same deps with beta.12 results in nested objects being serialised as [object Object]
Full config used:
const resource = Resource.EMPTY
resource.attributes[SEMRESATTRS_SERVICE_NAME] = '[REDACTED]'
resource.attributes[SEMRESATTRS_SERVICE_NAMESPACE] = '[REDACTED]'

useAzureMonitor({
  resource,
  instrumentationOptions: {
    azureSdk: { enabled: false },
    mongoDb: { enabled: false },
    mySql: { enabled: false },
    postgreSql: { enabled: false },
    redis: { enabled: false },
    redis4: { enabled: false },
    console: { enabled: false },
    bunyan: { enabled: false },

    http: { enabled: true },
    winston: { enabled: true },
  } satisfies ApplicationInsightsInstrumentationOptions as unknown as OpenTelemetryInstrumentationOptions, // https://github.com/microsoft/ApplicationInsights-node.js/issues/1269
})

const tracerProvider = trace.getTracerProvider()

registerInstrumentations({
  tracerProvider,
  instrumentations,
})

@cuzzlor Thank you for providing the config and reporting this issue. Could you also provide an example of a log producing the output in the portal you noted above? Thank you!

@JacksonWeber An example of producing a log which would result in a field of the trace customDimensions section showing a value of [object Object] would be any that uses an object as a value in the winston logger 2nd log method parameter for log entry arguments, e.g.:
logger.info('This is my info log message', { foo: 'this will display OK', nested: { foo: 'this nested field value will not be serialised' } } )

I experience the same issue after upgrading to 3.0.0-beta.12, which forces me to stay on beta.11.

@cuzzlor @mderriey Thank you for your continued usage and testing of the beta! We're moving away from the https://www.npmjs.com/package/diagnostic-channel-publishers solution for collecting Winston logs and moving to the OpenTelemetry instrumentation. While this won't be available in the release of ApplicationInsights 3.0.0, it's undergoing review here https://github.com/Azure/azure-sdk-for-js/pull/29321.
I'll work on addressing the ability to send these kinds of nested logs in the OpenTelemetry transport for Winston https://github.com/open-telemetry/opentelemetry-js-contrib/tree/main/packages/winston-transport. I can alert you both when these changes are completed and the issue of serialization is fully solved (for both our Azure Monitor OpenTelemetry, and Application Insights 3.X SDK offerings).

I feel like log instrumentation was the biggest thing for us that made us use the App Insights SDK and not the Azure Monitor OpenTelemetry Distro.
Once the serialisation is fixed, we could use the OpenTelemetry transport for winston and get the logs shipped to App Insights through the OTel logs.
Is there a page that lists what the App Insights SDK offers on top of @azure/monitor-opentelemetry? I don't think either of us used the 2.x SDK, and we're familiar with OpenTelemetry, but maybe there are built-in features we don't realise we depend on...
Thanks in advance!

@mderriey The official Azure Monitor OpenTelemetry Distro docs are a good resource for the differences https://learn.microsoft.com/azure/azure-monitor/app/opentelemetry-enable?tabs=nodejs as well as the migration guide for those using Application Insights 2.X APIs https://learn.microsoft.com/azure/azure-monitor/app/opentelemetry-nodejs-migrate?tabs=cleaninstall, but please let me know if you have any further questions regarding comparing feature sets!
Since the Application Insights 3.X SDK is intended to work as a wrapper around the distro, you'd likely be better served by using that product given your familiarity with OpenTelemetry.

@mderriey @cuzzlor Just wanted to give you both an update that the PR addressing this on the Azure Monitor Distro side has been merged and will be available in the next release https://github.com/Azure/azure-sdk-for-js/pull/29321.

Hi @JacksonWeber,
I tried updating to v3.0.1 and updated all the @otel packages to latest, I still get this issue.
Can you please clarify the roadmap for this bug being fixed? It burns a lot of time deploying updates that need to be tested then rolled back.
Thanks!

@cuzzlor the fix for object serialization will be coming with the next release of the Azure Monitor OpenTelemetry package that Application Insights 3.X SDK also relies on.
I expect a release of that package this week. Once that release is out, I'll make a release of this repo with the updated Azure Monitor OpenTelemetry package.
I'm glad to hear the AzMon OpenTelemetry package will work for you both! It should be more versatile if you're not dependent on legacy App Insights API support.

@cuzzlor @mderriey The updated distro (1.5.0) and exporter (beta.23) are now available in the Azure SDK. A release of Application Insights based on these packages will be available soon.

Thanks Jackson, will use, appreciate your work and comms thank you. 🙏

Closing as fixed, please reopen if you have any follow up questions or issues.


pythonPackage.ovirt-engine-sdk: init at 4.3.3

Motivation for this change
Ansible ovirt_* modules require this lib
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Notify maintainers
cc @

bump, author
going to close if there's no activity in a week

Closing due to being very stale


Add og image option

Hi! Thank you for your great work on this package.
Would it be an option to add the generating of an og image with the dimensions of 1200*630 pixels (the recommended size of an og image)?
More info: https://ogp.me/
Thanks in advance!

Other sites like Reddit use square og:images.
https://www.h3xed.com/web-and-internet/how-to-use-og-image-meta-tag-facebook-reddit
It may be worth investigating how Facebook, Reddit, and Twitter treat multiple og:image tags with different aspect ratios to see what the best to generate are.


[oadp-1.4] OADP-4379: read ephemeral-storage in code

Why the changes were made
cherry picked from commit https://github.com/openshift/oadp-operator/commit/b51ce21d3df79005a81ed6e579a3359cffa46b0f : PR https://github.com/openshift/oadp-operator/pull/1477
How to test the changes made
Follow instructions from parent PR.

/retest

/retest
infra and post restore flake

/retest

/retest

/retest

hrm... this doesn't seem like a "flake" more like build / containers aren't right, but unrelated to this patch.

/retest

/retest

/retest

/retest

/lgtm


error when run in ios

[capacitor]         ld: in /Users/unknown/Documents/projects/sample/ios/capacitor-cordova-ios-plugins/sources/CordovaPluginStripe/src/ios/Stripe.framework/Stripe(STPAPIClient.o), building for iOS Simulator, but linking in object file built for iOS, for architecture arm64
[capacitor]         clang: error: linker command failed with exit code 1 (use -v to see invocation)
[capacitor]
[capacitor]         ** BUILD FAILED **
[capacitor]
[capacitor]
[capacitor]         The following build commands failed:
[capacitor]         CompileSwiftSources normal arm64 com.apple.xcode.tools.swift.compiler (in target 'Capacitor' from project 'Pods')
[capacitor]         Ld /Users/unknown/Documents/projects/sample/ios/DerivedData/AB6EFF0A-3DF3-4E7A-BDBF-121B52627091/Build/Products/Debug-iphonesimulator/CordovaPlugins/CordovaPlugins.framework/CordovaPlugins normal (in target 'CordovaPlugins' from project 'Pods')
[capacitor]         (2 failures)

[capacitor] ld: in /Users/unknown/Documents/projects/sample/ios/capacitor-cordova-ios-plugins/sources/CordovaPluginStripe/src/ios/Stripe.framework/Stripe(STPAPIClient.o), building for iOS Simulator, but linking in object file built for iOS, for architecture arm64 [capacitor] clang: error: linker command failed with exit code 1 (use -v to see invocation) [capacitor] [capacitor] ** BUILD FAILED ** [capacitor] [capacitor] [capacitor] The following build commands failed: [capacitor] CompileSwiftSources normal arm64 com.apple.xcode.tools.swift.compiler (in target 'Capacitor' from project 'Pods') [capacitor] Ld /Users/unknown/Documents/projects/sample/ios/DerivedData/AB6EFF0A-3DF3-4E7A-BDBF-121B52627091/Build/Products/Debug-iphonesimulator/CordovaPlugins/CordovaPlugins.framework/CordovaPlugins normal (in target 'CordovaPlugins' from project 'Pods') [capacitor] (2 failures)

Hello. Did you solve it somehow? I'm having the same issue. Did you have to migrate to a different plugin? Thanks!

I have almost the same issue from the Cordova framework in Mac arm64 platform.


Investigate XMPP support

See this comment: https://elixirforum.com/t/an-open-source-alternative-to-intercom-drift-etc/33450/4
I'm not too familiar with XMPP, but wanted to kick off a discussion thread here so I don't forget about it :)

Hello, I was digging into how would be possible to integrate with XMPP, like ejabberd.
Some links:
https://docs.ejabberd.im/use-cases/#customer-chat-crm
https://livehelperchat.com/full-xmpp-chat-support-for-ejabberd-423a.html (see a demo in the bottom of the page)
https://github.com/LiveHelperChat/xmpp-chat

thanks @joaohf this is super helpful!

There's also a XMPP library from processone if papercups should get direct XMPP support.
IMHO XMPP support would be great. :heart:

nice, we'll definitely check that out @alexanderadam!

just adding a note for one XMPP client we've heard about: https://conversations.im/


remove the change event object being passed to the callback

@contra this will require a major bump so we don't break anyone

updated

Coverage remained the same at 92.31% when pulling 03086c2ef684c0ead6348ca5089f802ac08e5bfd on phated:master into f3ec0ccf56856ff5bac701b1708fa62543ab5697 on wearefractal:master.

Coverage remained the same at 92.31% when pulling c24af724a64b84c1bc1feeb7b1352d9bd996d681 on phated:master into f3ec0ccf56856ff5bac701b1708fa62543ab5697 on wearefractal:master.

Coverage remained the same at 92.31% when pulling c24af724a64b84c1bc1feeb7b1352d9bd996d681 on phated:master into f3ec0ccf56856ff5bac701b1708fa62543ab5697 on wearefractal:master.

Coverage increased (+7.69%) to 100.0% when pulling dbea1bff005bb9cc4bdf888f3f91058931d5bfeb on phated:master into f3ec0ccf56856ff5bac701b1708fa62543ab5697 on wearefractal:master.

Weird that coveralls is reporting 100%, istanbul reported less locally.  Anyway, this has been updated

Probably needs some doc updates right?

@contra yep, just updated them now.

Coverage increased (+7.69%) to 100.0% when pulling 6611454fd9c1827af4b8e84f4bb7299e0e01d46c on phated:master into f3ec0ccf56856ff5bac701b1708fa62543ab5697 on wearefractal:master.


NuGet.exe on the agent should specify binding redirects for MSBuild

As a result of #529 the user can now specify that nuget pack should trigger a build. Consequently, nuget.exe should specify binding redirects for MSBuild so that projects that use tasks built against different versions of MSBuild work correctly.
See #793 and #972 for more information and examples where the build triggered by the NuGet task fails.
Workaround for an on-prem agent that has MSBuild v14.0 installed: add the following content in a text file called nuget.exe.config next to nuget.exe i.e. in *\agent\Worker\Tools*. This redirects MSBuild tasks built against v4 or v12 to v14.
<?xml version ="1.0"?>
<configuration>
    <runtime>
      <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
        <dependentAssembly>
          <assemblyIdentity name="Microsoft.Build.Framework" publicKeyToken="b03f5f7f11d50a3a" culture="neutral"/>
          <bindingRedirect oldVersion="<IP_ADDRESS>-<IP_ADDRESS>" newVersion="<IP_ADDRESS>"/>
        </dependentAssembly>
        <dependentAssembly>
          <assemblyIdentity name="Microsoft.Build" publicKeyToken="b03f5f7f11d50a3a" culture="neutral"/>
          <bindingRedirect oldVersion="<IP_ADDRESS>-<IP_ADDRESS>" newVersion="<IP_ADDRESS>"/>
        </dependentAssembly>
        <dependentAssembly>
          <assemblyIdentity name="Microsoft.Build.Engine" publicKeyToken="b03f5f7f11d50a3a" culture="neutral"/>
          <bindingRedirect oldVersion="<IP_ADDRESS>-<IP_ADDRESS>" newVersion="<IP_ADDRESS>"/>
        </dependentAssembly>
        <dependentAssembly>
          <assemblyIdentity name="Microsoft.Build.Conversion.Core" publicKeyToken="b03f5f7f11d50a3a" culture="neutral"/>
          <bindingRedirect oldVersion="<IP_ADDRESS>-<IP_ADDRESS>" newVersion="<IP_ADDRESS>"/>
        </dependentAssembly>
        <dependentAssembly>
          <assemblyIdentity name="Microsoft.Build.Tasks.Core" publicKeyToken="b03f5f7f11d50a3a" culture="neutral"/>
          <bindingRedirect oldVersion="<IP_ADDRESS>-<IP_ADDRESS>" newVersion="<IP_ADDRESS>"/>
        </dependentAssembly>
        <dependentAssembly>
          <assemblyIdentity name="Microsoft.Build.Utilities.Core" publicKeyToken="b03f5f7f11d50a3a" culture="neutral"/>
          <bindingRedirect oldVersion="<IP_ADDRESS>-<IP_ADDRESS>" newVersion="<IP_ADDRESS>"/>
        </dependentAssembly>
      </assemblyBinding>
    </runtime>
</configuration>

I'm not sure we can do anything correct here. We can redirect to <IP_ADDRESS> but then a user that needs <IP_ADDRESS> is stuck, or vice versa. Since we allow you to bring-your-own-nuget.exe in the NuGet tasks, you could also put nuget.exe.config in the repo. Am I missing anything?

@pascalberger does the proposed work for you?
@vtbassmatt Users should be able to work round the issue if they check in their own nuget.exe and provide a suitable config file, but this solution isn't very discoverable - could it be made more so?
Also, I'd guess that the current behaviour will fail for most users that use the -MSBuild option i.e. it will fail unless the build only uses tasks from a single version of MSBuild. MSBuild assemblies are backwards compatible so providing a redirect to the latest version will allow builds that uses tasks built against different versions to succeed. That would seem like a better default behaviour for most users. If a user really needed to build using a specific down-level version of MSBuild for some reason then they could do that by checking in a nuget.exe with an appropriate nuget.exe.config.

@duncanpMS @vtbassmatt Our case is a little special that we have quite a few repositories. Therefore putting nuget.exe.config in each repository just for the build server is not really a solution since it is not easy to maintain. Packaging it in a custom build task might be a solution, but currently we're working around it by first building the source for sonar and in a second step package the stuff.

nuget.exe will accept -MSBuildVersion as an argument. Does this solve the problem more cleanly than checking in binding redirects to a bunch of repos?

@vtbassmatt no, specifying -MSBuildVersion doesn't help - we tried that when looking at issues #793 and #972.
The underlying issue appears to be with how NuGet.exe triggers MSBuild; it looks for the appropriate version of MSBuild, then executes it using the MSBuild API rather than executing MSBuild.exe. NuGet.exe doesn't provide any binding redirects so the build failures will be common (i.e. unless every task used in the build is built against the same version of MSBuild). If NuGet.exe executed MSBuild.exe then the issue probably wouldn't arise as each version of MSBuild.exe does provide binding redirects for earlier versions: see e.g.
%PROGRAMFILES(x86)%\MSBuild\12.0\bin\msbuild.exe.config and
%PROGRAMFILES(x86)%\MSBuild\14.0\bin\msbuild.exe.config
However, if the task shipped with a NuGet.exe.config that had the same redirects as %PROGRAMFILES(x86)%\MSBuild\14.0\bin\msbuild.exe.config then any build triggered by the task would be much more likely to succeed.

if we add a redirect to v14, and the user specifies -MSBuildVersion 12, does that not mean that we are either a) broken, or b) actually using 14 when the user explicitly wants 12?

a) probably not since the assemblies are backwards-compatible, and b) this may or may not be a problem. The v14 backwards-compatible assemblies would be used which should be ok. The important thing is whether the v12 targets and tasks are used, as they control how the build is actually performed.


[Question]: The log shows No chunk! Done!

Describe your problem
When running file parsing, the log shows No chunk! Done!
Previous versions that support streaming responses parse files properly, but the latest versions don't parse files properly.

Could you attach the file?

Sure, it's this pdf
123.pdf

It is okay on the demo. I guess the open sourced layout recognition model is not good enough.

我用的嵌入模型是text-embedding-v2。在执行解析操作时会判断es库中是否有键，没有的话会根据当前用户创建一个，但是新版本的无法成功创建，旧版本的却可以


This app you can get some ideas.

https://github.com/vas3k/btt-touchbar-presets
Thanks for you awesome app.

🤭


Any suggestions about developing with Clarity UI components under AngularJS 1.5.x

Select one ...  (check one with "x")
[ ] bug
[x] feature request
[ ] enhancement

Expected behavior

Need information
Actual behavior

Reproduction of behavior

Environment details

Angular version:
1.5.X
Clarity version:
lastest
OS and version:
Ubuntu 14.04
Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]
all

I'm a UI developer with AngularJS 1.5.x, recently want to migrate UI from Bootstrap based to Clarity, I found Clarity provides three approaches with UX, UI and Components. I wonder know whether it will take more efforts to use Clarity UI and Components with Angular 1.5.x or it rather upgrade to Angular 2 directly for our next UI refactoring works. Thanks a lot!

Hi @wknet123,

clarity-ui / clarity-icons will work on your angular 1.5 projects as is. You just need to include the css / javascript for them in your project
clarity-angular can work with an angular 1.5.x app but there is some work that needs to be done to lay the foundation. I believe that if you follow the preperation steps here: https://angular.io/docs/ts/latest/guide/upgrade.html

Note: if you only use clarity-ui / clarity-icons then some components will not work (DataGrid, etc) because they depend on clarity-angular code and not just css.

@wknet123: as @hippee-lee mentioned, you can still use Clarity (clarity-ui and clarity-icons) regardless of the framework but when it comes to using clarity-ng, we think looking at the future and building for Angular 2 applications has been the right step for us. We recommend you look into migrating your application to Angular 2, the resources @hippee-lee suggested should help!


Recovering from the bad JPX images (#1145)

Partial solution for #1145 and #1154. The rendering of the page will not stop, but the bad images will have artifacts.
We can keep #1145 or #1154 open to see if we can suppress those artifacts.

@pdfjsbot test


Bug when using "0" as a memory limit for BungeeCord servers

Product
Please check the corresponding boxes below for which products this is about.

[x] Panel
[x] Daemon
[ ] Dockerfile(s) [Please list if so: __ ]

Type

[x] Bug or Issue
[ ] Feature Request
[ ] Enhancement
[ ] Other

What Happens

When typing 0 into the memory limit field on the New Server page of the panel to disable the memory limit feature for a BungeeCord server and then attempting to start the server will not start properly and give out an error saying "Invalid maximum heap size: -Xmx0M" since BungeeCord won't accept -Xmx0M as a valid memory limit.
How to Reproduce

Go to the Create Server page.
Try to create a BungeeCord server with a maximum memory limit of 0.
Go to the manage server page for the newly created server and attempt to start it.
Notice how the server will not start and give out an error saying: "Invalid maximum heap size: -Xmx0M"

Error Logs

Here are the CONSOLE logs as the rest aren't really needed and would probably be humungous:
> curl -sSL http://ci.md-5.net/job/BungeeCord/lastSuccessfulBuild/artifact/bootstrap/target/Bun
geeCord.jar -o bungeecord.jar
openjdk version "1.8.0_92-internal"
OpenJDK Runtime Environment (build 1.8.0_92-internal-alpine-r1-b14)
OpenJDK 64-Bit Server VM (build 25.92-b14, mixed mode)
$ java -Xms128M -Xmx0M -jar bungeecord.jar
Invalid maximum heap size: -Xmx0M
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.

System Information
Output of uname -a:
Linux vps123456 4.4.0-45-generic #66-Ubuntu SMP Wed Oct 19 14:12:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

Output of php -v (if Panel):
PHP 7.0.8-0ubuntu<IP_ADDRESS> (cli) ( NTS )
Copyright (c) 1997-2016 The PHP Group
Zend Engine v3.0.0, Copyright (c) 1998-2016 Zend Technologies
    with Zend OPcache v7.0.8-0ubuntu<IP_ADDRESS>, Copyright (c) 1999-2016, by Zend Technologies

Output of node -v (if Daemon):
v6.9.1

Output of docker info and docker -v (if Daemon or Dockerfiles):
DOCKER INFO:

Containers: 8
 Running: 7
 Paused: 0
 Stopped: 1
Images: 9
Server Version: 1.12.3
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 104
 Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: host overlay null bridge
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Security Options: apparmor seccomp
Kernel Version: 4.4.0-45-generic
Operating System: Ubuntu 16.04.1 LTS
OSType: linux
Architecture: x86_64
CPUs: 1
Total Memory: 5.689 GiB
Name: vps123456
ID: DM3F:5SZ5:H4YP:3RWX:Y5DA:H6HY:6H5X:6M36:NBEA:KMXD:2LJZ:4S2Q
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
WARNING: No swap limit support
Insecure Registries:
 <IP_ADDRESS>/8

DOCKER -V:
Docker version 1.12.3, build 6b644ec

EDIT:
This also seems to occur for normal Spigot servers.

Thats more of a user error, rather than a panel error. You have to change the startup to tell it how much memory to use. Theres no way for the panel to really be smart enough to handle that without just removing the entire startup argument.
The startup line does say that it will use the value from SERVER_MEMORY, so its working as intended for all intents and purposes.


Fix #3034: don't allow a negative viewport height

It doesn't make sense that the viewport height would ever be less than zero.
The change in getViewportHeight() exposed a problem in cellnav which I fixed and also updated the unit tests to be a little more meaningful.

@swalters: I think this one probably needs your review as I think you've recently been in this code.

@priceld I'm really sorry it's taken me so long to get to this but I'm checking it over now.
It looks like there's was a lot of refactoring in the scrolling code around the same time that you submitted this PR. For instance, the 1scrollToIfNecessary method has been refactored from the Scrolling feature to the core Grid class.
Would you be interested in trying to rebase on current master and adjust your changes to suit?

I'm having a hell of a time figuring out the merge for this. For some reason the diff when I try to apply your commit locally is way way different than what's here.
If you want I can try to pull out your code changes myself and commit them, or you can resubmit your PR.

Sorry for taking so long.  I'd be glad to merge my changes locally and open an new PR.  It may be a week or so before I can get to it though.

@priceld I am closing your PR for now due to merge conflicts. But feel free to reopen it when you are ready.


KDE 5 Klipper broken

I will shortly attempt to see why this is occurring, but here is what happens if you try to use the latest release under KDE 5. (Please note this still works under KDE 4)
---------- Data ----------
13:33 $ python -m unittest basicTests
Testing on: Python 2.7.9 - (KDE Klipper) - qdbus (external)
Cannot find '.setClipboardContents' in object /klipper at org.kde.klipper
Service 'org.kde.klipper' does not exist.
FCannot find '.setClipboardContents' in object /klipper at org.kde.klipper
Service 'org.kde.klipper' does not exist.
F
======================================================================
FAIL: test_copyPaste (basicTests.TestCopyPaste)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "basicTests.py", line 15, in test_copyPaste
    self.assertEqual(pyperclip.paste(), msg)
AssertionError: u'' != 'The quick brown fox jumped over the yellow lazy dog.'

======================================================================
FAIL: test_randomCopyPaste (basicTests.TestCopyPaste)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "basicTests.py", line 24, in test_randomCopyPaste
    self.assertEqual(pyperclip.paste(), msg)
AssertionError: u'' != 'kioqdZBItNwtDuIYvfqjjoxIu8JWBUU1QCJgFPRYOWng5lVipdXSZ59s5K8cb04GWQyfTRltS3XhG3OGxDC40XnxhYLkDeH7AZ2Oy1CTo3F8NMjlKPQEAMzBe62607pcTwmEJ2s1UgaHzavNwshSVFfLkP4AKemr769rzbubncriqMaLmREdvVpyH9'

----------------------------------------------------------------------
Ran 2 tests in 0.072s

FAILED (failures=2)

Maybe this thread on forum.kde.org  help.

@drakulavich  So pretty much, they have completely disabled communication to Klipper via dbus? I've been reading those post and there is no explanation of how to now interact with Klipper. Perhaps for now, we will have to wait to see what KDE has planned of a new form of interaction for Klipper.

As I understood, klipper is still available.

Resolved; the method for Klipper 4 still works for Klipper 5.

Is there something we can do about this though? We could at least check if the process object's returncode is not 0 (it is 1 if klipper is not running). Should we try to start klipper if it isn't running?
Otherwise, copy() and paste() don't raise any exceptions for the Cannot find '.setClipboardContents' in object /klipper at org.kde.klipper and Service 'org.kde.klipper' does not exist. error messages, but instead the program just keeps running.

It seems for the dbus, you must start klipper like so in the terminal.
klipper

Then the dbus will function properly.

I think, pyperclip should not try and start klipper. It's a user's responsibility. I prefer returncode checking.
We can put RuntimeError exception in copy_klipper and paste_klipper if command fails.

It would be best to auto-start the process. i see nothing wrong with PyPerclip doing so, However just to note that method would only be needed for KDE 5.

IMHO we should check if klipper is running instead of just checking that's installed.

I would expect that checking if service is ran to be the valid behaviour instead of checking if its installed. still not the case, coallegue has hit it in #202.


Builds are failing after upgrading to version 0.9.0 with error - "Variable $allow_rebuilds is declared by  but not used"

We are seeing failures after we upgraded to version 0.9.0, downgrading to 0.8.0 is working fine.
Error -
│ Error: Variable $allow_rebuilds is declared by  but not used
│
│   with buildkite_pipeline.custom-job,
│   on main.tf line 1544, in resource "buildkite_pipeline" "custom-job":
│  1544: resource "buildkite_pipeline" "custom-job" {

Yep that looks right!


Use native options of dependencies when available

Is your feature request related to a problem? Please describe.
Since is-my-node-vulnerable is officially recommended by Node.js, it would be better to have as less dependencies as possible.
Describe the solution you'd like
Use native options of dependencies when available
Additional context
Discussion on Twitter https://x.com/styfle/status/1847469788236255562

undici is an official Node.js dependency. I don't see why changing it to node:https will change things. If undici is vulnerable, Node.js is vulnerable (also npx). A different and more reasonable solution would be that we won't need to download a module making npx is-my-node-vulnerable fast, but it possible uses cache.

The feature request, and the discussion on Twitter, is not about the vulnerabilities the Node.js version being tested - but the ones used by is-my-node-vulnerable module.

Yes, I understand. However, I'm still not convinced that removing undici in favor of node:https will enhance security. Upgrading undici might be a better option.

Yes, I understand. But upgrading undici, or any other dependencies, may conflict with the minimum Node.js version which is-my-node-vulnerable aims to support.
Ideally, this module should support some EOL Node.js versions, as it's aimed to inform users whether their Node.js version is vulnerable. But it's dependencies may (and likely) drop support for EOL Node.js versions.

There's no package.json engines field for this module, and I couldn't find any documentation in README. As per  https://github.com/RafaelGSS/is-my-node-vulnerable/pull/6#issuecomment-1406824777, I think this module aims to support Node.js 12+. Undici 6.x supoports Node.js 18+, for example https://github.com/nodejs/undici/blob/e218fc61eda46da8784e0cedcaa88cd7e84dee99/package.json#L137-L139

I just realized that you're bundling all the code with ncc before publishing to npm, therefore you could move all dependencies to devDependencies and it will still work.

The dist is only used for github actions, when users attempt to npx is-my-node-vulnerable it's supposed to install package.dependencies otherwise it will fail. Am I missing something?

I see. In that case, moving the GitHub Actions usage into its own package might be better.


Disabling the plugin reports an invalid access error

Issue description
When the plugin is disabled, Godot will print the following error:

This can be easily fixed by rewriting the _exit_tree function inside plugin.gd to perform the inverse operations of _enter_tree in the correct order.
Here is the entire rewritten function:
func _exit_tree() -> void:
	scene_changed.disconnect(_scene_changed)
	scene_changed.disconnect(editor_panel_instance.viewfinder.scene_changed)
	panel_button.toggled.disconnect(_btn_toggled)

	remove_control_from_bottom_panel(editor_panel_instance)
	editor_panel_instance.queue_free()

	remove_node_3d_gizmo_plugin(pcam_3D_gizmo_plugin)

	remove_custom_type(PCAM_HOST)
	remove_custom_type(PCAM_3D)
	remove_custom_type(PCAM_2D)

	remove_autoload_singleton(PHANTOM_CAMERA_MANAGER)

Steps to reproduce
Enable the Phantom Camera plugin and then either disable it manually or simply close Godot.
(Optional) Minimal reproduction project
No response

Thanks for the report!
Resolved in #358


Async Awaitsend method

Closes #6
What it Does
Adds an async / await variation to the send method.

Ugh, of course @bcapps beat me to it 😛. I wish GitHub let you know when someone else was typing.

I think the last thing we’ll want to do here is add a ## How I Tested section to the PR and test out this work. Might be worth replacing the usage of the Combine version of send in AppDelegate.swift in the example project, catching and logging an error in the case of failure, and testing the success path, and the failure path (maybe by using airplane mode).

I think the last thing we’ll want to do here is add a ## How I Tested section to the PR and test out this work. Might be worth replacing the usage of the Combine version of send in AppDelegate.swift in the example project, catching and logging an error in the case of failure, and testing the success path, and the failure path (maybe by using airplane mode).

Is it ok if I write a unit test for this?

Is it ok if I write a unit test for this?
Yup!

@ashlirankin18 I think we just need to remove that test file for now and then this can be approved/merged.


Mutants & Masterminds 3E Official

Updates to making the importer more robust and capable of bringing in the default NPC sheets.
Updates to fix a majority of text overflow problems, particularly in the power window.
Minor adjustment to the hero points so it doesn't cover the Power Points section
Changes / Comments
Roll20 Requests
Comments are very helpful for reviewing the code changes. Please answer the relevant questions below in your comment.

[ ] Does the pull request title have the sheet name(s)? Include each sheet name.
[ ] Is this a bug fix?
[ ] Does this add functional enhancements (new features or extending existing features) ?
[ ] Does this add or change functional aesthetics (such as layout or color scheme) ?
[ ] If changing or removing attributes, what steps have you taken, if any, to preserve player data ?
[ ] If this is a new sheet, did you follow Building Character Sheets standards ?

If you do not know English. Please leave a comment in your native language.

Character Sheet Info Roll20 Internal Use only.


this is my hello world java file

Description

Types of changes

[ ] Bug fix or improving code quality
[ ] New language
[ ] New feature

Checklist:

[ ] My code follows the code style of this project.
[ ] I have updated the documentation accordingly.

this is my hello World java file

this is my hello world java file


about the gap time

Guys ，I have a question about the gap time。
I understand what's gap time it is ,but I don't understand how it occur
for example：the gap time  between method A and  method B is 10 seconds, then what happened in that 10 seconds  ? it's synchronize lock? but i can't find  any synchronize lock, anything else?

Hello @zxfxpower,
asynchronous could be the answer

Hi @RoySRose
Thanks for  you answer, but I don't find any asynchronous code ,it's all  sequence execute ,can you give an example ,please !

@zxfxpower
asynchronous invocation was one of an example.
To clarify the term 'GAP', click on the question mark on the top right corner of the call stack.
Also, you should find what results the gap in your application. I can't find it for you.

@RoySRose
is it pinpoint miss asynchronous invocation call stack?

@zxfxpower
If you are using the 1.8.0+ then pinpoint will probably trace asynchronous invocation calls


JBEAP-13099 Duplicate record is written in property file when group name set to empty

Changes for JIRA: https://issues.jboss.org/browse/JBEAP-13099
Upstream JIRA: https://issues.jboss.org/browse/WFCORE-3282
Upstream PR: https://github.com/wildfly/wildfly-core/pull/2832

Can one of the admins verify this patch?

@andeyRedhat I don't think this is the right repository for the 7.0.z issue. Please wait for the upstream merge first.

This is OK to test

Full integration - Windows Build 4749 outcome was FAILURE using a merge of 7be344c4c8a93f803a614f15e4ae3e8987313b63
Summary: Exit code 1 Build time: 00:02:45

We're not maintaining the 2.x branch. I commented on JBEAP-13099 re: how the maintenance branch for EAP 7.0.x works.


UnhandledException when ListView doubletapped event should hide ContentDialog

Describe the bug
Please see issue #8136
in my opinion this was closed prematurely. The issue remains as given via comments.
Steps to reproduce the bug
See in #8136
Expected behavior
No response
Screenshots
No response
NuGet package version
None
Windows version
Windows 11 (22H2): Build 22621
Additional context
in my humble option it felt like the issue was closed for the sake of keeping a small number of open issues. Given my descriptions one could see that there are two different outcomes of very similar controls being used.

@TRadigk I've reopened the original issue since it has all the information. Sorry, that should have been activated on your comment.

Thank you ranjeshj, much appreciated.


Cannot save games

Using the "boot1.rom" method to load ROMs instead of using https://github.com/pocomane/MiSTer_Batch_Control makes it so games cannot be saved. Could go back to using MBC, but enjoy the lack of menu flash that the boot1.rom method allows. Looking into options.

Resolve here:
https://github.com/illusion-pasture-program/snesRFID/commit/d090744161f70d448c2a16e713d085f66d90f07c#diff-077612e10649d5cfb9b7b998958c94075f0de59537c8b6fb0aa73ddf6778e80a


Please add documentation for NVIDIA GRID Driver License Type

After lots of frustration and debugging why I couldn't get 2 GPU-powered displays on my Linux NV12s_v3 VM, we finally found that the Azure-provided extension is configuring the license type (aka feature type) to 1 (GRID vGPU), not 2 (GRID Virtual Workstation). The virtual workstation license type is required for multiple monitors.
My request for these docs is to make this configuration option clear to users. The extension configures the NVIDIA control panel to hide the licensing section, so it's really not something you can stumble upon easily. Please update your documentation, explaining how to change the license/feature type, enabling multiple monitors. For us, it involved editing /etc/nvidia/gridd.conf, and setting FeatureType=2. It wouldn't hurt for these Azure docs to also link to a document like this or this, explaining the options and capabilities a bit more clearly.
Finally, I'd also ask that this option be configurable in the extension settings, along with the existing driverVersion setting. This seems like an incredibly fundamental thing to need the ability to configure during the driver installation, instead of forcing users to do it after the fact.

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

ID: 374c8361-9b31-2488-f04b-766e6305c91b
Version Independent ID: aebb9dd3-d1e6-4319-9ab1-0088bd8416e3
Content: NVIDIA GPU Driver Extension - Azure Linux VMs - Azure Virtual Machines
Content Source: articles/virtual-machines/extensions/hpccompute-gpu-linux.md
Service: virtual-machines
Sub-service: hpc
GitHub Login: @vermagit
Microsoft Alias: amverma

@jsmartt - Thanks for bringing this to our attention.
I'm going to assign this to the document author so they can update the document accordingly.

The manual driver installation docs currently recommend removing the FeatureType=0 config parameter from the gridd configuration file (/etc/nvidia/gridd.conf). This appears to have the same effect as setting it to 2.
The NVIDIA GPU Driver Extension docs do not mention this config file. The extension docs are unclear as to what license is set by the extension and what steps are to be taken to troubleshoot the unlicensed state.

Thanks for your dedication to our documentation. Unfortunately, at this time we have been unable to review your issue in a timely manner and we sincerely apologize for the delayed response. The requested updates have not been made since the creation of this issue, and the timeline for resolution may vary based on resourcing, so we've created an internal work item to incorporate your suggestions. We are closing this issue for now, but feel free to comment here as necessary. #please-close


✨ detailed theme validation errors

no issue
Display the detailed validation errors that we get back from gscan so that users know how to fix their theme

add ThemeValidationError to custom ajax error types
intercept failed theme uploads from the uploader component and switch to an "invalid theme" state if we have a theme validation error, otherwise display an error in the upload component as usual

TODO:

[x] styling
[x] tests

@JohnONolan: I've thrown in some very basic styling for now. Any thoughts on what's there (screenshot included above) or is it good enough for now?

👍 🚢


Invalid config for [climate.myicomfort]

Hi, just installed this to a Hassio install (v 0.93.2) and got the following errors:

Invalid config for [climate.myicomfort]: expected float for dictionary value @ data['max_temp']. Got '90 (optional, default = 95)'
expected float for dictionary value @ data['min_temp']. Got '55 (optional, default = 45)'
expected int for dictionary value @ data['system']. Got '0 (optional, default = 0)'
expected int for dictionary value @ data['zone']. Got '0 (optional, default = 0)'. (See /config/configuration.yaml, line 380). Please check the docs at https://home-assistant.io/components/climate.myicomfort/

I believe I have followed the installation instructions to a tee:

Copied contents of  'myicomfort' folder to /custom_components/myicomfort/
Added the sample configuration to my configuration.yaml
Added my icomfort_username and icomfort_password to my secrets.yaml

(can't figure out how to format this correctly in the issue editor - this looks exactly like the sample given in the README.md)
`climate:

platform: myicomfort
name: lennox
username: !secret icomfort_username
password: !secret icomfort_password
system: 0 (optional, default = 0)
zone: 0 (optional, default = 0)
min_temp: 55 (optional, default = 45)
max_temp: 90 (optional, default = 95)`

I figured it out - the parenthetical text (option, default = #) is not supposed to be part of the config.  Deleting that and leaving just the numerical values fixed my error.


Change the examples/ to snake_case

Assigning to Jaime if he has a chance, otherwise I can take a pass next week.

Yes, I have all of this in a separate branch I will push today or tomorrow. I will tackle everything examples related in that one (snake_case, but also some other modern Python practices).

Addressed by #374


Flag and handle inappropriate behavior

Participants always have the ability to leave the experiment by exiting the browser window, but we also want to give them the ability to flag inappropriate or abusive behavior. We will need to decide how to handle these cases in a way that doesn't penalize those who flag the behavior, either by depriving them of earnings or by delegitimizing their concerns.

Leaving the experiment / ejecting from the discussion could be a really strong signal that the discussion is going poorly, and we want to capture that. Unfortunately, if participants just close the browser window, we can't easily determine if this is because they got fed up, or if they had a technical error.
Perhaps we should have a "punch out" button (with a popup confirmation) that lets people end the discussion itself, and then proceed to the exit steps (or the next stage). This would let us ask them for more information about why they left the discussion (I was too upset / the other person wasn't being polite vs. we ran out of things to talk about.) and they could still finish and be paid.

Leave with the option to return
Leave and go to a "why did you leave" page

Link to slides: https://docs.google.com/presentation/d/1tqNtPLgchkRN39DhMCFaoxvHAGffafJtpA9TIMev764/edit?usp=drivesdk

closing in favor of https://github.com/Watts-Lab/deliberation-empirica/issues/423


Add and fetch modules

Positional Encoding  in pytorch
Fetch minor source codes : minor fetches are reported on this issue

#24 merged


Speedup DFSchema::merge using HashSet indices

Which issue does this PR close?

Relates to https://github.com/apache/arrow-datafusion/issues/5637
Rationale for this change

Planning time of Datafusion is slow.
What changes are included in this PR?

Profiling shows that a large part of planning is spent in DFSchema::merge.
Before this PR, merging was complexity O(N * M), where N and M are number of fields in the two schemas.
With this PR, merging is complexity O(N + M) using a HashSet as an index.
Speeds up benchmarks in sql_planner.rs by 18-75%. However, physical planning benchmarks seem to regress by 1.8%. I wonder if that is an acceptable trade?
CC @matthewmturner who seems interested in planning performance

Benchmark results
Gnuplot not found, using plotters backend
Benchmarking logical_select_one_from_700: Warming up for 3.0000 s
Warning: Unable to complete 100 samples in 5.0s. You may wish to increase target time to 6.8s, enable flat sampling, or reduce sample count to 60.
logical_select_one_from_700
                        time:   [1.3324 ms 1.3359 ms 1.3396 ms]
                        change: [-54.725% -54.348% -53.914%] (p = 0.00 < 0.05)
                        Performance has improved.
Found 14 outliers among 100 measurements (14.00%)
  6 (6.00%) low mild
  3 (3.00%) high mild
  5 (5.00%) high severe

physical_select_one_from_700
                        time:   [4.6236 ms 4.6485 ms 4.6795 ms]
                        change: [-75.159% -74.941% -74.735%] (p = 0.00 < 0.05)
                        Performance has improved.
Found 8 outliers among 100 measurements (8.00%)
  3 (3.00%) high mild
  5 (5.00%) high severe

Benchmarking logical_trivial_join_low_numbered_columns: Warming up for 3.0000 s
Warning: Unable to complete 100 samples in 5.0s. You may wish to increase target time to 6.8s, enable flat sampling, or reduce sample count to 60.
logical_trivial_join_low_numbered_columns
                        time:   [1.3504 ms 1.3546 ms 1.3592 ms]
                        change: [-22.854% -22.042% -21.199%] (p = 0.00 < 0.05)
                        Performance has improved.
Found 11 outliers among 100 measurements (11.00%)
  1 (1.00%) low mild
  4 (4.00%) high mild
  6 (6.00%) high severe

Benchmarking logical_trivial_join_high_numbered_columns: Warming up for 3.0000 s
Warning: Unable to complete 100 samples in 5.0s. You may wish to increase target time to 7.1s, enable flat sampling, or reduce sample count to 50.
logical_trivial_join_high_numbered_columns
                        time:   [1.3961 ms 1.4003 ms 1.4051 ms]
                        change: [-21.654% -21.238% -20.848%] (p = 0.00 < 0.05)
                        Performance has improved.
Found 12 outliers among 100 measurements (12.00%)
  2 (2.00%) low mild
  8 (8.00%) high mild
  2 (2.00%) high severe

Benchmarking logical_aggregate_with_join: Warming up for 3.0000 s
Warning: Unable to complete 100 samples in 5.0s. You may wish to increase target time to 9.3s, enable flat sampling, or reduce sample count to 50.
logical_aggregate_with_join
                        time:   [1.8286 ms 1.8331 ms 1.8381 ms]
                        change: [-18.973% -18.543% -18.126%] (p = 0.00 < 0.05)
                        Performance has improved.
Found 8 outliers among 100 measurements (8.00%)
  1 (1.00%) low mild
  6 (6.00%) high mild
  1 (1.00%) high severe

physical_plan_tpch      time:   [5.6537 ms 5.6803 ms 5.7095 ms]
                        change: [+1.1125% +1.7618% +2.3821%] (p = 0.00 < 0.05)
                        Performance has regressed.
Found 9 outliers among 100 measurements (9.00%)
  6 (6.00%) high mild
  3 (3.00%) high severe

Are these changes tested?

Should be in existing tests.
Are there any user-facing changes?

Faster planning.

Nice 😀
Trade off seems worth it.
I'm curious what's going on in that TPCH benchmark though as the other physical select benchmark showed solid improvement so not sure it's all physical planning.

Speeds up benchmarks in sql_planner.rs by 18-75%. However, physical planning benchmarks seem to regress by 1.8%. I wonder if that is an acceptable trade?

I think this is an acceptable trade

Anything I need to do before we can merge this?

Thanks again @simonvandel  and @matthewmturner and @comphead


Reduce HLS startup latency

Currently (v2.4) we try to determine the start time of the first segment in each playlist.  This is time-consuming and adds latency to startup.  There are some details in the HLS spec which we may be able to exploit to reduce this significantly.
This could also allow us to skip timestamp parsing in text cues, which contain no timestamps if empty, or in raw AAC or MP3, which may not have parseable timestamps at all.

For VOD, we may assume that all playlists are aligned, and we only need to get the timestamp of the first segment from one playlist.  https://tools.ietf.org/html/rfc8216#section-6.2.4

If the Playlist contains an EXT-X-PLAYLIST-TYPE tag with the value of VOD, the first segment of every Media Playlist in every Variant Stream MUST start at the same media timestamp.

For live, things are more complicated.
We can't use the media sequence numbers / segment numbers for alignment in a live stream.  https://tools.ietf.org/html/rfc8216#section-6.3.2

A client MUST NOT assume that segments with the same Media Sequence Number in different Variant Streams or Renditions have the same position in the presentation; Playlists MAY have independent Media Sequence Numbers.  Instead, a client MUST use the relative position of each segment on the Playlist timeline and its Discontinuity Sequence Number to locate corresponding segments.

It seems that date-time mappings would help, if present, but they are optional.
https://tools.ietf.org/html/rfc8216#section-6.2.4

If any Media Playlist in a Master Playlist contains an EXT-X- PROGRAM-DATE-TIME tag, then all Media Playlists in that Master Playlist MUST contain EXT-X-PROGRAM-DATE-TIME tags with consistent mappings of date and time to media timestamps.

This would appear to state that playlists need not start at the same point in time in the general case.  But it also seems to say that sync will never be off by more than one segment.
https://tools.ietf.org/html/rfc8216#section-6.2.4

Content that appears in a Media Playlist of one Variant Stream but not in another MUST appear either at the beginning or at the end of the Media Playlist file and MUST NOT be longer than the target duration.

If we assume that the first segment in each live playlist is no more than one segment out of sync with the other playlists, then we can probably just parse one segment.  If our segment indices are off by one segment, we may wind up jumping over a gap or fetching an extra segment at some point.

Also, we probably make multiple network request for the same segments.  The current algorithm is to iterate through each variant and check its audio and video.  This means when streams appear in multiple variants, we make multiple requests.


Unregister algorithm step 6.1 is no longer necessary

Step 6.1 of the Unregister algorithm is:

If registration’s uninstalling flag is unset, invoke Finish Job with job and abort these steps.

I don't think this can ever be true now, though.  The uninstalling flag is now cleared in the Register algorithm which executes within a job.  Since we have a single job queue the flag cannot be cleared until the Unregister job completes.

Pre F2F notes: Confirm this. Seems right.


Move code from Solr git repo to this repo

I believe the DIH code should be removed from Solr main and branch_9x, and added here instead so it can be built and developed independent of Solr.

I believe it has been done...   https://github.com/apache/solr/tree/main/solr/modules and https://github.com/apache/solr/tree/branch_9x/solr/modules do not list the DIH module....

I was going off the readme on this project which says the code is in the Solr repo.  So it's been removed from Solr, but hasn't been added to this repo.  Is this the canonical project for the community DIH?

It is now.  However I suspect some updates to Readme's would be a "good thing".

I see now.  There is a src tree on branch_8x and branch_9x ... I was looking at master and didn't think to check other branches.  Odd, I would have expected code to be added first to the default branch first.


[5.5] Let Blade custom if works with a handler.

Let Blade custom if works with a handler.

This doesn't actually work as you intend. It just calls the given class immediately on Blade::if and never calls it again.


Delete SJW

I have fixed SJW CoC.

There exist more profound and enduring pursuits than spamming.

indeed


Migrate Mirage2 build from bower and compass to yarn and node-sass

References

Recent mailing list post about build issues related to torquebox.org

Description
In short, this pull request replaces bower with yarn and compass with node-sass in order to fix the ancient Mirage2 build when using the "slow" -Dmirage2.deps.included=true maven build.
For more background, the Mirage2 build system uses bower for package management and Ruby sass/compass for SASS processing. Bower has been deprecated for years and is an increasing source of obscure build issues. Compass is Ruby based and requires the user to preinstall Ruby and several gems, or use those provided by JRuby via torquebox.org during build time. As of last week the torquebox.org domain expired and is likely abandoned, making it impossible to build Mirage2.
Instructions for Reviewers
Test building Mirage2 at your site using the -Dmirage2.deps.included=true option to maven. I have tested both vanilla Mirage2 and a slightly modified one with style overrides in dspace/modules/xmlui-mirage2.
List of changes in this PR:

Use eirslett/frontend-maven-plugin to install Node.js and yarn during maven build. JavaScript packages that were previously installed by bower are now installed by yarn.
Remove JRuby and compass stuff from build. Use node-sass as the SASS processor and essentially polyfill the compass SASS mixins using compass-sass-mixins. Allow building with Node.js 12.
Use a static copy of Modernizr.min.js because the version we need is not available on NPM.
Update CI to use latest Node.js 12 and remove useless pre-requisite step (as GitHub CI already has yarn and grunt installed).

Many thanks to @alanorth for this PR. Great job. I readily admit to not understanding this build process, what exactly is happening is beyond me.
I am building from this PR and seeing the following:
[INFO] [2/5] Resolving packages...
[INFO] warning autoprefixer ><EMAIL_ADDRESS>Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
[INFO] warning cssnano > postcss-merge-rules ><EMAIL_ADDRESS>Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
[INFO] warning cssnano > postcss-merge-rules > caniuse-api ><EMAIL_ADDRESS>Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
[INFO] warning cssnano > postcss-svgo ><EMAIL_ADDRESS>This SVGO version is no longer supported. Upgrade to v2.x.x.
[INFO] warning cssnano > postcss-merge-rules > postcss-selector-parser ><EMAIL_ADDRESS>flatten is deprecated in favor of utility frameworks such as lodash.
[INFO] warning<EMAIL_ADDRESS>This NPM package for DataTables has now been deprecated and the 'datatables.net' set of packages should be used in preference to this one. Please see the NPM installation guide for DataTables for more details: https://datatables.net/download/npm.
[INFO] warning grunt-contrib-coffee ><EMAIL_ADDRESS>CoffeeScript on NPM has moved to "coffeescript" (no hyphen)
[INFO] warning grunt-node-sass > node-sass ><EMAIL_ADDRESS>request has been deprecated, see https://github.com/request/request/issues/3142
[INFO] warning grunt-node-sass > node-sass > node-gyp ><EMAIL_ADDRESS>request has been deprecated, see https://github.com/request/request/issues/3142
[INFO] warning grunt-node-sass > node-sass > node-gyp ><EMAIL_ADDRESS>This version of tar is no longer supported, and will not receive security updates. Please upgrade asap.
[INFO] warning grunt-node-sass > node-sass > request ><EMAIL_ADDRESS>this library is no longer supported
[INFO] warning grunt-node-sass > node-sass > request ><EMAIL_ADDRESS>Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
[INFO] warning pixrem ><EMAIL_ADDRESS>Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.

Auto-prefixer is at v. 10 and Cssnano at v. 5, perhaps an opportunity to use latest version of packages?
There's a lot of outdated info in /dspace-xmlui-mirage2/readme.md and while I would never ask you to add information there :) it would be good if you could throw out the obsolete Ruby/Gem stuff. Note also that https://wiki.lyrasis.org/display/DSDOC6x/Installing+DSpace links to that readme file to give instructions on how to pre-install dependencies.
Builds fine, with no problems. Runs fine in docker and opens up and yes, it's Mirage2.
I can't easily apply massively modified Mirage2 frontends. @alanorth , if there are specific instructions you would recommend?

@J4bbi thank you for testing. I tried a modified Mirage2 by adding a custom CSS rule here:

dspace/modules/xmlui-mirage2/src/main/webapp/themes/Mirage2/styles/_style.scss

Regarding autoprefixer and cssnano, actually those are not used by vanilla Mirage2, but they were introduced on our site. I should technically remove them from this PR since that is not in the scope!

@J4bbi I've removed the autoprefixer, cssnano, and postcss stuff, as it was not relevant for this PR. Please try again! Also, I've updated the Mirage2 readme (that reminds me, I will need to update the installation notes on the wiki when this gets merged).

Closing this PR in favor of a newer one: https://github.com/DSpace/DSpace/pull/8292
The newer one uses npm directly instead of yarn, which means one less thing we need to install to build Mirage 2. As a bonus, npm comes with the Node.js distribution so users will already have it once they install Node.js.


nftables options in FelixConfiguration

Description

Add nftables specific options to FelixConfiguration.
There are a few ways we could go about this:

Simply add new NftablesFoo fields alongside the equivalent IptablesFoo fields.
Add a new Nftables sub-section to FelixConfiguration to group config.
Deprecate old IptablesFoo fields and introduce generic Foo fields for both.

For now, I've opted for option #1, but open to opinions on alternatives or arguments for other approaches.
Related issues/PRs

Todos

[ ] Tests
[ ] Documentation
[ ] Release note

Release Note

TBD

Reminder for the reviewer
Make sure that this PR has the correct labels and milestone set.
Every PR needs one docs-* label.

docs-pr-required: This change requires a change to the documentation that has not been completed yet.
docs-completed: This change has all necessary documentation completed.
docs-not-required: This change has no user-facing impact and requires no docs.

Every PR needs one release-note-* label.

release-note-required: This PR has user-facing changes. Most PRs should have this label.
release-note-not-required: This PR has no user-facing changes.

Other optional labels:

cherry-pick-candidate: This PR should be cherry-picked to an earlier release. For bug fixes only.
needs-operator-pr: This PR is related to install and requires a corresponding change to the operator.

Thanks @fasaxc !
I pushed a new commit which addresses the defaulting, and also fixes up a few other names that wrongly had Iptables prefixes.