Strange behavior while using @extend multiple times

To avoid multiple lines of CSS, I'm using the foundations exports mixin (short description here).
But if I use @import to include my module multiple times, the @extend-functions blows up my css.
I also tried a @mixin instead of @extend and asserted that there is no problem.
Code does say more than thousand words, so I made a gist that shows the problem:
https://gist.github.com/NikFlip/5418438ef0da2dd1c694
Just run:
$ npm install
$ node .

and watch the result in the console
===
should:
.selector-with-extend {
  background: red; }

.selector-without-extend {
  color: green; }

is:
.selector-with-extend {
  background: red; }

.selector-without-extend {
  color: green; }

.selector-with-extend {
  background: red; }

.selector-with-extend {
  background: red; }

.selector-with-extend {
  background: red; }

@NikFlip how are defining should?
Node Sass should do what Ruby Sass does.
Ruby Sass 3.4.18
/**
 * List of already exported style blocks. Used by mixin `exports(name)`.
 */
/**
 * Exports the given @content once. Uses the name, passed as first parameter to
 * evaluate if the content was already exported. We use this to prevent styles
 * from being loaded multiple times for components that rely on other components.
 *
 * @param {name} name
 */
/**
 * Import the same module four times
 */
.selector-with-extend {
  background: red; }

.selector-without-extend {
  color: green; }

.selector-with-extend {
  background: red; }

.selector-with-extend {
  background: red; }

.selector-with-extend {
  background: red; }

Node Sass 3.4.2
/**
 * List of already exported style blocks. Used by mixin `exports(name)`.
 */
/**
 * Exports the given @content once. Uses the name, passed as first parameter to
 * evaluate if the content was already exported. We use this to prevent styles
 * from being loaded multiple times for components that rely on other components.
 *
 * @param {name} name
 */
/**
 * Import the same module four times
 */
.selector-with-extend {
  background: red; }

.selector-without-extend {
  color: green; }

.selector-with-extend {
  background: red; }

.selector-with-extend {
  background: red; }

.selector-with-extend {
  background: red; }


[ez] linter autofix

[ez] linter autofix
Your code has been rated at 6.99/10 (+0.27)

Should this be failing python tests?
I just pulled aiconfig main & running this on Mac had no failures (I have python aliased to python3 in ~/.zshrc):
cd ~/Projects/aiconfig/python
python -m venv ./venv
source ./venv/bin/activate
pip install -r requirements.txt
pip install -r requirements-dev.txt
pip install -e .
pytest

Should this be failing python tests?
I just pulled aiconfig main & running this on Mac had no failures (I have python aliased to python3 in ~/.zshrc):
cd ~/Projects/aiconfig/python
python -m venv ./venv
source ./venv/bin/activate
pip install -r requirements.txt
pip install -r requirements-dev.txt
pip install -e .
pytest

Yeah, I noticed the same thing. pytest does not reproduce this. I'm working on that; we should be able to easily repro CI tests locally


Feature/problem report didcomm message

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

Project coverage is 22.51%. Comparing base (3471b60) to head (729f9a0).

Files
Patch %
Lines

...common/response/problem_report_message_entity.dart
0.00%
36 Missing :warning:

...ta_sources/lib_pidcore_credential_data_source.dart
0.00%
3 Missing :warning:

...dential/libs/polygonidcore/pidcore_credential.dart
0.00%
2 Missing :warning:

...ial/data/data_sources/local_claim_data_source.dart
0.00%
1 Missing :warning:

...mm/domain/use_cases/get_iden3message_use_case.dart
50.00%
1 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff             @@
##           develop     #400      +/-   ##
===========================================
- Coverage    22.60%   22.51%   -0.09%
===========================================
  Files          314      315       +1
  Lines         8768     8810      +42
===========================================
+ Hits          1982     1984       +2
- Misses        6786     6826      +40

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


Missing validation on pipeline and connector connection

Problem
It is possible to create a invalid and non obviously wrong configuration when connecting to non existing ports on sources, sinks or pipelines.
Steps

connect the in port of a source to the in port of a pipeline
observe no error
observe no data flowing

Possible Solution(s)
We should validate the choice of ports when connecting different artifacts.

Upon the binding process in https://github.com/tremor-rs/tremor-runtime/blob/main/src/repository/artefact.rs#L487 we should verify that we only ever link

from an output port (not in) AND
to an input port (in)

and return with an error if we don't.

@mfelsche I picked up this issue before I got a chance to read your comment. This patch should do the trick as well. Please let me know, if this isn't what we are looking for :)

@aryan9600 nice patch. This is in principle a good approach, but it will only catch the cases where both ports are the same. We need to check the conditions described above.

I think to really solve this it will require for artifacts to share what input/output ports are available on them so it can be validated not only that they exist, but also that they are going in the right direction right

that we only ever link  from an output port (not in) AND to an input port (in)
@mfelsche do you mean that a upstream entity can only have an /out port and a downstream entity an /in port?

An upstream entity can have any output port, except the reserved in port. There is only one in port for input. We might revisit this at some point, but for now this is how it is.

So rather the validation should be something like any upstream entity can have any output port except in and make sure that all downstream entities have a in port? I guess if we validate this we implicitly guarantee that upstream and downstream entities don't have the same ports.

