How do I manage wd* parameters in a WOPI host page?

The documentation says that "Office Online will sometimes pass additional query string parameters to your host page." It is not clear when or why this may happen. Is it only on page load or can these parameters be added dynamically?
The documentation also says "When you receive these query string parameters on your host page URLs, you must pass them, unchanged, to the Office Online iframe." It is not specified how these parameters are to be passed. Are they supposed to be added to the iFrame URL, sent in a form POST, using the HTML 5 Post method or something else?
A code sample or explanation would be brilliant!

On a side note, it would be fantastic to be able to pass wd* parameters like wdPageFit=2, etc... and have word react to those accordingly.


Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './jsx-runtime' is not defined by "exports" in package.json

Hey everyone!
I've just upgraded from 4.0.0 to 4.2.0 and now I'm getting the following error:
Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './jsx-runtime' is not defined by "exports" in /.../node_modules/jsx-slack/package.json
    at new NodeError (node:internal/errors:329:5)
    at throwExportsNotFound (node:internal/modules/esm/resolve:337:9)
    at packageExportsResolve (node:internal/modules/esm/resolve:562:3)
    at resolveExports (node:internal/modules/cjs/loader:473:36)
    at Function.Module._findPath (node:internal/modules/cjs/loader:513:31)
    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:910:27)
    at Function.Module._resolveFilename (/.../node_modules/module-alias/index.js:49:29)
    at Function.Module._load (node:internal/modules/cjs/loader:769:27)
    at Module.require (node:internal/modules/cjs/loader:996:19)
    at require (node:internal/modules/cjs/helpers:92:18)
    at Object.<anonymous> (/.../blocks.js:15:21)
    at Module._compile (node:internal/modules/cjs/loader:1092:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1121:10)
    at Module.load (node:internal/modules/cjs/loader:972:32)
    at Function.Module._load (node:internal/modules/cjs/loader:813:14)
    at Module.require (node:internal/modules/cjs/loader:996:19) {
  code: 'ERR_PACKAGE_PATH_NOT_EXPORTED'
}

Thanks a lot!

Thanks for feedback! It brings by lack of ES modules support for JSX runtime. I have delayed to work this because React is not supported ES modules officially, but should consider to support ES modules also in jsx-runtime.js.
I'll do it right away, but you can use v4.1.0 instead if you're in a hurry.

Fixed in the latest release v4.2.1. Please try upgrading again!

Awesome!! Works great!
Thanks a lot, @yhatt
I have experienced many similar issues due to the gradual switch to ES modules in open source JS. This will probably cause us many more headaches in the near future :D


Bug- Invocation error thrown when error encountered when parsing dates

error occurs in view commands.
eg. view-exam date/1 will not handle the error properly

Maybe can also show the user the correct format of the date input in the error message. The accepted formats are store in the file logic/commands/parser/ParserUtil.java


Support running superset via pex

to: @mistercrunch @bkyryliuk
Context
Pex is a packaging system and format for Python apps that combines the code for an app and its dependencies in a single file. This change includes some minor updates to superset to support running it via a pex. Everything should be backwards-compatible.
Content

Support running gunicorn without going through gunicorn command-line; this requires bypassing the cli.manager and having some wrapper code in superset/bin/superset so that the app forks cleanly in this case
Support loading a local config that isn't in the python path. In the pex case, the pythonpath is isolated and immutable, so this is the easiest way to bring in an external config.

LGTM

LGTM

@bkyryliuk @mistercrunch Refactored the runserver flow a bit as we discussed earlier today. In particular, both the debug and gunicorn cases are now handled consistently, so we won't have to deprecate anything in the future. Can you take another look? Thanks!

We've found other ways of pex-ing for gunicorn to address this problem (gunicorn forking the process while sqlalchemy is not fork-safe), we'll revert most of this PR as soon as the alternative solution is up.


Meteor version: <IP_ADDRESS>     No compatible binary build found for this package

C:\Users\Rocky\Documents\GitHub\meteor-dapp-cosmo\app [master]> meteor
[[[[[ C:\Users\Rocky\Documents\GitHub\meteor-dapp-cosmo\app ]]]]]
=> Started proxy.
=> Started MongoDB.
=> Errors prevented startup:
While checking for<EMAIL_ADDRESS>error: No compatible binary build found for this package. Contact the package author and ask them to publish it
for your platform.
=> Your application has errors. Waiting for file change.

Duplicate of #46. Sorry, currently abroad with limited access to Internet and will take care of this when I return.

Ah, fantastic. Thanks @mizzao .For someone like me just starting Meteor, it is great to have sweet libraries like yours, thanks! For reference here are the error messages that brought me here.
C:\Users\heyandy889\Documents\src\gamestart-ide>meteor
This project uses Meteor <IP_ADDRESS>, which isn't available on Windows. To
work with this app on all supported platforms, use
meteor update --release<EMAIL_ADDRESS>to pin this app to the newest
Windows-compatible release.

C:\Users\heyandy889\Documents\src\gamestart-ide>meteor update --release METEOR@1
.1.0.2
=> Errors while initializing project:

While checking for<EMAIL_ADDRESS>error: No compatible binary build found for this package. Contact the
package author and ask them to publish it for your platform.

Thanks again, enjoy the time abroad

Sincerely sorry for the delay on this - should be working with the newly bumped 0.7.4 release.

Thanks, will give it a spin!


chore: list v2 - execute action

Description
This PR aimed at enabling access for the use of currentItem currentIndex currentRow and level_* properties in the events.
While development, it was found that the functionality already works from the POC so the following changes were only made:

Removed the concept of dynamicPathMapList. While generating meta widgets, we are now looking into the paths that are only present in dynamicBindingPathList and dynamicTriggerPathList to decide which properties to include for evaluations (currentItem/currentRow etc).
Added cypress test to validate.
Removed overrideExecuteAction as there seems to be no requirement to override the executeAction of the child widgets.

Fixes #17386
Note to QA:
This PR deals with the access and usage of the internal properties in the Events on any widget present inside the List widget.
Media
https://www.loom.com/share/2efa8877448f4dba9ff772c93ef4b087
Type of change

Please delete options that are not relevant.

New feature (non-breaking change which adds functionality)

How Has This Been Tested?

Cypress

Test Plan

Add Testsmith test cases links that relate to this PR

Issues raised during DP testing

Link issues raised during DP testing for better visiblity and tracking (copy link from comments dropped on this PR)

Checklist:
Dev activity

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[ ] PR is being merged under a feature flag

QA activity:

[ ] Test plan has been approved by relevant developers
[ ] Test plan has been peer reviewed by QA
[ ] Cypress test cases have been added and approved by either SDET or manual QA
[ ] Organized project review call with relevant stakeholders after Round 1/2 of QA
[ ] Added Test Plan Approved label after reveiwing all Cypress test

@Tooluloope Yeah, once the designs come in, we will take infinite scrolling also into consideration.


Fix sorting issue affecting user endpoints

Fixes issue https://github.com/Instagram/instagram-ruby-gem/issues/175

Signed up! :)

Any update on this PR? Can it be merged? 1.1.5 is broken w/o it

Any update on this? 1.1.6 and 1.1.5 were released without this issue being fixed.

Encountered the same issue. 👍
Why this is not yet pushed? @heatonjb

IG doesn't care about this gem anymore.
I have my own fork we've been using in prod for about a year now
https://github.com/bobber205/instagram-ruby-gem


Few issues with messenger

The type message bar is still light
The settings and writing cog in top left should be white
The name on right should really be white/grey, blue looks a little awkward.

