Could not find tech.annexflow.compose-constraintlayout-compose-multiplatform-0.3.1-iosMain-nK9X2g.klib

When i build project, i get next error:
e: Could not find "/Users/timur/AndroidStudioProjects/App/shared/build/kotlinTransformedMetadataLibraries/iosMain/tech.annexflow.compose-constraintlayout-compose-multiplatform-0.3.1-iosMain-nK9X2g.klib" in [/Users/timur/AndroidStudioProjects/App, /Users/timur/.konan/klib, /Users/timur/.konan/kotlin-native-prebuilt-macos-aarch64-1.9.20/klib/common, /Users/timur/.konan/kotlin-native-prebuilt-macos-aarch64-1.9.20/klib/platform/ios_x64]
Execution failed for task ':shared:compileIosMainKotlinMetadata'.
My build.gradle for shared:
val commonMain by getting {
            dependencies {
                implementation("tech.annexflow.compose:constraintlayout-compose-multiplatform:0.3.1")
                implementation(compose.runtime)
                implementation(compose.foundation)
                implementation(compose.material)
                @OptIn(org.jetbrains.compose.ExperimentalComposeLibrary::class)
                implementation(compose.components.resources)

            }
        }

val iosMain by creating {
            dependsOn(commonMain)
            iosX64Main.dependsOn(this)
            iosArm64Main.dependsOn(this)
            iosSimulatorArm64Main.dependsOn(this)
            dependencies {
            }
        }

And i can run Android and Desktop App. Problem only with build and run on iOs

Bug fixed


Playing on onboard RPI2 instead of Sabre A9023 DAC

Hi,
I have RPI2 running latest RuneAudio beta. All working good, if I stream music using RuneAudio, its play from my Sabre A9023 DAC. But if I try Spotify connect its play from onboard RPI2 audio card and DAC is silent. Dont know how to fix it, pls help me and sorry for my really bad english. Thx.
Kemo

I am using running an RPI3 with an outboard USB DAC. I was able to set the default output to usb by creating the file /etc/asound.conf containing these lines:
pcm.!default {
        type hw
        card 1
}

ctl.!default {
        type hw
        card 1
}

You can also try adding the parameter --device 1 to your spotify-connect-web.sh launch command.
This package has been working extremely reliably for me, kudos to the developers.

Great! Parametr --device 1 work for me. Thanks for help, and i want thanks a developers for their work. Its sound great on Sabre A9023. Thanks.

I'm gonna close this issue since it seems like you got it working
Feel free to re-open if you need to


[feature] Volume rendering scissors cropping

One approach is to run a double pass volume rendering that will allow us to do some volume rendering on irregular shapes.
However there are limitation with "convex shapes" and any advice on the right approach would be very much appreciated!
Current experiments: https://drive.google.com/file/d/1-Xxs7lJ3GOYsoqckbzsyKrsjMJ1m0jA6/view

Another approach is to edit the voxel values then push the new voxels back to the shader. Will not be real time but 2-3s delay may be OK.

The most robust (not fastest) approach seem to be the following:
1- Draw ROI to be cropped
2- If voxels of the data belong to ROI, change intensity to "background" color.
// we assume the background will be transparent
3- Perform regular volume rendering
Other faster approaches (double pass + irregular mesh shape) seem to have more limitations but may be fine for basic use cases

@NicolasRannou Thank you, it seems very interesting.
Do you guys already have some piece of code to play with it?

Let me check if there is something around - however be warned that is pure testing/investigation code :)

Some quick notes:
The approach there was to modify the shape of the base object that is volume renderered, then perform a 2 pass volume rendering on this new shape.
We use ThreeJS helpers to generate a convex geometry that is then "cropped out" of the stack with the "three-csg" library.
As you will see it works well on some limited cases that may not be enough.
My idea was that a the we can not just get away with using "CSG" + "double pass" VR and that a better approach is to:
1- generate a geometry we want to "crop out" - (current approach with ray casting + large bbox seems ok, need to generate concave + convex shapes though)
2- for all voxels in our stack, test if it belong to the new geometry or not.
3- if it belongs to the geometry, then we want to exclude it and we change its value to "background" color?
4- Pack new texture with updated voxel values and push it to shaders
Lot of questions to be answered, happy to use this thread for discussion / work on it!

yarn example vr_crop


nodePackages.pnpm: 6.32.6 -> 6.32.7

Description of changes
https://github.com/pnpm/pnpm/releases/tag/v6.32.7
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] 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

[ ] Fits CONTRIBUTING.md.

This has been merged in a separate commit.


Email app - Integrate Push wallet connect

Hello @riyanshu-patro  A support ticket has been opened for you. Kindly Talk to Support on the Live support page so that your issue can be looked into. CLICK HERE


disable libvtv for gcc/musl cross compiler

since approximately gcc 4.9, gcc has libvtv, whose use flag is enabled
by default in gentoo. it doesn't work with musl, because of a lack of
execinfo.h. set USE=-vtv to fix it.
fixes #45

@edannenberg thanks for the neat project, i made my own gentoo overlay just for it ;-)


Simulator API updates

Updating simulator API

Hi @avneet006 Could you briefly explain what is the main purpose of this PR?

Hello Sebastian,
Hope you are doing well. We have cancelled this PR since merging PR 53 created some merge conflicts.
We will create a new PR once we have implemented the latest codes.
Thanks and Regards
Avneet
Data Scientist,
NEC Corporation India
[NEC_new_signature]
From: Andres Sebastian Cespedes cubides @.>
Sent: 16 May 2024 18:02
To: JBjoernskov/Twin4Build @.>
Cc: Avneet @.>; Mention @.>
Subject: Re: [JBjoernskov/Twin4Build] Simulator API updates (PR #52)
External Message: Please be cautious when opening links or attachments in email
Hi @avneet006https://github.com/avneet006 Could you briefly explain what is the main purpose of this PR?

Reply to this email directly, view it on GitHubhttps://github.com/JBjoernskov/Twin4Build/pull/52#issuecomment-2115128712, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A5ROCNUJHFW7NFWSOKPHQI3ZCSRNVAVCNFSM6AAAAABHMHV4X2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJVGEZDQNZRGI.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only.
It shall not attach any liability on the originator or NEC Corporation India Private Limited or its affiliates.
Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of NEC Corporation India Private Limited or its affiliates.
Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited.
If you have received this email in error please delete it and notify the sender immediately.


QuestSaberPatch not updating correctly

Not sure where to put this but on sidequest when I redownload patcher, it doesn't change anything, like it doesn't update.

This sounds like something for the SideQuest Discord, maybe include some info about how you know that it doesn't seem to update QuestSaberPatch.

It doesn't have playlists and no custom sabers
I even restarted

Oh for that you need a new version of SideQuest and a new version of the patcher. First update SideQuest until your UI has playlists, then redownload the patcher.


Populate "Programmed" condition for managed objects

Is there an existing issue for this?

[X] I have searched the existing issues

Problem Statement
Recently, we improved the visibility of translation failures by creating warning Kubernetes events when they occur (see https://github.com/Kong/kubernetes-ingress-controller/issues/3097). To take it further, we'd like to introduce an additional way to tell whether a given managed object was successfully configured in the Gateway by introducing a Programmed status to our CRDs and built-in managed objects. That would allow users to programmatically wait for resources to be configured in the Gateway.
Proposed Solution
Add Programmed condition to every object KIC manages. That may require adding status.conditions to Kong CRDs.
Following logic should be followed when processing Kubernetes objects in KIC:

When an object gets created, it gets the Programmed condition assigned with state=Unknown and reason=Unknown
Once the object gets successfully sent to the data plane, it turns the state into True and reason into ConfiguredInGateway
In case of a translation failure, the state is set to False, with a reason=TranslationError

A condition value can be used to pretty print a current state using kubebuilder’s printcolumn annotations providing the visibility for the user kubectl get-ting the affected resource.
Additional information
The condition's name and meaning are borrowed from the upstream GEP:

The Programmed condition is being added to replicate the functionality that the Ready condition currently indicates, namely that all the resources in the set are valid enough to produce some data plane configuration, and that configuration has been sent to the data plane, and should be ready soon.
It is a positive-polarity summary condition, and so should always be present on the resource. It should be set to Unknown if the implementation performs updates to the status before it has all the information it needs to be able to determine if the condition is true.

POC: https://github.com/Kong/kubernetes-ingress-controller/pull/3087
Suggested split of work

[ ] Modify Set so it handles (Unknown, Configured and FailedToConfigure) states of objects (similarly to POC), align existing r.DataplaneClient.KubernetesObjectIsConfigured calls in controllers
[ ] Define constants for the new condition (name, states, reasons)
[ ] Extend CRDs with Status.Conditions, make sure Set is populated with status for them, make sure controllers set the condition:

[ ] KongPlugin
[ ] KongClusterPlugin
[ ] KongConsumer
[ ] TCPIngress
[ ] UDPIngress

[ ] Make sure Set is populated with status for upstream Kubernetes objects and handle it properly in their controllers by setting the condition

[ ] Gateway
[ ] HTTPRoute
[ ] TLSRoute
[ ] TCPRoute
[ ] UDPRoute
[ ] Ingress
[ ] knative.Ingress

Acceptance Criteria

[ ] All KIC-managed Kubernetes objects have Status.Conditions populated with the new Programmed condition
[ ] Integration tests verifying status propagation exist for every object
[ ] docs.konghq.com is updated to reflect the changes

Not all managed objects have status.condition field. For the metioned objects, the following objects does not have status field:

KongPlugin
KongClusterPlugin
KongConsumer
The following objects have status field, but no status.conditions field:
Ingress
TCPIngress
UDPIngress
The following objects have status.conditions field:
Gateway
HTTPRoute
TCPRoute
TLSRoute
UDPRoute
GRPCRoute (not supported now)
knative.Ingress
So the "Programmed" condition could only be applied to objects having the status.conditions field.

Broken into two sub-issues:

#3343 for resources in gateway APIs
#3344 for other CRDs

I adjusted the suggested split of work and acceptance criteria to the above split @randmonkey done. This issue is going to be for tracking the initial efforts to make the Set ready to handle configuration errors.


Error when editing images above 2k

It seems to error out on larger images when editing the original size.
3840x2880
3648x5472
2299x3065
I've attached the error outputs:
err2.txt
err1.txt
I'm on CUDA 11.1 (I've tried 11.3/11.5 too) and have also tried torch 1.9-1.10, with the same errors occurring on my
RTX 3080 GPU. I'm using the Docker setup but with the torch replaced with the cuda 11.1+ version. Selecting 2k or 1080p usually results in it working properly (I believe sometimes 2k will throw an error, but then will work)

I use torch 1.8 to convert torchscript model, maybe you can try convert it using 1.9 or 1.10. https://github.com/saic-mdal/lama/pull/63

I use torch 1.8 to convert torchscript model, maybe you can try convert it using 1.9 or 1.10. saic-mdal/lama#63

Thanks for the tip, I used your script, had to modify it a bit to run,
image = torch.rand(1, 3, 120, 120).to(device)
mask = torch.rand(1, 1, 120, 120).to(device)
output = jit_model_wrapper(image, mask)

and had an output successfully generated on 1.10 with "diff: 0.0".
Unfortunately with this new model installed, the same error occurs. Would there be anything else that I could try?

You seems to be running into memory issues (RAM, not GPU). I get the same error on some servers with low memory. Please not than images higher than 2k will use up or even more than 32GB of RAM.

I mainly noticed these errors on linux systems. Windows seems to try and free as much as memory as possible to avoid a crash.

Why your image take up so much memory?
# rgb image
np_img = np.ones((2000,2000,3), dtype=np.uint8)
np_img.nbytes / 1024 / 1024 # ~= 11MB

That's a good question. All I know is that LaMa uses a lot of memory with big images on my setup, no matter the system.
I tried it on 3 different OS (Windows, Debian, Ubuntu), with various configurations and it has always been using a lot of memory with high-quality input (starting from 2k).

Why your image take up so much memory?
# rgb image
np_img = np.ones((2000,2000,3), dtype=np.uint8)
np_img.nbytes / 1024 / 1024 # ~= 11MB

lazy coding

I can't reproduce in my environment(RTX3090 + pytorch1.8.2)
This is the result of benchmark script

Add crop mode for very large image, this helps with memory issues.


Add build workflow to Github Actions

Issue #106. Builds on Windows and Linux. Caches Linux dependencies. Runs on every push and PR.
[Sorry, my previous PR failed the pipeline because I had apparently missed to pull in the latest changes from main, and there had been some changes on Linux.]
Note that it takes some time to build it on Windows. Not sure if the parallelization make -j4 really took effect on Windows, or if it's just slow in general. Linux build is significantly faster since it doesn't need to build Assimp, which takes the majority of the time.
An addition to this could be to upload tarballs of the binary + other necessary files (Resources/?).
I was originally planning on doing this last week, but got stuck on getting it to build on Linux then. I realize someone else was assigned to this issue, but if they still do it you could give them hacktoberfest-accepted label even if you don't merge it (though I don't see any fork that they could be working on).

