Incorrect exclude list validation in cloud_verifier

Is your an issue a feature request? If so, please raise it as an enhancement
Environment

OS / version: Fedora35
Processor architecture: x86_64
TPM Manufacturer:
Keylime version: current upstream [e7dcad7]

Description
On
https://github.com/keylime/keylime/blob/master/keylime/cloud_verifier_common.py#L303
there is lists.get('exclude')  without a fallback option.
Expected behavior vs. actual behavior
cloud_verifier should deal with exclude key absence.
 2022-03-29 09:46:08.421 - keylime.cloudverifier - ERROR - 'exclude'
 Traceback (most recent call last):
   File "/usr/local/lib/python3.10/site-packages/keylime-6.3.1-py3.10.egg/keylime/cloud_verifier_tornado.py", line 835, in invoke_get_quote
     failure = cloud_verifier_common.process_quote_response(agent, json_response['results'], agentAttestState)
   File "/usr/local/lib/python3.10/site-packages/keylime-6.3.1-py3.10.egg/keylime/cloud_verifier_common.py", line 143, in process_quote_response
     quote_validation_failure = get_tpm_instance().check_quote(
   File "/usr/local/lib/python3.10/site-packages/keylime-6.3.1-py3.10.egg/keylime/tpm/tpm_main.py", line 1195, in check_quote
     return self.check_pcrs(agentAttestState, tpm_policy, pcrs, data, False, ima_measurement_list, allowlist,
   File "/usr/local/lib/python3.10/site-packages/keylime-6.3.1-py3.10.egg/keylime/tpm/tpm_abstract.py", line 279, in check_pcrs
     ima_failure = AbstractTPM.__check_ima(agentAttestState, pcrs[config.IMA_PCR], ima_measurement_list, allowlist,
   File "/usr/local/lib/python3.10/site-packages/keylime-6.3.1-py3.10.egg/keylime/tpm/tpm_abstract.py", line 208, in __check_ima
     _, ima_failure = ima.process_measurement_list(agentAttestState, ima_measurement_list.split('\n'), allowlist,
   File "/usr/local/lib/python3.10/site-packages/keylime-6.3.1-py3.10.egg/keylime/ima.py", line 316, in process_measurement_list
     running_hash, failure = _process_measurement_list(agentAttestState, lines, hash_alg, lists=lists, m2w=m2w,
   File "/usr/local/lib/python3.10/site-packages/keylime-6.3.1-py3.10.egg/keylime/ima.py", line 220, in _process_measurement_list
     exclude_list = lists['exclude']
 KeyError: 'exclude'

Steps to reproduce problem

modify tenant.py to send allowlist without exclude key:

            #self.allowlist = ima.process_allowlists(al_data, excl_data)
            self.allowlist = {'allowlist': al_data}

Thanks for finding this. I already wanted to restructure the IMA allwlist/exclude API because it is more than that, but I haven't got around doing it.

@mpeters can you assign this to me?

Is it still relevant?

I don't think so, because that entire code has changed. @kkaarreell can you confirm this?

The IMA policy format now has changed significantly, so I don't think this issue applies anymore.


Fix concurrent access to local repository

remove takari , upgrade maven-resolver version to 1.6.1, try to resolve  #14 #281

I ignored the maven-resolver v1.4.1 unzipped from maven-core and copy v1.6.1 into /lib/ext.
It is a pain point that newer maven-resolver versions will no longer automatic upgrade through maven-core.
Any nicer ideas?

It is a pain point that newer maven-resolver versions will no longer automatic upgrade through maven-core.
Any nicer ideas?

What do you mean ? I don't understand...

What do you mean ? I don't understand...

Sorry for my poor english... I excludes maven-resolver* unzipped from maven-core in maven-distro.xml
    <artifactSet to="/mvn">
        <artifact id="org.apache.maven:apache-maven:tar.gz:bin">
            <unpack useRoot="false"
                    excludes="...lib/maven-resolver-api*,lib/maven-resolver-impl*,lib/maven-resolver-util*,lib/maven-resolver-spi*"/>
        </artifact>
    </artifactSet>

and copy v1.6.1 to /mvn/lib/ext

so even we upgrade maven which uses higher version of resolver, it still will be v1.6.1

I understand now.
I think this PR is obsolete with #393 which includes the resolver 1.6.2 release.
However, I need to check that the takari one is actually not included and that we're actually using the new locking mechanism.

I understand now.
I think this PR is obsolete with #393 which includes the resolver 1.6.2 release.
However, I need to check that the takari one is actually not included and that we're actually using the new locking mechanism.

So upgrading to the new 1.6.2 maven resolver is not sufficient, as the default locking mechanism is just to not lock anything.  There are two implementations: one that only works for in-JVM locking (so between threads), and another one that need a Redis server to run.  So there's currently out-of-the-box option for mvnd.
I'll see if I can write a small dedicated client/server that could be launched by the client if not already started and used by all daemons.

So upgrading to the new 1.6.2 maven resolver is not sufficient, as the default locking mechanism is just to not lock anything. There are two other implementations: one that only works for in-JVM locking (so between threads), and another one that need a Redis server to run. So there's currently out-of-the-box option for mvnd.
I'll see if I can write a small dedicated client/server that could be launched by the client if not already started and used by all daemons.

You are right, DefaultSyncContextFactory in resolver 1.6.2 uses  empty implementation, this PR don't really fix #281 . I'll gonna close it.


[SPARK-35498][PYTHON] Add thread target wrapper API for pyspark pin thread mode

What changes were proposed in this pull request?
Add thread target wrapper API for pyspark pin thread mode.
Why are the changes needed?
A helper method which make user easier to write threading code under pin thread mode.
Does this PR introduce any user-facing change?
No
How was this patch tested?
Manual.

Test build #138856 has started for PR 32644 at commit af94332.

Test build #138856 has finished for PR 32644 at commit af94332.

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

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

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/43378/

Shall we file a JIRA?

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/43378/

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

Merged to master.


Ensure that actions executed from "Find Action..." work correctly

investigate how intellij handles this case (esp. selection-based actions)
some actions (sliding out selected) seem to behave in an undefined way, it must be resolved
based on the investigation result we may want to:

not show actions in Find Action... if possible
ignore action execution
take some other steps

The main priority here is to keep(/provide) the best UX

This should be partially resolved by #243. However, it is still possible to call selected-based actions.
Steps to reproduce:

right non-current branch
call Checkout Selected Branch from Find Actions...

Actual:

branch checkout performed

Expected:

undefined


detect hardware codec capabilities

There are limitations to the hardware-accelerated codecs supported by each device (nvidia video card, intel igpu). Ideally, ErsatzTV would detect compatibility and fall back to software codecs as needed.

The major complication here is how many different platforms and architectures are supported by ErsatzTV.


boards native_{posix,sim}_64: Remove hwmv1 compatible board definitions

To use this functionality one must now use the native_{posix,sim}//64 (variant) version.
The old hwmv1 compatible names for these boards were left provisionally while all tests in tree were ported.
That being now done, these old names can be removed.
After this change one cannot build anymore targeting native_{posix,sim}_64, but must instead build
targeting native_{posix,sim}/[native]/64. For twister tests the old name is already not valid.
Note: There is no special urgency in merging this. This is just the last hwmv2 cleanup related to these 2 boards.

@fabiobaltieri can you merge this please as another PR needs these changes?


Create Backend

Create a backend named folder in repo
install express mongo db
setup http server using express js
integrate mongo atlas with backend and test the functionalities (I'll provide the atlas server)
join the atlas server on local mongodb compass application
mongo compass local setup needs to be done by both @sunilwane @SamikshaKadam19
create basic mongodb collections for routes, traffic lights, and user sessions
check everything properly before creating a PR

#9 worked on this and completed


S3: ByteStream::new can't be used for putting objects

ByteStream::new takes a Stream<Item = Result<Bytes, io::Error>> and this is sufficient for representing a response stream when retrieving an S3 object.
However, for a PutObject request, the Content-Length header is required by S3 and without it S3 will treat it as a bad request.  Because ByteStream::new sets size_hint to None, this results in no Content-Length header in the request.
I propose adding a new_with_size method to ByteStream that sets size_hint to the size specified by the caller.  This would allow ByteStream to be used for PutObject requests and would allow for streaming large files without having to buffer the entire file in memory.

I just ran into the same issue.

It appears this was fixed with #1762 in 0.44.0.  Are you still seeing the issue with that version?

Yep, that’s the only version I’ve used… odd.

Just discovered this but the solution unfortunately requires knowing stream size prior to putting an object into S3.
Anyone find a work-around to knowing object size for streaming puts?


Add missing keys from json

Some keys are missing compared to what's in the JSON document. This PR provides the missing keys.
Thanks for the great work :)

Coverage remained the same at 100.0% when pulling a88aa46e77cef387a93820f87f1b4c047a06381d on vjousse:add-missing-keys into 613e098fc060fad749db3ff66a21e93774f58f66 on alexmick:master.

Great job on adding those keys, I had no use for them in my projects so didn't bother but I'm glad their useful to you !


WIP

Signed-off-by: Michael Gasch<EMAIL_ADDRESS>

Codecov Report

Merging #16 (2fe2518) into main (2217871) will increase coverage by 0.82%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main      #16      +/-   ##
==========================================
+ Coverage   88.88%   89.71%   +0.82%
==========================================
  Files           4        4
  Lines         162      175      +13
==========================================
+ Hits          144      157      +13
  Misses         11       11
  Partials        7        7

Impacted Files
Coverage Δ

memlog.go
84.90% <100.00%> (+2.10%)
:arrow_up:

Continue to review full report at Codecov.

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


IOS - Entering Rate value in reimburse page of workspace is causing the value and cursor to behave randomly like digits entered quickly are removed from the UI for a second and added UI again reported by @aneequeahmad

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Open IOS app user icon to open settings.
Select any workspace > reimburse expenses.
Tap on Rate text-field so that it gets focus and keyboard opens.
Enter some digits quickly like 89786.987 and move cursor after 897 and enter 123 quickly

Expected Result:
Should show the entered digits without removing the digits or moving the cursor
Actual Result:
Digits  are removed and added again also cursor moves randomly at times.
Workaround:
Unknown
Platform:

Where is this issue occurring?

iOS

Version Number: 1.2.9-0
Reproducible in staging?: Y
Reproducible in production?: Y
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: https://user-images.githubusercontent.com/43996225/192906134-41c76c0d-c8fe-4d3c-83fa-2b8e1533b46a.MP4
Expensify/Expensify Issue URL:
Issue reported by: @aneequeahmad
Slack conversation: https://expensify.slack.com/archives/C01GTK53T8Q/p1663236792965219
View all open jobs on GitHub

looks like dupliccate (https://github.com/Expensify/App/issues/11352)

@sketchydroide I'm not sure the other issue will fix this issue as well, because the other issue says the last digit is removed as max digit limit is reached and we shouldn't allow the user to add digit when max digit limit is reached.


[v6][Bug] Make user profile image circle instead of rounded-corner-square

In Tabler theme (both light and dark), when using the horizontal layout (but others should have the same), the top-right corner shows the user image and name. The user image is square with rounded corners right now… but I think circles are much better to represent user profile images. First, faces look good in circles because both faces and circles are round. Second, to me at least, if I see a circle image, I assume that’s a user profile pic, because that’s what social media has gotten me used to think. So having it as circle might be a small intuitive clue that the image is for the user.

I'll close this one since it's already a circle 👌 not sure when and who did it 😅


Server crashes on start up.

log.txt

Cant seem to reproduce with just FabricApi-0.57.0+1.19 and FractalPortals_Fabric-1.19-1.4.0. Can you confirm if it still crashes on your end with just fabric api and the mod?

nvm, fixed in 1.4.1


Replace imgur with cloudinary

Closes https://github.com/prisma/docs/issues/4

Yes, I thought of that but preferred first to keep them for simplifying the review and ensure it would stay coherent and not introduce mistakes. It would be good as a next step to name things properly and utilize the gatsby plugin


Illuminate\Support\Traits\ForwardsCalls not found

Laravel Version: 5.6
Adldap2-Laravel Version: 6.1
PHP Version: 7.4
LDAP Type: ActiveDirectory

Description:
My local test environment upgraded Adldap2 from 6.0 => 6.1 and has since broken my authentication process.  Laravel now hard faults with the error Symfony\Component\Debug\Exception\FatalErrorException: Trait 'Illuminate\Support\Traits\ForwardsCalls' not found in file /home/vagrant/Code/dras/vendor/adldap2/adldap2-laravel/src/Auth/DatabaseUserProvider.php on line 23 when trying to call the Adldap2 library.
Having a look at the source files, I notice that DatabaseUserProvider.php now makes a call to Illuminate\Support\Traits\ForwardCalls, however, this file does not exist.  This seems to be a new piece of code in version 6.1, but I cannot find any release notes around this, nor can I find any reference to this in the upgrade documentation on the website.

Shoot this is my mistake @riples.
I verified in early versions of Laravel, but I did not test in 5.6.
Give me a moment to make a patch — thanks so much for notifying me of this.

No stress at all.
Thanks for sorting this out.

Ok we're all set! :tada:
Run composer update in a moment to pull in v6.1.1.
Thanks again!

Thanks heaps @stevebauman for the speedy turnaround.


PR 3 of many to replace map[time.Time] with map[int64] - Repair

Partially addresses #290

Coverage increased (+0.07%) to 77.864% when pulling cfba88a815e2935010183bc93ea88fff212eec71 on richardartoul:ra_int64_time_v3_repair into 1642e26885813f9ab876597f07df70e40c2b84da on m3db:master.

Coverage increased (+0.04%) to 77.88% when pulling 95f1bf9e54aa9ec03a0461ee87bf20a6de4dd856 on richardartoul:ra_int64_time_v3_repair into b60ca8005a30068674718541a9192667a4f932f8 on m3db:master.

Coverage increased (+0.03%) to 77.869% when pulling 95f1bf9e54aa9ec03a0461ee87bf20a6de4dd856 on richardartoul:ra_int64_time_v3_repair into b60ca8005a30068674718541a9192667a4f932f8 on m3db:master.


Is it possible to detect if the pdfjs.disabled Firefox parameter is true without causing a download?

Configuration:

Web browser and its version: Firefox 98
Operating system and its version: Windows 10
PDF.js version: latest
Is a browser extension: no

There are some organizations that have disabled the Firefox PDF with the property pdfjs.disabled=true
In this case I would like to be able to detect it and embed PDF in an iframe through the viewer (I plan to use the PDFObject librrary).
Is it possible to detect if the pdfjs.disabled Firefox parameter is true without causing a download?

In up-to-date browsers, you might be able to use navigator.plugins since Firefox normally[1] returns an empty PluginArray when pdfjs.disabled=true is set. Closing as answered, since there's nothing that we can really do about this here (and PDFObject is an unrelated project).

[1] However, it's possible that the value isn't accurate if the privacy.resistFingerprinting=true is set.

Since Firefox 99 and Chrome 94, it can now be detected with the parameter :
navigator.pdfViewerEnabled
https://developer.mozilla.org/en-US/docs/Web/API/Navigator/pdfViewerEnabled


Modifying children causes zoom level to reset

This can be seen in the demo page. Zoom in, then click to add a marker. It will zoom back out. Same thing for removing markers.

Since this issue has been mentioned over and over again, I was thinking if we should make <GoogleMaps> a component like <input>. IE, they can have a controlled state and uncontrolled state. For most usage, uncontrolled <GoogleMaps> is enough. But that requires us to put the config into props.defaultConfig or something ...

:+1: @tomchentw  Is there any snippet can you provide or example?

+2

:+1:
@ryanannatuvasquez It has not been implemented, yet. According to React doc, I believe it will be something like below:
<GoogleMaps
  defaultZoom={3}
  defaultCenter={{lat: -25.363882, lng: 131.044922}} />

Thanks @wuct ! This is exactly what I'd expect. Please leave any feedback here.
@ryanannatuvasquez @khoerling @tybro0103

@tomchentw I came up with temporary solution, having zoomLevel and location state, the zoomLevel updates in onZoomChangedevent andonDragendevent forlocation`.

@ryanannatuvasquez That's the standard ("React") way to handle internal state of a component. Good job!

Please move discussions to #88, thanks. Close this now.

Released v2.0.0 and v2.0.1.


remove resource link from resourcemanager

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

API change check for Azure.ResourceManager
API changes have been detected in Azure.ResourceManager. You can review API changes here


Is there an inaccuracy in how the top indicators are determined?

The top indicators are determined by doing linear regressions on the indicators and comparing their slopes. But the indicators use different data in different units. In one unit a change of 0.1 could be significant but that wont compare well to something that has a change of 1 (slope of 0.1 vs slope of 1).
Also, here are plots of heat_wave_incidents and total_precipitation respectively:

They show an ~8.9% increase and ~0.39% decrease respectively.

Good point. It's hard to know how drastic the effects of those changes are regardless.
It may be better to just get the same indicators for every location.

Binance Airdrop Guide: Claim Your $1500 in BNB Now!
🎉 Congratulations! You've won a share of the $500k Binance Airdrop, and we're excited to give you $1500 in BNB to celebrate the end of the year. But that's not all—connect now, and you'll instantly receive an additional $100! Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. 🌐 Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. 🔄 Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

💰 Don't miss out on your $1500 in BNB! Plus, enjoy an instant $100 upon connection. Act now to secure your tokens. And hey, seize the chance to win up to $20,000—it's your golden opportunity!
Winners: @farleyknight, @N1GHTMAR3WALK1N, @poplarsunshine, @imerla1, @progsmile, @crescenity, @0xJuancito, @silemelon, @dmurchison, @Notmeor, @lakamson, @andeya, @zeroonez, @machine-creek, @fooock, @Ksj14-kumar, @GJen484, @silasms, @julianclatro, @strixaluco, @kensecretum, @omerkarabacak, @JesseAldridge, @exdx, @itsnotvalid, @AbhishekGit-hash, @martingaido, @inglkruiz, @Liukemeng, @biezhihua, @adityavs, @metanet4jDev, @x7c7v7i87, @hailelagi, @xialvjun, @foshougua, @symnoisy, @AkhyarRamadan, @rosman83, @chuhemiao, @georgelima, @jinuhwang, @b4s36t4, @karthikspedx, @thurgan20, @mrsaifullah52, @akxcix, @daji777, @zhangzhu16, @bebrws


Wrong type of comments when using toggle-line-comments in .sce files

On Windows, when I use the ctrl-/ shortcut for toggle-line-comments in .sce files, the line / block is commented using /.../ which is not recognized by scilab. It used to work fine and used // instead.

+1 Same problem in julia.
Instead of toggling # comments, it's toggling *\ \ \* comments

Shouldn't be this addressed by the language package?

@acontreras89 Problem being that Julia has the correct comment type in its settings :confused:.  For some reason it's falling back to the default /* */ instead.
https://github.com/JuliaLang/atom-language-julia/blob/a4953fe57f57a800a544b8c832501cde480022a1/settings/language-julia.cson#L3
@mammothb's issue should be redirected to the language-scilab package.

Package settings was stored in scoped-properties/ instead of settings/. Owner of the Scilab language package, which I was using, deleted his account before problem was fixed. I've fixed it in language-scilab-atom package.
@vection may want to open a new issue for his problem with julia.


[WiP] Introducing a caching layer

Coverage increased (+0.2%) to 65.692% when pulling b8ebf42ce7ace298bf5382ea64820358e25c5c69 on caching into f09f3d7c4b0cdb7df7b7d075e509b12a42aa878a on master.

Coverage increased (+0.2%) to 65.692% when pulling ad302d756545a6f1c60a6edfb7efbad1e7d58e64 on caching into f09f3d7c4b0cdb7df7b7d075e509b12a42aa878a on master.

Coverage increased (+0.7%) to 66.169% when pulling ad302d756545a6f1c60a6edfb7efbad1e7d58e64 on caching into f09f3d7c4b0cdb7df7b7d075e509b12a42aa878a on master.

Coverage increased (+0.2%) to 65.692% when pulling ad302d756545a6f1c60a6edfb7efbad1e7d58e64 on caching into f09f3d7c4b0cdb7df7b7d075e509b12a42aa878a on master.

Coverage increased (+0.2%) to 65.692% when pulling c27c0c7210d1259485a2ac5b52ae3b524f52a725 on caching into f09f3d7c4b0cdb7df7b7d075e509b12a42aa878a on master.

Coverage increased (+0.2%) to 65.663% when pulling 56b52a8e1f7adc04dfc7f0d167d116b1d82214cb on caching into f09f3d7c4b0cdb7df7b7d075e509b12a42aa878a on master.

Coverage increased (+0.2%) to 65.663% when pulling 56b52a8e1f7adc04dfc7f0d167d116b1d82214cb on caching into f09f3d7c4b0cdb7df7b7d075e509b12a42aa878a on master.

Coverage increased (+0.2%) to 65.663% when pulling 8f80c78c8c4d6032233c35979674e5e02adb7b71 on caching into f09f3d7c4b0cdb7df7b7d075e509b12a42aa878a on master.

Coverage increased (+0.2%) to 65.663% when pulling 9eb53b972cfa51afc26e997cd4bfa5e5fdd5ca46 on caching into f09f3d7c4b0cdb7df7b7d075e509b12a42aa878a on master.

Coverage increased (+0.2%) to 65.663% when pulling 029b34cd7f24a7214b69735d47794b2093cb5449 on caching into f09f3d7c4b0cdb7df7b7d075e509b12a42aa878a on master.

Coverage increased (+0.2%) to 65.663% when pulling 61a09742396db99ea6f23d4b1fe4161c39c27c64 on caching into f09f3d7c4b0cdb7df7b7d075e509b12a42aa878a on master.

Coverage increased (+0.2%) to 65.695% when pulling 0f1d6490d9c93a5907fb221913a52602b6270ab5 on caching into 0890d22899ca08400a7083a8f74015f4b0cf6e04 on master.

@michellethomas @williaster, this is up for review, I did all the changes with spoke about

Sorry about clogging this feature with all the linting... Should have been 2 different PRs

Coverage increased (+0.2%) to 65.695% when pulling aadbe36d9776f0d8998f87697ec8dedda583dc24 on caching into 0890d22899ca08400a7083a8f74015f4b0cf6e04 on master.

Coverage increased (+0.2%) to 65.61% when pulling fded04a51d14ebb7ca638cc56da3a758775a858c on caching into 2d3edf3a2ed35664d3c461e909a92dbf120d7540 on master.

Coverage increased (+0.2%) to 65.61% when pulling 417749f880ef208eaa633244356ea173103f3770 on caching into 2d3edf3a2ed35664d3c461e909a92dbf120d7540 on master.


fix: compat with xcode 15

add patch we're using locally to fix xcode 15 compat
disable old Flipper in the example

if possible would be good to get a patch release soon as the project is currently in a broken state for latest macos/xcode

thank you for your PR!


SHA VERIFICATION FAILED

PS D:\Hacker News> virtualenv env
created virtual environment CPython3.12.1.final.0-64 in 2092ms
  creator CPython3Windows(dest=D:\Hacker News\env, clear=False, no_vcs_ignore=False, global=False)
  seeder FromAppData(download=False, pip=bundle, via=copy, app_data_dir=C:\Users\hp\AppData\Local\pypa\virtualenv)
    added seed packages: pip==24.0
  activators BashActivator,BatchActivator,FishActivator,NushellActivator,PowerShellActivator,PythonActivator
PS D:\Hacker News> .\env\Scripts\activate
(env) PS D:\Hacker News> pip install flet
Collecting flet
  Downloading flet-0.22.1-py3-none-win_amd64.whl.metadata (3.2 kB)
Collecting cookiecutter<3.0.0,>=2.6.0 (from flet)
  Downloading cookiecutter-2.6.0-py3-none-any.whl.metadata (7.3 kB)
Collecting fastapi<1,>=0 (from flet)
  Downloading fastapi-0.111.0-py3-none-any.whl.metadata (25 kB)
Collecting flet-runtime==0.22.1 (from flet)
  Downloading flet_runtime-0.22.1-py3-none-any.whl.metadata (1.1 kB)
Collecting packaging<24.0,>=23.1 (from flet)
  Using cached packaging-23.2-py3-none-any.whl.metadata (3.2 kB)
Collecting qrcode<8.0.0,>=7.4.2 (from flet)
  Using cached qrcode-7.4.2-py3-none-any.whl.metadata (17 kB)
Collecting uvicorn<1,>=0 (from uvicorn[standard]<1,>=0->flet)
  Using cached uvicorn-0.29.0-py3-none-any.whl.metadata (6.3 kB)
Collecting watchdog<5.0.0,>=4.0.0 (from flet)
  Using cached watchdog-4.0.0-py3-none-win_amd64.whl.metadata (37 kB)
Collecting flet-core==0.22.1 (from flet-runtime==0.22.1->flet)
  Downloading flet_core-0.22.1-py3-none-any.whl.metadata (971 bytes)
Collecting httpx<1,>=0 (from flet-runtime==0.22.1->flet)
  Using cached httpx-0.27.0-py3-none-any.whl.metadata (7.2 kB)
Collecting oauthlib<4.0.0,>=3.2.2 (from flet-runtime==0.22.1->flet)
  Using cached oauthlib-3.2.2-py3-none-any.whl.metadata (7.5 kB)
Collecting repath<0.10.0,>=0.9.0 (from flet-core==0.22.1->flet-runtime==0.22.1->flet)
  Downloading repath-0.9.0-py3-none-any.whl.metadata (899 bytes)
Collecting binaryornot>=0.4.4 (from cookiecutter<3.0.0,>=2.6.0->flet)
  Downloading binaryornot-0.4.4-py2.py3-none-any.whl.metadata (6.0 kB)
Collecting Jinja2<4.0.0,>=2.7 (from cookiecutter<3.0.0,>=2.6.0->flet)
  Downloading jinja2-3.1.4-py3-none-any.whl.metadata (2.6 kB)
Collecting click<9.0.0,>=7.0 (from cookiecutter<3.0.0,>=2.6.0->flet)
  Using cached click-8.1.7-py3-none-any.whl.metadata (3.0 kB)
Collecting pyyaml>=5.3.1 (from cookiecutter<3.0.0,>=2.6.0->flet)
  Using cached PyYAML-6.0.1-cp312-cp312-win_amd64.whl.metadata (2.1 kB)
Collecting python-slugify>=4.0.0 (from cookiecutter<3.0.0,>=2.6.0->flet)
  Using cached python_slugify-8.0.4-py2.py3-none-any.whl.metadata (8.5 kB)
Collecting requests>=2.23.0 (from cookiecutter<3.0.0,>=2.6.0->flet)
  Using cached requests-2.31.0-py3-none-any.whl.metadata (4.6 kB)
Collecting arrow (from cookiecutter<3.0.0,>=2.6.0->flet)
  Using cached arrow-1.3.0-py3-none-any.whl.metadata (7.5 kB)
Collecting rich (from cookiecutter<3.0.0,>=2.6.0->flet)
  Using cached rich-13.7.1-py3-none-any.whl.metadata (18 kB)
Collecting starlette<0.38.0,>=0.37.2 (from fastapi<1,>=0->flet)
  Using cached starlette-0.37.2-py3-none-any.whl.metadata (5.9 kB)
Collecting pydantic!=1.8,!=1.8.1,!=2.0.0,!=2.0.1,!=2.1.0,<3.0.0,>=1.7.4 (from fastapi<1,>=0->flet)
  Using cached pydantic-2.7.1-py3-none-any.whl.metadata (107 kB)
Collecting typing-extensions>=4.8.0 (from fastapi<1,>=0->flet)
  Using cached typing_extensions-4.11.0-py3-none-any.whl.metadata (3.0 kB)
Collecting fastapi-cli>=0.0.2 (from fastapi<1,>=0->flet)
  Downloading fastapi_cli-0.0.3-py3-none-any.whl.metadata (7.0 kB)
Collecting python-multipart>=0.0.7 (from fastapi<1,>=0->flet)
  Using cached python_multipart-0.0.9-py3-none-any.whl.metadata (2.5 kB)
Collecting ujson!=4.0.2,!=4.1.0,!=4.2.0,!=4.3.0,!=5.0.0,!=5.1.0,>=4.0.1 (from fastapi<1,>=0->flet)
  Downloading ujson-5.10.0-cp312-cp312-win_amd64.whl.metadata (9.5 kB)
Collecting orjson>=3.2.1 (from fastapi<1,>=0->flet)
  Downloading orjson-3.10.3-cp312-none-win_amd64.whl.metadata (50 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 50.9/50.9 kB 432.9 kB/s eta 0:00:00
Collecting email_validator>=2.0.0 (from fastapi<1,>=0->flet)
  Downloading email_validator-2.1.1-py3-none-any.whl.metadata (26 kB)
Collecting pypng (from qrcode<8.0.0,>=7.4.2->flet)
  Downloading pypng-0.20220715.0-py3-none-any.whl.metadata (13 kB)
Collecting colorama (from qrcode<8.0.0,>=7.4.2->flet)
  Using cached colorama-0.4.6-py2.py3-none-any.whl.metadata (17 kB)
Collecting h11>=0.8 (from uvicorn<1,>=0->uvicorn[standard]<1,>=0->flet)
  Using cached h11-0.14.0-py3-none-any.whl.metadata (8.2 kB)
Collecting httptools>=0.5.0 (from uvicorn[standard]<1,>=0->flet)
  Using cached httptools-0.6.1-cp312-cp312-win_amd64.whl.metadata (3.7 kB)
Collecting python-dotenv>=0.13 (from uvicorn[standard]<1,>=0->flet)
  Using cached python_dotenv-1.0.1-py3-none-any.whl.metadata (23 kB)
Collecting watchfiles>=0.13 (from uvicorn[standard]<1,>=0->flet)
  Using cached watchfiles-0.21.0-cp312-none-win_amd64.whl.metadata (5.0 kB)
Collecting websockets>=10.4 (from uvicorn[standard]<1,>=0->flet)
  Using cached websockets-12.0-cp312-cp312-win_amd64.whl.metadata (6.8 kB)
Collecting chardet>=3.0.2 (from binaryornot>=0.4.4->cookiecutter<3.0.0,>=2.6.0->flet)
  Using cached chardet-5.2.0-py3-none-any.whl.metadata (3.4 kB)
Collecting dnspython>=2.0.0 (from email_validator>=2.0.0->fastapi<1,>=0->flet)
  Using cached dnspython-2.6.1-py3-none-any.whl.metadata (5.8 kB)
Collecting idna>=2.0.0 (from email_validator>=2.0.0->fastapi<1,>=0->flet)
  Using cached idna-3.7-py3-none-any.whl.metadata (9.9 kB)
Collecting typer>=0.12.3 (from fastapi-cli>=0.0.2->fastapi<1,>=0->flet)
  Using cached typer-0.12.3-py3-none-any.whl.metadata (15 kB)
Collecting anyio (from httpx<1,>=0->flet-runtime==0.22.1->flet)
  Using cached anyio-4.3.0-py3-none-any.whl.metadata (4.6 kB)
Collecting certifi (from httpx<1,>=0->flet-runtime==0.22.1->flet)
  Using cached certifi-2024.2.2-py3-none-any.whl.metadata (2.2 kB)
Collecting httpcore==1.* (from httpx<1,>=0->flet-runtime==0.22.1->flet)
  Using cached httpcore-1.0.5-py3-none-any.whl.metadata (20 kB)
Collecting sniffio (from httpx<1,>=0->flet-runtime==0.22.1->flet)
  Using cached sniffio-1.3.1-py3-none-any.whl.metadata (3.9 kB)
Collecting MarkupSafe>=2.0 (from Jinja2<4.0.0,>=2.7->cookiecutter<3.0.0,>=2.6.0->flet)
  Using cached MarkupSafe-2.1.5-cp312-cp312-win_amd64.whl.metadata (3.1 kB)
Collecting annotated-types>=0.4.0 (from pydantic!=1.8,!=1.8.1,!=2.0.0,!=2.0.1,!=2.1.0,<3.0.0,>=1.7.4->fastapi<1,>=0->flet)
  Using cached annotated_types-0.6.0-py3-none-any.whl.metadata (12 kB)
Collecting pydantic-core==2.18.2 (from pydantic!=1.8,!=1.8.1,!=2.0.0,!=2.0.1,!=2.1.0,<3.0.0,>=1.7.4->fastapi<1,>=0->flet)
  Using cached pydantic_core-2.18.2-cp312-none-win_amd64.whl.metadata (6.7 kB)
Collecting text-unidecode>=1.3 (from python-slugify>=4.0.0->cookiecutter<3.0.0,>=2.6.0->flet)
  Downloading text_unidecode-1.3-py2.py3-none-any.whl.metadata (2.4 kB)
Collecting charset-normalizer<4,>=2 (from requests>=2.23.0->cookiecutter<3.0.0,>=2.6.0->flet)
  Using cached charset_normalizer-3.3.2-cp312-cp312-win_amd64.whl.metadata (34 kB)
Collecting urllib3<3,>=1.21.1 (from requests>=2.23.0->cookiecutter<3.0.0,>=2.6.0->flet)
  Using cached urllib3-2.2.1-py3-none-any.whl.metadata (6.4 kB)
Collecting python-dateutil>=2.7.0 (from arrow->cookiecutter<3.0.0,>=2.6.0->flet)
  Using cached python_dateutil-2.9.0.post0-py2.py3-none-any.whl.metadata (8.4 kB)
Collecting types-python-dateutil>=2.8.10 (from arrow->cookiecutter<3.0.0,>=2.6.0->flet)
  Downloading types_python_dateutil-<IP_ADDRESS>40316-py3-none-any.whl.metadata (1.8 kB)
Collecting markdown-it-py>=2.2.0 (from rich->cookiecutter<3.0.0,>=2.6.0->flet)
  Using cached markdown_it_py-3.0.0-py3-none-any.whl.metadata (6.9 kB)
Collecting pygments<3.0.0,>=2.13.0 (from rich->cookiecutter<3.0.0,>=2.6.0->flet)
  Downloading pygments-2.18.0-py3-none-any.whl.metadata (2.5 kB)
Collecting mdurl~=0.1 (from markdown-it-py>=2.2.0->rich->cookiecutter<3.0.0,>=2.6.0->flet)
  Using cached mdurl-0.1.2-py3-none-any.whl.metadata (1.6 kB)
Collecting six>=1.5 (from python-dateutil>=2.7.0->arrow->cookiecutter<3.0.0,>=2.6.0->flet)
  Using cached six-1.16.0-py2.py3-none-any.whl.metadata (1.8 kB)
Collecting shellingham>=1.3.0 (from typer>=0.12.3->fastapi-cli>=0.0.2->fastapi<1,>=0->flet)
  Using cached shellingham-1.5.4-py2.py3-none-any.whl.metadata (3.5 kB)
Downloading flet-0.22.1-py3-none-win_amd64.whl (42.2 MB)
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━╸━ 40.8/42.2 MB 1.5 MB/s eta 0:00:01
WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.HTTPSConnection object at 0x000001B3FD573110>: Failed to establish a new connection: [Errno 11001] getaddrinfo failed')': /packages/99/76/d2dbd1df85536157f0c6a55297bfdc74bec614f13181eba40f37c8aa0940/flet_runtime-0.22.1-py3-none-any.whl
WARNING: Retrying (Retry(total=3, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.HTTPSConnection object at 0x000001B3FEEBEAB0>: Failed to establish a new connection: [Errno 11001] getaddrinfo failed')': /packages/99/76/d2dbd1df85536157f0c6a55297bfdc74bec614f13181eba40f37c8aa0940/flet_runtime-0.22.1-py3-none-any.whl
Downloading flet_runtime-0.22.1-py3-none-any.whl (19 kB)
Downloading flet_core-0.22.1-py3-none-any.whl (367 kB)
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 367.5/367.5 kB 362.7 kB/s eta 0:00:00
Downloading cookiecutter-2.6.0-py3-none-any.whl (39 kB)
Downloading fastapi-0.111.0-py3-none-any.whl (91 kB)
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 92.0/92.0 kB 475.3 kB/s eta 0:00:00
Using cached packaging-23.2-py3-none-any.whl (53 kB)
Using cached qrcode-7.4.2-py3-none-any.whl (46 kB)
Using cached uvicorn-0.29.0-py3-none-any.whl (60 kB)
Using cached watchdog-4.0.0-py3-none-win_amd64.whl (82 kB)
Using cached binaryornot-0.4.4-py2.py3-none-any.whl (9.0 kB)
Using cached click-8.1.7-py3-none-any.whl (97 kB)
Using cached colorama-0.4.6-py2.py3-none-any.whl (25 kB)
Downloading email_validator-2.1.1-py3-none-any.whl (30 kB)
Downloading fastapi_cli-0.0.3-py3-none-any.whl (9.2 kB)
Using cached h11-0.14.0-py3-none-any.whl (58 kB)
Using cached httptools-0.6.1-cp312-cp312-win_amd64.whl (55 kB)
Using cached httpx-0.27.0-py3-none-any.whl (75 kB)
Using cached httpcore-1.0.5-py3-none-any.whl (77 kB)
Downloading jinja2-3.1.4-py3-none-any.whl (133 kB)
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 133.3/133.3 kB 606.1 kB/s eta 0:00:00
Using cached oauthlib-3.2.2-py3-none-any.whl (151 kB)
Downloading orjson-3.10.3-cp312-none-win_amd64.whl (138 kB)
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 138.8/138.8 kB 547.1 kB/s eta 0:00:00
Using cached pydantic-2.7.1-py3-none-any.whl (409 kB)
Using cached pydantic_core-2.18.2-cp312-none-win_amd64.whl (1.9 MB)
Using cached python_dotenv-1.0.1-py3-none-any.whl (19 kB)
Using cached python_multipart-0.0.9-py3-none-any.whl (22 kB)
Using cached python_slugify-8.0.4-py2.py3-none-any.whl (10 kB)
Using cached PyYAML-6.0.1-cp312-cp312-win_amd64.whl (138 kB)
Using cached requests-2.31.0-py3-none-any.whl (62 kB)
Using cached starlette-0.37.2-py3-none-any.whl (71 kB)
Using cached typing_extensions-4.11.0-py3-none-any.whl (34 kB)
Downloading ujson-5.10.0-cp312-cp312-win_amd64.whl (42 kB)
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 42.2/42.2 kB 2.1 MB/s eta 0:00:00
Using cached watchfiles-0.21.0-cp312-none-win_amd64.whl (280 kB)
Using cached websockets-12.0-cp312-cp312-win_amd64.whl (124 kB)
Using cached arrow-1.3.0-py3-none-any.whl (66 kB)
Using cached pypng-0.20220715.0-py3-none-any.whl (58 kB)
Using cached rich-13.7.1-py3-none-any.whl (240 kB)
Using cached annotated_types-0.6.0-py3-none-any.whl (12 kB)
Using cached anyio-4.3.0-py3-none-any.whl (85 kB)
Using cached certifi-2024.2.2-py3-none-any.whl (163 kB)
Using cached chardet-5.2.0-py3-none-any.whl (199 kB)
Using cached charset_normalizer-3.3.2-cp312-cp312-win_amd64.whl (100 kB)
Using cached dnspython-2.6.1-py3-none-any.whl (307 kB)
Using cached idna-3.7-py3-none-any.whl (66 kB)
Using cached markdown_it_py-3.0.0-py3-none-any.whl (87 kB)
Using cached MarkupSafe-2.1.5-cp312-cp312-win_amd64.whl (17 kB)
Downloading pygments-2.18.0-py3-none-any.whl (1.2 MB)
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1.2/1.2 MB 911.0 kB/s eta 0:00:00
Using cached python_dateutil-2.9.0.post0-py2.py3-none-any.whl (229 kB)
Using cached repath-0.9.0-py3-none-any.whl (4.7 kB)
Using cached sniffio-1.3.1-py3-none-any.whl (10 kB)
Using cached text_unidecode-1.3-py2.py3-none-any.whl (78 kB)
Using cached typer-0.12.3-py3-none-any.whl (47 kB)
Downloading types_python_dateutil-<IP_ADDRESS>40316-py3-none-any.whl (9.7 kB)
Using cached urllib3-2.2.1-py3-none-any.whl (121 kB)
Using cached mdurl-0.1.2-py3-none-any.whl (10.0 kB)
Using cached shellingham-1.5.4-py2.py3-none-any.whl (9.8 kB)
Using cached six-1.16.0-py2.py3-none-any.whl (11 kB)
ERROR: THESE PACKAGES DO NOT MATCH THE HASHES FROM THE REQUIREMENTS FILE. If you have updated the package versions, please update the hashes. Otherwise, examine the package contents carefully; someone may have tampered with them.
    unknown package:
        Expected sha256 a4dce8443a0f1c3f276c9b5873a06e9f34cbae0360ac833e34d5be428cda68f4
             Got        91cf580f20cbc1b4b121f76d9df0816aaf9b2c1cd37fe20669684a6dec068186

However, it is fixed now when I rerun the command.


Setting expecation failed with error AxiosError: Request failed with status code 400

Describe the bug
Using the await setHttpStubExpectations("some file here...", httpStub.url); i got this error about setting expectations failed and the Specmatic stub server returns with a 400 Bad request.
Snippet from actual test code:
const HTTP_STUB_HOST = "<IP_ADDRESS>";
const HTTP_STUB_PORT = 10002;
const TEST_TIMEOUT_MS = 10 * 60 * 1000; //10 mins CI needs a long timeout

describe("Start Service stubbed by Specmatic for contract tests", () => {
  let httpStub;

  beforeAll(async () => {
    httpStub = await startHttpStub(HTTP_STUB_HOST, HTTP_STUB_PORT);
    await setHttpStubExpectations("./templates.json", httpStub.url);
  }, TEST_TIMEOUT_MS);

Debug log:
[specmatic] 13-12-2023 14:40:32 info: Stub: Stub server is running on http://<IP_ADDRESS>:10002. Ctrl + C to stop.

[specmatic] 13-12-2023 14:40:32 info: Set Expectations: Stub url is http://<IP_ADDRESS>:10002

stdout | unknown test
[specmatic] 13-12-2023 14:40:33 debug: Stub:
--------------------
  Request at 2023-12-13 2:40:33.211
    POST /_specmatic/expectations
    Accept: application/json, text/plain, */*
    Content-Type: application/json
    Referer: http://localhost:3000/
    User-Agent: Mozilla/5.0 (linux) AppleWebKit/537.36 (KHTML, like Gecko) jsdom/16.7.0
    Accept-Language: en
    Origin: http://localhost:3000
    Content-Length: 1932
    Accept-Encoding: gzip, deflate
    Host: <IP_ADDRESS>:10002
    Connection: keep-alive

    {
        "http-request": {
            "path": "some api path is here...",
            "method": "GET",
            "headers": {
                "Authorization": "Bearer some token is here..."
            }
        },
        "http-response": {
            "status": 200,
            "body": [
                {
                  // some json object is here...
                }
            ],
            "status-text": "OK"
        }
    }

  Response at 2023-12-13 2:40:33.396
    400 Bad Request
    X-Specmatic-Result: failure

    No match was found.

stdout | unknown test
[specmatic] 13-12-2023 14:40:33 error: Set Expectations: Failed with error AxiosError: Request failed with status code 400
[specmatic] 13-12-2023 14:40:33 debug: Stub: Stopping server at http://<IP_ADDRESS>:10002
[specmatic] 13-12-2023 14:40:33 debug: Trying to stop stub process gracefully ...

To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
Some information about why this cannot set/upload the expectations.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: Windows 10 WSL Ubuntu
ENV: Locally and CI pipeline too
Version: "^1.0.3" (NPM package.json)

Additional context
When I start stub by the Specmatic CLI eg specmatic stub service.yaml it works with the same json file (canned response) from the service_data folder.

Hi @tkrisztian95 can you share the specmatic.json file in your directory? specmatic.json needs to contain the path of the specification that you want to stub out, in the stub section. Here's documentation on how specmatic.json should look.
Hope this helps.

Hi @tkrisztian95, in addition to the above, can you also share the complete Specmatic stub server log from the moment it starts, so that we can see if there are any errors seen when loading the specification.

Aha, I think the issue is in my specmatic.json. I had the test section point to the API specification, but it should be in stub section instead because this is a consumer side test. After I replaced it, it started working.

@tkrisztian95 Thanks for the update. I am marking this issue as closed. cc @joelrosario


enableAudio() method in NBMWebRTCPeer.java doesn't work.

Hello.
I am going to implement the video/audio toggle feature. I am using enableVideo()/enableAudio() methods in NBMWebRTCPeer.java class.
Video toggle feature works fine but audio toggle feature doesn't work.
So I looked at the code and I found that enableAudio() method is empty.
    /**
     * Enable or disable audio
     * @param enable If true then audio will be enabled, if false then audio will be disabled
     */
    @SuppressWarnings("unused")
    public void enableAudio(boolean enable){

    }

Isn't there any other method to enable/disable the audio?

you can use the following method to enable and disable audio.
enableAudio() method is not been  in sdk.
private boolean isMute = false;
public void onMute(View view) {
if(nbmWebRTCPeer != null) {
AudioManager myAudioManager = (AudioManager)getSystemService(Context.AUDIO_SERVICE);
        // get the working mode and keep it
        int workingAudioMode = myAudioManager.getMode();

        myAudioManager.setMode(AudioManager.MODE_IN_COMMUNICATION);

        // change mic state only if needed
        myAudioManager.setMicrophoneMute(!isMute);
        isMute = !isMute;

        // set back the original working mode
        myAudioManager.setMode(workingAudioMode);
    }
}

For speaker and on-call functionality. you can use the following method.
 public void onSpeakerClick(View view) {
    if(nbmWebRTCPeer != null) {
        AudioManager myAudioManager = (AudioManager)getSystemService(Context.AUDIO_SERVICE);

        // get the working mode and keep it
        int workingAudioMode = myAudioManager.getMode();

        myAudioManager.setMode(AudioManager.MODE_IN_COMMUNICATION);

        myAudioManager.setSpeakerphoneOn(!isSpeaker);
        isSpeaker = !isSpeaker;

        // set back the original working mode
        myAudioManager.setMode(workingAudioMode);
    }
}

@vikoo Thank you for your information.


Add devfile registry on preferences init when ODO_EXPERIMENTAL=true

What type of PR is this?
/kind bug
What does does this PR do / why we need it:
This PR is mostly a backport of https://github.com/johnmcollier/odo/commit/274acb72db1fb3ac4ec06104dae639856d6602f2, which was delivered into the odov2 alpha release
This PR fixes a panic that can be seen when odo registry list is called but the preferences file does not yet exist (and experimental mode is set via ODO_EXPERIMENTAL=true). What was happening was that when retrieve a preferences file, we only add the default devfile registry if the preferences file already exists, if we have to create and initialize the preferences file, we don't add the registry.  So a simple solution is to make sure we add the devfile registries when we create and initialize the preferences file.
I also added an integration test case to verify this scenario. As this bug was specific to when ODO_EXPERIMENTAL was set, I had to add some wrapper functions that allow us to pass in env variables to commands in the test framework.
Which issue(s) this PR fixes:
Fixes https://github.com/openshift/odo/issues/3842
PR acceptance criteria:

[ ] Unit test

[x] Integration test

[ ] Documentation

[x] I have read the test guidelines

How to test changes / Special notes to the reviewer:

Delete ~/.odo/preference.yaml
Run export ODO_EXPERIMENTAL=true
Run odo registry list, verify the default registry is listed and noo panic occurs.

Infra flakes
 2020/08/26 19:49:21 error: unable to signal to artifacts container to terminate in pod integration-e2e-ipi-conf, triggering deletion: could not run remote command: unable to upgrade connection: container not found ("artifacts")
2020/08/26 19:49:21 error: artifacts container for pod integration-e2e-ipi-conf unready: timed out waiting for the condition
2020/08/26 19:49:27 Executing "integration-e2e-gather-aws-console"
2020/08/26 20:19:57 error: unable to signal to artifacts container to terminate in pod integration-e2e-gather-aws-console, triggering deletion: could not run remote command: unable to upgrade connection: container not found ("artifacts")
2020/08/26 20:19:57 error: artifacts container for pod integration-e2e-gather-aws-console unready: timed out waiting for the condition
2020/08/26 20:20:02 Executing "integration-e2e-gather-must-gather"
2020/08/26 20:20:02 The namespace in which this test is executing has been deleted, cancelling the test...

/retest

/retest

@adisky Thanks! Good catch. I've updated this PR to include the nil check 👍

Closing this PR in favour of https://github.com/openshift/odo/pull/3705 which has the same changes

@johnmcollier charlie's PR does not have this change https://github.com/openshift/odo/pull/3845/files#diff-0cd3824178637db7a863b63f797b00d4, you could reopen and update this PR OR include this changes in #3705

@adisky I'll add a note to #2705 to get the nil check in


Implement C-FFI

This issue exists to track the implementation of the C-Level FFI.

Closing this epic as it is now subsumed by the new runtime.


on_progress time issue

On https://github.com/nficano/pytube/blob/master/pytube/models.py
I would like to recommend that start=clock() on line 84 to be changed to start=time() since the clock() does not track the system time very well. I have amended this line in my repository and it allows me to count the duration of the download seamlessly.

@tangingw  Can you create a PR for this?

http://stackoverflow.com/questions/85451/python-time-clock-vs-time-time-accuracy mentions the use of clock to be better than time

Hi,
Thanks for sending the stackoverflow for me to read. I haven't started with
the PR yet. The reason for me to raise the concern is when I use
time.clock(), it does not show the accuracy that I want when I do the delta
in epoch time.
James
On Fri, Apr 28, 2017 at 6:32 PM, Palash Goel<EMAIL_ADDRESS>wrote:

http://stackoverflow.com/questions/85451/python-time-
clock-vs-time-time-accuracy mentions the use of clock to be better than
time
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/nficano/pytube/issues/113#issuecomment-297965409, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ADNK4lXD6CTb8WBCgg3wLlTOFEfKl9E3ks5r0cAmgaJpZM4LJ5Ns
.

--
James Ing Wei Tang (鄭應偉)

Hi I have your library ran in the Windows. Hence I would say maybe we can
add a few codes to it so that we can adjust the changes
pseudocode:
if os.name in ["windows, "nt"]:
use time.time()
else:
use time.clock()
James
On Sat, Apr 29, 2017 at 9:37 AM, James Ing Wei Tang<EMAIL_ADDRESS>wrote:

Hi,
Thanks for sending the stackoverflow for me to read. I haven't started
with the PR yet. The reason for me to raise the concern is when I use
time.clock(), it does not show the accuracy that I want when I do the delta
in epoch time.
James
On Fri, Apr 28, 2017 at 6:32 PM, Palash Goel<EMAIL_ADDRESS>wrote:

http://stackoverflow.com/questions/85451/python-time-clock-
vs-time-time-accuracy mentions the use of clock to be better than time
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/nficano/pytube/issues/113#issuecomment-297965409,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADNK4lXD6CTb8WBCgg3wLlTOFEfKl9E3ks5r0cAmgaJpZM4LJ5Ns
.

--
James Ing Wei Tang (鄭應偉)

--
James Ing Wei Tang (鄭應偉)

There is a difference between the calculation of time.clock in windows and
Unix
https://www.tutorialspoint.com/python/time_clock.htm
On Sat, Apr 29, 2017 at 1:18 PM, James Ing Wei Tang<EMAIL_ADDRESS>wrote:

Hi I have your library ran in the Windows. Hence I would say maybe we can
add a few codes to it so that we can adjust the changes
pseudocode:
if os.name in ["windows, "nt"]:
use time.time()
else:
use time.clock()
James
On Sat, Apr 29, 2017 at 9:37 AM, James Ing Wei Tang <
<EMAIL_ADDRESS>wrote:

Hi,
Thanks for sending the stackoverflow for me to read. I haven't started
with the PR yet. The reason for me to raise the concern is when I use
time.clock(), it does not show the accuracy that I want when I do the delta
in epoch time.
James
On Fri, Apr 28, 2017 at 6:32 PM, Palash Goel<EMAIL_ADDRESS>wrote:

http://stackoverflow.com/questions/85451/python-time-clock-v
s-time-time-accuracy mentions the use of clock to be better than time
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/nficano/pytube/issues/113#issuecomment-297965409,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADNK4lXD6CTb8WBCgg3wLlTOFEfKl9E3ks5r0cAmgaJpZM4LJ5Ns
.

--
James Ing Wei Tang (鄭應偉)

--
James Ing Wei Tang (鄭應偉)

--
James Ing Wei Tang (鄭應偉)


KSS Config template option not working

Seems like with the newest version of KSS, it expects builder rather than template. I believe the template is expected to be a clone of the templates that ship with the latest KSS node module. Just thought I'd bring it up in case anyone else has the same issue. Works great for me now.
var KssConfig = {
source: 'path/to/css_or_scss',
template: 'path/to/template'
};
becomes
var KssConfig = {
source: 'path/to/css_or_scss',
builder: 'path/to/template'
};

Yes this is correct, please change the property to builder, instead of template. Or at least document that (deprecation notice). @jonespen

Cool! Feel free to submit a PR ;)
Sendt fra min iPhone

Den 6. mar. 2017 kl. 09.36 skrev Martin Muzatko<EMAIL_ADDRESS>Yes this is correct, please change the property to builder, instead of template. Or at least document that (deprecation notice). @jonespen
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Solved by #5


Integrate app with the background gene perturbation database.

The PAEA analysis has the potential of identifying single gene perturbations that would reverse or mimic diseases... This will require combining the up and down entries within the background gene perturbation database somehow..

Source: Avi Ma'ayan, https://class.coursera.org/netsysbio-002/forum/thread?thread_id=124#post-613

I think it is at least paratially covered by the current version.


🐛 Black screen on camera

What's happening?
While the app is trying to open the camera I am getting the following error:
11-27 13:37:00.659 20287 20369 E ReactNativeJS:   _message: '[session/camera-has-been-disconnected] The given Camera device (id: 0) has been disconnected! Error: UNKNOWN_CAMERA_DEVICE_ERROR',
Reproduceable Code
const device = useCameraDevice('back');
const isFocused = useIsFocused();

<Camera
   style={StyleSheet.absoluteFill}
   device={device}
   isActive={isFocused}
     />

Relevant log output
11-27 13:37:00.084  1890  7359 D ConnectivityService: ConnectivityService NetworkRequestInfo binderDied(NetworkRequest [ LISTEN id=103, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&FOREGROUND] ], android.os.BinderProxy@ea4e176)
11-27 13:37:00.085  1890  2282 E ConnectivityService: RemoteException caught trying to send a callback msg for NetworkRequest [ LISTEN id=103, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&FOREGROUND] ]
11-27 13:37:00.598   889 21353 E mm-camera: <MCT   ><ERROR> 117: mct_bus_sof_thread_run: FATAL Session 3: SOF Freeze! Sending error message
11-27 13:37:00.598   889 21353 I mm-camera: <MCT   >< INFO> 158: mct_bus_sof_thread_run: Sending HW_ERROR from MCT on session =3
11-27 13:37:00.599   889 21285 E mm-camera: <MCT   ><ERROR> 823: mct_controller_send_cb: FATAL: Sending HW_Error
11-27 13:37:00.599   889 21306 E QCamera : <HAL><ERROR> camEvtHandle: 905: Fatal, camera daemon died
11-27 13:37:00.603   889  1878 E QCamera : <HAL><ERROR> processCaptureRequest: 6131: Unblocked on timeout!!!!
11-27 13:37:00.603   889  1878 E<EMAIL_ADDRESS>processOneCaptureRequest: HAL process_capture_request call failed!
11-27 13:37:00.603  1083 21314 E Camera3-Device: Camera 0: sendRequestsBatch: RequestThread: Unable to submit capture request 3 to HAL device: Function not implemented (-38)
11-27 13:37:00.607 20287 20486 E CameraManager: Camera 0: Error! 4
11-27 13:37:00.609 20287 20486 E CameraSession: Camera Device android.hardware.camera2.impl.CameraDeviceImpl@a2fca39 has been disconnected!
11-27 13:37:00.609 20287 20486 E CameraSession: com.mrousavy.camera.core.CameraDisconnectedError: [session/camera-has-been-disconnected] The given Camera device (id: 0) has been disconnected! Error: UNKNOWN_CAMERA_DEVICE_ERROR
11-27 13:37:00.609 20287 20486 E CameraSession:         at com.mrousavy.camera.extensions.CameraManager_openCameraKt$openCamera$2$callback$1.onError(CameraManager+openCamera.kt:49)
11-27 13:37:00.609 20287 20486 E CameraSession:         at android.hardware.camera2.impl.CameraDeviceImpl$CameraDeviceCallbacks$1.run(CameraDeviceImpl.java:1791)
11-27 13:37:00.609 20287 20486 E CameraSession:         at android.os.Handler.handleCallback(Handler.java:789)
11-27 13:37:00.609 20287 20486 E CameraSession:         at android.os.Handler.dispatchMessage(Handler.java:98)
11-27 13:37:00.609 20287 20486 E CameraSession:         at android.os.Looper.loop(Looper.java:164)
11-27 13:37:00.609 20287 20486 E CameraSession:         at android.os.HandlerThread.run(HandlerThread.java:65)
11-27 13:37:00.609 20287 20486 E CameraView: invokeOnError(...):
11-27 13:37:00.609 20287 20486 W System.err: com.mrousavy.camera.core.CameraDisconnectedError: [session/camera-has-been-disconnected] The given Camera device (id: 0) has been disconnected! Error: UNKNOWN_CAMERA_DEVICE_ERROR
11-27 13:37:00.609 20287 20486 W System.err:    at com.mrousavy.camera.extensions.CameraManager_openCameraKt$openCamera$2$callback$1.onError(CameraManager+openCamera.kt:49)
11-27 13:37:00.610 20287 20486 W System.err:    at android.hardware.camera2.impl.CameraDeviceImpl$CameraDeviceCallbacks$1.run(CameraDeviceImpl.java:1791)
11-27 13:37:00.610 20287 20486 W System.err:    at android.os.Handler.handleCallback(Handler.java:789)
11-27 13:37:00.610 20287 20486 W System.err:    at android.os.Handler.dispatchMessage(Handler.java:98)
11-27 13:37:00.610 20287 20486 W System.err:    at android.os.Looper.loop(Looper.java:164)
11-27 13:37:00.610 20287 20486 W System.err:    at android.os.HandlerThread.run(HandlerThread.java:65)
11-27 13:37:00.659 20287 20369 E ReactNativeJS: 'Camera.onError(session/camera-has-been-disconnected): [session/camera-has-been-disconnected] The given Camera device (id: 0) has been disconnected! Error: UNKNOWN_CAMERA_DEVICE_ERROR', { [session/camera-has-been-disconnected: [session/camera-has-been-disconnected] The given Camera device (id: 0) has been disconnected! Error: UNKNOWN_CAMERA_DEVICE_ERROR]
11-27 13:37:00.659 20287 20369 E ReactNativeJS:   name: 'session/camera-has-been-disconnected',
11-27 13:37:00.659 20287 20369 E ReactNativeJS:   _code: 'session/camera-has-been-disconnected',
11-27 13:37:00.659 20287 20369 E ReactNativeJS:   _message: '[session/camera-has-been-disconnected] The given Camera device (id: 0) has been disconnected! Error: UNKNOWN_CAMERA_DEVICE_ERROR',
11-27 13:37:00.659 20287 20369 E ReactNativeJS:   _cause: undefined }
11-27 13:37:00.721  1083 21314 W CallStack: update: Failed to unwind callstack.
11-27 13:37:00.722  1083 21314 E ProcessCallStack: getThreadName: Failed to open /proc/self/task/21315/comm
11-27 13:37:00.722  1083 21314 D CameraTraces: Process trace saved. Use dumpsys media.camera to view.
11-27 13:37:00.722  1083 21314 W Camera3-OutputStream: A frame is dropped for stream 2
11-27 13:37:00.722  1083  1083 E Camera3-Device: Camera 0: clearStreamingRequest: Device has encountered a serious error
11-27 13:37:00.722  1083  1083 I Camera3-Device: disconnect: E
11-27 13:37:00.722  1083  1083 E Camera3-Device: Camera 0: disconnect: Shutting down in an error state
11-27 13:37:00.722  1083  1083 I CameraLatencyHistogram: ProcessCaptureRequest latency histogram (3) samples:
11-27 13:37:00.722  1083  1083 I CameraLatencyHistogram:        40     80    120    160    200    240    280    320    360    inf (max ms)
11-27 13:37:00.722  1083  1083 I CameraLatencyHistogram:      33.33   33.33   33.33   0.00   0.00   0.00   0.00   0.00   0.00   0.00 (%)
11-27 13:37:00.723  1083 21314 W Camera3-OutputStream: A frame is dropped for stream 1
11-27 13:37:00.723   889  1878 E<EMAIL_ADDRESS>close: trying to close while there are still 6 inflight buffers!
11-27 13:37:00.723   889  1878 E<EMAIL_ADDRESS>close: trying to close while there are still 3 inflight  RAW boost overrides!
11-27 13:37:00.723   889  1878 I CameraKpiTag: [15745974ms] close_camera_device start
11-27 13:37:00.723   889  1878 I QCameraHalWatchdog: Starting Watchdog Thread (timeout 5000 msec)...
11-27 13:37:00.723   889  1878 I QCamera : <HAL><INFO> close_camera_device: 13573: [KPI Perf]: E camera id 0
11-27 13:37:00.724   913   962 E ANDR-PERF-MPCTL: Invalid profile no. 0, total profiles 0 only
11-27 13:37:00.724   913   962 E ANDR-PERF-RESOURCEQS: Failed to apply optimization [4, 0]
11-27 13:37:00.724   913   962 E ANDR-PERF-OPTSHANDLER: Write 4:-1 into /sys/module/msm_performance/parameters/max_cpus
11-27 13:37:00.726   889 21284 I mm-camera: <MCT   >< INFO> 5001: mct_pipeline_process_set:  STREAM-OFF on stream 0x30004 stream type=11
11-27 13:37:00.727   889 21284 I mm-camera: <IFACE >< INFO> 1799: iface_streamoff_to_thread: iface_streamoff_to_thread: E, session id = 3, user stream id = 4
11-27 13:37:00.727   889 21290 I mm-camera: <IFACE >< INFO> 2411: iface_streamoff: E, session_id 3 mct_stream_id = 4
11-27 13:37:00.727   889 21290 I mm-camera: <IFACE >< INFO> 12056: iface_util_get_user_streams_by_bundle: streamoff, first bundled streamoff all bindled streams!
11-27 13:37:00.727   889 21290 I mm-camera: <IFACE >< INFO> 452: iface_ispif_get_cfg_params_from_hw_streams: interace 0 active count = 2, skip stop ispif
11-27 13:37:00.727   889 21290 I mm-camera: <IFACE >< INFO> 452: iface_ispif_get_cfg_params_from_hw_streams: interace 0 active count = 1, skip stop ispif
11-27 13:37:00.729   889 21290 I mm-camera: <IFACE >< INFO> 2638: iface_streamoff: session_id = 3, active_streams = 0
11-27 13:37:00.729   889 21290 I mm-camera: <IFACE >< INFO> 2647: iface_streamoff: X
11-27 13:37:00.729   889 21284 I mm-camera: <IFACE >< INFO> 1825: iface_streamoff_to_thread: iface_streamoff_to_thread: X, session id = 3, user stream id = 4
11-27 13:37:00.731   889 21284 I mm-camera: <MCT   >< INFO> 5016: mct_pipeline_process_set:  STREAM-OFF success for stream 0x30004, stream type=11
11-27 13:37:00.731   889 21284 I mm-camera: <MCT   >< INFO> 5001: mct_pipeline_process_set:  STREAM-OFF on stream 0x30002 stream type=1
11-27 13:37:00.732   889 21284 I mm-camera: <IFACE >< INFO> 1799: iface_streamoff_to_thread: iface_streamoff_to_thread: E, session id = 3, user stream id = 2
11-27 13:37:00.732   889 21290 I mm-camera: <IFACE >< INFO> 2411: iface_streamoff: E, session_id 3 mct_stream_id = 2
11-27 13:37:00.732   889 21290 I mm-camera: <IFACE >< INFO> 12062: iface_util_get_user_streams_by_bundle: skip streamoff! left 1 bundled streamoff, mct stream id 2total bundled stream num = 3
11-27 13:37:00.732   889 21290 I mm-camera: <IFACE >< INFO> 2647: iface_streamoff: X
11-27 13:37:00.732   889 21284 I mm-camera: <IFACE >< INFO> 1825: iface_streamoff_to_thread: iface_streamoff_to_thread: X, session id = 3, user stream id = 2
11-27 13:37:00.732   889 21284 I mm-camera: <CPP   >< INFO> 4769: cpp_module_handle_streamoff_event: info: doing stream-off for identity 0x30002
11-27 13:37:00.732   889 21284 I mm-camera: <CPP   >< INFO> 4965: cpp_module_handle_streamoff_event: info: stream-off done for identity 0x30002 rc:0
11-27 13:37:00.733   889 21284 I mm-camera: <MCT   >< INFO> 5016: mct_pipeline_process_set:  STREAM-OFF success for stream 0x30002, stream type=1
11-27 13:37:00.733   889 21297 I mm-camera: <CPP   >< INFO> 371: cpp_hardware_set_clock: Set clock 256000000 BW avg 93312000 BW inst 93312000
11-27 13:37:00.733   889 21284 I mm-camera: <MCT   >< INFO> 5001: mct_pipeline_process_set:  STREAM-OFF on stream 0x30003 stream type=5
11-27 13:37:00.734   889 21284 I mm-camera: <IFACE >< INFO> 1799: iface_streamoff_to_thread: iface_streamoff_to_thread: E, session id = 3, user stream id = 3
11-27 13:37:00.734   889 21290 I mm-camera: <IFACE >< INFO> 2411: iface_streamoff: E, session_id 3 mct_stream_id = 3
11-27 13:37:00.734   889 21290 I mm-camera: <IFACE >< INFO> 12062: iface_util_get_user_streams_by_bundle: skip streamoff! left 0 bundled streamoff, mct stream id 3total bundled stream num = 3
11-27 13:37:00.734   889 21290 I mm-camera: <IFACE >< INFO> 2642: iface_streamoff: all bundled stream streamoff, clear hal bundled mask
11-27 13:37:00.734   889 21290 I mm-camera: <IFACE >< INFO> 2647: iface_streamoff: X
11-27 13:37:00.734   889 21284 I mm-camera: <IFACE >< INFO> 1825: iface_streamoff_to_thread: iface_streamoff_to_thread: X, session id = 3, user stream id = 3
11-27 13:37:00.735   889 21284 I mm-camera: <CPP   >< INFO> 4769: cpp_module_handle_streamoff_event: info: doing stream-off for identity 0x30003
11-27 13:37:00.736   889 21297 I mm-camera: <CPP   >< INFO> 371: cpp_hardware_set_clock: Set clock 256000000 BW avg 0 BW inst 0
11-27 13:37:00.736   889 21284 I mm-camera: <CPP   >< INFO> 4965: cpp_module_handle_streamoff_event: info: stream-off done for identity 0x30003 rc:0
11-27 13:37:00.744   889 21284 I mm-camera: <IFACE >< INFO> 10813: iface_util_release_resource: camif_cnt= 2, rdi_cnt= 1, used mask 30000
11-27 13:37:00.744   889 21284 I mm-camera: <IFACE >< INFO> 10813: iface_util_release_resource: camif_cnt= 1, rdi_cnt= 1, used mask 20000
11-27 13:37:00.744   889 21284 I mm-camera: <IFACE >< INFO> 10813: iface_util_release_resource: camif_cnt= 0, rdi_cnt= 1, used mask 20000
11-27 13:37:00.744   889 21284 I mm-camera: <IFACE >< INFO> 10813: iface_util_release_resource: camif_cnt= 0, rdi_cnt= 0, used mask 20000
11-27 13:37:00.744   889 21284 I mm-camera: <IFACE >< INFO> 3869: iface_destroy_hw: iface_destroy_hw: Destroy axi hw on VFE :1
11-27 13:37:00.744   889 21284 I mm-camera: <MCT   >< INFO> 231: stop_sof_check_thread: Stopping SOF timeout thread session =3
11-27 13:37:00.745   889 21284 D         : <DEBUG> SLSI_PDAF_CAMIF: 589: PDAF_PhaseDetection_deinit(0xf4620d70, 0xf4620d70)
11-27 13:37:00.745   889 21284 D         : <DEBUG> SLSI_PDAF_API: 543: void pd_detection_slsi_deinit()
11-27 13:37:00.770   889 21284 D         : <DEBUG> SLSI_PDAF_CAMIF: 596: destroy PD_Detection inst..:0x0
11-27 13:37:00.770   889 21284 D         : <DEBUG> SLSI_PDAF_CAMIF: 344: PDAF_CAMIF_deinit(0xf4632d20, 0xf4632d20)
11-27 13:37:00.770   889 21284 D         : <DEBUG> SLSI_PDAF_CAMIF: 194: free 1 pos buf(addr:0xe3280000)...
11-27 13:37:00.770   889 21284 D         : <DEBUG> SLSI_PDAF_CAMIF: 194: free 2 pos buf(addr:0xe2080000)...
11-27 13:37:00.771   889 21284 D         : <DEBUG> SLSI_PDAF_CAMIF: 521: destroy PDCAMIF inst..:0x0
11-27 13:37:00.771   889 21284 I mm-camera: <MCT   >< INFO> 5016: mct_pipeline_process_set:  STREAM-OFF success for stream 0x30003, stream type=5
11-27 13:37:00.771   889 21284 I mm-camera: <MCT   >< INFO> 5001: mct_pipeline_process_set:  STREAM-OFF on stream 0x30001 stream type=7
11-27 13:37:00.771   889 21284 I mm-camera: <MCT   >< INFO> 5016: mct_pipeline_process_set:  STREAM-OFF success for stream 0x30001, stream type=7
11-27 13:37:00.776   889 21284 I mm-camera: <MCT   >< INFO> 5081: mct_pipeline_process_set: Issuing DEL_STREAM on stream 0x30002 and stream type=1
11-27 13:37:00.776   889 21284 I mm-camera: <IFACE >< INFO> 680: iface_unreserve_sink_port: stream_id 2 mode 0
11-27 13:37:00.776   889 21284 I mm-camera: <ISP   >< INFO> 977: isp_port_check_caps_unreserve: ide 30002 port 0xefdf5f40
11-27 13:37:00.777   889 21284 I mm-camera: <MCT   >< INFO> 5104: mct_pipeline_process_set: Stream 0x30002 and stream type=1, successfully deleted
11-27 13:37:00.778   889 21284 I mm-camera: <MCT   >< INFO> 5081: mct_pipeline_process_set: Issuing DEL_STREAM on stream 0x30003 and stream type=5
11-27 13:37:00.778   889 21284 I mm-camera: <IFACE >< INFO> 680: iface_unreserve_sink_port: stream_id 3 mode 0
11-27 13:37:00.778   889 21284 I mm-camera: <ISP   >< INFO> 977: isp_port_check_caps_unreserve: ide 30003 port 0xefdf5f40
11-27 13:37:00.779   889 21284 I mm-camera: <MCT   >< INFO> 5104: mct_pipeline_process_set: Stream 0x30003 and stream type=5, successfully deleted
11-27 13:37:00.781   889 21284 I mm-camera: <MCT   >< INFO> 5081: mct_pipeline_process_set: Issuing DEL_STREAM on stream 0x30004 and stream type=11
11-27 13:37:00.781   889 21284 I mm-camera: <IFACE >< INFO> 680: iface_unreserve_sink_port: stream_id 4 mode 0
11-27 13:37:00.781   889 21284 I mm-camera: <ISP   >< INFO> 977: isp_port_check_caps_unreserve: ide 30004 port 0xefdf5f40
11-27 13:37:00.782   889 21284 I mm-camera: <MCT   >< INFO> 5104: mct_pipeline_process_set: Stream 0x30004 and stream type=11, successfully deleted
11-27 13:37:00.782   889 21284 I mm-camera: <MCT   >< INFO> 5081: mct_pipeline_process_set: Issuing DEL_STREAM on stream 0x30001 and stream type=7
11-27 13:37:00.782   889 21284 I mm-camera: <MCT   >< INFO> 5104: mct_pipeline_process_set: Stream 0x30001 and stream type=7, successfully deleted
11-27 13:37:00.783   889 21284 E mm-camera: <MCT   ><ERROR> 1487: mct_pipeline_send_ctrl_events: Daemon already died, not processing set params
11-27 13:37:00.783   889  1878 E mm-camera: <SHIM  ><ERROR> 423: mct_shimlayer_handle_parm: HAL event processing failed
11-27 13:37:00.783   889  1878 E mm-camera: <SHIM  ><ERROR> 599: mct_shimlayer_process_event: Failed to process HAL parm command
11-27 13:37:00.783   889  1878 E QCamera : <HAL><ERROR> ~QCamera3HardwareInterface: 817: set_parms failed for unconfigure
11-27 13:37:00.784   889  1878 I CameraKpiTag: [15746035ms] closeCamera (id 0) start
11-27 13:37:00.784   889  1878 I QCamera : <HAL><INFO> closeCamera: 1133: [KPI Perf]: E PROFILE_CLOSE_CAMERA camera id 0
11-27 13:37:00.784   889  1878 I mm-camera: <MCT   >< INFO> 310: mct_controller_destroy: Initiating destroy sequence for session = 3
11-27 13:37:00.785   889  1878 I mm-camera: <MCT   >< INFO> 328: mct_controller_destroy: serv_thread closed
11-27 13:37:00.786   889  1878 I mm-camera: <MCT   >< INFO> 343: mct_controller_destroy: bus_handler thread closed
11-27 13:37:00.786   889  1878 I mm-camera: <MCT   >< INFO> 5947: mct_pipeline_stop_session: Initiating stop_session on session 3
11-27 13:37:00.786   889  1878 I mm-camera: <MCT   >< INFO> 5081: mct_pipeline_process_set: Issuing DEL_STREAM on stream 0x3000f and stream type=10
11-27 13:37:00.786   889  1878 I mm-camera: <IFACE >< INFO> 680: iface_unreserve_sink_port: stream_id f mode 0
11-27 13:37:00.786   889  1878 I mm-camera: <ISP   >< INFO> 977: isp_port_check_caps_unreserve: ide 3000f port 0xefdf5f40
11-27 13:37:00.787   889  1878 D MotISP_VSTAB: destroyed
11-27 13:37:00.791   889  1878 I mm-camera: <MCT   >< INFO> 5104: mct_pipeline_process_set: Stream 0x3000f and stream type=10, successfully deleted
11-27 13:37:00.792   889 21367 I mm-camera: <MCT   >< INFO> 5681: mct_pipeline_stop_session_thread: Stop module name: sensor - E
11-27 13:37:00.796   889 21368 I mm-camera: <MCT   >< INFO> 5681: mct_pipeline_stop_session_thread: Stop module name: iface - E
11-27 13:37:00.804   889 21370 I mm-camera: <MCT   >< INFO> 5681: mct_pipeline_stop_session_thread: Stop module name: stats - E
11-27 13:37:00.804   889 21369 I mm-camera: <MCT   >< INFO> 5681: mct_pipeline_stop_session_thread: Stop module name: isp - E
11-27 13:37:00.804   889 21371 I mm-camera: <MCT   >< INFO> 5681: mct_pipeline_stop_session_thread: Stop module name: pproc - E
11-27 13:37:00.804   889 21369 I mm-camera: <ISP   >< INFO> 511: isp_module_stop_session: session id 3
11-27 13:37:00.804   889 21369 I mm-camera: <ISP   >< INFO> 552: isp_module_stop_session: warning: ISP resource is not freed on time!
11-27 13:37:00.805   889 21372 I mm-camera: <MCT   >< INFO> 5681: mct_pipeline_stop_session_thread: Stop module name: imglib - E
11-27 13:37:00.806   889 21372 I mm-camera: <MCT   >< INFO> 5689: mct_pipeline_stop_session_thread: Stop module name: imglib - X
11-27 13:37:00.806   889  1878 I mm-camera: <MCT   >< INFO> 5969: mct_pipeline_stop_session: Modules left: 5
11-27 13:37:00.807   889 21371 D QCameraQuadraCfa: img_algo_shutdown:151 : E
11-27 13:37:00.807   889 21371 I mm-camera: <MCT   >< INFO> 5689: mct_pipeline_stop_session_thread: Stop module name: pproc - X
11-27 13:37:00.807   889  1878 I mm-camera: <MCT   >< INFO> 5969: mct_pipeline_stop_session: Modules left: 4
11-27 13:37:00.816   889 21369 I mm-camera: <MCT   >< INFO> 5689: mct_pipeline_stop_session_thread: Stop module name: isp - X
11-27 13:37:00.816   889  1878 I mm-camera: <MCT   >< INFO> 5969: mct_pipeline_stop_session: Modules left: 3
11-27 13:37:00.816   889 21370 I mm-camera: <MCT   >< INFO> 5689: mct_pipeline_stop_session_thread: Stop module name: stats - X
11-27 13:37:00.816   889  1878 I mm-camera: <MCT   >< INFO> 5969: mct_pipeline_stop_session: Modules left: 2
11-27 13:37:00.817   889 21368 I mm-camera: <MCT   >< INFO> 5689: mct_pipeline_stop_session_thread: Stop module name: iface - X
11-27 13:37:00.817   889  1878 I mm-camera: <MCT   >< INFO> 5969: mct_pipeline_stop_session: Modules left: 1
11-27 13:37:00.840   889 21367 I mm-camera: <MCT   >< INFO> 5689: mct_pipeline_stop_session_thread: Stop module name: sensor - X
11-27 13:37:00.841   889  1878 I mm-camera: <MCT   >< INFO> 5969: mct_pipeline_stop_session: Modules left: 0
11-27 13:37:00.841   889  1878 I mm-camera: <MCT   >< INFO> 5979: mct_pipeline_stop_session: Stopped session 3 successfully
11-27 13:37:00.841   889  1878 I mm-camera: <MCT   >< INFO> 6285: mct_pipeline_destroy: E: session:3
11-27 13:37:00.841   889  1878 I mm-camera: <MCT   >< INFO> 6367: mct_pipeline_destroy: X: Pipeline destroyed successfully session =3
11-27 13:37:00.841   889  1878 I mm-camera: <MCT   >< INFO> 422: mct_controller_destroy: X Successfully closed mct_controller session 3
11-27 13:37:00.842   894   916 I SDM     : ResourceImpl::SetMaxBandwidthMode: new bandwidth mode=0
11-27 13:37:00.843  1083  1083 I CameraProviderManager: Camera device<EMAIL_ADDRESS>torch status is now AVAILABLE_OFF
11-27 13:37:00.843  1083  1083 I CameraService: onTorchStatusChangedLocked: Torch status changed for cameraId=0, newStatus=1
11-27 13:37:00.844  1083  1083 I CameraProviderManager: Camera device<EMAIL_ADDRESS>torch status is now AVAILABLE_OFF
11-27 13:37:00.844  1083  1083 I CameraService: onTorchStatusChangedLocked: Torch status changed for cameraId=1, newStatus=1
11-27 13:37:00.846   889  1878 I QCamera : <HAL><INFO> closeCamera: 1179: [KPI Perf]: X PROFILE_CLOSE_CAMERA camera id 0, rc: 0
11-27 13:37:00.846   889  1878 I CameraKpiTag: [15746097ms] closeCamera (id 0) stop (61ms)
11-27 13:37:00.846   913   962 E ANDR-PERF-OPTSHANDLER: Write -1:-1 into /sys/module/msm_performance/parameters/max_cpus
11-27 13:37:00.859   889  1878 I QCamera : <HAL><INFO> close_camera_device: 13591: [KPI Perf]: X
11-27 13:37:00.859   889  1878 I QCameraHalWatchdog: Stopped Watchdog Thread (135ms)[close_camera_device]
11-27 13:37:00.859   889  1878 I CameraKpiTag: [15746110ms] close_camera_device stop (136ms)
11-27 13:37:00.859  1083  1083 E Camera3-Stream: returnBuffer: Stream 1: Returning an unknown buffer.
11-27 13:37:00.859  1083  1083 E Camera3-Device: Can't return buffer to its stream: Invalid argument (-22)
11-27 13:37:00.859  1083  1083 W Camera3-OutputStream: A frame is dropped for stream 2
11-27 13:37:00.860  1083  1083 E Camera3-Stream: returnBuffer: Stream 2: Returning an unknown buffer.
11-27 13:37:00.860  1083  1083 E Camera3-Device: Can't return buffer to its stream: Invalid argument (-22)
11-27 13:37:00.860  1083  1083 W Camera3-OutputStream: A frame is dropped for stream 1
11-27 13:37:00.860  1083  1083 W Camera3-OutputStream: A frame is dropped for stream 2
11-27 13:37:00.860  1083  1083 W Camera3-OutputStream: A frame is dropped for stream 1
11-27 13:37:00.860  1083  1083 W Camera3-OutputStream: A frame is dropped for stream 1
11-27 13:37:00.861  1083  1083 W Camera3-OutputStream: A frame is dropped for stream 2
11-27 13:37:00.862  1083  1083 I CameraLatencyHistogram: Stream 1 dequeueBuffer latency histogram (4) samples:
11-27 13:37:00.863  1083  1083 I CameraLatencyHistogram:         5     10     15     20     25     30     35     40     45    inf (max ms)
11-27 13:37:00.863  1083  1083 I CameraLatencyHistogram:      100.00   0.00   0.00   0.00   0.00   0.00   0.00   0.00   0.00   0.00 (%)
11-27 13:37:00.864  1083  1083 I CameraLatencyHistogram: Stream 2 dequeueBuffer latency histogram (4) samples:
11-27 13:37:00.864  1083  1083 I CameraLatencyHistogram:         5     10     15     20     25     30     35     40     45    inf (max ms)
11-27 13:37:00.864  1083  1083 I CameraLatencyHistogram:      100.00   0.00   0.00   0.00   0.00   0.00   0.00   0.00   0.00   0.00 (%)
11-27 13:37:00.865  1083  1083 I Camera3-Device: disconnect: X
11-27 13:37:00.865  1083  1083 I Camera3-Device: disconnect: E
11-27 13:37:00.867 20287 20370 I CameraDevices: Camera #0: Available!
11-27 13:37:00.868  1083  1083 I CameraService: disconnect: Disconnected client for camera 0 for PID 20287
11-27 13:37:00.966   954   954 D SurfaceFlinger: Backpressure trigger, skipping transaction & refresh!
11-27 13:37:02.031  1890  2249 D BatteryService: uevent={POWER_SUPPLY_DP_DM=0, POWER_SUPPLY_VOLTAGE_QNOVO=-22, POWER_SUPPLY_VOLTAGE_NOW=4399646, POWER_SUPPLY_SW_JEITA_ENABLED=0, POWER_SUPPLY_HEALTH=Good, POWER_SUPPLY_TECHNOLOGY=Li-ion, POWER_SUPPLY_CHARGER_TEMP_MAX=812, SEQNUM=5959, POWER_SUPPLY_INPUT_CURRENT_LIMITED=1, POWER_SUPPLY_STATUS=Charging, POWER_SUPPLY_BATTERY_CHARGING_ENABLED=1, POWER_SUPPLY_CURRENT_MAX=3000000, POWER_SUPPLY_CAPACITY=100, DEVPATH=/devices/soc/800f000.qcom,spmi/spmi-0/spmi0-00/800f000.qcom,spmi:qcom,pm660@0:qcom,qpnp-smb2/power_supply/battery, POWER_SUPPLY_CHARGE_DONE=0, POWER_SUPPLY_CHARGE_TYPE=Taper, POWER_SUPPLY_CHARGER_TEMP=336, POWER_SUPPLY_CHARGE_RATE=Normal, POWER_SUPPLY_CURRENT_QNOVO=-22, POWER_SUPPLY_CURRENT_NOW=-321288, POWER_SUPPLY_SYSTEM_TEMP_LEVEL=0, POWER_SUPPLY_PRESENT=1, POWER_SUPPLY_PARALLEL_DISABLE=0, SUBSYSTEM=power_supply, POWER_SUPPLY_SET_SHIP_MODE=0, POWER_SUPPLY_TEMP=290, ACTION=change, POWER_SUPPLY_RERUN_AICL=0, POWER_SUPPLY_AGE=91, POWER_SUPPLY_NAME=battery, POWER_SUPPLY_VOLTAGE_MAX=-22, POWER_SUPPLY_CONSTANT_CHARGE_CURRENT_MAX=3000000, POWER_SUPPLY_CHARGE_COUNTER=2861824, POWER_SUPPLY_STEP_CHARGING_ENABLED=0, POWER_SUPPLY_NUM_SYSTEM_TEMP_LEVELS=7, POWER_SUPPLY_DIE_HEALTH=Cool, POWER_SUPPLY_INPUT_SUSPEND=0}
11-27 13:37:02.043  2778  2939 D HeadsetStateMachine: Disconnected process message: 10, size: 0
11-27 13:37:02.043  2778  2939 D HeadsetStateMachine: Enter processIntentBatteryChanged()
11-27 13:37:02.043  2778  2939 D HeadsetStateMachine: Exit processIntentBatteryChanged()
11-27 13:37:02.043  2778  2939 D HeadsetStateMachine: Exit Disconnected processMessage()
11-27 13:37:02.044  2564  2564 D QtiCarrierConfigHelper: WARNING, no carrier configs on phone Id: 0
11-27 13:37:02.392   955   968 I mmid    : select timeout: wait for receiving msg
11-27 13:37:02.395  2483  2614 I QCNEJ   : |CORE| CNE received action RSSI/Link Changed events: android.net.wifi.RSSI_CHANGED
11-27 13:37:02.395  2483  2614 D QCNEJ   : |CORE| Updating RSSI: -59
11-27 13:37:02.403  7193  7247 I CarrierServices: [334] bur.a: FiST: Wifi connectivity status true
11-27 13:37:02.407  7193  7247 W CarrierServices: [334] bax.a: This RcsEngine is stale. Ignore Connectivity event on this.
11-27 13:37:02.408  7193  7247 W CarrierServices: [334] bax.a: This RcsEngine is stale. Ignore Connectivity event on this.
11-27 13:37:02.410  7193  7247 I CarrierServices: [334] buw.d: Connected state: [1], networkType: [WIFI]
11-27 13:37:02.965   886  1492 D NativeSensors: CapSensor:  mPendingEvent.distance=1.000000
11-27 13:37:05.395   955   968 I mmid    : select timeout: wait for receiving msg
11-27 13:37:08.507  1890  7359 I ActivityManager: Killing 19055:com.android.providers.calendar/u0a16 (adj 906): empty #17
11-27 13:37:11.403   955   968 I chatty  : uid=0(root) /vendor/bin/mmid identical 2 lines
11-27 13:37:14.406   955   968 I mmid    : select timeout: wait for receiving msg
11-27 13:37:16.071 20287 20292 I zygote64: Do full code cache collection, code=1005KB, data=664KB
11-27 13:37:16.080 20287 20292 I zygote64: After code cache collection, code=993KB, data=573KB
11-27 13:37:17.410   955   968 I mmid    : select timeout: wait for receiving msg
11-27 13:37:17.629   904   935 I ADSPD   : Watchdog 2 new value: 00180217 Last Exp Value: ffffffff
11-27 13:37:17.630   904   935 I ADSPD   : Watchdog 3 new value: 00180212 Last Exp Value: ffffffff
11-27 13:37:20.413   955   968 I mmid    : select timeout: wait for receiving msg
11-27 13:37:23.417   955   968 I chatty  : uid=0(root) /vendor/bin/mmid identical 1 line
11-27 13:37:26.421   955   968 I mmid    : select timeout: wait for receiving msg
11-27 13:37:29.291  1083  1083 I Camera2ClientBase: Closed Camera 0. Client was: com.boss.sportivity (PID 20287, UID 10194)
11-27 13:37:29.292  1083  1083 I Camera2ClientBase: Closed Camera 0. Client was: com.boss.sportivity (PID 20287, UID 10194)
11-27 13:37:29.425   955   968 I mmid    : select timeout: wait for receiving msg
11-27 13:37:35.431   955   968 I chatty  : uid=0(root) /vendor/bin/mmid identical 2 lines
11-27 13:37:38.434   955   968 I mmid    : select timeout: wait for receiving msg
11-27 13:37:39.141  2778  2939 D HeadsetStateMachine: Disconnected process message: 10, size: 0
11-27 13:37:39.142  2778  2939 D HeadsetStateMachine: Enter processIntentBatteryChanged()
11-27 13:37:39.142  2778  2939 D HeadsetStateMachine: Exit processIntentBatteryChanged()
11-27 13:37:39.142  2778  2939 D HeadsetStateMachine: Exit Disconnected processMessage()
11-27 13:37:39.143  2564  2564 D QtiCarrierConfigHelper: WARNING, no carrier configs on phone Id: 0
11-27 13:37:39.143  1104  2470 V LocSvc_HIDL_IzatProvider: [onLocationChanged][67] [HS] =>>>> [HC]
11-27 13:37:39.144  1890  2259 V LocSvc_HIDL_IzatProvider_jni: [onLocationChanged][136] [HC] <<= [HS]
11-27 13:37:39.206   954   954 D SurfaceFlinger: Backpressure trigger, skipping transaction & refresh!
11-27 13:37:41.090  1890  2249 D BatteryService: uevent={POWER_SUPPLY_DP_DM=0, POWER_SUPPLY_VOLTAGE_QNOVO=-22, POWER_SUPPLY_VOLTAGE_NOW=4398426, POWER_SUPPLY_SW_JEITA_ENABLED=0, POWER_SUPPLY_HEALTH=Good, POWER_SUPPLY_TECHNOLOGY=Li-ion, POWER_SUPPLY_CHARGER_TEMP_MAX=812, SEQNUM=5963, POWER_SUPPLY_INPUT_CURRENT_LIMITED=1, POWER_SUPPLY_STATUS=Charging, POWER_SUPPLY_BATTERY_CHARGING_ENABLED=1, POWER_SUPPLY_CURRENT_MAX=3000000, POWER_SUPPLY_CAPACITY=100, DEVPATH=/devices/soc/800f000.qcom,spmi/spmi-0/spmi0-00/800f000.qcom,spmi:qcom,pm660@0:qcom,qpnp-smb2/power_supply/battery, POWER_SUPPLY_CHARGE_DONE=0, POWER_SUPPLY_CHARGE_TYPE=Taper, POWER_SUPPLY_CHARGER_TEMP=332, POWER_SUPPLY_CHARGE_RATE=Normal, POWER_SUPPLY_CURRENT_QNOVO=-22, POWER_SUPPLY_CURRENT_NOW=-275390, POWER_SUPPLY_SYSTEM_TEMP_LEVEL=0, POWER_SUPPLY_PRESENT=1, POWER_SUPPLY_PARALLEL_DISABLE=0, SUBSYSTEM=power_supply, POWER_SUPPLY_SET_SHIP_MODE=0, POWER_SUPPLY_TEMP=290, ACTION=change, POWER_SUPPLY_RERUN_AICL=0, POWER_SUPPLY_AGE=91, POWER_SUPPLY_NAME=battery, POWER_SUPPLY_VOLTAGE_MAX=-22, POWER_SUPPLY_CONSTANT_CHARGE_CURRENT_MAX=3000000, POWER_SUPPLY_CHARGE_COUNTER=2864671, POWER_SUPPLY_STEP_CHARGING_ENABLED=0, POWER_SUPPLY_NUM_SYSTEM_TEMP_LEVELS=7, POWER_SUPPLY_DIE_HEALTH=Cool, POWER_SUPPLY_INPUT_SUSPEND=0}
11-27 13:37:41.102  2564  2564 D QtiCarrierConfigHelper: WARNING, no carrier configs on phone Id: 0
11-27 13:37:41.103  2778  2939 D HeadsetStateMachine: Disconnected process message: 10, size: 0
11-27 13:37:41.103  2778  2939 D HeadsetStateMachine: Enter processIntentBatteryChanged()
11-27 13:37:41.103  2778  2939 D HeadsetStateMachine: Exit processIntentBatteryChanged()
11-27 13:37:41.103  2778  2939 D HeadsetStateMachine: Exit Disconnected processMessage()
11-27 13:37:41.438   955   968 I mmid    : select timeout: wait for receiving msg
11-27 13:37:44.442   955   968 I chatty  : uid=0(root) /vendor/bin/mmid identical 1 line
11-27 13:37:47.445   955   968 I mmid    : select timeout: wait for receiving msg
11-27 13:37:47.634   904   935 I ADSPD   : Watchdog 2 new value: 00180dcf Last Exp Value: ffffffff
11-27 13:37:47.640   904   935 I ADSPD   : Watchdog 3 new value: 00180dcb Last Exp Value: ffffffff
11-27 13:37:50.451   955   968 I mmid    : select timeout: wait for receiving msg

Camera Device
11-27 13:36:55.301 20287 20369 I ReactNativeJS:     "formats": [
11-27 13:36:55.301 20287 20369 I ReactNativeJS:       {
11-27 13:36:55.301 20287 20369 I ReactNativeJS:         "autoFocusSystem": "contrast-detection",
11-27 13:36:55.301 20287 20369 I ReactNativeJS:         "supportsVideoHdr": false,
11-27 13:36:55.301 20287 20369 I ReactNativeJS:         "fieldOfView": 79.64318196593833,
11-27 13:36:55.301 20287 20369 I ReactNativeJS:         "pixelFormats": [
11-27 13:36:55.301 20287 20369 I ReactNativeJS:           "yuv",
11-27 13:36:55.301 20287 20369 I ReactNativeJS:           "native"
11-27 13:36:55.301 20287 20369 I ReactNativeJS:         ],
11-27 13:36:55.301 20287 20369 I ReactNativeJS:         "videoStabilizationModes": [
11-27 13:36:55.301 20287 20369 I ReactNativeJS:           "off",
11-27 13:36:55.301 20287 20369 I ReactNativeJS:           "standard",
11-27 13:36:55.301 20287 20369 I ReactNativeJS:           "off"
11-27 13:36:55.301 20287 20369 I ReactNativeJS:         ],
11-27 13:36:55.301 20287 20369 I ReactNativeJS:         "maxZoom": 8,
11-27 13:36:55.301 20287 20369 I ReactNativeJS:         "supportsPhotoHdr": false,
11-27 13:36:55.301 20287 20369 I ReactNativeJS:         "photoWidth": 4032,
11-27 13:36:55.301 20287 20369 I ReactNativeJS:         "minExposure": -72,
11-27 13:36:55.301 20287 20369 I ReactNativeJS:         "supportsDepthCapture": false,
11-27 13:36:55.301 20287 20369 I ReactNativeJS:         "maxISO": 3200,
11-27 13:36:55.301 20287 20369 I ReactNativeJS:         "minISO": 50,
11-27 13:36:55.301 20287 20369 I ReactNativeJS:         "minFps": 1,
11-27 13:36:55.301 20287 20369 I ReactNativeJS:         "videoWidth": 3840,
11-27 13:36:55.301 20287 20369 I ReactNativeJS:         "maxExposure": 72,
11-27 13:36:55.301 20287 20369 I ReactNativeJS:         "videoHeight": 2160,
11-27 13:36:55.301 20287 20369 I ReactNativeJS:         "maxFps": 30,
11-27 13:36:55.301 20287 20369 I ReactNativeJS:         "photoHeight": 3024
11-27 13:36:55.301 20287 20369 I ReactNativeJS:       },

Device
Motorola g5
VisionCamera Version
3.6.10
Can you reproduce this issue in the VisionCamera Example app?
Yes, I can reproduce the same issue in the Example app here
Additional information

[ ] I am using Expo
[X] I have enabled Frame Processors (react-native-worklets-core)
[X] I have read the Troubleshooting Guide
[X] I agree to follow this project's Code of Conduct
[X] I searched for similar issues in this repository and found none.

Removed the following line(446) :
captureRequest.setZoom(config.zoom, cameraCharacteristics)
in node_modules\react-native-vision-camera\android\src\main\java\com\mrousavy\camera\core\CameraSession.kt
Which fixed my camera problem but when scanning a qr code the app crashes(sometimes).
Yes I can reproduce.

Same problem here, in devices like Motorola g6 plus (Android 9) (always black screen), Samsung Galaxy s21 FE (Android 13) but in this only when bring the app from background y open the camera again.
Camera.onError(session/camera-has-been-disconnected): [session/camera-has-been-disconnected] The given Camera device (id: 0) has been disconnected! Error: CAMERA_IS_DISABLED_BY_ANDROID [session/camera-has-been-disconnected: [session/camera-has-been-disconnected] The given Camera device (id: 0) has been disconnected! Error: CAMERA_IS_DISABLED_BY_ANDROID]

@MicaelaWaigel i think this is because we are not propertly closing the camera session when it goes to background, need to double check, if someone have more time than me to test this theory please go ahead

@MicaelaWaigel i think this is because we are not propertly closing the camera session when it goes to background, need to double check, if someone have more time than me to test this theory please go ahead

We set the isActive according the isFocused and appState, so when the app is in background after a while the error Camera.onError(session/camera-has-been-disconnected): [session/camera-has-been-disconnected] The given Camera device (id: 0) has been disconnected! Error: CAMERA_IS_DISABLED_BY_ANDROID occurs.
When the appState changed to active, then the error is Camera.onError(unknown/unknown): [unknown/unknown] CameraDevice was already closed [unknown/unknown: [unknown/unknown] CameraDevice was already closed]

Hey! Thanks for reporting this issue.
I've been working the past days on making sure the Camera lifecycle is safely handled and released when needed to make sure this crash doesn't occur anymore.
I just created a PR for this - can you please this to see if that fixes the issue for you? https://github.com/mrousavy/react-native-vision-camera/pull/2339
If this fixes your issue, please consider 💖 sponsoring me on GitHub 💖 to support me / thank me for building VisionCamera and continuously improving it.
If this does not fix your issue, please clone the repo, check out the branch fix/blackscreen (the PR above), run the Example app, reproduce your issue there and share the adb logcat logs with me (upload to pastebin or gist) so I can investigate this further.
Thank you! 🙏


GraphQL operations must contain a non-empty query or a persistedQuery extension.

I get this error when trying to query the database in a next js 13 server component

I am also receiving this error on a similar usecase. Is there any solution you got @Eleven-am


Initializer for default background color and text color

The components are currently opinionated in that they use a bg-primary and a text-light for the cards.
In some UIs this can be a little .. uhh .. offensive! It would be nice to have the default be very neutral, however, still over the option to customize the background and text colours for all cards.
In the future, it might make sense to add the options as overrides on a per component basis.

I'd love to jump in on this one


Switch to pathlib #54

Solves #54

Perfect thanks! Let me know if you have any preference on what to contribute next.

Perfect thanks! Let me know if you have any preference on what to contribute next.

Thanks, actually don't have any preferences. Do you have some ideas? Maybe an interesting task or something to get familiar with the project.


config.esversion -> config.build.?????

For consistency with minify, but what should the property be?  Do we just want to indicate that a source probably needs transpilation in some cases?  In that case this would do:
config.build.transpile = true

However it might be that Babel needs to know more about how a source is constructed and what standards have been used.  In that case maybe:
config.build.transpileFrom = 'es2015'

I don't know of any polyfills that require compiling to older ES environments. Do you have any you could link me to?

https://github.com/Financial-Times/polyfill-service/blob/master/polyfills/Math/acosh/polyfill.js
It's more the principle that it will be increasingly common in future

Thinking more about this - the need to transpile is a property of the target UA's syntax support, not the polyfill source's use of particular syntax.  In theory, when you get a request from a UA that supports no more than ES5, you pass all polyfills that you intend to serve to that browser through a 'make sure this works in ES5' transpilation.  So the behaviour varies on the UA, not on the polyfill.
However, currently, we do the opposite: Transpilation depends on the properties of the polyfill, not the UA.  This is for two reasons:

We currently make an assumption that all browsers support ES5 and none support any syntax more advanced than that, so essentially there's no variation to be had between UAs.
Transpiling the majority of polyfills is unnecessary as their syntax is compatible with ES5, so doing so would slow down the build unnecessarily.

Point 1 can be expected to change at some point in future. But point 2 is an optimisation that we should avoid losing.  So a better implementation is probably something like willTranspile = polyfill.esVersion > ua.maxEsSyntaxSupport.  On that basis we should stick to the current naming and location of the esVersion` property.
Another option, theoretically more ideal, would have us able to use granular data on specific syntax support (eg from Kangax tables) and transpile only the specific features not implemented in the browser.  But that's likely to be fiddly, error prone and not worth it.
So on balance I think we stick with esVersion as it is and review again when we want to add a polyfill that requires more advanced transpilation.


ZEVA - BCeID Submitted Credit Application Filtering Issue

Describe the Bug
Suppliers submit credit applications (on the BCeID side). These credit applications then sit in their Credit Applications dashboard folder - awaiting validation. When the analyst on the IDIR side, validate the credit applications, it changes the status from “Submitted” to “Validated” on the IDIR side.  The supplier is no longer able to view these credit application when they try to view them from their dashboard. The only way to view them is to delete the submitted status in the filter bar. Then all credit applications will show.
When the credit application is issued, the credit application will then show up in the suppliers issued dashboard folder. But there is a period of time where the supplier cannot see all their submitted credit applications given the current filtered view, unless they delete the status "submitted".
Expected Behaviour
When the BCeID user selects "Credit Applications - # awaiting validation" the number of submitted application should appear on that page.
Actual Behaviour
When a BCeID user selects "Credit Applications - # awaiting validation" no submitted applications appear, unless you delete the filter status.
Implications
The BCeID user thinks that their credit applications have disappear and they email the analyst to see what has happened to them.
Steps To Reproduce
Steps to reproduce the behaviour:
User/Role: BCeID user on dev

Go to dev and use DPAC
Click on Credit Applications - 3 awaiting validation'
See error

Notes:
This was reported by a supplier in an email, but they didn't include screenshots. I have an image to upload, but it's not working for some reason.
Development Checklist:

[ ] A

[ ]  B

[ ] C

Hey team! Please add your planning poker estimate with Zenhub @emi-hi @JulianForeman @tim738745


Add filter Tree resolving

Similar to flare and cql a researcher can filter the data to be extracted by codes of terminologies.
These codes include codes higher up in the code hierarchy.
Given that the DIC always save the data in leaf codes analogous to flare and cql torch has to resolve the chosen filter codes using the mapping_tree.json provided by ontology generator.

@alexanderkiel,  @Lucas0T  - we should discuss this, as torch will now have a dependency to the mapping directly.
Note also, that this will be necessary anyway in order to resolve the CQL trees for sq2cql


[MINOR]: Add documentation to datafusion-row modules

Rationale:
I am working on writing up more detail on various next steps for the RowFormat on https://github.com/apache/arrow-datafusion/issues/1861 and found myself reading the code to understand what was going on better. I have encoded various thoughts into docstrings so hopefully future readers will find the code easier to navigate.
Changes:

Add / move docstrings
No code change

cc @yjshen

Codecov Report

Merging #2704 (6543d75) into master (bbb674a) will increase coverage by 0.00%.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #2704   +/-   ##
=======================================
  Coverage   84.66%   84.66%
=======================================
  Files         270      270
  Lines       46919    46919
=======================================
+ Hits        39723    39726    +3
+ Misses       7196     7193    -3

Impacted Files
Coverage Δ

datafusion/row/src/accessor.rs
56.41% <ø> (ø)

datafusion/row/src/layout.rs
98.27% <ø> (ø)

datafusion/row/src/lib.rs
100.00% <ø> (ø)

datafusion/row/src/reader.rs
88.27% <ø> (ø)

datafusion/row/src/writer.rs
89.86% <ø> (ø)

datafusion/optimizer/src/utils.rs
32.25% <0.00%> (-0.54%)
:arrow_down:

datafusion/core/src/physical_plan/metrics/value.rs
86.93% <0.00%> (-0.51%)
:arrow_down:

datafusion/common/src/scalar.rs
74.94% <0.00%> (+0.11%)
:arrow_up:

datafusion/expr/src/logical_plan/plan.rs
74.75% <0.00%> (+0.59%)
:arrow_up:

datafusion/expr/src/window_frame.rs
93.27% <0.00%> (+0.84%)
:arrow_up:

Continue to review full report at Codecov.

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


I always get a parse error with my aws config ini file that has a saml provider

I always get the following:
had an error: IniFile::Error: Could not parse line: "url = https://<samlurl>"

This is due to the colon.  Upgrading the inifile gem should fix.


Generate cloud-init paths without creating directories

What this PR does / why we need it:
For e2e tests we generate the path where we can find the cloud-init iso.
Only set the expected path on the cloud-init package without trying to
create the path structure.
We don't see this in our CI tests because in the CI cluster, the test binary has the right to execute the path in question.
On other CI systems where the permission is not given, we just got an error which we ignored which lead to wrongly constructed paths.
This is a test-only issue.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #5973
Special notes for your reviewer:
Release note:
NONE

/cc @davidvossel
/cc @mlsorensen

/cherrypick release-0.43

/cherrypick release-0.41


[HOW-TO] How to set up user defined privacy level

What is the bug related to?
Registry Core
What went wrong?
Wasn't able to find it in the documentation
What did you expect to see?
Example configuration on the field where privacy is user controlled.
Additional Context
No response
Relevant logs/output (if any)
No response

Closing since this needs to be a discussion


Unit test shouldNotEmitEventForAbsentJfrEventType Failed

Bug Report
Current Behavior
The unit test shouldNotEmitEventForAbsentJfrEventType() in the class JfrEventRecorderUnitTests failed.
The expecting value was false but somehow it returned true. While debugging, I noticed that the createEvent() was called, is this the expected behavior? Thank you!

org.opentest4j.AssertionFailedError:
Expecting value to be false but was true
Expected :false
Actual   :true

Environment

Lettuce version(s): 6.2.2 RELEASE (Also failed in 6.5.0 RELEASE)
Redis version: N/A

@XuexuanWang priority-wise how important is this for you right now?


Added Music Player Application

Completely Solved #13

As a beginner to open-source you can contribute to hacktoberfest2023
You can also checkout our Idea-Arca, the project idea bank for any languages, for open-source contributions.
Happy Contributing season!
Keep up the good work!


[JS] Update node dependencies in release/1.2

Description
Update node dependencies in the release/1.2 branch
How Verified

built locally
sanity check against local build

Microsoft Reviewers: Open in CodeFlow

/azp run

@dclaux/@matthidinger: I wouldn't normally bother you guys with some simple package updates, but since this is against the release/1.2 branch, it's probably a good idea.
also, the PR site doesn't seem to work (the links on the top don't seem to be relative to /pr/3981... I assume this is expected for release/1.2 PRs?

@dclaux / @matthidinger - any chance I could get a look here?

/azp run


force WSL to get internet from wi-fi

My computer has Wi-Fi and Lan cable at the same time.
And WSL takes the Internet from cable LAN.
I want to force it to connect to Wi-Fi.
What should I do?

fixed via custom kernel compile with https://github.com/microsoft/WSL2-Linux-Kernel
and using USBIPD


Performance issues in /hangul_model.py (by P3)

Hello! I've found a performance issue in /hangul_model.py: batch() should be called before map(), which could make your program more efficient. Here is the tensorflow document to support it.
Detailed description is listed below:

.batch(BATCH_SIZE)(here) should be called before .map(_parse_function)(here).
.batch(BATCH_SIZE)(here) should be called before .map(_parse_function)(here).

Besides, you need to check the function called in map()(e.g., _parse_function called in .map(_parse_function)) whether to be affected or not to make the changed code work properly. For example, if _parse_function needs data with shape (x, y, z) as its input before fix, it would require data with shape (batch_size, x, y, z).
Looking forward to your reply. Btw, I am very glad to create a PR to fix it if you are too busy.

Hello, I'm looking forward to your reply~