[FLINK-34511] Remove legacy State&Checkpointing&Recovery options

What is the purpose of the change
Removes the deprecated State&Checkpointing&Recovery related options
Brief change log
Several commits:

Remove force checkpointing flag
Remove deprecated ExternalizedCheckpointCleanup
Remove deprecated ExecutionCheckpointingOptions
Remove deprecated SavepointConfigOptions
Cleanup CheckpointConfig
Cleanup deprecated APIs in rocksdb state backend

Verifying this change
This change is already covered by existing tests
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): yes
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? no
If yes, how is the feature documented? docs and JavaDocs

@flinkbot run azure

@fredia @masteryhx Would you please take a look?

@flinkbot run azure

Thanks for the review! The CI green, merging...


X-Ray segment longer than lambda function execution time

We have a serverless typescript lambda function which makes API calls to other APIs.
We are using the aws-xray-sdk to instrument downstream API calls that are made with axios.
Currently using version 3.3.3 of the SDK.
We are seeing the execution time of those downstream API calls as  substantially higher that the actual lambda function execution time and the downstream APIs does not see a lambda execution time corresponding to this execution time.
In the example below the API call is listed as 1.06 seconds execution time but the function only executed for 275ms.
What could be causing this discrepancy?

Cloudwatch log message also show 269 ms execution time.
REPORT RequestId: 1bd3866d-a4ff-4d12-9e42-8fddc98853a4	Duration: 268.37 ms	Billed Duration: 269 ms	Memory Size: 512 MB	Max Memory Used: 138 MB
XRAY TraceId: 1-6163f603-7b02f3fd233c022a431a11d1	SegmentId: 6c8548f51f835b8b	Sampled: true

Code snippets for the implementation of tracing.
import express from 'express';
import AWSXRay from 'aws-xray-sdk';
import { AxiosRequestConfig } from 'axios';

import Redis from '@libs/cache/cache';
import InstrumentedCache from '@libs/cache/instrumentedCache';
import serverlessExpress from '@vendia/serverless-express';

const http = require('http');
const https = require('https');

AWSXRay.captureHTTPsGlobal(http, false);
AWSXRay.captureHTTPsGlobal(https, false);
AWSXRay.capturePromise();

const axiosConfig: AxiosRequestConfig = {
  httpAgent: new http.Agent(),
  httpsAgent: new https.Agent(),
};

app.use(AWSXRay.express.openSegment('mc-moderation-api'));
app.use(connectToCache(instrumentedRedis));
app.use(disconnectFromCache(instrumentedRedis));
app.use('/', router);
app.disable('x-powered-by');
app.use(AWSXRay.express.closeSegment());
app.use(unknownRouteHandler);
app.use(unexpectedErrorHandler);

Hi @RealityCtrl
I'm not very familiar with axios but it seems like it's an async HTPP client. I'm guessing what's happening here is that your async request is taking probably taking 1.06s to complete but in the meantime the execution moves forward and the lambda segment is closed before that async request completes and the corresponding subsegment is emitted later on.
But I'm also confused by the fact that even if the HTTP request is taking that long, once the lambda finishes execution in 269ms, this subsegment shouldn't be emitted after the function terminates.
I'll let @willarmiros take a stab at this one since he may have more idea.

Hi @RealityCtrl,
The only explanation I can think of is that somehow the Lambda function is completing its invocation and being frozen before the subsegments are closed, causing them to be closed during the next invocation and reflect a time longer than the function invocation. It will be very difficult to investigate further without code reproducing the issue, and I know these production Lambda issues tend to be very difficult to reproduce.
I would also recommend trying out the AWS Distro for OpenTelemetry JavaScript Lambda layer, it can auto-instrument your downstream requests & send trace data to X-Ray without modifying your code. Maybe the issue won't appear with that.

I can report that I am experiencing the same issues in on of our environments. Is there any plan to look further into this issue? We are using aws-xray-skd 3.6.0.
I will check out if we can change to OpenTelemetry, but I still would expect that an issue like this deserves a fix in a library like this.


Overlapping text in options popup

Describe the bug
Overlapping text in options popup
To Reproduce
Steps to reproduce the behavior:

Go to options
Change platformUrl
See screenshot

Expected behavior
A readable warning text.
Screenshots

Environment (please complete the following information):
v2.2.1

Legacy (wont fix)


Create Extensive Initial Documentation

Someone has to write the initial documentation on https://wiki.pamaxie.com. I will do it if nobody else feels willing to do it.

Document the current data structure the API uses


When pressing shift+drag, it takes 1 second before a zone is highlighted

Not sure if this is a bug or feature, but I find it annoying:
When I hold shift and mouse click, the zone overlay will show immediately when I start moving the window, but the zone highlighting will delay at least 1 second. I want it to instantly hightlight the zone the cursor is in when I start moving the window.
Edit: I have 3 monitors. I noticed now that it first show the overlay on monitor 1, then montor 2, then monitor 3, and then it highlights the current zone.
In other words, all these UI drawings are done in succession, and each takes about 0,5 seconds.

I agree, it should definitely not have a delay, or at least that long of a delay.

I'm also experiencing my computer semi freezes for 1s before they appear

I think this is a "performance issue": I have 3 monitors. I noticed now that it first show the overlay on monitor 1, then montor 2, then monitor 3, and then it highlights the current zone.
In other words, all these UI drawings are done in succession, and each takes about 0,5 seconds.

I'm experiencing it on my laptop, without any monitors connected.
On Fri, May 29, 2020, 15:28 GeeZuZz<EMAIL_ADDRESS>wrote:

I think this is a "performance issue": I have 3 monitors. I noticed now
that it first show the overlay on monitor 1, then montor 2, then monitor 3,
and then it highlights the current zone.
In other words, all these UI drawings are done in succession, and each
takes about 0,5 seconds.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/PowerToys/issues/3856#issuecomment-635972556,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AD22EOS4GZPUTFZSOUU3H5TRT62AZANCNFSM4NN5X6JQ
.

I also think it's a performance issue, probable related to your hardware.  Maybe you can give us some number on those?
For example, right now I am using a Surface Pro 4 (Intel i5 @ 2.40 or 2.50 GHz, 8 GB RAM) and it works without any problem.
Also have two other pc's, but imma have to get back on the numbers for you.

When I wrote "performance issue", i meant code, not hardware. While I don't have top of the line hardware, it should definitely be able to perform this faster...
It's a desktop PC, AMD 8320 @ 3.79Ghz with 11/16GB RAM in use. GPU is Radeon RX550.

I have a laptop and a external monitor connected.
The zone's are never shown on my laptop screen, only on the external. this is not really a problem for me, because I only need the zones on my (large) external screen. I also had this freezing problem, I solved it by disabling the "Show zones on all monitors while dragging a window". So it has probably something to do with multiple screens.

This issue is fixed for me in the latest version.


Prepare CallBacks

[x] Update Config.yaml
[x] research or analysis
[x] Update Entitity
[x] Update Configuration Manager in src Config
[x] Update Component
[x] Update the Pipeline

Completed


Support branchPolicy regex with mutually exclusive capture groups

The following regex has two mutually-exclusive capture groups
<pattern>(?:hotfix|feature)/(?:(\w{3,}-[0-9]+).*|(.*))</pattern>

This matches either of

feature/TICKET-123_description > (TICKET-123, null)
feature/description > (null, description)

1.7.1 fails this on the second case because group(1) is null.
Workaround is to have two carefully-ordered branchPolicies with the same transformations (which is a DRY fail)

the pattern supports only one capturing group.
can't you reverse the capturing/non-capturing ?  with ( (?:xxx) | (?:yyy) )

Wonderful idea but only works where the content is a full match.
(?:hotfix|feature)/((?:\w{3,}-[0-9]+).*|(?:.*))
                                     ^^

This no longer extracts the ticket because the trailing part is part of the capture

:x: feature/TICKET-123_description > TICKET-123_description

The ask is that the pattern supports one non-null capture-group. My example was specifically crafted to be exclusively one or the other.

we should investigate how breaking/compatible it would be to enhance the rule from "1 capturing group" to "first non null/not empty capturing group"

Should be fine because it isn't an enforced rule! The provided pattern has two groups and works just fine in the TICKET case.
The current rule takes group(1) without checking for others. If group(1) is null, the tool fails. Hence, all existing users have a working group(1) and this change is as extension not change to that support


Fix instructions for filtering tests on Windows

In the command nmake TEST='foo' test, on Windows the runner will look for test 'foo' and complain about the test not being found (due to the extraneous single quotes), whereas with nmake TEST="foo" test, the test foo will be correctly found
CLA: trivial

oops, sorry, yes, okay with trivial

24 hours has passed since 'approval: done' was set, but as this PR has been updated in that time the label 'approval: ready to merge' is not being automatically set.  Please review the updates and set the label manually.

Agreed, it's trivial.

As this is a doc fix, I am applying this to all 3.x branches.

Merged to the master, 3.2, 3.1, and 3.0 branches. Thank you for your contribution.


Add skeleton classes based on the design doc.

The methods are mostly no-ops.

This is an updated version of #27 - I think I addressed most/all of the comments from there (copyrights, comments, grouping methods, etc).  I also updated everything to what's in the current design doc and removed the "dummy" method implementations in favor of having them return empty/unimplemented.
I have a .cc file i was using to make sure this compiled and linked, but it's not really worth checking in... I should work on a proper example though.

Thanks, Todd.
First a general question.
I have a mild concern about adding skeleton code en mass based on the very rough sketch code from jgm.cc. That code was written quickly, with only enough thought or care to make it compile (probably with warnings). Its only goal was to give us some way to quickly experiment with and decide between various possible API choices. I think every line of that sketch code needs to be reconsidered and likely rewritten with intentional engineering. I'm hesitant to start with any of that sketch code in the code base for fear that it may accidentally live on.
We filed separate issues to implement the basics for each of the classes described in the design doc. The intent was to thoughtfully translate the abstractions from the design doc into properly written, well engineered code with unit tests. The "skeleton" part of that is that each abstraction need not be perfect or complete on the first PR, just some of the basic parts and a unit test.
So we could either tackle these abstractions one at a time, handling and closing the filed GH issues. Or would could do a more bulk laying down of skeleton code as in this PR. I was thinking we'd be doing the former. Do you think it's better to do the latter? Or some other option that I've missed?

ok, after chatting with Greg, I'm going to abandon this - we should (collectively) split it into smaller and more fleshed out chunks.


getPaymentInfo regression

It looks like the result of the API call details_for is returned as part of the getPaymentInfo, causing failed payments to be returned as PROCESSED (i.e. success) by the plugin.

It looks like this was caused by https://github.com/killbill/killbill-paypal-express-plugin/pull/18.

Fixed by https://github.com/killbill/killbill-paypal-express-plugin/pull/27.


Automatic recovery (salvage) from faulted volume due to the engine in the isolated network

If a network split happens, the engine might declare all the replicas error thus volume faulted. In this case, we require user to perform salvage operation to repair the volume.
But once the network connection restored, we might able to help the user to recover the volume automatically.

Validation: PASSED
Test case 1:

A pod is running and using Longhorn volume.
Stop all the replicas of the longhorn volume at the SAME time.

Expect result:

Volume recovers by itself.  (PASS)
Pod recovers by itself. (PASS)

Test case 2:

A pod is running and using Longhorn volume.
Stop one replica.
Wait for 30 seconds.
Stop all the other replicas

Expect result: Same as test case 1  (PASS)

Test case 3:

A pod is running and using Longhorn volume.
Stop one replica.
Wait for 2 minutes.
Stop all the other replicas

Expect result: Same as test case 1: The first stopped replica should remain in the Error state.  (PASS)

Test case 4

A pod is running and using Longhorn volume.
Stop the node network connection to other nodes to simulate a network outage.
Resume network connection after 1 minute

Expect result: Same as test case 1.  (PASS)

@yasker I have recently installed 0.8.0 and noted that a fault seems to have been recovered well from the longhorn side however on the pod side i see that where the volume is mounted when i try to do an "ls" i get "ls: reading directory .: Input/output error".
This leads me to think that either something must be made on the pod to reattach the volume properly or the pod restarted. Is this known or a bug ?

@gittygoo you're right, pod needs to be restarted to use the reattached volume. You can setup liveness probe on pod for that. See https://longhorn.io/docs/users-guide/recover-volume/


Mark overlayContainer and overlayContainerStopEvent as non-nullable

And remove an unnecessary cast

Looks good, please merge.


Visualizations

Map of US with consumption shown and slider that changes the year

Line graph of each different energy source's production over time with widgets that can filter/group the lines

Bar chart of all the states' total expenditures along with widgets that can show the expenditures
by state or by energy type.

Stacked bar  graph with each states energy consumption. Clean stacked on top of not clean. Slider that changes the year

Pie chart with energy type expenditure. Widget option to filter between states, and slider to filter year.


index.html Not found

when trying to go to the swagger documentation the index.html is not found in the webjar.
Used version of the liberary: 1.1.0
2023-01-31 09:22:20.132 [main] INFO  Application - Responding at http://<IP_ADDRESS>:8080
2023-01-31 10:03:35.677 [eventLoopGroupProxy-4-2] TRACE io.ktor.server.sessions.Sessions - Sessions found for /swagger-ui/index.html: Session
2023-01-31 10:03:35.686 [eventLoopGroupProxy-4-2] TRACE io.ktor.routing.Routing - Trace for [swagger-ui, index.html]
/, segment:0 -> SUCCESS @ /
  /swagger-ui, segment:1 -> SUCCESS @ /swagger-ui
    /swagger-ui/(method:GET), segment:1 -> FAILURE "Not all segments matched" @ /swagger-ui/(method:GET)
    /swagger-ui/api.json, segment:1 -> FAILURE "Selector didn't match" @ /swagger-ui/api.json
    /swagger-ui/{filename}, segment:2 -> SUCCESS; Parameters [filename=[index.html]] @ /swagger-ui/{filename}
      /swagger-ui/{filename}/(method:GET), segment:2 -> SUCCESS @ /swagger-ui/{filename}/(method:GET)
  /api, segment:0 -> FAILURE "Selector didn't match" @ /api
  /{...}, segment:0 -> FAILURE "Better match was already found" @ /{...}
Matched routes:
  "" -> "swagger-ui" -> "{filename}" -> "(method:GET)"
Route resolve result:
  SUCCESS; Parameters [filename=[index.html]] @ /swagger-ui/{filename}/(method:GET)
2023-01-31 10:03:35.690 [eventLoopGroupProxy-4-2] TRACE io.ktor.server.sessions.Sessions - Sending session data for /swagger-ui/index.html: Session
2023-01-31 10:03:35.691 [eventLoopGroupProxy-4-2] TRACE i.k.s.p.c.ContentNegotiation - Skipping because the type is ignored.
2023-01-31 10:03:35.697 [eventLoopGroupProxy-4-2] TRACE i.k.s.p.compression.Compression - Skip compression because no suitable encoder found.
2023-01-31 10:03:35.698 [eventLoopGroupProxy-4-2] TRACE i.k.s.p.statuspages.StatusPages - No handler found for status code 404 Not Found for call: /swagger-ui/index.html
2023-01-31 10:03:35.832 [eventLoopGroupProxy-4-2] TRACE Application - 404 Not Found: GET - /swagger-ui/index.html

My configuration:
install(SwaggerUI){
        pathFilter = { _, url -> url.firstOrNull() == "api" }
        swagger {
            forwardRoot = false
            swaggerUrl = "swagger-ui"
            onlineSpecValidator()
            displayOperationId = true
            showTagFilterInput = true
            syntaxHighlight = SwaggerUiSyntaxHighlight.MONOKAI
        }

        info {
            title = "Ktor swagger"
            version = "latest"
            description = "Ktor swagger api documentation"
            contact {
                name = "Mike Dirven"
                url = "http://www.icsvertex.nl"
                email =<EMAIL_ADDRESS>            }
        }
    }

Issue has been resolved there was another old swagger-ui liberary that imported the swagger-ui webjar version 4.15.5 while yours is using 4.15.0

I have the same issue, the jar is the right version.
2023-03-19T00:41:06.075763177Z 156343 [DefaultDispatcher-worker-11] TRACE io.ktor.routing.Routing  - Trace for [docs, index.html]
2023-03-19T00:41:06.075790327Z /, segment:0 -> SUCCESS @ /
2023-03-19T00:41:06.075795139Z   /docs, segment:1 -> SUCCESS @ /docs
2023-03-19T00:41:06.075798344Z     /docs/(method:GET), segment:1 -> FAILURE "Not all segments matched" @ /docs/(method:GET)
2023-03-19T00:41:06.075801185Z     /docs/api.json, segment:1 -> FAILURE "Selector didn't match" @ /docs/api.json
2023-03-19T00:41:06.075804172Z     /docs/{filename}, segment:2 -> SUCCESS; Parameters [filename=[index.html]] @ /docs/{filename}
2023-03-19T00:41:06.075807149Z       /docs/{filename}/(method:GET), segment:2 -> SUCCESS @ /docs/{filename}/(method:GET)
2023-03-19T00:41:06.075809851Z   /login, segment:0 -> FAILURE "Selector didn't match" @ /login
2023-03-19T00:41:06.075812465Z   /(authenticate "default"), segment:0 -> SUCCESS @ /(authenticate "default")
2023-03-19T00:41:06.075815320Z     /(authenticate "default")/user, segment:0 -> FAILURE "Selector didn't match" @ /(authenticate "default")/user
2023-03-19T00:41:06.075818275Z   /, segment:0 -> SUCCESS @ /
2023-03-19T00:41:06.075821062Z     /storage, segment:0 -> FAILURE "Selector didn't match" @ /storage
2023-03-19T00:41:06.075823758Z Matched routes:
2023-03-19T00:41:06.075826262Z   "" -> "docs" -> "{filename}" -> "(method:GET)"
2023-03-19T00:41:06.075839388Z Route resolve result:
2023-03-19T00:41:06.075842599Z   SUCCESS; Parameters [filename=[index.html]] @ /docs/{filename}/(method:GET)
2023-03-19T00:41:06.139270846Z 156407 [DefaultDispatcher-worker-15] TRACE io.ktor.routing.Routing  - Trace for [favicon.ico]
2023-03-19T00:41:06.139293204Z /, segment:0 -> SUCCESS @ /
2023-03-19T00:41:06.139295922Z   /docs, segment:0 -> FAILURE "Selector didn't match" @ /docs
2023-03-19T00:41:06.139299896Z   /login, segment:0 -> FAILURE "Selector didn't match" @ /login
2023-03-19T00:41:06.139302895Z   /(authenticate "default"), segment:0 -> SUCCESS @ /(authenticate "default")
2023-03-19T00:41:06.139306072Z     /(authenticate "default")/user, segment:0 -> FAILURE "Selector didn't match" @ /(authenticate "default")/user
2023-03-19T00:41:06.139308676Z   /, segment:0 -> SUCCESS @ /
2023-03-19T00:41:06.139310976Z     /storage, segment:0 -> FAILURE "Selector didn't match" @ /storage
2023-03-19T00:41:06.139316746Z Matched routes:
2023-03-19T00:41:06.139319276Z   No results
2023-03-19T00:41:06.139321394Z Route resolve result:
2023-03-19T00:41:06.139324019Z   FAILURE "No matched subtrees found" @ /

/docs/api.json returns an empty json as well.


ProblemFile and source term

Can someone take a look to what happens when we use the standard ProblemFile without adding any source term?
S is defined in the problem file as an input-output variable.
However, it does not seem to be defined anywhere in the code. What's the initial value of S? I think it is compiler dependent and a source of possible errors.

S_NS is allocated and set to 0 at the begging of the simulation in the storage construction. Also in SpatialDiscretization is set to 0 before calling the problem file each time Qdot is computed. In the problem file is inout so that if nothing is done it remains 0 (that is the standard ProblemFile or one that only changes other thing, as IC or BC).

I think that the source term is also used in multi grid. I agree with Oscar regarding what he said.

Good. It only gives problems in the truncation error estimation then. Thanks!


MkII PCB

Moved MkI PCB to PCB/MkI folder
Added MkII PCB Files
Changed README format and added accreditation

fixes #3

Updated to match current project head


Update path.sh

Codecov Report

Merging #139 into master will decrease coverage by 0.09%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #139      +/-   ##
==========================================
- Coverage   39.15%   39.05%   -0.10%
==========================================
  Files          84       84
  Lines       10060    10060
  Branches     2110     2110
==========================================
- Hits         3939     3929      -10
- Misses       5921     5926       +5
- Partials      200      205       +5

Impacted Files
Coverage Δ

neural_sp/models/modules/cif.py
87.34% <0.00%> (-1.27%)
:arrow_down:

neural_sp/models/seq2seq/decoders/las.py
50.50% <0.00%> (-0.57%)
:arrow_down:

neural_sp/models/modules/mocha.py
83.59% <0.00%> (-0.53%)
:arrow_down:

neural_sp/models/seq2seq/decoders/transformer.py
62.04% <0.00%> (-0.41%)
: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 66a8865...c0cba3a. Read the comment docs.


Return icon images on search responses

Library needs manage statics files like images, icons... These files will be in a shared static folder but we don't know yet the exact location, library must have this option configurable, maybe setting the URL of the static folder location.

We don't have a complete algorithm, so let's return something (could be a placeholder), then refine.

There is a comment on Trello Card about this issue.


Feature request: do not add " " unless it is part of the string

Hello! Thanks for the extension, it is very interesting indeed!
I was trying to get the default "// " to be "//" without spaces. Is there a reason why the extension adds it too?
Could it be skipped and just use the string specified in the settings? The user could just add the space there. There could also be a global setting to enable the addition of the space to preserve the current behavior.
Going further, for me it would be nice if that setting would be able to disable the space added in vscode by default to comments too. This way I would not have to write configs for all languages removing it, etc.
Cheers

Thanks so much for the tip!
I guess it was a long time ago when I tried to look for that setting :)
Then the extension works as expected, feel free to close the issue whenever you want.
Thanks.


Add Celery + Redis

Can we use docker-compose with this, in combination with the cookie-cutter backend (+ frontend)?

See https://github.com/UUDigitalHumanitieslab/sasta/blob/develop/docker-compose.yml and https://github.com/UUDigitalHumanitieslab/I-analyzer/blob/develop/docker-compose.yaml for inspiration. SASTA uses rabbitmq instead of redis, but that's easily adaptable.

Celery should also periodically clean up any remaining files on the latex-service server (cronjob). Latexmk provides a command for this (latexmk -C).

Instead of Celery/Redis, we can also use crontabs on the server.

Cronjob set up for all ParsePort servers: 30 2 * * * /usr/bin/docker exec pp-latex sh -c 'latexmk -C && rm *.tex'