Awesome! And thanks for editing the non-linux-compilant code in Entity.h, looks like a mistake by me haha 😄


Timeout waiting to connect

I want to render this value, but I don't see any instructions for this in the documentation.
try to get it in the following way, but an error is reported.
handle_provide_parameter.c
...
switch (context->next_param) {
        case MIN_AMOUNT_RECEIVED:
            copy_parameter(context->amount_pay,
                            msg->pluginSharedRO->txContent->value.value,
                            sizeof(context->amount_pay));
            copy_parameter(context->amount_received,
                           msg->parameter,
                           sizeof(context->amount_received));
            context->next_param = UNEXPECTED_PARAMETER;
            break;
        // ...
        default:
            PRINTF("Param not supported: %d\n", context->next_param);
            msg->result = ETH_PLUGIN_RESULT_ERROR;
            break;
}

handle_query_contract_ui.c
// ...
amountToString(context->amount_pay, sizeof(context->amount_pay), decimals, ticker, msg->msg, msg->msgLength);
// ...

xxx.test.js
// ...
unsignedTx.value = parseEther("0.0009");
// ...

This value is always displayed

Thanks Reply.
I shouldn't use sizeof.
used msg->pluginSharedRO->txContent->value.length to get the length, which solved the error.

Glad to hear that! Sorry I thought it was always displayed but actually no.


Return custom message for specific error codes in NUnit/NUnit3 tools

Fixes #517.
Uses the new custom error code functionality in #1031 for the NUnit tools. Have been eyeing this up for a while, however now the frameworks already been discussed and put in, it seemed too simple to not to do.
I've never used XUnit before - is that Theory/InlineData thing the correct approach to doing this sort of test?
For reference:

NUnit2 exit codes
NUnit3 exit codes

@ChrisMaddock thanks for making this contribution!
As you will have noticed, our CLA bot has identified that you need to sign our CLA, but it helpfully hasn't told you where that is.  You can find it here:
https://cla2.dotnetfoundation.org/
Are you in a position to sign it for us? Thanks!

@ChrisMaddock, Thanks for signing the contribution license agreement so quickly! Actual humans will now validate the agreement and then evaluate the PR.
Thanks, DNFBOT;

Thanks @gep13 - was wondering what to do about that! Done!

@ChrisMaddock perfect!  We are looking into what is causing the issue.  Now that you have signed it though, you won't need to sign it again :smile:

@ChrisMaddock LGTM! Thank you for your contribution!
I have merged the changes here https://github.com/cake-build/cake/commit/a509518b0dcd2a2553b262d7e8f1db98ae244395 to save you doing a rebase.
GitHub won't follow what I did, so I will close this PR, but your commit is still intact.  Thanks again!

Great, thanks!


Move deprecated_focus* events to the new events api

This task is automatically imported from the old Task Issue Board and it was originally created by Wojciech Daniło.
Original issue is here.

The event endpoints generated by ensogl::define_endpoints/2 macros were recently prefixed with the deprecated_ prefix. They should be replaced by the new mechanism built into display objects.

EnsoGL is removed.


Game Title
God of War
Game Website
https://store.steampowered.com/app/1593500/God_of_War/
Anti-Cheat Software
VAC
Status of the Anti-Cheat
⭐ Supported
Proof of Mention
N/A

Can someone confirm that it actually uses it? GoW doesn't have any multiplayer capabilities, so it is weird.

If it happens that God of War does indeed have anti-cheat for whatever reason, please re-open this. At the moment this does not seem to be the case, so I will close this for now.


Re-upload of media files with umlauts not possible

If a media file, e.g. an image for a product, is uploaded and the name contains umlauts, the image is saved without the umlaut in the file name.
If you now try to upload a new image with the same name, Shopware recognizes that there is an associated image, but since the image is saved under a different name (the one without the umlaut), it is not displayed and cannot be replaced.

[public] Automated response: This issue is linked to the internal issue https://shopware.atlassian.net/browse/NEXT-36753.
[created from NEXT-36753, comment 486646]


Update README.md

Adding my name and my Githube account
Related issue

What changes does this PR do?
Screenshots (If any)
Questions

updte README.md file

closing due to inactivity. feel free to reopen


got a compile-time error when cmpile the spark-streamingsql-master

Hi,I have a question when compile the spark-streamingsql-master using the command sbt under spark-streamingsql-master.
The following is the error stack:
[error] /opt/xcdong/spark-streamingsql-master/src/main/scala/org/apache/spark/sql/streaming/SchemaDStream.scala:64: not found: type CreateTableAsSelect
[error] case : InsertIntoTable | _: CreateTableAsSelect[] | _: WriteToFile =>
[error] ^
[error] /opt/xcdong/spark-streamingsql-master/src/main/scala/org/apache/spark/sql/streaming/StreamSQLContext.scala:63: type mismatch;
[error] found : org.apache.spark.sql.types.StructType
[error] required: Seq[org.apache.spark.sql.types.DataType]
[error] val rowStream = stream.transform(rdd => RDDConversions.productToRowRdd(rdd, schema))
[error] ^
[error] /opt/xcdong/spark-streamingsql-master/src/main/scala/org/apache/spark/sql/streaming/StreamSQLParser.scala:49: not enough arguments for method apply: (input: String, exceptionOnError: Boolean)Option[org.apache.spark.sql.catalyst.plans.logical.LogicalPlan] in class StreamSQLParser.
[error] Unspecified value parameter exceptionOnError.
[error] Some(apply(input))
[error] ^
[error] three errors found
error Compilation failed
[error] Total time: 6 s, completed Dec 21, 2015 4:49:07 AM
What's wrong with it? ^_^
Thanks.

I've seen this error before because of spark version. What version of Spark are you using, and what version of StreamingSQL here?

This error really is due to spark version.I've compiled the package for spark 1.4.1 used in my cluster.
Thanks.^_^

So I'm closing this one, thanks!


EnchantmentData translation error

https://gist.github.com/connorhartley/23b3a362bea664c3a764577c9e43d951

I don't believe this should be an issue still, if it is, please reopen.


Kubernetes-Mesos v0.7.1-v1.1.3

@s-urbaniak: Would you mind explaining what we are trying achieve with this pull request?
Thanks

@imesh This is a work-in-progress PR for our upcoming k8s release candidate. We're testing it right now so it is not ready to merge yet.

lgtm

Thanks @s-urbaniak!


npx @react-native-community/cli@latest init <project_name> Missing yarn.lock file, prevent yarn install to run automatically

Description
npx @react-native-community/cli@latest init <project_name> Missing yarn.lock file, prevent yarn install to run automatically, breaking the project init workflow and prevent user to yarn install afterwards, unless the yarn.lock file been added.
Steps to reproduce

run npx @react-native-community/cli@latest init xxxx <- (any project name)
the terminal give out the error automatically
no yarn.lock file which cannot using default yarn to init the project, nor yarn install inside the directory

React Native Version
0.75.4
Affected Platforms
Other (please specify)
Output of npx react-native info
System:
  OS: macOS 13.6.3
  CPU: (20) arm64 Apple M1 Ultra
  Memory: 18.27 GB / 64.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 20.18.0
    path: /opt/homebrew/opt/node@20/bin/node
  Yarn:
    version: 3.6.4
    path: /opt/homebrew/bin/yarn
  npm:
    version: 10.8.2
    path: /opt/homebrew/opt/node@20/bin/npm
  Watchman:
    version: 2<IP_ADDRESS>
    path: /opt/homebrew/bin/watchman
Managers:
  CocoaPods:
    version: 1.15.2
    path: /opt/homebrew/bin/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 23.2
      - iOS 17.2
      - macOS 14.2
      - tvOS 17.2
      - visionOS 1.0
      - watchOS 10.2
  Android SDK: Not Found
IDEs:
  Android Studio: 2024.1 AI-241.18034.62.2411.12169540
  Xcode:
    version: 15.2/15C500b
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 18.0.2
    path: /usr/bin/javac
  Ruby:
    version: 3.3.5
    path: /opt/homebrew/opt/ruby/bin/ruby
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 18.3.1
    wanted: 18.3.1
  react-native:
    installed: 0.75.4
    wanted: 0.75.4
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: false
iOS:
  hermesEnabled: true
  newArchEnabled: false

