Fixing up consumer example confusion.

Coverage increased (+0.05%) to 92.4% when pulling 552ec2b78c73a57aa7fb13b11341fdd782dd66d4 on Interrupt:master into dd74d9473692080cf49d3740eb3d7d929e79e1c9 on bpot:master.

Coverage increased (+0.05%) to 92.4% when pulling 552ec2b78c73a57aa7fb13b11341fdd782dd66d4 on Interrupt:master into dd74d9473692080cf49d3740eb3d7d929e79e1c9 on bpot:master.


Per-VPC docker registries

Configuring the local registry as a pull-through cache while retaining security is going to require more work/research.  See: https://github.com/docker/distribution/issues/1486


Limit full scan run on Zuul on PRs to main

Currently, even a commit with a LICENSE update triggers the full run of Zuul pipelines. We should limit this to only run, when relevant files are going to be merged onto main.

this is not a problem right now - test cloud is not providing working VMs as of now and as such all jobs running on VMs are not able to start.

Fixed with #20


Exercise accepts Pixel and Percentage answer due to image dimensions

Challenge http://www.freecodecamp.com/challenges/waypoint-make-circular-images-with-a-border-radius has an issue. Please describe how to reproduce it, and include links to screen shots if possible.
For this exercise someone may accidentally use 50px instead of 50% and think it's Ok though the exercise calls for percentage. It just so happens to work for this exercise because the image is 100px and of course 50px is 50% of 100px. Really minor issue as I think everyone would figure this out during the exercise or when it comes up again.
Sorry if this has been mentioned already; learning Git Hub

I think this was fixed in 1002 tonight by Quincy.  Wish  there was some way to link this to that one.

..sorry, seeing this late, thanks guys!


miri: implement most floating point math operations using soft floats

This is a preview of how it would look to implement math intrinsics using soft floats.
Deterministic non-determinism (this.machine.rng) is used to apply some random error to the results to model the non-guaranteed precision (except for sqrt).
cc https://github.com/rust-lang/miri/issues/3898

As already mentioned, my main concern here is about pulling in a not-widely-used (and not-widely-vetted) third-party dependency to fix something that's not fundamentally wrong. The only part of this that is a bugfix is using a softfloat implementation for sqrt.
How large is an sqrt implementation built directly on rustc_apfloat, and could we reasonably carry it in-tree?

