ICD: Publisher-selected maximum subscription interval.

Publisher-selected maximum subscription interval enforced according to <IP_ADDRESS>. (Subscribe Interaction Limits)
Unit tests ran successfully.

Implements the spec PR #6516

[x]  Do not read attribute store (or call EmberAf or call zap-generated anything) in IM layer (ReadHandler).

I have removed all references to the ZAP-generated code from the ICD files (table and server). The server attributes are now initialized from the ZAP files on the cluster initialization callback.


Data viewer title should be less verbose and include variable shape if any

Feedback from Jill: 'Data Viewer' is included in every data viewer's title, which takes up a lot of space. See if we can shorten the title and include more info like the shape of the variable. Also see if we can associate an icon with the viewType so the tab doesn't just show the default text editor seti icon.

Closing this issue as there haven't been enough upvotes on this feature request since it was created


Can't undo cell DND

Drag cell in notebook to new location
cmd+z, nothing happens

Possibly only reproes after doing https://github.com/microsoft/vscode/issues/131936

The trick is, after I move a markdown cell or do something else to put focus in the webview, I can't do undo/redo/copy/paste anymore because the webview is never unfocused

This is me from e96fcce300cb6fe6b58b416d3797049a7edb1f28. I didn't understand why that condition was different from the focus handler. Now I get it but I don't understand why that condition is there at all. @rebornix Is the idea to not set _webviewFocused when the notebook editor is not focused? I think we should be setting this._webviewFocused = without the condition


Default packaging uses german as main language for installer

When I use package script, the resulting exe/dmg is coming out with using german language. I am not sure if this is an issue for this repository or electron-builder (or any other repo).
Anyone have a solution for customising this installer section? or am I doing something wrong?

Try asking for help in the electron-builder. They can give you better guidance for this over there


Fix lndLogGetLevel to apply the most-recent log level when none is detected

In some cases, multi-line log output was output at its value for the first line,
but in the trace log in following lines. For example, in this output:
zap:lnd  [DBG]  2018-06-17 18:30:35.051 [DBG] CRTR: New channel update applied: (*channeldb.ChannelEdgePolicy)(0xc420e74310)({ +0ms
zap:lnd  [DBG]   SigBytes: ([]uint8) (len=71 cap=71) { +0ms
zap:lnd  [DBG]   }, +0ms
zap:lnd  [DBG]   sig: (*btcec.Signature)(), +0ms
zap:lnd  [DBG]   ChannelID: (uint64)<PHONE_NUMBER>626526208, +0ms
zap:lnd  [DBG]   LastUpdate: (time.Time) 2018-06-17 18:30:26 -0500 CDT, +0ms
zap:lnd  [DBG]   Flags: (lnwire.ChanUpdateFlag) 1, +0ms
zap:lnd  [DBG]   TimeLockDelta: (uint16) 6, +0ms
zap:lnd  [DBG]   MinHTLC: (lnwire.MilliSatoshi) 1000 mSAT, +0ms
zap:lnd  [DBG]   FeeBaseMSat: (lnwire.MilliSatoshi) 1 mSAT, +0ms
zap:lnd  [DBG]   FeeProportionalMillionths: (lnwire.MilliSatoshi) 10 mSAT, +0ms
zap:lnd  [DBG]   Node: (*channeldb.LightningNode)(), +0ms
zap:lnd  [DBG]   db: (*channeldb.DB)() +1ms
zap:lnd  [DBG]  }) +0ms
zap:lnd  [DBG]   +0ms
Previously the first line would be marked DBG, while the others were marked TRC.

/cc @mrfelton


Problem installing packages

Hi, I made a new installation cloning the repo, and following https://themesberg.com/docs/volt-bootstrap-5-dashboard/getting-started/quick-start/ but when doing npm install I get this error, tried few things, but I can't make it work.
sammy@a090c903117d:/var/www$ npm install
npm WARN deprecated<EMAIL_ADDRESS>Modern JS already guarantees Array#sort() is a stable sort, so this library is deprecated. See the compatibility table on MDN: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort#browser_compatibility
npm WARN deprecated<EMAIL_ADDRESS>See https://github.com/lydell/source-map-url#deprecated
npm WARN deprecated<EMAIL_ADDRESS>this library is no longer supported
npm WARN deprecated<EMAIL_ADDRESS>Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated<EMAIL_ADDRESS>https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated<EMAIL_ADDRESS>See https://github.com/lydell/source-map-resolve#deprecated
npm WARN deprecated<EMAIL_ADDRESS>Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
npm WARN deprecated<EMAIL_ADDRESS>The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated<EMAIL_ADDRESS>Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated<EMAIL_ADDRESS>request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated<EMAIL_ADDRESS>Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
npm WARN deprecated<EMAIL_ADDRESS>This version of tar is no longer supported, and will not receive security updates. Please upgrade asap.
npm ERR! code 1
npm ERR! path /var/www/node_modules/node-sass
npm ERR! command failed
npm ERR! command sh -c node scripts/build.js
npm ERR! Building: /usr/bin/node /var/www/node_modules/node-gyp/bin/node-gyp.js rebuild --verbose --libsass_ext= --libsass_cflags= --libsass_ldflags= --libsass_library=
npm ERR! gyp info it worked if it ends with ok
npm ERR! gyp verb cli [
npm ERR! gyp verb cli   '/usr/bin/node',
npm ERR! gyp verb cli   '/var/www/node_modules/node-gyp/bin/node-gyp.js',
npm ERR! gyp verb cli   'rebuild',
npm ERR! gyp verb cli   '--verbose',
npm ERR! gyp verb cli   '--libsass_ext=',
npm ERR! gyp verb cli   '--libsass_cflags=',
npm ERR! gyp verb cli   '--libsass_ldflags=',
npm ERR! gyp verb cli   '--libsass_library='
npm ERR! gyp verb cli ]
npm ERR! gyp info using<EMAIL_ADDRESS>npm ERR! gyp info using<EMAIL_ADDRESS>| linux | x64
npm ERR! gyp verb command rebuild []
npm ERR! gyp verb command clean []
npm ERR! gyp verb clean removing "build" directory
npm ERR! gyp verb command configure []
npm ERR! gyp verb find Python Python is not set from command line or npm configuration
npm ERR! gyp verb find Python Python is not set from environment variable PYTHON
npm ERR! gyp verb find Python checking if "python3" can be used
npm ERR! gyp verb find Python - executing "python3" to get executable path
npm ERR! gyp verb find Python - executable path is "/usr/bin/python3"
npm ERR! gyp verb find Python - executing "/usr/bin/python3" to get version
npm ERR! gyp verb find Python - version is "3.9.2"
npm ERR! gyp info find Python using Python version 3.9.2 found at "/usr/bin/python3"
npm ERR! gyp verb get node dir no --target version specified, falling back to host node version: 19.4.0
npm ERR! gyp verb command install [ '19.4.0' ]
npm ERR! gyp verb install input version string "19.4.0"
npm ERR! gyp verb install installing version: 19.4.0
npm ERR! gyp verb install --ensure was passed, so won't reinstall if already installed
npm ERR! gyp verb install version is already installed, need to check "installVersion"
npm ERR! gyp verb got "installVersion" 9
npm ERR! gyp verb needs "installVersion" 9
npm ERR! gyp verb install version is good
npm ERR! gyp verb get node dir target node version installed: 19.4.0
npm ERR! gyp verb build dir attempting to create "build" dir: /var/www/node_modules/node-sass/build
npm ERR! gyp verb build dir "build" dir needed to be created? /var/www/node_modules/node-sass/build
npm ERR! gyp verb build/config.gypi creating config file
npm ERR! gyp ERR! UNCAUGHT EXCEPTION
npm ERR! gyp ERR! stack TypeError: Cannot assign to read only property 'cflags' of object '#<Object>'
npm ERR! gyp ERR! stack     at createConfigFile (/var/www/node_modules/node-gyp/lib/configure.js:117:21)
npm ERR! gyp ERR! stack     at /var/www/node_modules/node-gyp/lib/configure.js:84:9
npm ERR! gyp ERR! stack     at FSReqCallback.oncomplete (node:fs:180:23)
npm ERR! gyp ERR! System Linux 5.15.0-58-generic
npm ERR! gyp ERR! command "/usr/bin/node" "/var/www/node_modules/node-gyp/bin/node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library="
npm ERR! gyp ERR! cwd /var/www/node_modules/node-sass
npm ERR! gyp ERR! node -v v19.4.0
npm ERR! gyp ERR! node-gyp -v v7.1.2
npm ERR! gyp ERR! Node-gyp failed to build your package.
npm ERR! gyp ERR! Try to update npm and/or node-gyp and if it does not help file an issue with the package author.
npm ERR! Build failed with error code: 7

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/sammy/.npm/_logs/2023-01-17T11_03_41_371Z-debug-0.log

Nodejs v19.4.0
npm 9.3.0
Python 3.9.2
Ubuntu 22

Hello,
Thank you for using Creative TIM!
We could not recreate the issue.
Can you try again using npm v6.14 and node v14.17 and let us know if that fixes the problem?
Thank you.

yes, it works with those versions, any way to upgrade to a higher node version?
thank you for your reply.


Stawberryshake incorrectly picks .net9 Tool in .net8 project

Product
Strawberry Shake
Version
14.2.0
Link to minimal reproduction
https://github.com/adminnz/Issue
Steps to reproduce

Create new .net8 Class Library
Open terminal in solution folder
Run dotnet add package StrawberryShake.Blazor
Run dotnet new tool-manifest
Run dotnet tool install StrawberryShake.Tools
Run dotnet graphql init https://demo.chillicream.com/graphql/ -n CryptoClient -p ./Demo

What is expected?
Runs the strawberryshake.tools\14.2.0\tools\net8.0\any\dotnet-graphql.dll
What is actually happening?
Attempts to run the strawberryshake.tools\14.2.0\tools\net9.0\any\dotnet-graphql.dll
Relevant log output
You must install or update .NET to run this application.

App: C:\Users\<redacted>\.nuget\packages\strawberryshake.tools\14.2.0\tools\net9.0\any\dotnet-graphql.dll
Architecture: x64
Framework: 'Microsoft.NETCore.App', version '9.0.0' (x64)
.NET location: C:\Program Files\dotnet\

The following frameworks were found:
  6.0.35 at [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  6.0.36 at [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  8.0.10 at [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  9.0.0-rc.2.24473.5 at [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]

Learn more:
https://aka.ms/dotnet/app-launch-failed

To install missing framework, download:
https://aka.ms/dotnet-core-applaunch?framework=Microsoft.NETCore.App&framework_version=9.0.0&arch=x64&rid=win-x64&os=win10

Additional context
I'm not sure if there is a command argument i can pass for the dotnet graphql init to make it use the .net8 tool rather than the .net9.
Upgrading the project to .net9 is not an option.
Also just FYI: The slack link when creating an issue is no longer valid. It says:
This link is no longer active

To join this workspace, you’ll need to ask the person who originally invited you for a new link.

Found out that if the net9 RC was installed on the machine, it causes the tool to break. Installing the .net 9 SDK and redoing the steps works against a .net 8 project.


Fix: wrong input values used when creating a base image

Some input fields were not updated during the migration to the newest version of the GraphQL API.
This change fixes how localized fields are provided in the mutation when creating a base image.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 0.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
0

Relevant Lines:
0

💛  - Coveralls


Index recommendation on jobGraph Collection

Hi! We've been happily using Hangfire.Mongo for the last 6 months using a cluster hosted on Mongo Atlas.
However, there are a few index recommendations on the jobGraph collection that are consistently being recommended, so I figured I would let you know:
{ Queue: 1, _t: 1, FetchedAt: 1 }
{ Key: 1, _t: 1 }

Thanks for putting this library together btw it's been a life-saver!

@samuelcadieux,
Now we are at the subject, does it recommend to drop any indexes?
Thanks!

Hey Jonas, I've double-checked both our dev and prod cluster and the only recommendation is to drop the ExpireAt index from the locks collection.

Got it. thanks!

Confirmed it was fixed in 1.9.14 thanks for the quick turnaround!


Firefox addon url

please fix url

Where is this URL (which one?) in the code? Then it should be easy to prepare a PR.


Discussion: Automatic retries

At the moment, the client does not automate any retries. This issue is to capture the current behaviour of the client library in various failure scenarios - taken from here.
Points of failure client-broker over gRPC
There are three points of contact:

Client initiating an operation on the broker

failJob
publishMessage
createWorkflowInstance
resolveIncident

Worker activating jobs

activateJobs

Worker completing / failing job

completeJob
failJob

Current Failure Modes
Looking at the current behaviour of each one:

Client initiating an operation on the broker.

If the client is started and the broker is not contactable, any operations will throw.
If the broker becomes available, operations succeed.
If the broker goes away, operations throw again.
No automatic retries.

Worker activating jobs

If the worker is started and the broker is not contactable, an error is printed to the console.
If the broker becomes available, the worker activates jobs.
If the broker goes away, no error is thrown or printed.
If the broker comes back, jobs are activated.
In this case, the worker polling is an automatic retry.

Worker completing jobs

If the broker goes away after the worker has taken a job, the worker throws Error: 14 UNAVAILABLE when it attempts to complete the job.
No automatic retry.

Ways the broker could go away / be unavailable:

Broker address misconfigured.
Transient network failure.
Broker under excessive load.

Broker Address Misconfigured
This is an unrecoverable hard failure. Retries will not fix this.
Transient network failure
Some temporary disruption in connectivity between worker and broker. This could include a broker restarting or (potentially) a change in DNS (have to test this).
A retry will deal with this case if the transient network failure is fixed before the retries timeout.
Broker is under excessive load and cannot respond
In this case, retries may actually make it worse. Zeebe is horizontally scalable, but I have driven it to failure on a single node by pumping in a massive number of workloads when it is memory starved (I can kill it with 2GB of memory, but haven't yet with 4GB) or runs out of disk space (a slow exporter with a high through-put can do this). Having automated retries will not recover any of these situations.
If the broker is experiencing excessive load because of a traffic spike, then automated retries may drive it to failure, whereas workers failing to complete tasks once and letting the broker reschedule them may allow the broker to recover.
Other failure modes not distinguished
The as-yet unknown unknowns. Any ideas?

Conclusions
I'm not yet sure that automatic retry is (a) necessary; (b) a good idea.
The transient network failure seems to be the only case. I'm not sure how much of an issue that is in an actual system, and if it warrants complicating the code, or the potential downside of hammering a broker when it is experiencing excessive load (which will be either ineffective if it is a hard failure, and could contribute to a hard failure if it is a spike).

I'm open to more data on this, but I don't have a case for implementing retries yet.

Client-side gPRC load-balancing may be one option (see here.
This would look like making the brokerAddress an string|string[]. If it is an array of broker addresses, then the client lib would implement simple round-robin. If a call fails, it will rotate through the others until one succeeds or they all failed.
We could track which ones are failing, and weight repeated failures to try those gateways less often, then heal it on success.

I'd also look at implementing leaky bucket so you can ensure that it's not a straight retry which would resolve the hammering the broker.

 The two built-in policies in the gRPC-Go library are the roundrobin and grpclb policies. ref: On gRPC Load-balancing
The underlying node grpc library does support retries, via interceptors (see here). To get support for retries via this method would probably involve adding support to (node-grpc-client)[https://www.npmjs.com/package/node-grpc-client]. They are amenable to PRs - I added streaming support there to get it working for the Zeebe client.

Yeah, it's a cost/benefit analysis. Have to see where it makes sense to locate load-balancing and whether it makes sense to implement automatic retries.
gRPC load-balancing is usually done with either a client library implementation or some kind of service mesh, like Istio+Envoy. Retries is either automated in the client lib, or the call is failed and it is up to the application to handle it in the context of the business process.
A simple round-robin in the client would be a way to do both load-balancing and a short period retry that handles a gateway failure. It wouldn't give you a long-running retry (for example if the broker goes away ála Google Cloud disappearing or a disk filling up), but in that case you may want the business process to fail fast and handle the failure systemically.
I think start from a simple round-robin and put in more sophisticated retry behaviour if there is a use-case for it.

Noting for future reference another Node gRPC library that provides a simple linear retry: grpc-caller
It uses the same interface as async.retry.
Could be a drop-in replacement for node-grpc-client, which would give zeebe-node simple retry for free.

Addressed by #40 based on a concrete use case.


copr: add (non-)vectorized WeekWithoutMode, YearWeekWithMode & YearWeekWithoutMode

Signed-off-by: wangggong<EMAIL_ADDRESS>
What problem does this PR solve?
Issue Number: #9016
Problem Summary:
What is changed and how it works?
What's Changed:
Add scalar & vectorized copr functions WeekWithoutMode, YearWeekWithMode & YearWeekWithoutMode
Related changes
Check List
Tests

Unit test

Side effects
Release note
No release note.

@Xuanwo CI failed, PTAL
Please tell me if there is something wrong with the code. Thx.

@Xuanwo CI failed, PTAL
Please tell me if there is something wrong with the code. Thx.

/retest

/retest

/label sig/coprocessor

/label sig/coprocessor

/sig copr

/sig copr

/retest

/retest

/run-all-tests

/run-all-tests

/merge

/merge


Add Turkish language strings

Sorry for the delay. Looks good to me. Will be in next release.

@egeesin Just thought I'd mention that this is finally in the newest release

I'm doing a major refactor and most of the translations have been removed/changed. If your interested in updating them here are the new translations.


update default registry domain

update default registry domain from registry.ollama.ai to ollama.com
migrate models by moving models to their new location. this is one directional

I think we should resurrect this one


dendrite: add some kind of security for inter communication between nodes

I'm interested in building distributed applications in golang and have been looking for a potential DHT library. This appears to be a very good option out of the available choices.
Do you plan on finishing this feature?
dendrite: add some kind of security for inter communication between nodes
I could start working on this feature. Do you have any opinions on how it should be implemented?

I'm honestly not sure what would be the best approach. If a shared private key is acceptable, then we could possibly just encrypt the data before sending it to the wire. On the other hand, we could further explore 0mq protocol capabilities regarding authentication and encryption (see CurveMQ).
Current dendrite implementation is done with ZeroMQ for networking, but it is pluggable and other transport methods can be written. If CurveMQ is to be implemented, it will be kinda coupled with ZeroMQ implementation and won't work with basic HTTPS implementation one day (if someone decides to implement it).
Option 1: use shared private key to encrypt and sign the data messages on top of plain ZMQ.
Option 2: implement CurveMQ for ZMQ transport implementation.
Option 3: use some other generic approach for all transports involved.

I'm trying to make a basic example of usage of the library and I was basing it off your usage example but I get the following error:
not enough arguments in call to dendrite.InitZMQTransport

Is the usage example out of date?

Yes. Just pass the nil as a third argument to that call. It allows custom loggers to be used. I'll update the readme.

Yeah, I noticed it was a logger but I wasn't sure what to pass, thanks for the tip with passing nil. Sorry I'm new to golang too so I'm still stumbling a little.


Cannot reference sizes that have keys with decimals

🐛 Bug Report
Incorrect sizes are given when using size keys that have decimal places when using w and h utility props. Instead of the setting the width or height value to the value defined in the theme, it sets the value to the key as a pixel value.
This issue doesn't seem to arise when referencing size keys that do not have decimals.
To Reproduce
Steps to reproduce the behavior:

add a sizes key to the theme with a number with a decimal as the key with a value. For example:

const theme = {
  ...
  sizes: {
    ...
    12.5: '3.125rem',
  }
}

reference that size key in a w or h utility prop. For example:

<x.div w={12.5} h={12.5} />

Expected behavior
I expected the div to have a width and height of 3.125rem instead of 12.5px.
Link to repl or repo
Code Sandbox: https://codesandbox.io/s/xstyled-v2-playground-forked-iu87j?file=/src/App.js

I also noticed that if I have the size key 3.5:
const theme = {
  sizes: {
    3.5: '0.875rem',
  },
};

and set the w & h utility props to w={3.5} h={3.5} the width and height both become e, which is invalid css. I feel that this may be related. If it's not it should be another issue.
I have also added this example to the Code Sandbox linked in the original issue.

Hi Greg,
We encounter the same case using CSS properties in a styled component, with padding declaration in our side.
https://codesandbox.io/s/young-sea-peeur?file=/src/App.js
padding-top: 1;
padding-left: 0.5;

outputs:
padding-top: 0.25rem;
padding-left: 0.5px;

Note that reverting from 3.1.2 to 3.1.0 resolve it for us in our project.
This is not the case in the Codesandbox linked upper: it need to use 2.5.0 to fix

Any progress on this bug?

What if you make the key a string instead? Wondering if there’s some floating point stuff happening that is breaking comparison


Hello, I'm very interested in your work. When will the code for semantic segmentation applications be open ?

The work on land cover mapping is very meaningful. I hope the relevant code can be opened as soon as possible

您好，您的邮件已收到，我会尽快回复，谢谢！——徐馨怡

Hi @SHyeong1 , I am sorry I didn't get you. I mean I haven't mailed you in this.


host copyright.html from /data/

https://organicmaps.app/terms/
https://github.com/organicmaps/organicmaps/blob/master/data/copyright.html
Currently, the copyright page isn't hosted, and directs to the raw HTML file on github. we should properly host & link to it. (some sort of symlink would be good for automatic updates, but idk if it's possible from another repo)

Why it should be hosted on the web site? That copyright page is about the app, not about the website.
https://htmlpreview.github.io/?https://github.com/organicmaps/organicmaps/master/data/copyright.html


httpstat.us/504 returns a 200

When requesting to page for 504 status codes it actually returns a response with status code 200:
$ curl -v https://httpstat.us/504
*   Trying <IP_ADDRESS>:443...
* TCP_NODELAY set
* Connected to httpstat.us (<IP_ADDRESS>) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: C=US; ST=CA; L=San Francisco; O=Cloudflare, Inc.; CN=sni.cloudflaressl.com
*  start date: Jul 28 00:00:00 2020 GMT
*  expire date: Jul 28 12:00:00 2021 GMT
*  subjectAltName: host "httpstat.us" matched cert's "httpstat.us"
*  issuer: C=US; O=Cloudflare, Inc.; CN=Cloudflare Inc ECC CA-3
*  SSL certificate verify ok.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Using Stream ID: 1 (easy handle 0x5648d9576ea0)
> GET /504 HTTP/2
> Host: httpstat.us
> user-agent: curl/7.68.0
> accept: */*
>
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 256)!
< HTTP/2 200
< date: Thu, 20 May 2021 09:52:28 GMT
< content-length: 0
< cache-control: private
< x-aspnetmvc-version: 5.1
< access-control-allow-origin: *
< access-control-expose-headers: Link, Content-Range, Location, WWW-Authenticate, Proxy-Authenticate, Retry-After
< x-aspnet-version: 4.0.30319
< request-context: appId=cid-v1:7585021b-2db7-4da6-abff-2cf23005f0a9
< access-control-expose-headers: Request-Context
< x-powered-by: ASP.NET
< set-cookie: ARRAffinity=39467ba08a17f8976ce282973f000131800a90e092db2082961e59a18502a560;Path=/;HttpOnly;Domain=httpstat.us
< cf-cache-status: DYNAMIC
< cf-request-id: 0a2ac9e3920000012afc2a3000000001
< expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
< report-to: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report?s=f6Gr%2BvU6fBlXSHb%2F2JZPTdgzjI8o0MwsElOJgzHf45RGtTS66jyB7YwZmKWqFHQ6ZxnE1k4MJgcvwfRzxhwTbtWQtoLAxaNMLFlkSg%3D%3D"}],"group":"cf-nel","max_age":604800}
< nel: {"report_to":"cf-nel","max_age":604800}
< server: cloudflare
< cf-ray: 6524ac18eaeb012a-AMS
< alt-svc: h3-27=":443"; ma=86400, h3-28=":443"; ma=86400, h3-29=":443"; ma=86400
<
* Connection #0 to host httpstat.us left intact

This is intended behavior to address sustained abuse
See https://github.com/Readify/httpstatus/issues/89#issuecomment-705978272

Thanks @bplowry

Some additional notes - https://github.com/Readify/httpstatus/issues/97


[Problem] -f, --filename didn't work on ud -m

Current version.
Both -f, --filename filename option not worked.
(-de, --description can work)

This has since been fixed. No idea on the timeframe.


Uploading Profile Pictures and Banner Pictures on Edit Profile

Description
Uploading pictures to update a profile picture or a banner picture doesn't automatically change on the app. The previously used profile and banner pictures will remain. The profile picture on each post made by the user will be changed to the updated picture, but the profile page won't update.
Steps to reproduce

Go to the profile page and select "Edit Profile"
Upload a new picture for your profile and for your banner pictures, and then save that information.
See if the profile page is updated with the new uploaded images, along with the profile picture on each post.

Expected Behavior
The profile page should be updated as soon as I save the edited profile's information. We should see the new uploaded profile and banner pictures right away.
Actual Behavior

The profile page will keep the previous profile and banner pictures, and not update to the new saved profile pictures.

Additional context
If you edit your profile, save the information and then search the account on the web app, it will show you the new updated profile information, so the profile is being edited, it's just not updating on the iOS app.

I agree this doesn't work correctly. I have to close the app and reopen for it to update.


Add composer test command

composer test seems like a common convention for running tests in PHP projects.
This change adds test as a script in the composer.json. When you run composer test the single test file is run.

Coverage remained the same at 100.0% when pulling 87885c54fc299211b8168e9d77415cea320a9ab7 on jazzdan:patch-1 into 4438d81ec66a1460e6da408ce974b7e41a753212 on phospr:master.

Thanks, @jazzdan.  Would it not be better to just have the following, in case we add more tests?
    "scripts": {
        "test": "phpunit tests"
    }

Ah yes of course @tomhv, one sec will update.

Coverage remained the same at 100.0% when pulling 6ee62dff9d3ecc4e78e8b93e3a8a924fb840bfce on jazzdan:patch-1 into 4438d81ec66a1460e6da408ce974b7e41a753212 on phospr:master.

Thanks again, @jazzdan.


[Bug] Private connectors are not listed in the low-code

Description:
Private connectors are not listed in the low-code.
Steps to reproduce:

Create and publish a private connector to the Ballerina central.
Try to add that connector from the low-code connector flow.

Affected Versions:
Dev

RCA
the issue was  BALLERINA_DEV_CENTRAL environment variable not configured correctly,.


Script to regenerate conda environment and associated issues

This PR addresses the following:

Add a conda equivalent of the script regenerate_venv.sh
Put the conda environment in /opt/environments
Some common code between regenerate_conda_env and airflow_wrapper is moved to a separate script
Testing was performed under Airflow2 on DEV under both python3.6 and python3.9

Closes https://github.com/hubmapconsortium/ingest-pipeline/issues/671


QemuVideoDxe SCT inconsistent test failures and logging issue (Bugzilla Bug 3601)

This issue was created automatically with bugzilla2github
Bugzilla Bug 3601
Date: 2021-09-01T11:47:35+00:00
From: Shashi Mallela <<shashi.mallela>>
To:   Edhay <<edhaya.chandran>>
CC:   edhaya.chandran, edk2+bugs+int+994+563148131503455288, shashi.mallela, Sunny.Wang
Last updated: 2022-11-07T10:13:50+00:00

Comment 17123
Date: 2021-09-01 11:47:35 +0000
From: Shashi Mallela <<shashi.mallela>>

Industry Specification: ---
Release Observed: EDK II Master
Releases to Fix: EDK II Master
Target OS: ---

In SBSA SCT tests,the main UEFI failures (120 instances) are around the EFI_GRAPHICS_OUTPUT_PROTOCOL QueryMode() and SetMode().
There are 2 issues seen as below:-

On testing with the RELEASE version of edk2 images and analyzing the logs(as seen in the Release section of the attached log file), it is seen that the errors are around "compare Info structure" (in GraphicsOutputBBTestConformance.c  and GraphicsOutputBBTestFunction.c files of edk-test) which compares the queried Info structure with the Info structure within the current instance of EFI_GRAPHICS_OUTPUT_PROTOCOL. Both these files have code to print out the Info structures(mentioned above) after SetMode() followed by QueryMode(),but the output only shows all information in the queried Info structure.The same Info structure information from the current instance of EFI_GRAPHICS_OUTPUT_PROTOCOL is not printed.

To confirm QemuVideoDxe GOP implementation handling the full ABI definition as per UEFI spec,i added debug logs in the Gop.c file and confirmed that all members of the Info structure are being implemented in both QueryMode() and SetMode()(Please refer to the prints labelled "QueryMode Result.." and "Reference Info..." in the attached SCT logfile under debug section.Since the returned query Info is seen in the logs,the issue is with printing the Info structure from current instance of EFI_GRAPHICS_OUTPUT_PROTOCOL(lines 158 in GraphicsOutputBBTestFunction.c and lines 526 in GraphicsOutputBBTestConformance.c)

While arriving at the debug logs (indicated in 1 above),an interesting observation was that with DEBUG version of edk2 images,all test cases around "compare Info structure"(which failed in the RELEASE version) PASSED (can be seen in the attached logfile under debug section). The print Info issue stayed even with debug logs.However,a newer series of errors showed up,this time around "compare FrameBufferSize"(in GraphicsOutputBBTestFunction.c). But these FrameBufferSize errors are within the scope of QemuVideoDxe and can be handled by edk2 separately,so we can ignore these errors in the scope of sct tests for now.

Please provide your comments on the errors discrepancy seen between RELEASE & DEBUG images and also the print issue in GraphicsOutputBBTestFunction.c & GraphicsOutputBBTestConformance.c.

Comment 17892
Date: 2021-12-02 01:43:16 +0000
From: Edhay <<edhaya.chandran>>
Hi Shashi,

Regarding the printing of current instance of EFI_GRAPHICS_OUTPUT_PROTOCOL, it is agreed that there is an issue. We suspect this is to do with the print buffer. We are checking the same.

Regarding the issue of discrepancy of results themselves.
Release version : Fail. Debug version: Pass
Could you please update how you acquired these release and debug versions?
From the prints in the logs, it points that you are using the same ACS image.

Comment 17124
Date: 2021-09-01 11:59:16 +0000
From: Shashi Mallela <<shashi.mallela>>
Created attachment 821
SCT Logs with edk2 RELEASE & DEBUG images
Attachment: SCT_Release_and_Debug.log

Comment 17137
Date: 2021-09-02 10:23:27 +0000
From: Edhay <<edhaya.chandran>>
@Shashi,
Please provide an indication of the bug in edk2-test.

Comment 17144
Date: 2021-09-02 10:40:07 +0000
From: Shashi Mallela <<shashi.mallela>>
The files GraphicsOutputBBTestConformance.c and GraphicsOutputBBTestFunction.c(as indicated in the description and attached log) in edk2-test are the sources of this bug.

Comment 17902
Date: 2021-12-02 09:46:01 +0000
From: Edhay <<edhaya.chandran>>
Check for '\n' in other assert prints.

Comment 18130
Date: 2022-01-13 09:16:58 +0000
From: Edhay <<edhaya.chandran>>
Mail Shashi Mallela directly.

Comment 19959
Date: 2022-11-07 10:13:50 +0000
From: Edhay <<edhaya.chandran>>
The SCT part of the solution is
https://edk2.groups.io/g/devel/topic/92068027
upstreamed by the commmit-id:
https://github.com/tianocore/edk2-test/commit/4a25c3b3c79f63bd9f98b4fffcb21b5c66dd14bb
Keeping this ticket open until the edk2 solution is upstreamed.

Comment 19025
Date: 2022-06-02 11:12:01 +0000
From: Edhay <<edhaya.chandran>>
Hi Shashi,
Could you further update on the steps to reproduce the same?
Is the test system used QEMU? If yes, which architecture was used?

Comment 19019
Date: 2022-06-02 07:49:45 +0000
From: Edhay <<edhaya.chandran>>
Sent a mail to Shashi regarding our comments/queries.

Comment 19030
Date: 2022-06-02 13:45:24 +0000
From: Shashi Mallela <<shashi.mallela>>
Yes, the testing used qemu and platform was sbsa-ref(qemu).
The edk2 firmware was generated for (aarch64)sbsa platform too.

Comment 19020
Date: 2022-06-02 09:43:19 +0000
From: Shashi Mallela <<shashi.mallela>>
(In reply to Edhay from comment #4)
> Hi Shashi,
>
> 1. Regarding the printing of current instance of
> EFI_GRAPHICS_OUTPUT_PROTOCOL, it is agreed that there is an issue. We
> suspect this is to do with the print buffer. We are checking the same.
>
> 2. Regarding the issue of discrepancy of results themselves.
> Release version : Fail. Debug version: Pass
> Could you please update how you acquired these release and debug versions?
> From the prints in the logs, it points that you are using the same ACS image.
Hi Edhay,
I generated the RELEASE and DEBUG versions separately by building edk2 firmware with "-b RELEASE" and "-b DEBUG" options

Comment 19241
Date: 2022-07-14 10:35:11 +0000
From: Sunny Wang <<Sunny.Wang>>
For the inconsistent test failure issue, the patches were sent out by Dimitrije Pavlov<EMAIL_ADDRESS>It can be fixed by either of the following patches.

QemuVideoDxe improvement - https://edk2.groups.io/g/devel/topic/patch_v1_1_1/92050521
SCT fix - https://edk2.groups.io/g/devel/topic/92068027

For the logging issue, we still need someone to fix it and send out a patch.


JSDoc @summary tag

I propose to use the jsdoc @summary tag when showing the hover information.

/**
 * @summary
 * Get Document body.
 *
 * @description
 * Get the document body of the view. Sometimes, it is useful to render an
 * alert view or notify the user of something that have happened. These views
 * are owned by the document body, so to reference the document body, you use
 * `this.document`. And it is only, `ContentBaseView` and it derivatives that
 * has a reference to the document body.
 *
 * @example
 * ```
 * render () {
 *     return (
 *         <div className='NameField'>{this.l('NAME_FIELD')}</div>
 *     );
 * }
 * ```
 */
function getDocument() {
    return '';
}

Right now, the summary of the hover info is empty. I guess it doesn't recognize it at the moment?

I believe this tag is now displayed in TS 2.7 with VS Code insiders 1.20:


Linker error "mismatches non-TLS reference" when using header-only library

This seems to be a very obscure linker error and google isn't helping and I'm wondering if you've encountered this. When I include libxsmm_source.h to do a header-only build, the compile works and creates a shared library libmylib.so. When linking this library to the executable, I get this message:
/bin/ld: error_message: TLS definition in ./_bin/libmylib.so section .tbss mismatches non-TLS reference in //usr/lib64/libgssapi_krb5.so.2
//usr/lib64/libgssapi_krb5.so.2: error adding symbols: Bad value

When I include libxsmm.h and link to the compiled library I have no such issue and linking happens as expected. Any idea?

Sounds nasty. Can you please share a recipe/reproducer? Alternatively (if you think it's quicker), you can send me a private message and we can arrange some access (either on my end or on your side).

It is nasty, unfortunately it's tied into a very complex build system so a reproducer will be difficult. Just hoping someone had seen this before. Feel free to close.


HTTP Basic Auth

@singingwolfboy if someone does not pass in those args, I'm assuming it'll merrily crawl along without using basic auth?

Correct. I'll improve the README to make that clearer. (@cptvitamin asked for this feature.)


Cakeshop not compatible with RAFT Consensus, Getting the following error "Failed to connect to RPC,  invalid argument 1: json: cannot unmarshal hex string without 0x prefix into Go value of type hexutil.Bytes"

I'm trying to integrate Cakeshop with the Quorum node(Using Raft Consensus), but it is taking Voting Parameters which is part of old Quorum Chain(Voting Consensus Model), it is no longer in use now but the cakeshop repo is not updated since then.
I'm running 4 nodes in different different VM's.
Getting the following error "Failed to connect to RPC,  invalid argument 1: json: cannot unmarshal hex string without 0x prefix into Go value of type hexutil.Bytes"
Is it compatible with IBFT?
Can anyone please help.
Regards,
Ajay

@Ajaysethi136 current release of cakeshop only supports Quorum v1, so no Raft or IBFT yet. Theres been some work done in the pull. Check it out? https://github.com/jpmorganchase/cakeshop/pull/72

@fixanoid  Do you have any suggestion whether we should integrate our Quorum Nodes using RAFT with cakeshop or not if somehow we make it work with RAFT bby making few changes in Cakeshop code??

@fixanoid do I need to incorporate all the changes committed by @yourcodesucks in the current version of cakeshop? or Is it already incorporated into the current version 0.10 of cakeshop, if yes, but i'm facing error while integrating the current version of cakeshop "Failed to connect to RPC, invalid argument 1: json: cannot unmarshal hex string without 0x prefix into Go value of type hexutil.Bytes".
Kindly suggest.

Hi, you either use yourcodesucks fork or quorum-ui branch. Master is too
old at the moment.
On Thu, Jun 28, 2018, 11:08 AM Ajaysethi136<EMAIL_ADDRESS>wrote:

@fixanoid https://github.com/fixanoid do I need to incorporate all the
changes committed by @yourcodesucks https://github.com/yourcodesucks in
the current version of cakeshop? or Is it already incorporated into the
current version 0.10 of cakeshop, if yes, but i'm facing error while
integrating the current version of cakeshop "Failed to connect to RPC,
invalid argument 1: json: cannot unmarshal hex string without 0x prefix
into Go value of type hexutil.Bytes".
Kindly suggest.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jpmorganchase/cakeshop/issues/76#issuecomment-401068015,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAbPjOb4ymADnp4aErxq6Pq-jyT2wL1tks5uBPFTgaJpZM4U3aV4
.

@Ajaysethi136 have you solve the problem? I'm facing the same prob and I would like to know what happened with you.
I'm working on ubuntu 16.04
cakeshop 0.10.0
quorum 7nodes example


Kbw 242

Please don't merge this yet. I need to refactor a bit more code.

I refactored the SendMessageService to implement the strategy pattern to make the code cleaner and more abstract. There's still more work needed to be done on some functions to make it cleaner but this is a start.

Also made a small change on the messages service but that's just separating the SMTP server classes and it's a TODO.


Add support for Accumulo database as part of the install

Accumulo is missing as a feature for the dynamic blueprint.  Since the purpose is to be able to dynamically generate a blueprint based upon the number of servers that were created, having Accumulo would be beneficial.

Hi, thanks for the suggestion!
Arguably, Accumulo isn't the most popular component on the stack :) but here it is: https://github.com/hortonworks/ansible-hortonworks/commit/3790deb372d841b28ae8f3657c343e41648de269
Some blueprint examples in: https://github.com/hortonworks/ansible-hortonworks/tree/master/playbooks/group_vars


Compile warning on 2.3.4 with Elixir 1.8.0-otp-21.2.2

==> quantum
Compiling 37 files (.ex)
warning: function Quantum.DateLibrary.Timex.tz_to_utc!/2 is undefined (module Quantum.DateLibrary.Timex is not available)
  lib/quantum/date_library.ex:40

warning: function Quantum.DateLibrary.Timex.utc_to_tz!/2 is undefined (module Quantum.DateLibrary.Timex is not available)
  lib/quantum/date_library.ex:47

Generated quantum app

If something is dependent on Timex then all code related to it should be compiled only conditionally or else Timex should become a hard dependency.  When depender project is compiling with warnings as errors then it fails to build.

This issue will be solved with Version 3 (already solved on master)


Rename muon containers to make naming more consistent

The muon containers were named pretty inconsistently to the other containers

Sorry, overlooked the column name in the tests.


IDP4 and MVC 5.0, ProtocolValidator.RequireNonce error on Google Chrome

Hey guys. We have an application made with ASP.NET MVC 5 that will be part of a solution to authenticate using a Single Sign On made with Identity Server 4 and the Skoruba implementation with Asp.Net Core 2.2. It is working on Microsoft Edge and Firefox but on the Google Chrome we are getting the error message with

IDX21323: RequireNonce is '[PII is hidden]'. OpenIdConnectProtocolValidationContext.Nonce was null, OpenIdConnectProtocol.ValidatedIdToken.Payload.Nonce was not null. The nonce cannot be validated. If you don't need to check the nonce, set OpenIdConnectProtocolValidator.RequireNonce to 'false'. Note if a 'nonce' is found it will be evaluated.

I as searching on web about the error and I have seen that Chrome is not able to read an external cookie for authentication but I am not sure if I understand correctly. I have tried to add the app.UseExternalSignInCookie(..) method to make sure that the application could be able to read it but no good results so far. The code bellow, is what we have made to implement the SSO on ASP.NET MVC 5 authentication:

private static void UseSingleSignOnAuthentication(this IAppBuilder app)
{
    JwtSecurityTokenHandler.DefaultInboundClaimTypeMap.Clear();

    app.UseCookieAuthentication(new CookieAuthenticationOptions
    {
        AuthenticationType = DefaultAuthenticationTypes.ApplicationCookie
    });

    app.UseExternalSignInCookie(DefaultAuthenticationTypes.ExternalCookie);

    app.UseOpenIdConnectAuthentication(new OpenIdConnectAuthenticationOptions
    {
        ClientId = "..", // the client id generated on Skoruba portal
        ClientSecret = "..", // the client secret generated on Skoruba portal
        Authority = "..", // the base address to the STS Skoruba
        RedirectUri = "..", // Url of this application
        PostLogoutRedirectUri = "..", // Url of this application
        ResponseType = "code id_token",
        Scope = "openid email profile",
        RequireHttpsMetadata = false,
        UseTokenLifetime = false,
        SignInAsAuthenticationType = "Cookies",
        SaveTokens = true,

        Notifications = new OpenIdConnectAuthenticationNotifications
        {
            AuthorizationCodeReceived = async notification =>
            {
                var tokenClient = new TokenClient(SsoSettings.TokenEndpoint,
                    SsoSettings.ClientId,
                    SsoSettings.ClientSecret);

                var tokenResponse = await tokenClient.RequestAuthorizationCodeAsync(notification.Code, notification.RedirectUri);

                var userInfoClient = new UserInfoClient(SsoSettings.UserInfoEndpoint);
                var userInfoResponse = await userInfoClient.GetAsync(tokenResponse.AccessToken);

                var auth = userInfoResponse.Auth(tokenResponse, notification);
                AuthHelper.FillUpUserInfo(auth);

                // authenticate user with Owin and define claims from user and SSO based on userInfoResponse
                var user = AuthHelper.Login(tokenResponse, userInfoResponse);

                if (user == null)
                    thrown newException ( .... );
            },
            RedirectToIdentityProvider = n => { /* logout code */ }
        }
    });
}

I have tried it on serveral machines with Chrome to make sure that is not something on a single machine and I get the same error. Does anyone already pass to it on Google Chrome and know how to fix it?
Thank you.

Hi @felipeoriani - sorry for delay, how did you fix it? Everything work?
Thx

Hi @skoruba, yes, we have added https on the client (asp.net mvc 5) and now it works, but we still have a problem in Chrome, we can't logout, even on the admin panel. If we click at logout button, the application just login again. The same happen for client apps. On the other browsers it works (Edge and Firefox).
Is there any way to fix it on the STS application?

has same issue

Please, could you please switch to dev branch and try install project with the newest RC2?
https://github.com/skoruba/IdentityServer4.Admin/tree/dev

@skoruba fixed by running this command on windows run:
Chrome --disable-web-security --user-data-dir=~/ChromeUserData/

@khaninejad and @skoruba  I have been facing this intermittent problem of IDX21323 with some users and given it is intermittent we are not able to investigate it properly. Is there any User Friendly way to change this configuration the @khaninejad suggested here in Google Chrome or the machine? I want to avoid to ask the users running this command on the prompt as administrator.
@skoruba was it fixed in the lastest versions of your project?
Thank you.

apparently this bug related to Content-Security-Policy.

@khaninejad - do you have more details about this? Thanks.

Hey guys,
Considering it is intermittent problem with some users, I have found a way to simulate it. Try to following these steps:

Go to Chrome
On url enter with chrome://flags
On the search text look for Cookies
Set the flag Cookies without SameSite must be secure to Disabled
Restart chrome

Then if you try to access a client from the project, you will get the error of IDX21323 of the Required Nonce. As we know, the browser new Edge uses the same engine of the Chrome and this problem does not happen over there. Looking for why it is happening with Chrome, I have found the following blog post:
https://www.thinktecture.com/en/identity/samesite/prepare-your-identityserver/
We are trying to get a way to make sure our clients works and maybe it can help us to fix the problem (on @skoruba project and client projects).

Hi @felipeoriani
could you please try latest code from dev branch? I already fixed sime site cookies there and switch solution from http to https.
Thanks.


Add doc for new backend api

Doc changes needed from PR #2378 including --

inheritance diagram
new classes and methods
how to work with backend -> executable
plus anything else anybody else thinks would be useful

P.S.  Yes,  this contains a version change on the root doc to v0.15 so don't merge until that is approved and ready.


Error during nosetests run

Hi!
I have test with theanets simple trainings. Then I do in terminal (in test folder):
nosetests -vd .

Of course, if I use
nosetests .

all works fine.

Is this with theanets 0.5.x? If so, this happens because theanets tries to automatically define a bunch of command-line flags.
This has changed in the upcoming 0.6.x release (current git master) so that there are no command-line flags, so nosetests will work with -vd on the command-line.

Yep, 0.5.x. Ok, I'll check in new release.


fix UnLockAndRelock and length of resourceIDs

Description
needed to improve #76
WOPI Validator
./Microsoft.Office.WopiValidator -n SuccessfulLockSequence -w https://wopiserver.team.owncloud.works/wopi/files/<fileID> -t <token> -l<PHONE_NUMBER>000

Test group: Locks
  Pass: SuccessfulLockSequence

@wkloucek FYI

Hello @micbar, thanks for this, happy to merge the CS3API part and the "heuristic", but for the UnlockAndRelock requests a priori the existing code covers them (though I reckon in a convoluted way, I shall add some comments to explain how) - and the test suite does pass as well.
So can we try without that change first? In particular I guess the more permissive heuristic should allow you to run the test suite with your WOPI proxy.

but for the UnlockAndRelock requests a priori the existing code covers them (though I reckon in a convoluted way, I shall add some comments to explain how) - and the test suite does pass as well.

Can you point me to that? In fact the testsuite was failing before my change.  I used https://learn.microsoft.com/en-us/microsoft-365/cloud-storage-partner-program/rest/files/unlockandrelock as a reference.

So can we try without that change first? In particular I guess the more permissive heuristic should allow you to run the test suite with your WOPI proxy.

Yes. resourceIDs are longer on the edge branch. Other than that we could improve that particular part of the code and do not check the length but the type of the fileID.

Yes, that is what I have used as well, but it's covered (and in a more atomic way) by the check at https://github.com/cs3org/wopiserver/blob/master/src/core/wopi.py#L250
And the screenshot in #76 shows that the lock tests are all green

Yes. resourceIDs are longer on the edge branch. Other than that we could improve that particular part of the code and do not check the length but the type of the fileID.

And yes I suspected that. Agreed that we could also try to check if the fileID looks like a JWT, but probably the heuristic is good enough and we could raise the threshold even more

Yes, that is what I have used as well, but it's covered (and in a more atomic way) by the check at https://github.com/cs3org/wopiserver/blob/master/src/core/wopi.py#L250
And the screenshot in #76 shows that the lock tests are all green

Let me explain:
The UnlockAndRelock operation:
This operation is basically a LOCK operation which sends a new Lock ID and also the old Lock ID.
UnlockAndRelock is similar semantically to the [Lock](https://learn.microsoft.com/en-us/microsoft-365/cloud-storage-partner-program/rest/files/lock) operation.
The two operations share the same X-WOPI-Override value.
So, hosts must differentiate the two operations based on the presence, or lack of, the X-WOPI-OldLock request header.

I think that https://github.com/cs3org/wopiserver/blob/master/src/core/wopi.py#L250 doesn't cover it.
We need to check if the Lockop == LOCK and when an X-WOPI-OldLock is set we should do a unlock operation.

OK, now I understand why we have different results. The xroot storage interface does cover that case, but not the CS3API storage interface. Yet, the CS3API storage interface is correct according to the CS3API specifications, in the sense that refreshLock fails in that case when oldLock is given and is different from the given lock.
So on one side this PR is OK, and on the other side I'll look if we can have a better approximation of atomicity of the unlock+lock operation (not that obvious of course), plus make the xroot layer behave exactly like the CS3 one.


[FLINK-9190][flip6,yarn] Request new container if container completed unexpectedly

What is the purpose of the change
Request new YARN container if container completed unexpectedly.
cc: @sihuazhou @StephanEwen @tillrohrmann
Brief change log

Request new container if container completed unexpectedly.
Reduce visibility of some fields in YarnResourceManager.

Verifying this change
This change added tests and can be verified as follows:

Manually verified the change by deploying a Flink cluster on YARN and killing TaskExecutorRunners randomly.

Does this pull request potentially affect one of the following parts:

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

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

@sihuazhou Thx for the review. I'll take a look at your comments later. Unfortunately with this patch it can still happen that a job is not running even if enough TMs are available. I have uploaded the JM logs here https://gist.github.com/GJL/3b109db48734ff40103f47d04fc54bd3

@GJL Briefly digging through the log, there are a few strange things happening:

YarnResourceManager still has 8 pending requests even when 11 containers are running:
Received new container: container_1524853016208_0001_01_000184 - Remaining pending container requests: 8

Some slots are requested and then the requests are cancelled again

In the end, one request is not fulfilled: aeec2a9f010a187e04e31e6efd6f0f88

Might be an inconsistency in either in the SlotManager or SlotPool.

@GJL In blink, we solve this problem like this.
When a container complete, we will first whether the container has registered yet, if it has registered before, RM will not request a new container, as the job master will ask for it when failover. If it has not registered, RM will request a new one.

Hi @shuai-xu, If I'm not misunderstand, I think your approach is exactly what I have done in the previous PR for this ticket, but it faces the same problem as that faced by this PR. That's even the  container registered with RM successfully, but after RM offering the slot to JM, the container was killed before it registered with JM successfully. I think one way to overcome this is that the RM should notify the JM which TM it will connect with before the RM assign the slot to it, this way JM could be notified that the TM was killed before connecting with it successfully.

@sihuazhou and @shuai-xu thank you for your help in understanding the bug here.
Let me rephrase it to make sure I understand the problem exactly. The steps are the following:

JobMaster / SlotPool requests a slot (AllocationID) from the ResourceManager
ResourceManager starts a container with a TaskManager
TaskManager registers at ResourceManager, which tells the TaskManager to push a slot to the JobManager.
TaskManager container is killed
The ResourceManager does not queue back the slot requests (AllocationIDs) that it sent to the previous TaskManager, so the requests are lost and need to time out before another attempt is tried.

Some thoughts on how to deal with this:

It seems the ResourceManager should put the slots from the TaskManager that was failed back to "pending" so they are given to the next TaskManager that starts.
I assume that is not happening, because there is concern that the failure is also detected on the JobManager/SlotPool and retried there and there are double re-tries
The solution would be to better define the protocol with respect to who is responsible for what retries.

Two ideas on how to fix that:

The ResourceManager notifies the SlotPool that a certain set of AllocationIDs has failed, and the SlotPool directly retries the allocations, resulting in directly starting new containers.
The ResourceManager always retries allocations for AllocationIDs it knows. The SlotPool would not retry, it would keep the same allocations always unless they are released as unneeded. We would probably need something to make sure that the SlotPool can distinguish from different offers of the same AllocationID (in case the ResourceManager assumes a timeout but a request goes actually through) - possibly something like an attempt-counter (higher wins).

@tillrohrmann also interested in your thoughts here.

@StephanEwen, Good idea, I prefer the first one. As for the second one, the pending request may have been fulfilled when task executor is killed. so job master can not cancel the pending request. And when job master failover the job at the same time with resource manager request a new container, it may ask one more container than needed.

I also +1 for the first approach, but I would like to wait for @tillrohrmann 's opinion.
And I also curious about one thing, that is currently when ResourceManager allocate a slot for the pendingSlotRequest, it send JM's information to the TM, and let TM offer the slot to the JM. What I wonder is that why the ResourceManager doesn't send the slot's TM information to the JM, and let the JM fetch slot from TM, is there some special reasons? This problem seems should not exists, if RM send slot's TM information to JM and let JM fetch slot from TM.

I looked into the problem @GJL reported and I think it is not caused by killed TMs which don't have the chance to tell the JMs about the slot allocations (even though this can theoretically happen). In such a case, the protocol currently relies on the slot request timeout on the JM side to resend new requests.
I think the actual problem is related to #5980. The problem there is that the ExecutionGraph does not wait until all of its slots have been properly returned to the SlotPool before it is restarted in case of a recovery. Due to this, it might happen that some of the old tasks occupy some slots which are actually needed for the new tasks. If this happens, the actual task to slot assignment might be suboptimal meaning that the tasks are spread across more slots than needed. For example, assume that we have two slots with a mapper and sink task:
S1: M1_old, S1_old
S2: M2_old, S2_old
Now a failover happens and the system restarts the ExecutionGraph. When this happens M1_old and S2_old have not been properly released.
S1: M1_old
S2: S2_old
Now we try to schedule the new tasks which suddenly needs 3 slots.
S1: M1_old, S1_new
S2: M2_new, S2_old
S3: M1_new, S2_new
After the old tasks have been released it would like that:
S1: S1_new
S2: M2_new
S3:M1_new, S2_new
With @GJL tests we had the situation that we could only allocate one additional container due to resource limitations. Thus, if we actually needed 2 additional container, the program could not start.
By properly waiting for the slot release such a situation should no longer happen.
However, #5980 does not solve the problem of early killed TMs which could not communicate with the JM. At the moment we would have to rely on the slot request timeouts to resolve this situation.

@TisonKun, yes #6132 implements the notification about failed allocations. However, the SlotPool won't directly retry the slot request. Instead the ExecutionGraph will be failed and the allocation will be retried after the job has been restarted.

@tillrohrmann thanks for your reply. Here is one more question.
Does ResourceManager asks for slot by itself? With current codebase ResourceManager would ask for new worker as container complete unexpectedly. What if ExecutionGraph failover concurrent to  ResourceManager asks for new worker? Is there one more extra worker be started?

Yes at the moment, this could happen. However, the superfluous TaskManager should be released after it idled around for too long. Moreover, I'm currently working on making the SlotManager aware of how many outstanding slots he has requested. That way he should not allocate additional containers in case of a failover of the ExecutionGraph.

IIRC it is FLINK-9455 :-)


Possibility to use custom template

Hi, thanks for the role!
Sometimes it's useful to have the possibility of using a custom template to configure ddclient.
The change proposed in this PR allows it through a variable, while maintaining the default behavior of the role.

Thank you @santiagomr for the feature


Getting hidden collections does not work

What I'm trying to achieve
I'm trying to get hidden collections using graphql with app token, however CollectionPublished filter doesn't seem to work at all. It doesn't return any collections, while on the dashboard it does.
Steps to reproduce the problem
Unpublish a collection, then try running a query. Make sure to use app token.
{
    collections(first: 100, filter:{published: HIDDEN }) {
        edges {
            node {
                id
            }
        }
        pageInfo {
            hasNextPage
            endCursor
        }
    }
}

What I expected to happen
I expect hidden collections to be returned.
Screenshots and logs

System information

Saleor version:

[ ] dev (current master)
[ ] 3.0
[x] 2.11
[ ] 2.10

Operating system:

[ ] Windows
[x] Linux
[ ] MacOS
[ ] Other

Hi @DVSoftware this issue has been corrected in version 3.0 and we advise to use this version. If you need more information please let me know.

@eCzerniak Is the version 3.0 production ready?

Works in 3.18


make sure masks are working as expected

As of last night, the Replicate API no longer returns data URLs from prediction input. This makes it a bit challenging to see the mask that was supplied with the request.
One alternative would be to upload the data URL to GCS/S3/something and then use that HTTPS url in the prediction request.

done!


Simple faceting implementation for fast numerical fields

Thanks.
Im a bit swamped at the moment but I should have to hit this PR time later this week.
At first glance it looks good.

Can you extend this to work on i64 fields?

Done

Thanks, looks good to me.
You can fix the CI error by running cargo fmt with rustfmt 0.8.4, but it's no biggie.

I squashed the commits, rebased against master and pusehd to https://github.com/tantivy-search/tantivy/tree/facets.

It was merged. Because of some commit squashing I assume, this branch was not automatically closed.
I had to do a bunch of modification for the following reasons.

.new() was not called
I removed the wrapper that makes it possible to have more than once facet. tantivy already has
chain() to handle multiple collectors with a static dispatch.
set_segment() was not handled.

Thanks for your PR !


Use better alternatives to HaarCascade for Face Detection and Benchmark them

https://learnopencv.com/what-is-face-detection-the-ultimate-guide/
MediaPipe or YuNet or RetinaFace-Mobilenet
https://huggingface.co/qualcomm/MediaPipe-Face-Detection
https://huggingface.co/camenduru/ncnn
https://huggingface.co/google/mobilenet_v2_0.75_160
https://github.com/geaxgx/depthai_yunet
https://github.com/Linzaer/Ultra-Light-Fast-Generic-Face-Detector-1MB

Efficientnet B3 or B7


[Relabel] Remove "Hypermethioninemia due to" from disease entity

Mondo term (ID and Label):
Hypermethioninemia due to adenosine kinase deficiency; MONDO:0013676
Suggested new label:
Adenosine kinase deficiency OR ADK deficiency
Your nano-attribution (ORCID)
Aminoacidopathy Expert Panel (https://www.clinicalgenome.org/affiliation/40011/)
Optional: Any additional information (like supporting evidence, PubMed ID, etc.)
Although there are very few cases of ADK deficiency, there are more recognized phenotypes observed in these probands than the hypermethioninemia. Developmental delay, liver involvement, hypotonia, and dysmorphic features are all associated with this disease entity (PMIDs: 30477030, 33309011). Therefore, the naming should be reflective of the full spectrum of the disorder and the published literature.

I am concerned about defining what a Mondo ID represents.  I failed to speak up when gyrate atrophy was renamed to be Ornithine aminotransferase deficiency.  In this case, a relabeling will broaden the concept represented by the ID.  Seems if we want a general concept, a new record should be created for it.  Created a new node, not redefine an existing one. Just my opinion, of course.

Hi @RedRiver1816 thanks for the request, I will look at this more closely.
@maglott very good point, let me look into this further.

Looking at this - I agree with @maglott, we should obsolete this term and create a new term called 'adenosine kinase deficiency'.
I'll email the Mondo users list to make sure there are no objections.
cc @ana-rath-orphanet

@RedRiver1816 for now, I can create a new class called adenosine kinase deficiency

@RedRiver1816
is this text def okay:
A rare inborn error of metabolism characterized by persistent hypermethioninemia with increased levels of S-adenosylmethionine and S-adenosylhomocysteine which manifests with encephalopathy, severe global developmental delay, mild to severe liver dysfunction, hypotonia and facial dysmorphism (most significant is frontal bossing, macrocephaly, hypertelorism and depressed nasal bridge). Epileptic seizures, hypoglycemia and/or cardiac defects (pulmonary stenosis, atrial and/or ventricular septal defect, coarctation of the aorta) may be associated. Clinical picture may range from neurological symptoms only to multi-organ involvement.
And should the parents be:
'neurometabolic disease'
'autosomal recessive non-syndromic intellectual disability'
'disorder of methionine catabolism'
'inborn disorder of methionine cycle and sulfur amino acid metabolism'

@nicolevasilevsky That all looks great! Let me know if you need any more info to finalize things.

Hi!  We don't have this condition in GARD.  As we do not name diseases I would probably use as main term the name "Adenosine kinase deficiency" as per my review in Pubmed and include as synonyms the names that Orphanet (note that this was recently updated) and OMIM use which reflect the biochemical defect affecting methionine metabolism,

@RedRiver1816 This is all set, thanks! It will be available in the next release.


Whether to support changing to another algorithm

Hi. Thank you for everything. This is great. I would like to ask if I can change the TD3 algorithm to other algorithms based on your work, such as DQN, DDQN and so on. I don't know much about this. I hope you can spare some time to answer my questions. Thanks again!

Hi
Yes you could change the algorithm to other DRL algorithms and train the network with your own methods. You could specify a different algorithm class to be called in line:
https://github.com/reiniscimurs/DRL-robot-navigation/blob/101ed8eaba77b9f447e3d57cc71518cfedb7f65c/TD3/train_velodyne_td3.py#L261
This would call a different DRL training, assuming that the class methods (such as train() and get_action()) are implemented.
It should be relatively painless to adapt a DQN or DDQN algorithm to work here.

I'm sorry to ask you again. Based on your work, I used DQN to implement it. The number of action Spaces of the robot is 5, and the corresponding linear and angular velocities of the 5 actions are shown in the picture below. The neural network outputs the value of the 5 actions, and then the robot chooses one of the actions to execute. However, I encountered some problems during operation, as shown in the picture, after entering the train(), the values of max_value and Q_value are very large, I don't know what caused it, can you give me some help? Looking forward to your reply, thank you!

嗨，是的，您可以将算法更改为其他 DRL 算法并使用您自己的方法训练网络。您可以指定要在行中调用的其他算法类：
https://github.com/reiniscimurs/DRL-robot-navigation/blob/101ed8eaba77b9f447e3d57cc71518cfedb7f65c/TD3/train_velodyne_td3.py#L261
这将调用不同的 DRL 训练，假设实现了类方法（例如 和 ）。
在这里调整 DQN 或 DDQN 算法应该相对轻松。train()``get_action()

I'm sorry to ask you again. Based on your work, I used DQN to implement it. The number of action Spaces of the robot is 5, and the corresponding linear and angular velocities of the 5 actions are shown in the picture below. The neural network outputs the value of the 5 actions, and then the robot chooses one of the actions to execute. However, I encountered some problems during operation, as shown in the picture, after entering the train, the values of max_value and Q_value are very large, I don't know what caused it, can you give me some help? Looking forward to your reply, thank you!

Is the training running alright and at what stage of training do you see these values? How do you come to conclusion that the Q value is too high? If it is a random initialization the Q values would be rather unstable and could be overestimated in the beginning of the training.

Is the training running alright and at what stage of training do you see these values? How do you come to conclusion that the Q value is too high? If it is a random initialization the Q values would be rather unstable and could be overestimated in the beginning of the training.

Thanks for your reply! The training did not go well, and it was the first step into the train() function that led to this result.

Can you share the full code?
It seems a bit weird to me that action is reshaped to shape (-1,1) even though it is a 2 dimensional vector in the regular replay buffer. Then this is used in max_q calculation with gather function. If you are using the DQN from pytorch tutorial, then there it uses a 1D vector for action space so there might be a discrepancy there.

Can you share the full code?
It seems a bit weird to me that action is reshaped to shape (-1,1) even though it is a 2 dimensional vector in the regular replay buffer. Then this is used in max_q calculation with gather function. If you are using the DQN from pytorch tutorial, then there it uses a 1D vector for action space so there might be a discrepancy there.

Thanks for your reply! I mainly changed the actions of the robot in the file "train_velodyne_td3.py", but did not change other files. Please look at the picture.

Are you implementing the DQN from pytorch (https://pytorch.org/tutorials/intermediate/reinforcement_q_learning.html)?
If not, let me know the source of your implementation.
I do not see any major issues here, but the train function might have some issues here. Not sure if you want to reset the target critic model every second training iteration (line 114). Might be better to reset after the training loop has completed. But generally I would expect a soft update of the target network parameters, which I do not see in this code. Here, the target network just takes over all the network weights as they are on every second weight update. This should make the network quite unstable and learning might fail.
But also did you run it only for one training episode? Do the Q values not reduce over the training? Here we are initializing the neural network with random values so the values being wildly off in the beginning would not be unexpected.

Are you implementing the DQN from pytorch (https://pytorch.org/tutorials/intermediate/reinforcement_q_learning.html)? If not, let me know the source of your implementation.
I do not see any major issues here, but the train function might have some issues here. Not sure if you want to reset the target critic model every second training iteration (line 114). Might be better to reset after the training loop has completed. But generally I would expect a soft update of the target network parameters, which I do not see in this code. Here, the target network just takes over all the network weights as they are on every second weight update. This should make the network quite unstable and learning might fail.
But also did you run it only for one training episode? Do the Q values not reduce over the training? Here we are initializing the neural network with random values so the values being wildly off in the beginning would not be unexpected.

Thank you very much for your help! I referred to the link you provided. The soft update you mentioned was used. After running several training sessions, you find the results as shown below. Does this mean that the training is effective?

But I'd like to ask you a few more questions.

"Exception sending a multicast message:Network is unreachable" appears on the terminal. Do I need to be connected to the network for this training?

The implementation of DQN algorithm I refer to is not the official website, it does not use soft update, but the official use. Here soft updates seem to play a big role. Is it necessary in the algorithm?

For some existing algorithms, can I also refer to the official website provided by you for implementation?

May I ask what caused the initial increase in the loss function?

Thank you, you have been a great help to me!

I am not familiar with this error. Please post the error log.
Here is a good answer to this question: https://ai.stackexchange.com/questions/21485/how-and-when-should-we-update-the-q-target-in-deep-q-learning
While not strictly required, the target network update scheme must make sense.
I am not sure what the question is here. Feel free to refer to official websites of implementation if it makes sense.
Loss function is the target Q value difference from Q value. Initially you will see smaller target Q values as reward will be low since most likely would not have encountered that many terminal episodes. Then target Q values will be lower and very close to Q values. As such, your loss will increase and then reduce once actual training begins.

It seems to me that some training is happening as average Q value increases. Not sure if you want to cap the max Q value though, but that is up to your design. However, you should be able to visually see how the policy works in the environment. 30 episodes are a rather small amount for any reasonable training though.

Ok, thank you, what you said is quite right. Before, there was too little training, but with the increase of training, I found a problem. Is it because DQN is not suitable for such a scenario or the code itself has defects and needs to be improved?

DQN and DDQN should not have any major issues in learning with this code as there exist successful implementations. I do not see any reason why it shouldn't work from theoretical standpoint. Most likely there is some discrepancy in the code itself.

Okay, thank you. I recently in learning reinforcement learning in this website "https://spinningup.openai.com/en/latest/spinningup/rl_intro3.html" saw such a content: In Policy Learning, we should care about average returns. The loss function means nothing. I wonder if the same is true in value learning?

DQN and DDQN should not have any major issues in learning with this code as there exist successful implementations. I do not see any reason why it shouldn't work from theoretical standpoint. Most likely there is some discrepancy in the code itself.

Okay, thank you. I recently in learning reinforcement learning in this website "https://spinningup.openai.com/en/latest/spinningup/rl_intro3.html" saw such a content: In Policy Learning, we should care about average returns. The loss function means nothing. I wonder if the same is true in value learning?

What they mean here is that in typical imitation learning tasks you would have ground truth and your calculated observation. Loss is expressed as the difference between ground truth and the observation. Therefore, the lower the loss, the closer your model is to ground truth so that is your target for optimization.
Here, though, there is no ground truth, there is only a reward function that you are trying to optimize for. The loss is just a direction for your optimization in which to optimize your parameters, as you are comparing the target Q to the network Q value, both of which are to be learned.
It does not matter if it is DQN or Policy gradient. What you learn in the end is to estimate the value of your state-action pair. The question for the network here is "if I take this action, what will be my current + future reward?". The more correct your Q value estimation is, the better the policy. Both methods solve this problem.
You could look into the implementation of a similar method with D3QN in: https://arxiv.org/pdf/1706.09829.pdf
You could take inspiration from their open source code.


Preact unmounts DOM Node (wrong diff?)

Hello,
I trimmed down my problem to the simplest example and I actually think the issue comes down to some difference in implementation with React.
So I have a pretty simple use case / page:

A list of Hotels on the left
A Google map on the right
When I click a Hotel in the list, a detailed view appears on top of the map (<HotelPane />)

const HotelListPage = ({ hotels, selectedHotel }) => {
  return (

         <HotelList hotels ={hotels} />

      {selectedHotel !== null &&
        <HotelPane hotel={selectedHotel} />
      }

        <Map hotels ={hotels} />

  )
}

Steps:

First time, <HotelPane /> is not rendered, <Map /> and <HotelList /> are.
Hotel in the list is clicked
<HotelListPage /> re-renders
<HotelPane /> renders...
<Map /> is unmounted ! <HotelList /> not.

So I don't understand why 5- occurs. From my understanding there is no reason why this DOM node should be removed. There is no difference (regarding that exact component) between steps 1- and 5-.
This exact same use case works as expected with React (<Map /> is not being unmounted).
The versions I am using are:
    "preact": "^7.2.0",
    "preact-compat": "^3.13.1",

<Map /> component quickly:
class Map extends Component {
  ...
  render () {
    return (

 { this.mapElement = el }}>

    )
  }
}

Note: A Google Map is attached to this.mapElement on componentDidMount.
Thanks for your help.

Closing.
It seems to come from my code. I use some kind of withGoogleApi() HOC and if I remove it, the problem doesn't occur.
Thanks. If you have any hints though.

@eightyfive Good to know you solved it - wondering which version of Preact this was with?

Sure:
    "preact": "^7.2.0",
    "preact-compat": "^3.13.1",

Note: Was really just my code / understanding. Hehe.

Ahh ok, good to know!  If you ever run into things like this there are over 200 lovely people in the Preact Slack that can help out super quick, if that is of interest to you 🙂


Feature Request: Proxy support

The script fails when a proxy is configured in macOS System Preferences, and is required for Internet access.

I see no reason why that should happen, and I can’t reproduce. The setup script makes two curl calls: one to know what to get, and the other to get it.
You can copy the script to your machine and edit those two lines to use your proxy configuration. That script is stable and unlikely to change, so there’s little risk of it becoming outdated. I might add an option for codesigning, but it’s unlikely I’ll add anything else.


chore(main): release 1.26.2

:robot: I have created a release beep boop
1.26.2 (2024-12-12)
Bug Fixes

height for pwa (e848e94)
padding (8443931)
reduce dom (9799232)
reduce dom for proxy group (86cf36c)
sidebar collapse btn & input clear btn (b19128d)
virtual scroller for rule (0a35b87)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v1.26.2
:sunflower:


rename plugin for consistency

While you're refactoring for QGIS3;
afaik QGIS3 will use a separate plugin repository. You might use the opportunity to rename the plugin from "OSM Tools" to "ORS Tools"? I had trouble finding the plugin the first time..

Yes, they have to use separate repos for dependency conflicts.
It originally was ORS Tools. Then I changed it to OSM Tools for the idea to offer many more API's, Graphhopper, Here, route360 etc. But for many reasons, I might not do that after all. So yeah, ORS Tools it'll probably be.

QGIS3 will use the same plugin repo apparently. So I changed the the repo URL.


Swagger change for SAP Cloud For Customer

This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information

[x] The title of the PR is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[x] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[x] If applicable, the PR references the bug/issue that it fixes.
[x] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[x] I have read the contribution guidelines.
[x] My spec meets the review criteria:

[x] The spec conforms to the Swagger 2.0 specification.
[x] The spec follows the guidelines described in the Swagger checklist document.
[x] Validation tools were run on swagger spec(s) and have all been fixed in this PR.

@wenbof don't forget you need a .NET SDK PR to go along with this

@sergey-shandar these are models that correspond to creating/getting linked services, datasets and pipelines, i.e. existing APIs

@bgold09 well noted for the SDK. It was on my radar and was planning to send the PR for it after the approval. Thanks for your reminder.

I have also sent SDK change PR. Thanks. https://github.com/Azure/azure-sdk-for-net/pull/3832


The extraction method of function variable is improved

Changes Unknown when pulling<PHONE_NUMBER>a8a95f7573cce97a47d27e0f4a0ad3 on BlBana:master into ** on wufeifei:master**.


Recipe: API Pagination

As an application developer, I would like to understand all the ways to paginate API results, so that I can work with larger sets of data.
There are several different ways that steemd and hivemind will provide pagination, depending on the namespace and/or method.  Some methods are a bit more flexible than others.
This recipe needs to group all of the methods into one place and point to the API Definitions for more detail.
AC

[x] overview about why pagination is required
[x] show the various strategies that methods use to support pagination

[x] also link to API Definitions for these methods
- [ ] provide alternatives to querying the API make a separate recipe

Going through this, I am realizing that a small number of order types have been added after the API Definitions were created.  So a new issue should be created to update API Definitions and also link back to this new document.

As an example of new order types being added:
https://github.com/steemit/steem/blob/b2c9ae89f08de79ea8577d39e4a7b99781c472b0/libraries/plugins/apis/database_api/database_api.cpp#L1262
It looks like database_api.list_votes will support ordering by SMT.

https://github.com/steemit/devportal/pull/425


[FR] Add resized image names to original image meta info

[REQUIRED] Step 2: Extension name
This feature request is for extension: _ (storage-resize-images)
Add resized image names as meta info to the original image
To help discovering if resized images were created for an image add resized image path/name(s) as a meta information to the original image
Will help finding thumbnails without extra queries even with changing configurations.

Thanks for the feature request!

I think this is a MUST needed feature

XFN Team: Related PRs https://github.com/firebase/extensions/pull/6 https://github.com/firebase/extensions/pull/42

Likewise, I think this is a must-have feature. I can compose the string to get the path of the resized image, but it's pretty long-winded as this extension appends (rather than prepends) the image size prior to the file extension, meaning that I've got to do some pretty complicated regex logic to get the resized image path.

Thanks so much for the feature request! This makes a lot of sense to track the original image. However, given you can have multiple Resize Image extensions for multiple phone sizes and this should be a two-way sync (the link should update if images get deleted), the implementation is a bit complicated.
A more flexible solution seems like it would be a new extension that manages a Firestore collection to track all your images. This way, you'd be able to sort and update the records as files in Cloud Storage changes.
I'm going to close this for now and track separately as a extension to mirror your Cloud Storaage bucket.


Issue #SB-919 feat:Test cases for announcement router

@loganathan1989 please review, also check the build status in Travis.


Remove unused Emitter2.jl file

This is old code that is not used anywhere. Deleting it.

 There's also an include statement in Optical.jl that needs to be removed. Probably not worth making another PR just for this.


Bump types-toml from 0.10.3 to 0.10.4 (#3813)

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

Merged in c94e9341a64c5eecef4afb80149c731686f6a340


fix(amplify-codegen): fix name for many to many join table fields

Description of changes

fix naming for many-to-many join table fields

Description of how you validated changes

manual testing for iOS datastore app
yarn test passes

Checklist

[x] PR description included
[x] yarn test passes
[x] Tests are changed or added
[ ] Relevant documentation is changed or added (and PR referenced)
[ ] Breaking changes to existing customers are released behind a feature flag or major version update
[ ] Changes are tested using sample applications for all relevant platforms (iOS/android/flutter/Javascript) that use the feature added/modified

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #303 (8e5608c) into master (3ab7469) will increase coverage by 0.06%.
The diff coverage is 98.36%.

@@            Coverage Diff             @@
##           master     #303      +/-   ##
==========================================
+ Coverage   85.16%   85.23%   +0.06%
==========================================
  Files         144      146       +2
  Lines        6814     6798      -16
  Branches     1749     1715      -34
==========================================
- Hits         5803     5794       -9
+ Misses        937      913      -24
- Partials       74       91      +17

Impacted Files
Coverage Δ

...odelgen-plugin/src/utils/process-connections-v2.ts
89.83% <88.88%> (+0.17%)
:arrow_up:

...es/appsync-modelgen-plugin/src/utils/fieldUtils.ts
100.00% <100.00%> (ø)

...c-modelgen-plugin/src/utils/process-connections.ts
92.30% <100.00%> (-0.17%)
:arrow_down:

...appsync-modelgen-plugin/src/utils/process-index.ts
100.00% <100.00%> (ø)

...c-modelgen-plugin/src/utils/process-primary-key.ts
100.00% <100.00%> (ø)

...delgen-plugin/src/visitors/appsync-java-visitor.ts
93.09% <100.00%> (-0.01%)
:arrow_down:

...elgen-plugin/src/visitors/appsync-swift-visitor.ts
96.37% <100.00%> (+0.81%)
:arrow_up:

...nc-modelgen-plugin/src/visitors/appsync-visitor.ts
94.78% <100.00%> (+0.80%)
:arrow_up:

packages/appsync-modelgen-plugin/src/plugin.ts
0.00% <0.00%> (ø)

packages/appsync-modelgen-plugin/src/preset.ts
0.00% <0.00%> (ø)

... and 10 more

Continue to review full report at Codecov.

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


Nouns

Letters for women are more likely to use adjectives instead of nouns

Goal: Develop code that can read text for the presence of nouns that highlight roles/positions (like leader, researcher).  If position nouns are absent, return a summary statement that directs the author to consider using nouns to strengthen the letter.
This one can be complicated.  The goal is to differentiate between descriptions that use adjectives, verbs, or weaken the position noun (i.e., she was involved in research, she taught).

This project sounds amazing, congrats on pitching such a cool project. I'm going to start putting together a script to track frequency of nouns and adjectives for different letters, and potentially play with sentiment analysis to figure out if letters for males show a stronger positive sentiment indicating a higher use of superlatives. I do most of my coding in python, is that going to be a problem?

I am also interested in working on this problem. One way to approach this is to make a list of relevant nouns and their corresponding verbs and check the relative frequencies of these (e.g., if "leads" or "led" is used more than "leader"). That seems like a fairly simple first step and I could work on that. It's probably also a good idea to use POS tagging to detect passive voice, as that would catch things like "was involved".
What programming language are we using? I'm most comfortable with Python, though I've done some coding in Perl (I know other languages, but I don't think any of them would be good for this sort of problem). What sort of POS tagging would we use? I've used TreeTagger for Python and Lingua::EN::Tagger for Perl, but I know Python's nltk has several POS taggers built in. I've also used Spacy a little bit, but I'm less familiar with that.

Python is prefect!  That is the language I know best!  I'm still learning programming, so it isn't saying much!   I working on setting up a website.  Hoping to have that ready to go by Thursday.
Feel free to use the POS tagging you are most comfortable with!  Please remember to add your names to the contributors page as well.  I want to be certain to recognize all the contributions.

Thank you both for the kind words, support, and help!

@molliem — love love love this project, and looking forward to helping!
I did a quick search of the repo and it doesn't look like anyone's mentioned proselint here. This is a general prose-checking framework (tips like weasel_words.very: don't use the word 'very', or typography.symbols.curly_quotes Use curly quotes “”, not straight quotes "".), and the needs of this project reminded me of proselint's plugin-based architecture.
In short, each 'plugin' has its own rules, ways of checking, and error messages — and each is completely independent of the others. So a adjectives_vs_nouns plugin can use a totally different technology to check for bias than stereotypes plugin.
Thought I'd drop the link here in case it's a useful reference, but in the meantime, looking forward to getting started wherever is most helpful!

@j6k4m8 Thank you for the kind words!  And thanks for the link to proselint!!  I hadn't heard of it and it is a fabulous reference!
Although we haven't been tackling this project as plugins, our approach feels similar.  I divided the issues up into topics and people have been working on scripts for each topic.  My plan at the end is to use a wrapper or a for loop to combine the separate topics into one.
Do you know python?  There are four issues that no one has tackled: superlatives, family life, minimal assurance, and raises doubt.  Help on any of those would be great.  If you know web design, I could use some help there too.  It is pretty plain.
Thanks for reaching out! Excited to have you join the team!

Python or web-design or both! Up to you, wherever you'd prefer to have more help!


docs: "Crypto Cipher" API isn't available in the docs

So, we have https://github.com/zephyrproject-rtos/zephyr/blob/master/include/crypto/cipher.h#L9 which clearly has docstrings defining a whole API subsystem. However, search for "Crypto Cipher APIs" (section title from that file) doesn't give useful hits: https://docs.zephyrproject.org/latest/search.html?q=Crypto+Cipher+APIs&check_keywords=yes&area=default
It looks like that API is not included in the docs. That might be as well because of warning sign in that file:

[Experimental] Users should note that the APIs can change

as a part of ongoing development.

But that notice is from 2016. By 2020, it may be still experimental, but not as experimental as to exclude it from the docs.
@dbkinder, Can you please do initial triaging on this, maybe you're aware of the situation, maybe there's just some markup error. Then as needed, let's involve Anas et al.

Note that we have https://docs.zephyrproject.org/latest/guides/crypto/index.html . But that goes just orthogonal: So, Zephyt has own crypto API, in particular, it provides wrappers for 3rd-party libraries, like mbedTLS. Wrappers, because we want to use people to use native Zephyr API, which may be implemented by different underlying crupto providers. And yet we have that "Cryptography" section where only thing that it does is exposes 3rd-party lib directly.
Also cc: @d3zd3z to be aware of this situation.

Actually, looking closer at cipher.h, the majority of comments there are simple comments /* */, and not docstring comments /** */. @dbkinder, is that what precludes a useful doc section to be generated out of it?

David let me know that he no longer oversees Zephyr docs. So, ping to you, @nashif, whether you know of a reason why Crypto API docs shouldn't be in the manual. If not, I'll try to look into getting them rendered there.

taking a stab on this now


Feature/animation looping

Add looping flag to loop animations

👌

👏🏻
On Mon, Jul 4, 2016 at 8:23 AM Koen Bok<EMAIL_ADDRESS>wrote:

Merged #371 https://github.com/koenbok/Framer/pull/371.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/koenbok/Framer/pull/371#event-712157881, or mute the
thread
https://github.com/notifications/unsubscribe/AACbYhqyE8pd6pP0w4iEG_vC3-K7oidGks5qSSWCgaJpZM4I8sP1
.


fix: simplify count statements

Description

Simplify Count statement in 2 cases of policy attachments as it causes failures during apply in some cases
Motivation and Context

Simplify Count statement in 2 cases of policy attachments as it causes failures during apply in some cases
Breaking Changes

No.
How Has This Been Tested?

Yes.

@bryantbiggs if you have some time to take a look.

Nice and sweet 👍
v2.20.0 has been just released.


improve type conversions in SGv2 REST service

Looks like the branch contains all the commits from your previous PR. You should be able to rebase to only keep the last commit:
git rebase --onto v2.0.0 v2/jeff/sgv2-time^ v2/jeff/sgv2-time


Consider adding key binding support for `` wrapping

Commonly used in markdown editing, would be highly beneficial!

added in version 0.8.0


fix: nan inf float

Change Summary
Based upon the first commit from #888 (many thanks @JeanArhancet), adding a config value ser_json_inf_nan to choose whether to serialize as null or constants.
Unlike the last comment in #888 we decided not to have the serializer interact with allow_inf_nan at all. We preferred to not error on the serialization path, and just assume that if allow_inf_nan=False then the validator has already prevented an out of range value.
Probably in V3 we want to flip the default of ser_json_inf_nan to constants, as that matches closer the behaviour of json.dumps.
Related issue number
Closes #872
Closes #888
Checklist

[ ] Unit tests for the changes exist
[ ] Documentation reflects the changes where applicable
[ ] Pydantic tests pass with this pydantic-core (except for expected changes)
[ ] My PR is ready to review, please add a comment including the phrase "please review" to assign reviewers

(implementation can always be changed later)


Introduce latest changes to fix pipelines

Description
Changes proposed in this pull request:

fix verification
unify k3d targets

/test all

LGTM


CompiledIncludeNode miss base path

readFile method invoke TemplateRuntime.execute(cFileCache, ctx, factory) does not pass the basePath in CompiledIncludeNode class.

It can not find the @include file when it is in other @include file

Hi, I have a hack for this, see #301