Stacktrace or Logs
(base) ➜  Git npx @react-native-community/cli@latest init DemoProject

               ######                ######
             ###     ####        ####     ###
            ##          ###    ###          ##
            ##             ####             ##
            ##             ####             ##
            ##           ##    ##           ##
            ##         ###      ###         ##
             ##  ########################  ##
          ######    ###            ###    ######
      ###     ##    ##              ##    ##     ###
   ###         ## ###      ####      ### ##         ###
  ##           ####      ########      ####           ##
 ##             ###     ##########     ###             ##
  ##           ####      ########      ####           ##
   ###         ## ###      ####      ### ##         ###
      ###     ##    ##              ##    ##     ###
          ######    ###            ###    ######
             ##  ########################  ##
            ##         ###      ###         ##
            ##           ##    ##           ##
            ##             ####             ##
            ##             ####             ##
            ##          ###    ###          ##
             ###     ####        ####     ###
               ######                ######

              Welcome to React Native 0.75.4!
                 Learn once, write anywhere

✔ Downloading template
✔ Copying template
✔ Processing template
⠸ Installing dependencies

error An unexpected error occurred: Command failed with exit code 1: yarn install
Usage Error: The nearest package directory (/Users/username/Git/DemoProject) doesn't seem to be part of the project declared in /Users/username.

- If /Users/username isn't intended to be a project, remove any yarn.lock and/or package.json file there.
- If /Users/username is intended to be a project, it might be that you forgot to list Git/DemoProject in its workspace configuration.
- Finally, if /Users/username is fine and you intend Git/DemoProject to be treated as a completely separate project (not even a workspace), create an empty yarn.lock file in it.

