Enhance Documentation

[ ] Breaking change? (if so, please describe the impact and migration path for existing application instances)

What changes did you make? (Give an overview)

Update docs to help Apple Mac M1 Users
Update missing information about building react app
Update prerequisites docs

Some of the steps from building and running document were overlapping and causing some confusion thus I propose to have one file as currently as our steps are limited.
There were some steps missing for Apple macOS M1. Included them.
Is there anything you'd like reviewers to focus on?
How Has This Been Tested? (put an "x" (case-sensitive!) next to an item)

[x] No need to
[ ] Manually (please, describe, if necessary)
[ ] Unit checks
[ ] Integration checks
[ ] Covered by existing automation

Checklist (put an "x" (case-sensitive!) next to all the items, otherwise the build will fail)

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation (e.g. ENVIRONMENT VARIABLES)
[x] My changes generate no new warnings (e.g. Sonar is happy)
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged

Check out Contributing and Code of Conduct
A picture of a cute animal (not mandatory but encouraged)

Hii this PR looks good and answers all the trouble we faced during building the app without docker. Till the time it is merged can anybody just reference it in the documentation or is there a timeline for it to be merged?

@JIBIN-P merged

@shubhwip thank you very much


[BUG] Incorrect redirect url after payment with STRIPE

Describe the bug
After making a payment with STRIPE user is redirected to "http://shop.backend.url/payment/finalize-transaction
instead of http://shop.frontent.url/order/###
The call to /pay endpoint contains the proper URL, however, stripe receives a payment object with the wrong redirect URL.
In a result, user lands on "classic" storefront channel, not PWA
Disabling this channel leads to 500 error on both redirect and webhook calls.
This may be problem with stripe plugin, not shopware-pwa, but any help will be greatly appreciated :)
Additional context
Shopware <IP_ADDRESS>
phopware-pwa 0.8.1
PWA Integration (v0.2.1)

Actually, this is working properly, you need the /payment/finalize-transaction endpoint to be available as it will eventually emit a 301 redirect back to your client, after updating the payment state. We are trying to figure out another day of doing this, but for the moment, it is the only way to inform Shopware about the payment status. Stripe should not redirect straight to your PWA, as Shopware wouldn't be able to know about anything that happened in the meantime.

@elkmod
I'm petty sure, webhooks are for this purpose and they are triggered async and headless in most cases.
Webhooks are in fact most important way of communication between payment gates, as allow delayed approval, chargeback and other scenarios without user interaction. (eg. browser dies, user closes browser or navigates away)
Redirect is meant for end user consistent flow, and it is not needed for shopware to handle payment. Yes I know it contains payment details (if completed) but it is supplementary (and we can also decode it on PWA if we choose to)
As for the /payment/finalize-transaction endpoint, it redirects user to login screen, so there goes redirection...
If I am talking nonsense, I am sorry. But I have tested it, by blocking redirection in browser and payment was registered in shopware. Unless I messed up something :)

any further comments, feedback?
If I'm wrong,  ELI5

Anyone willing to help me?
Bug or not aside, how to prevent user being stopped at login page after payment callback.

hi @cruonline, in the upcoming release we've got it done like it's here: https://github.com/vuestorefront/shopware-pwa/blob/master/packages/default-theme/src/pages/checkout.vue#L190

we are calling handlePayment with success and failure page's provided as the parameters.
notice we are using getAbsoluteUrl method that generates the whole PWA URL like "http://localhost:3000/en-US/success".

Under the hood, the handle-payment endpoint passes these urls to the specific payment provider to get them know what's the URL the customer has to be redirected in success/fail scenarios (special token is generated to identify the config).
After the payment is done, the payment provider redirects the customer to finalize-transaction of API and then to the one of provided URLS (finishUrl or errorUrl in handle-payment method)
I recommend you to follow this flow and see what will happen 👍🏻 let us know if it's working :)

thanks @mkucmus , I will give it a try.
Keep up the good work!


Fails on main branch

https://github.com/damacus/check-chef-metadata-action/blob/3b3a50e04db7d5296d360eaaa940862047c33cd9/src/main.ts#L11
We are getting failures on main branches for some reason, https://github.com/sous-chefs/postgresql/actions/runs/5301412531/jobs/9595660978
report_checks: true
comment_on_pr: true
Reading metadata file: metadata.rb
Reporting the results of the checks to the PR
Message: {"name":"Check Metadata","message":"Metadata matches","conclusion":"success","summary":["Metadata validated"],"title":"Metadata validated"}
Error: Cannot find the PR id.
Error: Invalid request.

"head_sha" wasn't supplied.

nope @damacus


Added basic touchbar implementation for query screen

Status
Type

:x: Hold
Feature

Description
This PR adds the possibility to use the Touch Bar of a MacBook for certain operations. Currently the following are implemented.
If you have some other ideas where the Touch Bar could be useful. Feel free to comment below.

[x] Query-screen
[ ] Dialogs

Motivation and Context

Screenshots / GIFs (if appropriate):

Checklist

[x] I have read the CONTRIBUTING document.
[x] I have considered the accessibility of my changes (i.e. did I add proper content descriptions to images, or run my changes with talkback enabled?)
[x] I have documented my code if needed

Resolves

You could add a button to switch the card (and show the solution)


I use less in my projects and do not know the configuretion for webpack.config.js

Check the version of package you are using. If it's not the newest version, update and try again (see changelog while updating!).
If the issue is still there, write a minimal project showing the problem and expected output.
Link to the project and mention Node version and OS in your report.

IMPORTANT! You should use Stack Overflow for support related questions.

Please submit support requests and questions to StackOverflow using the tag [webpack]. StackOverflow is better suited for this kind of support though you may also inquire in Webpack Gitter. The issue tracker is for bug reports and feature discussions. See also our CONTRIBUTING guidelines.


VGA mode is no longer compliant with LG screens

The default VGA mode with cable detect is now causing issues with LG TVs. Previous firmware did not have this issue and functioned normally. This issue would be solvable if the WiFi password was static and not dynamic or there was a way to access this without using the OSD.
This issue has been confirmed on a 65C9 OLED, 65G7 OLED, and a 10 year old LG 21" LCD TV. The 10 year old TV does not have the ability to perform firmware updates and is stuck on the factory firmware.

Also found this issue on the following TV's.
Sony XBR75850D 4K
Toshiba 46SV670U
Both of these work if you change from VGA to another resolution and save. The LG OLED C9 also will work as long as it's not VGA. The G7 will not work at all.

There was a bug in the initialization sequence occurring when the output resolution was set to VGA and the video mode was set to Cable Detect, which resulted in no image being shown. This is fixed and will be released to the firmware update server soon. Version is v2.3.3 for standard and v3.0.3 for relaxed.

This is no longer occurring in v2.3.4 and v3.0.4.


Configure TypeScript to target ES2017

We're currently targetting ES6 (=ES2015). As a result we're compiling away async/await functions, and probably a few more things. It may be having performance consequences, and also increasing the size of our packages. I think we can safely target ES2017, since it's supported fine in Node 10. See node.green for the detailed support information.

This reduced the size of the compiled JavaScript code by about 10%.


remove extra-lazy collection fetching

This is a proposal to remove support for @LazyCollection and in particular @LazyCollection(EXTRA).
Important note: as a side-effect we lost most of the support for "queued" collection operations, something that someone (@gbadner?) clearly put some work into.
Am I right in understanding that queued puts were only for extra-lazy collections, or did I screw up?

A thought to potentially rescue some of this functionality: instead of having collections being defined as extra-lazy, we could allow certain operations to be performed via static methods of the Hibernate class, e.g:
Hibernate.getSize(my.getItems())

Or:
Hibernate.contains(my.getItems(), item)

Or
Hibernate.remove(my.getItems(), item)

Or:
Hibernate.put(my.getMap(), key, value)

This would be much more useful than the previous functionality, though of course I would not be able to delete quite as much code.
Thoughts?

So apparently there is some evidence that this is a feature some people actually use.
If that's the case, I don't think it's critical to remove it, and I'm withdrawing this proposal for now.


Set up continuous integration

This is a work in progress. Please DO NOT MERGE YET.

test

Ready for your review

DataTransferKitOperators_SplineInterpolation_test_MPI_4 is failing

I recommend merging this commit and deal with the test failure separately

CDash server is here

One question here:
How does docker/configure_trilinos.sh get updated if we change which Trilinos packages we are using? Do we have to do this manually? If so do we see this in a pull request I guess and the build will fail if the file hasn't been updated?

this all have to be updated manually
note that it involves updating the docker image dtk-stk which provides the pre-built environment for the regression


submitPayment method is super slow and Throw exception as BadNonce

I am using @kinecosystem/kin-sdk-v2 version 0.5.0 SDK
I have two issue with submitPayment method

Getting super slow response approx 2 to 3min
Sometimes get BadNonce exception

return new BadNonce("", txId);
                   ^

BadNonce
    at errorFromProto (path\node_modules\@kinecosystem\kin-sdk-v2\dist\errors.js:90:20)
    at Object.errorsFromSolanaTx (path\node_modules\@kinecosystem\kin-sdk-v2\dist\errors.js:18:17)
    at path\node_modules\@kinecosystem\kin-sdk-v2\dist\client\internal.js:346:58
    at Object.onReceiveStatus (path\node_modules\grpc\src\client_interceptors.js:1212:9)
    at InterceptingListener._callNext (path\node_modules\grpc\src\client_interceptors.js:568:42)
    at InterceptingListener.onReceiveStatus (path\node_modules\grpc\src\client_interceptors.js:618:8)
    at callback (path\node_modules\grpc\src\client_interceptors.js:847:24)

I am using passing following options to submitPayment method
const txId = await kinClient.submitPayment(
    {
      sender: privateKey,
      destination: publicKey,
      type: TransactionType.P2P,
      quarks: kinToQuarks(kinAmount),
      invoice: {
        Items: [
          {
            amount: kinToQuarks(kinAmount),
            description: "kin spent or p2p",
            sku: new Date().getTime().toString(),
            title: "kin spent or p2p",
          },
        ],
      },
    },
  );

Hi. Thanks for submitting this issue. We think this is due to issues on the Solana end. They are taking a bit of a battering at the moment in terms of performance.
https://analytics.solscan.io/public/dashboard/8d888828-baae-47b9-948b-d087e5de1411?select_report_period=past30days

For context, we really want this to be over 2000:

https://explorer.solana.com/

So what can be done related to this?
Do we need to raise issue with solana? If yes then where and how to generate issue with the solana?

Hi. It looks like this is something Solana is aware of and a fix is coming. Link for some context: https://twitter.com/aeyakovenko/status/1512551478883405834

There's some chat about this on our developer discord if you're not there already: https://discord.gg/kdRyUNmHDn


WIP: rb-nutshell

After an initial s/Perl 5/Ruby/g, I went through and did some edits. I left just a touch of the original "you are upgrading from 5 to 6" style language in at the top to illustrate how biased the existing 5to6 documents are -- separately I'll propose renaming them to "5vs6".
TODO:

Objects!

I'm not going to merge this without some discussion.  Ruby isn't Perl after all.

