Add ability to infer missing peaks for some isotopeLabels

FEATURE DESCRIPTION
Feature Inspiration
(El-)MAVEN does not output a row for some isotope labels when no data for that labling is found. This causes load_accucor_msruns.py to fail.
AccuCor infers that the values for the missing isotope labeling values are zero and fills them in on the "corrected" worksheet, however, the "original" worksheet from (El-)MAVEN doesn't have them.
Feature Description
When loading the Original data from (El-)MAVEN, the loading script should infer zero values for any missing isotope label values.
Alternatives Considered
Comment
In the example below, the rows for isotopeLabel C13-label-5, C13-label-6,C13-label-7, C13-label-8, and C13-label-10 are missing in the "Original" worksheet. The values in the "Corrected" worksheet are zeros.
Original worksheet:

label
metaGroupId
groupId
goodPeakCount
medMz
medRt
maxQuality
isotopeLabel
compound
compoundId
formula
expectedRtDiff
ppmDiff
parent
serum-xz969
serum-xz970
serum-xz979
serum-xz989

0
1
5
255.2326
2.314517
0.8185162
C12 PARENT
C16:0
C16:0
C16H32O2
7.805483
1.255459
255.2326
805432300
1154166000
1292612000
1472555000

0
2
5
256.236
2.316407
0.8271532
C13-label-1
C16:0
C16:0
C16H32O2
7.803593
1.310093
255.2326
138051500
201778100
231019800
253609900

0
3
5
257.2396
2.31263
0.8188428
C13-label-2
C16:0
C16:0
C16H32O2
7.80737
0.4745392
255.2326
10343600
14372760
19908750
22173560

0
4
5
258.2428
2.303187
0.8545959
C13-label-3
C16:0
C16:0
C16H32O2
7.816813
1.063565
255.2326
576782.8
745905.8
1208412
1243975

0
5
4
259.2458
2.303046
0.6084198
C13-label-4
C16:0
C16:0
C16H32O2
7.816954
2.35433
255.2326
0
137531.9
496514.1
348400.5

0
6
1
264.2625
2.3078
0.4295699
C13-label-9
C16:0
C16:0
C16H32O2
7.8122
2.656081
255.2326
0
0
103849.4
0

0
7
1
266.2685
2.3078
0.4991664
C13-label-11
C16:0
C16:0
C16H32O2
7.8122
5.042904
255.2326
0
0
243142.2
0

0
8
4
267.2732
2.317567
0.8550228
C13-label-12
C16:0
C16:0
C16H32O2
7.802433
0.1141812
255.2326
106800.5
0
495461.5
335666.6

0
9
5
268.2767
2.30799
0.8559901
C13-label-13
C16:0
C16:0
C16H32O2
7.81201
0.3412625
255.2326
326256.8
623346.5
749252.8
951065.8

0
10
5
269.2799
2.325853
0.8071074
C13-label-14
C16:0
C16:0
C16H32O2
7.794147
0.2266606
255.2326
1939976
3603214
6054250
5764500

0
11
5
270.283
2.312634
0.8247123
C13-label-15
C16:0
C16:0
C16H32O2
7.807366
1.129096
255.2326
14937920
29787460
49312190
45732670

0
12
5
271.2864
2.316407
0.809041
C13-label-16
C16:0
C16:0
C16H32O2
7.803593
0.899936
255.2326
80304900
153432400
253075200
237934200

Corrected worksheet:

Compound
C_Label
serum-xz969
serum-xz970
serum-xz979
serum-xz989
xz1018-t

C16:0
0
963802497.317324
1381911570.01444
1548624357.3105
1762421928.88546
1033226822.36885

C16:0
1
0
0
942387.403274423
0
0

C16:0
2
0
0
0
0
0

C16:0
3
0
0
0
0
0

C16:0
4
0
0
405071.995986288
204364.89094726
0

C16:0
5
0
0
0
0
0

C16:0
6
0
0
0
0
0

C16:0
7
0
0
0
0
0

C16:0
8
0
0
0
0
0

C16:0
9
0
0
117436.642927713
0
0

C16:0
10
0
0
0
0
0

C16:0
11
0
0
218380.675882312
0
0

C16:0
12
89531.6245387077
0
504171.811503446
289542.161667861
63453.6653472893

C16:0
13
193424.232643768
401095.261730774
304379.440909968
569033.077733821
104770.750853828

C16:0
14
777825.822200985
1142648.50091085
1993797.29347301
2062655.82133341
946089.032433367

C16:0
15
2470458.83305593
6204641.92502113
10445932.5863072
9069961.78322296
3029552.24397228

C16:0
16
94845095.9159948
181191178.697518
298857435.978697
280988425.008348
139868960.005772

ISSUE OWNER SECTION
Assumptions

List of assumptions made WRT the code
E.g. We will assume input is correct (explaining why there is no validation)

Requirements

List of conditions to be met for the feature
E.g. Every column/row must display a value, i.e. cannot be empty

Limitations

A list of things this work will specifically not do
E.g. This feature will only handle the most frequent use case X

Affected/Changed Components

Files
Environment variables
External executables
Database tables
Cron job settings
Etc.

DESIGN
GUI Change description
Describe changes the user will see.
Code Change Description (Pseudocode optional)
Describe code changes planned for the feature.
Tests
A test should be planned for each requirement (above), where possible.

FYI - I'm starting work on this.

I'm reviewing the details of this issue in preparation for reviewing the associated PR.  It took me awhile to understand this issue.  Now that I think I get it, I think it would help if there was a current behavior and expected behavior section associated issues like this, especially when something in this code base is not working as might be expected.  I think I understand why the enhancement issue form was used, instead of the bug report, but I would say that if current code in the project fails given different inputs, those current/expected behavior sections would be really useful, thus I think that the bug report form has elements that would make the issue clearer.

That's a good point. If I had indicated that the current behavior was to fail with the error message Number of rows in AccuCor original and corrected data are different, it would have made it clearer what the problem was.
BTW, feel free to reach out on Slack or Zoom etc. if you're having trouble understanding things. It can be difficult to capture the full context of an issue and sometimes a quick chat can clear things up.


FIX - Domain - Reset tree selected when resetting search.

@rhtyd @davidjumani cc @svenvogel

Before:

After:

@blueorangutan package

@utchoang a Jenkins job has been kicked to build primate packages. I'll keep you posted as I make progress.

Packaging result: :heavy_check_mark:centos :heavy_check_mark:debian :heavy_check_mark:archive.
QA: http://primate-qa.cloudstack.cloud:8080/client/pr/857 (JID-3655)


Add editGroups to SQS Message Parse Task and to Sinopia New Metadata Task

We want the new localAdminMetadata record in Sinopia to have it's editGroups field with the same editGroups as the original BF Instance. This will require adjusting the SQS Message Parse task and the Sinopia New Metadata Task.

Extend https://github.com/LD4P/ils-middleware/blob/main/ils_middleware/tasks/amazon/sqs.py#L48 to add editGroup (check get_group)


Test Engine Performance with Large AAS Files

I have encountered a performance issue with our test engine when processing large AAS files.The test engine currently takes too long to generate results for large aas files.

Hi @Rudra-sandeep thanks for reporting this. How large is your AAS file? Could you provide a sample?

@otto-ifak I attached the file
test_engine.json

Thanks, I will have a look.

Improved


Fix Rollbar binding

😞 similar to https://github.com/studentinsights/studentinsights/pull/2524

selfie


ignore acceleration from driving ?

since measurements are taken from a vehicle you'd have the acceleration spikes of driving which is not a measure of how bumpy the drive was (unless madmax).
gotta do something about that, do I

only count quick short acceleration spikes, so we only count bumps and not speeding up?

not listen to readings from the axis the forward acceleration is happening on(use compass and GPS to see which way the vehicle is moving in then remove that axis, or tell users to hold phone pointing forward?)

remove acceleration from driving by checking velocity from GPS readings then removing that from the axis pointing forward before saving?

this might not even be a problem, who knows?

you idiot, cars cant do more than one g and thatd be a smooth spike, a bump is a jagged chunk of spikes.
https://www.quora.com/What-g-forces-can-most-cars-produce


How to snapshot a NAS share via Rubrik API?

I'm always frustrated when I have to do a manual snapshot of (m)any NAS shares (on a NetApp Filer) for some reasons. I didn't find anything useful for or related to this in "Rubrik REST API" for neither Base URL: /api/v1 up to /api/v3 😞
I would really appreciate a howto or some samples to do a snapshot of a NAS share via Rubrik REST API.

I now have a solution but I have to ask management/open-source-team if I can share it (due to many customization with some internal infos that should not be public)

I now have a solution but I have to ask management/open-source-team if I can share it (due to many customization with some internal infos that should not be public)…


Deleting a database connection is not deleting the entries from ab_view_menu and ab_permission_view metadata tables

Deleting a database connection is not deleting the entries from ab_view_menu and ab_permission_view_menu. which results many unnecessary rows present in the above mentioned tables in metadata.
How to reproduce the bug

Go to Database section
Click on add database
Create a new database connection and save
Delete the Database connection
go to the Metadata and query the ab_view_menu and ab_view_menu and ab_permission_view you can still see the entries of the deleted database.

Expected results
Deleting a Database connection should delete the corresponding entries from the respective tables.
what you expected to happen.
Actual results
Deleting a database connection is not deleting the entries from ab_view_menu and ab_permission_view metadata tables
Screenshots
If applicable, add screenshots to help explain your problem.
Environment
(please complete the following information):

browser type and version:
1.3.2
python version: 3.7.9
node.js version: node -v
any feature flags active:

Checklist
Make sure to follow these steps before submitting your issue - thank you!

[ ] I have checked the superset logs for python stacktraces and included it here as text if there are any.
[ ] I have reproduced the issue with at least the latest released version of superset.
[ ] I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context
Add any other context about the problem here.

Hi, @radhakvnr. Do you try to run superset init? I remember there are some cleanup steps in this command.

Hi, @zhaoyongjie . I stumbled across this issue while I was in the process of manually cleaning up these tables for this exact reason! We've renamed our DB connections several times and the permissions have never been cleaned up, which means they continue to appear as options in the "Edit Role" view. It's a minor annoyance for admins.
Running superset init doesn't clean anything up for us (on 1.4.).

any update on this?

Curious if anyone is still running into this in current-era superset or is interested in opening a PR. If not, perhaps it's been long enough to close this one out? Also, as far as the validation:required tag, I assume this is still happening in 2.0.1 / master? Confirmation or denial would be helpful :)

@zhaoyongjie unfortunately the superset init is not really deleting any un used or orphan connections. Even we rename a database connection the under lying permissions on top of that database is not renaming instead it is creating a new set of permissions with the new name. hence over load on Metadata

same problem here, now my permission of datasouce access ..... is a mess and I don't know how to clean it.
Is there any update on this problem

Curious if anyone is still running into this in current-era superset or is interested in opening a PR. If not, perhaps it's been long enough to close this one out? Also, as far as the validation:required tag, I assume this is still happening in 2.0.1 / master? Confirmation or denial would be helpful :)

yes, the problem is still there (v2.0.1 here) and quite annoying honestly. Wouldn't it be possible to perform an update operation instead of an insert one when performing any edit on the database connection?

I just check the version 2.1.0 and this problem was solved. When you change the dataset name, the role accessing datasource also update the new name.
However there is a drawback, when I choose a dataset name for a role, that name don't dissapear on the list to choose as previous version

Closing this as it seems the problem was solved in recent versions of Superset. Please reopen if that's not the case.


notmuch: 0.26 -> 0.26.1

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/notmuch/versions.
These checks were done:

built on NixOS
ran ‘/nix/store/05v4k89ni4phwyxvqskr0hji49b5fmck-notmuch-0.26.1/bin/notmuch --help’ got 0 exit code
ran ‘/nix/store/05v4k89ni4phwyxvqskr0hji49b5fmck-notmuch-0.26.1/bin/notmuch help’ got 0 exit code
ran ‘/nix/store/05v4k89ni4phwyxvqskr0hji49b5fmck-notmuch-0.26.1/bin/notmuch --version’ and found version 0.26.1
found 0.26.1 with grep in /nix/store/05v4k89ni4phwyxvqskr0hji49b5fmck-notmuch-0.26.1
directory tree listing: https://gist.github.com/adeae189f9ac416571a7c0e3beca712f