These issues come with the new update from Facebook. I will fix today.

The name on right should really be white/grey, blue looks a little awkward.

Where is this? I did not notice about this one.

@CptDinosaur all issues got fixed.


[BIOMAGE-1027] Add safeBatchGetItem

Background
Link to issue
https://biomage.atlassian.net/browse/BIOMAGE-1027
Link to staging deployment URL
https://ui-martinfosco-api138.scp-staging.biomage.net/
Links to any Pull Requests related to this
Anything else the reviewers should know about the changes here
Changes
Code changes
Definition of DONE
Your changes will be ready for merging after each of the steps below have been completed:
Testing

[ ] Unit tests written
[x] Tested locally with Inframock (with latest production data downloaded with biomage experiment pull)
[x] Deployed to staging

To set up easy local testing with inframock, follow the instructions here: https://github.com/biomage-ltd/inframock
To deploy to the staging environment, follow the instructions here: https://github.com/biomage-ltd/biomage-utils
Documentation updates
Is all relevant documentation updated to reflect the proposed changes in this PR?

[ ] Relevant Github READMEs updated
[ ] Relevant wiki pages created/updated

Approvers

[ ] Approved by a member of the core engineering team
[ ] (UX changes) Approved by vickymorrison (this is her username, tag her if you need approval)

Just before merging:

[ ] After the PR is approved, the unstage script in here: https://github.com/biomage-ltd/biomage-utils is executed. This script cleans up your deployment to staging

Optional

[ ] Photo of a cute animal attached to this PR

Unit tests pending.


Devise’s authenticate block breaks previews

Describe the bug
Am I the only one who gets undefined method 'authenticate!' for nil:NilClass when I use Devise’s authenticate block in routes like this: https://github.com/changepack/changepack/blob/5d27756550051dd6adafe52e8ecc83186bf12ea9/config/routes.rb#L9
To Reproduce
Steps to reproduce the behavior:

git clone git@github.com:changepack/changepack.git
Go to http://localhost:3000/lookbook
Click on the only available component
See below.

Expected behavior
I expect to see the component previewed. When I comment the authenticate block out, everything works perfectly.
Version numbers
Please complete the following information:

Lookbook: 2.0.0
ViewComponent: 3.0.0
Rails: 7.0.4
Ruby: 3.2.1

I got the exact same issue

@nicieja thanks for bringing this to my attention - I don't use Devise personally so I haven't run into this before, but I can replicate it with the repo you provided so just looking into it now. Will hopefully have a fix up soon 👍

Hey @nicieja @guillaumebriday-pa - I believe I have a fix for this now in PR #450.
It works for me in the changepack/changepack app now but it would be great to get confirmation if you have a chance to give it a try by bundling Lookbook from the devise-preview-fix branch.
It is a bit of a hack to be honest - the issue you are seeing is actually being caused by a workaround for another bug. But if this works for now then I'll ship it for now and hopefully spend a bit of time on unpicking the actual root cause of the problem when I have a little more time.
I'm going to go a little more testing but once I'm happy (and unless I hear back that it is still causing issues for either of you) I'll merge it in and get it out in the next release (which will be v1.0.1).

(@nicieja as an aside, Changepack looks very interesting! I'm keen to dig in a bit more when I get a chance 😊)

The fix actually works for me as well!
Thank you for your reactivity! 🙏

Awesome 🙏 , can you release the 2.0.1?

@guillaumebriday-pa @nicieja 2.0.1 is now out that includes the fix for this. Thanks for your help!

@allmarkedup Didn’t look at GitHub yesterday but I can confirm that the fix works for me too. Thanks!

(as an aside, Changepack looks very interesting! I'm keen to dig in a bit more when I get a chance 😊)

🙏 Glad you like it!


Fix getter error messages

Seems like copy-and-paste errors for a couple of the getter properties.
Fixed to use the correct names

Thank you for the contribution!
Actually, in the newer version of Anko this bug was fixed.


Problem plugins

https://github.com/webed-themes/sedna#how-to-use
After the action template demo data problems begin with the activation, deactivation and installing plug-ins.
I get this error ..
Some error occurred. View console log for more information.

Hello,
It's because of the sample data. I've updated the sample data, you can try it.

php artisan vendor:publish --tag=webed-public-assets
PHP Fatal error:  Class 'Laravel\Tinker\TinkerServiceProvider' not found in /......../ptznew.ru/vendor/laravel/framework/src/Illuminate/Foundation/ProviderRepository.php on line 146
[Symfony\Component\Debug\Exception\FatalErrorException]
Class 'Laravel\Tinker\TinkerServiceProvider' not found
I do as it is written here: https://github.com/webed-themes/sedna#how-to-use

This problem was solved ....
After editing the home page menu does not work and disturbed the whole entire work site :(
Here's a look please  http://ptznew.ru
It is possible that once set the whole project together with all plugins and design theme .... without the "dancing with a tambourine"?
really liked the system, but quite difficult to configure all of the different sections ....
Thank.

It's because of the Laravel Tinker package in Laravel 5.4. You can go through to config/app.php and command the line Laravel\Tinker\TinkerServiceProvider::class,,
or you can try to run composer require laravel/tinker:~1.0
Btw, i've updated the composer.json.

Yeah, I'm building a system to manage the packages. You can download the package from the dashboard.

Well, this problem is also solved or will be solved .... :)
Now, when editing the page does not display blocks of content ... although previously displayed ... Now only this:

I'll try later to install all over again

This theme is made for WebEd version 2. I changed some fields in backend.
With this case, you can go to Custom Fields and edit all the field groups. Set the Page template rule to HomePage
Or try to download the latest db I've pushed.

Ok, Thank.

Everything is ok now?

No :(
Whoops, looks like something went wrong.
2/2
ErrorException in 198823d5fa7d130c608a5f993d457b59ad6a350c.php line 110:
Invalid argument supplied for foreach() (View: /....../ptznew.ru/themes/sedna/resources/views/front/page-templates/homepage.blade.php)
What I edited it wrong :)

The cache is cleared to no avail

My email is<EMAIL_ADDRESS> Could you send me the dashboard credentials?

This is a test site, please:
admin
123456

lol
You deleted the custom fields in the field group: Homepage CMS blocks - Blog intro.

And what not? Maybe add a field again?

Using custom fields is very convenient, but very dangerous too.

Well ... I reinstalled

Install the plugin blog ... Now when you try to view the recording issue is:
Class WebEd\Themes\Sedna\Http\Controllers\Blog\PostController not exists
Please excuse me if tired :)

Sorry, that theme doesn't support blog.
I will make a blank theme soon.
Or you can try to create a new one by run command: php artisan theme:create your-theme-alias

Well, I will follow the development of your project. You can close issue. Thank you very much.


StreamBuilder rebuilds with old Stream data when changing Streams

Currently, after the first data from a stream is processed by StreamBuilder, StreamBuilder will only ever use actual stream data in its builder function.
This is a problem when we pass a new and unique different stream to the same StreamBuilder widget after it has been used for a bit.
When you pass a new Stream to a StreamBuilder after a first Stream has already been processed and built by it, due to didUpdateWidget the StreamBuilder will be built again and the builder function will execute.
However, the data passed to the builder function is from the old stream and does not reflect the fact that the stream being managed by the StreamBuilder has changed.
Obviously it's not possible to take the most recent value automatically from the stream to pass to the builder, however in this situation I feel that it is more correct the use the initialData until StreamBuilder can get a first value from the Stream itself.
It would be up to the user then to change the initialData along with the stream being passed in to the StreamBuilder, but that makes sense since that is what you have to do anyways when building the StreamBuilder for the first time.
I've included sample code below explaining the problem.
There is text showing the current information for the current build, along with two buttons.
One to add new data to the current stream, and one to switch the stream to a different one (back and forth).
Notice how when you push the switch streams button, a build occurs, but the data shown is still the old data from the old (possibly closed) stream.
import 'package:flutter/material.dart';
import 'dart:async';

final Color darkBlue = Color.fromARGB(255, 18, 32, 47);

void main() {
  runApp(MyApp());
}

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      theme: ThemeData.dark().copyWith(scaffoldBackgroundColor: darkBlue),
      debugShowCheckedModeBanner: false,
      home: Scaffold(
        body: SafeArea(
          child: Center(
            child: StreamSwitcher(),
          ),
        ),
      ),
    );
  }
}