:umbrella: The latest upstream changes (presumably #4009) made this pull request unmergeable. Please resolve the merge conflicts.


Added handling of None values in cache

This adds handling of None values. Use case is:
Sample memoized function like:
   @memoize(timeout=100)
   def sample(param):
       return Model.objects.filter(field=param).first()

In case sample function returns None this None is stored in the cache by memoize. However in case of further calls to the sample function, memoize internally does rv = self.get(...) and then if rv is None: then execute function again. This means it treats None as no value in cache. Provided fix changes this behaviour to clearly differentiate between "no value in cache" and "None in cache" situations.

Coverage remained the same at 87.793% when pulling 1d401f81159326724addbee9ade8e2a30395a316 on restless:master into e4c9afcd26fb3934be49c17af5612aa2f20fa413 on tvavrys:master.

Duplicate of #17 . Closing. Done.


completing purchase =order for  Virtual parts fails.

Please verify that this feature request has NOT been suggested before.

[X] I checked and didn't find a similar feature request

Problem statement
Hi i have a virtual part, a SW licence that i need to purchase and sell along with a product. so i create a SW lic.
So i create a part ProduuctX FW Lic. make it a component, Purchaseable, Virtual and Active. so far so good
when i look a the BOM for the product requiring this lic. i can see that since i have no stock i can not build the part. hence i create a purchase order and send it out. next i go for received items and mar it as cpompleted i received all  qty.
but now im not able to proceed. the form says ....
i had to go back in the part and disable virtual to complete the order
Suggested solution
a virtual component should either be A treated as a normal part or should not be blocking the build. or i am missiing something. if so please add this to the help file or prefereable to the text when hoovering above the virutal
Describe alternatives you've considered
made it non virtual
Examples of other systems
No response
Do you want to develop this?

[ ] I want to develop this.

This is probably more of a higher level discussion of what a virtual part "means", and what actions should be made available for virtual parts. Currently some actions are prohibited for parts which are marked as virtual (e.g. purchase orders) but this is not necessarily the best approach.
I'd be interested in feedback on how people use virtual parts, or would intent to use them

A virtual part to me would like the comment stated before as example a SW license which I:
need to purchase and sell along with the product
do not need to purchase but still sell since i made it my self
so a virtual part for me is like a normal part except for the fact that i might not care how many i have in stock. so the BOM does not complain i can not build it.
currently i can not close the form if it has a virtual part in. then you get an error.
Br Martijn

Just found a similar issue with virtual parts in Sales Orders: I would like to use virtual parts for non-physical items like a hourly rate for design work or a technical service fee for example. But I cannot add virtual parts as line items to a Sales Order currently.
I would agree with @mabroens on the definition that virtual parts should mainly just not have any stock management - but they can be purchasable and salable if defined as such.
@SchrodingersGat I could take a look into the changes necessary, if you share this objective...

The issue there is that purchase and sales order require stock, either incoming or outgoing. So, some other considerations would then have to be made, if you want to be able to assign "stock" (which doesn't exist for a virtual part) to a sales order

Well, I see your point... Thinking about that a bit further I realize that it might be actually beneficial for our internal processes to not use virtual parts for these items, but instead just use regular "parts/assemblies" that have a measurement unit of "hours" for example. The advantage would be that I can issue build orders for these (in the meaning of "work orders") in order to assign them to users or departments.
The "build output" is measured in hours then and can be used like physical stock items for completing a sales order.
I will give that a proper test here, so for now I suggest we can close the issue again.


Plans on supporting GMS?

Hey, I know I'm getting ahead of myself, but if Nexon releases the API for GMS, do you plan on supporting it? I'm building a calculator/simulator website, and if you do plan on supporting it I could start ahead of the launch with your interfaces and everything.

@hyoretsu Hello, Maple Adventurer of another world!
If Nexon releases the GMS API and the interfaces don't undergo significant changes, I'd be happy to assist and support you.

Nexon has opened the Global API, but GMS doesn't seem to support it yet.  I hope this will be released soon.
https://openapi.nexon.com/support/notice/2597245/


add support of linux/ppc64le and linux/arm64

the build log shows that the builds were success,
but the push failed because the images were pushed from the chhsiao1981 repo, not from the FNNDSC repo.
We should pass this merge.


Update picobrew_api.py

In the latest Zymatic FW (1.1.14), uses Get  /API/SyncUSer and not Get  /API/SyncUser

Thanks for the PR.


Add working Linux tests

As with Graphiti, GraphQL does not have working Linux tests.
This PR resolves this.

The thread sanitizer is complaining.

Removed the thread sanitizer. Issues are with Runtime package and cannot be resolved here. I've added an issue https://github.com/wickwirew/Runtime/issues/87

Is there any reason GraphQL doesn't use Mirror instead of the Runtime package?

Back then, Mirror wasn't powerful enough! Do you reckon it is possible to replace Runtime with Mirror? I haven't heard of any updates regarding reflection in Swift. I'd love to simplify the codebase and remove the dependency, if possible.

Back then, Mirror wasn't powerful enough! Do you reckon it is possible to replace Runtime with Mirror? I haven't heard of any updates regarding reflection in Swift. I'd love to simplify the codebase and remove the dependency, if possible.

All you seem to be using it for is extracting values out of a type using the variable name. I'll add a PR to demonstrate

@adam-fowler I think updating from master should solve the issue with GH actions.

Basically adding the macos-latest?

@paulofaria This change will need a change to the required tests.
The ubuntu tests you had before didn't test anything. This is why I added this PR. But the change uses the swift docker images which have different names to the ubuntu images required at the moment. The swift docker images are better to use because we can be specific about which version of swift we want running.
As an aside isn't macos-10.15 the same as macos-latest?

As an aside isn't macos-10.15 the same as macos-latest?
@adam-fowler Yeah, I think so. @alexsteinerde might chime in and let us know why adding "macos-latest" fixes the GH actions stall issue. If changing to "macos-latest" and removing macos-10.15 works, I'm cool with just using "macos-latest".

@adam-fowler With this change, should we remove the ubuntu items from this line in the existing workflow yml?

Looks like it needs updated to support 5.5 and 5.6. Although since I posted the new swift install actions are available which could simplify this more. I'll rebuild this using them.

Can we get rid of the required tests Build and test on macos-10.15 and Build and test on ubuntu-18.04. @NeedleInAJayStack don't know if you have the power. Maybe @paulofaria can do this.

Added @NeedleInAJayStack to the admins team. He should have full access now.

Closed by accident.

Hm, not sure how I can get rid of that? Maybe we should force merge, then that requirement will be gone, since it won't be in the yml file anymore? This looks like a GH bug, I reckon.

Hm, not sure how I can get rid of that? Maybe we should force merge, then that requirement will be gone, since it won't be in the yml file anymore? This looks like a GH bug, I reckon.

It is in the settings for the project (something only admins can access). Do you have branch protection setup?

I've removed Build and test on macos-10.15 and Build and test on ubuntu-18.04 from the master branch protection rules

Scratch that - I've changed the branch protection rules to be the actions that ran when this was merged to master. Specifically, the actions required are:

Build and test on macos-latest
Build 5.4 on ubuntu-latest
Build 5.5 on ubuntu-latest
Build 5.6 on ubuntu-latest

I think it's pretty pointless adding required builds. You already require an admin approval. Also the required builds will change overtime as new versions of swift are released.
Swift NIO is only ever planning to support the last three versions of swift so there is no real point for a project reliant of NIO trying to support more version of swift than that. So when 5.7 is released support for 5.4 won't be required. Of course you can still support 5.4 if you want.

I agree with you Adam - requiring code owner approval seems sufficient to me. I'll let @paulofaria make the final call on this one though since he's been the primary maintainer.

Yeah! Let's do it!

Awesome, I've removed the required status checks from GraphQL and aligned the projects throughout GraphQLSwift to have the same main branch protection settings. Thanks guys!

Thank you, Jay!


Other export formats

Addressing a Problem?
For spirograph, we might need save_to_shapefile or save_to_geojson. We might also want save_to_csv for some projects.
Potential Solution
No response
Additional context
No response
Contribution

[ ] I would be willing/able to open a Pull Request to contribute this feature.

save_to_excel would be useful too and might be better than save_to_csv.
@sarahclaude

@vindelico


Update integration tests to use vm_service_lib

This switches the integration tests to the vm_service_lib which is a lighter wrapper over the the VM service.
I originally used vm_service_client because it was in the dependencies list, but it seems to be a transitive dependency from test (which we flatten into all pubspecs). We've been blocked a few times (and still are for the debugger tests) because the extra functionality added by vm_service_client sometimes requires updates with changes to Dart and right now we're pinned to a version of test that makes it more complicated to get the updates through.
Most of the changes are a very simple mapping, though waitForPause got slightly more complicated since we have to handle waiting for the pause event and checking the isolates existing state ourselves.

I guess adding dev_dependencies requires running flutter update-packages --force-upgrade too!
I think I'll need to wait until #23755 lands then, since running update-packages tries to update test and adds test_api which I think I probably don't want to do. I'll rebase this and run it after #23755 lands.

@devoncarew this has been rebased and the bots are all green :-)


feat: improve backoff settings for cold starts

After some testing, this is the sweet spot to archive better cold starts. Tested in FRA, fastest numbers after five trials:
Before: ~1.4s
After: ~1.08s

Checklist

[ ] run make test
[ ] PR title must follow conventional-commit-standard
[ ] tests and/or benchmarks are included
[ ] documentation is changed or added
[ ] commit message and code follows the Code of conduct

@StarpTech please test with the latest commit. If you don't like it or if it's slowing things down, you can revert the commit.


Add Sora network SS58 Address

This PR adds an account prefix for Sora network.
Signed-off-by: Vladislav Markushin<EMAIL_ADDRESS>

@bkchr seems like @gavofyork is a bit busy, can we bring someone to review this faster?

@vmarkushin can you merge master

@apopiak thanks for the approve.
When this PR might be merged?

bot merge


Support installing plugin from custom source

The vagrant_plugin provider supports installing from a custom source. This PR adds that possibility to the install_plugins recipe

I'll review this and other PRs/issues in this repository next week. I've been out on vacation and then the Chef summit the last couple weeks. :ice_cream:

I'm working on this. I'm writing a failing spec first.

@miguelaferreira I'd like to understand your use case a bit better. Are you trying to specify a vagrant plugin on disk, or at a custom https:// location?
There seem to be issues with the way Vagrant handles --plugin-source locations. This is from the Vagrant docs:
--plugin-source SOURCE - Adds a source from which to fetch a plugin. Note that this doesn't only affect the single plugin being installed, by all future plugins as well. This is a limitation of the underlying plugin installer Vagrant uses.

See this Vagrant issue.
Also, see this StackOverflow question.

I was planning to point the source to an http url. But from disk would work too.
Reading the snippet from the vagrant docs, I'm guessing that spectrograph a source is a bad idea. However, I've installed custom builds of variant plugins from disk by specifying a file name. An example would be:
vagrant plugin install vagrant-cloudstack-1.0.0.gem

This PR is superceded by PR #48.


[Bugfix] Bump transformers to 4.43.2

@mgoin Thanks you for the PR! Could uncomment the test here as well?
https://github.com/vllm-project/vllm/blob/f4f8a9d892a357e341b90bc47a8d72ece62323d5/tests/test_config.py#L98


Peek option

Taskbar X is an great taskbar customization tool . I feel it would be amazing if the developer can add the peek option when we hover over the app in taskbar . That would be very helpful

Doesn't Windows already support this via AeroPeek?


No MDX Compatibility

Bug report

What is the current behavior?
warn The GraphQL query in the non-page component "/Users/matthew/Desktop/MDX Please
PLease/src/templates/about-page.js" will not be run.
warn The GraphQL query in the non-page component "/Users/matthew/Desktop/MDX Please
PLease/src/templates/blog-post.js" will not be run.
warn The GraphQL query in the non-page component "/Users/matthew/Desktop/MDX Please
PLease/src/templates/index-page.js" will not be run.
warn The GraphQL query in the non-page component "/Users/matthew/Desktop/MDX Please
PLease/src/templates/product-page.js" will not be run.

Simply install gatsby-plugin-mdx and change all instances of MarkdownRemark to Mdx.
If the current behavior is a bug, please provide the steps to reproduce.

What is the expected behavior?
Treating the pages as pages and rendering them out just as before MDX is added.

Other relevant information:
I spent over 9 hours trying to figure out why it suddenly treats that as non-page components. No helpful was provided regardless of flag used.

System:
OS: macOS 12.1
CPU: (8) x64 Intel(R) Core(TM) i7-4870HQ CPU @ 2.50GHz
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 16.13.2 - /usr/local/bin/node
Yarn: 1.21.1 - /usr/local/bin/yarn
npm: 8.1.2 - /usr/local/bin/npm
Languages:
Python: 2.7.18 - /usr/bin/python
Browsers:
Firefox: 96.0.3
Safari: 15.2
npmPackages:
gatsby: ^4.0.0 => 4.8.1
gatsby-plugin-image: ^2.0.0 => 2.8.1
gatsby-plugin-mdx: ^3.8.1 => 3.8.1
gatsby-plugin-netlify: ^3.14.0 => 3.14.0
gatsby-plugin-netlify-cms: ^6.0.0 => 6.8.0
gatsby-plugin-purgecss: ^6.0.0 => 6.1.0
gatsby-plugin-react-helmet: ^5.0.0 => 5.8.0
gatsby-plugin-sass: ^5.0.0 => 5.8.0
gatsby-plugin-sharp: ^4.0.0 => 4.8.1
gatsby-remark-copy-linked-files: ^5.0.0 => 5.8.0
gatsby-remark-images: ^6.0.0 => 6.8.1
gatsby-remark-relative-images: ^0.3.0 => 0.3.0
gatsby-source-filesystem: ^4.0.0 => 4.8.1
gatsby-transformer-remark: ^5.0.0 => 5.8.1
gatsby-transformer-sharp: ^4.0.0 => 4.8.0
npmGlobalPackages:
gatsby-cli: 2.12.91

Howdy @matthewhoth! Thank you for this report, do you happen to have a reproducing repo I could take a gander at?


Fix avro data test schema according to spec

According to the spec, struct fields must have unique IDs within the table schema:

A struct is a tuple of typed values. Each field in the tuple is named and has an integer id that is unique in the table schema.

This PR fixes the AvroDataTest defined nested structs to match the spec.

@rdblue I found this caused issues while testing https://github.com/apache/incubator-iceberg/pull/227

+1
Thanks @edgarRd!


[ArangoDB 3.2][rocksdb] data racing when using more processes accessing same database

my environment running ArangoDB
I'm using the latest ArangoDB of the respective release series:

[ ] 2.8
[ ] 3.0
[ ] 3.1
[x] 3.2
[ ] self-compiled devel branch

Mode:

[ ] Cluster
[x] Single-Server

Storage-Engine:

[ ] mmfiles
[x] rocksdb

On this operating system:

[ ] DCOS on

[ ] AWS
[ ] Azure
[ ] own infrastructure

[ ] Linux

[ ] Debian .deb
[ ] Ubuntu .deb
[ ] SUSE   .rpm
[ ] RedHat .rpm
[ ] Fedora .rpm
[ ] Gentoo
[x] docker - official docker library
[ ] other:

[ ] Windows, version:
[ ] MacOS, version:

Versions:

[x]<EMAIL_ADDRESS>[x] node v6.11.1

After the release of 3.2.0 I wanted to try out the new rocksdb feature because it would help my case with huge datasets and memory issues. For first try running 3.2.0 with our application I got a weird error ArangoError: precondition failed, trying the default storage engine it was fine.
Today I decided to give it another try and track down the issue, but this time I got additional error ArangoError: conflict (while executing)
After a little testing I found out it's because of data racing on different processes trying to update database.
The issue can be reproduced by:
'use strict';

const { fork } = require('child_process');

if (process.argv[2]) {
    const arangojs = require('arangojs');

    const connection = arangojs({
        url: 'http://root@localhost:8529',
        databaseName: 'local'
    });

    const query = `
        UPSERT {url: @url}
        INSERT {url: @url, host: @host, baseDomain: @baseDomain, status: @status, socialKind: @socialKind}
        UPDATE {host: @host, baseDomain: @baseDomain, socialKind: @socialKind} IN Link
        RETURN NEW._id
    `;

    const urls = 'abcdefghijklmnopqrstuvwxyz0123456789'.split('');

    console.log('Child forked!');
    const task = () => {
        const id = Math.floor(Math.random() * urls.length);
        const bindVars = {
            url: urls[id],
            host: "subdomain.exmaple.com",
            baseDomain: "exmaple.com",
            status: null,
            socialKind: true
        }
        connection
            .query(query, bindVars)
            .catch((e) => {
                console.log('ERROR:', e.message);
            })
    };

    let counter = 0;
    const interval = setInterval(() => {
        if (++counter >= 1e5) {
            clearInterval(interval);
            console.log('DONE')
            return;
        }

        if (counter % 100 === 0) {
            console.log('Counter at', counter);
        }

        task()
    }, 50);
} else {
    fork(process.argv[1], ['forked']);
    fork(process.argv[1], ['forked']);
}

If I run this using the default storage engine I get no errors, I can even set setInterval to 5 ms, using rocksdb I get results like this
Child forked!
Child forked!
ERROR conflict (while executing)
ERROR conflict (while executing)
ERROR conflict (while executing)
Counter at 100
Counter at 100
ERROR conflict (while executing)
ERROR conflict (while executing)
ERROR conflict (while executing)
Counter at 200
Counter at 200
ERROR conflict (while executing)
Counter at 300
Counter at 300
ERROR conflict (while executing)
^C

Is there any chance to solve this without touching application code?
Regarding ArangoError: precondition failed, even turning off the other process, this issue stays, please note for that query I'm using collection.update and when I'm changing it to native AQL I get ArangoError: conflict (while executing)

I meet the same issue ('code': 409, 'errorNum': 1200, 'errorMessage': 'conflict (while executing)') while performing UPSERT via pyArango.database.Database.AQLQuery with multiprocessing.

Same error here (ArangoError: precondition failed) occuring randomly with arangodb 3.3.2, RocksDB, arangojs 5.8.0 and no AQL being directly involved (only myCollection.update(key, ...)).
I guess I have to return to mmfiles for now...

Getting the same during an update via query on rocksdb, 3.2.10, using the nodejs 5.7.1 driver

What does "ArangoError: conflict (while executing)" mean exactly in this example?
const query = `
        UPSERT {url: @url}
        INSERT {url: @url, host: @host, baseDomain: @baseDomain, status: @status, socialKind: @socialKind}
        UPDATE {host: @host, baseDomain: @baseDomain, socialKind: @socialKind} IN Link
        RETURN NEW._id

Does it mean that UPSERT is not atomic operation?
Does it mean that UPSERT checked whether need to do INSERT or UPDATE and was about to do it but someone else changed the record in between?
Is it only UPSERT causing this particular error? What other scenarios can cause it?
Please provide as much information as possible. I am considering to add OPTION { ignoreErrors: true } (do I have other options?) but need to understand exactly what it will lead to.

It's been half a year now, any updates on this bug?

Hi,
I have the same problem on last version (3.3.9) while doing concurrent update on the same document.
Any workaround or fix ?

And on 3.3.10

The RocksDB storage engine in ArangoDB intentionally does not use any collection locks, in order to allow for higher parallel throughput.
That means two concurrent requests/transactions may update the same document at the very same time, which is a write-write conflict that the storage engine will not allow. Otherwise any transaction could suffer from anomalies, which is probably undesired too.
The proper way to handle such conflicts is to retry them from the application side, because only the application will know if an operation is retryable or if retrying may make things worse.
However, in the devel branch we have augmented most of the AQL data modification statements with an exclusive option that will make them lock out any other write operations on the collection while running. This is opt-in however, because in many cases that is the opposite of what is actually desired. But in devel it's up to the user to decide.

@jsteemann Do I understand correctly that write-write conflict happens when a transaction tries to acquire write lock on a document already locked by another transaction/request?

Yes. Because if they would be let through, then one transaction would just overwrite data of another, without the client application getting a chance to detect this.

@jsteemann I have a specific use case, appreciate if you could advise the best approach.
Let say I have an array of sensors, they send some values which I store in a database. For each sensor I am only interested in the latest value so when I receive new value from a sensor I run UPSERT command
UPSERT { _key = sensorId } INSERT { _key = sensorId, value = value_from_sensor } UPDATE { _key = sensorId, value = value_from_sensor }
Sometimes values from the same sensor come quickly then it can cause write-write conflict. If I handle it in application and try again after some delay it can cause overwriting of newer value.
The proper solution probably would be a queue etc but for my task it seems excessive.
I am wondering whether there is a setting for ArangoDb to just ignore write-write conflict and overwrite the value anyway?

@irriss : there are two solutions for this, but they are both available in our current devel version and will be released with ArangoDB 3.4:

use "overwrite" option in AQL: INSERT { _key: "someKey", ... } INTO collection OPTIONS { overwrite: true }: this will turn the insert operation into a "repsert", which will try to insert the value if it does not yet exist, but replace and overwrite it if it exists
use "exclusive" option in AQL: UPSERT { ... } INSERT ... UPDATE ... INTO collection OPTIONS { exclusive: true }: this will use an exclusive lock on the collection and block other operations while the upsert is going, thus preventing any write-write conflicts from happening.

For ArangoDB versions before 3.4 the solution is to use insert in a try ... catch block in the application, and react as follows:

if it works, all good and done
if it fails with "unique constraint violation", use a replace or update on the _key
if it fails with any other error, let it bubble up
This is a bit more inconvenient, that's also why we have worked on the above alternatives in 3.4.

@jsteemann  if i use mmfile engine the peoblem will be solved or not ?

The MMFiles engine uses collection level locks (writes block reads):
https://docs.arangodb.com/3.4/Manual/Architecture/StorageEngines.html
Therefore, the behavior with MMFiles engine should be like RocksDB with the exclusive option enabled.

@jsteemann This is still a problem for me, even with await collection.save(message, {overwrite: true, silent: true}); (ArangoJS) in ArangoDB 3.4.1. Can I help in any way to debug this or is this a known bug? Or is it not considered a bug?

I'm still getting data racing (on 3.6 with rocksdb) with a simple update request, collection.update("key", {data}, {keepNull: false}). Although it's error code 412 not 409.

OPTIONS { exclusive: true } for INSERT and UPSERT works for me for arangodb 3.8.7 (in case someone comes across this issue in 2022)


websocket proxy

There is problem in used gorilla/websocket package for proxying websocket traffic.
I start bug report Fragment Size is not buffer size.
And I thing you should be aware of.

Hi! I'm Træfiker :robot: the bot in charge of communication regulation.
Thanks for your interest in Træfik!
Issue templates help us help you by providing all necessary information.
Please edit your issue and use the available templates:

Feature request
Bug report

And remember: each time someone ignores the template, a cute little bunny dies.

#SaveTheCuteBunny :heart: :rabbit: :heart:

Hi @SergeVL . Thanks for reporting this issue.
I am closing this issue for 2 reasons:

As specified by the traefiker's Bot, we would need you to use the templates to fill issues. It would help the project to track, fix, collect and analyse issues over time.
This bug is caused by an upstream dependency. As soon as your fix in gorilla/websocket would have been fixed, we'll update Træfik's to benefit from the dependency's fix.

You use  gorilla/websocket constructor without parameters and by default buffers has size just 4K.
At least you can add configuration parameters for this.

Hello @SergeVL , as explained on my previous message and by the bot's message, we need your help as you are a potential contributor as well as any other current maintainers.
Could you please help the project by opening an issue using the default's message template? It would help us to prioritize and follow user requests, as it looks like you are giving us a valuable tip.
Thanks in advance


Bizarre behavior with Statistics.mean.

I have two identical arrays generated in different ways which produce different means.  What is going on here?
julia> using Measurements, Statistics

julia> a = fill(1.0 ± 0.5, 2)
2-element Array{Measurement{Float64},1}:
 1.0 ± 0.5
 1.0 ± 0.5

julia> b = [1.0 ± 0.5, 1.0 ± 0.5]
2-element Array{Measurement{Float64},1}:
 1.0 ± 0.5
 1.0 ± 0.5

julia> a == b
true

julia> mean(a)
1.0 ± 0.5

julia> mean(b)
1.0 ± 0.35

julia> mean(a) == mean(b)
false

(@v1.5) pkg> st Measurements
Status `~/.julia/environments/v1.5/Project.toml`
  [eff96d63] Measurements v2.2.1

You're missing correlation between variables: https://juliaphysics.github.io/Measurements.jl/stable/usage/#Correlation-Between-Variables-1.  a has the same measurement twice, b has two distinct measurements

To elaborate a bit:
julia> using Measurements

julia> a = fill(1.0 ± 0.5, 2)
2-element Array{Measurement{Float64},1}:
 1.0 ± 0.5
 1.0 ± 0.5

julia> a[1] === a[2]
true

julia> sum(a)
2.0 ± 1.0

julia> b = [1.0 ± 0.5, 1.0 ± 0.5]
2-element Array{Measurement{Float64},1}:
 1.0 ± 0.5
 1.0 ± 0.5

julia> b[1] === b[2]
false

julia> sum(b)
2.0 ± 0.71

a[1] === a[2] shows that the two quantities are exactly the same measurements and their sum must take this into account, while the fact that b[1] !== b[2] means that the two quantities are distinct measurements, and the uncertainty of their sum is simply the quadrature sum of their uncertainties.
You can understand that the mean of a is the same as each element of the vector because they're just all the same measurement, so you don't get more insight by taking the mean of the same measurement repeated multiple times.

Thank you very much, this explains the tag property, of which I found the discussion of in the Appendix.


⚠ Samsung has degraded performance

In 2cd2ee1, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2899 ms

Resolved: Samsung performance has improved in b571a74.


Make array buffer work in libuser

Also remove lifetime dependency

Thinking about this a bit more, we have no good reason to keep the buffer.rs file at all with the new object system. The pop functions should just return a reference (with a lifetime chosen by the caller).


Plugin does not support instance_refresh in aws_autoscaling_group

Prerequisites

[x] Ensure you have latest version of plugin installed
[x] Search for possible issue duplicates

Installation details

[x] IDE version (Help->About->Copy to Clipboard)
[x] intellij-hcl plugin version (Settings->Plugins)
[x] Terraform version (terraform -v)

PhpStorm 2020.3.2 RC
Build #PS-203.7148.74, built on January 27, 2021
Licensed to Matthew Salazar
You have a perpetual fallback license for this version.
Subscription is active until December 15, 2021.
Runtime version: <IP_ADDRESS>+11-b1145.77 aarch64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
macOS 11.2.1
GC: ParNew, ConcurrentMarkSweep
Memory: 1981M
Cores: 8
Registry: run.processes.with.pty=TRUE
Non-Bundled Plugins: com.arcticicestudio.nord.jetbrains, com.mallowigi, org.intellij.plugins.hcl, com.jetbrains.codeWithMe, name.kropp.intellij.makefile, de.espend.idea.laravel, ru.adelf.idea.dotenv

Hashicorp Terraform / HCL language support 0.7.10

Terraform v0.14.6

Exception
Unknown block type instance_refresh

This property was added in 0.3.22 of the AWS provider, back in December.
Release info here: https://github.com/hashicorp/terraform-provider-aws/blob/v3.22.0/CHANGELOG.md.
Documentation of instance_refresh here: https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/autoscaling_group#instance_refresh
Steps to Reproduce
Please list the steps required to reproduce the issue, for example:

Create a block for aws_autoscaling_group.
Add a block inside that for instance_refresh.
See the warning.
Run terraform apply and see it works as intended.

Fixed in 0.7.11


Error when npm rebuild with node v7

Upgrade to node v7 and execute npm rebuild in my project, then got error message said
Error<EMAIL_ADDRESS>install: `node-pre-gyp install --fallback-to-build`

Two errors reported
../src/heap_snapshot.cc:46:46: error: no member named 'GetHiddenValue' in 'v8::Object'
      info.GetReturnValue().Set(info.This()->GetHiddenValue(__root));
                                ~~~~~~~~~~~  ^
../src/heap_snapshot.cc:50:20: error: no member named 'SetHiddenValue' in 'v8::Object'
      info.This()->SetHiddenValue(__root, _root);
      ~~~~~~~~~~~  ^
2 errors generated.

same here

https://github.com/node-inspector/v8-profiler/pull/96 solves the issue

Hi folks,
Any updates ?
We have a good tool that generates flamegraph and do some profiling things, and that tool is using v8-profiler, and we can't test against Node.js 7x yet :/
thanks.

Is this published to NPM, I've got the same problem on node 7.3.0

Same with 7.4.0 too.

Just checking in to see if this package is going to be updated for node v7+ or taken over by somebody else?

I'm also interested why has it stopped and what the future holds @3y3 @bajtos ?

I'm using this for now:
https://github.com/node-inspector/v8-profiler/pull/96#issuecomment-271152662

Please try<EMAIL_ADDRESS>, should work now!


React Native: Requiring unknown module "react". If you are sure the module is there, try restarting the packager.

Hi. I'm trying to use Look with React Native and has issue described in title.
Below is some simplified code i've used
import React, { View } from 'react-native';
import Look, { StyleSheet } from 'react-look';

class MyComponent extends React.Component {
    render() {
        return (
            <View look={styles.container}>
            </View>
        )
    }
}

const styles = StyleSheet.create(MyComponent, {
    container: {
        flex: 1
    }
});

export default Look(MyComponent);

"react-look": "^0.7.1"
"react-native": "^0.17.0"

Oh, got that issue. I thought react-native would install react by default as it is build on it? Could you please just "try" to npm install react would like to see what happens actually.
If not I might have to use different packages again as I had Look working with react-native before.

I think this issue is corresponding with https://github.com/facebook/react-native/issues/2985
I'll try to wait RN0.18 for few days.
Thanks.

Thanks for refering. After all I will soon refactor the code base and and packaging to allow better usage with RN anyways. Hope you can fix the issue right now :)

@andycaramba Are you fine if I close this issue? (at least for now, as it seems its not an issue with Look itself rightß)

Yes, i'm fine. I have some time and I'll wait RN team for 0.18 release. Thank you.

Great! Come back creating an issue if there's anything not working as expected with 0.18 soon. You're welcome :)

same problem but with the toast

error eith the restart the packager or runing npm install


mediathekview: 13.5.1 -> 13.7.0

Motivation for this change
Version bump. When testing please make a backup of yout configuration as citing from the release page:
Erstellt vor dem Update zwingend ein Backup eurer Konfiguration! Ein Mischbetrieb von 13.7 und älteren Versionen ist ohne Verlust von Downloadhistorie und anderen Parametern NICHT möglich!!!
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

This is a semi-automatic executed nixpkgs-review which is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
If you have any questions or problems please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 110833 run on x86_64-darwin 1

1 package built:

mediathekview

This is a semi-automatic executed nixpkgs-review which is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
If you have any questions or problems please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 110833 run on x86_64-darwin 1

1 package built:

mediathekview

Version bump. When testing please make a backup of yout configuration as citing from the release page:

Does this require a changelog entry?

Version bump. When testing please make a backup of yout configuration as citing from the release page:

Does this require a changelog entry?

Version bump. When testing please make a backup of yout configuration as citing from the release page:

Does this require a changelog entry?

No, why would people ever downgrade their version?

Version bump. When testing please make a backup of yout configuration as citing from the release page:

Does this require a changelog entry?

No, why would people ever downgrade their version?

Version bump. When testing please make a backup of yout configuration as citing from the release page:

Does this require a changelog entry?

I guess in principal it would be nice to document that, but other packages like afaik syncthing and joplin had non-backwards compatible updates without changelog entries.

Version bump. When testing please make a backup of yout configuration as citing from the release page:

Does this require a changelog entry?

I guess in principal it would be nice to document that, but other packages like afaik syncthing and joplin had non-backwards compatible updates without changelog entries.


chore: improve task execution order

Some have noticed that the order of execution changed after the microtask PR got introduced, while there is no guarantee of order in case of parallel combinators it would still be good to preserve it if possible.
This PR introduce an internal task scheduler that uses mictotasks but avoids oversuspension, it basically suspends once and executes everything that can be scheduled in a loop until nothing else is to be done, this mechanisms preserves the order of scheduling because scheduling is sync within a single suspension

cc @StefanoMagrassi @gcanti


[next] fix keyframe name collisisions

This fixes @keyframes rules from multiple CSS chunks being minified to the same name (generally "a" or "b"). Currently, optimize-css-assets-webpack-plugin does not have a way to minify global identifiers across assets without colliding.

We're using this on the new Preact website. Can confirm it works.


cri-o: allow a prefix for all bind mounts

Introduce a new config --bind-mount-prefix=PREFIX that adds a prefix
to the source for every bind mount.  This allows CRI-O to run inside
of a container, and be able to see the host rootfs.
Signed-off-by: Giuseppe Scrivano<EMAIL_ADDRESS>- What I did
Added a new option --bind-mount-prefix=PREFIX to specify a prefix for every bind mount.
- How I did it
If a bind mount PREFIX is specified, the source for each bind mount is prefixed with it
- How to verify it
# mkdir -p /host/foo
# touch /host/foo/bar
# crio --bind-mount-prefix=/host/host
A mount from /foo/bar -> /bar is converted to /host/foo/bar -> /bar
- Description for the changelog
New option --bind-mount-prefix=PREFIX to permit CRI-O in a container to get full access to the host rootfs
Marked as WIP as I am still testing it

/test all

I moved the symlink check before the missing src directory is created so that we can reuse the error code from the Lstat in resolveSymbolicLink

/test all

/test all

/test all

@wking @mrunalp @runcom @umohnani8 PTAL

/test all

merging.


Inline clock

for one of my app i am looking for inline clock, if this can be used inline this is the perfect clock i will ever use for mobile:).
Thanks in advance

@nbandla I've added inline support in my fork here: https://github.com/mdehoog/clockpicker


remove scs node-template dependency

Closes #165.
This was such a low-hanging fruit that I just needed to tackle it.
@haerdib can you update jenkins to use the node-template from substrate instead?

@haerdib I think we can merge this one as is. I prefer not to invest work into jenkins anymore, and the tests pass there currently. We should rather tackle #176 soon.


[WIP] Partition column name should be case insensitive

Why is this PR needed?
when inserting into the static partition, the partition column name is case sensitive now.
What changes were proposed in this PR?
the partition column name should be case insensitive.
convert all partition column names to low case.
Does this PR introduce any user interface change?

No

Is any new testcase added?

Yes

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/1251/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/2969/

LGTM


dynamic import() on caption.js and meme.js

Couldn't load command caption.js: Error [ERR_REQUIRE_ESM]: require() of ES Module C:\Users#####\node_modules\file-type\index.js from C:\Users#####\Desktop\MemerBot-master\commands\caption.js not supported.
Instead change the require of index.js in C:\Users#####\Desktop\MemerBot-master\commands\caption.js to a dynamic import() which is available in all CommonJS modules.
index.js:29
Couldn't load command meme.js: Error [ERR_REQUIRE_ESM]: require() of ES Module C:\Users#####\node_modules\file-type\index.js from C:\Users#####\Desktop\MemerBot-master\commands\meme.js not supported.
Instead change the require of index.js in C:\Users#####\Desktop\MemerBot-master\commands\meme.js to a dynamic import() which is available in all CommonJS modules.

i know like nothing about javascript but ive gotten through most problems except this

What's the output of node -v?
Try running the Bot under an older version of Node.js.
If i remember correctly i used Node.js v16 LTS to develop this bot.


ts-bridge build does not compile properly with React Native in a monorepo

Description
The ts-bridge build is currently experiencing issues with React Native in a monorepo setup (not yet tested in a standalone repository). The screenshots below illustrate the build behavior when using tsc

Compared to when using ts-bridge

Steps to reproduce

Clone https://github.com/MetaMask/metamask-design-system
Change the build script for the package design-system-react-native and/or design-system-twrnc-preset to use ts-bridge
Run yarn workspace @metamask/design-system-react-native build or yarn workspace @metamask/design-system-twrnc-preset build from root or yarn build in the respective package
Observe error

This is an annoying one. react-native doesn't specify a main or exports field, but it has a index.js, so Node.js (thus ts-bridge) falls back to that, but the index.js is actually Flow, not plain JavaScript. ts-bridge tries to rewrite imports if they are not detected by cjs-module-lexer, which does not work for Flow. We may just need to assume the best case scenario when a package cannot be parsed, and leave imports as-is.


.net core hangs

fix #401

Hi, thanks for this. Can you explain some of the changes you've done? Especially regarding the ConnectAsync and stuff?


allow for a display label on minions

currently minions are displayed by id, this value is currently required to be routable even though minions have a separate hostIP attribute which should nominally perform that role. either allowing id to be a display label and using hostIP for access, or separately having a displayName/label on minions would allow users to tag minion instances by a consistent / human interpretable naming scheme.

@ddysher Is this done?

Done.
#2547 and a few others.


[4.2] Make FloatingPoint require that Self.Magnitude == Self

We didn't have the where clause to express this constraint at the time that the FloatingPoint protocol was implemented, but we do now. This is not a semantic change to FloatingPoint, which has always bound IEEE-754 arithmetic types, for which this constraint would necessarily hold, but it does effect the type system.
For example, currently the following function does not type check:
func foo<T>(x: T) -> T where T: FloatingPoint {
  var r = x.remainder(dividingBy: 1)
  return r.magnitude
}

with this change, it compiles correctly.
Having done this, we no longer need to have a separate abs defined on FloatingPoint; we can use the existing function defined on SignedNumeric instead. Additionally mark the global fabs defined in the platform C module deprecated in favor of the Swift abs; we don't need to carry two names for this function going forward.

@swift-ci Please test


How to set maximum duration for a video?

Is there any way to set maximum and minimum duration of video?

I'm unsure if that is part of this library. But you can definitely use a timer once the user starts recording that determines whether the user can stop the recording, whether the video should stop recording on it's own, etc.
https://www.hackingwithswift.com/articles/117/the-ultimate-guide-to-timer

@kselvin Thank u so much, I used timer to acheive the same and it's working.


Allow mitigation of CVE-2023-25577

Description
Mitigation of CVE-2023-25577 requires upgrading Werkzeug to 2.2.3. This PR loosens the dependency requirement to allow any Werkzeug 2.x as there doesn't appear to be a reason to be stricter.
This resolves #1695.
Checklist

[x] Created tests which fail without the change (if possible)

n/a

[x] All tests passing
[x] Added a changelog entry
[x] Extended the README / documentation, if necessary

n/a

Codecov Report

Merging #1696 (0b95609) into master (10c389b) will not change coverage.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@           Coverage Diff           @@
##           master    #1696   +/-   ##
=======================================
  Coverage   98.94%   98.94%
=======================================
  Files          97       97
  Lines        7768     7768
  Branches     1610     1610
=======================================
  Hits         7686     7686
  Misses         49       49
  Partials       33       33

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

Looks good to me! Thank you :)
I can add all the RST links separately, so you don't have to worry about them :) Is there anything you'd like to work on in this PR (as it is in the draft state)?

Thanks! Please go ahead and do what you need to do 🙂

Thanks, @Stranger6667! Are you expecting to make a release soon?

You're very welcome :) Yes, I'll make a new release today

Released in 3.18.4 :)


Unsafe When Not Unsafe

So, I have a sign portal pointing to a place which is safe, and my users get destination unsafe - I do not. The location, I double checked is not unsafe. My wish is for there to be an option in config to completely disable the unsafe location feature.

Hmm, may be a bug with the messages (I think the people may just not have perms) but it's telling them it is unsafe. Will investigate tonight.

I need this fixed, fast.

Well, Multiverse is open source. Fix the bug, and submit a pull request. That's the fastest way it'll get fixed.

I'm no java guy but my server just lost it's userbase so yeah :'(

Closing, this should be fixed in 2.2 already.


Missing autoupdate on group delete

When deleting a group, all users in the deleted group doesn't update. A reload is necessary that all 'undefined' strings in the client disappear.

It seems to be also a cache problem. Using redis a reload does not work. Deleting cache helps.

In the client I can see a string "unknown" but the server looks like sending a correct autoupdate, right?

Yes, all users get a deleted for the one group. But see this situation:
A user is just in one group and this group has no permissions. Then this group is deleted, so the user should get all perms of the default group. The user gets the autoupdate with the deleted group - but does not get an autoupdate with "changed: users/user" for himself. So his groups_id is not updated in the client, resulting in wrong permission calculation. I tried adding this in the destroy view in the GroupViewSet:
affected_users = User.objects.filter(groups__pk=instance.pk)
inform_changed_data(affected_users)

But the user affected by the deletion does not get updated.
This is also important for the user list view: The group selection does not work, because the client stucks at the old group and changing results in "the pk '...' does not exist"; so the manager need to get updates for all affected users, too.

Similar problem when a user gets a new permission (e.g. "motions.can_see_comments"). The user see the new comment fields but without content. Also reload does not helps because the restricted user cache contains was not updated (with new comment field values). Deleting the specific cache key helps. After reload the config values are visible in OpenSlides. - The REST api already shows the correct values.
Any hints how to fix this?


"node is undefined" when using dx serve

Problem
When running a Dioxus Web app in debug mode (dx serve --hot-reload) we get the following error that blocks pages from rendering. It seems to be related to our usage of resources because removing the use_resource call and stubbing the data "fixes" the issue. I'm having trouble debugging this however as the error seems to happen in Dioxus' JS code which is minified.
The error is not present when compiled in released mode and served from the final web server.
I'm not able to reproduce it with a minimal dx new project, so I guess I'm hitting some kind of edge case.
I know it's very hard to debug a foreign codebase, so I'm just here asking for help and pointers on how to debug and fix it. I've no experience with web renderers or webassembly, so digging into the minified JS has not been very helpful unfortunately :c
Update 1: I got the same error with a page that didn't have a use_resource hook, so the resource clue might be a red herring.
Update 2: the issue doesn't seem to be with the build profile (debug vs release) but with dx serve exclusively. If I run the app with cargo watch -s 'dx build' and then access it via our backend endpoint (which serves the UI by serving the dist folder directly as static files) everything works fine. If I use dx serve (both with and without --hot-reload) then I get the error.

JS Console Error
wasm-bindgen: imported JS function that was not marked as `catch` threw an error:
node is undefined

Stack:
run@http://localhost:8080/assets/dioxus/snippets/dioxus-interpreter-js-7c1300c6684e1811/inline0.js:142:16
__wbg_get_imports/imports.wbg.__wbg_run_2ca7d9c27d6a5eb6/<@http://localhost:8080/assets/dioxus/oxidrive.js:566:25
logError@http://localhost:8080/assets/dioxus/oxidrive.js:259:18
__wbg_get_imports/imports.wbg.__wbg_run_2ca7d9c27d6a5eb6@http://localhost:8080/assets/dioxus/oxidrive.js:565:66
oxidrive-06c73cddedade17f.wasm.dioxus_interpreter_js::unified_bindings::RawInterpreter::run::h2f27ca4ac0da4dae@http://localhost:8080/assets/dioxus/oxidrive_bg.wasm:wasm-function[16667]:0x600d98
oxidrive-06c73cddedade17f.wasm.dioxus_interpreter_js::unified_bindings::Interpreter::flush::he23cf67a41e98678@http://localhost:8080/assets/dioxus/oxidrive_bg.wasm:wasm-function[395]:0x10d9fc
oxidrive-06c73cddedade17f.wasm.dioxus_web::mutations::<impl dioxus_web::dom::WebsysDom>::flush_edits::h4fd3c12ffc74e2a9@http://localhost:8080/assets/dioxus/oxidrive_bg.wasm:wasm-function[19361]…
oxidrive.js:268:17

Uncaught TypeError: node is undefined
    run http://localhost:8080/assets/dioxus/snippets/dioxus-interpreter-js-7c1300c6684e1811/inline0.js:142
    __wbg_run_2ca7d9c27d6a5eb6 http://localhost:8080/assets/dioxus/oxidrive.js:566
    logError http://localhost:8080/assets/dioxus/oxidrive.js:259
    __wbg_run_2ca7d9c27d6a5eb6 http://localhost:8080/assets/dioxus/oxidrive.js:565
inline0.js:142:16
    run http://localhost:8080/assets/dioxus/snippets/dioxus-interpreter-js-7c1300c6684e1811/inline0.js:142
    __wbg_run_2ca7d9c27d6a5eb6 http://localhost:8080/assets/dioxus/oxidrive.js:566
    logError http://localhost:8080/assets/dioxus/oxidrive.js:259
    __wbg_run_2ca7d9c27d6a5eb6 http://localhost:8080/assets/dioxus/oxidrive.js:565
    h2f27ca4ac0da4dae http://localhost:8080/assets/dioxus/oxidrive_bg.wasm:6294936
    he23cf67a41e98678 http://localhost:8080/assets/dioxus/oxidrive_bg.wasm:1104380
    oxidrive-06c73cddedade17f.wasm.dioxus_web::mutations::<impl dioxus_web::dom::WebsysDom>::flush_edits::h4fd3c12ffc74e2a9 http://localhost:8080/assets/dioxus/oxidrive_bg.wasm:6479575
    h16edd80ab2a30af9 http://localhost:8080/assets/dioxus/oxidrive_bg.wasm:431908
    h01209da20c082729 http://localhost:8080/assets/dioxus/oxidrive_bg.wasm:3236497
    h758c38d8e961a82b http://localhost:8080/assets/dioxus/oxidrive_bg.wasm:3427820
    h73b74b9ff63543bd http://localhost:8080/assets/dioxus/oxidrive_bg.wasm:3179121
    h5a97e43d75380cc8 http://localhost:8080/assets/dioxus/oxidrive_bg.wasm:5773541
    oxidrive-06c73cddedade17f.wasm.<dyn core::ops::function::FnMut<(A,)>+Output = R as wasm_bindgen::closure::WasmClosure>::describe::invoke::h8227b253940eb1ee http://localhost:8080/assets/dioxus/oxidrive_bg.wasm:4995315
    __wbg_adapter_63 http://localhost:8080/assets/dioxus/oxidrive.js:337
    real http://localhost:8080/assets/dioxus/oxidrive.js:242
    (Async: VoidFunction)
    __wbg_queueMicrotask_481971b0d87f3dd4 http://localhost:8080/assets/dioxus/oxidrive.js:580
    logError http://localhost:8080/assets/dioxus/oxidrive.js:259
    __wbg_queueMicrotask_481971b0d87f3dd4 http://localhost:8080/assets/dioxus/oxidrive.js:579
    h2756ad73d0cac424 http://localhost:8080/assets/dioxus/oxidrive_bg.wasm:6300164
    h892a0569e6c5a6d1 http://localhost:8080/assets/dioxus/oxidrive_bg.wasm:3960798
    h88f3ba17d6281c7a http://localhost:8080/assets/dioxus/oxidrive_bg.wasm:6457031
    h445ee9005fe306fb http://localhost:8080/assets/dioxus/oxidrive_bg.wasm:6456969
    h64a697db0772aaca http://localhost:8080/assets/dioxus/oxidrive_bg.wasm:4627915
    h97a7c5d4634d908c http://localhost:8080/assets/dioxus/oxidrive_bg.wasm:5313265
    h30459a8e935ec4a4 http://localhost:8080/assets/dioxus/oxidrive_bg.wasm:6352734
    h48f11179c74b1cf0 http://localhost:8080/assets/dioxus/oxidrive_bg.wasm:4973216
    h431ef98fbcd46a77 http://localhost:8080/assets/dioxus/oxidrive_bg.wasm:6414052
    h6ceaceb742779739 http://localhost:8080/assets/dioxus/oxidrive_bg.wasm:6280414
    h26a57e69c749346f http://localhost:8080/assets/dioxus/oxidrive_bg.wasm:4273419
    hab67b51f4e8566c6 http://localhost:8080/assets/dioxus/oxidrive_bg.wasm:6036980
    hc56bbf2149a94479 http://localhost:8080/assets/dioxus/oxidrive_bg.wasm:4114346
    ha4b411e76aa9b44f http://localhost:8080/assets/dioxus/oxidrive_bg.wasm:6357822
    oxidrive-06c73cddedade17f.wasm.<dioxus_core::tasks::LocalTaskHandle as futures_task::arc_wake::ArcWake>::wake_by_ref::hd11f2247016cc8e1 http://localhost:8080/assets/dioxus/oxidrive_bg.wasm:5683236
    h4f19ea5be08c58ec http://localhost:8080/assets/dioxus/oxidrive_bg.wasm:6082710
    hd7aeae41df181142 http://localhost:8080/assets/dioxus/oxidrive_bg.wasm:6345244
    hf5db5641673706ce http://localhost:8080/assets/dioxus/oxidrive_bg.wasm:6258619
    h89969427fa6b567d http://localhost:8080/assets/dioxus/oxidrive_bg.wasm:2590921
    oxidrive-06c73cddedade17f.wasm.<futures_channel::oneshot::Sender<T> as core::ops::drop::Drop>::drop::h1f80afe3d1b11612 http://localhost:8080/assets/dioxus/oxidrive_bg.wasm:6461241
    heb3b14efb1622fb3 http://localhost:8080/assets/dioxus/oxidrive_bg.wasm:6472528
    h288cfca33087130e http://localhost:8080/assets/dioxus/oxidrive_bg.wasm:5870457
    hbd0b243bb2956694 http://localhost:8080/assets/dioxus/oxidrive_bg.wasm:6287188
    oxidrive-06c73cddedade17f.wasm.<T as wasm_bindgen::closure::WasmClosureFnOnce<(),R>>::into_fn_mut::{{closure}}::h47c6d9f4e97df5eb http://localhost:8080/assets/dioxus/oxidrive_bg.wasm:6088910
    oxidrive-06c73cddedade17f.wasm.<dyn core::ops::function::FnMut<()>+Output = R as wasm_bindgen::closure::WasmClosure>::describe::invoke::ha5f6ee08ab7008e0 http://localhost:8080/assets/dioxus/oxidrive_bg.wasm:5308035
    __wbg_adapter_48 http://localhost:8080/assets/dioxus/oxidrive.js:275
    real http://localhost:8080/assets/dioxus/oxidrive.js:242
    (Async: setTimeout handler)
    __wbg_setTimeout_7d81d052875b0f4f http://localhost:8080/assets/dioxus/oxidrive.js:441
    handleError http://localhost:8080/assets/dioxus/oxidrive.js:342
    __wbg_setTimeout_7d81d052875b0f4f http://localhost:8080/assets/dioxus/oxidrive.js:440
    he0d9fea3b01d6e1b http://localhost:8080/assets/dioxus/oxidrive_bg.wasm:4318361
    h99609eeb050e5fe3 http://localhost:8080/assets/dioxus/oxidrive_bg.wasm:3873974
    hba140d558ab5d413 http://localhost:8080/assets/dioxus/oxidrive_bg.wasm:4910831
    ha28ec4674b5eb4a6 http://localhost:8080/assets/dioxus/oxidrive_bg.wasm:1907573
    oxidrive-06c73cddedade17f.wasm.<core::pin::Pin<P> as core::future::future::Future>::poll::h289cf37395beec6c http://localhost:8080/assets/dioxus/oxidrive_bg.wasm:6048964
    h0f49d4d6fc9d9c98 http://localhost:8080/assets/dioxus/oxidrive_bg.wasm:6180655
    h58877f03fb174ca6 http://localhost:8080/assets/dioxus/oxidrive_bg.wasm:6312388
    h9ef21a7298190039 http://localhost:8080/assets/dioxus/oxidrive_bg.wasm:5804578
    hc7ebcb8e1a97ab65 http://localhost:8080/assets/dioxus/oxidrive_bg.wasm:5982423
    oxidrive-06c73cddedade17f.wasm.<futures_util::future::poll_fn::PollFn<F> as core::future::future::Future>::poll::h7ca7f1cf7f0f15c4 http://localhost:8080/assets/dioxus/oxidrive_bg.wasm:6015478
    h86424d9a454ec509 http://localhost:8080/assets/dioxus/oxidrive_bg.wasm:1964905
    oxidrive-06c73cddedade17f.wasm.dioxus_core::tasks::<impl dioxus_core::runtime::Runtime>::handle_task_wakeup::h2625d569b7d4750e http://localhost:8080/assets/dioxus/oxidrive_bg.wasm:1501410
    h11a91eca0733c46e http://localhost:8080/assets/dioxus/oxidrive_bg.wasm:999195
    hf018c5a5bd4571cc http://localhost:8080/assets/dioxus/oxidrive_bg.wasm:1282778
    h101333dc4b979024 http://localhost:8080/assets/dioxus/oxidrive_bg.wasm:3260571
    he41aa9d4d6fcdea3 http://localhost:8080/assets/dioxus/oxidrive_bg.wasm:1441104
    oxidrive-06c73cddedade17f.wasm.<futures_util::future::future::fuse::Fuse<Fut> as core::future::future::Future>::poll::h7e3025f8b9a43ef1 http://localhost:8080/assets/dioxus/oxidrive_bg.wasm:4513560
    oxidrive-06c73cddedade17f.wasm.<core::pin::Pin<P> as core::future::future::Future>::poll::he8121bf7a57137ea http://localhost:8080/assets/dioxus/oxidrive_bg.wasm:5905202
    oxidrive-06c73cddedade17f.wasm.<core::pin::Pin<P> as core::future::future::Future>::poll::h0aec9c05b9b0f5e3 http://localhost:8080/assets/dioxus/oxidrive_bg.wasm:5904974
    hc64ae98e4195c0ae http://localhost:8080/assets/dioxus/oxidrive_bg.wasm:6043747
    h55d0908120f064d9 http://localhost:8080/assets/dioxus/oxidrive_bg.wasm:3930952
    oxidrive-06c73cddedade17f.wasm.core::ops::function::impls::<impl core::ops::function::FnMut<A> for &mut F>::call_mut::h37d1f48912645926 http://localhost:8080/assets/dioxus/oxidrive_bg.wasm:6092373
    h33b6ab9931fbc0a6 http://localhost:8080/assets/dioxus/oxidrive_bg.wasm:2252526
    oxidrive-06c73cddedade17f.wasm.<futures_util::future::poll_fn::PollFn<F> as core::future::future::Future>::poll::hd830184b90587d42 http://localhost:8080/assets/dioxus/oxidrive_bg.wasm:6024207
    h16edd80ab2a30af9 http://localhost:8080/assets/dioxus/oxidrive_bg.wasm:426534
    h01209da20c082729 http://localhost:8080/assets/dioxus/oxidrive_bg.wasm:3236497
    h758c38d8e961a82b http://localhost:8080/assets/dioxus/oxidrive_bg.wasm:3427820

Steps To Reproduce
Fortunately the affected code is an open source project 😄
Steps to reproduce the behavior:

git clone https://github.com/oxidrive/oxidrive.git (requires Rust, dx, Node 20 and NPM)
if you use Nix, nix develop installs all the required tools
cd web/app
npm install && npx tailwindcss -i ./input.css -o ./assets/styles.css
dx serve --hot-reload --bin oxidrive

The affected page is this one, and it seem to run fine until the API call finishes loading and goes past line 45.
Expected behavior
The page should render correctly as it does when compiled with dx build --release
Screenshots

Environment:

Dioxus version: 0.5.1
Dioxus CLI version: 0.5.4
Rust version: 1.78 stable
OS info: NixOS 23.11
App platform: web

Questionnaire

[x] I'm interested in fixing this myself but don't know where to start
[ ] I would like to fix and I have a solution
[ ] I don't have time to fix this right now, but maybe later

The Javascript interpreter is largely generated by sledgehammer so even the unminified version is not super easy to debug. I would recommend trying to minify the problem first and then if it is a diffing issue, walking through the mutations dioxus generates
The error you got could be caused by anything that modifies nodes on the page other than dioxus (like a chrome extension) or a diffing issue. If dioxus sends the wrong stream of edits to the javascript side, then it could try to access a node that doesn't exist.
Here are a few things to try to debug the issue:

Serve the application with dx serve --release. This will disable hot reload mode. The CLI currently has a bug that causes it to enable hot reloading even when you set it to false
It could be a diffing error. You could try to reproduce the issue by switching between the rsx blocks that happen when the resource finishes (rsx! { Loading {} } and rsx! { Pane {} }

The linked repo no longer uses dioxus and there is no reproduction of this issue. We have fixed several diffing bugs in the main branch of dioxus that may have been causing this issue. If anyone runs into a similar problem, feel free to open an new issue and we can debug more there


Temporal BEV feature align

Dear author,
Hello,
Great Works! When will the code be released?
Before the code is released, I am wondering how do you align the BEV features at different timestamps in your short-term/long-term temporal decoder. Can you give some clues?
Thank you for your time.

Hi @QixingJiang, thanks for your interest in our work.
We align all the BEV features to the current timestamp $t$, as illustrated in the Section 3.1 in our paper.

Thank you for your reply :)
I have tracked your code releasing today and found the corresponding code at
https://github.com/Sense-X/HoP/blob/bffcb2f02d568e9339cb827d9a5eedd961ab5323/mmdet3d_plugin/hop/detectors/hop_bevdet.py#L67
Now I get how it works!


Error with Ember-source version 3.3.0 to 3.4.8

After updating Ember-source to version 3.4.8, Ember sortable stopped working.
I was able make it work normally with Ember v3.2.2, but after v3.3.0 I get a console error.
I am not currently able to test with ember-source v3.5.x or above because I have other dependency breaking my app.
Steps to reproduce the behavior:

Install Ember source version 3.4.8
Try to drag and drop an element
See an error in console and all item are stuck

See the picture and the video (in .zip) of the error for more info.

error_video.zip

Ok updating to latest version fixed this issue. But I got other small bug with the latest version. Closing this issue.

Thanks for the report and the follow-up 🙂


[New Product] Add Mastodon

Mastodon follows Semantic Versioning. Its support and EOL policy is not
clearly defined, but supported releases are documented on its Security Policy page.

@Gargron, I am trying to reach out because you're part of the Mastodon team and I saw your name a few time in Mastodon's SECURITY.md page history, so I thought you could give us some insight about Mastodon security and EOL policy.
But first let me introduce you to endoflife.date. endoflife.date is a MIT Licensed website that documents EOL dates and support lifecycles for various products. It aggregates data from various sources and presents it in an understandable and succinct manner. It also makes the data available using an API and has iCalendar support.
We will soon add a page for Mastodon (that's what this PR is for) but before that I wanted to reach someone working on Mastodon to find out if what I wrote is correct. You can see a preview of this page on https://deploy-preview-2576--endoflife-date.netlify.app/mastodon.
When you have some time could you let me know if what's written on the preview page is correct and, if possible, how it could be improved ?

LGTM!

LGTM!

Ok, thanks a lot @Gargron.


Color and ColorPalette conflict

ColorPalette uses RGB values to determine colors for 16 rendering posibilities.
Color on the other hand, which I only now realized, uses a position to index which of those possibilities to display, so in other words engine assumes color as a 255 byte (16 foreground * 16 background) integer.
Color struct will most likely be renamed to PaletteColor while color indexing is likely to use
Color flags enum.

Solved with commit: https://github.com/LtLi0n/ConsoleGameEngine/commit/2179c459201d950101910aa0228953cd3eb68d64


Correction

Add "--partition-count 2" when creating the hub to avoid the error "Invalid PartitionCount 4 - value must be between 2 and 2."

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

ID: e2289383-6ce2-a036-c710-7d1fad6e1700
Version Independent ID: 3b902941-0876-17c3-3f0b-a4b7f7770531
Content: Quickstart create an Azure IoT Edge device on Linux
Content Source: articles/iot-edge/quickstart-linux.md
Service: iot-edge
GitHub Login: @kgremban
Microsoft Alias: kgremban

@mcurko Thanks for bringing this to our attention. We are currently investigating and will update you shortly.

@mcurko PR has been created to address this issue and update the doc. Changes will go live once it has been peer reviewed and merged.
We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Should we version the run container based on the OpenPegasus version

Today the container version tag is the version of OpenPegasusDocker.  Should we keep this or make it the version of OpenPegasus or the build environment.
The build tools changing is what changes the version of this repo release.

could we consider multiple repository names.

Name: where tag is some sort of versioning.   Thus we pegasus-server:0.1.3
v 2.`14.3


Suggestion - Community Calls Shared OneNote

Easy to see what what was discussed at the last community call and future ones as well

Great idea.

Did this get mentioned or at the community call yesterday or has it been added?? cc @raghushantha @joeyaiello

@kilasuit: We canceled this week's meeting due to the holidays.
I love OneNote and use it everyday, but I would prefer that we keep everything for this project within GitHub rather than spin up an external notebook/process that requires an additional app.
If it's okay, I have no problem opening up the Wiki for this project to public editing. Is everyone okay with that approach?

Sure. Wherever it makes the most sense to put this info.

Agreed - OneNote was just a suggestion but wherever this makes most sense - the key thing is that any discussions on the community calls are noted with decent levels of notes for reference.

The wiki is now open to all for editing. We will be front-loading a notes page for the upcoming community meeting. Feel free to append there any agenda items you'd like to discuss.
Thanks!


Issue with creating API through PUT/POST

Even with empty DB, this request currently fails for me locally:
curl --silent --request PUT --header "Content-Type: application/json" --data '{"name":"\"Somename\"","request":"{\"host\":\"%\",\"path\":\"/apis_status\",\"port\":80,\"scheme\":\"http\",\"methods\":[\"GET\"]}"}' "http://localhost:4001/apis/9C556157-2BAC-4901-8E3C-4471F0302D70"

The error is this:
{
  "meta": {
    "url": "http://localhost:4001/apis/9C556157-2BAC-4901-8E3C-4471F0302D70",
    "type": "object",
    "request_id": "7avvvl3ahin30empcu9kg7s1rjj88c2i",
    "code": 422
  },
  "error": {
    "type": "validation_failed",
    "message": "Validation failed. You can find validators description at our API Manifest: http://docs.apimanifest.apiary.io/#introduction/interacting-with-api/errors.",
    "invalid": [
      {
        "rules": [
          {
            "rule": null,
            "params": [],
            "description": "is invalid"
          }
        ],
        "entry_type": "json_data_property",
        "entry": "$.request"
      }
    ]
  }
}

This happens because you are sending request as a json-serialized string. Validation response should be clear on it.


Added delta parameter to subscribe request - to support delta fossil compression

Hello @Mahdibn
Thanks! But we still need the code which implements Fossil algorithm to decode deltas.

Hello @Mahdibn
Thanks! But we still need the code which implements Fossil algorithm to decode deltas.

Hello @FZambia
Ahh ok I will add it as well 👍🏻

Hello @FZambia,
I've just pushed an update to the PR that includes the implementation of the Fossil decoding algorithm. Please take a look when you have a chance and let me know if you have any further feedback.

@Mahdibn hello, this is cool! Could you please add test test cases to Fossil algorithm implementation? Probably re-use tests cases from other Fossil algorithm implementations? Ex. https://github.com/dchest/fossil-delta-js/tree/master/test

@Mahdibn hello, this is cool! Could you please add test test cases to Fossil algorithm implementation? I think it's very important to have. Probably re-use tests cases from other Fossil algorithm implementations? Ex. https://github.com/dchest/fossil-delta-js/tree/master/test

Hello @FZambia,
yes sure I will add them 👍🏻

Thanks the updates! I see this error in CI:
/Users/runner/work/centrifuge-swift/centrifuge-swift/Tests/SwiftCentrifugeTests/DeltaFossilTests.swift:32: error: -[SwiftCentrifugeTests.DeltaFossilTests testDeltaCreateAndApply] : failed - Could not find file origin
Test Case '-[SwiftCentrifugeTests.DeltaFossilTests testDeltaCreateAndApply]' failed (0.803 seconds).

Probably related to current working directory used during test run


IDVA6-1436 & IDVA6-1441: Refactor user addition flow and improve internationalization

Redirect to a dedicated "Cannot Add User" page instead of rendering in-line
Update controllers to handle user addition edge cases more consistently
Implement new cannotAddUserController for centralized error handling
Enhance internationalization support in views and JSON files
Update tests to reflect new user addition flow and error handling
Refactor constants and routes to support new "Cannot Add User" page
Improve error logging and user feedback in various controllers
Remove unnecessary user detail fetching in addUserController
Update footer and header partials with internationalized content

CI: No security warnings found

CI: No security warnings found

CI: No security warnings found


Integer row/col failing with wmts.gettile

We have found in Cartopy that we need to convert row/col from integers to string representations for the WMTS gettile method. I don't know if this is the intent, or if integers should be expected to work, but I thought I would start an issue here.
We work around in Cartopy with the following change minor change: https://github.com/SciTools/cartopy/pull/1052

Could someone using wmts give a comment on this issue?
@acrosby
Would be nice if you could provide a pull-request including a test. See:
https://github.com/geopython/OWSLib/blob/56410931e3234e46a077fb15c436294154c30a0c/tests/test_wmts.py#L12

Just run into this trying to use a Mapbox WMTS source in cartopy. It's a simple case of type error - since the string substitution is being done with 'replace' instead of 'format' there is no automatic type conversion from integer to string.
What needs to be clarified is whether row/col arguments are required to be strings to begin with (seems unlikely). If not then this should either use format or add a str cast.

this is probably because gettile is handled differently in RESTful only mode .. I could fix that in my case with appended patch of wmts.py
owslib_wmts.patch.txt

@chrisgraf Thanks for looking at this :) Please, could you provide a PR. It is easier to review and merge.

