SIGSEGV in digiKam 7.9.0

Describe the bug
I have recently noticed digiKam crashing. Did a sysupgrade to confirm.
It (at least) crashes when trying to save a face tag, but also simply displaying --help or --version (which is worrying)
Steps To Reproduce
Steps to reproduce the behavior:
❯ digikam --version
digikam 7.9.0
fish: Job 1, 'digikam --version' terminated by signal SIGSEGV (Address boundary error)

Expected behavior
No crash :slightly_smiling_face:
Additional context
Apparently this has not always been the case, I have two other versions of digiKam 7.9.0 on my system from previous generations, one of which does not segfault:
❯ /nix/store/cx88i17h9pf9baigv732znslwsldyxiz-digikam-7.9.0/bin/digikam --version # current
digikam 7.9.0
fish: Job 1, '/nix/store/cx88i17h9pf9baigv732…' terminated by signal SIGSEGV (Address boundary error)

❯ /nix/store/056pi3s2samjj065prdgqfcmiffix190-digikam-7.9.0/bin/digikam --version
digikam 7.9.0
fish: Job 1, '/nix/store/056pi3s2samjj065prdg…' terminated by signal SIGSEGV (Address boundary error)

❯ /nix/store/c05y2qz0bij8q4z70kqb2b732hd9lr7l-digikam-7.9.0/bin/digikam --version
digikam 7.9.0

Notify maintainers

@Atemu @fabianhjr you have the last commit which touched this derivation, which happened post update to 7.9.0
Metadata
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.1.25-xanmod1, NixOS, 23.05 (Stoat), 23.05pre477241.c8018361fa1`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.13.3`
 - channels(root): `"home-manager, nixos"`
 - channels(user): `""`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

Can reproduce issue on current staging-next
digikam --version                                                  Wed 26 Apr 2023 03:30:30 PM CST
digikam 7.9.0
fish: Job 1, 'digikam --version' terminated by signal SIGSEGV (Address boundary error)

However application launches and runs correctly. :O

7.10.0 has been released with the following note:
See below a list of major improvements included in this release:

    Fix crashes with last OpenCV 4.7.0

and this is currently built with opencv 4.7.0

Even after upgrade the issue remains.
digikam --version                                                               984ms  Wed 26 Apr 2023 03:52:09 PM CST
digikam 7.10.0
fish: Job 1, 'digikam --version' terminated by signal SIGSEGV (Address boundary error)

Can reproduce issue on current staging-next
digikam --version                                                  Wed 26 Apr 2023 03:30:30 PM CST
digikam 7.9.0
fish: Job 1, 'digikam --version' terminated by signal SIGSEGV (Address boundary error)

However application launches and runs correctly. :O

What do you mean by correctly? Mine still launches and runs, but spits a SIGSEGV on quit, and sometimes crashes (when saving face tags as mentioned)

Crash on face tags might be related to the item mentioned on the 7.10.0 changelog.
I meant the same ("launches and runs but spits a SIGSEGV on quit")

No crashes (neither face tags nor cli) on ba2f6a3aa27aef45d876758891dae8ad387ea68f

Even after upgrade the issue remains.
digikam --version                                                               984ms  Wed 26 Apr 2023 03:52:09 PM CST
digikam 7.10.0
fish: Job 1, 'digikam --version' terminated by signal SIGSEGV (Address boundary error)

Really? I just tested commit 1e07e5480d8fceac95be7eaaced4885d1859ed85 from your PR #228408 and I don't have any crash or error anymore

Crash might have been related to OpenCV 4.7.0, that upgrade would have happened after the original digikam 7.9.0 version upgrade.


Fix llvm-cm tests against recent LLVM

Bumping to a recent LLVM version causes the LLVM tests to fail. This patch updates the tests and makes them slightly more resilient against small changes.

