[BUG] Cannot locate my database directory on disk

System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Linux Ubuntu 20.04
FiftyOne installed from (pip or source): pip
FiftyOne version (run fiftyone --version): 0.14.4
Python version: 3.8.10

Commands to reproduce
import fiftyone as fo

fo.config.default_dataset_dir = 'data/alen/FiftyOne_DB'

dataset = fo.Dataset('Test')
dataset.persistent = True

print(fo.list_datasets())  # Returns ['Test']
print(fo.core.dataset.get_default_dataset_dir('Test'))  # Returns '/data/alen/FiftyOne_DB/Test'

Describe the problem
I am trying to verify that the database is being written on my custom path, since I do not want to blow up my SSD (where the library is stored). However when I look into the folder 'data/alen/FiftyOne_DB', it is completely empty (even no hidden files). Can anybody help me to clarify this? :)
Code to reproduce issue
provided above
Other info / logs
/
What areas of FiftyOne does this bug affect?

[ ] App: FiftyOne application issue
[X ] Core: Core fiftyone Python library issue
[ ] Server: Fiftyone server issue

Willingness to contribute
The FiftyOne Community encourages bug fix contributions. Would you or another
member of your organization be willing to contribute a fix for this bug to the
FiftyOne codebase?

[ ] Yes. I can contribute a fix for this bug independently.
[ ] Yes. I would be willing to contribute a fix for this bug with guidance
from the FiftyOne community.
[X ] No. I cannot contribute a bug fix at this time.

Hi @alen-smajic. database_dir (not default_dataset_dir) is the option you are looking for. See configuring FiftyOne for more details.

Pro tip: run fiftyone config from your shell to see the current value of database_dir for your deployment.
FYI- database_dir is not something you can change at runtime in Python, because the database connection is established immediately when import fiftyone occurs.
You can definitely customize database_dir, but you must do it either by setting this environment variable:
export FIFTYONE_DATABASE_DIR=/path/for/db

or by adding it to your FiftyOne config at ~/.fiftyone/config.json (create one if you haven't used this feature yet):
{
    "database_dir": "/path/for/db",
    ...
}

See this page for more information about configuring FiftyOne.

FYI- database_dir is not something you can change at runtime in Python, because the database connection is established immediately when import fiftyone occurs.

I think this is something that is not mentioned in the docs :). Before posting my issue I also tried to set
fo.config.database_dir = "/data/alen/Master_Thesis/FiftyOne_DB"
inside of my python script, but obviously it did not work.
So I went with the option of creating a FiftyOne config file at ~/.fiftyone/config.json.  Everything is working fine, unless I try to change the database_dir then I always get this error:
{"t":{"$date":"2022-02-17T07:47:37.536Z"},"s":"I",  "c":"CONTROL",  "id":20697,   "ctx":"main","msg":"Renamed existing log file","attr":{"oldLogPath":"/data/FiftyOne_data/log/mongo.log","newLogPath":"/data/FiftyOne_data/log/mongo.log.2022-02-17T07-47-37"}}
Subprocess ['/home/alen/Master_Thesis/venv/lib/python3.8/site-packages/fiftyone/db/bin/mongod', '--dbpath', '/data/FiftyOne_data', '--logpath', '/data/FiftyOne_data/log/mongo.log', '--port', '0', '--nounixsocket'] exited with error 14:
I also deleted the folder ~/.fiftyone/var as I have seen in previous issues that this often helped. However the error message is still the same.

Are you saying there's a problem when you set database_dir before importing Python? Or are you just pointing out that if you change fo.config.database_dir within in Python session then you start getting errors?
You are not allowed to change database_dir within a session, period.

I was just pointing out that I was trying to change fo.config.database_dir within a Python session before you clarified that, it is not allowed to do so. That's why I pointed out, that it would be maybe helpful to add that information in the docs :).
However right now I am having problems when trying to import fiftyone with my config file at ~/.fiftyone/config.json. As soon as I edit the fo.config.database_dir property, the import of fiftyone will fail with the error message posted above.

I have tried out a few things and I think I found the core of the problem.
So the server I am using has a SSD where the fiftyone library has been installed and where my home folder is ('/home/alen'). The server has also an additional external hard drive mounted at '/data', which I want to use to store the database.
I have made sure to set the permission on '/data/FiftyOne_db' (the folder which I want to use for storing the database), but I always keep getting the same error and the log files have many 'Operation not permitted' messages, which means that there is some kind of permission error. However, when I set the database path to be anywhere inside the SSD for example '/home/fiftyOne_db', it works without any problems.
For me it seems like its kinda related to the usage of a different hard drive and mongodb. Any ideas or suggestions :)?

You haven't set the permissions on /data/FiftyOne_db correctly yet. /data is probably owned by root whereas your home directory is owned by your user.
chmod 777 /data/FiftyOne_db would definitely work, but you should probably chown the /data drive to your current user. Or better create a group, and yourself to it, make the group the owner of /data, and then use something like chmod 774 to set the permissions.


refactoring and reorganization for module and test management

Renamed src to bernoullid and added init.py to form a python-recognized package. Imports are handled by importing everything absolutely (with respect to the repository) this mean that scrips will need to be run from root.  unittests were moved to bernoullid/tests to encourage expansion.
commands that work from root:
python main.py
python -m unittest bernoullid/tests/test_unittests.py (all tests passed)

I've incorporated these changes into the PR #21, so I think this PR can be closed. Thoughts?


closes #1659: proper handling of retries for unprepared errors in grpc

What this PR does:
Extends the grpc RetryPolicy in order to allow specific retries for the UNPREPARED error code. Currently allows limites retries, but we should agree in this PR if this is fine or not. See #1659 for more details.
Which issue(s) this PR fixes:
Fixes #1659
Checklist

[x] Automated Tests added/updated

@mpenick Let's agree if limitless retries are fine? Can adapt to whatever we want..

I think I'd prefer we cap the number of retries. Default to 1 or 2, and potentially have a property to set to something higher. I'm worried at the potential for something like this to spin in a loop because of a defect.

Fixed to 2 retries. As other methods don't expose a property for their limits, I kept the same behavior here as well.. Let's see if this passes our test now..


better Makefile

change Makefile

Thank you for your PR!
I've been struggling to create a good makefile but failed.
You saved my life


Invoke Customisation Step Function exceeded maximum output limit

Terraform Version & Prov:
AFT Version:
(Can be found in the AFT Management Account in the SSM Parameter /aft/config/aft/version)
1.7.0
Terraform Version & Provider Versions
Please provide the outputs of terraform version and terraform providers from within your AFT environment
terraform version
1.3.7

terraform providers
provider[registry.terraform.io/hashicorp/aws] ~> 4.26

Bug Description
When I invoke a customisation step that involves many accounts, I run into a quota of Step Functions, namely the "Maximum input or output size for a task, state, or execution"
{
  "Error": "States.DataLimitExceeded",
  "Cause": "The state/task 'arn:aws:lambda:ap-southeast-1:123456789012:function:aft-customizations-identify-targets' returned a result with a size exceeding the maximum number of bytes service limit."
}

This is a combination of the large number of accounts (100+) and the amount of data we have in custom fields.
To Reproduce
Steps to reproduce the behavior:

Create large number of accounts.
Fill account requests with sufficient amount of custom fields
Invoke Customisation to target a large number of accounts
See error

{
  "Error": "States.DataLimitExceeded",
  "Cause": "The state/task 'arn:aws:lambda:ap-southeast-1:123456789012:function:aft-customizations-identify-targets' returned a result with a size exceeding the maximum number of bytes service limit."
}

Expected behavior
To not fail
Related Logs
I can provide the lambda logs in a more private method if you need it.
Additional context
he recommended solution from the Step Functions documentation is to store the data somewhere else (e.g. S3) and pass around the ARN instead of raw JSON.

Hey @lawliet89!
Thank you for pointing out this issue! I went ahead and created an item in our backlog for this issue. Thanks!!

May I suggest you use a DynamoDB table rather than an S3 bucket for this?
The former is lightweight and fast, the latter is more work to manage.
On Wed, 18 Jan 2023 at 20:45, hanafya @.***> wrote:

Hey @lawliet89 https://github.com/lawliet89!
Thank you for pointing out this issue! I went ahead and created an item in
our backlog for this issue. Thanks!!
—
Reply to this email directly, view it on GitHub
https://github.com/aws-ia/terraform-aws-control_tower_account_factory/issues/298#issuecomment-1387675539,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAA6OJBITDLLNCAVXHTFFTWTBB6DANCNFSM6AAAAAAT6RED3M
.
You are receiving this because you are subscribed to this thread.Message
ID:
<aws-ia/terraform-aws-control_tower_account_factory/issues/298/1387675539@
github.com>

Encountering the same issue, any delivery date for the fix ? Many thanks !

Having the same issue, any delivery date for the fix ? Thanks !

What's going on with this bug? This causes a hard fail on the entire step function and prevents any customization from being applied. This is causing a hard limit on the number of accounts we can manage with AFT even with limited custom field data.

This starts to cause hard failures in our environment with even a modest number of accounts processing at once... I've seen it fail with even 15 or so accounts.  This is a major scalability problem in the platform and should be addressed.
We would be able to put in a PR for this issue.... if AFT was open for collaboration.

Same issue


prisma migrate resolve --applied not working on new project, migration ... could not be found.

As mentioned in another issue: Following the Tutorial to baseline a database when using prisma in a new project with an existing database leads to an error:
The final step npx prisma migrate resolve --applied 0_init leads to the following error:

Error: P3017
The migration 0_init could not be found. Please make sure that the migration exists, and that you included the whole name of >the directory. (example: "20201207184859_initial_migration")

The database (in my case) is mssql - if it makes any difference.
The steps before (pulling, generating, creating migrations-directory and creating diff-sql) are all successful.
I tried the following things:

