device-linear-multifrag execution mode

As of now, HDK's heterogeneity looks like this:

We have X fragments, when we schedule them on a GPU, it will receive X kernels, X fragments and execute kernels sequentially.

The currently disabled multifragment option does the following:

We have X fragments, when we schedule them on a GPU, it will receive 1 kernel and X fragments and execute this one kernel.

Why is current multifragment good:

We avoid repeated administrative work around preparing X kernels, scheduling them and retrieving results.
Fine grained control (allocate/free) over memory of fragments.

Why is it not that good:

Currently we place fragments in GPU memory arbitrarily, this is taken care of in the code of GPU kernels which increases their complexity for the programmer, we cannot simply index into the multifragmented column and we have to do more checks per tuple (e.g.,  JoinColumnIterator& operator++() and related for loops). This likely eats some performance from the executePlan stage, which is often the costliest.

Basic idea:
The best case for the kernel is if all columns are linear (simple loops over dense data). All GPU-assigned fragments have to be materialized anyways, so why not place them linearly?
We can add a new execution mode where fragments (regardless of their position in host memory) are assembled linearly on GPU, this way, the fragments become transparent for the GPU kernel, it will treat them as one big fragment. We still know the address of each fragment and can get it back to CPU, but we cannot free individual fragments, only if we do it for the whole linear buffer. Such behavior is not different from just a big fragment size.
Why is it supposed to be better?

Cheap initial data locality
Easier indexing into a column -> easier and (likely) faster kernel code

What's the catch?

We lose fine granularity of memory control on GPU. But do we always care?
What if the next step takes more fragments? We know which fragments are still on GPU and their location, so one could avoid using bandwidth by memmove/memcpy'ing on the device itself and add only missing ones. If it is not possible, we pay the fetching price. Maybe this is a subject to more sophisticated data structures.

This won't bring any benefit for CPU as it is expensive and redundant (with regards to memory) to linearize fragments, also likely pointless anyways, since each thread processes one fragment (which is linear) at a time.
When does this execution mode make sense:

Query is just one step (or more with the latter ones being more compute intense)
Proportions do not change between steps (this is in a simple CPU+GPU scenario, but the more devices we have, the more likely we are to shuffle the fragments between them anyways)
Pure plan execution speed, the workload is not severely bandwidth bound.

Fetching chunks takes noticeably less time than executePlan, possible savings in executePlan might justify a small increase in latency caused by chunk placement.
Summary:
GPUs will be able to treat any number of fragments as one big fragment of arbitrary size, which aligns with the goal of heterogeneity and GPU's preferred programming model. But there's a price: memory management granularity + bandwidth. The question is if the price is justified? After all, it will be just an option, so if the bandwidth is the bottleneck, one could just switch to the current way of multifragment execution. But if one knows that a workload needs only a handful of columns, why not get the most out of the hardware?
The purpose of the related work is to see if it brings noticeable benefits at all, if not, then we will at least know where not to look into.
Any tips, suggestion and critic is welcomed.

The basic idea looks very reasonable. But before implementation, I'd try to measure possible gain by running some queries on GPU with different fragment sizes. Changing fragment size you can run the same query with multi-fragment kernels and single-fragment kernels by setting a big enough fragment size (and maybe setting config flag?). Then you'd be able to decide if the implementation complexity is worth it.

@akroviakov, could you please post the preliminary data here as well?

