Broken Link on Homepage Card for "DB Integration"

Hi,
I noticed an issue on the homepage of your website. When I clicked on the card labeled "DB Integration," it redirected me to a page that displays "404 Not Found."
Steps to Reproduce:
Go to the homepage of the website.
Locate the card for "DB Integration."
Click on the card.
Observe the 404 error page.
Expected Behavior:
The card should redirect to the relevant page with information or functionality for "DB Integration."
Actual Behavior:
The link redirects to a page showing "404 Not Found."
Additional Context:
Browser: [Add your browser and version, e.g., Google Chrome 117.0]
OS: [Add your operating system, e.g., Windows 11]
URL: [Provide the link to the homepage where you found the issue]
I hope this helps you identify and resolve the issue! Let me know if you need any more details.
Thanks!

I think this is Nginx configuration error.

Hey @menaehab @Anhunghezo thanks for pointing out this error, I will fix it today


feat(prometheus): Add Prometheus collector

This patch introduces a custom Prometheus collector, allowing users to subscribe to a designated endpoint for accessing insights derived from Chainloop metadata and instrumentation. The goal is to establish a unified access point for creating Grafana dashboards and alerts, leveraging Alert Manager and other integration options.
Specifically, this patch implements a new Prometheus service that exposes an endpoint /prom/{org_name}/metrics. Users can configure their Prometheus instances to begin collecting data specific to their Chainloop organization from this endpoint.
For this initial approximation, only one metric is emitted: chainloop_workflow_up that indicates for each workflow in the organization, its latest run was successful or not.
Remember the endpoint is authenticated and you might need to create an API Token to access the information. Example of Prometheus configuration yaml.
global:
  scrape_interval: 15s
  scrape_timeout: 10s
  evaluation_interval: 15s
runtime:
  gogc: 75
alerting:
  alertmanagers:
    - follow_redirects: true
      enable_http2: true
      scheme: http
      timeout: 10s
      static_configs:
        - targets: []
scrape_configs:
  - job_name: chainloop-metrics
    honor_timestamps: true
    track_timestamps_staleness: false
    scrape_interval: 15s
    scrape_timeout: 10s
    scrape_protocols:
      - OpenMetricsText1.0.0
      - OpenMetricsText0.0.1
      - PrometheusText0.0.4
    metrics_path: /prom/read-only-demo/metrics
    scheme: http
    bearer_token: API_TOKEN
    enable_compression: true
    static_configs:
      - targets:
          - localhost:8000

On there you can see how the job chainloop-metrics has as metric_path /prom/read-only-demo/metrics indicating the target organization is read-only-demo and bearer_token with a valid API Token configuration.
Refs #1098

Added a small bit to include the prometheus integration in the Chart configuration and bump the chart version


Fix UtxoInterface and test via fetchPrevoutAndTryToUnblindUtxo method

The return value from Esplora has changed but UtxoInterface has not been updated.
This PR add the missing fields and test the interface via fetchPrevoutAndTryToUnblindUtxo method.
Please review @tiero @louisinger

This opens up a good point: is the current design of UtxoInterface covering to much?
ie. it has fields which are used internally (ie. unblindData, prevout) menwhile is also used as return type of fetchPrevoutAndTryToUnblindUtxo


ConfigureRequestContainer vs ConfigureApplicationContainer

This is a question about defaults in IoC registration (not a bug).
I have read all google'able documentation about using the default container in Nancy, including the wiki, stackoverflow, and TinyIoC docs.
First let's see if I understand correctly:

When overriding ConfigureApplicationContainer, every registered interface will get a singleton lifetime, and every registered class type will get a multiple instance lifetime. The latter meaning each type request will get a new object.
When overriding ConfigureRequestContainer, the previous lifetimes are scoped to the request (à la Asp.Net).

And now some True/False? statements:

Modules are registered multi-instance, and are resolved just once per-request. Thus, if the dependency-tree of the module only need to resolve class types exactly once, then doing all registrations in ConfigureApplicationContainer achieves the same behavior than doing it in ConfigureRequestContainer.
Following 1., if we add the .AsMultiInstance() extension to interface registrations, then we also get a resolution per request but only using ConfigurationApplicationContainer override.
The default behavior of Nancy registration could be considered dangerous when registering interfaces in ConfigureApplicationContainer with types that hold state in a multi-threaded environment (asp.net). Typical example MyBusinessThingsRepository. Thread-safety should be analyzed for those types.
ConfigureRequestContainer is only needed when you need multiple resolutions of the same dependency within a single request, and you want the same object to be returned (i.e. singleton within the request).

If all above is right (miracle!), then I would say that default behavior and also "AutoRegister" is a bit confusing and could lead to mistakes in common cases (sharing a non-thread-safe object as a singleton).
It may be safer to default to multiple instance lifetime allways.
I suspect I am not considering cases where a dependency is resolved several times within the same request. It seems a pretty uncommon case that may be resolved with a third method extension (AsRequestSingleton()). Then a ConfigureRequestContainer would not be needed.

When overriding ConfigureApplicationContainer, every registered interface will get a singleton lifetime, and every registered class type will get a multiple instance lifetime. The latter meaning each type request will get a new object.

Yes, this is correct, unless you explicitly specify the lifetime when you register stuff.

When overriding ConfigureRequestContainer, the previous lifetimes are scoped to the request (à la Asp.Net).

The request container is a request-scoped container, that "inherits" the registrations from the application container. That means

Application singleton -> one single instance is resolved during the lifetime of the entire application
Application transient -> a new instance is always resolved each time
Request singleton -> one single instance is resolved during the lifetime of the request
Application transient -> same as "Application transient"

It also means that each of the registration lifetimes can resolve stuff from all the "scopes" above them in the list.

Modules are registered multi-instance, and are resolved just once per-request. Thus, if the dependency-tree of the module only need to resolve class types exactly once, then doing all registrations in ConfigureApplicationContainer achieves the same behavior than doing it in ConfigureRequestContainer.

Modules are registered as "request singletons", which means only one instance of a module will ever exist during the lifetime of a request. This doesn't really matter much, because Nancy will always just resolve a single instance of a module anyway.

Following 1., if we add the .AsMultiInstance() extension to interface registrations, then we also get a resolution per request but only using ConfigurationApplicationContainer override.

AsMultiInstance (or as I call it; "transient") means that you get a new instance every time you ask for it. It doesn't matter whether these are registered in the application or request container.

The default behavior of Nancy registration could be considered dangerous when registering interfaces in ConfigureApplicationContainer with types that hold state in a multi-threaded environment (asp.net). Typical example MyBusinessThingsRepository. Thread-safety should be analyzed for those types.

Yes. Singleton services live from they're first resolved until the application is killed. This means, if they have state, they should be thread-safe.

ConfigureRequestContainer is only needed when you need multiple resolutions of the same dependency within a single request, and you want the same object to be returned (i.e. singleton within the request).

Yes, kinda. As mentioned earlier; transient registrations will always return a new instance, so it doesn't matter much if they're registered in the application- or request-scoped container. The only exception is if you have transient services that need access to other request-scoped services. Then you have to register them in the request container, because the registrations won't be available in the application container.

I would say that default behavior and also "AutoRegister" is a bit confusing and could lead to mistakes in common cases (sharing a non-thread-safe object as a singleton).
It may be safer to default to multiple instance lifetime allways.

To be honest, I'm not really sure how TinyIoC auto-registers stuff, because I've always disabled it (because of performance and control), but I guess you're right. I don't think we've received a lot of feedback on this, though, so I'm not sure it's a big problem. People generally tend to avoid keeping state in web applications these days.

It seems a pretty uncommon case that may be resolved with a third method extension (AsRequestSingleton()). Then a ConfigureRequestContainer would not be needed.

Several containers (and bootstrappers) support this already. I.e. Autofac has a InstancePerRequest method.

