Develop a Laika CLI for Node.js and Native

This issue is spun out of https://github.com/planet42/Laika/issues/281#issue-1220788257.

Postpone support for Scala.js in laika-io
This option has been mentioned in the original request. It is, however, beyond the scope of the 0.19 roadmap. Any future consideration would require that someone opens a ticket for this and is able to generate significant interest in the community for having this module on Scala.js.

The goals of this issue are to propose the broader idea, evaluate if it is even within Laika's scope, and see if there is community interest.
Proposal
The idea is really two separate but (IMO) related things.

cross-publish laika-io for Scala.js (targeting Node.js) and Scala Native
create a CLI application

The motivation for a CLI is so that Laika can be used as a standalone site generator à la Jekyll. @valencik and I recently discussed this in context of the typelevel.org website. I'm not entirely sure if this is possible, since I've really only used it via sbt: specifically, if there is enough configuration flexibility via HOCON/templates, without resorting to Scala code.
Assuming a CLI is a feasible and attractive feature, then cross-building laika-io to Scala.js and Native becomes very interesting.

Scala Native CLI would be a self-contained lightweight binary with instant startup (vs a JVM application)
A Scala.js CLI published to NPM would be extremely easy to install and run from virtually everywhere

If publishing a CLI application is out-of-scope for Laika, then I think cross-building laika-io for JS/Native is less valuable. The core is already cross-published for JS (and maybe Native someday) which, if desired, can be used directly with fs2-io without going through laika-io.

Many thanks for authoring this proposal. While I generally think this presents an interesting and exciting opportunity, I also have quite a number of doubts, and they are less about the feasibility of this effort (I really cannot judge feasibility of anything related to Scala Native), but more about a) the scope of work that I would see as mandatory to make this an attractive offering for which I'll try to provide some context below and b) the fact that a CLI application is not a frequently requested feature at the moment.
Since this comment turned out to become rather long, I've split it into three main section that address A) the target audience you intend to reach with the proposal, B) the scope of work I'd see as necessary to produce an attractive offering and C) the question of development and maintenance, specifically in the context of the other work happening in the coming months.
Target Audience
The proposal so far discusses the question whether it is feasible and what advantages CLI applications would have (I think they are pretty obvious), but an even more critical question for me is: who would actually benefit, and how many? And by that expand the question "is it feasible" to "is it worth the effort"? I personally expect the effort to be high, and I'll explain why in the next section below about scope. Regarding the target audience I see primarily two variants, which each come with their own downsides.
The first option would be to still mostly target the Scala community. I don't feel like this would be attractive though. This would mean we target a subset of an audience that is already not that large to begin with. Usage, feedback and participation have somewhat increased since the 0.18 release and the Typelevel adoption, but given that Laika has a fairly unique position as one of very few pure-JVM options, I still feel it's not as high as it could be. And within the user base there is a clear dominance of JVM users vs. Scala.js users and within the former a clear dominance of plugin usage. I'll give some Sonatype download statistics for November as an example, it's for 0.18.2 and 0.19.0 combined to ignore aspects like migration speed: it's around 11,000 for the plugin, around just 150 for laika-core_2.13 for the JVM and around just 10 (!!!) for laika-core_2.13 for Scala.js. I don't have meaningful numbers for Scala 3 as the statistics seem to be distorted by some 3rd party integration I am not aware of. The numbers are unusually high and almost identical for JVM and Scala.js which is very unlikely to reflect real usage. And the numbers for Scala 2.12 are distorted by the plugin usage. With those numbers I am currently very reluctant to even think about increasing the maintenance burden by supporting Scala.js in additional modules. Native is a different story, but even here we can see that within the existing user community there is no significant number of requests for such functionality at the moment.
This leaves us with the second option, which is to target a wider audience and not just the Scala community. Existing usage patterns and download statistics are less relevant for this discussion as we would seek to attract a completely new group of users. This feels generally more attractive to me, but has its own downsides: We would enter a large and crowded arena, with tools like Jekyll, Hugo, Docusaurus and many more. All of which have a much larger user base, larger number of maintainers and 3rd party extensions and in some cases also a larger feature set. We would need to really think about how and where we would announce and market such a solution and what the selling points would be that could potentially tempt users to switch. When I started with Laika I was very well aware of the crowded nature of this arena and deliberately chose not to compete in it. If others feel like it is worth it, I am happy to chime in and contribute, but I currently do not consider to lead such an effort (more on that under Development & Maintenance).
Scope
The second important discussion is the scope of the work. An option that would be very unattractive in my view is to simply support all functionality we get mostly for free simply by adding those new target platforms and a bit of bootstrap logic for the CLI app itself while stripping off all modules that don't work on Native out of the box. The huge downsides with that would be twofold: the documentation which already needs to distinguish between library API and sbt plugin would receive further fragmentation by many features not being supported on Native or Node or in a very different way. Secondly competing with any comparable tool becomes even harder when we only offer a small subset of functionality. I would want to avoid increasing the maintenance burden by cross publishing when we realistically would only reach a small audience.
For this reason I feel like it's appropriate to hijack this proposal a bit for a wider discussion of the Laika road map and I hope you don't mind the wall of text that will follow. In my view aiming for feature parity with what the sbt plugin offers plus filling functional gaps compared to competiting native apps in this space would be the only viable approach. Which turns this idea into a fairly ambitious endeavor. I would actually love to change the title of this proposal from "Publish..." to "Develop..." if you guys don't mind as that would more accurately reflect the scope of the work.  I haven't thought about every module and feature in detail, but I'll list a few things that spontaneously come to mind just as an example for the challenge that would lie ahead.
Helium Configuration
In contrast to the configuration in Laika Core which supports both, HOCON and programmatic configuration for (I think) all features out of the box, that is currently not the case for Helium. I think it is feasible to add that support, but it's a non-trivial size of work. The DX of the syntax for this vast set of options would need to be carefully considered and HOCON decoders would need to be written (which is a lot of boilerplate as Laika does not support macros like some JSON libraries do - this might change when everyone is on Scala 3, but until I'd prefer not to implement those twice for Scala 2 and 3)
PDF Support
As you might be aware, PDF support in Laika is based on the Apache FOP project which in turn is based on the XSL-FO format which appears to be a legacy format right now. I would have preferred to avoid the format, but there are no comparable libraries for the JVM and not requiring any external tools was a primary goal from the beginning. Apache FOP will never work on Scala.js nor Scala Native, so PDF support would need to be re-implemented from scratch based on toolling available for the relevant platforms. One option would be to add a LaTeX renderer to Laika (a non-trivial effort on its own) and then rely on all the existing tooling around that format (the result would probably look even better than what Apache FOP produces). Another option would be to use HTML as the interim format, but that could not simply use Laika's existing renderer as it would need to deal with features only supported for PDF (manual page breaks, footnotes, configurable bookmarks and typographic controls like preventing headlines on the bottom of the page) and I am not sure whether PDF tooling accepting HTML as input format would support all these. You might feel tempted to say: let's skip PDF support then, but that brings the other downsides listed above: an inconsistent feature set and offering less than competitors.
EPUB Support
This might be significantly easier than PDF support, but I ultimately don't know. The big advantage here is that everything non-portable is concentrated in a single Laika class that depends on the JDKs ZipOutputStream (EPUB is essentially ZIP plus XML metadata). Whatever alternative we would be using needs to support a way to specify the compression per file (EPUB requires the first file to be written uncompressed).
Extensibility
To my knowledge, most alternatives in this space support a way of installing 3rd-party extensions. On top of that, the large set of extension points of Laika is an aspect that distinguishes Laika from some other solutions, so the idea of producing a CLI app that closes this door feels like stripping off a large portion of what makes Laika attractive. To achieve feature parity with the JVM version and enable community plugins, there would need to be a way to compile and load extensions. The downside, apart from the associated complexity is that the language would be Scala. When trying to target communities outside of Scala, this might be a showstopper for some. If a CLI application would see any signifant adoption at all, I can already sense that some might start requesting Java APIs. But given that most extension points center around writing partial functions for AST nodes which are case classes, I'm not sure this could be added in any elegant way.
HOCON
This is another piece in the puzzle where we offer something alien when targeting developers beyond Scala. I'm fairly sure that at some point people would ask for YAML support and that would be very difficult to integrate in Laika. Wrapping a YAML parser is the easy step, but we would need to translate the internal format of the result to Laika's internal HOCON format to preserve the hierarchical nature of Laika's configuration with its cross-reference support. YAML is also not a good fit for some use cases like directive attributes (a format with significant whitespace does not work well in an inline scenario).
CommonMark
Another gap to competitors that most users and contributors are probably not aware of is that Laika still builds on the original, classic Markdown definition. But today, in most cases where people talk about Markdown they actually mean CommonMark. To provide some context for those who did not follow these developments, the CommonMark spec was a joint effort to add detail to many of the vague or incomplete syntax descriptions of the original Markdown definition as well as a comprehensive test suite. Unfortunately the original author of Markdown did not agree to the name Markdown being used, hence the new name CommonMark. But in practice everyone still calls this Markdown. For Laika the plan is to integrate the CommonMark test suite of 600+ tests to match what other tools offer by now. Most users won't notice the difference, as using Markdown with GitHubFlavor today will get you very close to what is now called CommonMark and the tests which will be red will most likeley center around more esoteric edge cases. But I still feel this is an area where catching up to comparable toolkits is necessary and the work for this is currently scheduled for the 1.1 time frame.
Syntax Highlighting
This is another area where some catch up would be required when targeting a wider audience. Laika's built-in highlighter still lacks support for some of the major languages like C++, C#, Ruby, Rust, Go. Options here would be, a) adding those highlighters to the integrated support, which is the ideal solution as it makes the syntax available as AST nodes and thus opens it for customizations and makes it work for all output formats, b) offer some JavaScript solution out of the box, which would have the downside of not working for PDF or C) integrate with some native solution for which I have not done any research yet.
Search
This really hasn't been on my radar so far, and it's also not getting requested frequently, but many alternative solution have some support for searching. This is relevant for HTML output only, as EPUB and PDF come with search functionality in the respective readers. I did some brief research a few years ago, but did not find any attractive solution. Most JavaScript seach engines I could find where either very limited in functionality or no longer actively maintained or, in most cases, both.
Parallel Execution
The transformation time for Laika benefits from the fact that there is only a very brief bottleneck in the middle of the transformation where the AST processing happens in a single thread (to resolve cross-references, produce tables of contents, etc.), the first and last phases of the process (parsing and rendering together with I/O) happen for all documents in parallel. I don't know whether parallel execution can be kept for Node or Native, but if not I could imagine that sequential execution might result in performance that does not match that of other native tools.
Development & Maintenance
The third and final topic I'd like to discuss is how such a solution would be developed and maintained. I hope that I could convince you with my thoughts above that providing some sort of minimal POC would most likely just increase the maintenance burden for little gain and probably little adoption in the community. But if we agree to aim a bit higher the next question is who would be doing this work and when.
At this point in time I personally have no capacity myself to increase the scope of the work I do with Laika. The coming months my focus will be the 1.0 milestone series and a bit of 0.19 maintenance. For 1.0 my sole focus is improving binary compatibility. There will be a series of PRs for each package focusing around two areas: reducing the surface of the public API which is currently way too large and replacing all case classes by other constructs (apart from those forming the AST which can stay for a number of reasons).
But even if others step in and do all work without the need for me to contribute or review (I'm currently unable to even review PRs for Scala Native as my knowledge about it is exactly zero) I'd still be concerned that the work would be disruptive as it would mean we would have two parallel streams of work that would both need to move stuff around and also make merging 0.19 fixes up a bit harder. Most of the time Laika does not have maintenance branches, but in the coming months this will unfortunately be different.
Given all these constraints and the fact that at this point in time we don't know how much interest in the community we can generate for this effort and that the amount of work is significant for producing a viable product, I'm somewhat sceptical about the idea at least for the coming months. But this view could change in the future if several criteria around the Laika project and this proposal change over time:

increased adoption and participation
one or more additional admin-level maintainers who can merge PRs and cut releases
a really significant number of requests for a CLI application coming from the community
a shared vision for such an application (mine is primarily achieving feature parity, otherwise I'm quite open-minded)
someone other than me stepping up to lead such an effort with me acting merely as contributor and reviewer
filling functional gaps to competitors before increasing the maintenance burden by cross-publishing
ideally not starting to cross-publish during the 1.0 milestone series when there is a maintenance branch (probably active for 12-18 months)

Finally, while the proposal addresses both, Native and Node, I think the criteria for committing to this effort have to be met for both individually, and doing one of them should not automatically imply doing the other.
I'm happy to keep this open for a long time, to allow for further discussion, collecting ideas, and as a place where users can provide feedback. So if anyone has interest in a CLI application or would like to contribe to the development, please chime in and describe your use case. What would you do with it and why would you prefer it over any of the other native or Node.js toolkits which are available today?

Firstly, thank you for taking the time to consider this and write such a detailed response ❤ besides the specific points of this proposal, it is really great to get insight into where things are, and where things are headed.
Overall, I agree with your analysis above, both on the audience and effort required (and changed "publish" to "develop" :)
I'm going to read through a second time and respond to a few points below.

The big advantage here is that everything non-portable is concentrated in a single Laika class that depends on the JDKs ZipOutputStream (EPUB is essentially ZIP plus XML metadata)

Ideally this would lean on fs2.compression which already cross-compiles on JVM/JS/Native. Unfortunately fs2.compression currently only supports Gzip and Inflate/Deflate, but adding Zip would be a good (and requested) feature anyway.

Search This really hasn't been on my radar so far, and it's also not getting requested frequently, but many alternative solution have some support for searching.

Well, we are getting plenty of requests downstream, for searchable project documentation :) @valencik is currently exploring this arena.

I don't know whether parallel execution can be kept for Node or Native, but if not I could imagine that sequential execution might result in performance that does not match that of other native tools.

Parallel execution can definitely be kept on all platforms. Applications/libraries using Cats Effect etc. combinators for concurrency and parallelism Just Work:tm: with identical semantics.
On Node.js, I/O tasks can run in parallel, but there is only one thread for compute tasks.
Scala Native 0.4 is currently single-threaded, but the 0.5 series in development already supports multi-threading. This is expected to land sometime in the next few months-ish. Suffice to say, it will match the JVM on all counts.

But even if others step in and do all work without the need for me to contribute or review (I'm currently unable to even review PRs for Scala Native as my knowledge about it is exactly zero)

I'm always happy to review platform- and build-related PRs. I know it doesn't really address the issue you raise here, just saying :)

one or more additional admin-level maintainers who can merge PRs and cut releases

Along these lines, I'd love to see Laika become a Typelevel-org project, if this is something that interests you. This would secure multiple admins, who can maintain (or delegate).

ideally not starting to cross-publish during the 1.0 milestone series when there is a maintenance branch

In my experience cross-building libraries, it is generally much better to figure out the cross-building before 1.0 and compatibility constraints kick in, since dealing with (even subtle) platform differences becomes a lot more painful. In fact, knowing that you are working towards 1.0 was one of my motivations for opening this discussion now, before it was too late :)
The intent is not to invalidate your point but better illustrate the interactions of constraints. Basically, establishing an API with long-term binary-compatibility is somewhat coupled to cross-platforming, so if both are goals they should not be done separately.