My 2 cents on this is have a separate $foo in a nutshell set of docs somewhere else. Personally, I'd even put Perl 5 docs somewhere other than http://docs.perl6.org/language.html

I can host this elsewhere if we don't want it here. But my thoughts:

Ruby is the next-closest language to Perl 5 and Perl 6 (IMO)
Perl 6 is much closer to Ruby than to Perl 5 in many ways, especially when it comes to objects-all-the-way-down
Lots of Perl 5 devs have become Ruby devs; maybe they'd be interested in Perl 6 (anecdotal)
I chopped down the intro text a lot -- it was basically tongue-in-cheek Perl 5 advocacy to leave it in which I didn't plan on keeping, sorry if it was distracting
Nutshell rosetta-stone guides are a great way to show people what is the same between languages; having Python as the next one would be great (but I don't know Python as well)

I guess it's this -- I've been going around telling everyone that Perl 6 is a different language than Perl 5, and that Perl 5 isn't end-of-life, and that they should learn Perl 5 AND Perl 6 just like they should learn Ruby and Python and Rust etc. That everyone should learn from and build off one another.
Here we have another language with overlapping community (I hear Perl is big in Japan!) and philosophy (TIMTOWTDI !) -- this document and the concept behind its existence aims to embrace the overlap with Ruby and enhance the distinction between Perl 5 and Perl 6 as separate entities.
As we add more Inline::* and start doing like use ActiveRecord:from<Ruby> or use matplotlib::pyplot:from<Python> we'll want to share more and more of the joy! Let's get started :)

You make a good point about many Perl 5 devs who moved to Ruby some time ago.... To be clear,  I ment we should have some sort of the subfolder where all the nutshells for other languages are,  not hosted entirely somewhere else. And my reasoning is that after I go to docs.perl6.org and click Language Reference & Tutorials I see nothing but p5 stuff, in which I'm not interested. And now there's a proposal to add Ruby to that list as well shrug :)

I'm all for having this on the doc site. #114 proposes a good organization for the doc site that will accommodate more types of documentation. I wanted to try to work on that but my work on the doc site in general is stalled on making my branch of Pod::To::HTML performant enough to be usable.

*see nothing but p5 stuff on my phone >_< GitHub mobile is terrible

@autarch Yeah, I want to work on #114 also, but haven't gotten around tuit. I agree @zoffixznet -- I might polish this a bit more, but then maybe we can tackle the restructure so it has a reasonable place to live (can be left pending or I can put it in a subdir in the meantime, I don't know what the builder will do with that).

As a general point, I think having $language-to-Perl6 guides is a good idea. If we wind up getting a bunch, I don't have a problem with putting them in a dedicated directory.

Re. $lang-to-P6, Ruby has some brief Ruby-to-$lang docs at https://www.ruby-lang.org/en/documentation/ruby-from-other-languages/ which may be worthwhile to emulate for Perl 6.

@awwaiid I haven't yet carefully read all of rb-nutshell.pod, but it looks good so far (nice writing), and I think it's a great idea. Would be good to see a python-to-p6 nutshell doc as well.
Also, I think the $lang-to-P6 docs should have their own page linked to from https://doc.perl6.org/. At least, I don't think they really belong under https://doc.perl6.org/language.html.
As for feedback on the document itself:

method call: what about the colon syntax? (I don't much Perl 6, but I thought the colon (instead of parens) was used for method calls.)
I think your examples of hash access should show %h{'foo'}, before showing the shortcut %h<foo>.
twigils: can they go after @ and % as well? You've only got them after $.
in the array indexing/slicing section, you mention adverbs in the text, but don't explain/show what they are.
I'd remove the "Just to be confusing" phrase.
You might add a section on Pairs, since it's used in this doc.
What is "Blue Tiger"?

What's the status of this pull request?

I am supposed to help make a directory for it to live in, which includes
reworking some of the main doc processor. I guess what I should do is make
the directory and put this in there, even unkinked, and see what happens
(separate out the two tasks).
Further prs would follow to continue building the ruby programmer guide to
p6.
On Mar 5, 2016 07:12, "Ahmad M. Zawawi"<EMAIL_ADDRESS>wrote:

What's the status of this pull request?
—
Reply to this email directly or view it on GitHub
https://github.com/perl6/doc/pull/288#issuecomment-192627899.

Bump.
What about merging this first and then creating a separate directory?

I would be totally happy to merge this as-is and go from there.

I'm with the general principle of creating a new section within the docs that can contain this and the P5 stuff, however I do think that we could get bogged down in how to do this for ever, so totally with @AlexDaniel's point about merging this as-is now and worrying about the rest later.
So I think I'd be minded to merge this now unless anyone else has anything to add.

I'll go through and fix the things I commented on and then merge it, hearing no objections.

Sounds good!


[FUSE] Merge main

Merges main into the fuse branch

Basically doing a fuse operation on main and fuse branch.

Actual src changes fixed in conflicts:
both modified:   src/Compiler/Microsoft.CodeAnalysis.Razor.Compiler/src/Language/CodeGeneration/CodeWriterExtensions.cs
both modified:   src/Compiler/Microsoft.CodeAnalysis.Razor.Compiler/src/Language/CodeGeneration/RuntimeNodeWriter.cs
both modified:   src/Compiler/Microsoft.CodeAnalysis.Razor.Compiler/src/Language/Components/ComponentRuntimeNodeWriter.cs
both modified:   src/Compiler/Microsoft.CodeAnalysis.Razor.Compiler/src/Language/DefaultRazorIntermediateNodeLoweringPhase.cs
both modified:   src/Razor/src/Microsoft.AspNetCore.Razor.ProjectEngineHost/Serialization/MessagePack/Formatters/RazorConfigurationFormatter.cs
both modified:   src/Razor/src/Microsoft.CodeAnalysis.Razor.Workspaces/ProjectSystem/FallbackRazorConfiguration.cs
both modified:   src/Razor/src/Microsoft.VisualStudio.LanguageServices.Razor/ProjectSystem/DefaultWindowsRazorProjectHost.cs
both modified:   src/Shared/Microsoft.AspNetCore.Razor.Serialization.Json/ObjectReaders.cs


Enhance Logo Visibility in Bright Mode

Fixed issue: #814
Enhanced the visibility of the logo in bright mode by adjusting its brightness. The changes ensure that the logo stands out and is easily distinguishable against the background, improving the overall user experience.
Fixes:  #814
Before making the changes, the logo looks like:

After making the changes:

Great contribution to GSSOC'24! 🎉


Snippet test invalidGlobImport6.pkl is too slow

This test takes 15 seconds to run on my machine, hampering developer productivity.

Typically, I only include the tests that address the issue I'm working on by adding a filter here: https://github.com/apple/pkl/blob/d00c466843abf1d88abf9d897941fce71334efd4/pkl-core/src/test/kotlin/org/pkl/core/LanguageSnippetTestsEngine.kt#L53
But, if you really want to exclude this test specifically, you can also add it to your excluded tests temporarily:
diff --git a/pkl-core/src/test/kotlin/org/pkl/core/LanguageSnippetTestsEngine.kt b/pkl-core/src/test/kotlin/org/pkl/core/LanguageSnippetTestsEngine.kt
index 1aca859ab..061ecf81c 100644
--- a/pkl-core/src/test/kotlin/org/pkl/core/LanguageSnippetTestsEngine.kt
+++ b/pkl-core/src/test/kotlin/org/pkl/core/LanguageSnippetTestsEngine.kt
@@ -58,6 +58,7 @@ abstract class AbstractLanguageSnippetTestsEngine : InputOutputTestEngine() {

   override val excludedTests: List<Regex> = buildList {
     add(Regex(".*/native/.*"))
+    add(Regex(".*/invalidGlobImport6\\.pkl"))
     if (IoUtils.isWindows()) {
       addAll(windowsExcludedTests)
     }

My point is that this test slows down ./gradlew test by 15 seconds, which is unjustified.

That sounds like a good solution to this problem

Would you be OK with making this limit configurable in the CLI and Evaluator API?

It's imminent! We're targeting an end-of-October release, so, in the next two weeks.
I'd rather not add user-facing knobs here. I think this can be as simple as something like this in GlobResolver:
-private static final int MAX_LIST_ELEMENTS = 16384;
+private static final int MAX_LIST_ELEMENTS = IoUtils.isTestMode() ? 500 : 16384;


taxNumber1 Issue when creating an Invoice

When creating an invoice - it returns the following error
Write access denied. Tried to write None to field taxNumber1 of object line
Per Freshbooks Support - we aren't supposed to send/try to set taxNumber1 or taxNumber2

Hi!
Thanks for finding the issue and opening the ticket.
So it looks like that is a change in the FreshBooks API. The field was not read-only before.
I'll put up a change to not write that field.

I've updated and published a new release. Thanks again.


Adopt vscode.open or vscode.diff in built-in extensions

With https://github.com/microsoft/vscode/issues/85636 landed, it is now recommended that an extension sets the TreeItem command to vscode.open or vscode.diff if the resource is know upfront.
Example from ref view:
https://github.com/microsoft/vscode-references-view/blob/730800271aa5ef52b1c49608d68f14ee585f7821/src/calls/model.ts#L176-L186
List of extensions with custom views we ship:

[x] JavaScript Debugger @connor4312
[x] JavaScript Perf View @connor4312
[x] NPM @alexr00
[x] References View @jrieken already did that to my knowledge

Git support is tracked in https://github.com/microsoft/vscode/issues/110397 and timeline in https://github.com/microsoft/vscode/issues/110496
//cc @isidorn @weinand not sure if debug has custom views where we should support this as well?

Debug had loaded scripts view, but it is now in the vscode core. So we should be covered there.

We have some views but don't open sources from them.

NPM involves opening package.json files and finding specific scripts in them. Adopting vscode.open there should wait until https://github.com/microsoft/vscode/issues/110498

@alexr00 can you clarify? at the time I have expanded the NPM tree to see scripts, we should have already resolved everything, no?

The view uses fetchTasks to populate the tree view, which gives no information about where in the package.json file the task is coming from. The code can always be refactored to not do this, but it isn't just a simple adoption then.

It probably should be refactored that way since it will be more efficient then.

After a quick check, I think the only blocker is this code:
https://github.com/microsoft/vscode/blob/7b5849b123de0dbf1d0c7a21e3cc10cfa550746f/extensions/npm/src/npmView.ts#L198-L198
If the position was known upfront, this could be changed from:
https://github.com/microsoft/vscode/blob/7b5849b123de0dbf1d0c7a21e3cc10cfa550746f/extensions/npm/src/npmView.ts#L82-L86
to something like:
'open': {
	title: 'Edit Script',
	command: 'vscode.open',
	arguments: [uri, selection]
}

That is correct.

@connor4312 and @jrieken FYI I have made a test plan item for NPM scripts, but we will still need test items for the other extensions.

I have a verificated-needed item for this

I had this for my https://github.com/microsoft/vscode/issues/111417 already spelled out:

Maybe I leave my thing in for SCM at least (@joaomoreno fyi)

@bpasero I have this for Git/SCM: https://github.com/microsoft/vscode/issues/111519

Ok good then I will simply remove that part from my test plan item, thanks for covering it in other issues 👍


AI Attempting to understand it's purpose, this was the "go help buildconstraint" log after my source code was crossing boundaries else's.

A build constraint, also known as a build tag, is a line comment that begins
    // +build

that lists the conditions under which a file should be included in the package.
Constraints may appear in any kind of source file (not just Go), but
they must appear near the top of the file, preceded
only by blank lines and other line comments. These rules mean that in Go
files a build constraint must appear before the package clause.
To distinguish build constraints from package documentation, a series of
build constraints must be followed by a blank line.
A build constraint is evaluated as the OR of space-separated options.
Each option evaluates as the AND of its comma-separated terms.
Each term consists of letters, digits, underscores, and dots.
A term may be negated with a preceding !.
For example, the build constraint:
    // +build linux,386 darwin,!cgo

corresponds to the boolean formula:
    (linux AND 386) OR (darwin AND (NOT cgo))

A file may have multiple build constraints. The overall constraint is the AND
of the individual constraints. That is, the build constraints:
    // +build linux darwin
    // +build amd64

corresponds to the boolean formula:
    (linux OR darwin) AND amd64

During a particular build, the following words are satisfied:
    - the target operating system, as spelled by runtime.GOOS, set with the
      GOOS environment variable.
    - the target architecture, as spelled by runtime.GOARCH, set with the
      GOARCH environment variable.
    - the compiler being used, either "gc" or "gccgo"
    - "cgo", if the cgo command is supported (see CGO_ENABLED in
      'go help environment').
    - a term for each Go major release, through the current version:
      "go1.1" from Go version 1.1 onward, "go1.12" from Go 1.12, and so on.
    - any additional tags given by the -tags flag (see 'go help build').

There are no separate build tags for beta or minor releases.
If a file's name, after stripping the extension and a possible _test suffix,
matches any of the following patterns:
*_GOOS
*_GOARCH
*_GOOS_GOARCH
(example: source_windows_amd64.go) where GOOS and GOARCH represent
any known operating system and architecture values respectively, then
the file is considered to have an implicit build constraint requiring
those terms (in addition to any explicit constraints in the file).
Using GOOS=android matches build tags and files as for GOOS=linux
in addition to android tags and files.
Using GOOS=illumos matches build tags and files as for GOOS=solaris
in addition to illumos tags and files.
To keep a file from being considered for the build:
    // +build ignore

(any other unsatisfied word will work as well, but "ignore" is conventional.)
To build a file only when using cgo, and only on Linux and OS X:
    // +build linux,cgo darwin,cgo

Such a file is usually paired with another file implementing the
default functionality for other systems, which in this case would
carry the constraint:
    // +build !linux,!darwin !cgo

Naming a file dns_windows.go will cause it to be included only when
building the package for Windows; similarly, math_386.s will be included
only when building the package for 32-bit x86.

I don't see a bug report here.  Closing.  Please comment if you disagree.
Please don't randomly post on our issue tracker, it's being watched by thousands of people.  Thanks.


Judith/events

Description
New events in the queue, which I'd love to get merged before the release does if you have a sec to look at them soon 🙌
Urgency

[ ] Blocker
[x] High
[ ] Medium

Requirements

Test all commands and procedures.
Build content locally and test for formatting/links.
Add redirects to dcos-website/redirect-files.
Change all affected versions (e.g. 1.7, 1.8, and 1.9).
See the contribution guidelines.

This got messed up. Closing it in favor of #1521


Bug: i expect to see errors

PHP Version
8.2
CodeIgniter4 Version
4.3.2
CodeIgniter4 Installation Method
Composer (using codeigniter4/appstarter)
Which operating systems have you tested for this bug?
Linux
Which server did you use?
apache
Database
Mongodb
What happened?
My 2 projects share some data with curl post. the sender project is running codeigniter 3 and receiver is running codeigniter 4.3.2.
when i try to send data i am getting 500 http status code.
but there is no response of what the error was even after i ask php to display errors .
the problem is when CI_ENVIRONMENT in .env is set as  production.
https://prnt.sc/JzVAPYsHf4ks
when it is set as development i am getting proper response.
https://prnt.sc/_Xlp9cnFA5Ly
but since this is a production server and i only want to enable errors for one page i am puzzled here.
Steps to Reproduce
1.) set CI_ENVIRONMENT = production in .env file
2.) write 2 functions
a) reciever.php
      function processing() {
        ini_set('display_errors', 1);
        ini_set('display_startup_errors', 1);
        error_reporting(E_ALL);
        dd($and);
    }

