Impossible run Spooky:  Child terminated with non-zero exit code 1

I'm using Debian GNU/Linux 7
Versions STACK:
Node: v0.10.15
PhantomJS: 1.9.2
CasperJS: 1.1.0-DEV

Content of app.js:

try {
    var Spooky = require('spooky');
} catch (e) {
    console.log("ERROR");
    var Spooky = require('../lib/spooky');
}

var defaults = {
    transport: {
        http: {
            host: 'localhost'
        }
    },
    child: {
        command: 'casperjs',
        port: 8081,
        script: './node_modules/spooky/lib/bootstrap.js',
        spooky_lib: './node_modules/spooky/',
        transport: 'http',
        bufferSize: 16 * 1024 // 16KB
    },
    casper: {
        verbose: true,
        logLevel: 'debug',
        clientScripts:  [
            'lib/jquery.min.js',
        ]
    }
};
var spooky = new Spooky(defaults, function (err) {

    if (err) {
        var e = new Error('Failed to initialize SpookyJS');
        e.details = err;
        throw e;
    }

    spooky.start('https://www.twitter.com', function(){

        this.capture('./captures/twitter.png');

    });

    spooky.thenEvaluate(function () {

        $("#signin-email").val(":D");

    });

    spooky.then(function() {

        this.capture('./captures/twitter2.png');

    });

    spooky.run();

});

In shell:
node app.js

ERROR:
events.js:72
        throw er; // Unhandled 'error' event
              ^
Error: Child terminated with non-zero exit code 1
    at Spooky.<anonymous> (/home/leif/proyectos/testSpooky/node_modules/spooky/lib/spooky.js:177:17)
    at ChildProcess.EventEmitter.emit (events.js:98:17)
    at Process.ChildProcess._handle.onexit (child_process.js:789:12)

I make a console log like https://github.com/WaterfallEngineering/SpookyJS/issues/59#issuecomment-19059810
casperjs ./node_modules/spooky/lib/bootstrap.js --command=casperjs --port=8081 --spooky_lib=./node_modules/spooky/lib/ --transport=http --bufferSize=16384

I'm new to this whole spookyjs business, and I feel like I'm to blame for this error since this ticket is closed and > 2 years old.
events.js:141
      throw er; // Unhandled 'error' event
      ^

Error: Child terminated with non-zero exit code 1
    at Spooky.<anonymous> (/app/node_modules/spooky/lib/spooky.js:210:17)
    at emitTwo (events.js:87:13)
    at ChildProcess.emit (events.js:172:7)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:200:12)

PhantomJS

phantomjs --version
1.9.8

CasperJS

casperjs --version
1.1.0-beta3

Heroku
buildpacks

https://github.com/leesei/heroku-buildpack-casperjs.git
heroku/nodejs

You're not alone, @joseym. I'm seeing the exact same problem.

@joseym and @stenrap Can you please verify if both dependencies are installed globally? I've also had a similar problem but seemed to be fixed when I got both PhantomJS and CasperJS installed and executable in a global namespace

To see what casperJS is saying, I passed the following object to child.spawnOptions: {stdio: 'inherit'} which has the casperJS child process use the executing script's stdio. Here is the output I got (replaced my home dir with ######)
{
	"jsonrpc":"2.0",
	"method":"emit",
	"params":[
		"error",
		"Error: Cannot find module '/######/node_modules/spooky/lib/../node_modules/tiny-jsonrpc/lib/tiny-jsonrpc'",
		[
			{"file":"phantomjs://bootstrap.js","line":289,"function":""},
			{"file":"phantomjs://bootstrap.js","line":254,"function":"require"},
			{"file":"/######/node_modules/spooky/lib/bootstrap/http-server.js","line":6,"function":""},
			{"file":"/######/node_modules/spooky/lib/bootstrap/http-server.js","line":65,"function":""}
		]
	]
}

And this reveals the source of the problem... The script tries to access the tiny-jsonrpc directory/module that's located in spooky's parent node_modules directory via ../ but falls short as it needs to traverse an additional directory upwards (../../node_modules/).


Handler does not export a fetch() function.

I just cloned the repo and ran yarn ; yarn dev and am getting this error when the browser opens.
I am posting here in case anyone else runs into this. It is an upstream known issue: https://github.com/cloudflare/workers-sdk/issues/5726
Please share your experience there.

Thank you for your comment. Always appreciate people trying to link related issues.
In this case it isn't an issue in this repo. We do indeed not expose a fetch function in our code because it's an email worker example.
If you wanted a fronted you'd have to implement the fetch function as the error (in this case correctly) suggests.

Thanks for the quick response. I don't yet understand how this repo works or the dev setup for it. I just assumed it was also an issue in this repo because it happened when running yarn dev.
Now I am starting to see that it isn't relevant. If that's the case then please close this as it won't be helpful to many people.
Thank you!
Also: great setup! I love that this repo has unit tests. It's a great foundation to start a new project from.


[bug] [bitcoin-core test] '1 2DUP 1'

Issue
The following bitcoin-core test is failing to give the correct result :
1 2DUP 1

This code should be failing due to a INVALID_STACK_OPERATION.
Replicate
To replicate the issue you can use the latest main branch with the following command:
scarb cairo-run '[[],49,1,[],55269070479409,6]'

Hi @b-j-roberts can I work on this?

@adrianvrj I'll keep this one open for now while you are on the other issue. Thanks.

@b-j-roberts Can I work on this?

Yeah, I'll assign you. Thanks @raizo07

This seems to have been a duplicate bug and was resolved as part of this PR : https://github.com/keep-starknet-strange/shinigami/pull/155

This seems to have been a duplicate bug and was resolved as part of this PR : #155

Been working on this, I was already going to send a PR for it @b-j-roberts


Mentor Feature

Is your feature request related to a problem? Please describe.
Some of my friends and family want to learn to code. I point them to FreeCodeCamp as a great resource, but I have no insight into their progress or the quality of their code solutions and as such am not able to provide quality mentorship advice.
Describe the solution you'd like
Allow students to assign another user as a mentor. The mentor account would able to see progress of the student and give feedback on their code solutions (maybe initially on a exercise-by-exercise basis and eventually on a line-by-line basis like GitHub PR reviews).
Describe alternatives you've considered
I could review progress with them over a video call, but that requires both parties to be available at the same time rather than asynchronous.
Additional context
No response

This seems like something that might work well with our upcoming classroom mode.

It is awesome to receive some notification once the mentee completes a section, like an email, or from the mentor's perspective, a timeline on where they are with a course.


TODO: Implement thorough testbench

ZEXALL test suite with "illegal" instructions https://mdfs.net/Software/Z80/Exerciser, https://mdfs.net/Software/Z80/Exerciser/Spectrum/
z80test suite for "undocumented" flag behaviors and MEMPTR register https://github.com/raxoft/z80test
ZX Spectrum suite including MEMPTR register [https://web.archive.org/web/20130511214919id_/http://homepage.ntlworld.com/mark.woodmass/z80tests.tap]

Also check test suite: https://github.com/redcode/Z80/wiki/Tests
And hardware recordings: https://stardot.org.uk/forums/viewtopic.php?t=15464

You should also take a look at this: https://github.com/SingleStepTests/z80

You should also take a look at this: https://github.com/SingleStepTests/z80

This looks great! Thank you for a hint!
I updated the list above.


Change default service URLs in fluxd and fluxctl

For fluxd --fluxsvc-address the default should be wss://cloud.weave.works/api/flux
For fluxctl --url the default should be https://cloud.weave.works/api/flux

Changed in #222


Unable to collect styled-component styleTags for SSR.

Description
Hello,
I use vike with grommet.io components. These are styled by styled-components. I try to collect the styleTags of the pages in order to use them for server-side-rendering with client hydration. I use ServerStyleSheet() as described here and in the vike docs:
https://styled-components.com/docs/advanced#server-side-rendering
The problem is, that there are no styles collected with grommet components used. If I use other components and apply styled-components to it, it works just fine. I setup a simple example:
https://github.com/der1igedon/vite-ssr-styled-components-grommet/tree/main/
The styles should be collected on the server side (see renderer/_default.page.server.tsx) and injected in the

Hey @der1igedon, thanks for reaching out. I have wrapped my head around styled-components and grommet, and am now having a look at your repo

See my fix in https://github.com/der1igedon/vite-ssr-styled-components-grommet/pull/1
Please note also that you are using an old version of Vike, so you might run into other issues later on. The latest version is 0.4.144


add key to StatusWithStatusIndicator component in loop

missing key was causing reconciliation errors in console

LGTM besides failed DCO and CI tests

I triggered a rerun.
Regarding DCO:
For legal reasons, we require that all commits are signed with a DCO before we can merge them. See this blog post for considerations around this.
This means that the last line of your commit message should read like:
Signed-Off-By: Your Name<EMAIL_ADDRESS>If you are using GitHub through the web interface, it's quickest to close this PR and open a new one with the appropriate line.
If you are using Git on the command line, it is probably quickest to amend and force push. You can do that with
git commit --amend --signoff
git push -f $remote $remote_branch_for_pr

As always, be careful when force-pushing.

rebased and signed

:+1: Nice, thanks!


Add the ssh options flag back in

This was originally added in https://github.com/aeroxis/sultan/pull/65
And seemingly removed by https://github.com/aeroxis/sultan/pull/71/files#diff-b40d03f22a7fbe9af83a379b51281fb7L584
As far as i can tell by looking at the changeset of #71 I don't think this was in intentional change.

Bump on this. Is this something you would consider merging? We have had to maintain a fork to just add this back in, and it would be nice for us to be able to just use upstream again.
Thank you!


Proposal : substitute Google Drive by remoteStorage.

remotestorage.js allows self-hosted per-user storage.
Please consider it over maintaining a Google Drive integration.
It also takes care of that, including Dropbox.
I am sure @michielbdejong, @galfert and @skddc can give fruitful advice, if only pointers, if needed. There's also a community discourse.

This version of colaboratory is no longer supported, please switch to https://colab.research.google.com.


jupyter notebook in the scrapy-xpath code-server

Hello Alfredo,
This is another issue in the code-server of laboratory Parse HTML with Scrapy and XPath
The files:  persistence.ipynb and scraping-with-htmlparser.ipynb only are avaiable in the text editor and not in the jupyter notebool editor.  I wasn't able to modify this because it doesn't work.

Could you verify please what happen there?
Thanks.

Likewise, going through the Python/SQL course, get to the Web-scraping section, the page mentions the Jupyter notebook, but there is no link to it. Search on git turns up only this issue.
Course URL:
https://www.coursera.org/learn/scripting-with-python-sql-for-data-engineering-duke/supplement/xalEx/parsing-techniques-with-htmlparser

Use the scraping-with-htmlparser.ipynb file to use HTMLParser to extract data from HTML.

^ Can't be done, no link to the notebook on that page.

@kushtun @Neri-hV thanks for highlighting this, I'll get this resolved ASAP

@kushtun @Neri-hV I've removed the lab and created a Reading that has instructions on how to open the lab with Codespaces with this repository template: https://github.com/alfredodeza/scrapy-xpath
Feel free to open the template repository to your own GitHub Account and use the updated "Reading: Codespaces LAb: Parse HTML with Scrapy and XPath"
That template has everything for the lab including all dependencies. Please re-open this issue if you are still having problems


Address feedback from #22517

use octicons for icon
use fomantic for centering the link

For others reviewing, here is a screenshot:


[pyyaml] Fix create-regex-at-runtime patch

What does this PR do?
Fix the patch diff following this change in the upstream repo, which was added in 5.3.
Motivation
Fix Agent pipelines, make integrations build work.

The PR already exist https://github.com/yaml/pyyaml/pull/301 (cc @therve ) from discussion history it was scheduled for 5.3, but it's now back to Backlog.


[mxnet2.0] gluon 2.0 data: deprecate dataset transform= argument

Description
Fix https://github.com/apache/incubator-mxnet/issues/11141
This is part of changes for gluon 2.0 which addresses the usability issue.
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[ ] The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes)
[ ] Changes are complete (i.e. I finished coding on this PR)
[ ] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[ ] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
Check the API doc at https://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
[ ] To the best of my knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

