Pre-publish Tab and Checklist

Feature description
The helper tool is not fully described yet (if at all), but we're assuming it will contain some kind of smart positioning of elements in a grid, perhaps with margins.
The pre-publish checklist is a list with critical and recommended idea. Easy to visually make, but complex to create. UX and product has lead on this.
Product question: Should we think about opening this up to extension early? Should other plugins be able to provide items and rules for this checklist?
Product brief
Figma

Do not alter or remove anything below. The following sections will be managed by moderators only.
Acceptance criteria

The helper component is created (framework, not including the canvas)
Additional helper features are able to be added in future tickets
The test for missing alt text is implemented
I am able to see if the post is live or not
I am able to view the post (story)
I am able to copy a link to the story
I am able to embed my story in a newly published WordPress post
I am able to embed my story in a newly drafted WordPress post
The checklist tells me if I am missing a feature image
The checklist tells me if a poster image is missing
See #50 for multi resolution check on checklist

OLD AC (Additional tickets for the Helper Tool will be created) :

Helper is a mode that the user can turn ON and OFF to get design guidance.
After helper mode is turned on, the user sees visual guidance as they create their story.
The Pre-publish helper is shown on the right hand side under the Checklist Panel tab.
The same guidances from the helper are shown in the Checklist.

Implementation brief

QA testing instructions

Demo

Changelog entry

@samitron7 is the helper tool gone and is it just the prepublish tab now?

@jauyong The helper tool is not gone but not a feature we'll expose till after stable. For now we'll go with the simple pre-publish list. Just hopping on to answer questions but I added this to my queue.

One thing to include:

video too large to display (total resolution) can't be above 4K (or iPhones/top tier Androids) won't be able to play this.

Drafted brief waiting for reviews.

Just reviewed and left comment. On UX side, we basically need a list.
"For each detected error, the checklist should make it easy to find the error by letting the user directly go to the page and element where the error is found, or allow direct fixing (e.g., if missing title allow directly adding a title)"
@omar can you confirm if we're doing the above for stable versus a pure list you can't click on. The original design supported this but I removed it.

Confirmed that it is in scope. Moving this to the UX queue given that most feedback is addressed.

@carlos-kelly  to speak with @barklund on the technical feasibilty of north star

@barklund @carlos-kelly Please get back to me once you guys scope out what's possible as I may need to create a stop gap design for this.

@barklund / @carlos-kelly following up on this - have you spoken about this ?

Have no idea what's required for this one. UX is still pending.

Discussed during call, @barklund will estimate - but pushing to be post 1.0 Stable.
We should turn this into an epic to have:

ticket for basic tab setup
ticket for each general bucket/type of validations (errors, warnings, guidance)

That would make it easier to estimate overall.

EAP feedback: a link to AMP Test tool with story URL pre-filled on dashboard or editor would be helpful. I.e. https://search.google.com/test/amp?url=<encoded_story_url>

HI @o-fernandez and team,
Designs for the Pre-publish checklist (MVP version) are ready for your implementation.
Figma File: https://www.figma.com/file/NHHMwIfxMnz39NxqkrFb7R/Stories---Post-Stable?node-id=1684%3A0
Please let us know if you have additional questions.


Panic on formatting SQL with multibyte chars and leading non-printing characters

https://github.com/launchbadge/sqlx/issues/831
It looks like sqlformat chokes on the first query here:
let query = "\nSELECT 'главная'"; // bad query
// let query = "SELECT 'главная'"; // good query
// let query = "\nSELECT 'main'"; // good query

Panic location: sqlformat-0.1.4\src\tokenizer.rs:157:37

Thanks for the report! Fixed in 0.1.5.

Thank you!


Graph.removeEdge() for edges with index

Looks like we need a more-specific version of Graph.removeEdge() for edges with index.

Moved to https://github.com/flowbased/fbp-graph/issues/2


Add toolchain runenvs in run action

Before adding new features and new modules, please go to issues to submit the relevant feature description first.
Write good commit messages and use the same coding conventions as the rest of the project.
Please commit code to dev branch and we will merge into master branch in feature
Ensure your edited codes with four spaces instead of TAB.

增加新特性和新模块之前，请先到issues提交相关特性说明，经过讨论评估确认后，再进行相应的代码提交，避免做无用工作。
编写友好可读的提交信息，并使用与工程代码相同的代码规范，代码请用4个空格字符代替tab缩进。
请提交代码到dev分支，如果通过，我们会在特定时间合并到master分支上。
为了规范化提交日志的格式，commit消息，不要用中文，请用英文描述。

