pin fairotag opencv version avoid breaking change in opencv-4.7

Description
fairotag is broken due to

contract breaking change introduced in opencv 4.7.
dependency of opencv does not have version pinned.
https://stackoverflow.com/questions/74964527/attributeerror-module-cv2-aruco-has-no-attribute-dictionary-get

I attempted to refactor into a version to be compatible with both versions but found it difficult. So I decided to pin the version first.
Test
/Users/tingfan/github/fairo/perception/fairotag
pip install -e .

Then

Type of change
Please check the options that are relevant.

[X] Bug fix (non-breaking change that fixes an issue)
[ ] Proposes a change (non-breaking change that isn't necessarily a bug)
[ ] Refactor
[ ] New feature (non-breaking change that adds a new functionality)
[ ] Breaking change (fix or feature that would break some existing functionality downstream)
[ ] This is a unit test
[ ] Documentation only change
[ ] Datasets Release
[ ] Models Release

Type of requested review

[ ] I want a thorough review of the implementation.
[ ] I want a high level review.
[ ] I want a deep design review.

Before and After
If this PR introduces a change or fixes a bug, please add before and after screenshots (if this is causes a UX change) or before and after examples(this could be plain text, videos etc ) to demonstrate the change.
If this PR introduces a new feature, please also add examples or screenshots demonstrating the feature.
Testing
Please describe the tests that you ran to verify your changes and how we can reproduce.
Checklist:

[ ] I have performed manual end-to-end testing of the feature in my environment.
[ ] I have added Docstrings and comments to the code.
[ ] I have made changes to existing documentation where needed.
[ ] I have added tests that show that the PR is functional.
[ ] New and existing unit tests pass locally with my changes.
[ ] I have added relevant collaborators to review the PR before merge.
[ ] [Polymetis only] I ran on hardware (1) all scripts in tests/scripts, (2) asv benchmarks.

retest this please


_write_to_stream() in the Download class forces decompression of the response even if "Accept-Encoding: gzip" was present in the request

Note for Googlers: This is the follow-up for an internal-only-visible issue at https://issuetracker.google.com/issues/115343385.
The Decompressive Transcoding docs for Cloud Storage [1] state that if an object's Content-Encoding is set to "gzip", we'll decompress the object when someone performs a media request to download it... unless 1 of 2 conditions are true -- one of which is if the requester sets the "Accept-Encoding: gzip" header on the request; then we'll serve the bytes in gzipped form.
This works as expected from the service, but when downloading a gzipped object using the Cloud Storage Python client library [2] (which uses this library), the bytes end up being written to the desired file as if they were served decoded.
It turns out, the bytes are being served gzipped-encoded, but this library is decoding them before writing them out to the desired file/stream.  I used this Python script to reproduce the issue:
import os
from google.cloud import storage

BUCKET='set your bucket name here'
GZIPPED_OBJECT='set your object name here'

os.environ['GOOGLE_APPLICATION_CREDENTIALS'] = 'path/to/json/keyfile.json'

# The object {GZIPPED_OBJECT} contains gzipped text, and I've set its
# Content-Encoding header to the value "gzip".
client = storage.Client()
bkt = client.get_bucket(BUCKET)
blob = bkt.get_blob(GZIPPED_OBJECT)

with open('/tmp/gzipped-from-cli-lib', 'w') as f:
  blob.download_to_file(f, client)

and before running it, I set a breakpoint directly before this line:
https://github.com/GoogleCloudPlatform/google-resumable-media-python/blob/50f4c4d22cdaea71c794639226e819197f11f555/google/resumable_media/requests/download.py#L121
...and if you get to that breakpoint and execute response.raw.read() in the debugger, it gives you the gzipped bytes for the object.  The problem comes from using iter_content() -- that method should NOT be used here if response.request.headers contains the ("accept-encoding", "gzip") pair, since it will explicitly decompress the stream, as mentioned in the warning box in the webdocs for the Requests library [3]:
"""
Note
An important note about using Response.iter_content versus Response.raw. Response.iter_content will automatically decode the gzip and deflate transfer-encodings. Response.raw is a raw stream of bytes – it does not transform the response content. If you really need access to the bytes as they were returned, use Response.raw.
"""
We should be checking for that header, and if it's present, manually chunking/writing the bytes to the stream instead of using iter_content().
[1] https://cloud.google.com/storage/docs/transcoding#decompressive_transcoding
[2] https://github.com/GoogleCloudPlatform/google-cloud-python/
[3] http://docs.python-requests.org/en/master/user/quickstart/#raw-response-content

This was something I was worried could happen but never adequately followed up, thanks @houglum. There was discussion in #35 and #36 (and related issues).

Thanks for the quick response!
I'd write up a fix for this, but I've got other higher-priority work lined up for the next couple of weeks.  And the bulk of my time on this would be spent looking through the tests and figuring out how to add a test for it :P
Is it likely this will be fixed anytime soon? If not, I can take a stab at it when I get the time.


Toyota: combine hybrid platforms

TODOs:

[ ] Highlander Hybrid TSS-P missing DSU (probably just never added, but we can)
[ ] Engine diffs (different addresses, should be added to non_essential_ecus)

[x] C-HR
[x] C-HR TSS2
[ ] Highlander
[ ] Lexus RX
[x] Camry
[ ] Lexus NX

[x] ABS missing on Alphard ICE
[ ] Remove hybrid ECU from RAV4 2023

Torque params look fine to merge:

Platforms where any torque param error is over 0.1 abs diff.
  TOYOTA HIGHLANDER 2017 -> TOYOTA HIGHLANDER HYBRID 2018
Factor:            1.870 -> 1.752 (-6.29% change)
Measured:          1.626 -> 1.643 (1.05% change)
Friction:          0.175 -> 0.145 (-17.30% change)

           LEXUS RX 2016 -> LEXUS RX HYBRID 2017
Factor:            1.588 -> 1.698 (6.98% change)
Measured:          1.043 -> 1.321 (26.70% change)
Friction:          0.213 -> 0.182 (-14.67% change)

       TOYOTA CAMRY 2018 -> TOYOTA CAMRY HYBRID 2018
Factor:            2.117 -> 1.996 (-5.71% change)
Measured:          1.716 -> 1.800 (4.90% change)
Friction:          0.105 -> 0.113 (7.01% change)

       TOYOTA CAMRY 2021 -> TOYOTA CAMRY HYBRID 2021
Factor:            2.446 -> 2.264 (-7.46% change)
Measured:          2.348 -> 2.390 (1.81% change)
Friction:          0.122 -> 0.115 (-5.23% change)

TOYOTA COROLLA TSS2 2019 -> TOYOTA COROLLA HYBRID TSS2 2019
Factor:            2.074 -> 1.908 (-8.02% change)
Measured:          1.926 -> 1.812 (-5.92% change)
Friction:          0.169 -> 0.223 (31.75% change)

  TOYOTA HIGHLANDER 2020 -> TOYOTA HIGHLANDER HYBRID 2020
Factor:            2.022 -> 1.901 (-5.99% change)
Measured:          1.618 -> 2.104 (30.01% change)
Friction:          0.146 -> 0.144 (-1.00% change)

        TOYOTA RAV4 2017 -> TOYOTA RAV4 HYBRID 2017
Factor:            2.086 -> 1.980 (-5.09% change)
Measured:          2.214 -> 1.750 (-20.95% change)
Friction:          0.133 -> 0.146 (9.67% change)

        TOYOTA RAV4 2019 -> TOYOTA RAV4 HYBRID 2019
Factor:            2.331 -> 2.227 (-4.47% change)
Measured:          2.099 -> 2.075 (-1.17% change)
Friction:          0.130 -> 0.144 (10.78% change)

           LEXUS ES 2019 -> LEXUS ES HYBRID 2019
Factor:            1.936 -> 2.136 (10.32% change)
Measured:          2.135 -> 1.863 (-12.72% change)
Friction:          0.093 -> 0.110 (17.32% change)

           LEXUS NX 2018 -> LEXUS NX HYBRID 2018
Factor:            2.303 -> 2.403 (4.34% change)
Measured:          2.138 -> 1.808 (-15.44% change)
Friction:          0.150 -> 0.153 (2.42% change)

           LEXUS RX 2020 -> LEXUS RX HYBRID 2020
Factor:            1.523 -> 1.552 (1.93% change)
Measured:          1.431 -> 1.255 (-12.29% change)
Friction:          0.164 -> 0.222 (35.33% change)

Going to start with TSS2 only here since there are no feature differences: https://github.com/commaai/openpilot/pull/30194


pam_google_authenticator.so on debian 8 never prompts - configs correct

I've been trying to get the google auth  to work on debian 8 with no luck.
I've followed various tutorials exactly with no luck.
Below are my auth.log sample outputs, my sshd_config, and my pam.d/sshd config
pam
# PAM configuration for the Secure Shell service

# Standard Un*x authentication.
@include common-auth

# Disallow non-root logins when /etc/nologin exists.
account    required     pam_nologin.so

# Uncomment and edit /etc/security/access.conf if you need to set complex
# access limits that are hard to express in sshd_config.
# account  required     pam_access.so

# Standard Un*x authorization.
@include common-account

# SELinux needs to be the first session rule.  This ensures that any
# lingering context has been cleared.  Without this it is possible that a
# module could execute code in the wrong domain.
session [success=ok ignore=ignore module_unknown=ignore default=bad]        pam_selinux.so close

auth required /usr/local/lib/security/pam_google_authenticator.so
# Set the loginuid process attribute.
session    required     pam_loginuid.so

# Create a new session keyring.
session    optional     pam_keyinit.so force revoke

# Standard Un*x session setup and teardown.
@include common-session

# Print the message of the day upon successful login.
# This includes a dynamically generated part from /run/motd.dynamic
# and a static (admin-editable) part from /etc/motd.
session    optional     pam_motd.so  motd=/run/motd.dynamic
session    optional     pam_motd.so noupdate

# Print the status of the user's mailbox upon successful login.
session    optional     pam_mail.so standard noenv # [1]

# Set up user limits from /etc/security/limits.conf.
session    required     pam_limits.so

# Read environment variables from /etc/environment and
# /etc/security/pam_env.conf.
session    required     pam_env.so # [1]

# In Debian 4.0 (etch), locale-related environment variables were moved to
# /etc/default/locale, so read that as well.
session    required     pam_env.so user_readenv=1 envfile=/etc/default/locale

# SELinux needs to intervene at login time to ensure that the process starts
# in the proper default security context.  Only sessions which are intended
# to run in the user's context should be run after this.
session [success=ok ignore=ignore module_unknown=ignore default=bad]        pam_selinux.so open

# Standard Un*x password updating.
@include common-password

sshd_config
# Package generated configuration file
# See the sshd_config(5) manpage for details

# What ports, IPs and protocols we listen for
Port 22
# Use these options to restrict which interfaces/protocols sshd will bind to
#ListenAddress ::
#ListenAddress <IP_ADDRESS>
Protocol 2
# HostKeys for protocol version 2
HostKey /etc/ssh/ssh_host_rsa_key
HostKey /etc/ssh/ssh_host_dsa_key
HostKey /etc/ssh/ssh_host_ecdsa_key
HostKey /etc/ssh/ssh_host_ed25519_key
#Privilege Separation is turned on for security
UsePrivilegeSeparation yes

# Lifetime and size of ephemeral version 1 server key
KeyRegenerationInterval 3600
ServerKeyBits 1024

# Logging
SyslogFacility AUTH
LogLevel INFO

# Authentication:
LoginGraceTime 120
PermitRootLogin no
StrictModes yes

RSAAuthentication yes
PubkeyAuthentication yes
#AuthorizedKeysFile     %h/.ssh/authorized_keys

# Don't read the user's ~/.rhosts and ~/.shosts files
IgnoreRhosts yes
# For this to work you will also need host keys in /etc/ssh_known_hosts
RhostsRSAAuthentication no
# similar for protocol version 2
HostbasedAuthentication no
# Uncomment if you don't trust ~/.ssh/known_hosts for RhostsRSAAuthentication
#IgnoreUserKnownHosts yes

# To enable empty passwords, change to yes (NOT RECOMMENDED)
PermitEmptyPasswords no

# Change to yes to enable challenge-response passwords (beware issues with
# some PAM modules and threads)
ChallengeResponseAuthentication yes

# Change to no to disable tunnelled clear text passwords
#PasswordAuthentication yes

# Kerberos options
#KerberosAuthentication no
#KerberosGetAFSToken no
#KerberosOrLocalPasswd yes
#KerberosTicketCleanup yes

# GSSAPI options
#GSSAPIAuthentication no
#GSSAPICleanupCredentials yes

X11Forwarding yes
X11DisplayOffset 10
PrintMotd no
PrintLastLog yes
TCPKeepAlive yes
#UseLogin no

#MaxStartups 10:30:60
#Banner /etc/issue.net

# Allow client to pass locale environment variables
AcceptEnv LANG LC_*

Subsystem sftp /usr/lib/openssh/sftp-server

# Set this to 'yes' to enable PAM authentication, account processing,
# and session processing. If this is enabled, PAM authentication will
# be allowed through the ChallengeResponseAuthentication and
# PasswordAuthentication.  Depending on your PAM configuration,
# PAM authentication via ChallengeResponseAuthentication may bypass
# the setting of "PermitRootLogin without-password".
# If you just want the PAM account and session checks to run without
# PAM authentication, then enable this but set PasswordAuthentication
# and ChallengeResponseAuthentication to 'no'.
UsePAM yes

sample output
Jun 29 20:36:58 calypso sshd[5755]: Accepted publickey for serubin from --- port 65306 ssh2: RSA  ---
Jun 29 20:36:58 calypso sshd[5755]: pam_unix(sshd:session): session opened for user serubin by (uid=0)

Are there any other logs I can look at for further errors? Any ideas are appreciated.

You're using public key auth, so it never touches PAM for auth, only for session.
Newer OpenSSH adds "AuthenticationMethods" (http://manpages.ubuntu.com/manpages/trusty/en/man5/sshd_config.5.html) which allows you to require keys and then PAM auth, but note that for your current config, that would mean key -> password -> TOTP.

Oh Brilliant. Thanks for the info!!


UI for editing named parameters

On any page displaying a custom query that includes named parameters, we should show HTML form fields for editing those parameters.
Eg the breed parameter on https://australian-dogs.now.sh/australian-dogs-3ba9628?sql=select+name%2C+count(*)+as+n+from+(

select+upper("Animal+name")+as+name+from+[Adelaide-City-Council-dog-registrations-2013]+where+Breed+like+%3Abreed

union+all

select+upper(Animal_Name)+as+name+from+[Adelaide-City-Council-dog-registrations-2014]+where+Breed_Description+like+%3Abreed

union+all+

select+upper(Animal_Name)+as+name+from+[Adelaide-City-Council-dog-registrations-2015]+where+Breed_Description+like+%3Abreed

union+all

select+upper("AnimalName")+as+name+from+[City-of-Port-Adelaide-Enfield-Dog_Registrations_2016]+where+AnimalBreed+like+%3Abreed

union+all

select+upper("Animal+Name")+as+name+from+[Mitcham-dog-registrations-2015]+where+Breed+like+%3Abreed

union+all

select+upper("DOG_NAME")+as+name+from+[burnside-dog-registrations-2015]+where+DOG_BREED+like+%3Abreed

union+all+

select+upper("Animal_Name")+as+name+from+[city-of-playford-2015-dog-registration]+where+Breed_Description+like+%3Abreed

union+all

select+upper("Animal+Name")+as+name+from+[city-of-prospect-dog-registration-details-2016]+where"Breed+Description"+like+%3Abreed

)+group+by+name+order+by+n+desc%3B&breed=pug

Demo: https://australian-dogs.now.sh/australian-dogs-3ba9628?sql=select+name%2C+count(*)+as+n+from+(

select+upper("Animal+name")+as+name+from+[Adelaide-City-Council-dog-registrations-2013]+where+Breed+like+%3Abreed

union+all

select+upper(Animal_Name)+as+name+from+[Adelaide-City-Council-dog-registrations-2014]+where+Breed_Description+like+%3Abreed

union+all+

select+upper(Animal_Name)+as+name+from+[Adelaide-City-Council-dog-registrations-2015]+where+Breed_Description+like+%3Abreed

union+all

select+upper("AnimalName")+as+name+from+[City-of-Port-Adelaide-Enfield-Dog_Registrations_2016]+where+AnimalBreed+like+%3Abreed

union+all

select+upper("Animal+Name")+as+name+from+[Mitcham-dog-registrations-2015]+where+Breed+like+%3Abreed

union+all

select+upper("DOG_NAME")+as+name+from+[burnside-dog-registrations-2015]+where+DOG_BREED+like+%3Abreed

union+all+

select+upper("Animal_Name")+as+name+from+[city-of-playford-2015-dog-registration]+where+Breed_Description+like+%3Abreed

union+all

select+upper("Animal+Name")+as+name+from+[city-of-prospect-dog-registration-details-2016]+where"Breed+Description"+like+%3Abreed

)+group+by+name+order+by+n+desc%3B&breed=chihuahua

