How can i get the information about Focus with a kinect DK?

I am doing some work about Multi-focus Image Fusion.And I try to get some train dataset by Kinect dk which can provide me RGB and Depth data. SO I want to know if Kinect dk can Adjust the focus of kinect dk . if not , how can I calculate the focus ?

It is my understanding that the Kinect Azure RGB camera is a fixed focus camera.
You can get the camera calibration matrix which contains the focal point and other intrinsic/extrinsic values using https://docs.microsoft.com/en-us/azure/kinect-dk/use-calibration-functions#retrieve-calibration-data

Very thank you for response，and i do get the matrix and focal point .Just like these picture.

SO I want to know is the matrix Unchangeable？If I can change it , how should I do?
It is very important for my work , if it is possible I can get the Multi-focus image as my train data.
Thanks again.

The calibration matrices (intrin, extrin) are unchangable for a given mode (wide pov, narrow pov, etc.). There is no variable lens focus.

Thank you very much.

problem solved


Added better layout, graphs, and datatables for visualizing and inspecting layers

Codecov Report

Merging #64 into develop will decrease coverage by 2.04%.
The diff coverage is 0%.

@@           Coverage Diff            @@
##           develop   #64      +/-   ##
========================================
- Coverage    52.04%   50%   -2.05%
========================================
  Files            3     3
  Lines          171   178       +7
========================================
  Hits            89    89
- Misses          76    83       +7
  Partials         6     6

Impacted Files
Coverage Δ

utils/utils.go
50% <0%> (-4.55%)
:arrow_down:

Continue to review full report at Codecov.

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


context canceled and 502

