Error: invalid device function launching kernel kScaleAndBias_kernel

Hi All,
I am following the example with movielens and got the error as below:
train -c config.json -i gl_input.nc -o gl_output.nc -n gl.nc -b 256 -e 10
NNNetwork::NNNetwork: 1 input layer
NNNetwork::NNNetwork: 1 output layer
NNWeight::NNWeight: Allocating 13697024 bytes (128, 26752) for weights between Input and Hidden
Error: invalid device function launching kernel kScaleAndBias_kernel
GpuContext::Shutdown: Shutting down cuBLAS on GPU for process 0
GpuContext::Shutdown: CuBLAS shut down on GPU for process 0
GpuContext::Shutdown: Shutting down cuRand on GPU for process 0
GpuContext::Shutdown: CuRand shut down on GPU for process 0
GpuContext::Shutdown: Process 0 out of 1 finalized.

Could you suggest some hints to figure out what did I do wrong?
Thanks a lot.

I believe that's a Fermi class GPU (GF119 according to the link below).
DSSTNE requires Kepler (2012) or later GPUs due to the use of the __shfl
instruction in its CUDA kernels which was introduced with GK104.
https://www.techpowerup.com/gpudb/821/geforce-gt-610
On Thu, Jun 16, 2016 at 5:18 AM, oyotong<EMAIL_ADDRESS>wrote:

Hi All,
I am following the example with movielens and got the error as below:
train -c config.json -i gl_input.nc -o gl_output.nc -n gl.nc -b 256 -e 10
NNNetwork::NNNetwork: 1 input layer
NNNetwork::NNNetwork: 1 output layer
NNWeight::NNWeight: Allocating 13697024 bytes (128, 26752) for weights
between Input and Hidden
Error: invalid device function launching kernel kScaleAndBias_kernel
GpuContext::Shutdown: Shutting down cuBLAS on GPU for process 0
GpuContext::Shutdown: CuBLAS shut down on GPU for process 0
GpuContext::Shutdown: Shutting down cuRand on GPU for process 0
GpuContext::Shutdown: CuRand shut down on GPU for process 0
GpuContext::Shutdown: Process 0 out of 1 finalized.
[image: image]
https://cloud.githubusercontent.com/assets/9816096/16113007/a22f7fd8-33ec-11e6-9879-0bcba151ce73.png
Could you suggest some hints to figure out what did I do wrong?
Thanks a lot.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/amznlabs/amazon-dsstne/issues/41, or mute the thread
https://github.com/notifications/unsubscribe/ARNK9m2cWnWeo7ve0B8yX8r_EpDSD4Hmks5qMSLzgaJpZM4I3PF2
.

Interestingly, DSSTNE should have kvetched about this during GPU
initialization.  I'll figure out why it didn't.
On Thu, Jun 16, 2016 at 5:27 AM, Scott Le Grand<EMAIL_ADDRESS>wrote:

I believe that's a Fermi class GPU (GF119 according to the link below).
DSSTNE requires Kepler (2012) or later GPUs due to the use of the __shfl
instruction in its CUDA kernels which was introduced with GK104.
https://www.techpowerup.com/gpudb/821/geforce-gt-610
On Thu, Jun 16, 2016 at 5:18 AM, oyotong<EMAIL_ADDRESS>wrote:

Hi All,
I am following the example with movielens and got the error as below:
train -c config.json -i gl_input.nc -o gl_output.nc -n gl.nc -b 256 -e 10
NNNetwork::NNNetwork: 1 input layer
NNNetwork::NNNetwork: 1 output layer
NNWeight::NNWeight: Allocating 13697024 bytes (128, 26752) for weights
between Input and Hidden
Error: invalid device function launching kernel kScaleAndBias_kernel
GpuContext::Shutdown: Shutting down cuBLAS on GPU for process 0
GpuContext::Shutdown: CuBLAS shut down on GPU for process 0
GpuContext::Shutdown: Shutting down cuRand on GPU for process 0
GpuContext::Shutdown: CuRand shut down on GPU for process 0
GpuContext::Shutdown: Process 0 out of 1 finalized.
[image: image]
https://cloud.githubusercontent.com/assets/9816096/16113007/a22f7fd8-33ec-11e6-9879-0bcba151ce73.png
Could you suggest some hints to figure out what did I do wrong?
Thanks a lot.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/amznlabs/amazon-dsstne/issues/41, or mute the thread
https://github.com/notifications/unsubscribe/ARNK9m2cWnWeo7ve0B8yX8r_EpDSD4Hmks5qMSLzgaJpZM4I3PF2
.

Got it, thank you!
Oh, I need to upgrade the card.
How about 'GeForce GTX 760M'? Could you suggest some card?
Only for study DSSTNE.
Thanks again!

I
On Jun 16, 2016 6:18 AM, "oyotong"<EMAIL_ADDRESS>wrote:

Hi All,
I am following the example with movielens and got the error as below:
train -c config.json -i gl_input.nc -o gl_output.nc -n gl.nc -b 256 -e 10
NNNetwork::NNNetwork: 1 input layer
NNNetwork::NNNetwork: 1 output layer
NNWeight::NNWeight: Allocating 13697024 bytes (128, 26752) for weights
between Input and Hidden
Error: invalid device function launching kernel kScaleAndBias_kernel
GpuContext::Shutdown: Shutting down cuBLAS on GPU for process 0
GpuContext::Shutdown: CuBLAS shut down on GPU for process 0
GpuContext::Shutdown: Shutting down cuRand on GPU for process 0
GpuContext::Shutdown: CuRand shut down on GPU for process 0
GpuContext::Shutdown: Process 0 out of 1 finalized.
[image: image]
https://cloud.githubusercontent.com/assets/9816096/16113007/a22f7fd8-33ec-11e6-9879-0bcba151ce73.png
Could you suggest some hints to figure out what did I do wrong?
Thanks a lot.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/amznlabs/amazon-dsstne/issues/41, or mute the thread
https://github.com/notifications/unsubscribe/ASdfmc9OgGvDA0rZyP3FWS6A4hyqRjmGks5qMSL0gaJpZM4I3PF2
.

Gtx 760 ought to do.

Got it, thanks a lot!

Getting similar error on volta, any idea on how to workaround this ?
`
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 384.81                 Driver Version: 384.81                    |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|===============================+======================+======================|
|   0  Tesla V100-SXM2...  Off  | 00000000:07:00.0 Off |                    0 |
| N/A   36C    P0    43W / 300W |     10MiB / 16152MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
`


[83]  Error pages are shown when errors are caused by SSO

When a request comes in from another source that raises an error, eg. SSO, then currently the application does not provide a 500 page and the request results in an unstyled browser 500.
Replicate by signing in and then visiting https://tvs.edge.dxw.net/auth/azureactivedirectory/callback directly

Before:

After:

 Errors caused by sign-in are rendered correctly

 Errors caused by sign-in are rendered correctly


Cadence/Temporal unit tests failing: cannot connect to server

Both Cadence and Temporal unit tests are all failing due to being unable to connect to the server.  This is happening on my developer workstation as well as the GitHub test runners.
I've marked these tests with [TestTrait.Category, TestTrait.Investigate] to disable them in the GitHub runners.
@johncburns1: Perhaps you could have a look at some point.  I'm on the tail end of the GitHub Action automation effort and just noticed this when retesting the unit testing actions.  The unit tests were basically hanging on these and the GitHub Action eventually gets cancelled.

You know, this is probably the same as #1199.
I'm going to try upgrading to the new .NET 5.0 packages across all of the libraries and modify the test projects to multi-target .NET Framework, .NET Core 3.1 and .NET 5.0 and see that happens.

There's actually a few other issues here including port conflicts with containers hanging around from previous unit tests and docker being put into swarm mode by some unit tests and not restoring normal mode.  I'm not sure why we haven encountered and of this before.
I've added the new TestHelper.ResetDocker() method and am going to call this in the constructor of any tests that rely on Docker to ensure it's in a known state.
I also noticed that Visual Studio makes it easy to have unit test projects target multiple frameworks.  I didn't know this was a feature.  I'm going to add net48 and netcoreapp3.1 targets where it makes sense.

I've fixed some things here, leaving #1199 open for a moment.


⚠ SceneTime has degraded performance

In ab17a48, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 1277 ms

Resolved: SceneTime performance has improved in aca127b after 6 minutes.


gulp protractor - tests not working

Hello,
this is my first ever issue on github, so please bear with me if I make mistakes in submitting it :)
I scaffolded my project using yo m-ionic and chose tabs and SASS and all cordova plugins as options.
When I run gulp protractor right after the scaffolding has terminated the error message I get is the following:
1) Debug page should grade passwords
   Message:
     ElementNotVisibleError: element not visible
  (Session info: chrome=46.0.2490.86)
  (Driver info: chromedriver=2.19.346063 (38b35413bd4a486d436a9749e090454bc9ff6708),platform=Mac OS X 10.11.1 x86_64) (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 45 milliseconds
Build info: version: '2.47.1', revision: '411b314', time: '2015-07-30 03:03:16'
System info: host: 'Roccos-Air.default', ip: '<IP_ADDRESS>', os.name: 'Mac OS X', os.arch: 'x86_64', os.version: '10.11.1', java.version: '1.8.0_45'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{applicationCacheEnabled=false, rotatable=false, mobileEmulationEnabled=false, chrome={userDataDir=/var/folders/_m/rxjymxms1zz6_mzr_jhwjj880000gn/T/.org.chromium.Chromium.uzpd1G}, takesHeapSnapshot=true, databaseEnabled=false, handlesAlerts=true, hasTouchScreen=false, version=46.0.2490.86, platform=MAC, browserConnectionEnabled=false, nativeEvents=true, acceptSslCerts=true, locationContextEnabled=true, webStorageEnabled=true, browserName=chrome, takesScreenshot=true, javascriptEnabled=true, cssSelectorsEnabled=true}]
Session ID: f7e90aadf3578c0231561ed836fa1eb0
   Stacktrace:
     ElementNotVisibleError: element not visible
  (Session info: chrome=46.0.2490.86)
  (Driver info: chromedriver=2.19.346063 (38b35413bd4a486d436a9749e090454bc9ff6708),platform=Mac OS X 10.11.1 x86_64) (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 45 milliseconds
Build info: version: '2.47.1', revision: '411b314', time: '2015-07-30 03:03:16'
System info: host: 'Roccos-Air.default', ip: '<IP_ADDRESS>', os.name: 'Mac OS X', os.arch: 'x86_64', os.version: '10.11.1', java.version: '1.8.0_45'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{applicationCacheEnabled=false, rotatable=false, mobileEmulationEnabled=false, chrome={userDataDir=/var/folders/_m/rxjymxms1zz6_mzr_jhwjj880000gn/T/.org.chromium.Chromium.uzpd1G}, takesHeapSnapshot=true, databaseEnabled=false, handlesAlerts=true, hasTouchScreen=false, version=46.0.2490.86, platform=MAC, browserConnectionEnabled=false, nativeEvents=true, acceptSslCerts=true, locationContextEnabled=true, webStorageEnabled=true, browserName=chrome, takesScreenshot=true, javascriptEnabled=true, cssSelectorsEnabled=true}]
Session ID: f7e90aadf3578c0231561ed836fa1eb0
    at Array.forEach (native)
    at process._tickCallback (node.js:377:9)
