scipy/stats/tests/test_continuous_basic.py::test_cont_basic[500-200-ncf-arg74] test fails with IntegrationWarning

scipy/stats/tests/test_continuous_basic.py::test_cont_basic[500-200-ncf-arg74] test fails in 1.7.1.
Error message:
_________________________________________________ test_cont_basic[500-200-ncf-arg74] __________________________________________________
scipy/stats/tests/test_continuous_basic.py:189: in test_cont_basic
    check_entropy(distfn, arg, distname)
        alpha      = 0.01
        arg        = (27, 27, 0.41578441799226107)
        distfn     = <scipy.stats._continuous_distns.ncf_gen object at 0x7f8939255910>
        distname   = 'ncf'
        locscale_defaults = (0, 1)
        m          = array(1.09663138)
        meths      = [<bound method rv_continuous.pdf of <scipy.stats._continuous_distns.ncf_gen object at 0x7f8939255910>>, <bound method ...f8939255910>>, <bound method rv_continuous.logsf of <scipy.stats._continuous_distns.ncf_gen object at 0x7f8939255910>>]
        n_fit_samples = 200
        rng        = RandomState(MT19937) at 0x7F88CEEBDB40
        rvs        = array([0.90888841, 0.87523216, 0.73228753, 1.33584017, 0.93548576,
       1.09504212, 1.15670442, 0.36786914, 0.791225...03, 1.73540023, 0.87035866, 0.73702581, 0.81477748,
       0.87362182, 1.58673099, 1.88455316, 0.61564337, 1.09912842])
        sm         = 1.0740685247899555
        sn         = 500
        spec_x     = {'levy_l': -0.5, 'pareto': 1.5, 'rv_histogram_instance': 5.0, 'tukeylambda': 0.3, ...}
        sv         = 0.1911827409537913
        v          = array(0.2013794)
        x          = 0.5
scipy/stats/tests/common_tests.py:93: in check_entropy
    ent = distfn.entropy(*arg)
        arg        = (27, 27, 0.41578441799226107)
        distfn     = <scipy.stats._continuous_distns.ncf_gen object at 0x7f8939255910>
        msg        = 'ncf'
scipy/stats/_distn_infrastructure.py:1254: in entropy
    place(output, cond0, self.vecentropy(*goodargs) + log(goodscale))
        args       = (array(27), array(27), array(0.41578442))
        cond0      = True
        goodargs   = [array([27]), array([27]), array([0.41578442])]
        goodscale  = array([1])
        kwds       = {}
        loc        = array(0)
        output     = array(0.)
        scale      = array(1)
        self       = <scipy.stats._continuous_distns.ncf_gen object at 0x7f8939255910>
/usr/lib/python3.8/site-packages/numpy/lib/function_base.py:2163: in __call__
    return self._vectorize_call(func=func, args=vargs)
        args       = (array([27]), array([27]), array([0.41578442]))
        excluded   = set()
        func       = <bound method rv_continuous._entropy of <scipy.stats._continuous_distns.ncf_gen object at 0x7f8939255910>>
        kwargs     = {}
        self       = <numpy.vectorize object at 0x7f8939255c10>
        vargs      = (array([27]), array([27]), array([0.41578442]))
/usr/lib/python3.8/site-packages/numpy/lib/function_base.py:2246: in _vectorize_call
    outputs = ufunc(*inputs)
        args       = (array([27]), array([27]), array([0.41578442]))
        func       = <bound method rv_continuous._entropy of <scipy.stats._continuous_distns.ncf_gen object at 0x7f8939255910>>
        inputs     = [array([27], dtype=object), array([27], dtype=object), array([0.41578441799226107], dtype=object)]
        otypes     = 'd'
        self       = <numpy.vectorize object at 0x7f8939255c10>
        ufunc      = <ufunc '_entropy (vectorized)'>
scipy/stats/_distn_infrastructure.py:2621: in _entropy
    h = integrate.quad(integ, _a, _b)[0]
        _a         = 0.0
        _b         = inf
        args       = (27, 27, 0.41578441799226107)
        integ      = <function rv_continuous._entropy.<locals>.integ at 0x7f88cba75550>
        self       = <scipy.stats._continuous_distns.ncf_gen object at 0x7f8939255910>
scipy/integrate/quadpack.py:400: in quad
    warnings.warn(msg, IntegrationWarning, stacklevel=2)
E   scipy.integrate.quadpack.IntegrationWarning: The occurrence of roundoff error is detected, which prevents
E     the requested tolerance from being achieved.  The error may be
E     underestimated.
        a          = 0.0
        args       = ()
        b          = inf
        epsabs     = 1.49e-08
        epsrel     = 1.49e-08
        flip       = False
        full_output = 0
        func       = <function rv_continuous._entropy.<locals>.integ at 0x7f88cba75550>
        ier        = 2
        limit      = 50
        limlst     = 50
        maxp1      = 50
        msg        = 'The occurrence of roundoff error is detected, which prevents \n  the requested tolerance from being achieved.  The error may be \n  underestimated.'
        msgs       = {80: 'A Python error occurred possibly while calling the function.', 1: 'The maximum number of subdivisions (50) has b...\n  underestimated.', 3: 'Extremely bad integrand behavior occurs at some points of the\n  integration interval.', ...}
        points     = None
        retval     = (nan, nan, 2)
        weight     = None
        wopts      = None
        wvar       = None

Scipy/Numpy/Python version information:
$  python3.8 -c 'import sys, scipy, numpy; print(scipy.__version__, numpy.__version__, sys.version_info)'
1.7.1 1.21.1 sys.version_info(major=3, minor=8, micro=11, releaselevel='final', serial=0)

Same... passes on master. Can you verify all three with master on your system?

Closing as probably related to #14517 We can reopen if you have contradicting elements later on.

I've just seen this error in scipy 1.8.1, rebuilding on a Debian (unstable) system. It previously passed fine.  The main difference is that previously the tests were run with
python3 -c "import scipy; exit( not scipy.test() )"

Now I'm trying to run them using
python3 runtests.py -n -v

(in order to get more control of which tests are run).
I can reproduce the error directly with
python3 runtests.py -n -v -- -k "test_cont_basic[500-200-ncf-arg74]"

Patch #16822 that closed #14517) only changed Schur tests.  Should this Issue #14519 be reopened?
Building with gcc 12.1.0 and pythran 0.11.0.
System info:
python3.10 -c 'import sys, scipy, numpy; print(scipy.__version__, numpy.__version__, sys.version_info)'
1.8.1 1.21.5 sys.version_info(major=3, minor=10, micro=6, releaselevel='final', serial=0)

@drew-parsons, you are right, this issue is not related to #14157.

I reopened the issue, but it is still possible that the problem has been fixed (directly or indirectly) in the main development branch.  For example, https://github.com/scipy/scipy/pull/15763 made significant changes to the ncf distribution.  @drew-parsons, are you able to rerun the tests on your system with SciPy 1.9.0?

Our watch script got stuck on 1.8, I hadn't seen that 1.9 is already released. I'll prepare a 1.9 build and report back.

@drew-parsons any luck here?

I've had to put the 1.9 build on hold since it requires pymeson to build.  Debian doesn't have pymeson packaged yet, but the packagin process has started, tracked at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017959

@drew-parsons it looks like that issue was resolved. Does the test pass now?

debian finally got mesonpy packaged, and we now have scipy 1.10 built.  test_cont_basic[500-200-ncf-arg74] is indeed passing now.
$ python3 runtests.py -v -n -s stats -- -k "test_cont_basic[500-200-ncf-arg74]"
Running tests for scipy version:1.10.0, installed at:/usr/lib/python3/dist-packages/scipy
=============================================================================================== test session starts ===============================================================================================
platform linux -- Python 3.11.1, pytest-7.2.1, pluggy-1.0.0+repack -- /usr/bin/python3
cachedir: .pytest_cache
hypothesis profile 'default' -> database=DirectoryBasedExampleDatabase('/home/drew/projects/python/build/scipy/build/test/.hypothesis/examples')
rootdir: /home/drew/projects/python/build/scipy, configfile: pytest.ini
plugins: xvfb-2.0.0, remotedata-0.4.0, asyncio-0.20.3, arraydiff-0.5.0, filter-subpackage-0.1.2, flaky-3.7.0, hypothesis-6.64.0, cov-4.0.0, mpi-0.6, astropy-header-0.2.2, openfiles-0.5.0, mock-3.8.2, doctestplus-0.12.1, astropy-0.10.0
asyncio: mode=Mode.STRICT
collected 8512 items / 8511 deselected / 1 selected

../../tests/test_continuous_basic.py::test_cont_basic[500-200-ncf-arg74] PASSED                                                                                [100%]

======================================================================================= 1 passed, 8511 deselected in 2.71s ========================================================================================


old gulp-sass version breaks npm install ...

... using the current gulp-sass version fixes the issue

sorry, wrong project


WebGPU Support

This is the root ticket of WebGPU Implementation, and will be updated regularly to keep it up to date with new issues to work on and the work done.
For live preview, visit the url on up to date Chrome: https://playcanvas.github.io/
https://user-images.githubusercontent.com/59932779/203333981-3d77fc58-5e5a-4b00-add1-8ab5a3991c84.mov
https://user-images.githubusercontent.com/59932779/205290862-22eff1fd-53d9-4336-815e-5f7311b923d5.mov
https://user-images.githubusercontent.com/59932779/205290893-555888b4-74d2-4b6d-a963-1e0a86daea12.mov
https://user-images.githubusercontent.com/59932779/208122279-d85d1c22-48b3-4db8-b9d8-9872d111c739.mov
https://user-images.githubusercontent.com/59932779/205909226-d3d90aa0-c118-49f7-be0e-b56576a5235c.mov
https://user-images.githubusercontent.com/59932779/213508864-71ba2fb6-7c59-425e-bc3d-db94c2cd6e65.mov
https://user-images.githubusercontent.com/59932779/214621963-bc1b6bd5-8775-40f7-a339-6612b59fd5c2.mov
https://user-images.githubusercontent.com/59932779/217569603-95fc0dbd-d86f-4ccd-badf-42f9873ab3a7.mov
https://user-images.githubusercontent.com/59932779/222208562-efa32552-9da7-4a3d-a27f-f67fc1e91812.mov
https://github.com/playcanvas/engine/assets/59932779/b56291dc-513f-49f6-bcbc-50b0a24ec3cc
Class layout overview

