Quickstart needs update

from featurex.stims import VideoStim
---------------------------------------------------------------------------
ImportError                               Traceback (most recent call last)
<ipython-input-2-fd7d648ab17b> in <module>()
----> 1 from featurex.stims import VideoStim

ImportError: No module named stims

I've started work on a completely revamped README, so this should be addressed soon.

Duplicates #18, and I'm planning to push a massively revamped README in a few days, so closing this.


Add checks to ensure required files/directories exist

Add checks to create directories and files, and/or warn the user they don't have the required files (ex. netflix dataset downloaded, eventually recommendation model checkpoint file, etc.). Currently, we just run the program until it fails (ex. whole processing script runs and then no "/out" directory exists). I'm sure this is a obvious issue, but I thought I'd document it so we don't forget + can discuss file structure.
I think this could be added to #28, but we might want to have an extendable way to check for files we require isolated to a designated file.

Yes, we should create the required directories here: https://github.com/noisebridge/MediaBridge/blob/main/mediabridge/data_processing/wiki_to_netflix.py#L14-L15
os.makedirs(data_dir, exist_ok=True), same thing for out_dir.

As far as not having the Netflix data, we could definitely add some code that downloads it and decompresses it to the right location. Or we can just wrap the part that tries to read the movie titles in a try...except and print a more useful message ("It seems you don't have the Netflix dataset download, please get it from https://....").


Is there a driver for zigbee vibration sensors? How can I add a vibration device to SmartThings？

Hi @1joyce! "Vibration Sensors" aren't really well defined in the Zigbee world. They exist but most of them work by providing post-processing over an acceleration sensor.
An example of an existing Zigbee device that provides a vibration notification on our platform is the Zigbee Contact Sensor's Multisensor profile: https://github.com/SmartThingsCommunity/SmartThingsEdgeDrivers/blob/main/drivers/SmartThings/zigbee-contact/profiles/multi-sensor.yml
Because we are very busy in the migration process of moving our legacy DTH integrations over to our new Edge Drivers platform, we'd like to keep this issue tracker limited to issues that are identifying bugs that have been found in the edge driver code, as per this pinned issue: https://github.com/SmartThingsCommunity/SmartThingsEdgeDrivers/issues/642
I would very much encourage you to re-open this question on the community forums, though, where you'll find that there are both very helpful power users as well as SmartThings developers available to guide you towards more information on integrating your sensor with our platform!


Nh revisit start and tree

@solomonhawk and @mzlock found some fun issues in transaction history that would cause store handlers to execute more times than expected. We've addressed that in the latest beta release (9.14.1-beta), however I wanted to rethink this a bit.
There are a couple of changes:

Do not re-evaluate state when a store is added. In future releases, I may consider throwing an error if a store is added after a Microcosm starts.
:start() pushes the willStart lifecycle action instead of resetting. This sounds pretty obvious, I'm not sure why it wasn't this way before.
Removed some null optimization checks that aren't necessary.

:+1:


Set persist sandbox to false for evaluations

Close since https://github.com/OpenDevin/OpenDevin/pull/2139 disables persist sandbox by default.


[$250] Distance - Distance changes to incorrect value when waypoint is changed without saving

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

Version Number: 1.4.69-0
Reproducible in staging?: Y
Reproducible in production?: Y
Logs: https://stackoverflow.com/c/expensify/questions/4856
Issue reported by: Applause-Internal team
Action Performed:

Go to staging.new.expensify.com
Go to workspace chat.
Submit a distance expense.
Go to transaction thread.
Click Distance.
Edit either the start or end location but do not save it.

Expected Result:
Distance row in the background will not change because the new distance is not saved.
Actual Result:
Distance row in the background changes and the distance is incorrect.
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

Screenshots/Videos
https://github.com/Expensify/App/assets/115492554/84c4e661-19b9-4529-92db-eebb94c060db

View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~017033137f73d95d13
Upwork Job ID:<PHONE_NUMBER>874479104
Last Price Increase: 2024-06-19

We think this issue might be related to the #collect project.

Distance row in the background changes and the distance is incorrect.

Not reproducible:
https://github.com/Expensify/App/assets/59809993/933f67bf-66e8-4d22-88b9-cfb7d2dcfec3

I can't reproduce either. Closing since three of us cannot reproduce this. Please reopen if it's still an issue

This issue is still reproducible
Build 1.4.74-0
https://github.com/Expensify/App/assets/115492554/31bb2500-c426-49b5-8bfa-0244ce3cfbee

Looking for proposals

still cannot reproduce i am having the same behaviour as in here: https://github.com/Expensify/App/issues/41404#issuecomment-2093695682

Unable to reproduce the bug too

@izarutskaya are you still able to reproduce this?

Adding retest label to see if anyone can reproduce this still

Not overdue, waiting to see if anyone else can reproduce this

I'll test this tomorrow

I can reproduce this on prod
https://github.com/Expensify/App/assets/17131195/12954cb3-5a7f-4cb2-9972-12fccc6fd03e

Still reproducible. Looking for proposals

looking for proposals

asking for proposals in slack

@eVoloshchak what do you think of the above proposal?

@nkdengineer's proposal does look good from a technical perspective, but I'm still unable to reproduce the issue on my end
@sonialiap, @nkdengineer, could you please share the exact steps you've used to reproduce this issue?

@eVoloshchak Did you enable P2PDistance beta?

@nkdengineer, that did the trick, thank you!
Why does this work correctly if the request is submitted to a workspace, but incorrectly if it's submitted to a user? Is BE the difference?

@eVoloshchak This bug here happens when we edit the waypoint of distance request in the WS.

I just checked and it also happens for P2P distance.

This bug happens when P2P distance is enabled. If this beta is disabled, we display the merchant of transaction that isn't changed when we edit the waypoint.  When the beta is enabled, the distance is displayed as the quantity of transaction that is changed (about why it's changed I mentioned in my proposal) when we edit the waypoint. That is how the bug happens and it's not a BE issue.

@nkdengineer's proposal looks good to me!
🎀👀🎀 C+ reviewed!

@eVoloshchak The PR is here. Jest test is failed on the latest main.

Not sure why automation didn't work, PR was deployed to staging four days ago, waiting for it to be deployed to prod

Payment summary:

@eVoloshchak $250 please request in ND - please complete the checklist
@nkdengineer $250 - paid in upwork ✔

@CortneyOfstad I'm OOO Aug 19-30, adding leave buddy.
Status: waiting for @eVoloshchak to complete the checklist and then we need to submit a new regression test issue to QA

bump @eVoloshchak

The PR that introduced the bug has been identified. Link to the PR: there isn't a PR that caused this, rather a limitation of the original implementation
The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment: N/A
A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion: N/A

Regression Test Proposal
Precondition: Enable P2PDistance beta

Create a distance request
Go to the combine report or transaction thread report
Click on distance
Select a new waypoint (do not click Save)
Verify that the distance in the money request view did not change

Do we agree 👍 or 👎

$250 approved for @eVoloshchak

Thanks @JmillsExpensify!

Payment Summary
@nkdengineer — paid $250 via Upwork
@eVoloshchak — paid $250 via NewDot
Regression Test
https://github.com/Expensify/Expensify/issues/422310


Containers on swarm-hosts not accessible via console in portainer 1.18

Bug description
Since upgrading from 1.17.1 to 1.18 I can no longer list or access (via console) containers that are running in the Docker Swarm but are not located on the host running Portainer.
I am using portainer-agent (and have set tasks.portainer_agent:9001 as the endpoint for portainer) and was previously able to access all consoles directly from portainer.
In 1.18 this seems to be no longer possible. Portainer is not behind a reverse proxy.
The containers view only shows containers that are located on the portainer-host itself.
Services-view lists all containers but any container not on portainer-host can only show logs.
Expected behavior
Remote console-access and listing of containers located anywhere in the swarm.
Steps to reproduce the issue:
Upgraded to portainer 1.18 from 1.17.1. latest agent.
Technical details:
I am using the following stack to deploy portainer and agents:
version: '3.2'
services:
portainer_agent:
image: portainer/agent
environment:
# REQUIRED: Should be equal to the service name prefixed by "tasks." when
# deployed inside an overlay network
AGENT_CLUSTER_ADDR: tasks.portainer_agent
# AGENT_PORT: 9001
# LOG_LEVEL: debug
volumes:
- /var/run/docker.sock:/var/run/docker.sock
ports:
- target: 9001
published: 9001
protocol: tcp
mode: host
networks:
- portainer_agent
deploy:
mode: global
labels:
- "logspout.exclude=true"
portainer:
image: portainer/portainer
command: -H tcp://tasks.portainer_agent:9001 --tlsskipverify
ports:
- "9000:9000"
volumes:
- portainerdata:/data
networks:
- portainer_agent
deploy:
mode: replicated
replicas: 1
placement:
constraints: [node.role == manager]
labels:
- "logspout.exclude=true"
networks:
portainer_agent:
driver: overlay
volumes:
portainerdata:
external: true

Portainer version: 1.18
Docker version (managed by Portainer): 18.03.1-ce
Platform (windows/linux): Ubuntu 16.04
Command used to start Portainer : stack deployment; see above for yml
Browser: Firefox, Edge

Hi @ijzerbroot
How did you upgrade Portainer? Also, what's the number of node reported in the dashboard when you connect to the agent endpoint?

Thank you for your quick response!
I upgraded by removing the existing stack and then creating it using the supplied yaml. (docker stack rm portainer && docker stack deploy -c yamlfile portainer). The number of nodes was correct (4 in my case)
I have in the meantime decided to reboot the swarm and it seems this fixes my issue!
I am now a bit concerned that the "bug" is not in fact a portainer-issue and I may have wasted your time, for which I apologize.
Shall i keep this one open in case you wish to determine whether the reboot is a necessity or rather a circumstantial site-specific issue ?
I should

All good, I will assume that the previous agent instances were not shut down properly and still holding information about the previously connected Portainer instance.
I'll close this issue as the problem is solved but we definitely need to write an upgrade procedure for the agent setup.

Thank you.
FWIW: I tried the procedure again (after reboot) but this time using a stack-redeployment rather than first removing it.
This time I did not need to reboot after going from 1.17.1 to 1.18. I am not sure if that would have worked the first time; it's quite possible my Linux-nodes or Docker were troublesome before the reboot; this swarm does get software-updates from time-to-time and I tend to not restart if there has not been a kernel-update. Perhaps I should have.
Thank you for an amazing product; it's generally behaved admirably :)