I think this one needs some more investigating. It looks like one of the expected outputs is off by a good bit, and we would want to pin the LLVM version to one where things work as intended (like #158 does for the CI with the version in WORKSPACE).
For what it's worth, some git bisect run-ing tells us that the LLVM commit that broke the tests was ea222be0d9266d9d5c100496f8c9606f213454ee.

I think this one needs some more investigating. It looks like one of the expected outputs is off by a good bit, and we would want to pin the LLVM version to one where things work as intended (like https://github.com/google/gematria/pull/158 does for the CI with the version in WORKSPACE).

We can't just pin the LLVM version to one where things work as expected. That prevents us from importing the code into google3 (at least without test failures) as the LLVM version there essentially tracks ToT, so we need to try and follow close to ToT externally.

I think this one needs some more investigating. It looks like one of the expected outputs is off by a good bit, and we would want to pin the LLVM version to one where things work as intended (like https://github.com/google/gematria/pull/158 does for the CI with the version in WORKSPACE).

For what it's worth, some git bisect run-ing tells us that the LLVM commit that broke the tests was ea222be0d9266d9d5c100496f8c9606f213454ee.
Thanks for the git bisect. Based on that commit, the changes are pretty likely to be noise. Given that .p2align expands differently, some difference in the counts is expected.
The tests need to be rewritten at some point to not just contain a dump of assembly so that they vary less from changes like this. I think IR with profile metadata would be the optimal choice but rewriting them has been low priority.

We can't just pin the LLVM version to one where things work as expected. That prevents us from importing the code into google3 (at least without test failures) as the LLVM version there essentially tracks ToT, so we need to try and follow close to ToT externally.

I'm rather for pinning the version:

When we pin, we might be lagging behind LLVM head a bit, but at least we can always have CI passing, and a project that builds.
Without it, our build and CI might get broken by random (well meaning) changes in LLVM and we'd only find out when the project doesn't work. Which means that it can block others from working, add noise to CI, ...
Even if we pin, it doesn't mean that we need to stay on one version for too long, we can continuously keep moving forward similarly to what google3 does. But we'd be doing it in a controlled manner (1) when someone has time to work on broken tests, and (2) while keeping our CI status green.

For what it's worth, some git bisect run-ing tells us that the LLVM commit that broke the tests was ea222be0d9266d9d5c100496f8c9606f213454ee.
Thanks for the git bisect. Based on that commit, the changes are pretty likely to be noise. Given that .p2align expands differently, some difference in the counts is expected.
The tests need to be rewritten at some point to not just contain a dump of assembly so that they vary less from changes like this. I think IR with profile metadata would be the optimal choice but rewriting them has been low priority.

When merging, please add all this info to the commit message for the record.

I'm rather for pinning the version:

My last response I guess misses this a bit. I'm definitely for pinning here, just trying to point out that we do need to roll past any breaking changes to keep the google3 import working.

When we pin, we might be lagging behind LLVM head a bit, but at least we can always have CI passing, and a project that builds. Without it, our build and CI might get broken by random (well meaning) changes in LLVM and we'd only find out when the project doesn't work. Which means that it can block others from working, add noise to CI, ...

Yep.

Even if we pin, it doesn't mean that we need to stay on one version for too long, we can continuously keep moving forward similarly to what google3 does. But we'd be doing it in a controlled manner (1) when someone has time to work on broken tests, and (2) while keeping our CI status green.

I think we're all on the same page here. I just need to state my thoughts a little bit more clearly next time.


updates to scikit-fmm cause errors with poreture

Updated scikit-fmm now returns an error for the kline_vessel demo:
File "test_vessel.py", line 22, in
[extracted_centerline, final_march] = kline_vessel(a, root_location, min_branch_to_root=mbtr_to_pass)
File "/path_to_code/poreture-master/poreture/extract_centerline.py", line 185, in kline_vessel
weighted_travel_time = skfmm.travel_time(phi, weighted_speed)
File "/path_to_python/python2.7/site-packages/skfmm/pfmm.py", line 173, in travel_time
int(self_test), TRAVEL_TIME, order, narrow, periodic)
RuntimeError: Negative discriminant in time marcher quadratic.

scikit-fmm version 0.0.8 works


Add support for collections

I really enjoy your source api, super easy to use!
Currently I'm using categories but I wish I could use collections instead. Categories feature way to much images and not all off them fit nicely together. Therefore, I would love to use curated collections like Cabin Life etc. .

@Pczek Great suggestion, we're definitely working on bringing that out :)
As soon as collections is supported by the JSON API (unsplash.com/documentation), then we'll update Unsplash Source to support it, and then update Unsplash Source JS to support that.
Collections support on the JSON API will be out in the next few weeks, as soon as collections is publicly available.


validate_db_name error

with mongoid 2.0.0rc7 (but even with previouses rc: i tried to downgrade) i receive this error:
(rails/gem dir)/mongo-1.2.0/lib/mongo/util/support.rb:50: in 'validate_db_name': db_name must be a String or Symbol (TypeError).

just a query is executed:
admin['$cmd'].find({:ismaster=>1}, {}).limit(-1)

My yml file is fine, i even rebuilt it with rails g mongoid:config, i then started a new empty app to try if something was wrong with my system: same error.
I then tried mongo_mapper, and everything works with it. Seems something is wrong with mongoid... does anyone have this problem? Any tip on how to solve it?

The actual problem is with the rubygem in ruby 1.9.2 Here is the reason http://redmine.ruby-lang.org/issues/show/4300

Came across this via Google as I have this issue with mongoid 2.2.4 and Rails 3. Big thanks to @ricny046 - you nailed it man!

This is happening to me. Very sudden, don't know what changed but my nightly task is suddenly failing for an error in validate_db_name in support.rb. Doesn't look like a mongoid error to me but this comes up in the google search so it seems like it would be helpful to have here. My mongo db has 4 databases:
thedb_dev
thedb_test
local	(empty)
test	(empty)
But when I put a puts inside that validate method I see:
db name is: "admin"
db name is: "admin"
db name is: nil
and then it fails.
My mongoid.yml hasn't changed in 2 weeks, the nightly task has been running fine for that time. All my mongoid.yml entries look like:
development:
host: localhost
database: thedb_dev
etc...
Changing to the syck parser didn't help.


Specify encodings for materialised tables on Redshift

Feature description
My materialised tables are created with pretty good defaults -- no encoding for sort keys, lzo for everything else -- but I'd like to switch to zstd, and perhaps provide my own per-column settings.
Basic approach: Specify a single encoding for unsorted columns.
Advanced approach: Specify an encoding for individual columns, perhaps falling back to a default.
Who will this benefit?
Redshift users who want to customise their data encoding. I'd hope that'd be a lot of dbt users!

hey @jdub! Thanks for creating this issue. I want to document my thinking around 1) why this doesn't exist already and 2) how we could make it happen in the future.

Why this doesn't exist already

dbt uses create table as (...) statements to build tables in Redshift. These statements don't support the specification of column encodings, so we'd need to create an empty table with the proper encodings, then insert into it inside of dbt.
Creating this empty table from DDL has always been problematic in dbt, as we don't really have a good place to put this DDL code. Moreover, I'd argue that dbt exists to help mitigate the need for actually writing DDL! These days, I consider "needing to care about column encoding" a limitation of Redshift, rather than a feature.

How we could build this

The new v2 schema.yml files support column specifications. I think there might be an opportunity to augment these schema specs with things like column types and encodings. dbt could then use the schema spec for a model, coupled with model configs (like sort/dist keys) to generate the DDL for a table. It could run this DDL, then use the model SQL to insert into the table.
I like that this approach doesn't force users to write DDL directly, but I fear it might be a little bit constraining. There are heaps of other table DDL options, like foreign keys / unique keys / etc, that I don't have a ton of interest in supporting in dbt. It's just not the right tool for that particular job.
So, it could be that the better option is to to just allow users to write their own DDL.

Regarding some specific things you mentioned in the issue:

Basic approach: Specify a single encoding for unsorted columns.
You have to set encodings for all columns at once, when the table is created, so I don't think there's a way to make this happen

Advanced approach: Specify an encoding for individual columns, perhaps falling back to a default.

We could probably do this with the schema.yml approach

Definitely keen to hear your thoughts here!

Aha! The schema.yaml approach would suit this very nicely, deferring to #582 for more advanced requirements.

I'm going to close this - until Redshift provides a mechanism for configuring column encodings in a create table as statement, we don't have any real options here. An enumeration of all the columns, types, and encodings for a table is antithetical to how dbt fundamentally operates

closing (again) in favor of https://github.com/fishtown-analytics/dbt/issues/1438

In my experience the workflow in Redshift to add compression to an existing table is to rename that table, make a new table with desired encodings, then insert the data from the previous table to the new table, then drop the previous table.
In my dbt setup my biggest models are also incremental models.
In theory, I can sneak into Redshift, run the above operation on my already-existing incremental tables, and then as long as the table isn't dropped or a --full-refresh is run, the table keeps my compression. (Right?)
Is it possible to integrate the above steps into the dbt job as some sort of post-hook that only runs after --full-refresh on an incremental model? I believe this would cover most of the use cases for compression, as the models most needing compression are generally the models who also most need incremental updates.
Apologies if this is already possible, as I am far from a dbt expert!

hey @dataxpress - check out this macro. It implements something like what you're describing, using analyze compression to find optimal encodings. To be very honest, I haven't run that code in a long time, but it definitely worked in the past :)
I'd either invoke this macro from a post-hook (checking the flags.FULL_REFRESH flag) or use an "operation" to invoke this macro for particular models on an as-needed basis. Hope this helps!


