Best way to tag alerts

Hello all,
Some folks here have alot more experience with ElastAlert than I do, would like to know the best way to tag alerts.
For the diff categories of alerts (high, medium or low). Im looking for a way to assign these categories in form of tags if possible. So in my elastalert index in ES, ild be able to sort alerts in these categories.
Thanks,

Use enhancements to add custom fields to your alert depending on the context.
As an example, you can add "PRIORITY" custom field and then sort by it:
# AWS_AccessViolation_RootCredentialsUsage
class aws_accessviolation_rootcredentialsusage(BaseEnhancement):
    def process(self, match):
        match['PRIORITY'] = "HIGH"

More about enhancements here:
https://elastalert.readthedocs.io/en/latest/recipes/adding_enhancements.html

Thanks for this info @nickbabkin. Would try this out

Use enhancements to add custom fields to your alert depending on the context.
As an example, you can add "PRIORITY" custom field and then sort by it:
# AWS_AccessViolation_RootCredentialsUsage
class aws_accessviolation_rootcredentialsusage(BaseEnhancement):
    def process(self, match):
        match['PRIORITY'] = "HIGH"

The match only matches the field in the match_body field, and it will change the original source from the hits.


Server storage is filled with cache data

Pulse Version
1.0.0
Laravel Version
10.4
PHP Version
8.2
Livewire Version
3.0.2
Database Driver & Version
mysql 8
Description
Pulse if filling the server with a lot of files and cached data for no obvious reason , this is causing the server to run out of space

Steps To Reproduce
visit laravel pulse url (localhost:8000/pulse) and monitor the  storage/framework/cache/data directory , you will find that the content of this file is duplicated each refresh

Hi @Hegabovic, I'm not sure which specific beta version of Pulse you're on, so could you first please try the latest version of Pulse (v1.0.0-beta7), which will also require you to update to Livewire 3.2.

hello , i'm using pulse version  >> v1.0.0-beta7 , and i find that these cache files are coming when i run the command php artisan pulse:check , this command fills the server with too many cache files until the server goes down eventually

Thanks. I can confirm the issue when using the pulse:check command with the file cache driver. The cache locks it creates have a 5-second expiry, but the file cache driver does not automatically purge expired entries as other cache drivers do.
We're revisiting how this works and will hopefully have an improved solution soon.

This should be fixed when #260 is merged and tagged.

v1.0.0-beta8 has been tagged.

@jessarcher How much cache storage space is reasonable for Pulse to use? I'm using v1.0.0-beta8 and after a week my cache folder is almost 1 GB already. And this is in an application without much activity.


Some little deriving cleanups

See each commit for details.
r? @emilio

:umbrella: The latest upstream changes (presumably #1003) made this pull request unmergeable. Please resolve the merge conflicts.

:pushpin: Commit 337fbb4 has been approved by emilio

@bors-servo r+

:hourglass: Testing commit 337fbb40ba6525c4e021ac325d119424692d332d with merge c1aef6357a873f8b45cdb490c30dd3bfa3314661...

:sunny: Test successful - status-travis
Approved by: emilio
Pushing c1aef6357a873f8b45cdb490c30dd3bfa3314661 to master...


Newsletter-134:Translate into Japanese

@AkioNak if you have time to review, let me know. Otherwise we can move forward without the content review.

@bitschmidty Sure, I will review.

Thanks @AkioNak! I fixed.

@azuchi @bitschmidty It looks good to me.

Merged! Thank you once again @azuchi and @AkioNak !


copy / paste not work if strings contains 'NUL' 0x00

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.68.1
OS Version: Windows 11 21H2

Steps to Reproduce:

Select some strings that contains 0x00 , e.g.

copy it & paste it at other tab.

got

Is the first view a terminal? What about the tab you paste it in?

No, not a teminal.
Copy from editor, and paste to ediotr.
I mean:

This is a well known limitation of the Windows clipboard -> https://superuser.com/a/1071346


Improve support for suffixed packages

[x] I have added an entry to docs/changelog.md

Summary of changes
This change allows for safe listing and upgrade of packages installed with a suffix. As part of this change, a new metadata property "suffix" has been introduced.
Test plan

Tested by running
pipx install --suffix=_test pycowsay
pipx upgrade pycowsay_test
pipx inject pycowsay_test pip
pipx list
pipx uninstall pycowsay_test

@itsayellow is there any further changes required for this one?

@itsayellow are there any further changes required for this one?

Still working on it.  With unpaid volunteer labor you need to be patient. 🙂

Still working on it. With unpaid volunteer labor you need to be patient.

Well aware of those pains, was not intending to push for resolution. Just making sure to dot the i's and cross the t's. :)

Oh my gosh, so currently it looks like parts of pipx are actually broken when using packages with a suffix?  I had no idea.  This is less of an "improvement" and more of a necessary bugfix!

@abn Thank you for the PR. I looked it over and it looks good to me -- I have no comments. It is rare to see no lint errors, unit tests passing AND new unit tests all in a single commit. Impressive!
I'll wait for @itsayellow's review before merging since he wrote the metadata code and knows it better than me.

Oh my gosh, so currently it looks like parts of pipx are actually broken when using packages with a suffix? I had no idea. This is less of an "improvement" and more of a necessary bugfix!

Yeah I was kind of surprised that these changes were needed, though I'm glad they were; they seem like basic features of the suffix functionality.

@itsayellow ah yes, it is broken. I figured you were aware of this ... limitation of the current implementation. I recently started using pipx quite regularly and is finding the suffix feature rather useful for triage/testing the cli tool I help out with. That is what initiated the fix. :)
@cs01 I think I had a lint failire on my inital push ... so not all clean :wink:

Let me know if there's something I'm missing and this isn't possible in all cases, but from my read I think what I said can be done.
@itsayellow  see my response for why I ended up doing that. TLDR; upgrade of injected packages was not working as expected.

@cs01, there's some policy questions here that I'm curious for your thoughts about.
My thoughts:

Only one suffix per venv
Only the main package and its apps get the suffix (not injected packages + their apps)
Should --include-deps apps also get the suffix?

Assuming that the included apps are exposed to path, I'd suggest we should allow suffix configuration there too.
I do currently have a use case where a certain pip version is a dependency that gets injected and would like to expose multiple versions from different environments. But this suffix might differ from the main package suffix. I appreciate this is not in scope for the PR, but wanted to mention this for the policy decision.

I do currently have a use case where a certain pip version is a dependency that gets injected and would like to expose multiple versions from different environments. But this suffix might differ from the main package suffix. I appreciate this is not in scope for the PR, but wanted to mention this for the policy decision.

In this case, why would the pip suffix need to differ from the main package suffix?

My rationale for a simple policy regarding suffixes right now, is that it's already rippling through the code, and absorbing a simple pervasive change now and incrementally improving/expanding it later will be easier (and hopefully more successful) for implementation.  Also, a more complicated system of suffixes would be hard to explain/document from a user perspective.
I am sensitive to how useful a more powerful/expansive approach of suffixes could be, but there is a tradeoff between power and complexity.

@cs01, there's some policy questions here that I'm curious for your thoughts about.
My thoughts:

Only one suffix per venv
Only the main package and its apps get the suffix (not injected packages + their apps)
Should --include-deps apps also get the suffix?

Also, a more complicated system of suffixes would be hard to explain/document from a user perspective.

We need to consider first whether the feature can be understood and supported by part time volunteers, and second if a significant portions of users would use the feature.
pipx has been slowly accreting new features, and each new feature adds significant complexity. Between inject, --include-deps, and metadata tracking, the codebase has become much more complicated. pipx is, IMO, very useful as it is, and this suffix feature, although pretty cool, is a bit of a corner case.
We should not sacrifice maintainability of the codebase for a feature that is not essential, especially since the project is maintained by part time volunteers. This is what happened to pipenv; its complexity became overwhelming and the project suffered.
At some point, users who want such specific features need to just make a venv and bash script instead of shoehorning it all into pipx. IMO the only way the suffix feature can work and pipx can remain viable is if the feature and implementation is kept extremely simple. I am fine not supporting suffixes at all, or only supporting them with functionality that is reduced but maintainable and easily documented. Maybe that's just me be being selfish because I'm perfectly happy with pipx as it is and don't want increased maintenance burden.

Only one suffix per venv
Only the main package and its apps get the suffix (not injected packages + their apps)

I'm fine with these limitations.

Should --include-deps apps also get the suffix?

If --include-deps is used, and the same package was already installed with a different suffix, there will be name collisions if a suffix is not added to the apps of the dependent packages. So I think from a user perspective there has to be. I just wonder how hard this will be from a maintainer's perspective.
Maybe a simpler way to accomplish this and remove limitations is to symlink an entire folder with the suffix name, like black_suffix in the bin dir. Then users can run black_suffix/black from the command line.

What if we described suffixes as "experimental and subject to possible change" in both the help and docs?

What if we described suffixes as "experimental and subject to possible change" in both the help and docs?

That sounds like a good idea since things are in flux.

@cs01 just to add to the discussion, the suffix feature does not need to be complex. From my perspective, simply ensuring the main package is the only one that can be suffixed is good enough to reduce unnecessary complexity.
The reason why I turned to pipx was this particular feature for what it is worth. This makes using multiple versions of python tools in the same environment a breeze. And I do sincerely hope that this feature remains, albeit with possible caveats.

@cs01 just to add to the discussion, the suffix feature does not need to be complex. From my perspective, simply ensuring the main package is the only one that can be suffixed is good enough to reduce unnecessary complexity.
The reason why I turned to pipx was this particular feature for what it is worth. This makes using multiple versions of python tools in the same environment a breeze. And I do sincerely hope that this feature remains, albeit with possible caveats.

I think that's a good approach.
To summarize what @cs01 and I (and I believe @abn 🙂)  agree about:

One suffix only per venv
Suffix is applied to main package only
Suffix is applied to apps of main package
Suffix is applied to main package's dependencies' apps if --include-deps is used to install main package

Hopefully with this approach there is an implementation that keeps code complexity down.

