Don't hardcode dh params

Break the hardcoded DH params and you can break encryption on all ZNCs.

https://github.com/znc/znc/blob/znc-1.6.1/src/Utils.cpp#L44-L51 or is there even a need of breaking?
https://www.eff.org/deeplinks/2015/10/how-to-protect-yourself-from-nsa-attacks-1024-bit-DH
https://freedom-to-tinker.com/blog/haldermanheninger/how-is-nsa-breaking-so-much-crypto/

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Just to measure things, I generated my own dhparams. This printed three pages of mixtures of dots and pluses and took 6 minutes. In the same time I was using the computer in other ways, so I guess there was more entropy available than in some freshly booted server doing nothing else.

Let me put my two cents.
Firstly, it doesn't take too long to generate the dhparams for 2048bit.  Secondly, let's take a page out of webservers: Allow a custom dhparams file to be used.
This then is the logic:
if (CUSTOM DHPARAM PROVIDED) then (USE CUSTOM)
else (USE HARDCODED).
Most webservers seem to still do this type of function.  Let people generate the dhparams with OpenSSL or others and then use the custom ones if they have been provided as a config option.

We allow custom dhparams... It's read from znc.pem.
The default hardcoded one is used only during znc --makepem to write znc.pem

Custom dhparams on a separate file seem to have become supported (by https://github.com/znc/znc/pull/1192?) or I don't see ZNC complaining about SSLDHParamFile = /home/znc/.znc/ssl/dh.pem.
I am still not sure on the default hardcoded ones though.

I dont think they are hard coded in ZNC but in the SSL libs.  Which is why we support the params file now...

It's read from SSLDHParamFile, yes, which defaults to ~/.znc/znc.pem. If that file doesn't have DH params, the pregenerated (hardcoded) one is used.
I don't see the problem.

I think the bigger issue here is, that we don't have DHParams.  It's almost like this request is "If there are no defined DHParams in znc.pem AND there are no separate dhparam files, generate some.
@Mikaela is this what you're looking for?  All libssl driven systems 'inherit' the default DHParams.  (We could alter default SSL Ciphers to drop all DHE ciphers (but not ECDHE which uses elliptical curves instead of DHParams))

I am under impression that ZNC has dhparams in https://github.com/znc/znc/blob/znc-1.7.4/src/Utils.cpp#L69-L76 that are put to znc.pem or used by default and that if they are broken (or is that like a private key that doesn't need to be broken as it's there for anyone to see?), the traffic between most of ZNC instances and IRC client is followable by parties such as the NSA as indicated by the articles I linked four years ago.
I don't know about the default parameters of lbssl systems and I am not sure if I even understand DH.

dhparams are not private. Moreover, if server supports DH at all, it tells the SSL client what the values are.


Transformer LM lattice rescoring

To be updated.

Implement PyTorch Transformer LM lattice rescoring in the Decoder class of kaldi-serve core C++ library. Please find a similar implementation for RNN LM lattice rescoring here. The idea here is to be able to rescore the n-gram LM lattice using a more sophisticated model like a Transformer to acheive greater accuracy.
Relevant links:

PyTorch NN Lattice Rescoring - script
NN LM Rescore - Source
LM Lattice Rescore - Source


Start notebook for persistence landscapes

Add axis passthrough for simple plotting functions a la persim/visuals.py

Fixed this bug in latest commit. Should work for you now!

Fixed this bug in latest commit. Should work for you now!

Awesome. I'm about to push another notebook that is quite similar to yours. Would you mind if we took yours in another direction? I noticed you wanted some edits made to it anyways.

Awesome. I'm about to push another notebook that is quite similar to yours. Would you mind if we took yours in another direction? I noticed you wanted some edits made to it anyways.

Sure. I'll merge the two branches, and you can commit your notebook with a different name. I'm interested to take a look at it and see what the best direction is for my notebook.

Sure. I'll merge the two branches, and you can commit your notebook with a different name. I'm interested to take a look at it and see what the best direction is for my notebook.


Failed to create raster dataset because of out of memory

I am trying to run the dem_parameters.py script, however I get this error when it tries to fill:
ERROR 999999: Error executing function.
Failed to create raster dataset
Failed because of out of memory
Failed to execute (Fill).
I have a 4GB DEM at 1 meter resolution.
Python memory use only reaches 600MB of memory and I have 9GB available.
Any idea what could be happening or what I might be doing wrong?
Thank you in advance
Nada

Hi @nsydro
I think this maybe caused by Arcgis. If you use a 32-bit application, then the limit RAM is about 800Mb. You need to try a 64-bit geoprocessing application. Or you can split your file.


Update connecting-to-applications-port-forward.md

Fixed invalid port typo on line 23.

I signed it!

LGTM, thanks


is export compatible for android?

I did not succeed.
I generated the apk and installed it on my smartphone, but the game didn't work

You can try the new publish template apk from the release page.


fix #19: Update HTTP File Upload Component dependency to v1.3.0

The build currently fails, as the new dependency (which has just been released) isn't available through Maven yet. The build will probably succeed in a few hours.


Runtime Error

On a fresh install today I am unable to get past the login screen (when I hit Enter to login the app crashes and throws npm errors)
Debian 3.16.0-4-amd64
ipfs 0.4.5-dev (built from go-ipfs master, ipfs daemon --enable-pubsub-experiment works fine when run from command line)
<EMAIL_ADDRESS><EMAIL_ADDRESS>(also tried v6.9.2 and v6.0.0)
Here's my npm debug log: npm-debug.txt I thought maybe the errors were due to using node v7, so I downgraded to node v6.9.2 but got the same errors:  npm-debug_v6.9.2.txt It appears to be failing on the call to npm run electron
Probably unrelated, but I also received the following warnings during npm install:
npm WARN deprecated<EMAIL_ADDRESS>This package is discontinued. Use<EMAIL_ADDRESS>npm WARN deprecated<EMAIL_ADDRESS>use uuid module instead
npm WARN prefer global<EMAIL_ADDRESS>should be installed with -g

I can reproduce this:
[ERROR] orbit-electron: TypeError: IpfsDaemon is not a constructor

links to this:
https://github.com/haadcode/orbit/blob/master/index.js#L130
@haadcode, has the IpfsDaemon interface changed ? Will try to fix it but diving into IpfsDaemon object asap
Thanks for the report @rsynnest

Thanks for reporting this @rsynnest. Not sure what's going on here, the logs don't tell much. Could you run it with LOG=debug npm run electron and drop the output here?

[ERROR] orbit-electron: TypeError: IpfsDaemon is not a constructor

@theobat This sounds like dependency conflict. The interface for IpfsDaemon was indeed changed, see https://github.com/haadcode/ipfs-daemon. So what I take from this report is that there's an old version of ipfs-daemon there and it's trying to use that.

My mistake, I thought that the logfile would be more verbose than stdout. I've pasted stdout logs below (after running LOG=debug npm run electron).
The core issue seems to be:
Inconsistency detected by ld.so: dl-close.c: 762: _dl_close: Assertion `map->l_init_called' failed!

So, looks like an error in dynamic linking? I'm running glibc 2.19-18+deb8u6 , not sure if this is an issue in ipfs or what. Full stdout error logs below:
><EMAIL_ADDRESS>electron /home/rsynnest/src/orbit
> LOG=debug IPFS_FD_MAX=4096 $(npm bin)/electron .

2016-12-07T17:48:09.107Z [DEBUG] orbit-electron: Run index.js in 'debug' mode
2016-12-07T17:48:09.924Z [DEBUG] orbit-electron: Received 'disconnected' event from renderer process
2016-12-07T17:48:23.466Z [DEBUG] orbit-electron: Received 'ipfs-daemon-start' event from renderer process
2016-12-07T17:48:23.470Z [DEBUG] ipfs-daemon: Initializing IPFS daemon
2016-12-07T17:48:23.470Z [DEBUG] ipfs-daemon: Using IPFS repo at '/home/rsynnest/.config/orbit'
2016-12-07T17:48:24.065Z [DEBUG] ipfs-daemon: Starting IPFS daemon
Inconsistency detected by ld.so: dl-close.c: 762: _dl_close: Assertion `map->l_init_called' failed!

npm ERR! Linux 3.16.0-4-amd64
npm ERR! argv "/home/rsynnest/.nvm/versions/node/v7.2.1/bin/node" "/home/rsynnest/.nvm/versions/node/v7.2.1/bin/npm" "run" "electron"
npm ERR! node v7.2.1
npm ERR! npm  v3.10.10
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR<EMAIL_ADDRESS>electron: `LOG=debug IPFS_FD_MAX=4096 $(npm bin)/electron .`
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>electron script 'LOG=debug IPFS_FD_MAX=4096 $(npm bin)/electron .'.
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 orbit package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     LOG=debug IPFS_FD_MAX=4096 $(npm bin)/electron .
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs orbit
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls orbit
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /home/rsynnest/src/orbit/npm-debug.log

Thank you @rsynnest, this helps a lot! :)
That said, I have no idea what this is about. Seems like it happens when starting the IPFS daemon. I see you're using node 7, could you give it a try with 6 and see if it occurs with that too?