I think it will be a bit more complicated. We need to track all valid input/output ports and check that connections are done in the correct direction.
If we allow or forbid naming input and output ports the same isn't strict as of today. Right now we could have a output port called in and it would work correctly as long as we connect it up correctly.
I think there are arguments for both unique names and unique for input and output and allowing them to exist side by side. For the sake of preventing 'footguns' I would opt for unique names (i.e. we can't have an input and output port with the same name) but that's my personal bias for explicitly not founded in any facts other than "this kind of things have bitten me in the past".


Building with Vite

I'm running into an odd issue with the dependency when building with Vite.
Here's a simple component using react-responsive:
import React from 'react';
import { useMediaQuery } from 'react-responsive';

const Component = () => {
  const isMobile = useMediaQuery({ query: '(max-width: 991px)' });

  if (isMobile) {
    return Mobile view;
  }

  return PC View;
};

export default Component;

After building with Vite (vite build) and visiting my website, it'll return me an error:
TypeError: reactResponsive.exports.useMediaQuery is not a function

I've tried numerous things to fix this issue. One odd fix is by simply logging the imported function.
import React from 'react';
import { useMediaQuery } from 'react-responsive';

+ console.log(useMediaQuery);

const Component = () => {
  const isMobile = useMediaQuery({ query: '(max-width: 991px)' });

  if (isMobile) {
    return Mobile view;
  }

  return PC View;
};

export default Component;

I've also run Vite in development mode (vite), and this issue did not arise within that environment.

@Kyzegs Are you using the latest 9.0.0 beta or the 8.x version?

Using Vite 3.0.0-beta.4 solved the issue for me.


Backporting shape hash optimization

@devdoshi well turns out the thing we did before didn't work right. using sets now and everything seems friendly again


feat(ui): redesign asset & rate limit alerts

Update clockface to 2.3.0
Update Asset Limit alerts to be in-list
Replace the upgrade button with rate limit alert when cardinality is exceeded

Rate Limit Alert

Asset Limit Alert

[x] CHANGELOG.md updated with a link to the PR (not the Issue)
[x] Well-formatted commit messages
[x] Rebased/mergeable
[ ] Tests pass

@bpalani fyi


CCTextureCache AddImageAsync not working

Closed via commit https://github.com/mono/CocosSharp/commit/b1e9d837d8e767074d9781d10b474ed7a07486e2


Use the newly added dependency pruning

Bazel 0.27 has finally allowed Starlark access to dependency pruning, a feature that has previously been reserved only for native rules.
https://github.com/bazelbuild/bazel/commit/57363813d3c72129c61c35a2b03c3033b62cb49d
Implement unused_inputs_list for TypeScript compilation, thereby improving cache hits.

Can you give a hint how you think this would be used? Would we detect that a certain input wasn't read in one compilation and then assume it won't be read in a following compilation either?


DocumentDB Swagger Spec

This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information

[X] The title of the PR is clear and informative.
[X] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[X] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[X] If applicable, the PR references the bug/issue that it fixes.
[X] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[X] I have read the contribution guidelines.
[X] My spec meets the review criteria:

[X] The spec conforms to the Swagger 2.0 specification.
[X] Validation errors from the Linter extension for VS Code have all been fixed for this spec. (Note: for large, previously checked in specs, there will likely be many errors shown. Please contact our team so we can set a timeframe for fixing these errors if your PR is not going to address them).
[X] The spec follows the patterns described in the Swagger good patterns document unless the service API makes this impossible.

This change is

Hi @dmakwana, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

It looks like you're working at Microsoft (dimakwan). If you're full-time, we DON'T require a contribution license agreement.

If you are a vendor, DO please sign the electronic contribution license agreement. It will take 2 minutes and there's no faxing! https://cla.azure.com.

TTYL, AZPRBOT;

@amarzavery Unfortunately, had to do a force push, but I've addressed the comments.

Content writer review complete!

@amarzavery Let me know if there are any fixes needed

@tbombach & @amarzavery & @erickson-doug just a reminder that this is waiting to be reviewed/merged. Needs to be merged by 11/4.

This will be reviewed before EOD today.
Thanks,
Amar
From: Mimi Gentz<EMAIL_ADDRESS>Sent: Wednesday, November 2, 2016 12:58 PM
To: Azure/azure-rest-api-specs<EMAIL_ADDRESS>Cc: Amar Zavery<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [Azure/azure-rest-api-specs] DocumentDB Swagger Spec (#603)
@tbombachhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Ftbombach&data=02|01|amzavery%40microsoft.com|94e7e0c65d824dd8ad1408d4035a94fd|72f988bf86f141af91ab2d7cd011db47|1|0|636137134975184403&sdata=CG68%2BLxhDBjkulNBdGvZFD4uXd71Uk3tDq7i8Xc9POE%3D&reserved=0 & @amarzaveryhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Famarzavery&data=02|01|amzavery%40microsoft.com|94e7e0c65d824dd8ad1408d4035a94fd|72f988bf86f141af91ab2d7cd011db47|1|0|636137134975184403&sdata=gw%2F1N4rjCIC7Z6U75cLLYWcuMw5shAIa%2BY9fnujv99k%3D&reserved=0 & @erickson-doughttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Ferickson-doug&data=02|01|amzavery%40microsoft.com|94e7e0c65d824dd8ad1408d4035a94fd|72f988bf86f141af91ab2d7cd011db47|1|0|636137134975184403&sdata=oPakKmPk%2Ff0hOzmmrNIbAYeOUjmtQjJooYoMkpHOOWY%3D&reserved=0 just a reminder that this is waiting to be reviewed/merged. Needs to be merged by 11/4.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2Fazure-rest-api-specs%2Fpull%2F603%23issuecomment-257980814&data=02|01|amzavery%40microsoft.com|94e7e0c65d824dd8ad1408d4035a94fd|72f988bf86f141af91ab2d7cd011db47|1|0|636137134975184403&sdata=%2FLGQxvM3Lvncgfv2NHYYQZEEd98VOCPbLeI3AgFo0Ug%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAET9B8mdBE_Wn6jagkaytblFbWXp9p6Zks5q6OtVgaJpZM4KVXl0&data=02|01|amzavery%40microsoft.com|94e7e0c65d824dd8ad1408d4035a94fd|72f988bf86f141af91ab2d7cd011db47|1|0|636137134975184403&sdata=nNQr2%2BoNhmr1mPdajb%2FqsslgUkQoQdxodf86HFRQbg4%3D&reserved=0.

@mimig1 - Please make sure that the description in the spec for all the artifacts are as per the guidelines from the documentation team. Please sync with @erickson-doug  about this before EOD today. This will make sure there are no multiple PRs after this PR is merged.

@amarzavery - I am the writer that reviewed this and I believe it meets the guidelines. This is my first swagger file though. I checked it using a swagger previewer and I also used grammarly.

@amarzavery I've addressed the comments

@dmakwana - Are we waiting on signoff from @amarzavery?

@mimig1 yes

@amarzavery ready

Will merge once the CI passes

No modification for Python

No modification for NodeJS

No modification for Ruby


stack traces are useless

Chrome 45.0.2454 (Mac OS X 10.10.5) ERROR
  Uncaught TypeError: Cannot read property 'actions' of undefined
  at /Users/vlin/workspace/source-2/responsive-web/src/tests.bundle.js:55939:0 <- webpack:///src/modules/flux-context/index.jsx:41:8
Chrome 45.0.2454 (Mac OS X 10.10.5): Executed 0 of 0 ERROR (1.175 secs / 0 secs)

Great? Could really use more than one line of context here. I'm not sure if the problem lies in mocha, karma-webpack, webpack, karma, babel, or any of the other bricks in the towering abomination of build tools we've constructed...

What version of mocha are you using? Wondering it it's an issue with stacktrace filtering, since we have a couple open issues. Could you you post the output with mocha 2.2.0?

Hey @danielstjules,
That output came from 2.2.1. After doing some more digging it looks like the truncated stack traces happen when there's a crash in the test setup (tests haven't actually started running yet). If you point me towards where to look for the stacktrace filtering logic I can investigate more.

that doesn't have anything to do with mocha though. It's the way karma+babel+webpack build the test file

Stack filtering was introduced in 2.2.2 though, so it's likely unrelated to mocha

Gotcha. Thanks!

@wonnage you could set devtool to source-map in your webpack config and use node-source-map-support with Mocha by passing --require source-map-support/register. This will report line lumbers from the source, not the compiled bundle.


WIP: Filestore validation callback.

@tacaswell can probably do this better, but I'll leave this PR here so we remember that it exists. Feel free to supercede.

This needs to be revisited in light of new api's in dataportal, metadatastore and filestore

It's like we also broke some other bits of broker_callbacks.
On Mon, Sep 21, 2015 at 9:36 AM Eric Dill<EMAIL_ADDRESS>wrote:

This needs to be revisited in light of new api's in dataportal,
metadatastore and filestore
—
Reply to this email directly or view it on GitHub
https://github.com/NSLS-II/bluesky/pull/60#issuecomment-141980221.

Superceded by a succinct implementation in #311


Roll Flutter Engine from 05e26c1b2c79 to 8055bc973a8a (4 revisions)

https://github.com/flutter/engine/compare/05e26c1b2c79...8055bc973a8a
2023-10-11<EMAIL_ADDRESS>Roll Dart SDK from 0732be6b823a to db2465f106ad (8 revisions) (flutter/engine#46797)
2023-10-11<EMAIL_ADDRESS>[Impeller] Use triangle strips to dedupe rectangle vertices. (flutter/engine#46610)
2023-10-11<EMAIL_ADDRESS>[Impeller] Bump impeller-cmake (flutter/engine#46764)
2023-10-11<EMAIL_ADDRESS>Roll Skia from 2459d71707e0 to 924df8d87766 (7 revisions) (flutter/engine#46798)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC jsimmons@google.com,rmistry<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


🐛 [firebase_dynamic_links] iMessage short link error

Bug report
When I generate a short link and send it through iMessage, the link changes and becomes invalid. A normal shortlink has the structure like https://myapp.page.link/aBcd.  If I share the link using the library share. Using other apps to share, like WhatsApp or Slack, it works just fine. It happens only with iMessage (not regular msgs but iMessage) that the link changes to something like https://myapp.page.link/s?socialDescription=My+Description&socialImageUrl=some://url&socialTitle=My+Title. Which is not valid and does no let me process my params correctly. I get the error:
Deep Link does not contain valid required params

Note: this does not happen with long links.
Steps to reproduce

Generate a short link.
Share the link on iMessage to another iMessage user
Tap on sent link
Get error

You can copy the shared link, and see that weird structure
Expected behavior

Generate a short link.
Share the link on iMessage to another iMessage user
Short link should open app with specified parameters

Sample project
My share function looks like the following:
import 'package:firebase_dynamic_links/firebase_dynamic_links.dart';
import 'package:share/share.dart';

Future<Uri> createShortOrLongLink(bool short, DynamicLinkParameters parameters) async {
  Uri url;
  if (short) {
    final ShortDynamicLink shortLink = await parameters.buildShortLink();
    url = shortLink.shortUrl;
  } else {
    url = await parameters.buildUrl();
  }
  return url;
}

...

onShareLink() async {
  Uri url = createShortOrLongLink(true, myParams);
  Share.share(url);
}

Additional context
iOS 14.5
Flutter 2.0.6
Share ^2.0.1
Flutter Dynamic Links: ^2.0.3

Flutter doctor
Run flutter doctor and paste the output below:
Click To Expand
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel unknown, 2.0.6, on macOS 11.4 20F71 darwin-x64, locale en-US)
[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
[✓] Xcode - develop for iOS and macOS
[✓] Chrome - develop for the web
[✓] Android Studio (version 4.1)
[✓] VS Code (version 1.56.2)
[✓] Connected device (3 available)

Flutter dependencies
Run flutter pub deps -- --style=compact and paste the output below:
Click To Expand
Dart SDK 2.12.3
Flutter SDK 2.0.6
Myapp 1.51.0-2

dependencies:
- another_flushbar 1.10.20 [pedantic flutter]
- bloc_test 8.0.0 [bloc meta mocktail test]
- cached_network_image 3.0.0 [flutter flutter_cache_manager octo_image]
- carousel_slider 4.0.0-nullsafety.0 [flutter]
- characters 1.1.0
- csv 5.0.0
- cupertino_icons 1.0.3
- dartz 0.10.0-nullsafety.2
- data_connection_checker_tv 0.3.4-nullsafety
- equatable 2.0.0 [collection meta]
- ext_storage 1.0.3 [flutter]
- firebase_analytics 8.0.4 [firebase_analytics_platform_interface firebase_analytics_web firebase_core flutter meta]
- firebase_core 1.1.1 [firebase_core_platform_interface firebase_core_web flutter meta]
- firebase_crashlytics 2.0.3 [firebase_core firebase_core_platform_interface firebase_crashlytics_platform_interface flutter stack_trace]
- firebase_dynamic_links 2.0.3 [firebase_core flutter]
- firebase_messaging 9.1.4 [firebase_core firebase_core_platform_interface firebase_messaging_platform_interface firebase_messaging_web flutter meta]
- flex_color_picker 2.0.1 [flutter]
- flutter 0.0.0 [characters collection meta typed_data vector_math sky_engine]
- flutter_bloc 7.0.0 [flutter bloc provider]
- flutter_native_timezone 1.0.10 [flutter]
- flutter_redux 0.8.2 [redux flutter]
- flutter_svg 0.22.0 [flutter meta path_drawing vector_math xml]
- flutter_web_auth 0.3.0 [flutter]
- fluttertoast 8.0.6 [flutter flutter_web_plugins]
- font_awesome_flutter 9.0.0 [flutter]
- get_it 7.1.3 [async collection]
- hexcolor 2.0.3 [flutter flutter_web_plugins]
- http 0.13.3 [async http_parser meta path pedantic]
- image_picker 0.7.5 [flutter flutter_plugin_android_lifecycle image_picker_platform_interface image_picker_for_web]
- intl 0.17.0 [clock path]
- intl_phone_field 2.0.0 [flutter]
- intl_phone_number_input 0.7.0+2 [flutter meta libphonenumber_plugin equatable collection]
- multi_image_picker 4.8.00 [flutter meta]
- open_file 3.2.1 [flutter ffi]
- path_provider 2.0.1 [flutter path_provider_platform_interface path_provider_macos path_provider_linux path_provider_windows]
- pdf 3.3.0 [archive barcode crypto image meta path_parsing vector_math xml]
- pdf_viewer_jk 2.1.0 [flutter async flutter_cache_manager path_provider numberpicker http path flutter_svg pool]
- percent_indicator 3.0.1 [flutter]
- permission_handler 7.1.0 [flutter meta permission_handler_platform_interface]
- plaid_flutter 2.1.2 [flutter flutter_web_plugins js]
- random_string 2.2.0-nullsafety
- redux 5.0.0
- redux_thunk 0.4.0 [redux]
- share 2.0.1 [meta mime flutter]
- shared_preferences 2.0.5 [meta flutter shared_preferences_platform_interface shared_preferences_linux shared_preferences_macos shared_preferences_web shared_preferences_windows]
- sqflite 2.0.0+3 [flutter sqflite_common path]
- square_in_app_payments 1.7.1 [flutter built_value built_collection meta]
- stripe_sdk 5.0.0-nullsafety.0 [flutter http url_launcher mask_text_input_formatter flutter_slidable simple_animations supercharged awesome_card uni_links2 credit_card_validator collection]
- timezone 0.7.0 [path]
- uni_links2 0.6.0+2 [uni_links2_platform_interface uni_links_web2 flutter]
- url_launcher 6.0.3 [flutter url_launcher_platform_interface url_launcher_linux url_launcher_macos url_launcher_windows url_launcher_web]
- validators 3.0.0
- webview_flutter 2.0.4 [flutter]
- yaml 3.1.0 [collection source_span string_scanner]

dev dependencies:
- flutter_driver 0.0.0 [file meta path vm_service webdriver flutter flutter_test fuchsia_remote_debug_protocol archive args async boolean_selector characters charcode clock collection convert crypto fake_async matcher platform process source_span stack_trace stream_channel string_scanner sync_http term_glyph test_api typed_data vector_math]
- flutter_test 0.0.0 [flutter test_api path fake_async clock stack_trace vector_math async boolean_selector characters charcode collection matcher meta source_span stream_channel string_scanner term_glyph typed_data]
- mockito 5.0.7 [analyzer build code_builder collection dart_style matcher meta path source_gen test_api]
- test 1.16.5 [analyzer async boolean_selector coverage http_multi_server io js node_preamble package_config path pedantic pool shelf shelf_packages_handler shelf_static shelf_web_socket source_span stack_trace stream_channel typed_data web_socket_channel webkit_inspection_protocol yaml test_api test_core]

dependency overrides:
- archive 3.1.2 [crypto path]
- convert 3.0.0 [typed_data]
- crypto 3.0.1 [collection typed_data]

transitive dependencies:
- _fe_analyzer_shared 21.0.0 [meta]
- analyzer 1.5.0 [_fe_analyzer_shared cli_util collection convert crypto glob meta package_config path pub_semver source_span watcher yaml pedantic]
- args 1.6.0
- async 2.5.0 [collection]
- awesome_card 1.1.5 [flutter]
- barcode 2.1.0 [meta qr]
- bloc 7.0.0 [meta]
- boolean_selector 2.1.0 [source_span string_scanner]
- build 2.0.1 [analyzer async convert crypto glob logging meta path]
- built_collection 5.0.0
- built_value 8.0.6 [built_collection collection fixnum]
- charcode 1.2.0
- cli_util 0.3.0 [meta path]
- clock 1.1.0
- code_builder 4.0.0 [built_collection built_value collection matcher meta]
- collection 1.15.0
- coverage 0.15.2 [args logging package_config path source_maps stack_trace vm_service]
- credit_card_type_detector 2.0.0-nullsafety.0
- credit_card_validator 2.0.0-nullsafety.0 [credit_card_type_detector]
- dart_style 2.0.1 [analyzer args path pub_semver source_span]
- fake_async 1.2.0 [clock collection]
- ffi 1.0.0
- file 6.0.0 [meta path]
- firebase 9.0.1 [http http_parser js]
- firebase_analytics_platform_interface 2.0.1 [flutter meta]
- firebase_analytics_web 0.3.0+1 [firebase firebase_analytics_platform_interface flutter flutter_web_plugins meta]
- firebase_core_platform_interface 4.0.1 [collection flutter meta plugin_platform_interface]
- firebase_core_web 1.0.3 [firebase_core_platform_interface flutter flutter_web_plugins js meta]
- firebase_crashlytics_platform_interface 3.0.3 [collection firebase_core flutter meta plugin_platform_interface]
- firebase_messaging_platform_interface 2.1.4 [firebase_core flutter meta plugin_platform_interface]
- firebase_messaging_web 1.0.7 [firebase_core firebase_core_web firebase_messaging_platform_interface flutter flutter_web_plugins js meta]
- fixnum 1.0.0
- flutter_blurhash 0.6.0 [flutter meta pedantic]
- flutter_cache_manager 3.0.2 [clock collection file flutter http image path path_provider pedantic rxdart sqflite uuid]
- flutter_plugin_android_lifecycle 2.0.1 [flutter]
- flutter_slidable 0.6.0 [flutter]
- flutter_web_plugins 0.0.0 [flutter js characters collection meta typed_data vector_math]
- fuchsia_remote_debug_protocol 0.0.0 [process vm_service file meta path platform]
- glob 2.0.1 [async collection file path pedantic string_scanner]
- http_multi_server 3.0.1 [async]
- http_parser 4.0.0 [charcode collection source_span string_scanner typed_data]
- image 3.0.2 [archive meta xml]
- image_picker_for_web 2.0.0 [image_picker_platform_interface meta flutter flutter_web_plugins]
- image_picker_platform_interface 2.1.0 [flutter meta http plugin_platform_interface]
- infinite_listview 1.1.0 [flutter]
- io 1.0.0 [meta path string_scanner]
- js 0.6.3
- libphonenumber 2.0.0 [flutter meta]
- libphonenumber_platform_interface 0.3.1 [flutter plugin_platform_interface]
- libphonenumber_plugin 0.2.3 [flutter flutter_web_plugins libphonenumber_platform_interface libphonenumber_web libphonenumber]
- libphonenumber_web 0.2.0+1 [flutter flutter_web_plugins js libphonenumber_platform_interface]
- logging 1.0.1
- mask_text_input_formatter 2.0.0-nullsafety.2 [flutter]
- matcher 0.12.10 [stack_trace]
- meta 1.3.0
- mime 1.0.0
- mocktail 0.1.2 [collection matcher test]
- nested 1.0.0 [flutter]
- node_preamble 1.4.13
- numberpicker 2.1.1 [flutter infinite_listview]
- octo_image 1.0.0+1 [flutter flutter_blurhash]
- package_config 2.0.0 [path]
- path 1.8.0
- path_drawing 0.5.1 [vector_math meta path_parsing flutter]
- path_parsing 0.2.1 [vector_math meta]
- path_provider_linux 2.0.0 [path xdg_directories path_provider_platform_interface flutter]
- path_provider_macos 2.0.0 [flutter]
- path_provider_platform_interface 2.0.1 [flutter meta platform plugin_platform_interface]
- path_provider_windows 2.0.1 [path_provider_platform_interface meta path flutter ffi win32]
- pedantic 1.11.0
- permission_handler_platform_interface 3.3.0 [flutter meta plugin_platform_interface]
- petitparser 4.1.0 [meta]
- platform 3.0.0
- plugin_platform_interface 2.0.0 [meta]
- pool 1.5.0 [async stack_trace]
- process 4.0.0 [file path platform]
- provider 5.0.0 [collection flutter nested]
- pub_semver 2.0.0 [collection]
- qr 2.0.0 [meta]
- rxdart 0.27.0
- shared_preferences_linux 2.0.0 [flutter file meta path path_provider_linux shared_preferences_platform_interface]
- shared_preferences_macos 2.0.0 [shared_preferences_platform_interface flutter]
- shared_preferences_platform_interface 2.0.0 [flutter]
- shared_preferences_web 2.0.0 [shared_preferences_platform_interface flutter flutter_web_plugins meta]
- shared_preferences_windows 2.0.0 [shared_preferences_platform_interface flutter file meta path path_provider_platform_interface path_provider_windows]
- shelf 1.1.4 [async collection http_parser path stack_trace stream_channel]
- shelf_packages_handler 3.0.0 [path shelf shelf_static]
- shelf_static 1.0.0 [convert http_parser mime path shelf]
- shelf_web_socket 1.0.1 [shelf stream_channel web_socket_channel]
- simple_animations 3.1.1 [flutter supercharged pedantic]
- sky_engine 0.0.99
- source_gen 1.0.0 [analyzer async build dart_style glob meta path pedantic source_span]
- source_map_stack_trace 2.1.0 [path stack_trace source_maps]
- source_maps 0.10.10 [source_span]
- source_span 1.8.0 [charcode collection path term_glyph]
- sqflite_common 2.0.0+2 [synchronized path meta]
- stack_trace 1.10.0 [path]
- stream_channel 2.1.0 [async]
- string_scanner 1.1.0 [charcode source_span]
- supercharged 2.0.0 [supercharged_dart flutter]
- supercharged_dart 2.0.0
- sync_http 0.2.0
- synchronized 3.0.0
- term_glyph 1.2.0
- test_api 0.2.19 [async boolean_selector collection meta path source_span stack_trace stream_channel string_scanner term_glyph matcher]
- test_core 0.3.15 [analyzer async args boolean_selector collection coverage glob io meta package_config path pedantic pool source_map_stack_trace source_maps source_span stack_trace stream_channel vm_service yaml matcher test_api]
- typed_data 1.3.0 [collection]
- uni_links2_platform_interface 1.0.0+2 [plugin_platform_interface flutter]
- uni_links_web2 0.1.0+2 [uni_links2_platform_interface flutter flutter_web_plugins]
- url_launcher_linux 2.0.0 [flutter]
- url_launcher_macos 2.0.0 [flutter]
- url_launcher_platform_interface 2.0.2 [flutter plugin_platform_interface]
- url_launcher_web 2.0.0 [url_launcher_platform_interface meta flutter flutter_web_plugins]
- url_launcher_windows 2.0.0 [flutter]
- uuid 3.0.4 [crypto]
- vector_math 2.1.0
- vm_service 5.5.0 [meta]
- watcher 1.0.0 [async path pedantic]
- web_socket_channel 2.1.0 [async crypto stream_channel]
- webdriver 2.1.2 [archive matcher path stack_trace sync_http]
- webkit_inspection_protocol 1.0.0 [logging]
- win32 2.0.5 [ffi]
- xdg_directories 0.2.0 [meta path process]
- xml 5.1.0 [collection meta petitparser]

Hi @Andranjo97
Since the package is generating the link correctly there is not really anything we can fix (especially since it's caused by this one specific messaging backend in this specific share scenario).
This report is better suited for https://firebase.google.com/support/troubleshooter/contact
Thank you


Dc apps

@micmitch Apps:

Plate 2D, 2.5D
Resistive layer
Conversion to dipole

@thast:
-Cylinder 2D

@thast, @sgkang, @micmitch, can you give a 👍 if you are good with merging this in?

@lheagy, @sgkang  : I think I have found a solution for your scale problems! I will update DC_cylinder_2D with it tonight and if it works for you I can make it all the DCapps!
(Log secondary sensitivity is quite fun to look at)

:+1: can you share a picture??

Nice work @thast @micmitch !! I have few minor suggestions, but other than that I am happy with this pull request.
For DCResLayer2D and DCResLayer2_5D

[ ]  In set up figures notation for resistivities are: rho_1, rho_2, rho_3, but in the app they are not matching (rho_half, rho_target, rho_cyl)

[ ]  When "Sensitivity" is chosen, Pole-Dipole and Pole-Pole are not working (we can fix this later)

Just made those changes for you Seogi.
We are lacking sensitivity for the 2.5D apps since there is no fields object in the 2.5D class. This fields object is needed in the call to JTvec. We could display the 2D sensitivity in the 2.5D app but this might be misleading.

😃


🐛 [firebase_messaging] Should update minSdkVersion in gradle

Bug report
Describe the bug
When installing firebase_messaging, flutterfire configure should update gradle to support minSdkVersion for given version of firebase_messaging.
Steps to reproduce

Start new project, install firebase_core, add firebase_messaging.
run project
See error message in console
"The plugin firebase_messaging requires a higher Android SDK version"

Expected behavior
I expect flutterfire configure to update gradle as it as done for other packages (ie. firebase_crashlytics)
Flutter doctor
Run flutter doctor and paste the output below:
Click To Expand
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.3.5, on macOS 13.1 22C65 darwin-arm, locale en-GB)
[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 14.3.1)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2021.3)
[✓] Android Studio (version 2020.3)
[✓] VS Code (version 1.78.2)
[✓] Connected device (3 available)
[✓] HTTP Host Availability

• No issues found!

Flutter dependencies
Run flutter pub deps -- --style=compact and paste the output below:
Click To Expand
flutter pub deps -- --style=compact
Dart SDK 2.18.2
Flutter SDK 3.3.5
firebase_test 1.0.0+1

dependencies:
- bloc 8.1.2 [meta]
- firebase_core 2.13.1 [firebase_core_platform_interface firebase_core_web flutter meta]
- firebase_crashlytics 3.3.2 [firebase_core firebase_core_platform_interface firebase_crashlytics_platform_interface flutter stack_trace]
- firebase_messaging 14.6.2 [firebase_core firebase_core_platform_interface firebase_messaging_platform_interface firebase_messaging_web flutter meta]
- flutter 0.0.0 [characters collection material_color_utilities meta vector_math sky_engine]
- flutter_bloc 8.1.3 [bloc flutter provider]
- flutter_localizations 0.0.0 [flutter intl characters clock collection material_color_utilities meta path vector_math]
- intl 0.17.0 [clock path]

dev dependencies:
- bloc_test 9.1.3 [bloc diff_match_patch meta mocktail test]
- flutter_test 0.0.0 [flutter test_api path fake_async clock stack_trace vector_math async boolean_selector characters collection matcher material_color_utilities meta source_span stream_channel string_scanner term_glyph]

transitive dependencies:
- _fe_analyzer_shared 47.0.0 [meta]
- _flutterfire_internals 1.3.2 [collection firebase_core firebase_core_platform_interface flutter meta]
- analyzer 4.7.0 [_fe_analyzer_shared collection convert crypto glob meta package_config path pub_semver source_span watcher yaml]
- args 2.4.1
- async 2.9.0 [collection meta]
- boolean_selector 2.1.0 [source_span string_scanner]
- characters 1.2.1
- clock 1.1.1
- collection 1.16.0
- convert 3.1.1 [typed_data]
- coverage 1.6.3 [args logging package_config path source_maps stack_trace vm_service]
- crypto 3.0.2 [typed_data]
- diff_match_patch 0.4.1
- fake_async 1.3.1 [clock collection]
- file 6.1.4 [meta path]
- firebase_core_platform_interface 4.8.0 [collection flutter flutter_test meta plugin_platform_interface]
- firebase_core_web 2.5.0 [firebase_core_platform_interface flutter flutter_web_plugins js meta]
- firebase_crashlytics_platform_interface 3.6.2 [_flutterfire_internals collection firebase_core flutter meta plugin_platform_interface]
- firebase_messaging_platform_interface 4.5.2 [_flutterfire_internals firebase_core flutter meta plugin_platform_interface]
- firebase_messaging_web 3.5.2 [_flutterfire_internals firebase_core firebase_core_web firebase_messaging_platform_interface flutter flutter_web_plugins js meta]
- flutter_web_plugins 0.0.0 [flutter js characters collection material_color_utilities meta vector_math]
- frontend_server_client 2.1.3 [async path]
- glob 2.1.1 [async collection file path string_scanner]
- http_multi_server 3.2.1 [async]
- http_parser 4.0.2 [collection source_span string_scanner typed_data]
- io 1.0.4 [meta path string_scanner]
- js 0.6.4
- logging 1.1.1
- matcher 0.12.12 [stack_trace]
- material_color_utilities 0.1.5
- meta 1.8.0
- mime 1.0.4
- mocktail 0.3.0 [collection matcher test]
- nested 1.0.0 [flutter]
- node_preamble 2.0.2
- package_config 2.1.0 [path]
- path 1.8.2
- plugin_platform_interface 2.1.4 [meta]
- pool 1.5.1 [async stack_trace]
- provider 6.0.5 [collection flutter nested]
- pub_semver 2.1.4 [collection meta]
- shelf 1.4.1 [async collection http_parser path stack_trace stream_channel]
- shelf_packages_handler 3.0.2 [path shelf shelf_static]
- shelf_static 1.1.2 [convert http_parser mime path shelf]
- shelf_web_socket 1.0.4 [shelf stream_channel web_socket_channel]
- sky_engine 0.0.99
- source_map_stack_trace 2.1.1 [path source_maps stack_trace]
- source_maps 0.10.12 [source_span]
- source_span 1.9.0 [collection path term_glyph]
- stack_trace 1.10.0 [path]
- stream_channel 2.1.0 [async]
- string_scanner 1.1.1 [source_span]
- term_glyph 1.2.1
- test 1.21.4 [analyzer async boolean_selector collection coverage http_multi_server io js node_preamble package_config path pool shelf shelf_packages_handler shelf_static shelf_web_socket source_span stack_trace stream_channel typed_data web_socket_channel webkit_inspection_protocol yaml test_api test_core]
- test_api 0.4.12 [async boolean_selector collection meta source_span stack_trace stream_channel string_scanner term_glyph matcher]
- test_core 0.4.16 [analyzer async args boolean_selector collection coverage frontend_server_client glob io meta package_config path pool source_map_stack_trace source_maps source_span stack_trace stream_channel vm_service yaml matcher test_api]
- typed_data 1.3.2 [collection]
- vector_math 2.1.2
- vm_service 9.4.0
- watcher 1.0.2 [async path]
- web_socket_channel 2.4.0 [async crypto stream_channel]
- webkit_inspection_protocol 1.2.0 [logging]
- yaml 3.1.1 [collection source_span string_scanner]

@Hauglid flutterfire configure related issues need to be reported in tool's dedicated repo: https://github.com/invertase/flutterfire_cli/issues
Closing from here.


GitHub Actions Updates

If you haven't already, please read through our contributing guidelines before opening your PR
What is the purpose of this PR?
Closes #28.
How did you implement your changes
Split the Build and Test CI job into separate reusable workflows as in ark.
Set the Python version to the latest stable version (3.x).
Updated packages to work with new NumPy releases.
Cleaned up the names of various Workflows, Jobs and Steps to be less cluttered.
Added a badge table inspired by pypa/hatch.
Remaining issues
N/A

@camisowers The changes would have an effect on them yeah. Won't make a new release until all the other repos have PRs addressing it as well.


Support all float dtypes in F.spatial_transformer_sampler

This PR follows #4582, generalize F.spatial_transformer_sampler to support all float dtypes.

Jenkins, test this please.

Jenkins CI test (for commit 057d2500d01c5cc3185beb8456f2824edfe3fcc1, target branch master) failed with status FAILURE.
(For contributors, please wait until the reviewer confirms the details of the error.)

Jenkins CI test (for commit 16c218d31783be1a9a96c3da1b33322f7494418a, target branch master) succeeded!

Jenkins, test this please.

Jenkins, test this please.

Jenkins CI test (for commit 93e80a0290545845329cfab5afb2d4233ad1077c, target branch master) succeeded!


[Docs] a misspelling in "User Tutorial>Making your Hardware Accelerator TVM-ready with UMA"

UMA is a nice project for AI compilers, wish to see more tutorials committed.
Documentation Title & Type
Path: Docs>User Tutorial>Making your Hardware Accelerator TVM-ready with UMA
Title: Making your Hardware Accelerator TVM-ready with UMA
Type:  User Tutorial
Additions/Changes Requested
There seems to be a misspelling in "User Tutorial>Making your Hardware Accelerator TVM-ready with UMA"
"revist"  better corrected to be "revisit".

Feel free to send a PR to fix it :)

Hi @SStarver @Hzfengsy
I think we can close this issue if you agreed. :grinning:

Thanks for your fixes. Let's close it as completed

Feel free to send a PR to fix it :)
Happy to do so next time.


⚠ Jenkins Plugins Artifactory has degraded performance

In 2865b77, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1177 ms

Resolved: Jenkins Plugins Artifactory performance has improved in 7157547 after 31 minutes.


Changelog

It would be nice to list the changes on the library landing page, showing the updates been made so far.

Agreed, I've been making quite a few breaking changes lately (apologies to those who've updated the package). I can't make one right now (busy at the moment), but I will when I'm free on Sunday. Thanks @Qandil.

Added!


Implement the Month Module of the Morphir SDK

Is your feature request related to a problem? Please describe.
Morphir's SDK seeks to have parity with much of elm/core and should have full parity with elm/core Month.
Describe the solution you'd like
Implement the functions in elm/core Month and add tests. Over time we will add more functionality here, but this is a good start.
Describe alternatives you've considered
N/A
Additional context
N/A

Assign me this issue!


Made securityError more descriptive for OS X

Modified securityError to use SecCopyErrorMessageString on OS X for a more descriptive error message.

Thanks for your suggestion.
But tests failed because SecCopyErrorMessageString does not exist in iOS.
Please fix the compile error, for example enclosed in preprocessor macro.

Coverage decreased (-0.1%) to 73.26% when pulling 1d2a7953db953086113dd8dd86d362821bd49b93 on sirnacnud:error into 34386e521849b348bd666770056bc171d9a217f2 on kishikawakatsumi:master.

Awesome, thanks for your quick reply.


[Enhancement]: Extend teams user app add command with --name option

Currently we only accept the ID of the app, we should extend this so you can also use the name of the app.

Can I work on it?

Sure, all yours @nanddeepn!


IAM Role Support

Hello,
what do you think about IAM Role Support? I don't think it would be hard thing to do: http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/iam-roles-for-amazon-ec2.html. For us it would be extremely usefull since we do everything with IAM Roles instead of shipping credentials.

+1 . @i0rek let me know if you aren't actively working on a patch, I could whip up a PR for this.

@amoghe I am not working on it, feel free to take a stab at it! That would be great!

Okay, so pulling the credentials from the IAM role associated with the instance is trivial. Here are my thoughts so far:
Attaching an IAM role to the instance results in keys being made available via the metadata server. These can be fetched when the kinesis.NewClient populates the Auth struct (by looking at the env, and maybe also querying the server).
The part that is tricky to handle (and the part that I'd really like to handle) is where the keys are rotated, the kinesis client should also have its creds auto-magically updated. To do this we could either:

setup a goroutine that periodically polls and updates the keys in the Auth object. I don't particularly like this approach.
kinesis.Client.Do() can be made to inspect the response (after every request it makes), check for auth errors and maybe update its Auth and retry (once).

Option 2 seems simpler, so I'm inclined towards that. Thoughts?

When I thought about it I planned to do 1). Because as far as I know we even know when the token expires, right?!

When I thought about it I planned to do 1). Because as far as I know we even know when the token expires, right?!