So I think found out why it's failing. It join some env by the env separator C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.37.32822\include in the same table element of pathenv. I don't have the time to debug more today, I will do it tomorrrow.


Preventing actions for specific commands

I have a event handler registered for ivy.events.Event.EXIT that copies figure files from src/*/whatever to docs/*/whatever. I want it to run for ivy build and ivy watch, but not for ivy clear. What's the right way to ensure this?

Probably best to register it on the EXIT_BUILD event:
https://github.com/dmulholl/ivy/blob/64ab5c1dbc58c5cacefa365a07ce06ff7ddfbb2f/ivy/cli/build.py#L56

:+1: I'll give it a try.

Good stuff. The build command fires its own set of build events: INIT_BUILD, MAIN_BUILD, and EXIT_BUILD. They're the ones you want to use for anything purely related to building the site.
The watch command ultimately calls the build command so it fires the same set of hooks for each build.

thanks. BTW, I'm with http://deepgenomics.com these days, and we're hiring Python programmers... :-)

works - thank you

Ooooh, that's a really interesting area to work in, pet interest of mine. I've just accepted an offer from a self-driving car company in Berlin, otherwise I'd be all over that. I'll keep an eye on you guys for for future opportunities :)


Release 2.3.2

[x] Towncrier
[x] pyproject.toml
[x] poetry.lock
[ ] https://github.com/nautobot/nautobot/pull/6175 - approved
[ ] https://github.com/nautobot/nautobot/pull/6167
[ ] https://github.com/nautobot/nautobot/pull/6160

Should we include any of the current open PRs against develop in this release?

Should we include any of the current open PRs against develop in this release?

Added some prs in the description that I think should be merged before the relesae


Dynamic Mini map.

Greetings, I have a idea that I would like to present, the mini map takes all of the assigned position vertically, this means that if you don't have alot of code vscode mimi map still take all vertical space and it can block the view of code that is long horizontally, I would suggest a dynamic mini map layout that does not take all the vertical view unless there is code there.

Please check if one of the editor.minimap.size options already cover your use-case.

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!


[TEST]-Increased timeout of the test method concurrentSyslogMessageTest()

Build Completed
:fire: This pull request has some issues. It would be preferable to fix them in order for it to be just perfect. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
ant -Dtestreports.dir=bin/reports/unit-test -f engine/build.xml clean-all resolve jacoco && ant -f engine/build.xml checkstyle publish-local

Cleanup Commands
rm -r ~/.ivy2/local || echo no publish local to remove

Changed files
  engine/test-src/org/pentaho/di/trans/steps/syslog/SyslogMessageConcurrentTest.java

