undefined reference to 'std::__exception_ptr::exception_ptr::~exception_ptr()'

Hi,
I have successfully generated the 32 toolchain by running the following commands:./make-standalone-toolchain.sh --install-dir=/home/gaor/gaor/my_toolchain --toolchain=arm-linux-androideabi-4.9 --arch=arm --ndk-dir=/home/gaor/gaor/android-ndk-r11c --use-llvm --stl=gnustl with ndk r11c because of my project. But when I try to cross compile the library on android 32bit using the following commands:CXX=clang++ CC=clang scons Werror=1 -j8 debug=1 neon=1 opencl=0 os=android arch=armv7a, it will get these errors:scons: *** [build/neon_convolution] Error 1 src/runtime/CPP/CPPScheduler.cpp:92: error: undefined reference to 'std::__exception_ptr::exception_ptr::~exception_ptr()' src/runtime/CPP/CPPScheduler.cpp:134: error: undefined reference to 'std::__exception_ptr::exception_ptr::~exception_ptr()' src/runtime/CPP/CPPScheduler.cpp:148: error: undefined reference to 'std::current_exception()' src/runtime/CPP/CPPScheduler.cpp:148: error: undefined reference to 'std::__exception_ptr::exception_ptr::~exception_ptr()' src/runtime/CPP/CPPScheduler.cpp:108: error: undefined reference to 'std::__exception_ptr::exception_ptr::~exception_ptr()' src/runtime/CPP/CPPScheduler.cpp:126: error: undefined reference to 'std::__exception_ptr::exception_ptr::exception_ptr(std::__exception_ptr::exception_ptr const&)' and so on. I figure out that these are caused by libstdc++ and I find there are -static-libstdc++ LINKFLAGS in sconscript file, but why still get this problem?
I try to export the generated sysroot path to my 64bit ubuntu env but still get this problem. Are there anyone meet the same problem?

The Android toolchain is broken (not fully C++11 compatible) when used with --stl=gnustl. Could you try to create a toolchain that uses --stl=libc++ instead?
For more information please see the "How to build" section in the documentation: https://arm-software.github.io/ComputeLibrary/v17.04/index.xhtml#S3_3_1_library

Thanks for your help.
But I have tried to use --stl=libc++ to generate android toolchain and met the same problems when building arm compute library. What's more, there are other problems such as
Utils.h:250: error: undefined reference to 'std::basic_ofstream<char, std::char_traits<char> >::basic_ofstream()',
Utils.h:255: error: undefined reference to 'std::basic_ofstream<char, std::char_traits<char> >::open(std::string const&, std::_Ios_Openmode)',
Utils.h:322: error: undefined reference to 'std::basic_ofstream<char, std::char_traits<char> >::~basic_ofstream()' and so on occur when using --stl=libc++.
I wonder if the version of ndk must be r14 beta2? Or the generated toochain need to be set as the bin/lib path?

Just noticed that you're using r11. Unfortunately that will not work as we require r14 (not necessarily the beta. It's just that when we wrote the documentation only the beta was available). The earlier versions have known issues and fail to compile valid code.

Thank you. I use r14 and it works.


request for a property under "envoyconfig" in kafka CRD to pass loadBalancerIP to external loadBalancer like metallb

Is your feature request related to a problem? Please describe.
Currently in kafka CRD, under "envoyConfig" (externallistener) there is no property to set loadBalancerIP. I have a use case where I want to use metallb "spec.loadBalancerIP" functionality to allocate specific IP to envoy LB
Describe the solution you'd like to see
A clear and concise description of what would you like to happen.
Provide  property under "envoyconfig" in kafka CRD to set loadBalancerIP to be used by external loadBalancer like metallb
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

hi, when will this be available?
thanks

@baluchicken is operator available with this fix?
thanks

@priyavj08  We just released it today.


add-lockfile

This pins Torch to <2.2.1, but if deleting the cached version worked, maybe we go with something less restrictive?

This pins Torch to <2.2.1, but if deleting the cached version worked, maybe we go with something less restrictive?

I think we should revert that limit on torch, otherwise LGTM.

This pins Torch to <2.2.1, but if deleting the cached version worked, maybe we go with something less restrictive?

I think we should revert that limit on torch, otherwise LGTM.

You got it, reverting!


[OpenGL] Fix lib files copy when VCPKG_BUILD_TYPE is set

Signed-off-by: Vitalii Koshura<EMAIL_ADDRESS>

/azp run

@PhoebeHui, done. Thanks for the fast review!

Oops, forgot to merge after I pushed changes; thanks @AenBleidd :D

@strega-nil, thank you too :)


OpenSearch container exits on startup due to model deployment failure

Description
The OpenSearch container is exiting with code 1 shortly after startup, preventing the system from fully initializing. The error occurs during the model setup phase, specifically when deploying the TEXT_SIMILARITY model.
Error Message
ERROR:root:Unrecognized error message: Cannot invoke "java.lang.Integer.intValue()" because "totalChunks" is null
ERROR: Failed to setup models

Steps to Reproduce

Run docker compose up
Observe OpenSearch container logs
Container exits before fully initializing

Environment

MacOS: Apple M3 Pro, 14.4
OpenSearch Version: 2.12.0

Additional Details

The error occurs during the deployment of the TEXT_SIMILARITY model
The 'totalChunks' variable is unexpectedly null, causing a NullPointerException
The container successfully performs initial

Complete Log:
opensearch-1  | Waiting for opensearch to start... Sleeping. Try 7/300
demo-ui-1     | No issues found.
opensearch-1  | Waiting for opensearch to start... Sleeping. Try 8/300
opensearch-1  | Waiting for opensearch to start... Sleeping. Try 9/300
importer-1    | No changes at 2024-08-13 08:08:41.489388 sleeping
opensearch-1  | Waiting for opensearch to start... Success
opensearch-1  | **************************************************************************
opensearch-1  | ** This tool will be deprecated in the next major release of OpenSearch **
opensearch-1  | ** https://github.com/opensearch-project/security/issues/1755           **
opensearch-1  | **************************************************************************
opensearch-1  | Security Admin v7
opensearch-1  | Will connect to localhost:9200 ... done
opensearch-1  | Connected as "CN=Admin,O=Aryn.ai,ST=California,C=US"
opensearch-1  | OpenSearch Version: 2.12.0
opensearch-1  | Contacting opensearch cluster 'opensearch' and wait for YELLOW clusterstate ...
opensearch-1  | Clustername: opensearch
opensearch-1  | Clusterstate: GREEN
opensearch-1  | Number of nodes: 1
opensearch-1  | Number of data nodes: 1
opensearch-1  | .opendistro_security index already exists, so we do not need to create one.
opensearch-1  | Populate config from /usr/share/opensearch/config/opensearch-security
opensearch-1  | Will update '/config' with config/opensearch-security/config.yml
opensearch-1  |    SUCC: Configuration for 'config' created or updated
opensearch-1  | Will update '/roles' with config/opensearch-security/roles.yml
opensearch-1  |    SUCC: Configuration for 'roles' created or updated
opensearch-1  | Will update '/rolesmapping' with config/opensearch-security/roles_mapping.yml
opensearch-1  |    SUCC: Configuration for 'rolesmapping' created or updated
opensearch-1  | Will update '/internalusers' with config/opensearch-security/internal_users.yml
opensearch-1  |    SUCC: Configuration for 'internalusers' created or updated
opensearch-1  | Will update '/actiongroups' with config/opensearch-security/action_groups.yml
opensearch-1  |    SUCC: Configuration for 'actiongroups' created or updated
opensearch-1  | Will update '/tenants' with config/opensearch-security/tenants.yml
opensearch-1  |    SUCC: Configuration for 'tenants' created or updated
opensearch-1  | Will update '/nodesdn' with config/opensearch-security/nodes_dn.yml
opensearch-1  |    SUCC: Configuration for 'nodesdn' created or updated
opensearch-1  | Will update '/whitelist' with config/opensearch-security/whitelist.yml
opensearch-1  |    SUCC: Configuration for 'whitelist' created or updated
opensearch-1  | Will update '/audit' with config/opensearch-security/audit.yml
opensearch-1  |    SUCC: Configuration for 'audit' created or updated
opensearch-1  | Will update '/allowlist' with config/opensearch-security/allowlist.yml
opensearch-1  |    SUCC: Configuration for 'allowlist' created or updated
opensearch-1  | SUCC: Expected 10 config types for node {"updated_config_types":["allowlist","tenants","rolesmapping","nodesdn","audit","roles","whitelist","internalusers","actiongroups","config"],"updated_config_size":10,"message":null} is 10 (["allowlist","tenants","rolesmapping","nodesdn","audit","roles","whitelist","internalusers","actiongroups","config"]) due to: null
opensearch-1  | Done with success
opensearch-1  | Waiting for opensearch on ssl... Success
opensearch-1  | CLUSTER SETTINGS SET
opensearch-1  | INFO:root:ARYN MODEL GROUP ID: QwLTQJEBS9XVaW7rBoNz
opensearch-1  | INFO:root:>EMBEDDING MODEL ID: RQLTQJEBS9XVaW7rB4Mh
opensearch-1  | WARNING:root:Error detected: {'model_id': 'SALTQJEBS9XVaW7raIMd', 'task_type': 'DEPLOY_MODEL', 'function_name': 'TEXT_SIMILARITY', 'state': 'FAILED', 'worker_node': ['hLMxDOX6T0KJd7L7jbfKtg'], 'create_time':<PHONE_NUMBER>656, 'last_update_time':<PHONE_NUMBER>705, 'error': '{"hLMxDOX6T0KJd7L7jbfKtg":"Cannot invoke \"java.lang.Integer.intValue()\" because \"totalChunks\" is null"}', 'is_async': True}
opensearch-1  | ERROR:root:Unrecognized error message: Cannot invoke "java.lang.Integer.intValue()" because "totalChunks" is null
opensearch-1  | ERROR: Failed to setup models
opensearch-1 exited with code 1

We see this from time to time... can you do the following:
$ docker compose up reset
$ NOEXIT=1 DEBUG=1 docker compose up
# in another terminal or something
$ docker compose exec -it opensearch sh -c "cat /usr/share/opensearch/data/aryn_status/opensearch.log"