[ ] Feature1, tests, (and when applicable, API doc)
[ ] Feature2, tests, (and when applicable, API doc)

Comments

If this change is a backward incompatible change, why must this change be made.
Interesting edge cases to note here

Is there any timeline when to drop the deprecated argument?

Ideally the first release after 2.0

@mxnet-bot run ci [all]


Title: HLS source not working on iPhone, including demo page

Current Behavior
React Player does not seem to work with HLS sources on iPhone devices, even on the demo page: https://cookpete.com/react-player/
Expected Behavior
React Player should be able to play HLS sources on iPhone devices without issues.
Steps to Reproduce
Visit https://cookpete.com/react-player/ on an iPhone
Attempt to play an HLS source
Observe that the player fails to load the HLS source
Environment
URL attempting to play: Any HLS source on https://cookpete.com/react-player/
Browser: Safari (latest version)
Operating system: iOS (latest version)
Other Information
This issue seems to be specific to iPhone devices, as the HLS sources play without issues on other devices and platforms.

Still no answer?? same problem..


[IOTDB-1597] Finish DIFF encoding algorithm which is reserved in enum before

In the enum class: TSEncoding, there's  DIFF encoding, so when user want to choose a type of encoding algorithm(or input the wrong encoding type name), DIFF encoding is in the output hint and is one of IoTDB's recommending encoding type,
but in IoTDB, DIFF encoding has not been added before, which I think may cause some problems.
I think it's necessary to finish it.
Both DIFF and TS_2DIFF encoding are based on delta encoding algorithm,
so I finish DIFF using similar interfaces and structures like TS_2DIFF to make it easier to understand.

please apply this patch to solve the conflicts.
git apply solve_conflict.txt
solve_conflict.txt

there are too many duplications between DIFFEncoder and DeltaBinaryEncoder. Better to inherit DeltaBinaryEncoder, rather than copy codes.

What is the benefit to add such a method? Trying to give some experimental results to show when should we use it...

there are too many duplications between DIFFEncoder and DeltaBinaryEncoder. Better to inherit DeltaBinaryEncoder, rather than copy codes.
What is the benefit to add such a method? Trying to give some experimental results to show when should we use it...