graphics folder will have two subfolders created for respective implementations: /webgl, /webgpu
existing GraphicsDevice class will be platform independent, and WebglGraphicsDevice and WebgpuGraphicsDevice will extend it to implement platform specific implementations.
other graphic classes, such as VertexBuffer, IndexBuffer and similar will be split into 3 classes as well, and this is the example structure:

// base platform independent class
class VertexBuffer {
    impl = null;   // platform dependent implementation (WebglVertexBuffer or WebgpuVertexBuffer)
};

Refactorings
The engine will undergo extensive refactoring, to more natively and with better performance support WebGPU API.
Issues:

General
#4261
#2254
#4281
#4271
#5689
#5688
#5357
#5690
#2974
#5692

PRs:

General
#3982
#4009
#4010
#4014
#4013
#4086
#4127
#5150
#5083

Uniform buffer / bind group support:
#4156
#4258
#4387
#4394
#4402
#4410
#4497
#4568
#4575
#5438

Render Passes
#4272
#4317
#4328

WebGPU implementation
#4534
#4818
#4872
#4989
#5050
#5118
#5275
#5319
#5336
#5485
#5490

Compute shaders
#5757
#5760
#6201

Partial list of missing features:

rendering to cube-map render target (both color and depth) does not support multisampling, and might be upside down, related to https://github.com/playcanvas/engine/pull/4911
async texture readback is missing https://github.com/playcanvas/engine/issues/2974
picker is not working, requires the async texture feedback
Lightmapper is disabled as it has issues
https://github.com/playcanvas/engine/issues/6157
https://github.com/playcanvas/engine/issues/6171