1. What version of Caddy are you using (caddy -version)?
0.10.10
2. What are you trying to do?
Proxy an express app.
Seems like caddy responds with 502 and complains when I write the request and close the socket for writing. I'm still available for reading, so caddy should send me the proper response.
Note that request gets proxied just fine (I can see in webapp's logs). If I enter request in nc manually without closing the stdin then I get the right response.
3.
Docker, abiosoft/caddy image.
5.  What did you expect to see?
A proper JSON response.
7. What did you see instead (give full error messages and/or log)?
gateway_1     | <IP_ADDRESS> - - [17/Oct/2017:21:04:30 +0000] "POST /api/graphql HTTP/1.1" 502 16
gateway_1     | 17/Oct/2017:21:04:30 +0000 [ERROR 502 /api/graphql] context canceled

Btw this is reproducible every time.

I think this is related to #1828 and https://caddy.community/t/error-context-canceled/2034
The request goes through to the backend, but the user gets a 502 Bad Gateway error.

This can also be forced upon caddy via browser requests. Imagine a backend serving this simple php at localhost:8081 :
<?php
sleep(10);
phpinfo();
?>

And a simple Caddyfile like this:
:8080 {
        log / stdout "{host} {combined} {request_id}"
        errors stderr

        proxy / localhost:8081 {
                transparent
                policy least_conn
                keepalive 5
                fail_timeout 10s
                max_fails 1
                try_duration 1s
        }
}

Point your browser to http://localhost:8080 and wait for the phpinfo to be displayed - works.
Press F5 and while it's loading the ESC button -> you'll see [ERROR 502 /] context canceled message in the log.
Press F5 again within fail_timeout and you'll get 502 bad gateway and [ERROR 502 /] no hosts available upstream in the caddy log. This will persist until fail_timout has passed since the first fail. In the log of the backend (NGINX), I only get a HTTP 499.
2018-03-03T14:24:05+00:00 <IP_ADDRESS> - - localhost/localhost "GET / HTTP/1.1" 499 4.048 374 0 29 1 "-" "-" "Mozilla/5.0 (X11; Linux x86_64; rv:58.0) Gecko/20100101 Firefox/58.0"
So it seems caddy is misinterpreting the client "error" for a backend error.

In my case I'm currently using a fail_timeout 0 as a workaround or else all my sites go down for fail_timeout.
@mholt This sounds pretty much exploitable for DDoS attacks, doesn't it?
Caddy Version: 0.10.11 (and build from git https://github.com/mholt/caddy/commit/5552dcbbc7f630ada7c7d030b37c2efdce750ace).

Is this still an issue in 0.10.14?

@tobya Just tested it and unfortunately yes, it is still present.
$ ./caddy -version
Caddy 0.10.14 (non-commercial use only)
$ ./caddy -conf Caddyfile
Activating privacy features... done.
http://:8080
WARNING: File descriptor limit 1024 is too low for production servers. At least 8192 is recommended.

Haven this issue too on 0.11.0

Are there any plans to fix this potentially devastating issue? (as it can be exploited for a DDoS attack)

It has a devastating potential as it can be exploited for a DDoS attack...

Do explain...

@mholt: It is enough that one evil client will repeatly make request and imidietly close connection and caddy will stop proxing for defined fail_timeout time. Even if you set max_fails higher than 1, only client could easily do it cancel that many request in row. so it is not even DDoS, but more severe DoS attack.

Hmm, I see. Well, you could for now use fail_timeout of 0 if you're worried about attacks like that; but better would be to have this fixed. I don't have the time right now to do it, but I welcome pull requests, and help reviewing them to get them merged.

Setting fail_timeout to 0 will make load balancing proxy useless (it will forward requests to truely failed nodes, all the time), so it is not really option.

I understand that. Feel free to open a pull request for quicker resolution!

I suggest tagging this issue as "Bug".
Was original issue fixed by #2297?

Good point; yes, we seem to handle the context cancelled error specially now, so that it does not consider the backend to be down. I believe this is fixed.

I've been running into issues with Caddy 0.11.5 constantly stopping, and noticed a lot of these in my log files:
18/Apr/2019:22:44:46 -0500 [ERROR 499 /radarrdoc/signalr/connect] context canceled
18/Apr/2019:22:44:52 -0500 [ERROR 499 /lidarrdoc/signalr/poll] context canceled
18/Apr/2019:22:45:10 -0500 [ERROR 499 /sonarrdoc/signalr/poll] context canceled
18/Apr/2019:22:46:47 -0500 [ERROR 499 /lidarrdoc/signalr/poll] context canceled
18/Apr/2019:22:48:24 -0500 [ERROR 499 /lidarrdoc/signalr/poll] context canceled
18/Apr/2019:22:48:24 -0500 [ERROR 499 /lidarrdoc/signalr/abort] context canceled
18/Apr/2019:22:48:24 -0500 [ERROR 499 /sonarrdoc/signalr/poll] context canceled
18/Apr/2019:22:48:24 -0500 [ERROR 499 /radarrdoc/signalr/poll] context canceled
18/Apr/2019:22:49:56 -0500 [ERROR 499 /lidarrdoc/signalr/poll] context canceled
18/Apr/2019:22:51:44 -0500 [ERROR 499 /lidarrdoc/signalr/poll] context canceled
18/Apr/2019:22:57:44 -0500 [ERROR 499 /lidarrdoc/signalr/poll] context canceled
18/Apr/2019:22:58:07 -0500 [ERROR 499 /lidarrdoc/signalr/poll] context canceled

After a bunch of trial and error with the way I start PHP it just keeps happening no matter how I call it, which led me to stumbling upon this post. I tested with @ionphractal 's insturctions and it seems to still be happening in this version of Caddy.
caddy
Activating privacy features... done.


Import Historical Identity Validation Through SFAS-SIMS Data Bridge

Hugh to Confirm that this is reflected in business processes of the Ops Manual / alternative process list before closing the ticket
TBD Whether this is included in-scope or not. Requirements
https://bcgov.sharepoint.com/:u:/r/teams/00371/Shared Documents/General/b)%20Development%20and%20Testing/SIMS%20Project%20Scope,%20Enhancements%20%26%20Decisions/Decisions/Decision%20Materials/SIN-less%20Parents%20and%20LevelofAssurance%20from%20SFAS.msg?csf=1&web=1&e=jQupvO
It is anticipated that:

Not all students who are eligibile for BCSC will actually use that login method; actual # of student susing BasicBCeID path is anticipated to be ~500 students
For BasicBCeid students, each one needs to have their identity validated offline by Service Delivery
For many of those BasicBCeID students, their identity has already been validated in legacy systems, and it would be great to have a method of recognizing that validation so we don't have to do it a second time.

Question for Business:

Can we not ask SD to just manually review their SFAS records anytime a request for BasicBCeID account is submitted to SIMS?

Closing as this is captured within the Operations Manual; Ministry staff can look up a student's prior relationship with SABC and honour any preivously approved identity attestation forms used by SABC.


Editor Design Document contains older screen shots

Following link https://docs.wso2.com/display/SP420/Working+with+the+Design+View contains older screen shots. Can we please update them

Suggested Labels:

Suggested Assignees:

Affected Product Version:
OS, DB, other environment details and versions:
Steps to reproduce:
Related Issues:

Replaced the images and changed the related text in [1] and [2]. Added descriptions for Pattern and Sequence. Please review.
This correction was made for SP versions 4.2.0, 4.3.0, and 4.x.x.
[1] https://docs.wso2.com/display/SP430/Working+with+the+Design+View
[2] https://docs.wso2.com/display/SP430/Creating+a+Siddhi+Application

Closing as per above comment


PT-1224 | Add notice about unreliable mail traffic

Waiting for translations

Codecov Report

Merging #161 (5ae89d3) into master (f283adb) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #161   +/-   ##
=======================================
  Coverage   92.64%   92.64%
=======================================
  Files         103      103
  Lines        3401     3401
  Branches      609      609
=======================================
  Hits         3151     3151
  Misses        247      247
  Partials        3        3

Impacted Files
Coverage Δ

src/domain/event/EventPage.tsx
96.05% <ø> (ø)

Continue to review full report at Codecov.

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


builder not displaying underlying error

When the builder fails, there is no error output. it just responds with [remote rejected] master -> master (pre-receive hook declined) with no reason for the error. This was introduced when we refactored the builder in #2335 to start refactoring the component over to Go.
This has been seen in previous issues such as #2876 and in #1748, so a fixup would help us better determine the underlying issue.

:100:

This seems to have gone away -- if not, please open another issue on the specific error. :)


Fixed Driver Dependency Tests on Windows

All Driver/Dependency tests now pass on Windows!
Requires https://github.com/apple/swift/pull/22596
-- Testing: 52 of 4486 tests, 12 threads --
Testing: 0 .. 10.. 20.. 30.. 40.. 50.. 60.. 70.. 80.. 90..
Testing Time: 150.70s
  Expected Passes    : 43
  Expected Failures  : 2
  Unsupported Tests  : 7

The two expected failures are due to tests which expect parallel execution. The unsupported tests are due to the use of $(subshells), mostly to get the version of swift compiler that is running.
As part of this, I've also implemented output buffering for the default TaskQueue implementation since it was required for a few of the tests. Are there platforms besides Windows that use the default implementation that I need to be aware of?  @compnerd had mentioned rewriting the Windows TasksQueue implementation so that it supports parallel execution soon, so this might be a temporary thing anyways.
@jrose-apple

Cleaned up both the code and the temp files!

TIL, list initialization is really neat.
     SmallVector<Optional<StringRef>, 4> redirects = {None, {stdoutPath}, {stderrPath}};

They did need the extra braces though, clang wasn't able to go from the stdoutPath: SmallString directly to Optional

(not running full tests because the code being changed isn't used on POSIXy platforms…)
@swift-ci Please smoke test

Oops, I forgot that this one requires the other one.

@swift-ci Please smoke test

Looks like something's not quite right even after merging the other PR. Can you take a look?

I'm not entirely sure what happened. I'm unable to reproduce it on either a Linux (CentOS) or macOS machine locally. Is there something special about the Jenkins environment that I should know about?
The expected stdout and stderr look okay: the ls error is expected, but fake-ld.py never ran. The test overrides ld with fake-ld.py then expects swift to call it which then does a few assertions and prints out "Handled link" It seems like one of the tasks the driver spawned got killed before fake-ld was able to print...
13:39:28 --
13:39:28 Exit Code: 1
13:39:28
13:39:28 Command Output (stdout):
13:39:28 --
13:39:28 /Users/buildnode/jenkins/workspace/swift-PR-osx-smoke-test/branch-master/buildbot_incremental/swift-macosx-x86_64/test-macosx-x86_64/Driver/Output/filelists.swift.tmp/tmp/outputs-bee66b
13:39:28 /Users/buildnode/jenkins/workspace/swift-PR-osx-smoke-test/branch-master/buildbot_incremental/swift-macosx-x86_64/test-macosx-x86_64/Driver/Output/filelists.swift.tmp/tmp/sources-7c25b1
13:39:28 /Users/buildnode/jenkins/workspace/swift-PR-osx-smoke-test/branch-master/buildbot_incremental/swift-macosx-x86_64/test-macosx-x86_64/Driver/Output/filelists.swift.tmp/tmp-crash/outputs-ce9afc
13:39:28 /Users/buildnode/jenkins/workspace/swift-PR-osx-smoke-test/branch-master/buildbot_incremental/swift-macosx-x86_64/test-macosx-x86_64/Driver/Output/filelists.swift.tmp/tmp-crash/sources-f43471
13:39:28
13:39:28 --
13:39:28 Command Output (stderr):
13:39:28 --
13:39:28 ls: /Users/buildnode/jenkins/workspace/swift-PR-osx-smoke-test/branch-master/buildbot_incremental/swift-macosx-x86_64/test-macosx-x86_64/Driver/Output/filelists.swift.tmp/tmp-fail/sources-*: No such file or directory
13:39:28 ls: /Users/buildnode/jenkins/workspace/swift-PR-osx-smoke-test/branch-master/buildbot_incremental/swift-macosx-x86_64/test-macosx-x86_64/Driver/Output/filelists.swift.tmp/tmp-fail/outputs-*: No such file or directory
13:39:28

<unknown>:0: error: compile command failed due to signal 9 (use -v to see invocation)
13:39:28
/Users/buildnode/jenkins/workspace/swift-PR-osx-smoke-test/branch-master/swift/test/Driver/filelists.swift:68:16: error: CHECK-LINK: expected string not found in input
13:39:28 // CHECK-LINK: Handled link
13:39:28                ^
13:39:28 <stdin>:1:1: note: scanning from here
13:39:28 Handled a.swift
13:39:28 ^

…Well, I don't get it either, but to not block this PR, how about you just revert the changes to test/Driver/filelists.swift for now? The test is still using symlinks so it's already marked unsupported on win32.

Reverted the filelists.swift changes. Let's see if it's happier now.

@swift-ci please test

@swift-ci please test

Build failed
Swift Test OS X Platform
Git Sha - ac0d9ef31a8f16e34deef1e779daff838f45f5c0

@swift-ci please test macOS platform

Build failed
Swift Test OS X Platform
Git Sha - ac0d9ef31a8f16e34deef1e779daff838f45f5c0

Build failed
Swift Test OS X Platform
Git Sha - ac0d9ef

Same as the previous run, During iphone simulator tests:
xcodebuild: error: The authorization was denied since no user interaction was possible.

That might have been an Xcode update. Let's try one more time. (If not, it's a test change again and we'll have to figure out why.)
@swift-ci Please test macOS

Build failed
Swift Test OS X Platform
Git Sha - ac0d9ef31a8f16e34deef1e779daff838f45f5c0

@swift-ci Please test macOS

Yay, gonna merge this, as this prevents the test harness from dying!


"Explore" button in SQL Editor is disabled

Make sure these boxes are checked before submitting your issue - thank you!

[✔ ] I have checked the superset logs for python stacktraces and included it here as text if there are any.
[✔ ] I have reproduced the issue with at least the latest released version of superset.
[ ✔] I have checked the issue tracker for the same issue and I haven't found one similar.

Superset version
0.28.1
Expected results
Visualize button
Actual results
disabled Explore button instead of Visualize button
Steps to reproduce
We added druid as a sql database and ran some queries, works fine. But we are not able to visualize the result. Explore button is disabled.

Thanks for the feedback.  Four months ago i used this feature to create charts, just wondering why cannot now.  That time it shows Visualize button instead of Explore.
I will wait for upcoming feature  direct chart inside SQL Lab :)

Yes it worked.  I created some charts to visualize ivw monthly data. We are using those charts every month by "force refresh" option to visualize new data.

Hello,
It seemed like I am having quite similar problem here...
superset version: 0.29.0rc7
python version: Python 3.6.8
node version: v10.16.0
the 'explore' button seems like disabled:

There's only error shown in the console in the internet browser:

same here ... I cant see it either - does it only work with some sources ?


[Existing API Name] : Wetather fetching api

Brief Description 🤓
Fetch the current weather of any place using OpenWeatherMap api. please assign this to me under gssoc.
Provide reference!
.
Select the open source program you are contributing to
Other
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINES of this project.

Greetings @kashnx🎀 ! , We are excited to have you dive into another issue with us!🚀
Your involvement in our project has been invaluable, and we're confident that your skills and insights will help us conquer this challenge😇.  Use command /gssoc24 to self assign the issue.  This issue represents an exciting opportunity for us to improve and enhance our project, and we are thrilled to have you on board.
We request you to follow CONTRIBUTING GUIDELINES.
Looking for your PR soon!
In case of any issues, you can contact us on Discord.❣

/gssoc24


Register FluentValidation with SimpleInjector

FluentValidation 8.1.3
ASP.NET Core 2.2

We use SimpleInjector for DI and we are building custom validators which use components registered in SimpleInjector container. We can't find a way to register fluentValidation with SimpleInjector so it can use the validators we register there. Is there a way?

Hi, I'm not sure I understand your question...FluentValidation is completely agnostic of which DI container you want to use

It's just that it's registered in IServiceCollection but the integrated DI can't read registrations fron the SimpleInjector container so it doen't work. As we use generics Validators the have to be registered in the container like this
container.Register<IValidator<ClientCareManagerModel>, MetadataFluentValidator<ClientCareManagerModel>>();
but it doen't validate when it's registered there. If I register in the service collection
services.AddScoped<IValidator<ClientCareManagerModel>, MetadataFluentValidator<ClientCareManagerModel>>();
it's called but for more complex case we need components registered in the SimpleInjector container to be injected in custom validator so that's the problem we are facing.

You need to provide a validator factory. The default factory pulls from the service collection.
Create  a SimpleInjectorValidatorFactory that inherits from FluentValidation.ValidatorFactoryBase and implement the CreateInstance method, which should resolve the validator of the specified type from SimpleInjector. You can then provide this in your app startup.
services.AddMvc().AddFluentValidation(fv => {
   fv.ValidatorFactory = new SimpleInjectorValidatorFactory();
   // or fv.ValidatorFactoryType = typeof(SimpleInjectorValidatorFactory)
});

Can you give me some details on how to implement the CreateInstance method.

You'll need to obtain a reference to the SImpleInjector container, and ask it to resolve the type that's passed into the method. I can't help you more than that I'm afraid, as the logic will be specific to working with SimpleInjector, which I've never used

`public class SimpleInjectorValidatorFactory : ValidatorFactoryBase
{
private readonly Container container;
    public SimpleInjectorValidatorFactory(Container container)
    {
        this.container = container;
    }

    public override IValidator CreateInstance(Type validatorType)
    {
        Type generic = typeof(IValidator<>);
        Type specific = generic.MakeGenericType(validatorType);

        return this.container.GetInstance(specific) as IValidator;
    }
}`

Is that ok?

You don't need the 2 lines beginning Type generic and Type specific ... that's already handled by the base class. The type passed in is the final, closed type that you need to resolve.

Ok thanks

I have this error when I try to use a custom validatorFactory
No registration for type IValidator could be found. Note that there exists a registration for a different type FluentValidation.IValidator while the requested type is FluentValidation.IValidator<System.Guid>.

Right....MVC will attempt to instantiate validators for every type it encounters. You need to handle that at the container level. Inside your factory you need to check whether the type is registered. If not, return null.

Again I'm not sure what the api is for SimpleInjector, but most containers have a IsRegistered(type) or something like that. For those that don't have that, there's usually a GetAllInstances(type) you can use instead (ie if 0 are returned, then return null)

Thanks for your help, it works perfectly now.


rapid metadata indexing can incur ~O(N^2) behavior

This is relevant to the new (NIEHS) metadata schema, as all metadata AVU are now kept within  a list element of the index record describing the data object (or collection) they annotate.
Because of this, any  scenario (but in particular automated ingest with importation/translation of many e.g. header key-value elements then  being attached as AVU's by the ingest hook) in which N  metadata AVU's are attached in rapid-fire fashion will spawn N delayed re-indexing tasks. If the object starts out with no AVU's (best case) we will have an average of N/2 AVU's already present, so the total number of iterations over AVU's tends toward N*(N/2), which is order N-squared.

One way around this, with the upcoming release (<IP_ADDRESS>) of the indexing plugin, will be to use  atomic metadata operations where feasible (python-irodsclient will now allow this).
But ultimately, we may want to follow the approach of limiting the number of delayed tasks submitted per object, particularly when they are seen at time of submission to be redundant with later tasks already entered into the delay queue.

for clarity... "later tasks already entered"... i am reading as "future tasks already entered"

Correct, that was badly worded


Jc/api options parameter

-
-

Issue
Fix https://github.com/ripe-tech/pconvert-rust/issues/21

Dependencies
None

Decisions
1. blend_* methods now receive an additional options argument which is a map of optional settings with corresponding values (e.g. python dict options = {"num_threads": 5})  2. Current supported options are num_threads (if 0 or less, methods are single-threaded), compression and filter types (lower case strings of the enum versions of image::png::CompressionType and image::png::FilterType)  3. Note that the WASM module can't make use of the std::thread API, and since it still does not make use of web workers, there is no need to pass num_threads and since the resultant file is not compressed or "filtered" before writing (because is is not written to a file system), this PR does not implement optionsfor the WASM module. Future web workers implementations and corresponding PRs should pass these optional parameters (like num_web_workers

@joao-conde please fix the conflicts

@joao-conde let's be careful about merging conflicts


when called without args, mp_land.jnl forgets to do modulo replications

Reported by andrew wittenberg on 1 Apr 2015 21:28 UTC
(We discovered the following when working with our ocean model data, which has longitudes on the interval -280:80.)
First create a variable with longitudes on the interval -360:0.
 	NOAA/PMEL TMAP
 	FERRET v6.933 (beta)
 	Linux 2.6.32-504.3.3.el6.x86_64 64-bit - 01/27/15
 	 1-Apr-15 17:18

yes? use coads_climatology
yes? def ax/x/unit=degrees_e/modulo `sst,r=xaxis` = x[!-> def ax/x/unit=degrees_e/modulo COADSX = x[gx=sst](gx=sst]-360
)-360
Replacing definition of axis COADSX
           *** NOTE: grid  used by data set coads_climatology
           *** NOTE: Redefinition may alter apparent contents of data set

Then do an orthographic projection, and overlay the land outline:
yes? go mp_orthographic 210 90; set grid sst; go mp_aspect
yes? shade/noax/l=1/x=0.5:360.5 sst*mp_mask, x_page, y_page
yes? go mp_land

See how the land outline is missing from -360:-180?
But if we simply provide a linestyle argument, mp_land.jnl then does the modulo replications!
yes? go mp_land 1

The bug might be at line 106 of mp_land.jnl.
See also #1654, which we might be able to resolve.
Migrated-From: http://dunkel.pmel.noaa.gov/trac/ferret/ticket/2256

Comment by ansley.b.manke on 1 Apr 2015 21:58 UTC
The script defines variables to do modulo replications, comparing the minimum and maximum map projection longitudes with the minimum and maximum longitudes in the geo_borders file.
Then it draws the map. The comments say,

! always do the continents
set grid CONTINENT_LON
...
plot/...

The next section draws any lines beyond longitude in 0:360, but only if there's an argument 1.
! Draw any lines outside 0 to 360
IF ($1"0|*>1") THEN

IF `landi_addx NE 0` THEN
...

We need to just remove that test on argument 1.
The fixed script will be in the next release, and is attached to this ticket.

Attachment from ansley.b.manke on 1 Apr 2015 21:56 UTC
the repaired script.
REPLACE THIS TEXT WITH UPLOADED FILE ./attachments/TRAC_2256_GIT_1528/mp_land.jnl


[Hotfix]  Use published webpack 4 compatible fork of react-dev-utils

Issue: https://github.com/storybooks/storybook/pull/3148#issuecomment-377233037

@Hypnosphi how do I see the changes to react-dev-utils?

Nevermind, assuming it's: https://github.com/facebook/create-react-app/pull/4077/files


<EMAIL_ADDRESS>

Hi! Just moved this to grunt v1.0.1
Changes

[x] updated deps
[x] remove unused package chalk
[x] updated README

Tests are passing too!

Can you please accept this pull request?


Self-hosted: Apollo Federation: Unable to use schema with @external

I have been trying to host schema created with Apollo Federation into self hosted Hive but seems like Hive is not composing super-graph correctly when @external is used in schema. Super-graph schema cannot used due to this issue
Example: Schema defined in subgraph1 sub-graph as below:
name: String! @external

Results in subgraph2 sub-graph schema:
name: String! @join__field(graph: SUBGRAPH2)

Expecting it to be resulted in below supergraph schema:
name: String! @join__field(graph: SUBGRAPH2) @join__field(graph: SUBGRAPH1, external: true)

This is field is implemented as part of interface in both subgraphs.

I feel like I need a small reproduction here (SDLs), I can't tell if it's an issue or not based only on informations provided by you.
I don't know how you implement an interface, I don't know if an interface has a @key directive, and if so what fields are part of it etc. There's a lot of missing things here for me to verify it.


Added basic script for batchManager command completion

Updated README to include new script
More features may be added later

Thanks!


before interceptor not working

The before interceptor below is not working.  Can someone tell me where I am going wrong?
It should return the text access token invalid and stop but it does not.
type AddressValidation struct {
	*revel.Controller
}

func (c AddressValidation) Before() (r revel.Result, a AddressValidation) {
	var rq = c.Request.In.GetRaw().(*http.Request)
	isValid, info, err := Validate(rq)
	log.Println(isValid)
	log.Println(info)

	if isValid == false {
		return c.RenderText("access token invalid"), a
	}
	if err != nil {
		return c.RenderError(err), a
	}
	return nil, a
}

Is the revel.BeforeAfterFilter in your init.go file ?
revel.Filters = []revel.Filter{
		revel.PanicFilter,             // Recover from panics and display an error page instead.
		revel.RouterFilter,            // Use the routing table to select the right Action
		revel.FilterConfiguringFilter, // A hook for adding or removing per-Action filters.
		revel.ParamsFilter,            // Parse parameters into Controller.Params.
		revel.SessionFilter,           // Restore and write the session cookie.
		revel.FlashFilter,             // Restore and write the flash cookie.
		revel.ValidationFilter,        // Restore kept validation errors and save new ones from cookie.
		revel.I18nFilter,              // Resolve the requested language
		HeaderFilter,                  // Add some security based headers
		revel.InterceptorFilter,       // Run interceptors around the action.
		revel.CompressFilter,          // Compress the result.
                revel.BeforeAfterFilter,
		revel.ActionInvoker,           // Invoke the action.
	}

Yes, it is there.  I can tell from the log that the Before method is being called but it is not stopping the request from completing as intended.  Unless I misunderstand how these work.  In the code below NOT VALID is shown in the log and I would expect "that access token invalid" would be sent back as the response but it does not.  My understanding was that any non nil value returned would stop the request from going forward.  Is that not the case?
  func (c AddressValidation) Before() (r revel.Result, a AddressValidation) {
	var rq = c.Request.In.GetRaw().(*http.Request)
	isValid, _, err := Validate(rq)
	if isValid == false {
		log.Println("NOT VALID")
		return c.RenderText("access token invalid"), a
	}
	if err != nil {
		return c.RenderError(err), a
	}
	return nil, a
}

@rps-repo did you find a solution? If not, we can add this to the queue for further digging.

@brendensoares No, I never did.

@rps-repo I think the problem in your Before method is that u have used identifier with return type. Only Return type should be there. for example my below Before function working as expected
func (p Product) Before() (revel.Result,Product) {
authToken := p.Request.Header.Get("authToken")
if(authToken == "XXXXXX"){
	return nil,p
}

data := make(map[string]interface{})
data["status"] = 0
data["message"] = "authorization fail"
return p.RenderJSON(data),p

}


Introduce model_visitor

As requested, this is a basic visitor framework on models.
Services names are inspired from those in the AST visitor.
Fell free to comment the API or suggest ideas.

test this please

+1

Easy enough, :shipit:

rerolled: improve doc

test this please

ping @Morriar


ES6 import fails

I'm trying to import the library via an ES6 import statement import InstaScan from 'instascan', which throws the following error:
ERROR in ./node_modules/instascan/src/zxing.js
Module not found: Error: Can't resolve 'fs' in 'C:\projects\my_project\node_modules\instascan\src'
 @ ./node_modules/instascan/src/zxing.js 4:725-738 4:313578-313591
 @ ./node_modules/instascan/src/scanner.js
 @ ./node_modules/instascan/index.js
 @ ./src/components/qrcode-scanner.component.js
 @ ./stories/qrcode-scanner.component.story.js
 @ ./stories/index.js
 @ ./.storybook/config.js

Is it just my npm setup beeing all messed up again, or is this lib not intended to be used that way?
Probably this is just webpack messing things up...
To reproduce create a simple react based app with one of the create-react-scripts, start the dev server and try to import and/or require it from there.
Windows 10 1607 build 14393.1480
Npm 5.03
The npm module fs is installed globally and locally in the project's folder.

I encountered this issue in react too. I managed to get it working using find/replace in instascan/src/zxing.js. Find the 2 phrases below and replace both with empty strings.
var fs=require("fs");

var nodeFS=require("fs");

I'm honestly not very familiar with zxing.js so I don't know why this works.

Not sure why webbrowser targeted libs should make any use of 'fs' but your absolutely right that this was the problem!
Thank you very much for this!
Is it appropiate to make a PR for this or will @schmich take this into account?

Unfortunately, this library breaks my webpack build process (same issue as above). The hack of @rshepp works, but is very impractical when working with multiple people on a project.
@axed Can you make a PR? That would be great :)

add this to your webpack config:
module.exports = {
  node: {
    fs: "empty"
  },
  entry: {
    app: [
      './src/main.js'
    ]
  },
...

Like in https://github.com/pugjs/pug-loader/issues/8#issuecomment-55568520

add this to your webpack config:
module.exports = {
  node: {
    fs: "empty"
  },
  entry: {
    app: [
      './src/main.js'
    ]
  },
...

Like in pugjs/pug-loader#8 (comment)

alhamdulillah bisa :)


feat: backup dir contents with google cloud and inotify

Adds a crate to do filesystem compressed tar backups of the rocksdb database to google cloud using inotify.
Can do interval backups or backup on closing every write.

moved to separate project


[BUG] All requests are delayed when using RequestRetryOptions

Describe the bug
When using RequestRetryOptions on the BlobServiceClient, also successful requests are delayed by retryDelayInMs. I would expect successful requests to return immediately.
Exception or Stack Trace
Output of sample code:
started https://xxx.blob.core.windows.net/container1?restype=container
done after 17140 ms
started https://xxx.blob.core.windows.net/container1/blob3?blockid=xxx%3d%3d&comp=block
done after 15183 ms

To Reproduce
Run the code snippet. Using current master branch.
Code Snippet
String CONN = "DefaultEndpointsProtocol=https;AccountName=......==;EndpointSuffix=core.windows.net";

int maxTries = 1;
long retryDelayInMs = 15_000L;

BlobContainerClient blobContainerClient = new BlobServiceClientBuilder()
        .connectionString(CONN)
        .retryOptions(new RequestRetryOptions(RetryPolicyType.FIXED, maxTries, 20, retryDelayInMs, retryDelayInMs, null))
        .addPolicy((context, next) -> {
                    long start = System.currentTimeMillis();
                    System.out.println("started " + context.getHttpRequest().getUrl());
                    return next.process()
                            .doFinally(e -> System.out.println("done after " + (System.currentTimeMillis() - start) + " ms"));
                }
        )
        .buildClient()
        .getBlobContainerClient("container1");

blobContainerClient.exists();

BlockBlobClient blob1 = blobContainerClient.getBlobClient("blob3").getBlockBlobClient();
blob1.getBlobOutputStream().write("hello world".getBytes());

pom.xml:
<dependency>
            <groupId>com.azure</groupId>
            <artifactId>azure-storage-blob</artifactId>
            <version>12.1.0-preview.1</version>
        </dependency>

(azure-storage-blob was built locally (commit a08d971a493efb06777f4b9572cb836f61412185))
Expected behavior
There should be a delay after errors, but only if maxTries>1.
There should be no delay if maxTries=1 for errors.
There should be no delay on success.
log output when RequestRetryOptions is not used:
started https://xxx.blob.core.windows.net/container1?restype=container
done after 1378 ms
started https://xxx.blob.core.windows.net/container1/blob3?blockid=xxx%3d%3d&comp=block
done after 144 ms

Setup (please complete the following information):

OS: macOS
IDE : IntelliJ
Version of the Library used: current master branch (commit a08d971a493efb06777f4b9572cb836f61412185)

Additional context
Workaround

do not use RequestRetryOptions. (we need retry)
use com.azure.storage.common.policy.RetryPolicyType#EXPONENTIAL with a very small retryDelayInMs (we want linear backoff)

@synox Thanks for pointing this out. It looks like you're right that we incorrectly apply the fixed timeout to the first try. I will work on getting a pull request out for this. In the meantime, I think you can work around this by using exponential retries and setting your retry delay and max retry delay to be the same value.


[KOGITO-6677] Implementing keep active

I have to create an example, but this can go, since it depends on well tested kie engine

(tests) - kogito-runtimes job #329 was: UNSTABLE
Possible explanation: This should be test failures
Please look here: https://eng-jenkins-csb-business-automation.apps.ocp-c1.prod.psi.redhat.com/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-runtimes.tests.kogito-runtimes/329/display/redirect
Test results:

PASSED: 2748
FAILED: 1

Those are the test failures:

org.kie.kogito.quarkus.workflows.ParallelStateIT.testPartialParallelRest
java.lang.AssertionError: 1 expectation failed.JSON path workflowdata.result doesn't match.Expected: a CharSequence with length <2>  Actual: ABC	at org.kie.kogito.quarkus.workflows.ParallelStateIT.testPartialParallelRest(ParallelStateIT.java:50)


Possible Issues with New NodeJS Documentation

I recently received the pointer to the new NodeJS Getting Started with the Node SDK development documents (https://kintegrate.dev/tutorials/getting-started-node-sdk/).  After review and several unsuccessful hours/days of testing, there seem to be many issues with following that guidance as it is written.  The steps assume the reader will guess or reverse engineer the source code to figure out the missing steps to get it going.  As a examples:
2. Create a Node.js app and add the kin.ts class to your app
There is no guidance in the document for how the best way to include that class.  One could assume that the tsc package needs to be installed and working, but there is no prerequisite list of extra node packages that must be included to indicate we need tsc.  In addition, depending on the operating system (Fedora 33 server in my case) tsc presents all kinds of issues because it must be globally installed vs. local.  I had to find that out the hard way as most folks assume local tsc package installs should work.  The end result of using tsc was 17 compile errors on that kin.ts file.  One could also assume that edits could be made to the package. json file to include {"target", "module"} to allow import of the ts file as is with no compile and the extension changed to js for nodejs.  But again, its not clear which path is best without instructions.
Using either of those approaches does not provide a clear understanding of what should be required or imported after inclusion in my own test.js script.   As an example the very next step says the following:
3. Instantiate a new Kin client
// Set up Kin client
const kin = new Kin(Environment.Test)
How?  When did you tell me what to require or import  where?  Should I  have done any of the following?
Kin = require('./kin.js')  OR, Import Kin as './kin.js'
In your instructions on the main kin_node githum site located here: https://github.com/kinecosystem/kin-node/tree/master/src.  You say do this:
import {Client, Environment} from "@kinecosystem/kin-sdk-v2";
const client = new Client(Environment.Test);
I realize that the NEW and improved instructions say use the kin.ts file and use Kin for the new kin, but the reason I mention this is the because of the following things I found. After a require or import of ./kin.js to Kin as a guess and proper assignment of kin to new Kin(Environment.Test).  I get the following nodejs error.
const kin = new Kin(Environment.Test)
ReferenceError: Environment is not defined
After hours of digging through various pieces of your code located:
HERE: https://github.com/kinecosystem/kin-node/tree/master/examples/client
AND HERE: https://github.com/kintegrate/kin-starter-node/tree/main/src
AND HERE: https://github.com/kinecosystem/kin-node/tree/master/src
Then, compiling your various ts.files with errors and looking through the code there I managed to get some of the basic things working by reverse engineering what I saw in your source ts and compiled js files and coming up with things that worked somewhat.  After custom edits to my package.json file to allow us of import statements instead of requires statements, I ended up hacking the kin.ts file and taking what I needed to create my own test.js file by including the following in it:
import { Client, Environment, kinToQuarks, PrivateKey, PublicKey, TransactionType } from '@kinecosystem/kin-sdk-v2'
This revealed that the main kin_node source code only exposes Client as an option.  So I used that in the workarounds I produced.  Also while tracking the original error down, I reviewed the source code outputs (kin.js) from the compile of the kin.ts file and found the following:
kin = new kin_1.Kin(kin_sdk_v2_1.Environment.Test);
That is not anywhere close to the instructions provided in your new guide that says do the following once importing the kin.ts class:
const kin = new Kin(Environment.Test)
However creating my workaround via direct import of the exposed Environment method, I was able to execute most of the rest of your guide until I got to the requestAirDrop function.  The function provided in your guide does not match the declared function in your source which, requires a publicKey value vs. the Account object or array you specified in your original gitlab source located here:
https://github.com/kinecosystem/kin-node/tree/master/src
console.log('Request Airdrop for Alice')
await kin.requestAirdrop(balancesAlice[0], '10')
balanceAlice[0] in this case throws an error stating that the 0 is invalid.  balanceAlice alone throws and error stating that the Account or Key information is incorrect.  I reviewed the source code in the kin_node source and found that the original method declaration for requestAirdrop() requires the PublicKey.   I also initially experienced  an error at line 450 of<EMAIL_ADDRESS>where running the function produced an error for req.setQuarks(quarks.toNumber()) stating that quarks.toNumber does not exist.  I later found that  toNumber is not even a function to be used in this way.
Understanding the issue I changed that line to the following just to see if everything else would work:
var quarkserror = "quarks value needs to be number";
Number(quarks)? req.setQuarks(quarks) : quarkserror;
I got that section to work then got a series of "Account doesn't Exist" errors when attempting to run the requestAirDrop method.   I could not get that issue resolved using my own code.
I also forgot to mention earlier that Step 4 also fails.  Here is how it reads:
4. Create account for Alice
const privateKeyAlice = Kin.generateKey()
In the source code located here https://github.com/kinecosystem/kin-node/tree/master/src  there is no function that exists anywhere with that name (searched entire source code directory using grep generateKey * -R).  The function does not exist.  Even in your kin.ts or resulting tsc compiled kin.js file there is no reference to generateKey in the context of creating a new user account and key pair. There is reference to the .generateKey and .random().  I see that there is an exported method in the Kin class under kin.ts called generateKey.  I am assuming that the tsc errors produced at compile time did not allow generation of that method in my final kin.js file.
Finally I read at the bottom of your guide page regarding the quick startup files.  I downloaded the nodejs quickstart up source code located here: https://github.com/kintegrate/kin-starter-node/tree/main/src.  Again, there were no instructions or guide as to how I should use them.  Again, I had to guess that I should use tsc to compile them into nodejs usable form.  Again, I received plenty of errors.  However, this time when I ran the index.js file using node everything worked ok, but it ran a tight set of related scripts in a specified order.  So that means, I am still going to have to dig through the source code in those compiled *.js files to figure out the right function calls to use what you created for my own app.  So far, they do not seem to match up in any way to the NEW or OLD guide you provided.
Did I miss something in the documents you provided or are there a new ones coming?

@lvto2000 thanks for writing this up. Please provide any feature issues with Kintegrate.dev to the repo https://github.com/kintegrate/kintegrate.dev as it's not about the sdk.
However, from reading your post I feel like there might be some assumptions about the level of knowledge from the developer we expect, and have not made explicit - this is my fault.
We expect the developer to have decent working experience with the specific tech  they pick. You should for instance never have to compile anything manually, nor run tsc manually.
I'm sorry this has cost you hours or days, that's what we try to avoid. I invite you to join the Discord linked on https://kintegrate.dev and ask questions in the kin-node channel.
That way we can help you better buy guiding you along the way, and pointing to resources that might help cover the base knowledge of using Node with TypeScript.

Hmmm...  Well, I still got it working being the lowly programmer that I am.  :-)  I appreciate your graciousness in owning the issue nonetheless.  I will readily concede that I am not among the cool kid Principle Software Developers for nodejs.  However, I have been programming in various languages for over 30 years.  With that in mind and now that I have it working, there are some fairly simple steps that could be added to your guide that will assist all levels of programmers in understanding what should be simple starter examples in my mind.
As a potential business who might use Kin, I would expect all of my programming folks to at least be able to get your basic API examples working with minimal effort and knowledge.  That's why you developed them I would hope.   As an example (pun intended), to elect to use TypeScript vs nodejs's for such a small code stack (learning examples) seems like a bit of  ostentation even for the nodejs cool kids.  Conversely, selecting a scripting language with that level of meticulousness and complexity vs pure JavaScript, would make interested users assume that same level of detail would be followed with the guides to support it.
Again, I appreciate you owning the issue.  Still, as a Kin holder it is terrifyingly sobering to know that this is what potential companies and curious users/programmers of kin's API may be experiencing and not saying anything or anything good to folks who want to know about Kin's interoperability in their business models.   I think the "assumptions about the level of knowledge from the developer [you] expect" are not good for this purpose.   Just my 2 cents, but I strongly recommend that you take ALL the guides that you posted thus far.   They should never see the light of day until the new documentation is fully complete and thoroughly tested by folks not close to your direct DevOps group and devoid of the usual "advanced" programmer assumptions that usually come with the cool kids way of thinking vs the Kin business's bottom line.  I don't need hand holding on Discord to know that.   Appreciate the offer though.

@lvto2000 I'm sorry to hear you feel this way. Others have praised the new docs as it was 'exactly what they were looking for'. So to each their own I guess.

Yes I am fully aware of the echo chamber and fan boys who are exist on Reddit, Discord and other Kin communities.  Believe it or not, I am here to help from a different perspective.
Again, I appreciate your graciousness in trying to find a solution.  Just forgive me if I am not completely loving all of it. :-)

Your package.json file that looks as if it requires the same tsc program (highlighted below) I used to compile the js code that worked.  Interesting.  Got mine to work before in your kin-starter-node directory before I found this, then I moved that file to the kin_node_master where it wasn't working.  Then  I ran npm install.  Now it works in that directory too.   So I am not sure I agree with this statement "You should for instance never have to compile anything manually, nor run tsc manually." However, I was never supplied an alternative method even in your last post.
This package.json file for notes if I or some other poor soul need to reference later.
{
"name": "kin-starter-node",
"version": "1.0.0",
"description": "",
"main": "index.js",
"scripts": {
"dev": "ts-node-dev --respawn src/index.ts",
"test": "echo "Error: no test specified" && exit 1"
},
"keywords": [],
"author": "Bram Borggreve",
"license": "ISC",
"devDependencies": {
"@kinecosystem/kin-sdk-v2": "^0.5.0",
"@types/bs58": "^4.0.1",
"@types/node": "14",
"bs58": "^4.0.1",
"ts-node-dev": "^1.1.1",
"typescript": "^4.1.5"
},
"dependencies": {
"@kinecosystem/agora-api": "^0.26.1"
}
}


Run unbundle before bundling.

It is almost always a good practice to run unbundle before bundling. The existing bundle injection and depCache should be cleared from config.js.

Fixed in our tasks. Clean runs unbundle.


Add safe notification center utility.

This wraps up NSNotificationCenter so that observers can be removed
automatically, which is much less error prone.

@hanningni please review. This NSNotification change will be used for listening to push notifications

:+1:


Microsoft Wireless Notebook Optical Mouse 3000 dongle not recognised

Hi there. Would it be intentional that this device isn't recognised?
Still doesn't work if I manually edit rules.json to include the device ID (USB\VID_045E&PID_00E1\5&2393c676&0&1).
Thanks!

Hi @digitaltrousers, thanks for reporting it! Not intentional that your mouse dongle isn't recognised.
The USB detection uses this query:
SELECT * FROM __InstanceCreationEvent WITHIN 2 WHERE TargetInstance ISA 'Win32_USBHub'
which is in this file:
\SimpleKVM\USB\win\USBSystem.cs.
It typically detects when a USB switch has moved from one computer to another. I'll tweak it to detect your dongle in the next day or so :)
Thanks again,
Fidel

Hi @digitaltrousers, I've made a branch which detects a whole lot more USB classes. Could you please download the exe from the release section and send a screenshot of what it now displays?
It should be a lot more verbose, like this:

Thank you,
Fidel

Wow Fidel, Thanks!
Attached, a screenshot with the new build. It detects the dongle now, and if I make a rule based on the Win32_PointingDevice, it does detect correctly and increase the run count when I plug it in. However, my monitor doesn't respond. I don't know if that's expected in this build? I can correctly control my monitor using ddcutil in Linux and winddcutil in Windows.
Cheers,
Dan.

Perfect, thanks Dan! I'll add Win32_PointingDevice to the main code.
The monitor should respond. Could you please try with a hotkey rule until I update the main code?

Unfortunately with a hotkey rule, the monitor still doesn't respond. The counter increments as expected, so I presume it's attempting to send the command to the monitor.
If I run winddcutil setvcp 1 60 3, the monitor responds as expected. The monitor is a Dell U2410 from about 2013.

Thanks Dan, I've added Win32_PointingDevice to the main code and released version 1.05.
As for the not switching, could you please post your rules.json?
Thanks :)
Fidel

