Premier League Match Analysis

ML-Crate Repository (Proposing new issue)
:red_circle: Project Title : Premier League Match Analysis
:red_circle: Aim : Analyze the PL matches for the season of 2019-20.
:red_circle: Dataset : https://www.kaggle.com/datasets/idoyo92/epl-stats-20192020
:red_circle: Approach : Try to use 3-4 algorithms to implement the models and compare all the algorithms to find out the best fitted algorithm for the model by checking the accuracy scores. Also do not forget to do a exploratory data analysis before creating any model.
Hello, ML-Crate contributors, this issue is only for the contribution purposes and allocated only to the participants of SWOC 2.0 Open Source Program and JWOC '22 Open Source Program.

📍 Follow the Guidelines to Contribute in the Project :

You need to create a separate folder named as the Project Title.
Inside that folder, there will be four main components.

Images - To store the required images.
Dataset - To store the dataset or, information/source about the dataset.
Model - To store the machine learning model you've created using the dataset.
requirements.txt - This file will contain the required packages/libraries to run the project in other machines.

Inside the Model folder, the README.md file must be filled up properly, with proper visualizations and conclusions.

:red_circle::yellow_circle: Points to Note :

The issues will be assigned on a first come first serve basis, 1 Issue == 1 PR.
"Issue Title" and "PR Title should be the same. Include issue number along with it.
Follow Contributing Guidelines & Code of Conduct before start Contributing.
This issue is only for 'SWOC' and 'JWOC' contributors of 'ML-Crate' project.

:white_check_mark: To be Mentioned while taking the issue :

Full name :
GitHub Profile Link :
Participant ID :
Approach for this Project :
What is your participant role?

[ ] SWOC 2.0 Participant.
[ ] JWOC 2022 Participant.
[ ] Contributor

Happy Contributing 🚀
All the best. Enjoy your open source journey ahead. 😎

Hi,
I would like to work on this issue.

Full Name: Sriniketh J
GitHub Profile Link: https://github.com/srini047
Approach for this Project: I will initially clean the dataset, preprocess it, and finally do EDA to get insights into the dataset.
Participant Role:

[x] HSOC Participant

What's the update on this issue @srini047?

What's the update on this issue @srini047?

@abhisheks008 I have my end-sem exam on Tuesday. I need some time to complete the issue. I will be able to do a PR within Tuesday night at the max. Please consider my issue.

It's okay @srini047. Thanks for the update, concentrate on your exams, you can solve this issue later. All the best for your end sem 🚀

It's okay @srini047. Thanks for the update, concentrate on your exams, you can solve this issue later. All the best for your end sem 🚀

Thanks for the consideration ☺😊!!

Updates please @srini047

Updates please @srini047

@abhisheks008  I have started the building model's, need to do 2 more models and summary alone.
Sorry for the delay in making PR.

Thanks for the update @srini047. No worries, take your time. 😃

@abhisheks008 done with Model. Need to make README alone. Will do PR within today.
Sorry for the delay in making PR.


[backport] Verbose error in gradient check

Backport of #3833

LGTM. Merging if all tests pass.

Verified that tests pass.


Fix findbugs

What changes are proposed in this pull request?
Assign the cause to a local variable.
Why are the changes needed?
Fix findbugs.
Does this PR introduce any user facing changes?
no.

alluxio-bot, merge this please

alluxio-bot, merge this please

alluxio-bot, cherry-pick this to branch-2.8 please


Create functional tests coverage: submit domestic standing order consent

Description
Implement the proper functional tests to cover the domestic standing orders consent flow Here
Tasks

[ ] Test coverage domestic standing orders submission with all fields
[ ] Test coverage domestic standing orders submission with only mandatory fields
[ ] Test coverage domestic standing orders submission expected errors
[ ] Add gradle group task to run only the domestic standing orders tests v3.1.8

Acceptance criteria

[ ] All current functional tests pass.
[ ] The Domestic standing orders functional tests pass.
[ ] As a developer I can run the a task to run only the domestic standing orders functional tests v3.1.8

Hey team! Please add your planning poker estimate with ZenHub @andra-racovita @mariantiris


Bad translation: "Exportar to PDF"

Bad translation: "Exportar to PDF" in english bundle.

Solved


Update index.md

Optional extended

Why:
Closes [issue link]

What's being changed:

Check off the following:

[ ] I have reviewed my changes in staging (look for the latest deployment event in your pull request's timeline, then click View deployment).
[ ] For content changes, I have completed the self-review checklist.

Writer impact (This section is for GitHub staff members only):

[ ] This pull request impacts the contribution experience

[ ] I have added the 'writer impact' label
[ ] I have added a description and/or a video demo of the changes below (e.g. a "before and after video")

Optional extended

Why:
Closes [issue link]

What's being changed:

Check off the following:

[ ] I have reviewed my changes in staging (look for the latest deployment event in your pull request's timeline, then click View deployment).
[ ] For content changes, I have completed the self-review checklist.

Writer impact (This section is for GitHub staff members only):

[ ] This pull request impacts the contribution experience

[ ] I have added the 'writer impact' label
[ ] I have added a description and/or a video demo of the changes below (e.g. a "before and after video")

range

U going to be smiling silent now 😂
Sent from Yahoo Mail on Android
On Sat, Sep 25, 2021 at 6:38 PM, Smile @.***> wrote:
range
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.


Breaks selecting recently pasted text with [v]

When I have vim-auto-save enabled, I cannot use this helpful trick to select recently pasted text  http://vim.wikia.com/wiki/Selecting_your_pasted_text
When you use
`[v`]

, it selects the entire file.

Could you give some more details?
What vim-auto-save configuration do you use, do you get any errors?

The only configuration that makes it break is enabling the plugin in my vimrc using
:let g:autosave = 1

When I do backtick + [ or  singlequote + [ I am taken to the beginning of the file, rather than to the beginning of the last pasted text.

@dechimp The same happens when you just use :w (and we use it for saving in vim-auto-save). I'm not sure we're able to fix it.

Ah.  That's a shame. At least we got to the bottom of the issue.
On Tue, Mar 17, 2015 at 11:41 PM, Alexey Chernenkov <
<EMAIL_ADDRESS>wrote:

@dechimp https://github.com/dechimp The same happens when you just use
:w (and we use it for saving in vim-auto-save). I'm not sure we're able
to fix it.
--
Reply to this email directly or view it on GitHub
https://github.com/907th/vim-auto-save/issues/15#issuecomment-82779361.


Tag the new release on Publish action

@N3xed - I assume you'll do something similar for embedded-svc, esp-idf-hal and esp-idf-template? Would be greatly appreciated!

@N3xed - I assume you'll do something similar for embedded-svc, esp-idf-hal and esp-idf-template? Would be greatly appreciated!

Yup, done. I've also pushed tags that I've scraped from the successful Publish runs.


Update jsoniter-scala-core, ... to 2.23.0

About this PR
📦 Updates

com.github.plokhotnyuk.jsoniter-scala:jsoniter-scala-core
com.github.plokhotnyuk.jsoniter-scala:jsoniter-scala-macros

from 2.17.9 to 2.23.0
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.github.plokhotnyuk.jsoniter-scala" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.github.plokhotnyuk.jsoniter-scala" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, version-scheme:early-semver, commit-count:1

Superseded by #480.


Please list all the categories somewhere or tell us how to determine the values for it

I have tried categories based on collection names and tags - neither works.

Never mind, I didn't realise the unsplash source website was scrollable....


observation

hi, not really an issue, just an observation.
my UI is one i cobbled together myself.
using bloodmoon status i have UI info displayed in the top right corner of my screen as you can see in the first pic.
in the second pic when bloodmoon starts the old info is overlapped by the new info.
the old info does not disappear till i kill a zed, then it updates.

so as you can see its not really an issue, but maybe something that could be improved.

Hi!
This mod simply syncs a CVAR to each remote player and does nothing more.
Some controllers don't react to CVAR changes until certain events happen, but others proactively update.
I can't recall for sure, but I believe the toolbelt controller does update immediately when CVAR changes are received. Using that as a controller might help if you aren't using it already.

I'm using compass in this case.
I use toolbelt for other stuff.
No worries, it's pretty much what I thought.
I will see if I can swap it but my setup is complicated bc I use Gears to
offer different UI layouts.
On Mon, Dec 30, 2024, 3:07 p.m. Jonathan Robertson @.***>
wrote:

Hi!
This mod simply syncs a CVAR to each remote player and does nothing more.
Some controllers don't react to CVAR changes until certain events happen,
but others proactively update.
I can't recall for sure, but I believe the toolbelt controller does update
immediately when CVAR changes are received. Using that as a controller
might help if you aren't using it already.
—
Reply to this email directly, view it on GitHub
https://github.com/jonathan-robertson/bloodmoon-server-status/issues/3#issuecomment-2565995779,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AZS4VZKV6ZZH2RZNZMQAIC32IHG4JAVCNFSM6AAAAABUMVZNI6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRVHE4TKNZXHE
.
You are receiving this because you authored the thread.Message ID:
@.***
com>


XZ2 Compact Support (apollo, H8314 and H8324)

As stated in the Readme.md. An issue for monitoring the status/development of the single sim XZ2 Compact.

Tasks to do:

[ ] check whether partitioning is the same as in akari. List of partitions available already
[ ] compile system and vendor images. Upload them to OBS
[ ] configure kernel as in akari
[ ] compile hybris-hal packages
[ ] add device specific files in droid-config-sony-tama-pie
[ ] add device specific files in droid-hal-img-boot-sony-tama-pie
[ ] add device specific files in droid-hal-img-dtbo-sony-tama-pie
[ ] add device specific files in droid-hal-version-sony-tama
[ ] add device specific packages to OBS

Partitions on apollo (ls -l /dev/block/bootdevice/by-name)
lrwxrwxrwx 1 root root 15 1971-09-18 09:11 LTALabel -> /dev/block/sda2
lrwxrwxrwx 1 root root 16 1971-09-18 09:11 Qnovo -> /dev/block/sda70
lrwxrwxrwx 1 root root 15 1971-09-18 09:11 TA -> /dev/block/sda1
lrwxrwxrwx 1 root root 16 1971-09-18 09:11 abl_a -> /dev/block/sda12
lrwxrwxrwx 1 root root 16 1971-09-18 09:11 abl_b -> /dev/block/sda24
lrwxrwxrwx 1 root root 15 1971-09-18 09:11 aop_a -> /dev/block/sda9
lrwxrwxrwx 1 root root 16 1971-09-18 09:11 aop_b -> /dev/block/sda21
lrwxrwxrwx 1 root root 16 1971-09-18 09:11 apdp -> /dev/block/sda54
lrwxrwxrwx 1 root root 16 1971-09-18 09:11 appslog -> /dev/block/sda68
lrwxrwxrwx 1 root root 16 1971-09-18 09:11 bluetooth_a -> /dev/block/sda34
lrwxrwxrwx 1 root root 16 1971-09-18 09:11 bluetooth_b -> /dev/block/sda44
lrwxrwxrwx 1 root root 16 1971-09-18 09:11 boot_a -> /dev/block/sda36
lrwxrwxrwx 1 root root 16 1971-09-18 09:11 boot_b -> /dev/block/sda46
lrwxrwxrwx 1 root root 16 1971-09-18 09:11 cdt -> /dev/block/sda64
lrwxrwxrwx 1 root root 16 1971-09-18 09:11 cmnlib64_a -> /dev/block/sda15
lrwxrwxrwx 1 root root 16 1971-09-18 09:11 cmnlib64_b -> /dev/block/sda27
lrwxrwxrwx 1 root root 16 1971-09-18 09:11 cmnlib_a -> /dev/block/sda14
lrwxrwxrwx 1 root root 16 1971-09-18 09:11 cmnlib_b -> /dev/block/sda26
lrwxrwxrwx 1 root root 15 1971-09-18 09:11 ddr -> /dev/block/sda8
lrwxrwxrwx 1 root root 16 1971-09-18 09:11 devcfg_a -> /dev/block/sda16
lrwxrwxrwx 1 root root 16 1971-09-18 09:11 devcfg_b -> /dev/block/sda28
lrwxrwxrwx 1 root root 15 1971-09-18 09:11 devinfo -> /dev/block/sda7
lrwxrwxrwx 1 root root 16 1971-09-18 09:11 diag -> /dev/block/sda69
lrwxrwxrwx 1 root root 16 1971-09-18 09:11 dsp_a -> /dev/block/sda35
lrwxrwxrwx 1 root root 16 1971-09-18 09:11 dsp_b -> /dev/block/sda45
lrwxrwxrwx 1 root root 16 1971-09-18 09:11 dtbo_a -> /dev/block/sda39
lrwxrwxrwx 1 root root 16 1971-09-18 09:11 dtbo_b -> /dev/block/sda49
lrwxrwxrwx 1 root root 16 1971-09-18 09:11 frp -> /dev/block/sda67
lrwxrwxrwx 1 root root 16 1971-09-18 09:11 fsc -> /dev/block/sda72
lrwxrwxrwx 1 root root 16 1971-09-18 09:11 fsg -> /dev/block/sda63
lrwxrwxrwx 1 root root 16 1971-09-18 09:11 fsmetadata -> /dev/block/sda71
lrwxrwxrwx 1 root root 16 1971-09-18 09:11 hyp_a -> /dev/block/sda11
lrwxrwxrwx 1 root root 16 1971-09-18 09:11 hyp_b -> /dev/block/sda23
lrwxrwxrwx 1 root root 16 1971-09-18 09:11 keymaster_a -> /dev/block/sda13
lrwxrwxrwx 1 root root 16 1971-09-18 09:11 keymaster_b -> /dev/block/sda25
lrwxrwxrwx 1 root root 16 1971-09-18 09:11 keystore -> /dev/block/sda66
lrwxrwxrwx 1 root root 16 1971-09-18 09:11 limits -> /dev/block/sda57
lrwxrwxrwx 1 root root 16 1971-09-18 09:11 logdump -> /dev/block/sda60
lrwxrwxrwx 1 root root 16 1971-09-18 09:11 logfs -> /dev/block/sda59
lrwxrwxrwx 1 root root 16 1971-09-18 09:11 misc -> /dev/block/sda65
lrwxrwxrwx 1 root root 16 1971-09-18 09:11 modem_a -> /dev/block/sda33
lrwxrwxrwx 1 root root 16 1971-09-18 09:11 modem_b -> /dev/block/sda43
lrwxrwxrwx 1 root root 16 1971-09-18 09:11 modemst1 -> /dev/block/sda61
lrwxrwxrwx 1 root root 16 1971-09-18 09:11 modemst2 -> /dev/block/sda62
lrwxrwxrwx 1 root root 16 1971-09-18 09:11 msadp -> /dev/block/sda55
lrwxrwxrwx 1 root root 16 1971-09-18 09:11 oem_a -> /dev/block/sda40
lrwxrwxrwx 1 root root 16 1971-09-18 09:11 oem_b -> /dev/block/sda50
lrwxrwxrwx 1 root root 15 1971-09-18 09:11 persist -> /dev/block/sda5
lrwxrwxrwx 1 root root 16 1971-09-18 09:11 qupfw_a -> /dev/block/sda17
lrwxrwxrwx 1 root root 16 1971-09-18 09:11 qupfw_b -> /dev/block/sda29
lrwxrwxrwx 1 root root 16 1971-09-18 09:11 rddata -> /dev/block/sda74
lrwxrwxrwx 1 root root 16 1971-09-18 09:11 rdimage_a -> /dev/block/sda37
lrwxrwxrwx 1 root root 16 1971-09-18 09:11 rdimage_b -> /dev/block/sda47
lrwxrwxrwx 1 root root 16 1971-09-18 09:11 sec -> /dev/block/sda53
lrwxrwxrwx 1 root root 16 1971-09-18 09:11 spunvm -> /dev/block/sda56
lrwxrwxrwx 1 root root 15 1971-09-18 09:11 ssd -> /dev/block/sda6
lrwxrwxrwx 1 root root 16 1971-09-18 09:11 system_a -> /dev/block/sda42
lrwxrwxrwx 1 root root 16 1971-09-18 09:11 system_b -> /dev/block/sda52
lrwxrwxrwx 1 root root 16 1971-09-18 09:11 toolsfv -> /dev/block/sda58
lrwxrwxrwx 1 root root 16 1971-09-18 09:11 tz_a -> /dev/block/sda10
lrwxrwxrwx 1 root root 16 1971-09-18 09:11 tz_b -> /dev/block/sda22
lrwxrwxrwx 1 root root 16 1971-09-18 09:11 tzxfl_a -> /dev/block/sda20
lrwxrwxrwx 1 root root 16 1971-09-18 09:11 tzxfl_b -> /dev/block/sda32
lrwxrwxrwx 1 root root 16 1971-09-18 09:11 tzxflattest_a -> /dev/block/sda19
lrwxrwxrwx 1 root root 16 1971-09-18 09:11 tzxflattest_b -> /dev/block/sda31
lrwxrwxrwx 1 root root 16 1971-09-18 09:11 userdata -> /dev/block/sda73
lrwxrwxrwx 1 root root 16 1971-09-18 09:11 vbmeta_a -> /dev/block/sda38
lrwxrwxrwx 1 root root 16 1971-09-18 09:11 vbmeta_b -> /dev/block/sda48
lrwxrwxrwx 1 root root 16 1971-09-18 09:11 vendor_a -> /dev/block/sda41
lrwxrwxrwx 1 root root 16 1971-09-18 09:11 vendor_b -> /dev/block/sda51
lrwxrwxrwx 1 root root 15 1971-09-18 09:11 xbl_a -> /dev/block/sdb1
lrwxrwxrwx 1 root root 15 1971-09-18 09:11 xbl_b -> /dev/block/sdc1
lrwxrwxrwx 1 root root 15 1971-09-18 09:11 xbl_config_a -> /dev/block/sdb2
lrwxrwxrwx 1 root root 15 1971-09-18 09:11 xbl_config_b -> /dev/block/sdc2
lrwxrwxrwx 1 root root 16 1971-09-18 09:11 xfl_a -> /dev/block/sda18
lrwxrwxrwx 1 root root 16 1971-09-18 09:11 xfl_b -> /dev/block/sda30
lrwxrwxrwx 1 root root 15 1971-09-18 09:11 xflkeystore -> /dev/block/sda3
lrwxrwxrwx 1 root root 15 1971-09-18 09:11 xflkeystorebak -> /dev/block/sda4

Mountpoints are the same; PR will be submitted soon

As-is, rpm packages are ready. I need to build image for flashing. For that, we have gitlab CI already setup, just need to config the server to accept images. We already have a server in mind, shouldn't take too long.
As soon as image is ready, someone with xz2c will have to test it

The development build is available at https://thaodan.de/public/sailfishos/community/images/sony/tama/ (select appropriate device image).
I have not tested for XZ2c, as I don't have one. Please test and report back
Please note these are development images. If all works as intended (boots and functionality is as for XZ2 single sim), we will make new release images. The difference is in over-the-air update support - this is available to release images only.

@rinigus Should i open a new issue for the dual version or the phones are similar enough so we can keep things in this one??
Will have a dual version in about a week and then i can test stuff.

Let's keep it here. I will change the title to include dual as well

Got the phone and tested basic functionality on android. @rinigus is there a way of contacting you??? Sailfish porters needs registration. We can do it here if you are ok with this.

Test the functionality well. Also make sure you update to the latest stock before unlocking.
As for contact, let's keep public discussion here regarding XZ2c. When I will ask for logs, better use my email (see authors file in Pure Maps github repo) to avoid exposing any sensitive info (imei numbers, for example).
Overall, plan is simple.

get it to boot and work on development build. that's the one which is available right now for XZ2c. Main expected problem is touchscreen device name, which maybe different from XZ2 and XZ3.

flash release build which should support OTA as well.

You could also look into what we were doing with ljo at TMO: http://talk.maemo.org/showthread.php?t=100877

Flashing vbmeta partition...
fastboot: error: cannot load 'vbmeta': No such file or directory

even though i got the vbmeta.img in the folder with the rest of the  files i get this error when i run
sudo bash ./flash.sh
anything i need to modify on the script??

Ok. Passed that point and i am at the same spot as ljo on the TMO thread. In a shell in recovery mode.

sorry - will be a bit slow in replies until the workday is done.
so, in recovery you will have to find which device is the touch device among event? ones. I suspect that is the problem. Try to determine it and use in config, as is explained in posts 16 and 15 at TMO thread (in that order)

PS: do you know what was wrong with vbmeta?

No problem. Take your time. What pays the bills is always more important.

I found the touch device. It is /dev/event1 for the xz2c. Changed it in droid-hal-device.conf and now i am trying to understand what is going on with udev stuff ljo mentions and how to proceed. Where and where do i need to type the udevadm info -q all -a /dev/input/event1 command.

(with a huge grain of salt since i don't understand much of those things) I highly suspect the vbmeta problem has to do with the ${SAILFISH_IMAGE_PATH} before the vbmeta.img option in the flash.sh file. After it failed i run the last command as : fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img and it flashed it worked.

1: After you changed /var/lib/environment/compositor/droid-hal-device.conf , you should be able to boot into SFOS.
When in SFOS, you can determine info that we will use to assign touch device automatically. See https://github.com/sailfishos-sony-tama/main/issues/41#issuecomment-562822285
2: maybe its sudo invocation. Will have to look into it later...

Sadly it didn't boot. Got stuck again in the sony screen with no led. So it must be something more than the touch device. :disappointed:

OK, then we need logs. please send them by email. You should be able to grab them by following post 13 at TMO. I think ljo used scp for it, not through telnet

Question: did the led became white while booting and then switched off?

Yes it was white and then went off and got stuck in the sony screen. Also because i had the usb cable attached it showed the plug thing that SFOS shows when rebooting/starting it with a usb connection.
Sailfish is there in a way :smile:

FUUUUUUUUUUUUUCK now i found whats wrong. I typed /dev/event1 instead of dev/input/event1
pebkac. apologies

Yesss! Very good. Now take your time and when ready:

udev command output is needed

for Jolla Store registration, we need all as described in http://talk.maemo.org/showpost.php?p=1563117&postcount=35

Before the udev command -which i need to find a way to copy paste- a few issues. (running it without a sim card)
I don't see an IMEI on the settings.
If i lock the phone it reboots after some time.
No BT, WLAN, etc
I am getting a nano sim in a few minutes and will report back.

it should work fine and show IMEI without sim card. that is strange, so we need new logs with reboots, no wifi and bt.

It doesn't even read the sim card i just put into it. The sim card works in another phone.

it's obviously wrong day+date to fix it, but logs please :)

ok. what logs you need and how can i get them.

same shutdown log, as you sent before. and the same way:

start phone
try to enable wifi
shutdown
in recovery, get the logs

to be more specific - I would like to get journal and logcat logs

i know it is an idiotic way but in case you need it here is an image of the udev command.
http://i.imgur.com/9ulJB4z.jpg
couldn't think of something better :man_shrugging:

that's not bad - looks like you have synaptics_tcm_touch
from your logs, what looks to be wrong is a kernel command line. For some reason, you have it extremely short (I even missed it few times):
Sailfish kernel: Kernel command line: rcupdate.rcu_expedited=1 lpm_levels.sleep_disabled=1 service_locator.enable=1 androidboot.bootdevice=1d840

In my case (xz2) and for xz3 earlier, this is something like
kernel: Kernel command line: rcupdate.rcu_expedited=1 lpm_levels.sleep_disabled=1 service_locator.enable=1 androidboot.bootdevice=1d84000.ufshc androidboot.selinux=permissive msm_rtb.filter=0x3F ehci-hcd.park=3 coherent_pool=8M
sched_enable_power_aware=1 user_debug=31 cgroup.memory=nokmem printk.devkmsg=on androidboot.hardware=akari androidboot.verifiedbootstate=orange androidboot.keymaster=1 root=PARTUUID=...

and it goes on and on. Same short version was in the first log you sent as well.
So, what could have caused it?

I presume its either something went wrong during flashing (maybe that's why vbmeta was not going through) or

maybe you didn't update stock android to the latest.

So, I suggest to try to flash again. It should go all through in the script. Note that you have to use USB2 for flashing, USB3 is no good and produces errors with those phones. In my case, I had to use older PC with USB2 to flash the phone.
We don't have a fix for touch device yet on your images. But you may as well boot into it, shutdown, and check the logs for kernel command line as well. If it is long, shows your IMEI, serial no, then it was just flashing gone bad. In that case, fix touch device config and try SFOS again.
If command line is still short, we have to figure out what's your stock version was. But let's take that if reflashing will not help.

PS: I did check the images that we have on https://thaodan.de/public/sailfishos/community/images/sony/tama/h8324/ - I presume you used that - and that image does have a correct command line.
Looks like yours is "just" cut for some reason. Fingers crossed that reflashing will help

I had the android stuff on the phone updated to the latest. I even checked with the IMEI on the sony website. The version was correct.

Also i used USB2.
If it doesn't go through the whole script i'll again run the last command manually and see how it goes. I assume its no big deal since it didn't have anything more after it. AFAI understand at least.
It would be also good to have another tester. That would help a bit.

That's both very good! Then we don't have to mess with stock updates. Did you boot into the last stock as well?
As for USB2, let's hope that it will work this time then.

Yes. Did the updates and tested phone 4g etc.
The script failed again BTW.
[toliz@mainland flash]$ sudo fastboot getvar current-slot
[sudo] password for toliz:
current-slot: a
Finished. Total time: 0.003s
[toliz@mainland flash]$ sudo ./flash.sh
Detected Linux
Searching device to flash..
Found 1 devices: BH9004VJGY
Fastboot command: fastboot -s BH9004VJGY
Flashing boot partition..
Sending 'boot_a' (20352 KB)                        OKAY [  0.644s]
Writing 'boot_a'                                   OKAY [  0.122s]
Finished. Total time: 0.779s
Flashing dtbo partition..
Sending 'dtbo' (8192 KB)                           OKAY [  0.263s]
Writing 'dtbo'                                     OKAY [  0.060s]
Finished. Total time: 0.334s
Flashing userdata partition..
Sending sparse 'userdata' 1/3 (522124 KB)          OKAY [ 16.463s]
Writing 'userdata'                                 OKAY [  0.001s]
Sending sparse 'userdata' 2/3 (498392 KB)          OKAY [ 16.159s]
Writing 'userdata'                                 OKAY [  0.001s]
Sending sparse 'userdata' 3/3 (355431 KB)          OKAY [ 11.569s]
Writing 'userdata'                                 OKAY [  0.001s]
Finished. Total time: 44.237s
Flashing system_b partition..
Sending sparse 'system_b' 1/2 (524284 KB)          OKAY [ 16.447s]
Writing 'system_b'                                 OKAY [  0.004s]
Sending sparse 'system_b' 2/2 (82460 KB)           OKAY [  9.856s]
Writing 'system_b'                                 OKAY [  0.001s]
Finished. Total time: 83.824s
Flashing vendor_a partition..
Sending 'vendor_a' (376 KB)                        OKAY [  0.022s]
Writing 'vendor_a'                                 OKAY [  0.001s]
Finished. Total time: 2.057s
Flashing vendor_b partition..
Sending 'vendor_b' (376 KB)                        OKAY [  0.022s]
Writing 'vendor_b'                                 OKAY [  0.001s]
Finished. Total time: 72.685s
Flashing oem partition..
Sending 'oem_a' (194436 KB)                        OKAY [  6.095s]
Writing 'oem_a'                                    OKAY [  1.082s]
Finished. Total time: 79.820s
Flashing vbmeta partition...
fastboot: error: cannot load 'vbmeta': No such file or directory
[toliz@mainland flash]$ sudo fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
[sudo] password for toliz:
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (4 KB)                            OKAY [  0.004s]
Writing 'vbmeta'                                   OKAY [  0.001s]
Finished. Total time: 0.016s
[toliz@mainland flash]$

OK, then I have to look into it.
How is the command line for kernel?

Jul 05 16:47:15 Sailfish kernel: Kernel command line: rcupdate.rcu_expedited=1 lpm_levels.sleep_disabled=1 service_locator.enable=1 androidboot.bootdevice=1d84000.ufshc androidboot.selinux=permissive msm_rtb.filter=0x3F ehci-hcd.park=3 coherent_pool=8M sched_enable_power_aware=1 user_debug=31 cgroup.memory=nokmem printk.devkmsg=on androidboot.hardware=akari androidboot.verifiedbootstate=orange androidboot.keymaster=1 root=PARTUUID=f9cdf7ba-b834-a72a-f1c9-d6e0c0983896 androidboot.bootdevice=1d84000.ufshc androidboot.baseband=sdm lcdid_adc=231857 androidboot.slot_suffix=__a skip_initramfs rootwait ro init=/init  androidboot.dtbo_idx=2  androidboot.bootloader=xboot oemandroidboot.xboot=1310-7079_X_Boot_SDM845_LA2.0_P_118 androidboot.serialno=BH9004VJGY startup=0x00000001 warmboot=0x00000000 oemandroidboot.babe09a9=00 oemandroidboot.babe08b3=50000000 oemandroidboot.babe137e=31 oemandroidboot.imei=35500309212925 oemandroidboot.security=0 oemandroidboot.securityflags=0x00000003
this is the command line. probably me cnp the logs cut a few long lines.

Looking waaaay better. Please correct the touch device and see if all works

ok, looks like its still using old boot image for some reason. See "androidboot.hardware=akari" . Let me make new development images for you. I suspect that there will be issues with some radios. That may take 1 hour...

I'll use it also to add touchscreen config

I 'll be here. :smile:

Looks like boot image has a correct cmd line now:
cmdline = lpm_levels.sleep_disabled=1 androidboot.bootdevice=1d84000.ufshc swiotlb=2048
service_locator.enable=1 androidboot.selinux=permissive msm_rtb.filter=0x3F ehci-hcd.park=3
coherent_pool=8M sched_enable_power_aware=1 user_debug=31 cgroup.memory=nokmem
printk.devkmsg=on androidboot.hardware=apollo

(on device it should add other options to it). So, please try the current build from https://thaodan.de/public/sailfishos/community/images/sony/tama/h8324/

Huge improvement in general. Most stuff seem to work. Tested with the mce tool.
However i have two issues and seem to be big.
First after i lock the phone from the top menu it reboots. This of a big deal.
Second the sim card is disabled and i cant get 4g internet.
Other than that everything i tested with the mce tool seems to work ok -apart from fingerprint which is known and radio which doesn't have one-. NFC also works.
So if we fix the reboot issue i thing we are good to go.
Also. ssu s reports the same IMEI (first only) as in the Device.
Xperia XZ2 Compact (h8324 / h8324)

Thank you for ssu test. I will request access to your device as well.
Cannot reproduce here locking of the phone nor 4g net issues. Please send the logs (journal and logcat).
4G: Easiest is probably to boot, try to enable 4G. Then shutdown and on new boot to SFOS grab shutdown logs from /root/
locking: change journal storage to persistent (as in https://www.freedesktop.org/software/systemd/man/journald.conf.html). reboot. then try induce reboot by locking. after reboot, become root and grab journal: journalctl > journal.lock.txt. Please send me that
I don't have right now idea why it could happen. But we can test whether rebuild using XZ2c specific hal will help.
I may ask you to flash AOSP and test if the sim card works in it. Its available at https://forum.xda-developers.com/xperia-xz2/development/aosp-aosp-8-1-h8266-t3843269

Thanks for logs, will take some time before I can fully get through them. Looks like we don't reach network, sound, and bluetooth targets during boot.
Would you mind to test if 4G and Bluetooth works on AOSP9 on your device? Link to XDA is in the message above

Unless you flashed AOSP already, let's see what can we do with SFOS to see 4G situation clearer. Right now, nothing really showed up in the logs except non-reaching targets.

Please switch off WIFI and reboot.
Login, try to enable 4G network, and wait for 10 minutes without doing anything.
Check if network showed on by loading some web page - no videos, just page
Should it not work, reboot and grab the logs (shutdown; journal + logcat)

If its not working, while I'll be checking logs, please check if it works in AOSP

One more update:
before reboot after 4G network failure, please also get
systemctl status > status

That will tell us which systemd services are failing. Would simplify going through the journal.

systemctl status > status running this gives no result.
also systemctl list-units --state=failed  lists 0 failed units.

systemctl status > status will put its output to status file. I'd like to see it - looks like some targets are not reached and it should show why

and in the last logs, without wifi, all targets are reached nicely. no wonder there are no failed units

I have looked through the logs and nothing really strikes me as failing. Except ofono does not have something like
Dec 14 19:42:55 Sailfish ofonod[3302]: data reg changed 0 -> 2 (searching), attached 0
Dec 14 19:42:56 Sailfish ofonod[3302]: Requested file structure differs from SIM: 6fb7
Dec 14 19:42:57 Sailfish ofonod[3302]: data reg changed 2 -> 1 (registered), attached 1
Dec 14 19:42:57 Sailfish ofonod[3302]: Activating context: 1
Dec 14 19:42:59 Sailfish ofonod[3302]: setting up data call

and your log has instead
Dec 14 18:37:36 Sailfish ofonod[3251]: Requested file structure differs from SIM: 6fb7
Dec 14 18:37:38 Sailfish ofonod[3251]: Unable to read mailbox identifies from SIM
Dec 14 18:37:40 Sailfish ofonod[3251]: export_entries_one_storage_cb with ME failed
Dec 14 18:38:05 Sailfish ofonod[3251]: sms received, smsc_len is 7
Dec 14 18:38:06 Sailfish ofonod[3251]: sms received, smsc_len is 7

Please check whether it does actually work with AOSP. I want to be sure before digging further that its not SIM/Operator/AOSP error. I presume that you see in Settings/Mobile network connection disabled or something similar.

Can you point me to the correct file to download from the links??? I looked to the linked websites and see stuff for android 8 android 9 10 and  other stuff.
Also do i need TWRP or i can get something usable with only the first part of https://forum.xda-developers.com/showpost.php?p=77635765&postcount=2 ??

Also one observation regarding the reboot issue (migh be unrelated but here goes) While i had the phone shut i plugged the usb cable to charge it. It showed the usual SFOS usb cable plugged in etc. In this state of the phone it wasn't rebooting. I could press the button to wake it > press again blank the screen with no issue. No idea if this helps. Just an observation.

We don't need TWRP, fastboot flashing is sufficient.
As for files, I think this should be enough for our tests:
http://www.dhsfileserver.de/ftp/MartinX3/Xperia XZ2 Compact/android_9/custom_rom/aosp/2019-10-27_13-41-39_sonyaosp_xz2c_ss.tar.gz
While its a single-sim, I presume that we can test with that. We don't need GAPPS and as you have flashed OEM already, we don't need it either. You also don't need to flash oem during installation.
So, after download, follow FASTBOOT installation. For you, points 1,2,3,4,5,7 under fastboot section

OK. No idea if it is because we used a single sim  image but i have no mobile network at all. I can't even place a phone call with aosp (while i can in SFOS).
if you have a link for a dual one i can try this.

Reading now that install by MartinX3, I can see that dual sim version requires Dual Sim Patcher. I presume that we get it from http://www.dhsfileserver.de/ftp/MartinX3/Xperia XZ2 Compact Dual/android_9/sony-dualsim-patcher-v4alpha.zip
Which means that we have to install TWRP as well. Which was not exactly as was in instructions (https://forum.xda-developers.com/showpost.php?p=77177196&postcount=2), at least for me.

get http://www.dhsfileserver.de/ftp/MartinX3/Xperia XZ2 Compact/android_9/twrp/custom_rom/2019-08-10_17-49-21_twrp_sodp_xz2c.tar.gz

get http://www.dhsfileserver.de/ftp/MartinX3/Xperia XZ2 Compact Dual/android_9/sony-dualsim-patcher-v4alpha.zip

go to fastboot mode

boot into twrp: fastboot boot twrp.img

we can try to avoid installing twrp fully, by pushing patcher to it:

5a: on PC: adb push sony-dualsim-patcher-v4alpha.zip /sdcard
5b: in TWRP, install that ZIP
5c: reboot into system

alternative is to install TWRP.

6a: on PC: adb push twrp.img /sdcard
6b: Advanced menu -> "Install recovery ramdisk" -> Choose twrp.img
6c: Reboot into Recovery
6d:  on PC: adb push sony-dualsim-patcher-v4alpha.zip /sdcard
6e: in TWRP, install dualsim patcher zip.
6f: reboot into system
I wrote it down according to my memory, hopefully its all correct. In the end of the day, we need to know whether that

SIM allows to have network connection. In theory, we could even use other device for that test.

whether your XZ2c, AOSP9 and that SIM works. For that we need to have them all together.

PS: That dual sim patcher should allow you to transform single-sim into dual-sim variant.

i assume you need an sd card in the phone right??

The sim works fine on my J1. I also tried with another SIM on SFOS with the same results. That SIM was the one i tested before unlocking the bootloader and stuff.

OK, so it's a question of combination of then all of them: device + sim + aosp9. I hope it all works. If it does, I will make an image that is based exactly on your model. Maybe that will make a difference. But let's take it one step in a time.
/sdcard is emulated, so no need for real sdcard in those instructions.

ehhhh. the first link doesn't contain a twrp.img file

it has twrp-xz2c.img - that's the same :)

fastboot boot twrp-xz2c.img gets stuck in the sony logo boot.

meh known bugs > https://forum.xda-developers.com/xperia-xz2/development/recovery-twrp-3-2-2-0-touch-recovery-t3821597

that's right, please use fastboot reboot bootloader when you enter fastboot from hardware buttons. then after that you could make fastboot boot twrp-xz2c.img

I'll be afk for about 1 hour.

And now the touchscreen doesn't work when on twrp. Nice hehe.

I think there was someone complaining about non-working touch on twrp. I'll try to find some info regarding it at XDA tomorrow. Either someone complained on TWRP or AOSP9 thread.
As far as I understood, you haven't tested that SIM (or maybe other) using stock? From your messages, I can summarize it as follows:

your current XZ2c SIM card worked in J1 (network and calls)
on SFOS, we have cellular data not working. Calls, Wifi, BT(?) work

Have you tried your or some other SIM on stock before or after unlocking? Was network working then? I presume yes.
Tomorrow, we probably should try to see if we can make AOSP9 work for testing. I will make a new SFOS image which is using XZ2c as a base, instead of XZ2 as it is now. There are just few packages that I can prioritize while building images. For XZ3, XZ2 was fine. Maybe, its not for XZ2c. Although, I don't know why. However, its relatively simple to test and we will do that.
Re reboot: mode when switched off and put on charging is different. But let's try to get 4G working first.

RE TWRP with touch issue: Try to use image from http://www.dhsfileserver.de/ftp/MartinX3/Test Builds/SODP/4.9/Touch Issues/Xperia XZ2 Compact/apollo_twrp_v8.zip

It went like this. When i got the phone out of the box i updated to latest & tested everything i could. I put in my brothers SIM -didn't have a nano sim at that point- and browsing worked fine.
Flashed SFOS -and after all the stuff we went through- we came to something that has the reboot and 4G issue. (calls messages BT wifi and everything i tested with the mce tool worked)
Before i installed AOSP i tested the phone again with my brothers SIM again. The same results as with mine which works fine on the J1.

Ok. After installing the patch we are at the same point -on AOSP- as with SFOS. I can make/receive calls but no internet over 4G. So probably its not SFOS here to blame but something on the AOSP side.

So, we will need help then from AOSP side. Maybe relevant post, https://forum.xda-developers.com/showpost.php?p=79815582&postcount=728, but it sounds like you actually did it.
If you have done it, then please register at XDA and ask for help at https://forum.xda-developers.com/xperia-xz2/development/aosp-aosp-8-1-h8266-t3843269 . I will join you and I am sure we will get it fixed, as there are no major complaints over there...

@ApostolosB : I think to identify the issue with 4G, logcat will be needed. You should be able to grab it without rooting, as far as I remember. I would suggest to use
https://forum.xda-developers.com/showthread.php?t=2774386 with the part corresponding "from PC". When doing it from Linux, you just need to install adb from your distribution (maybe something like android tools, you probably have it together with fastboot already).
In Android, you would have to enable developer options first: https://developer.android.com/studio/debug/dev-options . After that, proceed with grabbing logcat while you are in AOSP. Check if it has some IMEI or serial numbers and delete them. Then either upload it here or in XDA thread.

Is it ok to wait for martin to reply and give us instructions??

we may as well generate logcat as well. it will proceed faster then :) . for dmesg we may have to root the device, but maybe something is clear from logcat already

I am to blame i know but i flashed SFOS back on the device cause i wanted to test/play with stuff. I asked to wait just in case we need to do something different.

Fair enough :) . Then we can wait - maybe there is some known issue with AOSP that we hit

Another issue i noticed. Minor i know and not important at all at this point. Is there a way to make the key press haptic feedback a bit stronger (when typing). It seem to be inconceivable. Vibration in general works.

For haptic feedback, please open an issue. We started discussion at XDA regarding your device :)

Just saw that. I'll need some more time for this. My mobile network operator is having a generalized problem and i don't have 4g even on my J1.

Please let Martin know via XDA as well. Its good to keep communication going and keep him in the loop, as soon as we involved AOSP devs.

The problems with the data provider seem to have started at about the time i was testing with AOSP. And i didn't try another SIM while i had that flashed. It'll be "mad fun" to discover that what i was experiencing there was a problem with the provider. Or dithe problem being on the SFOS side.

Its just a bad coincidence. As you wrote at XDA, we have to wait to get the provider side sorted and then take it from there.

@rinigus if you want me to test anything in relation to the reboot bug while we wait for the data provider to get back to normal just tell me what.

I will have to look and maybe recompile kernel for it. From the logs that you sent, I haven't seen anything and I suspect that we didn't catch reboot moment. Will let you know when new image is ready, probably tomorrow night as I have to recompile Android bits as well.

No rush. In other news. Data still down as we speak.

Ok. I tested with aosp and the internet works. The problem is on the SFOS side. It was the providers problem that didn't let me get 4g on aosp the first time around. Bad luck. I'll inform the xda thread.
@rinigus How we proceed from now on???

To be clear: after all is working in AOSP, cellular network is NOT working in SFOS, right?
Then, let's get logcat's for SFOS and AOSP. In the both cases, it would simplify to have WIFI disabled.
In AOSP: boot, enable cellular data and after that get logcat.
In SFOS: boot, enable cellular data and after waiting for 10 min to be sure that its not enabling itself, reboot. after reboot, grab logcat and journal from /root (shutdown version).

I realized that you may use newer AOSP base than the one we have for SFOS. To be sure that its not playing a role, please also test http://www.dhsfileserver.de/ftp/MartinX3/Xperia XZ2 Compact/android_9/custom_rom/aosp/2019-08-08_17-45-03_sonyaosp_xz2c_ss.tar.gz
Its possible, though, that this one doesn't have touch working. But if it works, please check out whether 4G is fine there.

I cant check with the base used on SFOS because i have no touchscreen and i cant unlock the SIM.

:) yes, but with locked sim there is not much internet ... thank you very much for checking. I'll look into all collected logs later tonight

For reasons i cannot explain at all i now have 4G internet after installing SFOS. I didn't do anything different than all the other times.

I will HAPPILY take this. Its possible that your provider was already failing earlier. Or somehow SFOS was not able to establish new sim card connection.
So, we have one issue left - crash / reboot while locking. I think, at least, I will need new kernel for it. Maybe you will be able to try it as OTA update from devel later tonight.

It cant be the provider since i tested with another sim also and that didn't work. I am honestly beyond confused. If someone has an explanation i'd be more than glad to hear it.
Probably someone needs to test without installing an aosp rom. Straight from stock to SFOS.
Other than that (related to sim stuff) the test (SIM card) in the mce tool fails. Could it be that it expects 2 SIMS to be inserted i don't know.
I also run most of the tests (whatever i had available) in the mce tool and it passes them.
So for now only the reboot thing remains which as you said you will handle later tonight. ping me here and tell me if something special is needed.

Turns out, we have PSTORE enabled already - I did it before. Please check what you have in /sys/fs/pstore after reboot and send me those files via email. If you have any

Nothing there.

Check zcat /proc/config.gz | grep -i pstore if you have CONFIG_PSTORE set.
If it is set, then I don't really see what's going on. Try to enable persistent store again and send full journal after reboot (journalctl > journal.txt). If we don't see anything there, let's try to make your-device specific image.

[nemo@Sailfish ~]$ zcat /proc/config.gz | grep -i pstore
CONFIG_PSTORE=y
CONFIG_PSTORE_ZLIB_COMPRESS=y
# CONFIG_PSTORE_LZO_COMPRESS is not set
# CONFIG_PSTORE_LZ4_COMPRESS is not set
CONFIG_PSTORE_CONSOLE=y
# CONFIG_PSTORE_PMSG is not set
CONFIG_PSTORE_RAM=y

yep set

I'll start baking image and you could try meanwhile to catch it  in the journal :)

@rinigus a question. When i scroll and in general interact vigorously with the UI there seems to be that lipstick (the compositor AFAI understand) consumes quite a bit of CPU. This is considered normal right??? Is it that the compositor isn't HW accelerated by GL or whatever??

And one more thing. I inserted an SD card and i had to go into settings>storage to get it to mount. (i was expecting that to happen automatically on boot). Its vfat i think.  Also nothing appeared on the media app (sd is full of flac files.) but its maybe that i needed to wait more.

can't tell that something would be slower than expected. I would expect that UI is accelerated, as we use hybris. To check whether you get very poor performance, try to enable in Settings/Developer tools/Frame rate display -> Simple. Green means its OK, red is delayed. I usually would get most green with bits in red. If I open Pure Maps and start shifting a map fast, I can get more red regions. But nothing unexpected, I guess.
You could ask around (TMO/TJC) if there are ways to check it better

Re SD Card: last time I mounted it, it was on 1+X and I used ext4. So, no idea on whether it is expected to be mounted on boot.

Yeah i enabled the frame rate thing and only got few reds here and there. Probably an optimization thing or something.
For the indexing/ssd stuff  i'll check again once i have phone i can leave on the side and not needing to have a finger on it all the time :lol:

With reboots. We see, top have lots of messages in logs that I don't have on XZ2:
Dec 16 20:41:17 Sailfish kernel: synaptics_tcm_i2c 2-003c: touch_set_input_reporting: Input parameters unchanged
Dec 16 20:41:37 Sailfish kernel: i2c_geni a88000.i2c: i2c error :-107
Dec 16 20:41:38 Sailfish kernel: synaptics_tcm_i2c 2-003c: syna_tcm_dispatch_message: Received identify report (firmware mode = 0x01)
Dec 16 20:41:38 Sailfish kernel: synaptics_tcm_i2c 2-003c: touch_set_input_reporting: Input parameters unchanged
Dec 16 20:43:01 Sailfish kernel: i2c_geni a88000.i2c: i2c error :-107

journal finishes on suspend message before reboot and your description suggests that it happens on suspend entry (~10 seconds after closing display).
Dec 16 20:43:01 Sailfish mce[3172]: powerkey.c: pwrkey_datapipe_keypress_event_cb(): powerkey pressed
Dec 16 20:43:01 Sailfish mce[3172]: powerkey.c: pwrkey_datapipe_keypress_event_cb(): powerkey released
Dec 16 20:43:01 Sailfish mce[3172]: modules/display.c: mdy_display_state_leave(): current display state = POWER_DOWN
Dec 16 20:43:01 Sailfish sensorfwd[3356]: virtual bool HybrisAdaptor::setInterval(unsigned int, int) setInterval not ok
Dec 16 20:43:01 Sailfish statefs[3186]: Display: "off"
Dec 16 20:43:01 Sailfish kernel: CPU0: update max cpu_capacity 306
Dec 16 20:43:01 Sailfish lipstick[4173]: [D] unknown:0 - sleepDisplay
Dec 16 20:43:01 Sailfish kernel: i2c_geni a88000.i2c: i2c error :-107
Dec 16 20:43:01 Sailfish kernel: CPU0: update max cpu_capacity 306
Dec 16 20:43:01 Sailfish kernel: pn547_dev_ioctl power off, irq=0
Dec 16 20:43:01 Sailfish nfcd[3262]: [gbinder] WARNING! Unknown local object 0xe8504f00
Dec 16 20:43:01 Sailfish kernel: @@@@ panel power off @@@@
Dec 16 20:43:01 Sailfish mce[3172]: modules/display.c: mdy_display_state_enter(): current display state = OFF
Dec 16 20:43:01 Sailfish kernel: CPU2: update max cpu_capacity 306
Dec 16 20:43:02 Sailfish kernel: CPU2: update max cpu_capacity 306
Dec 16 20:43:03 Sailfish kernel: CPU1: update max cpu_capacity 306
Dec 16 20:43:03 Sailfish kernel: CPU1: update max cpu_capacity 306
Dec 16 20:43:06 Sailfish kernel: PM: suspend entry 2019-12-16 18:43:06.720334213 UTC

This looks very similar to report at XDA on AOSP9 issue https://forum.xda-developers.com/showpost.php?p=80549303&postcount=991
Looks to be resolved, as in https://forum.xda-developers.com/showpost.php?p=80549977&postcount=994
@MartinX3 : what was in that V10?

With the new image. I have bad news and worst news.
Bad news first. The reboot issue persists.
Worst news is that the 4G issue came back.
this is what i get in the journal when trying to activate the 4g from top menu:
Dec 16 21:38:19 Sailfish estart[6415]: [W] unknown:17 - file:///usr/share/jolla-settings/pages/mobile/mainpage.qml:17: Error: Qt.createQmlObject(): failed to create object:
                                           file:///usr/share/jolla-settings/pages/mobile/inline:1:1: module "com.jolla.settings.multisim" is not installed

Back to where we were. Sending you journal by mail.

No problem. I think I have a theory - as the port was started around the same time as the crash on XZ2c was reported (https://forum.xda-developers.com/showpost.php?p=80452073&postcount=931), I suspect I don't have proper fix for it in my base either. Symptoms, at least regarding reset, are the same.
AOSP issue seems to be fixed in https://github.com/MartinX3sAndroidDevelopment/bug_tracker/issues/31, so we will need to update AOSP base or just kernel. I'll work on it and will ping when the new images are ready.

Thanks a lot.

As far as I could see, main change was in the kernel. While new flashable image is being built, we should get the same effect (mostly) using OTA. For that, in terminal:
devel-su

to become root. As root
zypper ref
zypper up

That should pull and install droid-hal-apollo-img-boot and maybe few other packages. After install, reboot. During the next boot, it should flash boot image on boot partition. It should not go to GUI while it flashes boot. After flashing, it will reboot again and you should get to GUI.
Let's see how it will go.
As for image for flashing, it should be ready in 10-20 minutes.

After the reboot and getting to GUI i have no touchscreen. However the phone doesn't seem to reboot any more. I can leave it like that for a few minutes and wake it up by pressing the power button.

OK. Patch did change touchscreen driver. Now I wonder whether our touchscreen detection has been messed up by that. Or I disabled touchscreen.
If you have ssh access to the phone (wifi or usb), try to login and determine touchscreen device as we did earlier.
If you don't we have to flash new image (in usual location) and determine touch screen device using cat as we did earlier (/dev/input/event?), if there is any

I changed the device in /var/lib/environment/compositor/droid-hal-device.conf with what we had earlier (dev/input/event1) and it didn't work.
I tried cating all events and nothing did anything.

We have to determine the device again. I suspect it has either changed its name or description. So, if you have access to the device after booting to regular SFOS, check out

do we have /dev/touchscreen ?

which of the devices in /dev/input/event react to you touching the screen? The device that does, should go to /var/lib/environment/compositor/droid-hal-device.conf

There is a /dev/touchscreen but when i cat it doesn't do anything
No /dev/input/eventX reacts to anything. tried them all.

and in agreement with my theory, we have CONFIG_TOUCHSCREEN_SYNAPTICS_TCM=y dropped from kernel apollo config. It is possible that we removed touchscreen support as well. So, if you cannot find new touch device, I will reenable that config and make new kernel/image.
But looks we are on the right path as there are no crashes.
Just got your message, thank you. Fix is on the way :)

New kernel is ready. If you have access to device, please update via zypper ref && zypper up
Replace the touchscreen back to /dev/touchscreen. I hope it works now. Will start making new flashable image as well.

OK. The touchscreen works. And on top of that the reboot problem is fixed as it seems.
Now on the serious one. 4g internet still doesn't work. When i go to settings cellular network it says disabled. Telephony and sms work.

Good. Please send the log (journal and logcat). Easiest is probably to reboot and then grab from /root/shutdown
Also, just in case, please send output of getprop command. Send it via private email, please

I am now looking into what could be missing. As you pointed out, seems like at least multisim gui is one. Try to install jolla-settings-networking-multisim and let me know if it was absent

pkcon install jolla-settings-networking-multisim
Resolving                                                                                [ ==                                                              ]
Querying                                                                                [  ==                                                             ]          [                                                                 ] (0%)
Testing changes
Finished                                                                                [                                                                 ] (0%)
The following packages have to be installed:
 jolla-settings-networking-multisim-0.5.58-1.25.1.jolla.armv7hl Settings plugin for Multi SIM
Proceed with changes? [N/y]

looks like its missing, indeed. you may have to reboot after installing it.

https://www.youtube.com/watch?v=usfiAsWR4qU

:) I will tomorrow add multisim support (was sure its there, but somehow I missed it), finalize the builds and then we have to move over to OTA-enabled ones.
the last kernel is built with the faster timer, as updated by Sony AOSP devs. try to see if its any better.
great job, enjoy it!

Everything seems to work ok now. I'll obviously need to test more stuff and i'll take the phone with me the next few days to see whats going on.
But it seems we are in a good state now. Lets go from here.I'll test the new stuff once they are ready. Just ping me.
Thanks for all your hard work. This device is all i could ask for from a SFOS handset. :smiley:

Released and announced at TMO and XDA. Closing, thanks a lot for help!


VB version Blinky ?

Is there a VB version of the Blinky?

There is a C# version - See https://developer.microsoft.com/en-us/windows/iot/win10/samples/blinkyheadless


Move autoscale into DesiredState method for upgrade

Explain the changes

make sure noobaa autoscale configuration will added/updated to noobaa CR if noobaa CR missing the configuration

Issues: Fixed #xxx / Gap #xxx

After upgrading to 4.14, MCG endpoint minCount and maxCount in ocs-storagecluster are ignored,
since 4.13 noobaa CR missing autoscaling configuration, after upgrade this configuration was still missing and this created issue

https://bugzilla.redhat.com/show_bug.cgi?id=2227607
Testing Instructions:

install ODF in openshift 4.13 and upgrade it to 4.14
update noobaa endpoint maxCount to 2, wait for the second noobaa endpoint pod

[ ] Doc added/updated
[ ] Tests added

/assign @umangachapagain @jarrpa @iamniting @dannyzaken

Can you also correct the typo in the commit msg
move autoscal into DesiredState method for upgrade -> move autoscale into DesiredState method for upgrade

/cherry-pick release-4.14


Button in email message not correctly rendered

The button in the email sent is not correctly rendered.
As such, the user has only the alt text displayed.
Check this behavior and understand whether it's better to remove completely the html button or not.

Tested locally and button in email is correctly rendered, could you please add more details?
See the screen attached:

@sebbalex I guess we will be able to reproduce this just when a complete onboarding cycle will be closed. Or we could "test" the system by using the onboarding with the PCM ipa.

Attaching the needs-more-info label, I'd remove it from the milestone for now. What do you think @sebbalex ?

Works for me.


Invalid text of OWNERDRAW menu

Total Commander (x64) 8.52
Windows 8 64bit
pywinauto 0.5.2
Menu type = 256
Cannot get menu and submenu item's text. Returns that all items named - 'Ĉ'.
The next code rewrites right value:
pywinauto\controls\menuwrapper.py
103:    # OWNERDRAW case try to get string from BCMenu
        if item_info.fType & 256:
            mem = RemoteMemoryBlock(self.ctrl)
            address = item_info.dwItemData
            s = win32structures.LPWSTR()
            mem.Read(s, address)
            address = s
            s = ctypes.create_unicode_buffer(100)
            mem.Read(s, address)
            item_info.text = s.value
            del mem

If I comment this piece, all menu items have right names.
Also the problem is not reproduced on Windows 7 32bit.

Verified


Unable to view Logcat

Hi, thanks a lot for the extension, it's great to have some alternative to Android Studio. I've just installed it on VS Code 1.29.1, but when I try to open logcat I get the following error:
command 'android-dev-ext.view_logcat' not found
Does this look like a bug or is it something I'm missing?
Cheers!

Same here, just installed in VS Code 1.30.0 and I get the same exact error.
I have adb logcat installed and works fine from command line.

Fixed in 0.6.2


PropertyGrid 不支持 ExpandableObjectConverter

Feature request type
sample request
Is your feature request related to a problem? Please describe
子类属性不能直接绑定，能否支持和winform一样的 TypeConverter 转换
Describe the solution you'd like
PropertyItem 增加Children属性。展开显示子项
Describe alternatives you've considered
No response
Additional context
No response

https://handyorg.github.io/handycontrol/extend_controls/propertyGrid/

https://handyorg.github.io/handycontrol/extend_controls/propertyGrid/
文档没写这个功能吧？我看了源码好像没看到

已收到您的邮件,我会及时查看的!


API Down

Summary
I am using the simple code example with a user token. It's supposed to log in but fails as of now.
Reproduction Steps
I am using the simple code example with a user token. It's supposed to log in but fails as of now.
Code
import discord
from discord.ext import commands

bot = commands.Bot(command_prefix='>', self_bot=True)

@bot.command()
async def ping(ctx):
    await ctx.send('pong')

bot.run('.............')

Expected Results
The bot is supposed to login.
Actual Results
The bot fails to login and responds with
"2024-10-14 08:02:21 WARNING  discord.utils Info API down. Falling back to manual fetching...".
System Information
C:\Users\Penguin>python -m discord -v

Python v3.12.6-final
discord.py-self v2.0.0-final
aiohttp v3.7.4.post0
system info: Windows 11 10.0.22631

Checklist

[X] I have confirmed I am using unmodified discord.py-self and not the upstream discord.py.
[X] I have searched the open issues for duplicates.
[X] I have shared the entire traceback.
[X] I am using a user token (and it isn't visible in the code).

Additional Information
No response

It is up for me
discord-protos==0.0.2
discord-webhook==1.3.1
discord.py-self==2.1.0a4853+gcbf0f7a5

using this version

Thanks a lot.


Organize supplier/retailer endpoints

In the product grouping specifically it seems that the endpoints would be better organized by account type:

Product (Universal)
Product (Retailer)
Product (Supplier)

Would this also apply to other sections at all?

Review each and separate as supplier or retailer as appropriate:

[ ] Accounting
[ ] Organization
[ ] Product
[ ] Orders
[ ] Discovery
[ ] Tools
[ ] Files
[ ] Data


Flutter should have a ScrollbarTheme

As we are updating our scrollbar, we should also include a theme for Scrollbars.
Related issues:
https://github.com/flutter/flutter/issues/36412
https://github.com/flutter/flutter/issues/31753
https://github.com/flutter/flutter/issues/40107

Whoops, this already exists, thanks @johnpryan! https://github.com/flutter/flutter/issues/61362


Polyline click and show popup/callouts info box

Hi Guys,
Is possibile to show a popup info with same string when a polyline is clicked. I'm able to grab a click event on line but how to create a box ?
Thanks

This was reported before the first beta of v4. Assuming this is not relevant anymore.


Safari extension for opening downforacross.com urls in the app

Apparently Apollo's implementation is open source and wayyyyyyyyyy easier than using declarativeNetRequest
https://github.com/christianselig/OpenInApolloExtension/blob/main/Resources/content.js


PoolTimeoutException when renew Connection

Scheduler starting working properly , if any cassandra connection renew with 9160 has problem. where should be a problem, Cassandra or scheduler library.
Following Exception
java.util.concurrent.ExecutionException: com.netflix.astyanax.connectionpool.exceptions.PoolTimeoutException: PoolTimeoutException: [host=<IP_ADDRESS>(<IP_ADDRESS>):9160, latency=60001(60001), attempts=2]Timed out waiting for connection
Caused by: com.netflix.astyanax.connectionpool.exceptions.PoolTimeoutException:PoolTimeoutException: [host=<IP_ADDRESS>(<IP_ADDRESS>):9160, latency=60001(60001), attempts=2]Timed out waiting for connection
thanks

I have seen one more case also with same PoolTimeoutException,
We have started first node scheduler application, after some to we try to start another node of scheduler application, both node started but any one of the node we got PoolTimeoutException, that time cassandra server some connection under "TIME_WAIT" state, what was the reason, any help thanks.

Hi got following different cases when debug this case,

Try to add new node as scheduler client app

we have one node scheduler app running when we plan to add additional node and test scheduler functions,
============== Log Started ====================================
2019-01-01 12:44:48 INFO  AbstractCoordinator {org.apache.kafka.clients.consumer.internals.AbstractCoordinator$HeartbeatResponseHandler handle} - [Consumer clientId=consumer-5, groupId=scheduler] Attempt to heartbeat failed since group is rebalancing
2019-01-01 12:44:48 INFO  ConsumerCoordinator {org.apache.kafka.clients.consumer.internals.ConsumerCoordinator onJoinPrepare} - [Consumer clientId=consumer-5, groupId=scheduler] Revoking previously assigned partitions []
2019-01-01 12:44:48 INFO  Scheduler$ {com.pagerduty.scheduler.Scheduler$LoggingImpl trackResourceShutdown} - Shutting down SchedulingSystem...
2019-01-01 12:44:48 INFO  Scheduler$ {com.pagerduty.scheduler.Scheduler$LoggingImpl trackResourceShutdown} - Shutting down TaskExecutorService...
**2019-01-01 12:44:49 ERROR ConnectionPoolMBeanManager {com.netflix.astyanax.connectionpool.impl.ConnectionPoolMBeanManager unregisterMonitor} - com.netflix.MonitoredResources:type=ASTYANAX,name=DevClusterConnectionPool,ServiceType=connectionpool**
2019-01-01 12:44:49 INFO  Scheduler$ {com.pagerduty.scheduler.Scheduler$LoggingImpl trackResourceShutdown} - TaskExecutorService was shut down.
2019-01-01 12:44:49 INFO  Scheduler$ {com.pagerduty.scheduler.Scheduler$LoggingImpl trackResourceShutdown} - SchedulingSystem was shut down.
2019-01-01 12:44:49 INFO  Scheduler$ {com.pagerduty.scheduler.Scheduler$LoggingImpl reportIsolationDetectionWait} - Holding group=scheduler for topic=scheduler, partitions [] for 16500 milliseconds for proper isolation detection.
2019-01-01 12:44:51 INFO  AbstractCoordinator {org.apache.kafka.clients.consumer.internals.AbstractCoordinator$HeartbeatResponseHandler handle} - [Consumer clientId=consumer-5, groupId=scheduler] Attempt to heartbeat failed since group is rebalancing
2019-01-01 12:44:54 INFO  AbstractCoordinator {org.apache.kafka.clients.consumer.internals.AbstractCoordinator$HeartbeatResponseHandler handle} - [Consumer clientId=consumer-5, groupId=scheduler] Attempt to heartbeat failed since group is rebalancing
2019-01-01 12:44:57 INFO  AbstractCoordinator {org.apache.kafka.clients.consumer.internals.AbstractCoordinator$HeartbeatResponseHandler handle} - [Consumer clientId=consumer-5, groupId=scheduler] Attempt to heartbeat failed since group is rebalancing
2019-01-01 12:45:00 INFO  AbstractCoordinator {org.apache.kafka.clients.consumer.internals.AbstractCoordinator$HeartbeatResponseHandler handle} - [Consumer clientId=consumer-5, groupId=scheduler] Attempt to heartbeat failed since group is rebalancing
2019-01-01 12:45:03 INFO  AbstractCoordinator {org.apache.kafka.clients.consumer.internals.AbstractCoordinator$HeartbeatResponseHandler handle} - [Consumer clientId=consumer-5, groupId=scheduler] Attempt to heartbeat failed since group is rebalancing
2019-01-01 12:45:05 INFO  Scheduler$ {com.pagerduty.scheduler.Scheduler$LoggingImpl reportPartitionsRevoked} - Rebalancing group=scheduler for topic=scheduler, partitions revoked [].
2019-01-01 12:45:05 INFO  AbstractCoordinator {org.apache.kafka.clients.consumer.internals.AbstractCoordinator sendJoinGroupRequest} - [Consumer clientId=consumer-5, groupId=scheduler] (Re-)joining group
2019-01-01 12:45:05 INFO  AbstractCoordinator {org.apache.kafka.clients.consumer.internals.AbstractCoordinator$1 onSuccess} - [Consumer clientId=consumer-5, groupId=scheduler] Successfully joined group with generation 1757
2019-01-01 12:45:05 INFO  ConsumerCoordinator {org.apache.kafka.clients.consumer.internals.ConsumerCoordinator onJoinComplete} - [Consumer clientId=consumer-5, groupId=scheduler] Setting newly assigned partitions [scheduler-0]
2019-01-01 12:45:05 INFO  Scheduler$ {com.pagerduty.scheduler.Scheduler$LoggingImpl reportPartitionsAssigned} - Rebalancing group=scheduler for topic=scheduler, partitions assigned [0].
2019-01-01 12:45:05 INFO  Slf4jLogger {akka.event.slf4j.Slf4jLogger$$anonfun$receive$1 applyOrElse} - Slf4jLogger started

============== Log End ====================================
after this log I have checked connections in cassandra side , I got some connections under TIME_WAIT state.
root@csd12:~# netstat -an | grep 9160
tcp        0      0 <IP_ADDRESS>:9160            <IP_ADDRESS>:*               LISTEN
tcp        0      0 20.300.1.5:9160        20.300.1.1:54554       TIME_WAIT
tcp        0      0 20.300.1.5:9160        20.300.1.1:54556       TIME_WAIT
tcp        0      0 20.300.1.5:9160        20.300.1.2:56248    ESTABLISHED
20.300.1.1 -> node 1 with scheduler application
20.300.1.2 -> node 2 with scheduler application
only node 2 connection in ESTABLISHED state, node connections under TIME_WAIT , node 1 keep trying get new connection always return PoolTimeoutException.
@danwenzel any help on this problem,
thanks

@DWvanGeest @davidrusu any help above mention problem, We are in staging to release this application , any help most welcome. thanks


Bootstrap - visual indication of which page is currently being viewed on page menu

Should we have a visual indication of which page in page menu list is the current page? For screen readers we should use aria-current="page" on the current page's link.
The section menu already has a visual indicator of which is the current section but needs aria-current="true" for screen readers

Looks like this has been done in 3.12 - not sure who by!

@Timo did (one of our developers)
Merged in about two weeks ago

@FayCross @torinfo @TimoBoer I've re-opened this because I'm a bit concerned that it doesn't pass our usual goal of not adversely impacting existing projects. I think it needs to be controlled by an optional property that is off by default or some other method that doesn't impact custom themes by default. I've only done some quick checks so far and I think it's mostly fine with the bundled themes but any theme that has a light background to the navbar and therefore dark link text for contrast is instantly broken by this change because the contrast is wrong e.g. dark green link colour on black background.
I know we've made other changes in 3.12 that require updates to custom themes but they don't really impact existing projects but this does.

@FayCross well perhaps yes but my main point was if it's on by default it mustn't break existing projects. We only have a few bundled themes with Bootstrap but I've just been checking those:
default theme - black on black so doesn't show
dark black & grey - black on black so doesn't show
Experimental section pages - not relevant as replaces nav bar
Flat Black & Green - works fine because black bg with white text
Flat Blue & Grey - works but really ought to be the hover colour rather than black
So even with the bundled themes there are some small issues and in my develop I have at least 6 custom themes where this either breaks or requires changes to the custom theme to be optimal.
We have a navigation bar optional property so perhaps we should now add 'current page' colour options to that anyway but we can't ignore the fact that institutions have custom themes and at the moment this requires changes to those themes for existing projects to work without problems.
Yes just changing border might have less impact but would need to be tested and could still have issues or not show if on by default. I haven't looked at the code yet does it have a hard coded background colour I'm guessing it does. Perhaps a border could be triggered but without a hard coded colour so that it picks up the relevant theme colours? I don't know just thinking out loud but we definitely need to change something.

@FayCross just looking at this further and the relevant commits I'm not sure what is the best way to deal with this. I could easily update the custom themes I have developed or have control of but it's obviously about all the other custom themes and projects in use out there that we can't control. We can obviously tweak the bundled themes so I'm wondering if there's another check or new custom style we can add for now so that it only impacts themes that meet a detectable condition? Obviously the aria changes are fine.

@FayCross @ronm123 The idea is to update the themes. We did not do that yet.

@torinfo update what themes?
Bundled themes fine.
Custom themes that we have access to fine (sort of).
But this currently causes an immediate, noticeable and undesirable impact on any theme where the default styling doesn't work and that's not good at all. We need to agree a solution to that so let's discuss in our meeting later?

@ronm123 just committed a possible way of doing current page highlight. Default is underlined text (seen in default theme) as this will mean that the colour will always be ok in custom themes (easier than adding border as we don't know suitable colour for border). Can override this to have background colour instead in individual themes (only added to Apereo theme so far). Only thing left to do would be add new option to xwd so you could specify active colour background colour if you have a custom colour added to project for nav bar. What do you think?

@FayCross yes I think that's more predictable and less likely to have unforeseen impact. Obviously the first part of that is what I also tried by using the new style of activePage in custom.css rather than just active in bootstrap.css and as you say that means we can change it as we see fit for bundled themes and custom themes that we control. The one thing that I would add is:
text-underline-position: under;
I've always hated the way the default underline style works and used border-bottom styles instead but the position option is much simpler and as I understand it works with most modern browsers these days.
I've just tested that and it seems to work fine with my tests projects so shall I commit that or do you want to add that?
Yes ideally we should add the nav bar option too.
What about the other bundled themes are you going to change those or shall I? I think in most cases the activePage background colour should be the same as the hover colour do you agree?

@ronm123 fine for you to change the default css for underline. Could you change the themes please? I think you made most of them so will have a better idea of colour to use. I don't mind which colour you choose.

@FayCross @torinfo ok I'll add the change to custom.css and check and update the bundled themes tomorrow.

@FayCross @torinfo You may have seen I committed changes to each of the bundled site themes on Friday but haven't yet closed this issue because I have a quick question about the default theme:
I see this currently has an activePage background colour of #333 on your computers is that visible enough?
On my normal monitors I would say it's ok but on my 4k monitor it's possibly a bit too subtle.
So should we make the #333 just a bit lighter e.g. #404040
Also should we add the link hover colour so #6FD9D9 and in that case the background possibly doesn't need to change?


Providers and contexts relationships

A follow-up to #21604
The question is what and where of this information should go.
Separate instances of the provider can be loaded in the separate library contexts.
Several instances of the same provider in the same context using different section names, module names (e.g. via symlinks) and provider names. But unless the provider does not support some configuration options, the algorithms in this case will have the same provider property and the result of fetching is not determined. We strongly discourage against this trick.
The run-time change of the loaded provider configuration is not supported. If it is necessary, the calls to OSSL_PROVIDER_unload with the following call to the OSSL_PROVIDER_load or OSSL_PROVIDER_load_ex should be used.

@mattcaswell is there anything I missed from the discussion? Where should this information go?

Other edge cases to consider are:

The case where configuration exists and "activate = 1"
The case where configuration exists and there is no "activate" line, what config take precedence (config, app provided, or a merge of config and app provided).

There should be some document discussing the various API choices and edge cases. I'd put it in doc/designs

Thanks, pushed as a part of #21604


14 parsing single character variables fails

Single character references were not correctly extracted from block_content.
Reason was the regex used to find them.

[x] replaced all occurences of \$\w[\w\[\]]+ with \$\w[\w\[\]]*  (i.e. using * instead of + )
[x] added unit tests to check that single character references get correctly identified, extracted and resolved.

I tried to adapt for single character keyword vectors. For single component it worked, so I think the issue is fixed.
I have no clue why and when this "$\w[\w[]]+" was introduced, but probably "someone" had no single char. keywords in mind. And it is surely a bad manner.
I marked an issue that I found with mixed string lists in test_dictReader.py:594, any idea what I missed there?

oops. No python string concatenation. This is simply substitution.


Extend AvS config model to support Tags

related: https://github.tools.sap/orgs/kyma/projects/25/views/10

/test pre-kyma-environment-broker


Write common interfaces for the different kinds of transforms we identify in the dataflow read pre-processing pipeline

Should be done AFTER https://github.com/broadinstitute/hellbender/issues/459

This issue was moved to broadinstitute/hellbender-dataflow#32


Where can I find sentry-symbols.js?

I didn't use "Sentry Wizard" to implement this library with my Electron project. How can I find the sentry-symbols.js file?
As a workaround, I'm downloading the debug information file myself to ~/Download/ and running:
./node_modules/.bin/sentry-cli upload-dif -t dsym ~/Downloads/electron-v2.0.11-darwin-x64-dsym.zip --org my-org --project my-project

The script can be found here, you should be able to use it by just calling it like node sentry-symbols.js
https://github.com/getsentry/sentry-wizard/blob/master/scripts/Electron/symbols.js
Sentry Wizard just copies it to your project and makes sure all deps are installed.

@HazAT Ah! I was Googling for a while but didn't come across getsentry/sentry-wizard. Thanks!

FYI @HazAT our app is based on the popular electron-react-boilerplate project, and I posted in this issue some things you might be interested in how we setup electron-sentry with that project: https://github.com/electron-react-boilerplate/electron-react-boilerplate/issues/1560
Y'all have it pretty well-covered in your docs, but that's how we do it in a real day-to-day app. The main "ahhh nice" thing was cleaning up breadcrumb logging from electron-log and redux-logger.


Fix job service gRPC stream cancellation handling

This is a follow up to https://github.com/armadaproject/armada/pull/3555 where I tried to get cute about handling stream cancellation. I updated the code from performing string matching to checking whether the error was of type context.Canceled and this introduced a cosmetic bug. The issue with this is that the errors returned in the stream are gRPC specific, so this pull request updates the unite test and fixes the logic to continue and not log the cancellation as some other error.

Unit test failures seem unrelated
     🧪 - com/armadaproject/armada/internal/lookoutv2/repository | Failed
     🧪 - com/armadaproject/armada/internal/lookoutv2/repository | Failed
     🧪 - com/armadaproject/armada/internal/lookoutv2/repository | Failed

Closing this one, as the query API will supercede this effort.


[WFCORE-5888] Upgrade httpcore to 4.4.15

Fixes https://issues.redhat.com/browse/WFCORE-5888

Please find git-tag, git-diff, release notes links in the Jira.

@boris-unckel the Jhonzon removal made a conflict on this one. Would you mind rebasing this? thanks!

@boris-unckel thanks


Add new codemirror-promql-based expression editor

based on the work done by @juliusv
Should fix #4028

ah yeah that's true, I forgot that,  nodejs should be upgraded to the v14 at least

is a strong requirement to support node v10 + v12 ? Or is it fine to drop them and move to node v14 ?

is a strong requirement to support node v10 + v12 ? Or is it fine to drop them and move to node v14 ?

I'm not too famliair with the UI part here, but if Prometheus 'forces' a minimum of node v14 then I see no reason to stick with 10 & 12. It seems v14 is the default at the moment too.
I also checked the code but it only looks like Thanos is testing against 10 & 12, not that it is 'used' perse?
In the config.yaml for Thanos .circleci this is used: - image: cimg/go:1.15-node  which is: https://github.com/CircleCI-Public/cimg-go/blob/master/1.15/node/Dockerfile
Which then uses -> https://raw.githubusercontent.com/CircleCI-Public/cimg-node/master/ALIASES and then grep on LTS, which is lts=14.16.0
Soooo.... I think we build on node v14 and we should test against v14 and not 'bother' with < v14 anymore.

alright the build is finally passing with nodeJS v14.
I supposed then the build of Node 10/12 should be unchecked in the settings to remove them from the required list.
Hope it is fine for you as well :)

ah the e2e test are not passing. Mmm that's quite weird I didn't touch at the golang part.
Did I break something unexpectedly ?

ah the e2e test are not passing. Mmm that's quite weird I didn't touch at the golang part.
Did I break something unexpectedly ?

Always blame the user for breaking tests :p I have no idea actually, I'll try a local test :)

Nice thanks @wiardvanrij !

thanks :) and np !

I only would propose to enable experimental editor by default. WDYT?

I guess it's more depending if you want to rely on the Prometheus choice or not ^^. It's not enable by default on Prometheus side, so I assumed it would be the same here. From my point of view, it's fine to enable it by default :) specially since it should be the case in the next Prometheus release (I hope)

Also I am not sure, but did we already enabled new UI by default? If not, we could too

I'm not sure as well, but when I tried locally I was on the old UI at the beginning. So I supposed by default the new UI is not enabled by default.

btw for the record, I'm relying on the code done here: https://github.com/prometheus/prometheus/pull/8634

alright I enabled the experimental editor by default, but I didn't find how to enable the new ui by default :/. If you can point me what boolean I should change @bwplotka or @onprem , I would be greatful :D
I also managed to use the pathPrefix in the experimental editor (I forgot to use it). Not sure that's the correct way, so let me know if it's fine like that.

lol the e2e tests are failing again. Guess a retry will fix it ? :D

Hey @Nexucis, thanks for the PR!

is a strong requirement to support node v10 + v12 ? Or is it fine to drop them and move to node v14 ?

I'd say, no. At the time when these CI Jobs were added, Node v12 was the LTS version so we were testing on 10, 12, and 14. Now that the v14 is LTS, we can move the CI jobs to v14 and maybe v15.

enabled the experimental editor by default, but I didn't find how to enable the new ui by default :/. If you can point me what boolean I should change

There isn't a single variable which you can flip to make the new UI default. It will require a bit more work than that (changing prefixes in react routes, handling the go code that serves the UI etc). Let's do that in a separate PR.

Btw could be a good idea actually to generate the assets at the ci level (and so to ignore this file in git). Like that the update of the assets cannot be missed

Yes, we discussed that briefly during office hours I guess but there was no concrete discussion (like a GitHub issue) on that point. I think that moving make assets step to build-time will reduce a lot of friction on the contributors' side but there are a few cons as well, for example, Nodejs will be required for anyone who's building Thanos from the source.

there are a few cons as well, for example, Nodejs will be required for anyone who's building Thanos from the source.

well when you are starting to build from the source a project, then it's quite fine to install the language required to build it. As long as you are ready to install golang, installing nodejs shouldn't be an issue :D
Then if it's more a developer issue, like backend developer doesn't want to be bothered by nodejs, then adding a default index.html in case the folder dist doesn't exist should solve the issue. The build will pass and so you can focus on the backend only.


Fix icon align with input.

Closes #332
Bug fix
What is the current behavior?
The Icon is not aligned with the input field.

What is the new behavior?

Supabase UI is being deprecated.
As part of that, we are closing Pull Requests in this repo for now.
If you'd like to still make these changes, you could consider making these changes in https://github.com/supabase/supabase/tree/master/packages/ui

We are moving the components to the main mono repo at https://github.com/supabase/supabase.
The auth component has been moved to it's own repo and package. https://github.com/supabase-community/auth-ui. You can also read the docs for auth ui here.


Updated to use latest client.

Mergeable PR is mergeable
Lots of breaking changes in the client so lots of little bits needed updating.
Mostly consists of property relocations from the client.
Also needed to change the fixtures for the tests as we don't just have one big render response as we use views now (Delta).

After the client is merged I will update the PR with the correct release tag for the client and not just some branch commit hash.

This has now been updated with a release tag. Although it'd be nicer if it was using a published version from npm.


Heading "Unlimited content sharing" has incorrect information.

The heading Unlimited content sharing has incorrect information. It implies that ALL premium SKUs allow unlimited content sharing with user free licenses.  It says (With Premium, anyone, whether they're inside or outside your organization can view your Power BI content including paginated and interactive reports without purchasing individual licenses.)
This is now incorrect with the newer EM premium SKUs! In this other Power BI Docs (https://docs.microsoft.com/en-us/power-bi/developer/embedded/embedded-capacity#capacity-and-skus) it clearly states 'Only the P SKU allows free Power BI users to consume Power BI apps and shared content, in Power BI service.'.
Can this information be updated please? It implies that any Premium SKU has this capability but that is incorrect. Only the P premium SKUs allow this, and EM premium SKUs do not.
Thank you.

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

ID: 18013a6f-b02d-30d4-3b6d-93295624f352
Version Independent ID: e307e1d7-e565-8742-e563-86d596d7d1e1
Content: What is Microsoft Power BI Premium? - Power BI
Content Source: powerbi-docs/admin/service-premium-what-is.md
Service: powerbi
Sub-service: powerbi-admin
GitHub Login: @davidiseminger
Microsoft Alias: davidi

Thanks for your question, @emilylait ! Assigning to the author to investigate.

Hi @emilylait ,
Thank you for your suggestion.  We've made the update and set the article to republish.
All the best,
The DOCS team


Not able to derive city names using Geotext library

Hi,
I have texts extracted from certain contexts of files like:
'.  Education  :  05/2012  DePaul  University  Graduate  School  Master  of  Science  in  E-Commerce  Technology  Morgan in  E-Commerce  Technology  Morgan  State  University  05/88  BS  in  Computer  Science  Technical  Training  or  Certifications '
'Information  Technology  Southern  New  Hampshire  University  Expected  2015  Associate  of  Arts  ,  Graphic  Design  Penn'
These contain the name of some university along with some city names like 'Morgan city' in the first sentence and 'New Hampshire' in the second sentence. I am using the code mentioned below to extract the city names from the text using the 'geotext' python library:
from geotext import geotext
places = GeoText(sent1) -- or sent2
        print(places.cities)

I had used pip install geotext for the installation on Python 3 Anaconda 3.0 in Windows 7.
The output I am getting is ['University'] and ['University', 'University']. These are clearly not city names.
I would like to mention that the post installation I have had some 'expecting bytes not strings' errors and 'cannot find name GeoText' errors which I corrected manually.
I changed the import statement in init.py to contain geotext instead of GeoText and
I changed the string to string.encode() for the byte array errors.

You guys are both using Python 3 right? I was having the same issue. My temporary workaround was to move the contents of geotext.py into the init file, change the file reading from 'rb' to 'r', remove the .decode(encoding), and enclose the print statements. Works as a quick solution but definitely not worthy of a pull request to this repo. @elyase would you be ok with me submitting a pull at some point to try and make this lib both 2 and 3 compatible? Really like the functionality of this module

Hi guys, sorry that I haven't been following the issues. I thought I was the only one using the library. Promise to take a look in January. @cdpeuter a PR would be very welcome!

Hey @elyase I like geotext's functionality. Used it for my project :smile: It works how I expected it to be. I had some problem with importing it with python3 as others mentioned above. I fixed it and now it works with python3.
I pulled a request, is it ok? :+1:

Hi Benjamin, I will take a look when I come back from holidays. Right now my internet is somewhat limited. Thanks a lot!

I merged @freezer9 pull requests. I have tested it with conda 2 and 3 environments and it seems to work well. Please upgrade with:
pip install geotext -U


Add a judgment condition(>API 26) when calling "FragmentManager.isSta…

Add a judgment condition(>API 26) when calling "FragmentManager.isStateSaved" method.

I signed it!

@CaiPeng can you explain a bit why this addition is needed?

When the dialog is shown, I clicked the denied button, and then my App crashed.
The log shows：
  java.lang.NoSuchMethodError: No virtual method isStateSaved()Z in class Landroid/support/v4/app/FragmentManager; or its super classes (declaration of 'android.support.v4.app.FragmentManager' appears in /data/app/.../split_lib_dependencies_apk.apk:classes2.dex)                                                                      at pub.devrel.easypermissions.RationaleDialogFragmentCompat.showAllowingStateLoss(RationaleDialogFragmentCompat.java:48)                                                                      at pub.devrel.easypermissions.helper.BaseSupportPermissionsHelper.showRequestPermissionRationale(BaseSupportPermissionsHelper.java:43)

The FragmentManager in the class you're modifying here comes from the support library.  The isStateSaved method was added in support lib 26.0.1:
https://developer.android.com/reference/android/support/v4/app/FragmentManager#isstatesaved
What are your app dependencies?  Are you using a lower support library level?  I don't think adding an SDK version check should matter here.

@CaiPeng I am going to close this since it been a few weeks without a response and I can't see the motivation for this PR, however if you have more information please let me know and I will re-open.
Thanks for the contribution!


AbstractProvider::getAuthorizationHeaders() - why not abstract?

Hello,
I just spent ~20 minutes chasing my tail trying to work out why an authenticated request wasn't working, at which point I discovered that I had to implement the getAuthorizationHeaders() method in my custom provider.
If it has to be implemented, is there any reason that this method is not abstract in the first place?
I'm happy to submit a PR but wanted to check that there wasn't some use-case that I hadn't thought about.

Only one reason:
There is nothing in the specification that requires using headers as the method for passing the authentication token with the request.
Some providers use query strings to pass the token. The ones that do use headers have different formats with Bearer being the most common, though there are exceptions.

That makes sense.
It may be useful to make the documentation clearer on this point - even just updating the line about AbstractProvider here would help. Shall I PR this?

That would be great!


add Electromobile_In_Elevator_Detection

新增电梯内电瓶车检测

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Compatibility with Jupyterlab 0.32

I got this theme a few weeks back I think. And I recently had to update Jupyterlab to 0.32 but it seems that the theme is no longer compatible.
Is this being addressed (or probably has already been addressed already and I missed this)?

Yes, I had the same problem and I made the necessary changes to make it work with jupyterlab 0.32. However, since I haven't put this on npm yet*, you need to rebuild and reinstall the extension in the same way you did the first time, but with the updated code (current on GitHub, you can get it with a simple git pull). It should then work. Let me know if it still doesn't and I'll look into it.

I haven't put this on npm yet because the jupyterlab team said that the API will probably change in the beta phase, and I'm now swamped with work and I don't know how fast I'll be able to fix it if everything breaks. Once the extentions API is stable, I'll publish this on npm and the upgrade process should be smoother.

Excellent! I thought I would check before trying anything else. I will try and rebuild it with the updated version and come back if I encounter any issues.
BTW love the theme 😀

With the changes I pushed 2 days ago it should be working with jupyterlab 0.32. It does for me without problems. What error do you get when you try npm run build?

Thanks for your swift reply. I thought it might be a missing dependencies issue, so after running npm install I was able to run npm run build without errors. However then jupyter labextension install failed with There appears to be trouble with your network connection. (I didn't think it was actually the network because I tried in several different places). I thought it may be to do with the socks version because of the following warning MaterialDarker > npm > npm-profile > make-fetch-happen > socks-proxy-agent ><EMAIL_ADDRESS>If using 2.x branch, please upgrade to at least 2.1.6 to avoid a serious bug with socket data flow and an import issue introduced in 2.1.0?
But then after re-running npm run build,  suddenly jupyter labextension install was successful. I am somewhat confused. Apologies I've very much at the beginner-learner stage with JS!

I'm glad it works now. I've never seen the error you encountered, but I'll keep my eyes open in case it pops up in future versions.


Incorrect autocomplete suggestions for hyphenated class names.

When the user types a class name containing a hyphen, the autocomplete suggestions stop when the user gets to a hyphen. It then continues again once the user has typed past that hypen, but the suggestions are no longer the most relevant because anything preceding the hyphen is ignored.

The extension currently adds completion items using the JavaScript API https://docs.nova.app/api-reference/completion-item/. It's possible that the better solution may be to use an xml file for generating completion items, but I have not yet been able to generate a completion item this way. The Panic docs discuss this at https://docs.nova.app/syntax-reference/completions/.

I have an email into Panic asking if they have any suggestions. Will add any information they might send.

After talking to some devs on the Nova Extension Discord channel, the consensus seems to be that it is not currently possible to change the user entered text evaluated for completions when using the JavaScript API. As it stands, Nova considers the word boundary (with no hyphens) to be the evaluated user text. This issue will likely need to be addresses on the Nova side.

The extension currently adds completion items using the JavaScript API https://docs.nova.app/api-reference/completion-item/. It's possible that the better solution may be to use an xml file for generating completion items, but I have not yet been able to generate a completion item this way. The Panic docs discuss this at https://docs.nova.app/syntax-reference/completions/.

I have discovered that the xml method of providing completions also has some limitations. It does not appear to offer the ability to include details, documentation, or color symbols. Still waiting on a response from Panic to determine a best way forward.

Quick update. I am in contact with Panic and working through this issue.

It has been determined that this issue will need to be resolved in Nova and will be addressed in Nova 1.3.

This issue should now be fixed in Nova 2.0.

Weird question: this doesn't seem work in Blade templates (if you start typing, e.g., bg-blue-500, then the autocompletion stops when you type the first hyphen). I see Blade is listed in the extension configuration as a supported file type; is there something that could be happening in the Blade extension that's borking this up somehow? It looks like it has a simple XML file for completion and I'm not seeing anything obvious there, but my knowledge of Nova extensions is pretty limited.


Specify mock requirement for tox

Adds mock requirement to tox.ini
Without this git clone ...  followed by tox fails with ImportError: No module named 'mock' in all environments.

great, thx.


Can we validate AD Token and B2C Token using single validation code?

Based on my analysis,
For validating AD Token we are using UseWindowsAzureActiveDirectoryBearerAuthentication() from Owin
For validating B2C Token we are using UseOAuthBearerAuthentication() from Owin
I saw issuer, audience and metadata url are different for AD and B2C tokens.
My Scenario is that my client will pass either AD token or B2C token to my API. But my API should have single code to validate both token. Is it possible?

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

ID: b05bb7df-98fc-1342-640d-02063f6d8a11
Version Independent ID: f6ac357f-f846-83c5-f19f-91e1bc0954e3
Content: Token reference in Azure Active Directory B2C
Content Source: articles/active-directory-b2c/active-directory-b2c-reference-tokens.md
Service: active-directory
GitHub Login: @davidmu1
Microsoft Alias: davidmu

@vetrivelmp Thanks for your feedback! We will investigate and update as appropriate.

@vetrivelmp Can you try using UseJwtBearerAuthentication to validate the token. Please refer to post for more details on using this extension method.

@vetrivelmp We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.