Sorry I missed the pings from this thread, thanks for taking a look


DRAFT - Unity Mod Manager compability

Hello. I'm trying to update this mod to work with Unity Mod Manager (https://www.nexusmods.com/planetbase/mods/43), which is the only mod loading solution that I have managed to get to work. Currently the Init() method returns this error:
[StorageGuru] Version '<IP_ADDRESS>'. Loading.

Non platform assembly: C:\Program Files (x86)\Steam\steamapps\common\Planetbase\Mods\StorageGuru\StorageGuru.dll.28166.cache (this message is harmless)
[StorageGuru] [Error] Error trying to call 'StorageGuru.StorageGuruMod.Init'.

[StorageGuru] [Exception] TargetInvocationException - Exception has been thrown by the target of an invocation.

System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.NullReferenceException: Object reference not set to an instance of an object

  at StorageGuru.ContentManager.Init () [0x00000] in <filename unknown>:0

  at StorageGuru.StorageGuruMod.Init () [0x00000] in <filename unknown>:0

  at (wrapper managed-to-native) System.Reflection.MonoMethod:InternalInvoke (object,object[],System.Exception&)

  at System.Reflection.MonoMethod.Invoke (System.Object obj, BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x00000] in <filename unknown>:0

  --- End of inner exception stack trace ---

  at System.Reflection.MonoMethod.Invoke (System.Object obj, BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x00000] in <filename unknown>:0

  at System.Reflection.MethodBase.Invoke (System.Object obj, System.Object[] parameters) [0x00000] in <filename unknown>:0

  at UnityModManagerNet.UnityModManager+ModEntry.Invoke (System.String namespaceClassnameMethodname, System.Object& result, System.Object[] param, System.Type[] types) [0x00000] in <filename unknown>:0