Thanks, Kristian. I can not extend my experience to other projects, but It took me some time to figure this out. In particular, the default lifetime for objects in the registrations. If you think it might add some value I could try to improve the documentation at Bootstrapping-nancy.

In particular, the default lifetime for objects in the registrations.

Yeah, personally I would never rely on either the implicit lifetimes, nor the auto-registration. It's just "too magic" to me. It's not my call, though :wink:

If you think it might add some value I could try to improve the documentation at Bootstrapping-nancy.

Sure, knock yourself out! We always appreciate documentation work :heart:


Fix "no-redeclare" issue in lib/client.js

'http_request' is already defined.
https://codeclimate.com/github/sendgrid/nodejs-http-client/lib/client.js#issue_59f5551205f9300001000024

Fixed with PR #70

Fixed by https://github.com/sendgrid/nodejs-http-client/pull/61


change readme

change readme

Codecov Report

Merging #1 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master       #1   +/-   ##
=======================================
  Coverage   53.96%   53.96%
=======================================
  Files           4        4
  Lines         126      126
  Branches       12       12
=======================================
  Hits           68       68
  Misses         58       58

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 5e7dab6...a351173. Read the comment docs.


Bug bounty test - PLEASE DO NOT APPROVE. ldrvbm

Bug bounty test - PLEASE DO NOT APPROVE. ldrvbm

nice try


Why retention policy can't be shorter than/must be at least 1 hour?

Hello,
I'm wondering why you can't CREATE RETENTION POLICY shorter than 1 hour.
> USE testdb
Using database testdb
> CREATE RETENTION POLICY foo ON testdb DURATION 30m REPLICATION 1
ERR: retention policy duration must be at least 1h0m0s

As for why, well, the ease of testing.
Thanks.

I'll guess is because DROP has a high cost in influx and you don't want to be removing stuff that often.

Dropping due to retention enforcement is actually low cost, since it's just the deletion of files.
We had to have some minimum duration since we wanted to prevent nonsensical stuff like retention durations of, say, 1 millisecond.
InfluxDB is open-source. You can always change the minimum yourself and build. :-)
https://github.com/influxdb/influxdb/blob/master/meta/data.go#L23

@otoolep that doesn't really make sense, but given you reply ... whatever. I feel sorry for asking.

Realize this is an old thread but there's a very big difference between 1 millisecond as a min retention time and 1 hour. The latter makes it difficult to write a quick test, because I have to wait an hour to see if the data was deleted.

I accept that time-driven tests are important, you can potentially mock out the time package somehow, and force its time forward.

@otooltep I don't know how to do that. I don't even know GoLang.

This is old, but I also don't see why there should be a minimum of 1h... For testing purposes it's very annoying. Hell, even 1ms, that choice should be left up to the user...

This is old, but I also don't see why there should be a minimum of 1h... For testing purposes it's very annoying. Hell, even 1ms, that choice should be left up to the user...


Docker container: XDebug enabled even though explicitly disabled

Describe the Problem
XDebug tries to connect to a server even though it is disabled through an environment variable
To Reproduce
My .gitlab-ci.yml config:
.only-default: &only-default
  only:
    - master
    - develop
    - merge_requests

build-dev:
  <<: *only-default
  variables:
    DDEV_XDEBUG_ENABLED: "false"
  stage: build
  image: drud/ddev-webserver:v1.17.2
  before_script:
    - echo "${DDEV_XDEBUG_ENABLED}"
    - composer --version
    - composer config gitlab-token.gitlab.com $PERSONAL_ACCESS_TOKEN

    - mkdir -p $CI_PROJECT_DIR/.cache/yarn && yarn config set cache-folder $CI_PROJECT_DIR/.cache/yarn
    - yarn cache dir
  script:
    - composer install --no-progress --no-ansi --no-interaction
  artifacts:
    name: build
    paths:
      - ./public/
      - ./vendor/
      - ./.cache/
      - ./composer.json
      - ./composer.lock
    expire_in: '1h'
  tags:
    - docker

results in the following output on gitlab.com:
Running with gitlab-runner 13.11.0 (7f7a4bb0)
  on verdi zRkhyC6s