Putting folder in quotes: npx prisma migrate resolve --applied "0_init"
Passing the complete path: npx prisma migrate resolve --applied ./prisma/migrations/0_init
Passing the complete path with filename: npx prisma migrate resolve --applied ./prisma/migrations/0_init/migration.sql
Changing into prisma-directory and executing command
Changing into prisma/migrations-directory and executing command
Renaming folder "0_init" to "20201207184859_initial_migration" (I know, it's stupid) and running npx prisma migrate resolve --applied<PHONE_NUMBER>4859_initial_migration

… to no avail.

For reference: Here is the relevant comment from the other issue:
Hi I'm facing the same issue as @mrunalhajare. Here is what I'm doing:

1. `npx prisma db pull` -- Populates schema.prisma correctly
2. `npx prisma generate` -- Success generating
3. `mkdir -p prisma/migrations/init`
4. `npx prisma migrate diff --from-empty --to-schema-datamodel prisma/schema.prisma --script > prisma/migrations/init/migration.sql` -- Creates migration.sql file in prisma/migrations/init directory
5. `npx prisma migrate resolve --applied init` -- ERROR

> Error: P3017
>
> The migration init could not be found. Please make sure that the migration exists, and that you included the whole name of the directory. (example: "20201207184859_initial_migration")

NOTE: I did manually create `migration_lock.toml` before step 5 above, but I get the same error.

Anything I'm doing wrong?

Originally posted by @simplypress in https://github.com/prisma/prisma/issues/11555#issuecomment-1331671279

So your project now has a prisma/migrations/0_init folder with a migration.sql file in it?
Are you excecuting the npx prisma migrate resolve --applied command in the root of your project?
Can you maybe but your full project on GitHub (replace sensitive information) and share the link with us?

I am experiencing the same issue, but it only occurs with IntelliJ IDEA. I followed these steps:

nest new check-prisma
cd check-prisma
npm install prisma --save-dev
npx prisma init
npx prisma db pull
mkdir -p prisma/migrations/0_init
npx prisma migrate diff --from-empty --to-schema-datamodel prisma/schema.prisma --script > prisma/migrations/0_init/migration.sql
npx prisma migrate resolve --applied 0_init

I only executed these commands above.
In Visual Studio Code, applying "0_init" was successful,
but in IntelliJ IDEA, it failed. I tried these steps on a Windows PC and PowerShell.

@janpio To answer your questions:

Yes, my project now has a prisma/migrations/0_init folder with a migration.sql file in it.
Yes, as described in the first post. I executed the command from root (and only out of desperation from ./prisma).
Please have a look at https://github.com/notmyfiles/prisma_migrate_debug
I documented all the console/manual steps I took in the Readme.
For me the error occurs in Visual Studio Code or even when I just run the migrate-command from cmd.

I'm having the same issue in VSCode.  Running from the root of the project and following the directions for adding Prisma to an existing project. Same error as the issue creator.

I just tried to reproduce this:
C:\Users\Jan\Documents\throwaway>mkdir 17558

C:\Users\Jan\Documents\throwaway>cd 17558

C:\Users\Jan\Documents\throwaway\17558>npm install prisma @prisma/client && npx prisma init && code .

added 4 packages, and audited 5 packages in 8s

found 0 vulnerabilities

✔ Your Prisma schema was created at prisma/schema.prisma
  You can now open it in your favorite editor.

Next steps:
1. Set the DATABASE_URL in the .env file to point to your existing database. If your database has no tables yet, read https://pris.ly/d/getting-started
2. Set the provider of the datasource block in schema.prisma to match your database: postgresql, mysql, sqlite, sqlserver, mongodb or cockroachdb.
3. Run prisma db pull to turn your database schema into a Prisma schema.
4. Run prisma generate to generate the Prisma Client. You can then start querying your database.

More information in our documentation:
https://pris.ly/d/getting-started

C:\Users\Jan\Documents\throwaway\17558>npx prisma db pull
Prisma schema loaded from prisma\schema.prisma
Environment variables loaded from .env
Datasource "db": PostgreSQL database "pink_alligator", schema "public" at "db-provision-postgres23452b4.c8yxynpcltwd.us-east-1.rds.amazonaws.com:5432"

✔ Introspected 1 model and wrote it into prisma\schema.prisma in 4.14s

Run prisma generate to generate Prisma Client.

C:\Users\Jan\Documents\throwaway\17558>mkdir -p prisma\migrations\0_init

C:\Users\Jan\Documents\throwaway\17558>npx prisma migrate diff --from-empty --to-schema-datamodel prisma/schema.prisma --script > prisma/migrations/0_init/migration.sql

PS C:\Users\Jan\Documents\throwaway\17558> cat prisma/migrations/0_init/migration.sql
-- CreateTable
CREATE TABLE "workspace_folder" (
    "id" UUID NOT NULL,
    "name" TEXT NOT NULL,
    "workspaceId" UUID NOT NULL,

    CONSTRAINT "workspace_folder_pkey" PRIMARY KEY ("id")
);

-- CreateIndex
CREATE INDEX "workspace_folder_wid_index" ON "workspace_folder"("workspaceId");

C:\Users\Jan\Documents\throwaway\17558>npx prisma migrate resolve --applied 0_init
Environment variables loaded from .env
Prisma schema loaded from prisma\schema.prisma
Datasource "db": PostgreSQL database "pink_alligator", schema "public" at "db-provision-postgres23452b4.c8yxynpcltwd.us-east-1.rds.amazonaws.com:5432"
Migration 0_init marked as applied.

C:\Users\Jan\Documents\throwaway\17558>cat prisma/migrations/0_init/migration.sql
'cat' is not recognized as an internal or external command,
operable program or batch file.

C:\Users\Jan\Documents\throwaway\17558>

So seems everything is working for me here. What am I doing different than you?

I could reproduce with your repository @notmyfiles. Let's see if we can figure out what is going on.

I could isolate the difference of your and my project, it is literally only the encoding of the file:

Somehow that is throwing us off. But I have a reproduction now thanks to your repository @notmyfiles - so we can investigate this. Thanks!

I checked about the first 2 commands: I wrote it down in the wrong order, but did them in the correct order 🙃.
Anyway, I tried everything again - once in the VSCode terminal (which uses powershell) and once outside VSCode using cmd.exe.
The command npx prisma migrate diff --from-empty --to-schema-datamodel prisma/schema.prisma --script > prisma/migrations/0_init/migration.sql seems to be the culprit – VSCode/powershell lead to the error, cmd not. As you noticed: VSCode or powershell seem to use a different encoding.
So either prisma migrate resolve or … diff has to be fixed to deal with different encodings.
Thanks for your detective work!

Ahh, creating the diff via VSCode is a good idea. Let me do that. I used cmd or Powershell externally.

Based on the excellent information that @notmyfiles provided, here is a reproduction repository that shows both a working and a non-working migration file: https://github.com/janpio/prisma-repro-17558
Maybe follow the steps in the README @notmyfiles to confirm. (Also for @kraighamady and @rahInoue - but you using VSCode and Intellij would fit nicely here of course)
We definitely need to fix migrate resolve here (and other commands that probably would have a problem with this file).

Thank you for investigating! I have tried the prisma db pull in various databases, but some encodings have caused character corruption in IntelliJ. This may be the same cause. If it continues, I will report back again. Thank you!

@janpio I just deleted my migration.sql file and reran the last two commands from the quickstart and it worked. The key was I used Git Bash instead of PS or the default PS in VSCode.
I didn't take a look at the encoding of the files,, but just recreating the initial migration in bash did the trick.

I could isolate the difference of your and my project, it is literally only the encoding of the file:
Somehow that is throwing us off. But I have a reproduction now thanks to your repository @notmyfiles - so we can investigate this. Thanks!

I could isolate the difference of your and my project, it is literally only the encoding of the file:
Somehow that is throwing us off. But I have a reproduction now thanks to your repository @notmyfiles - so we can investigate this. Thanks!

I can confirm it's the file encoding as well.
After changing the it Windows 1252, the issue goes away.

This was fixed by changing the encoding of the generated migration.sql file! I changed it to UTF-8 and it works like a charm!

This was fixed by changing the encoding of the generated migration.sql file! I changed it to UTF-8 and it works like a charm!

That Fixed it for me too!

Thanks for the investigation! It did not work on vscode/powershell but it works just fine in cmd :D

Hi, thank you for al the context, but I'm still having the same issue .. i'm in MacOs with VsCode
Any idea guys would be helpful :-)
thank you so much

Hi, thank you for al the context, but I'm still having the same issue .. i'm in MacOs with VsCode
Any idea guys would be helpful :-)
thank you so much

Does it work using the terminal?

Hi, thank you for al the context, but I'm still having the same issue .. i'm in MacOs with VsCode
Any idea guys would be helpful :-)
thank you so much

Does it work using the terminal?

Not, I also tried the terminal and it does not work either !

Hi, thank you for al the context, but I'm still having the same issue .. i'm in MacOs with VsCode
Any idea guys would be helpful :-)
thank you so much

Check the location of your schema.prisma file, seems like the migration folder should be relative to that file as follows:
Correct options:
./prisma/schema.prisma
./prisma/migrations/0_init/migration.sql

./schema.prisma
./migrations/0_init/migration.sql

It will fail if you mix the above locations. E.g.:
./schema.prisma
./prisma/migrations/0_init/migration.sql

That solved it for me, good luck!

I faced similar issue when using powershell. Try the command from git bash it works.
npx prisma migrate resolve --applied 0_init

It's Not working on Powershell. you have to change the terminal to maybe git bash or other, and then it will work

you can also change the encoding format in vs code and run the command from your usual terminal, like mentioned below
If you're using VsCode and your 0_init/migration.sql is in the wrong encoding you can:

Open the file 0_init/migration.sql
Press Ctrl+Shift+p
Type "Change File Encoding"
Select "Save With Encoding"
Select "UTF-8"

got it from here https://github.com/prisma/prisma/issues/14762#issuecomment-1533177502

Hey guys i am currently trying to setup Prisma with my nuxt/supabase project and I just had the same exact issue, I am less experimented on the Database / backend and I just wanted to maybe put a reminder that the issue is still there ?
I tried to execute the commands from Vscode and Cmd, both did not work for me.
It was a real pain to setup, thanks to this thread which helped a lot.  As someone stated, the git bash is what did it for me.

moayadmgh

thanks!!

@janpio I just deleted my migration.sql file and reran the last two commands from the quickstart and it worked. The key was I used Git Bash instead of PS or the default PS in VSCode.
I didn't take a look at the encoding of the files,, but just recreating the initial migration in bash did the trick.

This worked for me, thanks!

This was fixed by changing the encoding of the generated migration.sql file! I changed it to UTF-8 and it works like a charm!

Worked for me, thanks!!

I checked about the first 2 commands: I wrote it down in the wrong order, but did them in the correct order 🙃. Anyway, I tried everything again - once in the VSCode terminal (which uses powershell) and once outside VSCode using cmd.exe. The command npx prisma migrate diff --from-empty --to-schema-datamodel prisma/schema.prisma --script > prisma/migrations/0_init/migration.sql seems to be the culprit – VSCode/powershell lead to the error, cmd not. As you noticed: VSCode or powershell seem to use a different encoding. So either prisma migrate resolve or … diff has to be fixed to deal with different encodings. Thanks for your detective work!

I my case, VSCode powershell got the same problem. When I paste the command, it became:

It seems have problem with Less than character >
When I tried switch to Git Bash terminal, the error disappear

Hi, thank you for al the context, but I'm still having the same issue .. i'm in MacOs with VsCode
Any idea guys would be helpful :-)
thank you so much

Check the location of your schema.prisma file, seems like the migration folder should be relative to that file as follows:
Correct options:
./prisma/schema.prisma
./prisma/migrations/0_init/migration.sql

./schema.prisma
./migrations/0_init/migration.sql

It will fail if you mix the above locations. E.g.:
./schema.prisma
./prisma/migrations/0_init/migration.sql

That solved it for me, good luck!