and tell me what you get?


⚠ sandbox-api.piste.gouv.fr healthcheck has degraded performance

In 4dbb74b, sandbox-api.piste.gouv.fr healthcheck (https://sandbox-api.piste.gouv.fr/cassation/judilibre/v1.0/healthcheck) experienced degraded performance:

HTTP code: 200
Response time: 2596 ms

Resolved: sandbox-api.piste.gouv.fr healthcheck performance has improved in 47768c7.


[Bug][6.x] relationship column ignores attribute

Bug report
What I did
I've used in V5 relationship field like this:
[
    'name' => 'referralSource', // name of relationship method in the model
    'type' => 'relationship',
    'label' => trans('Ref'),
    'orderable' => true,
    'orderLogic' => function ($query, $column, $column_direction) {
        return $query->leftJoin('referral_sources', 'users.id', '=', 'referral_sources.user_id')
            ->select('users.*', 'referral_sources.source')
            ->orderBy('referral_sources.source', $column_direction);
    },
    'model' => ReferralSource::class,
    'attribute' => 'source', // foreign key attribute that is shown to user
]

What I expected to happen
Expected to see only source field of ReferralSource model.
What happened
It shows entire related model as json

Is it a bug in the latest version of Backpack?
Latest v6 backpack after migration from v5
Backpack, Laravel, PHP, DB version
When I run php artisan backpack:version the output is:
PHP VERSION:
PHP 8.1.12 (cli) (built: Oct 28 2022 17:39:37) (NTS)
Copyright (c) The PHP Group
Zend Engine v4.1.12, Copyright (c) Zend Technologies
with Zend OPcache v8.1.12, Copyright (c), by Zend Technologies
LARAVEL VERSION:
<IP_ADDRESS>
BACKPACK PACKAGE VERSIONS:
backpack/basset: 1.0.0
backpack/crud: 6.0.6
backpack/filemanager: 3.0.2
backpack/generators: v4.0.1
backpack/newscrud: v5.0.0
backpack/pagemanager: 3.2.0
backpack/permissionmanager: 7.0.0
backpack/pro: 2.0.8
backpack/settings: 3.1.0
backpack/theme-coreuiv2: 1.1.3

Tiny update regarding this issue:
looks like it fails only on hasOne relationship. BelongsTo works as it should be.

Hello there !
I've got the exact same problem and created an issue. I'm also facing the problem on a "belongsToMany" n-n relationship.

@pxpm can you take this over please?

I think I've already fixed this in PRO 2.0.10 https://backpackforlaravel.com/products/pro-for-unlimited-projects/CHANGELOG.md
Please run a composer update and make sure you got the latest versions installed with php artisan backpack:version.
If the error persist please let me know and we can re-open this! 🙏
Cheers

btw, my mistake. The problem in relationship column, not field

Hey @marechenok
From the description you gave you are using a HasOne relation that's not aware of the attribute. That's a "select" thing. (BelongsTo, BelongsToMany etc). HasOne is not a selectable relation.
You can display the value of your relation with: CRUD::column('referralSource.source') assuming your relation is called referralSource. If you want to display more fields in the same column, you can define the subfields (name is correct, subfields works for columns and fields) and the column will display similar to a table.
Let me know how it goes.

$this->crud->addColumn('referralSource');

$this->crud->addColumn('referralSource.source');

Made it works like this:
[
    'name' => 'referralSource.source', // name of relationship.attribute
    'type' => 'relationship',
    'label' => trans('Ref'),
    'orderable' => true,
    'orderLogic' => function ($query, $column, $column_direction) {
        return $query->leftJoin('referral_sources', 'users.id', '=', 'referral_sources.user_id')
            ->select('users.*', 'referral_sources.source')
            ->orderBy('referral_sources.source', $column_direction);
    },
],


Feat: reworked quick tour functionalities

@fsdavid as promised, I prepared a PR to your quick tour branch.

reworked the calculation of position of quick tour component + arrow (they are now completely dynamic)
added resize observer, which should update the position when window is resized
reworked force recalculate position

Can you take a look if I have missed anything?

One thing I should note is, I have no idea how arrows differed from one and another, so I had to recreate them.

As I see while touring full viewer is darker, I'm not sure that it is better than keep it light. Could you check the google maps approach?

The tours progress indicator is missing.

Does this arrow look nice?

could we change it back?

Arrow for the slice view tools are missing - I had the same problem and I got the review that it needs to be at the correct position.

Region search slide is missing

Automatic changes for the layer selector don't work anymore. The same approach is used also for google maps.

As I see while touring full viewer is darker, I'm not sure that it is better than keep it light. Could you check the google maps approach?

I actually disagree with google map's approach. I find it very hard to find the tour panel, without the overlay

The tours progress indicator is missing.

This is true. This can be added relatively easily, but the danger is that it can change dynamically (depending on elements being created/destroyed etc)

Region search slide is missing

How did you handle when search bar is not being shown?

Automatic changes for the layer selector don't work anymore. The same approach is used also for google maps.

Hmm, there is a slight difference. Google maps elements do not change drastically. They translate, and (maybe) scale a little bit.
In the case of layer selector, the entire element element transform into a different element.

Does this arrow look nice?
could we change it back?

I don't mind changing it back, but as discussed, I have no idea about the difference between arrow1-arrow7.
If you feel strongly about, feel free to push to branch with new arrows, but with more descriptive names how to distinguish the arrows.

Arrow for the slice view tools are missing - I had the same problem and I got the review that it needs to be at the correct position.

This can be fixed. I think i missed it yes.

As I see while touring full viewer is darker, I'm not sure that it is better than keep it light. Could you check the google maps approach?

I actually disagree with google map's approach. I find it very hard to find the tour panel, without the overlay

Yeah, maybe it is a disadvantage but, that's why we can change the style of the tip - so we will not have problems at all - users will explore features better and find tip cards easier.

The tours progress indicator is missing.

This is true. This can be added relatively easily, but the danger is that it can change dynamically (depending on elements being created/destroyed etc)

Yeah, I think it should not be the problem - it was Timos suggestion to see the progress. You are right and that's why I think it is better to implement a progress indicator with point icons, not with numbers, as it was in the last version.

Region search slide is missing

How did you handle when search bar is not being shown?

When the sidebar was open, in normal cases region search would be there. (I guess we can also watch if there is dataset preview)

Automatic changes for the layer selector don't work anymore. The same approach is used also for google maps.

Hmm, there is a slight difference. Google maps elements do not change drastically. They translate, and (maybe) scale a little bit.
In the case of layer selector, the entire element element transform into a different element.

Yeah, that's why it is useful to have overwritten position. Anyways we will stay into the same component I guess.

As I see while touring full viewer is darker, I'm not sure that it is better than keep it light. Could you check the google maps approach?

I actually disagree with google map's approach. I find it very hard to find the tour panel, without the overlay

Yeah, maybe it is a disadvantage but, that's why we can change the style of the tip - so we will not have problems at all - users will explore features better and find tip cards easier.

removing the darkened overlay is actually very easy, but I still disagree that it should be be clear.

The tours progress indicator is missing.

This is true. This can be added relatively easily, but the danger is that it can change dynamically (depending on elements being created/destroyed etc)

Yeah, I think dynamic changes should not be the problem - it was Timos suggestion to see the progress. You are right and that's why I think it is better to implement a progress indicator with point icons, not with numbers, as it was in the last version.

I agree. I will push commit today or next days for this issue.

Region search slide is missing

How did you handle when search bar is not being shown?

When the sidebar was open, in normal cases region search would be there. (I guess we can also watch if there is dataset preview)

hmm, I thought I added it in, but maybe i took it out by accident.
I will take a look at the region selection and re add the quick tour to it, if I accdentally took it out

Does this arrow look nice?
could we change it back?

I don't mind changing it back, but as discussed, I have no idea about the difference between arrow1-arrow7.
If you feel strongly about, feel free to push to branch with new arrows, but with more descriptive names how to distinguish the arrows.

Nice I will do that, just I wanted to mention that there is 1 arrow for almost all the slides. I think that for the elements in corner could be better to have little bit different style arrow than others. I will try to make it work.

@xgui3783 Thank you so much for the PR :) I will make changes for arrow SVGs.

As I see while touring full viewer is darker, I'm not sure that it is better than keep it light. Could you check the google maps approach?

I actually disagree with google map's approach. I find it very hard to find the tour panel, without the overlay

Yeah, maybe it is a disadvantage but, that's why we can change the style of the tip - so we will not have problems at all - users will explore features better and find tip cards easier.

removing the darkened overlay is actually very easy, but I still disagree that it should be be clear.

Yeah, then let's leave it darker.

Automatic changes for the layer selector don't work anymore. The same approach is used also for google maps.

Hmm, there is a slight difference. Google maps elements do not change drastically. They translate, and (maybe) scale a little bit.
In the case of layer selector, the entire element element transform into a different element.

Yeah, that's why it is useful to have overwritten position. Anyways we will stay into the same component I guess. You can look at the third slide of google maps.

I see google map's third slide, I think I see what you mean, I will take a look at how it can be done.
I still very much disagree that it requires hard coding of the positions, that the positions of the tour can, and should be calculated dynamically.

Automatic changes for the layer selector don't work anymore. The same approach is used also for google maps.

Hmm, there is a slight difference. Google maps elements do not change drastically. They translate, and (maybe) scale a little bit.
In the case of layer selector, the entire element element transform into a different element.

Yeah, that's why it is useful to have overwritten position. Anyways we will stay into the same component I guess. You can look at the third slide of google maps.

I see google map's third slide, I think I see what you mean, I will take a look at how it can be done.
I still very much disagree that it requires hard coding of the positions, that the positions of the tour can, and should be calculated dynamically.

Yeah, it would be perfect, if it will work without hardcoded position.

@fsdavid I pushed a few more changes. Except for arrow styling, the rest of the issue should be solved.

@fsdavid I pushed a few more changes. Except for arrow styling, the rest of the issue should be solved.

Now I will make arrow changes here.
I still see two issues:

Ordering does not work correctly
For the atlas layer selector expanded - tip should be on the right-side because it is overflowed at the top or bottom positions

