Simplified PR for esm and cjs builds

This is an alternative PR to #120
My goal was the minimal number of changes that would produce esm and cjs builds.
Basically, tsc is just run twice, with two different tsconfig files.
This article was used as a general guide (no affiliation):
How to Create a Hybrid NPM Module for ESM and CommonJS
Both npm test and npm run test-ci still run successfully.
I also built ip-address locally, and ran it against my current project using npm link, and all my tests still pass :star:
To summarize this PR...
I renamed the root tsconfig file to tsconfig-base and then added a tsconfig file for esm and another for cjs.
The new configs inherit from tsconfig-base and only contain module related overrides.
package.json was changed to ensure the correct tsconfig is called, and the new entry points were indicated for cjs vs esm.
FWIW, I worked through these changes for two of my own GitHub projects (pcafstockf/async-injection and pcafstockf/pfta) before starting this PR, and am happy with the results so far.
I used to get warnings from the Angular compiler:
Warning: /src/validations.ts depends on 'ip-address'. CommonJS or AMD dependencies can cause optimization bailouts.
For more info see: https://angular.io/guide/build#configuring-commonjs-dependencies

// Repeated for my own two GitHub projects

All 3 of those warnings are now gone.
Caveat
Now I get:
Warning: node_modules/ip-address/dist/mjs/lib/ipv4.js depends on 'sprintf-js'. CommonJS or AMD dependencies can cause optimization bailouts.
But that's a problem for another day.  Maybe I'll submit a PR to sprintf-js folks when I have a little more time.
:smiley:

thanks for this @pcafstockf--in looking at this and the other open PR that I didn't quite get merged there are some things I like about both; going to take the best of both now. :)

closed in favor of #138; thanks for the pointer on the hybrid approach! re: sprintf, that can all be ripped out in favor of template literals now :)


deps: Upgrade to Node v16, in setup docs and in CI