{
  "$type": "System.Collections.Generic.List`1[[SimpleKVM.Rules.Rule, SimpleKVM]], System.Private.CoreLib",
  "$values": [
    {
      "$type": "SimpleKVM.Rules.Rule, SimpleKVM",
      "Trigger": {
        "$type": "SimpleKVM.Rules.Triggers.HotkeyTrigger, SimpleKVM",
        "HotkeyAsString": "Ctrl+Alt+Back"
      },
      "Actions": {
        "$type": "System.Collections.Generic.List`1[[SimpleKVM.Rules.Actions.IAction, SimpleKVM]], System.Private.CoreLib",
        "$values": [
          {
            "$type": "SimpleKVM.Rules.Actions.SetMonitorSourceAction, SimpleKVM",
            "Monitor": {
              "$type": "SimpleKVM.Displays.win.Monitor, SimpleKVM",
              "MonitorUniqueId": "1"
            },
            "SetMonitorSourceIdTo": 3
          }
        ]
      },
      "RunCount": 21,
      "LastRun": "2021-12-25T20:08:08.6924515+11:00",
      "Status": 0,
      "Name": "Switch to work laptop"
    }
  ]
}

Thanks Dan, that all looks fine to me.
Could you please run the following commands with ddc_test_tool?
ddc_test_tool list
ddc_test_tool set-source --monitor 1 --source 3
(ddc_test_tool uses the same code base as Simple KVM).
Thanks and Merry Christmas!
Fidel