I have made some experiment abouot it(https://cwiki.apache.org/confluence/display/IOTDB/DIFF+encoding's+perfomance).
As I said in email-list, this method's performance is not better than TS_2DIFF (included in 'DeltaBinaryEncoder'), only when the data set is in best circumstances, the new method can save very little room (about 4 bytes, in head)
I add it beacuse DIFF is a reserved method, it's one of the recommending method when user want to choose a encoding method in IoTDB, but it's not finished before. It's in the system prompt, but user can't chooose it

Hi, please resolve the conflicts

Coverage increased (+0.02%) to 67.386% when pulling fd3813587c5c804bd614a86f37ef79df20376b00 on 5Reasons:addDiff into fb18357edee14e60893e968aeddc3177fba868bc on apache:master.


Update to natest NAEI data

This PR updates to latest NAEI data

This doesn't seem to delete the old emissions data?


problem provisioning sharepoint folder

quote: When you create a private/shared channel, the SharePoint site might fail to provision. If the site fails to provision after 5 minutes, use the Get filesFolder API to trigger provisioning.
This does not seem to work, i have repeatedly tried to call the "get-files-folder" API for days and months for some teams rooms. The only thing that seems to solve the problem is if a user navigates to the private team-channel in question, and manually clicks the "files" tab.

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

ID: c06a8a7a-b0fa-8304-84f5-9ada3b3c2ea5
Version Independent ID: 2c33f569-87dd-68be-2048-770788eae940
Content: Create channel - Microsoft Graph v1.0
Content Source: api-reference/v1.0/api/channel-post.md
Product: microsoft-teams
Technology: microsoft-graph
GitHub Login: @nkramer
Microsoft Alias: MSGraphDocsVteam

This is honestly the same issue. https://github.com/microsoftgraph/microsoft-graph-docs-contrib/issues/4452
This needs to get escalated. It was fine that this was a little buggy in 2020 when teams was a brand new product, but not being able to pre-provision our rooms with the correct setup in 2024 is honestly unacceptable.
If it cant be fixed, a suitable workaround should at least be added to the documentation.
The previous issue did not get solved. They added an internal process to get their employees to click the "files tab"

Hello @Ballzer0 - Thanks for raising your query.
We will look into it and let you know the updates.

We checked this at our end and it is working fine at our end. Sharepoint site gets created as soon as we create a private channel.

We checked this at our end and it is working fine at our end. Sharepoint site gets created as soon as we create a private channel.

If the site provisioning is delayed due to failures, there are different ways that trigger site provisioning for the private channel, one of which is visiting the Files tab. In such a case, the site provisioning gets retriggered (which you observed as well) followed by the channel membership (members + admins) sync to the site in a background operation. If this also encounters failures, we have a user-triggered background periodic sync (24-48 hrs) from the client that will sync channel membership to the channel site. That will eventually sync the membership to the site.
Let me know if that is not happening for you, if so please share the logs including the team id, channel id, tenant id.

Its still an issue on our end.. the screenshot you took is of the "files tab" that means you have visited it already.

Can you find the drive via the graph api, without ever having visited the site manually?
Do you have an email or something where i can share logs and diagnostic information? Its against our policy to share these details online

Please share these details at<EMAIL_ADDRESS>

Please share these details at<EMAIL_ADDRESS>
just sent you an email with our diagnostic information. Just titled the email with "Github issue 8982"

according to the documentation. the provisioning of sharepoint resources should have been "self healing" as my requests to the "Get filesFolder" should have fixed the issue.

but this does not seem to be working.

@Ballzer0 - Thank you for additional details, could you also share the request id and timestamp for channel creation. Looks like you shared request id for accessing sharepoint folder. Please share the channel creation logs as well.

unfortunetly i dont have that request id. We only have logs of failed requests.

@Ballzer0 - Thank you for additional details, could you also share the request id and timestamp for channel creation. Looks like you shared request id for accessing sharepoint folder. Please share the channel creation logs as well.

unfortunetly i dont have that request id. We only have logs of failed requests.

@Meghana-MSFT  is this issue just going to die since i cant find any channel creation logs?

We shared the details shared by you with engineering team. We will follow up and get back to you.

Hello @Ballzer0 - Thanks for sharing the information.
We will look into it and let you know the updates.


Convert to ONNX and TensorRT

Hi, I'm trying to export this to ONNX to later convert to TensorRT for deployment. Even though this model is one-stream one-stage making it a lot easier to convert, I've encountered several warnings about converting a tensor to Python [integer, boolean, etc.]. The problems are with 2 torch.linspace() here, and math.ceil() and the equality operator here.
Below is one of the warnings:
TracerWarning: Converting a tensor to a Python boolean might cause the trace to be incorrect.
We cant record the data flow of Python values, so this value will be treated as a constant in the future.

Has the author or anyone successfully converted this to ONNX and TensorRT? Can you guys give me some suggestions on how to work around this issue, or directly convert to TensorRT without facing this again?
Thanks a lot.

For torch.linspace, you can replace it with torch.arange.
Maybe you can replace math.ceil with another function supported by ONNX or implement it on you own.
if lens_keep == lens_s: can be simply removed since the inequality has already been guaranteed outside this function.

I'll also try to add ONNX/TensorRT support when I have time and pull requests are welcome.

Hi, I'm trying to export this to ONNX to later convert to TensorRT for deployment. Even though this model is one-stream one-stage making it a lot easier to convert, I've encountered several warnings about converting a tensor to Python [integer, boolean, etc.]. The problems are with 2 torch.linspace() here, and math.ceil() and the equality operator here.
Below is one of the warnings:
TracerWarning: Converting a tensor to a Python boolean might cause the trace to be incorrect.
We cant record the data flow of Python values, so this value will be treated as a constant in the future.

Has the author or anyone successfully converted this to ONNX and TensorRT? Can you guys give me some suggestions on how to work around this issue, or directly convert to TensorRT without facing this again?
Thanks a lot.

Hello, dalao. Can I borrow your script of exporting the onnx file?

@Stoooner My exporting script is just the same as any normal one. The difference is my modifications to some operations inside the model to fix incompatibility issues, but I don't really remember correctly all the things I have done. You can send me an email at<EMAIL_ADDRESS>with the specific problems you encounter and I'll show you a workaround.
P/s: I'm the one who emailed you asking for help with exporting Stark to TensorRT ;)


docs(deprecations): add new page including upcoming deprecation details

Part of https://github.com/carbon-design-system/carbon/issues/12497
Changelog
New

Add new page for deprecations, add details of upcoming deprecations

I purposely left this page out of the left nav for now. I don't think there's a strong case for discoverability of this page. The intent is to link to carbondesignsystem.com/deprecations from the deprecation message that will be visible on npmjs.com as well as developer terminal/consoles when installing the deprecated packages. but let me know what you think!

Update various references to v10 and deprecated packages across the site

@alisonjoseph Yeah I was surprised too 😱
I'm not opposed to adding it to the nav, just felt 50/50 to me if we'd want it there. Sorta feels like it shouldn't be discoverable, to instead have users hit that page only when they're guided there? Like from the npm deprecation message or the package readme's. What do you think?  I also couldn't figure out where we'd want to put it in the left nav 🤔

@Kritvi-bhatia17 great points, thanks for bringing them up!
These deprecations are slightly different than feature-flag-related deprecations. These docs relate to the larger/more broad package and package version "deprecations" which happen after a package's end-of-support date. These are different from deprecations within the packages (components, functions, etc.). We should discuss and figure out where those "intra-package" deprecations docs should live. I skew towards continuing to document them in situ at the package-level storybook, but maybe there is a place for some kind of content about them on the website.
The package and version deprecations here will be immediately relevant on Monday as we'll be doing a formal deprecation on npm for both these packages, as well as v10.x versions of the other @carbon/colors, etc.
One other thing regarding the left nav concern is I think it's beneficial for this url to be as short as possible. We'll be using it in the deprecation message on npm and it will be printed in developer consoles where space is limited. Example:
This package is no longer supported. More info at carbondesignsystem.com/deprecations

vs
This package is no longer supported. More info at carbondesignsystem.com/components/overview/deprecations/

Oh, I see! Got it—thanks a lot, @tay1orjones, for such a detailed explanation.
If needed, we can discuss later how to handle feature-flag-related deprecations for both developers and designers. I believe there might already be a section for that on the website, but I’ll need to check; that’s a bit off-topic for now.
In any case, you guys have more knowledge and insight on this, will leave it up to y'll!

@alisonjoseph @annawen1 @Kritvi-bhatia17 I've updated this to include the latest feedback, and also added a section for v10 elements packages and carbon-icons

I'm just going to leave this comment here since I didn't get it in before the merge. There are some formatting/visual things I would like to fix on this page if we ever make the deprecations page visible in the nav.

I'm just going to leave this comment here since I didn't get it in before the merge. There are some formatting/visual things I would like to fix on this page if we ever make the deprecations page visible in the nav. Just to help with type hierarchy and information processing.

Derp! Sorry about that. I should have let you have a pass before merging.

@aagonzales sounds good, the main thing I was optimizing for was anchor links per-package so we can deep link for support purposes. Like carbondesignsystem.com/deprecations#carbon-icons for example


No way to capture top level dependencies from yarn projects

Since the yarn lock file does not contain dependency information about the root project, the tool flattens all the transitive dependencies and represents them as direct dependencies of the root in the sBOM for yarn projects.
Issue not present in npm or pnpm as their lock files represent this relationship accurately.
Would propose to modify the logic to generate the direct relationships for the root project only from package.json and the rest from yarn.lock as it currently is.

@ajmalab I exactly know what you're talking about. I tried to mirror what yarn list does. Will revisit and see if this could be improved.
https://github.com/CycloneDX/cdxgen/blob/master/index.js#L1896

@prabhu any update on this? I tried to build the cdxgen for react project: https://github.com/facebook/react
I noticed that it is adding all the dependencies as if it is coming from the root package.json.
Mostly for mono repos it is very hard to find the exact root project where the dependency is present. It should identify all the dirs with package.json as separate components.
Command used: cdxgen -t js

Added needs contributor label

Is there anything that can be done with the SrcFile property in the meanwhile. Ideally, it must list all the lock files a given component was found.


Allow configuring a producer for at-most-once delivery

Currently we only support at-least-once, retaining unacknowledged messages and re-sending them at the next delivery. Doing at-most-once is tricky, so I'd like to see some concrete use cases first.

Closing due to a lack of activity.


feat: separate flow for folder and file uploads

Known issue: when using drag and drop for folder uploads, paths are not retained correctly.  This is likely because drag and drop doesn't set webkitRelativePath on File objects

Also if I try to download a folder that I just uploaded I get 404 error

but it does work for both websites and single files


removing unrelated articles to avoid confusion

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

@AndreasWolter Not sure of the motivation here. The links you removed are still related to certificates.
Also, our content guidelines have a requirement of 3 links in the related content. I know we don't always stick to that, but we can't remove these and not replace them.

The 2 links refer to certificates within the SQL Engine, exposed in master and other databases.
This is not related to certificates that are used by the OS for encrypting the connections. Those you cannot grant permissions for using TSQL.  To avoid people mixing up topics I thought its better to delete these.
Here are some more useful references if you need to add something instead: https://learn.microsoft.com/en-us/sql/database-engine/configure-windows/certificate-requirements?view=sql-server-ver16
https://learn.microsoft.com/en-us/sql/database-engine/configure-windows/certificate-overview?view=sql-server-ver16

That first one in the related content is the same as your first example, so we'll just take the second one and add it.

oups, pardon the confusion


[CORE-1706] Cluster-defaults-aware CreatePipelineV2

Are we doing the environment variable migration in this PR?

No, that will be in CORE-1785.


Target a child turbo-frame without having to create another blade

Hi!
Here is an extract of my code.

<x-turbo-frame :id="$listing">

Description

    <x-turbo-frame :id=["$listing", "quantity_component"]>

            <form action="/prototype/variant/{{ $listing->variant->id }}/decrease" method="POST">
                @csrf
                <button>
                    -
                </button>
            </form>

            <x-turbo-frame :id="[$listing, 'quantity_in_cart']">
                <input value="{{ $listing->quantity_in_cart }}">
            </x-turbo-frame>

            <form action="/prototype/variant/{{ $listing->variant->id }}/increase" method="POST">
                @csrf
                <button>
                    +
                </button>
            </form>

    </x-turbo-frame>
</x-turbo-frame>

if (request()->wantsTurboStream()) {
    // return response()->turboStream($listing) // this doesn't work, it takes the whole _listing.blade.php
    //     ->target(dom_id($listing, 'quantity_in_cart')); // and puts it into the quantity_in_cart turbo-frame

    // this targets :id="$listing", not as efficient, causes img to reload as well
    return response()->turboStream($listing);
}

Is there a way to write the PHP to replace only the quantity_in_cart without having to extract its insides into another blade file?
Is there a convention on naming the blade if I were to extract it?
If extraction is a must, does it make sense to add a method ->returnOnly("quantity_in_cart_listing_xxx")? (Yes, I'm aware of the performance hit haha)

I try to keep my blade files relatively intact so that it is still possible to get an overview when reading it. Hope I'm making sense here.
The above is a numeric increase/decrease component, I'm planning to replace the input quantity with a  such that if it is clicked, the quantity_component will turn into a form with 1 textbox and save button. Would appreciate if you could share how to name/organize the blade files so that it remains readable.
Thank you!

I made quite a bit of progress and wanted to add on to this.
Perhaps ->returnOnly[[... array of frames...]); which in turn gets "translated" into Turbo Stream combo https://github.com/tonysm/turbo-laravel#turbo-streams-combo will make code shorter

So you want to limit which pieces of the view will be returned based on the DOM element? I try to limit the package to how the turbo-rails gem work as much as I can and that's not built-in there.
One thing you could try is extracting that DOM element to another partial/view/snippet, and use the view() helper. Something like:
return response()
  ->turboStream($listing)
  ->action(dom_id($listing, 'quantity_in_cart'))
  ->view('listings._quantity_in_cart_listing', ['any' => 'local variable']);

All the conventions I use are documented in the readme. I find it useful to break up a view into smaller chunks if I want to reuse them.


Try to use different instances

Hi!
With some other tasks your cron works nicely, but with next primitive task for cleaning cart from outdate items:
 const cartItems = (ready) => {
    bound(() => {
        ready();
        // some cleaning code
    });
};
  const testCartItems = cartItemsCron.setInterval(cartItems, 20 * 1000, 'cartItems');

i have problems:
[josk] [josk] [cart-itemssetInterval] Something went wrong with one of your tasks is missing.
          Try to use different instances.
           It's safe to ignore this message.
          If this task is obsolete - simply remove it with `JoSk#clearTimeout('cart-itemssetInterval')`,
          or enable autoClear with `new JoSk({autoClear: true})`

Please help me, thanks

I guessed, there should be only one single cron for different tasks with different taskIds!


Repo sync for protected CLA branch

The pull request is created from master637638879170928170 to master to fix git push error for protected CLA branch

@ghogen : Thanks for your contribution! The author(s) have been notified to review your proposed change. @bytesguy


Configure releases via JReleaser

Configures releases via JReleaser

creates x-platform custom Java Runtimes (jlink) for 8 targets
creates 3 native executables with GraalVM native image
creates 4 installers with jpackage
all binaries are checksumed with SHA256
rolling early-access releases on every push to main
final release by manual trigger on GH UI

Converting to draft as JReleaser v1.0.0-M3 is needed.

@HanSolo ready for review


chore: update repo by service bot

This is a routine update from cc-service-bot based on the service.yml in your repo. This PR
should be approved and merged as soon as CI passes.

CHANGELOG
FILE NAME - CHANGED BY - COMMIT MESSAGE
.semaphore/project.yml - framework - removing generated internal project.yml
.semaphore/project_public.yml - framework - removing generated public project.yml
.semaphore/semaphore.yml - framework - chore: update repo semaphore config


QoS API Updates and Timer Resolution changes

Updates wording to reflect QoS naming and links to forthcoming QoS docs (separate PR).
Documents new timer resolution behavior for Windows 11 and related API changes to control this behavior.

@mabellon-msft : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@Karl-Bridge-Microsoft : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@Karl-Bridge-Microsoft : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@Karl-Bridge-Microsoft : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@Karl-Bridge-Microsoft : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off


Question: is there any way to monitor tcp based (Postgres) traffic?

I use PostgresQL as database. The network protocol is TCP (set by port name).
I want to monitor the network traffic between my components and Postgres. But I am not able to collect any metrics from or to Postgres (only metrics with label value "unknown" are available). In the documentation I found the following: "HTTP requests that invoke a local response from Envoy have “unknown” destination_* labels on metrics. ". - But is there any way to configure my clients, Osm, Envoy or Postgres to enable monitoring?
I have set the envoy log level to debug, but I can't find any reason for a "local response" from the envoy proxy.
I would be very happy if someone has an idea!

@shashankram Yes, the osm_request_total and osm_request_duration metrics are only expected to work for HTTP traffic currently. Envoy exposes TCP metrics on clusters and listeners which may be enough depending on what you need, but you may need to tweak the default Prometheus configuration for them to be scraped:
https://github.com/openservicemesh/osm/blob/5a885ef60653fb4c987c847b33ece14bad56dfba/charts/osm/templates/prometheus-configmap.yaml#L57-L59
Envoy provides a Postgres filter which exposes metrics specific to Postgres traffic, but currently there's no way for OSM to configure that.

Since PostgreSQL will use TCP-based (appProtocol: tcp) routing in OSM, at the very least default metrics for TCP clusters should be published by Envoy.
We can provide further metrics by:

Adding custom metrics/labels using WASM for TCP: #2506
Allow setting appProtocol: postgresql on service ports, where we add the additional postgres_proxy filter for such ports

@benediktwetzel, are you able to retrieve the default metrics for TCP based clusters?

May i can reopen this issue.
I am not able to retrieve the envoy metrics for TCP based clusters.
I have added your snippet to my service monitor:
apiVersion: monitoring.coreos.com/v1
kind: PodMonitor
metadata:
  name: envoy-pod-monitor-tcp
spec:
  podMetricsEndpoints:
  - interval: 10s
    metricRelabelings:
    - action: keep
      regex: '(envoy_server_live|envoy_cluster_health_check_.*|envoy_cluster_upstream_rq_xx|envoy_cluster_upstream_cx_active|envoy_cluster_upstream_cx_tx_bytes_total|envoy_cluster_upstream_cx_rx_bytes_total|envoy_cluster_upstream_rq_total|envoy_cluster_upstream_cx_destroy_remote_with_active_rq|envoy_cluster_upstream_cx_connect_timeout|envoy_cluster_upstream_cx_destroy_local_with_active_rq|envoy_cluster_upstream_rq_pending_failure_eject|envoy_cluster_upstream_rq_pending_overflow|envoy_cluster_upstream_rq_timeout|envoy_cluster_upstream_rq_rx_reset|envoy_cluster_upstream_rq_retry.*|^osm.*)'
      sourceLabels:
      - __name__
    - action: keep
      regex: envoy_.*osm_request_(total|duration_ms_(bucket|count|sum))
      sourceLabels:
      - __name__
    - action: replace
      regex: envoy_response_code_(\d{3})_source_namespace_.*_source_kind_.*_source_name_.*_source_pod_.*_destination_namespace_.*_destination_kind_.*_destination_name_.*_destination_pod_.*_osm_request_total
      sourceLabels:
      - __name__
      targetLabel: response_code
    - action: replace
      regex: envoy_response_code_\d{3}_source_namespace_(.*)_source_kind_.*_source_name_.*_source_pod_.*_destination_namespace_.*_destination_kind_.*_destination_name_.*_destination_pod_.*_osm_request_total
      sourceLabels:
      - __name__
      targetLabel: source_namespace
    - action: replace
      regex: envoy_response_code_\d{3}_source_namespace_.*_source_kind_(.*)_source_name_.*_source_pod_.*_destination_namespace_.*_destination_kind_.*_destination_name_.*_destination_pod_.*_osm_request_total
      sourceLabels:
      - __name__
      targetLabel: source_kind
    - action: replace
      regex: envoy_response_code_\d{3}_source_namespace_.*_source_kind_.*_source_name_(.*)_source_pod_.*_destination_namespace_.*_destination_kind_.*_destination_name_.*_destination_pod_.*_osm_request_total
      sourceLabels:
      - __name__
      targetLabel: source_name
    - action: replace
      regex: envoy_response_code_\d{3}_source_namespace_.*_source_kind_.*_source_name_.*_source_pod_(.*)_destination_namespace_.*_destination_kind_.*_destination_name_.*_destination_pod_.*_osm_request_total
      sourceLabels:
      - __name__
      targetLabel: source_pod
    - action: replace
      regex: envoy_response_code_\d{3}_source_namespace_.*_source_kind_.*_source_name_.*_source_pod_.*_destination_namespace_(.*)_destination_kind_.*_destination_name_.*_destination_pod_.*_osm_request_total
      sourceLabels:
      - __name__
      targetLabel: destination_namespace
    - action: replace
      regex: envoy_response_code_\d{3}_source_namespace_.*_source_kind_.*_source_name_.*_source_pod_.*_destination_namespace_.*_destination_kind_(.*)_destination_name_.*_destination_pod_.*_osm_request_total
      sourceLabels:
      - __name__
      targetLabel: destination_kind
    - action: replace
      regex: envoy_response_code_\d{3}_source_namespace_.*_source_kind_.*_source_name_.*_source_pod_.*_destination_namespace_.*_destination_kind_.*_destination_name_(.*)_destination_pod_.*_osm_request_total
      sourceLabels:
      - __name__
      targetLabel: destination_name
    - action: replace
      regex: envoy_response_code_\d{3}_source_namespace_.*_source_kind_.*_source_name_.*_source_pod_.*_destination_namespace_.*_destination_kind_.*_destination_name_.*_destination_pod_(.*)_osm_request_total
      sourceLabels:
      - __name__
      targetLabel: destination_pod
    - action: replace
      regex: .*(osm_request_total)
      sourceLabels:
      - __name__
      targetLabel: __name__
    - action: replace
      regex: envoy_source_namespace_(.*)_source_kind_.*_source_name_.*_source_pod_.*_destination_namespace_.*_destination_kind_.*_destination_name_.*_destination_pod_.*_osm_request_duration_ms_(bucket|sum|count)
      sourceLabels:
      - __name__
      targetLabel: source_namespace
    - action: replace
      regex: envoy_source_namespace_.*_source_kind_(.*)_source_name_.*_source_pod_.*_destination_namespace_.*_destination_kind_.*_destination_name_.*_destination_pod_.*_osm_request_duration_ms_(bucket|sum|count)
      sourceLabels:
      - __name__
      targetLabel: source_kind
    - action: replace
      regex: envoy_source_namespace_.*_source_kind_.*_source_name_(.*)_source_pod_.*_destination_namespace_.*_destination_kind_.*_destination_name_.*_destination_pod_.*_osm_request_duration_ms_(bucket|sum|count)
      sourceLabels:
      - __name__
      targetLabel: source_name
    - action: replace
      regex: envoy_source_namespace_.*_source_kind_.*_source_name_.*_source_pod_(.*)_destination_namespace_.*_destination_kind_.*_destination_name_.*_destination_pod_.*_osm_request_duration_ms_(bucket|sum|count)
      sourceLabels:
      - __name__
      targetLabel: source_pod
    - action: replace
      regex: envoy_source_namespace_.*_source_kind_.*_source_name_.*_source_pod_.*_destination_namespace_(.*)_destination_kind_.*_destination_name_.*_destination_pod_.*_osm_request_duration_ms_(bucket|sum|count)
      sourceLabels:
      - __name__
      targetLabel: destination_namespace
    - action: replace
      regex: envoy_source_namespace_.*_source_kind_.*_source_name_.*_source_pod_.*_destination_namespace_.*_destination_kind_(.*)_destination_name_.*_destination_pod_.*_osm_request_duration_ms_(bucket|sum|count)
      sourceLabels:
      - __name__
      targetLabel: destination_kind
    - action: replace
      regex: envoy_source_namespace_.*_source_kind_.*_source_name_.*_source_pod_.*_destination_namespace_.*_destination_kind_.*_destination_name_(.*)_destination_pod_.*_osm_request_duration_ms_(bucket|sum|count)
      sourceLabels:
      - __name__
      targetLabel: destination_name
    - action: replace
      regex: envoy_source_namespace_.*_source_kind_.*_source_name_.*_source_pod_.*_destination_namespace_.*_destination_kind_.*_destination_name_.*_destination_pod_(.*)_osm_request_duration_ms_(bucket|sum|count)
      sourceLabels:
      - __name__
      targetLabel: destination_pod
    - action: replace
      regex: .*(osm_request_duration_ms_(bucket|sum|count))
      sourceLabels:
      - __name__
      targetLabel: __name__
    path: /stats/prometheus
    targetPort: 15010
  selector:
    matchLabels:
      monitoring: enabled

Do you have an idea what could be the problem?


HiddenSelect does not provide a value for collections with size > 300, throwing console error

🐛 Bug Report
When rendering collections with a size of 300 or more, HiddenSelect does not provide a fallback value for the rendered input field which logs a console error for value of null, then uncontrolled -> controlled switch when a value is then set / provided onSelectionChange.
🤔 Expected Behavior
No console errors, probably needs the same state.selectedKey ?? '' that useHiddenSelect uses for the selectProps.
😯 Current Behavior
Console error for invalid value, then error for uncontrolled -> controlled state switch.
💁 Possible Solution
state.selectedKey ?? '' on L137
🔦 Context

💻 Code Sample
https://codesandbox.io/s/epic-swirles-2ho1my?file=/src/index.js
🌍 Your Environment

Software
Version(s)

react-spectrum
3.24.1

Browser
Chrome

Operating System

🧢 Your Company/Team

🕷 Tracking Issue (optional)

I see, you mean this one?

Warning: value prop on input should not be null. Consider using an empty string to clear the component or undefined for uncontrolled components.

followed by

Warning: A component is changing an uncontrolled input to be controlled. This is likely caused by the value changing from undefined to a defined value, which should not happen.

I think your diagnosis seems correct. Would you like to open a PR?

@snowystinger Created, let me know how it looks. Thanks.


config.json: Add topics & difficulty for pov

See #345 & #731

Was not sure if we should consider "Graphs" and "Trees" redundant. Going by the way nextercism is shaping up I erred on the side of more topics being better than less.


add version components, string_template

This ticket is to add raw components to the dictionary returned by get_versions(), and to provide some sort of versioneer.string_template= config setting to control what the default get_version() returns. The details are in a comment in #24.

FYI, I'm no longer aiming to provide a string template, as that turned out to be too difficult. But I have been able to distill the "turn a bunch of version data into a single version string" code down into a single function, and that function will soon take a "style" configuration knob, to choose between several pre-configured approaches. And we can take patches to add new ones.
Using an actual template, as in version = template % datadict, turned ugly because you need a whole lot of keys with values like "empty string or -DISTANCE", and then number of possible combinations got large. The error cases made it worse (missing tags, etc). It really helps to have some code running to assemble those strings.

18ab1e3 landed the "styles" work, which replaces this feature, so I'm closing this issue. If you find a form of the version string that isn't currently handled by one of the existing styles, please file an issue and we can add it (to src/render.py).


Query for images of neurons broken on v2a

Support info:
Wed Jun 03 2020 17:52:45 GMT 0100 (British Summer Time)
Chrome 83.0.4103.61 [612,624]
https://v2a.virtualflybrain.org/org.geppetto.frontend/geppetto?id=FBbt_00040041&i=VFB_00101567
+ Buffered 18000 tiles
+ Buffered 18000 tiles
+ Buffered 18000 tiles
+ Buffered 18000 tiles
+ Buffered 18000 tiles
+ Buffered 18000 tiles
+ Buffered 18000 tiles
+ Query requested: ImagesNeurons vest
+ Buffered 18000 tiles
+ Buffered 18000 tiles

My bad was testing a fixed version for multiple alignments - fixed on latest version


Add config setting for transparent slide backgrounds

Current is black opaque. Actually make the setting so you can specify bg color. Current is 000000ff (RGBA black opaque). Make it so you can have that be anything.
will be a quick change. I think writing this issue took longer than this will take to implement

done


Unstable rule selection by the GHOST action selector

The GHOST action selector makes unpredictable rule selection between two same rules but different in their goal strength (ghost-parse "#goal: (goal1=0.7) u: (hi) hello there ^keep")  and (ghost-parse "#goal: (goal1=0.5) u: (hi) hi there ^keep"). Running the code (test-ghost "hi") gives sometimes ((WordNode "hi")  (WordNode "there") ) and other times ((WordNode "hello")  (WordNode "there") ).
The expected response was expected to be of the rule with the highest goal strength, that is ((WordNode "hello")  (WordNode "there") )

There are also inconsistencies in output of rule goal strength with ghost-rule-tv command.
(FYI: tested without starting cog-server and without using ecan based rules)
scheme@(guile-user)> (ghost-parse "#goal: (goal1=0.4) u: lbl2(hi) hi there ^keep")
scheme@(guile-user)> (ghost-parse "#goal: (goal1=0.8) u: lbl2(hi) hello there ^keep")
scheme@(guile-user)> (test-ghost "hi")
[2018-10-31 09:43:29:500] [WARN] No configuration file was loaded! Param=STARTING_STI_FUNDS
[2018-10-31 09:43:29:500] [WARN] No configuration file was loaded! Param=STARTING_LTI_FUNDS
[2018-10-31 09:43:29:500] [WARN] No configuration file was loaded! Param=STI_FUNDS_BUFFER
[2018-10-31 09:43:29:500] [WARN] No configuration file was loaded! Param=LTI_FUNDS_BUFFER
[2018-10-31 09:43:29:500] [WARN] No configuration file was loaded! Param=TARGET_LTI_FUNDS
[2018-10-31 09:43:29:500] [WARN] No configuration file was loaded! Param=TARGET_STI_FUNDS
[2018-10-31 09:43:29:500] [WARN] No configuration file was loaded! Param=ECAN_STARTING_ATOM_STI_WAGE
[2018-10-31 09:43:29:500] [WARN] No configuration file was loaded! Param=ECAN_STARTING_ATOM_LTI_WAGE
[2018-10-31 09:43:29:500] [WARN] No configuration file was loaded! Param=ECAN_MAX_AF_SIZE
[2018-10-31 09:43:29:505] [INFO] [say] (hello there)
$1 = ((WordNode "hello")
(WordNode "there")
)
Action selection seems correct in this case, but running ghost-rule-tv "lbl2" returned the other value.
scheme@(guile-user)> (ghost-rule-tv "lbl2")
$2 = (stv 0.400000 0.900000)
The top level goal strength is not recognized by the same command:
scheme@(guile-user)> (ghost-parse "goal: (please_user=0.8)")
scheme@(guile-user)> (ghost-parse "u: lbl1 (hello) Hello wonderful human")
[2018-10-30 12:38:31:960] [WARN] [GHOST] Did you forget to link a goal to the rule?
scheme@(guile-user)> (ghost-rule-tv "lbl1")
$2 = (stv 0.900000 0.900000)

@joejnke Action selection is probabilistic, so not always choosing the one with the highest weight is the expected behavior here.

@simonmekit Again, put everything in a text file and use ghost-parse-files to parse rules. If you want to call ghost-parse repeatedly, don't forget to put all the related goals/rules etc in one call, i.e. (ghost-parse "#goal: (please_user=0.8) u: lbl1 (hello) Hello wonderful human") in this case.

yes, indeed using ghost-parse-file makes stable action selection for same rule with different goal strength.
The Ghost tutorial  could be updated with ghost-parse-file in addition to  ghost-parse to align with subsequent test process.

@leungmanhin as you mentioned rule-level goal also works fine with ghost-parse-file and  ghost-rule-tv  commands. However, it seems the concept of top-level goal described in the tutorial is not properly working.
"ghostfile.ghost" contains these subsequent lines :
#goal: (goal1=0.4) u: lbl2(hi) hi there ^keep
#goal: (goal1=0.8) u: lbl2(hi) hello there ^keep
goal: (please_user=0.8)
u: lbl1(hello) Hello wonderful human
u: lbl3(Dr. Watson) hello everyone ^keep
scheme@(guile-user)> (ghost-rule-tv "lbl2")
$1 = (stv 0.800000 0.900000)
scheme@(guile-user)> (ghost-rule-tv "lbl1")
$2 = (stv 0.800000 0.900000)
scheme@(guile-user)> (ghost-rule-tv "lbl3")
$3 = (stv 0.800000 0.900000)

"ghostfile.ghost" contains these subsequent lines :
#goal: (goal1=0.4) u: lbl2(hi) hi there ^keep
#goal: (goal1=0.8) u: lbl2(hi) hello there ^keep
goal: (please_user=0.8)
u: lbl1(hello) Hello wonderful human
u: lbl3(Dr. Watson) hello everyone ^keep
scheme@(guile-user)> (ghost-rule-tv "lbl2")
$1 = (stv 0.800000 0.900000)
scheme@(guile-user)> (ghost-rule-tv "lbl1")
$2 = (stv 0.800000 0.900000)
scheme@(guile-user)> (ghost-rule-tv "lbl3")
$3 = (stv 0.800000 0.900000)

@simonmekit Sorry I don't see any problem in the above example... What is the expected result? Or are you just talking about the ones in the tutorial?

yes, I was running tests to make sure that the tutorial complies with current updates and prepare some test-suite. Top level goal works fine with ghost-parse-file, sorry @leungmanhin for confusion!

@simonmekit no problem, thanks for doing all these!


Disconnect server???

Sorry for bothering, but I put up heroku file still running normally but service peer calls on browser mobile  phone and browser on pc didn't connect...
Thank you,

Problem is: not run https://localhost:3000, thanks you.


Higher-dimensional tensors

I notice that you have vectors and matrices. Would you be willing to accept PRs adding a few more dimensions? We can leave Vector and Matrix and make them aliases of something like Tensor1 and Tensor2. Then we can start to add operations like higher-dimensional convolution and such.
If this is outside the scope of aljabar, I don't mind creating a new crate, but I figure this is a good place for collective const generics experimentation on linear algebra, so I wanted to see if this is of interest.

PR acceptance is pretty ad-hoc at the moment but I will say that any addition that can be in a backwards compatible manner (I.e. passing existing tests) that provides such generality I think makes an extremely strong case for being accepted. At the very least, I would love to see whatever you come up with, whether it manifests as a PR here or in a separate crate

I'm going to close this issue because I do not believe that this dimensionality is expressible with const generics in rust at the current moment


[vcpkg docs] Modify incorrect description of  valid clear

Describe the pull request

What does your PR fix?
The valid clear of --binarysource is disable load the cache in machine, so the description of it is incorrect, change the incorrect decription.

Thank you!


fix: Track L1 block for last L2 block body retrieved

The archiver was keeping a single L1 pointer for L2 blocks, shared by block metadata and block bodies, using the min of the two. However, if a block metadata had no corresponding block body, then the L1 pointer would not be advanced, leading to the same block metadata to being downloaded again, which triggered an error of expected L2 block mismatch.
Having no corresponding block body happens when the tx effects hash is not submitted by the sequencer, which happens when it is detected to have been uploaded already, which happens when the tx effects hash is repeated across two blocks, which happens when two blocks are empty (ie have only padding txs).
By adding separate tracking pointers, we ensure that we don't accidentally process the same block header twice from the archiver. This PR also adds a try/catch to the archiver loop so it doesn't bring down the entire node if it runs into an error.
Fixes #7918

Benchmark results
Metrics with a significant change:

protocol_circuit_simulation_time_in_ms (private-kernel-tail-to-public): 8,626 (+221%)

Detailed results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
Proof generation
Each column represents the number of threads used in proof generation.

Metric
1 threads
4 threads
16 threads
32 threads
64 threads

proof_construction_time_sha256_ms
5,774
1,560
703 (+1%)
768 (+2%)
780 (+2%)

proof_construction_time_sha256_30_ms
11,914
3,215 (+1%)
1,427 (+1%)
1,456 (+1%)
1,486 (+1%)

proof_construction_time_sha256_100_ms
44,554 (+1%)
12,651 (+3%)
6,014 (+6%)
5,753 (+2%)
5,634 (+2%)

proof_construction_time_poseidon_hash_ms
79.0
34.0
34.0
59.0
87.0 (-1%)

proof_construction_time_poseidon_hash_30_ms
1,534
421
201
230 (+2%)
268 (-4%)

proof_construction_time_poseidon_hash_100_ms
5,670
1,540 (+1%)
681 (+1%)
746 (+1%)
756 (+1%)

L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
4 txs
8 txs
16 txs

l1_rollup_calldata_size_in_bytes
4,324
7,844
14,852

l1_rollup_calldata_gas
49,720
92,424
177,656

l1_rollup_execution_gas
1,294,383
2,042,055
3,869,326

l2_block_processing_time_in_ms
255 (-2%)
445 (-2%)
798 (-2%)

l2_block_building_time_in_ms
9,647 (-1%)
18,872
37,893 (+1%)

l2_block_rollup_simulation_time_in_ms
9,647 (-1%)
18,872
37,893 (+1%)

l2_block_public_tx_process_time_in_ms
8,036 (-1%)
17,012
35,871

L2 chain processing
Each column represents the number of blocks on the L2 chain where each block has 8 txs.

Metric
3 blocks
5 blocks

node_history_sync_time_in_ms
3,006 (+4%)
3,870 (-2%)

node_database_size_in_bytes
12,697,680
16,765,008 (-1%)

pxe_database_size_in_bytes
16,254
26,813

Circuits stats
Stats on running time and I/O sizes collected for every kernel circuit run across all benchmarks.

Function
time_ms
bytecode_size_in_bytes

FeeJuice:_increase_public_balance
95.6 (+1%)
8,139

FeeJuice:set_portal
9.57 (-3%)
2,362

Token:constructor
121 (-4%)
31,107

FPC:constructor
94.0 (-10%)
22,380

FeeJuice:mint_public
80.3 (-3%)
6,150

Token:mint_public
85.6 (-10%)
11,720

Token:assert_minter_and_mint
91.5 (+2%)
8,028

AuthRegistry:set_authorized
6.64 (-19%)
4,537

FPC:prepare_fee
276 (-3%)
8,812

Token:transfer_public
32.1 (+3%)
47,374

FPC:pay_refund
61.8 (+2%)
12,114

Benchmarking:increment_balance
1,027
7,450

Token:_increase_public_balance
10.8 (-6%)
8,960

FPC:pay_refund_with_shielded_rebate
140 (+1%)
12,663

Public DB Access
Time to access various public DBs.

Function
time_ms

get-nullifier-index
0.158

Tree insertion stats
The duration to insert a fixed batch of leaves into each tree type.

Metric
1 leaves
16 leaves
64 leaves
128 leaves
256 leaves
512 leaves
1024 leaves

batch_insert_into_append_only_tree_16_depth_ms
2.15 (-2%)
3.95 (+1%)
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_count
16.8
31.7
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_ms
0.112 (-2%)
0.112 (+2%)
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_32_depth_ms
N/A
N/A
11.5 (+1%)
17.5 (-3%)
30.5 (-2%)
60.0 (-3%)
112 (-1%)

batch_insert_into_append_only_tree_32_depth_hash_count
N/A
N/A
95.9
159
287
543
1,055

batch_insert_into_append_only_tree_32_depth_hash_ms
N/A
N/A
0.111 (+1%)
0.102 (-2%)
0.0991 (-1%)
0.103 (-2%)
0.100 (-1%)

batch_insert_into_indexed_tree_20_depth_ms
N/A
N/A
14.4 (-1%)
25.4 (-1%)
42.9 (-3%)
81.8 (-4%)
159 (-2%)

batch_insert_into_indexed_tree_20_depth_hash_count
N/A
N/A
109
207
355
691
1,363

batch_insert_into_indexed_tree_20_depth_hash_ms
N/A
N/A
0.109 (-1%)
0.102 (-1%)
0.0997 (-6%)
0.101 (-4%)
0.100 (-3%)

batch_insert_into_indexed_tree_40_depth_ms
N/A
N/A
16.3 (-1%)
N/A
N/A
N/A
N/A

batch_insert_into_indexed_tree_40_depth_hash_count
N/A
N/A
132
N/A
N/A
N/A
N/A

batch_insert_into_indexed_tree_40_depth_hash_ms
N/A
N/A
0.105 (-1%)
N/A
N/A
N/A
N/A

Miscellaneous
Transaction sizes based on how many contract classes are registered in the tx.

Metric
0 registered classes
1 registered classes

tx_size_in_bytes
64,756
668,997

Transaction size based on fee payment method
| Metric |  |
| - |  |


Some commands dont return multiple values

I've tried summary, label and description all of which suggest it is possible to get multiple results by providing multiple IDs, e.g.:
wd label Q18120925 Q22117436 Q22117437
I can only get the first result back. Am I doing anything wrong?

this feature is available only since 5 days, when the v5.0.0 was published, could it be that your version is older than that?

I do apologise, I should have checked for having the latest version first. I updated and can get it working. However I did have to also update node to the latest, I had v6.10.0 before which is later than the version recommended for this, but on that version I got this error:
TypeError: Object.values is not a function
    at entities (/Users/pmackay/.config/yarn/global/node_modules/wikidata-cli/lib/entity_attribute_command.js:14:33)
    at process._tickCallback (internal/process/next_tick.js:103:7)
Context: undefined

no problem :)
thanks for spotting the Object.values issue, it indeed appears to only be available from Node v7.0, so I'm replacing those to avoid having to ask everyone to update Node

all occurrences of Object.values got removed in ee5e90c, the updated version was published as v5.0.2


Rare Pokemon Idea!!!!

Hi. I have a great idea for this bot.
I always catch my rare pokemons by http://pokesnipe.de/
There is the rare pokemon coridates.. I use app player for this and fake GPS. I set he gps cordinates to the rare pokemon, click on it to catch but i dont do anything!! Dont throw ball etc... just but back the cordinates to the last one, where there teleported. When i set it, i can do anything to catch them.
If this could be done, then please make a task for this, this makes the bot f*cking awesome.
Sorry for the bad english.
I'm waiting for answers.

Duplicate with many other, for example #3226

If I understand correctly you can't catch the pokemon when you teleport to it?
 You are teleport to him to start catching but dont do anything!!! Go back and catch him... And you solved the softban :) I catched 20+ rare pokemon like this.