Preparing the "docker" executor
00:02
Using Docker executor with image drud/ddev-webserver:v1.17.2 ...
Pulling docker image drud/ddev-webserver:v1.17.2 ...
Using docker image sha256:c06746f5cd03eabf5eb2655b69d6487c71041f5f642b6e594db46a2fa799bfdb for drud/ddev-webserver:v1.17.2 with digest drud/ddev-webserver@sha256:48af9655e35aab11415dd422d305f61c347ead2a755fc5c2c2441d5b39fba164 ...
Preparing environment
00:00
Running on runner-zrkhyc6s-project-23514596-concurrent-0 via verdi...
Getting source from Git repository
Fetching changes with git depth set to 50...
Reinitialized existing Git repository in /builds/xxx/xxx/.git/
Checking out de313363 as refs/merge-requests/640/head...
Removing .phplint-cache
Skipping Git submodules setup
Executing "step_script" stage of the job script
00:27
Using docker image sha256:c06746f5cd03eabf5eb2655b69d6487c71041f5f642b6e594db46a2fa799bfdb for drud/ddev-webserver:v1.17.2 with digest drud/ddev-webserver@sha256:48af9655e35aab11415dd422d305f61c347ead2a755fc5c2c2441d5b39fba164 ...
$ echo "${DDEV_XDEBUG_ENABLED}"
false
$ composer --version
Xdebug: [Step Debug] Could not connect to debugging client. Tried: host.docker.internal:9000 (through xdebug.client_host/xdebug.client_port) :-(
Composer version 2.0.13 2021-04-27 13:11:08
$ composer config gitlab-token.gitlab.com $PERSONAL_ACCESS_TOKEN
Xdebug: [Step Debug] Could not connect to debugging client. Tried: host.docker.internal:9000 (through xdebug.client_host/xdebug.client_port) :-(
$ mkdir -p $CI_PROJECT_DIR/.cache/yarn && yarn config set cache-folder $CI_PROJECT_DIR/.cache/yarn
yarn config v1.22.10
success Set "cache-folder" to "/builds/xxx/xxx/.cache/yarn".
Done in 0.02s.
$ yarn cache dir
/builds/xxx/xxx/.cache/yarn/v6

As you can see, xdebug tries to make a connection so it is enabled!
Any idea how to fix it?

I would not use this image for CI. Please check the repo of the Q&A team how to setup your workflows properly see https://github.com/TYPO3-Documentation/tea. Also check the related Slack channel https://typo3.slack.com/archives/CSQ8T0VS5

i tried it with environment but then gitlab complained about invalid yml. I wonder why xdebug is enabled by default. On my local ddev environment I always need to activate it manually after restart.

Well, you have to figure out how to use your system to get environment variables into the container. Since you don't even give context about how you're using it, it's hard to help.
xdebug is enabled by default because people begged for it in https://github.com/drud/ddev/issues/2245

As I said, this is my GitLab CI config.

xdebug is enabled by default

I see, it's not a bug, it's a feature :facepalm:

I don't know anything about your gitlab ci, but you have to introduce the environment variable into the container, not just enable it outside the container. If you want to pursue this, you have to figure out how to do that. There are many other techniques you can use as well (like a build stage that would change it).


Minor bug in the code for torch_unet_kvasir, which leads to run-time error due to CUDA, if running on CPU mode.

In the openfl/openfl-workspace/torch_unet_kvasir/code/fed_unet_runner.py
Line23 : It should be
def __init__(self, device='cpu', **kwargs):
Instead of
def __init__(self, device='cuda', **kwargs):
This seems to be a typo, as in the description it is written that the default device is set to be 'cpu'.
Without this change, one would encounter a run-time error due to CUDA not found.

@saransh09 thanks for bringing this up! Fixed in https://github.com/intel/openfl/commit/65728d8b09ea45092cef91f11127021288b5ae20 .

@alexey-gruzdev can you please make this fix in the main branch as well?
I have to prepare for a demo, and when I fresh pip install the library, this problem persists. I guess pip pulls the code from main branch, if I am not wrong.

@saransh09 we are preparing new release package and as a part of this activity we will merge develop in master and fix also will be available through pip. Stay tuned, we should have it pretty soon.


Instagram is not working

I was tried instagram in your demo site, but it through below errors.
{"code": 400, "error_type": "OAuthException", "error_message": "Redirect URI does not match registered redirect URI"}

Hello armsmani,
Did you resolve this situation in your IG account? If so, I get the same error, could you let me know your solution to get past it? Thanks!


check that nh slides look correct

Reel_2_Story slides have some slides that are inverted and some that are not inverted. we should use these to check that our code is correct

[x] checking our invert algorithm vs theirs

result: ours is brighter :(

get base game slide for Reel_2_Story (in cinder isles) to see Slide_2_Story_01_01.png
put Slide_2_Story_01_Vision_01.png on a nh slide
see if they look the same (that means the way we invert is the same as way they invert)

[x] (less important) check vision vs non vision

use the non inverted slide (like Slide_2_Story_01_Vision_01.png) on a vision torch (standing or target)
use the inverted slide (like Slide_2_Story_01_01.png) on a reel
check that they look the same on both

now that i see this issue, i did notice that my nh-generated reels are brighter than base game's, and i would have to darken the images themselves to achieve a similar brightness as base game.
here i attached an example reel from echoes of the eye i reimported into the game through new horizons. you may notice the darker images look more natural when inserted into the projector, but are dark on the actual reel model.
Homeworld.zip

nh slide reel

base game slide reel

vision torch is a much more direct png to in-game transition. we dont have to do anything to make it look right there

ive decided that the current thing nh does (darkening images via marking them as linear) is a good enough. it could darken them in different ways, but its fine
the goal should be to make the in game slides match the source pngs. making them match base game is secondary because base game severely darkens the source image, which we shouldnt make users do


Integration with TitleStrategy

Could be nice to avoid users to migrate to setting the client using the lib if they're using a TitleStrategy already
To take into account: Route.title

Moving to https://github.com/davidlj95/ngx/discussions/253


Add PIL image rotation according to exif info (PR 3779 alt)

What changes are proposed in this pull request?
Introduce exif orientation support when importing images into a dataset - see https://github.com/voxel51/fiftyone/issues/3778
How is this patch tested? If it is not, please explain why.
Tested on the code posted in the Issue linked above.
Before the fix image dimensions are flipped and annotation is displayed in the wrong position:

After the fix dimensions are correct and annotation is displayed in the correct position:

Release Notes
Is this a user-facing change that should be mentioned in the release notes?

[x] No. You can skip the rest of this section.
[ ] Yes. Give a description of this change to be included in the release
notes for FiftyOne users.

What areas of FiftyOne does this PR affect?

[ ] App: FiftyOne application changes
[ ] Build: Build and test infrastructure changes
[x] Core: Core fiftyone Python library changes
[ ] Documentation: FiftyOne documentation changes
[ ] Other

Thank you @Fraccalo for the contribution! and again apologies for messing up your original PR.
I took the concept across the finish line by adding a test and adapting the source code of exif_transpose() so that we correct the width and height dimensions without having to open and transpose the whole image.

Thank you @Fraccalo for the contribution! and again apologies for messing up your original PR. I took the concept across the finish line by adding a test and adapting the source code of exif_transpose() so that we correct the width and height dimensions without having to open and transpose the whole image.

that's brilliant, thanks for the update :)


BBI: Should the covariate estimator be fitted on the training or test set ?

The covariate estimator $\hat{\mathcal{E}}[X^j|X^{-j}]$ is currently fitted and used for predicting on the test set:
https://github.com/mind-inria/hidimstat/blob/7c3af80e501e2c448dd7b1dbf21f1159c17c514b/hidimstat/compute_importance.py#L251-L265
This could lead to overfitting on the test set and underestimating the conditional importance of covariate $j$.
Another solution suggested by Ahmad would be to cross-fit on the test set. This could on the contrary lead to poorer fit of the covariate estimator compared to methods like LOCO that leverage the entire train set for accounting for correlations.
Also, I find the naming importance_estimator a bit misleading. It reminds me of the method used for importance estimation (LOCO, SHAP, CPI...) but actually corresponds to the estimator used in CPI to predict $X^j$ from $X^{-j}$

Thx. This should be addressed in 2 PRs.


Cmake changes

These changes are tested with CMake 3.5.2 but I tested with cmake_policy(VERSION 2.8), so it should work for the minimum required version. However, I think it would be useful to update the minimum required version of CMake as a lot of useful stuff has been introduced since then. BTW using at least 3.1 will make the policy CMP0054 if-clause obsolete.
Here is what this patch does:

Provide an INSTALL target also for MSVC
Use message(STATUS "...") wherever it is not an error or warning to allow spotting of errors in CMake output easier.
Allow a possible toolchain file to set  ${TOOLCHAIN_COMPILER_FLAGS} in CMake in order to introduce toolchain specific (additional) compiler flags. If this variable is not set, nothing changes.
In WIN32, change the name of the static library to g3logger_static when the DLL is also built. On WIN32 the DLL should be the default (I would even suggest removing the static library alltogether or at least remove the option for adding the DLL and add it always), as usually one will use g3log across multiple DLLs in one project and ensure that every DLL uses the same logger (g_logger_instance).
Not sure, BTW, about the behavior on Linux if several shared libraries use the static lib and are part of one executable. Maybe the situation is similar and the static library should be removed all together?
Moved the generated header file out of the source tree to enable building for several platforms with different settings out of the same source without the need to re-compile (or: ensure that cmake re-runs when changing platforms). The header is installed with the rest to the /include subdir. The include paths for the compiler are adjusted to find the generated header. Technically the include statement should probably be changed to use <> instead of "".

I did not test this on linux very well as I only compile on Windows and for Win32, Win64 and my very vendor specific ARM platform but I tried to make sure that nothing changes on Linux with this patch.

please pull latest from masters so the travis build works

We usually put the install directive next to where the target is created (in fact we usually create our targets with custom scripts that take care of all that).
Thus when you add new targets in subdirectories or tie some subdirs into another cmake project as externals the master files do not need to be edited. It seems common practice and makes sense to me.
In this particular case I could leave the rest of the CPack file untouched and make sure that windows sees the install directive.

@AndreasSchoenle  please see the conflict and the PR that caused it: https://github.com/KjellKod/g3log/pull/145

Became obsolete, as shared library is now the default.

Thanks
Please see the raised issues however.
There were people using the static line so I'll bring the static build option back again

OK. Not sure what you meant by raised issues? Static as an option is quite ok in my opinion. Would you introduce it as an option?
See comment in other merge request.

@AndreasSchoenle  would you mind opening up a new pull request that only adds the windows install target as that is currently missing?


[BUG] 530 Documentation

I think there is a mistake in the ITU 530 documentation for the function XPD_outage_precipitation; it's description is the same as XPD_outage_clear_air:

PD: Thanks for the hard work!

Thanks for reporting this, It has been fixed now.


feat: extend datasource reconnect modal tooltip to include title

Pull Request Template
Use this template to quickly create a well written pull request. Delete all quotes before creating the pull request.

Description

Show tooltip when user hovers over datasource title or icon in DatasourceReconnectModal. Previously, the tool tip only showed when the icon was hovered over. This fixes that.
Please include a summary of the changes and which issue has been fixed. Please also include relevant motivation
and context. List any dependencies that are required for this change
Links to Notion, Figma or any other documents that might be relevant to the PR

PR fixes following issue(s)
Fixes #28008
Media
Type of change

Please delete options that are not relevant.

New feature (non-breaking change which adds functionality)

Testing

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Also list any relevant details for your test configuration.
Delete anything that is not relevant

[ ] Manual
[ ] JUnit
[ ] Jest
[x] Cypress

Test Plan

Add Testsmith test cases links that relate to this PR

Issues raised during DP testing

Link issues raised during DP testing for better visiblity and tracking (copy link from comments dropped on this PR)

Checklist:
Dev activity

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[ ] PR is being merged under a feature flag

QA activity:

[ ] Speedbreak features have been covered
[ ] Test plan covers all impacted features and areas of interest
[ ] Test plan has been peer reviewed by project stakeholders and other QA members
[ ] Manually tested functionality on DP
[ ] We had an implementation alignment call with stakeholders post QA Round 2
[ ] Cypress test cases have been added and approved by SDET/manual QA
[ ] Added Test Plan Approved label after Cypress tests were reviewed
[ ] Added Test Plan Approved label after JUnit tests were reviewed

/build-deploy-preview

/build-deploy-preview

/ok-to-test


Poteto.RunTLS(addr, cert, key) starts https server

Change

You can start https server with certfile and key

How to use
cert := []byte("hello")
key, _ := os.ReadFile("./_fixture/certs/key.pem")
p := New()
p.RunTLS("8080", cert, key)

Issue
https://github.com/poteto0/poteto/issues/79
Version
It will be included >=0.26.0.

https://github.com/poteto0/poteto/issues/143


software could not be found on any servers at this time / Need help with package creation

I am trying to implement this, but always the error: software could not be found on any servers at this time
Can you maybe provide a step-by-step instruction with screenshots on how to get there and how to build for example a notepad++ package? I swear, I am trying this for hours and cant get it work.

https://github.com/Romanitho/Winget-Install/discussions/59#discussioncomment-7444310

#59 (comment)

Thanks, but this is for Intune and I meant SCCM, sorry.

Same. Just use powershell.exe instead of the sysnative path.

Thanks, but this is for Intune and I meant SCCM, sorry.

I'll create a step-by-step instruction with screenshots when I'm at work again (I have in the moment 20+ WinGet-apps Available for users to self install/uninstall both in System as User context through Software Center)

Klogg (WinGet) as Available application in SCCM (installs in System context) via %ProgramData%\winget-install.ps1:

powershell.exe -NoProfile -ExecutionPolicy Bypass -File %ProgramData%\winget-install.ps1 -AppIDs variar.klogg
powershell.exe -NoProfile -ExecutionPolicy Bypass -File %ProgramData%\winget-install.ps1 -AppIDs variar.klogg -Uninstall

Available application

And as the original Uninstall uses dialogs (requires WAU if no Uninstall Content is used):
C:\ProgramData\Winget-AutoUpdate\mods:
variar.klogg-uninstall.ps1
<# ARRAYS/VARIABLES #>
#Beginning of Process Name to Wait for to End - optional wildcard (*) after, without .exe, multiple: "proc1","proc2"
$Wait = @("Un_A")

<# FUNCTIONS #>
. $PSScriptRoot\_Mods-Functions.ps1

<# MAIN #>
if ($Wait) {
    Wait-ModsProc $Wait
}

<# EXTRAS #>

Smart. You deploy winget-install.ps1 with another app on the Programdata. This way, you only maintain it once... 🤩

Smart. You deploy winget-install.ps1 with another app on the Programdata. This way, you only maintain it once... 🤩

Thanks!
Yes, WAU rolls out on all or domain computers, winget-install.ps1 is a part of it.
When upgrading WAU (and if winget-install is newer) that too gets a new file.

...thinking of it; could actually be a part of WAU to.. ..when a new release is created it could pull the latest winget-install.psi from that Repo...

wooow thank you verry much!

Or I was thinking about that from a while, but we can add the install feature to WAU and create a kind of 'all in one' tool for winget packages...

a kind of 'all in one' tool for winget packages...

Winget-Install-GUI too...

Possibly

Hi there
Thank you very much for your detailed instruction. This worked on a "older" machine, where winget worked before.
But I have the following problem:
When I pxe boot/install a new client with SCCM/MECM, WinGet seems not to work.
When you call winget in a terminal after fresh new-install, it seems to work, but if you type in for example winget search notepad or winget install notepad++.notepad++ it wont load.
When you try to force update or reset the winget source, it wont work.
Only if you open the Microsoft Store and update winget there manually, winget finally works.
But at this step its too late for my task sequence, cause I added a few winget-install packages and they could not be installed until I update winget in the Microsoft Store manually.
Might you help here?
Thanks!

I can't help, but I can explain.
When I get home.

Prerequisites for the modern WinGet are:

Visual C++ 2019 or 2022
Microsoft.VCLibs.140.00.UWPDesktop (Server 2019 cant install that but WinGet runs without problems...)

The latest winget-install.ps1 takes care of it and pre-installs them on a client/server.
It also updates WinGet to the latest version by checking the tag_name at: https://api.github.com/repos/microsoft/winget-cli/releases/latest
So, you can use that to test (should work for installing in System context):

Download v1.11.1 Pre-release
Download the latest RAW winget-install.ps1 and replace the one in the Pre-release

When a new client (Win10 and probably even Win11?) is deployed the "WinGet" is a very old version before it got named winget.exe.
That's why it doesn't work until the Store updates to the latest WinGet from User context (updating the machine WinGet and creating som kind of SymLink under %LocalAppData%\Microsoft\WindowsApps\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe).
The Store can't be initialized until an user has logged on once.
So, for using WinGet as a deployment installer there are some caveats:

Your deployment network needs to be able to access the whole world (not recommended at all!)
Anything can happen when installing/uninstalling WinGet apps, they'll need to be extremely well tested
WinGet itself can hang/crash/burn/stall...

So, the only recommended way of using this is to keep WinGet apps away from deployments!

The plan is to implement winget-install as a new feature to WAU, because it uses the same functions...
It will became the WAU Tools, or something like that 😅
This way, our tools will be easier to maintain. The idea is that if someone uses winget-install, it means it does probably use WAU as well,  as it exists a lot of ways to implement winget apps in intune or MECM.
So for me it makes sense that it should become an all-in-one tool 😊

But, then you must have a way to not install it during SCCM task sequence (security, locked down deployment network) or set the task to ignore this install fail (can't reach internet) or install the prerequisites and WinGet before WAU.
My organisation has the ability to mark those applications that cannot install during deployment.

Yes, install WAU first, which will install all prerequisites. Then install apps.
Continue the task if it fails, but report those failing apps.
You can even use mods to install a default app once if winget-install fails. Obviously, the app will not be up to date, but at least you have all the apps at the end of the TS. WAU will catch things up when available.

Download v1.11.1 Pre-release
Download the latest RAW winget-install.ps1 and replace the file from the Pre-release (@Romanitho maybe a new one? )
Wait for the next Stable release before using it in a production environment

Now:

Download v1.11.2 😍


Replace quarkus.camel.native.resources.* with quarkus.native.resource…

…s.* fix #988

I guess we should do a scan of the example projects and clean this up over there too.

Indeed, I wanted to, ... and forgotten. Thanks for the reminder!

Fun fact: quarkus.native.resources.includes honors trailing white space in the value, while quarkus.camel.native.resources.include-patterns used to strip it. That's why the stringtemplate test failed.

I guess we should do a scan of the example projects and clean this up over there too.

Indeed, I wanted to, ... and forgotten. Thanks for the reminder!

I checked and there were no occurrences of quarkus.camel.native.resources.


filter, sort, weight and some other typesense search options have not been implemented yet?

I would like to know if this is a work in progress? Or am I not finding the right code.

Hi @fireindark707  👋 it's still WIP. If you have something in mind and want to add, feel free to PR. Thank you for asking.

hi @fireindark707, i've bumped the version to include filter and sort (see the recent version). LMK if this helps.


BVS-6565 router policy look and feel enhancements

Reviewer: @wolverineav

make diagonal entries hyphenated
show nexthops in conflicted policies modal
display not one, but all conflicting policies in the conflict modal
allow any-any to be clickable

Refer to this link for build results (access rights to CI server needed):
https://jenkins.bigswitch.com/job/openstack_horizon_bsn_pull_req/90/

Refer to this link for build results (access rights to CI server needed):
https://jenkins.bigswitch.com/job/openstack_horizon_bsn_pull_req/91/

Refer to this link for build results (access rights to CI server needed):
https://jenkins.bigswitch.com/job/openstack_horizon_bsn_pull_req/92/


In CloudStack, when creating an instance, the security group is not applied, and there are errors reported by iptables.

ISSUE TYPE

Bug Report

COMPONENT NAME

Security groups,iptables

CLOUDSTACK VERSION

cloudstack <IP_ADDRESS>

CONFIGURATION

OS / ENVIRONMENT

Centos 7.9
SUMMARY

A newly deployed CloudStack <IP_ADDRESS> agent node is experiencing issues where the security group rules are not being applied to the created instance machines. Additionally, there are errors reported by iptables.
STEPS TO REPRODUCE

2024-08-23 14:35:26,306 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-3:null) (logid:20080328) Failed to get dom xml: org.libvirt.LibvirtException: Domain not found: no domain with matching name 'i-2-5292-VM'
2024-08-23 14:35:26,308 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-3:null) (logid:20080328) Failed to get dom xml: org.libvirt.LibvirtException: Domain not found: no domain with matching name 'i-2-5292-VM'
2024-08-23 14:35:26,309 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-3:null) (logid:20080328) Failed to get dom xml: org.libvirt.LibvirtException: Domain not found: no domain with matching name 'i-2-5292-VM'
2024-08-23 14:35:26,310 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-3:null) (logid:20080328) Executing: /usr/share/cloudstack-common/scripts/vm/network/security_group.py destroy_network_rules_for_vm --vmname i-2-5292-VM
2024-08-23 14:35:26,312 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-3:null) (logid:20080328) Executing while with timeout : 1800000
2024-08-23 14:35:26,808 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-3:null) (logid:20080328) Execution is successful.
2024-08-23 14:35:26,809 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-3:null) (logid:20080328) Chain 'i-2-5292-VM-in' doesn't exist.
Chain 'i-2-5292-VM-out' doesn't exist.
Chain 'i-2-5292-VM-in-ips' doesn't exist.
Chain 'i-2-5292-VM-out-ips' doesn't exist.
Chain 'i-2-5292-VM-in-src' doesn't exist.
Chain 'i-2-5292-VM-out-dst' doesn't exist.
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
ipset v7.1: The set with the given name does not exist