@fsdavid can you be more specific which tour has the order incorrectly placed? it would help me pin down the issue.
re: atlas layer browser placement issue: I will look into it.

@fsdavid can you be more specific which tour has the order incorrectly placed? it would help me pin down the issue.
re: atlas layer browser placement issue: I will look into it.

They are different at different times - I guess, sorting algorithm does not work at all. The directive has the input variable order and slides should be ordered by this.

@fsdavid I pushed two commits, which should fix the order issue, and partially fix the dialog position issue.
smartly positioned quick tour will now be restricted inside the viewport (see below)

Absolute positioned tour points (e.g. slice views, see below) will look wonky. I will provide a fix tomorrow.

@fsdavid per our discussion, adaptive region search quick tour is now commited

@fsdavid per our discussion, adaptive region search quick tour is now commited

Great looks pretty. Thank you very much.

@fsdavid anything else we should change?
also, since now there are merge conflicts, I am thinking of merging this to dev instead, and close the other PR, rather than resolve the merge conflicts.

@xgui3783 No problem - I'm resolving conflicts

@xgui3783 Conflicts are resolved and will be ready after checks.

@fsdavid and now tests are failing.
Do you have anything against PR exmp_quickTour -> dev instead of exmp_quickTour -> dev_quick_tour -> dev ?
The commit history will still be there, and your work is credited.

@fsdavid and now tests are failing.
Do you have anything against PR exmp_quickTour -> dev instead of exmp_quickTour -> dev_quick_tour -> dev ?
The commit history will still be there, and your work is credited.

Hah, I just meant to keep the flow, but resolving conflicts from GitHub was not a good idea :). To avoid force changes I've created a new PR "exmp_quickTour_forMerge" directly to the dev 😬. But we can force remove the last commit from here as well, as you wish. Sorry :)

I make changes here :)

now that repo is public, it's a good idea to avoid force pushes.
I will create a new PR, and ref it here.


not standart baude rate

can i use unsupported baude rate like 10400 baude for all supported usb-uart chip?

@Mebius84 I am afraid not.


Update stable version in repo from 2.0.3 to 2.1.5

Think about update stable version to 2.1.5
Version: stable=2.0.3 (98 days old) => latest=2.1.5 (15 days old)
Installs: stable=1295 (41.18%), latest=599 (19.05%), total=3145
Click to edit

This issue seems to be outdated
This issue suggests to update the stable version of this adapter to 2.1.5 but the current stable version is already 2.1.5.
So this issue should be closed.


No way to add a data source

As you try to start a project where you are going to upload data, you run into a blocking issue.

Start creating your standard project and select "Import your own"

You're brought to a page where you can choose the data source you'll be adding imagery to

Now I'm stuck. So I exit out of the project creation modal and tab over to "Imports"

But there's no way to add a data source. Two opportunities to fix this issue:
Add the ability to add a data source at the appropriate place in the project creation process
Add the ability to add a data source on the "Imports" page

+1 from a user


Published module display

This PR adds the published module display. This was rather straightforward because I implemented all relevanted elements for the invitations screen.

Note that the actions for published modules are not yet defined and hence not implemented.

Depends on #169 being merged into this PR.


Added in a few fixes, tidied up code base and begun work on additional modules and functionality

Closed for repull due to side conversation


DBZ-7351 Avoid child data snapshots from PostgreSQL parent tables

When PostgreSQL tables are configured with inheritance (INHERIT clause), data is streamed by Debezium from the table where the data resides (usually the child tables).
However, during the initial/incremental snapshot, Debezium selects all data from the parent tables, including child data, which pushes unexpected/duplicate data into the topics (all data from child tables).
Using a "SELECT ... FROM ONLY" retrieves only data from the current table and avoids retrieving data from child tables.