thanks a lot! you'll go to heaven for this (unless you prefer otherwise ;))


Smooth-scrolling does not support mouse scrolling inside lit-component in chrome

So when trying out your example in https://dile-components.polydile.com/components/dile-smooth-scroll/ it works perfectly in firefox. In chrome however it is not possible to scroll inside the bottom textarea with a mouse scroller.
If I set the page overflow: hidden it works - but not out of the box.
Kooha-2023-09-26-12-43-44.webm

In a browser with no plugins - i cannot reproduce.


PR for issues #142 and #143

This is a first implementation to provide the features mentioned in Issue #142 and #143 .

Thanks for the PR!

@UnsignedLong please let us know when u want this to be reviewed

@ideahitme I'm done - so free for review.

thanks for PR @UnsignedLong , here is the follow up https://github.com/kubernetes-incubator/external-dns/pull/160


Get File Size Estimation

Hi,
In my project, we will need to show the filesize that will be downloaded. Is there anyway to do this using TableExport?
Thanks.

@muzavan – you can get the size, in bytes, by calling the Blob constructor. I will need to put in a method to retrieve this (for xls and xlsx) since it is internal at the moment.


Link to "application design" in README is broken

Link goes to https://github.com/microservices-demo/microservices-demo/blob/master/docs/internal-docs/design.md
instead of https://github.com/microservices-demo/microservices-demo/blob/master/internal-docs/design.md

The broken links have been fixed. Thanks for reporting @tedmdelacruz!


Add a Gitter chat badge to README.md

tabatkins/bikeshed now has a Chat Room on Gitter
@tabatkins has just created a chat room. You can visit it here: https://gitter.im/tabatkins/bikeshed.
This pull-request adds this badge to your README.md:

If my aim is a little off, please let me know.
Happy chatting.
PS: Click here if you would prefer not to receive automatic pull-requests from Gitter in future.

Added manually.


added balances and signatures to OverflowTransaction

Pull Request Test Coverage Report for Build<PHONE_NUMBER>6
Details

36 of 36 (100.0%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.09%) to 75.087%

Totals

Change from base Build<PHONE_NUMBER>0:
0.09%

Covered Lines:
2149

Relevant Lines:
2862

💛  - Coveralls


Windows 8.1 >> berks install fails SSLv3 error