EXPECTED RESULTS

Here is an example where I created a machine on an agent node with a functioning security group. In this case, both the security group and iptables are working correctly, and there are no iptables errors reported.
2024-08-23 16:28:22,918 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-2:null) (logid:c5363bc1) Executing: /usr/share/cloudstack-common/scripts/vm/network/security_group.py default_network_rules --vmname i-2-5310-VM --vmid 5310 --vmip <IP_ADDRESS> --vmmac 1e:00:c6:00:00:95 --vif vnet10 --brname cloudbr0 --nicsecips 0; --isFirstNic
2024-08-23 16:28:22,920 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-2:null) (logid:c5363bc1) Executing while with timeout : 1800000
2024-08-23 16:28:24,427 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-2:null) (logid:c5363bc1) Execution is successful.
2024-08-23 16:28:24,427 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-2:null) (logid:c5363bc1) Chain 'i-2-5310-VM-in' doesn't exist.
Chain 'i-2-5310-VM-out' doesn't exist.
Chain 'i-2-5310-VM-in-ips' doesn't exist.
Chain 'i-2-5310-VM-out-ips' doesn't exist.
Chain 'i-2-5310-VM-in-src' doesn't exist.
Chain 'i-2-5310-VM-out-dst' doesn't exist.
ipset v7.1: The set with the given name does not exist
ipset v7.1: The set with the given name does not exist
Chain 'i-2-5310-VM-in' doesn't exist.
Chain 'i-2-5310-VM-out' doesn't exist.
Chain 'i-2-5310-VM-in-ips' doesn't exist.
Chain 'i-2-5310-VM-out-ips' doesn't exist.
Chain 'i-2-5310-VM-in-src' doesn't exist.
Chain 'i-2-5310-VM-out-dst' doesn't exist.