Thanks for the kind words @ijzerbroot
Note that we just found a bug with stacks in 1.18.0 (see #1998), it has been fixed and I'll release 1.18.1 soon !


deploy on serverless architecture

Someone experience with deploying this to serverless ?
AWS lambda has size restrictions to max of 512MB temp storage which is a problem.

Other options ? Because BERT can be GPU resource heavy if running fulltime

Hi. Also researching this. Found out that you can rather decrease the model requirements (aka use distilbert instead), or provision this yourself, try using cortex framework to ease the pain.


Default resource detector env var and add auto-instrumentation resource detector

Description
Follow up to #33305 and fix for #33295, and #33253. Changed resource detector behavior to only default the env var. This will allow customers to customize resource detectors and disable any that may cause issues.
Also, adding the app service detector to auto-insturmentation
All SDK Contribution checklist:

[x] The pull request does not introduce [breaking changes]
[x] CHANGELOG is updated for new features, bug fixes or other significant changes.
[x] I have read the contribution guidelines.

General Guidelines and Best Practices

[x] Title of the pull request is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[x] Pull request includes test coverage for the included changes.

API change check
API changes are not detected in this pull request.


(WIP) terminfo-extra: init

Motivation for this change
Headless systems may need extra terminfo definitions, but users would prefer not to have all the X11 baggage that the terminal emulators bring with them, making "just install the terminal" an unattractive option. This is a possible solution.
Marked as WIP because I'm not sure of the approach and would appreciate some feedback.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

Success on aarch64-linux (full log)
Attempted: terminfo-extra
Partial log (click to expand)
  /nix/store/6cizsv82y2sld7dbxgi82sqng448x7f5-rxvt-unicode-9.22.tar.bz2
copying path '/nix/store/6cizsv82y2sld7dbxgi82sqng448x7f5-rxvt-unicode-9.22.tar.bz2' from 'https://cache.nixos.org'...
copying path '/nix/store/5jraiq0sanzs4hpvp2gswb9jmk019s28-st-0.8.1.tar.gz' from 'https://cache.nixos.org'...
building '/nix/store/hx55k2c2mp7i1dbys7b0r6v29jpqhzdp-terminfo-extra.drv'...
unpacking source archive /nix/store/6cizsv82y2sld7dbxgi82sqng448x7f5-rxvt-unicode-9.22.tar.bz2
unpacking source archive /nix/store/5jraiq0sanzs4hpvp2gswb9jmk019s28-st-0.8.1.tar.gz
source root is .
setting SOURCE_DATE_EPOCH to timestamp<PHONE_NUMBER> of file ./.attr-0
warning: file ./.attr-0 may be generated; SOURCE_DATE_EPOCH may be non-deterministic
/nix/store/cljdsw9lwgsfx4kknprik1cwf968vf03-terminfo-extra

Success on x86_64-linux (full log)
Attempted: terminfo-extra
Partial log (click to expand)
  /nix/store/6cizsv82y2sld7dbxgi82sqng448x7f5-rxvt-unicode-9.22.tar.bz2
copying path '/nix/store/6cizsv82y2sld7dbxgi82sqng448x7f5-rxvt-unicode-9.22.tar.bz2' from 'https://cache.nixos.org'...
copying path '/nix/store/5jraiq0sanzs4hpvp2gswb9jmk019s28-st-0.8.1.tar.gz' from 'https://cache.nixos.org'...
building '/nix/store/f0gfhfss14nmdmwnm1zfsl6awrkkarfl-terminfo-extra.drv'...
unpacking source archive /nix/store/6cizsv82y2sld7dbxgi82sqng448x7f5-rxvt-unicode-9.22.tar.bz2
unpacking source archive /nix/store/5jraiq0sanzs4hpvp2gswb9jmk019s28-st-0.8.1.tar.gz
source root is .
setting SOURCE_DATE_EPOCH to timestamp<PHONE_NUMBER> of file ./.attr-0
warning: file ./.attr-0 may be generated; SOURCE_DATE_EPOCH may be non-deterministic
/nix/store/8c8a0zjv283wcxinb2ha8kjkmplhdnfh-terminfo-extra

Success on x86_64-darwin (full log)
Attempted: terminfo-extra
Partial log (click to expand)
  /nix/store/5jraiq0sanzs4hpvp2gswb9jmk019s28-st-0.8.1.tar.gz
  /nix/store/6cizsv82y2sld7dbxgi82sqng448x7f5-rxvt-unicode-9.22.tar.bz2
copying path '/nix/store/6cizsv82y2sld7dbxgi82sqng448x7f5-rxvt-unicode-9.22.tar.bz2' from 'https://cache.nixos.org'...
copying path '/nix/store/5jraiq0sanzs4hpvp2gswb9jmk019s28-st-0.8.1.tar.gz' from 'https://cache.nixos.org'...
building '/nix/store/ifyfly6w1gk5hbfpzcfs71prbpa8h379-terminfo-extra.drv'...
unpacking source archive /nix/store/6cizsv82y2sld7dbxgi82sqng448x7f5-rxvt-unicode-9.22.tar.bz2
unpacking source archive /nix/store/5jraiq0sanzs4hpvp2gswb9jmk019s28-st-0.8.1.tar.gz
source root is .
setting SOURCE_DATE_EPOCH to timestamp<PHONE_NUMBER> of file ./st-0.8.1/x.c
/nix/store/jgxpy8kvwwpqkiswd9pxpyfdx4lz8gx3-terminfo-extra

@tilpner suggested on IRC that this could accept any number of terminals as an argument and search their sources for terminfo definitions. I'm not sure there's a good heuristic we can use to find them, as searching the source trees for *.info may include GNU info pages.

I would prefer to move terminfo stuff to its own output. That should avoid this hack. We also discussed it here:
https://github.com/NixOS/nixpkgs/issues/40404#issuecomment-388815948

@matthewbauer If it is an output of ncurses I suspect it could easily lead to infinite cycles if ncurses is also needed to build the terminal emulator's dependencies.


OpenResty link for source installation instructions is broken

Here: https://getkong.org/install/source/
Links to openresty.com, should be openresty.org

Updated, thank you!


Fix downloads badge

pypip.in has been down for a while, but http://shields.io/ is another service.
This is the monthly badge; change dm to dw or dd for weekly or daily downloads.
[CI skip]

Thanks! :smiley_cat:


Add yarn related entries to gitignore

The problem
@FrancescoXX Switched to yarn for docusaurus'. Now we have these files that will be committed when someone runs yarn or yarn install in the project root

In my opinion, .yarn/ and .yarnrc.yml shouldn't be committed. yarn.lock however, should be committed. It ensures that all the developers on this project install the same package. See a post by yarn themselves

please handle this on the .gitignore file


Enable copy-pasting path into import file picker

I often look for binaries with the OS file explorer first, but if I then want to import a file into Ghidra, I have to do the entire navigation again within the file picker window.
The file picker has a sort of address bar, just let me paste into it like I can with Windows Explorer or Nautilus on Ubuntu.
Edit: I just noticed drag and drop works from Nautilus (it can be finicky on Linux sometimes), so...maybe it's not a super critical issue.

You should be able to paste a path into the "File name: " text field and then press Enter.  This will then move the chooser to that directory.

Yeah that works, though it's a little confusing from a UX perspective.
Is there anything that precludes the file picker's location textbox working that way (like hardcoded assumptions in the UI framework or something)?

Is there anything that precludes the file picker's location textbox working that way

Nope.  The file chooser UI was modeled after something in Windows XP.  Hard to believe, but it really hasn't changed much since then.

If I wanted to take a stab at making this a thing, where would I find the code?

The class is docking.widgets.filechooser.GFileChooser.   The code itself is probably not very difficult.  Trickier is dealing with the multithreaded nature of the filechooser.   It can be tricky to get that right.    There are a ton tests that you can run to verify you did't break anything.


"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" : "iPhone13,3",
               "identifier" : "8C990757-738C-46AF-A2C4-91E00A30AD90",
               "architecture" : "x86_64",
               "modelUTI" : "com.apple.iphone-12-pro-1",
               "modelName" : "iPhone 12 Pro",
               "name" : "iPhone 12 Pro"
             },
             {
               "simulator" : true,
               "operatingSystemVersion" : "13.5 (17F61)",
               "available" : true,
               "platform" : "com.apple.platform.iphonesimulator",
               "modelCode" : "iPhone10,5",
               "identifier" : "94DB95BB-62DB-48DE-B502-772B609E8FEA",
               "architecture" : "x86_64",
               "modelUTI" : "com.apple.iphone-8-plus-2",
               "modelName" : "iPhone 8 Plus",
               "name" : "iPhone 8 Plus"
             },
             {
               "simulator" : true,
               "operatingSystemVersion" : "14.0.1 (18A394)",
               "available" : true,
               "platform" : "com.apple.platform.iphonesimulator",
               "modelCode" : "iPhone12,5",
               "identifier" : "7A82F29E-E49E-4B3C-8609-1570361DBC17",
               "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" : "iPhone12,3",
               "identifier" : "50D474F4-8A73-41A7-A17C-0B046F7043B3",
               "architecture" : "x86_64",
               "modelUTI" : "com.apple.iphone-11-pro-1",
               "modelName" : "iPhone 11 Pro",
               "name" : "iPhone 11 Pro"
             },
             {
               "simulator" : true,
               "operatingSystemVersion" : "14.0.1 (18A394)",
               "available" : true,
               "platform" : "com.apple.platform.iphonesimulator",
               "modelCode" : "iPad8,9",
               "identifier" : "2FEF59F6-8E72-4FE1-A1B6-935588D65B49",
               "architecture" : "x86_64",
               "modelUTI" : "com.apple.ipad-pro-11-2nd-1",
               "modelName" : "iPad Pro (11-inch) (2nd generation)",
               "name" : "iPad Pro (11-inch) (2nd generation)"
             },
             {
               "simulator" : true,
               "operatingSystemVersion" : "14.4 (18D46)",
               "available" : true,
               "platform" : "com.apple.platform.iphonesimulator",
               "modelCode" : "iPhone13,4",
               "identifier" : "AE2F4F51-880E-44FB-BB29-171B766D9B54",
               "architecture" : "x86_64",
               "modelUTI" : "com.apple.iphone-12-pro-max-1",
               "modelName" : "iPhone 12 Pro Max",
               "name" : "iPhone 12 Pro Max"
             },
             {
               "simulator" : true,
               "operatingSystemVersion" : "12.4 (16G73)",
               "available" : true,
               "platform" : "com.apple.platform.iphonesimulator",
               "modelCode" : "iPad7,3",
               "identifier" : "32C0AA64-B0A2-45CD-83AD-F6DAAEBF6A83",
               "architecture" : "x86_64",
               "modelUTI" : "com.apple.ipad-pro-10point5-a1701-1",
               "modelName" : "iPad Pro (10.5-inch)",
               "name" : "iPad Pro (10.5-inch)"
             },
             {
               "simulator" : true,
               "operatingSystemVersion" : "13.5 (17F61)",
               "available" : true,
               "platform" : "com.apple.platform.iphonesimulator",
               "modelCode" : "iPhone12,5",
               "identifier" : "913ADC1E-400E-4AA0-8302-D955869FF1C9",
               "architecture" : "x86_64",
               "modelUTI" : "com.apple.iphone-11-pro-max-1",
               "modelName" : "iPhone 11 Pro Max",
               "name" : "iPhone 11 Pro Max"
             },
             {
               "simulator" : true,
               "operatingSystemVersion" : "14.3 (18K559)",
               "available" : true,
               "platform" : "com.apple.platform.appletvsimulator",
               "modelCode" : "AppleTV5,3",
               "identifier" : "3BAE9B02-C16A-47C0-BA91-A3B6F30D9A0F",
               "architecture" : "x86_64",
               "modelUTI" : "com.apple.apple-tv-4",
               "modelName" : "Apple TV",
               "name" : "Apple TV"
             },
             {
               "simulator" : true,
               "operatingSystemVersion" : "12.4 (16G73)",
               "available" : true,
               "platform" : "com.apple.platform.iphonesimulator",
               "modelCode" : "iPad7,1",
               "identifier" : "FF691497-7BF0-4016-9F99-ABFFA7DAEEA2",
               "architecture" : "x86_64",
               "modelUTI" : "com.apple.ipad-pro-a1670-1",
               "modelName" : "iPad Pro (12.9-inch) (2nd generation)",
               "name" : "iPad Pro (12.9-inch) (2nd generation)"
             },
             {
               "simulator" : true,
               "operatingSystemVersion" : "14.0.1 (18A394)",
               "available" : true,
               "platform" : "com.apple.platform.iphonesimulator",
               "modelCode" : "iPhone12,1",
               "identifier" : "F956DEEF-6F7C-4D24-ABFF-7E6FFF1A29CD",
               "architecture" : "x86_64",
               "modelUTI" : "com.apple.iphone-11-1",
               "modelName" : "iPhone 11",
               "name" : "iPhone 11"
             },
             {
               "simulator" : true,
               "operatingSystemVersion" : "13.1 (17A844)",
               "available" : true,
               "platform" : "com.apple.platform.iphonesimulator",
               "modelCode" : "iPad8,1",
               "identifier" : "F70314A8-F9E8-437D-B4B7-540B6A2630F6",
               "architecture" : "x86_64",
               "modelUTI" : "com.apple.ipad-pro-11-1",
               "modelName" : "iPad Pro (11-inch) (1st generation)",
               "name" : "iPad Pro (11-inch) (1st generation)"
             },
             {
               "simulator" : true,
               "operatingSystemVersion" : "12.4 (16G73)",
               "available" : true,
               "platform" : "com.apple.platform.iphonesimulator",
               "modelCode" : "iPhone9,1",
               "identifier" : "AD614B0F-5B2E-4559-9B72-4109082755D0",
               "architecture" : "x86_64",
               "modelUTI" : "com.apple.iphone-7-1",
               "modelName" : "iPhone 7",
               "name" : "iPhone 7"
             },
             {
               "simulator" : true,
               "operatingSystemVersion" : "12.4 (16G73)",
               "available" : true,
               "platform" : "com.apple.platform.iphonesimulator",
               "modelCode" : "iPhone11,8",
               "identifier" : "6A5511DC-C7B4-461E-BE3B-141A9BFBC5E5",
               "architecture" : "x86_64",
               "modelUTI" : "com.apple.iphone-xr-1",
               "modelName" : "iPhone Xʀ",
               "name" : "iPhone Xʀ"
             },
             {
               "simulator" : true,
               "operatingSystemVersion" : "12.4 (16G73)",
               "available" : true,
               "platform" : "com.apple.platform.iphonesimulator",
               "modelCode" : "iPhone6,1",
               "identifier" : "95930E62-4213-4186-9B74-3D8E81839A6E",
               "architecture" : "x86_64",
               "modelUTI" : "com.apple.iphone-5s-a1453-d4c5b3",
               "modelName" : "iPhone 5s",
               "name" : "iPhone 5s"
             },
             {
               "simulator" : true,
               "operatingSystemVersion" : "14.3 (18K559)",
               "available" : true,
               "platform" : "com.apple.platform.appletvsimulator",
               "modelCode" : "AppleTV6,2",
               "identifier" : "F61ECB7E-0342-4DDA-B4C8-AF6C234711BD",
               "architecture" : "x86_64",
               "modelUTI" : "com.apple.apple-tv-4k",
               "modelName" : "Apple TV 4K (at 1080p)",
               "name" : "Apple TV 4K (at 1080p)"
             },
             {
               "simulator" : true,
               "operatingSystemVersion" : "14.4 (18D46)",
               "available" : true,
               "platform" : "com.apple.platform.iphonesimulator",
               "modelCode" : "iPod9,1",
               "identifier" : "F1CA8543-7379-43FC-8F3E-E8389396E69F",
               "architecture" : "x86_64",
               "modelUTI" : "com.apple.ipod-touch-7-2",
               "modelName" : "iPod touch (7th generation)",
               "name" : "iPod touch (7th generation)"
             },
             {
               "simulator" : true,
               "operatingSystemVersion" : "12.4 (16G73)",
               "available" : true,
               "platform" : "com.apple.platform.iphonesimulator",
               "modelCode" : "iPhone10,4",
               "identifier" : "4E22D24A-10BF-4BEF-BB62-F12486CC7EB2",
               "architecture" : "x86_64",
               "modelUTI" : "com.apple.iphone-8-2",
               "modelName" : "iPhone 8",
               "name" : "iPhone 8"
             },
             {
               "simulator" : true,
               "operatingSystemVersion" : "14.4 (18D46)",
               "available" : true,
               "platform" : "com.apple.platform.iphonesimulator",
               "modelCode" : "iPad11,7",
               "identifier" : "FDD5F840-BF62-4D00-979C-A3AE6BD1389C",
               "architecture" : "x86_64",
               "modelUTI" : "com.apple.ipad-8-wwan-1",
               "modelName" : "iPad (8th generation)",
               "name" : "iPad (8th generation)"
             },
             {
               "simulator" : true,
               "operatingSystemVersion" : "13.5 (17F61)",
               "available" : true,
               "platform" : "com.apple.platform.iphonesimulator",
               "modelCode" : "iPad7,12",
               "identifier" : "298A16E3-E27E-4227-A001-A2F6D0636497",
               "architecture" : "x86_64",
               "modelUTI" : "com.apple.ipad-7-wwan-1",
               "modelName" : "iPad (7th generation)",
               "name" : "iPad (7th generation)"
             },
             {
               "simulator" : true,
               "operatingSystemVersion" : "14.0.1 (18A394)",
               "available" : true,
               "platform" : "com.apple.platform.iphonesimulator",
               "modelCode" : "iPhone12,8",
               "identifier" : "73F44B09-DA2A-4628-8066-45AD173AD649",
               "architecture" : "x86_64",
               "modelUTI" : "com.apple.iphone-se-1",
               "modelName" : "iPhone SE (2nd generation)",
               "name" : "iPhone SE (2nd generation)"
             },
             {
               "simulator" : true,
               "operatingSystemVersion" : "14.0.1 (18A394)",
               "available" : true,
               "platform" : "com.apple.platform.iphonesimulator",
               "modelCode" : "iPhone12,3",
               "identifier" : "0FC01CE8-FEF7-4AE2-96EC-982E6E5CC80D",
               "architecture" : "x86_64",
               "modelUTI" : "com.apple.iphone-11-pro-1",
               "modelName" : "iPhone 11 Pro",
               "name" : "iPhone 11 Pro"
             },
             {
               "simulator" : true,
               "operatingSystemVersion" : "14.4 (18D46)",
               "available" : true,
               "platform" : "com.apple.platform.iphonesimulator",
               "modelCode" : "iPad6,4",
               "identifier" : "72D9AC36-F758-4328-9EFD-745C134AE1B2",
               "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" : "13.1 (17A844)",
               "available" : true,
               "platform" : "com.apple.platform.iphonesimulator",
               "modelCode" : "iPhone10,5",
               "identifier" : "E69523B7-45D8-41D9-B433-A421846532BB",
               "architecture" : "x86_64",
               "modelUTI" : "com.apple.iphone-8-plus-2",
               "modelName" : "iPhone 8 Plus",
               "name" : "iPhone 8 Plus"
             },
             {
               "simulator" : true,
               "operatingSystemVersion" : "12.4 (16G73)",
               "available" : true,
               "platform" : "com.apple.platform.iphonesimulator",
               "modelCode" : "iPad5,4",
               "identifier" : "63922EBD-0B5E-4687-8F24-190B2B412BED",
               "architecture" : "x86_64",
               "modelUTI" : "com.apple.ipad-air2-a1567-b4b5b9",
               "modelName" : "iPad Air 2",
               "name" : "iPad Air 2"
             },
             {
               "simulator" : true,
               "operatingSystemVersion" : "12.4 (16G73)",
               "available" : true,
               "platform" : "com.apple.platform.iphonesimulator",
               "modelCode" : "iPhone8,1",
               "identifier" : "6DD666D6-A7F5-4864-A271-7DED3BAA62DF",
               "architecture" : "x86_64",
               "modelUTI" : "com.apple.iphone-6s-b9b7ba",
               "modelName" : "iPhone 6s",
               "name" : "iPhone 6s"
             },
             {
               "simulator" : true,
               "operatingSystemVersion" : "12.4 (16G73)",
               "available" : true,
               "platform" : "com.apple.platform.iphonesimulator",
               "modelCode" : "iPhone11,4",
               "identifier" : "76CE5B21-A134-4B32-A007-5593E5221893",
               "architecture" : "x86_64",
               "modelUTI" : "com.apple.iphone-xs-max-1",
               "modelName" : "iPhone Xs Max",
               "name" : "iPhone Xs Max"
             },
             {
               "simulator" : true,
               "operatingSystemVersion" : "12.4 (16G73)",
               "available" : true,
               "platform" : "com.apple.platform.iphonesimulator",
               "modelCode" : "iPhone7,2",
               "identifier" : "9920DED2-1303-4945-AE55-06DB955E481F",
               "architecture" : "x86_64",
               "modelUTI" : "com.apple.iphone-6-b4b5b9",
               "modelName" : "iPhone 6",
               "name" : "iPhone 6"
             },
             {
               "simulator" : true,
               "operatingSystemVersion" : "14.4 (18D46)",
               "available" : true,
               "platform" : "com.apple.platform.iphonesimulator",
               "modelCode" : "iPhone10,5",
               "identifier" : "EBA56873-1468-42C9-A006-24D0B5134D60",
               "architecture" : "x86_64",
               "modelUTI" : "com.apple.iphone-8-plus-2",
               "modelName" : "iPhone 8 Plus",
               "name" : "iPhone 8 Plus"
             },
             {
               "simulator" : true,
               "operatingSystemVersion" : "14.0.1 (18A394)",
               "available" : true,
               "platform" : "com.apple.platform.iphonesimulator",
               "modelCode" : "iPad6,4",
               "identifier" : "4B6E9A66-897D-4824-8F46-502AB879D60E",
               "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" : "12.4 (16G73)",
               "available" : true,
               "platform" : "com.apple.platform.iphonesimulator",
               "modelCode" : "iPad6,12",
               "identifier" : "88820B37-98C4-442C-9ABA-0915263EBA41",
               "architecture" : "x86_64",
               "modelUTI" : "com.apple.ipad-gen5-a1823-1",
               "modelName" : "iPad (5th generation)",
               "name" : "iPad (5th generation)"
             },
             {
               "simulator" : true,
               "operatingSystemVersion" : "14.3 (18K559)",
               "available" : true,
               "platform" : "com.apple.platform.appletvsimulator",
               "modelCode" : "AppleTV6,2",
               "identifier" : "05148B81-88CC-4560-900C-4996743952D6",
               "architecture" : "x86_64",
               "modelUTI" : "com.apple.apple-tv-4k",
               "modelName" : "Apple TV 4K",
               "name" : "Apple TV 4K"
             },
             {
               "simulator" : true,
               "operatingSystemVersion" : "13.5 (17F61)",
               "available" : true,
               "platform" : "com.apple.platform.iphonesimulator",
               "modelCode" : "iPad8,9",
               "identifier" : "A78537CF-2CCC-4D2B-B58B-F582AE700B01",
               "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" : "12.4 (16G73)",
               "available" : true,
               "platform" : "com.apple.platform.iphonesimulator",
               "modelCode" : "iPad8,5",
               "identifier" : "61D447E5-A020-43DD-9A40-7B6FD74337D2",
               "architecture" : "x86_64",
               "modelUTI" : "com.apple.ipad-pro-12point9-1",
               "modelName" : "iPad Pro (12.9-inch) (3rd generation)",
               "name" : "iPad Pro (12.9-inch) (3rd generation)"
             },
             {
               "simulator" : true,
               "operatingSystemVersion" : "14.4 (18D46)",
               "available" : true,
               "platform" : "com.apple.platform.iphonesimulator",
               "modelCode" : "iPad8,9",
               "identifier" : "FA649C2F-C617-4DDB-82D0-0AE656BE4871",
               "architecture" : "x86_64",
               "modelUTI" : "com.apple.ipad-pro-11-2nd-1",
               "modelName" : "iPad Pro (11-inch) (2nd generation)",
               "name" : "iPad Pro (11-inch) (2nd generation)"
             },
             {
               "simulator" : true,
               "operatingSystemVersion" : "14.4 (18D46)",
               "available" : true,
               "platform" : "com.apple.platform.iphonesimulator",
               "modelCode" : "iPhone12,5",
               "identifier" : "D4039885-904C-45EE-BDF6-23102966E15E",
               "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" : "iPhone13,1",
               "identifier" : "2836CE65-87C5-43F9-8D0A-84FBDDD65B03",
               "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" : "iPad8,12",
               "identifier" : "0DBA537F-6AD3-4707-A16D-27D532931CB6",
               "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" : "13.5 (17F61)",
               "available" : true,
               "platform" : "com.apple.platform.iphonesimulator",
               "modelCode" : "iPad11,3",
               "identifier" : "CF37AB2F-A322-48A1-AD89-3C110DF70EA9",
               "architecture" : "x86_64",
               "modelUTI" : "com.apple.ipad-air3-wifi-1",
               "modelName" : "iPad Air (3rd generation)",
               "name" : "iPad Air (3rd generation)"
             },
             {
               "simulator" : true,
               "operatingSystemVersion" : "12.4 (16G73)",
               "available" : true,
               "platform" : "com.apple.platform.iphonesimulator",
               "modelCode" : "iPhone8,2",
               "identifier" : "34650EA5-E2A6-4117-ADA7-437DFA725138",
               "architecture" : "x86_64",
               "modelUTI" : "com.apple.iphone-6s-plus-b9b7ba",
               "modelName" : "iPhone 6s Plus",
               "name" : "iPhone 6s Plus"
             },
             {
               "simulator" : true,
               "operatingSystemVersion" : "14.0.1 (18A394)",
               "available" : true,
               "platform" : "com.apple.platform.iphonesimulator",
               "modelCode" : "iPhone10,4",
               "identifier" : "B62AC598-23C6-40FA-9F65-5680C7D338DC",
               "architecture" : "x86_64",
               "modelUTI" : "com.apple.iphone-8-2",
               "modelName" : "iPhone 8",
               "name" : "iPhone 8"
             },
             {
               "simulator" : true,
               "operatingSystemVersion" : "12.4 (16G73)",
               "available" : true,
               "platform" : "com.apple.platform.iphonesimulator",
               "modelCode" : "iPad8,1",
               "identifier" : "468EE1DF-2DF5-4320-B54C-A74748F78493",
               "architecture" : "x86_64",
               "modelUTI" : "com.apple.ipad-pro-11-1",
               "modelName" : "iPad Pro (11-inch) (1st generation)",
               "name" : "iPad Pro (11-inch) (1st generation)"
             },
             {
               "simulator" : true,
               "operatingSystemVersion" : "14.4 (18D46)",
               "available" : true,
               "platform" : "com.apple.platform.iphonesimulator",
               "modelCode" : "iPhone12,8",
               "identifier" : "70C4B6C7-4746-4D93-B7B2-6FE11017EA99",
               "architecture" : "x86_64",
               "modelUTI" : "com.apple.iphone-se-1",
               "modelName" : "iPhone SE (2nd generation)",
               "name" : "iPhone SE (2nd generation)"
             },
             {
               "simulator" : true,
               "operatingSystemVersion" : "14.0.1 (18A394)",
               "available" : true,
               "platform" : "com.apple.platform.iphonesimulator",
               "modelCode" : "iPhone10,5",
               "identifier" : "5372BBB9-3E3B-4457-AC76-2C82E9A9C033",
               "architecture" : "x86_64",
               "modelUTI" : "com.apple.iphone-8-plus-2",
               "modelName" : "iPhone 8 Plus",
               "name" : "iPhone 8 Plus"
             },
             {
               "simulator" : true,
               "operatingSystemVersion" : "13.1 (17A844)",
               "available" : true,
               "platform" : "com.apple.platform.iphonesimulator",
               "modelCode" : "iPad8,5",
               "identifier" : "ABA8D4B4-8F2A-4237-9AE9-B436CD3CF043",
               "architecture" : "x86_64",
               "modelUTI" : "com.apple.ipad-pro-12point9-1",
               "modelName" : "iPad Pro (12.9-inch) (3rd generation)",
               "name" : "iPad Pro (12.9-inch) (3rd generation)"
             },
             {
               "simulator" : true,
               "operatingSystemVersion" : "13.5 (17F61)",
               "available" : true,
               "platform" : "com.apple.platform.iphonesimulator",
               "modelCode" : "iPhone12,3",
               "identifier" : "8A9959EF-0C07-4B1B-AB51-AEE8D2689674",
               "architecture" : "x86_64",
               "modelUTI" : "com.apple.iphone-11-pro-1",
               "modelName" : "iPhone 11 Pro",
               "name" : "iPhone 11 Pro"
             },
             {
               "simulator" : true,
               "operatingSystemVersion" : "13.5 (17F61)",
               "available" : true,
               "platform" : "com.apple.platform.iphonesimulator",
               "modelCode" : "iPad6,4",
               "identifier" : "EFDB7606-244A-495B-BA73-71B4CAC2AC8F",
               "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" : "12.4 (16G73)",
               "available" : true,
               "platform" : "com.apple.platform.iphonesimulator",
               "modelCode" : "iPhone8,4",
               "identifier" : "39B28A0E-5BA1-4479-822D-2A5014D2BDE6",
               "architecture" : "x86_64",
               "modelUTI" : "com.apple.iphone-se-a1662-aeb1b8",
               "modelName" : "iPhone SE (1st generation)",
               "name" : "iPhone SE (1st generation)"
             },
             {
               "simulator" : true,
               "operatingSystemVersion" : "13.1 (17A844)",
               "available" : true,
               "platform" : "com.apple.platform.iphonesimulator",
               "modelCode" : "iPad11,3",
               "identifier" : "753BD72B-77AB-4115-8013-23832911DC74",
               "architecture" : "x86_64",
               "modelUTI" : "com.apple.ipad-air3-wifi-1",
               "modelName" : "iPad Air (3rd generation)",
               "name" : "iPad Air (3rd generation)"
             },
             {
               "simulator" : true,
               "operatingSystemVersion" : "12.4 (16G73)",
               "available" : true,
               "platform" : "com.apple.platform.iphonesimulator",
               "modelCode" : "iPhone11,2",
               "identifier" : "C11F120D-CE67-4C86-834E-332B9653BA65",
               "architecture" : "x86_64",
               "modelUTI" : "com.apple.iphone-xs-1",
               "modelName" : "iPhone Xs",
               "name" : "iPhone Xs"
             },
             {
               "simulator" : true,
               "operatingSystemVersion" : "13.1 (17A844)",
               "available" : true,
               "platform" : "com.apple.platform.iphonesimulator",
               "modelCode" : "iPhone12,1",
               "identifier" : "309C799F-99AC-458F-AC37-D5F1D05D8DB0",
               "architecture" : "x86_64",
               "modelUTI" : "com.apple.iphone-11-1",
               "modelName" : "iPhone 11",
               "name" : "iPhone 11"
             },
             {
               "simulator" : true,
               "operatingSystemVersion" : "13.1 (17A844)",
               "available" : true,
               "platform" : "com.apple.platform.iphonesimulator",
               "modelCode" : "iPhone12,5",
               "identifier" : "805EA053-9354-4428-83C4-9ADF79DC6BD3",
               "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.0.1 (18A394)",
               "available" : true,
               "platform" : "com.apple.platform.iphonesimulator",
               "modelCode" : "iPod9,1",
               "identifier" : "56C8E046-1783-4616-B263-146C8ACEF6AD",
               "architecture" : "x86_64",
               "modelUTI" : "com.apple.ipod-touch-7-2",
               "modelName" : "iPod touch (7th generation)",
               "name" : "iPod touch (7th generation)"
             },
             {
               "simulator" : true,
               "operatingSystemVersion" : "14.0.1 (18A394)",
               "available" : true,
               "platform" : "com.apple.platform.iphonesimulator",
               "modelCode" : "iPad13,2",
               "identifier" : "A3695261-8F73-44DD-B54A-E2153115C06F",
               "architecture" : "x86_64",
               "modelUTI" : "com.apple.ipad-air4-1",
               "modelName" : "iPad Air (4th generation)",
               "name" : "iPad Air (4th generation)"
             },
             {
               "simulator" : true,
               "operatingSystemVersion" : "12.4 (16G73)",
               "available" : true,
               "platform" : "com.apple.platform.iphonesimulator",
               "modelCode" : "iPad6,4",
               "identifier" : "0A8886DA-D4FC-49AD-B37C-A87B62E1F409",
               "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" : "13.1 (17A844)",
               "available" : true,
               "platform" : "com.apple.platform.iphonesimulator",
               "modelCode" : "iPhone10,4",
               "identifier" : "16300A34-746B-4F40-BE91-868623998BA0",
               "architecture" : "x86_64",
               "modelUTI" : "com.apple.iphone-8-2",
               "modelName" : "iPhone 8",
               "name" : "iPhone 8"
             },
             {
               "simulator" : true,
               "operatingSystemVersion" : "13.5 (17F61)",
               "available" : true,
               "platform" : "com.apple.platform.iphonesimulator",
               "modelCode" : "iPhone12,8",
               "identifier" : "1AFB561A-79EA-4AFC-97A8-8B0335DD4141",
               "architecture" : "x86_64",
               "modelUTI" : "com.apple.iphone-se-1",
               "modelName" : "iPhone SE (2nd generation)",
               "name" : "iPhone SE (2nd generation)"
             },
             {
               "simulator" : true,
               "operatingSystemVersion" : "12.4 (16G73)",
               "available" : true,
               "platform" : "com.apple.platform.iphonesimulator",
               "modelCode" : "iPhone9,2",
               "identifier" : "BC85A6DE-D7AF-4AFC-960E-9D8CE7FFFC91",
               "architecture" : "x86_64",
               "modelUTI" : "com.apple.iphone-7-plus-1",
               "modelName" : "iPhone 7 Plus",
               "name" : "iPhone 7 Plus"
             },
             {
               "simulator" : true,
               "operatingSystemVersion" : "14.4 (18D46)",
               "available" : true,
               "platform" : "com.apple.platform.iphonesimulator",
               "modelCode" : "iPhone12,1",
               "identifier" : "6DC3D1E0-3BC2-49F7-93FB-2C40CBCF8E71",
               "architecture" : "x86_64",
               "modelUTI" : "com.apple.iphone-11-1",
               "modelName" : "iPhone 11",
               "name" : "iPhone 11"
             },
             {
               "simulator" : true,
               "operatingSystemVersion" : "14.0.1 (18A394)",
               "available" : true,
               "platform" : "com.apple.platform.iphonesimulator",
               "modelCode" : "iPad11,7",
               "identifier" : "A396D179-4F0E-4391-AFB5-6E1526C236F4",
               "architecture" : "x86_64",
               "modelUTI" : "com.apple.ipad-8-wwan-1",
               "modelName" : "iPad (8th generation)",
               "name" : "iPad (8th generation)"
             }
           ]