To see the benefit and compare to the current multifrag, one must be able to (1) linearize on GPU one-by-one and (2) modify some kernel (I'm thinking of HT builder) to make it somewhat "linear". I'm currently working on linearizing on GPU which needs something like getOneTableColumnFragmentTo(int8_t* dest, ..) to omit materialization on CPU and copy to the desired location.

To see the benefit and compare to the current multifrag, one must be able to (1) linearize on GPU one-by-one and (2) modify some kernel

Can you run the same query on the same data imported with different fragment sizes? E.g. you can import 100M rows with fragment_size=1'000'000 and fragment_size=100'000'000. The first one would use multi frag kernel with 100 fragments and the other one can be run with a single fragment

Quick data on a simple group by 10'000'000 rows:
Current multifrag, 2nd run, 20 frags:
          77ms start(16ms) executePlan Execute.cpp:3540
Current one frag, 2nd run:
          76ms start(13ms) executePlan Execute.cpp:3576

The difference simply due to a memory layout is indeed not noticeable.
Does that mean that it is simply better to focus on enabling current multifragment? Btw, why is it currently disabled?
I was thinking about the execution mode with HT builder in mind, which is not codegen'ed and looks a bit messy, so would you say it is just because of its implementation, not related to the memory layout assumptions?

I'm rooting for the approach. I see no reason to linearize the data on the CPU. I also think kernel data sizes should be arbitrary. Here are some thoughts on the topic.
Interleaved execution
The multi-fragment execution approach potentially allows for interleaving data copying with the execution. Having all the data linearized assumes (though not necessarily, but we imply it when we say the kernel will be simplified) that the iteration space for threading is now the whole linearized memory chunk (instead of a single fragment as it is now). The proposed approach can employ the technique as well but at a coarse granularity: interleaving will happen between kernels. The tradeoff affects latency and is probably not a considerable point since any latency-sensitive (small data) query is perfectly fine on the CPU.
Memory management on re-fragmenting
First, let's assume the data is small enough (for the other case see below). In such a case there can be a situation when we would need to move an additional fragment to or from the device. A naïve approach would reallocate the device buffer and move the data again to preserve linearity. My take on it is twofold:

Having a GPU proportion small enough to not occupy GPU memory is likely unreasonable to change as the bookkeeping would outweigh the benefit.
If we do have a benefit from rearranging the data in such a case, first, for moving the data from GPU there's no problem as we can keep track of the fragments with metadata. Second, moving fragments to GPU does not necessarily mean reallocation. One could either use the multi-fragment approach at a larger scale (chained linear chunks) or use a heap manager to do allocations dynamically (if the cost of memory provider allocations is tolerable; this can be managed by heuristics).

For larger datasets, a proportion on GPU would mean rather how many kernels we schedule to GPU while each of them may occupy "all" (probably half to allow interleaved execution?) the available memory. In this case, there's no need for fine-grained fragment management.

Quick data on a simple group by 10'000'000 rows:
Current multifrag, 2nd run, 20 frags:
          77ms start(16ms) executePlan Execute.cpp:3540
Current one frag, 2nd run:
          76ms start(13ms) executePlan Execute.cpp:3576

The difference simply due to a memory layout is indeed not noticeable. Does that mean that it is simply better to focus on enabling current multifragment? Btw, why is it currently disabled? I was thinking about the execution mode with HT builder in mind, which is not codegen'ed and looks a bit messy, so would you say it is just because of its implementation, not related to the memory layout assumptions?

This is an expected result since for a simple group-by query you replace a global loop with more work for each thread essentially saving several always-taken branch instructions. The benefit of simplicity as we discussed may come for those checks (or rather their absence) in the HT build.

This is an expected result since for a simple group-by query you replace a global loop with more work for each thread essentially saving several always-taken branch instructions. The benefit of simplicity as we discussed may come for those checks (or rather their absence) in the HT build.

Does it mean linear-multifrag can be beneficial only when we have proper runtime/codegen to remove multifrag costs we don't need when running on a single linear chunk? Then I'd suggest working on this first to get an opportunity to measure the real benefit of big linear chunks through experiments with fragment size.
The separate issue I guess is the efficiency of data fetch to GPU devices. Currently, we can have unnecessary copies of fragment data to CPU memory prior to copying it to GPU even when we fetch a single fragment. In many cases fragment is not zero-copy accessible on CPU and therefore we linearize it just to copy it to GPU. If we could change it to copy zero-copy accessible fragment parts directly to GPU then we could save some time and CPU memory. After that, the solution might be extended to multi-frag linearized fetches.

Does it mean linear-multifrag can be beneficial only when we have proper runtime/codegen to remove multifrag costs we don't need when running on a single linear chunk?

I think so. I don't see much reason for a linear chunk to be significantly superior in most common cases. It does save us some overhead on branching, but that's about it. Joins, however, is a different story.
The issue with data fetch is an evident one, I agree.

A few thoughts...
On GPU execution, we already support multi-fragment kernels. Therefore, we could have arbitrary sized fragments (yes there is some outer loop overhead but that seems negligible, and let's ignore copy overheads for now) for GPU now except that we need per-fragment metadata to properly size data structures - though, because we do not have any concept of sharding we actually don't size data structures for anything more than the full data. So, multi-frag execution of arbitrary size on GPU should be doable today quite easily.
As an aside, linearization cost is very high for varlen data. JoinColumnIterator was created to support joins on varlen data across multiple fragments. It was never finished, though, because the payload of the hash table really needs the ability to do the index. At the end of the day, though, it is just a multi-index and I cannot imagine the overhead of adding to two integers is much higher than the overhead of adding to one.
On CPU, we do not support multi-fragment kernels because it seems redundant. On GPU you have kernel launch overhead, on CPU not so much. That being said, it probably would not be too hard to add multi-fragment capability. But, I think that is probably misguided. What you really want is to be able to assign each kernel some set of rows to compute - those rows may come from 10 fragments if the kernel is simple, or from < 1 fragment if the kernel is complex (e.g. sub-fragments). The metadata problem is as above, right? You only care about whole-table stats, not per-fragment stats at the end of the day. So, if you could (1) arbitrarily slice storage and assign it to kernels and (2) parametrize the kernels to generically take a set of rows to process, you could have both multi-fragment kernels and sub-fragments with just one code path (and again, likely minimal overhead - but would be interesting to test).
There is one place where per-fragment metadata can be incredibly useful, though, and that is in fragment skipping. If we ingest data in date order, for example (lots of data is generated in date order - think of point of sale records for one) and  then query on a date range, we can avoid even loading a lot of data if we have per-fragment metadata. Since we have to compute metadata anyway, it may make sense to leave the concept of fragment in storage and use the per-fragment metadata for fragment skipping on filter queries. I don't know how prevalent this is in our use cases or benchmarks, though.

As an aside, linearization cost is very high for varlen data.

In relation to the idea: if it has to be sent to GPU anyways and we know the total size of what we are sending, we can assemble data linearly without any additional cost, can't we?

overhead of adding to two integers is much higher than the overhead of adding to one.

We iterate there using operator++ which checks if we are inside the chunk for each row for each column. Isn't such a branch a performance penalty for GPU? Maybe it concerns only this unfinished iterator.

you could (1) arbitrarily slice storage

That is the biggest issue, we have columns that are chunked (ArrowStorage ChunkedArray), we read CSVs in 20MB blocks. That means that e.g., some of 8GB (20Mil. rows) Taxi dataset partition columns get sliced into ~407 arrays (of size 48.5-50k rows). With parquet it is a bit better, but still ~153 arrays (~131k rows per array). Getting arbitrary slices (i.e., fragments) would at the end mean redundant linearized materialization of these arrays. Currently we materialize fragments that require linearization (so most of the fragments). Any fragment load onto GPU also materializes, if it requires linearization, on CPU (memory levels).
The big plan is to move away from fragments and operate directly on these arrow chunks which will be zero-copy for CPU, so no actual need to materialize data on CPU. But on GPU we have to materialize data anyways, so why not walk over chunks and directly assemble into a linear GPU buffer (i.e., set of rows of arbitrary size), we can stick to fixed size types for now in this execution mode. This way CPU (with multifragment or "multichunk") still has good granularity, and GPU can easily slide through its set of rows. This way both CPU and GPU will be in their optimal setting for a step/pipeline execution, regardless of the fragment/chunk size.

(2) parametrize the kernels to generically take a set of rows

this is supposed to be part of implementing this execution mode for GPU.

it may make sense to leave the concept of fragment in storage and use the per-fragment metadata for fragment skipping on filter queries

Aren't we doing it when deciding which fragments to skip on dispatching somewhere in createKernels()? And the fragments already have a nice function mergeStats(), which later can be easily adapted to arrow chunks and won't go away.

As an aside, linearization cost is very high for varlen data.

It's true, we have to adjust offsets for varlen data. But we pay this price anyway even for CPU now because arrow chunks don't match fragments and we make an adjusted copy of the offset buffer on fetch.

On CPU, we do not support multi-fragment kernels because it seems redundant.

Actually, we do support it. When the aggregation result is so big that the reduction kills any gain of multiple kernels, we run a single multi-fragment kernel on CPU.

So, if you could (1) arbitrarily slice storage and assign it to kernels and (2) parametrize the kernels to generically take a set of rows to process, you could have both multi-fragment kernels and sub-fragments with just one code path

Yes, this is the goal. An additional challenge here is to use zero-copy fetch as much as possible, i. e. follow arrow chunks for imported tables, or ResultSets when working with execution results. Following existing arrow chunks in ArrowStorage can be quite tricky though. Different columns might have different chunks in our arrow data because some columns have the original split, while others were linearized during nulls/data transformations. The resulting batches would actually depend on the set of rows we want to use in a query. The easiest solution is to always use the most granular split we have for all columns. I guess it should be OK for CPU unless chunks become extremely small.

In relation to the idea: if it has to be sent to GPU anyways and we know the total size of what we are sending, we can assemble data linearly without any additional cost, can't we?

Well, one issue I can think of is you lose your notion of where you are in the original dataset in "storage". Consider SELECT * FROM t WHERE x > 10. We only need to do computation on column x - the other columns in t are immaterial to the query. So, we would place column x on the GPU and then place the fragment offsets that pass the filter in the output buffer, materializing lazily as the user iterates (this is especially important for SELECT * FROM t WHERE x > 10 LIMIT 10 queries, where you may be able to skip the load entirely once enough rows pass while iterating the result set). That works nicely now because we can easily map the fragment ID and offset in fragment to the list of fragments when iterating Results, but would require more computation if we assembled data linearly on the way to the GPU.

Yes, this is the goal. An additional challenge here is to use zero-copy fetch as much as possible, i. e. follow arrow chunks for imported tables, or ResultSets when working with execution results. Following existing arrow chunks in ArrowStorage can be quite tricky though. Different columns might have different chunks in our arrow data because some columns have the original split, while others were linearized during nulls/data transformations. The resulting batches would actually depend on the set of rows we want to use in a query. The easiest solution is to always use the most granular split we have for all columns. I guess it should be OK for CPU unless chunks become extremely small.

I don't follow - why can't we just maintain Arrow chunks of whatever size is optimal, and slice them globally using some notion of "virtual fragment" when we fetch data for the query?

I don't know why launchGpuCode would be slower with more fragments than with fewer on the same data. The join column iterator is all pre-processing, so that should not effect gpu code (perhaps with the lookup - but I am pretty sure the lookup is still a global index, which causes other problems). It would be good to understand where the current overheads are coming from - perhaps just ordering the data blocks passed to GPU or changing the algorithm for balancing fragments across GPUs would provide the same benefits as linearization without having to re-construct (and then put back together in ResultSet) the fragment ordering?


Include multiple relationships?

Is there any way to include multiple relationships? E.g.,:
The following works for a single association:
const homes = Homes.includes('rooms').all();

But this doesn't appear to work.
const homes = Homes.includes('rooms,residents').all();

Looking at the request header, it appears that this produces an incorrect request URL along with a 400 Bad Request response message:
http://localhost:4000/api/homes/?include=rooms%2Cresidents.

 Backend was misconfigured.


Add "create" subcommand

 $ wasmstation create ~/Documents/w4games/watris.wasm -t "watris"
Created your wasmstation project at /home/grant/Documents/watris

Build the cart by running:
    $ cd watris
    $ cargo build --release

After building:
 $ du -sh target/release/watris
816K	target/release/watris

Thank you for pointing out quite a few things that I overlooked when creating this subcommand. This new commit revises the create subcommand, it's new behavior looks like this:
 $ wasmstation create --help
Usage: wasmstation create <cart> [-s <display-scale>]

Create a Rust project for wrapping a WASM-4 game into a native executable in the current directory.

Positional Arguments:
  cart              path leading to the game's cartridge file (e.g.
                    /path/to/cart.wasm)

Options:
  -s, --display-scale
                    default scale factor of the window
  --help            display usage information

 $ wasmstation create ./watris.wasm -s 2
Created your wasmstation project at /home/grant/Downloads/watris

Build the cart by running:
    $ cd watris
    $ cargo build --release

 $ tree watris
 watris
├── build.rs
├── Cargo.toml
├── src
│   └── main.rs
└── watris.wasm

2 directories, 4 files

^ This new file structure includes {cart_name}/{cart_name}.wasm instead of {cart_name}/cart.wasm, this is much more readable for the end user 😃 .


react-animation: Better support hot reloading where refs become null

I've found two places that break hot reloading:

In AnimationMap.set we check for null-refs to prevent stored animations ending up in a void without anyone realising something went wrong, and a ref was never set.
In assertAndUnwrapRefs we change the TS type, and fail if any refs are null.

Both cases break hot reloading, meaning that the dev will see an error on screen (and in console), and has to reload the page manually.
AnimationMap.set
Here we can leave out the error, and use an error log instead, since it's just to inform the user.
Downside is that we don't want to flood the console with error logs in valid cases (during hot reloading).
Here we could keep track of which refs ever had a value set, and ignore this error log when it's emptied (assuming this is just temporary, and on purpose).
assertAndUnwrapRefs
The reason it exists is to not continue the rest of the function in case any refs are null, and to inform the user.
Instead of bailing out with an error, we could also let the user handle it more elegantly, something like:
const { isValid, self, item } = assertAndUnwrapRefs(refs);
if (!isValid) return gsap.timeline();

We still want to show an error log, but ideally not in a way that floods the console. In the same was as with the AnimationMap, we could detect if we've already validated the refs object once correctly, and forgo any logs if that's the case.

@ThaNarie changes in #208 will prevent the error in AnimationsMap.set. We're not trying to set an animation for a nullable key anymore.

assertAndUnwrapRefs is part of @mediamonks/react-hooks, I'll make an issue for this problem in that repository.


Disabled MoneyCap resulting in exceptions.

Additionally to the custom money cap TE should also respect the technical limits currently doesn't.
For example, with the cap disabled, paying yourself<PHONE_NUMBER>23743e542 Dollars causes your balance in the config to become (literally) "Infinity" which entirely disables salaries due to a NumberFormatException in #getBalance.
Imo balances and transactions should ultimately be limited to what TE/Java can handle to prevent unexpected behavior or even bugs as this one.
I would also recommend catching NFEs in such methods. TEAccount e.g. This way they can be properly reported.
Instead of #hasBalance and a default (or fallback) value for #getBalance I'd suggest using an Optional<BigInteger> as the return type of #getBalance. This way an invalid balance simply defaults to not having a balance in the specified currency.

@MarkL4YG Should we just hardcode a max value in then? Because as far as I know, the maximum size of a BigDecimal depends on how much memory there is. So there is no set maximum.

According to the Java docs a BigDecimal is limited to Int32*10^Int32 which explaines why an Integer of size 10^542 exceeds the max.
I think that looking at the exponent is enough for setting a performant limit to all transactions. Therefore it should be enough to check if the scale exceeds the scale limit. The actual scale limit could be Integer.MAX_VALUE-1 or just Integer.MAX_VALUE/2.
Using the scale for the limit will enforce an upper and a lower limit simultaneously.

So... I found the limitation. Turns out that configurate-hocon from Sponge uses com.typesafe.ConfigValueFactory whichs ConfigImpl formats BigDecimals into doubles.

That makes it a lot easier. We'll just cap it to the double max then.


Add content encoding to server options

For more context, see #553.
This PR adds allows clients to define contentEncoder and contentDecoder in their server options. This addition makes it easier for clients to opt-in to different content encodings, such as msgpack, without having to worry about the life cycle of the process spawned - which is necessary when passing a function.
There's a simple example usage in the integration tests, which doesn't actually do anything, but demonstrates that clients will be able to hook their own content encoders and decoders.

I will close the PR for now. Please ping if you decide to continue working on this.


[alexmuller] Add pre-commit hooks for all projects

Install a pre-commit hook in all of my GOV.UK projects that checks for the string "PRIVATE KEY".
Feel free to use this if you would like to.

to the golf bags!

LGTM :+1: :balloon:


(flagd) Return the provided default value in case of error

Each flag resolution method's signature requires a default_value. Currently it isn't used by the flagd provider.
It should be returned as value in case of error (here)

As discussed in https://github.com/open-feature/ruby-sdk-contrib/pull/24#discussion_r1576594466, providers should rather raise in case of error, letting the SDK handle the error (and run necessary hooks). Then I guess it should probably be the responsibility of the SDK as well to craft a ResolutionDetail response with the default value in it. Does this make sense @beeme1mr ?

Yes, exactly.

Note at the moment, there is no error management in the SDK I believe: https://github.com/open-feature/ruby-sdk/blob/main/lib/open_feature/sdk/client.rb#L22-L36
Until hooks are properly implemented, the error will just bubble up

@beeme1mr @maxveldink
Looking at other provider implementations, in-memory, meta provider, the current pattern is to let provider implementations populate an error ResolutionDetails in case of issue.
I think we should align so the change is consistent across providers. Perhaps we could deal with this along these lines:

SDK exposes a ProviderError(error_code, reason) struct
In case of error, provider returns ProviderError instead of ResolutionDetails
SDK pattern matches against the returned type, either forwards a ResolutionDetails or builds one using the ProviderError attributes and the default_value

Yeah, we're missing the appropriate handling of provider errors in the client. Would you mind opening an issue on the ruby-sdk repo to track this discussion?
So, I think the error use case is already covered in the ResolutionDetails spec type. If the provider implementation knows about an error, it returns a ResolutionDetails with the error code, error message and probably reason fields filled out, then uses the supplied default_value to the call for the value field. The OF client then passes all that information through to the user as an EvaluationDetails, and once we have hook support, you could log/in whatever there or with a passed-in provider hook.
We're not covering the case where an exception is thrown in a provider implementation (or any abnormal execution of a provider that does something that isn't spec-compliant). We need to protect against that in the client and return a default value with the error fields filled out.