b) sending.php
    function sending() {

        try {
            $curl         = curl_init();
            $request_body = [];
            curl_setopt_array($curl, array(
                CURLOPT_URL            => "**reciever.php**",
                CURLOPT_RETURNTRANSFER => true,
                CURLOPT_ENCODING       => "",
                CURLOPT_MAXREDIRS      => 10,
                CURLOPT_TIMEOUT        => 30,
                CURLOPT_HTTP_VERSION   => CURL_HTTP_VERSION_1_1,
                CURLOPT_CUSTOMREQUEST  => "POST",
                CURLOPT_POSTFIELDS     => json_encode($request_body),
                CURLOPT_HTTPHEADER     => array(
                    "authorization: Bearer test",
                    "content-type: application/json"
                ),
            ));
            $response     = curl_exec($curl);
            dd("curl_exec response : ", 0);
            dd($response, 0);
            $http_status  = curl_getinfo($curl, CURLINFO_HTTP_CODE);
            $response     = json_decode($response);
            $err          = curl_error($curl);

            curl_close($curl);
            dd("http_status : ", 0);
            dd($http_status, 0);
            dd("curl_error : ", 0);
            dd($err);

        } catch (\Exception $e) {
            dd($e->getMessage(), 0);
        }
    }

3.) run sending function
Expected Output
i expect to see errors because i forcefully requested php to show errors with code .
ini_set('display_errors', 1);
        ini_set('display_startup_errors', 1);
        error_reporting(E_ALL);

Anything else?
No response

We use GitHub issues to track BUGS and to track approved DEVELOPMENT work packages. We use our forum to provide SUPPORT and to discuss FEATURE REQUESTS.

dd() outputs nothing in production environment.

dd() outputs nothing in production environment. And you can see errors in log files on the server.

i donot use ci4 dd() this is a custom function that print data so it will  work fine in production too, as you can see from the provided screenshot.  my issue is not still resolved.

No. This is not a bug.
Why don't you see the log file?
It is the easiest way to see the error.

@kenjis  i understood. i can see the error in server2 log. but i am getting 2 responses when i directly loading the receiver.php and loading it via curl.  when i load it directly i get error response that there is  no variable. but in curl i dont get any response. is this out of ci4 question?

It is not a framework issue. The framework does not show errors in production environment.
It is intentional.
Unfortunately, there is no easy way to show errors that you want with the framework.
Even if there is, the core code of the framework would need to be customized.
At least I don't immediately know how to customize it.


stack summary stat bars for more viewspace

instead of horizontally placing these together, stack them on top of each other so each bar can consume the entire horizontal space on the viewport.

stacked now

live on the server


ZipArchive Extraction Performance Magnitudes Slower in latest version

I work in an offline environment and we haven't pulled in the latest SharpCompress in a while.  I did so yesterday and found that our zip extraction performance plummeted from the last version we were using, v25.0.  I wrote this simple method and main loop to time extract a zip between the latest version and v25:
static void Main(string[] args)
{
    var stopwatch = new Stopwatch();

    for (int i = 0; i < 10; ++i)
    {
        Directory.Delete(@"<hard coded output folder>", true);
        Directory.CreateDirectory(@"<hard coded output folder>");

        stopwatch.Reset();
        stopwatch.Start();
        UnZipFile(@"<hard coded zip file path>", @"<hard coded output folder");
        stopwatch.Stop();

        Console.WriteLine(stopwatch.EllapsedMilliseconds);
    }
}

public static List<string> UnZipFile(string file, string outputDirectory)
{
    var extractedFiles = new List<string>();

    using (var stream = File.OpenRead(file))
    using (var archive = ZipArchive.Open(stream))
    {
        foreach (var entry in archive.Entries.Where(entry => !entry.IsDirectory))
        {
            entry.WriteToDirectory(outputDirectory, new SharpCompress.Common.ExtractionOptions
            {
                ExtractFullPath = true,
                Overwrite = true,
            });
            extractedFiles.Add(Path.Combine(outputDirectory, entry.Key));
        }
    }
}

Times from v25.0
614
590
714
626
584
614
628
552
623
611
Time from latest:
2304
2305
2051
1918
2098
1984
1883
1969
1924
2045
What dramatically changed in the zip flow to cause this?

More information: I commented out the actual extraction part and discovered it's the ZipArchive.Open() that is so slow.  Will try to investigate, but if anyone has an immediate clue, I'm all ears.

Not an issue.


AzOps Pull – Bicep

Update AzOps Pull to pull the exported templates in Bicep, is an added option to give customer more flexibility.

Hi guys, any update on this one?

Moving forward our long-term plans are in the following direction:
To expand AzOps capabilities by enabling Bicep file generation confidently with existing Pull operation (dependent on Bicep CLI) we have spent a few cycles experimenting with the bicep decompile workflow. We need the use of AzOps to be predictable/reliable to avoid a flood of community issues due to uncertainty in decompile quality and cause.
The main challenge we see pivots around the “best-effort” nature in the chain of “two” decompile events:

AzOps acts as the main “first” decompiler with “best-effort” targets by interacting with Azure and gathering the ARM resource and structures the information with the help of Jq to ensure the pulled ARM template file ideally results in a deployable asset (Push operation).

Adding the option to output the information to Bicep files with a “second” decompiler (bicep decompile) based on yet another “best-effort” chain creates a higher level of unpredictability and complexity during Pull / Push operation.
The “results” of the decompile events 1 and 2 are both of a “best-effort” nature and puts increased importance of tests / traceability to say that at version X the following Y resource providers were Pulled and Pushed by AzOps successfully.

AzOps journey to add bicep support for the Pull operations hinges on the following items:

Establish baseline of most used resource providers in the AzOps community today

Expand Jq templates where required to cover baseline
Expand AzOps automated testing to include those resource providers for ARM

Add AzOps Bicep decompile support

Expand AzOps automated testing to include those resource providers for Bicep

The “best-effort” nature becomes less of an issue with the addition of establishing a baseline testing for popular resource providers and the AzOps community just as always can raise issues and introduce new providers.
Why not just test all the resource providers in Azure?
•	Labor intensive to implement and maintain
•	We want to spend time on RP’s that are used by the AzOps community

I think that we should look into using the "insert resource" function that's available in Bicep here. It will export the resource and clean up the template based on the Bicep type system to make sure that read-only properties and other noise is removed. At the moment it's only available in the VSCode extension, but it can be added to Bicep CLI as well. There is a feature request open to add it but it is not top priority at the moment, https://github.com/Azure/bicep/issues/5696.
In my opinion I would say that a baseline of most used resource types that should be prioritized can be skipped. If the export of a bicep template/decompile fails we could fallback to exporting an ARM template instead of Bicep.