@koleo Please try to run RecordsSnapshotParallelProducerIT and RecordsSnapshotProducerIT with Postgres 14 (you can use postgres-14 profile.

Yes I will 👌

affects us too


Feature/uot 130924 - updating recommender to take lists

Description:

updating recommender model to take lists of filenames
removing the need to check a corpus
refactoring for plural
Test:
start ml api
curl --location --request POST 'http://localhost:5000/recommender' \ --header 'Content-Type: application/json' \ --data-raw '{   "filenames": ["Title 10"] }'


Fix envvar-arg mapping when spaces are in value.

The environment variable to ES option mapping in es-docker does not
work correctly when an option value contains whitespace.  This commit
changes the assembly of options to use an array instead of a string, and
then uses a proper all-array-items-to-words expansion at the end so
things like quoting don't need to be worried about.

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

@kainz Thank you for this PR! As we are working on a rather large refactoring effort for 5.4, including switching to a different base, do you mind pushing this PR against https://github.com/elastic/elasticsearch-docker/tree/switch-to-centosbase? The testing framework has also been reworked and simplified and allows us to add an acceptance test for this feature.

@kainz The work I was talking about can be found in https://github.com/elastic/elasticsearch-docker/pull/55. If you have the time to create the same PR against https://github.com/elastic/elasticsearch-docker/tree/shell_friendly_parameters (lines: 17 , 44 , 51 and 70) I will be happy to merge it ASAP.
If you don't have time to do this until tomorrow, (sorry for the hurry), just let me know, I can add it and properly reference your contribution. Thank you!

@dliappis Sure, I'm going to close this PR and open a rebased one against shell_friendly_parameters.

@kainz Can you share what key you were passing a value containing a space that the current approach failed on (and the value too, if you can)?

I see you opened a new PR, let me follow you over there rather than here on this closed PR.

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

We have decided to push back shell friendly env var fixes for a bit later, so I've merged your original PR thank you!


Depending on time of changelog creation the date of old changelog entries changes

Maybe this is not related to github-changelog-generator may be it is.
I have a closed pull request that was closed and merged on 08.04.2017 23:23 MESZ (UTC+2) according to GitHub. I created the changelog on 09.04.2017 00:05 MESZ (UTC+2). The release got the release date of 09.04.2017. Let's name this release R-1.
When I create a changelog for new releases the date for release R-1 changes to 08.04.2017 depending on the time I create the changelog.
According to GitHub the commits API returns dates with timeformat: https://developer.github.com/v3/#timezones
I am not a ruby user so I have no clue if we need to specify a timezone for strftime in https://github.com/skywinder/github-changelog-generator/blob/master/lib/github_changelog_generator/generator/generator_generation.rb#L56

strftime's date format is a configuration options
        opts.on("-f", "--date-format [FORMAT]", "Date format. Default is %Y-%m-%d") do |last|
          options[:date_format] = last
        end


Remove usage of DT_INST in samples

Is your enhancement proposal related to a problem? Please describe.
Various samples use DT_INST(0, compat) to get the node identifier for a particular compatible. Using instance numbers in samples does more harm than good: explaining the semantics is quite complicated.
(Don't believe me? Have a look at the awful amount of text describing them in the DT_INST documentation.)
Putting the DT_INST macro in front of users just for the sake of getting a device should be considered an antipattern. It also has the problem that it forces users to understand devicetree node identifiers etc., which is a whole additional pile of complexity that 99.9% of people who just want to get a working const struct device* and move on within a simple sample application don't and should not care about.
Describe the solution you'd like

Add a new macro, DEVICE_DT_GET_ANY(compat). This takes a devicetree compatible (in lowercase-and-underscore form) and gives you a straight up const struct device* created for that devicetree compatible.
Use this in samples that just want to get a device by any means necessary for the purposes of showing off an API or a particular driver's implementation of it

Describe alternatives you've considered
In #30536, I originally tried adding sample specific aliases, but this got shot down for good reasons.

#30536 adds DEVICE_DT_GET_ANY. I will postpone switching other samples over to using it until after we get a chance to discuss the idea in dev-review.

Fully supporting the approach.

+1

As suggested in the first discussion below, this could be an opportunity to provide a small library of routines that would help make samples more uniform.  Candidates for that library include:

A function to retrieve and validate a device pointer.
API to get the current kernel time in millisecond resolution in a readable standard format which I currently have replicated in multiple samples that track values over time.

Perhaps there are more.
Such a library isn't directly related to this, except that if it were available reworking the way samples get devices could be combined with general review and cleanup of the samples.

Would it be appropriate time to introduce aliases or zephyr_ node labels for the common sensors and replace all samples that do the same thing, like x temperature sensor samples, with generic one?

As suggested in the first discussion below, this could be an opportunity to provide a small library of routines that would help make samples more uniform.

My general experience with previous attempts to do things like this has been uniformly negative, so I have reservations.
The problem is that such things have generally worked for their developers, but it's easy for hardcoded assumptions that the library code lives in zephyr/samples to slip in.
When that happens, as a user trying to recursively copy a sample directory somewhere else in order to start building on top of it as your own application, I've been frustrated by needing to fight the build system to get access to the common code.
If the functionality is so commonly needed by zephyr applications that a large fraction of samples require it, then IMO it should be placed somewhere outside of samples, to preserve the usual layering and ability to build it into out of tree apps with Kconfig.

Would it be appropriate time to introduce aliases or zephyr_ node labels for the common sensors and replace all samples that do the same thing, like x temperature sensor samples, with generic one?

We've debated this, but I think this issue stands anyway. I agree that having a general purpose "temperature sensor sample" would be a good idea, but in practice people are going to want samples for specific drivers no matter what.

My general experience with previous attempts to do things like this has been uniformly negative, so I have reservations.
The problem is that such things have generally worked for their developers, but it's easy for hardcoded assumptions that the library code and the application code live in zephyr/samples to slip in.

Fair enough, though I think that could be averted by some reasonable review and API design.  E.g. my "timestamp" format is good for arbitrary durations extending to years; the only clear flaw is it uses a static buffer and that could be easily worked around with a now_str_r() variant like asctime_r().  (The name, of course, is completely inadequate.)
(I'm really more interested in getting that specific functionality into Zephyr somewhere it can be re-used so I don't have to keep having to paste it into applications when I'm trying to get time values in a readable format.)

If the functionality is so commonly needed by zephyr applications that a large fraction of samples require it, then IMO it should be placed somewhere outside of samples, to preserve the usual layering and ability to build it into out of tree apps with Kconfig.

Oh, absolutely, I wouldn't suggest a library that's restricted for use in samples and/or tests.

(I'm really more interested in getting that specific functionality into Zephyr somewhere it can be re-used so I don't have to keep having to paste it into applications when I'm trying to get time values in a readable format.)

I haven't looked at this case, but yeah, my general feeling is that these things should be encoded as helper functions that live in the files which provide the subsystem functionality, rather than a "libsample" directory. Sounds like this one could be solved that way.

Would it be appropriate time to introduce aliases or zephyr_ node labels for the common sensors and replace all samples that do the same thing, like x temperature sensor samples, with generic one?

We've debated this, but I think this issue stands anyway. I agree that having a general purpose "temperature sensor sample" would be a good idea, but in practice people are going to want samples for specific drivers no matter what.

Where was it discussed? What would be the desired approach aliases or zephyr prefixed node labels?

Where was it discussed?

All the usual places -- meetings, Slack, miscellaneous GitHub issues.

What would be the desired approach aliases or zephyr prefixed node labels?

It's never really been settled, but the general consensus seemed to be that applications can use aliases instead of node labels for pointing at particular nodes.

@benjaminbjornsson mind taking a look at this.


Fix: Do not combine default type imports with value imports

This fixes a bug which was causing default type imports to be combined into value imports, which isn't safe to do.  For instance,
import { ComponentProps, useEffect } from 'react';
import type React from 'react';

was turning into
import { ComponentProps, useEffect, React } from 'react';

Which is not correct.  This change prevents default type imports from ever being merged.

I'm going to merge this to get the fix released, but I'd still love an ex post facto review if anyone has some time.


Setup nextcloud/owncloud integration tests for WebDAV

NextCloud and OwnCloud provides webdav APIs, it's better for us to setup integration tests to make sure OpenDAL works well on them
Tasks

[x] #2629
[x] #2630

Future possibilities
Nextcloud and OwnCloud provides their own extensions of WebDAV, we can implement native service for them in the future.

I think we can /close this issues as completed


Add a choice of the number of the displayed information in the tables.

Add this possibility wherever there is only a table ( gateways, nodes, sensors, etc )

@arturmon I will add in global settings to change number of rows to display in tables.


disabled use_custom_ssl_port_test pre 3 since the functionality was n…

…ot available

Looks good, +1.


Is this the same idea with fastKAN

Hi, your work is really great. But I do notice that both you and the fastkan use RBF kernels as bases function. Can I ask if both are the same?

The concept remains the same, but this version is more optimized and improved.


Unite error handling for AWS and GCP HTTP gateways

GCP API gateway service is missing some features that AWS offers, namely request body validation and support for API keys. Due to this, each gateway handles error states a bit differently. We should unite the behavior so that gateways will act the same no matter which cloud provider the user uses.
From a recent PR, also reconsider if status 400 is the correct status code or if there might be a more suitable code to use.

Hi @Siegrift, I've pushed this back and prioritized other issues but since I've managed to blast the rest of the column, I'm working on it now. I'm collecting various error messages via postman and putting together a list so I hope this will be done by the call.

Hi, @amarthadan and @Siegrift, I've used the coingecko-testable example to attempt various scenarios (I helped myself out by reading the code and designing the test cases accordingly). I'm happy to say all of them performed as intended in the code on both providers, but let me just sum it up here:

incorrect API key - a 401 error
missing endpoint ID - a 400 error
request without a body - a 400 error
incorrect encodedParameters value - a 400 error

This didn't take that long but then I realized the signed and relayed gateway files were also changed so I ran the tests with those two as well on both providers. Thankfully, nothing's broken :) I'm happy to move this to Done.


setuptools wants to install 'examples' and 'benchmarks' package

Please don't use setuptools.find_packages() in setup.py, as this causes setuptools to want to install packages named 'examples' and 'benchmarks'.  This generally wreaks havoc if fastTSNE isn't installed in a virtual environment.

Thanks for bringing this up, I'll take a look at it ASAP.

diff --git a/setup.py b/setup.py
index 452079d..755f284 100644
--- a/setup.py
+++ b/setup.py
@@ -37,7 +37,7 @@ setup(
<EMAIL_ADDRESS>version='0.2.7',
url='https://github.com/pavlin-policar/fastTSNE',

packages=setuptools.find_packages(),

packages=['fastTSNE','fastTSNE.pynndescent','fastTSNE._matrix_mul'],
ext_modules=extensions,
install_requires=[
'numpy>1.14',

The one-line patch above worked for me.  I note that fastTSNE is now a dependency of Orange 3.18 (https://orange.biolab.si/).

Thanks, I've already pushed a patch to a branch (e7638af) where I'm adding several improvements. I'll merge this as soon as I test this on a mac.

I've released a new version which fixes this. Please note that the package has been renamed to openTSNE. It is already available on PyPi, and I've already opened a PR on conda-forge, which I assume will be merged in the next couple of days.


Popover is misaligned when certain html styles are applied

CodeSandbox demo
https://codesandbox.io/s/dry-water-t02k7

Steps to reproduce the problem

Open the popper (it has placement right)
Shrink the viewport a bit by opening devtools or moving the codesandbox console up
Observe the tooltip is aligned too high
Remove any of the styles from body/html height 100% or overflow-x: hidden or the position relative wrapper and see it fix itself.

What is the expected behavior?
the body/html and relative wrapping styling should not warp the alignment.
What went wrong?
Similar to https://github.com/popperjs/popper-core/issues/1110

html has style of height 100%
body has styles for overflow-x: auto and height: 100%
a containing div has position: relative;

Any other comments?
The fix from https://github.com/popperjs/popper-core/issues/1110 does not work for this issue

I think it's the same issue, you just need to apply it to preventOverflow as well as flip


Bad request for commit endpoint: It appears that one or more of your files contain valid Hugging Face secrets, such as tokens or API keys

I tried to push GPT2 to my HF account.
I have used os to hide the token:
os.environ["HF_TOKEN"] = "token"
Error message:
ERROR    | 2024-09-13 10:59:26 | autotrain.trainers.common:wrapper:120 - train has failed due to an exception: Traceback (most recent call last):
File "C:\Users\sharm\anaconda3\lib\site-packages\huggingface_hub\utils_errors.py", line 304, in hf_raise_for_status
response.raise_for_status()
File "C:\Users\sharm\anaconda3\lib\site-packages\requests\models.py", line 1021, in raise_for_status
raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 400 Client Error: Bad Request for url: https://huggingface.co/api/models/Amitontheweb/my-autotrain-GPT2/commit/main
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "C:\Users\sharm\anaconda3\lib\site-packages\autotrain\trainers\common.py", line 117, in wrapper
return func(*args, **kwargs)
File "C:\Users\sharm\anaconda3\lib\site-packages\autotrain\trainers\clm_main_.py", line 28, in train
train_sft(config)
File "C:\Users\sharm\anaconda3\lib\site-packages\autotrain\trainers\clm\train_clm_sft.py", line 56, in train
utils.post_training_steps(config, trainer)
File "C:\Users\sharm\anaconda3\lib\site-packages\autotrain\trainers\clm\utils.py", line 327, in post_training_steps
api.upload_folder(
File "C:\Users\sharm\anaconda3\lib\site-packages\huggingface_hub\utils_validators.py", line 114, in _inner_fn
return fn(*args, **kwargs)
File "C:\Users\sharm\anaconda3\lib\site-packages\huggingface_hub\hf_api.py", line 1286, in _inner
return fn(self, *args, **kwargs)
File "C:\Users\sharm\anaconda3\lib\site-packages\huggingface_hub\hf_api.py", line 4724, in upload_folder
commit_info = self.create_commit(
File "C:\Users\sharm\anaconda3\lib\site-packages\huggingface_hub\utils_validators.py", line 114, in _inner_fn
return fn(*args, **kwargs)
File "C:\Users\sharm\anaconda3\lib\site-packages\huggingface_hub\hf_api.py", line 1286, in _inner
return fn(self, *args, **kwargs)
File "C:\Users\sharm\anaconda3\lib\site-packages\huggingface_hub\hf_api.py", line 3719, in create_commit
hf_raise_for_status(commit_resp, endpoint_name="commit")
File "C:\Users\sharm\anaconda3\lib\site-packages\huggingface_hub\utils_errors.py", line 358, in hf_raise_for_status
raise BadRequestError(message, response=response) from e
huggingface_hub.utils._errors.BadRequestError:  (Request ID: Root=1-66e3cdb3-405d77654163ce5664aefd2f;34dbc6ef-92df-4ddf-8a55-6b8276332f66)
Bad request for commit endpoint:
It appears that one or more of your files contain valid Hugging Face secrets, such as tokens or API keys. It is important to keep your secrets private and not expose them in code that is publicly accessible. Read more: https://huggingface.co/docs/hub/spaces-overview#managing-secrets Offending files: - .ipynb_checkpoints/training_params-checkpoint.json (ref: refs/heads/main, token: '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')
It appears that one or more of your files contain valid Hugging Face secrets, such as tokens or API keys. It is important to keep your secrets private and not expose them in code that is publicly accessible. Read more: https://huggingface.co/docs/hub/spaces-overview#managing-secrets  Offending files:   - .ipynb_checkpoints/training_params-checkpoint.json (ref: refs/heads/main, token: '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')
ERROR    | 2024-09-13 10:59:26 | autotrain.trainers.common:wrapper:121 -  (Request ID: Root=1-66e3cdb3-405d77654163ce5664aefd2f;34dbc6ef-92df-4ddf-8a55-6b8276332f66)
Bad request for commit endpoint:
It appears that one or more of your files contain valid Hugging Face secrets, such as tokens or API keys. It is important to keep your secrets private and not expose them in code that is publicly accessible. Read more: https://huggingface.co/docs/hub/spaces-overview#managing-secrets Offending files: - .ipynb_checkpoints/training_params-checkpoint.json (ref: refs/heads/main, token: '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')
It appears that one or more of your files contain valid Hugging Face secrets, such as tokens or API keys. It is important to keep your secrets private and not expose them in code that is publicly accessible. Read more: https://huggingface.co/docs/hub/spaces-overview#managing-secrets  Offending files:   - .ipynb_checkpoints/training_params-checkpoint.json (ref: refs/heads/main, token: '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')
INFO     | 2024-09-13 10:59:27 | autotrain.parser:run:217 - Job ID: 5348

you should remove the file with token inside and also refresh your token as you published it here

Thanks, it's resoled.

dont forget to revoke your token! :)

Yes, I have refreshed the token, many thanks!
On Fri, 13 Sept 2024 at 12:00, abhishek thakur @.***>
wrote:

dont forget to revoke your token! :)
—
Reply to this email directly, view it on GitHub
https://github.com/huggingface/autotrain-advanced/issues/762#issuecomment-2348135084,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMBK3B67EB7BW5WP2WVGA73ZWKA7LAVCNFSM6AAAAABOEUANXSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNBYGEZTKMBYGQ
.
You are receiving this because you modified the open/close state.Message
ID: @.***>


Add support for routing on subdomains

Feature Request
Not all of the url routing is complete. I'm just wondering if  support for routing on subdomains could be added into the framework.
Detailed Description

Add new methods to the router.rs and server.rs to support users to route on subdomains as well. An example of the resulting api I am thinking of would look like so:
let mut app = tide::new();
app.on_subdomain(":sub1.:sub2.:sub3").at("/").with(validate_subdomain).all(handle_user);

Context

I have an application that can have multiple tenets that can upload content to the server and would like to configure my webserver to be able to route on subdomains. This will benefit other users of tide who want to add the same functionality to their own application.
Possible Implementation

I haven't dove into the code base that much but i would assume that I would need to add functionality to server.rs and router.rs. I know this maybe a big addition so I wouldn't mind taking a chance and implementing it and putting in a PR.
Just wondering if this project is also interested in adding support for it and want to start a discussion.

We had a bit of a chat about this earlier today, I think this is a fairly promising direction. Earlier art for subdomain routing includes:

koa-sub-domain
Rails subdomain routing (official docs)

The Rails subrouting API seems quite interesting; if we were to translate that to Tide it could look like:
let mut app = tide::new();
app.subdomain("blog").at("/").get(|_| async { Ok("welcome to my blog") });
app.listen("localhost:8080").await?;

I'm leaning towards app.subdomain rather than abbreviating it as app.sub  to prevent confusion with app.nest. Also we should only add subdomain to Server but not Route. Because subdomains feel like they should be declared at the root of the app, not nested within routes. As such we should perhaps also guard that when nesting apps we disallow subdomains on the app we're nesting.

That's my opinion, @jbr had some different ideas that I'm hoping he'll share!

proposal in brief
app.at("/path/still/works").get(…);
app.at("http://*/only-http").get(…);
app.at("//example.com/any-scheme/but-only-example.com").get(…);

why don't other servers do this?
This proposal is further afield from examples in other frameworks, in that I've never seen a http server router that does this. In general, perhaps because http/1.0 requests don't have a host, routers treat the host, scheme, and path as distinct aspects of a request. In tide, we always have a host for a request.

Happy to hear the advice. I really enjoyed looking into the Rails subdomain routing and have an approach I think would work. I liked your proposal and I think the API design should look like the following:
let mut app = tide::new();
app.subdomain("example").at("/").get(|_| async { Ok("example subdomain") });
app.subdomain("portal").with(authentication).at("/").get(|_| async { Ok("Secure portal") });
app.subdomain(":user.blog").at("/").get(|req| async { Ok(req.param::<String>("user").unwrap()) });
app.listen("example.com").await?;

You may have noticed but I am making one prediction which is that the user treats their apex domain as their base url. I'm not sure 100% sure of a good way to allow the user to state the base url.
In terms of the design of additional code needed, I believe it would be best to do the same thing that route-recognizer is doing and by having a Router container around the Route struct. I propose wrapping a Subdomain struct around a Namespace container:
struct Server<State> {
    ...
    namespace: Namespace<State>;
    ...
}

struct Namespace<State> {
    router: SubdomainRouter<Subdomain<State>>
}

struct Subdomain<State> {
    subdomain: String,
    router: Router<State>,
    middleware: Vec<Arc<dyn Middleware<State>>>,
}

The SubdomainRouter<T> would just be like route-recognizer except simpler.
I wouldn't mind hearing your thoughts about this this design. I am working on an implementation and hopping for it to be finished soon.

Is this still being considered? Would be nice to e.g. partition app routes from api routes.

This is a feature that I'd really like as well. Any update on this? I'm willing to contribute if needed, I'll just need a little guidance.

I no longer recall the conversation well enough on what @jbr's ideas for this were, only that they were interesting.

I think I stalled out on that idea for tide because it would work better if there were a way to modularly experiment with alternative routers without having to opt everyone into a new experimental router. It might be worth exploring it in trillium first and then proposing it over here once the dust has settled, since adding a new router to trillium is just adding a new opt-in crate.
The core idea was to allow "route specifications" to look like a full url, with matchers in any position, so "https://$domain/users/$user_id" or ""$subdomain.example.com/users/$user_id" or "$scheme://example.com/users/$user_id" would all be valid route specs. Note that I typed this out with $ instead of : to represent named route params, in order to allow for $scheme://. It would still be valid to describe a route as "/users/$user_id", which would be functionally equivalent to "$scheme://$domain/users/$user_id" but without capturing scheme and domain (probably?).


chore(deps): update secops orb to v2.0.1

This PR contains the following updates:

Package
Type
Update
Change

secops
orb
patch
2.0.0 -> 2.0.1

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - "after 8am and before 4pm on tuesday" in timezone Etc/UTC.
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Renovate Ignore Notification
Because you closed this PR without merging, Renovate will ignore this update (2.0.1). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.
If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.


Images no longer enter Media Pool on Resolve Studio, starting version 19.1

I swear this update was a downgrade, performance declined as well as this script breaking.
I was hoping I just reached the natural limit of pastable assets (it quit working at C999 exactly lol), but upon starting a new project, the issue persists.
It'll even create a "Clipboard" folder in the media pool, but simply won't add what's in my clipboard
If it helps in diagnosing - I checked the folder it creates, and there is no C0 image within it, so it looks like it's failing at the step where it creates the image file from whatever is in my clipboard
I should note that I did a windows update concurrently with the Davinci update & a driver update (foolish I know...), so those could be confounding factors in figuring out the cause

Ive heard about that, For some reason the latest update really doesn't like this old script.
I now day use some custom tools for these kind of stuff. But your issue here got me to just make a really simple new one that does work in DaVinci Resolve Studio 19.1+ confirmed. And its just an executable to run now. Nothing else and works for more than 1000 images for sure.
Linked here:
https://github.com/VilleOlof/resolve_clipboard
Will mark this repository as an archive and link new people over to the link above


How to implement complex SQL functions

How to implement complex SQL functions similar to the following
type TransactionRecord struct {
	ID        uint64
	AccountID string
	TCode     string
	TDate     string
	TType     uint8
	Amount    float64
}

var tds []TransactionRecord
t1 := TransactionRecord{ID: 1, AccountID: "A001", TCode: "161700", TDate: "2020-08-01", TType: 17, Amount: 23.0}
t2 := TransactionRecord{ID: 2, AccountID: "A001", TCode: "161700", TDate: "2020-08-01", TType: 17, Amount: 99.0}
t3 := TransactionRecord{ID: 3, AccountID: "A001", TCode: "161700", TDate: "2020-08-01", TType: 17, Amount: 25.0}

t4 := TransactionRecord{ID: 1, AccountID: "A001", TCode: "161700", TDate: "2020-08-01", TType: 24, Amount: 13.0}
t5 := TransactionRecord{ID: 2, AccountID: "A001", TCode: "161700", TDate: "2020-08-01", TType: 24, Amount: 69.0}
t6 := TransactionRecord{ID: 3, AccountID: "A001", TCode: "161700", TDate: "2020-08-01", TType: 24, Amount: 85.0}

t7 := TransactionRecord{ID: 4, AccountID: "A001", TCode: "161700", TDate: "2020-08-02", TType: 17, Amount: 11.0}
t8 := TransactionRecord{ID: 5, AccountID: "A001", TCode: "161700", TDate: "2020-08-02", TType: 17, Amount: 33.0}
t9 := TransactionRecord{ID: 6, AccountID: "A001", TCode: "161700", TDate: "2020-08-02", TType: 17, Amount: 57.0}

tds = append(tds, t1)
tds = append(tds, t2)
tds = append(tds, t3)
tds = append(tds, t4)
tds = append(tds, t5)
tds = append(tds, t6)
tds = append(tds, t7)
tds = append(tds, t8)
tds = append(tds, t9)

I want to implement the following SQL functions, how to write code with go-linq package
select AccountID,TCode, TDate,TType, sum(Amount)  as am from TransactionDetails where TType = 17 or TType = 24 GROUP BY AccountID, TCode,TDate, TType ORDER BY AccountID, TCode,TDate, TType;

I also want to use it like this, sum is in group by

Hey, @penhauer-xiao and @107295472! My apologies for the delay. Here a possible code example for your problem:

Thanks, really strong

thanks @cleitonmarx

fantastic, thanks @cleitonmarx


Invalid numbers parsed

The following invalid Json numbers are parsed as numbers by Boon:
034 parsed as 34, instead is invalid JSON, some other implementations parse it as an octal 28 that is what javascript would do. Same for -034. See http://stackoverflow.com/a/27361596/1536382
0., invalid for JSON, parsed as 0 like javascript would do, note that .0 is treated as an error (also invalid for JSON while for js is also ok), so for consistency also 0. should be, IMHO. If there is a way of doing relaxed-parsing may be both should be allowed in that case.
See also http://deron.meranda.us/python/comparing_json_modules/numbers#t5-3 (today unavailable, cached)
See same issue for genson https://github.com/owlike/genson/issues/111

Thanks.


Provide an easy way to see the public version of MSTest

MSTest dlls do not contain the version under which it is published, which makes it really hard to see what is being used. Here I am using 2.2.9-preview-20220210-07.  I would like to be able to easily see the version in ilspy, and hopefully in file properties as well:

Ideally this would also be accompanied by docs page that lists versions from all the available nugets on nuget.org and their publish version, until we started embedding that data. I can help automating that if you'd like.

I think we started including branch name and commit id in assemblies. Let me verify.

Binaries in the latest preview now contain commit hash as assembly metadata.

Please add the public version, I don’t want to be hunting commit ids to know what version the dll is.

@Evangelink thanks!


infer issue

Traceback (most recent call last):
File "C:\Users\RIS-FC3PF63\Downloads\Sarcasm-Detection-with-BERT-and-GCN-main\Sarcasm-Detection-with-BERT-and-GCN-main\infer.py", line 110, in
t_probs = inf.evaluate(raw_text)
File "C:\Users\RIS-FC3PF63\Downloads\Sarcasm-Detection-with-BERT-and-GCN-main\Sarcasm-Detection-with-BERT-and-GCN-main\infer.py", line 69, in evaluate
t_outputs = self.model(t_inputs)
File "D:\anaconda3\lib\site-packages\torch\nn\modules\module.py", line 1501, in _call_impl
return forward_call(*args, **kwargs)
File "C:\Users\RIS-FC3PF63\Downloads\Sarcasm-Detection-with-BERT-and-GCN-main\Sarcasm-Detection-with-BERT-and-GCN-main\models\bertgcn.py", line 27, in forward
text_bert_indices, bert_segments_ids, dependency_graph, affective_graph = inputs #text_indices,
ValueError: too many values to unpack (expected 4)

Hi @sherifyounis I have fixed the issue. Please verify. Thanks!


fix: Config input name and set kustomize paths

What type of PR is this?

kind/bug
What this PR does / why we need it:

Fixes input name in project trigger script.
Sets kustomize paths for which falco config to apply.

Which issue(s) this PR fixes:

None
Special notes for your reviewer (optional):
CI error is expected because my fork can't access the repo secrets.

Can we merge this?


cross-platform: fix AutoSystemInfo Initialization

AutoSystemInfo class was being initialized before its cross dependencies are able to initialize.
This is a compiler/linker dependent issue, requires that AutoSystemInfo is initialized
at the end of the initializion phase.
Although the problem at hand  was not necessarily requiring a thread safe solution, the one proposed here (static function type of initializer) is thread safe and incredibly liteweight. It does the job by
passing the first __cxx_global_var_init (or similar) phase for its host module.

Overall, looks ok- little confused though, I don't see any use of __cxx_global_var_init - can you explain this part some more please?

I don't see any use of __cxx_global_var_init- can you explain this part some more please?

That refers to i.e. a static object is being initialized at runtime by the order defined by linker/compiler. So you don't directly use it but can observe if you assert/break on an initializing i.e. global variable.

Got it- I thought you were saying that you'd explicitly annotated the static somewhere, understood now.
One thing- the change doesn't guarantee the order of static initialization (the original priority was there basically to make sure that the PAL statics were initialized before AutoSystemInfo). Your solution is to lazily initialize it, which I think should work, but the caveat is, no other static can directly access fields from AutoSystemInfo::Data. On windows, we do explicitly control static variable initialization- might want to leave a comment to make sure that no field should directly be accessed, and every getter should call InitializeOnDemand.

Can we check if there are perf impact?  We may have assumed that these are super lite weight with just a data load, and now there is an extra compare/branch.

Closing this one as #1234 fixes this issue without altering the behavior of AutoSystemInfo


another android app (aYourls)

Hello,
you recently added an android app into the list, but i've found an alternative that supports server url deletion too :D https://apkpure.com/ayourls/de.mateware.ayourls. Saldy it's not on play store anymore but i use and it. It works very well.

Seems to be also available at https://gitlab.com/matecode/ayourls, I'd rather add that link instead of the apkpure one. Fancy a pull request to add it to the list?

PR done.


Restrict permissions further

Is there any reason this is not merged yet @Phu2 ?

Actually not :) Leave it to you.


feat(keychain): allow exporting sodium private keys

Description
Adds a new exportPrivate parameter to the keychain.sodium.getSodiumKeysFromSeed method, similar to what we have forkeychain.exportKey, allowing to export the sodium private keys when that flag is set to true.

@kewde good call, though that will be a breaking change

@mvayngrib how would that be a breaking change?

because secret was always exported before and now only when exportPrivate is true, or did i misunderstand?

because secret was always exported before and now only when exportPrivate is true, or did i misunderstand?
Yes, @kewde if by secret you are referring to this, my PR didn't touch that, it only include private keys for sign and box when exportPrivate is set to true


Dsl1p complex update

Later papers by the same author PMID: 20005800 call this “Dsl1 complex”  and a review PMID: 22486903.
In human it is called NZR complex
also CATCHR family...maybe this could be the term name but I don't know if this covers  other related complexes.
If it does, Dsl1/NZR complex would be clearer, with all other names as synonyms.
NRZ complex comprises NAG, RINT1, and ZW10
members of this complex  appear to have moonlighting function in human PMID: 25364732
and possibly in pombe too (I was puzzliing about this recently but it seems that the moonlighting function are probably conserved, will look into this further as it might be useful for a comment)

Ok, so proposal is this:  Please confirm.

[ ] rename 'Dsl1p complex' term as ' Dsl1/NZR complex'
[ ] add related synonym, Dsl1p complex
[ ] add related synonym, NZR complex
[ ] add related synonym, CATCHR family complex

Here's my understanding of the CATCHR complexes:
The CATCHR family are/include four complexes: Dsl1, COG, GARP, exocyst (also known as the DCGE group). They are multi-subunit tethering complexes which share low sequence identity but conserved helical bundle structures.

That makes sense. So should CATCHR family complex be broad?
I have been listing the tethering complexes here. I wasn't sure which ones were CATCHR
https://github.com/geneontology/go-ontology/issues/12542
So not HOPS/CORVET or TRAPP complex? (also tethering complexes, but maybe different mechanism?)
Note that in GO COG is called
GO:0017119 - Golgi transport complex
COG seems better here (its a synonym)
Also the def says
"In yeast, this complex is called the Sec34/35 complex"
maybe this would be better as a synonym than part of the definitions ( yeast people generally call it COG nowadays?) In fact in pombe and cerevisiae we call the subunits cog1 -cog 8 now....

Hi Tanya,
I'm not sure if
Dsl1p complex and NZR complex are related or exact? ...they are supposedly describing exactly  the same complex, just in different species ?  but in that case should they be exact?

If they are exactly the same complex, same components, just a different species, then Dsl1p and NZR should be exact synonyms.  I'm not sure what you're getting at by adding in information about other complexes.  Do they relate to this term?  If not, please split that out to another ticket for clarity.  Thanks.

I just satisfied myself that these were identical:
So,
Add comment:
Dsl1/NZR complex comprises Hu ZW10 (Sc Dsl1) , Hu RINT1 (Sc Tip20), Hu NBAS (Sc Sec39)
(this comment is useful because the ZW10/Dsl1 orthology won't be picked up between metazoa to fungi by any of the ortholog predictors... I still cant find the pombe subunit....)
current term has this comment:
See also the molecular function term 'acetolactate synthase activity ; GO:0003984'.

[x] rename 'Dsl1p complex' term as ' Dsl1/NZR complex'
[x] add exact synonym, Dsl1p complex
[x] add exact synonym, NZR complex
[x] add broad synonym, CATCHR family complex

Also added 'capable_of_part_of 'vesicle tethering'  => classification under 'vesicle tethering complex'

Could I check if all the CATCHR family complexes going to get the "add broad synonym, CATCHR family complex"? (re:vesicle tethering complexes #12555)


Feature DLUT.RAM not emitted

This issue emerged in the PR https://github.com/SymbiFlow/symbiflow-arch-defs/pull/1502 (SHA c6a66c0) on Murax built for A200T (test tests/9-soc/murax, target murax_nexys_video_100_bit_v).
While decoding the bitstream fasm2bels throws an assertion error meaning that there are LUT RAMs in a SLICEM enabled, but none of them is packed into DLUT hence the DLUT.RAM feature is not set and presumably it should be:
Traceback (most recent call last):
  File "/tmpfs/src/github/symbiflow-arch-defs-presubmit-xc7a200t-vendor/env/conda/envs/symbiflow_arch_def_base/lib/python3.8/runpy.py", line 194, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/tmpfs/src/github/symbiflow-arch-defs-presubmit-xc7a200t-vendor/env/conda/envs/symbiflow_arch_def_base/lib/python3.8/runpy.py", line 87, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/symbiflow-arch-defs-presubmit-xc7a200t-vendor/third_party/symbiflow-xc-fasm2bels/fasm2bels/__main__.py", line 4, in <module>
    main()
  File "/tmpfs/src/github/symbiflow-arch-defs-presubmit-xc7a200t-vendor/third_party/symbiflow-xc-fasm2bels/fasm2bels/fasm2bels.py", line 416, in main
    process_tile(top, tile, tile_features)
  File "/tmpfs/src/github/symbiflow-arch-defs-presubmit-xc7a200t-vendor/third_party/symbiflow-xc-fasm2bels/fasm2bels/fasm2bels.py", line 103, in process_tile
    PROCESS_TILE[tile_type](top.conn, top, tile, tile_features)
  File "/tmpfs/src/github/symbiflow-arch-defs-presubmit-xc7a200t-vendor/third_party/symbiflow-xc-fasm2bels/fasm2bels/models/clb_models.py", line 1218, in process_clb
    process_slice(top, slices[s])
  File "/tmpfs/src/github/symbiflow-arch-defs-presubmit-xc7a200t-vendor/third_party/symbiflow-xc-fasm2bels/fasm2bels/models/clb_models.py", line 528, in process_slice
    assert not site.has_feature('{}LUT.RAM'.format(row))
AssertionError

Now, the comment in the architecture definition file for SLICEM says that whenever any LUT RAM is used in a SLICEM the DLUT.RAM feature should be set. But that's done only for the DRAM128 mode that uses the whole SLICEM, not for any other. The comment:
      <!-- The DLUT must be in RAM-mode for any of the RAM's to work.
           As a corollary, a DRAM requires the clock, so only turn on the
           DRAM if the clock is also connected.
      -->

So in the end VPR packs 2 LUT RAMs into ALUT and BLUT thus the DLUT.RAM feature is not set. It it unclear whether this behavior is correct or not (haven't check if the design works on HW). Configuration of the particular SLICEM (as emitted by VPR) looks like that:
CLBLM_L_X60Y118.SLICEM_X0.AOUTMUX.A5Q
CLBLM_L_X60Y118.SLICEM_X0.COUTMUX.O5
CLBLM_L_X60Y118.SLICEM_X0.FFSYNC
CLBLM_L_X60Y118.SLICEM_X0.DFFMUX.DX
CLBLM_L_X60Y118.SLICEM_X0.A5FFMUX.IN_B
CLBLM_L_X60Y118.SLICEM_X0.A5FF.ZRST
CLBLM_L_X60Y118.SLICEM_X0.A5FF.ZINI=1'b0
CLBLM_L_X60Y118.SLICEM_X0.DFF.ZRST
CLBLM_L_X60Y118.SLICEM_X0.DFF.ZINI=1'b0
CLBLM_L_X60Y118.SLICEM_X0.CLUT.INIT[31:0]=32'b11001100000000001100110000000000
CLBLM_L_X60Y118.SLICEM_X0.CLUT.INIT[63:32]=32'b10000000100000001111111111111111
CLBLM_L_X60Y118.SLICEM_X0.BLUT.DI1MUX.BI
CLBLM_L_X60Y118.SLICEM_X0.BLUT.RAM
CLBLM_L_X60Y118.SLICEM_X0.BLUT.INIT[63:0]=64'b0000000000000000000000000000000000000000000000000000000000000000
CLBLM_L_X60Y118.SLICEM_X0.ALUT.DI1MUX.BDI1_BMC31
CLBLM_L_X60Y118.SLICEM_X0.ALUT.RAM
CLBLM_L_X60Y118.SLICEM_X0.ALUT.INIT[63:0]=64'b0000000000000000000000000000000000000000000000000000000000000000
CLBLM_L_X60Y118.SLICEM_X0.WEMUX.CE

I think we can just add the fasm_mux from https://github.com/SymbiFlow/symbiflow-arch-defs/blob/f0e7b4212544e1d55da776fb7a2ff79117e01454/xc/common/primitives/slicem/slicem.pb_type.xml#L847-L855 and comment to the
"DRAMs" mode, and this should be fixed.  It isn't an ideal packing, but it should be legal.  @mkurc-ant / @acomodi Could you test this?  I won't be able to get to this until next Tuesday.

Fixed in #1629


Fix CI

Describe what this PR does and why we need it:

Fix build of the image
Fix go vet

Changes proposed in this pull request
$ docker build -f  build/custom-ci-build-root.Dockerfile .
Sending build context to Docker daemon  206.3MB
Step 1/4 : FROM openshift/origin-release:golang-1.12
 ---> c6a41783d3ef
Step 2/4 : RUN yum install -y epel-release     && yum install -y python-devel python-pip gcc
 ---> Using cache
 ---> 3fe44eaf9581
Step 3/4 : RUN pip install -U setuptools wheel && pip install -U more-itertools==7.0.0 molecule==2.20.0 jmespath openshift
 ---> Using cache
 ---> fca57e14583c
Step 4/4 : RUN chmod g+rw /etc/passwd
 ---> Running in d1e6bfdd9884
 ---> 8211e08223d9
Removing intermediate container d1e6bfdd9884
Successfully built 8211e08223d9

Does this PR depend on another PR (Use this to track when PRs should be merged)
depends-on
Which issue this PR fixes (This will close that issue when PR gets merged)
Collecting more-itertools>=4.0.0 (from pytest!=3.0.2->testinfra==1.19.0->molecule==2.20.0)
  Downloading https://files.pythonhosted.org/packages/a0/47/6ff6d07d84c67e3462c50fa33bf649cda859a8773b53dc73842e84455c05/more-itertools-8.2.0.tar.gz (82kB)
    Complete output from command python setup.py egg_info:
    /usr/lib/python2.7/site-packages/pkg_resources/py2_warn.py:21: UserWarning: Setuptools will stop working on Python 2
    ************************************************************
    You are running Setuptools on Python 2, which is no longer
    supported and
    >>> SETUPTOOLS WILL STOP WORKING <<<
    in a subsequent release (no sooner than 2020-04-20).
    Please ensure you are installing
    Setuptools using pip 9.x or later or pin to `setuptools<45`
    in your environment.
    If you have done those things and are still encountering
    this message, please follow up at
    https://bit.ly/setuptools-py2-warning.
    ************************************************************
      sys.version_info < (3,) and warnings.warn(pre + "*" * 60 + msg + "*" * 60)
    Traceback (most recent call last):
      File "<string>", line 1, in <module>
      File "/tmp/pip-build-C67ASH/more-itertools/setup.py", line 5, in <module>
        from more_itertools import __version__
      File "more_itertools/__init__.py", line 1, in <module>
        from .more import *  # noqa
      File "more_itertools/more.py", line 480
        yield from iterable
                 ^
    SyntaxError: invalid syntax

    ----------------------------------------
Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-build-C67ASH/more-itertools/
You are using pip version 8.1.2, however version 20.0.2 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
subprocess exited with status 1
subprocess exited with status 1
error: build error: error building at STEP "RUN pip install -U setuptools wheel && pip install -U molecule==2.20.0 jmespath openshift": exit status 1
2020/03/27 12:33:42 No custom metadata found and prow metadata already exists. Not updating the metadata.
2020/03/27 12:33:43 Ran for 3m55s
2020/03/27 12:33:43 Submitted failure event to sentry (id=a5d92d21b2b84513b21ff809333b586b)
error: could not run steps: step root failed: could not wait for build: the build root failed after 3m49s with reason DockerBuildFailed: Dockerfile build strategy has failed.

You are using pip version 8.1.2, however version 20.0.2 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
subprocess exited with status 1
subprocess exited with status 1
error: build error: error building at STEP "RUN pip instal...tall -U molecule==2.20.0 jmespath openshift": exit status 1

Force merging this to fix the CI builds.


Seek feedback from AWS experts

I'm not an AWS expert. I would feel a lot more comfortable if some AWS experts could review this tool and make sure that what it is doing makes sense and there are no unpleasant flaws in the approach it is taking.

 IAM is part of my daily life.
My suggestions:

specify individual actions explicitly (no wildcards)
separate permissions by resource (Buckets vs. Objects)
Sid is unnecessary

Your read/write policy is good, but instead of *Object, list GetObject and PutObject.
Your read-only policy would be better written like your read/write policy, one section for the bucket permission (ListBucket), one for the object permission (which should be GetObject, no wildcard).
Your write-only policy is great as is.
You may want to add additional permissions to let clients set ACLs. But if it's all simple object-by-object stuff, these very simple policies are great.

This is fantastic, thank you!

The thing I need the most help with now is deciding whether or not to use action wildcards and - if not - which S3 action should go in the list for read-only and for read-write, see:

#15

I implemented --policy custom-policy.json to allow people to apply entirely custom policies in:

#14

First off, thanks for making this tool! AWS is daunting for the uninitiated and tools that simplify common AWS tasks are very helpful.
I second @jdub's suggestions with a few of my own:

An optional flag for attaching bucket policies to the new s3 bucket. These are just like IAM user policies, but attached to the bucket itself.
Enable Server Side Encryption with AWS S3-Manged-Keys by default
Require a flag to enable public access to the bucket rather than making the bucket public by default. See docs
Flag for setting canned ACL policies

Also, take a look at the s3 security best practices in the official docs.

@zacaytion these are really great suggestions, thank you. Will split these out into separate issues.

Enable Server Side Encryption with AWS S3-Manged-Keys by default

I researched this in #18 but as far as I can tell there isn't a bucket-level way of saying "encrypt all contents in this bucket" - you need to include the x-amz-server-side-encryption: AES256 header every time you upload an object. You can add a policy to the bucket that rejects uploads that don't use that header, but that's a bit of a weird workaround.
So I'm considering that out-of-scope for this tool, though users can set their own custom policies for this (especially if I allow custom bucket policies in #19).

I am by no means an AWS expert! However, I must confess that I was expecting the user created for this s3 bucket to have permission to access only that bucket. Instead, the user's permissions allow access to any s3 bucket in the account. Is there a reason for this?

I think fundamentally, this project could be split into two pieces. The part that manages bucket and principal policies for access to S3 is really useful. The part that provisions long-term credentials via IAM Users is something I'd like to discourage. In general, long-term credentials are only appropriate when there is no trusted source of identity that can be relied on.
For your local dev machine, you (a human) are the source of identity. IAM Identity Center (formerly AWS SSO) provides the best way to have AWS credentials on behalf of a human. Log in once per day, and your tools get access to short-lived AWS credentials.
For something like an EC2 instance, AWS is the trusted source of identity, and can provide short-lived credentials by giving the instance an IAM role.
For something like GitHub Actions, the provider is a trusted source of identity, and you can use the GitHub OIDC token provided to an action to assume an IAM role, giving the action short-lived AWS credentials with no secrets embedded in your action at all, see https://github.com/aws-actions/configure-aws-credentials
If you're running an automated process on, say, a server sitting under your desk at home, that's the case where you don't have a trusted source of identity, and you end up needing long-term credentials of some kind. But because this should be the exception rather than the rule, placing IAM user creation as the default, central part of this tool is a mistake imo.

I built this tool because I have a whole bunch of cases where I've needed to create long-term IAM credentials for accessing an S3 bucket, where the STS route isn't applicable.
All of these are things I've run into:

Running Transmit on my Mac laptop to upload files to a bucket
Backup scripts running on a Digital Ocean machine in a cron
An application deployed to Vercel which needs to pull images from a private S3 bucket, then resize and serve them: https://github.com/simonw/s3-image-proxy
The "machine under my desk" case - a machine in my home that backs things up to S3

And now a confession: I would like to use OIDC for my GitHub Actions (I use long-term credentials for those instead a the moment). But I've read that GitHub OIDC documentation multiple times and it utterly befuddles me - I cannot figure it out!
I swear OIDC between GitHub and AWS is one of the hardest problems in computer science. I really, really wish someone would turn that into a sequence of steps that I can follow. I used to feel ashamed about this, but I think it's a case where it's not me, it's them.


Timer (and maybe other stuff) falls over when Facebook is down

Today is the day of the Great Facebook Outage of 2021, and the MHCT extension (Firefox) has stopped running the timer because of "cannot contact server". The timer part should work even if mhg is the only thing online.

Transferred issue to extension repo. good point. I'm assuming MH was still working? I don't see any dependencies in the extension that  are not included in the extension itself. Especially for popup page.

MH page has to be open and loaded in the same browser window I believe. But that's the only dependency

I would suggest playing on https://www.mousehuntgame.com instead of facebook, if facebook is having issues. The game itself might have some dependencies on fb, but the extension doesn't. In fact i'm using it with an ad blocker that blocks facebook, and it seems to work just fine. I'll close this for now, but if you notice it again on the https://www.mousehuntgame.com, let me know, and i'll reopen.


Config search to not ignore dots

I have field with ip address like '<IP_ADDRESS>' and Mongoid::Search create one keyword only '10'. How to tune search to ignore dots ?

Probably a bug, feel free to PR.

@dblock https://github.com/mongoid/mongoid_search/blob/master/lib/mongoid_search/util.rb#L44
Seems strip just ignored some symbols, what about to make this configurable ?

I've the same issue with dates like 2017-08-10 which are considered "2017", "08", "10" while it's supposed to be a complete date search.
@sveredyuk have you fixed this issue on your own ?

@Loschcode Yeah, I have to monkey-patch this gem)
# Mogoid::Search Overwrite
module Mongoid::Search::Util
  def self.normalize_keywords(text)
    ligatures     = Mongoid::Search.ligatures
    ignore_list   = Mongoid::Search.ignore_list
    stem_keywords = Mongoid::Search.stem_keywords
    stem_proc     = Mongoid::Search.stem_proc

    return [] if text.blank?
    text = text.to_s.
      mb_chars.
      normalize(:kd).
      downcase.
      to_s.
      gsub(/[_:;'\"`,?|+={}()!@#%^&*<>~\$\-\\\/\[\]]/, ' '). # strip symbols
      gsub(/[#{ligatures.keys.join("")}]/) {|c| ligatures[c]}.
      split(' ').
      reject { |word| word.size < Mongoid::Search.minimum_word_size }
    text = text.reject { |word| ignore_list.include?(word) } unless ignore_list.blank?
    text = text.map(&stem_proc) if stem_keywords
    text
  end
end

module Mongoid::Search
  def set_keywords
    self._keywords = Mongoid::Search::Util.keywords(self, self.search_fields)
      .flatten
      .reject{|k| k.nil? || k.empty?}
      .push(*self.search_fields)
      .flatten.map(&:to_s).uniq.sort
  end
end

@sveredyuk I actually didn't expect any answer so I went forward and made a fork earlier today ; to add a configuration option and slightly change the structure of what you kinda monkey patched on your end.
Thanks for your solution though ;)
https://github.com/Loschcode/mongoid_search
I'll make a pull request, might not suit everyone but it works in production for me.

Pull request https://github.com/mongoid/mongoid_search/pull/110

my pr is waiting more than half a year - https://github.com/mongoid/mongoid_search/pull/108

I've the feeling we will both wait for a while then, ouch

We need more maintainers for this repo, @sveredyuk @Loschcode you guys volunteer?
@mauriciozaffari is the sole owner of this right now, ping?

I opened https://github.com/mongoid/mongoid_search/issues/111 to discuss ownership.


fix cuda warning

I see this error message when compiling with nvcc 7.5

Can one of the admins verify this patch?

Please verify that this doesn't break nvcc 7.0 and we'll re-open, thanks!


Datasplash post

Here's my stab at describing how the experience of using Datasplash in production has been.

Fixed the typos

:shipit:

Is the text _really_ supposed to decrease in size like this?

@larsbkrogvig I was just assuming that was caused by the differences in Github Markdown processor and Jekyll. We're using Jekyll(?) on github-pages and I'm assuming @torbjornvatn has checked it locally that it doesn't get smaller and smaller

As glitches go, it was a pretty funny one.

@larsbkrogvig no worries, it looks good in real (virtual) life


Landing Page

I am new to react js and i want to do a landing page.
Currently we have the APP that points to the Routes (dashboard)
        <StyledEngineProvider injectFirst>
            <ThemeProvider theme={theme(customization)}>
                <CssBaseline />
                <NavigationScroll>
                    <Routes />
                </NavigationScroll>
            </ThemeProvider>
        </StyledEngineProvider>

How can we have a landing page that will have the register/login and after that can redirect to the dashboard? Thank you

With the free version, the app will land to the dashboard. If you want to go to login first, you need to implement route guards. Route Guard will check if the user login or not and based on that redirect to the proper path. You may need to implement two route guard, Guest and Auth.

Please create a separate issue for this.


Rename the repos to shorter versions?

The org and repo together are very long, and email notifications have no useful title on mobile because of that.
I wonder if they can't be renamed to stld-cmps/stld-cmps or even s-c/s-c?
Just wondering out loud :)

Probably not :blush:

Agreed, styled-components has become a “household name” and at this point it’d be disastrous to go for a hackt workaround to shorten the name :/


deps: Bump to go 1.21

Description
Go 1.19 is EOL since August 10th.

Test

CI
Additional Information
Tradeoff

Potential improvement

this is on top of https://github.com/kubewarden/audit-scanner/pull/109, because I bumped golangci-lint there, and this needs it.

rebased and merged via GH


When using my own data for training, the first epoch reached an IOU value of over 0.9. May I ask if there is a problem? The data is 5000

When using my own data for training, the first epoch reached an IOU value of over 0.9. May I ask if there is a problem? The data is 5000

what's the IoU if directing using SAM w/o training?


Force news hubs links to open in default OS browser

Fix the underlying issue preventing links opening correctly in #3262
This PR doesn't add a setting to control it, I assume everyone want the links to open in the OS browser.

@Sheikah45 Mutation observer works nicely to fix any links added to the page
Unsure but perhaps there is still a concern with a race condition between the java code and the js hook? Where a link can get added after the java code runs but before mutation observer is added.

@Sheikah45 Mutation observer works nicely to fix any links added to the page
Unsure but perhaps there is still a concern with a race condition between the java code and the js hook? Where a link can get added after the java code runs but before mutation observer is added.

The race condition concern would be fixed by first adding the mutation observer and then going through and changing all the links already added to the page. This would guarantee that all the links are set since we observe and then change the preexisting ones.

We could also prevent the race condition by writing the logic to handle pre-existing links in the js script


New feature: copy/initialize a file instead of linking

The problem
With the current capabilities of dotbot, I can have a ~/.vim/vimrc file in my dotfiles, and dotbot will correctly create the link. Inside that file, I am sourcing another file ~/.vimrc/vimrc-local, which should contain local changes that should not be stored in the dotfiles. So far, so good.
However, the tricky part is initializing the -local file. It should have a certain structure, it should declare a few functions. In other words, there is some boilerplate it should have.
The proposed solution
I am proposing a new directive: skel (or initialize or seed or copy or copy_without_overwriting or… well, naming is hard!)
It would be declared in a similar way to the link directive, but instead of creating a symlink, it would just copy the file over there. Look:
- link:
    '~/.vim/vimrc': 'base/.vim/vimrc'
- skel:
    '~/.vim/vimrc-local': 'base/.vim/vimrc-local'

On a fresh machine, the outcome would be:

~/.vim/vimrc → ~/dotfiles/base/.vim/vimrc (symlink)
~/.vim/vimrc-local (regular file, copied from ~/dotfiles/base/.vim/vimrc)

On subsequent runs on the same machine:

~/.vim/vimrc → ~/dotfiles/base/.vim/vimrc (the tool ensures the symlink is still correct)
~/.vim/vimrc-local

If it still exists, it is not touched at all. It is assumed to have local changes.
If it doesn't exist, it is recreated (copied) from ~/dotfiles/base/.vim/vimrc

The proposed behavior reminds me of /etc/skel/.
Additional configuration
Maybe the name should be copy, and it should have the same configuration keys as link:

path
create parent directories as needed.
relink not relevant.
force overwrites the existing file. Dangerous, should be off by default, but maybe useful in some exotic configuration. (e.g. A separate YAML config could be used to "reset" a certain application configuration to a known state.)
canonicalize, if, ignore-missing
glob, exclude, prefix

Alternatives

I keep the -local file in my dotfiles, and I have to remember to copy/create it manually.
I keep the -local file in my dotfiles, and I add some custom shell directive to copy only if it doesn't exist.
I can keep different versions of -local, one for each machine. Many people do that, but it is not desirable for files that contain sensitive information (such as API keys or tokens).
Templating as requested in #117. It has the same drawbacks as alternative 3, plus the additional complexity of requiring additional Python modules.

Compared to the alternatives, the skel/copy solution has the following advantages:

Automatic, I don't have to remember to copy it manually.
Clean configuration. I don't have to write shell script code inside an YAML file.
Easy to learn and easy to understand, as it is very similar to link.
Simple to implement, can be implemented using the standard library, should require no additional modules. In fact, most of the behavior would be identical to link.

Nice suggestion! I'm currently doing this with my shared git config:
- shell:
    - description: "Copy shared/git/gitconfig.ini to ~/.gitconfig (if needed)"
      command: >
        if [ ! -e ~/.gitconfig ]; then
            cp shared/git/gitconfig.ini ~/.gitconfig;
        fi
      quiet: true

A copy directive might be just the ticket in this situation.


Balancer v1 classifier / abis

Initial Balancer v1 classifier.
Spot checked against mev-inspect-rs and picks up all the same trades.
Have not yet integration tested with arbitrage logic, that'll come in a later commit.

This looks super solid! Love the the tests!

Thanks for the PR @sragss! This looks great. Unit tests are 🔥


Remove mentions to beta in ddc

Deploy preview ready!
Built with commit e13fa53e95dc01e99cd40f5043ac0b8001ad726d
https://deploy-preview-574--docker-docs.netlify.com