ACTUAL RESULTS

it looks like the error happened when destroy network rules for a stopping vm
(the command is  destroy_network_rules_for_vm )
they are just some warnings I think

@Qinshan886 is there a malfunction in your system? A deletion of a rule that does not exist is just a warning unless a rule remains that should have been deleted.


Unable to init from given url (url which exists and I can access via browser ).

Hi, I am getting images from remote address and save them in local. Everything works fine. I have allow_url_fopen enabled and  I can access the url which is http. The problem is when I put that code in a queued job, then in the logs I see this error:

local.ERROR: Unable to init from given url
I can't understand, because the same code works without queued job, but inside it don't.
The code is simple:

`				      try{
// $photo->url exists
$img = Image::make($photo->url);
				// SAVE BIG IMAGE
				$img->save($path . $filenameBig);

			}catch (Intervention\Image\Exception\NotReadableException $e){
				var_dump($e->getMessage());
			}`

I even changed the URL to some of online fake image generators. The result is the same

Same for me. Image URL is valid, but can't process it with this library

Same here... URL is valid but can't be processed

apparently I'm not alone

Anyone solved this one?

Same issue here

I've digged in this since I myself have the very same problem as above.
I've found that the issue relies on the PHP file_get_contents getting a timeout whilst trying to retrieve the input file.

failed to open stream: Connection timed out

This means that the PHP instance gets timed out, obviously. Reason can be too big of a file, the PHP container is restricted to curl from external resources or just a firewall blocking.
You can verify the latter by increasing default_socket_timeout and then run it again. This will show if it's a firewall/restriction:

file_get_contents(blablabla): failed to open stream: Connection refused

The integration of the option to read data directly via URLs was a mistake. The task of this library is image manipulation. Reading data via HTTP should be done by a corresponding client. For this reason, Intervention Image Version 3 does not support reading URLs.


Question: what kind of task/labels can this library supports?

Is this framework specifically for image classification only, or can it also be used / adapted for cell detection and nuclei segmentation? If not, is there any plan to add these tasks? Thanks!

Cell detection and nuclei segmentation are under development! We are hoping to include these tasks in version 1.5, which we aim to release around February. In the meantime, Slideflow supports classification, regression, and time-to-event prediction.

Just to follow up - Version 1.5 has been released, and with this release Slideflow supports:

Weakly-supervised tile-based models (CNNs and transformers) for classification, regression, and time-to-event
Weakly-supervised multi-instance learning (CLAM) for classification
Self-supervised learning (SimCLR)
Generative adversarial networks (StyleGAN2 and StyleGAN3)
Whole-slide cell segmentation (Cellpose)
Custom training loops and architectures by providing a preprocessed Tensorflow or PyTorch dataloader

Thanks, and closing this issue for now.


companies, broadcasts, errors, etc.

whoop!

don't forget to bump version and push to npm :D @brainflake

the error change is semver breaking


remove conditional compilation of use std::env; statement

This has been bugging me while working on other things, and it has a simple solution.

r? @reese


"window is not defined"

Getting this issue at build time:

The odd part is I already deployed it to netflify. Anyone else come across and solved this problem? Thanks!

Hi!
Did you add custom code to the layout.js file? Cause I couldn't find the code snippet you posted.
In general, window is not available during build time hence it should be wrapped in an isSSR condition like here: https://github.com/konstantinmuenster/gatsby-starter-portfolio-minimal/blob/master/src/components/header.js#L82.
Maybe that already solves your issue?

Closed due to inactivity.


Suggestions Page - Input Text

USER STORY
As a student
I Want to enter text
So That I can start receiving suggestions
ACCEPTANCE CRITERIA
*We should add a text box that users should be able to type or paste text into

[ ] Do Backend


Suggestion: Installation of Chromium in user mode