Ah I see. I think there are a few threads requesting an interface with pokesnipers now but not sure if the devs are working on it.

use this repo for sniping.
https://github.com/PokemonGoMap/PokemonGo-Map
and for how to use it, please use slack chat to install and config.

@Fellner96  what do you mean by "You are teleport to him to start catching but dont do anything!!! Go back and catch him..." ? Thanks.

Here is an example:
https://www.youtube.com/watch?v=Me90koMLrwg

I see, yeah no idea how to implement this in the script/ code at the moment heh. thanks

Please use the search function: #1887

It's already supported, if you use https://github.com/PokemonGoMap/PokemonGo-Map with the config.json.map.example you can use it.


Dataset

Do you have an alternative link for Dataset? Thank you!
Previous one in not publicly available anymore: https://drive.google.com/drive/folders/1FHPJRCab-cyLq8IVz83LkU71gOc7gTS8?usp=sharing

Do you have an alternative link for Dataset? Thank you!
Previous one in not publicly available anymore: https://drive.google.com/drive/folders/1FHPJRCab-cyLq8IVz83LkU71gOc7gTS8?usp=sharing

yeah, i hope to


Pin datasets dependency at 2.15

It seems as though many users are receiving errors when upgrading to datasets versions 2.16 and above, and also because datasets on the HF hub are being replaced with Parquets in the background.
We should fix this alongside accomodating #1135 , but in the meantime pinning datasets version in the hopes it will minimize pain for users for now.
#1217 #1311 #1307