You are correct (I had not done all my homework). So the question now is what do we do with the expiry time? Setup a goroutine that wakes up at/around that time to refresh them?

You are correct (I had not done all my homework). So the question now is what do we do with the expiry time? Setup a goroutine that wakes up at/around that time to refresh them?

You can check expiration time before each request and refresh if need to do this before request. No need to create goroutine.

You can check expiration time before each request and refresh if need to do this before request. No need to create goroutine.

Yes, we can perform the time comparison before every call to client.Do(), I was suggesting using the goroutine so that we could leave that codepath alone (and avoid unneccesary computation on what is essentially a hot codepath), and have another one update the Auth object when the time is right. Thoughts?

@amoghe the main problem, what goroutine is not controllable by developer and possible cases, where it is not need. Simple example: current implementation no need goroutine and still be used by many developers.

Thats fine. I'm okay with implementing it either way.
Just so that I understand the reasoning better - seems like you would prefer it if we did not spawn goroutines behind the scenes (esp since the user cannot "control" them) ?

Just so that I understand the reasoning better - seems like you would prefer it if we did not spawn goroutines behind the scenes (esp since the user cannot "control" them) ?

Yes, you are right!

Hi guys,
I just stumbled across this thread as I was going to fork the repo to add the ability to pass in the IAM token. I wanted to go for a more explicit and simple approach by changing  (https://github.com/sendgridlabs/go-kinesis/blob/master/kinesis.go#L50)
func New(access_key string, secret_key string, region Region) *Kinesis {

to
func New(auth *Auth, region Region) *Kinesis {

To me this seems more flexible and explicit. Wdyt?
Regarding the token rotation, do you really think this should be handled by the kinesis library? It would include speaking to the metadata service as well, including error handling and so on. To me this does not seem to match the focus of the kinesis lib and might be done by a different lib even? It probably would make sense if long running poll/subscribe methods would be in place but as far as I can see there's not such thing involved here.

To me this seems more flexible and explicit. Wdyt?

Looks good, need to see implementation :)

Regarding the token rotation, do you really think this should be handled by the kinesis library? It would include speaking to the metadata service as well, including error handling and so on. To me this does not seem to match the focus of the kinesis lib and might be done by a different lib even? It probably would make sense if long running poll/subscribe methods would be in place but as far as I can see there's not such thing involved here.

Maybe. I am not using such feature in AWS, what is why harder to me say the best way to solve this problem. We can split this stuff in separate pull request.

Please review https://github.com/sendgridlabs/go-kinesis/pull/19

@rubyphunk I think the first change you propose (to the signature of New) is reasonable, and can be made regardless.
However the fetching of keys from the metadata server by the kinesis lib emulates the behavior of other aws/cloud libs which attempt to fetch keys from various sources (including env and reading dotfiles). For this reason I don't think its unreasonable for it do to do this. Also, if you see #19 , you will
notice that is preserves the current (annoying, IMHO) behavior of being silent when it fails to get creds.

This (http://docs.aws.amazon.com/aws-sdk-php/guide/latest/credentials.html) documents all the ways one can plumb credentials to the SDK. The official AWS SDKs attempt to fetch credentials from various sources, for the ruby sdk (aws-sdk), the order of preference seems to be:

environment variables
dotfile (~/.aws/credentials)
metadata server (IAM credentials)

@rubyphunk with your proposed change to the constructor, you can override this "magical" creds fetching by providing your own Auth object (with the Expiry set to the zero-value of time.Time{}). This will give you the behavior you want, while allowing the lib to do more for other users. Thoughts?

@amoghe Yes makes sense. Cool. Being able to turn of magic behavior is always a good idea :)
One small addition (I'll comment on the PR #19 in a sec): If you add the X-Amz-Security-Token regardless of the state of c.Auth.Expiry we would not even need to pass in an empty Expiry which makes stuff a little more predictable.

@le0pard @amoghe See #20

Closed by https://github.com/sendgridlabs/go-kinesis/pull/19

Thank you very much for your work, this is great!


Mutants marked as escaped when, not?

Maybe I'm not fully getting how to read the logs here so, might just be misunderstanding the docs.
Humbug ran and generated a log with 61 escaped mutants – in my mind those are the mutants that the tests did not catch (ie. all tests ran green when they shouldn't have).
However I tried to redo the changes of 3 or 4 of them and when running PHPUnit I do get failing tests.
Example diff:
-        return $this->usesStages && !empty($stages);
+        return $this->usesStages || !empty($stages);

Now if I redo that very change myself and run phpunit it seems to be caught as expected:
$ phpunit --stop-on-failure
PHPUnit 4.4.1 by Sebastian Bergmann.

There was 1 failure:

1) Rocketeer\Traits\BashModules\FlowTest::testCanCheckIfUsesStages
Failed asserting that true is false.

Am I just misunderstanding how to read the logs or is this a bug?

It's a bug. One of the upcoming changes is switching to processing TAP output - a defined format that I really should have used on Day 1. At present, there is a hack and slash processing of the actual text output as above. In this case, since we introduced --stop-on-failure, there is no guarantee of a progress line (i.e. a series of .EFSI characters).

Ok will wait a little bit before officially integrating Humbug to my test process and will watch on this issue. Amazing tool nonetheless, really eager to fully take advantage of it

I've implemented this (stupidly simple obvious should-have-been-done on Day 1) feature ;) https://github.com/padraic/humbug/commit/a7841e786c2feb4afcf36d0b67ba6f978d754ba1
Let me know how it goes - the TAP should always provide a "not ok" line on early interrupt.

@Anahkiasen We're slowly rounding out those rough edges ;).

Just tested with a7841e786c2feb4afcf36d0b67ba6f978d754ba1 and I'm still getting the error above in my escaped mutants – actually I'm still getting the same number of escaped mutants. Do I need to enable an option or pass a specific option? Could the way PHPunit is configured affect the results?

Could it be the test that makes it fail is not run for that particular mutation? How does Humbug decides which tests to run for a given mutation?

Actually no I don't think that's related. One of the mutations marked as escaped is this:
14) \Humbug\Mutator\Boolean\LogicalNot
Diff on ???::???() in /Users/anahkiasen/Sites/rocketeers/rocketeer/src/Rocketeer/RocketeerServiceProvider.php:
--- Original
+++ New
@@ @@
 // Define DS
-if (!defined('DS')) {
+if (defined('DS')) {
     define('DS', DIRECTORY_SEPARATOR);
 }

If I do that change, literally all tests fail, so shouldn't matter

Reopening to investigate

@Anahkiasen In terms of test decisions, we use code coverage data (PHP not HTML/XML) which lists the tests run per line of code, so we can cross reference to the mutated line and determine test classes to execute. You can usually find a copy in /tmp after humbug completes the initial test run prior to mutation testing - it tends to be a large file making up quite a chunk of humbug's memory usage.

@Anahkiasen Would you mind checking if still an issue? The current master has replaced a lot of the test selection code with a new package I've written for PHPUnit. I'm hoping it resolves all of these omitted test/incorrect escape issues.

Would but I can't, cause of #69 :p

But I think it's an issue on my end, will try to see what it is

@Anahkiasen I see what you did there ;).

Same problem here. For example:
 \Humbug\Mutator\Arithmetic\Division
Diff on Pagination::calculateTotalPages() in /var/www/test/Pagination/Pagination.php:
--- Original
+++ New
@@ @@
     protected function calculateTotalPages($itemsPerPage, $totalItems) {
-        return ( int ) ceil( $totalItems / $itemsPerPage );
+        return ( int ) ceil( $totalItems * $itemsPerPage );
     }

Humbug tells me, that it was an escaped mutant. But if I change the code manually to "return ( int ) ceil( $totalItems * $itemsPerPage );" , phpunit throws multiple errors.

My problem is equal to #94
If I only run one suite, everything works as expected.


fix: let Windows CNS use the InClusterConfig

Reason for Change:
As of AKS 1.30, service account tokens refresh every ~1 hour when OIDC is enabled. They were previously valid for a year.
This setkubeconfigpath.ps1 script was at some point necessary on Windows to create a valid kubeconfig for CNS (and NPM and others), but based on my testing we don't need it today. It copies the token from the token file to create a custom kubeconfig from a template at startup and then we pass CNS that file via --kubeconfig.
The script runs at startup and never re-runs, so the token that exists at Pod start is the token CNS will try to use forever. Yearly token lifespans were long enough that no CNS Pod was ever up long enough to hit token expiration.
This becomes an issue with hourly token lifespans. An hour after Pod start, the token becomes invalid and CNS can no longer auth to the API server. For PodSubnet clusters, this permanently prevents CNS from being able to scale the IPAM pool and provide more Pod IPs.
Issue Fixed:

https://github.com/Azure/AKS/issues/4679
Requirements:

[ ] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests
[ ] relevant PR labels added

Notes:

/azp run Azure Container Networking PR

/azp run Azure Container Networking PR


replace window prompt/confirm with modals

there's maybe just one window modal left, and it's a confirmation for deleting a row.
there are likely other places where confirmation modals may be needed as well, though.


Clean out and start fresh landscape for UCF

Clean out all old LF AI projects.  Add Mapping and Data Visualization categories and initial set of projects.
Pre-submission checklist:
Please check each of these after submitting your pull request:

[ ] Are you only including a repo_url if your project is 100% open source? If so, you need to pick the single best GitHub repository for your project, not a GitHub organization.
[ ] Is your project closed source or, if it is open source, does your project have at least 300 GitHub stars?
[ ] Have you picked the single best (existing) category for your project?
[ ] Does it follow the other guidelines from the new entries section?
[ ] Have you included a URL for your SVG or added it to hosted_logos and referenced it there?
[ ] Does your logo clearly state the name of the project/product and follow the other logo guidelines?
[ ] Does your project/product name match the text on the logo?
[ ] Have you verified that the Crunchbase data for your organization is correct (including headquarters and LinkedIn)?
[ ] ~5 minutes after opening the pull request, the CNCF-Bot will post the URL for your staging server. Have you confirmed that it looks good to you and then added a comment to the PR saying "LGTM"?

If you create an account on slack.cncf.io and ping me I'm happy to help you debug your landscape issues.
https://app.netlify.com/sites/ucf-landscape/deploys/5d97dfe89eb1330008e7e583
On your latest commit, you need to remove the trailing / from https://github.com/mapserver/mapserver/


Updating travis to run coveralls

This PR should add a coveralls hook

Did this work? I can see that the runs passed, but I don't know what I should expect from coveralls to know that stats were successfully transferred.

I wasn't quite sure. The build shows up on coveralls, but I think it needs to get coverage on master to set a baseline.

So we should merge to see what happens?

:)


Frigate Proxy - Pass URL Path

I notice that Frigate Proxy does not pass any of the path along.
For example if I wanted to jump right to events I could use /events in Frigate but this does not work via the proxy.

I am having the same issue.
Linking to sub-pages in frigate through the proxy would be useful.
Or should I try using Nginx Proxy Manager to have more control?
(I am using the proxy addon to access frigate via HA with intended side-effect that only HA users can access Frigate.)

I would like this feature too please.  From my HA notifications about an even I would like to pass query string parameters too. (ex: /events?camera=front_door_cam&label=car)

+1 trying to figure this out too, would be great feature.

I would also be interested in this especially in being able to navigate to each camera directly to be able to view the live stream and check recordings.
I imagine something like this would work nicely:
tap_action:
  action: navigate
  navigation_path: /ccab4aaf_frigate-fa/cameras/front_door

Currently I can only navigate to the addon landing page.


Title: ACSS: Present VS Desired

Description:
At present for the expression
\frac{a+b}{c+d}
SRE with emacspeak produces the following sexp:
(exp
(text ((richness . 6)) "a plus b")
(pause . 350)
"divided by"
(pause . 350)
(text ((richness . 4)) "c plus d"))
Notice that the richness is 6 for the numerator and 4 for the
denominator.
I'd like  to change this to what AsTeR  produced (approximately) --
namely use the same richness value for both numerator and denominator.
Reason:

Numerator and Denominator are already distinguished by the richness
of 6, and highlighted by the phrase "divided by" being in the
normal voice.

Consistently setting richness to a new value as we enter each new
nesting level makes things like continuous fractions work well.
So here's what I'd like to produce:
(exp
(text ((richness . 6)) "a plus b")
(pause . 350)
"divided by"
(pause . 350)
(text ((richness . 6)) "c plus d"))

Now if I could figure out where to make the change --- hope you can
point the way.

The fraction rules are from Line 241 onwards.
The rate is translated to richness. Currently, we add a value for enumerator and subtract a value for the denominator. So if the denominator gets the same positive value you should get the desired effect.

Found it!
So now what do I need to do to build this thing?
I know we designed the rule syntax together, but 8+ years later, the
darn thing looks like APL:-)