I've created an issue on the ruby-sdk repo


Multiple clients subscribe same topic, no subscribers will receive message if one of them is closed by destroying socket

I have written a unit test for testing this behaviour. https://github.com/gnought/aedes/commit/81a12299ce60fdca82f4068e5cfb71f6f31490fe
This always fails in Nodejs v10. https://travis-ci.org/gnought/aedes/builds/553241364
I don't know if it is a nodejs bug, but it will pass if we modified mqemitter https://github.com/mcollina/mqemitter/blob/master/mqemitter.js#L88-L92 as
  setImmediate(() => {
    this._matcher.remove(topic, notify)
    if (done) {
      done()
    }
  })

@mcollina any clue from your expertise?

I don't know, nor I have the time to debug this :(.

Fixed in https://github.com/mcollina/aedes/pull/283


Updates to task endpoint

Related product team resources:
Related product discussion:
Related spec: https://github.com/meilisearch/specifications/pull/253
Motivation
Give people a better sense of what's happening in their environment by being able to easily and accurately tell them how many tasks meet a filter criteria without having to page through the results and count them manually.
Usage
Enables easier UI building for task view work.

When calling the /tasks endpoint with no filters show the total number of tasks there are in the environment.
When calling the /tasks endpoint with a filter (e.g. /tasks?statuses=enqueued ) show the total number of tasks that meet that filter criteria.

TODO

[x] Update the spec

Impacted teams
@meilisearch/cloud-team @meilisearch/docs-team @meilisearch/integration-team

PR has been merged and will be included in v1.3.0-rc1 🎉

Closing this issue out, spec is in review

Hello everyone 👋
We have released an RC (release candidate) of Meilisearch containing this change!
For anyone interested you can try it out by using

the release assets
the Meilisearch Docker image

docker run -it --rm -p 7700:7700 -v $(pwd)/meili_data:/meili_data getmeili/meilisearch:v1.3.0-rc.1

If you encounter any bugs, please report them here.
Thanks in advance for your help and your involvement in Meilisearch ❤
🎉 The official and stable release containing this change will be available on July 31st, 2023
⚠ RC (release candidates) are not recommended for production


Icon overlays are blurry in Grid View mode

What's the Problem?
right now the check icons for items in google drive (or similar) are blurred and not sharp.
Solution/Idea
use vector icons instead?
Alternatives
no alternatives available.
Priorities
| Vector check icons | Should |
Files Version
Version: <IP_ADDRESS>
Windows Version
OS Version: 10.0.19044.1348
Additional comment
No response

Tanks for the report. Could you post a screenshot?

Is this still an issue in the preview version? https://files.community/download/preview


Draft for file entropy scoring.

Summary

Issue] Briefly discuss the summary of the changes made in this
pull request in 2-3 lines.
Changes

[ ] Client-facing API Changes
[ ] Internal API Changes
[ ] Bug Fixes
[x] New Features
[ ] Performance Improvements
[ ] Code Style
[ ] Refactoring
[ ] Documentation
[ ] Tests

For all the boxes checked, please include additional details of the changes made in this pull request.
Testing Done

[ ] Manually Tested on local docker setup. Please include commands ran, and their output.
[ ] Added new tests for the changes made.
[ ] Updated existing tests to reflect the changes made.
[x] No tests added or updated. Please explain why. If unsure, please feel free to ask for help.
[ ] Some other form of testing like staging or soak time in production. Please explain.

For all the boxes checked, include a detailed description of the testing done for the changes made in this pull request.
Additional Information

[ ] Breaking Changes
[ ] Deprecations
[ ] Large PR broken into smaller PRs, and PR plan linked in the description.

For all the boxes checked, include additional details of the changes made in this pull request.

FYI, it wouldn't let me create a branch without spotless which triggered a whole bunch of code changes. The relevant changes for this PR are in the datalayout package. Please advise how I can fix the spotless issue.

FYI, it wouldn't let me create a branch without spotless which triggered a whole bunch of code changes. The relevant changes for this PR are in the datalayout package. Please advise how I can fix the spotless issue.

one simple way is
git reset f10c2663b43a61fc0dd26be87cddf9db1bd7f0fc^ -- `git show f10c2663b43a61fc0dd26be87cddf9db1bd7f0fc --name-only | egrep -v libs/datalayout | grep java`

then commit staged, checkout unstaged files
we need to setup hooks in IDE, or we can also terminal during commit/push

FYI, it wouldn't let me create a branch without spotless which triggered a whole bunch of code changes. The relevant changes for this PR are in the datalayout package. Please advise how I can fix the spotless issue.

one simple way to mitigate
git reset f10c2663b43a61fc0dd26be87cddf9db1bd7f0fc^ -- `git show f10c2663b43a61fc0dd26be87cddf9db1bd7f0fc --name-only | egrep -v libs/datalayout | grep java`

then commit staged, checkout unstaged files
we need to setup hooks in IDE, or we can also use terminal during commit/push

Even if I do this + a local commit for a file path only, it won't let me do it. Should I just do a separate PR with all the spotless fixes to help others, too?

FYI, it wouldn't let me create a branch without spotless which triggered a whole bunch of code changes. The relevant changes for this PR are in the datalayout package. Please advise how I can fix the spotless issue.

one simple way to mitigate
git reset f10c2663b43a61fc0dd26be87cddf9db1bd7f0fc^ -- `git show f10c2663b43a61fc0dd26be87cddf9db1bd7f0fc --name-only | egrep -v libs/datalayout | grep java`

then commit staged, checkout unstaged files
we need to setup hooks in IDE, or we can also use terminal during commit/push

Even if I do this + a local commit for a file path only, it won't let me do it. Should I just do a separate PR with all the spotless fixes to help others, too?

Fixed! :)


Problem with APL-1.0

When loading the module into meteor which does parsing of the JSON files
node_modules/spdx-license-list/spdx-full.json:54:15: Unterminated string constant (54:15)

appears on the logs

Hopefully fixed in 3.0.0: https://github.com/sindresorhus/spdx-license-list/releases/tag/v3.0.0


[dummy] checking test_disappearing_class

https://github.com/bazelbuild/rules_scala/pull/1071 is failing on test_disappearing_class and we have a hunch that it's not related to the change but to travis cache or something.
I ran the same test on my fork and it didn't fail.
FYI @simuons @ittaiz