Hi ! The three issues you mentioned can be fixed by requiring datasets>=2.14
Sorry for the inconvenience, this is due to converting some datasets to Parquet. And datasets>=2.14 is required to load Parquet datasets with multiple subsets like https://huggingface.co/datasets/allenai/ai2_arc


Configure 0pdd for the project

@proshin-roman 2 puzzles #13, #14 are still not solved.

@proshin-roman 4 puzzles #13, #14, #37, #38 are still not solved.

@proshin-roman 5 puzzles #13, #14, #37, #42, #43 are still not solved; solved: #38.

@proshin-roman 2 puzzles #37, #74 are still not solved; solved: #13, #14, #38, #42, #43.

@proshin-roman the puzzle #37 is still not solved; solved: #13, #14, #38, #42, #43, #74.


No Build - AstroI18nextConfig is not exported by node_modules/astro-i18next/src/types.ts

I have this problem with astro-i18next. In development mode it works perfect, the problem is when I want to build

astro-i18next version: 1.0.0-beta.21
astro version: 1.0.9
OS: WSL with Debian
Browser: Chrome, Brave

It was because of the astro version, now with "astro": "2.1.7" it works perfectly.


[BUG]evaluator keeps failing with promptflow-eval 0.3.1 but works with 0.3.0

Describe the bug
After switching promptflow-eval from 0.3.0 to 0.3.1, for same code, it keeps giving me the error:
2024-07-15 06:52:21 +0000     377 execution.bulk     ERROR    Error occurred while executing batch run. Exception: The input for batch run is incorrect. Input from key 'data' is an empty list, which means we cannot generate a single line input for the flow run. Please rectify the input and try again.