Error
    at [object Object].<anonymous> (/Users/rocco/development/test/generator/test/protractor/main-debug.spec.js:15:19)
From: Task: Asynchronous test function: it()
Error
    at [object Object].<anonymous> (/Users/rocco/development/test/generator/test/protractor/main-debug.spec.js:9:3)
    at Object.<anonymous> (/Users/rocco/development/test/generator/test/protractor/main-debug.spec.js:3:1)

Finished in 1.13 seconds
1 test, 1 assertion, 1 failure

Shutting down selenium standalone server.
[launcher] 0 instance(s) of WebDriver still running
[launcher] chrome #1 failed 1 test(s)
[launcher] overall: 1 failed spec(s)
[launcher] Process exited with error code 1

I did a bit of research and someone suggested to tweak the protractor.conf.js file by adding this:
onPrepare: function() {     browser.driver.manage().window().maximize();   },
This changed the error message which is now the following:
Starting selenium standalone server...
[launcher] Running 1 instances of WebDriver
Selenium standalone server started at http://<IP_ADDRESS>:59929/wd/hub
F

Failures:

  1) Debug page should grade passwords
   Message:
     Expected '' to equal 'weak'.
   Stacktrace:
     Error: Failed expectation
    at [object Object].<anonymous> (/Users/rocco/development/test/generator/test/protractor/main-debug.spec.js:16:40)

  2) Debug page should grade passwords
   Message:
     Expected '' to equal 'medium'.
   Stacktrace:
     Error: Failed expectation
    at [object Object].<anonymous> (/Users/rocco/development/test/generator/test/protractor/main-debug.spec.js:21:40)

  3) Debug page should grade passwords
   Message:
     Expected '' to equal 'strong'.
   Stacktrace:
     Error: Failed expectation
    at [object Object].<anonymous> (/Users/rocco/development/test/generator/test/protractor/main-debug.spec.js:26:40)

Finished in 2.128 seconds
1 test, 6 assertions, 3 failures

Shutting down selenium standalone server.
[launcher] 0 instance(s) of WebDriver still running
[launcher] chrome #1 failed 3 test(s)
[launcher] overall: 3 failed spec(s)
[launcher] Process exited with error code 1

/Users/rocco/development/test/generator/gulp/testing.js:42
      throw err;
      ^
Error: protractor exited with code 1

when looking at the test execution, it looks like protractor is actually performing "sendKeys", but the tests fail. I've been struggling with this issue for quite a while and did a lot of research on SO or similar, but I couldn't fix it.
Please let me know if it a bug on my side or if it's a common issue. Again, sorry if this is in any way inappropriate.
Thanks,
Rocco

Hi Rocco / @bagolol. In my opinion you reported this issue very nicely. You described which actions you performed that led to the error and you did some research trying to fix it on your own and provided the result of that as well. That's how it's done. Excellent :)
I'll look into it!

I just set up a project with tabs from scratch as you described, and ran gulp protractor
[10:09:49] Starting 'webdriver-update'...
Updating selenium standalone
downloading https://selenium-release.storage.googleapis.com/2.47/selenium-server-standalone-2.47.1.jar...
Updating chromedriver
downloading https://chromedriver.storage.googleapis.com/2.19/chromedriver_mac32.zip...
[more gulp f
chromedriver_2.19.zip downloaded to /Users/jonathan/Projects/play/test/node_modules/protractor/selenium/chromedriver_2.19.zip
[10:09:51] Finished 'build-vars' after 1.22 s
[10:09:51] Finished 'eslint' after 1.85 s
[10:09:51] Starting 'linting'...
[10:09:51] Finished 'linting' after 4.36 μs
[10:09:51] Finished 'bower-fonts' after 1.87 s
[10:09:51] Finished 'styles' after 1.28 s
[10:09:51] Starting 'inject-all'...
[10:09:51] gulp-inject 5 files into index.html.
[10:09:51] gulp-inject 1 files into index.html.
[10:09:51] Finished 'inject-all' after 87 ms
[10:09:51] Starting 'serve'...
[10:09:51] Finished 'serve' after 9.62 ms
[BS] Access URLs:
 ---------------------------------------
       Local: http://localhost:3000
    External: http://<IP_ADDRESS>:3000
 ---------------------------------------
          UI: http://localhost:3001
 UI External: http://<IP_ADDRESS>:3001
 ---------------------------------------
[BS] Serving files from: app
[BS] Serving files from: .tmp
selenium-server-standalone-2.47.1.jar downloaded to /Users/jonathan/Projects/play/test/node_modules/protractor/selenium/selenium-server-standalone-2.47.1.jar
[10:10:00] Finished 'webdriver-update' after 11 s
[10:10:00] Starting 'protractor'...
Starting selenium standalone server...
[launcher] Running 1 instances of WebDriver
Selenium standalone server started at http://<IP_ADDRESS>:63362/wd/hub
.

Finished in 1.155 seconds
1 test, 6 assertions, 0 failures

Shutting down selenium standalone server.
[launcher] 0 instance(s) of WebDriver still running
[launcher] chrome #1 passed
[10:10:05] Finished 'protractor' after 4.51 s

Honestly I'm not sure why it isn't working for you... I'm just gonna throw in some ideas and hope they are helpful:

When you navigate to http://localhost:3000/#/main/debug and scroll down to the password field, is it visible and does it grade your passwords when you type them in?
Just in case. Maybe set up again and see if that changes anything or delete the node_modules folder and install again using npm install
Did you leave gulp watch or any other task running while running gulp protractor? It needs to run alone.
the protractor.conf.js the generator provides assumes you have chrome installed. Is that the case? Or maybe there's something else different in your setup: baseUrl?
Maybe you can setup a small protractor example without the generator and see if that works.

It's a little weird that protractor obviously seems to run the tests but that they seem to fail. So it's not that likely that there's something wrong with the setup... Can you make sure the content of the following files are as they are in the demo?
https://github.com/mwaylabs/generator-m-ionic-demo/blob/master/app/main/controllers/debug-ctrl.js
https://github.com/mwaylabs/generator-m-ionic-demo/blob/master/app/main/templates/debug.html
https://github.com/mwaylabs/generator-m-ionic-demo/blob/master/test/protractor/main-debug.spec.js
What happens, when you clone the demo and run gulp protractor?

Hi,
thanks for the swift reply.
I just cloned the repo, run npm install and bower install. when I run gulp protractor I still get an error message:
Starting selenium standalone server...
[launcher] Running 1 instances of WebDriver
Selenium standalone server started at http://<IP_ADDRESS>:50165/wd/hub
FF

Failures:

  1) Debug page should grade passwords
   Message:
     ElementNotVisibleError: element not visible
  (Session info: chrome=46.0.2490.86)
  (Driver info: chromedriver=2.19.346063 (38b35413bd4a486d436a9749e090454bc9ff6708),platform=Mac OS X 10.11.1 x86_64) (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 33 milliseconds
Build info: version: '2.47.1', revision: '411b314', time: '2015-07-30 03:03:16'
System info: host: 'Roccos-Air.default', ip: '<IP_ADDRESS>', os.name: 'Mac OS X', os.arch: 'x86_64', os.version: '10.11.1', java.version: '1.8.0_45'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{applicationCacheEnabled=false, rotatable=false, mobileEmulationEnabled=false, chrome={userDataDir=/var/folders/_m/rxjymxms1zz6_mzr_jhwjj880000gn/T/.org.chromium.Chromium.Dl0nqc}, takesHeapSnapshot=true, databaseEnabled=false, handlesAlerts=true, hasTouchScreen=false, version=46.0.2490.86, platform=MAC, browserConnectionEnabled=false, nativeEvents=true, acceptSslCerts=true, locationContextEnabled=true, webStorageEnabled=true, browserName=chrome, takesScreenshot=true, javascriptEnabled=true, cssSelectorsEnabled=true}]
Session ID: 35e73179a918cbb1a260eeafd85bc7a8
   Stacktrace:
     ElementNotVisibleError: element not visible
  (Session info: chrome=46.0.2490.86)
  (Driver info: chromedriver=2.19.346063 (38b35413bd4a486d436a9749e090454bc9ff6708),platform=Mac OS X 10.11.1 x86_64) (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 33 milliseconds
Build info: version: '2.47.1', revision: '411b314', time: '2015-07-30 03:03:16'
System info: host: 'Roccos-Air.default', ip: '<IP_ADDRESS>', os.name: 'Mac OS X', os.arch: 'x86_64', os.version: '10.11.1', java.version: '1.8.0_45'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{applicationCacheEnabled=false, rotatable=false, mobileEmulationEnabled=false, chrome={userDataDir=/var/folders/_m/rxjymxms1zz6_mzr_jhwjj880000gn/T/.org.chromium.Chromium.Dl0nqc}, takesHeapSnapshot=true, databaseEnabled=false, handlesAlerts=true, hasTouchScreen=false, version=46.0.2490.86, platform=MAC, browserConnectionEnabled=false, nativeEvents=true, acceptSslCerts=true, locationContextEnabled=true, webStorageEnabled=true, browserName=chrome, takesScreenshot=true, javascriptEnabled=true, cssSelectorsEnabled=true}]
Session ID: 35e73179a918cbb1a260eeafd85bc7a8
    at Array.forEach (native)
    at process._tickCallback (node.js:377:9)
Error
    at [object Object].<anonymous> (/Users/rocco/development/test/generator-m-ionic-demo/test/protractor/main-debug.spec.js:15:19)
From: Task: Asynchronous test function: it()
Error
    at [object Object].<anonymous> (/Users/rocco/development/test/generator-m-ionic-demo/test/protractor/main-debug.spec.js:9:3)
    at Object.<anonymous> (/Users/rocco/development/test/generator-m-ionic-demo/test/protractor/main-debug.spec.js:3:1)

  2) Debug page should grade passwords
   Message:
     Expected '' to equal 'weak'.
   Stacktrace:
     Error: Failed expectation
    at [object Object].<anonymous> (/Users/rocco/development/test/generator-m-ionic-demo/test/protractor/side-debug.spec.js:16:40)

  3) Debug page should grade passwords
   Message:
     Expected '' to equal 'medium'.
   Stacktrace:
     Error: Failed expectation
    at [object Object].<anonymous> (/Users/rocco/development/test/generator-m-ionic-demo/test/protractor/side-debug.spec.js:21:40)

  4) Debug page should grade passwords
   Message:
     Expected '' to equal 'strong'.
   Stacktrace:
     Error: Failed expectation
    at [object Object].<anonymous> (/Users/rocco/development/test/generator-m-ionic-demo/test/protractor/side-debug.spec.js:26:40)

Finished in 4.041 seconds
2 tests, 7 assertions, 4 failures

Shutting down selenium standalone server.
[launcher] 0 instance(s) of WebDriver still running
[launcher] chrome #1 failed 4 test(s)
[launcher] overall: 4 failed spec(s)
[launcher] Process exited with error code 1

/Users/rocco/development/test/generator-m-ionic-demo/gulp/testing.js:42
      throw err;
      ^
Error: protractor exited with code 1

and to reply to your previous questions:

yes, when I navigate to the relevant url the 'password strength check' works fine
no, I always make sure gulp watch isn't running
yes, I have chrome installed and it is up to date and I haven't changed the baseUrl
I tried to create my own tests, but protractor seems to be able to find only the elements with custom class names and not by binding or ionic class names