cc @chaoflow @flokli @garbas @the-kenny for review

Success on x86_64-linux (full log)
Attempted: notmuch
Partial log (click to expand)
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/05v4k89ni4phwyxvqskr0hji49b5fmck-notmuch-0.26.1
shrinking /nix/store/05v4k89ni4phwyxvqskr0hji49b5fmck-notmuch-0.26.1/bin/notmuch
shrinking /nix/store/05v4k89ni4phwyxvqskr0hji49b5fmck-notmuch-0.26.1/lib/libnotmuch.so.5.1.0
strip is /nix/store/fzcs0fn6bb04m82frhlb78nc03ny3w55-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/05v4k89ni4phwyxvqskr0hji49b5fmck-notmuch-0.26.1/lib  /nix/store/05v4k89ni4phwyxvqskr0hji49b5fmck-notmuch-0.26.1/bin
patching script interpreter paths in /nix/store/05v4k89ni4phwyxvqskr0hji49b5fmck-notmuch-0.26.1
/nix/store/05v4k89ni4phwyxvqskr0hji49b5fmck-notmuch-0.26.1/bin/notmuch-emacs-mua: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/q1g0rl8zfmz7r371fp5p42p4acmv297d-bash-4.4-p19/bin/bash"
checking for references to /tmp/nix-build-notmuch-0.26.1.drv-0 in /nix/store/05v4k89ni4phwyxvqskr0hji49b5fmck-notmuch-0.26.1...
/nix/store/05v4k89ni4phwyxvqskr0hji49b5fmck-notmuch-0.26.1

Success on x86_64-darwin (full log)
Attempted: notmuch
Partial log (click to expand)
/nix/store/ahpq12kbs7iwbh3l1z607rpzj7fy5s15-notmuch-0.26.1/lib/libnotmuch.5.1.0.dylib: fixing dylib
/nix/store/ahpq12kbs7iwbh3l1z607rpzj7fy5s15-notmuch-0.26.1/lib/libnotmuch.5.1.0.dylib: fixing dylib
/nix/store/ahpq12kbs7iwbh3l1z607rpzj7fy5s15-notmuch-0.26.1/lib/libnotmuch.5.1.0.dylib: fixing dylib
/nix/store/ahpq12kbs7iwbh3l1z607rpzj7fy5s15-notmuch-0.26.1/lib/libnotmuch.5.1.0.dylib: fixing dylib
/nix/store/ahpq12kbs7iwbh3l1z607rpzj7fy5s15-notmuch-0.26.1/lib/libnotmuch.5.1.0.dylib: fixing dylib
/nix/store/ahpq12kbs7iwbh3l1z607rpzj7fy5s15-notmuch-0.26.1/lib/libnotmuch.5.1.0.dylib: fixing dylib
/nix/store/ahpq12kbs7iwbh3l1z607rpzj7fy5s15-notmuch-0.26.1/lib/libnotmuch.5.1.0.dylib: fixing dylib
/nix/store/ahpq12kbs7iwbh3l1z607rpzj7fy5s15-notmuch-0.26.1/lib/libnotmuch.5.1.0.dylib: fixing dylib
/nix/store/ahpq12kbs7iwbh3l1z607rpzj7fy5s15-notmuch-0.26.1/lib/libnotmuch.5.1.0.dylib: fixing dylib
/nix/store/ahpq12kbs7iwbh3l1z607rpzj7fy5s15-notmuch-0.26.1