[ +244 ms] <- reset
[  +13 ms] /Users/pedromassango/Code/flutter_master/bin/cache/dart-sdk/bin/dart --disable-dart-dev /Users/pedromassango/Code/flutter_master/bin/cache/artifacts/engine/darwin-x64/frontend_server.dart.snapshot --sdk-root /Users/pedromassango/Code/flutter_master/bin/cache/flutter_web_sdk/ --incremental --target=dartdevc --debugger-module-names --experimental-emit-debug-metadata -DFLUTTER_WEB_AUTO_DETECT=true --output-dill /var/folders/ks/08wz1bwx12x69sbhqt14brh00000gp/T/flutter_tools.PXqDW3/flutter_tool.V4hZ9O/app.dill --libraries-spec file:///Users/pedromassango/Code/flutter_master/bin/cache/flutter_web_sdk/libraries.json --packages /Users/pedromassango/dev/Projects/flutter_example/.dart_tool/package_config.json -Ddart.vm.profile=false -Ddart.vm.product=false --enable-asserts --track-widget-creation --filesystem-root /var/folders/ks/08wz1bwx12x69sbhqt14brh00000gp/T/flutter_tools.PXqDW3/flutter_tools.rKtJsw --filesystem-scheme org-dartlang-app --initialize-from-dill build/b1b715402d823b7fd5c2b68d2edcb2ce.cache.dill.track.dill --platform file:///Users/pedromassango/Code/flutter_master/bin/cache/flutter_web_sdk/kernel/flutter_ddc_sdk_sound.dill --sound-null-safety
[  +11 ms] <- compile org-dartlang-app:/web_entrypoint.dart
[{"event":"app.progress","params":{"appId":"b92ad772-5731-41b9-a94d-d413c42505f9","id":"1","progressId":null,"finished":true}}]
[+23611 ms] Synced 28.6MB.
[   +1 ms] <- accept
[        ] Caching compiled dill
[ +422 ms] Using Google Chrome 90.0.4430.212