Inconsistency detected by ld.so: dl-close.c: 762: _dl_close: Assertion `map->l_init_called' failed!

@whyrusleeping does that tell you anything? @dignifiedquire could this be related to compiling crypto on Linux?

@haadcode I tried node 6 before since that's what's explicitly listed in the README. Both node 6.0.0 and node 6.9.2 give the exact same errors as pasted above. I'm also able to reproduce this on another machine that is also running Debian.

ok. thanks for trying that. will need to investigate.

Small update:
I am able to install and run Orbit on Arch Linux. I installed everything using the exact same methods (installed go-ipfs from source). Here are some version numbers for various tools that might affect build:
Arch
go 1.7.4
gcc 6.2.1
glibc 2.24
ipfs 0.4.5-pre1
Debian
go 1.7.4
gcc 4.9.2
glibc 2.19
ipfs v0.4.5-dev
Regarding the ipfs version, I'm unsure if this is just a different name for the same version or if there is some minor version difference even though I installed from the same source. Even if I install using ipfs-update install v0.4.5-pre1 on Debian, the resulting ipfs version is still listed as v0.4.5-dev.

Ok, so I installed gcc-6 on Debian Jessie using the Debian Stretch repositories, and then reinstalled Orbit (a simple npm install). Orbit now runs without erroring out. I'm not sure if the rebuild is necessary. But either way it seems users will need a minimum (and non-standard) gcc as part of the Orbit build process. I haven't dived too far into the npm dependency rabbit hole, but my best guess is the ipfs-daemon package is the one that needs gcc since that appears to be what was calling runtime libraries and failing when built using gcc 4.9.
Newer gcc versions will be standard on most modern distros soon, and Orbit/IPFS are ahead of the curve so shooting for future release makes sense.
Standard gcc versions listed below.
Debian Jessie: gcc 4.9
RHEL7: gcc 4.8
Ubuntu 16.04 LTS: gcc 5.3+
Debian Stretch: gcc 6.2.1
OSX (listed because it seems lots of people use it): Uses Clang not gcc. Unsure of the Clang equivalent to gcc 6.
Steps to reproduce: try installing orbit on Debian Jessie (which comes with gcc 4.9.2 by default)
Fix: Install gcc-6 (lower version may work, I suspect gcc 5.3+ will work but haven't tested)
Recommended action: add a minimum gcc version dependency to documentation ?

Thank you @rsynnest for the excellent work on figuring this out! We should absolutely add it to the README. Would you like to PR it?
I suspect this is related to ipfs that ipfs-daemon pulls in, and most likely the new crypto and its build process. @dignifiedquire @diasdavid  we should try to reproduce this with js-ipfs or js-ipfs-api and see if it's the same result, and if so, we should make the same notes in the READMEs regarding the required gcc version.

This was fixed by adding the gcc versions to the readme in orbit-web: https://github.com/orbitdb/orbit-electron/pull/2.


Fix array pattern assignements

See issue #17 or the new test for examples of failures with the current master.

@guimier , please look my refactoring at #19
I write new simplest code, and this problem fixed without hardcode

Fixed at version 1.1.0 by #19
Your test cherry-picked

@gvozd Many thanks!


Labels for non-RTE input fields are disappearing briefly

Expected behaviour

Labels should not disappear when clicking on an input field

Actual behaviour

Labels for non-RTE input fields are disappearing briefly

Steps to reproduce the behaviour

Create new Page
Add Text answer
Label appears after a few seconds
Navigate to Section editor
Navigate back to Page
Click on Text answer input
Label disappears briefly

Screenshot

Not an issue.  Grammarly chrome extension was causing this.


Mysterious problem with MacAir broadwell.

Somehow after a long sleep, the client sends a discover, we send a reply, but the client does not see the reply. This was observed with charrua-mirage, it might not occur in charrua-unix.

The dhcp server is over a wireless connection, it used to be at address x.x.x.1, with mirage I use a vm on x.x.x.5.
OS X does dirty tricks to figure out if it is in "the same network" when it wakes, this is done by doing unicast reverse arps to the dhcp server address.
I believe somehow, this address is saved with the wireless ssid, so OS X remembers "ssid dhcp server is at IP X with MAC M".
Now for some reason, only this macair laptop triggers the bug, my macbook pro works just fine.
I'll try forgetting the network on the laptop, if not changing the ssid to see if OS X stops remembering the old address. Can't do now as the laptop is not mine, and she already put up with the dhcp bugs :)

This happened with a Wii U machine as well, I believe it's something to do with my bridge/iptables configuration in xen, linux sucks beyond repairs, it could be some funky behaviour with arptables, which is now disabled.

It seems a switch in the path got its configuration back to factory defaults (no idea how). LACP got disabled and bond0 on linux didn't work properly, it seems some arps were dropped, anyhow, after fixing the LACP config in the switch everything works as expected.


Version added to MANIFEST.MF

I've added the library version to the MANIFEST.MF file so that StdoutLogger.class.getPackage().getImplementationVersion(); can be used in the initialization logging.

Since this happens at build time, I couldn't think of a good way to unit test it.


Convert style1 class tables to Patternfly #1

Issue: #3139

Old:

New:

@dclarizio please review


Add Libretro core manager module

The basic idea is to let workers manage their core list instead of keeping each os/arch core library combination (nix, osx, win, arm) in the repo, cluttering the source.
A proposed solution:

[ ] add configuration params to workers which will describe a list of supported Libretro cores;
[ ] add manager module to workers that allow downloading and persistence of cores according to the config and runtime OS/ARCH info;
(optionally) add the ability for cascade cores update from the coordinator;
(optionally) create a separate mirror repository for keeping a selected list of cores from the official Libretro repo;
[ ] remove Libretro cores from the repository.

TBD.

oh it's really nice. Where will we download the core, is it from nightly build?

@giongto35, yes, nightly builds, as far as I know, it's the only place with Libretro cores. As a safety measure (if it will be down), I'll consider making a partial mirror of their nightly repo which will be auto-generated and updated with Github CI (Actions), maybe.
(I really want to implement a p2p mesh from the workers allowing them to download cores from each other, but it's, probably, hard to do (: )


Add parallel bpf recording e2e test

What type of PR is this?
/kind cleanup
What this PR does / why we need it:
This test ensures that parallel recording works as intended.
Which issue(s) this PR fixes:

None
Does this PR have test?
Yes

Special notes for your reviewer:
None
Does this PR introduce a user-facing change?

None

/retest

/retest

/test all

@saschagrunert mind rebasing this so the GH actions run again?
otherwise lgtm

@saschagrunert mind rebasing this so the GH actions run again?

Sure, gave it a rebase.

/lgtm


Add playsInline and muted to video background elements

What changed? Why?
Notes to reviewers
How has it been tested?

🟡 Heimdall Review Status

Requirement
Status
More Info

Reviews

🟡
0/1

Denominator calculation

Show calculation

1 if user is bot
0

1 if user is external
0

From .codeflow.yml

1

Additional review requirements

Show calculation

Max
0

0

From CODEOWNERS

0

Global minimum
0

Max

1

1

1 if commit is unverified
0

Sum
1


multicoreSupport = true not found

when I use the option "multicoreSupport = true" at @EnableSolrRepository I get the following error:
The attribute multicoreSupport is undefined for the annotation type EnableSolrRepositories
is there a workaround to fix this?

Hi @landoephan ,
Note that in our module we don't use the latest version of spring-data-solr.
multicoreSupport has been removed in the more recent releases.
Please see this StackOverflow thread - https://stackoverflow.com/questions/52123135/spring-data-solr-multi-core-support
Hope that helps.


Switching from skill calculator screen to xp rate screen is very intensive and laggy

Replicate: do some calculations in the skill calculator, and then return to the xp rate screen (ideally while you're doing something that gives xp). The game will massively lag (likely depending on your hardware)

I'll fix this

@deathbeam this can be closed.


Typo in Tutorial documentation

Awesome project! I believe there is a small typo with "shows" here: https://github.com/lupoglaz/GodotGymAI/blob/f55e245dbb344c2febefc7a9787b8bedc11e4c36/docs/tutorial.html#L132
Cheers!

Thank you, corrected with 84aec4927d9289803f12c447bb2ba2361f1261f2


Offset and RETRY -- v0.3.0

Coverage remained the same at 96.625% when pulling 462904b7f64a31b439efb7f16596a8bf93910089 on offset into be546714b4797800186e1f6ef0e7c2a18d34a3ed on master.


Stacktrace doesn't show exact line number

I have the following error and it doesn't show the exact line number unlike what it's supposed to.
I had an existing serverless app which I migrated towards this nodejs-starter a few minutes ago and trying it out.
SyntaxError: Unexpected token u in JSON at position 0
    at Object.parse (native)
    at _callee$ (/Users/vadorequest/dev/student-loan-simulator-serverless/aws/simulator-feedback/.webpack/service/feedback.js:111:25)
    at tryCatch (/Users/vadorequest/dev/student-loan-simulator-serverless/aws/simulator-feedback/node_modules/regenerator-runtime/runtime.js:62:40)
    at GeneratorFunctionPrototype.invoke [as _invoke] (/Users/vadorequest/dev/student-loan-simulator-serverless/aws/simulator-feedback/node_modules/regenerator-runtime/runtime.js:296:22)
    at GeneratorFunctionPrototype.prototype.(anonymous function) [as next] (/Users/vadorequest/dev/student-loan-simulator-serverless/aws/simulator-feedback/node_modules/regenerator-runtime/runtime.js:114:21)
    at step (/Users/vadorequest/dev/student-loan-simulator-serverless/aws/simulator-feedback/node_modules/babel-runtime/helpers/asyncToGenerator.js:17:30)
    at /Users/vadorequest/dev/student-loan-simulator-serverless/aws/simulator-feedback/node_modules/babel-runtime/helpers/asyncToGenerator.js:35:14
    at Promise.F (/Users/vadorequest/dev/student-loan-simulator-serverless/aws/simulator-feedback/node_modules/core-js/library/modules/_export.js:35:28)
    at /Users/vadorequest/dev/student-loan-simulator-serverless/aws/simulator-feedback/node_modules/babel-runtime/helpers/asyncToGenerator.js:14:12
    at create (/Users/vadorequest/dev/student-loan-simulator-serverless/aws/simulator-feedback/.webpack/service/feedback.js:143:17)
    at AwsInvokeLocal.invokeLocalNodeJs (/Users/vadorequest/.nvm/versions/node/v6.10.3/lib/node_modules/serverless/lib/plugins/aws/invokeLocal/index.js:338:12)
    at AwsInvokeLocal.invokeLocal (/Users/vadorequest/.nvm/versions/node/v6.10.3/lib/node_modules/serverless/lib/plugins/aws/invokeLocal/index.js:125:19)
    at AwsInvokeLocal.tryCatcher (/Users/vadorequest/.nvm/versions/node/v6.10.3/lib/node_modules/serverless/node_modules/bluebird/js/release/util.js:16:23)
    at Promise._settlePromiseFromHandler (/Users/vadorequest/.nvm/versions/node/v6.10.3/lib/node_modules/serverless/node_modules/bluebird/js/release/promise.js:512:31)
    at Promise._settlePromise (/Users/vadorequest/.nvm/versions/node/v6.10.3/lib/node_modules/serverless/node_modules/bluebird/js/release/promise.js:569:18)
    at Promise._settlePromise0 (/Users/vadorequest/.nvm/versions/node/v6.10.3/lib/node_modules/serverless/node_modules/bluebird/js/release/promise.js:614:10)
    at Promise._settlePromises (/Users/vadorequest/.nvm/versions/node/v6.10.3/lib/node_modules/serverless/node_modules/bluebird/js/release/promise.js:693:18)
    at Async._drainQueue (/Users/vadorequest/.nvm/versions/node/v6.10.3/lib/node_modules/serverless/node_modules/bluebird/js/release/async.js:133:16)
    at Async._drainQueues (/Users/vadorequest/.nvm/versions/node/v6.10.3/lib/node_modules/serverless/node_modules/bluebird/js/release/async.js:143:10)
    at Immediate.Async.drainQueues (/Users/vadorequest/.nvm/versions/node/v6.10.3/lib/node_modules/serverless/node_modules/bluebird/js/release/async.js:17:14)
    at runCallback (timers.js:672:20)
    at tryOnImmediate (timers.js:645:5)
    at processImmediate [as _immediateCallback] (timers.js:617:5)

package.json
{
  "name": "aws-nodejs-typescript",
  "version": "1.0.0",
  "description": "Serverless webpack example using Typescript",
  "main": "handler.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "devDependencies": {
    "babel-core": "6.26.0",
    "babel-loader": "7.1.2",
    "babel-plugin-source-map-support": "1.0.0",
    "babel-plugin-transform-runtime": "6.23.0",
    "babel-preset-env": "1.6.1",
    "babel-preset-stage-3": "6.24.1",
    "serverless-webpack": "4.3.0",
    "webpack": "3.11.0",
    "webpack-node-externals": "1.6.0"
  },
  "author": "The serverless webpack authors (https://github.com/elastic-coders/serverless-webpack)",
  "license": "MIT",
  "dependencies": {
    "aws-sdk": "2.194.0",
    "babel-runtime": "6.26.0",
    "jest": "22.3.0",
    "moment": "2.20.1",
    "uuid": "3.2.1"
  }
}

webpack.config.js
const slsw = require("serverless-webpack");
const nodeExternals = require("webpack-node-externals");

module.exports = {
  entry: slsw.lib.entries,
  target: "node",
  // Since 'aws-sdk' is not compatible with webpack,
  // we exclude all node dependencies
  externals: [nodeExternals()],
  // Run babel on all .js files and skip those in node_modules
  module: {
    rules: [
      {
        test: /\.js$/,
        loader: "babel-loader",
        include: __dirname,
        exclude: /node_modules/
      }
    ]
  }
};

.babelrc
{
  "plugins": ["transform-runtime"],
  "presets": ["env", "stage-3"]
}

AM I misunderstanding something or is there something wrong with my setup?

@Vadorequest Hmm your .babelrc and webpack.config.js are different form the ones in the repo. https://github.com/AnomalyInnovations/serverless-nodejs-starter/blob/master/webpack.config.js#L8 & https://github.com/AnomalyInnovations/serverless-nodejs-starter/blob/master/.babelrc#L2

Indeed... How did I miss that -_-
Thanks!


Trim fat of the fonts

Make sure that the font we settle with is structured across the boards ex: Headers, paragraphs, spans etc


Wrong SMILES form non-standard Inchi

Google Colab
conda-forge install
version 2020.03.5
m = Chem.MolFromInchi('InChI=1/C2H5NO2/c3-1-2(4)5/h1H2,3H3')
print(Chem.MolToSmiles(m))
yields [NH3+]C[C+]([O-])[O-] instead of [NH3+]CC(=O)[O-]
Same for this zwitterion: InChI=1/C6H5NO2/c8-6(9)5-2-1-3-7-4-5/h1-4,7H

Hi @jhjensen2, that's the tautomer that's encoded in the InChI.


A question about modify ElastoDyn code as bend-twist coupling

Hello all,
I am currently modifying ElastoDyn code to achieve calculating bend-twist couping blade , but I have run into a troubling problem.
In the original code subroutine coeff, the blade twisted shape function is calculated as:
p%TwsitedSF(K,1,1,J,2) = Shape*CThetaS(K,J)
but in the bend-twist couping code , I need to change this twisted shape function as a time variable , such as:
p%TwsitedSF(K,1,1,J,2) = Shape*cos(ThetaS(K,J)+Bladetwistangle)
but I cannot determine the variable type of the bladetwistangle in this subroutine , and I do not know how to change the twisted shape function as a time variable , because subroutine coeff is called in subroutine ED_Init , which is called just at the start of the simulation , this bothers me a lot. Can someone help me solve the problem ? Thanks kindly.
Best regards,
AsIlll123

Dear @AsIlll223,
As you noted, ElastoDyn SUBROUTINE Coeff() is set up to define time-independent parameters rather than dynamics that are solved at every time step.
Regarding adding a blade-torsion degrees of freedom to ElastoDyn, see the following related discussion on our forum: https://forums.nrel.gov/t/coupled-blade-modes-in-fast/314/39?u=jason.jonkman.
Best regards,

Dear @jjonkman
Thank you for your advice. I have previously modified the ElastoDyn code with reference to the artical you mentioned in the forum, ,including SUBROUTINE Coeff() ，SUBROUTINE FillAugMat（），etc. But I have no idea about how to modify SUBROUTINE Coeff() to a time-dependent subroutine that are updated at every time step.
Could you give me some advice? Thanks kindly.
Best regards,

Dear @AsIlll223,
I would not recommend modifying ElastoDyn SUBROUTINE Coeff() to be called every time step.  Rather, I would suggest modifying SUBROUTINE Coeff() only to define any new time-independent parameters you may need.  New dynamics should be implemented in SUBROUTINE ED_CalcContStateDeriv() or one of the routines called by that routine.
I can't really provide more guidance without more understanding of how you intend to modify ElastoDyn.  As noted on the forum topic  I linked, adding a blade-torsion degree of freedom to ElastoDyn would be quite challenging.
Before changing any source code, I would recommend developing an implementation plan outlining what you intend to change.
Best regards,

Dear @jjonkman
Thank you for your advice. I have solved the problem by writing a new subroutine to calculate these time variable. Then I make it called in the SUBROUTINE ED_CalcContStateDeriv() ，and it works well.
Best regards,


Display cookies based on the filter i.e. regex(say *.github.com)  - Enhanced the domain filter

A filter has been applied to domain field to match all the domain names provided in the  field control along with their respective cookies. An additional column can be found in the cookies displayed table header "DOMAIN". Also increased the length of the table cell to 20 & 25 for better readability. These changes have been made without touching the other operations.
See the below screenshot:

#hacktoberfest #goodfirstissue

@bhargava-raju Thank you for the PR! You may look into a few more good first issues here which are up for grabs!


"Terminal middleware" enhancements

Apologies for the length of these remarks :point_down:, but there be 🐉 here.
Addresses #10987
@shapeh and I deliberated a bit further: Turns out that we aren't covering "terminal middleware" very well. The last PR didn't go far enough.
"Terminal middleware" only appears in the Built-in middleware table of the Middleware topic and assumes that the reader will define it correctly.

I've elaborated on it in the Middleware topic ... both early where "short-circuiting" is described and later where it's used in the table.
The Response Caching topic now has a spot that we can link directly for terminal middleware (and then links to the whole topic as 'for more info, see'). I link to the table because the caching topic is saying that 'a terminal middleware' must not process the request first and the table indicates which middlewares can act as a terminal middleware. Since that condition of caching now links to both the table and the topic as a whole, I think we're covered.
The paragraph at Line 31 of the Middleware topic is a bit disorganized. I update it here so that the concepts pertaining to short-circuiting/terminal middleware are in their own paragraph. Also ...
:dragon: I move the paragraph on terminal middleware down in the section because I'd like to make a point about earlier middleware that still processes its post-next.Invoke code after the terminal middleware runs. The only way to do that is to move this paragraph down below where next is described.
:dragon: The current text implies (via the HasStarted check remark) that completely terminating request processing (i.e., including any post-next.Invoke code in prior middleware) isn't possible. Just making sure the doc is correct on that point. We could add a HasStarted example to the warning where a prior middleware checks before it processes any post-next.Invoke code. Let me know if you'd like to see that drafted in here.

Thanks @shapeh! :rocket:

Wait to see what Chris thinks, then we can go forward with it. Watch out for little 🐉 here.

ok ...

[Error] An exception occurred during the build process. Please check the raw log and retry building your content again. If the issue persists, please open a ticket in http://SiteHelp and include the URL of publishing report as well as below information: One or more errors occurred.

Ty @Tratcher ......
Sir Chris the 🐉 Slayer
If you'll be around for the Summit, the :beers: are on me .... er .... MS. lol See you there.


Filtering by tags results in empty list

I'm observing an unexpected issue while reading data from InfluxDB
client = InfluxDBClient('localhost', 8086, 'root', 'root', 'influx_demo')

result = client.query("SELECT * FROM energy WHERE time >= '2015-01-01T00:00:00Z' AND time <= '2015-01-01T00:30:00Z'")

series = list(result.get_points(tags={'source': 'SBERA0'}))

series variable is an empty list and it should not; the same query using CLI returns the following points where [account location  source] are "Tags" and value is "Field"
> SELECT * FROM energy WHERE time >= '2015-01-01T00:00:00Z' AND time <= '2015-01-01T00:30:00Z'
name: energy
time                account location source value
----                ------- -------- ------ -----
1420070400000000000 BER     A        SBERA0 1
1420070400000000000 PAR     A        SPARA0 3
1420070400000000000 LOS     A        SLOSA0 6
1420070400000000000 LON     A        SLONA0 4
1420070400000000000 MIL     A        SMILA0 4
1420070700000000000 LON     A        SLONA0 6
1420070700000000000 MIL     A        SMILA0 8
[...]

I can make it work by using GROUP BY clause
result = client.query("SELECT * FROM energy WHERE time >= '2015-01-01T00:00:00Z' AND time <= '2015-01-01T00:30:00Z' GROUP BY source")

series = list(result.get_points(tags={'source': 'SBERA0'}))

But at this point I can only use the tag you have used in GROUP BY tags={'source': }
and using  multiple tags  tags={'source': , 'location': } is not returning appropriate values.

closing as a dupe of #251 and #441


Delete manifests/j/JanDeDobbeleer/OhMyPosh/7.46.2 directory

[ ] Have you signed the Contributor License Agreement?
[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.2 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

@wingetbot run


Project crashes after not having opened it for some time

Tested versions
Happened in 4.2, still happens after upgrading 4.3.
System information
Originally i was using windows 10, the issue now appears when using windows 11.
Issue description
After not having opened my project in some time, it now crashes on startup. no log is produced and the backtrace appears useless.
after running it with console.txt
Steps to reproduce
Open the provided project in godot 4.3
Minimal reproduction project (MRP)
cloud-attempt-1.zip
the entire project is very simple and has barely anything, it was just a shader test. and i wouldnt know how to make the project any smaller while still having the issue

Reproduced this in 4.3 release, but tested it on the latest commit in 4.3 branch and seemingly it has been fixed.

Closing then as already fixed by #95503, and that fix was already cherry-picked for 4.3.1. That version just needs to be released one day 🙃


Prep for Node 18 release, Node 12 deprecation

Latest information seems to indicate 4/19 for the release date of Node 18 and thus deprecation of Node 12.
Given the increase of macOS machines with Apple Silicon hardware, this will also switch the default OS from "buster" (Debian 10) to "bullseye" (Debian 11) to better enable arm64 support.
We can validate and merge once the upstream Node 18 image has been released.

Node.js 18 is now available and I’m looking forward seeing this merged! :)

@joshspicer looks like this is ready! Are you alright handling testing and merge?

discovered an issue with our node-debian.sh script in git 2.35.2, trying to fix it with https://github.com/microsoft/vscode-dev-containers/commit/6bb7605d0679910b63db63eb93e876febcf0bd8d


Error boundaries

💥 Proposal
There's no getDerivedStateFromError or componentDidCatch in Docusaurus v2.
Errors might not happen very often, particularly most of them would simple make the build fail.
But it might still be useful to add a default global error boundary in case the code of the user produces a runtime error. Some people might introduce buggy code in pages that might crash at runtime.

I'll take a look into this.


$(layers-active) is not resolved in VS Code Windows Task Bar

When using GitHub.remotehub-insiders to open a repository, this shows up in VS Code's task bar entry on Windows:

@joyceerhl that is an interesting question which we actually have to ask @bpasero or @sbatten. They are correctly rendered in this recent list

@dbaeumer the only location where this kind of icon is supported is quick pick and I think status bar entries only to enable extensions to e.g. present actions with icons in the picker.
No other location, specifically not menus or the jumplist support icons, so we would need to filter them out before showing. But if valuable information is carried in the icons, I wonder if this kind of information should be presented differently then and not just stripped from the label.

Due to the fact that index switching is hot I removed the icons for now. For pull requests I added PR to the PR id to make it more distinguishable from commits.


Adds the "English readme" link to all README.* files

Type of changes

[ ] Bug fix
[ ] New feature
[ ] Documentation / docstrings
[ ] Tests
[x] Other

Checklist

[ ] I've run the latest black with default args on new code.
[ ] I've updated CHANGELOG.md and CONTRIBUTORS.md where appropriate.
[ ] I've added tests for new code.
[x] I accept that @willmcgugan may be pedantic in the code review.

Description
I've been working on a new translation and found it unnatural not having a link to go back to the English version of the readme, as it was a quick change I decided to propose instead of asking.

Good idea. Would you mind fixing those merge conflicts?

Hi Will, it's done. Also, I took the freedom to reformat the very long line of READMEs translation into multiple lines on the .md files. The content looks exactly the same, it is just way easier to maintain IMHO.
Please let me know If you don't think it is a good idea and I can revert. Cheers

All good. Thanks!


Use pip to install packages

:notebook_with_decorative_cover: Description
This fixes the Docker build.
:memo: Checklist

[x] All user-facing changes have changelog entries.
[x] The changes are reflected on docs.tenzir.com/threatbus, if necessary.
[x] The PR description contains instructions for the reviewer, if necessary.

:dart: Review Instructions
cp config.yaml.example config.yaml
docker build . -t tb
docker run --net=host -ti tb

It will behave like a normal process, can be terminated with ctrl+c and updates logs to the terminal when you send around messages. The --net=host makes it work with locally installed software like misp, cif, or vast.

I tried to follow the review instructions, but ran into the following error in the final step:
$ sudo docker run --net=host -ti tb
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/dist-packages/confuse/yaml_util.py", line 85, in load_yaml
    with open(filename, 'rb') as f:
FileNotFoundError: [Errno 2] No such file or directory: '/opt/tenzir/threatbus/config.yaml'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/bin/threatbus", line 8, in <module>
    sys.exit(main())
  File "/usr/local/lib/python3.7/dist-packages/threatbus/threatbus.py", line 200, in main
    config.set_file(args.config)
  File "/usr/local/lib/python3.7/dist-packages/confuse/core.py", line 637, in set_file
    self.set(YamlSource(filename, loader=self.loader))
  File "/usr/local/lib/python3.7/dist-packages/confuse/sources.py", line 58, in __init__
    self.load()
  File "/usr/local/lib/python3.7/dist-packages/confuse/sources.py", line 67, in load
    loader=self.loader) or {}
  File "/usr/local/lib/python3.7/dist-packages/confuse/yaml_util.py", line 88, in load_yaml
    raise ConfigReadError(filename, exc)
confuse.exceptions.ConfigReadError: file /opt/tenzir/threatbus/config.yaml could not be read: [Errno 2] No such file or directory: '/opt/tenzir/threatbus/config.yaml'

@lava I updated the installation instructions. The config file was missing. I also used this branch to pin a dependency version that has a bug in latest (pymisp). Could you please pull and retry?

Yes, correct. The config activates almost all plugins and hence tries to connect to a bunch of systems. The error messages tell us that these configured endpoints don't exist. The important bit is that Threat Bus and plugins come up correctly.


whenNextSequential + quiescence

Andreas has a case where the pool does not reach quiescence. (Works well with with whenNext.)

Fixed


Update to official solcast-api-python-sdk repo

Hi Chris,
Hope you're well! We wanted to let you know that there's now an official solcast-api-python-sdk that Harry and the rest of the Solcast team have released and Darren has transferred ownership of https://pypi.org/project/solcast/
This means that pip install solcast will actually grab the official package now.
If you're still maintaining this, would you be able redirect this repo or to add a note on the ReadMe pointing to solcast-api-python-sdk so that users don't get confused? You're also welcome to fork the Solcast repo so you can use the new features and endpoints if you're interested.
Thanks, Alex (and James)

Hey Alex,
No problem at all, I will add a note to the README. Don't think it's possible for me to set up a redirect unfortunately (but if you know how to do it I'm happy to).

Thanks @cjtapper - a note at the top of the README is fine.
In terms of redirect, the only thing that might work is if you re-make the repo under the same name (cjtapper/solcast-py) as a fork of solcast-api-python-sdk so there's a more direct link?
Much appreciated!


Ask for help

If you encountered the same condition when I tap "backspace" key in one kind of input aid software to input something for a TextBox etc, the letter was deleted while a letter in the TextBox also disappeared! Do you know how to fix it?

Sorry, I could not represent same problems.
If you can take screenshots or photos step by step, take them between before and after tapping backspace. And attempt to report it to AvaloniaUI.
I find same probrem in the Avalonia issue, but I couldn't find progress to resolve it.

Sorry, I could not represent same problems.
If you can take screenshots or photos step by step, take them between before and after tapping backspace. And attempt to report it to AvaloniaUI.
I find same probrem in the Avalonia issue, but I couldn't find progress to resolve it.

anyway, thank you very much


fix: create correct url when using ipv6

Currently when using IPv6 I get the following errors:
2023-08-31 00:59:25.359 ERROR (MainThread) [custom_components.google_home] Request from Cocina device error: https://2a02:9140:4d80:xxxx:2880:fef1:8065:ad8d:8443/setup/assistant/alarms
2023-08-31 00:59:25.361 ERROR (MainThread) [custom_components.google_home] Request from Cocina device error: https://2a02:9140:4d80:xxxx:2880:fef1:8065:ad8d:8443/setup/assistant/alarms/volume
2023-08-31 00:59:25.364 ERROR (MainThread) [custom_components.google_home] Request from Cocina device error: https://2a02:9140:4d80:xxxx:2880:fef1:8065:ad8d:8443/setup/assistant/notifications
2023-08-31 00:59:25.368 ERROR (MainThread) [custom_components.google_home] Request from Dormitorio device error: https://2a02:9140:4d80:xxxx:7ed9:5cff:fe1b:dcef:8443/setup/assistant/alarms
2023-08-31 00:59:25.371 ERROR (MainThread) [custom_components.google_home] Request from Dormitorio device error: https://2a02:9140:4d80:xxxx:7ed9:5cff:fe1b:dcef:8443/setup/assistant/alarms/volume
2023-08-31 00:59:25.374 ERROR (MainThread) [custom_components.google_home] Request from Dormitorio device error: https://2a02:9140:4d80:xxxx:7ed9:5cff:fe1b:dcef:8443/setup/assistant/notifications
2023-08-31 00:59:25.376 ERROR (MainThread) [custom_components.google_home] Request from Salón device error: https://2a02:9140:4d80:xxxx:3944:b4e3:bed3:fce:8443/setup/assistant/alarms
2023-08-31 00:59:25.379 ERROR (MainThread) [custom_components.google_home] Request from Salón device error: https://2a02:9140:4d80:xxxx:3944:b4e3:bed3:fce:8443/setup/assistant/alarms/volume
2023-08-31 00:59:25.381 ERROR (MainThread) [custom_components.google_home] Request from Salón device error: https://2a02:9140:4d80:xxxx:3944:b4e3:bed3:fce:8443/setup/assistant/notifications

This is due to a malformed URL when using IPv6, as the IPv6 needs to be placed between [], for example https://[2a02:9140:4d80:xxxx:3944:b4e3:bed3:fce]:8443/setup/assistant/notifications.
This PR detects if the IP is IPv6 and adds them.

Please update warnings found by linters.

There is another warning about using isinstance instead of type.

Ok, I've ended up installing pre-commit it locally. I missed that one in the action log. That should be it. Sorry for the noise.

Hello, just a note.
This error does not appear only when IPv6 is used.
I have my home network completely on IPv4 with IPv6 disabled on my router and this error appears only on HA startup/reboot.
So I would like to know where the IPv6 adresses are coming from on Google devices.
Anyway it looks like this PR fixes my issue also so thank you very much @skgsergio
and I will keep monitoring this for few more days.

It seems zeroconf may return ipv6 addresses sometimes when discovering Google Home devices. I guess it should be possible to disable this in zeroconf or make this configurable from integration settings. If someone is interested in working on this, PR is welcome.


Model#fetch returns null not undefined

This is a couple months late, but at least there's a happy ending.
I've updated the documentation for Model#fetch to reflect that an unfetched model is a rejected promise that resolves to null instead of undefined. I've also added a test case that demonstrates this behavior.
fixes #860
Edit: I've updated my PR to include Collection#fetchOne documentation updates as well. I've also included a test for that case.

Love your work, @jadengore!

Thanks a bunch @rhys-vdw! Love being able to contribute to a project I use!


Reland "Add default selection style (#100719)"

Relands https://github.com/flutter/flutter/pull/100719
Internal test failed because the text selection theme in Theme widget does not override the default selection style correctly, The change is in the second commit.
Pre-launch Checklist

[ ] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[ ] I read the Tree Hygiene wiki page, which explains my responsibilities.
[ ] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[ ] I signed the CLA.
[ ] I listed at least one issue that this PR fixes in the description above.
[ ] I updated/added relevant documentation (doc comments with ///).
[ ] I added new tests to check the change I am making, or this PR is test-exempt.
[ ] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

Looks like a resync is needed here.

@HansMuller The tests are passing now.


⚠ Bofrost.at has degraded performance

In 8ae61fb, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1336 ms

Resolved: Bofrost.at performance has improved in 06e0355.


Fast forward util

added a utility to OpsTest to temporarily set "update-status-hook-interval" to a given value, and then set it back to whatever it was before (or another 'slow' value).
Note that I couldn't run the pytest-operator itests locally because of #77
So let's see if the CI here does a better job of that.
Solves #78

I don't see any trouble here.

could you fill in the docs here

@addyess done!


TypeError: Converting circular structure to JSON

Hi,
When I load jcs-auto-validate.js via HTML in a chrome for both version 1.18.13 and 1.18.14 the console prints out:
TypeError: Converting circular structure to JSON
at Object.stringify (native)
Is anyone else experiencing this? before I add some more detail.
I am referencing via maven webjar using wro4j for minification.
Thanks
Sanjay

Hi,
I don't think the library does an Object.stringify anywhere?
In either case I'd upgrade to the latest release (v1.18.16) and still if this is still an issue.  If it is could you do up a reproducing plunker and I'll get it fixed :-)

Its also happening with v1.18.16. 1.18.6 works fine. But reproducing it is inconsistent... grrr

What the stack trace when it happens?  Does it only happen when minified?

Any further information?

Closing as no further information provided.  Please feel free to re-open it a reproducing Plunker is provided

I am facing this issue. I just included 'jcs-autoValidate' in my angular module and refreshed the page.
Following is the stacktrace
TypeError: Converting circular structure to JSON
at Object.stringify (native)
at toJson (http://localhost:63342/Angular/js/angular.js:1234:15)
at http://localhost:63342/Angular/js/angular.js:19067:12
at fn (eval at  (http://localhost:63342/Angular/js/angular.js:13322:15), :4:156)
at regularInterceptedExpression (http://localhost:63342/Angular/js/angular.js:14402:21)
at Object.expressionInputWatch [as get] (http://localhost:63342/Angular/js/angular.js:14304:26)
at Scope.$digest (http://localhost:63342/Angular/js/angular.js:15818:40)
at Scope.$apply (http://localhost:63342/Angular/js/angular.js:16097:24)
at bootstrapApply (http://localhost:63342/Angular/js/angular.js:1660:15)
at Object.invoke (http://localhost:63342/Angular/js/angular.js:4478:17)
TypeError: Converting circular structure to JSON
at Object.stringify (native)
at toJson (http://localhost:63342/Angular/js/angular.js:1234:15)
at http://localhost:63342/Angular/js/angular.js:19067:12
at fn (eval at  (http://localhost:63342/Angular/js/angular.js:13322:15), :4:156)
at regularInterceptedExpression (http://localhost:63342/Angular/js/angular.js:14402:21)
at Object.expressionInputWatch [as get] (http://localhost:63342/Angular/js/angular.js:14304:26)
at Scope.$digest (http://localhost:63342/Angular/js/angular.js:15818:40)
at Scope.$apply (http://localhost:63342/Angular/js/angular.js:16097:24)
at http://localhost:63342/Angular/js/angular.js:17864:36
at completeOutstandingRequest (http://localhost:63342/Angular/js/angular.js:5507:10)

Could you do a reproducing Plunker?

Please find the attached project
On Thu, Oct 8, 2015 at 1:24 PM, Jon Samwell<EMAIL_ADDRESS>wrote:

Could you do a reproducing Plunker?
—
Reply to this email directly or view it on GitHub
https://github.com/jonsamwell/angular-auto-validate/issues/92#issuecomment-146448567
.

can be reproduced from
https://github.com/surendrand/angular-auto-validate-issue.git
On Thu, Oct 8, 2015 at 1:24 PM, Jon Samwell<EMAIL_ADDRESS>wrote:

Could you do a reproducing Plunker?
—
Reply to this email directly or view it on GitHub
https://github.com/jonsamwell/angular-auto-validate/issues/92#issuecomment-146448567
.

Fixed in v1.19.0


tag_recent_media not escaping non-ascii tags properly

This works great:
Instagram.tag_search 'håkan' # my name

=> [#<Hashie::Mash media_count=18254 name="håkan">, #<Hashie::Mash media_count=58890 name="håkanhellström">,...

This doesn't:

Instagram.tag_recent_media 'håkan'

URI::InvalidURIError: bad URI(is not URI?): tags/håkan/media/recent.json
	from /Users/hakan/.rbenv/versions/2.1.1/lib/ruby/2.1.0/uri/generic.rb:1203:in
'rescue in merge'
	from /Users/hakan/.rbenv/versions/2.1.1/lib/ruby/2.1.0/uri/generic.rb:1200:in 'merge'
	from /Users/hakan/.rbenv/versions/2.1.1/lib/ruby/gems/2.1.0/gems/faraday-0.9.0/lib/faraday/connection.rb:406:in 'build_exclusive_url'
	from /Users/hakan/.rbenv/versions/2.1.1/lib/ruby/gems/2.1.0/gems/faraday-0.9.0/lib/faraday/rack_builder.rb:191:in 'build_env'
	from /Users/hakan/.rbenv/versions/2.1.1/lib/ruby/gems/2.1.0/gems/faraday-0.9.0/lib/faraday/rack_builder.rb:139:in 'build_response'
	from /Users/hakan/.rbenv/versions/2.1.1/lib/ruby/gems/2.1.0/gems/faraday
...

The problem is that the å needs to be run through CGI.escape.
Possibly there other APIs which also need to be fixed?

Same issue here, foreign language characters causesbad URI errors

Same issue here
2015-04-17T11:19:40.354274+00:00 app[worker.1]: #München min_tag_id 0
2015-04-17T11:19:40.357403+00:00 app[worker.1]: /app/vendor/ruby-1.9.3/lib/ruby/1.9.1/uri/generic.rb:1202:in `rescue in merge': bad URI(is not URI?): tags/münchen/media/recent.json (URI::InvalidURIError)
2015-04-17T11:19:40.357406+00:00 app[worker.1]:         from /app/vendor/ruby-1.9.3/lib/ruby/1.9.1/uri/generic.rb:1199:in `merge'
2015-04-17T11:19:40.357412+00:00 app[worker.1]:         from /app/vendor/bundle/ruby/1.9.1/gems/faraday-0.8.9/lib/faraday/request.rb:94:in `to_env'
2015-04-17T11:19:40.357410+00:00 app[worker.1]:         from /app/vendor/bundle/ruby/1.9.1/gems/faraday-0.8.9/lib/faraday/connection.rb:303:in `build_exclusive_url'
2015-04-17T11:19:40.357416+00:00 app[worker.1]:         from /app/vendor/bundle/ruby/1.9.1/gems/faraday-0.8.9/lib/faraday/connection.rb:252:in `run_request'
2015-04-17T11:19:40.357419+00:00 app[worker.1]:         from /app/vendor/bundle/ruby/1.9.1/gems/faraday-0.8.9/lib/faraday/connection.rb:106:in `get'
2015-04-17T11:19:40.357423+00:00 app[worker.1]:         from /app/vendor/bundle/ruby/1.9.1/gems/instagram-1.1.3/lib/instagram/request.rb:31:in `request'
2015-04-17T11:19:40.357430+00:00 app[worker.1]:         from /app/vendor/bundle/ruby/1.9.1/gems/instagram-1.1.3/lib/instagram/client/tags.rb:37:in `tag_recent_media'
2015-04-17T11:19:40.357426+00:00 app[worker.1]:         from /app/vendor/bundle/ruby/1.9.1/gems/instagram-1.1.3/lib/instagram/request.rb:9:in `get'
...