Thank you for providing all these pointers. I'll comment on two of them here.

one or more additional admin-level maintainers who can merge PRs and cut releases

Along these lines, I'd love to see Laika become a Typelevel-org project, if this is something that interests you. This would secure multiple admins, who can maintain (or delegate).

Happy to discuss this if there is interest. I just have no idea what this means in practical terms, so someone would need to brief me a bit on this... 🙂

ideally not starting to cross-publish during the 1.0 milestone series when there is a maintenance branch

In my experience cross-building libraries, it is generally much better to figure out the cross-building before 1.0 and compatibility constraints kick in, since dealing with (even subtle) platform differences becomes a lot more painful. In fact, knowing that you are working towards 1.0 was one of my motivations for opening this discussion now, before it was too late :)
The intent is not to invalidate your point but better illustrate the interactions of constraints. Basically, establishing an API with long-term binary-compatibility is somewhat coupled to cross-platforming, so if both are goals they should not be done separately.

I think I kind of understand this. This point was more around the fact that I would prefer not to commit to cross-publishing at all before all the other criteria are met. This means definitely not in the early milestone phases. If the situation changes in an unexpectedly swift way and we are half-way through the milestones, we can still start cross-publishing at that point. If this lies dormant until after the 1.0 release and suddenly there is an unexpected explosion of interest and contributors chiming in and we discover we need to break bin-compat for cross-publishing, well, I'm pragmatic, in such a scenario I don't mind to go for a 2.0 release shortly after 1.0. My main point is, if the CLI app work does not become a proposal with both, significant community interest and someone stepping up to lead this, I would prefer to never introduce the cross-publishing. Which is why I gave the download statistics for reference, without the CLI work kicking in I don't think it's attractive to cross-publish.

I just have no idea what this means in practical terms, so someone would need to brief me a bit on this...

@valencik can expand more, but by "org level" project I mean moving the project under the github.com/typelevel org (and possibly publishing under the org.typelevel groupid). IMO Laika was already a great candidate for membership, and now that it is core infrastructure it makes even more sense. Since you are looking for more admin-level maintainers, this seems like it could be a good fit for you as well :)

not cross-publish 1.0 at all if these criteria are not met around the time we get close to the first RC

Yup, we are very much in agreement on this :) without a CLI I just don't see a compelling usecase, although users should certainly chime in if they do!

I just have no idea what this means in practical terms, so someone would need to brief me a bit on this...

@valencik can expand more, but by "org level" project I mean moving the project under the github.com/typelevel org (and possibly publishing under the org.typelevel groupid). IMO Laika was already a great candidate for membership, and now that it is core infrastructure it makes even more sense. Since you are looking for more admin-level maintainers, this seems like it could be a good fit for you as well :)

I think that might be a good step to consider. Changing the group ID for 1.0 would also be ok, that's a step where users will not be caught by surprise when major changes are made. Shall we move the conversation somewhere else? It does not really belong into this ticket.

Hey @jenshalm, yeah, let's move this discussion elsewhere. The right place is likely an issue on the governance repo: https://github.com/typelevel/governance.
I am collecting some thoughts from the other steering committee members on a non-legalese description of what practically happens when a project joins as either an organization project or affiliate project. I hope to have more to share shortly.
So feel free to create an issue on the governance repo. You can create a blank issue, you don't have to follow the project submission template for this discussion. Or, once I have some more feedback from the team I'll create one and tag you :)

Thank you for the pointers, I'll probably write up a little proposal sometime in the coming weeks when I return to spending a bit more time on this project.


post type to enable in wp-api

I just read that wp-api 2 does not  supports from default custom type. This one needs to be enabled by passed $args like 'show_in_rest'       => true,. How would I do that?

Sorry I don't quite understand, I'm not very familiar with WP-API, could you give me the link to what you're referring to so I can look into it.
Thanks :)

I just did a quick search,
I believe you just need to add it to the second parameter when creating the post type, for example
$books = new CPT('book', array(
    'show_in_rest' => true
));

I got it between thank you. Great Class!

No problem and thanks! :)


Update CI/CD & use flit build system

Description:

Closes #74
Closes #76
Uses SINTEF/ci-cd for workflows.
Updates to use the flit build system (instead of setuptools), collecting all relevant package management information in the single pyproject.toml file.
NOTE: Since this PR updates the workflows, the required status checks set for the master branch (and ci/dependency-updates) must be updated prior to merging this PR, and all other open PRs must be rebased/updated accordingly after this has been merged.
Type of change:

[ ] Bug fix.
[ ] New feature.
[ ] Documentation update.

Checklist for the reviewer:

This checklist should be used as a help for the reviewer.

[ ] Is the change limited to one issue?
[ ] Does this PR close the issue?
[ ] Is the code easy to read and understand?
[ ] Do all new feature have an accompanying new test?
[ ] Has the documentation been updated as necessary?

Codecov Report
Base: 93.49% // Head: 93.49% // No change to project coverage :thumbsup:

Coverage data is based on head (d35ec4e) compared to base (098f86a).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##           master      #77   +/-   ##
=======================================
  Coverage   93.49%   93.49%
=======================================
  Files          20       20
  Lines         338      338
=======================================
  Hits          316      316
  Misses         22       22

Flag
Coverage Δ

linux
93.49% <ø> (ø)

windows
?

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

otelib/backends/python/base.py
89.70% <ø> (ø)

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Error 502

App is registering at your url. But when I change it to mine I'm getting 502 error. Why, http://movie.jkdesigns.lk

Created database
Imported SQL file
Changed the DBOperations.php credentials....

Issue Found:
php versions -> PDO not enabled - fixed
php versions -> json not enabled - fixed
renamed functions.php into  Functions.php as in index.php line #3 require_once 'Functions.php';