[ +303 ms] executing: sysctl hw.optional.arm64
[  +13 ms] Exit code 1 from: sysctl hw.optional.arm64
[        ] sysctl: unknown oid 'hw.optional.arm64'
[ +886 ms] [CHROME]:
[   +2 ms] [CHROME]:DevTools listening on ws://<IP_ADDRESS>:51794/devtools/browser/9cb147ce-9185-4ceb-ba80-3487455ec8ec
[{"event":"app.webLaunchUrl","params":{"url":"http://localhost:51771","launched":true}}]
[ +941 ms] DwdsInjector: Received request for entrypoint at http://localhost:51771/main_module.bootstrap.js
[  +20 ms] MetadataProvider: Loading debug metadata...
[  +67 ms] MetadataProvider: Loaded debug metadata (sound null safety)
[   +8 ms] DwdsInjector: Injected debugging metadata for entrypoint at http://localhost:51771/main_module.bootstrap.js
[+3142 ms] ChromeProxyService: Initializing expression compiler for main_module.bootstrap.js with sound null safety: true
[ +107 ms] DevHandler: Debug service listening on ws://<IP_ADDRESS>:51841/Zmc-ulHWyQA=/ws

[  +33 ms] This app is linked to the debug service: ws://<IP_ADDRESS>:51841/Zmc-ulHWyQA=/ws
[  +12 ms] Debug service listening on ws://<IP_ADDRESS>:51841/Zmc-ulHWyQA=/ws
[        ] 💪 Running with sound null safety 💪
[{"event":"app.started","params":{"appId":"b92ad772-5731-41b9-a94d-d413c42505f9"}}]
[{"event":"app.debugPort","params":{"appId":"b92ad772-5731-41b9-a94d-d413c42505f9","port":51841,"wsUri":"ws://<IP_ADDRESS>:51841/Zmc-ulHWyQA=/ws"}}]
[+1317 ms] DevTools activation throttled until 2021-05-14 22:31:44.997303.
[+81849 ms] DevHandler: Stopped debug service on ws://<IP_ADDRESS>:51839