Another demo - this time it lets you search by name and see the most popular breeds with that name: https://australian-dogs.now.sh/australian-dogs-3ba9628?sql=select+breed%2C+count(*)+as+n+from+(

select+upper("Breed")+as+breed+from+[Adelaide-City-Council-dog-registrations-2013]+where+"Animal+name"+like+%3Aname

union+all

select+upper("Breed_Description")+as+breed+from+[Adelaide-City-Council-dog-registrations-2014]+where+"Animal_Name"+like+%3Aname

union+all+

select+upper("Breed_Description")+as+breed+from+[Adelaide-City-Council-dog-registrations-2015]+where+"Animal_Name"+like+%3Aname

union+all

select+upper("AnimalBreed")+as+breed+from+[City-of-Port-Adelaide-Enfield-Dog_Registrations_2016]+where+"AnimalName"+like+%3Aname

union+all

select+upper("Breed")+as+breed+from+[Mitcham-dog-registrations-2015]+where+"Animal+Name"+like+%3Aname

union+all

select+upper("DOG_BREED")+as+breed+from+[burnside-dog-registrations-2015]+where+"DOG_NAME"+like+%3Aname

union+all+

select+upper("Breed_Description")+as+breed+from+[city-of-playford-2015-dog-registration]+where+"Animal_Name"+like+%3Aname

union+all

select+upper("Breed+Description")+as+breed+from+[city-of-prospect-dog-registration-details-2016]+where+"Animal+Name"+like+%3Aname

)+group+by+breed+order+by+n+desc%3B&name=rex


Bintray2

@densh I'm on it ;-). I'm a bit stuck with caching issue running the test. I should be done soon ;-).

Great this one passes!
I suggest to tag this 0.1.0 and re-release on Bintray.
I bumped Scala.js from 0.6.13 to 0.6.14

just removed the resolver :)

It look like removing the resolver does not work for sbt-scala-native. I sent an email to Bintray about this.

curl -vvv https://dl.bintray.com/scala-native/sbt-plugins/org.scala-native/sbt-scala-native/scala_2.10/sbt_0.13/0.1.0/ivys/ivy.xml our repository works
curl -vvv https://dl.bintray.com/sbt/sbt-plugin-releases/org.scala-native/sbt-scala-native/scala_2.10/sbt_0.13/0.1.0/ivys/ivy.xml sbt/sbt-plugins-releases does not work
curl -vvv https://dl.bintray.com/sbt/sbt-plugin-releases/org.scala-native/sbt-crossproject/scala_2.10/sbt_0.13/0.1.0/ivys/ivy.xml sbt/sbt-plugins-releases works for sbt-crossproject

@MasseGuillaume Is there a still a problem here? I was able to resolve all the things without extra resolvers  for my demo game build after nuking ivy cache completely.

@densh restarting the build. The issue above should be fixed

@densh Great the ci pass on linux!

Fantastic work, LGTM!


Hide implementation details from library users

OkHttp3 and Gson leak through the client-side API. Check if really necessary and change if needed. Leaking details to the library users makes it difficult to change implementation details without breaking the API.

For some progress here, I have a patch at https://github.com/bocops/mastodon4j/tree/patch_mastodonclient_1 that changes the GET/DELETE/PATCH/PUT methods in MastodonClient to mostly accept Parameter lists instead of having to expose OkHttp's RequestBody.
Should this be added to main directly, or do we want to have a separate branch for that?

Hello @bocops, maybe we can start using feature branches for issues in general, and create PR's for merging them into master when they are ready? Would make reviewing code easier, right?

@bocops : Looking at the MastodonClient.Builder()signature, I think we could also get of the Gson() instance that is passed every time the Builder(...) is called. IMHO, we could remove the Gson parameter entirely from the method signature, as we always pass the same object. I do not think that a library user should ever be able to tinker with the serialization/deserialization logic we're relying on. Do you share that opinion?

Definitely, we shouldn't expose implementation details to users like that, the Gson() instance in each Builder call should be removed and I can deal with that in my upcoming revised PR.
I think we can go one step further. Currently, basically every API method looks like this:
    fun getAccount(accountId: Long): MastodonRequest<Account> {
        return MastodonRequest(
            { client.get("api/v1/accounts/$accountId") },
            { client.getSerializer().fromJson(it, Account::class.java) }
        )
    }

with the Gson instance being exposed via MastodonClient.getSerializer(). It is probably cleaner to change this into something like a call to client.getMastodonRequest(...), which would deal with the necessary serialization in our MastodonClient instead. I would like to do that in a separate PR later, because the one I'm working on already deals with #48 and #49 and would become too massive otherwise.

Yes, sounds good to me. Classes like Accountprovide the methods for calling the API endpoints (like now) but deserialization is moved into MastodonClient. Doing so, we can save quite some lines of code I guess. Yes, let's do this in a separate issue/PR then. Thanks for pointing out! 😀

Reposted the above as separate issue #51.


Passing "Empty" Values to Functions with Arguments - tests still pass

Challenge Passing Values to Functions with Arguments
 has an issue.
User Agent is: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.
My code:

// Example
function ourFunctionWithArgs(a, b) {
  console.log(a - b);
}
ourFunctionWithArgs(10, 5); // Outputs 5

// Only change code below this line.
function functionWithArgs (word1, word2){
  console.log(word1 + word2);
}

functionWithArgs();

Tests are passing when no values are passed into function, variable/parameter name is of no affect

@JoeEarly You don't have to call each test yourself, the test functions are called one after the other when you click "Run Tests".

@JoeEarly
Thank you for reporting this issue.
This is a standard message notifying you that this issue seems to be a request for help. Instead of asking for help here, please click the "Help" button on the challenge on freeCodeCamp, which will take you to the help chatroom for that specific challenge. You can also view our full list of official chatrooms.
If you think I'm wrong in closing this issue, please reopen it and add further clarification. Thank you, and happy coding.


Move 'change password' form to sidebar

Currently the 'change password' form (for non-openID users) is part of the the normal 'edit' view of user profiles.
It can be moved to the sidebar to unclutter the main content.

As a first step, moved to sidebar in 'edit' view.


Is it able to add a 'download' button ?

Some of the blueprints gen by it is too huge and difficult to copy to clipboard.

Sure :) However, I don't know when I will have the time to implement it.


change relevant parts of the map to match inverted day/night colors

show map in dark grey (original) during the day to be able to see the sensor colors clearly
show map brighter during the night to better distinguish sensor colors (rather black probably)

that means #333333 is the day color and #000000 the night color in the background?

the default night color should be what the default is right now.
for the I would invert it I guess. something to play with

the detection is added. but we need to define the colors.
now on day-time bg: #333333, none eu: #3d3d3d, eu: #515151 and hover: steelblue.

I found it works best the way it is.


Use latest version of heroics

@camelmasa Can you test this?

I'll review it 😃

@rramsden LGTM 👍  It works for me.