@JKDesignslk  is your issue resolved or is it still there ?


[tests] Fix liveexec windows realtime output

Realtime output on windows is broken. Do not use pipes on windows to get external process output in liveexec package.
Switch back liveexec to github.com/onsi/gomega/gexec.

/run tests


version in the OpenAPI descriptions is incorrect

The version field of the OpenAPI description is currently being set to a random number instead of the true version (v1.0|beta).
This is causing issues for indexers and might be confusing to consumers of the description.
We should address this in the generation process to correct that information.
Once this is fixed, please revert to the issue linked to give a heads up to maintainers.

@baywet this sounds like a conversion issue. Should we move it to the relevant repository?

You are correct, the conversion library reads the information from the odata context.
https://github.com/microsoft/OpenAPI.NET.OData/blob/a8d815a19f8feae41c55fc66779d25d26ef7eb78/src/Microsoft.OpenApi.OData.Reader/Generator/OpenApiInfoGenerator.cs#L29
And that comes from the version in the convert settings.
https://github.com/microsoft/OpenAPI.NET.OData/blob/a8d815a19f8feae41c55fc66779d25d26ef7eb78/src/Microsoft.OpenApi.OData.Reader/OpenApiConvertSettings.cs#L28
Transferring.
(once the fix is implemented, we'll need to update the conversion settings)

I'm not powerful enough to transfer between orgs. closing this and will reopen on the other side.

created this https://github.com/microsoft/OpenAPI.NET.OData/issues/346


Import options don't refresh after reimport

Godot version
4.1.beta.official
System information
Windows 10
Issue description
EditorImportPlugin options that change visibility based on the value of other options don't update after reimporting the asset.
Steps to reproduce

Create an EditorImportPlugin that implements _get_import_options and _get_option_visibility.
In _get_option_visibility, return true or false depending on the value of a separate option.
Changing that variable should show or hide the other on reimport, but doesn't.

Minimal reproduction project

Thanks for the report! Consolidating in https://github.com/godotengine/godot/issues/49641.


Move Supermicro.IMPIView 2.21.1 to Supermicro.IPMIView 2.21.1

Checklist for Pull Requests

[x] Have you signed the Contributor License Agreement?
[x] Resolve #201782

Depend on #202054

Manifests

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

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

Microsoft Reviewers: Open in CodeFlow

@stephengillie, further investigation required. 🙏🏼
Changes are generated by Tools/YamlCreate.ps1 with "package identifier rename" feature.


FR:  supports command-modifiers  for :GrugFar

make grug-far buffer be opened aboveleft or botright the current window.

already supported 😄, see this option https://github.com/MagicDuck/grug-far.nvim/blob/c5b4aab4dc4e7d10e77fd12324cd1a29441c0f15/lua/grug-far/opts.lua#L26

oh do you mean like on the command itself?

yes, like run :aboveleft GrugFar to open the grug-far buffer in the left of current win.

@gh-liu command-modifiers should now be supported 😄


Add CodeQL security scanning

Hi, I'm a PM on the GitHub security team. This repository is eligible to try the new GitHub Advanced Security code scanning beta.
Code scanning runs a static analysis tool called CodeQL which scans your code at build time to find any potential security issues. We've tuned the set of queries to be only the most severe, most precise issues. We'll show alerts in the security tab, and we'll show alerts for any net new vulnerabilities on pull requests as well. We've tried to make this super developer friendly, but we'd love your feedback as we work through the beta.
If you're interested in trying it out, you can merge this pull request to set up the Actions workflow.

This one should be good to go if you're happy with it. The build is working in my fork.

@jhutchings1
Thanks for raising the PR!
Several questions:

How long will CodeQL  runs? Just to want to will it make the develop process be slower.
What kind of issue will be found by CodeQL , how will it reported, and how should we handle it?

@blueww Thanks for having a look

How long will CodeQL  runs? Just to want to will it make the develop process be slower.

The build took 5m 27s. That's currently faster than your existing test run, so your developers wouldn't notice since it runs in parallel.

What kind of issue will be found by CodeQL , how will it reported, and how should we handle it?

CodeQL is configured to find security vulnerabilities. After the first run, you'll see results in the Security tab for your repo. These are visible to folks with write permissions. You'll also see information about any new vulnerabilities in your Checks for pull requests, so you can make sure that new vulnerabilities don't make it into your code. I'd recommend that you treat any of the alerts as real, and try to fix them. If it's in test code, or is a false positive, you can close the alert by providing that reason, however.

@jhutchings1
Thanks for the detail! I am good for this PR.
@XiaoningLiu
Would you please help to look, if you are also good with it, we can merge it.


Aca-Py Endorsement in Sovrin MainNet?

Hello
I have a question: Is it possible to use a aca-py agent as andorser on Sovrin MainNet? Currently we use builder and Staging, but someone said, on MainNet the aca-py protocol is not implemented yet.
Regards, Roman

Closing this issue.


feat: add languages page

Adds /languages page
this page contains links to documentation in other languages
ref: denoland/deno#7490, denoland/deno#5435, denoland/deno#5911, #550

@ry WDYT?

@tokiedokie Cool - put the link with the other "extra" pages at the bottom. Title it "Translations"?

@ry Thank you for your response. I renamed languages to translations, added link to translations on footer


error while starting

Description
Please provide as much info as you can.
There is a big error in console while starting the bot , something related to sqlite.

Can you please provide more info. By saying 'a big error in console while starting bot' is not very helpful. Please include screenshots if you can too.

Please explain your error in details. Better you join the Support Server.(Link in Readme)

Closed due to inactivity & no response.


Write 'Helm Charts' section

Info should be sourced from walkthrough with Keating. Video forthcoming.

https://staging-haus-toolbox.vercel.app/decentralized-infrastructure/helm-charts

https://github.com/HausDAO/sdk-docs/pull/34/commits


refactor: JSON-based render content-type and clean-up

Cleans up the JSON-based renders as follows

Inject a function "initialize" that defaults to "application/json"
Removed all manual "application/json" settings
Remove vi's special loginSucceeded() that was implemented for ViUR-vi <= 3

@sveneberth will provide an alternative attempt.


uninitialized constant ResourceKit::ResourceCollection::Forwardable

Good day, i'm running into issues while trying to perform a snapshot backup.

Using ruby 2.4.1, OSX
Installed do_snapshot as a gem
Set ENV token variable
Execute do_snapshot --only 53097244 -k 5 -c -v

Result:
Start performing operations
Loading list of DigitalOcean droplets
uninitialized constant ResourceKit::ResourceCollection::Forwardable
/Users/sk/.rvm/gems/ruby-2.4.0@servpro-devops/gems/resource_kit-0.1.6/lib/resource_kit/resource_collection.rb:3:in `<class:ResourceCollection>'
/Users/sk/.rvm/gems/ruby-2.4.0@servpro-devops/gems/resource_kit-0.1.6/lib/resource_kit/resource_collection.rb:2:in `<module:ResourceKit>'
/Users/sk/.rvm/gems/ruby-2.4.0@servpro-devops/gems/resource_kit-0.1.6/lib/resource_kit/resource_collection.rb:1:in `<top (required)>'
/Users/sk/.rvm/rubies/ruby-2.4.0/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in `require'
/Users/sk/.rvm/rubies/ruby-2.4.0/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in `require'
/Users/sk/.rvm/gems/ruby-2.4.0@servpro-devops/gems/do_snapshot-1.0.0/lib/do_snapshot/gem_ext/resource_kit.rb:19:in `<top (required)>'
/Users/sk/.rvm/gems/ruby-2.4.0@servpro-devops/gems/do_snapshot-1.0.0/lib/do_snapshot/adapter/droplet_kit.rb:4:in `require_relative'
/Users/sk/.rvm/gems/ruby-2.4.0@servpro-devops/gems/do_snapshot-1.0.0/lib/do_snapshot/adapter/droplet_kit.rb:4:in `<top (required)>'
/Users/sk/.rvm/rubies/ruby-2.4.0/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in `require'
/Users/sk/.rvm/rubies/ruby-2.4.0/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in `require'
/Users/sk/.rvm/gems/ruby-2.4.0@servpro-devops/gems/do_snapshot-1.0.0/lib/do_snapshot/adapter.rb:13:in `const_defined?'
/Users/sk/.rvm/gems/ruby-2.4.0@servpro-devops/gems/do_snapshot-1.0.0/lib/do_snapshot/adapter.rb:13:in `api'
/Users/sk/.rvm/gems/ruby-2.4.0@servpro-devops/gems/do_snapshot-1.0.0/lib/do_snapshot/command.rb:102:in `api'
/Users/sk/.rvm/gems/ruby-2.4.0@servpro-devops/gems/do_snapshot-1.0.0/lib/do_snapshot/command.rb:144:in `load_droplets'
/Users/sk/.rvm/gems/ruby-2.4.0@servpro-devops/gems/do_snapshot-1.0.0/lib/do_snapshot/command.rb:133:in `work_with_droplets'
/Users/sk/.rvm/gems/ruby-2.4.0@servpro-devops/gems/do_snapshot-1.0.0/lib/do_snapshot/command.rb:21:in `snap'
/Users/sk/.rvm/gems/ruby-2.4.0@servpro-devops/gems/do_snapshot-1.0.0/lib/do_snapshot/cli.rb:161:in `snap'
/Users/sk/.rvm/gems/ruby-2.4.0@servpro-devops/gems/thor-0.20.0/lib/thor/command.rb:27:in `run'
/Users/sk/.rvm/gems/ruby-2.4.0@servpro-devops/gems/thor-0.20.0/lib/thor/invocation.rb:126:in `invoke_command'
/Users/sk/.rvm/gems/ruby-2.4.0@servpro-devops/gems/thor-0.20.0/lib/thor.rb:387:in `dispatch'
/Users/sk/.rvm/gems/ruby-2.4.0@servpro-devops/gems/thor-0.20.0/lib/thor/base.rb:466:in `start'
/Users/sk/.rvm/gems/ruby-2.4.0@servpro-devops/gems/do_snapshot-1.0.0/lib/do_snapshot/runner.rb:39:in `run_cli'
/Users/sk/.rvm/gems/ruby-2.4.0@servpro-devops/gems/do_snapshot-1.0.0/lib/do_snapshot/runner.rb:18:in `execute!'
/Users/sk/.rvm/gems/ruby-2.4.0@servpro-devops/gems/do_snapshot-1.0.0/bin/do_snapshot:16:in `<top (required)>'
/Users/sk/.rvm/gems/ruby-2.4.0@servpro-devops/bin/do_snapshot:22:in `load'
/Users/sk/.rvm/gems/ruby-2.4.0@servpro-devops/bin/do_snapshot:22:in `<main>'
/Users/sk/.rvm/gems/ruby-2.4.0@servpro-devops/gems/resource_kit-0.1.6/lib/resource_kit/resource_collection.rb:3:in `<class:ResourceCollection>': uninitialized constant ResourceKit::ResourceCollection::Forwardable (NameError)
	from /Users/sk/.rvm/gems/ruby-2.4.0@servpro-devops/gems/resource_kit-0.1.6/lib/resource_kit/resource_collection.rb:2:in `<module:ResourceKit>'
	from /Users/sk/.rvm/gems/ruby-2.4.0@servpro-devops/gems/resource_kit-0.1.6/lib/resource_kit/resource_collection.rb:1:in `<top (required)>'
	from /Users/sk/.rvm/rubies/ruby-2.4.0/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /Users/sk/.rvm/rubies/ruby-2.4.0/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /Users/sk/.rvm/gems/ruby-2.4.0@servpro-devops/gems/do_snapshot-1.0.0/lib/do_snapshot/gem_ext/resource_kit.rb:19:in `<top (required)>'
	from /Users/sk/.rvm/gems/ruby-2.4.0@servpro-devops/gems/do_snapshot-1.0.0/lib/do_snapshot/adapter/droplet_kit.rb:4:in `require_relative'
	from /Users/sk/.rvm/gems/ruby-2.4.0@servpro-devops/gems/do_snapshot-1.0.0/lib/do_snapshot/adapter/droplet_kit.rb:4:in `<top (required)>'
	from /Users/sk/.rvm/rubies/ruby-2.4.0/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /Users/sk/.rvm/rubies/ruby-2.4.0/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /Users/sk/.rvm/gems/ruby-2.4.0@servpro-devops/gems/do_snapshot-1.0.0/lib/do_snapshot/adapter.rb:13:in `const_defined?'
	from /Users/sk/.rvm/gems/ruby-2.4.0@servpro-devops/gems/do_snapshot-1.0.0/lib/do_snapshot/adapter.rb:13:in `api'
	from /Users/sk/.rvm/gems/ruby-2.4.0@servpro-devops/gems/do_snapshot-1.0.0/lib/do_snapshot/command.rb:102:in `api'
	from /Users/sk/.rvm/gems/ruby-2.4.0@servpro-devops/gems/do_snapshot-1.0.0/lib/do_snapshot/command.rb:144:in `load_droplets'
	from /Users/sk/.rvm/gems/ruby-2.4.0@servpro-devops/gems/do_snapshot-1.0.0/lib/do_snapshot/command.rb:133:in `work_with_droplets'
	from /Users/sk/.rvm/gems/ruby-2.4.0@servpro-devops/gems/do_snapshot-1.0.0/lib/do_snapshot/command.rb:21:in `snap'
	from /Users/sk/.rvm/gems/ruby-2.4.0@servpro-devops/gems/do_snapshot-1.0.0/lib/do_snapshot/cli.rb:161:in `snap'
	from /Users/sk/.rvm/gems/ruby-2.4.0@servpro-devops/gems/thor-0.20.0/lib/thor/command.rb:27:in `run'
	from /Users/sk/.rvm/gems/ruby-2.4.0@servpro-devops/gems/thor-0.20.0/lib/thor/invocation.rb:126:in `invoke_command'
	from /Users/sk/.rvm/gems/ruby-2.4.0@servpro-devops/gems/thor-0.20.0/lib/thor.rb:387:in `dispatch'
	from /Users/sk/.rvm/gems/ruby-2.4.0@servpro-devops/gems/thor-0.20.0/lib/thor/base.rb:466:in `start'
	from /Users/sk/.rvm/gems/ruby-2.4.0@servpro-devops/gems/do_snapshot-1.0.0/lib/do_snapshot/runner.rb:39:in `run_cli'
	from /Users/sk/.rvm/gems/ruby-2.4.0@servpro-devops/gems/do_snapshot-1.0.0/lib/do_snapshot/runner.rb:18:in `execute!'
	from /Users/sk/.rvm/gems/ruby-2.4.0@servpro-devops/gems/do_snapshot-1.0.0/bin/do_snapshot:16:in `<top (required)>'
	from /Users/sk/.rvm/gems/ruby-2.4.0@servpro-devops/bin/do_snapshot:22:in `load'
	from /Users/sk/.rvm/gems/ruby-2.4.0@servpro-devops/bin/do_snapshot:22:in `<main>'

Any clue what is the problem and how I can fix this?

Similar error, Ubuntu 14.04, ruby 2.3.1:
/root/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/resource_kit-0.1.6/lib/resource_kit/resource_collection.rb:3:in <class:ResourceCollection>': uninitialized constant ResourceKit::ResourceCollection::Forwardable (NameError)         from /root/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/resource_kit-0.1.6/lib/resource_kit/resource_collection.rb:2:in module:ResourceKit'
from /root/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/resource_kit-0.1.6/lib/resource_kit/resource_collection.rb:1:in <top (required)>'         from /root/.rbenv/versions/2.3.1/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in require'
from /root/.rbenv/versions/2.3.1/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in require'         from /root/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/do_snapshot-1.0.0/lib/do_snapshot/gem_ext/resource_kit.rb:19:in <top (required)>'
from /root/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/do_snapshot-1.0.0/lib/do_snapshot/adapter/droplet_kit.rb:4:in require_relative'         from /root/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/do_snapshot-1.0.0/lib/do_snapshot/adapter/droplet_kit.rb:4:in <top (required)>'
from /root/.rbenv/versions/2.3.1/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in require'         from /root/.rbenv/versions/2.3.1/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in require'
from /root/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/do_snapshot-1.0.0/lib/do_snapshot/adapter.rb:13:in const_defined?'         from /root/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/do_snapshot-1.0.0/lib/do_snapshot/adapter.rb:13:in api'
from /root/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/do_snapshot-1.0.0/lib/do_snapshot/command.rb:102:in api'         from /root/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/do_snapshot-1.0.0/lib/do_snapshot/command.rb:144:in load_droplets'
from /root/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/do_snapshot-1.0.0/lib/do_snapshot/command.rb:133:in work_with_droplets'         from /root/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/do_snapshot-1.0.0/lib/do_snapshot/command.rb:21:in snap'
from /root/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/do_snapshot-1.0.0/lib/do_snapshot/cli.rb:161:in snap'         from /root/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/thor-0.20.0/lib/thor/command.rb:27:in run'
from /root/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/thor-0.20.0/lib/thor/invocation.rb:126:in invoke_command'         from /root/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/thor-0.20.0/lib/thor.rb:387:in dispatch'
from /root/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/thor-0.20.0/lib/thor/base.rb:466:in start'         from /root/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/do_snapshot-1.0.0/lib/do_snapshot/runner.rb:39:in run_cli'
from /root/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/do_snapshot-1.0.0/lib/do_snapshot/runner.rb:18:in execute!'         from /root/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/do_snapshot-1.0.0/bin/do_snapshot:16:in <top (required)>'
from /root/.rbenv/versions/2.3.1/bin/do_snapshot:23:in load'         from /root/.rbenv/versions/2.3.1/bin/do_snapshot:23:in '

Oops. I will fix it asap. Seems it's caused by my monkey patch of resource_kit. This library still don't have full support for ruby 2.4.
Please use 0.6.4 till fix.

Fixed, checked from OSX.


Increment version for cosmosdb releases

Increment package version after release of Azure.ResourceManager.CosmosDB

API change check
API changes are not detected in this pull request.


Not downloading reels if they aren't inclided in the "posts" section

Describe the bug
Instaloader is not downloading a profile's reels unless they are included as profile "posts"
To Reproduce
instaloader -s --highlights --igtv --login=_xxxxxx zzzzzz
Expected behavior
Instaloader should be able to download separate reels, even if they aren't in the "posts" tab
Instaloader version
4.9

Maybe duplicate of #812 ?
I don't know if there has been any progress on it.


socha 2.0.1 incomplete

Description
in venv:
pip install socha => socha 2.0.1
socha is incomplete, from socha install  IClientHandler, ... or from socha install * does not find to the classes expected in module socha
Environment

Python version: 3.11.2
Operating System: Debian 12
Version of the Python SoCha Client: 2.0.1

Many thanks for the tip. In fact, everything is still there, but the imports in init.py had to be removed (f8d397ab1e23750d59f39733d43003f0da3476f4), otherwise the code completion of the IDEs would get mixed up. Unfortunately, the logic.py was forgotten to be adapted accordingly.


SSH Proxy - Question

Sorry if this is a noob question.
This plugin will allow me to proxy ssh to a local ip? For example ssh.myserver to localhost:22?
The reason I want this is that I’m behind a corporate firewall that blocks outgoing ssh connections.
However if I could cloak it in https traffic it would work. As long I configure sshd to respond to http requests then this plugin should is what I’m looking for correct ? I believe you can do this with apache using http connect module.

However if I could cloak it in https traffic it would work.

It would still be raw TCP traffic. This plugin wouldn't "cloak" anything as HTTPS. All this does is raw TCP/UDP connections and traffic, then allows you to handle it depending on the shape of the data.

This module can be used to "cloak" connections but clients have to be configured to work with it. For example, TLS-in-TLS. You could in theory do SSH-in-TLS too, but you'd need a wacky SSH client that can establish a TLS handshake and then send SSH over it. :man_shrugging:

Thanks, I’ll test and see if it works.  If your curious this is the setup I want to replicate
https://nurdletech.com/linux-notes/ssh/via-http.html
It’s just I use caddy as my front reverse proxy and am happy with it. Don’t want to switch to Apache. Anyway I think this may work or at the very least allow me to have ssh.myserver dns which listens on 443 rather than port 22 which might allow me to bypass the firewall.

So if I understand correctly, you want to serve both HTTP(S) and SSH on the same port (either 80 or 443)?
If so, you don't need any special client. Just use the ssh matcher to proxy SSH connections to your SSH server, and everything else to your HTTP server. (Similar examples are in our README.)
Will close now as I think that should answer your question...


update(cmake/modules): bump Falco rules to 3.0

What type of PR is this?
/kind cleanup
Any specific area of the project related to this PR?
/area build
What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Note: FALCOSECURITY_RULES_FALCO_CHECKSUM is unchanged, since the file content is identical to last RC.
/milestone 0.37.0
Does this PR introduce a user-facing change?:

update: default ruleset upgrade to version 3.0

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

Needs approval from an approver in each of these files:

OWNERS [leogr]

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

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

Needs approval from an approver in each of these files:

OWNERS [Andreagit97,leogr]

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

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

Needs approval from an approver in each of these files:

OWNERS [Andreagit97,FedeDP,leogr]

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


Test-pr

@mdroidian 👋
I'm going to kindly ask they you move your testing of PRs back on to your fork rather than on the source.
Thanks!


Update README.md

Added import instructions for the 'do it yourself'ers' who weren't lucky enough to start their apps in Vue.  If importing in modules is still necessary for SPA's and that step is still missing from the docs, someone else will need to confirm.

The's not quite the right way to import an ES6 module. at a minimum it requires the module attribute, but more importantly, if it's legacy support people are looking for they should use the cdn installation options. I'll close this for now, but feel free to re-submit with modified docs.


Leap Motion Core Version 4.4.0  if Scale !=1  Hand Mesh Deformation occurred

For now, this is a known issue with our rigged hand models for which we don't have a fix in the pipeline. Hands need to be rendered at unit scale to deform correctly. I haven't looked deeply into this because our demos are all built at unit scale: 1 Unity Unit == 1 Meter.
It should be possible to scale the model of a rigged hand to compensate for the increased bone length, but it's not something we support currently.

We are now in 2020 Is there no solution?
@nickjbenson

We currently have no plans to support this. However, it would be interesting to know more about your use case for this?

@Ultraleap-Dan I am also having the same problem and I was hoping Ultraleap would support this.
Currently we are working on a demo for our HMD device and that demo is scaled 10x, which wasn't an issue until now. I agree that the demo is not correctly scaled with the real world, and we could potentially make the demo to be correctly scaled too, but we tried that and it's not worth the effort. Doing an overall scale adjustment messes up with many aspects of our demo scene, so the best we can do is to place our hands very close to the camera for it to seem like it's in the correct scale -- though the distortion wouldn't be correct.
Anyways, it's really annoying that you guys haven't implemented a scaling feature in your SDK, and I really hope you do in the near future.


Add close state to tsdb.DB

Does this solve any known issue?

Does this solve any known issue?

No, but a more consistent state makes this "library" easier to use, for example, return an error or nil is better than panic when calling DB.Close twice.

I have pushed another commit to fix the logic when open tsdb.DB, and it may cause a panic now without the close state.

My opinion is not to add more code except when fixing a bug, adding a feature that users have asked for, or clearly improving performance.

@bboreham If you read my comment carefully, this is a BUG fix:

I have pushed another commit to fix the logic when open tsdb.DB, and it may cause a panic now without the close state.


Search sorted lower bin search

Binary search implementation
Description
Implement binary search for hint search sorted lower and fix a bug in operations_with_data_structures.cairo
Resolves #315
Checklist

[x] Linked to Github Issue

Codecov Report

Merging #438 (040f65d) into main (4a243e4) will decrease coverage by 0.02%.
The diff coverage is 89.47%.

@@            Coverage Diff             @@
##             main     #438      +/-   ##
==========================================
- Coverage   91.94%   91.92%   -0.03%
==========================================
  Files          48       48
  Lines        3302     3317      +15
==========================================
+ Hits         3036     3049      +13
- Misses        266      268       +2

Impacted Files
Coverage Δ

...cessor/builtin_hint_processor/find_element_hint.rs
91.25% <89.47%> (-1.06%)
:arrow_down:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Was this change properly benchmarked? Does it create more objects?

I'll close this. It's becoming stale, there are no benchmarks to measure the changes (neither for runtime nor for memory usage) and we have no time to prioritize it right now and it would need some changes to be merged.


*: regenerate proto to use local import path

Using Go-style import paths in protos is not idiomatic. Normally, this
detail would be internal to etcd, but the path from which gogoproto
is imported affects downstream consumers (e.g. cockroachdb).
In cockroach, we want to avoid including $GOPATH/src in our protoc
include path for various reasons. This patch puts etcd on the same
convention, which allows this for cockroach.
More information: https://github.com/cockroachdb/cockroach/pull/2339#discussion_r38663417
This commit also regenerates all the protos, which seem to have
drifted a tiny bit.
cc @xiang90 @yichengq @bdarnell

LGTM. Please change the commit message to "*: regenerate proto to use local import path"
/cc @yichengq

changed the message

LGTM


Fix typos and broken links in README

Just a few more README fixes I missed the first time around...

Thanks


Best way to find "directly" inherited types?

Lets say we need the "tree" of inheritance
to display in a gui
or generate wrappers (non cpp) mirroring a class hierarchy
get_base_classes() returns ALL classes, as does get_derived_classes()
is_base_of() and is_derived_from() both consider ALL types inherited
What it the best way to find the types "directly" inherited using the RTTR public API?
Ex
struct a {} ;
struct b : a {};
struct c {} ;
struct d : c, b {};
We want to return range of types
"c, b"
for stuct d rather than
"a, b, c"
as get_base_classes() provides

Sorry, but at the moment there is no such function to get this information.
I have to provide such function similar to this like get_properties(filter_item

PR #237 - add rttr:type::get_direct_base_classes()
https://github.com/rttrorg/rttr/pull/237


T4.3.1 requirements for monitoring values, display, alerting

find in walletBE source code sites that might benefit from monitoring or display in EKG.

We could monitor events which are related to benchmarked functions (please see https://github.com/input-output-hk/iohk-monitoring-framework/issues/327#issuecomment-501222535)


Max Length Policies API level changes

@ukrocks007  One suggestion:
const { name, slug, domain } = req.body;
validateWithSchema(updateTeamSchema, req.body);

With above code;

We're loosing the type safety Zod provides.
If you have transform method within Zod schema, when reading from req.body, it will not be transformed.

So better do
const { name, slug, domain } = validateWithSchema(updateTeamSchema, req.body);

Make sure you have proper return type on validateWithSchema method.


Merge OSQPSettings and OSQPData destruction into osqp_cleanup()?

In the C implementation, OSQPSettings and OSQPData resources have to be destroyed separately from the workspace osqp_cleanup(), I am curious if it is possible to merge OSQPSettings and OSQPData destruction into OSQPWorkspace clean up, so that osqp_cleanup() cleans up everything?
Thanks for this great library.

I think that we would not want to merge them into a single struct, but it might be an idea to create single top-level struct that has pointers to the OSQP Settings / Data / Workspace structs as members.     Creating / destroying a solver would then be a bit shorter I suppose.
This is roughly how OSQP works through its interfaces, i.e. the Matlab and Python interfaces both have a single high-level class 'osqp' that acts as a container for all of the C pieces.

This is what I am doing now:
void new_osqp_cleanup(void *workspace)
{
	OSQPWorkspace* work = (OSQPWorkspace*)workspace;
	if (NULL!=work)
	{
		if (NULL!=work->data)
		{
			c_free(data->A);
			c_free(data->P);
			c_free(data);
		}
		if (NULL!=work->settings)
		{
			c_free(settings);
		}
		osqp_cleanup(work);
	}
}

I think we are following the idea that the memory is cleaned by the function/program that allocated it. Since OSQP functions do not create the data and settings structures, they should not clean it either. One reason for doing this is because these structures can also be statically allocated.
Also, I think you should not clean matrices P and A using c_free function. This will probably cause a memory leak. You should use this function instead.

Thanks @gbanjac , that's good to know.
I modified the example from:
https://github.com/oxfordcontrol/osqp/blob/master/examples/osqp_demo.c#L57
I think the example should be fixed as well.

Actually, in the example above the vectors P_x, P_p, P_i, A_x, A_p, A_i are statically allocated, so the cleanup is done correctly. I assumed you created the matrices with this function.

Thanks for pointing out. I am trying to create another language binding for OSQP, I think I will just create a new struct that holds workspace, settings and data. We can probably close this issue. Thanks for the help.

Based on the comments above, it is clear why we don't want to have a single function that cleans all the OSQP structures. Essentially, one cannot know a priori if the data are allocated statistically or dynamically.
I suggest closing the issue.

@hyumo Please do let us know if you create an interface in any additional languages, particularly if it is public.

I will do my best to make it open source.
I am trying to make a Modelica interface, to be honest, the implementation is quite straight forward thanks to the very clean C interface.


Allow rules evaluation for Gitlab

I saw that the generic OIDC feature allows evaluating rules to determine if a user is an admin or not. It would be great if the Gitlab connector also supported this feature.

I'd be happy to accept a PR for this.
The gitlab provider uses the OIDC provider under-the-hood so it should be as easy as accepting and passing the config forward.


missing to probe some domain.

here you can check.

Hey @blackcodersec ,
Thank you for this and I want to inform that I'm already aware of this problem and Im still in development of subprober to resolve this issue, soon I will make a update on this issue thank you for this :)

Is it possible to show redirected domain like fhc output.

Hey @blackcodersec ,
Since the both tools are build for different purpose and these output will be not same but you can get more information from subprober , you can see in your output how the both redirected location urls are different , unlike fhc,  subprober gives output differently not same as the fhc.

Hey @sanjai-AK47,
I know both tools are build for different purpose and these outputs are not same.
but I use subprober for httpx & httprobe alternative script. that's why I said is this possible or not.
actually, I like python script, that's why I check your script and created the issue, but I think it increases the feature of your script.
okay, no problem.
fhc doing good.

Hey @blackcodersec ,
Thanks for providing information about your needs, Subprober can't give output like the fhc , if I made those changes means it will also affect entire subprober outputs so sorry to say subprober cannot give output like this but after looking on your provided img , I can make this update on another tool httprober. if you have other issues means please submit it and thanks for showing your intrest on my tools.I want to clear one more thing is enabling -ar will make subprober to follow redirection and give results of redirected domain only and to know that I updated subprober with -l and -ar flags

I saw your httprober script. There are not available function like subprober. That's why I use your subprober script.
Ok, as your wish :)

Hey @sanjai-AK47 ,
Is it possible to implement -dhp,-ar,-px,-das,-to,-mc,-ex on the httprober script?
I think it would be good.
Another thing is the accuracy and concurrency of httpprober as the subprober script?

Hey @blackcodersec ,
really appreciate your ideas but httprober is simple probing tool for replacement of  tomnomnom's httprobe, Since httprobe ris running on traditional threading, It will be updated to asychoronous performance and its not possible to add those features in that.

Ok no problem :)

completed this issue thank you


fix: readd autopause

Fixes #229.
This one is just embarrassing, please approve and let's move on. 🤡

CI blocking merge because of #231. Once that is merged, pull main into into here and retry.


feat: catalyst redirect

Jira: B2B-1932
What/Why?
Catalyst cart redirect
Rollout/Rollback
revert
Testing
https://github.com/user-attachments/assets/e561d434-0281-43a0-a1c1-d5112a7fa54c

@bc-micah I disabled cspell as it introduced several errors, we should tackle them in a separate PR before incorporating again


ValueError: day is out of range for month

In most cases it works, but not with these dates:
ValueError: day is out of range for month
2011-09-09 14:00:00
2020-06-15 14:00:00
2021-07-06 08:00:00
{% from 'relative_time_plus.jinja' import relative_time_plus %}
{{ relative_time_plus("2011-09-09 14:00:00", 5, language="de") }}
{{ relative_time_plus('2023-01-01', parts=2, time=false, not_use=['wk']) }}

Home Assistant on Docker
Core 2024.5.5
Frontend 20240501.1
Relative Time Plus v2.2.3 (Hacs)

Fixed in https://github.com/TheFes/relative-time-plus/releases/tag/v2.2.4


Subtraction Operator Outputs Wrong Result While Using TFLite Model

Hi there,
I'm using ARMNN 20.05, android-ndk-r20b-linux-x86_64, with API 21.
I found the output of subtraction operator giving me wrong result while using tflite model. I will show you in a toy example:

I build a tensorflow lite model with subtraction operator only, the model does one thing: f(x) = x - 1. However, the result I got was: f(x) = 1-x. Could you please kindly check the tflite parser to see whether there are some issues? I'll attach my toy project below. There is a readme.md in the compressed file, showing how to compile and test.
armnn_sub_sample.zip

Hi @XiaoxingChen ,
Thanks for reporting this issue. We are investigating it now.
Cheers,
James

Hi @XiaoxingChen
Thank you for the report and the example, this reveals a defect in the way we handle Broadcasting in all TFLite operations. When we have to Broadcast a Tensor for an operation we put in a Reshape for the smaller Tensor (in this case input B) but due to a bug in our code the reshaped Tensor was always connected to the first input and the non-reshaped Tensor to the second input. In this case it reversed the operand order for the operation changing it from A - B to B - A.
I've fixed the issue so we remember the correct order for the inputs. The code for the fix is at:
https://review.mlplatform.org/c/ml/armnn/+/3515
It should be merged in the next day or so.
Best regards,
Mike

Hi @XiaoxingChen ,
@MikeJKelly 's patch has now merged. Please let us know if this resolves your issue.
Cheers,
James

Hi @james-conroy-arm and @MikeJKelly ,
Thank you for your fast response, the patch works!
Best!
Xiaoxing.

Glad to help!
Please let us know if we can close this issue, if you don't have any other questions relating to this.
Cheers,
James

Yes, James, please close it. Appreciate your efforts!


nextjs+pm2:  [PM2][ERROR] script not found

I'm using pm2 to start my application in production
here's my script
  "scripts": {
    "dev": "cross-env NODE_ENV=development PORT=3000 node server/server.js",
    "build": "next build",
    "start": "next start"
  },

here's my ecosystem.config.js file
module.exports = {
  apps: [
    {
      name: "ssr",
      script: "next",
      instances: 1,
      autorestart: true,
      watch: true,
      max_memory_restart: "1G",
      env: {
        NODE_ENV: "development"
      },
      env_production: {
        NODE_ENV: "production"
      }
    }
  ]
};

when I run pm2 start ecosystem.config.js in server, I got an error

need some help, thanks

Please follow the issue template, questions should be posted on https://spectrum.chat/next-js as the community is there. However I doubt this is an actual issue with Next.js, and more related to the configuration 🤔


Add prototype of application to find matching pipelines

find_pipelines loads all of the spirv listed in a flat file (probably obtained through something like find . -name *.spv > spv.txt) and then compares inputs and outputs to build pipelines.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


[Improvement][k8s] Update the deprecated k8s api

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Description
Update the deprecated k8s api
Are you willing to submit a PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Since K8S task plugin was released in 3.1.0 and no classes will use K8sUtils in 3.0.x, I think this PR might be better cherry-picked to 3.1.x or 3.2.0 instead of 3.0.2.


[1.19.2] Broken Textures

Mod Version 1.1.1
forge Version 43.1.52
Describe the bug
Some textures are broken with the latest update.
Screenshots

this is already fixed in https://github.com/sa-shiro/Minecraft-Compressed-Blocks/commit/6dea9aed4936d8935164ea0b34425d8d57b6c837
upload to cf is under review

take this as a faster solution, idk how long curseforge will need
https://github.com/sa-shiro/Minecraft-Compressed-Blocks/releases/tag/1.1.1


Folder duplicates

A user reported this problem.  I verified that it is real for the first of the resources indicated.  Suspicion is that this is related to Python 3 upgrade
This morning around 11 am, as ~ 15 CAS project members tried to access two hydroshare resources, the resources showed multiple copies of the same folder (see below). This issue is even worse now for the Wildfire group (16 folders named Economic Analysis and 9 folder named Fire Analysis).
Cohort 1 - Wildfire - https://www.hydroshare.org/resource/c063e0d244744d298428ea17e3a93b69/
Cohort 2 - Utah Ski Areas - https://www.hydroshare.org/resource/f528f92d8a47464d906058dd2882ba7c/
There was only 1 instance of each folder yesterday. Not sure how to resolve.

Code fix for this issue has been deployed, so closing this issue.


After migrating from 0.72.8 to 0.73.6 having following error

any leads?

any leads?

Will be fixed within next week

I have updated rn version to 0.74.5 and issue is gone


Results in json format Map<String, dynamic>

@Kerego I was thinking if we save the jsons as Map, in the models and use getters for each of the Json keys.
In this way anyone can use the Maps only instead of the predefined class formats if they wish to.

Hi @Akash98Sky,
I am probably missing a point here, but I'm not sure what is the use case of this.
The original idea of the library was to transform some of the oddities in the TMDB API's data into something more useful and easier to use from an app developer perspective.
Using Maps directly would be kinda equivalent to doing HTTP requests directly without using the library at all.

Yeah it's fine. But if we add Map with getters for its keys. Then others can just use it as they wish. I mean it would be a good way to get json formats of data. If anyone wishes to use. And also the objects if needed.

Ok, now I see, this could be helpful in offline scenarios when the app needs to save some amount of data locally and show it if there is no internet connection or when the API doesn't provide a way to access multiple movie details in a single request (something like favorites, or watchlist).
I think this would be a great addition to the library, great idea @Akash98Sky.


Console support

It would be really cool, if I could pipe some strings into Hex Fiend via the console. You know for some GUI tools e.g. with TextMate you can e.g. nvram -p | mate to load the nvram to your editor or any other text. I have only experience in augmented reality and games development and not so much system applications development. I could do this by myself If I would know how this interface’s name is. Is the pipe used automatically like a launch parameter?
I think an install button in the settings would work well

. This is also how Github and TextMate do this. :)