[StorageGuru] Not loaded.

[StorageGuru] Loading time 0.04 s.

My current understanding is that the ContentManager.Init() is responsible but I don't see why.
I would like some help with the port. Ideally once the port is finished it would be uploaded to Nexus either as an altrernative file in https://www.nexusmods.com/planetbase/mods/13 or a separate mod entirely.

I haven't had a chance to work out how to mod with UnityModManager yet, so I can't really help.
All I can is that the Patcher (that StorageGuru is written to work with) exposes many fields as public that weren't originally, so at a glance I'd say StringList.mStrings.Add("tooltip_manage_storage", "Manage Storage"); in ContentManager.Init may be the culprit because mStrings is probably not accessible

mStrings is shown as private in ILSpy but I use Krafs.Publicizer to make the whole Planetbase namespace available. Nevertheless, I've commented out that line and now mod loads without errors. I've loaded a pre-existing save, clicked on storage - no storage buttons. Same on a new save. No indication of an error in the log

Well without that line, it may fail to create the buttons because they use that tooltip on construction. As I say, I'm not familiar with the changes required to port to using Unity, so I can't really help

Ok thanks, take your time.

I worked on it a bit in the week - I've got a ported version of CheatTools working on the branch unitymm-port that you might find useful to look at... I started on CheatTools cause it's the simplest, but I reckon the techniques will be similar for the other mods. I pulled some of the helpersout into a helper project that I can hopefully use on the others...

