[L5.5] Plugin doesn't generate images

Hi Renatio,
I'm having trouble with images inside PDF. When I'm trying this code in template:
{% set config = {mode: 'crop', extension: 'auto'} %}

it gets me this PDF:

I have tried to debug template output by this snippet:
$pdf = App::make('dynamicpdf');
$user = UserModel::find(1);
$template = Template::byCode('rainlab::user');
dd($pdf->parseTemplate($template, compact('user')));

And it returns correct code with correct image path:

This code definitely works in previous versions, because I'm using it at User PDF export plugin and I also make some screenshots for plugin page, where user avatars are shown.
Do you know, where could be a problem please? Tried on latest October build 419 with Laravel 5.5.
Thank you very much!
Vojta

Hi,
please update plugin to allow Laravel 5.5 - https://github.com/mplodowski/DynamicPDF/commit/40259f5c78dfcd2e5166ea22c7f7ee3dfda3a282
In your code template change:

to

In your example there is no slice function, but when I installed your plugin it was there.
In plugins/vojtasvoboda/userexportpdf/behaviors/PdfExportBehavior.php:30 add following option:
'isRemoteEnabled' => true

I tested this and it worked with Laravel 5.5.

Hi Michal,
sorry for late reply. All changes were done: https://github.com/vojtasvoboda/oc-userexportpdf-plugin/commit/2d48be91559c3d98690292594e4852cc5915d96b
But the user avatar is still hidden + generate PDF takes about 2 minutes.
Could you please test it?
Thanks
Vojta

After I pulled your changes everything works fine. I have pdf with embedded avatar.
michal-michalplodowski-at-gmailcom.pdf
For isRemoteEnabled option to work, you must have this php settings enabled: allow_url_fopen=1.
Another approach will be to generate full path relative links.
Example:
/home/vagrant/code/october/storage/app/uploads/public/59b/1a1/e87/59b1a1e879d93974530641.jpeg

This can be done with getLocalPath() function on avatar like so {{ user.avatar.getLocalPath() }}.
I cannot find function to generate local path for thumbs. Probably you will have to make it on your own.


spec: Support ruby 3.1 and 3.3 error message formats

This message is different for ruby 3.3 and 3.1
Change phrase to be the common factor for both ruby versions
This is currently the only failure for 3.1/3.3 on master
(besides the gem changes)

Label says 3.2, but the title says 3.3 - do you know which one introduced the change?

update:

swapped a_string_matching back to a_string_including


Namespace-isolation policy should consider secondary brokers

Motivation
Right now, LoadManager is not considering secondary-brokers from NamespaceIsolation-Policy while selecting broker-candidates.
For example: if NamespaceIsolation-policies has primary and secondary brokers configured and if primary is not available then load-manager should only consider secondary brokers and should never look into shared-pool brokers.
Right now, load-manager is completely ignoring secondary brokers and always look into shared brokers if it doesn't find enough primary broker.
NOTE: Pulsar has this behavior from the beginning and both load-manager has the same behavior.
Modifications
Broker should consider secondary brokers while selecting broker candidate.
Result
Load-manager follows namespace-isolation policy correctly by considering primary and secondary brokers appropriately.

retest this please

retest this please

retest this please

retest this please


PHP 8.1 - TypeError: Memcached::setMulti(): Argument #2 ($expiration) must be of type int, int given

What steps will reproduce the problem?
Run the phpunit test with command
vendor/bin/phpunit --verbose --exclude-group mssql,oci,wincache,xcache,zenddata,cubrid --colors=always

What is the expected result?
Memcached related tests should be passed.
What do you get instead?
There were 3 errors:

1) yiiunit\framework\caching\MemCachedTest::testMultiset with data set #0 (0)
TypeError: Memcached::setMulti(): Argument #2 ($expiration) must be of type int, int given

/home/runner/work/yii2/yii2/framework/caching/MemCache.php:312
/home/runner/work/yii2/yii2/framework/caching/Cache.php:313
/home/runner/work/yii2/yii2/tests/framework/caching/CacheTestCase.php:125
/home/runner/work/yii2/yii2/vendor/phpunit/phpunit/phpunit:52
/home/runner/work/yii2/yii2/vendor/bin/phpunit:110

2) yiiunit\framework\caching\MemCachedTest::testMultiset with data set #1 (2)
TypeError: Memcached::setMulti(): Argument #2 ($expiration) must be of type int, int given

/home/runner/work/yii2/yii2/framework/caching/MemCache.php:312
/home/runner/work/yii2/yii2/framework/caching/Cache.php:313
/home/runner/work/yii2/yii2/tests/framework/caching/CacheTestCase.php:125
/home/runner/work/yii2/yii2/vendor/phpunit/phpunit/phpunit:52
/home/runner/work/yii2/yii2/vendor/bin/phpunit:110

3) yiiunit\framework\caching\MemCachedTest::testGetOrSetWithDependencies
TypeError: Memcached::setMulti(): Argument #2 ($expiration) must be of type int, int given

/home/runner/work/yii2/yii2/framework/caching/MemCache.php:312
/home/runner/work/yii2/yii2/framework/caching/Cache.php:313
/home/runner/work/yii2/yii2/framework/caching/TagDependency.php:96
/home/runner/work/yii2/yii2/framework/caching/TagDependency.php:54
/home/runner/work/yii2/yii2/framework/caching/Dependency.php:56
/home/runner/work/yii2/yii2/framework/caching/Cache.php:246
/home/runner/work/yii2/yii2/framework/caching/Cache.php:608
/home/runner/work/yii2/yii2/tests/framework/caching/CacheTestCase.php:285
/home/runner/work/yii2/yii2/vendor/phpunit/phpunit/phpunit:52
/home/runner/work/yii2/yii2/vendor/bin/phpunit:110

Additional info

Q
A

Yii version
2.0.43

PHP version
8.1.1

Operating system
Ubuntu 20.04

Current memcached version 3.1.5 is currently lack of support for both PHP 8.0 and 8.1 and there is a thread from the team to focus on this case.
Hence looks like those 3 failed tests are now depending on a new version of memcached.

Yes, can not be fixed from our side, I guess.