@mvaligursky https://poki.com/en/g/village-builder is now running the WebGPU enabled build of PlayCanvas. At Poki we capture erros, so I'm seeing a bunch of WebGPU related errors now. Would you like me to create separate issues for those or maybe just post comments for them here? The errors all affect less than 1% of the players, so if you don't have time you can also ignore them. I have some stack traces and device/browser information with them as well.
These are the most occurring error messages:
console.error: ["Failed to link shader program. 'tex2Dgrad': no matching 2 parameter intrinsic function

AbortError: Failed to execute 'mapAsync' on 'GPUBuffer': Device is lost

RangeError: Failed to execute 'createBuffer' on 'GPUDevice': createBuffer failed, size is too large for the implementation when mappedAtCreation == true

TypeError: Cannot read properties of undefined (reading 'renderTarget')

Failed to transpile webgl vertex shader [Shader Id 3 LitShader-ShadowPass_1_0-proc] to WebGPU: [GLSL compilation failed] while rendering undefined

TypeError: a.vertexAttribDivisor is not a function (doesn't seem WebGPU related but only happens in this latest release)

@erikdubbelboer - please create multiple issues on these with the details you have, keen to see what's going on.


Fresh install of Sofie crash.

Hi,
I have just installed Sofie on a new machine.
I have the Playout Gateway and the MOS Gateway running.
But when I try to run Sofie (using "meteor") I get this error.
client/ui/Prompter/PrompterView.tsx (85, 3): Type '{ mirror: boolean; mirrorv: boolean; restrictMode: string | string[] | undefined; followTake: boo...' is not assignable to type 'PrompterConfig'

Have tried both Master and Develop branch.

Here´s the full error:
=> Started proxy.
client/ui/Prompter/PrompterView.tsx (85, 3): Type '{ mirror: boolean; mirrorv: boolean; restrictMode: string | string[] | undefined; followTake: boo...' is not assignable to type 'PrompterConfig'.
  Types of property 'restrictMode' are incompatible.
    Type 'string | string[] | undefined' is not assignable to type 'string | undefined'.
      Type 'string[]' is not assignable to type 'string | undefined'.
        Type 'string[]' is not assignable to type 'string'.
client/ui/Prompter/PrompterView.tsx (90, 23): Argument of type 'string | string[] | null | undefined' is not assignable to parameter of type 'string'.
  Type 'undefined' is not assignable to type 'string'.
client/ui/Prompter/PrompterView.tsx (91, 21): Argument of type 'string | string[] | null | undefined' is not assignable to parameter of type 'string'.
  Type 'undefined' is not assignable to type 'string'.
=> Meteor 1.8.1 is available. Update this project with 'meteor update'.
=> Started MongoDB.
W20190408-10:02:38.907(2)? (STDERR) {"date":"Mon Apr 08 2019 10:02:36 GMT+0200 (CEST)","process":{"pid":23822,"uid":1000,"gid":1000,"cwd":"/home/ndi/sofie/tv-automation-server-core/meteor/.meteor/local/build/programs/server","execPath":"/home/ndi/.meteor/packages/meteor-tool/.1.6.1_4.qkg478.l0i3e++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/bin/node","version":"v8.11.4","argv":["/home/ndi/.meteor/packages/meteor-tool/.1.6.1_4.qkg478.l0i3e++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/bin/node","/home/ndi/sofie/tv-automation-server-core/meteor/.meteor/local/build/main.js","program.json"],"memoryUsage":{"rss":158351360,"heapTotal":114016256,"heapUsed":82087920,"external":23374768}},"os":{"loadavg":[0.97119140625,0.9287109375,0.89697265625],"uptime":334227},"trace":[{"column":18,"file":"module.js","function":"Module._extensions..node","line":681,"method":".node","native":false},{"column":32,"file":"module.js","function":"Module.load","line":565,"method":"load","native":false},{"column":12,"file":"module.js","function":"tryModuleLoad","line":505,"method":null,"native":false},{"column":3,"file":"module.js","function":"Module._load","line":497,"method":"_load","native":false},{"column":17,"file":"module.js","function":"Module.require","line":596,"method":"require","native":false},{"column":18,"file":"internal/module.js","function":"require","line":11,"method":null,"native":false},{"column":48,"file":"/home/ndi/sofie/tv-automation-server-core/meteor/node_modules/bindings/bindings.js","function":"bindings","line":112,"method":null,"native":false},{"column":32,"file":"/home/ndi/sofie/tv-automation-server-core/meteor/node_modules/node-expat/lib/node-expat.js","function":null,"line":4,"method":null,"native":false},{"column":30,"file":"module.js","function":"Module._compile","line":652,"method":"_compile","native":false},{"column":10,"file":"module.js","function":"Module._extensions..js","line":663,"method":".js","native":false},{"column":32,"file":"module.js","function":"Module.load","line":565,"method":"load","native":false},{"column":12,"file":"module.js","function":"tryModuleLoad","line":505,"method":null,"native":false},{"column":3,"file":"module.js","function":"Module._load","line":497,"method":"_load","native":false},{"column":17,"file":"module.js","function":"Module.require","line":596,"method":"require","native":false},{"column":18,"file":"internal/module.js","function":"require","line":11,"method":null,"native":false},{"column":13,"file":"/home/ndi/sofie/tv-automation-server-core/meteor/node_modules/xml2json/lib/xml2json.js","function":null,"line":1,"method":null,"native":false},{"column":30,"file":"module.js","function":"Module._compile","line":652,"method":"_compile","native":false},{"column":10,"file":"module.js","function":"Module._extensions..js","line":663,"method":".js","native":false},{"column":32,"file":"module.js","function":"Module.load","line":565,"method":"load","native":false},{"column":12,"file":"module.js","function":"tryModuleLoad","line":505,"method":null,"native":false},{"column":3,"file":"module.js","function":"Module._load","line":497,"method":"_load","native":false},{"column":17,"file":"module.js","function":"Module.require","line":596,"method":"require","native":false},{"column":18,"file":"internal/module.js","function":"require","line":11,"method":null,"native":false},{"column":18,"file":"/home/ndi/sofie/tv-automation-server-core/meteor/node_modules/xml2json/lib/index.js","function":null,"line":3,"method":null,"native":false},{"column":30,"file":"module.js","function":"Module._compile","line":652,"method":"_compile","native":false},{"column":10,"file":"module.js","function":"Module._extensions..js","line":663,"method":".js","native":false},{"column":32,"file":"module.js","function":"Module.load","line":565,"method":"load","native":false},{"column":12,"file":"module.js","function":"tryModuleLoad","line":505,"method":null,"native":false}],"stack":["Error: The module '/home/ndi/sofie/tv-automation-server-core/meteor/node_modules/node-expat/build/Release/node_expat.node'","was compiled against a different Node.js version using","NODE_MODULE_VERSION 64. This version of Node.js requires","NODE_MODULE_VERSION 57. Please try re-compiling or re-installing","the module (for instance, using `npm rebuild` or `npm install`).","    at Object.Module._extensions..node (module.js:681:18)","    at Module.load (module.js:565:32)","    at tryModuleLoad (module.js:505:12)","    at Function.Module._load (module.js:497:3)","    at Module.require (module.js:596:17)","    at require (internal/module.js:11:18)","    at bindings (/home/ndi/sofie/tv-automation-server-core/meteor/node_modules/bindings/bindings.js:112:48)","    at Object.<anonymous> (/home/ndi/sofie/tv-automation-server-core/meteor/node_modules/node-expat/lib/node-expat.js:4:32)","    at Module._compile (module.js:652:30)","    at Object.Module._extensions..js (module.js:663:10)","    at Module.load (module.js:565:32)","    at tryModuleLoad (module.js:505:12)","    at Function.Module._load (module.js:497:3)","    at Module.require (module.js:596:17)","    at require (internal/module.js:11:18)","    at Object.<anonymous> (/home/ndi/sofie/tv-automation-server-core/meteor/node_modules/xml2json/lib/xml2json.js:1:13)","    at Module._compile (module.js:652:30)","    at Object.Module._extensions..js (module.js:663:10)","    at Module.load (module.js:565:32)","    at tryModuleLoad (module.js:505:12)","    at Function.Module._load (module.js:497:3)","    at Module.require (module.js:596:17)","    at require (internal/module.js:11:18)","    at Object.<anonymous> (/home/ndi/sofie/tv-automation-server-core/meteor/node_modules/xml2json/lib/index.js:3:18)","    at Module._compile (module.js:652:30)","    at Object.Module._extensions..js (module.js:663:10)","    at Module.load (module.js:565:32)","    at tryModuleLoad (module.js:505:12)"],"level":"error","message":"uncaughtException: The module '/home/ndi/sofie/tv-automation-server-core/meteor/node_modules/node-expat/build/Release/node_expat.node'\nwas compiled against a different Node.js version using\nNODE_MODULE_VERSION 64. This version of Node.js requires\nNODE_MODULE_VERSION 57. Please try re-compiling or re-installing\nthe module (for instance, using `npm rebuild` or `npm install`)."}

Thanks for this bug report. There's probably something wrong with some typings, I'll get back to you shortly.

I've pushed a fix onto /develop, let me know it if fixes your issue :)

I don't think the typings issue causes the crash. This bit of the log seems particularly interesting:
"stack":["Error: The module '/home/ndi/sofie/tv-automation-server-core/meteor/node_modules/node-expat/build/Release/node_expat.node'","was compiled against a different Node.js version using","NODE_MODULE_VERSION 64. This version of Node.js requires","NODE_MODULE_VERSION 57. Please try re-compiling or re-installing","the module (for instance, using npm rebuild or npm install)."
It might be that Meteor is using a different node version internally then you are using and if so should be fixed by executing a meteor npm rebuild

ah, you're probably right, @baltedewit, I missed the last line in the error message (the one that counted)..

To add to Balte's answer: If meteor npm rebuild doesn't help, try downgrading your node-version to version 8 (preferably using nvm ) when doing the install.

meteor npm rebuild   did the job.
And as always I forgot rule number one:
Read the full error message.

Thanks :)

Wrong nodejs version. "meteor nom rebuild" fixed it.

Wrong nodejs version. "meteor nom rebuild" fixed it.


Support TLS 1.3 on Apple platforms

Describe the feature
Support for TLS 1.3 on Apple
Use Case
Support for TLS 1.3
Proposed Solution
No response
Other Information
No response
Acknowledgements

[ ] I may be able to implement this feature request
[ ] This feature might incur a breaking change

TODO: Verify S2N can do TLS 1.3 as well.


Norminette fails when their is a space at the bank line after the code

Describe the bug
Norminette fails when their is a space at the bank line after the code
Erroneous code
"Error: Code ended unexpectedly."
Additional infos

OS: Mac
python 2.7:
norminette 3:

Additional context
Add any other context about the problem here.

Hello,
Can you provide an example?

By norm rules, we have to add a blank line after each function, if there are any spaces or tabs on that line, it would fail producing  "Error: Code ended unexpectedly."

This is normal behaviour, read the norm more carefully. A line can never end with spaces or tabulations.
Also when people ask you for an example erroneous code, they expect code, not an error message.

@fifididi A normal behavior of norminette is to produce an error, not fail. The case it quite clear and need no example for one who understands human language too.

If you can't provide example, there is no bug. You managed to poorly ask your question and i can't decipher what's not working.
Have a great day.

Yea, I get it, you have a lot to fix.


Is their a method to show/hide the insert row.

I want the user to see just the current values unless they hit an "add new" button. Is it possible to show/hide the insert row?

It appears this can be accomplish via the option method
 $('.name-charge_table').jsGrid('option', 'inserting', false);

Yes, you are right, it can be done changing this option.

FYI, clearInsert method does not appear to work.  The alternative shown above works fine.

$("#grid").jsGrid("clearInsert");

http://js-grid.com/docs/#clearinsert


search bar fixes

I propose the following fixes to the search bar to improve the UX, especially in terms of keyboard navigation:

When there's no search query (empty search bar), the close button should be disabled and unclickable.
Both the help icon and the close buttons should be visually highlighted when tabbing through them. E. g. if I hit Ctrl + F to focus the search bar and find some todos, I need to navigate to them quickly. Currently I hit Tab a couple of times (is there a better way perhaps?) to get the todos in the list. While tabbing, the help and close buttons are "invisibly selected", which is confusing.
I would also hide the Add as todo button from the search bar when a user selects a saved search from the dropdown. Why would you want to add a saved search as a todo? And, it adds another (in this case, I think, unnecessary) button to tab through to get to the list of todo rows.
Under the saved searches, it seems the notification icon should not be a crossed-out one, as this means "no notifications". Instead, this icon seems to be the right one: https://mui.com/material-ui/material-icons/?query=Notifications&selected=Notifications
Speaking of the notification icon, should it be shown at all if the user has notifications disabled in Preferences? Personally, I don't currently use todo notifications, so the presence of the bell icon is a bit confusing. Does it override global notification preferences?

@ransome1 What do you think?

Under the saved searches, it seems the notification icon should not be a crossed-out one, as this means "no notifications". Instead, this icon seems to be the right one: https://mui.com/material-ui/material-icons/?query=Notifications&selected=Notifications

There is a misconception on how this feature works. It is about suppressing notifications, which match a search filter: https://github.com/ransome1/sleek/wiki/Search-filters#suppressing-notifications
This was a low hanging fruit feature piggybacking the implementation of the search filter function. We can of course still change the logic behind it, since this little feature is not mission critical and most likely not heavily used yet.

I would also hide the Add as todo button from the search bar when a user selects a saved search from the dropdown. Why would you want to add a saved search as a todo? And, it adds another (in this case, I think, unnecessary) button to tab through to get to the list of todo rows.

No problem, should be available in the next release.

When there's no search query (empty search bar), the close button should be disabled and unclickable.

React MUI proposes hiding the element, instead of deactivating it. So I think we should comply to this. However I agree we don't need to leave it present and clickable if there is no content in the search field.

Both the help icon and the close buttons should be visually highlighted when tabbing through them. E. g. if I hit Ctrl + F to focus the search bar and find some todos, I need to navigate to them quickly. Currently I hit Tab a couple of times (is there a better way perhaps?) to get the todos in the list. While tabbing, the help and close buttons are "invisibly selected", which is confusing.

Highlighting on focus has simply been forgotten to implement on my side, should be available in the next release. About the question if there is a better way to do something, I am not sure what exactly you're trying to achieve. If you want to clear the search field, you can alternatively press escape key and if you want to then close/hide the search field, press escape key another time.

@ransome1 Thanks for the detailed response!

About the question if there is a better way to do something, I am not sure what exactly you're trying to achieve.
I'm looking for a keyboard-driven way to focus the first todo row -- preferably from anywhere in the app. Right now the best way I've found is to hit Ctrl+F to focus search, then tab through to the first todo.

@andrei-a-papou I think most of the issues should be covered by: https://github.com/ransome1/sleek/releases/tag/v2.0.9-rc.4
As for the tabbing issue (accessing the list without tabbing through the element between search field and list) I haven't found a proper solution yet. If you have a concrete proposal, feel free to open up a detailed feature request.

There is a misconception on how this feature works. It is about suppressing notifications, which match a search filter:

OK, but as a user, I don't use sleek notifications at all. They are disabled under Preferences, so there should be nothing to suppress, correct? I think from a UX perspective, it's sort of confusing to suddenly discover a specific notification suppression option, when you have notifications generally off.

As for the tabbing issue (accessing the list without tabbing through the element between search field and list) I haven't found a proper solution yet. If you have a concrete proposal, feel free to open up a detailed feature request.

IMHO, a good solution would be implementing #645 and exposing as many commands as possible to be bound to keys/key combos that users can choose. Unfortunately, I'm not skilled in React/Electron, or I would have done it myself.

@andrei-a-papou I think most of the issues should be covered by: https://github.com/ransome1/sleek/releases/tag/v2.0.9-rc.4

Tested, seems to work! Thank you!


Getting a Warning and Fatal error while executing STORM_TEST

Hello Revans,
I am new to Yahoo benchmark , just done with SETUP , On executing STORM_TEST on a single node on the console logs I see WARNING and FATAL error in  logs asbelow : How do I fix this ?
"WARN  o.a.s.s.o.a.z.s.NIOServerCnxn - caught end of stream exception
org.apache.storm.shade.org.apache.zookeeper.server.ServerCnxn$EndOfStreamException: Unable to read additional data from client sessionid 0x155254d0fc6000a, likely client has closed socket
at org.apache.storm.shade.org.apache.zookeeper.server.NIOServerCnxn.doIO(NIOServerCnxn.java:228) [storm-core-0.10.0.jar:0.10.0]"
2016-06-06 16:18:01,565 FATAL Unable to register shutdown hook because JVM is shutting down.

Hello Revans,
I am not sure if this is correct I got rid of the FATAL  by adding shutdownHook="disable" in cluster.xml  in storm.
Please confirm.

That is interesting.  Not really sure why that would happen I have not seen it before.


The app isn't in the repository

I am new to github.  When I click the download button, it doesn't work. Please fix this!!! I'm currently on the new Windows 2020 Pro Max

Issue has been solved. Kindly revert back to repository. Duhh Windows 2020 Pro Max?!?!?!?


Add type usage extractor to the smart sintr job

TBR @emsod This adds a feature extractor for pulling inferred type usage. This can then be used to compute tdf-if ratings for the types in the files, which combined with the object-protocol will form the 'usage discovery model'.
CC @danrubel @sgjesse

Added some comments. Over all looks good to me.


Failed build script is not tracked in fingerprint.

There is a scenario where cargo fails to rebuild when the execution of a build script is interrupted (such as hitting ctrl-c).  There are a variety of ways this can happen, the test below illustrates one way.
The fundamental problem is that the fingerprint does not track enough information about the execution of a build script as a dependency.  #6720 added tracking the invoked.timestamp file, but that is not sufficient.
I've been pondering various ways to fix this, but not loving the options. I would be interested if anyone has any more ideas. Bonus points if both this and #6733 can be fixed. Some options:

#6733 mentions adding the info from  build_script_local_fingerprints, but there are some complications with updating that after the build is done (it would need to do everything that prepare_build_cmd does, too).
Add another file that is written in the fingerprint dir that tracks the completion of running the build script, perhaps with a sequence number bumped each time it is run.
When the build script starts, write invoked.timestamp.start (and delete invoked.timestamp) and then when the build script succeeds, rename it to invoked.timestamp.  I think this should work, but I'm not sure.
(Crazy) Switch to a database for fingerprint tracking to make it easier to track dependencies.

Example
(This currently fails on the last line where the build succeeds when it should fail.)
#[test]
fn script_fails_stay_dirty() {
    let p = project()
        .file(
            "build.rs",
            r#"
                mod helper;
                fn main() {
                    println!("cargo:rerun-if-changed=build.rs");
                    helper::doit();
                }
            "#,
        )
        .file("helper.rs", "pub fn doit() {}")
        .file("src/lib.rs", "")
        .build();

    p.cargo("build").run();
    p.change_file("helper.rs", r#"pub fn doit() {panic!("Crash!");}"#);
    p.cargo("build")
        .with_stderr_contains("[..]Crash![..]")
        .with_status(101)
        .run();
    // There was a bug where this second call would be "fresh".
    p.cargo("build")
        .with_stderr_contains("[..]Crash![..]")
        .with_status(101)
        .run();
}

Jeez we just can't seem to get this right :(. I really would start seriously considering larger scale revamps because it's be clear that ever since inception we haven't been able to ever produce a bug-free system where incremental works correctly in all cases...
Is the problem here that there's still a file on the filesystem which indicates a successful run, and so during the failing step above Cargo correctly realizes it doesn't need to rebuild the build script itself but incorrectly reuses the old successful output assuming the new binary succeeded?
I sort of forget how this is solved for crates, but I vaguely remember us deleting files that is recognized specially (this could be totally wrong though). Do you recall off the top of your head how that works for normal crates?

still a file on the filesystem

Correct. The build script fingerprint only tracks the rerun-if statements, and this example it is literally just build.rs.  Thinking about it more, perhaps it is sufficient to add the fingerprint of the compilation of the build script?  I'm going to experiment with that, it might be sufficient.  I think the issue in #6720 would still broken here, though.
For context, this was discovered by @eddyb working on the gll crate which has a number of modules in the build script and he was hitting the OOM killer (I think).  gll could add rerun-if-changed lines for each file, but I don't think it is reasonable to require that for normal rust modules.

how that works for normal crates

A normal crate would catch this from the dep-info file.  The running of a build script is the odd one out. It requires build script authors to be extremely diligent in tracking all inputs, and I think we can ease that a little.  I suspect I'm missing something, though.

Hm ok, so it sounds like the build script execution is buggily not tracking the build script itself. In that one of the inputs to the build script execution should be the binary of the build script itself, which we should recognize has changed from the previous successful run which triggers a run until it succeeds.
I do remember we fixed a number of issues like this by adding dependency edges from packages to their dependencies (in the fingerprints), so maybe we're just missing that for build script execution?


Correct OpenLineage spec

Fix the references in current OpenLineage spec such that it will reflect correct references to the child Elements under each facets of OpenLineage event spec. For example, the current spec defines DataSet facets as such:
    "Dataset": {
      "type": "object",
      "properties": {
        "namespace": {
          "description": "The namespace containing that dataset",
          "type": "string",
          "example": "my-datasource-namespace"
        },
        "name": {
          "description": "The unique name for that dataset within that namespace",
          "type": "string",
          "example": "instance.schema.table"
        },
        "facets": {
          "description": "The facets for this dataset",
          "type": "object",
          "additionalProperties": {
            "$ref": "#/$defs/DatasetFacet"
          }
        }
      },
      "required": [
        "namespace",
        "name"
      ]
    },

But, because of that, the facets section does not contain what kind of child properties may be added to it, so the user does not have ways to determine what is legal and what is not legal.
The solution is to add a more definite child facets as such:
    "Dataset": {
      "type": "object",
      "properties": {
        "namespace": {
          "description": "The namespace containing that dataset",
          "type": "string",
          "example": "my-datasource-namespace"
        },
        "name": {
          "description": "The unique name for that dataset within that namespace",
          "type": "string",
          "example": "instance.schema.table"
        },
        "facets": {
          "description": "The common facets for this dataset",
          "type": "object",
          "allOf": [
            { "$ref": "facets/ColumnLineageDatasetFacet.json" },
            { "$ref": "facets/DatasourceDatasetFacet.json" },
            { "$ref": "facets/DataQualityAssertionsDatasetFacet.json" },
            { "$ref": "facets/LifecycleStateChangeDatasetFacet.json" },
            { "$ref": "facets/OwnershipDatasetFacet.json" },
            { "$ref": "facets/SchemaDatasetFacet.json" },
            { "$ref": "facets/StorageDatasetFacet.json" },
            { "$ref": "facets/SymlinksDatasetFacet.json" },
            { "$ref": "facets/DatasetVersionDatasetFacet.json" }
          ],
          "additionalProperties": {
            "$ref": "#/$defs/DatasetFacet"
          }
        }
      },
      "required": [
        "namespace",
        "name"
      ]
    },

So that the spec files contain the proper referenced elements.

@collado-mike , what do you think? This may involve changes in the current OL spec, so wanted to get your feedback on this as well.

I don't think this does what you think it does. From https://swagger.io/docs/specification/data-models/oneof-anyof-allof-not/#allof (bold added for emphasis)

allOf takes an array of object definitions that are used for independent validation but together compose a single object. Still, it does not imply a hierarchy between the models. For that purpose, you should include the discriminator. To be valid against allOf, the data provided by the client must be valid against all of the given subschemas.

That is, you've defined a facet that must have all of the properties defined in each of the facet schemas you included.
The DatasetFacet $ref should be enough to indicate to users what facets are valid types for this field. It doesn't tell them which facets implement that type, it's true. IDEs can do a good job of that, as the code generator does generate a super class for DatasetFacet and each implementation inherits from that super class. Thus the IDE can show all subclasses of the DatasetFacet type with a single keyboard shortcut. This is less helpful in languages other than Java, I admit. But I think the solution there is better code generators, not updates to the spec.

Comment in different issue related to a discussion above: https://github.com/OpenLineage/OpenLineage/issues/1190#issuecomment-1301761985

I don't think this does what you think it does. From https://swagger.io/docs/specification/data-models/oneof-anyof-allof-not/#allof (bold added for emphasis)

allOf takes an array of object definitions that are used for independent validation but together compose a single object. Still, it does not imply a hierarchy between the models. For that purpose, you should include the discriminator. To be valid against allOf, the data provided by the client must be valid against all of the given subschemas.

That is, you've defined a facet that must have all of the properties defined in each of the facet schemas you included.
The DatasetFacet $ref should be enough to indicate to users what facets are valid types for this field. It doesn't tell them which facets implement that type, it's true. IDEs can do a good job of that, as the code generator does generate a super class for DatasetFacet and each implementation inherits from that super class. Thus the IDE can show all subclasses of the DatasetFacet type with a single keyboard shortcut. This is less helpful in languages other than Java, I admit. But I think the solution there is better code generators, not updates to the spec.

Hey, thanks for the comments - I see this from the perspective of how 'useful' the spec is, not only for tools like IDE, but for human users who need to understand the spec. It is true that technically, having the ref of DatasetFacet is legitimate, and I'm sure it is for the code generator as well.
However, I do want our spec to do more, and be more, so my issue is that when I tried to go through generating open API documentation from our openlineage spec, using tools like redoc-cli, the doc was not really that useful to the users, since under the facets, for example, user couldn't see the list of valid facets that can be available for run, job, input, and output. All they saw was DatasetFacets, or JobFacets, which were too generic for them to properly learn the specifics.
This is actually in-line with the work related to improving our OL documentation - and one area that Ross and I agreed was that we need to, perhaps, use redoc-cli for our next openlineage openapi doc, and believe having these updates to the spec would go a long way.

Sure, that goal makes sense. Unfortunately, your spec changes aren't going to accomplish that, per the OpenAPI documentation I linked to. We need another way of generating more comprehensive documentation from the spec.

Sure, that goal makes sense. Unfortunately, your spec changes aren't going to accomplish that, per the OpenAPI documentation I linked to. We need another way of generating more comprehensive documentation from the spec.

I see, and am open to anything better. This issue is not a PR, so I'd be happy to see if we could highlight any shortcomings of the current OL spec, and make necessary changes that will have a more correct representation of the spec. If there's anybody who wants to take a poke at this, more than happy for them to also chime in.


[main] Upgrade to latest dependencies

Cron -knative-prow-robot
/cc knative/operations-wg-leads
/assign knative/operations-wg-leads
Produced by: knative-extensions/knobots/actions/update-deps

/override "Code Style / style / Golang / Lint (pull_request)"

/override "style / Golang / Lint"


How to Solve This (Value cannot be null. Parameter name: property)

I'm trying To Compile a test App With https://github.com/quartznet/quartznet
after Compiling when try to run the Compiled app I got below exception! idk What should i put in the rd.xml to make it run successfully! :/

Unhandled Exception: System.TypeInitializationException: A type initializer threw an exception. To determine which type, inspect the InnerException's StackTrace property.
---> System.ArgumentNullException: Value cannot be null. Parameter name: property
at System.Linq.Expressions.Expression.Property(Expression, PropertyInfo) + 0x181
at TestApp!+0x12868b5
at TestApp!+0x1286712
at TestApp!+0x15003cd
at TestApp!+0x305d41
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x20
at TestApp!+0x88027a
at TestApp!+0x8ff08e
at System.Linq.Expressions.Interpreter.LightLambda.Run(Object[]) + 0x82
at TestApp!+0xf10363
at Quartz.Logging.LogProvider.GetLogger(String) + 0x14
at TestApp!+0x7cbe74
at TestApp!+0xd69a93
--- End of inner exception stack trace ---
at TestApp!+0xd69a8a
at TestApp!+0xd6995d
at Quartz.Impl.StdSchedulerFactory.get_Log() + 0x9
at Quartz.Impl.StdSchedulerFactory.Initialize() + 0x2b4
at Quartz.Impl.StdSchedulerFactory.d__69.MoveNext() + 0x5f
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x20
at TestApp!+0xd6b0ca
at TestApp!+0xd6b004
at TestApp.Models.SchedulerManager.d__4.MoveNext() + 0xd4

the rd.Xml for this Lib Defined as Below

<Assembly Name="Quartz" Dynamic="Required All">

<Type Name="Quartz.Impl.StdSchedulerFactory" Dynamic="Required All"/>
<Type Name="Quartz.Simpl.RAMJobStore" Dynamic="Required All"/>
<Type Name="Quartz.Simpl.TaskSchedulingThreadPool" Dynamic="Required All"/>
<Type Name="Quartz.Core.QuartzScheduler" Dynamic="Required All"/>
<Type Name="Quartz.Core.QuartzSchedulerThread" Dynamic="Required All"/>
<Type Name="Quartz.Core.ErrorLogger" Dynamic="Required All"/>
<Type Name="Quartz.Core.SchedulerSignalerImpl" Dynamic="Required All"/>
</Assembly>

and when using     <IlcArg Include="--stacktracedata" />

Unhandled Exception: System.TypeInitializationException: A type initializer threw an exception. To determine which type, inspect the InnerException's StackTrace property.
---> System.ArgumentNullException: Value cannot be null. Parameter name: property
at System.Linq.Expressions.Expression.Property(Expression, PropertyInfo) + 0x181
at System.Runtime.CompilerServices.CallSiteBinder.Stitch[T](Expression, CallSiteBinder.LambdaSignature1) + 0x115    at System.Runtime.CompilerServices.CallSiteBinder.BindCore[T](CallSite1, Object[]) + 0x92
at TestApp!+0x150055d
at System.InvokeUtils.CallDynamicInvokeMethod(Object, IntPtr, Object, IntPtr, IntPtr, Object, Object[], BinderBundle, Boolean, Boolean, Boolean) + 0x211
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x20
at System.Linq.Expressions.Interpreter.MethodInfoCallInstruction.Run(InterpretedFrame) + 0x17a
at System.Linq.Expressions.Interpreter.Interpreter.Run(InterpretedFrame) + 0x2e
at System.Linq.Expressions.Interpreter.LightLambda.Run(Object[]) + 0x82
at TestApp!+0xf104f3
at Quartz.Logging.LogProvider.GetLogger(String) + 0x14
at Quartz.Impl.StdSchedulerFactory..cctor() + 0x34
at System.Runtime.CompilerServices.ClassConstructorRunner.EnsureClassConstructorRun(StaticClassConstructionContext*) + 0xd3
--- End of inner exception stack trace ---
at System.Runtime.CompilerServices.ClassConstructorRunner.EnsureClassConstructorRun(StaticClassConstructionContext*) + 0xca
at System.Runtime.CompilerServices.ClassConstructorRunner.CheckStaticClassConstructionReturnGCStaticBase(StaticClassConstructionContext*, Object) + 0xd
at Quartz.Impl.StdSchedulerFactory.get_Log() + 0x9
at Quartz.Impl.StdSchedulerFactory.Initialize() + 0x2b4
at Quartz.Impl.StdSchedulerFactory.d__69.MoveNext() + 0x5f
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x20
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0xba
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x44
at TestApp.Models.SchedulerManager.d__4.MoveNext() + 0x102

any help to get ride of this please!

and when using <IlcArg Include="--stacktracedata" />

How does your CSPROJ look like? The stack trace data should be enabled by default unless it was explicitly disabled. Did you turn off any compilation options?

and when using <IlcArg Include="--stacktracedata" />

How does your CSPROJ look like? The stack trace data should be enabled by default unless it was explicitly disabled. Did you turn off any compilation options?

thanks to @wieslawsoltes I'm using it like so
<!-- https://github.com/dotnet/corert -->   <ItemGroup Condition="'$(CoreRT)' == 'True'">     <RdXmlFile Include="rd.xml" />     <!--Include stack trace data -->     <IlcArg Include="--stacktracedata" />      <PackageReference Include="Microsoft.DotNet.ILCompiler" Version="1.0.0-alpha-*" />   </ItemGroup>

Can you paste the contents of the *.ilc.rsp file from obj\Release\netcoreapp3.1\win-x64\native? There should be a directory with that name in your project directory.

Can you paste the contents of the *.ilc.rsp file from obj\Release\netcoreapp3.1\win-x64\native? There should be a directory with that name in your project directory.

sorry I have given up on this and removed the Project


ModuleNotFoundError: No module named 'openai.types.beta.threads.message_content'

when running "python3 run.py --verbose True --config examples/example_cn_agent_setup.json"
prompt：
Traceback (most recent call last):
File "/mnt/workspace/SalesGPT/run.py", line 10, in
from salesgpt.agents import SalesGPT
File "/mnt/workspace/SalesGPT/salesgpt/agents.py", line 17, in
from litellm import acompletion
File "/opt/conda/envs/salesgpt/lib/python3.10/site-packages/litellm/init.py", line 761, in
from .llms.openai import OpenAIConfig, OpenAITextCompletionConfig, MistralConfig
File "/opt/conda/envs/salesgpt/lib/python3.10/site-packages/litellm/llms/openai.py", line 28, in
from ..types.llms.openai import *
File "/opt/conda/envs/salesgpt/lib/python3.10/site-packages/litellm/types/llms/openai.py", line 12, in
from openai.types.beta.threads.message_content import MessageContent
ModuleNotFoundError: No module named 'openai.types.beta.threads.message_content'

delete openai and install the newest version, helped for me
pip uninstall openai
pip install openai

Thank you for your reply.
But after executing the above code, the following prompt appears：ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
salesgpt 0.1.2 requires openai==1.7.0, but you have openai 1.30.1 which is incompatible.
In addition, when running "python3 run.py --verbose True --config examples/example_cn_agent_setup.json" ，the following prompt appears：Traceback (most recent call last):
File "/mnt/workspace/SalesGPT/run.py", line 10, in
from salesgpt.agents import SalesGPT
File "/mnt/workspace/SalesGPT/salesgpt/agents.py", line 27, in
from salesgpt.tools import get_tools, setup_knowledge_base
File "/mnt/workspace/SalesGPT/salesgpt/tools.py", line 4, in
import boto3
ModuleNotFoundError: No module named 'boto3'

安装 boto3

Hey @uptang14 has the issue been fixed? Hopefully the dependency improvements should have fixed this. :)


Character costume clearing during the 2nd knife piece area

I've noticed this is an issue with every character mod I've seen so it might be a limitation of modding itself, but the character costume clears during the 2nd knife piece area in the mines.
Thankfully it comes back afterwards but hopefully there's a way to fix it.

It has being reported as a bug on the Repentance API. I cannot currently fix this. Here

ahhh
hoping that gets fixed eventually then


Recommended way of click and hover actions for each part

Hi,

I would like to add some hover action to display more data
click on a section/ part and do eg. navigation. Therefore I need to access the data.

Whats your recommended way to do so?
Thx.

yes need this feature so that on click of any section of the funnel we can navigate to data


hideMediaControl: false is not working properly

The controls are hidden on page load.
Only after a first mouse over the player, the controls are shown.
It means that if the user is not moving the mouse, she/he may not see the player in the use case of audio.

related to #207

@whadar can you try with master branch and tell me if works for you?


Swift51 support

Add unit tests for SwiftyRequest and SwiftyRequestCodable

I discussed the removal of Swift3, I was told iot is already removed AFAIK so I added that to make simpler the maintenance of the tests. Will discuss in mailing list.

I helped Andrea to rework and reintroduce 3.2.1 please confirm we can merge.


Add variable to stop creation of admin account

Adds option to disable admin account creation with the installer

Is this new option discoverable, either in the docs on in the installer help?

No, I need it mostly for repeatable e2e testing


what's the way to set verbose logging(debugging) of all the acvitites?

the env NODE_DEBUG=request doesn't work for CRI,
need logging of which sending data and receiving.
since capturing full-size page scereenshots hangs for me
const {data} = await Page.captureScreenshot();

NODE_DEBUG=request is a request-only feature (which I'm not using), try with NODE_DEBUG=net,http.
Besides, If you post the code that hangs I can take a look at it.

it's just ordinary snippet of codes, only full size capturing hangs
const CDP = require('chrome-remote-interface');

module.exports = takeScreenshot;

async function sleep(delay) {
  return new Promise((ok, fail) => {
    setTimeout(ok, delay * 1000);
  });
}

async function takeScreenshot(url, options, instance) {
  const params = { host: instance.hostname, port: instance.port, secure: instance.isSecure };

  let tab;

  try {
    tab = await CDP.New(params);
    const client = await CDP(Object.assign(params, {tab}));

    client.on('error', err => {
      throw err;
    });

    client.on("disconnect", _ => {
      console.log("disconnect");
    });

    const {DOM, Emulation, Network, Page, Security} = client;

    await Page.enable();
    await Security.enable();

    await Security.setOverrideCertificateErrors({override: true});
    await DOM.enable();
    await Network.enable();

    if (options.userAgent) {
      await Network.setUserAgentOverride({userAgent: options.userAgent});
    }

    const deviceMetrics = {
      width: options.viewportWidth,
      height: options.viewportHeight,
      deviceScaleFactor: 0,
      mobile: options.mobile,
      fitWindow: false,
    };

    await Emulation.setDeviceMetricsOverride(deviceMetrics);
    await Emulation.setVisibleSize({width: options.viewportWidth, height: options.viewportHeight});

    await Page.navigate({url});

    await Page.loadEventFired();

    if (options.delay) {
      await sleep(options.delay);
    }

    if (options.fullPage) {
      const {root: {nodeId: documentNodeId}} = await DOM.getDocument();
      const {nodeId: bodyNodeId} = await DOM.querySelector({
        selector: 'body',
        nodeId: documentNodeId,
      });
      const {model: {height}} = await DOM.getBoxModel({nodeId: bodyNodeId});

      await Emulation.setVisibleSize({width: options.viewportWidth, height: height});

      await Emulation.forceViewport({x: 0, y: 0, scale: 1});
    }

    const {data} = await Page.captureScreenshot({format: options.format, quality: options.quality});

    await CDP.Close(Object.assign(params, {id: tab.id}));

    return data;
  } catch(err) {
    if (tab) {
      await CDP.Close(Object.assign(params, {id: tab.id}));
    }
    throw err;
  }
}

also the tracing
profile-1496981925524.devtools.trace.txt

hangs issue was due of memory limitation, currently running on 512mb of ram vps,
i run it with the options, but didn't help
/usr/bin/google-chrome-stable \
            --disable-gpu \
            --disable-software-rasterizer \
            --enable-logging \
            --v=99 \
            --headless \
            --hide-scrollbars \
            --no-sandbox \
            --deterministic-fetch \
            --js-flags='--max-old-space-size=500' \
            --remote-debugging-address=<IP_ADDRESS> \
            --remote-debugging-port=9222 \
            --user-data-dir=/data

tried with --single-process & --no-zygote no luck, what's your advices?

I think this is somewhat similar to #147, tl;dr triggered by using docker with defaults setting thus with limited available memory.
If the available memory is really your problem here, I'm not aware of any flags that can help you, my only advice is obviously to provide more memory to the VPS or change the environment if that's not possible.
You may want to ask this in the Google Group.


attempting to connect to a cam5 TM1 instance hosted on Azure

Describe what did you try to do with TM1py
Describe the script you ran and what it is supposed to do.
attempting connection with TM1service
script
from TM1py import TM1Service
with TM1Service(address="", port=19308, ssl=True, namespace="LDAP", gateway="http://ctccrdev01.ct.hayne.cloud/ibmcognos/bi/v1/disp", verify=True) as tm1:
print(tm1.server.get_product_version())
End script
Describe what's not working the way you expect
Didn't get the expected result? Describe:

The result you expected.

Attempting to connect to a TM1 instance that is hosted on our 3rd party support provider in Azure, Expected connection to exist and Server version to be returned
Additional context
config file "
[TM1S]
AllowSeparateNandCRules=T
CAMPortalVariableFile = portal/variables_TM1.xml
ClientCAMURI = http://ctccrdev01.ct.#####.cloud/ibmcognos/bi/v1/disp
ServerCAMURI = http://ctccrdev01.ct.#####.cloud:9300/p2pd/servlet/dispatch
ClientMessagePortNumber = 19307
ClientPingCAMPassport = 43200
ClientPropertiesSyncInterval=180
IntegratedSecurityMode = 5
AdminHost=localhost
ServerName=CXMD
PortNumber = 19306
HTTPPortNumber = 19308
Protocol=tcp
UseSSL = T
Language = ENG
DistributedPlanningOutputDir = ./tunit
IdleConnectionTimeOutSeconds=9010
MaximumCubeLoadThreads= 5
DataBaseDirectory=F:\TM1DATA\CXMD\DATA
LoggingDirectory=F:\TM1DATA\CXMD\LOGS
RawstoreDirectory=F:\TM1DATA\CXMD\RAW
AuditLogMaxFileSize= 100 MB
AuditLogOn=T
AuditLogUpdateInterval=60
ParallelInteraction=T
#PerformanceMonitorOn=T
PersistentFeeders=T
ProgressMessage=True
GroupsCreationLimit=400 "
end config file
If you encounter an error, please add the error message and the stack trace
error code
C:\Users\Jon.Wilson\PycharmProjects\pythonProject1\venv\Scripts\python.exe C:/Users/Jon.Wilson/PycharmProjects/pythonProject1/venv/connect.py
Traceback (most recent call last):
File "C:\Users\Jon.Wilson\PycharmProjects\pythonProject1\venv\connect.py", line 3, in
with TM1Service(address="", port=19308, ssl=True, namespace="LDAP", gateway="http://ctccrdev01.ct.hayne.cloud/ibmcognos/bi/v1/disp", verify=True) as tm1:
File "C:\Users\Jon.Wilson\PycharmProjects\pythonProject1\venv\lib\site-packages\TM1py\Services\TM1Service.py", line 15, in init
self._tm1_rest = RestService(**kwargs)
File "C:\Users\Jon.Wilson\PycharmProjects\pythonProject1\venv\lib\site-packages\TM1py\Services\RestService.py", line 201, in init
self._start_session(
File "C:\Users\Jon.Wilson\PycharmProjects\pythonProject1\venv\lib\site-packages\TM1py\Services\RestService.py", line 353, in _start_session
token = self._build_authorization_token(
File "C:\Users\Jon.Wilson\PycharmProjects\pythonProject1\venv\lib\site-packages\TM1py\Services\RestService.py", line 472, in _build_authorization_token
return RestService._build_authorization_token_cam(user, password, namespace, gateway, verify)
File "C:\Users\Jon.Wilson\PycharmProjects\pythonProject1\venv\lib\site-packages\TM1py\Services\RestService.py", line 493, in _build_authorization_token_cam
raise RuntimeError(
RuntimeError: Failed to authenticate through CAM. HTTP response does not contain 'cam_passport' cookie
Process finished with exit code 1
end error code

Hi @JonChrista,
this is an issue, that is been reported a few times in the past. Unfortunately, I haven't experienced the situation myself so I can not confidently say what resolves it.
Maybe start looking into these 3 suggestions:

@MaaYuu has suggested a solution here to change the configuration for the CAM Gateway:
https://github.com/cubewise-code/tm1py/issues/222#issuecomment-620300563

You can access the URL manually and take the CAM passport from the browser cookies. Once you have the CAM passport, you can instantiate the TM1Service like this:

with TM1Service(address=address, port=port, ssl=ssl, cam_passport=passport) as tm1:
    print(tm1.server.get_server_name())

You can automate the above manual process with selenium. Python can use chrome to access the URL and grab the cookie. @AlexanderDvoynev discusses a solution here:
https://github.com/cubewise-code/tm1py/issues/124
The solution is a bit heavy, but it works.

My preferred solution would be 1. We have heard from other users that configuration on the Cognos Gateway can resolve this issue.
Please let us know how it goes!

@JonChrista were you able to resolve the issue yet?

Issue resolved, using incorrect Namespace
working code
with TM1Service(address="10.xx.xx..xx",
port=19308, ssl=True,
namespace="AD",
gateway="http://###############.cloud/ibmcognos/bi/v1/disp",
) as tm1:
Thanks for the advice Marius
Regards Jon


Thanks for this!

Would really love to see the atomic stuff. I am trying to get my head around this working on some stuff on the RPI4 and this has been helpful.

You're welcome. I did eventually want to continue with something more complete, but https://gitlab.freedesktop.org/daniels/kms-quads became a pretty good example to point people at for atomic specifically.

I did find that one and with a few tweaks (disabling VT) it does work on the RPI4 so will be digging into that :)


Improve doxygen documentation for AzureIoTHubClient_SubscribeCommand

From customer feedback:
I think a tiny bit of extra explanation for AzureIoTHubClient_SubscribeCommand() would be very helpful on this page: https://azure.github.io/azure-iot-middleware-freertos/azure__iot__hub__client_8h.html

Fixed.
Thanks,
Azure IoT SDK Team.


[veda-binder] Update the underlying infra

This is for https://github.com/2i2c-org/infrastructure/issues/4576

I may have broken this now as the build pod is no longer able to connect to the docker socket
Events:
  Type     Reason       Age                From               Message
  ----     ------       ----               ----               -------
  Normal   Scheduled    79s                default-scheduler  Successfully assigned binder/build-binder-2dexamples-2drequirements-55ab5c-505-2c to ip-192-168-30-60.us-west-2.compute.internal
  Warning  FailedMount  15s (x8 over 79s)  kubelet            MountVolume.SetUp failed for volume "docker-socket" : hostPath type check failed: /var/run/binder-binder/docker-api/docker-api.sock is not a socket file

My problems above seem to be caused by trying to add the 2i2c:node-purpose tag - I don't know why because tags should just be at the AWS-level, not the k8s level. But I reverted my attempts and the binder works again now. So I'm going to merge this as-is.

Currently build pods are not being scheduled on the binder nodegroup. I think the node selector and toleration need to be added to the section below, but I don't know what the appropriate key is. I've tried extraTolerations, extra_tolerations, and tolerations - none of which worked.
https://github.com/GeorgianaElena/pilot-hubs/blob/263fc911b6ff5da4ed3cd22c244d2e00304248de/config/clusters/nasa-veda/binder.values.yaml#L111-L115


Tabel cell - vertical alignment fix

Description
I have added a table with input field example to Storybook, this should help to document the pattern which first highlighted the issue. The fix is a simple line of css but I wanted to add the example to get some design eyes on the pattern to make sure we are doing it right. (cc @alexcanning)
Fixes # #108

Checklist:

[x] The commit messages follow the convention for this project
[ ] I have provided an adequate amount of test coverage
[ ] I have added the functionality to the test app
[x] I have provided a story in storybook to document the changes
[ ] I have provided documentation in the notes section of the story
[ ] I have added any new public feature modules to public-api.ts
[ ] I have linked the new component to adobe DSM (if appropriate)

Looks good to me!


avoid plot init twice

When setting both dataset and options, the onOptionsChanged will act after the onDatasetChanged, and the plot will init twice, and this will cause the callback method will be called twice.

Nice catch! Thanks! :+1:
I'm cutting a release shortly.


Game plan / initial roadmap

Excited about collaborating on this @melchoyce!
What are your initial thoughts for what the block will do? Show recent donations?

I'm thinking:

The initial view when you add the block is a placeholder that takes a campaign's ActBlue donation URL
When you enter the URL, the block will fetch and load their current donation increments
You should be able to edit or delete those increments, and add new increments
Quick toolbar options should be:
Align left, center, center
Maybe a full-width option?

Might also be cool to create a custom URL parameter for tracking.

Once you add a url:

Adding a new donation amount:

When you enter this, it should:

Create a new custom amount that will pre-fill in ActBlue when they click the button
Add another blank button after it

Note: Blank buttons won't be rendered on the front-end, or when you don't have the block selected.
Deleting a button:

These should maybe be child blocks?
Unselected

Ok! Seems simple enough. I'll dig into their documentation and then come up with a development plan.
Do you have an example ActBlue campaign page we can use?

ActBlue is recommending https://secure.actblue.com/donate/dccc-1, haha, so let's just go with that.

Thanks @melchoyce, @raquelmsmith
Surely, dig into this stuff :relaxed:

hi!
so a few hints: all you really need is the form name, which would be dccc-1 for that DCCC link, then you can form an URL with  https://secure.actblue.com/donate/${formName}.
we also have some nice params: amount=${amountInDollars} will prefill the form with whatever link they clicked. we do have refcode=gutenwebsite, which will let candidates see where the donations come from. i also like amounts=5,10,25, which sets the values of the buttons, so you can match them with the website.
i don't think you particularly need to scrape actblue for any of this?

Thanks for the hints @samuelcole! Does this info live in any documentation anywhere? I spent about 10 mins in the ActBlue docs last night and didn't see these params as options.

sorry about that!
https://support.actblue.com/tutorial#reference-codes
there isn't a more technical list of params anywhere, sadly

Ok, did some looking 👀 into this today. Initial dev gameplan:

Bootstrap setup with create-guten-block
Add placeholder view
For now, this won't scrape the page for preset donation amounts
Show a few basic donation amounts ($10, $50, $100) and link those up to the page
set the refcode to the website name using refcode=
set the amount to the button amount using amount=
Enable adding new buttons
Enable deleting existing buttons

Any thoughts on this? Specifically, is does anyone here have any preference for or against using create-guten-block for setup?

That sounds like a great game plan!
I've heard good things about create-guten-block, so let's give it a try.

@melchoyce yeah I used create-guten-block and it works fine :+1:


Show instructions for turns onto oneway streets

Fixes #1048.
The idea of this PR is that we show an instruction, even if the turn is the only viable turn, if there is another potential (but forbidden) turn and if the turn is not a "follow road/slight turn".
The idea is that we don't see instructions when entering motorways, because these turns are usually only slight turns, but that we see instructions when turning onto a separated lane oneway as described in #1048.
One situation would be this, but there are plenty.
So far the cases I looked at, look good. So far it feels like a good improvement. But I didn't perform too many tests yet.

Thanks!


Make sure the same question and targetperson is not triggered multiple times

Sometimes it happens that the same person randomly chosen multiple times. Same with questions. It would be better to remember which persons and questions have been triggered recently, so that they do not get triggered for a while.

This has been fixed by implementing a weighed random for triggering users and also for questions.


spike: collecting logs and allowing querying

Description
how to use:

run docker-compose -f docker-compose.loki.yml up -d in docker_rig
start tari_launchpad
start any container from launchpad
see logs under http://localhost:3100/loki/api/v1/query_range?query={job="logstash"}&start=1653823389381999872

Motivation and Context
#206
this can allow our backend to provide an api endpoint to frontend for log querying (LogQL queries from frontend, based on labels setup in logstash)
How Has This Been Tested?
??

closing, we will not use logspot/logstash, since the files are discoverable, they will be scraped with promtail and loki


Fix resource leak bug

Description (required)
This patch fixes a potential resource leak bug in the event that an exception is thrown during the copy operation

Thanks for your contribution! For the sake of reference, could you kindly clarify how you came across this resource leakage issue ? 🤔

we investigated open-source projects to see if the projects contain code that is similar to (or reused from) Stack Overflow and whether the code on Stack Overflow underwent any bug or security fixes. We found that the code in this method is somewhat similar to the one in the first version of this answer. The issue was subsequently fixed in the second version, however, the fix is not reflected in this method.
So this PR is a way of notifying about the issue

@sivaraam I updated the PR to incorporate your comments. Can you please take another look?

Looks great. Thank your for your contribution!


HHH-16279 Hibernate ORM with hibernate.hbm2ddl.import_files_sql_extractor = multi-line fails to process import.sql containing only comments

https://hibernate.atlassian.net/browse/HHH-16279
The patch seems to make sense, though I wouldn't be able to tell you why the parser worked fine with an empty file before... There's probably some early check that's not part of the grammar.

Merged, thanks

Grr was in the process of squashing and merging ;)

Sorry :shrug:

No problem.  Just apply it to 6.2 branch as well please.
On Tue, Mar 14, 2023 at 11:02 AM Yoann Rodière @.***>
wrote:

Sorry 🤷
—
Reply to this email directly, view it on GitHub
https://github.com/hibernate/hibernate-orm/pull/6228#issuecomment-1468382296,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABZIE7RRJUZOQU3JFWZYVTW4CJCBANCNFSM6AAAAAAVWOMBBE
.
You are receiving this because your review was requested.Message ID:
@.***>

Right. Done.


Fetch vertex by key value - low performance after addEdge operation

OrientDB Version: TP3 3.0.17
Java Version: 1.8.0_111
OS: Windows 7 Enterprise
Expected behavior
Time to fetch vertex by key value was not affected by other operations in OrientDB 2.2.12 Graph API. The fact that the fetch-vertex operation was immediatly after an add-edge operation did not significantly worsen the performance of the former.
It was expected that the same occured in OrientDB 3.0.17 Tinkerpops 3 implementation.
Actual behavior
Tests were carried out where 5 records of a particular class were fetched in a loop 100,000 times by using an indexed key.

In ODB 2.2.12 the average fetch time per record was ~0.5ms
In ODB 3.0.17 TP3 the average fetch time per record was ~0.25ms

Additional tests were then performed to see the impact of add-edge operations on the fetch-vertex operations (see steps to reproduce). The results were:

In ODB 2.2.12 the avergage fetch time per rectord retrieved after an add-edge operation was ~0.6ms
In ODB 3.0.17 TP3 the average fetch time per record retrieved after an add-edge operation was ~40ms (that is, almost 200 times slower than expected!)

Steps to reproduce

Define class "A" with indexed property "property" (index "A.property")

Define edge "EdgeA"

Create 1,000,000 instances of A

Test 1: Just fetch-vertex operations:

-- Fetch 5 A vertices by their "A.property" valule in a loop 100,000 times and get average fetch time per vertex
-- In OrientDB 2.2.12 vertices are fetched with graph.getVertices("A.property", value).iterator().next();
-- In OrientDB 3.0.17 TP3 vertices are fetched with:
--- String query  = "SELECT FROM A WHERE property = ?";
--- graph.querySql(odbSqlSelection, value).stream().map(gr -> gr.getVertex().get()).findFirst().orElse(null);
-- The results show that OrientDB 3.0.17 TP3 gets vertices faster (0.25ms vs 0.5ms)

Test 2:  Fetch vertices after add-edge:

-- Create three sets S1, S2, S3 of 1,000 "property" values each
-- In a 1,000 size loop
--- Using property value from S1 fetch vertex v1
--- Using property value from S2 fetch vertex v2
--- Add edge v1.addEdge("EdgeA", v2)
--- Using property value from S3 fetch vertex v3
-- In OrientDB 2.2.12 all three vertices were fetched in ~0.6ms
-- In OrientDB 3.0.17 TP3, v1 & v2 were fetched in ~0.3ms & v3 in ~40ms

I am also facing this issue too.

Hi guys, please let me know if this issue still actual I will work on it.


Allowed for non semver InformationalVersion.

Silently ignores when not a semver compliant version.
Fixes #1133

thx


Added GetWindowRefreshRate

People to my knowledge were unable to get the refresh rate of the application before, if they were able to before then it should probably be move to the system settings as I couldn't find it there and it should be there. Thus I added a function named: CP_System_GetWindowRefreshRate that takes nothing and return a float representing the refresh rate of the monitor. This would allow users who make their applications use DeltaTime instead of frame counts to set the frame rate of their application so that it may be smoother.
@AEllinger suggested making the default framerate be 60FPS, I decided to change this but if you want that reverted just let me know! As I can definitely see not wanting to break any projects in progress.

Cherry picked the refresh rate and FPS updates into PR #35.
Thanks @NovaSmoof!


Change camera matrix from local to world.

We should use world transform instead of local to ensure we are getting world space rotation.

We can always just request a standard 4x4 transform matrix or 3x3 transform matrix (and remove the camera) and then it's up to the user to decide which matrix to provide. This is probably the safest solution as it won't break if camera's properties change. It's how I'm doing things in songbird as well. I agree, we should have a test for sure (we have a test for matrices already in test-hoa-rotator.js).

After the discussion with @toji, I decided to revert the rotation API change. Omnitone can accept the pure Float32Array for Matrix4 and Songbird can interact with Three.js by supporting the camera object directly.

sgtm. should we remove support for Camera entirely to avoid confusion?

I will revert the change in Omnitone. For Songbird, I will leave it up to you. However, perhaps we can do some research on other WebGL libraries' convention.

With https://github.com/GoogleChrome/omnitone/commit/77e26678a8d0d647a15f05fa8c58678a0bc61fc1, Omnitone prefers the pure Float32Array for the rotation matrix.


Package issues

I dont know the proper name: but this should explain it:
Caused by: java.lang.IllegalAccessError: tried to access method net.minecraft.item.tool.ItemPickaxe.(Lnet/minecraft/item/Item$ToolMaterial;)V from class net.minecraft.item.Item

See this that asie made: http://paste.asie.pl/I9hu

Fixed.


Notification call handle

For background calls we use Connectycube Push notifications feature and some helpful plugins:

For iOS we use:

flutter_voip_push_notification;
flutter_call_kit (from the GitHub repository);
For Android we use:

firebase_messaging
connectycube_flutter_call_kit

I found 2 lib:

https://pub.dev/packages/callkeep
https://pub.dev/packages/flutter_callkeep
they support both Android and IOS. And you try to use them?

When we developed our samples we investigated some available plugins and selected these. But you can use any other plugins in your project.

ok. i will check it. thanks you so much


Searching for boot produces no results

If I go to https://www.rdocumentation.org/ and search for the package boot and wait for a bit, I get a suggestion in the dropdown:

The package is, in fact, indexed. However, actually performing the search gives me an empty page:

The package boot does exist, it just isn't found in the search: https://www.rdocumentation.org/packages/boot/versions/1.3-30. If you search, for instance, for boot.ci, this hits that function from the package.
The issue happens with other packages, but I haven't tracked which, I simply decided to finally submit an issue. It might be that somehow the search query is filtering out "boot" as a common word or something?

I've been having the same issue for the past several months now. Direct search for almost anything, including basics like 'strsplit' yields no results (no packages and no functions), unless I start from the main page where I need to select one of the suggestions. If I select 'View results for "strsplit"', I get nothing. Feels like a bug, and for a newbie trying to learn R, it's not a pleasant experience.
I understand someone has to pay the bills, but why on RDocumentation.org if you click "Introduction to R" you are sent to the Datacamp lessons instead of the "Introduction to R" book I was expecting (https://cran.r-project.org/doc/manuals/r-release/R-intro.pdf)?

Ok, found my answers. According to #138  this is a known issue and RDocumentation.org only works INSIDE Datacamp's lessons. This issue has been brought up earlier as #147
My solution is to use https://rdrr.io/ instead


WIP: DB commit retry

Alternative, more generic attempt at #1351, but abandoned for now because of lifetime issues. If anyone has some ideas how to fix please lmk.

Lifetimes semi fixed with 9c0d4775b73e8cdf973553c2807b279e39
@elsirion

Superseded by #1423


Add shape param for LogN distribution

It is currently not possible to set the "usual" loc and scale params on the log scale for the LogNormal distribution.
loc is usually 0, and scale should usually set to exp(mu)
For details, see http://nbviewer.ipython.org/url/xweb.geos.ed.ac.uk/~jsteven5/blog/lognormal_distributions.ipynb

While this is true for the built-in "LogN" function, you can input your own distribution directly like
a = rv(scipy.stats.lognorm(shape, loc=0, scale=scale))
I'll have to look into this more to justify the correction to the convenience function.


Update coingecko api call

Downside here is that Rinkeby isn't supported, so we won't have images for it right now. We can add back support to use the whole id mapping system for Rinkeby but I'd rather get back to other stuff right now than deal with that!

Yeah I don't feel Rinkeby is that important! 👍


Botframework 4 is more hectic to work.

Comparing to Botframework 3 Version 4 is more tedious even to create a simple bot. the framework is not simple as version 3.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 1217f5b5-6736-e72c-c420-773fc968aff3
Version Independent ID: 3a139655-6959-d8fd-a982-fe527db4d04a
Content: Additional support resources for the Bot Framework - Bot Service
Content Source: articles/bot-service-resources-links-help.md
Product: bot-framework
GitHub Login: @RobStand
Microsoft Alias: kamrani

For feedback on the SDK design itself, please log an issue in the appropriate repository for the language you are using. See BotBuilder for a list of the repos.


Windows compatibility (LOCAL DEVELOPMENT)

Motivation
New scripts to build and run the app locally in windows without any problems
Closes #38
Summary of changes

Added a .ps1 file that builds the entire app (front and back) and runs it as a production version.
Modified /truco-back/package.json and added an npm script npm run build-windows, the rest of scripts work in both linux and windows
Added said command to the truco-back/README.md
Deleted old build-front2back.sh

Checklist

[x] Tested the changes locally.
[x] Reviewed the changes on GitHub, line by line.
[x] This change requires new documentation.

No me queda claro como correrlo para desarrollar en windows, podrias aclararlo en el readme global. Gracias.

No me queda claro como correrlo para desarrollar en windows, podrias aclararlo en el readme global. Gracias.
(Necesitamos 1 sola manera de hacerlo, no muchas).

Lo agrego para hoy antes del fin del dia!

I finished making the app compatible with windows and additionally created a truco-back/public directory as it should always exist since its part of the structure


bootstrap/install not waiting for operator to be ready

Hey folks,
trying to make
glasskube bootstrap
glasskube install argo-cd

An error occurred during installation:

Internal error occurred: failed calling webhook "vpackage.kb.io": failed to call webhook: Post "https://glasskube-webhook-service.glasskube-system.svc:443/validate-packages-glasskube-dev-v1alpha1-package?timeout=10s": no endpoints available for service "glasskube-webhook-service"

Meanwhile deployment:

Expected behaviour:

boostrap waiting for deployment to be ready
install waiting for returning error message

I investigated this a little and it looks like replicas and availableReplicas can both be nil here:
https://github.com/glasskube/glasskube/blob/54d0f0f556a7ddefb5e15e5d252abbad8aa24948/pkg/bootstrap/bootstrap.go#L174-L176
…in which case the comparison evaluates to true when it should be false.


Initial Win32 implementation

Very WIP for the time being until I can get my hands on a Windows VM

Cool! Feel free to merge it yourself when you feel it's ready, I don't really have the time currently to put much focus on this project myself


Feature babel reintroduction

This reverts the previous PR that removed babel-ready es6 code, and sets up babel to work correctly in the global install.
Please test this in both node 0.12.x and 5.x:
$ npm install -g https://github.com/dcneiner/tag-release.git\#feature-babel-reintroduction

The one commit is a straight revert, so it might be best to look at just the other commit.

YES YES YES YES YES YES YES


RangeSlider Rendering Breaks within ScrollView

My app has an onboarding process that utilizes a pages horizontal ScrollView to walk new users through creating their profile, step by step.
I have used this RangeSlider component elsewhere in the app, successfully, within a bottom sheet.
However, when I added it to a page in my onboarding flow, the rendering broke.  I recall from the first time I used it that a similar thing occurred, and I was able to fix it by providing a fixed width to the RangeSlider container, instead of a percentage width.
However, in this case, this doesn't fix the issue.  I believe the problem is that the RangeSlider is somehow computing its size on mount based on the ultimate ancestor component, which, since this is part of a horizontal ScrollView is the width of the entire ScrollView, rather than the width of the actual screen.
Please let me know if you have a fix or a workaround for this!  I like this package, but I will unfortunately be forced to use another or sink a bunch of extra time in order make my own, if I can't solve this issue.
Screenshot: (Note: the minimum and maximum are 0 and 99, respectively, and the knobs should be at 19 and 29, respectively, with a white inRangeBarColor between them, and a translucent white outOfRangeBarColor on either side, with rounded edges, however, you can see that the rendering is quite broken instead)

After looking through your code and inspecting the layout events, I actually determined that the aforementioned is not the cause of the layout bug.  It's much simpler.
Your library doesn't support translucent colors for the outOfRangeBarColor, because it gets layered over the inRangeBarColor, which is just applied to a static 100% width bar below, thus giving the effect seen above, with half of the knob size sticking out of either side visible.
You could fix this by animating both the inner bar and outer bar when the knobs are dragged, instead of just the outer bars.
For now, since i am in a severe time crunch, I'm just going to set it to a solid color.


add description to devicelab .manual_quarantine_file

We can manually quarantine a devicelab bot by add a .manual_quarantine_file to the homedir.
It would be nice to be able to specify some text in the file which shows up on the swarming bot webpage, to see why the host was quarantined.
\cc @keyonghan

https://chrome-internal-review.googlesource.com/c/infradata/config/+/6113870 to support.
http://cl/544718451 to update doc.


Hash IPSec keys in the bugtool. Unit test are also added.

Previously keys were trimmed from the output but now keys are hashed and stored in the output

Fixes : #15375

@qmonnet I made some changes but I had an issues, I tried to process the output and have attached screenshots

this is the modified output which I tried for hashing the keys but when I open tar and view its output
 I get this, I can't figure out why. Can you help please ?

@qmonnet Thankyou. I just fixed them and updated and pr.

Ok I won't have time to review today. If you can, please have a look at the GitHub actions errors and see if some look related to your PR (and if so, if you can fix them!). The Go-related checks in particular are usually easy to fix, and this may improve the result for other of the actions to.

test-me-please

@qmonnet , Any hints on why the test are failing ?

I think the test failures are unrelated to this PR.
In this stage of CI we see:
Run docker/build-push-action@e1b7f96249f2e4c8e4ac1519b9608c0d48944a1f
📣 Buildx version: 0.5.1
🏃 Starting build...
/usr/bin/docker buildx build --tag quay.io/cilium/operator-alibabacloud-ci:059ffdbd0724c17ad364a14d0f93195738e69ace --platform linux/amd64,linux/arm64 --iidfile /tmp/docker-build-push-V78r8I/iidfile --file ./images/operator-alibabacloud/Dockerfile --push .
error: could not find images/operator-alibabacloud: stat images/operator-alibabacloud: no such file or directory
Error: buildx call failed with: error: could not find images/operator-alibabacloud: stat images/operator-alibabacloud: no such file or directory

which relates to recently-merged code, and it looks like the Cilium images are not being built as a result.
Other  tests are failing when they are unable to retrieve the image:
Run until curl --silent -f -lSL "https://quay.io/api/v1/repository/cilium/cilium-ci/tag/059ffdbd0724c17ad364a14d0f93195738e69ace/images" &> /dev/null; do sleep 45s; done
Error: The action has timed out.

Please can you rebase the PR on the latest master, which I think will fix the problem.

I think the test failures are unrelated to this PR.
In this stage of CI we see:
Run docker/build-push-action@e1b7f96249f2e4c8e4ac1519b9608c0d48944a1f
📣 Buildx version: 0.5.1
🏃 Starting build...
/usr/bin/docker buildx build --tag quay.io/cilium/operator-alibabacloud-ci:059ffdbd0724c17ad364a14d0f93195738e69ace --platform linux/amd64,linux/arm64 --iidfile /tmp/docker-build-push-V78r8I/iidfile --file ./images/operator-alibabacloud/Dockerfile --push .
error: could not find images/operator-alibabacloud: stat images/operator-alibabacloud: no such file or directory
Error: buildx call failed with: error: could not find images/operator-alibabacloud: stat images/operator-alibabacloud: no such file or directory

which relates to recently-merged code, and it looks like the Cilium images are not being built as a result.
Other tests are failing when they are unable to retrieve the image:
Run until curl --silent -f -lSL "https://quay.io/api/v1/repository/cilium/cilium-ci/tag/059ffdbd0724c17ad364a14d0f93195738e69ace/images" &> /dev/null; do sleep 45s; done
Error: The action has timed out.

Please can you rebase the PR on the latest master, which I think will fix the problem.

Thanks, @twpayne. That helped.

This looks good! A few minor nits.
Please also squash your two commits into a single one.
I'm starting to believe that hashEncryptionKeys() being slightly complex, it could benefit from a test to make sure that it processes the strings as expected. Would you be willing to look into that? It shouldn't be too complex - we would probably move the function to bugtool/cmd/helper.go and add a test in bugtool/cmd/helper_test.go, where we'd call the function with a few strings as input and we would make sure they would be processed as expected. It could be in this PR or as a follow-up.

Sure. I'll do that and will make the necessary changes in the morning.

@qmonnet Thanks for mentoring. Learned a lot! I have tried to fix and make all the necessary changes. Can u please look at the final changes? Also both of my commits are signed but I don't know why the label is attached.

Awesome, thank you!

@qmonnet Can I work on some other issue as well?

Sure, I can't see why not

test-me-please

Reviews are in. The only test failure is due to known flake https://github.com/cilium/cilium/issues/15737, since fixed. I'm merging.