DynamoDBMapperConfig works in Java config but not in XML config

I tried to use a DynamoDB tablename prefix (e.g. "dev_", "qa_", etc.) with XML config as in this snippet:
    <!-- configure a different tablename prefix per environment, e.g. "dev_", "qa_", "prod_" -->
    <bean id="tableNameOverride" class="org.springframework.beans.factory.config.MethodInvokingFactoryBean">
        <property name="staticMethod" value="com.amazonaws.services.dynamodbv2.datamodeling.DynamoDBMapperConfig.TableNameOverride.withTableNamePrefix"/>
        <property name="arguments" value="${dynamo.tablename.prefix}" />
    </bean>
    <bean id="dynamoDBMapperConfigBuilder" class="com.amazonaws.services.dynamodbv2.datamodeling.DynamoDBMapperConfig.Builder">
        <property name="tableNameOverride" ref="tableNameOverride" />
    </bean>
    <bean id="dynamoDBMapperConfig" factory-bean="dynamoDBMapperConfigBuilder" factory-method="build" />

    <bean id="dynamoDBMapper" class="com.amazonaws.services.dynamodbv2.datamodeling.DynamoDBMapper">
        <constructor-arg index="0" ref="amazonDynamoDB" />
        <constructor-arg index="1" ref="dynamoDBMapperConfig" />
    </bean>

    <!-- spring-data-dynamodb configuration -->

    <dynamodb:repositories base-package="com.example.repository"
                           dynamodb-mapper-config-ref="dynamoDBMapperConfig" amazon-dynamodb-ref="amazonDynamoDB"/>

I tried a few alternatives to the above as well, but found that in all cases the tableNameOverride worked with DynamoDBMapper but was ignored by spring-data-dynamodb.  I was able to get the tableNameOverride working in spring-data-dynamodb by switching to Java config and following the directions on the wiki.
So it appears that handling of the dynamoDBMapperConfig does not work correctly with XML config.
Thanks for your continuation of this project!

Thanks for providing the XML. Need to transfer that into a Unit test


merge wip to main

new directory structure
gateway split into Gateway + Rollup
provider split into src/Chain + test/Provider
new rollups: Linea, ZKSync
redesigned rollup: OPFault
everything is finalized, removed unverified/unfinalized variants
new provers: EthProver, LineaProver, ZKSyncProver
redesigned delay and alignment logic

Merging down.
Notes:

Small notes added and discussed with @adraffy
Codebase feature complete, API stable, and functionally complete for initial release.

Additional work needed before stabilising main:

OP/Base Sepolia gateway tests not working. Fault proofs?

zkSync gateway tests 4 fail

Scroll gateway tests fail

test-gateways package script not consistently working..

bun test test/examples/ENSv2/owned-resolver.test.ts needs updating for recent changes.

Passing CI


Silverlight - ClickToPlay not working

As soon as the movie starts playing it's impossible to pause/resume it by clicking on the movie itself.
It gets paused on MouseDown but automatically resumes on MouseUp
It seems Silverlight version sends 'click' event on LeftMouseButtonUp which is handled in JavaScript, so eventually there are two state changes on MouseDown/Up.
I suppose triggering 'click' from Silverlight is intended, so you should change the condition in the following code
						// create callback here since it needs access to current
						// MediaElement object
						t.clickToPlayPauseCallback = function() {
							//

							if (t.options.clickToPlayPause) {
								if (t.media.paused) {
									t.play();
								} else {
									t.pause();
								}
							}
						};

to:
						// create callback here since it needs access to current
						// MediaElement object
						t.clickToPlayPauseCallback = function() {
							//

							if (t.options.clickToPlayPause && t.media.pluginType !== 'silverlight') {
								if (t.media.paused) {
									t.play();
								} else {
									t.pause();
								}
							}
						};

hey, any chance to have this fixed? is the above solution valid?

@bpampuch Is this still an issue?

Closing this issue since no answer has been posted in more than 2 weeks. If you'd like to reopen this, let us know. Thanks!


Question & Proposition

Hi Issam,
I'm sorry to ask you this question in issue format (I couldn't find any other way to contact you).
I just have a question about the latest changes on "weighted behavior". does this concern the following story :  "Use a contagion probability model for each individual"?
because I'm trying to understand these last modifications and I wanted to know the context first to easily understand the idea.
And I also have a proposal that we can add. since this algorithm models individuals, so it might be interesting to add a "deconfinement"  protocol, for example a test and isolation strategy. I explain, we can say that at the end of confinement, each sympthomatic person will be tested and also the  members of his family, then  eache positive person  will be isolated or hospitalized (in any case he can not infect anyone).
I preferred  to not write this in the backloc because it might be out of  scop of this study.
What do you think?

Hi Abdelmouise, yes this weighted behavior is the individual behavior dictionnary. I'll update the README. Every person has weights that can make the global lockdown values change slightly. I wanted to see the impact of a whole neighborhood (block) not following lockdown rules (it will be a scenario).
About your idea, it is a good one. Here is how I would see it :
So if a person is hospitalized (there others can be considered asymptomatic), there is a "test-isolation protocol" probability for each person he infected to be tested and then we make those persons isolated (no store, no work). It seems some changes are needed but definitely possible.
With probability 0 of test-isolation protocol, the current behavior should hold.
Good for backlog to me. You take it ?

I added it to the backlog, Yes i'll strat working on it

Hi Issam,
could you please add another branch, in which i push my commits? because the story of "test-isolation strategy needs a lot fo changes"   so I would like to push the changes even if they are incomplete, so you can follow the what i have done, and adapt the code as things progress without changing the Master branch.

Hi Abdelmouise, sure. I created a test-isolation-feature branch.
Can't wait to see the new feature.
Issam


Use better types for all timeout arguments

It looks like there may be other work on this area from perusing the existing issues and PRs, so maybe this is covered by that work already, but I wanted to use a Duration (or equivalent) for poll::poll(). Looks like there are a number of functions that could use this type treatment:

poll::poll()
event::kevent() (though this looks like a backcompat issue)
epoll::epoll_wait()

I'm not certain if there are rationales for why this hasn't been done already since it looks like some functions have been converted to use TimeSpec/TimeVal already.

I think part of the rationale was wanting to support old versions of Rust. Duration was only added in 1.3.0, and for a long time we supported back to 1.1.0. I think we now support ~1.7.0 so this could be revisited. @nix-rust/nix-maintainers thoughts?

If the type is stable in all supported Rust versions, definite +1 to using proper time/duration types as arguments.

Yeah, no objection from me.

This brings up an interesting point, both for users and developers, that the minimum supported rust version isn't explicitly stated anywhere, though your CI only tests Rust 1.7. Can this be added to the readme?

Can this be added to the readme?

That seems reasonable. I do believe we have tried to make a note of any changes to supported version in the changelog.

1.7 is the current minimum, I believe.
Re taking Duration, I'd suggest taking Into<Duration> or perhaps Into<TimeVal> / Into<TimeSpec> as appropriate for the function.

Why not just use Duration everywhere? #511 shows that if helper methods are desired they can just be implemented for Duration instead of introducing a new type. Or am I missing something and it's inappropriate or unergonomic in some cases?

@posborne @kamalmarhubi Any comments on this?

I agree that taking Duration would be more ergonomic and would be in favor of taking Into<Duration> (which will work just fine with a Duration due to reflexivity).  The only minor downside would be that we might need to do conversions more frequently if a syscall is made frequently (but even then the conversion overhead is approximately nothing compared to the syscall in most cases).

Would Rust be able to optimize across Into<Duration>? So we can have keep the nix-specific TimeVal and it contains the most common representation and if the Duration is converted back before use within a function, then Rust could optimize that out and no conversion would be done if you do back-to-back calls?

Regarding my comment above, it doesn't appear that Rust can reach through multiple From types. It's likely we'll want to have From implementations between several types. The types used for relative time currently is:

poll::poll() - uint of ms
event::kevent() - timespec
sys::epoll::epoll_wait() - int of ms
select::select() - timeval
sys::aio_suspend() - timespec
sys::Dqblk::{block_time_limit, set_block_time_limit, inode_time_limit, set_inode_time_limit} - implied to be time_t or target-specific type holding seconds
unistd::sleep() - uint seconds

Some more notes:

sys::epoll::epoll_wait() uses an int to store ms units, but then uses -1 and 0 as special values.
select() actually modifies the timeout argument.
pselect() uses a const timespec *