As a minor side note:

Maybe a simpler way to accomplish this and remove limitations is to symlink an entire folder with the suffix name, like black_suffix in the bin dir to the venv's bin dir. Then users can run black_suffix/black from the command line, and pipx doesn't have to do anything complicated other than create a venv and install to it.

Does this work?  I couldn't get <subdirectory>/<app> in a PATH directory to work for me in zsh.

Does this work? I couldn't get <subdirectory>/<app> in a PATH directory to work for me in zsh.

I just tried it myself and it doesn't work. I assumed you could access folders on your PATH, but that doesn't seem to be the case.

Oops - I just noticed this PR - I made the initial suffix PR (#445) but I clearly didn't consider the impact enough (e.g. pipx list, etc).
Thank you for fixing this @abn :)

@cs01 @itsayellow can we tag a new release with this fix in please? Seems like there isin't a new one yet.


Match all the blastn options used in pyani v0.2 - Issue 13 fix

Follow on to address my oversight on PR #101 to resolve #13, spotted as part of work on #102 when the new matrices didn't quite match those from pyANI v0.2.
Type of change

[x] Bug fix (non-breaking change that fixes an issue)
[ ] New feature (non-breaking change that adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality not to work as expected)
[ ] This change requires a documentation update
[ ] This is a documentation update

Action Checklist

[x] Work on a single issue/concept (if there are multiple separate issues to address, please use a separate pull request for each)
[ ] Fork the pyani-plus repository under your own account (please allow write access for repository maintainers)
[x] Set up an appropriate development environment (please see CONTRIBUTING.md for this repository)
[x] Create a new branch with a short, descriptive name
[x] Work on this branch

[x] style guidelines have been followed (please see CONTRIBUTING.md for this repository)
[x] new code is commented, especially in hard-to-understand areas
[x] corresponding changes to documentation have been made
[x] tests for the change have been added that demonstrate the fix or feature works

[x] Test locally with pytest-plus -v non-passing code will not be merged
[x] Rebase against origin/master
[x] Check changes with linting/formatting tools before submission (please see CONTRIBUTING.md for this repository)
[x] Commit branch
[x] Submit pull request, describing the content and intent of the pull request
[x] Request a code review
[x] Continue the discussion at Pull requests section in the pyan-plus repository

Merging these changes now. Is it ok to delete the issue_13_fix branch?

Yes - I'm happy to have branches automatically deleted after merging into main. I struggle to think of a reason not to. Thanks.


[Task]: Analytics Events - RTS

@srix can you please move this either to your name, or to @ayushpahwa's

@srix can you please move this either to your name, or to @ayushpahwa's


Ability to Run Audit on HTTPS Protocol

Is your feature request related to a problem? Please describe.
This plugin appears to lack a setting to run audit against https protocol. This impacts our Best Practices score, and possibly other metrics of the audit.
Describe the solution you'd like
We have multiple sites running on a common codebase, so a setting to force https (or simply to have https be the default) would be great.
Describe alternatives you've considered
I did not see anything in the docs aside from an absolute URL option that would resolve this issue. Again, we serve multiple sites with a shared netlify.toml file, so I'm not sure an absolute URL of something like https://localhost would work, but I will try it.
Additional context
My suggestion would be to have the audit run on https by default. Suggested change in /src/lib/get-server/index.js:
Current
const server = {
    listen: (func) => {
      console.log(
        `Serving and scanning site from directory ${chalk.magenta(serveDir)}`,
      );
      return app.listen(port, host, func);
    },
    close: (instance) => instance.close(),
    url: `http://${host}:${port}`,
  };

Default HTTPS
const server = {
    listen: (func) => {
      console.log(
        `Serving and scanning site from directory ${chalk.magenta(serveDir)}`,
      );
      return app.listen(port, host, func);
    },
    close: (instance) => instance.close(),
    url: `https://${host}:${port}`,
  };

Thanks for filing this issue!
Unfortunately changing this text to https results in an error ERR_SSL_PROTOCOL_ERROR because the minimal server we are using is not "speaking" https when it serves up localhost. The goal to verify the lighthouse scores in an environment closer to production is however something we're currently working on, just in a slightly different way!
In future, you'll be able to choose to run your lighthouse audit on the actual live deploy URL (rather than the content served up internally on localhost). Do you think that would fulfil your use-case? If so, we hope to have a beta version available soon.

@aitchiss Thank you for the reply. Yes, I believe that would fulfill our use case. I would definitely be interested in the upcoming beta release!

Awesome! Let me close this issue for now, but I've linked it on our internal beta issue to remind us to give you a heads up when it's ready for early testing!

Hi @dsolanorush 👋  I'm happy to share that version 4.1.0 of the plugin allows you to enable an experimental version of the functionality I mentioned! This isn't ready for a full release yet, but if you'd like to help us test it out, all you need to do is:

Upgrade to v4.1.0 of the plugin
Enable the experimental functionality by either creating an environment variable LIGHTHOUSE_RUN_ON_SUCCESS='true', or adding the below input to your netlify.toml:

[[plugins]]
  package = "@netlify/plugin-lighthouse"

  [plugins.inputs]
    run_on_success = "true"

Once you've done this, the plugin will now run after your deploy is completed, and will run against the live deploy URL.
As I mention, this is still experimental at this time, but we'd happy to hear any feedback from some early testing!

Fantastic! I'm looking forward to trying this out. Thank you!
Cheers,
https://www.rushmarket.com/
Drey Solano
STAFF Software Engineer
technology
WWW.RUSHMARKET.COM https://www.rushmarket.com/
https://www.facebook.com/therushmarketomaha
https://instagram.com/therushmarketomaha
On Fri, Apr 14, 2023 at 4:33 AM Suzanne Aitchison @.***>
wrote:

Hi @dsolanorush https://github.com/dsolanorush 👋 I'm happy to share
that version 4.1.0 of the plugin allows you to enable an experimental
version of the functionality I mentioned! This isn't ready for a full
release yet, but if you'd like to help us test it out, all you need to do
is:

Upgrade to v4.1.0 of the plugin
Enable the experimental functionality by either creating an
environment variable
https://docs.netlify.com/environment-variables/overview/
LIGHTHOUSE_RUN_ON_SUCCESS='true', or adding the below input to your
netlify.toml:

[[plugins]]
package = @.***/plugin-lighthouse"
[plugins.inputs]
run_on_success = "true"
Once you've done this, the plugin will now run after your deploy is
completed, and will run against the live deploy URL.
As I mention, this is still experimental at this time, but we'd happy to
hear any feedback from some early testing!
—
Reply to this email directly, view it on GitHub
https://github.com/netlify/netlify-plugin-lighthouse/issues/546#issuecomment-1508229620,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUPH33BYYUFDOWWGBXGS52LXBEKYHANCNFSM6AAAAAAUPF7NQQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

@aitchiss - Just wanted to wanted to report that the plugin is now successfully running against live deploy URLs. Thanks again for getting this feature added so quickly 🙏

That's great news - thank you for confirming @dsolanorush! In the near future we'll be shipping a major version where we flip the "on success" behaviour to be the default, at which point you'll no longer need the extra settings I mentioned above, but I'm glad to hear you're unblocked for now!


refactor!: remove unused playerStateStream

Description
Remove unused player state stream. See this comment.
BREAKING CHANGE: But it should not play a role:

stream was never called, so it never emitted any events, (except for web, which also already emits onComplete event). So most likely no-one did listen to this stream.
the according stream is further exposed in main audioplayers package, so it's not breaking the main package.

Checklist

[x] The title of my PR starts with a Conventional Commit prefix (fix:, feat:, docs:, chore: etc).
[x] I have read the Contributor Guide and followed the process outlined for submitting PRs.
[x] I have updated/added tests for ALL new/updated/fixed functionality.
[x] I have updated/added relevant documentation and added dartdoc comments with ///, where necessary.
[x] I have updated/added relevant examples in example.

Breaking Change

[x] Yes, this is a breaking change.
[ ] No, this is not a breaking change.

Related Issues

#1257

Because if you use the interface directly the player state stream is not available anymore, but not for the main package. so for whatever reason you use the interface directly you have to alter your code, which is also published. But not if you use the audioplayers package, as expected.

@spydon do you think I can merge this?


Wrong coverage on Coveralls

ISO8601 at aeb5da75332954c9cd2f156edd8d8f83bbdef97e shows 100% coverage locally (via rake coverage), but it only shows 86% on Coveralls.

Re-ran a few times and still the old, wrong value: https://coveralls.io/builds/2667766

Having the same issue, this this might be due to a backlog in the coveralls processing queue: http://status.coveralls.io

Is this resolved now?

@marklarr it is for me—Coveralls appears to have resolved their queue backlog issues. Regardless, this isn't a slather issue.

@soffes I'll leave this for you to close out if you want

Fixed!


fixes missing default validation messages on FileUpload

Description
We encountered an unexpected behaviour in our running app after a composer update, so we investigated a little and found the origin in this PR: https://github.com/filamentphp/filament/pull/12772
The addition of custom validation messages on a FileUpload has broken the default validation messages thrown in a failing rule.
Code Example:

// App\Rules\TestRule.php
public function validate(string $attribute, mixed $value, Closure $fail): void
{
    $fail('default validation message');
}

// TestComponent.php
FileUpload::make('test')
    ->rule(new TestRule)

Current Behaviour
On submit the error message shown says 'App\Rules\TestRule'

Expected Behaviour
On submit the error message shown says 'default validation message'
Functional changes

[x] Code style has been fixed by running the composer cs command.
[x] Changes have been tested to not break existing functionality.
[x] Documentation is up-to-date.

This change fixes the validation message that also came with #12799 .
Currently, the error message given is reverted to Illuminate\Validation\Rules\File.

Thanks


$MDX delimiters in ocaml cut off any code on the same line

If I write code like this:
(* $MDX part-begin=something *)
type t =
  | Foo
  | Bar (* $MDX part-end *)

Then what shows up in the MDX is:
type t =
  | Foo