I also tried to resize the view setting it at 70, 80 or 90% so that all the elements were visible when the test is run, but that didn't change the error message.
Thanks,
Rocco

Sorry you're having this issue. Honestly I'm not sure what else could cause this...
What's the result of
node -v
npm -v

rocco:~ $ node -v
v5.0.0
rocco:~ $ npm -v
3.4.1

That's my current setup:
$ node -v
v5.0.0
$ npm -v
3.3.9

This should be fine I think... Just to be 100% sure, can you downgrade to npm 3.3.9 and try again?
Sorry. I have no further ideas. Please let me know if you find out something.

Closing due to inactivity and since we cannot reproduce. If anything more comes up, I'll reopen this issue.


Is it possible to visualize geojson.io in an iframe?

Perhaps, but you'll be better served by hosting your own copy on your own server.

I've tried to host geojson.io on my server, but still, I'm always redirected.


Generate pod.Name when pod.Name == "" for both HTTP and file sources.

Fix #3584
cc/ @thockin
I patched release-0.8 branch with PR #3725 with some modification in both http.go and http_test.go.

LGTM


Feats that are "Class Bound" selectable by any class bug  [[ Hardy and Primate Rage bugged ]]

Hardy is a Fighter only feat.   Notice how it is presenting itself as an option for my Sorcerer.  It should only be presented as option for the Fighter class.
Primal Rage is a Barbarian only feat.  Notice how it is presenting itself as an option for my Sorcerer.  It should only be presented as an option to the Barbarian class.
I believe they should say "Requirement: 4 levels in Fighter class" and "Requirement: 4 levels in Barbarian class" respectfully.   (( So you could select them upon reaching 4th level in either class. ))

Fixed


When List Report, only works when pressed on "Start"/"Go"

no binding is present if no automatic loading on loading the app
Currently i dont know any way to get binding infos


Updated dev-tools

Fixes all the warnings here: https://travis-ci.org/FriendsOfPHP/PHP-CS-Fixer/jobs/657490890.

Can you update the travis script to output the versions of the versions of the tooling used (the changed ones), as I think we currently do not see this? After that, RTM from me

The versions are already shown?

all I see is
0.18s$ ./dev-tools/tools/composer-normalize composer.json --dry-run
composer.json is already normalized.

https://travis-ci.org/github/FriendsOfPHP/PHP-CS-Fixer/jobs/662693195?utm_medium=notification&utm_source=github_status
maybe I missing something?

Linking /home/travis/.phive/phars/composer-normalize-2.3.2.phar to ./tools/composer-normalize

Full version:
λλλ phive packages

Phive 0.13.2 - Copyright (C) 2015-2020 by Arne Blankerts, Sebastian Heuer and Contributors

Downloading https://api.github.com/repos/ergebnis/composer-normalize/releases

Downloading https://github.com/ergebnis/composer-normalize/releases/download/2.3.2/composer-normalize.phar

Downloading https://github.com/ergebnis/composer-normalize/releases/download/2.3.2/composer-normalize.phar.asc

Linking /home/travis/.phive/phars/composer-normalize-2.3.2.phar to ./tools/composer-normalize

Downloading https://api.github.com/repos/maglnet/ComposerRequireChecker/releases

Downloading https://github.com/maglnet/ComposerRequireChecker/releases/download/2.1.0/composer-require-checker.phar

Downloading https://github.com/maglnet/ComposerRequireChecker/releases/download/2.1.0/composer-require-checker.phar.asc

Linking /home/travis/.phive/phars/composer-require-checker-2.1.0.phar to ./tools/composer-require-checker

Downloading https://api.github.com/repos/phpstan/phpstan/releases

Downloading https://github.com/phpstan/phpstan/releases/download/0.12.11/phpstan.phar

Downloading https://github.com/phpstan/phpstan/releases/download/0.12.11/phpstan.phar.asc

Copying phpstan-0.12.11.phar to ./tools/phpstan

Can you update the travis script to output the versions of the versions of the tooling use

I'm interested in the versions of the tools are used by Travis, I did see which are downloaded


fixed save button event, initial MoP (5.4.8) support

i wonder how you could make 2 separate pull requests, github UI is new for me


Bug: Title Incorrect

Describe the bug
The title on the Record Badge Presentation report has an incorrect in that the Unit name is repeated 3 times.
To Reproduce
Steps to reproduce the behavior:

Go to Present Awards

Expected behavior
It should say "Record Badge Presentation - [Unit Name]
Screenshots

Device/ Version Deatils

Samsung S22 Ultra - Android
Mobile App
2.3.0

Additional context
The correct title is on the chrome version

Can confirm

Yeah, the issue with the buttons and header all appearing 3 times is the same root cause. It seems like on mobile terrain reloads part of the page 3 time so part of my code runs causing a triple up. I will merge these issues. Thanks for letting me know.

@CrispyCamper can you check if this still happens on the 2.5.0 which should be coming out on the store any day now? Just waiting on google checks.

Fixed with change from Cordova to Flutter in 2.4.2 releasing now.

Issue has come back up in version 2.4.4 as per app but 2.4.6 as per the google play store.

Details
Samsung s22 ultra


[Stdlib] Optimize CollectionType.first

For lazy collections, isEmpty and startIndex may be O(N) operations.
The old implementation ended up being potentially O(2N) instead of O(1).
In particular, accessing col.lazy.filter(pred).first would evaluate
the predicate on elements twice, once to determine the result of
isEmpty and once to determine startIndex.
While we're at it, tweak the complexity as well, as lazy collections may
be O(N).

Whether or not it could happen, pass (performance) regression tests, and not get reverted is academic.  The point is to prevent maintainers from even heading down that road mentally.

Whether or not it could happen, pass (performance) regression tests, and not get reverted is academic.  The point is to prevent maintainers from even heading down that road mentally.