C:\PROGRAMS>ddc_test_tool list
ddc_test_tool v1.0
1 monitors found:
        Monitor 1:    Model     Current source: 0    Valid sources according to capability string: 1, 3, 4, 5, 12, 15, 17

C:\PROGRAMS>ddc_test_tool set-source --monitor 1 --source 3
ddc_test_tool v1.0

C:\PROGRAMS>ddc_test_tool set-source --monitor 1 --source 1
ddc_test_tool v1.0

C:\PROGRAMS>ddc_test_tool set-source --monitor 1 --source 4
ddc_test_tool v1.0

C:\PROGRAMS>ddc_test_tool set-source --monitor 1 --source 5
ddc_test_tool v1.0

C:\PROGRAMS>

Monitor doesn't respond. I also tried it in an elevated command window.
I'm no coder, but to me it looks like winddcutil is using SetVCPFeature from lowlevelmonitorconfigurationapi.h header
Thank you and Merry Christmas!

Wow, very interesting. I'm using that same SetVCPFeature function, exposed by lowlevelmonitorconfigurationapi.h in Dxva2.dll.
Does it not respond when changing to the other inputs (12, 15, 17)?

Oh, do you have more than one monitor?
I've just uploaded a new version of ddc_test_tool.
It now lists all monitors, even if they don't respond with a DDC/CI capabilities string.

