cutter: 2.1.0 -> 2.1.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/rizinorg/cutter/releases.
meta.description for cutter is: "Free and Open Source Reverse Engineering Platform powered by rizin"
meta.homepage for cutter is: "https://github.com/rizinorg/cutter"
meta.changelog for cutter is: ""
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.1.1 with grep in /nix/store/0m525y82w3jr630b8xkqk5zw5l5r6i81-cutter-2.1.1
found 2.1.1 in filename of file in /nix/store/0m525y82w3jr630b8xkqk5zw5l5r6i81-cutter-2.1.1

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
cutter

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/0m525y82w3jr630b8xkqk5zw5l5r6i81-cutter-2.1.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/0m525y82w3jr630b8xkqk5zw5l5r6i81-cutter-2.1.1
ls -la /nix/store/0m525y82w3jr630b8xkqk5zw5l5r6i81-cutter-2.1.1/bin

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

1 package built:

cutter (radare2-cutter)

Maintainer pings
cc @Mic92 @dtzWill for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/rizinorg/cutter/releases.
meta.description for cutter is: "Free and Open Source Reverse Engineering Platform powered by rizin"
meta.homepage for cutter is: "https://github.com/rizinorg/cutter"
meta.changelog for cutter is: ""
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.1.2 with grep in /nix/store/h0z5dbdsxjkj8dva7zzrbcjrsiwqnr16-cutter-2.1.2
found 2.1.2 in filename of file in /nix/store/h0z5dbdsxjkj8dva7zzrbcjrsiwqnr16-cutter-2.1.2

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
cutter

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/h0z5dbdsxjkj8dva7zzrbcjrsiwqnr16-cutter-2.1.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/h0z5dbdsxjkj8dva7zzrbcjrsiwqnr16-cutter-2.1.2
ls -la /nix/store/h0z5dbdsxjkj8dva7zzrbcjrsiwqnr16-cutter-2.1.2/bin

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

1 package built:

cutter (radare2-cutter)

Maintainer pings
cc @Mic92 @dtzWill for testing.


fix(schedules): handle invalid week value

:tada: This PR is included in version 1.5.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Refactor config-generator to generate yaml

The config-generator artifact currently processes user .yaml configuration files and generates the Infinispan server configuration in .xml.
ISPN-12618 adds yaml parsing support to the server. Therefore, we should refactor config-generator to output the server's configuration as a .yaml file.
The advantage of this approach is that it allows the image to support additional server configuration options without having to implement yaml->xml transformations in config-generator.

Closing as won't do. The config-generator has been deprecated in 13.x. Users who require yaml configuration should configure the server directly using a mounted yaml file: https://github.com/infinispan/infinispan-images#server-configuration


Add support to generate SAS URI for entire containers

We are using this as a dependency in Yammer's fork of hashicorp/vault which includes support for Azure Blob Storage SAS URI generation (I'll send them a PR once I get the OSS approval)
Slightly modifies GetBlobSASURI behavior to generate a URI for the entire container instead of just a single blob, if blob name isn't specified.
-- Rao Li<EMAIL_ADDRESS>

Hi @lirao, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla.microsoft.com.

TTYL, MSBOT;

Hi @lirao, please join the Microsoft Github org to avoid getting the CLA warning, or else you'll have to sign for us to move forward here

Joined, how do I get the bot to verify me?

@msftclas Could you take another look?

I'm going to close and re-open to attempt to get @msftclas to take another look.

Hi @lirao, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

It looks like you're a Microsoft contributor. If you're full-time or an intern, we DON'T require a Contribution License Agreement. If you are a vendor, please DO sign the electronic Contribution License Agreement. It will take 2 minutes and there's no faxing! https://cla.microsoft.com.

TTYL, MSBOT;

Looks like there is a missing function pathForContainer() From CI:

storage/blob.go:1023: undefined: pathForContainer
FAIL	github.com/Azure/azure-sdk-for-go/storage [build failed]

Wow looks like there was a major refactor today, I'll rebase/merge it


Configure port without hardware offload option in case of virtio-net (lagopus-0.1).

Currently rte_eth_tx_queue_setup() trying configure queue with hardware
offload option as default. lagopus failed to configure virtio tx queue at
rte_eth_tx_queue_setup(), because virtio does not support hardware offload
and virtio assumes given port supports hardware offload feature.
This fix adds ETH_TXQ_FLAGS_NOOFFLOADS option to rte_eth_tx_queue_setup()'s
arguments of virtio configuration explicitly.

This patch is for Lagopus 0.1
For lagopus-0.2, please see https://github.com/lagopus/lagopus/pull/46

This is deprecated, so it is closed.


Added metadata for packaging

:tada: This PR is included in version 1.0.0-dev.1 :tada:
The release is available on:

GitHub release
v1.0.0-dev.1
v1.0.0-dev.1

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

GitHub release
v1.0.0
v1.0.0

Your semantic-release bot :package::rocket:


Store Locator - Remove the copy text on the right

In figma we do not have the copy on the right next to Store Locator Title.
Make the Store Locator title as 1 line

in figma :

Updated


502 Bad Gateway on 3.2.2

Upgrading to 3.2.2 results in a Bad Gateway on any request that uses Laravel Data, other requests are returned as expected. Downgrading to 3.2.1 resolves the issue.
How can I help troubleshoot this? I don't see anything in laravel.log related to this.

Do you have a circular dependency within your data objects and are you running including, excluding, except or only operations on these objects?

I've reverted this in 3.3.3, we'll need another look at this solution before we can use it.

@rubenvanassche thanks, if you are unable to reproduce this I will take the time to setup a project to see if I can track down how this is happening in my use case.

I'm going to work on it within an hour, I think I know what the problem is because I've rewritten the original PR. But if I can't reproduce it then I'll certainly ping you, thanks!

New version tagged which should fix everything


Host resolution not changing.

 BackgroundJob   Running       True            localhost            ...
3      ResolutionMa... BackgroundJob   Running       True            localhost            ...
Waiting for the next event to be called... (for starting/ending stream)
Processing event: Start
Setting screen resolution to 1920 x 1200 x 90
Request to terminate has been processed, script will now revert resolution.
Setting screen resolution to 2560 x 1440 x 144
Resolution changed successfully.

Windows PowerShell transcript end
End time:<PHONE_NUMBER>0355

I created a custom resolution for 1920x1200x90 in nvidia settings and set it in the overrides.txt
The overrides.txt:
1280x800x90=1920x1200x90 # For Steam Deck users, typically if the user has a 4k screen this resolution is supported and will auto swap aspect ratios for them.

You'll have to use CRU if NVIDIA Control panel fails to work

Got it. I'll update after using CRU


[FLINK-28013] Shade all netty dependencies in sql jar

Shade all netty dependencies to resolve java.lang.NoClassDefFoundError: org/apache/flink/hbase/shaded/io/netty/channel/EventLoopGroup.

@MartijnVisser PTAL

@whhe The connector actually shouldn't rely on flink-shaded at all.

It will not depend on 'flink-shaded', this modification is to add netty packages other than 'netty-all', such as 'netty-transport' here, to the sql jar.

this modification is to add netty packages other than 'netty-all', such as 'netty-transport' here, to the sql jar.

Ah sorry, I misread. I'll try to have a look later today

Any progress?  @MartijnVisser

Hello again @MartijnVisser, please take a look on this pr if you are available. It wouldn't take a long time.


iterate behavior mixins in reverse order as the hasOwnProperty chec…

…k means whoever goes first wins

@cdata

This PR is faulty, don't merge until I can fix it.

Rebuilt this PR to actually do what it claims. Also added repairs for hostAttributes overriding and better tests. Note the test throws a warning in the console on purpose.

Merged!


Spellchecking for target names

It would be cool if ninja would do simple 1-edit-distance spell checking of target names, like so:
$ ninja fo.o
ninja: error: unknown target 'fo.o', did you mean 'foo.o'?

I tried to send out a pull request that adds an EditDistance() function which can be used for this issue: https://github.com/martine/ninja/pull/130

https://github.com/martine/ninja/pull/132


Improve the workflomics visualisation of the metrics

the current visualization presents the metrics as 2 independent values:

Proposed improvements:

[ ] Group the 2 values together
[ ] Rename Pubmetric to a more descriptive metric name (e.g., co-citations)

The OS compatibility should also be grouped together I think. Maybe just with a thin horizontal line between categories?