Suggestion: Installation of Chromium in user mode
Expected Behavior
Target environment requires a Chrome browser.  Chrome/Chromium browser should be available for testing user interfaces.
Current Behavior
No Chrome/Chromium browser is present.  Insufficient access to install Chrome .deb package.
Possible Solution
If Chrome will not be included in a standard Linux build, add installation script for Chromium browser using the URL https://download-chromium.appspot.com/
chromium.zip
Context
Developing specifically for a Chrome target environment, testing using FireFox is adequate but a Chrome browser would be more representative of the end-user experience.
Your Environment

Ubuntu 16.04 development laptop

Chrome is installed by default on the latest builds


Bug: FzfLuaNormal not working in nvim nightly

RTFM Checklist

[X] I have searched exisiting issues / discussions
[X] I have read the Wiki including the Advanced section
[X] I have read man fzf / I am well versed in shell fzf

Operating system
Mac
Shell
fish
Neovim version (nvim --version)
NVIM v0.10.0-dev-build-20231109-1627-gefaf37a2b Build type: Release LuaJIT 2.1.1713484068 Run "nvim -V1 -v" for more info
Fzf version (fzf --version)
0.50.0 (brew)
Output of :lua print(os.getenv('FZF_DEFAULT_OPTS'))
not matter
Is the problem reproducible with mini.sh?

[X] My issue is reproducible with mini.sh
[X] My issue IS NOT reproducible with mini.sh
[X] I have not tested with mini.sh (not relevant, requires LSP, Windows, etc)

Fzf-lua configuration
default, repro with mini.sh
Describe the bug / steps to reproduce
FzfLuaNormal not working in nvim nightly version.
See https://github.com/ibhagwan/fzf-lua/discussions/1160 for details.

@towry, I verified https://github.com/ibhagwan/fzf-lua/commit/b107fb7a3893bcfb2d27b6f397cf290b3e0d1ca7 with the latest nightly, can you also verify?

mini.sh works, but my config doesn't, i need to investigate further.

mini.sh works, but my config doesn't, i need to investigate further.

You might be overriding the fg|bg with fzf_colors, is FzfLuaBorder working for you now (the border is a separate window unaffected by fzf_colors)?

If i run min.sh in /tmp, it works. but not working if running inside $HOME/

If i run min.sh in /tmp, it works. but not working if running inside $HOME/

Why would the path make any difference to neovim highlights, maybe you have a mismatch of runtimes and the said change that caused this issue somehow prevents this from working?
This is highly suspicious as I didn’t remove any highlight from the float windows I just added setting NormalFloat on top of the already set Normal.

I notice your mini.sh doesn't use --clean this affect the difference. with --clean, it will work.

augroup vimrc | autocmd! | augroup end

set nocompatible
set number
set laststatus=2

" change this to your local coc.nvim location.
set runtimepath^=/Users/towry/.local/share/nvim/lazy/fzf-lua
filetype plugin indent on
syntax on

set expandtab shiftwidth=4 tabstop=4 softtabstop=4

run nvim -u mini.vim
run :FzfLua files hls.normal=IncSearch hls.border=IncSearch

Actually I know what this bug is, it's something I already fixed in cmp_src branch, specifying two dotted options with the :FzfLua hls.normal=... hls.border=... can randomly bug out (one will be missing) due to map ordering.
This will probably work for you:
:lua require("fzf-lua").files({ hls = { normal="IncSearch", border="IncSearch" } })

Let me know if the above works for you that would confirm my assumption regarding the already fixed bug and I'll merge the branch even though it's WIP the code is settled, only OPTIONS.md is not yet complete.

Yes, it seems random.
https://github.com/ibhagwan/fzf-lua/assets/8279858/fc4da003-d7f0-4517-a004-cecbd9d39711

Yes, it seems random.

This is a bug with the :FzfLua command parser (which I already fixed in the cmp_src branch), the lua variant of the command will work:
lua require("fzf-lua").files({ hls = { normal="IncSearch", border="IncSearch" } })

The cmp_src doesn't work with my config, strange, must be some plugin affected.

The cmp_src doesn't solve the highlight issue with my config, strange, must be some plugin affected.

Does the lua command I posted also fail randomly? If so that might be the case.
If only the :FzfLua ... command variant fails randomly that would be a bug in fzf-lua.

The lua command doesn't work, no random.

The lua command doesn't work, if using my config, no random. I will try to narrow down specific config that cause this.

Alright, let me know what you find, I will merge cmp_src soon so we can have that to test as well.

https://github.com/ibhagwan/fzf-lua/commit/eed06a7a9a28aeb47659b609999813d1bedc1a00
@towry, cmp_src was merged so the :FzfLua ... variant shouldn't be bugged anymore when specifying more than one "dotted" option (e.g. hls.normal).

It is https://github.com/tknightz/telescope-termfinder.nvim
after i commented out require('telescope').load_extension('termfinder'), fzf-lua highlights works ok.

after i commented out require('telescope').load_extension('termfinder'), fzf-lua highlights works ok.

Very interesting, keep me posted if you find out why this plugin conflicts with fzf-lua highlights.

@ibhagwan actually, fzf-lua conflicted with toggleterm.terminal module.
If id run :lua require('toggleterm.terminal') (or open ToggleTerm), this issue will happen.

The cause is toggleterm's shade_filetypes https://github.com/akinsho/toggleterm.nvim?tab=readme-ov-file#set-terminal-shading
If i remove this option, no issue.

In my config I have shade_terminals = true but my  shade_filetypes is empty and don’t have this issue.
Fzf-lua’s filetype is set to fzf and you’re effectively telling toggleterm to take over the highlight and modify its shade, I’m not sure what toggleterm does to modify the shade but perhaps it fails to restore the FloatBorder hlgroup when it does that?

My initial shade_filetypes is { 'none' }, it will cause toggleterm to override the terminal highlights.
Every time fzf is started, toggleterm will change the highlights:

Every time fzf is started, toggleterm will change the highlights:

I know, I also use but with  the shade_termianls option.


Add state charts as depds

Add package StateCharts.jl as weak dependent package of AlgebraicABMs. And also add an example using the state chart of a SIR agent-based model, and with a small world network.

Thanks Xiaoyan, independent of my review, can you increase the code coverage of the tests?
Also it seems to have errored on Julia 1.11 (but not on Julia 1.10) which is interesting. What version do you use when you test on your local machine?

Thanks Xiaoyan, independent of my review, can you increase the code coverage of the tests?
Also it seems to have errored on Julia 1.11 (but not on Julia 1.10) which is interesting. What version do you use when you test on your local machine?

Hi Kris, I’m currently using Julia 1.10.1 on my local machine. I’ll update to Julia 1.11 and investigate the bug. I will also increase the code coverage of tests. Thank you very much!


chore(dev-infra): enable rule @typescript-eslint/no-non-null-assertion

Summary

Disable rule @typescript-eslint/no-non-null-assertion is bad. We should leave it enable
Test plan

Green CI, no lint warnings
Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information
N.A.

Pull Request Test Coverage Report for Build 4928

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 92.826%

Totals

Change from base Build 4925:
0.0%

Covered Lines:
1060

Relevant Lines:
1095

💛  - Coveralls


Te4mmerge

te4m merge

@userazhao So this branch is comprised of the files from the te4mdemo branch copied into the te4m branch? Just making sure I am following here.

Will we want the demo file on main? Additionally, if we are using Team Team's objects/code for some of these things (such as Cards) do we want our code for them on main if it won't be used?


Update iSponsorBlockTV to latest v2 release

Could you please update iSponsorBlockTV addon to the latest v2 release?

I'll take a look, is there a list of breaking changes somewhere?

It is entirely untested but I have pushed a 2.0.0 release, give it a go if you are feeling brave.