I have a laptop and one external monitor. Up until now, changing to the other inputs hasn't worked.
The new ddc_test_tool works now, if I select monitor 2. Do you think we've been trying to talk to the laptop display?
C:\PROGRAMS>ddc_test_tool.exe list
ddc_test_tool v1.1
2 monitors found:
        Monitor 1:    Model Unknown    Current source: 0    Valid sources according to capability string:
        Monitor 2:    Model     Current source: 4    Valid sources according to capability string: 1, 3, 4, 5, 12, 15, 17

Ahh! That must be it.
The numbering was off by one because I excluded monitors without DDC capability.
I've released SimpleKVM 1.06 with the fix, could you please give it a go?
Thanks,
Fidel

Working! Thanks Fidel.

Woohoo! Terrific! Thanks for your patient feedback Dan :D

Dongle not recognised addressed in v1.05
Monitor not responding to change input command addressed in v1.06


Ping

Supersedes #2652 by refactoring the code into a new service class that both the in-game command and the menu GUI now use.
Quite a few Runnables and Callables here, but they all make sense (at least for me).
Feedback very welcome - first PR in ages :-)

Hooray Jenkins reported success with all tests good!

Not quite my field of expertise, sorry... but it's good to have you back. :smiley:

Thanks for this. 😄
Actually, the displaying of ping in the server list was just something added on the side. The main issue that the PR was initially targetting was the ability for clients to retrieve the client-server pings of all other clients connected to the multiplayer server, and then displaying this in the player list overlay. I wasn't familiar or confident enough to implement that one so I left it out in the end. The idea was that the server would ping all connected clients and then make this information available to the clients through some sort of subscriber system or event. Any comments or plans on implementing this one?

I believe that the server should perform the ping to all connected clients in the frame of a regular message. This could be done on a regular basis to discover stalled clients and also to serve ping stats to interested parties such as a client viewing the player overview screen.
@emanuele3d thanks :-)

Btw. creating and throwing connections away en mass looks like denial of service attacks. So a router inbetween might decide to act by blocking.
So what you suggest (using regular messages of the existing connections) can be much better.

Tested this out locally - seems to work fine :-)
Can we merge this now or do we want to change the connection / message setup? Is that more of a separate follow-up issue for later?
One minor side note that may not relate: On an server-client the ping console command complains it can't ping the server as single player doesn't count :D

I think that we can merge this with two follow-up issues:

Fix the error message for the ping console command (for single-player/server client)
Implement the ping for all clients. from the server

Hooray Jenkins reported success with all tests good!

Submitted follow-up issue #2787 - just one as I suspect the ping command should probably just be clearer until that changes more later (split apart server/client more even in single player?)
Re-tested real quick, validates fine, merging! Thanks for getting back on PRs, hope you find time for some more! :-)


Create reducing-attack-surface-in-microsoft-teams.md

@MSFTTracyP - Please review and push live under Configure

Learn Build status updates of commit d1dae39:
:warning: Validation status: warnings

File
Status
Preview URL
Details

microsoft-365/security/office-365-security/step-by-step-guides/reducing-attack-surface-in-microsoft-teams.md
:warning:Warning

Details

microsoft-365/security/office-365-security/step-by-step-guides/reducing-attack-surface-in-microsoft-teams.md

Line 45, Column 150: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/microsoft-365/security/office-365-security/turn-on-mdo-for-spo-odb-and-teams?view=o365-worldwide#step-1-use-the-microsoft-365-defender-portal-to-turn-on-safe-attachments-for-sharepoint-onedrive-and-microsoft-teams' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 93, Column 1: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-US/microsoftteams/meeting-policies-participants-and-guests' contains locale code 'en-US'. For localizability, remove 'en-US' from links to most Microsoft sites.
Line 45, Column 1: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/microsoft-365/security/office-365-security/safe-links#safe-links-settings-for-microsoft-teams' will be broken in isolated environments. Replace with a relative link.
Line 45, Column 150: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/microsoft-365/security/office-365-security/turn-on-mdo-for-spo-odb-and-teams?view=o365-worldwide#step-1-use-the-microsoft-365-defender-portal-to-turn-on-safe-attachments-for-sharepoint-onedrive-and-microsoft-teams' will be broken in isolated environments. Replace with a relative link.
Line 45, Column 150: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL.  Otherwise, remove the view parameter. URL: https://docs.microsoft.com/en-us/microsoft-365/security/office-365-security/turn-on-mdo-for-spo-odb-and-teams?view=o365-worldwide#step-1-use-the-microsoft-365-defender-portal-to-turn-on-safe-attachments-for-sharepoint-onedrive-and-microsoft-teams
Line 93, Column 1: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-US/microsoftteams/meeting-policies-participants-and-guests' will be broken in isolated environments. Replace with a relative link.
Line 119, Column 1: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/microsoftteams/manage-external-access' will be broken in isolated environments. Replace with a relative link.
Line 132, Column 41: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/microsoft-365/security/office-365-security/teams-access-policies' will be broken in isolated environments. Replace with a relative link.
Line 134, Column 29: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/microsoftteams/security-compliance-overview' will be broken in isolated environments. Replace with a relative link.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Learn Build.
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.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

