Unable to use SSO with tenants that enforce device management compliance policy.

[X] I am running the latest version of Node and the tools
[X] I checked the documentation and found no answer
[X] I checked to make sure that this issue has not already been filed

Expected behavior
On a machine registed in AAD and with a valid compliance status, I expect to be able to sign in to my tenant inside an Excel add-in, even if the tenant enforces device compliance.
Current behavior
Using the [SSO quickstart] (https://docs.microsoft.com/en-us/office/dev/add-ins/quickstarts/sso-quickstart), signing in results in an compliance error as the device state does not meet my tenant's requirements.  The details show my device is considered "Unregistered" inside the add-in but sign in works normally in a browser. Device is AAD joined.
Steps to Reproduce
Please provide detailed steps for reproducing the issue.

Test on a tenant that enforces device compliance.
Follow the [SSO quickstart] (https://docs.microsoft.com/en-us/office/dev/add-ins/quickstarts/sso-quickstart)
Run the sample and click the "Get My User Profile Button"

Context
Please provide any relevant information about your setup. This is important in case the issue is not reproducible except for under certain conditions.

Operating System: Windows 11
Node version: v14.18.1
Office version: v2110 (build 14527.20178 C2R)
Tool version:

Failure Logs

I just followed all the steps on your issue and managed to follow the tutorial as normal with no errors on webview 2 (which was the one you were having trouble with).
There shouldn't be any configuration missing in webview2 and the project works just as normal.
Could you try rerunning the SSO configuration you ran on another device? Just to see if you can get it to work right away with webview2, as there may be something we are missing.

To clarify, for readers and folks on Office's engineering end. If the legacy Edge control works for you, then what is failing here is the fallback that uses the Dialog API, not the SSO API itself, the SSO API does not depend on what WebView control you use.

The SSO template has been updated significantly in recent months.  Please try it out on a new project and re-open this (or log a new issue) if you are still encountering problems.


Testing autocomplete with Cucumber

Is anyone having problems to test it with Cucumber, and with the helper provided?
I try a lot to debug, but I still can't find the root of the problem. The helper acts as follow:
	page.execute_script %Q{ $('input[data-autocomplete]').trigger("focus") }
	page.execute_script %Q{ $('input[data-autocomplete]').trigger("keydown") }
	sleep 1
	page.execute_script %Q{ $('.ui-menu-item a:contains("#{value}")').trigger("mouseenter").trigger("click"); }

Which I guess should be working fine, however when I put save_and_open_page and also use debugger (which allows me to play with the page, check for the XHR, etc) I see that no autocomplete is appearing there. The XHR in fact happens, but the autocomplete menu with suggestions doesn't appear.
I have other javascript tests, and they all working fine, however this one isn't. I tried with different javascript drivers also, selenium and webkit.
Let's say I have this test (as is the example in the main Git page):
	@javascript
	Scenario: Autocomplete
	  Given the following brands exists:
	    | name  |
	    | Alpha |
	    | Beta  |
	    | Gamma |
	  And I go to the home page
	  And I fill in "Brand name" with "al"
	  And I choose "Alpha" in the autocomplete list
	  Then the "Brand name" field should contain "Alpha"

The last step would fail, saying that "Alpha" was expected, but instead it was "al" (the user input). Again, means the autocomplete isn't loading (?). Oh, and btw, it works fine when I do rails s  and access it via browser.
Any advices or anyone there that had trouble with it?
Thanks

OK, found the problem:
Rails3 autocomplete is using html entities within the SQL. That is, instead of " it's using "
I realized that after debugging it using selenium and seeing Firefox XHR logs. Look:


Merge websocket star and webrtc star signal server

Currently Webrtc star has a signal server bundled into the library. I purpose moving it into its own library or merging it into this library and put them behind flags. Thoughts?

WebSocketStar is in the process of being deperacted due to protocol problems, such as not having any buffering mechanisms which usually caused the whole thing to blow up multiple times a day.
It would be great though, to take the code from here and use it as a base for the WebRTCStar Server
Another thing that's in progress is https://github.com/mkg20001/interface-data-exchange (currently WIP), which might completly remove the server requirement in WebRTCStar and simply re-use the existing libp2p swarm instead of adding socket.io into the mix.

Interesting. Looks like there hasn't been much movement on data- exchange in the last few months, but it sounds great. Are you up for a brief call to chat about the idea a bit? I'd be willing to take a stab at pushing the protocol forward.

Are you up for a brief call to chat about the idea a bit? I'd be willing to take a stab at pushing the protocol forward.

Do you mean zoom? Yes, but my scheudle today is pretty limited. Otherwise usually from 16:30 UTC+1
Recently I've decided to continue the protocol, working on making it use Promises.
You should be able to take most of the info out of this PR https://github.com/libp2p/js-libp2p-webrtc-star/pull/148 and the linked slides https://docs.google.com/presentation/d/1yfxI_4wY-5ydFxcIr2NBsg8E0wyJJStekRfectZjcf0/edit?usp=sharing

@mkg20001 sounds good. I just got back from a trip and I should be able to jump on Zoom or Discord to chat. I'm UTC-7 atm, so any time after 16:30 UTC+1 should work for me as well.

@JustMaier sent you the details via email


Allow setting a constance spacing between arc elements

Resolves #4990

Size Change: +520 B (0%)
Total Size: 245 kB

Filename
Size
Change

dist/chart.esm.js
70.6 kB
+216 B (0%)

dist/chart.js
89.6 kB
+182 B (0%)

dist/chart.min.js
63.8 kB
+122 B (0%)

Thanks. I figure we should release a v3.3.1 first, so will merge this after that goes out. I think #9181 should be the last thing in 3.3.1


Crash ingame

https://mclo.gs/4Rtb2lO

Try version 1.0.1 - I didn't find any crashes during testing and everything was stable. Version 1.0.1 will be on CurseForge within a day.


[Feature request] Title max length parameter

Hi,
Thanks for the great job! I would need a title length a bit longer than 18.. would it be possible to have a parameter like:
<ExNavigator
    showNavigationBar={true}
    navigationBarStyle={styles.navigationBar}
    titleStyle={styles.title}
    sceneStyle={styles.scene}
    maxTitleLength={20} //<--- new parameter
    initialRoute={initialRoute} />

to enable to have title longer than 18 caracters?
That would be great!
Thanks,

Hi,
I'm trying to make a pull request with that modification but I can't push my commits in the branch I created, I'm getting this error:
remote: Permission to exponentjs/ex-navigator.git denied to fxhereng.
fatal: unable to access 'https://github.com/exponentjs/ex-navigator.git/': The requested URL returned error: 403

Could you explain to me the procedure to make a pull request?
I would appreciate,
Thanks!

Instead of maxTitleLength, how about a function called truncateTitle that receives the original title and is supposed to return the new one? That way you can decide how the title is shortened.

Read this for how to send PRs: https://help.github.com/articles/using-pull-requests/

Sure, and as default parameter I can put the shortenTitle function you already have.


spotify-player via bash/CLI

Is your feature request related to a problem? Please describe.
I am looking for a substitution of my current setup using libspotify/mopidy.
Describe the solution you'd like
Control the spotify-player via bash.
Essentially, i would like to issue a bash command on my machine (providing Spotify URI or alike) which then starts steaming the music. I dont want to have to go over the tui.
Describe alternatives you've considered
hmm... no idea.
Additional context
< imagine a screenshot of an empty terminal window here >

if this is already possible, could you point me to an example/documentation?

I assume that you want a headless spotify-player. I don't really have any plans to do that as spotify-player is a TUI application. I think you may want to look into spotifyd.

ok thanks.
spotifyd (just as 99% of the forks of librespot ) requires a dedicated spotify client (eg mobile phone) to operate... so they do me no good.

No iirc, spotifyd itself is a client, so you don't need another one. From the project's README:

Spotifyd streams music just like the official client, but is more lightweight and supports more platforms. Spotifyd also supports the Spotify Connect protocol, which makes it show up as a device that can be controlled from the official clients.

naah, spotifyd is only the deamon for playback. Most people seem to use spotify-tui to control it (which offered a nice clean CLI), but thats no longer maintaned. This is why i ended up on your repo in the first place :-)
But thanks anyway, much appreciation!

FYI - for anyone also interested: librespot-java offers an HTTP-Endpoints which can be served by curling:
https://github.com/librespot-org/librespot-java/tree/dev/api

i think a workaround is to literally spawn spotify-player into an empty shell, and have one of #103 (control and query spotify-player, and other devices) feature request.
however, you can simply use spotifyd and control it with playerctl :D

This appears to be related to https://github.com/aome510/spotify-player/issues/42 in terms of replacing other music daemons.

Yeah, I'm aware of this issue and the other one. Currently working on implementing daemon support.


Generative Art Project :white_flower:

Rangoli Generative Art
This is a JavaScript project to celebrate Diwali festival in Digital manner using Generative Art for creating Rangoli.
Project is live at 👇
rangoli-generative-art.netlify.app/
Output of Rangoli Generative Art :smiley:

Hacktobefest 2022
Thank you!

@thinkswell please review! 😅


Ballerina build command does not show all the semantic errors for a project

Description:
Consider the following project structure
project
-------|---src
------------|--mod1
----------------|--test1.bal
------------|--mod2
----------------|--test2.bal
In the above case, test2.bal has a semantic error.
test1.bal has an import statement for mod2 as import mod2;
This import is an unused import.
When executing the ballerina build -a command it should prompt both errors. But, the observed behaviour is, it only prompts the semantic error in test2.bal.
Affected Versions:
v1.2.0-SNAPSHOT at least

@hevayo @warunalakshitha seems like this is broken from the packerina side.

Compilation does not allow to move to the next phase if typechecker has errors. Unused import is checked in dataflow analyser and it skips the type checker errors.


getting-started-guides-Kubespray-pr-2017-07-15

NOTE: Please check the “Allow edits from maintainers” box (see image below) to
allow reviewers to fix problems on your patch and speed up the review process.
Please delete this note before submitting the pull request.

@chentao1596 @markthink  按照 review 我改了提交了 你们看看 还有其他问题吗

@yufengqi OK


LayerTree changes are not getting saved into the file

See https://github.com/QuantStack/jupytergis/pull/22#discussion_r1660718649

The changes on the tree are propagated to collaborators, but not save in the file. In a regular usage (new layer and layer included in tree), it works well because the new layer trigger the change on the server side. But if we only include a layer in the tree, it is not saved in the file. @davidbrochart any thoughts on this ?

Actually I can't reproduce, I can see the layerTree being properly updated:
https://github.com/QuantStack/jupytergis/assets/21197331/9fe81bef-cf8c-416f-91dc-2cd979b4f848

Yes, I observed this when doing some tests modifying only the layer tree, and not the layers and sources.
We will soon add a way to move the layers in the tree (without changing the layers and the sources), we'll see if the issue is still relevant.

I guess the kind of UI we'd want is being able to select multiple layers then right-click -> group selection

Yes, the context menu is a good option to create groups from layers.
We probably also want drag and drop to move the layers individually.


Added pin configuration for esp32-c6

Added pin configuration for ESP32-C6.  Tested with Beetle ESP32-C6 from DFRobot

Thanks for the addition, happy to see people getting use out of this. 🙂


Built-in keys link for 1.x build definition docs broken

The following link
on the build definition page
is broken in the Built-in keys section

Also broken in Library-Dependencies


Missing resolutions even with DASH Playback enabled?

Hi, new user here, I just installed YouTubeCenter with the default options in Chrome/Tampermonkey, so DASH Playback is already checked, but I'm still not able to see the various missing resolutions  (480p, 1080p).
Is there another setting or conflicting extension, etc. that may be causing this? When I disable YTC, those resolutions are available again...
I have Magic Actions and anything Youtube-related removed from my Chrome extensions, so I'm quite confused. For reference, I'm using the YTC developer build (537)  and latest Chrome 47.
Thanks!

I'm having this issue as well, only 720p and 360p are available to me. It's as if YouTube Center has lost the ability to have DASH enabled, regardless of how the setting is set.

Same issue here. Interestingly enough, it's only happening to my own newer videos that I uploaded, both Chrome and Firefox.
Some other interesting facts:

Videos that work correctly in 1080p60, both with and without YTC, are video/webm; codecs="vp9" in Chrome, and video/mp4; codecs="avc1.64002a" in Firefox.
Videos that do not work correctly with YTC and are 1080p60, are video/mp4; codecs="avc1.64002a" in both browsers. When using YTC it detects them as video/mp4; codecs="avc1.64001F, mp4a.40.2" and doesn't use DASH at all.

And yes, DASH is enabled in settings.

Good insight.
Hope this is fixed soon.

I tried to look what the difference is between the videos, and I've found something that might causes YTC to not detect DASH.
Apparently, YTC checks the adaptive_fmts parameter, which is where the information about DASH streams are located (I assume). If this parameter is not available, YTC assumes DASH is not available.
But, now comes the fun part. The video that works correctly with YTC, does indeed have this parameter. But the video that doesn't work correctly with YTC, doesn't have this parameter at all, even though that video still has DASH streams.
So, upon further investigating, I stumped upon the dashmpd parameter. I monitored the network in Chrome, and YouTube indeed downloads the file that's listed in this parameter (something along the lines of http://manifest.googlevideo.com/api/manifest/dash/...). The resulting file is an XML file with the DASH streams. Interestingly enough, with the other video that does work correctly with YTC, YouTube skips this file entirely even though the dashmpd parameter is still there.
I don't have the knowledge to try fixing it myself, as the source file is huuuuuge and it seems to involve more than just fixing it in one line. Anyway, here are some of my videos to show the issue:

https://www.youtube.com/watch?v=LXc0rpJv9qs (doesn't work properly in YTC)
https://www.youtube.com/watch?v=IzH3NKqArr0 (works properly in YTC)

Both of them are 1080p60.

Bump

I have exact same problems


Perhaps you should write in README.md that you need a firewall to open the port Receivers to work properly.

I didn’t know that Receivers needed to monitor 4010 to work half an hour ago.😂

Added a note :+1:


hasp_Dim_Screen_on_Idle.yaml - anyway to turn off screen?

Thank you for producing hasp_Dim_Screen_on_Idle.yaml.  I was curious if there was a way to have the screen go to 0 (or ideally off) on idle?

There wasn't, but now that you said that, I think it's a good idea (thanks!) and I've updated the blueprint so that you can now enter 0 as a brightness value for the dimming, which will turn off the backlight entirely.
Great idea and thanks for the issue!

Bedroom installations are the reason I wrote the blueprint in the first place :D  Glad this seems to fit your use case!

This is wonderful. I am going to use this for a neat use case (IMO). I have bedside HASPone's that during the day will dim to 20 when idle and go up to 60 when pressed. At night, when all the lights are off, locks are locked, and security system is active screen will dim to 0 when idle and up to 40 when in use. This has very very high wife approval. Thank you for making us both very happy!

Very cool.  I've love to do something similar.  How do you set the variable dimming?

There a probably many ways to do this and most are probably better than what I came up with.  I used one template and four automations.  The template creates a binary sensor that if on indicates we are ready for 'night mode.' Then two automations that derived from the Dim screen on idle blue print.  One for the day state one for the night.  Then two more automation triggered by the state of the template, that execute the day or the night automation mentioned above.
I've attached the two as pasting to this message board seems to mess up the formatting
Automations.txt
Template.txt


Create endpoint to check if a descriptor has been imported

Derive the descriptor at address index 0 and see if the encoded address exists in the wallet pool of bitcoind.
Bonus: figure out the range that was used to import the descriptor.

Done


Encode failed (error 3)

You have helped in the past, and now I am back!
My computing environment has completely changed, so I will try to provide all the pertinent info:
Here is the command resulting in the failure:

f:\Users\Randall>transcode-video --quick --no-log --output "G:\plex media\Movies\The Italian Job (2003\The Mighty Minis of the Italilan Job.mkv" --crop 0:0:0:0 "G:\MKVfiles\ITALIAN_JOB\title06.mkv"

Here is the result of running that command:

f:\Users\Randall>transcode-video --quick --no-log --output "G:\plex media\Movies
\The Italian Job (2003\The Mighty Minis of the Italilan Job.mkv" --crop 0:0:0:0 "G:\MKVfiles\ITALIAN_JOB\title06.mkv"
[12:17:31] hb_init: starting libhb thread
[12:17:31] thread 54e4a90 started ("libhb")
HandBrake 1.1.2<PHONE_NUMBER>) - MinGW x86_64 - https://handbrake.fr
8 CPUs detected
Opening G:\MKVfiles\ITALIAN_JOB\title06.mkv...
[12:17:31] CPU: Intel(R) Core(TM) i7 CPU       Q 740  @ 1.73GHz
[12:17:31]  - logical processor count: 8
[12:17:31] Intel Quick Sync Video support: no
[12:17:31] hb_scan: path=G:\MKVfiles\ITALIAN_JOB\title06.mkv, title_index=1udfread ERROR: ECMA 167 Volume Recognition failed
src/libbluray/disc/disc.c:323: failed opening UDF image G:\MKVfiles\ITALIAN_JOB\title06.mkv
src/libbluray/disc/disc.c:424: error opening file BDMV\index.bdmv
src/libbluray/disc/disc.c:424: error opening file BDMV\BACKUP\index.bdmv
[12:17:31] bd: not a bd - trying as a stream/file instead
libdvdnav: Using dvdnav version 6.0.0
libdvdread: Encrypted DVD support unavailable.
libdvdread:DVDOpenFileUDF:UDFFindFile /VIDEO_TS/VIDEO_TS.IFO failed
libdvdread:DVDOpenFileUDF:UDFFindFile /VIDEO_TS/VIDEO_TS.BUP failed
libdvdread: Can't open file VIDEO_TS.IFO.
libdvdnav: vm: failed to read VIDEO_TS.IFO
[12:17:31] dvd: not a dvd - trying as a stream/file instead
Input #0, matroska,webm, from 'G:\MKVfiles\ITALIAN_JOB\title06.mkv':
Duration: 00:05:39.00, start: 0.000000, bitrate: N/A
Stream #0:0(eng): Video: mpeg2video (Main)
yuv420p, tv, smpte170m/smpte170m/smpte170m
720x480 [PAR 8:9 DAR 4:3], 9800 kb/s, PAR 8:9 DAR 4:3
29.97 fps, 1k tbn
Metadata:
BPS-eng         : 4778106
DURATION-eng    : 00:05:39.005333333
NUMBER_OF_FRAMES-eng: 10160
NUMBER_OF_BYTES-eng: 202475232
SOURCE_ID-eng   : 0100E0
_STATISTICS_WRITING_APP-eng: MakeMKV v1.12.3 win(x64-release)
_STATISTICS_WRITING_DATE_UTC-eng: 2018-09-25 23:20:46
_STATISTICS_TAGS-eng: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES SOURCE_ID
Stream #0:1(eng): Audio: ac3
48000 Hz, stereo, fltp, 192 kb/s (default)
Metadata:
title           : Stereo
BPS-eng         : 192000
DURATION-eng    : 00:05:39.008000000
NUMBER_OF_FRAMES-eng: 10594
NUMBER_OF_BYTES-eng: 8136192
SOURCE_ID-eng   : 0180BD
_STATISTICS_WRITING_APP-eng: MakeMKV v1.12.3 win(x64-release)
_STATISTICS_WRITING_DATE_UTC-eng: 2018-09-25 23:20:46
_STATISTICS_TAGS-eng: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES SOURCE_ID
[12:17:31] scan: decoding previews for title 1
[12:17:31] scan: audio 0x1: ac3, rate=48000Hz, bitrate=192000 English (AC3) (2.0 ch) (Dolby Surround)
[12:17:31] scan: 10 previews, 720x480, 29.970 fps, autocrop = 0/0/0/2, aspect 4:3, PAR 8:9
[12:17:31] libhb: scan thread found 1 valid title(s)

Using preset: CLI Default
title 1:

stream: G:\MKVfiles\ITALIAN_JOB\title06.mkv
duration: 00:05:39
size: 720x480, pixel aspect: 8/9, display aspect: 1.33, 29.970 fps
autocrop: 0/0/0/2
chapters:

1: cells 0->0, 0 blocks, duration 00:05:39

audio tracks:

1, English (AC3) (2.0 ch) (Dolby Surround) (iso639-2: eng), 48000Hz, 192000bps

subtitle tracks:
[12:17:31] 1 job(s) to process
[12:17:31] json job:
{
"Audio": {
"AudioList": [
{
"Encoder": 512,
"Track": 0
}
],
"CopyMask": [
"copy:aac",
"copy:ac3",
"copy:eac3",
"copy:dtshd",
"copy:dts",
"copy:mp3",
"copy:truehd",
"copy:flac"
],
"FallbackEncoder": "av_aac"
},
"Destination": {
"AlignAVStart": false,
"ChapterList": [
{
"Name": ""
}
],
"ChapterMarkers": false,
"File": "G:/plex media/Movies/The Italian Job (2003/The Mighty Minis ofthe Italilan Job.mkv",
"InlineParameterSets": false,
"Mp4Options": {
"IpodAtom": false,
"Mp4Optimize": false
},
"Mux": "mkv"
},
"Filters": {
"FilterList": [
{
"ID": 6,
"Settings": {
"mode": 1,
"rate": "27000000/1126125"
}
},
{
"ID": 11,
"Settings": {
"crop-bottom": 0,
"crop-left": 0,
"crop-right": 0,
"crop-top": 0,
"height": 480,
"width": 720
}
}
]
},
"Metadata": {},
"PAR": {
"Den": 9,
"Num": 8
},
"SequenceID": 0,
"Source": {
"Angle": 0,
"Path": "G:\MKVfiles\ITALIAN_JOB\title06.mkv",
"Range": {
"End": 1,
"Start": 1,
"Type": "chapter"
},
"Title": 1
},
"Subtitle": {
"Search": {
"Burn": true,
"Default": false,
"Enable": false,
"Forced": false
},
"SubtitleList": []
},
"Video": {
"ColorMatrixCode": 0,
"Encoder": "x264",
"Level": "3.0",
"Options": "vbv-maxrate=1500:vbv-bufsize=3000:crf-max=25:qpmax=34:analyse=none:ref=1:rc-lookahead=30",
"Preset": "medium",
"Profile": "high",
"QSV": {
"AsyncDepth": 4,
"Decode": false
},
"Quality": 1.0,
"Tune": "",
"Turbo": false,
"TwoPass": false
}
}
[12:17:31] starting job
[12:17:31] work: mixdown not specified, track 1 setting mixdown Dolby Surround
[12:17:31] work: compression level not specified, track 1 setting compression level 2.00
[12:17:31] work: bitrate not specified, track 1 setting bitrate 160 Kbps
[12:17:31] job configuration:
[12:17:31]  * source
[12:17:31]    + G:\MKVfiles\ITALIAN_JOB\title06.mkv
[12:17:31]    + title 1, chapter(s) 1 to 1
[12:17:31]    + container: matroska,webm
[12:17:31]  * destination
[12:17:31]    + G:/plex media/Movies/The Italian Job (2003/The Mighty Minis of the Italilan Job.mkv
[12:17:31]    + container: Matroska (libavformat)
[12:17:31]  * video track
[12:17:31]    + decoder: mpeg2video
[12:17:31]      + bitrate 9800 kbps
[12:17:31]    + filters
[12:17:31]      + Framerate Shaper (mode=1:rate=27000000/1126125)
[12:17:31]        + frame rate: 29.970 fps -> constant 23.976 fps
[12:17:31]      + Crop and Scale (width=720:height=480:crop-top=0:crop-bottom=0:crop-left=0:crop-right=0)
[12:17:31]        + source: 720 * 480, crop (0/0/0/0): 720 * 480, scale: 720 * 480
[12:17:31]    + Output geometry
[12:17:31]      + storage dimensions: 720 x 480
[12:17:31]      + pixel aspect ratio: 8 : 9
[12:17:31]      + display dimensions: 640 x 480
[12:17:31]    + encoder: H.264 (libx264)
[12:17:31]      + preset:  medium
[12:17:31]      + options: vbv-maxrate=1500:vbv-bufsize=3000:crf-max=25:qpmax=34:analyse=none:ref=1:rc-lookahead=30
[12:17:31]      + profile: high
[12:17:31]      + level:   3.0
[12:17:31]      + quality: 1.00 (RF)
[12:17:31]  * audio track 1
[12:17:31]    + decoder: English (AC3) (2.0 ch) (Dolby Surround) (track 1, id 0x1)
[12:17:31]      + bitrate: 192 kbps, samplerate: 48000 Hz
[12:17:31]    + mixdown: Dolby Surround
[12:17:31]    + encoder: MP3 (libmp3lame)
[12:17:31]      + bitrate: 160 kbps, samplerate: 48000 Hz
[12:17:31]      + compression level: 2.00
[12:17:31] sync: expecting 10159 video frames
[12:17:31] encx264: min-keyint: 24, keyint: 240
[12:17:31] encx264: encoding at constant RF 1.000000
[12:17:31] encx264: unparsed options: vbv-maxrate=1500:vbv-bufsize=3000:crf-max=25:qpmax=34:analyse=none:ref=1:rc-lookahead=30:level=3.0
x264 [info]: using SAR=8/9
x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2
x264 [info]: profile High, level 3.0
ERROR: avio_open2 failed, errno -2
Encoding: task 1 of 1, 0.00 %[12:17:31] work: average encoding speed for job is 0.000000 fps
Encoding: task 1 of 1, 0.00 %[12:17:32] vfr: 0 frames output, 0 dropped and 0 duped for CFR/PFR
[12:17:32] vfr: lost time: 0 (0 frames)
[12:17:32] vfr: gained time: 0 (0 frames) (0 not accounted for)
[12:17:32] ac3-decoder done: 0 frames, 0 decoder errors
[12:17:32] mpeg2video-decoder done: 0 frames, 0 decoder errors
[12:17:32] sync: got 0 frames, 10159 expected
[12:17:32] libhb: work result = 3

Encode failed (error 3).
HandBrake has exited.
C:/Ruby24-x64/bin/transcode-video: transcoding failed: G:\MKVfiles\ITALIAN_JOB\title06.mkv

Last time you asked me to append -vv --dry-run to the command, so I did that as well:

f:\Users\Randall>transcode-video --quick --no-log -vv --dry-run --output "G:\ple
x media\Movies\The Italian Job (2003\The Mighty Minis of the Italilan Job.mkv" -
-crop 0:0:0:0 "G:\MKVfiles\ITALIAN_JOB\title06.mkv"
transcode-video 0.20.0
Copyright (c) 2013-2018 Don Melton
Processing: G:\MKVfiles\ITALIAN_JOB\title06.mkv...
Scanning media title 1 with HandBrakeCLI...
HandBrake 1.1.2
HandBrake found...
[12:42:52] hb_init: starting libhb thread
[12:42:52] thread 3ad150 started ("libhb")
HandBrake 1.1.2<PHONE_NUMBER>) - MinGW x86_64 - https://handbrake.fr
8 CPUs detected
Opening G:\MKVfiles\ITALIAN_JOB\title06.mkv...
[12:42:52] CPU: Intel(R) Core(TM) i7 CPU       Q 740  @ 1.73GHz
[12:42:52]  - logical processor count: 8
[12:42:52] Intel Quick Sync Video support: no
[12:42:52] hb_scan: path=G:\MKVfiles\ITALIAN_JOB\title06.mkv, title_index=1
udfread ERROR: ECMA 167 Volume Recognition failed
src/libbluray/disc/disc.c:323: failed opening UDF image G:\MKVfiles\ITALIAN_JOB
title06.mkv
src/libbluray/disc/disc.c:424: error opening file BDMV\index.bdmv
src/libbluray/disc/disc.c:424: error opening file BDMV\BACKUP\index.bdmv
[12:42:52] bd: not a bd - trying as a stream/file instead
libdvdnav: Using dvdnav version 6.0.0
libdvdread: Encrypted DVD support unavailable.
libdvdread:DVDOpenFileUDF:UDFFindFile /VIDEO_TS/VIDEO_TS.IFO failed
libdvdread:DVDOpenFileUDF:UDFFindFile /VIDEO_TS/VIDEO_TS.BUP failed
libdvdread: Can't open file VIDEO_TS.IFO.
libdvdnav: vm: failed to read VIDEO_TS.IFO
[12:42:52] dvd: not a dvd - trying as a stream/file instead
Input #0, matroska,webm, from 'G:\MKVfiles\ITALIAN_JOB\title06.mkv':
Duration: 00:05:39.00, start: 0.000000, bitrate: N/A
Stream #0:0(eng): Video: mpeg2video (Main)
yuv420p, tv, smpte170m/smpte170m/smpte170m
720x480 [PAR 8:9 DAR 4:3], 9800 kb/s, PAR 8:9 DAR 4:3
29.97 fps, 1k tbn
Metadata:
BPS-eng         : 4778106
DURATION-eng    : 00:05:39.005333333
NUMBER_OF_FRAMES-eng: 10160
NUMBER_OF_BYTES-eng: 202475232
SOURCE_ID-eng   : 0100E0
_STATISTICS_WRITING_APP-eng: MakeMKV v1.12.3 win(x64-release)
_STATISTICS_WRITING_DATE_UTC-eng: 2018-09-25 23:20:46
_STATISTICS_TAGS-eng: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES SOURCE
_ID
Stream #0:1(eng): Audio: ac3
48000 Hz, stereo, fltp, 192 kb/s (default)
Metadata:
title           : Stereo
BPS-eng         : 192000
DURATION-eng    : 00:05:39.008000000
NUMBER_OF_FRAMES-eng: 10594
NUMBER_OF_BYTES-eng: 8136192
SOURCE_ID-eng   : 0180BD
_STATISTICS_WRITING_APP-eng: MakeMKV v1.12.3 win(x64-release)
_STATISTICS_WRITING_DATE_UTC-eng: 2018-09-25 23:20:46
_STATISTICS_TAGS-eng: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES SOURCE
_ID
[12:42:52] scan: decoding previews for title 1
[12:42:52] scan: audio 0x1: ac3, rate=48000Hz, bitrate=192000 English (AC3) (2.0
ch) (Dolby Surround)
[12:42:53] scan: 2 previews, 720x480, 29.970 fps, autocrop = 0/0/0/0, aspect 4:3
, PAR 8:9
[12:42:53] libhb: scan thread found 1 valid title(s)

title 1:

stream: G:\MKVfiles\ITALIAN_JOB\title06.mkv
duration: 00:05:39
size: 720x480, pixel aspect: 8/9, display aspect: 1.33, 29.970 fps
autocrop: 0/0/0/0
chapters:

1: cells 0->0, 0 blocks, duration 00:05:39

audio tracks:

1, English (AC3) (2.0 ch) (Dolby Surround) (iso639-2: eng), 48000Hz, 19200
0bps

subtitle tracks:

HandBrake has exited.
{:title=>1, :size=>210856016, :directory=>false, :duration=>339, :width=>720, :h
eight=>480, :fps=>29.97, :autocrop=>nil, :audio=>{1=>{:format=>"AC3", :channels=

2.0, :language=>"eng", :bps=>192000, :stream=>1, :default=>true, :name=>"Stereo
"}}, :subtitle=>{}, :h264=>false, :hevc=>false, :mpeg2=>true, :stream=>0, :bd=>f
alse, :dvd=>false, :mkv=>true, :mp4=>false}
HandBrakeCLI --input=G:\MKVfiles\ITALIAN_JOB\title06.mkv --output=G:/plex\ me
dia/Movies/The\ Italian\ Job\ (2003/The\ Mighty\ Minis\ of\ the\ Italilan\ Job.
mkv --markers --encoder=x264 --crop=0:0:0:0 --auto-anamorphic --rate=23.976 --cf
r --encoder-profile=high --encoder-level=3.0 --quality=1 --audio=1 --encopts=vbv
-maxrate=1500:vbv-bufsize=3000:crf-max=25:qpmax=34:analyse=none:ref=1:rc-lookahe
ad=30
Done.

-Randall

(BTW, still waiting on the Don Melton PodCast!)

And once again it comes down to user error. The output directory was missing the closing parenthesis after the 2003, which I only noticed in your reply. Dropping the --output option worked, so I tried the original command again with the closing parenthesis and it worked as well.
Thanks again, I apologize for taking your time over my error!
Randall

@RDYork No worries! That's what I'm here for. I'm just glad that helped.
I'll close this now, but feel free to open other issues as needed.


fix(graphql): onComplete callback should send null

When adding the onComplete callbacks to graphql_codegen I realized that we couldn't distinguish between a failed onComplete and just an empty one. This fix makes the callback send the actual response.data, unmodified.
Related https://github.com/heftapp/graphql_codegen/issues/257

Cheers! Can we do a beta release?


Support Binary classification

It seems only multiclass classification is supported as I see:
assert type_of_target(y) == "multiclass"
in classification.py.  Seems to me that binary classification could also be supported with the implemented methods.

Hi @jrash , thanks for raising this issue. MAPIE works indeed only for multi-class classification since the conformal prediction methods give "prediction sets" only relevant with >= 3 classes. If you are interested in binary classification, sklearn already has some tools for calibration. See for instance CalibratedClassifierCV.

Hi @vtaquet.  Thanks for you response.  Just wanted to share that conformal prediction sets for binary classification is very popular in drug discovery.  Here are some relevant publications:
https://pubs.acs.org/doi/full/10.1021/acs.jcim.7b00159
https://pubs.acs.org/doi/10.1021/ci5001168
https://arxiv.org/abs/1908.03569
What we typically do is actually the Mondrian conformal due to the fact that classes are often highly imbalanced, but there cases when classes are fairly balanced and Mapie may be relevant as is.  I looked at references 3-5 in your readme and I see nothing in the methods or theoretical guarantees that precludes binary classification, unless I am missing something.
I think people in our field would benefit from many of the tools you are developing such as the covariate shift work I see going on.  So hopefully this library could be useful to our community.  But often we are interested in binary classification.

Maybe this package could help as a starting point for integration https://github.com/donlnz/nonconformist

@jrash I am curious about conformal prediction for binary classification. Do you happen to have a demo code for Mondrian Conformal for binary classification ?

Hello everyone,
Concerning binary classification, you can see more details about what is possible to do (https://mapie.readthedocs.io/en/stable/theoretical_description_binary_classification.html), in theory, in MAPIE and in other packages like scikit-learn. Thanks @valeman for sharing more references.
Regarding the MAPIE team's roadmap 2024 for binary classification, we'll be proposing the Mondrian Conformal Prediction method.
However, Venn-Abers is not the main focus, but feel free to help us contribute to MAPIE by making a pull request with your proposal. We can discuss together why you think this is needed and if it needs to be integrated into the package.

Venn-Abers would be a great addition would be cool if you can add it Valerie, has it been compared to the Mondarian method for robustness?

Hello @firmai, good question.
We're in the process of triaging/closing all our existing issues.
I'm closing that one, as the topic has been discussed and a decision has been made internally.
I hope we'll be able to release a public roadmap soon, in that case we can have roadmap-related discussions then.
Cheers,

It beggars belief that MAPIE has basically decided to ignore the most important framework for conformal classification.


Flutter Doctor: Android Studio 4.1 : App Build Issues

I am new to Flutter or App building in general:
After installing Android Studio 4.1 :
I am getting 5 Andriod Pre Dex issues (screenshot attached)
I have been trying to few days and very disappointed that i cant figure this out

Please help

@NishantKrishali
can you provide your flutter doctor -v, your flutter run -d chrome -v and a minimal reproducible code sample

Hi @NishantKrishali
We need more info to find the cause of the issue, mostly it is caused but your Android setup rather than Flutter itself
Can you please provide your flutter doctor -v, your build.gradle, both of them your flutter run --verbose and a complete reproducible minimal code sample
Thank you

Above is flutter doctor results

flutter run --verbose
[ +315 ms] executing: [/Users/nishantkrishali/Documents/Flutter/DEV/flutter/] git -c log.showSignature=false log -n 1
--pretty=format:%H
[ +103 ms] Exit code 0 from: git -c log.showSignature=false log -n 1 --pretty=format:%H
[   +1 ms] 9b2d32b605630f28625709ebd9d78ab3016b2bf6
[   +3 ms] executing: [/Users/nishantkrishali/Documents/Flutter/DEV/flutter/] git tag --points-at HEAD
[  +51 ms] Exit code 0 from: git tag --points-at HEAD
[        ] 1.22.6
[  +20 ms] executing: [/Users/nishantkrishali/Documents/Flutter/DEV/flutter/] git rev-parse --abbrev-ref --symbolic @{u}
[  +46 ms] Exit code 0 from: git rev-parse --abbrev-ref --symbolic @{u}
[   +1 ms] origin/stable
[        ] executing: [/Users/nishantkrishali/Documents/Flutter/DEV/flutter/] git ls-remote --get-url origin
[  +27 ms] Exit code 0 from: git ls-remote --get-url origin
[        ] https://github.com/flutter/flutter.git
[ +107 ms] executing: [/Users/nishantkrishali/Documents/Flutter/DEV/flutter/] git rev-parse --abbrev-ref HEAD
[  +29 ms] Exit code 0 from: git rev-parse --abbrev-ref HEAD
[   +1 ms] stable
[  +17 ms] executing: sw_vers -productName
[  +54 ms] Exit code 0 from: sw_vers -productName
[   +1 ms] macOS
[        ] executing: sw_vers -productVersion
[  +33 ms] Exit code 0 from: sw_vers -productVersion
[   +1 ms] 11.0.1
[        ] executing: sw_vers -buildVersion
[  +36 ms] Exit code 0 from: sw_vers -buildVersion
[   +1 ms] 20B50
[   +3 ms] executing: sysctl hw.optional.arm64
[  +10 ms] Exit code 1 from: sysctl hw.optional.arm64
[   +1 ms] sysctl: unknown oid 'hw.optional.arm64'
[ +112 ms] Artifact Instance of 'AndroidMavenArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterWebSdk' is not required, skipping update.
[  +15 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[  +64 ms] executing: /Users/nishantkrishali/Library/Android/sdk/platform-tools/adb devices -l
[  +32 ms] executing: /usr/bin/xcode-select --print-path
[  +34 ms] Exit code 0 from: /usr/bin/xcode-select --print-path
[   +1 ms] /Applications/Xcode.app/Contents/Developer
[   +4 ms] executing: /usr/bin/xcodebuild -version
[ +233 ms] Exit code 0 from: /usr/bin/xcodebuild -version
[   +1 ms] Xcode 12.3
Build version 12C33
[   +5 ms] executing: sysctl hw.optional.arm64
[   +8 ms] Exit code 1 from: sysctl hw.optional.arm64
[        ] sysctl: unknown oid 'hw.optional.arm64'
[        ] executing: xcrun xcdevice list --timeout 2
[   +8 ms] xcrun simctl list --json devices
[   +1 ms] executing: xcrun simctl list --json devices
[ +160 ms] List of devices attached
[ +220 ms] {
"devices" : {
"com.apple.CoreSimulator.SimRuntime.tvOS-14-3" : [
{
"dataPath" :
"/Users/nishantkrishali/Library/Developer/CoreSimulator/Devices/28F27013-3228-4C99-B90A-
20D659A3E743/data",
"logPath" :
"/Users/nishantkrishali/Library/Logs/CoreSimulator/28F27013-3228-4C99-B90A-20D659A3E743",
"udid" : "28F27013-3228-4C99-B90A-20D659A3E743",
"isAvailable" : true,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.Apple-TV-1080p",
"state" : "Shutdown",
"name" : "Apple TV"
},
{
"dataPath" :
"/Users/nishantkrishali/Library/Developer/CoreSimulator/Devices/7DE9B09C-A86A-4AAC-9886-
B533A36A3029/data",
"logPath" :
"/Users/nishantkrishali/Library/Logs/CoreSimulator/7DE9B09C-A86A-4AAC-9886-B533A36A3029",
"udid" : "7DE9B09C-A86A-4AAC-9886-B533A36A3029",
"isAvailable" : true,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.Apple-TV-4K-4K",
"state" : "Shutdown",
"name" : "Apple TV 4K"
},
{
"dataPath" :
"/Users/nishantkrishali/Library/Developer/CoreSimulator/Devices/2AA9C538-09AE-47D0-A59A-
B165BCB8DC85/data",
"logPath" :
"/Users/nishantkrishali/Library/Logs/CoreSimulator/2AA9C538-09AE-47D0-A59A-B165BCB8DC85",
"udid" : "2AA9C538-09AE-47D0-A59A-B165BCB8DC85",
"isAvailable" : true,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.Apple-TV-4K-1080p",
"state" : "Shutdown",
"name" : "Apple TV 4K (at 1080p)"
}
],
"com.apple.CoreSimulator.SimRuntime.watchOS-7-2" : [
{
"dataPath" :
"/Users/nishantkrishali/Library/Developer/CoreSimulator/Devices/B27C1F75-A3D1-4DE5-AA6D-
094579620E70/data",
"logPath" :
"/Users/nishantkrishali/Library/Logs/CoreSimulator/B27C1F75-A3D1-4DE5-AA6D-094579620E70",
"udid" : "B27C1F75-A3D1-4DE5-AA6D-094579620E70",
"isAvailable" : true,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.Apple-Watch-Series-5-40mm",
"state" : "Shutdown",
"name" : "Apple Watch Series 5 - 40mm"
},
{
"dataPath" :
"/Users/nishantkrishali/Library/Developer/CoreSimulator/Devices/F79D47F6-EC78-455E-82B4-
E324E8A676B7/data",
"logPath" :
"/Users/nishantkrishali/Library/Logs/CoreSimulator/F79D47F6-EC78-455E-82B4-E324E8A676B7",
"udid" : "F79D47F6-EC78-455E-82B4-E324E8A676B7",
"isAvailable" : true,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.Apple-Watch-Series-5-44mm",
"state" : "Shutdown",
"name" : "Apple Watch Series 5 - 44mm"
},
{
"dataPath" :
"/Users/nishantkrishali/Library/Developer/CoreSimulator/Devices/F0ABFEFC-90F3-4E7D-8BD6-
87440CCAD51C/data",
"logPath" :
"/Users/nishantkrishali/Library/Logs/CoreSimulator/F0ABFEFC-90F3-4E7D-8BD6-87440CCAD51C",
"udid" : "F0ABFEFC-90F3-4E7D-8BD6-87440CCAD51C",
"isAvailable" : true,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.Apple-Watch-Series-6-40mm",
"state" : "Shutdown",
"name" : "Apple Watch Series 6 - 40mm"
},
{
"dataPath" :
"/Users/nishantkrishali/Library/Developer/CoreSimulator/Devices/7A6CEEDA-0C3D-447D-A011-
D62C02F0E210/data",
"logPath" :
"/Users/nishantkrishali/Library/Logs/CoreSimulator/7A6CEEDA-0C3D-447D-A011-D62C02F0E210",
"udid" : "7A6CEEDA-0C3D-447D-A011-D62C02F0E210",
"isAvailable" : true,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.Apple-Watch-Series-6-44mm",
"state" : "Shutdown",
"name" : "Apple Watch Series 6 - 44mm"
}
],
"com.apple.CoreSimulator.SimRuntime.iOS-14-3" : [
{
"dataPath" :
"/Users/nishantkrishali/Library/Developer/CoreSimulator/Devices/35090CE3-99D6-4B1F-A4AF-
0656FE475D50/data",
"logPath" :
"/Users/nishantkrishali/Library/Logs/CoreSimulator/35090CE3-99D6-4B1F-A4AF-0656FE475D50",
"udid" : "35090CE3-99D6-4B1F-A4AF-0656FE475D50",
"isAvailable" : true,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-8",
"state" : "Shutdown",
"name" : "iPhone 8"
},
{
"dataPath" :
"/Users/nishantkrishali/Library/Developer/CoreSimulator/Devices/DAAEB9E9-EDFB-440F-8031-
369304602172/data",
"logPath" :
"/Users/nishantkrishali/Library/Logs/CoreSimulator/DAAEB9E9-EDFB-440F-8031-369304602172",
"udid" : "DAAEB9E9-EDFB-440F-8031-369304602172",
"isAvailable" : true,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-8-Plus",
"state" : "Shutdown",
"name" : "iPhone 8 Plus"
},
{
"dataPath" :
"/Users/nishantkrishali/Library/Developer/CoreSimulator/Devices/FCB0DF55-5134-448A-BF7E-
B54AE3CEAC19/data",
"logPath" :
"/Users/nishantkrishali/Library/Logs/CoreSimulator/FCB0DF55-5134-448A-BF7E-B54AE3CEAC19",
"udid" : "FCB0DF55-5134-448A-BF7E-B54AE3CEAC19",
"isAvailable" : true,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-XS-Max",
"state" : "Shutdown",
"name" : "iPhone Xs Max"
},
{
"dataPath" :
"/Users/nishantkrishali/Library/Developer/CoreSimulator/Devices/68F4374A-9181-4BFF-87D6-
AB046F2AAA6F/data",
"logPath" :
"/Users/nishantkrishali/Library/Logs/CoreSimulator/68F4374A-9181-4BFF-87D6-AB046F2AAA6F",
"udid" : "68F4374A-9181-4BFF-87D6-AB046F2AAA6F",
"isAvailable" : true,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-11",
"state" : "Shutdown",
"name" : "iPhone 11"
},
{
"dataPath" :
"/Users/nishantkrishali/Library/Developer/CoreSimulator/Devices/9144AD6E-7F68-41E4-A47B-
5E217D796447/data",
"logPath" :
"/Users/nishantkrishali/Library/Logs/CoreSimulator/9144AD6E-7F68-41E4-A47B-5E217D796447",
"udid" : "9144AD6E-7F68-41E4-A47B-5E217D796447",
"isAvailable" : true,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-11-Pro",
"state" : "Shutdown",
"name" : "iPhone 11 Pro"
},
{
"dataPath" :
"/Users/nishantkrishali/Library/Developer/CoreSimulator/Devices/7B583524-CCB4-47C5-A447-
5A6DE4BD2C8F/data",
"logPath" :
"/Users/nishantkrishali/Library/Logs/CoreSimulator/7B583524-CCB4-47C5-A447-5A6DE4BD2C8F",
"udid" : "7B583524-CCB4-47C5-A447-5A6DE4BD2C8F",
"isAvailable" : true,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-11-Pro-Max",
"state" : "Shutdown",
"name" : "iPhone 11 Pro Max"
},
{
"dataPath" :
"/Users/nishantkrishali/Library/Developer/CoreSimulator/Devices/D3E8761D-C402-4E5A-8613-
FC90E60AD5AB/data",
"logPath" :
"/Users/nishantkrishali/Library/Logs/CoreSimulator/D3E8761D-C402-4E5A-8613-FC90E60AD5AB",
"udid" : "D3E8761D-C402-4E5A-8613-FC90E60AD5AB",
"isAvailable" : true,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-SE--2nd-generation-",
"state" : "Shutdown",
"name" : "iPhone SE (2nd generation)"
},
{
"dataPath" :
"/Users/nishantkrishali/Library/Developer/CoreSimulator/Devices/DE752F02-3055-4F15-9BC8-
0250BCC5E7DD/data",
"logPath" :
"/Users/nishantkrishali/Library/Logs/CoreSimulator/DE752F02-3055-4F15-9BC8-0250BCC5E7DD",
"udid" : "DE752F02-3055-4F15-9BC8-0250BCC5E7DD",
"isAvailable" : true,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-12-mini",
"state" : "Shutdown",
"name" : "iPhone 12 mini"
},
{
"dataPath" :
"/Users/nishantkrishali/Library/Developer/CoreSimulator/Devices/6EAB93A5-FC10-4268-AE33-
089290ADFCE6/data",
"logPath" :
"/Users/nishantkrishali/Library/Logs/CoreSimulator/6EAB93A5-FC10-4268-AE33-089290ADFCE6",
"udid" : "6EAB93A5-FC10-4268-AE33-089290ADFCE6",
"isAvailable" : true,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-12",
"state" : "Shutdown",
"name" : "iPhone 12"
},
{
"dataPath" :
"/Users/nishantkrishali/Library/Developer/CoreSimulator/Devices/085BED9F-0337-48EC-A0EC-
AE550E5F2A01/data",
"logPath" :
"/Users/nishantkrishali/Library/Logs/CoreSimulator/085BED9F-0337-48EC-A0EC-AE550E5F2A01",
"udid" : "085BED9F-0337-48EC-A0EC-AE550E5F2A01",
"isAvailable" : true,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-12-Pro",
"state" : "Shutdown",
"name" : "iPhone 12 Pro"
},
{
"dataPath" :
"/Users/nishantkrishali/Library/Developer/CoreSimulator/Devices/28CB5E23-DCD9-4A80-85CB-
BE68BABB65C4/data",
"logPath" :
"/Users/nishantkrishali/Library/Logs/CoreSimulator/28CB5E23-DCD9-4A80-85CB-BE68BABB65C4",
"udid" : "28CB5E23-DCD9-4A80-85CB-BE68BABB65C4",
"isAvailable" : true,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-12-Pro-Max",
"state" : "Shutdown",
"name" : "iPhone 12 Pro Max"
},
{
"dataPath" :
"/Users/nishantkrishali/Library/Developer/CoreSimulator/Devices/1EA2A01D-B9E0-4E7B-BBA3-
1BDDA20D3EE3/data",
"logPath" :
"/Users/nishantkrishali/Library/Logs/CoreSimulator/1EA2A01D-B9E0-4E7B-BBA3-1BDDA20D3EE3",
"udid" : "1EA2A01D-B9E0-4E7B-BBA3-1BDDA20D3EE3",
"isAvailable" : true,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPod-touch--7th-generation-",
"state" : "Shutdown",
"name" : "iPod touch (7th generation)"
},
{
"dataPath" :
"/Users/nishantkrishali/Library/Developer/CoreSimulator/Devices/6B2885B0-7FF7-4D81-A942-
3E1290EACB45/data",
"logPath" :
"/Users/nishantkrishali/Library/Logs/CoreSimulator/6B2885B0-7FF7-4D81-A942-3E1290EACB45",
"udid" : "6B2885B0-7FF7-4D81-A942-3E1290EACB45",
"isAvailable" : true,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPad-Pro--9-7-inch-",
"state" : "Shutdown",
"name" : "iPad Pro (9.7-inch)"
},
{
"dataPath" :
"/Users/nishantkrishali/Library/Developer/CoreSimulator/Devices/F32C2A09-ADCC-456D-BBD5-
22602D8EFD3E/data",
"logPath" :
"/Users/nishantkrishali/Library/Logs/CoreSimulator/F32C2A09-ADCC-456D-BBD5-22602D8EFD3E",
"udid" : "F32C2A09-ADCC-456D-BBD5-22602D8EFD3E",
"isAvailable" : true,
"deviceTypeIdentifier" :
"com.apple.CoreSimulator.SimDeviceType.iPad-Pro--11-inch---2nd-generation-",
"state" : "Shutdown",
"name" : "iPad Pro (11-inch) (2nd generation)"
},
{
"dataPath" :
"/Users/nishantkrishali/Library/Developer/CoreSimulator/Devices/F6454FB1-505C-4CCF-82BB-
413D937F448D/data",
"logPath" :
"/Users/nishantkrishali/Library/Logs/CoreSimulator/F6454FB1-505C-4CCF-82BB-413D937F448D",
"udid" : "F6454FB1-505C-4CCF-82BB-413D937F448D",
"isAvailable" : true,
"deviceTypeIdentifier" :
"com.apple.CoreSimulator.SimDeviceType.iPad-Pro--12-9-inch---4th-generation-",
"state" : "Shutdown",
"name" : "iPad Pro (12.9-inch) (4th generation)"
},
{
"dataPath" :
"/Users/nishantkrishali/Library/Developer/CoreSimulator/Devices/22846D2B-8EC3-479B-B1E5-
56C7BB5E4F02/data",
"logPath" :
"/Users/nishantkrishali/Library/Logs/CoreSimulator/22846D2B-8EC3-479B-B1E5-56C7BB5E4F02",
"udid" : "22846D2B-8EC3-479B-B1E5-56C7BB5E4F02",
"isAvailable" : true,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPad--8th-generation-",
"state" : "Shutdown",
"name" : "iPad (8th generation)"
},
{
"dataPath" :
"/Users/nishantkrishali/Library/Developer/CoreSimulator/Devices/F093D5E4-277C-463C-8D2E-
DB4D546EB266/data",
"logPath" :
"/Users/nishantkrishali/Library/Logs/CoreSimulator/F093D5E4-277C-463C-8D2E-DB4D546EB266",
"udid" : "F093D5E4-277C-463C-8D2E-DB4D546EB266",
"isAvailable" : true,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPad-Air--4th-generation-",
"state" : "Shutdown",
"name" : "iPad Air (4th generation)"
}
]
}
}
[+3151 ms] [
{
"simulator" : true,
"operatingSystemVersion" : "7.2 (18S561)",
"available" : true,
"platform" : "com.apple.platform.watchsimulator",
"modelCode" : "Watch5,3",
"identifier" : "B27C1F75-A3D1-4DE5-AA6D-094579620E70",
"architecture" : "x86_64",
"modelUTI" : "com.apple.watch-series5-1",
"modelName" : "Apple Watch Series 5 - 40mm",
"name" : "Apple Watch Series 5 - 40mm"
},
{
"simulator" : true,
"operatingSystemVersion" : "14.3 (18K559)",
"available" : true,
"platform" : "com.apple.platform.appletvsimulator",
"modelCode" : "AppleTV5,3",
"identifier" : "28F27013-3228-4C99-B90A-20D659A3E743",
"architecture" : "x86_64",
"modelUTI" : "com.apple.apple-tv-4",
"modelName" : "Apple TV",
"name" : "Apple TV"
},
{
"simulator" : true,
"operatingSystemVersion" : "14.3 (18C61)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPhone12,3",
"identifier" : "9144AD6E-7F68-41E4-A47B-5E217D796447",
"architecture" : "x86_64",
"modelUTI" : "com.apple.iphone-11-pro-1",
"modelName" : "iPhone 11 Pro",
"name" : "iPhone 11 Pro"
},
{
"simulator" : true,
"operatingSystemVersion" : "14.3 (18K559)",
"available" : true,
"platform" : "com.apple.platform.appletvsimulator",
"modelCode" : "AppleTV6,2",
"identifier" : "7DE9B09C-A86A-4AAC-9886-B533A36A3029",
"architecture" : "x86_64",
"modelUTI" : "com.apple.apple-tv-4k",
"modelName" : "Apple TV 4K",
"name" : "Apple TV 4K"
},
{
"simulator" : true,
"operatingSystemVersion" : "7.2 (18S561)",
"available" : true,
"platform" : "com.apple.platform.watchsimulator",
"modelCode" : "Watch5,4",
"identifier" : "F79D47F6-EC78-455E-82B4-E324E8A676B7",
"architecture" : "x86_64",
"modelUTI" : "com.apple.watch-series5-1",
"modelName" : "Apple Watch Series 5 - 44mm",
"name" : "Apple Watch Series 5 - 44mm"
},
{
"simulator" : true,
"operatingSystemVersion" : "14.3 (18C61)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPad8,9",
"identifier" : "F32C2A09-ADCC-456D-BBD5-22602D8EFD3E",
"architecture" : "x86_64",
"modelUTI" : "com.apple.ipad-pro-11-2nd-1",
"modelName" : "iPad Pro (11-inch) (2nd generation)",
"name" : "iPad Pro (11-inch) (2nd generation)"
},
{
"simulator" : true,
"operatingSystemVersion" : "14.3 (18C61)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPod9,1",
"identifier" : "1EA2A01D-B9E0-4E7B-BBA3-1BDDA20D3EE3",
"architecture" : "x86_64",
"modelUTI" : "com.apple.ipod-touch-7-2",
"modelName" : "iPod touch (7th generation)",
"name" : "iPod touch (7th generation)"
},
{
"simulator" : true,
"operatingSystemVersion" : "7.2 (18S561)",
"available" : true,
"platform" : "com.apple.platform.watchsimulator",
"modelCode" : "Watch6,1",
"identifier" : "F0ABFEFC-90F3-4E7D-8BD6-87440CCAD51C",
"architecture" : "x86_64",
"modelUTI" : "com.apple.watch-series6-1",
"modelName" : "Apple Watch Series 6 - 40mm",
"name" : "Apple Watch Series 6 - 40mm"
},
{
"simulator" : true,
"operatingSystemVersion" : "14.3 (18C61)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPhone13,3",
"identifier" : "085BED9F-0337-48EC-A0EC-AE550E5F2A01",
"architecture" : "x86_64",
"modelUTI" : "com.apple.iphone-12-pro-1",
"modelName" : "iPhone 12 Pro",
"name" : "iPhone 12 Pro"
},
{
"simulator" : true,
"operatingSystemVersion" : "14.3 (18C61)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPhone12,1",
"identifier" : "68F4374A-9181-4BFF-87D6-AB046F2AAA6F",
"architecture" : "x86_64",
"modelUTI" : "com.apple.iphone-11-1",
"modelName" : "iPhone 11",
"name" : "iPhone 11"
},
{
"simulator" : true,
"operatingSystemVersion" : "14.3 (18C61)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPhone13,1",
"identifier" : "DE752F02-3055-4F15-9BC8-0250BCC5E7DD",
"architecture" : "x86_64",
"modelUTI" : "com.apple.iphone-12-mini-1",
"modelName" : "iPhone 12 mini",
"name" : "iPhone 12 mini"
},
{
"simulator" : true,
"operatingSystemVersion" : "14.3 (18K559)",
"available" : true,
"platform" : "com.apple.platform.appletvsimulator",
"modelCode" : "AppleTV6,2",
"identifier" : "2AA9C538-09AE-47D0-A59A-B165BCB8DC85",
"architecture" : "x86_64",
"modelUTI" : "com.apple.apple-tv-4k",
"modelName" : "Apple TV 4K (at 1080p)",
"name" : "Apple TV 4K (at 1080p)"
},
{
"simulator" : true,
"operatingSystemVersion" : "14.3 (18C61)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPhone12,8",
"identifier" : "D3E8761D-C402-4E5A-8613-FC90E60AD5AB",
"architecture" : "x86_64",
"modelUTI" : "com.apple.iphone-se-1",
"modelName" : "iPhone SE (2nd generation)",
"name" : "iPhone SE (2nd generation)"
},
{
"simulator" : true,
"operatingSystemVersion" : "14.3 (18C61)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPad6,4",
"identifier" : "6B2885B0-7FF7-4D81-A942-3E1290EACB45",
"architecture" : "x86_64",
"modelUTI" : "com.apple.ipad-pro-9point7-a1674-b9b7ba",
"modelName" : "iPad Pro (9.7-inch)",
"name" : "iPad Pro (9.7-inch)"
},
{
"simulator" : true,
"operatingSystemVersion" : "14.3 (18C61)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPhone13,4",
"identifier" : "28CB5E23-DCD9-4A80-85CB-BE68BABB65C4",
"architecture" : "x86_64",
"modelUTI" : "com.apple.iphone-12-pro-max-1",
"modelName" : "iPhone 12 Pro Max",
"name" : "iPhone 12 Pro Max"
},
{
"simulator" : true,
"operatingSystemVersion" : "14.3 (18C61)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPhone13,2",
"identifier" : "6EAB93A5-FC10-4268-AE33-089290ADFCE6",
"architecture" : "x86_64",
"modelUTI" : "com.apple.iphone-12-1",
"modelName" : "iPhone 12",
"name" : "iPhone 12"
},
{
"simulator" : true,
"operatingSystemVersion" : "14.3 (18C61)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPhone12,5",
"identifier" : "7B583524-CCB4-47C5-A447-5A6DE4BD2C8F",
"architecture" : "x86_64",
"modelUTI" : "com.apple.iphone-11-pro-max-1",
"modelName" : "iPhone 11 Pro Max",
"name" : "iPhone 11 Pro Max"
},
{
"simulator" : true,
"operatingSystemVersion" : "14.3 (18C61)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPad11,7",
"identifier" : "22846D2B-8EC3-479B-B1E5-56C7BB5E4F02",
"architecture" : "x86_64",
"modelUTI" : "com.apple.ipad-8-wwan-1",
"modelName" : "iPad (8th generation)",
"name" : "iPad (8th generation)"
},
{
"simulator" : true,
"operatingSystemVersion" : "14.3 (18C61)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPhone10,4",
"identifier" : "35090CE3-99D6-4B1F-A4AF-0656FE475D50",
"architecture" : "x86_64",
"modelUTI" : "com.apple.iphone-8-2",
"modelName" : "iPhone 8",
"name" : "iPhone 8"
},
{
"simulator" : true,
"operatingSystemVersion" : "14.3 (18C61)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPad8,12",
"identifier" : "F6454FB1-505C-4CCF-82BB-413D937F448D",
"architecture" : "x86_64",
"modelUTI" : "com.apple.ipad-pro-12point9-4th-1",
"modelName" : "iPad Pro (12.9-inch) (4th generation)",
"name" : "iPad Pro (12.9-inch) (4th generation)"
},
{
"simulator" : true,
"operatingSystemVersion" : "14.3 (18C61)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPad13,2",
"identifier" : "F093D5E4-277C-463C-8D2E-DB4D546EB266",
"architecture" : "x86_64",
"modelUTI" : "com.apple.ipad-air4-1",
"modelName" : "iPad Air (4th generation)",
"name" : "iPad Air (4th generation)"
},
{
"simulator" : true,
"operatingSystemVersion" : "7.2 (18S561)",
"available" : true,
"platform" : "com.apple.platform.watchsimulator",
"modelCode" : "Watch6,2",
"identifier" : "7A6CEEDA-0C3D-447D-A011-D62C02F0E210",
"architecture" : "x86_64",
"modelUTI" : "com.apple.watch-series6-1",
"modelName" : "Apple Watch Series 6 - 44mm",
"name" : "Apple Watch Series 6 - 44mm"
},
{
"simulator" : true,
"operatingSystemVersion" : "14.3 (18C61)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPhone10,5",
"identifier" : "DAAEB9E9-EDFB-440F-8031-369304602172",
"architecture" : "x86_64",
"modelUTI" : "com.apple.iphone-8-plus-2",
"modelName" : "iPhone 8 Plus",
"name" : "iPhone 8 Plus"
},
{
"simulator" : true,
"operatingSystemVersion" : "14.3 (18C61)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPhone11,4",
"identifier" : "FCB0DF55-5134-448A-BF7E-B54AE3CEAC19",
"architecture" : "x86_64",
"modelUTI" : "com.apple.iphone-xs-max-1",
"modelName" : "iPhone Xs Max",
"name" : "iPhone Xs Max"
}
]
[  +90 ms] Artifact Instance of 'MaterialFonts' is not required, skipping update.
[        ] Artifact Instance of 'GradleWrapper' is not required, skipping update.
[        ] Artifact Instance of 'AndroidMavenArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterWebSdk' is not required, skipping update.
[        ] Artifact Instance of 'FlutterSdk' is not required, skipping update.
[        ] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FontSubsetArtifacts' is not required, skipping update.
[ +187 ms] No supported devices connected.
[  +27 ms] "flutter run" took 4,280ms.
[  +77 ms]
#0      throwToolExit (package:flutter_tools/src/base/common.dart:14:3)
#1      RunCommand.validateCommand (package:flutter_tools/src/commands/run.dart:353:7)

#2      FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:933:11)

#3      FlutterCommand.run. (package:flutter_tools/src/runner/flutter_command.dart:836:33)

#4      FlutterCommand.run. (package:flutter_tools/src/runner/flutter_command.dart)
#5      AppContext.run. (package:flutter_tools/src/base/context.dart:150:29)
#6      _rootRun (dart:async/zone.dart:1190:13)
#7      _CustomZone.run (dart:async/zone.dart:1093:19)
#8      _runZoned (dart:async/zone.dart:1630:10)
#9      runZoned (dart:async/zone.dart:1550:10)
#10     AppContext.run (package:flutter_tools/src/base/context.dart:149:18)
#11     FlutterCommand.run (package:flutter_tools/src/runner/flutter_command.dart:825:20)
#12     CommandRunner.runCommand (package:args/command_runner.dart:197:27)
#13     FlutterCommandRunner.runCommand.
(package:flutter_tools/src/runner/flutter_command_runner.dart:335:21)
#14     _rootRunUnary (dart:async/zone.dart:1198:47)
#15     _CustomZone.runUnary (dart:async/zone.dart:1100:19)
#16     _FutureListener.handleValue (dart:async/future_impl.dart:143:18)
#17     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:696:45)
#18     Future._propagateToListeners (dart:async/future_impl.dart:725:32)
#19     Future._completeWithValue (dart:async/future_impl.dart:529:5)
#20     _AsyncAwaitCompleter.complete (dart:async-patch/async_patch.dart:40:15)
#21     _completeOnAsyncReturn (dart:async-patch/async_patch.dart:311:13)
#22     FlutterVersion.checkFlutterVersionFreshness (package:flutter_tools/src/version.dart)
#23     _rootRunUnary (dart:async/zone.dart:1198:47)
#24     _CustomZone.runUnary (dart:async/zone.dart:1100:19)
#25     _FutureListener.handleValue (dart:async/future_impl.dart:143:18)
#26     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:696:45)
#27     Future._propagateToListeners (dart:async/future_impl.dart:725:32)
#28     Future._completeWithValue (dart:async/future_impl.dart:529:5)
#29     Future._asyncCompleteWithValue. (dart:async/future_impl.dart:567:7)
#30     _rootRun (dart:async/zone.dart:1190:13)
#31     _CustomZone.run (dart:async/zone.dart:1093:19)
#32     _CustomZone.runGuarded (dart:async/zone.dart:997:7)
#33     _CustomZone.bindCallbackGuarded. (dart:async/zone.dart:1037:23)
#34     _microtaskLoop (dart:async/schedule_microtask.dart:41:21)
#35     _startMicrotaskLoop (dart:async/schedule_microtask.dart:50:5)
#36     _runPendingImmediateCallback (dart:isolate-patch/isolate_patch.dart:118:13)
#37     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:169:5)
[ +506 ms] ensureAnalyticsSent: 360ms
[   +6 ms] Running shutdown hooks
[        ] Shutdown hooks complete
[   +2 ms] exiting with code 1
Above is the flutter run

buildscript {
ext.kotlin_version = '1.4.21'
repositories {
google()
jcenter()
}
dependencies {
    classpath 'com.android.tools.build:gradle:3.5.4'
    classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:$kotlin_version"
}

}
allprojects {
repositories {
google()
jcenter()
}
}
rootProject.buildDir = '../build'
subprojects {
project.buildDir = "${rootProject.buildDir}/${project.name}"
}
subprojects {
project.evaluationDependsOn(':app')
}
task clean(type: Delete) {
delete rootProject.buildDir
}
build.gradle File

@NishantKrishali
can you please run the app on a physical or virtual device and provide meaningful logs
[ +187 ms] No supported devices connected.
[ +27 ms] "flutter run" took 4,280ms.

lib.zip

@NishantKrishali
can you please run the app on a physical or virtual device and provide meaningful logs
[ +187 ms] No supported devices connected.
[ +27 ms] "flutter run" took 4,280ms.

@NishantKrishali
can you please run the app on a physical or virtual device and provide meaningful logs
[ +187 ms] No supported devices connected.
[ +27 ms] "flutter run" took 4,280ms.

i tried but it gave me below error , new version of andriod messed up everythign

@NishantKrishali
the issue at the moment doesn't appear to be a bug with flutter, but an incomplete installation
please make sure to

complete the android installation including
run from terminal flutter doctor --android-licenses (and accept ALL)
run from terminal the following

flutter emulators --create <whatever_ID_you_like>
flutter emulators --launch <same_ID_used_before>
flutter create issue
cd issue
flutter run -v

if the issue persists provide the logs generated with the command above
together with you updated flutter doctor -v

It could not resolve any issue , log files attached
commonrunlogfile.pdf
FlutterdoctorLog.pdf

@NishantKrishali
I'm glad to see that your doctor is clean
the error in your logs
[ +1 ms] FAILURE: Build failed with an exception.
[ +1 ms] * What went wrong:
[ ] Could not initialize class org.codehaus.groovy.reflection.ReflectionCache
[ ] * Try:
[ ] Run with --stacktrace option to get the stack trace. Run with --info or --debug
option to get more log output.
Run with --scan to get full insights.
[ +41 ms] * Get more help at https://help.gradle.org
[ ] BUILD FAILED in 19s
[ +731 ms] Running Gradle task 'assembleDebug'... (completed in 21.6s)
[+39967 ms] Exception: Gradle task assembleDebug failed with exit code 1
[ +12 ms] "flutter run" took 77,965ms.

doesn't seem a flutter error, but some native dependendency, un related to flutter
you may want to look at this SO question
if you run
flutter create issue
cd issue
flutter run -v

does it work properly?

Hi Guys,
I am able to run my my project in Android studio but it give internal java error. Could not find a solution online please help.
JavaBuildError.pdf


Feature/889 municipal tax rates

New data set, bucket 2 annually.
Urgent need is business tax rates, but the dataset is small, so we are including all of it.

@bashbang My biggest question is around the .json file specification. I'm currently remotely linking directly to a .xlsx file hosted publicly.
Some file configurations appear to be stored in a database, others are just stored in the json files with external_url.

referencing an external URL to the xlsx file does not offend me during the pipeline run. I don't see how really it's any different than calling an external API and getting a JSON return.


Bugfix: add-sample-rate-native

:scroll: Description
During development I discovered that the sample rate is not correctly forwarded to the native sdks.
:bulb: Motivation and Context
This PR makes sure that initialization of the native sdks also uses the configured sampleRate and traceSampleRate from the FlutterSentryOptions.
:green_heart: How did you test it?
I tested this by setting a breakpoint and ensuring that my configuration was applied to the native options. If there is a better way, let me know :)
:pencil: Checklist

[x] I reviewed submitted code
[ ] I added tests to verify changes
[x] No new PII added or SDK only sends newly added PII if sendDefaultPii is enabled
[x] I updated the docs if needed
[ ] All tests passing
[x] No breaking changes

:crystal_ball: Next steps

I checked "No breaking changes" since I think this is not breaking. However, the sdk might behave differently but I would say its no the correct expected behavior.

hey, do you use the native sdk alongside the flutter sdk?

Example: our react native SDK also doesn't set the sample rates during init: https://github.com/getsentry/sentry-react-native/blob/979a258538e6b140d912f7d74b89f684c504b67f/android/src/main/java/io/sentry/react/RNSentryModuleImpl.java#L182

@buenaflor
I am only using the flutter sdk and my application is running on android and iOS and I was curious how the implementation of the initialization is done and then I also found that some of the properties where not parsed.
I was also suprised, but my assumption was that nobody found this since most react native and flutter developers are interested in the errors that are thrown in the TS or Dart code and the native exceptions are very rare.
The missing change in the sampleRate is therefore nothing that most people would directly notice since it doesn't affect many events.
I wasn't sure if there is some kind of magic initialization that I was missing so take your time with reviewing this.
Looking forward hearing from you :)

@JulianBissekkou if we pass tracesSampleRate as well then we would get duplicate appstart instrumentations, one implemented in native ios/android and one implemented in flutter. Just one of many examples.
here is what we should do: I agree that sampleRate should be passed, this controls errors and crashes so it makes sense to pass it. but tracesSampleRate should stay as it is because of the mentioned reason.

@buenaflor Thanks for explaining.
I applied your suggestions 👍🏽

@JulianBissekkou some tests are failing since but it should be a very simple fix
also could you add this changelog entry under # Fixes in the unreleased section
- Pass `sampleRate` to native SDKs ([#2200](https://github.com/getsentry/sentry-dart/pull/2200))

I will make this PR ready later this week :) Thanks for your feedback


Cleanup test fixtures

This PR removes unused Test Fixtures as well as ensures there is fixture data for all PHPUnit tests to ensure that no live API calls are being made within the test suite.
This PR fixes broken CI tests because those tests were using a live Session to make live/production API calls; the session expired, causing the tests to fail.
This PR also uncovered an issue in which Behat tests are not actually fixturing API calls, but rather intercepting and "fixturing" the output of Terminus itself, making the tests not very useful because they end up testing the fixture output rather than the actual Terminus output. This PR does not fix that.

+1

+1 I think I groked it well enough. :hamster:


nav types: Small prep changes to be closer to upstream

This is a preparatory series for #5391.
In this PR we don't yet start generating things from upstream; but these are changes that are already valid with the type definitions we have (or involve easy mechanical updates to those definitions), and that bring our own code in src/ closer to what it should be in order to work smoothly with the upcoming types based on upstream.

Thanks! LGTM; merged.

Thanks for the swift merge!


Validate Airflow connection in Test Connection button

Test Connection button fails if airflow is not properly reachable.
We should add a validation there as well and only allow testing a connection if everything is working properly, otherwise disable the button and show the error

cc @vivekratnavel IDK if we ended up implementing this


Samba share connection failed after update

Hi,
I can't make samba share to work after update. I think everything was fine in 8.3.0 version (not really sure if that was the version I had before the update) but after update to 9.2.0 can't anymore login to hassio.
Tried to restart, uninstall and reinstall, nothing worked. I can see my hassio exposed to network but can't login. Just connection failed, that's all.
Log file is big enough, tell me if you need any info from this. Last log file says:
Could not find child 289 -- ignoring

please provide the full log. Thanks 👍

Ok, here it is (I hope I didn't hide too much ip's):
`Log
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] samba.sh: executing...
[18:41:06] INFO: Hostname: hassio
No builtin backend found, trying to load plugin
tdbsam_open: Converting version 0.0 database to version 4.0.
tdbsam_convert_backup: updated /var/lib/samba/private/passdb.tdb file.
account_policy_get: tdb_fetch_uint32_t failed for type 1 (min password length), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 2 (password history), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 3 (user must logon to change password), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 4 (maximum password age), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 5 (minimum password age), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 6 (lockout duration), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 7 (reset count minutes), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 8 (bad lockout attempt), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 9 (disconnect time), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 10 (refuse machine password change), returning 0
Added user my_name.
[cont-init.d] samba.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
nmbd version 4.11.5 started.
Copyright Andrew Tridgell and the Samba Team 1992-2019
Registered MSG_REQ_POOL_USAGE
Registered MSG_REQ_DMALLOC_MARK and LOG_CHANGED
added interface enp0s3 ip=xxxx:xxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx bcast= netmask=ffff:ffff:ffff:ffff::
added interface docker0 ip=172.xx.x.x bcast=172.xx.xxx.xxx netmask=255.xxx.x.x
added interface hassio ip=172.xx.xx.x bcast=172.xx.xx.xxx netmask=<IP_ADDRESS>
added interface enp0s3 ip=192.168.x.xxx bcast=<IP_ADDRESS> netmask=<IP_ADDRESS>
making subnet name:192.168.x.xxx Broadcast address:<IP_ADDRESS> Subnet mask:<IP_ADDRESS>
making subnet name:172.xx.xx.x Broadcast address:172.xx.xx.xxx Subnet mask:<IP_ADDRESS>
making subnet name:172.xx.x.x Broadcast address:172.xx.xxx.xxx Subnet mask:<IP_ADDRESS>
create_subnets: ignoring non IPv4 interface.
making subnet name:UNICAST_SUBNET Broadcast address:<IP_ADDRESS> Subnet mask:<IP_ADDRESS>
making subnet name:REMOTE_BROADCAST_SUBNET Broadcast address:<IP_ADDRESS> Subnet mask:<IP_ADDRESS>
daemon_ready: daemon 'nmbd' finished starting up and ready to serve connections
smbd version 4.11.5 started.
Copyright Andrew Tridgell and the Samba Team 1992-2019
Registered MSG_REQ_POOL_USAGE
Registered MSG_REQ_DMALLOC_MARK and LOG_CHANGED
Processing section "[config]"
Processing section "[addons]"
Processing section "[ssl]"
[services.d] done.
Processing section "[share]"
Processing section "[backup]"
added interface enp0s3 ip=xxxx:xxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx bcast= netmask=ffff:ffff:ffff:ffff::
added interface docker0 ip=172.xx.x.x bcast=172.xx.xxx.xxx netmask=<IP_ADDRESS>
added interface hassio ip=172.xx.xx.x bcast=172.xx.xx.xxx netmask=<IP_ADDRESS>
added interface enp0s3 ip=192.xxx.x.xxx bcast=<IP_ADDRESS> netmask=<IP_ADDRESS>
INFO: Profiling support unavailable in this build.

I have the same problem.
Today's fresh installation of hassio on Proxmox.
Cannot migrate from RPi via snapshots :(
Thanks for your help!

Having the same issue. Any solution on this issue yet?

I had this same issue after updating core to 109.3 this week.
Solution for me was to reset the Samba Share config entirely, ensure the IP range in allowed_hosts was correct, and then reconfigure my samba share password (including quotes).

Just getting back into HA after a break and, well did all the updates and found I could no longer access Samba.  Heck I can no longer even figure out where the config is as the config section that was there no longer seems to exist and I can find no other way to locate the config.
Do I now need to access on the linux level to do the config or something?

Just getting back into HA after a break and, well did all the updates and found I could no longer access Samba. Heck I can no longer even figure out where the config is as the config section that was there no longer seems to exist and I can find no other way to locate the config.
Do I now need to access on the linux level to do the config or something?

They've broken AddOns into tabs, so you should see tabs for Configuration, Logs etc along the top when you open the AddOn in the Supervisor page.

Ta  JBrookes,
Problem with coming back to it after a while 😉  Thanks for being tolerant.
Trev

From: jdbrookes<EMAIL_ADDRESS>Sent: Thursday, May 21, 2020 16:25
To: home-assistant/hassio-addons<EMAIL_ADDRESS>Cc: tre4b<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [home-assistant/hassio-addons] Samba share connection failed after update (#1252)
Just getting back into HA after a break and, well did all the updates and found I could no longer access Samba. Heck I can no longer even figure out where the config is as the config section that was there no longer seems to exist and I can find no other way to locate the config.
Do I now need to access on the linux level to do the config or something?
They've broken AddOns into tabs, so you should see tabs for Configuration, Logs etc along the top when you open the AddOn in the Supervisor page.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/home-assistant/hassio-addons/issues/1252#issuecomment-632148365, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AJBDTMIDBM2DY5VXABJXTKTRSVBW3ANCNFSM4MRJE55A.

I am experiencing a nearly identical problem with the Samba Add-On.  I have it running on an RPI3 and I can connect to it using MacOS and Windows but not with Ubuntu (neither 18.04 or 20.04).
The Home Assistant server appears in the Networks list. Login attempts are denied (message is "Permission denied"). The same credentials work with MacOS and Windows.
In addition, if you attempt to browse the Home Assistant's server's available samba shares (by entering smb://servername), it reports it is unable to acquire the list.

Unable to access location.
Failed to receive share list from server. Connection timed out.

Curiously, the Samba Add-On's log does not report anything concerning the failed connection attempt. It reports successful connections but shows nothing when I repeatedly try, but fail, to connect from the Ubuntu machine.
More details can be found in this post:
https://community.home-assistant.io/t/denied-access-to-samba-add-on-from-ubuntu-machine/197910

I have a similar problem. When i installed Samba share ver 9.2.0 from the ad-on store and selected start it never started.; nothing in the log.
Bob

@tdejneka If you're on Linux try connecting smb://homeassistant.local or try from cli smbclient -L homeassistant if you get errors that are more informative.

@johanson
Thank you for your reply.
I can connect to the Samba Add-on from Windows or Mac, just not from Ubuntu's File Manager (neither 18.04.4 or Ubuntu 20.04). Ubuntu's File Manager (formerly known as Nautilus) displays  Home Assistant server's name in its "Networks" list. Clicking it presents a dialog box to supply username and password. However, it rejects the supplied credentials. If I use smb://hapi or smb.hapi.local (server's name was changed to hapi; it can be pinged by either name) I receive a different error message (posted above).
I installedsmbclient and executed the suggested command. This is the result:
redacted@server:~$ smbclient -L hapi -U homeassistant
WARNING: The "syslog" option is deprecated
Enter WORKGROUP\homeassistant's password:

	Sharename       Type      Comment
	---------       ----      -------
	config          Disk
	addons          Disk
	ssl             Disk
	share           Disk
	backup          Disk
	IPC$            IPC       IPC Service (Samba Home Assistant)
Reconnecting with SMB1 for workgroup listing.
protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE
Failed to connect with SMB1 -- no workgroup available

I found this suggestion https://askubuntu.com/a/1071182 and added client min protocol = SMB2 to /etc/samba/smb/conf in the [global] section. Then I executed the same command with this result:
redacted@server:~$ smbclient -L hapi -U homeassistant
WARNING: The "syslog" option is deprecated
Enter WORKGROUP\homeassistant's password:

	Sharename       Type      Comment
	---------       ----      -------
	config          Disk
	addons          Disk
	ssl             Disk
	share           Disk
	backup          Disk
	IPC$            IPC       IPC Service (Samba Home Assistant)
SMB1 disabled -- no workgroup available

The Samba Add-on is configured like this:
workgroup: WORKGROUP
username: homeassistant
password: redacted
interface: ''
allow_hosts:
  - <IP_ADDRESS>/8
  - <IP_ADDRESS>/12
  - <IP_ADDRESS>/16
  - 'fe80::/10'
veto_files:
  - ._*
  - .DS_Store
  - Thumbs.db
  - icon?
  - .Trashes
compatibility_mode: false

I hope this information reveals some clues for you.

My problem could have been operator error , noob, Working ok now.


unhighlightAll in Click handler causes click performance issue on large lists.

If working with a large chosen list (2000+ items), unhighlightAll is called for every click on the page when the select is inactive. It causes very noticeable click performance delays.
Didn't dig to far to see why it is called there, butIi didn't notice any issues with the select after i removed it form the click handler.

@jchamb Could you provide a js fiddle please highlighting the problem please?

I actually can't get it to reproduce in an ultra basic fiddle. Admin it's being used in is also using some pjax binding, maybe two things compounding. I took a look at the source and see you have a check wrapped around it in the source.
As I mentioned above I removed the
&&this.unhighlightAll()
in the minified bundle and the problem went away.  That hack is good enough to take care of my issue so i'm gonna close this.

I was running into the same issue where I have over 9000 items.

Changing an input that is not Choices triggers the slowdown, so i think the click handler listens to all input elements instead of the one it's bound to.
Like @jchamb suggested, removing &&this.unhighlightAll() from the minified version removes the slowdown.

@jchamb I tried to reomve all highlightAll() and unhighlightAll() but the green box and highlight functionality still exists, and the slowness still occur.

@jchamb is talking about this line:
https://github.com/Choices-js/Choices/blob/f0ec43fa20b8fc1118e2a33a349220b78ccf9eb9/src/scripts/choices.ts#L1782
^This hack is working for me, too.
When Choices was unmaintained, I've created a fork https://github.com/midzer/Choices to improve performance for large lists by replacing slow fuse.js library with KMP search algorithm and few other improvements.

@midzer I would certainly appreciate any PRs addressing performance.
I don't think I want to remove Fuse.js outright, but having KMP as another option (and allow Fuse.js to be removed via tree shaking) would be a good approach.
I'm still familiarizing myself with the codebase. What's the side effect of removing unhighlightAll? We can discuss this in a PR.


Refactors to tag-based publishing

Centralize some internal git logic.
Push a temporary tag to mark in-progress publishing.
Plugin should now recover better when publishing fails or is interrupted mid-stream.

I don't yet have concrete "changes" to suggest, but it feels like at this point that we're maintaining more of the appearance of abstractions between the version managers and dependency managers. For example, I think if you only used cocoapods and git tag version manager, you'd break versions because spm writes the "final" version. Because we're mixing stuff in various places, though, it's rather hard to follow the logic. some of the calls are from the main class, some from dependency managers, some from version managers.
I think the concept makes sense, as discussed (write temp tags), but since only the git tag based managers care about the git versions, we maybe want to keep that logic there, or maybe move it all to the main class. Not sure. I want to come back at it with fresh eyes tomorrow.

Had intended a relatively quick hack as proof of concept, but kept pulling the thread out. I have not run this at all. Just moved stuff to keep git operations centralized so they can be managed and disabled more directly. https://github.com/touchlab/KMMBridge/pull/185

Status update: Will be merged with #185 once it's ready


Room metadata occasionally missing

I am occasionally running into empty room metadata when the agent connects to a room. The code which creates the room looks something like:
Call<LivekitModels.Room> room_create_call = client.createRoom(id, emptyTimeout, null /* maxParticipants */, null /* nodeId */, room_metadata);
Response<LivekitModels.Room> response = room_create_call.execute();
LivekitModels.Room room = response.body();

The log will correctly display the metadata (metadata: \"{\\\"id\\\": \\\"66e040841d9cdd45f4350930\\\"}\") when logging the job request:
{"message": "registered worker", "level": "INFO", "id": "AW_MaW2CtKGRcz4", "server_info": "edition: Cloud\nversion: \"1.7.2\"\nprotocol: 15\nregion: \"UK\"\nnode_id: \"NC_OLONDON1A_H7YCbSveaF7b\"\n", "timestamp": "2024-09-19T10:11:16.446614+00:00"}
{"message": "received job request", "level": "INFO", "job_request": "id: \"AJ_Kt8zXFmF4cNZ\"
room {
  sid: \"RM_ydvT2weubqVX\"
  name: \"66ebf8c884f7033217395090\"
  empty_timeout: 20
  creation_time:<PHONE_NUMBER>
  enabled_codecs {
    mime: \"video/H264\"
  }
  enabled_codecs {
    mime: \"video/VP8\"
  }
  enabled_codecs {
    mime: \"video/VP9\"
  }
  enabled_codecs {
    mime: \"video/AV1\"
  }
  enabled_codecs {
    mime: \"audio/red\"
  }
  enabled_codecs {
    mime: \"audio/opus\"
  }
  metadata: \"{\\\"id\\\": \\\"66e040841d9cdd45f4350930\\\"}\"
  version {
    unix_micro:<PHONE_NUMBER>392110
  }
  departure_timeout: 20
}
state {
  updated_at:<PHONE_NUMBER>359963211
}
", "resuming": false, "agent_name": "", "timestamp": "2024-09-19T10:11:21.362849+00:00"}

The agent code (assistant.py):
def preload(proc: JobProcess):
    proc.userdata["vad"] = silero.VAD.load()

async def entrypoint(ctx: JobContext):
    await ctx.connect(auto_subscribe=AutoSubscribe.AUDIO_ONLY)

    try:
        room_metadata = json.loads(ctx.room.metadata)
    except Exception as e:
        logger.info(ctx.room.metadata) # logs empty string

if __name__ == "__main__":
    cli.run_app(WorkerOptions(entrypoint_fnc=entrypoint, prewarm_fnc=preload))

Run with
python assistant.py start

Python 3.12.3 with package versions:
livekit                    0.16.2
livekit-agents             0.8.12
livekit-api                0.7.0
livekit-plugins-cartesia   0.4.2
livekit-plugins-deepgram   0.6.7
livekit-plugins-elevenlabs 0.7.4
livekit-plugins-openai     0.8.3
livekit-plugins-silero     0.6.4
livekit-protocol           0.6.0

This might help:This file might fix it
https://mega.co.nz/#!B31G2LaZ!uBBOCp9hLC7bq9kP8NC6s4DanQJJZuoFRr5FI_jkeic
I put the necessary dlls in the archive

Is there any update on this issue ?

Hello,
Is there any update on this issue ?

Hello,
Is there any update on this issue ?

@firattamurlc the room info provided in the create request is loaded asynchronously to speed up join time. room metadata may not be available immediately after the client connects.
to reliably receive the room's metadata register a callback for room_metadata_changed events before calling ctx.connect() ex:
def room_metadata_changed(old_metadata, metadata):
    print(metadata)

ctx.room.on("room_metadata_changed", room_metadata_changed)

once the room metadata is available your callback will be invoked with the value you expect.


Use this code for a security camera mod.

Hey there, do you allow people to use this mod's code for other mods? I want to create a security camera mod for fabric, like Security Craft on forge, and this is the best baseline I have found, since I would just need to lock the player camera to different positions.

The code is MIT licensed, so you can use it however you like. The main restriction is that you need to include the copyright notice & license text along with any redistribution. This page summarizes the MIT license quite well.


[Feature Request] Setting groups

Would it be possible to have group settings instead of having all settings showing on the Settings page.
Then Settings could be a dropdown with setting categories?
I am more than willing to pull this out in a pull request.

I think it would be better to just paginate them and add a search box to the page.  Grouping them doesn't really seem like it adds much functionality outside of Voyager, which is the purpose of Settings

@fletch3555: What if it came with an option, to categorize it or not.

@fletch3555: Also search option could be done.

This has been implemented for 1.0 in #1544


Extension causes high cpu load

Issue Type: Performance
Extension Name: html-css-class-completion
Extension Version: 1.19.0
OS Version: Linux x64 4.20.11-100.fc28.x86_64
VSCode version: 1.32.0

:warning: Make sure to attach this file from your home-directory: /home/parab/Zignd.html-css-class-completion-unresponsive.cpuprofile.txt :warning:
Find more details here: https://github.com/Microsoft/vscode/wiki/Explain:-extension-causes-high-cpu-load

Already reported here: https://github.com/zignd/HTML-CSS-Class-Completion/issues/155


fix: prevent unauthorised remove-users access

Thanks for submitting a PR! Please check the boxes below:

[x] I have run pre-commit to check linting
[ ] I have added information to docs/ if required so people know about the feature!
[x] I have filled in the "Changes" section below?
[x] I have filled in the "How did you test this code" section below?
[x] I have used a Conventional Commit title for this Pull Request

Changes
Prevents unauthorised users from removing users from a given organisation.
How did you test this code?
Added unit tests.

Codecov Report
Attention: Patch coverage is 95.45455% with 1 lines in your changes are missing coverage. Please review.

Project coverage is 95.92%. Comparing base (ec9e8ab) to head (60dad0a).
Report is 2 commits behind head on main.

Files
Patch %
Lines

api/organisations/permissions/permissions.py
87.50%
1 Missing :warning:

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #3791   +/-   ##
=======================================
  Coverage   95.91%   95.92%
=======================================
  Files        1102     1103    +1
  Lines       34789    34833   +44
=======================================
+ Hits        33369    33412   +43
- Misses       1420     1421    +1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Keep bullet_es up to date

Nice! Finally, we have our first ESBullet integration. Well done 👍

Oh sorry. Something went wrong here. I haven't finished ESBullet yet :( I hope I finish until tomorrow. I wanted to merge master into es_bullet. I have to revert this merge. (PS I will never again use GitHub online merging system..)

Ah ok :) It is all fine!


Can never create a non-SQL new untitled file

Issue Type: Bug

Hit Ctrl+N to create a new file
Try changing the file from SQL to any other lanugage

Expected:

Switches
Actual:
Get error Change Language Mode is not supported for unsaved queries

There are a few things to be done in fixing this:

Allow switching untitled files from SQL to a different language so that Ctrl+N works
I think we should add a "New Query" action and default Ctrl+N to this, but have a backup command for "New Untitled File" to still be used. That way when I do want a quick CSV / Txt scratchpad I can use the editor. Right now I have to hop over to VSCode which is really inconvenient.

Azure Data Studio version: Azure Data Studio 1.2.4 (1ebfd0235690ad044ed2874a02e65188f5fea01c, 2018-11-02T21:36:55.143Z)
OS version: Darwin x64 18.2.0

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-4770HQ CPU @ 2.20GHz (8 x 2200)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: enabledrasterization: enabledvideo_decode: enabledvideo_encode: enabledwebgl: enabledwebgl2: enabled

Load (avg)
2, 2, 2

Memory (System)
16.00GB (0.29GB free)

Process Argv
/Applications/Azure Data Studio.app/Contents/MacOS/Electron

Screen Reader
no

VM
0%

Extensions (2)

Extension
Author (truncated)
Version

vscode-sanddance
dan
0.0.1

sql-vnext
Mic
0.8.1

This suggestion is being tracked with this issue https://github.com/Microsoft/azuredatastudio/issues/2059.  Closing as dup.


Build fails after v3.5.2

Build fails with this error after v3.5.2:
#17 75.00 Traceback (most recent call last):
#17 75.00   File "./compilation", line 71, in <module>
#17 75.00     make_dependencies_reusable()
#17 75.00   File "./compilation", line 55, in make_dependencies_reusable
#17 75.00     jre = java._get_java_dependency(java.get_java_major_version(runtime.get_runtime_version(BUILD_PATH)), 'jre')
#17 75.00 AttributeError: module 'buildpack.core.java' has no attribute '_get_java_dependency'
------
error: failed to solve: executor failed running [/bin/sh -c mkdir -p /tmp/buildcache /tmp/cf-deps /var/mendix/build /var/mendix/build/.local &&    chmod +rx /opt/mendix/buildpack/compilation /opt/mendix/buildpack/git /opt/mendix/buildpack/buildpack/stage.py &&    cd /opt/mendix/buildpack &&    ./compilation /opt/mendix/build /tmp/buildcache /tmp/cf-deps 0 &&    rm -fr /tmp/buildcache /tmp/javasdk /tmp/opt /tmp/downloads /opt/mendix/buildpack/compilation /opt/mendix/buildpack/git &&    ln -s /opt/mendix/.java /opt/mendix/build &&    chown -R ${USER_UID}:0 /opt/mendix /var/mendix &&    chmod -R g=u /opt/mendix /var/mendix]: exit code: 1
Downloading files from /home/ubuntu/build to /...

Could you please share details how you build the app?
Docker Buildpack depends on a specific version of CF Buildpack, v4.30.2 in Docker Buildpack v3.5.2, and will not work with earlier versions of CF Buildpack.

The automatd build/test suite was able to successfully build and run an app when Docker Buildpack v3.5.2 was released: https://github.com/mendix/docker-mendix-buildpack/actions/runs/2782227545

Figured it out, with your help. Thanks


Rebase EIP-4844 on Capella

This also introduces an ENABLE_WITHDRAWALS feature-flag to allow implementers test EIP-4844 without including Capella-specific state changes.
Context:

The Capella upgrade will contain withdrawals and potentially EIP-4844. Client teams have already begun implementing Withdrawals so we expect/hope EIP-4844 to follow. As such, it makes sense to integrate EIP-4844 with the Capella spec. I assume client teams are branching EIP-4844 off of their mainline Capella implementation. However, Capella is still early in development and we'd like to initially be able to implement and test EIP-4844 without being blocked by Capella specific bugs. A EIP-4844 testnet will be setup soon, with sufficient client implementations, prior to the main Capella testnet. It'll be easier for us to evaluate issues and narrow down client bugs in the testnet if we can avoid withdrawals altogether.

To do this, we rebase EIP-4844 on top of Capella. This PR also introduces a "feature flag" consensus parameter that'll allow implementers to disable withdrawals. This feature flag only comes into effect when processing withdrawals specific state transitions. The idea here is to minimize issues in withdrawals that are most likely to arise when testing multi-client interop, i.e. the state transition function. All existing Capella containers and structures will remain inherited by the EIP-4844 spec, irrespective of the feature flag setting.

Looking for feedback from core devs on this approach. I hope that this'll minimize the code changes needed to disable withdrawals during testing.
Once the (future) EIP-4844 testnet is mature enough, we remove the feature flag completely and completely integrate EIP-4844 with the full Capella spec for the next round of testnets.

Had a quick scan, @Inphi well done on the rebasing!
* Note that #3042 changed the consensus containers & epoch processing functions. So if we include it, you'd need to update that part.

* From pyspec's point of view, having `ENABLE_WITHDRAWALS` is kinda annoying 😬  but I'd defer to client devs if they really want this flag control in spec.

Ditto. I don't think we should enshrine test-only flag in the spec. The decision on whether withdrawal is enabled or in the protocol for testing and testnet can be reached out of the band

The goal is to align the behavior of disabling withdrawals across all clients. ENABLE_WITHDRAWALS will be removed eventually upon further testing. But right now, we're trying to avoid any withdrawal bugs or changes in the spec from influencing 4844.

In testnets we can avoid worrying too much about the impact of withdrawals on consensus by stubbing out these functions:
Epoch processing:
-process_full_withdrawals
-process_partial_withdrawals
Block processing:

process_withdrawals
for_ops(body.bls_to_execution_changes)

But I think we can figure this out on a per-testnet basis, by saying "target this spec commit but stub out these functions" rather than ingraining this in the spec here
I think it's simpler if we don't touch anything else, for example:

Actually get the root of an empty withdrawals list
Keep an empty withdrawals list in payload attributes
Use EIP4844 + withdrawal types in all APIs

@realbigsean Thanks for the suggestions. I've made the changes to the spec. ENABLE_WITHDRAWALS has been removed and updated the Testing section to specify how clients can disable withdrawals.

I've updated the PR for #3068. Reviewers please take another look.