Fix | Allow non-conformity upon init

What?

Some layers' keys add a -dr to the layer name, since they are disaster recovery layers, make the layout validation account for that.
No halt initialization when layout validation fails, simply warn the user and give a little time to cancel the operation.

Output looks like this during init on a disaster recovery layer:
leverage tf init
[15:44:09.892] INFO     Checking environment name definition in account.tfvars...
[15:44:09.903] INFO     ✔ OK

[15:44:09.907] INFO     Checking backend key...
[15:44:09.908] INFO     Found: 'apps-devstg/security-keys-dr/terraform.tfstate'
[15:44:09.909] INFO     ✔ OK (Seems to be a disaster recovery layer.)

[15:44:09.910] INFO     Checking backend.tfvars:

[15:44:09.912] INFO     Checking if profile starts with bb-apps-devstg...
[15:44:09.913] INFO     ✔ OK

[15:44:09.914] INFO     Checking if bucket starts with bb-apps-devstg...
[15:44:09.915] INFO     ✔ OK

[15:44:09.916] INFO     Checking if dynamodb table starts with bb-apps-devstg...
[15:44:09.917] INFO     ✔ OK
...

Ouput looks like this on an non confoming layout:
leverage tf init
[15:47:33.377] INFO     Checking environment name definition in account.tfvars...
[15:47:33.387] INFO     ✔ OK

[15:47:33.390] INFO     Checking backend key...
[15:47:33.391] INFO     Found: 'apps-devstg/security-keys-disasterrecovery/terraform.tfstate'
[15:47:33.393] INFO     Expected: 'apps-devstg/security-keys/terraform.tfstate'
[15:47:33.394] ERROR    ✘ FAILED

[15:47:33.396] INFO     Checking backend.tfvars:

[15:47:33.397] INFO     Checking if profile starts with bb-apps-devstg...
[15:47:33.398] INFO     ✔ OK

[15:47:33.400] INFO     Checking if bucket starts with bb-apps-devstg...
[15:47:33.401] INFO     ✔ OK

[15:47:33.404] INFO     Checking if dynamodb table starts with bb-apps-devstg...
[15:47:33.405] INFO     ✔ OK

[15:47:33.406] WARNING  ‼ Layer configuration doesn't seem valid. Proceed with caution.

^C
Aborted!


How to modify audio input received?

I would like to modify the audio input, but I'm very new to flutter and have no idea how to start.

WDYM? What would you like to modify?


Won't share items

My poshwar bot is running fine but for some reason it is "sharing 0 items in closet". Is there a parameter or line of code that I have to change telling it how many active items I have in my closet. 7 scrolls(the default) should be enough to at least get through most of my items. It seems like it tries to open my closet and then the browser shuts down.

Hi there, looks like you might have your email address where your closet name should be. Try updating your credentials.py to include your closet name rather than your login email.

@Joel0420, I would agree with @nicolealaine. Your credentials file should have your poshmark username (closetname). See the README. The code uses the closet name in the credentials.py file (or the passed alternate account name) and navigates to that page using the following function:
def get_seller_page_url(poshmark_account):
    url_stem = 'https://poshmark.com/closet/'
    available = '?availability=available'
    url = '{}{}{}'.format(url_stem, poshmark_account, available)
    return url

In other words, it is trying to share items at an invalid closet: https://poshmark.com/closet/joel.jerez0420@gmail.com?availability=available, which explains why 0 items are found.
For example, I get the same results if I try to share items for your email address (not your user name).

The issue does suggest a possible feature improvement, such as a regex function to detect when either the username (or alternate account) is an email instead of a closetname, and in such as case raise a warning and exit.

Hi ya'all!  I just finished creating a java/selenium bot that will send an offer to all likers.  Feel free to check it out/improve on it
https://github.com/nstepka/PoshMarkDiscountBot


Lookout:  responsive logs modal

A PR was made to fix and add features to the job logs modal - see https://github.com/armadaproject/armada/pull/2804 - however, that PR has become very out-of-date and is currently un-mergeable. It would still be good to recover those changes, updating as needed, and get that merged into the codebase.
The original PR goals:

Make Job log modal responsive, a responsive website can make it easy for users to access the features of the website, irrespective of their Device width or height.
re-structure the log modal to show details of the logs properly with user experience and interaction in mind.
a new feature for opening logs in a new browser tab in other for logs to be viewed clearly for efficient analysis of the log's details.

Original rendering of Job Log modal

Lookout V1 Video of interface and New feature shown below.
https://github.com/armadaproject/armada/assets/58771507/f60d1f69-175b-471e-afdc-69757715aa09
Lookout V2 video (Showing the new Window tab feature implemented) and UI tweaks.
https://github.com/armadaproject/armada/assets/58771507/ad1d1c75-5bce-48e8-8091-c60abe470dcb

