Fixed all the conflicts

SonarQube analysis reported 50 issues

 3 critical
 17 major
 12 minor
 18 info

Watch the comments in this conversation to review them.
Top 10 extra issues
Note: The following issues were found on lines that were not modified in the pull request. Because these issues can't be reported as line comments, they are summarized here:

 AbsractQueryBuilder.java#L67: This block of commented-out lines of code should be removed.
 ExtGtwAppRequestBuilder.java#L36: Move the contents of this initializer to a standard constructor or to field initializers.
 HubAppRequestBuilder.java#L37: Move the contents of this initializer to a standard constructor or to field initializers.
 ExtGtwSubRequestBuilder.java#L28: Move the contents of this initializer to a standard constructor or to field initializers.
 HubSubRequestBuilder.java#L27: Move the contents of this initializer to a standard constructor or to field initializers.
 IntGtwSubRequestBuilder.java#L28: Move the contents of this initializer to a standard constructor or to field initializers.
 ExtGtwAppRequestBuilder.java#L40: Remove the declaration of thrown exception 'com.wso2telco.core.dbutils.exception.BusinessException', as it cannot be thrown from constructor's body.
 HubAppRequestBuilder.java#L41: Remove the declaration of thrown exception 'com.wso2telco.core.dbutils.exception.BusinessException', as it cannot be thrown from constructor's body.
 AbstractAppRequestBuilder.java#L77: Reduce the number of returns of this method 2, down to the maximum allowed 1.
 AbstractAppRequestBuilder.java#L85: Reduce the number of returns of this method 2, down to the maximum allowed 1.

SonarQube analysis reported 48 issues

 3 critical
 15 major
 12 minor
 18 info

Watch the comments in this conversation to review them.
Top 10 extra issues
Note: The following issues were found on lines that were not modified in the pull request. Because these issues can't be reported as line comments, they are summarized here:

 ExtGtwAppRequestBuilder.java#L36: Move the contents of this initializer to a standard constructor or to field initializers.
 HubAppRequestBuilder.java#L37: Move the contents of this initializer to a standard constructor or to field initializers.
 ExtGtwSubRequestBuilder.java#L28: Move the contents of this initializer to a standard constructor or to field initializers.
 HubSubRequestBuilder.java#L27: Move the contents of this initializer to a standard constructor or to field initializers.
 IntGtwSubRequestBuilder.java#L28: Move the contents of this initializer to a standard constructor or to field initializers.
 ExtGtwAppRequestBuilder.java#L40: Remove the declaration of thrown exception 'com.wso2telco.core.dbutils.exception.BusinessException', as it cannot be thrown from constructor's body.
 HubAppRequestBuilder.java#L41: Remove the declaration of thrown exception 'com.wso2telco.core.dbutils.exception.BusinessException', as it cannot be thrown from constructor's body.
 AbstractAppRequestBuilder.java#L77: Reduce the number of returns of this method 2, down to the maximum allowed 1.
 AbstractAppRequestBuilder.java#L85: Reduce the number of returns of this method 2, down to the maximum allowed 1.
 AbstractAppRequestBuilder.java#L97: Reduce the number of returns of this method 2, down to the maximum allowed 1.


I want to use the featurettes folder name like video_extras

What TMM version are you using?
3.0.2
release, pre-release, nightly, or directly from GitHub/branch?
release
What is the actual behaviour?
when i renamed,
"fearturettes" folder files in the movie folder are distributed
What is the expected behaviour?
I want to use the featurettes folder name like video_extras.
Where can I fix it?I can't make template.conf..sorry
I want to modify only that part
Steps to reproduce:

first
second
...

Additional
Have you attached the Logfile from the day it happened?
Your Operating system? (win/mac/linux? version?)

try to only name that folder extras


[prometheus-node-exporter] Add pod annotations

Signed-off-by: Chirica Gheorghe<EMAIL_ADDRESS>What this PR does / why we need it:
Add pod annotations
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md

@botzill it seems there is a problem with the Chart.yaml file syntax. Can you please correct that.


Xenia Canary Netplay support

It'd be nice to have Xenia Canary Netplay support. I appreciate your hard work 🫡
https://github.com/AdrianCassar/xenia-canary/releases

Duplicate of #26


BLD: Add -std=c99 to sigtools to compile with C99

Reference issue
Should fix gh-12579
What does this implement/fix?
Adds -std=c99 flag to sigtools. This uses the same build_ext hook system used to add the -std= flag for C++ code.

My bad in merging that PR - I thought we had C99 required already, but that was NumPy (because of the C99 version of Pocketfft).
Thanks Peter, this LGTM.


Making scripts S3-aware.

Did I miss something? Are we on s3?
On Friday, February 27, 2015, Jason Hollinger<EMAIL_ADDRESS>wrote:

Merged #117
https://github.com/MushroomObserver/mushroom-observer/pull/117.
--
Reply to this email directly or view it on GitHub
https://github.com/MushroomObserver/mushroom-observer/pull/117#event-243652004
.

--
Ray Suelzer
Mobile:<PHONE_NUMBER>

Not yet, just getting things in place.  Tomorrow's our last day.    But it should at least
be safe to delete the bulk of the original images from
images.digitalmycology.com.  Waiting for some feedback from Nathan before I
know how we're going to proceed beyond tomorrow.
-Jason
On Fri, Feb 27, 2015 at 6:19 PM, Raymond Suelzer<EMAIL_ADDRESS>wrote:

Did I miss something? Are we on s3?
On Friday, February 27, 2015, Jason Hollinger<EMAIL_ADDRESS>wrote:

Merged #117
https://github.com/MushroomObserver/mushroom-observer/pull/117.
--
Reply to this email directly or view it on GitHub
<
https://github.com/MushroomObserver/mushroom-observer/pull/117#event-243652004
.

--
Ray Suelzer
Mobile:<PHONE_NUMBER>
—
Reply to this email directly or view it on GitHub
https://github.com/MushroomObserver/mushroom-observer/pull/117#issuecomment-76505070
.


Patch 1

Two things that may be "bugs".
Thank you very much for this blog post. I enjoyed reading it.

Thanks!


Deprecations removal around default product scopes

Remove fallback to '' scope in a couple of places

Can you add QA steps please?


[8.x] Pivot ids are strings not integers

Laravel Version: 8.54
PHP Version: 8.0
Database Driver & Version: mysql 5.7

Description:
The automatic pivot ids are strings when other ids are ints
Failed asserting that 1 is identical to '1'.
Failed asserting that 2 is identical to '2'.
Steps To Reproduce:
->assertJsonPath('post.id', $post->id) ✅
->assertJsonPath('tag.pivot.post_id', $post->id) 🚫
->assertJsonPath('tag.pivot.tag_id', $tag->id); 🚫

Hi there,
Thanks for reporting but it looks like this is a question which can be asked on a support channel. Please only use this issue tracker for reporting bugs with the library itself. If you have a question on how to use functionality provided by this repo you can try one of the following channels:

Laracasts Forums
Laravel.io Forums
StackOverflow
Discord
Larachat
IRC

However, this issue will not be locked and everyone is still free to discuss solutions to your problem!
Thanks.


Middleware support

Middlewares
Support middlewares in routes
const compression		= require("compression");
const serveStatic 		= require("serve-static");

broker.createService({
    mixins: [ApiService],
    settings: {
        routes: [
            {
                path: "/",

                // Middlewares
                use: [
                    compression(),
                    serveStatic(path.join(__dirname, "public"))
                ]
            }
        ]
    }
});

2 new examples

Webpack
Webpack & Vue

Coverage decreased (-0.03%) to 95.537% when pulling dc1b051bc6a2d79e4f899b51e7dd600a7b9b3657 on webpack into 5a9976adb576a83735d9ce438ba0b4c3c0accaab on master.


Allow todo prompt segment background and forground to be colorized

This change would allow color adjustments to the todo prompt segment using POWERLEVEL9K_TODO_BACKGROUND and POWERLEVEL9K_TODO_FOREGROUND.

Hi @voldemortensen! Thanks so much for submitting this PR!
So, P9k has a built-in methodology for allowing setting the FG and BG colors of any segments. You can read how it works here. Was that approach not working for you?

Ahh.. I was scanning for todo in the colorization sections and missed those details. I’m sure that will work, thanks! And thanks for a great theme!

On Dec 29, 2017, at 12:26, Ben Hilburn<EMAIL_ADDRESS>wrote:
Hi @voldemortensen! Thanks so much for submitting this PR!
So, P9k has a built-in methodology for allowing setting the FG and BG colors of any segments. You can read how it works here. Was that approach not working for you?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

No problem, @voldemortensen! Thanks for going through the effort to try and implement something you thought was missing! Hopefully you're back with more PRs soon =)


Use Flowcore CLI to create Data Core, Flow Type and Event Type configuration

Is your feature request related to a problem? Please describe. 👨🏫
When creating a new deployment or developing locally it should be easy to create a self-contained data-core structure up with the flowcore cli
Describe the solution you'd like 📝
Create a manifest that describes any Flowcore Resources required for storing the data for the conference app
Use the flowcore cli's data-core apply functionality to apply the manifest to your setup

This has been resolved, so I am closing this issue


Allow to get custom user data with key

Changes
Please describe both what is changing and why this is important. Include:
I've set custom data in Auth0 via Rules. Currently, it is not possible to retrieve that data from the User class. I've added a getter method to get the custom user data by key. As the content of that data is not known, we have to use mixed as the return type.
An alternative approach would be to make the current private property data protected, so I as a developer can extend the User class and get fetch my custom data in my own class.
References

https://auth0.com/docs/customize/rules

Testing
Create a rule in Auth0, which adds some custom data to e.g. idToken or accessToken with a custom key e.g. https://mydomain.com/custom_data.
[x] This change has been tested on the latest version of Symfony
Checklist
[x] I have read the Auth0 general contribution guidelines
[x] I have read the Auth0 Code of Conduct
[x] All existing and new tests complete without errors

Thanks for your contribution, @maxwagner-dev! 👋


[MacOS] Engine crashes when loading a project with Godot Jolt installed

Have been interested in testing this out after some issues I've been having with the internal physics engine but installing it in both an active project as well as a fresh project on my Macbook Pro crashes the engine before it launches. Attached is the crash report. Would love to fix this and get into open source stuff but no idea where to even start!
cr.txt

Your crash report seems to indicate that you're using Godot 4.2, which is technically not not supported by this extension, as mentioned in README.md.
Could you check whether it crashes when you use Godot 4.1.1 instead?