Just posted a new beta with this functionality:
https://github.com/ridiculousfish/HexFiend/releases/tag/v2.10b5
(@nneonneo)

cmd | hexf works great - thanks for the quick feature implementation!


Understand the basic flow of Electron Js

Grasp the Basics of the ElectronJS.
Installed the locally using node package manager & create a applications.

Exploring the basics of electronjs with creating dummy application.

Understand the basic flows and integrated with PouchDB.

Defunct.


fix(k8s) correct link to kustomize based for k4k8s

@hbagdi , not urgent, but while we wait for the all-clear, could you please resolve conflicts?

@h3xar0n  ping for merge


Fixed usage of beacon GUID.

Changes Unknown when pulling 9d4d5dc6e50b4557c5c2e4b6e67cab35cc3264ef on Fraser999:fix_guid into ** on dirvine:master**.

Reviewed files:

src/beacon.rs @ r1
src/connection_manager.rs @ r2
src/tcp_connections.rs @ r2

Comments from the review on Reviewable.io


Typo on Push Notifications Subscribing a User Page: "strinigify"

"Strinigify" should probably be "stringify".
https://github.com/google/WebFundamentals/blame/master/src/content/en/fundamentals/engage-and-retain/push-notifications/subscribing-a-user.md#L302

@juniperbelmont  Fixed by https://github.com/google/WebFundamentals/pull/4646
Ticket can be closed.