Hi I think I've got a version of StorageGuru working against UMM on this branch. Feel free to check it out and see if it's working for you

It does. Thanks, I had problems with Reflections giving me compile errors. I see that rather than using them you relied on PlanetbaseModUtilites. Will try to keep that in mind when it comes to updating other mods.

Yeh PlanetbaseModUtilities is just a small helper library I made to standardize the reflection calls and Harmony/ModEntry setup bits so I could use them across my other mods... I got tired of writing .GetType().GetField() etc. over and over!
I'm not totally happy with all the changes I made to port StorageGuru so I'm going to do some more work to make it a bit more robust


Remove where parameter from transform lambda

Version: 1.0.0
The transform_t codec takes a function with two arguments to transform the decoded value. I propose that we remove the second parameter, where. It is there so that there is something to pass into the decode_exception constructor. It makes the function more boilerplatey and also means that you cannot easily use transform functions not specifically written for our JSON library, e.g., using an int2str function that takes an int and returns a std::string.
The original use case for the where parameter can be handled by catching any decode_exception thrown by the transform function and just setting the where parameter as appropriate before re-throwning the exception.

:+1:

+1

Nice. I like it


Change page DOM layout

Turn page header into h3.  Since we need to touch all legacy page
templates anyway to turn h2 tags into h3 tags we can finally clean
this up.
The following CSS classes need to be changed in page templates:

blackLayer -> black_layer
backgroundArea -> page_background
contentWrapper -> content_wrapper
videoWrapper -> uncropped_media_wrapper

The default header and content snippet

   <%= configuration['tagline'] %>
   <%= configuration['title'] %>
   <%= configuration['subtitle'] %>

 <%= background_image_tag(configuration['background_image_id'], {class:

"print_image"}) %>

<%= raw configuration['text'] %>

should be replaced with the following helper call:
<%= page_default_content(page) %>

REDMINE-16511

Coverage increased (+0.03%) to 99.292% when pulling a97229e971fc5422fc033e6eb8892916965fde39 on tf:h3 into 003c364e77a7c6042535cebf1ef200c772c2fe08 on codevise:master.


GH-34339: [R] Add skip_rows_after_names option to read_csv_arrow's options

Rationale for this change
The skip_rows_after_names option implemented in C++ was not exposed to R.
What changes are included in this PR?
The new skip_rows_after_names option is now available for the read_csv_arrow function.
> csv <- "a,b\n1,2\n3,4"
> arrow::read_csv_arrow(I(csv), read_options = list(skip_rows_after_names = 1))
# A tibble: 1 × 2
      a     b
  <int> <int>
1     3     4

Are these changes tested?
Tests are added for the new option.
Are there any user-facing changes?
The new skip_rows_after_names option can be used.