just made some tests in the instagram api console, which works with the following
GET /v1/tags/m%C3%BCnchen/media/recent?access_token=
String has to be URL encoded.

The solution is: use URI.encode(tag) before passing the tag into the method

Thank you for reporting this issue and appreciate your patience. We've  notified the core team for an update on this issue. We're looking for a response within the next 30 days or the issue may be closed.


Kafka extract

Pull Request Test Coverage Report for Build 581645412

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

Totals

Change from base Build 581635943:
0.0%

Covered Lines:
1470

Relevant Lines:
5431

💛  - Coveralls


add config to allow debugger attach in sleep/stop mode

see  #56096

DBGMCU was
actually configured by CONFIG_USE_SEGGER_RTT but more as an side-effect.

This was actually made on purpose in #38561.

Yes, but not fully understood (I believe)

    and sometimes also
    one of the DBGMCU bit STOP/STANDBY/SLEEP is set

without the DBGMCU patch the debugger would hard-reset the target when attaching the RTTViewer and the user would always see reboots w/o understanding why ;) This patch should be more clear, you need to ability to attach the debugger in sleep/stop modes ;)

Yes, but not fully understood (I believe)

Indeed. But it was clear that this was required to have RTT working on some targets even w/o PM use cases.
With this patch, this won't work anymore. This has to be taken into account