@dabrahams Ah, I see. I thought you were arguing in favor of the possibility of reverting it at some point, but I gather now that you're saying it's not unrealistic for someone else to think reverting it makes sense (without the comment saying why it's a bad idea).

@dabrahams Ah, I see. I thought you were arguing in favor of the possibility of reverting it at some point, but I gather now that you're saying it's not unrealistic for someone else to think reverting it makes sense (without the comment saying why it's a bad idea).

@kballard It looks like this change could be trivially tested...

Yeah, you're right. I was being lazy. I'll write up a test tomorrow.

@gribozavr Test submitted as #860


Support Client Credentials Login

I would like to test operations using client credentials logins.  (Client ID and Client Secret.)  My scenario is that I have an application that has created other applications.  (So it the child applications has the owner set to the parent application).  I would like to use Graph Explorer to test out what operations are allowed in that scenario.
Describe the solution you'd like
I would like a way for the access token used by Graph Explorer to be generated from a Client ID and Client Secret.
Describe alternatives you've considered
I did think about getting an access token from powershell and then swapping out the access token used by Graph Explorer (on the Access Token tab).  But that tab is read only.

Hey @Vaccano. Graph Explorer does not support application permissions because of the security vulnerability caused by exposing your client secret and clientID to the web.
The authentication provider that we use also does not support this by default because of the same reasons.

@Onokaev - That makes sense.  However, getting an Access Token for a client credentials login is not too hard, and they expire fairly quickly.  Maybe consider allowing the input of a Client Credentials access token and using it in the Graph Explorer?

Sure thing @Vaccano. Let me log this as a feature request


Platform not found

Hello and many thanks for this great software. Today, I've set up my 800w-2t. So far I was able to change network configuration to match my local network. I also installed the custom component via HACS on my HA Core. The integration shows up and connects to the device/ip. Unfortunately, there are errors that prevent any further interactions. I hope, you can help me. :)
Regards, Mathias
The error:
Logger: homeassistant.setup
Source: setup.py:344
First occurred: 17:38:57 (4 occurrences)
Last logged: 17:38:57
Unable to prepare setup for platform hoymiles_wifi.sensor: Platform not found (cannot import name 'DeviceInfo' from 'homeassistant.helpers.device_registry' (/usr/src/homeassistant/homeassistant/helpers/device_registry.py)).
Unable to prepare setup for platform hoymiles_wifi.binary_sensor: Platform not found (cannot import name 'DeviceInfo' from 'homeassistant.helpers.device_registry' (/usr/src/homeassistant/homeassistant/helpers/device_registry.py)).
Unable to prepare setup for platform hoymiles_wifi.number: Platform not found (cannot import name 'DeviceInfo' from 'homeassistant.helpers.device_registry' (/usr/src/homeassistant/homeassistant/helpers/device_registry.py)).
Unable to prepare setup for platform hoymiles_wifi.button: Platform not found (cannot import name 'DeviceInfo' from 'homeassistant.helpers.device_registry' (/usr/src/homeassistant/homeassistant/helpers/device_registry.py)).

Are you running the latest version of home assistant? It seems you are running an old version where the device info was not available.

Good morning and thanks a lot. You are right. In fact, I checked for updates before, but HA doesn't show any available updates in the UI. Your hint made me think about it and yes, I currently run some 2023 version. So I have to solve this one first. Many thanks and have a great weekend!

All is running fine now. Thank you!

Great! Closing the issue then.


Unbonding Locks Component needed.

What's the problem? (required)
I am not able to manage my unbonding locks within the explorer.
What's the current behavior? (required)
No unbonding locks shows up within the explorer.
Do you have any personal experiences dealing with this problem? (optional)
Yes, when someone unbonds, whether partially or fully, the LP tokens are held within an unbonding lock for a period of 7 days. After 7 days passes then the token holder is able to withdraw or rebond their tokens. Currently the UX for this process is bad. Each unbond creates a new lock. See this issue for more details surrounding unbonding locks.
Describe a possible solution you've considered (optional)
I would like to see users having the ability to manage their unbonding locks within the explorer's MyAccount Delegating page. A section would show up with all the user current and pending unbonding locks, where with the click of a button tokens can be withdrawn when a lock is ready or rebonded whether lock is ready or not. For this to happen a component is needed for helping to display and manage unbonding locks.
Additional context (optional)
Each unbonding lock should have two buttons, withdraw and rebond. The withdraw button should be disabled if the unbonding lock is not ready to be withdrawn and the rebond button is only enabled when the token have not been withdrawn or rebonded.

Note: The styling of the unbonding lock component should follow the normal styling within the explorer.
Please see partial unbonding and fully unbonding for a walk through of the mock ups and user flow of how partial/fully unbonding should operate.

Is this design okay?

@samparsky sure that design if fine. At the section where you talk about the block number that the transaction occurred, we will replace that with the estimated date the user will be able to withdraw and until that date arrives and the unbonding lock is open then the withdraw button should be disabled.

@samparsky @Randy1Burrell the WITHDRAW button on the 30 LPT should be Greyed out, like it is in my design mockup. The text above is not correct - please make sure to use the text that is linked in the preview flow. If you hover over it, it should look like

The hover format should be the same as it is with all other "i" hovers (question mark when you hover over it)


Question regarding replication

Hello,
I have made my own little implementation of some of the methods described here (using some of your code as an example). I have a specific question regarding the Fast Gradient Sign method.
I have set epsilon to 0.3 as per the example. About 97.5 percent of my predicted labels change. This should be good. However on Cifar 10, the images become quite pixelated due to this. Is this supposed to happen? I thought the perturbations were invisible to the naked eye.
The convnet I am using uses 3 convolutional layers and 1 softmax layer with relu activations.
regards,
Riaan

Hi Riaan,
The value of the parameter epsilon should be set depending on the input domain you are working with. It lets you trade-off the chances of having the input misclassified with the magnitude of the perturbation introduced. The impact of an epsilon parameter of 0.3 on your CIFAR data will depend on how you pre-processed it before training your model. Have you tried reducing the value of epsilon?
You may want to check https://github.com/openai/cleverhans/blob/master/examples/ex_cifar10_tf.py and ping @paulhendricks
Cheers

I have tried various values for epsilon. between 0.007 up until 0.3 . I preprocess the data by dividing it by 255.0. With for example 0.07, approximately 70% of the labels changes! The lower I go, the less the likelihood of the prediction changing!
And yes I am using that code to replicate your research! If you wish, I can send you what I have done, although I don't want to impose!
@paulhendricks


ExtendableMessageEvent.source cannot be SameObject

According to [WebIDL] (http://heycam.github.io/webidl/#SameObject), [SameObject] doesn't apply to union types, so we should remove this annotation from ExtendableMessageEvent.source.

The [SameObject] extended attribute must not be used on anything other than a read only attribute whose type is an interface type or object. (WebIDL 4.3.15 [SameObject])

Did you reference this part? Before removing it, I just want to make sure whether it intends to disallow the case when all the member types of the union are interface types.
/cc @heycam @bzbarsky

That part of the IDL spec is just bogus, imo; there are existing IDL issues on that.  Any type that's always an object, including unions of interface types, Promise, etc, should be OK to use with [SameObject].
Arguably, even a union for which some types are an object should be OK with [SameObject].
@heycam may have pointers to the IDL spec issues off the top of his head.

Sounds reasonable. I found the IDL spec issue for this: https://github.com/heycam/webidl/issues/71

Pre F2F notes: Doesn't look like there's anything to discuss

Closing waiting on the IDL issue.


agent: memif and vcl fixes

Actually with the release proximity and as this fixes memif/VCL, let's maybe merge this PR and keep the refactoring for a later PR.


WIP search tweaks

[x] In search results: service icons on the right side when searching Keybase should be the colored ones, not the monochrome/icon font ones.
[x] In search results if you select a non-keybase service and search if you see a result that has keybase info, if you track them the username should be green (not orange)
[x] In search results: Rows cover up border / scrollbar: this is due to https://github.com/keybase/client/blob/master/shared/search/user-search/render.desktop.js#L115 the background being set to white causes this overlap
[x] In search results: Disallow finding yourself
[ ] In search results show spinner while waiting for results
[x] In search results: search input should be auto focused. Keep focus on input when changing the service type.
[ ] In search results: The services / input shouldn't scroll, just the results
[x] In search area hint text should be left aligned and be aligned with actual input text (currently it floats above the actual typed text)
[x] In search area hint text should be 'Search a xxxxx user' (with no group) and 'Add a xxxx user' when a group exists
[ ] In search area unselected services should be opacity 0.6. on hover/selected 1.0 opacity.
[ ] In search area removing the query should show the group or initial screen (currently shows no results)
[ ]
[ ] In search group view usersnames should be semibold
[ ] In group view actions should be clickable links, not row items (no highlight on hover, etc)
[ ] In group view, selected user should remain selected (not just on hover). So if they're shown on the right pane, they should be highlighted blue
[ ] In group view the remove 'x' button should be black_60 on hover, no animations
[ ] In group view we need the 'Clear search' link on the top right, see https://zpl.io/ZDWKbY
[ ]
[ ] Main nav search needs hand pointer on hover
[ ]
[ ] Profile card: Trakcers / Tracking links should be black_60 style not black_40 (maybe text style is wrong)
[ ] Profile card: Send invite link should be underlined on hover

:mag_right: The commits 0675cf484270...82840aab34c2 introduced some visual changes on win32:

Changed: Request_Invite-Name_Error (before) (after)

:mag_right: The commits 4c1f0cff4fb3...55f94a8bb101 introduced some visual changes on win32:

Changed: user_search-Normal (before) (after)

:mag_right: The commits 4c1f0cff4fb3...55f94a8bb101 introduced some visual changes on linux:

Changed: user_search-Normal (before) (after)

:mag_right: The commits 32560b07b04f...da45e65404f5 introduced some visual changes on win32:

Changed: unlock_folders-Success (before) (after)

Changed: unlock_folders-Single (before) (after)

:mag_right: The commits da45e65404f5...1b9a9b1e852b introduced some visual changes on win32:

Changed: user_search-Normal (before) (after)

:mag_right: The commits da45e65404f5...1b9a9b1e852b introduced some visual changes on linux:

Changed: user_search-Normal (before) (after)

:mag_right: The commits 54e3098cd1cb...1d4595a3f00a introduced some visual changes on win32:

Changed: user_search-Normal (before) (after)

:mag_right: The commits 54e3098cd1cb...1d4595a3f00a introduced some visual changes on linux:

Changed: user_search-Normal (before) (after)

:mag_right: The commits 1d4595a3f00a...e5c5bdb7b5bb introduced some visual changes on win32:

Changed: user_group-Chat_enabled (before) (after)

:mag_right: The commits 1d4595a3f00a...e5c5bdb7b5bb introduced some visual changes on linux:

Changed: user_group-Chat_enabled (before) (after)

:mag_right: The commits e5c5bdb7b5bb...ffdf3e12075c introduced some visual changes on win32:

Changed: user_group-Chat_enabled (before) (after)

:mag_right: The commits e5c5bdb7b5bb...ffdf3e12075c introduced some visual changes on linux:

Changed: user_group-Chat_enabled (before) (after)

:mag_right: The commits 8b6df0b9ef94...b327d904cbae introduced some visual changes on win32:

Changed: user_search-Normal (before) (after)

:mag_right: The commits 8b6df0b9ef94...b327d904cbae introduced some visual changes on linux:

Changed: user_search-Normal (before) (after)

@keybase/react-hackers this is ready for review. before i squish / rebase master to get the icon stuff i'll get feedback first since the commits are small and sensible now. when i get a thumb i'll do the rebase / waiting icon

Looks great! Thanks for cleaning this up!
Re: the UserPane smart component, I still think that's a good idea. It makes the parent component have to worry about much less, it just uses the component and the rest is taken care of.

The parent smart component passes just the UserPane smart component.

@MarcoPolo instead of allowing the component to be injected (i think thats a little bit of an abstraction violation, instead i went with allowing ownProps to have the selected user (really this thing is driven by one input anyways). i think this works nicely. if you don't init it like
<UserPane userForInfoPane={whatever}/>
then you get the totally connected one.

ok i'm going to squish / rebase

Replaced by squish/rebased version here: https://github.com/keybase/client/pull/3444


Backup config isn't working

Hi Alexis,
Found a bug in Get-FGTMonitorSystemConfigBackup: this function isn't working.
It returns $response.results but it should returns $response
Also fixed in PR #177

Fixed with 0.6.1


[1.x] Fixed type error caused by route $action error getting

This error message appeared in my use.

After checking, I found that the action obtained was an empty object because the following routing method was used.

This data is incorrectly stored as an empty object in the Recorders/SlowRequests file

So I provided a temporary patch to fix the error of not getting what I expected.
My English is not that good, so please understand if there is a mistake, thank you.

https://github.com/laravel/pulse/pull/432/commits/fb0b703ef5902087cf5aa2bf48538cb8cde17e2f
I have supported the internationalization of pulse, which can now be used in English, Chinese (simplified), Chinese (Traditional)
You only need to run the following command to generate the file
php artisan pulse:lang-publish

@KanekiYuto, can you please revert the internationalization commit (https://github.com/laravel/pulse/commit/fb0b703ef5902087cf5aa2bf48538cb8cde17e2f) and send that in a new pull request?
We will need individual PRs for the fix and the language feature.

@KanekiYuto, I've just tried to make this error happen with the routing method you have been using.
I created a test (https://github.com/laravel/pulse/pull/433/files) which seems to be passing.
Can you please create a minimal reproduction for this issue and we take a closer look?
laravel new bug-report --github="--public"

@KanekiYuto，您能否恢复国际化提交（fb0b703）并在新的拉取请求中发送它？
我们需要单独的公关修复和语言功能。

yes,i need.

@timacdonald After my repeated verification, I found that the error was caused by the incorrect generation of the routing cache file routes-v7.php. After updating to the latest laravel version, this problem seemed to disappear

@timacdonald经过我的反复验证，发现该错误是由于路由缓存文件 routes-v7.php 生成不正确导致的，在更新到最新的 laravel 版本后，这个问题似乎消失了

However, I still recommend providing a compatible type option to avoid errors

Thanks for checking that out for us.


Enhanced the random seed generation function.

This PR enhances the function that generates default random seeds for TensorFlow. This is needed because the previous approach is weak in multi-process settings, which are quite common when training or evaluating machine learning models. The implementation is inspired from OpenAI Gym.
I also added an implementation on SHA512 in the utilities to avoid having any external library dependencies along with a test for the hash function. The SHA512 implementation is based on that of CryptoSwift.

All the requested changes (except for the fileprivate for the bytes(count:startingAt:) function are done.

This should be ready for another look now.

@eaplatanios, If you need any help with all these tasks you are undertaking, I'd love to help you out. I really like the enhancements we've had in the past week. So if there are trivial/non-trivial tasks you need some help with, do tag me.

@Shashi456 Thanks a lot! Sorry for the late response but I was traveling. I don't have something planned right now, but I will definitely tag you if anything comes up. :)


Added functionality to interact with regex expressions

Description
Added functionality to interact with regex expressions.
Closes #2.
Author's Checklist

[x] These changes don't break existing dependants. If they do, and you suggest to proceed,
please explain why.

Reviewer's Checklist

[ ] All classes have documentation comments.
[ ] All methods have documentation comments.
[ ] No parameters are hardcoded. Should be loaded as properties instead. If there needs to be hardcoded properties, explain why.
[ ] All information to be logged/displayed to the user are internationalized. If not, explain why.
[ ] README.md has been updated if needed.
[ ] pom.xml version is set to the latest date If not, explain why.

Assignee's Checklist

[ ] All GitHub action checks have passed.
[ ] All reviewers have approved.
[ ] Relevant documentation has been updated if needed.
[ ] pom.xml version is set to the latest date If not, explain why.

The following needs to be added/modified:
[ ]  Test scenarios for matching input string to personal identifiable information.
[ ]  Project version in pom.xml.


Enable send screen scrolling when keyboard is shown

Related to YOMO-494
IOS
https://user-images.githubusercontent.com/105349292/225727297-e2d363bb-05c0-4b19-9974-c96555e69984.mov
Android
https://user-images.githubusercontent.com/105349292/225727355-d86f679b-fa6e-4b53-bcb4-86a5409b3963.mov

why ScrollableView? this component is meant for controlled scrolls. is there a child component that is controlling the scroll position?

Total copy from other places where KeyboardSpacer 😅. Changed.


Version namespacing

For the sake of ABI incompatibility for different versions.
In theory it allows to use several libraries that use different Blackhole versions in a single project.

Done in 9b7f6f54514209684d3144c72c7d385d1b7b4207


feat: Add Terraform Role configuration for GitHub Actions OIDC

Creating a Terraform Role to allow it to deploy the infrastructure.

:tada: This PR is included in version 1.3.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


vpx-seawitch view isn't great

Not sure if this requires a ticket but the view for this table isn't great as you can't see the sides or part of the plunger lane. I placed an ini with a fixed view here - https://filebin.net/liugjcv0b6ebbh9f

updated

PR Merged


Generate Migration file using sea-orm-cli

Problem

When we create migration file its name is expected to be in a particular pattern m<date>_<6-digit-index>_<description>.rs
example: m20220101_000001_create_table.rs
It will be better if we can generate it using sea-orm-cli which will automatic use current date-time for name and take description as parameter.
Proposed Solutions
API format
sea-orm-cl migrate new [description] [path_to_folder]
or
sea-orm-cl generate migration [description] [path_to_folder]
example
sea-orm-cli generate migration create_table_chef ./src/migrator
Apart from just the name default snippet code can also be written to that file.
Implementation
We can add a value to MigrateSubCommand / GenerateSubcommands and respective implementation in commands folder.

@Diwakar-Gupta If i understand correctly the main request is to implement a default template for a migration?
Aside from that there is already the sea-orm-cli migration generate command which can be used to generate the migration file.
Also there is a --universal-time flag on it to use universal time.

feature already exist sea-orm-cli migrate generate Thanks @aadi58002.


Consider maxItems value before rendering the add button

jsonschema refuses to validate an array of items when the number of
items is greater than the maxItems constraint. Therefore the UI should
consisder this constraint and not provide an "add" button when the
maximum number of elements is reached.
The "add" button is rendered in the following cases:

ui:options.addable is not false and items.length < schema.maxItems
schema.maxItems is unspecified and ui:options.addable is not false

As before, if ui:options.addable is not specified, it is considered as
true by default.
The "add" button is not rendered in the following cases:

ui:options.addable is false,
items.length >= schema.maxItems, even if ui.options:addable is true

Reasons for making this change
[Please describe them here]
If this is related to existing tickets, include links to them as well.
Checklist

[ ] I'm updating documentation

[ ] I've checked the rendering of the Markdown text I've added
[ ] If I'm adding a new section, I've updated the Table of Content

[ ] I'm adding or updating code

[x] I've added and/or updated tests
[ ] I've updated docs if needed
[x] I've run npm run cs-format on my branch to conform my code to prettier coding style

[ ] I'm adding a new feature

[ ] I've updated the playground with an example use of the feature

Hi @glasserc
Thanks for your comments. I've updated the pull request to take your requests into account. Is it good enough ?


Selecting camera in viewer isn't persistent

Describe the bug
Clicking the "eye" in the camera list moves the green camera, but does not change the time step. Therefore when interacting with the scene it snaps back
https://user-images.githubusercontent.com/3310961/201157826-259340f4-baaf-4aff-9153-e7831f9d6447.mov

Disclaimer: I'm new here and this is my first issue so what I'm saying might be totally wrong/dumb
I think this is because when the mouse moves to the viewer the green box goes to the camera that would be selected based on the playback slider. I figured the sensible thing to do would be just to change the slider position when you click the 👁 button. The problem is I don't think you can access the right slider state element from that element.
https://github.com/nerfstudio-project/nerfstudio/blob/main/nerfstudio/viewer/app/src/modules/SidePanel/CameraPanel/CameraPanel.jsx#L392
This is where we'd need to change the slider.
https://github.com/nerfstudio-project/nerfstudio/blob/main/nerfstudio/viewer/app/src/modules/SidePanel/CameraPanel/CameraPanel.jsx#L458
This is where the correct slider state is defined.
There seems to be another slider state defined above the 👁 button but when I set it to something nothing seems to happen. I'll keep messing with it though.

I just looked at it again and I realized I could just pass in the slider stuff in props.
here is my PR: https://github.com/nerfstudio-project/nerfstudio/pull/1192
I think I need a maintainer to approve running workflows so I'd appreciate if someone looked at it at their earliest convenience! Obviously no rush especially cause it's New Year's! Happy Holidays everyone! @tancik (I think)

Can I close this issue @tancik ?


login: allow passing additional args to provider

As part of moving asymmetric token support to a credential provider in #12334, support for passing --key-subject to cargo login was removed.
This change allows passing additional arguments to credential providers when running cargo login. For example:
cargo login -- --key-subject foo.
The asymmetric token provider (cargo:paseto) is updated to take advantage of this and re-enables setting --key-subject from cargo login.
r? @Eh2406
cc #8933

Looks good to me.

Seems reasonable to me.
@bors r=Eh2406

:pushpin: Commit 589a111893946cffb9ab3bca04c116bc5eca6f9a has been approved by Eh2406
It is now in the queue for this repository.

:hourglass: Testing commit 589a111893946cffb9ab3bca04c116bc5eca6f9a with merge 609ab73a76961ba709a1d5f48267a929bc2b9b29...

:sunny: Test successful - checks-actions
Approved by: Eh2406
Pushing 609ab73a76961ba709a1d5f48267a929bc2b9b29 to master...

:eyes: Test was successful, but fast-forwarding failed: 422 Update is not a fast forward

:bulb: This pull request was already approved, no need to approve it again.

This pull request previously failed. You should add more commits to fix the bug, or use retry to trigger a build again.

:pushpin: Commit 589a111893946cffb9ab3bca04c116bc5eca6f9a has been approved by Eh2406
It is now in the queue for this repository.

:sunny: Test successful - checks-actions
Approved by: Eh2406
Pushing 37a0514c75115c9208290490ec84a2e9833e0f5f to master...


A little bit of web-common code tidying.

Renaming one module, splitting another.

Pre-submit checklist:

Branch

[X] Commit sequence broadly makes sense
[X] Key commits have useful messages
[X] Relevant tickets are mentioned in commit messages

PR

[X] Self-reviewed the diff
[X] Useful pull request description
[X] Reviewer requested

If you updated any cabal files or added Haskell packages:

[ ] $(nix-build default.nix -A pkgsLocal.updateMaterialized) to update the materialized Nix files
[ ] Update hie-*.yaml files if needed

If you changed any Haskell files:

[ ] $(nix-shell shell.nix --run fix-stylish-haskell) to fix any formatting issues

If you changed any Purescript files:

[X] $(nix-shell shell.nix --run fix-purty) to fix any formatting issues

Pre-merge checklist:

[ ] Someone approved it
[ ] Commits have useful messages
[ ] Review clarifications made it into the code
[ ] History is moderately tidy; or going to squash-merge

@merivale - please take a look too.


bump(library-go): improve logging of what causes a static pod rollout

https://github.com/openshift/library-go/pull/293
https://github.com/openshift/library-go/pull/292

/lgtm
/approve

/refresh

/test all


Missing font

Got the error of missing font, I think.
File "D:\Repo\ComfyUI\ComfyUI\custom_nodes\ComfyUI-FatLabels\fat_labels.py", line 60, in calculate_text_size
font = ImageFont.truetype("/usr/share/fonts/truetype/dejavu/DejaVuSans-Bold.ttf", font_size)

Could you please include the font file or add a way to specify local font files to load?
Thanks.

Hey thanks, I noticed that error this morning. Yeah I'll try and investigate and update soon.


add support to store devicetree phandle+specifier as "foo_dt_spec" structures

#23245 improves the devicetree access solution significantly, but currently lacks a replacement for phandle-array values which are a series of phandle + specifier.  Example is a GPIO device reference plus a pin and initial flags; or an ADC device and and an input channel.  In the existing access solution a C initializer list is generated that captures the combined values, e.g. { "GPIO_0", 1, 0" }.
This gap complicates conversions of drivers that use the initializer list, e.g. the following:
-       .bus_name = DT_INST_0_MAXIM_DS3231_BUS_NAME,
+       .bus_name = DT_INST_BUS_LABEL(0),
        /* Driver does not currently use 32k GPIO. */
-#ifdef DT_INST_0_MAXIM_DS3231_ISW_GPIOS_CONTROLLER
-       .isw_gpios = DT_INST_0_MAXIM_DS3231_ISW_GPIOS,
+#if DT_INST_NODE_HAS_PROP(0, isw_gpios)
+       .isw_gpios = DT_INST_GPIO(0, isw_gpios),
 #endif
-       .addr = DT_INST_0_MAXIM_DS3231_BASE_ADDRESS,
+       .addr = DT_INST_REG_ADDR(0),

requires local addition of the following macro:
#define DT_INST_GPIO(inst, gpio_pha) {		\
	DT_INST_GPIO_LABEL(inst, gpio_pha),	\
	DT_INST_GPIO_PIN(inst, gpio_pha),	\
	DT_INST_GPIO_FLAGS(inst, gpio_pha),	\
}

to initialize the local definition:
struct gpios {
        const char *ctrl;
        gpio_pin_t pin;
        gpio_dt_flags_t flags;
};

Such a definition has not been standardized because technically different GPIO controllers could use different cells in their specifiers.
Where we have consistent cells for all drivers it would good to have a standard structure that can be used to store a phandle+specifier, and a way to initialize such a structure.
See discussion at/around: https://github.com/zephyrproject-rtos/zephyr/pull/23245#issuecomment-602649499

@mbolivar @galak let's discuss here rather than clutter up #23245

@pabigot collecting a list of where we want interim "LPF" style macros as discussed in #23245:

GPIOs
ADC

Interrupts also? Anything else?

git grep -e -cells  dts/bindings/ | sed -r -e 's@^[^:]*:\s*@@' | sort | uniq probably shows the candidates.  At minimum clock dma gpio interrupt io-channel (ADC) pinmux pwm may be candidates.  An issue is that the number of cells and their names/roles is binding-specific.

I've renamed the issue now that we are using 'foo_dt_spec' (e.g. gpio_dt_spec, i2c_dt_spec, spi_dt_spec) for this type of thing.

A status update as we head into v3.1: we have foo_dt_spec structures for the following cases, which overlaps somewhat with the above list.

gpio: added in https://github.com/zephyrproject-rtos/zephyr/pull/32805
adc: added in https://github.com/zephyrproject-rtos/zephyr/pull/43030 (not exactly io-channels, but more generally related to configuring ADC channels in DT)
pwm: added in https://github.com/zephyrproject-rtos/zephyr/pull/44523
spi: added in https://github.com/zephyrproject-rtos/zephyr/pull/36489
i2c:  added in https://github.com/zephyrproject-rtos/zephyr/pull/37359
reset: added in https://github.com/zephyrproject-rtos/zephyr/pull/43073
pinmux: won't do, but we now have DT-based pinctrl since https://github.com/zephyrproject-rtos/zephyr/pull/37572, so I'm proposing we consider that "done"

Still not done from the above list:  dmas and clocks properties are usuallly phandle+specifiers in DT, but have no corresponding spec structures in their zephyr APIs.
I would argue that interrupts does not fit within the scope of this issue, as it is a plain array, not a phandle-array, in terms of its type in the bindings.
The interrupts


Recompile fails when using environment configuration and ng serve -e=envName

Bug Report or Feature Request (mark with an x)
- [X] bug report -> please search issues before submitting
- [ ] feature request

Versions.
@angular/cli: 1.0.0-rc.1
npm: 4.2.0
node: v7.4.0

Repro steps.

Environment file located at src/environments/environment.dev.ts

This configuration in the .angular-cli.json
      "environments": {      "dev": "environments/environment.dev.ts",      "prod": "environments/environment.prod.ts"    }

Run ng serve -e=dev

Everything will compile fine the first time, go and make a small change and save one of your component files and it will fail to recompile.

You can use this repo branch as an example.
https://github.com/itmayziii/blog-ui/tree/Sjhx8HgD_contact_form/src

The log given by the failure.

Module build failed: Error: ENOENT: no such file or directory, open '/Users/txm241/Sites/blog-ui/src/environments/environment.ts'
Desired functionality.
I expect ng serve to recompile the app successfully.

Mention any other details that might be useful.

@itmayziii Is it still an issue. I don't see the branch on github.

I have a related, but slightly different issue. I created an environment named ua; when  I use it with ng serve --env=ua it works fine; unfortunately, when I change the software, the automatic rebuild reverts back to the default environment! Any thoughts on how to overcome this?

Closing in favor of https://github.com/angular/angular-cli/issues/6201, which seems to have the same root cause but contains a few more details.


[BEAM-12533] Define a __repr__ for DeferredDataFrame and DeferredSeries

Having a useful __repr__ is important for an API that may be used in an interactive context, as jupyter notebooks will call __repr__ on an object when it is the output of a cell. This PR adds an implementation for __repr__ that seeks to emulate the pandas implementation, but omits the data in order to make it clear to the user that the dataframe is deferred and has not yet been materialized.
The repr for a pandas DataFrame might look like this:
     index foofoofoo barbar  bazzy zoop
0        0       one      A      1    x
1        1       one      B      2    y
2        2       one      C      3    z
3        3       two      A      4    q
4        4       two      B      5    w
..     ...       ...    ...    ...  ...
595      1       one      B      2    y
596      2       one      C      3    z
597      3       two      A      4    q
598      4       two      B      5    w
599      5       two      C      6    t

[600 rows x 5 columns]

With this implementation a similar Beam DataFrame will be displayed like this:
  index foofoofoo barbar bazzy zoop
:     :         :      :     :    :
:     :         :      :     :    :

[?? rows x 5 columns]

A pandas Series:
0      A
1      B
2      C
3      A
4      B
      ..
595    B
596    C
597    A
598    B
599    C
Name: barbar, Length: 600, dtype: object

A Beam DeferredSeries:
: :
: :
Name: barbar, Length: ??, dtype: object

Note there's quite a bit of complexity in the implementation in order to deal with column and index names (and names for multiple levels of columns), as well as justification. Tests are added in frames_test.py::ReprTest to verify these cases.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

Here's what this looks like for a wordcount DataFrame in a colab notebook:

I'm 100% open to bikesheds about how this might be more intuitive. Maybe "..." is better than ":"? Maybe we should just display basic information instead of trying to replicate the pandas repr?

R: @robertwb @rohdesamuel
Note I still want to clean up the code here, but I'm interested in feedback on the approach.

I'm 100% open to bikesheds about how this might be more intuitive. Maybe "..." is better than ":"? Maybe we should just display basic information instead of trying to replicate the pandas repr?

I personally like your existing solution. There aren't many other symbols that can be used to signify an unknown or uncomputed quantity.

Discussed this offline with @robertwb and we decided that a simple approach that lists columns and index names (if non-trivial) would be better for now (e.g. DeferredDataFrame(columns=['foo', 'bar', 'baz'], indexes=[None, 'group']).
We could consider something like this again later on.

Ah, too bad, the formatted view was nice to see. lgtm

Closing in favor of  #15089


Tag StatisticalRethinking 2.0.5 - Initial version of plotcoef

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/9668
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if Julia TagBot is installed, or can be done manually through the github interface, or via:
git tag -a v2.0.5 -m "<description of version>" b38a06241650ed391896c9ea313a9f00bc327701
git push origin v2.0.5


Added directories needed for volume mounts to Git.

Also moves logs one level up to simplify navigation.
Fixes #2096.

This will break tests.

There is an explicit .gitignore for things under tests/logs, so this should reflect that also.
You also need to change tests/regression/config.ini to reflect where to find files.

Thanks @fzipi. I've made the fix. Not sure however, what you are referring to w.r.t. .gitignore. Do you mean, you want explicit ignore paths for the directories and readme files in the .gitignore file? I can do that but those are already covered by tests/logs(that path covers all nested files and directories, regardless of the level of nesting).

Thanks @theseion!
No, I was just saying that .gitignore has
# Ignore test logs
tests/logs/

And we need to change that to reflect the new situation. We don't want testers to accidentally commit error.log or access.log files.

Still not sure what you mean. I've made a change that I think you might want but I'm not sure...

I don't know how you added the files with that .gitignore :)
If you try to add files from that directory, it should not allow you... 🤔
❯ git add tests/logs/modsec2-apache
The following paths are ignored by one of your .gitignore files:
tests/logs
hint: Use -f if you really want to add them.
hint: Turn this message off by running
hint: "git config advice.addIgnoredFile false"

Oh, I see! 😄. You can always just git add -f somefile if you really want to add it and override .gitignore.
So, I guess I can revert those entries in .gitignore to simply tests/logs/. Do you agree?

Agreed. Thanks and sorry.

👍 No worries.

LGTM. Thanks @theseion for your contribution!


Open link in modal

Fixes #19

Requires https://github.com/origo-map/origo/pull/1833 to be merged


Get config always returns the current config generated irrespective of the trial number

Get config always returns the last config generated irrespective of the trial number in case of gRPC service. With REST service, get config returns -1 for all trial numbers except the current trial for which it shows the config.
To recreate follow the below steps:

Deploy HPO service - ./deploy_hpo.sh -c native
Post a new experiment - python grpc_client.py new --file=../tests/resources/searchspace_jsons/newExperiment.json
Get the config using - python grpc_client.py config --name petclinic-sample-2-75884c5549-npvgd --trial 0
Post the result - python grpc_client.py result --name petclinic-sample-2-75884c5549-npvgd --trial 0 --result SUCCESS --value_type double --value 5745.33
Post the next experiment - python grpc_client.py next --name petclinic-sample-2-75884c5549-npvgd
Get the config using both trial numbers or any random trial number that has not been generated so far
python grpc_client.py config --name petclinic-sample-2-75884c5549-npvgd --trial 10

I have posted the result for trial 0 & trial 1, trial 2 is the current config

(base) [csubrama@csubrama src]$ python grpc_client.py config --name petclinic-sample-2-75884c5549-npvgd --trial 2
{
  "config": [
    {
      "name": "memoryRequest",
      "value": 209.0
    },
    {
      "name": "cpuRequest",
      "value": 1.89
    }
  ]
}
(base) [csubrama@csubrama src]$ python grpc_client.py config --name petclinic-sample-2-75884c5549-npvgd --trial 0
{
  "config": [
    {
      "name": "memoryRequest",
      "value": 209.0
    },
    {
      "name": "cpuRequest",
      "value": 1.89
    }
  ]
}
(base) [csubrama@csubrama src]$ python grpc_client.py config --name petclinic-sample-2-75884c5549-npvgd --trial 1
{
  "config": [
    {
      "name": "memoryRequest",
      "value": 209.0
    },
    {
      "name": "cpuRequest",
      "value": 1.89
    }
  ]
}
(base) [csubrama@csubrama src]$ python grpc_client.py config --name petclinic-sample-2-75884c5549-npvgd --trial 10
{
  "config": [
    {
      "name": "memoryRequest",
      "value": 209.0
    },
    {
      "name": "cpuRequest",
      "value": 1.89
    }
  ]
}

@chandrams do you want me to fix this?

Thanks for fixing this @johnaohara
In optuna we aren't using persistent storage at present, does this mean all previous trial configs for which results are posted aren't stored anywhere in memory? Going through optuna docs. @khansaad - Do you know if the previous trial configs are stored in the study & can be retrieved?

@chandrams This opens an interesting question about experiment/trial persistence. I'll open an issue to discuss

I opened: https://github.com/kruize/hpo/issues/43


Image size problem

After training I run the test_frcnn, I got some bounding box cross the image boundary.
I set image_size to 500, and anchor size to [128, 256, 500],
I got some bounding box start with -16, or end up with 512?
What is the problem?
I think faster rcnn will remove the region proposal that cross the boundary?

faster-rcnn removes proposals that cross the boundary at train time, not at test time. Sometimes generated proposals cross the border -- feel free to clamp them to the border if it fits your needs.


Fix - the description of the return for the RLiveObjectService interface

The description of the return value is incorrect.
The return value of detach method of the RLiveObjectService interface is not proxied object.

Thanks for contribution!


css module import * as not work after upgrade to webpack5

Bug report
I had update webpack4 to webpack5, but some css module not work.
For example:
// ...
{
  test: /\.module\.css$/,
  use: [
    isEnvDevelopment && require.resolve('style-loader'),
    isEnvProduction && require("mini-css-extract-plugin").loader,
    {
      loader: 'css-loader',
      options: {
        importLoaders: 1,
        modules: {
          compileType: 'module',
          exportLocalsConvention: 'camelCase',
          localIdentName: '[name]_[local]_[hash:8]'
        },
        esModule: false
      }
    },
    // ... postcssLoader,
    // ... lessLoader
  ].filter(Boolean)
}
// ...

/* xxx.module.css */
.root {
	color: #fff;
}

not work

env

<EMAIL_ADDRESS><EMAIL_ADDRESS>

// a.jsx
import * as styles from './xxx.module.css'
import ss from './xxx.module.css'

console.log(styles) //  Module {__esModule: true, Symbol(Symbol.toStringTag): "Module"}
console.log(ss) // {root: "[name]_root_[hash]"}

work

env

<EMAIL_ADDRESS><EMAIL_ADDRESS>

// a.jsx
import * as styles from './xxx.module.css'
import ss from './xxx.module.css'

console.log(styles) //  {root: "[name]_root_[hash]"}
console.log(ss) // {root: "[name]_root_[hash]"}

I had read change log, so, it's because of tree-shaking? But i had set sideEffects: true, that not work.

What is the current behavior?
If css imported by import * as xxx from '*.css', the style not work.
If the current behavior is a bug, please provide the steps to reproduce.

What is the expected behavior?
import * as xxx from '*.css' work, likes webpack5

Other relevant information:
webpack version:  5.16.0
Node.js version: 12.13.1
Operating System: macOS Mojave
Additional tools:

You should not disable esModule (i.e. remove this option), not related to webpack

You should not disable esModule (i.e. remove this option or set esModule: true), not related to webpack

No. If esModule: true in option:

env

<EMAIL_ADDRESS><EMAIL_ADDRESS>

// a.jsx
import * as styles from './xxx.module.css'
import ss from './xxx.module.css'

console.log(styles) //  {}
console.log(ss) // {}

So, i think it's because of webpack.

No problems on webpack side, if you need help please open an issue in css-loader and provide simple reproducible test repo

No problems on webpack side, if you need help please open an issue in css-loader and provide simple reproducible test repo

Ok, thanks for you response.


Flask-User's UserMixin class breaks Flask-Admin's editor for unqiue fields

When using Flask-User v1.0, Flask-Admin cannot edit the user object anymore, but shows the "Username already exists" error. Inserting still works fine. When I remove the UserMixin from the class, editing in Flask-Admin works fine.
I know that this has been a common error with Flask-Admin in the past and you (@lingthio) even commented on that very issue.

Can you please investigate what part of the UserMixin class creates this conflict? -- I don't have a Flask-Admin app at hand. Thanks

Hi!
Thanks to @clarete's answer at https://github.com/flask-admin/flask-admin/issues/782, I've found that the issue is caused by the method override get_id() defined at https://github.com/lingthio/Flask-User/blob/master/flask_user/user_mixin.py#L16.
This overriden method get_id() is called from https://github.com/maxcountryman/flask-login/blob/master/flask_login/mixins.py#L41 and as it always returns a different value, the equalty comparison of the same object always returns False:
>>> u = User.query.get(1)
>>> u.get_id()
'gAAAAABdG435DHtkA0HVk1Nkzzb_TP9rMEk6YcenftZU2NnF3BaxEIyLMRu-6EcbjANHIXVidon0y1K7yeENEAeDPaG85b3rgg'
>>> u.get_id()
'gAAAAABdG437InvA0_j9eNcVbh7XqcgU3XZQ8KX9lTWgx_Mw8QtJSR9FMdOV1J9qlBF8TaOtvc6Tj9qOgRZEtg2uPyYp2L2cKQ'
>>> u == u
False
>>> u != u
True

The default get_id() implementation from flask-login basically returns the id field converted to a string and therefore it doesn't change in every call.
To workaround this issue, I've overriden the __eq__() method at my User class as follows:
    def __eq__(self, other):
        return self.id == other.id if other else False


audio_example-DEMO_PDM_RECORD_PLAYBACK

When trying to build the following case in audio_example:
#define DEMO_SELECTION                  DEMO_PDM_RECORD_PLAYBACK    (file: audio_task.h)
brings up the following error:
../audio_iface.c:32:34: error: 'sys_audio_pcm_specific_t {aka struct }' has no member named 'clk_generation'
device->pcm_param.clk_generation = HW_PCM_CLK_GEN_FRACTIONAL;
and indeed there is no field clk_generation in sys_audio_pcm_specific_t.
By commenting out the lines that create the error the build can be completed successfully, but then there is an error when trying to execute the example. Specifically after recording the audio the code is stuck in the following assert:
sys_audio_mgr.c(line:255) --> initialize_pcm_reg --> case I2S_MODE: -->
ASSERT_WARNING(param->total_channel_num == 2 * param->bits_depth / 8 );
SDK_<IP_ADDRESS> was used for the demonstration examples.
btw I see that there is an apu_demo project in the SDK that does pretty much the same things. What are the differences?

Hello,
the example comes with an SDK patch, did you try to apply it ?
clk_generation is one of the reasons why it is necessary to apply the patch first.
there are other things that will not work without the patch, as well.
Differences from the apu_demo include
-this and other bugfixes,
-optimizations for power consumption,
-being able to playback a reference audio file (with apu_demo you can only record audio from the microphone, and then optionally play it back)
-but most importantly it supports DA7212, DA7213, DA7217, DA7218 CODECs with official release HAL drivers which the apu_demo does not include.
In general the scope of the apu_demo was to demonstrate some audio functionality, while  the scope for this example was to showcase the usage of the DA721X  CODECs with the DA1469x.
I hope this helps,

I missed this one.
I had done it by commenting out the error lines but now with the patch everything is built.
Thank you!


customInternalAttach -> authorize -> errCallback undefined?

Echo Version
1.0.3
Laravel Version
10.38.1
PHP Version
8.2
NPM Version
10.1
Database Driver & Version
MySQL 8.0.35 on AWS RDS
Description
Just a minor one, but gets a bit spammy in Sentry. There appears to be cases where the overriden channel attach method is called with an undefined errCallback. It doesn't appear to have any impact on the end user, but it does get reported in Sentry at least a few times a day

https://github.com/ably-forks/laravel-echo/blob/master/src/channel/ably/attach.ts#L28
Wasn't sure if it would be fine to check if errCallback is defined before calling, or something more elaborate like this would be necessary:
https://github.com/ably/ably-js/blob/fdd5a566eafac0a7fae9592f890361a608794487/src/common/lib/client/realtimechannel.ts#L335-L339
Merry Christmas! 🎄
Steps To Reproduce
I haven't been able to reproduce this myself, but looking at the Sentry replays, it seems that users are idling, a request is made which 403s, and then the error above occurs.

@ryzr Thanks for reporting, seems we can modify check as
if (error && errCallback)

Since this is a small change, you might wanna create a PR for the same.

I have merged the PR. We will see if we can do the release in the near future. If you want to use the latest code on the master branch, you can include github url for the same in package.json dependency.
https://dev.to/michalbryxi/github-urls-in-package-json-5412

Seems we need to fix this properly, so I opened https://github.com/ably-forks/laravel-echo/pull/31

@ryzr please do add comments there if you find anything missing

Thanks @sacOO7 😄

@ryzr I have merged the PR. We will see if we can do the release in the near future. If you want to use the latest code on the master branch, you can include github url for the same in package.json dependency. https://dev.to/michalbryxi/github-urls-in-package-json-5412

@ryzr do update the code as per comment and let us know if you still facing issues with sentry.

@ryzr please do star https://github.com/ably/laravel-broadcaster and this repo if your issue is addressed 👍

Have done -  thanks again for all your help, I appreciate it! :-)


Cannot make callStatic

Current Behavior
For contracts like https://docs.uniswap.org/contracts/v3/reference/periphery/lens/QuoterV2
You may want to only do a static call to not spend money on the quote
When I try to do IWETH.callStatic.symbol() inside , I get this error
TypeError: Cannot read properties of undefined (reading 'symbol')
Expected Behavior
Would make the static Call
Steps to Reproduce the Problem

Prepare a IERC20 multicall contract
Make a static call like IWETH.callStatic.symbol()

Environment

Version: 3
Platform: Win
Node.js Version: 16

Hi, thanks for reporting. This issue seems to not be related to this package, as this package doesn't overwrite anything related to the contract object IWETH. Can you provide the exact code which leads to the error you describe pls?
Just confirmed locally that using this package, you should be able to access callStatic on contract objects.


GitHub App can only list public containers from repo

GitHub fine grained tokens, including the tokens generated by a GitHub Apps, do not have access to list all the containers associated with a repository.
In Minder's implementation of the GitHub App provider, we use a fallback token in order to list the containers associated with a repository. https://github.com/stacklok/minder/blob/f716baa8d6e97a5ef246c8afe1176dc8c44b07df/internal/providers/github/common.go#L169
However, this token only has access to public packages on public repos.
This is a limitation of the GitHub packages API.
There is currently no issue in the GitHub backlog that is tracking this feature, but is related to https://github.com/github/roadmap/issues/558.

@ethomson -- is this something we want to spend influence with GitHub on?

I've yelled about it to the PM, I'll yell about it some more, but it doesn't seem like something they're likely to fix in the near term.


fix: add error logging for request failures + remove load schedule qu…

…ery param

:tada: This PR is included in version 1.5.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


feat(actl-build): move actl-build to clipanion

affects: @atlantis-lab/actl-build
BREAKING CHANGE:
Breaks compatibility with @atlantis-lab/actl
ISSUES CLOSED: #124

Moved to https://github.com/Atlantis-Lab/actl/pull/123
Commit 4f90f11


What is the Latest version of Extent Reporting for C# - Selenium - Specflow? I am using version 5.0.0-alpha6 and have issue

Hi @anshooarora ,
I am using extent reporting version 5.0.0-alpha6 for C#, selenium and Specflow combination.
I have observed that sometime Steps for Pass scenario did not get expand once clicked on the Pass scenario in Report. Please see below screenshot

In this above screenshot, Pass scenario has three-four steps which are passed but in report it is not getting displayed even when I clicked on the pass scenario. Ideally when clicking on the pass/fail scenario, it should get expand and steps should display but it is not happening.
Need your help to resolev this issue ASAP.
Note: It is not happening for all the scenarios.

The first beta was released yesterday: https://www.nuget.org/packages/ExtentReports/5.0.0-beta1
There are several changes and fixes available. Please check and revert back if you continue to face this issue.

~The first beta was released yesterday: https://www.nuget.org/packages/ExtentReports/5.0.0-beta1~
Refer https://www.nuget.org/packages/ExtentReports#versions-body-tab for the latest available version.
There are several changes and fixes available. Please check and revert back if you continue to face this issue.

Hi @anshooarora ,
I upgrade to Extent reporting to 5.0.0-beta1but still facing the same issue. Could you please rectify it please.

Please share a sample report file with the behavior you've described.

Please share a sample report file with the behavior you've described.

Hi @anshooarora ,
I cant share the report(due to complaince) as it is my official project report. And to reproduce this issue I might need to have lots of sample TCs ( this will be little challenging for me to generate the Sample report)
Any other way I can help to make issue reproducible?

Closing since there was no response from OP.  Feel free to open a new ticket if you're still facing this issue.


Change a cluster's trust bundle

Main change
Support changing a cluster's additional trust bundle. Changes all locations where the additional trust bundle is stored in.
If an existing trust bundle is not found, this will cause an error, as creating the relevant resources is beyond the scope of this tool.
The trust bundle's validity will not be checked. When using a RECERT_CONFIG file, raw PEMS can be used instead of a path to a trust bundle file.
When using this feature it is recommended to also run the update-ca-trust script after running recert to ensure that the trust bundle is properly updated in all locations.
Other changes

Created ./hack/ directory to store some certs used during ./run_seed.sh

Deprecated --static-files and --static-dirs, which were used for both recert and rename. Now --crypto-dir and --crypto-file will be used for recert while --cluster-customization-dir and --cluster-customization-file will be used for rename (aka cluster customization). This was needed because /etc/pki is full of certs we discover and fail to process during recert, but we do need to process /etc/pki for editing the additional trust bundle cluster customization. Using --additional-trust-bundle along with --static-* will cause an error. The old behavior for --static-files and --static-dirs is maintained for backwards compatibility, but they cannot be used along with the new flags.

Made ConfigPath a less leaky abstraction for ClioPath and moved its relevant code to its own module path (under config)

Renamed many cli_parse functions to parse as those functions were used outside of CLI parsing as well (during config file parsing)

Refactored config parsing into topical functions because that functions was getting a bit too long

/test baremetalds-sno-recert-cluster-rename
/test e2e-aws-ovn-single-node-recert-serial
/test e2e-aws-ovn-single-node-recert-parallel

/test baremetalds-sno-recert-cluster-rename
/test e2e-aws-ovn-single-node-recert-serial
/test e2e-aws-ovn-single-node-recert-parallel

/lgtm
I tested it with LCA release-4.15, in order to verify backwards compatibility and everything looks good in that respect as well :+1:

/approve


Determine how to incorporate partial, malformed definitions

Part of handling and ingesting updates to AaC definitions will be to gracefully handle and reject malformed definitions.
AC:

[ ] Identify the need and application of 'unsafe' yaml parsing
[ ] Identify tooling and strategies to support gracefully handling malformed definitions
[ ] Identify the impact on LSP diagnostics for supporting malformed definitions (or don't publish diagnostics for malformed definitions)
[ ] Identify whether malformed definitions should update definitions in the language context, or if definitions can only be updated if correctly formed yaml

It won't directly resolve this, but I think the discussion in this PR comment is related.

I've been thinking on this approach. If we can prune malformed sections of the yaml definition, then we could provide diagnostics on the remainder of the definition.


Adding missing customerName property to fix S360 swagger correctness

ARM API Information (Control Plane)
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Azure 1st Party Service can try out the Shift Left experience to initiate API design review from ADO code repo.  If you are interested, may request engineering support by filling in with the form https://aka.ms/ShiftLeftSupportForm.
To fix the below S360 item:
https://vnext.s360.msftcloudes.com/blades/unifiedplatform?blade=AssignedTo:All~KPI:cf751b97-2c95-420f-baa8-9a16e8643a5b~SLA:1~Forums:All~_loc:UnifiedPlatform&def=&peopleBasedNodes=anr_team;vikdesai_team&tile=S360_ServiceId:a9305e6b-3d6c-477c-b3cf-1a81498037be~_loc:__key__UnifiedPlatform__cf751b97-2c95-420f-baa8-9a16e8643a5b&global=4:a9305e6b-3d6c-477c-b3cf-1a81498037be
https://portal.azure-devex-tools.com/amekpis/correctness/detail?errorId=503AA620-9782-4684-86AA-7E648EFE46E0
Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[ ] update existing version for new feature
[x] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month. - NA
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month. - NA
By default, Azure SDKs of all languages (.NET/Python/Java/JavaScript for both management-plane SDK and data-plane SDK, Go for management-plane SDK only ) MUST be refreshed with/after swagger of new version is published. If you prefer NOT to refresh any specific SDK language upon swagger updates in the current PR, please leave details with justification here.

Contribution checklist (MS Employees Only):

[ ] I commit to follow the Breaking Change Policy of "no breaking changes"
[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[ ] Check this box if any of the following apply to the PR so that the label "ARMReview" and "WaitForARMFeedback" will be added by bot to kick off ARM API Review.  Missing to check this box in the following scenario may result in delays to the ARM manifest review and deployment.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits. You can use OpenAPIHub to initialize the PR for adding a new version. For more details refer to the wiki.

[ ] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If you have any breaking changes as defined in the Breaking Change Policy, request approval from the Breaking Change Review Board.
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Additional details on the process and office hours are on the Breaking Change Wiki.
NOTE: To update API(s) in public preview for over 1 year (refer to Retirement of Previews)
Please follow the link to find more details on PR review process.

@us6193 ,you removed "NewApiVersionRequired" label, so I think you want to update this change in this exist api version, so I added "BreakingChangeReviewRequired" label

@kazrael2119 I have got the change reviewed and approved can you please help merging the change. thanks

@kazrael2119 I have got the change reviewed and approved can you please help merging the change. thanks

I can't approve because Swagger BreakingChange is failed

The swagger breaking change was failing saying there is a new property added compared to previous version for which we got the approval on, I have updated the tags accordingly and hopefully that should fix the issue. Can you help merge this asap as this is going to mark our services Red if this change is not merged sooner

The swagger breaking change was failing saying there is a new property added compared to previous version for which we got the approval on, I have updated the tags accordingly and hopefully that should fix the issue. Can you help merge this asap as this is going to mark our services Red if this change is not merged sooner

@us6193 , this change is adding property to a released stable version which is breaking change and should be approved by breaking change review board. You cannot add approval label, neither does me.

@raych1 Can you help me understand who needs to approve this then? As I already got approval from the review board

@raych1 Can you help me understand who needs to approve this then? As I already got approval from the review board

Can you share me where's the approval from breaking change review board? Can you ask Jeffrey or Mike to approve in this PR?

Got the change approved from breaking change approver:
https://msazure.visualstudio.com/One/_workitems/edit/23124358


std::bad_alloc while running TPC-DS Q4

Hi all,
We've been getting std::bad_alloc exceptions in TPC-DS Q4. The actual exception usually seems to happen in the JOIN stage between customer and catalog_sales (randomly stages 22, 30, 39), but not always.
The symptoms are that we see a high number of TaskManager::getResults calls... example:
I1101 18:14:26.092751 147346 TaskManager.cpp:592] TaskManager::getResults <taskId>.39.0.3, 1, 75
I1101 18:14:26.122815 147347 TaskManager.cpp:96] TaskManager::acknowledgeResults <taskId>.7.0.12, 10, 213
I1101 18:14:26.123914 152670 PrestoExchangeSource.cpp:90] Fetching data from <Host:Port><taskId>.7.0.1/results/3/257

Followed by allocation backoffs. In one, example I saw 94 of the backoff log entries
I1101 18:14:26.347635 152677 AsyncDataCache.cpp:587] Backoff in allocation contention for 16920 us.
I1101 18:14:26.347688 152670 AsyncDataCache.cpp:587] Backoff in allocation contention for 7425 us.
I1101 18:14:26.347718 152654 AsyncDataCache.cpp:587] Backoff in allocation contention for 38290 us.
I1101 18:14:26.347733 152684 AsyncDataCache.cpp:587] Backoff in allocation contention for 8619 us.

Finally the memory allocation related issue... (the actual place of the memory allocation failure can be different)
W1101 17:25:32.659839 143603 MmapAllocator.cpp:251] Could not advise away  enough for 294912 pages for allocateContiguous
E1101 17:25:32.735970 145039 Exceptions.h:68] Line: ../../velox/velox/exec/HashTable.cpp:505, Function:allocateTables, Expression:  Could not allocate join/group by hash table, Source: RUNTIME, Erro
rCode: INVALID_STAT