class StreamSwitcher extends StatefulWidget {
  @override
  _StreamSwitcherState createState() => _StreamSwitcherState();
}

class _StreamSwitcherState extends State<StreamSwitcher> {
  StreamController<String> _controller1;
  StreamController<String> _controller2;
  StreamController<String> _currentController;

  int _controller1Value = 0;
  int _controller2Value = 0;
  int _buildCount = 0;

  @override
  void initState() {
    super.initState();
    _controller1 = StreamController.broadcast();
    _controller2 = StreamController.broadcast();
    _currentController = _controller1;
  }

  @override
  void dispose() {
    _controller1.close();
    _controller2.close();
    super.dispose();
  }

  @override
  Widget build(BuildContext context) {
    return Column(
      children: [
        StreamBuilder<String>(
          initialData:
              _currentController == _controller1 ? 'Initial 1' : 'Initial 2',
          stream: _currentController.stream,
          builder: (context, snapshot) {
            if (snapshot.hasData) {
              return Text('BuildCount:${++_buildCount}:${snapshot.data}');
            } else {
              return Text('BuildCount:${++_buildCount}:No data');
            }
          },
        ),
        MaterialButton(
            child: const Text('Push To Stream'),
            onPressed: () {
              _currentController.add(_currentController == _controller1
                  ? 'Stream1:${++_controller1Value}'
                  : 'Stream2:${++_controller2Value}');
            }),
        MaterialButton(
            child: const Text('Switch Streams'),
            onPressed: () {
              setState(() {
                _currentController = _currentController == _controller1
                    ? _controller2
                    : _controller1;
              });
            }),
      ],
    );
  }
}

flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, v1.17.2, on Mac OS X 10.15.6 19G2021, locale en-CA)
[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
[✓] Xcode - develop for iOS and macOS (Xcode 11.2.1)
[✓] Android Studio (version 4.0)
[✓] VS Code (version 1.48.1)
[✓] Connected device (1 available)

flutter doctor -v
[✓] Flutter (Channel stable, 1.20.2, on Mac OS X 10.15.6 19G2021, locale en-GB)
    • Flutter version 1.20.2 at /Users/tahatesser/Code/flutter_stable
    • Framework revision bbfbf1770c (3 weeks ago), 2020-08-13 08:33:09 -0700
    • Engine revision 9d5b21729f
    • Dart version 2.9.1

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

[✓] Xcode - develop for iOS and macOS (Xcode 11.6)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.6, Build version 11E708
    • CocoaPods version 1.9.3

[✓] Android Studio (version 4.0)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 48.1.2
    • Dart plugin version 193.7547
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6222593)

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

[✓] Connected device (2 available)
    • Taha’s iPhone (mobile) • 00008020-001059882212002E            • ios • iOS
      13.6.1
    • iPhone 11 (mobile)     • A63D6F51-59F3-4A75-961F-3769709F3A92 • ios •
      com.apple.CoreSimulator.SimRuntime.iOS-13-6 (simulator)

• No issues found!

flutter doctor -v
[✓] Flutter (Channel master, 1.22.0-2.0.pre.139, on Mac OS X 10.15.6 19G2021,
    locale en-GB)
    • Flutter version 1.22.0-2.0.pre.139 at
      /Users/tahatesser/Code/flutter_master
    • Framework revision c0ea00ed3f (7 hours ago), 2020-08-30 22:20:16 -0700
    • Engine revision bada9fc5f3
    • Dart version 2.10.0 (build 2.10.0-76.0.dev)

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

[✓] Xcode - develop for iOS and macOS (Xcode 11.6)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.6, Build version 11E708
    • CocoaPods version 1.9.3

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

[✓] Android Studio (version 4.0)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 48.1.2
    • Dart plugin version 193.7547
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6222593)

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

[✓] Connected device (5 available)
    • Taha’s iPhone (mobile) • 00008020-001059882212002E            • ios
      • iOS 13.6.1
    • iPhone 11 (mobile)     • A63D6F51-59F3-4A75-961F-3769709F3A92 • ios
      • com.apple.CoreSimulator.SimRuntime.iOS-13-6 (simulator)
    • macOS (desktop)        • macos                                • darwin-x64
      • Mac OS X 10.15.6 19G2021
    • Web Server (web)       • web-server                           •
      web-javascript • Flutter Tools
    • Chrome (web)           • chrome                               •
      web-javascript • Google Chrome 84.0.4147.135

• No issues found!

What is the cause of this problem?

I encountered this as well and was surprising.
I expected that the StreamBuilder will handle if the stream object is changed but seems to not.
My workaround is to use a different key when the stream changed.

I am facing the same issue. Is there any solution to fix this?

I am facing the same issue. Is there any solution to fix this?

I'm using BehaviorSubject from RxDart. It emits last value as soon as you subscribe to it. So in the described scenario - as soon as the builder subscribed to a new Stream, it will receive the last emitted value from the stream and build UI with most recent data

This issue bit me as well, this makes the use of the snapshot impossible inside of the builder function if the stream changes.

Any update on this?

Verified this issue by running the originally reported behavior and updated code sample and observed the same behavior.

 stable, master flutter doctor -v
[!] Flutter (Channel stable, 3.7.7, on macOS 12.2.1 21D62 darwin-x64, locale
    en-GB)
    • Flutter version 3.7.7 on channel stable at
      /Users/dhs/documents/fluttersdk/flutter
    ! Warning: `flutter` on your path resolves to
      /Users/dhs/Documents/Fluttersdk/flutter/bin/flutter, which is not inside
      your current Flutter SDK checkout at
      /Users/dhs/documents/fluttersdk/flutter. Consider adding
      /Users/dhs/documents/fluttersdk/flutter/bin to the front of your path.
    ! Warning: `dart` on your path resolves to
      /Users/dhs/Documents/Fluttersdk/flutter/bin/dart, which is not inside your
      current Flutter SDK checkout at /Users/dhs/documents/fluttersdk/flutter.
      Consider adding /Users/dhs/documents/fluttersdk/flutter/bin to the front
      of your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 2ad6cd72c0 (12 days ago), 2023-03-08 09:41:59 -0800
    • Engine revision 1837b5be5f
    • Dart version 2.19.4
    • DevTools version 2.20.1
    • If those were intentional, you can disregard the above warnings; however
      it is recommended to use "git" directly to perform update checks and
      upgrades.