and sometimes also one of the DBGMCU bit STOP/STANDBY/SLEEP is set
without the DBGMCU patch the debugger would hard-reset the target when attaching the RTTViewer and the user would always see reboots w/o understanding why ;)

Is that a specific RTT debugger behavior ?

This patch should be more clear, you need to ability to attach the debugger in sleep/stop modes ;)

Debugging in sleep more is another topic, see soc/arm/st_stm32/stm32**/power.cfiles in which this bit is enabled if CONFIG_DEBUG=y.
Btw, note that there is be a conflict with openocd behavior which sets this bit by default at flash. So it is set whatever f/w status when flashing. In this case bit is reset on power down (unplug/plug).
So I'm not opposed to make some changes, adding a specific flag might be a good idea, but the full picture should be taken into account. Your patch doesn't take into account points 1 and 3.

Yes, but not fully understood (I believe)

Indeed. But it was clear that this was required to have RTT working on some targets even w/o PM use cases. With this patch, this won't work anymore. This has to be taken into account (point 1)

This still works as it used to because USE_SEGGER_RT selects STM32_ENABLE_DEBUG_SLEEP_STOP (c.f. modules/segger/Kconfig)

and sometimes also one of the DBGMCU bit STOP/STANDBY/SLEEP is set
without the DBGMCU patch the debugger would hard-reset the target when attaching the RTTViewer and the user would always see reboots w/o understanding why ;)