I'm trying to perform berks install from an existing cookbook.
I've installed chefdk 0.4.0
I've found and tried several solutions I found here or stackoverflow. To no avail.
Let me know if you need any more information. (and perhaps explain how to get it, since this is my first time doing this)
So, when i do berks install I get this error:
Fetching cookbook index from https://supermarket.getchef.com...
C:/opscode/chefdk/embedded/lib/ruby/2.0.0/net/http.rb:918:in `connect': SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify
 failed (Faraday::SSLError)
        from C:/opscode/chefdk/embedded/lib/ruby/2.0.0/net/http.rb:918:in `block in connect'
        from C:/opscode/chefdk/embedded/lib/ruby/2.0.0/timeout.rb:66:in `timeout'
        from C:/opscode/chefdk/embedded/lib/ruby/2.0.0/net/http.rb:918:in `connect'
        from C:/opscode/chefdk/embedded/lib/ruby/2.0.0/net/http.rb:862:in `do_start'
        from C:/opscode/chefdk/embedded/lib/ruby/2.0.0/net/http.rb:851:in `start'
        from C:/opscode/chefdk/embedded/lib/ruby/2.0.0/net/http.rb:1367:in `request'
        from C:/opscode/chefdk/embedded/lib/ruby/2.0.0/net/http.rb:1126:in `get'
        from C:/Users/ME/.chefdk/gem/ruby/2.0.0/gems/faraday-0.9.1/lib/faraday/adapter/net_http.rb:80:in `perform_request'
        from C:/Users/ME/.chefdk/gem/ruby/2.0.0/gems/faraday-0.9.1/lib/faraday/adapter/net_http.rb:40:in `block in call'
        from C:/Users/ME/.chefdk/gem/ruby/2.0.0/gems/faraday-0.9.1/lib/faraday/adapter/net_http.rb:87:in `with_net_http_connection'
        from C:/Users/ME/.chefdk/gem/ruby/2.0.0/gems/faraday-0.9.1/lib/faraday/adapter/net_http.rb:32:in `call'
        from C:/Users/ME/.chefdk/gem/ruby/2.0.0/gems/faraday-0.9.1/lib/faraday/request/retry.rb:110:in `call'
        from C:/Users/ME/.chefdk/gem/ruby/2.0.0/gems/faraday-0.9.1/lib/faraday/response.rb:8:in `call'
        from C:/Users/ME/.chefdk/gem/ruby/2.0.0/gems/faraday-0.9.1/lib/faraday/response.rb:8:in `call'
        from C:/Users/ME/.chefdk/gem/ruby/2.0.0/gems/faraday-0.9.1/lib/faraday/rack_builder.rb:139:in `build_response'
        from C:/Users/ME/.chefdk/gem/ruby/2.0.0/gems/faraday-0.9.1/lib/faraday/connection.rb:377:in `run_request'
        from C:/Users/ME/.chefdk/gem/ruby/2.0.0/gems/faraday-0.9.1/lib/faraday/connection.rb:140:in `get'
        from C:/opscode/chefdk/embedded/lib/ruby/gems/2.0.0/gems/berkshelf-api-client-1.2.1/lib/berkshelf/api_client/connection.rb:62:in `universe'
        from C:/opscode/chefdk/embedded/apps/berkshelf/lib/berkshelf/source.rb:22:in `build_universe'
        from C:/opscode/chefdk/embedded/apps/berkshelf/lib/berkshelf/installer.rb:21:in `block (2 levels) in build_universe'

I've been researching this some more. Haven't found a solution yet.
One thing that appears strange to me is that part of the trace comes from C:/opscode/chefdk and so on..
While another part comes from C:/Users/ME/.chefdk....

Ok so in my desperation I have disabled SSL verification of the embedded Ruby version.
So just a 'workaround', and not an actual solution.

The windows ruby build we use has a broken hard-coded path to the SSL certificate bundle, which we try to work around by patching Ruby to set an environment variable pointing to the correct cert bundle. Can you post the last few lines of your openssl.rb file? You can find it with chef gem which openssl (in a unix-y shell, tail $(chef gem which openssl) would work). You should have require 'ssl_env_hack' as the last line.
Also, can you make sure you do not have the environment variable SSL_CERT_FILE set to anything? Our patch works by setting that variable to the correct path to the certificates, but it does not change anything if that variable is already set (just in case you really meant to set it to something else). As a debugging step, you can try setting the SSL_CERT_FILE to C:/opscode/chefdk/embedded/ssl/certs/cacert.pem and see if that fixes anything. That should not be necessary on a permanent basis, but it would be useful to know if that did anything to solve the problem.
It may also be useful to see if knife can connect to supermarket via ssl. You can run knife ssl check https://supermarket.getchef.com and see if it verifies the certificate or not.
HTH

Thank you for you response and here is a answer to your questions:

The openssl.rb file indeed ends with the ssl_env_hack. These are the last few lines of openssl.rb:
require 'openssl.so'
require 'openssl/bn'
require 'openssl/cipher'
require 'openssl/config'
require 'openssl/digest'
require 'openssl/x509'
require 'openssl/ssl'
require 'ssl_env_hack'

I did have the SSL_CERT_FILE set... I had done this because of previous trouble with Ruby gem installations for Ruby 2.1. For chef purposes I have set the embedded Ruby 2.0 as my active ruby version after which I also changed the SSL variable to: C:\opscode\chefdk\embedded\ssl\certs
Important difference, without the carcert.pem actually... WITH the cacert.pem it worked! :+1:
I will just set the Cert variable to empty again and try that later.

The 'knife ssl check https://supermarket.getchef.com' command didn't do anything for me. It just opens the knife file in my editor and that's it.

So basically as far as I can see now It is important to Empty the SSL_CERT_FILE variable OR set to point towards the document you want and not just the location. If I find out more I will let you know.
Thanks for the help!

You need to set SSL_CERT_FILE to the full path to the cacert.pem file, e.g., C:/opscode/chefdk/embedded/ssl/certs/cacert.pem The simplest thing to do is just unset this variable, and then anything using the ChefDK embedded ruby should work. However, if you want to use this CA cert file with other ruby installations, then setting SSL_CERT_FILE would be a good way to configure all of them.
I'm going to close this since it looks like a config issue, but if you still have trouble after unsetting SSL_CERT_FILE (or setting it to the full path), I'll reopen this.


Add new dependencies

In commit https://github.com/LibrePhotos/librephotos-docker/commit/176cd88c96e1588c5704c04a6cb4b66991293e3e
we added a couple of new dependencies. These should be added to the install scripts.

@tomamplius

@derneuere tkx


Unflake Retry Test

Coverage increased (+0.4%) to 69.307% when pulling e310dd29add8759803e3ccd0c70030af8d4653ee on unflake-rety into 7fefaf4b9368b91799e3974798a9c55388722d42 on main.

Coverage increased (+0.4%) to 69.307% when pulling e310dd29add8759803e3ccd0c70030af8d4653ee on unflake-rety into 7fefaf4b9368b91799e3974798a9c55388722d42 on main.

Coverage increased (+0.4%) to 69.307% when pulling e310dd29add8759803e3ccd0c70030af8d4653ee on unflake-rety into 7fefaf4b9368b91799e3974798a9c55388722d42 on main.


Importing using rocks

Still missing:

Tests
Progress update
Diff with previous commit (?)

Codecov Report

Merging #1133 (0970777) into master (542ae35) will decrease coverage by 0.33%.
The diff coverage is 2.06%.

@@            Coverage Diff             @@
##           master    #1133      +/-   ##
==========================================
- Coverage   47.30%   46.96%   -0.34%
==========================================
  Files         185      188       +3
  Lines       14464    14559      +95
==========================================
- Hits         6842     6838       -4
- Misses       6724     6821      +97
- Partials      898      900       +2

Impacted Files
Coverage Δ

catalog/rocks/cataloger.go
17.94% <0.00%> (-0.05%)
:arrow_down:

catalog/rocks/entry_catalog.go
21.42% <0.00%> (-0.64%)
:arrow_down:

catalog/rocks/entry_value_iterator.go
0.00% <0.00%> (ø)

graveler/committed/manager.go
0.00% <0.00%> (ø)

graveler/graveler.go
35.71% <0.00%> (-0.42%)
:arrow_down:

onboard/inventory_entry_iterator.go
0.00% <0.00%> (ø)

onboard/rocks_catalog_actions.go
0.00% <0.00%> (ø)

onboard/catalog_actions.go
69.66% <100.00%> (ø)

onboard/import.go
71.21% <100.00%> (ø)

catalog/mvcc/cataloger_create_entry.go
94.73% <0.00%> (-5.27%)
:arrow_down:

... and 4 more

Continue to review full report at Codecov.

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


Possibility to turn off or customize version/help option

It would be a good idea to make it possible to turn off (or at least customize) version and help options, probably via an attribute for the options class. This especially concerns version option - we are migrating from old custom parsers to the CommandLine library and we have noticed that it conflicts with our custom version option (-v, --version). This option is unrelated to version of an application, it concerns version of a file being processed by the executable. In our case it is not possible to use a different option name as we have to maintain 100% backward compatibility inside an enterprise system. Fortunately this "conflict" seems to be only visible in the help screen, when both our custom option and the default option are displayed at once.

This is a good idea. Right now both --help and --version are hardcoded into the application.

+1


Update Meta “authors”

Automatically generated by Netlify CMS

👷 Deploy Preview for serene-johnson-e50710 processing.
🔨 Explore the source changes: 6cb80035b1e770dee212fa6be1f0ff0051fa0066
🔍 Inspect the deploy log: https://app.netlify.com/sites/serene-johnson-e50710/deploys/61b01b33f3f8c8000835d16f


Fixes after brainstorming rules with TLs.

padded-blocks => Padded blocks seems fine since it prevents redundant empty space in beginning and end of each block. It is also auto-fixable. Any side effects you encountered with this rule? Indeed deprecated, on master is already replaced with stylistic corresponding rule.
func-style => Why would you use function at all nowadays? With variable as arrow function you can make it readonly and code is more encapsulated. I think people should actually learn to code that way the same way we're not using public setters anymore in C#. Why would you use function before defining it in typescript? Aren't we using typescript to normalize this quirky behaviour of JS?
@typescript-eslint/no-unused-vars => we can decrease severity of this to warning so you can develop without blockages, but you should still fix this before pushing final solution. It's rightfully one of eslint recommended rules turned on by default.
@typescript-eslint/no-magic-numbers => I feel pain regarding this I'm not against it, but we can perhaps keep it by loosening it by allowing hard-coded ArrayIndexes, default values of objects, initial class field values (options were added later)?
@typescript-eslint/no-non-null-assertion => I think form.get('name') falls into 5% category we'd like to ignore. This rule helped us a lot in past to spot holes in our nswag-generated API related code + is forcing us (not) to have guards. Any other problematic and realistic example that is causing you pain you'd like to share with us?
@typescript-eslint/space-before-function-paren => I think this shouldn't be changed since it's how community expects function to look like + it's autofixed.
unused-imports/no-unused-imports => similar as for no-unused-vars (decrease severity to warning). Take into account we'll put treshold of X warnings after which build's gonna be red.
no-negated-condition => legit comment, but is it the case in more than 5% of cases?
no-warning-comments => this has warning severity, so it doesn't break builds nor blocks anyone. Totally fine to add TODOs to code base, but if you have hundreds of them in your code base (seen cases), something's gotta give. We can talk about treshold value, but this reminds us to address them and treshold reminds us that if they pile up we gotta do something about them for real.
no-loops => get this part, but should we left warning for people to actually learn something and reconsider using linq?


Add excluded regions and EC2 filtering

Add two new options to specify excluded regions for AWS integration and tags to filter out EC2 instances.

doned, @houqp

ping @houqp

Thanks @Art3mK !


python solution

Solved issue #698
In Language- Python

[x] Updated README Link
[x] Added code with comments

Thanks for contributing!

Resolve conflicts

Resolve conflicts

Done.

Done.


Fix #4834 Core Lightning Peercount

fixes #4834 - @openoms please test with a CLN node having channels
TODO: Merge into v1.11 as a hotpatch & then also cherry-pick over into dev

Tested with mainnet and signet CLN. The status values appear correctly.

cherry-picked to dev


[Fix #12931] Fix false positives for Style/RedundantLineContinuation

Fixes #12931.
This PR fixes false positives for Style/RedundantLineContinuation when line continuations involve break, next, or yield with a return value.

Before submitting the PR make sure the following are checked:

[x] The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
[x] Wrote good commit messages.
[x] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[x] Added tests.
[x] Ran bundle exec rake default. It executes all tests and runs RuboCop on its own code.
[x] Added an entry (file) to the changelog folder named {change_type}_{change_description}.md if the new code introduces user-observable changes. See changelog entry format for details.

Thanks!


Feature Request: Querying for sub relationships on related data

As an example let's say I have comments, posts, and users.
Say I want to get all posts, by a given user and the comments on those posts. In my proposal a url like the following would be called:
https://example.com/users/USER_ID?$populate=post&$populate=post__comment
This URL would return a body that is similar to the following:
{
    "meta":  "", // stuff
    "user": {
        "id": 124,
        "name": "May Name",
        "posts": [
            {
                "id": "postID",
                "title": "postTitle",
                "body": "Long post test",
                "comments": [
                    {
                        "createdBy": 3294,
                        "commment": "Some comment"
                    },
                    {
                        "createdBy": 43434,
                        "commment": "Some comment 2"
                    },
                    {
                        "createdBy": 1454,
                        "commment": "Some comment 3"
                    },
                    {
                        "createdBy": 32435594,
                        "commment": "Some comment 4"
                    }
                ]
            },
            {}, // Post 2 + comments
            {} // Post 3 + comments
        ]
    }
}

I have a simple implementation currently occurring that passes the Sequelize include.  That code looks like this:
// Helper function for knowing if we need to get a models or an otherModels
// Allows for more than one set of models to be defined and used for querying
// NOTE: the related models must be in the same database, otherwise the related
// query will break
function getSourceModel(application, modelName) {
    const sourceOne = application.get('models');
    const sourceTwo = application.get('otherModels');

    if (sourceOne[modelName]) {
        return {
            model: sourceOne[modelName],
        };
    } else if (sourceTwo[modelName]) {
        return {
            model: sourceTwo[modelName],
        };
    }
    return null;
}

// Setup global hooks for all services
app.hooks({
    // This hook allows for adding related results to an API call.
    // Allows for one level to two levels deep.
    before(hook) {
        // Setup related query calls. This allows us to pass a
        // $populate=modelName to fill out related models in a query.
        // https://github.com/feathersjs/feathers-sequelize/issues/89 <-- this helped me figure it out
        if (hook.params.query && hook.params.query.$populate) {
            const populateParam = hook.params.query.$populate;
            const includeObject = { include: [] }; // Contains objects used for querying sequelize
            const includeTables = {};
            const subTables = {};

            if (Array.isArray(populateParam)) {
                populateParam.forEach((param) => {
                    // Logic here for supporting nested param queries.
                    // e.g. myRelation__subRelation
                    const paramSplit = param.split('__');

                    if (paramSplit.length === 1) {
                        includeTables[param] = getSourceModel(hook.app, paramSplit[0]);
                    } else {
                        const existingSubTable = subTables[paramSplit[0]];
                        if (existingSubTable) {
                            existingSubTable.push(paramSplit);
                        } else {
                            subTables[paramSplit[0]] = [paramSplit];
                        }
                    }
                });
            } else {
                includeTables[populateParam] = getSourceModel(hook.app, populateParam);
            }

            // Add the sub tables to their include tables
            // Only supports one layer deep. This is on purpose. We do not want
            // very deeply nested query calls available to the API.
            Object.keys(subTables).forEach((key) => {
                const table = includeTables[key];

                // If the main table is not there we cannot get the sub table relationship
                if (!table) {
                    return;
                }

                subTables[key].forEach((subTableGroup) => {
                    subTableGroup.forEach((subTable) => {
                        // Don't try to include the original table.
                        if (subTable === key) {
                            return;
                        }

                        if (table.include) {
                            table.include.push(getSourceModel(hook.app, subTable));
                        } else {
                            table.include = [getSourceModel(hook.app, subTable)];
                        }
                    });
                });
            });

            // Go over the existing setup tables and include each "table object".
            // The objects getting added look like:
            //
            // [{
            //    tableName: {
            //          model: tableName,
            //          include: [tableNameOther1, tableNameOther2]
            //        }
            //    }, {
            //    tableName2: {
            //          model: tableName2
            //        }
            //    }
            // ]
            Object.keys(includeTables).forEach((key) => {
                includeObject.include.push(includeTables[key]);
            });

            if (hook.params.sequelize) {
                Object.assign(hook.params.sequelize, includeObject);
            } else {
                Object.assign(hook.params, {
                    sequelize: includeObject
                });
            }

            /* eslint-disable no-param-reassign */
            // get() will interpret $populate as a column if we do not remove.
            delete hook.params.query.$populate;
            /* eslint-enable no-param-reassign */
            return hook;
        }
        return hook;
    }
});

Does this seem like a feature that feathers would want? It's been very useful for us, we currently have an Ember frontend, and having these nested relationship gets has made it much easier to implement.
As a further note, in our applications we put the service as raw: false for all of them. It allows the nesting returns to be more easily understood on the frontend.

I use the sequelize specific include param for my pg models and  $populate param for mongoose models. They all seem to work fine for me.
An example of a inclusion hook
const inclusions = () => ctx => ({
  ...ctx,
  params: {
    ...ctx.params,
    sequelize: {
      include: [
        {
          model: db.role,
          attributes: ['id', 'name'],
          include: [
            {
              model: db.permission,
              through: { attributes: [] },
              attributes: ['type', 'id']
            }
          ]
        }
      ]
    }
  }
});

this.service('db/users').hooks({
  before: {
    all: [inclusions()]
  }
});

https://docs.feathersjs.com/api/databases/sequelize.html#paramssequelize
Similarly for mongoose it (params) would look something like:
{
  $populate: ['user'] // lets say I want to get the user of a task (which already has a ref field)
}

https://docs.feathersjs.com/api/databases/mongoose.html#populate
Would this be helpful to you?

Thanks for responding @zusamann.  I'll get straight to my thoughts to your main question.

Would this be helpful to you?

The code is currently using the hook.params.sequelize to fill out the query parameters for model relationships. Which in turn creates the sql query to get all the data our frontend needs. It allows for nesting of data and relationships in a dynamic fashion. (e.g. I can get a user, all the posts made by that user, and the comments on those posts).
The main piece I want to work is querying via the API. I don't want to have to write code for each specific relationship, whenever the relationships are already defined in sequelize.
As mentioned this is the sort of API call I want to get the data https://example.com/users/USER_ID?$populate=post&$populate=post__comment and I want that to work for any relationship that's properly defined in sequelize.
I know there are other considerations to take into account with Mongo as a possible backend. My main focus is sql, because that is the data store I primarily use.
I appreciate the help and feedback!

Referencing this is https://github.com/feathers-plus/feathers-hooks-common/issues/347 in order to consolidate these related issues.


Unable to change the domain when a user is authenticated by SAML

ISSUE TYPE
BUG
COMPONENT NAME
Component:  Bug
CLOUDSTACK VERSION
Cloudstack version <IP_ADDRESS>, <IP_ADDRESS>
SUMMARY
Unable to change the domain when a user is authenticated by SAML
Steps to reproduce the issue
On <IP_ADDRESS>  environment

Enable SAML authentication
Create 2 domains (domain 1 and domain 2)
Create Account in each domain and authorize Saml

Login as single sign-on

Change the domain

Exception message

Video recording
https://www.loom.com/share/7dd809008a7649e7907bdf10c56af185?sid=86038cae-f441-4d8f-b76a-0db59486bf0b

Followed, the same steps on <IP_ADDRESS> and found  no issue on <IP_ADDRESS>
Video recording
https://www.loom.com/share/6cc8b0625c324976b338965ae679ae26?sid=01b0d96e-5b6d-4d77-bacd-e81c62e66610
Expected Behaviour
Cloudstack saml configured users should be able to change the domain
Actual Behaviour
Cloudstack saml configured users are not able to change the domain

this seems to be regression of security bug fixes in
https://cloudstack.apache.org/blog/security-release-advisory-<IP_ADDRESS>-<IP_ADDRESS>
there are two related fixes
CVE-2024-45462: Incomplete session invalidation on web interface logout
CVE-2024-45693: Request origin validation bypass makes account takeover possible

Thanks @weizhouapache  Saml authenticatied users can change the domain till the <IP_ADDRESS> release.
The issue is occurring from the  <IP_ADDRESS> release

@kiranchavala
thanks
can you change global setting api.sessionkey.check.locations to CookieOrParameter, and retry ?

@weizhouapache Getting the same error even after changing the api.sessionkey.check.locations to CookieOrParameter

@weizhouapache @kiranchavala , I set this to 4.20.1 but am having second thoughts. should (and can!) we move this forward or is it too complicated to solve?

@weizhouapache @kiranchavala , I set this to 4.20.1 but am having second thoughts. should (and can!) we move this forward or is it too complicated to solve?

@DaanHoogland
I have not looked into this issue yet, so no idea what's the root cause and how to fix it
IMHO, the fix could be very simple.
@kiranchavala
can SAML user log in with specific domain ? (not switch/change domain)

@weizhouapache
Currently, there is no option to select a specific domain to during login  for saml

Once logged in user's get the option to switch to a specific  domain

@weizhouapache
Currently, there is no option to select a specific domain to during login for saml

Once logged in user's get the option to switch to a specific domain

thanks @kiranchavala
then this becomes a critical issue for SAML users who has accounts in multiple domains.

clear, thanks @weizhouapache @kiranchavala

clear, thanks @weizhouapache @kiranchavala

I will have a look @DaanHoogland @kiranchavala

fixed by #10047


Resolutions

It's possible to shink the screen size to a point where various key elements aren't visible on mobile (in particular the speed selector)

This is an odd one, the design is set with min-width on container elements which I believe should stop the browser from collapsing too far (and if it does, applying a scrollbar) this doesn't seem to work though even in a really simply example: https://jsbin.com/nuzemogaxa/edit?html,css,output


Update keycloak realm token times (5 hours => 15min, etc)

We need to tweak the token timeouts as they are far too large (hours instead of minutes) on various items.

@JLWade FYI.

Tested on PROD: Pending

Looks like some session tokens are still set to hours/days instead of minutes. @marklise , could you please check this again? Thanks!

Confirmed with @marklise, that only the client session idle/max/token lifespan has to be set to minutes. Therefore passing this ticket to Done.
FYI @JLWade


added test for getEffectStyles

Pull Request Test Coverage Report for Build 378725446

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+1.2%) to 43.574%

Totals

Change from base Build 378458884:
1.2%

Covered Lines:
127

Relevant Lines:
314

💛  - Coveralls


Handle errors in the send_test_email and send_campaign actions

The save_campaign action wraps its call to the campaign backend in a try/except block, and it reports a user-friendly error if the call fails.
https://github.com/wagtail/wagtail-newsletter/blob/db88d1a934d8923879043f8b2b0a8b3bcc193255/wagtail_newsletter/actions.py#L17-L27
The send_test_email and send_campaign actions should do the same.

Fixed in #65.


looks like that it is some problem with UnicodeDecodeError,i'm completely unfamiliar with it

PS D:\test\mine\Voyager> pip install -e .
Looking in indexes: https://mirrors.aliyun.com/pypi/simple/
Obtaining file:///D:/test/mine/Voyager
Preparing metadata (setup.py) ... error
error: subprocess-exited-with-error
× python setup.py egg_info did not run successfully.
│ exit code: 1
╰─> [8 lines of output]
Traceback (most recent call last):
File "", line 2, in
File "", line 34, in
File "D:\test\mine\Voyager\setup.py", line 38, in
long_description=_read_file("README.md"),
File "D:\test\mine\Voyager\setup.py", line 16, in _read_file
return fp.read()
UnicodeDecodeError: 'gbk' codec can't decode byte 0xa5 in position 2098: illegal multibyte sequence
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed
× Encountered error while generating package metadata.
╰─> See above for output.
note: This is an issue with the package mentioned above, not pip.
hint: See above for details.

Try using a different codec to decode the file. For example, you can try using the 'utf-8' codec instead of 'gbk'.
Check if the file contains non-ASCII characters and remove them if possible.
Try upgrading pip to the latest version using the command python -m pip install --upgrade pip.
Try installing the package using a different version of Python or a different operating system.
Here's an example of how to use the 'utf-8' codec to decode the file in the setup.py script:
python
def _read_file(filename):
    with open(filename, 'r', encoding='utf-8') as fp:
        return fp.read()

This code replaces the 'gbk' codec with the 'utf-8' codec to decode the file.
If none of the above solutions work, you can try searching for the error message on the internet to see if others have encountered the same issue and found a solution. Some of the search results may provide additional information or insights on how to fix the error.```
it looks like you are using a non standard terminal. beyond that, it is hard to say without further OS details