Oh gosh I’ll be so embarrassed if I didn’t read the dang README. Let me get back to you but assume you’re good!
On Thu, Sep 28, 2023 at 22:40, Mikael Hermansson @.***(mailto:On Thu, Sep 28, 2023 at 22:40, Mikael Hermansson < wrote:

Your crash report seems to indicate that you're using Godot 4.2, which is technically not not supported by this extension, as mentioned in README.md.
Could you check whether it crashes when you use Godot 4.1.1 instead?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

My sincere apologies, you're totally correct. Issue closed.


GPU not found on Tensorflow 1.4.1

System information

Linux Ubuntu 20.04
tensorflow-gpu            1.4.1                    pypi_0    pypi
Python version: 2.7.15
Installed using virtualenv? pip? conda?:
CUDA/cuDNN version: CUDA version 8.0.61 with cuDNN version 6.0.21
1x GTX 1080TI

The problem
I cannot run any scripts from GPU using tensorflow. When I run:
import os
import tensorflow as tf
os.environ["CUDA_VISIBLE_DEVICES"]="0"
print(tf.test.gpu_device_name())

I get:
2021-10-14 11:35:56.443831: I tensorflow/core/platform/cpu_feature_guard.cc:137] Your CPU supports instructions that this TensorFlow binary was not compiled to use: SSE4.1 SSE4.2 AVX AVX2 FMA
2021-10-14 11:35:57.277446: E tensorflow/stream_executor/cuda/cuda_driver.cc:406] failed call to cuInit: CUDA_ERROR_INVALID_DEVICE
2021-10-14 11:35:57.277535: I tensorflow/stream_executor/cuda/cuda_diagnostics.cc:158] retrieving CUDA diagnostic information for host: erwin-SYS
2021-10-14 11:35:57.277557: I tensorflow/stream_executor/cuda/cuda_diagnostics.cc:165] hostname: erwin-SYS
2021-10-14 11:35:57.277638: I tensorflow/stream_executor/cuda/cuda_diagnostics.cc:189] libcuda reported version is: 470.74.0
2021-10-14 11:35:57.277692: I tensorflow/stream_executor/cuda/cuda_diagnostics.cc:369] driver version file contents: """NVRM version: NVIDIA UNIX x86_64 Kernel Module  470.74  Mon Sep 13 23:09:15 UTC 2021
GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
"""
2021-10-14 11:35:57.277742: I tensorflow/stream_executor/cuda/cuda_diagnostics.cc:193] kernel reported version is: 470.74.0
2021-10-14 11:35:57.277762: I tensorflow/stream_executor/cuda/cuda_diagnostics.cc:300] kernel version seems to match DSO: 470.74.0
''

Other info / logs
When I run nvidia-smi it does find the gpu:
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 470.74       Driver Version: 470.74       CUDA Version: 11.4     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|                               |                      |               MIG M. |
|===============================+======================+======================|
|   0  NVIDIA GeForce ...  Off  | 00000000:02:00.0 Off |                  N/A |
| 27%   26C    P8     6W / 180W |     14MiB /  8118MiB |      0%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+

@tilakrayal
I need this specific version of Tensorflow as it required by an old project. Any idea what the problem could be?

@erwinerdem ,
Please take a look at this issue1, issue2 with the similar error.Also  Its unlikely for TF 1.x version to receive any bug fixes except when we have security patches. There is a high possibility that this was fixed with later TF versions. Perhaps you can use latest tf versions for your case. Thanks!

I didn't really solve the problem directly but I was able to get it working using a docker image.


fix: update quick start to ghcr image

Description
What this PR does / why we need it:

Which issue(s) this PR fixes (optional, using fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when the PR gets merged):
Fixes #
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Helm Chart Change (any edit/addition/update that is necessary for changes merged to the main branch)
[ ] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Please also list any relevant details for your test configuration

[ ] Test A
[ ] Test B

Checklist:

[ ] Does the affected code have corresponding tests?
[ ] Are the changes documented, not just with inline documentation, but also with conceptual documentation such as an overview of a new feature, or task-based documentation like a tutorial? Consider if this change should be announced on your project blog.
[ ] Does this introduce breaking changes that would require an announcement or bumping the major version?
[ ] Do all new files have appropriate license header?

Post Merge Requirements

[ ] MAINTAINERS: manually trigger the "Publish Package" workflow after merging any PR that indicates Helm Chart Change

Ditto, thanks for looking into this.  Once this is merged, we should let Yi and Xinhe know so that they update the docs.
How did you get the images in the registry?

Thanks for the update! We can update our testing pipeline in a follow up PR?
Do we need to update the docs on the website too?

For our azure e23 testing pipeline, we should continue using wabbitnetwork, for non azure test, i believe we are doing local registry ? Good point on the website, i ll check what needs to be updated


fix: improve death item locking logic

Improves death item locking logic to use the API methods rather than persistent data stuff

Just need to test this before merge


Fix infercorrect layout in Layoutrewrite and improve naming.

This model
def @main(%x: Tensor[(1, 1, 1, 1), float32] /* ty=Tensor[(1, 1, 1, 1), float32] */) -> Tensor[(1, 1, 1), float32] {
  %0 = image.resize2d(%x, size=[2, 4], roi=[0f, 0f, 0f, 0f], rounding_method="") /* ty=Tensor[(1, 1, 2, 4), float32] */;
  %1 = mean(%0, axis=[3]) /* ty=Tensor[(1, 1, 2), float32] */;
  image.resize1d(%1, size=[1], roi=[0f, 0f], rounding_method="") /* ty=Tensor[(1, 1, 1), float32] */
}