My current theory is that the random backoff delay (caused by high number of threads in allocation) is causing this issue, because the evict happens after the delay. So if there's a high number of concurrent allocation requests piled up, we don't try the "evict" fast enough... e.g. this part of the code in AsyncDataCache.cpp
    if (rank) {
      backoff(nthAttempt + rank);
    }
    ++shardCounter_;
    // Evict from next shard. If we have gone through all shards once
    // and still have not made the allocation, we go to desperate mode
    // with 'evictAllUnpinned' set to true.
    shards_[shardCounter_ & (kShardMask)]->evict(
        numPages * sizeMultiplier * MappedMemory::kPageSize,
        nthAttempt >= kNumShards);
    if (numPages < kSmallSizePages && sizeMultiplier < 4) {
      sizeMultiplier *= 2;
    }

I will be adding some more logs to get some more data around this point, but let me know if you have thoughts.
Thanks!
Explain plan for your reference:
Explain_TPCDS_Q4.txt

CC: @xiaoxmeng

CC: @oerling @tanjialiang

If you have a concurrent high demand for pages for buffering IO and making a hash table of 1.2GB, it can be that the 1.2GB gets evicted and then before the allocation is actually completed somebody else allocates just enough memory that there's  just a little less than the evicted size available when we get to the alocation itself.
So, whatever gets evicted on behalf of an allocation should be held in reserve and made not allocatable for anybody else. The structure is then probably that when the evict is done, we check that the free space is sufficient and then block all allocation for the duration. This is not very parallel but only applies to the relatively rare situation you are getting.