:-( passed... but it also couldn't download cache so maybe it's related...

@or-shachar since https://github.com/bazelbuild/rules_scala/pull/1081 is merged and now https://github.com/bazelbuild/rules_scala/pull/1071 passed I think this can be closed.

Thanks!


The "readme.md" is inaccurate..

I feel as if it has been quite awhile since we have updated this. I'll probably fix it.
Just for future reference, we should update this more frequently.
(and are we going to use ; as a prefix for Ubi forever?)

Yes were gonna use ; forever


Move S3 bucket versioning test to test_s3.py

This also adds a simple waiter class for use in our tests to help in cases where we need to wait for API to reach eventual consistency.

Codecov Report

Merging #1750 into develop will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop    #1750   +/-   ##
========================================
  Coverage    92.41%   92.41%
========================================
  Files           53       53
  Lines         9850     9850
========================================
  Hits          9103     9103
  Misses         747      747

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 9a6fcb4...a34a8c3. Read the comment docs.


SpeechFactory_CreateSpeechRecognizer_With_Stream api not include in c++ sdk

hi Microsoft
SpeechFactory_CreateSpeechRecognizer_With_Stream api not include in c++ sdk，I find it in dll file, please add it in api file.

文档详细信息
⚠ 请勿编辑此部分。 docs.microsoft.com ➟ GitHub 问题链接必须具有此部分。

ID: efae7ff6-5557-221f-7539-5d2d1883127d
Version Independent ID: 4b868e15-0248-635c-aa2f-d591bbc77d65
Content: About the Cognitive Services Speech SDK - Microsoft Cognitive Services
Content Source: articles/cognitive-services/Speech-Service/speech-sdk.md
Service: cognitive-services
GitHub Login: @v-jerkin
Microsoft Alias: v-jerkin

@zentelfong Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.
@v-jerkin Hi, this is a document-enhancement issue, can you please check it and update the document as necessary? Thanks a lot!

C++ API has ICognitiveServicesSpeechFactory::CreateSpeechRecognizerWithStream() to allow you use audio stream for speech recognition:
```
auto factory = SpeechFactory::FromSubscription(L"YourSubscriptionKey", L"YourServiceRegion");
auto recognizer = factory->CreateSpeechRecognizerWithStream(YourStream);

The SpeechFactory_CreateSpeechRecognizer_With_Stream() is a C API. This is only used when you have to use C, instead of C++.

#please-close

@zentelfong
We will now proceed to close this thread. If there are further questions regarding this matter, please respond here and @YutongTie-MSFT and we will gladly continue the discussion.


Simple Java Programs

Heyy @trishan9 Please add some description of the issue to contribute. I want to contribute to this issue. Please it to me.

Ok, so you can add any simple Java programs under Java directory in the project, any program that you have in Java, you can add to the project!

Heyy @trishan9 , I have made the necessary changes and Added 4 Java programs including Insertion Sort, Cyclic Sort, Linear Search in 2D Arrays, and Reverse an Array. Kindly approve my pull request and merge it under hacktoberfest. Thanks!

Heyy @trishan9 , I have made the necessary changes and Added 4 Java programs including Insertion Sort, Cyclic Sort, Linear Search in 2D Arrays, and Reverse an Array. Kindly approve my pull request and merge it under hacktoberfest. Thanks!

It has been merged under hacktoberfest!

Thanks for your contribution!

Heyy @trishan9 Please add

Assigned!

Happy contribution!

Please assign this issue to me under Hacktoberfest2024


RecordType 8 event Operation nuance in Rare Application Consent

Describe the bug
Most Record Type 8 events have operations that end in a period - so I think the following line can't use an equality operator. You could use startswith but I've seen this event with the trailing period as "Consent to application.".
https://github.com/Azure/Azure-Sentinel/blob/be0a63cb09ef43a4d625a6c106529d44f5a222db/Detections/AuditLogs/RareApplicationConsent.yaml#L35

@mbrancato - thanks, PR #1509 submitted and should be completed today.

#1509 approved and merged.


outline getting removed on resize

we have an issue with black outlines of images getting removed in the current version (0.26.1). In 0.24.1 we still had the outline, though it was more grey than black.
What are the steps to reproduce?
sharp("test.jpg").resize({width: 1400}).toFile("test2.jpg")

What is the expected behaviour?
the outline is still visible after resizing the image
test image:

test result in 0.26.1

test result in 0.24.1:

any ideas?

Hi, did you see the fastShrinkOnLoad option?
https://sharp.pixelplumbing.com/api-resize#parameters

unfortunately this doesn't work
sharp("test.jpg").resize({width: 1400,fastShrinkOnLoad:true}).toFile("test0.26_fast.jpg")

I could reproduce this on libvips master with:
vips resize x.jpg tn_x.jpg 0.929615

This small + 0.5-patch in the libvips mask calculations seems to resolve this.

Patch
diff --git a/libvips/resample/templates.h b/libvips/resample/templates.h
index 1111111..2222222 100644
--- a/libvips/resample/templates.h
+++ b/libvips/resample/templates.h
@@ -329,7 +329,7 @@ calculate_coefficients_triangle( double *c,

 	sum = 0;
 	for( i = 0; i < n_points; i++ ) {
-		const double xp = (i - half) / shrink;
+		const double xp = (i - half + 0.5) / shrink;

 		double l;

@@ -367,7 +367,7 @@ calculate_coefficients_cubic( double *c,

 	sum = 0;
 	for( i = 0; i < n_points; i++ ) {
-		const double xp = (i - half) / shrink;
+		const double xp = (i - half + 0.5) / shrink;
 		const double axp = VIPS_FABS( xp );
 		const double axp2 = axp * axp;
 		const double axp3 = axp2 * axp;
@@ -416,7 +416,7 @@ calculate_coefficients_lanczos( double *c,

 	sum = 0;
 	for( i = 0; i < n_points; i++ ) {
-		const double xp = (i - half) / shrink;
+		const double xp = (i - half + 0.5) / shrink;

 		double l;

(I'm not sure if this patch could cause regressions, I'll have to check this against this and this repository)
I now see:

/cc @jcupitt as he recently did https://github.com/libvips/libvips/pull/1647.

With commit https://github.com/kleisauke/libvips/commit/18eebf7a9491163d72e07f9c674a9af1c9517a90 (which is included in PR https://github.com/libvips/libvips/pull/1769), I now see:

Output image

Which looks to be the correct output for this image. This change causes no regressions on the above linked repositories. It also seems to improve the 9.4x resize on the pyvips-issue-148 repository, see:

VIPS before
VIPS after

Above border is missing
No missing borders

This sounds great! How ist your process now? will there be a bugfix version?

@markusmoormann Please subscribe to https://github.com/libvips/libvips/pull/1769 for updates.

This is fixed in libvips 8.10.4, which will be included in the prebuilt binaries provided by sharp v0.27.0.

Great! @lovell when will v0.27.0 be released?

sharp v0.27.0 now available with a prebuilt libvips v8.10.5 - thanks for reporting this.

@lovell works flawlessly. Thanks

@lovell works flawlessly. Thanks


Add network types for Windows

r? @Amanieu
(rust-highfive has picked a reviewer for you, use r? to override)

I'm not sure libc is the right crate for these Windows-specific APIs. They are already available on Windows via the winapi crate.

On windows these types are not part of libc (msvcrt) but are part of winsock which is part of the win32 API. I don't think these belong in the libc crate.


Add clue index for across/down mapping help

This is to support tools that may want to manipulate clues based on
whether they are across or down.  I think this would be fairly complex
without this addition.  Maybe there's an easier way.
Here's how the addition here might be used:
def convert_to_downs_only(p):
    for i in map(lambda c: c['clue_index'], p.clue_numbering().across):
        p.clues[i] = '-'

    #  clear any previous cached numbering
    p.helpers.pop('clues', None)

lgtm. thanks for contributing


Per-app plan questions in the Office 365 section

In the "Office 365" section of the document, there are two questions pertaining to per-app licensing: "The Power Apps per app plan allows users to run specific apps. Can you explain what this means in terms of the number and types of apps I can use?" and "Do embedded canvas apps in model-driven apps count toward the two-apps limits?". Am I right that these should be moved into the "General licensing questions" section?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: a2cad5bd-4ffa-3671-0364-95e5b6f65256
Version Independent ID: 6d0cc055-b7be-02d7-3ba8-55e400ccd21b
Content: Power Apps and Power Automate licensing FAQs - Power Platform Admin center
Content Source: power-platform/admin/powerapps-flow-licensing-faq.md
Service: power-platform
GitHub Login: @dileepsinghmicrosoft
Microsoft Alias: dileeps

@rgsteele
Thanks for the suggestion. We've moved the content.


find browser OperaGX failed, profile folder is not exist - Even When Manually entering path

Describe the bug

Auto detecting profile doesnt work nor even entering its location manually it doesnt find profile although i have passwords.db folder also there
Desktop (please complete the following information):

OS Name: Windows 10 Home
Browser Name: Opera GX
Browser Version: 85

Try adding double quotes
hack-browser-data.exe -b opera-gx -p "your-profile-path"

This has been fixed after v0.4.3


[opt](inverted index) Default support support_phrase

Proposed changes

"support_phrase" = "true"
New tables support phrase by default

run buildall

run buildall

run buildall

run buildall

run buildall


Add Carbon Package Namespace to typeMapping

The packages from https://github.com/CarbonPackages have an own namespace to collect these little helpers into one folder. To make sure these get also listed on neos.io, I add the typeMapping neos-carbon

If we merge this we have to accept all kind of packages people would like to add as this is not a "core" package name. But still, the neos documentation says that it's legit to use your own namespace
https://flowframework.readthedocs.io/en/stable/TheDefinitiveGuide/PartIII/PackageManagement.html?highlight=composer type#additional-package-locations

Or we scan also for keywords…

I think it is essential that people find packages who was made for Neos, even with custom namespaces. So yes, we would have to add custom namespaces, or we also scan for keywords in composer.json

I think a search by keyword is not supported by packagists API
https://packagist.org/apidoc

But a search by tags is supported, which is keywords in a composer manifest: https://github.com/Seldaek/monolog/blob/334b8d8783a1262c3b8311d6599889d82e9cc58c/composer.json#L4
Maybe support for that would solve this (sensible!) requirement?

Yeah! But it should be in a way that is an additional search criteria so we don't have to edit all existing core-packages, right?

Yes, of course! It can be as it is now (by the "official" types) and take tags into on top of that.

So we could filter for the keyword neos or should we use neoscms?

I think we should use neos, as well as neoscms as well as flow as well as flowframework. And make sure for all of those results got a package type neos-xy set.

So is anyone into this? I'm (unfortunately) not the php guy, but if I can help somehow, this would be great!

Closing this to clean things up…


Telecast Errors

Hello all! Currently im getting an error message in the DEV Console when trying to telecast and the messages are not popping up.

I tested out a few commands, sent out notifications, took a screenshot. Made sure privacy mode was off for the bot however only thing that seems to fail is the telecast. Attaching config in case its something I missed API keys and names replaced.
{
module: 'MMM-TelegramBot',
config: {
position: "center",
telegramAPIKey : '',
allowedUser : [''],
adminChatId : '',
allowedUser: [""],
useWelcomeMessage: true,
telecast: "*******", // true or chat_id
telecastLife: 60,
telecastLimit: 5,
telecastHideOverflow: false,

commandAllowed: {
"telecast": [""],
"mychatid": [""],
"modules": ["*****"],
}
}
},

telecastLife: 60,

means 60ms and chat will be disappeared
but ... do you want really 60ms !?

Okay, you got me there, SO I upped it to 10000MS just to make sure that wasnt it. Still getting that error message only happens when I send a telecast.  Also uppded the telecastlimit to 500.

i will inspect

Thanks!

hi, inspected, there is some bug but not related to your issue
I think it's just because, you dont set the position of the module
sample
    {
      module: "MMM-TelegramBot",
      position: 'top_center',
      config: {
        telegramAPIKey : "921442896:AAEWU_4-lK5tXuou5f4z_pBS_TONbkryinE",
        allowedUser : ["bugsounet"], // This is NOT the username of bot.
        adminChatId : xxx,
        telecast: xxx,
        useWelcomeMessage: false,
        verbose: false,
      }
    },

and in your config:
you have set the position of the module inside the config {}
{
   module: 'MMM-TelegramBot',
   config: {
     position: "center",
     ...
   }
},


updated readme for composer1.x user

close #55

We should fix the code not the document? But yes, until then it would be great for the user have the problem.
"現在の最新バージョンでは問題のある場合があり、うまくいかない場合は" とか注釈を入れましょうか？

@koriym
I understand composer1.x is outdated today. so we don't have to fix code, I suppose. 🤔
we should focus on new composer2 features instead :sparkles:

注釈

okay, I'll do it at my lunch break today :smile:

@koriym
You also have the warning with Composer 1.x:

PHP Warning:  include(/private/tmp/a/vendor/composer/../composer/InstalledVersions.php): failed to open stream: No such file or directory in /private/tmp/a/vendor/composer/ClassLoader.php on line 444
https://github.com/koriym/Koriym.PhpSkeleton/issues/55#issuecomment-724674839

The warning comes from psalm. Does psalm needs Composer 2.0?

The warning comes from psalm. Does psalm need Composer 2.0?

No.
See my log. I have no warning in the installation of psalm.
The problem is we can not figure out why we have different results with the same command.
 % composer create-project koriym/php-skeleton a
Creating a "koriym/php-skeleton" project at "./a"
Installing koriym/php-skeleton (1.1.6)
  - Installing koriym/php-skeleton (1.1.6): Downloading (100%)
Created project in /private/tmp/a
> Koriym\PhpSkeleton\Installer::preInstall

What is the vendor name?
(MyVendor):
MyVendor

What is the package name?
(MyPackage):
MyPackage

What is your name?
(Akihito Koriyama):
Akihito Koriyama

What is your email address ?
(akihito.koriyama@gmail.com):
<EMAIL_ADDRESS>Loading composer repositories with package information
Updating dependencies (including require-dev)
Package operations: 74 installs, 0 updates, 0 removals
  - Installing composer/package-versions-deprecated (<IP_ADDRESS>): Downloading (100%)
  - Installing squizlabs/php_codesniffer (3.5.8): Loading from cache
  - Installing dealerdirect/phpcodesniffer-composer-installer (v0.7.0): Loading from cache
  - Installing sebastian/version (2.0.1): Loading from cache
  - Installing sebastian/type (1.1.3): Loading from cache
  - Installing sebastian/resource-operations (2.0.1): Loading from cache
  - Installing sebastian/recursion-context (3.0.0): Loading from cache
  - Installing sebastian/object-reflector (1.1.1): Loading from cache
  - Installing sebastian/object-enumerator (3.0.3): Loading from cache
  - Installing sebastian/global-state (3.0.0): Loading from cache
  - Installing sebastian/exporter (3.1.2): Loading from cache
  - Installing sebastian/environment (4.2.3): Loading from cache
  - Installing sebastian/diff (3.0.2): Loading from cache
  - Installing sebastian/comparator (3.0.2): Loading from cache
  - Installing phpunit/php-timer (2.1.2): Loading from cache
  - Installing phpunit/php-text-template (1.2.1): Loading from cache
  - Installing phpunit/php-file-iterator (2.0.2): Loading from cache
  - Installing theseer/tokenizer (1.2.0): Loading from cache
  - Installing sebastian/code-unit-reverse-lookup (1.0.1): Loading from cache
  - Installing phpunit/php-token-stream (3.1.1): Loading from cache
  - Installing phpunit/php-code-coverage (7.0.10): Loading from cache
  - Installing doctrine/instantiator (1.4.0): Downloading (100%)
  - Installing phpdocumentor/reflection-common (2.2.0): Loading from cache
  - Installing symfony/polyfill-ctype (v1.20.0): Loading from cache
  - Installing webmozart/assert (1.9.1): Loading from cache
  - Installing phpdocumentor/type-resolver (1.4.0): Loading from cache
  - Installing phpdocumentor/reflection-docblock (5.2.2): Loading from cache
  - Installing phpspec/prophecy (1.12.1): Loading from cache
  - Installing phar-io/version (2.0.1): Loading from cache
  - Installing phar-io/manifest (1.0.3): Loading from cache
  - Installing myclabs/deep-copy (1.10.1): Loading from cache
  - Installing phpunit/phpunit (8.5.9): Downloading (100%)
  - Installing psr/log (1.1.3): Loading from cache
  - Installing composer/xdebug-handler (1.4.4): Loading from cache
  - Installing symfony/polyfill-php80 (v1.20.0): Loading from cache
  - Installing symfony/filesystem (v5.1.8): Loading from cache
  - Installing symfony/deprecation-contracts (v2.2.0): Loading from cache
  - Installing symfony/config (v5.1.8): Loading from cache
  - Installing psr/container (1.0.0): Loading from cache
  - Installing symfony/service-contracts (v2.2.0): Loading from cache
  - Installing symfony/dependency-injection (v5.1.8): Loading from cache
  - Installing pdepend/pdepend (2.8.0): Loading from cache
  - Installing phpmd/phpmd (2.9.1): Loading from cache
  - Installing phpstan/phpstan (0.12.54): Downloading (100%)
  - Installing webmozart/path-util (2.3.0): Loading from cache
  - Installing symfony/polyfill-mbstring (v1.20.0): Loading from cache
  - Installing symfony/polyfill-intl-normalizer (v1.20.0): Loading from cache
  - Installing symfony/polyfill-intl-grapheme (v1.20.0): Loading from cache
  - Installing symfony/string (v5.1.8): Loading from cache
  - Installing symfony/polyfill-php73 (v1.20.0): Loading from cache
  - Installing symfony/console (v5.1.8): Loading from cache
  - Installing openlss/lib-array2xml (1.0.0): Loading from cache
  - Installing nikic/php-parser (v4.10.2): Loading from cache
  - Installing netresearch/jsonmapper (v2.1.0): Loading from cache
  - Installing felixfbecker/language-server-protocol (v1.5.0): Loading from cache
  - Installing felixfbecker/advanced-json-rpc (v3.1.1): Loading from cache
  - Installing dnoegel/php-xdg-base-dir (v0.1.1): Loading from cache
  - Installing composer/semver (3.2.2): Loading from cache
  - Installing amphp/amp (v2.5.1): Downloading (100%)
  - Installing amphp/byte-stream (v1.8.0): Loading from cache
  - Installing vimeo/psalm (4.1.1): Loading from cache
  - Installing phpmetrics/phpmetrics (v2.7.4): Loading from cache
  - Installing phpstan/phpdoc-parser (0.4.9): Loading from cache
  - Installing slevomat/coding-standard (6.4.1): Loading from cache
  - Installing doctrine/coding-standard (8.2.0): Loading from cache
  - Installing react/promise (v2.8.0): Loading from cache
  - Installing symfony/process (v5.1.8): Loading from cache
  - Installing symfony/finder (v5.1.8): Loading from cache
  - Installing seld/phar-utils (1.1.1): Loading from cache
  - Installing seld/jsonlint (1.8.3): Downloading (100%)
  - Installing justinrainbow/json-schema (5.2.10): Loading from cache
  - Installing composer/spdx-licenses (1.5.4): Loading from cache
  - Installing composer/ca-bundle (1.2.8): Loading from cache
  - Installing composer/composer (2.0.6): Downloading (100%)
sebastian/global-state suggests installing ext-uopz (*)
phpunit/php-code-coverage suggests installing ext-xdebug (^2.7.2)
phpunit/phpunit suggests installing phpunit/php-invoker (^2.0.0)
phpunit/phpunit suggests installing ext-xdebug (*)
symfony/config suggests installing symfony/yaml (To use the yaml reference dumper)
symfony/dependency-injection suggests installing symfony/yaml
symfony/dependency-injection suggests installing symfony/expression-language (For using expressions in service container configuration)
symfony/dependency-injection suggests installing symfony/proxy-manager-bridge (Generate service proxies to lazy load them)
symfony/console suggests installing symfony/event-dispatcher
symfony/console suggests installing symfony/lock
vimeo/psalm suggests installing ext-igbinary (^2.0.5)
Package phpunit/php-token-stream is abandoned, you should avoid using it. No replacement was suggested.
Writing lock file
Generating autoload files
composer/package-versions-deprecated: Generating version class...
composer/package-versions-deprecated: ...done generating version class
31 packages you are using are looking for funding.
Use the `composer fund` command to find out more!
PHP CodeSniffer Config installed_paths set to ../../doctrine/coding-standard/lib,../../slevomat/coding-standard
> Koriym\PhpSkeleton\Installer::postInstall
PHP Warning:  include(/private/tmp/a/vendor/composer/../composer/InstalledVersions.php): failed to open stream: No such file or directory in /private/tmp/a/vendor/composer/ClassLoader.php on line 444
Warning: include(/private/tmp/a/vendor/composer/../composer/InstalledVersions.php): failed to open stream: No such file or directory in /private/tmp/a/vendor/composer/ClassLoader.php on line 444
PHP Warning:  include(): Failed opening '/private/tmp/a/vendor/composer/../composer/InstalledVersions.php' for inclusion (include_path='.:/usr/local/Cellar/php/7.4.12/share/php/pear') in /private/tmp/a/vendor/composer/ClassLoader.php on line 444
Warning: include(): Failed opening '/private/tmp/a/vendor/composer/../composer/InstalledVersions.php' for inclusion (include_path='.:/usr/local/Cellar/php/7.4.12/share/php/pear') in /private/tmp/a/vendor/composer/ClassLoader.php on line 444
Scanning files...
Analyzing files...

░░░
my-vendor/my-package package created.
Happy quality coding!

Merged. But hope we will find the real cause and revert this PR!
@77web @kenjis


Implement Profile Grouping

A second draft of how profile grouping could work.

I improved the sanitization for cities so that about 200 cities that were on a group on their own are now grouped with another city.
I got the execution time down from 60-70ms to around 45ms.
I  managed to get rid off the ruby crutch for the languages by using REGEXP_MATCHES.
I added a way to limit the search for cities by locale

TODO:

We could probably speed it up more by having only one connection to the database (putting all queries in one exec_query-call)
Incorporating a "base query" so we can group on search results instead of the whole database
Decide if you want to show cities with count 1 (I added this to reduce noise and make handling the resulting hash in ruby faster, but now that I think about it: After a search you probably want to see the 1's as well, right?)
 I cherry-picked your commit in this branch https://github.com/rubymonsters/speakerinnen_liste/tree/1316-postgres-search.


model loading too slow

1
You can download it from modelscope.
I have try the AIFSH's package in huggingface and the BAAI's package in modelscope, all of it will crash in 98%, it seem get a wrong shasum, but I don't think it's my net problem.
The AI-ModelScope's package in modelscope is easy to access, I get it directly, no crash.
2
refer AI-ModelScope/OmniGen-v
pip install modelscope
modelscope download --model AI-ModelScope/OmniGen-v1

3
mv it form [/home/user/.cache/modelscope/hub/AI-ModelScope] to your prefer path,
and change the [OmniGen-ComfyUI/init.py],
the path depand your download path.
import sys
import folder_paths
import os.path as osp
now_dir = osp.dirname(__file__)
aifsh_dir = osp.join(folder_paths.models_dir,"AI-ModelScope")
sys.path.append(now_dir)

from huggingface_hub import snapshot_download
omnigen_dir = osp.join(aifsh_dir,"OmniGen-v1")


Fire extension onMouseMove instead of on interval

Currently, the extension is relying on setInterval to determine when to fire. This can cause the function to fire an excessive amount of times even when the page is idle, contributing to CPU usage. The problem is worse when more tabs are opened.
Instead, it's better to fire immediately on mouse move, with a delay if the function had recently been fired.
Doing this also allows the default time delay to be reduced.

I appreciate your help and support.
This way give huge advantage to reduce resource uses :)
I considered short inteveral time also.
But, short inteveral time may cause translate api ban because of too many request.
I will try it to use it but this feature may can be rollback.


tkinter problems

From issue 201, reported by kostik.vento:
While cfd.plot(cumulative=True) works fine, cfd.plot() takes all the
processor's time (more exactly: the graph appeares, but I can't resize it,
nor even minimize it — the window hangs, and the only thing that helps is
to forcingly close the graph window, causing Python Shell's restart). The
screenshot about the problem is attached as cfd.plot.jpg.
But when I try the same code after Python Shell's restart, cfd.plot() works
correctly, so that I can resize the plot's window or minimize it and so on.
I use Python 2.5 on WinXP SP2, if it matters.
Migrated from http://code.google.com/p/nltk/issues/detail?id=250

Closing – too out of date.


Older PARAM.SFO reading problems

I was trying to convert Folklore (BCES00050) using your script, but it stops with the message"Title, category and App_ver missing".
I opened my param.sfo on notepad and app_ver isn't there, but version is.
I changed version to app_ver on my param.sfo and it worked.
So I think you should check for both app_ver and version strings.
Sorry if I sounded rude, English is not my first language
Best regards

Hi im the same problem here with folklore but what do u do? u edited param.sfo just with netepad or with param editor
si hablas español mejor

I edited param.sfo on notepad ++
Just changed "VERSION" to "APP_VER"
Just had the same problem with heavenly sword and fixed it by doing the same thing.

Hi im the same problem here with folklore but what do u do? u edited param.sfo just with netepad or with param editor
si hablas español mejor

many thanks it works!!! i almost get crazy looking for a solution... due to the compatibilty list says Folklore have no installation  issues
i will do the same for heavnly sword and vikings, it may happen with older titles

have you already installed the Folklore dlcs? just install normal or edit the param.sfo

I just installed the dlcs and they are working ok, no problem. Just reassigned the pkg and it was ready to go.
The only thing that I noted is that the version number doesn't appear on PlayStation "information" menu about the game (When you highlight the game and press triangle).
But nonetheless, the game works just fine.
You can try changing back the param.sfo to the original after the conversion is finished.
I didn't test it but it should work okay, since the "Version" attribute just shows info about update, and doesn't direct involve ID or title.
As long as you remember which pkg is installed for that game, you're good to go!

Well i think that the version number is a little issue, what really matters is that the game and dlcs works properly, anyway i will try to changing back to the original param file in Heavenly sword.
i really appreciate your help, have a nice day :)

Should be fixed now with v13, hopefully.


Adds --output-file parameter

Hello,
This allows to (re)generate an arb file with the desired name.
It's useful for automation, and also to avoid wrong locale detection from files called intl_messages.arb because it has an underscore.
It can be called for example messages.arb to avoid auto-detection, or messages_en.arb to force en locale.
I've let this value as the default for backward compatibility,

sorry for #13, I didn't realized commit had to be done with the Google account email

LGTM. Thanks! I'll pull this in through the convoluted way we have of doing this, since the source of truth is in a Google-internal repo and mirrored to here.


Fix polling when provisioning state is null

Description

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] Please add REST spec PR link to the SDK PR
[ ] I have read the contribution guidelines.
[ ] The pull request does not introduce breaking changes.

General Guidelines

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

SDK Generation Guidelines

[ ] If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
[ ] The generate.cmd file for the SDK has been updated with the version of AutoRest, as well as the commitid of your swagger spec or link to the swagger spec, used to generate the code.
[ ] The *.csproj and AssemblyInfo.cs files have been updated with the new version of the SDK.

@jianghaolu closing this PR in lieu of the below PR.
Took this opportunity to clean up duplicate that you had updated for this fix.
Added more tests to cover few additional scenarios. The packages have been published.
https://github.com/Azure/azure-sdk-for-net/pull/4558


Do not run Envoy in prometheus TLS sidecar mode

https://istio.io/latest/docs/ops/integrations/prometheus/#tls-settings in this config we are deploying a full sidecar with envoy, etc. Now we can disable Envoy, so we can clean it up a bit. We may simplify it a bit with https://istio.io/latest/docs/setup/additional-setup/sidecar-injection/#customizing-injection as well possibly

Not stale

@howardjohn i feel like scrape tools + TLS is a hot topic again. should we try to find some cycles to focus on a more holistic approach here?

Do we think we should do a different approach than described here (run sidecar that just provisions a cert)? Or just to actually implement this

Do we think we should do a different approach than described here (run sidecar that just provisions a cert)? Or just to actually implement this

I haven't thought through it enough, but this has come to my attention at least 5 times this week in different contexts. Some people are full-on injecting sidecars, etc., leading to all sorts of issues (and not all are using prometheus). Simplification and better documentation may go a long way.

https://blog.howardjohn.info/posts/securing-prometheus/  (ambient, works today) or https://github.com/istio/istio/issues/36596 (sidecars) are the best option here


Add rethinkdb to travis.yml

Current coverage is 0.00%

Branch #10 has no coverage reports uploaded yet.

No diff could be generated. No reports for develop found.

Powered by Codecov. Updated on successful CI builds.

:+1:


Apply for Approver Role

I would like to nominate myself as a Approver of KubeVela.
I'd be honored if I can continue my contributions as a approver and committed to make the community better.
These are my contributions:
pull requests:

https://github.com/kubevela/kubevela/pull/5189
https://github.com/kubevela/kubevela/pull/5202
https://github.com/kubevela/kubevela/pull/5221
https://github.com/kubevela/kubevela/pull/5325
https://github.com/kubevela/kubevela/pull/5497
https://github.com/kubevela/kubevela/pull/5559
https://github.com/kubevela/kubevela/pull/5646
https://github.com/kubevela/kubevela/pull/5924
https://github.com/kubevela/kubevela/pull/6096
https://github.com/kubevela/kubevela/pull/6207
https://github.com/kubevela/kubevela/pull/6256
https://github.com/kubevela/kubevela/pull/6288
https://github.com/kubevela/catalog/pull/563
https://github.com/kubevela/catalog/pull/570
https://github.com/kubevela/catalog/pull/580
https://github.com/kubevela/catalog/pull/662
https://github.com/kubevela/kubevela.github.io/pull/1082
https://github.com/kubevela/kubevela/pull/6257

issues:

https://github.com/kubevela/kubevela/issues/6208
https://github.com/kubevela/kubevela/issues/6244
https://github.com/kubevela/kubevela/issues/6331
https://github.com/kubevela/kubevela/issues/5148
https://github.com/kubevela/kubevela/issues/5214
https://github.com/kubevela/kubevela/issues/5324
https://github.com/kubevela/kubevela/issues/5467
https://github.com/kubevela/kubevela/issues/5556
https://github.com/kubevela/kubevela/issues/5645
https://github.com/kubevela/kubevela/issues/5750
https://github.com/kubevela/kubevela/issues/6092
https://github.com/kubevela/kubevela/issues/6206
https://github.com/kubevela/kubevela/issues/6255
https://github.com/kubevela/kubevela/issues/6289
https://github.com/kubevela/kubevela/issues/6327
https://github.com/kubevela/catalog/issues/569
https://github.com/kubevela/catalog/issues/576

code reviews:

https://github.com/kubevela/kubevela/pull/6273
https://github.com/kubevela/catalog/pull/725

Thanks for contribution! Hopefully you can contribute more on code reviewing in the future. +1

+1

+1 thanks for your great work!

+1

LGTM, thanks for the contribution!


Share API improvement ideas

@appcypher and I had some ideas on how we could improve the share API.
Consider this a list of "may or may not be a good idea".

We should probably provide a (feature-gated) implementation of ExchangeKey. Feature-gated, because pulling in the RSA dependency may be undesired for WASM, where we might instead want to simply depend on WebCrypto (but in that case this needs re-thinking anyways, since that abstraction would require passing in an object from the JS side, not a static trait).
RsaError should probably be renamed to something more abstract when we add other protocols (e.g. Ed25519)
We should compute find_current_share_counter for the user (by default, at least). It can be made faster by caching previous results, but that doesn't mean the default case needs to be a more complicated API.
We probably don't need the Share struct. The share function is just fine. This struct was deleted.
Perhaps it's also possible to remove the receiver and sender modules, and simply merge them all into the share module.

Currently it's necessary to keep a global counter because of some issues with the API. The share() function expects a counter but a counter depends on a public key and a DID, the function however retrieves the public keys for you; so it would make sense if the share function also figured out the counter for you. The counter should be returned to the use.
That said, I think the counter should be the same for all the public keys in the same share. Reason being that the user will need to use the counter to retrieve older shares (ie. not the latest) (retrieving a share automatically uses the last counter).
Also, fetch_exchange_keys is missing on the wasm side.


anonymize inspect on users

In order to avoid accidentally compromising user identity when demoing or livestreaming, it would be nice to customize the inspect method for users to eliminate the first_name, last_name, apartment, and email attributes.

This was done a while ago, not sure what the commit hash for it was.


Initialize with a lock

Initialize worker instance using the autumndb migration functionality.
This gives us a system-wide db lock, ensuring that only a single
instance upserts contracts on boot.
Change-type: patch
Signed-off-by: Josh Bowling<EMAIL_ADDRESS>
Depends on:

https://github.com/product-os/autumndb/pull/1460

@Ereski Looking to piggy back off of the existing migrations functionality in autumndb to get system-wide db locks during backend init (only have a single instance do things that only need to be done once during boot). I looked at using the Context argument provided to the migration callback to ensure everything is done within the same transaction, but it was more trouble than it was worth as all I really need is the single lock on the record in the migrations table to ensure only one starting instance executes the callback. Let me know what you think, the autumndb PR this depends on is linked in the description above.

About the "running migrations on a transaction" issue. I think it would help to decide to know what happens if there's an error during the migration; let's say the migration for a contract on a plugin fails. What would happen with the changes on this PR and what would happen with the current version? I think if we keep the current behavior, then it would be ok.

Another aspect I was thinking about: what happens with the other workers in JF or the other instances that run the migration concurrently?
autumndb does a SELECT FOR UPDATE but not a SELECT FOR UPDATE NOWAIT. Do the other workers/peers wait for the first one to finish? If we want to avoid collisions I think it's ok, but maybe it'd be helpful to explain on a comment

autumndb does a SELECT FOR UPDATE but not a SELECT FOR UPDATE NOWAIT. Do the other workers/peers wait for the first one to finish? If we want to avoid collisions I think it's ok, but maybe it'd be helpful to explain on a comment

I didn't create the original migration code in autumndb so I can't give a full reason as to why NOWAIT isn't included, but I believe its intentional. We don't necessarily want the backend to attempt to run if the database isn't prepared, so my understanding is that we shouldn't include NOWAIT.

@balena-ci retest

@balena-ci retest

@balena-ci retest

I'm off for the next two weeks, will push this through when I get back.

@ramirogm What do you think about giving this a go? Any other issues/comments about the PR?


Use decodeURIComponent for window.location.search

decodeURI does not decode certain characters (&,@ etc) so query strings involving these characters are returned partially decoded

v0.13.x is no longer supported. Barring extraordinary circumstances there's not going to be another release, so there's no point in merging this.


Remove redundant argument and improve error message

Which issue does this PR close?
None
Rationale for this change
Simplify the code
What changes are included in this PR?
Remove redundant argument and improve error message
Are these changes tested?
No
Are there any user-facing changes?
No

@comphead would you want to take a look? thanks!

thanks, updated!


What about replacing underscore with Lodash?

Lodash is a lighter drop-in replacement for Underscore. It's worth it

Also  https://github.com/lodash/babel-plugin-lodash

At the time I was actively developing the project, Lodash seemed to me an overkill with all it's lots of features. Maybe, some day I will use it, but I believe that will not change anything much.

Thank you for your response


Alert countdown does not start

Describe the bug
Using a dismissable alert with countdown does only work if the v-model ref is changed after the alert is initialized.
Having the variable already set at some value will have the timer never start
To Reproduce
https://stackblitz.com/edit/vue-wdw4g9?file=src%2Fcomponents%2FHelloWorld.vue
The stackblitz shows the sample from the documentation - except that dismissCountDown is now initialized to dismissSecs
const dismissCountDown = ref(dismissSecs);
Expected behavior
Timer should start the moment the alert is shown - hiding the alert afterwards
Environment (please complete the following information):

OS: [e.g. Windows 11]
Version [e.g. 0.2.6] 0.4.8

Additional context
This is obviously a usecase that could be covered by an onMounted hook - however my aim is to show a list of alerts (which are created as part of a v-for loop) - so i don't really have the possibility to change the value of the ref after initialization.

Hi , a simple fix is on the way.


Add locale format option LY for MM/DD/YY in en and en-gb

PR for Issue https://github.com/moment/moment/issues/2158 (Localized MM/DD/YY)
Changes Summary

Adds locale format option LY to format date as:

MM/DD/YY in en
DD/MM/YY in en-gb (cc: locale author, @chrisgedrim)

Includes corresponding tests.  grunt test output screenshot below.

I should know the answer to this, but what happens if you try to use LY in a locale where it's not supported?

If I remember correctly you'll get the Y treated as a literal.
According to the docs you can overload/extend default values:
moment.locale('xx', {
    longDateFormat : {
        LY : "DD/MM/YYYY"
    }
});

However a quick and dirty test in the console seemed to imply it doesn't work like that:
> moment.locale('sv')
< "sv"
---
> moment().format('LY')
< "2015-11-26Y"
---
> moment.locale('sv', {
      longDateFormat : {
          LY : "DD/MM/YYYY"
      }
  });
< "sv"
---
> moment().format('LY')
< "LY"

Yeah, as @chrisgedrim said, it would return LY...same as it would if you passed in any other unsupported format string. Is this okay? It's my first PR, so feel free to provide input.
> moment.locale('sv')
< "sv"
> moment().format('LY')
< "LY"
> moment().format('O')
< "O"

For reference, the last added format string was LTS last year (pull #2000) where all locales were added in one go.

Yeah, I think we need to have something for everyone or it will just cause confusion. Ideally, Moment would work by having everything "inherit" from, say, "en-us", but that's not currently how it works. @ichernev - what's the policy here? Does he need to go through each locale, add a format string for "LY" and a test?
FWIW, I ran locales from here (which I'm not sure is up-to-date WRT what Moment actually supports) through my fancy modern browser's built-in i8tl support, and it gave me this:
af 15-12-03
ar ٣/١٢/١٥
ar-ma ٣/١٢/١٥
ar-sa ٣/١٢/١٥
ar-tn ٣/١٢/١٥
az 15-12-03
be 15-12-03
bg 3.12.15 г.
bn ৩/১২/১৫
bo 12/3/15
br 15-12-03
bs 15-12-03
ca 3/12/15
cs 3. 12. 15
cv 12/3/15
cy 15-12-03
da 3/12/15
de 3.12.15
de-at 3.12.15
el 3/12/15
en 12/3/15
en-au 3/12/15
en-ca 15-12-03
en-gb 03/12/15
eo 15-12-03
es 3/12/15
et 3.12.15
eu 15-12-03
fa ۹۴/۹/۱۲ ه.ش.
fi 3.12.15
fo 15-12-03
fr 3/12/15
fr-ca 15-12-03
fy 12/3/15
gl 15-12-03
he 3.12.15
hi 3/12/15
hr 03.12.15.
hu 15. 12. 03.
hy-am 15-12-03
id 3/12/15
is 15-12-03
it 3/12/15
ja 15/12/3
ka 15-12-03
km 15-12-03
ko 15. 12. 3.
lb 12/3/15
lt 15-12-03
lv 3.12.15.
me 12/3/15
mk 15-12-03
ml 3/12/15
mr ३/१२/१५
ms-my 3/12/15
my 15-12-03
nb 3.12.15
ne 15-12-03
nl 3-12-15
nn 15-12-03
pl 3.12.15
pt 03/12/15
pt-br 03/12/15
ro 03.12.15
ru 03.12.15
sk 3. 12. 15
sl 3. 12. 15
sq 15-12-03
sr 3.12.15.
sr-cyrl 3.12.15.
sv 15-12-03
ta 3-12-15
th 3/12/58
tl-ph 12/3/15
tr 03.12.15
tzm 12/3/15
tzm-latn 12/3/15
uk 03.12.15
uz 15-12-03
vi 3/12/15
zh-cn 15/12/3
zh-tw 15/12/3

Ah great stuff - thanks for the info! I'm more than happy to add these in. I'll update this over the next week.

@icambron that is why we don't change tokens very often. I just implemented locale inheritance, but all locales inheriting from the en one should be done implicit, not explicit.
@blankmaker if you wait until locale inheritance and basing everything off english gets merged it will save you a lot of work.

:+1: sounds good

I haven't dug deeply into the implications of this pull request, but I want to note that locale inheritance went out with 2.12.0. Where does that leave this?

@maggiepint apologies for the delay in reply. I'll close this PR so that this issue doesn't get blocked. Unfortunately, I haven't been able to dig into locale inheritance yet. Thanks!

@blankmaker , it's not blocking anything. I just wanted to know whether that allows this to progress.

@maggiepint tbh, I haven't kept up-to-date with locale inheritance so I'm not sure. I closed this in case anyone wanted to take up https://github.com/moment/moment/issues/2158 as I haven't gotten around to digging into it.


Can you upload version 0.3.11 to pypi?

Hey @jasonkeene, made an upgrade for Python3.5.  Tests are running.  I don't have permission to upload to pypi though.
Could you upload it or transfer ownership?  Thanks.
Hope all is well in CO :smile:

What's your PyPI username? I'll add you as maintainer.

@Kazanz shoot me an email if you still need access.

I went ahead and uploaded 0.3.11 to PyPI today.


Error name before Agree to the rules before downloading data.

When you are trying to download data for Kaggle InClass (for instance https://www.kaggle.com/c/catch-me-if-you-can-intruder-detection-through-webpage-session-tracking2/data) it give an error 403 before accepting rules of competition.
I believe this should be said directly in error message.

We improved the error messages in the latest release.


fix(documentation): broken links

Changes proposed in this pull request

fixes some broken doc links

Context

follow up on https://github.com/interledger/rafiki/issues/2242. A helpful contributor fixed some which closed the issue, and this is fixing the remaining.
Checklist

[x] Related issues linked using fixes #number
[ ] Tests added/updated
[x] Documentation added
[ ] Make sure that all checks pass
[ ] Postman collection updated

@huijing is there a way we can fail builds in astro if there are broken links?


Configurable app-serve protocol meteor://

It could be greate if the app serve protocol meteor://  be user configurable, with a default of meteor://  probably via setting.json  variable.
Scenario
A scenario affecting this is where user has Iframes  in the app , and the Iframes are CSP (Content-Security-Policy) configured to allow subset of origin

That would be a good idea, maybe this helps to solve this another  issue

That would be a good idea, maybe this helps to solve this another  issue


As a developer, I would like to refactor the data persistence solution, in order to read and save data more streamlined

Refactor data persistence to library project SimpleDB, using an generic interface and class with two methods read and store.
Acceptance criteria: Read and write data from SimpleDB using the two methods.

Created the empty shell for the generic interface and CSV specific class. When ready the CSV function needs to be moved to CSVDatabase class.

Review changes made in SimpleDBIntergration branch


Update tools-version

Would you be able to update the Travis configuration? I think it's still on Xcode 9 which won't support Swift 5+


fix Dockerfile, seems that new flask does not have JSONEncoder

https://flask.palletsprojects.com/en/2.3.x/changes/
2.3.0 -> json_encoder and json_decoder attributes on app and blueprint, and the corresponding json.JSONEncoder and JSONDecoder classes, are removed.

Thanks @mach0 I see now that this is due to flassger which we don't really need, since we're not offering a public documented API yet.
A better way out would actually maybe to use this new functionality and ship with orjson because especially for the bsdd part we're quite dependent on json serialization performance. But for now I'll merge this in.


Error on running 'who'

Hi,
I cannot successfully run the command  python runfuzzer.py -s '/PATH_TO_vuzzer-code/bin/who %s' -i 'datatemp/utmp/' -w 'idafiles/who.pkl' -n idafiles/who.names -o '0x00000000', which is provided in the wikiHOWTO.md.
The error is
Traceback (most recent call last):
File "/usr/lib/python2.7/threading.py", line 810, in __bootstrap_inner
self.run()
File "/usr/lib/python2.7/threading.py", line 763, in run
self.__target(*self.__args, **self.__kwargs)
File "runfuzzer.py", line 631, in main
gbb,bbb=dry_run()
File "runfuzzer.py", line 475, in dry_run
(bbs,retc)=execute(tfl)
File "runfuzzer.py", line 155, in execute
bbs = bbdict(config.BBOUT)
File "runfuzzer.py", line 77, in bbdict
with open(config.BBOUT,"r") as bbFD:
IOError: [Errno 2] No such file or directory: '/xxx/vuzzer/outd/bbc.out'
I think bbc.out should be an output file, so any hint on how this happen and how to fix it?
Thanks.

i my guess is: your pintool is not executing the application and therefore bbc.out is not getting generated. Just check if you can run pintool separately.

@tosanjay Thanks for your quick reply.
I tried the PIN, it is not executing because of the kernel version is too high. After I downgrade the kernel version, the PIN and the sample command could be successfully executed.
However, I have the same problem when I run the program with library in it.  The following is the command I run. Another problem is that after run the command first time, get 'load address changed..run again!', the content of imageOffset.text is Main: 0x00000000, the library address is not in this file. There is an address 0xb6553000 in the file image.offset, so I use this address as the library address, I am not sure if this is correct.
python runfuzzer.py -s './bin/tiff2pdf %s -o result.pdf' \
 -i 'datatemp/tiff2pdftemp/' \
 -w './idafiles/tiff2pdf.pkl,./idafiles/libtiff.so.pkl' \
 -n './idafiles/tiff2pdf.names,./idafiles/libtiff.so.names' \
 -l 2 \
 -o '0x00000000, 0xb6553000' \
 -b 'tiff'

Thanks

As before, if pin is not able to run the application, it is difficult to move forward. can you run the application directly with pintool as follows:
$pin -tool_exit_timeout 1 -t pintool-path -o path-to-bbc.out -x 0 -libc 0-l "libtiff" -- your utility commandline
as you can see, i used lib name with full prefix.
let me know what do you get.

It works, thank you so much for your help. The pin command could work. After I change the lib name with full prefix, it fails on the first time I run it with the same error, success on the second time.
During the runtime, vuzzer print out some error blocks. What are those error blocks? Would these error blocks have any influence on result?

Glad that it worked. for the other query on error BB, please read the VUzzer paper, presented at NDSS'17.


Design and Structure Changes

Just changed a bit of designing and content structure. Please take a look :)

Hey @skks1212 , I reviewed your pull request and I can see you have done a nice work structuring the site but can you explain why you are going for an approach which loads html files through AJAX requests? I saw that you are going for a component based approach and I want to understand a little bit more about it. Looking forward to your response! Thanks.

Hey @skks1212 , I reviewed your pull request and I can see you have done a nice work structuring the site but can you explain why you are going for an approach which loads html files through AJAX requests? I saw that you are going for a component based approach and I want to understand a little bit more about it. Looking forward to your response! Thanks.

We are are using vanilla js. We don't have any backend to support components and views etc.
Loading components this way might be a bottleneck for a one page website, but as you have indicated, this will prove to be fruitful once we expand the number of pages. So rather than writing the same code for each HTML page, why not use up the same components.
Another plus point is that it helps to keep code segmented. Less spaghetti.


Bump to Ansible 2.6 and Molecule 2

As discussed earlier today, this new set of requirements supersedes the ones previously proposed in #10.

Now released as https://pypi.org/project/ome-ansible-molecule/0.4.0/. I will look into whether PyPI has some mechanism to annotate a project as superseded by another. Otherwise, might create a final 0.3.2 release on https://pypi.org/project/ome-ansible-molecule-dependencies/ to indicate the new meta-package should be used instead.


Havells inverter (rebranded sofar)

My logger serial  number starts from 29xxxxx, I have tried everything from downgrading to 1.4.3, tried evert yaml config. I alwats get querying registers failed, aborting.

Is this a new integration or has this been working and now stopped working? Debug log around the point where 'querying registers failed' occurs would give more hints what might be wrong.


[INFRA] Does skywalking-eyes support resolve license dependencies from pom.xml

Please answer these questions before submitting your issue.

Why do you submit this issue?
[x] Question or discussion
[ ] Bug
[ ] Requirement
[ ] Feature or performance improvement

Question

What do you want to know?
When I browsed the skywalking-eyes code, I found that the interface Resolve only have GoModResolver one kind of implementation.
Does this mean that skywalking-eyes can currently only resolve dependencies from the .mod file and not support resolve from pom.xml.

Duplicate with #7311


[flaky-test] test_mcapp_rollback_validation test failure

Flaky Test
tests/integration/suite/test_multi_cluster_app.py - test_mcapp_rollback_validation

Release Branch
source branch of PR: release/v2.7
Drone Build (if applicable)
pipeline stage URL: https://drone-pr.rancher.io/rancher/rancher/31076/5/2

Another pipeline failure related to the same issue:

https://drone-pr.rancher.io/rancher/rancher/31411/5/2


Validate orphan block pos

Current dependencies on/for this PR:

feature/pos-fast-hotstuff-consensus

PR #742

PR #746

PR #747

PR #748

PR #749

PR #751   👈

This comment was auto-generated by Graphite.


Fix verigreen Dockerfile to use $APP_DIR instead of $VG_ROOT as WORKDIR

$VG_ROOT was replaced with $APP_DIR in the new version of verigreen docker image

we will take a look


[Bug]

Bug report
I can't delete text in the field (translatable)
What I did
I edited one translatable field and wanted to delete the text in this field. After pushing the button "save and back" was the same text in the field.
What I expected to happen
I expected to see the empty field.
What happened
the text wasn't deleted.
What I've already tried to fix it
debugged in HasTranslations.php, another field saves the information correctly with translation into 2 languages, but this field not.
Is it a bug in the latest version of Backpack?
Yes
After I run composer update backpack/crud the bug... is it still there?
Yes
Backpack, Laravel, PHP, DB version
4.1.64, v8.69.0 ,  7.4.24 , 10.3.31-MariaDB-0ubuntu<IP_ADDRESS>
When I run php artisan backpack:version the output is:
PHP VERSION:
PHP 7.4.24 (cli) (built: Sep 23 2021 21:36:11) ( NTS )
Copyright (c) The PHP Group
Zend Engine v3.4.0, Copyright (c) Zend Technologies
with Zend OPcache v7.4.24, Copyright (c), by Zend Technologies
with Xdebug v3.0.4, Copyright (c) 2002-2021, by Derick Rethans
LARAVEL VERSION:
v8.69.0@545181da688db64fed6d8427e55f630a90ca0d32
BACKPACK VERSION:
4.1.64@e49566ebd4a55e6849ef7e88822e53195719e2b8

Problem seems to be, that the fallback language is pulled. It's a big confusing but might not be an actual bug.
I might be good to be able to set a field explicitly to "empty" in a derived language to stop using the fallback though.

Totally agree, it's a bug. Just talked to @pxpm yesterday and settled on a way to solve this in a non-breaking way:

when you open the Edit form, when a translation doesn't exit, the fields are all empty
a new alert/button shows up at the top, same line as the language picker, that says something like "This entry has not been translated to this language yet. << Import texts from English >>"
if you click that button, it will add ?fallback_locale=true to the URL so you'll see the texts from the fallback language, to quickly translate them
click Save

This will basically make the "populate with English" functionality OPTIONAL instead of DEFAULT.

Fixed by https://github.com/Laravel-Backpack/CRUD/pull/4267 which will be polished and merged soon. Let's move the conversation there please 🙏
Thanks for opening this issue @Svetlana-Pribylova


Question: How is date modified supposed to work?

What you would like to know more about...
When I use YAML Timestamp >> Date Modified the first time YAML is inserted, it grabs the last modified date/time from the file metadata. However, if this feature is turned on when linting the file in the future, the "date modified" is the same date/time as the lint that just occurred. That is: linting counts as the last modification to the file.
I get it...but that's more literal than I think it should be. I want it to grab the last time I modified the file myself, not the moment the file was linted.
Is this a bug, a feature, or user error?

That is a feature. There are new docs available to explain it here: https://platers.github.io/obsidian-linter/settings/yaml-rules/#date-modified-value-origin
Please let me know if that makes sense or if something needs clarification still.

Thank you! I am only unclear on one part of the description:

As such, the date modified is the time the Linter needs to update the file via any rule except Custom Commands.

What does "needs to update" mean, exactly?
Is there some exception here with Custom Commands that would be useful to understand?

Just want to say how AWESOME this plugin is. It is an absolute godsend as I'm trying to refactor my vault. Thank you.

I am glad that it is useful!
"needs to update" means that the Linter rule for updating date modified is active and a change has been made in the file, the date modified is not in the specified format, the date modified is missing, or the date modified is more than 5 seconds from the time the file's metadata says.
Aa for custom commands, there is nothing the Linter can do around updating the date modified of a file when custom commands run. They are responsible for doing any updates needed there with no later input from the Linter. So if custom commands modify a file, the date modified is not updated in the file until the next time the Linter is run.

Just as a heads up @kalico1 , I plan to close this question come Wednesday if there are no followup questions.


fix: cannot find startswith of undefined

What kind of change does this PR introduce?
bugfix

Did you add tests for your changes?
No
If relevant, did you update the documentation?
NA
Summary
As we have configured selectors based upon object keys in some condition object properties is not defined, thus the selector resolves to undefined, i.e. await page.waitForSelector(undefined); This results in the following error:
Cannot read property 'startsWith' of undefined

Does this PR introduce a breaking change?
No

Other information

Closing !! as not in a CLA list


discordapp.com flagged as malicious [false positive]

This time it's "discordapp.co" (Line 1277) that matches part of the url. You might want to use some regex to extract the URLs and match the entirety of the URL

I see.
will remove the domain. I currently can't think of a solution that works for all the domains, my current regex skills are not that good sadly


Unexpected behavior in Time-Input onBlur event

Bug Report
Description
I encountered two issues with the 12-hour terra-time-input component:

Although an onBlur event is triggered when the hours loses focus and when the minutes loses focus, no onBlur is triggered when the meridiem loses focus.
There is no separate event that is triggered when leaving the time-input component as a whole, only from each field within the component.
This is a problem when validation logic is performed on an onBlur event. Since the onBlur event is fired while the user is still editing the time value, the validation logic is performed too soon, causing premature errors.

Steps to Reproduce

Focus into the time input component and enter hours. onBlur event is triggered. Enter minutes. onBlur event is triggered. Enter meridiem and remove focus from the meridiem. No onBlur event is triggered. In the example below, each onBlur event generates a printed line in the Console. No line is printed when tabbing off the meridiem.
Observe that the onBlur event is triggered when focus is removed from the hours or minutes but remains within the component. No onBlur event occurs when the TimeInput element as a whole loses focus.

Screen recordings

No onBlur fired when meridiem loses focus

onBlur event is fired while focus is still in component

Expected Behavior
The onblur event should be triggered only when when the TimeInput as a whole loses focus.
Possible Solution
When each individual section loses focus, that can trigger separate events, i.e. onBlurHours, onBlurMinutes, onBlurMeridiem.

These issues have been resolved by #588 and #837


firewalld: 2.1.2 -> 2.2.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/firewalld/versions.
meta.description for firewalld is: Firewall daemon with D-Bus interface
meta.homepage for firewalld is: https://github.com/firewalld/firewalld
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.2.0 with grep in /nix/store/aq9jnnczh3pld3irn57hg5y4dg11cgg9-firewalld-2.2.0
found 2.2.0 in filename of file in /nix/store/aq9jnnczh3pld3irn57hg5y4dg11cgg9-firewalld-2.2.0

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

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath

firewalld
firewalld-gui

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/aq9jnnczh3pld3irn57hg5y4dg11cgg9-firewalld-2.2.0 \
  --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 firewalld https://github.com/r-ryantm/nixpkgs/archive/903a80fbe5298ef90c39d7f32bb73853fe72c1c7.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/903a80fbe5298ef90c39d7f32bb73853fe72c1c7#firewalld

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

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

2 packages built:

firewalld
firewalld-gui

Maintainer pings

done in https://github.com/NixOS/nixpkgs/pull/326452


Cors setting

How to set up the Cors option in the SwiftR Mac Demo?
I tried your demo and I got "Error during negotiation request." message.
Thanks,
Joseph

The iOS demo talks to http://swiftr.azurewebsites.net. The macOS demo is expecting some local SignalR server. CORS only needs to be configured on the server.


ClientConstants.js missing entries

Description
A transaction generated by a node.js backend fails to be processed by a wallet with an 'invalid node account id' error.
The transaction specified node account id 0.0.18 which is a valid consensus node, however the ClientConstants.js doesn't have an entry for this node accountId, it goes from 17 to 19, skipping 18 altogether
https://github.com/hashgraph/hedera-sdk-js/blob/develop/src/constants/ClientConstants.js
    "https://node14.swirldslabs.com:443": new AccountId(17),
    "https://node16.swirldslabs.com:443": new AccountId(19),

Also note that the list of consensus nodes https://docs.hedera.com/hedera/networks/mainnet/mainnet-nodes goes up to node account id 0.0.31, the constants file stops at 0.0.29.
Steps to reproduce
Generate a transaction which specifies account id 0.0.18 for the node_account_id, attempt to sign and execute the transaction in a web client, it will fail.
Additional context
No response
Hedera network
mainnet
Version
2.29
Operating system
None

Noting here that 0.0.31 and 0.0.30 do not currently have a gRPC web proxy set up. Once this service is available we will add them to the SDKs. DevOps will note when available.