Hand-off Notes for Finishing Development on this change:
Use a fork/copy of the Armada repository - if not already existing, clone it:
  $ git clone git@github.com:myusername/armada.git
  $ cd armada
``
Add the repository containing the branch of the submitted (abandoned) PR as a  Git remote:

$ git remote add kanu https://github.com/Ginohmk/armada.git
Fetch (but do not automatically merge) the branches from that repository:

$ git fetch kanu
Make a new work branch and switch to it:

$ git branch feat/responsive-logs-modal
$ git checkout feat/responsive-logs-modal
Merge in the changes from the branch of the abandoned PR:

$ git merge kanu/feat/responsive-logs-modal
There will be merge conflicts, in internal/lookout/ui/yarn.lock and package.json, and maybe others.

**RUNNING AND TESTING LOOKOUT UI**

Start the Armada services, from the top of the Armada repo tree:

$ mage localdev full
Run the basic testsuite, to be sure the backend services are working well:

$ mage testsuite
If that runs successfully, install the Lookout dependencies:

$ cd internal/lookout/ui
$ yarn install
$ yarn run openapi
The 'yarn install' step will have errors - this is the remaining issue to be fixed to deliver these changes. Once those errors are fixed (by modifying package.json), run the server with:

$ yarn start
There are run-time processing errors that can occur here. The UI is available at http://hostname:3000/

**TESTING AFTER INSTALLATION**

Once the installation issues are resolved, you can verify the change by submitting an Armada job, then viewing the logs details tab for that job. You can submit a job that will run for a while.

Save the following YAML in a file named 'slow-job-test.yaml':

numBatches: 1
batchSize: 10
queue: e2e-test-queue
jobSetId: job-set-1
randomClientId: true
jobs:

priority: 0
namespace: personal-anonymous
podSpec:
terminationGracePeriodSeconds: 0
restartPolicy: Never
containers:
- name: ls
imagePullPolicy: IfNotPresent
image: alpine:3.10
command:
- sh
args:
- -c
- ls -l; sleep 30; date; echo '========'; ls -l; sleep 10; date
resources:
limits:
memory: 10Mi
cpu: 100m
requests:
memory: 10Mi
cpu: 100m

timeout: "180s"
expectedEvents:

submitted:
succeeded:

Then submit it to Armada:

$ armadactl submit ./slow-job-test.yaml
It will take a while to run, so you can view the log details tab for that job in the Lookout UI, confirm the new layout rendering, etc.

**MODULE VERSION ISSUES**