$ yarn install [--json] [--immutable] [--immutable-cache] [--check-cache] [--inline-builds] [--mode #0].

(base) ➜  Git cd DemoProject
(base) ➜  DemoProject yarn i
Usage Error: The nearest package directory (/Users/username/Git/DemoProject) doesn't seem to be part of the project declared in /Users/username.

- If /Users/username isn't intended to be a project, remove any yarn.lock and/or package.json file there.
- If /Users/username is intended to be a project, it might be that you forgot to list Git/DemoProject in its workspace configuration.
- Finally, if /Users/username is fine and you intend Git/DemoProject to be treated as a completely separate project (not even a workspace), create an empty yarn.lock file in it.

$ yarn run [--inspect] [--inspect-brk] [-T,--top-level] [-B,--binaries-only] <scriptName> ...

Reproducer
https://github.com/react-native-community/reproducer-react-native
Screenshots and Videos
you get the error when you npx init the project.

@tonyjohnvan I just tried as you said. npx @react-native-community/cli@latest init ReproApp.
It's working

One thing which you can check to make things work:

Check for yarn.lock and package.json in /Users/username
If you have a yarn.lock or package.json file in /Users/username, yarn might be treating it as the workspace root.
Remove any yarn.lock or package.json files from /Users/username if they are not intended to manage packages.
Re run npx @react-native-community/cli@latest init <projectName> command.

Closing as we cannot reproduce as per @shubhamguptadream11 comment

Check for yarn.lock and package.json in /Users/username
If you have a yarn.lock or package.json file in /Users/username, yarn might be treating it as the workspace root.
Remove any yarn.lock or package.json files from /Users/username if they are not intended to manage packages.
Re run npx @react-native-community/cli@latest init  command.

Those tips are really valid and could help you solve your problem @tonyjohnvan
You can also see futher support in the Community CLI repo here:
https://github.com/react-native-community/cli/issues


Testing events that fire multiple times

I'm running into an issue with vows for events that fire multiple times. According to @indexzero's comment in #79, firing callbacks multiple times should be possible, so hopefully I'm correct in thinking firing multiple events should also. I'd like to know whether the behaviour I'm seeing is expected, a bug, or if I'm going about it the wrong way.
Basically I'm doing some testing of hook.io hooks, using the new event support from #109/#145, and in some cases I'm testing events that need to fire multiple times, and I have to verify they fired the correct number of times. So, I use a macro to generate a vow for the event that closes over a counter which is incremented each time the vow fires, and another vow that later on checks the counter. So far so good.
What happens is that the batch.honored counter is incremented each time a duplicate event is fired, and so sometimes in tryEnd (in lib/vows/suite.js) this condition fails:
if (batch.honored + batch.broken + batch.errored + batch.pending === batch.total &&
    batch.remaining === 0) {

because there were more vows honored than batch.total (which is incremented when addVow is called).
The result is that the batch, while passing, hangs indefinitely.
I was able to work around this by changing the first === to >= and moving the tally,
Object.keys(batch).forEach(function (k) {
  (k in batch.suite.results) && (batch.suite.results[k] += batch[k]);
});

down into finish().
This didn't break my own tests or the Vows tests, but, I'm not sure what other consequences it might have. It might be better instead to change the way addVow works so that batch.total gets set correctly when dealing with events that fire multiple times or so that batch.honored is incremented only once per vow, regardless of how many times it's executed.
If this behaviour is supposed to work I can put together a failing test.

A failing test and, I think, a better fix submitted in #193.


Final dataset configuration for v0.2

Added configuration for Twitter MPI graph and added missing metadata for LDBC graphs.

Refer to this link for build results (access rights to CI server needed):
http://jenkins.tribler.org//job/Graphalytics_pull_request_tester/35/Failed Tests: 1nl.tudelft.graphalytics:graphalytics-platforms-graphlab: 1nl.tudelft.graphalytics.graphlab.cd.CommunityDetectionTest.testCDUndirected
Test FAILed.


Stracktraces obfscuated despite mapping files being uploaded

Thanks for taking the time for reporting an issue!
Describe what happened
We're using this plugin to upload mapping files to de-obfsucate our stacktraces. I can validate that these mapping files were successfully uploaded via gradle output and when I view the RUM Debug Symbols page, but our traces are still garbled.
Steps to reproduce the issue:
We build a release application, release it, and expect to see traces on RUM de-obsfucated.
Describe what you expected:
Non-obfsucated stacktraces.
Additional context

Android Build Tools version: We're on AGP 8.5
Gradle version: 8.7
OS version: N/A
Plugin version: 1.14.0
Proguard configuration:

# Add project specific ProGuard rules here.
# You can control the set of applied configuration files using the
# proguardFiles setting in build.gradle.
#
# For more details, see
#   http://developer.android.com/guide/developing/tools/proguard.html

-keepattributes *Annotation*
-keepattributes SourceFile,LineNumberTable
-keep public class * extends java.lang.Exception

# GeoComply Proguard rules
-keep class com.geocomply.** { *; }
-keep class com.google.** { *; }
-keep class android.support.** { *; }

##---------------Begin: proguard configuration for Gson  ----------
# Gson uses generic type information stored in a class file when working with fields. Proguard
# removes such information by default, so configure it to keep all of it.
-keepattributes Signature

# Gson specific classes
-dontwarn sun.misc.**

# Prevent proguard from stripping interface information from TypeAdapter, TypeAdapterFactory,
# JsonSerializer, JsonDeserializer instances (so they can be used in @JsonAdapter)
-keep class * implements com.google.gson.TypeAdapter
-keep class * implements com.google.gson.TypeAdapterFactory
-keep class * implements com.google.gson.JsonSerializer
-keep class * implements com.google.gson.JsonDeserializer

# Prevent R8 from leaving Data object members always null
-keepclassmembers,allowobfuscation class * {
 @com.google.gson.annotations.SerializedName <fields>;
}
##---------------End: proguard configuration for Gson  ----------

-assumenosideeffects class android.util.Log {
   public static *** d(...);
   public static *** v(...);
}

# Navigation
-keep public class * implements android.os.Parcelable

-dontwarn org.conscrypt.Conscrypt$Version
-dontwarn org.conscrypt.Conscrypt
-dontwarn org.conscrypt.ConscryptHostnameVerifier
-dontwarn org.openjsse.javax.net.ssl.SSLParameters
-dontwarn org.openjsse.javax.net.ssl.SSLSocket
-dontwarn org.openjsse.net.ssl.OpenJSSE

-keepclassmembernames class bet.thescore.android.ui.webview.WebViewEvent$RunLexisNexisProfiling { *; }

-dontwarn com.miui.referrer.**
-dontwarn com.samsung.android.sdk.sinstallreferrer.**

# Keep public ViewModel constructors
-keepclassmembers public class * extends androidx.lifecycle.ViewModel { public <init>(...); }

Other Gradle Plugins:

org.gradle.testing.jacoco.plugins.JacocoPlugin
io.gitlab.arturbosch.detekt.DetektPlugin
com.google.firebase.crashlytics.buildtools.gradle.CrashlyticsPlugin
com.google.firebase.perf.plugin.FirebasePerfPlugin
org.gradle.api.plugins.JvmToolchainsPlugin
com.android.build.gradle.AppPlugin
com.google.gms.googleservices.GoogleServicesPlugin
androidx.navigation.safeargs.gradle.SafeArgsJavaPlugin
com.datadog.gradle.plugin.DdAndroidGradlePlugin
io.github.takahirom.roborazzi.RoborazziPlugin
org.jetbrains.kotlin.gradle.internal.Kapt3GradleSubplugin
org.jetbrains.kotlin.gradle.plugin.KotlinAndroidPluginWrapper
com.adarshr.gradle.testlogger.TestLoggerPlugin
org.jetbrains.kotlin.gradle.internal.ParcelizeSubplugin
app.cash.paparazzi.gradle.PaparazziPlugin

Hello @mformetal! Sorry for the very late reply.
Can you please share which version of our SDK you are using? If it is the version above 2.9.0, can you please check that error events you see in RUM/Logs have a build_id attribute with a value equal to the value shown in the mapping file upload?

Hey!
I am currently running into the same problem as described here. However, a few times the mapping was successful.
To give more detail (for cases where it does not work):
SDK Version: 2.13.1
Plugin Version: 1.14.0
The build_id attribute found in the error-log-JSON does not match the uploaded build_id from the logs or any uploaded mapping file at all. Seems logical, that matching is not possible here.
We upload the symbols right after minifying on CI:
afterEvaluate {
  if (System.getenv("DATADOG_API_KEY").isNullOrBlank()) return@afterEvaluate
    tasks.named("minify{...}WithR8") {
      finalizedBy("uploadMapping{...}")
    }
}

Logs show everything happening in the correct sequence, with the app built and distributed as an APK in our test environment:
> Task :app:uploadMapping{...}
Mapping file upload successful with tags `service:{...}`, `version:X.Y.Z`, `version_code:XXXXX`, `variant:`, `build_id:XXXXXXXXX`.
Make sure the SDK is initialized with the same values to ensure proper deobfuscation. Mapping files will be processed and ready within the next five minutes.

> Task :app:compile{...}ArtProfile
> Task :app:package{...}
> Task :app:create{...}ApkListingFileRedirect
> Task :app:assemble{...}

> <___Tasks that upload APK from outputs/___>

From checking out the source code of the plugin and SDK, it seems that the build_id is just read from file inside of the SDKs initialisation process, so as you would expect, we do not set, manipulate or use the file at all in our code.
Do you have any insight or idea why this could be happening?
Greatly appreciate the time!

Hello @RSM-CZE! Build ID is indeed injected by the Datadog Gradle Plugin.
The reason it may be different is having APK produced in the different build run than mapping file upload. Then in this case you may have different Build IDs for these two separate build runs. May it happen in our case?
Do you mind also to share the AGP version you are using?

I thought of that as well, but this is the only pipeline that uploads the mappings (because it is the only machine that has the API_KEY set). There are no new assemble tasks in between the mapping upload and the APK upload.
I can also reproduce this behaviour when building locally.
AGP: 8.3.2, Gradle: 8.9

@RSM-CZE Is it possible for you to provide a minimal reproducible example project?

@RSM-CZE This is kind of strange, because buildId should be updated.
Can you please share what are the command/tasks/inputs participating in the first build (checklist/tests as you've described), and what are the same values for the second build?
Also can you please share a workaround you've applied?
Maybe updating AGP version can solve your issue?

Hi @0xnm,
Apologies for the delayed response!
Updating AGP to 8.6.1 resolved the issue. Although I further tested isolated scenarios in a minimal project, I couldn't replicate the exact behaviour seen in the main project, so I can't provide further details on the root cause.
Thank you for your quick and helpful responses! 😊


Add documentation for configuration options

Per https://github.com/github/view_component/pull/952#discussion_r647465286, let's add a documentation section for configuration options to the API page, preferably generated via YARD.
cc @Spone

@Spone I've assigned you, but feel free to take your name off this if you'd like ❤

I think it maybe easier to write it manually like the Generators page (#952). I'm not sure how it could be generated via YARD.

@Spone I think we could extract the comments for the mattr_accessors that make up the configuration options via YARD 🤔


Global Illumination Light (none) setting ignores color settings of bright vision.

When you set this

your color settings for bright vision are ignored. In particular I'm using the module with 3.5 system for b/w darkvision, and it stops being b/w.

There's never a monochrome effect with global illumination enabled because the entire scene is lit, so technically there's no darkness. It's not a bug. With None it's just scene darkness.

I see, that sorta makes sense, but isn't too obvious. Thanks.


Setup Ceramic infrastructure

Cloud environment
Here are the official docs for running Ceramic in the cloud, including scripts for setting up kubernetes: https://developers.ceramic.network/docs/composedb/guides/composedb-server/running-in-the-cloud
I'm not sure how well those setup scripts work with the rest of our infrastructure.
What needs to be available is the trifecta of an IPFS node, a ceramic node, and a postgres database; each with its own persistent volume. Maybe not currently required, but there are some serious persistence requirements for the ceramic state store, the IPFS store, and the PG database. Since there is likely no-one else pinning the blocks with the codex commits at the moment, the data will be lost unless our node can recover from critical failure.
Service configuration
Here are the docs on configuring the ceramic service: https://developers.ceramic.network/docs/composedb/guides/composedb-server/server-configurations

@hubsmoke
Prep work

Create an RDS DB called ceramic

Image
https://hub.docker.com/r/ceramicnetwork/js-ceramic
Config
Configuration is done by mounting a config file at /root/.ceramic/daemon.config.json. Ceramic requires a state store, which is either a PD or an S3 bucket. Up to you what's easiest, I think it should work the same. See config alternative for this below.
{
  "anchor": {
    "ethereum-rpc-url": "[RPC_URL]"
  },
  "http-api": {
    "cors-allowed-origins": [
      ".*"
    ],
    "admin-dids": [
      "did:key:z6MktbKJrMnhVJ37QFTo12911ycm2juKDUzWHDVETu9s5a9T"
    ]
  },
  "ipfs": {
    "mode": "remote",
    "host": "http://[IPFS_IP_ADDRESS]:5001"
  },
  "logger": {
    "log-level": 2,
    "log-to-files": false
  },
  "metrics": {
    "metrics-exporter-enabled": false,
    "metrics-port": 9090
  },
  "network": {
    "name": "testnet-clay"
  },
  "node": {},
  "state-store": {
    "mode": "fs",
    "local-directory": "[PD_MOUNT_PATH]/ceramic/statestore"
  },
  "indexing": {
    "db": "postgres://[DB_USERNAME]:[DB_PASSWORD]@[HOST]/[DB_NAME]",
    "allow-queries-before-historical-sync": true,
    "enable-historical-sync": true,
    "models": []
  }
}

S3 state-store
If S3 for the ceramic state store is preferred, change state-store to this:
"state-store": {
    "mode": "s3",
    "s3-bucket": "[BUCKET_NAME]"
}

If so, these are the required permissions on the bucket:
"Action": [
  "s3:ListBucket",
  "s3:GetObject",
  "s3:PutObject",
  "s3:DeleteObject"
]

Running container
This is the command to run the container, I'm not sure how these convert to kube config:
docker run -d \
  -p 7007:7007 \
  -v /path_on_volume_for_daemon_config:/root/.ceramic/daemon.config.json \
  -v /path_on_volume_for_ceramic_statestore:/root/.ceramic/statestore \
  -e NODE_ENV=production \
  --name js-ceramic \
  ceramicnetwork/js-ceramic:latest

S3 alternative
If using S3 for the datastore, this is the corresponding command:
docker run -d \
  -p 7007:7007 \
  -v /path_for_daemon_config:/root/.ceramic/daemon.config.json \
  -e NODE_ENV=production \
  -e AWS_ACCESS_KEY_ID=s3_access_key_id \
  -e AWS_SECRET_ACCESS_KEY=s3_secret_access_key \
  --name js-ceramic \
  ceramicnetwork/js-ceramic:latest

Additional info
There is a YAML file here for health checks etc, if you want to set that up: https://github.com/ceramicstudio/simpledeploy/blob/aba2957f6add0a13d218bd04b352280dc6f70861/k8s/base/composedb/manifests/composedb.yaml


Passport generator not working

When I run tsed init . and choose Passport, it wasn't generate any passport files or endpoints, only includes dependencies

Yes. You have to run tsed g protocol after to choose the wanted protocol. It's not a bug :)


Usatlas

Hi, thanks for the great repo.
We are trying to build Usatlas to reproduce your results on multimodal data. We have downloaded satlas in it's entirety, do you have a script to build Usatlas from this?
Thanks again!

Thanks for your kind words!
Can you try the code here? https://github.com/stanfordmlgroup/USat/tree/satlas_dev/usat/data/satlas_data_prep

Ah great I had not seen. Closing the issue until I try it out.


Once docked, make the ship rotate with the dockable

Doing so would increase the game's polish. Right now, the station rotates and the ship doesn't move.
We should be able to do this with a RemoteTransform2D

I am interested in taking this issue. My only concern is the urgency of it. I might not be able to start looking at it seriously for a few days.

You can give it a try! Be sure to check our GDScript guidelines and commit guidelines

You can give it a try! Be sure to check our GDScript guidelines and commit guidelines

Ty! Can you assign this issue to me, just so I could find it easily :)
I will attach a gif to get your feedback, is this more or less what you are looking for (just to make sure I have understood the task)?

I assigned you!

is this more or less what you are looking for (just to make sure I have understood the task)?

Yes, exactly 🙂

Sorry for being a bad contributor and going silent, I have an initial PR up here https://github.com/GDQuest/godot-2d-space-game/pull/52


Generated Data Simulator (WIP)

Adds a new --sim argument that will run the mock simulation with randomly generated data. Long-term WIP.

Once you are done with this, I'll look over and maybe do a little more clean up, and maybe I'll have some suggestions/changes. Then we can merge it.
Once everything is merged, we can make a new branch/pr for writing integration tests that use the sim and test air brakes working

sounds good. Im not too sure when i'll be done with it, because it mostly comes down to fixing the last few bugs with apogee convergence time, and im not sure how long it will take me to find (and fix) the bug lol


Support `default_nettype in Verilog generator

Motivate of the pull request

[X] To address an existing issue. If so, please provide a link to the issue.
[ ] Breaking new feature. If so, please decribe details in the description part.

Describe the technical details

What is currently done? (Provide issue link if applicable)

Address issue #251
Currently OpenFPGA only support default_net_type none when generating Verilog netlists.

What does this pull request change?
This PR introduces a new option --default_net_type <string> to write_fabric_verilog command in openfpga shell.
Using the new option, users can customize the default net type for Verilog netlists to be auto-generated. See details at link
As a result, netlist sizes of top-level modules can be significantly reduced.

Take the example in behavioral_verilog generation test case:

Top-level netlist fpga_top.v has 634 lines when default_nettype  is set to none.
Top-level netlist fpga_top.v has 489 lines when default_nettype  is set to none.

Size compression rate is 23%.
Three new tests have been added:

Behavioral Verilog auto-generation with default net type wire
Verilog auto-generation with default net type wire using implicit port mapping
Verilog auto-generation with default net type wire using explicit port mapping

All the new tests, along with other tests for Verilog format support, are now moved to the test group verilog_netlist_formats under FPGA-Verilog tests.
Documentation has been added accordingly.
Which part of the code base require a change
In general, modification on existing submodules are not acceptable. You should push changes to upstream.

[ ] VPR
[X] OpenFPGA libraries
[X] FPGA-Verilog
[ ] FPGA-Bitstream
[ ] FPGA-SDC
[ ] FPGA-SPICE
[ ] Flow scripts
[ ] Architecture library
[ ] Cell library

Checklist of the pull request

[X] Require code changes.
[X] Require new tests to be added
[X] Require an update on documentation

Impact of the pull request

[ ] Require a change on Quality of Results (QoR)
[X] Break back-compatibility. If so, please list who may be influenced.

This PR introduces to minor changes to Verilog netlists but should not impact any functionality of previous tape-outs, such as SOFA.

@ganeshgore  Please review it and see it is what you want.

This works well. I can see top level netlist size reduced.
Pull request is out-of-date, please update and merge with master

@ganeshgore synchronized with master already.

Looks good


Create a 1.0.0 release tag

Hi,
Thanks for merging the bower.json, would it be possible for you to make a release with a 1.0.0 tag so I can pull from this repo from bower.
Thanks,
Simon

Hello,
I created it, thank you. I named the tag "v1.0.0" following github suggestion, let me know if this works for you.
Pierre

Works perfectly, thank you vey much. And thanks for the lib, makes constructing elastic queries very easy.
Simon


Adding Storyblok extension

Description
We use Storyblok, a headless CMS, a lot at my current outfit. I am always bopping around between different client spaces, development sandboxes, etc. This extension brings the power of Storyblok to Raycast to quickly open up those spaces, as well as accessing info without needing the Storyblok web interface. You can access stories (content), assets, users, and space activity all from within this command.
Screencast
https://github.com/raycast/extensions/assets/1895120/de9c83cd-4f0e-4ee1-a907-ebe07927581d
User preferences:

Checklist

[x] I read the extension guidelines

[x] I read the documentation about publishing

[x] I ran npm run build and tested this distribution build in Raycast

[n/a] I checked that files in the assets folder are used by the extension itself

[x] I checked that assets used by the README are placed outside of the metadata folder

Hi Rob Erskine 👋.
I am NOT a member of the Raycast team.
I was also working on an extension for Storyblok and I'm glad I can stop because yours is phenomenal 👌.
I notice you are using useFetch but you might be interested in the approach I took; though definitely a work-in-progress I used storyblok-js-client as it exposes types and I created my own custom hook Link to Hook in Repo that works like useFetch but has the benefit of returning errors which might be helpful in the future.
I look forward to installing your extension from the store!
Best.

@xmok thanks for the heads up on the custom hook. I will take a look at this for v1.1. I want to get it live and see how people use it and then improve on it; this hook looks like a great start.

Better to use some mock data instead of mosaics on the screenshot.

@LitoMore I hear you, but Storyblok is a paid service, and getting the full scope of what's possible on a free account to create mock data is a bit tricky.
It's not impossible, so if the recommendation is to use mock data instead (some of the screenshots will be more limited in what they show), I can do that.

If there is no sensitive data it's okay to use it, but many uses some mock data - is there any sensitive data @RobErskine

@pernielsentikaer the information mosaicked out in the screenshots in metadata are client/brand names in our Storyblok Partner space and subsequent customer names / their emails.
Do you recommend swapping what I posted with a fake account / mock data instead of censoring those private strings? I know the Do's and Don'ts say not to use censored data, which is why I have the censored out.
If it's better to use mock data, I can spin up a new Storyblok account, create a bunch of fake data, hook the extension up to that access token, and take new screenshots this evening.


UserWarning: Accession IMS:1000046

When I try to follow the Example , I met an error:

UserWarning: Accession IMS:1000046 found with incorrect name "pixel size". Updating name to "pixel size (x)".

But there's no "pixel size" in the code, what does it means?

I think your error is related to the reading or writing of the .imzML data.
Make sure that your using the pyimzML functions correctly and that your data is correct!

I think your error is related to the reading or writing of the .imzML data.
Make sure that your using the pyimzML functions correctly and that your data is correct!

I met this problem same! I don not know how to solve this problem yet!  Can you give some advices?
from pyimzml.ImzMLParser import ImzMLParser
p = ImzMLParser('3DMouseKidney.imzML')
That is how i read the imzML. It warns me that "UserWarning: Accession IMS:1000046 found with incorrect name "pixel size". Updating name to "pixel size (x)".
% (accession, raw_name, name)
IndexError: list index out of range"

@skywalker-andy I am one of developers of pyimzml. Please ask your question in our repo: https://github.com/alexandrovteam/pyimzML
It would be very useful to have access to your imzML file, or at least the first few hundred lines of that file.


Fix/hcc bundle

Codecov Report
Base: 86.31% // Head: 86.28% // Decreases project coverage by -0.03% :warning:

Coverage data is based on head (008e1b9) compared to base (78815dd).
Patch coverage: 0.00% of modified lines in pull request are covered.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##           master     #321      +/-   ##
==========================================
- Coverage   86.31%   86.28%   -0.03%
==========================================
  Files          40       40
  Lines        4098     4099       +1
  Branches     1204     1204
==========================================
  Hits         3537     3537
- Misses        498      499       +1
  Partials       63       63

Impacted Files
Coverage Δ

packages/cli-plugin-package/src/index.ts
82.15% <0.00%> (-0.13%)
:arrow_down:

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

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


Is there some control over number of 'dots' shown on carousel?

regardless of slides added I always get three dots?

I will look into this, it should automatically have the correct number of dots as you add in slides.

This is a confirmed bug. I've fixed the issue, I will send out a new CocoaPods update sometime today which will solve this and #22.

I'm still seeing three dots everytime (actual slides I can still swipe through is more its jsut the indicator not right)
Im running proper version
Installing ZKCarousel 0.2.1 (was 0.1.8 and source changed to https://github.com/CocoaPods/Specs.git from https://github.com/cocoapods/specs.git)
cheers
Chris

I'll look into it again, for now I would recommend looking at the updated example project. I have set that to implement 6 slides, with the dots showing correct number for slides.

@ChrisAldridgeRIT Not sure what’s going on for you, I’m not able to replicate the bug after update 0.2.1. I am able to download the example project, build and run without issues.
If you would like to post your code that adds the slides, that may provide some insight.

Closing due to the fact that everything seems good on my end. I am able to run pod try ZKCarousel in terminal, which downloads and opens version 0.2.1, and the project runs as expected. Dots work correctly relative to the number of slides you feed into the carousel.

I think its related to the problems I have with the Async loading of the images. NP though, am investigating and will let you know if I spot anything
cheers

I think its related to the problems I have with the Async loading of the images. NP though, am investigating and will let you know if I spot anything
cheers

Let me know if I can do anything to help. As long as you are updating the slides property on ZKCarousel, it should auto-update the page indicator dots.


Promtool: support rule evaluation command

Proposal
Use case. Why is this important?
As a Prometheus user/SRE, I want to add some new alerting rules. But right now, there is not a good way to test these new rules against a running Prometheus. Compare to promtool test rules command, the rule evaluation command can specify the server address and evaluates the rules against that server. This is more like an E2E test rather than a unit test.
Example usage
promtool  rules <server> <rule-files-to-evaluate>
Possible implementation
Similar to promtool tsdb create-blocks-from rules command, this command can iterate through all rules in the rule files and perform instant queries against the server based on the given query expression. This goes through the api/v1/query API so ALERTS and ALERTS_FOR_STATE won't be written to TSDB.

It's an interesting idea and something I've thought about too, but really this direction leads to re-implementing Prometheus itself in promtool (rules that depend on each other need to be written to an underlying TSDB... how do you view the results? do you want a graph UI? etc...)
A way you can do this right now is write a minimal Prometheus config that points at another Prometheus through remote read, literally just this:
remote_read:
  - url: http://prometheus.demo.do.prometheus.io/api/v1/read
    read_recent: true
rule_files:
  - the-extra-rules-you-want-test.yaml

Another idea that I quite like is making it easier to write rule tests, maybe a way to point at some data and generate the input_series based on that data (this gets into needing to understand relationships of rules and so on, e.g. https://github.com/vatine/promgraph type thing); that could be a tool that sits outside of prometheus itself and help with this kind of thing though.

It's an interesting idea and something I've thought about too, but really this direction leads to re-implementing Prometheus itself in promtool (rules that depend on each other need to be written to an underlying TSDB... how do you view the results? do you want a graph UI? etc...)

We can do it in a simple way and I think it is okay to not handle recording rules and these dependencies. Instant query for rules expr would be good enough.

... which we already support in promtool

and in the prometheus UI

This seems like
https://github.com/prometheus/prometheus/pull/4277
https://github.com/prometheus/prometheus/issues/1220
https://github.com/prometheus/prometheus/issues/1154
WDYT?

@roidelapluie Thanks, I see. Yeah, there is some overlapping here

Hello from the bug scrub!
3y later… Since nothing has happened here to further flesh out what to do here concretely, we'll close this now. Please refer to the other issues for related topics that are probably more concrete feature requests to implement.
Feel free to follow up with contrary evidence.


iOS: input file click not triggered

Hello, it seems that the input.click() is not triggered with a mousedown or touchstart event. It should be attached on the click event instead. Found this bug on iOS 16

Hey, thanks for opening an issue.
Care to expand on what went wrong? Do you mean that the following line is not being executed on iOS 16?
https://github.com/LuchoTurtle/tweakpane-plugin-file-import/blob/548e1144ad5b69684b4d855e34b53e3d9fd10652/src/controller/controller.ts#L102
Are you using which browser?

Care to expand on what went wrong? Do you mean that the following line is not being executed on iOS 16?

It's indeed this line. I would say this action is ignored because it was not triggered from a click but with touchstart/mousedown from used in the tweakpane PointerHandler.

Are you using which browser?

Safari

@Matoseb thanks for opening. The issues has been fixed in v1.0.2. 👌


Add HashiCorp

Name with link
HashiCorp
https://www.hashicorp.com/
Description
Software company.
Developing Consul, Nomad, Packer, Vagrant, Terraform, Vault, ...etc.
Link to the vector file, preferably from an official source
https://www.hashicorp.com/brand#logo

Get a zip file with Download Logo Assets button.
SVG files in the zip file:

Corporate/Logo/Primary_Horizontal/RGB/SVG/*.svg
Corporate/Logo/Secondary_Vertical/RGB/SVG/*.svg
Corporate/Logomark/RGB/SVG/*.svg

Added in 1f372be75689d73cae89b6de808149b606b879e1
Thanks


Translations: Auto fallback to english if translation is empty

In case we are missing a translation in some language, I think it is better to show a message in english, instead of showing noting.
Now for example trying to login with wrong username/password and with  swedish as the language, you are presented with empty error message and thats just a bit silly.

+1

Sounds like a plan!


[stable/kube-state-metrics] Version bump to 1.9.0

What this PR does / why we need it:
Updates to K-S-M 1.9.0
Special notes for your reviewer:
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
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

/lgtm

/assign


mobile: change tun_fd in start_mycelium to Option.

Change it for flexibility.
In our case, Windows won't send the TUN fd.

closing it,
it is not a valid issue


Modularize deployer

Use the Docker image https://github.com/CloudReactor/aws-ecs-cloudreactor-deployer to deploy instead of including all deployment files and dependencies.

Merged already


Additional minor edits

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/best-practices/retry-service-specific.md
:white_check_mark:Succeeded
View

docs/multitenant-identity/authenticate.md
:white_check_mark:Succeeded
View

docs/multitenant-identity/token-cache.md
:white_check_mark:Succeeded
View

docs/reference-architectures/identity/adds-extend-domain.md
:white_check_mark:Succeeded
View

docs/reference-architectures/identity/adds-forest.md
:white_check_mark:Succeeded
View

docs/reference-architectures/identity/adfs.md
:white_check_mark:Succeeded
View

docs/reference-architectures/sharepoint/index.md
:white_check_mark:Succeeded
View

docs/reference-architectures/virtual-machines-linux/single-vm.md
:white_check_mark:Succeeded
View

docs/reference-architectures/virtual-machines-windows/single-vm.md
:white_check_mark:Succeeded
View

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


add infrawallet to the plugins directory

Hey, I just made a Pull Request!
This PR adds our new FinOps plugin InfraWallet to the plugins directory page.
https://github.com/electrolux-oss/infrawallet
:heavy_check_mark: Checklist
Based on the tips on this page, we have done the following checks.

[x] For any icon that you use make sure you have the proper rights to use it.
[x] Make sure that your package had been published on the NPM registry and that it's public.
[x] Make sure your package on NPM has a link back to your code repo, this helps provide confidence that it's the right package.
[x] Where possible, please use an NPM scope that matches either your Organization name or user name, this provides trust in the plugin
[x] If your plugin has both a frontend and backend link the documentation to the frontend package but make sure it mentioned needing to install the backend package.
[x] Where possible include a screenshot of the features in you plugin documentation, it really does help when deciding to use a plugin.

Thanks @Rugvip for the quick review!


Disambiguate subscript decls by preferring the one with more accessors.

Closing #5034.
Directly allowing defining set and get in different subscript decls and allow deferred overload resolution is tricky to support. However it is trivial to add a disambiguation rule to prefer the one with more complete accessors. This should allow example like #5034 to work, but in a slightly different way:
//TEST(compute):COMPARE_COMPUTE_EX(filecheck-buffer=CHECK):-slang -compute -shaderobj -output-using-type
//TEST(compute, vulkan):COMPARE_COMPUTE_EX(filecheck-buffer=CHECK):-vk -compute -shaderobj -output-using-type

// Test that we can disambiguiate subscript decls by prefering the candidate that contains a super set of
// accessors than the other candidates.
interface IBuf<T>
{
    T read(int x);
}
interface IRWBuf<T> : IBuf<T>
{
    [mutating]
    void write(int x, T v);
}

extension<T, U : IBuf<T>> U
{
    __subscript(int x) -> T { get { return read(x); } }
}

extension<T, U : IRWBuf<T>> U
{
  // This would have introduced ambiguity, however by providing both getter and setter
  // here, we can make use the disambiguation logic to prefer this one.
    __subscript(int x)->T { get { return read(x); } set { write(x, newValue); } }
}

struct MyArray<T> : IRWBuf<T>
{
    T data[4];
    T read(int x) { return data[x]; }
    [mutating]
    void write(int x, T v) { data[x] = v; }
}

//TEST_INPUT:ubuffer(data=[0 0 0 0], stride=4):out,name=outputBuffer
RWStructuredBuffer<int> outputBuffer;

[numthreads(1,1,1)]
void computeMain()
{
    MyArray<int> arr = {};
    arr[0] = 1;
    arr[1] = 2;
    // CHECK: 1
    // CHECK: 2
    outputBuffer[0] = arr[0];
    outputBuffer[1] = arr[1];
}

The interfaces may not have any subclass relationship, but you may still expect this work:
extension MyType
{
      __subscript {get;set;}
}
extension MyType
{
      __subscript{get;}
}


feat: update grpc stubs

Updates gRPC stubs from ZITADEL main branch.
Definition of Ready

[x] I am happy with the code
[x] Short description of the feature/issue is added in the pr description
[ ] PR is linked to the corresponding user story
[x] Acceptance criteria are met
[x] All open todos and follow ups are defined in a new ticket and justified
[x] Deviations from the acceptance criteria and design are agreed with the PO and documented.
[x] No debug or dead code
[x] My code has no repetitions
[x] Critical parts are tested automatically
[x] Where possible E2E tests are implemented
[x] Documentation/examples are up-to-date
[x] All non-functional requirements are met
[x] Functionality of the acceptance criteria is checked manually on the dev system.

Closing, as #207 is merged


feat: tune trivy scanning severity

continues #522 to increase sensitivity and integrate with the github security tab
ref #366

We'll need to keep an eye on the Security tab moving forward, and we'll triage on a sprint basis. The goal in merging this is to avoid introducing a regression. It looks really bad here because there's no data on the main branch yet, but once there is our checks will fail based on the diff between the PR and the main branch (ie new issues will cause failure).


The dictionary AttrDict is not deepcopiable

The deepcopy of the AttrDict is failing as the "getattr" doesn't raise AttributeError for non existing attributes.
The getattr(x, "deepcopy", None) is invoked internally on deepcopy.
The attribute "deepcopy" is not present and hence KeyError is raised by "getitem" but AttributeError is expected from "getattr"

Fixed in 2.0.0, thanks for your PR!


Backport "HBASE-27568 ChaosMonkey add support for JournalNodes" to branch-2.4

Signed-off-by: Reid Chan<EMAIL_ADDRESS>

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
2m 44s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ branch-2.4 Compile Tests _

+0 :ok:
mvndep
0m 10s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m  4s
branch-2.4 passed

+1 :green_heart:
compile
3m 12s
branch-2.4 passed

+1 :green_heart:
checkstyle
0m 47s
branch-2.4 passed

+1 :green_heart:
spotless
0m 45s
branch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
2m  8s
branch-2.4 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 11s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 57s
the patch passed

+1 :green_heart:
compile
3m  3s
the patch passed

+1 :green_heart:
javac
3m  3s
the patch passed

+1 :green_heart:
checkstyle
0m 44s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
17m 22s
Patch does not cause any errors with Hadoop 2.10.2 or 3.1.4 3.2.4 3.3.4.

+1 :green_heart:
spotless
0m 42s
patch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
2m 21s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 17s
The patch does not generate ASF License warnings.

42m 29s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4978/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/4978

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti spotless checkstyle compile

uname
Linux 6301a20902d1 5.4.0-135-generic #152-Ubuntu SMP Wed Nov 23 20:19:22 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2.4 / 6d2064d443

Default Java
Eclipse Adoptium-11.0.17+8

Max. process+thread count
81 (vs. ulimit of 30000)

modules
C: hbase-server hbase-it U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4978/1/console

versions
git=2.34.1 maven=3.8.6 spotbugs=4.7.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 20s
Docker mode activated.

-0 :warning:
yetus
0m  6s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2.4 Compile Tests _

+0 :ok:
mvndep
0m 13s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
2m 50s
branch-2.4 passed

+1 :green_heart:
compile
1m 16s
branch-2.4 passed

+1 :green_heart:
shadedjars
5m  8s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 37s
branch-2.4 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 12s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 23s
the patch passed

+1 :green_heart:
compile
1m  1s
the patch passed

+1 :green_heart:
javac
1m  1s
the patch passed

+1 :green_heart:
shadedjars
4m 37s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 38s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
181m 15s
hbase-server in the patch passed.

+1 :green_heart:
unit
1m  1s
hbase-it in the patch passed.

206m 34s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4978/1/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/4978

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux e370e03fd09d 5.4.0-1088-aws #96~18.04.1-Ubuntu SMP Mon Oct 17 02:57:48 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2.4 / 6d2064d443

Default Java
Temurin-1.8.0_352-b08

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4978/1/testReport/

Max. process+thread count
2609 (vs. ulimit of 30000)

modules
C: hbase-server hbase-it U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4978/1/console

versions
git=2.34.1 maven=3.8.6

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
2m 20s
Docker mode activated.

-0 :warning:
yetus
0m  5s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2.4 Compile Tests _

+0 :ok:
mvndep
0m 14s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m  3s
branch-2.4 passed

+1 :green_heart:
compile
1m  9s
branch-2.4 passed

+1 :green_heart:
shadedjars
5m 28s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 43s
branch-2.4 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 17s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 32s
the patch passed

+1 :green_heart:
compile
1m  9s
the patch passed

+1 :green_heart:
javac
1m  9s
the patch passed

+1 :green_heart:
shadedjars
5m 27s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 37s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
185m 24s
hbase-server in the patch passed.

+1 :green_heart:
unit
1m 11s
hbase-it in the patch passed.

215m  1s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4978/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/4978

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 9ab6c72b606c 5.4.0-1088-aws #96~18.04.1-Ubuntu SMP Mon Oct 17 02:57:48 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2.4 / 6d2064d443

Default Java
Eclipse Adoptium-11.0.17+8

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4978/1/testReport/

Max. process+thread count
2948 (vs. ulimit of 30000)

modules
C: hbase-server hbase-it U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4978/1/console

versions
git=2.34.1 maven=3.8.6

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.


fix: reader.ReadRotationPacked() "w" reconstruction

The correct formula to reconstruct w is

w = sqrt( 1 - x^2 - y^2 - z^2 )

but in code was

w = sqrt(1 - x^2 + y^2 - z^2)

This pull request is included in version 11.11.1
The release is available to download on GitHub release or in the MLAPI Installer.


Twitter doesn't work anymore

I'm using sharrre on my website for a long time and i just realize that twitter sharing button is no more active. This problem is also occuring on official sharrre website (http://sharrre.com/example1.html). Is there a way to fix this problem?

Twitter removed the link to get the share count. This seems to break a lot of Twitter buttons. See #258 for something that may fix this.

More info on the removal of Twitter's Tweet count endpoint:

http://stackoverflow.com/a/33893042
https://blog.twitter.com/2015/hard-decisions-for-a-sustainable-platform

Now you can create an account on OpenShareCount if you want to use the feature.


build(finq): prepare release v0.2.0 to pypi with poetry

Large changes to pyproject.toml config with poetry as build engine. Changed CI and tests steps to use poetry and pytest instead of pip and unittest. Added CD pipeline that runs on release publish eventhook.
TODO before first release: add pypi token as repo secret

Related issue #26

@AugustSoderlund  sadly there's a lot of changes here to look through... sorry
However, I would recommend just looking at changes that are related to the code base (finq/, tests/)
We're (most likely) gonna have some breaking changes with the workflow and testing changes, but we can resolve them after merge. Thoughts? 😺

I'm gonna merge this and handle any breaking changes.


Wagtail API should have a browsable root URL

It always feels nice when browsing to /api/v1/ presents a list of the available API endpoints.
Something like this should do it.. mashing up the get_api_root_view from rest_framework's  DefaultRouter.
Is there a reason we're not extending one of the rest_framework router classes? I guess ViewSets + Page model introspection could be an issue, but haven't looked into it too much.
I'm in the middle of a project, but will create a PR when I get a moment if you think it's a good idea.
from collections import OrderedDict
from django.conf.urls import url, include
from django.core.urlresolvers import NoReverseMatch
from rest_framework import views
from rest_framework.reverse import reverse
from rest_framework.response import Response
from wagtail.contrib.wagtailapi.router import WagtailAPIRouter
from wagtail.utils.urlpatterns import decorate_urlpatterns

class WagtailAPIDefaultRouter(WagtailAPIRouter):
    root_view_name = 'api-root'

    def get_api_root_view(self):
        """
        Return a view to use as the API root.
        """
        api_root_dict = OrderedDict()

        # In the DRF, these are usually {basename}-list
        for name, class_ in self._endpoints.items():
            api_root_dict[name] = "{basename}".format(basename=name)

        class APIRoot(views.APIView):
            _ignore_model_permissions = True

            def get(self, request, *args, **kwargs):

                ret = OrderedDict()
                namespace = request.resolver_match.namespace

                for key, url_name in api_root_dict.items():
                    url_name = url_name + ':' + 'listing'

                    if namespace:
                        url_name = namespace + ':' + url_name

                    try:
                        ret[key] = reverse(
                            url_name,
                            args=args,
                            kwargs=kwargs,
                            request=request,
                            format=kwargs.get('format', None)
                        )
                    except NoReverseMatch:
                        # Don't bail out if eg. no list routes exist
                        continue

                return Response(ret)

        return APIRoot.as_view()

    def get_urlpatterns(self):
        urlpatterns = []

        for name, class_ in self._endpoints.items():
            # print name
            pattern = url(
                r'^{}/'.format(name),
                include(class_.get_urlpatterns(), namespace=name)
            )
            urlpatterns.append(pattern)

        decorate_urlpatterns(urlpatterns, self.wrap_view)

        root_url = url(r'^$', self.get_api_root_view(), name=self.root_view_name)
        urlpatterns.append(root_url)

        return urlpatterns

Devs would have to assign the API endpoints manually using the subclass, but that's easy enough to do.
v1 = WagtailAPIDefaultRouter('wagtailapi_v1')
v1.register_endpoint('pages', PagesAPIEndpoint)
v1.register_endpoint('images', ImagesAPIEndpoint)
v1.register_endpoint('documents', DocumentsAPIEndpoint)

urlpatterns = [
    url(r'^v1/', v1.urls),
]

Also, I think it would be helpful to bake-in references to the children + a hint to see whether we should bother looking them up... something like this?
"children": {
        "total_count": 5,
        "url": "http://localhost:8111/api/v1/pages/?child_of=3"
  }

Thanks @JoshBarr. I think both are good ideas.
Open question: Should we expand v1 or make these changes on a new v2 API instead?
I think we should avoid changing v1 now and create a new api endpoint called "v2beta" for new features. So those who want a stable API that will never change between releases could use v1, and those who don't mind having to update client-side code on every Wagtail update can use "v2beta" and will get all the new features. At a point in the future, we would stabilise v2 and start working on v3beta, and so on and so on. Is this worth doing or too much hastle?

Is there a reason we're not extending one of the rest_framework router classes?

I think it was because we need to cross-link between the endpoints and I couldn't find an easy way to do this with REST framework's routers. I would be in favour of switching to them if we find a way to implement this though.

I'm in favour of a v2 API. There's some other optimisations that might be nice to make, like providing a list of relations to return inline rather than as references, automatically including the parents up to the root (ie, for creating breadcrumbs), making nodes discoverable via their slug, etc. I think there's enough in here to warrant a v2beta without being worried about backwards-breaking changes, as you suggest!
@jordij also brought up filtering nodes via relations, which might require leveraging more rest_framework components.
Would you imagine the v2 API being the same as the admin API, providing authenticated and non-authenticated views?

bump for root


Add prints to show space

It is passing on this one. I think it problem on github runner. we probably just need to re-run.


Added test steps for all threads as well as setup steps for checking …

…the environment, filling memory pages, and then checking that memory copy operations were executed properly.
Internal reference: b/273820182
Tested:
dthawkes@dthawkes:~/ocp-diag-sat$ bazel-docker
Starting local Bazel server and connecting to it...
INFO: Analyzed 2 targets (127 packages loaded, 4252 targets configured).
INFO: Found 2 targets...
INFO: From Compiling src/sat.cc:
src/sat.cc: In member function 'int Sat::CacheLineSize()':
src/sat.cc:1538:21: warning: 'linesize' may be used uninitialized in this function [-Wmaybe-uninitialized]
 1538 |   int max_linesize, linesize;
      |                     ^~~~~~~~
INFO: Elapsed time: 13.563s, Critical Path: 8.29s
INFO: 7 processes: 1 internal, 6 processwrapper-sandbox.
INFO: Build completed successfully, 7 total actions
dthawkes@dthawkes:~/ocp-diag-sat$ ./bazel-bin/src/sat_bin
{"schemaVersion":{"major":2,"minor":0},"sequenceNumber":0,"timestamp":"2023-03-21T23:27:06Z"}
{"testRunArtifact":{"testRunStart":{"name":"Stress App Test","version":"1.0.0","commandLine":"./bazel-bin/src/sat_bin","parameters":{},"dutInfo":{"dutInfoId":"holder","name":"place","metadata":{},"platformInfos":[],"hardwareInfos":[],"softwareInfos":[]},"metadata":{}}},"sequenceNumber":1,"timestamp":"2023-03-21T23:27:06Z"}
{"testStepArtifact":{"testStepStart":{"name":"Setup and Check Environment"},"testStepId":"0"},"sequenceNumber":2,"timestamp":"2023-03-21T23:27:06Z"}
2023/03/21-23:27:06(UTC) Log: 1 nodes, 64 cpus.
2023/03/21-23:27:06(UTC) Log: Defaulting to 64 copy threads
2023/03/21-23:27:06(UTC) Log: Total 515961 MB. Free 493187 MB. Hugepages 0 MB. Targeting 489971 MB (94%)
2023/03/21-23:27:06(UTC) Log: Prefer plain malloc memory allocation.
2023/03/21-23:27:06(UTC) Log: Using mmap() allocation at 0x7ea2d871e000.
2023/03/21-23:27:06(UTC) Stats: Starting SAT, 489971M, 20 seconds
{"testStepArtifact":{"testStepEnd":{"status":"COMPLETE"},"testStepId":"0"},"sequenceNumber":3,"timestamp":"2023-03-21T23:27:06Z"}
{"testStepArtifact":{"testStepStart":{"name":"Fill Memory Pages"},"testStepId":"1"},"sequenceNumber":4,"timestamp":"2023-03-21T23:27:06Z"}
2023/03/21-23:27:27(UTC) Log: Region mask: 0x1
{"testStepArtifact":{"testStepEnd":{"status":"COMPLETE"},"testStepId":"1"},"sequenceNumber":5,"timestamp":"2023-03-21T23:27:27Z"}
{"testStepArtifact":{"testStepStart":{"name":"Poll for System Error Messages"},"testStepId":"2"},"sequenceNumber":6,"timestamp":"2023-03-21T23:27:27Z"}
{"testStepArtifact":{"testStepStart":{"name":"Run Memory Copy Threads"},"testStepId":"3"},"sequenceNumber":7,"timestamp":"2023-03-21T23:27:27Z"}
2023/03/21-23:27:37(UTC) Log: Seconds remaining: 10
{"testStepArtifact":{"testStepStart":{"name":"Run Post-Test Memory Check Threads"},"testStepId":"4"},"sequenceNumber":8,"timestamp":"2023-03-21T23:27:47Z"}
{"testStepArtifact":{"testStepEnd":{"status":"COMPLETE"},"testStepId":"4"},"sequenceNumber":9,"timestamp":"2023-03-21T23:27:51Z"}
2023/03/21-23:27:51(UTC) Stats: Found 0 hardware incidents
{"testStepArtifact":{"testStepEnd":{"status":"COMPLETE"},"testStepId":"2"},"sequenceNumber":10,"timestamp":"2023-03-21T23:27:51Z"}
2023/03/21-23:27:51(UTC) Stats: Completed: 2528154.00M in 20.09s 125839.50MB/s, with 0 hardware incidents, 0 errors
2023/03/21-23:27:51(UTC) Stats: Memory Copy: 2528154.00M at 126014.09MB/s
2023/03/21-23:27:51(UTC) Stats: File Copy: 0.00M at 0.00MB/s
2023/03/21-23:27:51(UTC) Stats: Net Copy: 0.00M at 0.00MB/s
2023/03/21-23:27:51(UTC) Stats: Data Check: 0.00M at 0.00MB/s
2023/03/21-23:27:51(UTC) Stats: Invert Data: 0.00M at 0.00MB/s
2023/03/21-23:27:51(UTC) Stats: Disk: 0.00M at 0.00MB/s
{"testStepArtifact":{"testStepEnd":{"status":"COMPLETE"},"testStepId":"3"},"sequenceNumber":11,"timestamp":"2023-03-21T23:27:51Z"}
2023/03/21-23:27:51(UTC)
2023/03/21-23:27:51(UTC) Status: PASS - please verify no corrected errors
2023/03/21-23:27:51(UTC)
{"testRunArtifact":{"testRunEnd":{"status":"COMPLETE","result":"PASS"}},"sequenceNumber":12,"timestamp":"2023-03-21T23:27:56Z"}

Current dependencies on/for this PR:

SAT_INIT_TEST_RUN

PR #6   👈

PR #7

This comment was auto-generated by Graphite.


Use single package manager.

https://github.com/Arpan-206/DevArmyKnife/blob/5b5fdd54809a72a0038be1f857d61f429b10adb3/Dockerfile#L10
We should use any one package manager. As yarn is most preferable here so I think we can convert this line to something equivalent using yarn.

Go right ahead!

https://github.com/Arpan-206/DevArmyKnife/blob/5b5fdd54809a72a0038be1f857d61f429b10adb3/Dockerfile#L5
can you please tell me why you are using --frozen-lockfile flag? Is there any specific cause? Because yarn install is sufficient to remove packages and installing dependencies as per the documentation.

https://github.com/Arpan-206/DevArmyKnife/blob/5b5fdd54809a72a0038be1f857d61f429b10adb3/Dockerfile#L5
can you please tell me why you are using --frozen-lockfile flag? Is there any specific cause? Because yarn install is sufficient to remove extraneous packages and installing dependencies as per the documentation.

Well, it has actually been so long that I don't actually remember, a bad answer I know, but well. So, once you make a PR, Netlify will give you a preview if it's a site change. For docker, I'll have to check it out.

As I will be modifying the docker file hopefully you have to check it manually but let me cross check everything and I will be opening a pr soon.


Crash After Updating From <IP_ADDRESS> to <IP_ADDRESS>

Forge Version:
2772
Link to crash log (if applicable):
crash-2018-11-02_22.20.29-client.txt
Description:
First of all, i'm not %100 sure it's about Dynamic Surroundings, but this crash happens randomly while playing. And it started happening after updating DS. Sorry if it's not about DS, but i need help :(

I can't say with 100% certainty what who the culprit is.  But in general these things are caused by the server side thread trying to play a sound.  What happens is that mod logic works with the client side classes which is a big no no.  Depending on how you feel you can do one of two things:

In the Dynamic Surroundings configuration you can set "Enable synchronized for Sound Manager".  This will cause DS to modify some java code at startup to synchronize (or only let one call through) to the SoundManager at a time.  So if indeed the server thread is trying to talk with client code, and the client thread wants to do something, they won't step over each other.
You can put DS in developer mode.  Add "-Ddsurround.devMode" (without the quotes) to your Java command line parameters.  What this will do is cause DS to audit what thread is doing what with the sound engine.  If it detects that a thread other than the client thread does something with the sound engine it will cause your client to crash, generating a callstack in the process.  This callstack will allow us to pin point the mod that is causing this issue.
Which of these options you pick is up to you.  The first gets you back to playing, the second helps find the root problem and we can notify the mod developer.  Of course, you can do the 2nd, and when we identify the problem you can do the 1st until a fix is made.

Thank you so much for your help! I will try those things and give you feedback if would needed by you.

Yes, I would like feedback as to the results.  I have an interest in which mod is causing the difficulty.

Uhm, last night, i just did this. Then we played about 45 mins, and it didn't crash. I can help you understand which mod causes if you wish. BUT, my guessing is, it's Weather mod. You could take a look into that :p

Cool.  If I were to guess I would say Ice and Fire.  Reason is, well, those two settings you turned on I put because of Ice and Fire. :)  I am going to close the defect, and if you run into any further problems let me know.


[Table pagination dropdown arrow]: Dropdown not appearing when you click the arrow

Detailed description
I added a pagination model to my table (separately as I needed to add my own functionality to the pagination bar) and when you click on the dropdown arrow to select a page number nothing appears. However, when you click the number then the dropdown appears. I'm not sure if this is a bug or just intended but it is a little confusing. I currently work in Firefox, and working with the latest version of carbon-components and carbon-components-angular.
Steps to reproduce the issue

Added pagination component to page
Gave the pagination component a model with sizes and page numbers etc
Set current page to 1 and set total data length to size of data coming in from the api

Additional information

Screenshots or code

Seems to be working fine in the story. Here's the code for that story.
From your comment, it's not clear if you're using the same (TableModel) for the table and the pagination, but you should, they are designed for that.
It also, from the image, looks like only the number portion is selected (the blue rectangle) while in the story it always also selects the chevron (so it's inside the rectangle).
Can you create a minimal reproduction app?

Seems to be working fine in the story. Here's the code for that story.
From your comment, it's not clear if you're using the same (TableModel) for the table and the pagination, but you should, they are designed for that.
It also, from the image, looks like only the number portion is selected (the blue rectangle) while in the story it always also selects the chevron (so it's inside the rectangle).
Can you create a minimal reproduction app?

After chatting about it, it looks like an app level issue.


Refactor manifest testsuites

The various manifest test suites (for SPARQL compliance, for example) still using Junit 3 constructions to create the suite. A major drawback is that because of the way the individual tests are created and run, it is virtually impossible to efficiently debug a single case.
We should look into a more efficient test suite setup using parametrized tests.

is this related to #1563 ?

Not necessarily - we can already make the manifest tests a lot easier to use in JUnit 4. I've already put some new code in place when I was doing fixes for named graph support in FedX - I now mostly need to find the time to apply it to the other testsuites and then phase out the antiquated junit3-based manifest tests.


Option --windows-driver ovpn-dco is ignored because Data Channel Offload is disabled

Hi, everyone
OS: Windows 11 Version 22H2 (OS Build 22621.1413)
I am trying to connect to my VPN server through the OpenVPN GUI using the new driver, but it does not work. In the logs I see the following:
2023-03-24 12:56:06 WARNING: Compression for receiving enabled. Compression has been used in the past to break encryption. Sent packets are not compressed unless "allow-compression yes" is also set.
2023-03-24 12:56:06 Note: '--allow-compression' is not set to 'no', disabling data channel offload.
2023-03-24 12:56:06 Option --windows-driver ovpn-dco is ignored because Data Channel Offload is disabled
2023-03-24 12:56:06 OpenVPN 2.6.1 [git:v2.6.1/2c2a98a0e559928c] Windows-MSVC [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [AEAD] [DCO] built on Mar  8 2023
2023-03-24 12:56:06 Windows version 10.0 (Windows 10 or greater), amd64 executable
2023-03-24 12:56:06 library versions: OpenSSL 3.0.8 7 Feb 2023, LZO 2.10

At the same time, I see that the Data Channel Offload adapter is installed and enabled:
>netsh int show int

Admin State    State          Type             Interface Name
-------------------------------------------------------------------------
Enabled        Disconnected   Dedicated        OpenVPN Wintun
Enabled        Disconnected   Dedicated        OpenVPN TAP-Windows6
Enabled        Disconnected   Dedicated        OpenVPN Data Channel Offload

What am I doing wrong?

Forget about .ovpn config:
client
dev tun
windows-driver ovpn-dco
proto udp
remote <masked>
remote <masked>
resolv-retry infinite
nobind
persist-key
persist-tun
remote-cert-tls server
key-direction 1
cipher AES-256-CBC
data-ciphers AES-256-CBC
comp-lzo
verb 3
reneg-sec 36000
auth-user-pass

Hi,
On Fri, Mar 24, 2023 at 03:30:02AM -0700, Yan Zarytovsky wrote:

What am I doing wrong?

Your config has 'comp-lzo' in it.  Compression is incompatible with DCO,
so remove that (on client and server!) and you can use DCO.
gert
"If was one thing all people took for granted, was conviction that if you
feed honest figures into a computer, honest figures come out. Never doubted
it myself till I met a computer with a sense of humor."
Robert A. Heinlein, The Moon is a Harsh Mistress
Gert Doering - Munich, Germany                             @.***

Excuse me. I didn't pay attention to the
Note: '--allow-compression' is not set to 'no', disabling data channel offload
in the line above . Thanks


Facebook OAuth failing

Facebook attestations in the DApp are currently failing as reported in #328.
The app is currently doing the OAuth handshake using client id=179007166076828 (the one @nick initially setup then deleted) instead of<PHONE_NUMBER>53956 as defined in EnvKey. @tomlinton any idea why this variable isn't getting passed through correctly?

In the Heroku setup a bunch of environment variables (Settings/Reveal Config Vars in the Heroku dashboard) are defined in addition to EnvKey. The environment variables are processed after EnvKey so they'd overwrite them (in the new production setup I'm building we are strictly EnvKey for the bridge settings). I nuked the Facebook settings in Heroku and restarted the bridge dyno so<PHONE_NUMBER>53956 is now passed correctly.
Now we have this error from Facebook:
Can't Load URL: The domain of this URL isn't included in the app's domains. To be able to load this URL, add all domains and subdomains of your app to the App Domains field in your app settings.
@joshfraser do you have access to the Facebook app settings to update that?

Aha! Updated and seems to be working again. Thanks @tomlinton!


Typed array assignment fails on unambiguous case

Tested versions
v4.3.dev.custom_build [a7b860250]
System information
linux
Issue description
var untyped: Array = PackedStringArray() # works
var typed: Array[String] = PackedStringArray() # doesn't work

I think it should work, we know it's all strings.
Steps to reproduce
see above
Minimal reproduction project (MRP)
any

See also:

https://github.com/godotengine/godot-proposals/discussions/7364

The broader specifics of typed arrays is still under evaluation and development

Same core issue as #91048, Packed Arrays do not coerce to typed arrays, only to Array.


NIFI-4290: Ensure that the InFlightMessageTracker is instantiated whe…

…n getTracker() is called
Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[ ] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[ ] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[ ] Has your PR been rebased against the latest commit within the target branch (typically master)?

[ ] Is your initial contribution a single, squashed commit?

For code changes:

[ ] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[ ] Have you written or updated unit tests to verify your changes?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.

Reviewing...

@markap14 LGTM +1. I was able to reproduce the NPE with a schema name which doesn't exist in schema registry. Then confirmed that with this fix, it can show the appropriate error message instead of NPE. Merging into master. Thanks!

NiFi flow template I used for testing is available here:
https://gist.github.com/ijokarumawak/6f16e6ffdafc00a514a826884eb3a17a


dbt build

resolves #2743
Description
Adds a dbt build command that does "all the things" for a given project.  More specifically:

models invoke logic from dbt run
tests invoke logic from dbt test
seeds invoke logic from dbt seed
snapshots invoke logic from dbt snapshot

This is all handled in dependency order.  Test failures block further downstream processing.
Checklist

[x] I have signed the CLA
[x] I have run this code in development and it appears to resolve the stated issue
[x] This PR includes tests, or tests are not required/relevant for this PR
[ ] I have updated the CHANGELOG.md and added information about my change to the "dbt next" section.

Do we have an integration test that hits all the types with the build command?

Do we have an integration test that hits all the types with the build command?

We do now :)


RequirementMachine: Disable merged associated types by default

This feature allows the following construct to work:
protocol P1 {
  associatedtype T : P1
}

protocol P2 {
  associatedtype T : P2
}

func foo<T : P1 & P2>(_: T) {}

However, I haven't figured out how to make it work with rewrite system minimization, so it's already disabled when you use the requirement machine for protocol or generic signature minimization. In addition to that it adds some complexity.
I haven't found any real-world uses of this pattern yet, so I'm going to try to turn it off, and if nobody complains, remove the support altogether.
If people do complain, we'll have to figure out how to make it work with minimization.

@swift-ci Please test source compatibility

@swift-ci Please smoke test


Bottom Navigation Bar

Describe the bug
When I open a link from another app the bottom navigation bar is unresponsive and is also shown at the top. The navigation bar at the top works fine but covers content from the webpage. This started happening with the recent big update.
I have the bottom navigation bar activated in the settings.
Expected behavior
There should only be one navigation bar.
Screenshots

Smartphone (please complete the following information):

Device: Pixel 7
Android Version : 13
Kiwi Browser Version: 116.0.5845.72

Same issue here!

Every tab switcher mode seems to have some problem when bottom navigation bar is enabled.

Same issue here, and I hadn't thought about that, but indeed it may be related, as all the examples that I've seen regarding this issue have been with the bottom bar enabled.

I also have the same issue.
Description
When opening a link from another app, in webview mode, 2 toolbars are visible. Only the top one works.
Reproduce

Activate bottom toolbar
Go to YouTube app and click on any video with links in the description
Click on one of the links

Expected behavior
Only the bottom toolbar should be active.
Screenshot

I'm stuck with the same issue and the development team didn't fix it in the latest version either