@magnuspalmblad I agree. I added the issue under Workflomics front-end (see https://github.com/Workflomics/workflomics-frontend/issues/80) as it was not pubmetric-specific.


Feature/source ads

Add the ability to use Atmosphere data store in addition to the climate data store. (https://github.com/ecmwf/earthkit-data/issues/141)
Mostly copied from climetlab. The two APIs are almost identical save for having different endpoints and needing different authentication tokens.
The only change I made is a slight refactor to cds.py::CdsRetriever that allows us to subclass it for the AdsRetrriever rather than copying all that identical code. I also added some tests that I copied and adapted from tests/sources/test_cds.py
Let me know if there are any additional changes you'd like to see before merging this into earthkit. For instance CDSAPIKeyPrompt and ADSAPIKeyPrompt are also basically identical so could be merged if it seems worth it.

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

The unit-tests fail because of #143

Hi @TomHodson, please merge the latest develop into your branch to fix the failing test.


iOS app: Going back from first view often times breaks the UI

Often times, when I start the Raindrop.io app freshly and try to go to the main view (either by swiping right or using the arrow button in the top-left corner), the UI gets totally broken and I can’t interact with the app anymore (no button is working and most of the UI seems to be cramped into the top-left corner?).
Example:

This has been happening for a few weeks already, at least.
I am using an iPhone 12 Mini with iOS 18.1.1, if it matters.

Looks like this has been resolved in version 5.1.41 now! 🎉


[Feature request] Support for ahxt/llama2_xs_460M_experimental model

Support for ahxt/llama2_xs_460M_experimental model
This text-generation model is based on llama2 and uses the gpt2 tokenizer. I think it would be a great addition to the models we can run with transformers.js.
Model on HF: https://huggingface.co/ahxt/llama2_xs_460M_experimental
I've converted it with Optimum v1.14.0 and uploaded it here in case someone wants to try making it work.
Reason for request
The quantized version is small enough to run in desktop browsers, and it has reasonable outputs. It's trained on the RedPajama dataset.

Hi there 👋 Thanks for converting and contributing the model! 🤗 The issue seems to be in models.js, where the current version only supports multi head attention (and not grouped query attention; see below):
https://github.com/xenova/transformers.js/blob/c98073042f39d77eed9d52dab0e4a6c20ba3101a/src/models.js#L3038-L3040
should be
this.num_heads = this.config.num_key_value_heads ?? this.config.num_attention_heads
this.num_layers = this.config.num_hidden_layers
this.dim_kv = this.config.hidden_size / this.config.num_attention_heads

From the transformers codebase:

num_key_value_heads (int, optional):
This is the number of key_value heads that should be used to implement Grouped Query Attention. If
num_key_value_heads=num_attention_heads, the model will use Multi Head Attention (MHA), if
`num_key_value_heads=1 the model will use Multi Query Attention (MQA) otherwise GQA is used.

If you can test that locally, and it works, would you like to submit a PR to fix this? :)
Here's some sample code to help test (adapted from here):
import { AutoModelForCausalLM, AutoTokenizer } from '@xenova/transformers'

const model_path = 'Felladrin/onnx-int8-llama2_xs_460M_experimental'

const model = await AutoModelForCausalLM.from_pretrained(model_path)
const tokenizer = await AutoTokenizer.from_pretrained(model_path)

const prompt = 'Once upon a time,'
const input_ids = tokenizer(prompt).input_ids
const tokens = await model.generate(input_ids, { max_length: 20 })
console.log(tokenizer.decode(tokens[0], { skip_special_tokens: true }))

Happy to help! I'll try it as soon as I can. Thanks for showing me the way!

Great news! Got some time to test it today and it worked like a charm! 🎉
import { AutoModelForCausalLM, AutoTokenizer } from "http://localhost:8080/dist/transformers.js";
const model_path = "Felladrin/onnx-int8-llama2_xs_460M_experimental";
const model = await AutoModelForCausalLM.from_pretrained(model_path);
const tokenizer = await AutoTokenizer.from_pretrained(model_path);
const prompt = "Q: What is the largest bird?\nA:";
const input_ids = tokenizer(prompt).input_ids;
const tokens = await model.generate(input_ids, { max_length: 20 });
console.log(tokenizer.decode(tokens[0], { skip_special_tokens: true }));

Once upon a time,:

"Girafatron is obsessed with giraffes, the most glorious animal on the face of this Earth. Giraftron believes all other animals are irrelevant when compared to the glorious majesty of the giraffe.\nDaniel: Hello, Girafatron!\nGirafatron:" [1] 😆

It's also working fine through pipeline!
pipeline("text-generation", "Felladrin/onnx-int8-llama2_xs_460M_experimental")

Gonna open a PR with the two changed lines!


EnvironmentVariableCollection API enhancements

This issue tracks the overall improvements for the upcoming API improvements so they're all in one place:

https://github.com/microsoft/vscode/issues/179476
https://github.com/microsoft/vscode/issues/171173
https://github.com/microsoft/vscode/issues/171108

We don't currently have a proposal for the first issue but the combined proposal for the other two is currently:
export interface EnvironmentVariableMutator {
	readonly type: EnvironmentVariableMutatorType;
	readonly value: string;
	readonly scope: EnvironmentVariableScope | undefined;
}

export interface EnvironmentVariableCollection extends Iterable<[variable: string, mutator: EnvironmentVariableMutator]> {
	/**
	 * Sets a description for the environment variable collection, this will be used to describe the changes in the UI.
	 * @param description A description for the environment variable collection.
	 * @param scope The scope to which this description applies to. If unspecified, operation applies to all
	 * workspace folders.
	 */
	setDescription(description: string | MarkdownString | undefined, scope?: EnvironmentVariableScope): void;

	replace(variable: string, value: string, scope?: EnvironmentVariableScope): void;
	append(variable: string, value: string, scope?: EnvironmentVariableScope): void;
	prepend(variable: string, value: string, scope?: EnvironmentVariableScope): void;
	get(variable: string, scope?: EnvironmentVariableScope): EnvironmentVariableMutator | undefined;
	delete(variable: string, scope?: EnvironmentVariableScope): void;
	clear(scope?: EnvironmentVariableScope): void;
}

export type EnvironmentVariableScope = {
	/**
	* The workspace folder to which this collection applies to. If unspecified, collection applies to all workspace folders.
	*/
	workspaceFolder?: WorkspaceFolder;
};

I have given feedback about scope being everywhere and maybe we should have a getScopedEnvironmentVariableCollection API on ExtensionContext instead of peppering it everywhere.

Alternative proposal:
export interface ExtensionContext {
    /**
     * Gets the extension's environment variable collection for this workspace, enabling changes
     * to be applied to terminal environment variables.
     *
     * @param scope The scope to which the environment variable collection applies to.
     */
    getEnvironmentVariableCollection(scope?: EnvironmentVariableScope): EnvironmentVariableCollection;
}

export type EnvironmentVariableScope = {
	/**
	* The workspace folder to which this collection applies to. If unspecified, collection applies to all workspace folders.
	*/
	workspaceFolder?: WorkspaceFolder;
};

export interface EnvironmentVariableCollection extends Iterable<[variable: string, mutator: EnvironmentVariableMutator]> {
	/**
	 * A description for the environment variable collection, this will be used to describe the
	 * changes in the UI.
	 */
	description: string | MarkdownString | undefined;
}

Note the following already exists, so we'll be duplicating APIs, in cases where scope is not required:
export interface ExtensionContext {
    /**
     * Gets the extension's environment variable collection for this workspace, enabling changes
     * to be applied to terminal environment variables.
     */
    readonly environmentVariableCollection: EnvironmentVariableCollection;
}

Another thing to keep in mind is In the future we may also be adding options parameter to .replace() API.

Comments/open questions:

readonly scope: EnvironmentVariableScope | undefined;

This instead?
readonly scope?: EnvironmentVariableScope

getEnvironmentVariableCollection(scope?: EnvironmentVariableScope): EnvironmentVariableCollection;

Do we need some way to enumerate and delete collections?

getEnvironmentVariableCollection(scope?: EnvironmentVariableScope): EnvironmentVariableCollection;

My preference if we go this route:
getScopedEnvironmentVariableCollection(scope: EnvironmentVariableScope): EnvironmentVariableCollection;

export interface EnvironmentVariableCollection extends Iterable<[variable: string, mutator: EnvironmentVariableMutator]> {
	/**
	 * A description for the environment variable collection, this will be used to describe the
	 * changes in the UI.
	 */
	description: string | MarkdownString | undefined;
}

Do we need a note here about only taking the first line of the description?

Feedback from API sync:

Workspace scope

How does the default and scoped collections interact? @karrtikr and I chatted about this; they are completely separate objects and are both applied, similar to how 2 extension collections both apply. We need to make sure this is explained well in the jsdoc
getScopedEnvironmentVariableCollection should live under EnvironmentVariableCollection, maybe as getScoped?
We can use EnvironmentVariableCollection & { getScoped(workspace) } as the type, or Exclude<EnvironmentVariableCollection, 'getScoped'>. Whatever way is preferred in the future API sync
Still not sure if we need a way to get all scoped collections and/or delete them, let's assume no for now as an extension can always do getScoped(workspace).clear()

Description

Let's finalize the description property 🚀

Closing in favor of https://github.com/microsoft/vscode/issues/171173 as the other proposal is finalized.


Inferred array type allows unsound covariance?

The following code should raise an error, but doesn't:
Try Flow
const a = [1];

function foo(arr: (number|string)[]) {
    arr.push("x");
}
foo(a);

function bar(arr: number[]) { }
bar(a);

This problem seems to be specific to arrays. If I replace all T[] with {x: T}, then I get the expected behavior.
Flow version: v0.146.0
Expected behavior
Either an error on foo(a), or an error on bar(a). If a is inferred to be number[], then foo(a) should be an error. If it's inferred to be (number|string)[], then bar(a) should be an error.
Actual behavior
When the type of the array is left off (inferred), it seems to produce unsound results. When the type is explicitly specified I get the expected results.

It works as expected though when declaring the variable type explicitly.
const a = [1];
const b: number[] = [1];

function foo(arr: (number|string)[]) {
    arr.push("x");
}

foo(a); // no error
foo(b); // error

Yes, I guess it’s a bug with the inference behavior.

Seems like the same thing as in #8108 and #8593

I agree—thanks for linking these. I think my repro case is a bit simpler since only primitive types are used 🙂


Support for new OTG node in KNE topology

Fixes https://github.com/google/kne/issues/139
This is yet another PR with squashed commits.
I have closed all existing PRs for OTG node refactor in favor of this.
I haven't deleted otg-refactor branch yet; will do so once this PR is merged.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

15 of 356 (4.21%)  changed or added relevant lines in 3 files are covered.
5 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-3.8%) to 54.319%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

topo/node/node.go
0
52
0.0%

topo/topo.go
11
95
11.58%

topo/node/ixia/ixia.go
4
209
1.91%

Files with Coverage Reduction
New Missed Lines
%

topo/node/ixia/ixia.go
1
9.09%

topo/topo.go
4
41.0%

Totals

Change from base Build<PHONE_NUMBER>:
-3.8%

Covered Lines:
1893

Relevant Lines:
3485

💛  - Coveralls

i am seeing the following
INFO[0000] Getting interfaces for ixia node resource otg ...
INFO[0000] Creating new ixia CRD for node: otg
INFO[0000] Creating custom resource for ixia (desiredState=INITIATED) ...
Error: could not get meshnet topologies: could not fetch topology specs for node otg: could not create custom resource for ixia: the server could not find the requested resource (post Ixiatgs)
versions:
ixia-c-operator:0.1.77
{
  "release": "0.0.1-9999",
  "images": [
    {
      "name": "controller",
      "tag": "0.0.1-2790"
    },
    {
      "name": "gnmi-server",
      "tag": "1.7.15"
    },
    {
      "name": "grpc-server",
      "tag": "0.7.8"
    },
    {
      "name": "traffic-engine",
      "tag": "<IP_ADDRESS>"
    },
    {
      "name": "protocol-engine",
      "tag": "<IP_ADDRESS>"
    }
  ]
}

@marcushines Please use v0.1.89 (publicly released): https://github.com/open-traffic-generator/ixia-c-operator/releases/download/v0.1.89/ixiatg-operator.yaml
0.1.77 won't work because as mentioned in the email I had sent, we explicitly changed the API version from v1alpha1 to v1beta1 (so KNE raises explicit failure instead of silently failing, when working with ixia-c-operator from 0.0.x branch).
P.S. All 0.1.x builds older than v0.1.89 provided were internal builds and shall be removed from repository.

tested with both 0.80 operator and 1.89 operator


Provide a way to fetch whether a ShaderType is runtime sized or not

It's currently not possible to check if a type T: ShaderType is runtime sized or not. This makes it difficult, in generic code, to tell if one can assume that the T::min_size can be used to accurately estimate how large a preallocated buffer needs to be to fit N elements of T. This mandates the use of dynamic allocation
The motivation here is to support use cases that directly use  wgpu::Queue::write_buffer_with to avoid extra copies, but it requires a preallocated non-expandable buffer. To preallocate, a maximum capacity for the buffer must be known, and this requires summing the size of all elements (padding for alignment), or computing the capacity assuming the size is fixed. This is doable in non-generic contexts where we know a type is not runtime sized, but not possible in generic contexts without T::is_runtime_sized or something similar.

I see that ShaderSize provides this functionality, but without specialization this isn't very usable in generic contexts.

Wouldn't https://docs.rs/encase/latest/encase/trait.CalculateSizeFor.html work for your usecase?
Although I imagine it would be tricky to use in a generic context since it's only implemented for runtime-sized arrays.
ShaderType::max_size(nr_of_el) sounds like something that would be nice to have but I don't know how it should behave for things that are not runtime-sized arrays. Does it just ignore the arg?


Doesn't stop on breakpoins

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

VS Code Version:  1.70.2 (Universal)
OS Version: MacOS (M1)
Python Extension Version: v2022.12.1
Pylance Extension Version: v2022.8.40
Python Version: 3.10

Steps to Reproduce:

Open the django project.
Create lunch.json file for django
Run the debugger.
Keep breakpoins

Does't stop in Breakpoint. I have tried everything and here to report expecting i will get any help from here.

/extPython

It looks like this is caused by the Python extension. Please file the issue to the Python extension repository. Make sure to check their issue reporting template and provide them relevant information such as the extension version you're using. See also our issue reporting guidelines for more information.
Happy Coding!


Update README.md

@arshidkv12 The CI failed, please execute make lint.

@arshidkv12 Hi, It seems this project is just hello world demo for write PHP extension in Zig, not a web framework, maybe you can put it under FFI

Thank you


feat(compiler-core): support Error in template

Related to #7015

console was requested in the past but it was decided not to be added. I can’t find the issue now. Maybe it was in vue repo and not in core?

The only use case would be passing Error() as a parameter but then we would also have to support the Promise global (@znck said offline)
Whatever direction this take, at least we will have a reference issue for future feature requests

since vue3 , vue 's error message for template, the source position  incorrect, bad experience

Related #9069

@posva It looks like this PR has been mangled by changes elsewhere. The file globalsWhitelist.ts has been renamed to globalAllowList.ts, which is likely why the unit test is failing on the CI.

@skirtles-code It should be good now!


TfLiteInferenceCalculator failed to load model.

 I tried to load my custom model with TfliteInferenceCalculator. It gave following error:
IrisTrackingGpuApp[1840:609884] The model is not a valid Flatbuffer buffer. I passed the path of a tflite model and I am working with latest mediapipe .

Hi @shivambhardwaj120, Could you please provide steps to reproduce the above error. Thanks!

Hi @sgowroji,  I changed  a lot of things in the subgraph of iris tracking subgraph, I am not sure,  you can reproduce it directly. Subgraph takes a GPU image as input, resize it to (224,224,3), make it a cpu image, passes it to "TfLiteConverterCalculator" and then to
node {
calculator: "TfLiteInferenceCalculator"
input_stream: "TENSORS:right_image_tensor"
output_stream: "TENSORS:right_detection_tensors"
node_options: {
[type.googleapis.com/mediapipe.TfLiteInferenceCalculatorOptions] {
model_path: "mediapipe/models/custom.tflite"
}
}
}

@shivambhardwaj120 there's a chance that your model is not available at the path you provided, try to look what you need to do make sure your iOS has custom.tflite model.
For example for iris demo models are ensured by including them into "data": https://github.com/google/mediapipe/blob/master/mediapipe/examples/ios/iristrackinggpu/BUILD#L66-L67

Hi @shivambhardwaj120, Could you please verify the issue w.r.t the above comment. Thanks!

Hi @gkarpiak,  you were right, I didn't know that I need to update the path to IristrackinggpuApp build as well. I updated only the subgraph of iristracking graph and build of model folder. Thanks @gkarpiak @sgowroji for the help.


Implement OpenOrdersAccount deserialization and fix things in SerumClient

Status
Type
⚠ Core Change
Issue

Ready
Features/Refactor
Yes
Closes #8

Problem
Needs bump to Solnetv0.3.2
No decoding for Open Orders Account data
There was an issue in the GetTokens where it was hitting the same GitHub file as GetMarkets
Solution
Bumped Solnet to v0.3.2 to include the newest GetProgramAccounts and bandwidth metrics on streaming client
Implemented OpenOrdersAccount, GetOpenOrdersAccount and SubscribeOpenOrdersAccount
Change the way the Actions are raised to more easily distinguish between EQ/OOA/other subscriptions

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

51 of 91 (56.04%)  changed or added relevant lines in 6 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+0.8%) to 61.493%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

Solnet.Serum/Models/EventQueue.cs
3
6
50.0%

Solnet.Serum/SerumClient.cs
8
45
17.78%

Files with Coverage Reduction
New Missed Lines
%

Solnet.Serum/SerumClient.cs
1
39.6%

Totals

Change from base Build 997158782:
0.8%

Covered Lines:
183

Relevant Lines:
283

💛  - Coveralls


Add the ability to manage replication in ADS

There is currently no support for replication (transactional, merge or snapshot) in ADS.  It would be useful for those using replication to be able to add, remove and configure publishers and subscribers as well as monitor the synchronisation.

I believe this is regarding SQL Server Replication
cc @erinstellato-ms

I get this is a big new feature but ids there any movement on this?

Hi @alleycat58uk - there is no movement on this feature, and it's not on our current roadmap.  We are currently focused on completing core operational experiences with an Azure focus.  Azure SQL Database only supports replication as a push subscriber (one way), so this is a lower priority and will remain on our backlog for now.


Add applicationId and assessmentId to Placement Request responses

Record which assessment was used to create a Placement Request
Return the applicationId and assessmentId with Placement Request response bodies

 Add an applicationId and assessmentID to a placement request response


Added support for scissor testing.

This is a subset of #846 and implements a part of #1.
Test with:
#include <SFML/Graphics.hpp>

int main()
{
    sf::RenderWindow window(sf::VideoMode(200, 200), "Test");

    sf::CircleShape shape(100.f);
    shape.setFillColor(sf::Color::Green);

    sf::View left = window.getView();
    left.setScissor(sf::FloatRect(0, 0, 0.5, 1));

    sf::View right = window.getView();
    right.setScissor(sf::FloatRect(0.5, 0, 0.5, 1));

    while (window.isOpen())
    {
        sf::Event event;
        while (window.pollEvent(event))
        {
            if (event.type == sf::Event::Closed)
                window.close();
        }

        window.setView(window.getDefaultView());
        window.clear();

        window.setView(left);
        window.clear(sf::Color::Red);

        window.setView(right);
        window.draw(shape);

        window.display();
    }
}

Updated to current master.

Updated to current master and added tests.

Fixed.

Updated.

It doesn't work well in interaction with sf::Font.
See the result of the following code:
#include <SFML/Graphics.hpp>

int main()
{
    auto target = sf::RenderTexture{};
    if (!target.create({400, 300}))
        return 1;

    auto font = sf::Font{};
    // https://github.com/SFML/SFML/raw/master/test/Graphics/tuffy.ttf
    if (!font.loadFromFile("tuffy.ttf"))
        return 1;

    auto text = sf::Text{font, "0123456789ABCDEFGHIJKLMNOPQ", 30};
    text.setFillColor(sf::Color::White);
    text.setPosition({0.f, 100.f});

    target.clear(sf::Color{64, 64, 64});

    auto scissorView = target.getDefaultView();
    scissorView.setScissor({{0.1f, 0.1f}, {0.8f, 0.8f}});
    target.setView(scissorView);
    target.clear(sf::Color{128, 192, 128});
    target.draw(text);

    target.display();

    if (!target.getTexture().copyToImage().saveToFile("result.png"))
        return 1;

    return 0;
}

Below is the expected result, which I get after applying this patch (quick hack, probably not a proper solution).
diff --git a/src/SFML/Graphics/Texture.cpp b/src/SFML/Graphics/Texture.cpp
index 7c6df2e5..70b5286d 100644
--- a/src/SFML/Graphics/Texture.cpp
+++ b/src/SFML/Graphics/Texture.cpp
@@ -463,6 +463,8 @@ void Texture::update(const std::uint8_t* pixels, const Vector2u& size, const Vec
         // Make sure that the current texture binding will be preserved
         const priv::TextureSaver save;

+        glCheck(glDisable(GL_SCISSOR_TEST));
+
         // Copy pixels from the given array to the texture
         glCheck(glBindTexture(GL_TEXTURE_2D, m_texture));
         glCheck(glTexSubImage2D(GL_TEXTURE_2D,

Updated. Turns out scissor testing was having an affect on our texture copying when the FBO blit implementation is used.

Updated.

Updated.


Tooltip not visible in stacked column chart , when y-axis is reversed.

https://github.com/apexcharts/apexcharts.js/assets/98647697/a6ab4972-8048-436c-a8e2-7d4a89a01ea2
Description
We are using column chart (stacked)
having numeric values in y-axis
sometimes those values can be negative
according to which we
set the boolean value for y-axis in chart options  "reversed" : true/ false
if reversed is false
the chart works fine but
if reversed is true
then tooltip is not visible .
Steps to Reproduce

Create a column chart
Have a set of series data with negative values on Y-axis
Set the reversed options in y-axis to true
Set Tooltip enable option to true .
Check for the chart tooltip

Expected Behavior
It should show tooltip with y-axis value in the chart at the tip of the hovered bar
Actual Behavior
Tooltip is not visible
until or unless tooltip is fixed
(In fixing the tooltip there might be some difference between the tooltip height and hight of bars in column chart .)
Screenshots
attached a video
Reproduction Link
https://codesandbox.io/embed/cyqjy2?view=editor+%2B+preview&module=%2Fsrc%2Fcomponents%2FChart.component.vue

https://codesandbox.io/embed/cyqjy2?view=editor+%2B+preview&module=%2Fsrc%2Fcomponents%2FChart.component.vue
attaching screenshots of the code pen
pay attention to tooltip

Looks like ApexCharts is miscalculating the y coordinates or the tooltip when yaxis is reversed.

Possibly tooltip is overshooting the chart area and hence not visible.

Kindly check this issue in priority basis , as Its a major bug for a simple change in charts

Any fix for this ?

still facing issue ,
will this work in any upcoming npm updates ?


New charts url

Sorry, didn't mean to send that for PR. Though, happy to if you are interested. I recently found that the list was not working with the RSS links originally used, but charts was. I'm not completely sure of what their differences mean though.

I would love to take a look! Thanks for finding it; we disabled the charts on our application a while ago since the RSS stopped working.


Be able to maintain separate separate settings, keybindings, and snippet files, and include them with a directive

be able to define separate setting, keybinding, and snippet, module files:
// ~/.config/code/settings/commons.json
{
    "editor.insertSpaces": false,
    "editor.tabSize": 16,
    ...
}

// ~/.config/code/keybindings/commons.json
{
    ...
}

// ~/.config/code/snippets/python.json
{
    ...
}

and then be able to include them in other setting, keybinding, and snippet files, keeping everything clean and simple:
// settings.json
{
    "include": "~/.config/code/settings/commons.json"
    "include": "~/.config/code/settings/theme-base16.json",
    "include": "~/.config/code/settings/lang-python.json",
    "include": "~/.config/code/settings/lang-javascript.json",
    ...
}
// keybindings.json
{
    "include": "~/.config/code/keybindings/commons.json"
    ...
}
// snippets/python.json
{
    "include": "~/.config/code/snippets/python.json"
    ...
}

and then in some other profile setting, instead of copy pasting from one place to another, and having to go back and maintain 10 profiles, just include the setting modules I want for that specific profile, and just edit the separate modules and have everything automatically reflected throughout all setting profiles:
// settings.json (profile: school)
{
    "include": "~/.config/code/settings/commons.json"
    "include": "~/.config/code/settings/theme-monkai.json",
    "include": "~/.config/code/settings/lang-java.json",
    ...
}
// keybindings.json (profile: school)
{
    "include": "~/.config/code/keybindings/commons.json"
    ...
}
// snippets/java.json (profile: school)
{
    "include": "~/.config/code/snippets/java.json"
    ...
}

// settings.json (profile: work)
{
    "include": "~/.config/code/commons.json"
    "include": "~/.config/code/theme-one-dark.json",
    "include": "~/.config/code/lang-c.json",
    "include": "~/.config/code/lang-cpp.json",
}
...

you get the point

thousands of less sophisticated software has this ability, why can't we have this in vscode ?

/duplicate
Seems similar to https://github.com/microsoft/vscode/issues/156144

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.
Happy Coding!


Errors incorrectly detected when failures="0"

Consider the following xunit output:
<testsuite name="Testem Tests" tests="18" skipped="0" failures="0" timestamp="Mon Nov 08 2021 10:21:17 GMT+1100 (Australian Eastern Daylight Time)" time="8.652">
    <!-- Redacted -->
</testsuite>

This is being reported as an error, which I've traced to detection.sh line 19.
I noticed there's inconsistent usage of the -L option of grep. This is important because the -L option not only suppresses output (replacing it with the name of the file), but also inverts the match.
Interestingly, when I ran this locally on macOS to reproduce the issue, I couldn't reproduce it. However, I was able to reproduce it in Linux. It seems that grep -L always returns 0 on macOS, whereas it returns 1 on Linux when a match is found (i.e. opposite of what grep -l would do).
The pseudocode of this snippet:
if echo "$suite_line" | grep "failures=\"0\"";then
    if echo "$suite_line" | grep -L "errors=\"[1-9]\d*\"";then
        echo "Error found in $file: $suite_line"
        return 1
    else
        return 0
    fi
elif echo "$suite_line" | grep -L "errors=\"0\"";then
    if echo "$suite_line" | grep -L "failures=\"[1-9]\d*\"";then
        echo "Error found in $file: $suite_line"
        return 1
    else
        return 0
    fi
else
    echo "Failure found in $file: $suite_line"
    return 1
fi

appears to be the following:

If the test report contains failures="0", then

If the test report doesn't contain errors="1+", then one or more tests failed.
Otherwise, all tests passed.

Otherwise, if the test report doesn't contain errors="0", then

If the test report doesn't contain failures="1+", then one or more tests failed.
Otherwise, all tests passed.

Otherwise, one or more tests failed.

More concisely, failure occurs if one of the following is true:

The test report contains failures="0" and doesn't contain errors="1+";
The test report contains neither errors="0" nor failures="1+"; or
The test report doesn't contain failures="0" and does contain errors="0".

This is what I think is needed:

Fail if the test report contains failures="1+";
Fail if the test report contains errors="1+"; or
Fail if the test report is missing the failures attribute (could be a malformed test report).

In which case, find_fail should become:
find_fail() {
    target=$1
    file=$2
    suite_line=$(cat "$file" | grep "$target")

    if echo "$suite_line" | grep -q -E "failures=\"[1-9]\\d*\""; then
      echo "Failure(s) found in $file: $suite_line"
      return 1
    elif echo "$suite_line" | grep -q -E "errors=\"[1-9]\\d*\""; then
      echo "Error(s) found in $file: $suite_line"
      return 1
    elif echo "$suite_line" | grep -qv -E "failures=\"0\""; then
      echo "Test report may be malformed: No errors were detected, but the failures attribute is missing from the testsuite element."
      return 1
    fi
}

As a bonus, it also works on macOS.

I am also experiencing this issue since yesterday and would appreciate a fix.

Notice the action from a  clean branch of master shows tests failing.

Then merging branch #13 fixes the tests in this action.  It would seem something stopped working correctly without any code introduced.

@trittgers-principal @steve-taylor please see if v1 tag works now for your actions.  Close the issue if so or let me know what we need to do next.
v1 now points to the latest release that includes #13

Thanks for your contribution.

This works for me. Thanks!


[ISSUE] In the Alpha chart (8.6), tasklist fails to connect to external Elasticsearch

Describe the issue:

I set up Elastic Cloud on Google Cloud. I configured the Camunda chart to connect to the external Elasticsearch. I noticed that all relevant pods became healthy except tasklist.
To confirm that operate was working successfully and connected the external Elasticsearch, I deployed a model from the desktop modeler by connecting to the zeebe gateway ingress endpoint. I could then see the deployed model on Operate.
This confirms that there is no problem with the configuration related to the external elasticsearch but a problem related to tasklist itself.
Actual behavior:

Tasklist pod is unhealthy when connected to external Elasticsearch.
I also can't connect to the ingress endpoint. I get a 503 service unavailable error.
Expected behavior:

Tasklist pod is healthy and accessible.
How to reproduce:

values.yaml that I used:
global:
  elasticsearch:
    enabled: true
    external: true
    tls:
      enabled: true
    auth:
      username: elastic
      password: password
    disableExporter: false
    url:
      protocol: https
      host: "host"
      port: 443
elasticsearch:
  enabled: false

Logs:

pod logs for tasklist:
Standard Commons Logging discovery in action with spring-jcl: please remove commons-logging.jar from classpath in order to avoid potential conflicts

  _______ ___ ___ ___   _____ _   ___ _  ___    ___ ___ _____
 |_  / __| __| _ ) __| |_   _/_\ / __| |/ / |  |_ _/ __|_   _|
  / /| _|| _|| _ \ _|    | |/ _ \\__ \ ' <| |__ | |\__ \ | |
 /___|___|___|___/___|   |_/_/ \_\___/_|\_\____|___|___/ |_|

				       8.6.0-alpha5

2024-09-27 15:45:55.515 [] [main] [] INFO
      io.camunda.application.StandaloneTasklist - Starting StandaloneTasklist v8.6.0-alpha5 using Java 21.0.4 with PID 7 (/usr/local/tasklist/lib/camunda-zeebe-8.6.0-alpha5.jar started by camunda in /usr/local/tasklist)
2024-09-27 15:45:55.525 [] [main] [] INFO
      io.camunda.application.StandaloneTasklist - The following 3 profiles are active: "tasklist", "standalone", "identity-auth"
2024-09-27 15:46:01.853 [] [main] [] WARN
      org.springframework.context.support.PostProcessorRegistrationDelegate$BeanPostProcessorChecker - Bean 'io.camunda.tasklist.webapp.security.CustomMethodSecurityExpressionHandler' of type [io.camunda.tasklist.webapp.security.CustomMethodSecurityExpressionHandler] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected into a currently created BeanPostProcessor [meterRegistryPostProcessor]? Check the corresponding BeanPostProcessor declaration and its dependencies.
2024-09-27 15:46:01.915 [] [main] [] WARN
      org.springframework.context.support.PostProcessorRegistrationDelegate$BeanPostProcessorChecker - Bean 'io.camunda.tasklist.webapp.security.MethodSecurityConfig' of type [io.camunda.tasklist.webapp.security.MethodSecurityConfig$$SpringCGLIB$$0] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected into a currently created BeanPostProcessor [meterRegistryPostProcessor]? Check the corresponding BeanPostProcessor declaration and its dependencies.
2024-09-27 15:46:02.944 [] [main] [] INFO
      org.springframework.boot.web.embedded.tomcat.TomcatWebServer - Tomcat initialized with port 8080 (http)
2024-09-27 15:46:02.958 [] [main] [] INFO
      org.apache.coyote.http11.Http11NioProtocol - Initializing ProtocolHandler ["http-nio-<IP_ADDRESS>-8080"]
2024-09-27 15:46:03.019 [] [main] [] INFO
      org.apache.catalina.core.StandardService - Starting service [Tomcat]
2024-09-27 15:46:03.019 [] [main] [] INFO
      org.apache.catalina.core.StandardEngine - Starting Servlet engine: [Apache Tomcat/10.1.28]
2024-09-27 15:46:03.333 [] [main] [] INFO
      org.apache.catalina.core.ContainerBase.[Tomcat].[localhost].[/tasklist] - Initializing Spring embedded WebApplicationContext
2024-09-27 15:46:03.336 [] [main] [] INFO
      org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext - Root WebApplicationContext: initialization completed in 7684 ms
Standard Commons Logging discovery in action with spring-jcl: please remove commons-logging.jar from classpath in order to avoid potential conflicts
2024-09-27 15:46:03.458 [] [main] [] INFO
      org.hibernate.validator.internal.util.Version - HV000001: Hibernate Validator 8.0.1.Final
2024-09-27 15:46:04.222 [] [main] [] INFO
      graphql.kickstart.autoconfigure.annotations.GraphQLAnnotationsAutoConfiguration - Using GraphQL Annotations library to build the schema. Schema definition files will be ignored.
2024-09-27 15:46:04.224 [] [main] [] INFO
      graphql.kickstart.autoconfigure.annotations.GraphQLAnnotationsAutoConfiguration - GraphQL classes are searched in the following package (including subpackages): io.camunda.tasklist
2024-09-27 15:46:04.932 [] [main] [] INFO
      org.reflections.Reflections - Reflections took 695 ms to scan 10 urls, producing 205 keys and 934 values
2024-09-27 15:46:05.032 [] [main] [] INFO
      graphql.kickstart.autoconfigure.annotations.GraphQLAnnotationsAutoConfiguration - Registering query resolver class: class io.camunda.tasklist.webapp.graphql.resolvers.Queries
2024-09-27 15:46:05.033 [] [main] [] INFO
      graphql.kickstart.autoconfigure.annotations.GraphQLAnnotationsAutoConfiguration - Registering mutation resolver class: class io.camunda.tasklist.webapp.graphql.resolvers.Mutations
2024-09-27 15:46:05.035 [] [main] [] INFO
      graphql.kickstart.autoconfigure.annotations.GraphQLAnnotationsAutoConfiguration - Registering type extension class io.camunda.tasklist.webapp.graphql.extensions.TaskExtension
2024-09-27 15:46:05.036 [] [main] [] INFO
      graphql.kickstart.autoconfigure.annotations.GraphQLAnnotationsAutoConfiguration - Using default GraphQL Annotation processor.
2024-09-27 15:46:05.319 [] [main] [] INFO
      graphql.kickstart.autoconfigure.annotations.GraphQLScalarTypeFunction - Registering scalar type DateTime for Java class class java.time.OffsetDateTime
2024-09-27 15:46:05.320 [] [main] [] INFO
      graphql.kickstart.autoconfigure.annotations.GraphQLScalarTypeFunction - Registering scalar type DateTime for Java class class java.time.OffsetDateTime
2024-09-27 15:46:05.353 [] [main] [] INFO
      graphql.kickstart.autoconfigure.annotations.GraphQLScalarTypeFunction - Registering scalar type javaUtilDate for Java class class java.util.Date
2024-09-27 15:46:05.354 [] [main] [] INFO
      graphql.kickstart.autoconfigure.annotations.GraphQLScalarTypeFunction - Registering scalar type javaUtilDate for Java class class java.util.Date
2024-09-27 15:46:08.300 [] [main] [] WARN
      io.camunda.tasklist.es.ElasticsearchConnector - Elasticsearch cluster is not accessible
2024-09-27 15:46:09.233 [] [main] [] INFO
      graphql.kickstart.autoconfigure.web.servlet.GraphQLWebAutoConfiguration - Enabling cors filter
2024-09-27 15:46:10.118 [] [netty-messaging-event-epoll-server-0] [] INFO
      io.atomix.cluster.messaging.impl.NettyMessagingService - TCP server listening for connections on <IP_ADDRESS>:26502
2024-09-27 15:46:10.226 [] [netty-messaging-event-epoll-server-0] [] INFO
      io.atomix.cluster.messaging.impl.NettyMessagingService - Started messaging service bound to [<IP_ADDRESS>:26502], advertising <IP_ADDRESS>:26502, and using plaintext
2024-09-27 15:46:10.322 [] [netty-unicast-event-nio-client-0] [] INFO
      io.atomix.cluster.messaging.impl.NettyUnicastService - Started plaintext unicast service bound to <IP_ADDRESS>:26502, advertising <IP_ADDRESS>:26502
2024-09-27 15:46:10.323 [] [atomix-cluster-0] [] INFO
      io.atomix.cluster.discovery.BootstrapDiscoveryProvider - Local node Node{id=camunda-tasklist-697b6c78c8-6jzcs, address=<IP_ADDRESS>:26502} joined the bootstrap service
2024-09-27 15:46:10.354 [] [atomix-cluster-0] [] INFO
      io.atomix.cluster.protocol.swim - Started
2024-09-27 15:46:10.414 [] [atomix-cluster-0] [] INFO
      io.atomix.cluster.impl.DefaultClusterMembershipService - Started cluster membership service for member Member{id=camunda-tasklist-697b6c78c8-6jzcs, address=<IP_ADDRESS>:26502, properties={}}
2024-09-27 15:46:10.415 [] [atomix-cluster-0] [] INFO
      io.atomix.cluster.messaging.impl.DefaultClusterCommunicationService - Started
2024-09-27 15:46:10.417 [] [atomix-cluster-0] [] INFO
      io.atomix.cluster.messaging.impl.DefaultClusterEventService - Started
2024-09-27 15:46:10.560 [] [main] [] WARN
      io.camunda.service.license.CamundaLicense - No license detected when one is expected. Please provide a license through the CAMUNDA_LICENSE_KEY environment variable.
2024-09-27 15:46:11.319 [] [main] [] INFO
      io.camunda.tasklist.WebappModuleConfiguration - Starting module: webapp
2024-09-27 15:46:11.324 [] [main] [] INFO
      io.camunda.tasklist.zeebe.ZeebeConnector - Zeebe Client - Using REST Configuration: http://camunda-zeebe-gateway:8080/zeebe
2024-09-27 15:46:11.324 [] [main] [] INFO
      io.camunda.tasklist.zeebe.ZeebeConnector - Zeebe Client - Using Gateway Configuration: camunda-zeebe-gateway:26500
2024-09-27 15:46:11.329 [] [main] [] INFO
      io.camunda.tasklist.zeebe.ZeebeConnector - Use plaintext connection to zeebe
2024-09-27 15:46:12.217 [] [atomix-cluster-heartbeat-sender] [] INFO
      io.atomix.cluster.protocol.swim - camunda-tasklist-697b6c78c8-6jzcs - Member added Member{id=0, address=camunda-zeebe-0.camunda-zeebe:26502, properties={brokerInfo=EADJAAAABQAAAAAAAwAAAAMAAAADAAAAAAABCgAAAGNvbW1hbmRBcGkjAAAAY2FtdW5kYS16ZWViZS0wLmNhbXVuZGEtemVlYmU6MjY1MDEFAAMBAAAAAAIAAAAAAwAAAAAMAAMBAAAAAQAAAAAAAAACAAAAAQAAAAAAAAADAAAAAQAAAAAAAAAMAAAAOC42LjAtYWxwaGE1BQADAQAAAAECAAAAAQMAAAAB}}
2024-09-27 15:46:12.320 [] [main] [] INFO
      io.camunda.tasklist.schema.SchemaStartup - SchemaStartup started.
2024-09-27 15:46:12.320 [] [main] [] INFO
      io.camunda.tasklist.schema.SchemaStartup - SchemaStartup: validate index versions.
2024-09-27 15:46:12.526 [] [atomix-cluster-heartbeat-sender] [] INFO
      io.atomix.cluster.protocol.swim - camunda-tasklist-697b6c78c8-6jzcs - Member added Member{id=1, address=camunda-zeebe-1.camunda-zeebe:26502, properties={brokerInfo=EADJAAAABQABAAAAAwAAAAMAAAADAAAAAAABCgAAAGNvbW1hbmRBcGkjAAAAY2FtdW5kYS16ZWViZS0xLmNhbXVuZGEtemVlYmU6MjY1MDEFAAMBAAAAAQIAAAABAwAAAAEMAAAMAAAAOC42LjAtYWxwaGE1BQADAQAAAAECAAAAAQMAAAAB}}
2024-09-27 15:46:14.462 [] [atomix-cluster-heartbeat-sender] [] INFO
      io.atomix.cluster.protocol.swim - camunda-tasklist-697b6c78c8-6jzcs - Member added Member{id=camunda-zeebe-gateway-8477954dcb-9bl25, address=<IP_ADDRESS>:26502, properties={event-service-topics-subscribed=KIIDAGpvYnNBdmFpbGFibOU=}}
2024-09-27 15:46:15.715 [] [main] [] INFO
      io.camunda.tasklist.schema.SchemaStartup - SchemaStartup: validate index mappings.
2024-09-27 15:46:17.360 [] [atomix-cluster-heartbeat-sender] [] INFO
      io.atomix.cluster.protocol.swim - camunda-tasklist-697b6c78c8-6jzcs - Member added Member{id=2, address=camunda-zeebe-2.camunda-zeebe:26502, properties={brokerInfo=EADJAAAABQACAAAAAwAAAAMAAAADAAAAAAABCgAAAGNvbW1hbmRBcGkjAAAAY2FtdW5kYS16ZWViZS0yLmNhbXVuZGEtemVlYmU6MjY1MDEFAAMBAAAAAQIAAAABAwAAAAEMAAAMAAAAOC42LjAtYWxwaGE1BQADAQAAAAECAAAAAQMAAAAB}}
2024-09-27 15:46:17.579 [] [main] [] INFO
      io.camunda.tasklist.schema.SchemaStartup - SchemaStartup: schema won't be created, it either already exist, or schema creation is disabled in configuration.
2024-09-27 15:46:17.579 [] [main] [] INFO
      io.camunda.tasklist.schema.SchemaStartup - SchemaStartup finished.
2024-09-27 15:46:17.585 [] [main] [] INFO
      io.camunda.tasklist.ImportModuleConfiguration - Starting module: importer
2024-09-27 15:46:17.587 [] [main] [] INFO
      io.camunda.tasklist.ArchiverModuleConfiguration - Starting module: archiver
2024-09-27 15:46:17.637 [] [main] [] INFO
      io.camunda.tasklist.es.ILMPolicyUpdateElasticSearch - Removing ILM policy to all existent indices
2024-09-27 15:46:17.763 [] [main] [] INFO
      io.camunda.tasklist.webapp.StartupBean - INIT: DONE
2024-09-27 15:46:17.835 [] [atomix-cluster-heartbeat-sender] [] INFO
      io.atomix.cluster.protocol.swim - camunda-tasklist-697b6c78c8-6jzcs - Member added Member{id=camunda-operate-5f6bf5d4f5-c4q2k, address=<IP_ADDRESS>:26502, properties={event-service-topics-subscribed=KIIDAGpvYnNBdmFpbGFibOU=}}
2024-09-27 15:46:18.617 [] [grpc-default-worker-ELG-3-1] [] WARN
      io.camunda.zeebe.client.impl.ZeebeCallCredentials - The request's security level does not guarantee that the credentials will be confidential.
2024-09-27 15:46:18.926 [] [main] [] INFO
      io.camunda.tasklist.zeebeimport.RecordsReaderHolder - Starting import for partitions: [1, 2, 3]
2024-09-27 15:46:18.937 [] [main] [] INFO
      io.camunda.tasklist.zeebeimport.ImportPositionHolderAbstract - INIT: Start import position updater...
2024-09-27 15:46:19.388 [] [main] [] WARN
      io.camunda.tasklist.es.ElasticsearchConnector - Elasticsearch cluster is not accessible
2024-09-27 15:46:19.392 [] [main] [] INFO
      io.camunda.tasklist.zeebeimport.ZeebeImporter - INIT: Start importing data by '16' importers
2024-09-27 15:46:19.416 [] [main] [] INFO
      io.camunda.tasklist.archiver.ArchiverStarter - INIT: Start archiving data...
2024-09-27 15:46:19.417 [] [main] [] INFO
      io.camunda.tasklist.archiver.ArchiverStarter - Starting archiver for partitions: [1, 2, 3]
2024-09-27 15:46:20.718 [] [main] [] INFO
      org.springframework.boot.autoconfigure.web.servlet.WelcomePageHandlerMapping - Adding welcome page: class path resource [META-INF/resources/tasklist/index.html]
2024-09-27 15:46:21.251 [] [main] [] WARN
      org.springframework.boot.actuate.endpoint.EndpointId - Endpoint ID 'usage-metrics' contains invalid characters, please migrate to a valid format.
2024-09-27 15:46:21.636 [] [main] [] INFO
      io.camunda.tasklist.webapp.security.identity.IdentityWebSecurityConfig - CSRF Protection Enabled
2024-09-27 15:46:21.723 [] [main] [] INFO
      io.camunda.tasklist.webapp.security.oauth.IdentityOAuth2WebConfigurer - Using value in SPRING_SECURITY_OAUTH_2_RESOURCESERVER_JWT_JWK_SET_URI for issuer authentication
2024-09-27 15:46:21.723 [] [main] [] INFO
      io.camunda.tasklist.webapp.security.oauth.IdentityOAuth2WebConfigurer - Using http://camunda-keycloak:80/auth/realms/camunda-platform/protocol/openid-connect/certs for issuer authentication
2024-09-27 15:46:22.090 [] [main] [] INFO
      io.camunda.tasklist.webapp.security.oauth.IdentityOAuth2WebConfigurer - Enabled OAuth2 JWT access to Tasklist API
2024-09-27 15:46:22.689 [] [main] [] INFO
      io.camunda.tasklist.es.ElasticsearchConnector - Elasticsearch cluster health: Green
2024-09-27 15:46:22.690 [] [main] [] WARN
      io.camunda.tasklist.es.ElasticsearchConnector - Elasticsearch cluster is not accessible
2024-09-27 15:46:24.536 [] [main] [] INFO
      org.apache.coyote.http11.Http11NioProtocol - Starting ProtocolHandler ["http-nio-<IP_ADDRESS>-8080"]
2024-09-27 15:46:24.550 [] [main] [] INFO
      org.springframework.boot.web.embedded.tomcat.TomcatWebServer - Tomcat started on port 8080 (http) with context path '/tasklist'
2024-09-27 15:46:24.921 [] [main] [] INFO
      org.springframework.boot.web.embedded.tomcat.TomcatWebServer - Tomcat initialized with port 9600 (http)
2024-09-27 15:46:24.922 [] [main] [] INFO
      org.apache.coyote.http11.Http11NioProtocol - Initializing ProtocolHandler ["http-nio-<IP_ADDRESS>-9600"]
2024-09-27 15:46:24.922 [] [main] [] INFO
      org.apache.catalina.core.StandardService - Starting service [Tomcat]
2024-09-27 15:46:24.923 [] [main] [] INFO
      org.apache.catalina.core.StandardEngine - Starting Servlet engine: [Apache Tomcat/10.1.28]
2024-09-27 15:46:25.024 [] [main] [] INFO
      org.apache.catalina.core.ContainerBase.[Tomcat-1].[localhost].[/tasklist] - Initializing Spring embedded WebApplicationContext
2024-09-27 15:46:25.025 [] [main] [] INFO
      org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext - Root WebApplicationContext: initialization completed in 468 ms
Standard Commons Logging discovery in action with spring-jcl: please remove commons-logging.jar from classpath in order to avoid potential conflicts
2024-09-27 15:46:25.050 [] [main] [] INFO
      org.springframework.boot.actuate.endpoint.web.EndpointLinksResolver - Exposing 7 endpoints beneath base path '/actuator'
2024-09-27 15:46:25.322 [] [main] [] INFO
      org.apache.coyote.http11.Http11NioProtocol - Starting ProtocolHandler ["http-nio-<IP_ADDRESS>-9600"]
2024-09-27 15:46:25.326 [] [main] [] INFO
      org.springframework.boot.web.embedded.tomcat.TomcatWebServer - Tomcat started on port 9600 (http) with context path '/tasklist'
2024-09-27 15:46:25.348 [] [main] [] INFO
      io.camunda.application.StandaloneTasklist - Started StandaloneTasklist in 31.29 seconds (process running for 34.345)
2024-09-27 15:46:25.418 [] [main] [] INFO
      io.camunda.tasklist.schema.migration.SchemaMigration - SchemaMigration finished.
2024-09-27 15:46:43.956 [] [http-nio-<IP_ADDRESS>-9600-exec-1] [] INFO
      org.apache.catalina.core.ContainerBase.[Tomcat-1].[localhost].[/tasklist] - Initializing Spring DispatcherServlet 'dispatcherServletRegistration'
2024-09-27 15:46:43.956 [] [http-nio-<IP_ADDRESS>-9600-exec-1] [] INFO
      org.springframework.web.servlet.DispatcherServlet - Initializing Servlet 'dispatcherServletRegistration'
2024-09-27 15:46:43.957 [] [http-nio-<IP_ADDRESS>-9600-exec-1] [] INFO
      org.springframework.web.servlet.DispatcherServlet - Completed initialization in 0 ms

This log is not relevant because the same log appears on operate and operate is working fine:
io.camunda.tasklist.es.ElasticsearchConnector - Elasticsearch cluster is not accessible

Environment:
Please note: Without the following info, it's hard to resolve the issue and probably it will be closed.

Platform: GKE
Helm CLI version:
Chart version: Alpha
Values file:

When investigating, we found that curling the healthcheck endpoint in tasklist returned a response in 1.6 seconds on GKE.  However, our tasklist.readinessProbe is configured by default to cancel the request after 1 second.  This can be overridden to be 2 seconds, and the readinessProbe will succeed.
We can also consider changing the default timeoutSeconds in the helm chart for tasklist to prevent others running into this problem.

The helm chart updated it's default timeoutSeconds for tasklist. closing


[SUGGESTION] Disable the Plugin and Theme Editor by default

Would it be smart to disable the Plugin and Theme Editor by default?
define('DISALLOW_FILE_EDIT',true);
Just for obvious security reasons and lack of use.

Hello I think this is done on bedrock. (https://roots.io/bedrock/).
Either way, IMO this is something for the bootstrap of the Wordpress installation it self and not for the theme.


MBA ESG

French school from ESG Group

School url : https://www.mba-esg.com/
Program : https://www.mba-esg.com/master-big-data.html

Thank you

@Azzerty23 Pull request merged. Thank you!


Rules in a a ResourceRequest are not checked against the Schema's defined fields; no exception thrown for an incorrect Request

I'm still new to Laravel JSON API. I had a
<?

class UpsellRequest extends ResourceRequest
{
  /**
   * Get the validation rules for the resource.
   *
   * @return array
   */
  public function rules(): array
  {
    return [
      "salesarea" => JsonApiRule::toOne(),
      "upsell_variant" => ["required", "string"],
      "name" => ["required", "string"],
    ];
  }
}

The accompanying schema is as follows
<?

class UpsellSchema extends Schema {
  /* ... */

   public function fields(): array
    {
      return [
        ID::make(),
        Str::make("name"),
        Str::make("upsell_variant"),
        BelongsTo::make("salesarea"),
        HasMany::make("upsell-products"),
        DateTime::make("createdAt")
          ->sortable()
          ->readOnly(),
        DateTime::make("updatedAt")
          ->sortable()
          ->readOnly(),
      ];
    }
}

I tried creating a new Upsell with a salesarea relation, and sent the following data
{
    "data": {
        "type": "upsells",
        "attributes": {
            "name": "Test",
            "upsell_variant": "upsell"
        },
        "relationships": {
            "salesarea": {
                "data": {
                    "type": "salesareas",
                    "id": "1"
                }
            }
        }
    }
}

The resource is created succesfully (200 OK), the Upsell model with name Test is created, all looks ok!
After inspecting the created model, I found that the salesarea_id is set to 0.
After a lot of searching in

The upsell schema
The salesarea schema
The relationships in the route
The upsell and salesarea policies
The data I'm sending on the frontend

I figured out that the issue lied with the Request, I had named rule salesareas (referring to the resource name: "salesareas") and not salesarea (referring to the field in the schema).
I'm noticing that in general it's very difficult to know which naming convention to use when, and I really hope it could be included in the base library to throw errors as early as possible to prevent having to search through all the related logic for a tiny singular typo or confusion between a schema field and relation.

Yeah agree this is tricky with the current version. You have to add validation rules, as we only use validated data. It's a bit of a gotcha that's caught people out.
I'm actually going to close this issue, as this is solved in the next major version. We're moving validation to the fields on the schema, which makes it clearer as to what's going on. You can see an example of that here:
https://github.com/laravel-json-api/laravel/issues/39#issuecomment-2101260482

Yeah agree this is tricky with the current version. You have to add validation rules, as we only use validated data. It's a bit of a gotcha that's caught people out.
I'm actually going to close this issue, as this is solved in the next major version. We're moving validation to the fields on the schema, which makes it clearer as to what's going on. You can see an example of that here: #39 (comment)

Ah, awesome! I'll keep a close eye on development, and will be providing feedback when I have some.


Why does RocketMQ pick "PUSH" model to implement HA?

Why not PULL?

Issues are generally used for bug reports and feature requests, so if you have any questions about     Apache  RocketMQ, it is recommended to discuss it on the mailing list first, the mailing list [address]    (https://rocketmq.apache.org/about/contact). I will close the Issue first, but please feel free to   reopen it if you have any other issues.


Parallelize the compiler

SqliteCoreEnvironment.forSourceFiles seems like a good one to parallelize.

https://github.com/AlecStrong/sqlite-psi/pull/26#pullrequestreview-106124809


Minimum number of samples

for minimum number of samples, there is an issue with the type of data. INT type cannot read the min. number

Hi! What do you mean under "minimum number of samples"?

I will close this issue for now as the question is unclear. Please re-open this issue if you can clarify the problem.


API :"v1/friendships/create" tragger log out

Hi,  TheM4hd1 :
I  was using i.instagram.com/api/v1/friendships/create/{userPk}/, but found that it  tragger "ve Been Logged Out" . I try to fix this by add cookie header, but failed . Could you please help me
details:
Optional(Ig_Followers.GenericError.custom("https://i.instagram.com/api/v1/friendships/create/1492092934/.\nInvalid response.\n{\n  "errorBody" : "Please log back in.",\n  "errorTitle" : "You've Been Logged Out",\n  "logoutReason" : 3,\n  "message" : "login_required",\n  "status" : "fail"\n}.\n403"))

Hey 😊
I can't seem to replicate the issue tbh. What version are you on? @swelzh


ReflectionException : Class env does not exist

Laravel Version: 5.7.10
PHP Version: 7.2.10
Database Driver & Version: Nothing connected or setup

Description:
When running PHPUnit tests an exception is thrown, ReflectionException : Class env does not exist;
ReflectionException : Class env does not exist
/var/www/vendor/laravel/framework/src/Illuminate/Container/Container.php:779
/var/www/vendor/laravel/framework/src/Illuminate/Container/Container.php:658
/var/www/vendor/laravel/framework/src/Illuminate/Container/Container.php:609
/var/www/vendor/laravel/framework/src/Illuminate/Foundation/Application.php:733
/var/www/vendor/laravel/framework/src/Illuminate/Container/Container.php:1222
/var/www/vendor/laravel/framework/src/Illuminate/Foundation/Application.php:487
/var/www/app/Providers/TelescopeServiceProvider.php:24
/var/www/vendor/laravel/framework/src/Illuminate/Support/HigherOrderCollectionProxy.php:60
/var/www/vendor/laravel/framework/src/Illuminate/Support/HigherOrderCollectionProxy.php:60
/var/www/vendor/laravel/framework/src/Illuminate/Support/Collection.php:442
/var/www/vendor/laravel/framework/src/Illuminate/Support/HigherOrderCollectionProxy.php:61
/var/www/vendor/laravel/telescope/src/Telescope.php:204
/var/www/vendor/laravel/telescope/src/Telescope.php:177
/var/www/vendor/laravel/telescope/src/Telescope.php:207
/var/www/vendor/laravel/telescope/src/Telescope.php:231
/var/www/vendor/laravel/telescope/src/Watchers/CacheWatcher.php:63
/var/www/vendor/laravel/framework/src/Illuminate/Events/Dispatcher.php:360
/var/www/vendor/laravel/framework/src/Illuminate/Events/Dispatcher.php:209
/var/www/vendor/laravel/framework/src/Illuminate/Cache/Repository.php:486
/var/www/vendor/laravel/framework/src/Illuminate/Cache/Repository.php:92
/var/www/vendor/laravel/framework/src/Illuminate/Cache/CacheManager.php:304
/var/www/vendor/laravel/telescope/src/Watchers/DumpWatcher.php:43
/var/www/vendor/laravel/telescope/src/RegistersWatchers.php:48
/var/www/vendor/laravel/telescope/src/Telescope.php:94
/var/www/vendor/laravel/telescope/src/TelescopeServiceProvider.php:25
/var/www/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php:29
/var/www/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php:87
/var/www/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php:31
/var/www/vendor/laravel/framework/src/Illuminate/Container/Container.php:572
/var/www/vendor/laravel/framework/src/Illuminate/Foundation/Application.php:793
/var/www/vendor/laravel/framework/src/Illuminate/Foundation/Application.php:776
/var/www/vendor/laravel/framework/src/Illuminate/Foundation/Application.php:777
/var/www/vendor/laravel/framework/src/Illuminate/Foundation/Bootstrap/BootProviders.php:17
/var/www/vendor/laravel/framework/src/Illuminate/Foundation/Application.php:206
/var/www/vendor/laravel/framework/src/Illuminate/Foundation/Console/Kernel.php:297
/var/www/tests/CreatesApplication.php:18
/var/www/vendor/laravel/framework/src/Illuminate/Foundation/Testing/TestCase.php:91
/var/www/vendor/laravel/framework/src/Illuminate/Foundation/Testing/TestCase.php:68
While the exception mentions Laravel Telescope it isn't relevant. I removed it and it still throws the error for another custom service provider. I did move code out of my boot function in my service provider to the register function but it still throws the error.
Steps To Reproduce:
Run php vendor/phpunit/phpunit/phpunit --configuration phpunit.xml tests

I have tried running composer update, composer dump as well as the various artisan commands to clear compiled resources.

I try the following commands.
$ composer create-project --prefer-dist laravel/laravel
$ cd laravel
$ composer require laravel/telescope
$ php vendor/phpunit/phpunit/phpunit --configuration phpunit.xml tests

Everything works normally for me.

Please update to 5.7.11 and check.
There was a bug in 5.7.10 around file permissions - might be related to this.

The issue was caused by my unit test itself. I was overriding the setup function and didn't call
the parent::setUp() function;

Adding this in case someone else has this issue....
I am not using setUp() and got the same error when I try to run a whole class of tests within PHPStorm.
Running a single test did not give me the error though.
I fixed it simply by setting the following in Storm Settings under Test Frameworks :
Default configuration File: ~/myproject/phpunit.xml
Default bootstrap file: ~/myproject/vendor/autoload.php

Experienced the same problem. Interesting enough after commenting out App\Providers\TelescopeServiceProvider::class from the providers list in app.php(config file) and ran my test suites, did not get the error.
Suspecting a call from TelescopeServiceProvider to the .env config file may be causing the problem when running the test suite

Having this problem with laravel v5.6.39. Using the default TestCase.php and CreatesApplication.php files.
Not using telescope. I'm only using the env() function from my config files.
Strange thing is that the tests do finish, however I just get this error at the end:
 % phpunit
PHPUnit 7.5.4 by Sebastian Bergmann and contributors.

..                                                                  2 / 2 (100%)

Time: 205 ms, Memory: 24.00MB

OK (2 tests, 2 assertions)
PHP Fatal error:  Uncaught ReflectionException: Class env does not exist in /home/somefolder/vendor/laravel/framework/src/Illuminate/Container/Container.php:767
Stack trace:
#0 /home/somefolder/vendor/laravel/framework/src/Illuminate/Container/Container.php(767): ReflectionClass->__construct('env')
#1 /home/somefolder/vendor/laravel/framework/src/Illuminate/Container/Container.php(646): Illuminate\Container\Container->build('env')
#2 /home/somefolder/vendor/laravel/framework/src/Illuminate/Container/Container.php(601): Illuminate\Container\Container->resolve('env', Array)
#3 /home/somefolder/vendor/laravel/framework/src/Illuminate/Foundation/Application.php(734): Illuminate\Container\Container->make('env', Array)
#4 /home/somefolder/vendor/laravel/framework/src/Illuminate/Container/Container.php(1210): Illuminate\Foundation\Application->make('env')
#5 /home/somefolder/vendor/laravel/framework/src/Illuminate/Foundation/Application.php(487): Illuminate\ in /home/somefolder/vendor/laravel/framework/src/Illuminate/Container/Container.php on line 767
PHP Stack trace:
PHP   1. {main}() /home/somefolder/vendor/phpunit/phpunit/phpunit:0
PHP   2. PHPUnit\TextUI\Command::main() /home/somefolder/vendor/phpunit/phpunit/phpunit:61
PHP   3. PHPUnit\TextUI\Command->run() /home/somefolder/vendor/phpunit/phpunit/src/TextUI/Command.php:162
PHP   4. PHPUnit\TextUI\TestRunner->doRun() /home/somefolder/vendor/phpunit/phpunit/src/TextUI/Command.php:206

https://github.com/laravel/framework/issues/26627#issuecomment-497276990

For someone still having the issue, it can be solved adding
<server name="TELESCOPE_ENABLED" value="false"/> in phpunit.xml.

#26627 (comment)

For someone still having the issue, it can be solved adding
<server name="TELESCOPE_ENABLED" value="false"/> in phpunit.xml.

Perfect !


Issue 3275/fix remove used param

What's changed?
https://github.com/openrewrite/rewrite/issues/3275 pointed out an issue with incorrectly removing an import that was being used as a function parameter. This change updates the class path matching logic to check for either a . or a $ class path separator.
What's your motivation?
My motivation is to resolve https://github.com/openrewrite/rewrite/issues/3275 and make the RemoveUnusedImports recipe more reliable for wider adoption.
Anything in particular you'd like reviewers to focus on?
I co-opted the predicate used in https://github.com/openrewrite/rewrite/pull/3363 to more generally match against class paths that have a $ as a separator.
Anyone you would like to review specifically?
Any maintainer 😄
Have you considered any alternatives or workarounds?
n/a
Any additional context
n/a
Checklist

[x] I've added unit tests to cover both positive and negative cases
[x] I've added the license header to any new files through ./gradlew licenseFormat
[x] I've used the IntelliJ auto-formatter on affected files

@tclayton-newr Thanks for contributing this PR! I will take a look at it later today or tomorrow.

Thank you very much for your contribution and addressing all the comments :)


SIGSEGV occasionally occurs when calling vmaVirtualFree with TLSF algorithm

Hi.
I am implementing a mesh streaming system using the virtual allocation feature. With the default algorithm, everything works fine. But when I enabled VMA_VIRTUAL_BLOCK_CREATE_TLSF_ALGORITHM_BIT in virtual block creation, crashes occasionally occurs in vmaVirtualFree.
I tested it multiple times, and found the crashes all take place in VmaBlockMetadata_TLSF::InsertFreeBlock (line 10341), and block->NextFree() seems to be an invalid pointer (not null) which cause statement "block->NextFree()->PrevFree() = block;" to crash. Further more there might be some errors maintaining VmaBlockMetadata_TLSF::m_FreeList since block->NextFree() is from it. I hope the information can be of help.
The commit I use is 05d0c89 (the latest at the time). And I'm sure all the virtual block usage is protected by a mutex.

Hi,
Do you have VMA_ASSERT defined to something that would report failures? Can you please also enable VMA_HEAVY_ASSERT and check if you can find something with it? That would help to find the bug.

I tried, in Debug mode, with VMA_HEAVY_ASSERT macro enabled. Sadly no failed assertion occurs.

Could you please somehow dump the sequence of allocations and frees you do in the virtual block, e.g. to some log or CSV file?
Are you sure you are not passing to vmaVirtualFree some uninitialized or already freed allocation handle?

// vma_test_simple.cpp
#define VMA_IMPLEMENTATION
#include "vk_mem_alloc.h"

VmaVirtualBlock block{VK_NULL_HANDLE};

int main() {
	{
		VmaVirtualBlockCreateInfo info = {};
		info.flags = VMA_VIRTUAL_BLOCK_CREATE_TLSF_ALGORITHM_BIT;
		info.size = 50331648;
		vmaCreateVirtualBlock(&info, &block);
	}
	{
		VmaVirtualAllocationCreateInfo info = {};
		info.alignment = 2;
		info.flags = VMA_VIRTUAL_ALLOCATION_CREATE_STRATEGY_MIN_MEMORY_BIT;

		VmaVirtualAllocation allocation[3] = {};

		info.size = 576;
		assert(vmaVirtualAllocate(block, &info, allocation + 0, nullptr) == VK_SUCCESS);
		assert(allocation[0] != VK_NULL_HANDLE);

		info.size = 648;
		assert(vmaVirtualAllocate(block, &info, allocation + 1, nullptr) == VK_SUCCESS);
		assert(allocation[1] != VK_NULL_HANDLE);

		vmaVirtualFree(block, allocation[0]);

		info.size = 720;
		assert(vmaVirtualAllocate(block, &info, allocation + 2, nullptr) == VK_SUCCESS); // where the segfault occurs
		assert(allocation[2] != VK_NULL_HANDLE);
	}
	return 0;
}

I found a simple example of this bug.
Compiled with g++ vma_test_simple.cpp -lvulkan, the code produces a segfault

I also accidentally discovered another bug: when using default algorithm, the allocation object can be null even if vmaVirtualAllocate succeed
#define VMA_IMPLEMENTATION
#include "vk_mem_alloc.h"

VmaVirtualBlock block{VK_NULL_HANDLE};

int main() {
	{
		VmaVirtualBlockCreateInfo info = {};
		info.size = 134217728;
		assert(vmaCreateVirtualBlock(&info, &block) == VK_SUCCESS);
		assert(block != VK_NULL_HANDLE);
	}
	{
		VmaVirtualAllocationCreateInfo info = {};
		info.alignment = 8;
		info.flags = VMA_VIRTUAL_ALLOCATION_CREATE_STRATEGY_MIN_MEMORY_BIT;

		VmaVirtualAllocation allocation;

		info.size = 1536;
		assert(vmaVirtualAllocate(block, &info, &allocation, nullptr) == VK_SUCCESS);
		assert(allocation != VK_NULL_HANDLE); // VK_SUCCESS but allocation is null
	}
	return 0;
}

Thank you for the repro, we will investigate it.
Regarding the other bug, we just fixed it today. Please check the latest code and see if it is fine now - VK_NULL_HANDLE should never happen for a successful allocation in the default or linear algorithm.

In your first code sample, please note you are calling functions with side-effects inside assert. If the program is not compiled in some Debug mode, this code is not executed.
I pushed fixes to the library so that calling vmaVirtualFree for allocation == VK_NULL_HANDLE is legal and does nothing.

Well, after some test, I believe the bug still exist.
I add a assertion in the vma header as followed:
void VmaBlockMetadata_TLSF::InsertFreeBlock(Block* block)
{
    // ...
    uint32_t index = GetListIndex(memClass, secondIndex);
    VMA_ASSERT(index < m_ListsCount); // THE ASSERTION
    block->PrevFree() = VMA_NULL; // Line 10342
    block->NextFree() = m_FreeList[index];
    m_FreeList[index] = block;
    if (block->NextFree() != VMA_NULL)
    // ...

And in the example code (compiled in debug mode)
#define VMA_IMPLEMENTATION
#include "vk_mem_alloc.h"

#include <cstdio>
#include <cstdlib>

VmaVirtualBlock block{VK_NULL_HANDLE};

int main() {
	{
		VmaVirtualBlockCreateInfo info = {};
		info.flags = VMA_VIRTUAL_BLOCK_CREATE_TLSF_ALGORITHM_BIT;
		info.size = 50331648;
		vmaCreateVirtualBlock(&info, &block);
	}
	{
		VmaVirtualAllocationCreateInfo info = {};
		info.alignment = 2;

		VmaVirtualAllocation allocation[3] = {};

		info.size = 576;
		vmaVirtualAllocate(block, &info, allocation + 0, nullptr);

		info.size = 648;
		vmaVirtualAllocate(block, &info, allocation + 1, nullptr);

		vmaVirtualFree(block, allocation[0]);

		info.size = 720;
		vmaVirtualAllocate(block, &info, allocation + 2, nullptr);
	}
	return 0;
}

the assertion fails, which indicates there are surely some memory access errors.


[GOBBLIN-1084] Refresh flowgraph when templates are modified

Dear Gobblin maintainers,
Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!
JIRA

[x] My PR addresses the following Gobblin JIRA issues and references them in the PR title. For example, "[GOBBLIN-XXX] My Gobblin PR"

https://issues.apache.org/jira/browse/GOBBLIN-1084

Description

[x] Here are some details about my PR, including screenshots (if applicable):

Currently, if edges fail to be added on startup, they will not be tried again even if the issue is fixed through modifying the templates. This change causes the entire flowgraph to be refreshed if any template is modified.
Tests

[x] My PR adds the following unit tests OR does not need testing for this extremely good reason:

Commits

[x] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

@sv2000 please review

Codecov Report

Merging #2924 into master will decrease coverage by 0.01%.
The diff coverage is 57.14%.

@@             Coverage Diff              @@
##             master    #2924      +/-   ##
============================================
- Coverage     45.46%   45.45%   -0.02%
- Complexity     9109     9113       +4
============================================
  Files          1936     1936
  Lines         73059    73145      +86
  Branches       8051     8071      +20
============================================
+ Hits          33217    33246      +29
- Misses        36782    36828      +46
- Partials       3060     3071      +11

Impacted Files
Coverage Δ
Complexity Δ

...blin/service/modules/core/GitFlowGraphMonitor.java
72.00% <0.00%> (-1.78%)
23.00 <1.00> (ø)

...lin/service/modules/core/GitMonitoringService.java
57.59% <ø> (ø)
9.00 <0.00> (ø)

...odules/template_catalog/FSFlowTemplateCatalog.java
59.57% <100.00%> (+0.87%)
9.00 <1.00> (+1.00)

...te_catalog/ObservingFSFlowEdgeTemplateCatalog.java
88.23% <100.00%> (+1.13%)
9.00 <1.00> (+1.00)

...obblin/service/monitoring/FlowStatusGenerator.java
46.00% <0.00%> (-23.70%)
11.00% <0.00%> (ø%)

...blin/service/modules/orchestration/DagManager.java
71.33% <0.00%> (-5.14%)
13.00% <0.00%> (ø%)

...e/gobblin/runtime/locks/ZookeeperBasedJobLock.java
63.33% <0.00%> (-1.12%)
15.00% <0.00%> (-1.00%)

...he/gobblin/compaction/source/CompactionSource.java
72.16% <0.00%> (-0.90%)
14.00% <0.00%> (ø%)

...main/java/org/apache/gobblin/util/HadoopUtils.java
30.20% <0.00%> (-0.68%)
24.00% <0.00%> (-1.00%)

...service/modules/orchestration/DagManagerUtils.java
85.05% <0.00%> (-0.49%)
39.00% <0.00%> (+2.00%)
:arrow_down:

... and 2 more

Continue to review full report at Codecov.

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


Firefox: Endless loading icon

The icon in the firefox-tab do not stop due to the streaming responses. Can we do something against it?

Could you try to add a timeout before connecting to the streaming services?
https://stackoverflow.com/questions/9932462/how-to-remove-safaris-loading-wheel-when-using-server-sent-events
Our should were use websockets? 😀

Maybe some browser lifecycle thing. I can imagine, that we should wait for DomContentLoaded or so, before issuing new requests. Maybe browsers think that those early requests are still page loading request. I'll du some experiments tomorrow.

OK: We need to start communication (->bootup) in the root-component's ngOnInit, which is fired after DomContentLoaded with an async dispatch (-> timeout of 0 seconds). Firefox is ok, but I did not check Edge and Safari.
@jsangmeister I wanted to fiddle around with the communication, so I can include this into  the changes I have in mind.


Hackage docs failed to build for doormouse-client-<IP_ADDRESS>

Not sure what the problem is because I was able to build them locally.
PS: Thanks for the new library, excited to see where it goes!

The Hackage documentation mentions that this can happen, seemingly for no particular reason.
There is a manual process to include the docs in the package, I will investigate and see if I can upload a fixed version.

The build failed due to missing Lift Text instances: https://hackage.haskell.org/package/dormouse-client-<IP_ADDRESS>/reports/2
These instances were only added in text-<IP_ADDRESS>, so the lower bound of the dependency on text should be bumped

Thanks @mitchellwrosen, just realised this as well.  Fixing now.

A new version has now been published and module documentation has been successfully built in Hackage.  Thanks both.


Ability to extend existing modules

It should be possible to extend existing modules with more functions. Let's say I want to make use of the built-in io module but my interpreter needs to add more functionality which fits into the same category and should thus use the same namespace. Then I'd like to extend the existing KMap with the new functions in the prelude.

If I understand the question correctly this is already possible, the core library modules are simply KMaps that can be modified like any other.
This is what enables custom iterator adaptors to be written like in this example from the guide.
Now of course being able to modify core modules is a huge potential footgun (e.g. nothing's stopping you from saying number.pi = 3.2 and suffering the consequences), but for now I haven't been able to bring myself to prevent it.

Interesting, even though we're talking about different layers again 😄 I want to insert a Rust module into the prelude and extend an existing KMap from there. I haven't found a way to get a reference to the core module KMaps. Your example was about runtime modification, but that could also be very helpful. That's why I like your language, it's really dynamic.

I see! My gut reaction is that you'd be better off introducing a new module like io_ext or my_io, or whatever, rather than introducing general extensions to the core library, which has the potential for confusing the learner, e.g., why aren't these functions available in the core lib? Why am I getting errors when I run this function in a different app that uses Koto?, etc.. In the example where the core library is modified from within a Koto script, at least it's visible to the user (and it was most likely the user that made the modification).
If you really want to modify the core io module then it's available in the default prelude, you can just call Koto::prelude().data().get("io") and do what you like, although I think I'd advise against it.

You got a point there. I guess I'll go with the io_ext pattern then.


⚠ Turnos 24x7 has degraded performance

In cbeecdf, Turnos 24x7 (https://reservas-dev.alternativasinteligentes.com/) experienced degraded performance:

HTTP code: 200
Response time: 968 ms

Resolved: Turnos 24x7 performance has improved in 06a2aad.


Customizing mimalloc to enable store and restore of a memory heap from one process to another for same binary

Hi,
At work, we are looking into experimenting with mimalloc as a general purpose memory allocator and possible replacement for jemalloc (from initial benchmark, it is showing promise and we see around ~1.5GB lesser memory consumption on avg. for a long running process). In addition, we are working on a project to improve startup time of our application. Currently the app is deployed in multiple machines (same/similar machine characteristics) and they all process a bunch of files before beginning to take user requests. This takes a long time on each machine and we are looking to speed up this process by making just one machine (producer) process the files and have its processed memory dump to file and directly load the file backed memory in other machines (consumers) so they can avoid the too long startup time. There is a separate effort to write a custom allocator for this use case but we wondered whether mimalloc can be customized to support it and started working on the PoC.
My current approach:
On Producer machine-

Create a new heap via mi_heap_new() that returns huge chunk of OS memory at a fixed base address, that is then used to process these files . (This also requires modification to mmap routine to use MAP_FIXED since we want to ensure OS returns address at given fixed base address)
Enable this new heap as current heap.
Any subsequent malloc()/free() will come from this heap.
When producer is done, then dump the whole heap in a file and ship them to the consumers.

On Consumer machines-

Create a new heap via mi_heap_new() and load the memory backed by file at the same fixed base address as on producer machine. (Note: This is crucial so all the internal pointers will be relative to the fixed base address and doesn't need to be changed/patched.)
Enable this new heap as current heap.
From now on, any subsequent malloc()/free() can come from this heap but also the app can use the existing memory objects created on the producer machines.
(In a way, the idea is to patch up the mimalloc internal states so that it continues to work as if it had created these memory objects).

First of all, I would like to get feedback on this approach and also want to know if there are any alternate approach based on existing mimalloc features/api that will make this implementation easier. Also, given that this feature might be useful for others, is this something the upstream maintainers interested in merging to mimalloc ?
Please let me know if you have any questions!

@daanx any thoughts or comments on the above please ?

Based on my latest findings, it looks like currently the mi_heap_new() doesn't automatically use a new segment that I created (backed with huge OS allocation ~ 2GB) but still uses the thread local segments (mi_heap_s->tld->segments) which it shares with other heaps. Currently I don't see any way to override it without affecting other heaps as well.

Hi @beyonddream, very interesting -- but tricky...  recently we added the mi_manage_os_memory which can be used to assign a large memory arena;  So, in the producer, one can

allocate using direct OS calls memory at a fixed address
use mi_manage_os_memory to add that as memory arena to mimalloc and set the option mi_option_limit_os_alloc to stop mimalloc from allocating from the OS itself.
at the end write out the memory area to file.

Now, all memory for all heaps come from that area but there are some parts of the state that you need to save/restore which may be more tricky:

the threadid's: mimalloc uses the threadid to check multi-threaded access in the heaps and segments; these need to be saved/restored differently; actually, you can use the heap and segment walking functions to do this I think.
same for the security keys if using secure mode (as those use randomness)
there is a static structure (in init.c) for the initial main heap that points to the rest; this needs to be saved/restored as well but again, very carefully :-)

Not sure of this covers it; it will be tricky to do this but might perhaps work


Amount not restored from token in receive screen

When token is saved to address book, then token menu -> receive.
Receive screen opened. Amount, address type &c is restores. Currency is not.

Should be OK, please test.

Currency is not restored

Currency is not restored on the Send screen

This task is only for receive screen. We never modify someone's else address. If your friend gave you address to receive 10 BEAM it would be save in address book exactly as provided, as 10 BEAM, even if you choose to send 10 Yan.

Checked


properly calculate weighted median

Properly calculates a pixel-coverage weighted mean, median uses all values equally cc: @olafveerman
re: https://github.com/NASA-IMPACT/covid-dashboard/issues/412

This seems to check out. Are you getting CO2 means that are more in line with the expectation with these changes?


Caching the grapheme_length of a Text

Pull Request Description
Computing length of a text takes time. Let's cache it after first computation.
Important Notes
Wrote StringBenchmarks that sums lengths of (the same) Text present many time in a Vector. Initially it took 383.673 ms per operation. Then it took 0.031 ms/op. Looks like the length calls are returning instantly as they get cached.
Checklist
Please include the following checklist in your PR:

[x] The documentation has been updated if necessary.
[x] All code conforms to the Java style guides.
All code has been tested:

[x] Benchmarks have been written where possible.

Hehe, I guess I will have to fix our annotation processor to eliminate this failure.


[Typechecker] Disallow passing expression pattern inout to the match function

The following code is legal:
func ~= (pattern: inout Int, value: Int) -> Bool {
  pattern = value
  return true
}

var x = 0

switch 49 {
case x:
  print("yup")
default:
  print("nope")
}

print(x) // 49

Disallow passing the expression pattern inout to the pattern matching function (~=). This is a source-breaking change, but is deemed acceptable by Joe Groff.
Resolves SR-11488.

Should we add a diagnostic instead of simply discarding the choice?

Honestly if we can figure out how to make the value being matched an rvalue instead of an lvalue we'd pretty much get this behavior for free, including a diagnostic. @xedin, is there an easy way to do that?

We don't call the above operator func if x is a let variable. This is the main reason why I didn't add a diagnostic.

If it's the only match operator for a type, though, it would still show up.

Hmm yeah, since the expr pattern has to be Equatable in order for ~= to be called, we'll always have at least one match operator func (i.e. Swift.~=). In the above case, we're choosing that over the one we've provided since x is immutable, so I thought I'd make sense to do that for mutable one as well (to keep the behaviour consistent).

Nevermind, it seems like if the expr pattern isn't Equatable we do use the custom one.

I don't think the expr pattern has to be Equatable. Where do we check that?

class A {
  let id = UUID().uuidString
}

var x = A()
var y = A()

switch y {
case x: // argument type 'A' does not conform to expected type 'Equatable'
  print("yup")
default:
  print("nope")
}

That's coming out of the constraint system trying to use the only generic ~= it can find. If you define the inout one you'll get a different error.

(None of these diagnostics are great.)

If I define:
func ~= (pattern: inout A, value: A) -> Bool {
  pattern = value
  return true
}

it compiles and prints "yup". Although when x is immutable, I get: left side of mutating operator isn't mutable: 'x' is a 'let' constant

That's what I was getting at this whole time, although I guess it's a pretty lousy diagnostic. Still, it doesn't seem like we need to do better than what we do for let.

We have a couple of options here but the question I have is whether it should be valid to declare ~= with inout parameters at all? I guess we could diagnose and strip inout away if that's not something which should be supported...

Diagnosing the declaration seems nice and it means the mistake can be caught earlier (rather than diagnosing when we attempt to switch).

I understand that ~= is a special operator, but I don't think it should be illegal to write this operator with inout. I do think that any version which uses inout parameters shouldn't be considered when type checking an expression pattern which is why I'm kind of in favor of the proposed implementation. (Although I would check all parameters rather than just the first one).

I suppose we can check both parameters but if the value parameter is inout or if both params are inout, then we don't get this behaviour, so maybe we only need to check the pattern parameter?

I think the best option might be to bring this up on the forum and probably update the accepted proposal afterwards.

Yeah, I’ll create a discussion thread on swift evolution shortly.

@theblixguy Thank you! Please CC me as well, I'm out for a week but I'll follow along when I have a minute.

Created a thread here: https://forums.swift.org/t/disallow-passing-expression-pattern-inout-to-the-match-function/29446

So…what's up with this PR? Doug struck out the "~= should not have inout because it's only used for switch" interpretation, but that still leaves "filter out the inout cases" vs. "leave in the inout cases and let them error". (And I still prefer the latter.)

Looks like that forum post didn't get any traction, I think it would be great to document the behavior (I prefer the "leave and error" approach) in the proposal before we go ahead and implement it.

Does this need an evolution proposal to change the behavior? Thought it was considered a bug which didn't need one.

Yeah, Joe said so on the original SR.

I have talked to @DougGregor about this today, and he is going to bring it up to the Core Team to discuss.  It might be possible to do this through amendment to existing proposal.

through amendment to existing proposal

Which proposal?

Hm, I thought that there was one for that but I guess there is none, so it would have to a proposal.

The Core Team discussed this today. Our preference is to maintain the current type checking behavior, but error when this implicit inout conversion happens to the pattern during pattern matching. That would let us stage out the behavioral change over more than one release: diagnose the code that would break or change behavior "now", then in a future release we can disable the implicit inout conversion in the type checker. So the first example mentioned in the PR summary would be ill-formed "now", and fall back to the Equatable some time in the future.

Can one of the admins verify this patch?

@theblixguy Are you still pursuing this?

Please update the base branch to main by Oct 5th otherwise the pull request will be closed automatically.

How to change the base branch: (Link)
More detail about the branch update: (Link)