I think this discussion should only attempt to address the TimeSpec and TimeVal types here. My current proposal is change functions that take TimeVal or TimeSpec to instead take Into<TimeVal> or Into<TimeSpec> where possible (select() uses it as an output value, so it couldn't with this). Then we can also implement From<Duration> for both of these types to facilitate passing Duration types directly into these functions. I'd therefore also suggest that we remove all arithmetic operations on both of these types in favor of doing that through the Duration type instead. It should be fairly uncommon to do arithmetic from these types anyways, especially if users are using Durations as the backing datatype and a conversion occurring to pass to the function. I think I know what this will look like so I'll write up an implementation and we'll see where we get. This will likely supplant #511.


Improvements in ByteBuffer read path

For Apache Drill, we are looking to pass in a buffer that we have already allocated (in this case from Direct memory), wrapped in a ByteBuffer.
The current effort to allow a ByteBuffer read path is great except that the interface allocates the memory and there is no way for an application to pass in memory that has been allocated or (even better) to provide an allocator.
Additionally, it would be great to be able to use the same approach while decompressing.
As a starting point here is a patch on top of the ByteBuffer read effort that adds a function in CompatibilityUtils and also adds a ByteBuffer path for the Snappy Decompressor. The latter requires Hadoop 2.3 though, so some discussion on this would be called for.
Please let me have any feedback and I can make changes/additions.
Reporter: Parth Chandra / @parthchandra
Assignee: Jason Altekruse / @jaltekruse
Related issues:

Binary column statistics error when reuse byte[] among rows (contains)
ColumnChunkPageWriter uses only heap memory. (relates to)
Move off of Parquet fork (is depended upon by)

PRs and other links:

GitHub Pull Request #49

Note: This issue was originally created as PARQUET-77. Please see the migration documentation for further details.

Dmitriy V. Ryaboy / @dvryaboy:
Thanks!
Can you post this as a pull request to the github repo?
You can see the recommended process for contributions in CONTRIBUTING.md:
https://github.com/apache/incubator-parquet-mr/blob/master/CONTRIBUTING.md

Parth Chandra / @parthchandra:
Added a pull request-
https://github.com/apache/incubator-parquet-mr/pull/49

Julien Le Dem / @julienledem:
Issue resolved by pull request 267
https://github.com/apache/parquet-mr/pull/267


Something went wrong page when trying out redirect to IS error page from adaptive script.

Describe the issue:

We have an adaptive function (sendError) to direct the user to IS error page with custom error messages.

This has been broken in the latest versions due to a content spoofing fix. So as a solution, we need to store these error content to cache and retrieve back from the page and show it to the user.

@senthalan are we good to close this issue?

yes. this can be closed


Support for breakpoint debugging

PTAL, this is a moderately large change that we'll likely have to iterate on quite a bit.
The major shortcoming here is that this is only worker for single service configs, with multiple services we attempt to launch multiple inspector threads on the same port. This should be fixable, but it would be good to feedback in the interim.
Thanks.

The major shortcoming here is that this is only worker for single service configs. This should be fixable, but it would be good to get feedback in the interim. The specific example that fails is ssh://git@bitbucket.cfdata.org:7999/~bcoll/workerd-bus-error-10.git

This is addressed in the second commit. Wrangler does not expect to package multiple user written workers in a config, but may in practice. With the second commit chrome devtools would be able to debug any code referenced by the config. Wrangler devtools only wants to be able to debug the user written workers (except if they need to debug their stuff).

Sadly, it appears my comments were lost. Ugh.

@kentonv, friendly ping, last comment incorporated on 7/14, thanks.

(Sorry for the slow review, this fell off my radar last week somehow.)

awesome, approved!
hopefully this fixes setting breakpoints in vscode
is there a target release to include this PR?
Thanks!

I assume you've tested this running in the fiddle service (internal codebase)? That should be a pretty easy way to verify it works with the internal threading model, in addition to the workerd model.

Yes, you can set breakpoints and single step. Logging to console and heap querying appear to still work as before.


AdaptMember attribute only Memberside ?

Hi,
I have a Entity Framework model which has terrible names like
    public class User
    {
        public int UserIdentification {get; set;}
    }

Then I have a DTO used by my Business models like this:
    public class UserDto
    {
        [AdaptMember("UserIdentification"]
        public int UserId {get; set;}
    }

This works lovely and the UserDto UserId gets set as expected. Then we have some API models like this:
    public class UserInfo
    {
        public int UserId {get; set;}
    }

The issue I am having is I cannot get the UserInfo UserId value set via an Adapt():
    userDto.Adapt<UserInfo>();

Unless I add the AdaptMember attribute as set on the DTO User. I don't want to do this as then the API model seems tightly coupled to the database, just seems I must be doing this incorrectly.
Any help is appreciated!

Will add in future version. For now, you might need to config using Map instead of attribute.

Will add in future version. For now, you might need to config using Map instead of attribute.


Fix: memory leak of velaux apiserver

Signed-off-by: Jianbo Sun<EMAIL_ADDRESS>Description of your changes

Fixes #
I have:

[ ] Read and followed KubeVela's contribution process.
[ ] Related Docs updated properly. In a new feature or configuration option, an update to the documentation is necessary.
[ ] Run make reviewable to ensure this PR is ready for review.
[ ] Added backport release-x.y labels to auto-backport this PR if necessary.

How has this code been tested

Special notes for your reviewer

@barnettZQG will send a new one with more enhancements

ref to
#4773


Add Web Authentication API demo to the Test Drive Demos

The live demo is here. The code implements a polyfill (webauthn.js) to bridge the gap between the new Web Authentication API and the preliminary Microsoft implementation. It also showcases a demo website which demonstrates how the register and logon flow looks like when using the new API. The current codebase only implements the client-side code. The public keys generated by the WebAuthN API are typically sent to the server but, in this codebase, only stored in indexedDB.
All images and libraries used here are either free or under Apache 2.0 license.

The link to the live example was changed to match the name of the API. It used to point to the fido folder but it now points to the webauthn folder: demo.

There was some misunderstanding between me and Adrian, who created the original version of the polyfill. Closing this pull request and sending a new one with a more up-to-date polyfill.


add basic "howto" for using Terraform with EKS-Anywhere

A simple document which lays out steps for managing an EKS-A cluster with the Terraform Kubernetes provider.
This is meant as a first-step PoC. Following this doc will allow you to start managing mutable fields of an EKS-A cluster with the K8s terraform provider. Any field which the controller can reconcile (and the webhooks allow you to mutate) can be managed using this approach.
This also adds an 'examples' top level directory, this will make it easy to add additional content for how-to examples like this over time
Where this is going to ge interesting is when we can reconcile workload cluster objects; then, we can easily generate multiple workload clusters at a time and scale up/down the number of workload clusters with the modification of a single variable. will also generate a howto and examples for this when the time comes.
additions to this doc:

which fields are mutable?
iterative loops to create multiple worker node group configurations from one block definition

things we should consider adding to eks-a:

auto-generate TF for cluster resources using a command like eksctl anywhere generate terraform or the like

thanks for proof-reading this folks...this is what happens when you write docs in VIM 😄


Retry timeouts only

I would like to propose a flag that when used with retries it would only retry on timed out tests. This would help with retrying only flakey tests.

@gita-codaio thank you for your proposition.
I don't think we need such a granular configuration on CLI/config file  level. On flaky tests you can set retries:

it('flaky test', async function() { this.retries(2) });
it('flaky test', async function() {  })retries(2);


Add support for SHA256

I feel like there was one algorithm missing!

:+1: I just needed this exact same thing, and implemented it on my own only to find @FWFabio had an identical pull request already open.
Thanks for the library, @JoeKun.


Release pynndescent 0.3.0

It would be good to do a new release. The last release was 0.2.1 in July last year (https://pypi.org/project/pynndescent/).

I ran pyroma (via Prospector), a linting tool specifically for setup.py, and it suggested a few minor changes that might be worth including. I will supply a PR later today.

Thanks @jlmelville!

Thanks @tomwhite and @jlmelville for all the work you have both put into this recently -- it has been greatly appreciated. I really hope to get some time soon to go through and properly catch up with everything and start adding a few bits and pieces (multi-threaded trees, dask support, etc.) In the meantime, yes, this is definitely worthy of a 0.3 release -- I'll wait for James to make his changes, and try and get it done in the next day or so.

Thanks @lmcinnes.
Re dask support, I have got a branch that I wrote a while ago. I'll post it soon.

Before we release this I was thinking it would be good to be sure that the API for running in threaded mode is what we want. I've started looking at joblib to see if we can use that.

I'm happy with the current state, but understand if you want to address a few of the remaining joblib related bits and pieces first (alternatively we can add those in a 0.3.1 as needed). Let me know.

I think it's worth removing chunk_size from the API for NNDescent or at least making it optional. I will submit a PR. (Other bits and pieces can wait for a point release.)

Thanks for releasing 0.3.0 @lmcinnes!

Glad to see all your and James' work make it out into a release.


[Snyk] Security upgrade cryptography from 41.0.3 to 41.0.4

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to fix one or more vulnerable packages in the `pip` dependencies of this project.
Changes included in this PR

Changes to the following files to upgrade the vulnerable dependencies to a fixed version:

server/backend/requirements.txt

Vulnerabilities that will be fixed
By pinning:

Severity
Priority Score (*)
Issue
Upgrade
Breaking Change
Exploit Maturity

97/1000  Why? Confidentiality impact: None, Integrity impact: None, Availability impact: High, Scope: Unchanged, Exploit Maturity: No data, User Interaction (UI): Required, Privileges Required (PR): None, Attack Complexity: Low, Attack Vector: Network, EPSS: 0.00043, Social Trends: No, Days since published: 12, Transitive dependency: Yes, Is Malicious: No, Provider Urgency: Medium, Package Popularity Score: 99, Impact: 5.99, Likelihood: 1.61, Score Version: V4
Denial of Service (DoS) SNYK-PYTHON-CRYPTOGRAPHY-5914629
cryptography:  41.0.3 -> 41.0.4
No
No Known Exploit

(*) Note that the real score may have changed since the PR was raised.
Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the affected dependencies could be upgraded.
Check the changes in this PR to ensure they won't cause issues with your project.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings
📚 Read more about Snyk's upgrade and patch logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Denial of Service (DoS)

duplicate as #923


Reuse the same connection to work with multiple Redis modules

I am using RedisGears and RedisTimeSeries modules for one of my databases. I would like to reuse the same connection to run RedisGears and RedisTimeSeries commands and don't worry about managing multiple connections for each module.
Similar to:
r = new Redis()
r.ftSearch()
r.graphQuery()
r.tsRange()

Thank you.

@mikhailredis Version 0.3.7 should be deployed in a few moments.
Code snippet:
import { Redis } from 'redis-modules-sdk';
const client = new Redis(...)
await client.connect()
await client.redis.set(....);
await client.search.search(....)
await client.disconnect()

The available class properties are:
redis -> IORedis
rejson -> ReJSON module
graph -> RedisGraph module
gears -> RedisGears module
search -> Redisearch module
bloom -> RedisBloom module
bloomTopK -> RedisBloomTopK filter module
bloomCuckoo -> RedisBloomCuckoo filter module
bloomCMK -> RedisBloomCMK filter module
ai -> RedisAI module

Available functions are:
.connect() -> This connects all class properties in the 'Redis' obj
.disconnect() -> This disconnects all class properties in the 'Redis' obj

Please make sure you give out some feedback, it's important it fits you as wanted.


Lot of TODO's in the GDPR Compliance page

This page has lot of TODO's. Shall we fix those soon?
https://docs.wso2.com/pages/viewpage.action?pageId=85392485

This is the purpose of TODO in WIP document, so why create an issue for such things?

This issue was raised, so that the TODO's won't be missed and will be addressed soon. Since we are relying entirely on docs, having TODO's at this stage blocks us verifying the content in that page.

Fixed.


Unit/Data Type Consistency?

Should points with the same units use the same data type throughout all the 7xx models?

As long as the data type can hold the largest value needed for the units, then it can't hurt, other than maybe taking up a little more space and bandwidth. For example, ESHzHi is specified in IEEE 1547-2018 as having 0.1Hz resolution, while grid frequency measurements may need to be made in 0.001Hz resolution. Both are measured in Hz. In this case, the two data types don't need to be the same, but they can be as long as the type can accommodate both resolutions (would need to be 32bit), and implementations can simply ignore the extra resolution in ESHzHi if not needed.

The list of updated types and units:

Models 709, 710, 711: change 'Hz' point type to 'uint32'
Models 701, 704: 'Pct' type Points to 'uint16'
Models 705, 706, 711, 703: 'Secs' type Points to 'uint32'
Model 704: '%Max/Sec' type Points to 'uint16'
Models 712, 705: 'VarPct' type Points to 'uint16'
Model 706: 'DeptRef' type Points to 'uint16'
Model 712: 'WMaxPct' type Points to 'uint16'


Separate vision_layer

Since we are going to develop a separate vision_layer , which was before incorporated in the task_handler_layer, so we need to decide its organisation. For now, I have made a basic layout of the layer which can be used as a starting point to work on.
vision_layer/
├── calibration
├── cfg
├── CMakeLists.txt
├── color_processing
├── feature_detectors
├── filters
├── launch
├── package.xml
└── src

Shouldn't color_processing, feature_detectors and filters just be libraries? In that case, all of that would come under include directory, right?

Yeah...Right, all will be under include. Then the layout will be..
├── calibration
├── cfg
├── CMakeLists.txt
├── include
│   ├── color_processing
│   ├── feature_detectors
│   └── filters
├── launch
├── package.xml
└── src

How is each task being dealt with in this case?

feature_detector will be responsible for getting all the features from an object like its coordinates, contours, etc. It will contain the target specific code to get the info about the targets like buoy_detector, gate_detector, etc. The main code will be written inside src which will sequentially send the information to the task_handler_layer using the feature_detector lib.

Hm so how about we have a separate package named vision_commons which will have all the common libraries that we create and then separate packages for each task? Also, I was thinking of using service-client nodes for tasks instead of normal subscribers-publishers.

Instead of making separate packages, why can't we make special classes for the tasks and include those classes in the main vision code. So, there will be no separate packages for doing the tasks but one main vision code where we can create objects for handling all the detection related work and executing them sequentially according to the motion plan.

Also by making separate packages we will repeat the same thing again. One of the things that I felt wrong with the previous code was a lot of repetition. Even for different tasks containing 300 lines of code there is literally very few lines of difference. By doing the first way we can use the inheritance property of C++ and develop a base obstacle_detector class and derive the other classes from it.

Anyway, I will make a full proof plan of the whole thing that I have in mind, with all the pros and cons and get back to you @Mayankm96 .

In my opinion, this should be the package structure
├── calibration
├── cfg
├── CMakeLists.txt
├── include
│   ├── color_processing
│   ├── feature_detectors
│   └── filters
├── launch
├── package.xml
└── src
     ├── buoy_detection.cpp
     ├── gate_detection.cpp
     ├── .
     ├── . more nodes
     ├── .
     └── last_node.cpp

This is essentially what @ksakash said.
I don't see the point of making an entirely new package only for the libraries, since we are writing those files in vision_layer/include and this library won't be used anywhere else except vision_layer. I agree with @Mayankm96 that we can use a client-service system instead of subscriber-publisher because we will need only one type of data (buoy, gate, marker dropper...) at a time and not all types of data at all times. What type of data is needed at a particular moment will be decided by master_layer.

The only reason why I suggest to have different packages is to avoid having too many nodes inside one package itself.  Moreover, the service messages would be added to the hyperion_msgs package since it is a recommended way to organize a ROS repository.

Hmm... We will not need too many nodes or packages. According to the plan there will separate classes for each mission element to handle all the operations to get the necessary information, under feature_detector. We can apply Service in the classes too, i guess, by initialising a node_handle inside the classes. So, we will not need distinct nodes for each task, but just separate objects to handle each tasks, which will be included in a single vision code.

@ksakash just wanted to know that is this organisation of vision layer being followed for our new vehicle........?????

We can close this issue I believe.


how can i use in with hilt?

and this methods are undefined:                     setupNavigation("splash") {                         splashScreen()                     }

You can try 1.3.0-beta04 version and add odyssey-android in dependencies or wait stable 1.3.0 release

You can read documentation about this here - https://github.com/AlexGladkov/Odyssey/blob/rc/release-1.3.0/documentation/HILT.md
And it works only in 1.3+ versions


Use go modules with go1.11

I tried to update Go version to 1.11, but even though it compiles fine on Mac (without using any flags, using go build .)
when I run docker build . it fails with:
loadinternal: cannot find runtime/cgo

then I tried few things and found that -linkmode external (with Go 1.11) seems to be the problem (even on Mac); couldn't find a fix yet. If someone knows, please let me know. Thanks

This PR doesn't use the vendor/ directory and downloads things from scratch.

We might need to set GOFLAGS=-mod=vendor to enforce use of vendor but that will prevent go-get'ing gox.
The best solution here could be just removing vendor/ for good.

thanks! let me try.

I just revisited this by rm -rf vendor/ Gopkg* and initialized module cleanly. I nicely got a file like:
module github.com/grpc-ecosystem/grpc-health-probe

require google.golang.org/grpc v1.17.0

and builds seem to be working fine ✅ once I:

changed release step (gox) to env -u GOPATH gox (which unsets GOPATH)
deleted dep related steps

in travis.yml. Build: https://travis-ci.org/grpc-ecosystem/grpc-health-probe/builds/470400544
Would you like to make these changes yourself –or want me to push to your branch (it'll still get merged with your name)?

@ahmetb I am so sorry, I moved to Android team and didn't have time look at it again, now I still don't have Go setup on this machine, I will be thankful if you can push to this branch.
thank you!

Thank you so much!


[IMP] Traeffik 3 compatibility

New Feature Added: Doodba Copier Template Now Compatible with Traefik 3
With these changes, the Doodba Copier Template is now compatible with Traefik 3. When selecting Traefik as the proxy, you can choose which version to use. By default, version 2 is selected as it is the most stable.
Additionally, this PR includes the Traefik version in the test matrix and excludes tests with insecure connections for Traefik 3 due to incompatibilities.

Be careful, the version that was published for Traefik 3 does not support exposed databases or subdomains.

I hope the tests carried out here are helpful: Solution

Hi, I tested Traefik 3, but the paths_without_crawlers feature is not working. If you navigate to /website/info, it still shows the information. Is this change intentional?

Hi, I tested Traefik 3, but the paths_without_crawlers feature is not working. If you navigate to /website/info, it still shows the information. Is this change intentional?

It was a mistake. Fixed here https://github.com/Tecnativa/doodba-copier-template/pull/483


[21973] Update commercial support section

This PR updates the commercial support section

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 26.34%. Comparing base (63f6158) to head (ab0de97).

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #163      +/-   ##
==========================================
+ Coverage   24.99%   26.34%   +1.35%
==========================================
  Files          75       56      -19
  Lines        5842     3671    -2171
  Branches     2999     1811    -1188
==========================================
- Hits         1460      967     -493
+ Misses       3426     2030    -1396
+ Partials      956      674     -282

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


How can I add watermark in Video

can I add watermark ?

Yas you can, try the placing view above ffmpeg surface view or modify player_decode_video code


not add Registry Custom

Not add custom Registry Credentials *

Useful
Info

Versions
Rancher v2.4.3 UI: v2.4.22

Route
undefined

I got the same issue. In the console i've got the following error :
component.js:79 Uncaught TypeError: Cannot read property 'id' of null
    at n.willSave (component.js:79)
    at n.save (new-or-edit.js:54)
    at e.n._join (backburner.js:1048)
    at e.n.join (backburner.js:759)
    at p (index.js:176)
    at glimmer.js:7609
    at s (index.js:143)
    at n.save (glimmer.js:7608)
    at n.save (component.js:55)
    at n.send (action_support.js:19)

There is the same problem in #27373.

Just tested it with a signle namespace, works perfect!
This only happs, when the option Available to all namespaces in this project is selected.

@rancher/qa can we re-test this? I believe the main issue was found and resolved in the attached PR.
https://github.com/rancher/rancher/issues/26981

Reproduced the issue with v2.4.4
Validated with v2.4.5-rc6.

Create a registry credential available to all namespaces choosing address Dockerhub/quay.io/artifactory/custom and provide username/password.
Registry gets added correctly with no errors.

Note: Also verified that creating registry available for a single namespace is functional.


Support copas.sleep() in the main thread

Useful when writing functions that work both in and out of a copas context.

This is a piece of code I had laying around forgotten, decided to just throw the PR in there in case it's useful (I'm not using this or plan to give it further thought :) )

I don't like this change. Because it might implicitly block everything. If you know you're on the main thread then call socket.sleep, if you don't know then your code is faulty or you don't know what you're doing.

It wasn't about the programmer not knowing. It was about writing reusable functions that work either inside or outside a coroutine context without having to write the boilerplate every time. I did have a use case for this when I wrote this, for sure, but I don't even remember what I was working on. I just bumped into this branch because someone pinged me on Github. So nevermind :) (just writing this message to clarify that this function wasn't written out of laziness, but to allow for reusability -- it sucks having to write code one way in one context and one way in another (e.g. the OpenResty contortions for "you can do X in this phase but not on that phase"))

ok, good to know, let's leave the branch around


Problem with futures in 3.6.0b2 when "coverage" is enabled

I recently installed Python 3.6.0b2 and I've run into a problem with the handling of result values in asyncio Futures. This only seems to be triggered when I run with "coverage" enabled, but the problem appears to be specific to changes in asyncio between 3.6.0b1 and 3.6.0b2. Here's a small test program which reproduces the issue:
import asyncio

@asyncio.coroutine
def coro(fut):
    fut.set_result((1, 2, 3))

@asyncio.coroutine
def test():
    fut = asyncio.Future()

    asyncio.ensure_future(coro(fut))

    print((yield from fut))

asyncio.get_event_loop().run_until_complete(test())

When I run this as "python3.6 test.py", I get the proper output of (1, 2, 3). Similarly, when I run it with older version of Python with coverage enabled, like "python3.5 -m coverage run test.py", I get the same result. However, when I run "python3.6 -m coverage run test.py", the return value changes to just 1 (the first value in the tuple), discarding the rest.
I haven't tracked down the specific change in asyncio which is causing this, but reverting just the asyncio Python components back to 3.5 (which still running the 3.6 interpreter and rest of the 3.6 library) was enough to fix the problem. I think this will probably be the case if I go back to the 3.6.0b1 version of the asyncio module as well as I had no problems with that, but I haven't had a chance to revert back to that yet.

Just tried replacing the asyncio module with the version from 3.6.0b1, and confirmed that the problem was definitely introduced between 3.6.0b1 and 3.6.0b2. I'll try to narrow it down further when I get some time later this week.

It may be http://bugs.python.org/issue28492
Removing _future extension module may solve it.

This problem is exactly the one that http://bugs.python.org/issue28492 fixed. I'll close this issue, @ronf thanks for reporting this and feel free to reopen.

Thanks - that does look like it might be it, and disabling lib/python3.6/lib-dynload/_futures.cpython-36m-darwin.so does appear to work around the issue for now!


Configurable version selector

When you browse to documentation for a module that exist only in the 4.x stack (e.g SQL Client Templates), the version selector still indicate all known versions.
If this selector is configurable, we could filter out versions that do not include the current module.
Is that doable @michel-kraemer ?

Very good point. This can be implemented. I will assign this issue to me.

Thank you Michel!


disable webPreferences.nodeIntegration, drop usage of v-html

in index.js, webPreferences.nodeIntegration shall not be used
v-html is used to display articles in the news section, it should be dropped in favour of a WebView or equivalent

closed in favour of #324


WIP: better remote windows

The goal is to simplify how we handle remote stores allowing us to use immutable on all stores (tracker, config, etc)

[x] Port config to immutable
[ ] make pinenentry work
[ ] Make menubar work
[ ] Other remotes w/ access to config

TODO remake vs master once 23 goes in


Reproduction: Recursion fails in ECDSA circuit

This draft PR exposes a bug: It seems that recursion (verifying other proofs) can't be used as part of a circuit that verifies an ECDSA signature. The proof fails in wrap_main (detailed error below).
I have no clue yet what exactly about the ECDSA circuit causes this problem, but confirmed that it does not occur for a simple circuit which does practically nothing apart from the recursion. The location of the error indicates some connection with feature flags.
Associated issue: #1336
To reproduce:
npm i && npm run build
./run src/lib/gadgets/ecdsa-recursion-isolated.unit-test.ts

It fails in exists when trying to witness the Req.Evals request:

Full error message:
Error: Option.value_exn None
    at raise (ocaml/base/error.ml:8:21)
    at value_exn (ocaml/base/option.ml:123:68)
    at a_typ (src/lib/pickles_types/opt.ml:80:36)
    at var_of_fields (src/lib/snarky/src/base/typ.ml:181:55)
    at _pwu_ (src/lib/snarky/src/base/typ.ml:354:39)
    at _pwu_ (src/lib/snarky/src/base/typ.ml:355:42)
    at _pwu_ (src/lib/snarky/src/base/typ.ml:355:42)
    at _pwu_ (src/lib/snarky/src/base/typ.ml:355:42)
    at _pwu_ (src/lib/snarky/src/base/typ.ml:355:42)
    at _pwu_ (src/lib/snarky/src/base/typ.ml:355:42)
    at _pwu_ (src/lib/snarky/src/base/typ.ml:355:42)
    at _pwu_ (src/lib/snarky/src/base/typ.ml:355:42)
    at _pwu_ (src/lib/snarky/src/base/typ.ml:355:42)
    at _pwu_ (src/lib/snarky/src/base/typ.ml:355:42)
    at _pwu_ (src/lib/snarky/src/base/typ.ml:355:42)
    at var_of_fields (src/lib/snarky/src/base/typ.ml:181:55)
    at _pwu_ (src/lib/snarky/src/base/typ.ml:354:39)
    at _pwu_ (src/lib/snarky/src/base/typ.ml:355:42)
    at var_of_fields (src/lib/snarky/src/base/typ.ml:181:55)
    at _pwu_ (src/lib/snarky/src/base/typ.ml:354:39)
    at var_of_fields (src/lib/snarky/src/base/typ.ml:181:55)
    at _pwu_ (src/lib/snarky/src/base/typ.ml:354:39)
    at var_of_fields (src/lib/snarky/src/base/typ.ml:181:55)
    at var_of_fields (src/lib/snarky/src/base/typ.ml:181:55)
    at var_of_fields (src/lib/snarky/src/base/checked_runner.ml:279:31)
    at <anonymous> (src/lib/snarky/src/base/checked_runner.ml:54:30)
    at run (src/lib/snarky/src/base/snark0.ml:749:27)
    at exists (src/lib/snarky/src/base/snark0.ml:1213:11)
    at <anonymous> (src/lib/pickles/wrap_main.ml:269:17)
    at with_label (src/lib/snarky/src/base/snark0.ml:1253:15)
    at <anonymous> (src/lib/pickles/wrap_main.ml:261:11)
    at with_label (src/lib/snarky/src/base/snark0.ml:1253:15)
    at main (src/lib/pickles/wrap_main.ml:159:18)
    at <anonymous> (src/lib/pickles/wrap.ml:887:59)
    at handle (src/lib/snarky/src/base/snark0.ml:1237:15)
    at _iy5_ (src/lib/pickles/wrap.ml:887:13)
    at mark_active (src/lib/snarky/src/base/snark0.ml:1167:19)
    at _piV_ (src/lib/snarky/src/base/snark0.ml:1302:52)
    at as_stateful (src/lib/snarky/src/base/snark0.ml:755:15)
    at handlers (src/lib/snarky/src/base/runners.ml:82:22)
    at <anonymous> (src/lib/snarky/src/base/runners.ml:337:13)
    at <anonymous> (src/lib/snarky/src/base/runners.ml:305:34)
    at <anonymous> (src/lib/snarky/src/base/snark0.ml:1302:19)
    at finalize_is_running (src/lib/snarky/src/base/snark0.ml:1272:15)
    at generate_witness_conv (src/lib/snarky/src/base/snark0.ml:1301:7)
    at <anonymous> (src/lib/pickles/wrap.ml:885:23)
    at time (src/lib/pickles/common.ml:69:3)
    at wrap_vk$1 (src/lib/pickles/wrap.ml:854:5)
    at withThreadPool (/home/gregor/o1/mina/src/lib/snarkyjs/src/bindings/js/node/node-backend.js:55:14)
    at prettifyStacktracePromise (/home/gregor/o1/mina/src/lib/snarkyjs/src/lib/errors.ts:137:12)
    at prove_ (/home/gregor/o1/mina/src/lib/snarkyjs/src/lib/proof_system.ts:394:18)
    at async file:///home/gregor/o1/mina/src/lib/snarkyjs/dist/node/lib/gadgets/ecdsa-recursion-isolated.unit-test.js:44:13

context https://o1-labs.slack.com/archives/C01UNQH8XEZ/p1702989926504659?thread_ts=1702973753.503689&cid=C01UNQH8XEZ

after the update to latest develop (https://github.com/o1-labs/o1js/pull/1629), it works!


[PE-D][Tester C] "Addmempts" command has a different error message than the expected one

Steps to reproduce:

Run the following command: addmempts n/Irfan Ibrahim mp/999999999999999999999999999999999999999999

Expected behaviour: that the program should inform me that the mp/ parameter value is too large.
Actual behaviour: as shown in the screenshot below. It says that input must be a valid integer although "999999999999999999999999999999999999999999" is technically a positive integer.

My suggestion: the error for this can be changed to state that the expected maximum value is Java's definition of INT_MAX, or something along those lines.

Labels: severity.Low type.FeatureFlaw
original: kailashgautham/ped#8

REPEATED


Visual Studio 2019 crashes if opening settings

TLDR:
VS crashes if trying to open Settings
Long Story
same ;)
Versions:
MS Visual Studio Community 2019 - Version 16.5.5 (with .NET Framework Version 4.8.03752) (update of 12.05.2020)
Clang Power Tools 5.9.0
More information
first time install of Clang Power Tools
Screenshot

Tested Projects
https://github.com/yuzu-emu/yuzu
https://github.com/yuzu-emu/yuzu-canary
(https://github.com/yuzu-emu/yuzu/wiki/Building-for-Windows used Method 1)
Extension
other Parts arent working too
--- CLANG TIDY STARTED ---

PROJECT: E:\dev\workspace\repos\yuzu-canary\binory\src\yuzu\yuzu.vcxproj
46: E:\dev\workspace\repos\yuzu-canary\src\yuzu\configuration\configure_audio.cpp
clang-tidy.exe: Unknown command line argument '-quiet'.  Try: 'clang-tidy.exe -help'
clang-tidy.exe: Did you mean '-fix'?

46: E:\dev\workspace\repos\yuzu-canary\src\yuzu\configuration\configure_audio.cpp

--- CLANG TIDY FINISHED ---

Extension 2
possible Duplicate of #804

Hello @Sickeroni,
Thank you for taking the time to write your issue in such a detailed manner.
Clang Power Tools 5.9.1 was just released and it includes the fix for the crash when first opening Settings on a CMake project.
Regarding the issue with Tidy, we are still investigating but we were not able to reproduce it yet. We will update #804 on this matter.

still crashes with Clang Power Tools 5.9.1
deinstall and new installing didn't worked either.

Could you try to delete Settings.json manually from %appdata%\ClangPowerTools? Let me know if the issue persists.

okay strange behaviour
step 1
removed settings -> not crashing anymore, but still no settingswindow
step 2
reinstalled -> same behaviour
step 3
deactivated resharper (installed yesterday after 5.9.1 update)
-> now it crashes again

So after some fiddling around I made the Nintendo Switch emulator project work. Settings seem to work fine.
I had a couple of crashes when working with just the CMake project and Reshaper installed, without Clang Power Tools. Except for this everything seems OK.
You cannot open Settings from both Toolbar and the context menu? Did you try a different project?

I have the same issue with 7.0.1, I cannot access the settings at all.

This issue should be fixed in v7.1 (latest version). Please check for updates.
@netx123 Can you check if the problem is persisting on your machine?

@Enache-Ionut I've check 7.1 and it's resolved the issue for me.

Thank you for the quick testing. I'm glad to hear that.
I will close this issue for now. If the problem appears again, we'll reopen this thread.


System.OutOfMemoryException when trying to build & publish app

Describe the bug
We're in the process with the whole development team to split up our solution into multiple apps, but things are going really slowly because of this error occuring time and time again.
When trying to build & publish our app for the second time during a VS Code session (because of ongoing development) a System.OutOfMemoryException occurs
To Reproduce
Steps and to reproduce the behavior:

Open VS Code
Open a workspace with the app (in our case +/- 4300 source files)
Press F5 to build & publish
Check some functionality
Back to VS Code and stop debugger
Make some changes to the code
Press F5 again to build & publish
Error occurs

Update: This only occurs if the "features" property in the app.json file is set to "TranslationFile"
But of course this is only a workaround
Expected behavior
Even after disabling a lot of VS extensions en changing settings in VS Code to boost performance, it presents this issue.
We need to be able to trust AL en VS Code to work smooth and properly without out-of-memory exceptions.
Screenshots

5. Versions:

AL Language: 5.0.280447

Business Central: 16.0.13440.13772 (OnPrem)

Hi @ptijsma, thank you for reporting the issue. Could you please provide a project which demonstrates the issue, may be it is possible to localize the problem. It would significantly help us to reproduce the issue. What kind of changes do you make at i.6, does the translation file has any changes between ii.3 and 7? Thank you.

Hi @AndreyKorepanov,
Provide a project.. Ehhm.. I could provide you our App in a private message somehow, however, it's in total 249 MB and contains 4452 files.
Regarding the translation files:
We have these translation files in the directory:

The BaseApp.g.xlf would normally be bigger, but beacuse the property "TranslationFile" has been disabled, this isn't rebuild currently
re/ Changes at i.6: Can be any change as simple as adding a MESSAGE somewhere. Nothing fancy
re/ Translation file changes: We haven't made any changes to the en, nl, de translation files between i.3 and i.7. The only change (When the property "TranslationFile" has been enabled) is that the BaseApp.g.xlf is being rebuild on F5.
To my understanding it's exactly the rebuild of BaseApp.g.xlf that causes the crash.
Hope this helps,
Thanks,
Peter

Hi @ptijsma, thank you for reply. I'll try to get a repro on the Base app, In my case Base app translation file is around 50K.

Hi @AndreyKorepanov ,
Just to be sure: BaseApp in our case, is our BaseApp which has of course a dependancy on the Microsoft BaseApp.

Hi @AndreyKorepanov ,
Just another screen shot with a different Out of memory exception. Same app. Not sure if this helps though.

Hi @AndreyKorepanov,
Just found out one more thing.
Seems our generated Xlf files are also kind of corrupted... It seems there are quite some entries with duplicate id's:

I'm guessing this could also be some kind of reason for out of memory exceptions..

Hi @ptijsma, it seems the former is related to the #5866. Thanks.

@atoader @AndreyKorepanov
Do we have any resolution for this issue??

Use 64 bit compiler.
It will be much faster and does not give out of memory exceptions

This error usually comes while building large applications/extensions.
When the memory used for this process exceeds 4GB it throws out of memory.

@suryanshsangwan
Is there a 64 bit compiler for AL available? If so, where would i find it?

@iTomate AL vscode extension is the compiler. When you extract it, you will find a win32 folder that contains the 64bit compiler and its dependencies.

We ran into simular problems when changing the BC18 baseapp. We are unable to compile the app: System.OutOfMemoryException
When deleting the xlf files from the Translations folder, compilation finishes succesfully.

Use this path

Thats seems to be working quite well! Thanks a lot Suryansh

The 64 bit executable is shipped nowadays, so I'll close this


SQL Import append data option

The flat file data import wizard follows the functionality in SSMS in that you can only import data into a new table.
It would be really useful to have the option to spend data to an existing table as well.

This should be a really high priority. Even more so than the already prioritized Excel Import feature (though both would be ideal). As it is, this is the ONLY thing that I have to keep jumping back to SSMS for. Azure Data Studio has it beat in every other regard for what I need to do.


Fix get_mac_address_table XML issue

Refer to issue #17: get_mac_address_table method: Response from the device is not in expected format

Thanks for the PR @lboue


Can't input double quotes (< " > character) on Mac OS X with US International keyboard layout

Operating system or device:
MacOS X Mavericks
Issue description (what happened, and what was expected):
Can't use simple or double quotes inside the godot script editor using US-International keyboard layout.
Steps to reproduce:

Open any godot version since 2.0 stable
Attach a Panel to you Scene
Create a Script attached to the given panel
Try to use quotes and double-quotes

Link to minimal example project (optional but very welcome):
You can use my project as example:
https://github.com/emanuelcds/SlotMockRuntime
(I need to edit the gdscript files on VIM to edit the game logic and resync it on the engine).

OSX 10.11.6
Godot_v<IP_ADDRESS>_stable_osx
Unfortunately, the issue still here, any update about ? @akien-mga

No idea, we'd need someone who can reproduce it to debug the issue and try to fix it. AFAIK, it only affects certain users, as we have many OSX users who never complained about it.
I guess the common denominator is that you're all using the "US international" keyboard layout?

Yeah, definitely the common denominator is the "US international", I bet that is the main symptom

Confirmed, the quotes and double quotes works correctly when the OSX is using "US" keyboard, but fail if the user set "US International" keyboard

if you press double quote and then space, does it work?
On Wed, Jul 27, 2016 at 5:48 PM, Eduardo Nunes Pereira <
<EMAIL_ADDRESS>wrote:

Confirmed, the quotes and double quotes works correctly when the OSX is
using "US" keyboard, but fail if the user set "US International" keyboard
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/issues/4403#issuecomment-235715801,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF-Z21aJ_EgsQKUoYljGn8tPqo2yTkvcks5qZ8QBgaJpZM4IN5Gv
.

@reduz, doesn't work either, my keyboard is a "US International" due the PT-br idiom. When I press the double quote and then space nothing happens, it just considers as a simple space and ignores the  double quote as if haven't pressed

I think this is the same as #1490, a general problem with dead keys.

Same error here!
I can't write something like this: is_action_pressed("left")

This needs an OSX developer to dive into the input code.

I'm having this same problem here: When i use "US International" mode on my keyboard i can't type quotes neither other characters in the Godot Editor - but when i change the keyboard mode all seems to be working fine.

The problem doesn't only affects the double quote, but any character that "waits" (a.k.a. dead keys) for the next input in the International Keyboard. For example, when I press the " key and follow it by a vowel like a, it produces ä instead of "a. Likewise, the characters ``` ~ ^ ' also "wait" for the next input key so they can determine which character will be inputted, be the regular character, be a modified character like ç, or ê or ñ.
My system settings:
ProductName:	Mac OS X
ProductVersion:	10.12.4
BuildVersion:	16E195
$ printenv

TERM_PROGRAM=Apple_Terminal
SHELL=/bin/bash
TERM=xterm-256color
LANG=pt_BR.UTF-8
XPC_FLAGS=0x0
XPC_SERVICE_NAME=0
SHLVL=1

As you can see, I'm using the UTF-8 version of the pt_BR locale, with the Brazilian Keyboard Pro.

The bug can be avoided temporarily by selecting the US keyboard on the System Preferences -> Keyboard -> Layout

@BastiaanOlij want to give this one a try?

CC also @bruvzg and @marcelofg55 :)

I'm searching this 'quetos' isse about last 4 hours. Thanks to "eduardonunesp" i handled it. Changing 'US Internatiol' Keyboard to 'US' Keyboard worked for me.

I changed to keyboard "US" from "US International" and it works

It seems this is not solved? I'm having the same problem with Godot 4.2.1 on Pop!_OS.
I am also using US - International keyboard layout.

I'm also getting this bug, when using dead keys on US-International Layout on Fedora 40, I can't type quotes, double quotes or other types of dead-keys characters.
Changing to another layout fixes some characters, but then I can't type the new layout dead keys
Desktop: Gnome with Xorg on Fedora Workstation 40
Godot Version: v4.2.2.stable.official [15073afe3]


Update Make commands for Mac

Use gsed if Mac is detected
Consistently use GOOS and GOARCH for installing binaries
Use binaries installed in LOCAL_BIN -- don't rely on the local version
Add clean Make target to remove stale binaries

I have been attaching two quotes after sed. And when it is time to commit I removed it lol. This is amazing for me. Thanks Dale

@mprahl There are some non-Mac-specific things in here if you could also review it when you have a moment.


Add additional text options and pcbStand pin options

Add four additional text options (to match what's available in OpenSCAD.
//   p(9) = Direction : { <yappTextLeftToRight>, yappTextRightToLeft, yappTextTopToBottom, yappTextBottomToTop }
//   p(10) = Horizontal alignment : { <yappTextHAlignLeft>, yappTextHAlignCenter, yappTextHAlignRight }
//   p(11) = Vertical alignment : {  yappTextVAlignTop, yappTextVAlignCenter, yappTextVAlignBaseLine, <yappTextVAlignBottom> }
//   p(12) = Character Spacing : Default = 1

With examples in WaterHeaterMonitor_v3.scad.

Add Custom pin length option to pcbStand
Add yappTopPin option (in addition to , yappHole)
Removed the forced color on the Hooks

Dear @rosenhauer,
Given the amount of new functionality and options I’m loosing track of the possibilities (also due to limited time on my side).
Would you mind editing / appending the “Official Documentation” in gitbook?
If so I thing you have to create an account on gitbook and give me your account name (I think) so I can add you as a collaborator.

I signed up for a Personal account. Same username as GitHub.

I made a few changes and sent them for your review, Just to check out the
process.
I can work my way through the entire document making sure that all of the
changes/additions are documented.
Do you like the idea of adding subpages for the optional parameters to keep
the main pages cleaner?
On Tue, Jan 30, 2024 at 12:04 PM mrWheel @.***> wrote:

Ok, if I understand it right you can follow this link
https://app.gitbook.com/invite/-M0s3OOkvpRGMMljA00t/-M0s3PkDnxkFYcwjURMJ
—
Reply to this email directly, view it on GitHub
https://github.com/mrWheel/YAPP_Box/pull/62#issuecomment-1917605839, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AIBTUKHMRXZZ6TFWJAB25S3YREY2DAVCNFSM6AAAAABCK724DGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMJXGYYDKOBTHE
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Dave

I will look at the changes you made.
Subpages for optional parameters is a great idea.
If you get to it, for parameters with a default value: please show them as first parameter in the list:
parm = {<rectangle> | circle | something_else }

Where rectangle is the default value

@rosenhauer,
Well , I see you did some additions to the documentation.
But every time I now open gitbook in [edit] mode I see different things (?). An error that syncing did not go well. Also a lot of changes I made months ago that have to be merged .. but then I get conflicts so I archived those changes.
I will, for the time being not enter gitbook in [edit] mode, just to make sure I won’t destroy your work!
So, please merge your changes yourself. I have confidence your English is far better than mine!


Label selector & Field selector syntax evaluation

Would you like to work on this feature?
Sure!
What problem are you trying to solve?
Let's say I have an application using Api<K>::list with some ListParams { label_selector: Some(_), field_selector: Some(_), _} to filter results. If I then want to maintain a cache runtime::reflector::Store<K> and call Store<K>::state, I'd like to be able to filter the Vec<Arc<K>> based on ListParams.
For example: if I have a Store<Pod> of all pods all namespaces, I'd like to lookup store.state() with multiple different label_selector expressions, without having to keep multiple Store<Pod>s around.
Describe the solution you'd like
I'd like to evaluate selector syntax and filter a Vec<AsRef<K>> based on some ListParams. I'm not sure if this is planned or within the scope of this crate.
Describe alternatives you've considered
Alternate solutions require more restrictive API designs when using Store<K> on applications with dynamic-list requirements.
Documentation, Adoption, Migration Strategy
No response
Target crate for feature
kube-core

oh, that is interesting, basically runtime simulation of what the apiserver does with ListParams
I think this type of thing can probably be added direct as pub impls on Store now that we are using a less difficult datastore (AHashMap rather than the lockfree one) and I have also wanted some extra convenience helpers there so +1 for something like this.
Not sure I would want it to take the whole of ListParams as an input though, since most params there don't make sense for local filtering (like timeouts, bookmarks and continue tokens), but label filtration makes sense. Maybe it would make sense to do some more general filter lambdas like AsRef<K> -> bool since they should be able to be inlined rather easily?


Disk removing not working for UNDEPLOED VMs

Description
If VM have UNDEPLOYED state and you call remove it. VM drives won't be removed, from the storage.
To Reproduce

Create VM
Undeploy VM
Remove VM
Check system datastore (drive will not be removed)

Expected behavior
Removed VM and all its resources.
Details

Affected Component: Core / Storage drivers
Hypervisor: KVM
Version: <5.6

Additional context
Add any other context about the problem here.

Progress Status

[ ] Branch created
[ ] Code committed to development branch
[ ] Testing - QA
[ ] Documentation
[ ] Release notes - resolved issues, compatibility, known issues
[ ] Code committed to upstream release/hotfix branches
[ ] Documentation committed to upstream release/hotfix branches

Hmm, it seems problem was solved by itself.
I have all needed API calls during deletion, but now I have another one: https://github.com/OpenNebula/one/issues/2981


applet.video.ws2818_output: add support for LEDs other than RGB

This sits on top of #224, and adds the ability to give other pixel formats.
I've backed down from the more complex options, and have opted for a simple lambda function that constructs the final pixel shape, paired with -f, e.g:

-f RGB-BRG
-f RGB-xBRG - for use with RGBW LEDs, with the White blanked to zero
-f RGBW-WBRG

pixel_formats = {
    # in-out      in size  out size  format_func
    'RGB-BRG':   (   3,        3,    lambda r,g,b:   Cat(b,r,g)   ),
    'RGB-xBRG':  (   3,        4,    lambda r,g,b:   Cat(Const(0, unsigned(8)),b,r,g) ),
    'RGBW-WBRG': (   4,        4,    lambda r,g,b,w: Cat(w,b,r,g) ),
}

p = self.pix_format_func(*pix, self.out_fifo.r_data)
m.d.sync += word.eq(Cat(word[pix_out_bpp:], p))

Using a string of LEDs to do light painting can be accomplished using the script below.
Configure and tweak accordingly, but this will take care of resizing the image to fit your LED string, starting glasgow, displaying each line, one by one, and then blanking the chain.
img_src="gir_dog_suit.png"
img_tmp="${img_src%.*}_resized.${img_src##*.}"
img_fmt="rgba"

led_num=15
led_fmt="RGBx"

socket="leds.sock"

# resize the image, and get its resulting height
convert "${img_src}" -resize "${led_num}x" "${img_tmp}"
read img_h < <( identify -format '%h' "${img_tmp}" )

# start glasgow, with a single buffer, and the correct number of LEDs and LED format
glasgow run video-ws2812-output -c "${led_num}" -f "${led_fmt}" -b 1 -V 5 --pins-out 0 "unix:${socket}" &
glasgow_pid="$!"

# wait for glasgow to build the applet and startup
sleep 5

# paint each line, one by one, with a 50ms delay... finish by blanking the LEDs
nc -NU "${socket}" < <(
    for i in $(seq $(( ${img_h} - 1))); do
        convert "${img_tmp}" \
            -brightness-contrast -60x-30 \
            -crop x1+0+$i rgba:-
        sleep 0.05
    done
    dd if=/dev/zero bs=4 count="${led_num}" status=none
)

# tidy up
kill "${glasgow_pid}"
wait

@attie Should I make you the code owner for this applet?

Should I make you the code owner for this applet?

Happy to / I did it.

Again, merge after #357

Can you rebase this?

Done

Hm. I still see commits from the other branch here?

Wierd... me too.
... but the history for 7ecd372 goes via ef17f63 which is merged into main.
... is GitHub being slow?

I'm nervous that GitHub is going to try and merge f4607bd, not 7ecd372... also, I expect it to fail to merge when combined with #246


Support DISA STIG Viewer Results Import

By trial and error, I've discovered that this is the minimal XML that the STIG viewer will accept for results import, including "pass", "fail", and (the useless) "notchecked"
<?xml version="1.0" encoding="UTF-8"?>
<TestResult>
  <rule-result idref="SV-86681r2_rule">
    <result>pass</result>
  </rule-result>
  <rule-result idref="SV-86921r3_rule">
    <result>notchecked</result>
  </rule-result>
  <rule-result idref="SV-86473r3_rule">
    <result>notapplicable</result>
  </rule-result>
  <rule-result idref="SV-86853r3_rule">
    <result>fail</result>
  </rule-result>
</TestResult>

Given the simplicity of this format, it should be feasible to output "XCCDF Results" that can be imported into the STIG Viewer.  The ComplianceAsCode/content (aka ssg) project has a tool to automatically generate the STIG-ID to Rule-ID mapping, but it'd need to be adapted to our use case.  Ideally, this mapping should be kept in an automatically-generated vars file.
When instrumenting this extra output, I'd want to start with:

Items that both DISA and SSG don't check (currently 22 items)
Items where SSG gets a false positive and our role is compliant (currently 3 items: 010320, 030840, 040810)

Edit: more helpfully, notapplicable is supported as well.

I like the idea as we discussed in IRC. I definitely think there would be some use to it.

Agreed this would be valuable to output XCCDF files with our use cases.

Hello,
I wanted to reach out and let you know that this issue is being closed. We have re-worked the role and want to start with a fresh issues list with this latest version. There was a post in the Ansible-Lockdown google group (https://groups.google.com/g/ansible-lockdown) with the details of the changes that are coming. Please checkout the thread titled RHEL 7 CIS and STIG Changes for all of the details, I also have the message pasted at below.
Please as you use the latest version and open issue tickets as you find them, it is the best way for us to improve the role for everyone. Thank you for being part of the community and providing awareness of problems or advice on improvement. Reporting is a huge part of improving this project.

Hello,
Thank you to everyone in the Ansible-Lockdown community who has contributed to RHEL7 STIG/CIS. Our team at MindPoint Group has been working with the entirety of the Ansible-Lockdown project, and we have some significant updates for both RHEL 7 STIG and CIS. With these updates, some larger changes have been made. I have these changes/updates outlined below.
Testing:

CI/CD - We have implemented some automated testing pipelines to test pull requests into the devel and main branches. With the current workflow, the community will PR into the devel branch (never the main branch) for review by the administrators. When your PR is created, the first check will remain the DCO check. The second check is a functional testing pipeline that will automatically perform a functional test of the branch the PR is initiated from. Once both tests pass, someone from the Administrator Team will review the changes and merge them into the devel branch. From there, an additional review is completed before the devel branch is merged into the main branch. Only the Admin Team will perform PRs/merges into the main branch. There is also an automated pipeline for PRs from devel to main. Please do not edit the .github/workflows files since those are used as part of the pipeline.
Compliance Checking – MindPoint Group has been working to create our own compliance audit scan tool. The tool uses a goss framework executable to run custom checks that we have created. The goal is to provide a more thorough check for control compliance and decrease the number of false positives/negatives. For example, it will check the configuration file related to the control and as well as checking if that configuration is active. With a smarter scan, we can hopefully identify attempts to trick scanners as well (for example stacking a parameter in a config file where the first instance is enabled and second disabled. Most audit tools search for the first instance but the application might look for the last instance of the parameter, thus making the scanning tool think it's enabled). In testing, we have found that our audit scan runs significantly faster than other audit tools, reducing audit times. Our audit tool and profiles will have their own repositories in the Ansible-Lockdown org, but within the remediation role there will be an integrated way to incorporate the audit. Keep an eye out for the audit tools as they are released. We plan on developing a goss audit profile for each current remediation role. Going forward, we plan to release a remediation role and goss audit tool profile simultaneously.
Role Updates:
RHEL 7 STIG/CIS – We have re-written much of the RHEL 7 STIG and CIS roles to increase clarity and readability and address some functionality items. We performed these updates while creating our goss testing framework for each of these roles. We plan on pushing our update to the devel and main branches. We will move the current devel and master branches to a devel_stable_ and master_stable_ branch in the respective repositories. Accordingly, community members who rely on the current version can still use that version going forward; this process will not remove what is currently there. The latest versions of the roles have also been updated to comply with the latest benchmarks.
Role Architecture – All roles will change with regard to the structure in the tasks folder. Taking CIS as an example, there will be a folder per section and yaml files for each sub-section. For example control 1.2.1 in CIS will be located in RHEL7-CIS/tasks/section_1/cis_1.2.x.yml. The cis_1.2.x.yml file will contain all controls related to section 1.2.x. This will hopefully make updates to roles a bit easier with less risk. This matches the architecture of our audit tool, creating consistency across remediation and audit platforms. The end goal is to repeat this architecture (the best we can) on STIG roles, but we are starting with CIS.
Existing PRs and Issues – With all of these changes comes the task of cleaning up existing PR’s and issues. Our plan is to close all of the existing PR’s and issues because of the re-work. Our team is growing and should be able to stay on top of the new issues and PRs as they come in.
Again, I would like to thank the community for your involvement in this project. The input and work from the community has contributed significantly to the success of this project. Please keep an eye out for these changes, which will be rolling out in the coming weeks.


Page index gets set to -1 with manual pagination and zero pages

Describe the bug
When using manual pagination, if we have zero pages of results, any attempt to set the pageIndex gives a pageIndex of -1 (which would often be invalid as an API parameter).

autoResetPageIndex doesn't work with manual pagination, because it resets to page zero whenever the data changes, which it inherently will do with manual pagination
As a workaround (or legitimate functionality, if the page count is likely to reduce while paging through), we have/had an implementation to reset the page index if it got "out of bounds". This was trying to set pageIndex to 0 or pageCount - 1 (or the greater of the two), but if pageCount = 0, react-table would "clamp" it to -1 anyway.
Better functionality is for the page index to reset to 0 when changing the filter/sort order, but I still think that setting pageIndex of -1 is incorrect
Another workaround is when passing the pageIndex parameter to the API to make sure it is "reasonable", but I don't think react-table should be setting an unreasonable value in the first place
Another workaround would be to say that we should never have zero pages, we should always have at least 1, even if it's empty. But that doesn't necessarily seem right either.

https://github.com/TanStack/table/blob/main/packages/table-core/src/features/Pagination.ts#L123-L139 is the relevant bit - the way that the clamp works assumes that pageCount - 1 > 0, but it isn't necessarily.
Your minimal, reproducible example
https://codesandbox.io/s/confident-roman-iwj4le?file=/src/main.tsx
Steps to reproduce

Go next page
Type "no_results" into the search box
See that pageIndex gets set to -1, and the fake fetchData API errors because of it

Expected behavior
react-table shouldn't set pageIndex to -1 - it should not set it to < 0
How often does this bug happen?
Every time
Screenshots or Videos
No response
Platform
macOS, chrome 102
react-table version
8.5.6
TypeScript version
4.5.5
Additional context
I think the workarounds are reasonable and probably give a better UX, but I still think that the clamp behaviour is wrong because it shouldn't be possible to get to pageIndex -1
Terms & Code of Conduct

[X] I agree to follow this project's Code of Conduct
[X] I understand that if my bug cannot be reliable reproduced in a debuggable environment, it will probably not be fixed and this issue may even be closed.

Our problem is that we persist the pageIndex in the URL, and for some reason when navigating away and coming back to the page, while loading the data from cache and network, react-table freaks out and sets the pageIndex to -1. Our workaround was something extremely hacky and potentially bug prone (although it seems to work):
While manually handling the state updates, ensure pageIndex is never set to -1, and maintain the previous state pageIndex:
table.setOptions((prev) => ({
    ...prev,
    state,
    onStateChange: (updater) => {
      if (typeof updater === 'function') {
        const newState = updater(state);
        setState({
          ...newState,
          pagination: {
            ...newState.pagination,
            pageIndex:
              newState.pagination.pageIndex === -1
                ? state.pagination.pageIndex
                : newState.pagination.pageIndex,
          },
        });
      }
    }
})

Weird but it solves our particular niche case.


Add scaler metric latency support

Add scaler metric latency support
Checklist

~[ ] When introducing a new scaler, I agree with the scaling governance policy~
[x] I have verified that my change is according to the deprecations & breaking changes policy
[ ] Tests have been added
[ ] Changelog has been updated and is aligned with our changelog requirements
~[ ] A PR is opened to update our Helm chart (repo) (if applicable, ie. when deployment manifests are modified)~
[ ] A PR is opened to update the documentation on (repo) (if applicable)
[x] Commits are signed with Developer Certificate of Origin (DCO - learn more)

Relates to #4037

Can you also please update our documentation please?

Added e2e test and updated CHANGELOG, will update doc as well

Doc updated, https://github.com/kedacore/keda-docs/pull/1034

/run-e2e prometheus_metrics*


Merge latest master from upstream

@gilessbrown Thanks!

You’re welcome!
From: Philippe Ombredanne<EMAIL_ADDRESS>Reply-To: pombredanne/wextracto<EMAIL_ADDRESS>Date: Saturday, April 29, 2017 at 12:18 AM
To: pombredanne/wextracto<EMAIL_ADDRESS>Cc<EMAIL_ADDRESS><EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [pombredanne/wextracto] Merge latest master from upstream (#2)
@gilessbrownhttps://github.com/gilessbrown Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/pombredanne/wextracto/pull/2#issuecomment-298152589, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AIpC-eaJWwk6iShMAUEQea9Tj7hre3iAks5r0uQ-gaJpZM4NMLOj.


Support Kaltura's HTML5 player (v2)

This pull adds support for Kaltura player embeds (using an iframe tag).
Thanks in advance for your consideration,

Hi @cookpete,
First of all, a very useful project, well done:)
Would you please review this pull request? It basically follows the same implementation as Streamable, using the Embed.ly playerjs lib.
Thanks,

Hi @jessp01, sorry for how long it has taken to get back to you on this.
I'm running it locally and not much is working. Pause doesn't work, seeking doesn't work, volume change only works when you set it to 0, and none of the callback props are called (onPlay, onPause, etc).
The player API docs also don’t mention anything about supporting player.js: http://player.kaltura.com/docs/api

Hi @jessp01, sorry for how long it has taken to get back to you on this.
I'm running it locally and not much is working. Pause doesn't work, seeking doesn't work, volume change only works when you set it to 0, and none of the callback props are called (onPlay, onPause, etc).
The player API docs also don’t mention anything about supporting player.js: http://player.kaltura.com/docs/api

Hi @cookpete,
Thanks for getting back to me. When you say you're running it locally, do you mean with the demo app (src/demo/App.js)?
It worked okay when I tested but I will check again. Also could you please let me know which API ops you consider mandatory, or, in other words: must be implemented before the pull can be merged?
As for the documentation, indeed, it is lacking in that sense. The Kaltura player supports multiple embed methods and has its own API but when embedding in an iframe (which seems to be the preferred method for react-player, quite sensibly), using Embed.ly's player.js is the only way.
Thanks again,

Hi @cookpete,
Thanks for getting back to me. When you say you're running it locally, do you mean with the demo app (src/demo/App.js)?
It worked okay when I tested but I will check again. Also could you please let me know which API ops you consider mandatory, or, in other words: must be implemented before the pull can be merged?
As for the documentation, indeed, it is lacking in that sense. The Kaltura player supports multiple embed methods and has its own API but when embedding in an iframe (which seems to be the preferred method for react-player, quite sensibly), using Embed.ly's player.js is the only way.
Thanks again,

Hi @cookpete ,
All basic APIs work now (tested using the demo app). If you feel it's important, I can implement the speed increase actions as well.
Let me know if this can be merged?
Cheers,

Hi @cookpete ,
All basic APIs work now (tested using the demo app). If you feel it's important, I can implement the speed increase actions as well.
Let me know if this can be merged?
Cheers,

I think something must be broken with their player API? Things still aren't working for me.
Even the most basic interactive embed code (copied directly from their docs) doesn’t seem to work:
http://player.kaltura.com/modules/PlayersJsReceiver/tests/PlayersJsReceiver.qunit.html
	var player = new playerjs.Player( document.getElementById('kaltura_player') );
	//listen to play start
	player.on(playerjs.Events.PLAY, function() {
	  // This is never called :(
		console.log('play');
	});

Live example: https://jsfiddle.net/zes7n2pw/

I think something must be broken with their player API? Things still aren't working for me.
Even the most basic interactive embed code (copied directly from their docs) doesn’t seem to work:
http://player.kaltura.com/modules/PlayersJsReceiver/tests/PlayersJsReceiver.qunit.html
	var player = new playerjs.Player( document.getElementById('kaltura_player') );
	//listen to play start
	player.on(playerjs.Events.PLAY, function() {
	  // This is never called :(
		console.log('play');
	});

Live example: https://jsfiddle.net/zes7n2pw/

There’s also this page that has a script tag that doesn't work:
https://developer.kaltura.com/player/web/getting-started-web
  <script type="text/javascript" src="https://cdnapisec.kaltura.com/p/000000/embedPlaykitJs/uiconf_id/22222222"></script>

I get a 404 when I try the example as well as replace the conf_id and partner id with the ones from your sample URL:

There’s also this page that has a script tag that doesn't work:
https://developer.kaltura.com/player/web/getting-started-web
  <script type="text/javascript" src="https://cdnapisec.kaltura.com/p/000000/embedPlaykitJs/uiconf_id/22222222"></script>

I get a 404 when I try the example as well as replace the conf_id and partner id with the ones from your sample URL:

Hi @cookpete ,
Yes, I am aware of the fact that this demo (http://player.kaltura.com/modules/PlayersJsReceiver/tests/PlayersJsReceiver.qunit.html) does not work. I will try to get that fixed (not under my direct remit but I'll speak to the relevant people).
But does the demo app not work for you following my last commit? It does for me.
Also, here's a standalone demo that works as well:
https://demo.kaltura.me/player.js.demo.html
The documentation you referenced (https://developer.kaltura.com/player/web/getting-started-web) pertains to Kaltura's player v7 (aka playKit). That's a completely different codebase I'm afraid (I agree it is confusing). I'll submit a pull to support that a bit later in the game, when it's a bit more mature.

Hi @cookpete ,
Yes, I am aware of the fact that this demo (http://player.kaltura.com/modules/PlayersJsReceiver/tests/PlayersJsReceiver.qunit.html) does not work. I will try to get that fixed (not under my direct remit but I'll speak to the relevant people).
But does the demo app not work for you following my last commit? It does for me.
Also, here's a standalone demo that works as well:
https://demo.kaltura.me/player.js.demo.html
The documentation you referenced (https://developer.kaltura.com/player/web/getting-started-web) pertains to Kaltura's player v7 (aka playKit). That's a completely different codebase I'm afraid (I agree it is confusing). I'll submit a pull to support that a bit later in the game, when it's a bit more mature.

Added some tweaks and fixes, mainly around the onReady and event binding logic. Hopefully all good now. Thanks for the help @jessp01 👍

Hi @cookpete,
Excellent. Thanks again for your time :)

@cookpete - would it be possible for you to create a new release version?
Thanks,

Would like to get some other stuff in first. Will publish soon 👍

Cheers, @cookpete. Much appreciated.


How to Assign Labels to Connections in DrawFlow Condition Node?

I'm currently working with DrawFlow and I have a requirement to assign labels to connections in the condition node. The condition node has a rhombus shape and consists of one input and two outputs.

I would like to know how I can achieve the following behaviour:
When a connection is dragged from the right end of the condition node, I want to set the label of the connection to "true".
When a connection is dragged from the bottom of the condition node, I want to set the label of the connection to "false".
I would appreciate any guidance, code examples, or suggestions on how to implement this functionality in DrawFlow.
Please feel free to share your insights or point me in the right direction. Thank you in advance for your help!

View:

https://github.com/jerosoler/Drawflow/issues/18

Thank,
But how to identify the link coming form true output or false output in exported json

In the export with output_1 and output_2

Can you please provide with the code.
this.editor.createCurvature = function (start_x, start_y, end_x, end_y, curvature_value, type) {
....
}
Iam using this function to create curvatures, but now i want to pass the nodeid and outpuId (from which output the connection is creating) based on these values, i will put conditions inside above function and generate links respectively.

CreateCurvature function not get the nodeId.
But use events with connection created:
editor.on('connectionCreated', (obj) => {
 console.log(obj)
});

Is it possible to redraw the curvature of the connection within the 'connectionCreated' event handler? I would like to customize the curvature based on the newly created connection, its source node, and the output it is coming from.
Specifically, I'd like to adjust the curvature based on different conditions depending on the source node and the specific output that was used to create the connection.
Please help me.

You could modify the creacteCurvature function in the code.
You could modify drawflow to pass it more values.
Here, for example, there is a PR to add the input and output addresses of a node.
https://github.com/jerosoler/Drawflow/pull/32

I replaced the code mentioned there in drawflow.min.js, in angular
But not working, is there any other fix for adding the input and output addresses of a node.

I checked with that code but it is giving only the in_dir only and giving unknown for value out_dir
this.editor.createCurvature = function (start_x, start_y, end_x, end_y, curvature_value, type, out_dir = 'unknown', in_dir = 'unknown')

For the bottom node the curvature is not rendering correctly.
Please help me with this

Hi @jerosoler, Can you please help me with it

out_dir and in_dir is not drawflow is the fork drawflow. I can't help you. From what I see in the PR, it has to indicate if it is top or bottom in the curve.


undefined method `locations'

Summary
Running cucumber-ruby 4.0.0rc.3 the following error is raised
undefined method `locations' for #<Cucumber::Messages::Pickle::PickleStep:0x00007fb6a98c3ea0> (NoMethodError)
/Users/USERNAME/.rvm/gems/ruby-2.6.3/gems/cucumber-core-5.0.2/lib/cucumber/core/compiler.rb:42:in `method_missing'
/Users/USERNAME/.rvm/gems/ruby-2.6.3/gems/cucumber-core-5.0.2/lib/cucumber/core/compiler.rb:42:in `create_test_step'
/Users/USERNAME/.rvm/gems/ruby-2.6.3/gems/cucumber-core-5.0.2/lib/cucumber/core/compiler.rb:35:in `block in create_test_case'
/Users/USERNAME/.rvm/gems/ruby-2.6.3/gems/cucumber-core-5.0.2/lib/cucumber/core/compiler.rb:35:in `each'
/Users/USERNAME/.rvm/gems/ruby-2.6.3/gems/cucumber-core-5.0.2/lib/cucumber/core/compiler.rb:35:in `collect'
/Users/USERNAME/.rvm/gems/ruby-2.6.3/gems/cucumber-core-5.0.2/lib/cucumber/core/compiler.rb:35:in `create_test_case'
/Users/USERNAME/.rvm/gems/ruby-2.6.3/gems/cucumber-core-5.0.2/lib/cucumber/core/compiler.rb:22:in `pickle'
/Users/USERNAME/.rvm/gems/ruby-2.6.3/gems/cucumber-core-5.0.2/lib/cucumber/core/gherkin/parser.rb:24:in `block in document'
/Users/USERNAME/.rvm/gems/ruby-2.6.3/gems/gherkin-8.2.1/lib/gherkin/stream/parser_message_stream.rb:39:in `yield'
/Users/USERNAME/.rvm/gems/ruby-2.6.3/gems/gherkin-8.2.1/lib/gherkin/stream/parser_message_stream.rb:39:in `block (3 levels) in messages'
/Users/USERNAME/.rvm/gems/ruby-2.6.3/gems/gherkin-8.2.1/lib/gherkin/stream/parser_message_stream.rb:38:in `each'
/Users/USERNAME/.rvm/gems/ruby-2.6.3/gems/gherkin-8.2.1/lib/gherkin/stream/parser_message_stream.rb:38:in `block (2 levels) in messages'
/Users/USERNAME/.rvm/gems/ruby-2.6.3/gems/gherkin-8.2.1/lib/gherkin/stream/parser_message_stream.rb:83:in `yield'
/Users/USERNAME/.rvm/gems/ruby-2.6.3/gems/gherkin-8.2.1/lib/gherkin/stream/parser_message_stream.rb:83:in `block (2 levels) in sources'
/Users/USERNAME/.rvm/gems/ruby-2.6.3/gems/gherkin-8.2.1/lib/gherkin/stream/parser_message_stream.rb:82:in `each'
/Users/USERNAME/.rvm/gems/ruby-2.6.3/gems/gherkin-8.2.1/lib/gherkin/stream/parser_message_stream.rb:82:in `block in sources'
/Users/USERNAME/.rvm/gems/ruby-2.6.3/gems/gherkin-8.2.1/lib/gherkin/stream/parser_message_stream.rb:26:in `each'
/Users/USERNAME/.rvm/gems/ruby-2.6.3/gems/gherkin-8.2.1/lib/gherkin/stream/parser_message_stream.rb:26:in `each'
/Users/USERNAME/.rvm/gems/ruby-2.6.3/gems/gherkin-8.2.1/lib/gherkin/stream/parser_message_stream.rb:26:in `block in messages'
/Users/USERNAME/.rvm/gems/ruby-2.6.3/gems/cucumber-core-5.0.2/lib/cucumber/core/gherkin/parser.rb:20:in `each'
/Users/USERNAME/.rvm/gems/ruby-2.6.3/gems/cucumber-core-5.0.2/lib/cucumber/core/gherkin/parser.rb:20:in `each'
/Users/USERNAME/.rvm/gems/ruby-2.6.3/gems/cucumber-core-5.0.2/lib/cucumber/core/gherkin/parser.rb:20:in `document'
/Users/USERNAME/.rvm/gems/ruby-2.6.3/gems/cucumber-core-5.0.2/lib/cucumber/core.rb:30:in `block in parse'
/Users/USERNAME/.rvm/gems/ruby-2.6.3/gems/cucumber-core-5.0.2/lib/cucumber/core.rb:29:in `each'
/Users/USERNAME/.rvm/gems/ruby-2.6.3/gems/cucumber-core-5.0.2/lib/cucumber/core.rb:29:in `parse'
/Users/USERNAME/.rvm/gems/ruby-2.6.3/gems/cucumber-core-5.0.2/lib/cucumber/core.rb:21:in `compile'
/Users/USERNAME/.rvm/gems/ruby-2.6.3/gems/cucumber-4.0.0.rc.3/lib/cucumber/runtime.rb:73:in `run!'
/Users/USERNAME/.rvm/gems/ruby-2.6.3/gems/cucumber-4.0.0.rc.3/lib/cucumber/cli/main.rb:29:in `execute!'
/Users/USERNAME/.rvm/gems/ruby-2.6.3/gems/cucumber-4.0.0.rc.3/bin/cucumber:9:in `<top (required)>'
/Users/USERNAME/.rvm/gems/ruby-2.6.3/bin/cucumber:23:in `load'
/Users/USERNAME/.rvm/gems/ruby-2.6.3/bin/cucumber:23:in `<main>'
/Users/USERNAME/.rvm/gems/ruby-2.6.3/bin/ruby_executable_hooks:24:in `eval'
/Users/USERNAME/.rvm/gems/ruby-2.6.3/bin/ruby_executable_hooks:24:in `<main>'

Expected Behavior
Cucumber's features are executed correctly.
Current Behavior
Cucumber's features can't be run.
Your Environment

Version used: cucumber 4.0.0.rc.3
Ruby version: 2.6.3
Operating System and version: MacOS Mojave 10.14.6

Running the gem info cucumber
Output is:
*** LOCAL GEMS ***

cucumber (4.0.0.rc.3, 3.1.2)
    Authors: Aslak Hellesøy, Matt Wynne, Steve Tooke
    Homepage: https://cucumber.io/
    License: MIT
    Installed at (4.0.0.rc.3): /Users/USERNAME/.rvm/gems/ruby-2.6.3
                 (3.1.2): /Users/USERNAME/.rvm/gems/ruby-2.6.3

    cucumber-4.0.0.rc.3

Hi and thank you for reporting the bug.
This could be fixed by adding this in your Gemfile:
gem 'gherkin', '~> 8.1',  '= 8.1.1'

The next rc release should come next week and this time I'll make sure we don't get this kind of trouble with a new major release of an underlying library.

This should be fixed by 4.0.0.rc.4. Please do not hesitate to reopen the issue if it's still happening.

Hi and thank you for reporting the bug.
This could be fixed by adding this in your Gemfile:
gem 'gherkin', '~> 8.1',  '= 8.1.1'

The next rc release should come next week and this time I'll make sure we don't get this kind of trouble with a new major release of an underlying library.

Sorry for delayed answer. I confirm it works properly with this fix


Assertion failures missing key information

Assume a simple build method like the following:
Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      color: const Color(0x303030), // this line will fail for non-obvious reasons
      home: Container(/* ... */),
    );
  }

Here's what Flutter gives:

Here's what Flutter_Web gives:

We need an improved message here to avoid friction to users. For some reason, the assert fields aren't getting properly propagated.

This is a DDC issue.
@nshahan - can you file accordingly on DDC?

@nshahan - can we close this now?  Should be fixed on the next roll of Dart into Flutter, right?

It's landed into the SDK, but I don't know when that commit will actually make it into Flutter but users of flutter_web with the bleeding edge SDK could try it out now.


Handle invalid date in Received header

Raise ArgumentError If invalid date in Received header.
On the other hand, nothing raised if invalid date in Date header.
So I think mail library should not raise ArgumentError if invalid date in Received header.
This patch can improve robustness.
I created this patch for 2-5-stable branch but it may be applied for master.
(I have not checked for master yet.)
Thanks!
Related issues: #564, #216

Superseded by #594


Move the notifier bot to independent repository

Close?

Yes, close. https://github.com/grammyjs/website/pull/636


Add AutoFields. Move field-components to their own folder.

Description
Adds an AutoFields component. The idea is to use a hook to get the value of the form. In this way, either explicitly pass in AutoFields as a child of FormContainer, or leave FormContainer empty to get the same result:
<FormContainer onChange={onChange} value={formValues}>
  <AutoFields />
</FormContainer>

is the same as
<FormContainer onChange={onChange} value={formValues} />

One thing to note is how we're inferring the schema. In this first pass it's not ideal in that we infer the schema with in the component function. As a result, we'll infer the types of values each time onChange is fired. One alternative would be to useMemo to get the schema from values, but this could be problematic if we have a dynamic form that adds new values (which should add form fields). The most performant way might be to use a schema if we think we'll be using dynamic forms. Then if we're inferring the schema from values, we can assume the number of fields will always be static.
We'll also need to pass a schema to do some more interesting things with AutoFields such as mixing it with static fields.

@stevelikesmusic I went ahead and merged. In case I conflict in my changes, I didn't want to cause conflicts in your branch.


Pull 811 work

Docs Build status updates of commit 5ecba2e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

azureadps-2.0-preview/AzureAD/New-AzureADMSConditionalAccessPolicy.md
:white_check_mark:Succeeded
View (azureadps-2.0-preview)

azureadps-2.0/AzureAD/New-AzureADMSConditionalAccessPolicy.md
:white_check_mark:Succeeded
View (azureadps-2.0)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

@CelesteDG, this is continuation of the work in PR #811. Please review.


Issues with the Clipboard?

I'm unable to get the Clipboard function to work. Specifically, the y y command to copy current URL. The alternate commands to paste in new window and whatnot seem to work fine.
I'm using the Brave browser, and I did enable access to file extensions.
What am I doing wrong?

This seems to be an issue withe Copy Current URL functionality specifically.  I have the same issue on Firefox that it fails to work most of the time, regardless of the keybinding involved.  Sometimes it works, but usually not.


Enable multi-class classification

This is maybe a change too big and cumbersome to be worth implementing, because it means tensors will be replaced by lists of tensor of different shapes (because each dataset doesn't have the same number of labels, which is precisely the point of using multi-class classification).

I actually think this is worth implementing after my realization that you could do this in a mathematically elegant way by penalizing the squared log normalizer. That said we need to think carefully about how to code it

This was solved months ago


⚠ Caution when using this library: The private keys are incompatible with other ed25519 implementations.

Used this library to sign software for my auto-updater. As long as you use this implementation stand-alone everything seems to be ok. Signing and verification works.
But: The private keys generated with this library are incompatible with other implementations (e.g. libsodium which is used by PHP).
See https://github.com/jedisct1/libsodium/discussions/1213 for more details.

My library is older than libsodium, and predates the RFC by 4 years. I chose this API because it means I don't have to re-hash the seed on every invocation without a further state struct. If you wish to be compatible with libsodium you have to keep the seed around separately. The combination of the seed plus public key is equivalent to the libsodium private key.

As a courtesy against future confusion I added this note to the readme:

Note: this library stores private keys in a different format than some other libraries, notably libsodium. They tend to store the concatenation of the seed and public_key as their private key representation. If you wish to be compatible with these libraries you must keep the seed around.


Cache Rust toolchain in CI

Problem
We currently reinstall the stable and nightly Rust toolchains multiple times in a hardhat-core CI workflow run.
Definition of Done
Cache the Rust toolchain installations (both nightly and stable)  in hardhat-core CI workflow jobs.

Would there be a speed difference between installing it (requiring a download) or retrieving from cache (requiring a download), given that we don't have a dedicated CI machine?

In a project of mine it's 2-3 times faster to install from cache than CI. It's not much in absolute terms, since the install itself is only 10-20 seconds, but it adds up if we install the toolchain in multiple jobs.


(0 , i.__exportStar) is not a function

Followed the installation for the next js, got the error, I followed the tutorial carefully.
to reproduce follow the installation guide here : https://docs.nhost.io/platform/quickstarts/nextjs

I'll just stick with firebase


Make TypeMaps work with superclasses of mapping sources

Hello,
I have some trouble mapping inherited source classes with the ModelMapper:
Situation:

abstract class: Fruit
class: Apple extends Fruit
class: Banana extends Fruit
DTO class: FruitDTO

Now the root of the problem is that I couldn't simply register a Provider for the Fruit -> FruitDTO TypeMap.
I managed to sail around registering the same provider for both - Apple and Banana - separately.
Where I really run into problems is when working with mocks in tests. There even the two separate configurations won't help, because there I have the mock proxy objects. And a Apple$MockitoMock is not an Apple...
Is it possible in future to make TypeMaps work also for subclasses of the registered classes? Or at least also de-proxy source types? I found the following for destination types
engine.<Object, D>map(source, Types.<Object>deProxy(source.getClass()), destination,         TypeToken.<D>of(destinationType), typeMapName);
in ModelMapper#573 but I can't estimate the final impacts also in other places.

I guessed Type Map Inheritance is what you are looking for.

I guessed Type Map Inheritance is what you are looking for.

This is a tedious manual approach. An automatic mechanism should be made:

When creating a typemap, a check should be made if a typemap for a base type exists and inherit it automatically.
Inheriting typemap doesn't inherit provider/converter/etc.

Please change this form Question to `Feature request.