Hit send before attaching build errors.
This is after installing closure and  closure compiler via npm.
make
Compiling Speech Rule Engine
/home/raman/sourceforge/zorkow/speech-rule-engine/src/common/cli.js:202: ERROR - [JSC_POSSIBLE_INEXISTENT_PROPERTY] Property on never defined on inter
inter.on('line', goog.bind(
^^
/home/raman/sourceforge/zorkow/speech-rule-engine/src/common/cli.js:209: ERROR - [JSC_POSSIBLE_INEXISTENT_PROPERTY] Property on never defined on inter
inter.on('close', goog.bind(function() {
^^
/home/raman/sourceforge/zorkow/speech-rule-engine/src/common/cli.js:293: ERROR - [JSC_POSSIBLE_INEXISTENT_PROPERTY] Property on never defined on ?
on('option:options', goog.bind(function() {
^^
/home/raman/sourceforge/zorkow/speech-rule-engine/src/common/debugger.js:78: ERROR - [JSC_POSSIBLE_INEXISTENT_PROPERTY] Property on never defined on sre.Debugger.stream_
this.stream_.on('error', goog.bind(
^^
/home/raman/sourceforge/zorkow/speech-rule-engine/src/common/debugger.js:84: ERROR - [JSC_POSSIBLE_INEXISTENT_PROPERTY] Property on never defined on sre.Debugger.stream_
this.stream_.on('finish', function() {
^^
5 error(s), 0 warning(s), 97.6% typed
make: *** [Makefile:159: /home/raman/sourceforge/zorkow/speech-rule-engine/lib/sre.js] Error 5
07:43:06 raman-glaptop speech-rule-engine $

Can't reproduce that. When you say

This is after installing closure and  closure compiler via npm.
have you done that separately, for example globally?

The best is to run in your speech-rule-engine directory:
npm install
make all

That should do the trick. Note that SRE is currently not using the latest closure as closure currently  can't compile in strict mode without throwing an error on its own code.


Input automatically rerenders immediately after deletion of leading month/day characters in datepicker

Describe the bug

Once a user has selected a full date, they have the option to edit their date selection via the keyboard. When the first of the two digits in a month or day is deleted via keyboard input, datepicker automatically reformats the input before the user has a chance to replace their deletion.
To Reproduce
Steps to reproduce the behavior:

Go to https://auro.alaskaair.com/components/auro/datepicker.
Set date to '09/18/2022'
Set cursor after the '1'.
Press backspace/delete to delete the character.
See that the '1' was automatically replaced with a '0'.

Expected behavior

The datepicker input should not automatically reformat and allow the user to replace the deleted digit.
Additional context

This is an issue with Cleave.js and will take a deeper dive to fix.

This is tricky and I fear a rabbit hole. Cleave is doing exactly what Cleave is supposed to do, so for the most part this is expected behavior.
IMHO, I am getting closer and closer to the idea that if a user puts the cursor back into the input once there is a value, it should simply clear the value and the user can start over.
It's a date, so this is not complicated data. Also, this UX is bound to a calendar where the assumption is that most of the users will use that to change the date versus editing the current value.

Adding this back to refinement so that we discuss this in the next session.

Metting to discuss development options and the desired UX has been scheduled.

The team discussed this and we decided to punt on this issue. It's edge cases that cause this scenario and not worth a deep-dive at this time.


Deploy using a single binary

This is part of oCIS Extensions, as a single binary is about to bundle the multiply microservice extensions, and providing good configuration conventions.

[ ] https://github.com/owncloud/ocis/issues/2
[ ] https://github.com/owncloud/ocis-webdav/issues/1
[ ] https://github.com/owncloud/ocis-phoenix/issues/3
[ ] https://github.com/owncloud/ocis-ocs/issues/1

ocis-simple is intended to show how to build extensions. As that it will run the full stack, but a self contained set of services that serve as an example for how to write extensions with front and backend parts:

hello contains the example extension, including a protobuf generated api and a phoenix extension/app?
phoenix server the web framework. hello adds a ? to it
konnectd as the openid connect provider for authentication
devldap as the user backend for konnectd, comes with a few demo users

It will not contain reva or the graph, yet. We will add that to the ocis full sever.

Why is this issue closed again? There's a PR that can make use of this issue to track. Also, it's part of the backlog. #79


new branch for panel

@michaelweinold

@michaelweinold
This is the most up to date version now. Sorry for the confusion.
Give it a try and let us know if anything doesn't work for you.


Documentation on feature "ASR Only Per Rule Exclusion" in Attack Surface Reduction is missing in the "Learn more" page

This link "Learn more" doesn't have any information on the feature "ASR Only Per Rule Exclusion".  I searched the whole page but it doesn't mention it at all. It needs to describe how it works and how conflicts with "Attack Surface Reduction Only Exclusions" feature and how to resolve those conflicts.

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

ID: 96cedf2c-e6fa-bbfb-61f0-ab4bcaae1479
Version Independent ID: 45ca9ffb-55e9-7721-3433-017a513a59be
Content: Use attack surface reduction rules to prevent malware infection
Content Source: microsoft-365/security/defender-endpoint/attack-surface-reduction.md
Service: microsoft-365-security
Sub-service: mde
GitHub Login: @Dansimp
Microsoft Alias: dansimp

@Dansimp Please help us in resolving this issue. Thanks

@Dansimp  - can you please take a look?

any updates on this?

Pending input from the feature team.

Status:
Fixed the following:
REMOVED - Removed outdated statement:
{ but you can't specify which rules the exclusions apply to }
ADDED - Added link to location where per-rule exclusions are documented, as follows:
{ For information about per-rule exclusions, see: Configure ASR rules per-rule exclusions. }
Still need information from product team about [ conflicts with "Attack Surface Reduction Only Exclusions" feature and how to resolve those conflicts. ] to resolve this issue.


test: implement codec registration tests for ibc core and lightclients

Description
ref: #4747

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[ ] Targeted PR against correct branch (see CONTRIBUTING.md).
[ ] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[ ] Code follows the module structure standards and Go style guide.
[ ] Wrote unit and integration tests.
[ ] Updated relevant documentation (docs/) or specification (x/<module>/spec/).
[ ] Added relevant godoc comments.
[ ] Provide a commit message to be used for the changelog entry in the PR description for review.
[ ] Re-reviewed Files changed in the Github PR explorer.
[ ] Review Codecov Report in the comment section below once CI passes.

Codecov Report

Merging #4757 (295c2ca) into main (e443a88) will increase coverage by 0.25%.
Report is 3 commits behind head on main.
The diff coverage is n/a.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #4757      +/-   ##
==========================================
+ Coverage   79.49%   79.75%   +0.25%
==========================================
  Files         189      189
  Lines       13285    13285
==========================================
+ Hits        10561    10595      +34
+ Misses       2296     2262      -34
  Partials      428      428

see 1 file with indirect coverage changes

Nice! I wonder if there are some duplicate tests that can be removed now. Curious if this covers testing for UnpackInterfaces func needing to be required

Indirectly I think it kind of covers it. But its not really explicit. I think its probably worth keeping the existing marshal/unmarshal tests for Any unpacking for now until it can be further worked out.


Reduce datastore debug logging

This reduces a lot of the repetitive and excessively verbose log statements.

https://ocd.appscale.com:8080/job/Daily Build/2462/


1.20.2

What is missing to merge this branch?

There are three things I know of:

Updating the behavior of ConnectionManager#getOnlinePlayers
Reentering the configuration phase
New chunk batching

I am going to merge before new chunk batching is done, it is not a requirement for the client. On top of those other bits, I would like to try using it a bit in a real world case. I am trying to add branch publishing so that I (and others) can try it before committing to merging it.

Snapshots for this branch (and other PR-ed branches) can be found here: https://repo1.maven.org/maven2/dev/hollowcube/minestom-ce-snapshots/

I updated my project to Minestom 1.20.2 and it sparkled with new colors :D

I have run this on my own server and it appears to be working as expected. I need to do some cleanup in this branch, but it seems functional.

When a client receives a PLAY packet during CONFIGURATION, the client throws this error. I would really like to have such a check on the server side, and the server would throw an error when trying to send a PLAY packet

I'm not sure it's super trivial at the moment, but I'll look into it. I agree the current behavior is pretty bad.

This will be superseded by #92. Leaving open for the moment so I can see the diff between the two of them, but future changes should be submitted to that PR instead (this one will be closed later).


Feature/tiling statement

updated tiling option in soil drainage to show what is selected when tiling is active and show a statement for what the new drainage is while maintaining the calculations.

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.

if i choose nc -> somewhat poorly drained -> yes to tiling it takes the drainage class down to poorly drained when it should go to moderately well drained

if i chose ny selecting tiling doesn't change anything and says my improved drainage class is the same as unimproved drainage class

in midwest if i select tile drainage it doesn't improve my drainage class it stays the same. unselecting reduces the selected chip

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.

if i chose ny selecting tiling doesn't change anything and says my improved drainage class is the same as unimproved drainage class

I'm also having same issue here. When I select NC -> Drainage Class: Very poorly drained -> Tile Drainage: true -> And it shows: Your improved drainage class is Very poorly drained.
Sometime it works and update drainage class to next level, but most time it just shows the same, especially first time enter the page.

if i chose ny selecting tiling doesn't change anything and says my improved drainage class is the same as unimproved drainage class

I'm also having same issue here. When I select NC -> Drainage Class: Very poorly drained -> Tile Drainage: true -> And it shows: Your improved drainage class is Very poorly drained.
Sometime it works and update drainage class to next level, but most time it just shows the same, especially first time enter the page.

In the updateDrainageClass function (line ~66 RenderDrainageClasses) i intended to move setUpdateTilingCheck into the if statement and also left that state update outside of the if.  This is updated now.

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.


477 how to handle xtandem hidden parameters that have an impact on final results

Hi!
It now adds ",Acetyl(N-term)" when "protein, quick acetyl	yes", and ",Pyrolidone(N-term)" when "protein, quick pyrolidone	yes" in the parameter file, if the search engine is X!Tandem.
I also changed the test result.
It is not clean because the modification format is not the same as the modifications automatically parsed ("15.99491@M"), but I am not sure what would correspond to "Pyrolidone N-ter" in this fomat. I have to look for it.
There was a change made to the vscode/settings.json, I changed it back. I think. Not sure. Sorry about that. Please let me know if I messed this bit up.

I'll quickly add information in the docs to explain that we do this.

Looks good:) So what does 15.99491@M mean?

This would be a way to say "methionine oxidation" with the mass of the modification and the residue.


netlrts hangs in SMP mode

Original issue: https://charm.cs.illinois.edu/redmine/issues/299

Testing megatest, jacobi2d (or any other program) for netlrts-linux[-x86_64] results in a hang at exit.

Original date: 2013-10-07 02:53:50

Bug fixed by change in LrtsExit call for netlrts based layer to do what they are supposed to do (not what they used to do in non-LRTS version).

Original date: 2013-10-23 04:36:14

After making use of more of LRTS API, a new bug manifests as a hang in multicast test.


Cannot import Library build package created for React tsx project in some other React tsx project

Describe the bug
I have created and uploaded the lib build as an npm package for react tsx project, but on installing the package in other project, it gives error as below "
 [plugin: vite:dep-scan] Failed to resolve entry for package "@reporting-ui-component". The package may have incorrect main/module/exports specified in its package.json.

Reproduction
Steps Done:

- Package.json for library project

  "main": "./dist/reporting-ui-component.umd.js",
  "module": "./dist/reporting-ui-component.es.js",
  "exports": {
    ".": {
      "import": "./dist/reporting-ui-component.es.js",
      "require": "./dist/reporting-ui-component.umd.js"
    }
  },

1.1 vite.config for library project

return defineConfig({
      plugins: [reactRefresh()],
      resolve: {
        alias: readAliasFromTsConfig(),
      },
      build: {
        lib: {
          entry: path.resolve(__dirname, 'src/main.tsx'),
          name: 'report-ui-component'
        },
        rollupOptions: {
          external: ['react'],
          output: {
            // Provide global variables to use in the UMD build
            // for externalized deps
            globals: {
              react: 'React',
            },
          },
        },
        minify: false,
        sourcemap: false,

1.2 main.tsx file
/* eslint-disable simple-import-sort/imports */
import { ApolloClient, InMemoryCache } from '@apollo/client';
import { ApolloProvider } from '@apollo/react-hooks';
import React from 'react';
import ReactDOM from 'react-dom';
import './index.scss';
import config from './local/local-config.json';
import Root from './root';

// Retrieve the authorization token from local storage.
const token = config.authToken;

const client = new ApolloClient({
  cache: new InMemoryCache(),
  uri: 'https://someUrl.com/graphql',
  headers: {
    authorization: token ? `Bearer ${token}` : '',
    'x-api-key': config.apiKey,
  },
});

const Main = () => (
  <ApolloProvider client={client}>
    <Root />
  </ApolloProvider>
);

ReactDOM.render(<Main />, document.getElementById('root'));
export default Main;

**_Output for the above library build in dist folder **

 | dist
 |--- reporting-ui-component.es.js
 |--- reporting-ui-component.umd.js
 |---  style.css

Created a npm package an published it as an artifactory with name - @reporting-ui-component
3.1 On installing the package in some other repo, the same dist structure is downloaded from npm i command

Now I am planning to install the library in other project, but it gives an error
As of now I am importing as below  in other project

import Main from '@org-Name/package-name'

System Info
(Link which I referred to create a library build)
Output of npx envinfo --system --npmPackages vite,@vitejs/plugin-vue --binaries --browsers:
  System:
    OS: Windows 10 10.0.19043
    CPU: (8) x64 Intel(R) Core(TM) i7-8565U CPU @ 1.80GHz
    Memory: 4.70 GB / 15.81 GB
  Binaries:
    Node: 12.18.4 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.10 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 6.14.6 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Spartan (44.19041.964.0), Chromium (91.0.864.48)
    Internet Explorer: 11.0.19041.1
  npmPackages:
    vite: ^2.1.0 => 2.3.3

Used package manager:  yarn
Logs

> vite --debug

  vite:config bundled config file loaded in 190ms +0ms
  vite:config using resolved config: {
  vite:config   plugins: [
  vite:config     'vite:pre-alias',
  vite:config     'alias',
  vite:config     'react-refresh',
  vite:config     'vite:dynamic-import-polyfill',
  vite:config     'vite:resolve',
  vite:config     'vite:html',
  vite:config     'vite:css',
  vite:config     'vite:esbuild',
  vite:config     'vite:json',
  vite:config     'vite:wasm',
  vite:config     'vite:worker',
  vite:config     'vite:asset',
  vite:config     'vite:define',
  vite:config     'vite:css-post',
  vite:config     'vite:client-inject',
  vite:config     'vite:import-analysis'
  vite:config   ],
  vite:config   server: {
  vite:config     fsServe: {
  vite:config       root: 'C:/Aagam Doshi/Aagam - Rhydon/Reports Base',
  vite:config       strict: false
  vite:config     }
  vite:config   },
  vite:config   configFile: 'C:/Aagam Doshi/Aagam - Rhydon/Reports Base/vite.config.ts',
  vite:config   configFileDependencies: [ 'vite.config.ts' ],
  vite:config   inlineConfig: {
  vite:config     root: undefined,
  vite:config     base: undefined,
  vite:config     mode: undefined,
  vite:config     configFile: undefined,
  vite:config     logLevel: undefined,
  vite:config     clearScreen: undefined,
  vite:config     server: { fsServe: [Object] }
  vite:config   },
  vite:config   root: 'C:/Aagam Doshi/Aagam - Rhydon/Reports Base',
  vite:config   base: '/',
  vite:config   resolve: { dedupe: undefined, alias: [ [Object] ] },
  vite:config   publicDir: 'C:\\Aagam Doshi\\Aagam - Rhydon\\Reports Base\\public',
  vite:config   cacheDir: 'C:\\Aagam Doshi\\Aagam - Rhydon\\Reports Base\\node_modules\\.vite',
  vite:config   command: 'serve',
  vite:config   mode: 'development',
  vite:config   isProduction: false,
  vite:config   build: {
  vite:config     target: [ 'es2019', 'edge88', 'firefox78', 'chrome87', 'safari13.1' ],
  vite:config     polyfillDynamicImport: false,
  vite:config     outDir: 'dist',
  vite:config     assetsDir: 'assets',
  vite:config     assetsInlineLimit: 4096,
  vite:config     cssCodeSplit: true,
  vite:config     sourcemap: false,
  vite:config     rollupOptions: {},
  vite:config     commonjsOptions: { include: [Array], extensions: [Array] },
  vite:config     minify: 'terser',
  vite:config     terserOptions: {},
  vite:config     cleanCssOptions: {},
  vite:config     write: true,
  vite:config     emptyOutDir: null,
  vite:config     manifest: false,
  vite:config     lib: false,
  vite:config     ssr: false,
  vite:config     ssrManifest: false,
  vite:config     brotliSize: true,
  vite:config     chunkSizeWarningLimit: 500,
  vite:config     watch: null
  vite:config   },
  vite:config   env: { BASE_URL: '/', MODE: 'development', DEV: true, PROD: false },
  vite:config   assetsInclude: [Function: assetsInclude],
  vite:config   logger: {
  vite:config     hasWarned: false,
  vite:config     info: [Function: info],
  vite:config     warn: [Function: warn],
  vite:config     warnOnce: [Function: warnOnce],
  vite:config     error: [Function: error],
  vite:config     clearScreen: [Function: clearScreen]
  vite:config   },
  vite:config   createResolver: [Function: createResolver],
  vite:config   optimizeDeps: { esbuildOptions: { keepNames: undefined } }
  vite:config } +20ms
  vite:deps Hash is consistent. Skipping. Use --force to override. +0ms

  vite v2.3.7 dev server running at:

  > Local: http://localhost:3000/
  > Network: use `--host` to expose

  ready in 593ms.

  vite:time 1ms   / +0ms
  vite:spa-fallback Rewriting GET / to /index.html +0ms
  vite:time 49ms  /index.html +118ms
  vite:resolve 6ms   /Aagam Doshi/Aagam - Rhydon/Reports Base/node_modules/vite/dist/client/client -> C:/Aagam Doshi/Aagam - Rhydon/Reports Base/node_modules/vite/dist/client/client.js +0ms
  vite:resolve 8ms   /@vite/client -> C:/Aagam Doshi/Aagam - Rhydon/Reports Base/node_modules/vite/dist/client/client.js +1ms
  vite:load 4ms   [fs] /@vite/client +0ms
  vite:resolve 2ms   ./env -> C:/Aagam Doshi/Aagam - Rhydon/Reports Base/node_modules/vite/dist/client/env.js +40ms
  vite:resolve 1ms   /node_modules/vite/dist/client/env.js -> C:/Aagam Doshi/Aagam - Rhydon/Reports Base/node_modules/vite/dist/client/env.js +2ms
  vite:transform 25ms  /@vite/client +0ms
  vite:time 58ms  /@vite/client +102ms
  vite:resolve 5ms   /dist/style.css?direct -> null +14ms
  vite:spa-fallback Not rewriting GET /dist/style.css because the path includes a dot (.) character. +158ms
  vite:time 12ms  /dist/style.css +15ms
  vite:resolve 1ms   /src/main.tsx -> C:/Aagam Doshi/Aagam - Rhydon/Reports Base/src/main.tsx +30ms
  vite:load 4ms   [fs] /src/main.tsx +80ms
  vite:load 0ms   [plugin] /@react-refresh +749ms
  vite:rewrite 5ms   [no imports] /@react-refresh +0ms
  vite:transform 7ms   /@react-refresh +803ms
  vite:time 10ms  /@react-refresh +788ms
  vite:resolve 0ms   react -> C:/Aagam Doshi/Aagam - Rhydon/Reports Base/node_modules/.vite/react.js?v=4236347e&es-interop +776ms
  vite:resolve 1ms   /node_modules/.vite/react.js?v=4236347e&es-interop -> C:/Aagam Doshi/Aagam - Rhydon/Reports Base/node_modules/.vite/react.js?v=4236347e&es-interop +2ms
  vite:resolve 0ms   react-dom -> C:/Aagam Doshi/Aagam - Rhydon/Reports Base/node_modules/.vite/react-dom.js?v=4236347e&es-interop +31ms
  vite:resolve 1ms   /node_modules/.vite/react-dom.js?v=4236347e&es-interop -> C:/Aagam Doshi/Aagam - Rhydon/Reports Base/node_modules/.vite/react-dom.js?v=4236347e&es-interop +12ms
  vite:resolve 1ms   ./root -> C:/Aagam Doshi/Aagam - Rhydon/Reports Base/src/root.tsx +6ms
  vite:resolve 0ms   /src/root.tsx -> C:/Aagam Doshi/Aagam - Rhydon/Reports Base/src/root.tsx +16ms
  vite:resolve 0ms   /node_modules/.vite/react.js?v=4236347e -> C:/Aagam Doshi/Aagam - Rhydon/Reports Base/node_modules/.vite/react.js?v=4236347e +1ms
  vite:resolve 0ms   /node_modules/.vite/react-dom.js?v=4236347e -> C:/Aagam Doshi/Aagam - Rhydon/Reports Base/node_modules/.vite/react-dom.js?v=4236347e +2ms
  vite:transform 840ms /src/main.tsx +84ms
  vite:time 849ms /src/main.tsx +84ms
  vite:load 79ms  [fs] /node_modules/vite/dist/client/env.js +95ms
  vite:rewrite 0ms   [no imports] node_modules\vite\dist\client\env.js +91ms
  vite:transform 2ms   /node_modules/vite/dist/client/env.js +8ms
  vite:time 87ms  /node_modules/vite/dist/client/env.js +8ms
  vite:load 1ms   [fs] /src/root.tsx +26ms
11:16:47 PM [vite] Internal server error: Failed to resolve entry for package "@ci-technology/reporting-ui-component". The package may have incorrect main/module/exports specified in its package.json.
  Plugin: vite:import-analysis
  File: C:/Aagam Doshi/Aagam - Rhydon/Reports Base/src/root.tsx
      at resolvePackageEntry (C:\Aagam Doshi\Aagam - Rhydon\Reports Base\node_modules\vite\dist\node\chunks\dep-bc228bbb.js:32615:15)
      at tryNodeResolve (C:\Aagam Doshi\Aagam - Rhydon\Reports Base\node_modules\vite\dist\node\chunks\dep-bc228bbb.js:32434:11)
      at Context.resolveId (C:\Aagam Doshi\Aagam - Rhydon\Reports Base\node_modules\vite\dist\node\chunks\dep-bc228bbb.js:32317:28)
      at Object.resolveId (C:\Aagam Doshi\Aagam - Rhydon\Reports Base\node_modules\vite\dist\node\chunks\dep-bc228bbb.js:44708:55)
      at processTicksAndRejections (internal/process/task_queues.js:97:5)
      at async TransformContext.resolve (C:\Aagam Doshi\Aagam - Rhydon\Reports Base\node_modules\vite\dist\node\chunks\dep-bc228bbb.js:44510:23)
      at async normalizeUrl (C:\Aagam Doshi\Aagam - Rhydon\Reports Base\node_modules\vite\dist\node\chunks\dep-bc228bbb.js:69449:34)
      at async TransformContext.transform (C:\Aagam Doshi\Aagam - Rhydon\Reports Base\node_modules\vite\dist\node\chunks\dep-bc228bbb.js:69584:57)
      at async Object.transform (C:\Aagam Doshi\Aagam - Rhydon\Reports Base\node_modules\vite\dist\node\chunks\dep-bc228bbb.js:44765:30)
      at async transformRequest (C:\Aagam Doshi\Aagam - Rhydon\Reports Base\node_modules\vite\dist\node\chunks\dep-bc228bbb.js:59029:29)
  vite:time 121ms /src/root.tsx +138ms
  vite:time 8ms   /src/favicon.svg +924ms

Before submitting the issue, please make sure you do the following

[x] Read the Contributing Guidelines.
[x] Read the docs.
[x] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[x] Provide a description in this issue that describes the bug.
[x] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/vue-next instead.
[x] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.

Probably related to your use of resolve.alias. What Vite plugins is your application using?

Changing lib output formats worked for me:

Closing due to lack of response


add metadata for hex.pm

Ship it =)

I'll wait with merge until I can make sure it works with mix deps.compile.


Fix socket performance regression on Linux and OSX

In c5a3ad4d the socket code was changed and was benchmarked to be significantly better. Than benchmark was only run on Windows and the changes actually made things worse on Linux and OSX.
These changes fix the regression in Linux and OSX.
Note that performance on Windows is significantly improved while on Linux it's neutral to marginally worse. One thing to keep in mind is that these changes fix the issue where messages could get stuck in a buffer until a future read where the last two bytes read were \r\n.
If in reality there are frequently messages trapped in the buffer then these changes are a net positive. If that's rare then likely these changes are a net negative.
Remember that the benchmark is measuring the total time taken to receive and process all of the messages and not the time taken to process a message after having received it.
Benchmarks:
Windows

                                                     Benchmarks, repeat=5, number=5
┌─────────────────────────────────────────────────┬─────────┬─────────┬─────────┬─────────────────┬─────────────────┬─────────────────┐
│                                       Benchmark │ Min     │ Max     │ Mean    │ Min (+)         │ Max (+)         │ Mean (+)        │
├─────────────────────────────────────────────────┼─────────┼─────────┼─────────┼─────────────────┼─────────────────┼─────────────────┤
| Original Client Code vs socket.makefile version │ 73.695  │ 76.014  │ 75.057  │ 45.791 (1.6x)   │ 46.994 (1.6x)   │ 46.509 (1.6x)   │
└─────────────────────────────────────────────────┴─────────┴─────────┴─────────┴─────────────────┴─────────────────┴─────────────────┘

Linux
                                                    Benchmarks, repeat=5, number=5
┌─────────────────────────────────────────────────┬─────────┬─────────┬─────────┬─────────────────┬─────────────────┬─────────────────┐
│                                       Benchmark │ Min     │ Max     │ Mean    │ Min (+)         │ Max (+)         │ Mean (+)        │
├─────────────────────────────────────────────────┼─────────┼─────────┼─────────┼─────────────────┼─────────────────┼─────────────────┤
│ Original Client Code vs socket.makefile version │ 11.542  │ 12.429  │ 11.746  │ 11.786 (-1.0x)  │ 12.769 (-1.0x)  │ 11.995 (-1.0x)  │
└─────────────────────────────────────────────────┴─────────┴─────────┴─────────┴─────────────────┴─────────────────┴─────────────────┘

Adding to the above I see 1.4x+ improvement by simply increasing the buffer to 8192 on the original client

Increasing the buffer size will make it more likely that there's
less-than-one-full-buffers worth of data to read and increase the chance
that the last two characters read will be CRLF.
My gut feeling is that in all likelihood during real world usage the
original code will be faster on average as long as the buffer is set
appropriately, as on a low latency connection I believe a single message
will be read in totality much more often than not.
It will have the chance of spikes of latency for individual messages if
they ever get stuck in the buffer as described, but again my suspicion is
that this would actually be rare.
I think you should not merge this and revert the other commit.
On Fri, 15 Sept 2023, 14:58 Liam, @.***> wrote:

Adding to the above I see 1.4x+ improvement by simply increasing the
buffer to 8192 on the original client
—
Reply to this email directly, view it on GitHub
https://github.com/betcode-org/betfair/pull/540#issuecomment-1721241942,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJDC6RWXZQDQU3BPB4KJJ3X2RGIFANCNFSM6AAAAAA4Y3Z2HQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

Good point, started a thread on slack

Just did some real world testing on this, when subscribed to all racing markets and all data I see no improvement in latency comparing this branch to master with roughly only 4% of updates greater than 1024 bytes.
Interestingly when a large update comes through (> 4000 bytes) master is quicker.


Use a query parameter for AMP pages instead of new route

Per consensus in a mixed-application scenario, we'll use the amp query parameter convention.
This has a nice side effect of reducing duplication! 😄

I saw that twitter also tries to route to ?amp=1 so this makes sense.

/cc @sebastianbenz


updated name-mangler (3.3.4)

https://github.com/caskroom/homebrew-cask/issues/17098

Merged as bcb6626ba1c1de1013838d35a839c120672c21c6.


support Sphinx .. ipython:: python blocks

See: https://ipython.readthedocs.io/en/stable/sphinxext.html#writing-pure-python-code
The code syntax is equivalent to .. code-block:: python, so the change is trivial.

could you please add a simple test -- thanks!

I had a change of heart, the original patch was good enough -- thanks for the PR! 🎉

My pleasure


Systemd Service Should Be Type "forking"

Description
On my laptop (specs below), betterlockscreen will be be bale to lock properly if set to be type=simple. The reason is because the service will detect sleep or suspend event, then execute lock, then exit since execution is successful, and kill the lock program altogether. Under forking, the service file will execute lock program and exit without killing the lock, keeping it alive until user intervention (password input) clears the forked process.
I got the idea to change to forking from this page of the arch wiki.
Hopefully I made a sensible change in the right place.
How Has This Been Tested?
Close lid, locking with key binding.
Specifications
Thinkpad W550s
i3wm
Arch Linux
Checklist:

[x ] I have performed a self-review of my own code/checked that ShellCheck succeeds
[ x] I have made corresponding changes to the documentation (if applicable)

This also fixed it for me running Arch Linux with bspwm.
However on an older arch install I recall using type simple.
It had been forking before but has changed: https://github.com/betterlockscreen/betterlockscreen/issues/277
The machine I am on just recently got installed and I noticed that systemctl suspend call requires root permission.
This possibly has been changed recently and thus requiring type forking now for betterlockscreen service to work.

@denppa Did you check if you have polkit like @Shourai suggested that it solved it?
I'm very hesitant especially as I maintain this repo only because I haven't found someone taking over and somehow blind because i switched to wayland so have no way of testing.
We tried that in the past and the feedback was quite bad/broke for many more people: https://github.com/betterlockscreen/betterlockscreen/issues/277

@denppa Did you check if you have polkit like @Shourai suggested that it solved it?
I'm very hesitant especially as I maintain this repo only because I haven't found someone taking over and somehow blind because i switched to wayland so have no way of testing.
We tried that in the past and the feedback was quite bad/broke for many more people: #277

I missed what @Shourai  edited, but since I  no longer use arch, I can't experiment the behavior on arch anymore. Closing the PR for now.


Add license

BSD 2-clause with copyright to "Lund University and connect contributors"
Contributors are listed

@emenlu any thoughts on the copyright stuff?

Current coverage is 42.16% (diff: 100%)

Merging #56 into master will not change coverage

@@             master        #56   diff @@
==========================================
  Files            15         15
  Lines          1046       1046
  Methods           0          0
  Messages          0          0
  Branches        116        116
==========================================
  Hits            441        441
  Misses          553        553
  Partials         52         52

Powered by Codecov. Last update 206d005...138e14d

Yes, I'm not sure about the copyright. We could write Lund University and connect contributors. Why do you want to distinguish between contributors and authors?

It's a human who writes code but it could be an organisation that employs that code writer. I.e. people contribute but are not always the authors (from a copyright point of view). Does that make sense?
We could probably just mash them together have something like you suggested -- I think it's just a matter of technicality.

@emenlu I've updated the files; any comments?

@smetz In this case contributors have copyright so I suggest that you change to "This file lists contributors". We could also add date of first contribution to the format. Then you could go back in history if you for some reason would like to do that.
I also think you should add Alex since he was involved in the project as a whole and not only the fronted development.
Remove the following from the CONTRIBUTORS file:
If a name is added to this file, consider adding
it to the AUTHORS file - either the name itself

Nice catches! When did you guys start?

Same day as you and Alex :-)

Hmm, around 5/11/15 or was it in october?

Format: Given Family <email> <date>
sorted by given name

Alexander Cobleigh<EMAIL_ADDRESS><2015-10-05>
Axel Smeets<EMAIL_ADDRESS><2015-10-05>
Emelie Engström<EMAIL_ADDRESS><2015-10-01>
Erik Andersson<EMAIL_ADDRESS><2016-09-05>
Kai Petersen<EMAIL_ADDRESS><2015-10-01>
Nauman Ali<EMAIL_ADDRESS><2015-10-01>
Tim Borglund<EMAIL_ADDRESS><2016-09-05>
Jamie Caprani<EMAIL_ADDRESS><2016-10-28>

sorted by join date -- tie break with given

Emelie Engström<EMAIL_ADDRESS><2015-10-01>
Kai Petersen<EMAIL_ADDRESS><2015-10-01>
Nauman Ali<EMAIL_ADDRESS><2015-10-01>
Alexander Cobleigh<EMAIL_ADDRESS><2015-10-05>
Axel Smeets<EMAIL_ADDRESS><2015-10-05>
Erik Andersson<EMAIL_ADDRESS><2016-09-05>
Tim Borglund<EMAIL_ADDRESS><2016-09-05>
Jamie Caprani<EMAIL_ADDRESS><2016-10-28>

I think it makes more sense to sort by name, any thoughts?

I agree

Ok, then we're live!

 Set a LICENSE file


fix: box sizing mixin

Describe pull-request
Adding box-sizing mixin and adding it to component that do not have that rule.
Solving issue
Fixes:  Issue with Footer
How to test

Go to Netlify link
Check mainly footer component, but also others if they are displayed correctly

Something is off with the Native button with Icon. Not sure if it was this PR that introduces it.

Something is off with the Native button with Icon. Not sure if it was this PR that introduces it.

Seems like the sdds-icon has the wrong margin-left, should be 28px for lg, 20px for md and 24 for sm. Should we fix it in this or in another PR?

@mJarsater - I will try to fix it in this one, both the issues. Thank you for good 👀


grafx2: rename output binary

Description of changes
The grafx2.desktop file that gets installed under /share/applications references grafx2, but the package outputs grafx2-sdl which results in a broken desktop entry. This change renames the binary post-install in order to fix that.

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Are you still interested in getting this done?

pinging @trofi for review


Update to the statement "invalidates the single VM SLA"?

Hi,
Now that we offer SLA's on VM's with Standard SSD / HDD storage it might be good to update this statement in section Cost conscious solution with Azure premium storage:

Another aspect to reduce costs in such environments can be the usage of Azure Standard SSD storage. Though a choice which invalidates the single VM SLA for Azure Virtual Machines.

"Reduces" would be a better fit.
[Enter feedback here]

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

ID: 13ecd5d2-9d58-1d74-8e27-22754055120c
Version Independent ID: 3e93d9d3-5341-0e3c-a15c-85906fc0b5b3
Content: SAP HANA Azure virtual machine storage configurations - Azure Virtual Machines
Content Source: articles/virtual-machines/workloads/sap/hana-vm-operations-storage.md
Service: virtual-machines-linux
Sub-service: workloads
GitHub Login: @msjuergent
Microsoft Alias: juergent

@dohughes-msft
Thanks for the feedback! I have assigned the issue to content author to check and update the document as appropriate.

@msjuergent
Can you please check and add your comments on this doc update request as applicable.

Thanks a lot Vikas, the PR with the changed wording just got merged and should be released with the next release. Thanks a lot for pointing me to the inconsistency.


login screen not available

webpack error keeps logins creen from  appearing. see attached screen snapshot

Maybe it was due to a deploy.sh execution to cp the startup_dokimion_server.sh script.