So what if we skip those tests that depend on memcache module for PHP 8.1 and enable them back once a new release from the team. Such as (inside MemcachedTest#getCacheInstance)
..
if (PHP_VERSION_ID >= 80100 && version_compare(phpversion('memcached'), '3.1.5', '<=')) {
    $this->markTestSkipped('memcached version 3.1.5 is not ready for PHP 8.1. Skipping.');
}
..

Yes, good idea.

thanks, so I prepare the pull request to handle this case for now.


Proxy doesn't seem to work, gives 404

To reproduce, launch ldnode locally, with a proxy parameter. Try to access an existing URL with that proxy. (Gives a 404).

How did you run ldnode?

I can confirm that running --proxy=/proxy works and --proxy=proxy doesn't.

@csarven I restarted databox2.com with that argument.   Give it a try?

I will fix this so that the trailing / is not required

On Mar 30, 2016, at 11:45 AM, Sandro Hawke<EMAIL_ADDRESS>wrote:
@csarven I restarted databox2.com with that argument. Give it a try?
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub

Ah, ok, yeah, seems to work with the leading slash. Happy to close this issue.

Actually, I think it is good to have the trailing slash since it gives a hint as to where it'll be available from. Perhaps the --help  or documentation should be clear. We all missed this "obvious" case so lets take that as a hint to improve. eg:
--proxy            Use a proxy on example.tld/proxyPath (eg '/proxyPath')

One more step: use default /proxy when no value provided with --proxy

@csarven I think it would be a security issue if I start a proxy on your server by default, is the proxy a mandatory tool in solid?

Does #307 work?

@nicola - yep, #307 works for me.
As for your other question, is proxy a mandatory tool in solid -- it is for the moment. I don't have any strong feelings about enabling it by default, though. Since clients use databox's proxy by default, it's probably fine either way.

Hardcoding any centralized server into the client is presumably a very-short-term workaround, and since that seems unnecessary here, I suggest by default proxy be on, unless there's a security risk.   As long as ldnode has a clear warning never to run it behind a firewall, it should be fine, I think.


Do not include event ids of closed events in CASEIDS command

Closes #187.
Needs to be first checked if this is the same behavior as with Zino 1.0.

Needs to be first checked if this is the same behavior as with Zino 1.0.

Seems consistent, according to my tests.  The main difference is that Zino 1 doesn't filter the events in the implementation of CASEIDS, rather it only indexes non-closed events.
However, it doesn't really matter how this works internally in Zino 2 as long as CASEIDS doesn't list closed events, and closed events cannot be reopened.


[k8s][cti] Add ct-k8s-status.sh

Summary
This script prints out all the cluster-test pods from the various cluster-test k8s clusters
Test Plan
./scripts/ct-k8s-status.sh

@bors-libra r+
Thank you!

:pushpin: Commit f461c25 has been approved by andll

@bors-libra r=andll

:pushpin: Commit f8f3f6f has been approved by andll

:hourglass: Testing commit f8f3f6f04898ade8f430893c6c25a702344ed5a1 with merge 8163ff876f03f15f1114542c9dec4ce818d25cc3...

:sunny: Test successful - checks-actions_land_blocking_test, checks-circle_commit_workflow
Approved by: andll
Pushing 8163ff876f03f15f1114542c9dec4ce818d25cc3 to master...


Citation tools

https://www.mendeley.com/
https://www.zotero.org/
https://www.citethisforme.com/
https://www.refme.com/

Tools to generate papers:

http://thatsmathematics.com/mathgen/
https://pdos.csail.mit.edu/archive/scigen/


Update specs2-core, specs2-scalacheck to 4.9.2

Updates

org.specs2:specs2-core
org.specs2:specs2-scalacheck

from 4.8.3 to 4.9.2.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.specs2" } ]

labels: test-library-update, semver-minor

Coverage remained the same at 95.205% when pulling 6c18a513ab0893cd56fc7df1b0899b16622243f7 on scala-steward:update/specs2-core-4.9.2 into 155c4ca5596b44cd9855dcca95406c1c19b512a6 on iheartradio:master.

Coverage remained the same at 95.205% when pulling 6c18a513ab0893cd56fc7df1b0899b16622243f7 on scala-steward:update/specs2-core-4.9.2 into 155c4ca5596b44cd9855dcca95406c1c19b512a6 on iheartradio:master.

Superseded by #138.

Superseded by #138.


ERESOLVE unable to resolve dependency tree

Hi!
When I try to install the package I get the following error:
npm i screen-space-reflections -S                                                                                ─╯
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/three
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!   peer three@">= 0.107.0 < 0.143.0" from<EMAIL_ADDRESS>npm ERR!   node_modules/postprocessing
npm ERR!     peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!     node_modules/screen-space-reflections
npm ERR!       screen-space-reflections@"*" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/screen-space-reflections
npm ERR!   screen-space-reflections@"*" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See /home/xxx/.npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/xxx/.npm/_logs/2022-07-17T18_19_51_727Z-debug-0.log

My project package.json looks like this:
{
  "name": "front-end",
  "version": "0.0.1",
  "scripts": {
    "dev": "vite dev",
    "build": "vite build",
    "package": "svelte-kit package",
    "preview": "vite preview",
    "prepare": "svelte-kit sync",
    "test": "playwright test",
    "check": "svelte-check --tsconfig ./tsconfig.json",
    "check:watch": "svelte-check --tsconfig ./tsconfig.json --watch",
    "lint": "prettier --check --plugin-search-dir=. . && eslint .",
    "format": "prettier --write --plugin-search-dir=. ."
  },
  "devDependencies": {
    "@playwright/test": "^1.22.2",
    "@sveltejs/adapter-auto": "next",
    "@sveltejs/kit": "next",
    "@types/cookie": "^0.5.1",
    "@typescript-eslint/eslint-plugin": "^5.27.0",
    "@typescript-eslint/parser": "^5.27.0",
    "autoprefixer": "^10.4.2",
    "eslint": "^8.16.0",
    "eslint-config-prettier": "^8.3.0",
    "eslint-plugin-svelte3": "^4.0.0",
    "postcss": "^8.4.14",
    "postcss-cssnext": "^3.1.1",
    "postcss-load-config": "^3.1.1",
    "postcss-nested": "^5.0.6",
    "prettier": "^2.6.2",
    "prettier-plugin-svelte": "^2.7.0",
    "svelte": "^3.46.0",
    "svelte-check": "^2.7.1",
    "svelte-preprocess": "^4.10.6",
    "tslib": "^2.3.1",
    "typescript": "^4.7.4",
    "vite": "^2.9.13"
  },
  "type": "module",
  "dependencies": {
    "@babylonjs/core": "^5.14.1",
    "@babylonjs/materials": "^5.14.1",
    "@fontsource/fira-mono": "^4.5.0",
    "@lukeed/uuid": "^2.0.0",
    "@three-ts/orbit-controls": "^1.4.7",
    "@types/three": "^0.141.0",
    "babylonjs": "^5.13.3",
    "babylonjs-loaders": "^5.13.3",
    "cookie": "^0.4.1",
    "gsap": "^3.10.4",
    "three": "^0.142.0",
    "three-gltf-loader": "^1.111.0",
    "three-orbitcontrols": "^2.110.3",
    "three-orbitcontrols-ts": "^0.1.2"
  }
}

Am I doing something wrong?
I'd really like to try this out - it just looks too good!
Thanks

The issue was that the effect required exactly<EMAIL_ADDRESS>as a peer dependency. I changed it so that it now needs at least version 0.141.0 of three.js. Higher versions will work too now.
Can you check if the issue is gone in the latest release (2.0.4)?

Ah great, I'm curious what exactly caused the issue with the red screen?

Hi!
When I try to install the package I get the following error:
npm i screen-space-reflections -S                                                                                ─╯
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/three
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!   peer three@">= 0.107.0 < 0.143.0" from<EMAIL_ADDRESS>npm ERR!   node_modules/postprocessing
npm ERR!     peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!     node_modules/screen-space-reflections
npm ERR!       screen-space-reflections@"*" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/screen-space-reflections
npm ERR!   screen-space-reflections@"*" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See /home/xxx/.npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/xxx/.npm/_logs/2022-07-17T18_19_51_727Z-debug-0.log

My project package.json looks like this:
{
  "name": "front-end",
  "version": "0.0.1",
  "scripts": {
    "dev": "vite dev",
    "build": "vite build",
    "package": "svelte-kit package",
    "preview": "vite preview",
    "prepare": "svelte-kit sync",
    "test": "playwright test",
    "check": "svelte-check --tsconfig ./tsconfig.json",
    "check:watch": "svelte-check --tsconfig ./tsconfig.json --watch",
    "lint": "prettier --check --plugin-search-dir=. . && eslint .",
    "format": "prettier --write --plugin-search-dir=. ."
  },
  "devDependencies": {
    "@playwright/test": "^1.22.2",
    "@sveltejs/adapter-auto": "next",
    "@sveltejs/kit": "next",
    "@types/cookie": "^0.5.1",
    "@typescript-eslint/eslint-plugin": "^5.27.0",
    "@typescript-eslint/parser": "^5.27.0",
    "autoprefixer": "^10.4.2",
    "eslint": "^8.16.0",
    "eslint-config-prettier": "^8.3.0",
    "eslint-plugin-svelte3": "^4.0.0",
    "postcss": "^8.4.14",
    "postcss-cssnext": "^3.1.1",
    "postcss-load-config": "^3.1.1",
    "postcss-nested": "^5.0.6",
    "prettier": "^2.6.2",
    "prettier-plugin-svelte": "^2.7.0",
    "svelte": "^3.46.0",
    "svelte-check": "^2.7.1",
    "svelte-preprocess": "^4.10.6",
    "tslib": "^2.3.1",
    "typescript": "^4.7.4",
    "vite": "^2.9.13"
  },
  "type": "module",
  "dependencies": {
    "@babylonjs/core": "^5.14.1",
    "@babylonjs/materials": "^5.14.1",
    "@fontsource/fira-mono": "^4.5.0",
    "@lukeed/uuid": "^2.0.0",
    "@three-ts/orbit-controls": "^1.4.7",
    "@types/three": "^0.141.0",
    "babylonjs": "^5.13.3",
    "babylonjs-loaders": "^5.13.3",
    "cookie": "^0.4.1",
    "gsap": "^3.10.4",
    "three": "^0.142.0",
    "three-gltf-loader": "^1.111.0",
    "three-orbitcontrols": "^2.110.3",
    "three-orbitcontrols-ts": "^0.1.2"
  }
}

Am I doing something wrong?
I'd really like to try this out - it just looks too good!
Thanks

sommerper Please contact me HQ#0001 (discord) or @Valorado (telegram)


Error E171: Missing :endif probably introduced by timers commit

I removed ensime from my ivy cache and regenerated the ensime configs.
Tested with the following config
call plug#begin('~/.config/nvim/plugged')
Plug 'https://github.com/ensime/ensime-vim', { 'commit': 'bdc8d35e7d6e195ce8305153ad3f542e280e2e06' }
call plug#end()

Neovim
NVIM 0.1.7
Build type: RelWithDebInfo
Compilation: /usr/local/Homebrew/Library/Homebrew/shims/super/clang -Wconversion -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -O2 -g -DDISABLE_LOG -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wvla -fstack-protector-strong -fdiagnostics-color=auto -DINCLUDE_GENERATED_DECLARATIONS -DHAVE_CONFIG_H -I/tmp/neovim-20170318-55698-1bprndh/neovim-0.1.7/build/config -I/tmp/neovim-20170318-55698-1bprndh/neovim-0.1.7/src -I/usr/local/include -I/usr/local/include -I/usr/local/include -I/usr/local/include -I/usr/local/include -I/usr/local/include -I/usr/local/opt/gettext/include -I/usr/include -I/usr/include -I/tmp/neovim-20170318-55698-1bprndh/neovim-0.1.7/build/src/nvim/auto -I/tmp/neovim-20170318-55698-1bprndh/neovim-0.1.7/build/include

Steps to reproduce

Use above neovim config and run :PlugInstall
Open a scala file

Expected behaviour
No error
Actual behaviour
Getting below error:
Error detected while processing BufEnter Auto commands for "*.scala":
error caught in request handler '~/.config/nvim/plugged/ensime-vim/rplugin/python/ensime.py:autocmd:BufEnter:*.scala ('server/src/main/scala/Application.scala',)':
Traceback (most recent call last):
  File "~/.config/nvim/plugged/ensime-vim/rplugin/python/ensime.py", line 176, in au_buf_enter
    super(NeovimEnsime, self).au_buf_enter(*args, **kwargs)
  File "~/.config/nvim/plugged/ensime-vim/ensime_shared/ensime.py", line 22, in wrapper2
    create_client=create_client)
  File "~/.config/nvim/plugged/ensime-vim/ensime_shared/ensime.py", line 95, in current_client
    create_client=create_client)
  File "~/.config/nvim/plugged/ensime-vim/ensime_shared/ensime.py", line 105, in client_for
    client = self.create_client(config_path)
  File "~/.config/nvim/plugged/ensime-vim/ensime_shared/ensime.py", line 124, in create_client
Error detected while processing function remote#define#AutocmdBootstrap:
line    7:
E171: Missing :endif

Reverting back to commit https://github.com/ensime/ensime-vim/commit/511f60911ecdeb6deb732d8a383892a0a1de63a8 works.

Did you run :UpdateRemotePlugins after installing?

Yeah
Also getting this error:
"server/src/main/scala/Application.scala" 277L, 12001C
Error detected while processing function 13[30]..<SNR>19_callback:
line   33:
Vim(call):error caught in request handler '~/.config/nvim/plugged/ensime-vim/rplugin/python/ensime.py:autocmd:BufEnter:*.scala ('server/src/main/scala/Application.scala',)':

I can confirm this error using neovim 0.1.7, ensime 1.12.9 and latest ensime-vim (via pathogen).
The interesting part of the error message seems to be the last lines:
line    7:
E171: Missing :endif

Some research indicates that this might be related to calling python from vimscript.

Please see this comment: https://github.com/ensime/ensime-vim/issues/386#issuecomment-290740703
As mentioned in the linked comment, I believe I have it traced back to EnTick not being registered correctly as a function in neovim. Yes, I am confident that I am running neovim that is loading a file that contains the definition for EnTick
The work-around prevents the error message, but I still have a non-functioning ensime. Looking at the .ensime_cache/server.log after performing the work-around I have Error: Could not find or load main class org.ensime.server.Server.
I'm using maven with scala 2.11 for my project, and another oddity that I noticed is that after running mvn ensime:generate, I get this message:
[WARNING] The POM for org.ensime:server_2.11:jar:2.0.0-SNAPSHOT is missing, no dependency information available

Given that, I searched my ~/.m2/repository for the mentioned jar file and it doesn't exist. Nor could I find a 2.0.0-SNAPSHOT version of ensime server in maven central: https://mvnrepository.com/artifact/org.ensime/server_2.11.
With the work-around in place, I can see that the ensime server is attempting to be started, and .ensime_cache/server.pid contains a pid. That pid, however, looks like this:
$ ps -ef | grep 20784
thegner  20784 20768  0 08:43 pts/0    00:00:00 [java] <defunct>

Please let me know if I can provide an further troubleshooting assistance.

I made quite the same observations as @travishegner using neovim.

@travishegner Ok. it seems that your build tool integration does not support generating ensimeServerJars field in .ensime so the error might be related to ensime-vim trying to bootstrap the server and some kind of incompatibility with the new timers approach. Any idea @Kazy ?
Could you please provide the .ensime file maven is generating?
Also it would be helpful if you started vim like this: ENSIME_VIM_DEBUG=1 vim and then attached your ensime-vim.log

@ktonga I had the same problem with EnTick by using a .ensime file generated by sbt. neovim claimed that EnTick command is not defined.

The error only exists with Neovim 1.7, but is fixed when using the current HEAD. The actual bug is this one: https://github.com/neovim/neovim/issues/5821. As mentioned in the issue, if you first do :call EnTick() before opening a Scala file, and then open it, it works correctly.
@ktonga: we can revert the commit until the fix is in a stable release (2.0 apparently). Since there is a (manual) workaround, I'll try to see if we can call the function to force Neovim to register it.