I really like this suggestion by @StefanIvemo (although I would prefer bicep export over insert or import if implemented in bicep.

@StefanIvemo
I did not come across your comment before now, but this would be preferred. Using inbuilt logic from the binary would be to considerate as the most optimal.
I will highlight this for the Bicep-team (as you have done), but their backlog is huge.
Utilizing this, it will save AzOps team for creating and maintaining all the logic at least..
Sidenote:
Be able to prioritze .bicep over .json in the same folder when the resource declaration is identical. It seems like AzOps already has this in place, only the opposite way.
Run what-if against compiled bicep file > .json since it can't be proven trustworthy on .bicep. It seems like this is already in place by AzOps.
Would really be to get "rid off" (dream) human interaction with .json, after Bicep I've almost forgotten how to use it..


Class Pico not found

After installing pico in localhost following the instructions, I uploaded all my files to a blank webpage for testing propouses.
Yet, I keep seing this error message.
Fatal error: Class 'Pico' not found in /home/vol8_8/byethost16.com/b16_16402975/htdocs/index.php on line 6

What is it I'm doing wrong?
Just for the record, I've tried first with a custom installation (a custom theme, some content, highgly edited config file, etc.) and after seing it was no good, I've tested overriding it with a default installation (freshly installed composer, no plugins, etc.). The error was still there! In both cases, the site was working perfectly on localhost, wich is what makes me guess... maybe there's a wrong PHP config?
This is a link to the PHP info of the blank website I'm testing on: http://phpinfo.byethost11.com/index.php
(please let me know if the link is not working)
In advance, thank you very much for the feedback, and for pulling together this great publishing tool :+1:

Solved, sorry I uploaded wrong files :confounded:


Docs titles are clipped on the left side

please, fix css margin property at anchors titles
.docs-header-link header-link a {
text-decoration: none;
 /* margin-left: -30px; */ this property hide anchors at the page titles
 display: inline-block;
vertical-align: middle;
}

If margin value -30px I can't see anchor for navigate
https://material.angular.io/components/table/overview#filtering
Affected documentation page: https://material.angular.io/components/table/overview

Confirmed that the titles in the docs are clipped on the left side, which affects both the link-on-hover treatment and the text itself.

@jelbourn Are the issues assigned first? I am new here and would like to start with working on this one

@ChiragAwale feel free to send a PR

@ChiragAwale  Hi , Are you still interested in solving this issue or not ? I'm also new here .


Selectable, Insertable and Updateable Kysely wrappers

Hey, thanks for this package! I was reading this page:  https://www.kysely.dev/docs/getting-started and there is a section in there that says
// You should not use the table schema interfaces directly. Instead, you should
// use the `Selectable`, `Insertable` and `Updateable` wrappers. These wrappers
// make sure that the correct types are used in each operation.
export type Person = Selectable<PersonTable>
export type NewPerson = Insertable<PersonTable>
export type EditedPerson = Updateable<PersonTable>

I noticed the output file from this pacakge does not include Selectable<TableName> , Insertable<TableName>, and Updateable<TableName> is this not required if you are generating the types from a Prisma schema or is that something we have to manually add to the output file?
thanks in advance

Hey! I'm happy prisma-kysely is of use to you! The wrapper types you're mentioning are actually not related to the inner workings of Kysely itself, but are meant as a convenient way to get normal typescript interfaces from table definitions. Take the example of a table that has rows with different types for insert, update and select. The wrapper types extract only the types that apply to each one of these cases.
type TestTable = {
  created_at: ColumnType<Date, string | undefined, never>;
}

Here Selectable would return an interface with created_at of type Date, Insertable string | undefined and Updateable never.
In my opinion it's probably out of scope for prisma-kysely to generate these types, since it's a case of adding a single wrapper type. I would be willing to consider a pull request that adds this functionality though, if anyone wants to build it.


Screenshots in VS Code Marketplace listing for Turborepo LSP are broken links

Verify canary release

[X] I verified that the issue exists in the latest Turborepo canary release.

Link to code that reproduces this issue
N/A
What package manager are you using / does the bug impact?
pnpm
What operating system are you using?
Mac
Which canary version will you have in your reproduction?
N/A
Describe the Bug
https://marketplace.visualstudio.com/items?itemName=Vercel.turbo-vsc

Expected Behavior
Images.
To Reproduce
Look.
Additional context
No response

Yeah, also would be nice to release a new version that includes the search-for-turbo logic that potentially makes it work with project-level turbo

New version being reviewed as we speak!


Make Kong 1.0 version number work correctly

https://github.com/Kong/docs.konghq.com/pull/946 demonstrated that using 1.0 for a Kong version number causes the Docs site to build incorrectly.
1.0.x works correctly, but we don't want to use the trailing .x once we release Kong 1.0

I would like to work on this issue. How can i start?

I'd suggest you pull #946 , get it running locally, then try to fix the issue.

@dash34 we got this fixed, just letting you know.


Create Check Point User Center Account

Describe the issue

Find out if there exists any pre-existing user center account for CPF
User Center Account is required for getting Check Point Support

Additional context

Dome9 Admin Guide
Checkpoint SK#22575

Definition of done

Create Check Point User Center Account

User Center

User Center Account is required for the following services:
Manage Accounts & Products
Get Support Offers
License Products
Open & manage your Service Requests
Access Downloads and product documentation
Search Technical Knowledge Center
Refers to SK#22716 for details
https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk22716&partition=General&product=User


Short solution needed: "MAPE" (python-scikit-learn)

Please help us write most modern and shortest code solution for this issue:
MAPE (technology: python-scikit-learn)
Fast way
Just write the code solution in the comments.
Prefered way

Create pull request with a new code file inside inbox folder.
Don't forget to use comments explain solution.
Link to this issue in comments of pull request.

How to calculate MAPE (mean absolute percentage error)


When using lucide icon pack not all the icons from the set are available

I am using this plugin with Lucide icon pack. However not all the icons that are available originally through the lucide.dev are available here (e.g. :utensils, :chef-hat, :soup) and some others are overridden by internal (system?) icons (e.g. :pizza, :scroll, :croissant).
For the overlapping icons - the solution might be to add an option to use only specific icon packs (or to simply toggle usage of the build in system icons set). However I have no clue why some icons are simply missing from the set at all.

I've noticed a few as well (toy-brick, cuboid).
Would be great if we could see which version of Lucide is downloaded and update it. Great plugin!


Folder for step 1 NA

Hi guys, for this step:
Go to %userprofile%\AppData\Local\Packages\49306atecsolution.FilesUWP_et10x9a9vyk8t\LocalState\

do we need to create the folder 49306... or should be present already, as it is not on my PC
getting folder NA error on Windows Run panel.

@anishre You need the "Files"-App from the Microsoft Store. Then you got the Folder.

it's for $7


Add Teardown, HighFleet, NEBULOUS, Carrier Command 2

Teardown is similar to Instruments of Destruction. With nice voxel physics.
Carrier Command 2 operates weaponized UAVs and rovers against other weaponized UAVs and rovers.
HighFleet is about building armed ships in a dusty, future/soviet theme
Nebulous is The Expanse style space combat with missile and cannon mechanics and deep customization.
https://store.steampowered.com/app/1167630/Teardown/
https://store.steampowered.com/app/1489630/Carrier_Command_2/
https://store.steampowered.com/app/1434950/HighFleet/
https://store.steampowered.com/app/887570/NEBULOUS_Fleet_Command/

Thank you!


Exclude hashicorp vault versions

Which issue this PR addresses:
Fixes https://msazure.visualstudio.com/AzureRedHatOpenShift/_workitems/edit/9555522
What this PR does / why we need it:
Excludes versions of hashicorp/vault possibly effected by https://nvd.nist.gov/vuln/detail/CVE-2020-16251
Regenerates go.sum deps based on updated exclusions.
Test plan for issue:
Existing unit and integration tests.
Is there any documentation that needs to be updated for this PR?
No, module updates only.

/azp run CI

/azp run CI


Spectrum Analyser's peak dots are not handled

The little gray (in the default skin) dots at the peaks fall at a different rate. We should handle those specially.

We do this now.


Performance (again)

A scrolling effect is still observable when running cat (as one example).
While I've used slower terminal emulators, the scroll should be imperceptible.

It seems that each byte sent to the terminal is expensive, and it might make sense to buffer each Window's Grid to a common Grid, which determines the minimum update required.


Test from workflow fix

The purpose of this change is to test whether the fix in fix-gh-workflow actually lets us run CI against pull requests from forks. (Must target main instead of fix-gh-workflow to trigger workflow run)

Looks like this did fix the issue


#pad[] blocks/removes all the customfootnote.entry styling

Description
https://typst.app/docs/reference/meta/footnote/#definitions-entry:

#let title-page = pad[]
#title-page

#show footnote.entry: set text(red)

My footnote listing
#footnote[It's down here]
has red text!

The Discord Typst bot gives white result with this:
#let title-page = pad[] // This still somehow affects the color
// #title-page

#show footnote.entry: set text(red)

My footnote listing
#footnote[It's down here]
has red text!

How does #let title-page = pad[] or/and #title-page nullifies footnote entry styling? You can also just use #pad[] instead.
Reproduction URL
No response
Operating system
Linux
Typst version

[X] I am using the latest version of Typst

See here: https://github.com/typst/typst/issues/1348#issuecomment-1566316463
And the note in the docs:

Set and show rules for footnote.entry must be defined at the beginning of the document in order to work correctly. See here for more information.

If #let title-page = pad[] doesn't add any content, why is Discord Typst renders differently from my Typst? It should be the same v0.9.0.
And since previous issues are pretty much identical to this one (but for some reason I couldn't find them), is this issue will be closed or is it, at this point, indeed considered a bug and need to be fixed (in the future)?

Maybe the Discord bot has some preamble code or something.
I wouldn't say it's a bug, but it's a limitation. We can leave it open.

After more consideration, I think there isn't much we can reasonably change here. It would be unclear which styles to use. Consider this:
Hi, here is some text.

#set text(font: "Helvetica")
#set align(center)
#show footnote.entry: set text(red)

Here is a #footnote[with text].

Should the footnote be red? What's the font? Should it be center aligned?
What about this?
Hi, here is some text.

#set text(font: "Helvetica")
#figure[
  #show footnote.entry: set text(red)
  Here is a #footnote[with text].
]

What's the font? Would the figure's centering affect the footnote?
The problem is that there aren't any well-defined styles to use for the footnote except for those that are already active at the page level.

After more consideration, I think there isn't much we can reasonably change here. It would be unclear which styles to use.

There is only 1 style being added. And it is specifically for the footnote.entry. Clearly a footnote entry should use a style that is explicitly applied to it. It should also be applied to everything with #set text(red), since it is addressed to any text, but this doesn't work either (on the footnote).
You said that it's a limitation and a restriction, so surely this means that it can be fixed eventually? If not now, then maybe in a year or two.

Should the footnote be red? What's the font? Should it be center aligned?

Yes. Yes. Assuming footnote can inherit any general rules (if semantically possible), then yes. But I guess if we are going off of the "block of set/show rules won't change output depending on the order of set/show rules", then this might break it. Depends on how you look at it.

What's the font? Would the figure's centering affect the footnote?

The explicitly specified one. Would be weird, as you didn't say explicitly that stuff must be centered. So, since the footnote will be in a separate place than the figure caption, then the implicit centering of the caption shouldn't affect the footnote. But the line isn't 100% clear.

You said that it's a https://github.com/typst/typst/issues/2765#issuecomment-1826445074 and a https://github.com/typst/typst/issues/1348#issuecomment-1566316463, so surely this means that it can be fixed eventually?

That's why I wrote "After more consideration". I changed my mind.
I attempted applying local styles (basically the styles where the footnote itself is) to footnote entries and it was a disaster. It results in all-over-the-place styling because the footnotes pick up heading styling, centering, etc. I think it does not make any sense. Rather, in my opinion, the footnote should use the page-wide styles, just like the header and footer.
As a result, the footnote.entry show rule needs to come before the first piece of page content. Otherwise, it isn't uniform across the page and won't become part of the page styles. That's just how it works and I think somehow special-casing just this property would be very inconsistent.

That's why I wrote "After more consideration". I changed my mind.

This means that this note should be updated as well, it's now (slightly) outdated, more precisely the linked comment:
https://github.com/typst/typst/blob/40fcd97d584fc1dfa6446bc4922d3b1e440e0afd/crates/typst/src/model/footnote.rs#L49-L50
Maybe even the note without any links, just a raw explanation of where you should and shouldn't put the set/show rules.

Yeah, thanks for the heads up.


Fix close action missing bug

Issue:
ticket close action was not showing because in ActionView, we were adding a css class whose name includes an action name. In our case, foam-u2-ActionView-close css class was added to the element that wrapped the action. Since a css class that has the name 'foam-u2-ActionView-close' already existed in our system, applied its style to the action, it hid the action.
Solution:
Don't add css class whose name includes an action name

note: also fixes isAvailable as ticket now uses string id

Not sure if this is a good idea, what was the conflicting action?

We named an action 'close'. So foam-u2-ActionView-close class was added to the action element. I think the purpose of adding a class with action name was to mark that the element belonged to that action. However this css doesn't have any styles defined (unless it's already defined in our system which is what happened in this case), so I didn't think removing this would matter.