Keycloakify v10 unable to test in Keycloak container

This is a continuation of https://github.com/keycloakify/keycloakify/pull/538#issuecomment-2203941056. I didn't want to pollute that PR any further!
When running latest starter template within Keycloak docker (e.g. npx keycloakify start-keycloak) it just spits out a blank page with the following error:

You've modified the configuration of the Keycloak server in a way that is incompatible withthis test application.

...and contains the following in the console:

[Error] Not allowed to request resource
[Error] Fetch API cannot load http://localhost:8080/realms/myrealm/.well-known/openid-configuration due to access control checks.
[Error] OIDC initialization error: Bad configuration. Timed out after 5000ms
Maybe something to look into? I couldn't see anything in the config that would cause that.

I've validated port 8080 is open and the Keycloak container is correctly binding to it.
This is on macOS 14.5. Using yarn 1.22 since no version is specified in package.json and hence corepack uses that by default.

Damn this is the exact same config I'm using...
Are you on apple Silicon?
Can we jump on a quick call on discord to see what's up?
https://discord.gg/mJdYJSdcm4

Oh wait, I can reproduce with safari

@garronej it's Safari vs Chrome 🤣 I just tried it in Chrome and it works. Safari must be more restrictive regarding CORS or redirect URL's or some such thing.

Oh wait, I can reproduce with safari

