Symfony\Component\Process expects an array not a string.

Summary

Oro\Bundle\InstallerBundle\Composer\ScriptHandler::setPermissions
In Process.php line 143:

[TypeError]
Symfony\Component\Process\Process::__construct(): Argument #1 ($command) must be of type array, string given, called in /var/www/html/vendor/oro/platform/src/Oro/Bundle/InstallerBundle/Composer/Permission
sHandler.php on line 111
Steps to reproduce
composer run-script post-update-cmd
or  composer run-script post-install-cmd
Actual Result
string(94) "ps aux|grep -E '[a]pache|[h]ttpd|[_]www|[w]ww-data|[n]ginx'|grep -v root|head -1|cut -d' ' -f1"
going through line 110 return new Process($commandline);
Expected Result
string(94) "ps aux|grep -E '[a]pache|[h]ttpd|[_]www|[w]ww-data|[n]ginx'|grep -v root|head -1|cut -d' ' -f1"
going through line 110 return new Process([$commandline]); // AS an ARRAY
Details about your environment

OroPlatform version: 5.0.2
PHP version: 8.1.4
Database (MySQL) version 8

Custom Dockerfile
Additional information
https://github.com/symfony/process/blob/5.4/Process.php

Oro\Bundle\InstallerBundle\Composer\ScriptHandler::setPermissions
string(94) "ps aux|grep -E '[a]pache|[h]ttpd|[_]www|[w]ww-data|[n]ginx'|grep -v root|head -1|cut -d' ' -f1"

In Process.php line 143:
[TypeError]
Symfony\Component\Process\Process::__construct(): Argument #1 ($command) must be of type array, string given, called in /var/www/html/vendor/oro/platform/src/Oro/Bundle/InstallerBundle/Composer/PermissionsHandler.php on line 111
Exception trace:
at phar:///usr/local/bin/composer/vendor/symfony/process/Process.php:143
Symfony\Component\Process\Process->__construct() at /var/www/html/vendor/oro/platform/src/Oro/Bundle/InstallerBundle/Composer/PermissionsHandler.php:111
Oro\Bundle\InstallerBundle\Composer\PermissionsHandler->getProcess() at /var/www/html/vendor/oro/platform/src/Oro/Bundle/InstallerBundle/Composer/PermissionsHandler.php:95
Oro\Bundle\InstallerBundle\Composer\PermissionsHandler->runProcess() at /var/www/html/vendor/oro/platform/src/Oro/Bundle/InstallerBundle/Composer/PermissionsHandler.php:81
Oro\Bundle\InstallerBundle\Composer\PermissionsHandler->getUsers() at /var/www/html/vendor/oro/platform/src/Oro/Bundle/InstallerBundle/Composer/PermissionsHandler.php:49
Oro\Bundle\InstallerBundle\Composer\PermissionsHandler->setPermissionsSetfacl() at /var/www/html/vendor/oro/platform/src/Oro/Bundle/InstallerBundle/Composer/PermissionsHandler.php:28
Oro\Bundle\InstallerBundle\Composer\PermissionsHandler->setPermissions() at /var/www/html/vendor/oro/platform/src/Oro/Bundle/InstallerBundle/Composer/ScriptHandler.php:196
Oro\Bundle\InstallerBundle\Composer\ScriptHandler::setPermissions() at phar:///usr/local/bin/composer/src/Composer/EventDispatcher/EventDispatcher.php:391
Composer\EventDispatcher\EventDispatcher->executeEventPhpScript() at phar:///usr/local/bin/composer/src/Composer/EventDispatcher/EventDispatcher.php:248
Composer\EventDispatcher\EventDispatcher->doDispatch() at phar:///usr/local/bin/composer/src/Composer/EventDispatcher/EventDispatcher.php:108
Composer\EventDispatcher\EventDispatcher->dispatch() at phar:///usr/local/bin/composer/src/Composer/EventDispatcher/EventDispatcher.php:228
Composer\EventDispatcher\EventDispatcher->doDispatch() at phar:///usr/local/bin/composer/src/Composer/EventDispatcher/EventDispatcher.php:125
Composer\EventDispatcher\EventDispatcher->dispatchScript() at phar:///usr/local/bin/composer/src/Composer/Installer.php:372
Composer\Installer->run() at phar:///usr/local/bin/composer/src/Composer/Command/UpdateCommand.php:241
Composer\Command\UpdateCommand->execute() at phar:///usr/local/bin/composer/vendor/symfony/console/Command/Command.php:298
Symfony\Component\Console\Command\Command->run() at phar:///usr/local/bin/composer/vendor/symfony/console/Application.php:1015
Symfony\Component\Console\Application->doRunCommand() at phar:///usr/local/bin/composer/vendor/symfony/console/Application.php:299
Symfony\Component\Console\Application->doRun() at phar:///usr/local/bin/composer/src/Composer/Console/Application.php:334
Composer\Console\Application->doRun() at phar:///usr/local/bin/composer/vendor/symfony/console/Application.php:171
Symfony\Component\Console\Application->run() at phar:///usr/local/bin/composer/src/Composer/Console/Application.php:130
Composer\Console\Application->run() at phar:///usr/local/bin/composer/bin/composer:83
require() at /usr/local/bin/composer:29

Internal issue ID: BAP-21304

@Daimyo7 as a workaround you can use an older version of composer (anything prior to 2.3.0 should work). All composer versions are available for download here - https://getcomposer.org/download/

Ok I'll update the Dockerfile and set
https://github.com/mlocati/docker-php-extension-installer/
Back to 2.3.0.
Give me a moment to test it.

Ok setting the composer back to 2.2 was able to pass over the command array type error.
Thanks for the response. I'll be sure to post a version of my Dockerfile later to a open project.


MSID: 98485 Version: 1 DOI: 10.1101/2<IP_ADDRESS>5316

MSID: 98485
Version: 1
Preprint DOI: https://doi.org/10.1101/2<IP_ADDRESS>5316
Step 1. Awaiting reviews
Editorial to post reviews via hypothesis
Useful links:

DocMap: https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v2/by-publisher/elife/get-by-manuscript-id?manuscript_id=98485
New model tracking: https://docs.google.com/spreadsheets/d/1_fHaoOy7hjyocptKtVJRijeNpUY4hBS7Ck_aVmx6ZJk/
Reviews on sciety: https://sciety.org/articles/activity/10.1101/2<IP_ADDRESS>5316

For trouble shooting (e.g. no Docmaps available):

DocMap issue addressing: https://miro.com/app/board/uXjVNCwK6EI=/
Explore DataHub DocMaps API: https://lookerstudio.google.com/reporting/4c2f0368-babb-4beb-b5b3-497e7e7b0f08/page/ejphD
Unmatched submissions and preprints: https://lookerstudio.google.com/u/0/reporting/9f86204f-3bf7-477c-9b18-5c5ef141bf69/page/p_gxi57ha93c
Unmatched manuscripts spreadsheet: https://docs.google.com/spreadsheets/d/15QcK8w-ssB7109RQEDtFpJPZ0J5HTGxoHa_2TtpMBbg/edit#gid=1336081641

Step 2. Preview reviewed preprint
Production QC content ahead of publication
Instructions:

QC preview: https://prod--epp.elifesciences.org/previews/98485v1
Update ticket with any problems (add blocked label)
When QC OK, add QC OK label to ticket and add publication date and time to https://docs.google.com/spreadsheets/d/1amAlKvdLcaDp5W8Z8g77NmkwbMF5n_u89ArSqPMO8jg
Move card to next column
(At end of the day post link in #enhanced-preprint and ask for PDF to be generated)

Useful links:

Preprint DOI :  https://doi.org/10.1101/2<IP_ADDRESS>5316
Confirm reviews returned by EPP: https://prod--epp.elifesciences.org/api/reviewed-preprints/98485/v1/reviews
To update the MECA path in the docmap: https://docs.google.com/spreadsheets/d/1mctCQuNFBjSn97Lihy7_vBO6z7-N-oqyLv4clyi6zHg

Step 3: Awaiting search reindex
This step adds the reviewed preprint to the homepage: https://elifesciences.org
The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.
Useful links:

Jenkins pipeline to reindex search can be triggered sooner or monitored here: https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 4: Published! PDF requested
Waiting for PDF to be generated
Useful links:

PDF tracking: https://docs.google.com/spreadsheets/d/106_XeDjmuBae7gexOTNzg60lapeqjl2aRn9DzupGyS8/

Step 5: Introduce PDF to data folder and git repo
Upload PDF to relevent folder in git repo https://github.com/elifesciences/enhanced-preprints-data/
Step 6: Done!

[ ] Kettle is on!

error: [ref-doi-conformance]  in reference (id=c21) does not contain a valid DOI: '10.1007/'.
error: [ref-doi-conformance]  in reference (id=c34) does not contain a valid DOI: '10.1186/'.
error: [ref-doi-conformance]  in reference (id=c37) does not contain a valid DOI: '10.1016/'.
error: [ref-doi-conformance]  in reference (id=c38) does not contain a valid DOI: '10.1038/'.


Eastwest gateway incorrectly applies DR

Bug Description
If mTLS for a destination is enabled via a DR in a namespace other than istio-system, the eastwest gateway will never get endpoints for the destination service.
This is due to the fact that the eastwest gateway still applies endpoint filters, which use the mtlsChecker. East-west's mtlsChecker will have no DR for the service (since the DR was not applied to the istio-system namespace) and will therefore assume the default non-mTLS setting, which means that the endpoint will be filtered from the east-west gateway.
Judging by the comment in that code, it appears this was intentional. However, I'm not sure that this particular case was considered or tested. Other parts of the logic for eastwest gateway ignore DR, and I suspect this should as well.
Version
head

Additional Information
No response

@howardjohn do you know if there is anything that can be done here? I know that this logic was added to deal with a vul.

@stevenctl I think the DR part specifically is actually not for the CVE, but rather to avoid accidentally sending non-mTLS traffic to EW gw (which fails). So to have that same check at the EW gw may not make sense?
Just the DR part - the rest is required.

@stevenctl are you still looking into this? Can I assign to you?

https://github.com/istio/istio/pull/39829#issuecomment-1179236417

not-stale. Need to verify #40243 fixed this. I don' think it did.


Fix DCAP build in docker

Fixes the issues mentioned in https://github.com/integritee-network/book/issues/33.

Superseeded by #1306, which is the same branch but not from my fork.


Portmaster: several ports are not loading

Two ports are not loading:

Blake Stone - Planet Strike
C-Dogs

further ports will be tested in the next few days
bstone-PS: purchased game files added from GOG.com
cdogs: game files included
system:
RG351V
ArkOS v2.0 (updated to 08222022)
Portmaster v6.55

Have you updated PortMaster to version 6.55?

The ports have been fixed.  Just redownload them through PortMaster.


Make MetaDataHandle handle all keys correctly

BEGINRELEASENOTES

Make the MetaDataHandle work corretly with DataHandles that do not have "/Event/" in their descriptor
Mark get and fullDescriptor as const as they don't mutate any internal state

ENDRELEASENOTES

Merging this as it is in order to let the wrapper PR move forward


Users/yuliang/server

Summary

Update Api interface:

topicName(for calling API): a new paramater with boolean type that specify if llm-server needs to generate conversation topic
topicName(for return value): conversation topic(string) | undefined(if topicName != true)
test.html for usage example

Modify prompts:

remove export statement, add render statement
remove import statement
modify package usage

Delete Unused Componenet "LLM"

Screenshot
upload the screenshot of the changes made
Checklist

[x] My code follows ESLint rules and passes all tests.
[x] I have updated the documentation accordingly.

Unused Componenet "LLM" is deleted since it causes lint to fail after API is updated


There is no full implentation  to 5-node cluster

In  roles/tb/tasks/main.yml need to add support to adding secondary tie-breaker and add the support to switch to 5-node cluster.

Working on this...currently looking at a way to loop or define it in group_vars/all

With version 64a69a9c it should now be working


Wrong layout/icons on new georeference results modal

use new icons and layout:

[x] no georeferenced data (points)

[x] no georeferenced data (polygons)

[x] geocoding succesful - default

[x] geocoding successful - no cost

[x] geocoding successful - cost

Remember it depends if they are points or polygons

 looks like this one doesn't match either

We have a similar version on the last file version that I sent to slack

Yep, I saw it, just added the screenshot above to remember fixing it when updating this

Please, @viddo, take care of this plural bug.

Thanks

@josecruz updated the description with the new screens I found in the sketch file, are there screens missing or other things that are expected to be fixed here that is not already listed?

To avoid having redo things again: I'm observing that the margins are not consistent with existing modals

the icon + title are varying between 16px and 11px, in the existing modals it's always 20px.
the title is 16px, in existing modals they're all 18px
the description text is 14px, in the existing modals they're all 15px
the go back button text has color #666, in existing modals they're all #bbb

I find it weird that we are not consistent in the existing styles. I'm all for changing but shouldn't we update all places then?

Okay, so changing it on the sketch file. Probably the rest of the modals on the sketch files aren't updated as well (I just copy/pasted them from another sketch file). Thanks for spotting this! Let's use production styles

merged in #4567


Tearing or hard-to-see goo in bulbs

When there's a relatively small amount of goo in a bulb it's hard to see, and also results in some funky z fighting due to just being a really small amount.
Make it so that even at small values, minimal amounts of goo still have a relatively substantial enough presence in the bulb to avoid tearing and make it easier to see.

Fixed in the next release; minimum of 1% visibility on all goo at any amount keeps things visible.


feat(@angular/cli): option to build and test only specified spec files

A new --spec option is added. It is a glob/pattern that specifies which specs should be included in the build.
Command:
ng test --spec=app/services/auth*
When karma is already running, selected spec can be updated by running following command:
ng test --spec=app/login* --spec-update
Few rules are applied to the pattern to make certain things possible:

.spec.ts is added automatically if missing (less typing)
if it ends with *.ts and doesn't have .spec.ts, extension will be replaced with .spec.ts
if path starts at root, source root directory will be trimmed. So that you could use relative file path from editor to make custom tasks to run the command

Behind the scenes a new test.generated.ts is saved next to original test.ts which instead of using require.context imports all matching files. This gives quite a big boost in the project at work (at least 10s on each iterative build!)
 Takes almost a minute with 4000+ tests and barely works when code coverage is enabled.
Missing: docs(?)
Example tasks for vscode:
{
  // See https://go.microsoft.com/fwlink/?LinkId=733558
  // for the documentation about the tasks.json format
  "version": "2.0.0",
  "tasks": [
    {
      "type": "shell",
      "label": "test selected spec",
      "command": "node_modules/.bin/ng",
      "args": [
        "test",
        "--spec",
        "${relativeFile}"
      ],
      "problemMatcher": []
    },
    {
      "type": "shell",
      "label": "switch selected spec",
      "command": "node_modules/.bin/ng",
      "args": [
        "test",
        "--spec",
        "${relativeFile}",
        "--spec-update"
      ],
      "problemMatcher": [],
      "isBackground": true
    }
  ]
}

PS. The setup for writing tests is quite nice!

@FDIM heya, we got together and discussed this PR yesterday. This PR adds two new pieces of functionality: running targeted specs, and changing the targeted spec of a running process. We feel there's a lot of value in the former, but comparatively less so in the latter since it's a subset of the usescases of the first.
The main gripe the team has with it is the temporary file. In this PR the temporary file is used to transform the original test code via regexes running it, and communicate between processes when updating the targeted spec
Creating temporary files on disk has a few problems though:

requires a migration of existing projects (via ng update) to ignore it on git
it's surprising for users that files are created in their sources
it can remain on disk despite best efforts to remove it (e.g. process crash)
multiple targeted spec runs will interfere with each other because they use the same temp file

So for now we'd like to not add the temporary file at all. There are some ways of limiting the specs without it so we can still have targeted specs. But changing targeted specs mid-run without it would not be easy. So for now we propose to have targeted specs but not changing them on the fly, and later we could add a way to do that as well.
If we ignore the cross process communication we could easily avoid the temporary file by either

editing the tsconfig include for that run, causing only some specs to be compiled, or
creating a custom context for the require in test.ts, similar to what we do for lazy routes

I favor the first option myself because it also makes for a smaller, TS compilation, which should make both initial build and rebuilds faster.
I understand it's disappointing to be asked to reduce the scope of something you've designed and that covers your usecase very well. But for us as maintainers these questions of migration and usability are always key concerns.
For instance, anything that requires a migration can only be on a major since our policy is to only require migrations for majors. On the other hand something that requires no interaction with the user source is much easier to land. Things that have any chance of leaving artifacts in the user sources are also scrutinized because they are hard to clean after.
Please let me know what you think.

@filipesilva I agree 100% that generated/temp file is not ideal, but I do not know how else scope could be limited effectively without a way to feed webpack/typescript a stream/string instead of an entry point file.
I'll test if your theory holds by changing tsconfig include option and get back to you. Do you have any pointers for custom context? I'd like to see how that works as well.
On a flip side, I do not really agree with other team concerns:

requires a migration of existing projects (via ng update) to ignore it on git
it's surprising for users that files are created in their sources
it can remain on disk despite best efforts to remove it (e.g. process crash)

These steps can be fairly easily handled manually and documented as a quirk of -spec option for performance reasons - this is my number 1 problem for spending time on this! Not sure if you realized, but if you do not use the option - file will not be generated. I'd rather spend 5 minutes configuring my project manually and having fastest rebuild time than making this automatic process, but potentially slower (currently I have no idea if tsconfig include option would slower/faster and if it would be a working solution) and having to restart the process to switch to a different test.
In other words, I am in favor of development experience/quick iteration when doing unit tests over configuration. Some things do not have simple solutions.

multiple targeted spec runs will interfere with each other because they use the same temp file

I'd say this is more like a limitation that you can have only single targeted test run at the same time per project. Isn't it safe to assume that one would use this option when working on a specific feature/task?
Thanks for looking into this!

This is where we manipulate the custom context for lazy routes: https://github.com/angular/angular-cli/blob/6fc6e84b0a0d84f04be5b21cf7c0a6411829c554/packages/ngtools/webpack/src/angular_compiler_plugin.ts#L697-L753

These steps can be fairly easily handled manually and documented as a quirk of --spec option for performance reasons

Generally speaking, anything that requires a user to go figure out the quirks of the tool isn't great. And anything that requires a user to manually change their project isn't going to happen for the vast majority of projects.
Yes, the performance would be better. And I also understand that it would be much preferable for your usecase to have the "hot switch" feature. But I think that for most users, the base "targetted spec" feature gets them most of the way to faster test turnaround time without any quirks, pitfalls, needed upgrades, etc. Then the feature can be enhanced over time.
One thing I ask you to keep in mind is that we have a two release cycle deprecation policy. Since we release roughly every six months, that means that a new feature will need to be around and maintained for at least one year. I hope this puts into perspective why we favor less user-facing complexity and things that don't require upgrade paths.

You have very valid points from maintenance point of view and I agree, but this does not help in landing such feature to the 'core'. I am also a bit puzzled why there is no demand for such option (maybe not many enterprise apps have tests... I hope not!) or what people do after they pass certain number of tests (gonna have to check jest).
Anyway, I've tried tinkering and customizing tsconfig include option and from my understanding solution would not be simpler. Basically I'd have to recursively find all related files to targeted specs and pass them via files option or include option. I don't think there is a way to pass a mask to typescript and let it handle this automatically.
To make matters worse, consider this tsconfig:
{
    "extends": "./tsconfig.json",
    "exclude": [
        "./node_modules"
    ],
    "include": [
        "source/polyfills.ts",
        "source/test.ts",
        "source/common/components/input/**/*.ts"
    ]
}

One could expect that only files related to the listed ones would be included, but no - typescript also tries to compile files that are not referenced directly or indirectly (such as source/common/services/* or source/mw/*). Only changing require.context('./', true, /\.spec\..s$/); to require.context('./', true, /common\/components\/input\/.*\.spec\..s$/); in test.ts fixes the issue.
Could you share the solution that worked for you when you discussed include option as a potential alternative?
In the meantime I'll investigate what custom context does and how it works - thanks for that!

The tsconfig you showed is quite different from the ones we generate for specs, mind you. We explicitely set both files and include. If you don't set files, everything is included by default.
Tried my hand at manipulating the tsconfig manually:

made a new app with ng new targeted-specs-tsconfig
added a failing spec src/app/failing.spec.ts: it('should fail', () => expect(false).toBeTruthy());
npm run test -- --watch=false --browsers=ChromeHeadless fails
edit tsconfig to have this include property:

  "include": [
    "**/app.component.spec.ts",
    "**/*.d.ts"
  ]

npm run test -- --watch=false --browsers=ChromeHeadless fails with a badly formatted message that says

Uncaught Error: Module build failed (from ./node_modules/@ngtools/webpack/src/index.js):
Error: D:\\sandbox\\targeted-specs-tsconfig\\src\\app\\failing.spec.ts is missing from the TypeScript compilation. Please make sure it is in your tsconfig via the 'files' or 'include' property.

I expected that to work. But it doesn't because our webpack plugin errors out when requested TS files that aren't in the compilation.
We added this error specifically to avoid implicitly importing TS files. Maybe this is a restriction that we can relax on this particular case, and serve an empty file instead. But either way this approach got more complicated.

If you want to check how ignoring that error looks like, open<EMAIL_ADDRESS>and comment out this block:
https://github.com/angular/angular-cli/blob/6fc6e84b0a0d84f04be5b21cf7c0a6411829c554/packages/ngtools/webpack/src/angular_compiler_plugin.ts#L1016-L1030
Doing that will work with my previous example and only run src/app/app.component.spec.ts.
I'm unsure of what the best API within the plugin for this would be, but probably an option that alters the include array, and ignore the error above if the file matches the alteration.

@filipesilva I think I found a perfect solution!
I'll make a webpack loader (see last commit) that will be registered in karma builder for test.ts files which will transform it in the same way as in original suggestion.
I tested the idea in angular 8 project by modifying karma js file manually in node_modules and it seemed to work.
Now I have to figure out again how to work on cli locally

I think I have it working! Only missing 2 things now:

support directory when one is passed as spec
figure out sourceRoot from target (so it would also work in multi-project setup)

PR is ready for review. @filipesilva would you mind having a look at current implementation and provide some feedback? Thanks!
Aside of that some help regarding failing circleci test would be great, as the same tests are passing locally and the feature is working as intended when build_angular package is installed in another project.

PR should be ready now. I've rebased from master and updated karma/schema.json with more details about spec option.

I just had to adjust the text in schema.json, apparently having **/* in description results in broken schema.ts file. As it ends multi-line comment.

@filipesilva I see you've added 8.1 milestone, which is nice!
I am just a bit confused on what should I change to finalize this? Would it be enough to rename option from spec to include (or files)?

I've rebased from master and I think this is ready to go. include option can now be passed multiple times and appropriate specs are executed in test project.
It's just a bit strange that I see a warning that the option is passed multiple times. Can one of point out how one can pass an array to cli? e.g. codeCoverageExclude, there is no example in docs :(

@FDIM I updated your original PR message to list the new --include name, and remove references to --spec-update. I was pointing people here and they were confused that the spec option wasn't listed in docs.

Angular CLI: 8.1.2
Node: 10.16.0
OS: win32 x64
Angular: 8.1.2
... animations, cli, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router, upgrade

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.800.6
@angular-devkit/build-angular     0.800.6
@angular-devkit/build-optimizer   0.800.6
@angular-devkit/build-webpack     0.800.6
@angular-devkit/core              7.3.4
@angular-devkit/schematics        8.1.2
@angular/cdk                      8.1.1
@ngtools/webpack                  8.0.6
@schematics/angular               8.1.2
@schematics/update                0.801.2
rxjs                              6.5.2
typescript                        3.4.5
webpack                           4.30.0

npx ng test --include something
Unknown option: '--include'
Unknown option: 'something'

Shouldn't this work?

@krokofant yeah you need to update @angular-devkit/build-angular to include these changes.


model.Model is not an abstract class

More of a nit-pick here,
model.Model has __metaclass__ = ABCMeta so I'm assuming that it's to be extended before use.
However, I installed cleverhans via pip and I am able to initiate an instance of Model.
This shows that the property is not implemented properly. I'm not sure what's the best way to do this,
but decorating the method we want to overload with @abstractmethod (cf. https://dbader.org/blog/abstract-base-classes-in-python)
I'd be happy to send a PR with the changes if that's the desired behaviour.
Additionally, it would be good to mention which methods we want users to implement when extending in the docs.

Yes, it would be great to have a PR to address these issues, you may want to send a quick email describing the changes you'll make to<EMAIL_ADDRESS>I just accepted your membership request

Great, I'll write it up. I'm new to cleverhans, so could you let me know which methods must be overloaded? Looks like get_layer_names and fprop are the only candidates.

Closing after discussions on cleverhans-dev


Roll back packageConfig/File/Spec updates in 1.13

[ ] Remove Isolate.packageMap getter
[ ] Remove Isolate.packageRoot getter
[ ] Remove Isolate.spawnUri({packageMap}) named argument

cc @iposva-google

Review pending in https://codereview.chromium.org/1409343007/

Landed in 1fa2ef874d61eb3ea994d26009cb2d02a86e5bf3
Thanks, @iposva-google - would you open a merge request for 1.13?

Removed additional obsolete test with d164c23394d2afd34c7cd4d2dc96940789db7c77

Merge request filed as issue 24701.


Add functionality to transform BitSet to RoaringBitmap efficiently

This tries to bypass any add() function, where one has to decompress or
re-size arrays, etc..
Could still be improved in the loops. Also the decision between RunContainer/ArrayContainer/BitmapContainer needs some work.

Looks like a good idea. Will review.
c.c. @gssiyankai

@okrische
Good job.
I just added some comments on the changes.
As you mentionned, BitmapContainer are not used at the moment. I would recommand to support this transformation before merging.

One thing that would be very useful, if you have time, is to do a benchmark, if only an informal one, to check how fast things run compared to simply iterating over the BitSet and calling "add" to a RoaringBitmap. It would be best if such a benchmark included varied BitSet objects (small, large, dense, sparse). We would like to make sure that your function is always faster than the naive way.
Optional but nice: If you really want to be helpful, you could add a JMH benchmark to our set. I think that @gssiyankai could give pointers as he is very good at that.
Regarding the code, this is a good starting point. I would suggest simplifying/optimizing the code :
Assuming that the BitSet is long enough (has >= 1024 64-bit words):

Start by calling toLongArray on the BitSet .
Iterate over chunks as is done now.
Create a BitmapContainer for each chunk. Call computeCardinality. Next check cardinality. If too low, call toArrayContainer.
Don't worry about run containers. Just have the user call runOptimize on the final result if desired. This will simplify your logic as you won't need to worry about runs.

You need a special code path for the "last chunk" (a chunk that does not span 1024 words in the original BitSet) and for BitSet that span fewer than 1024 words. I think you want to first determine the cardinality. To do so you may need a special function, but please don't iterate over the set bits to computer the cardinality. Instead use Long.bitCount.

I like the idea of skipping RunContainer at all. And sure, i can use Bitset#toLongArray and use it directly in the BitmapContainer.
Thanks to both of you for your comments.

@okrische
To add a new JMH benchmark, you would need to :

Add a new class under the jmh module
Annotate the class with

@BenchmarkMode(Mode.AverageTime)
@OutputTimeUnit(TimeUnit.MICROSECONDS)

Add a setup method where you construct the bitset to convert. Annotate it with:

@Setup

Add a method where you convert the bitset to a roaring bitmap. Annotate it with:

@Benchmark

You can have a look at the existing benchmarks (this one for example can be a good starting point: https://github.com/RoaringBitmap/RoaringBitmap/blob/master/jmh/src/main/java/org/roaringbitmap/BasicBenchmark.java)
To run the benchmark, you can either add a main method in your class and launch it from your IDE, or use the script run.sh. Make sure to give the name of the class you added (otherwise, all of the benchmarks will be launched)

Using long[] simplified a lot.
Also added BitSetUtilBenchmark in jmh.
I still have some doubts about efficiently iterating over one 64bit word to extract the bits for the ArrayContainer, though. But it was fun to think about it, soooo long ago to think about such low level things.
I kept the BitSet transformation, as i can use a shortcut for cardinality < 4096, as i do not need to do this extra toLongArray() copy.
Since its still java 1.6, i also added a toLongArray() implementation for BitSet, well, using the javadoc from BitSet in 1.8, in the way they suggested it. When you guys change to java 1.7, this can be removed and speeds up the whole transformation again.

@gssiyankai
I checked and RoaringBitmap is compatible still with Java 6. Note however that we have not systematic testing (travis) in place.

@okrische
I'll review the code soon. Thanks.

@lemire,
Great. If so, I suggest to add it back in travis CI (we used to have it
before if I'm correct).
I'll submit the change if you agree.
On Wed, Feb 3, 2016 at 7:27 PM, Daniel Lemire<EMAIL_ADDRESS>wrote:

@gssiyankai https://github.com/gssiyankai
I checked and RoaringBitmap is compatible still with Java 6. Note
however that we have not systematic testing (travis) in place.
—
Reply to this email directly or view it on GitHub
https://github.com/RoaringBitmap/RoaringBitmap/pull/70#issuecomment-179390598
.

@gssiyankai
I don't object to you adding it, but there is an opportunity here for upgrading to Java 7.
Thoughts?

Ah, ok.
IMHO, it's reasonable to upgrade. Java 7 offers a richer concurrency api
that might be helpful to parallelize executions (and we know that Roaring
internal structure is well suited for such things).
Plus I'm not sure we have a lot of Java 6 users. The end of public updates
for Oracle Java 6 was on Feb 2013 (the end of extended support is scheduled
on Dec 2018, but this case should be very rare). Besides, as you mentionned
before, future versions of Android will be based on OpenJdk and will be
Java 8 compatible.
I would just point out that the upgrade to java 7 should be made available
in a major release of Roaring(version 0.6.xxx) so that we can still provide
bug fixes for java 6.
How about upgrading to java 8 directly ?
On Wed, Feb 3, 2016 at 8:44 PM, Daniel Lemire<EMAIL_ADDRESS>wrote:

@gssiyankai https://github.com/gssiyankai
I don't object to you adding it, but there is an opportunity here for
upgrading to Java 7.
Thoughts?
—
Reply to this email directly or view it on GitHub
https://github.com/RoaringBitmap/RoaringBitmap/pull/70#issuecomment-179421612
.

I am of course in favour of java 8. But not because of the concurrency stuff (i personally do not like any executor/runnable things in libraries), but rather because of lambdas. For example, one could stream efficiently indexes into a bitmap via an IntStream. Or like in other threads, offering nice collectors for OR/AND operations between bitmaps (and then, by choice, allowing parallel streaming, but externally, not from within the library)

I propose moving the java6/java8 discussion to an actual issue I just created.
https://github.com/RoaringBitmap/RoaringBitmap/issues/74

@okrische

When you guys change to java 1.7, this can be removed and speeds up the whole transformation again.

I think there there is agreement to move to 1.7 as major vendors have upgraded to 1.7. So starting with version 0.6, RoaringBitmap will no longer be compelled to support Java 1.6. This means that we can merge your PR without sacrificing performance.
However, this is currently stalled because travis is failing for us... I have opened an issue...
https://github.com/RoaringBitmap/RoaringBitmap/issues/75
I think that @gssiyankai  has agreed to look at it.
Once the build is officially passing the tests, we shall be able to merge in your PR.
Thanks for your patience.

Thanks to @gssiyankai , we are back in business.

@okrische
I am working on a PR that I will submit to your fork soon.

@okrische  Please see...
https://github.com/okrische/RoaringBitmap/pull/1
Review and possibly merge  my PR. Then, possibly, we can merge back in the main RoaringBitmap.

Yay! With your changes, the conversion is now 4 times faster according to jmh with my dataset, where i have only a max of 96 bits per BitSet ( so it uses only ArrayContainers)
$:~/git/RoaringBitmap/jmh$ ./run.sh org.roaringbitmap.BitSetUtilBenchmark
...
Benchmark                                            Mode  Cnt       Score       Error  Units
BitSetUtilBenchmark.BitSetToRoaringByAddingBitByBit  avgt    5  321265.672 ± 16719.292  us/op
BitSetUtilBenchmark.BitSetToRoaringUsingBitSetUtil   avgt    5   80315.676 ±   711.213  us/op

If i duplicate each bitset a hundred times to the right (96000 bits max), it now even gets 10 times faster.
...
Benchmark                                            Mode  Cnt        Score        Error  Units
BitSetUtilBenchmark.BitSetToRoaringByAddingBitByBit  avgt    5  9869858.180 ± 129760.451  us/op
BitSetUtilBenchmark.BitSetToRoaringUsingBitSetUtil   avgt    5  1060313.473 ±  10476.022  us/op

Not to mention memory usage...
Thanks!

@okrische
Thanks for your hard work.

@okrische
Your name was added...
https://github.com/RoaringBitmap/RoaringBitmap/commit/4306038ea4487d28410bd9a814ae1c1a7a23b7c5


Left click outside bug fix

Clicking outside the context menu when using @angular/core: 2.3.0 was not closing the context menu.

The @hostListener('document:click') was not working but it starts working after the two host listeners are bound to two different function.

Thanks for the contribution! I'll review it next week when I'm back from
vacation.
On Dec 30, 2016 7:14 AM, "Shahbaz Ali Shueb"<EMAIL_ADDRESS>wrote:

Clicking outside the context menu when using @angular/core: 2.3.0 was not
closing the context menu.
You can view, comment on, or merge this pull request online at:
https://github.com/isaacplmann/angular2-contextmenu/pull/36
Commit Summary

Left click outside bug fix

File Changes

M src/contextMenu.component.ts
https://github.com/isaacplmann/angular2-contextmenu/pull/36/files#diff-0
(8)

Patch Links:

https://github.com/isaacplmann/angular2-contextmenu/pull/36.patch
https://github.com/isaacplmann/angular2-contextmenu/pull/36.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/isaacplmann/angular2-contextmenu/pull/36, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AA0lQC2h63xRRIofSV69CkTS3FZJ8_fIks5rNPXAgaJpZM4LYKAC
.

Thanks for making a PR!  But it looks like this bug was fixed in angular 2.3.1, so I won't merge this in.


Camel case not default for Model validation

MVC serializes JSON with camel case by default. However, it doesn't seem true for Model validation and still requires. .AddJsonFormatters(j => j.ContractResolver = new CamelCasePropertyNamesContractResolver())
Otherwise, the validation errors come back in pascal case as seen below on BadRequest(ModelState).
{
  "FirstName": [
    "The FirstName field is required."
  ]
}

where it should actually be
{
  "firstName": [
    "The FirstName field is required."
  ]
}

It's true the keys added to ModelState are generally based on C# properties (usually Pascal-cased) and not the incoming data. But names are matched case-insensitively in model binding and validation and the ModelStateDictionary does case-insensitive lookups.
Could you clarify why the line you added insufficient or perhaps an undue burden to adjust the system to match your preferences?

Adding the line isn't an undue burden but we assumed since camel case was the default json formatter that this line wouldn't be needed. When any other object is serialized to json which has pascal-cased properties it correctly uses the default formatter which is camel case. However, except for the returned validation result errors json.

Please describe your scenario in more detail, including the validation errors when submitted JSON has unexpected key casing. A small repro project hosted in a public GitHub repo would be ideal.

Here you go. camel-case-issue

@bryjshed your tests show that the service is indeed configured with the expected output formatter configuration. However, asserting specific key casing doesn't demonstrate an end-to-end problem.
Are you using a client-side JSON parser that is case-sensitive? If yes, configure the service to match the exact keys your client expects.

@dougbu I don't really think that the need for case-sensitivity is the issue. There is a work around. I think the issue is that this is unexpected behavior. As described here: https://github.com/aspnet/Mvc/issues/4842

@johnathan-walker I'm closing this as a duplicate of the #4842 discussion. Had thought you were reporting a bug.

The expected behavior for serializing ModelState is camel case. The actual behavior is pascal. I think that is a bug.

@dougbu

FYI the JSON serializer doesn't special case ModelState and it's handled like any other dictionary.

@dougbu This should really be a bug (since #4842 announces that the default casing in camel and in this case it is not) and fixed in upcoming releases, although there are workarounds as pointed out by @johnathan-walker and @bryjshed

Please see #4969 as well as discussion of the intentional distinction between code and data in #4842.
As I said earlier, MVC treates ModelState like any other dictionary. Feel free however to file a feature request for a special case in this area. Note it would be somewhat strange because ModelState keys come from both C# property names and users' submitted dictionary keys.

@dougbu C# property names are an internal implementation detail of the API code, and should not be exposed verbatim to the API clients.  I would argue that the same justification used to default to camel case should be applied here.
In other words, as an API client, when I submit a payload containing key, and it is incorrect, I don't expect to receive validation errors referring to a different property Key. I didn't send that and I should not be expected to map it back to the key name I sent to make sense of it.
For Javascript apps running in a browser, Javascript property lookups are case sensitive. Doing case-insensitive lookups is not trivial nor very performant.
And it shouldn't be necessary either if this issue is fixed.

Have to agree this is really an issue. It shouldn't be hard to fix.


Slippage Tolerance issue

Summary of Bug
This one I faced when I change the Tolerance it would not stick up for long, possibly in next swap it reset back to default tolerance. Give more control over this.

Version
Cosmos SDK Liquidity module Testnet

Steps to Reproduce

Goto transaction settings
By default it shows 3%, instead add 3 or 4 options 0.5 1 2 and 3%
If possible add transaction deadline limit, during a case of pending
For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate contributors tagged
[ ] Contributor assigned/self-assigned

Hi
Am I eligible for bug bounty?
62.52 ————> Total Score
279————>Rank


Session.removeAttribute throws NullPointerException

Cloud Tools for IntelliJ version: 18.10.1
Google Cloud SDK version (run gcloud version on the command line): 220.0.0
OS: macOS 10.13.6

What did you do?
Updated to the newest version of Google Cloud Tools for IntelliJ. Now all instances where we remove session attributes throw a NullPointerException.
What did you expect to see?
Session variable should be removed.
What did you see instead?
NullPointerException
java.lang.NullPointerException
at com.google.apphosting.runtime.jetty94.AppEngineSession.setAttribute(AppEngineSession.java:81)
at org.eclipse.jetty.server.session.Session.removeAttribute(Session.java:786)
Same issue if you try to use session.setAttribute("someattribute", null);

hi @brandon-rentpingmedia thanks for the report
Could you please provide a bit more detail so that we can help diagnose? What operation were you trying to perform using the plugin (local-run, deployment etc.)? Are you using App Engine standard?
Also you mentioned this happened after updating the plugin; so I assume you were using the same workflow with the previous version of the plugin and not running into this?

Running app engine java locally (standard). And yes, this code has been in place for years, so it was specific to the update.

Update: rolling back to gcloud version 219.0.1 fixes the problem:
gcloud components update --version 219.0.1

issue filed internally, will update here when I have some more info

@ludoch

Sorry about that, I think a temp workaround it is to add
<sessions-enabled>true</sessions-enabled>

in appengine-web.xml

FWIW, I had that sessions-enabled xml attribute in my appengine-web.xml when I reported the issue.

Thanks for the info, this helps a lot....
I found the issue where we should support null in setAttribute, but we currently do not...
For now, keep the previous SDK as a workaround... I can do the fix, but no guarantee it will become public in next Cloud SDK push,  but definitely in the one after.

BTW, this is not affecting apps in production, so deployments with old or new Cloud SDKs are fine, only local execution.

Thanks for the quick responses on this. We appreciate it!

Appears to be fixed now!

thats great. thanks for updating us @MuffinTheMan


Drift between server responses and documented schema

We use the published schema to generate dataclasses for a python application.
At some point between 2024-02-02 and 2024-02-06, the structure of the structuredData.json files being returned from the PDF Services Extract API drifted from this schema - e.g.
https://github.com/adobe/pdftools-sdk-docs/blob/9dca8714c6325033ff43a475b415101b24f665f0/docs/release/shared/extractJSONOutputSchema2.json#L88
This key is missing from the extended_metadata of the structuredData.json files (possibly renamed to is_signed?).
I have not checked if there are additional discrepancies.

I was able to get a response to this issue on the forums here.


Enable virtual service delegate by default

[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[X] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Pull Request Attributes
Please check any characteristics that apply to this pull request.
[ ] Does not have any changes that may affect Istio users.

@hzxuzhonghu: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
ab117e4eff86328451650b3403d9745f49555cec
link
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hzxuzhonghu: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
ab117e4eff86328451650b3403d9745f49555cec
link
/test release-notes_istio

unit-tests_istio
ab117e4eff86328451650b3403d9745f49555cec
link
/test unit-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hzxuzhonghu: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
ab117e4eff86328451650b3403d9745f49555cec
link
/test release-notes_istio

unit-tests_istio
ab117e4eff86328451650b3403d9745f49555cec
link
/test unit-tests_istio

integ-pilot-k8s-tests_istio
ab117e4eff86328451650b3403d9745f49555cec
link
/test integ-pilot-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hzxuzhonghu: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
ab117e4eff86328451650b3403d9745f49555cec
link
/test unit-tests_istio

integ-pilot-k8s-tests_istio
ab117e4eff86328451650b3403d9745f49555cec
link
/test integ-pilot-k8s-tests_istio

release-notes_istio
c4d39e4b0a3181863fa877b14f77784a29cc4aeb
link
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hzxuzhonghu: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
ab117e4eff86328451650b3403d9745f49555cec
link
/test unit-tests_istio

integ-pilot-k8s-tests_istio
ab117e4eff86328451650b3403d9745f49555cec
link
/test integ-pilot-k8s-tests_istio

release-notes_istio
19a52b419d0eb303b2a1b72e31b7e37849b5ca02
link
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hzxuzhonghu: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
ab117e4eff86328451650b3403d9745f49555cec
link
/test unit-tests_istio

integ-pilot-k8s-tests_istio
ab117e4eff86328451650b3403d9745f49555cec
link
/test integ-pilot-k8s-tests_istio

release-notes_istio
19a52b419d0eb303b2a1b72e31b7e37849b5ca02
link
/test release-notes_istio

gencheck_istio
19a52b419d0eb303b2a1b72e31b7e37849b5ca02
link
/test gencheck_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hzxuzhonghu: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

gencheck_istio
19a52b419d0eb303b2a1b72e31b7e37849b5ca02
link
/test gencheck_istio

release-notes_istio
21a23276e53f18c5f2c217646962f0673ec3757a
link
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hzxuzhonghu: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
21a23276e53f18c5f2c217646962f0673ec3757a
link
/test release-notes_istio

integ-pilot-k8s-tests_istio
21a23276e53f18c5f2c217646962f0673ec3757a
link
/test integ-pilot-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@hzxuzhonghu: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
21a23276e53f18c5f2c217646962f0673ec3757a
link
/test integ-pilot-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@esnible for the ut update

/test integ-pilot-k8s-tests_istio


This was necessary because the documentation
does not correspond to the realization.
The tests run again after the processing.

review-requested: @mristin


404 error on new install

Actions before raising this issue

[X] I searched the existing issues and did not find anything similar.
[X] I read/searched the docs

Steps to Reproduce
I've followed the guide here to install https://discordapp.com/channels/1000789942802337834/1000789943293063257/1205268156482846730 and the last step is to connect ot localhost:8080 when I do all I get is a 404 error page. I've checked it's coming from this by taking the containers down, and when I do I get a host not found error.
I don'tknow if there's files missing from github clones somehow, or if there's a config step missing from the install instructions, but can someone point me towards what I should change to get a home page of some kind
Expected Behavior
Open the homepage for the new server
Possible Solution
No response
Context
Brand new install on a local linux machine, and then a second attempt on a clean aws machine.
Environment
git clone from 08/02/2024
ubuntu 20.04 local
aws linux on ec2 instance
ubuntu 20.04 on remote machine for one last try!

docker ps?

Hmmm..
If you deployed on AWS, you can't use localhost :)
It should have a specific IP address, but when in browser you use localhost it asks your computer to have this server up

Hmmm..
If you deployed on AWS, you can't use localhost :) It should have a specific IP address, but when in browser you use localhost it asks your computer to have this server up

Yes, sorry I should perhaps have been more clear. When using my local machine I went to localhost from that local machine, an it served the 404 error.
when using a remote machine, I first opened the port on the relevant firewall for that remote machine and then went to the public facing IP of the machine.
In each instance I got a very specific looking 404 error page - with a particular font etc. When I turned off the containers that error page no longer came up.
I can run docker ps - but there were no errors starting the containers for CVAT and no other docker processes running as there was literally nothing else on the machine.

went to the public facing IP of the machine.

You deployed on localhost, you can't use public IP. It is about security policies.
If you are planning to use on public IP, please export corresponding env variable and upgrade a port in config file: https://opencv.github.io/cvat/docs/faq/#how-to-change-default-cvat-hostname-or-port

went to the public facing IP of the machine.

You deployed on localhost, you can't use public IP. It is about security policies. If you are planning to use on public IP, please export corresponding env variable and upgrade a port in config file: https://opencv.github.io/cvat/docs/faq/#how-to-change-default-cvat-hostname-or-port

Sorry I shouldn't have conflated the error on different machines back to one - I was trying to say that the behaviour was the same or similar from different installs. On the AWS machine I changed the configs as intended.
The error seems to be different today on my local machine though:

I've taken a screen recording of the process to get to error in case that helps. As mentioned in there I replaced 8080 & 8090 in the docker yaml file with 8082 and 8092 - maybe that needs changing elsewhere?
https://github.com/opencv/cvat/assets/12558370/9d08a5bb-b2cf-4d94-be8b-bb39fe102e3f

The error seems to be different today on my local machine though:

First of all, please check /healthcheck response in the browser console (F12, Network, Refresh page, wait).

Similar to the homepage - spinning animated connection wheel then the same error message:

Please, check one more time what the guide suggests to change and what you changed in the videofile.
That is not the same..

Sorry I did a search and replace, and then a find to "demonstrate" the change and obviously picked the wrong place - I've had a look back and it's also changed in the right place:

It's also changed in some extra places that aren't mentioned though, so I've put those back for to 8080 to see if that fixes anything and the healthcheck runs for a bit longer maybe, but still comes up as unavailable:

Still not correct file, at least in this place.

Internal docker ports 8082, 8092 are empty.  Please, re-check all again.

ok, healthcheck wasn't working, but the main screen now seems to.
It seems that whatever is on my port 8080 and my subsequent attempts to side-step it are what's caused all the issues.


laconfig.json file missing from repo

laconfig.json file seems to be missing from the repository

Laconfig.json file is created through the MPARR_Setup.ps1 script.


Displays

@Strilanc I'd like to know your thoughts on this "display" concept that you mentioned at #942 . Do you imagine this as a separate class whose instances would be bundled with the Circuits sent to Quantum Engine?

A Display would be a special kind of gate that indicates "please tell me XX about the qubits I am targeting at this time". Displays are no-ops as far as the rest of the circuit is concerned (there would be dedicated runs of the circuit to compute each display's value, and for other runs the display is omitted).
Basically, it's exactly the concept of displays that I use in Quirk.

It might be useful to integrate this with the concept of an "acquaintance gate". One would commonly be interested in "displaying" the logical qubits (or modes in the fermionic case) mapped to the corresponding physical qubits at some point in time.

@Strilanc how does this affect the Quantum Engine API? Are you proposing to add a method separate from run that would be used to calculate displays?


"new foo" reports misleading error message when auth is not first added

this is using webpacked kui, when you type "new foo" to create a new action before you've added an auth key, you get a misleading error: The given action name is already in use.

moving to https://github.com/IBM/kui/issues/604


go-1.15-2 + certificate generation

Using of certificate CommonName is deprecated in Go-1.15.
Made changes to the self-signed certificate generation and client certificate
verification code so that now they work on DNSNames instead of CommonName.
Whereas the certificate generation using cfssl tools insetup-ca.sh
script already setting the hostname(s) which is good enough for us.
cfssl treats as an error if no Subject set, so keep setting the CN.
Also updated to the latest cfssl release - v1.4.1

This is PR is based on #753. I reverted the "enable legacy certificate support" (https://github.com/intel/pmem-csi/pull/755/commits/487f65bbfccac58e8ad76f322f1e5bddbd86deb1) commit and made changes to self-signed certificate code to generate SAN/hostname certificates. @pohly Can you please check if this is what you wanted to have?

This looks good, except for the added set +x.
Can you submit just your one commit? It should work independently of the Go 1.15 change. That way we get some indirect testing for the downgrade scenario ("new" certificates with "old" code).

Ok,  I will submit rebasing on devel.


Escape unescaped periods in route regular expression

Works: /compare/sha1...sha1
Works: /compare/sha1FOOsha1 <-- make this don't work anymore

Side note:
Actually, I was trying to make 7-digit sha1 sums work, but I failed, because you can't make a Hex from an odd length string (here).
Another thing: I really wonder why gogs does not use libgit2 (like GitHub, BitBucket, etc.). Is that on purpose?

May consider after 1.0 release.
It uses CGO and very hard (not even know how) to cross-compile...


create_app() not working for docker container

Hi, Below is the script i am trying to create a docker container using Marathon.
I doubt the issue with the json data sent in create_app()
from marathon import MarathonClient
from marathon.models import MarathonApp
from marathon.models.container import MarathonContainer
from marathon.models.container import MarathonDockerContainer
marathonApp = MarathonApp(cmd = 'while sleep 10; do date -u +%T; done', container = {'docker': {'image': 'ubuntu:latest', 'network': 'BRIDGE'}, 'type': 'DOCKER'}, cpus = 0.5, instances = 2, mem = 128)
marathonClient = MarathonClient('localhost:8082/')
marathonClient.create_app('/anbu/tst-ubuntu-ssh', marathonApp)
Getting error response as
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3.2/site-packages/marathon/client.py", line 109, in create_app
return self._parse_response(response, MarathonApp)
File "/usr/lib/python3.2/site-packages/marathon/client.py", line 52, in _parse_response
return clazz.from_json(target)
File "/usr/lib/python3.2/site-packages/marathon/models/base.py", line 30, in from_json
return cls({to_snake_case(k): v for k,v in attributes.items()})
File "/usr/lib/python3.2/site-packages/marathon/models/app.py", line 88, in init
else MarathonContainer.from_json(container)
File "/usr/lib/python3.2/site-packages/marathon/models/base.py", line 30, in from_json
return cls({to_snake_case(k): v for k,v in attributes.items()})
File "/usr/lib/python3.2/site-packages/marathon/models/container.py", line 25, in init
else MarathonDockerContainer().from_json(docker)
File "/usr/lib/python3.2/site-packages/marathon/models/base.py", line 30, in from_json
return cls(**{to_snake_case(k): v for k,v in attributes.items()})
AttributeError: 'NoneType' object has no attribute 'items'

Tried to dump the JSON sent in create_app().
{"cmd": "while sleep 10; do date -u +%T; done", "container": ["docker", "type"], "cpus": 0.5, "id": "/anbu/tst-ubuntu-ssh", "instances": 2, "mem": 128}

Using the latest release of marathon-python (0.6.13), I was able to deploy your app to a Marathon 0.8.1 server without any changes:
>>> import marathon
>>> c = marathon.MarathonClient("http://marathon.example.net:8080")
>>> m = marathon.MarathonApp(cmd = 'while sleep 10; do date -u +%T; done', container = {'docker': {'image': 'ubuntu:latest', 'network': 'BRIDGE'}, 'type': 'DOCKER'}, cpus = 0.5, instances = 2, mem = 128)
>>> c.create_app('foo', m)
MarathonApp::/foo

Your JSON output seems to have a bad container field. You should see:
>>> marathon.MarathonApp(cmd = 'while sleep 10; do date -u +%T; done', container = {'docker': {'image': 'ubuntu:latest', 'network': 'BRIDGE'}, 'type': 'DOCKER'}, cpus = 0.5, instances = 2, mem = 128).to_json()
'{"cmd": "while sleep 10; do date -u +%T; done", "container": {"docker": {"image": "ubuntu:latest", "network": "BRIDGE", "privileged": false}, "type": "DOCKER"}, "cpus": 0.5, "instances": 2, "mem": 128}'

What version are you using? Can you try reinstalling, perhaps in a [new] virtualenv?

I'm using Python 2.7.6, and it looks like you're using Python 3.2. I wonder if this is related to https://github.com/thefactory/marathon-python/pull/27.
Assuming you're using 0.6.13, would you mind installing from master instead?
pip install -e git+git@github.com:thefactory/marathon-python.git#egg=marathon

I am not able to load marathon module with python 2.7.8. I am using "marathon-0.6.13"
FYI, I am using cygwin.... Not sure, is this a problem.
Python 2.7.8 (default, Jul 28 2014, 01:34:03)
[GCC 4.8.3] on cygwin
Type "help", "copyright", "credits" or "license" for more information.

from marathon import MarathonClient
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python2.7/site-packages/marathon-0.6.13-py2.7.egg/marathon/init.py", line 3, in
from .client import MarathonClient
File "/usr/lib/python2.7/site-packages/marathon-0.6.13-py2.7.egg/marathon/client.py", line 14, in
import requests
ImportError: No module named requests

Not sure about how things work in cygwin, but installing from pip should get you all the (requirements)[https://github.com/thefactory/marathon-python/blob/master/setup.py#L14]. In any case, you just need to install the requests package (this requests)
pip install requests

That should have fixed it - please feel free to reopen if you're still having trouble with requests


[BUG] Undefined Behavior in ts::AVCParser::expColomb (found in ubsan+fuzz testing)

Bug description:
During fuzzing test (using make UBSAN=1 build) 'shift exponent' undefined behaviour was found:
src/libtsduck/dtv/codec/tsAVCParser.h:281:21: runtime error: shift exponent 590 is too large for 32-bit type 'unsigned int'
    #0 0x1033a50c4 in bool ts::AVCParser::expColomb<unsigned int, (void*)0>(unsigned int&) tsAVCParser.h:281
    #1 0x103710178 in ts::HEVCSequenceParameterSet::parseBody(ts::AVCParser&, std::initializer_list<unsigned int>) tsHEVCSequenceParameterSet.cpp:116
    #2 0x1034124ac in ts::AbstractVideoAccessUnit::parse(unsigned char const*, unsigned long, std::initializer_list<unsigned int>) tsAbstractVideoAccessUnit.cpp:35
    #3 0x10370e3e0 in ts::HEVCSequenceParameterSet::HEVCSequenceParameterSet(unsigned char const*, unsigned long) tsHEVCSequenceParameterSet.cpp:19
    #4 0x1036e8ef8 in ts::HEVCAttributes::moreBinaryData(unsigned char const*, unsigned long) tsHEVCAttributes.cpp:64
    #5 0x1038f4cd8 in ts::PESDemux::handlePESContent(ts::PESDemux::PIDContext&, ts::PESPacket const&) tsPESDemux.cpp:510
    #6 0x1038f205c in ts::PESDemux::processPESPacket(unsigned short, ts::PESDemux::PIDContext&) tsPESDemux.cpp:405
    #7 0x1038f1654 in ts::PESDemux::processPacket(ts::TSPacket const&) tsPESDemux.cpp
    #8 0x1038f0dac in ts::PESDemux::feedPacket(ts::TSPacket const&) tsPESDemux.cpp:156
    #9 0x103b60630 in ts::TSAnalyzer::feedPacket(ts::TSPacket const&) tsTSAnalyzer.cpp:1382
    #10 0x100d2bb00 in MainCode(int, char**) tsanalyze.cpp:100

How to reproduce:

Build tsduck with ubsan: make -j9 UBSAN=1 (on macos arm64 or linux x86_64)
Run UBSAN_OPTIONS=print_stacktrace=1 tsanalyze test-074.hevc-fuzz.ts

TS file: test-074.hevc-fuzz.zip
Expected behavior:
no undefined behavior
Environment:

OS: macOS
OS version: 14.1
TSDuck full version: 3.37-3610
Installation type: rebuilt binary

Additional information:
this issue is similar to https://github.com/tsduck/tsduck/pull/1416

You are fixing so fast. There is no commercial vendor with such speed...

The fix has been pushed.
Another one was in UString was also fixed (found in utest). It was another issue on iterator at end of container being nullptr (similar to #1421).

You are fixing so fast. There is no commercial vendor with such speed...

 Especially when I created them.
Commercial vendor don't hate anything, they just love money...


Upgrade springboot 2.0.

Pull Request Test Coverage Report for Build 369

20 of 26 (76.92%)  changed or added relevant lines in 4 files are covered.
52 unchanged lines in 16 files lost coverage.
Overall coverage decreased (-0.8%) to 70.118%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

infra-sofa-boot-starter/src/main/java/com/alipay/sofa/infra/constants/SofaBootInfraConstants.java
0
1
0.0%

infra-sofa-boot-starter/src/main/java/com/alipay/sofa/infra/endpoint/SofaBootVersionEndpoint.java
17
22
77.27%

Files with Coverage Reduction
New Missed Lines
%

healthcheck-sofa-boot-starter/src/main/java/com/alipay/sofa/healthcheck/core/HealthIndicatorProcessor.java
1
90.57%

runtime-sofa-boot-starter/src/main/java/com/alipay/sofa/runtime/spring/callback/CloseApplicationContextCallBack.java
1
75.0%

isle-sofa-boot-starter/src/main/java/com/alipay/sofa/isle/spring/listener/SofaModuleBeanFactoryPostProcessor.java
1
94.74%

healthcheck-sofa-boot-starter/src/main/java/com/alipay/sofa/healthcheck/startup/ReadinessCheckListener.java
1
96.3%

runtime-sofa-boot-starter/src/main/java/com/alipay/sofa/runtime/integration/activator/SofaRuntimeActivator.java
1
0.0%

runtime-sofa-boot-starter/src/main/java/com/alipay/sofa/runtime/spring/factory/ServiceFactoryBean.java
2
66.67%

runtime-sofa-boot-starter/src/main/java/com/alipay/sofa/runtime/spring/health/MultiApplicationHealthIndicator.java
2
68.75%

runtime-sofa-boot-starter/src/main/java/com/alipay/sofa/runtime/service/helper/ReferenceRegisterHelper.java
3
72.73%

test-sofa-boot-starter/src/main/java/com/alipay/sofa/test/runner/SofaJUnit4Runner.java
3
56.67%

infra-sofa-boot-starter/src/main/java/com/alipay/sofa/infra/config/spring/namespace/handler/SofaBootNamespaceHandler.java
3
0.0%

Totals

Change from base Build 368:
-0.8%

Covered Lines:
1483

Relevant Lines:
2115

💛  - Coveralls


Camp model validations

Form validations
forms in camps module should implement client-side validations,
implement form validation for:

add new camp
edit camp

for the following attributes:

email (valid email address)
phone (valid phone, israeli & non-israeli)
other inputs (should not be null if database-model requires it)

done.


Remove IServerLoader and add the IServerFactory to the DI container

This change removes the indirection and between the IServerLoader and
the IServerFactory. We now add the IServerFactory directly to the DI
container and resolve it from there.

/cc @lodejard @Tratcher @JunTaoLuo

:up::date:

:shipit:


WIFI-12907: cig-wf186w fix mpsk dynamic vlan

This is still raw and under test, let's not merge yet

@blogic Fixed the VID logic, and tested to make sure everything is still working.    Also rebased it on top of current next.  This should be good to go now.

merged, Thanks !


Assembly ID Missing on lambda.xml

Maven 3.3.9 is requiring an assembly id.  As is, the command "mvn clean package -Plambda" fails with an error reading "Assembly: null is not configured correctly: Assembly ID must be present and non-empty."  On a local copy, this was resolved by adding "0" before .

Thanks for reporting!
Do you want to send a PR?


Error with nested queries

I'm trying to execute this query:
mysql.query('SELECT R.*,K.name as key_name FROM rules as R, topics as T, table_keys as K WHERE T.id = R.id_topic AND T.type = "publish" AND K.id = R.id_key AND T.name = ?',topic, function (error, results, fields) {

	    results.forEach(function(row){

                        mysql.query('SELECT T.name as topic_name_result, K.name as key_name_result FROM topics as T, table_keys as K WHERE T.id = ? AND K.id = ?',row['id_topic_result'],row['id_key_result'], function (error_2, results_2, fields_2) {
});
});
});

but i get this error when the nested query is executed:
/var/www/html/tesi-iot.com/public_html/nodejs_iot/node_modules/mysql/lib/protocol/Parser.js:77
        throw err; // Rethrow non-MySQL errors
              ^
TypeError: Object 14 has no method 'apply'

what is the problem?
thanks

Hi @Piero87, the issue is with some code you put in your callback, not with this module. The error you are getting, TypeError: Object 14 has no method 'apply', means that you are probably doing variable.apply(...) somewhere and variable is the number 14 or something.
You didn't include any of your code that is in the callback function, so I can't pick out where this would be happening. Typically there is a much longer stack trace than the one you pasted which would point to were in your code this is occurring.


Add NFOviewer 0.3 beta 3

If there’s a checkbox you can’t complete for any reason, that's okay, just explain in detail why you weren’t able to do so.
After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} reports no offenses.
[x] The commit message includes the cask’s name and version.

Additionally, if updating a cask:

[ ] If the sha256 changed but the version didn’t,
provide public confirmation by the developer: {{link}}

Additionally, if adding a new cask:

[x] Named the cask according to the token reference.
[x] brew cask install {{cask_file}} worked successfully.
[x] brew cask uninstall {{cask_file}} worked successfully.
[x] Checked there are no open pull requests for the same cask.
[x] Checked the cask was not already refused in closed issues.
[x] Checked the cask is submitted to the correct repo.

Thank you for your PR but NFOviewer hasn't been updated for ten years.

rejected_casks
The Cask is for an app that is unmaintained (no releases in the last year, or explicitly discontinued).

I'd suggest hosting this in your own tap.

But its working perfectly.


SDK-248: resolve swizzling bug in push notifications handler

Corrected completion blocks usage to resolve #62

Hi @ygit
Thank you for the findings.
I have already added the change to our release branch.


Add Droidcon London 22 talk

Current dependencies on/for this PR:

main

PR #3   👈

This comment was auto-generated by Graphite.


bezierChartScale CUSTOM accept DateTime type

When using my DateTime data for xAxisand bezierChartScale: BezierChartScale.CUSTOM, I get an error (accepts only doubles):

lib/ui/common/logchart.dart:141:40: Error: The argument type 'List' can't be assigned to the parameter type 'List'

How can i have my filters (querys) to scale ?
many thanks

Yes, custom scale only accept double values but you can use
footerValueBuilder to display a custom footer.
On Mon, Jul 29, 2019, 1:30 PM Daniel Roviriego<EMAIL_ADDRESS>wrote:

When using my DateTime data for xAxisand bezierChartScale:
BezierChartScale.CUSTOM, I get an error (accepts only doubles):
lib/ui/common/logchart.dart:141:40: Error: The argument type 'List' can't
be assigned to the parameter type 'List'
How can i have my filters (querys) to scale ?
many thanks
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/aeyrium/bezier-chart/issues/28?email_source=notifications&email_token=ABFL3UDBI6GO3772JRL2CTLQB4ZK3A5CNFSM4IHVCCR2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HCDT5RA,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABFL3UB6CY4V2HIDHPDDOA3QB4ZK3ANCNFSM4IHVCCRQ
.


Lack of player score copying

Scoreboard operation does not accept PlayerScore, and PlayerScore.set does not accept another PlayerScore.

Ok for scoreboard operation, but I don't think I will add it.
PlayerScore.set actually accepts a PlayerScore. Can you show me a snippet of non-working code?
This works:
import { MCFunction } from "sandstone/core";
import { createObjective } from "../../sandstone/dist/variables";

MCFunction('test', () => {
  const myObjective = createObjective('test', 'dummy')
  const myPlayerScore1 = myObjective.ScoreHolder('@s')
  const myPlayerScore2 = myObjective.ScoreHolder('@r')
  myPlayerScore1.set(myPlayerScore2)
})

OH, the PlayerScore usage is an overload of set, not a | of number as I was expecting. Enormous brain.


fix Fitbit OAuth 1 authorization URL

According to
https://wiki.fitbit.com/display/API/OAuth+1.0a+Authentication#OAuth1.0aAuthentication-Notes,
the base url for the oauth authroization page is
https://www.fitbit.com, not https://api.fitbit.com. Soon they will
redirect authorize requests to api to www,
which will increase page load time for end users

:+1:

Thanks!


Question: about possible format option (line by line basis for users)

Version

Have not implemented yet
Development Environment

Have not implemented yet
Current Behavior

// Just a small question

Expected Behavior

Is it possible to format the calendar in a way that it has users on a line by line basis? (Used for applications such as shift scheduling). Something along the lines of this:

Completely understand if this is not possible and not in the pipeline but would be great to know if this kind of manipulation is possible?
Thanks for a great calendar!

@nicholasgcoles Thank you for your attention. It's possible to implement. Some guys need same thing, but requirements are not exactly defined and requested yet.

@dongsik-yoo thank you for your reply! Is there anything I can do to assist the process?


Add an incremental HTTP parser using the llhttp APIs

Goals:

[x] Can generate HTTP messages from llhttp callbacks without invoking C-to-Lua callbacks (which are extremely slow)
[x] The FFI layer's performance should be at least 80% (in the average case) of the raw llhttp performance
[x] Parsed messages that are too large to be buffered should trigger llhttp errors and not SEGFAULT or overwrite memory
[x] LuaJIT string buffers can optionally be used to store large body payloads (to faciliate streaming to temporary files, later)
[x] Buffered requests should be small enough to fit into common CPU caches (approximated by the 1k requirement for my i7)

I'm not 100% on the requirements here, since most special/fringe cases are either handled by the parser, or would need to be tested separately as part of #137 (and related issues). I suppose as long as "chunks" can be parsed and (llhttp) events are triggered on success/error, that's as good a starting point as any.
The main thing I've taken care of already is to allow forwarding events to Lua from C without incurring the 50x slowdown. Right now, the parser can replay events and generate (buffered) Lua requests/responses at about 40%+ native performance, which could clearly be better but also a lot worse. If more is needed, 60% to 95% should be possible by moving the HttpMessage generation to C as well, though it would require putting hardcoded limits on various things (and increase the risk of segfaults). Streaming is TBD.

The above design is still too slow. The final version amounted to about 16-20% of llhttp's performance. Considering there are many features that were missing, I might just go a different route and assemble the messages fully in C. This means:

Hardcoded size limits have to be used (via compile-time defines), to avoid lots of allocations
The limit can't be changed at runtime  :(
Streaming large messages will need a completely different design, and probably a new API
Extra features may also need to be (at least partially) added in C, which could be annoying if they're complex
On the plus side, the performance is basically 95-100% at all times so that concern is eliminated...

The current version should fulfill all requirements and allow future extension, for example streaming large files via libuv FS requests.
I'm sure a lot could be done to improve the implementation, but I guess it's good enough to move on to the HTTP RFCs for now.


[help] .pck file not found

Godot version
3.4.beta
System information
POP_OS, GLES 2/3, GTX 960 (nvidia-driver-470), ryzen 1600
Issue description
ERROR: Pack version unsupported: 1.
at: try_open_pack (core/io/file_access_pack.cpp:176)
ERROR: Pack version unsupported: 1.
at: try_open_pack (core/io/file_access_pack.cpp:176)
Error: Couldn't load project data at path ".". Is the .pck file missing?
If you've renamed the executable, the associated .pck file should also be renamed to match the executable's name (without the extension)
handle_crash: Program crashed with signal 11
Dumping the backtrace. Please include this when reporting the bug on https://github.com/godotengine/godot/issues
[1] /lib/x86_64-linux-gnu/libc.so.6(+0x41950) [0x7f8271ef5950] (??:0)
[2] ./VoxelDemo.x86_64() [0x71b3b7] (/home/chibbi/Downloads/godot/main/main.cpp:1083)
[3] ./VoxelDemo.x86_64() [0x6e25e1] (/home/chibbi/Downloads/godot/platform/linuxbsd/godot_linuxbsd.cpp:52)
[4] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf2) [0x7f8271edccb2] (??:0)
[5] ./VoxelDemo.x86_64() [0x6e9b6e] (??:?)
-- END OF BACKTRACE --
Aborted (core dumped)
Steps to reproduce
I dunno
I guess:

use godot 3.4.beta version from voxel_plugin
use this as a project: https://github.com/Zylann/voxelgame (commit: 0690648ff180f710dd8abff54f4c9a9c5b2e1789)
use official godot 3.4.beta (commit: 286e9b853315343c8ddc121098e412af812b3495) to create your export templates (for linux)

Minimal reproduction project
No response

./VoxelDemo.x86_64() [0x6e25e1] (/home/chibbi/Downloads/godot/platform/linuxbsd/godot_linuxbsd.cpp:52)

That's Godot 4 (master branch), not 3.4.

what, but i looked into the "about Godot" inside the program, and there is: "Godot Engine v3.4.beta.custom_build [526447b86]".

You probably have two different binaries, but this VoxelDemo.x86_64 one (i.e. your export template) was built from the master branch (linuxbsd is the name in master, in 3.x it's still x11).

Where do i find the 3.4.beta source? (so i can build the right export templates) xd

ah found it thx

ERROR: Pack version unsupported: 1.
at: try_open_pack (core/io/file_access_pack.cpp:176)

This should probably display a visible alert with OS::alert() when it's the main pack.


Dashboard Settings: Publisher Logos

Feature Description
The overarching work for this can be found here for context: https://github.com/google/web-stories-wp/issues/2747
Set up functionality in dashboard settings to read and update publisher logos from wordPress settings API
We will iterate from this on what the UI should look like for active logos, deleting logos, and updating the active logo.

Do not alter or remove anything below. The following sections will be managed by moderators only.
Acceptance Criteria
(all of this is behind a feature flag)

[x] Ability to read existing logos from API and render previews
[x] Active logo should come first in list
[x] If user has permissions ability to update logos ability to update logos (add and delete)
[x] If user does not have permissions to update logos this should be disabled
[x] Connect error handling to toaster
[x] Unit Tests
[x] Karma Tests

Implementation Brief

UI is already drafted behind feature flag, just need to add in functionality and state changes for permissions

Moving this to done. Feature work is complete and there's a separate ticket to enable feature flag after QA and UAT:  https://github.com/google/web-stories-wp/issues/4132


Multi-modal release

Things to do before the public release of new multi-modal narrative.

[x] implement and release attribute access: https://github.com/jina-ai/docarray/pull/425
[ ] write blog post
[ ] restructure docs
[ ] support access_path as traversal_path in core
[ ] discuss: should data class directly return a Document? @samsja
[ ] Q: How does mm play with storage backends and/or secondary index?

Step 3 does not imply core right now but Hub Executors


SSL_get0_chain_certs always returns zero

We are using OpenSSL-1.1.1. The function SSL_get0_chain_certs is always returning zero.
The following code in s3_lib.c is not setting return code, therefore the function ssl3_ctrl  always returns zero.
case SSL_CTRL_GET_CHAIN_CERTS:
        *(STACK_OF(X509) **)parg = s->cert->key->chain;
        break;

Fix in #9395.


Cache use cases

My primary use case is to give control to the developer over the caches that the memo function would use for function memoization. For example, Python offers a LRU policy with a customizable limit.
@syg from V8 said:

We have a lot of pressure, from my observations, of large and "expert" apps asking for GC hooking points and GC info to be exposed for the purpose of writing userland caches. They might misguidedly use WeakRefs right now, which, with a “maybe clear on every GC”, is a particularly bad cache eviction policy. One realization the V8 team has had recently is well, maybe there's space for directly designing caches instead of exposing GC stuff, which seems blech. […] I have not thought yet deeply about if LIFO and FIFO with a simple size are sufficiently flexible eviction policies. [Use cases would include] roughly, the same kind of things Java's soft reference and prio references tried to solve.

@rickbutton added:

Userland caches with gc-hooks has come up on our side internally as something people are really asking for. Not convinced but it keeps getting mentioned. We also had the thought “what if we provided a cache instead”.

We need to come up with specific isolated illustrations of these use cases and check if they would be adequately served by Map-like data structures with constant limits.

The withdrawn WICG memory-pressure proposal lists several use cases related to memory pressure and therefore to caching in general:

An application with an infinite-scroll wants to know if they need to remove items from their list and how agressively.
An application handling large files (photo/video sharing for example) wants to free up cache when the user's device need it.
An email application saving email content for fast interaction wants to free up the cache if it is needed by the system.


Fix the tests and add CI to run them

Please provide a description of the purpose of this pull request, as well as its
motivation and context.
This PR fixes the tests that were failing.
It also adds a GitHub workflow (CI) to the tests on push and pull request events to the master branch.
How was the code tested?
It was tested locally with both Centos 7 and Ubuntu focal LXD-deployed charms.
Also, the CI itself runs the tests.
Final checklist

[x] I am the author of these changes, or I have the rights to submit them.
[ ] I added the relevant changed to the README and/or documentation.
[x] I self reviewed my own code.
[ ] I updated the CHANGELOG according to the contributing
guide

Hey @heitorPB,
The test below fails randomly. I mean, it usually fails, but if I run the action again, It successfully passes.
Can you think of a reason for that?
not ok 13 test we can set a default partition
(from function `assert_output' in file tests/../node_modules/bats-assert/src/assert.bash, line 247,
in test file tests/10-slurm-partition.bats, line 32)
`assert_output --partial "$partition* "' failed

-- output does not contain substring --
substring (1 lines):
Default-test-partition*
output (3 lines):
PARTITION              AVAIL  TIMELIMIT  NODES  STATE NODELIST
Default-test-partition    up   infinite      1   idle juju-a0a8b2-2
Default-test-partition    up   infinite      1   down juju-a0a8b2-5
--


Refactoring method names.

Refactoring method names.

How about updating the tests too?
 ~/gh6/firebase-ios-sdk (emb/fdl-rm-fp-kw) $ git grep -i finger
FirebaseDynamicLinks/Tests/Unit/FIRDynamicLinksTest.m:- (void)testCustomScheme_FirstTimeOpenedFromFingerprintCodepathShouldGetWeakMatch {
FirebaseDynamicLinks/Tests/Unit/FIRDynamicLinksTest.m:      @"matchConfidence should be weak when app is first opened from fingerprint codepath.");

Done


Return error if multiple brackets exist in the authority

Fixes #435

I added a test which tests the exact string that causes the bug.

Thanks!


supersonic: 0.6.0 -> 0.7.0

Description of changes
Updating supersonic.
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[x] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[x] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 266134 run on aarch64-linux 1

2 packages built:

supersonic
supersonic-wayland


Callbacks not triggered when value updated at the class level before being set on an instance

Param allows to update the value of instances of a class from the class level, when the value hasn't yet been set (constructor or setattr), e.g.:
import param

class P(param.Parameterized):
    m = param.Parameter(0)
    n = param.Parameter(0)
    o = param.Parameter(0)

p = P(n=1)
p.o = 1
P.m = P.n = P.o = 2
print(f'{p.m=} {p.n=} {p.o=}')
# p.m=2 p.n=1 p.o=1

However, watching a parameter changed at the class level doesn't trigger its callbacks, while it certainly should:
import param

class P(param.Parameterized):
    m = param.Parameter()

    @param.depends('m', watch=True)
    def update(self):
        print(self.m)

p = P()
# Does NOT trigger `update`
P.m = 10
print(p.m)
# 10

I have a brief (late) look at this issue, I'm not sure how to trigger the callbacks of all the instances of a class when a watched Parameter is updated at the class level. @jbednar @philippjfr interested in your opinion and if it's worth spending time on this to get it in Param 2.0.

Yeah, this is awkward to fix. The only way to get all instances would be to keep (weak) references to all instances of a class or iterating over all objects in gc.get_objects(). Both of which seem less than ideal, although I can vaguely imagine the weakref approach. I'd say we skip this one for now.


Node v10 errors: no member named 'ForceSet' in 'v8::Object'

<EMAIL_ADDRESS><EMAIL_ADDRESS>  CXX(target) Release/obj.target/unix_dgram/src/unix_dgram.o
In file included from ../src/unix_dgram.cc:5:
In file included from ../../nan/nan.h:190:
../../nan/nan_maybe_43_inl.h:88:15: error: no member named 'ForceSet' in 'v8::Object'
  return obj->ForceSet(GetCurrentContext(), key, value, attribs);
         ~~~  ^

Same issue, first time trying Node 10, installing the zmq package.
Here's full output:
Signafy+mapper-annotator.git git:develop ❯ npm i

><EMAIL_ADDRESS>install /Users/trusktr/src/Signafy+mapper-annotator.git/node_modules/zmq
> node-gyp rebuild

xcode-select: error: tool 'xcodebuild' requires Xcode, but active developer directory '/Library/Developer/CommandLineTools' is a command line tools instance

xcode-select: error: tool 'xcodebuild' requires Xcode, but active developer directory '/Library/Developer/CommandLineTools' is a command line tools instance

  CXX(target) Release/obj.target/zmq/binding.o
In file included from ../binding.cc:29:
/usr/local/Cellar/zeromq/4.2.5/include/zmq_utils.h:42:32: warning: unknown warning group '-Werror', ignored [-Wunknown-warning-option]
#pragma GCC diagnostic ignored "-Werror"
                               ^
/usr/local/Cellar/zeromq/4.2.5/include/zmq_utils.h:45:9: warning: Warning: zmq_utils.h is deprecated. All its functionality is provided by zmq.h. [-W#pragma-messages]
#pragma message(                                                               \
        ^
In file included from ../binding.cc:38:
In file included from ../../nan/nan.h:190:
../../nan/nan_maybe_43_inl.h:88:15: error: no member named 'ForceSet' in 'v8::Object'
  return obj->ForceSet(GetCurrentContext(), key, value, attribs);
         ~~~  ^
In file included from ../binding.cc:38:
../../nan/nan.h:816:18: warning: 'MakeCallback' is deprecated: Use MakeCallback(..., async_context) [-Wdeprecated-declarations]
    return node::MakeCallback(
                 ^
/Users/trusktr/.node-gyp/10.1.0/include/node/node.h:171:1: note: 'MakeCallback' has been explicitly marked deprecated here
NODE_DEPRECATED("Use MakeCallback(..., async_context)",
^
/Users/trusktr/.node-gyp/10.1.0/include/node/node.h:88:20: note: expanded from macro 'NODE_DEPRECATED'
    __attribute__((deprecated(message))) declarator
                   ^
In file included from ../binding.cc:38:
../../nan/nan.h:830:18: warning: 'MakeCallback' is deprecated: Use MakeCallback(..., async_context) [-Wdeprecated-declarations]
    return node::MakeCallback(
                 ^
/Users/trusktr/.node-gyp/10.1.0/include/node/node.h:164:1: note: 'MakeCallback' has been explicitly marked deprecated here
NODE_DEPRECATED("Use MakeCallback(..., async_context)",
^
/Users/trusktr/.node-gyp/10.1.0/include/node/node.h:88:20: note: expanded from macro 'NODE_DEPRECATED'
    __attribute__((deprecated(message))) declarator
                   ^
In file included from ../binding.cc:38:
../../nan/nan.h:844:18: warning: 'MakeCallback' is deprecated: Use MakeCallback(..., async_context) [-Wdeprecated-declarations]
    return node::MakeCallback(
                 ^
/Users/trusktr/.node-gyp/10.1.0/include/node/node.h:157:1: note: 'MakeCallback' has been explicitly marked deprecated here
NODE_DEPRECATED("Use MakeCallback(..., async_context)",
^
/Users/trusktr/.node-gyp/10.1.0/include/node/node.h:88:20: note: expanded from macro 'NODE_DEPRECATED'
    __attribute__((deprecated(message))) declarator
                   ^
In file included from ../binding.cc:38:
../../nan/nan.h:1457:31: warning: 'MakeCallback' is deprecated: Use MakeCallback(..., async_context) [-Wdeprecated-declarations]
    return scope.Escape(node::MakeCallback(
                              ^
/Users/trusktr/.node-gyp/10.1.0/include/node/node.h:171:1: note: 'MakeCallback' has been explicitly marked deprecated here
NODE_DEPRECATED("Use MakeCallback(..., async_context)",
^
/Users/trusktr/.node-gyp/10.1.0/include/node/node.h:88:20: note: expanded from macro 'NODE_DEPRECATED'
    __attribute__((deprecated(message))) declarator
                   ^
6 warnings and 1 error generated.
make: *** [Release/obj.target/zmq/binding.o] Error 1
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:258:23)
gyp ERR! stack     at ChildProcess.emit (events.js:182:13)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:235:12)
gyp ERR! System Darwin 17.5.0
gyp ERR! command "/usr/local/Cellar/node/10.1.0/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /Users/trusktr/src/Signafy+mapper-annotator.git/node_modules/zmq
gyp ERR! node -v v10.1.0
gyp ERR! node-gyp -v v3.6.2
gyp ERR! not ok
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

┌────────────────────────────────────────────────────────────┐
│                  npm update check failed                   │
│            Try running with sudo or get access             │
│            to the local update config store via            │
│ sudo chown -R $USER:$(id -gn $USER) /Users/trusktr/.config │
└────────────────────────────────────────────────────────────┘

npm ERR!      /Users/trusktr/.npm/_logs/2018-05-25T05_14_50_946Z-debug.log

@kkoopa which version of nan should be used with node 10.x? Running npm show nan versions returns 2.10 as the highest version, and that version doesn't seem to work with 10.x.

2.10 works fine. Any errors you get come from something else pulling in an older version of NAN or using V8 functions not included in Node 10.

In my case the thing pulling nan < 2.10 was node-sass 4.7.3 - fixed by upgrading it to latest 4.9.3. Just adding nan 2.10 to package.json didn't help.


Update sql-database-aad-authentication.md

Typo correction :
Azure SQL Serve ror SQL Data Warehouse
to
Azure SQL Serve or SQL Data Warehouse:

Hi @MattBrowne, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no contribution license agreement is required at this point. Real humans will now evaluate your PR.

TTYL, AZPRBOT;

@MattBrowne : Thanks for your contribution to the Azure documentation! The author, @BYHAM, has been notified to review your proposed change.

#sign-off


[TE] Added /application/reset API +refactor

Description

Added /application/reset/{name}. Resets an application
Reset Usage: Primarily for demo purposes. It cleans up all old alerts and anomalies for an application
Refactored /delete API code. reuse of deleteDependents and getByName methods
Removed manual exception handling since Jersey throws 500 by default

No backward incompatible changes.

Thanks a lot @akshayrai !


SQL LAB - unexpected error

Bug description
When selecting "SQL" and then "SQL Lab" a big red popup appears with the words "Unexpected error" and a "See more " link to the right.

How to reproduce the bug

Select "SQL" from the top bar menu.
Select "SQL Lab" from the dropdown menu

Screenshots/recordings

Superset version
4.0.1
Python version
3.9
Node version
16
Browser
Firefox
Additional context
It's actually version 4.0.2 Docker from hub.docker.com (treating this as an "official" version.
The container is:     image: apache/superset:linux-arm64-4.0.2
The old V2 container (home brew) was working quite well. Most things in 4.0.2 seem to be working correctly. Right now I can't create a virtual dataset without SQL Lab's assistance.
It may be a client side issue?

[X] I have searched the GitHub issue tracker and didn't find a similar bug report.
[X] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.

Thanks for that. That fix appears to be dated 2022. Should I expect that to be included in version 4.0.2?
Here is a more or less identical screen grab from Windows Edge browser (It may not be the browser doing this):

@electricbrain-code run the below commands after restart the service:
export FLASK_APP=superset
superset db upgrade
superset init

Completely fixed.
Thankyou and best regards
superset@ac2026f63635:/app$ export FLASK_APP=superset
superset@ac2026f63635:/app$ superset db upgrade
Loaded your LOCAL configuration at [/app/pythonpath/superset_config.py]
logging was configured successfully
2024-07-04 15:34:46,145:INFO:superset.utils.logging_configurator:logging was configured successfully
2024-07-04 15:34:46,166:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
/usr/local/lib/python3.9/site-packages/flask_limiter/extension.py:293: UserWarning: Using the in-memory storage for tracking rate limits as no storage was explicitly specified. This is not recommended for production use. See: https://flask-limiter.readthedocs.io#configuring-a-storage-backend for documentation about configuring the storage backend.
warnings.warn(
WARNI [alembic.env] SQLite Database support for metadata databases will         be removed in a future version of Superset.
INFO  [alembic.runtime.migration] Context impl SQLiteImpl.
INFO  [alembic.runtime.migration] Will assume transactional DDL.
superset@ac2026f63635:/app$ superset init
Loaded your LOCAL configuration at [/app/pythonpath/superset_config.py]
logging was configured successfully
2024-07-04 15:36:37,176:INFO:superset.utils.logging_configurator:logging was configured successfully
2024-07-04 15:36:37,196:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
/usr/local/lib/python3.9/site-packages/flask_limiter/extension.py:293: UserWarning: Using the in-memory storage for tracking rate limits as no storage was explicitly specified. This is not recommended for production use. See: https://flask-limiter.readthedocs.io#configuring-a-storage-backend for documentation about configuring the storage backend.
warnings.warn(
Syncing role definition
2024-07-04 15:36:56,915:INFO:superset.security.manager:Syncing role definition
Syncing Admin perms
2024-07-04 15:36:57,403:INFO:superset.security.manager:Syncing Admin perms
Syncing Alpha perms
2024-07-04 15:36:57,484:INFO:superset.security.manager:Syncing Alpha perms
Syncing Gamma perms
2024-07-04 15:36:59,576:INFO:superset.security.manager:Syncing Gamma perms
Syncing sql_lab perms
2024-07-04 15:37:01,673:INFO:superset.security.manager:Syncing sql_lab perms
Fetching a set of all perms to lookup which ones are missing
2024-07-04 15:37:03,749:INFO:superset.security.manager:Fetching a set of all perms to lookup which ones are missing
Creating missing datasource permissions.
2024-07-04 15:37:03,811:INFO:superset.security.manager:Creating missing datasource permissions.
Creating missing database permissions.
2024-07-04 15:37:03,864:INFO:superset.security.manager:Creating missing database permissions.
Cleaning faulty perms
2024-07-04 15:37:03,895:INFO:superset.security.manager:Cleaning faulty perms

Closing