After trying some things out, here is what I've found.

In this query (for the join stage mentioned), the big fact table (catalog_sales) is getting hashed, thus requiring a lot of memory to hold this. (this is because our tables currently don't have stats, so CBO isn't working well...)
If I disable the Buffered Input Cache, then we quickly get "INSUFFICIENT RESOURCES" (VeloxRuntimeError:  Exceeded memory cap of 40.00GB when requesting 4.00MB.)
It looks like enabling Buffered input cache, we are not able to detect hitting the per-node memory limits, which seems to cause thrashing, and bad_alloc exception before the cleaner "Exceeded memory cap" error.
Increasing the per-node memory cap for the query (e.g. to 70GB) seems to resolve this issue.

So I'm guessing it's a problem of out configs/data sizings rather than an issue with the code. So closing the ticket.

Firstly, Prestoo is known not to do many of the optimizer tricks DS requires. But even so, it should know better than to build on th fact table.
Secondly, running from cache is necessary for any benchmarks. So, we must stop other activity if there is a large allocation that does not make progress while having concurrent small ones.
When you set the query limit to 70G and run with cache, what happens? What is the total data size and what is the total worker memory?
Now,

So some more findings (after changing various configs)
node.memory_gb=80
In Prestissimo, AsyncDataCache is being used for mappedMemory_. Also the value set on the size of this memory is by default 40GB. When I increase this by "node.memory_gb=80", then even with caching on, we get
VeloxRuntimeError:  Exceeded memory cap of 40.00GB when requesting 4.00MB
node.memory_gb=80, query.max-memory-per-node=70GB (Buffered Input Cache on)
The query runs successfully.
node.memory_gb=80, query.max-memory-per-node=70GB (Buffered Input Cache off)
The query runs successfully. This runs a bit faster (~10%) than without caching even vs consecutive runs of cache on.