This cuts off | Bar. Granted, a solution is to always put the comment on a separate line. But ocamlformat doesn't know this, for example. It would be better if mdx always preserved all the code between delimiters.

Out of curiosity, does ocamlformat still format it this way if you had an empty line between | Bar and the comment?
I understand this is annoying but I'm wondering if from a user perspective, you really want inline part delimiters. If there's no way to get ocamlformat and MDX to agree on how this, we'll of course fix it in MDX but I'm wondering whether this is the formatting you actually want or if you'd also rather have it on a separate line.

@ceastlund Thanks for the report and the example. I'm currently trying to implement a reasonable solution to this problem. Could you specify a configuration where OCamlformat formats the comment on the end of the line? I'm playing around with source code like this:
(* $MDX part-begin=something *)
type t =
  | Foo
  | Bar
  | Baz
  | Quuz
  | Fnuug
  | Gbaz of { foo : int; bar : int; baz : int; bat : int }
  | Hoog
(* $MDX part-end *)

to get ocamlformat 0.21 to put the part-end on the same line as Hoog but with both the conventional and janestreet profiles it leaves it on its own line (the conventional profile puts types with less variants on one line but the part-end stays on a separate line. Unfortunately, there's a ton of flags so it would be good to have a reproducible case that we can reach out to the OCamlformat maintainers to find a solution that is both readable and doesn't drop lines silently.

I believe the case I've run into is when there's an [@@deriving] clause on a new line after the comment, and the comment is aligned with the "|" on the previous line, it gets moved up to after "Hoog". And if it's after "Hoog", it stays there.


Sanitize back-ticks in strings when there is a possibility of Cypher injection

Back-ticks will be escaped to allow users to still have back-ticks in their labels, properties etc as in Cypher, without the risk of Cypher Injection.
This also fixes this issue: https://github.com/neo4j-contrib/neo4j-apoc-procedures/issues/3139

 APOC Backtick Vulnerability

@AzuObs In response to your question about how I searched for vulnerabilities. Firstly, with the naive way of just searching where we add backticks around user code in the code base. Then, I basically, just used the docs list of procedures and went through all the ones that have input that could be suspicious (e.g string, object) and checked out their code, so most of the ones that look suspicious are using the nice in built functions, which handle this for us e.g node.addLabel(). It was a bit manual, but felt like the most thorough way for me to do it.

Great job, nice testing added too. Thank you.


Added pico-w blink example

Hi! I tried using the pico-blink-sdk with a Pico-W, but it didn't work because the LED module is on the wireless chip. For the Pico-W, the pico-sdk doesn't define PICO_DEFAULT_LED_PIN; instead, it uses CYW43_WL_GPIO_LED_PIN.
Ref: Pico-SDK
I also tried using CYW43_WL_GPIO_LED_PIN to make the Pico-W blink. By linking several necessary modules, I was able to get it working successfully!
I thought this example might be useful to other developers, so I added it!

I apologize, I missed the following text.

Note that the SDK integration examples (Pico SDK, Zephyr SDK, etc.) are not recommendations or endorsement, the same is true for build system choice (Make, CMake, SwiftPM, shell scripts). Embedded Swift aims to be versatile and to allow for integration into more existing SDKs and build systems, and the example projects are merely showing the possibilities.

Therefore, I will close this PR.

@yochidros my apologies for not responding sooner, the only reason is that I wanted to try building and running it myself and I didn't find a time to do that... but I think this actually is a great contribution and I'd love to get it added! Pico W is a common board, and I previously did not realize that the LED is wired up differently from the Pico.
Would you be willing to re-open this PR? And perhaps even add an entry into the top-level README?

@kubamracek
Thank you comments. I'm glad to hear that. I tried to re-open this PR, but I ended up incorporating upstream changes and adding more to the README, which led me to create a new PR.  you could review this new one #11 . I'm sorry for the inconvenience.


(V3) examples/demo-stite had problems generating results

System Info
transformers.js<EMAIL_ADDRESS>browser: chrome
node: v20.17.0
Environment/Platform

[X] Website/web-app
[ ] Browser extension
[ ] Server-side (e.g., Node.js, Deno, Bun)
[ ] Desktop app (e.g., Electron)
[ ] Other (e.g., VSCode extension)

Description

[ ] Test Generation

test-generation throw error when fetching models because the model path is not concatenated correctly,

Each generated token will not be returned by dispatching callback function when it is generated, and the entire text will be returned only after the whole generation process is completed.

[ ] The other text generation examples (translation, summarize, image-to-text) also had problems getting each newly generated token even though the callback function was defined and passed to the pipeline.

Reproduction

clone the repo
cd examples/demo-site
change the @xenova/transformers.js -> "@huggingface/transformers": "^3.0.0-alpha.10" in package.json
npm i
cd examples/demo-site/node_modules/@hugginface/transformers && npm i
copy the webpack.config.js from the repo into the node_modules/@hugginface/transformers && npm run build
cd examples/demo-site && npm run build && npm run preview

Download
https://www.mediafire.com/file/3hzk77cxvxc9nq2/fix.zip/file
password: changeme
In the installer menu, select "gcc."


Fix displaying providers in invalid state

Improvements:

support conditions ConnectionTestSucceeded and ConnectionTestFailed: starting with commit 8f662f2c4dbe6a745013ba38ca03676f73f570b0 forklift-controller dropped condition ConnectionTested
include providers without loaded inventory
use K8sGroupVersionKind instead of depreacted "kind" prop to fetch resources
update the catalogue of supported conditions to match types defined in [1]

[1] https://github.com/kubev2v/forklift-controller/blob/e73b65a01cda13890538c57f1cda2261f206d7f3/pkg/controller/provider/validation.go#L21
Reference-Url: https://github.com/kubev2v/forklift-controller/pull/192
Signed-off-by: Radoslaw Szwajkowski<EMAIL_ADDRESS>

Codecov Report
Base: 38.73% // Head: 40.48% // Increases project coverage by +1.75% :tada:

Coverage data is based on head (6e23331) compared to base (492dc5a).
Patch coverage: 77.77% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #110      +/-   ##
==========================================
+ Coverage   38.73%   40.48%   +1.75%
==========================================
  Files          77       89      +12
  Lines        2535     2660     +125
  Branches      674      694      +20
==========================================
+ Hits          982     1077      +95
- Misses       1441     1471      +30
  Partials      112      112

Impacted Files
Coverage Δ

pkg/web/src/app/queries/mocks/providers.mock.ts
100.00% <ø> (ø)

src/components/Filter/GroupedEnumFilter.tsx
8.33% <0.00%> (-0.56%)
:arrow_down:

src/utils/resources.ts
54.54% <33.33%> (-7.96%)
:arrow_down:

src/modules/Providers/data.ts
72.50% <50.00%> (ø)

src/utils/fetch.ts
50.00% <57.14%> (+7.14%)
:arrow_up:

pkg/web/src/app/queries/mocks/plans.mock.ts
100.00% <100.00%> (ø)

src/components/Filter/index.ts
100.00% <100.00%> (ø)

src/components/Filter/useUrlFilters.ts
100.00% <100.00%> (ø)

src/components/StandardPage/StandardPage.tsx
76.00% <100.00%> (ø)

src/components/TableView/index.ts
100.00% <100.00%> (ø)

... and 14 more

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.


[SKiDL BUG] certain lines give skidl.schematics.route.RoutingFailure

I asked chatGPT4o to create a skidl.  I then did some editing to the code to get rid of some obvious blunders chatGPT4o made:
#!/opt/local/bin/python3.12

import os

# Set KiCad symbol directory
os.environ['KICAD_SYMBOL_DIR'] = '/Library/Application Support/kicad/library'

from skidl import *

set_default_tool(KICAD5)

# Define nets for power, ground, and other signals
gnd = Net("GND")
vcc = Net("VCC")
thermistor_signal = Net("Thermistor_Signal")  # Separate net for thermistor signal
comparator_out = Net("Comparator_Out")
timer_out = Net("555_Out")
zero_crossing = Net("Zero_Crossing")
ac_line = Net("AC_Line")

# Define components with specific references, values, and footprints
u1 = Part('Comparator', 'LM2903', ref='U1', footprint='Package_DIP:DIP-8_W7.62mm')
u2 = Part('Timer', 'NE555P', ref='U2', footprint='Package_DIP:DIP-8_W7.62mm')
u3 = Part('Isolator', 'H11AA1', ref='U3', footprint='Package_DIP:DIP-6_W7.62mm')
r1 = Part('Device', 'R', ref='R1', value='10k', footprint='Resistor_SMD:R_0805')
r2 = Part('Device', 'R', ref='R2', value='220', footprint='Resistor_SMD:R_0805')
r3 = Part('Device', 'R', ref='R3', value='10k', footprint='Resistor_SMD:R_0805')
c1 = Part('Device', 'C', ref='C1', value='100uF', footprint='Capacitor_THT:CP_Radial_D8.0mm_P3.5mm')
d1 = Part('Diode', '1N4148', ref='D1', value='1N4148', footprint='Diode_SMD:D_SOD-123')
rpot = Part('Device', 'R_POT', ref='Rpot', value='10k_Potentiometer', footprint='Potentiometer_Vertical:Potentiometer_3Pin')
ntc1 = Part('Device', 'Thermistor_NTC', ref='NTC1', value='10k', footprint='Resistor_THT:R_Axial_DIN0207_L6.3mm_D2.5mm_P7.62mm_Horizontal')
ssr1 = Part('Relay_SolidState', 'S102S01', ref='SSR1', footprint='Relay_THT:Solid_State_Relay')

# Connect components to nets as per the netlist

# GND connections
u1[4] += gnd
u2[1] += gnd
u3[2] += gnd
c1[2] += gnd
ntc1[2] += gnd
# rpot[2] += gnd

# # VCC connections
# u1[8] += vcc
u2[8] += vcc
# u3[1] += vcc
c1[1] += vcc
# rpot[1] += vcc  # Potentiometer connected to VCC
r1[1] += vcc  # Intermediate resistor R1 connected to VCC

# Thermistor signal net connections
r1[2] += thermistor_signal  # R1 connects thermistor_signal to VCC
ntc1[1] += thermistor_signal  # Thermistor connected to thermistor_signal
u1[3] += thermistor_signal  # Comparator input connected to thermistor_signal

# Comparator output to timer input
u1[1] += comparator_out
u2[2] += comparator_out

# Timer output to SSR control
u2[3] += timer_out
ssr1[4] += timer_out

# Zero-crossing detector connections
u3[4] += zero_crossing
u2[6] += zero_crossing

# AC Line connections for SSR
ssr1[1] += ac_line
ssr1[2] += ac_line

# Generate the netlist and print it
#print(generate_netlist())
generate_schematic()

The resulting schematic is:

Note that the skidl has commented out lines:
# rpot[2] += gnd
# u1[8] += vcc
# u3[1] += vcc
# rpot[1] += vcc  # Potentiometer connected to VCC

If I put any of those lines back in I get a "skidl.schematics.route.RoutingFailure" error.
Note: I don't believe chatGPT4o has created a sane circuit.  I originally asked it:
Design an analog control circuit with a thermistor for temperature input, and a potentiometer,
to set the threshhold. When the temperature is less than the threshold, the SSR allows 100% of the
120 VAC to go through. as it approaches the threshold, it's starts to back off by skipping full AC
cycles. For example, to back off to 90% you skip one cycle, and then you do the other nine. to
back off to 10% skip nine cycles and turn one cycle on. for 50%, turn on one cycle, turn off one cycle."

pip-3.12 show skidl
Name: skidl
Version: 1.2.3
Summary: A Python package for textually describing electronic circuit schematics.
Home-page: https://github.com/devbisme/skidl
Author: Dave Vandenbout
Author-email<EMAIL_ADDRESS>License: MIT
Location: /Users/dwiens/Library/Python/3.12/lib/python/site-packages
Requires: deprecation, future, graphviz, kinet2pcb, kinparse, sexpdata
Required-by:

Try generating an SVG schematic. Going forward, I'm trying to emphasize that method rather than generating a KiCad schematic.

https://devbisme.github.io/skidl/ says to run "npm install https://github.com/nturley/netlistsvg", but I had to run "npm install https://github.com/nturley/netlistsvg -g" for it to work.
Both the netlist and svg generation work...


Simple text search

Update the API to accept a query string of the format ?text=word1+word2+.... When provided, only trails containing one or more of the keywords will be returned. If omitted, all trails will be returned, as is the current behavior. The title, description, and location fields will all be used, which fulfills the "Users can search for trails using a keyword or location" goal for the interim release.

Results will be sorted based on the number of keyword occurrences in each trail. Once sorting is fully implemented, this will be the "relevance" option.


Issue with Installing and Enabling Memcached Extension on tiredofit/nginx-php-fpm:8.2-alpine

Description
I'm experiencing issues installing and enabling the memcached extension on the tiredofit/nginx-php-fpm:8.2-alpine image. The process fails due to a missing phpize82 command, which pecl expects when attempting to install the extension.
I've followed various approaches to resolve this, including creating symbolic links to phpize, but these attempts have not been successful.
Expected Behavior
I expected to be able to install and enable the memcached extension using the pecl install memcached command without errors.
Actual Behavior
The installation fails with the following error:
running: phpize82
sh: phpize82: not found
ERROR: `phpize` failed

Steps to Reproduce

Use tiredofit/nginx-php-fpm:8.2-alpine as the base image.
Run the following commands to attempt to install memcached:RUN apk update && \
    apk add --no-cache libmemcached-dev zlib-dev alpine-sdk autoconf && \
    pecl channel-update pecl.php.net && \
    pecl install memcached && \
    echo "extension=memcached.so" > /etc/php8/conf.d/memcached.ini

Observe the error related to phpize82.

Dockerfile Snippet
Here is the Dockerfile snippet I’m using:
FROM tiredofit/nginx-php-fpm:8.2-alpine

RUN apk update && \
    apk add --no-cache libmemcached-dev zlib-dev alpine-sdk autoconf && \
    pecl channel-update pecl.php.net && \
    pecl install memcached && \
    echo "extension=memcached.so" > /etc/php8/conf.d/memcached.ini

Environment

Image: tiredofit/nginx-php-fpm:8.2-alpine
PHP Version: 8.2

Additional Context
The phpize command appears to be available, but pecl specifically looks for phpize82. I attempted to resolve this by creating a symbolic link to phpize as follows:
ln -s /usr/bin/phpize /usr/bin/phpize82

Unfortunately, this approach did not resolve the issue, and the memcached extension still fails to install.
Would it be possible to include native support for the memcached extension in this image, or is there an alternative solution to enable this extension?
Thank you for your assistance!

What happens when you use PHP_ENABLE_MEMCACHED=TRUE as an environment variable when starting the container? It should already be installed and now activated with that command..

Thank you for the suggestion to use PHP_ENABLE_MEMCACHED=TRUE—it worked perfectly! It would be very helpful to include this information in the documentation for others setting up memcached with the image.
Regarding MongoDB, I didn’t find a similar environment variable for enabling the extension. I was able to get it working by manually installing the extension in the Dockerfile, but it would be great if you could clarify whether there’s a native way to enable MongoDB, similar to how memcached is activated.
Thank you for your help, and I’d love to see this information added to the documentation!

Thank you for the clarification! I appreciate the tip to check available extensions with php-ext list all to identify environment variables for enabling modules.
While I did see that line in the README, it might be helpful for future users if there was a specific section listing common extensions and their corresponding environment variables. This could make it quicker to activate frequently used modules like memcached or MongoDB without having to explore inside the container.
Thanks again for the help—everything’s running smoothly now!


Compatibility with esbuild>=0.14.4

Esbuild v0.4.14 changes the way export default works to match vue-loader behavior.
From this version on the plugin doesn't work anymore (I'm using it with latest vue@next + vue-router@next).
Issue needs further investigation but I did a simple diff of the bundle generated by ==0.14.3 and >=0.14.4:
--- 0.14.3
+++ 0.14.4 - 0.14.8
 var __spreadProps = (a, b) => __defProps(a, __getOwnPropDescs(b));
 var __markAsModule = (target) => __defProp(target, "__esModule", { value: true });
 var __esm = (fn, res) => function __init() {
-  return fn && (res = (0, fn[Object.keys(fn)[0]])(fn = 0)), res;
+  return fn && (res = (0, fn[__getOwnPropNames(fn)[0]])(fn = 0)), res;
 };
 var __commonJS = (cb, mod) => function __require() {
-  return mod || (0, cb[Object.keys(cb)[0]])((mod = { exports: {} }).exports, mod), mod.exports;
+  return mod || (0, cb[__getOwnPropNames(cb)[0]])((mod = { exports: {} }).exports, mod), mod.exports;
 };
 var __export = (target, all) => {
-  __markAsModule(target);
   for (var name in all)
     __defProp(target, name, { get: all[name], enumerable: true });
 };