Fix do method

Coverage decreased (-9.0%) to 67.401% when pulling af819ddc64ad7c687dc1c5e90e10a1175c1c4cc5 on fix_do_method into 113788e4de039d9e40c42302648272a56a6d2541 on master.


Can you come up with a support for nuxt3 or vue3?

I think this design concept is very innovative. It would be even better if it could support Vue3 or Nuxt3.

Thank you very much for your help. I have tried in nuxt3

This quote prompts Vue: Could not find a declaration file for module Vue bigheads.
It should be Vue2's JavaScript and cannot be directly referenced in TS. But with help, if I have time, I will try to change it to TS. Thank you again for your help.


percentage variable name is confusing

To me:

A percentage means e.g. 25 for 25% mines.
A mine count, or how_many_mines_user_wants, means how many mines there are, e.g. 200.

These are different things. But variable names are confusing, and percentage is a variable whose value is actually a mine count.
        self.how_many_mines_user_wants = percentage

Also, when there is an actual percentage, it is called slider_value instead. Even real_percentage isn't really a percentage; it's a mine count that hasn't been rounded to an integer yet.
    slider_value = int(difficulty_slider.scale.get())
    real_percentage = (width * height / 100) * slider_value
    percentage = round(real_percentage)

Not completely sure what you mean, but I tried to clear it up a bit. Tell me if it needs further attention

Not completely sure what you mean, but I tried to clear it up a bit. Tell me if it needs further attention

real_percentage and percentage distinction was fixed in ddcb96f6a675ed0913b1083e494eea994d039f0c but the rest of it is still just as confusing as before. If you have a variable whose value is the mine count, then why in the world does it have to be named rounded_percentage instead of mine_count?

real_percentage and percentage distinction was fixed in ddcb96f6a675ed0913b1083e494eea994d039f0c but the rest of it is still just as confusing as before. If you have a variable whose value is the mine count, then why in the world does it have to be named rounded_percentage instead of mine_count?

Fixed this in pr #40

Fixed this in pr #40


Main listing briefly shows outcome delimiters for categorical markets

The markets listing very briefly displays the unprocessed description string, including the (unsightly) outcome delimiters (~|>, |) for categorical markets.  If it is possible to parse the descriptions string immediately on loading this would be preferable.

don't see anymore


1DS Implemetation: IPC Request Time for logging in telemetry using 1DS

Proposed changes
Passing requestReceivedTimestamp in Broker to calculate IPC Perf as part of telemetry using 1DS SDK.
Related PR: https://github.com/AzureAD/azure-activedirectory-tokenbroker-for-objc/pull/1156
Type of change

[ ] Feature work
[ ] Bug fix
[ ] Documentation
[ ] Engineering change
[ ] Test
[x] Logging/Telemetry

Risk

[ ] High – Errors could cause MAJOR regression of many scenarios. (Example: new large features or high level infrastructure changes)
[x] Medium – Errors could cause regression of 1 or more scenarios. (Example: somewhat complex bug fixes, small new features)
[ ] Small – No issues are expected. (Example: Very small bug fixes, string changes, or configuration settings changes)

Additional information

In order to make these Throttling Tests run with correct input params (requestSentDate != nil) can you update fullRequestThumbprintExcludeParams in MSIDBrokerOperationSilentTokenRequest to be excluded from full thumbprint calculation. For example: Old code: `+ (NSSet *)fullRequestThumbprintExcludeParams { static dispatch_once_t once_token; static NSSet *excludeSet;
dispatch_once(&once_token, ^{
    excludeSet = [NSSet setWithArray:@[MSID_ACCOUNT_DISPLAYABLE_ID_JSON_KEY, //since we already use home account id, this is redundant
                                       MSID_BROKER_CLIENT_CAPABILITIES_KEY,
                                       MSID_BROKER_CLIENT_VERSION_KEY,
                                       MSID_BROKER_CLIENT_APP_VERSION_KEY,
                                       MSID_BROKER_CLIENT_APP_NAME_KEY,
                                       MSID_BROKER_CORRELATION_ID_KEY,
                                       MSID_BROKER_KEY]];
});
return excludeSet;

} ` New code:

(NSSet *)fullRequestThumbprintExcludeParams
{
static dispatch_once_t once_token;
static NSSet *excludeSet;
dispatch_once(&once_token, ^{
excludeSet = [NSSet setWithArray:@[MSID_ACCOUNT_DISPLAYABLE_ID_JSON_KEY, //since we already use home account id, this is redundant
MSID_BROKER_CLIENT_CAPABILITIES_KEY,
MSID_BROKER_CLIENT_VERSION_KEY,
MSID_BROKER_CLIENT_APP_VERSION_KEY,
MSID_BROKER_CLIENT_APP_NAME_KEY,
MSID_BROKER_CORRELATION_ID_KEY,
MSID_BROKER_KEY,
your new request sent key string here]];
});
return excludeSet;

}

Resolved comments


fix(schema): Fixing issue with last commit

:tada: This PR is included in version 3.0.6 :tada:
The release is available on npm package (@latest dist-tag)
Your semantic-release bot :package::rocket:


Some bash output is offset

unless there's a way to modify the properties of the message tht prevents that, the solution would be to put ideally a non printing character at the from and end of the stream, assuming that one exists that discord will not strip


Update app.py

Documentation

please close+mark the PR as [invalid] to the OP gets banned from hacktoberfest for this garbage/spam


python311Packages.testcontainers: 4.6.0 -> 4.7.0

Description of changes
Changelog: https://github.com/testcontainers/testcontainers-python/releases/tag/testcontainers-v4.7.0
cc @onny

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 323180 run on x86_64-linux 1

8 packages marked as broken and skipped:

python311Packages.apache-beam
python311Packages.apache-beam.dist
python311Packages.dm-sonnet
python311Packages.dm-sonnet.dist
python311Packages.tensorflow-datasets
python311Packages.tensorflow-datasets.dist
python312Packages.apache-beam
python312Packages.apache-beam.dist

8 packages built:

python311Packages.aio-pika
python311Packages.aio-pika.dist
python311Packages.testcontainers
python311Packages.testcontainers.dist
python312Packages.aio-pika
python312Packages.aio-pika.dist
python312Packages.testcontainers
python312Packages.testcontainers.dist

Result of nixpkgs-review pr 323180 run on aarch64-linux 1

4 packages marked as broken and skipped:

python311Packages.apache-beam
python311Packages.apache-beam.dist
python312Packages.apache-beam
python312Packages.apache-beam.dist

8 packages built:

python311Packages.aio-pika
python311Packages.aio-pika.dist
python311Packages.testcontainers
python311Packages.testcontainers.dist
python312Packages.aio-pika
python312Packages.aio-pika.dist
python312Packages.testcontainers
python312Packages.testcontainers.dist

Result of nixpkgs-review pr 323180 run on aarch64-darwin 1

4 packages marked as broken and skipped:

python311Packages.apache-beam
python311Packages.apache-beam.dist
python312Packages.apache-beam
python312Packages.apache-beam.dist

8 packages built:

python311Packages.aio-pika
python311Packages.aio-pika.dist
python311Packages.testcontainers
python311Packages.testcontainers.dist
python312Packages.aio-pika
python312Packages.aio-pika.dist
python312Packages.testcontainers
python312Packages.testcontainers.dist

Result of nixpkgs-review pr 323180 run on x86_64-darwin 1

4 packages marked as broken and skipped:

python311Packages.apache-beam
python311Packages.apache-beam.dist
python312Packages.apache-beam
python312Packages.apache-beam.dist

8 packages built:

python311Packages.aio-pika
python311Packages.aio-pika.dist
python311Packages.testcontainers
python311Packages.testcontainers.dist
python312Packages.aio-pika
python312Packages.aio-pika.dist
python312Packages.testcontainers
python312Packages.testcontainers.dist

Result of nixpkgs-review pr 323180 run on x86_64-linux 1

8 packages marked as broken and skipped:

python311Packages.apache-beam
python311Packages.apache-beam.dist
python311Packages.dm-sonnet
python311Packages.dm-sonnet.dist
python311Packages.tensorflow-datasets
python311Packages.tensorflow-datasets.dist
python312Packages.apache-beam
python312Packages.apache-beam.dist

8 packages built:

python311Packages.aio-pika
python311Packages.aio-pika.dist
python311Packages.testcontainers
python311Packages.testcontainers.dist
python312Packages.aio-pika
python312Packages.aio-pika.dist
python312Packages.testcontainers
python312Packages.testcontainers.dist


feat: Add support for dedicated agent - Backend

[x] Agent configure API
[x] DID create and update isPrimary in the with ledger
[x] On-premises agent shell script
[x] Publish on-premises agent shell script in github
[x] Deploy on-premises agent on the AWS instance

Pending Todo:
Backend

[ ] When creating a DID through the API with "isPrimaryDid": true, the API should ensure that only one DID is marked as primary at a time. If a new DID is set as primary, any existing primary DID should be unmarked as primary.


Custom labels added for istio-cni deployment and pods in helm chart

This PR adds the capability in helm chart for adding custom labels to istio-cni deployments ands pods and aims at this Issue - https://github.com/istio/istio/issues/50372

Hi @nischay30. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

I was about to open a PR - can you add the "app: istio-cni" label as well ?
It is very annoying that all other charts have this label - but this one uses k8s-app instead ( and I don't know what "-node" suffix means - all other charts use the "app: chart_name")

The k8s-app label is present in spec.selector.matchLabels, which is immutable field. By replacing, it will become a breaking change, where first it needs to be uninstalled.

And it may be useful to provide an example of 'when you need them' - by the criteria that you may need something we would replicate the entire Pod spec in values.yaml...
I know there is a pattern of redundant docs in most of the helm charts, but at least for new stuff it may be nice to have at least an example use case.

Do you have any example? any format? where we can add? because custom labels isn't a big thing

Not change - add. There is no harm in adding an extra label.
On Mon, Apr 29, 2024, 03:45 Nischay Goyal @.***> wrote:

I was about to open a PR - can you add the "app: istio-cni" label as well ?
It is very annoying that all other charts have this label - but this one
uses k8s-app instead ( and I don't know what "-node" suffix means - all
other charts use the "app: chart_name")
The k8s-app label is present in spec.selector.matchLabels, which is
immutable field. By replacing, it will become a breaking change, where
first it needs to be uninstalled.
—
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/pull/50694#issuecomment-2082401496, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAUR2XRRTNNQ7TX6YIOYJLY7YQDDAVCNFSM6AAAAABG2QGFCGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBSGQYDCNBZGY
.
You are receiving this because your review was requested.Message ID:
@.***>

Don't worry about 'app', I can open a separate PR.
For comments - just some example like what label you are planning to use, I
assume this PR is based on some use case you have.
On Mon, Apr 29, 2024, 15:50 Costin Manolache @.***> wrote:

Not change - add. There is no harm in adding an extra label.
On Mon, Apr 29, 2024, 03:45 Nischay Goyal @.***>
wrote:

I was about to open a PR - can you add the "app: istio-cni" label as well
?
It is very annoying that all other charts have this label - but this one
uses k8s-app instead ( and I don't know what "-node" suffix means - all
other charts use the "app: chart_name")
The k8s-app label is present in spec.selector.matchLabels, which is
immutable field. By replacing, it will become a breaking change, where
first it needs to be uninstalled.
—
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/pull/50694#issuecomment-2082401496, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAUR2XRRTNNQ7TX6YIOYJLY7YQDDAVCNFSM6AAAAABG2QGFCGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBSGQYDCNBZGY
.
You are receiving this because your review was requested.Message ID:
@.***>

Can you add a release note file?
Also explain why use daemonset vs pod level label for istio-cni?
cc @bleggett

It's good practice to have both, like we already do in the ztunnel daemonset chart.
My biggest beef with the istio-cni chart is the use of the cni prefix for all the values, which is an artifact of istioctl and very non-helm.

On Thu, May 2, 2024 at 9:02 AM Ben Leggett @.***> wrote:

Can you add a release note file?
Also explain why use daemonset vs pod level label for istio-cni?
cc @bleggett https://github.com/bleggett
It's good practice to have both, like we already do in the ztunnel
daemonset chart.
My biggest beef with the istio-cni chart is the use of the cni prefix for
all the values, which is an artifact of istioctl and very non-helm

+1
There is an opportunity to cleanup a bit - add new things at top level, add
"public / stable" things to top level, etc.

PR needs rebase.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

Can you add a release note file?
Also explain why use daemonset vs pod level label for istio-cni?
cc @bleggett

I have changed to labels as discussed above. Also, how to add release-notes file?

Can you add a release note file?
Also explain why use daemonset vs pod level label for istio-cni?
cc @bleggett

I have changed to labels as discussed above. Also, how to add release-notes file?

Check istio/releasenotes/README.md

Custom labels on Daemonset level, for eg - FinOps/teams labels

labels: {}

 # team-owner: finops

Custom labels on Pod level, for eg - FinOps/teams labels

podLabels: {}

 # team-owner: finops

Minor nit - don't need specific examples.

I asked for examples and use cases - but I agree 'team-owner' is not the
right example for CNI or ztunnel, it's not a regular pod.
I still don't understand the use case, but since all other helm charts we
have contain similar customisation I don't mind this, was just hoping to
understand.

Custom labels on Daemonset level, for eg - FinOps/teams labels + labels: {} + # team-owner: finops + + # Custom labels on Pod level, for eg - FinOps/teams labels + podLabels: {} + # team-owner: finops + Minor nit - don't need specific examples.

I asked for examples and use cases - but I agree 'team-owner' is not the right example for CNI or ztunnel, it's not a regular pod. I still don't understand the use case, but since all other helm charts we have contain similar customisation I don't mind this, was just hoping to understand.

I'll leave it to you then, I missed you had asked for it, it just looks weird since we don't do that in other spots and people might not know what finops is.

What is blocking to get this merged?

Not sure.

PR needs rebase.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@nischay30: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
b16c562d46125989e1f6bbc69477d50069ec9427
link
true
/test unit-tests-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@nischay30: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
b16c562d46125989e1f6bbc69477d50069ec9427
link
true
/test unit-tests-arm64

gencheck_istio
b16c562d46125989e1f6bbc69477d50069ec9427
link
true
/test gencheck

unit-tests_istio
b16c562d46125989e1f6bbc69477d50069ec9427
link
true
/test unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@nischay30 can you make CI happy?

can this be reopened? another use case would be adding necessary labels to specify the kyverno pod security policy.

@yyardeng you're welcome to reopen it or open another PR. https://github.com/istio/istio/issues/50372 is still open and I think we're OK to do this.


-T13- Fix bullet (bullet on separate line) on "jobs" page under "Current jobs"

If by fix - you mean get rid of.

Similar to this: http://web.archive.org/web/20150219081813/http://www.atlrug.com/jobs

Turned off houndci.com - FYI

Cool. Thanks for the merge.


gnss-share: 0.6 -> 0.7.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/gnss-share/versions.
meta.description for gnss-share is: share GNSS data between multiple clients
Updates performed

Golang update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.7.1 with grep in /nix/store/2qndzq9v0yf47i33dpqmllpkwjiz9nvb-gnss-share-0.7.1
found 0.7.1 in filename of file in /nix/store/2qndzq9v0yf47i33dpqmllpkwjiz9nvb-gnss-share-0.7.1

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
gnss-share

Instructions to test this update (click to expand)

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

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

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/2qndzq9v0yf47i33dpqmllpkwjiz9nvb-gnss-share-0.7.1
ls -la /nix/store/2qndzq9v0yf47i33dpqmllpkwjiz9nvb-gnss-share-0.7.1/bin

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

1 package built:

gnss-share

Maintainer pings
cc @balsoft for testing.

Result of nixpkgs-review pr 237238 run on x86_64-darwin 1

1 package built:

gnss-share


Snapshot 78

It's ready to deploy Snapshot 78.
https://github.com/macvim-dev/macvim/wiki/Deployment

Vim patch 7.4.902
Add basic support for CoreText ligatures
Add optional blur to transparent windows
Allow to open directory in Open dialog
Fix rendering and resizing issues on El Capitan Split View
Fix Deployment Target for Yosemite with Xcode 7.1

any other updates?

Wasn't there already a Snapshot 78?

Yes, there was: https://github.com/macvim-dev/macvim/commit/c45736ab2b3dec5297be3049cfe0edd4ef55416c

78 is already reverted. never mind.

Snapshot 78 will be built with dynamic linking to Lua, Perl, Python 2, Python 3, and Ruby.
https://github.com/macvim-dev/macvim/blob/77b7042855becd832fe3c03ae1af4e6db5985e57/.travis.yml#L17
However the runtime depends on Homebrew path hierarchy. To adopt the other package system or self built for loading script binding shared libraries, I'll release another snapshot after my patch is applied.
https://github.com/vim/vim/commit/a0f849ee40cbea3c889345256786b640b0becca2#diff-38d7929bd26d74d92ceddf984bbfc8dbR125

There shouldn't be a snapshot 78, as it already exists (not on the releases page, but at the link I gave above).  There should be a snapshot 79.

ok, It doesn't matter it's up to you

ok, It doesn't matter it's up to you

It does matter, which is why I tried to prevent the existence of two distinct things named "Snapshot 78".  If someone creates an issue and we ask what version of MacVim she is using, and she says "Snapshot 78", we won't know which version she is using.  She could be using the thing we just built and released today, or she could be using c45736a.

https://github.com/macvim-dev/macvim/releases/tag/snapshot-79

Honestly to say, there was snapshot 78 build. But it had been removed very soon after released.

By the way, good job, guys!

Honestly to say, there was snapshot 78 build. But it had been removed very soon after released.

That's not the point, though.  The point is that a user could have checked out commit c45736a, which is titled "Snapshot 78", and completely reasonably have told us she is using Snapshot 78.

yeah. but it's rare case, no one cares.


OS X: tensorflow java image not found

i am running with Mac OS
<dependencies>
		<dependency>
			<groupId>org.tensorflow</groupId>
			<artifactId>tensorflow</artifactId>
			<version>1.4.0-rc0</version>
		</dependency>
	</dependencies>

please note the issue is seen in 1.4.0-rc0 and 1.3.0, however the example works fine with 1.3.0-rc0
org.tensorflow.NativeLibrary: tryLoadLibraryFailed: no tensorflow_jni in java.library.path
org.tensorflow.NativeLibrary: jniResourceName: org/tensorflow/native/darwin-x86_64/libtensorflow_jni.dylib
org.tensorflow.NativeLibrary: frameworkResourceName: org/tensorflow/native/darwin-x86_64/libtensorflow_framework.dylib
org.tensorflow.NativeLibrary: org/tensorflow/native/darwin-x86_64/libtensorflow_framework.dylib not found. This is fine assuming org/tensorflow/native/darwin-x86_64/libtensorflow_jni.dylib is not built to depend on it.
org.tensorflow.NativeLibrary: extracting native library to: /var/folders/bj/v1l790113yn16zvhljd6yl8h0000gn/T/tensorflow_native_libraries-1508538938374-0/libtensorflow_jni.dylib
org.tensorflow.NativeLibrary: copied 90774332 bytes to /var/folders/bj/v1l790113yn16zvhljd6yl8h0000gn/T/tensorflow_native_libraries-1508538938374-0/libtensorflow_jni.dylib
Exception in thread "main" java.lang.UnsatisfiedLinkError: /private/var/folders/bj/v1l790113yn16zvhljd6yl8h0000gn/T/tensorflow_native_libraries-1508538938374-0/libtensorflow_jni.dylib: dlopen(/private/var/folders/bj/v1l790113yn16zvhljd6yl8h0000gn/T/tensorflow_native_libraries-1508538938374-0/libtensorflow_jni.dylib, 1): Library not loaded: @rpath/libtensorflow_framework.so
  Referenced from: /private/var/folders/bj/v1l790113yn16zvhljd6yl8h0000gn/T/tensorflow_native_libraries-1508538938374-0/libtensorflow_jni.dylib
  Reason: image not found
	at java.lang.ClassLoader$NativeLibrary.load(Native Method)
	at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1937)
	at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1822)
	at java.lang.Runtime.load0(Runtime.java:809)
	at java.lang.System.load(System.java:1086)
	at org.tensorflow.NativeLibrary.load(NativeLibrary.java:96)
	at org.tensorflow.TensorFlow.init(TensorFlow.java:66)
	at org.tensorflow.TensorFlow.<clinit>(TensorFlow.java:70)
	at org.tensorflow.Graph.<clinit>(Graph.java:258)
	at xTensorflow.HelloTF.main(HelloTF.java:13)

Thanks for a report, there seems to be an issue with 1.4.0-rc0 and Mac OS X.
However the point release 1.3.0 should be fine.
The  snippet you provided seems to be on the usage of 1.4.0-rc0. Could you provide the same log for when you're using 1.3.0?

I ran into the same problem in 1.4.0-rc0 and 1.4.0-rc0. But it works well in 1.3.0
It's import to me for supporting string tensor with Java in version 1.4.0

Yup, we will have this fixed in 1.4.0-rc1 (if there is one) and surely in the 1.4.0 release.
(For the record, things should be fine for Linux and Windows. If the problem appears in anything other than 1.4.0-rc0 on OS X, please let us know)

@asimshankar yes 1.3.0 works fine

1.4.0-rc1 was just published and should have the problem fixed. Could you confirm that it works @sujitbiswas @mclodaa ?

@asimshankar it works well in 1.4.0-rc1. Thx!
I wonder what causes this problem. I tried to solve this problem, but failed.

i am using the maven repo [https://mvnrepository.com/artifact/org.tensorflow/libtensorflow] it is not yet updated with 1.4.0-rc1

I am able to replicate this in 1.14.0 on OSX.

org.tensorflow
tensorflow
1.13-1

I use the version1.13.1, then this problem appeared too.


ajax Contact

well, after update root-scripts.php my Contact ajax (plugins) is dead...
if is (js) conflict ?

Closing this due to lack of details.

and this is only, Inompatibility Plugins (wp).
The solution is:

deactivate
update version ( plugins )


add connection event listener support similar to node-redis

Tried to imitate node-redis event listener to make migrations easier. Having an event handler is always useful for logging, debugging and tracing as well.
connect: fires when (re)connected sucessfully
ready: fires when (re)connected and authenticated sucessfully, and ready to send commands
reconnecting: fires only before reconnection with a delay
close: fires after connection is closed for whatever reason
end: fires after connection is closed and terminated, no reconnection is planned
error: fires when an unexpected/uncontrolled error occurs

I took way more than i thought to implement a proper, full typed event-target based solution due to typescript inconvenience with events. Honestly, i can't spend any more time for this but i think it is done. I am updating the pull request soon.

Released in v0.37.0!


Added Multistage-graph.md

📥 Pull Request
Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes #1279
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] Documentation update

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

This program is w.r.t issue #1279 which you assigned me.

@ajay-dhangar I have changed the id value as per required. If any other changes is required I will also do that. Please review it


SimpleForm hint: using key in the locale as attribute when in fact is a model

Hi there!
When I add a hint to a attribute of a particular model and I use a association input for this model the i18n is mistakenly displayed;
Very confusing explanation.
Let's see a real example:
  simple_form:
    hints:
      splitting:
        interval: "em dias"

  <%= f.input :splitting %>

The hint is returned as interval: em dias
I created a test case for this: f3eabaf06e8dcd96f3ef26b409efc3832c193af0

Hey mate! Thank you for the test case. I'll see this issue tomorrow.


Screen goes black after setting tabbar item badge to nil

let tabArray = self.tabBarController?.tabBar.items as NSArray?
let tabItem = tabArray?.object(at: 4) as! UITabBarItem
tabItem.badgeValue = nil

This code sometimes makes app goes black screen.

@UtkuDalmaz Not able to reproduce.
If your controller is a subclass of UITabBarController try this
let tabArray = self.tabBar.items
let tabItem = tabArray![4]
tabItem.badgeValue = nil

No repose, so closing issue.


iOS app cannot scrolling after upgrade to react-native-webview v5.2.3

Hi,
I cannot scrolling webview after upgrade to the last version 5.2.3.
My app using react-native 0.58.6
I've to rollback to version 5.2.1 to make it works.

Thanks for the report, let me test, might be because of https://github.com/react-native-community/react-native-webview/pull/158


Adding docs for securing operator webhooks

We commission both CA and server certificates for securing the webhooks in the operator. By default this is a no-touch process which generates a self-signed CA certificate and uses that to generate a server certificate at startup.
If people want to use their own CA for this, it is possible, but we need to tell them how. This PR addresses that.

@taroface you mentioned that you were going to take this over. Just wanted to make sure that's still the case.

@pseudomuto Yes, aiming to do it this week!


Nodes crashes after a fail to connect web3 HTTP provider

Running AIRA for a day or longer I often face with robonomics_liability and ethereum_common crashes at least once a day with an error like:
requests.exceptions.ConnectionError: HTTPConnectionPool(host='<IP_ADDRESS>', port=8545): Max retries exceeded with url: / (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f986007fa20>: Failed to establish a new connection: [Errno 111] Connection refused',))

After it, for example, erc20 node services becomes unavailable. I did not check robonomics_liability. And at the same time parity still works ok and if I restsart robonomics_comm packages it works all right.
I suggest to handle this error with user warning notification in logs and reconnect to RPC after it becomes available.

It looks like Ethereum node unavailable, do you have Ethereum node logs?

I just catch similar situation, please find a log below. In that case parity stops syncing, restart helped. But it seems like it's not what I told in opening comment where parity continue writing a log. I will collect more information.
[root@aira-mainnet-dev:~]# journalctl -u parity -f
-- Logs begin at Mon 2018-09-10 19:49:54 +04. --
Sep 11 00:52:18 aira-mainnet-dev 91c9mq6jkwmsh69q82fk6zb9vr1v0q54-unit-script-parity-start[26912]: 2018-09-11 00:52:18  Imported #6308139 0x42ae…0d19 (8.01 Mgas)
Sep 11 00:52:20 aira-mainnet-dev 91c9mq6jkwmsh69q82fk6zb9vr1v0q54-unit-script-parity-start[26912]: 2018-09-11 00:52:20    26/50 peers     10 MiB cache  0 bytes queue  RPC:  0 conn,  0 req/s,   0 µs
Sep 11 00:52:25 aira-mainnet-dev 91c9mq6jkwmsh69q82fk6zb9vr1v0q54-unit-script-parity-start[26912]: 2018-09-11 00:52:25  Syncing #6308139 0x42ae…0d19     0 hdr/s      0+    0 Qed  #6308139   26/50 peers
  10 MiB cache  0 bytes queue  RPC:  0 conn,  0 req/s,   0 µs
Sep 11 00:52:25 aira-mainnet-dev 91c9mq6jkwmsh69q82fk6zb9vr1v0q54-unit-script-parity-start[26912]: 2018-09-11 00:52:25  Imported #6308140 0x2ec5…84a9 (8.00 Mgas)
Sep 11 00:52:44 aira-mainnet-dev 91c9mq6jkwmsh69q82fk6zb9vr1v0q54-unit-script-parity-start[26912]: 2018-09-11 00:52:44  Imported #6308141 0xf989…c31d (7.99 Mgas)
Sep 11 00:52:50 aira-mainnet-dev 91c9mq6jkwmsh69q82fk6zb9vr1v0q54-unit-script-parity-start[26912]: 2018-09-11 00:52:50  Imported #6308142 0x5866…bdbc (7.90 Mgas)
Sep 11 00:52:55 aira-mainnet-dev 91c9mq6jkwmsh69q82fk6zb9vr1v0q54-unit-script-parity-start[26912]: 2018-09-11 00:52:55    26/50 peers     10 MiB cache  0 bytes queue  RPC:  0 conn,  0 req/s,   0 µs
Sep 11 00:53:13 aira-mainnet-dev 91c9mq6jkwmsh69q82fk6zb9vr1v0q54-unit-script-parity-start[26912]: 2018-09-11 00:53:13  Imported #6308143 0x3cfe…128f (7.92 Mgas)
Sep 11 00:53:25 aira-mainnet-dev 91c9mq6jkwmsh69q82fk6zb9vr1v0q54-unit-script-parity-start[26912]: 2018-09-11 00:53:25  Imported #6308144 0x8a2f…0b3e (7.15 Mgas)
Sep 11 00:53:25 aira-mainnet-dev 91c9mq6jkwmsh69q82fk6zb9vr1v0q54-unit-script-parity-start[26912]: 2018-09-11 00:53:25    26/50 peers     10 MiB cache  0 bytes queue  RPC:  0 conn,  0 req/s,   0 µs

@strdn looks like a temporary connection problems, Ethereum interaction should be wrapped in ‘try’blocks.


HTTP Error: HTTP/1.1 400 Bad Request

I do a very simple test but get this exception
I ensure that I enter a correct api key

Oh I think it work when max token is below 4096


Test/runtime

Changes

Add some tests for ImplWrapper, List and ModuleRenderer and does not modify their current logic.
Add  a TestLib which consists of some simple components and trait just for test.

Testing principles
There are 2 principles when testing sunmao:

Test the components' rendering result rathen than their implementation details.
Test the component as whole rather than apart.

For example, ImplWrapper is a very complex component which has a lot of state, effects. It is hard to test itself. So I add a TestLib to test it and only focus on the rendering result of ImplWrapper. If the result is right, than I assume the whole ImplWrapper is working as expected.
issue: #436

Updated.


For a create request, get rid of the comments field

Feedback indicates that there aren't many situations in which they need to share comments on approval of a creation request.
Current testing indicates that these comments are not being shared at all (for a creation approval).
DoD:

[x] no comments field for a creation approval

No need to comment on approval of Create Request now:


bug: need a way to specify filters and query parameters to methods that get all resource records

The methods are:

getAllProfiles
getAllOrgUnits
getAllServices

Query Parameters supported:

_lineCount (integer)
_order (string)

Filters
Filters depend on the resource (do a getMetadataForResource call). They are specified in the URL after the resource, and can be chained.
Thus, if your resource is at /profileAndServices/profile and you have a filter filter1, your url will be: /profileAndServices/profile/filter1
If your resource is at /profileAndServices/profile and you have filters filter1 and filter2, your url will be: /profileAndServices/profile/filter1/filter2 (chain them)
Record Column Selection
Instead of a filter, you can also "select" a field from the resource (think of a database table selection), by specifying the field after the resource. You can only select one field. For example, if you want the Profile records returned to only select the "email" field, your url will be:
/profileAndServices/profile/email
Example Call
const params = {
    lineCount: 10, // pagination: default 25
    order: 'email',  // sort: what field to sort on
    descendingSort: true // sort: default is ascending
}
const filters = [ 'byEmail', 'byText' ]
getAllProfiles(filters, params)

The Sorting where you add %20desc or %20asc to the end of the URL (see https://docs.campaign.adobe.com/doc/standard/en/api/ACS_API.html#sorting) is highly unconventional, and I'm not sure if this can be expressed in the OpenAPI spec.
I will treat it as appending this to the value for the _order query parameter as specified in the example, which makes more sense (I've asked for clarification with the API devs).
So, if you have query param _order=email, I would append _order=email%20desc for descending sort.


Update approvals-known-issues.md

https://msazure.visualstudio.com/One/_workitems/edit/10936899 - adding the Power Apps v2 trigger limitations

@sbasi19 : Thanks for your contribution! The author(s) have been notified to review your proposed change. @hamenon

@MSFTMan : Thanks for your contribution! The author(s) have been notified to review your proposed change. @hamenon

@MSFTMan : Thanks for your contribution! The author(s) have been notified to review your proposed change. @hamenon


Waiting For Service error

Application: RiingPlus.Service.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.ComponentModel.Win32Exception
at System.ServiceProcess.ServiceProcessInstaller.GetAccountSid(System.String)
at System.ServiceProcess.ServiceProcessInstaller.Install(System.Collections.IDictionary)
at System.Configuration.Install.Installer.Install(System.Collections.IDictionary)
at System.Configuration.Install.Installer.Install(System.Collections.IDictionary)
at System.Configuration.Install.AssemblyInstaller.Install(System.Collections.IDictionary)
at System.Configuration.Install.Installer.Install(System.Collections.IDictionary)
at System.Configuration.Install.TransactedInstaller.Install(System.Collections.IDictionary)
Exception Info: System.InvalidOperationException
at System.Configuration.Install.ManagedInstallerClass.InstallHelper(System.String[])
at RiingPlus.Service.Program.InstallService()
at RiingPlus.Service.Program.ManageService()
at RiingPlus.Service.Program.Main(System.String[])
Managed to install from the zip file. But after login it says "Waiting for service". This is the log from the event viewer. Is there any fix to this ? Thanks for any help in advance

It seems like you are using the old version but it is no longer supported.
Please try the new one from the releases.

Is it also the zipped one too? Coz tried the one from github but im a total noob in pc software. Ill try when i got home thanks man keep it up good job 👍👍👍

Yea it is also zipped.
If you get to trying it make sure you stop the official software. You could first check for any errors by running it in the console instead of installing it. There is a "Run in console" option in the menu when you launch the service exe.

Hi, I tried running the latest version TTController_<IP_ADDRESS>-dev, but as u suggested when i run in console it stuck at "Creating Device Manager".
In General tab it says  "The Thermaltake Controller service is marked as an interactive service.  However, the system is configured to not allow interactive services.  This service may not function properly."

7030
0
2
0
0
0x8080000000000000

5313

System
DESKTOP-1IFSF9T

Thermaltake Controller

Any tips ? Is it because of my hardware?

Could you list what thermaltake devices you have?

In General tab it says "The Thermaltake Controller service is marked as an interactive service. However, the system is configured to not allow interactive services. This service may not function properly."

Yes this is what it says for me too but it works just fine.

Im using the Riing 12 Radiator Fan TT Premium Edition 3 fan pack.

TTController_0.6.0-alpha.27.f01ab074a4ddd974b8abc9cafeaefc675d57eaec.zip
Tried using this, but seems when I run in console it get stuck at Searching for "Riing" Controllers.
When i run Hardware Info there is nothing listed. Is it because of the controller? But my fan is running but only with the default red color.

Please post the whole initialization log. You can select text in the console and right click to copy.

3:43:16.5235: ================================================================
23:43:16.5655: Initializing...
23:43:16.6115: Loading plugins...
23:43:16.6185: Loading assembly: TTController.Plugin.BlinkEffect [<IP_ADDRESS>]
23:43:16.6385: Loading assembly: TTController.Plugin.ByLedColorEffect [<IP_ADDRESS>]
23:43:16.6385: Loading assembly: TTController.Plugin.FlowEffect [<IP_ADDRESS>]
23:43:16.6565: Loading assembly: TTController.Plugin.FullColorEffect [<IP_ADDRESS>]
23:43:16.6565: Loading assembly: TTController.Plugin.PulseEffect [<IP_ADDRESS>]
23:43:16.6665: Loading assembly: TTController.Plugin.RawEffect [<IP_ADDRESS>]
23:43:16.6665: Loading assembly: TTController.Plugin.RippleEffect [<IP_ADDRESS>]
23:43:16.6665: Loading assembly: TTController.Plugin.SnakeEffect [<IP_ADDRESS>]
23:43:16.6665: Loading assembly: CSCore [<IP_ADDRESS>]
23:43:16.6805: Loading assembly: TTController.Plugin.SoundEffect [<IP_ADDRESS>]
23:43:16.6805: Loading assembly: TTController.Plugin.SpectrumEffect [<IP_ADDRESS>]
23:43:16.6805: Loading assembly: TTController.Plugin.TemperatureEffect [<IP_ADDRESS>]
23:43:16.6805: Loading assembly: TTController.Plugin.WaveEffect [<IP_ADDRESS>]
23:43:16.6955: Loading assembly: TTController.Plugin.CopySpeedController [<IP_ADDRESS>]
23:43:16.6955: Loading assembly: TTController.Plugin.PwmSpeedController [<IP_ADDRESS>]
23:43:16.6955: Loading assembly: TTController.Plugin.StaticSpeedController [<IP_ADDRESS>]
23:43:16.6955: Loading assembly: TTController.Plugin.AlwaysTrigger [<IP_ADDRESS>]
23:43:16.6955: Loading assembly: TTController.Plugin.LogicTrigger [<IP_ADDRESS>]
23:43:16.7095: Loading assembly: TTController.Plugin.OneTimeTrigger [<IP_ADDRESS>]
23:43:16.7095: Loading assembly: TTController.Plugin.ProcessTrigger [<IP_ADDRESS>]
23:43:16.7095: Loading assembly: TTController.Plugin.PulseTrigger [<IP_ADDRESS>]
23:43:16.7095: Loading assembly: TTController.Plugin.TemperatureTrigger [<IP_ADDRESS>]
23:43:16.7365: Creating Config Manager...
23:43:16.7415: Loading config...
23:43:17.0016: Loading done...
23:43:17.0116: Creating DataCache...
23:43:17.0116: Creating Sensor Manager...
23:43:18.9508: Detected sensors: 54
23:43:18.9618: Creating Temperature Manager...
23:43:18.9618: Valid sensor identifier: /amdcpu/0/temperature/0
23:43:18.9778: Valid sensor identifier: /amdcpu/0/temperature/1
23:43:18.9778: Valid sensor identifier: /atigpu/0/temperature/0
23:43:18.9918: Valid sensor identifier: /hdd/0/temperature/0
23:43:18.9918: Valid sensor identifier: /hdd/1/temperature/0
23:43:18.9918: Valid sensor identifier: /hdd/2/temperature/0
23:43:19.0108: Creating Effect Manager...
23:43:19.0108: Creating Speed Controller Manager...
23:43:19.0238: Creating Device Manager...
23:43:19.0648: Searching for "Dpsg" controllers
23:43:19.0978: Searching for "Riing" controllers
Here is the log as you requested

Hmm thats wierd.
Could you edit the TTController.Service.exe.config file and change this line
        <logger name="*" minLevel="Debug" writeTo="console" enabled="true" />

to
        <logger name="*" minLevel="Trace" writeTo="console" enabled="true" />

and post the output again?

00:03:05.8443: ================================================================
00:03:05.8853: Initializing...
00:03:05.9303: Loading plugins...
00:03:05.9303: Loading assembly: TTController.Plugin.BlinkEffect [<IP_ADDRESS>]
00:03:05.9483: Loading assembly: TTController.Plugin.ByLedColorEffect [<IP_ADDRESS>]
00:03:05.9483: Loading assembly: TTController.Plugin.FlowEffect [<IP_ADDRESS>]
00:03:05.9483: Loading assembly: TTController.Plugin.FullColorEffect [<IP_ADDRESS>]
00:03:05.9651: Loading assembly: TTController.Plugin.PulseEffect [<IP_ADDRESS>]
00:03:05.9651: Loading assembly: TTController.Plugin.RawEffect [<IP_ADDRESS>]
00:03:05.9761: Loading assembly: TTController.Plugin.RippleEffect [<IP_ADDRESS>]
00:03:05.9761: Loading assembly: TTController.Plugin.SnakeEffect [<IP_ADDRESS>]
00:03:05.9761: Loading assembly: CSCore [<IP_ADDRESS>]
00:03:05.9761: Loading assembly: TTController.Plugin.SoundEffect [<IP_ADDRESS>]
00:03:05.9911: Loading assembly: TTController.Plugin.SpectrumEffect [<IP_ADDRESS>]
00:03:05.9911: Loading assembly: TTController.Plugin.TemperatureEffect [<IP_ADDRESS>]
00:03:05.9911: Loading assembly: TTController.Plugin.WaveEffect [<IP_ADDRESS>]
00:03:05.9911: Loading assembly: TTController.Plugin.CopySpeedController [<IP_ADDRESS>]
00:03:05.9911: Loading assembly: TTController.Plugin.PwmSpeedController [<IP_ADDRESS>]
00:03:05.9911: Loading assembly: TTController.Plugin.StaticSpeedController [<IP_ADDRESS>]
00:03:06.0091: Loading assembly: TTController.Plugin.AlwaysTrigger [<IP_ADDRESS>]
00:03:06.0091: Loading assembly: TTController.Plugin.LogicTrigger [<IP_ADDRESS>]
00:03:06.0091: Loading assembly: TTController.Plugin.OneTimeTrigger [<IP_ADDRESS>]
00:03:06.0091: Loading assembly: TTController.Plugin.ProcessTrigger [<IP_ADDRESS>]
00:03:06.0091: Loading assembly: TTController.Plugin.PulseTrigger [<IP_ADDRESS>]
00:03:06.0231: Loading assembly: TTController.Plugin.TemperatureTrigger [<IP_ADDRESS>]
00:03:06.0411: Creating Config Manager...
00:03:06.0411: Loading config...
00:03:06.2571: Loading done...
00:03:06.2571: Creating DataCache...
00:03:06.2751: Creating Sensor Manager...
00:03:07.9688: Detected sensors: 54
00:03:07.9848: Creating Temperature Manager...
00:03:07.9938: Valid sensor identifier: /amdcpu/0/temperature/0
00:03:07.9938: Valid sensor identifier: /amdcpu/0/temperature/1
00:03:07.9938: Valid sensor identifier: /atigpu/0/temperature/0
00:03:08.0068: Valid sensor identifier: /hdd/0/temperature/0
00:03:08.0068: Valid sensor identifier: /hdd/1/temperature/0
00:03:08.0068: Valid sensor identifier: /hdd/2/temperature/0
00:03:08.0068: Creating Effect Manager...
00:03:08.0248: Creating Speed Controller Manager...
00:03:08.0248: Creating Device Manager...
00:03:08.0638: Searching for "Dpsg" controllers
00:03:08.0798: Searching for "Riing" controllers
00:03:08.0918: W[9802, 8001] 0, 254, 51, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
Edited the file as you instructed and here is the output. Sorry man for taking your time :"D

Nah, no worries 😄
I think you are the first one with the first gen controllers so they have not been tested. I have to find out how they initialize those, because it hangs waiting for a reply from the controller.
I'll post a release for you to test one I figure it out.

Oh how do you know that mine was a first gen controllers? Sure man ill wait thanks for your tips and help :D

Because your controller has the lowest product id (8001) that is supported by the official software.
There is also 8101 that is second gen, 8501 that is riing trio and 8601 that is an unreleased controller.
It seems like there is nothing special they do and it should work just fine, so I dont really know why it is hanging. Are you sure that any official software is not running? How about the old version from the forums? Do you have the controllers dip switches correctly set? Is the official software working if you use it?
I've added a timeout so it does not hang but just returns an error, post log again running this:
TTController_0.6.0-alpha.30.f14b7f7669c319f6457000f90a06f9d606850681.zip

Oh i see noted. Yeah all of the official software I installed, they only run in task manager and there is no window or anything to be seen. The error I get in my first post here is from the zip file you give in the forum. The controller dip is the default setting, its set to no.1.
01:17:15.4499: ================================================================
01:17:15.4968: Initializing...
01:17:15.5437: Loading plugins...
01:17:15.5437: Loading assembly: TTController.Plugin.BlinkEffect [<IP_ADDRESS>]
01:17:15.5593: Loading assembly: TTController.Plugin.ByLedColorEffect [<IP_ADDRESS>]
01:17:15.5593: Loading assembly: TTController.Plugin.FlowEffect [<IP_ADDRESS>]
01:17:15.5749: Loading assembly: TTController.Plugin.FullColorEffect [<IP_ADDRESS>]
01:17:15.5749: Loading assembly: TTController.Plugin.PulseEffect [<IP_ADDRESS>]
01:17:15.5749: Loading assembly: TTController.Plugin.RawEffect [<IP_ADDRESS>]
01:17:15.5749: Loading assembly: TTController.Plugin.RippleEffect [<IP_ADDRESS>]
01:17:15.6062: Loading assembly: TTController.Plugin.SnakeEffect [<IP_ADDRESS>]
01:17:15.6062: Loading assembly: CSCore [<IP_ADDRESS>]
01:17:15.6218: Loading assembly: TTController.Plugin.SoundEffect [<IP_ADDRESS>]
01:17:15.6218: Loading assembly: TTController.Plugin.SpectrumEffect [<IP_ADDRESS>]
01:17:15.6218: Loading assembly: TTController.Plugin.TemperatureEffect [<IP_ADDRESS>]
01:17:15.6374: Loading assembly: TTController.Plugin.WaveEffect [<IP_ADDRESS>]
01:17:15.6374: Loading assembly: TTController.Plugin.CopySpeedController [<IP_ADDRESS>]
01:17:15.6374: Loading assembly: TTController.Plugin.PwmSpeedController [<IP_ADDRESS>]
01:17:15.6374: Loading assembly: TTController.Plugin.StaticSpeedController [<IP_ADDRESS>]
01:17:15.6374: Loading assembly: TTController.Plugin.AlwaysTrigger [<IP_ADDRESS>]
01:17:15.6374: Loading assembly: TTController.Plugin.LogicTrigger [<IP_ADDRESS>]
01:17:15.6374: Loading assembly: TTController.Plugin.OneTimeTrigger [<IP_ADDRESS>]
01:17:15.6531: Loading assembly: TTController.Plugin.ProcessTrigger [<IP_ADDRESS>]
01:17:15.6531: Loading assembly: TTController.Plugin.PulseTrigger [<IP_ADDRESS>]
01:17:15.6843: Loading assembly: TTController.Plugin.TemperatureTrigger [<IP_ADDRESS>]
01:17:15.6843: Creating Config Manager...
01:17:15.6999: Loading config...
01:17:15.6999: Config does not exist! Creating default config...
01:17:15.7156: Saving config...
01:17:16.3250: Saving done...
01:17:16.3406: Loading done...
01:17:16.3406: Creating DataCache...
01:17:16.3562: Creating Sensor Manager...
01:17:20.8566: Detected sensors: 54
01:17:20.8566: Creating Temperature Manager...
01:17:20.8722: Valid sensor identifier: /amdcpu/0/temperature/0
01:17:20.8722: Valid sensor identifier: /amdcpu/0/temperature/1
01:17:20.8722: Valid sensor identifier: /atigpu/0/temperature/0
01:17:20.8722: Valid sensor identifier: /hdd/0/temperature/0
01:17:20.8722: Valid sensor identifier: /hdd/1/temperature/0
01:17:20.8878: Valid sensor identifier: /hdd/2/temperature/0
01:17:20.8878: Creating Effect Manager...
01:17:20.8878: Creating Speed Controller Manager...
01:17:20.9035: Creating Device Manager...
01:17:20.9972: Searching for "Dpsg" controllers
01:17:21.1468: Searching for "Riing" controllers
01:17:21.1624: Found 1 controller [9802, 8001]
01:17:21.1780: W[9802, 8001] 0, 254, 51, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
Here is the log with the new zip file you give :D

Yeah all of the official software I installed, they only run in task manager and there is no window or anything to be seen

Oh, so they dont show up in the task bar? Did you kill them in the task manager before running the ttcontroller?
If even the official software hangs then either you controller is dead or there is some motherboard issue, try maybe using another usb header on the motherboard?

Yeah I did kill all of them before running ur program, and I even uninstalled them.
I tried switching to another working usb header which im using for my pc casing front usb, and still the same

But does the controller work with the official software? Or was working before?
Because if it doesnt, I dont think there is anything I can do to fix this.

Yeah its not working too i guess. Coz the app wont even load, only show in the task manager. My fan is all running but only with the default red LED. Nvm then I guess I just have to buy another. Should have research earlier about their software problem. Rip money. Thanks man for your help and sorry for taking much of your time.

Yeah I think its either broken, or somethings up with the usb stuff ☹
You can try sending it for RMA but dont know how long it will take knowing TT.
I'm closing this issue but feel free to open another one if you need help. Or comment here that you got the official software working and I'll reopen.


Is it possible to increase resolution

Hello,
I am using this library with an AI thinker esp32cam module. It works great and I am able to connect through Zoneminder to it (it was not possible with other libraries I tried before).
However the quality is quite low.
I saw in the code that there is a point where SVGA quality is selected and there are comments about the other qualities. Is it possible to use the other (higher) qualities? Or there is not enough space to fit the buffers?
Thanks

Yes - here is the enum: (please do consider that higher resolution means lower FPS).
typedef enum {
    FRAMESIZE_96X96,    // 96x96
    FRAMESIZE_QQVGA,    // 160x120
    FRAMESIZE_QCIF,     // 176x144
    FRAMESIZE_HQVGA,    // 240x176
    FRAMESIZE_240X240,  // 240x240
    FRAMESIZE_QVGA,     // 320x240
    FRAMESIZE_CIF,      // 400x296
    FRAMESIZE_HVGA,     // 480x320
    FRAMESIZE_VGA,      // 640x480
    FRAMESIZE_SVGA,     // 800x600
    FRAMESIZE_XGA,      // 1024x768
    FRAMESIZE_HD,       // 1280x720
    FRAMESIZE_SXGA,     // 1280x1024
    FRAMESIZE_UXGA,     // 1600x1200
    // 3MP Sensors
    FRAMESIZE_FHD,      // 1920x1080
    FRAMESIZE_P_HD,     //  720x1280
    FRAMESIZE_P_3MP,    //  864x1536
    FRAMESIZE_QXGA,     // 2048x1536
    // 5MP Sensors
    FRAMESIZE_QHD,      // 2560x1440
    FRAMESIZE_WQXGA,    // 2560x1600
    FRAMESIZE_P_FHD,    // 1080x1920
    FRAMESIZE_QSXGA,    // 2560x1920
    FRAMESIZE_INVALID
} framesize_t;


Kotlin files in "kotlin" directory are not formatted in Android project

🐛 Describe the bug

Since I am writing my Android app in kotlin, I started putting all my source code
in src/main/kotlin. However, these files are not formatted by the gradle plugin.
⚠ Current behavior

Only files in src/main/java are formatted.
✅ Expected behavior

Files in src/main/kotlin should be formatted as well.
💣 Steps to reproduce

Create an Android project in Android Studio and configure ktfmt-gradle
Add a app/src/main/kotlin directory
Add a Kotlin file to it with some incorrect formatting
Run ./gradlew ktfmtFormat
Kotlin file in app/src/main/kotlin is not formatted

📱 Tech info

OS: macOS 11.6.1
Library/App version: ktfmt-gradle 0.7.0

Since I am writing my Android app in kotlin, I started putting all my source code
in src/main/kotlin

I believe this is happening as I'm feeding the source of the Ktfmt task with sourceSet.java.srcDirs. IIRC this should be fixed by updating the AGP version to 7.x (PRs are more than welcome).
As a workaround you should be able to workaround with:
tasks.withType<KtfmtBaseTask>().configureEach {
    source += fileTree("src/main/kotlin")
}

This is fixed by #57
Will be available with version 0.9.0


ReflectionException  Class \yii\mongodb\Connection does not exist

I am trying yii2 with mongo. This is what i did. Could be a noob error
I did Install the following
php /usr/local/bin/composer create-project yiisoft/yii2-app-basic basic 2.0.0-beta

then
php composer.phar require --prefer-dist yiisoft/yii2-mongodb "*"

but second one gave me  some error so i ran this
   "require": {
    	"yiisoft/yii2": "2.0.0-beta",
    	"yiisoft/yii2-composer": "2.0.0-beta",
        "yiisoft/yii2-mongodb": "2.0.0-beta"
    }

All fine. Yii is running
This to web.php i add
        'mongodb' => [
            'class' => '\yii\mongodb\Connection',
            'dsn' => 'mongodb://localhost:27017/cname',
        ],

Finally create this
<?php

namespace app\controllers;

use Yii;
use yii\web\Controller;
use yii\mongodb\Query;
use yii\mongodb\Collection;

class ItemController extends Controller
{
    /**
     *
     */
    public function actionIndex()
    {
        $collection = Yii::$app->mongodb->getCollection('cname');
    }

    /**
     * @param string $id MongoId string (not object)
     */
    public function actionUpdate($id)
    {
        $query = new Query;
    }
}
```

but i get this error
ReflectionException  Class \yii\mongodb\Connection does not exist

Why did this get closed without explanation? I have the same issue on 2.0.2, except that I did not have composer errors when installing.

Please report a separate issue. This one was closed by its author so probably he somehow solved it. It was long time ago.


Follow and Unfollow methods are not working.

Hi,
I am using your library and I am developing an iOS app.
I try to follow or unfollow users but not working this methods.
Can you check these methods?

Hello,
methods are fine and updated with latest instagram changes.
read here: https://github.com/TheM4hd1/SwiftyInsta/issues/218

Hi,
I know all api changes, I developed an android app and published it. Everything is working good.
Also I know about api limits.
However when I can make follow or unfollow in my android app, with your latest version of library, I can not do that.
I simply add as a pod and call your methods like you describe.
I can not understand what is the problem.

it may be related to user-agent.
check the other library, and update this issue please.
https://github.com/sbertix/Swiftagram

I think your should sign follow and unfollow request with igSignatureValue.
and you should send ig_sig_key_version in request body.

I checked that library and they sign the body excatly I do in my android code.
https://github.com/sbertix/Swiftagram/blob/d2016870a2184d72ce951523cc02406000b83e5d/Sources/SwiftagramCrypto/Extensions/Crypto.swift
You should check here.

there is no need to sign the requests with signature key in recent versions.

Yes, you are right, I checked it.
However I can not achieve follow action with your library.

It is indeed related to the user agent. It's a long known issue with SwiftyInsta.
Basically, authentication cookies and actual API requests are not mocked to be fetched by the same device, so some endpoints automatically fail, like these ones.
Adjusting the user agent for the web view authenticator in your code so that it matches the device used for all other requests, and logging back in should to the trick @ahmetkocu.

Hi,
In this library, it can be fixed I think.
I checked the user agent that is for API call, these are android device brands and models. However in loginwebview, using a different user agent, it is iphone device.

Sure it can be fixed :blush:
If you wanna work on a fix you can just port Swiftagram's implementation here.
You have my blessings 💪

check the development branch, I added a temporary way, lmk if it fixed your problem.


Add AzureCloudInstance to JS libraries

This PR adds convenience strings to sovereign cloud endpoints to make it easy for developers to onboard to a specific cloud.
This translates to adding enums for:
    // Microsoft Azure public cloud. Maps to https://login.microsoftonline.com
    AzurePublic,

    // Microsoft Chinese national cloud. Maps to https://login.chinacloudapi.cn
    AzureChina,

    // Microsoft German national cloud ("Black Forest"). Maps to https://login.microsoftonline.de
    AzureGermany,

    // US Government cloud. Maps to https://login.microsoftonline.us
    AzureUsGovernment,

Codecov Report

Merging #4106 (4740ab0) into dev (1324cee) will decrease coverage by 0.12%.
The diff coverage is 54.83%.

Flag
Coverage Δ

*Carryforward flag

msal-angular
96.31% <ø> (ø)

msal-browser
88.48% <100.00%> (ø)

msal-common
84.91% <60.00%> (-0.19%)
:arrow_down:

msal-core
76.90% <ø> (ø)

Carriedforward from 1324cee

msal-node
80.76% <40.00%> (-0.70%)
:arrow_down:

msal-react
94.17% <ø> (ø)

*This pull request uses carry forward flags. Click here to find out more.

Impacted Files
Coverage Δ

lib/msal-browser/src/cache/TokenCache.ts
96.36% <ø> (ø)

...rc/interaction_client/StandardInteractionClient.ts
98.86% <ø> (ø)

lib/msal-common/src/utils/Constants.ts
100.00% <ø> (ø)

...l-node/src/client/ConfidentialClientApplication.ts
62.50% <ø> (ø)

...ib/msal-node/src/client/PublicClientApplication.ts
77.77% <ø> (ø)

lib/msal-node/src/config/Configuration.ts
78.57% <0.00%> (-21.43%)
:arrow_down:

lib/msal-common/src/authority/Authority.ts
94.93% <36.36%> (-3.15%)
:arrow_down:

.../msal-common/src/error/ClientConfigurationError.ts
93.02% <50.00%> (-2.10%)
:arrow_down:

lib/msal-node/src/client/ClientApplication.ts
67.59% <57.14%> (-1.94%)
:arrow_down:

lib/msal-browser/src/config/Configuration.ts
94.44% <100.00%> (ø)

... and 3 more

Does cloudInstance need to be a separate property in teh configuration, or could we have it so that you can pass this enum as authority (and then augment the authority type to be string | AzureCloundInstance?

Does cloudInstance need to be a separate property in teh configuration, or could we have it so that you can pass this enum as authority (and then augment the authority type to be string | AzureCloundInstance?

This may change the public interface. I have seen changing the type, even if it supports the old type, will break apps, depending on their import of types.


Change of tweet message.

I'm submitting a ...

[ ] bug report
[x] feature request

Current behavior:

Right now, the tweet only consists of a couple of hashtags, with no message of any  other kind.
Expected behavior:

The tweet should be like Hey, Check out this new search engine with which you search on multiple platforms all at the same time.  Followed by a couple of hashtags, so that the people who see the tweet get to know about Query Server.
Steps to reproduce:

Hey. I would like to work on this.

I have already submitted a PR.

Claiming this due to inactivity!

I have already submitted a pr

It was not updated with new commits to master branch, and also since it was 18 days ago, I thought you might not be watching it, so just made a PR :smile:
Anyways, let the maintainers decide.


Bump bundler from 2.3.13 to 2.3.17

https://github.com/rubygems/rubygems/blob/master/bundler/CHANGELOG.md#2317-june-29-2022

@jurre CI run into a regression in Bundler 😞. I will release the fix tomorrow though.

2.3.18 is out!

Closing in favor of https://github.com/dependabot/dependabot-core/pull/5382


Windows 10 64-bit version 10.0.19041.1387 not working

termsrv.zip

it work for me,and I don't know is it have any bug:
[10.0.19041.1387]
LocalOnlyPatch.x64    =1
LocalOnlyOffset.x64   =8A021
LocalOnlyCode.x64     =jmpshort
SingleUserPatch.x64   =1
SingleUserOffset.x64  =D1E2
SingleUserCode.x64    =Zero
DefPolicyPatch.x64    =1
DefPolicyOffset.x64   =190D5
DefPolicyCode.x64     =CDefPolicy_Query_eax_rcx
SLInitHook.x64        =1
SLInitOffset.x64      =1E95C
SLInitFunc.x64        =New_CSLQuery_Initialize

I copy it from 19041.1379 and only change version to 19041.1387.
The ini data come from: https://github.com/affinityv/INI-RDPWRAP

work for me
rdpwrap.ini.txt

Interesting, I did autoupdate and the script hasn't found this version (I have the newest autoupdate.bat). I'll check it later.

Interesting, I did autoupdate and the script hasn't found this version (I have the newest autoupdate.bat). I'll check it later.

Check now ;)
https://github.com/sebaxakerhtc/rdpwrap.ini/commit/29f51958c85c532e68e136a0adda97079639adb9

Interesting, I did autoupdate and the script hasn't found this version (I have the newest autoupdate.bat). I'll check it later.

Check now ;) sebaxakerhtc/rdpwrap.ini@29f5195

Checked. Works good :)

Interesting, I did autoupdate and the script hasn't found this version (I have the newest autoupdate.bat). I'll check it later.

How can I get this autoupdate.bat?

Interesting, I did autoupdate and the script hasn't found this version (I have the newest autoupdate.bat). I'll check it later.

How can I get this autoupdate.bat?
I found here. Thanks.

after i autoupdate this, need login with credentials, you wanna accses my pc?

Hi,
I tried applying the latest .ini file from sebaxakerhtc and affinityv for 1387 build, RDP connection is working but mapping local printer to remote host is not working at all.
I've tried rewriting the termsrv.dll also from a 1266 build with the latest .ini files, rdp works but again remote printer redirection is not working.
In order to check that this is from the path itself, I have disable it and rolled-back to win defaults. If connected with just 1 session, (without rdpwrap) all printers are redirected.
Any ideas on how to fix this?
Thx

Any solution for x86 ???

Any solution for x86 ???

Please, attach your termsrv.dll file

termsrv.zip
x86 10.0.19044.1387 from Win 10 Starter

btw... is there a tutorial to find this offsets by myself? :-)

btw... is there a tutorial to find this offsets by myself? :-)

Of course. Look at Readme

x86 10.0.19044.1387

Values added
https://github.com/sebaxakerhtc/rdpwrap.ini/commit/9a55a24dbae7624a361032155f1b26e672ac01af

Any solution for x86 ???
rdpwrap.zip

10.0.19041.1387. This ini file worked for me X86 ,

the file worked for me but it does not allow me several connections at the same time

Windows Defender identifies the  https://github.com/sebaxakerhtc/rdpwrap/releases/download/v<IP_ADDRESS>/RDPW_installer-Black.exe  as a Trojan.
Why is it being released outside the statscorp tree?

Why is it being released outside the statscorp tree?

Because it's a Modification of original version

Why is it being released outside the statscorp tree?

Because it's a Modification of original version

Why not submit a PR, merge it and publish it under stascorp?

Why is it being released outside the statscorp tree?

Because it's a Modification of original version

Why not submit a PR, merge it and publish it under stascorp?

Because this project is abandoned.

Hi @sebaxakerhtc, v. 10.0.19041.1387 works for me with the current rbackup.ini from your repo, BUT it doesn't allow parallel connection of multiple users (which is kinda' point of this wrapper). Is that supposed to work - the old binary and new config?

Hi @sebaxakerhtc, v. 10.0.19041.1387 works for me with the current rbackup.ini from your repo, BUT it doesn't allow parallel connection of multiple users (which is kinda' point of this wrapper). Is that supposed to work - the old binary and new config?

It should work if you have an original termsrv.dll and my whole ini file.
Try uninstall and reinstall rdpwrapper and reboot your PC.
Check your filesystem for errors.

@sebaxakerhtc Sure I do. Freshly updated Win10, freshly reinstalled RDPwrap, only your ini was downloaded after it was installed again. The RDPconf shows "fully supported" but using DRPcheck, it shows the usual error speaking about the limit of connections and contacting the administrator.
It seems I'm not the only one having a problem with this, maybe Microsoft screwed something 🤔

Does it support simultaneous login of multiple Windows AD accounts?All the tests in my computer have passed, showing  “fully supported”，but i cannot log in at the same time with Windows AD account。How to fix it, thank you all。

It seems I'm not the only one having a problem with this, maybe Microsoft screwed something

Clean installation of Latest Windows 10 (build 19044.1415)
So all works fine!

Use my ini

I don't understand, are the modified binaries necessary or should this still be compatible with the original stascorp binaries + this updated rdpwrap.ini config? When I apply this rdpwrap config using stascorp binaries Terminal Services fail to start.

I don't understand, are the modified binaries necessary or should this still be compatible with the original stascorp binaries + this updated rdpwrap.ini config? When I apply this rdpwrap config using stascorp binaries Terminal Services fail to start.

No problem with original version

Somehow it started working after a system restart.

@jifengg
The offsets from your link https://github.com/affinityv/INI-RDPWRAP worked very well for 19041.1387.
My OS version is win 10 enterprise x64 10.0.19042.1415
Thank you! :-)
-Gamma

the file worked for me but it does not allow me several connections at the same time

I was having the same issue, I tried multiple versions of rdwrap.ini files with no luck. I had to uninstall the 2021-12 cumulative update to get RDPWrap working again.

Não permite fazer multi acessos, derruba o usuário, alguém pode me ajudar?
Win 10 x64 21h2 Compilação 19044.1466

There is full solution:
https://github.com/simonchen/RDPWrapper_Win10_20H2_termsrv_dll_10.0.19041.1387

There is full solution:
https://github.com/simonchen/RDPWrapper_Win10_20H2_termsrv_dll_10.0.19041.1387

Wrong solution

Hi man, if you thought it's wrong solution, you should point out which is wrong, just commented your solution is correct for prove that ? that's funny

There is full solution:
https://github.com/simonchen/RDPWrapper_Win10_20H2_termsrv_dll_10.0.19041.1387

Wrong solution The solutions are:
1. Use original rdpwrapper and autoupdate.bat from asmtron or manualy replace rdpwrap.ini

2. Use my modded version

Hi man, if you thought it's wrong solution, you should point out which is wrong, just commented your solution is correct for prove that ? that's funny~

Received, thanks.
------------------ 原始邮件 ------------------
发件人:                                                                                "stascorp/rdpwrap"                                                                                @.>;
发送时间: 2022年2月18日(星期五) 晚上8:54
@.>;
<EMAIL_ADDRESS>主题: Re: [stascorp/rdpwrap] Windows 10 64-bit version 10.0.19041.1387 not working (Issue #1630)
There is full solution:
https://github.com/simonchen/RDPWrapper_Win10_20H2_termsrv_dll_10.0.19041.1387
Wrong solution The solutions are:

Use original rdpwrapper and autoupdate.bat from asmtron or manualy replace rdpwrap.ini 2. Use my modded version
Hi man, if you thought it's wrong solution, you should point out which is wrong, just commented your solution is correct for prove that ? that's funny~

—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you commented.Message ID: @.***>


Proposal: add crypto implementations as optional import

To make the usage easier for developers, I would suggest also to publish an implementation for the signet and verifier functions like key generation, hashing etc.
I would like to include it in the src folder and not an example folder so a developer can easily import and use it.
We are not forcing someone to use it, but we offer a challenged implementation that is ready to be used in the browser or in nodejs.

Since we are planning to split it up in multiple packages, we could create two implementations that can be used and can be used on demand. Then everyone should be happy

That's good idea :)
How it's done is very simple. We just recover the removed crypto functions in #60. crypto.ts, crypto-broswer.ts

I think providing some default crypto can be very nice. Deciding which algorithms to support might get a bit more complex.
I suggest the following:
packages

@sd-jwt/crypto-nodejs
@sd-jwt/crypto-react-native
@sd-jwt/crypto-browser

Algorithms

SHA2-256
Ed25519
ES256

But just to be clear, these should match an interface provided by the core library and users can provide their own cryptography.

@berendsliedrecht yeah, I would go with the default ones that are supported natively by Node or the browser. For me the EC based ones would be enough since RSA is not the way to go today.

Agreed.
Supporting React Native is also good idea. (Might need to check the Expo)

@berendsliedrecht yeah, I would go with the default ones that are supported natively by Node or the browser. For me the EC based ones would be enough since RSA is not the way to go today.

I think supporting all the native ones is a good goal, but quite a bit. Also, it is not consistent between platforms. We could diverge them, but I think it would provide a nicer experience for all the packages to have the same functionality and keep it limited at a start. Especially with key management, users will likely already have some mechanism for that, so I don't expect heavy usage of these packages.

@berendsliedrecht yeah, I would go with the default ones that are supported natively by Node or the browser. For me the EC based ones would be enough since RSA is not the way to go today.

I think supporting all the native ones is a good goal, but quite a bit. Also, it is not consistent between platforms. We could diverge them, but I think it would provide a nicer experience for all the packages to have the same functionality and keep it limited at a start. Especially with key management, users will likely already have some mechanism for that, so I don't expect heavy usage of these packages.

I would prefer to start with a "mvp" approach, giving people an implementation for EC for Browser, Node and React Native, and for hash maybe SHA 256. Of course we will not limit it to this, but having this generic interface allows everyone to append one more crypto implementation.
With the minimal approach we have to be sure that we provide a challenged implementation to avoid bad PR ;)

Which way do you prefer?

using platform's crypto features (like node:crypto from nodejs, subtle from browser etc.)
using pure js implementation like noble-curve

I am a fan of native ones because there is less third party dependency. We already have them implemented in the example so it's not big deal to finish this task (for now).
In case we see problems with the implementation we can quickly add noble-curve.

Okay Let's try native one first :)

Native has my preference as well. That way it would also be easier to add potential support for bun or deno and what not.

I'll work on the nodejs and browser first :)

Closing this since it got implemented in #106