If some of you could test the fix with the following commit (https://github.com/Kazy/ensime-vim/commit/2ab94df5d5d1b59937e2faecb5dedea8ae0b651a) to confirm it works that would be great :)

Oh, that's why I'm not experiencing this issue, coz I'm on NVIM v0.2.0-dev
Ok @Kazy let's try to automate the workaround :smile:  I'd prefer that over reverting. If it isn't possible then we should revert.
Thanks for taking care so quickly.

@Kazy fix works for me. Using NVIM 0.1.7

@Kazy the work-around prevents the error message for me also. I'm still having a separate issue with mvn ensime:generate not downloading the correct ensime server version, so I will file a separate issue for that.

Good to know, thanks for testing !

I happened to stumble on this just now. I'm still having the issue even with the PR. Using NVIM 0.1.7 as well with ensime-sbt 1.12.9
"~/projects/voz/libraries/voz-common-core/src/main/scala/voz/common/AppName.scala" 27L, 1217C
Error detected while processing BufEnter Auto commands for "*.scala":
error caught in request handler '/Users/jacobbarber/.config/nvim/plugged/ensime-vim/rplugin/python/ensime.py:autocmd:BufEnter:*.scala ('libraries/voz-common-core/src/main/scala/voz/common/AppName.scala',)':
Traceback (most recent call last):
  File "/Users/jacobbarber/.config/nvim/plugged/ensime-vim/rplugin/python/ensime.py", line 179, in au_buf_enter
    self._vim.command('call EnTick()')
  File "/usr/local/lib/python2.7/site-packages/neovim/api/nvim.py", line 201, in command
    return self.request('vim_command', string, **kwargs)
  File "/usr/local/lib/python2.7/site-packages/neovim/api/nvim.py", line 129, in request
    res = self._session.request(name, *args, **kwargs)
  File "/usr/local/lib/python2.7/site-packages/neovim/msgpack_rpc/session.py", line 98, in request
    raise self.error_wrapper(err)
NvimError: Vim(return):no request handler registered for "/Users/jacobbarber/.config/nvim/plugged/ensime-vim/rplugin/python/ensime.py:function:EnTick"
Error detected while processing function remote#define#AutocmdBootstrap:
line    7:
E171: Missing :endif

I appear to have PR #389
jacob.barber ~/.config/nvim/plugged/ensime-vim (master) $ git log
commit 271d91b428033f40cb24173bf43e9662a1b1ccf0
Author: Boullier Jocelyn<EMAIL_ADDRESS>Date:   Wed Apr 5 19:54:20 2017 +0200

    Close #388: Adds workaround (#389)

    * Close #388: Adds workaround

    * Adds TODO comment for the removal of the workaround

My stacktrace is a bit different, so it might be a new issue.  I just saw mentions of EnTick in here and in my stacktrace so I figured I'd post here.

Does it happen consistently ? Did you run UpdateRemotePlugins ?

Ah, I didn't realize I'd have to run UpdateRemotePlugins.  It seems to work now, aside from this error which I assume is unrelated:
jacob.barber ~/projects/voz (master) $ cat ./.ensime_cache/ensime-vim.log
INFO     <2017-04-05 14:50:12,099> (client.py:83) - Initializing project - /Users/jacobbarber/projects/voz
ERROR    <2017-04-05 14:50:14,545> (client.py:212) - connection error: Handshake status 404
Traceback (most recent call last):
  File "/Users/jacobbarber/.config/nvim/plugged/ensime-vim/ensime_shared/util.py", line 48, in catch
    yield
  File "/Users/jacobbarber/.config/nvim/plugged/ensime-vim/ensime_shared/client.py", line 228, in connect_ensime_server
    self.ws = websocket.create_connection(self.ensime_server, **options)
  File "/usr/local/lib/python2.7/site-packages/websocket/_core.py", line 489, in create_connection
    websock.connect(url, **options)
  File "/usr/local/lib/python2.7/site-packages/websocket/_core.py", line 219, in connect
    self.handshake_response = handshake(self.sock, *addrs, **options)
  File "/usr/local/lib/python2.7/site-packages/websocket/_handshake.py", line 67, in handshake
    status, resp = _get_resp_headers(sock)
  File "/usr/local/lib/python2.7/site-packages/websocket/_handshake.py", line 123, in _get_resp_headers
    raise WebSocketBadStatusException("Handshake status %d", status)
WebSocketBadStatusException: Handshake status 404

@Jacoby6000 See https://github.com/ensime/ensime-vim/issues/386

:+1:


Q: Vue Template for ASP.Net Core 3 with Identity support?

Hello Team;
I just read the docs on Integrating Identity Server4 into Asp.Net Core for V3. Great news.
I also read the info on both sides (server and client) support when creating Angular or React client apps. And it seems like there are lots of helpers code written to make Angular & React apps quickly with authentication & Authorization. In a way it's great, but we use Vue Framework and some others might use vanilla JS client apps.
My question is, are you going to provide us a Vue template as well? If not, Could you please extend the docs, that is not so Angular or React focused and how we should use other client side frameworks to communicate with the Web API and the ASP server, that can talk to any type of SPA not just Angular or React?
Thanks!
..Ben

As we, that is ASP.NET, don't have Vue templates, no. We'd have to have Vue templates for everything, rather than just have a single template for one use case of a framework.
Docs however we can address. There will be a File New > Web Api with individual auth, which will just give you an api endpoint, and some URLs and then you have to do the hard work yourself. The hard work is the bit that needs documenting, it'd be something along the lines of the docs that third parties already have for Vu, e.g. https://www.richard-banks.org/2018/11/securing-vue-with-identityserver-part2.html
cc @DamianEdwards

@blowdart ;
Thank you Sir for the reply. I do agree with your comments. The reason I asked for Vue, because it seemed like Angular and React were the "chosen" Ones.
But a good docs/guideline on the Web API side would be great and we also need a JS SDK library that we can use on Vue side to authenticate the user just be passing email/password by simply calling a JS function as part of the SDK.
For example, Firebase Auth offers a very nice SDK library to sign up and login client user to backend Firebase Auth server. Something like that makes life a lot easier.
Thanks!

Well an SDK for Identity Server would, in all honesty, be their concern, or more likely a community concern. As it's not a framework with first party support in our product (which I guess does mean Angular and React were the chosen ones, although that's based on customer research and numbers), I don't see how we'd be comfortable attempting that.

Closing as old and someone else's problem really.

Closing as old and someone else's problem really.

The issue remains as a current & mutual problem, @blowdart  -- assuming developers have a say...
Stack Overflow - Developer Survey Results - 2019
Most Loved, Dreaded, and Wanted Web Frameworks


getUserMedia() error   Error: TypeError

I'm stuck on step 5 and 6, I keep on having these typeErrors when accessing http://localhost:8080 on browser. Help would be greatly appreciated. :)

yes .. chrome is error but firefox is ok.. You try firefox.   _

Thank you, moohyu.


[mini.ai] Implementation of builtin text objects w, W, p

Contributing guidelines

[X] I have read CONTRIBUTING.md
[X] I have read CODE_OF_CONDUCT.md

Module(s)
mini.ai
Description
Hi there, thanks for the amazing plugins! I've recently been looking into using mini.ai's textobject search to automatically generate targets for leap-spooky. However I've noticed that some text objects I was expecting to be there do not exist.
Here is the full list of 'builtin' ones according to the source I have:

I was just wondering what the reason is for the ommission of w (word), W (WORD) and p (paragraph)? And if it makes sense to add them in?

Hi!
Well, mostly because they are pretty good in their built-in implementation. That said, I miss sometimes the possibility to change the next word with cinw.
Implementing iW and aW should be pretty straightforward as there are %S and %s in Lua patterns for non-blank and blank characters.
Implementing iw and aw seems to be many times harder as Lua patterns recognize alphanumeric only for Latin alphabet. There is also an issue of respecting user settings like 'iskeyword'.
Making ip and ap is also possible, but not with Lua patterns.
I'll consider it, but don't think it will be added in 'mini.ai' builtin textobjects.

I see. Thanks for the info and quick response. I'll try and implement them as custom text objects on my side for now.


Contribute new package: Native Windows C++ library for EMC ECS S3 REST support

I have a new Windows C++ library:
https://github.com/EMCECS/ecs-object-client-windows-cpp
It is ready to be published in vcpkg.
I have tested x64, x86, dynamic and static builds.
What info do you need?

Hi bobk2824,
I am not 100% sure but I think only CMake-based builds are supported at the moment. This means you will have to write a CMakeLists.txt file containing all your source files, linker dependencies and build flags. Then, clone the vcpkg repository, add your package and create a pull request. See also https://github.com/Microsoft/vcpkg/blob/master/docs/examples/packaging-zlib.md for a short tutorial on how to contribute new packages.

@bobk2824 Thanks for the interest!
We definitely support MSBuild[1], however as @chausner suggests CMake makes it easier to express all the capabilities of Vcpkg.
To add a library to vcpkg, all you need to do is submit a PR adding a folder into ports\ that tells us how to build it! I also recommend the tutorial example that @chausner mentioned to get started with that.
[1] https://github.com/Microsoft/vcpkg/blob/master/docs/maintainers/vcpkg_build_msbuild.md

It was fixed in https://github.com/Microsoft/vcpkg/commit/13ec697c39ff6441393003f38635898b04d6d931#diff-df9c2d78ca7daa27b0fee9339fb95048


Oh no, Org Check had an error!

Describe the bug
While we are trying to access Apex Classes we are getting the error Oh no, Org Check had an error!
To Reproduce
Install org check and navigate to Apex Classes
Oh no, Org Check had an error!
More details:
Salesforce Information
Salesforce API Version: 62
Installed on OrgId: 00DAq000006Cx5i
Type of this org: undefined
Current running UserId: 005Aq00000MzWloIAF
Current Daily Api Requests: {"apiUsage":{"used":74,"limit":32007800}}
Navigation Information
Page: /apex/OrgCheck_ApexComponents_VFP
System Information
Language: en-GB
Issue #0: INSUFFICIENT_ACCESS
When: While creating a promise to call a SOQL query.
What:
index: 3
queryMore: undefined
queryString: SELECT ApexClassId FROM AsyncApexJob WHERE JobType = 'ScheduledApex'
queryUseTooling: undefined
Stack:
INSUFFICIENT_ACCESS: Requires Extra Verification
at r.getError (/resource/1730740070000/orgcheck__OrgCheck_SR/js/jsforce.js:1:72641)
at /resource/1730740070000/orgcheck__OrgCheck_SR/js/jsforce.js:1:71009
at /resource/1730740070000/orgcheck__OrgCheck_SR/js/jsforce.js:1:229493
at /resource/1730740070000/orgcheck__OrgCheck_SR/js/jsforce.js:1:229521
at MutationObserver.o (/resource/1730740070000/orgcheck__OrgCheck_SR/js/jsforce.js:1:104504)

Hello thank you for you ticket.
Can you upgrade the version of package your using in this org?
To do so, go to https://appexchange.salesforce.com/appxListingDetail?listingId=a0N4V00000HA0X2UAL
Then install the new package on the same org it will update the app.
I am sure it will solve your issue.