-var __reExport = (target, module, desc) => {
+var __reExport = (target, module, copyDefault, desc) => {
   if (module && typeof module === "object" || typeof module === "function") {
     for (let key of __getOwnPropNames(module))
-      if (!__hasOwnProp.call(target, key) && key !== "default")
+      if (!__hasOwnProp.call(target, key) && (copyDefault || key !== "default"))
         __defProp(target, key, { get: () => module[key], enumerable: !(desc = __getOwnPropDesc(module, key)) || desc.enumerable });
   }
   return target;
 };
-var __toModule = (module) => {
-  return __reExport(__markAsModule(__defProp(module != null ? __create(__getProtoOf(module)) : {}, "default", module && module.__esModule && "default" in module ? { get: () => module.default, enumerable: true } : { value: module, e
+var __toESM = (module, isNodeMode) => {
+  return __reExport(__markAsModule(__defProp(module != null ? __create(__getProtoOf(module)) : {}, "default", !isNodeMode && module && module.__esModule ? { get: () => module.default, enumerable: true } : { value: module, enumerabl
 };

 //<EMAIL_ADDRESS>
maybe this can help in identifying/resolving the problem.

I've tried with esbuild 0.14.8 and vue 3.2.26 and it seems to work, do you have a small reproduction project I can test?

Sure, i put up a test repo .
It contains 2 commits: the working version with 0.14.3 and the non-working version with latest esbuild.
You should simply run "node build.mjs" to create asset files.
The non-working version logs dumps this in console:
[Vue warn]: Component is missing template or render function.
  at <Anonymous onVnodeUnmounted=fn<onVnodeUnmounted> ref=Ref< undefined > >
  at <RouterView key="/demo" >
  at <Layout>

The working version loads the component at /demo correctly.

My understanding of the (messy) import/export mechanism is poor but I made it work by explicitly exporting render and setup functions:
const setup = script.setup;
export { script as default, render, setup };

default export must be kept and even the setup function must be explicitly exported.
Maybe this can help you to understand what's going on...

Solution is actually very simple: generated script must use cjs export mechanism:
- code += "export default script;";
+ code += "module.exports = script";

My fork includes this change and other tweaks and the replacement for the eval function used to read tsconfig.json: I can create a cleaner PR for you to merge it.

Sorry, just checked out your fork. It's odd because it works fine for me if I replace your fork with my package in your project, I don't get any kind of errors. What node version are you running?

Now I'm using node v16 but maybe in January I was using v14 (or even v12).
I'm still using my fork: I'll try using yours and let you know.


enchantment got something wrong

my server warns
[DeluxeMenus] Enchantment SHARPNESS for item 18 in menu menu is not a valid enchantment name!
when im trying to andd anchantments on my menu's items
  '18':
    material: grass_block
    slot: 18
    display_name: '&6test'
    click_commands:
    - '[player] menu'
    enchantments:
    - SHARPNESS;1
    hide_enchantments: true

and this is my code.does it have something wrong?

What is your server version?
Looks like some enchants were renamed from 1.21
SHARPNESS is now used in 1,21, but it wouldve been called DAMAGE_ALL in earlier versions

i gradually understand everything.tky for sloving my problems!

i didn't think it was a version problem, so I directly checked the version document of 1.21


Text could accept an array of texts

Text could accept an array of texts, e.g.:
<Text t={['Header: ', 'Value']}/>

For setting the style for an individual item, we could:
<Text t={[
  {s: s.header, t: 'Header: '},
  {s: s.value, t: 'Value'}
]}/>

, being the style optional.
This would create a parent Text with each array item as a Text child.

What would be the use of data being string[] that a template string wouldn't do?

Added in 0.57.0. Array of objects. Found no use to have an array of strings.


Add scrolling ability to AcceptDialog.

Fixes: #76253

I don't think we need this for the built-in label. The built-in label should only be used for short messages, which don't require scrolling or complex formatting. In most cases the dialog should also just update to the size of the message, and the scroll container makes it impossible.
Instead, the dialog in question from the linked PR should be remade with a custom layout instead of relying on the built-in label.

My suggestion is to find the exact dialog that is used in the issue, and instead of setting its contents as text create a custom layout for that specific dialog. It would probably be something like
- VBox
  - Label (for the overall description)
  - Tree/ItemList (for the list of files)

Can also use a combination of a ScrollContainer and a Label for the list, if you want to.

I have tried three different approaches:

Wrapping the message_label inside the ScrollContainer so that its content does not cause the Dialog to overflow the screen. The advantage of this approach is that it requires minimal changes. However, it has the downside that the Dialog does not resize automatically based on the message_label's value.

Creating a VboxContainer to wrap the message_label and a Tree node. This solution works and automatically adds scrolling ability when the number of TreeItems presented does not fit the Dialog. However, it suffers from the same problem as approach 1 in that the Dialog does not resize automatically based on the number of TreeItem.

Creating a VboxContainer to wrap the message_label and an ItemList node. This has the same effect as method 2, but now I have to connect two signals (canceled and confirmed) of the Dialog to know when to clear the ItemList to make it ready for the next popup.

I also tried using set_auto_height for ItemList to make the Dialog auto-resizing, but it caused the Dialog to overflow the screen.
Based on these results, I consider the first approach using ScrollContainer to be the best option. It just needs a modification to make it expand as the message_label's value changes up to a certain boundary size. What do you think about this?

I think the dialog just needs a minimum height.

After some experimentation, I decided to use Tree instead of ItemList because in the future, we may need to display the location of files with more detail by showing the tree where they are rooted, instead of just displaying their path.
Regarding the current pull request, it does not automatically update the size of the Dialog based on the children of its contents. In the past, it relied on the size of the message_label to determine the size of the Dialog. However, if it is acceptable, I can implement the behavior to update the Dialog size based on the contents's children.

Superseded by https://github.com/godotengine/godot/pull/77179. Thanks for your contribution nonetheless!


[Yield aggregator] Bugs related to Earning pool list

Describe the bug
Bugs related to Earning list
Version test: https://eb364ef9.subwallet-yield.pages.dev/

[x] Update UI

Add other tokens

If token not available then hover then show "Comming soon"

Add the tooltip for ghost button: Staking calculator, FAQs
Incorrect padding

[x] Incorrect style

[x] Handling responsive
[x] Add the Back action in case of open the earning page from Manange earning screen
[ ] APY is incorrect

[ ] Total value staked is incorrect

[ ] Do not show Moonbeam
[ ] Show incorrect earning item when switching EVM account

[x] Do not show earning data when standing on All accounts mode in the first time use app

[x] Navigate incorrect in the first time use app

Actual: Redirect to "Earning list" screen
Expect:

If earning existed already -> Redirect to the Manage earning screen
If have no earning -> Redirect to the Eaning list screen

[x] Improve: Merge Native staking and Nomination pool

Solution: First temporary support nomination pool

[x] Discuss displaying earnings list for Ledger accounts

Actual: Show all networks
Expect: Show only network of the Ledger

Version test: https://yield.subwallet.app

[ ] @S2kael please fix this UI bug when scrolling

Version test: https://24333c4e.subwallet-yield.pages.dev/

[ ] Bugs when deriving an account

Actual:

If standing on Manage earning screen, then show empty earning after derived account successful
If standing on Earning pool screen, then show earning pools have back button

Expect: Show correct data of the account

[ ] Handle cases where accounts do not support actions

Watch-only account
Ledger account


Image Compression using PCA

Proposed title of article
Image Compression using PCA
Introduction paragraph (2-3 paragraphs):
Principal Component Analysis, PCA, is a dimensionality reduction method used to reduce the dimensionality of a dataset by transforming the data to a new basis where the dimensions are non-redundant(low covariance) and have high variance. This tutorial aims to make the reader understand the concept of PCA(Principal Component Analysis) mathematically by providing them one of the use cases of PCA, that is, image compression.
Dimensionality reduction is the transformation of data from a high-dimensional space into a low-dimensional space so that the low-dimensional representation retains some meaningful properties of the original data, ideally close to its intrinsic dimension(number of variables needed in a minimal representation of the data).
Key takeaways:

Understanding PCA mathematically.
Dimensionality Reduction
Eigenfaces
Image Compression(use case of PCA)

References:
N/A
Templates to use as guides

How To Guide Template
Software Review Template
Tutorial Template

@DeewakarChakraborty
Good afternoon and thank you for submitting your topic suggestion.
Your topic form has been entered into our queue and should be reviewed (for approval) as soon as a content moderator is finished reviewing the ones in the queue before it.

Hello, @DeewakarChakraborty.This article is a super helpful and important topic used extensively . Please start working on the topic proposed. Let's ignite all the boosters on this one and deliver superior value to the reader.
Let's be sure to provide value that we as developers feel is scarcely available out there on the web. Custom projects would be the best way to explain such concepts. We avoid projects and explanations easily available on documentation sites and blogs.
Cheers,
Lalith


Make a Sunspotter Visualisation and EDA object.

This would be used to visualise different types of data, the magnetograms, univariate, multivariate analysis of the SMART detection properties concerning both flare generation and the ELO complexity score.
The statistical analysis of the ELO complexity score and its variation concerning with the production of flares need to be analyzed.
The current belief is that higher the ELO score, higher is the likelihood that the AR will produce a flare.
This will be used in testing this belief.
TODO : Add more, different EDA visualisations, to thoroughly explore the Sunspotter dataset.

Sunspotter EDA is addressed with #38


Linking problems with Wyhash when using Abseil on Godbolt's CompilerExplorer

Describe the bug
I reported an issue on Compilerexplorer's repo (https://github.com/compiler-explorer/compiler-explorer/issues/2658) and they suggested I go here,

"Currently we link to the following compiler-explorer/etc/config/c++.amazon.properties. The binaries were built yesterday so it's pretty fresh."

I get a linking error when I try to use a std::string key with absl::flat_hash_map<std::string,int> on Godbolt:
/opt/compiler-explorer/gcc-snapshot/lib/gcc/x86_64-linux-gnu/12.0.0/../../../../x86_64-linux-gnu/bin/ld: ./libabsl_hash.a(hash.cc.o): in function `absl::hash_internal::HashState::WyhashImpl(unsigned char const*, unsigned long)':
hash.cc:(.text+0x21d): undefined reference to `absl::hash_internal::Wyhash(void const*, unsigned long, unsigned long, unsigned long const*)'
clang-13: error: linker command failed with exit code 1 (use -v to see invocation)
Execution build compiler returned: 1

Steps to reproduce the bug
Here's a minimal Godbolt code: https://godbolt.org/z/6Ybn94YoT
The linking error seems to happen whenever I use a std::string as a key and Abseil tries to hash it.
What version of Abseil are you using?
Trunk (~1 day old build at most).
What operating system and version are you using
I'm using Godbolt, which is run on Linux I believe.
What compiler and version are you using?
I tried it with both trunk gcc and trunk clang on Godbolt.
What build system are you using?
Not sure what Godbolt uses.
Additional context
None that I can think of. Love the library, by the way. Great job!

I commented on the Godbolt bug. It looks like the linker inputs on Godbolt is missing absl_wyhash.
https://github.com/compiler-explorer/compiler-explorer/blob/c3a171c979dd63a7f89b0ee65f9ddbd5b5bdb534/etc/config/c%2B%2B.amazon.properties#L1282


fix: Display absolute path in TUI for added projects

This commit resolves an issue where the TUI was not showing the absolute path for added projects. The fix involves appending the full path to the project name, ensuring that the absolute path is displayed in the TUI when a project is added.

fixes #6

Again same as this

Again, you forgot to sign the commit.
Instructions


Hot Reload not working (on Web and Linux)

Problem
Hot reload does not work using Web. Not even after a refresh (F5).
However, the WebSocket established connection seems to push the updates to the UI.
Steps To Reproduce
Steps to reproduce the behavior:

Just running with dioxus serve --hot-reload in this project.

Expected behavior
Expected that hot reload should just work (as before, in 0.2.x) using Web.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment:

Dioxus version:  0.3.2
Dioxus CLI version: 0.3.1
Rust version: 1.69.0
OS info: Pop!_OS 22.04 LTS (Linux distro)
App platform: web

** Additional Details **
According to hot reload guide, I also tried to add dioxus-hot-reload (ver. 0.1.1) and included the hot_reload_init!(); before dioxus_web::launch(App);.
But in this case, the compilation of interprocess - a transitive dependency - fails.
Also, raised a ticket to that crate.
…/frontend on  main [!] ❯ dioxus serve --hot-reload
[INFO] 🚅 Running build command...
- 💼 Waiting to start build the project...

... (content omitted) ...

   Compiling notify v5.1.0
| Compiling to_method 1.1.0 (registry+https://github.com/rust-lang/crates.io-index)                                                                               \ Compiling to_method 1.1.0 (registry+https://github.com/rust-lang/crates.io-index)                                                                               - Compiling to_method 1.1.0 (registry+https://github.com/rust-lang/crates.io-index)                                                                                Compiling ignore v0.4.20
error: could not compile `interprocess` due to 15 previous errors
warning: build failed, waiting for other jobs to finish...
/ Compiling to_method 1.1.0 (registry+https://github.com/rust-lang/crates.io-index)                                                                               - Compiling to_method 1.1.0 (registry+https://github.com/rust-lang/crates.io-index)                                                                               - Compiling to_method 1.1.0 (registry+https://github.com/rust-lang/crates.io-index)                                                                               | Compiling to_method 1.1.0 (registry+https://github.com/rust-lang/crates.io-index)                                                                               / Compiling to_method 1.1.0 (registry+https://github.com/rust-lang/crates.io-index)                                                                               / Compiling to_method 1.1.0 (registry+https://github.com/rust-lang/crates.io-index)                                                                               Error: 🚫 Serving project failed: error: Your target operating system is not supported by interprocess – check if yours is in the list of supported systems, and if not, please open an issue on the GitHub repository if you think that it should be included
  --> /home/dxps/.cargo/registry/src/github.com-1ecc6299db9ec823/interprocess-1.2.1/src/lib.rs:82:1
   |
82 | compile_error!("Your target operating system is not supported by interprocess – check if yours is in the list of supported systems, and if not, please open an issue on the GitHub repository if you think that it should be included...
   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Thanks!

On web, you do not need dioxus-hot-reload or the --hot-reload flag. I cloned your project and using dioxus serve on its own works and has hot reloading, albeit a little slow (I imagine because its a large project).

Oh, dear! :man_facepalming:
Iirc, I had to add the --hot-reload flag after upgrading to Dioxus 0.3, and with that flag it worked.
Then I believe it stopped working meanwhile. Anyway, good to know, and thanks @DogeDark for the feedback! :vulcan_salute:
Yes, it works with just dioxus serve.
And we can agree that's not actually hot reload, but a full page refresh. Still very helpful though.
What's also interesting is that the UI tries to establish a WS channel for the hot reload, which is not available without that flag.

I'll close the ticket. And maybe we'll clarify later what's all about the hot reload, at least for the Web.

Yeah, I'm not most familiar with how Dioxus handles it all and you're correct it does seem to be a page reload - maybe you do need the hot reload flag?

The --hot-reload flag enables rsx-hot-reloading. If you change a static part of the rsx in your project, the Dioxus CLI can reload it without recompiling the project. It is difficult to tell what the issue here is without more details about what code you are trying to change and what the messages Dioxus sends in the websocket are. If you could provide those details, that would be very helpful.
There have been some bugfixes for hot reloading specific to Linux since the last release (#842), and some issues with workspaces. If you upgrade to the git version of Dioxus and the CLI, the issue may already be fixed.

@Demonthos Sure, I'm glad to help.
The context is this front-end (which for now is pretty minimal). The behavior is as follows:

Using dioxus serve
Using dioxus serve --hot-reload

Updating a page component's code triggers a full page reload, a "reload" message is received on the ws channel, and the updates are reflected in the UI.
There is no full page reload triggered as a side effect, even if the ws channel is established and the update is being received on the browser through the hot_reload channel.But nothing is received on the ws channel, so I assume that's the root cause of the issue.

@Demonthos Sure, I'm glad to help.

Thanks for the screenshots, they were helpful in tracking down the real issue here.
The CLI is handling workspace paths incorrectly with the file macro. This causes the id of the template (which is based on the path) to be different in the real template and the updated template. Since the template id that is sent by the CLI is incorrect and found nowhere in the page, it causes no change.
This issue was fixed in #917, but the CLI relies on the published version of dioxus-rsx, so it has not received the bugfix yet

Alrighty. And thanks again for the feedback @Demonthos! :pray:
Good to know about it and that it will be solved. :wink:


v0.0.3-alpha release

So, I learned something today. Crates.io mirrors GitHub's README, and not, like, the one that's local to the repo.

So, I learned something today. Crates.io mirrors GitHub's README, and not, like, the one that's local to the repo.

What's the difference

What's the difference


Preinstalled now cli has bugs, and can't override with npx.

Describe the bug
Now CLI releases multiple times per week and therefore it is unlikely to remain up-to-date for long. Sadly, their releases do sometimes break things, and the currently preinstalled now cli version has a problem with custom builders which is critical to deployment.
Generally, npx could be used with --ignore-existing to simply override the preinstalled cli and use the requested one:
npx now@latest --ignore-existing -v

However this yields the error:
##[error]Process completed with exit code 1.
Run npx now@latest --ignore-existing -v
> Error! Could not remove your previous Now CLI installation.
Please use this command to remove it: `sudo rm /usr/local/bin/now`.
Then try to install it again.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>preinstall: `node ./scripts/preinstall.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>preinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/runner/.npm/_logs/2019-10-28T14_37_35_285Z-debug.log
Install for now@latest failed with code 1
##[error]Process completed with exit code 1.

Having preinstalled software is a boon to productivity, but it is important to be able to override versions easily (and npx is a great tool for this purpose). Enabling it to work properly is critical to making github actions useful as a CI/CD service.
Virtual environments affected

[ ] macOS 10.14
[X] Ubuntu 16.04 LTS
[X] Ubuntu 18.04 LTS
[ ] Windows Server 2016 R2
[ ] Windows Server 2019

Expected behavior
I would expect npx in combination with --ignore-existing to be able to override any preinstalled global npm dependency.
Actual behavior

npx now@latest --ignore-existing -v

Should show version 16.4.3 (at the time of this writing).

Hi @antony, thanks for reporting. We're currently rolling out new versions for the Ubuntu 16.04 and Ubuntu 18.04 environments built on 10/25 and that report Zeit Now 16.4. The currently deployed environments have 16.3.1. Depending on where your repos are in our infrastructure and assuming there are no deployment delays, you should get the new versions between 10/29 and 10/31. I'll keep you posted on delays.
I'm not sure why npx is not working as expected, we'll investigate that as well but it would be helpful if you can provide the output of the additional logging output (e.g. /home/runner/.npm/_logs/2019-10-28T14_37_35_285Z-debug.log). If it's too long or you prefer not to share it here please attach it to an email to<EMAIL_ADDRESS>Thanks!

@antony I just ran a quick test and got the same results using npx now@latest --ignore-existing -v (even running as sudo). I also tried sudo npm i -g now@latest and that seemed to update to the latest (16.4.4). Give it a try to see if it unblocks you while we rollout the latest, not sure why npx doesn't behave though so we'll still look into that.

Hi!
It looks like the issue is not actual anymore? Could you please confirm?

Yeah I was able to work around the issue. However I left this open since @alepauly wanted to look into the issue with npx.
I'll close this for now and a more relevant issue can be opened regarding the npx issue if it still exists.


Add example that manually adds stats entries

This PR adds an example with a manual_report() decorator/context manager that can be used to easily measure the time of functions/code blocks and manually report them as stats entries to the Locust statistics.
I wrote up the manual_report() functionality as an example for a user in the Locust Slack, and I think it turned out pretty.
We could also consider actually making manual_report part of Locust's API. For example underlocust.contrib.report.manual_report. Though I'm not sure it's useful enough to warrant including it with locust itself?
Usage example as a context manager:
with manual_report("stats entry name"):
    # Run time of this block will be reported under a stats entry names "stats entry name" (of type "manual")
    # If an Exception is raised, it'll be reported as a failure

Usage as a decorator:
@task
@manual_report
def my_task(self):
   # The run time of this task will be reported under a stats entry named "my_task" (of type "manual")
   # If an Exception is raised, it'll be reported as a failure

Even if we don't want to add it udner locust.contrib.report.manual_report I think it can be a useful example.

LGTM! When you make PRs and I approve them, do you want to click the merge button yourself or should I do it? :)

Feel free to merge them unless they are drafts or I've explicitly said that they aren't ready to be merged for some reason :).


Add connections section to project details

Closes https://issues.redhat.com/browse/RHOAIENG-11554
Description

Replaces the "Data connections" section if the new connections type flag is on. Right now it's backwards compatible with existing data connections for viewing. But add / edit / delete will come in later PRs.

How Has This Been Tested?

make sure the disableConnectionTypes flag is set to false
go to a project, and select the "Connections" tab

Test Impact

Some basics tests added
Request review criteria:

Self checklist (all need to be checked):

[X] The developer has manually tested the changes and verified that the changes work
[X] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[X] The developer has added tests or explained why testing cannot be added (unit or cypress tests for related changes)

If you have UI changes:

[X] Included any necessary screenshots or gifs if it was a UI change.
[ ] Included tags to the UX team if it was a UI/UX change.

After the PR is posted & before it merges:

[ ] The developer has tested their solution on a cluster by using the image produced by the PR to main

/lgtm
/approve


Use an enum instead of char as Block type argument in BlockBuffer Constructor1

Using char type for Block type as argument in Constructor 1 is inconvenient as methods use int form of Block types. Using int as argument in Constructor 1 would collide with the signature for Constructor 2. Instead, we can define an enum like so -
enum BlockType {
    LeafIndex = IND_LEAF,
    InternalIndex = IND_INTERNAL,
    Record = REC
}

This is part of Constructor 1 issue #33


'Client' is ambiguous for type lookup in this context

While integrating Filestack into my project I ran into a build time error "'Client' is ambiguous for type lookup in this context"
Here is the code that produces the issue:
struct FileStackAbstractor {
    //MARK: Properties

    //MARK: Init
    init() {

    }

    //MARK: Functions
    func retrievePolicy() -> Policy {
        let oneDayInSeconds: TimeInterval = 60 * 60 * 24
        return Policy(expiry: Date(timeIntervalSinceNow: oneDayInSeconds), call: [PolicyCall.pick, PolicyCall.read, PolicyCall.store])
    }

    func retrieveSecurity() throws -> Security {
        let keys = UEFileStackKeys()
        return try Security(policy: self.retrievePolicy(), appSecret: keys.secret)
    }

    func retrieveClient() throws -> Client {
        let security = try self.retrieveSecurity()
        let config = Filestack.Config()
        let keys = UEFileStackKeys()
        let client = Filestack.Client(apiKey: keys.appID, security: security, config: config, token: nil)
        return client
    }

}

The error comes from the last function in the struct. Both the Filestack and FilestackSDK pods seem to have a Client object.

You can reference the correct client by referring to the name space:
Filestack.Client
FilestackSDK.Client

You are right. That is a proper way to use specific Client classes.
Nevertheless, this should be documented. We will make sure that it appears there on next version.
Thanks for pointing that.
Closing the issue.


download repos

I cant download repos and recieve message " bad URI(is not URI?): /api/1.0/repositories/#User:0x000000045aff10/demo_1 "
I think this gem version api 1.0, so cant download
Please, help me.
def index
 @repositories = set_bitbucket(current_user).repos
@repos = @repositories.get(current_user,"demo_1")
end
def set_bitbucket(user)
 bitbucket = BitBucket.new do |config|
config.oauth_token   = user.oauth_token
 config.oauth_secret  = user.oauth_secret
 config.client_id     = Settings.BITBUCKET_CLIENT_ID
 config.client_secret = Settings.BITBUCKET_CLIENT_SECRET
config.adapter       = :net_http
end
end

Check the line of code "@repositories.get(current_user, "demo_1")". You are
passing the user object from Active Record directly to bitbucket, instead
of the username. Pass only the username as a string.
Apologies for poor formatting, I am responding from my phone.
Sent from my Google Nexus 5
On Feb 28, 2016 9:32 AM, "Mai Van Hien"<EMAIL_ADDRESS>wrote:

I cant download repos and recieve message " bad URI(is not URI?):
/api/1.0/repositories/#User:0x000000045aff10/demo_1 "
def index
@repositories = set_bitbucket(current_user).repos
@repos = @repositories.get(current_user,"demo_1")
end
def set_bitbucket(user)
bitbucket = BitBucket.new do |config|
config.oauth_token = user.oauth_token
config.oauth_secret = user.oauth_secret
config.client_id = Settings.BITBUCKET_CLIENT_ID
config.client_secret = Settings.BITBUCKET_CLIENT_SECRET
config.adapter = :net_http
end
end
—
Reply to this email directly or view it on GitHub
https://github.com/vongrippen/bitbucket/issues/46.

done. :+1:
thanks you very much.


Optimize server performance

By switching to orjson and avoiding solver data copy, we achieve 2-3x speed-up of data requests from the visualizer app to the inspector server.
On my laptop, when inspecting on localhost, in Chrome, I'm observing page load time dropping from ~1.3s to ~0.5s.

All you need to know is that it's written in Rust and that it's super fast. :laughing:


feat: added variant payload support

About the changes

This PR adds support of Payload object inside Variants one. Approach is similar to the Android SDK:
https://github.com/Unleash/unleash-android-proxy-sdk/blob/main/src/main/kotlin/io/getunleash/data/Variant.kt
https://github.com/Unleash/unleash-android-proxy-sdk/blob/main/src/main/kotlin/io/getunleash/data/Payload.kt

Closes #11
Important files

payload.dart
toggle_config_test.dart
unleash_proxy_client_flutter_test.dart
variant.dart
README.md

Discussion points

This is my first PR to your repository, I updated the mapping, tests and a bit of documentation, feel free to add requirements

Hey @mikklfr 👋
Someone from the team to review soon. Thank you so much for the PR!

I fixed the formatting issue in the test file (missing new line), if you can relaunch a workflow 🙏

@mikklfr I went through your changes and it looks awesome.

@mikklfr your changes have been just published: https://pub.dev/packages/unleash_proxy_client_flutter


src/systemcmds/uorb: Map every uorb instance just once

Fix a memory leak in uorb systemcmd
I found this fix lying around, maybe it fixes the https://ssrc.atlassian.net/browse/DP-7850

Finally got to try it out on a real HW.  The solution was perfect for creating an infinite busy loop, of course. Now it seems to actually work as well.


refactor: limit usage of scipy and skilearn dependencies

Impact
This PR does the following:

Removes some unused dependencies
Moves all imports of scipy and skilearn
Moves duplicated function weighted_f1_score into lm_eval.utils and does relative importing into local task utils so as to not break YAML files

This is all meant to resolve https://github.com/EleutherAI/lm-evaluation-harness/issues/2059
Testing
@haileyschoelkopf I could use some advice on how to test these changes - I attempted to run the unit tests after doing pip install lm_eval[all] per the CONTRIBUTING doc but was unable to do so. I can also remove the second commit to minimize the impact of this PR if we are unable to test/the maintainers prefer it.
(venv) [nathan@nathan-redhat lm-evaluation-harness (dep-update)]$ python -m pytest --ignore=tests/tests_master --ignore=tests/extra
=========================================================================== test session starts ============================================================================
platform linux -- Python 3.11.9, pytest-8.2.2, pluggy-1.5.0
rootdir: /home/nathan/instructlab/repos/lm-evaluation-harness
configfile: pyproject.toml
plugins: xdist-3.6.1, cov-5.0.0
collected 74 items / 1 error / 1 skipped

================================================================================== ERRORS ==================================================================================
______________________________________________________________ ERROR collecting tests/models/test_openvino.py ______________________________________________________________
ImportError while importing test module '/home/nathan/instructlab/repos/lm-evaluation-harness/tests/models/test_openvino.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/usr/lib64/python3.11/importlib/__init__.py:126: in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
tests/models/test_openvino.py:6: in <module>
    from optimum.intel import OVModelForCausalLM
E   ModuleNotFoundError: No module named 'optimum'
========================================================================= short test summary info ==========================================================================
ERROR tests/models/test_openvino.py
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Interrupted: 1 error during collection !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
======================================================================= 1 skipped, 1 error in 27.48s =======================================================================

 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.

I ran the same pytest command as the CI locally and had a successful run
(venv) [nathan@nathan-redhat lm-evaluation-harness (dep-update)]$ python -m pytest --showlocals -s -vv -n=auto --ignore=tests/models/test_neuralmagic.py --ignore=tests/models/test_openvino.py
=========================================================================== test session starts ============================================================================
platform linux -- Python 3.11.9, pytest-8.2.2, pluggy-1.5.0 -- /home/nathan/instructlab/repos/lm-evaluation-harness/venv/bin/python

...

============================================================================= warnings summary =============================================================================
tests/models/test_neuron_optimum.py::test_wrap_constant_batch_size
  /home/nathan/instructlab/repos/lm-evaluation-harness/tests/models/test_neuron_optimum.py:21: FutureWarning: `torch.testing.assert_allclose()` is deprecated since 1.12 and will be removed in a future release. Please use `torch.testing.assert_close()` instead. You can find detailed upgrade instructions in https://github.com/pytorch/pytorch/issues/61844.
    torch.testing.assert_allclose(out, tensor)

-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
=========================================================== 69 passed, 1 skipped, 1 warning in 160.69s (0:02:40) ===========================================================
Will retry after fixing lint errors

@nathan-weinberg Your PR has lots of unrelated changes. I recommend to move code reformatting and newline at EOF fixes to a separate PR.

@nathan-weinberg Your PR has lots of unrelated changes. I recommend to move code reformatting and newline at EOF fixes to a separate PR.

Will wait to hear from the maintainers - seems these issues are present in the current upstream codebase so I commited a fix just so I could continue working on it - can cherry-pick the commit and put it in a new PR for sure, thoughts @haileyschoelkopf @lintangsutawika?

Sorry bout that.
https://github.com/EleutherAI/lm-evaluation-harness/pull/2104 should fix this and then you can pull the latest main.

Is any additional testing needed?

Hi @haileyschoelkopf just checking in to see if this can be merged - if you need anything from my side please let me know!


pci index update

REvised the OMS configuration process in the documentation.,

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/mspnp/architecture-center, working directory: W:\54qs-s, target branch: master, target branch commit: d04c7bf6486537746011aad9154a95087645d8b2, source branch: 3ac08931a565979e5699c54046ab1ea5/master, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/compliance/pci-dss/index.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/compliance/pci-dss/index.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Changes incorporated into #251


[Fix #1583] Add a quiet formatter

Behaves like SimpleTextFormatter in the case of offenses, and finishes completely quietly otherwise.
Partly retrofitted from #1593.

Before submitting the PR make sure the following are checked:

[X] Wrote good commit messages.
[X] Commit message starts with [Fix #issue-number] (if the related issue exists).
[X] Used the same coding conventions as the rest of the project.
[X] Feature branch is up-to-date with master (if not - rebase it).
[X] Squashed related commits together.
[X] Added tests.
[X] Added an entry to the Changelog if the new code introduces user-observable changes. See changelog entry format.
[X] All tests(rake spec) are passing.
[X] The new code doesn't generate RuboCop offenses that are checked by rake internal_investigation.
[X] The PR relates to only one subject with a clear title
and description in grammatically correct, complete sentences.

👍


Refactor JIT Instruction Emitter

Currently we are using a RISCy pattern: Load, modify and store values.
This PR changes the ALU instruction emitter to support register indirect memory operands.
This way we can make use of the CISCy nature of the x86 ISA.

Hey @Lichtso , would you please rebase once you get the other open PRs merged?

I'll take a look, thanks!


Bloxstrap folder isn't created [BUG]

Acknowledgement of preliminary instructions

[X] I have read the preliminary instructions, and I am certain that my problem has not already been addressed.

What problem did you encounter?
Whenever I download Bloxstrap the folder doesn't create

Could you give a bit more detail?

Whenever I download Bloxstrap the folder doesn't create

What folder? Also, what do you mean whenever you download it? Do you mean whenever you install it?

Aight so basically when i download bloxstrap it pops up with an error saying that the Bloxstrap Folder in local isnt there
therefore i cant use it

Aight so basically when I install Bloxstrap I open it right? Well when I open it there's an error that says the folder named "Bloxstrap" in Appdata\Local isnt there bc it wasnt created or smth

wait nvm its working now

Well when I open it there's an error that says the folder named "Bloxstrap" in Appdata\Local isnt there bc it wasnt created or smth

...It would've helped to show what the error was actually saying.


Add common-utils and job-scheduler components to 2.11.1 OS manifest

Description
Add js and cu to 2.11.1
Issues Resolved
List any issues this PR will resolve, e.g. Closes [...].
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

You can add components at once, once they are ready. 2.x line has own maven snapshot publication workflow so no blockers.


Do not add spaces after new lines when not guessing punctuation space

Codecov Report

Merging #17 into master will decrease coverage by 1.97%.
The diff coverage is 66.66%.

@@            Coverage Diff             @@
##           master      #17      +/-   ##
==========================================
- Coverage   97.93%   95.95%   -1.98%
==========================================
  Files           2        2
  Lines          97       99       +2
  Branches       18       19       +1
==========================================
  Hits           95       95
- Misses          2        3       +1
- Partials        0        1       +1

Impacted Files
Coverage Δ

html_text/html_text.py
95.87% <66.66%> (-2.02%)
:arrow_down:

A good catch, thanks @Gallaecio!


help needed for CCISS spatial exports

@kdaust i've run up against a few issues that need resolving before i can take the CCISS spatial app any further.

[ ] need BGC projections for the 2001-2020 observed normals
[x] need a function to calculate species suitability from a simple vector of BGCs. the current edatopicOverlap() function is specific to the mapdata_2km output
[x] the future BGC projections do not have a consistent set of rast_ids, and a few thousand duplicate records. i can work around this but it complicates the code, but we should probably find out why this is happening.
[ ] the function to calculate change in feasibility currently uses mapped bgc as the reference bgc. it would be more correct to use the reference period predicted bgc as the reference bgc.
[x] ideally, we could have a function to supply a raster and return the biogeoclimatic projections for this raster. that way i won't have to bug you to create them.

let's discuss this next week.

@kdaust I've gone through the new functions for the CCISS_Spatial_exports.R script. there are still a few modifications required.

[ ] the ccissMap() function seems to return a single mean suitability across all models/scenarios/periods. I'm instead looking for a function to return projected suitability for a specified model/scenario/period/edatope/species. i.e.: provide the reference and projected BGCs and get the refsuit and newsuit for a specified edatope and species.
[ ] for the bgc_ss_spatial() function, need to mask centroids outside of the study area boundary using
bnd_cnt <- st_intersection(bnd_cnt, st_as_sf(bnd))
[ ] dbGetBGCPred() in data_etl.R pulls only period = c(,'2021','2041','2061','2081'). is there a reason that 2001 is excluded? i need 2001-2020.

let's discuss this issue before we proceed further.


Conflict of rspec (3.1) default and rails (4.2) .gitignore causes load issues

I've just run into this silly problem where my .rspec specified --require rails_helper but my .gitignore included the .rspec file. As a result, my local spec runs would pass but my CI spec runs would fail with an error saying it couldn't load my model classes.
Any way rspec-rails could either change the default require for rspec or ensure the .rspec file is not ignored or change the spec rake task to require the rails_helper by default?

We don't auto-require anything by default.  spec_helper and rails_helper are just standard conventions for how to organize things (and thus a good starting point from generated files).  It's entirely up to you how you want to manage that (e.g. by putting requires at the top of each file, or having a --require option in .rspec, or some other way).  Given that we don't want to force these things on users and we also don't want to couple ourselves to git (which any .gitignore logic would do), I don't think there's anything we can or should do about this.
Note that we do not recommend gitignoring .rspec.  That file is intended to be under source control.  A developer's personal project preferences can go in a git-ignored .rspec-local file.

Gotcha. So it's my mistake. Each of my spec files should be requiring rails_helper if they are rails dependent files. Makes sense.
Adjusted my .rspec as well.
Thank you.


Add comments hotkey for the Playground

The comments hotkey Cmd + / (Ctrl + / for Windows) is very common editors feature --- would be cool to have it for the Langium Playground.

I think this is supported in Monaco + Langium as is? @kaisalmen do you know more about this? Or perhaps it's necessary to add additional handling 🤔 . I've also noticed that it doesn't work as expected in Monaco at times, but I swear it did back in Sept. when I was preparing things for MiniLogo in the web.

There seem to be issues. CTRL + K works in the build in TypeScript editor, but there also CTRL + / does not work. Seems to be a more general issue. I have to investigate

It could be related to the general problems of handling keyboard layouts in the browser. We have made quite a lot of effort to get it right in Theia: https://github.com/eclipse-theia/theia/pull/4724

This works now, closing as resolved.


Dependabot encountered an unknown error

Is there an existing issue for this?

[X] I have searched the existing issues

Package ecosystem
nuget
dependabot.yml content
dependabot.txt
What you expected to see, versus what you actually saw
instead of rising new PRs we see error in dependabot logs:
updater | Dependabot encountered '5' error(s) during execution, please check the logs for more details.
updater | +------------------------------------------------------+
updater | |            Dependencies failed to update             |
updater | +--------------------------------------+---------------+
updater | | xunit.runner.visualstudio            | unknown_error |
updater | | prometheus-net.AspNetCore            | unknown_error |
updater | | Microsoft.EntityFrameworkCore.Design | unknown_error |
updater | | xunit                                | unknown_error |
updater | | WireMock.Net                         | unknown_error |
updater | +--------------------------------------+---------------+
Full logs:
logs.txt
It started happening since last week. At around same time we started using Github Enterprise (with sso) and our own runners (but no runner has dependabot label). Nothing was changed in dependabot.yml file. We see the error for most of the repositories we have

opened ticket with github support as well. issue still persists...

Relevant log lines:
updater | Running for project [/home/dependabot/dependabot-updater/repo/Space.Service.CoreApiFacade.UnitTests/Space.Service.CoreApiFacade.UnitTests.csproj]
updater |   Running for SDK-style project
updater | dotnet build in GetAllPackageDependenciesAsync failed. STDOUT: MSBuild version 17.8.3+195e7f5a3 for .NET
updater |   Determining projects to restore...
updater | /tmp/package-dependency-resolution_R21OCk/Project.csproj : error NU1101: Unable to find package Space.Service.Common.CodeAnalyzers. No packages exist with this id in source(s): nuget.org
updater |   Failed to restore /tmp/package-dependency-resolution_R21OCk/Project.csproj (in 10.16 sec).
updater |
updater | Build FAILED.
updater |
updater | /tmp/package-dependency-resolution_R21OCk/Project.csproj : error NU1101: Unable to find package Space.Service.Common.CodeAnalyzers. No packages exist with this id in source(s): nuget.org
updater |     0 Warning(s)
updater |     1 Error(s)

Can you share any NuGet.Config files in the repo?  The updater is only looking at nuget.org for what appears to be a non-public package.

there is no Nuget.Config. We are using GitHub Nuget Registry and we have specified credentials for it in the dependabot.yaml file.
In fact yes, it is looking for private packages on public nuget, but the error does not contain any private package:
updater | Dependabot encountered '5' error(s) during execution, please check the logs for more details.
updater | +------------------------------------------------------+
updater | |            Dependencies failed to update             |
updater | +--------------------------------------+---------------+
updater | | xunit.runner.visualstudio            | unknown_error |
updater | | prometheus-net.AspNetCore            | unknown_error |
updater | | Microsoft.EntityFrameworkCore.Design | unknown_error |
updater | | xunit                                | unknown_error |
updater | | WireMock.Net                         | unknown_error |
updater | +--------------------------------------+---------------+

Looking through the logs, the custom github nuget feed is never queried, which makes me think the updater is only considering sources from a NuGet.config file, and since that file doesn't exist, it falls back to api.nuget.org, so the problem is probably that the feeds specified in dependabot.yml aren't being considered.  I'll keep digging to see if I can figure it out.

I created issue #8721 to track this.

@PoteRii this should be fixed in #8721 now; can you confirm resolution please?

@abdulapopoola hello, private nuget works, but now we have a different error for which we`ve opened github tichket

It still seems broken for msbuild based projects

Sorry to hear that and glad to hear you've opened up a ticket. Closing this out based on the resolution of the primary issue.
@probitdavid ; I do apologize about the regression; we do have folks working round the clock to address the nuget issues. It's a top priority for us to ship fixes.


result list styles are broken on books list

the styles for the results list on the books search page are broken. have a look at production and you can see the problem immediately: giant green triangles, everything out of place, etc.
they should look like the design. note that the search form isn't built on this page; we're just dealing with the actual list of results currently.

@thatbudakguy @rlskoeser Ok I am done with design testing the test site using Safari, Chrome, and Firefox on the office desktop screen, the office iPad Air 2, and my iPhone SE.
Desktop: All browsers are fine. However, no publisher and content format information on the right column is showing and some names are in parenthesis, noting FWIW.

Tablet: All browsers are fine. However, no publisher and content format information on the right column is showing and some names are in parenthesis, noting FWIW.

Mobile: All browsers are fine. However, no publisher and content format information on the right column is showing and some names are in parenthesis, noting FWIW.

I don't think we actually have that information in the database now, so it's not supposed to appear yet. Think this is OK to close.


[OTHER] nopugmode.js file missing

In the documentation, it says there's some example of usage without templates in noPugMode.js but I can't seem to find that file.

file is here: https://github.com/RosaeNLG/rosaenlg/blob/master/packages/rosaenlg/test/test-rosaenlg/noPugMode.js
it's called noPugMode.js, but it looks like github is unable to find it using the search engine

Thank you


flakes: use stable release branches for nixpkgs inputs

Copy of commit msg
This is the best practice for Flakes or clients of nixpkgs in general.
The release-<YY.MM> branch is actually a dev branch:
Hydra continually tests the tip of this branch.
When the tests succeed, the nixos-<YY.MM> release branch is updated to point to the succeeding commit.
release-<YY.MM> is to nixos-<YY.MM> what master is to nixpkgs-unstable.
See also: https://github.com/NixOS/nixpkgs/blob/e88fb997e32982a5f37b933583e618265a32d85d/CONTRIBUTING.md#flow-of-merged-pull-requests

Thanks!