Is that a specific RTT debugger behavior ?

No this affects all debug dongles and use-cases (e.g. west flash, west attach, ...) and especially west attach makes no sense when the target gets reset on debugger connection (which is the main reason for this PR).

This patch should be more clear, you need to ability to attach the debugger in sleep/stop modes ;)

Debugging in sleep more is another topic, see soc/arm/st_stm32/stm32**/power.cfiles in which this bit is enabled if CONFIG_DEBUG=y. Btw, note that there is be a conflict with openocd behavior which sets this bit by default at flash. So it is set whatever f/w status when flashing. In this case bit is reset on power down (unplug/plug). (point 3)

DEBUG also select STM32_ENABLE_DEBUG_SLEEP_STOP (c.f. soc/arm/st_stm32/Kconfig)

So I'm not opposed to make some changes, adding a specific flag might be a good idea, but the full picture should be taken into account. Your patch doesn't take into account points 1 and 3.

the existing code in soc/arm/st_stm32/stm32**/power.c is a good point though, the current state is:
9 out of 20 stm32* subdirectories take care of the DBGMCU, the others don't.

g0: also enables LL_APB1_GRP1_PERIPH_DBGMCU clock
g4: is covered by PR
l0: also enabled LL_APB2_GRP1_PERIPH_DBGMCU clock
l4:  is covered by PR
l5:  is covered by PR
u5:  is covered by PR
wb: is covered by PR
wl: is covered by PR
wba: is covered by PR