fails with error   Check failed: (tir::BijectiveLayout(new_src_layout, dst_layout).defined()) is false: Cannot insert layout transform because there are inconvertible layouts: NCW v.s. NCH. This should be a bug introduced in https://github.com/apache/tvm/pull/10118. This line https://github.com/apache/tvm/pull/12007/commits/7805d6fb113c9a68dd4628bb136416349f211ca2#diff-c3bb97b7e813244d6dae39925cc10bb9d50e8b7a280556b423068b3705f9f114R363 fixes it.
In short, there should be no layout rewriting here since no conv etc. are used. But when the pass is checking resize1d, the previous code do not pass consistent layouts for the argument old_in_layouts for the two calls of ResizeInferCorrectLayout (the first time NCH from old_inhttps://github.com/apache/tvm/blob/ef08c36294dc7c90f9d4536948507eca515012bd/src/relay/transforms/transform_layout.h#L341, second time NCW from old_in_2https://github.com/apache/tvm/blob/ef08c36294dc7c90f9d4536948507eca515012bd/src/relay/transforms/transform_layout.h#L363), misleading the optimizer into thinking that the layout has changed and hence an ill-formed layout_transform is inserted.
This PR also improves the naming based on suggestions from @masahi in https://github.com/apache/tvm/pull/10118, as well as adds several comments and logging statements to help people understand. (Hope this helps you understand that change better too @masahi :-)).

To reproduce the problem, run the following code:
import tvm
from tvm import relay
from tvm.relay.transform import InferType

@tvm.instrument.pass_instrument
class PrintIR:
    """Print the name of the pass, the IR, only before passes execute."""

    def __init__(self, print_mod=True, show_meta_data=False) -> None:
        self.pass_cnt = 0
        self.print_mod = print_mod
        self.show_meta_data = show_meta_data

    def run_before_pass(self, mod, info):
        with tvm.transform.PassContext(instruments=[]):
            global prev_mod
            if self.print_mod:
                print(relay.transform.InferType()(mod))
            print('>' * 40, f'Running Pass#{self.pass_cnt}:', info)

        self.pass_cnt += 1

x = relay.var("x", shape=(1, 1, 1, 1))
y = relay.image.resize2d(x, (2, 4))
z = relay.mean(y, axis=3)
a = relay.image.resize1d(z, (1,))
func = relay.Function((x,), a)
mod = tvm.IRModule.from_expr(func)
print(InferType()(mod))

with tvm.transform.PassContext(opt_level=4, instruments=[PrintIR()]):
    relay.create_executor("graph", mod).evaluate()
print('pass')


catkin: drop redundant build dependency on python-empy

It's enough to have python-empy-native in the build dependencies
of catkin and catkin-runtime. If we ever support on target
development then python-empy should be better added to
catkin's run-time dependencies.

I reviewed it and did a clean test build on this build configuration:
Build Configuration:
BB_VERSION        = "1.33.2"
BUILD_SYS         = "x86_64-linux"
NATIVELSBSTRING   = "fedora-23"
TARGET_SYS        = "i586-oe-linux"
MACHINE           = "qemux86"
DISTRO            = "nodistro"
DISTRO_VERSION    = "nodistro.0"
TUNE_FEATURES     = "m32 i586"
TARGET_FPU        = ""
meta              = "HEAD:ac5c08ea00816852a712a8d7025bce7e865460ec"
meta-oe
meta-python
meta-multimedia   = "master:1dff2351aa6cdafa5a501e8956cb853ab17ed9ae"
meta-qt4          = "master:2c7f8df9039be498f8a2232d1428adb7f4e5e800"
meta-intel-realsense = "master:1d50cb5b82926f8e69a78999e9e8d2ffe2169897"
meta-ros          = "rojkov-empy-native-only-v1:5c53ae284e527d15daf839cf4a1f03ef3f2b4526"


Fix doc about explicit dereference and borrow

Description
Checklist

Do all Lints pass?

[ ] Have you ran pnpm spellcheck?
[ ] Have you ran pnpm fmt?
[ ] Have you ran pnpm lint?

#592  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @vineethk and the rest of your teammates on  Graphite


added a basic meaning function

wrote a horrible code for finding meaning of any word in or out of the dataset. please hide api keys

Can you give the screenshots ?

Test meaning() def. The code.

This branch has conflicts that must be resolved


KAFKA-5548 - Extended validation for SchemaBuilder methods.

More input validation for SchemaBuilder methods.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/kafka-pr-jdk7-scala2.11/5857/
Test PASSed (JDK 7 and Scala 2.11).

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/kafka-pr-jdk8-scala2.12/5843/
Test PASSed (JDK 8 and Scala 2.12).


Terminal output on wrong line

VSCode Version: 1.11.2
OS Version: Windows 10.3 64 bit

Steps to Reproduce:
1.When I opened the vs code, the terminal's output used incorrect line breaks

2.Then I inputted cls, npm run cover, then output still used incorrect line breaks

Duplicate https://github.com/Microsoft/vscode/issues/19665


docs: update overlay mode get-started.md

Thanks for contributing!

What type of PR is this?

kind/doc

What this PR does / why we need it:
docs: update overlay mode get-started.md
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

这个检查失败没有关系嘛？
@weizhoublue @cyclinder


Method to get job by runId

Would be nice to have method to get job by runId getJobByRunId($runId) and get same result as getJob(..) has - the Job object.
// zakladam aby som nezabudol, asi to dorobim

https://github.com/keboola/syrup-queue/blob/84481bc734bb325bec0bfdb868572ce77b30b405/Command/MetricsProcessElasticStatsCommand.php#L133

obsolete


FileNotFoundError when running ./build.py ...

New to treesitter. Just wanted to try in from clojure with java api.

I cloned this project.
Run ./gradlew assemble.
Download tree-sitter-dart;
Run ./build.py libjava-tree-sitter ~/path/to/dart/tree-sitter-dart

And I get: FileNotFoundError: [Errno 2] No such file or directory: 'libjava-tree-sitter/src/parser.c'. And there is no libjava-tree-sitter/src/parser.c in this project (like there is in tree-sitter-dart, for example).
So maybe docs are outdated?
I also tried not to pass the first arg (libjava-tree-sitter), and it failed with:
/Users/m1/IdeaProjects/java/java-tree-sitter/lib/ai_serenade_treesitter_TreeSitter.cc:5:10: fatal error: 'tree_sitter/api.h'
file not found
#include <tree_sitter/api.h>
...
distutils.errors.CompileError: command '/usr/bin/cc' failed with exit code 1

You can specify a different output file with the "-o" flag or omit it to use the default "libjava-tree-sitter" name.
So you could use "./build.py -o 'your-file-name' ~/path/to/dart/tree-sitter-dart".
Regarding the second error you got, have you pulled the tree-sitter submodule? Git doesn't do that automatically on clone.
So inside the repository you pulled, do --> "git submodule update --init --recursive"

Can this information be added to main readme so that 1st timers like me (who never deal with this stuff) will appreciate.


Allow multiple API Keys, but store them hashed

While investigating Auth I looked up info on some other services. One thing that stuck out for me was Google's "App-specific Passwords" model for allowing apps that do not support two-factor auth to authenticate with Google Accounts. I think we should adopt a similar model in NuGet moving forward.
So, an account should be able to have multiple API Keys, each with a name. New API Keys generated in this model would be hashed and thus not recoverable. When the user adds a new API Key, we send the plaintext (over SSL) once and then store the hashed value. This means that API Keys can never be retrieved again, only Revoked or Reset to a new random value. Using this model also encourages users to generate a new key whenever they need to set up a new build server or other automated pusher, which makes it easier to audit who pushes what. Any API Key attached to an account would be authorized to push packages on behalf of that user, and an audit log of which API Key was used to push a particular package would be recorded for use by Support in resolving issues (and possibly displayed to package owners at a future date).

Feature in progress: https://github.com/NuGet/NuGetGallery/issues/3246


node.c: check that malloc succeeds

Make sure the program doesnt die on ENOMEM

:+1: after nitpick. You should have merge perms now.


add deform link to get notifications

🟡 Heimdall Review Status

Requirement
Status
More Info

Reviews

🟡
0/1

Denominator calculation

Show calculation

1 if user is bot
0

1 if user is external
0

From .codeflow.yml

1

Additional review requirements

Show calculation

Max
0

0

From CODEOWNERS

0

Global minimum
0

Max

1

1

1 if commit is unverified
0

Sum
1


Add ignore as optional feature

The ignore crate pulls in regex, which adds to the binary size quite significantly. If we do not need the .ignore features, we can opt out of it and drop the dependency.
This PR locks the ignore crate behind a use-ignore default feature, and adds a walkdir optional feature. When walkdir is enabled, we use the walkdir crate to traverse the directory instead. This does not respect .ignore files.
If neither use-ignore nor walkdir features are enabled, a compile-time error is raised.

Thank you for your PR, and congrats on your first contribution! 🎉


Reading published AAS Submodel Templates from aasx

Reading published AAS Submodel Templates
When trying to read published Submodel Templates from the provided aasx-files i get an error.
I tried to read them like this:
from basyx.aas import model
from basyx.aas.adapter import aasx

filename = "IDTA 2023-0-9 _Template_CarbonFootprint_Final.aasx"

new_object_store: model.DictObjectStore[model.Identifiable] = model.DictObjectStore()
new_file_store = aasx.DictSupplementaryFileContainer()

with aasx.AASXReader(filename) as reader:
    reader.read_into(object_store=new_object_store,
                     file_store=new_file_store)

    new_meta_data = reader.get_core_properties()

And i got the following error:
Traceback (most recent call last):
  File "/xxx/venv/lib/python3.10/site-packages/basyx/aas/adapter/aasx.py", line 142, in read_into
    aasx_origin_part = core_rels[RELATIONSHIP_TYPE_AASX_ORIGIN][0]
IndexError: list index out of range

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/xxx/scratch_1.py", line 10, in <module>
    reader.read_into(object_store=new_object_store,
  File "/xxx/venv/lib/python3.10/site-packages/basyx/aas/adapter/aasx.py", line 144, in read_into
    raise ValueError("Not a valid AASX file: aasx-origin Relationship is missing.") from e
ValueError: Not a valid AASX file: aasx-origin Relationship is missing.

This error could be related to known issues #185 or #666, but it's also possible that it's a separate issue.

Thank you for opening this issue.
Considering the template you tried to read "IDTA 2023-0-9 _Template_CarbonFootprint_Final.aasx" appears to have been released last week, I assume it has been built with the current version of the AASX Package Explorer at version 3.0 of the specification.
Therefore, to my knowledge, it is still aas-package-explorer#666 that is the issue, as also shown by the stack-trace you provided that says that the aasx-origin Relationship is missing

Everytime i try to read an aasx file it fails either with the error above or with this error:
The following required namespaces are not declared: https://admin-shell.io/aas/3/0 - Is the input document of an older version?
Unexpected top-level list {http://admin-shell.io/aas/3/0}assetAdministrationShells on line 3!
Unexpected top-level list {http://admin-shell.io/aas/3/0}assets on line 20!
Unexpected top-level list {http://admin-shell.io/aas/3/0}submodels on line 21!
Unexpected top-level list {http://admin-shell.io/aas/3/0}conceptDescriptions on line 810!

Looks like you'd only have to append an s to http in the namespace of the XML file inside the AASX file in this case.

Where can i get a valid V3 aasx file to test?

You can zip the _aasx directories here individually to obtain the AASX files that are used to test this sdk. Just make sure that the directory itself is not contained in the zip file, i.e. the zip files should contain the file [Content_Types].xml at the top level.

I've contacted the guys to make the aas-package-explorer#666 issue visible again, considering there are obviously lots of shells in the wild that still have this issue, even if the newest version of the AASX Package Explorer fixed it.

thanks for the Reply!
Let's explain further what i did.
i download the official Template from https://github.com/admin-shell-io/submodel-templates/blob/main/published/Contact%20Information/1/IDTA%2002002-1-0_Template_ContactInformation.aasx
If i try to read it:
The following required namespaces are not declared: https://admin-shell.io/aas/3/0 - Is the input document of an older version?
Unexpected top-level list {http://admin-shell.io/aas/2/0}assetAdministrationShells on line 3!
Unexpected top-level list {http://admin-shell.io/aas/2/0}assets on line 20!
Unexpected top-level list {http://admin-shell.io/aas/2/0}submodels on line 21!
Unexpected top-level list {http://admin-shell.io/aas/2/0}conceptDescriptions on line 810!

ok, let's unzip it.
there is no result of http://admin-shell.io/aas/2/0
there are 34 results for /2/ in AssetAdministrationShell---61CFE571.aas.xml
<aas:key type="GlobalReference" local="false" idType="IRI">http://admin-shell.io/DataSpecificationTemplates/DataSpecificationIEC61360/2/0</aas:key>
there are 60 results for http://admin-shell , 57 in AssetAdministrationShell---61CFE571.aas.xml
If i replace all /2/ with /3/ we get the same error:
The following required namespaces are not declared: https://admin-shell.io/aas/3/0 - Is the input document of an older version?
Unexpected top-level list {http://admin-shell.io/aas/3/0}assetAdministrationShells on line 3!
Unexpected top-level list {http://admin-shell.io/aas/3/0}assets on line 20!
Unexpected top-level list {http://admin-shell.io/aas/3/0}submodels on line 21!
Unexpected top-level list {http://admin-shell.io/aas/3/0}conceptDescriptions on line 810!

if i replace all http://admin with https://admin it fails with:
Traceback (most recent call last):
  File "./basyx/basyx/aas/adapter/aasx.py", line 144, in read_into
    aasx_origin_part = core_rels[RELATIONSHIP_TYPE_AASX_ORIGIN][0]
IndexError: list index out of range

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "./src/__main__.py", line 27, in <module>
    reader.read_into(object_store=new_object_store,
  File "./basyx/basyx/aas/adapter/aasx.py", line 146, in read_into
    raise ValueError("Not a valid AASX file: aasx-origin Relationship is missing.") from e
ValueError: Not a valid AASX file: aasx-origin Relationship is missing.

What's also confusing is the line numbers, because there is no occur of http://admin-shell.io/aas/3/0 in this lines (line 1-28):
<?xml version="1.0"?>
<aas:aasenv xmlns:IEC="http://admin-shell.io/IEC61360/3/0" xmlns:xsi="http://w3.org/2001/XMLSchema-instance" xmlns:abac="http://admin-shell.io/aas/abac/3/0" xsi:schemaLocation="http://admin-shell.io/aas/3/0 AAS.xsd http://admin-shell.io/IEC61360/3/0 IEC61360.xsd" xmlns:aas="http://admin-shell.io/aas/3/0">
  <aas:assetAdministrationShells>
    <aas:assetAdministrationShell>
      <aas:idShort />
      <aas:identification idType="Custom">AssetAdministrationShell---61CFE571</aas:identification>
      <aas:assetRef>
        <aas:keys />
      </aas:assetRef>
      <aas:submodelRefs>
        <aas:submodelRef>
          <aas:keys>
            <aas:key type="Submodel" local="true" idType="IRI">https://example.com/ids/sm/1231_6162_1022_9579</aas:key>
          </aas:keys>
        </aas:submodelRef>
      </aas:submodelRefs>
      <aas:conceptDictionaries />
    </aas:assetAdministrationShell>
  </aas:assetAdministrationShells>
  <aas:assets />
  <aas:submodels>
    <aas:submodel>
      <aas:idShort>ContactInformations</aas:idShort>
      <aas:identification idType="IRI">https://example.com/ids/sm/1231_6162_1022_9579</aas:identification>
      <aas:kind>Template</aas:kind>
      <aas:semanticId>
        <aas:keys>
          <aas:key type="ConceptDescription" local="true" idType="IRI">http://admin-shell.io/zvei/nameplate/1/0/ContactInformations</aas:key>

line 810-828:
  <aas:conceptDescriptions>
    <aas:conceptDescription>
      <aas:idShort>RoleOfContactPerson</aas:idShort>
      <aas:identification idType="IRDI">0173-1#02-AAO204#003</aas:identification>
      <aas:embeddedDataSpecification>
        <aas:dataSpecificationContent>
          <aas:dataSpecificationIEC61360>
            <IEC:preferredName />
            <IEC:shortName />
            <IEC:unit />
            <IEC:dataType />
            <IEC:definition>
              <IEC:langString lang="en">function of a contact person in a process</IEC:langString>
            </IEC:definition>
          </aas:dataSpecificationIEC61360>
        </aas:dataSpecificationContent>
        <aas:dataSpecification>
          <aas:keys>
            <aas:key type="GlobalReference" local="false" idType="IRI">http://admin-shell.io/DataSpecificationTemplates/DataSpecificationIEC61360/3/0</aas:key>

It would be nice if you could help me figure out what's wrong with this files.
I don't know which tool or sdk is right or wrong.
official templates <-> basyx-python-sdk = doesn't work
basyx-python-sdk <-> aasx-server = doesn't work
if i try to upload a aasx file that i created fresh with basyx tutorial 1.5 the server complains:
aasx-server    | fail: IO.Swagger.Lib.V3.Middleware.ExceptionMiddleware[0]
aasx-server    |       Object reference not set to an instance of an object.

Same with the basyx testfiles.
Every project assert to support V3, but they don't work together.
PS:

You can zip the _aasx directories here individually to obtain the AASX files that are used to test this sdk.

That work's, i can read this files. But i would like to use templates. I don't want to create every file myself if i can avoid it.
Thanks for your time.

If i replace all /2/ with /3/ we get the same error:

You cannot just do that. The /2/ indicates that it is a version 2 XML file. Many things changed with the move to /3, e.g. Assets were removed and AssetInformation was introduced instead, to name just one. You can use version 2 of the SDK, e.g. release 0.2.2 or the v2.0.1 branch. However, there are still a lot of errors in the templates, @zrgt has published fixed V2 templates here: https://github.com/zrgt/submodel-templates-fixed

if i replace all http://admin with https://admin it fails with:

Did you perhaps also replace this in the .rels files?

What's also confusing is the line numbers, because there is no occur of http://admin-shell.io/aas/3/0 in this lines (line 1-28):

The curly braces {} indicate an XML namespace in the error message. This corresponds to aas: in the XML file. You can see the namespace corresponding to aas: at the top of the XML file:
xmlns:aas="http://admin-shell.io/aas/3/0"

Oh wow, thank you for your detailed research!
I checked this Submodel Template's history and it's last been touched 2 years ago: https://github.com/admin-shell-io/submodel-templates/commits/main/published/Contact Information/1
Since v3.0 of the metamodel was released in April of last year, the SMT must be of version 2.0.1 of the metamodel (or even older).
If you really need to use it, can you please try to open it with release 0.2.2 of our SDK?
(Additionally, it would make sense to me to request an update of the SMT to v3.0 by the IDTA)

if i replace all http://admin with https://admin it fails with

Back then, the http://www.admin-shell-io reference was still correct and part of the specification.

If i replace all /2/ with /3/ we get the same error

Since some of the model objects changed between v3.0 and v2.0.1, doing this will most likely break everything.

What's also confusing is the line numbers, because there is no occur of http://admin-shell.io/aas/3/0 in this lines (line 1-28)

Now it's me that gets confused. The file cannot be of v3.0. I have no idea, why the /3/0 even appears in any of the namespaces.

Every project assert to support V3, but they don't work together.

My conclusion that I draw from the information that I can see right now:

The Submodel Template you try to read in is actually based on an older version of the metamodel
(And hopefully the BaSyx SDKs do work together)

We try our best to follow the specification of the AAS verbatim.

Now it's me that gets confused. The file cannot be of v3.0. I have no idea, why the /3/0 even appears in any of the namespaces.

This is probably because @Kuchsn replaced /2/0 with /3/0 by himself in an effort to make them compatible.

I will close this issue now, but please let us know if you have further problems with using our SDK!

I'm a little bit disappointed, that things get updated so slow, wrong communication, miss understanding versioning.

Yeah, that annoys me, too. As you can see in #185, we get a lot of issues similar to yours. These minor changes like http:// -> https:// in the XML namespace and the removal of www. in the OPC relationship types are just completely unnecessary and not properly highlighted in the spec, which is why a lot of SDK developers seem to miss them.

But thanks for your explanations. I will check out the fixed templates and if they don't work i will have to do it from scratch..

Sure, just keep in mind that these are for V2 and that you'll need the older basyx-python-sdk version.


Update to use ww corporate FOSSA api token

The current API token is linked to my personal account. Created a new one using corporate account and replacing it.

LGTM


API version were missing

Package Name:
Package Version:
Operating System:
Python Version:

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
1.
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

Hi @neapan, can you please provide some more details around the affected package, python version, the scenario you are trying to execute for the team to better assist you ?

Please disregard that.
Thank you for reaching out.


question: package manager

<EMAIL_ADDRESS>is currently in use, but the zero-install dependencies are not committed to this repository. Should they? Or should pnpm be used instead, as for most nuxt repositories? I'd be happy to make a contribution once I know :)

@dargmuesli Actually, i disable zero-install on purpose. It came with many issue when i was first time use yarn berry along with nuxt 3.
i haven’t tried pnpm before. Is any benefit using pnpm compare to yarn?

Ah, now I see the .yarnrc.yml!
For me the main benefit is having a centralized package store from which all projects link their dependencies to. That allows for libraries only having to be downloaded once and not for every project. That also makes node_modules (or .yarn) directories very small.


Add version to inventory contract

This would make it easier to discover what functionality to expect from a deployed contract (beyond just the method signatures).

I wanted to add a comment here. I started down the road to oss our version implementation from 1o1 to use in inventory as well.
I realized that we pivoted to using 725Y for storage, which will mean we have to tease out our impl into something more shareable.
Maybe next week we'll have that in a state to be integrated with.  In the meantime here's the general scheme in typescript to assess.
export interface Version {
  major: number;
  minor: number;
  patch: number;
}

export function packVersion(version?: Version): Uint8Array {
  const versionArray = new Uint8Array(32);

  if (version) {
    const majorBytes = ethers.utils.arrayify(
      ethers.BigNumber.from(version.major).toHexString()
    );
    const minorBytes = ethers.utils.arrayify(
      ethers.BigNumber.from(version.minor).toHexString()
    );
    const patchBytes = ethers.utils.arrayify(
      ethers.BigNumber.from(version.patch).toHexString()
    );

    versionArray.set(majorBytes, 20 - majorBytes.length); // major occupies first 20 bytes
    versionArray.set(minorBytes, 30 - minorBytes.length); // minor occupies next 10 bytes
    versionArray.set(patchBytes, 32 - patchBytes.length); // patch occupies last 2 bytes
  }

  return versionArray;
}

export function getPackedVersion(version?: Version): BigNumber {
  const versionArray = packVersion(version);
  return BigNumber.from(ethers.utils.hexlify(versionArray));
}

export function unpackVersion(versionPacked: BigNumber): Version {
  const major = versionPacked.shr(160).toNumber();
  const minor = versionPacked
    .shr(80)
    .and(BigNumber.from("0xFFFFFFFFFFFF"))
    .toNumber();
  const patch = versionPacked.and(BigNumber.from("0xFFFFFFFFFFFF")).toNumber();
  return { major, minor, patch };
}

We'll just use semantic versioning and only the admin could change that, should be a simple string saved in the contract, overcomplex this is not required or necessary.


Retry resource synchronization caused by storage component exceptions

What would you like to be added?
If the current resource synchronizer fails to add, delete or change data due to a storage layer problem when synchronizing resources, it will print a log and discard the event.
https://github.com/clusterpedia-io/clusterpedia/blob/75446232bf5f04c4f1c590e77b46cd14511a2efe/pkg/synchromanager/clustersynchro/resource_synchro.go#L344-L355
If resources change frequently, then a single update failure does not cause any problems, but for deletion events or when changes are infrequent, dropping events can cause data inconsistencies.
We need to ensure that the resources must be consistent with the resources in the cluster, and there must not be dirty data or missing some resources.
So the following policy is defined for resource synchronization:

Keep retrying if the resource synchronization failure is caused by a storage component exception
To avoid resource accumulation in memory, when there are more than 5 retries and the data in the pressure queue is greater than 10, only 10 resources are kept, the rest are discarded, and stop informer.
Restart the informer when the resource has been written successfully and the pressure queue has been emptied of data

Because of data discard, the version of the resource recorded in the informer's cache may not represent the version of the resource written to the storage component, so we need to keep two copies of the resource version:

storage resource versions records the resource versions of resources saved to the storage layer for successful operations
informer store used by informer

If the resources are discarded, a new informer store will be generated from the storage resource versions and passed to the informer on the next restart.

The start and stop of the resource informer is not only controlled by the cluster state, but by two conditions together:

Cluster Status: If two consecutive health checks fail, stop the resource synchronizer informer
Storage Component Status: If a resource fails due to an exception in the storage component, and the resource retries more than 5 times, and the number of data in the pressure queue is greater than 10, stop informer

Additional optimizations that are not part of this feature:

The restart of the resource informer may only be a few seconds or minutes apart, when the resource version may still be valid, to avoid the data transfer brought by the direct list, we could change the reflector from List-Watch to Watch-Relist

Why is this needed?
We can't ignore resource events just because of exceptions in storage components

/milestone 0.5.0

/milestone v0.5.0


don't remove representative peers in any-namespace

issue #236
sub task:

[ ]  handling cases of empty nsSelector (any-namespace) with non-empty podSelector : don't refine its representative peer if there is a matching pod in a specific namespace

in this commit
added two examples of exposure to an existing namespace (having real pod in the ns)
with current approach:

in first test test_conn_to_all_pods_in_an_existing_ns since we have a real pod in backend we don't see "all pods" exposure line
in second test test_conn_to_new_pod_in_an_existing_ns I used specific podSelector and so we see it in the exposure report


Insertion Sort Algorithm

Write an implementation of insertion sort algorithm on an integer array with proper explanation through comments.

@prafulla-k-roy Can you please assign this to me?
Thanks!

I can do this in java @prafulla-k-roy can you assign this to me

hey @prafulla-k-roy , I can implement this is C++, and would love to do this.

Hii... kindly assign this to me . I can implement this in CPP.

Mission Accomplished Everyone!!!


No versions available for glab

There appears to be no available versions for installing or updating the glab tool:
$ binenv update glab
2021-10-01T08:49:06-05:00 INF retrieving distribution cache from https://raw.githubusercontent.com/devops-works/binenv/develop/distributions/cache.json
2021-10-01T08:49:06-05:00 INF fetched updates for 194 distributions

$ binenv install glab
2021-10-01T08:49:13-05:00 WRN version for "glab" not specified; using ""
2021-10-01T08:49:13-05:00 ERR unable to install "glab" () error="unable to select latest stable version for \"glab\": no stable version available. May be run 'binenv update glab' ?"

$ curl https://raw.githubusercontent.com/devops-works/binenv/develop/distributions/cache.json 2>/dev/null| grep glab
  "glab": [],

Thanks !
This seems to be a dupe or #156 and #157
Probably some issue with cache generattion. We'll look into that.
In the meantime, you can get out of trouble using:
binenv update glab -f

May be not a duplicate
No versions available even with this in the cache:
  "glab": [
    "1.20.0",
    "1.20.0-pre1",
    "1.19.0",
    "1.18.1",
    "1.18.0",
    "1.17.0",
    "1.16.0",
    "1.15.0",
    "1.14.0",
    "1.13.1",
    "1.13.0",
    "1.12.1",
    "1.12.0",
    "1.11.1",
    "1.11.0",
    "1.11.0-pre2",
    "1.11.0-pre1",
    "1.10.0",
    "1.9.1",
    "1.9.0",
    "1.8.1",
    "1.8.0",
    "1.7.1",
    "1.7.0",
    "1.6.2",
    "1.6.1",
    "1.6.0",
    "1.5.0",
    "1.5.1",
    "0.1.0"
  ],

binenv install glab
2021-10-13T09:40:21+06:00 WRN version for "glab" not specified; using "1.21.1"
fetching glab version 1.21.1 100% |█████████████████████████████████████████████████████████████████████████████████████████████████████| (5.9/5.9 MB, 5.733 MB/s)
2021-10-13T09:40:24+06:00 INF "glab" (1.21.1) installed


[ENHANCEMENT] Support XFS for RWX volumes

Is your feature request related to a problem? Please describe.
It appears that the longhorn-share-manager only supports ext4 filesystems. When I create an RWX volume and then create the PV via the Longhorn UI, I select xfs as the filesystem type. However, after mounting the volume, I notice that longhorn-share-manager formats it as ext4. I can create the the volume as an RWO with XFS, and when I change the access type to RWX, the share manager fails to mount the volume because it's trying to mount it as an ext4 filesystem.
Describe the solution you'd like
I took a look through the longhorn-share-manager code, and it looks like, indeed, ext4 is hardcoded into the mount code. XFS is not mentioned anywhere in the codebase. I would like to see XFS support built into share-manager.
Describe alternatives you've considered
I have tried using ext4 volumes, but with the use case I have (personal file storage, up to 1TB, with large files such as videos), the volume seems to want to rebuild every time a large batch of incoming files is uploaded.
I have also tried running XFS in RWO, and it seems to be stable. However, I have a use case where I want to scale the availability of the application heads, and I want to support an out-of-band backup, which requires an RWX volume.

This can be done together with
https://github.com/longhorn/longhorn/issues/2096#issuecomment-857225036 and https://github.com/longhorn/longhorn/issues/2659#issuecomment-857219535
I want to add the ability to configure the nfs-server / share-manager via a config map.
Then the user can make the appropriate changes or we can derive the fs type for the share-manager used volume as part of pvc/pv volume attributes lookup.

I have tried using ext4 volumes, but with the use case I have (personal file storage, up to 1TB, with large files such as videos), the volume seems to want to rebuild every time a large batch of incoming files is uploaded.

What is the underlying disk? Is it an HDD?

For this volume, it is an HDD. I had problems in the past with all workloads running on HDDs. After reading the hardware guide (my mistake for not reading that section first), I did switch the smaller volumes to SSDs and saw improvements, but getting SSDs sized for this particular workload isn't practical for the budget. I am thinking that, if HDDs continue to be problematic, I may have to just set up the HDDs as a different storage solution, perhaps something like Ceph.

@edjmao we made some addition to better support spinning disks ref#https://github.com/longhorn/longhorn/issues/2206
They will be available in v1.2 as well as v1.1.3 if you want to provide early feedback you can deploy the master for testing on a separate cluster that utilizes hdds :)

That's awesome! I see that in the 1.2 release notes. I'll see if I can spin something up on a test bench I have using kind.

Validation: PASSED
Test steps: https://github.com/longhorn/longhorn/issues/2867#issuecomment-904204920


Create Pesayetu dockerfile

Description
This PR adds a dockerfile to deploy Pesayetu.
Type of change

[x] New feature (non-breaking change which adds functionality)

Screenshots
Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation

I'm out of the @koechkevin, why do we need to add that?

I'm out of the @koechkevin, why do we need to add that?

@kilemensi if we are to avoid using pnpm start or next start  serving production static files then we can use the custom server to start.

May be @koechkevin ... my main question is why or where does pnpm get the custom server to run but normal npm can not?

May be @koechkevin ... my main question is why or where does pnpm get the custom server to run but normal npm can not?

@kilemensi npm start and pnpm start  work the same way here. Perhaps your proposal was to use npm instead of npm?

May be @koechkevin ... my main question is why or where does pnpm get the custom server to run but normal npm can not?

@kilemensi npm start and pnpm start work the same way here. Perhaps your proposal was to use npm instead of npm?

Sorry, no, I meant node @koechkevin ... why can't node find whatever pnpm/npm uses to start the app?

May be @koechkevin ... my main question is why or where does pnpm get the custom server to run but normal npm can not?

@kilemensi npm start and pnpm start work the same way here. Perhaps your proposal was to use npm instead of npm?

Sorry, no, I meant node @koechkevin ... why can't node find whatever pnpm/npm uses to start the app?

I believe this is the script executed by next start.

Please test the changes I've pushed @koechkevin

@kilemensi Just tested this and it works like a charm. Thank you. @koechkevin Your review before we merge it.


classSet deprecated

Hi,
we get this warning while using your library :
"Warning: React.addons.classSet will be deprecated in a future version. See http://fb.me/react-addons-classset"
It seems that classSet is used in ToastMessage.
Hope that helps,
Regards,
Antoine

Shouldn't this be closed?

Released as v1.5.0, close now. Thanks @L8D

Great ! Thansk


Fix Security Dependabot Issues

Describe the bug
Dependabot has raised security issues in the project.
Expected behavior
Dependabot should not have any security issues upon fix.

This Issue is closed with PR #35.


update dpc_common.hpp

Existing Sample Changes

Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes Issue#
With the current dpc_common.hpp, running make shows the following error:
/opt/intel/oneapi/dev-utilities/2021.8.0/include/dpc_common.hpp:14:36: error: use of undeclared identifier 'cl' static auto exception_handler = [](cl::sycl::exception_list eList) {                                    ^ 1 error generated. make[2]: *** [src/CMakeFiles/openmp_reduction.dir/build.make:63: src/CMakeFiles/openmp_reduction.dir/main.cpp.o] Error 1 make[1]: *** [CMakeFiles/Makefile2:122: src/CMakeFiles/openmp_reduction.dir/all] Error 2 make: *** [Makefile:84: all] Error 2
Changing the header from sycl/sycl.hpp to CL/sycl.hpp in dpc_common.hpp resolves the issue.
External Dependencies
List any external dependencies created as a result of this change.
Type of change
Please delete options that are not relevant. Add a 'X' to the one that is applicable.

[X] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Implement fixes for ONSAM Jiras

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[X] Command Line
[ ] oneapi-cli
[ ] Visual Studio
[ ] Eclipse IDE
[ ] VSCode
[ ] When compiling the compliler flag "-Wall -Wformat-security -Werror=format-security" was used

The current version of dpc_common.hpp is located here. It did not get picked up as part of the base kit packaging in the 2023.0 release but will be picked in the 2023.1 release.

Going to close this PR out. I've verified that it compiles and runs when using the updated dpc_common.hpp file. It will be bundled with the next version of the toolkit.


Feature Request: provide a mechanism to change the conversion from Pydantic to Strawberry

Currently, we use a registration mechanism and some basic rules to figure out how a type should be converted from Pydantic to Strawberry and vice versa. The rules map scalars to their equivalent scalar using some hard-coded mappings, then recursively build up more complex types from there.
This is all great for automatic conversion, but there are use cases where I'd like to be able to provide a registered Strawberry type that doesn't follow these rules, and instead uses some custom logic to convert to and from the Pydantic type.
An example of when this would be useful is if I'm defining a custom scalar that I want to be used in some of the fields of the model:
class MyModel(pydantic.BaseModel):
    my_field: int

CustomInt = strawberry.scalar(NewType("CustomInt", int), ...)

@strawberry.experimental.pydantic.type(model=MyModel)
class MyStrawberryModel:
    my_field: strawberry.auto  # I want this to be wrapped in CustomInt during the conversion so it uses my custom serializer logic

Another time this would be helpful is when the Pydantic model represents some type or value that I don't want to translate directly to GraphQL types, either because it is cumbersome/undesirable, or because it is actually not representable in GraphQL. An example of the latter case would be anything involving unions of scalar fields, which GraphQL doesn't know how to represent. If I could provide custom conversion logic, I could keep the union type in Pydantic but provide some alternative concrete type in Strawberry land.
class MyModel(pydantic.BaseModel):
    my_field: Union[int, str]

@strawberry.experimental.pydantic.type(model=MyModel)
class MyStrawberryModel:
    my_field: strawberry.auto  # I want this to be mapped to a specific type in Strawberry

The overall goal here is to be able to support existing (possibly highly used and constrained already) Pydantic models in Strawberry with more flexibility. There are definitely cases where it's helpful to be able to change the data representation during conversion beyond these, this is just what I've run into during my implementation. The problem today is that if you want to do custom conversions/types for one piece of a deeply nested hierarchy, the entire conversion process from Pydantic fails because the types aren't registered as being related to the Pydantic models.

This is reasonable. Did you have any idea on how it would look?
The first idea I can think of is of doing a global configuration, but this is something we don't really support right now[1].
The other option is to add a configuration on the schema and do the conversion of the types later 🤔
[1]: we support per schema configuration at the moment

My thought was something like this:
class MyModel(pydantic.BaseModel):
    my_field: int

CustomInt = strawberry.scalar(NewType("CustomInt", int), ...)

@strawberry.experimental.pydantic.type(model=MyModel)
class MyStrawberryModel:
    my_field: CustomInt

    def to_pydantic(self):
        return MyModel(my_field=int(self.my_field))

    @classmethod
    def from_pydantic(cls, pydantic_model):
        return MyStrawberryModel(my_field=CustomInt(pydantic_model.my_field))

Note that this code works today if you use strawberry.type and then set up the _strawberry_type and _pydantic_type references yourself, but that's a horrible hack 😆

just to clarify :)
for the first example whats the rationale behind not doing it in the parse_value / serialize argument of scalar type?
class MyModel(pydantic.BaseModel):
    my_field: int

CustomInt = strawberry.scalar(NewType("CustomInt", int), parse_value = my_custom_parsing, serialize = my_custom_serialize)

@strawberry.experimental.pydantic.type(model=MyModel)
class MyStrawberryModel:
    my_field: CustomInt

is the reason to provide that logic for that particular MyStrawberryModel instead of that particular type?

So if you try that example it actually doesn't work for me, because it's not clear what's supposed to happen when you have a field redefined in the Strawberry model but you don't use auto. What happens right now is confusing, if it's the only field in the model like this example it fails because technically you haven't pulled any fields from the pydantic model. If you add a second field, you will get the desired behavior, but only because there is an undocumented feature that the Pydantic converter implicitly calls the constructor of the type you specify on the Strawberry type (I'm still not sure why this actually happens btw). So in that case it will wrap the int in CustomInt when converting to Strawberry, and then things will work.
I'm not sure what we're actually supposed to do in this kind of case, because the current behavior gives you some limited control over the conversion behavior by specifying alternate types, but only allows you to use types that are convertible to each other through their constructors. This behavior just seems weird and counterintuitive to me, and I think a more explicit approach is better in the long run, whether that's refining and documenting this behavior or something like I've proposed here.
Additionally, if you want to make more structural changes to the type (like combining two fields into one or flattening a list or something), then the type conversion method is definitely not powerful enough to use.

Additionally, if you want to make more structural changes to the type (like combining two fields into one or flattening a list or something), then the type conversion method is definitely not powerful enough to use.

yep definitely agreed on this. overriding to_pydantic and from_pydantic is nice and explicit / discoverable too. :)

I'm not sure what we're actually supposed to do in this kind of case, because the current behavior gives you some limited control over the conversion behavior by specifying alternate types, but only allows you to use types that are convertible to each other through their constructors. This behavior just seems weird and counterintuitive to me, and I think a more explicit approach is better in the long run, whether that's refining and documenting this behavior or something like I've proposed here.

Anyone have thoughts on this part? I'm thinking the current behavior is nice but can be confusing, but maybe with some documentation and cleanup it could be useful?


dataclass config fields not warranted in json schema (1.8)

Checks

[X] I added a descriptive title to this issue
[X] I have searched (google, github) for similar issues and couldn't find anything
[X] I have read and followed the docs and still think this is a bug

Bug
Output of python -c "import pydantic.utils; print(pydantic.utils.version_info())":
             pydantic version: 1.8
            pydantic compiled: True
                 install path: /Users/dafcok/miniconda3/lib/python3.6/site-packages/pydantic
               python version: 3.6.8 |Anaconda, Inc.| (default, Dec 29 2018, 19:04:46)  [GCC 4.2.1 Compatible Clang 4.0.1 (tags/RELEASE_401/final)]
                     platform: Darwin-19.6.0-x86_64-i386-64bit
     optional deps. installed: ['devtools', 'dotenv', 'email-validator', 'typing-extensions'

from pydantic import BaseModel
from pydantic.dataclasses import dataclass

# works
class A(BaseModel):
    a: str

    class Config:
        fields = {"a": {"description": "descr"}}

assert A.schema()["properties"]["a"]["description"] == "descr"

# works on 1.7.3
# fails on 1.8
@dataclass(config=A.Config)
class Ad:
    a: str

assert Ad.__pydantic_model__.schema()["properties"]["a"]["description"] == "descr"

Traceback (most recent call last):
  File "tests/test_schema_descr.py", line 24, in <module>
    assert Ad.__pydantic_model__.schema()["properties"]["a"]["description"] == "descr"
KeyError: 'description

It seems that config.fields is not processed in the decorator.

Thanks for reporting, see the discussion on #2437, this is rooted in a wider problem which I'm fixing now.


Include preloading in documentation

Include info from #218 and #223 in documentation as soon as we describe using an external dask cluster.

Hmm, somehow we forgot about this change - I'll assign it to the 0.4 milestone

This is partly documented in #1151. API documentation will be included in #1158.

...now in #1170!


Need to setup unique index with a where condition

We have a system where we need to express a unique index for all in-use (not-soft-deleted) resources in a multi-tenant system. The simplified SQL is
CREATE UNIQUE NONCLUSTERED INDEX [IX_Unique_Composite_Name_For_Active]
    ON [dbo].[Resources]([TenantId] ASC, [Name] ASC)
    WHERE MarkedForDeletionAt IS NULL; -- <== this!
GO

How can this be expressed in EF Core 3.x ? The closest is
resource
.HasIndex(r => (r.MarkedForDeletionAt == null) ? new { r.TenantId, r.Name } : null ) //
.IsUnique();

but that throws an exception
The properties expression 'r => IIF((r.MarkedForDeletionAt == null), new <>f__AnonymousType8`4(TenantId = r.TenantId, Name  = r.Name), null)' is not valid. The expression should represent a simple property access: 't => t.MyProperty'. When specifying multiple properties use an anonymous type: 't => new { t.MyProperty1, t.MyProperty2 }'. (Parameter 'propertyAccessExpression')

Questions:

How do we express this constraint into the EF Core model itself?

If EF Core doesn't support this at the moment (please do soon), what workflow is suggested for engineers using EF Core? Can we express most of the model EF and then apply the remaining conditions as some raw SQL that's always applied?

Further technical details
EF Core version: 3.0.0-preview7.19362.6
Database Provider: Microsoft.EntityFrameworkCore.SqlServer
Operating system: Windows 10 x64 v1903
IDE: Visual Studio 2019 16.2.1

Use
resource.HasIndex(r => new { r.TenantId, r.Name }).IsUnique().HasFilter("[MarkedForDeletionAt] IS NULL")

Confirmed that this works. Thank you.


CDN not working with Caddy Proxy on AWS S3

The configuration operates smoothly with MinIO and Caddy; however, it encounters issues when attempting to utilize AWS S3
server image ghcr.io/kamilkisiela/graphql-hive/server:7399aa50bef74464c0012c360479a1a927d7a1a0
Here are the environment variables
  "S3_ACCESS_KEY_ID": "xxxx",
  "S3_BUCKET_NAME": "my-bucket",
  "S3_ENDPOINT": "https://s3.us-west-2.amazonaws.com",
  "S3_PUBLIC_URL": "https://caddy.example.com",
  "S3_SECRET_ACCESS_KEY": "xxxx",

and caddy
      - command:
        - caddy
        - reverse-proxy
        - --from
        - :8083
        - --to
        - my-bucket.s3-us-west-2.amazonaws.com:443
        - --change-host-header

also tried to enable debug logs and specify AWS keys but no luck
        env:
        - name: CADDY_LOG
          value: debug
        - name: AWS_ACCESS_KEY_ID
          value: xxx
        - name: AWS_SECRET_ACCESS_KEY
          value: xx/xx/xx

{"level":20,"time":1692161494464,"pid":1,"hostname":"main-graphql-hive-server-dfb6d8c88-868wl","msg":"Parsing request to extract GraphQL parameters - (requestId=C09ip5n3Q9yOrErJz4BzJA/0000000041)"}
{"level":20,"time":1692161494464,"pid":1,"hostname":"main-graphql-hive-server-dfb6d8c88-868wl","msg":"Processing GraphQL Parameters - (requestId=C09ip5n3Q9yOrErJz4BzJA/0000000041)"}
{"level":20,"time":1692161494483,"pid":1,"hostname":"main-graphql-hive-server-dfb6d8c88-868wl","msg":"Translating Organization Clean ID (selector={\"organization\":\"example\"}) - (requestId=C09ip5n3Q9yOrErJz4BzJA/0000000041)"}
{"level":20,"time":1692161494484,"pid":1,"hostname":"main-graphql-hive-server-dfb6d8c88-868wl","msg":"Translating Project Clean ID (selector={\"organization\":\"example\",\"project\":\"test\"}) - (requestId=C09ip5n3Q9yOrErJz4BzJA/0000000041)"}
{"level":20,"time":1692161494484,"pid":1,"hostname":"main-graphql-hive-server-dfb6d8c88-868wl","msg":"Translating Target Clean ID (selector={\"organization\":\"example\",\"project\":\"test\",\"target\":\"development\"}) - (requestId=C09ip5n3Q9yOrErJz4BzJA/0000000041)"}
{"level":20,"time":1692161494628,"pid":1,"hostname":"main-graphql-hive-server-dfb6d8c88-868wl","msg":"Processing GraphQL Parameters done. - (requestId=C09ip5n3Q9yOrErJz4BzJA/0000000041)"}
{"level":30,"time":1692161494628,"pid":1,"hostname":"main-graphql-hive-server-dfb6d8c88-868wl","msg":"[200] (::ffff:<IP_ADDRESS>) POST /graphql 'CDNAccessTokens_CDNAccessTokenCreateMutation' (reqId=C09ip5n3Q9yOrErJz4BzJA/0000000041)"}

The above logs are from the server. Is there anything else I might be overlooking? Thank you.

Hello @n1ru4l , could you kindly review this issue?"

It seems like there is an error happening on either caddy or s3 that is swallowed within the business log.
Could you add logging here and build + run the images again to gather more insight? https://github.com/kamilkisiela/graphql-hive/blob/1454ea351384e5d8c531627f8103de857485455a/packages/services/api/src/modules/cdn/providers/cdn.provider.ts#L149

It indicates a 403 error from S3, even though I can successfully publish artefacts to S3, which means the server has the capability to write to S3. This situation might be related to Caddy?
  options: {
    status: 403,
    statusText: 'Forbidden',
    headers: {
      'x-amz-request-id': 'xxx',
      'x-amz-id-2': 'GWRLzk35qJXD1GQy3+xxxx+xx/eR40Qe5w=',
      'content-type': 'application/xml',
      date: 'Sun, 20 Aug 2023 15:26:23 GMT',
      server: 'AmazonS3',
      connection: 'close'
    },
    url: 'https://s3.us-west-2.amazonaws.com/my-bucket/cdn-keys/5f84bfb4-b3f5-4f2c-97e2-2fa777956e35/0005b7d2-9f3c-4cf8-96ec-c3e061b656c9'
  },
  bodyUsed: false,
  contentType: 'application/xml',
  contentLength: null,
  _bodyFactory: [Function: bodyFactory],
  _generatedBody: null,
  bodyType: 'Readable',
  headers: Headers {
    'x-amz-request-id': 'xxx',
    'x-amz-id-2': 'GWRLzk35qJXD1GQy3+xxxx+xx/eR40Qe5w=',
    'content-type': 'application/xml',
    date: [ 'Sun', '20 Aug 2023 15:26:23 GMT' ],
    server: 'AmazonS3',
    connection: 'close'
  },
  status: 403,
  statusText: 'Forbidden',
  url: 'https://s3.us-west-2.amazonaws.com/my-bucket/cdn-keys/5f84bfb4-b3f5-4f2c-97e2-2fa777956e35/0005b7d2-9f3c-4cf8-96ec-c3e061b656c9',
  redirected: false,
  type: 'default'
}

@adiii717 Can you confirm this issue is still present without using caddy as a proxy?

Hello, we've attempted various approaches to address the problem, but unfortunately, we haven't been able to find a solution. As a result, we've chosen to explore Wundergraph. Given this, we can close this issue, as I won't be able to attempt further troubleshooting personally

Hey @adiii717, if possible please share the approaches you tried for solving your issue, so other people experiencing the same problem don't have to start from scratch.
If anyone else is reading this I am happy to re-open this issue and help finding a solution.
From the clients we work with that use S3, we recommend skippinh the caddy proxy and point to the S3 bucket directly. The caddy proxy in the docker-compose file is only there to work around local host issues with pre-signed urls.


bug: Jellyfin does not scans using "notify"

Description of the bug
As the title says, jellyfin does not perform scan (so media which got added is not appearing in jellyfin). Same approach does work for Plex fine, it does perform scan. Everything is in docker containers, they are using same network.
Again, plex works, jellyfin not. Radarr/Sonarr hooks are not used, i wanna use only notify and make it work also for jellyfin :)
This is my conifguration:
[app]
hostname = "<IP_ADDRESS>"
port = REDACTED_PORT
database_url = "REDACTED_DATABASE_URL"
log_level = "info"

[auth]
username = "REDACTED_USER"
password = "REDACTED_PASSWORD"

[opts]
check_path = false
max_retries = 5
default_timer_wait = 30
cleanup_days = 10

[triggers.my_notify]
type = "notify"
paths = ["/home/REDACTED_USER/rclone"]

[triggers.my_notify.timer]
wait = 30

[triggers.my_sonarr]
type = "sonarr"

[triggers.my_sonarr.timer]
wait = 30

[triggers.my_radarr]
type = "sonarr"

[triggers.my_radarr.timer]
wait = 30

[targets.my_plex]
type = "plex"
url = "http://plex:32400"
token = "REDACTED_TOKEN"

[targets.my_jellyfin]
type = "jellyfin"
url = "http://jellyfin:8096"
token = "REDACTED_API_TOKEN"

[webhooks]

Logs:
2024-09-22T09:31:20.036495Z  INFO autopulse: 💫 autopulse starting up...
2024-09-22T09:31:20.053356Z  INFO actix_server::builder: starting 32 workers
2024-09-22T09:31:20.053402Z  INFO actix_server::server: Tokio runtime found; starting in existing Tokio runtime
2024-09-22T09:31:20.053408Z  INFO actix_server::server: starting service: "actix-web-service-REDACTED_IP:REDACTED_PORT", workers: 32, listening on: REDACTED_IP:REDACTED_PORT
2024-09-22T09:36:33.812600Z  INFO autopulse::service::runner: sent 4 files to targets

Are you certain the paths are correct for the Jellyfin?

Are you certain the paths are correct for the Jellyfin?

Indeed, i even tested with curl inside the container.

Hey @ViktorsBaikers can you try out #35 with the tag "pr-35"

I'm confident this was closed in #35


Support multiple components and microgrids

What's needed?
In the initial version only a combination of one metric, component and microgrid ID each can be requested. The API supports arbitrary lists of microgrid-component IDs and metric IDs. This  functionality should be exposed.
In a first step, multiple metrics for a single component is implemented in https://github.com/frequenz-floss/frequenz-client-reporting-python/pull/26. Multiple components will be addressed separately.
Proposed solution
The case of multiple metrics, components has been considered in the current design already and only needs to be exposed. First steps in this direction are addressed for multiple metrics in https://github.com/frequenz-floss/frequenz-client-reporting-python/pull/26.
Use cases
No response
Alternatives and workarounds
No response
Additional context
The API requests the cross-combination of the elements in the list of microgrid_components and the elements in the list of metrics, which might not provide sufficient control over the combinations (e.g. too many or non-existing). For instance
metrics = [SOC, power]
microgrid_components = [ {MID, CID_meter}, {MID, CID_battery} ]

leads to 4 combinations.
EDIT: For now we focus on exposing the signature as close to the underlying  API as possible and keep the following as potential future enhancements:
Alternatively we could require the user to provide request data in the format
[[mid1, cid1, metric1], [mid2, cid2, metric2], ...]

and potentially have multiple requests whose output needs to be merged.

Updated scope of this PR since multiple metrics are now addressed here: https://github.com/frequenz-floss/frequenz-client-reporting-python/pull/26.

Updated issue description narrowing down the scope.

Closing issue after merging PR #39.


this.unset() does not remove value or property

To reproduce, have a property and a value on a document (query: 'abcd'), change Simple Schema's autoValue for that property to this.unset();, and submit the form. Using meteor mongo find the document and note that the property and value still exist on the document.
query: {
  label: 'Search query',
  type: String,
  optional: true,
  autoValue: function() {
    this.unset();
  }
},

A workaround for the current time is to return an empty string to clear the value, however that leaves the property itself still defined on the document.

You're misunderstanding what unset does. Nothing simple-schema cleaning does has any effect on stored data. You are only manipulating the object while it is being cleaned. So you might be cleaning a document {query: 'foo', a: 2}, which your autoValue would change to {a: 2} because query is unset in the object. Or you might be cleaning a modifier {$set: {query: 'foo', a: 2}}, which your autoValue would change to {$set: {a: 2}}.
In your case your intent seems to be to add $unset to the modifier when cleaning it before an update. So you can do that by returning the pseudo-modifier.
autoValue: function () {
  return {$unset: ''};
}

Which also implicitly calls this.unset().

Thanks for the info!


Is it possible to warn on type synonym declarations like "type Foo = Bool"?

Possible, but sometimes such definitions are useful for documentation. The GHC codebase is absolutely full of them. I'm inclined to think their overuse is an issue, but any one instance is not necessarily problematic.

Sure – I'm talking about a custom .hlint.yaml file, not about adding this as a default hint.
I'm asking because I haven't found a spec for writing hints, and all hints I've seen previously involve expressions, not declarations, so I'm not sure how I would write such a hint on my own.

You can't write custom hints, they are only for expressions, so this hint would have to be built in.

I'd probably accept such a hint in off-by-default configuration.

https://github.com/ndmitchell/hlint/issues/449 would enable this

I'm happy to hack that (ignored by default, would had to be turn on by .hlint.yaml


When adding new Fruit: "bad request"

To replicate:
Launch on Minishift a new CRUD Node Booster
Wait for deployment
Navigate to index.html in the route
Use the form to create a new fruit name and qualtity
Hit "save"
See "bad request" response returned as dialog box in Chrome, for instance

@ALRubinger i'll check it out.   is the database up when you run this command?
is there also anything in the pod log?

I just tried with what is in master,  I get the bad request error, but that is only because i didn't create the database first.
Once i run oc new-app -e POSTGRESQL_USER=luke -ePOSTGRESQL_PASSWORD=secret -ePOSTGRESQL_DATABASE=my_data openshift/postgresql-92-centos7 --name=my-database
then redeploy my app and refresh the page,  everything works


libepoxy: disable glx on darwin

Originally enabled in
950261bb9a4bcc1ae959b76e8ee0f1c52819c304 ('darwin: fix gtk+3 dependencies')
since then many dependencies may have been changed to rely on Cocoa
only. Let's try disabling it by default to avoid the mesa dependency
on darwin, we can always enable on a case-by-case basis for apps that
really use X11.

Motivation for this change
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[x] x86_64-darwin
[ ] aarch64-darwin

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

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

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

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

[x] Fits CONTRIBUTING.md.

If we're possibly going to want to enable this on a case-by-case basis why not make it a boolean package argument?

If we're possibly going to want to enable this on a case-by-case basis why not make it a boolean package argument?

Cherry-picked back to master, this builds for me, macos 10.15, nixos x86_64 & aarch64.
Output on macos still appears to retain a reference to mesa though. Perhaps this is fixed in staging?

Cherry-picked back to master, this builds for me, macos 10.15, nixos x86_64 & aarch64.
Output on macos still appears to retain a reference to mesa though. Perhaps this is fixed in staging?

If we're possibly going to want to enable this on a case-by-case basis why not make it a boolean package argument?

Initially I could not see any package that would use libepoxy directly and that also works on darwin. However, I now realized that gtk2-x11, gtk3-x11, gtk4-x11 would need such a parameter. Perhaps we could add a libepoxy-x11 attribute for that.

If we're possibly going to want to enable this on a case-by-case basis why not make it a boolean package argument?

Initially I could not see any package that would use libepoxy directly and that also works on darwin. However, I now realized that gtk2-x11, gtk3-x11, gtk4-x11 would need such a parameter. Perhaps we could add a libepoxy-x11 attribute for that.

Cherry-picked back to master, this builds for me, macos 10.15, nixos x86_64 & aarch64.

This branch is based off merge base of the current master and staging.

Output on macos still appears to retain a reference to mesa though. Perhaps this is fixed in staging?

Missed a reference in NIX_CFLAGS_COMPILE.

Cherry-picked back to master, this builds for me, macos 10.15, nixos x86_64 & aarch64.

This branch is based off merge base of the current master and staging.

Output on macos still appears to retain a reference to mesa though. Perhaps this is fixed in staging?

Missed a reference in NIX_CFLAGS_COMPILE.


add support for daisyui and other tailwind-based component libraries

bit of a pie in the sky idea, but it would be nice if typewind could parse classes from other tailwind plugins - currently adding daisyui to my plugins breaks typewind's type codegen, resulting in the tw import being typed as unknown

This did work with plugins like tailwindcss-animate and @tailwindcss/typography. I'll take a look at this.

Seems to be working for me @sigmachirality. Did you run npx typewind generate after adding daisyui to the plugin list?

@sigmachirality I can't seem to be able to reproduce this issue. Can you give us a few more details?

I'll look into it again on my end. Thanks for the prompt response!

There was issue with my language server on my end, closing this issue!


Feature : Adding Sorting Algorithm to Search Results

Is your feature request related to a problem? Please describe
When you search for the "SAP-1" project, the results aren't very helpful because they're not sorted effectively. The most popular projects related to "SAP-1" are showing up on the second page, while the first page mainly shows projects with very few views.

Describe the solution you'd like
I suggest there should be an option for the user to search projects with "sort by name", "sort by views" and "sort by stars" options which will lead the user to the best projects with maximum views and stars.
FIgma Design for the issue
https://www.figma.com/file/GU1UXZLb9lEeuQgBcuemtV/Search_bar?type=design&node-id=0-1&mode=design&t=7n2IUOPatwICH7dp-0
Describe alternatives you've considered
We should sort the projects based on the number of views if we don't want to add a dropdown menu.
Additional context
No response
Are you working on this?
No

Good one. @tanmoysrt  Please assign this to me

@tanmoysrt Please assign this issue to me

Duplicate of https://github.com/CircuitVerse/CircuitVerse/issues/4782

You can add but this page's revamp is part of GSoc Project 1, it will be better if you can add this as proof of work in proposal.
Ref - https://github.com/CircuitVerse/CircuitVerse/wiki/GSoC'24-Project-List#project-1---enhancing-circuitverse-user-experience


Add warning about scoped Slot implementation

Thanks @LinusBorg . Can you run prettier to fix the formatting issue?

@eddyerburgh

when i run prettier on the whole repo (yarn format) it changes >200 files.
When I run it on just the docs file (yarn prettier --no-semi --single-quote --write "./docs/api/options") it also changes around 20 other things, mostly turning - into* ` for lists.

No idea why?

@LinusBorg Just a wild guess but maybe https://github.com/vuejs/vue-test-utils/pull/1247 helps here. :thinking:

I tried to rebase and encountered the same problem described above, but did not notice until pushing the commits. So I just made a fresh fork of dev and copied the content over. It's here: #1389.


Adding sweet-error library support across the application

Summary:
Adding of Sweet-error library across the application in order to avoid manual handling of UI error.

@therajanmaurya  I would like to be a part of this task.

@AkshGautam are you gonna do full of it ..

@ivary43 Of course not.It would take a lot of time doing alone and this needs to be done as early as possible but since the server is down there would be no way to verify that the changes made are working as expected.


Remove 0.4.9 deprecations

Description
This removes old code that was deprecated and slated for removal in version 0.4.9

ready @sofroniewn


Independent QA of BUGS code

Input from someone with expertise in BUGS language to assess whether code is appropriate for the task and faithful to the model in STING1 report.

Issues that occur to me:

[ ] Are the hyperpriors on alpha.p redundant? This code was derived from a model in which there was an annual value.
[ ] Is beta3 redundant? I think the two alpha.p parameters make it unnecessary. Perhaps more identifiable if JulDate was centred on zero.
[ ] muZ is doing two different jobs: one as probability of occupancy (i.e. bounded between 0 and 1) and the intensity, which should be unbounded above zero. Need to include a cloglog link somewhere to achieve this.

Since setting up a model in Nimble, I have completely rewritten the code, meaning that some of the issues above disappear. I started really simple then built it up.  At the time of writing I now have an IDM, linked through the phenology of detection. Some issues that need attention/help from others:

[ ] I don't have a cloglog link. I think this is only necessary if I have covariates (i.e. sharing info on the state process, not the observation process). Is that right?
[ ] I would like to add covariates .....
[ ] I'd also like to add that detection in the occupancy part should be dependent on lambda[i]

Closing this issue since the mainly reflect the early stages of development.


Cannot change staple color

Abstract: can't change staple color on  https://scadnano.org/dev/
How to reproduce:

Select any origami example on  https://scadnano.org/dev/
Right Click on a staple then "set color" then change the color then "OK"
The color doesnt change

I am using Chrome 1.0.4044.138

This is strange. I get this same error on https://scadnano.org/dev/, but I cannot reproduce it locally.
When I do run locally, I see the following warning in Dev Tools, which might be related:

That warning also appears on https://scadnano.org/dev/, and here is the exception that gets thrown when you try to change the color. As you can see, it is occurring within the react-color component that we use.

I have a fix ready. I'm wondering if we should consider this as a hot fix and directly commit fix to master, updating the version to something like 0.12.2. I anticipate that there won't be any issues merging since I only need to edit strand_color_picker.dart This way, the color picker of version 0.12 will be fix before we upgrade to 0.13.0

I have a fix ready. I'm wondering if we should consider this as a hot fix and directly commit fix to master (this is broken not only in dev but also master), updating the version to something like 0.12.2. I anticipate that there won't be any issues merging since I only need to edit strand_color_picker.dart This way, the color picker of version 0.12 will be fix before we upgrade to 0.13.0

Is the bug appearing in master? I don't think it's there, so if not, let's leave master alone for now.

I can't use color picker on scadnano.org so I think master has this issue also

I can't use color picker on scadnano.org so I think master has this issue also

Ah, you're right.

But anyway, we're going to merge dev into master soon, so I don't think this is worth rushing.

Was thinking we might want a functioning color picker in v0.12 since this will be permanently deployed.

Was thinking we might want a functioning color picker in v0.12 since this will be permanently deployed.

Ah, I see. Sure, go ahead.


i18n error: path "errors.models.posts.postNotFound" was not found

I'm getting the following error when adding and deleting content
Technical details:

Ghost Version: 1.21.6
Node Version: 6.9
Browser/OS: Chrome
Database: SQLite

{
   "name":"Log",
   "hostname":"Site",
   "pid":25551,
   "level":50,
   "err":{
      "id":"b76e1d90-2c6b-11e8-8595-99a5c9cf6e1c",
      "domain":"https://mertcangokgoz.com/",
      "code":null,
      "name":"IncorrectUsageError",
      "statusCode":400,
      "level":"critical",
      "message":"i18n error: path \"errors.models.posts.postNotFound\" was not found",
      "stack":"IncorrectUsageError: i18n error: path \"errors.models.posts.postNotFound\" was not found\n    at new IncorrectUsageError (/var/www/ghost/versions/1.21.6/node_modules/ghost-ignition/lib/errors/index.js:79:23)\n    at Object.findString (/var/www/ghost/versions/1.21.6/core/server/lib/common/i18n.js:152:31)\n    at Object.t (/var/www/ghost/versions/1.21.6/core/server/lib/common/i18n.js:66:23)\n    at Child.then (/var/www/ghost/versions/1.21.6/core/server/models/post.js:690:50)\n    at Child.tryCatcher (/var/www/ghost/versions/1.21.6/node_modules/bluebird/js/release/util.js:16:23)\n    at Promise._settlePromiseFromHandler (/var/www/ghost/versions/1.21.6/node_modules/bluebird/js/release/promise.js:512:31)\n    at Promise._settlePromise (/var/www/ghost/versions/1.21.6/node_modules/bluebird/js/release/promise.js:569:18)\n    at Promise._settlePromise0 (/var/www/ghost/versions/1.21.6/node_modules/bluebird/js/release/promise.js:614:10)\n    at Promise._settlePromises (/var/www/ghost/versions/1.21.6/node_modules/bluebird/js/release/promise.js:693:18)\n    at Async._drainQueue (/var/www/ghost/versions/1.21.6/node_modules/bluebird/js/release/async.js:133:16)\n    at Async._drainQueues (/var/www/ghost/versions/1.21.6/node_modules/bluebird/js/release/async.js:143:10)\n    at Immediate.Async.drainQueues (/var/www/ghost/versions/1.21.6/node_modules/bluebird/js/release/async.js:17:14)\n    at runCallback (timers.js:794:20)\n    at tryOnImmediate (timers.js:752:5)\n    at processImmediate [as _immediateCallback] (timers.js:729:5)"
   },
   "msg":"i18n error: path \"errors.models.posts.postNotFound\" was not found",
   "time":"2018-03-20T18:22:58.547Z",
   "v":0
}

Hey!
Thanks for your report.

errors.models.posts.postNotFound

Indeed the key does not exist, it must be errors.models.post.postNotFound.
But the i18n library is written in a way that Ghost won't fail or respond with an errorl, it just logs the error and falls back to a general error message -> An error occurred.
I can't reproduce what you are reporting. The error is only thrown if you are trying to edit an existing post which does not exist in the database. Are using a special setup or a custom client?

I did not do a special installation, re-install with this error. met again with the same error.

@MertcanGokgoz Can you pls swing by our slack community? It's easier to figure this out in a chat. We can leave this issue open till we know what causes your problem.

@kirrg001 I tried node version 8.9, so maybe it will not give an error. but it still gives an error, Nothing changed
note: im coming slack

@kirrg001 I threw together something to look for other translation strings that don't exist:
Assumed to be run from the root of the repo, it does take a little while - maybe 30secs:
grep -rhoE --include=\*.js "i18n\.t\('([^']+)'" . | sed -e "s/i18n.t(//" | sed -e "s/'//g" | xargs -L1 -I % sh -c "cat core/server/translations/en.json | jq 'if (.% | length) > 0 then empty else \".%\" end'"

Current output:
jq: error: syntax error, unexpected '|', expecting FORMAT or QQSTRING_START (Unix shell quoting issues?) at <top-level>, line 1:
if (.errors.api. | length) > 0 then empty else ".errors.api." end
jq: 1 compile error
jq: error: syntax error, unexpected '|', expecting FORMAT or QQSTRING_START (Unix shell quoting issues?) at <top-level>, line 1:
if (.errors.api. | length) > 0 then empty else ".errors.api." end
jq: 1 compile error
".errors.api.themes.invalidRequest"
jq: error: syntax error, unexpected '|', expecting FORMAT or QQSTRING_START (Unix shell quoting issues?) at <top-level>, line 1:
if (.notices.data.validation.index.validationFailedTypes. | length) > 0 then empty else ".notices.data.validation.index.validationFailedTypes." end
jq: 1 compile error
".warnings.helpers.get.mustBeCalledAsBlock"

The errors are from places where we use concatenation, and the key ends with a .  E.g. i18n.t('.errors.api.' + ..... - you can ignore the errors, but it at least indicates the items we can't check this way.
The 2 keys that are output on their own are missing keys:

".errors.api.themes.invalidRequest"
".warnings.helpers.get.mustBeCalledAsBlock"

@ErisDS Cool thanks 👍

...because the i18n library falls back to a valid key.

I will add them next Monday, it won't break anything.

I will add them next Monday, it won't break anything.

👍I know, just thought it would be useful to have a command to run to check this. Maybe wire it up as a grunt/yarn command 😬

I know, just thought it would be useful to have a command to run to check this

Definitely. You are the queen of shell piping 🚬

@MertcanGokgoz Did you swing by our slack channel?

@kirrg001  I resolved the error, downgraded the nodejs(version 6.8)

@MertcanGokgoz You downgraded from 6.9 to 6.8?

@kirrg001 unfortunately yes, I have not been successful in latest versions

That is weird. I'll do some more testing on Monday. If i can't reproduce, i have to close this issue. Thanks for coming back :) Very helpful

@MertcanGokgoz I wasn't able to reproduce. Do you have any more information? Steps to reproduce...?

Hi @kirrg001
explain the situation step by step

created a virtual machine on Microsoft Azure
I got the backups on the old machine
installed ghost-cli and nodejs 6.13.1 on ubuntu 16 LTS
created a ghost user
I've completed the upload by document
Set up my backup with ghost admin (exported data v1.21.5, imported to 1.21.6)
The stories area started to 500 error and I could not update and delete it.

@MertcanGokgoz How did you install Ghost on Ubuntu? Did you follow our installation guide https://docs.ghost.org/docs/install?

@kirrg001
Yes, I used the official document.

Pushed two broken i18n keys, see https://github.com/TryGhost/Ghost/commit/e43bdad8184700752ed1c042bf5a81bc53d7f772.
Discovered by @ErisDS - thanks!


Error: XML document not well formed:

I just compiled tilemill with the latest carto
I think there is a bug with the new textsymbolizer
I get an error:
Error: XML document not well formed:
the resulting xml looks like this on the labels:
<TextSymbolizer size="12" fontset-name="fontset-0" fill="#646464" placement="interior" >[name]</@sans>

the /@sans should not be there

Fixed in 29c96f6810a0bc013b0f56d26b34fe8c4a54eb61


python310Packages.pynamodb: 5.3.4 -> 5.3.5

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.pynamodb is: Interface for Amazon’s DynamoDB
meta.homepage for python310Packages.pynamodb is: http://jlafon.io/pynamodb.html
meta.changelog for python310Packages.pynamodb is: https://github.com/pynamodb/PynamoDB/releases/tag/5.3.5
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 5.3.5 with grep in /nix/store/3c1cpfk794hbyd0nciy6k5adyj639wkj-python3.10-pynamodb-5.3.5
found 5.3.5 in filename of file in /nix/store/3c1cpfk794hbyd0nciy6k5adyj639wkj-python3.10-pynamodb-5.3.5

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath
python310Packages.pynamodb
python311Packages.pynamodb

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/3c1cpfk794hbyd0nciy6k5adyj639wkj-python3.10-pynamodb-5.3.5 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python310Packages.pynamodb https://github.com/r-ryantm/nixpkgs/archive/0d31ee45ccf9c1b6dc5587ca94a9f031ec57bbf2.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/3c1cpfk794hbyd0nciy6k5adyj639wkj-python3.10-pynamodb-5.3.5
ls -la /nix/store/3c1cpfk794hbyd0nciy6k5adyj639wkj-python3.10-pynamodb-5.3.5/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

2 packages built:

python310Packages.pynamodb
python311Packages.pynamodb

Maintainer pings

Result of nixpkgs-review pr 213495 run on aarch64-darwin 1

2 packages built:

python310Packages.pynamodb
python311Packages.pynamodb


Add subtitle to ApsAlert

Tested for APNS. Works.

@dsanghan why was this closed?

I closed the issue and opened the PR

@dsanghan Can you fix the linter error detected by Travis (line-too-long)? Also please update the tests.

Closing in favor of #239


Create two namespaces on odh-cl2

Can I please get a namespace created on cl2 to run some secrets experiments?
Namespace name: vault-dev

@caldeirav - FYI

Reassigning to @ryanaslett and adding @redmikhail to provide any support required

It seems that this task is more suited for cluster 1 , resulting solution can be subsequently propagated to cluster 2

Namespaces have been created. Thanks. Closing this issue now.


chore(papyrus_node): use printing util in papyrus node config test

crates/papyrus_config/src/lib.rs line 73 at r1 (raw file):

pub mod loading;
pub mod presentation;
#[cfg(test)]

I do not understand why I need to delete this for the import to work...
Code quote:
#[cfg(test)]

crates/papyrus_config/src/lib.rs line 73 at r1 (raw file):
Previously, Itay-Tsabary-Starkware wrote…
I can take a deeper look if needed, please lmk

No longer relevant. test_utils is no longer a part of this lib.