Newly Fixed Tests:
org.pentaho.di.trans.steps.syslog.SyslogMessageConcurrentTest.concurrentSyslogMessageTest:
:large_blue_circle: org.junit.runners.model.TestTimedOutException
org.junit.runners.model.TestTimedOutException: test timed out after 2000 milliseconds
	at java.lang.Class.getName0(Native Method)
	at java.lang.Class.getName(Class.java:642)
	at org.objenesis.ObjenesisBase.getInstantiatorOf(ObjenesisBase.java:89)
	at org.objenesis.ObjenesisBase.newInstance(ObjenesisBase.java:73)
	at org.mockito.internal.creation.instance.ObjenesisInstantiator.newInstance(ObjenesisInstantiator.java:14)
	at org.powermock.api.mockito.repackaged.ClassImposterizer.createProxy(ClassIm

Unit test coverage change
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.
org.pentaho.di.job.entries.evaluatetablecontent.JobEntryEvalTableContent

Branch Change:  + 1.01%
Complexity Change:  + 1.06%
Instruction Change:  + .17%

org.pentaho.di.job.entries.sql.JobEntrySQL

Instruction Change:  + 3.28%
Line Change:  + 3.87%

org.pentaho.di.job.entries.syslog.SyslogDefs

Branch Change:  + 23.53%
Complexity Change:  + 11.11%
Instruction Change:  + 5.64%
Line Change:  + 14.93%
Method Change:  + 33.33%

org.pentaho.di.job.entries.waitforsql.JobEntryWaitForSQL

Branch Change:  + .66%
Complexity Change:  + .93%
Instruction Change:  + .13%

org.pentaho.di.trans.step.StepMeta

Instruction Change:  + .19%
Line Change:  + .26%

org.pentaho.di.trans.steps.combinationlookup.CombinationLookupMeta

Instruction Change: -.04%:small_red_triangle_down:

org.pentaho.di.trans.steps.csvinput.CsvInputMeta

Instruction Change:  + .05%

org.pentaho.di.trans.steps.dimensionlookup.DimensionLookupMeta

Branch Change: -.31%:small_red_triangle_down:
Instruction Change: -.06%:small_red_triangle_down:
Line Change:  + .23%
Method Change:  + 1.02%

org.pentaho.di.trans.steps.groupby.GroupByMeta

Branch Change: -3.12%:small_red_triangle_down:
Complexity Change: -3.16%:small_red_triangle_down:
Instruction Change: -.28%:small_red_triangle_down:
Line Change: -.74%:small_red_triangle_down:

org.pentaho.di.trans.steps.ifnull.IfNullMeta

Branch Change:  + 2.00%
Complexity Change:  + 1.89%
Instruction Change:  + .17%

org.pentaho.di.trans.steps.insertupdate.InsertUpdateMeta

Instruction Change: -.05%:small_red_triangle_down:

org.pentaho.di.trans.steps.ldapoutput.LDAPOutputMeta

Instruction Change: -.06%:small_red_triangle_down:

org.pentaho.di.trans.steps.memgroupby.MemoryGroupByMeta

Instruction Change: -.18%:small_red_triangle_down:
Line Change: -.48%:small_red_triangle_down:

org.pentaho.di.trans.steps.replacestring.ReplaceStringMeta

Instruction Change:  + .07%

org.pentaho.di.trans.steps.rowgenerator.RowGeneratorMeta

Instruction Change: -.08%:small_red_triangle_down:

org.pentaho.di.trans.steps.setvalueconstant.SetValueConstantMeta

Instruction Change: -.14%:small_red_triangle_down:

org.pentaho.di.trans.steps.singlethreader.SingleThreaderMeta

Instruction Change: -.10%:small_red_triangle_down:

org.pentaho.di.trans.steps.syslog.SyslogMessage

Branch Change:  + 20.00%
Complexity Change:  + 4.76%
Instruction Change:  + 21.47%
Line Change:  + 22.08%
Method Change:  + 16.67%

org.pentaho.di.trans.steps.webservices.WebServiceMeta

Branch Change: -1.79%:small_red_triangle_down:
Complexity Change: -1.19%:small_red_triangle_down:
Instruction Change: -.07%:small_red_triangle_down:


Wait pending translation parts

Hello,
I have a problem with angular translate part loader.
Context
I have one directive in another (parent and child).
I add a part json file with the following code in the parent directive :
  $translatePartialLoader.addPart('pages/news');
  $translate.refresh()

Then, in the child directive, I would like to be sure translation part  is loaded before to use $translate.
Problem

I can't easily use $translateRefreshEnd in child directive, because if event is emitted before child directive load is complete, child directive never receive the event.
I can't use $translate.refresh().then() because I do the refresh in parent and I need to wait pending parts in child.

A possible solution
To solve the problem, I think to a function like that :
 $translate.whenAllPendingPartLoaded(function () {
     // Guaranty that there is no pending parts, so I can use my part safely
     $translate('sentence.in.my.part', function () {});
 });

If there is no pending parts, the callback is called immediately, else, the callback is called when all pending parts are loaded.
Question
What do you think about that ?
Note :

This issue have some similarities with https://github.com/angular-translate/angular-translate/issues/663.
Sorry for my bad english, I'm french :s

Jérémie C.

If you have to call the service $translate directly, you should install a local listener for translateRefreshEnd ensuring it can refresh your directive's texts (this fixes language changes in the future including running changes while evaluating/compiling the directive). Be sure to add appropriate listeners for every parameters (for the translations) if they exist. In addition to the initial translation (on compile, postlink, controller) you should cover everything.
You can avoid installing the listener when using the translate directive and filter directly (i.e. in the template).


Enable TestDiscovery again (followup of #14598)

Problem
This PR tries to enable back TestDiscovery by fixing the test runner to have a mechanism to wait for the accessory advertisement, which should prevent the mdns browse operations to finish because of the cross-talk mdns advertisement that are caught before the app has a chance to emit its own.
Change overview

Add a callback to the dnssd platform code to know when the mdns advertisement is effective. On some platforms, such as Darwin it may takes quite some time depending on how busy is the app
Move some chip-tool and examples/placeholder delay commands into src/app/tests/suites/commands/delay
Extend DelayCommands with WaitForOperationalAdvertisement and WaitForOperationAdvertisement
Use them in TestDiscovery instead of some delays
Enable back TestDiscovery

Fast tracking, given this is re-enabling testing.


Add NumericUpDown control

Note that the Value property is of type Nullable, since the underlying Avalonia control was recently reworked to treat an empty entry as null (https://github.com/AvaloniaUI/Avalonia/pull/8259).
In a Fabulous context, is a nullable Value property the desired behavior for this control? Unlike the Date and Time picker controls, a non-nullable value for NumericUpDown cannot be enforced solely by the constructor, since the user has the option to manually clear the input via keyboard entry. (Note also that watermark visibility is contingent on the Value property being nullable.)

Awesome 👍 . Thanks


Add info about needing to accept self-signed cert, fix test user

previous attempt: adding white spaces between the lines and indenting the code blocks
next attempt: adding 2 spaces not before the dash but after the dash...

so apparently this is what it wanted, but the error message was not helpful... why so many spaces ?!
anyway, I bowed to this bot's will now after losing my sanity
squashing...

@PVince81 please rebase

rebased


fix: added more line tests

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


list Github issues URL on beyondgrep community page ?

If we want suggestions & bugs to appear here and questions on the mailing lists, maybe the /community/ page should list the github /petdance/ack2 or /petdance/ack2/issues there with description of what's appropriate ?

migrated to https://github.com/petdance/beyondgrep/issues/43


69 deprecation warnings need dealing with

Fixing deprecation warnings that have been exposed by the test suite.

Codecov Report

Merging #71 (2b84d79) into main (df3105c) will increase coverage by 0.03%.
The diff coverage is 83.33%.

@@            Coverage Diff             @@
##             main      #71      +/-   ##
==========================================
+ Coverage   82.87%   82.90%   +0.03%
==========================================
  Files          30       30
  Lines        3358     3364       +6
==========================================
+ Hits         2783     2789       +6
  Misses        575      575

Impacted Files
Coverage Δ

clarity/enhancer/gha/gainrule_camfit.py
92.46% <ø> (ø)

clarity/predictor/torch_msbg.py
80.27% <70.00%> (ø)

clarity/data/HOA_tools_cec2.py
96.85% <100.00%> (+0.06%)
:arrow_up:

clarity/data/scene_renderer_cec2.py
91.61% <100.00%> (+0.16%)
:arrow_up:

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

@ns-rse this PR is just dealing with some minor deprecation warnings that were caught by the test suite. Nothing very important but some of them would have led to problems later. We might as well merge this into main before releasing v0.1.0


.Net: Allow the endpoint parameter in AddHuggingFaceChatCompletion to be optional

Motivation and Context

Ensure that the parameters related to the endpoint in AddHuggingFaceChatCompletion and AddHuggingFaceImageToText provide a consistent development experience.
Description

HuggingFaceChatCompletionService removed the check that ensures the endpoint value is not null, so that both HuggingFaceChatCompletionService and HuggingFaceImageToTextService follow the same logic. This is because both services ultimately use HuggingFaceClient, and HuggingFaceClient already has a default URI internally: https://api-inference.huggingface.co/.
Contribution Checklist

[v] The code builds clean without any errors or warnings
[v] The PR follows the SK Contribution Guidelines and the pre-submission formatting script raises no violations
[v] All unit tests pass, and I have added new tests where possible
[v] I didn't break anyone :smile:

Hi @RogerBarreto
My sample code for ChatCompletion and image-to-text uses the same public API endpoint 'https://api-inference.huggingface.co/', but the development experience is different. ChatCompletion requires the endpoint to be explicitly specified, even though both use the same public endpoint.
//ChatCompletion
var kernel = Kernel.CreateBuilder()
.AddHuggingFaceChatCompletion(
endpoint: new Uri(Config.huggingface_endpoint),  //https://api-inference.huggingface.co/
model: model,
apiKey: Config.huggingface_apiKey)
.Build();
// ImageToText
var kernel = Kernel.CreateBuilder()
.AddHuggingFaceImageToText(
model: imageToTextModel,
apiKey: Config.huggingface_apiKey)
.Build();
ref api doc : https://huggingface.co/docs/api-inference/tasks/chat-completion?code=curl

Hi @iangithub, thanks for the extra info, good to see they are now supporting it publicly