======= Run Summary =======

Run name: "promptflow_evals_evaluators_content_safety_content_safety_contentsafetyevaluator_k3ldgeeq_20240715_065220_068989"
Run status: "Failed"
Start time: "2024-07-15 06:52:20.066987+00:00"
Duration: "0:00:01.488330"
Output path: "/root/.promptflow/.runs/promptflow_evals_evaluators_content_safety_content_safety_contentsafetyevaluator_k3ldgeeq_20240715_065220_068989"

Traceback (most recent call last):
...
    _ = evaluate(
  File "/usr/local/miniconda/lib/python3.9/site-packages/promptflow/evals/evaluate/_telemetry/__init__.py", line 111, in wrapper
    result = func(*args, **kwargs)
  File "/usr/local/miniconda/lib/python3.9/site-packages/promptflow/evals/evaluate/_evaluate.py", line 365, in evaluate
    raise e
  File "/usr/local/miniconda/lib/python3.9/site-packages/promptflow/evals/evaluate/_evaluate.py", line 340, in evaluate
    return _evaluate(
  File "/usr/local/miniconda/lib/python3.9/site-packages/promptflow/evals/evaluate/_evaluate.py", line 447, in _evaluate
    evaluator_info["result"] = batch_run_client.get_details(evaluator_info["run"], all_results=True)
  File "/usr/local/miniconda/lib/python3.9/site-packages/promptflow/evals/evaluate/_batch_run_client/proxy_client.py", line 33, in get_details
    run = proxy_run.run.result(timeout=BATCH_RUN_TIMEOUT)
  File "/usr/local/miniconda/lib/python3.9/concurrent/futures/_base.py", line 446, in result
    return self.__get_result()
  File "/usr/local/miniconda/lib/python3.9/concurrent/futures/_base.py", line 391, in __get_result
    raise self._exception
  File "/usr/local/miniconda/lib/python3.9/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/local/miniconda/lib/python3.9/site-packages/promptflow/_sdk/_pf_client.py", line 301, in run
    return self._run(
  File "/usr/local/miniconda/lib/python3.9/site-packages/promptflow/_sdk/_pf_client.py", line 226, in _run
    return self.runs.create_or_update(run=run, **kwargs)
  File "/usr/local/miniconda/lib/python3.9/site-packages/promptflow/_sdk/_telemetry/activity.py", line 265, in wrapper
    return f(self, *args, **kwargs)
  File "/usr/local/miniconda/lib/python3.9/site-packages/promptflow/_sdk/operations/_run_operations.py", line 137, in create_or_update
    self.stream(created_run)
  File "/usr/local/miniconda/lib/python3.9/site-packages/promptflow/_sdk/_telemetry/activity.py", line 265, in wrapper
    return f(self, *args, **kwargs)
  File "/usr/local/miniconda/lib/python3.9/site-packages/promptflow/_sdk/operations/_run_operations.py", line 228, in stream
    raise InvalidRunStatusError(error_message)
promptflow._sdk._errors.InvalidRunStatusError: First error message is: The input for batch run is incorrect. Input from key 'data' is an empty list, which means we cannot generate a single line input for the flow run. Please rectify the input and try again.

I noticed some changes related to performance/parallelization between 0.3.0 and 0.3.1. e.g. https://github.com/microsoft/promptflow/commit/32115d397b888be86eaea9b54039f5dd20f55dc0

for the evaluate API, i see it changed from

    use_thread_pool = kwargs.get("_use_thread_pool", True)
    batch_run_client = CodeClient() if use_thread_pool else pf_client

to
    use_pf_client = kwargs.get("_use_pf_client", True)
    batch_run_client = ProxyClient(pf_client) if use_pf_client else CodeClient()

so accordingly, the batch_run_client changed from a CodeClient to ProxyClient with default inputs (neither passing in _use_thread_pool nor _use_pf_client)

Is this related to the failure? and which client is parallelization and recommended to use?
How To Reproduce the bug
Steps to reproduce the behavior, how frequent can you experience the bug:
1.
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Running Information(please complete the following information):

Promptflow Package Version using pf -v: [e.g. 0.0.102309906]
Operating System: [e.g. Ubuntu 20.04, Windows 11]
Python Version using python --version: [e.g. python==3.10.12]

{
"promptflow": "1.13.0",
"promptflow-azure": "1.13.0",
"promptflow-core": "1.13.0",
"promptflow-devkit": "1.13.0",
"promptflow-evals": "0.3.1", or 0.3.0 as comparision
"promptflow-tracing": "1.13.0"
}
Additional context
Add any other context about the problem here.

Hi @ninghu , I think i was able to identify the root cause.
The issue was when the evaluate api gets called, the data path should be absolute path, not relative path w.r.t. working directory.
    _ = evaluate(
        evaluation_name=evaluation_name,
        data=data_path,
        target=custom_user_call,
        evaluators=evaluators_set,
        evaluator_config=evaluators_config,

        )

When using CodeClient, the dataframe read from data_path is used. When using ProxyClient, data (data path) is used for pfclient run.  However, this still puzzles me, because for target call, it is also a pf client run, with data to be relative path, it still works well. but it makes a difference when using ProxyClient.
Another observation is, if we use one evaluator (either built-in or customized), even with ProxyClient + relative path, it still worked.
But when using two evaluators, ProxyClient + relative path didn't work. We have to use absolute path.

These are great findings! The behavior you described is interesting and seems to occur only when using more than one evaluator. We'll try to reproduce this issue and get back to you.


universal-gcode-sender: Add version 2.0.7

Closes #5849

The archive contains both 32 and 64bit executables and I originally just created shortcuts for both and left both shims available
but I decided to make only the detected architecture available.
Not sure if it is okay or ugly stuff, so let me know if I should just stick to the former option.

What is the point of requesting review when you did not do anything about the major issue??

My apologies but I'm missing something here.

Is the problem that it's a nightly build?
If it's that, versions on the ugs repo are not labelled in any way.

If it's not, can you please clarify what you mean and I will fix it.

It is unacceptable that user is exposed to use nightly build without prior notice. When they do not provide stable builds it will not be added.

Fair enough.
Currently, the link to the latest version and the link to the nightly provide the exact same archive.
I'm gonna check if it's the same problem for their older versions and if it is, I will just close this PR.

Well, it is. Closing.


tomcat5: remove (EOL)

Motivation for this change
Please also backport to 16.09
"Fixes" #18336
The source for 5.0.27 is not available anymore. We could update to 5.0.30 (2004-11-24) or 5.5.36 (2012-10-09) but I don't think it's worth the effort.
Archive url: http://archive.apache.org/dist/tomcat/tomcat-5/
EOL announcement: https://tomcat.apache.org/tomcat-55-eol.html
Things done

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

[x] NixOS
[ ] OS X
[ ] Linux

[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

Alternatively, #18345 actually fixes it.

@chris-martin : https://tomcat.apache.org/security-5.html
If there really is a need for tomcat 5, we should update to 5.5.36 and take the 10 years worth of security updates. Please note: even that version hasn't been fixed in nearly 4 years.

The tomcat5 package doesn't even build, so I'm going to go ahead and agree with you, let's just ditch it.


platform compatibility with Windows

Hello, I'm quite interested in what you're developing here, it's been on my list as well—not nearly as robust as what could come from this.
My problem is I can't seem to get it running anywhere [for future readers, it does operate fine on MacOS]. Either following your help documentation, using the 'examples' (after updating them to match the documentation), the 'docs', or using the nuxtent-starter quick-start (vue-cli init ..., npm install, then npm run dev).
I'm mainly focusing on the dev server, but also cannot get it running under build then start.
I cannot navigate between pages on either Linux or Windows, however on Linux if I get the SSR page directly it will load. There appears to be no error messages outputted.
Do you have a working example that I can tease out or perhaps there's something I'm missing?
[Note to future readers: both Linux and MacOS will work, as things are currently coded (17-07-21) you must load the dev server from localhost:3000 to avoid CORS errors as the content-api is loaded from local host, not <IP_ADDRESS>]

Weird... I JUST updated the documentation and examples. How recently did you test it?

If the problem is the navigation then you might be using the wrong baseURL.
Make sure you set this appropriately:
module.exports = {
  api: {
    baseURL: (isProd) => isProd ? 'http://localhost:3000' : 'http://localhost:3000'
  }
}

You can also go to the endpoint using the 'http://localhost:3000'/content-api/' path, it should show you JSON of appropriate content data.
For example:
If you're using 'content/posts' registered directory then  'http://localhost:3000'/content-api/posts' should show you all posts data.

15 minutes ago. I see you updated the examples, just pulled down the new examples and tried a run on the markdown-components and multiple-content-types. On Windows, MacOS & Linux I initially get:

[nuxt] Module [@nuxtjs/axios,[object Object]] should export a function

I can correct this by replacing the pinned nuxt version with latest, but results in still having the navigation problem. SSR still works on Linux, not on windows.
Testing it on a MacOS machine, it works perfectly (aside from the Nuxt version problem). It looks like there could be a platform issue?

The content-api loads fine on all platforms.

Yeah, I've unfortunately only had the chance to test it on Mac.
So to be clear: with updated examples:

It works on Linux.
On Windows SSR doesn't work, but you still see the data when you go to the appropriate content-api endpoint.

Is there really no error messages - either in the inspector or in the terminal?

With updated examples,

Linux only provides SSR pages, hydration (is that the correct term?) does not work; you must type / manually navigate to the page url
On windows both SSR and navigation does not work.
On both Linux and Windows the content-api appears functional.

On Linux, the JS console spits out the following on navigation:
(index):1 XMLHttpRequest cannot load http://localhost:3000/content-api/hello-world. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://<IP_ADDRESS>:3000' is therefore not allowed access.
createError.js:16

Uncaught (in promise) Error: Network Error
    at createError (createError.js:16)
    at XMLHttpRequest.handleError (xhr.js:87)

There are no console errors on SSR load, and just a 404 in windows

Well, that last error on Linux is avoidable with CORS setup.
So at least there's that found out. I'm not sure why MacOS doesn't have the same problem...

Good to know that at least something works 😅
Ok, so let's narrow this down:
Hydration issue I'm aware of. If you're referring to incorrect HTML markup error. I opened up seperate issue for that. Problem seems to be with JSX rendering HTML because if you use v-html directive, the error goes away. But ideally, I need JSX so that users can just use nuxtent-body for both markdown HTML and components. So let's just say that Linux "works".
The problem is that SRR and client side routing don't work... It seems to be a problem with axios request (maybe a @nuxtjs/axios module problem?), since you can navigate to content-api endpoint without a problem.

Unfortunately, I don't have a windows computer to test this out -- can you try fetching from that same endpoint on your own (without the app.$content helper) and see if that works?

On windows it returns a 404 when manually entering the page, perhaps it's encountering a problem even before rendering?
I wish I understood more about Nuxt's routing—and how it interfaces with Nuxtent... still working on that myself.

Further hammering:
The user is presented a <IP_ADDRESS> url from webpack's dev server to load in the browser. The content-api is being loaded from localhost; this results in CORS problems, and stops navigation. This is valid for box MacOS an Linux. I was loading manually from localhost when testing MacOS.
This can be solved by either always using <IP_ADDRESS> or localhost throughout -> I'm not sure how to get webpack to show localhost instead of <IP_ADDRESS> when it loads up the dev server.

This doesn't solve the windows problem. There are problems with both SSR and navigation, with either <IP_ADDRESS> and localhost.

Yea, Nuxtent sends a 404 is sent if the content-api endpoint doesn't exist, which would happen with different base URLs. (see https://github.com/nuxt-community/nuxtent/blob/master/lib/core/api.js#L32)
We probably just need to configure axios appropriately to solve the CORS problem. (see https://github.com/nuxt-community/nuxtent/blob/master/lib/module.js#L100)
Right now I'm only providing a server and browser API endpoint, not handling CORS problems.

From axios module readme:
If browserBaseURL is not provided it defaults to baseURL value.
If hostname & port of browserbaseURL are equal to nuxt server, it defaults to relative part of baseURL. So if your nuxt application is being accessed under a different domain, requests go to same origin and prevents Cross-Origin problems.

Which is weird since both of them should point to same  host and port... only thing being changed is prefix.

I think a solution for the CORS issue is to use <IP_ADDRESS> as the final host option instead of localhost ( https://github.com/nuxt-community/nuxtent/blob/master/lib/module.js#L9 ). That way everything lines up as expected if you don't have process.env.HOST set.
Still trying to figure out the windows glitch.

But the axios module uses the same fallback https://github.com/nuxt-community/modules/blob/master/modules/axios/index.js#L7. Have you checked if using the module works for you? It might not be specific to Nuxtent.

Have you checked out the env property for Nuxt? https://nuxtjs.org/api/configuration-env/#the-env-property.
Also the fallback wouldn't matter because you can pass your own custom option that overrides it (see: https://github.com/nuxt-community/nuxtent/blob/master/lib/module.js#L33)
e.g.
module.exports = {
  api: {
    baseURL: (isProd) => isProd ? 'http://<IP_ADDRESS>:3000' : 'http://<IP_ADDRESS>:3000'
  }
}

Yep, it helps the CORS issue, but the defaults still present localhost as the content api endpoint and <IP_ADDRESS> as the webpack dev server location.
Also setting a HOST or PORT environment variable does this too.

Ah okay but that's not a problem with Nuxtent. All Nuxtent does is hook up to the existing serverMiddleware and use axios module to request that endpoint.
I'd open up the issue in the nuxt.js, or @nuxtjs/axios module repo and perhaps @pi0 will have a better answer.

I'm going to close this issue, because, as described above, there doesn't seem to be much I can do on the Nuxtent end to resolve it.
Feel free to open it back up or open up a new one if I'm mistaken.

Well... I'm not sure if that's it. Sure it could be that the CORS problem is solvable upstream, but the windows issue is separate: there's two issues discussed in this post, 1) the cors problem, 2) the windows compatibility issue, unfortunately I haven't had more time to dig into that—or if the windows issue is also due to upstream. You're probably right, but I just can't see it yet. I'll have to give the axios module a try on it's own.

Yeah, that's what I was going to recommend - give axios module a try by itself and get back to me.

I have this issue with Nuxtent as well. It seems everyone on my team using Mac/Linux have no issues, but because I'm on a Windows machine, somehow things fail? With nuxtent removed, the app is fine, so there's definitely something going on here.


Update README.md

Edited shortest payload from script to embed

embed is considered an external resource to be embedded into the current context, its not the same as script


Allow skipping creating tags?

It would be nice to be able to skip creating tags for specific projects.
The use case I would currently like is to skip creating tags for packages in our /libs directory while still creating them for /apps.

Hi @NullDivision, by design semver is tag-based, which means it uses tags to define the current version so it doesn't make sense to add an option to skip tagging, it would break version calculation. Note that there's already an open PR about that (https://github.com/jscutlery/semver/pull/687) but I would not merge it until we choose to support other strategies to get the current version. For now, it's not a priority.

+1 for this. It would be nice to at least support that option for more advanced cases.
The problem with creating tags after versioning each given individual package, is that they are blocking the git process.
In my use case, the difference between versioning in a single process and in 5 different processes is quite dramatic, as I use semver to version an nx monorepo with around 200 independent packages. I'm pushing (and squashing) manually after the main process finishes.
And right now the tags are the only reason why I cannot scale up the parallel tasks.


(BROKEN) Added a SWIFT Sample - RBQFetchedResultsControllerSwiftExample

Hi Adam,
Sorry i mis-read your post today.   This pull request adds a 2nd example, which might serve 2 purposes:

Eventually act as a example of how to use RBQFetchedResultsController with Swift (though not yet because it doesn't work :)
As I mentioned, it appears that RBQFetchedResultsController isn't returning any records.  If you have any interest/time in debugging, this might act as a starting point.

If you'd prefer to that I debug, that's fine as well - any suggestions on where to look/get started would be appreciated.
Note that, In addition, I needed to make the following modifications to the #imports
in the following files in the RBQFetchedResultsControllerSwiftExample
pod:
FILE                                 OLD Value
NEW value
RBQSafeRealmObject.h  #import "RLMProperty.h"   #import
<Realm/RLMProperty.h>
RLMObject+Notifications.h #import "RLMObject.h"  #import
<Realm/RLMObject.h>
RLMRealm+Notifications.h  #import "RLMRealm.h"  #import
<Realm/RLMRealm.h>
RLMObject+SafeObject.h  #import "RLMObject.h"   #import
<Realm/RLMObject.h>
RLMObject+Utilities.h        #import "RLMObject.h"   #import
<Realm/RLMObject.h>

Ok well the issue is that Swift Classes are identified with a different string than Obj-C classes. So the logic is broken because the FRC represents the original RLMObject in its cache by storing the NSString of the Class name. It then reproduces the object by calling the function NSClassFromString() to get the Class to call the RLMObject class method to retrieve the object by primary key.
So the problem is that the class name it is storing is "TestObject" versus "RBQFetchedResultsControllerSwiftExample.TestObject"
I recalled noticing this when reviewing Realm's code because they have two methods to identify and clean up Swift classes in RLMSwiftSupport
So I will need to rework the logic to handle this issue since it touches the RBQFetchRequest and RBQFRC.

Thanks Adam!

One thing I noticed is line 87 in ExampleTableViewController.swift should not have "let" but rather just be:
fetchedResultsController = RBQFetchedResultsController(fetchRequest: fetchRequest, sectionNameKeyPath: "sectionName", cacheName: "testCache")

I added a class method in RBQFetchRequest to pass in the Class and derive the entity name from that, and also adjusted the FRC to use the entity name from it's fetch request, and now the tableview shows all the rows. However, not sure if I like this approach. Wondering if there is a cleaner way. Will continue to play with it...

Line 87
Good catch.

I added a class method...
Awesome!  Could you post what you added?

Ok, have a better way to fix this so that it hides the complexity from the developer.
in RBQFetchRequest you can add the follow class method:
+ (NSString *)verifyEntityName:(NSString *)entityName
{
    Class objcClass = NSClassFromString(entityName);

    if (objcClass) {
        return entityName;
    }

    NSString *appName = [[NSBundle mainBundle] objectForInfoDictionaryKey:@"CFBundleName"];

    NSString *swiftClassName = [NSString stringWithFormat:@"%@.%@",appName,entityName];

    return swiftClassName;
}

then in the two other constructor class methods, just add the call:
entityName = [RBQFetchRequest verifyEntityName:entityName];

RBQFetchRequest *fetchRequest = [[RBQFetchRequest alloc] initWithEntityName:entityName
                                                                        inRealm:realm];

Finally, replace the class method classNameForObject: in RLMObject+Utilities category with this:
+ (NSString *)classNameForObject:(RLMObject *)object
{
    // Returns the class name in code (i.e. "TestObject" not "RLMAccessor_V0_TestObject")
    NSString *className = [[object class] className];

    Class objectClass = NSClassFromString(className);

    // If we have Obj-C class return the name
    if (objectClass) {
        return className;
    }

    NSString *appName = [[NSBundle mainBundle] objectForInfoDictionaryKey:@"CFBundleName"];

    NSString *swiftClassName = [NSString stringWithFormat:@"%@.%@",appName,className];

    return swiftClassName;
}

Ok this issue should be fixed in v1.7.4: https://github.com/Roobiq/RBQFetchedResultsController/releases

Awesome thanks!
Unfortunately, I can't quite get it to work.  2 things:

Had to re-do the #imports to get it to compile (using Cocoapods):

FILE                                       OLD Value                            NEW value
RBQSafeRealmObject.h    #import "RLMProperty.h"  --> #import <Realm/RLMProperty.h>
RLMObject+Notifications.h #import "RLMObject.h"    --> #import <Realm/RLMObject.h>
RLMRealm+Notifications.h #import "RLMRealm.h"    --> #import <Realm/RLMRealm.h>
RLMObject+SafeObject.h   #import "RLMObject.h"    --> #import <Realm/RLMObject.h>
RLMObject+Utilities.h          #import "RLMObject.h"   --> #import <Realm/RLMObject.h>

Although the section names now have data in the tableview headers, the cells are still blank.  In RBQObjectCacheObject.m in [RBQObjectCacheObject objectInRealm:realm forCacheObject:cacheObject], for some reason, it looks as though realClass ends up nil when running the Swift version, but the Objective-C version gets "(Class) TestObject"

I don't understand the import changes you mentioned?

Sorry, it seems to be cutting off 1/3 of the lines
FILE                                       OLD Value
NEW value
RBQSafeRealmObject.h    #import "RLMProperty.h"   --> #import <Realm/RLMProperty.h>
RLMObject+Notifications.h #import "RLMObject.h"     --> #import <Realm/RLMObject.h>
RLMRealm+Notifications.h #import "RLMRealm.h"     --> #import <Realm/RLMRealm.h>
RLMObject+SafeObject.h   #import "RLMObject.h"     --> #import <Realm/RLMObject.h>
RLMObject+Utilities.h         #import "RLMObject.h"     --> #import <Realm/RLMObject.h>

Hmm all of that has been fixed. I think there is an issue with Cocoapods and submodules. The changes are not being reflected when installed through that. All of this was fixed.

Ok just updated the podspec to v1.7.5 and tried the install. It now is installing the proper submodule commits.... so give it a try.

Terrific - that did it!

Excellent, not sure why the submidules were off. Let me know if you run into any other issues.


Correcting a bug in the replace links functionality

The replace links functionality currently replaces all internal links with a link to the current document, not the target document. This PR corrects that.

I have turned the original script into a plugin, and this issue is resolved. The plugin is awaiting submission to the community store, but you can install with BRAT if you want to use it now. I would appreciate the testing.
The most significant change with the plugin is that the data is now encrypted at rest on the server - so you can share anything and the server is never able to read it.

I have turned the original script into a plugin, and this issue is resolved. The plugin is awaiting submission to the community store, but you can install with BRAT if you want to use it now. I would appreciate the testing.
The most significant change with the plugin is that the data is now encrypted at rest on the server - so you can share anything and the server is never able to read it.


CDATA in description not parsed as desired

Hi Team,
Thanks for building this open-source tool. I'm new to dealing with RSS feeds and wanted an easy way to parse the data into typed objects. I'm having an issue with one feed where they have embedded A LOT Of CDATA in the description, with a lot of HTML with styles and links to images, etc..
Here is an example:
(NOTE: some of this is being hidden by the browser; open this issue in Edit view to see all the data might work. If there is a way to prevent it from rendering as HTML in this Issue, I don't know how.)
`<![CDATA[The German Supply Chain Due Diligence Act goes into effect January 2023 and is already making waves within supply chain, risk management, and compliance communities. […]
The post Meeting the Obligations of the German Supply Chain Due Diligence Act: FAQs appeared first on Aravo.
]]>`
Options: { descriptionMaxLen: 20000,       xmlParserOptions: {       // I've tried a bunch. . . nothing "worked"}     }
Output:
description :  "The German Supply Chain Due Diligence Act goes into effect January 2023 and is already making waves within supply chain, risk management, and compliance communities. […] The post Meeting the Obligations of the German Supply Chain Due Diligence Act: FAQs appeared first on Aravo." link :  "https://aravo.com/blog/meeting-the-obligations-of-the-german-supply-chain-due-diligence-act-faqs/" published :  "2022-12-01T14:33:07.000Z" title :  "Meeting the Obligations of the German Supply Chain Due Diligence Act: FAQs"
Desired output: All contents of the description CDATA
Questions:

Is this something that can be supported?
How unusual (to you) is this use of the description field (all CDATA of HTML)?

@CoryKniefel could you share link to that feed source so I can investigate its content structure? (I can not access someorg.org)

@CoryKniefel could you share link to that feed source so I can investigate its content structure? (I can not access someorg.org)

I emailed you at the link. Please let me know if you didn't receive.

@CoryKniefel I received. Maybe I can detect the problem there.

@CoryKniefel you can use getExtraEntryFields. This is a function that allows you to customize the output, add or modify any part of feed data.
Please try this and let's me know if the result matches your expectation:
import { read } from '@extractus/feed-extractor'

const YOUR_FEED_URL = 'https://a...'

await read(YOUR_FEED_URL, {
  getExtraEntryFields: (feedEntry) => {
      const { description: content } = feedEntry
      return {
        content,
      }
    }
})

Yes, matches expectations perfectly. Thanks for showing me how that works.


Bug: New properties and Linter (with 12-hour datetime format) not working together well.

[X] I have verified that I am on the latest version of the Linter

Describe the Bug
New properties feature doesn't seem to work well with auto “created” and “modified” datetime in 12-hour format. Sometimes works with 24 format. Always works for regular dates.
How to Reproduce
Steps to reproduce the behavior:

Go to 'Linter Settings'
Got to 'YAML'
Scroll down to 'YAML Timestamp' > 'Format'
Use 'MM/DD/YYYY hh:mm A' for 12-hour format
Properties will stay empty

Expected Behavior
For proper datetime format to be returned in 12-hour format in new properties.
Device

[X] Desktop
[X] Mobile

This is an interesting potential issue. I will habe to take a look at this at some point. I know that we had an issue similar to this in the past, but it was due to the system time and desired display formats being different
Hopefully I will be able to take a stab at this shortly.

No prob at all. Please let me know if you need me to test anything on my end.

@everonegraham , I see you mentioned a new properties feature. Do you mind explaining what that means? You probably should not use YAML Timestamp keys with Insert YAML Keys

Hi @pjkaufman, referring to this new feature:

https://twitter.com/obsdmd/status/1684275039703814145
https://obsidian.md/changelog/2023-07-26-desktop-v1.4.0

It does seem to work with date format though. Just not sure what the issue with datetime.

That may be something specific to the insider options. I am not sure I can do anything around that. However I can see if there is an issue with the logic around YAML Timestamp for the date format specified. If the issue is specific to an insider build, I will have to wait to address this until it is available as part of the non-insider release.

I am not sure how properties are stored, so I can only speculate as to what may be going on.

Based on what I am seeing here, this new feature is something that deals with the YAML Frontmatter, so the issue may not be related to the new properties option except in that it causes values not to populate visually. So this may be fixable/reproducible.

I am not seeing a problem with the YAML. If you could provide your data.json that would help me confirm whether the problem is with my attempts to reproduce whether it is a problem with a newer version of Obsidian.

Hi @pjkaufman, data.json is in that zip file. Sorry, I forgot to mention that it is currently an insider feature. :(
data.zip

Sorry, wrong button.

I found a format that works for me: YYYY-MM-DDThh:mm A
If I try anything else, it returns as a string.

I am glad that you have found at least a partial workaround. I need to double check with the data.json you provided above to see if I can reproduce this scenario. I am not sure if I can. I thought I had tested it and still could not see the problem, but lacking a comment from me, I assume I must have not actually done the check.

It's defaulting to AM for some reason. Probably an issue on my end.

I know that when this happened before it was because the system clock and the time format desired did not match the mode. Are you sure your system is also set to 12 hour mode?
For example, if the system is set to 24 hour mode and the date format that is specified to be 12 hour mode, it might not parse the file metadata correctly and just assume it is always the AM. It has happened before, but I thought it was fixed.

It should be in 12 hour mode. See attached image below. Very unclear what the issue is to me. But it could be a bug with the properties feature?

@everonegraham , could you provide a screenshot of both the properties view of the YAML frontmatter and the actual value in frontmatter (i.e. the source view of the YAML frontmatter)? I can only assume it is mutating the value instead of leaving it as is.

Hi @pjkaufman,

It seems to be going through correctly.

@everonegraham , is it not showing properly in the properties UI?

That's the strange part. It does, but it defaults to AM even if it gets edited during PM* . I have a feeling that I have to get the formatting just right for it to take it.
Or maybe it's that properties is still being a bit wonky.

@pjkaufman, I figured it out. YYYY-MM-DDTHH:mm works. Properties auto-interprets AM/PM. So leaving it in 24-hour format in Linter YAML settings is the way to go.
Will close this out.
Thanks for all the help on this. :D

Gotcha. I am glad that you found a solution.


Attention Visualisation

The diagrams present for attention visualisation don't show the network has learned very well. For eg : in the first figure, the output word "she" has the most attention to the input word "cinq", which is not correct. And in general, the learning seems to be very bad based on the attention visualisations. On the other hand, the training graph shows that the loss is very low (around 0.6); so the network must have learnt well.
I am confused by these conflicting understanding. Could you please help explain it.

The RNN is gradually building up its state, not just based on the current word, so as it gets further in the sentence it may become "more sure" about the context of previous words. That's why you sometimes see this shift. In some cases you will see the final EOS token being overly focused on because that final state encodes all the information in the sentence (as in seq2seq without attention).
Plus, the examples shown were only trained for around 40 minutes with a limited dataset, so the results are not great. With a small training set the network sometimes learns weird patterns that don't seem to line up at all, because it doesn't have to rely on alignment. Longer training time, more data, and a bidirectional encoder (coming soon) will improve results.
The bidirectional encoder especially helps because the forward and backward RNN states are combined to incorporate info from both directions. This makes the position of the attention more interpretable: