truncated tweet without a retweeted_status key

Hi everyone, I am trying out twython,
edit: and by the way it's very nice ;) thanks
I query something with
betterquery = "something -filter:retweets -filter:replies"
search_results = twitter.search(q=betterquery, count=30)

and in search_results['statuses'] I get tweets where the attribute "truncated" is set to True, but there is no 'retweeted_status' object (the key is missing too) within the tweet.
I am trying to obtain the full text of such tweets, and I read that it should be available at tweet['retweeted_status']['text'] when truncated is True.
Please note that my research query contains "-filter:retweets", so I should in the first place avoid retweets that are too long and thus truncated... This is something I don't really understand ?! I thought vanilla tweets are limited in size, so why would it be truncated ?
But I am not very familiar with twitter and I might be missing something obvious...
Thanks for helping,
Cheers,
M.

OK, my bad, I was doing something wrong, but somehow I did not find it in the documentation. I found it in one of the open (issue)[https://github.com/ryanmcgrath/twython/issues/471#issuecomment-345766655] here which was redirecting to https://stackoverflow.com/questions/47391092/twython-with-140-character-limitation-of-twitter
new code is:
search_results = twitter.search(q=betterquery, count=30, tweet_mode='extended')

and then fetching for
search_results['statuses'][0]['full_text']

instead of search_results['statuses'][0]['text']
I think this should appear somewhere here:
https://twython.readthedocs.io/en/latest/usage/starting_out.html#what-twython-returns
Sorry for disturbing :D


Confusion on nonepidermolytic palmoplantar keratoderma terms

Rather than reopening #3108 , I wanted to open a new ticket to request review of just a couple of these terms because we are running into issues trying to map MONDO:0006588 "nonepidermolytic palmoplantar keratoderma" and MONDO:0010962 "diffuse nonepidermolytic palmoplantar keratoderma" in MedGen.
The preferred name on MONDO:0006588  matches the OMIM preferred name for 600962 (but this maps to MONDO:0010962).
So I am reviewing the X-refs on these Mondo IDs in hopes that a better nomenclature/distinction can be made between the grouping concept and the gene-specific forms.... as best I can tell, historically these have been mixed up/used interchangeably until the molecular cause was determined to be two different loci. So I appreciate the need for a parent concept and the two gene-specific children, but I don't think the X-refs as they are currently mapped are correct, nor do the names align with the X-refs. My attached notes hopefully document how mixed up the different cross-references are here, but we certainly need medical review of these two/three concepts to determine what the correct names/concepts are that should be represented. If I can find a good review of these disorders I'll post the article as a comment.
nonepidermolytic palmoplantar keratoderma_XRefNotes.txt
Notes are pasted below:
nonepidermolytic palmoplantar keratoderma MONDO:0006588
Orphanet:2337 (MONDO:equivalentTo) "Non-epidermolytic palmoplantar keratoderma"
SYNS: Synonym(s):
Autosomal dominant diffuse palmoplantar keratoderma, Norrbotten type
Diffuse palmoplantar keratoderma, Bothnian type
NEPPK
X-refs: OMIM: 600231 "PALMOPLANTAR KERATODERMA, BOTHNIAN TYPE; PPKB"
UMLS: C1833030 "PALMOPLANTAR KERATODERMA, NONEPIDERMOLYTIC" (and UMLS says this CUI matches HP:0007404, OMIM: 600962, and MESH C563422)
C1838359 "Diffuse palmoplantar keratoderma, Bothnian type" (UMLS x-refs MESH C536173 and OMIM 600231)
GARD: 1862  "Diffuse palmoplantar keratoderma, Bothnian type"
DOID:0050428 (MONDO:equivalentTo) : "nonepidermolytic palmoplantar keratoderma" with exact syns "Thost-Unna Syndrome; Unna-Thost Syndrome; tylosis; diffuse nonepidermolytic palmomplantar keratoderma"
ICD10:Q82.8 (Orphanet:2337) (Not evaluated)
SCTID:716105001 (MONDO:equivalentTo) "Autosomal dominant diffuse palmoplantar keratoderma Norrbotten type" syn of Non-epidermolytic palmoplantar keratoderma; Definition: "This syndrome has manifestation of a diffuse non-epidermolytic palmoplantar keratoderma with frequent fungal infections. Prevalence in the general population is estimated at 1 in 40,000 but is much higher in northern Sweden. Transmission is autosomal dominant and the causative gene has been localized to chromosome 12q11-q13. (SNOMEDCT_US)"
EFO:1000743 (MONDO:equivalentTo) (Not evaluated, not sure what this resource is and there is no link from Mondo)
diffuse nonepidermolytic palmoplantar keratoderma MONDO:0010962
OMIM:600962 (Orphanet:530838) "PALMOPLANTAR KERATODERMA, NONEPIDERMOLYTIC; NEPPK" aka PPKNE
NONEPIDERMOLYTIC PALMOPLANTAR KERATODERMA
KERATODERMA, NONEPIDERMOLYTIC PALMOPLANTAR
TYLOSIS (though perhaps this is an instance of OMIM using a more general concept as an alternate name)
Orphanet:496 (OMIM:600962) "Thost-Unna palmoplantar keratoderma" X-refs GARD 5186 (but OrphaNet has note: "This entity has been excluded from the Orphanet nomenclature of rare diseases and moved to Epidermolytic palmoplantar keratoderma." So maybe this should be obsoleted in Monodo X-ref?)
GARD:0005186 (OMIM-shared) "Unna-Thost palmoplantar keratoderma" and GARD defines it as "Unna-Thost palmoplantar keratoderma is inherited in an autosomal dominant pattern and caused by genetic changes in the KRT1 gene." and X-refs Palmoplantar keratoderma, nonepidermolytic, NEPPK. Online Mendelian Inheritance of Man (OMIM). September 2009; http://omim.org/entry/600962. Accessed 10/12/2011.
Orphanet:530838 (MONDO:equivalentTo) "KRT1-related diffuse nonepidermolytic keratoderma" points to OMIM 600962, and thank you that this is not Mondo's preferred name.
Related Mondo term:
palmoplantar keratoderma, Bothnian type  MONDO:0010849
Points to OMIM: 600231;  PALMOPLANTAR KERATODERMA, BOTHNIAN TYPE; PPKB
and GARD:0001862 (OMIM-shared)
Clean up idea:
There is the Orphanet term  "Autosomal dominant isolated diffuse palmoplantar keratoderma ORPHA:98349" which could be the parent concept to OMIM:600962 and OMIM: 600231 since they are both AD inhertiance. Then 'dissolve' MONDO:0006588 and move the X-refs to the appropriate gene-specific terms, maybe adjust some of the names from X-refs to "related synonyms" to clarify which type is which?

I reviewed the descriptions in OMIM, and the orphanet/OMIM mappings. I think these are the correct ids:
| OMIM | Orphanet | Gene | From omim description
-- | -- | -- | -- | --
MONDO:0010962 diffuse nonepidermolytic palmoplantar keratoderma | 600962 | ORPHA:530838 | KRT1 | diffuse nonepidermolytic palmoplantar keratoderma (NEPPK)
MONDO:0010849 palmoplantar keratoderma, Bothnian type | 600231 | ORPHA:2337 | AQP5 | diffuse Bothnian type of NEPPK (PPKB)
*MONDO:0013073 palmoplantar keratoderma, nonepidermolytic, focal 1 | 613000 | [ORPHA:448264 =isolated focal, map to 2 omim: 613000  616400) | KRT16 | focal form of NEPPK
*MONDO:0014272palmoplantar keratoderma, Nagashima type | 615598 | ORPHA:140966 | SERPINB7 | diffuse Nagashima type of NEPPK (PPKN)
*MONDO:0014327 palmoplantar keratoderma, nonepidermolytic, focal or diffuse | 615735 | ORPHA:402003 | KRT6C | form of NEPPK
All these terms should have a common parent (terms with * in table above do not share a parent):
nonepidermolytic palmoplantar keratoderma (MONDO:0006588)
Note that we need to review and find the correct x-refs for this term such that it represents the parent term.
@nicolevasilevsky, could you review this when you have a moment. If it sounds good, I will make the changes in the ontology. Thank you.

This looks okay to me. @kanems is it okay with you?

@sabrinatoro and @nicolevasilevsky yes, I agree with Sabrina's excellent and very clear table with one parent term that is agnostic of inheritance pattern. Thanks!

Thanks @kanems! @sabrinatoro please go ahead!

I want to make sure our classification is correct.
Currently in Mondo:
'nonepidermolytic palmoplantar keratoderma' (MONDO:0006588) (NEPPK)
is a child of
'isolated diffuse palmoplantar keratoderma' (MONDO:0017667)
@ahamosh
Is this correct? is NEPPK always 'diffuse'?
If yes, then in addition to split/merge, we need to rename labels according to disease-by-gene pattern.
If no, then we need to review classification.

I think so.  honestly, just read all the information and am still somewhat confused...
Ada

I reviewed the terms once again, looking specifically at their inheritance mode and whether they are diffuse or focal. I am taking back what I said above :-)
The current terms and their parents are ok, except for the following terms:

'palmoplantar keratoderma, Bothnian type' (MONDO:0010849)
This term should be a child of 'autosomal dominant isolated diffuse palmoplantar keratoderma' (MONDO:0020093).
Also, this term should have MondoEquivalentTo: Orphanet:2337  (and this xref should be removed from MONDO:0006588)

'nonepidermolytic palmoplantar keratoderma' (MONDO:0006588) should be merged into 'diffuse nonepidermolytic palmoplantar keratoderma' (MONDO:0010962)
The parent term, 'autosomal dominant isolated diffuse palmoplantar keratoderma' (MONDO:0020093), is correct


Cannot find repo scality/cdmiclient

Issue template
If you are reporting a new issue, make sure that we do not have any
duplicates already open. You can ensure this by searching the issue list for
this repository. If there is a duplicate, please close your issue and add a
comment to the existing issue instead.
General support information
GitHub Issues are reserved for actionable bug reports and feature requests.
General questions should9.7.1 be sent to the
S3 scality server Forum.
Bug report information
Description
While performing "npm install" he can't find the scality/cdmiclient repository
Steps to reproduce the issue
Clone project from Github and run "npm install"
Actual result
I'm getting the following error message:
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: cdmiclient@github:scality/cdmiclient (node_modules/cdmiclient):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Error while executing:
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: /usr/bin/git ls-remote -h -t<EMAIL_ADDRESS>npm WARN optional SKIPPING OPTIONAL DEPENDENCY:
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: ERROR: Repository not found.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fatal: Could not read from remote repository.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY:
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Please make sure you have the correct access rights
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: and the repository exists.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY:
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: exited with error code: 128
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.

Expected result
Performing a clean installation of all dependencies.
Additional information: (Node.js version, Docker version, etc)
NPM Version: 5.7.1
Node Version: 9.7.1

Hi @YannickFricke ,
cdmiclient is a Scality private module which is why it is configured as an optional dependency. It should not impact the server startup/usage as the default backend is installed correctly.

Hi @rahulreddy,
as you see it impacts the installation of S3 :)

Hi @YannickFricke ,
The errors you're seeing are npm warnings, not npm failures. Have you starting the service (npm start) to check whether you could use it? I am confident the install went well, as Rahul said.
If you can't start it, can you send us the logs please, so we can look into them?
Cheers!

Hi @LaureVergeron ,
you see it as warning, but actually it is an error.
Here is the log from npm while performing npm start
0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'start' ]
2 info using<EMAIL_ADDRESS>3 info using<EMAIL_ADDRESS>4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>6 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>7 verbose lifecycle<EMAIL_ADDRESS>unsafe-perm in lifecycle true
8 verbose lifecycle<EMAIL_ADDRESS>PATH: /usr/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/srv/S3/node_modules/.bin:/home/yfr/bin:/home/yfr/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/home/yfr/.composer/vendor/bin
9 verbose lifecycle<EMAIL_ADDRESS>CWD: /srv/S3
10 silly lifecycle<EMAIL_ADDRESS>Args: [ '-c', 'npm-run-all --parallel start_dmd start_s3server' ]
11 silly lifecycle<EMAIL_ADDRESS>Returned: code: 1  signal: null
12 info lifecycle<EMAIL_ADDRESS>Failed to exec start script
13 verbose stack Error<EMAIL_ADDRESS>start: `npm-run-all --parallel start_dmd start_s3server`
13 verbose stack Exit status 1
13 verbose stack     at EventEmitter.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:285:16)
13 verbose stack     at EventEmitter.emit (events.js:180:13)
13 verbose stack     at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack     at ChildProcess.emit (events.js:180:13)
13 verbose stack     at maybeClose (internal/child_process.js:936:16)
13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:220:5)
14 verbose pkgid<EMAIL_ADDRESS>15 verbose cwd /srv/S3
16 verbose Linux 4.13.0-37-generic
17 verbose argv "/usr/bin/node" "/usr/bin/npm" "start"
18 verbose node v9.8.0
19 verbose npm  v5.6.0
20 error code ELIFECYCLE
21 error errno 1
22 error<EMAIL_ADDRESS>start: `npm-run-all --parallel start_dmd start_s3server`
22 error Exit status 1
23 error Failed at the<EMAIL_ADDRESS>start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]

Here is the error from the console:
yfr@yfr-linux /s/S3> npm start

><EMAIL_ADDRESS>start /srv/S3
> npm-run-all --parallel start_dmd start_s3server

><EMAIL_ADDRESS>start_s3server /srv/S3
> node index.js

><EMAIL_ADDRESS>start_dmd /srv/S3
> npm-run-all --parallel start_mdserver start_dataserver

><EMAIL_ADDRESS>start_mdserver /srv/S3
> node mdserver.js

><EMAIL_ADDRESS>start_dataserver /srv/S3
> node dataserver.js

/srv/S3/mdserver.js:8
    const mdServer = new MetadataFileServer(
                     ^

TypeError: MetadataFileServer is not a constructor
    at Object.<anonymous> (/srv/S3/mdserver.js:8:22)
    at Module._compile (module.js:649:30)
    at Object.Module._extensions..js (module.js:660:10)
    at Module.load (module.js:561:32)
    at tryModuleLoad (module.js:501:12)
    at Function.Module._load (module.js:493:3)
    at Function.Module.runMain (module.js:690:10)
    at startup (bootstrap_node.js:194:16)
    at bootstrap_node.js:666:3
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>start_mdserver: `node mdserver.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start_mdserver script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
{"name":"DataFileStore","time":1521178892623,"level":"info","message":"pre-creating 3511 subdirs...","hostname":"yfr-linux","pid":7542}

npm ERR!  Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start_dmd script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!  Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/yfr/.npm/_logs/2018-03-16T05_41_32_844Z-debug.log

Cheers!

@YannickFricke ,
Thanks for the log output. The error is not actually because of that module not installing but incorrect version of code/dependencies. It's possible that your code is out of date, can you please rebase from master again and re-install npm modules?
One more thing, I noticed that you are using nodejs version 9.7.1. We currently support > 6.9.5, please make sure you install the above version before installing the npm modules and starting the server.

@rahulreddy
Sorry for my very late reply!
Rebased code now I am on commit "208c024" and removed "node_modules" directory.
Still the same error: Git cannot read from the remote repository<EMAIL_ADDRESS>When I run git like it is showing in the output I get the following message:
ERROR: Repository not found.
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

I tried to install the dependencies with yarn and with npm and get the error with both.
But as far as I know: It shouldn't depend on yarn / npm / node. It's a problem with git.

@rahulreddy @LaureVergeron  I m seeing the errors wfor cdmiclient .
MM99468M2:S3 mm99468$ sudo npm install
Password:
npm ERR! Error while executing:
npm ERR! /usr/bin/git ls-remote -h -t<EMAIL_ADDRESS>npm ERR!
npm ERR! ERROR: Repository not found.
npm ERR! fatal: Could not read from remote repository.
npm ERR!
npm ERR! Please make sure you have the correct access rights
npm ERR! and the repository exists.
npm ERR!
npm ERR! exited with error code: 128

Hi got same problem:
`
npm install
npm ERR! Error while executing:
npm ERR! /usr/bin/git ls-remote -h -t<EMAIL_ADDRESS>npm ERR!
npm ERR! Warning: Permanently added the RSA host key for IP address '<IP_ADDRESS>' to the list of known hosts.
npm ERR! Permission denied (publickey).
npm ERR! fatal: Could not read from remote repository.
npm ERR!
npm ERR! Please make sure you have the correct access rights
npm ERR! and the repository exists.
npm ERR!
npm ERR! exited with error code: 128
npm ERR!

@YannickFricke  I was unable to reproduce this, I am gonna be trying again with a non-scality Github user and get back to you.

I just tried npm install again from an anonymous github clone. The install doesn't seem to fail, although the error is thrown. But the current version fails to start (see log below)
npm WARN deprecated<EMAIL_ADDRESS>Use uuid module instead
loadDep:cdmiclient → addT ▄ ╢██████████████████████░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░╟
The authenticity of host 'github.com (<IP_ADDRESS>)' can't be established.
loadDep:cdmiclient → reso ▄ ╢██████████████████████░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░╟
npm ERR! git clone --template=/home/ubuntu/.npm/_git-remotes/_templates --mirror git@github.com:scality/cdmiclient.git /home/ubuntu/.npm/_git-remotes/git-github-com-scality-cdmiclient-git-8f0c2e6-7531c719: Cloning into bare repository '/home/ubuntu/.npm/_git-remotes/git-github-com-scality-cdmiclient-git-8f0c2e6-7531c719'...
npm ERR! git clone --template=/home/ubuntu/.npm/_git-remotes/_templates --mirror git@github.com:scality/cdmiclient.git /home/ubuntu/.npm/_git-remotes/git-github-com-scality-cdmiclient-git-8f0c2e6-7531c719: Warning: Permanently added 'github.com,<IP_ADDRESS>' (RSA) to the list of known hosts.
npm ERR! git clone --template=/home/ubuntu/.npm/_git-remotes/_templates --mirror git@github.com:scality/cdmiclient.git /home/ubuntu/.npm/_git-remotes/git-github-com-scality-cdmiclient-git-8f0c2e6-7531c719<EMAIL_ADDRESS>Permission denied (publickey).
npm ERR! git clone --template=/home/ubuntu/.npm/_git-remotes/_templates --mirror git@github.com:scality/cdmiclient.git /home/ubuntu/.npm/_git-remotes/git-github-com-scality-cdmiclient-git-8f0c2e6-7531c719: fatal: Could not read from remote repository.
npm ERR! git clone --template=/home/ubuntu/.npm/_git-remotes/_templates --mirror git@github.com:scality/cdmiclient.git /home/ubuntu/.npm/_git-remotes/git-github-com-scality-cdmiclient-git-8f0c2e6-7531c719:
npm ERR! git clone --template=/home/ubuntu/.npm/_git-remotes/_templates --mirror git@github.com:scality/cdmiclient.git /home/ubuntu/.npm/_git-remotes/git-github-com-scality-cdmiclient-git-8f0c2e6-7531c719: Please make sure you have the correct access rights
npm ERR! git clone --template=/home/ubuntu/.npm/_git-remotes/_templates --mirror git@github.com:scality/cdmiclient.git /home/ubuntu/.npm/_git-remotes/git-github-com-scality-cdmiclient-git-8f0c2e6-7531c719: and the repository exists.
npm WARN deprecated<EMAIL_ADDRESS>Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated<EMAIL_ADDRESS>Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated<EMAIL_ADDRESS>Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated<EMAIL_ADDRESS>to-iso-string has been deprecated, use @segment/to-iso-string instead.
npm WARN deprecated<EMAIL_ADDRESS>Jade has been renamed to pug, please install the latest version of pug instead of jade

><EMAIL_ADDRESS>install /home/ubuntu/S3/node_modules/ioctl
> node-gyp rebuild

ubuntu@propitious-production-rig:~/S3$ npm --version
3.5.2

ubuntu@propitious-production-rig:~/S3$ npm start

><EMAIL_ADDRESS>start /home/ubuntu/S3
> npm-run-all --parallel start_dmd start_s3server

><EMAIL_ADDRESS>start_dmd /home/ubuntu/S3
> npm-run-all --parallel start_mdserver start_dataserver

><EMAIL_ADDRESS>start_s3server /home/ubuntu/S3
> node index.js

><EMAIL_ADDRESS>start_mdserver /home/ubuntu/S3
> node mdserver.js

><EMAIL_ADDRESS>start_dataserver /home/ubuntu/S3
> node dataserver.js

module.js:549
    throw err;
    ^

Error: Cannot find module './build/Release/diskusage.node'
    at Function.Module._resolveFilename (module.js:547:15)
    at Function.Module._load (module.js:474:25)
    at Module.require (module.js:596:17)
    at require (internal/module.js:11:18)
    at Object.<anonymous> (/home/ubuntu/S3/node_modules/diskusage/index.js:1:76)
    at Module._compile (module.js:652:30)
    at Object.Module._extensions..js (module.js:663:10)
    at Module.load (module.js:565:32)
    at tryModuleLoad (module.js:505:12)
    at Function.Module._load (module.js:497:3)

npm ERR! Linux 4.15.0-15-generic
npm ERR! argv "/usr/bin/node" "/usr/share/npm/bin/npm-cli.js" "run" "start_s3server"
npm ERR! node v8.10.0
npm ERR! npm  v3.5.2
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>start_s3server: `node index.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start_s3server script 'node index.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the @zenko/cloudserver package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node index.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs @zenko/cloudserver
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls @zenko/cloudserver
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /home/ubuntu/S3/npm-debug.log
ERROR: "start_s3server" exited with 1.

npm ERR! Linux 4.15.0-15-generic
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "start"
npm ERR! node v8.10.0
npm ERR! npm  v3.5.2
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>start: `npm-run-all --parallel start_dmd start_s3server`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script 'npm-run-all --parallel start_dmd start_s3server'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the @zenko/cloudserver package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     npm-run-all --parallel start_dmd start_s3server
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs @zenko/cloudserver
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls @zenko/cloudserver
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /home/ubuntu/S3/npm-debug.log

Seems to be working with npm 6.1.0
https://asciinema.org/a/AnV7WCyMsFWH5fSEYt8R28tMS
Thank you for your patience :)


An extra DC power feed

It would be nice if the board could be powered from two DC Feeds (failover).

Adding an extra USB Type-C connector and using this PoE adapter might be a nice solution.
This would require a power selector switch or circuit for the ESP32 power.


Schedule crontab issue

Hi
I have made changes for the schedule crontab but it's not popping on dashboard, but from the command line i am able to see the values

on dash board

Without details, it is difficult to tell what the issue is in this case.
Does the browser's console provide more details?
Please note that Github Issues are not the appropriate forum for support on development questions. Please use the Gitter Channel


handling of ties in score

It looks like trec_eval handles ties by sorting (descending) by doc id. It would be nice to document this and also to standardize the behavior across dataset providers, if possible.

qrels:
0 0 0 0
0 0 1 1

run:
0 Q0 0 0 0 run
0 Q0 1 1 0 run

./trec_eval qrels run -m P.1
P_1                   	all	1.0000

@eugene-yang brought this up yesterday.
This is important because different providers do this differently, so they can essentially be scoring based on different rankings.
Both @eugene-yang @andrewyates -- what do you think would be the desired handling of this? Follow trec_eval's lead by always sorting by score (desc), docid (desc)? score (desc), docid (asc)? Rank if available? Something else?
Here are my thoughts:
I think the easiest way to standardize this would be to reassign run scores based on sorting by score and docid before sending to the provider. I believe all measures currently supported only consider the order, so this should only change the behaviour for ties. If different tie-breaking behaviour is desired, it can be done by whatever calls it. (E.g., pyterrier could provide its assigned ranks as the scores, rather than the scores themselves.)
Worth considering: Maybe we don't want to discard the order explicitly provided in the run file. In the above example, doc 0 is explicitly ranked above doc 1, based on the rank attribute. So in some sense, it's wrong for trec_eval to re-sort them. This was an explicit decision in trec_eval though:

In particular, note that the rank field is ignored here; internally ranks are assigned by sorting by the sim field with ties broken deterministicly [sic] (using docno).

And IIRC a prior version of trec_eval only used the provided ranks and discarded the score.
This would be an easy change on the surface. Basically, just replace the scores when reading trec run files with the ranks. But then would ties in ranks be broken by docid? Score (desc) then docid? Same problem. So maybe it's just best to stick with the scores, since trec_eval sets the precedent for ignoring rank.

Fair point RE implementation details of the providers themselves. I suppose the risk is that providers A and B end up scoring essentially different rankings due to ties, so the results may not align E.g., let's say P@1 is calculated by trec_eval and gives a score of 0.0 for a particular query. Meanwhile, ERR provided by gdeval could give a score of 1.0 due to different tie-breaking. To the user, these results would seem to be incompatible.
Documenting the tie-breaking behaviour of each tool would be another option.


add insecure registry(http) support

add insecure registry support, such as 'http://...'

I've merged an option for http support here: https://github.com/anchore/stereoscope/pull/75 is it okay to close this PR?

Thank you, it's ok to close this PR
Is it possible to modify the stereoscope version syft that depends this package?


How to do recursive downloads?

Hi, how do you do recursive downloads similar to this.

Recursive downloads is a feature that is beyond the scope of a simple HTTP client that HTTPie tries to be I'm afraid. But wget -r does a great job and there are other specialised tools such as HTTrack that are good at that.


Update README.md

Update the Documentation

Made spelling corrections e.g change concensus to consensus, involed to involved
Adjust spacing

Thanks! :)

Welcome, Happy to contribute.


Feature request: Upload files

Was wondering if adding the API routes for uploading files is planned for this project? I was taking a look to see if I could port over the TS/JS implementation, but my general working knowledge of TS/JS is a bit lacking for me to make any meaningful progress in the short time frame I was testing things out. Would be happy to help out with getting this feature in though!

Absolutely, I'm in a work crunch at the moment so might be a little slow but let me put together a plan and I'll add it to this thread! Thanks for your help on this @malaow3

I actually was able to make some headway on file uploads! Not a complete 1:1 of the JS/TS implementation but it's a decent start AND selfishly is good enough for my use case. I will clean up the code and put up a PR soon. Thanks for laying the groundwork with this package!


Add support of tr.anidub.com

Will be good if support of tr.anidub.com can be added.

The same as #161, it is very unlikely that I'll do it, if someone want to do it, PR will be welcome.


Fix a bug: unknown-option

Fix a bug: the parser signals unknown-option for --option when there is another longer option of the form --option-long.

This was merged in PR #25.


KeyVault old dependency causes warning at restore time

Version
v4.9.0
Describe the bug
Bot builder 4.9.0 references "Microsoft.Azure.Storage.Blob" v9.4.2 that, on restore, shows:
Package 'Microsoft.Azure.KeyVault.Core 1.0.0' was restored using '.NETFramework,Version=v4.6.1, .NETFramework,Version=v4.6.2, .NETFramework,Version=v4.7, .NETFramework,Version=v4.7.1, .NETFramework,Version=v4.7.2, .NETFramework,Version=v4.8' instead of the project target framework '.NETCoreApp,Version=v3.1'. This package may not be fully compatible with your project.

With later versions (I believe, starting with v10) of "Microsoft.Azure.Storage.Blob", that warning is removed. Can it be updated?
To Reproduce
Refere
Expected behavior
Although it is understood that the warning has no impact, still packaged dependencies should not throw non user-fixable warnings. Can you update the dependency?

Hi @EPinci
Unfortuantely, v10 of Microsoft.Azure.Storage.Blob has different dependencies and Bot Builder AzureBlobStorage and AzureBlobTranscriptStore expose CloudStorageAccount via the constructor.  We cannot update the Microsoft.Azure.Storage.Blob lib without a major version bump of Bot Builder, since the break would not adhere to semver rules we are following.

@cleemullins  maybe we should consider a v5 version of just https://www.nuget.org/packages/Microsoft.Bot.Builder.Azure in order to bring our dependencies up to the latest versions, and remove deprecated code.

Assigned to R10

@EPinci We have released a new package https://www.nuget.org/packages/Microsoft.Bot.Builder.Azure.Blobs which uses https://www.nuget.org/packages/Azure.Storage.Blobs/
Thank you for raising this issue.  Closing now.

Oh, hey, great!
I'm trying to use it and I have a few questions.
Since the problem was with Microsoft.Bot.Builder.Azure do I have to assume this package is a substitute (with a few type names changes) that does not include support for cosmos?
If I also need cosmos I need the former package and I'm back to square one?
Thank you.

@EPinci The new package uses the latest libraries for blob storage, so is not just a 'substitute' for the previous.
You are correct, if you also need CosmosDb then you will need to use Microsoft.Bot.Builder.Azure and the warning will still show.  We are somewhat tied down here, since we cannot upgrade to the latest Microsoft.Azure.Storage.Blob in a minor release due to the backward compat issues mentioned earlier.
Something you could do is ignore the NU1701 warning, as instructed in this issue: https://github.com/Azure/azure-storage-net/issues/834

@EricDahlvang I see. Since now I don't need CosmosDB... I'm perfectly fine with this new implementation. ;)
As a curiosity, have you guys figured out a long term for this?
Is this implementation going to fall back on Microsoft.Bot.Builder.Azure in the next major release?
Or are you going to split providers in different packages?
Or... neither of the two? :)
Thank you.

I believe the long term plan is to release individual packages, similar to what Azure is doing with Azure.Storage.* and as the Bot Framework team has done in 4.10.n with these two:
https://www.nuget.org/packages/Microsoft.Bot.Builder.Azure.Blobs
https://www.nuget.org/packages/Microsoft.Bot.Builder.Azure.Queues (preview)
We have found that a single Microsoft.Bot.Builder.Azure package, pulling in various storage dependencies, results in compatibility  issues, like this KeyVault problem.


[4.2] Wrap Throwables thrown from custom handlers in FatalThrowableError.

If a custom error handler throws a PHP 7 Error, Handler::formatException() causes this to happen:
PHP Fatal error:  Uncaught TypeError: Argument 1 passed to Illuminate\Exception\Handler::formatException() must be an instance of Exception, instance of Error given, called in /vagrant/vendor/laravel/framework/src/Illuminate/Exception/Handler.php on line 262 and defined in /vagrant/vendor/laravel/framework/src/Illuminate/Exception/Handler.php:328
Stack trace:
#0 /vagrant/vendor/laravel/framework/src/Illuminate/Exception/Handler.php(262): Illuminate\Exception\Handler->formatException(Object(Error))
#1 /vagrant/vendor/laravel/framework/src/Illuminate/Exception/Handler.php(147): Illuminate\Exception\Handler->callCustomHandlers(Object(Error))
#2 /vagrant/vendor/laravel/framework/src/Illuminate/Exception/Handler.php(171): Illuminate\Exception\Handler->handleException(Object(Error))
#3 [internal function]: Illuminate\Exception\Handler->handleUncaughtException(Object(Error))
#4 {main}
  thrown in /vagrant/vendor/laravel/framework/src/Illuminate/Exception/Handler.php on line 328

masking what the actual Error that happened was.  Simplest solution seemed to be to wrap the Throwable in FatalThrowableError before passing it along.  That seemed go along with what @GrahamCampbell mentioned in #15994, though that was a different situation.

Laravel 4.2 is no longer supported.

That didn't stop the special release, and the three after it, from being released.
This is a minor change that will greatly help myself and anyone else who uses custom error handlers that occasionally throw their own PHP errors.

This fix won't fix php 7 support properly. There were lots of changes I had to make to get 5.1 to work.


[PORT] Treat '@{' an error instead of text in LG

close: #1702

Pull Request Test Coverage Report for Build 107821

9 of 9 (100.0%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.008%) to 72.886%

Totals

Change from base Build 107782:
0.008%

Covered Lines:
8764

Relevant Lines:
11484

💛  - Coveralls


a Fields component within FormSection should not need to know the FormSection name

This fixes #2148,
Currently a Fields component within a FormSection needs to know what the FormSection prefix is in order to access the fields inside the Fields component. This PR makes it so that the form sectionPrefix doesn't carry over into the Fields component props. Also included is a test case.
<FormSection name='parent'>
  <Fields name={['foo', 'bar']} component={renderFields} />
</FormSection>

...

// current
const renderFields = ({parent: {foo, bar}}) => (

    <input {...foo} />
    <input {...bar} />

)

// proposed
const renderFields = ({foo, bar}) => (

    <input {...foo} />
    <input {...bar} />

)

Current coverage is 100% (diff: 100%)

Merging #2154 into master will not change coverage

@@           master   #2154   diff @@
=====================================
  Files          58      58
  Lines        1140    1141     +1
  Methods         0       0
  Messages        0       0
  Branches        0       0
=====================================
+ Hits         1140    1141     +1
  Misses          0       0
  Partials        0       0

Powered by Codecov. Last update cec0c7e...f25f3e7

Looks good.

Published in v6.2.1.


Issue on page /pre-hunt/data_documentation.html

Hey Roberto,
thanks for all the references!
The page mentioned above references this file, but the link is dead.
The sentence in question is "Translate useful fields to a YAML file as shown here."
Furthermore, in the section References, there is an ) too much.
Thanks again!
Matthias

Thank you for letting me know Matthias! I appreciate you taking the time :)


Make shopify theme dev more resilient to HTTP errors with the Admin API

WHY are these changes introduced?
Related to https://github.com/Shopify/cli/issues/4576, https://github.com/Shopify/cli/issues/4598, and https://github.com/Shopify/cli/pull/4599
Retry requests for some HTTP errors. This PR doesn't propose to refresh the session because we're already refreshing it every 30 minutes, the Admin session token expires in 2 hours, and we're getting a fresh token when we start the session.
WHAT is this pull request doing?
This PR updates the Admin REST API client to retry requests when they encounter certain HTTP errors. The Ruby CLI was more permissive regarding execution abortion, so we're adopting this approach as a middle-term to: fail when errors really happen but also be resilient and retry in some scenarios.
How to test your changes?

Run shopify theme push -d
Cherry-pick this commit e806941bd7538a0325593da4c02663c599f18e64 in your local CLI (it will trigger an error every time we update a file)
Update the layout/theme.liquid file
Run shopify theme push -d --verbose
Notice the retries happening in the logs

Post-release steps
N/A
Measuring impact
How do we know this change was effective? Please choose one:

[ ] n/a - this doesn't need measurement, e.g. a linting rule or a bug-fix
[x] Existing analytics will cater for this addition
[ ] PR includes analytics changes to measure impact

Checklist

[x] I've considered possible cross-platform impacts (Mac, Linux, Windows)
[x] I've considered possible documentation changes

🚀  Thank you! This looks great. I left a quick question about the retry time

@Shopify/app-inner-loop Could you please review this PR?(this is important to the next minor release). Thank you!


Unable to get proper results

Hi folks and @elgatito
PFA and I'm not getting proper results while compare to the website.
I have increased number of results to 25 in burst. Still problem not solved.
Pls help

Thanks in advance

https://elementumorg.github.io/contribute/log/

Even rarbg also having same issue.

hi anton thanks for the reply. i resolve the issue. by adding keywords.
"movie_keywords": "{title} x265 {year}",
Request to add in advanced section search with keyword instead of filter.

Request to add in advanced section search with keyword instead of filter.

please paraphrase.

Not much information here.Closing.


Update wordlist and fix typos

The PySpelling tool allows to easily detect some typos in the documentation, this tool can be run with tox -e spell command. This change updates the word list file and fixes some typos.

/approve

/lgtm


Using defaults for apps

Describe the feature you'd like to have in Pock
I wanted to make the music widget default to spotify, but if I close it, it goes to music
Describe alternatives you've considered
Tried leaving spotify open in background

You can already do this. Under pock in the menu bar, click on manage widgets. Next, click on the now playing widget. You will have the option of changing the default music app


Cors Pre Flight Request

Spring Cloud Version: Greenwich.RELEASE
To make my application work with CORS, I used the global cors in the yaml file as the following
spring:
cloud:
gateway:
globalcors:
corsConfigurations:
'[/**]':
allowedOrigins: ''
allowedMethods:
- ''
allowedHeaders: '*'
This actually works well  when there is no preflight request. However, if I make a call with an Authorization header (which will make the browser make a pre-flight request), this is not enough to make it work. I actually need to add a route like that:
routes:

id: options-S3-call
uri: someuirhere
predicates:
- Method=OPTIONS

I dont quite understand why this works, but shouldnt the globacors do the trick by itself? Moreover, the uri in the options route is simply irrelevant, but seems you need to have a route that matches the OPTIONS method for the pre-flight call in one of your routes, otherwise it won't work.
What I get is a 403 status and the following message:
"Access to fetch at 'http://localhost:8080/api/webcontent/en/menu' from origin 'http://localhost:3000' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled."

I have a PR for this: https://github.com/spring-cloud/spring-cloud-gateway/pull/520

Thanks for the reminder

implements WebFluxConfigurer
    @Override
    public void addCorsMappings(CorsRegistry registry) {
        registry.addMapping("/**")
                .allowCredentials(true)
                .allowedOrigins("*")
                .allowedHeaders("*")
                .allowedMethods("*")
                .exposedHeaders(HttpHeaders.SET_COOKIE);
    }

    @Bean
    public CorsWebFilter corsWebFilter() {
        CorsConfiguration corsConfiguration = new CorsConfiguration();
        corsConfiguration.setAllowCredentials(true);
        corsConfiguration.addAllowedHeader("*");
        corsConfiguration.addAllowedMethod("*");
        corsConfiguration.addAllowedOrigin("*");
        corsConfiguration.addExposedHeader(HttpHeaders.SET_COOKIE);
        CorsConfigurationSource corsConfigurationSource = new UrlBasedCorsConfigurationSource();
        ((UrlBasedCorsConfigurationSource) corsConfigurationSource).registerCorsConfiguration("/**", corsConfiguration);
        return new CorsWebFilter(corsConfigurationSource);
    }

Hello,
we also discovered this problem in our project.
Since the fix is planned to be released with version 2.1.3, I was looking for a way to use it right now.
We currently use 2.1.1.RELEASE.
Is there any version, milestone may be we could use right now?
thanks
Dmitri

@mitok you can use Greenwich.BUILD-SNAPSHOT

i tried the fix with BUILD-SNAPSHOT version and did not get it run.
this may because of my configuration.
I configured gateway RouteLocator bean and cors like this:
@Configuration
@EnableWebFlux
public class CorsConfig implements WebFluxConfigurer {
@Override
public void addCorsMappings(CorsRegistry corsRegistry) {
corsRegistry.addMapping("/**")
.allowedOrigins("http://ifap.vos:4200")
.allowedHeaders("")
.allowedMethods("");
//        .maxAge(3600);
}
also put this value into configuration.
spring.cloud.gateway.globalcors.add-to-simple-url-handler-mapping=true
This is what i get on start..

APPLICATION FAILED TO START

Description:
Field simpleUrlHandlerMapping in org.springframework.cloud.gateway.config.SimpleUrlHandlerMappingGlobalCorsAutoConfiguration required a bean of type 'org.springframework.web.reactive.handler.SimpleUrlHandlerMapping' that could not be found.
The injection point has the following annotations:
- @org.springframework.beans.factory.annotation.Autowired(required=true)
Action:
Consider defining a bean of type 'org.springframework.web.reactive.handler.SimpleUrlHandlerMapping' in your configuration.
I'm not very experienced in WebFlux and gateway. What could be wrong here?
thanks for help
regards
Dmitri

i configure this bean.
@Bean
public SimpleUrlHandlerMapping simpleUrlHandlerMapping() {
SimpleUrlHandlerMapping simpleUrlHandlerMapping = new SimpleUrlHandlerMapping();
return simpleUrlHandlerMapping;
}
but still get:
Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.
It seems that it does not work with RouteLocator or i do something wrong..

You should only have to set the property spring.cloud.gateway.globalcors.add-to-simple-url-handler-mapping=true. You should not need to create the SimpleUrlHandlerMapping bean since it should be provided by webflux.
I suggest you create a github project which demonstrates the issue you are seeing.

To version pre to 2.1.3.RELEASE, this works for me:
@Configuration
public class PreFlightCorsConfiguration {

    @Bean
    public CorsWebFilter corsFilter() {
        return new CorsWebFilter(corsConfigurationSource());
    }

    @Bean
    CorsConfigurationSource corsConfigurationSource() {
        final UrlBasedCorsConfigurationSource source = new UrlBasedCorsConfigurationSource();
        CorsConfiguration config = new CorsConfiguration().applyPermitDefaultValues();
        config.addAllowedMethod(HttpMethod.PUT);
        config.addAllowedMethod(HttpMethod.DELETE);
        source.registerCorsConfiguration("/**", config);
        return source;
    }
}

Unfortunately we can not use WebFilter. We have several Spring Boot Services embedded in one Big Spring Boot Service. So WebFilter is called twice in our configuration. Why and if we could avoid it is other story. If it called twice, the cors header is placed also twice in response and this does not like browser.

You should only have to set the property spring.cloud.gateway.globalcors.add-to-simple-url-handler-mapping=true. You should not need to create the SimpleUrlHandlerMapping bean since it should be provided by webflux.
I suggest you create a github project which demonstrates the issue you are seeing.

i will create a small sample.

To version pre to 2.1.3.RELEASE, this works for me:
@Configuration
public class PreFlightCorsConfiguration {

    @Bean
    public CorsWebFilter corsFilter() {
        return new CorsWebFilter(corsConfigurationSource());
    }

    @Bean
    CorsConfigurationSource corsConfigurationSource() {
        final UrlBasedCorsConfigurationSource source = new UrlBasedCorsConfigurationSource();
        CorsConfiguration config = new CorsConfiguration().applyPermitDefaultValues();
        config.addAllowedMethod(HttpMethod.PUT);
        config.addAllowedMethod(HttpMethod.DELETE);
        source.registerCorsConfiguration("/**", config);
        return source;
    }
}

Unfortunately we can not use WebFilter. We have several Spring Boot Services embedded in one Big Spring Boot Service. So WebFilter is called twice in our configuration. Why and if we could avoid it is other story. If it called twice, the cors header is placed also twice in response and this does not like browser.

I just run into the same problem. I use version Greenwich.BUILD-SNAPSHOT and set property spring.cloud.gateway.globalcors.add-to-simple-url-handler-mapping=true to enable the latest fix. The project started successfully, but the problem remains the same: preflight requests (with method "OPTIONS") are not handled.

To version pre to 2.1.3.RELEASE, this works for me:
@Configuration
public class PreFlightCorsConfiguration {

    @Bean
    public CorsWebFilter corsFilter() {
        return new CorsWebFilter(corsConfigurationSource());
    }

    @Bean
    CorsConfigurationSource corsConfigurationSource() {
        final UrlBasedCorsConfigurationSource source = new UrlBasedCorsConfigurationSource();
        CorsConfiguration config = new CorsConfiguration().applyPermitDefaultValues();
        config.addAllowedMethod(HttpMethod.PUT);
        config.addAllowedMethod(HttpMethod.DELETE);
        source.registerCorsConfiguration("/**", config);
        return source;
    }
}

this works for me! thx!

Hi @fifman
Which versions do you use?
I'm using Greenwich.SR2(-->spring-cloud-starter-gateway 2.1.2.RELEASE)
plus the Filter class that works for you.
But, I'm getting this error message:
has been blocked by CORS policy: The 'Access-Control-Allow-Origin' header contains multiple values '*, *', but only one is allowed.

Hi @fifman
Which versions do you use?
I'm using Greenwich.SR2(-->spring-cloud-starter-gateway 2.1.2.RELEASE)
plus the Filter class that works for you.
But, I'm getting this error message:
has been blocked by CORS policy: The 'Access-Control-Allow-Origin' header contains multiple values '*, *', but only one is allowed.

Could you double check your configuration? Looks like corsFilter applies twice in your filter chain.  I suggest you put a break point at the line of return new CorsWebFilter(corsConfigurationSource()); to see how many times it stops right there and where it comes from.

I did double check.
Duplication has a reason with spring cloud gateway,
I found a workaround here:
https://blog.csdn.net/zimou5581/article/details/90043178
Thanks a lot to this human.

This workaround does work and I suggest it be included as an option for a future release of Spring Cloud. Many thanks to Zimou5581 and kcotzen.
Baeldung describes the use of this type of Global, Ordered filter in
https://www.baeldung.com/spring-cloud-custom-gateway-filters
For anyone interested, I have made a slight modification to the workaround posted by Zimou5581. I already had a bean for the CORS config in SecurityConfig.java file.
    @Bean     CorsConfigurationSource corsConfigurationSource() {         CorsConfiguration configuration = new CorsConfiguration();         configuration.setAllowedOrigins(Arrays.asList("http://localhost:3000"));         configuration.setAllowedMethods(Arrays.asList("GET","POST", "PUT", "DELETE", "PATCH", "OPTIONS"));         configuration.setExposedHeaders(Arrays.asList("Authorization", "content-type"));         configuration.setAllowedHeaders(Arrays.asList("Authorization", "content-type"));         configuration.setAllowCredentials(true);         UrlBasedCorsConfigurationSource source = new UrlBasedCorsConfigurationSource();         source.registerCorsConfiguration("/**", configuration);         return source;     }
I then just created another file for the CorsResponseHeaderFilter and copied/pasted the code from Zimou5581.
`@Component
public class CorsResponseHeaderFilter implements GlobalFilter, Ordered {
@Override
public int getOrder() {
    // NettyWriteResponseFilter
    return NettyWriteResponseFilter.WRITE_RESPONSE_FILTER_ORDER + 1;
}

@Override
public Mono<Void> filter(ServerWebExchange exchange, GatewayFilterChain chain) {
    return chain.filter(exchange).then(Mono.defer(() -> {
        exchange.getResponse().getHeaders().entrySet().stream()
                .filter(kv -> (kv.getValue() != null && kv.getValue().size() > 1))
                .filter(kv -> (kv.getKey().equals(HttpHeaders.ACCESS_CONTROL_ALLOW_ORIGIN)
                        || kv.getKey().equals(HttpHeaders.ACCESS_CONTROL_ALLOW_CREDENTIALS)))
                .forEach(kv -> {
                    kv.setValue(new ArrayList<String>() {{
                        add(kv.getValue().get(0));
                    }});
                });

        return chain.filter(exchange);
    }));
}

}`
Everything worked as intended after that.

There's already a DedupeResponseHeader filter.

Spencer - thanks for the reply. Before implementing the workaround, I added the following to the application.yml file:
spring:   cloud:     gateway:       default-filters:         - DedupeResponseHeader=Access-Control-Allow-Origin Access-Control-Allow-Credentials, RETAIN_UNIQUE
Nothing changed so I sought the work around. Is there something in the yml that is incorrect? Also, is there a reference for this dedupe filter? I cannot find any links regarding this topic.
Any help is greatly appreciated. Best.

the unformatted yaml looks weird so I can't say
https://cloud.spring.io/spring-cloud-static/spring-cloud-gateway/2.2.1.RELEASE/reference/html/#the-deduperesponseheader-gatewayfilter-factory

Sorry about the bad yaml... I pasted into code section and that was result. Perhaps this is clearer:
spring:
cloud:
gateway:
default-filters:
- DedupeResponseHeader=Access-Control-Allow-Origin Access-Control-Allow-Credentials, RETAIN_UNIQUE
From the link you sent me, it appears that the DedupeResponseHeader filter needs to be inserted as a filter for each route and does not work as a global default-filter.
One more small question - is the strategy parameter separated from the response header cases with a comma?
Again, many thanks for the help. It is greatly appreciated.

no, just the examples show per filter, yes, separated by comma. If you have anymore questions please find us on gitter or stack overflow rather than a closed issue.

To version pre to 2.1.3.RELEASE, this works for me:
@Configuration
public class PreFlightCorsConfiguration {

    @Bean
    public CorsWebFilter corsFilter() {
        return new CorsWebFilter(corsConfigurationSource());
    }

    @Bean
    CorsConfigurationSource corsConfigurationSource() {
        final UrlBasedCorsConfigurationSource source = new UrlBasedCorsConfigurationSource();
        CorsConfiguration config = new CorsConfiguration().applyPermitDefaultValues();
        config.addAllowedMethod(HttpMethod.PUT);
        config.addAllowedMethod(HttpMethod.DELETE);
        source.registerCorsConfiguration("/**", config);
        return source;
    }
}

this works for me! thx!

For me too ! With Springboot 2.2.5.RELEASE, Spring cloud Hoxton.SR3, and Spring cloud security 2.2.1.RELEASE ! HUGE THANKS!!! :)

the unformatted yaml looks weird so I can't say
https://cloud.spring.io/spring-cloud-static/spring-cloud-gateway/2.2.1.RELEASE/reference/html/#the-deduperesponseheader-gatewayfilter-factory

it works for ,Thanks a lot!!!!
the dependency of my gateway  is org.springframework.cloud.spring-cloud-gateway.2.2.2.RELEASE

the unformatted yaml looks weird so I can't say
https://cloud.spring.io/spring-cloud-static/spring-cloud-gateway/2.2.1.RELEASE/reference/html/#the-deduperesponseheader-gatewayfilter-factory

it works for me ,Thanks a lot!!!!
the dependency of my gateway is org.springframework.cloud.spring-cloud-gateway.2.2.2.RELEASE

What configuration options did you try? I tried different combinations and it still doesn't work.

I showed the yaml I tried above although it did not work. IMHO - there is a problem with the built in Spring Gateway DeDupe filter. It may be with the documentation but I could not get it to work. I think others are experiencing the same. Implementing a filter directly with using the yaml for the built in filter works great. There are a few similar examples in this post. I suggest that you try these (it's basically copying and pasting into your app; you may have to add a new class to hold the bean, filter, etc.)

To version pre to 2.1.3.RELEASE, this works for me:
@Configuration
public class PreFlightCorsConfiguration {

    @Bean
    public CorsWebFilter corsFilter() {
        return new CorsWebFilter(corsConfigurationSource());
    }

    @Bean
    CorsConfigurationSource corsConfigurationSource() {
        final UrlBasedCorsConfigurationSource source = new UrlBasedCorsConfigurationSource();
        CorsConfiguration config = new CorsConfiguration().applyPermitDefaultValues();
        config.addAllowedMethod(HttpMethod.PUT);
        config.addAllowedMethod(HttpMethod.DELETE);
        source.registerCorsConfiguration("/**", config);
        return source;
    }
}

This worked for me thank you so much @hank-cp ...

I had same cors issue for preflight Options request with spring cloud gateway. it started working after put PreFlightCorsConfiguration class in and configuration in yml
spring:
cloud:
gateway:
globalcors:
add-to-simple-url-handler-mapping: true
corsConfigurations:
'[/**]':
allowedOrigins: "*"
allowedMethods:
- GET
- POST
- DELETE
- PUT
default-filters:
- DedupeResponseHeader=Access-Control-Allow-Credentials Access-Control-Allow-Origin
i am using 2.3.3.RELEASE spring boot, Hoxton.SR7 which is 2.2.4 for spring cloud


Support 6.0

Since we don't map a lot of the Query DSL yet this should just be a matter of tweaking some bits in elastic_types and updating CI to target 6.0.
The biggest change to think about is the removing support for multiple types per index. An implication is that we could remove indices as required parameters and rely on the type name as a default. It raises a question of whether all operations, like index_create, should require a generic document type.

I just tried to use this library with 6.0.0 and I got an error when indexing a document stating missing field "created", which I assume is because the created field has been removed and replaced with the operation field[1].
[1] https://www.elastic.co/guide/en/elasticsearch/reference/6.x/breaking_60_docs_changes.html

Ah thanks @mbilker! These are all localised to the responses side but are breaking changes so I'll need to roll them up into the next release. I don't have much blocking that besides a half-baked cluster sniffer so will work on 6.0 support and get that up on crates.io ASAP.

Thank you very much and glad to be of help!
Luckily I am only working on a small personal project and I just rolled back to 5.6.4, but I will likely test changes for 6.x support as I have two virtual machines, one with 5.6.4 and one with 6.0.0.

Just to communicate the plan here, I'm thinking I'll cut a release of 0.21.0 with the new client features, and then focus on support for Elasticsearch 6.0 purely for 0.22.0. I think that path should be clearer for people looking to upgrade, and anyone stuck on 5.0 for now can still get the benefit of some of these new features.

So what about 7.0? haha...
There doesn't seem to be that many breaking changes that we would have to worry about...

I would like to see this as well!

I've bumped our target up to 7.0, which we should "support" on master (and in the next preview) once #364 lands.

@KodrAus this upcoming cut looks AWESOME and promising. Thanks a bunch for your hard work here.
Do you know if/when you're going to cut a new pre release for 0.21?

Hi @flaper87! :wave:
I was going to work in support for the scroll API first, but there’s a lot of inventory on master now that fixes real issues. So I’ll just give the docs a run through and get it up on crates.io ASAP.

@KodrAus fantastic!
FWIW, I've been using master for the last three days and things seem to work for me. Looking forward to the next pre cut and to the next release! thanks again :)

Alrighty, I've published a new pre-release as 0.21.0-pre.5!
This one pushes our target version of Elasticsearch to 7.2. I've also refactored our integration tests so that they should be easier to add (there's still a lot of fiddling with async code though). So I think the only real blocker to a proper release is confidence that we support 7.x correctly and don't need to break a lot of other things.

Amazing!
My current use case is simple but I can try to come up with more thorough tests for this.
Thanks again 🤙😬

Thanks a lot for everything! Great work! Without you I wouldn't have been able to continue my work :)

With the latest pre-release, I'm getting an issue revolving around the document type. If I build out the mappings without ::static_ty(): ::index_mapping(), it's fine. Removing the wrapping "_doc": {} corrected the issue.

Hello,
Version field in hit struct is outdated for optimistic version control.
Could you add _seq_no and _primary_term ?
Nice crate btw !

@Bealiah-dev those were added in 08ed5ce8a9881bc4dfe546055c4f020f33ed01d7. Both the latest pre-release version (0.21.0-pre.5) and the latest stable release (0.20.10) do not have that commit though. It will be in the next release though!

@mwilliammyers Thanks , it's awesome.


Nonsense error messages when running test and serve.prod

I'm getting a bunch of nonsense errors when I try to run npm test or serve.prod, most of the line numbers referred to don't exist or do not reflect the error message that reported. I'm just copying a handful of them as I'm getting more than 100 lines. Has anyone else experienced the same or has an explanation for it?
src/client/app/+dashboard/dashboard.component.ts(47,42): error TS1005: ':' expected.
src/client/app/+dashboard/dashboard.component.ts(47,86): error TS1005: ',' expected.
src/client/app/+dashboard/dashboard.component.ts(47,95): error TS1005: ':' expected.
src/client/app/+dashboard/dashboard.component.ts(53,42): error TS1005: ':' expected.
src/client/app/+dashboard/dashboard.component.ts(53,81): error TS1005: ',' expected.
src/client/app/+dashboard/dashboard.component.ts(53,90): error TS1005: ':' expected.
src/client/app/+transactions/transaction-detail/transaction-detail.component.ts(45,45): error TS1005: ':' expected.
src/client/app/+transactions/transaction-detail/transaction-detail.component.ts(45,65): error TS1005: ',' expected.
src/client/app/+transactions/transaction-detail/transaction-detail.component.ts(45,74): error TS1005: ':' expected.
src/client/app/+transactions/transaction-detail/transaction-detail.component.ts(50,45): error TS1005: ':' expected.
src/client/app/+transactions/transaction-detail/transaction-detail.component.ts(50,69): error TS1005: ',' expected.
src/client/app/+transactions/transaction-detail/transaction-detail.component.ts(50,78): error TS1005: ':' expected.
src/client/app/+transactions/transaction-detail/transaction-detail.component.ts(55,45): error TS1005: ':' expected.
src/client/app/+transactions/transaction-detail/transaction-detail.component.ts(55,74): error TS1005: ',' expected.
src/client/app/+transactions/transaction-detail/transaction-detail.component.ts(55,83): error TS1005: ':' expected.
src/client/app/+transactions/transaction-detail/transaction-detail.component.ts(60,34): error TS1136: Property assignment expected.
src/client/app/+transactions/transaction-detail/transaction-detail.component.ts(60,99): error TS1005: '}' expected.
src/client/app/+transactions/transaction-detail/transaction-detail.component.ts(60,108): error TS1005: ':' expected.
src/client/app/+transactions/transaction-detail/transaction-detail.component.ts(60,109): error TS1005: ',' expected.
src/client/app/+transactions/transaction-detail/transaction-detail.component.ts(61,32): error TS1136: Property assignment expected.
src/client/app/+transactions/transaction-detail/transaction-detail.component.ts(61,44): error TS1005: ':' expected.
src/client/app/+transactions/transaction-detail/transaction-detail.component.ts(61,72): error TS1005: ',' expected.
src/client/app/+transactions/transaction-detail/transaction-detail.component.ts(61,74): error TS1110: Type expected.
src/client/app/+transactions/transaction-detail/transaction-detail.component.ts(61,75): error TS1161: Unterminated regular expression literal.
src/client/app/+transactions/transaction-detail/transaction-detail.component.ts(62,25): error TS1161: Unterminated regular expression literal.
src/client/app/+transactions/transaction-detail/transaction-detail.component.ts(64,21): error TS1161: Unterminated regular expression literal.

Ok, I found the cause of the errors. A $ sign character before a one way binding variable on their corresponding html files for the mentioned components:
${{transaction.amount}}

replaced by
${{transaction.amount}}

fixed the nonsense error messages coming from build.js.test and build.js.prod
Closing issue.


Hedera Sourcify search views have different behavior

Description
The search tool from the following link does not work as expected:
https://repository-verify.hashscan.io/select-contract/
See repro steps below for details.
Steps to reproduce

Contract address: 0x00000000000000000000000000000000002e7a5d

HashScan View (Partial Match ✅): https://hashscan.io/mainnet/contract/0.0.3045981

Search result from this view: https://verify.hashscan.io/#/lookup

Search result from this view: https://repository-verify.hashscan.io/select-contract/

For clarity, the verification results exist in Hedera Sourcify: https://repository-verify.hashscan.io/contracts/partial_match/295/0x00000000000000000000000000000000002E7A5D/
The search functionality from one of the views is what is broken.
Additional context
No response
Hedera network
mainnet, testnet
Version
Latest
Operating system
macOS

This lookup page doesn't work and should be deprecated:
https://repository-verify.hashscan.io/select-contract/
All lookups should route to:
https://verify.hashscan.io/#/lookup

The issue is:

the lookup page (https://verify.hashscan.io/#/lookup) support both plain address and mixed-case checksum address (per ERC-55). If you enter 0x00000000000000000000000000000000002e7a5d it converts it into 0x00000000000000000000000000000000002E7A5D
the select-contract form (https://repository-verify.hashscan.io/select-contract/) actually works but only supports the mixed-case checksum address, i.e. 0x00000000000000000000000000000000002E7A5D
Hence the disconnect.

This code is a dependency (furthermore an indirect one) of hedera-sourcify, and code that we currently do not control, so we need to investigate what is the best way to mitigate.


Fix build on Debian and other systems that enable PIE by default

Before the patch:
$ make clean all
rm -f *.o injector
cc -fPIC -c injector.c -o injector.o -Wall
injector.c:321:93: warning: excess elements in array initializer
  .start={.bytes={0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00}, .len=0},
                                                                                ^~~~
injector.c:321:93: note: (near initialization for ‘total_range.start.bytes’)
injector.c:322:91: warning: excess elements in array initializer
  .end={.bytes={0xff,0xff,0xff,0xff,0xff,0xff,0xff,0xff,0xff,0xff,0xff,0xff,0xff,0xff,0xff,0xff}, .len=0},
                                                                                ^~~~
injector.c:322:91: note: (near initialization for ‘total_range.end.bytes’)
injector.c: In function ‘inject’:
injector.c:778:2: warning: asm operand 15 probably doesn’t match constraints
  __asm__ __volatile__ ("\
  ^~~~~~~
injector.c:778:2: error: impossible constraint in ‘asm’
make: *** [Makefile:38: injector.o] Error 1
2

I had the same issue. Should I make another PR? Your seems to be abandoned.

This project was last updated 4 years ago. My PR was updated 3 years ago. So I'd say it's the project that is abandoned, not my PR. :)

@infinity0 I want to continue this project. Issues are closed. What should I do?


⚠ main has degraded performance

In c6be834, main ($MAIN_API_URL) experienced degraded performance:

HTTP code: 200
Response time: 25626 ms

Resolved: main performance has improved in 6e4a732.


Bump path version in stable/beta versions

The current version of the path package in flutter_test is 1.8.0 in both stable and beta versions.
The newer version is already used in master :
https://github.com/flutter/flutter/blob/5f105a6ca7a5ac7b8bc9b241f4c2d86f4188cf5c/packages/flutter_test/pubspec.yaml#L18
so maybe it can be picked up for the next beta candidate?

It sounds like you are asking for a cherry-pick of this version change. What is the critical need (per policy) for such a cherry-pick?

not cherrypick specifically, but just an issue to keep track that it gets bumped in the next beta candidate.

not cherrypick specifically, but just an issue to keep track that it gets bumped in the next beta candidate

For future reference, there are only two ways something gets into beta:

the normal process of landing before the branch point, in which case there's no need to track anything--everything that lands before the branch point is in the branch
a cherry pick to the existing beta

So the only reason to file an issue is if you are requesting a cherry pick.


Feature Request: Pass Resources As Data

If this is a duplication please feel free to point me to it.
This would need to be in Helm 3 rather than 2 because of the API change.
Helm currently passes the resource listing (e.g., that you can get with helm status) as a string that's custom build. For example, see how the JSON output looks for the status command.
{
    "info": {
        "Description": "Install complete",
        "first_deployed": {
            "nanos": 869943809,
            "seconds":<PHONE_NUMBER>
        },
        "last_deployed": {
            "nanos": 869943809,
            "seconds":<PHONE_NUMBER>
        },
        "status": {
            "code": 1,
            "notes": "MariaDB can be accessed via port 3306 on the following DNS name from within your cluster:\nirreverant-terrier-mariadb.default.svc.cluster.local\n\nTo get the root password run:\n\n    MARIADB_ROOT_PASSWORD=$(kubectl get secret --namespace default irreverant-terrier-mariadb -o jsonpath=\"{.data.mariadb-root-password}\" | base64 --decode)\n\nTo connect to your database:\n\n1. Run a pod that you can use as a client:\n\n    kubectl run irreverant-terrier-mariadb-client --rm --tty -i --env MARIADB_ROOT_PASSWORD=$MARIADB_ROOT_PASSWORD --image bitnami/mariadb --command -- bash\n\n2. Connect using the mysql cli, then provide your password:\n    mysql -h irreverant-terrier-mariadb -p$MARIADB_ROOT_PASSWORD\n",
            "resources": "==> v1beta1/Deployment\nNAME                         DESIRED   CURRENT   UP-TO-DATE   AVAILABLE   AGE\nirreverant-terrier-mariadb   1         1         1            1           2m\n\n==> v1/Pod(related)\nNAME                                          READY     STATUS    RESTARTS   AGE\nirreverant-terrier-mariadb-659794f44f-2bmkn   1/1       Running   0          2m\n\n==> v1/Secret\nNAME                         TYPE      DATA      AGE\nirreverant-terrier-mariadb   Opaque    2         2m\n\n==> v1/ConfigMap\nNAME                         DATA      AGE\nirreverant-terrier-mariadb   1         2m\nirreverant-terrier-mariadb-tests   1         2m\n\n==> v1/PersistentVolumeClaim\nNAME                         STATUS    VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS   AGE\nirreverant-terrier-mariadb   Bound     pvc-2ae73c8e-cb11-11e7-a9b6-080027ceaa8a   8Gi        RWO            standard       2m\n\n==> v1/Service\nNAME                         TYPE        CLUSTER-IP   EXTERNAL-IP   PORT(S)    AGE\nirreverant-terrier-mariadb   ClusterIP   <IP_ADDRESS>   <none>        3306/TCP   2m\n\n"
        }
    },
    "name": "irreverant-terrier",
    "namespace": "default"
}

This appears to be built in the kube.Get function used in places like tiller and passed as the string in the protobuf. Please correct me if I'm wrong somewhere.
Instead of passing this as a custom built string the request is to pass it in a data format (even if something like a json blob) and then pretty printing in a client. This would be better for outputting this data in other formats or if a UI were to use it.

/remove-lifecycle stale

/lifecycle frozen

@mattfarina do you know the context behind this change? Is this still needed or can we close this?

closing as inactive.


Feature/sdl 0236 tire status mismatch

Implements https://github.com/smartdevicelink/rpc_spec/issues/168
This PR is [ready] for review.
Summary
Mark the parameters of the TireStatus structure as non-mandatory in the MOBILE_API
CLA

[x] I have signed the CLA

@atiwari9 please review this PR

@JackLivio This PR is ready for Livio review. Thank you!

@theresalech This PR is ready for Livio review. Thank you!

@LitvinenkoIra Please see Jacks' review feedback above and let us know if you have any questions. Thanks!

@LitvinenkoIra Please see Jacks' review feedback above and let us know if you have any questions. Thanks!

@jordynmackool all Livio comments have been processed


Sync read status to inoreader

I manage my rss with inoreader, but it seems that the read status can not be synced back to inoreader site.
After reading some articles from my iPhone(subscribe with iOS NetNEewsWire with inoreader), these articles are still in unread status.
The version in macOS works well, it happned in iOS version only.
Read article in iOS -> didn't sync to inoreader -> can't sync to macOS

I also have the same issue and I’m using the latest version available (6.1.4)


can't use in OSX 10.12.5

I'm using the latest version 0.90.92

Works fine for me with 10.12.5.

Works fine for me too. You are talking about this project, right? Karabiner-elements, not Karabiner.

I’m talking about Karabiner-elements.
the first time I do the following settings, it doesn't work.

and when I restart this software,my settings disapperd.

I have exactly the same problem. MacOS updated overnight to 10.12.5 and now it doesn't work. Key modifications disappear when I close Karabiner Elements, and they don't have any effect while the app is open. I rely on this for work – help?

Does this happen after reinstalling as well?

reinstalling doesn't work!

That seems like a permission problem.
When user creates rules in KE, KE will write these rules into the settings file ~/.config/karabiner/karabiner.json. If this file is not writable, then nothing will work, and the rules will disappear every time you restart the app.
You may test if this file exists. If not, create this file and adjust the permission of it, and then create the rules in KE again.
$ touch ~/.config/karabiner/karabiner.json
$ chown $(whoami) ~/.config/karabiner/karabiner.json

Please note that the command above assumes you have an existing ~/.config/karabiner/ directory and that the permissions of that directory are correct.

the file exists and the permission is right!

What's the content of this file? If you write some rules directly into this file, will they work?

Yesterday I updated to the beta version 0.91.4, the problem still exists.
when I do the Simple Modifications in the software, it changed in real time in the file.
when I write some rules directly into this file, still doesn't work!
{
    "global": {
        "check_for_updates_on_startup": true,
        "show_in_menu_bar": true,
        "show_profile_name_in_menu_bar": false
    },
    "profiles": [
        {
            "devices": [],
            "fn_function_keys": {
                "f1": "display_brightness_decrement",
                "f10": "mute",
                "f11": "volume_decrement",
                "f12": "volume_increment",
                "f2": "display_brightness_increment",
                "f3": "mission_control",
                "f4": "launchpad",
                "f5": "illumination_decrement",
                "f6": "illumination_increment",
                "f7": "rewind",
                "f8": "play_or_pause",
                "f9": "fastforward"
            },
            "name": "Default profile",
            "selected": true,
            "simple_modifications": {
                "caps_lock": "return_or_enter"
            },
            "virtual_hid_keyboard": {
                "caps_lock_delay_milliseconds": 0,
                "keyboard_type": "ansi"
            }
        }
    ]
}

beta version 0.91.5 now works fine with me！

bump
same thing happens for me on 0.91.5
just remapping "right_option": "left_control"
installed it on a fresh MacBook pro 15 2014, permissions on the config file are ok, pretty much went through the same stuff @yuzhuxiang did, I have some other version working ok on the my MacBook 12 btw

It now works for me too – Thank you sooooooooooo much!
On Mon, Jul 3, 2017 at 1:03 PM, klnvnv<EMAIL_ADDRESS>wrote:

bump
same thing happens for me on 0.91.5
just remapping "right_option": "left_control"
installed it on a fresh MacBook pro 15 2014, permissions on the config
file are ok, pretty much went through the same stuff @yuzhuxiang
https://github.com/yuzhuxiang did, I have some other version working ok
on the my MacBook 12 btw
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/tekezo/Karabiner-Elements/issues/784#issuecomment-312627931,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJBjPTMWTfust5WedH0MkhqLr36wBP7qks5sKNingaJpZM4N9Yg1
.


Does harp  contain THREE post-processing?

Hey bro , Does harp  contain THREE's post-processing?  How can I use it?

@aoyaZY , check out:
https://www.harp.gl/docs/master/examples/#rendering_post-effects_all.html
https://www.harp.gl/docs/master/examples/#rendering_post-effects_themes.html

@nzjony ,thanks
I've seen those example before , those are about the whole scene or theme post-processing
I am trying to make custom Object's effects , like single building bloom or something
so I need some module like EffectComposer,RenderPass and so on , just like what THREE‘s’ doc said: https://threejs.org/docs/index.html#manual/en/introduction/How-to-use-post-processing
Does harp contain these module? Or I need to import by myself ?

Hard coding the effects in the code was first imagined to quickly benefit the threejs rendering possibilities. However it does not allow generation of custom effects, an API would need to be design in that purpose, which would be more reasonable and maintainable as well. It was first planned for demoing and was surely not the most consensual idea.

@aoyaZY , I'm not quite sure I follow, my understanding of post-processing is that it applies some processing to the currently rendered output, so if you wanted some single building / object bloom, you would need to render it separately and then overlay it on the scene. Is that what you mean?
Yes, as mentioned by @Astrak , what we have would need to be extended to make it more customizable, we had another request to add this, see: https://github.com/heremaps/harp.gl/issues/1561
I will ask internally if we can raise the priority to add such an API to expose the EffectComposer etc.

@aoyaZY , do you mean something like: https://threejs.org/examples/?q=post#webgl_postprocessing_unreal_bloom_selective ?
Or is there another three.js demo which shows what you want to achieve?

@aoyaZY , we found a ticket that @Astrak  had created a while back to add this API, I have linked it.

I actually remember a request for such a thing as highlighting a road or a building at the time of the implementation of the post processing. However I think it was not possible to determine the semantics of the result of the raycasting (a building can be several polygons, like for the ones in NY). I don't remember what data this applied to though, and if it could now be possible.

@Astrak, I think for buildings it would unfortunably not be possible, at least there is no unique ids generated for the buildings in the data that I am currently aware of. Unless the buildings were somehow ID'ed by location. For roads, I guess you have the same problem. BTW, have you seen: https://www.harp.gl/docs/master/examples/#object-picking.html ? It at least shows picking of roads is possible.

@nzjony ,  yes , that's the example I have seen , you do know what I'm talking about .
And I know what you're going through , good luck !
I will try MapRenderingManager , thanks !

@aoyaZY , thanks. All the best and let us know how you get on. Either re open this issue or create a new one if you have problems / need help.


Add constraint for non-blank strings

Hi there 👋
Awesome project, love the v2 changes! I was experimenting with it at one of our apps and one of the refined types I tend to abuse (particularly when it comes to user input) is non-empty strings. So I thought you might be interested in having this here?
Let me know if there's anything that I need to do more for the PR (tests, etc)

Hi @kyri-petrou.
Firstly, thank you for this PR! I am always glad to see people contributing to Iron 😄 .
I see the benefits of a "not only whitespaces" String constraint and understand why it can be useful. However, I have concerns on 2 points:

Can't this constraint be made using a type alias on Match? For example: type NonWhitespace = Match["(.|\s)*\S(.|\s)*"]
Is this constraint common enough to justify putting it in the core lib?

Ultimately, I think a NonEmpty constraint (for collections and strings) has its place in the main module (really common like in Cats via NonEmptyList etc...) but not with this special treatment for whitespaces. In my opinion, NonEmpty should be an alias for MinLength[1]. If we add your proposal to the core lib, I would rather choose a more explicit name like NotOnlyWhitespace or something like that.

Thanks for taking the time to review this! I'll try my best to answer your (very valid) questions:

Can't this constraint be made using a type alias on Match

Definitely. Particularly for strings that can be refined during compile-time, this would probably be preferable. The main issue however is with variable strings / runtime refinements. User input strings in applications can be very large, so performing regex operations on them can be rather expensive (albeit I don't know much about the underlying Scala / Java implementation so I could be wrong). The approach in this PR "breaks" after the first non-whitespace character so it's a very cheap runtime refinement as in 99.9% of the cases, the first character will not be a whitespace one.

Is this constraint common enough to justify putting it in the core lib

Frankly, I don't know how common it is. My opinion is heavily biased since I've been "bitten" before by issues due to strings in databases that contain only whitespace characters due to user input. I've also seen empty strings more often than not used in Postgres where the columns don't allow for nulls. I don't have any solid evidence, but I'd be surprised if more people were not interested in it

I would rather choose a more explicit name like NotOnlyWhitespace

That's a valid point, I agree. Happy to rename it :)

I think this PR requires more feedback about the commonness of such constraint. Can you push the new constraint name to this PR?

An example showing the use case if possible would be appreciated to better measure how this constraint is common and useful in your codebase.

A very simple example which is already in the docs would be the field name for User if we were to allow non-Latin characters:
case class User(name: String :| NotBlank, age: Int :| Greater[0])

Other usecases:
case class Book(title: String :| NotBlank)
case class Item(id: String :| UUIDLike, description: String :| NotBlank)

If you're happy with any of these I can add them in /docs

Another very common usecase is messaging / chat apps. Most apps won't allow you to send a string that contains only whitespace characters. In fact, Github won't allow comments that are blank strings either 😅

Apologies for the multiple comments, I just keep thinking of more valid examples. I also think that it's very expressive and dev friendly. The Item example above can be changed to:
case class Item(id: String :| UUIDLike, description: Option[String :| NotBlank])

In this example, it becomes immediately clear to the developer that the string would still be non-empty after one calls .trim(). Option[String :| MinLength[1]] on the other hand would still leave the possibility that the string would become empty.

The change seems good to me. I am however wondering if a Blank instead of a NotBlank constraint would be better to avoid double negation if someone wants to check for a blank String. To check if a String is not blank, the user would use Not[Blank] which is not that longer.
In fact, Refined also uses Blank (named Whitespace) instead of NotBlank.
So I think NotBlank should become Blank to avoid double negation and then, we should be ok to merge this PR 👍

Thanks, made the changes!

I still think there might be some value in providing the negation of the predicate in cases where it's what is likely the most common use-case (e.g., NonEmpty, NonBlank). refined for example provided both Empty and NonEmpty predicates for collections, as well as Positive and NonPositive etc for numericals.

https://github.com/fthomas/refined#provided-predicates

I still think there might be some value in providing the negation of the predicate in cases where it's what is likely the most common use-case (e.g., NonEmpty, NonBlank).

Do you think it provides more value than Not[Blank] and Not[Empty]? This is not a rethorical question at all. I really wonder.
My main concern is mostly about user experience: should I use NonEmpty or Not[Empty]? I want a constraint that checks if my constraint C does not pass, should I look for a NonC first?

Do you think it provides more value than Not[Blank] and Not[Empty]

I think the only real value is that you don't need to use the brackets, which can be cumbersome when dealing with nested types, e.g.,
Map[String :| NonBlank, List[String :| NonBlank]] // imho reads better
Map[String :| Not[Blank], List[String :| Not[Blank]]]

However, this is very minor benefit and I think the point you're raising regarding confusion is very valid, so it's probably best not to add them as separate types for the time being and maybe consider it in the future if more people need them

so it's probably best not to add them as separate types for the time being and maybe consider it in the future if more people need them

That's my opinion. Even if we don't add it when 2.0.0 is released, adding a simple alias like this does not break anything so we can add it later if there's more demand.

Can't seem to be able to merge due to this reason. Is there something I missed or that's normal?

It is my bad. I have to check how to remove this warning since pages deployment should not be triggered on working branches.


PORT

how exactly each service communicate each other?
and is it okay if i changed pprof or expose port?

SFU, ISLB, AVP and BIZ mostly interact with each other using NATS as a messaging queue and etcd for service registration. ISLB also uses redis internally as a routing cache (I think).
PProf is a profiling helper for development and not necessary in production; you can disable it in the config.toml for each service, and if you do leave it enabled you should ensure the port isn't accessible. Also I think docker-compose is the most common/advised way to run the services, so if you don't expose the pprof ports on the docker containers, nobody can access it.
The only service that needs an outside port for ion is biz:8443 which is a websocket signal interface for sending join() and publish() and subscribe() messages, basically. If you are running ion-app-web also via docker (recommended) as a web UI, you should keep biz:8443 private and expose ion-app-web (it's a Caddy reverse proxy) over port 443 for HTTPS -- Caddy will serve the necessary HTML+JS, and will proxy all requests to /ws to biz:8443 over the internal docker network.

Thanks a lot @leewardbound
But how about listen port for biz?
can i change the port to 80 instead port 8443?
and how about SFU server? i read in WIKI it must expose port 5000-5200/udp,
please your help, thanks a lot

Yes, you can change biz to 80 if you want, if you aren't using ion-app-web. Biz does not really serve a UI though so I don't know why you'd want it to be on 80; up to you.
Yes, sorry I forgot to mention that (large) detail - SFU also has to open UDP ports, 1-or-more per webrtc connection. You can specify the port range in the config; really you should try to make as many ports as possible available, 200 isn't very many for a large conference server. I'm experimenting myself with opening 50,000+ UDP ports but I don't think there's any official documentation around this.

allright thanks a lot @leewardbound
can i create 3 instance of each services ( biz, islb, sfu, avp ) ?

Hi @leewardbound
Is SFU needs an outside ports or just open udp ports internally?

UDP ports need to be open externally to establish webrtc transport

@masatrio-business-account The plan is to support multiple of each service, but currently behavior for multiples of each instances isn't well defined; it is still very WIP and unsupported.

thanks guys @tarrencev @leewardbound
whats avp?
why avp need - "./:/out/" volume in docker compose?

avp is for audio/video processing. the mounted directory is for outputting recordings

is there any extra configuration if i deploy ion-web-app and ion-backend in separate domain?
please help, thanks

can you guys guide me to deploy this service separately?
i need this to deploy it for education startup in indonesia, thanks a lot

Sorry, this use case is not currently supported. It might be possible, but
we aren't completely sure, and we can't really help you through this.
Also, we should close this ticket. This ticking system is primarily for bug
reports and tracking issues, rather than support tickets -- since it seems
like you need a lot of assistance, you might find someone kind enough to
help in #pion on the Golang Gophers slack chat, there's a link on the
project page to join -- but our project is run by a community of
volunteers, so if you wind up getting that working, you should write a
guide for our docs!
On Sun, Jun 14, 2020 at 10:56 PM masatrio-business-account <
<EMAIL_ADDRESS>wrote:

can you guys guide me to deploy this service separately?
i need this to deploy it for education startup in indonesia, thanks a lot
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/pion/ion/issues/302#issuecomment-643919047, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AADAOY5S6FX4XMM5JU2R6PLRWWZYZANCNFSM4N3FIL5A
.


refactor: rationalise into a single version

Refs #33.
This doesn’t completely resolve #33, because there’s still duplicative code in src/raphael_backend_flask/youtube.py and src/health_misinfo_shared/youtube_api.py. But it gets some of the way.

Pull request checklist

[x] I have linked my PR to an issue
[x] I’ve used conventional commits
[x] My branch is up-to-date with main
[ ] Where appropriate, I have added or updated tests
[ ] Where appropriate, I have updated documentation to reflect my changes

nice one clarifying some variable names

I didn’t do that – that was you! I attempted to merge chunked_transcript and form_chunks. The variable renaming was in chunked_transcript.

(but I agree – the variable renaming here is good!)


Cannot resolve method 'displayPreview(android.graphics.SurfaceTexture)' in ConversationHelper.Java

I have followed steps given in read me, but still getting one error in file ConversationHelper.java at line number 353. Screenshot attached for the reference.

It seems the method has been renamed to showPreview() but not changed in ConversationHelper class.

Thanks for reporting this.
Yes this is renamed to showPreview. We will fix this.


Fix and refactor deployer reconciliation

How to categorize this PR?

/area deployers
/kind bug
/priority 3
What this PR does / why we need it:
This PR depends on PR https://github.com/gardener/landscaper/pull/465. It refactors the reconciliation of the deployer sich that:

coding is better readable
errors which are not LsErrors are not lost
error codes of LsErrors deeply embodied in other errors are collected

Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Release note:

NONE

/test


[EventRequest] SalesTaxCalculate.Codeunit.al (codeunit 398 "Sales Tax Calculate")

Hi MS,
Please help us in migrating our verticalized solution by adding below events in SalesTaxCalculate.Codeunit.al codeunit.
Standard Code (Screenshot from DistTaxOverSalesLines)

Modified Code

Event Signature

Thanks
SUD

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.

Hi There,
In requested event amount should be passed as parameter by VAR.
Kindly update!!
Thanks
SUD

Please create a new request.  Don't forget to mention the precise name of the object and the event.
Please always put all details in text instead of screenshots.


Added the logo of MakesMathEasy at the center of the page

Related Issue

The issue was that the website looks blank as it has only the search bar, and the number fact.

Closes: #90
Describe the changes you've made
In order to remove the issue I had created, I added the logo of MakesMathEasy at the top center of the page. I wanted to make it look like google.
Checklist:

[x] My code follows the style guidelines of this project.
[x] I have performed a self-review of my own code.
[ ] I have commented my code, particularly in hard-to-understand areas.
[ ] I have made corresponding changes to the documentation.
[x] My changes generate no new warnings.

Screenshots
Updated

After changing mode

Thankyou @shrey27tri01                                                                                I wanted to ask if I have to do anything else after making PR? This is my first PR, I don't have any idea of what to do next.

@gritika18 There's nothing more you need to do after making the PR. It has been approved by me, and once other mentors or the project admin approves it, it will be merged to the main project :)

@gritika18 There's nothing more you need to do after making the PR. It has been approved by me, and once other mentors or the project admin approves it, it will be merged to the main project :)

Okay, thankyou :)


blockchain: remove v1 and make v2 default

Description
Remove v1 as there is a bug present in it.
Make v2 the default. There has been some testing in the real world with this reactor, more will happen soon.
Closes: #13

On one hand, I'm a bit wary about making the default reactor v2 just yet. On the other had it is still very, very early days for ll-core so it's a perfect playground to test the new reactor. By the time we launch our first dev or test-net, the v2 reactor will be battle-tested 👍  And the v0 reactor isn't really accessible anyways. Thanks @marbar3778!


adding custom color picker

Description 📜
A web-app based Color-Choosing Game
Fixes #703

Type of change 📝
Please delete options that are not relevant.And in order to tick the check box just but x inside them for example [x] like this

[x] Add a new project

Domain of Contribution 📊
Please delete options that are not relevant.And in order to tick the check box just but x inside them for example [x] like this

[x] Project using HTML, CSS & JS

Checklist ✅
Please delete options that are not relevant.And in order to tick the check box just but x inside them for example [x] like this

[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I'm GSSoC'22 contributor

Screenshots / Gif (Optional) 📸

@khushi-purwar please merge this PR, upon reviewing it.

@khushi-purwar please merge this PR, upon reviewing it.

@khushi-purwar Can you please review this PR and merge it upon finding it correct.

This branch is 1 commit ahead, 187 commits behind khushi-purwar/WebDev-ProjectKart:master.

This branch is one commit ahead because of its own commit and when I made this PR, the branch was fully fetched and merged.
So please approve this PR, as that is because of the delay in approval and merge

@khushi-purwar and @gurjeetsinghvirdee when I was assigned this issue i was given a level label 3 as my other issues and PR, it seems that you have removed those to ass new, please understand that we worked on these issues considering the amount of points we were getting, so please restore my old level lables in all the PRs because I started working on them post the level label was addressed.

This branch is 1 commit ahead, 187 commits behind khushi-purwar/WebDev-ProjectKart:master.

@khushi-purwar and @gurjeetsinghvirdee This branch is one commit ahead because of its own commit and when I made this PR, the branch was fully fetched and merged. So please approve this PR, as that is because of the delay in approval and merge

@khushi-purwar can you review this PR now, and please merge it with its original level label.

@gurjeetsinghvirdee and @khushi-purwar I fetched upstream and merged into this branch. Can you once check this too


speed LDA (individual Experiments) broken

happened since the last changes. May be the same with other speed LDA functions.

Fix has been put in to resolve this issue and is available on Subiculum.


Update README.md

Fixed typo

@dasa just pinging you, fixed a teeny typo but don't have write permissions to fix it directly.


Smoke test Kotlin Gradle Plugin 1.5.0-RC

See https://github.com/JetBrains/kotlin/releases/tag/v1.5.0-RC

@bot-gradle test AST

OK, I've already triggered AllSmokeTestsReadyForMerge build for you.

@bot-gradle help

Currently I support the following commands:

@bot-gradle test {BuildStage} to trigger a build

e.g. @bot-gradle test SanityCheck plz
SanityCheck/CompileAll/QuickFeedbackLinux/QuickFeedback/ReadyForMerge/ReadyForNightly/ReadyForRelease are supported
test this means test ReadyForMerge
test and merge to trigger a pre-tested commit build
SanityCheck can be abbreviated as SC, ReadyForMerge as RFM, etc.
Specific builds:

AST: AllSmokeTestsReadyForMerge
AFT: AllFunctionalTestsReadyForMerge
ASB: AllSpecificBuildsReadyForMerge
ACT: AllCrossVersionTestsReadyForNightly
APTN: AllPerformanceTestsReadyForNightly
AFTN: AllFunctionalTestsReadyForNightly
ACTR: AllCrossVersionTestsReadyForRelease
AFTR: AllFunctionalTestsReadyForRelease

@bot-gradle help to display this message
@bot-gradle clean to clear the conversation history

@bot-gradle help

Currently I support the following commands:

@bot-gradle test {BuildStage} to trigger a build

e.g. @bot-gradle test SanityCheck plz
SanityCheck/CompileAll/QuickFeedbackLinux/QuickFeedback/ReadyForMerge/ReadyForNightly/ReadyForRelease are supported
test this means test ReadyForMerge
test and merge to trigger a pre-tested commit build
SanityCheck can be abbreviated as SC, ReadyForMerge as RFM, etc.
Specific builds:

AST: AllSmokeTestsReadyForMerge
AFT: AllFunctionalTestsReadyForMerge
ASB: AllSpecificBuildsReadyForMerge
ACC: AllConfigCacheTestsReadyForMerge
ACT: AllCrossVersionTestsReadyForNightly
APTN: AllPerformanceTestsReadyForNightly
AFTN: AllFunctionalTestsReadyForNightly
ACTR: AllCrossVersionTestsReadyForRelease
AFTR: AllFunctionalTestsReadyForRelease

@bot-gradle help to display this message
@bot-gradle clean to clear the conversation history

@bot-gradle test ACC

OK, I've already triggered AllConfigCacheTestsReadyForMerge build for you.

@bot-gradle test AST

OK, I've already triggered AllSmokeTestsReadyForMerge build for you.

@bot-gradle test AST

OK, I've already triggered AllSmokeTestsReadyForMerge build for you.

@bot-gradle test AST

OK, I've already triggered AllSmokeTestsReadyForMerge build for you.

@bot-gradle test AST

OK, I've already triggered AllSmokeTestsReadyForMerge build for you.

@bot-gradle test AST

OK, I've already triggered AllSmokeTestsReadyForMerge build for you.

@bot-gradle test RFN

OK, I've already triggered ReadyForNightly build for you.

@bot-gradle test RFN

Sorry some internal error occurs, please contact the administrator @blindpirate

@bot-gradle test AST

OK, I've already triggered AllSmokeTestsReadyForMerge build for you.

@bot-gradle test AST

OK, I've already triggered AllSmokeTestsReadyForMerge build for you.

@bot-gradle test RFN

OK, I've already triggered ReadyForNightly build for you.

@bot-gradle test RFN

OK, I've already triggered ReadyForNightly build for you.

@bot-gradle test and merge

Your PR is queued because #17064 is being built.

OK, I've already triggered a build for you.

Pre-tested commit build failed.

@bot-gradle test and merge

Your PR is queued because #17064 is being built.

@bot-gradle test and merge

OK, I've already triggered a build for you.