[ +301 ms] Application finished.
[{"event":"app.stop","params":{"appId":"b92ad772-5731-41b9-a94d-d413c42505f9"}}]
[  +14 ms] "flutter run" took 119,140ms.
[ +260 ms] ensureAnalyticsSent: 256ms
[   +1 ms] Running shutdown hooks
[        ] Shutdown hooks complete
[        ] exiting with code 0

flutter doctor -v
/Users/pedromassango/Code/flutter_master/bin/flutter doctor --verbose
[✓] Flutter (Channel master, 2.3.0-2.0.pre.163, on macOS 11.2.3 20D91 darwin-x64, locale en-AO)
    • Flutter version 2.3.0-2.0.pre.163 at /Users/pedromassango/Code/flutter_master
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 298f18b592 (30 hours ago), 2021-05-12 20:50:14 -0700
    • Engine revision a339374296
    • Dart version 2.14.0 (build 2.14.0-109.0.dev)

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
    • Android SDK at /Users/pedromassango/Library/Android/sdk
    • Platform android-30, build-tools 30.0.2
    • ANDROID_HOME = /Users/pedromassango/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.4, Build version 12D4e
    • CocoaPods version 1.10.1

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.1)
    • 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 1.8.0_242-release-1644-b3-6915495)

[✓] IntelliJ IDEA Community Edition (version 2021.1)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 56.0.5
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart

[✓] VS Code (version 1.55.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.16.0

[✓] Connected device (2 available)
    • macOS (desktop) • macos  • darwin-x64     • macOS 11.2.3 20D91 darwin-x64
    • Chrome (web)    • chrome • web-javascript • Google Chrome 90.0.4430.212

• No issues found!

This still happens, any workaround for it?

me  too

hi, any workaround?

For now, my team just switched to fade instead of ellipsis.

I am using Open Sans and was able to fix this by including the font files as assets:
https://pub.dev/packages/google_fonts#bundling-font-files-in-your-applications-assets

I am experiencing this issue as well. Just adding my comment to hopefully keep this issue from being auto-closed. 🙂

I am also experiencing this issue, even when using GoogleFonts pub.dev package https://pub.dev/packages/google_fonts#bundling-font-files-in-your-applications-assets.

Same issue, it adds a weird icon after the three dots.
Text(
                      "This is a very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very long text.",
                      overflow: TextOverflow.ellipsis,
                      style: GoogleFonts.plusJakartaSans(fontSize: 25),
                    )

any update after like two years :)

any update?

still an issue for me

Still an issue in 2023.

my mean change default ellipsis character  to "..."