Do the consecutive runs with cache actually hit? For example, is affinity on? (session property). If you have total memory set to 40 and query max to 80 then you will error out in the manner that you have seen. You could put a consistency check at startup to declra that query max is not over 90% of the max memory, i.e. capacity for AsyncDataCache.
Run the presto CLI with –debug . See where the data for the fragments comes from. ramReadBytes, localReadBytes, storageReadBytes.
If you have cache hits and it is worsre than no cache then we’d see the profile. Perf record –pid xxx for the worker.
What kind of platform do you run on? Local ssd? Data from S3 or HDFS?
Thanks
Orri
From: Uhyon Chung @.>
Sent: Wednesday, November 2, 2022 11:32 AM
To: facebookincubator/velox @.>
Cc: oerling @.>; Mention @.>
Subject: Re: [facebookincubator/velox] std::bad_alloc while running TPC-DS Q4 (Issue #3057)
So some more findings (after changing various configs)
node.memory_gb=80
In Prestissimo, AsyncDataCache is being used for mappedMemory_. Also the value set on the size of this memory is by default 40GB. When I increase this by "node.memory_gb=80", then even with caching on, we get
VeloxRuntimeError: Exceeded memory cap of 40.00GB when requesting 4.00MB
node.memory_gb=80, query.max-memory-per-node=70GB (Buffered Input Cache on)
The query runs successfully.
node.memory_gb=80, query.max-memory-per-node=70GB (Buffered Input Cache off)
The query runs successfully. This runs a bit faster (~10%) than without caching even vs consecutive runs of cache on.
—
Reply to this email directly, view it on GitHub https://github.com/facebookincubator/velox/issues/3057#issuecomment-1301055704 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AKPPPTZP6Q743TCCB32BCHDWGKXRTANCNFSM6AAAAAARUK6HEE .
You are receiving this because you were mentioned.Message ID: @.***>

Do the consecutive runs with cache actually hit? For example, is affinity on? (session property).
If you have total memory set to 40 and query max to 80 then you will error out in the manner that you have seen. You could put a consistency check at startup to declra that query max is not over 90% of the max memory, i.e. capacity for AsyncDataCache.
Run the presto CLI with –debug . See where the data for the fragments comes from. ramReadBytes, localReadBytes, storageReadBytes.
If you have cache hits and it is worsre than no cache then we’d see the profile. Perf record –pid xxx for the worker.
Ah, good question. I'll try out some of your suggestions here to get some more info.

What kind of platform do you run on? Local ssd? Data from S3 or HDFS?
Kubernetes on Debian linux. Data is from HDFS.


Readonly GPS and Accuracy fields.

Issue Reference
This PR addresses the Issue : Fixes #225
Summarize
Made gpsFIeld and accuracyFields as readonly, I hadn't noticed that someone also changed this. Sorry about it.

@irshadshalu can you ping me on slack