The sequential example in the docs doesn't work

When you try the following pattern described in the docs for sequential it doesn't work in the studio.
You also get the following warning.
Log Warning: sequential matches at the top of the file. If a pattern matched outside of a
sequential, but no longer matches, it is likely because naked patterns are
automatically wrapped with `contains bubble <pattern>`

This warning is somewhat unclear, as it doesn't really tell the user how they should proceed to make things work the way they expect it to.

good catch in the docs.
The error message is trying to explain that most patterns are auto wrapped
https://docs.grit.io/language/bubble#pattern-auto-wrap
sequential is not auto wrapped because it only matches on files, so the pattern inside of a sequential needs to match a top level file. in this case the easy fix is to insert a contains in front of each step like so:
sequential {
    contains `console.log($message)` => `console.warn($message)`,
    contains `console.warn($message)` => `console.info($message)`
}

Are there other strategies besides using contains?

The core thing is that each step is matching the file as a whole. In most cases, you want to look for some code inside the file so contains is the best option. Why do you want an alternative?

The bubble needs to go around the scope you actually want to isolate, like this:
sequential {
    file($body) where $body <: contains bubble `def $name($args, $...): $funcbody` where {
        $args <: `self` => .
    }
}

@morgante Thank you.
Worth noting that the example in documentation here > https://docs.grit.io/language/patterns#sequential
contains
sequential {
    bubble file($body) where $body <: contains `console.log($message)` => `console.warn($message)`,
    bubble file($body) where $body <: contains `console.warn($message)` => `console.info($message)`
}

In other words it is using bubble the very first.
Also I'm noticing that or does not seem to work together with bubble. Is there a way to make that work?
Ie the following code does not work as expected finding zero matches. Though each sequence in separation does work as expected.
sequential {
    file($body) where $body <: contains bubble `class $name($parent): $funcbody` => $funcbody,
    file($body) where $body <: contains bubble or {
        `self.assertEqual($first, $second)` => `assert $first == $second`,
        `self.assertEqual($first, $second, $third)` => `assert $first == $second`
    },
}


Meet errors when running

Hello, your work about the peg-in-hole with the reinforcement is excellent!
I am so happy to have a tutorial like this.
Unfortunately, I had some trouble when running your example, the details are as below:
(python:46275): Gtk-WARNING **: 16:25:05.465: Theme parsing error: gtk.css:8008:70: The :focused pseudo-class is deprecated. Use : focus instead.
terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc

I had tried so many times but could not solve the problem
and my device is Ubuntu20.04(CPU) with the conda environment as below
python=3.6.5
torch=1.3.1
torchivision=0.4.2
catalyst=20.9
catalyst-rl=20.3

Thank you for your time. And I'm looking forward to your reply!

Hi @Homiejc! One of the authors here. I'm happy you found our tutorial useful!
Unfortunately, it's quite some time has passed since we released the code so I assume some dependencies can be outdated. I have some time to look into it now, and maybe replace some dependencies with more up-to-date libraries.
To help me better figure out which libraries to use - could you provide more details on a project you have in mind right now? Or are you simply interested in following the tutorial for learning purposes? - In this case, what primarily are you interested in - robotics / Computer Vision part / Reinforcement Learning? Are you interested in learning specific tools like CoppelliaSim or Catalyst?
Understanding your motivation for using this project will help me fix it!
Thanks!
Fedor "Theo" Chervinskii

Hi Fedor-Chervinskii! I am so appreciative that I can get your relay since this project has been released for a long long time. Thank you for your help again！
I am a post-student major in robotics and very interested in the peg-in-hole problem. There is no doubt that reinforcement learning is a good way to solve this problem and your work has proven that. I am so excited by the performance of your work. I hope I can learn more about robotics and reinforcement by following your tutorial and eventually build my project to solve the problem as you did. And, yes, I am interested in learning reinforcement learning tools like CoppelliaSim and Catalyst as they provide enough resources to help me study.
Thank you!
ZY H

@Homiejc
Hello, classmate, have you solved your problem? How to solve it

Sorry, I did not solve that problem either. I think this problem happened because the incompatible between the  version
of the tensorflow and the Catalist-RL.Catalist-RL is too old for most published python-packages.

maybe you can try the stable baseline 3 as the training part. and you can take the code from this resource as an example to rebuild the project based on sb3 and coppelisim. That works for me. and the simulated scenario provided by this resource works well

@Homiejc Thank you for your reply, may I ask if you have time to provide some technical guidance? In fact, I am just getting started and want to repeat an example of an assembly scene that can run through, but I am not very proficient in reinforcement learning. If you are convenient, you can add wechat to chat:<PHONE_NUMBER>1, thank you very much

@mechanics-chenshuo @Homiejc Hello,classmate,have you solved your problem?I also meet this problem.If i don‘t use the stable baseline 3,is there a solution？


Use Datadog APM

I need an APM, so let's go with Datadog. What should we add to Datadog?

Cloud Run: backend, pusher, frontend https://console.cloud.google.com/run?project=based-hardware
Firestore: https://console.firebase.google.com/u/0/project/based-hardware/firestore

Resources

Dev env:

Cloud Run: https://console.cloud.google.com/run?project=based-hardware-dev
Firestore: https://console.firebase.google.com/u/0/project/based-hardware-dev/firestore

Previous conversation with Datadog team: Hi Thinh, Thank you for reaching out to Datadog. My name is Eric, and I am part of the Technical Solutions Team. I will assist you with your inquiry today. Google Cloud Run is a serverless platform. You can set up the [Google Cloud Platform integration](https://docs.datadoghq.com/integrations/google_cloud_platform/) to collect the logs and out-of-the-box metrics. See the list of metrics here: [Data Collected](https://docs.datadoghq.com/integrations/google_cloud_run/#data-collected). You can also instrument your Cloud Run applications with a purpose-built Agent to enable tracing, custom metrics, and direct log collection. Please see this documentation: [Instrument your application](https://docs.datadoghq.com/serverless/google_cloud_run/#instrument-your-application). Best Regards,Eric Li | Solutions Engineer | Datadog

@mrlfarano hi man, please help me w/ this one.

@thainguyensunya

hey @mrlfarano hope that you are well. i send a warrior to help us finish this task quickly. if you could continue with the task, please collaborate with him(Thai Ng. @thainguyensunya ) or just let him take over it - no worries man.


normalize path for SVF Downloader

When using the downloader via APS VS Code extension, the downloader downloads corrupt files with filenames that match objects_*.json.gz. From a manifest.json file retrieved from unzipping contents from the .svf file, the asset URI's for those objects include \..\ in the path, which, when normalized, will go up the directory, and thereby download the correct contents for the file.
I've tested this with Python and the files outputted after the normalizing the path are valid JSON and no longer corrupt.

hi @petrbroz, would you be able to review this? let me know if you need anything else from me

Thanks @lucaschadwicklam97, good catch! I'm surprised I haven't run into this issue before (the objects_*.json.gz would always download fine for me), but this code change looks like it would help in these kinds of scenarios.


Provide Settings support for unfocused Tab color

Is the less-intense, unfocused Tab color intentional (screenshot below)?  I prefer the default, unfocused Tab color.  Could this be an option within the plugin's settings?
OS: Ubuntu 23.
Thanks.

Hi, this is a bug. Most likely some race condition. I'll look into it.

@stohn777 Could you provide steps to replicate or describe the conditions of this problem manifesting?

Interestingly and perhaps related to your earlier comment about being a race condition, cannot duplicate today.  If it recurs, I'll provide you with some details.
Will close.


Add ZiZZi, a library for elegant data objects to replace DTO

ZiZZi is a library which allows to declare data without deciding about the final format. Data can then be printed as xml, json or property objects for frameworks in which they cannot be avoided (usually UI).

Hey @yegor256, I don't know if you got a msg about this Pr. If you didn't, maybe you'd like to have a look.

@Meerownymous thanks!


Teach angular-translate pluggable fallback handler

Based on https://github.com/angular-translate/angular-translate/pull/330 this, we can introduce pluggable fallback handler.
I'd like to push this forward. The only thing I wanna add, is that we should make sure that $translateProvider.fallbackLanguage() still works. In case someone uses .fallbackLanguage() and useFallbackHander('foo'), the fallback handler would override .fallbackLanguage() (or at least, it's preferred).
Any thoughts on designing this one?

@DWand The extraction of the existing into a dedicated plugin would be possible addition for 3.0.0. What do you thing? Perhaps like the currently closed  #330 (yours), but based on the current code.

I still think that this is a nice and flexible feature.
But I'd like to avoid implementing it to the current architecture of the module. It is hard to predict the impact of such changes to 1818 lines of code. At least, I think, it affects translation "resolution" methods ($translate(), instant()), refresh() method and initial language loading.

Closing due #1671.
Already part of architecture proposals.


v0.6.11 introduced vertical chart growth every time the window loses and regains focus