my proposal to enhance this PR: unify this in soc/arm/st_stm32/common/soc_config.c (ifdef'ed by CONFIG_STM32_ENABLE_DEBUG_SLEEP_STOP) and remove from soc/arm/st_stm32/stm32**/power.c
This would then fulfill your points 1 and 3
@erwango do you know if enabling the clock is also required in the F0 and C0 parts?
Your remarks regarding openocd, i've looked through the scripts and see what you mean.
The DBGMCU stuff done there however does not conflict with this PR in my opinion, reason: this PR assures that the firmware sets those flags in the DBGMCU on startup and this will allow a debugger attach to happen for those builds. The workflow here is to have the board run w/o debugger connection and attach to target when a certain error state occurred.
openocd's non-persistent configuration allow use-cases like west debug to work even with firmware not configuring DBGMCU. This is not sufficient for certain use-cases involving bootloaders (i.e. our firmware depends on some in-memory data structures pre-filled by the bootloader) where a west attach must not reset the target.

my proposal to enhance this PR: unify this in soc/arm/st_stm32/common/soc_config.c (ifdef'ed by CONFIG_STM32_ENABLE_DEBUG_SLEEP_STOP) and remove from soc/arm/st_stm32/stm32**/power.c
This would then fulfill your points 1 and 3

Fine with me.

9 out of 20 stm32* subdirectories take care of the DBGMCU, the others don't.

When power.c is not available, PM is not implemented on the series.

@erwango do you know if enabling the clock is also required in the F0 and C0 parts?

If the question is regarding RTT , I don't have the info sorry.

Your remarks regarding openocd, i've looked through the scripts and see what you mean.

Ok. I just wanted you to be aware.


Flatpak autorebuild

This is a set of changes that should get autorebuilds working correctly for Flatpaks. The idea here is not that a Flatpak needs to be rebuilt when the base image is rebuilt - they aren't layers on top of the base image - but rather that we might have a policy where all containers are expected to be rebuilt when a base image is updated, and by using that image as the Flatpak base image as well, Flatpaks will participate in the overall policy.
As part of this change it became apparent that putting the code to determine what labels and base image will be used for a Dockerfile-less Flatpak in api.py didn't make sense (it's not API related, and there was one check usage of the labels elsewhere), so that code is moved to repo_info.py, and tests are added so that testing of the code is centralized in test_repo_info.py.
Maintainers will complete the following section:

[x] Commit messages are descriptive enough
[ ] "Signed-off-by:" line is present in each commit
[ ] Code coverage from testing does not decrease and new code is covered
[ ] JSON/YAML configuration changes are updated in the relevant schema
[ ] Changes to metadata also update the documentation for the metadata
[ ] Pull request includes link to an osbs-docs PR for user documentation updates

Neither eade499 nor 4a38532 have "Signed-off-by:"

Rebased, added requested doc comment, fixed sign-offs. I'll hold off on any reorganization of label_utils.py or fixes for atomic-reactor until I get reaction to my plan above.

New version implements my plan of utils.py => utils/init.py, and should be compatible with existing atomic-reactor.

/packit build

/packit copr-build

Packit did rebuild the packages successfully, but no updates here so far.
https://copr.fedorainfracloud.org/coprs/packit/containerbuildsystem-osbs-client-947/builds/
Thanks Owen!
LGTM

Release notes

Flatpak builds support autorebuilds


Add E2E Tests for UDPRoute

Description:
Add E2E tests in https://github.com/envoyproxy/gateway/tree/main/test/e2e/tests to test UDPRoute

Should this be done in upstream ?

it might be faster to do it here and then move the exact test upstream

I can take a look :)

ping @cnvergence , just want to make sure you're still working around.

@zirain, yes, I will push my changes today

should we bring it to upstream when it's ready?

you can proposal it at anytime

xref: https://github.com/kubernetes-sigs/gateway-api/pull/2661


Fix minor issues

Use MAX_CLUSTERS_PER_AF_REGISTER" instead of magic number.
Forgot to start announce notification thread
Fix discovery related javadoc
Fix typos

Thanks.


[WIP] Datatx driver

See sciencemesh/sciencemesh#140
Datatx driver pkg setup.
note: Datatx interface methods' signatures still indefinite.

@redblom good progress!

This now implements rclone driver DoTransfer, GetTransferStatus.
There are also 2 cli commands available for testing this: rclone-do-transfer, rclone-get-transfer-status
For tests you'll need a running rclone server and an rconfig file with the remotes/users specified.
Transfer eg. a cli triggered transfer between two running reva instances:
$ ./cmd/reva/reva rclone-do-transfer -senderEndpoint http://rclone-reva:5572/ -srcEndpoint reva-1 -srcPath /test/1gb.txt -srcToken marie -destEndpoint reva-2 -destPath /myfiles/1gb1.txt -destToken marie

This will echo the rclone job id.
Notes:

src/destEndpoint - the remotes' names as specified in the config
the tokens are not used but required by the cli

Get status eg.:
$ ./cmd/reva/reva rclone-get-transfer-status -senderEndpoint http://rclone-reva:5572/ -transferID 68

This will echo the transfer status.

All 3 methods (DoTransfer, GetTransferStatus, CancelTransfer) implemented.

@ishank011 yeah I know, I'm working on those right now. These rclone clients are for driver testing purposes only, I don't expect them to be part of the final PR.

Added a few comments. I'm not sure I fully understand how the token situation works. In OCM we transfer a token when sharing a file which is used to access resources on the file owner's provider, not sure how that translates here and how it connects to that, since these will be enabled only once an OCM share has been created, right? (https://wiki.cs3mesh4eosc.eu/wps/4/task44stuff/apis)

With data transfer a special transfer OCM share request (which will be a to be defined special datatx OCM protocol type) is done towards the anticipated destination and at destination a token is created and returned so the token is available at source site for use when doing the actual transfers (transfers are instigated at the source site so it must have a valid token).
Actually this is not described in the notes in CreateTransfer method of grpc service datatx.go. I will do that; should make it clear.

Added a few comments. I'm not sure I fully understand how the token situation works. In OCM we transfer a token when sharing a file which is used to access resources on the file owner's provider, not sure how that translates here and how it connects to that, since these will be enabled only once an OCM share has been created, right? (https://wiki.cs3mesh4eosc.eu/wps/4/task44stuff/apis)

With data transfer a special transfer OCM share request (which will be a to be defined special datatx OCM protocol type) is done towards the anticipated destination and at destination a token is created and returned so the token is available at source site for use when doing the actual transfers (transfers are instigated at the source site so it must have a valid token).
Actually this is not described in the notes in CreateTransfer method of grpc service datatx.go. I will do that; should make it clear.

@redblom please take a look at https://codimd.web.cern.ch/CsSOm-lxS52nV3hWjbglaw. I'd recommend merging this PR as is and starting with the OCM integration after that. I'd like to help with the coding part in that.

@redblom please take a look at https://codimd.web.cern.ch/CsSOm-lxS52nV3hWjbglaw. I'd recommend merging this PR as is and starting with the OCM integration after that. I'd like to help with the coding part in that.

This is not ideal though. IMO, the transfer should be initiated when the recipient accepts the share through the ocm-update-received-share method, since we create references then only as well. So the problem of transferring the token from the recipient to the original user won't arise in the first place. That would be a much better design in my opinion.

This is not ideal though. IMO, the transfer should be initiated when the recipient accepts the share through the ocm-update-received-share method, since we create references then only as well. So the problem of transferring the token from the recipient to the original user won't arise in the first place. That would be a much better design in my opinion.

@ishank011 I support Ishank's comment, that is the goal of having end to end transfers driven by OCM.

@ishank011 I support Ishank's comment, that is the goal of having end to end transfers driven by OCM.

@labkode @ishank011 : To me this looks like how it has been discussed before; and as drawn in the datatx diagram.
@labkode was however correct when showing the video, CreateTransfer returns the wrong state. It must return one of transfer_awaiting_acceptance or transfer_accepted). In this case transfer_accepted should be returned since in the current implementation the transfer is always accepted (there's no OCM accept share flow implemented yet).
Once the OCM share accept flow is implemented transfer_awaiting_acceptance may be returned (same as pending in file sharing).

@labkode @ishank011 : To me this looks like how it has been discussed before; and as drawn in the datatx diagram.
@labkode was however correct when showing the video, CreateTransfer returns the wrong state. It must return one of transfer_awaiting_acceptance or transfer_accepted). In this case transfer_accepted should be returned since in the current implementation the transfer is always accepted (there's no OCM accept share flow implemented yet).
Once the OCM share accept flow is implemented transfer_awaiting_acceptance may be returned (same as pending in file sharing).

When the (datatx) share is received in the ocmd we know it's a datatx share through the protocol options parameter. However we currently cannot persist it as such. Share objects have no tx specifics. So the receiver does not know it's a datatx share either. How do we go about that?

Why can't we persist it? On the recipient side, the request would look like as described in https://wiki.cs3mesh4eosc.eu/wps/4/task44stuff/apis, so it would know it's a datatx share.

The datatx transfer ends up as a 'marshalled' Share object in the received_shares section of the shares file at the receiver's end. What options do I have to define there that it is a datatx share; so that the receiver (and the system) when accepting this share know that after reading this share from the shares file that this is a datatx share and the transfer can commence?
In other words, in the shares file, how does a datatx share differ from a regular share?

Add one more parameter to the schema?

That is one solution I was also thinking of.
So simplest:
cs3.sharing.ocm.v1beta1.Share {
   ... ,
   bool is_data_transfer_share
}

Or maybe share_type in case there there could be other future types, don't know, maybe stream type ...

Sure, share_type would be better. Please create a PR and in the description part in the proto file, mention this use case

https://github.com/cs3org/cs3apis/pull/109

How about using the share ID instead of transfer ID in cs3 datatx api. The share ID is already there. That would simplify things.

@ishank011 : I believe ocm.share manager interface method Save() needs an additional share type arg.

@redblom sure, feel free to make changes as you need.

@ishank011 please review https://github.com/cs3org/reva/pull/1578

@ishank011 : Implementing this (#1578) I think we should use ocm-share-create for a transfer also. An OCM share will always be the starting point anyway and the Share.ShareType is already introduced. So the call would be something like:
cmd/reva/reva -insecure ocm-share-create -shareType transfer -grantee jarek1234 -granteeType user -idp softwaremind.com /home/test
Then we change the CS3 datatx CreateTransferRequest message to contain Share (or at least the share id) (and optional opaque) fields only. *Note that the actual share id will be the transfer identifier (previously transfer id).
Now when UpdateReceivedOCMShare is called it can delegate to grpc.gateway.datatx.CreateTransfer with the share specified and the transfer can be initiated from thereon:
pkg.datatx.TxDriver.CreateTransfer(shareID, ...)
I think it makes more sense.

When UpdateReceivedOCMShare is called, the reference is created in the shares directory https://github.com/cs3org/reva/blob/master/internal/grpc/services/gateway/ocmshareprovider.go#L260 -> https://github.com/cs3org/reva/blob/master/internal/grpc/services/gateway/ocmshareprovider.go#L291-L349, where the default path is /home/Shares/name-of-shared-resource. We can use the same path as the destination.
For WebDAV share references, we have the target webdav://token@idp?name=share-name. For transfers, we don't really need a target as the whole resource will be located here and we can just pass this path to rclone.
These references are statted in the gateway storageprovider service https://github.com/cs3org/reva/blob/master/internal/grpc/services/gateway/storageprovider.go#L1369-L1395. We'll need to add a case for transfer refs to just be returned as it is. We have all the existing functionalities that will allow users to make changes to any files/folders located inside this reference.

@ishank011 I'd like to see this merged first (create transfer type OCM share) https://github.com/cs3org/reva/pull/1578

When UpdateReceivedOCMShare is called, the reference is created in the shares directory https://github.com/cs3org/reva/blob/master/internal/grpc/services/gateway/ocmshareprovider.go#L260 -> https://github.com/cs3org/reva/blob/master/internal/grpc/services/gateway/ocmshareprovider.go#L291-L349, where the default path is /home/Shares/name-of-shared-resource. We can use the same path as the destination.

@ishank011 What would be the resulting location here, eg. marie/name-of-shared-resource ? And then ./reva stat /home/Shares/name-of-shared-resource would work?

You're passing the /remote.php/webdav endpoints for both PUT and GET to rclone, right? Then you just need to use the path /home/Shares/name-of-shared-resource everywhere. Reva will resolve that based on the user in context.

I use single endpoints for each request. For transfer the rclone service is called through 2 possible endpoints, operations/copyfile to transfer a file and sync/copy to transfer a folder structure. These calls will asynchronous and immediately return a jobID (to be used for status/cancel requests).
The requests' data is in the form of a single string with all necessary parameters included (https://rclone.org/docs/#connection-strings). A folder transfer example of such a req data string would be:
'{"_async":true,"srcFs":":webdav,bearer_token=\"...token...\",url=\"http://reva-datatx:20080/webdav\":/big-data","dstFs":":webdav,bearer_token=\"...token...\",url=\"http://reva-2:20080/webdav\":/big-data"}'
This would be a transfer to a 'local' path, eg marie/big-data/...
I experimented with accepted shares where I gave rclone the share path like url=\"http://reva-2:20080/webdav\":/MyShares/big-data but that did not quite work. I was expecting these files to exist somewhere in (my case) marie/big-data/... but for the user at /MyShares/big-data/.... So first I want to know if this is indeed what's expected.

Which service handles the requests at the /webdav endpoint?

Which service handles the requests at the /webdav endpoint?

../../internal/http/services/owncloud/ocdav/ocdav.go
@ishank011 I'm also not sure what should be returned here for the transfer case (https://github.com/cs3org/reva/blob/master/internal/grpc/services/gateway/storageprovider.go#L1369-L1395) exactly? Simply the provided resourceInfo? How should we establish here that this is a transfer ref?

Use the path /remote.php/webdav/home/MyShares/xyz. It should work

Simply the provided resourceInfo?

Yes

How should we establish here that this is a transfer ref?

Check the scheme

Use the path /remote.php/webdav/home/MyShares/xyz. It should work

Yes, that seems to work!

Simply the provided resourceInfo?
Yes

How should we establish here that this is a transfer ref?

Check the scheme

And that should read datatx I suppose, because now it's webdav. That makes sense.

Simply the provided resourceInfo?
Yes

How should we establish here that this is a transfer ref?

Check the scheme

And that should read datatx I suppose, because now it's webdav. That makes sense.

@ishank011 : I can set the scheme to datatx here: https://github.com/cs3org/reva/blob/1765ae8db4d0d5e615fc3b55275e563dd5a1c687/internal/grpc/services/gateway/ocmshareprovider.go#L324
Then I can determine it at https://github.com/cs3org/reva/blob/master/internal/grpc/services/gateway/storageprovider.go#L1369-L1395 for the new case. Is that correct?

This PR is superseded by https://github.com/cs3org/reva/pull/2052


BVAL-592 Example fixes

Hi, @gsmet. Can we merge this one?

It's already merged. Forgot to close it!

Ah, cool. So it's part of the last release actually?
2017-05-19 9:58 GMT+02:00 Guillaume Smet<EMAIL_ADDRESS>
Closed #178
https://github.com/beanvalidation/beanvalidation-spec/pull/178.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/beanvalidation/beanvalidation-spec/pull/178#event-1089093361,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABvxJbCYYS34m4LOCwphH5Ks2phyEvuks5r7Uu6gaJpZM4Nd6QO
.

Yes, it is.


Stack trace section could be more readable

IMO just some CSS improvement. previous was more readable/pleasant.
with version 1.4.24.RC2

with version  1.4.23

The situation on your  screenshot is not expected. For me it looks better:

Any information about your browser version and OS would be helpful.

Yes, the issue seems to be with the browser. Checked with firefox on the same machine it does not happen on firefox.
Here's the detail where issue is faced
Browser : Google Chrome Version 53.0.2785.101 (64-bit)
OS : Ubuntu 15.10

Fixed in 2.0-BETA1 https://github.com/allurefw/allure-report/releases/tag/2.0-BETA1


Spark SQL language server

hey @krassowski wanted to mention that we are mostly feature complete with our jupyterlab-sql-editor extension.
https://github.com/CybercentreCanada/jupyterlab-sql-editor
Since we make heavy use of jupyterlab-lsp I thought you might be interested in finding out more about it.
We wrote Towards Data Science articles describing its use.
<EMAIL_ADDRESS><EMAIL_ADDRESS>Our extension installs itself without any modifications to jupyterlab-lsp. However we would be interested in adding it to the list of language server you have in your documentation. What would be involved in doing so.

Good stuff, glad it's working out for you.
We don't really have such a section in docs/Language Servers.ipynb, as we only list stuff we test (or use in the course of development), though there are a couple more floating around out there such as graph-lsp, json-lsp and yaml-lsp.
As adding more servers-under-test to this repo is rather complicated, perhaps proposing a PR of  docs/Third Party Language Servers.md with a similar table structure to the the existing one would be appropriate, with links in the ToC, and at the bottom of the page.
Alternately, it could be another notebook and YAML file with these columns... this might actually be a bit more consistent and easier to PR against, as collaboratively editing Markdown tables isn't much fun.

@bollwyvl that sounds good. We'll add ourselves to the markdown file. I can't find it in the repo. Is it something generated?

No, it would need to be added to the docs folder.

Maybe creating a yaml file but adding the result as a section in docs/Language Servers.ipynb instead of a new page could end up being more discoverable for users?

I'm not too familiar with how the documentation generator works. I have placed this file which contains information for jupyterlab-sql-editor. It would be great if someone could integrate this into the documentation for me. I'm sure you guys can do this way faster than I can ;-)
https://github.com/jupyter-lsp/jupyterlab-lsp/pull/826

Thank you. I pushed to your branch and will merge once checks pass.

thanks @krassowski much appreciated

Closing as addressed by #826, thanks again!


fix typo: the the -> the

PR Summary
PR Context
minor fix
PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[ ] Summarized changes
[ ] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[ ] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.

Breaking changes

[x] None
OR
[ ] Experimental feature(s) needed

[ ] Experimental feature name(s):

User-facing changes

[x] Not Applicable
OR
[ ] Documentation needed

[ ] Issue filed:

Testing - New and feature

[ ] N/A or can only be tested interactively
OR
[ ] Make sure you've added a new test if existing tests do not effectively test the code changed

Tooling

[ ] I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
OR
[ ] I have considered the user experience from a tooling perspective and opened an issue in the relevant tool repository. This may include:

[ ] Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode
(which runs in a different PS Host).

[ ] Issue filed:

[ ] Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.

[ ] Issue filed:

[ ] Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).

[ ] Issue filed:

[ ] Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).