I am having  similar issue in Noto sans JP font,the ellipsis vertical alignment stays in the center instead of bottom.
 Text(                     "棟外わど育査とりを美付セコト激頭トひとが報29携オエロ通市図タヘ縮悲ば肉79交示布95申つふな。",                     style: context.bodyMedium?.copyWith(                         fontSize: 16.w,                         height: (21.72 / 16).w,                         fontWeight: FontWeight.w500,                         overflow: TextOverflow.ellipsis,                         color: Colors.black),                     maxLines: 1,                     // overflow: TextOverflow.ellipsis,                   ),


Update MSFT_xADDomain.psm1

Replacing code from v2.3 with the additional parameters for xADDomain.

Thanks @GoateePFE ,
Some of the common tests failed though: https://ci.appveyor.com/project/PowerShell/xactivedirectory/build/1.0.51
Looks like there are tabs instead of spaces in MSFT_xADDomain.psm1 file.
You can fix it by using one of our fixers:
Get-TextFilesList $pwd | ConvertTo-SPaceIndentation

from here:
https://github.com/powershell/dscresource.tests
Once it's done, please send those changes as another commit to this branch.
Thanks!

I removed the one tab from the file.  Please try to test and merge again.

Hello Karol,
This has been fixed.  Please retry.  Also, the patch-2 version of this file should be deleted as it is out of date significantly.
Thanks,
Ashley
From: KarolKaczmarek<EMAIL_ADDRESS>Sent: Wednesday, July 15, 2015 5:23 PM
To: PowerShell/xActiveDirectory
Cc: Ashley McGlone (GOATEEPFE)
Subject: Re: [xActiveDirectory] Update MSFT_xADDomain.psm1 (#22)
Thanks @GoateePFEhttps://github.com/GoateePFE ,
Some of the common tests failed though: https://ci.appveyor.com/project/PowerShell/xactivedirectory/build/1.0.51
Looks like there are tabs instead of spaces in MSFT_xADDomain.psm1 file.
You can fix it by using one of our fixers:
Get-TextFilesList $pwd | ConvertTo-SPaceIndentation
from here:
https://github.com/powershell/dscresource.tests
Once it's done, please send those changes as another commit to this branch.
Thanks!
—
Reply to this email directly or view it on GitHubhttps://github.com/PowerShell/xActiveDirectory/pull/22#issuecomment-121753595.

Tests are being run automatically by AppVeyor every time you add commit to the Pull Request.
You can see the current status at the bottom:
Some checks have failed — AppVeyor was unable to build non-mergeable pull request

We can’t automatically merge this pull request.

Use the command line to resolve conflicts before continuing.

However, as you can see there are some conflicts between your change and existing codebase which prevent tests from being run.
You can find instructions on how to resolve it here: http://githowto.com/resolving_conflicts
You should merge with dev branch and not master (as in the example from that link) though.
Having said that, I assume conflicts are caused because of merging previous PR: #16 which also modifies MSFT_xADDomain.psm1.
I briefly took a look at it and changes look very similar to what you are committing here. Can you please review them and see if we still want to add anything from this PR?
Thanks!

Deferring to Sergei's PR#9 changes that should fix this.


Release multihash to maven central

The build of dependent projects rely on this to be found on central or some other mvn repository. I can provide a PR that would allow to run
mvn release:prepare

I could then use the created tag to deploy it to central. Better still, someone else with appropriate authorization could run
mvn release:perform

Blocked by: https://github.com/multiformats/java-multibase/issues/7

wrong project, sorry


:hammer: Re-organize dependencies for local dev and CI

The 'hard' dependencies are now specified as extra groups in the setup.py package information. tox.ini points to these extras to install the required dependencies, and their supported version ranges.
The dev requirements file is now documented in the contributing guidelines, and makes use of the extras to pull in the optional dependencies for a full-blown local installation. The remaining dependencies (such as sphinx) are not used in tox and are still in the requirements_dev.txt file.
The linting dependencies (with upper bound versions) are now also specified as an extra group to prevent mismatching versions in tox env and local development envs.
Motivation and Context
pip install -r requirements_dev.txt lead to different versions of isort/flak8 being installed in local env and CI pipeline. While it
didn't cause problems yet, these are annoying to track down.
Additionally, when touching minimum required versions, it's hard to keep track of where the version numbers are all specified
and can lead to false negatives in the tests if there are things broken because one specification overrides another.
How Has This Been Tested?

Clean virtualenv
pip install -r requirements_dev.txt
make example-webauthn
tox

Screenshots (if appropriate):
n/a
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[x] Project maintenance

Checklist:

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

yeah, I wanted to mention that earlier but it involves some changes in build tooling too. we recently updated our own starter template to it, maybe @viicos wants to do this one :wink:

Sure thing, always happy to migrate projects to the new PEP 517/8


AVRO-3792 [java]: Fix comparison of Maps within GenericData (java).

What is the purpose of the change
2 bugs in comparing Maps within GenericData:

Comparison of size incorrectly compared map1 with map1 not map1 with map2.
When maps are empty an exception is incorrectly thrown (iterator().next() fails in that instance).

Verifying this change
This change added unit tests for empty and mismatched size maps.
Documentation

Does this pull request introduce a new feature? no

Duplicated by https://github.com/apache/avro/pull/2318


Command line table extraction is missing encoding info

Hello,
Web version extract beautifully tables with hebrew letters.
In the command line activation Hebrew letters becoming '?'.
Thanks, Yaakov.

How do you specify encoding on Windows? Using Windows 10, web OK but command line replaces Arabic text with ???


DB training with captions?

For Dreambooth training with this repo, can I label the images with full length captions instead of a name?
So instead of titles like:
'JJohn (1).png'
I would use:
'a man wearing a blue jumper, JJohn, in a forest on a sunny day, photorealist.png'?

Yes you can, separate the words with an underscore _
if you do the captioning, set the text encoder to 0%

Thanks

Yes you can, separate the words with an underscore _ if you do the captioning, set the text encoder to 0%

BRO, i was on my 15000 step and google close the Ssession EVEN ON PRO. and NOW I CANNOT LOAD becuase of ERRORS IN CODE??? JESUS WTF?

Yes you can, separate the words with an underscore _ if you do the captioning, set the text encoder to 0%

BRO, i was on my 15000 step and google close the Ssession EVEN ON PRO. and NOW I CANNOT LOAD becuase of ERRORS IN CODE??? JESUS WTF?

Three things:

Your comment is not related to the an open issue and not remotely related to this issue
You should never need to train 15000 steps
You do not pay for this software, you have no right to complain.

Yes you can, separate the words with an underscore _ if you do the captioning, set the text encoder to 0%

BRO, i was on my 15000 step and google close the Ssession EVEN ON PRO. and NOW I CANNOT LOAD becuase of ERRORS IN CODE??? JESUS WTF?

Three things:

Your comment is not related to the an open issue and not remotely related to this issue
You should never need to train 15000 steps
You do not pay for this software, you have no right to complain.

1 - i was replying to BEN because sometimes HE replies to me in OTHER POSTS also... so chill..
2 -  if i am training 150 photos, USING YOUR INSTRUCTIONS AS REFERENCE, i need 15000 steps
3 - I HAVE NO RIGHT TO COMPLAIN??? WTF?? OH WELL LET ME TELL YOU NOW i DO PAY google pro and i WILL BE GLAD TO PAY BEN ALSO IF HE WANTS ME TO PAY SOMETHING and get better access to error troubleshooting....  or even a custom page with WORKING CODES that wont change the next day as sometimes happens..... HOW COME YOU SAY I DONT HAVE RIGHT TO COMPLAIN if this is AN ISSUE PAGE TO REPORT ERRORS... WTF? are you ok bro?

Yes you can, separate the words with an underscore _ if you do the captioning, set the text encoder to 0%

BRO, i was on my 15000 step and google close the Ssession EVEN ON PRO. and NOW I CANNOT LOAD becuase of ERRORS IN CODE??? JESUS WTF?

Three things:

Your comment is not related to the an open issue and not remotely related to this issue
You should never need to train 15000 steps
You do not pay for this software, you have no right to complain.

i don't see your name on the REPO contributors nor people who work for this repo or collab, so WTH are you??? i was not talking to you. i already lost 20 computational units because of ERRORS MANY PEOPLE RE REPORTING... how come i don't have right to complain?

Yes you can, separate the words with an underscore _ if you do the captioning, set the text encoder to 0%

BRO, i was on my 15000 step and google close the Ssession EVEN ON PRO. and NOW I CANNOT LOAD becuase of ERRORS IN CODE??? JESUS WTF?

Three things:

Your comment is not related to the an open issue and not remotely related to this issue
You should never need to train 15000 steps
You do not pay for this software, you have no right to complain.

What now?? Money is an issue?? Ill BE GLAD TO PAY BEN HIMSELF!!! SO NOW WHAT????

ou should never need to train 15000 steps

Yes, the previous comment is not relevant to this thread, please vent your frustration elsewhere. However since its been mentioned:
Is there not a scenario where if you were to train a style or multiple concepts in Dreambooth you could train it beyond 15000 steps (if following a general rule of say 200 steps for every image with a low learning rate)?

There is, true, training mulitple concepts or people at the same time requires more steps.
Training two people I found it much better to use 2x 10 images, for a total of 2000 than 2x 40 images for a total of 2000

2

ou should never need to train 15000 steps

Yes, the previous comment is not relevant to this thread, please vent your frustration elsewhere. However since its been mentioned:
Is there not a scenario where if you were to train a style or multiple concepts in Dreambooth you could train it beyond 15000 steps (if following a general rule of say 200 steps for every image with a low learning rate)?

There is, true, training mulitple concepts or people at the same time requires more steps.
Training two people I found it much better to use 2x 10 images, for a total of 2000 than 2x 40 images for a total of 2000

ou should never need to train 15000 steps

Yes, the previous comment is not relevant to this thread, please vent your frustration elsewhere. However since its been mentioned:
Is there not a scenario where if you were to train a style or multiple concepts in Dreambooth you could train it beyond 15000 steps (if following a general rule of say 200 steps for every image with a low learning rate)?

There is, true, training mulitple concepts or people at the same time requires more steps.
Training two people I found it much better to use 2x 10 images, for a total of 2000 than 2x 40 images for a total of 2000

have you ever done DEEP FAKES IN YOUR LIFE?? i don't get the issue, its just MATH - "RECOMMENDED IMAGES 1 x 100 (or 200 actually) steps = 10 images then 1000 steps and 100 images then 10000 steps,,,, simple math, and YES if you use style and people combined then you need to work also the text encoder and steps count..... indeed. EVEN WORST, if you use a BIGGER MODEL like 768 then EVEN MORE TIME OR STEPS ARE SUGGESTED...
So Thanks for criticizing my training method then making an issue about it, cheers.... btw, i DID TIP BEN FOR THIS REPO... so CHILL. no need to me rude with your comments......


It's not open sites on port 8000 / 8080

If a blocked site (mostly iptv sites using that) has a main site in 80 port but iptv (or playlist) server on 8000 or 8080 port goodbyedpi works good on 80 port site/dashboard but  " Hmmm… can't reach this page / The connection was reset ." error happens on port 8000 site.
Edit: Non blocked 8000 / 8080 sites are opening when I use goodbyedpi normally.

Please make an provide network capture dump, here's the instruction: https://github.com/ValdikSS/GoodbyeDPI/wiki/How-to-make-traffic-dump-with-Wireshark

start "" goodbyedpi.exe -1 -w --port 8080 --port 8000 solves the issue thanks...


provide a canonical web-safe representation of a key

http://stackoverflow.com/questions/34875502/provide-web-safe-representation-of-key-that-i-can-use-to-look-up-the-entity

@eddavisson Any updates in the intervening years?

There's no single canonical URL-safe representation of a key, and we don't currently plan to define one.
Some specific client libraries do provide this functionality:

In the Java client, the Key class provides toUrlSafe and fromUrlSafe methods.

In ndb for Python 3, the Key class provides both urlsafe and to_legacy_urlsafe methods. The constructor accepts a serialized key as an input parameter.

The URL-safe formats used by the Java and Python libraries are not compatible with each other.


)HERE’S! WAY TO WATCH Tottenham Hotspur vs Aston Villa LIVE STREAMS Free ON TV CHANNEL 3 NOV 2024

1 Min AGo Tottenham host Aston Villa in a huge Premier League game at the Tottenham Hotspur Stadium.
CLICK HERE TO WATCH LIVE STREAM NOW
CLICK HERE TO WATCH LIVE STREAM NOW
CLICK HERE TO WATCH LIVE STREAM NOW
How to watch Tottenham vs Aston Villa online & on TV, head to head and predictions
Tottenham Hotspur is set to host Aston Villa at the Tottenham Hotspur Stadium in a Premier League clash on Sunday, 3 November 2024, with the match kicking off at 14:00. This match represents a significant fixture in the English football calendar, taking place in the state-of-the-art stadium located in London.
To watch, you must have a funded account at bet365 or a placed bet within the last 24h
In the UK, the match between Tottenham Hotspur and Aston Villa can be watched on Sky Sports Main Event, Sky Sports Premier League, and Sky Sports Ultra HDR.
Villa beat Spurs to Champions League qualification last season and will be dangerous opposition under Unai Emery.
While Spurs have impressed at times this season, consistency remains an issue and Villa are one of the form teams in the division.
CLICK HERE TO FOLLOW TOTTENHAM VS ASTON VILLA LIVE!
Spurs will kick-off down in 10th place but will go seventh with a win, while Villa could finish the weekend in third place behind Liverpool and Manchester City.
Here’s everything you need to know about where to watch the game later today.
How to watch Tottenham vs Aston Villa
TV channel: The game will be broadcast on Sky Sports Main Event, Sky Sports Premier League and Sky Sports Ultra HDR. Coverage starts at 1pm GMT ahead of a 2pm kick-off time.
Live stream: Subscribers will be able to watch on a live stream via the Sky Go app.
LIVE coverage: Follow all the action with Standard Sport’s dedicated match blog!
Read More

onfgre

fedr

ubpq

This is best option to Live Stream This Event, Follow Given Link for Free!👇👇👇
⭕📺📱💻👉CLICK HERE TO LIVE STREAM for Free
⭕📺📱💻👉CLICK HERE TO LIVE STREAM for Free


add get_vocabulary() to see the learned vocabulary

Added a cell in "Chapter13/Text Processing""
>>> text_vec_layer.get_vocabulary()
['', '[UNK]', 'be', 'to', 'the', 'thats', 'question']

Thanks for your PR! 👍
The diff is unfortunately too large for me to review. That's a problem with Jupyter notebooks + Git, they don't always play well together, especially when the outputs are included. Would you be so kind as to update the PR to only include the desired changes in the PR, without any changes to the rest of the notebook? Thanks a lot.


ODK Collect SSL connection?

Looking at the .env file for production mode it seems like by default ODK Collect connects unencrypted http via port 8443?
Is there a way to configure that more securely?
Thanks for the help!

yes, you should set all of those values (including http and www.example.com) in .env.production to match your own server; normally a website would default to using port 443 for secure HTTPS connections, in case that helps.

So this is not a direct connection that only ODK Collect uses? So I can just set it to my normal domain name with "https" and port 443 and everything goes through Nginx (which handles the SSL certificate)? Why mention ODK Collect specifically then?

Collect can connect to any website on any port, it just uses whatever you specify in your Collect settings. The NEMO docs mention Collect there specifically because in development it's useful to intentionally use an insecure port for local server debugging:

We default to a port of 8443 in development because ODK Collect can connect to that port over http without complaining about security. [but it can connect to any port, and generally requires the connection to be secure HTTPS except for on port 8443].

Updated docs on main branch! Thanks for the question.


how to use fterm

I want known how can i get something done like :FloatermNew --autoclose=0 gcc % -o %< && ./%:h, i know there's require("FTerm").run but i don't know , how can i get current buffer name , current buffer name without extension , current line number or something else . anyone knows if there a help manual?

Have a look at the lua API :h api

看看 lua API:h api

thank you for your reply and your work, i have not find much more useful information for there(just you can use nvim_buf_get_name() to get current buffer name), now i use vim.fn.expand("%:p:r") and similar things. thanks again!!

I am glad that it worked out for you. Nothing is better than reading vim help :)