I just tried but it fails to install with this message:
Can't install ghcr.io/bertybuttface/aarch64-addon-isponsorblocktv:2.0.0: 500 Server Error for http+docker://localhost/v1.42/images/create?tag=2.0.0&fromImage=ghcr.io%2Fbertybuttface%2Faarch64-addon-isponsorblocktv&platform=linux%2Farm64: Internal Server Error ("manifest unknown")
Logger: homeassistant.components.hassio
Source: components/hassio/websocket_api.py:138
Integration: Home Assistant Supervisor (documentation, issues)
First occurred: 3:57:26 PM (5 occurrences)
Last logged: 4:01:43 PM
Failed to to call /store/repositories - Cmd('git') failed due to: exit code(128) cmdline: git clone -v --recursive --depth=1 --shallow-submodules -- https://github.com/bertybuttface/addons/tree/main/isponsorblocktv /data/addons/git/c6aabcbc stderr: 'Cloning into '/data/addons/git/c6aabcbc'... fatal: repository 'https://github.com/bertybuttface/addons/tree/main/isponsorblocktv/' not found '
Failed to to call /store/repositories - https://github.com/bertybuttface/iSponsorBlockTV is not a valid add-on repository
Failed to to call /store/repositories - Cmd('git') failed due to: exit code(128) cmdline: git clone -v --recursive --depth=1 --shallow-submodules -- https://github.com/bertybuttface/addons/blob/main/isponsorblocktv /data/addons/git/f9a48b55 stderr: 'Cloning into '/data/addons/git/f9a48b55'... fatal: repository 'https://github.com/bertybuttface/addons/blob/main/isponsorblocktv/' not found '
Failed to to call /addons/932a64e5_isponsorblocktv/install - Can't install ghcr.io/bertybuttface/aarch64-addon-isponsorblocktv:2.0.0: 500 Server Error for http+docker://localhost/v1.42/images/create?tag=2.0.0&fromImage=ghcr.io%2Fbertybuttface%2Faarch64-addon-isponsorblocktv&platform=linux%2Farm64: Internal Server Error ("manifest unknown")

Yeah thats on me, I was maintaining a fork so breaking changes wouldn't hit this addon. I've removed the fork for now and I'll push a 2.0.1 release.

Upstream removed the ability to specify a config file (cheers for that), I've tried using a symlink for now but not tested.

Ok that works but it doesn't survive a reboot. 2.0.3 is building now.

Upstream removed the ability to specify a config file (cheers for that), I've tried using a symlink for now but not tested.

Sorry about that, it was done to support having multiple files in the future, and launching with docker easier

No worries I appreciate your hard work.


CSS for Work Experience cards

This card will contain the job title, the organization/company the job was with, a description of the job, and the start/end year/month. End dates are optional, as users can include current employment. Months are also optional. The minimum information required for a work experience is a title and organization.
Example picture of crude implementation

There is work experience cards. They are on profile-edit.php, there is not a description on yet.

Can we see a worst case scenario data-wise. For example an address to be shown in a card.

For work experience, the only fields will be job title, description, Organization, and start-date/end-date
if the existing cards support these, then consider this one my bad and close the issue :)


gradle not reading memory correctly on docker

I want gradle to read the correct memory information about the docker container.
Currently gradle is reading the memory information from /proc/meminfo as from https://github.com/gradle/gradle/blob/master/subprojects/process-services/src/main/java/org/gradle/process/internal/health/memory/MemInfoOsMemoryInfo.java.
Which in docker is giving the total memory available to the host and not the container. This means that gradle will make an idle daemon when it does not have memory to do so, ultimately meaning that the container is killed.
Steps to Reproduce
I made an example project where this can be tested: https://github.com/gregables/FratolishHiangPerpeshki.
Clone the repo and do a docker build -m=2g ., this will fail with a 137 error.
Now change the build.gradles for the following modules:

cerberus
hades
fratolishhiangperpeshki
zeus

so that the fork options have jvm args with xmx and xms values very close to the actual free memory on your host machine, now if you rerun the above command it will not fail.
Your Environment
Nothing special about my environment.
What is happening is like so: gradle only kills of idle worker daemons when a request for a new jvm comes in which requires a larger min heap than is available as determined by /proc/meminfo. Since, /proc/meminfo doesnt show the details of the container but rather the host we stumble on this problem.
https://github.com/itsyaboiyeah and I have been looking at this issue for the last week as we have identified it as the reason why jenkins builds intermittently fail, i suppose it would also be nice to have this: https://github.com/gradle/gradle/issues/15243 feature aswell for us memory conservatives.

This looks like a duplicate of #17610. It is more recent but has a PR already so I'm closing this one.

AFAICT this is not a duplicate of the linked issue, see #26065


Setup Danger

close #31
Changes

Setup Danger
Setup danger-android_lint

Codecov Report

Merging #83 (fa85727) into main (9be398f) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##               main      #83   +/-   ##
=========================================
  Coverage     30.36%   30.36%
  Complexity       32       32
=========================================
  Files            45       45
  Lines           573      573
  Branches         82       82
=========================================
  Hits            174      174
  Misses          398      398
  Partials          1        1

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9be398f...fa85727. Read the comment docs.


v7: Issues with consecutive verbs

In instances where the subject name (common or proper) is also a verb (in another context) then the subject is incorrectly marked as verb... I think if you have consecutive potential verbs then the first is most likely the subject and the second is the actual verb - unless the sentence is a question, in which case the order is reversed.

hey, just missed this one.
yeah, this is a good example. Reading here, even if it was the act of reading a book, should be a noun anyways. Right now gerund is a verb 'was reading quickly' - but it can also be a noun reading is great

hey leo, added support for a new #Activity tag, which is a noun.

will be part of v11.
cheers


Dodge the asteroids game for sprig

Your checklist for this pull request
yes
About your game
this is the game is very interesting... this game is stress relief game too.

Press WASD to move, J to restart, and K to toggle trails, Get A boxes (cyan) to A goals (green), Get B boxes (magenta) to B goals (red), Get normal boxes (gray) to either goal. (from Sokoban plus)

Code
Check off the items that are true.

[x] The game was made using the Sprig editor.
[x] The game is placed in the /games directory.
[x] The code is significantly different from all other games in the Sprig gallery (except for games labeled "demo").
[x] The game runs without errors.
[x] The name of the file/game contains only alphanumeric characters, -s, or _s.
[x] The game name is not the same as the others from gallery

Image (If an image is used)

[x] The image is in the /games/img directory.
[x] The name of the image matches the name of your file. Example: sokoban_plus.js -> sokoban_plus.png.

Thanks for PR!

Thank you for letting us improve our ideas and win the Sprigs.

Thanks for PR! Are fire_the_dodge and dodge_the_asteroids games the same? How about adding a little more to your games? to make them more original. if you need help, call me :)

It seems you need to make a few more changes before merging it in.
Because it's been a little while I'm going to close the PR for now but feel free to reopen at a later point if you want to continue working.


Locale-specific pluralization rules

Thanks for your work !
I see you made  some changes recently, is it still a work in progress ?

Yeah, I did some corrections while testing with my libraries. But now it is ready to review.

I don't think the user should need to define pluralization rules. There are only a handful of different rulesets and they can easily be included in this shard, could even be hard coded. There is an overview on MDN which could serve as a basis. Default mappings for major languages should also be provided.

The existing rulesets can be hardcoded, but why not keeping the flexibility for the user to define custom rules ?

As long as there are default rules which require no special configuration for all typical use cases, a customization option on top doesn't hurt. But I don't see why you would need it. I'd only add that complexity if there is a use case for it (and it can be added later should there be demand). All relevant use cases I can think of should be satisfied by implementing the standard ruleset.

Hi. So, what we will do with this? Any chance this will be merged, or I should close it?


Deformed image with Microsoft Edge

The desktop version of Edge on Windows 10 also shows images with squashed proportions as in  #105


Game.rnd is not properly initialized

This is a Utils.RandomDataGenerator object. It should be initialized with a random seed, to ensure that game randoms are truly random.
However, it is instead initialized with Date.now.toString(), which always evaluates to "function now() { [native code] }". This means the seed is always identical.
We need to evaluate that now function.