[!] Xcode - develop for iOS and macOS (Xcode 12.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    ! Flutter recommends a minimum Xcode version of 13.
      Download the latest version or update via the Mac App Store.
    • CocoaPods version 1.11.2

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

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

[✓] Connected device (5 available)
    • SM G975F (mobile)       • RZ8M802WY0X • android-arm64   • Android 11 (API 30)
    • Darshan's iphone (mobile)  • 21150b119064aecc249dfcfe05e259197461ce23 •
      ios            • iOS 14.4.1 18D61
    • iPhone 12 Pro Max (mobile) • A5473606-0213-4FD8-BA16-553433949729     •
      ios            • com.apple.CoreSimulator.SimRuntime.iOS-14-3 (simulator)
    • macOS (desktop)            • macos                                    •
      darwin-x64     • Mac OS X 10.15.4 19E2269 darwin-x64
    • Chrome (web)               • chrome                                   •
      web-javascript • Google Chrome 98.0.4758.80

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 1 category.

[!] Flutter (Channel master, 3.9.0-12.0.pre.18, on macOS 12.2.1 21D62
    darwin-x64, locale en-GB)
    • Flutter version 3.9.0-12.0.pre.18 on channel master at
      /Users/dhs/documents/fluttersdk/flutter
    ! Warning: `flutter` on your path resolves to
      /Users/dhs/Documents/Fluttersdk/flutter/bin/flutter, which is not inside
      your current Flutter SDK checkout at
      /Users/dhs/documents/fluttersdk/flutter. Consider adding
      /Users/dhs/documents/fluttersdk/flutter/bin to the front of your path.
    ! Warning: `dart` on your path resolves to
      /Users/dhs/Documents/Fluttersdk/flutter/bin/dart, which is not inside your
      current Flutter SDK checkout at /Users/dhs/documents/fluttersdk/flutter.
      Consider adding /Users/dhs/documents/fluttersdk/flutter/bin to the front
      of your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 28f17d345b (39 minutes ago), 2023-03-20 21:08:41 -0700
    • Engine revision ea6ed14b4e
    • Dart version 3.0.0 (build 3.0.0-345.0.dev)
    • DevTools version 2.22.2
    • If those were intentional, you can disregard the above warnings; however
      it is recommended to use "git" directly to perform update checks and
      upgrades.

[!] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /Users/dhs/Library/Android/sdk
    ✗ cmdline-tools component is missing
      Run `path/to/sdkmanager --install "cmdline-tools;latest"`
      See https://developer.android.com/studio/command-line for more details.
    ✗ Android license status unknown.
      Run `flutter doctor --android-licenses` to accept the SDK licenses.
      See https://flutter.dev/docs/get-started/install/macos#android-setup for
      more details.

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

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

[✓] IntelliJ IDEA Ultimate Edition (version 2021.3.2)
    • IntelliJ at /Applications/IntelliJ IDEA.app
    • Flutter plugin version 65.1.4
    • Dart plugin version 213.7228

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

[✓] Connected device (3 available)
    • Darshan's iphone (mobile) • 21150b119064aecc249dfcfe05e259197461ce23 • ios
      • iOS 15.3.1 19D52
    • macOS (desktop)           • macos                                    •
      darwin-x64     • macOS 12.2.1 21D62 darwin-x64
    • Chrome (web)              • chrome                                   •
      web-javascript • Google Chrome 109.0.5414.119

[✓] Network resources
    • All expected network resources are available.

! Doctor found issues in 1 category.

[!] Xcode - develop for iOS and macOS (Xcode 12.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    ! Flutter recommends a minimum Xcode version of 13.
      Download the latest version or update via the Mac App Store.
    • CocoaPods version 1.11.2

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

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

[✓] Connected device (5 available)
    • SM G975F (mobile)       • RZ8M802WY0X • android-arm64   • Android 11 (API 30)
    • Darshan's iphone (mobile)  • 21150b119064aecc249dfcfe05e259197461ce23 •
      ios            • iOS 14.4.1 18D61
    • iPhone 12 Pro Max (mobile) • A5473606-0213-4FD8-BA16-553433949729     •
      ios            • com.apple.CoreSimulator.SimRuntime.iOS-14-3 (simulator)
    • macOS (desktop)            • macos                                    •
      darwin-x64     • Mac OS X 10.15.4 19E2269 darwin-x64
    • Chrome (web)               • chrome                                   •
      web-javascript • Google Chrome 98.0.4758.80

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 1 category.

Updares?

@darshankawar Just ran into this issue as well, and just want to point out that this issue should be considered critical IMO.
Just imagine the following:
We have a user object that contains permissions. It's delivery via a stream and fed into an InheritedWidget.
For the sake of simplicity we'll just contain it in a Stream.value(adminUser) for our admin user.
See how that would play out:
class _ExampleState extends State<Example> {
  // Example. The default user would never be an admin.
  Stream<User>? _stream = Stream.value(User(role: 'ADMIN'));

  void logout() {
    setState(() {
      _stream = null;
    });
  }

  @override
  Widget build(BuildContext context) {
    return StreamBuilder<User>(
      stream: _stream,
      builder: (context, snapshot) {
        // When logout is called, the _stream is null, but the previous value is emitted.
        // In effect, this means that our admin user is still available to the entire widget tree.
        return InheritedUser(user: snapshot.data);
      },
    );
  }
}


Fix #1807, increase SB pool max size bucket

Describe the contribution
In the default config, the maximum bucket size for the SB pool was not quite big enough to allocate a message of CFE_MISSION_SB_MAX_SB_MSG_SIZE.
This increases the margin so this can be allocated again.
Fixes #1807
Testing performed
Build and run all tests
Expected behavior changes
A call to CFE_SB_AllocateMessageBuffer(CFE_MISSION_SB_MAX_SB_MSG_SIZE) now succeeds and returns non-null.
System(s) tested on
Ubuntu
Additional context
On my system the sizeof(CFE_SB_BufferD_t) is 64, hence why 40 was not enough.  Using 128 just adds an extra margin for padding and platform differences, etc.  Users can still reduce this in their tuning if they are using every possible byte.
Note we cannot use sizeof(CFE_SB_BufferD_t) directly here because its a private structure.
Contributor Info - All information REQUIRED for consideration of pull request
Joseph Hickey, Vantage Systems, Inc.

CCB:2021-08-18 APPROVED


Dev test

dev-deps(mocha,eslint): install with npx when needed
rm .travis.yml
test: remove useless done, they are only required for callback style async tests
test: add note about future use of node --test, paving the road to reducing deps
ci: add testing on node 16, 18, 22
ci: update GHA dep versions

Okay, so several changes here:

dep(eslint): declared dependency on v8
move the test file into lib (next to the code it runs). Naming files with *.test.js and putting them next to the files they test is apparently a pattern. Your thoughts?
mocha -> node --test

ci: drop testing for older nodes that lack support for node --test

naming files with *.test.js and putting them next to the files they test is apparently a pattern.

Something I just thought of and don't like, is that putting the test file in lib publishes it on npm. That's a small deal, but with 36m weekly downloads, the smallness has a very large multiplier. I've talked myself out of it. 😲 Sorry for the noise.

Thanks!


Registry Preview Open file crashes the whole app

Microsoft PowerToys version
0.69.0
Installation method
Chocolatey
Running as admin
Yes
Area(s) with issue?
Registry Preview
Steps to reproduce

Open Registry Preview from PowerToy Settings
Click "Open file..." button
App will crash

✔ Expected Behavior
Open file dialog window to open
❌ Actual Behavior
App crashes
Other Software
No response

/dup #25250


Handle namespace change

We don't handle namespace changes while DI is running. This seems to be because we don't recreate the provider in cluster.go, so the provider continues using the previous namespace.

https://trello.com/c/iEHZQito/32-handle-namespace-change#


[Github] Remove CODEOWNERS

Currently, with the inclusion of the .github/CODEOWNERS file, Github requires a member of that list to approve a PR in order to get it merged.
To maximize flexibility and avoid blockers we want to allow all repo admins to approve a PR and have it then be mergeable.
As far as I can tell, we can't disable this requirement so long as this file exists.
If we still want some approval protection, this is the only setting I see that seems to relate:

Settings updated

Thanks for bringing this up @meissadia!


Config option to not override with empty values

Describe the feature request
so imagine we have a 'base' yaml file
app:
  name: base
  vault:
    url: url
    path: path

we have an 'override' yaml file
app:
  name: api
  vault: {}

we're unmarshalling these into map[string]interface{}
on merge
err = deepmerge.DeepMerge(<map with base app>, <map with override app>, mergeConfig)
if err != nil {
  return err
}

we have as a result:
app:
  name: api
  vault: {}

it seems pretty logical indeed, but It would be great to have that behaviour configurable.
Why do you personally want this feature to be implemented?
in order not to write omitempty to every yaml structure
How long have you been using this project?
No response
Additional information
No response

Just to make sure I understand, you'd want a way to have the 2nd yaml file override the 1st in instances where json objects are explicitly set to {}?
I'm not against the idea


Add Hugo v0.87.0 [release] (closes #221)

Closes #221.

This looks good to me. Thank you for contributing! 🎉


Empty Message Custom Properties default to Boolean type

When resubmitting a single message, any Message Custom Properties that are blank default to Boolean type, but then I can't send the message with the blank value. After I change those fields to a different "nullable" type (I use String), I can send.
It'd be nice if it could default to a type that can be empty, or to allow any available type to be empty.

@spongessuck I'm not entirely sure how to go about this one. Custom properties are stored as a key value collection, where a value is one of the allowed types. If the value is null, I'd assume the value would be the default of the type. Boolean would be always false by default. A billable version would be bool? but I'm not sure Azure service bus supports that in the headers.

Here's what the properties look like in SBE:

You can see the 3 empty properties have been assigned the Boolean type. The values are null when sent to Azure Service Bus but it seems like SBE is defaulting them to the first type in the dropdown (Boolean) and I couldn't resubmit this message until I change the type selection on the null/empty-valued properties.
According to the article you linked, the type of the value is inferred, so as far as I can tell, there should be nothing in the message itself to suggest these properties have Boolean values. In fact, none of these properties are Boolean values even when they do happen to have one.

The original message that is resubmitted, was it already with those boolean headers w/o values?

No, the original message came from a c# client, and no values assigned to
the properties dictionary were boolean types.
On Mon, Jun 6, 2022, 23:57 Sean Feldman @.***> wrote:

The original message that is resubmitted, was it already with those
boolean headers w/o values?
—
Reply to this email directly, view it on GitHub
https://github.com/paolosalvatori/ServiceBusExplorer/issues/646#issuecomment-1148166616,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABQTITU6Q3IZZJQYDIXKM23VN3CCFANCNFSM5VOKUVMA
.
You are receiving this because you were mentioned.Message ID:
@.***>

Do you have the C# code that generated the message? I'd like to see what was it. Don't need the whole repro, just the snippet that has created the message and the ASB SDK version.

SDK is from NuGet package "Microsoft.Azure.ServiceBus" version 5.0.8 or 5.2.0, depending on the client app.
The code creating the message looks like this:
        protected Message ToServiceBusMessage(object message, TimeSpan? timeToLive = null)
        {
            var serviceBusMessage = new Message
            {
                Body = Encoding.UTF8.GetBytes(Newtonsoft.Json.JsonConvert.SerializeObject(message)),
                ContentType = "application/json",
            };

            if (timeToLive != null)
                serviceBusMessage.TimeToLive = timeToLive.Value;

            var type = message.GetType();
            ...

            this.messageMutator.MutateOutgoing(serviceBusMessage.UserProperties);

            return serviceBusMessage;
        }

MutateOutgoing copies values from a dictionary to the UserProperties dictionary of the message. The values come from a context object that produces the values you see in the screenshot of SBE I posted. None of these properties are boolean type; the one that ends up set to Boolean in SBE is an int? that is set to null. When it has a value, the type in SBE is correctly set to an Int32, it's only when it's null does it get set to Boolean.

It's also worth noting that this problem doesn't happen when selecting and resubmitting multiple messages - SBE passes those along without issue. It only happens when resubmitting a single message and the UserProperty value is null.

We observe this in our application too, and it does not seem to be an ServiceBusExplorer issue.
It seems as if UserProperties with null values are serialized as Boolean from the .net client.


Update MarcinOtorowski.MSIXHero to version <IP_ADDRESS>

Microsoft Reviewers: Open in CodeFlow

 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.:x: marcinotorowski sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


Soundcloud support

Hi there,
I don't believe soundcloud is supported anymore. Nothing seems to get loaded.
Is this something that could be fixed.
Thanks

Hey,
I'm also using Magnific Popup and if you use the correct embed code link from SoundCloud it's working like a charm.
click me

If you want to see it live go to my blog http://eargasm.at and check out the post "Klingande ...".
Greetings

Hi,
More straightforward way or how the maginific popup works for iframe
[youtube, dailymotion, vimeo, soundcloud etc embed players are all iframe]

Read the iframe type documentation carefully and see the how the youtube and other video sties embed works
see the pattern for soundcloud, I think you can put the src in in different way,
the doc for 3 methods of source http://dimsemenov.com/plugins/magnific-popup/documentation.html#content-types

My bellow example is for 3rd method
$soundcloud_url = '';
$.magnificPopup.open({
                            items: {
                                src: $soundcloud_url
                            },

                            type: 'iframe', // this is default type
                            iframe: {
                                /*markup: '
'+
                                '

'+
                                ''+
                                '
', // HTML markup of popup, `mfp-close` will be replaced by the close button*/
                                patterns: {

                                    soundcloud: {
                                        index: 'soundcloud.com/',
                                        id: function(url) {
                                            return encodeURI(url)
                                        },
                                        src: '//w.soundcloud.com/player/?url=%id%&auto_play=true&hide_related=true&show_comments=false&show_user=false&show_reposts=false&visual=true;' // URL that will be set as a source for iframe.
                                    },
                                },
                                srcAction: 'iframe_src'
                            }
                        });


Visibility in Draw components doesn't work properly, I suppose

First of all, thanks for the great game engine!
I have used it to make my prototype game. In the game, I wanted to hide some object(entity) in a particular condition, so I changed the is_visible value in the Draw component of the entity.
But when I set the is_visible value to false, the frame buffer suddenly wasn't refreshed at all. The window kept showing me the last frame just before I set the value to false. And I set the value to true again, then whole world goes normally.
Is this intended or just a bug? If it is a bug, would you fix it or let me know where to start fixing?

(I assigned the bug label because it sounds like a bug to me, but I am not fully sure myself :sweat_smile: )

Yeah this certainly sounds like a bug. Individual entity visibility shouldn't determine whether or not we clear the framebuffer. A minimal example that reproduces the error would be helpful here.

@cart
I added some code to the bevy's breakout example to reproduce the bug:
https://gist.github.com/jayong93/6d2082442c8f7cfe5a4c89b532f98940
What I did is adding this system to breakout.rs to hide a ball on mouse click:
fn speed_circle_place_system(
    mut input_reader: ResMut<EventReader<MouseButtonInput>>,
    button_input: Res<Events<MouseButtonInput>>,
    mut query: Query<(&Ball, &mut Draw)>,
) {
    match input_reader.latest(&button_input) {
        Some(MouseButtonInput {
            button: MouseButton::Left,
            state: ElementState::Pressed,
        }) => {
            for (_, mut draw) in &mut query.iter() {
                draw.is_visible = !draw.is_visible;
            }
        }
        _ => {}
    }
}

If you click left mouse button, the ball would disappear. But also the paddle would stop moving even if you move it by pressing left/right arrow key.
I checked this bug on Windows 10 and I'm not sure that it is reproducible on other OSs.

Issue reproduced on Linux with @jayong93 code, with rustc 1.47.0-nightly (6c8927b0c 2020-07-26) and bevy at 6228e8a4bbdb966659f7dae1e87cf55e8318bde3

Resolved by #230


update windows installer pointer

We're not going to update to 7.10 until it happens uniformly for Mac and Linux too. In the meantime this points to the latest in the 7.8 series, removes the now-extraneous instructions to install alex and happy, and also points to the minghc page for other versions.

partially addresses #105 and #106


Hotfixes for testnet

Revert commit with cache reuse. It causes problems and doesn't add much compared to the second optimisation.

@AnnaShaleva, please confirm the fix.

Well, at the very minimum it works for me. 3 out of 3 attempts to sync fail on master and 3 out of 3 succeed using this branch.

The same thing, the problem is gone.


v3: non https connection to Hue bridge

Can it be that non-https connection to port 80 is no longer possible to the Hue Bridge?
It seems like it is always using https
  connect(username, clientkey, timeout) {
    const self = this
      , hostname = self.hostname
      , baseUrl = self.baseUrl
    ;

    return axios.get(`${baseUrl}/api/config`, {httpsAgent: new https.Agent({rejectUnauthorized: false})})

I only connect via https in v3, it is the more secure and appropriate way to connect once they started self signing certificates on the bridges.
What is the use case here for not being able to use https?

See https://github.com/iobroker-community-adapters/ioBroker.hue/issues/78
And I am also not sure if it’s possible to connect to the 1st gen Bridge via https or is support dropped anyways in v3? Did not find anything breaking wrt to this in changelog.

Hmmm, not sure I really want to go backwards on this.
The purpose of forcing https was to ensure users are better protected and using the security features of the bridge. I can see them removing http connections in the future as well. And the remote api is https also.
This is not a real bridge, but an emulation of a bridge, I had a series of issues a few years back with someone raising a whole bunch of issues against the library due to a poorly written emulation library.
I only provide this library to work against and validate against actual hue bridges.
I will take a look at what might be possible to support http connections tomorrow, but if I do expose this, it will be under some really clear connectInsecure() like function.

I understand your concerns. For me as a dev who uses the library it would be a good thing if I have the ability to stay backward compatible as much as possible - I am not sure if I am the only one who comes up with these issues or if v3 is just too new.
However a method like connectInsecure would be fine for me.
Thank you for looking into this.

I have released version 3.4.0 to the npm registry with an insecure connection option.
It will print a warning indicating that you are using an insecure method for establishing a connection to the Hue Bridge. Consumers of the library should be using https, which is the default for the library, and this is here only to satisfy the software emulation solutions that appear to exist.
I will not support issues that arise from this library being used against emulated bridges. The Bridge API changes and has plenty of minor quirks in it which come and goe as the bridge firmware is updated. Most emulated solutions will introduce other quirks or failures to match the Hue Bridge in certain edge cases.
To use the new connection method, use code like the following:
const v3Api = require('node-hue-api').v3.api;
const api = await v3Api.createInsecureLocal(ipAddress).connect('username');

To really get the point across about this not being something I want used it will report a warning to the user on console.error. This can be suppressed using the presence of an environment variable NODE_HUE_API_USE_INSECURE_CONNECTION as there may be valid situations that may require this, although I cannot think of any as disabling security for users is far from ideal.

Thanks, works.


Feature / Codebase Upgrade

Upgrade framework to 3.5, move to Symfony/Mailer, update codebase

Codecov Report

Merging #107 (e6adea5) into master (63b6da0) will decrease coverage by 1.54%.
The diff coverage is 80.78%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@             Coverage Diff              @@
##             master     #107      +/-   ##
============================================
- Coverage     99.65%   98.12%   -1.54%
- Complexity      801      817      +16
============================================
  Files           132      136       +4
  Lines          2643     2719      +76
============================================
+ Hits           2634     2668      +34
- Misses            9       51      +42

Impacted Files
Coverage Δ

app/src/Config/AppConfig.php
100.00% <ø> (ø)

app/src/Config/CdnConfig.php
100.00% <ø> (ø)

app/src/Config/CorsConfig.php
100.00% <ø> (ø)

app/src/Config/FirebaseConfig.php
100.00% <ø> (ø)

app/src/Config/JwtConfig.php
100.00% <ø> (ø)

app/src/Config/MailConfig.php
87.50% <ø> (-12.50%)
:arrow_down:

app/src/Config/S3Config.php
100.00% <ø> (ø)

app/src/Exception/ViewRenderer.php
0.00% <0.00%> (ø)

app/src/Security/PasswordChecker.php
100.00% <ø> (ø)

app/src/Security/UniqueChecker.php
100.00% <ø> (ø)

... and 26 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Update QAT recipe to match full_finetune_distributed

Summary: Many changes have gone into the full_finetune_distributed recipe but were not reflected on the equivalent qat_distributed recipe. This commit brings the latter up to date, adding features like FSDP2, configurable FSDP sharding, and profiling.
Test Plan:
Ran QAT and full fine-tune on 6 A100 GPUs using the default Llama3-8B configs on the alpaca dataset:
tune run --nnodes 1 --nproc_per_node 6 qat_distributed --config llama3/8B_qat_full
tune run --nnodes 1 --nproc_per_node 6 full_finetune_distributed --config llama3/8B_full

Microbenchmarks:
QAT average throughput per GPU: 205.789 tok/s
Full fine-tune average throughput per GPU: 221.237 tok/s

QAT average loss in first and last 100 steps: 1.08369 -> 0.554201
Full fine-tune average loss in first and last 100 steps: 1.06767 -> 0.534989

QAT max memory reserved on rank zero: 17.166 GB
Full fine-tune max memory reserved on rank zero: 17.041 GB

QAT evaluation results (quantized):
|  Tasks  |Version|Filter|n-shot|    Metric     | Value |   |Stderr|
|---------|------:|------|-----:|---------------|------:|---|------|
|wikitext |      2|none  |     0|word_perplexity|14.2488|±  |N/A   |
|         |       |none  |     0|byte_perplexity| 1.6435|±  |N/A   |
|         |       |none  |     0|bits_per_byte  | 0.7167|±  |N/A   |
|hellaswag|      1|none  |     0|acc            | 0.5666|±  |0.0049|
|         |       |none  |     0|acc_norm       | 0.7490|±  |0.0043|

Full fine-tune evaluation results (quantized):
|  Tasks  |Version|Filter|n-shot|    Metric     | Value |   |Stderr|
|---------|------:|------|-----:|---------------|------:|---|------|
|wikitext |      2|none  |     0|word_perplexity|28.3989|±  |N/A   |
|         |       |none  |     0|byte_perplexity| 1.8697|±  |N/A   |
|         |       |none  |     0|bits_per_byte  | 0.9028|±  |N/A   |
|hellaswag|      1|none  |     0|acc            | 0.5406|±  |0.0050|
|         |       |none  |     0|acc_norm       | 0.7190|±  |0.0045|

Reviewers: ebsmothers, kartikayk, RdoubleA
Subscribers: ebsmothers, kartikayk, RdoubleA

Looks great! Unrelated but didn't I remember that QAT used a fair bit more memory than vanilla full finetune? Based on the benchmark results, is that no longer the case?

Looks great! Unrelated but didn't I remember that QAT used a fair bit more memory than vanilla full finetune? Based on the benchmark results, is that no longer the case?

Yeah, but I think with activation checkpointing that mostly goes away. Even before fine-tuning Llama3-8B on C4 was just
67.501 GB vs 69.850 GB with activation checkpointing.


ng build --localize fails when using module federation

Hi
I have a project that uses module federation (similar to https://github.com/manfredsteyer/module-federation-plugin-example)
After I added translations and running ng build --localize getting error
Localized bundle generation failed: project-web\main.js: import.meta may appear only with 'sourceType: "module"
Did some debugging and pinpoint the issue to this line:
https://github.com/angular/angular-cli/blob/464cf330a14397470e1e57450a77f421a45a927e/packages/angular_devkit/build_angular/src/utils/process-bundle.ts#L150
I assume that babel parsing in this stage should not be responsible for validation of already processed code so this error does not make much sense.
Would it make sense to change this to sourceType: 'unambiguous'. - per babel documentation https://babeljs.io/docs/en/options#sourcetype this seems like valid solution.
I've tested this approach and generated code for non module federated projects is the same both 'script' and 'unambiguous' values is identical.
<EMAIL_ADDRESS><EMAIL_ADDRESS>

anyone figured out how to fix this? any workarounds?

You can write a post install script to patch that particular line of code, that worked for me.

Did someone figured that out? I'm having the same issue after upgrading to angular v13 :(

@milanc thanks, it's working!
@joseluiz98 as a temporary workaround you have to change sourceType to unambiguous in your local copy(inside node_modules) of this file https://github.com/angular/angular-cli/blob/464cf330a14397470e1e57450a77f421a45a927e/packages/angular_devkit/build_angular/src/utils/process-bundle.ts#L150
Then you can easily prepare a patch with this tool: https://github.com/ds300/patch-package

A possible workaround that worked for us is downgrading the TS compilation target from ES2020 to ES2019 in tsconfig.app.json.
It seems to remove this issue temporarily.

Hi,
i also have the problem, but also use nx.
Error messsage of running localized builds:
nx / angular is able to build localized apps. But if mfe is added by @angular-architects/module-federation all builds break.
NX   RunStart

{
  "meta": {
    "nxCloudVersion": "latest"
  },
  "branch": null,
  "runGroup": "0f812757bcc70676bb5819e0deedaa509f1bc284",
  "hashes": [
    "2c3ae5f6939f2bccc377b016d96487405561a7f1d855c6a01648870c6fb904fb"
  ]
}

RunStart duration: 191

  NX   Nx Cloud: Cache miss 2c3ae5f6939f2bccc377b016d96487405561a7f1d855c6a01648870c6fb904fb.

nx run my-angular-app:build:production

⠙ Generating browser application bundles (phase: setup)...<t> [webpack.cache.PackFileCacheStrategy] restore cache container: 26.084 ms
⠹ Generating browser application bundles (phase: building)...<t> [webpack.cache.PackFileCacheStrategy] check build dependencies: 1104.2983 ms
<t> [webpack.cache.PackFileCacheStrategy] restore cache content metadata: 4.6979 ms
    [webpack.cache.PackFileCacheStrategy] starting to restore cache content 1 (145 bytes) because of request to: ProgressPlugin|counts
    [webpack.cache.PackFileCacheStrategy] starting to restore cache content 0 (24.7 MiB) because of request to: ResolverCachePlugin|normal|default|dependencyType=|esm|path=|C:\Users\matth\repo\my-workspace|request=|C:\Users\matth\repo\my-workspace\apps\my-angular-app\src\main.ts
<t> [webpack.cache.PackFileCacheStrategy] restore cache content 1 (145 bytes): 1.2067 ms
    [webpack.cache.PackFileCacheStrategy] Deserialization of 'Compilation/modules|javascript/esm|C:\Users\matth\repo\my-workspace\node_modules\<EMAIL_ADDRESS>1.7432 ms
    [webpack.cache.PackFileCacheStrategy] Deserialization of 'Compilation/modules|C:\Users\matth\repo\my-workspace\node_modules\@angular-devkit\build-angular\src\babel\webpack-loader.js??ruleSet[1].rules[2].use[0]!C:\Users\matth\repo\my-workspace\node_modules\rxjs\dist\esm\index.js': 1.2591 ms
<t> [webpack.cache.PackFileCacheStrategy] restore cache content 0 (24.7 MiB): 56.5858 ms
⠏ Generating browser application bundles (phase: sealing)...    [IdleFileCachePlugin] Initial cache was generated and cache will be persisted in 5s.
✔ Browser application bundle generation complete.
asset 571.df38f542d438fb92.js 198 KiB {571} [emitted] [immutable] [javascript module]
asset 782.a97096cf750b5100.js 66.8 KiB {782} [emitted] [immutable] [javascript module] (name: bootstrap)
asset 181.e6fce2857afcd1cb.js 59.6 KiB {181}, {895} [emitted] [immutable] [javascript module]
asset 895.ba1290a87f6c39df.js 59.6 KiB {895} [emitted] [immutable] [javascript module]
asset polyfills.55f481b98fe5b811.js 39.9 KiB {429} [emitted] [immutable] [javascript module] (name: polyfills)
asset 3rdpartylicenses.txt 12.7 KiB [emitted]
asset main.9ea00fcddc7e95f9.js 6.66 KiB {179} [emitted] [immutable] [javascript module] (name: main)
asset styles.ef46db3751d8e999.css 0 bytes {532} [emitted] [immutable] (name: styles)
Entrypoint main 6.66 KiB = main.9ea00fcddc7e95f9.js
Entrypoint polyfills 39.9 KiB = polyfills.55f481b98fe5b811.js
Entrypoint styles = styles.ef46db3751d8e999.css
chunk {179} (runtime: main) main.9ea00fcddc7e95f9.js (main) 70 bytes (javascript) 84 bytes (share-init) 17.9 KiB (runtime) [entry]
  cached modules 70 bytes (javascript) 84 bytes (share-init) 17.9 KiB (runtime) [cached] 17 modules
chunk {181} (runtime: main, polyfills, styles) 181.e6fce2857afcd1cb.js 42 bytes (consume-shared) 257 KiB (javascript)
  cached modules 257 KiB (javascript) 42 bytes (consume-shared) [cached] 2 modules
chunk {429} (runtime: polyfills) polyfills.55f481b98fe5b811.js (polyfills) 109 KiB (javascript) 84 bytes (share-init) 17.8 KiB (runtime) [entry]
  cached modules 84 bytes (share-init) 109 KiB (javascript) 17.8 KiB (runtime) [cached] 20 modules
chunk {532} (runtime: styles) styles.ef46db3751d8e999.css (styles) 50 bytes (javascript) 79 bytes (css/mini-extract) 84 bytes (share-init) 17.6 KiB (runtime) [entry]
  cached modules 84 bytes (share-init) 50 bytes (javascript) 79 bytes (css/mini-extract) 17.6 KiB (runtime) [cached] 18 modules
chunk {571} (runtime: main, polyfills, styles) 571.df38f542d438fb92.js 1.15 MiB
  cached modules 1.15 MiB [cached] 36 modules
chunk {782} (runtime: main) 782.a97096cf750b5100.js (bootstrap) 194 KiB (javascript) 84 bytes (consume-shared)
  cached modules 194 KiB (javascript) 84 bytes (consume-shared) [cached] 38 modules
chunk {895} (runtime: main) 895.ba1290a87f6c39df.js 257 KiB
  cached modules 257 KiB [cached] 1 module

LOG from webpack.Compiler
<t> make hook: 272.8485 ms
<t> finish make hook: 1.0202 ms
<t> finish compilation: 65.454 ms
<t> seal compilation: 384.7858 ms
<t> afterCompile hook: 0.1608 ms
<t> emitAssets: 5.9655 ms
<t> emitRecords: 0.0642 ms
<t> done hook: 0.5758 ms
<t> beginIdle: 0.8606 ms

LOG from webpack.Compilation
<t> compute affected modules: 0.0021 ms
<t> finish modules: 62.7385 ms
<t> report dependency errors and warnings: 2.6876 ms
<t> optimize dependencies: 6.8187 ms
<t> create chunks: 5.0066 ms
<t> compute affected modules with chunk graph: 0.0025 ms
<t> optimize: 29.0058 ms
    89 modules hashed, 0 from cache (0.36 variants per module in average)
<t> module hashing: 9.9771 ms
    0% code generated (0 generated, 48 from cache)
<t> code generation: 1.3689 ms
<t> runtime requirements.modules: 0.8019 ms
<t> runtime requirements.chunks: 0.2513 ms
<t> runtime requirements.entries: 3.6395 ms
<t> runtime requirements: 4.755 ms
<t> hashing: initialize hash: 0.0036 ms
<t> hashing: sort chunks: 0.055 ms
<t> hashing: hash runtime modules: 6.1114 ms
<t> hashing: hash chunks: 2.3144 ms
<t> hashing: hash digest: 0.0432 ms
<t> hashing: process full hash modules: 0.0017 ms
<t> hashing: 8.7488 ms
    0% code generated (0 generated, 43 from cache)
<t> record hash: 0.0566 ms
<t> module assets: 0.1814 ms
<t> create chunk assets: 1.4976 ms
<t> process assets: 316.0206 ms

LOG from webpack.ResolverCachePlugin
    0% really resolved (0 real resolves with 0 cached but invalid, 1679 cached valid, 0 concurrent)

LOG from webpack.FlagDependencyExportsPlugin
<t> restore cached provided exports: 1.7472 ms
<t> figure out provided exports: 4.8063 ms
    1% of exports of modules have been determined (8 no declared exports, 3 not cached, 0 flagged uncacheable, 235 from cache, 0 from mem cache, 0 additional calculations due to dependencies)
<t> store provided exports into cache: 0.0056 ms

LOG from webpack.SideEffectsFlagPlugin
<t> update dependencies: 1.9035 ms

LOG from webpack.FlagDependencyUsagePlugin
<t> initialize exports usage: 0.3896 ms
<t> trace exports usage in graph: 3.5953 ms

LOG from webpack.buildChunkGraph
<t> visitModules: prepare: 0.291 ms
<t> visitModules: visiting: 0.8221 ms
<t> visitModules: calculating available modules: 0.3017 ms
<t> visitModules: merging available modules: 0.328 ms
<t> visitModules: check modules for revisit: 0.1049 ms
<t> visitModules: prepare: 0.8224 ms
<t> visitModules: visiting: 1.6323 ms
<t> visitModules: calculating available modules: 0.103 ms
<t> visitModules: merging available modules: 0.0218 ms
<t> visitModules: check modules for revisit: 0.0014 ms
<t> visitModules: prepare: 0.2417 ms
<t> visitModules: visiting: 0.4244 ms
    460 queue items processed (216 blocks)
    10 chunk groups connected
    5 chunk groups processed for merging (10 module sets, 3 forked, 97 + 3 modules forked, 12 + 2 modules merged into fork, 7 resulting modules)
    5 chunk group info updated (0 already connected chunk groups reconnected)
<t> visitModules: 3.8236 ms
<t> connectChunkGroups: 0.1523 ms
<t> cleanup: 0.0034 ms

LOG from webpack.SplitChunksPlugin
<t> prepare: 0.023 ms
i18n file queued for processing: 895.ba1290a87f6c39df.js
⠹ Generating localized bundles...i18n file processed: 782.a97096cf750b5100.js
i18n file processed: 181.e6fce2857afcd1cb.js
i18n file processed: 895.ba1290a87f6c39df.js
i18n file processed: polyfills.55f481b98fe5b811.js
✖ Localized bundle generation failed: Cannot assign to read only property 'message' of object 'SyntaxError: import.meta may appear only with 'sourceType: "module"' (1:2970)
An error occurred inlining file "main.9ea00fcddc7e95f9.js"

 ——————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————

  NX   Running target "my-angular-app:build" failed

   Failed tasks:

   - my-angular-app:build:production

   Hint: run the command with --verbose for more details.

   See Nx Cloud run details at https://nx.app/runs/vw94xNimTw

If anybody lands up here for the same reason as me. If you have:

Nx Repo
Angular 13
Module Federation MFE's
and localization requirements

You can't just go to target ES2019, you have to implement the patch-package fix.


local - when using branch is producing a main-less repo.

Overview
Local, when build from branch is creating a mainless repo:

Registry should be based on main to match cluster version.

Merged to Release 1.11 branch


Verified badge gets cut off

I noticed when after downloading that the verified badge gets cut off just by a little. This only happens after downloading and looks fine in preview.

I noticed it quite a long back and I'm expecting to fix it as soon as possible. Thanks for raising an issue because that will push me to work on it 😄.

Fixed it up.


onDataReceived event handler is not cleared when the device is connected again?

Mobile Device Environment
Provide a list of operating systems on which this issue is relevant.

Device: Android
OS: Android 10

Application Environment
Provide information about your development environment:

React Native version: 0.73.6
RN Bluetooth Classic version: 1.73.0-rc.10

Describe the bug
So, here is my logic:
I want to connect to Device (say, device A), then subscribe to onDataReceived. If the device disconnects (for example, it is turned off), I will recursively try to connect to the device, until the device is turned on and connected, then I want the onDataReceived to subscribe again.
This logic works, in the sense that I can get the data at the initial connection, then automatically connect to the device when it is turned off and on again.
However, it seems that after the device is turned back on, all the data that I get are duplicated.
If I keep doing that (turn the device off and on again), every time when the device is turned on, I get 1 additional set of the same data.
To Reproduce
Steps to reproduce the behavior:

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

Expected behavior
When the device is reconnected again, I should only get the data once, not 2, 3, 4, etc times.
I am using a Garmin Glo 2 GPS receiver as an example. The data frequency is 10 Hz (i.e. I should get 10 data strings every second), but as soon as I turn off and on the device, I get 20Hz, 30Hz, etc.

The expectation here is that you're maintaining the connection and removing the listener when the connection is dropped.  I don't want to start doing things for people within the library and having it break others expectations, I also don't think the library should be responsible for managing things like this, for example if you're connecting to a number of devices at one time, now the library needs to manage all those?  What about for those that use the setTimeout and read manual method?

@kenjdavidson lol. Sorry. I forgot to save the reference to the listener and call .remove when I detect the device is disconnected. Thank you