@rramsden I merged this. Could you push to rubygems ❓


Feature/styles

Started removing bootstrap components - bootstrap is quite limiting
Added sass command to watch changes
tidy up UI
Added permalinks to result page headings.

Permalinks not quite working yet -- if hosted on a server, the links will 404 after page reload.
We should merge this anyway

Good point, Okay I'll have it build pages for this too.


Write details on running scale tests

https://mesosphere.atlassian.net/wiki/display/PRODUCT/Marathon+Scale+Tests

Thanks for the documentation.


Fix Integration test

Coverage increased (+0.04%) to 75.584% when pulling d454ce9de169fd9db54521e4a1a707b1a668ae44 on asifdxtreme:master into 2cd3d2204fe2476413fdc9d1c2a75dd52200adc3 on ServiceComb:master.

Codecov Report

Merging #28 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #28   +/-   ##
=======================================
  Coverage   71.08%   71.08%
=======================================
  Files           8        8
  Lines        3075     3075
=======================================
  Hits         2186     2186
  Misses        670      670
  Partials      219      219

Continue to review full report at Codecov.

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

Coverage increased (+0.1%) to 75.673% when pulling 471cd6b4e36337cf2bc7a8918a2ec0f58c8626cb on asifdxtreme:master into 2cd3d2204fe2476413fdc9d1c2a75dd52200adc3 on ServiceComb:master.


Vickel: Watch coinfomania(?!.com)

Vickel requests the watch of the watch_keyword coinfomania(?!\.com). See the MS search here and the Stack Exchange search in text, in URLs, and in code.

Approved by Jeff Schaller in Charcoal HQ

coinfomania(?!\.com) has been seen in 1 true positive, 0 false positives, and 0 NAAs.


getInboxFromActorProfile fails when remote instance requires HTTP signature on GET

I tried following my postmarks user from my account<EMAIL_ADDRESS>and got this error in the log on glitch:

The likely culprit is that hackers.town has AUTHORIZED_FETCH enabled as a Mastodon setting.
This means that fetching my actor data without HTTP signature headers in the GET request will result in a 401 Unauthorized status.
https://hackers.town/users/lmorchard.json
FWIW, it worked fine from my<EMAIL_ADDRESS>account, where AUTHORIZED_FETCH is not enabled.

thanks! I was vaguely aware of this setting but didn't have it on my radar.

It's been a gotcha in a few of my tinkery projects, too! Not sure it's a super-common setting enabled out there, but more of the privacy & security & moderation sensitive instances have switched it on

@pburke my only hesitation is that the code is such a mess, but if you're willing to help out, I definitely won't turn it down. Up until this point I've been coding in "just get it working" mode so some refactoring is definitely overdue. Thanks!

@ckolderup I'll take a crack at it soon and report back!


Refactor decodeControllerRevisionObject() to Use Delegated Type Handling

What this PR does

Fixes #12982
Why we need it and why it was done in this way
This PR introduces a delegated type handling approach to streamline and optimize the decoding and type conversion logic in the decodeControllerRevisionObject function. The aim is to avoid repetitive switch conditionals while maintaining flexibility for future scalability. By leveraging helper functions to handle type-specific conversions, the code is now more modular, readable, and easier to extend as new types or versions are introduced.
Special notes for your reviewer

Checklist
This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

[ ] Design: A design document was considered and is present (link) or not required
[ ] PR: The PR description is expressive enough and will help future contributors
[ ] Code: Write code that humans can understand and Keep it simple
[X] Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
[ ] Upgrade: Impact of this change on upgrade flows was considered and addressed if required
[ ] Testing: New code requires new unit tests. New features and bug fixes require at least on e2e test
[ ] Documentation: A user-guide update was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature / API change.
[ ] Community: Announcement to kubevirt-dev was considered

Release note

NONE

I'd suggest to put this on hold until https://github.com/kubevirt/kubevirt/pull/13036 is merged.

I'd suggest to put this on hold until #13036 is merged.

Yup apologies but we are heavily refactoring (finally) the instance type package at the start of the v1.5.0 cycle, would appreciate any help further refactoring this code later in the cycle if you have time then!


[11.x] Enhancing Middleware Configuration

This pull request enhances the Middleware class by introducing the ability to register middleware and their aliases simultaneously using the web() and api() methods. Users can now conveniently specify middleware aliases alongside middleware classes, streamlining the registration process. Additionally, the existing method of defining middleware and its alias separately remains fully functional.
Benefits:

Simplifies middleware registration by allowing users to specify aliases in addition to middleware classes in a single method call.
Enhances code readability and maintainability by consolidating related configuration tasks into one place.
Provides flexibility for developers to choose between the old and new registration methods, ensuring backward compatibility without breaking existing features.

Example Usage:
// old way
$middleware->web([
    TestMiddleware::class
]);

//new way
$middleware->web([
    'test' => TestMiddleware::class
]);

$middleware->api([
    'test' => TestMiddleware::class
]);

Thanks for your pull request to Laravel!
Unfortunately, I'm going to delay merging this code for now. To preserve our ability to adequately maintain the framework, we need to be very careful regarding the amount of code we include.
If possible, please consider releasing your code as a package so that the community can still take advantage of your contributions!
If you feel absolutely certain that this code corrects a bug in the framework, please "@" mention me in a follow-up comment with further explanation so that GitHub will send me a notification of your response.


Its not working anymore

sending a crashreport as soon as i open the game, tried to reset the config still nothing

same issue

Still works fine here

It works fine for me as well, maybe a clean reinstall may help.

Sorry! windows update broke things, back to normal


Update packages

updates and upgrades packages to their latest version.
Besides some little code cleanup, mostly removing unused variables.

I tried this:

$ nvm install 18
$ nvm use 18
$ rm -rf .cache public node_modules
$ npm i
npm run develop

...and I get this error:
 ERROR  UNKNOWN

There was a problem loading plugin "gatsby-plugin-gatsby-cloud". Perhaps you need to install its package?
Use --verbose to see actual error.

 ERROR  UNKNOWN

Failed to resolve gatsby-plugin-gatsby-cloud unreachable


[AdvancedSearch][Facets] conditional facets

Current behaviour
Facets with lots of values can be found even if they're facets covering sub-divisions of another facet.
It's easier to understand with an example: the world is divided in 5 geographical areas containing each several sub-divisions called (in this example) geomarkets, each of these containing several countries.

We currently see all three facets, though country will contain lots of values since there a many more countries than there are areas.
Expected behaviour
Having facets appear only if the parent facet has a selected value.

Then, when selecting a value (such as Asia), the Geomarket facet will appear:

And when selecting a Geomarket, the country facet will appear.

Versions
Focus-core: 0.12.3
Focus-components: 0.8.5

depending on server side ?
@NPi2Loup

@sgoretti I close it. If the issue is still occuring, reopen it.


Add at least some kind of if before the elif

There should be an if before elif.

Yup! Good spot, I clearly commented out too much.


yt-desc: Improved Track Parsing and more

yt-desc: Improvements and features
A. Previous Video / New Video / All Videos
Current Behaviour
This section is only shown if:

it is a video from a main track, which contains a playlistId field.
or challenges

New Behaviour
This section will be shown for all videos. (❗Is this reasonable? Should the default be something else?)

If the video is a challenge, no change in behaviour
If the video is from a track which does not have a playlistId field, then only Previous Video / Next Video will be shown (wherever applicable), and not All Videos.
If a video is in multiple tracks, then its canonicalTrack will be used.

B. Path resolution
Now it is possible to give any file path chunk in the generator, and it will know to read all index.json files inside the provided directory.
npm run yt-desc content/videos/transformations/
# same as
# npm run yt-desc content/videos/transformations/translate-rotate-push-pop/index.json
# npm run yt-desc content/videos/transformations/scale/index.json
# npm run yt-desc content/videos/transformations/more-transformations/index.json

C. Example of changes
If we generate the descriptions for transformations, here are the relevant segments:
# 1
🎥 Next video: https://youtu.be/pkHZTWOoTLM

# 2
🎥 Previous video: https://youtu.be/o9sgjuh-CBM
🎥 Next video: https://youtu.be/IVMvq9rd8dA

# 3
🎥 Previous video: https://youtu.be/pkHZTWOoTLM

Notice that there is no All Videos property, as the playlistId field is not set for this track.
D. Caveats:
1. Inconsistent data
Often, the site data is inconsistent with the data on YouTube. Ex: NOC Playlist

The YouTube playlist only contains videos upto 5.7. (and chapter 6 videos on the website are also inconsistently named on YouTube from an old playlist). A consequence of this mismatch, is that the description of 5.7 will link to 6.1 (physics libraries) as Next Video, although the YouTube playlist ends over there.
Though not too harmful, but important to know about.
2. Mixing of tracks
This is somewhat of a more significant caveat:
Let's check out the NOC track once again:

Here, the next video after video 3.7 is challenge 159 - Simple Pendulum. On YouTube, the description of 3.7 will link to this challenge, as the Next Video. However, this is where the chain breaks due to mixing of tracks - The Previous Video and Next Video for this challenge would be challenges 158 and 160, not some NOC video!
Obviously, this is completely expected, because it is a challenge video, but the point stands - whenever we are mixing videos of multiple tracks, it creates these "breaks" or "redirections" in the chain of links.

Hi @dipamsen I think this feels like the best solution possible even with all the caveats! I can always manually edit a YT description after all if I need it to do something specific.

Thanks, this is great, trying it out now!

Works great! I'll note I did get this error message when running npm run yt-desc content/videos/transformations/ but everything checks out otherwise!
⚠  Warning: Could not find this video: noc/p5-js-web-editor in any track or challenge!

Works great! I'll note I did get this error message when running npm run yt-desc content/videos/transformations/ but everything checks out otherwise!
⚠  Warning: Could not find this video: noc/p5-js-web-editor in any track or challenge!

@shiffman Yeah I also discovered that apparantly this video is not used anywhere

Ah, yes, that is a mistake I don't think the video should be there in the noc video directory! We can remove it in a separate branch. Merging this one now!


Question regarding injecting DocStrings