Try to change .open() in line 15 and 20 in setup.py to .open(encoding='utf-8'), and everywhere else you find similar.

The issue will be closed due to a lack of activity, feel free to reopen it if you would like to continue the discussion.


Miscellaneous improvements to FossID logging and issue handling

Please have a look at the individual commit messages for the details.

FYI @hanna-modica.

You could even improve it by passing a second package to the scanner and verify that it gets processed after the error with the unsupported VCS is handled.

I'll do this in a follow-up.


Batched pack/unpack params before/after allreduce

This PR aims to improve performance of multi-nodes training by reducing number of GPU kernel launched for packing/unpacking parameter gradients before/after allreduce communication among nodes. You can use this feature by just adding a argument batched_pack_unpack=True to create_communicator like below.
comm =  chainermn.create_communicator('pure_nccl', batched_pack_unpack=True)

In addition, this also supports mixed data type of parameters (only fp16 and fp32 for now). When dtype of a parameter and dtype for allreduce are different, the dtype of parameter is automatically converted to/from allreduce dtype by GPU kernel for packing/unpacking only when needed. (this is related to #5732).
Note that this feature is only available with 'pure_nccl' communicator for now.

Thank you! How fast will ChainerMN be by this PR?

How fast will ChainerMN be by this PR?

It depends on training configuration, and this feature will be effective when local batch size is small or a network/model has lots of layers, in other word, CPU is performance limiter. For your reference, performance when training resnet50 with local batch size of 32 was as follows.
[ performance (iterations/sec) ]
16.98  (w/o this feature)
17.54  (with this feature)
[ testing configs ]
GPU: 2x Tesla V100
Model: Resnet50
Dtype: FP16
Autotune: Enabled
Local batch size: 32
IO pipeline: DALI is used
Convolution: NHWC format is used
Batch normalization: NHWC format is used

Thank you for your feedback. I've fixed the branch based on your feedback. Could you check it again?

Thank you for updating the patch. I and @shu65 discussed on this a bit, and it's almost OK, but still one thing we need further discussion on supporting float64. We tend to not to support float64, but where to put numpy type check. Inserting it as else clause inside cuda kernel, but it'll have issue on how to pass error from cuda to Python. It might be good to add type check before entering into cuda kernel, right before packing. Do you have any good idea?

Regarding type checks, how about doing that in __init__ of _ParamsData? Then, you can do that with small overheads.

I've added type checks in object _ParamData, and also fixed some issues in GPU kernels for unpacking parameters and tests for batched_copy. Could you check it again?

The code looks good, but we need a bit more time to test this.


Change wait() docs

"the queue will actually be empty." should be "the queue has an available slot"

1.1.3


This works, but it isn't perfect

I'm kinda disappointed that these header errors keep coming up.
But hey, you did ask for it.

@pitaj Can you re-submit this as just your own changes? I've merged #17 in on its own, and I don't quite know what you fixed in this PR :smile:

It fixes the problem where you can't go back the the homepage without going to /home

But I guess I'll redo it

Thanks @pitaj :D
On Mon, 1 Jun 2015 16:29 Peter Jaszkowiak<EMAIL_ADDRESS>wrote:

But I guess I'll redo it
—
Reply to this email directly or view it on GitHub
https://github.com/NodeBB/nodebb-plugin-custom-homepage/pull/18#issuecomment-107697546
.

New PR #19


Fix validation preventing use of --svt args starting with "-i"

Fix validation preventing use of --svt args starting with "-i", e.g. "-irefresh-type".

Thanks, yeah I think the anti -i & -b validation there is no longer necessary after we stopped invoking svt-av1 directly


Highlighted text is hard to read on selection in the outline/breadcrumb views

Because both colors are blue they become hard to read and fail the color contrast ratio. Would expect for the highlighted text in these selected states to become white.
Outline

Current
Expected

Breadcrumb

Current
Expected

cc @jrieken @bpasero

@misolori can you also attach the look for quick open after this change? and would this change be for the light theme only or all themes?

@bpasero I can't find an example that uses selection for quick open, do you know of one? And this change would be the new default for the breadcrumb/outline view, so it would affect all themes that use the "light theme" defaults in those two views. It's currently broken and was hard to see in our previous color as well:

@misolori yeah, none of the pickers use selection color, I was more referring to how quick open would look like if you change highlight color to white. My understanding is that this would have an impact pretty much everywhere where highlighting is being used (independent from the tree or not)

so it would affect all themes that use the "light theme"

To clarify: this would affect all light themes, even the ones in the market place? or only our light theme

@bpasero sorry if I wasn't clear, my intention is to only change the highlight color when it's on a selection row. So I'm not intending to change the default highlight color. In the example below, the highlight color remains the same except when it's selected:

I still need to investigate how to do this, but my suspicion is that we already make the text lighter on a selected row, so I'd explore doing something like color: inherit !important while it's selected.

To clarify: this would affect all light themes, even the ones in the market place? or only our light theme

yes, this would affect all light themes.

@misolori but there is only list.highlightForeground, we do not distinguish the highlight color based on the type of selection currently.

@bpasero hmmm...let me do some investigation to figure this one out.

we do not distinguish the highlight color based on the type of selection currently.

I think the point is the we don't have (and want) a highlighted-and-selected-foregournd-color but that the selection color always wins.

The highlight color on the dark theme also fails the color contrast ratio (3.2:1):


Updated several reg tests.

This is a merge of multiple previously separate commits, essentially just updating several regression tests.  I will make a separate PR to update run-test.perl

LGTM


provision to add event logo

Top left, beside the event name.

Isnt this same as https://github.com/fossasia/open-event-orga-server/issues/98 ?

@championswimmer Hi! Is this issue fixed? I would like to work towards solving this! :)