I've been using this for local development for a few weeks now,
and all seems well.  (That's longer than it needs to be; I just
hadn't come back to this to follow up.)
Node v12 is going EOL in just over a week, 2022-04-30, so it's
past time to make this upgrade official.
Also delete an old troubleshooting entry for a problem with Node v11
that was avoided by sticking to v10; and fix two other references to
Node v10 (where the problem was using an older version like v8) so
that they remain accurate now and for further upgrades in the future.
(At least until Node v1000.  On Node's current release cadence, that
will happen in a little under 500 years.  I think we can tolerate
having to tweak this check then.)
Fixes: #4263

Should wait to merge this one until CI passes, because this is a rare PR that touches the CI workflow config directly.

CI passed; and did indeed get Node v16:
Run actions/setup-node@v2
Attempt to resolve the latest version from manifest...
Resolved as '16.14.2'
Found in cache @ /opt/hostedtoolcache/node/16.14.2/x64

(BTW I did post a revision applying Anders's feedback. I see I hadn't posted a comment saying so.)

It also LGTM. 🙂

Thanks for the reviews! Merged.


Add wrapped covered principal token in factory event

Coverage remained the same at 94.069% when pulling 565647ea1d1dae1ccfc36ddb0cc65dd246212758 on path-add-token-address-in-event into c8b5671b2880dd2647fea2f894a30e5b7017d9ea on main.


Bevy panics if started from a read-only directory without an assets folder

Bevy version
0.12
Relevant system information
Reproducible under both Windows and Linux.
What you did
Providing a minimal example application here:
use bevy::prelude::*;

fn main() {
    App::new().add_plugins(DefaultPlugins).run()
}

Compile the above code in release mode
Copy the executable to some folder that does not contain an assets subfolder and make that folder read-only.
Start the application from that folder.

What went wrong
The application panics when it attempt to create an assets folder in the read-only directory.
thread 'main' panicked at /home/tripokey/.cargo/registry/src/index.crates.io-6f17d22bba15001f/bevy_asset-0.12.0/src/io/file/mod.rs:48:13:
Failed to create root directory "/home/tripokey/projects/bevy_asset_issue_poc/testing/assets" for file asset reader: Os { code: 13, kind: PermissionDenied, message: "Permission denied" }
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

When using bevy as a backend for an application without any assets and installing this application to some system folder it would be desirable if it did not panic upon not being able to create the assets folder.
Additional information
A possible workaround for this problem could be to create an empty assets folder in the read-only directory.

The other workaround I would suggest is disabling default features for these applications, and being sure that bevy_assets is off.
That said, we should fail gracefully here instead.

@alice-i-cecile Would embedded assets still work with bevy_assets disabled?

Hmm, good question. Probably not!


Pass CMAKE_PREFIX_PATH to Ogre and disable precompiled header to compile Ogre on macOS

Passing CMAKE_PREFIX_PATH (set by user via colcon --cmake-args) so Ogre can use locally built libraries.

This fix is very important for conda users. It's impossible to build it in conda environment without it.

Is this PR still relevant ? There are some conflicts

I didn't have time to catch up to the latest changes so I have no idea. I will close the PR then.


How to un/marshal custom types with Google?

So this library now recommends to switch to google's implementation, which is ok with me. But the problem is that this library has
type JSONPBMarshaler interface {
	MarshalJSONPB(*Marshaler) ([]byte, error)
}

type JSONPBUnmarshaler interface {
	UnmarshalJSONPB(*Unmarshaler, []byte) error
}

but the Google library does not. So what is the migration path in this case? The note // Deprecated: Custom types should implement protobuf reflection instead. is quite useless because it  does not say anything useful.

I think we had the JSONPB marhsaller overriding because that was the only way to get into compliance with the JSON mapping standard with the old API, however, since the newer API provides protojson and follows the standards, and accounts for WKT, there’s no need to provide a way to override how to marshal/unmarshal to JSON.
Since it’s standardized, we need to follow the standard.

+1 to what puellanivis said. The standard way is to implement protoreflect.Message and use protojson to render it to JSON. I'm closing this. Feel free to re-open, if this didn't address your question.


WIP | feat: issue-9: create the UiPhoneNumber component

it's still in progress
Related issue
Closes issue #9
Scope of work

create the UiPhoneNumber component,
create stories.ts and spec.ts files,
todo:

write stories

write unit tests

styles with variables

what has happened here? :o


segmentQueryFirst works in JS but not when compiled for IOS

     var first = space.segmentQueryFirst(start, cp.v(segmentEndX, segmentEndY), -1, 0);
     cc.log('first: ', first);

first returns null in IOS but works in the HTML5 version of the app.

FWIW the layers parameter does not default to -1 when compiled to an IOS device for some reason.


redis.log not flush in docker on mac OrbStack

Search before asking

[X] I had searched in the issues and found no similar issues.

Version
unstable
Minimal reproduce step
https://lusun.com/v/5tn1fBHzmDO

EVAL 'redis.log(redis.LOG_WARNING, "test")' 0

I recorded the videos, all in docker, and the first redis shown was output in real time. Then I turned off redis and used kvrocks. I can see that it needs to cache more than a dozen items before outputting them at once.
我录了下视频，都是docker，第一个展示的redis，是实时输出的。然后我关了redis，用kvrocks，可以看到要缓存十几条才一次输出

@3tieto Thank you!

I cannot reproduce it on my side. To see if any one has any clues.

如上图，加上FLAGS_logbuflevel = -1;   可以只延时一个输出了（我也不知道为什么还是要延时一个，也就是
stdout会实时输出， LOG(WARNING)要打印下一个的时候会输出上一个
）


⚠ ClamAV has degraded performance

In 3ecd8d4, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 224 ms

Resolved: ClamAV performance has improved in ff8cb21.


Linking of items to external systems

Ability to configure items to have a link to external systems
Use Case
example: within a device a button/link to the device that is within a different management system. i.e. netbox, GLPI etc.
Details
Within the content title the "badges" could be added with float: right. The badges could be formated from the configuration provided by the user: text colour, background colour, url regex. the URL regex should be specified from fields that are available within the form. i.e. device.id for a device. i.e. url=http://domain.tld/some/path/{{ device.id }}. [^footnote-1].
Expansion of user provided jinja tag.
This code block contains an implementation that will expand a template tag provided in a string. This will make it possible for the end user to use jijna templating to access any context data that is provided to the form.

from django.template import Template, Context

...

def get_context_data(self, **kwargs):

    context = super().get_context_data(**kwargs)

    user_string = Template('http://domain.tld/{{ device.name }}')
    user_context = Context(context)
    context['test_link'] = user_string.render(user_context)

Sketch pad implementation
This code block provides an example for a template that creates a "badge" in the device's content header.

      Details
      Link

Requirements

[ ] All user context to be available for specifying within "badge"

Tasks

[ ] Plan feature

Footnotes
[^footnote-1]: the use of the jinja will have to be tested to see if it will still expand without extra processing Confirmed as possible. see above

added 2m of time spent

/cc @jasonpagetas

unassigned @jon-nfc

clearing milestone as its not required for production release

added 15m of time spent

added 7m of time spent

marked this issue as related to #79

added 30m of time spent

marked this issue as blocked by #50

mentioned in commit 812250e94162ff330bb1f614d32d93c3a851c636

mentioned in commit 6aa50140704673147d1a87b3eaa064a69d384764

mentioned in commit 21876328f09ca4e370c8f5f9c94e9794ff86897f

mentioned in commit 0bddb008a3ed611321b875a53bb45e5b68bcfffe

mentioned in commit dd6f8336fd3d3455ac985020d8238afecde4471d

mentioned in commit 527e784ea7b3ebdf778f0ce3d5affc00b9566267

mentioned in commit 33ceb96423caef7335076af24dc7370b93508d2c

mentioned in commit 79884d191fabc0d3ba2bbbd9589a50f07b1485cb

mentioned in commit b834fadab62ed923f24bcbcba887b7257fc12649

mentioned in commit 5f455683394f51d5dab773160ea491c5b5a339cd

mentioned in commit 2dc87e8fa2079600cac3dfd22c6ae174cfa64fe8

mentioned in commit 8b6aa4473b57c4340ec5a2d8527bb338609df3fb

mentioned in commit abfa03836abd231e880b8a81979d1cc1f07b54ef

mentioned in commit 379b69cd80d670174d07bae61542ae29e88eedc4

mentioned in commit da196f40e8552adfb6b0dd0ce8c245e7d92e9638

mentioned in commit ddc79f8aacb07f5a3d2ddd8d6621d0ecd498748f

mentioned in commit 65b4b1ad06246d2fd2c4a86ff8e9f4013bbdb5b6

mentioned in commit d8bfd6eb9b330ce423115152c400a2e7b78afd21

mentioned in commit e7b11b58a7c14ec005c74e6dff9f9958381b97bd

mentioned in commit f5eacd77a23a6ff9da5951b9aad85fce7a46fc8e

mentioned in commit bc5c577d9c83ee6ed036809363d9b460a1790d8d

mentioned in commit 3e236ce3c00e7ee82b03708d88c4c9756c33633e


remove tool submodules

@aolofsson I finally got the wheels build working on MacOS and Windows with the newest version of OpenROAD. I added the _tools.json and _tools.py to start tracking the tools and versions in a single place. I chose the json file to make it easier to update via a script instead of adding it to the python file and rewrite it. In a followon PR, we can add all remaining tools. I'm open to suggestions if you think a different form would be better.


Enable system timer interrupts

Setup timer interrupts for sys clock 1 and 3
https://student.cs.uwaterloo.ca/~cs452/F23/lectures/lec08.html


Improve SnapshotHelper.swift to support snapshotting for multiple apps.

#11834 duplicate.
Checklist

[x] I've read the Contribution Guidelines

Motivation and Context
Subsequent call to XCUIApplication() would rise an exception if UITest was previously setup with XCUIApplication(bundleIdentifier:).
Replacing XCUIApplication() with Snapshot.app is safe because app variable was previously initialized via setupSnapshot() function invocation.
Reusing an existing Snapshot.app variable will enable multiple apps testing by leveraging XCUIApplication(bundleIdentifier:) from user tests.
Description
Support multiple apps testing flows with native XCUIApplication(bundleIdentifier:).

@genkernel Heyyy 👋  Good catch here! We definitely don’t want to keep making a new XCUIApplication instance. Your change didn’t fully work because Snapshot.app is optional so I had to add some guards around things and I also bumped the version up so I added some commits for those 💪


Add createSpring primitive.

Summary

This PR adds the createSpring primitive. Inspired and Forked from https://svelte.dev/docs/svelte-motion#spring
The API works exactly like createSignal, just that the setter will actually interpolate the value.
It also has familiar opts as the one with svelte-motion/spring.
I come from using Svelte and it's one of the most essential primitives I use for animation. I've been using Solid more and more and have come to love it. I think this primitive is one of the few missing for me here. I think Solid would greatly benefit from a primitive like this since we already have a tween primitive.

Example Usage:
export default function SpringyPage() {
  const [progress, setProgress] = createSpring(0);

  const [radialProgress, setRadialProgress] = createSpring(0, {
    stiffness: 0.05,
  });

  const [xy, setXY] = createSpring(
    { x: 50, y: 50 },
    { stiffness: 0.08, damping: 0.2, precision: 0.01 }
  );

  function toggleProgress() {
    if (progress() === 0) setProgress(1);
    else setProgress(0);
  }
  // ...

Witness, the springiness:
https://github.com/solidjs-community/solid-primitives/assets/38070918/7c4fa01f-7959-4a67-9588-e28448f7f20d
https://github.com/solidjs-community/solid-primitives/assets/38070918/4dcf9e6f-7a2e-44f8-b15a-d29d6551f561
Todos:

[ ] Tests
[x] README.md
[x] package.json

Update: I also figure of adding createSpringDerived by the way, so that there's a similar API that works like the current createTween's API which doesn't return a setter, but takes in an Signal accessor.
const springValue = createTweenDerived(signal, opts)

Will add this tonight.

I don't necessarly like that createSpring by default tries to handle various types of data recursively.
The core idea of a spring is just a simple math equation for tweening numbers, but the source code reads like something much more complex.
I wonder if it would be smart to separate it into more functions rather than one-does-all primitive. Maybe a separate primitive for numbers and objects?
It would be nice to have a vanilla-js spring(from, to, time, options) function as well.
Also maybe the primitive could be added to the tween package? The use and concepts are similar. Separate package for each tweening strategy would probably be a lot.
I still need to think about that.

I tried to inline the tasks thing from svelte to the primitive. The tests pass and it works as it should in my eyes, but could you double check @Blankeos?
Probably will merge after that.

Awesome work guys! Couldn't really check the past week, it's been a very busy month for me.
Thanks for adding in your insights @thetarnav @rcoopr!  🦾🥳


fix(ci): call chart releaser directly.

Description
Updates the release CI to call Chart releaser directly to allow us more control over the process on how the artifacts are signed and uploaded.
Fix #574

LGTM, how are we going to test it?

I've tested it in my fork. I'll document my tests later in this PR

@jvanz ship it! :rocket:


Update lookup of rpc.h to account for new libnsl and headers location

See python/cpython@29a7df7
FAILED: CMakeBuild/extensions/extension_nis/CMakeFiles/extension_nis.dir/home/phc/Software/Slicer/build-release/Python-2.7.13/Modules/nismodule.c.o
/usr/bin/cc -Dextension_nis_EXPORTS -I/home/phc/Software/Slicer/build-release/Python-2.7.13/Include -Ibin -I/home/phc/Software/Slicer/build-release/Python-2.7.13/Python -Wall -Wstrict-prototypes -fno-strict-aliasing -fwrapv -g -O3 -DNDEBUG -fPIC -MD -MT CMakeBuild/extensions/extension_nis/CMakeFiles/extension_nis.dir/home/phc/Software/Slicer/build-release/Python-2.7.13/Modules/nismodule.c.o -MF CMakeBuild/extensions/extension_nis/CMakeFiles/extension_nis.dir/home/phc/Software/Slicer/build-release/Python-2.7.13/Modules/nismodule.c.o.d -o CMakeBuild/extensions/extension_nis/CMakeFiles/extension_nis.dir/home/phc/Software/Slicer/build-release/Python-2.7.13/Modules/nismodule.c.o   -c /home/phc/Software/Slicer/build-release/Python-2.7.13/Modules/nismodule.c
/home/phc/Software/Slicer/build-release/Python-2.7.13/Modules/nismodule.c:17:10: fatal error: rpc/rpc.h: No such file or directory
 #include <rpc/rpc.h>
          ^~~~~~~~~~~

+1 hitting this in Archlinux (gcc8.1)

+1 hitting this in Gentoo (gcc 8.3)
It seems that glib>=2.26 is getting rid of the old SunRPC which included rpc.h in /usr/include/rpc/rpc.h. Now RPC will be supported by the tirpc and ntirpc libraries, which place rpc.h in /usr/include/tirpc/rpc/rpc.h Gentoo Wiki glib 2.26. While the information in the link is Gentoo-specific, the issue seems applicable in a wider basis and even in pythonc repostiories there are some references to it here.
I have been working on a patch for python-cmake-buildsystem that seems to work properly. I will pull-request real soon.


Nitrous.io Quickstart - Something went wrong.

Launching “laravel5-example”…
Something went wrong. Open IDE anyway.
Querying the GitHub API for https://github.com/bestmomo/laravel5-example...
OK - GitHub says https://github.com/bestmomo/laravel5-example is legit.
Creating project on workstation "anonym"...
OK - project "laravel5-example" created.
Cloning https://github.com/bestmomo/laravel5-example to home directory on "larav
el5-example"...
Cloning into 'laravel5-example'...
remote: Counting objects: 4495, done.
remote: Total 4495 (delta 0), reused 0 (delta 0), pack-reused 4494
Receiving objects: 100% (4495/4495), 7.72 MiB | 344.00 KiB/s, done.
Resolving deltas: 100% (1858/1858), done.
Checking connectivity... done.
OK - Cloned repository.
Executing post-create script...
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.
 Problem 1
    - laravel/framework v5.2.9 requires ext-mbstring * -> the requested PHP exte
nsion mbstring is missing from your system.
    - laravel/framework v5.2.8 requires ext-mbstring * -> the requested PHP exte
nsion mbstring is missing from your system.
    - laravel/framework v5.2.7 requires ext-mbstring * -> the requested PHP exte
nsion mbstring is missing from your system.
    - laravel/framework v5.2.6 requires ext-mbstring * -> the requested PHP exte
nsion mbstring is missing from your system.
    - laravel/framework v5.2.5 requires ext-mbstring * -> the requested PHP exte
nsion mbstring is missing from your system.
    - laravel/framework v5.2.4 requires ext-mbstring * -> the requested PHP exte
nsion mbstring is missing from your system.
    - laravel/framework v5.2.32 requires ext-mbstring * -> the requested PHP ext
ension mbstring is missing from your system.
    - laravel/framework v5.2.31 requires ext-mbstring * -> the requested PHP ext
ension mbstring is missing from your system.
    - laravel/framework v5.2.30 requires ext-mbstring * -> the requested PHP ext
ension mbstring is missing from your system.
    - laravel/framework v5.2.3 requires ext-mbstring * -> the requested PHP exte
nsion mbstring is missing from your system.
    - laravel/framework v5.2.29 requires ext-mbstring * -> the requested PHP ext
ension mbstring is missing from your system.
    - laravel/framework v5.2.28 requires ext-mbstring * -> the requested PHP ext
ension mbstring is missing from your system.
    - laravel/framework v5.2.27 requires ext-mbstring * -> the requested PHP ext
ension mbstring is missing from your system.
    - laravel/framework v5.2.26 requires ext-mbstring * -> the requested PHP ext
ension mbstring is missing from your system.
    - laravel/framework v5.2.25 requires ext-mbstring * -> the requested PHP ext
ension mbstring is missing from your system.
    - laravel/framework v5.2.24 requires ext-mbstring * -> the requested PHP ext
ension mbstring is missing from your system.
    - laravel/framework v5.2.23 requires ext-mbstring * -> the requested PHP ext
ension mbstring is missing from your system.
 - laravel/framework v5.2.22 requires ext-mbstring * -> the requested PHP ext
ension mbstring is missing from your system.
    - laravel/framework v5.2.21 requires ext-mbstring * -> the requested PHP ext
ension mbstring is missing from your system.
    - laravel/framework v5.2.20 requires ext-mbstring * -> the requested PHP ext
ension mbstring is missing from your system.
    - laravel/framework v5.2.2 requires ext-mbstring * -> the requested PHP exte
nsion mbstring is missing from your system.
    - laravel/framework v5.2.19 requires ext-mbstring * -> the requested PHP ext
ension mbstring is missing from your system.
    - laravel/framework v5.2.18 requires ext-mbstring * -> the requested PHP ext
ension mbstring is missing from your system.
    - laravel/framework v5.2.17 requires ext-mbstring * -> the requested PHP ext
ension mbstring is missing from your system.
    - laravel/framework v5.2.16 requires ext-mbstring * -> the requested PHP ext
ension mbstring is missing from your system.
    - laravel/framework v5.2.15 requires ext-mbstring * -> the requested PHP ext
ension mbstring is missing from your system.
    - laravel/framework v5.2.14 requires ext-mbstring * -> the requested PHP ext
ension mbstring is missing from your system.
- laravel/framework v5.2.13 requires ext-mbstring * -> the requested PHP ext
ension mbstring is missing from your system.
    - laravel/framework v5.2.12 requires ext-mbstring * -> the requested PHP ext
ension mbstring is missing from your system.
    - laravel/framework v5.2.11 requires ext-mbstring * -> the requested PHP ext
ension mbstring is missing from your system.
    - laravel/framework v5.2.10 requires ext-mbstring * -> the requested PHP ext
ension mbstring is missing from your system.
    - laravel/framework v5.2.1 requires ext-mbstring * -> the requested PHP exte
nsion mbstring is missing from your system.
    - laravel/framework v5.2.0 requires ext-mbstring * -> the requested PHP exte
nsion mbstring is missing from your system.
    - Installation request for laravel/framework 5.2.* -> satisfiable by laravel
/framework[v5.2.0, v5.2.1, v5.2.10, v5.2.11, v5.2.12, v5.2.13, v5.2.14, v5.2.15,
 v5.2.16, v5.2.17, v5.2.18, v5.2.19, v5.2.2, v5.2.20, v5.2.21, v5.2.22, v5.2.23,
 v5.2.24, v5.2.25, v5.2.26, v5.2.27, v5.2.28, v5.2.29, v5.2.3, v5.2.30, v5.2.31,
 v5.2.32, v5.2.4, v5.2.5, v5.2.6, v5.2.7, v5.2.8, v5.2.9].
 To enable extensions, verify that they are enabled in those .ini files:
    - /etc/php/7.0/cli/php.ini
    - /etc/php/7.0/cli/conf.d/10-mysqlnd.ini
    - /etc/php/7.0/cli/conf.d/10-opcache.ini
    - /etc/php/7.0/cli/conf.d/10-pdo.ini
    - /etc/php/7.0/cli/conf.d/15-xml.ini
    - /etc/php/7.0/cli/conf.d/20-calendar.ini
    - /etc/php/7.0/cli/conf.d/20-ctype.ini
    - /etc/php/7.0/cli/conf.d/20-curl.ini
    - /etc/php/7.0/cli/conf.d/20-dom.ini
    - /etc/php/7.0/cli/conf.d/20-exif.ini
    - /etc/php/7.0/cli/conf.d/20-fileinfo.ini
    - /etc/php/7.0/cli/conf.d/20-ftp.ini
    - /etc/php/7.0/cli/conf.d/20-gd.ini
    - /etc/php/7.0/cli/conf.d/20-gettext.ini
    - /etc/php/7.0/cli/conf.d/20-iconv.ini
    - /etc/php/7.0/cli/conf.d/20-intl.ini
    - /etc/php/7.0/cli/conf.d/20-json.ini
    - /etc/php/7.0/cli/conf.d/20-mcrypt.ini
    - /etc/php/7.0/cli/conf.d/20-mysqli.ini
    - /etc/php/7.0/cli/conf.d/20-pdo_mysql.ini
    - /etc/php/7.0/cli/conf.d/20-phar.ini
    - /etc/php/7.0/cli/conf.d/20-posix.ini
    - /etc/php/7.0/cli/conf.d/20-readline.ini
    - /etc/php/7.0/cli/conf.d/20-shmop.ini
    - /etc/php/7.0/cli/conf.d/20-simplexml.ini
    - /etc/php/7.0/cli/conf.d/20-sockets.ini
    - /etc/php/7.0/cli/conf.d/20-sysvmsg.ini
    - /etc/php/7.0/cli/conf.d/20-sysvsem.ini
    - /etc/php/7.0/cli/conf.d/20-sysvshm.ini
    - /etc/php/7.0/cli/conf.d/20-tokenizer.ini
    - /etc/php/7.0/cli/conf.d/20-wddx.ini
    - /etc/php/7.0/cli/conf.d/20-xmlreader.ini
    - /etc/php/7.0/cli/conf.d/20-xmlwriter.ini
    - /etc/php/7.0/cli/conf.d/20-xsl.ini
  You can also run `php --ini` inside terminal to see which files are used by PH
P in CLI mode.
Exited with non-zero code.

Hello,
Check you have the good configuration to run Laravel :

PHP >= 5.5.9
OpenSSL PHP Extension
PDO PHP Extension
Mbstring PHP Extension (looks like you miss it)
Tokenizer PHP Extension

Solved it by adding the following to the post-create script:
sudo apt-get update sudo apt-get install php7.0-mbstring sudo apt-get clean

not work


Feature edition2021 is required on Fresh Ubuntu Install

Was actually testing the curl dependence on a fresh install of Ubuntu 20.04 LTS and after the following commands

sudo apt update && sudo apt upgrade
sudo apt install cargo
cargo install forc

When I encountered
error: failed to compile `forc v0.2.1`, intermediate artifacts can be found at `/tmp/cargo-installuiNuOQ`

Caused by:
  failed to parse manifest at `/home/controlc/.cargo/registry/src/github.com-1ecc6299db9ec823/fuel-types-0.1.0/Cargo.toml`

Caused by:
  feature `edition2021` is required

  consider adding `cargo-features = ["edition2021"]` to the manifest

Testing the recommended remedy atm

This is likely a sway issue: https://github.com/FuelLabs/sway/blob/master/forc/Cargo.toml#L5

Was actually due to not setting
rustup default stable

Closing this issue as that is recommended there, although adding as a warning or similar on forc's cargo page could be worth it.


Web Components:  CTA section variant (aka Promo Group) - Consulting support

User Story

As a [user role below]:
IBM.com Library developer

I need to:
create/change the Promo Group

so that I can:
provide the ibm.com adopter developers components they can use to build ibm.com web pages

Additional information

Story within Storybook with corresponding knobs
Utilize Carbon
Create with Shadow DOM and Custom Elements standards
See the Epic for the Design and Functional specs information
Visual QA testing issue (#5220 )
Prod QA testing issue (#5221 )

Pull out "CTA block" as a component
Remove "Promo group" & "Promo item"
Dev by AEM team, Raph consult.  Dev story points 13 story points (Raveena assigned).  Target date:  March 19.  Raph consulting 3 story points.
@RaphaelAmadeu @andysherman2121 Link the AEM created PR to this issue and move it though the development pipelines as we normally do.

Acceptance criteria

[ ] Include README for the web component and corresponding styles
[ ] Create Web Components styles in styles package
[ ] Do not create knobs in Storybook that include JSON objects
[ ] Break out Storybook stories into multiple variation stories, if applicable
[ ] Create codesandbox example under /packages/web-components/examples/codesandbox and include in README
[ ] Minimum 80% unit test coverage
[ ] Update the Carbon for ibm.com website component data file to be sure the web site Component Status and Storybook links are correct
[ ] If a design is provided, the Designer is included as a Reviewer in the Pull Request
[ ] Provide a direct link to the deploy preview for the designer in the Pull Request description
[ ] A comment is posted in the Prod QA issue, tagging Praveen when development is finished

Sandeep mentioned in satellite team slack that Raveena will take up this story from AEM side. fyi @RaphaelAmadeu

We just had an discussion, and agreed to make CTA Block into a component that shall be used within CTA Section.
We'll have the knobs mainly set on the CTA Block story and have the variations on CTA Section.
CC: @photodow @andysherman2121

@RobertaJHahn Adding myself back to this ticket. I started helping out Raveena with this

PR (#5330 ) referenced above will not be used.  This issue was changed from a consulting issue to a DDS engineering issue as the DDS team will  build this component.


3 logos

Sizes of the images I was given were all over the place. Frontline, in particular, is too small. But this is the right direction, at least. @afred : please review.

I can help out with sizing the logos, just let me know...

These should be sized well for the collection page banners.

and here's what they look like with a background...

New logos uploaded to S3. same filenames. Looks good. (Would have been better to open a new ticket for this to be sure it doesn't get lost.)


Enlargement is slow even though withoutEnlargement is specified

Question about an existing feature
What happens when attempting to increase the size of a GIF when withoutEnlargement is true? Why would that take a long time (seconds) as opposed to being nearly instantaneous?
What are you trying to achieve?
I have a GIF resizer, but I don't allow the size of the image to be increased. I set withoutEnlargement expecting the result to be the original image if a request tries to increase a dimension. The output is the same image, but it takes as long as a normal resize operation.
When you searched for similar issues, what did you find that might be related?
Couldn't find anything
Please provide a minimal, standalone code sample, without other dependencies, that demonstrates this question
const inStream = ...grab image from S3 (this request takes a few hundred ms)...

let transformer = sharp({ animated: true, failOnError: false })
transformer = transformer.resize({ width: 10000, withoutEnlargement: true })
transformer = transformer.gif()

inStream.pipe(transformer)
buffer = await transformer.toBuffer()

Please provide sample image(s) that help explain this question
Any GIF should work. I'm testing with an ~8MB gif that's about 4-5 seconds long.

Why would that take a long time (seconds) as opposed to being nearly instantaneous?

The input will always be decoded and the output will always be encoded, regardless of the operations that need to occur, if any. Encoding an 8MB animated GIF file is probably the bottleneck here.

@lovell thanks for the quick response! I guess I could just use the metadata API and skip the transform.
If anyone encounters this, you could modify the code above with something like:
inStream.pipe(transformer)

const metadata = await transformer.metadata()
if (withoutEnlargement && metadata.width < requestedWidth) {
  // skip transform
}

@lovell quick question. Is it expected that .metadata() throws transform errors (like Input image exceeds pixel limit)? I wasn't expecting to have to catch exceptions when using it.

Yes, it is a safety feature and all input is verified against this limit. A few of the more esoteric formats sometimes require pixel data to be decoded when determining metadata (e.g. custom libvips with support for *magick).


SuperDialog does not close

I am trying to close super dialog on the press of "cancel" button by setting state to false in Modifier.clickable inside a column which is the container for the content, I can see the state changing. But dialog won't hide.

Need to use dismissDialog(showDialog) to close the SuperDialog.
    val showDialog = remember { mutableStateOf(false) }
    SuperDialog(
        title = "Dialog",
        summary = "Summary",
        show = showDialog,
        onDismissRequest = {
            dismissDialog(showDialog)
        }
    ) {
        TextButton(
            text = "Confirm",
            onClick = {
                dismissDialog(showDialog)
            },
            modifier = Modifier.weight(1f),
            colors = ButtonDefaults.textButtonColorsPrimary()
        )
    }

Example code: https://github.com/miuix-kotlin-multiplatform/miuix/blob/v0.3.0/composeApp/src/commonMain/kotlin/component/TextComponent.kt#L416

Thanks for pointing out, it worked!


Update the URLs used for videos in PDF and EPUB output

Thank you for contributing to Quire! Please complete the form below to submit your pull request for review.
For the Title of this pull request, please use the format "Type/Issue-#: Brief description." For Type, the options are Fix, Feature, Docs, or Chore. Issue-# is only needed if this pull request addresses an exisiting issue.
Checklist
Please put an X within the brackets that apply [X].

[X] I have read the CONTRIBUTING.md file

[X] I have made my changes in a new branch and not directly in the main branch

[ ] This pull request is ready for final review by the Quire team

Is this pull request related to an open issue? If so, what is the issue number?
n/a
Please briefly describe the goal of this pull request and how it may impact Quire's functionality.
To update the Vimeo and YouTube URLs that are added above the figure captions in the PDF and EPUB output, so that they work consistently and are in as short a form as possible for readers.
Please describe the changes you made, and call out any details you think are particularly relevant for the Quire team to note in their review.
Previously, the emitted Vimeo URL was the same as the embed URL and not consistently working, and the YouTube URL worked but there's a shorter version available. So I updated the sourceUrl for each.
One question I had was around the replace() function being used for the Vimeo URLs. It's necessary and working, but it assumes the media_id will be supplied as a string. In a case like media_id: 672853278 where the id is not quoted, it is read as an integer and breaks the build/preview process when it runs into replace(). Could/should we also be converting the media_id to a string to eliminate this error? Or is this just something we need to document for users? To tell them they always need to quote media_ids?
Does this pull request necessitate changes to Quire's documentation?
n/a
Include screenshots of before/after if applicable.
n/a
Additional Comments

@thegetty/int-dev I made this small fix in our Getty books, so I thought I'd submit it as a PR here. (Though granted, I maybe should have created an issue for it first?)
I posed a question above about converting the media_id to a string. Can you take a look whenever you have a chance and let me know what you think? No rush.


当searcher和qrs启动失败再次循环启动时，增加了sleep机制

当searcher和qrs启动失败再次循环启动时，增加了1s的sleep。

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.lvjiang seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Feature: clear unused memory for pentagon children

This is a fantastic library!
I've encountered an inconsistency between h3ToChildren and kRing: The later sets memory to zero for pentagons. This left me confused when using h3ToChildren on pentagons which in my case returned valid indices (left over in memory from other calls) for the children that are skipped.
This pull request zeroes out memory for the unused slots.
Alternatively, the difference should at least be documented to let us know to use calloc.

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

Thanks! I've updated the PR accordingly.

Coverage remained the same at 100.0% when pulling 498e65d7a380c91b956c1bb0a51fc5fee15b81f5 on zachasme:feature-pentagon-zeroed-child into 518b324f30549244d31fedc242a3a97dc59916af on uber:master.


Failed to install tremor language server

Error message:
Compiling tremor-language-server v0.10.1
error: failed to run custom build command for `tremor-language-server v0.10.1`

Caused by:
  process didn't exit successfully: `/var/folders/84/zhf78lt50hsghfh5s6g9jmk00000gn/T/cargo-installweU1XI/release/build/tremor-language-server-cf2b09233f27bfff/build-script-build` (exit code: 101)
  --- stdout
  Dumping function docs for tremor-script to: /var/folders/84/zhf78lt50hsghfh5s6g9jmk00000gn/T/cargo-installweU1XI/release/build/tremor-language-server-11042796ebe3999c/out/function_docs.tremor-script.bin
  Detected tremor-script version from cargo lock file: 0.10.1
  Could not find tremor-script src in local cargo registry, so downloading it now...
  Downloading crate `tremor-script==0.10.1` from https://crates.io/api/v1/crates/tremor-script/0.10.1/download

  --- stderr
  thread 'main' panicked at 'there is no reactor running, must be called from the context of a Tokio 1.x runtime', /Users/rohitdandamudi/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.2.0/src/runtime/blocking/pool.rs:85:33
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...
error: failed to compile `tremor-language-server v0.10.1`, intermediate artifacts can be found at `/var/folders/84/zhf78lt50hsghfh5s6g9jmk00000gn/T/cargo-installweU1XI`

Caused by:
  build failed

OS: MacOS Mojave
Command: tremor-runtime rohitdandamudi$ cargo install tremor-language-server

We didnt release a new language-server yet, it seems. Gonna change that today.
Sorry for the inconvenience!

can you try again? I just released 0.10.2.

Yup, it works now.
Thank you!! 😁


Remove deprecated integrations

:star2: What does this PR do?

5136956 - chore(integration): Remove deprecated integrations

:bug: Recommendations for testing

Check if Track extension still works properly. 👌
Check Settings page and try to enable a few integrations and test them out.

:memo: Links to relevant issues or information
Closes #2101

Great cleanup! LGTM, let's only fix the CI error and merge it!


Bugsnag does not report errors that are not of type Error

Description
Bugsnag's error handler does not report errors that are not of type Error. This is problematic for existing codebases that are throwing Strings or Objects.
Issue
Codebase is throwing objects and strings that are not making it up to the bugsnag dashboard
https://github.com/bugsnag/bugsnag-react-native/blob/master/src/Bugsnag.js#L84
does the type check.
Ideally, the SDK can handle any object type...
Perhaps do something like this?
 notify = async (error, beforeSendCallback, blocking, postSendCallback, _handledState) => {
    if(typeof error !== 'Error') error = new Error(error);
    /*if (!(error instanceof Error)) {
      console.warn('Bugsnag could not notify: error must be of type Error')
      if (postSendCallback) { postSendCallback(false) }
      return
    }*/
}
    if(typeof msg !== 'object') msg = new Error(msg);
    bugsnag && bugsnag.notify(msg);

Environment
Library versions:

├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>└─<EMAIL_ADDRESS>

cocoapods version (if any) (pod -v):

iOS/Android version(s):

simulator/emulator or physical device?:

debug mode or production?:

[x] (iOS only) [BugsnagReactNative start] is present in the
application:didFinishLaunchingWithOptions: method in your AppDelegate
class?

[x] (Android only) BugsnagReactNative.start(this) is present in the
onCreate method of your MainApplication class?

Example code snippet
import { Client, Configuration } from 'bugsnag-react-native';

throw "String Error"

Thanks for the report @cpetzel - I believe this ticket is similar to #131, so I'm closing it for now.


Default thumbnail for audio and video resources that don't have a thumbnail

Should we have a default thumbnail for audio and video resources that don't provide a thumbnail e.g:

No thumb audio only: Simplest Manifest - Audio - ThumbnailPanel
No thumb video only: Simplest Manifest - Video - ThumbnailPanel

Should we have a fallback image for manifests where we struggle to get a thumbnail e.g:

Multiple choice of images in a single view - no thumbnail from choice ThumbnailPanel
Image Rotation Two Ways - image service selector - ThumbnailPanel
Image Rotation Two Ways - css rotation - ThumbnailPanel

Ref #4

Probably not important enough to get done by the conference
Pass in a default image but could be empty.


[schema registry] Migrate samples to workflow v2

Fix #14480

@witemple-msft Thanks for the great work on this and the impeccable documentation on how to migrate. 🎉

Given that Schema Registry is not yet GA, it has had only 1 preview and has no work in progress this semester, I would say we skip publishing to docs.microsoft.com/samples

Ok, I've set disableDocsMs for now. Do I need to also remove the productSlugs or is that good enough?

@nguerrera the last thing to do is to regenerate one final time, as disableDocsMs affects the output of the publication scripts. The YAML blob at the beginning of the READMEs is what actually controls publication.

@witemple-msft Ah, of course! Doh. Done.


Tune Arm Extension/Angles presets

ArmConstants.java contains a list of presets for the Arm positions.
Those positions need to be tuned with testing.

Fixed before BSU Weekend


config e

Getting page up and running
Mostly changed _config.yml including image

Give it a try?

Please reject this. I was trying to commit to my own repository. This is still new for me.


enshrouded-1  | [ecss] Could not add component e3b96393 for entity 1371

enshrouded-1  | [ecss] Could not add component e3b96393 for entity 1371 enshrouded-1  | [ecss] Could not add component e3b96393 for entity 1373 enshrouded-1  | [ecss] Could not add component e3b96393 for entity 1375 enshrouded-1  | [ecss] Could not add component e3b96393 for entity 1380 enshrouded-1  | [ecss] Could not add component e3b96393 for entity 1382 enshrouded-1  | [ecss] Could not add component e3b96393 for entity 1384 enshrouded-1  | [ecss] Could not add component e3b96393 for entity 1386 enshrouded-1  | [ecss] Could not add component e3b96393 for entity 1388 enshrouded-1  | [ecss] Could not add component e3b96393 for entity 1390 enshrouded-1  | [ecss] Could not add component e3b96393 for entity 1392 enshrouded-1  | [ecss] Could not add component e3b96393 for entity 1394 enshrouded-1  | [ecss] Could not add component e3b96393 for entity 1396 enshrouded-1  | [ecss] Could not add component e3b96393 for entity 1398 enshrouded-1  | [ecss] Could not add component e3b96393 for entity 1400 enshrouded-1  | [ecss] Could not add component e3b96393 for entity 1402 enshrouded-1  | [ecss] Could not add component e3b96393 for entity 1404 enshrouded-1  | [ecss] Could not add component e3b96393 for entity 1406 enshrouded-1  | [ecss] Could not add component e3b96393 for entity 1408 enshrouded-1  | [ecss] Stats:  Upd:3,360  (17.9ms)  Time:60,008ms  Total:47,989ms  Max:18ms  Avg:14.3ms  +:0  -:0  Ent:5,870  Pred:0 enshrouded-1  | [ecss] Could not add component e3b96393 for entity 1416 enshrouded-1  | [ecss] Could not add component e3b96393 for entity 1418 enshrouded-1  | [ecss] Could not add component e3b96393 for entity 1420 enshrouded-1  | [ecss] Could not add component e3b96393 for entity 1422 enshrouded-1  | [ecss] Could not add component e3b96393 for entity 1424 enshrouded-1  | [ecss] Could not add component e3b96393 for entity 1427 enshrouded-1  | [ecss] Could not add component e3b96393 for entity 1445 enshrouded-1  | [ecss] Could not add component e3b96393 for entity 1447 enshrouded-1  | [ecss] Could not add component e3b96393 for entity 1449 enshrouded-1  | [ecss] Could not add component e3b96393 for entity 1457 enshrouded-1  | [ecss] Could not add component e3b96393 for entity 1459 enshrouded-1  | [ecss] Could not add component e3b96393 for entity 1461 enshrouded-1  | [ecss] Could not add component e3b96393 for entity 1464 enshrouded-1  | [ecss] Could not add component e3b96393 for entity 1467 enshrouded-1  | [ecss] Could not add component e3b96393 for entity 1469 enshrouded-1  | [ecss] Could not add component e3b96393 for entity 1471 enshrouded-1  | [ecss] Could not add component e3b96393 for entity 1473
this is how i setup my docker compose
services:
enshrouded:
image: mbround18/enshrouded-docker:latest
build:
context: .
dockerfile: Dockerfile
platforms:
- linux/amd64
environment:
SERVER_NAME: "Bajubesi Enshrouded Server" # Optional, Name of the server
PASSWORD: "mypasswd" # Optional, Password for the server
#      SAVE_DIRECTORY: ./savegame # Optional, Save directory for the game
#      LOG_DIRECTORY: ./logs # Optional, Log directory for the server
#      SERVER_IP: <IP_ADDRESS> # Optional, IP address for the server
#      GAME_PORT: 15636 # Optional, Game port for the server
#      QUERY_PORT: 15637 # Optional, Query port for the server
#      SLOT_COUNT: 16 # Optional, Number of slots for the server
ports:
- "15636:15636/udp"
- "15636:15636/tcp"
- "15637:15637/udp"
- "15637:15637/tcp"
volumes:
- ./data:/home/steam/enshrouded
backups:
image: mbround18/backup-cron:latest
environment:
- SCHEDULE=*/10 * * * *
- INPUT_FOLDER=/home/steam/enshrouded/savegame
- OUTPUT_FOLDER=/home/steam/backups
- OUTPUT_USER=1000
- OUTPUT_GROUP=1000
- RETAIN_N_DAYS=5
volumes:
- ./data:/home/steam/enshrouded
- ./backups:/home/steam/backups
restart: unless-stopped

That looks good, what kind of processor are you using?

That looks good, what kind of processor are you using?
root@HPZ440-Server

OS: Ubuntu 22.04.4 LTS x86_64
Kernel: 6.5.0-21-generic
Uptime: 22 hours, 28 mins
Shell: bash 5.1.16
CPU: Intel Xeon E5-2680 v4 (28) @ 3.300GHz
GPU: NVIDIA Quadro K2000
Memory: 20082MiB / 64207MiB


refactor: add derive debug for PrismaClient

PrismaClient has no need to implement Debug, and a client generated with the change you have provided won't actually compile since QueryExecutor doesn't implement Debug.


Add support for generating classes in the global namespace

This makes it possible to create a CodeBuilder without needing to specify a namespace. It uses a new static method CreateInGlobalNamespace to make it a bit more intentional on the users part as it would be somewhat of an edge-case (that I just happen to need 😄 )

Thanks for the PR... you'll be able to grab a copy of the package from the CI build... I need to do a review of some things before I publish a release... but something official should be up hopefully next week

Thanks very much for the quick review & merge @dansiegel, unfortunately it looks like there's an authentication failure in the GH action: https://github.com/dansiegel/CodeGenHelpers/actions/runs/4449130543/jobs/7812880503

it just failed to publish to my internal feed... but the generated NuGet should still be attached to the build for you to try out


Bug: mdx-loader caching issue => linked md files should be added as dependencies

🐛 Bug Report
Suppose you have:
# md file

[link](./otherMdFile.md)

Then if the linked md file change from slug: /path1 to slug: /path2 the md file must be "invalidated"
Otherwise, we'll keep linking to /path1 (instead of new /path2) due to Webpack caches.
mdx-loader probably needs to collect linked file paths, and call this.addDependency(linkedFilePath);

Issue noticed in PR https://github.com/facebook/docusaurus/pull/5755
https://app.netlify.com/sites/docusaurus-2/deploys/6171611d255a130008c35dff
Had to clear the Netlify cache to fix the build failure

can you explain this issue a bit more @slorber

can you explain this issue a bit more @slorber

This is not really an issue for first-time contributors @balogun14, I take notes for myself to solve this problem on my own later.

@slorber  Thank you for the response i will check other issues then


Generated by :no_entry_sign: Danger


Update documentation numbers

#17633
Testing plan:
Ran linters
GIFs or screenshots:

This is complete and ready to be reviewed @timabbott

This is awesome @adambirds!  I posted comments on a couple categories of style decisions I'd have preferred to have been made differently; and then merged the ~50% of commits where those comments didn't apply here, with one extra commit to fix some preexisting organization issues with the Google Calendar docs: a14cd23bdb96933eecadd892d6d4c6158efe3968
One thing I'm noticing when looking at this batch of pages is that many of them have ancient screenshots don't follow other aspects of our current style guidelines.  See https://zulip.readthedocs.io/en/latest/documentation/integrations.html#writing-guidelines
I think what must have happened is that because they're largely not webhook integrations, they got missed in the various sweeps of zerver/webhooks/*/doc.md.  And also because they're not webhook integrations, our system for automatically generating current-UI screenshots doesn't work for them either.
Anyway, those are thoughts for later; let me know when you've updated the remaining commits for this sweet!

@timabbott will get these updated probably tomorrow or day after. Just note the question about the bits of code surrounded with {raw} tags.

@timabbott I think I've done all these, ready for review, let me know if I have missed any. Thanks

@timabbott this now ready for a review again. The screenshots below show where I have had to leave some of the indents in the twitter, hello world and capistrano docs without the backticks as otherwise it doesn't render correctly.

This is great, merged, thanks @adambirds!
Most of the integrations from this pull request have extremely old screenshots (some of them I can date to early 2013, based on the visual design).  Unfortunately they're potentially kinda a pain to redo, since unlike the normal webhooks, we can't trivially generate them using tools/generate-integration-docs-screenshot.  It may be worth looking at extending that tool to support fixtures for this sort of integration that is client-side code posting to the POST /messages API endpoint -- I can imagine just hardcoding sample message content for those from studying the examples.
@punchagan FYI in case you have ideas for how to design that.

Opened https://github.com/zulip/zulip/issues/17792 to track that follow-up project.


Crash happening with StreamHandler for the camera

Steps to Reproduce
I have no idea how to reproduce it, but it only happened in release mode for my beta testers.
It seems according to the trace that it comes from the camera package but i am absolutely not sure.

Expected results:
The app should not crash.
Actual results:
The app crashes.

Logs
Crashed: com.apple.main-thread
EXC_BAD_ACCESS KERN_INVALID_ADDRESS 0x68732d75652f2f3a
0  libobjc.A.dylib                0x15c8 objc_msgSend + 8
1  Flutter                        0x4ecd60 ___ZL39SetStreamHandlerMessageHandlerOnChannelPU31objcproto20FlutterStreamHandler8NSObjectP8NSStringPU33objcproto22FlutterBinaryMessengerS_PU29objcproto18FlutterMethodCodecS__block_invoke + 628
2  Flutter                        0x3eca8 flutter::PlatformViewIOS::HandlePlatformMessage(std::__1::unique_ptr<flutter::PlatformMessage, std::__1::default_delete<flutter::PlatformMessage> >) + 524
3  Flutter                        0x3bb628 std::__1::__function::__func<fml::internal::CopyableLambda<flutter::Shell::OnEngineHandlePlatformMessage(std::__1::unique_ptr<flutter::PlatformMessage, std::__1::default_delete<flutter::PlatformMessage> >)::$_16>, std::__1::allocator<fml::internal::CopyableLambda<flutter::Shell::OnEngineHandlePlatformMessage(std::__1::unique_ptr<flutter::PlatformMessage, std::__1::default_delete<flutter::PlatformMessage> >)::$_16> >, void ()>::operator()() + 92
4  Flutter                        0x2e8d8c fml::MessageLoopImpl::FlushTasks(fml::FlushType) + 1592
5  Flutter                        0x2ecae4 fml::MessageLoopDarwin::OnTimerFire(__CFRunLoopTimer*, fml::MessageLoopDarwin*) + 32
6  CoreFoundation                 0xae268 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 32
7  CoreFoundation                 0x32c40 __CFRunLoopDoTimer + 1076
8  CoreFoundation                 0x2d43c __CFRunLoopDoTimers + 328
9  CoreFoundation                 0xbc58 __CFRunLoopRun + 1944
10 CoreFoundation                 0x1f3b8 CFRunLoopRunSpecific + 600
11 GraphicsServices               0x138c GSEventRunModal + 164
12 UIKitCore                      0x5196a8 -[UIApplication _run] + 1100
13 UIKitCore                      0x2987f4 UIApplicationMain + 2092
14 Runner                         0x71c8 main + 7 (AppDelegate.swift:7)
15 ???                            0x1038f5a24 (Missing)

Thread
0  libsystem_kernel.dylib         0x1b2c __workq_kernreturn + 8
1  libsystem_pthread.dylib        0x1140 _pthread_wqthread + 364
2  libsystem_pthread.dylib        0xe94 start_wqthread + 8

Thread
0  libsystem_kernel.dylib         0x1b2c __workq_kernreturn + 8
1  libsystem_pthread.dylib        0x1140 _pthread_wqthread + 364
2  libsystem_pthread.dylib        0xe94 start_wqthread + 8

io.flutter.camera.dispatchqueue
0  libsystem_kernel.dylib         0x1504 mach_msg_trap + 8
1  libsystem_kernel.dylib         0x1b9c mach_msg + 76
2  CoreFoundation                 0x7688 __CFRunLoopServiceMachPort + 372
3  CoreFoundation                 0xb97c __CFRunLoopRun + 1212
4  CoreFoundation                 0x1f3b8 CFRunLoopRunSpecific + 600
5  AVFCore                        0x2f79c -[AVRunLoopCondition _waitInMode:untilDate:] + 412
6  AVFCapture                     0x51b84 -[AVCaptureSession _stopFigCaptureSession] + 436
7  AVFCapture                     0x348b8 -[AVCaptureSession _setRunning:] + 180
8  camera                         0x6568 -[FLTCam close] + 68
9  camera                         0x99e0 -[CameraPlugin handleMethodCallAsync:result:] + 2356
10 camera                         0x9034 __40-[CameraPlugin handleMethodCall:result:]_block_invoke + 68
11 libdispatch.dylib              0x2914 _dispatch_call_block_and_release + 32
12 libdispatch.dylib              0x4660 _dispatch_client_callout + 20
13 libdispatch.dylib              0xbde4 _dispatch_lane_serial_drain + 672
14 libdispatch.dylib              0xc958 _dispatch_lane_invoke + 392
15 libdispatch.dylib              0x171a8 _dispatch_workloop_worker_thread + 656
16 libsystem_pthread.dylib        0x10f4 _pthread_wqthread + 288
17 libsystem_pthread.dylib        0xe94 start_wqthread + 8

com.apple.uikit.eventfetch-thread
0  libsystem_kernel.dylib         0x1504 mach_msg_trap + 8
1  libsystem_kernel.dylib         0x1b9c mach_msg + 76
2  CoreFoundation                 0x7688 __CFRunLoopServiceMachPort + 372
3  CoreFoundation                 0xb97c __CFRunLoopRun + 1212
4  CoreFoundation                 0x1f3b8 CFRunLoopRunSpecific + 600
5  Foundation                     0x18354 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 236
6  Foundation                     0x59c28 -[NSRunLoop(NSRunLoop) runUntilDate:] + 92
7  UIKitCore                      0x4928a4 -[UIEventFetcher threadMain] + 524
8  Foundation                     0x6836c __NSThread__start__ + 808
9  libsystem_pthread.dylib        0x19a4 _pthread_start + 148
10 libsystem_pthread.dylib        0xea0 thread_start + 8

Thread
0  libsystem_pthread.dylib        0xe8c start_wqthread + 258

Thread
0  libsystem_pthread.dylib        0xe8c start_wqthread + 258

Thread
0  libsystem_kernel.dylib         0x1b2c __workq_kernreturn + 8
1  libsystem_pthread.dylib        0x1140 _pthread_wqthread + 364
2  libsystem_pthread.dylib        0xe94 start_wqthread + 8

io.flutter.1.ui
0  libsystem_kernel.dylib         0x1504 mach_msg_trap + 8
1  libsystem_kernel.dylib         0x1b9c mach_msg + 76
2  CoreFoundation                 0x7688 __CFRunLoopServiceMachPort + 372
3  CoreFoundation                 0xb97c __CFRunLoopRun + 1212
4  CoreFoundation                 0x1f3b8 CFRunLoopRunSpecific + 600
5  Flutter                        0x2ec9b4 fml::MessageLoopDarwin::Run() + 88
6  Flutter                        0x2eb7a4 void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, fml::Thread::Thread(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&)::$_0> >(void*) + 196
7  libsystem_pthread.dylib        0x19a4 _pthread_start + 148
8  libsystem_pthread.dylib        0xea0 thread_start + 8

io.flutter.1.raster
0  libsystem_kernel.dylib         0x1504 mach_msg_trap + 8
1  libsystem_kernel.dylib         0x1b9c mach_msg + 76
2  CoreFoundation                 0x7688 __CFRunLoopServiceMachPort + 372
3  CoreFoundation                 0xb97c __CFRunLoopRun + 1212
4  CoreFoundation                 0x1f3b8 CFRunLoopRunSpecific + 600
5  Flutter                        0x2ec9b4 fml::MessageLoopDarwin::Run() + 88
6  Flutter                        0x2eb7a4 void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, fml::Thread::Thread(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&)::$_0> >(void*) + 196
7  libsystem_pthread.dylib        0x19a4 _pthread_start + 148
8  libsystem_pthread.dylib        0xea0 thread_start + 8

io.flutter.1.io
0  libsystem_kernel.dylib         0x1504 mach_msg_trap + 8
1  libsystem_kernel.dylib         0x1b9c mach_msg + 76
2  CoreFoundation                 0x7688 __CFRunLoopServiceMachPort + 372
3  CoreFoundation                 0xb97c __CFRunLoopRun + 1212
4  CoreFoundation                 0x1f3b8 CFRunLoopRunSpecific + 600
5  Flutter                        0x2ec9b4 fml::MessageLoopDarwin::Run() + 88
6  Flutter                        0x2eb7a4 void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, fml::Thread::Thread(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&)::$_0> >(void*) + 196
7  libsystem_pthread.dylib        0x19a4 _pthread_start + 148
8  libsystem_pthread.dylib        0xea0 thread_start + 8

io.flutter.1.profiler
0  libsystem_kernel.dylib         0x1504 mach_msg_trap + 8
1  libsystem_kernel.dylib         0x1b9c mach_msg + 76
2  CoreFoundation                 0x7688 __CFRunLoopServiceMachPort + 372
3  CoreFoundation                 0xb97c __CFRunLoopRun + 1212
4  CoreFoundation                 0x1f3b8 CFRunLoopRunSpecific + 600
5  Flutter                        0x2ec9b4 fml::MessageLoopDarwin::Run() + 88
6  Flutter                        0x2eb7a4 void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, fml::Thread::Thread(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&)::$_0> >(void*) + 196
7  libsystem_pthread.dylib        0x19a4 _pthread_start + 148
8  libsystem_pthread.dylib        0xea0 thread_start + 8

io.worker.1
0  libsystem_kernel.dylib         0x1f90 __psynch_cvwait + 8
1  libsystem_pthread.dylib        0x8254 _pthread_cond_wait + 1228
2  libc++.1.dylib                 0x9ddc std::__1::condition_variable::wait(std::__1::unique_lock<std::__1::mutex>&) + 28
3  Flutter                        0x2e6428 void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, fml::ConcurrentMessageLoop::ConcurrentMessageLoop(unsigned long)::$_0> >(void*) + 280
4  libsystem_pthread.dylib        0x19a4 _pthread_start + 148
5  libsystem_pthread.dylib        0xea0 thread_start + 8

io.worker.2
0  libsystem_kernel.dylib         0x1f90 __psynch_cvwait + 8
1  libsystem_pthread.dylib        0x8254 _pthread_cond_wait + 1228
2  libc++.1.dylib                 0x9ddc std::__1::condition_variable::wait(std::__1::unique_lock<std::__1::mutex>&) + 28
3  Flutter                        0x2e6428 void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, fml::ConcurrentMessageLoop::ConcurrentMessageLoop(unsigned long)::$_0> >(void*) + 280
4  libsystem_pthread.dylib        0x19a4 _pthread_start + 148
5  libsystem_pthread.dylib        0xea0 thread_start + 8

io.worker.3
0  libsystem_kernel.dylib         0x1f90 __psynch_cvwait + 8
1  libsystem_pthread.dylib        0x8254 _pthread_cond_wait + 1228
2  libc++.1.dylib                 0x9ddc std::__1::condition_variable::wait(std::__1::unique_lock<std::__1::mutex>&) + 28
3  Flutter                        0x2e6428 void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, fml::ConcurrentMessageLoop::ConcurrentMessageLoop(unsigned long)::$_0> >(void*) + 280
4  libsystem_pthread.dylib        0x19a4 _pthread_start + 148
5  libsystem_pthread.dylib        0xea0 thread_start + 8

io.worker.4
0  libsystem_kernel.dylib         0x1f90 __psynch_cvwait + 8
1  libsystem_pthread.dylib        0x8254 _pthread_cond_wait + 1228
2  libc++.1.dylib                 0x9ddc std::__1::condition_variable::wait(std::__1::unique_lock<std::__1::mutex>&) + 28
3  Flutter                        0x2e6428 void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, fml::ConcurrentMessageLoop::ConcurrentMessageLoop(unsigned long)::$_0> >(void*) + 280
4  libsystem_pthread.dylib        0x19a4 _pthread_start + 148
5  libsystem_pthread.dylib        0xea0 thread_start + 8

io.worker.5
0  libsystem_kernel.dylib         0x1f90 __psynch_cvwait + 8
1  libsystem_pthread.dylib        0x8254 _pthread_cond_wait + 1228
2  libc++.1.dylib                 0x9ddc std::__1::condition_variable::wait(std::__1::unique_lock<std::__1::mutex>&) + 28
3  Flutter                        0x2e6428 void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, fml::ConcurrentMessageLoop::ConcurrentMessageLoop(unsigned long)::$_0> >(void*) + 280
4  libsystem_pthread.dylib        0x19a4 _pthread_start + 148
5  libsystem_pthread.dylib        0xea0 thread_start + 8

io.worker.6
0  libsystem_kernel.dylib         0x1f90 __psynch_cvwait + 8
1  libsystem_pthread.dylib        0x8254 _pthread_cond_wait + 1228
2  libc++.1.dylib                 0x9ddc std::__1::condition_variable::wait(std::__1::unique_lock<std::__1::mutex>&) + 28
3  Flutter                        0x2e6428 void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, fml::ConcurrentMessageLoop::ConcurrentMessageLoop(unsigned long)::$_0> >(void*) + 280
4  libsystem_pthread.dylib        0x19a4 _pthread_start + 148
5  libsystem_pthread.dylib        0xea0 thread_start + 8

dart:io EventHandler
0  libsystem_kernel.dylib         0x2e7c kevent + 8
1  Flutter                        0x4abdc8 dart::bin::EventHandlerImplementation::EventHandlerEntry(unsigned long) + 436
2  Flutter                        0x4dd608 dart::bin::ThreadStart(void*) + 44
3  libsystem_pthread.dylib        0x19a4 _pthread_start + 148
4  libsystem_pthread.dylib        0xea0 thread_start + 8

DartWorker
0  libsystem_kernel.dylib         0x1f90 __psynch_cvwait + 8
1  libsystem_pthread.dylib        0x8280 _pthread_cond_wait + 1272
2  Flutter                        0x5e02f0 dart::Monitor::WaitMicros(long long) + 128
3  Flutter                        0x653224 dart::ThreadPool::Worker::Main(unsigned long) + 664
4  Flutter                        0x5dfc78 dart::ThreadStart(void*) + 288
5  libsystem_pthread.dylib        0x19a4 _pthread_start + 148
6  libsystem_pthread.dylib        0xea0 thread_start + 8

DartWorker
0  libsystem_kernel.dylib         0x1f90 __psynch_cvwait + 8
1  libsystem_pthread.dylib        0x8280 _pthread_cond_wait + 1272
2  Flutter                        0x5e02f0 dart::Monitor::WaitMicros(long long) + 128
3  Flutter                        0x653224 dart::ThreadPool::Worker::Main(unsigned long) + 664
4  Flutter                        0x5dfc78 dart::ThreadStart(void*) + 288
5  libsystem_pthread.dylib        0x19a4 _pthread_start + 148
6  libsystem_pthread.dylib        0xea0 thread_start + 8

DartWorker
0  libsystem_kernel.dylib         0x1f90 __psynch_cvwait + 8
1  libsystem_pthread.dylib        0x8280 _pthread_cond_wait + 1272
2  Flutter                        0x5e02f0 dart::Monitor::WaitMicros(long long) + 128
3  Flutter                        0x653224 dart::ThreadPool::Worker::Main(unsigned long) + 664
4  Flutter                        0x5dfc78 dart::ThreadStart(void*) + 288
5  libsystem_pthread.dylib        0x19a4 _pthread_start + 148
6  libsystem_pthread.dylib        0xea0 thread_start + 8

Thread
0  libsystem_pthread.dylib        0xe8c start_wqthread + 258

Thread
0  libsystem_pthread.dylib        0xe8c start_wqthread + 258

Thread
0  libsystem_kernel.dylib         0x1b2c __workq_kernreturn + 8
1  libsystem_pthread.dylib        0x1140 _pthread_wqthread + 364
2  libsystem_pthread.dylib        0xe94 start_wqthread + 8

com.google.firebase.crashlytics.MachExceptionServer
0  FirebaseCrashlytics            0x1f44c FIRCLSProcessRecordAllThreads + 184
1  FirebaseCrashlytics            0x1f82c FIRCLSProcessRecordAllThreads + 1176
2  FirebaseCrashlytics            0x167f0 FIRCLSHandler + 48
3  FirebaseCrashlytics            0x195b8 FIRCLSMachExceptionServer + 1248
4  libsystem_pthread.dylib        0x19a4 _pthread_start + 148
5  libsystem_pthread.dylib        0xea0 thread_start + 8

Thread
0  libsystem_pthread.dylib        0xe8c start_wqthread + 258

AVAudioSession Notify Thread
0  libsystem_kernel.dylib         0x1504 mach_msg_trap + 8
1  libsystem_kernel.dylib         0x1b9c mach_msg + 76
2  CoreFoundation                 0x7688 __CFRunLoopServiceMachPort + 372
3  CoreFoundation                 0xb97c __CFRunLoopRun + 1212
4  CoreFoundation                 0x1f3b8 CFRunLoopRunSpecific + 600
5  AudioSession                   0x6308 CADeprecated::GenericRunLoopThread::Entry(void*) + 164
6  AudioSession                   0xfd64 CADeprecated::CAPThread::Entry(CADeprecated::CAPThread*) + 92
7  libsystem_pthread.dylib        0x19a4 _pthread_start + 148
8  libsystem_pthread.dylib        0xea0 thread_start + 8

DartWorker
0  libsystem_kernel.dylib         0x1f90 __psynch_cvwait + 8
1  libsystem_pthread.dylib        0x8280 _pthread_cond_wait + 1272
2  Flutter                        0x5e02f0 dart::Monitor::WaitMicros(long long) + 128
3  Flutter                        0x653224 dart::ThreadPool::Worker::Main(unsigned long) + 664
4  Flutter                        0x5dfc78 dart::ThreadStart(void*) + 288
5  libsystem_pthread.dylib        0x19a4 _pthread_start + 148
6  libsystem_pthread.dylib        0xea0 thread_start + 8

DartWorker
0  libsystem_kernel.dylib         0x1f90 __psynch_cvwait + 8
1  libsystem_pthread.dylib        0x8280 _pthread_cond_wait + 1272
2  Flutter                        0x5e02f0 dart::Monitor::WaitMicros(long long) + 128
3  Flutter                        0x653224 dart::ThreadPool::Worker::Main(unsigned long) + 664
4  Flutter                        0x5dfc78 dart::ThreadStart(void*) + 288
5  libsystem_pthread.dylib        0x19a4 _pthread_start + 148
6  libsystem_pthread.dylib        0xea0 thread_start + 8

DartWorker
0  libsystem_kernel.dylib         0x1f90 __psynch_cvwait + 8
1  libsystem_pthread.dylib        0x8280 _pthread_cond_wait + 1272
2  Flutter                        0x5e02f0 dart::Monitor::WaitMicros(long long) + 128
3  Flutter                        0x653224 dart::ThreadPool::Worker::Main(unsigned long) + 664
4  Flutter                        0x5dfc78 dart::ThreadStart(void*) + 288
5  libsystem_pthread.dylib        0x19a4 _pthread_start + 148
6  libsystem_pthread.dylib        0xea0 thread_start + 8

DartWorker
0  libsystem_kernel.dylib         0x1f90 __psynch_cvwait + 8
1  libsystem_pthread.dylib        0x8280 _pthread_cond_wait + 1272
2  Flutter                        0x5e02f0 dart::Monitor::WaitMicros(long long) + 128
3  Flutter                        0x653224 dart::ThreadPool::Worker::Main(unsigned long) + 664
4  Flutter                        0x5dfc78 dart::ThreadStart(void*) + 288
5  libsystem_pthread.dylib        0x19a4 _pthread_start + 148
6  libsystem_pthread.dylib        0xea0 thread_start + 8

DartWorker
0  libsystem_kernel.dylib         0x1f90 __psynch_cvwait + 8
1  libsystem_pthread.dylib        0x8280 _pthread_cond_wait + 1272
2  Flutter                        0x5e02f0 dart::Monitor::WaitMicros(long long) + 128
3  Flutter                        0x653224 dart::ThreadPool::Worker::Main(unsigned long) + 664
4  Flutter                        0x5dfc78 dart::ThreadStart(void*) + 288
5  libsystem_pthread.dylib        0x19a4 _pthread_start + 148
6  libsystem_pthread.dylib        0xea0 thread_start + 8

com.apple.NSURLConnectionLoader
0  libsystem_kernel.dylib         0x1504 mach_msg_trap + 8
1  libsystem_kernel.dylib         0x1b9c mach_msg + 76
2  CoreFoundation                 0x7688 __CFRunLoopServiceMachPort + 372
3  CoreFoundation                 0xb97c __CFRunLoopRun + 1212
4  CoreFoundation                 0x1f3b8 CFRunLoopRunSpecific + 600
5  CFNetwork                      0x27a6a0 _CFURLStorageSessionCopyIdentifier + 59784
6  Foundation                     0x6836c __NSThread__start__ + 808
7  libsystem_pthread.dylib        0x19a4 _pthread_start + 148
8  libsystem_pthread.dylib        0xea0 thread_start + 8

com.squareup.SocketRocket.NetworkThread
0  libsystem_kernel.dylib         0x1504 mach_msg_trap + 8
1  libsystem_kernel.dylib         0x1b9c mach_msg + 76
2  CoreFoundation                 0x7688 __CFRunLoopServiceMachPort + 372
3  CoreFoundation                 0xb97c __CFRunLoopRun + 1212
4  CoreFoundation                 0x1f3b8 CFRunLoopRunSpecific + 600
5  Foundation                     0x18354 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 236
6  FirebaseDatabase               0x52f5c -[_FSRRunLoopThread main] + 252
7  Foundation                     0x6836c __NSThread__start__ + 808
8  libsystem_pthread.dylib        0x19a4 _pthread_start + 148
9  libsystem_pthread.dylib        0xea0 thread_start + 8

com.apple.CoreMotion.MotionThread
0  libsystem_kernel.dylib         0x1504 mach_msg_trap + 8
1  libsystem_kernel.dylib         0x1b9c mach_msg + 76
2  CoreFoundation                 0x7688 __CFRunLoopServiceMachPort + 372
3  CoreFoundation                 0xb97c __CFRunLoopRun + 1212
4  CoreFoundation                 0x1f3b8 CFRunLoopRunSpecific + 600
5  CoreFoundation                 0x9fa78 CFRunLoopRun + 64
6  CoreMotion                     0x13544 CLMotionActivity::isTypeInVehicle(CLMotionActivity::Type) + 21264
7  libsystem_pthread.dylib        0x19a4 _pthread_start + 148
8  libsystem_pthread.dylib        0xea0 thread_start + 8

com.apple.CFSocket.private
0  libsystem_kernel.dylib         0x21d0 select$DARWIN_EXTSN + 8
1  libsystem_kernel.dylib         0x21d0 __select + 8
2  CoreFoundation                 0xaa740 __CFSocketManager + 648
3  libsystem_pthread.dylib        0x19a4 _pthread_start + 148
4  libsystem_pthread.dylib        0xea0 thread_start + 8

[✓] Flutter (Channel stable, 2.8.0, on macOS 12.1 21C52 darwin-x64, locale fr-FR)
    • Flutter version 2.8.0 at /Users/foxtom/Desktop/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision cf44000065 (8 days ago), 2021-12-08 14:06:50 -0800
    • Engine revision 40a99c5951
    • Dart version 2.15.0

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/foxtom/Library/Android/sdk
    • Platform android-31, build-tools 31.0.0
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7281165)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 13.2)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • CocoaPods version 1.11.2

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

[✓] Android Studio (version 2020.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7281165)

[✓] VS Code (version 1.63.1)
    • VS Code at /Users/foxtom/Desktop/Visual Studio Code.app/Contents
    • Flutter extension version 3.29.0

[✓] Connected device (2 available)
    • macOS (desktop) • macos  • darwin-x64     • macOS 12.1 21C52 darwin-x64
    • Chrome (web)    • chrome • web-javascript • Google Chrome 96.0.4664.110

• No issues found!

@flutter-symbolizer-bot https://github.com/flutter/flutter/issues/95459#issue-1083076485

@flutter-symbolizer-bot https://github.com/flutter/flutter/issues/95459#issue-1083076485 force flutter#v2.8.0 ios release arm64

Hi @Tom3652, can we get a list of devices that are affected by this?

Hi @danagbemava-nc, yes sure but for now it only happened on one device :

I will update if this still happens and on other devices

Hi @Tom3652, would it be possible for you to share the code snippet you're using for the camera?

Mmh it would be really hard actually, but i can tell you our logic and the methods we are using :
Future initCamera(CameraDescription cameraDescription) async {
    print('camera list :$cameras');
    print('camera description : $cameraDescription');

    _cameraController = CameraController(cameraDescription, ResolutionPreset.veryHigh);
    _cameraController!.initialize().then((value) async {

      _cameraOn = true;

      if(_cameraController != null) {

        // Improve performances for video recording on iOS only.
        // This loads the audio part faster
        _cameraController!.prepareForVideoRecording();

        _cameraController!
            .getMaxZoomLevel()
            .then((value) => _maxZoomLevel = value);

        _cameraController!
            .getMinExposureOffset()
            .then((value) => _minAvailableExposureOffset = value);

        _cameraController!
            .getMaxExposureOffset()
            .then((value) => _maxAvailableExposureOffset = value);

        _cameraController!
            .setZoomLevel(_cameraZoomLevel);

        _cameraController!
            .setFlashMode(_flashEnable ? FlashMode.always : FlashMode.off);

        _cameraController!
            .setExposureOffset(_currentExposureOffset.value);

        await _cameraController!
            .lockCaptureOrientation(DeviceOrientation.portraitUp);

        // Used in dispose method(), allow the dispose when the initialization is ready
        isInit = true;
        // If the dispose was called before the init = true, in dispose() askForDispose is set to true
        // then we re call the dispose because it was asked at the end of initialize to avoid errors
        if(askForDispose) {
          askForDispose = false;
          disposeCamera();
        }

        notifyListeners();
      }
    });
  }

We have a specific UI that requires the camera to be shut down (to avoid too high memory usage and battery consumption) when we change pages and reopen.
The animations when changing pages are sometimes quicker than the initialize() / dispose() methods of the CameraController, so we did this logic (with the askForDispose etc...) to prevent bugs when calling .setFlashMode or .setExposureOffset that were ending on a disposed controller.
This logic may sound weird but not sure this related and it fixes all the different kind of errors we had because of the different Futures.
We are also using startVideoRecording(), takePicture(), _cameraController!.setFocusPoint(points);, _cameraController!.setZoomLevel(_cameraZoomLevel); but i can't tell if this crash happened during one of these calls sorry...

Labeling for further investigation

Hi @Tom3652, can i ask why do you think this is related to dispose? I recently fixed a race condition crash related to dispose, which is a different crash, but could be related.

Hello @hellohuanlin, i think it is related to dispose because we had issues before because of some race condition as you said.
I explain myself :

We have an animation that follows the finger of the user
If the user drags a specific widget revealed at 80% in the screen, the camera is disposed
If the user drags back this same widget revealed at 10%, the camera is initialized

Now this was causing issues when dragging fast because as you see in the above code, all of the methods on the cameraController are Futures and the camera was sometimes disposed before the setFlashMode was ending for example.
We had errors like setFlashMode called on a disposed cameraController and / or null object (because we were setting it to null to release memory.
To prevent this, we have made this bool : askForDispose that was handling the fact the camera was asked for disposed but it's useless to dispose it because the user dragged back fast enough.
Moreover, we also had the dispose method and the initialize respectively in AppLifecycleState.inactive and AppLifecycleState.resumed with the same logic.
I have taken a look at your PR and indeed it can be related.
I say this because (on iOS), it might be linked when the user plays around with the bottom navigation bar (to swipe up and dismiss the current app on iPhone X - XS - 11 and all the above). And doing so fast enough might lead to this crash.
However i must say that it's very hard to reproduce, i have tried to make a reproductible sample code and spamming the dispose / initialize but i could not make it crash by simply doing this with a button. Some circumstances must be reunited i guess and if it's actually the problem...

Non-camera report at https://github.com/flutter/flutter/issues/95568.


pull request for e2e test at 01/22/2017 12:56:18

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Python interface for loading

Previously, I recall that we had methods like get_trainer and get_model to go along with train.get_trainer_from_argparse_args and train.get_model_from_argparse_args.
These seem to have disappeared. What is the rationale behind that? Was this a mistake?

I sort of put them in there anticipating having tests in place not long after, but never got around to finishing the testing, and the interfaces kept changing in the meantime. I think I should complete #91 and we should complete #60 in general before we are ready to freeze this interface.

Cool! So

before we are ready to freeze this interface.

The interface being the exact argument names? And then we would just add the other method, which would share that interface?

By interface I mean the helper functions to create the pieces you need for training. Maybe something like:
def get_datamodule(...): ...

def get_model(...): ...

def get_trainer(...): ...

You want different flavors of these in train and predict modules.
Alternatively we could have a sort of "god class" that wraps the trainer object.

Ahhh got. Makes sense.

Alternatively we could have a sort of "god class" that wraps the trainer object.

And this class would have the helpers as method?

Alternatively we could have a sort of "god class" that wraps the trainer object.

And this class would have the helpers as method?

That's what I had in mind. Though I am not sure if that's a good idea vs. the interface I outlined above.

Yeah it seems clean, but then, I would also want to advocate for exposing the PTL trainer as much as possible (not totally sure whether either suggestion is better than the other to this end).

Arguably we have a reasonably stable API for this as of #110. Do you have particular suggestions for what else is needed?

Going to close this---I think we have a reasonably good interface now. Feel free to reopen with specific requests.


jakttest: Make Jakttest not poll for processes

Instead of polling for every running test and spinning, we call
sigwait() when we don't have anything to run, so that Jakttest's process
is suspended until any child exits (SIGCHLD). When it wakes up it does
generic polls with waitpid(-1, ...) to process all the tests that
finished executing and mark their directories as freed, launch more test
processes and go back to sleep.
This way we avoid spinning which gets in the way of the N jobs running
clang++ that are compiling the generated C++ from running the tests.
On my system (i7-8550U, 4 physical cores, 8 processing units) this shaved around
10 seconds, which means Jakttest was previously getting in the way a LOT.
cc @alimpfard @ADKaster

Apart from resolving the merge conflict, the scheduler should temporarily sigignore(SIGCHLD) while it's processing the finished tests' results, because that checking method is not signal safe.

thinking about the above, it doesn't matter if it ignores SIGCHLD or not when processing the finished tests' results; since the signal handler that we set ([](int){}) will exit and return back to what was being done before the signal was received.

While merging I've caught a bug in codegen: Turns out that it doesn't get that continue is not allowed inside a function,  for some reason.


Implement dia_matrix

I implemented dia_matrix, that is diagonal format. dia_matrix is required for some creation methods such as eye and diags.
related to #36

I fixed it.


Revise deployment structure

Deployments for this project fail frequently.  Revise logic and allocations to accommodate more resources at startup.  Probes can likely be improved as well.

No longer necessary.


Interactive examples arn't updated on the documentation page

I was reading the docs for an example using xarray and I found

https://hvplot.holoviz.org/user_guide/Gridded_Data.html#n-d-plots
https://tutorial.xarray.dev/intermediate/hvplot.html#animations

On both pages the examples with a slider or other interactive widgets don't update.

Therefor I was running the example with the latest versions of all needed packages on my local machine. The initial plot is created but I also get an error message.
Technical details
#### software version info
Python version        :  3.11.8 | packaged by conda-forge | (main, Feb 16 2024, 20:40:50) [MSC v.1937 64 bit (AMD64)]
IPython version       :  8.22.2
Tornado version      :  6.4
Holoviews version   :  1.18.3
HVPlot version        :  0.10.0
Pandas version        :  2.1.0
Panel version          :  1.4.4
XArray version        :   2024.5.0
Bokeh version         :  3.4.1
BokehJS static path   :  C:\Users\Moritz\anaconda3\envs\bkdev\Lib\site-packages\bokeh\server\static
node.js version       :  v20.9.0
npm version           :  10.5.0
jupyter_bokeh version :  (not installed)
Operating system      :  Windows-10-10.0.19045-SP0

minimal example
import cartopy.crs as ccrs
import hvplot.xarray
import xarray as xr

ds = xr.tutorial.open_dataset("air_temperature.nc")
# set constant colorbar limits
ds.air.hvplot(
    groupby="time",  # adds a widget for time
    clim=(250, 295),  # sets colormap limits
    widget_type="scrubber",
    widget_location="bottom",
)

Stack traceback
Traceback (most recent call last):
  File "C:\Users\Moritz\anaconda3\envs\bkdev\Lib\site-packages\pyviz_comms\__init__.py", line 340, in _handle_msg
    self._on_msg(msg)
  File "C:\Users\Moritz\anaconda3\envs\bkdev\Lib\site-packages\panel\viewable.py", line 469, in _on_msg
    patch = manager.assemble(msg)
            ^^^^^^^^^^^^^^^^^^^^^
  File "C:\Users\Moritz\anaconda3\envs\bkdev\Lib\site-packages\panel\models\comm_manager.py", line 29, in assemble
    msg_obj = cls(header, msg['metadata'], msg['content'])
                                           ~~~^^^^^^^^^^^
KeyError: 'content'

Screenshots or screencasts of the bug in action

I found a working configuration:
Python version        :  3.11.8 | packaged by conda-forge | (main, Feb 16 2024, 20:40:50) [MSC v.1937 64 bit (AMD64)]
IPython version       :  8.22.2
Tornado version       :  6.4
Bokeh version         :  3.4.2
BokehJS static path   :  C:\Users\Moritz\anaconda3\envs\bkdev\Lib\site-packages\bokeh\server\static
node.js version       :  v20.9.0
npm version           :  10.5.0
holoviews version     :  18.3
jupyter_bokeh version :  4.0.5
panel version         :  1.4.4
Operating system      :  Windows-10-10.0.19045-SP0


Simulation Support

As part of Crazyswarm2, we want a new improved simulation support.
Goals
We would like the following features

Operates as a backend, i.e., can be used with C++ and Python nodes (unlike Crazyswarm1, which only supported the high-level Python API)
Supports multiple backends, including ones with a physics engine (unlike Crazyswarm1, which only supported visualization)
Uses the Crazyflie firmware as software-in-the loop (SIL) (similar to Crazyswarm1)
Can be used for heterogeneous simulation, e.g., UAVs and ground robots (with some backends; unlike Crazyswarm1, which did not have such support)

As simulation backends we are considering:

A pure visualization (e.g., Rviz, meshcat, or matplotlib)
WeBots, see also #106 and #77
Our custom simulator (currently at https://github.com/IMRCLab/pyCrazyflie)
Gazebo
CoppeliaSim

Usage (user-perspective)
From a user-perspective, the simulator should be usable using (or similar)
ros2 launch crazyflie launch.py backend:=sim sim:=webots

which will either connect or launch to the existing simulator, spawn the Crazyflies at the specified initial positions in the launch file, and react to ROS topics/services as similar as possible as when using the physical backend.
Design

The simulator will be written in Python and uses the crazyflie-firmware Python bindings to support SIL.
The interface of the simulator is the same as with the other backends, i.e., it provides high-level services (such as takeoff) for individual drones and all drones, as well as low-level topics (such as cmd_vel).
To support multiple simulator backends, the simulator will just map between the ROS interface and desired states (for visualization) and motor forces (for physics-based simulation). Each simulation backend will need to be able to provide:

a function to initialize a UAV at a given state/position. Input: state, Output: UAV-ID
a stepUAV RPC (can be a Python call, ROS service, or another RPC approach). Input: UAV-ID, desired states, motor forces, Output: new state (or some error if the drone crashed). Note that the new state is not strictly needed, but might allow us to have standardized logging tools across backends.
a stepTime RPC, to advance simulation time. Input: dt

Open Issues
We need to understand the way simulation time works in ROS2. One resource is https://design.ros2.org/articles/clock_and_time.html.

Adding @knmcguire and @Khaledwahba1994 to comment on this proposal.

The basic infrastructure with visualization backend has been merged. The next step is to enable controllers from the Python bindings to support physics-based backends.


Add Coder for custom ActiveRecord serialization

Add support for a custom coder strategy for encoding ActiveRecord attributes. This lets you apply units to a numeric column like so:
class Package < ActiveRecord::Base
  serialize :weight, Quantified::Mass.kilograms
end

Package.create!(weight: 1.pounds).weight
=> #<Quantified::Mass: 0.45359237 kilograms>

This looks good. One question. Then I can merge and bump for you @alethea

I'll change that is_a? to a responds_to? and push that up tonight.

Sure thing. And if you can make sure the test coverage hits both branches of the responds_to? check.

And thank you!

Done, thank you!

Released in 1.1.0

Thanks for your contribution @alethea

You're welcome


Add support for workspace/workspaceFolders request

Newer versions of pylance make a 'workspace/workspaceFolders' request when workspaces change. This allows for the detection of renames.
However PTVS wasn't handling this request, which causes Pylance to skip all workspaces and make it behave like it was in single file mode.

by the way, does PTVS support multi workspaces?

by the way, does PTVS support multi workspaces?

Yeah, when you open a solution. You should see that in the OnSolutionOpened changes.

Did you run any tests to verify this fixed the issue?

I tested it manually if that's what you're asking. I don't believe there are any automated tests.

once you merge I will make sure it gets inserted into the VS main.


location-mockup page

fixed spacing for the entire page and add grid layout
changed drop down menu and items style
redesigned UI for mobile view

Your review app has been deployed and is available at 'http://<IP_ADDRESS>:80'.Learn More about how to test and provide feedback for the app.

Your review app has been deployed and is available at 'http://<IP_ADDRESS>:80'.Learn More about how to test and provide feedback for the app.

Your review app has been deployed and is available at 'http://<IP_ADDRESS>:80'.Learn More about how to test and provide feedback for the app.

Your review app has been deployed and is available at 'http://<IP_ADDRESS>:80'.Learn More about how to test and provide feedback for the app.


add jspm to "using babel" page under build systems

@codylindley thanks for driving this! I'm wondering if jspm installation instructions should be included here at all? Perhaps rather the usage instructions you have of jspm dl-loader --babel and jspm init and select babel are the "babel install" instructions for jspm only?
Then instead of spelling out the full configuration jspm adds for Babel, just mention something along the lines of that by default jspm will add configuration to use the Babel runtime transformer for modular runtime loading but this can be disabled or other configuration options can be added as well here.

@guybedford - Please change it as you see fit. I'll follow your lead and @sebmck lead.

Closed in favor of #283. Thanks @codylindley!


Introduce distinct search for beta.consumerfinance.gov

This PR modifies the behavior of the website when deployed to beta.consumerfinance.gov, so that global site searches use beta-specific search indexes. Recall that our global site search currently uses Search.gov and has two indexes: cfpb for regular English-language pages and cfpb_es for Spanish-language pages.
This change modifies how the website works on beta such that it uses cfpb_beta and cfpb_beta_es. This is reflected two ways: first, the header search now queries Search.gov with those affiliate codes; and second, the Search.gov JavaScript snippet now uses these codes as well. Under the hood this behavior relies on our existing DEPLOY_ENVIRONMENT Django setting.
In order to support search on beta, this PR also modifies how we serve our robots.txt file. Currently, robots.txt is a hardcoded text file which allows all robots and disallows certain paths. We currently override robots.txt on beta as part of our (internal) deploy code. With this PR, robots.txt is now served by Django instead, and uses a new ROBOTS_TXT_SEARCH_GOV_ONLY feature flag in order to serve different robots directives on beta. Specifically, on beta we will now attempt to block all robots except the Search.gov one, based on its usasearch user agent.
Finally, a minor bit of cleanup included here is removal of the show_banner parameter to our global header; this is never used and has been superseded by alternate banner code.
How to test this PR
To test, you can run a local server and verify that searches on http://localhost:8000/ and http://localhost:8000/es/ work as expected (look at the affiliate=cfpb part of the search query string when you submit the form), and that the included JS snippet has the right code (look in source for usasearch_config).
Then, try running a local server but set the DEPLOY_ENVIRONMENT environment variable to beta, and confirm that the Search.gov codes update as expected.
Notes and todos

This change requires removing the code in our internal deployment repo that overwrites robots.txt on beta; I will open a separate PR for that purpose. Edit: a-c-f#394
We could use some documentation of how we use Search.gov.

Checklist

[x] PR has an informative and human-readable title
[x] Changes are limited to a single goal (no scope creep)
[x] Code follows the standards laid out in the CFPB development guidelines
[x] Future todos are captured in comments and/or tickets
[ ] Project documentation has been updated, potentially one or more of:

This repo’s docs (edit the files in the /docs folder) – for basic, close-to-the-code docs on working with this repo
CFGOV/platform wiki on GHE – for internal CFPB developer guidance
CFPB/hubcap wiki on GHE – for internal CFPB design and content guidance

TIL: How to concatenate strings in jinja2 with ~


Fixes jobStore "clean" method for service jobs (Resolves #908).

Aside from the file store tests failing, all the other tests passed. Will merge in a few hours..

s/Resolves/resolves in commit title

And no period at the end of commit title, please.

Otherwise +1 from me.

Okay, thanks. Will merge this one as do not see as critical to fix, but will get style right next time.


Change the description on the readme so that it is clear the bot is general purpose

The description on the README.md would have someone believe the bot is only intended for the UFCC discord and not general purpose. I'm proposing we change the wording so that it instead says something like "in use on UFCC discord" instead "for UFCC's discord". Maybe even state specifically that it is general purpose.

I can look into this. I can change up the wording so it makes it clear that it is general purpose and could be used for any chat room, and it is use on the FCC chat in specific.

Fixed up everything in the pull request so I closed it


update memory monitor

What does this PR do?
Updates memory monitor to use GB, which is much more readable. Also fixes it to track current allocated memory instead of cumulative (which isn't really useful)
What issue(s) does this change relate to?
CO-1740

Could we post an example of the new output before we're ready to merge this PR in the description?

	 Train trainer/global_step: 95
	 Train trainer/batch_idx: 95
	 Train memory/allocated_mem: 22.9840
	 Train memory/active_mem: 22.9840
	 Train memory/inactive_mem: 5.3172
	 Train memory/reserved_mem: 38.9250
	 Train memory/alloc_retries: 0
	 Train trainer/device_train_microbatch_size: 10
	 Train loss/train/total: 0.1528
	 Train wall_clock/train: 627.0995
	 Train wall_clock/val: 0.0000
	 Train wall_clock/total: 627.0995```


Layer skip

rn this is actually just fixing outstanding issues with the shells and adding tests

Keeping around as future work, but not relevant of itself


When will TADAM's code be released?

Thanks for your interesting work, but when will TADAM's code be released?

Thanks for your interesting work, but when will TADAM's code be released?

Soon, before the conference begins. Thanks for your patience!


lit component

    lit component

// t-button
@customElement('t-button')
...
return html`<button ?disabled=${this.disabled} @click=${console.log('button')}>
  <solt>
  </solt>
</button>`
...

use in html
<t-button disabled onClick="console.log('t-button')">button</t-button>

it also log:'t-button',how can forbidden by add a <slot></slot>
Originally posted by @marsDes in https://github.com/lit/lit/discussions/3734

What's the question here?

like this
// t-button
@customElement('t-button')
...
return html`<button ?disabled=${this.disabled} @click=${console.log('button')}>button</button>`
...

use
<t-button disabled onClick="console.log('t-button')">button</t-button>

when set disabled, nothing happed

Can you make a reproduction of what you're trying to do on https://lit.dev/playground ?

@marsDes we need more info if we're going to be able to help
I suspect that you might need to use type: Boolean in your definition of disabled. Like:
@customElement('t-button')
class TButton extends LitElement {
  @property({type: Boolean, reflect: true})
  disabled = false;
}

i think it is related to this https://stackoverflow.com/questions/32745276/explicitly-set-disabled-false-in-the-html-does-not-work

If this is still an issue, please re-open. We will need a clear question and hopefully a reproduction.


fix(firehose) double resources when using external name

Description of your changes

Fixes #1890  but for firehose.
I have:

[x] Read and followed Crossplane's contribution process.
[x] Run make reviewable test to ensure this PR is ready for review.

How has this code been tested
Tested locally

For the record: This actually contains the implementation for Firehose that was supposed to bemerged with #1885 but for due to some mistake was not merged (only minor refactorings got merged appearently).
@nilde could you squash all changes into a single commit and sign them? Please also make sure that the commit message follows the conventional commits standard. Since you are actually adding a feature here it might make sense to change it into something like feat(firehose): Add DevileryStream controller. I think you also need to rebase your changes on the latest master, as some refactoring has happened in the mean time.


New format in version 2.8.1 does not support loading from YAML files formatted from versions <2.8

Prior to version 2.8, the GPSTime class had attributes week_number and time_of_week. If stored in a YAML file, this would be stored as:
!!python/object:gps_time.core.GPSTime
    time_of_week: 23234.2
    week_number: 213

In version 2.8.1, the GPSTime class was changes to have attributes of week_number, seconds, and femtoseconds with time_of_week becoming a property with a setter to ensure existing code still works. However, if a GPSTime object is created using a YAML file for an older version of this library, it will not be instantiated properly and will lack the seconds and femtoseconds attributes.

Fixed on #3


MirrorsUsed cannot merge symbols

Given a library which imports dart:mirrors with:
library a;
@MirrorsUsed(symbols: ['foo'])
import 'dart:mirrors';
Then another import which attempts to modify the first with:
@MirrorsUsed(symbols: const ['bar'], override: 'a')
import 'dart:mirrors';
The dart2js compiler fails with:
Internal error: Unsupported operation: Cannot add to a non-extendable array
0      List.addAll (dart:core-patch/array.dart:230)
1      MirrorUsageAnalyzer.merge (file:///mnt/data/b/build/slave/dart-editor-linux-stable/build/dart/sdk/lib/_internal/compiler/implementation/mirrors_used.dart:311)
2      MirrorUsageAnalyzer.mergeUsages (file:///mnt/data/b/build/slave/dart-editor-linux-stable/build/dart/sdk/lib/_internal/compiler/implementation/mirrors_used.dart:289)

Mirrors is no longer supported in Dart2JS.