Just trying to understand, from what scope can I insert DocStrings into my project?
This here works:
::: logging.LogRecord
or even:
::: mkdocs.something_from_mkdocs
but
::: ast.AST
(or anything else from ast module) gives "could not collect" error.
EDIT:
My guess would be: because MkDocStrings is using the AST for checking and ast.AST is imported via star operator?
( https://github.com/python/cpython/blob/main/Lib/ast.py#L29C15-L29C15 )
EDIT2:
... and ::: collections.OrderedDict raises a different Exception, jinja2.exceptions.TemplateNotFound: alias.html

Hey, that's a very good question! This deserves an entry in the docs :slightly_smiling_face:
The ::: ast.AST case does not work, because the AST classes is imported from the private _ast module with a wildcard import, as you noted. And since we didn't pre-load the _ast module, or allowed alias resolution to external modules, all the wildcard imported objects are not detected. So when we try to access ast.AST, it fails because there's no AST member in ast. The error is propertly caught.
The collections.OrderedDict is almost the same, except that this time OrderedDict is imported directly (without a wildcard import), so the alias exist but cannot be resolved, ending up with a "template not found alias.html". This error could probably be better handled.
In the end, you can solve this by adding this line to your Python handler options, in mkdocs.yml: preload_modules: [_ast, _collections]. Also, we could consider always resolving to external modules if they are the private equivalent of the source module: if collections.OrderedDict -> _collections.OrderedDict then resolve.

Okay, thank you for the detailed explanation. The last detail I dont understand: OrderedDict is imported  explicitely. Why doesnt it work in that case? Because it´s placed in an exception block and therefore not at root level of the AST tree?

It does not work because it is imported from _collections, which is not loaded.

collections.OrderedDict points to _collections.OrderedDict
_collections is not loaded, so collections.OrderedDict cannot be resolved (stays an alias)
mkdocstrings fails with "no template alias.html"

Let me know if this is still unclear :slightly_smiling_face:

One more question if you dont mind, in case you are familiar with the following plugin. 😄
When I am inside a MkDocs-Gen-Files script and I am importing modules there, does that make them "preloaded" for MkDocStrings?

No, the preloading feature has nothing to do with modules being imported or not. By "loaded" we mean "loaded by Griffe". To pre-load a module, you have to use the preload_modules option option :slightly_smiling_face:  It acts as an include-list. If you want to resolve everything, always, you can use the load_external_modules option, though be careful of the side-effects (explained in the docs).

Griffe now automatically resolve aliases pointing to modules with the same name but private, for example:

ast -> _ast
collections -> _collections
etc.

So I believe this issue can be closed :relaxed:


Anchor with button

I leverage the combination of anchor and button to implement download as proposed in https://vaadin.com/forum/thread/17010389/17303946
Download works perfectly. Unfortunately the button inside anchor doesn't respect the rules of FormLayout. The button inside anchor unlike regualr standalone button doesn't occupy the complete form item cell.
Please find the screenshot

and the sample project https://github.com/vlipovetskii/vaadin-issue-0001-prj

Styling nested slotted elements with ::slotted()  isn't supported, this is how CSS works with Shadow DOM.
The only element which has a special meaning in <vaadin-form-layout> is <hr> element which creates line breaks.
As mentioned above, we are not going to introduce any other element-specific hacks to our layout components.
Closing as won't fix.


ig.publish.video 400 Bad Request; server processing error: VideoSourceError

Bug Report
I am trying to publish video.
Video source:
https://drive.google.com/file/d/1AmJtjr8ubrCTaLwzSipPiHlny1_VloJy/view?usp=sharing
Preview source (generated by ffmpeg -y -i pathtovideo -frames:v 1 outname):
https://drive.google.com/file/d/1kL57GFcnYnFtILyHPkLKD72hGxVT3b6i/view?usp=sharing
Form
Requirements

[x] I've searched the Issues
[x] I've read the basic concepts
[x] I'm using the latest version
[x] I've debugged my code using the DEBUG variable.

Platform

[x] I'm using Node.js version YOUR_VERSION (node -v) v12.16.0

Description
I am getting an error while uploading using ig.publish.video.
I don't know what is wrong, I just try to upload this video file direct by IG app in android phone and it works.
Code
I am using code from example just with my files:
https://github.com/dilame/instagram-private-api/blob/master/examples/upload-video.example.ts
// login...
// ..
await ig.publish.video({
            video: await readFileAsync(path),
            coverImage: await readFileAsync(previewFile),
})

Error and Output
IgUploadVideoError: POST /api/v1/media/upload_finish/?video=1 - 400 Bad Request; server processing error: VideoSourceError

videoInfo: { duration: 14882, width: 720, height: 1280 }

the video is a reels video and the video proportion are not allowed as a post
for now the library does not support uploading reels, you can share it as a story, it will work

videoInfo: { duration: 14882, width: 720, height: 1280 }

Your aspect ratio is 0.66 which is below the allowed one of 0.8.

@Nerixyz any library that you can suggest, which can help us to change the aspect ratio?

@Nerixyz Hello dear friend
I wish there was a way to change the images automatically, which is very important and useful. Can't you use ffmpeg and change the video file? I do not know much, but I think there is a spirit
Thanks

the video is a reels video and the video proportion are not allowed as a post
for now the library does not support uploading reels, you can share it as a story, it will work
another way is to use ffmpeg and create margins around so the proportions will be acceptable as a post

@nilyh how can i upload it as a story? its not working if i just import it and drop a buffer as the file flag using ig.publish.story()

the video is a reels video and the video proportion are not allowed as a post
for now the library does not support uploading reels, you can share it as a story, it will work
another way is to use ffmpeg and create margins around so the proportions will be acceptable as a post

@nilyh how can i upload it as a story? its not working if i just import it and drop a buffer as the file flag using ig.publish.story()


Expected ios/Runner.xcodeproj but this file is missing

Hi,
I created new project with command "flutter create PROJECT_NAME"
When i run the project by command "flutter run" i get error messages:

Expected ios/Runner.xcodeproj but this file is missing.
No application found for TargetPlatform.ios.
Is your project missing an ios/Runner/Info.plist?
Consider running "flutter create ." to create one.

I tried to use "flutter create ." but it doesn't help.

Hi @fadelguy
Can you please provide your flutter doctor -v and flutter run --verbose from new created project that shows this issue
Thank you

flutter doctor -v
[✓] Flutter (Channel stable, 2.2.0, on Mac OS X 10.15.7 19H1217 darwin-x64,
locale en-IL)
• Flutter version 2.2.0 at /Users/guyfadel/Development/flutter
• Framework revision b22742018b (12 days ago), 2021-05-14 19:12:57 -0700
• Engine revision a9d88a4d18
• Dart version 2.13.0
[!] Android toolchain - develop for Android devices (Android SDK version 27.0.3)
• Android SDK at /usr/local/share/android-sdk
✗ Flutter requires Android SDK 29 and the Android BuildTools 28.0.3
To update the Android SDK visit
https://flutter.dev/docs/get-started/install/macos#android-setup for
detailed instructions.
! Some Android licenses not accepted.  To resolve this, run: flutter doctor
--android-licenses
[!] Xcode - develop for iOS and macOS
• Xcode at /Applications/Xcode.app/Contents/Developer
• Xcode 12.4, Build version 12D4e
✗ CocoaPods installed but not working.
You appear to have CocoaPods installed but it is not working.
This can happen if the version of Ruby that CocoaPods was installed with
is different from the one being used to invoke it.
This can usually be fixed by re-installing CocoaPods.
To re-install see
https://guides.cocoapods.org/using/getting-started.html#installation for
instructions.
[✓] Chrome - develop for the web
• Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
[✓] Android Studio (version 4.2)
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6916264)
[✓] VS Code (version 1.56.2)
• VS Code at /Applications/Visual Studio Code.app/Contents
• Flutter extension can be installed from:
🔨 https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter
[✓] Connected device (1 available)
• Chrome (web) • chrome • web-javascript • Google Chrome 90.0.4430.212
flutter run --verbose
[+2978 ms] executing: sysctl hw.optional.arm64
[ +435 ms] Exit code 1 from: sysctl hw.optional.arm64
[   +2 ms] sysctl: unknown oid 'hw.optional.arm64'
[ +232 ms] executing: [/Users/guyfadel/Development/flutter/] git -c
log.showSignature=false log -n 1 --pretty=format:%H
[ +143 ms] Exit code 0 from: git -c log.showSignature=false log -n 1
--pretty=format:%H
[   +2 ms] b22742018b3edf16c6cadd7b76d9db5e7f9064b5
[   +1 ms] executing: [/Users/guyfadel/Development/flutter/] git tag --points-at
b22742018b3edf16c6cadd7b76d9db5e7f9064b5
[ +193 ms] Exit code 0 from: git tag --points-at
b22742018b3edf16c6cadd7b76d9db5e7f9064b5
[   +1 ms] 2.2.0
[  +31 ms] executing: [/Users/guyfadel/Development/flutter/] git rev-parse
--abbrev-ref --symbolic @{u}
[  +42 ms] Exit code 0 from: git rev-parse --abbrev-ref --symbolic @{u}
[   +1 ms] origin/stable
[        ] executing: [/Users/guyfadel/Development/flutter/] git ls-remote
--get-url origin
[  +38 ms] Exit code 0 from: git ls-remote --get-url origin
[   +1 ms] https://github.com/flutter/flutter.git
[+1953 ms] executing: [/Users/guyfadel/Development/flutter/] git rev-parse
--abbrev-ref HEAD
[  +60 ms] Exit code 0 from: git rev-parse --abbrev-ref HEAD
[   +2 ms] stable
[ +214 ms] executing: sw_vers -productName
[  +79 ms] Exit code 0 from: sw_vers -productName
[   +1 ms] Mac OS X
[        ] executing: sw_vers -productVersion
[  +42 ms] Exit code 0 from: sw_vers -productVersion
[        ] 10.15.7
[   +1 ms] executing: sw_vers -buildVersion
[  +40 ms] Exit code 0 from: sw_vers -buildVersion
[        ] 19H1217
[+1185 ms] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required,
skipping update.
[   +2 ms] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required,
skipping update.
[   +1 ms] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping
update.
[        ] Artifact Instance of 'FlutterWebSdk' is not required, skipping
update.
[  +20 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required,
skipping update.
[   +1 ms] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping
update.
[   +1 ms] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping
update.
[   +1 ms] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required,
skipping update.
[  +10 ms] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required,
skipping update.
[   +1 ms] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required,
skipping update.
[   +3 ms] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required,
skipping update.
[ +490 ms] executing: /usr/local/share/android-sdk/platform-tools/adb devices -l
[ +103 ms] executing: sysctl hw.optional.arm64
[  +15 ms] Exit code 1 from: sysctl hw.optional.arm64
[   +2 ms] sysctl: unknown oid 'hw.optional.arm64'
[        ] executing: xcrun xcodebuild -version
[+4816 ms] Exit code 0 from: xcrun xcodebuild -version
[        ] Xcode 12.4
Build version 12D4e
[  +10 ms] executing: xcrun xcdevice list --timeout 2
[  +13 ms] xcrun simctl list --json devices
[        ] executing: xcrun simctl list --json devices
[ +359 ms] List of devices attached
[ +732 ms] {
"devices" : {
"com.apple.CoreSimulator.SimRuntime.tvOS-14-3" : [
{
"dataPath" :
"/Users/guyfadel/Library/Developer/CoreSimulato
r/Devices/1025F9B1-2DF8-4B04-9920-60F26A885198/da
ta",
"logPath" :
"/Users/guyfadel/Library/Logs/CoreSimulator/10
25F9B1-2DF8-4B04-9920-60F26A885198",
"udid" : "1025F9B1-2DF8-4B04-9920-60F26A885198",
"isAvailable" : true,
"deviceTypeIdentifier" :
"com.apple.CoreSimulator.SimDeviceType.Apple-TV-1080
p",
"state" : "Shutdown",
"name" : "Apple TV"
},
{
"dataPath" :
"/Users/guyfadel/Library/Developer/CoreSimulato
r/Devices/871C672E-3D0C-481D-ACB4-A247AF5FEEC7/da
ta",
"logPath" :
"/Users/guyfadel/Library/Logs/CoreSimulator/87
1C672E-3D0C-481D-ACB4-A247AF5FEEC7",
"udid" : "871C672E-3D0C-481D-ACB4-A247AF5FEEC7",
"isAvailable" : true,
"deviceTypeIdentifier" :
"com.apple.CoreSimulator.SimDeviceType.Apple-TV-4K-4
K",
"state" : "Shutdown",
"name" : "Apple TV 4K"
},
{
"dataPath" :
"/Users/guyfadel/Library/Developer/CoreSimulato
r/Devices/8F29A47B-F453-45D6-92DA-888A0D794FA1/da
ta",
"logPath" :
"/Users/guyfadel/Library/Logs/CoreSimulator/8F
29A47B-F453-45D6-92DA-888A0D794FA1",
"udid" : "8F29A47B-F453-45D6-92DA-888A0D794FA1",
"isAvailable" : true,
"deviceTypeIdentifier" :
"com.apple.CoreSimulator.SimDeviceType.Apple-TV-4K-1
080p",
"state" : "Shutdown",
"name" : "Apple TV 4K (at 1080p)"
}
],
"com.apple.CoreSimulator.SimRuntime.watchOS-7-2" : [
{
"dataPath" :
"/Users/guyfadel/Library/Developer/CoreSimulato
r/Devices/37613E65-D0EE-475C-9244-197D6F9656A0/da
ta",
"logPath" :
"/Users/guyfadel/Library/Logs/CoreSimulator/37
613E65-D0EE-475C-9244-197D6F9656A0",
"udid" : "37613E65-D0EE-475C-9244-197D6F9656A0",
"isAvailable" : true,
"deviceTypeIdentifier" :
"com.apple.CoreSimulator.SimDeviceType.Apple-Watch-S
eries-5-40mm",
"state" : "Shutdown",
"name" : "Apple Watch Series 5 - 40mm"
},
{
"dataPath" :
"/Users/guyfadel/Library/Developer/CoreSimulato
r/Devices/29F58F54-9EE6-42D1-8F91-3DFBDC400938/da
ta",
"logPath" :
"/Users/guyfadel/Library/Logs/CoreSimulator/29
F58F54-9EE6-42D1-8F91-3DFBDC400938",
"udid" : "29F58F54-9EE6-42D1-8F91-3DFBDC400938",
"isAvailable" : true,
"deviceTypeIdentifier" :
"com.apple.CoreSimulator.SimDeviceType.Apple-Watch-S
eries-5-44mm",
"state" : "Shutdown",
"name" : "Apple Watch Series 5 - 44mm"
},
{
"dataPath" :
"/Users/guyfadel/Library/Developer/CoreSimulato
r/Devices/CDE5E4C8-B3BB-4ACC-BC90-4AEED9A8E5B6/da
ta",
"logPath" :
"/Users/guyfadel/Library/Logs/CoreSimulator/CD
E5E4C8-B3BB-4ACC-BC90-4AEED9A8E5B6",
"udid" : "CDE5E4C8-B3BB-4ACC-BC90-4AEED9A8E5B6",
"isAvailable" : true,
"deviceTypeIdentifier" :
"com.apple.CoreSimulator.SimDeviceType.Apple-Watch-S
eries-6-40mm",
"state" : "Shutdown",
"name" : "Apple Watch Series 6 - 40mm"
},
{
"dataPath" :
"/Users/guyfadel/Library/Developer/CoreSimulato
r/Devices/0E739086-F8CC-4F90-8B25-F8E1768E409F/da
ta",
"logPath" :
"/Users/guyfadel/Library/Logs/CoreSimulator/0E
739086-F8CC-4F90-8B25-F8E1768E409F",
"udid" : "0E739086-F8CC-4F90-8B25-F8E1768E409F",
"isAvailable" : true,
"deviceTypeIdentifier" :
"com.apple.CoreSimulator.SimDeviceType.Apple-Watch-S
eries-6-44mm",
"state" : "Shutdown",
"name" : "Apple Watch Series 6 - 44mm"
}
],
"com.apple.CoreSimulator.SimRuntime.iOS-14-4" : [
{
"dataPath" :
"/Users/guyfadel/Library/Developer/CoreSimulato
r/Devices/ADDB8268-A866-406D-8C87-FC0BFEB57F23/da
ta",
"logPath" :
"/Users/guyfadel/Library/Logs/CoreSimulator/AD
DB8268-A866-406D-8C87-FC0BFEB57F23",
"udid" : "ADDB8268-A866-406D-8C87-FC0BFEB57F23",
"isAvailable" : true,
"deviceTypeIdentifier" :
"com.apple.CoreSimulator.SimDeviceType.iPhone-8",
"state" : "Shutdown",
"name" : "iPhone 8"
},
{
"dataPath" :
"/Users/guyfadel/Library/Developer/CoreSimulato
r/Devices/216EB3B6-9304-4A26-B0AF-65A7BD55A9A7/da
ta",
"logPath" :
"/Users/guyfadel/Library/Logs/CoreSimulator/21
6EB3B6-9304-4A26-B0AF-65A7BD55A9A7",
"udid" : "216EB3B6-9304-4A26-B0AF-65A7BD55A9A7",
"isAvailable" : true,
"deviceTypeIdentifier" :
"com.apple.CoreSimulator.SimDeviceType.iPhone-8-Plus
",
"state" : "Shutdown",
"name" : "iPhone 8 Plus"
},
{
"dataPath" :
"/Users/guyfadel/Library/Developer/CoreSimulato
r/Devices/14776BB6-A75F-4D53-8C19-6D881DCA74B6/da
ta",
"logPath" :
"/Users/guyfadel/Library/Logs/CoreSimulator/14
776BB6-A75F-4D53-8C19-6D881DCA74B6",
"udid" : "14776BB6-A75F-4D53-8C19-6D881DCA74B6",
"isAvailable" : true,
"deviceTypeIdentifier" :
"com.apple.CoreSimulator.SimDeviceType.iPhone-11",
"state" : "Shutdown",
"name" : "iPhone 11"
},
{
"dataPath" :
"/Users/guyfadel/Library/Developer/CoreSimulato
r/Devices/D29ABC34-CE57-4189-AE40-E43C8A387D4D/da
ta",
"logPath" :
"/Users/guyfadel/Library/Logs/CoreSimulator/D2
9ABC34-CE57-4189-AE40-E43C8A387D4D",
"udid" : "D29ABC34-CE57-4189-AE40-E43C8A387D4D",
"isAvailable" : true,
"deviceTypeIdentifier" :
"com.apple.CoreSimulator.SimDeviceType.iPhone-11-Pro
",
"state" : "Shutdown",
"name" : "iPhone 11 Pro"
},
{
"dataPath" :
"/Users/guyfadel/Library/Developer/CoreSimulato
r/Devices/DC3B2D8F-584B-4E70-BEA2-3AF7FBB66871/da
ta",
"logPath" :
"/Users/guyfadel/Library/Logs/CoreSimulator/DC
3B2D8F-584B-4E70-BEA2-3AF7FBB66871",
"udid" : "DC3B2D8F-584B-4E70-BEA2-3AF7FBB66871",
"isAvailable" : true,
"deviceTypeIdentifier" :
"com.apple.CoreSimulator.SimDeviceType.iPhone-11-Pro
-Max",
"state" : "Shutdown",
"name" : "iPhone 11 Pro Max"
},
{
"dataPath" :
"/Users/guyfadel/Library/Developer/CoreSimulato
r/Devices/70DCA8DD-9E28-4C40-83D3-96407B061F98/da
ta",
"logPath" :
"/Users/guyfadel/Library/Logs/CoreSimulator/70
DCA8DD-9E28-4C40-83D3-96407B061F98",
"udid" : "70DCA8DD-9E28-4C40-83D3-96407B061F98",
"isAvailable" : true,
"deviceTypeIdentifier" :
"com.apple.CoreSimulator.SimDeviceType.iPhone-SE--2n
d-generation-",
"state" : "Shutdown",
"name" : "iPhone SE (2nd generation)"
},
{
"dataPath" :
"/Users/guyfadel/Library/Developer/CoreSimulato
r/Devices/FD5DD1AA-F5AE-4541-A4F8-717562C054AB/da
ta",
"logPath" :
"/Users/guyfadel/Library/Logs/CoreSimulator/FD
5DD1AA-F5AE-4541-A4F8-717562C054AB",
"udid" : "FD5DD1AA-F5AE-4541-A4F8-717562C054AB",
"isAvailable" : true,
"deviceTypeIdentifier" :
"com.apple.CoreSimulator.SimDeviceType.iPhone-12-min
i",
"state" : "Shutdown",
"name" : "iPhone 12 mini"
},
{
"dataPath" :
"/Users/guyfadel/Library/Developer/CoreSimulato
r/Devices/99FE1F83-7820-479B-8490-3167A98F0309/da
ta",
"logPath" :
"/Users/guyfadel/Library/Logs/CoreSimulator/99
FE1F83-7820-479B-8490-3167A98F0309",
"udid" : "99FE1F83-7820-479B-8490-3167A98F0309",
"isAvailable" : true,
"deviceTypeIdentifier" :
"com.apple.CoreSimulator.SimDeviceType.iPhone-12",
"state" : "Shutdown",
"name" : "iPhone 12"
},
{
"dataPath" :
"/Users/guyfadel/Library/Developer/CoreSimulato
r/Devices/EC19D0BB-8868-473D-8EB7-D4D7F578CBCB/da
ta",
"logPath" :
"/Users/guyfadel/Library/Logs/CoreSimulator/EC
19D0BB-8868-473D-8EB7-D4D7F578CBCB",
"udid" : "EC19D0BB-8868-473D-8EB7-D4D7F578CBCB",
"isAvailable" : true,
"deviceTypeIdentifier" :
"com.apple.CoreSimulator.SimDeviceType.iPhone-12-Pro
",
"state" : "Shutdown",
"name" : "iPhone 12 Pro"
},
{
"dataPath" :
"/Users/guyfadel/Library/Developer/CoreSimulato
r/Devices/D73CA108-B670-42CD-BD2E-2786BB39167A/da
ta",
"logPath" :
"/Users/guyfadel/Library/Logs/CoreSimulator/D7
3CA108-B670-42CD-BD2E-2786BB39167A",
"udid" : "D73CA108-B670-42CD-BD2E-2786BB39167A",
"isAvailable" : true,
"deviceTypeIdentifier" :
"com.apple.CoreSimulator.SimDeviceType.iPhone-12-Pro
-Max",
"state" : "Booted",
"name" : "iPhone 12 Pro Max"
},
{
"dataPath" :
"/Users/guyfadel/Library/Developer/CoreSimulato
r/Devices/528DEE06-BACB-4911-94B2-3508CD925E3D/da
ta",
"logPath" :
"/Users/guyfadel/Library/Logs/CoreSimulator/52
8DEE06-BACB-4911-94B2-3508CD925E3D",
"udid" : "528DEE06-BACB-4911-94B2-3508CD925E3D",
"isAvailable" : true,
"deviceTypeIdentifier" :
"com.apple.CoreSimulator.SimDeviceType.iPod-touch--7
th-generation-",
"state" : "Shutdown",
"name" : "iPod touch (7th generation)"
},
{
"dataPath" :
"/Users/guyfadel/Library/Developer/CoreSimulato
r/Devices/1B331719-F910-47A3-9BA7-9FBA7DE50F73/da
ta",
"logPath" :
"/Users/guyfadel/Library/Logs/CoreSimulator/1B
331719-F910-47A3-9BA7-9FBA7DE50F73",
"udid" : "1B331719-F910-47A3-9BA7-9FBA7DE50F73",
"isAvailable" : true,
"deviceTypeIdentifier" :
"com.apple.CoreSimulator.SimDeviceType.iPad-Pro--9-7
-inch-",
"state" : "Shutdown",
"name" : "iPad Pro (9.7-inch)"
},
{
"dataPath" :
"/Users/guyfadel/Library/Developer/CoreSimulato
r/Devices/DCD5296A-1CC5-405D-B3A6-DF366C0AA695/da
ta",
"logPath" :
"/Users/guyfadel/Library/Logs/CoreSimulator/DC
D5296A-1CC5-405D-B3A6-DF366C0AA695",
"udid" : "DCD5296A-1CC5-405D-B3A6-DF366C0AA695",
"isAvailable" : true,
"deviceTypeIdentifier" :
"com.apple.CoreSimulator.SimDeviceType.iPad-Pro--11-
inch---2nd-generation-",
"state" : "Shutdown",
"name" : "iPad Pro (11-inch) (2nd generation)"
},
{
"dataPath" :
"/Users/guyfadel/Library/Developer/CoreSimulato
r/Devices/A21ED01C-DCD5-40A8-9738-D7AF7AAC64C9/da
ta",
"logPath" :
"/Users/guyfadel/Library/Logs/CoreSimulator/A2
1ED01C-DCD5-40A8-9738-D7AF7AAC64C9",
"udid" : "A21ED01C-DCD5-40A8-9738-D7AF7AAC64C9",
"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/guyfadel/Library/Developer/CoreSimulato
r/Devices/F78FA452-AA49-43CE-987E-68987E153C82/da
ta",
"logPath" :
"/Users/guyfadel/Library/Logs/CoreSimulator/F7
8FA452-AA49-43CE-987E-68987E153C82",
"udid" : "F78FA452-AA49-43CE-987E-68987E153C82",
"isAvailable" : true,
"deviceTypeIdentifier" :
"com.apple.CoreSimulator.SimDeviceType.iPad--8th-gen
eration-",
"state" : "Shutdown",
"name" : "iPad (8th generation)"
},
{
"dataPath" :
"/Users/guyfadel/Library/Developer/CoreSimulato
r/Devices/FB191F29-3137-48B5-B234-CE15171FEF53/da
ta",
"logPath" :
"/Users/guyfadel/Library/Logs/CoreSimulator/FB
191F29-3137-48B5-B234-CE15171FEF53",
"udid" : "FB191F29-3137-48B5-B234-CE15171FEF53",
"isAvailable" : true,
"deviceTypeIdentifier" :
"com.apple.CoreSimulator.SimDeviceType.iPad-Air--4th
-generation-",
"state" : "Shutdown",
"name" : "iPad Air (4th generation)"
}
]
}
}
[+6249 ms] [
{
"simulator" : true,
"operatingSystemVersion" : "14.4 (18D46)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPhone12,5",
"identifier" : "DC3B2D8F-584B-4E70-BEA2-3AF7FBB66871",
"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.4 (18D46)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPad11,7",
"identifier" : "F78FA452-AA49-43CE-987E-68987E153C82",
"architecture" : "x86_64",
"modelUTI" : "com.apple.ipad-8-wwan-1",
"modelName" : "iPad (8th generation)",
"name" : "iPad (8th generation)"
},
{
"simulator" : true,
"operatingSystemVersion" : "14.4 (18D46)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPad13,2",
"identifier" : "FB191F29-3137-48B5-B234-CE15171FEF53",
"architecture" : "x86_64",
"modelUTI" : "com.apple.ipad-air4-1",
"modelName" : "iPad Air (4th generation)",
"name" : "iPad Air (4th generation)"
},
{
"simulator" : true,
"operatingSystemVersion" : "14.4 (18D46)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPhone12,1",
"identifier" : "14776BB6-A75F-4D53-8C19-6D881DCA74B6",
"architecture" : "x86_64",
"modelUTI" : "com.apple.iphone-11-1",
"modelName" : "iPhone 11",
"name" : "iPhone 11"
},
{
"simulator" : true,
"operatingSystemVersion" : "14.4 (18D46)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPod9,1",
"identifier" : "528DEE06-BACB-4911-94B2-3508CD925E3D",
"architecture" : "x86_64",
"modelUTI" : "com.apple.ipod-touch-7-2",
"modelName" : "iPod touch (7th generation)",
"name" : "iPod touch (7th generation)"
},
{
"simulator" : true,
"operatingSystemVersion" : "14.4 (18D46)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPhone10,4",
"identifier" : "ADDB8268-A866-406D-8C87-FC0BFEB57F23",
"architecture" : "x86_64",
"modelUTI" : "com.apple.iphone-8-2",
"modelName" : "iPhone 8",
"name" : "iPhone 8"
},
{
"simulator" : true,
"operatingSystemVersion" : "7.2 (18S561)",
"available" : true,
"platform" : "com.apple.platform.watchsimulator",
"modelCode" : "Watch6,2",
"identifier" : "0E739086-F8CC-4F90-8B25-F8E1768E409F",
"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.4 (18D46)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPad8,12",
"identifier" : "A21ED01C-DCD5-40A8-9738-D7AF7AAC64C9",
"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.4 (18D46)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPhone13,1",
"identifier" : "FD5DD1AA-F5AE-4541-A4F8-717562C054AB",
"architecture" : "x86_64",
"modelUTI" : "com.apple.iphone-12-mini-1",
"modelName" : "iPhone 12 mini",
"name" : "iPhone 12 mini"
},
{
"simulator" : true,
"operatingSystemVersion" : "14.4 (18D46)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPhone13,2",
"identifier" : "99FE1F83-7820-479B-8490-3167A98F0309",
"architecture" : "x86_64",
"modelUTI" : "com.apple.iphone-12-1",
"modelName" : "iPhone 12",
"name" : "iPhone 12"
},
{
"simulator" : true,
"operatingSystemVersion" : "14.4 (18D46)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPhone12,8",
"identifier" : "70DCA8DD-9E28-4C40-83D3-96407B061F98",
"architecture" : "x86_64",
"modelUTI" : "com.apple.iphone-se-1",
"modelName" : "iPhone SE (2nd generation)",
"name" : "iPhone SE (2nd generation)"
},
{
"simulator" : true,
"operatingSystemVersion" : "14.4 (18D46)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPad8,9",
"identifier" : "DCD5296A-1CC5-405D-B3A6-DF366C0AA695",
"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" : "7.2 (18S561)",
"available" : true,
"platform" : "com.apple.platform.watchsimulator",
"modelCode" : "Watch5,4",
"identifier" : "29F58F54-9EE6-42D1-8F91-3DFBDC400938",
"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 (18K559)",
"available" : true,
"platform" : "com.apple.platform.appletvsimulator",
"modelCode" : "AppleTV5,3",
"identifier" : "1025F9B1-2DF8-4B04-9920-60F26A885198",
"architecture" : "x86_64",
"modelUTI" : "com.apple.apple-tv-4",
"modelName" : "Apple TV",
"name" : "Apple TV"
},
{
"simulator" : true,
"operatingSystemVersion" : "14.4 (18D46)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPhone13,4",
"identifier" : "D73CA108-B670-42CD-BD2E-2786BB39167A",
"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.4 (18D46)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPhone13,3",
"identifier" : "EC19D0BB-8868-473D-8EB7-D4D7F578CBCB",
"architecture" : "x86_64",
"modelUTI" : "com.apple.iphone-12-pro-1",
"modelName" : "iPhone 12 Pro",
"name" : "iPhone 12 Pro"
},
{
"simulator" : true,
"operatingSystemVersion" : "14.4 (18D46)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPhone10,5",
"identifier" : "216EB3B6-9304-4A26-B0AF-65A7BD55A9A7",
"architecture" : "x86_64",
"modelUTI" : "com.apple.iphone-8-plus-2",
"modelName" : "iPhone 8 Plus",
"name" : "iPhone 8 Plus"
},
{
"simulator" : true,
"operatingSystemVersion" : "7.2 (18S561)",
"available" : true,
"platform" : "com.apple.platform.watchsimulator",
"modelCode" : "Watch5,3",
"identifier" : "37613E65-D0EE-475C-9244-197D6F9656A0",
"architecture" : "x86_64",
"modelUTI" : "com.apple.watch-series5-1",
"modelName" : "Apple Watch Series 5 - 40mm",
"name" : "Apple Watch Series 5 - 40mm"
},
{
"simulator" : true,
"operatingSystemVersion" : "7.2 (18S561)",
"available" : true,
"platform" : "com.apple.platform.watchsimulator",
"modelCode" : "Watch6,1",
"identifier" : "CDE5E4C8-B3BB-4ACC-BC90-4AEED9A8E5B6",
"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.4 (18D46)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPad6,4",
"identifier" : "1B331719-F910-47A3-9BA7-9FBA7DE50F73",
"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.4 (18D46)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPhone12,3",
"identifier" : "D29ABC34-CE57-4189-AE40-E43C8A387D4D",
"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" : "871C672E-3D0C-481D-ACB4-A247AF5FEEC7",
"architecture" : "x86_64",
"modelUTI" : "com.apple.apple-tv-4k",
"modelName" : "Apple TV 4K",
"name" : "Apple TV 4K"
},
{
"simulator" : true,
"operatingSystemVersion" : "14.3 (18K559)",
"available" : true,
"platform" : "com.apple.platform.appletvsimulator",
"modelCode" : "AppleTV6,2",
"identifier" : "8F29A47B-F453-45D6-92DA-888A0D794FA1",
"architecture" : "x86_64",
"modelUTI" : "com.apple.apple-tv-4k",
"modelName" : "Apple TV 4K (at 1080p)",
"name" : "Apple TV 4K (at 1080p)"
}
]
[  +15 ms] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required,
skipping update.
[        ] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required,
skipping update.
[  +14 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.
[ +269 ms] "flutter run" took 13,295ms.
[  +94 ms] Error: No pubspec.yaml file found.
This command should be run from the root of your Flutter project.
[  +11 ms]
#0      FlutterCommand.validateCommand
(package:flutter_tools/src/runner/flutter_command.dart:1309:11)
#1      RunCommand.validateCommand
(package:flutter_tools/src/commands/run.dart:448:19)
#2      FlutterCommand.verifyThenRunCommand
(package:flutter_tools/src/runner/flutter_command.dart:1148:11)

#3      FlutterCommand.run.
(package:flutter_tools/src/runner/flutter_command.dart:1043:27)

#4      AppContext.run.
(package:flutter_tools/src/base/context.dart:150:19)

#5      CommandRunner.runCommand
(package:args/command_runner.dart:196:13)

#6      FlutterCommandRunner.runCommand.
(package:flutter_tools/src/runner/flutter_command_runner.dart:284:9)

#7      AppContext.run.
(package:flutter_tools/src/base/context.dart:150:19)

#8      FlutterCommandRunner.runCommand
(package:flutter_tools/src/runner/flutter_command_runner.dart:232:5)

#9      run..
(package:flutter_tools/runner.dart:62:9)

#10     AppContext.run.
(package:flutter_tools/src/base/context.dart:150:19)

#11     main (package:flutter_tools/executable.dart:91:3)

[ +280 ms] ensureAnalyticsSent: 262ms
[   +3 ms] Running shutdown hooks
[        ] Shutdown hooks complete
[   +6 ms] exiting with code 1

Hi @fadelguy
I have the same stable channel, there is no such issue.
Can you please go to yourapp/ios/ and confirm Runner.xcodeproj is there?

The file doesn't exist

Format mac solved the problem


torch.cat consume large amount of memory

Dear author,
I saw that in `/home/dayu/convir/ColBERTv1/colbert/indexing/faiss.py", line 35 , this step
sample = torch.cat(sample).float().numpy()

will consume large amount of memory, which my machine cannot handle. Is there any alternative solution for this?
Best,
Dayu

Lower precision such as float16 might help


museum of history not registering as inf free

https://netrunnerdb.com/en/deck/view/720886

Thanks, fixed.


Exception Filter - Exception Propogation

the following is written in the doc of the exception filter:
To handle an exception, set the exceptionhandled property to true or write a response. This stops propagation of the exception. An exception filter can't turn an exception into a "success". Only an action filter can do that. - see link
how ever, when writing to the response the exception is still propogated.
this is how we write the response:
public async Task OnExceptionAsync(ExceptionContext context)
{
    context.HttpContext.Response.StatusCode = (int)requestFailureException.ResponseStatusCode;
    await context.HttpContext.Response.WriteAsJsonAsync(CreateErrorResponse()).ConfigureAwait(false);
}

it's either that the docs aren't 100% clear, or there is a Bug.

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

ID: a70a955f-dd5a-c46b-dfe8-21521e619320
Version Independent ID: ebb299e0-6c1c-7077-689d-ac711352e418
Content: Filters in ASP.NET Core
Content Source: aspnetcore/mvc/controllers/filters.md
Product: aspnet-core
Technology: aspnetcore-mvc
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

Hi @karayanni. Thanks for taking the time to open an issue.
It appears that setting ExceptionHandled to true is required, as writing a response doesn't stop the exception from propagating, as you've said. It also appears that it is possible to turn an exception into a "success", as setting ExceptionHandled and writing a response results in a 200 status-code by default. I've tested this using Razor Pages and an IAsyncExceptionFilter.
I agree: the docs either aren't clear, or something has changed since it was written.
@pranavkm Could you please advise on what might be wrong here in the docs, or let me know who I should ask? I can provide a minimal sample if that helps.

It should say if ExceptionHandled is set or ExceptionContext.Result is assigned which would prevent MVC from rethrowing the exception.

It should say if ExceptionHandled is set or ExceptionContext.Result is assigned which would prevent MVC from rethrowing the exception.

Thank you @pranavkm.

At the top right of the article, select the Edit pen icon:

Select the pen icon again. Save.

@serpent5 sure thing.

@serpent5  can u please give me write permissions

linked a PR to the issue:
https://github.com/dotnet/AspNetCore.Docs/pull/25015
give it a look when u get a chance and thanks for the quick response time.


Packaged .qmlc and pycache files

This plug-in comes with pre-packaged QMLC files. These files are not usable, since the QMLC file is a mmap of the memory used by the QML items. This is different between operating systems and Qt versions.
It also comes with a __pycache__ folder for cached Python compiled classes. However this cache is made with Python 3.6 rather than Python 3.5 that Cura is shipped with.
Maybe it's better to remove these cached files from the distribution?

It seems this might be a bug with the packaging service of the Marketplace, that one is supposed to skip all files that contain amongst others __pycache__ and qmlc in their paths. I'll have a look at that after the weekend. Of course it's still better to also not upload them at all.

I have check the last version of this plugin uploaded via the portal and there are no __pycache__ and qmlc files in the .curapackage. They are filtered out of the source files when building the package. Please let me know if you have a different experience.


Fatal error: Uncaught TypeError: Argument 1 passed to WCMP_Upgrade_Migration_v4_1_0::roundUpToMatch()

Describe the bug
Getting this error after upgrading from 3.2.0 to 4.6.0
Fatal error: Uncaught TypeError: Argument 1 passed to WCMP_Upgrade_Migration_v4_1_0::roundUpToMatch() must be of the type int, null given, called in /www/wp-content/plugins/woocommerce-myparcel/migration/wcmp-upgrade-migration-v4-1-0.php on line 200 and defined in /www/wp-content/plugins/woocommerce-myparcel/migration/wcmp-upgrade-migration-v4-1-0.php:212 Stack trace: #0 /www/wp-content/plugins/woocommerce-myparcel/migration/wcmp-upgrade-migration-v4-1-0.php(200): WCMP_Upgrade_Migration_v4_1_0->roundUpToMatch(NULL, Array) #1 /www/wp-content/plugins/woocommerce-myparcel/migration/wcmp-upgrade-migration-v4-1-0.php(81): WCMP_Upgrade_Migration_v4_1_0->correctPostNlInsurance() #2 /www/wp-content/plugins/woocommerce-myparcel/migration/wcmp-upgrade-migration.php(15): WCMP_Upgrade_Migration_v4_1_0->migrate() #3 /www/wp-content/plugins/woocommerce-myparcel/migration/wcmp-upgrade-migration-v4-1-0.php(55): migration\WCMP_Upgrade_Migration->__construct() #4 /www/wp-content/plugins/woocommerce-myparcel/migration/wcmp-upgrade-migration in /www/wp-content/plugins/woocommerce-myparcel/migration/wcmp-upgrade-migration-v4-1-0.php on line 212
Steps to reproduce this behaviour
upgrade from 3.2.0 to 4.6.0
Details

WordPress version: 5.8.2
WooCommerce version: 5.9.0
WooCommerce MyParcel version: 3.2.0

Hi @nilsdewilde .
Is this problem still present when you update the plugin to the latest version (v4.11.0) ?

Hi @nilsdewild ,
I have tried to reproduce this problem several times. But unfortunately I don't see the problem.
Since there has no response since April 19, I am closing the issue.
If this problem is still present, you can always open the issue again.


some more Geo: test links

https://github.com/organicmaps/organicmaps/issues/7837
adds:
geo:0,0?q=Restaurant - search for 'Restaurant' type around current position
geo:0,0?q=87G7MXQ4%2BM5 - search for Plus Code '87G7MXQ4+M5' from current position (strings in Geo URI must be encoded so '+' is '%2B')

@biodranik merge?


Upgrade kiali to version 0.8

Describe the feature request
Kiali supports customized context path in the latest release - v0.8.
for more details, refer to https://github.com/kiali/kiali/issues/526

Yes, this is being worked on - ansible installer upgraded: https://github.com/istio/istio/pull/9069
See this issue where the work will be getting done: https://github.com/istio/istio/issues/9066

Cool, thanks @jmazzitelli and @clyang82


Added a new category for Books

Hi,
Stjepan from Manning here. We have a new book on Jax: "Jax in Action" by Grigory Sapunov. If you agree with having the books on your list, I can contribute the link via PR.
Please, let me know.
Thank you.
Best,

Great suggestion! Left some comments for you to address.

Hi Nicholas,
Thank you for your feedback. I'm adding Jax in Action.

Sorry about the incomplete comment, should make sense now. Once you make that change, we can merge it in.

Hi Nicholas,
Thank you for all your comments. I hope I've managed to make changes
properly. Please, merge if so.
Best,
On Sun, Sep 4, 2022 at 1:22 AM Nicholas Vadivelu @.***>
wrote:

Sorry about the incomplete comment, should make sense now. Once you make
that change, we can merge it in.
—
Reply to this email directly, view it on GitHub
https://github.com/n2cholas/awesome-jax/pull/60#issuecomment-1236212451,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANDIEMOPEO363ZXP3PIC2WLV4PMSTANCNFSM57K5LWLQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
Stjepan Jureković
Manning Publications - Marketing
@.***

Thanks!

Thank you.
Best,
On Sun, Sep 18, 2022 at 10:39 PM Nicholas Vadivelu @.***>
wrote:

Merged #60 https://github.com/n2cholas/awesome-jax/pull/60 into main.
—
Reply to this email directly, view it on GitHub
https://github.com/n2cholas/awesome-jax/pull/60#event-7409421681, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ANDIEMIJ7QRIHC3MMO6ENCTV654W3ANCNFSM57K5LWLQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
Stjepan Jureković
Manning Publications - Marketing
@.***


Added pulldown option for review of articles. Added review page for e…

Added  the pulldown option for reviewing articles.
Added a review page that allows an admin person to see which articles are in the review process
Allows reviewer to click on an article and choose to reject/accept/return for revision/edit/trash submission

Bugs:

when you click on review articles, it takes you to the articles page; if you click a second time, it works

To do:

limit review page to only those with admin role
add tag to each article to show its current status; perhaps sort based on status

Cancelling this pull request. Since article upload is already available, I am adding the review functionality under the articleReview branch.


Eaf controlled vocabulary

[x] check that all the annotations use labels defined in the controlled vocabulary
[x]  import the description of each label of the controlled vocabulary and store it somewhere
[x] documentation
[x] tests

Few comments on this PR!

I was not convinced that the output belongs into metadata rather than annotations/<set>, but I think it does not matter so much!
I think the metadata file should contain information about the annotation set (annotation['set']) and the input annotation (annotation['raw_filename']). Maybe also the date of importation? (just like for the annotations' index).

What do you think?

I am in favour of putting the controlled vocabulary metadata inside the metadata folder. I find it simpler to have everything stored in one place rather than in several places.
I agree it's important to save the name of the annotation set in the metadata file. But I'm not convinced we should also save the raw_filename of all the files using this annotation scheme as all the files of a given set should be using it anyway...

For now the controlled vocabulary looks like this :

It's a good idea to add the annotation set !
I can add a column annotation_sets, with a list of the sets in which the tier is used.
I'm not sure about the raw_filename (and importation_date), the table would be difficult to read...

I agree that ideally all the files should share the same vocabulary within a set, but for debugging purposes it is still useful (I think) to keep track of where the information was retrieved. That does not mean keeping a duplicate entry for each file (so that should not pose any readability problem). Also this should allow to spot mismatches between annotations within a set if they occur. If you can't see a situation where this may be useful then forget about it! It's just an idea:)


🐛 Remove unnecessary memoize that is causing 🐛

Issue
This is what it looks like the problem is:

User visits https://inbox.google.com.  Some inbox pages don't have a favicon
Favioli memoizes that inbox.google.com doesn't have a favicon
User visits inbox at https://inbox.google.com/u/0/?pli=1
Subsequent link has favicon, but Favioli overrides because memoized that inbox doesn't have one.

Fix
Remove memoize from  hasFavIcon

Memoize originally was used here for consistency on websites
Due to subsequent fixes in favicon discovery, probably no longer necessary?

Should fix #30

For example, this warning page doesn't have a favicon:

lgtm 👍


tss-2294: Updated accessibility statement

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 43.52%. Comparing base (16d3c54) to head (636bb34).

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #431   +/-   ##
=======================================
  Coverage   43.52%   43.52%
=======================================
  Files          98       98
  Lines        4963     4963
  Branches      651      651
=======================================
  Hits         2160     2160
  Misses       2803     2803

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


explicit ORDERBY please

on pp73-75 book shows simple SELECT with an ORDER BY clause

but the "more complex sample" on p74 (and pp78-79) then forgets this basic advice (doh!)

TSQL code also does an unnecessary CAST to DATE because the ConfirmedDeliveryTime is already of datatype Datetime2(7)
Because this field is computed (but not persisted) via (both queries)
TRY_CONVERT(datetime2,json_value([ReturnedDeliveryData],N'$.DeliveredWhen'),(126))
it is Non-Sargable and inefficient, but that is consequence of WideWorldImporters design and not your usage thereof
P.S. thanks for previously accepting my Issue #4, PR #5 !

Not sure what is the issue here. ORDER BY is used in the first sample to introduce the concept that there is no inherent ordering. In the more complex sample it is not used as not needed, as the concept was already clarified.
CAST is needed to make sure that the time part of a DateTime is not used, so that you can only focus on the dates.

Readers might reasonably expect examples building up to the "complex example" should embody the lessons from earlier simpler examples, hence my advice to include the ORDER BY both here and generally for reader consideration. IMHO it is better to avoid surprises that might arise by leaving such matters indeterminate.
CAST is not needed for the TSQL example shown because the ConfirmedDeliveryTime computed field is of type Datetime2(7) so the code will compile the literals to that date+time format prior to executing the predicate. Thus my point that you should let the TSQL compiler to its thing and not uglify the example code with an unnecessary CAST.
Elsewhere guidance is to avoid UDFs as they can introduce performance problems, and any similar function/CAST/CONVERT can equally cause grief. If you don't need it, don't use it (YAGNI)!

@DickBaker CAST is needed as the ConfirmedDeliveryTime contains not only date, but also time. Since the predicate is using a BETWEEN operator, without the case to the date type, the predicate would be read as:
i.ConfirmedDeliveryTime BETWEEN '2016-01-01 00:00:00' AND '2016-03-31 00:00:00'
which you can see how wrong would that be. Right? :)

Also scalar UDFs have overhead that doesn't affect system functions like CAST or CONVERT. If we put the ability to use an index aside for a second, there is no harm in using CAST or CONVERT if needed. In this specific case, in addition, converting a DATETIME2 to a DATE doesn't even incur in the problem of preventing index usage, as optimizer is smart enough to understand that if there is an index on ConfirmedDeliveryTime and you are casting it do a date type, you're basically doing a prefix-search so index can be used to seek data efficiently.

i.ConfirmedDeliveryTime BETWEEN '2016-01-01' AND '2016-03-31' works fine - seems compiler is smarter than you think. Right?
imho fluff is unnecessary and distracts reader, and any such frippery can often lead to nonsargable perf problems. Unfortunately importance of SARG (Search ARGument ABLE) is not adequately explained. Perhaps test,test,test explains it better (YMMV!)

Just run the query and see yourself. This query
select count(*) from Sales.[Invoices] i
where i.ConfirmedDeliveryTime BETWEEN '2016-01-01' AND '2016-03-31'

returns 5309 rows, this one
select count(*) from Sales.[Invoices] i
where cast(i.ConfirmedDeliveryTime as date) BETWEEN '2016-01-01' AND '2016-03-31'

returns 5397 rows.


Add RGB v0.11-beta 8 tо notable releases, news section and Client-side validation topic page

Link to the topic page https://bitcoinops.org/en/topics/client-side-validation/
Link to the previous issue, which was definitely closed and marked as 'complete' by mistake due to a misunderstanding of what a client-side validation is https://github.com/bitcoinops/bitcoinops.github.io/issues/1879
@harding please check this and provide the feedback

Id imagine if there is a substantial RGB release that is covered in the client / services section, we would then link to it in the client side validation page, just as we did with the taproot assets release recently: https://bitcoinops.org/en/topics/client-side-validation/#optech-newsletter-and-website-mentions

Id imagine if there is a substantial RGB release that is covered in the client / services section, we would then link to it in the client side validation page, just as we did with the taproot assets release recently: https://bitcoinops.org/en/topics/client-side-validation/#optech-newsletter-and-website-mentions

As far as I'm aware of the process, you collect notable releases and news, publish them weekly and then summarise everything in monthly releases of Bitcoin Optech. Why are you making exceptions for RGB progress and refusing to follow your own established process?

you collect notable releases and news

(weekly) News from: https://bitcoinops.org/en/internal/sources/
(weekly) Notables from the list we note in the notable section for each newsletter. Currently: "Notable recent changes in Bitcoin Core, Core Lightning, Eclair, LDK, LND, libsecp256k1, Hardware Wallet Interface (HWI), Rust Bitcoin, BTCPay Server, BDK, Bitcoin Improvement Proposals (BIPs), Lightning BOLTs, Lightning BLIPs, Bitcoin Inquisition, and BINANAs."
(monthly) Changes to services and client software: In this monthly feature, we highlight interesting updates to Bitcoin wallets and services.
I noted that the RGB v0.11 Beta 8 changes to the nonce data type and change to data persistence didnt seem notable for this segment last month. Ill continue to keep an eye out for interesting updates here in the future.

I would kindly ask you to comment on the decision to exclude any mention of RGB, Prime or any other progress from Bitcoin Optech

We have no such exclusion policy.

were not mentioned even once over the past 2 years

I remember distinctly this large writeup on RGB updates: https://bitcoinops.org/en/newsletters/2023/04/19/#rgb-update
And also have Maxim on the Optech podcast: https://bitcoinops.org/en/podcast/2023/04/20/#rgb-update-transcript
We've covered RGB and related projects several times, as noted in one of your previous periodic interactions on this same topic.

(weekly) News from: https://bitcoinops.org/en/internal/sources/
(weekly) Notables from the list we note in the notable section for each newsletter. Currently: "Notable recent changes in Bitcoin Core, Core Lightning, Eclair, LDK, LND, libsecp256k1, Hardware Wallet Interface (HWI), Rust Bitcoin, BTCPay Server, BDK, Bitcoin Improvement Proposals (BIPs), Lightning BOLTs, Lightning BLIPs, Bitcoin Inquisition, and BINANAs."
(monthly) Changes to services and client software: In this monthly feature, we highlight interesting updates to Bitcoin wallets and services.

So basically, again, our work (including work on Bitcoin, Lightning and not just on RGB and client-side validation) is out of the scope for any of the topics or reviews above, is not notable for the Topic of client-side validation that is present on your website. Because you do not follow any of our work according to this list https://bitcoinops.org/en/internal/sources/ , you are not adding any of our work to the list of Notables regardless us being there for more than 5 years and building a lot of things (bringing Taproot to rust-bitcoin, building bp library, having RGB smart contracts, writing LNPBPs, building prime, having LNP Node etc) - nothing was notable enough for mentioning, I suppose, or even worth following? And we are not suitable for clients are services because a) RGB is NOT a client and service-related protocol - as I have been trying to tell you but you refuse to read and b) the actual wallets and 'services' improvements we have for some weird reasons also have not been included.
All mentioned above does, indeed, prove, that you do NOT have an exclusion policy on our work :D

Ill continue to keep an eye out for interesting updates here in the future.

How exactly will you do that  if our work is not on the list of the sources you are following and not on the list of notable things happening in the space?

I remember distinctly this large writeup on RGB updates: https://bitcoinops.org/en/newsletters/2023/04/19/#rgb-update
And also have Maxim on the Optech podcast: https://bitcoinops.org/en/podcast/2023/04/20/#rgb-update-transcript
We've covered RGB and related projects several times, as noted in one of your previous periodic interactions on this same topic.

Let's be honest here, you did those mentions only after the community forced you to, not because you actually follow our work or think it's valuable or because we did a good job at something.
Also, we have done MANY releases for the past year and you are still, stubbornly, finding excuses to never add anything about our work neither to the newsletters, nor to the CSV section.

you do NOT have an exclusion policy on our work

That is correct.

Because you do not follow any of our work according to this list https://bitcoinops.org/en/internal/sources/

These sources are all completely public and nothing is preventing you from posting interesting content there.

you did those mentions only after ...

Only after Maxim posted to Bitcoin-dev, one of our sources for the news section that we advised you to post to at that time

we have done MANY releases for the past year

Please let me know when something that is more interesting than the nonces and backups comes up and Ill consider it for the client/services segment

These sources are all completely public and nothing is preventing you from posting interesting content there.

So that you would point me at the door and tell me it's not good enough, as you have been doing here, with RGB updates?

Only after Maxim posted to Bitcoin-dev, one of our sources for the news section that we advised you to post to at that time

That's not what happened, have some decency.

Please let me know when something that is more interesting than the nonces and backups comes up and Ill consider it for the client/services segment

Wait a second, so you will follow our work as you wrote above or do I need to notify you when we have updates? You are contradicting your own words (as usual).

more interesting than the nonces and backups

This statement is completely false. It proves that  you did absolutely nothing to actually look in the code or release notes for that matter. I also have no idea what you are comparing the release to, especially taking into account that you yourself admitted that you do not follow our work. Sounds like yet another excuse to not ever post anything about our progress.
But of course, there is NO policy to exclude our work from your newsletters :D

Ive outlined source materials for each segment of the newsletter. Ill do it here, yet again
(weekly) News from: https://bitcoinops.org/en/internal/sources/
(weekly) Notables from the list we note in the notable section for each newsletter. Currently: "Notable recent changes in Bitcoin Core, Core Lightning, Eclair, LDK, LND, libsecp256k1, Hardware Wallet Interface (HWI), Rust Bitcoin, BTCPay Server, BDK, Bitcoin Improvement Proposals (BIPs), Lightning BOLTs, Lightning BLIPs, Bitcoin Inquisition, and BINANAs."
(monthly) Changes to services and client software: In this monthly feature, we highlight interesting updates to Bitcoin wallets and services.
Im happy to take recommendations for the client/services segment directly, as also already noted. As I am just repeating the same thing here, I think your energy would best spent to get interesting RGB content posted to the public forums.

Ive outlined source materials for each segment of the newsletter.  Yet again.

Im happy to take recommendations for the client/services segment directly,

I don't see the reason why a) I should do that because you will again tell me that we don't do enough; and b) yet again (tm) I'm telling you that RGB has nothing to do with the section of clients and services. Please let at least somewhat technical people like @harding that I repeatedly tagged, decide and analyse PRs and issues - clearly you are underqualified to do so.

I think your energy would best spent to get interesting RGB content posted to the public forums.

Sounds like a good idea as it does seem that Bitcoin Optech is a closed forum putting arbitrary demands to contributors and code, wasting everyone's time, driving contributors away and misleading the community on what's actually happening in the space. Great job, Mike!


Add feature to compute and plot Penrose diagrams

🐞 What bugs you?
Currently einsteinpy does not have the capability to compute and plot Penrose diagrams, which are 2-dimensional diagrams showing the causal relations between points in some spacetime. It would be good to implement some algorithm to add this feature. However, this will require some work on the null geodesics for Schwarzschild and Kerr Geometries (a GSoC 2020 Project idea) to have completed in order to build on top of it.
🎯 Goal

To carry out some preliminary research on Penrose diagrams and its potential implementation as an einsteinpy feature, and present the results as an EinsteinPy Proposals for Enhancement (EPE) in the einsteinpy/EinsteinPy-EPEs repo.
💡 Possible solutions
An EPE will be drafted in collaboration with @Raahul-Singh and @GTron-1729 with the theoretical background and potential solution(s) of implementation to be presented as a PR in the einsteinpy/EinsteinPy-EPEs repo.

📋  Steps to solve the problem

Research on the problem
Investigate potential implementation approaches best suited for einsteinpy to incorporate such a feature into the codebase
Present the findings in an EPE

📖  References

J. C. Schindler, A. Aguirre (2018), Algorithms for the explicit computation of Penrose diagrams
An existing implementation of a very similar idea at https://github.com/jcschindler01/xhorizon
M. Walker (1970), Block Diagrams and the Extension of Timelike Two‐Surfaces
A related Physics StackExchange page
Penrose diagram Wikipedia page
S. W. Hawking , G. F. R. Ellis (1973), The Large Scale Structure of Space-Time
S. M. Carroll (2019), Spacetime and Geometry: An Introduction to General Relativity
https://jila.colorado.edu/~ajsh/insidebh/penrose.html

Found a free ebook "The Large Scale Structure of Space-Time" by S. W. Hawking , G. F. R. Ellis that will be useful for us. Their Chapter 5 is on "Exact Solutions" with many examples of Penrose Diagrams. I have added this resource to No. 6 of the References above.

Found a more modern text by Sean Carroll titled "Spacetime and Geometry: An Introduction to General Relativity" published in 2019. Their Appendix H is dedicated to Conformal Diagrams which is especially suitable for our work in terms of the theoretical background. This has been added as reference No. 7 in the issue description above.

Hi everyone so can we do this using  pyqtgraph which makes animated 3D visualisation easier once we obtain the 2D points to be plotted after penrose coordinates are found further we can integrate this into the existing plotting library.

Hello there, well I don't see how 3D visualization would be useful because Penrose diagrams are a 2D representation of  4D SpaceTime. Also the diagrams need to be drawn for Schwarzschild, Kerr and other different metrics. To reach a Penrose diagram for a certain metric several equations get involved. So plotting those equations is done more easily and efficiently using Matplotlib or maybe Matlab even. For a clear idea, you could find the comparisons between Matplotlib and Pyqtgraph here --> https://python.libhunt.com/compare-matplotlib-vs-pyqtgraph
So moving forward with Matplotlib would be convenient.
Thanks for showing interest though!


Error Handling for File Upload

Issue: The background image upload lacks error handling (e.g., if a file is not an image).
Suggestion: Add a check to verify the file type before processing it.
please assign me this issue under gssoc and hacktober fest

Sure!


typo fix in prediction page example

Description
Updated useWecam to useWebcam in PagePrediction container.

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[x] My code is being merged to master so i've updated the package.json version.
[x] I have updated the documentation accordingly.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.

Thanks for the spell check. I'll also update the example app on the seperate repo soon.


demo: modify the release image without creating a new container image

This exports all manifests to the VM disk, modify them, and then mount
them in the CVO pod.

This is an alternative to a previous experiment where I needed to upload a new release image.
This attempt is far less simple!
/hold

/retest

/retest

 + ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -i id_ecdsa_crc<EMAIL_ADDRESS>-- sudo KUBECONFIG=/opt/kubeconfig oc rsync -n openshift-cluster-version pod/cluster-version-operator-8668d7dbd8-wgrg9:/release-manifests/ /opt/release-manifests/
Warning: Permanently added 'api.crc.testing,<IP_ADDRESS>' (ECDSA) to the list of known hosts.
WARNING: cannot use rsync: rsync not available in container
WARNING: cannot use tar: tar not available in container
error: No available strategies to copy.

Fails in the CI but works for me with 4.7.0-rc3 bundle :thinking:

/retest

/retest this please

/retest

 + ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -i id_ecdsa_crc<EMAIL_ADDRESS>-- sudo KUBECONFIG=/opt/kubeconfig oc rsync -n openshift-cluster-version pod/cluster-version-operator-8668d7dbd8-wgrg9:/release-manifests/ /opt/release-manifests/
Warning: Permanently added 'api.crc.testing,<IP_ADDRESS>' (ECDSA) to the list of known hosts.
WARNING: cannot use rsync: rsync not available in container
WARNING: cannot use tar: tar not available in container
error: No available strategies to copy.

Fails in the CI but works for me with 4.7.0-rc3 bundle

@guillaumerose you do need to use '' on the ssh command like I said https://github.com/code-ready/snc/pull/340#discussion_r580945383 here.

Closed in favor of https://github.com/code-ready/snc/pull/342


[#naver/pinpoint-docker#69]Update Readme.md

Line number 49 and 50 order changes.

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

Thank you for your contribution :)