This is, for now, done


Improve the public C API

I'd like to see a few additional functions in the public C API:

[ ] Support passing everything that can be set in YAML from code

[ ] a way to define complex types using the public C API
[ ] a new PDI_typed_share() function that takes a type in addition to the data

[ ] Add new features for sharing

[ ] functions to change the lock level of some already shared data

In GitLab by @ksiero on Oct 18, 2019, 13:28
What is the reason for sharing function pointers?
This can be done by passing a pointer to function pointer. Please see: https://wandbox.org/permlink/Ww6m0L8mKuOBYa9h
Is this related with some other feature?

Also see #76

unassigned @ksiero

Also see #35

Yes, but we currently don't support function pointer in Datatype

marked the checklist item a way to define complex types in the YAML and reference them later as completed


chore(package): update dependencies

Coverage decreased (-75.8%) to 21.212% when pulling 52c1a7503ab614e9c057c736a458ab45746e0fa5 on greenkeeper/initial into 4fa5074d1efdf58ed5d906db2626b2019d660c4c on master.


i18n(fr): Update guides/upgrade-to/v5.mdx from #10543

Description (required)
Update guides/upgrade-to/v5.mdx from #10543

Related issues & labels (optional)

Suggested label: i18n

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

File
Note

fr/guides/upgrade-to/v5.mdx
Localization changed, will be marked as complete.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.


MT4 'cannot open file' error with DWX_ZeroMQ_Server_v2.0.1_RC8.mq4

Hi. I just copied the DWX_ZeroMQ_Server_v2.0.1_RC8.mq4 into my Experts folder as instructed but the MT4 wont open the EA and keeps shouting the error 'cannot open file +(path to said file)' in the Experts logs.
I'm not sure what I did wrong. Can someone help?

Hi @gitobu56 ,
This appears to be an issue related to how you've possibly installed the project.. let's dig deeper.
Please reply with the following:

Your Expert logs

Confirmation that you've got the latest code in this repository, and have followed the README instructions (very important to follow everything in there to ensure correct functionality).

Hope this helps.

Thanks. Finally got it to work. I had failed to compile it in the Meta editor.Please include the instruction "Click compile button " for newer users.
kind regards


Unable to install on  macosx

The javacpp-presets is not installing cleanly on os/x.  This is  a prerequisite for using SparkNet on mac.
The page https://github.com/amplab/SparkNet/blob/master/doc/creating-jars.md  is for ubuntu and centos only.
The following page is apparently the one to follow:
https://github.com/bytedeco/javacpp-presets/wiki/Build-Environments
However the command
bash cppbuild.sh install
ended up with a tar corruption error after an hour of compilation.
So if anyone successfully builds on os/x it would be appreciated to update the above documentation.

fyi I have narrowed down the javacpp-presets build issue to a corrupted version of libpng-1.6.17.tar.gz.
I downloaded the file manually from http://pkgs.fedoraproject.org/repo/pkgs/libpng/libpng-1.6.17.tar.gz  and am now re-running
bash cppbuild.sh install
Let us see whether this allows further progress.

The installation is challenging. I need to troubleshoot missing files . e.g.
p>The requested URL /project/boost/boost/1.57.0/boost_1_57_0.tar.gz was not found on this server.
So then the solution is to find the file manually.

Did it end up working for you? There is now a new release of JavaCPP, if we switch to that it should also fix your problem!

The earlier javacpp version used by SparkNet no longer can be built. So if SparkNet has migrated/upgraded that would be good news.  I will pull latest from trunk and see what happens.


Alt+Shifts opens upper menu but we use that shortcut to switch languages.

Operating System:

[ ] Windows
[x] Linux/Ubutnu - Mint 18.3
[ ] macOS

Clear steps to reproduce the issue:
1.Run application
2.Choose any chat or stream by clicking on it
3.Put cursor to message entry window
4.Press Alt+Shift
Relevant error messages and/or screenshots:

Input language switch expected, but File menu opened and there is no ability to continue typing message. It could be very useful to disable Zulip Alt+Shift keyboard shortcut.

Hi @winmasta I couldn't reproduce this on Ubuntu 16.04. Zulip doesn't specifically use Alt+Shift to open File Menu i.e. this is not a Zulip level shortcut. I'd assume this is something Mint does by itself. I am not sure if we can explicitly stop this.

I have checked all OS shortcuts and didn't find Alt+Shift, moreover I am using Mint for more than 5 years already and never faced with such problem, moreover it affects only Zulip app.

@winmasta I can successfully switch the language using the Alt+Shift key combination on Ubuntu 16.04. You may find that shortcut in keyboard setting, please see. Also, can you switch language using the same shortcut in other apps?

@akashnimare Yes I can switch the language anywere but Zulip app. Trying to switch language in Zulip app leads to throwing down upper menu of the app.

Okay. This looks like an upstream issue and for some reason, it doesn't work in the mint os. I'll file an issue there and will look for the potential solution.

Thanks.

I'm using Linux Mint 18.3 and Zulib desktop, and I have the same problem.

@akashnimare yes, I'm ready to debugging

Okay, thanks. Are you using the .deb installer?

Yes, I am

@baumnkz I have published a new beta release for Linux - v2.3.8-beta. You need to run the following in order to get it (you might need to uninstall the stable version first) -
https://zulipchat.com/help/desktop-app-install-guide#linux-with-apt-ubuntu-or-debian-8

still problem

@akashnimare Great! But now one of menu item is hiding - help menu is not visible
When I press Alt+Shift now opened non-labeled menu:

@baumnkz just fixed it. Can you update and check if it works as expected?

Awesome, thanks for the help ❤


Why does substitution need to initialize the thread pool

In line 95 of the SqlParseUtils file, why are eight threads initialized to handle variable issues? Won't it cause a waste of resources? After all, variable problems are fast to calculate.

Normally, we can't estimate the number of variables, but now it seems that 8 threads are a bit big.


Fix IndexOutOfRangeException if a chromatogram has zero points in it

This bug was introduced as part of the "Spectrum Filter" checkin.
There has not yet been a Skyline-daily released with this bug in it.

Cherry pick action hadn't been updated yet. Now it is.


🐛 Fix npm publish step

Adds the npm registry as described in https://docs.github.com/en/actions/publishing-packages/publishing-nodejs-packages#publishing-packages-to-the-npm-registry

Note: I don't have permission to change allowed actions here so hopefully the v2 actions are good enough


Allow to configure environment variables for apt-get update command.

Hello all,
We are using custom APT transport for an internal mirror.
However our transport is configurable via environment variables.
In current state no ENV vars are available for update command.
This PR introduce argument option $::apt::update['environment'] to configure required ENV variables for APT update command.
BR

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Adrian Eib seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

I found workaround by editing /etc/default/puppet systemd environment file.

I will keep it open as it still can be use-full in some cases.

Any good soul who can take a look on this simple PR ?

Hey @findmyname666 , thank you!
Can you add a spec test to account for this new parameter?

Hi @findmyname666 - just hoping to check if there has been any progress on adding a spec test for this new functionality? Additionally, there are some conflicts that will need resolved. Thanks :-)

Hi @findmyname666!
We are reviewing some of our ageing PRs, and as there has been no movement on this since August 16th, it's suggested that we close this request.
If you have the time to pick this back up again in the near future and address the comments above - please do re-open this PR! (Or create a new one)
Thanks for all your work on this!


Add support for Mixed Instance Spot Policy Autoscaling.

Does as the label says; adds an example using it which I used to test that it works as expected.
The "make && make init" keeps trying to install and setup terraform 0.11 which is mildly infuriating.
Hacked around it; added a git attributes file as well as I doubt you want my windows crlfs in there 😉

@osterman could you have a poke 😉

I'd also pull out the type as per https://github.com/cloudposse/terraform-aws-ec2-autoscale-group/issues/18 but that can be a separate pr if needed

If this is unwanted let me know and I'll close it 🤷♂

@ChrisMcKee thank you for your contribution
could you please address some fixes:

remove .editorconfig file
remove update files with linux EOL if needed and remove .gitattributes file

@maximmi as https://github.com/cloudposse/terraform-aws-ec2-autoscale-group/pull/19 came after this PR and has been merged it appears to be trying to achieve the same thing?
You should have gitattributes files; I may not be the right person to be adding them but in general unless you want mixed line endings between platforms.


Docs: best practices: timestamp in private

Best practice docs for timestamps in private functions
Generic oracle -> validate in public

Consider a general purpose contract that stores a timestamp as a shared mutable for access from private while updating in public by anyone


GitHub action for rebuilding cache

Rebuilding the cache is more painful than needed, especially for new contributors, see e.g. https://github.com/CarloLucibello/GraphNeuralNetworks.jl/pull/253
First of all, you have to know you have to rebuild the cache, then you have to install the exact julia version used for the cache (also the patch number matters) and finally do the rebuild.
I was wondering if there is some way to configure a github action to do the whole thing, i.e. check for changes in the cache and do the rebuild only if there are any.

It's a bit unclear what exactly is the issue here. Do I understand correctly that a GitHub Actions Cache support is requested?


fix: f-client-nav={false} not working inside island

Fixes https://github.com/denoland/fresh/issues/2658

Thanks a lot Marvin! It can't be easy finding time for these at the moment


Missing rand procedure for MvNormalMeanScalePrecision

Following the discussion, we have found that sampling from MvNormalMeanScalePrecision is not implemented, i.e.
julia> dist = MvNormalMeanScalePrecision(zeros(2), 2.0)
MvNormalMeanScalePrecision{Float64, Vector{Float64}}(μ=[0.0, 0.0], γ=2.0)

julia> rand(dist)
ERROR: MethodError: no method matching length(::MvNormalMeanScalePrecision{Float64, Vector{Float64}})

Maybe we should move this distribution in ExponentialFamily.jl?


decoratorMetadataEmit not compatible with Babel's 6-to-5

I believe it's expected that tsc -t es6 should be externally transpilable to ES5 (eg with Babel)
See https://gist.github.com/alexeagle/24243fbb87dbd8bad6f1
Babel replaces the __decorate line this.__decorate with undefined.__decorate so that gives a runtime error. Uncaught TypeError: Cannot read property '__decorate' of undefined   app_bin.js:7
Note I also tried this with Closure Compiler ES6->ES5, and had a different problem because of this line in the emit:
Object.defineProperty(App, "name", { value: "App", configurable: true });
in ES6 spec, new objects are configurable:true by default, but in mainline Chrome it is configurable:false by default so this is also a runtime error. For this case, it leads me to wonder if ES5->ES6 transpilers should be expected to translate API incompatibilities in addition to new ES6 syntax.