[ ] Issue filed:

@eltociear https://github.com/eltociear/PowerShell/commit/564d1dfa5823bef8959adf4d787f9b06b5925b73 fixes the only instance of the the in https://github.com/PowerShell/PowerShell/commit/master, therefore you could change the PR title to:

fix typo: the the -> the

@eltociear FYI, you can backticks within GitHub issue titles for enhanced formatting, i.e.:
fix typo: `the the` -> `the`


Adaptive Correction factor

You have provided a way to supress high range frequencies in FDN.
def get_center_freq(self):
        # TODO compute them for a given min ad max frequency
        if self.octave == 1:
            self.f_bands = [63, 125, 250, 500, 1000, 2000, 4000, 8000]
            self.correction = np.array([5, 0, 0, 0, 0, 0, 0, 0, 5, 30])
        elif self.octave == 3:
            self.f_bands = [63, 80, 100, 125, 160, 200, 250, 315, 400, 500, 630, 800, 1000, 1250, 1600, 2000, 2500, 3150, 4000, 5000, 6300, 8000]
            self.correction = np.array([5, 5, 5, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 5, 5, 5, 30])
        else:
            ValueError('Resolutions different form one or one-third octave bands are not supported at the moment')

Would you recommend any adaptive method to change values in the variables correction for maximum similarity between FDN IR and reference IR?
Upon recommendation, I can do it and request you to contribute as well.
Thanks!

Hi @tarlanahad! That’s a great question. Adjusting the frequency response of the attenuation filters to improve the match between the target and synthesized RIR is a task that deserves careful study. However, since you have the reference T60 curve, you could iteratively adjust the command gains of the GEQ after analyzing the T60 curve of the synthesized RIR until you achieve a perfect match.
Personally, I’m exploring "lazier" methods for this adjustment. As a proof of concept (though not a perfectly working approach yet), we tried optimizing the command gains of a differentiable graphic equalizer using gradient descent and a cost function based on the STFTs of the target and reference RIRs. You can check it out in my other repository, which is dedicated to a PyTorch library that @GianMarcoDeBortoli and I have been working on recently.
Let me know if it helps!

I did the iterative FDN, however, although the match between target T60 and L values are perfect (virtually the same) it brings the metallic colour of the FDN back, unfortunately.  It probably happens because adjustment changes the modal excitation distribution of FDN back to the unoptimized version.
I will analyze the STFT based method mentioned. Thanks so much for the response!


Item rename - no refresh

when I rename a typical the name is not refreshed immediately, I need to update the node to see the new name

in some cases it works, not sure why.

from where? Is this related to #98 ?

In the node view.
Not sure if related.
That was on tag this is on slots..


Update to Angular 6 and fix demo with HttpClient

closes #265

Coverage remained the same at 96.594% when pulling 26c131e331b1a92661abdbd9e39c267904049e8e on dkamburov/update-angular6 into 26b7c743560506b2fb9c76b0cba8d375919862d7 on master.

Testing update: Everything looks good. We need to investigate the AOT sample.


WORK-535 Docusign2AppUpdate

Added new App for both acidic & docusign fact providers that now work with WORK-535 branch.

@tpanagos Any reason why it's on the test folder instead of demo?

@tpanagos
This is outdated, contains commits from a lot of other projects, and is overridden by  PR #22
Closing


Error on go get

Hi,
great library!
Thanks

Hi,
bug fixed.
The problem was in golang itself, which prohibits the use of special characters in paths. Using ":" is prohibited for Windows.
I have hidden the path fixtures from golang by transferring them to a zip archive.

Thank you !


50 update user form with clients feedback

Description
add 'Transgender' and 'Other' options to the gender dropdown list
qualification field should have the following options: 'Cannot read or write', '8th', '10th', '12th', 'Graduate', 'Postgraduate', 'Other'
case status should have the following options: 'Ongoing', 'Acquitted', 'Convicted'
pin code and email fields should be non compulsory: pin code should also be changed in the database and NOT have 'not null' requirement
Related
#50
Fixes #1
Checklist:

[x] My code follows the style guidelines of this project
[x] I have carefully reviewed my own code
[ ] I have commented my code
[ ] I have updated any documentation

I'm receiving error 400 (Bad Request) after submitting the form, are you done with these pull requests?

I'm receiving error 400 (Bad Request) after submitting the form, are you done with these pull requests?

thank you Milad for checking this it has done know please check again

@Miladepour , are you still getting an error?

@Miladepour , are you still getting an error?

Yes, what about you?

can you see what the error is? Is the pin code in your local database set to be NOT not null?

can you see what the error is? Is the pin code in your local database set to be NOT not null?

Thanks, I fixed that on my database.


Remove .travis.yml

Pull Request Test Coverage Report for Build 363599190

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

Totals

Change from base Build 363593669:
0.0%

Covered Lines:
716

Relevant Lines:
1066

💛  - Coveralls


Can't run, "Could not find nokogiri-1.13.8 in any of the sources"