Hi Team,
Even after upgrading the org check to the latest version we are getting the same error.
Error details:
INSUFFICIENT_ACCESS: Requires Extra Verification
at r.getError (https://finning--athr--orgcheck.sandbox.vf.force.com/resource/1732058472000/orgcheck__OrgCheck_SR/js/jsforce.js:1:72641)
at eval (https://finning--athr--orgcheck.sandbox.vf.force.com/resource/1732058472000/orgcheck__OrgCheck_SR/js/jsforce.js:1:71009)
at eval (https://finning--athr--orgcheck.sandbox.vf.force.com/resource/1732058472000/orgcheck__OrgCheck_SR/js/jsforce.js:1:229493)
at eval (https://finning--athr--orgcheck.sandbox.vf.force.com/resource/1732058472000/orgcheck__OrgCheck_SR/js/jsforce.js:1:229521)
at o (https://finning--athr--orgcheck.sandbox.vf.force.com/resource/1732058472000/orgcheck__OrgCheck_SR/js/jsforce.js:1:104504)
at MutationObserver. (https://static.lightning.force.com/can2s.sfdc-58ktaz/auraFW/javascript/dzlEdDRVZ1RsVXFtVkduczVYNVVfZ1ZuNVJhc1EyaHA2ZTdMUkxCNEw5Y1E5LjMyMC4y/aura_prod.js:92:91773)
at e. (https://static.lightning.force.com/can2s.sfdc-58ktaz/auraFW/javascript/dzlEdDRVZ1RsVXFtVkduczVYNVVfZ1ZuNVJhc1EyaHA2ZTdMUkxCNEw5Y1E5LjMyMC4y/aura_prod.js:46:4529)

Do you have Shield Platform Encryption in this Org among with the following
setting:
Manage Encryption Keys is set to "Raise session to high assurance"
https://issues.salesforce.com/issue/a028c00000j5kSTAAY/insufficient_access-requires-extra-verification-while-deploying-metadata-when-manage-encryption-keys-is-set-to-raise-session-to-high-assurance
Le mer. 20 nov. 2024 à 00:39, apadole1 @.***> a écrit :

Screenshot.2024-11-20.at.5.07.14.AM.2.png (view on web)
https://github.com/user-attachments/assets/bcca6dd7-7317-4fed-a153-d6acadad89f9
Hi Team,
Even after upgrading the org check to the latest version we are getting
the same error.
Error details:
INSUFFICIENT_ACCESS: Requires Extra Verification
at r.getError (
https://finning--athr--orgcheck.sandbox.vf.force.com/resource/1732058472000/orgcheck__OrgCheck_SR/js/jsforce.js:1:72641
)
at eval (
https://finning--athr--orgcheck.sandbox.vf.force.com/resource/1732058472000/orgcheck__OrgCheck_SR/js/jsforce.js:1:71009
)
at eval (
https://finning--athr--orgcheck.sandbox.vf.force.com/resource/1732058472000/orgcheck__OrgCheck_SR/js/jsforce.js:1:229493
)
at eval (
https://finning--athr--orgcheck.sandbox.vf.force.com/resource/1732058472000/orgcheck__OrgCheck_SR/js/jsforce.js:1:229521
)
at o (
https://finning--athr--orgcheck.sandbox.vf.force.com/resource/1732058472000/orgcheck__OrgCheck_SR/js/jsforce.js:1:104504
)
at MutationObserver. (
https://static.lightning.force.com/can2s.sfdc-58ktaz/auraFW/javascript/dzlEdDRVZ1RsVXFtVkduczVYNVVfZ1ZuNVJhc1EyaHA2ZTdMUkxCNEw5Y1E5LjMyMC4y/aura_prod.js:92:91773
)
at e. (
https://static.lightning.force.com/can2s.sfdc-58ktaz/auraFW/javascript/dzlEdDRVZ1RsVXFtVkduczVYNVVfZ1ZuNVJhc1EyaHA2ZTdMUkxCNEw5Y1E5LjMyMC4y/aura_prod.js:46:4529
)
—
Reply to this email directly, view it on GitHub
https://github.com/SalesforceLabs/OrgCheck/issues/458#issuecomment-2486987564,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA47R2YVJMK3KT3LCZ5CYLT2BPD2BAVCNFSM6AAAAABSAJNMEOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBWHE4DONJWGQ
.
You are receiving this because you were assigned.Message ID:
@.***>

Hi Team,
We could see Manage Encryption Keys is set to "Raise session to high assurance" and could also see other permissions set to "Raise session to high assurance". Could you please help letting us know which permission should be changed as it is a sandbox org for customer's metadata analysis.

Hello
In my dev org i reproduced the error when one of the two options are set to either BLOCK or RAISE SESSION TO HIGH ASSURANCE

Manage Sharing
Manage Users

The help text of the option Manage Sharing is  Controls access to the Sharing Settings Setup page, the SharingRules object, and the CustomObject’s sharingModel field in the Metadata API.
The help text of the option Manage Users is  Controls access to the Users Setup page.
Clearly these two options have an impact when using Salesforce REST API to query the Organization table.
The query is SELECT Id, Name, IsSandbox, OrganizationType, TrialExpirationDate, NamespacePrefix FROM Organization LIMIT 1

Thanks Vince,
Will try to make changes in these permissions and will let update you on the same.
Best Regards!

Thanks Vince,
But could see both the permissions are set to NONE for this org. Should I change it?

Thanks Vince,
When I changed Manage Data Export setting to NONE, the issue got resolved. Cool!
Best Regards!

I think i will just document this error in the web site... Thank you for your participation on making Org Check a more stable tool.

Changed!
https://salesforcelabs.github.io/OrgCheck/installation/


Static Logger and SetCurrentLogProvider() in UnitTests

Hi
I'm having some issues with the current situation and LibLog 4.2, .NET 4.6.1, MSTest and the VSRunner, NCrunchRunner & Reshaprer Runner.
I'm using the SetCurrentLogProvider() method to use to set my own Logger which captures all log-calls for later assertion. This happens in different tests which may run in any particular order, parallel or not.
My DummyLibrary
public class MyLibrary
{
    static readonly ILog StaticLogger = LogProvider.For<MyLibrary>();
    readonly ILog instanceLogger = LogProvider.For<MyLibrary>();

    public MyLibrary(bool useInstanceLogger = false, bool useStaticLogger = false)
    {
        if (useInstanceLogger) instanceLogger.Info("New Library has been constructed");
        if (useStaticLogger) StaticLogger.Info("New Library has been constructed");
    }
}

Test
CaptureLogProvider
public class CaptureLogProvider : ILogProvider
{
    public List<string> StoredLogs { get; } = new List<string>();
    public Logger GetLogger(string name) => this.WriteCore;

    private bool WriteCore(LogLevel loglevel, Func<string> messagefunc, Exception ex, object[] fparams)
    {
        if (messagefunc != null)
            this.StoredLogs.Add(messagefunc());
        return true;
    }
    public IDisposable OpenNestedContext(string message) => null;
    public IDisposable OpenMappedContext(string key, string value) => null;
}

I figured out that when starting 2 tests a the same time (any runner), one of the two tests did not capture anything, while as the first test also only captured 1 entry. Please see basic test below, the second one is just a copy.
Tests
[TestMethod]
public void LogProviderInstance_StaticLogger_Test1()
{
    var p = new CaptureLogProvider();
    LogProvider.SetCurrentLogProvider(p);

    var lib = new MyLibrary(useStaticLogger: true);

    Assert.IsTrue(p.StoredLogs.Any());
    Assert.AreEqual(1, p.StoredLogs.Count);
}

[TestMethod]
public void LogProviderInstance_StaticLogger_Test2()
{
    /* Copy of first test */
}

Running these two tests at the same time does fail for the second one, while the first one also only captures 1 single log entry. As you see I created a new instance of the LogProvider for every test but the Logger in MyFramework itself is static. I experimented a bit with static/instance and added a couple of unit tests which gave me the following results

Test
LogProvider
Logger
Result

LogProviderInstance_StaticLogger
Instance
Static
Fail

LogProviderInstance_InstanceLogger
Instance
Instance
Passed

StaticLogProvider_StaticLogger_Test
Static
Static
Fail

StaticLogProvider_InstanceLogger_Test
Static
Instance
Passed

It looks like the SetCurrentLogProvider() only works reliable (or can be called multiple times) if the Logger gets created for each instance of MyFramework. That makes somehow sense by since the static keywork in the Framework-Class. But when following this explanation the number of logs should by 2 and not zero.
Summary
I'm raising this here, but I don't know if this is really an issue or my approach is just wrong and I should go in the direction as it is explained here: http://dhickey.ie/2015/06/capturing-log-output-in-tests-with-xunit2/ (as far as I understand that does not explain why there are zero entries in the static test)
The complete source-code is available here: https://gist.github.com/michaelschnyder/7475beeaaf223bc0dd3c82acc897bd2e

A little update here: the call to LogProvider.SetCurrentLogProvider does not replace the instance in the wrapper or forces LibLog to aquire a new logger by using the newly set LogProvider.
For my case where I had to assert specific Log-Calls, I'm using NestedContexts (LogProvider.OpenNestedContext() and store the log-messages in relation to the contexts.
But am still not sure if the behavior of SetCurrentLogProvider() is valid.

This one is related to the behavior: http://stackoverflow.com/questions/39272937/liblog-asserting-calls-to-the-logger
I'm now using a ConsoleLog Capturing mechanism, but that does not work with any version above 3.1 because LibLog does not write to Console anymore if no LogProvider is registered. See example here: https://github.com/jobbrIO/jobbr-server/blob/develop/source/Jobbr.Tests/Integration/Startup/ConfigurationTests.cs#L210
The issue somehow still exists if I would upgrade to > 3.1 but i would just need to set a CaptureProvider before any of the tests start.

@michaelschnyder For tests, I explicitly re-create the static Logger instance after setting the current Log Provider. This is a bit wonky, although it addresses the issues above.


new with on stage is even better than which with two stage

Hi Marek,
i run  DANtest.py  and want to know the performance of different stage. However, the result of the network with one stage is even better. The data set is initialized as the paper said.below is the test result.(i used center distance)
OneStage
Processing common subset of the 300W public test set (test sets of LFPW and HELEN)
Average error: 0.428566349505
Processing challenging subset of the 300W public test set (IBUG dataset)
Average error: 0.598229653794
Showing results for the entire 300W pulic test set (IBUG dataset, test sets of LFPW and HELEN
Average error: 0.461809522334
TwoStage
Processing common subset of the 300W public test set (test sets of LFPW and HELEN)
Average error: 0.439570144885
Processing challenging subset of the 300W public test set (IBUG dataset)
Average error: 0.616254202783
Showing results for the entire 300W pulic test set (IBUG dataset, test sets of LFPW and HELEN
Average error: 0.474188937071

@MarekKowalski Hi, in the training phase, did you hold the learning rate fixed to be 0.001?  If I use learning rate 0.001, then the loss in stage 2 cannot drop.

Yes, the learning rate was kept the same. When you are training the second stage are you updating the parameters for both stages or just stage 2?
In my experience, if you are updating parameters of both stages at the same time, the error takes much longer to drop.

@MarekKowalski  Actually, I only update parameters for stage 2, but I can see error drop only when I lower down the learning rate.

That's surprising, for how long are you trying to see if the error starts droping? Also, is that in your implementation or in the one in this repo?

@MarekKowalski  I mean in my implementation, I only observe error drop with my learning rate lower down. And, someone has found almost the same problem in another tensorflow implementation. I've double checked the functionality of the self defined layer and found no problem, I don't know if the Adam is implemented differently in theano, or Batch Norm is implemented differently.

@MarekKowalski @mariolew  Hi
In my implementation on tensorflow, I have not found this problem.
i use a private dataset , and epoch is [15,45]

i want to know if both stages share parameters in the same layer?

No the parameter values are not shared between the stages.
Marek


Fix broken links

Most of these links are only broken when rendered out of tree, e.g. on the OpenXLA website: https://openxla.org/stablehlo. For example, the "More Examples" links lead to e.g.
https://openxla.org/stablehlo/tests/interpret/add.mlir, which is 404.
For links under docs/ it is possible to use relative paths.
Also, add labels to images used in spec. This will materialize as the "alt" text, which is used by screen readers.

LGTM. Just an FYI: There are other links at the index page of https://openxla.org/stablehlo which needs simialar fixes. I can take on that.

Ah interesting. Good catch yeah it looks like some links in the README point to e.g. docs/, but on the OpenXLA website the relevant pages appear under the top-level rather than under some docs subdirectory.
Yes, please feel free to send a PR! :)


Added ApolloClientSetup

Components added:

ApolloClientSetup

This PR add the ApolloClientSetup component, which initialize apolloProvider using the authenticatication token.

/rebase

/merge


Move alpine lib/llvm CI to CirrusCI

It's faster to finish there.

More than twice as fast. Nice.


User request: set up the default sort order in studies

See https://lichess.org/forum/lichess-feedback/feature-request-study-sort-order-preference
The issue here is that you will probably want Hot for the general one and Alphabetical for your own studies.

I don't want to implement this. It would mean detecting what the user meant when coming to a specific URL, then changing it to another page. People would freak out and pages would get loaded twice. This is something Lichess should implemente.


Fix prettify script

The prettify script seems to have been broken in https://github.com/cloudflare/workers-sdk/pull/3341 , this PR fixes it (and also runs it)
(my guess is that the change was made when the monorepo still used npm so running a script did require the extra --)

Ah, sorry about that. I merged #3341 too hastily. It looks like now .prettierignore isn't being used at all, only the .gitignore provided via the CLI flag. Also, it looks like .gitignore is honored by prettier by default in v3, so we should instead focus our efforts on upgrading to v3. I'll revert #3341.

@1000hz cool, sorry I didn't remember that the gitignored gets honored now, sure reverting sounds good to me 🙂👍


Edit the camera frame when runs on Android simulator

I would like to add a frame to the camera, when it runs on android simulator, how can I do this?
Which specific file am I suppose to edit? Thanks

Does anyone know which file do I have to edit in order to make changes to the QR scanner frame for Android devices?? Thank you!


normalize group for null value

Form with submit btn doesn't work properly:
Warning: array_filter() expects parameter 1 to be array, null given in [FormRuleContext.php#L29](https://github.com/boekkooi/JqueryValidationBundle/blob/726f34e7c4cef101bf5b6b998346b342b45c42ed/src/Form/FormRuleContext.php#L29)

$builder->add('submit', 'submit');

I think the default value for group should be array and not null normalizeGroups

Hi @aitboudad
I'm unable to reproduce this error would it be possible to provide me with a example form + model? Also what symfony version are you using?
Thanks for reporting!

@boekkooi here is an example to reproduce issue:
    public function issues18Action(Request $request)
    {
        $form = $this->get('form.factory')->createNamedBuilder('')
            ->add('submit', 'submit')
            ->getForm();
        $this->handleForm($request, $form);

        return $this->render('::form.html.twig', array('form' => $form->createView()));
    }

Thanks for the very quick response this should be fixed now


Generate documentation

Based on https://compodoc.app/

Won't be necessary as this is not a library


Rush prettier pre-commit hook does not work with VSCode GUI

The Rush prettier pre-commit hook breaks when used with the VSCode GUI. Error output suggests that this is because VSCode is using its own version of node which does not abide the version constraint specified in rush.json:
ERROR: Your dev environment is running Node.js version v18.0.0 which does not
meet the requirements for building this repository.  (The rush.json
configuration requires nodeSupportedVersionRange=">=14.15.0 <15.0.0 ||
>=16.13.0 <17.0.0")

@adobe export issue to Jira project CAI


Conichi_Meta swift dependency hot fix;

This hot fix removes swift dependency from our SDK
@Antondomashnev we can work directly on the new splitted conichi_Meta to remove the Swift dependency there.
Having CNISDK.framework.zip and SampleProject.zip in our releases page will be fixed as part of referencing the new conichi_meta from all of our repos 👍.
The 2 zip files were updated manually as a hot-fix temporary solution since we won't have an SDK release before referencing the new meta.

          1 Error

:no_entry_sign:
No CHANGELOG changes made

  Generated by :no_entry_sign: Danger


Primitive not found

I'm building with the latest versions of everything onto my Mac.
This seems to build and install fine but when I run my app on my iPhone (10.2) I get the following error when InitIOS is called.
Primitive not found : admobex_init__MULT
AdMob.hx:101: iOS INIT Exception: Null Function Pointer

Can the documentation be updated with a list of component versions that this extension works with, as I expect I need to downgrade something.

I'm having the same problem.
Were you able to fix the problem?

Are you using a haxelib version, or you using the development version?
If you are using a development version, can you try and run lime rebuild extension-admob ios?
Thanks

I'm using haxelib version, but can definitely try development one.
Will let you know the results.

What was the trigger between it working and not working? Did any code change? Does this code get called after the new constructor in your Main class, or could it be that it's being statically initialized? Did you change or HXCPP versions?
In the development version, does it appear to have all iOS architecture files generated (such as arm64, armv7) or are there some missing?

I have never tried this extension for iOS before, so my first time.
After rebuild it has all the iOS architecture files generated.

Are there any tutorials on how to make extensions for iOS?
I guess, I have to look into this myself. :)

Like @pozirk, I've never had this working as I've only started looking at this for the past few weeks.
My machine has HAXE 3.4.2 and the following haxelibs installed.
actuate: [1.8.7] extension-admob: [1.6.4] extension-googleplayservices-basement: [1.1.0] haxelib: [3.3.0] hxcpp: [3.4.64] lime-samples: [4.0.1] lime: [4.0.3] nme: [5.7.1] openfl-tools: [1.0.10] openfl: [4.9.2]
Which looks pretty much the same as the list mentioned above.

So, I was able to narrow down the problem to this:

private static var __init:String->String->String->Bool->Bool->Dynamic->Void =
function(bannerId:String, interstitialId:String, gravityMode:String, testingAds:Bool, tagForChildDirectedTreatment:Bool, callback:Dynamic){};

Becase of the callback:Dynamic, it fires mentioned error message.
After removing callback, it started to work, but this callback is important as well.
So, @jgranick any ideas why this is happening?

@pozirk I don't think taking out the callback will make this work. It just stops the error from being displayed.

Yes, right, that's why I've checked first and it's working without callback.

@fbricker, any help with that??? :)

Having the same issue here with the haxelib version, pulled today (12th July) from haxelib.

It's fixed by @grazer, just take version for github and rebuild it.

Hum... odd, I still get:
Primitive not found : admobex_init__MULT
AdMob.hx:101: iOS INIT Exception: Null Function Pointer

I installed the branch from which the pull request was made:
haxelib git extension-admob git@github.com:grazer/extension-admob.git bugfix-prim_multi
The file seems to be the one with the fix:
$ cat /usr/local/lib/haxe/lib/extension-admob/git/project/common/ExternalInterface.cpp
#ifndef STATIC_LINK
#define IMPLEMENT_API
#endif

#if defined(HX_WINDOWS) || defined(HX_MACOS) || defined(HX_LINUX)
#define NEKO_COMPATIBLE
#endif

#include <hx/CFFI.h>
#include "AdMobEx.h"

using namespace admobex;

AutoGCRoot* intestitialEventHandle = NULL;

static value admobex_init(value *args, int count){
	value on_interstitial_event = args[5];
	intestitialEventHandle = new AutoGCRoot(on_interstitial_event);

	const char* banner_id_str = val_string(args[0]);
	const char* interstitial_id_str = val_string(args[1]);
	const char* gravity_mode_str = val_string(args[2]);
	bool testing_ads = val_bool(args[3]);
	bool child_directed_treatment = val_bool(args[4]);

	init(banner_id_str, interstitial_id_str, gravity_mode_str, testing_ads, child_directed_treatment);

	return alloc_null();
}
DEFINE_PRIM_MULT(admobex_init);

static value admobex_banner_show(){
	showBanner();
	return alloc_null();
}
DEFINE_PRIM(admobex_banner_show,0);

static value admobex_banner_hide(){
	hideBanner();
	return alloc_null();
}
DEFINE_PRIM(admobex_banner_hide,0);

static value admobex_banner_refresh(){
	refreshBanner();
	return alloc_null();
}
DEFINE_PRIM(admobex_banner_refresh,0);

extern "C" void admobex_main () {
	val_int(0); // Fix Neko init

}
DEFINE_ENTRY_POINT (admobex_main);

static value admobex_interstitial_show(){
	return alloc_bool(showInterstitial());
}
DEFINE_PRIM(admobex_interstitial_show,0);

extern "C" int admobex_register_prims () { return 0; }

extern "C" void reportInterstitialEvent(const char* event)
{
	if(intestitialEventHandle == NULL) return;
//    value o = alloc_empty_object();
//    alloc_field(o,val_id("event"),alloc_string(event));
    val_call1(intestitialEventHandle->get(), alloc_string(event));
}

But I still get the error. The xcode version I'm using is 8.3.2 (8E2002).

Did you rebuild the extension for iOS?: lime rebuild extension-admob ios

I had not, I've done it now, and it fixed it.
Thanks. 👍


Can we output CSS to a file? [Question]

Issue description:
Is it possible to grab the CSS from the output argument and export it to a file? I've been digging through the source and thought it would be faster to ask.
Version used: Latest

Look: https://github.com/aristath/kirki/issues/1323#issuecomment-301876440


Movement: Wall jump and slide

Add the ability to jump against walls, and have the character slowly slide down slowly while against the wall

With "ability" you mean a new Skill?
If so, Skills are following a State pattern, right?
Could you tell me if these snippets are on the lines for this task?
WallSlide
WallJump  <- These add a vertical gravity to make the walls behave like a floor, making the character perform an arc similar to as if it was on the floor jumping and moving horizontally.

Skill.gd is specific to the hook and likely to go out of the project. Check the Player scene, it uses a state machine now (look for the StateMachine.gd script and Player/**/State.gd)
The character shouldn't be able to climb on a single wall indefinitely imo: the jump is weak in the game, the hook is your main tool. The wall jump's purpose is to help you change direction upon hitting a wall without losing momentum, e.g. to reach a hooking point that's just a little too high otherwise. Another use would be to climb between two walls that are close to one another.
Regarding your snippets, I don't want things like dividing or multiplying the gravity depending on the context, as it makes the motion unreliable: change the world's gravity and the arc of your jumps won't be the same anymore in different states. I prefer the jump to always work the same way, even from a Wall.
For now, you can keep it simple. The wall should mainly feel good and support the core mechanic: the hook.
I would create a Wall state as a child of the Move state, define the wall motion there (e.g. sliding down), and use the Jump state to jump away from the wall. You can already use StateMachine.transition_to(state, msg={'velocity': ...} to make the player jump in the direction you want, using the velocity you want.
Check the Move and Jump nodes in the Player scene.


Script install instructions not available

There is no documentation on how to install the script under Linux.

At the moment what you need to do is either git clone the repo, or download repo as zip file and unpack it somewhere on your system. Then add the top level directory to your PATH.


Does not work with Termux on Android

Expected Behavior
To work
Current Behavior
Doesn't work
kubecolor get nodes
...

 This is important in case the issue is not reproducible except for under certain conditions.

Operating System: Android using Termux
kubectl version: 1.29.2
kubecolor version: 0.2.2

Interesting case 🤔 thanks @onedr0p for reporting this!
It sounds like you're using the Linux build on an Android. In this case, I believe you should compile it with GOOS=android
Your logs also suggests that you're running this via GitHub Actions. So just to verify, could you try compiling kubecolor inside your GitHub Actions workflow?
Such as:
steps:
  - uses: actions/checkout@v4
  - uses: actions/setup-go@v5
    with:
      go-version: '>=1.22.0'
  - run: go install github.com/kubecolor/kubecolor@latest

Your logs also suggests that you're running this via GitHub Actions. So just to verify, could you try compiling kubecolor inside your GitHub Actions workflow?

Not sure where you got that impression, I downloaded the binary from GH releases and tried running it in Termux.

Not sure where you got that impression, I downloaded the binary from GH releases and tried running it in Termux.

My bad! I got juked by the paths in the stack traces, like /opt/hostedtoolcache/... which is a GH Actions thing. But it's probably added from when the binary was built.
But still to just verify, could you try installing Go into your Termux and running:
go install github.com/kubecolor/kubecolor get nodes

If that works, then we'd know that we need to add an Android built to our releases

Yep that worked. I'm pretty curious why the Linux arm64 build won't work though?  They don't appear to have a build specific for Android.

Yep that worked. I'm pretty curious why the Linux arm64 build won't work though?  They don't appear to have a build specific for Android.
I wonder if there's a fix in the code to remedy this instead?

Good point. And hopefully we can solve this without adding a new build target.
However compared to the other tools you listed, only kubecolor tries to run other executables. And the thing it's failing on here is a Linux syscall that Android does not allow.
Go itself seems to have solved this by only changing the Android builds (https://github.com/golang/go/issues/57393).
Kubecolor is only using higher level functions (os.Command), so we don't actually invoke the syscall ourselves. So updating this may be tricky.
I'm not able to debug and test solutions at the moment. But will come back to it when I find some time and lust. (We're also open to contributions if you want to give it a go 😉)

Though kubectl does occasionally execute external binaries, such as with kubectl plugins and credentials plugins. But they don't seem to provide a specific android binary. So might be worth looking into if they've come across this too and solved it without needing an Android build too.

No worries, I'll keep with the Go installed version for now as it works fine. Hopefully sometime can work out what's happening here. Thanks 🙏

I checked kubectl's source code, and they do not do anything special when it comes to handling exec.LookPath syscall on Android.
I also tried out Termux and saw that the binary used there was compiled with GOOS=android
$ go version -m /data/data/com.termux/files/usr/bin/kubectl | grep GOOS
        build   GOOS=android

Termux seem to compile using GOOS=android for their own packages, installed via pkg install kubectl. (Termux build script for kubectl here) Which also explains why kubectl version reports v0.0.0, as they're not building kubectl completely correctly.
Another possible workaround I found was to supply the absolute path to kubectl:
export KUBECTL_COMMAND=$(which kubectl)

# Should work fine
kubecolor get pods

Because it's the exec.LookPath that's trying to use an illegal syscall and thereby causing a panic. In exec.Command only executes exec.LookPath if filepath.Base(name) == name. Though I've not tested this.

Of course, a better option would be to get kubecolor added to the Termux packages, and let it get that Android build.

Looks to be working, thanks!


Check table for invalid values when fitting

Is your feature request related to a problem?
When fitting a model, passing a table containing missing values or non-numerical data will result in either a numpy error or in all future predictions of the model being NaN.
Desired solution
In the InputConversionLayer, check the passed table for invalid data and throw a clear error if so.
Possible alternatives (optional)
No response
Screenshots (optional)
No response
Additional Context (optional)
No response

:tada: This issue has been resolved in version 0.27.0 :tada:
The release is available on:

v0.27.0
GitHub release

Your semantic-release bot :package::rocket:


Taints and Tolerations: When is noexecute taint added to the node

Its not clear from this doc when the taint for the node NoExecute is added. It definitely is added when the node is not ready, what other conditions is the taint to the node added and not for Memory Pressure.
It might help to clarify this behavior
https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/#taint-nodes-by-condition

/sig node
/sig scheduling
/language en

It definitely is added when the node is not ready, what other conditions is the taint to the node added and not for Memory Pressure.

You can definitely add the taint to the node while it is running and is ready. Reference given in the concepts section

You add a taint to a node using kubectl taint.

Please note that NoExecute is a taint effect technically.

Regarding Taint-by-Condition,
a list of other conditions that let node controller add taint to nodes has been given here
However, I think you want the taints to be explained like node.kubernetes.io/memory-pressure has been explained.
In Taint-based-Eviction, node.kubernetes.io/unreachable is also explained just the same.
More clarification on the request might be helpful.

Updated the question,  The article mentions the list of node taints available. I am looking for when the NoExecute taint is added by the node controller (the scenarios)

NoExecute is added to the node, in general, when an already present pod needs to be evicted.
A few examples are:

In case a node is to be drained, the node controller or the kubelet adds relevant taints with the NoExecute effect. If the fault condition returns to normal the kubelet or node controller can remove the relevant taint(s).
When the node is not ready and taint the taint node.kubernetes.io/not-ready with effect NoExecute is added
When the node is unreachable, Network is unavailable , apart from memory-pressure , disk and pid pressure also can have NOExecute added to the node.

I think explaining certain scenarios like the one explained for NoSchedule can clear this taint effect uses. There is certainly scope for some additions.
I'd wait for the sig/scheduling and sig/node people to share their expertise. or opinion on the addition of more relevant examples for Noexecute.

I am looking for when the NoExecute taint is added by the node controller (the scenarios)

BTW The eg. in Taint based evictions are all going to add NoExecute.

Thanks, I am closing the issue. I wasn't sure about the MemoryPressure Node scenario. Reading the documentation, it seemed to me that it should have the NoExecute taint but I didn't see it on the node


config.py: Remove corobo as default prefix

Removed corobo as default BOT_PREFIX
and added a check for empty BOT_PREFIX
Closes https://github.com/coala/corobo/issues/365
Reviewers Checklist

[ ] Appropriate logging is done.
[ ] Appropriate error responses.
[ ] Handle every possible exception.
[ ] Make sure there is a docstring in the command functions. Hint: Lookout for
botcmd and re_botcmd decorators.
[ ] See that 100% coverage is there.
[ ] See to it that mocking is not done where it is not necessary.

@Vamshi99 made the required changes :)

@KVGarg IMHO think we should leave those PR's separate since they are dealing with completely different issues. also our aim would be to get the build green upstream first and then deal with these PR's later.
Also we dont have gitmate now :( So these rebases will have to be done manually sigh:/

@KVGarg IMHO think we should leave those PR's separate since they are dealing with completely different issues. also our aim would be to get the build green upstream first and then deal with these PR's later.
Also we dont have gitmate now :( So these rebases will have to be done manually sigh:/

Ohh, OK 👍🏻


Develop process to output hOCR

Basic example with tesseract is here: https://github.com/UAlbanyArchives/arclight_integration_project/blob/main/scripts/tesseract.py
Also have a similar framework with Whisper for A/V.
Needs further testing.

This is done, might just need minor adjustments going forward.


High Performance Python - Gus Cavanaugh | PyData Global 2021

High-Performance Python - Gus Cavanaugh | PyData Global 2021
https://www.youtube.com/watch?v=ewaY9CcjLt0
00:00 Welcome
01:15 Faking a Scientific Workload
02:35 Working with Numba
05:19 About Gus Cavanaugh
07:19 About Rapids. Why do we need it?
12:27 What is Dask?
15:35 Using Dask
20:00 Summarizing everything up to now
23:07 Setting up Rapids
26:00 Running Numba in Dask
28:50 Ways to deploy Dask cluster
29:55 Cost of setting up a Rapids client and Dask cluster
31:05 Running everything in the local machine: The Afar package

Thank you!!


Blog-Title Sizing Glitch

This is what happens when i reload my screen. I feel like its something with the jquery editing the css.

once i resize my screen it sorts itself out.

Adding a mobile layout as well.


Use CollectPhase for realtime pk lookups

For primary key lookups, we want to retrieve the documents from the
primary shard which retains the latest state. Although the latest state
may not be reflected on disk or in the Lucene reader, the transaction
log holds the latest state. This is expose by Elasticsearch through the
"realtime" flag in the API.
We currently issue GetRequests with the realtime flag on the handler
node. This has some limitations because the lookup operation is not
distributed in the cluster. Additionally, the realtime aspects are
unavailable in sub selects.
The changes replace the ESGetTask on the handler node which issues
Elasticsearch GetRequests with a new CollectPhase called
PrimaryKeyLookupPhase. The new phase operates directly on the nodes
which are responsible for the relevant PK shards without any additional
routing.
There is still a limitation with this new approach when it comes to sub
queries. We resolve the location of the where clause keys (docKeys) on
the handler node before all symbols which might be contained in the
docKeys are resolved. An additional change is necessary to issue
conventional GetRequests for these keys. These could be performed on the
handler node. This extra step could be removed once the runtime supports
deferred plans which allow to build up a plan depending on its
dependencies.

Closing for now.


ENH: stats: seamless support for Pandas inputs

Describe your issue.
Another pre-test failure in statsmodels unit testing
https://github.com/scipy/scipy/pull/17561/files#diff-c850dba4f9919cabafa6e3ffbc1d0c61cf315d1e06755a867317fd891f9e2aaaR580
added [()] to results which looks like it breaks if the value is already a scalar
from failing unit test https://dev.azure.com/statsmodels/statsmodels-testing/_build/results?buildId=5078&view=logs&j=aabc21e9-9439-578e-0393-ea6ef34c273c&t=3c5b382f-2ffe-594f-225e-664c15c6a882
        # `axis`, `nan_policy`, and `keepdims` are handled by `_axis_nan_policy`

        if a.size == 0:
            return ModeResult(np.nan, np.int64(0))

        vals, cnts = np.unique(a, return_counts=True)
        modes, counts = vals[cnts.argmax()], cnts.max()
>       return ModeResult(modes[()], counts[()])
E       TypeError: 'int' object is not subscriptable

This goes from statsmodels through pandas and then scipy.stats
I cannot extract the example (with pdb) because I don't have dev versions installed
Reproducing Code Example
-

Error message
-

SciPy/NumPy/Python version and system information
scipy main

It could be the NaNs, which are Python floats instead of NumPy floats. It's fine with NumPy floats:
import numpy as np
x = np.float64(1)
x[()]

So this might have been fixed by gh-18217. Let's see if that does the trick.

It will only break if the value is a Python scalar.
import numpy as np
np.float64(1)[()]  # 1.0

I'll have to see what is producing a regular int.

In any case, for best results (for now), please convert the input to a NumPy numerical array before calling stats functions. Whether stats functions currently work seamlessly with pandas arrays is hit or miss, and I'm not aware of a policy that they should, so I'm changing this to an enhancement request.

I think in general there is a wish to support the array API and use this mechanism as a way to bridge the gap between various arrays and libraries. I think we can close this in favour of this work (I don't know the status here though. Last thing I've seen was #15395)

Whether stats functions currently work seamlessly with pandas arrays is hit or miss, and I'm not aware of a policy that they should, so I'm changing this to an enhancement request.

This does not sound quite right to me. @josef-pkt linked to the exact change that introduced a regression. By design, SciPy functions (for better or worse) start with coercing their array-like inputs to an actual numpy.ndarray with np.asarray. The linked PR removes an asarray call, and the @axis_nan_policy_decorator decorator does not add it back. So, unless I'm missing something, that is a regression and may also break other things.

I think in general there is a wish to support the array API and use this mechanism as a way to bridge the gap between various arrays and libraries.

Arrays are a separate topic from pandas series/dataframe and other array-like input. pandas.Series instances are not arrays and won't be covered by the work you're referring to.

pd.Series has a __array__ attribute, so we consider that array-like and supported - it cannot break like this. So I'm sure enough this is a defect that I changed the labels back.

That said, the reproducer is fairly simple but does run into a deprecation warning that for some reason the statsmodels CI does not show:
>>> s = pd.array([1, 2, 3], dtype="Int64")
>>> stats.mode(s, keepdims=False)
<ipython-input-15-0431395f3b31>:1: DeprecationWarning: Support for non-numeric arrays has been deprecated as of SciPy 1.9.0 and will be removed in 1.11.0. `pandas.DataFrame.mode` can be used instead, see https://pandas.pydata.org/docs/reference/api/pandas.DataFrame.mode.html.
  stats.mode(s, keepdims=False)
ModeResult(mode=1, count=1)

now is:
>>> s = pd.array([1, 2, 3], dtype="Int64")
>>> stats.mode(s, keepdims=False)
Traceback (most recent call last):
  Cell In[32], line 1
    stats.mode(s, keepdims=False)
  File ~/code/scipy/build-install/lib/python3.10/site-packages/scipy/stats/_axis_nan_policy.py:521 in axis_nan_policy_wrapper
    res = hypotest_fun_out(*samples, **kwds)
  File ~/code/scipy/build-install/lib/python3.10/site-packages/scipy/stats/_stats_py.py:511 in mode
    return ModeResult(modes[()], counts[()])
TypeError: 'int' object is not subscriptable

So there's two separate issues:

While pandas series instances are valid input to scipy.stats functions, that is only true if those series are backed by numpy arrays with regular numpy dtypes. In this case, Int64 gets turned into object dtype - that needs fixing in statsmodels.
It's unclear (to me at least) whether axis_nan_policy_decorator is correctly implemented. We have very few tests with custom array-like's, so we can't rely on our test suite; there must be clear coercion to numpy arrays.

TypeError: 'int' object is not subscriptable

What would be helpful here in SciPy is to finalize this deprecation:
DeprecationWarning: Support for non-numeric arrays has been deprecated as of
SciPy 1.9.0 and will be removed in 1.11.0.

and emit a clear exception for object array input. Here is a test case that doesn't rely on pandas:
>>> class ArrLike():
...     def __init__(self, x):
...         self._x = x
...
...     def __array__(self):
...         return self._x.astype(object)
...
>>> stats.mode(ArrLike(np.arange(3)))

@rgommers thank you for your interest in this issue. Here are some responses to your comments.

This does not sound quite right to me. @josef-pkt linked to the exact change that introduced a regression. By design, SciPy functions (for better or worse) start with coercing their array-like inputs to an actual numpy.ndarray with np.asarray. The linked PR removes an asarray call, and the @axis_nan_policy_decorator decorator does not add it back. So, unless I'm missing something, that is a regression and may also break other things.

One thing that is missing is that the decorator does add back the coercion to a NumPy array. If you execute the example above, you will find that a is an array by the time it gets into mode.
The other thing that's missing is that it was not it's not the addition of the decorator that caused the problem. If you remove the _axis_nan_policy decorator and coerce to a NumPy array manually, you get the same error.
The link provided by @josef-pkt pointed to something else being the problem, but that has not been changed for several years; it just happens to be the place where the error occurs.
The problem was caused by removal of explicit object support at the end of the deprecation period. If the pandas series were coerced to any NumPy data type instead of object, this would not be a problem. I can add a more explicit message, though.
--
When I wrote before:

Whether stats functions currently work seamlessly with pandas arrays is hit or miss

I should have been more specific.

Whether stats functions currently work seamlessly with pandas arrays with pandas dtypes is hit or miss.

stats is not unusual in having trouble with this input because, as you noted above, it gets converted to an object array. The first functions I tried in linalg and special, for example, failed with the same sort of input.
So is the action on SciPy's side to raise a more informative error about the input type?

The problem was caused by removal of special handling of object arrays at the end of the deprecation period.

That makes sense. And yes, an explicit check would be good. That's generically true I think if we deprecate support for some input type - we then have to check and raise a clear error. Also, the exception type has to be stable I'd say. NumPy itself raises TypeError mostly (and has a specific UfuncTypeError subclass of TypeError) for unsupported dtypes, so that seems like the best fit.

the nice thing is that as we discover more, we only have to treat them in one place. [...] We should add a test with custom array-likes now that this has come up, but as discussed, it's dealing with them correctly in this case.

Agreed, that's a good thing - and adding a specific test should resolve the issue here.

The enhancement I thought this was prompting was the ability to work on arrays that contain numeric data even if they get converted to object dtype.

I think that that's not a good way to go. NumPy itself is going to deprecate and remove automatic creation of object arrays when dtype=object is not explicitly specified. We should not try to support object arrays in SciPy.
Supporting Pandas data structures is a separate topic from object array support, and also from an "issue logistics" point of view I would start a new issue for that rather than re-title this bug report. Surprisingly, I can't find a tracking issue for pandas (or better, general dataframe) data structure support. This may become feasible - I guess we'll let scikit-learn invent this particular wheel, and maybe we can then copy their way of doing that.

IIUC, the actions on SciPy's side are to

Yes, that sounds right.
I wanted to do some quick tests of  _axis_nan_policy_factory from within IPython, and it failed with a hard to understand inspect.signature traceback:
>>> def f(x):
...     x
...
>>> _axis_nan_policy_factory(f)([1])
Traceback (most recent call last):
  Cell In[16], line 1
    _axis_nan_policy_factory(f)([1])
  File ~/code/scipy/build-install/lib/python3.10/site-packages/scipy/stats/_axis_nan_policy.py:612 in axis_nan_policy_decorator
    sig = inspect.signature(axis_nan_policy_wrapper)
...
ValueError: callable [1] is not supported by signature

That led me to look at that factory function closer, and it's using inspect quite a bit - which tends to be not a good idea at runtime. Aside from robustness, some benchmarking shows large performance regressions:
>>> import numpy as np
>>> from scipy import stats
>>> z = np.random.randint(10000)
>>> scipy.__version__
'1.10.1'
>>> %timeit stats.mode(z, keepdims=True)
47.9 µs ± 235 ns per loop (mean ± std. dev. of 7 runs, 10,000 loops each)

compared to main:
>>> %timeit stats.mode(z, keepdims=True)
229 µs ± 2.45 µs per loop (mean ± std. dev. of 7 runs, 1,000 loops each)

I have not been involved in review of that machinery - I assume some of this was discussed already? My first impression is that the ~250 line implementation of _axis_nan_policy_factory looks a bit scary.

#18265 (comment) also notes that the definition of "array_like" is quite broad (e.g. scipy.stats is "array_like", according to the definition) so use of "array_like" in the documentation may need to be qualified.
I will also look at what stats functions do work with object arrays with numerical elements. Is expanding support for this still an enhancement request?

In my opinion, no. I'll comment on gh-18265 instead. For this issue, let's close it once a clear exception is raised. I'll open a new one for the _axis_nan_policy issue.

On the statsmodels side, this seems fixed already in its main branch - see https://github.com/statsmodels/statsmodels/issues/8776.


Please add python3-attrs to rosdep

Please add the following dependency to the rosdep database.
Package name:
python3-attrs
Package Upstream Source:
https://www.attrs.org/en/stable/
https://github.com/python-attrs/attrs
Purpose of using this:
attrs is a widely used library for making data-oriented classes.
It was in the list with python2, and there are packages that specify it as a dependency with python3. (e.g. python3-twisted)
Links to Distribution Packages

Debian: https://packages.debian.org/

https://packages.debian.org/bookworm/python3-attr

Ubuntu: https://packages.ubuntu.com/

https://packages.ubuntu.com/jammy/python3-attr

Fedora: https://packages.fedoraproject.org/

https://packages.fedoraproject.org/pkgs/python-attrs/python3-attrs/

Arch: https://www.archlinux.org/packages/

https://archlinux.org/packages/extra/any/python-attrs/

Gentoo: https://packages.gentoo.org/

https://packages.gentoo.org/packages/dev-python/attrs

macOS: https://formulae.brew.sh/

not available

Alpine: https://pkgs.alpinelinux.org/packages

not available

NixOS/nixpkgs: https://search.nixos.org/packages

https://hydra.nixos.org/job/nixos/release-23.05/nixpkgs.python311Packages.attrs.x86_64-linux

openSUSE: https://software.opensuse.org/package/

https://software.opensuse.org/package/python3-attrs

Done!


No work

Hello this does not work NO CHECKER WILL WORK WITHOUT PROXY CHECKER AND AS THIS CHECK WITH YOUR IP THEN IT WILL NOT WORK WHY IS IT GOING TO BLACKLIST YOU THE IP FOR 1 WEEK FROM THE DISCORD API

This is not really an issue so I will just close it here


watch.BuildUpdate is not exported

Noticed that the watches.config have changed.
I have custom watches and I am using require("@ionic/app-scripts").buildUpdate  which is exported from build rather than watch, which is resulting in triggering build without doing anything else.

Ionic App Scripts Version: 0.0.43

I can do a quick PR if you confirm that the buildUpdate should be exported from the watch rather than build file.

Also, notice that "js" files are not handled within the function. For my project its mandatory to handle this.

Any update re this please? I really want to use the the debounce functionality in 0.0.43

@alan-agius4,
Can you do a PR with what you need?
Thanks,
Dan


Add support for hub specific IHubProtocols that don't affect other hubs

Fixes #15128
Might add some more tests later.

@davidfowl We need to get the API for this locked down today or tomorrow!

@Pilchie for 3.1 approval. This is fixing the Scaleout + Blazor + SignalR scenario. There is one public API change, we're adding a new constructor to the RedisHubLifetimeManager so we can inject some services from DI.

There is one public API change, we're adding a new constructor to the RedisHubLifetimeManager so we can inject some services from DI.

One thing to clarify is that users are not expected to construct this object. It is initialized in DI. We should have (and may in a future major release) made it an internal class, to be honest.

Has this fix been released in 3.1.100?

It should be in the 3.1.0 runtime. The version you linked is an SDK version but as long as you're using that SDK and targeting netcoreapp3.1 then yes, the fix should be present.

Thanks! It's strange that I'm still getting this issue then. Going to try and make a min repo.

Yep, please do and file a new bug if you're still seeing the issue.

Turns out it's an issue with Microsoft.AspNetCore.SignalR.Redis vs Microsoft.AspNetCore.SignalR.StackExchangeRedis the former doesn't work while the latter does.

Microsoft.AspNetCore.SignalR.Redis was replaced by Microsoft.AspNetCore.SignalR.StackExchangeRedis in 3.0 and is not expected to work past 2.2.


Featuwe weqwest: s-stuttewing

I wecommend adding s-stuttewing! P-pwease w-weffer tyu watashi's owoifier

I think this would make the syntax very complex


L5 - phpspec dependency could not parse

I get error when i create simple laravel project
composer create-project laravel/laravel project-map dev-develop --prefer-dist

I get following error
  [RuntimeException]
  Could not load package phpspec/prophecy in http://packagist.org: [UnexpectedValueException] Could not parse version constraint ^1.0.2: Invalid version string "^1.0.2"

  [UnexpectedValueException]
  Could not parse version constraint ^1.0.2: Invalid version string "^1.0.2"

Run composer self-update.

Thanks this works!

I just meet the same bug and solve it with composer self-update.
But I'm wondering why it did the trick?
Because only newest composer version accept the string number like "^1.0.2" ?

But I'm wondering why it did the trick?

Yeh. It's a new feature to composer, although not that new...


Rename relocation prefix of Caffeine producer cache provider

The previous relocation mistakenly was using the prefix of "org.springframework.pulsar.shade" when it should not be vendor specific and instead be "org.apache.pulsar.reactive.shade".
Fixes #127
cc: @cbornet @lhotari

LGTM, thanks.


*: enable initial corrupt check in tests

Fix https://github.com/coreos/etcd/issues/8909.

lgtm

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@5fbb459). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master    #8922   +/-   ##
=========================================
  Coverage          ?   76.04%
=========================================
  Files             ?      359
  Lines             ?    29787
  Branches          ?        0
=========================================
  Hits              ?    22653
  Misses            ?     5549
  Partials          ?     1585

Continue to review full report at Codecov.

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


Create and document examples/canvas/mesh_manipulation.py

This code was from a Planet Kivy blog post I ran across.  URL is in the docstring below.

Awesome addition! Thanks for all your pulls, they are of great value.

Patched in https://github.com/kivy/kivy/pull/3008.


Enable fluent and struct API for go SDK

One of the biggest problems integrations might face is that fluent API forces end users to use specific interface (chain of operations/builder pattern-like) solutions. In many cases, this will mean that migration between SDKv1 and SDKv2 will be quite painful.
This PR introduces a new method to the API object that can accept structs.
As result, users will get:

Clean, effortless migration path from v1 to v2 (removing a lot of manual steps and a complete rewrite of the data layer or even the application layer)
Access to individual resources without the need to duplicate all requirement
Simple means to understand what arguments are required for each API method (right now users need to discover various objects.

While this change might look big due to the number of files changed what we changing here is only a single template that adds a new method.
I will be looking to adopt this upstream as well. Change is not breaking - it doesn't affect any goals and existing documentation etc.
Notes about recent updates

I have made this feature experimental for now. Fluent API is still the default feature
I will focus on small breaking changes for fluent API in separate PR to simplify the review.
This PR contains all non-breaking changes for atlas CLI (tested end to end)

As an outstanding item, we might need to clarify what to do with not optional arguments (Those are now supplied to method that creates requests and cannot be avoided. I really wanted to avoid breaking change for fluent API

Biggest challenge/inconvenience of that approach is that we need to supply an struct to the API containing nonoptional fields that we already supplied, making it an bad api. We can eventually generate separate struct for that purpose but it would seem to be counterintuitive.

waiting on https://github.com/mongodb/go-client-mongodb-atlas/pull/464#discussion_r1188312909


Angular framework is not downloaded when running npm install - this conflicts with instructions in tutorial

npm install is not automatically using bower to download the Angular framework into the app/bower_components directory as mentioned in the tutorial at https://docs.angularjs.org/tutorial/

I've found an angular-route folder inside app/bower_components so there's no need to modify bower.json to get it. I guess the addition of angular-route line into bower.json raises the error since there are two directives in conflict.

I got the same "npm WARN cannot run in wd..." error in Terminal when running "npm install".
I got Angular into app/bower_components, by fixing my npm permissions (using Option 1), and then running "npm install" again in the /angular-phonecat directory.

I fixed this by changing the ownership of /usr/local and ~/Users/user-name like so:
sudo chown -R my_name /usr/local
This allowed me to do everything without sudo

cd angular-phonecat/
sudo bower install angular --allow-root
Thanks for you help^v^


Add AUC metric

Add efficient version of AUC metric, this should ideally only require a single pass over both the predictions, and the performance target.

Merged into main, will go out on next release.


Use partitioned aggregation for single-function DISTINCT aggregation.

This PR uses the partitioned aggregation routine for parallelizing DISTINCT aggregation. It improves the performance of TPC-H Q16 from ~10s to ~2s with scale factor 100 on CloudLab machine.

@jianqiao Please fix the build failures using gcc. See here for more info.


Train on my dataset

I want to use the cardiffnlp/tweet-topic-21-multi model from huggingface. But I want to add more labels/categories in the output. It is my understanding that I would need to manually train the model. Any guidance on how to do so?

If you need a model to cover additional labels, you need first to prepare a set of tweets annotated with the labels, and fine-tune LM on your dataset. As a reference, the tweet-topic dataset consists of around 1k tweets annotated over 21 labels.


How to show times with seconds?

I used this formatter:
SimpleDateFormat formatter = new SimpleDateFormat("HH:mm:ss");
but seconds were not shown

It would be great to add a parameter for timezone and rounding seconds

As mentioned in the README time zones are handled through the formatter. This is the correct way to return a date object and avoids the issue of accidentally applying a timezone offset twice.

Can you explain the scenario why you want to show seconds? It would help us to understand how/why the library should make it a parameter.

It is actually to know the exact time mentioned here http://praytimes.org/wiki/A_note_on_Dhuhr

The library already accounts for that situation. You can see the 1 minute added to Dhuhr for most calculation methods here https://github.com/batoulapps/adhan-java/blob/master/adhan/src/main/java/com/batoulapps/adhan/CalculationMethod.java

@z3bi
sorry to revive this case. i would think having the resolution to seconds is a good option here. rounding it to minutes is also a developer choice. it shows how much precise this library is

@Abu-Abdullah no need to apologize, one of the main goals of this library is for this to be developed in the open and allow for peer discussion of these important issues.
The main reason that we round to the nearest minute is that in our source material, "Astronomical Algorithms" by Jean Meeus he says that because the value we use for refraction is a mean value that shifts based on atmospheric conditions, accuracy beyond the nearest minute does not make sense.

Because of that I am hesitant to even provide the seconds, as it would make it seem that the equations are able to produce a level of accuracy which is not actually possible without knowing things like temperature, atmospheric pressure and other information.

The precision this library offers is by not doing any rounding of the intermediate steps or using "approximate" equations. The calculations are done with full precision and then the end result is rounded to the smallest unit which we can fully claim to be able to represent.

thank you for the informative answer


Whitespace formatting

Description
Whitespace is an issue in a couple spots on the main page.
Expected Behavior

Navigation menu and page title easy to read - separated by space.
Should not have two spaces between result count and label in "xxx performance tests run!"

fixed


Extend size and position should be in local space for the physics engin(s)

Closing #7407
I checked other physics demos and they dont seem to be influenced by this change, however it needs to be monitored

Please wait with merging

good?

Still fighting Oimo, I hope to be done very soon

After this commit oimo compounds work. I had to disable the bidirectional transformation transfer between oimo and babylon when using compound meshes. So, this will work:
https://www.babylonjs-playground.com/#492ZK0#32
Setting the position AFTER creating the impostors will not work (!). To update the position use the physics body's position parameter:
impostor.physicsBody.position.y = 10:
https://www.babylonjs-playground.com/#492ZK0#33
(Note that the demos will only work after merging those changes to babylon!!)
@deltakosh - good to go now.


_raw event handlers

currently all event handlers are wrapped [1] by domvm during initial redraw to:

additionally pass through vnode, vm, data
handle event delegation
facilitate passing parameterized args,
invoke the global onevent, if defined
execute e.preventDefault() and e.stopPropagation() if false is returned

there are cases when this wrapping & exec overhead can lead to undesirable perf degradation (e.g. scroll, resize, touchmove, mousemove, drag). therefore, we need an escape hatch.
the idea is simple: add a _raw = true property to the handler:
function handleDrag(e) {}
handleDrag._raw = true;

el("img", {src: "moo.png", ondrag: handleDrag});

if you ever need to dive back into the vtree, the vnode is always accessible via e.target._node.
[1] https://github.com/leeoniya/domvm/blob/3.x-dev/src/view/patchEvent.js

implemented in 92bcd14b2efc5fd7785c0b2ea862e9a0466acdc4


Work out where we want to use the new emails on the site

tips@, help@, and media@
Talk to Annette.
Do we want a general info@ or hi@ too?
AB#26

Closing and merging into https://github.com/keithamoss/demsausage/issues/71


Previewing of attachments instead of downloading them

This looks really cool. On a general note, is there a previewing feature planned, which maybe be also integrated into the plugin system. This could then be used for e.g. directly previewing pdf, pictures. And with plugin support also for wirewiz files. I imagine this like an api endpoint which returns html content that previews that file. This could then be easily integrated into every platform, also the app via a web view. And in addition, one could also implement custom editors, so that one could edit attachments in place, useful for tables, wirewiz files with live preview.
Originally posted by @wolflu05 in https://github.com/inventree/InvenTree/pull/5525#issuecomment-1713742018

Not stale

This looks really interesting, if plugins would support the rendering of specific file extensions, a kicad plugin could be made using this library which is currently in alpha.

Already on it ;-) we featured Thea's funding call in a newsletter a few months ago
embeds work pretty well but there are some "special" things to work around:

you need to provide a kicad file (not always ideal even in an internal PLM)
the number of spanned events is limited currently but she is working on it as far as I know

Still relevant

Still important


Use a mail implementation not api

Caused by https://github.com/jenkins-infra/account-app/pull/143
see https://github.com/jenkins-infra/helpdesk/issues/3195
I'm not 100% sure what's going on here.
Locally I got java.lang.NoClassDefFoundError: com/sun/mail/util/MailLogger
In production it's getting com.sun.mail.smtp.SMTPSendFailedException: 550 Unauthenticated senders not allowed
I was able to reset the users password from my local machine port forwarding to prod ldap with this change

Incoming fix for the CI error

Incoming fix for the CI error

sure I'm not on a laptop that can see that right now, so if you can handle this it would be appreciated 😄

cc @dduportal


Convert tests to gtests

This replaces the ad-hoc test harness we're currently using with googletest pulled in via a git submodule, and converts the existing tests to gtests.
The conversion was fairly crude and mechanical aiming for minimal changes to aid review.  We can make a second pass later to make more use of the facilities provided by gtest.
Aside from being generally nicer to write tests with a proper harness (and we need more and better tests), additional motivation for this comes from BMO bug 1314514 trying to remove the XPCOM dependencies from the cubeb tests, which is blocked on converting the existing tests to gtests.
Note, to build this branch, you must perform an initial submodule setup:

git submodule init
git submodule update

r? @padenot

Looks good. Do you know what's up with the failure on AppVeyor ? If that's an AppVeyor issue, we can simply merge. I can't retrigger (or I haven't found how).
I'll handle rebasing the lockfree queue on top of this PR.

appveyor/pr got caught out when I rebased and tried to grab a cset that no longer exists.  It seems to happen a lot with that particular builder; I'll dig around and see if there's a solution.


⚠ Samsung has degraded performance

In 4be3e4b, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2100 ms

Resolved: Samsung performance has improved in 7c9a7e3.


Revert changes in travis.yml

In #3786 we had some changes in travis.yml. Wait on fix for https://github.com/travis-ci/travis-ci/issues/9815. Then revert the sudo and dist change.

This was merged with https://github.com/LibraryOfCongress/concordia/pull/317
So this should be a candidate to get closed soon.

Since there is no activity since almost a year, I consider this solved.