ack-grep:: command not found:

I found a way to make ack-grep unusable.
vagrant@xenial ack-grep --version
ack 2.14
Running under Perl 5.22.1 at /usr/bin/perl

Copyright 2005-2014 Andy Lester.

This program is free software.  You may modify or distribute it
under the terms of the Artistic License v2.0.
vagrant@xenial ack-grep Foo().Bar
vagrant@xenial ack-grep
ack-grep:2: command not found: .Bar
vagrant@xenial ack-grep --version
ack-grep:3: command not found: .Bar

When reloading my terminal session ack-grep is back to normal again, but can be brought into the described unhealthy state again. The malicious expression is <A>().<B>. Thus Cat().Dog causes ack-grep to fail as well. I am on a Vagrant box.
vagrant@xenial uname -a
Linux xenial 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:33:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
vagrant@xenial cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04 LTS"

Thanks for the report.
It sounds to me like something weird in your shell.  What shell are you running? When I run ack like that I get:
$ ack Foo().Bar
-bash: syntax error near unexpected token `('

And it doesn't matter if it's ack.
$ ls Foo().Bar
-bash: syntax error near unexpected token `('
$ tar Foo().Bar
-bash: syntax error near unexpected token `('

What happens when you quote the arguments, as in:
ack 'Foo().Bar'

Thanks for coming back that quickly. It is indeed weird. I am on zsh and the issue is not ack-grep as it looks like.
vagrant@xenial zsh --version
zsh 5.1.1 (x86_64-ubuntu-linux-gnu)
vagrant@xenial tar Foo().Bar
vagrant@xenial tar
tar:4: command not found: .Bar

I will check back with the z-shell folks.

That's actually what you said, a lack of quoting of parenthesis which are interpreted as defining a function. The solution then is quote everything: https://github.com/robbyrussell/oh-my-zsh/issues/5490#issuecomment-251251476. You can close this one.


CNAI Radar

Provide guidance on maturity levels of projects in the landscape.

Now that CNAI landscape is available, we might be able to move this forward a little.


Integration with OpenCV (Python)

The latest Mendel OS (v4.0 Day) adds support to OpenCV, but the documentation doesn't offer too much for this.
I'm trying to run a face recognition system using OpenCV (Python). It runs, but pretty slow, similar to how a Raspberry PI would run. I would like to integrate the capabilities of the TPU with OpenCV to improve the speed of video recognition, such as the edgetpu_demo does when running on the TPU.
Someone could say, hey you should use tf models instead, but the reality is that OpenCV makes much easier the implementation of custom models with few steps; that's why I decided to use OpenCV instead.
So, is there a chance to make run an OpenCV python code on the TPU instead on the CPU?
If it is not possible, I would like to hear additional alternatives. As I said, the system is running, slowly but running.
P.S: I use Coral Edge TPU Dev-Board.
Thanks in advance.

@sagilar Sorry for the confusion, Opencv is used on our board for pre-processing inputs only (video stream, capturing frame, resizing...), the inference part on the edgetpu are only supported with tflite

Ok, thanks for your response. Could you guide me if possible to a tutorial to modify the FaceNet model with my own dataset and convert it into tflite then?
Thank you so much. Have a great day.

@sagilar I'm not aware of any facenet specific model, however we do have a ssd face detection model here if that works for you.
Here is an example of how you can use it with opencv!


"fetch failed" when using motorhead and "out of memory" when using Buffer Memory when using Embed or Share Chatbot UI.

So, like the title says:

When we use Motorhead memory 1 out of ~3-4 messages raises fetch failed error on the server. We write a question, we get an answer then while we wait for the the TextInput to re-enable (which takes a lot of time btw) we get a "fetch failed" message.
When we use Buffer Memory we get JavaScript heap out of memory after ~15-20 messages. The TextInput still takes a lot of time to re-enable (taking logger as more messages are added). And we also upgraded our server memory to more to Flowise.

I post this as a bug because we did not have this error under the same setup when we were using an older version of Flowise. This started to appear after we upgraded to the latest version. So after the upgrade the TextInput takes a lot of time to re-enable and then we get "fetch failed" but this is after we get the response from the flow.
We run flowise in a docker container and orchestrated in docker-compose. Here is the docker-compose file:
version: '3.7'

services:
    redis:
        image: "redis:6-alpine"
        restart: unless-stopped
        ports:
            - "6379:6379"
        command: redis-server
        volumes:
            - redis_data:/data
        logging:
            options:
                max-size: "5m"
                max-file: "3"

    motorhead:
        image: "ghcr.io/getmetal/motorhead:latest"
        restart: unless-stopped
        depends_on:
            - redis
        ports:
            - "8000:8000"
        environment:
            - PORT=8080
            - REDIS_URL=redis://redis:6379
            - MOTORHEAD_MAX_WINDOW_SIZE=40
            - MOTORHEAD_LONG_TERM_MEMORY=0
            - OPENAI_API_KEY=
            - RUST_BACKTRACE=1
        logging:
            options:
                max-size: "5m"
                max-file: "3"

    flowise:
        image: flowiseai/flowise:latest
        restart: unless-stopped
        depends_on:
            - motorhead
            - redis
        environment:
            - PORT=${PORT}
            - FLOWISE_USERNAME=${FLOWISE_USERNAME}
            - FLOWISE_PASSWORD=${FLOWISE_PASSWORD}
            - DEBUG=${DEBUG}
            - DATABASE_PATH=${DATABASE_PATH}
            - APIKEY_PATH=${APIKEY_PATH}
            - SECRETKEY_PATH=${SECRETKEY_PATH}
            - FLOWISE_SECRETKEY_OVERWRITE=${FLOWISE_SECRETKEY_OVERWRITE}
            - LOG_LEVEL=${LOG_LEVEL}
            - LOG_PATH=${LOG_PATH}
        ports:
            - '${PORT}:${PORT}'
        volumes:
            - ~/.gmc_flowise:/root/.gmc_flowise
        command: /bin/sh -c "sleep 3; flowise start"

volumes:
    redis_data:

Here is a log I created to demonstrate the issue when using Mororhead memory. The log starts with a fresh instance of Flowise and ends with the error. I do nothing except to chat though the chat UI:
flowise-flowise-1    | 2023-12-06 11:16:42 [INFO]: Starting Flowise...
flowise-flowise-1    | 2023-12-06 11:16:42 [INFO]: ⚡ [server]: Flowise Server is listening at 3000
flowise-flowise-1    | 2023-12-06 11:16:42 [INFO]: 📦 [server]: Data Source has been initialized!
flowise-flowise-1    | 2023-12-06 11:16:56 [INFO]: ⬆ POST /api/v1/prediction/02a3bf6d-5af0-45e5-8b7e-89f8ef70e13b
flowise-motorhead-1  | [2023-12-06T11:16:56Z INFO  actix_web::middleware::logger] <IP_ADDRESS> "GET /sessions/6a538d6b-7ade-4fae-9894-c98868040c0a/memory HTTP/1.1" 200 41 "-" "node" 0.001107
flowise-flowise-1    | 2023-12-06 11:16:56 [INFO]: [server]: Chatflow 02a3bf6d-5af0-45e5-8b7e-89f8ef70e13b added into ChatflowPool
flowise-motorhead-1  | [2023-12-06T11:16:59Z INFO  actix_web::middleware::logger] <IP_ADDRESS> "POST /sessions/6a538d6b-7ade-4fae-9894-c98868040c0a/memory HTTP/1.1" 200 15 "-" "node" 0.000851
flowise-flowise-1    | 2023-12-06 11:17:27 [INFO]: ⬆ POST /api/v1/prediction/02a3bf6d-5af0-45e5-8b7e-89f8ef70e13b
flowise-motorhead-1  | [2023-12-06T11:17:27Z INFO  actix_web::middleware::logger] <IP_ADDRESS> "GET /sessions/6a538d6b-7ade-4fae-9894-c98868040c0a/memory HTTP/1.1" 200 168 "-" "node" 0.000676
flowise-flowise-1    | 2023-12-06 11:17:27 [INFO]: [server]: Chatflow 02a3bf6d-5af0-45e5-8b7e-89f8ef70e13b added into ChatflowPool
flowise-motorhead-1  | [2023-12-06T11:17:30Z INFO  actix_web::middleware::logger] <IP_ADDRESS> "POST /sessions/6a538d6b-7ade-4fae-9894-c98868040c0a/memory HTTP/1.1" 200 15 "-" "node" 0.000775
flowise-flowise-1    | 2023-12-06 11:17:42 [INFO]: ⬆ POST /api/v1/prediction/02a3bf6d-5af0-45e5-8b7e-89f8ef70e13b
flowise-motorhead-1  | [2023-12-06T11:17:42Z INFO  actix_web::middleware::logger] <IP_ADDRESS> "GET /sessions/6a538d6b-7ade-4fae-9894-c98868040c0a/memory HTTP/1.1" 200 346 "-" "node" 0.000665
flowise-flowise-1    | 2023-12-06 11:17:42 [INFO]: [server]: Chatflow 02a3bf6d-5af0-45e5-8b7e-89f8ef70e13b added into ChatflowPool
flowise-motorhead-1  | [2023-12-06T11:17:46Z INFO  actix_web::middleware::logger] <IP_ADDRESS> "POST /sessions/6a538d6b-7ade-4fae-9894-c98868040c0a/memory HTTP/1.1" 200 15 "-" "node" 0.000883
flowise-flowise-1    | 2023-12-06 11:17:52 [INFO]: ⬆ POST /api/v1/prediction/02a3bf6d-5af0-45e5-8b7e-89f8ef70e13b
flowise-motorhead-1  | [2023-12-06T11:17:52Z INFO  actix_web::middleware::logger] <IP_ADDRESS> "GET /sessions/6a538d6b-7ade-4fae-9894-c98868040c0a/memory HTTP/1.1" 200 463 "-" "node" 0.000524
flowise-flowise-1    | 2023-12-06 11:17:52 [INFO]: [server]: Chatflow 02a3bf6d-5af0-45e5-8b7e-89f8ef70e13b added into ChatflowPool
flowise-flowise-1    | 2023-12-06 11:17:57 [ERROR]: [server]: Error: fetch failed
flowise-flowise-1    | TypeError: fetch failed
flowise-flowise-1    |     at Object.fetch (node:internal/deps/undici/undici:11372:11)
flowise-flowise-1    |     at async RetryOperation._fn (/usr/local/lib/node_modules/flowise/node_modules/p-retry/index.js:50:12)

When using Buffer memory we simple run out of memory:
flowise-flowise-1    | 2023-12-06 11:27:50 [INFO]: ⬆ POST /api/v1/prediction/02a3bf6d-5af0-45e5-8b7e-89f8ef70e13b
flowise-flowise-1    | 2023-12-06 11:27:50 [INFO]: [server]: Chatflow 02a3bf6d-5af0-45e5-8b7e-89f8ef70e13b added into ChatflowPool
flowise-flowise-1    |
flowise-flowise-1    | <--- Last few GCs --->
flowise-flowise-1    |
flowise-flowise-1    | [1:0x7f323f511020]   333318 ms: Mark-sweep (reduce) 980.4 (996.5) -> 980.3 (997.3) MB, 755.4 / 0.0 ms  (+ 58.8 ms in 14 steps since start of marking, biggest step 20.7 ms, walltime since start of marking 855 ms) (average mu = 0.330, current mu = 0.257) al
flowise-flowise-1    |
flowise-flowise-1    | <--- JS stacktrace --->
flowise-flowise-1    |
flowise-flowise-1    | FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
flowise-flowise-1 exited with code 139

The way I see it ChatflowPool might be the cause of this issue. We do not have any problems chatting with the flow from within Flowise where ChatflowPool does not fire up.

does this happens only for the embedded chat? or its the same on the Flowise UI as well?

This happens only for the embedded chat. In Flowize UI everything looks good.

Experiencing the same issue. Mine runs into this error from calling the api. UI chat works accordingly.


align sql template tag with ExpressionBuilder.

deprecate Sql.value, for Sql.val - or should we name it value in both places instead?
add .literal @ ExpressionBuilder - QoL, so consumers don't have to import sql just for .literal.
add generics to various Sql methods.

Good catches! Should literal be lit to use the same naming?

Should literal be lit to use the same naming?

Yeah, let's go with lit.

I'm not sure we should have lit or literal in the ExpressionBuilder though. It's a dangerous method.

We could take a page out of react's playbook and call it dangerouslyLit 😃

Why add it at all if it's deprecated from the get go?

By the way, there's a discussion where people are already asking for a better, longed name for cmp 😮💨

Why add it at all if it's deprecated from the get go? Or dangerous. The user always has sql for dangerous stuff.

Just thought it would have some QoL benefits (not having to import sql). 🤷♂

Just thought it would have some QoL benefits (not having to import sql). 🤷♂

That's a good point. But I don't think users will need to use lit that often. It's only useful in migrations and some other very specific places. I think it's ok to import sql in those cases. That way we'll keep the dangerous stuff in one place.

Just thought it would have some QoL benefits (not having to import sql). 🤷♂

That's a good point. But I don't think users will need to use lit that often. It's only useful in migrations and some other very specific places. I think it's ok to import sql in those cases. That way we'll keep the dangerous stuff in one place.

Yeah, its rare with the built-in dialects, but from what I've seen, 3rd party dialects might require using it more.

Noice! Thanks!


ceph_orch_apply: fix idempotency

As is idempotency does not work as the ceph orch
output does contain more attributes than the expected spec.

jenkins test centos-container-cephadm_adopt


Feature request. Load.

Hi All
Is there any chance to implement in future version load of the system? Perfect would all 3 of them, 1, 5 and 15 minutes.
Thank you.

Not interested in adding this feature.

Thanks for opening this issue. :+1:


public domain

Please consider dedicating your work to the public domain so that others can safely copy & paste from your repo. You can use https://unlicense.org/ or https://creativecommons.org/publicdomain/zero/1.0/.

Feel free to send a PR to the README!


Hosts file and Registry Preview: on/off switch?

Description of the new feature / enhancement
Via the Settings, the ToggleSwitch is absolutely pointless. Via the Flyout: well, there's no point in switching it off either. If you open the flyout and you don't want to open it, you simply don't click it.
Let's remove these useless settings.

For registry preview the toggle also enables/disables the context menu.
Also the toggle decide if the module interface is loaded into memory or not.
So the toggle switch has its use case.


Update target is not loading the database project after successfully updated the project

Azure Data Studio Version:
OS Version:

Steps to Reproduce:

Create a database project from the database
Add a table to the database
Right click on db project and 'update project from database'
SC window will show the differences and click on 'Apply'
After successful update, observe the database projects pane and the db project is not loaded with new changes unless we close and reopen or click a refresh button.

Does this issue occur when all extensions are disabled?: Yes/No

fixed in https://github.com/microsoft/azuredatastudio/pull/18890


No compatible call signatures

Using array-sort in typescript for around 16 months, but am now faced wit:
Cannot invoke an expression whose type lacks a call signature. Type '{}' has no compatible call signatures.ts(2349)
Everytime I try use it, even when using the readme files. Has TS update caused this?

Has TS update caused this?

Sounds like it's a TS issue since nothing has changed in this package. Also, there aren't any type definitions published in this package, so if you have some from someplace else you might want to check to see if those have changed for any reason.
I'm going to close this, but if you think there's an issue with array-sort, please feel free to add additional information (code, environment information, etc...) so someone can help.


Default modules set

Add test for modules/default/defaultmodules.js

Thanks this works
You guys are amazing!!

app is running fine but getting black screen please help

Ok I install everything but only I sell the clock and the calendar of the messages and the news but install the modules of email and the weather but nothing comes out on the screen is black only with clock and calendar and news that I can do?

El abr. 13, 2017, a las 10:25 PM, undergroundauth<EMAIL_ADDRESS><EMAIL_ADDRESS>escribió:
app is running fine but getting black screen please help
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/MichMich/MagicMirror/pull/850#issuecomment-294092763, or mute the thread https://github.com/notifications/unsubscribe-auth/AYhTVnssXe5vL7Zpo0UxjGNZGuISFSaSks5rvwNdgaJpZM4M9aBs.

Need to see your code

Code change config.js but nothing happens

El abr. 15, 2017, a las 10:44 PM, justjim1220<EMAIL_ADDRESS>escribió:
Need to see your code
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/MichMich/MagicMirror/pull/850#issuecomment-294335021, or mute the thread https://github.com/notifications/unsubscribe-auth/AYhTVklACkyj6AVDXo1z4Ka2uL6v-BdYks5rwaqjgaJpZM4M9aBs.

Sorry guys this is a Pull Request. You should to move the conversation another place. In case the comment is related on review of this change add here.
If need support for any troubles go to forum https://forum.magicmirror.builders/


Missing Snakefile from example test dataset

I believe this is a distinct issue from https://github.com/a-ludi/dentist/issues/21 as it pertains to the Snakefile rather than the .yml files that you helpfully signposted. I am using the https://github.com/a-ludi/dentist-example/releases/download/v1.0.2-2/dentist-example.tar.gz example dataset.
When I execute
(base) ubuntu@bio-xanthomonas:~/dentist-example$ snakemake --configfile=snakemake.yml --use-singularity --cores=all
I get this error message:
Error: no Snakefile found, tried Snakefile, snakefile, workflow/Snakefile, workflow/snakefile.
So, I guessed the obvious thing to do was to download this Snakefile: https://github.com/a-ludi/dentist/blob/develop/snakemake/Snakefile.
However, when I try again to execute the above command line, with this Snakefile in the current directory, I get:
IndentationError in line 113 of <tokenize>:
unindent does not match any outer indentation level (<tokenize>, line 113)
 File "/usr/lib/python3.8/tokenize.py", line 512, in _tokenize

I suspect, that this might be because I am not using the correct Snakefile?

I suspect, that this might be because I am not using the correct Snakefile?

I agree. Try this Snakefile. It is the one that should be included in the tarball.

The link in your message above is: https://raw.githubusercontent.com/a-ludi/dentist/d85a86fda8da241b0de3d3b8d3b02cf9e3405302/snakemake/cluster.yml. This is file called 'cluster.yml' not 'Snakefile'. Is this intended?

This was a copy&paste mishap. Sorry. Correct link: https://raw.githubusercontent.com/a-ludi/dentist/d85a86fda8da241b0de3d3b8d3b02cf9e3405302/snakemake/Snakefile

Thanks, Arne.
However, with this file I now get this error message:
SyntaxError in line 896 of /home/djs217/dentist-example/Snakefile:
Unexpected keyword container in rule definition (Snakefile, line 896)

Possibly this is an issue with snakemake version used?
$ snakemake --version
5.10.0

The offending line 896 seems to be:

Possibly this is an issue with snakemake version used?
Yes, please update to v5.32.1.

Thanks, Arne. So, I think the original issue is now resolved since the the missing file is available at: https://raw.githubusercontent.com/a-ludi/dentist/d85a86fda8da241b0de3d3b8d3b02cf9e3405302/snakemake/Snakefile


SQL errors during initial startup, no default user created or data imported

[x ] I have read the FAQ.

Describe the bug
SQL errors during initial startup, no default user or data being imported.
To Reproduce

Defined the docker compose as below
Created empty bar_data folder and chown with the www-data user to be allowed to write there.
Start up with docker compose up -d

Please check the attached logs file.
version: "3"

services:
  meilisearch:
    image: getmeili/meilisearch:v1.1
    container_name: services.bar-assistant-meilisearch
    environment:
      - MEILI_MASTER_KEY=$MEILI_MASTER_KEY
      - MEILI_ENV=production
    restart: unless-stopped
    volumes:
      - ./meilisearch_data:/meili_data
    networks:
      - bar-network
      - proxy-network

  redis:
    image: redis
    container_name: services.bar-assistant-redis
    environment:
      - ALLOW_EMPTY_PASSWORD=yes
    restart: unless-stopped
    networks:
      - bar-network

  bar-assistant:
    image: barassistant/server:latest
    container_name: services.bar-assistant
    depends_on:
      - meilisearch
      - redis
    environment:
      - APP_URL=$API_URL
      - LOG_CHANNEL=stderr
      - MEILISEARCH_KEY=$MEILI_MASTER_KEY
      - MEILISEARCH_HOST=$MEILISEARCH_URL
      - REDIS_HOST=redis
      - ALLOW_REGISTRATION=true
      # - DISABLE_LOGIN=true # Optional if you want to disable auth
    restart: unless-stopped
    volumes:
      - ./bar_data:/var/www/cocktails/storage/bar-assistant
    networks:
        - bar-network
        - proxy-network

  salt-rim:
    image: barassistant/salt-rim:latest
    container_name: services.bar-assistant-salt-rim
    depends_on:
      - bar-assistant
    environment:
      - API_URL=$SALT_RIM_API_URL
      - MEILISEARCH_URL=$MEILISEARCH_URL
      - BAR_NAME=$BAR_NAME
      - DESCRIPTION=$BAR_DESCRIPTION
      - DEFAULT_LOCALE=en-US
      # - DISABLE_LOGIN=true # Optional if you want to disable auth
    restart: unless-stopped
    networks:
      - bar-network
      - proxy-network

networks:
  bar-network:
     name: bar-network
  proxy-network:
    external: true

Strange behavior afterwards. The first created user cannot be used to log in. Only the second created user seems to be able to log in.
Same issue happens when using volumes instead of directories. e.g.
volumes:
  bar_data:
  meilisearch_data:

Versions:

Docker: 23.0.3

Additional context, log outputs...
_services.bar-assistant_logs.txt

Make sure your Bar Assistant version is at least v2.6 since there were some issues in v2.5 with initial import.
I've just tested the stack with the config from https://github.com/bar-assistant/docker and everything is running successfully.
I can't test with your config since you have some of your own ENV vars

Thanks, switching to v2.6 fixed the issue. I usually rely on watchtower for updates but this time something went wrong there.