I added the missing (). Random numbers now evaluate randomly.


Rules engine project structure and pytest

This pull request introduces a Python project structure for the rules engine, along with the start of development dependencies with pytest, as well as functional example Python code and test files.

Locally:
$ pytest
================================================== test session starts ===================================================
platform win32 -- Python 3.8.10, pytest-7.3.2, pluggy-1.0.0
rootdir: C:\git\alanisaac\home-energy-analysis-tool\rules-engine
collected 1 item

tests\rules_engine\test_example.py .                                                                                [100%]

=================================================== 1 passed in 0.03s ====================================================


filtering-select not working!!

I'm working on project where I have some table that have so many records. and when I'm trying to filtering-select the record to choose it when I'm in Add new action, it doesn't work and I'm stuck!

What version of RailsAdmin are you using? Do you see any errors in your browser console?


gRPC server is listening on all interfaces.

Expected behavior
gRPC should(must?) listen only on <IP_ADDRESS>
Actual behavior
gRPC listening on <IP_ADDRESS>
Gauge version
gauge-java 0.7.10

Thanks for raising this. This seems to be the default that ServerBuilder seems to be setting.
According to https://github.com/grpc/grpc-java/issues/5791, we should be using NettyServerBuilder instead. Will try and see.

Fixed on release https://github.com/getgauge/gauge-java/releases/tag/v0.7.12


doc(maintainer): add contributor/needs-resolve-conflicts

Description
Replace contributor/needs-rebase by contributor/needs-resolve-conflicts.

@timoreimann Fixed! s/solve/resolve/


Implements the experimental contains filter operator

Pull Request
Related PRD: (private link) https://www.notion.so/meilisearch/Contains-Like-Filter-Operator-0d8ad53c6761466f913432eb1d843f1e
Public usage page: https://meilisearch.notion.site/Contains-filter-operator-usage-3e7421b0aacf45f48ab09abe259a1de6
Related issue
Fixes https://github.com/meilisearch/meilisearch/issues/3613
What does this PR do?

Extract the contains operator from this PR: https://github.com/meilisearch/meilisearch/pull/3751
Gate it behind a feature flag
Add tests

bors merge


Can't customize checkbox of column with checkboxSelection

I have a column that contains checkboxes for selection.  I set checkboxSelection:true on the column.
I don't know how to make custom css for a checkbox within this column.  To my knowledge, custom css for a checkbox requires a div around the checkbox.  What renders is a span around the checkbox.
When I create a cell renderer, my render appears behind a normal checkbox.  Looking at the code, checkboxSelection appears to call that.selectionRendererFactory.createCheckboxColDef(); and there's no way to patch it.
Am I missing some way of wrapping the input with a div so I can customize the look and feel of the checkbox?

To my knowledge, custom css for a checkbox requires a div around the checkbox.

That's not true! You just need the right CSS selector to get to the checkbox.

When I create a cell renderer, my render appears behind a normal checkbox. Looking at the code, checkboxSelection appears to call that.selectionRendererFactory.createCheckboxColDef(); and there's no way to patch it.

What you can do is create your own cellRenderer from scratch - forget about the built in checkbox. Provide your own checkbox. Then use the selection api to select / unselect the row.

I'd like to share some sample code if anyone would need help regarding this issue :)
What this does is, allows you to set an id to the select boxes which would be impossible with the built in selector.
Directive Controller code:
MyListCtrl.prototype.selectNodeById = function (nodeIdx) {
        if (this.lodash.find(this.gridOptions.api.getSelectedNodes(), {id: nodeIdx})) {
            this.gridOptions.api.deselectIndex(nodeIdx);
        } else {
            this.gridOptions.api.selectIndex(nodeIdx, true);   // true means additive selection
        }
    };

MyListCtrl.prototype.addControlColumns = function () {
        var vm = this;
        this.columns.unshift({
            field: 'select',
            headerName: '',
            width: 30,
            suppressSorting :true,
            cellRenderer: this.selectBoxFn.bind(vm)
        });
    };

MyListCtrl.prototype.selectBoxFn = function (params) {
        var compID = 'MyCustomComponentID';
        return '<input id="' + compID + '" type="checkbox" name="list-item-row-selection" ng-click="vm.selectNodeById(' + params.node.id + ')">';
    };


[19.03] python3.pkgs.joblib fails to build due to test failure

Joblib when attempting to build on 19.03 import (fetchTarball https://github.com/NixOS/nixpkgs-channels/archive/cf3e277dd0bd710af0df667e9364f4bd80c72713.tar.gz) {} fails:
=================================== FAILURES ===================================
________________________________ test_disk_used ________________________________

tmpdir = local('/build/pytest-of-nixbld/pytest-0/test_disk_used0')

    def test_disk_used(tmpdir):
        cachedir = tmpdir.strpath
        # Not write a file that is 1M big in this directory, and check the
        # size. The reason we use such a big file is that it makes us robust
        # to errors due to block allocation.
        a = array.array('i')
        sizeof_i = a.itemsize
        target_size = 1024
        n = int(target_size * 1024 / sizeof_i)
        a = array.array('i', n * (1,))
        with open(os.path.join(cachedir, 'test'), 'wb') as output:
            a.tofile(output)
>       assert disk_used(cachedir) >= target_size
E       AssertionError: assert 1 >= 1024
E        +  where 1 = disk_used('/build/pytest-of-nixbld/pytest-0/test_disk_used0')

joblib/test/test_disk.py:32: AssertionError
============= 1 failed, 1031 passed, 79 skipped in 124.63 seconds ==============
[INFO:MainProcess:MainThread] process shutting down
[DEBUG:MainProcess:MainThread] running all "atexit" finalizers with priority >= 0
[DEBUG:MainProcess:MainThread] Interpreter shutting down. Waking up queue_manager_threads [(<Thread(QueueManagerThread, started daemon<PHONE_NUMBER>24864)>, <joblib.externals.loky.process_executor._ThreadWakeup object at 0x7ffff4c28048>)]
[DEBUG:MainProcess:QueueManagerThread] queue management thread shutting down
[DEBUG:MainProcess:QueueManagerThread] closing call_queue
[DEBUG:MainProcess:QueueManagerThread] telling queue thread to quit
[DEBUG:MainProcess:QueueManagerThread] joining processes
[DEBUG:MainProcess:QueueFeederThread] feeder thread got sentinel -- exiting
[DEBUG:MainProcess:QueueManagerThread] queue management thread clean shutdown of worker processes: []
[DEBUG:MainProcess:MainThread] running the remaining "atexit" finalizers
builder for '/nix/store/sk913x41632c4413r87qpcddz9fgw43i-python3.6-joblib-0.13.2.drv' failed with exit code 1

I saw this error before here:
https://github.com/NixOS/nixpkgs/issues/54875#issuecomment-458787619

builder for '/nix/store/sk913x41632c4413r87qpcddz9fgw43i-python3.6-joblib-0.13.2.drv' failed with exit code 1

That's definitely not python3.pkgs.joblib. python36.pkgs.joblib also builds fine. Please provide info on how to reproduce this.

Just using nix repl with the pkg set brought in by import (fetchTarball https://github.com/NixOS/nixpkgs-channels/archive/cf3e277dd0bd710af0df667e9364f4bd80c72713.tar.gz) {}. And then :b pkgs.python36Packages.joblib or :b pkgs.python37Packages.joblib.

@dotlambda I also reported and fixed these test failures in PR #57176 (never merged), so I would consider them reproducible, at least when running NixOS on BTRFS (or a LUKS volume).
@CMCDragonkai What file system are you using? Do you encrypt your hard drive or have file system level compression enabled?

@FlorianFranzen I merged your fix as 604dae6797f4e2d83a263c3f4ffb639dce3bce04. Thanks a lot!

I use ZFS. What's the source problem.