Closes: #34339

I absolutely agree that it would make a lot more sense if they were side-by-side in documentation such as vignettes. I don't think we currently mention these options in the vignettes at all, but that could make for a really helpful follow-up issue/PR.

Thanks for the suggestion. I have created a follow-up issue #34383 and would be happy to discuss it here.


Add Movie / TV Show videos in the detail fragments

Suggestion / Feature Request
Display the a list of different trailers and videos in the detail fragments as a horizontal pager where one can swipe or press on an arrow button (your choice which implementation you wanna go with, or you can implement both) to move to the next video
You can use YoutubeView  in the layout to display a video, usage in kt file to display a video->
youtubeView.loadData(key, "text/html", "utf-8")

The videos and their keys can be obtained using this api endpoint
For now we'll stick ourselves to only youtube videos so ignore the videos which have site other than "Youtube"

Hi @ken1000minus7  ,
i would like to try working on this issue . Could you please assign it to me .
Thanks

Sure @krishnachaitanya0107 , good luck 😊


Consider splitting out the CLI as a separate module

After reading sindresorhus's reasons for splitting out the CLIs from his modules, and seeing that Babel does a variation of this too (providing a CLI-free 'core' module), I've come to think it's a better approach.
I suggest making a new module, node-sass-cli, which would be a simple CLI wrapper for node-sass. (And remove all the CLI-related deps and code from node-sass itself.)
The benefits are:

Quicker and less error-prone to install node-sass as a dep. Currently, if I want to depend on node-sass, I am forced to download and install a redundant file watcher too, which itself has a bunch of dependencies plus a postinstall script that takes minutes and can even error out sometimes.
Separation of concerns. The -cli module can just focus on being a good CLI.
One is a global application, the other is a library for importing into your code. Separating them would allow for shorter and more focused readmes.

Examples:

pageres / pageres-cli
opn / opn-cli
postcss / postcss-cli