Failure on aarch64-linux (full log)
Attempted: notmuch
Partial log (click to expand)
   Compiling proc_macro v0.0.0 (file:///build/rustc-1.24.0-src/src/libproc_macro)
   Compiling rustc_const_math v0.0.0 (file:///build/rustc-1.24.0-src/src/librustc_const_math)
   Compiling syntax_ext v0.0.0 (file:///build/rustc-1.24.0-src/src/libsyntax_ext)
building of '/nix/store/whsyh46wr0zfkw420xcc8ffgahszsd80-rustc-1.24.0.drv' timed out after 3600 seconds
cannot build derivation '/nix/store/nfjkyviyyy9ly6hq1pj5wzy6qxmd491n-cargo-0.24.0.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/bbqaq71xj30lggbbbf6calm3g7g56c02-librsvg-2.42.2.drv': 2 dependencies couldn't be built
cannot build derivation '/nix/store/0hjhsl89xb2yh8m4w00jk2jg1kbqhjzs-hook.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/ffwwyb0wmm22pkcq48j89bhfhaqpdwik-emacs-25.3.drv': 2 dependencies couldn't be built
cannot build derivation '/nix/store/q66s46d7fcr0rdjc59a59k55phsznajk-notmuch-0.26.1.drv': 1 dependencies couldn't be built
error: build of '/nix/store/q66s46d7fcr0rdjc59a59k55phsznajk-notmuch-0.26.1.drv' failed


Haungrui777/master

This is a PR that extends #2 with some adjustments.

@haungrui777 could you have a look at the failing lint-css command in the build? I think we can easily merge it when this is fixed.

@haungrui777 could you have a look at the failing lint-css command in the build? I think we can easily merge it when this is fixed.

fixed the css lint error

@JulianFeinauer Are we not ready to merge?

Thanks @haungrui777 and regarding your question @NiklasMerz there are still issues in the lint-css phase but I woild be fine in deactivating it for now so that we have a green Branch before merging. WDYT?

Check out this PR for your branch: https://github.com/JulianFeinauer/iotdb-web-workbench/pull/3

Will merge that now. Big thanks to @haungrui777 and @NiklasMerz ! 🎉


updated action.yml to use node20

Thanks @Wolf2323! There's a little bit more work needed here to make the move to Node 20 across the board. I'll do the all in one commit and will publish a new release.

Hat tip in the release notes: https://github.com/onyxmueller/build-tag-number/releases/tag/v1.0.3


[Feature] Allow "mass-assign" issue to a project

I would like to suggest that gitea allows "mass-assign" issue to a project, similar to labels. You can just select multiple issues and choose a label for all of them.

That is currently not possible in the slightest as one issue can only be assigned to one project at the same time.

That was generated by simply selecting an additional project.
I definitely agree, however, that either Gitea should not imply that an issue can be assigned to multiple projects, or implement multi-project assignments.
For most use cases, one project per issue suffices.
For now, I think its way easier to simply restrict issues to one project.
There is a reason behind that: The whole "Project"-backend is built around issues having only one dependent project. Adding issues to multiple projects increases complexity and potential errors by far.

I might have been wrong here. I'll test out the proposed solution now.


Jellyfin Support

I see listed in the docs that Jellyfin should be supported but I don't see anywhere to have it connect to Jellyfin to get a list of media to use to make channels.
How do I get it to support Jellyfin like the docs say?

@Protektor-Desura If you could point out where you see that documented, we should get it changed.  Jellyfin back-end support is on the roadmap, but it is currently not scheduled until Version 1.10.0.  The most recent version is 1.2.0.
After we get the documentation changed, then #177 Jellyfin Support can be resolved as a duplicate of #98 Jellyfin As A Media Source.  Track #98 to monitor progress for this enhancement.

"Access your channels by adding the spoofed dizqueTV HDHomerun tuner to Plex, Jellyfin or emby or utilize the M3U Url with any 3rd party IPTV player app."

"Access your channels by adding the spoofed dizqueTV HDHomerun tuner to Plex, Jellyfin or emby or utilize the M3U Url with any 3rd party IPTV player app."
Right there on the front page of the GitHub page.

In case you haven't been made aware yet, that documentation is referring to the fact that you can add the dizqueTV M3U playlist to Jellyfin to watch "Live TV". It does not state that you can use Jellyfin as a back-end source of the media content.

"It does not state that you can use Jellyfin as a back-end source of the media content."
That's exactly what HDHomerun is for.


move to rust 2021

Confirmed to build locally on Ubuntu 20.04.3 LTS:
rustc 1.56.1 (59eed8a2a 2021-11-01)
rustc 1.58.0-nightly (e90c5fbbc 2021-11-12)

Please bump the CI rust version https://github.com/paritytech/frontier/blob/master/.github/workflows/rust.yml

rust-version = "1.56.1" introduced
For reference, I tried to get this to cargo build with 1.56.0 and it failed with
error: package `...` cannot be built because it requires rustc 1.56.1 or newer, while the currently active rustc version is 1.56.0

With --ignore-rust-version it does build with 1.56.0, as expected.

I get some warnings FYI:
  Compiling frame-benchmarking-cli v4.0.0-dev (https://github.com/paritytech/substrate#ba153b9a)
warning: unused variable: `commands_stream`
   --> template/node/src/service.rs:352:21
    |
352 |     let (command_sink, commands_stream) = futures::channel::mpsc::channel(1000);
    |                        ^^^^^^^^^^^^^^^ help: if this is intentional, prefix it with an underscore: `_commands_stream`
    |
    = note: `#[warn(unused_variables)]` on by default

warning: struct is never constructed: `LightDeps`
  --> template/node/src/rpc.rs:30:12
   |
30 | pub struct LightDeps<C, F, P> {
   |            ^^^^^^^^^
   |
   = note: `#[warn(dead_code)]` on by default

warning: function is never used: `create_light`
   --> template/node/src/rpc.rs:203:8
    |
203 | pub fn create_light<C, P, M, F>(deps: LightDeps<C, F, P>) -> jsonrpc_core::IoHandler<M>
    |        ^^^^^^^^^^^^

    Building [=======================> ] 882/883: frontier-template-node(bin)

Maybe related to https://github.com/paritytech/frontier/pull/471 (stale and could be revived if needed?)

You can set the WASM_BUILD_TOOLCHAIN to stable release 1.56.1 actually. I recall it worked again now.


Fix Enum#to_s to wrap flag enums with parens

This fixes is to display multiple enum flags in collection. For example:
@[Flags]
enum Foo
  A
  B
end

p [Foo::A, Foo::B, Foo::A | Foo::B]

It outpus:
[A, B, A, B]

This output is ambigious, so this commit fixes it to wrap multiple flag enums with parens. Then, it outputs:
[A, B, (A, B)]

It looks good. Thanks.

WDYT about adding a skip_parens (default: false) named argument to the to_s?
If I want to print only one enum flag value I would not want those extra parens.

#to_s for usual enum (not flag) is useful sometime, but I think #to_s for flag enum is useful only for debugging
in many case. If you want another manipulation, you can use #each method.

I would think about piping possibilities, instead of surrounding them with parens:
[A, B, A | B]

I find it more consistent with how you write it in code

I agree for a pipe, it better represents the underlying value, and avoids the issue altogether.

Honestly, I thought same thing at first, but also I need to respect current implementation, so I fixed as this way.

Closed in favor of #4005


feat: rename api stub to api placeholder

:tada: This PR is included in version 0.373.0 :tada:
The release is available on:

npm package (@next dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Update change log

[Current coverage][cc-pull] is 87.48%

Merging [#1895][cc-pull] into [master][cc-base-branch] will not change coverage

@@             master      #1895   diff @@
==========================================
  Files           293        293
  Lines         52495      52495
  Methods           0          0
  Messages          0          0
  Branches       5431       5431
==========================================
  Hits          45924      45924
  Misses         5646       5646
  Partials        925        925

Powered by Codecov. Last updated by [7984735...c066678][cc-compare]
[cc-base-branch]: https://codecov.io/gh/numba/numba/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/numba/numba/compare/798473565791a6a7b47f0ecad2d82ffab9e4138d...c06667897302476c4cbb0f433135b7c26a1ce158
[cc-pull]: https://codecov.io/gh/numba/numba/pull/1895?src=pr


combine results into batch request

i think it's possible to send multiple results in a single api call
thos should be done. saves a lot of traffic

done and released with v2.6.0


25 create add new project page

This is for the 'add-new-project-page'
What I have done:
1 added multiselect-component.js
2. updated the add-new-project.html (with multiselect component)
3. updated the main-section.js (with multiselect component)
4. add createProject to the /data-access/calls.js (together with Moamin)
This version is not % done, still need to fix the connection to the backend and to add a piece of code to update the teamMembers selection from multiselect component.
However, please take a look and give feedback for better solution.
Thank youuuu happy llamas! 🦙

@inggritenovaleta  from the 1st sight, it looks so good :clap: and yeah still need backend connections
let me know if we can work all together to find the way to write the backend :+1:

@inggritenovaleta from the 1st sight, it looks so good 👏 and yeah still need backend connections let me know if we can work all together to find the way to write the backend 👍

thank you Moamin, tonight Rosa will help me too see it too and ill see what I can do know

ALso, I have a problem, everytime I git pull origin development, I get this merging conflict. Once I was fixing it with Yoshi, and I have to accept incoming changes on the file I did not touch.
Also today when call with Rosa, she mentioned the same problem. IS anyone know what could be the problem when git pull origin development?

Hallo Happy Llamas!
I have made the revision for the frontend - backend connection.
Now users can create a new project and click the 'save project', the input is successfully saved in the database.
@yoshimalaise @dirk-jacobs
thank you for the help @Moamin-AbuEwaida @RosaMoran :)

LGTM now :laughing:


Patching issue for quest patcher

I have a mac and and keep getting patching issue here's the message:
QuestPatcher.Core.SigningException: Destination file for signing /var/folders/fx/lgk0gm852v1djw30chzbvw_40000gn/T/QuestPatcher/patching/patched-debugSigned.apk already exists
at QuestPatcher.Core.ApkTools.SignApk(String apkPath, Boolean useZipAlign) in /Users/runner/work/QuestPatcher/QuestPatcher/QuestPatcher.Core/ApkTools.cs:line 107
at QuestPatcher.Core.Patching.PatchingManager.PatchApp() in /Users/runner/work/QuestPatcher/QuestPatcher/QuestPatcher.Core/Patching/PatchingManager.cs:line 431
at QuestPatcher.ViewModels.PatchingViewModel.StartPatching() in /Users/runner/work/QuestPatcher/QuestPatcher/QuestPatcher/ViewModels/PatchingViewModel.cs:line 59
Here's the log:
[2023-06-19 18:06:38 DBG] Saving default config file . . .
[2023-06-19 18:06:38 INF] Loading config . . .
[2023-06-19 18:06:38 DBG] QuestPatcherService constructed
[2023-06-19 18:06:39 INF] Starting QuestPatcher . . .
[2023-06-19 18:06:39 INF] Downloading openjre . . .
[2023-06-19 18:06:44 INF] Extracting . . .
[2023-06-19 18:06:45 INF] Downloading platform-tools . . .
[2023-06-19 18:06:47 INF] Extracting . . .
[2023-06-19 18:06:47 DBG] Executing ADB command: adb shell pm list packages com.AnotherAxiom.GorillaTag
[2023-06-19 18:06:47 VRB] Standard output: ""
[2023-06-19 18:06:47 VRB] Error output: "* daemon not running; starting now at tcp:5037

daemon started successfully
adb: no devices/emulators found
"
[2023-06-19 18:06:47 VRB] Exit code: 1
[2023-06-19 18:07:12 VRB] Standard output: ""
[2023-06-19 18:07:12 VRB] Error output: "adb: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
 Falling back to non-zipalign . . .
[2023-06-19 18:08:39 VRB] QuestPatcher.Core.SigningException: Signed APK at /var/folders/fx/lgk0gm852v1djw30chzbvw_40000gn/T/QuestPatcher/patching/patched-aligned-debugSigned.apk was missing, signing must have failed
at QuestPatcher.Core.ApkTools.SignApk(String apkPath, Boolean useZipAlign) in /Users/runner/work/QuestPatcher/QuestPatcher/QuestPatcher.Core/ApkTools.cs:line 119
at QuestPatcher.Core.Patching.PatchingManager.PatchApp() in /Users/runner/work/QuestPatcher/QuestPatcher/QuestPatcher.Core/Patching/PatchingManager.cs:line 391
[2023-06-19 18:08:59 VRB] Standard output: source:
/private/var/folders/fx/lgk0gm852v1djw30chzbvw_40000gn/T/QuestPatcher/patching
keystore:
[0] 161a0018 /private/var/folders/fx/lgk0gm852v1djw30chzbvw_40000gn/T/temp_4791580311231226693_debug.keystore (DEBUG_EMBEDDED)

patched.apk
SIGN
file: /private/var/folders/fx/lgk0gm852v1djw30chzbvw_40000gn/T/QuestPatcher/patching/patched.apk (408.84 MiB)
checksum: 1fe85ddcd82dc594256ca835d6eb125285d8d345f91d6207c3ac9039c295548d (sha256)

sign success

VERIFY
file: /private/var/folders/fx/lgk0gm852v1djw30chzbvw_40000gn/T/QuestPatcher/patching/patched-debugSigned.apk (408.85 MiB)
checksum: 4a143b0a03c51a404c2f00b9f5a81d75da9d7f39244cd893d2166c22f8e66b89 (sha256)

signature verified [v3]
Subject: CN=Android Debug, OU=Android, O=US, L=US, ST=US, C=US
SHA256: 1e08a903aef9c3a721510b64ec764d01d3d094eb954161b62544ea8f187b5953 / SHA256withRSA
Expires: Thu Mar 10 12:10:05 PST 2044

[Mon Jun 19 18:08:59 PDT 2023][v1.2.1]
Successfully processed 1 APKs and 0 errors in 19.18 seconds.
Cmd history for debugging purpose:
[2023-06-19 18:08:59 INF] Uninstalling the default APK . . .
[2023-06-19 18:08:59 DBG] Executing ADB command: adb uninstall com.AnotherAxiom.GorillaTag
[2023-06-19 18:08:59 VRB] Standard output: "Success
"
[2023-06-19 18:08:59 VRB] Exit code: 0
[2023-06-19 18:08:59 INF] Installing the modded APK . . .
[2023-06-19 18:08:59 DBG] Executing ADB command: adb install "/var/folders/fx/lgk0gm852v1djw30chzbvw_40000gn/T/QuestPatcher/patching/patched-debugSigned.apk"
[2023-06-19 18:09:06 VRB] Standard output: "Performing Streamed Install
"
[2023-06-19 18:09:06 VRB] Error output: "adb: failed to install /var/folders/fx/lgk0gm852v1djw30chzbvw_40000gn/T/QuestPatcher/patching/patched-debugSigned.apk:
"
[2023-06-19 18:09:06 VRB] Exit code: 1
[2023-06-19 18:09:06 ERR] Patching failed!: QuestPatcher.Core.AdbException: Performing Streamed Install
adb: failed to install /var/folders/fx/lgk0gm852v1djw30chzbvw_40000gn/T/QuestPatcher/patching/patched-debugSigned.apk:
at QuestPatcher.Core.AndroidDebugBridge.RunCommand(String command, Int32[] allowedExitCodes) in /Users/runner/work/QuestPatcher/QuestPatcher/QuestPatcher.Core/AndroidDebugBridge.cs:line 147
at QuestPatcher.Core.AndroidDebugBridge.InstallApp(String apkPath) in /Users/runner/work/QuestPatcher/QuestPatcher/QuestPatcher.Core/AndroidDebugBridge.cs:line 220
at QuestPatcher.Core.Patching.PatchingManager.PatchApp() in /Users/runner/work/QuestPatcher/QuestPatcher/QuestPatcher.Core/Patching/PatchingManager.cs:line 425
at QuestPatcher.ViewModels.PatchingViewModel.StartPatching() in /Users/runner/work/QuestPatcher/QuestPatcher/QuestPatcher/ViewModels/PatchingViewModel.cs:line 59
[2023-06-19 18:09:23 INF] Copying APK to patched location . . .
[2023-06-19 18:09:24 INF] Copying files to patch APK . . .
[2023-06-19 18:09:24 INF] Checking index for unstripped libunity.so . . .
[2023-06-19 18:09:24 WRN] Unstripped libunity found for other versions of this app, but not 1.1.49
[2023-06-19 18:09:32 INF] Copying libmain.so and libmodloader.so . . .
[2023-06-19 18:09:32 INF] Patching manifest . . .
[2023-06-19 18:09:32 INF] Loading manifest as AXML . . .
[2023-06-19 18:09:32 INF] Adding permission android.permission.READ_EXTERNAL_STORAGE
[2023-06-19 18:09:32 INF] Adding permission android.permission.WRITE_EXTERNAL_STORAGE
[2023-06-19 18:09:32 INF] Adding permission android.permission.MANAGE_EXTERNAL_STORAGE
[2023-06-19 18:09:32 INF] Adding legacy external storage flag . . .
[2023-06-19 18:09:32 INF] Saving manifest as AXML . . .
[2023-06-19 18:09:32 INF] Adding tag . . .
[2023-06-19 18:09:32 INF] Closing APK archive . . .
[2023-06-19 18:09:33 INF] Signing APK (this might take a while) . . .
[2023-06-19 18:09:36 VRB] Standard output: source:
/private/var/folders/fx/lgk0gm852v1djw30chzbvw_40000gn/T/QuestPatcher/patching
zipalign location: BUILT_IN
/var/folders/fx/lgk0gm852v1djw30chzbvw_40000gn/T/uapksigner-4422954069121723176/mac-zipalign-29_0_212273262529072127937.tmp
keystore:
[0] 161a0018 /private/var/folders/fx/lgk0gm852v1djw30chzbvw_40000gn/T/temp_992397881021711400_debug.keystore (DEBUG_EMBEDDED)

patched.apk
SIGN
file: /private/var/folders/fx/lgk0gm852v1djw30chzbvw_40000gn/T/QuestPatcher/patching/patched.apk (408.84 MiB)
checksum: 6dcdfc87ed7d8621fba43bc1d97359d5b59fafca2c4f1bce2bc94ae0357c9496 (sha256)

could not align

[2023-06-19 18:09:36 VRB] Error output: could not execute zipalign
java.lang.IllegalStateException: could not execute zipalign
at at.favre.tools.apksigner.SignTool.execute(SignTool.java:143)
at at.favre.tools.apksigner.SignTool.mainExecute(SignTool.java:45)
at at.favre.tools.apksigner.SignTool.main(SignTool.java:33)
Cmd history for debugging purpose:
[/var/folders/fx/lgk0gm852v1djw30chzbvw_40000gn/T/uapksigner-4422954069121723176/mac-zipalign-29_0_212273262529072127937.tmp, -p, -v, 4, /var/folders/fx/lgk0gm852v1djw30chzbvw_40000gn/T/QuestPatcher/patching/patched.apk, /var/folders/fx/lgk0gm852v1djw30chzbvw_40000gn/T/QuestPatcher/patching/patched-aligned.apk]
(-1)
[2023-06-19 18:09:36 WRN] Signing the APK failed with zipalign enabled. Falling back to non-zipalign . . .
[2023-06-19 18:09:36 VRB] QuestPatcher.Core.SigningException: Signed APK at /var/folders/fx/lgk0gm852v1djw30chzbvw_40000gn/T/QuestPatcher/patching/patched-aligned-debugSigned.apk was missing, signing must have failed
at QuestPatcher.Core.ApkTools.SignApk(String apkPath, Boolean useZipAlign) in /Users/runner/work/QuestPatcher/QuestPatcher/QuestPatcher.Core/ApkTools.cs:line 119
at QuestPatcher.Core.Patching.PatchingManager.PatchApp() in /Users/runner/work/QuestPatcher/QuestPatcher/QuestPatcher.Core/Patching/PatchingManager.cs:line 391
[2023-06-19 18:09:36 ERR] Patching failed!: QuestPatcher.Core.SigningException: Destination file for signing /var/folders/fx/lgk0gm852v1djw30chzbvw_40000gn/T/QuestPatcher/patching/patched-debugSigned.apk already exists
at QuestPatcher.Core.ApkTools.SignApk(String apkPath, Boolean useZipAlign) in /Users/runner/work/QuestPatcher/QuestPatcher/QuestPatcher.Core/ApkTools.cs:line 107
at QuestPatcher.Core.Patching.PatchingManager.PatchApp() in /Users/runner/work/QuestPatcher/QuestPatcher/QuestPatcher.Core/Patching/PatchingManager.cs:line 399
at QuestPatcher.ViewModels.PatchingViewModel.StartPatching() in /Users/runner/work/QuestPatcher/QuestPatcher/QuestPatcher/ViewModels/PatchingViewModel.cs:line 59
[2023-06-19 18:09:51 INF] Copying APK to patched location . . .
[2023-06-19 18:09:52 INF] Copying files to patch APK . . .
[2023-06-19 18:09:52 INF] Checking index for unstripped libunity.so . . .
[2023-06-19 18:09:52 WRN] Unstripped libunity found for other versions of this app, but not 1.1.49
[2023-06-19 18:10:00 INF] Copying libmain.so and libmodloader.so . . .
[2023-06-19 18:10:00 INF] Patching manifest . . .
[2023-06-19 18:10:00 INF] Loading manifest as AXML . . .
[2023-06-19 18:10:00 INF] Adding permission android.permission.READ_EXTERNAL_STORAGE
[2023-06-19 18:10:00 INF] Adding permission android.permission.WRITE_EXTERNAL_STORAGE
[2023-06-19 18:10:00 INF] Adding permission android.permission.MANAGE_EXTERNAL_STORAGE
[2023-06-19 18:10:00 INF] Adding legacy external storage flag . . .
[2023-06-19 18:10:00 INF] Saving manifest as AXML . . .
[2023-06-19 18:10:00 INF] Adding tag . . .
[2023-06-19 18:10:00 INF] Closing APK archive . . .
[2023-06-19 18:10:01 INF] Signing APK (this might take a while) . . .
[2023-06-19 18:10:03 VRB] Standard output: source:
/private/var/folders/fx/lgk0gm852v1djw30chzbvw_40000gn/T/QuestPatcher/patching
zipalign location: BUILT_IN
/var/folders/fx/lgk0gm852v1djw30chzbvw_40000gn/T/uapksigner-12686606255113776705/mac-zipalign-29_0_24375456920356243332.tmp
keystore:
[0] 161a0018 /private/var/folders/fx/lgk0gm852v1djw30chzbvw_40000gn/T/temp_3276177080679992689_debug.keystore (DEBUG_EMBEDDED)

patched.apk
SIGN
file: /private/var/folders/fx/lgk0gm852v1djw30chzbvw_40000gn/T/QuestPatcher/patching/patched.apk (408.84 MiB)
checksum: 450477d1fc3e9a389b73fd84bd3f25bd803504ff639565e8ac1d4eac24c31b64 (sha256)

could not align

[2023-06-19 18:10:03 VRB] Error output: could not execute zipalign
java.lang.IllegalStateException: could not execute zipalign
at at.favre.tools.apksigner.SignTool.execute(SignTool.java:143)
at at.favre.tools.apksigner.SignTool.mainExecute(SignTool.java:45)
at at.favre.tools.apksigner.SignTool.main(SignTool.java:33)
Cmd history for debugging purpose:
[/var/folders/fx/lgk0gm852v1djw30chzbvw_40000gn/T/uapksigner-12686606255113776705/mac-zipalign-29_0_24375456920356243332.tmp, -p, -v, 4, /var/folders/fx/lgk0gm852v1djw30chzbvw_40000gn/T/QuestPatcher/patching/patched.apk, /var/folders/fx/lgk0gm852v1djw30chzbvw_40000gn/T/QuestPatcher/patching/patched-aligned.apk]
(-1)
[2023-06-19 18:10:03 WRN] Signing the APK failed with zipalign enabled. Falling back to non-zipalign . . .
[2023-06-19 18:10:03 VRB] QuestPatcher.Core.SigningException: Signed APK at /var/folders/fx/lgk0gm852v1djw30chzbvw_40000gn/T/QuestPatcher/patching/patched-aligned-debugSigned.apk was missing, signing must have failed
at QuestPatcher.Core.ApkTools.SignApk(String apkPath, Boolean useZipAlign) in /Users/runner/work/QuestPatcher/QuestPatcher/QuestPatcher.Core/ApkTools.cs:line 119
at QuestPatcher.Core.Patching.PatchingManager.PatchApp() in /Users/runner/work/QuestPatcher/QuestPatcher/QuestPatcher.Core/Patching/PatchingManager.cs:line 391
[2023-06-19 18:10:03 ERR] Patching failed!:  Falling back to non-zipalign . . .
[2023-06-19 18:13:22 VRB] QuestPatcher.Core.SigningException: Signed APK at /var/folders/fx/lgk0gm852v1djw30chzbvw_40000gn/T/QuestPatcher/patching/patched-aligned-debugSigned.apk was missing, signing must have failed
at QuestPatcher.Core.ApkTools.SignApk(String apkPath, Boolean useZipAlign) in /Users/runner/work/QuestPatcher/QuestPatcher/QuestPatcher.Core/ApkTools.cs:line 119
at QuestPatcher.Core.Patching.PatchingManager.PatchApp() in /Users/runner/work/QuestPatcher/QuestPatcher/QuestPatcher.Core/Patching/PatchingManager.cs:line 431
[2023-06-19 18:13:22 ERR] Patching failed!:  Falling back to non-zipalign . . .
[2023-06-19 18:15:21 VRB] QuestPatcher.Core.SigningException: Signed APK at /var/folders/fx/lgk0gm852v1djw30chzbvw_40000gn/T/QuestPatcher/patching/patched-aligned-debugSigned.apk was missing, signing must have failed
at QuestPatcher.Core.ApkTools.SignApk(String apkPath, Boolean useZipAlign) in /Users/runner/work/QuestPatcher/QuestPatcher/QuestPatcher.Core/ApkTools.cs:line 119
at QuestPatcher.Core.Patching.PatchingManager.PatchApp() in /Users/runner/work/QuestPatcher/QuestPatcher/QuestPatcher.Core/Patching/PatchingManager.cs:line 431
[2023-06-19 18:15:21 ERR] Patching failed!: QuestPatcher.Core.SigningException: Destination file for signing /var/folders/fx/lgk0gm852v1djw30chzbvw_40000gn/T/QuestPatcher/patching/patched-debugSigned.apk already exists
at QuestPatcher.Core.ApkTools.SignApk(String apkPath, Boolean useZipAlign) in /Users/runner/work/QuestPatcher/QuestPatcher/QuestPatcher.Core/ApkTools.cs:line 107
at QuestPatcher.Core.Patching.PatchingManager.PatchApp() in /Users/runner/work/QuestPatcher/QuestPatcher/QuestPatcher.Core/Patching/PatchingManager.cs:line 431
at QuestPatcher.ViewModels.PatchingViewModel.StartPatching() in /Users/runner/work/QuestPatcher/QuestPatcher/QuestPatcher/ViewModels/PatchingViewModel.cs:line 59
[2023-06-19 18:19:58 INF] Copying APK to patched location . . .
[2023-06-19 18:19:58 INF] Copying files to patch APK . . .
[2023-06-19 18:19:59 INF] Checking index for unstripped libunity.so . . .
[2023-06-19 18:19:59 WRN] Unstripped libunity found for other versions of this app, but not 1.1.49
[2023-06-19 18:20:00 INF] Copying libmain.so and libmodloader.so . . .
[2023-06-19 18:20:00 INF] Patching manifest . . .
[2023-06-19 18:20:00 INF] Loading manifest as AXML . . .
[2023-06-19 18:20:00 INF] Adding permission android.permission.READ_EXTERNAL_STORAGE
[2023-06-19 18:20:00 INF] Adding permission android.permission.WRITE_EXTERNAL_STORAGE
[2023-06-19 18:20:00 INF] Adding permission android.permission.MANAGE_EXTERNAL_STORAGE
[2023-06-19 18:20:00 INF] Adding legacy external storage flag . . .
[2023-06-19 18:20:00 INF] Saving manifest as AXML . . .
[2023-06-19 18:20:00 INF] Adding tag . . .
[2023-06-19 18:20:00 INF] Closing APK archive . . .
[2023-06-19 18:20:02 INF] Signing APK (this might take a while) . . .
[2023-06-19 18:20:04 VRB] Standard output: source:
/private/var/folders/fx/lgk0gm852v1djw30chzbvw_40000gn/T/QuestPatcher/patching
zipalign location: BUILT_IN
/var/folders/fx/lgk0gm852v1djw30chzbvw_40000gn/T/uapksigner-2778656572203386508/mac-zipalign-29_0_22978270718218575007.tmp
keystore:
[0] 161a0018 /private/var/folders/fx/lgk0gm852v1djw30chzbvw_40000gn/T/temp_14409544584695284860_debug.keystore (DEBUG_EMBEDDED)

patched.apk
SIGN
file: /private/var/folders/fx/lgk0gm852v1djw30chzbvw_40000gn/T/QuestPatcher/patching/patched.apk (408.84 MiB)
checksum: 942e611a27c4d4094e321a47bf42a4c7790c17e4ba229a8ceed3a375548754cb (sha256)

could not align

[2023-06-19 18:20:04 VRB] Error output: could not execute zipalign
java.lang.IllegalStateException: could not execute zipalign
at at.favre.tools.apksigner.SignTool.execute(SignTool.java:143)
at at.favre.tools.apksigner.SignTool.mainExecute(SignTool.java:45)
at at.favre.tools.apksigner.SignTool.main(SignTool.java:33)
Cmd history for debugging purpose:
[/var/folders/fx/lgk0gm852v1djw30chzbvw_40000gn/T/uapksigner-2778656572203386508/mac-zipalign-29_0_22978270718218575007.tmp, -p, -v, 4, /var/folders/fx/lgk0gm852v1djw30chzbvw_40000gn/T/QuestPatcher/patching/patched.apk, /var/folders/fx/lgk0gm852v1djw30chzbvw_40000gn/T/QuestPatcher/patching/patched-aligned.apk]
(-1)
[2023-06-19 18:20:04 WRN] Signing the APK failed with zipalign enabled. Falling back to non-zipalign . . .
[2023-06-19 18:20:04 VRB] QuestPatcher.Core.SigningException: Signed APK at /var/folders/fx/lgk0gm852v1djw30chzbvw_40000gn/T/QuestPatcher/patching/patched-aligned-debugSigned.apk was missing, signing must have failed
at QuestPatcher.Core.ApkTools.SignApk(String apkPath, Boolean useZipAlign) in /Users/runner/work/QuestPatcher/QuestPatcher/QuestPatcher.Core/ApkTools.cs:line 119
at QuestPatcher.Core.Patching.PatchingManager.PatchApp() in /Users/runner/work/QuestPatcher/QuestPatcher/QuestPatcher.Core/Patching/PatchingManager.cs:line 431
[2023-06-19 18:20:04 ERR] Patching failed!:  Falling back to non-zipalign . . .
[2023-06-19 18:20:40 VRB] QuestPatcher.Core.SigningException: Signed APK at /var/folders/fx/lgk0gm852v1djw30chzbvw_40000gn/T/QuestPatcher/patching/patched-aligned-debugSigned.apk was missing, signing must have failed
at QuestPatcher.Core.ApkTools.SignApk(String apkPath, Boolean useZipAlign) in /Users/runner/work/QuestPatcher/QuestPatcher/QuestPatcher.Core/ApkTools.cs:line 119
at QuestPatcher.Core.Patching.PatchingManager.PatchApp() in /Users/runner/work/QuestPatcher/QuestPatcher/QuestPatcher.Core/Patching/PatchingManager.cs:line 431
[2023-06-19 18:20:40 ERR] Patching failed!: QuestPatcher.Core.SigningException: Destination file for signing /var/folders/fx/lgk0gm852v1djw30chzbvw_40000gn/T/QuestPatcher/patching/patched-debugSigned.apk already exists
at QuestPatcher.Core.ApkTools.SignApk(String apkPath, Boolean useZipAlign) in /Users/runner/work/QuestPatcher/QuestPatcher/QuestPatcher.Core/ApkTools.cs:line 107
at QuestPatcher.Core.Patching.PatchingManager.PatchApp() in /Users/runner/work/QuestPatcher/QuestPatcher/QuestPatcher.Core/Patching/PatchingManager.cs:line 431
at QuestPatcher.ViewModels.PatchingViewModel.StartPatching() in /Users/runner/work/QuestPatcher/QuestPatcher/QuestPatcher/ViewModels/PatchingViewModel.cs:line 59

You're using a very outdated version of QuestPatcher. Please update to the latest release


[WIP] Add scissor option to bandplot

Hi all, I thought a scissor option might be useful. I'm not familiar with the structure of the sumo code but this seemed like a logical place to add it.

Looks great. Any reason not to merge?

Might be worth thinking about the interaction/consistency with that proposal to set an optional Fermi level and/or add a horizontal line.

This shifts using the pymatgen scissor operator which shifts the conduction band energies and keeps the valence bands fixed. As long as a Fermi level / horizontal line is defined relative to the VBM I think this should be fine.

Should be pretty safe then


Mailto links on Casper?

Hey guys
I noticed that we merged a PR a long time ago to enable mailto: links as navigation items.
Ref. https://github.com/TryGhost/Ghost/pull/5013
Using Ghost 0.6.4, I am able to enter the mailto: url without issues and save the link.
However, on the frontend it doesn't use the saved mailto: value but instead points to the the blog's base URL.
Could this be an issue in Ghost, or would this be an issue related to https://github.com/TryGhost/Casper?
Using Casper 1.2.4.

Hi @MichielDeMey I'm not able to reproduce this issue on Ghost 0.6.4 with Casper (I tested it out on Ghost pro and it worked just fine), I did find a regression in master, but I'll sort that out separately. I recommend swinging by our slack channel so that we can help you troubleshoot what's going on in your case.

Reopening as bug report updated with reproducible case :+1:


perceivedExertion not being expanded in template

I have a calendar template like this:
${distance} @ ${speedAvg} (${perceivedExertion})
${elevationGain} (${climbingRatio})
${hrAvg}, ${wattsAvg}
Ride: ${gear}

But the resulting entries in ical look like this:
42.2mi @ 13mph (${perceivedExertion})
981ft (0.23)
145bpm, 149watts
Ride: Rove

I think the issue is simply that the value was left unset for the last two rides, and the template  chooses to leave the value unexpanded rather than using nil or unset as the interpolated text.


Does still preview version of Visual Studio 2022 may affect the result?

In prerequisites section of README.md file is stated that VS 2022 Preview 3 or later would bring the best result.
As visual Studio 2022 (17.0) was released about a year ago and still there are preview versions for next minor release (currently 17.3 preview), I think this statement should be updated to simply saying Visual Studio 2022 or specifying the exact minor version it need for best result.

You're right, the README hasn't been updated since VS 2022 was released. It should work fine with 17.0 or later. No need for preview builds. We'll update the README.


gpio: api to query pin configuration

Is your enhancement proposal related to a problem? Please describe.
In some cases, it's necessary to query the configuration (e.g. direction) of a particular GPIO pin. However, the existing GPIO API does not seem to provide a way to do that.
Describe the solution you'd like
__subsystem struct gpio_driver_api {
        // ...
        // deprecate this call. make it wrap gpio_set_config() instead
	int (*pin_configure)(struct device *port, gpio_pin_t pin, gpio_flags_t flags);
        // this call would be set up to simply call pin_configure
        int (*pin_set_config)(struct device *port, gpio_pin_t pin, gpio_flags_t flags);
        // this call would return the current pin configuration
        int (*pin_get_config)(struct device *port, gpio_pin_t pin, gpio_flags_t *flags);
        // ...
};

__syscall int gpio_set_config(struct device *port, gpio_pin_t pin,
			  gpio_flags_t flags);

__syscall int gpio_get_config(struct device *port, gpio_pin_t pin,
			  gpio_flags_t *flags);

// deprecate this call. make it wrap gpio_set_config() instead
__syscall int gpio_config(struct device *port, gpio_pin_t pin,
			  gpio_flags_t flags);

Describe alternatives you've considered
It's possible that gpio configuration registers may be write-only on some hardware, and perhaps that's the reason that this feature was not added originally. In those cases, I would expect that a simple bitmap is used internally instead of querying hardware.
Additional context

Could you elaborate a bit more on the use case for this?
I mean, normally you'd either have fixed input or output, or have the direction controlled by a driver, which could keep track of when to change the direction internally.
When would you need to query the direction?

Could you elaborate a bit more on the use case for this?

Sure - I'll be using it to implement Greybus GPIO support.

When would you need to query the direction?

Anytime there is a service that reports the current state of GPIO.


CIP-0030 normalize wallet names

Creating an issue with the intent to create a CIP unless there is some obvious reason not to.
See the image below; the window.cardano[name] and window.cardano.[name].name can differ in case (and perhaps in other ways as well). This makes it unnecessarily hard to dynamically iterate available wallets, with the intent to window.cardano[key].enable() it.
I suggest to normalize the names to always be lowercase, and fully match the key they are registered under. If needed, we could instead add an additional property, key which must match the corresponding key in window.cardano.
The point against this is that this can be derrived by the key itself, but this just adds more complexity where it does not need to be.
CC @alessandrokonrad

@GGAlanSmithee referencing https://github.com/cardano-foundation/CIPs/pull/446 since it looks like there is some improvement being made in this area.


Scheduled task interval does not change

I'm trying to use this with Sitecore 8.2. Per issue #6, I have adjusted the interval of all Sitecore.Tasks.DatabaseAgent agents (and Sitecore.Tasks.TaskDatabaseAgent) to 30 seconds so we can get a more immediate timing. However, for some reason it still only appears to do an automatic publish every 10 minutes. Do I have to do something different in Sitecore 8.2?
Thank you.

Oh, I just found the setting in the Tasks/Schedules path.
For anyone else confused about how to get it to fire more frequently, you also need to update the item at Sitecore/System/Tasks/Schedules/Scheduled Publish Task. It has a field named Schedule which is pipe delimited. The last item in that field is a frequency timer which you should set to how frequent you want it to run.


Crouton Crashing On Chromebook

When I Do sudo startxfce4, my chromebook crashes and be stuck on black screen and i have to force it to shutdown to go back to chrome OS. is there a way to fix this?

Please show us the output of: sudo edit-chroot -all

name: trusty
encrypted: no
Entering /mnt/stateful_partition/crouton/chroots/trusty...
crouton: version 1-20181001133934~master:38012fdf
release: trusty
architecture: amd64
xmethod: xorg
targets: xfce
host: version 11298.0.0 (Official Build) canary-channel celes
kernel: Linux localhost 3.18.0-18738-gdf8697848d55 #1 SMP PREEMPT Mon Nov 26 04:02:56 PST 2018 x86_64 x86_64 x86_64 GNU/Linux
freon: yes
Unmounting /mnt/stateful_partition/crouton/chroots/trusty...

@HRA2000,

When did it start doing this, after a Chrome OS update, a crouton chroot update, etc.?
Do you get any error messages at all?
Will it switch back to Chrome OS when you press ctrl+alt+shift+F1/F2?
Will the display come back if you toggle the full screen key?

-DennisLfromGA

Okay, thanx for the feedback and glad it's working again.
Closing. Please re-open if this issue is still a concern.


[SPARK-28152][SQL][2.4] Mapped ShortType to SMALLINT and FloatType to REAL for MsSqlServerDialect

What changes were proposed in this pull request?
This is a backport of SPARK-28152 to Spark 2.4. Because the fix in 3.0 was based on different base files, following relevant fixes have also been cherry-picked as part of this fix.

[SPARK-27159][SQL] update mssql server dialect to support binary type
SPARK-27168 [SQL][TEST] Add docker integration test for MsSql server

SPARK-28152  corrects mappings in MsSqlServerDialect. Post fix ShortType is mapped to SMALLINT and FloatType is mapped to REAL per JBDC mapping respectively.
ShortType and FloatTypes are not correctly mapped to right JDBC types when using JDBC connector. This results in tables and spark data frame being created with unintended types. The issue was observed when validating against SQLServer.
Refer JBDC mapping for guidance on mappings between SQLServer, JDBC and Java. Note that java "Short" type should be mapped to JDBC "SMALLINT" and java Float should be mapped to JDBC "REAL".
Some example issue that can happen because of wrong mappings
- Write from df with column type results in a SQL table of with column type as INTEGER as opposed to SMALLINT.Thus a larger table that expected.
- Read results in a dataframe with type INTEGER as opposed to ShortType

ShortType has a problem in both the the write and read path
FloatTypes only have an issue with read path. In the write path Spark data type 'FloatType' is correctly mapped to JDBC equivalent data type 'Real'. But in the read path when JDBC data types need to be converted to Catalyst data types ( getCatalystType) 'Real' gets incorrectly gets mapped to 'DoubleType' rather than 'FloatType'.

How was this patch tested?
Integration test using : ./build/mvn test -Pdocker-integration-tests -pl :spark-docker-integration-tests_2.11 -Dtest=none -DwildcardSuites=org.apache.spark.sql.jdbc.MsSqlServerIntegrationSuite
(Please explain how this patch was tested. E.g. unit tests, integration tests, manual tests)
(If this patch involves UI changes, please attach a screenshot; otherwise, remove this)
Please review https://spark.apache.org/contributing.html before opening a pull request.

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

ok to test

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/13176/
Test PASSed.

Welcome back, @shivsood . But, I guess SPARK-27168 should not be here.

Test build #108069 has started for PR 25238 at commit 277fda0.

Also, SPARK-27159 should not be here. Let me handle them for you.

Please rebase this PR against branch-2.4, @shivsood .

Test build #108069 has finished for PR 25238 at commit 277fda0.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/108069/
Test PASSed.

should not be here. Let me handle them
I can submit a separate PR for SPARK-27159. Can u please help me understand the reason. Is it because we will loose attribution as a result of squash when PR is merged. If so that would happen for  SPARK-27168 also and i should submit all these cherry-picks as separate PRs.  Please let me know and i can fix this.

Making this WIP till i fix these issues.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/13224/
Test PASSed.

@dongjoon-hyun i will close this PR and raise a new one. I messed up this branch. Do you want me to submit as 3PRs for the following commit  or 1 PR. My understanding is 3 PRs. So they would have to be in the following sequence.
[SPARK-27159][SQL] update mssql server dialect to support binary type
[SPARK-27168] [SQL][TEST] Add docker integration test for MsSql server
[SPARK-28152][SQL] Mapped ShortType to SMALLINT and FloatType to REAL for   MsSqlServerDialect

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/108119/
Test FAILed.

@shivsood . Please check the branch-2.4 first. :)

https://github.com/apache/spark/commits/branch-2.4

@shivsood . Please check the branch-2.4 first. :)
* https://github.com/apache/spark/commits/branch-2.4

@dongjoon-hyun  Awesome. thanks for pulling the dependency commit in. 'll submit my PR on top of these. Thanks.

Yep. Thanks!

Create a new PR https://github.com/apache/spark/pull/25248


Switch out HTTPotion for Tesla?

https://github.com/monterail/tesla

WARNING: Tesla is currently under heavy development, so please don't use it in your production application just yet.

@KamilLelonek Yeah, that's what is holding me back from using it right now. For now, I'm sticking with HTTPotion.

We use httpoison for everything else in our app (which uses hackney underneath). Why use potion or tesla?

Not going to do this. If anything, I'd rather switch to HTTPoison, since many Elixir apps seem to already depend on Hackney.


Cannot read property 'toJS' of undefined, even after adding to global reducer

When generating a new container, I get the following error from the generated selector.
Uncaught (in promise) TypeError: Cannot read property 'toJS' of undefined
After some googling, it seems like this is a common gotcha and you just need to add the reducer to the global combineReducers function, which I did here:
export default function createReducer(asyncReducers) {
  return combineReducers({
    route: routeReducer,
    language: languageProviderReducer,
    bingo: bingoCardReducer, // <- My added reducer.
    ...asyncReducers,
  });
}

However the error remains. It seems like the substate is never being initialized, even though when I call bingoCardReducer(undefined,'test'), I can confirm the state is initialized correctly. Has anyone else run into this problem?

Figured it out:
You have to add it to the reducer, with the name equal to the same one you see here in selectors.js
const selectBingoCardDomain = () => (state) => state.get('bingoCard');
Hopefully this helps someone else who encounters the same issue.


Automatically fill browser version for bug issue template

This can be closed since we added Sentry for error reporting.


Hint for kernel page chache problem in older kubernetes versions

This note would have saved me several hours of research... PR is ready when update of kubernetes fixes the problem

@Kraego Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

@Kraego Thank you for signing the Contributor License Agreement!

@Kraego if you suggest that we mention that the K8S/cgroups combination that reports kernel page cache as "memory used by the pod" (app), which is not really correct, we can do it today.
Kubernetes 1.25 with cgroups v2 support has been out for more than a year.
Any reasons why we should not make the docs say something like "this affects Kubernetes installations older than 1.25 and Linux distributions that use cgroups v1"?

I've edited this a bit and manually merged it into live


Re-enable prebuilt leak detection in master

As part of updating the master branch to 5.0, prebuilt leak detection was disabled until the entire product is built.  This should be re-enabled once the master branch builds through core-sdk.

[Triage] prebuilt detection is now enabled in all supported source-build versions.


added flexbox for motion sponsors

Added a small example to March 23 OP on how we could use flexbox for the motion sponsor section. I've not copied the indentation of the original HTML as I wasn't sure if you planned to do more indenting with the new HTML

Hi @jack-912  I have responded on Teams.


Github actions will be deprecating the use of ::set-output and moving to Environment Variables

When the action runs we get this warning:
Warning: The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

Other than that that's it. Thanks

Alright thank you for letting me know, I will get round to sorting this soon.

I have tried fixing this following the information on the github blog post but to no success, this should just have gone away by updating @actions/core to 1.10.0 but currently no success (i.e. we shouldn't have this issue to begin with). I am just going to come back to this possibly in a month or two, see if https://github.com/actions/toolkit/issues sorts itself out.

Sure thing. As far as I can tell aws-actions devs did the same with @actions/core. Thanks for checking it out.

I just remembered that FYI: save-state is also deprecating. aws-actions/ecr-login is a reference that has the same issue w/ the save-state. Maybe that helps out.

@jbutcher5 Did you have any luck resolving this issue?

@kennyheard honestly I have lost all interest in maintaining this repository. If there was a pr made for it I would happily look over it and merge it but otherwise I am just going to work on other things and not update this repo.

The only use of set-output that I see in this repo is in https://github.com/jbutcher5/read-yaml/blob/d1d6dd064c2e3e16b06bcc973ce4ec103898b2a2/dist/index.js#L365 -- it looks like this is a generated file and was last updated in 2021. Does it need to be regenerated?

@deejgregor That might just be the issue, I'll check this out briefly today.


iOS 13 adaptation

Need to adapt the App on the AppStore？ or Apple will do it yourself?

Need to adapt the App on the AppStore？ or Apple will do it yourself?

If your app use CNCopyCurrentNetworkInfo(). You have to update your code and release a new version. Otherwise your app will not work on iOS 13.


typo in documentation

Description
In the getting started guide there is a minor typo in the code snippet for the playground example.
`async fn main() -> loco_re::Result<()> {
let ctx = playground::().await?;
// add this:
let active_model: articles::ActiveModel = articles::ActiveModel {
    title: Set(Some("how to build apps in 3 steps".to_string())),
    content: Set(Some("use Loco: https://loco.rs".to_string())),
    ..Default::default()
};
active_model.insert(&ctx.db).await.unwrap();

let res = articles::Entity::find().all(&ctx.db).await.unwrap();
println!("{:?}", res);

Ok(())

}`
Return type shoule be loco_rs::Result<()>
(Minor issue as mentioned... Thanks!)

I have noticed another couple of minor issues with the user_report example in the guide:
use loco_rs::prelude::*;
use loco_rs::task::Vars;

use crate::models::users;

#[async_trait]
impl Task for UserReport {
    fn task(&self) -> TaskInfo {
      // description that appears on the CLI
        TaskInfo {
            name: "user_report".to_string(),
            detail: "output a user report".to_string(),
        }
    }

// variables through the CLI:
// $ cargo loco task name:foobar count:2
// will appear as {"name":"foobar", "count":2} in vars
async fn run(&self, app_context: &AppContext, vars: &BTreeMap<String, String>) -> Result<()> {
    let users = users::Entity::find().all(&app_context.db).await?;
    println!("args: {vars:?}");
    println!("!!! user_report: listing users !!!");
    println!("------------------------");
    for user in &users {
        println!("user: {}", user.email);
    }
    println!("done: {} users", users.len());
    Ok(())
}

}`
the example above is missing pub struct UserReport;
And the function signature is incorrect. the type for the vars variable should be &Vars and not &BTreeMap<String, String>

I would also add that all generate commands are missing the specifier ('html' 'htmx' or 'api')
Thank you so much for creating this framework! I hope I am not being to nit picky with my comments

Thanks for finding these!
Could you submit a PR with your suggested fixes?

It looks like these were fixed by someone else? I think the issue can be closed now


V0.20.1 bugfix release

Context: This bugfix release fixes an issue when building Lightning from source on newer compilers without explicit header-files included. In addition, we also fix a situation where the no-binary wheel fails on testing due to unskipped tests.
Description of the Change: Adds missing headers to source files. Skips unsupported tests.
Benefits: Compiles on newer MSVC. Tests pass.
Possible Drawbacks: None
Related GitHub Issues: https://github.com/PennyLaneAI/pennylane-lightning/issues/192

NOTE: do not merge master onto here, nor resolve conflicts!


Is it possible to just show the title of each commit?

Is it possible to just show the title of each commit, i.e. just the first line of the commit message?
Also, it would be great if there would be documentation on what fields the widetailand csdetail objects do have.
VSTS Extension you are using
Version 2.0 extension
Where are you running it?
VSTS

Just realized I am not sure if you are using the older PowerShell (Windows agent only works in builds and releases) or newer Node (Xplatform works only in releases) version of this extension
However, either way using something like this (assuming PowerShell version, alter the format for Node as require) will just dump the whole of the CS or Wi object so you can see the fields

Thanks for your answer. I tried dumping the whole object but all output I get is [object Object].
I'm using the Xplatform version 2 in my release pipeline.

Off the top of my head does a tostring() help?


Toast is showing vertically in Landscape iPad

JLToastView.setDefaultValue(
            UIColor.redColor(),
            forAttributeName: JLToastViewBackgroundColorAttributeName,
            userInterfaceIdiom: .Pad
        )
        let toast = JLToast.makeText("Testing Toast long toast long toast long toast..")
        toast.show()

@SSamanta, thanks for report! I'll take a look soon. Which version of iPad are you using?

iPad Air

And iOS version please :)

Latest ios 9.3.1. My apps orientation mode only landscape left or right

+1. This is happening on iPad Pro (12.1") as well as in Simulator.
Seems to have happened from the last time I updated JLToast.

yes. Before it was working correctly.

@SSamanta, are you not using LaunchScreen?

@SSamanta, Could you please try with ipad-orientation-launchscreen branch? If you're using CocoaPods, you can just edit your Podfile:
use_frameworks!

target 'YourProject' do

pod 'JLToast', :git => 'https://github.com/devxoul/JLToast', :branch => 'ipad-orientation-launchscreen'

end

and install
$ pod install

@devxoul - we use a LaunchScreen and I updated to the ipad-orientation-launchscreen branch and the issue still exists.

@24601, could you please provide me a sample project that I can test with?

@devxoul I tried LaunchScreen and pod 'JLToast', :git => 'https://github.com/devxoul/JLToast', :branch => 'ipad-orientation-launchscreen'
end both..same issue it's showing in vertically..I am trying to make one sample app..

This bug also happens on my code and the cause is due to statusBarOrientation is deprecated, based on https://developer.apple.com/library/ios/documentation/UIKit/Reference/UIApplication_Class/#//apple_ref/c/tdef/UIInterfaceOrientation
Whenever the following code is run in JLToastView on landscape orientation and iOS 9.3:
        let orientation = UIApplication.sharedApplication().statusBarOrientation
        if orientation.isPortrait || !JLToastWindow.sharedWindow.shouldRotateManually {
            width = containerSize.width
            height = containerSize.height
            y = portraitOffsetY
        } else {
            width = containerSize.height
            height = containerSize.width
            y = landscapeOffsetY
        }

The conditional always goes to portrait, never landscape.

I have found the root causes. If you select all device orientations and tap Off Requires full screen, it works fine. But if you either deselect any of device orientations or tap On Requires full screen, this bug happens.

Ohoo my requirement is landscape and full screen so second case . Are there any way to fix that?

@SSamanta @24601 @willyjl Could you guys please replace shouldRotateManually property of the JLToastWindow with the code above and try again?
/// Don't rotate manually if the application:
///
/// - is running on iOS 9
/// - supports all orientations
/// - doesn't require full screen
///
var shouldRotateManually: Bool {
    let application = UIApplication.sharedApplication()
    let window = application.delegate?.window ?? nil
    let orientationMask = application.supportedInterfaceOrientationsForWindow(window)
    let requiresFullScreen = NSBundle.mainBundle().infoDictionary?["UIRequiresFullScreen"]?.boolValue == true
    if #available(iOS 9, *), orientationMask == .All && !requiresFullScreen {
        return false
    }
    return true
}

I hope it works 🙏

Yup, I tried your solution and it works. Good job @devxoul! Thanks for the quick response. 👍

@SSamanta @24601 @willyjl I just released 1.4.1! If it has problem, please reopen this issue :smile:


NameError: name 'exit' is not defined

Must have

WhatsApp version: <IP_ADDRESS>
OS: iOS - 17.5.1
Platform: Windows
Branch and version: WhatsApp Chat Exporter: 0.10.0 - exe file downloaded today

If it is an error yield by Python, please also provide the trackback
PS C:\wabckp> .\wtsexporter_x64 -i -b "C:\Users\User1\Apple\MobileSync\Backup\00008110-001E490C0AEA901E"
Contact database not found.
Traceback (most recent call last):
  File "C:\Users\User1\AppData\Local\Temp\ONEFIL~1\__main__.py", line 519, in <module>
  File "C:\Users\User1\AppData\Local\Temp\ONEFIL~1\__main__.py", line 406, in main
  File "C:\Users\User1\AppData\Local\Temp\ONEFIL~1\Whatsapp_Chat_Exporter\ios_media_handler.py", line 99, in extract_media
NameError: name 'exit' is not defined

Powershell on Windows 10 Pro , iphone backup made with Apple Devices and later also with iTunes. Both on Windows. Does not work on both.

Could you try to install the tool using pip?

Yes

PS C:\wabckp> python --version
Python 3.12.4

PS C:\wabckp> wtsexporter -i -b "C:\Users\User1\Apple\MobileSync\Backup\00008110-001E490C0AEA901E"
Traceback (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "C:\Users\User1\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.12_qbz5n2kfra8p0\LocalCache\local-packages\Python312\Scripts\wtsexporter.exe\__main__.py", line 4, in <module>
  File "C:\Users\User1\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.12_qbz5n2kfra8p0\LocalCache\local-packages\Python312\site-packages\Whatsapp_Chat_Exporter\__main__.py", line 11, in <module>
    from Whatsapp_Chat_Exporter import ios_handler, ios_media_handler
  File "C:\Users\User1\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.12_qbz5n2kfra8p0\LocalCache\local-packages\Python312\site-packages\Whatsapp_Chat_Exporter\ios_media_handler.py", line 12, in <module>
    from iphone_backup_decrypt import FailedToDecryptError
ImportError: cannot import name 'FailedToDecryptError' from 'iphone_backup_decrypt' (C:\Users\User1\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.12_qbz5n2kfra8p0\LocalCache\local-packages\Python312\site-packages\iphone_backup_decrypt\__init__.py)

Sure.
PS C:\wabckp> python --version
Python 3.12.4

PS C:\wabckp> wtsexporter -i -b "C:\Users\User1\Apple\MobileSync\Backup\00008110-001E490C0AEA901E"
Traceback (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "C:\Users\User1\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.12_qbz5n2kfra8p0\LocalCache\local-packages\Python312\Scripts\wtsexporter.exe\__main__.py", line 4, in <module>
  File "C:\Users\User1\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.12_qbz5n2kfra8p0\LocalCache\local-packages\Python312\site-packages\Whatsapp_Chat_Exporter\__main__.py", line 11, in <module>
    from Whatsapp_Chat_Exporter import ios_handler, ios_media_handler
  File "C:\Users\User1\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.12_qbz5n2kfra8p0\LocalCache\local-packages\Python312\site-packages\Whatsapp_Chat_Exporter\ios_media_handler.py", line 12, in <module>
    from iphone_backup_decrypt import FailedToDecryptError
ImportError: cannot import name 'FailedToDecryptError' from 'iphone_backup_decrypt' (C:\Users\User1\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.12_qbz5n2kfra8p0\LocalCache\local-packages\Python312\site-packages\iphone_backup_decrypt\__init__.py)

Sure.
PS C:\wabckp> python --version
Python 3.12.4

PS C:\wabckp> wtsexporter -i -b "C:\Users\User1\Apple\MobileSync\Backup\00008110-001E490C0AEA901E"
Traceback (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "C:\Users\User1\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.12_qbz5n2kfra8p0\LocalCache\local-packages\Python312\Scripts\wtsexporter.exe\__main__.py", line 4, in <module>
  File "C:\Users\User1\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.12_qbz5n2kfra8p0\LocalCache\local-packages\Python312\site-packages\Whatsapp_Chat_Exporter\__main__.py", line 11, in <module>
    from Whatsapp_Chat_Exporter import ios_handler, ios_media_handler
  File "C:\Users\User1\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.12_qbz5n2kfra8p0\LocalCache\local-packages\Python312\site-packages\Whatsapp_Chat_Exporter\ios_media_handler.py", line 12, in <module>
    from iphone_backup_decrypt import FailedToDecryptError
ImportError: cannot import name 'FailedToDecryptError' from 'iphone_backup_decrypt' (C:\Users\User1\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.12_qbz5n2kfra8p0\LocalCache\local-packages\Python312\site-packages\iphone_backup_decrypt\__init__.py)

Make sure you are installing the iphone_backup_decrypt with the master branch. For details of your issue, see https://github.com/KnugiHK/WhatsApp-Chat-Exporter/issues/102.

If you are working on unencrypted iOS/iPadOS backup, skip this

I did not istall it because my iPhone backup is not encrypted.
Do I need to install it anyway?

I installed iphone_backup_decrypt using:
pip install git+https://github.com/KnugiHK/iphone_backup_decrypt
command and this is what's happening now:
PS C:\wabckp> wtsexporter -i -b "C:\Users\User1\Apple\MobileSync\Backup\00008110-001E490C0AEA901E" Contact database not found. PS C:\wabckp>
No errors, just that one line information about contact database and still no chat history export..
What should I do next?

If you are working on unencrypted iOS/iPadOS backup, skip this

I did not istall it because my iPhone backup is not encrypted.
Do I need to install it anyway?

Oh... Then it seems there could be issue in the code. I will take a look later.

I installed iphone_backup_decrypt using: pip install git+https://github.com/KnugiHK/iphone_backup_decrypt command and this is what's happening now: PS C:\wabckp> wtsexporter -i -b "C:\Users\User1\Apple\MobileSync\Backup\00008110-001E490C0AEA901E" Contact database not found. PS C:\wabckp> No errors, just that one line information about contact database and still no chat history export..
What should I do next?

If you are sure you have WhatsApp (not WhatsApp Business) installed and exported it in the backup, then, probably they changed the database name, which requires changes to the code.

OK, can I use different branch or wait?

Probably you will have to wait until I (or someone else who are willing to contribute) figure out the new things.

I installed iphone_backup_decrypt using: pip install git+https://github.com/KnugiHK/iphone_backup_decrypt command and this is what's happening now: PS C:\wabckp> wtsexporter -i -b "C:\Users\User1\Apple\MobileSync\Backup\00008110-001E490C0AEA901E" Contact database not found. PS C:\wabckp> No errors, just that one line information about contact database and still no chat history export..
What should I do next?

I could not reproduce the issue in iOS 17.6.1 with WhatsApp <IP_ADDRESS>. It works fine with 0.10.0. Not sure what have been changed inside the WhatsApp app.


Grouping

Added support for GroupBy statements and aggregate aliases.

Can you add documentation (e.g. in README.md) explaining the constraints on the current implementation of these features. Also I think some commits like Fixed testGroupByAndAlias can be squashed.

I can remove the last merge commit before merging this pull request. i just didn't want to do a rebase and force push due to the review, as that can break the association between comments and code.

The previous Travis failure seems to have just been a fluke, somehow Travis build container couldn't reach canonical's repository (I sincerely hope they actually run their own mirror). A simple rerun fixed it.
I have also added a couple more comments.


Update to Kodi Nexus

Credits go to @SmellyCat69 and @fugkco

@daanvandevliet thanks for the PR. I'm just trying to set up, so I can test it before I review and merge. I'm kind of curious how you got elementum working on Nexus, as it doesn't seem to want to install due to kodi_six not being installed, which in turn cannot be installed as it's for older versions of Kodi.

@fugkco thanks for going through the trouble. I just tested a clean install of Kodi Nexus and elementum installed as expected. I installed the universal package from the official website.
I hope that helps!

I'll make a release soon.


Inline wall icon svg to align on mac and PC

@shakao this has a conflict with master. Can you resolve?


This proposes to stabilize automatic garbage collection of Cargo's global cache data in the cargo home directory.
What is being stabilized?
This PR stabilizes automatic garbage collection, which is triggered at most once per day by default. This automatic gc will delete old, unused files in cargo's home directory.
It will delete files that need to be downloaded from the network after 3 months, and files that can be generated without network access after 1 month. These thresholds are intended to balance the intent of reducing cargo's disk usage versus deleting too often forcing cargo to do extra work when files are missing.
Tracking of the last-use data is stored in a sqlite database in the cargo home directory. Cargo updates timestamps in that database whenever it accesses a file in the cache. This part is already stabilized.
This PR also stabilizes the gc.auto.frequency configuration option. The primary use case for when a user may want to set that is to set it to "never" to disable gc should the need arise to avoid it.
When gc is initiated, and there are files to delete, there will be a progress bar while it is deleting them. The progress bar will disappear when it finishes. If the user runs with -v verbose option, then cargo will also display which files it deletes.
If there is an error while cleaning, cargo will only display a warning, and otherwise continue.
What is not being stabilized?
The manual garbage collection option (via cargo clean gc) is not proposed to be stabilized at this time. That still needs some design work. This is tracked in https://github.com/rust-lang/cargo/issues/13060.
Additionally, there are several low-level config options currently implemented which define the thresholds for when it will delete files. I think these options are probably too low-level and specific. This is tracked in https://github.com/rust-lang/cargo/issues/13061.
Garbage collection of build artifacts is not yet implemented, and tracked in https://github.com/rust-lang/cargo/issues/13136.
Background
This feature is tracked in https://github.com/rust-lang/cargo/issues/12633 and was implemented in a variety of PRs, primarily https://github.com/rust-lang/cargo/pull/12634.
The tests for this feature are located in https://github.com/rust-lang/cargo/blob/master/tests/testsuite/global_cache_tracker.rs.
Cargo started tracking the last-use data on stable via https://github.com/rust-lang/cargo/pull/13492 in 1.78 which was released 2024-05-02. This PR is proposing to stabilize automatic deletion in 1.82 which will be released in 2024-10-17.
Risks
Users who frequently use versions of Rust older than 1.78 will not have the last-use data tracking updated. If they infrequently use 1.78 or newer, and use the same cache files, then the last-use tracking will only be updated by the newer versions. If that time frame is more than 1 month (or 3 months for downloaded data), then cargo will delete files that the older versions are still using. This means the next time they run the older version, it will have to re-download or re-extract the files.
The effects of deleting cache data in environments where cargo's cache is modified by external tools is not fully known. For example, CI caching systems may save and restore cargo's cache. Similarly, things like Docker images that try to save the cache in a layer, or mount the cache in a read-only filesystem may have undesirable interactions.
The once-a-day performance hit might be noticeable to some people. I've been using this for several months, and almost never notice it. However, slower systems, or situations where there is a lot of data to delete might take a while (on the order of seconds hopefully).

@rfcbot fcp merge

@rfcbot concern field-name
Something that came up on the tracking issue is whether people will get confused with the gc name (https://github.com/rust-lang/cargo/issues/12633#issuecomment-2068163777).  I suspect that won't be a problem but I want to make sure we acknowledge it and agree it isn't a problem first.
I am also somewhat concerned about how to organize and name the config for if/when we get to GC within target directories.  I wonder if this would affect the top-level table name (e.g. calling it global-cache).  In other ways, only stabilizing auto gives us a lot of leeway in what it does.
(sorry, thought of this after the conversation about stabilizing this)

Something that came up on the tracking issue is whether people will get confused with the gc name

I agree that this isn't likely to be an issue in practice.
However, I also feel like we might as well be more accurate and call it something like "cache cleaning", which is what it actually is.  As I mentioned in the other thread, garbage collection is usually related to some concept of reachability and resultant high confidence that something is no longer used.  This doesn't reflect how this feature actually works, or ever reasonably could work.
And unless I'm missing something here (which is always possible), I don't think there's any cost to simply naming this feature more accurately, aside from taking a bit of time to decide on that name.

Sorry if this is the wrong place to ask, but will there be a way to disable this behaviour?

Sure, would be happy to rename it. I opened https://github.com/rust-lang/cargo/issues/14292 to have that suggestion, please express your thoughts over there.

:umbrella: The latest upstream changes (presumably #14388) made this pull request unmergeable. Please resolve the merge conflicts.

:umbrella: The latest upstream changes (presumably 4c39aaff66862cc0da52fe529aa1990bb8bb9a22) made this pull request unmergeable. Please resolve the merge conflicts.


How to calculate start and end while dataZoom event triggered ?

One-line summary [问题简述]
How to calculate start and end while dataZoom event triggered ?
I have 1,000 more data on xAxis.
And I want to calculate the index of xAxis data by start and end value.
I has already tried these two ways:
[1] Question: Dynamically change data existing data on Zoom event
[2] 折线图的dataZoom能否指定下标而不是百分比？
Any one of ways which I tried is fail : (sometimes need subtract 1)
Math.round(data.values.length*(param.start/100))
// or subtract 1
Math.round(data.values.length*(param.start/100)) - 1

or
Math.floor(data.values.length*(param.start / 100))
// or subtract 1
Math.floor(data.values.length*(param.start / 100)) - 1

Are there any methods can calculate start Index and end Index exactly ?
Version & Environment [版本及环境]

ECharts version [ECharts 版本]: 4
Browser version [浏览器类型和版本]: Chrome 64
OS Version [操作系统类型和版本]: Linux (Ubuntu) 16.04

My Code [我的代碼]
var start = Math.floor(zoom.batch[0].start / 100 * this.Content.length)
var end = Math.ceil(zoom.batch[0].end / 100 * this.Content.length)

The index sometimes was correct and sometimes wasn't.

datazoom事件接受两个参数，第二个参数是echart实例
可以通过echartsInstance._coordSysMgr._coordinateSystems找到坐标轴属性

@alanchanzm Thanks. I has already fixed it by some methods.
I forget to close issue. Sorry.

@alanchanzm Thanks. I has already fixed it by some methods.
I forget to close issue. Sorry.

May I ask what your solution was?

@abrahtomi I am sorry! I don't have solution now because it's a project of my former company. But I am sure about that I implemented charts with D3.js finally.


https://wiki.developer.mozilla.org/es/docs/Web/HTTP/Headers/Accept$history

Typo In Spanish Version

In words highlighted would say "Cualquier".

Thanks for your report! Please note that MDN translations are maintained by the MDN wiki community. The few MDN staff don't speak Spanish. Closing this issue, see also https://github.com/mdn/sprints#mdn-translations


Added query helper sample

Issue

Describe your changes

How to test

Checklist:

[ ] My code follows the style guidelines for this repo
[ ] I have performed a self-review of my code
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings/errors
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I don't require ops changes for this PR to go to prod
[ ] This change does not include a migration

Comments

:tada: This PR is included in version 1.32.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Break signal

Various things to make break signal StopExperiment work, as well as some corrections /additions to SONify.

@yamins81 merged break signal


[CIVP-18337] Update to civis-jupyter-notebook v1.0.0

Update to civis-jupyter-notebook v1.0.0

Since this change involves only a micro version update, kubernetes image prepulls do not need to be updated. (They specify only major & minor version)


⚠ API - Lens has degraded performance

In 4d57982, API - Lens ($LENS_API_URL) experienced degraded performance:

HTTP code: 503
Response time: 357 ms

Resolved: API - Lens performance has improved in 2e11a2a after 6 minutes.


[BUG] Can't GROUP BY on a calculated boolean column

Describe the bug
If GROUP BY statement refers on a column that has boolean value calculated in runtime, it fails.
See some examples:
opensearchsql> SELECT 1>1 AS a FROM calcs GROUP BY a;
TransportError(500, 'ClassCastException', {'error': {'type': 'ClassCastException', 'reason': 'There was internal problem at backend', 'details': "class java.lang.String cannot be cast to class java.lang.Boolean (java.lang.String and java.lang.Boolean are in module java.base of loader 'bootstrap')"}, 'status': 503})
opensearchsql> SELECT 1 IS NULL AS a FROM calcs GROUP BY a;
TransportError(500, 'ClassCastException', {'error': {'type': 'ClassCastException', 'reason': 'There was internal problem at backend', 'details': "class java.lang.String cannot be cast to class java.lang.Boolean (java.lang.String and java.lang.Boolean are in module java.base of loader 'bootstrap')"}, 'status': 503})
opensearchsql> SELECT int0 > 0 AS a FROM calcs GROUP BY a;
TransportError(500, 'ClassCastException', {'error': {'type': 'ClassCastException', 'reason': 'There was internal problem at backend', 'details': "class java.lang.String cannot be cast to class java.lang.Boolean (java.lang.String and java.lang.Boolean are in module java.base of loader 'bootstrap')"}, 'status': 503})
opensearchsql> SELECT (CASE WHEN bool0 THEN TRUE WHEN NOT bool0 THEN FALSE ELSE NULL END) AS a FROM calcs GROUP BY a;
TransportError(500, 'ClassCastException', {'error': {'type': 'ClassCastException', 'reason': 'There was internal problem at backend', 'details': "class java.lang.String cannot be cast to class java.lang.Boolean (java.lang.String and java.lang.Boolean are in module java.base of loader 'bootstrap')"}, 'status': 503})

But grouping on a boolean column works well:
opensearchsql> SELECT bool0 AS a FROM calcs GROUP BY a;
fetched rows / total rows = 3/3
+-------+
| a     |
|-------|
| null  |
| False |
| True  |
+-------+

To Reproduce
See examples above.

PR that fixes this issue: #284


With Ant-Design, the UI framework starts at @, leading to the constant introduction of Optimizedeps.include

Optimizedeps.include continues to be introduced
When I used Ant - Design, I started with @, so I had to keep adding Optimizedeps.include when I used different modules
Describe the solution you'd like
The expectation is that in certain circumstances, I will use escape methods to identify the @ match used in the UI framework, but this is only my personal idea
Describe alternatives you've considered
No clue
System Info

vite version: 1.0.0-rc.1

Operating System: Windows 10 Enterprise edition

Node version: 12.13.0

NPM version: 6.12.0

Installed vue version (from yarn.lock or package-lock.json): 3.0.0

Installed @vue/compiler-sfc version: 3.0.0-rc.1

example
https://github.com/Jack-rainbow/vite-project
 vite.config.js
 optimizeDeps: {
      include: ["lodash", "axios", 'ant-design-vue', '@ant-design-vue/use']
   }

This is expected behavior for cjs module. But the ant-design-vue exported the es6 module, you don't add it into optimizeDeps, it should worked fine as normal import.


Make find-doc-nits check for newly added undocumented symbols

We create lists of undocumented functions and macros as they are now so that find-doc-nits can check for newly introduced functions/macros that are undocumented.
This works in a similar way to the -u and -d options to find-doc-nits. These count undocumented symbols and print a detailed list of undocumented symbols repsectively. This PR adds the -v and -e options to restrict the count/detailed list to newly added undocumented symbols only.
There is also a new -s option that does the same as -e except that it produces no output if there are no newly undocumented symbols.
We also amend "make doc-nits" to add the -s option which should cause travis to fail if a PR adds undocumented symbols.
There is also the new option -o to amend the behaviour of -v or -e to check symbols that were newly
added since the release of 1.1.1.
Finally this PR fixes a documentation error that was found during development of this PR (a symbol that existed in 2 man pages), and an error in the definition of a macro that caused a false report from find-doc-nits.

There is also the new option -o to amend the behaviour of -v or -e to check symbols that were newly added since the release of 1.1.1.

Just a thought: using git blame, the script could even spit out the culprit who introduced it ;-)

Just a thought: using git blame, the script could even spit out the culprit who introduced it ;-)

Not sure I want to do automatic finger pointing at this stage :-)

Ping?

Also, what's the plan for updating the missing files? Any method to do so?

It's not particularly critical. Probably something we can just do on an occasional basis as we see fit. If a missing function gets documented, it doesn't matter if it is in one of the "missing" files (no error is reported). The worst that could happen would be that a missing function gets documented, and then at some later point the documentation is accidentally deleted. In that case find-doc-nits would not spot the sudden removal of the documentation.
We could make find-doc-nits complain if it finds a documented function in its undocumented list. That way if you document a function you also have to remove it from the missing list (otherwise travis "make doc-nits" builds will fail). Not sure if it is worth it at this stage.

Pushed. Thanks.

Backported to 1.1.1 via #10094.


qhyccd_sdk: init at 23.09.06

QHY CCD SDK :
A software development kit for interfacing with QHYCCD astronomy cameras, including libraries and sample code. Non-commercial use only."
https://www.qhyccd.com/html/prepub/log_en.html#!log_en.md#22.08.17
Things done

Built on platform(s)

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

[x] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

just notice there is a bug that breaks udev rules...working on a fix

fixed udev rules

Result of nixpkgs-review pr 254714 run on x86_64-linux 1

1 package built:

qhyccd_sdk

@AndersonTorres can you double check, sorry for the wrong commit before, last one address all the issues you raised but the one that i patch the install.bat file in order to place all the files it copies into the proper $out dir


Feature/documentation

What changes were made:
Comments and documentation
What are the relevant JIRA tickets:
94
How can these changes be tested(test #?):
n/a
Comments:
Please go through and make sure everything makes sense -- if there's something that should be said that I haven't, feel free to add it. If there's something that should be changed, feel free to change it. Additionally, once this pull request is completed and everything is in a state that everyone's happy with, this will be where the release will be created.

Comments and Documentation look really good! Nice work

Comments and documentation look really good!


Vibrant Capacitor Bank voiding energy

I've got two big reactors attached to a lot of vibrant capacitor banks. Each reactor is outputting 20k Rf/t and the energy use is 25k Rf/t. The capacitor banks are full but wont stop accepting energy. I can see that in the power monitor and the buffers of the reactors arent filling. If i set in the capacitor bank that it isnt allowed to accept or output power, the buffers are filling

What kind of cabling are you using? Ender IO conduits? Direct connection?

Im usind Ender Energy Conduits to connect the reactors to the capacitor banks and then thers a tesseract direct to the bank


Possible fix #237

Updated the "getting API key" section for better clarification.

thank you so much


[masters] Add extractor

Please follow the guide below

You will be asked some questions, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your pull request (like that [x])
Use Preview tab to see how your pull request will actually look like

Before submitting a pull request make sure you have:

[ x] At least skimmed through contributing guidelines including yt-dlp coding conventions
[ x] Searched the bugtracker for similar pull requests
[ x] Checked the code with flake8

In order to be accepted and merged into yt-dlp each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[ x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[ ] Bug fix
[ ] Improvement
[x ] New extractor
[ ] New feature

Description of your pull request and other information
New extractor addition, Masters, closes https://github.com/yt-dlp/yt-dlp/issues/3240

[ x] At least skimmed through contributing guidelines including yt-dlp coding conventions

It doesn't look like u did :(

hehe, first PR and all these blunders

@pukkandan
Changed conventions, PR to be reviewed


Unable to resolve module @expo/vector-icons/Ionicons  after eject from crna

"react-native": "0.50.3",
"react": "16.0.0",
"native-base": "^2.3.8"
steps:

create app with crna.
2.install native-base and works awesome with expo client.
3.npm run eject.
4.react-native run-ios. then got error:
Bundling index.js  [development, non-minified]  0.0% (0/1212), failed.
error: bundling failed: UnableToResolveError: Unable to resolve module @expo/vector-icons/Ionicons from ...../client/node_modules/native-base/dist/src/basic/Checkbox.js: Module does not exist in the module map

please help...

ok. solved.
use react-native start "--reset-cache".


bug: text input margin

Describe the bug
Right now text input margin is held by the vtmn-text-input_container.
Aim of this margin is - as far as I know - to give space between label / input / helper.
If the component doesn't hold a helper (or even a label), we get extra margin that we don't need :

Steps to reproduce
1. Go to 'https://decathlon.github.io/vitamin-web/@vtmn/showcase-css/?path=/story/components-forms-text-input--multiline'
2. hover #my-text-input-multiline-1 in inspector
3. See useless bottom margin
Expected behavior

keep outbound margin out of the component

Browsers affected
All

I can do a PR for css and React versions if you think it's relevant

I'm on it, sorry for the inconvenience


how to get cookies and downlload all videos in bilibili profile

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I intentionally remove or skip any mandatory* field

Checklist

[X] I'm asking a question and not reporting a bug or requesting a feature
[X] I've looked through the README
[X] I've verified that I'm running yt-dlp version 2023.10.13 (update instructions) or later (specify commit)
[X] I've searched known issues and the bugtracker for similar questions including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue

Please make sure the question is worded well enough to be understood
guys how to dl videos from https://space.bilibili.com/510877118/video . i want videos in 1080p and maybe with subtitles if possible, also how to scrape posts from bilibili profiles like same with youtube ytdlp
yt-dlp --print-to-file "%(title)s|%(upload_date)s|%(duration_string)s|%(view_count)s|%(comment_count)s|%(availability)s|%(channel)s|%(webpage_url)s|" "list.txt" "https://www.youtube.com/@IndiaNewsITV/videos"  --playlist-reverse --simulate ?
Provide verbose output that clearly demonstrates the problem

[X] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[X] If using API, add 'verbose': True to YoutubeDL params instead
[X] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
No response

https://github.com/yt-dlp/yt-dlp/wiki/FAQ#how-do-i-pass-cookies-to-yt-dlp

how to get cookies

https://github.com/yt-dlp/yt-dlp/wiki/FAQ#how-do-i-pass-cookies-to-yt-dlp

downlload all videos in bilibili profile

pass the profile url to yt-dlp

I'm in the same case as him since this morning, tried every sub here on github for this matters, cookies seems to not work, and i cant seem to find premium/free bilibili account cookie.
My prompt actually is that and it does not work
yt-dlp.exe --cookies-from-browser firefox  VIDEO_URL
then when you have a cookie file i do that
yt-dlp --cookies cookies.txt VIDEO_URL
Nothing works

I'm in the same case as him since this morning, tried every sub here on github/reddit/internet for this matters, cookies seems to not work, and i cant seem to find premium/free bilibili account or just cookies of an pre existing account.
My prompt actually is that and it does not work

yt-dlp.exe --cookies-from-browser firefox  VIDEO_URL

then when you have a cookie file i do that

yt-dlp --cookies cookies.txt VIDEO_URL

Nothing works

any update?

nop still not work i'm waiting for comments on this sub for a solution tried every sub most likely 10+ and does not work for me