C3 version: 0.6.11, 0.6.12
D3 version: 5.7.0
Browser: Firefox 64.0.2 and Chromium 71.0.3578.98
OS: Arch Linux 4.20

Timeseries line charts seemed to work fine with c3 v0.6.10 and lower.  Once I changed to using v0.6.11 or v0.6.12 (latest at time of writing), the chart's height grows every time the browser/page loses and regains focus.
Here's the most minimal version of a chart that does it: https://codepen.io/anon/pen/JxjdXX
When it loads, click the white rendered HTML area that contains the chart, then click back to the JS, then back to the rendered area, and so on, and so on.  Each time the focus is back on the area with the chart, the chart grows vertically.
This seems to be the likely culprit: https://github.com/c3js/c3/pull/2541
Please let me know if I can provide any further information.

Definitely a breaking issue here - I can't use this library while this bug exists

Happens to me as well

Happens to me as well. Additionally, our pie charts have initial 0 height, and applying the focus/blur approach above, the chart's height increases.

https://codepen.io/rompelstompel/pen/EMPmoV

Found a workaround. If you set svg's display property to block, then it seems fixing the issue.
https://codepen.io/kt3k/pen/OqXxoj
(I'm not sure the root cause of this behavior. Sometimes svg and its wrapper div have different sizes. And that cause this bug. But in some cases (for example this one in /htdocs) it doesn't simply happen (in that case, svg and its wrapper div have the same height.)

After looking at #2541's example carefully, I found that it doesn't work without additional styles like #chart { height: 100%; }. Now I think it's better to revert it.

Reverted #2541 and released it as v0.6.13.

Reverted #2541 and released it as v0.6.13.

Thanks!

The codepen example seems fixed with c3 updated to v0.6.13.
https://codepen.io/kt3k/pen/zboOKj


Upgrade to kafka 1.1.1

@smccauliff This patch upgrades kafka-monitor to 1.1.1. I have tested patch locally. Can you take a look when you get time?

@smccauliff I added the following comment Need to catch throwable because there is scala API that can throw NoSuchMethodError in runtime and such error is not caught by compilation.

Thanks for doing this.


[Mechanic] HP/MP rounding error with equipment

Reproducible: Yes
Impact: Low
When changing equipment, it is possible to lose/gain HP/MP due to the underlying data being stored as an integer instead of a float. RMMV recalculates the new stat value (after equipment change) to be as close to the previous percentage as possible, but then stores the new rounded value instead of the intended percentage. Because of this, undoing the most recent equip can cause the player to lose or gain HP/MP until either 1 HP or full HP is achieved (depending on the value change of the equipment and the starting values of the characters HP/MP).

I'm afraid you addressed the very problem that plagues most RM users. Because it's stored as an integer and not a float, HP gets continuously lost. I'm afraid there's not a valid solution to it that prevents abuse of unequipping repetition other than reducing HP each time without rewriting the base structure of MV. Sorry I couldn't be of more help here.
-Yanfly

RMMV recalculates the new stat value (after equipment change) to be as close to the previous percentage as possible

I tried testing the same situation.
However, after changing the equipment, HP/MP were simply clamped between 0 and the max value.
I'm sorry but I don't know what situations you are concerned about. 😖

Did you tried without yanfly plugins?

It has nothing to do with yanfly scripts. Its how the core script handles the data type.
If we simply round the value before displaying it, we should be able to keep the float for calculations, but still display the value we would like to display. The bad part is that it doesn't look like RMMV differentiates between calling the HP for a calculation and calling it for a display value, so we would have to write a new method .paramUnrounded that returns the unrounded version whenever a calculation is to be done, and then allow it to use the original rounding for display calls or we could do the opposite. It really depends on if there are more calls for calculation or display.

Clamp just keeps the HP value between 0 and Max which we obviously want to do. I assume it didn't round since most clamping functions don't. If a player has full health and unequips and then reequips they can lose or gain 1hp from the rounding error. I can show the problem in defualt/no plugin screenshots if it will help.

/**

Returns a number whose value is limited to the given range.

@method Number.prototype.clamp
@param {Number} min The lower boundary
@param {Number} max The upper boundary
@return {Number} A number in the range (min, max)
*/
Number.prototype.clamp = function(min, max) {
return Math.min(Math.max(this, min), max);
};

Champ is not rounding

as I said stop assuming,
before claiming a bug you should be able to reproduce it without any plugins or with a newer projects.
if they have plugins in it this not the responsability of the oss to find why it's bug with the said plugins.
as I said try to reproduce it with a fresh project without ANY plugins.
if it's doesn't bug without plugins, then it's a plugin bug. if you can reproduce without the plugins the said bug. then OSS will fix it.

You are correct. I'll be more careful claiming a bug in the future. Thanks for checking into it.
The problem still exists in the original game, but equipping/unequipping hp items simply doesn't attempt to keep the same %. I had realized the original scripts use the same hprate function that Yanfly uses, but failed to realize you never use it for equipping. You only use it for 2 purposes: 1. confitional branch (is actor hp between x/y) and 2. to confirm if the actor is alive for combat conditions. I can't think of a possible issue with rounding in those two instances where we would need a float over an int.


Create event / signal at start of cell execution

The  NotebookActions.executionScheduled and NotebookActions.executed events allow us to identify when a ntoebook cell is queued for execution and when it completes, but there is no signal for when it starts execution.
Would it be possible for this extension to generate a signal that other extensions can connect to that identifies when a cell starts executing?

Would it be possible for this extension to generate a signal that other extensions can connect to that identifies when a cell starts executing?

Currently this extension does not emit signals and has no public API. On implementation level, all it does is listen to cell metadata changes (using CellModel.metadataChanged signal) and reflects the status accordingly. In particular to know if execution started it checks for shell.execute_reply.started metadata in execution stanza. While it would be possible to add a signal as you propose, I think that creating a signal for other extensions to use should not be a responsibility of this extension as all it would be just proxying changes which are otherwise directly available in cell model.

Okay - thanks... just feels a bit redundant for multiple extensions to have to set up their own listeners on the metadata. (I assume core JL maintainers have a reason not to want to offer the event themselves.)

I assume core JL maintainers have a reason not to want to offer the event as a core signal

I don't think so. In fact when executionScheduled was being added I suggested to also add executionStarted too (https://github.com/jupyterlab/jupyterlab/issues/10259#issuecomment-844884865) but the contributor who did spend their time writing the code did not need it so they did not include it in https://github.com/jupyterlab/jupyterlab/pull/10493:

Note: @krassowski I didn't add the executionStarted signal because it didn't seem necessary. The started time had no noticeable difference compared to executionScheduled's start time.

... which I don't think is the case in general. Anyways, if you want to open a PR to core I would be happy to review it :)

Ah, interesting history, thanks. Agree with the "not generally true", eg if you Run All etc.
Re: a PR, I'm not sure my coding, or understanding of how JL works under the hood, is up to it.


Bug with Datepicker and custom format

Hi,
There is a strange UI behavior when custom date format is setted.
It seems like UI logic is still relying on 'MM-dd-yyyy' format instead of using the custom one.
You can try on this fiddle demonstrating the bug.

thanks for your issues!  We have fixed it in v2.2.3


Why always work from localhost and not from remote?

Same script on localhost work even without login..but from remote I got "Unusual login attempt"?
What is difference? How to solve that?
Local machine is Windows 10..and Instagram always allow script to work..Remote is Linux..and he not Allow??

Solved with setting user agent only to browser

Solved with setting user agent only to browser

hey bro how u solve this problem, can u give me a example


Fix docstring inheritance

What do these changes do?
Fix handling @staticmethod and @classmethod decorators, add tests for @_inherit_docstrings (finally 🤣, should have made those from the start).

[x] commit message follows format outlined here
[x] passes flake8 modin
[x] passes black --check modin
[x] signed commit with git commit -s
[x] Resolves #3033
[x] tests added and passing
[x] module layout described at docs/developer/architecture.rst is up-to-date

@vnlitvinov it seems that this PR has added another bug into _inherit_docstrings related to inheriting properties docstrings. In the following example, you can see that adding the _inherit_docstrings decorator overwrites the property itself, not only the docs.
from modin.utils import _inherit_docstrings

def property_builder(name):
    def getter(*args):
        """Getter doc-string."""
        print(f"{name} getter")

    return property(getter)

class Parent:
    my_prop = property_builder("Parent")

@_inherit_docstrings(Parent)
class Derived(Parent):
    my_prop = property_builder("Derived")

class DerivedNoDocs(Parent):
    my_prop = property_builder("Derived")

Parent().my_prop        # Parent getter
Derived().my_prop       # Parent getter
DerivedNoDocs().my_prop # Derived getter

P.S. this bug is not presented in the current master, so something in this PR has broken.

It is impossible to override a docstring of the property as it's a read-only field. _inherit_docstring in master is assigning the property attribute as it is in this PR :)
However it's working with properties in the wrong way, assigning a property based on its getter name (not property name).
Thanks for the example, I've add a test based on that and will fix it soon™.

@devin-petersohn @anmyachev any other comments?

@devin-petersohn it seems that #3001 has accidentally took most of the meat of this PR with it... so now it's basically fixing what @dchigarev found in the last comment :)

Restarted CI


Can't build on Linux with GTK 3.18

I have Gtk 3.18.9 installed on my box, and when I go to install Gotk3, I get these errors:
src/github.com/gotk3/gotk3/gdk/gdk_since_3_16.go:153:16: could not determine kind of name for C.gdk_gl_context_get_use_es
src/github.com/gotk3/gotk3/gdk/gdk_since_3_16.go:180:16: could not determine kind of name for C.gdk_gl_context_is_legacy
src/github.com/gotk3/gotk3/gdk/gdk_since_3_16.go:158:2: could not determine kind of name for C.gdk_gl_context_set_use_es

Things were working fine until the GL stuff was added.  But I also need the GL stuff, so I don't exactly want to revert back to an older revision.
I installed it using go get -u -v -tags gtk_3_18 github.com/gotk3/gotk3/gtk like I did before.
My Go installation is 1.12.4, but I also tested it with 1.12 and 1.11.4 with the same results.

Maybe we have done some mistake with the gtk version constraints. I'll take a look at this.
What version of gtk do you have installed?

It's Gtk v3.18.9
Thanks!

Should be working now. Just reopen the issue if it doesn't :)

Almost!  GDK now builds, but it looks like GTK itself now has a similar issue.
[alexa@emiko ~]$ go get -u -v -tags gtk_3_18 github.com/gotk3/gotk3/gtk
github.com/gotk3/gotk3 (download)
github.com/gotk3/gotk3/gdk
github.com/gotk3/gotk3/gtk
# github.com/gotk3/gotk3/gtk
mysrc/go/src/github.com/gotk3/gotk3/gtk/glarea.go:92:16: could not determine kind of name for C.gtk_gl_area_get_use_es
mysrc/go/src/github.com/gotk3/gotk3/gtk/glarea.go:97:2: could not determine kind of name for C.gtk_gl_area_set_use_es

Thanks for your help with this, I appreciate it!

Oof, I am dumb. Forgive me. Its midnight,  I'll fix this tomorrow, unless you wanna do it yourself. You'd just have to move the functions into files with gtk3.20+ buildconstraints.

K, now it works. For real this time ^^

Is this issue fixed? Because I'm having the same problem when i try to build this library in Ubuntu 16.04
gdk_since_3_20.go:15:16 could not determine kind of name for C.gdk_gl_context_is_legacy

I got the same issue using GTK3-3.18.9 on Slackware64 14.2 while using the https://github.com/sqweek/dialog library that downloads gotk3 v0.4.0.
The solution is to explicitly state during the go build phase the specific GTK3 version in use via a build tag, e.g:
go build -tags gtk_3_18
This should avoid taking into account the gdk_since_3_20.go file altogether.


Error when scaffolding with Entity framework core using Database first approach

Steps to reproduce

Create the Blogging database using the script in the docs
Create a empty Asp.NetCore project as explained in the docs
Run the below commands to install the necessary Nuget reference

Install-Package Microsoft.EntityFrameworkCore.SqlServer –Pre
Install-Package Microsoft.EntityFrameworkCore.Tools –Pre
Install-Package Microsoft.EntityFrameworkCore.SqlServer.Design –Pre

update the project.json

"tools": {
"Microsoft.EntityFrameworkCore.Tools": {
"version": "1.0.0-preview1-final",
"imports": [
"portable-net45+win8+dnxcore50",
"portable-net45+win8"
]
},

Now try scaffolding using the below command

Scaffold-DbContext "'Server=techestatevm.southeastasia.cloudapp.azure.com;Database=Blogging;User Id=newuser;Password=pass;'" Microsoft.EntityFrameworkCore.SqlServer -verbose
The issue
You get the below mentioned error.
Working directory: E:\Personal\TE\VS Projects\EFGetStarted.AspNetCore.ExistingDb\src\EFGetStarted.AspNetCore.ExistingDb
Executing command: dotnet ef --configuration Debug --build-base-path .\bin\ dbcontext scaffold ''Server=techestatevm.southeastasia.cloudapp.azure.com;Database=Blogging;User Id=newuser;Password=pass;'' Microsoft.EntityFrameworkCore.SqlServer --verbose
At line:1 char:215

... user;Password=pass;'' Microsoft.EntityFrameworkCore.SqlServer --verbo ...

                      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Unexpected token 'Microsoft.EntityFrameworkCore.SqlServer' in expression or statement.
Further technical details
I have also added every EF core nugets. My project.json is as below
"dependencies": {
"Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore": "1.0.0-rc2-final",
"Microsoft.AspNetCore.Identity.EntityFrameworkCore": "1.0.0-rc2-final",
"Microsoft.AspNetCore.Server.IISIntegration": "1.0.0-rc2-final",
"Microsoft.AspNetCore.Server.Kestrel": "1.0.0-rc2-final",
"Microsoft.EntityFrameworkCore": "1.0.0-rc2-final",
"Microsoft.EntityFrameworkCore.InMemory": "1.0.0-rc2-final",
"Microsoft.EntityFrameworkCore.SqlServer": "1.0.0-rc2-final",
"Microsoft.EntityFrameworkCore.SqlServer.Design": "1.0.0-rc2-final",
"Microsoft.EntityFrameworkCore.Tools": "1.0.0-preview1-final",
"Microsoft.EntityFrameworkCore.Tools.Cli": "1.0.0-preview1-final",
"Microsoft.EntityFrameworkCore.Tools.Core": "1.0.0-rc2-final",
"Microsoft.VisualStudio.Web.CodeGeneration.EntityFrameworkCore": "1.0.0-preview1-final"
},
EF Core version: (1.0.0-rc2-final)
Operating system: windows 10
Visual Studio version: (VS Enterprise 2015 with update 2)

Looks like this is a documentation issue. The suggestion caution as mentioned in the doc is the culprit. Removing the outer double quotes fixed the issue.
Note that the connection string is double quoted (with single quotes inside the double quotes). This is a workaround for a known issue in RC2 for more details.


Adds multi-language Python and Java quickstart release validations

This fixes #25853.
These tests server two purposes.

Server as reliable local validations for expansion services
Make sure that the pipelines advertised in Java and Python multi-language quick-start guides work for the new release.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

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

Run Java_Examples_Dataflow PreCommit

Run Python_Coverage PreCommit

Run Python_Runners PreCommit

Thanks!

Thanks!

Python test failures are unrelated to these release validation script updates.


Add Nong Song:

Song Name
Jocelyn flores
Artist Name
xxxtentacion
Source
Youtube
Youtube Link
https://youtu.be/FAucVNRx_mU?si=9oR2VySZWGqtLfLr
Direct File Link
No response
Song ID
590577
Start Offset [ms]
0
Extra
Used in level stereo Madness

Thanks for contributing! Someone will soon review your request.
Here is the JSON result for the reviewer:
{
  "name": "Jocelyn flores",
  "artist": "xxxtentacion",
  "source": "youtube",
  "startOffset": 0,
  "yt-id": "FAucVNRx_mU",
  "songs": [
    590577
  ]
}

To accept the request, a reviewer needs to write "accept".

Accept


Publish NARs in Maven

I'm building something that would be a lot easier if I could set up a maven dependency on the nifi-marklogic-services-api-nar. Could we get that published in either Maven Central or http://developer.marklogic.com/maven2?

I just revised my approach so that I won't need this after all. Still, it could be helpful.

@dmcassel  What exactly were you looking to reuse? This looks doable, though we'd need to publish not just the nars but all the jars as well. Which takes awhile (hours of waiting) to do with Maven Central.

Closing for now but will continue to use for conversation as needed.

@rjrudin I was working on a custom NiFi processor that was going to use some types from the MarkLogic NARs. We revised our approach and no longer have that dependency, so the need has gone away.

Got it - would the "processors" jar have likely been sufficient then, as opposed to the nar file(s)?

Got it - would the "processors" jar have likely been sufficient then, as opposed to the nar file(s)?

Yes, I think so.


installation

Hallo,
thank's for Your job, I've follow all the procedure, but finally I have no idea that how i can finalize  the HA data access,
please, can You explain step by step how i can run script and optain authorisations?!
Thank's in advance,
Gdi

Hallo, please, any help !?!?


Document steps + write next steps

Notes:

understand what people look for in terms of categories
better integration in OLS website
enrichments

Step 1:
Get data from the OLS paper repository
Step 2:
Data cleaning and enriching
Step 3:
Compile markdown and export html
Step 4:
Publish github page

Steps are written, still to do: the next steps

get help from communities to annotate and enrich; e.g. annotate descriptions
but then I need to figure out an annotation guidelines -- contributing via OLS website. They need to modify projects by cohort. Publish keywords, create a list of "preferred"keywords. Add contributors name. Reviewing. Annotations: domains, technical+community;
with OLS people we can try to integrate with the website
write some text to explain
put in the presentation that we will ask the community to annotate
migrating repository under OLS group --> move ownership to Berenice


Protect the main branch

@aabounegm Please, configure the Pages settings in GitHub like so:

It is needed for the workflow of publishing the presentation to your GitHub Pages

The only protection I applied for now is requiring a PR with one approval before merging. I don't personally like the "dismiss stale approvals" option, but we can vote on it. I will leave this issue open until the CI is all configured so that I require passing status checks as well (if that's desirable), and maybe requiring signed commits (if everyone agrees with Khaled)
@VanishMax done.

CI checks are already set up, so you can make them required. As for signing commits, guess we didn't agree on it after all as everyone seems to be pushing unsigned commits.
That said, after enabling the requirement of CI checks, this issue may be closed

Ok, and I noticed that #7 is about that anyway, so issue could have been closed since the beginning.


ClientPlayer is moving way faster than the ServerPlayer

Hi, I'm having an issue using the Client- and ServerPlayer. On my client side, the player is moving way "faster" (travels more units) than the player on the server side.
E.g. both start out at position { x: 0, y: 0, z: 0 } after shortly pressing: W, the position on the server is { x: 0.24, y: 0.58, z: 0.20} and on the client is: { x: 1.48 y: 0.58 z: 1.22 }
The plane is at location { x: 0, y: 0, z: 0} where as the scale is at 5 for each axis (as well for the client and the server). I'm runnning out of ideas, where to look for the error, can you point me into the right direction?
Furthermore, shouldn't the reconciliation kick in and "teleport" the client back?
Thanks for any kind of help!

Sorry for not responding earlier. Where you able to solve the issue?
2 things come to mind which could cause this:

Different speed values on the server and client version of the player.
Run in Background set to false in the project settings.

Thank you for your reply. Sadly I wasn't able to sort this issue out on my old project.
I've checked the settings on both the server and the client part on my machine - both are fine.  I guess I messed it up somewhere, while following the tutorial.
Just checked out the latest repository version and imported the scene I used to have, to see if it's reproducabl - no issues at all, I'm now going to look at my code and track down my mistake.
I consider this issue as resolved.


Updated to use Node20

Updated action to use Node.js 20 to close #23.
Also updated README to use latest checkout & setup-node versions and workflows to use Node 20.
Note: Though it should work, this PR is untested. Please do so before merging.

@alexesprit can you merge this one?

It's better late than never :D
Sorry for ignoring this.


Default type arguments should be omitted from documentation

Expected Behavior
If a type has a type argument and we use the default value for it, the type argument should not appear in the documentation.
Actual Behavior
Sometimes the type argument appears, sometimes it doesn't. It seems that Iterator<number> as a return type is rendered as Iterator<number> but as a parameter type is rendered as Iterator<number, any, undefined>.
Steps to reproduce the bug
I use Uint8Array for the repro because it is always present independent of the "lib" compiler option. Uint8Array just gained a type parameter in typescript 5.7 so this particular reproducer doesn't work in prior versions but it will reproduce with Iterator.
npm i<EMAIL_ADDRESS><EMAIL_ADDRESS>cat << 'END' > a.ts
export function f(a: Uint8Array): Uint8Array {
    return a;
}
END
npx typedoc a.ts

Output looks like:

Environment

Typedoc version: 0.27.5
TypeScript version: 5.7.1
Node.js version: 22.12
OS: ubuntu 22.04

Thanks for the fast fix @Gerrit0!


How to get/retrieve the name of a device from homekit?

Hello together,
i would like to get the name of a device from homkit, because i want to use the current name in homekit for processing an action.
This would be very good for the messenger plungin (https://github.com/potrudeau/homebridge-messenger), because this plugin send a message with the subject = device-name from the configfile.
So if you want change the message subject you have to change the name in the config and restart homebridge.
Changing in homekit app would be more flexible.
So: Is it possible to get the changed device name from homekit in a homebridge plugin?
kind regards,
Peter

HomeKit doesn’t know devices, only accessories and services.  The names of these are initialised from the accessory (i.c. the Homebridge plugin that typically uses the device name for this).  But after that, they are maintained exclusively trough HomeKit, invisible to the accessory, like rooms, groups, scenes, and automations.

Ah. Okay. Thank you.
But: In the Aquara App i can sync the names in both directions. So it must give a possibility...

The key being “app”: this is a HomeKit app that has access to HomeKit over the HomeKit framework, unlike accessories, which expose themselves over HAP.  Same for the Hue app.


SDK currently does not address the scenario where a large file needs to be downloaded serially to a non-seekable stream

Which service(blob, file, queue) does this issue concern?
blob/file
What problem was encountered?
referencing with some edits: https://github.com/Azure/azure-cli/issues/6608:
Currently the max_connections=1 arguments for downloads will only attempt to pull the larger files in one piece. When the file it is trying to download is larger than the memory on the workstation running the task the process consumes the workstation's entire memory and swap file then fails.
Looking to get the download methods to treat the max_connections=1 like it does when the max connections is set to 2 or more. That is to handle files larger than the memory of the workstation by breaking the file into multiple peices and make multiple requests to get the full file to download.
The Customer needs to download the blob to a named pipe so they must be able to use a single download connection to prevent seek operations on the pipe

Hi @williexu, thanks for creating the issue.
I'll update this thread once this work is scheduled on our end.

Has this been published?
Does the customer need to download a new version of the Azure CLI?
He tested the command and got the same results.

No @v-tisheg, this work will be scheduled soon.

Hi @williexu and @v-tisheg, this issue has been fixed in 1.3.1.


Add v0.7 as default version

Signed-off-by: Akash Srivastava<EMAIL_ADDRESS>

@atulabhi please check the URL of 0.6, if you need any change in that, please let me know.


[sdk]: Add options fn on HTTP router for Rust

This PR adds the options method for the Router struct provided by Spin SDK for Rust.
This allows users to quickly register handlers for incoming requests using the OPTIONS method:
Usage example
fn handle_options(_r: Request, _params: Params) -> Result<Response> {
  Ok(http::Response::builder().status(http::StatusCode::OK).body(None)?)
}

#[http_component]
fn handle_foo(req: Request) -> Result<Response> {
  let mut router = Router::default();
  router.options("/foo", handle_options);
  router.handle(req)
}

Thank you @ThorstenHans, looks great! Would you mind updating the http_router macro as well to keep the experiences consistent? I.e.
     ...
    (@build $r:ident OPTIONS $path:literal => $h:expr) => {
        $r.options($path, $h);
    };
    ...

Will add it once the kids are in bed 🤪


disagreements between plasmidVerify and viralVerify

Hi,
I have contigs assembled by plasmidSPAeds based on bacterial isolates PE reads -- therefore suspected plasmids. I want to further filter these contigs using plasmidVerify (as suggested in your paper) and viralVerify. So I have run both tools and found some disagreements in predictions. While, as expected, viralVerify predicted some of plasmidVerify 'Plasmid' contigs as viral ones, it also predicted some of the 'Chromosoome' plasmids as 'Plasmids'.
For example here are predicted 'plasmids' by viralVerify:
NODE_15_length_37998_cov_14.724243_component_0,**Plasmid**,37998,-,6.89,AIRS AIRS_C MCPsignal 4HB_MCP_1 TarH Oxidored_FMN Peripla_BP_4 AP_endonuc_2 GFO_IDH_MocA GFO_IDH_MocA_C Sigma54_activat HTH_8 Radical_SAM Bac_luciferase BPD_transp_2 Acyl-CoA_dh_2 Acyl-CoA_dh_M Acyl-CoA_dh_N BPD_transp_2 ABC_tran ABC_tran ABC_tran LysR_substrate HTH_1 Acetyltransf_1 Sigma54_activat PAS_9 PAS PAS_4 HTH_8 PAS_9 PAS_8 PAS_8 Peripla_BP_4 Abhydrolase_1 CN_hydrolase Molybdopterin Molydop_binding BPD_transp_2 Acyl-CoA_dh_N Acyl-CoA_dh_2 Acyl-CoA_dh_M ABC_tran BCA_ABC_TP_C BPD_transp_2 AMP-binding VirK Pyr_redox_3 Peripla_BP_6
NODE_16_length_25536_cov_16.257905_component_0,**Plasmid**,25536,-,5.07,Fe-ADH adh_short_C2 adh_short adh_short_C2 Epimerase NAD_binding_9 DJ-1_PfpI HTH_18 DJ-1_PfpI Sigma54_activat XylR_N V4R HTH_8 LysR_substrate HTH_1 Phenol_MetA_deg Peripla_BP_6 DAO PALP OCD_Mu_crystall Shikimate_DH K_oxygenase LysE Beta-lactamase tRNA-synt_1g Cupin_2 Aldedh Phage_integrase

and the corresponding prediction by the plasmidVerify:
NODE_15_length_37998_cov_14.724243_component_0,**Chromosome**,-2.497141683569888,AIRS AIRS_C MCPsignal 4HB_MCP_1 TarH Oxidored_FMN Peripla_BP_4 AP_endonuc_2 GFO_IDH_MocA GFO_IDH_MocA_C Sigma54_activat HTH_8 Radical_SAM Bac_luciferase BPD_transp_2 Acyl-CoA_dh_2 Acyl-CoA_dh_M Acyl-CoA_dh_N BPD_transp_2 ABC_tran ABC_tran ABC_tran LysR_substrate HTH_1 Acetyltransf_1 Sigma54_activat PAS_9 PAS PAS_4 HTH_8 PAS_9 PAS_8 PAS_8 Peripla_BP_4 Abhydrolase_1 CN_hydrolase BPD_transp_2 Acyl-CoA_dh_N Acyl-CoA_dh_2 Acyl-CoA_dh_M ABC_tran BCA_ABC_TP_C Molybdopterin Molydop_binding BPD_transp_2 AMP-binding VirK Pyr_redox_3 Peripla_BP_6
NODE_16_length_25536_cov_16.257905_component_0,**Chromosome**,-3.574700563044223,Fe-ADH adh_short_C2 adh_short adh_short_C2 Epimerase NAD_binding_9 DJ-1_PfpI HTH_18 DJ-1_PfpI Sigma54_activat XylR_N V4R HTH_8 LysR_substrate HTH_1 Phenol_MetA_deg Peripla_BP_6 DAO PALP OCD_Mu_crystall Shikimate_DH K_oxygenase LysE Beta-lactamase tRNA-synt_1g Cupin_2 Aldedh Phage_integrase

I would be happy for your advice regarding the best strategy to continue. Should I look only on consensus prediction by both viralVerify and plasmidVerify (i.e. both tools predict them as a plasmid) or any other approach?
Thanks in advanced,
Haim

Hi Haim!
Sorry for late reply. Indeed, we retrained our classifier in viralVerify, and results may differ slighltly. In your case it's hard to be certain - the scores in both cases are pretty low, and there are no strongly plasmidic genes, such as replication proteins.
Generally, it is advised to use viralVerify alone, and pay attention to reported plasmids with the low score (below 10) - these cases may require additional investigation.
Best,
Mike.


pkg-config for libraw asks for libstdc++ on darwin

Describe the bug
pkg-config --libs libraw asks for libstdc++, but it should be asking for libc++ on darwin.
Steps To Reproduce
Steps to reproduce the behavior:

nix-shell -p pkg-config libraw --run 'pkg-config --libs libraw'

-L/nix/store/0hr265hhxjyygmkl2413w54p66j4m2f9-libraw-0.21.1-lib/lib -L/nix/store/4kv96yrdskx
33fhvxgpndx6bw2vq7c3l-lcms2-2.15/lib -lraw -lstdc++ -llcms2

Expected behavior
pkg-config should ask for libc++ instead, or nothing? Linkers just provides the standard lib automagically right?
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
I'm not a C++ person (I'm trying to use the libraw rust crate), but apparently libstdc++ isn't supported by Apple.
I think the problem lies in libraw explicitly asking for libstdc++ in their build scripts. This was brought up (and pretty much ignored) to libraw maintainers: https://github.com/LibRaw/LibRaw/issues/248
Macports applies this patch to fix the issue: https://github.com/macports/macports-ports/blob/master/graphics/libraw/files/patch-libraw-no-libstdcxx.diff
Homebrew doesn't have such a patch, and I can confirm it's also broken this way: https://github.com/Homebrew/homebrew-core/blob/84fb6d8673d87eb06ee9db7cfb8631b9bd5a03c3/Formula/lib/libraw.rb
Notify maintainers
This package has no maintainers. :(
I'd be happy to add a patch similar to the one from macports (this is easy enough for me to understand). The ideal approach would be to patch the upstream with something portable, but I have no idea what that entails.

Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"aarch64-darwin"`
 - host os: `Darwin 23.1.0, macOS 14.1.1`
 - multi-user?: `yes`
 - sandbox: `no`
 - version: `nix-env (Nix) 2.18.1`
 - channels(root): `"nixpkgs"`
 - channels(julio): `""`
 - nixpkgs: `/etc/nixpkgs/channels/nixpkgs`

Add a :+1: reaction to issues you find important.

My workaround for this is to add gcc.cc.lib in your buildInputs or nix-shell command:
nix-shell -p pkg-config libraw gcc.cc.lib


[camera] Allow custom resolution and aspect ratio

there are only 5 enum selections.and we can not customize the size of picture which i take.
i want to get a pic with low's 320*240 (4:3) and high quality.but i can not make it. Why the resolution and aspect ratio should be bound together, how to set them separately and take photos of various quality with specific aspect ratio

for example if i want to take a pic with 960*1280,what i can do.

I also miss this question.how about setting a fixed aspect ratio firstly and then chosing the quality.

Hi @LTY2009
I think you are making a good point,
I feel that there's no harm in widening the topic a bit,
updating the title.
Thank you

anybody else ?

I'm annoyed by the fixed aspect ratio in the resolution preset. Ultra high, hight and Max all have 16:9 ratio, that mean the cameras with 4:3 sensor have areas cut off

This is a major oversight in the plugin. With low being, the only one with a 4:3 aspect ratio means that all the other ones are cropping into the sensor. If you want to have the widest field of view, you would have to either use the low resolution or write a custom native camera plugin?
Are there any workarounds or forked versions that solve this?

I need it as well. How can you not do something this basic?

Yeah same issue here. There is no way to set custom aspect ratios.

stop protecting google employees.

@Shawn-sudo stop sucking googles dick, they are not going to hire you

Please be aware of the wordings used in the comments and I strongly recommend to go through code of conduct to adhere to while commenting.

kys
On Thu, 1 Dec 2022 at 10:47, darshankawar @.***> wrote:

Please be aware of the wordings used in the comments and I strongly
recommend to go through code of conduct
https://docs.github.com/en/site-policy/github-terms/github-event-code-of-conduct#code-of-conduct
to adhere to while commenting.
—
Reply to this email directly, view it on GitHub
https://github.com/flutter/flutter/issues/45665#issuecomment-1333495621,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIDJW4A3CNN2AUMQRURKNSTWLBX4PANCNFSM4JSA2IFA
.
 If you stop wasting so much time this issue could already be resolved.

Do you have a good solution to this problem now

Do you have a good solution to this problem now

Yes, https://github.com/Apparence-io/CamerAwesome

I think CamerAwesome is just cropping an image that was cropped to 16:9 to 4:3 again. I need an option to use the full sensor.