We still find some bugs in the "lib" code with cli.js, I'd love to have the parity between api.js tests and cli.js.
lib/render.js seems to live kind of on its own (used only by the CLI), good question where it should land, should we split.
And I think that bin/node-sass has a lot of redundant code and can be actually made much smaller.
I think in close future we will change the interface between the C++ bindings and the Javascript code and simplify JavaScript side a lot. Since I have introduced test/lowlevel.js to see how a "pure" C++ API feels like. Lots of similarities with what the CLI is doing actually...
But to me as a priority would be to de-orbit sass_types and write them in JavaScript (#1088). For example, we could add some of the existing color modules as a dependency and just ask bindings to create /accept instances of it. And finally use normal null and JavaScript strings. We could have sass-map, sass-list modules if needed. (Unfortunately we cannot rely on tuples here).

:+1:

@saper From what I can tell, this would cut the install size for the core with 14MB (on disk, from 26MB to 12MB) by getting rid of request, meow, gaze, npmlog, async-foreach, cross-spawn, get-stdin, in-publish (should be devdependency?) and sass-graph, which are only used for the cli. Not to mention that the shrinkwrap is cut from the current 824 lines down to 191, and the corresponding less requests done to npm to fetch all of these things.

Looking at some open CLI issues I am getting more and more convinced this is the way to go. I'd love to fix the C binding API to make it usable without excessive wrapping as we do currently plus moving watching and other stuff into a separate possibly advanced command-line module.

Let's see how we feel post v5. There'll be significant clean ups in this
area that may make this less relevant.
On 13 Nov. 2017 8:44 am, "Marcin Cieślak"<EMAIL_ADDRESS>wrote:

Looking at some open CLI issues
https://github.com/sass/node-sass/issues?q=is%3Aissue+is%3Aopen+label%3A"Module+-+CLI"
I am getting more and more convinced this is the way to go. I'd love to fix
the C binding API to make it usable without excessive wrapping as we do
currently plus moving watching and other stuff into a separate possibly
advanced command-line module.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/sass/node-sass/issues/1156#issuecomment-343770538,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAjZWGETSZyl2pO1vr32HYLn3c9mXD31ks5s12bQgaJpZM4F_eIt
.


Add signature verification

Description
This adds public key fetching and caching as well as verification of the signature of the config after fetching and after retrieving of the the cached config from file.
An improvement that I still need to work on is implementing safeguards against modifying the cached public key in shared preferences at PublicKeyCache (it can be modified on a rooted device). A solution for this might be to encrypt the public key using the Android Keystore before caching it.
Links
SDKCF-1094
Checklist

[x] I have read the contributing guidelines.
[x] I wrote/updated tests for new/changed code
[x] I ran ./gradlew check without errors

Codecov Report

Merging #11 into master will increase coverage by 0.82%.
The diff coverage is 86.92%.

@@            Coverage Diff             @@
##           master      #11      +/-   ##
==========================================
+ Coverage    82.9%   83.73%   +0.82%
==========================================
  Files           7       12       +5
  Lines         117      209      +92
  Branches        9       15       +6
==========================================
+ Hits           97      175      +78
- Misses         18       32      +14
  Partials        2        2

Impacted Files
Coverage Δ

...om/rakuten/tech/mobile/remoteconfig/AsyncPoller.kt
85.71% <ø> (ø)
:arrow_up:

...ch/mobile/remoteconfig/RemoteConfigInitProvider.kt
0% <0%> (ø)
:arrow_up:

...en/tech/mobile/remoteconfig/api/ConfigApiClient.kt
100% <100%> (ø)

...rakuten/tech/mobile/remoteconfig/PublicKeyCache.kt
100% <100%> (ø)

...tech/mobile/remoteconfig/api/HeadersInterceptor.kt
95.45% <100%> (ø)

...om/rakuten/tech/mobile/remoteconfig/ConfigCache.kt
97.14% <100%> (+1.68%)
:arrow_up:

...n/com/rakuten/tech/mobile/remoteconfig/MapUtils.kt
100% <100%> (ø)

...uten/tech/mobile/remoteconfig/SignatureVerifier.kt
100% <100%> (ø)

...n/tech/mobile/remoteconfig/api/PublicKeyFetcher.kt
83.33% <83.33%> (ø)

...uten/tech/mobile/remoteconfig/api/ConfigFetcher.kt
86.66% <86.66%> (ø)

... and 6 more

Continue to review full report at Codecov.

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

Codecov Report

Merging #11 into master will increase coverage by 0.82%.
The diff coverage is 86.92%.

@@            Coverage Diff             @@
##           master      #11      +/-   ##
==========================================
+ Coverage    82.9%   83.73%   +0.82%
==========================================
  Files           7       12       +5
  Lines         117      209      +92
  Branches        9       15       +6
==========================================
+ Hits           97      175      +78
- Misses         18       32      +14
  Partials        2        2

Impacted Files
Coverage Δ

...om/rakuten/tech/mobile/remoteconfig/AsyncPoller.kt
85.71% <ø> (ø)
:arrow_up:

...ch/mobile/remoteconfig/RemoteConfigInitProvider.kt
0% <0%> (ø)
:arrow_up:

...en/tech/mobile/remoteconfig/api/ConfigApiClient.kt
100% <100%> (ø)

...rakuten/tech/mobile/remoteconfig/PublicKeyCache.kt
100% <100%> (ø)

...tech/mobile/remoteconfig/api/HeadersInterceptor.kt
95.45% <100%> (ø)

...om/rakuten/tech/mobile/remoteconfig/ConfigCache.kt
97.14% <100%> (+1.68%)
:arrow_up:

...n/com/rakuten/tech/mobile/remoteconfig/MapUtils.kt
100% <100%> (ø)

...uten/tech/mobile/remoteconfig/SignatureVerifier.kt
100% <100%> (ø)

...n/tech/mobile/remoteconfig/api/PublicKeyFetcher.kt
83.33% <83.33%> (ø)

...uten/tech/mobile/remoteconfig/api/ConfigFetcher.kt
86.66% <86.66%> (ø)

... and 6 more

Continue to review full report at Codecov.

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

I left a couple of comments but looks great!
Also, the ci job failed.


Adding changes to make possible to debug blazor add-in

Adressing this question:
https://github.com/OfficeDev/Office-Add-in-samples/issues/444
Depends on a PR on CBA, I will add the link for the PR here soon.
https://devdiv.visualstudio.com/DefaultCollection/DevDiv/_git/CBA/pullrequest/442150
https://user-images.githubusercontent.com/4503299/208124863-8f5a4a70-e8cd-4ad8-b2c9-2c5ed2e71ba0.mp4

I cloned your fork but can't get this to work, I have tested with Microsoft Visual 17.5.0 Preview 2.0 and Microsoft Visual Studio 17.4.4.
with "just my code" disabled.
Are there any other requirements to make it work?

Yes, my PR on VS side is not reviewed/approved/merged yet.

Video looks good, very happy ... is there a version/ETA for me to know when I can test this?
@davidchesnut maybe you can test before that as you are also 'internal' 😜?

@davidchesnut can you approve and merge this change please?
Thanks!


[SUGESTION] Add demo with custom cell classes

I think a demo with custom cell classes will help some users.
For example the demo can integrate https://github.com/SwipeCellKit/SwipeCellKit for the cells

@Zasuk
Currently not supports custom cell class which not inherited from UITableViewComponentCell or UICollectionViewComponentCell.
I'll probably support it in the future, but haven't yet considered the best API design.

I’ll second this. Would like to see the possibility to create a cell node from (custom) UITableViewCell or UICollectionViewCell.

Ok, I'll support it in the future.
I'm still thinking about a better API design for it.

@Zasuk @wousser
I'm trying to add ability to use custom cell subclass for the container of component.
Draft: https://github.com/ra1028/Carbon/pull/21

Hi, i haven't tested it yet but the implementation looks ok for me (i was thinking in the same solution).
Thanks for the hard work and awesome lib


Drop web-ui.console_json_parser config option (#467)

Pull request opened by the merge tool on behalf of #467

Merged into branches iso6 in bcedbadc33b639b0948d51ecaacac2c0d2d363d7


Fix shadowed import warnings

Shouldn't build have failed in case of warnings?

These warnings lack position information in 0.11, so they don't get picked up by psa --strict. They're fixed in 0.12.


Sidecar HBONE: disable metadata exchange

Currently we still use MX for these, which is not desired

cc @kyessenov. Naively, seems like we need to be able to selectively enable it per endpoint instead of per cluster. Unless we already have that with alpn negotiation and we just have some mismatch there

No, you are right, we should always disable MX when using HBONE. Is the problem a mixed cluster, with some internal (tunnel) endpoints and some real endpoints?
ALPN negotiation should in theory work since HBONE is plaintext in the context of this upstream cluster. MX checks for its ALPN string to do anything.

I don't think it's mixed but our code doesn't differentiate anyways. Let me check what's going on with ALPN.
Does ALPN impact the http mx as well? That is what I was seeing, not the TCP one which would have completely broken the tratfic

HTTP MX doesn't check for ALPN (or TCP MX), and is known to leak headers everywhere.
It's inherently per downstream, so it would be a new rewrite to apply it as an upstream HTTP filter.

Not stale

Maybe, I don't quite understand which MX and where it's used. This might be referring to sidecars sending MX headers to ambient, which is yet another category for https://github.com/istio/api/pull/2910/files. Per earlier discussion, if a cluster is mixed with ambient and non-ambient endpoints, there's not much we can do.

The issue, iirc, is we add the HTTP MX headers to the inner payload of the HBONE request. Like the work in https://github.com/istio/api/pull/2910/files we can probably add logic in the proxy to not do this if we are going to tunnel it anyways. I don't think we need an API for that, just the proxy side to check the tunnel metadata

Isn't Greg's PR checking endpoint metadata? If not, then I agree that may be problematic

No, downstream filters only see clusters, upstream filters see endpoints. We can refactor it to be upstream filter but it adds to the scope.


Address performance/execution plan of TPCH query 9

Describe the bug
TPC-H Query 9 consumes a lot of memory and takes ~8s in memory on a 8 core machine on SF=1 in memory (with 100%cpu usage across cores) to execute. That likely has to do with the plan misses a equi-join and turns it into a cross join.
To Reproduce
Run query 9, check plan and execution time.
Expected behavior
The query is expected to finish faster (<1s) and shouldn't need a cross join.
Additional context
N/A

So I took a look at this and I have two solutions one which I believe always finds all possible inner joins but runs in N^2 and one that works for this case and should work for most others that runs in N LogN where N is the number of plans in the select statement. Is the N^2 runtime and the added petgraph dependency alright? I don't want datafusion to show up on Accidentally quadratic because of me haha. I've attached a brief description of each method incase there are any obvious improvements that can be made.
Thorough version
Code

Create undirected graph of plans where each edge represents a join connection.
Find the connected components of the graph.
For each connected component find the plan with the schema that has the fewest number of columns.
Cross join all of the previously selected plans into a new node, removing the selected nodes from the graph.
Starting from an arbitrary node, traverse the graph performing inner joins on all remaining nodes.

Less thorough version
Code

Iterate over plans counting the number of join key hits in each schema.
Sort plans so that plans that have no key hits are at the beginning and then the vector is sorted in descending order. E.g. the array (0,0,1,2,3,4) would be sorted to (0,0, 4,3,2,1). The rationale being that cross joins should prefer to run early to limit the amount of data that needs to be duplicated and that there are more likely to be joins to plans with many join keys.
Build the plan as was done previously.

The less thorough version was able to find the inner join that was missed for query 9 but there is still the possibility to miss inner joins. For example if the tables have the join relations as seen below, the order of the plans after sorting would be (B,F,D,A,C,E,G). Which means that the plan would generate a cross join between B and F as they share no join key pairs, missing the inner join through D.
┌─┐                ┌─┐
│A│                │E│
└┬┘                └┬┘
 │                  │
┌┴┐      ┌─┐       ┌┴┐
│B├──────┤D├───────┤F│
└┬┘      └─┘       └┬┘
 │                  │
┌┴┐                ┌┴┐
│C│                │G│
└─┘                └─┘

I believe this is now resolved so will close this. Feel free to reopen if I am mistaken.
Here is the logical plan for q9 in master:
Sort: profit.nation ASC NULLS LAST, profit.o_year DESC NULLS FIRST
  Projection: profit.nation, profit.o_year, SUM(profit.amount) AS sum_profit
    Aggregate: groupBy=[[profit.nation, profit.o_year]], aggr=[[SUM(profit.amount)]]
      SubqueryAlias: profit
        Projection: nation.n_name AS nation, datepart(Utf8("YEAR"), orders.o_orderdate) AS o_year, CAST(lineitem.l_extendedprice AS Decimal128(38, 4)) * CAST(Decimal128(Some(100),23,2) - CAST(lineitem.l_discount AS Decimal128(23, 2)) AS Decimal128(38, 4)) - CAST(partsupp.ps_supplycost * lineitem.l_quantity AS Decimal128(38, 4)) AS amount
          Projection: lineitem.l_quantity, lineitem.l_extendedprice, lineitem.l_discount, partsupp.ps_supplycost, orders.o_orderdate, nation.n_name
            Inner Join: supplier.s_nationkey = nation.n_nationkey
              Inner Join: lineitem.l_orderkey = orders.o_orderkey
                Inner Join: lineitem.l_suppkey = partsupp.ps_suppkey, lineitem.l_partkey = partsupp.ps_partkey
                  Inner Join: lineitem.l_suppkey = supplier.s_suppkey
                    Inner Join: part.p_partkey = lineitem.l_partkey
                      Filter: part.p_name LIKE Utf8("%green%")
                        TableScan: part projection=[p_partkey, p_name]
                      TableScan: lineitem projection=[l_orderkey, l_partkey, l_suppkey, l_quantity, l_extendedprice, l_discount]
                    TableScan: supplier projection=[s_suppkey, s_nationkey]
                  TableScan: partsupp projection=[ps_partkey, ps_suppkey, ps_supplycost]
                TableScan: orders projection=[o_orderkey, o_orderdate]
              TableScan: nation projection=[n_nationkey, n_name]


tableView might not exist in a custom UIViewController

Unfortunately, this won't work as it will cause a regression with https://github.com/clearsightstudio/ProMotion/pull/658/files#diff-87714b54dd76a747f2f5b12c0582ae77R210 and #655.
Perhaps introduce a method in your custom UIViewController that delegates tableView to table_view?
def tableView
  table_view
end