lol..yep!

It's a security feature of safari. I'll try and see if I can go around it, it should work with other browsers though.
And it goes without saying that this problem only affect the test app that redirects to your locally running keycloak test instance.

Damn... there's no way around it :( to make it work on safari I'll have to spin another server locally just for this test app.

can you confirm that it works with Chrome and Firefox?

Well I've updated https://github.com/keycloakify/my-theme.keycloakify.dev/ so that it display an alert when using Safari.

It's not ideal but the Safary security policies being what they are the only workaround would be to to locally serve keycloakify/my-theme.keycloakify.dev when running npx keycloakify start-dev so I'll settle with the alert at least for now.

Thanks @garronej! This seems like a good enough solution. Glad we were able to figure out the cause!

Thanks for helping me figure this out!


Add CONTEXT:NOTES to test file for metadata; rename test file altitude.json

This pull requests serves two purposes:

add CONTEXT:NOTES to test file (see PR #787)
rename the test file altitude.json to sync with the naming in the simulation model repository reference_point_altitude.json - there is no need to review this file, this is done in https://github.com/gammasim/simulation_model/pull/4 - here we have a copy of this file.

Following tests cannot run successfully due to the renaming:

tests/unit_tests/utils/test_general.py::test_collect_data_from_http (it looks for the new file reference_point_altitude.json in the simtools main branch, which will be there after merging of this PR; see the successful test when given this branch name temporarily

Related to #789 (but it doesn't close that issue)

You asked for a review but it's still marked as a draft?

@orelgueta - you requested the test, now it is your review...
Note again that it is expected that one of the unit tests fails, see comment above.

CONTEXT is validated with the json schema - e.g., with the integration test in tests/integration_tests/config/validate_file_using_schema_json_input_test_meta.yml or with the tests in ./unit_tests/data_model/test_metadata_collector.py.
I think we can then assume safely that the yaml or astropy table readers are reading the dictionary key/values correctly.
Or do you mean something completely different?

No, that's what I meant, all good!


Fix package packages.yml name

Are you a current Fivetran customer?
John Ferlito, Co-Founder, Gladly
What change(s) does this PR introduce?
Use the new package name
Did you update the CHANGELOG?

No, not releaserelated

Does this PR introduce a breaking change?

[ ] Yes (please provide breaking change details below.)
[X] No  (please provide an explanation as to how the change is non-breaking below.)

Did you update the dbt_project.yml files with the version upgrade (please leverage standard semantic versioning)? (In both your main project and integration_tests)

No, doesn't need a release

Is this PR in response to a previously created Bug or Feature Request

[ ] Yes, Issue/Feature [link bug/feature number here]
[X] No

How did you test the PR changes?

[ ] CircleCi
[X] Local (please provide additional testing details below)

Tested by editing packages.yml on my repository
Select which warehouse(s) were used to test the PR

[ ] BigQuery
[ ] Redshift
[ ] Snowflake
[x] Postgres
[ ] Databricks
[ ] Other (provide details below)

Provide an emoji that best describes your current mood
:hamster:

@fivetran-joemarkiewicz Thanks, updated.


T1- Remove resume tab

Remove the 'Hire Someone' tab. No resumes have been uploaded, and it's not being utilized.

Great

Deployed to Heroku - @sherrimitchell


etesync-dav: fix build

Description of changes
This pull request fixes etesync-dav and in the process updates one of it's dependencies, etebase ( 0.31.5 -> 0.31.6 ).  In etesync-dav the werkzeug override was removed since it was causing the build to fail and it was not necessary. Unfortunately falsk-wtf override is still needed. But the current patches do not apply to it, so they where removed.
Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

closing bc of duplicate here https://github.com/NixOS/nixpkgs/pull/205675


fwts: 18.03.00 -> 18.05.00

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/fwts/versions.
These checks were done:

built on NixOS
/nix/store/v5wy7231jv43gnni4s3jcq0lz1qx21bs-fwts-18.05.00/bin/fwts passed the binary check.
Warning: no invocation of /nix/store/v5wy7231jv43gnni4s3jcq0lz1qx21bs-fwts-18.05.00/bin/kernelscan had a zero exit code or showed the expected version
1 of 2 passed binary check by having a zero exit code.
0 of 2 passed binary check by having the new version present in output.
found 18.05.00 with grep in /nix/store/v5wy7231jv43gnni4s3jcq0lz1qx21bs-fwts-18.05.00
directory tree listing: https://gist.github.com/8fb4995cd885cdeea7a35d51b7edca3b
du listing: https://gist.github.com/8cc61b948b8e0aa4a1a8088464c5536d

meta.description for fwts is: '"Firmware Test Suite"'.
cc @tadfisher for testing.
Experimental: this build is cached with Cachix. To use the cache follow these experimental instructions:
One time setup in nixpkgs Git checkout:
cachix use r-ryantm
git remote add r-ryantm https://github.com/r-ryantm/nixpkgs.git

Test this build:
git fetch r-ryantm && git checkout c05d12f0ec7b3e640bfb46fcfcdeabe8d312333e && nix-shell --pure -I nixpkgs=. -p fwts

Success on x86_64-linux (full log)
Attempted: fwts
Partial log (click to expand)
shrinking /nix/store/v5wy7231jv43gnni4s3jcq0lz1qx21bs-fwts-18.05.00/lib/fwts/libfwts.so.1.0.0
shrinking /nix/store/v5wy7231jv43gnni4s3jcq0lz1qx21bs-fwts-18.05.00/lib/fwts/libfwtsacpica.so.1.0.0
shrinking /nix/store/v5wy7231jv43gnni4s3jcq0lz1qx21bs-fwts-18.05.00/bin/fwts
shrinking /nix/store/v5wy7231jv43gnni4s3jcq0lz1qx21bs-fwts-18.05.00/bin/kernelscan
gzipping man pages under /nix/store/v5wy7231jv43gnni4s3jcq0lz1qx21bs-fwts-18.05.00/share/man/
strip is /nix/store/21ymadblbmsbb2bk4q7gl4kjasp8zmgd-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/v5wy7231jv43gnni4s3jcq0lz1qx21bs-fwts-18.05.00/lib  /nix/store/v5wy7231jv43gnni4s3jcq0lz1qx21bs-fwts-18.05.00/bin
patching script interpreter paths in /nix/store/v5wy7231jv43gnni4s3jcq0lz1qx21bs-fwts-18.05.00
checking for references to /build in /nix/store/v5wy7231jv43gnni4s3jcq0lz1qx21bs-fwts-18.05.00...
/nix/store/v5wy7231jv43gnni4s3jcq0lz1qx21bs-fwts-18.05.00

Success on aarch64-linux (full log)
Attempted: fwts
Partial log (click to expand)
shrinking /nix/store/zq085hbyp8r6gvpyayn93p0rfik1s42z-fwts-18.05.00/bin/fwts
shrinking /nix/store/zq085hbyp8r6gvpyayn93p0rfik1s42z-fwts-18.05.00/lib/fwts/libfwtsacpica.so.1.0.0
shrinking /nix/store/zq085hbyp8r6gvpyayn93p0rfik1s42z-fwts-18.05.00/lib/fwts/libfwts.so.1.0.0
shrinking /nix/store/zq085hbyp8r6gvpyayn93p0rfik1s42z-fwts-18.05.00/lib/fwts/libfwtsiasl.so.1.0.0
gzipping man pages under /nix/store/zq085hbyp8r6gvpyayn93p0rfik1s42z-fwts-18.05.00/share/man/
strip is /nix/store/qg2agrqkf240s656d207zqhipl0bc2id-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/zq085hbyp8r6gvpyayn93p0rfik1s42z-fwts-18.05.00/lib  /nix/store/zq085hbyp8r6gvpyayn93p0rfik1s42z-fwts-18.05.00/bin
patching script interpreter paths in /nix/store/zq085hbyp8r6gvpyayn93p0rfik1s42z-fwts-18.05.00
checking for references to /build in /nix/store/zq085hbyp8r6gvpyayn93p0rfik1s42z-fwts-18.05.00...
/nix/store/zq085hbyp8r6gvpyayn93p0rfik1s42z-fwts-18.05.00

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: fwts
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.


Vimeo show only black layer

[x] Issue does not already exist
[ ] Issue observed on https://plyr.io

Expected behaviour
Vimeo player shwoing only black layer no play icon etc
Actual behaviour
only showing black overlay for player
Environment
android

Browser:
Version:
Operating System:
Version:

Players affected:

[ ] Vimeo

Steps to reproduce

Relevant links

Could you be more vague, perhaps include less information for me to reproduce?

Hello SamPotts,
Video player is working for mp4 video and youtube also but for vimeo its no loading iframe (it load for youtube ) please check my screenshot for this


Conduct an impact analysis of Inbound SMTP DANE with DNSSEC for Exchange Online

💡 Summary
Microsoft announced support in Exchange Online for two security standards: DNS-based Authentication of Named Entities (DANE) for SMTP and Domain Name System Security Extensions (DNSSEC). The scope of this issue is to:

[ ] Understand the new EXO features as described in the documentation

[ ] Perform a hands-on experiment with the new features

[ ] Should Scuba create a new policy or update an existing policy that includes the new features?

[ ] Can a policy check be codified in ScubaGear?

For reference: https://techcommunity.microsoft.com/t5/exchange-team-blog/announcing-general-availability-of-inbound-smtp-dane-with-dnssec/ba-p/4281292


Can not determine the module class x Component in location/x.component.ts add xcomponent to Ng Module to fix it. Angular 4

I am not on the production phase on my web ... the project is working good ... I used
ng serve --o
ng build

and it is working great .... then I tried :-
ng build --prod

this error appeared
 Cannot determine the module for class CategoriesComponent in C:/project/src/app/Components/categories/categories.component.ts! Add CategoriesComponent to the NgModule to fix it.

I know that I made a mistake ... I made 2 components with the same name but I removed the wrong one.
and here is the code of app.Module.ts file :-
    import { BrowserModule } from '@angular/platform-browser';
import { NgModule } from '@angular/core';
import { RouterModule , Routes } from '@angular/router';

import { FormsModule } from '@angular/forms';
import { FlashMessagesModule } from 'angular2-flash-messages';

import { AngularFireModule } from 'angularfire2';
import { AngularFireDatabase } from 'angularfire2/database';
import { AngularFireAuth } from 'angularfire2/auth';

import { AppComponent } from './app.component';
import { OrdersComponent } from './Components/orders/orders.component';
import { ItemsComponent } from './Components/items/items.component';
import { NavbarComponent } from './Components/navbar/navbar.component';
import { LoginComponent } from './Components/login/login.component';
import { RegisterComponent } from './Components/register/register.component';

import { OrdersService } from './services/orders.service';
import { AdditemsService } from './services/additems.service';
import { AddcategoriesService } from './services/addcategories.service';
import { LoginService } from './services/login.service';
import { RegisterService } from './services/register.service';
import { AddresturantService } from './services/addresturant.service';

import { AllordersComponent } from './components/allorders/allorders.component';
import { CategoriesComponent } from './components/categories/categories.component';
import { RestaurantsComponent } from './Components/restaurants/restaurants.component';

const appRoutes: Routes = [
  {path: '', component: OrdersComponent},
  {path: 'register', component: RegisterComponent},
  {path: 'login', component: LoginComponent},
  {path: 'items', component: ItemsComponent},
  {path: 'categories', component: CategoriesComponent},
  {path: 'restaurants', component: RestaurantsComponent}
];

export const firebaseConfig = {

};

@NgModule({
  declarations: [
    AppComponent,
    OrdersComponent,
    ItemsComponent,
    NavbarComponent,
    LoginComponent,
    RegisterComponent,
    AllordersComponent,
    CategoriesComponent,
    RestaurantsComponent
  ],
  imports: [
    BrowserModule,
    FormsModule,
    FlashMessagesModule,
    AngularFireModule.initializeApp(firebaseConfig),
    RouterModule.forRoot(appRoutes)
  ],
  providers: [
    AngularFireDatabase,
    AngularFireAuth,
    OrdersService,
    AdditemsService,
    AddcategoriesService,
    LoginService,
    RegisterService,
    AddresturantService
  ],
  bootstrap: [AppComponent]
})
export class AppModule { }

I removed the component that was wrong and left the right one.
What shall I do to make the production accept these components !
any suggestions ?

I too am experiencing this problem.
We are using 1.5.0 for the CLI on Windows 10 x64

Subscribing. I've encountered the same issue with ng build --prod, but not on ng serve. See this thread, too: https://github.com/angular/angular/issues/13590

i have resolved this issue by removing multiple component classes with the same name.

I have fixed it just by matching the import statement with casing on the file name.

Thx. I had the same problem with also was caused by file casing

My component was not in app.module.ts declarations. (Thought it would be excluded though.)

I don't have multiple class with the same name and casing also is fine but still, I am getting this error.

My component was not in app.module.ts declarations. (Thought it would be excluded though.)

this fixed it for me as well. The component was not included in the app.module.ts file imports

I also having the same error:
ERROR in : Cannot determine the module for class CCURLActionComponent in C:/Users/HP/Desktop/default-2/default/src/app/content/pages/header/action/aslaAction/aslaActionURL/asla-url-action.component.ts! Add CCURLActionComponent to the NgModule to fix it.
how to solve this error.

I also resolved this by fixing casing in an import statement. However, in my case the casing error was not in the app.module.ts file, but in one of the guards. So be sure to check the import casing in ALL the ts files in the project!

I have the same error but I don't have any duplicate's and using the same file naming convention everywhere. I am lazy loading my components so they are not in the app.module

I had the same error because I changed the folder name (upper case) to (lower case). It was working fine with ng serve and ng build but give error when I tried to build for production.
I change the folder name in import statement on module file and it fixed the issue.

I had the same problem, Folder name casing was the reason for this .

solved this issue by removing a duplicate of same component

I have the same issue with an Abstract component.

I still have this issue. I created another project and add only the components which giving this error and guess what?! Still same issue.
I even switched the components name to A,B, C and D, still same issue. Why always angular build in production mode it's painful? Every time when I add an new component it's same issue and after some time I try build with prod randomly and works. What's the problem with angular?

User has added CategoriesComponent in two place means two different file have same registration in module. First search and delete one place entry and rebuild again for pointing to prod
Error : Cannot determine the module for class CategoriesComponent in C:/project/src/app/Components/categories/categories.component.ts! Add CategoriesComponent to the NgModule to fix it.
100% working for me

One more possibility: My issue was I renamed a folder lowercase to match the paths. For reasons beyond my expertise, the folder "appeared" to be lowercase, but with a fresh clone of the git repository, that folder rename never was applied other than visually on my system.


How to add space when insert?

For example, when I select two words, like 'abc', 'abc', first I press v, and press i to enter an insert mode, then I input ab cd,but I cannot input the space character. By the way, when I input b, or k, or something else, it will raise an error like:
Error detected while processing function <SNR>107_process_user_input

and
E488: Trailing characters

What's wrong with my vim env? Thanks very much

I'd suggest to isolate the source of the problem first. Disable all other plugins, minimize your ~/.vimrc and try it again. There might be some conflict with another plugin (it happened to me before) or a keybinding (use :map to see all your keybindings).

please look at this gif, I just use the very original vimrc file which was generated by the NeoBundle, and I have searched all my map keys, it seems just ok, so can you help me?

thanks, and I have install the kristijanhusak/vim-multiple-cursors version, and it works now

@msyesyan this repo is synced with my fork several months ago, and not updated since then. So this should work properly here. Maybe some later PR broke it.

@kristijanhusak yes, I think so, I will maintain attention on it, thanks very much

@msyesyan any progress?

I am now seeing this issue, come about within the last 2 weeks for me

Went back until it started working again and it looks like this is the PR that introduced the issue:
https://github.com/terryma/vim-multiple-cursors/pull/110

@garbelini @guyfedwards @msyesyan Please provide a reproducible minimal vimrc.

@balta2ar I solved this by updating my vim to 7.4, cheers


Update Cohere

This PR

Fixes cohere command by removing the unnecessary "template".
Adds retries to the cohere wrapper
Adds support for calling cohere in "chat" mode, effectively similar to the long preambles added to some other models.

Thanks @sanderland. That all looks good, I evaluated the outputs with both GPT4 and claude, and performance increased by ~7 percentage points. Although the performance for both the chat and the command models are surprisingly nearly the same... I'm not sure if that's also what you have found
Note that I didn't rerun the generations!
Once you make the minor change above I can merge the PR and update the leaderbaord

Will double check for your question. We can also just have one of them, depending on what this benchmark is focused on.

@YannDubs Code and generations seem fine, all good to merge. I can't run the eval, but would expect the chat mode to give slightly longer generations. It's the same model though, so it depends on how strongly the evaluator likes chattiness.

thanks it seems pretty robust to that choice given that the results are nearly the same. I'll add both given that I already ran the eval! Thank you

updated the main leaderboard with both models.


Add A-Z option to "Sort by" on listings page

Hi @smanivasag - can you review this please.

Hi @Raq-HEE - The chosen sortBy option isn't being retained when interacting with (Category, Group Impacted, etc) Filters. Could this be fixed ?

Hi @Raq-HEE - While testing the PR, have observed the following which are seem to be existing issues:

Selected sorting order (sortBy) isn't being retained on EventListing page.
Strategy document link/URL generation isn't working correctly for SearchBank listing page.

Hi @Raq-HEE - While testing the PR, have observed the following which are seem to be existing issues:

Selected sorting order (sortBy) isn't being retained on EventListing page.
Strategy document link/URL generation isn't working correctly for SearchBank listing page.

Have pushed the following commits to address the issues described above:

Selected sorting order (sortBy) isn't being retained on EventListing page: c5dc911867953184e40bd2ac28b1f5c5aaa77934
Strategy document link/URL generation isn't working correctly for SearchBank listing page: c5dc911867953184e40bd2ac28b1f5c5aaa77934

Hi @Raq-HEE - The chosen sortBy option isn't being retained when interacting with (Category, Group Impacted, etc) Filters. Could this be fixed ?

Have pushed 168afcf9f0f8484dd56f358adb52612c00d96727 to address the issue described above, thanks


v0.14.4 upgrade

This gets the code compiling with the newest terraform libraries.
In general it appears to create the local file properly, but I could not actually get terraform to respect the lock with a local state file.
Might try to test it with S3 and Dynamo DB when I get a moment. My guess it that there is now a bit more logic on determining wether the lock file is still valid.

@spkane - Just curious if you knew of any work left here. I tested this with a rather simple S3 and DnyamoDB lock setup and it seems to work. I'd be interested in helping if I can.

@jaredledvina As far as I know this did the job, but that work was all the time I had to spend on it. I think this project is dead, but this could be merged in if indeed it is both complining and working with current releases.

Ah great, yeah worked for me with the S3 state and DynamoDB lock setup on 0.14.10 on Friday actually.
@minamijoyo if you happen to still maintain this, it'd be great to see it merged in and I'm happy to help test it further if you would like to see anything specifically verified. Thanks for the project!

@spkane @jaredledvina Thank you for your work.
@jaredledvina Could you share you use-case if possible? Because I originally wrote the tflock for refactoring, but now I'm using the tfmigrate for it. I'm just curious when the tflock useful.


msbuild could not loacte on ubuntu

msbuid in ubuntu is subcommand, which cound not locate.
dotnet msbuild your.csproj

system
dotnet 7.0
vim9
https://github.com/OmniSharp/omnisharp-roslyn/releases/download/v1.39.10/omnisharp-linux-x64.tar.gz

:OmniSharpOpenLog
[info]: OmniSharp.Stdio.Host
        Starting OmniSharp on ubuntu 22.4 (x64)
[info]: OmniSharp.Services.DotNetCliService
        Checking the 'DOTNET_ROOT' environment variable to find a .NET SDK
[info]: OmniSharp.Services.DotNetCliService
        Using the 'dotnet' on the PATH.
[info]: OmniSharp.Services.DotNetCliService
        DotNetPath set to dotnet
[info]: OmniSharp.MSBuild.Discovery.MSBuildLocator
        Located 0 MSBuild instance(s)

:OmniSharpInstall v1.35.2 it works

@rainumdo The net6.0 builds of OmniSharp will work with the .NET SDK. It looks like you had installed the Framework version which requires Mono and MSBuild on non-windows platforms.


Consider refactoring the tree API to use key/value

Currently, the #find operation takes an entire object, even if the comparer only uses a piece of the object.  Consider refactoring this to use just a key to find a node.
For example, say we have the following type as the data type for a tree:
interface ITest {
    member1: number;
    member2: string;
}

function testComparer(a: ITest, b: ITest): number {
    return a.member1 - b.member1;
}

Perhaps the only member used in the comparer is #member1.  This would be considered the key, while the entire object would be the value.  To search for the node containing a specific object, the current API requires a full object passed to #find:
tree.find({ member1: 3, member2: 'this can be anything during find, since the comparer only considers #member1 during lookup'});
Consider refactoring #find such that it only requires the 'key' during lookup:
tree.find(3);

This would likely require a second templated argument throughout the codebase, and would also be a major breaking change.  Rather than IBinaryTree<T>, the base signature might be something like IBinaryTree<K,V>.  Given the example above, an invocation might look like new BinarySearchTree<number, ITest> rather than the current new BinarySearchTree<ITest>.

This would also likely require refactoring the signature of and use of an IComparer<T>.


shared storage limit

Signed-off-by: Mikhail Boldyrev<EMAIL_ADDRESS>

Description of the Change
A set of classes providing a shared limit between several storages.

Benefits

Possible Drawbacks

Usage Examples or Tests [optional]
please refer to storage_shared_limit_test: https://github.com/MBoldyrev/iroha/blob/wip/mst-shared-limit/test/module/libs/storage_shared_limit/storage_shared_limit_test.cpp

Alternate Designs [optional]

May be reopened later when MST component is refactored.