I believe the core of the issue is that the emit for this.__decorate is incompatible with ES6 module semantics (i.e. use of this). this is the same issue as #2811.
I do not have enough context for Object.defineProperty(App, "name", { value: "App", configurable: true }); can you elaborate.

In current chrome, here is an interactive session:

var f = function(){}
undefined
Object.getOwnPropertyDescriptor(f, "name");
Object {value: "", writable: false, enumerable: false, configurable: false}
Object.defineProperty(f, "name", {value: "name", configurable: true});
VM583:2 Uncaught TypeError: Cannot redefine property: name

@mhegazy, we have to manually assign the name of the class that has decorators due to the double-bind issue with class declarations. The problem is that the "name" property of Function has [[Configurable]]: true in ES6, but has [[Configurable]]: false in ES5 Chrome, as well as non-strict contexts in Chrome Canary with ES6 features enabled.
@alexeagle Given Chrome's update cycle, how likely would it be that they make Function#name configurable by default before ES6 support ships?

I have no idea. But for my part, as long as this is an isolated problem
with external tools doing the 6-to-5 lowering, this is a low priority issue
and can wait for at least a few weeks.
On Mon, Apr 20, 2015 at 3:16 PM Ron Buckton<EMAIL_ADDRESS>wrote:

@mhegazy https://github.com/mhegazy, we have to manually assign the
name of the class that has decorators due to the double-bind issue with
class declarations. The problem is that the "name" property of Function has
[[Configurable]]: true in ES6, but has [[Configurable]]: false in ES5
Chrome, as well as non-strict contexts in Chrome Canary with ES6 features
enabled.
@alexeagle https://github.com/alexeagle Given Chrome's update cycle,
how likely would it be that they make Function#name configurable by default
before ES6 support ships?
—
Reply to this email directly or view it on GitHub
https://github.com/Microsoft/TypeScript/issues/2836#issuecomment-94581839
.

@alexeagle, I could change this from Object.defineProperty to Reflect.defineProperty, assuming the polyfill babel uses for its runtime includes Reflect.defineProperty (which I believe it does).
Reflect.defineProperty does not throw if the property has [[Configurable]]: false.

I don't think this would help us in Closure, their runtime polyfill seems
to just be a couple of function declarations.
Let's revisit if this doesn't make it into mainline Chrome soon.
On Tue, Apr 21, 2015 at 11:44 AM Ron Buckton<EMAIL_ADDRESS>wrote:

@alexeagle https://github.com/alexeagle, I could change this from
Object.defineProperty to Reflect.defineProperty, assuming the polyfill
babel uses for its runtime includes Reflect.defineProperty (which I
believe it does).
Reflect.defineProperty does not throw if the property has
[[Configurable]]: false.
—
Reply to this email directly or view it on GitHub
https://github.com/Microsoft/TypeScript/issues/2836#issuecomment-94900680
.

Fixed in #2897

FYI, I'm still seeing this on the 1.5 beta.

@jamiewinder can you provide more details?
this input:
function dec() { }

@dec
export class Foo {

}

on 1.5-beta gives me:
if (typeof __decorate !== "function") __decorate = function (decorators, target, key, desc) {
    if (typeof Reflect === "object" && typeof Reflect.decorate === "function") return Reflect.decorate(decorators, target, key, desc);
    switch (arguments.length) {
        case 2: return decorators.reduceRight(function(o, d) { return (d && d(o)) || o; }, target);
        case 3: return decorators.reduceRight(function(o, d) { return (d && d(target, key)), void 0; }, void 0);
        case 4: return decorators.reduceRight(function(o, d) { return (d && d(target, key, o)) || o; }, desc);
    }
};
function dec() { }
var Foo = (function () {
    function Foo() {
    }
    Foo = __decorate([
        dec
    ], Foo);
    return Foo;
})();

Here's a basic reproduction, which uses TypeScript 1.5-beta, ES6 output, Babel, and SystemJS together:
index.html
<script src="system.js"></script>
<script>
    System.transpiler = "babel";
    System.babelOptions = {
        modules: "system"
    };
    System.import("app");
</script>

app.ts
import { DecoratedClass } from './decoratedclass';

var dc = new DecoratedClass();
var dummy = dc.name;

DecoratedClass.ts
import { TestDecorator } from './testdecorator';

export class DecoratedClass {
    @TestDecorator()
    public get name(): string {
        return "This is a test";
    }
}

TestDecorator.ts
export function TestDecorator() {
    return (target: any, key: string, props: PropertyDescriptor) => {
        var getter = props.get;

        props.get = function () {
            var val = getter();
            console.log(val);
            return val;
        };
    };
}

The expected result is that the 'This is a test' is written to the console (by the decorator). If I build as ES5 using a CommonJS module system, then it does exactly that. However, if I build to ES6, then I get an error:
Potentially unhandled rejection [2] TypeError: Error evaluating decoratedclass
Cannot read property '__decorate' of undefined
    at execute (http://localhost:31818/decoratedclass.js!eval:15:35)

Let me know if you need more information.

@rbuckton looks like "use strict" issue

I don't think the original issue is fixed. It's still the case that es6 emit produces Object.defineProperty which only works in Chrome Canary, not Chrome.
We now need a proper fix as we are starting to use typescript to compile the decorator parts of Angular.
Maybe what @rbuckton suggested in https://github.com/Microsoft/TypeScript/issues/2836#issuecomment-94900680 ?


Consistent chronological order Issue in File Renaming

Describe the bug
I consistently face an issue where file renaming with counter (on_conflict: rename_new) results in an order that doesn't align with the original chronological sequence, but a random order, of the files.
Environment

OS: MacOs 14.1.1
Output of organize --version: organize v3.1.1

Your config file
The first rule involves resizing an image with the "_r" suffix, transferring metadata from the original file to the newly resized file, synchronizing the timestamp of the resized file with the original file's, moving the original file to the Trash, and ultimately removing the "_r" suffix from the preprocessed file, thereby replacing the original image with the resized version.
The second rule renames the preprocessed photos with year-month-day_counter and sorts them in date folders. Here the counter seems to be random.

# ----------------------------------------------------------------------------------|
  - name: "{IMAGES} {processing + moves to folder2}"
    locations:
      - path: '~/Pictures/album/folder1/'
    subfolders: false
    enabled: true
    filters:
      - extension:
          - jpg
          - png
          - jpeg
          - heic
    actions:
      - shell: |
          magick "{path}" -resize '1440x1440>' "{path.parent}/{path.stem}_r.{extension.lower()}"
          exiftool -tagsFromFile "{path}" "{path.parent}/{path.stem}_r.{extension.lower()}"
          touch -r "{path}" "{path.parent}/{path.stem}_r.{extension.lower()}"
          mv "{path.parent}/{path.stem}_r.{extension.lower()}_original" ~/.Trash
          mv "{path}" ~/.Trash
          mv "{path.parent}/{path.stem}_r.{extension.lower()}" "{path.parent}/{path.stem}.{extension.lower()}"
      - move:
          dest: "~/Pictures/album/folder2/"
          on_conflict: rename_new
          rename_template: "{name}_{counter}{extension}"
# ----------------------------------------------------------------------------------|
  - name: "{IMAGES} {renames & moves to specific date folder}"
    locations:
      - path: '~/Pictures/album/folder2/'
    subfolders: false
    enabled: true
    filters:
      - created
      - extension:
          - jpg
          - png
          - jpeg
          - heic
    actions:
      - move: # and rename
          dest: "~/Pictures/album/{created.strftime('%Y-%m-%d')}/{created.strftime('%Y-%m-%d')}.{extension.lower()}"
          on_conflict: rename_new
          rename_template: "{name}_{counter}{extension}"

Thanks for the detailed report. What do you mean by the counter being "random"? The files are handled in the order they are visited, which depends on the filesystem and is not always alphabetically correct.

Exactly. So for instance, my list of photos is this one:

Which after the processing gets converted into this:

However, the rearranged photos deviate from the original sequential (chronological) order. Consequently, when navigating through the converted photos, they exhibit time jumps, creating a rather frustrating browsing experience.
Is there a way to tell Organize to follow a strict handling order?

I see the problem. This should really be handled in alphabetical order. I'm on it.

I decided to use natsort for this, so the files are sorted just like in the system file explorer. The fix is already on the main branch and will be released soon. Thanks again for the issue!

Just released the fixed version in v3.2.1


Prove the correctness of a work-stealing deque

Rendered
Implementation
This is a linearization proof of the Chase-Lev work-stealing deque.  To the best of my knowledge, it is the first publicly available linearization proof (attempt) of the Chase-Lev deque :)

@jeehoonkang Any news on this issue? How's the review of this proof going?

Sorry for inactivity these days.  My colleage and I are working on a different paper, so revising this proof had been postponed probably until mid July.  I guess the merge of this PR is not urgent, right?  I'll definitely come back and merge this PR :)

Just checking, take your time. :)


Updates to images and config maps for SSO and RBAC

I installed this operator in Openshift V4. However I don't see any place where I can see all configurations for updates. Somehow I could update operator yaml to update image paths because I want to use openshift registry for images. Instead of Openshift SSO, I want to enable GitHub SSO and I don't see any section for it ….rather I should say I am not sure where in the operator I should make these changes.
Any insight and docs update will be helpful.

@JTG2020 Take one of the examples and apply what you need. As documented all values from the Helm Chart work.
How to install Argo CD is documented for various Kubernetes Distributions here.
Hope this helps to get you up and running!

@disposab1e Thank you for your quick response. I could bring up ArgoCD using Operator because its already available in OpenShift Operators. I apologize in advance as this could be repeated question. Once operator is installed if I have to make changes to configs , do I have to apply configs separately  ex . I should run ocp.yaml (from examples )with required configurations after operator installation ? basically at what stage I should run ocp.yaml with config changes ? And also do I have to restart any pods ?

All operators work the same. They watch for custom resources and apply these resources to the cluster. When you apply ocp.yaml (after operator installation) the operator will install argocd with the settings from ocp.yaml. If you need to change settings after argocd installation, just change your ocp.yaml and apply it again. The operator will see the changes and will apply these changes to the cluster. When you remove ocp.yaml argocd will be removed from the cluster too.
When you intsall ocp.yaml (argocd) the first time you don't have to start/restart any pods. When you change some settings after installation in most cases there is no restart of any pods needed. But to get sure you can remove and add ocp.yaml. Your projects and apps are NOT deleted so you can simply remove and add with new settings.
Just give it a try and play a little. After operator installtion it's all about adding/changing/removing the custom resource e.g. ocp.yaml.
Hope this helps!

@disposab1e  I started playing around with ocp.yaml. I installed operator and did not create instance of ArgoCD from operator. Rather i modified ocp.yaml file to use specific images from OpenShift registry. Applied ocp.yaml and i don;t see any resources coming up i.e. i don;t see any pods, configmaps etc coming up in openshift. I am just seeing operator pod running in argocd project. Not sure what i am doing wrong or where to check for any errors. openshift events don;t have anything.