- some modules require a different version of React than 17.0.1 that is specified in package.json. I tried downgrading to 16.14.0 and upgrading to 18.2.0, because the  several visx/* required a different version.
- After module installation, errors are displayed when running the Lookout server about the 'lodash' module not found. I added that to the package.json. However, there are plenty of other module dependency errors I was unable to resolve.  An experienced React dev may know how to sort those out.
- To retry the module installs, I repeatedly ran (in the internal/lookout/ui directory):

$ git clean -f -x -d      # remove node_modules and other build artifacts
$ yarn install
$ yarn run openapi
$ yarn start
In attempting to fix the module version requirements, I tried various versions of the react and react-related modules, plus the 'mui' and 'visx' modules, by querying the NPM archive, e.g.

$ yarn npm info 'react'  --fields versions --json | jq

These changes were delivered in Oct 2023 in Lookout V1, and some of the styling was incorporated into V2 - closing.


Premium capacity and users w/out a pro license

FYI - the following paragraph is incorrect. I think it boils down to poor naming of the Premium capacities - EM SKUs are listed as premium capacity but all users accessing the report, whether or not it's in a premium capacity (EM Sku), needs a Pro license.
"If you've purchased Power BI Premium, you don't have to assign Pro licenses to enable user access. Users in the organization can access reports that are shared with them, as long as the reports are published to a Premium capacity."
[Enter feedback here]

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: d017bc96-49d4-7b63-9394-1739cdf7528d
Version Independent ID: 1e70d724-121d-feea-471e-307c2f27dd24
Content: Power BI for US government customers - Overview - Power BI
Content Source: powerbi-docs/admin/service-govus-overview.md
Service: powerbi
Sub-service: powerbi-admin
GitHub Login: @kfollis
Microsoft Alias: kfollis

@marcbeacom - thank you for the feedback on this article. After consulting with the product team, I made some wording changes to help clarify. Closing this issue now.


Navbar Items hover color is not contrasting and theme changing button does not feel interactive

Describe the bug
Hovering on the navbar items assigns them a color which makes them not clearly visible.
Also the icon for switching themes does not react to mouse hover by changing color like other navbar items.
The theme switching button must also change to a pointer cursor when hovered.
same goes for the text besides the logo, that text doesn't react to hovers either.
To Reproduce
Steps to reproduce the behavior:

Go to the website
Hover on navbar items
Hover on theme changing button
Hover on the text besides the logo

Expected behavior
The navbar items must have a contrasting color and the text besides the logo must react to hovers also the theme changing button should react to hovers by changing colors like other navbar items. The theme changing color also keeps the cursor static instead of making it a pointer.
Desktop :

OS: Windows 11
Browser Brave
Version 1.14.105

I believe I could fix this, please assign this task to me under hacktoberfest 2022

Can I be assigned this issue under hacktoberfest 2022 @akshitagupta15june

ok go for it

#188 this fixes it? if I reckon correctly

Please assigned it to me.


As a HR personnel, I can update a department

Points for consideration:

In EditDepartmentCommand#execute: Do I need to update department view?


[Enhancement][Lake] Compaction scheduling based on compaction score

What type of PR is this：

[ ] BugFix
[ ] Feature
[x] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

[FE PR Coverage Check]
:disappointed: fail : 125 / 263 (47.53%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/lake/Utils.java
0
4
00.00%
[78, 79, 124, 125]

:large_blue_circle:
com/starrocks/lake/compaction/CompactionContext.java
0
31
00.00%
[25, 26, 27, 30, 31, 34, 38, 39, 42, 46, 47, 50, 54, 58, 59, 62, 66, 70, 74, 75, 78, 82, 83, 86, 90, 91, 94, 98, 99, 102, 106]

:large_blue_circle:
com/starrocks/transaction/LakeTableTxnLogApplier.java
0
3
00.00%
[36, 43, 45]

:large_blue_circle:
com/starrocks/transaction/PartitionCommitInfo.java
0
3
00.00%
[138, 139, 143]

:large_blue_circle:
com/starrocks/transaction/PublishVersionDaemon.java
0
7
00.00%
[344, 345, 347, 348, 349, 351, 352]

:large_blue_circle:
com/starrocks/lake/compaction/CompactionScheduler.java
1
4
25.00%
[125, 129, 385]

:large_blue_circle:
com/starrocks/common/proc/CompactionsProcDir.java
6
22
27.27%
[27, 32, 37, 38, 39, 40, 41, 43, 44, 45, 46, 47, 48, 50, 51, 52]

:large_blue_circle:
com/starrocks/lake/compaction/CompactionManager.java
12
23
52.17%
[86, 87, 88, 90, 91, 92, 93, 118, 123, 133, 154]

:large_blue_circle:
com/starrocks/common/proc/PartitionsProcDir.java
66
118
55.93%
[87, 88, 89, 90, 91, 92, 93, 94, 95, 96, 97, 98, 99, 280, 281, 282, 285, 286, 289, 293, 294, 295, 296, 297, 298, 299, 300, 303, 304, 334, 340, 362, 363, 364, 366, 368, 369, 370, 371, 372, 373, 375, 376, 377, 378, 379, 380, 381, 382, 422, 429, 434]

:large_blue_circle:
com/starrocks/lake/compaction/Quantiles.java
16
24
66.67%
[24, 49, 57, 58, 60, 61, 63, 68]

:large_blue_circle:
com/starrocks/common/Config.java
1
1
100.00%
[]

:large_blue_circle:
com/starrocks/lake/compaction/ScoreSelector.java
8
8
100.00%
[]

:large_blue_circle:
com/starrocks/lake/compaction/ScoreSorter.java
5
5
100.00%
[]

:large_blue_circle:
com/starrocks/common/proc/ProcService.java
1
1
100.00%
[]

:large_blue_circle:
com/starrocks/lake/compaction/PartitionStatistics.java
9
9
100.00%
[]


Add progress dialog during webpage loading

After "log in" is pressed, there's a blank
white screen for several seconds.
This will be an indicator that something
is happening (which is loading the webpage).
It's better  than leaving the user wondering.

Is this going to show the dialog for every page load?

Only when loading url in LoginWebViewActivity..

Wouldn't it also show again after the user logs in and waits for the auth token or 2FA prompt?

Correct.
As long as there's a URL page loading in the background, this will happen.
You seem doubtful. Have something in mind?

If we really want we could check the URL and only show it when a specific URL is present.

LGTM

Thanks @hzsweers @Meisolsson!


How to use classes for routes?

Hello,
i don't know how I can use Classes like this? How can I get the Request and Response?
$app->get('/test', myClass);

@majoess check out the Slim Container Resolution section of the docs.

Hey,
thanks for you reply. How can I create a Controller? Please give me some example.
Best regards,
majoess

@majoess , see https://github.com/akrabat/slim-bookshelf/blob/master/app/src/Bookshelf/AuthorController.php

Hello,
i don't know how to autoload my Controller with namespace. they are located under /controllers/informationController (+ public function) and informationController.php is in
namespace miroAPI\Controllers


excalidraw+ can't change language

I've been using this tool for free for a while，I think this tool is so good that I bought excalidraw+ yesterday，But I found that you can't switch languages in excalidraw+，but you can switch languages in the free version，I am very strange.

Probably this is a recent regression
cc @dwelle

Yes, currently the Excalidraw+ editor is not multi-lingual as the site itself is not, but it doesn't hurt to have at least the editor translated, so we'll enable it.


question regarding Keys

Thanks again for building this.
Is it safe to have the Key be a string in our app's javascript code?
i.e. if the key is "password" and I store the user's password in the value, does that make it easier for someone to hack the password if the phone is compromised?
And is someone able to look at the list of "keys"?
Thank you!

@charlesmccann  obfuscation is by no means secure therefore it does not matter how you name a key.
You should consider keys to be public. Don't store sensitive information on a key this is what values are for.

@charlesmccann yes it is relevant what the key is called. It's the value that is encrypted. You can call it "password" or whatever you like.


📝 docs: add shouldSelect focus option

react-hook-form/react-hook-form#7781
react-hook-form/react-hook-form#7318

nice! I was going to do it.

would you like to add a quick example in the code example as well?

would you like to add a quick example in the code example as well?

What do you think about a code snippet under the options.shouldSelect description? It doesn't feel like that big of a code difference from the basic example to do it's own sandbox, in-app usage example and it's TS version

Sounds good to me with the example. Single paragraphs probably don't need a list, we can start to introduce a list when we have multiple dot points.

Single paragraphs probably don't need a list, we can start to introduce a list when we have multiple dot points.

Good point

Just one minor, for consistency could you move rules under the Props which I have actioned based on your feedback. Let's roll this feature out this weekend as well ☺

Let's roll this feature out this weekend as well ☺

I saw that, yeah!
I'm not a fan of having bright heading for a section as the section title seems like the only "important" information to me and my break skip passes the rest of the info. Maybe it's just me, but I'll much more reliably read the rest of the section, if it's all highlighted with a slightly different background along with the heading.
Not saying we should do that instead, just my personal feedback ;)

@Moshyfawn Thanks for the feedback, I change the title underline because there are two many pink headers.


npm test always fails

Description
I want to run tests.
Expected Behavior
Tests succeed.
Observed Behavior
Tests always fail. With a variety of syntax errors.
Environment
Please run these commands in the project folder and fill in their results:

npm ls react-native-scripts: 0.0.28 & 0.0.29
npm ls react-native: 0.43.4
npm ls expo: 16.0.0
node -v: 6.10.3
npm -v: 3.10.10

Also specify:

Operating system: Xubuntu 17.4
Phone/emulator/simulator & version: Jest 19.0.2

Reproducible Demo
I got only one test, it's the default test CRNA creates.
I try to run it with npm run test
I get SyntaxError: Unexpected token import in my own source files when I use this config:
"jest": {
  "preset": "jest-expo"
},

I get SyntaxError: Unexpected identifier on type ModuleConfig = [ in the react-native files when I use this config:
"jest": {
  "preset": "jest-expo",
  "transformIgnorePatterns": [
    "/node_modules/",
    "/src/"
  ]
},

I get SyntaxError: Unexpected token import on a react-native import in the expo package when I use this config:
"jest": {
  "preset": "react-native"
},

I get SyntaxError: Unexpected token ) in the react-native packages jest setup when I use this config:
"jest": {
  "preset": "react-native",
  "transformIgnorePatterns": [
    "/node_modules/",
    "/src/"
  ]
},

try this:
"transformIgnorePatterns": [
      "node_modules/(?!(jest-)?react-native|react-navigation)"
 ]

FAIL  ./App.test.js
  ● Test suite failed to run
..../mobile-app/node_modules/expo/src/Expo.js:6
import { NativeModules } from 'react-native';
^^^^^^
SyntaxError: Unexpected token import

  at transformAndBuildScript (node_modules/jest-runtime/build/transform.js:321:12)
  at Object.<anonymous> (src/components/shared/Screen.js:5:11)
  at Object.<anonymous> (src/components/Home/index.js:2:13)

Didn't work :/

On a fresh project with this jest config:
  "scripts": {
...
    "test": "node node_modules/jest/bin/jest.js --watch"
  },
  "jest": {
    "preset": "jest-expo"
  },

I'm able to run tests without problems. Can you paste your full package.json?

I just created a new project and ejected.
package.json

{
  "name": "mobile-app",
  "version": "0.1.0",
  "private": true,
  "devDependencies": {
    "jest-expo": "~1.0.1",
    "react-test-renderer": "16.0.0-alpha.6"
  },
  "scripts": {
    "start": "react-native start",
    "android": "react-native run-android",
    "ios": "react-native run-ios",
    "test": "node node_modules/jest/bin/jest.js --watch"
  },
  "jest": {
    "preset": "jest-expo"
  },
  "dependencies": {
    "react": "16.0.0-alpha.6",
    "react-native": "^0.44.0"
  }
}

Error
 FAIL  ./App.test.js
  ● Test suite failed to run

    /Users/kay/Development/mobile-app/App.test.js: Unexpected token (7:35)
         5 |
         6 | it('renders without crashing', () => {
      >  7 |   const rendered = renderer.create(<App />).toJSON();
           |                                    ^
         8 |   expect(rendered).toBeTruthy();
         9 | });
        10 |

Test Suites: 1 failed, 1 total
Tests:       0 total
Snapshots:   0 total
Time:        1.046s
Ran all test suites.

@kay-is - can you post the output of npm ls --depth=1?
What you're seeing here is a quirk of how babel and jest work with react-native.

react-native has a culture of shipping raw source (in other words, not compiled with babel yet) and jest by default does not run all of the packages in node_modules through babel, in order to be faster.
react-native defaults to react-native-stage-0 if no .babelrc is present, whereas jest just assumes no babel config. Currently create-react-native-app deletes the .babelrc when you eject because it was assumed that it wasn't needed due to the stage-0 default, but it should not do that because jest needs it.

So, you'll need to install babel-preset-react-native and re-create .babelrc on an ejected project like so:
{
  "presets": ["react-native"]
}

This is a bug that needs to be resolved, see #243

I'm also getting this error
my package.json is:
{
  "name": "mobile-client",
  "version": "0.1.0",
  "private": true,
  "devDependencies": {
    "babel-eslint": "^7.2.3",
    "eslint": "^3.19.0",
    "eslint-config-airbnb": "^15.0.1",
    "eslint-plugin-flowtype": "^2.34.0",
    "eslint-plugin-import": "^2.2.0",
    "eslint-plugin-jsx-a11y": "^5.0.3",
    "eslint-plugin-react": "^7.0.1",
    "eslint-plugin-react-native": "^2.3.2",
    "flow-bin": "^0.40.0",
    "jest-expo": "^0.4.0",
    "react-native-scripts": "0.0.29",
    "react-test-renderer": "16.0.0-alpha.6"
  },
  "main": "./node_modules/react-native-scripts/build/bin/crna-entry.js",
  "scripts": {
    "start": "react-native-scripts start",
    "eject": "react-native-scripts eject",
    "android": "react-native-scripts android",
    "ios": "react-native-scripts ios",
    "test": "node node_modules/jest/bin/jest.js --watch",
    "flow": "flow",
    "lint": "node node_modules/eslint/bin/eslint.js -c ./.eslintrc.json --ignore-pattern '*/node_modules/*' --ignore-pattern '*/npm/*' .; exit 0"
  },
  "jest": {
    "preset": "jest-expo"
  },
  "dependencies": {
    "apollo-client": "^1.4.0",
    "expo": "^16.0.0",
    "prop-types": "^15.5.10",
    "react": "16.0.0-alpha.6",
    "react-apollo": "^1.4.0",
    "react-native": "^0.43.4",
    "react-navigation": "^1.0.0-beta.11",
    "react-redux": "^5.0.5",
    "redux": "^3.6.0",
    "redux-persist": "^4.8.0",
    "redux-saga": "^0.15.3",
    "redux-thunk": "^2.2.0"
  }
}

what's in your .babelrc @erhathaway?

Okay, tried to install the preset and add a .babelrc didn't help.
I also tried to use the jest-react-native preset and install babel-jest.
Still getting ES2015 related errors :(

 FAIL  ./App.test.js
  ● Test suite failed to run

    /Users/kay/Development/mobile-app/node_modules/glamorous-native/src/index.js:1
    ({"Object.":function(module,exports,require,__dirname,__filename,global,jest){import createGlamorous
 from './create-glamorous'
                                                                                ^^^^^^
    SyntaxError: Unexpected token import

      at transformAndBuildScript (node_modules/jest-runtime/build/transform.js:321:12)
      at Object. (modules/screens/Placeholder.js:2:22)
      at Object. (modules/Navigation.js:2:18)

this is related to quirk 1. that i mentioned above -- glamorous-native needs to be transpiled. unfortunately this is more of a jest issue than anything that we deal with directly here, but i'll try to help anyhow.
you will need to add glamorous-native to the regex here: https://facebook.github.io/jest/docs/tutorial-react-native.html#transformignorepatterns-customization

@brentvatne my babelrc is:
{
  "presets": [
    "babel-preset-expo",
  ],
  "env": {
    "development": {
      "plugins": [
        "transform-react-jsx-source",
      ]
    }
  }
}

I was able to fix the problem using a variation of @bang88 approach:
  "jest": {
    "preset": "jest-expo",
    "transformIgnorePatterns": [
      "node_modules/(?!react|@expo|expo)"
    ]
  },

it should work if you just remove the following entirely:
    "transformIgnorePatterns": [
      "node_modules/(?!react|@expo|expo)"
    ]

unless you are including another package that needs to be transpiled (see https://github.com/react-community/create-react-native-app/issues/199#issuecomment-307890700). nonetheless, I'm glad you found something that works

Thanks, now to the JSX/ES2015 errors are gone.
Can it be that native modules have to be excluded entirely somehow?
I have a welcome screen with react-native-video as background and the whole thing blows up because of an undefined access of Constants native module here https://github.com/react-native-community/react-native-video/blob/master/Video.js#L172

@kay-is - you need to provide mocks for those constants. one of the nice things about using jest with expo is that we know all of the native apis that are available, so we can mock all of these for you, eg in jest-expo we have:
https://github.com/expo/jest-expo/blob/1041845d0dd128143d00a239f39921b5265e802c/src/exponentModules.js#L154-L159
then we apply all of those mocks (along with a few special case ones):
https://github.com/expo/jest-expo/blob/1041845d0dd128143d00a239f39921b5265e802c/src/setup.js#L28-L73
Regardless, this issue doesn't seem to be related to create-react-native-app anymore, maybe it's a problem with the jest documentation. The issue that has spun off from this is that we should switch the babel preset when ejecting: https://github.com/react-community/create-react-native-app/issues/243
thank you so much for your patience in going through the issue with me and sticking with it!

I was receiving a Syntax Error: Unexpected token import originating from react-navigation while attempting to run tests. After adding
"transformIgnorePatterns": [
  "node_modules/(?!(jest-)?react-native|react-navigation|other-problem-modules...)"
]

to the jest config in "package.json", the react-navigation error was no longer reported. Instead, jest complained with an error similar to the one mentioned here (involving expo modules).
This leads me to believe configuration settings in "package.json" override those in "jest-expo/jest-preset.json". Is this what is happening?
I ended up having to copy the setting from "jest-preset.json" and include react-navigation:
"transformIgnorePatterns": [
  "node_modules/(?!(jest-)?react-native|react-navigation|react-clone-referenced-element|expo|@expo/*|exponent|@exponent/*)"
]

I would love some help on this too.
Jest keeps failing and displays this:
`import type { NavigationAction } from './TypeDefinition';
^^^^^^
SyntaxError: Unexpected token import

  at ScriptTransformer._transformAndBuildScript (node_modules/jest-runtime/build/script_transformer.js:305:17)`

I've tried the various methods listed here, but nothing works.
My package.json file:
"devDependencies": {     "babel-cli": "^6.26.0",     "babel-preset-flow": "^6.23.0",     "babel-preset-react-native": "^4.0.0",     "jest": "^21.2.1",     "jest-expo": "^21.0.2",     "react-native-scripts": "1.3.1",     "react-test-renderer": "^16.0.0"   },   "main": "./node_modules/react-native-scripts/build/bin/crna-entry.js",   "scripts": {     "start": "react-native-scripts start",     "eject": "react-native-scripts eject",     "android": "react-native-scripts android",     "ios": "react-native-scripts ios",     "test": "node_modules/.bin/jest"   },   "jest": {     "preset": "react-native"   },   "dependencies": {     "axios": "^0.16.2",     "expo": "^21.0.2",     "firebase": "^4.5.1",     "lodash": "^4.17.4",     "moment": "^2.19.1",     "react": "16.0.0-beta.5",     "react-native": "0.48.4",     "react-native-router-flux": "^4.0.0-beta.21",     "react-native-spinkit": "^1.1.1",     "react-redux": "^5.0.6",     "redux": "^3.7.2",     "redux-thunk": "^2.2.0"   }
And my .babelrc file:
{   "presets": ["babel-preset-expo", "react-native"],   "env": {     "development": {       "plugins": ["transform-react-jsx-source"]     }   } }
A funny thing that happens when I type npm ls --depth=1into the console is that I get a huge list of missing dependencies. But my project runs just fine. I'm not sure what's up with that.

Following discussion too :)

following. I'm having the same issue as lazzlo

I was having the same issue. After trying a few different options of the posted above, the     "transformIgnorePatterns" targeting the correct package did the trick and now my tests pass normally.

@debugmaster @ethanbrown3 GitHub has a follow/subscribe system for this that doesn't add noise to the thread. The button is on the right of issue pages (towards the top).

@ide can you take a look at lazzlo's jest issue above here?

I probably won’t look into this for awhile so if it’s important or urgent for you I recommend creating a new project and honing in on the specific issue (may need to read source under node_modules, I usually do that to debug JS things). If there’s something specific to jest-expo (vs the React Native Jest preset or Babel) you can open an issue on that repo.


vue-popper: fix a node removal bug

Please makes sure these boxes are checked before submitting your PR, thank you!

[x] Make sure you follow Element's Contributing Guide.
[x] Rebase before creating a PR to keep commit history clear.
[x] Add some descriptions and refer relative issues for you PR.

#575


Document nav

Hi! I just came across this project and it wasn't obvious to me from reading the README how to structure my nav to include the auto-generated docs. Just wanted to post a quick note in case someone else is looking to try this out.
nav:
  - API Documentation: autoapi/

Hi @cdwilson! I'm happy to hear that at least one person has found the project in its early state :smile:
This is great feedback. The snippet you included is exactly how the auto-generated code should be placed in the nav, but instructions for this should've been included in the README. I'll update the README to include those instructions and also a section that demonstrates a full mkdocs.yml for a simple project.

Completed a first pass of the additional documentation.
@cdwilson If I submit a PR with the changes, would you be willing to review it?

@jcayers20 sorry, missed this earlier, sure!

Thanks! Just merged to develop; changes to documentation in PyPI will take effect when I release v0.1.7.


Feature Request

Hi, I've noticed that currently the plugin requires metadata to exist to inject them into env vars and I realized that this may limit the use case to converting values supplied by block-steps into env vars or cases where the user knows that the metadata will exist.
I was wondering if you're interested in extending this plugin to allow default values to be defined. So if a metadata doesn't exist it will assign a default value to the env vars.
Also, the current implementation actually overrides the env vars with the metadata values even if the env vars are defined previously. I'd also like to prevent this from happening.
I have actually forked this repo and implemented these features, if you're willing to review the code I can raise a PR and make any necessary changes to the implementation that's needed.

Hi, this is super useful! Any chance this can get merged upstream? :)


Plans and consumption for the same plan but diferent PeriodicityType

Hello! I'm reading your doc to create plans https://github.com/lucasdotvin/laravel-soulbscription?ref=madewithlaravel.com#creating-plans and you give an example to create a monthly plan, but what happens if the same plan has Quarterly and Annual PeriodicityType? how would I do it in that case?
$gold = Plan::create([
            'name'             => 'gold',
            'periodicity_type' => PeriodicityType::Month,
            'periodicity'      => 1,
        ]);

$gold = Plan::create([
            'name'             => 'gold',
            'periodicity_type' => PeriodicityType::Month,
            'periodicity'      => 3,
        ]);

$gold = Plan::create([
            'name'             => 'gold',
            'periodicity_type' => PeriodicityType::Month,
            'periodicity'      => 12,
        ]);
`
it would be like this?
And how would it work the consumption of features be in those cases?

Regards

@pixsolution I think the natural solution would be to treat them as separate plans. For example, plan-a-monthly and plan-a-yearly.

Hey! I believe @frknasir already provided an answer with the most proper way to work in this scenario.

Hey! I believe @frknasir already provided an answer with the most proper way to work in this scenario.

you did provide this in the docs :
$subscriber->subscribeTo($plan, expiration: today()->addYear());
So I wanted to know if using a monthly plan while setting the expiry to be after a year would work.


i have tried v3 not working, is it working for you sir?

i have tried v3 not working, is it working for you sir?

This plugin works fine on v2 with safetynet api, v3 is not supported.
refer: https://developers.google.com/recaptcha/docs/versions


Fix style differences between local and production

While pushing out a styling release it's become very clear that there are vast differences between the styles applied to local and production. These styling issues make it very difficult to have visual consistency which is a big problem.
Incorrect behavior
This shows what styles look like while running gatsby-develop on local.

Correct behavior
This shows what styles should look like and is currently on production.

.

This issue has been resolved by updating tailwind and enabling JIT. The issue was caused by the @base import not being utilized by production builds.


Would you like to provide a demo to use pysmilesutils for downstream examples?

Thank you so much for your repo. If you could give us a tutorial on how to use pysmilesutils in real applications, that will be a great help.
I think you knew selfies well. Is it possible to substitute smiles with selfies?

Hello
Thank you for trying out pysmilesutils.
There is an example folder in the base-folder of the repository with several examples. These can be view in VSCode or converted to Jupyter notebook.
We have no plans to support selfies at the moment. If you think it is of interest, we welcome the discussion in another issue.

I'm not fully into the SELFIES syntax, but I think it should be possible to modify the regular expression pattern and otherwise use the tokenizer class to build the vocabulary and tokenize.

Thank you very much!


switch in query

I wonder how I can write switch statements in query. I want to query depending on a search index (either id or name) For example,
From
provider.query()
.get('patrons')
.qs({id: 111, name: "Ronda"})
})

To, Something like this:
provider.query()
.get('patrons')
.qs(function() {
         switch (queryIndex) {
               case "id":
                 return {id, query};
               case "name":
                 return {name, query};
         }
  })

That depends on your application logic. You just have to set the parameter, it's not like queueing a real database. That's REST. Give me the bigger picture.

You are right. I was kind in a mixed bag of querying DB and REST. I have REST API api/patrons that returns patron lists in a following format. I want to  apply a query parameter depending on the user choice of query index option (either id or name, not both). I find a problem that the API does not provide the 'names' property as a query parameter. Is there any reasonable way to work around this? It seems that I have no option but fetching all data and filter with a name afterward. It looks a bad choice for performance.
{
  "total": 1,
  "entries": [
    {
      "id": 1000001,
      "names": [
        "Robert Lee"
      ],
      "emails": [
<EMAIL_ADDRESS>      ]
    }
  ]
}

var findPatrons = function(req, res, next) {

  var queryPatron = req.query.patron;  // query patron
  var queryIndex = req.query.index;  //query index

  switch (queryIndex) {
    case "recordNum":
        return sierraApi.query()
         .get('patrons')
         .qs({
              id : queryPatron,
          })
          .request(function (err, _res, body) {
              res.setHeader('content-type', 'application/json')
              if (err || _res.statusCode !== 200) { console.log(err) }
               res.end(JSON.stringify(body.entries))
          })

    case "patronName":
        return sierraApi.query()
         .get('patrons')
         .qs({
              names : queryPatron,
          })
          .request(function (err, _res, body) {
              res.setHeader('content-type', 'application/json')
              if (err || _res.statusCode !== 200) { console.log(err) }
               res.end(JSON.stringify(body.entries))
          })
  }
};

The parameter 'id' works fine. But the parameter 'names' is not.

I find a problem that the API does not provide the 'names' property as a query parameter.

If the API provider doesn't provide that option, there is nothing you can do about it really :)
Generally speaking making a query by id will be faster for both of you. The database engine will make the query faster, you'll get the results faster, and then you just have to filter them up. Searching by item in array is generally not fast for a database. The real problem for you and your users would be if you know only the name upfront.

Thanks Simov.  It was a good topic to think about.  I will close this issue.  Thanks you again for the great library.