I am trying to gem install license_finder and run as license_finder per README instructions.
I am trying to use it in a ruby project with a Gemfile.
But:
jrochkind-shi scihist_digicoll (master ?) $ gem install license_finder
Fetching license_finder-7.0.1.gem
Fetching with_env-1.1.0.gem
Fetching xml-simple-1.1.9.gem
Successfully installed xml-simple-1.1.9
Successfully installed with_env-1.1.0
Successfully installed license_finder-7.0.1
3 gems installed

jrochkind-shi scihist_digicoll (master ?) $ license_finder
LicenseFinder::Bundler: is active
LicenseFinder::NPM: is active
LicenseFinder::Yarn: is active
/Users/jrochkind/.gem/ruby/3.0.4/gems/bundler-2.3.14/lib/bundler/definition.rb:486:in `materialize': Could not find nokogiri-1.13.8 in any of the sources (Bundler::GemNotFound)
	from /Users/jrochkind/.gem/ruby/3.0.4/gems/bundler-2.3.14/lib/bundler/definition.rb:241:in `specs_for'
	from /Users/jrochkind/.gem/ruby/3.0.4/gems/license_finder-7.0.1/lib/license_finder/package_managers/bundler.rb:66:in `gem_details'
	from /Users/jrochkind/.gem/ruby/3.0.4/gems/license_finder-7.0.1/lib/license_finder/package_managers/bundler.rb:51:in `details'
	from /Users/jrochkind/.gem/ruby/3.0.4/gems/license_finder-7.0.1/lib/license_finder/package_managers/bundler.rb:16:in `current_packages'
	from /Users/jrochkind/.gem/ruby/3.0.4/gems/license_finder-7.0.1/lib/license_finder/package_manager.rb:105:in `current_packages_with_relations'
	from /Users/jrochkind/.gem/ruby/3.0.4/gems/license_finder-7.0.1/lib/license_finder/scanner.rb:42:in `each'
	from /Users/jrochkind/.gem/ruby/3.0.4/gems/license_finder-7.0.1/lib/license_finder/scanner.rb:42:in `flat_map'
	from /Users/jrochkind/.gem/ruby/3.0.4/gems/license_finder-7.0.1/lib/license_finder/scanner.rb:42:in `active_packages'
	from /Users/jrochkind/.gem/ruby/3.0.4/gems/license_finder-7.0.1/lib/license_finder/core.rb:84:in `current_packages'
	from /Users/jrochkind/.gem/ruby/3.0.4/gems/license_finder-7.0.1/lib/license_finder/core.rb:79:in `decision_applier'
	from /Users/jrochkind/.rubies/ruby-3.0.4/lib/ruby/3.0.0/forwardable.rb:232:in `any_packages?'
	from /Users/jrochkind/.gem/ruby/3.0.4/gems/license_finder-7.0.1/lib/license_finder/license_aggregator.rb:17:in `block in any_packages?'
	from /Users/jrochkind/.gem/ruby/3.0.4/gems/license_finder-7.0.1/lib/license_finder/license_aggregator.rb:15:in `map'
	from /Users/jrochkind/.gem/ruby/3.0.4/gems/license_finder-7.0.1/lib/license_finder/license_aggregator.rb:15:in `any_packages?'
	from /Users/jrochkind/.gem/ruby/3.0.4/gems/license_finder-7.0.1/lib/license_finder/cli/main.rb:119:in `action_items'
	from /Users/jrochkind/.gem/ruby/3.0.4/gems/thor-1.2.1/lib/thor/command.rb:27:in `run'
	from /Users/jrochkind/.gem/ruby/3.0.4/gems/thor-1.2.1/lib/thor/invocation.rb:127:in `invoke_command'
	from /Users/jrochkind/.gem/ruby/3.0.4/gems/thor-1.2.1/lib/thor.rb:392:in `dispatch'
	from /Users/jrochkind/.gem/ruby/3.0.4/gems/thor-1.2.1/lib/thor/base.rb:485:in `start'
	from /Users/jrochkind/.gem/ruby/3.0.4/gems/license_finder-7.0.1/bin/license_finder:6:in `<top (required)>'
	from /Users/jrochkind/.gem/ruby/3.0.4/bin/license_finder:25:in `load'
	from /Users/jrochkind/.gem/ruby/3.0.4/bin/license_finder:25:in `<main>'

Maybe somehow modern bundler is doing something automatically even though I didn't run bundle exec license_finder, becuase my project uses bundler, and in fact any project using bundler has to put license_finder in Gemfile? Should README be changed to recommend this?
If I do add license_finder to Gemfile and bundle exec license_finder instead, it does work.
But now I have to deal with:

but can pull in unwanted dependencies, including bundler. To mitigate this problem, see Excluding Dependencies.

This is definitely an environment issue. Bundler is always changing stuff and when we fix it one way it breaks another. Just to test this quick, I pulled the default ruby docker image and ran gem install license_finder --install-dir /usr/local/lib/ruby/gems/3.1.0 and it all seemed to work. Is there a specific image that you are getting this error on?
It just looks like license finder is being installed in a different folder than where the rest of your gems are

Hi, thanks for the response!
I am not using a docker image for my ruby environment, I don't use docker.

It just looks like license finder is being installed in a different folder than where the rest of your gems are

I have never run into such a thing before, I don't know how gems would wind up in different folders.
It also does not SEEM to be true to me.  All my gems seem to be in /Users/jrochkind/.gem/ruby/3.0.4/gems
Eg:
jrochkind-shi scihist_digicoll (master ?) $ gem which license_finder
/Users/jrochkind/.gem/ruby/3.0.4/gems/license_finder-7.0.1/lib/license_finder.rb

jrochkind-shi scihist_digicoll (master ?) $ gem which rake
/Users/jrochkind/.gem/ruby/3.0.4/gems/rake-13.0.6/lib/rake.rb

jrochkind-shi scihist_digicoll (master ?) $ bundle show rake
/Users/jrochkind/.gem/ruby/3.0.4/gems/rake-13.0.6

Where are you seeing the evidence that some of my gems are installed in a different place, and what is that place?
I do use chruby as a ruby version manager, perhaps it's somehow incompatible with license_finder? I have not previously run into any problems like this in years of using chruby, it's ordinarily pretty solid.
(Note: I can use license_finder by adding it to my Gemfile and using bundle exec, but I agree with README that this is undesirable).

Just playing in a fresh environment, the output of gem env is:
RubyGems Environment:
  - RUBYGEMS VERSION: 3.3.7
  - RUBY VERSION: 3.1.2 (2022-04-12 patchlevel 20) [x86_64-linux]
  - INSTALLATION DIRECTORY: /usr/local/bundle
  - USER INSTALLATION DIRECTORY: /root/.local/share/gem/ruby/3.1.0
  - RUBY EXECUTABLE: /usr/local/bin/ruby
  - GIT EXECUTABLE: /usr/bin/git
  - EXECUTABLE DIRECTORY: /usr/local/bundle/bin
  - SPEC CACHE DIRECTORY: /root/.local/share/gem/specs
  - SYSTEM CONFIGURATION DIRECTORY: /usr/local/etc
  - RUBYGEMS PLATFORMS:
     - ruby
     - x86_64-linux
  - GEM PATHS:
     - /usr/local/bundle
     - /root/.local/share/gem/ruby/3.1.0
     - /usr/local/lib/ruby/gems/3.1.0
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :backtrace => false
     - :bulk_threshold => 1000
     - "install" => "--no-document"
     - "update" => "--no-document"
  - REMOTE SOURCES:
     - https://rubygems.org/
  - SHELL PATH:
     - /usr/local/sbin
     - /usr/local/bin
     - /usr/sbin
     - /usr/bin
     - /sbin
     - /bin

The gem path being used is  /usr/local/lib/ruby/gems/3.1.0/gems/ but when installing license finder with gem install, license finder is installed into /usr/local/bundle/gems/. That is all I meant by changing the install directory. chruby would change this though. I use rvm and have this gems in an rvm specific folder

I had the same problem, solved by forcing ruby platform in bundle config: https://stackoverflow.com/questions/69807153/macos-m1-arm64-unable-to-load-nokogiri-using-system-default-ruby


On press does not change the text input

Hi,
After the autocomplete find the element, when I select it this does not show in the text input.
does anyone can understand what's happening?
<Autocomplete
data={notEatitems.length === 1 && comp(query, notEatitems[0]) ? [] : notEatitems}
defaultValue={query}
keyboardShouldPersistTaps={true}
onChangeText={text => this.setState({query: text})}
renderItem={data => (
<TouchableOpacity onPress={() =>
this.setState({query: data})}>
{data}

)}
/>

hi,
I also have the same issue as @Talkwondo described above. I tried in iOS and Android devices and result is the same. I also tried different versions of react-native-autocomplete-input (2.0.0 and 1.1.2) and still see the issue.
It seems that renderItem does not work at all, because alert is never invoked in the following example (similar as in Example.js):
renderItem={({ title, release_date }) => (
<TouchableOpacity
onPress={() => {
alert('onPress!')
this.setState({ query: title })
}}>

{title} ({release_date.split('-')[0]})

)}
any ideas?

Strange.. Does it work with the example?

unfortunately your example does not work for me (tried on real Android device and on iOS simulator)

hi @l-urence,
I finally found root of my problem: I put autocomplete component inside ScrollView (already checked solution for #5).  So it works fine for Android and iOS with version 1.1.2.
As the title of issue: 'On press does not change the text input', I had the same behavior, but it could be solved by customizing component: use states for text input (defaultValue property) and key (autocompleteUpdateableKey: Math.random())
<Autocomplete
// need this key for updating input field on selecting value from suggestion list
key={this.state.autocompleteUpdateableKey}
defaultValue={this.state.autocompleteDisplayedText}

@vasiliy-sarzhynskyi cool then I will close this.


[Candidate 1v1 Dammed Scorpion ZH v2] There is a gap in the water at destroyed dam

Issue Description
There is a gap in the water at destroyed dam. Is most visible when the fog hides the particles.
Expected behavior
No gap in water near dam.
Screenshots

fixed.


Moved clean up code out of disposing condition

This does not need to be inside the disposing condition. We also want to make sure we don't leave the timer event hanging around, as it may cause a memory leak.

Since these are managed resources my understanding was that they should be called within the disposing check so they are not called again during finalize.
See: https://docs.microsoft.com/en-us/dotnet/standard/garbage-collection/implementing-dispose

What I observed when testing this was on occasion these where not called which meant the FlushTimer.Elapsed was not cleaned up. I'll test it further to make sure.

Dispose() is the one that invokes Dispose(true) so you'd have to have all of the references in a using() for it to invoke properly. Having said that, I haven't implemented Dispose very much (the first version of the library didn't have Dispose at all) so it could be incorrect.  As long as each method that you moved out is safe to call more than once this would be a fine change as well.

Thanks again for your help by the way.  Hope you are enjoying the library and it's working for your use cases! I originally started it just for fun one weekend, and it's great to see it getting traction and that others are finding it useful.

@kodejack let me know you're still observing an issue with this on 1.0.0 or not

Sorry, I no longer have access to the equipment so can’t test it.