@JohanFreelancer9

@MSFTBen Please review for - Validation status: passed


Doesn't work @3.0.5 via browserify

I use swiper as the main slider on a site, and with update to @3.0.5 it stopped to slide more than one slide. @3.0.4 works fine.
I build it via browserify.

Can you give me a link to live example?

The same here. Swiping works normally, but navigation buttons sporadically stop working. And again the issue occurs when effect:fade.

Closing as no further discussion and can't replicate this issue with recent version. Reopen if issue or problem is still there


crd-version and webhook-version flags should be removed

This flags are deprecated and are only useful for those that want to create CRD and Webhooks using v1beta1 which is longer served since k8s 1.22. This options does not work with the dependencies of controller-runtime and controller-tools used in this project

I will take a look into it.

As of now, I added a deprecation warning. Anything else is expected of this issue?

This plugin is alpha therefore we can remove things.
Another point is that to use v1beta1 CRD/Webhook would be required to downgrade the dependencies which we do not here. So, this option does not seems to work well either. Because of this, I thought that the best approach would to be remove them.
@varshaprasad96 wdyt?


Sync scaffolding content to identity UI

@vijayrkn do these need to me merged anywhere else to make it into 3.0 builds?


ENH: Add multivariate support for ODR Poly model

Is your feature request related to a problem? Please describe.
The current odr.polynomial model does not seem to support multiple input values (meaning x has the shape (m, n)).
This is probably true for some of the other models as well.
Describe the solution you'd like.
I think the built-in models should support a few more cases. Of course, not everything can be included and it is easy to use your own model. But I think this is still useful for enough people.
I would like the polynomial and possibly the other models to support multiple inputs.
Describe alternatives you've considered.
No response
Additional context (e.g. screenshots, GIFs)
No response

I would be happy to add a PR, if this change is welcome.
Maybe I could also include the changes for #21306 and/or #21249 in one PR.

slightly off-topic but just so you are aware: there is discussion of potential upgrades/ports for scipy.odr in gh-7107?

As noted by @lucascolley above and by @rkern in #21249, a port of scipy.odr might come in the future.
I believe this issue could be solved without breaking backwards compability. But I also believe this issue is a bit more effort as things like these tend to come with small issues and bumps hidden along the way.
So I'm not sure yet if I will add a PR. Maybe I'll be bored on a weekend soon.
But I will add my current multivariate Poly model for future readers as a starting point tomorrow.
Should this issue stay open?

One way or the other we will rewrite this anyways. So probably better leave it open so we can come back to this when the rewrite is done. It seems to me that what @rkern is cautiously suggesting, fold odr into optimize and deprecate current odr, seems like a better option to address the API issues all at once. It is a lot of work but probably the necessary evil for future proofing. Hopefully the blast radius is not too big, at least from afar, it seems like it is not used much.

Here is the promised multivariate polynomial model:
from collections import Counter
from itertools import chain, combinations_with_replacement, repeat

import numpy as np
from scipy import odr

class Polynomial:
    def __init__(self, n_feat: int, degree: int, combinations=True):
        if combinations:
            self.combinations = list(
                chain.from_iterable(
                    combinations_with_replacement(range(n_feat), i)
                    for i in range(degree + 1)
                )
            )
        else:
            self.combinations = [()] + [
                tuple(repeat(j, i)) for i in range(1, degree + 1) for j in range(n_feat)
            ]

    def est(self, _) -> np.ndarray:
        return np.ones(len(self.combinations))

    def transform_x(self, x: np.ndarray):
        return np.array([x[list(idxs)].prod(axis=0) for idxs in self.combinations])

    def fcn(self, beta: np.ndarray, x: np.ndarray) -> np.ndarray:
        x = self.transform_x(x)

        return (beta[:, None] * x).sum(axis=0)

    def fjacb(self, beta: np.ndarray, x: np.ndarray) -> np.ndarray:
        return self.transform_x(x)

    def fjacd(self, beta: np.ndarray, x: np.ndarray) -> np.ndarray:
        x_t = self.transform_x(x)

        res = np.zeros_like(x)
        for i in range(x.shape[0]):
            counts = np.array([Counter(j)[i] for j in self.combinations])
            res[i] = (counts[:, None] * beta[:, None] * x_t).sum(axis=0) / x[i]

        return res

model = Polynomial(2, 5, combinations=True)
odr_model = odr.Model(model.fcn, model.fjacb, model.fjacd, estimate=model.est)

For example, with a model of 2nd order and 3rd degree, it calculates $y = \beta_0 + \beta_1 x_0 + \beta_2 x_1 + \beta_3 x_0^2 + \beta_4 x_0 x_1 + \beta_5 x_1^2 + \beta_6 x_0^3 + \beta_7 x_0^2 x_1 + \beta_8 x_0 x_1^2 + \beta_9 x_1^3$.
If combinations=False, it calculates $y = \beta_0 + \beta_1 x_0 + \beta_2 x_1 + \beta_3 x_0^2 + \beta_4 x_1^2 + \beta_5 x_0^3 + \beta_6 x_1^3$.
Keep in mind, this is not tested. I just provide it as a starting point for people as a starting point. Also, this should not work for higher output dimensions ($y_0, y_1$)

I'm not particularly enthusiastic about expanding the list of Models. The ones there are mostly for demonstrating the (unnecessarily complicated) Model infrastructure rather than being a comprehensive library of such. If (hopefully when) ODR gets reimplemented in scipy.optimize, it would follow scipy.optimize conventions and not have a library of models (there being no real infrastructure to demonstrate).
This would make a great blog post, though! Good work getting all that machinery to handle the generic case!


Process closures properly in Eloquent Collection::contains()

Only call find() when $key is not a callable.

In response to #7596 .
Do we have anything for or against using is_callable() and the callable typehint?


Removed mention of a version so old that nobody should be concerned.

The doc has many sentences starting by

Since Cython 0.xxxxx

or

Since version 0.xxxxx

I think the ones that are too old are not useful for the readers. I would like too remove all mentions of Cython versions below 0.xxx but I don't know what this xxx should be.
Any idea?

I guess it's mostly a decision on a case by case basis, but even 0.23 is 3 years old by now. I'd definitely drop any mention of older versions than that.


Staking not working or super slow with QRC 20 version?

This issue tracker is only for technical issues related to Qtum.
Describe the issue
since I upgraded to QRC 20 version of wallet, it was never able to get any reward for staking. Even tho it shows its staking and 90 other nodes connected to my node with 82 incoming and 8 outgoing. The approximate days to get reward is extremely variable and its been running since last 12 days with weight 1747? Any thoughts what to do to improve?
Can you reliably reproduce the issue?
If so, please list the steps to reproduce below:

Expected behaviour
Tell us what should happen
Actual behaviour
Tell us what happens instead
Screenshots.
If the issue is related to the GUI, screenshots can be added to this issue via drag & drop.
What version of Qtum are you using?
List the version number/commit ID
Machine specs:

OS: Win2012 r2
CPU: intrl cor i5 4 core
RAM: 16 gb
Disk size:

Any extra information that might be useful in the debugging process.
This is normally the contents of a debug.log or config.log file. Raw text or a link to a pastebin type site are preferred.

Staking is always up to chance and network conditions. A notable number of people have dry-spells where they can go 2-3x as much time as the "expected time". In addition, when there are more people staking, you are less likely to stake a block and your expected time decreases. If you are having problems with never getting a block, then you should make sure that your wallet is unlocked for staking.

understood..thanks for the reply. I had few blocks. Yesterday I noticed got .40 reward but just to mature that it took 2/3 of my stake offline and was only staking with few. Is there any way to tweak that or not necessary ?


Test  rocket

What does this PR do?
This PR is raised to implement the following features: 👍 :

[x] Add the test for the rocket and the header👌
[x] Use the react testing library for the testing⤵
[x] Use the jest to test the piece of the code of the component
[x] Use the snapshot for testing the component by the renderer💯

Description of the task to be completed 👎

[x] Add the test for the rocket and the header👌
[x] Use the react testing library for the testing⤵
[x] Use the jest to test the piece of the code of the component

How should it be tested
Clone the repository
git clone https://github.com/osamaashraf6/Space-X-React-Group

Navigate to the folder
cd Space-X-React-Group

Checkout the branch

git checkout test__rocket

#### Thanks for reviewing my PR 😊

Thanks @momotsow 🙏 for reviewing my pull request I appreciate your review I will work on this part to enhance my code thanks for advising me 👌 💯

Thanks again for reviewing my PR  and have a good day😊

Thanks @momotsow 🙏 for reviewing my pull request I appreciate your review 💯

Thanks again for reviewing my PR  and have a good day😊


#322 Deserializing applicationmetadata keeps unmapped properties

Description
Fixes #322
Related Issue(s)

#322

Verification

[x] Your code builds clean without any errors or warnings
[x] Manual testing done (required)
[x] Relevant automated test added (if you find this hard, leave it and we'll help out)
[x] All tests run green

Documentation

[x] User documentation is updated with a separate linked PR in altinn-studio-docs. (if applicable)

If we need to support newtonsoft json, there should probably be a test for it.
Also, the important thing to test here is the round trip deserialization - serialization. I don’t think we actually care much about accessing unknown properties through the dictionary.

If we need to support newtonsoft json, there should probably be a test for it.
Also, the important thing to test here is the round trip deserialization - serialization. I don’t think we actually care much about accessing unknown properties through the dictionary.

While trying to create tests for newtonsoft I realised that supporting newtonsoft would result in a different json returned if serializing with system.text and deserializing with newtonsoft (JsonElement vs JToken) as we still plan to remove Newtonsoft in favor of System.Text I don't think it is worth the effort to support both


Make goto, reload, goback and forward to use doActionAwaitingNavigation

Cleanup waiting for navigation logic in two places. Currently goto, reload, goback and forward uses different logic and other actions use  doActionAwaitingNavigation make both use the same and provide option to wait for custom events for other actions too.

Should be fixed in 26858ab.

Things to test:
APIs :  goto, reload, goBack, goForward and openTab
Also all APIs can now wait for custom events. So that can be tested.

Required api has been tested and found fixed with the version 9a876b8


EXSWHTEC-358 - Implement tests for 2D mipmapped texture device functions

tex2DLod
tex2DLayeredLod
tex2DGrad
tex2DLayeredGrad.

Depends-on: #367

PR has been merged into develop branch via commit 90a783c959172aa3887876aa6ac99b5744d2c6a2.


Gemspec: Drop EOL'd property rubyforge_project

The RubyGems property rubyforge_project is removed without a replacement.

Thanks 👍


 I would like to be able to package everything that I need to display my animations when I build my site so that when the user is offline, my web app still works.

Rive uses standard http to download its Wasm runtime and Rive file(s). The browser will typically cache these assets, but re-opening or refreshing the browser will obviously cause things to break.
To have a real offline experience through a browser, you might want to look at service workers where you can handle downloading and then caching any assets your web page uses.

Oh interesting. I downloaded the RIV file as an asset locally and I have caching set up. I thought about setting up a service worker but it would be great to support offline Rive animations without them (so long as I have all the right components cached on the device).
Thanks for the fast reply! Super cool project :)
Justin
On Mar 25, 2021, 10:10 PM -0700, Matt Sullivan @.***>, wrote:

Rive uses standard http to download its Wasm runtime and Rive file(s). The browser will typically cache these assets, but re-opening or refreshing the browser will obviously cause things to break.
To have a real offline experience through a browser, you might want to look at service workers where you can handle downloading and then caching any assets your web page uses.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

 Note that the library uses Wasm under the hood, so you'll need to check that rive.wasm (https://unpkg.com/rive-js/dist/rive.wasm) is also being cached.
We have a pure (i.e. non-wasm) version of the js, but haven't put that up on npm (yet); it adds a bit of additional size to the overall download.

@mjohnsullivan do you know if using the setWasmUrl() to use a locally hosted version of the wasm file will work in an offline scenario?


[Bug]: When using beam.io.kinesis.ReadDataFromKinesis, a java error is raised in DataFlowRunner

What happened?
"Error message from worker: generic::unknown: org.apache.beam.sdk.util.UserCodeException: java.lang.NullPointerException: Cannot invoke "org.apache.beam.sdk.io.kinesis.ShardReadersPool.getLatestRecordTimestamp()" because "this.shardReadersPool" is null
org.apache.beam.sdk.util.UserCodeException.wrap(UserCodeException.java:39)
org.apache.beam.sdk.io.Read$UnboundedSourceAsSDFWrapperFn$DoFnInvoker.invokeSplitRestriction(Unknown Source)
org.apache.beam.fn.harness.FnApiDoFnRunner.processElementForSplitRestriction(FnApiDoFnRunner.java:887)
org.apache.beam.fn.harness.data.PCollectionConsumerRegistry$MetricTrackingFnDataReceiver.accept(PCollectionConsumerRegistry.java:313)
org.apache.beam.fn.harness.data.PCollectionConsumerRegistry$MetricTrackingFnDataReceiver.accept(PCollectionConsumerRegistry.java:245)
org.apache.beam.fn.harness.FnApiDoFnRunner.outputTo(FnApiDoFnRunner.java:1788)
org.apache.beam.fn.harness.FnApiDoFnRunner.processElementForPairWithRestriction(FnApiDoFnRunner.java:824)
org.apache.beam.fn.harness.data.PCollectionConsumerRegistry$MetricTrackingFnDataReceiver.accept(PCollectionConsumerRegistry.java:313)
org.apache.beam.fn.harness.data.PCollectionConsumerRegistry$MetricTrackingFnDataReceiver.accept(PCollectionConsumerRegistry.java:245)
org.apache.beam.fn.harness.FnApiDoFnRunner.outputTo(FnApiDoFnRunner.java:1788)
org.apache.beam.fn.harness.FnApiDoFnRunner.access$3000(FnApiDoFnRunner.java:142)
org.apache.beam.fn.harness.FnApiDoFnRunner$NonWindowObservingProcessBundleContext.output(FnApiDoFnRunner.java:2506)
org.apache.beam.sdk.io.Read$OutputSingleSource.processElement(Read.java:1034)
org.apache.beam.sdk.io.Read$OutputSingleSource$DoFnInvoker.invokeProcessElement(Unknown Source)
org.apache.beam.fn.harness.FnApiDoFnRunner.processElementForParDo(FnApiDoFnRunner.java:799)
org.apache.beam.fn.harness.data.PCollectionConsumerRegistry$MetricTrackingFnDataReceiver.accept(PCollectionConsumerRegistry.java:313)
org.apache.beam.fn.harness.data.PCollectionConsumerRegistry$MetricTrackingFnDataReceiver.accept(PCollectionConsumerRegistry.java:245)
org.apache.beam.fn.harness.BeamFnDataReadRunner.forwardElementToConsumer(BeamFnDataReadRunner.java:213)
org.apache.beam.sdk.fn.data.BeamFnDataInboundObserver.multiplexElements(BeamFnDataInboundObserver.java:158)
org.apache.beam.fn.harness.control.ProcessBundleHandler.processBundle(ProcessBundleHandler.java:537)
org.apache.beam.fn.harness.control.BeamFnControlClient.delegateOnInstructionRequestType(BeamFnControlClient.java:151)
org.apache.beam.fn.harness.control.BeamFnControlClient$InboundObserver.lambda$onNext$0(BeamFnControlClient.java:116)
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
org.apache.beam.sdk.util.UnboundedScheduledExecutorService$ScheduledFutureTask.run(UnboundedScheduledExecutorService.java:163)
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
java.base/java.lang.Thread.run(Thread.java:833)
Caused by: java.lang.NullPointerException: Cannot invoke "org.apache.beam.sdk.io.kinesis.ShardReadersPool.getLatestRecordTimestamp()" because "this.shardReadersPool" is null
org.apache.beam.sdk.io.kinesis.KinesisReader.getSplitBacklogBytes(KinesisReader.java:172)
org.apache.beam.sdk.io.Read$UnboundedSourceAsSDFWrapperFn$UnboundedSourceAsSDFRestrictionTracker.getProgress(Read.java:999)
org.apache.beam.sdk.transforms.reflect.ByteBuddyDoFnInvokerFactory$DefaultGetSize.invokeGetSize(ByteBuddyDoFnInvokerFactory.java:432)
org.apache.beam.sdk.io.Read$UnboundedSourceAsSDFWrapperFn$DoFnInvoker.invokeGetSize(Unknown Source)
org.apache.beam.fn.harness.FnApiDoFnRunner$SizedRestrictionNonWindowObservingProcessBundleContext.output(FnApiDoFnRunner.java:2415)
org.apache.beam.sdk.io.Read$UnboundedSourceAsSDFWrapperFn.splitRestriction(Read.java:540)
Issue Priority
Priority: 3 (minor)
Issue Components

[X] Component: Python SDK
[ ] Component: Java SDK
[ ] Component: Go SDK
[ ] Component: Typescript SDK
[X] Component: IO connector
[ ] Component: Beam examples
[ ] Component: Beam playground
[ ] Component: Beam katas
[ ] Component: Website
[ ] Component: Spark Runner
[ ] Component: Flink Runner
[ ] Component: Samza Runner
[ ] Component: Twister2 Runner
[ ] Component: Hazelcast Jet Runner
[X] Component: Google Cloud Dataflow Runner

Hello @vishwesh0409, what was the fix that was applied for this ? Tried to look for it but did not find it

Hello @vishwesh0409, what was the fix that was applied for this ? Tried to look for it but did not find it

I'll reopen this. I thought it was fixed by #26953 but after updating the beam version to 2.49.0, I'm getting the same problem.

Hello @vishwesh0409, what was the fix that was applied for this ? Tried to look for it but did not find it

I'll reopen this. I thought it was fixed by #26953 but after updating the beam version to 2.49.0, I'm getting the same problem.

Yep, also tested this in the current master branch status and getting the same error when running a test job locally so def an issue IMO

also @vishwesh0409, if I implement that, fix myself in my copy of mater, and then rerun the job then it does not fail anymore however when running on DirectRunner on my laptop no data are read when using InitialPositionInStream.TRIM_HORIZON and after verifying there are data in the Kinesis Stream, am I doing something wrong there?

ok I am gonna structure my thought a little bit better here :)
So there are 2 KinesisReader.java around, one v1 and one v2, and as far as I can tell KinesisTransformRegistrar.java used to map the Python interface to the source Java package is relying on the v1 one.
https://github.com/apache/beam/pull/26953 fixed the issues in the KinesisReader.java v2 but not in the v1 and as a test I myself cloned master and applied the same fix on the v1 files and after that, the job runs without error.
I do encounter another issue though which is then when running on my laptop using the DirectRunner nothing happens when it comes to reading data even if I have data in the source stream and I am using the option InitialPositionInStream.TRIM_HORIZON, so the job runs but no data are read.
I also tried to make the KinesisTransformRegistrar.java` point to v2 as the job does get deprecation warnings as v1 seems to be deprecated but my understanding of the project is not enough to make it work right now (plus my Java is a bit rusty 😓 ).

Looks like the KinesisReader modules are not properly fixed yet. I observed the same deprication warnings when I tried to run my code on Google Cloud. It should be a simple enough fix tho.

Basically, there is a need to develop a new KinesisTransformRegistrar.java based on the aws2 kinesis package instead of the current one and expose a new python transform URN which would be v2, hopefully that should enable the python flow to work as expected with the latest modules

2.50 release manager here.
This issue is currently tagged for the 2.50.0 release, which cuts in a week on August 9th.
Please complete work and get it into the main branch in that time, or move this issue to the 2.51 Milestone: https://github.com/apache/beam/milestone/15

this was due to issue get reopened and the milestone not removed

@Abacn  @lostluck but then if an issue is open and neither who opened it nor who is participating in the discussion has the knowledge to fix it will the issue be forgotten or someone in the community will pick it up?
Just trying to understand if there will be any resolution to this or if it will just stick around

As an open source project, the primary means of fixes is via community and user involvement. As a rule, no one can expect someone else to fix an issue just because it's filed.
The story changes somewhat if judged to be  a P1 or P0, a regression from the previous release version, or if it's affecting a large Dataflow customer, at which point it's likely that someone from the Dataflow team will drive it yo resolution. That does require the customer to have a GCP support ticket in place as well.
P3s are typically not release blockers, so it's more likely this remains in the backlog until someone motivated to fix it it comes along. Beam welcomes contributions.

This issue seems to also affect FlinkRunner.

@mxm it should affect all runners since the issue is at source code level, the core issue I tried to explain in more details here https://github.com/apache/beam/issues/27165#issuecomment-1644183789

The same issue on my side.


add links and tables with test results in releases.md files

Signed-off-by: Kamil Pokornicki<EMAIL_ADDRESS>

@Pokisiekk I talked with @miczyg1. For this time we only add links to the test results spreadsheets - files releases.md are generated automatically so it would be better to improve the generator than add test results manually.


Upgrade Coda to v2.5.12

Thank you for the contribution. It was merged directly as 982c47712b66dd8ef1ea664203b87eef6e97ce0c to keep commit history cleaner. Your contribution is still credited to you.


General performance, and other things

High ram consumption:
During pictures scan, gallery has a very high ram consumption (500mb - 1gb), I think this bug only happens in scan of a lot of files, my 20000 pictures and 40 albums generated the problem environment, I think.

App stability:
General app performance is not good if you have 20000+ pictures and 40 albums.

Albums names text:
I'm facing pixelify problems in some albums names text, I can see pixels of name texts, and looks ugly.

In general:
App need to be optimized and improve to support very big content of pictures and albums

Please read this before opening issues.

High ram consumption
Unless the app crashes, it's not an issue.

App stability
Unactionable

Albums names text
Screenshot please

In general
Unactionable


Get-AzureStorageTableRowByPartitionKeyRowKey was added including test

Added another pre-defined filter to get one row based on partition key and row key
I added also an unit test (comment out as all others) to check my changes.

Cool ! Thanks


Enhancement: Keep plugins selected for a particular chat

What features would you like to see added?
When I start a chat with a particular set of plugins and later revisit this chat, I suggest the same set of plugins are still selected.
More details
./.
Which components are impacted by your request?
UI
Pictures
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

I agree this is a long-time coming


Default config.files.src should be an array

When attempting to pass an array of globs to the pipeline, I get an error:
events.js:154
      throw er; // Unhandled 'error' event
      ^
Error: streams not supported

Process finished with exit code 1

I was able to determine that this was because the default config.files.src is a simple string, while I'm passing an array. When the pipeline attempts to merge the config objects, it fails. By making the default file path a single item array, I was able to run the pipeline successfully.

@paul-barry-kenzan do you see this is as a bug or an enhancement?  If you submit a PR, i can get this published ASAP for you

It's a bug. I can't use this without making the default an array. PR on its way.

Awesome, thanks!


feat(resolver): expose raw package_json value; improve print debug

This is for integrating with Rspack.

Codecov Report
Patch coverage: 22.50% and project coverage change: -0.07% :warning:

Comparison is base (99a7ad4) 92.14% compared to head (4c59546) 92.07%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #738      +/-   ##
==========================================
- Coverage   92.14%   92.07%   -0.07%
==========================================
  Files         198      198
  Lines       40310    40344      +34
==========================================
+ Hits        37143    37147       +4
- Misses       3167     3197      +30

Files Changed
Coverage Δ

crates/oxc_resolver/src/cache.rs
95.19% <0.00%> (-2.83%)
:arrow_down:

crates/oxc_resolver/src/resolution.rs
72.00% <6.66%> (-25.23%)
:arrow_down:

crates/oxc_resolver/src/package_json.rs
91.74% <25.00%> (-2.55%)
:arrow_down:

crates/oxc_resolver/src/lib.rs
92.11% <35.29%> (-1.26%)
:arrow_down:

crates/oxc_resolver/src/options.rs
86.33% <100.00%> (ø)

... and 1 file with indirect coverage changes

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


Make auto-advance flag a requirement for conditional/expression evaluation

This is a PR to address a potential major design discontinuity with Godot's StateMachine system. This has been bothering me for a while, and I believe I understand why certain aspects of AnimationStateMachine's feel so counter-inuitive. I feel it is a consequence of two distinct ways of traversing them: via travel or via auto-advance/conditions. With travel, conditions are actually ignored, and it is a regular A* traversal to simply get to a desired node, whereas auto-advance can use conditional branch to have a state machine essentially drive itself.
The problem I feel with the current implementation is that you have mainly three types of transitions:

No auto-advance and no condition: does nothing on its own
No auto-advance but has conditions: advances but if conditions are met
Auto-advance: ignores all conditions and advances regardless

My problem is that auto-advance more or less overwrites the behaviour conditions, and this feels very strange from a usability standpoint. It essentially makes the it an either/or scenario, and the relationship between these two elements is not obvious. My proposal therefore is to make it so that for any automatic traversal, auto-advance must always be on, and conditional evaluation is only done if auto-advance is set. While this PR only changes the actual behaviour and documentation to provide better explanation, I think more could be done on the editor side to make the relationship between the two more obvious. I could also supplement this with features such as allowing you to set the default state of auto-advance on new transitions in the same way you can for switch mode.
I feel strongly on the whole that short of removing auto-advance entirely (which doesn't feel fair given not having auto-advance active can make it useful for the 'travel' method), this is the best way to address a pretty glaring design issue, and it feels relevant to address this given the potential that a lot of game logic can be implemented purely via state machines.

Added a new auto-advance toggle button next to the transition switch mode for creating new transitions. Feels important to do for the sake of workflow speed, though I do wonder if there's ways we could make the functionality more obvious.

I went and added the context-sensitive behaviour anyway. I could really see a reason not to do it given the way the state machine editor currently uses, and feel like it will make it easier for people to understand how it works.

@TokageItLab what do you think?

Does this PR solve this issue?
https://github.com/godotengine/godot-proposals/issues/2200

@TokageItLab It doesn't, but I've started experimenting with transition interrupts as part of major evaluation of state machine usability. I'm hoping I can add that as a new feature soon, along with more granular support of the exact timing of when transitions should occur.

I think I recall we discussed using an enum for this, what happened in the end?

Animation meeting: change to use an enum, maybe add disable. @SaracenOne wants to get this done in the next few days.

Thanks!


How you have trained the LID model

Can you share your LID training recipe and data preparation guide?

Yes, sure. It's not a secret. I used https://github.com/kaldi-asr/kaldi/blob/master/egs/sre16/v2/run.sh. In utt2spk file I used utt_id lang instead of utt_id speaker

Thanks, and to use the trained model with your vosk modified src what's the model structure?

You can find it here https://github.com/igorsitdikov/lid_kaldi/releases/tag/1.0.0

Thanks for the quick response. Also, I have a question about training. How much data do you recommend for each language? also is it necessary to have an even distribution of data volume for each language?

https://arxiv.org/abs/2011.12998


Default font-feature-settings

Feature Proposal
I would like have a defaultFontFeatureSetting option available for ChartJS
Feature Use Case
Right now it is possible to set defaultFontColor, defaultFontFamily, defaultFontSize, and defaultFontStyle to style fonts used within the canvas, but font-feature-settings is missing. This is an important setting to have to ensure font consistency between the chart and page if it used in the rest of the page.
Possible Implementation
I am unsure if this can be added with a plugin, but I think that it would make sense to expose as a global font setting. I know that this is less likely to be used than the other options, but I think it is very important in the cases it is needed.

@valtism thanks for raising this. How are you using the font-feature-settings in your app? The canvas font features are rather limited and a quick google seemed to confirm my initial thought which was that this isn’t possible. I may have alternatives though depending on your use case.

Ah, I didn't realise that canvas has limitations on font features.
My use case is that we are using IMB Plex Mono, which by default has 0s with dots in the middle. We apply font-feature-settings: 'ss04' to render our mono font 0s without dots, and were hoping to do the same for our charts.
That said, based off this it doesn't look doable. https://github.com/whatwg/html/issues/3571

Closing per the above discussion since this isn't possible with the canvas at this time


Stroke issues in figma

Hey there,
The icons looks okay on web, but when we open them in Figma, they look like this.

Hey @fayazara, try this: https://figma.com/file/vfjBXrSSOCgmVEX5fdvV4L. I cleaned them up myself for this every reason.

Pretty sure the SVG optimization breaks Figma.


Content Suggestion: Reggio Emilia Meetup

Link to Content: https://twitter.com/tierotiero/status/1176778406568058882?s=19
Briefly Describe Content: Reggio Emilia, Italy
Suggested Section: meetups

[Added[(https://github.com/bitcoin-only/bitcoin-only/commit/1887a6046f8d37b13dea446b72fecf5a6f61604f)


Cannot change NodePort values in UI

What kind of request is this (question/bug/enhancement/feature request):
Bug
Steps to reproduce (least amount of steps as possible):
Flow 1:

Tools --> Istio or
Expand "Ingress Gateway" and try to change the http2 and https ports.
Flow 2:
Workloads --> Deploy
Add Port, as a NodePort
Click "Random" and type any value

Result:
It uses the min/max values of the input field no matter what is typed (30000 or 32767) and cannot clear the field.
Other details that may be helpful:
Potential Workaround: should be able to enable w/ some value and then edit the istio app via api to change the port in the answers
Note that with UI Index https://releases.rancher.com/ui/2.3.26/index.html it allows clearing the field.
Example from deploying workload:

Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI):
master-head
UI Index: https://releases.rancher.com/ui/latest2/index.html
Installation option (single install/HA):
single

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported):
rke ec2: 1 t2.medium etcd + cp and 3 t2.xlarge workers
Kubernetes version (use kubectl version):

1.16.3

Docker version (use docker version):

1.10.3

Does it affect only "Edit Workload" or also Services from "Service Discovery" menu?

Good call out, it does not happen in the Service Discovery menu. It also looks like the min value of the field there is 1 instead of 30000.

Fixed in master-head commit id: 8bd9f3be2 using ui-index https://releases.rancher.com/ui/latest2/index.html
Can edit NodePort values on both Workload creation and Tools > Istio.


Chrome for Android get Error when danmaku api crash

OS: Android 5.0.2
Browser: Chrome Dev 60.0.3087.3
demo

Maybe it is Chrome Dev 60.0.3087.3 's Bug

find a jad酱！！
did you considerate  add  danmaku  function for imjad api  ?  i'm very  looking forward to it!!
hope DIYgod  don't mind - -!

ps. redmi 4x chrome 58.0.3029  also have this problem in your demo


Parallelizing track retriangulation

Is there any technical reason preventing this section of the code from being parallelized? The retriangulation / bundle adjustment loop takes a lot of time in my tests. Specifically the retriangulation section.
https://github.com/colmap/glomap/blob/4210f9392567c4f38dfd1300db0126b69606fc0e/glomap/controllers/track_retriangulation.cc#L62-L70

Yes, the current implementation of the underlying data structures of the reconstruction are not thread safe. Triangulating the observations in one image may affect the observations in other images.

I see, thank you for your responses. I try running glomap on videos, and on some of these videos the retrinagulation steps takes more than 75% of the time. Do you think it's worthwhile for me to look into it, or is there something fundamental preventing it.


error when training sample does not contain all labels

I am doing n-fold CV over my training set, so suppose if my training dataset in a fold does not all the labels, then i get an error
self._train_seq[self._train_phase][1](*args, **kwargs)
File "pyStruct_crf_node.py", line 30, in _stop_training
self.ssvm.fit(self.X_train,self.y_train)
File "/usr/local/lib/python2.7/dist-packages/pystruct/learners/frankwolfe_ssvm.py", line 288, in fit
self.model.initialize(X, Y)
File "/usr/local/lib/python2.7/dist-packages/pystruct/models/chain_crf.py", line 75, in initialize
% (self.n_states, n_states))
ValueError: Expected 36 states, got 29
Why it is necessary to have all the labels for the training? What if change 'initialize=False' in the fit method?
My code is as follows:-
model = ChainCRF(n_states=classes)
ssvm = FrankWolfeSSVM(model=model, C=.1, max_iter=10)
ssvm.fit(x_train,y_train)

yeah that's kind of expected but should be fixed. thanks for pointing it out.

Any solution？ I got this problem too