@JTG2020 Do you apply the Custom Resource (ocp.yaml) to the same namespace the operator is installed to?

yes i did make sure that i am running apply in same namespace. I do see operator pod running but none of the resources coming up.
However if i create ArgoCD instance from Operator, all goes well.

@disposab1e i did further digging on the issue and realized that existing groups did not clean up on deletion of operator which was causing issue with ocp.yaml file. After manually cleaning up groups, i could apply ocp.yaml successfully. Please ignore earlier message. Thanks for your time. I intend to play more with this file.

@disposab1e as i continue to do testing, I found one issue and am not sure if it is related to configuration but i want to mention it here. The Openshft SSO works fine however I am not getting any username when i sign in with SSO. We are using OKTA as identity provider in OpenShift. So basically users are first getting authenticated in OKTA and then callback happens to ArgoCD. I am not sure at what stage username is getting lost. Are there any additional configurations needed in dex when Openshift uses external idp.

@JTG2020 The dex implementation for OpenShift OAuth is from an RedHat engineer. He is aware that the user is not shown on the Argo CD Web UI but still exists :-) So this can be an dex problem or a problem from Argo CD working with dex. So not really a problem in functionality.

@disposab1e yes RedHat engineer fixed this issue. I used now updated image. However changes yet to be merged to upstream. I am hoping those changes will be made here as well. There is new images for dex.

@JTG2020 You can set: dex.image.tag in your CR to change it.


Switch from 4 x 1 to 2 x 2 for salespitch component when screensize is small enough

This should be 2 x 2 when screensize is small


platform testing

I was thinking about actually running the matrix tests on a pixhawk, snapdragon, etc. This ensures we don't hit compiler or other platform surprises.
Could we modify the existing matrix test so it continues to work standalone on travis-ci, but also could be built as a px4 module and in px4fmu-v2_test (https://github.com/PX4/Firmware/issues/4532). Alternatively we could just take a copy and hack them together into a test that lives in Firmware.

I pulled most of the matrix testing into PX4 tests here - https://github.com/PX4/Firmware/pull/4689
Some of the tests had to be stripped down to actually run on the pixhawk.


Enable container based builds

Speeds up our builds by a few minutes, and makes them start sooner.
http://blog.travis-ci.com/2014-12-17-faster-builds-with-container-based-infrastructure/
@maddalab @byxorna @defect @roymarantz

Wow. LGTM!


chore: docs syntax highlighting

Provides Syntax Highlighting for README.md

Hi @pschatzmann thanks so much for your efforts in building this library.
I saw many people had the Sketch too big issue before due to the small partition setting.
I was thinking that a picture like this in the README would call readers attention. What do you think?

I was also thinking that taking advantage of colored blocks like this:

[!WARNING]
Program memory is constrained by default. You must use a Huge App-like partition scheme.


test: enhance e2e debuggability by capturing resource changes and storing them as artifacts

Fixes #276
Modifications
To add to the controller artifacts that we currently have, it is also useful to track information of all the resources and their child resources. The best way to do this would be to store the output of kubectl get <resource> -o yaml anytime there is a change. We can achieve this by using a watch.Interface to watch each resource and generate an output file <resource>.yaml that continually receives the updated resource YAML every time a change occurs.
Verification
Ran make test-e2e locally to verify resource file are output correctly.
Verified artifacts are uploaded when test fails on Github CI.
Failed commit: https://github.com/numaproj/numaplane/pull/281/commits/218e6b4300be90cc53621e77563bd8de7079f2d9

Looks like we watch the entire resource Kind for each file generated. That seems fine. In the future, perhaps we will generate multiple files per resource name. But right now we don't have that need, since for these resources at least we only have one of each.

Looks like we watch the entire resource Kind for each file generated. That seems fine. In the future, perhaps we will generate multiple files per resource name. But right now we don't have that need, since for these resources at least we only have one of each.

Sounds good, this would be a pretty simple change when we need it: just adding the resource name as a parameter and using it in the label selector.


KS should not return all 0s if it gets an error fetching the source PDF

It should return no results, not 0s for all counties.
      const body = await fetch.pdf(this.url);
      if (body === null) {
        // throw new Error(`No data for ${date}`);
        return geography.addEmptyRegions([], this._counties, 'county');
      }

@paulboal ^^

Question @chunder - when there's no content, should the parser function just return []; or something else?  I'll get this fixed.

Good question. @lazd ?

Looks like this was already resolved.  This can be closed.

Sounds like this is related to #374, adding a note here.


not an issue but a how to: transparent background

Hi
I was going to suggest a transparent background but realised that if, in Settings / 3 vertical dots in the widget > Appearance > Colors section - Background colour >  you slide the top scroll bar to the right and the bottom scroll bar to the left, you can achieve gradient transparency.
NICE!
posting for those looking for the functionality

Please note that in version 3 (currently in Beta, see #320 ) we have another Color Picker in which making background transparent is much obvious to a User, I think :-)


IllegalStateException: released

java.lang.IllegalStateException: released
I'm getting this sporadically during long monkey test runs, we do lots of connection cancellation during these runs, so could be related to that maybe? Any insight into what might lead to this? The stack is entirely inside OkHttp code so not much to go on here.
// java.lang.IllegalStateException: released // 	at com.squareup.okhttp.internal.http.StreamAllocation.findConnection(StreamAllocation.java:142) // 	at com.squareup.okhttp.internal.http.StreamAllocation.findHealthyConnection(StreamAllocation.java:126) // 	at com.squareup.okhttp.internal.http.StreamAllocation.newStream(StreamAllocation.java:95) // 	at com.squareup.okhttp.internal.http.HttpEngine.connect(HttpEngine.java:283) // 	at com.squareup.okhttp.internal.http.HttpEngine.sendRequest(HttpEngine.java:224) // 	at com.squareup.okhttp.Call.getResponse(Call.java:286) // 	at com.squareup.okhttp.Call$ApplicationInterceptorChain.proceed(Call.java:243) // 	at com.squareup.okhttp.Call.getResponseWithInterceptorChain(Call.java:205) // 	at com.squareup.okhttp.Call.access$100(Call.java:35) // 	at com.squareup.okhttp.Call$AsyncCall.execute(Call.java:171) // 	at com.squareup.okhttp.internal.NamedRunnable.run(NamedRunnable.java:33) // 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1076) // 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:569) // 	at java.lang.Thread.run(Thread.java:856)

Definitely a bug in OkHttp, but nothing I could spot within a few minutes of staring at the code. I’ll try to reproduce and get this fixed.

This may or may not be related, I get the IllegalStateException with this scenario. I'm not 100% sure if this is considered valid
  @Test public void cachedRedirect() throws IOException {
    server.enqueue(new MockResponse()
        .setResponseCode(HttpURLConnection.HTTP_MOVED_PERM)
        .addHeader("Cache-Control: max-age=60")
        .addHeader("Location: /bar"));
    server.enqueue(new MockResponse()
        .setBody("ABC"));
    server.enqueue(new MockResponse()
        .setBody("ABC"));

    Request request1 = new Request.Builder().url(server.url("/foo")).build();
    Response response1 = client.newCall(request1).execute();
    assertEquals("ABC", response1.body().string());

    Request request2 = new Request.Builder().url(server.url("/foo")).build();
    Response response2 = client.newCall(request2).execute();
    assertEquals("ABC", response2.body().string());
  }

@dave-r12 ooh, awesome test. Thankyou

Is there any plan to release another bug fix to the 2.x branch or will this only be in 3.0?

Can do. https://github.com/square/okhttp/issues/2209


Video Share

Hi what is the correct way to share a video?
// this is the complete list of currently supported params you can pass to the plugin (all optional)
var options = {
  message: 'share this', // not supported on some apps (Facebook, Instagram)
  subject: 'the subject', // fi. for email
  files: ['file:///data/data/com.avifa.gifstar/files/b8808070-0a66-11e6-aec0-67c675b9eba0.mp4'], // an array of filenames either locally or remotely
  url: 'https://www.website.com/foo/#bar?a=b',
  chooserTitle: 'Shareereee' // Android only, you can override the default share sheet title
}

var onSuccess = function(result) {
  console.log("Share completed? " + result.completed); // On Android apps mostly return false even while it's true
  console.log("Shared to app: " + result.app); // On Android result.app is currently empty. On iOS it's empty when sharing is cancelled (result.completed=false)
}

var onError = function(msg) {
  console.log("Sharing failed with message: " + msg);
}

window.plugins.socialsharing.shareWithOptions(options, onSuccess, onError);

This did not work with whatsapp, fb or gmail

var options = {

  files: ["file:///storage/emulated/0/DCIM/Camera/a7835bf0-0a64-11e6-aec0-67c675b9eba0.mp4"], // an array of filenames either locally or remotely

  chooserTitle: 'Shareereee' // Android only, you can override the default share sheet title
}

This didnt work either

Related Issues and Possible dupes: #507 #48 #476
Possible solution : #315  (But I dont want to hardcode to only videos)
Possible fix : #165

Update
window.plugins.socialsharing.share(null,null,'file:///storage/sdcard0/Android/data/com.avifa.gifstar/files/08b7f380-0acf-11e6-bab6-4974cf1146bc.mp4')

Using just this uploads to gmail perfectly.
In fb messenger, its shows the video and the duration, but send fails.
In whatsapp it says cant send photo

Can you check if setting the mimetype indeed helps for all those apps? I'm considering extending sharing files with an option to set a mimetype in JS.

Hi @EddyVerbruggen ,
I could share video with everything just by this code below
  private Uri getFileUriAndSetType(Intent sendIntent, String dir, String image, String subject, int nthFile) throws IOException {
    // we're assuming an image, but this can be any filetype you like
    String localImage = image;
    if( image.endsWith("mp4") || image.endsWith("mov") || image.endsWith("3gp")  ){
      sendIntent.setType("video/*");
    }else {
      sendIntent.setType("image/*");
    }

If you want I can do a PR

Makes sense, please do! 👍

Added a PR.
@EddyVerbruggen Great work on the library! Will start on ios soon, lets see how that goes!

👍

@snowbreeze @EddyVerbruggen Will you guys add support to sharing video on iOS anytime soon? Currently sharing a video to whatsapp on iOS doesn't work... :(

Sorry to bring this up again.. @snowbreeze @EddyVerbruggen could you please add .webm file sharing to this as well..


[SW-183116]- adding missing init.py to mistral and mixtral test p…

…ackage
What does this PR do?
updating optimum-habana-fork model test as per the transformers test suite.
adding missing init.py file for mistral and mixtral test suite as this were not included.

https://github.com/huggingface/optimum-habana/pull/1188


RuntimeError: PytorchStreamReader failed reading zip archive: failed finding central directory

I have the same problem, have you fixed it?