[Footer.jsx] - Footer Component Completed !

The Footer Component was Completed as per the provided Figma prototype (Colors and other things are same as per the prototype)
Video of Proof:
https://github.com/Curious-Ecosystem/Curious-Connect/assets/94531691/9c7606e7-215b-4002-8a8f-758daf07ebc1
Checklist

[x] My code follows the style guidelines of this project
[x]  I have performed a self-review of my own code
[x]  My changes generate no new warnings
[x]  My changes does not break the current system and it passes all the current test cases.

Hi
we are getting this error

We are not able to see your code

We are not able to see your code

Sorry but this is not my code you can recheck my pull request I just created components name folder in side of that two files are there Footer.jsx and index. jsx

We are not able to see your code

My Footer code is out of the src file of components file

When I created this pull request the structure of folders are different due to this problem is occurred.

I will fix this today it self but please Mannualy check it once for me


Adding support for dict in  infer_shape

Currently in MXNET if I have below code, infer shape fails:
data = mx.sym.Variable('data-gpu0')
prev = mx.sym.Variable('prev')
fc1  = mx.sym.FullyConnected(data=data, name='fc1', num_hidden=128)
fc2  = mx.sym.FullyConnected(data=prev, name='fc2', num_hidden=128)
out  = mx.sym.Activation(data=mx.sym.elemwise_add(fc1, fc2), act_type='relu')
out.infer_shape(data-gpu0=(10,64), prev=(10,128))

  File "<ipython-input-6-3834d8e9b880>", line 2
    out.infer_shape(data-gpu0=(10,64), 'prev'=(10,128))
SyntaxError: keyword can't be an expression

Also one cannot infer_shape using variable  as name  i.e
data = mx.sym.Variable('data')
prev = mx.sym.Variable('prev')
fc1  = mx.sym.FullyConnected(data=data, name='fc1', num_hidden=128)
fc2  = mx.sym.FullyConnected(data=prev, name='fc2', num_hidden=128)
out  = mx.sym.Activation(data=mx.sym.elemwise_add(fc1, fc2), act_type='relu')
name="data"
out.infer_shape(name=(10,64), prev=(10,128))

MXNetError: [10:24:51] src/c_api/c_api_symbolic.cc:422: InferShapeKeyword argument name name not found.
Candidate arguments:
	[0]data
	[1]fc1_weight
	[2]fc1_bias
	[3]prev
	[4]fc2_weight
	[5]fc2_bias

To solve this issue I propose solution in this PR to add support for infer_shape to accept dict, so that user can provide data_names and shapes freely.(This will also be similar to mx.viz.plot_network that takes inputs as dict)
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[ ] The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes)
[ ] Changes are complete (i.e. I finished coding on this PR)
[ ] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[ ] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
Check the API doc at http://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
[ ] To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

[x] Add infer_shape to accept "dict" of input names and shapes as key value pair.

Comments

If this change is a backward incompatible change, why must this change be made.
Interesting edge cases to note here

@sandeep-krishnamurthy  @lupesko  @nswamy

out.infer_shape(data-gpu0=(10,64), prev=(10,128))
This is simply a syntax error. You can't use - in variable names. You need to use _

Sounds like we should instead limit the string being used in symbol's variable name.

@piiswrong  But that is variable name, which is a string .
mx.sym.Variable('data-gpu0')
User should be able to use special characters.
Moreover, we have encountered models (ONNX models) that have input name as "data/gpu0", which when imported to MXNet and tried to infer_shape  throws same error.

This is a conflict between the requirement of variable names in python and the one in our graph representation. Given the use case, I think it's indeed necessary to support dictionary to break the coupling.

You can use **kwargs for this. No need to change the interface

@piiswrong  Thanks. That should do the trick. I agree no need to change the interface.


I see that this was opened in 2018, has there been any updates?

    I see that this was opened in 2018, has there been any updates?

Originally posted by @sgau77 in https://github.com/jaredreich/notie/issues/147#issuecomment-1292299834
Really need this addition, am having to update accessibility on a site that makes extensive use of notie

Can I take this issue ?

I was tempted to use this library but the lack of activity on this repo has put me off.


Is it possible notify data from server to client

This is a good client/server erpc. The basic mode is that client send a remote call to server, then server give response. Is it possible server notify or push data to client at any time? Or is it possible implement both client and server on one node? For example two node A and B. Most of time, A can send call to B and wait response. But some case, B needs to send data to A initiatively, how can achieve it?

Hello @hyller ,
the solution of your case is the transport arbitrator. You can get more info from following discussions (incl. where to obtain an example projects): #80 , #62
Regards
Michal

Thanks Michal, it is what I want to have.


Support react 16.x?

This project is awesome! Any plans to support react 16.x?

Hi, just in case it has been buried in the issues. This fork here: https://github.com/marvelapp/react-ab-test supports React 16.
I'm not sure how much action either are getting at the moment. But it worked for me.


Add a new test with composition in mind

I was wondering how the lib would behave in such circumstance.
I couldn't find where we the order logic is in the source code, but it's working :). Any clue?
Thanks

I'm not 100% sure which part you're looking for, is this it? https://github.com/styled-components/styled-components/blob/b69e494638df7427a6c963d55b119e918f0c1ef6/src/models/StyledComponent.js#L16-L22

I'm not 100% sure which part you're looking for, is this it?

Oh exactly, that's what I was looking fro. Thanks!
So the style is injected in the DOM at the component's creation time.
That mean we have to be cautious with asynchronous js evaluation.
That's probably a rare enough case to be ignored.
E.g.
import React from 'react';
import { render } from 'react-dom';
import styled from 'styled-components';
import defer from './defer';

const Div1 = styled.div`color: green;`
const Div2 = defer(() => (
  styled(Div1)`color: blue;`
))
const Div3 = styled(Div2)`color: red;` //  ---> output blue, expect red

const App = () => (
  <Div3>Click me!</Div3>
);

render(<App />, document.getElementById('content'));

defer.js
```jsx
// @flow weak
import React, { Component } from 'react'
export default function defer(baseComponentGenerator) {
class Defer extends Component {
constructor(props, context) {
super(props, context)
  this.state = {
    show: false,
  }
}

componentDidMount() {
  /* eslint-disable react/no-did-mount-set-state */
  this.timer = setTimeout(() => {
    this.setState({
      show: true,
    })
  }, 0)
  /* eslint-enable react/no-did-mount-set-state */
}

componentWillUnMount() {
  clearTimeout(this.timer)
}

render() {
  if (this.state.show) {
    const BaseComponent = baseComponentGenerator();
    return <BaseComponent {...this.props} />
  }

  return null
}

}
return Defer
}
</detail>

No, it's actually injected at render time – I don't see how that's an issue, even with the above case? I feel like it works exactly how I would expect it to.

@mxstbr You are right sorry. I meant the rules declaration is injected at the component's creating time. It's not injected yet in the DOM.

it works exactly how I would expect it to.

Right, depend on the use case.
I'm still digging through this rabbit hole. I'm getting confused 😬 .

@mxstbr I have finally figured it out 🎋 >< .
The style injection order is determined at the Component creation time with this line that inject a placeholder styleSheet. That can be later hydrated at the render time.
That's smart.
So anything differing the component creation in the HoC chain is going to break the composition order. I better understand the tradeoff now with this approach.


NestedScrollView + ListView not work touchpad scroll

NestedScrollView + ListView not work touchpad scroll
if the application has a height equal to 0.8 of the screen height, then the touchpad scroll does not work
if we reduce the window size to about 0.5 screen height the touchpad scroll works
desktop macOS
master or stable
Flutter 3.7.0-10.0.pre.46 • channel master •
https://github.com/flutter/flutter.git
Framework • revision 420c6d6cc8 (89 minutes ago) • 2022-12-19 08:44:36 -0500
Engine • revision 58ab5277a7
Tools • Dart 3.0.0 (build 3.0.0-35.0.dev) • DevTools 2.20.0
import 'package:flutter/material.dart';

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

class MyApp extends StatelessWidget {
  const MyApp({super.key});

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(
        primarySwatch: Colors.blue,
      ),
      home: const MyHomePage(title: 'Flutter Demo Home Page'),
    );
  }
}

class MyHomePage extends StatefulWidget {
  const MyHomePage({super.key, required this.title});

  final String title;

  @override
  State<MyHomePage> createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: Text(widget.title),
      ),
      body: NestedScrollView(
        body: ListView(children: [
          ListView.builder(
              physics: const ScrollPhysics(),
              shrinkWrap: true,
              itemCount: 6,
              itemBuilder: (context, index) {
                return Padding(
                  padding: const EdgeInsets.all(8.0),
                  child:
                      Container(width: 100, height: 100, color: Colors.green),
                );
              }),
          ListView.builder(
              physics: const ScrollPhysics(),
              shrinkWrap: true,
              itemCount: 5,
              itemBuilder: (context, index) {
                return Padding(
                  padding: const EdgeInsets.all(8.0),
                  child:
                      Container(width: 100, height: 100, color: Colors.purple),
                );
              }),
        ]),
        headerSliverBuilder: (BuildContext context, bool innerBoxIsScrolled) {
          return [];
        },
      ),
    );
  }
}

@statsss thanks for reporting this. I can reproduce this issue on the latest master channel. But it works as expected on stable channel. Labeling this as a regression issue.

Master
Stable

❌
✅

MacOS
Chrome (Web)

❌
✅

✅: No Issue ❌: Issue reproduced

Demo
https://user-images.githubusercontent.com/104349824/208589084-54f6ae15-af90-4ce2-92ed-8e74f723a396.mov

flutter doctor -v (stable and master)
[✓] Flutter (Channel stable, 3.3.10, on macOS 13.0.1 22A400 darwin-x64, locale en-VN)
    • Flutter version 3.3.10 on channel stable at /Users/huynq/Documents/GitHub/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 135454af32 (13 hours ago), 2022-12-15 07:36:55 -0800
    • Engine revision 3316dd8728
    • Dart version 2.18.6
    • DevTools version 2.15.0

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/huynq/Library/Android/sdk
    • Platform android-33, build-tools 31.0.0
    • ANDROID_HOME = /Users/huynq/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14B47b
    • CocoaPods version 1.11.3

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

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

[✓] IntelliJ IDEA Community Edition (version 2022.1.1)
    • IntelliJ at /Users/huynq/Library/Application Support/JetBrains/Toolbox/apps/IDEA-C/ch-0/221.5591.52/IntelliJ IDEA CE.app
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart

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

[✓] Connected device (3 available)
    • SM T225 (mobile) • R9JT3004VRJ • android-arm64  • Android 12 (API 31)
    • macOS (desktop)  • macos       • darwin-x64     • macOS 13.0.1 22A400 darwin-x64
    • Chrome (web)     • chrome      • web-javascript • Google Chrome 108.0.5359.124

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

• No issues found!

[!] Flutter (Channel master, 3.7.0-10.0.pre.60, on macOS 13.0.1 22A400 darwin-x64, locale en-VN)
    • Flutter version 3.7.0-10.0.pre.60 on channel master at /Users/huynq/Documents/GitHub/flutter_master
    ! Warning: `flutter` on your path resolves to /Users/huynq/Documents/GitHub/flutter/bin/flutter, which is not inside your current Flutter SDK checkout at /Users/huynq/Documents/GitHub/flutter_master. Consider adding /Users/huynq/Documents/GitHub/flutter_master/bin to the front of your path.
    ! Warning: `dart` on your path resolves to /Users/huynq/Documents/GitHub/flutter/bin/dart, which is not inside your current Flutter SDK checkout at /Users/huynq/Documents/GitHub/flutter_master. Consider adding /Users/huynq/Documents/GitHub/flutter_master/bin to the front of your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision e625e5f461 (16 minutes ago), 2022-12-19 21:17:06 -0500
    • Engine revision 3330cce605
    • Dart version 3.0.0 (build 3.0.0-35.0.dev)
    • DevTools version 2.20.0
    • If those were intentional, you can disregard the above warnings; however it is recommended to use "git" directly to perform update checks and upgrades.

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/huynq/Library/Android/sdk
    • Platform android-33, build-tools 31.0.0
    • ANDROID_HOME = /Users/huynq/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14B47b
    • CocoaPods version 1.11.3

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

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

[✓] IntelliJ IDEA Community Edition (version 2022.1.1)
    • IntelliJ at /Users/huynq/Library/Application Support/JetBrains/Toolbox/apps/IDEA-C/ch-0/221.5591.52/IntelliJ IDEA CE.app
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart

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

[✓] Connected device (3 available)
    • SM T225 (mobile) • R9JT3004VRJ • android-arm64  • Android 12 (API 31)
    • macOS (desktop)  • macos       • darwin-x64     • macOS 13.0.1 22A400 darwin-x64
    • Chrome (web)     • chrome      • web-javascript • Google Chrome 108.0.5359.124

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

! Doctor found issues in 1 category.

@moffatman Is this by any chance related to the recent scrolling regression?
/cc @Piinks

Yes, we should cherry-pick https://github.com/flutter/flutter/pull/116689

Yeah that's what I was wondering.. we cherry picked #116689 yesterday in https://github.com/flutter/flutter/pull/117343 - however this reproduction looks curious, there are further nested scrolling widgets in the body of the NestedScrollView. @statsss Have you considered un-nesting the ListViews to use the NestedScrollView?

It looks like the nested scroll controller only knows about the second inner listview, and that's what it's basing its calculation of canDrag on. So when the window is taller than the listview of purple containers, the whole thing isn't scrollable. I think it is PrimaryScrollController which does that association, so the breaking change could have been in there as well.
I don't think this is related to my recent change.

Yeah I think that makes sense. I understand that this works on stable, but it looks like a happy accident. The NestedScrollView works through controlling an outer and inner scroll position, but in this example there are three inner scroll positions.
@statsss shrinkwrap is also very taxing on performance. It looks like the body of your NEstedScrollView should actually be composed like this:
// (Pseudo)
NestedScrollView(
  body: CustomScrollView(
    slivers: [
      SliverList(... list 1),
      SliverList(... list 2),
    ]
  )
)

or you could also do
// (still pseudo)
NestedScrollView(
  headerSliverBuilder: (_, __) {
      return [ SliverList(... list 1) ];
  },
  body: CustomScrollView(
    slivers: [
      SliverList(... list 2),
    ]
  )
)

or, based on the repro, the NestedScrollView is not necessary at all since there is not headerSliverBuilder.
// (still Pseudo)
CustomScrollView(
    slivers: [
      SliverList(... list 1),
      SliverList(... list 2),
    ]
  )

Thanks but that doesn't work either.
if the application has a height equal to ~0.9 of the screen height, then the touchpad scroll does not work
`import 'package:flutter/material.dart';
void main() {
runApp(const MyApp());
}
class MyApp extends StatelessWidget {
const MyApp({super.key});
@override
Widget build(BuildContext context) {
return MaterialApp(
title: 'Flutter Demo',
theme: ThemeData(
primarySwatch: Colors.blue,
),
home: const MyHomePage(title: 'Flutter Demo Home Page'),
);
}
}
class MyHomePage extends StatefulWidget {
const MyHomePage({super.key, required this.title});
final String title;
@override
State createState() => _MyHomePageState();
}
class _MyHomePageState extends State {
@override
Widget build(BuildContext context) {
return Scaffold(
appBar: AppBar(
title: Text(widget.title),
),
body: NestedScrollView(
headerSliverBuilder: (BuildContext context, bool innerBoxIsScrolled) {
return [];
},
body: CustomScrollView(slivers: [
SliverList(
delegate: SliverChildBuilderDelegate(
(context, index) => Padding(
padding: const EdgeInsets.all(8.0),
child:
Container(width: 100, height: 100, color: Colors.green),
),
childCount: 6,
),
),
SliverList(
delegate: SliverChildBuilderDelegate(
(context, index) => Padding(
padding: const EdgeInsets.all(8.0),
child:
Container(width: 100, height: 100, color: Colors.purple),
),
childCount: 5,
),
),
])),
);
}
}`


Source code pro syntax highlighting

syntax highlighting not working in source code pro. The text just blacks out

wrong repository. sorry for inconvinience


would this package support bulk update in the future?

the sql like :
UPDATE table_name
SET a = CASE WHEN id = 1
THEN 'something'
WHEN id = 2
THEN 'something else'
WHEN id = 3
THEN 'another'
END
WHERE id IN (1,2,3)
;

I don't think there's any plans to include this kind of feature, mainly because it's not a solution to the issue where gorm doesn't support bulk insert.
Support for upser/ON DUPLICATE KEY has been discussed, see the latest summary in #33 which mentions closed PRs and alternative implementations.
Other than that I see the end of this library getting closer while gorm is working it's way towards a v2.0 release with a total rewrite. You can follow the v2 development of gorm here.

ok, got this, thank you. I have already used v2.0 now.

I use the "insert_option" with "ON DUPLICATE KEY UPDATE column VALUES (column)", and resovle this problem. Thank you!

@itisbean how did you use the insert_option? I could not use it all.
db.Set("gorm:insert_option", "ON DUPLICATE KEY IGNORE")
err := gormbulk.BulkInsert(db, slice, 3000)

But I still get pq: duplicate key value violates unique constraint "name_unique_key"

@itisbean how did you use the insert_option? I could not use it all.
db.Set("gorm:insert_option", "ON DUPLICATE KEY IGNORE")
err := gormbulk.BulkInsert(db, slice, 3000)

But I still get pq: duplicate key value violates unique constraint "name_unique_key"

I use it like this way:
gormbulk.BulkInsert(db.Set("gorm:insert_option", "ON DUPLICATE KEY UPDATE field1 =  VALUES(field1), field2 = VALUES(field2)"), []interface{}, 3000)

@lopes-gustavo Most of the operations in gorm return a new pointer to the db handler so you need to re-assign it. With your code this should work:
db = db.Set("gorm:insert_option", "ON DUPLICATE KEY IGNORE")
err := gormbulk.BulkInsert(db, slice, 3000)


Faster Rgb to Hsl and Hsv conversions

Faster conversion from Rgb to Hsl and Rgb to Hsv

I've added the before and after benchmark  and tests code to the benches folder. Let me know if they should be removed.
Rgb to Hsl benchmarks
test rgb_to_hsl_original_f32  ... bench:          14 ns/iter (+/- 2)
test rgb_to_hsl_optimized_f32 ... bench:           9 ns/iter (+/- 1)

test rgb_to_hsl_original_f64  ... bench:          14 ns/iter (+/- 5)
test rgb_to_hsl_optimized_f64 ... bench:           9 ns/iter (+/- 1)

Rgb to Hsv benchmarks
test rgb_to_hsv_original_f32  ... bench:          12 ns/iter (+/- 0)
test rgb_to_hsv_optimized_f32 ... bench:           9 ns/iter (+/- 0)

test rgb_to_hsv_original_f64  ... bench:          12 ns/iter (+/- 1)
test rgb_to_hsv_optimized_f64 ... bench:           9 ns/iter (+/- 1)

Cool! And nice speedup. Are these new algorithms hand crafted or is there a source for them? (just curious) The benchmarks can stay, but how come they aren't using the rgb.into_hsl() and rgb.into_hsv()? Another inlining issue?

Are these new algorithms hand crafted or is there a source for them? (just curious)

It started with me noticing that there are unnecessary comparisons for finding both max and min and trying to optimize them.I also a stackoverflow answer that basically said the same, you can find max and min in 3 comparisons instead of 4.

The benchmarks can stay, but how come they aren't using the rgb.into_hsl() and rgb.into_hsv()?

I didn't check with the into_hsl and hsv. I guess because running the benchmarks will then no longer make sense once this is merged.

Yea, it was pretty naive before, since the first goal was to just get the basics down.

I didn't check with the into_hsl and hsv. I guess because running the benchmarks will then no longer make sense once this is merged.

What I meant was to run the into_* as the new algorithm. Thinking more about it makes me realize that these benchmarks will make little sense in the future, unless they are kept as some kind of regression tests. A proper performance test would compare to the previous release, and not just a previous algorithm, so this doesn't really work for that either... May be better to just remove them, after all...
Thank you for providing them, anyway. It's nice to see some numbers.

Just checked. The trait version is equally fast.
test rgb_to_hsv_optimized_f32 ... bench:           8 ns/iter (+/- 0)
test rgb_to_hsv_optimized_f64 ... bench:          10 ns/iter (+/- 0)
test rgb_to_hsv_original_f32  ... bench:          12 ns/iter (+/- 0)
test rgb_to_hsv_original_f64  ... bench:          12 ns/iter (+/- 1)
test rgb_to_hsv_trait_f32     ... bench:           8 ns/iter (+/- 0)
test rgb_to_hsv_trait_f64     ... bench:          10 ns/iter (+/- 0)

test rgb_to_hsl_optimized_f32 ... bench:           9 ns/iter (+/- 0)
test rgb_to_hsl_optimized_f64 ... bench:           9 ns/iter (+/- 0)
test rgb_to_hsl_original_f32  ... bench:          13 ns/iter (+/- 4)
test rgb_to_hsl_original_f64  ... bench:          13 ns/iter (+/- 4)
test rgb_to_hsl_trait_f32     ... bench:           9 ns/iter (+/- 0)
test rgb_to_hsl_trait_f64     ... bench:           9 ns/iter (+/- 1)

Alright, seems like inlining works as expected in this case.

Removed the benches. Should be good to go.

The RgbHue hiccups are probably related to the nested calls, while this is quite shallow. Anyway, I'll inspect this a bit deeper in a moment, but I think the tests has given this an OK stamp, already.

This looks great! Can't find anything to fix here :+1: Thank you!
@homu r+

:pushpin: Commit cdb4a3f has been approved by Ogeon

:zap: Test exempted - status


Set workdir for stressng benchmark

Set writeable WORKDIR for stressng image so output report can be written in an unprivileged pod when running on OpenShift.
This would fix #223

Can one of the admins verify this patch?

@mkarg75 FYI

/rerun all

Results for SNAFU CI Test

Test
Result
Runtime

snafu/stressng_wrapper
PASS
00:04:53


There is phantomjs and karma in dependencies. Why? As ngStorage user i think it should be in devDeps.

@ppatrik I was confused by this too. It actually was fixed years ago, but this package is published under two different names (ng-storage and ngstorage) and newer versions are only available under the official ngstorage name: https://github.com/gsklee/ngStorage/issues/209. Just upgrade to the latest version under the ngstorage name.


feat: drag n drop to reorder tasks

Implements #25
Drag and drop feature to reorder tasks using react-beautiful-dnd
I put the icon before the task name because when I was testing, the layout shift seems better to me. But i'm not designer and I have a poor knowledge on tailwinds classes...

do you have any idea to avoid this?

do you have any idea to avoid this?

Can you tell how you got this? I'm draggind the tasks randomly and didn't get to replicate this

do you have any idea to avoid this?

to my understanding, even though the user can drag a task outside of the Tasks area, it can't be dropped. as in it just snaps back to the expected area, which is expected behaviour. if the user could drop it outside, then we would have a problem.

is just a aesthetic thing., if you drag a task outside the container, when you drop, it comeback to original place

is just a aesthetic thing., if you drag a task outside the container, when you drop, it comeback to original place

we can keep it as is.

I though the drag button was to appear in all cases, then the layout shift being beside the done button and appearing under the same conditions, I think it will be good.  I'll work on the adjustments and update de pr soon.

great stuff, thanks for addressing all that
we have only one issue before merging this, the rest works fine:
from 320px..767px there are rough corners on top and bottom right. i think it is derived from one of your added divs. for simplicity, you can just slap "rounded-2xl", which is the default border radius for the whole project.

@LukeberryPi  I notice a border effect that have in production and also on my branch, that is this border:

This algo happens on lastTask. I added classes to avoid this when task is not empty. Hope its ok

@LukeberryPi I notice a border effect that have in production and also on my branch:
This algo happens on lastTask. I added classes to avoid this when task is not empty. Hope its ok
OBS: In one of my monitors I can see cleary a border, in the other one, i can't. So if you can't see, believe me, there is a border lol

great catch! my eyesight isn't the best, so i definetely can't see that. thanks for the change


Fix race condition when getting WALs for dead tserver

When a tablet server dies the master gets its WALs from ZK.  In ZK there
is a list of WALs per tserver. Each WAL in ZK has state that is either
OPEN, CLOSED, or UNREFERENCED.  The master needs a list of OPEN and
CLOSED logs for dead tservers.  While the master is trying to obtain
this list its possible that the Accumulo GC may delete an UNREFERENCED
WAL.  If this happened then the code before this commit would return an
empty list of WALs. This could result in OPEN and CLOSED logs being
ignored for recovery which could result in data loss.  This patch fixes
the race condition.
This bug was observed while looking into an exception I noticed while
writing test for #860.  In the IT I was frequently calling another
WalStateManager function and noticed NoNodeExceptions.  As a result I
examined how the entire class handled NoNode race conditions and found
this bug.  I noticed some other possible NoNode race condition, but do
not think this these would occur with the current way the code is called.

I have been looking into this and I think it could only happen if the GC pulled info about an unreferenced WAL into memory before a tserver died AND then deleted the unreferenced WAL after the tserver died (while the master is trying to get the list).  The GC seems to completely ignore WALs for any dead tservers that have tablets assigned to them.

Looking at the history of WalStateManager it seems like this may have been a bug since 1.8.0.


Move from Dockerize to Waiting on KV Store

Is your feature request related to a problem? Please describe.
Dockerize leaves a bit to be desired. We're moving to a distributed key-value (KV) store (Consul), so we should coordinate handoffs via this store.
Describe the solution you'd like
Rather than waiting for contracts to be deployed via Dockerize or file touches, block on the availability of a Consul key. When available, this key points to (its value is) necessary chain data.

Closing in favor of #54 which is already on its way.


contextMenuTarget?

Hi
how would i set up different place instead of document.body?
This doesn't work
contextMenuTarget: document.querySelector('.header')

Hi there, thanks for your report.
I will check that.

@plavet
When do you set contextMenuTarget ?
contextMenuTarget: document.querySelector('.header')
If .header has not mounted, you won't select it.
So you can set contextMenuTarget in the mounted hook of your component which contains .header.

when using document.querySelecotor ethe following error occured:
"vue.esm.js?65d7:479 [Vue warn]: Error in nextTick: "TypeError: _this.target.addEventListener is not a function"

I wonder how can I get the target element when I clicked the context menu?(If it is not supported how can I copy text?)

why not set contextMenuTarget prop to css seletor
Uh...when i run
npm install @xunlei/vue-context-menu

it reports a 404 error


Proposal 1 of 2: Add concurrency control to BaseChain

See also #92. We only want 1 of these.
Using https://github.com/sindresorhus/p-queue
This would allow all chains to be "rate-limited", especially useful when dealing with APIs that are heavily rate-limited, like OpenAI.

Closing in favour of #92


Attached extra bucket policy around the data bucket

The extra policies to secure the bucket existed  for the bucket but wasnt attached to the bucket . Terraform   was added attach the policy to bucket

can you do a find and replace for all s3 puts in the repo and add the parameters of this form so they don't get broken? we will have to do the container image separately
        s3.put_object(
            Body=json_body,
            Bucket=bucket,
            Key=key,
            ACL='bucket-owner-full-control',
            ServerSideEncryption='AES256',
        )


Errors reported when running "dotnet build /t:GenerateCode"

I've met some errors when running "dotnet build /t:GenerateCode" using remote branch in tsp-location.yaml, after mitigate with referencing to local repository, it works. But the CI build will be blocked by this error and others could not build on their machines.
Refer to tsp-location file here: https://github.com/mengaims/azure-sdk-for-net/blob/carnegie-test/sdk/contentsafety/Azure.AI.ContentSafety/tsp-location.yaml
The error is:
Copy-Item: [My local sdk repository]\eng\common\scripts\TypeSpec-Project-Sync.ps1:23
Line |
23 | Copy-Item -Path $source -Destination $dest -Recurse -Force
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| Cannot find path
| '[My local directory]\sparse-spec\Azure.AI.ContentSafety\specification\cognitiveservices\ContentSafety' because it
0m
| does not exist.
@chunyu3 @m-nash could you help have a check?
CC @heaths @catalinaperalta

it is the permission issue. it reference to the private repo azure-rest-api-specs-pr, it is no permission to sparse checkout code.

We should not be merging anything in azure-sdk-for-net that points at the private spec repo.  It should only go into the private sdk repo.

Thanks for confirming. I was afraid of that, but wasn't entirely sure. @mengaims can you get the specs moved to the public repo?

@heaths Yes, the specs has been merged. https://github.com/Azure/azure-rest-api-specs/pull/23840

@m-nash should we just close this issue as By Design then, or keep it open to track support -pr if that's even desirable?

This error has been resolved after pulling typespec from public repo. I think we can close it now.

Closing this as we have another issue tracking private repo support in the sync / generate scripts https://github.com/Azure/azure-sdk-tools/issues/5275


Write tests for ServiceUtils

Using CodeCov results as a guide, improve unit tests for ServiceUtils
https://codecov.io/gh/AndcultureCode/AndcultureCode.JavaScript.Core/src/master/src/utilities/service-utils.ts

Looks like there is far more coverage now (over 95%) then there was when this issue was created. I'll get it to 100%, but certainly not as high of a need as I thought when I jumped in 😄

Additional unit test added, which bumped the test coverage for ServiceUtils up to 100%.


Fix: No texture becoming transparent

I was going over issue https://github.com/M3-org/CharacterStudio/issues/147
I think I got it fixed:

You're welcome to try it out.
Here are files to test:
horns.zip
horns.vrm is a VRM1 of the horns based on the drophunter skeleton, just add it to your character-assets.
Edits to manifest.json of drophunter:
head:
        {
          "id": "hunter_horn",
          "name": "Hunter Horns",
          "directory": "head/hunter_horn.vrm",
          "thumbnail": "head/hunter_horn.png",
          "cullingDistance": [
            0.03,
            0.03
          ]
        },

Awesome job Benjy :) !, looks good to me, tested it and its working properly now. Merging!


[doc] Add the block-dashboards to the primative page

This expands to all the keys that contain 'prim' in ot-nightly-results.js (Currently 5)
@GregAC was there any reason not to add this the first time around? Just to double-check. Thanks

This expands to all the keys that contain 'prim' in ot-nightly-results.js (Currently 5)
@GregAC was there any reason not to add this the first time around? Just to double-check. Thanks

I don't think so, just an oversight on my part


Importing .DS_store

Dear Scott,
The TMT (version 1.0) on my Mac (OS Catalina 10.15.3) is importing the .DS_Store file (which is creating some odd topics! See #3 below [edit: file attached — issue-74-mallet-output.txt
)] Can you assist?
Thank you,
Adam

Yes, this is a very irritating problem. My current understanding is that MALLET, by default, imports everything in the input folder. Modifying that behavior directly requires me to re-design parts of the TMT to work directly with MALLET's internal API, which I haven't had time to do.
I have considered having the TMT actively delete the .DS_Store file before calling MALLET, but that seems a little aggressive. The simple fix is just to remove the file before running the tool, but of course that's a hassle.
I will give some more thought to this problem though — the risks of deleting the file automatically seem low, but I am uncertain, hence my hesitation.

PS: this is closely related to #69.

Dear Scott,
Thank you very much! I would be happy to remove the DS_Store file prior to
running the TMT. That said, I think that file is hidden; I don't see it in
my Mac's finder window. Is there an easy way to remove it?
Thank you!
Adam
On Fri, Mar 6, 2020 at 10:43 AM Jonathan Scott Enderle <
<EMAIL_ADDRESS>wrote:

Yes, this is a very irritating problem. My current understanding is that
MALLET, by default, imports everything in the input folder. Modifying that
behavior directly requires me to re-design parts of the TMT to work
directly with MALLET's internal API, which I haven't had time to do.
I have considered having the TMT actively delete the .DS_Store file before
calling MALLET, but that seems a little aggressive. The simple fix is just
to remove the file before running the tool, but of course that's a hassle.
I will give some more thought to this problem though — the risks of
deleting the file automatically seem low, but I am uncertain, hence my
hesitation.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/senderle/topic-modeling-tool/issues/74?email_source=notifications&email_token=AKIDMYV6C6H5UDGCROW6JPLRGEKZTA5CNFSM4LCTWUN2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEOBZN4I#issuecomment-595826417,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKIDMYRYMKXLU7INMDDC6RLRGEKZTANCNFSM4LCTWUNQ
.

--
Adam Mazel

@amaze2 so sorry — I missed this last until now. I'm realizing that the easiest way to remove it is using the terminal — which kind of defeats the point of having a GUI. I have to think about this a bit more. I might need to build in an option for this that removes the .DS_store file from the input folder if it exists.


chore: upgrade package ws from 5.0.0 to 7.4.6

Description

Task Item
close #7992

Screenshots

Coverage remained the same at 50.326% when pulling 4c5611a7e5880dc50370966510e3e1f33b0dda1c on zhixzhan/ws-upgrade into 4967e337136da3abc0391d9491a41d3e191ead00 on main.


How does the port map be modified after the container is created?

In the container details interface, I can not find the place to modify the port.

You cannot. This is a docker limitation.
We are adding a new feature soon, which will allow this, but only by automatically deleting and recreating the container.
Rgds,
Neil Cresswell
On 10/07/2017, at 2:33 PM, 邵磊 <notifications<EMAIL_ADDRESS>wrote:
In the container details interface, I can not find the place to modify the port.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_portainer_portainer_issues_1006&d=DQMCaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=0fx0h4vB56iTLpw2McH1ZD6TqG_QGpbggVOB-PfMJpM&m=opUiUfM-69DyTmr2NV9qIxuJ5cJjK_AX03HhHhYln-s&s=dAOH0IDBa8Nij_WsZZPY4zxWtkVo50AogssZbokomnw&e=, or mute the threadhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AWGrlc4tNFXusPnmwtXsN0AXQeJ2u9SSks5sMY1xgaJpZM4OSSgD&d=DQMCaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=0fx0h4vB56iTLpw2McH1ZD6TqG_QGpbggVOB-PfMJpM&m=opUiUfM-69DyTmr2NV9qIxuJ5cJjK_AX03HhHhYln-s&s=9E3jPqHzkfLFYBN1bEzem5C81A60KSAYwJW5oepe6FU&e=.

@ncresswell
I understand, thank you very much!


[Rendering] Lighting support

Background
At present, our lighting setup is terrible. We have some faux IBL going on and some weird global directional light.
Let's fix it.
TODO

[x] #255
[x] #314

Done


Explain Your Issue

Experiencing issues? Check our Troubleshooting FAQ wiki!
Describe the Bug
Trying this fix for a timeout issue on the server :
https://questions.satisfactorygame.com/post/62572a7cca608e080350c2ad
The engine.ini file that I'm using is currently rewritten and I loose the time out config everytime I redeploy the the container.
I am trying to set the following in the engine.ini file (.../gamefiles/FactoryGame/Saved/Config/LinuxServer/) :
[/Script/OnlineSubsystemUtils.IpNetDriver]
InitialConnectTimeout=30.0
ConnectionTimeout=60.0

The server itself crash due to what seems like a time out of more than 30sec for the save to write. Hardware wise, all config are already on a separate N100 beelink computer with files stored on the internal SSD (M.2 I believe)
Your Runtime Command or Docker Compose File
Please censor anything sensitive. Your runtime command might look like this:
services:
  satisfactory-server:
    container_name: 'satisfactory-server'
    hostname: 'satisfactory-server'
    image: 'wolveix/satisfactory-server:latest'
    ports:
      - '7777:7777/udp'
      - '7777:7777/tcp'
    volumes:
      - '/docker/satisfactory-server:/config'
    dns:
      - <IP_ADDRESS>
      - <IP_ADDRESS>  # DNS servers to use within the container
      - <IP_ADDRESS>
    environment:
      - MAXPLAYERS=4
      - TZ="America/Montreal"
      - PGID=1001
      - PUID=1001
      - ROOTLESS=false
      - STEAMBETA=false
      - TIMEOUT=120
    restart: unless-stopped
    healthcheck:
      test: bash /healthcheck.sh
      interval: 30s
      timeout: 10s
      retries: 3
      start_period: 120s
    deploy:
      resources:
        limits:
          memory: 12G
          cpus: 3.5
        reservations:
          memory: 10G

Debug Output
Run the container with DEBUG=true as an environment variable, and it'll print out the system specs requested below, as
well as a bunch of information about your container (version, environment variables, etc.)
OUTPUT HERE

System Specs (please complete the following information):
If you're on Linux, just paste the following block as a single command, and paste the output here.
===== START ISSUE REPORT =====
OS:  Linux docker 6.5.13-3-pve #1 SMP PREEMPT_DYNAMIC PMX 6.5.13-3 (2024-03-20T10:45Z) x86_64 GNU/Linux
CPU: Intel(R) N100
BIOS Intel(R) N100 To Be Filled By O.E.M. CPU @ 2.8GHz
RAM: 11GB/14GB
HDD: 39GB/99GB (41% used)
===== END ISSUE REPORT =====

Logs
_satisfactory-server_logs.txt
Additional Context
It's hard to maintain a stable container, I have health check enable and I often have my container turning to unhealthy in portainer when I leave it running overnight. I did disable the auto-pause recently (but the issue was happening before too)
Thank you!

Hi @Eri-tog, you should not modify ini files directly, and should instead use the environment variables (the TIMEOUT variable modifies those values for you).
Additionally, your instability issues will be due to your CPU's low single-core performance. As mentioned in various other issues, Satisfactory requires a single-core passmark score of approximately 3000+, while yours is ~1900.

I see - Thank you @wolveix ! I will setup a longer time out and get a more powerful dedicated server, until then I think I think i'll look into a save sync solution ! :)

@Eri-tog if you do want a save sync solution, do take a look at the saveshare directory on this repo :) I wrote it for exactly that reason


Package option for google.load method

Hi,
I noticed in the base_chart.rb that you use '#{options[:package].downcase}'.
base_chart.rb
script << "\n  google.load('visualization','1', {packages: ['#{options[:package].downcase}'], callback: function() {"
I'm using a ColumnChart and Rails 2 plugin.
In the ColumnChart example I found (http://code.google.com/apis/ajax/playground/?type=visualization#column_chart) it loads package 'corechart' and then do a "new google.visualization.ColumnChart".
I tried to change the base_chart.rb to use 'corechart' but it didn't work.
I also noticed quite a bit of changes in these methods for the Rails 3 version.
I'm wondering: is this a limitation of plugin version for Rails 2? Or the simple change to the line below is expected to work?
script << "\n  google.load('visualization','1', {packages: ['corechart'], callback: function() {"
Thanks
/Helio

The Rails 2 plugin is using an older version of the Google Visualization charts (i.e. not corechart, just the chart itself), which is why in the javascript generated, you don't see "corechart" in it.
There are also other changes in the latest gem (which should be compatible with Rails 2 too) to make it work with "corechart", therefore I would really recommend that you use the gem instead.
Hope this helps. Thanks!


Sync eng/common directory with azure-sdk-tools for PR 9234

Sync eng/common directory with azure-sdk-tools for PR https://github.com/Azure/azure-sdk-tools/pull/9234  See eng/common workflow

/check-enforcer override
CI pipeline failing on all mac agents for reasons unrelated to this pr


BatchNormalization virtual_batch_size does not work with None in input shape

Please make sure that this is a bug. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:bug_template
System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Linux Ubuntu 18.04
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: N/A
TensorFlow installed from (source or binary): binary
TensorFlow version (use command below):
v2.0.0-beta1-5101-gc75bb66 2.0.0-rc0
Python version: 3.6.8
Bazel version (if compiling from source): N/A
GCC/Compiler version (if compiling from source): N/A
CUDA/cuDNN version: CUDA 10.0, cuDNN <IP_ADDRESS>-1
GPU model and memory: Nvidia RTX 2070 8 GB

Describe the current behavior
A constructor of a tf.keras Model that uses tf.keras.layers.BatchNormalization with virtual_batch_size set and unspecified input shape dimensions throws an exception.
Describe the expected behavior
Such a model should be usable.
Code to reproduce the issue
import tensorflow as tf

inp = tf.keras.layers.Input(shape=(None, None, 3))
net = tf.keras.layers.BatchNormalization(virtual_batch_size=8)(inp)

model = tf.keras.Model(inputs=inp, outputs=net)

Other info / logs
Traceback of the exception:
Traceback (most recent call last):
  File "/home/ikrets/tf2/lib/python3.6/site-packages/tensorflow_core/python/framework/tensor_util.py", line 541, in make_tensor_proto
    str_values = [compat.as_bytes(x) for x in proto_values]
  File "/home/ikrets/tf2/lib/python3.6/site-packages/tensorflow_core/python/framework/tensor_util.py", line 541, in <listcomp>
    str_values = [compat.as_bytes(x) for x in proto_values]
  File "/home/ikrets/tf2/lib/python3.6/site-packages/tensorflow_core/python/util/compat.py", line 71, in as_bytes
    (bytes_or_text,))
TypeError: Expected binary or unicode string, got 8

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/ikrets/tf2/lib/python3.6/site-packages/tensorflow_core/python/framework/test_virtual_batch.py", line 6, in <module>
    net = tf.keras.layers.BatchNormalization(virtual_batch_size=8)(inp)
  File "/home/ikrets/tf2/lib/python3.6/site-packages/tensorflow_core/python/keras/engine/base_layer.py", line 802, in __call__
    outputs = call_fn(cast_inputs, *args, **kwargs)
  File "/home/ikrets/tf2/lib/python3.6/site-packages/tensorflow_core/python/keras/layers/normalization.py", line 652, in call
    inputs = array_ops.reshape(inputs, expanded_shape)
  File "/home/ikrets/tf2/lib/python3.6/site-packages/tensorflow_core/python/ops/array_ops.py", line 131, in reshape
    result = gen_array_ops.reshape(tensor, shape, name)
  File "/home/ikrets/tf2/lib/python3.6/site-packages/tensorflow_core/python/ops/gen_array_ops.py", line 8117, in reshape
    "Reshape", tensor=tensor, shape=shape, name=name)
  File "/home/ikrets/tf2/lib/python3.6/site-packages/tensorflow_core/python/framework/op_def_library.py", line 530, in _apply_op_helper
    raise err
  File "/home/ikrets/tf2/lib/python3.6/site-packages/tensorflow_core/python/framework/op_def_library.py", line 527, in _apply_op_helper
    preferred_dtype=default_dtype)
  File "/home/ikrets/tf2/lib/python3.6/site-packages/tensorflow_core/python/framework/ops.py", line 1296, in internal_convert_to_tensor
    ret = conversion_func(value, dtype=dtype, name=name, as_ref=as_ref)
  File "/home/ikrets/tf2/lib/python3.6/site-packages/tensorflow_core/python/framework/constant_op.py", line 286, in _constant_tensor_conversion_function
    return constant(v, dtype=dtype, name=name)
  File "/home/ikrets/tf2/lib/python3.6/site-packages/tensorflow_core/python/framework/constant_op.py", line 227, in constant
    allow_broadcast=True)
  File "/home/ikrets/tf2/lib/python3.6/site-packages/tensorflow_core/python/framework/constant_op.py", line 265, in _constant_impl
    allow_broadcast=allow_broadcast))
  File "/home/ikrets/tf2/lib/python3.6/site-packages/tensorflow_core/python/framework/tensor_util.py", line 545, in make_tensor_proto
    "supported type." % (type(values), values))
TypeError: Failed to convert object of type <class 'list'> to Tensor. Contents: [8, -1, None, None, 3]. Consider casting elements to a supported type.

I am replicate the issue with TF 2.0.0.rc0. Please take a look at gist here. Thanks!

Added a PR #39131 for the fix.


Add Auto-Discovery support for Laravel 5.5

Coverage remained the same at 87.333% when pulling 75d486751cdfd3fefb7c68279f377637223bb6bb on mul14:patch-1 into b05f60a72246abddfe964ba501831a58111149f0 on brozot:master.


firejail: allow wrapping .desktop applications

Motivation for this change
In addition to wrapping binaries it's convenient to wrap the 'Exec' attribute in
.desktop files with firejail. For example, wrapping the firefox binary with firejail
removes the firefox.desktop file so you cannot start firefox using an
application launches like in Gnome.
This patch allows to specify an attribute set of applications whose desktop file
to wrap. For convenience it allows wrapping their binary through the same config
element. Since firejail options cannot be part of the desktop file attribute, a
separate option is provided for those.
Things done

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

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[X] Ensured that relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

Today I tested some more and found that this doesn't cover all situations. First of all the desktop file icons are unavailable in this PR. The tougher issue is that some desktop files are using the fully qualified path in their Exec attribute, others use only the executable. The latter will cause a jail in a jail, which breaks some situations as well.
I need to some to rework a proper solution for this. I will create a new PR when I have something better. Until then, I'll close this one.


Chore: added Python question

Summary of changes
I added a security related question in the Python questions, let me know if you believe this would be better as a security question
Checklist

[X] I have read and followed the contribution guidelines.
[X] I have read through the Code of Conduct and agree to abide by the rules.
[X] This PR is for one of the available issues and is not a PR for an issue already assigned to someone else.
[X] My PR title has a short descriptive name so the maintainers can get an idea of what the PR is about.
[X] I have provided a summary of my changes.

closes #XXXXX

Hey @jdwilkin4 I've added the requested changes :)


Keep model_avg on cpu

Now model_avg is kept on cpu instead of cuda device, to avoid extra cuda memory usage.

This is a bit confusing, if we are setting a .device that is different from the device it is actually on.

We can replace
model.device =  device

with
@property
def device(self) -> torch.device:
  return next(self.parameters()).device

where the above block should be placed in class Transducer in model.py.

This is a bit confusing, if we are setting a .device that is different from the device it is actually on.

We can replace
model.device =  device

with
@property
def device(self) -> torch.device:
  return next(self.parameters()).device

where the above block should be placed in class Transducer in model.py.

Ok. I will do this.

I think it can be merged.


Feature/pipeline

@nick-j-roberts can you summarize here what this PR doing. Something like this:
This PR:
- does this
- and that
- and that


CI Improvements

This fixes an issue with the VS Test Console on the latest builds and updates CI to collect package artifacts as part of build.

CC. @mjsabby
We should be able to easily publish beta nuget packages after this


Why it doesn't work for me?

Here's my config, I've commented out all other sources to demonstrate.

Hi @pseudoparenchymatous, it's a bit difficult to say. Your configuration looks OK. Did you try with different prefixes when inserting a new plugin? Because only the repositories with the nvim tag are fetched. So if you start typing use { "foo... and there are no repos with a nvim tag starting with foo you won't get the completion.
Besides that, can you try with all lua files to ensure that the files is not the issue?
files = { ".*\\.lua" }

Thank you. Though I didn't change anything in the config, it suddenly decided to work now. I'm glad but confused.


Scruid should support authentication

The current (2.2.0) version of Scruid does not support authentication. Scruid should be able to authenticate itself with the Druid Broker.
Some thoughts:

to my mind this is only required in the DruidAdvancedHttpClient that @anskarl recently added. The simple HTTP client can remain simple.
supporting naive HTTP BASIC auth is the simplest case: it is sufficient to have an interception point in the outgoing half of the connection flow where an Authorization: header with static credentials can be blindly and synchronously added to the request.
however, Druid's auth support is completely pluggable, so for Scruid to support every possible case requires a more complex interception API:

the interceptor should be able to trigger after the original "401 Unauthorized" response arrives from Druid, asynchronously contact a different endpoint such as a KDC or a Vault, obtain whatever credential it requires, and then re-send the original request with the necessary headers added.
to do so, it should probably exist as a long-living object (for keeping shared state, such as a token and its expiry time) that creates a per-request object associated with an invocation of the flow.

I have no prior experience with Akka. Having looked at the code, I am confident that I can contribute a PR that implements the simple case (which would solve my immediate requirement). However, it would result in an API that cannot support the complex case.
If I can get a little help in defining the interception API and integrating it into the DruidAdvancedHttpClient at the appropriate places, I'd be happy to do the implementation work to get the fancy version in place.

Hi @barend ,
I dug into the AdvancedHttpClient a bit more and together with the cases you described, I implemented a rough design which I think would work for your case. It's on the outer edges of the executeRequest, not touching any of the internal stream stuff.
I have a branch here: https://github.com/ing-bank/scruid/compare/request-flow-customization
As you know I don't have much time coming weeks, so I hope it is of help in further steps to take. You can continue on the branch, or just use it as an inspiration, or go in a completely different direction.

Hi @barend and @bjgbeelen
I would like to help regarding the authentication support in Scruid.
@bjgbeelen I took the initiative to make some additions to your design in order to add support
for configuration and prepare a testing environment.

At the moment I've added a docker image with nginx as a basic-auth proxy in front of Druid.
I am using the image beevelop/nginx-basic-auth:latest. The image forwards requests to Druid,
but it expects to perform basic-auth first. The username and password are given to the env variable
HTPASSWD (the value is created using htpasswd -nb user aloha).

In tests, the ing.wbaa.druid.AuthHttpClientSpec overrides the configuration and sets
BasicAuthenticationAddition to the DruidAdvancedHttpClient in order to perform a
typical time-series query with basic-auth.

I haven't made any test for Kerberos at the moment and I haven't add a Kerberos service
to the docker-compose. Perhaps an option is to use an image like
gcavalcante8808/krb5-server:latest but we should also change the docker-image of Druid,
in order to set-up parameters for Kerberos (https://druid.apache.org/docs/latest/development/extensions-core/druid-kerberos.html)

All additions are in https://github.com/anskarl/scruid/tree/request-flow-customization

Awesome @anskarl !
I applied some renaming this morning, saw you worked on the branch already before i made those :D (i think I like RequestFlowExtension better than RequestFlowCustomization
I think @barend will find these additions very welcome!
I'll try to keep an eye on the development that's going to happen, but I'm expecting a daughter any time now, so will have focus off of my computer

Excellent news @bjgbeelen! I wish all the best for the birth of your daughter!!! I am also expecting a daughter the next month :)
I will update the branch with the changes and rename ing.wbaa.druid.AuthHttpClientSpec to ing.wbaa.druid.AuthenticationSpec in tests.

I have added another fork in the mix: barend/request-flow-customization 😄
No real customisations of my own yet. This starts with anskarl/request-flow-customization, merges the latest changes of master, and moves the authentication proxy into the existing NGINX container. I did add a "negative" test for the authentication flow, so that's a start. I'll look into this in more detail.


libsquoosh: node will not exit unless ImagePool is closed.

Hello,
After creating an instance of ImagePool, node will not exit unless ImagePool is closed.
For example, nodejs does not terminate when it reaches the end of following code.
import { ImagePool } from '@squoosh/lib';

const imagePool = new ImagePool();

$ node test1.mjs
(does not terminate)
^C
$

node will exit normally when instance of ImagePool is closed.
import { ImagePool } from '@squoosh/lib';

const imagePool = new ImagePool();
await imagePool.close();

$ node test2.mjs
(terminate normally)
$

Version:

libsquoosh version: 0.4.0, 0.3.1
OS w/ version: macOS 11.5.2
Node version: v14.17.6, v16.9.1

That is not really a bug. The ImagePool manages the workers and Node won’t exit if workers are still running. That’s also why every sample in the README explicitly closes the ImagePool.
At some point we might consider adding a FinalizationRegistry thing, but for now we are gonna keep it explicit.

@surma Thank you for your reply.
I was also thinking that this behavior might be a specification(not a bug), but I wrote this issue to confirm.
My library depends on ImagePool without close()ing, so I try some workarounds.
Thanks,


chore: minor fixes for arm based macs

Signed-off-by: Philippe Scorsolini<EMAIL_ADDRESS>

/ok-to-merge

/ready-to-test


Allow pkt validation hooks to filter packets.

This change is

Reviewed 2 of 2 files at r1.
Review status: :shipit: complete! all files reviewed, all discussions resolved

Comments from Reviewable


Fixes -loose preset for React Native

Should handle for #814 but since I know next to nothing about babel @deontologician should look at this.

This change is

npm run test seems to be hanging for me though.

This looks good, we should remove the dependency on loose though

Ok, I got react native working (chat example), and it seems the issue is that we include our .babelrc at all in the package (which we don't need to do). So, moving it out to a .babelrc, removing -loose (just cause) and making sure the .babelrc isn't distributed should work fine


Index Error

When execute following statement from .ipynb file
`neg_idx = df[(df.news_category=='technology') & (df.sentiment_score == -15)].index[0]
I get following
IndexError                                Traceback (most recent call last)
 in
----> 5 neg_idx = df[(df.news_category=='technology') & (df.sentiment_score == -15)].index[1]
~/anaconda3/envs/myenv/lib/python3.7/site-packages/pandas/core/indexes/base.py in getitem(self, key)
2082
2083         if is_scalar(key):
-> 2084             return getitem(key)
2085
2086         if isinstance(key, slice):
IndexError: index 1 is out of bounds for axis 0 with size 0`
Any assistance will be appreciated.
Gopinathan K.M

Hi @gopinathankm
Could you mention the particular notebook and chapter you are referring to. Also please mention your pandas and numpy versions

No problem I managed the issue. Thanks

@gopinathankm sure. If there's a fix you could share, please do so for everyone else's benefit.


World permissions

I can't set the permsissions per world on my bungeecord, it seems to only be global.

Use the world context key in bungee-lp to define server context. It's weird, I know. See #1668 it's already been suggested, even.

cheers, could you link the page, I can't find it.

https://github.com/lucko/LuckPerms/issues/1668


Test PR to review the changes as a whole.

Lorem ipsum

Please ignore this PR.  I meant to make it into my own repo as a way to review it before sending it to you.


Calc more accurate inverse matrices for cat and pre-calc D50 <-> D65

When applying the inverse CAT transform, the inverse should be calculated at double precision to match the precision of the values used.

Values were calculated with numpy. For reproduction, here is a script:
"""Calculate inverse CAT matrices"""
import numpy as np

np.set_printoptions(precision=16, sign='-', floatmode='fixed')

D50 = [0.3457 / 0.3585, 1.00000, (1.0 - 0.3457 - 0.3585) / 0.3585]
D65 = [0.3127 / 0.3290, 1.00000, (1.0 - 0.3127 - 0.3290) / 0.3290]

bradford = [
    [0.8951000, 0.2664000, -0.1614000],
    [-0.7502000, 1.7135000, 0.0367000],
    [0.0389000, -0.0685000, 1.0296000]
]

von_kries = [
    [0.4002400, 0.7076000, -0.0808100],
    [-0.2263000, 1.1653200, 0.0457000],
    [0.0000000, 0.0000000, 0.9182200]
]

cat02 = [
    [0.7328000, 0.4296000, -0.1624000],
    [-0.7036000, 1.6975000, 0.0061000],
    [0.0030000, 0.0136000, 0.9834000]
]

cat16 = [
    [  0.401288,  0.650173, -0.051461 ],
    [ -0.250268,  1.204414,  0.045854 ],
    [ -0.002079,  0.048952,  0.953127 ]
]

names = [
    'bradford',
    'von_kries',
    'cat02',
    'cat16'
]

if __name__ == '__main__':
    for cat in names:
        m = globals().get(cat)
        print(f'===== {cat} =====')
        print(m)
        print(f'===== {cat} inverse =====')
        print(np.linalg.inv(np.asarray(m, dtype=np.double)))

The recalculated D50 <--> D65 translation was dumped directly from Color.js via:
export function adapt (W1, W2, id = "Bradford") {
	// adapt from a source whitepoint or illuminant W1
	// to a destination whitepoint or illuminant W2,
	// using the given chromatic adaptation transform (CAT)
	// debugger;
	let method = CATs[id];

	let [ρs, γs, βs] = multiplyMatrices(method.toCone_M, W1);
	let [ρd, γd, βd] = multiplyMatrices(method.toCone_M, W2);

	// all practical illuminants have non-zero XYZ so no division by zero can occur below
	let scale = [
		[ρd/ρs,    0,      0      ],
		[0,        γd/γs,  0      ],
		[0,        0,      βd/βs  ]
	];
	// console.log({scale});

	let scaled_cone_M = multiplyMatrices(scale, method.toCone_M);
	let adapt_M	= multiplyMatrices(method.fromCone_M, scaled_cone_M);
	console.log({scaled_cone_M, adapt_M});
	return adapt_M;
};

Hey, thanks for working on this!
I'm wondering if it would make sense to have a build process that calculates these and stores the result in a simple ESM file? Then we could change the precision at will. The downside is it would require someone porting the python code to JS, so it requires more effort. Maybe something for the backlog.

@LeaVerou Forgive me, while capable in JS, it is not the language I usually work with.  I saw a similar script living in the repo https://github.com/LeaVerou/color.js/blob/main/scripts/RGB_matrix_maker.py, so I figured it was fine reaching for what I know.
I can update with a JS version. A little research turned up this project which seems capable of doing linear algebra: https://mathjs.org/docs/getting_started.html.
I'll provide the script in Scripts. Update dev dependencies to include math.js, then update the matrices with the results from the script.  I will likely let someone familiar with the build environment update any automated processes. Is that okay?
So, using that lib, here is a script:
import { create, all } from 'mathjs'
const config = {}
const math = create(all, config)

const d50 = [0.3457 / 0.3585, 1.00000, (1.0 - 0.3457 - 0.3585) / 0.3585]
const d65 = [0.3127 / 0.3290, 1.00000, (1.0 - 0.3127 - 0.3290) / 0.3290]

const bradford = [
    [0.8951000, 0.2664000, -0.1614000],
    [-0.7502000, 1.7135000, 0.0367000],
    [0.0389000, -0.0685000, 1.0296000]
]

const von_kries = [
    [0.4002400, 0.7076000, -0.0808100],
    [-0.2263000, 1.1653200, 0.0457000],
    [0.0000000, 0.0000000, 0.9182200]
]

const cat02 = [
    [0.7328000, 0.4296000, -0.1624000],
    [-0.7036000, 1.6975000, 0.0061000],
    [0.0030000, 0.0136000, 0.9834000]
]

const cat16 = [
    [  0.401288,  0.650173, -0.051461 ],
    [ -0.250268,  1.204414,  0.045854 ],
    [ -0.002079,  0.048952,  0.953127 ]
]

console.log('===== bradford =====')
console.log(bradford)
console.log('===== bradford inverse =====')
console.log(math.inv(bradford))

console.log('===== von kries =====')
console.log(von_kries)
console.log('===== von kries inverse =====')
console.log(math.inv(von_kries))

console.log('===== cat02 =====')
console.log(cat02)
console.log('===== cat02 inverse =====')
console.log(math.inv(cat02))

console.log('===== cat16 =====')
console.log(cat16)
console.log('===== cat16 inverse =====')
console.log(math.inv(cat16))

Here are the results:
===== bradford =====
[
  [ 0.8951, 0.2664, -0.1614 ],
  [ -0.7502, 1.7135, 0.0367 ],
  [ 0.0389, -0.0685, 1.0296 ]
]
===== bradford inverse =====
[
  [ 0.9869929054667121, -0.14705425642099013, 0.15996265166373122 ],
  [ 0.4323052697233945, 0.5183602715367774, 0.049291228212855594 ],
  [ -0.00852866457517732, 0.04004282165408486, 0.96848669578755 ]
]
===== von kries =====
[
  [ 0.40024, 0.7076, -0.08081 ],
  [ -0.2263, 1.16532, 0.0457 ],
  [ 0, 0, 0.91822 ]
]
===== von kries inverse =====
[
  [ 1.8599363874558397, -1.1293816185800916, 0.21989740959619328 ],
  [ 0.3611914362417676, 0.6388124632850422, -0.000006370596838649899 ],
  [ 0, 0, 1.0890636230968613 ]
]
===== cat02 =====
[
  [ 0.7328, 0.4296, -0.1624 ],
  [ -0.7036, 1.6975, 0.0061 ],
  [ 0.003, 0.0136, 0.9834 ]
]
===== cat02 inverse =====
[
  [ 1.0961238208355142, -0.27886900021828726, 0.18274517938277307 ],
  [ 0.4543690419753592, 0.4735331543074117, 0.07209780371722911 ],
  [ -0.009627608738429355, -0.00569803121611342, 1.0153256399545427 ]
]
===== cat16 =====
[
  [ 0.401288, 0.650173, -0.051461 ],
  [ -0.250268, 1.204414, 0.045854 ],
  [ -0.002079, 0.048952, 0.953127 ]
]
===== cat16 inverse =====
[
  [ 1.862067855087233, -1.0112546305316845, 0.14918677544445172 ],
  [ 0.3875265432361372, 0.6214474419314753, -0.008973985167612521 ],
  [ -0.01584149884933386, -0.03412293802851557, 1.0499644368778496 ]
]

I updated with a JS solution and included the script along with the necessary math.js dependency. My aim is mainly to fix the matrices. Any kind of refactoring, if desired, should be possible using math.js. I've provided the reproduction script along with the dependency.

I will state that there may be better JS matrix libraries out there, if a better one is discovered, I completely understand. If this project would like to roll its own inverse method, it is completely doable, though a bit more involved. I've done so with my own project as I do not currently rely on numpy, but implement matrix inverse doing LU decomposition. So a simplied version could be ported here, but that would most likely be something for another PR.


use SVGs from the source dir in .devel

When using ratbagctl.devel we would use the .device files
from the source dir. This patch also makes it use the .svg
files from the source dir. This makes it easier to edit the
svg and less surprising now that it follows the .devices files.
We need to treat the .device and .svg file a bit different. The
reason is that in soure the device files are in a separate dir
'data/devices' but we do not use the 'devices' dir when installed.

I pushed an updated patch with the change to install the .device files into a 'devices' subdirectory to match the source layout.


Github

https://github.com/f-droid

？

Please describe your problem, or I will close this issue later.


Update code in OpenTelemetry section

Change configuration code for OpenTelemetry as old code used obsolete methods to configure traccing and metrics
Summary
Old code used obsolete method for configuring OpenTelemetry. I've rewritten those samples to use not obsolete code.

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

@IEvangelist sure thing, done :D

Hey @Avabin

@IEvangelist sure thing, done :D

You also have to sign the contributor agreement here, then we're good to go - thanks: https://cla.dotnetfoundation.org/dotnet/docs?pullRequest=33991


Linked YouTube Video is not about Azure Active Directory Activity Reports

The embedded YouTube Video is not about Azure Active Directory Activity Reports. Instead it is about Azure Resource Activity Reports.

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

ID: 2763640f-ae78-a69e-0999-2863240dc2ff
Version Independent ID: dd39081a-afd8-dda2-5a08-7cf54bab1fa4
Content: What are Azure Active Directory reports?
Content Source: articles/active-directory/reports-monitoring/overview-reports.md
Service: active-directory
Sub-service: report-monitor
GitHub Login: @MarkusVi
Microsoft Alias: markvi

@diecknet Thank you for catching this . We will investigate and update the thread.

@diecknet We have removed the video for now and are in the process of getting a proper video done and linked to this page.
Thank you.


API mock doesn't work

What happened?
I've tried MSW, Miragejs, axios-mock-adapter and mock-xmlhttprequest to intercept the react-native's xmlhttprequest or http to do api mock in Detox e2e tests, but all failed. However, they works fine in Jest integration tests.
So, I'm wondering if there are some special configs in Detox.
Currently, I can mock API by setting up a local express server as here while running e2e tests. And change the app axios's baseURL to point to the local express api server as the mocking guide says
But above mocking libraries provide many features for testing which is very convenient. It would be better if we can just use those api mocking libraries.
Or do I miss anything?
Thank you
What was the expected behaviour?
we can use those api mocking libraries in e2e tests
Was it tested on latest Detox?

[ ] I have tested this issue on the latest Detox release and it still reproduces.

Help us reproduce this issue!
https://github.com/CoSNaYe/detox-experiment
If api mock successfully, we should see below api response logged in the react-native console.
{ email<EMAIL_ADDRESS>name: 'test user name' }

If api mock failed, we would see a 401 api response instead.
In what environment did this happen?
Detox version: ^19.12.5
React Native version: 0.70.1
Node version: v16.14.0
Test-runner (select one): jest-circus/runner
Detox logs
Detox logs
23:37:18.476 detox[94527] TRACE: [DETOX_CREATE] created a Detox instance with config:
{
  appsConfig: {
    default: {
      type: 'ios.app',
      binaryPath: 'ios/build/Build/Products/Debug-iphonesimulator/AwesomeProject.app',
      build: 'xcodebuild -workspace ios/AwesomeProject.xcworkspace -scheme AwesomeProject -configuration Debug -sdk iphonesimulator -derivedDataPath ios/build'
    }
  },
  artifactsConfig: {
    rootDir: 'artifacts/ios.2022-10-08 15-37-17Z',
    plugins: {
      log: {
        enabled: false,
        keepOnlyFailedTestsArtifacts: false
      },
      screenshot: {
        enabled: true,
        shouldTakeAutomaticSnapshots: false,
        keepOnlyFailedTestsArtifacts: false
      },
      video: {
        enabled: false,
        keepOnlyFailedTestsArtifacts: false
      },
      instruments: {
        enabled: false,
        keepOnlyFailedTestsArtifacts: false
      },
      timeline: {
        enabled: false
      },
      uiHierarchy: {
        enabled: false,
        keepOnlyFailedTestsArtifacts: false
      }
    },
    pathBuilder: ArtifactPathBuilder {
      _rootDir: 'artifacts/ios.2022-10-08 15-37-17Z'
    }
  },
  behaviorConfig: {
    init: {
      reinstallApp: true,
      exposeGlobals: true
    },
    cleanup: {
      shutdownDevice: false
    },
    launchApp: 'auto'
  },
  cliConfig: {
    configuration: 'ios',
    loglevel: 'trace',
    useCustomLogger: true
  },
  configurationName: 'ios',
  deviceConfig: {
    type: 'ios.simulator',
    device: {
      type: 'iPhone 13'
    }
  },
  runnerConfig: {
    testRunner: 'jest',
    runnerConfig: 'e2e/config.js',
    specs: 'e2e',
    skipLegacyWorkersInjection: true
  },
  sessionConfig: {
    autoStart: true,
    sessionId: '728d7154-b2e2-0bab-6838-4cf13a563054',
    debugSynchronization: 10000
  }
}
23:37:18.479 detox[94527] DEBUG: [WSS_CREATE] Detox server listening on localhost:61539...
23:37:18.488 detox[94527] DEBUG: [WSS_CONNECTION, #61540] registered a new connection.
23:37:18.489 detox[94527] TRACE: [WS_OPEN] opened web socket to: ws://localhost:61539
23:37:18.490 detox[94527] TRACE: [WS_SEND] {"type":"login","params":{"sessionId":"728d7154-b2e2-0bab-6838-4cf13a563054","role":"tester"},"messageId":0}
23:37:18.491 detox[94527] TRACE: [WSS_GET_FROM, #61540] {"type":"login","params":{"sessionId":"728d7154-b2e2-0bab-6838-4cf13a563054","role":"tester"},"messageId":0}
23:37:18.491 detox[94527] TRACE: [SESSION_CREATED] created session 728d7154-b2e2-0bab-6838-4cf13a563054
23:37:18.491 detox[94527] TRACE: [WSS_SEND_TO, #tester] {"type":"loginSuccess","params":{"testerConnected":true,"appConnected":false},"messageId":0}
23:37:18.492 detox[94527] TRACE: [SESSION_JOINED] tester joined session 728d7154-b2e2-0bab-6838-4cf13a563054
23:37:18.492 detox[94527] TRACE: [WS_MESSAGE] {"type":"loginSuccess","params":{"testerConnected":true,"appConnected":false},"messageId":0}

23:37:18.597 detox[94527] DEBUG: [EXEC_CMD, #0] applesimutils --list --byType "iPhone 13"
...

23:37:18.787 detox[94527] TRACE: [ARTIFACTS_LIFECYCLE] artifactsManager.onBootDevice({
  deviceId: 'DD740BE5-5DEF-4404-873E-A611FFB61801',
  type: 'ios.simulator',
  coldBoot: false
})
23:37:18.800 detox[94527] TRACE: [ARTIFACTS_LIFECYCLE] artifactsManager.onBeforeTerminateApp({
  deviceId: 'DD740BE5-5DEF-4404-873E-A611FFB61801',
  bundleId: 'org.reactjs.native.example.AwesomeProject'
})
23:37:18.800 detox[94527] DEBUG: [EXEC_CMD, #2] /usr/bin/xcrun simctl terminate DD740BE5-5DEF-4404-873E-A611FFB61801 org.reactjs.native.example.AwesomeProject
23:37:18.800 detox[94527] DEBUG: [EXEC_TRY, #2] Terminating org.reactjs.native.example.AwesomeProject...
23:37:18.885 detox[94527] DEBUG: [EXEC_SUCCESS, #2] org.reactjs.native.example.AwesomeProject terminated
23:37:18.886 detox[94527] TRACE: [ARTIFACTS_LIFECYCLE] artifactsManager.onTerminateApp({
  deviceId: 'DD740BE5-5DEF-4404-873E-A611FFB61801',
  bundleId: 'org.reactjs.native.example.AwesomeProject'
})
23:37:18.886 detox[94527] TRACE: [ARTIFACTS_LIFECYCLE] artifactsManager.onBeforeUninstallApp({
  deviceId: 'DD740BE5-5DEF-4404-873E-A611FFB61801',
  bundleId: 'org.reactjs.native.example.AwesomeProject'
})
23:37:18.887 detox[94527] DEBUG: [EXEC_CMD, #3] /usr/bin/xcrun simctl uninstall DD740BE5-5DEF-4404-873E-A611FFB61801 org.reactjs.native.example.AwesomeProject
23:37:18.887 detox[94527] DEBUG: [EXEC_TRY, #3] Uninstalling org.reactjs.native.example.AwesomeProject...
23:37:18.990 detox[94527] DEBUG: [EXEC_SUCCESS, #3] org.reactjs.native.example.AwesomeProject uninstalled
23:37:18.991 detox[94527] TRACE: [ARTIFACTS_LIFECYCLE] artifactsManager.onBeforeTerminateApp({
  deviceId: 'DD740BE5-5DEF-4404-873E-A611FFB61801',
  bundleId: 'org.reactjs.native.example.AwesomeProject'
})
23:37:18.991 detox[94527] DEBUG: [EXEC_CMD, #4] /usr/bin/xcrun simctl terminate DD740BE5-5DEF-4404-873E-A611FFB61801 org.reactjs.native.example.AwesomeProject
23:37:18.991 detox[94527] DEBUG: [EXEC_TRY, #4] Terminating org.reactjs.native.example.AwesomeProject...
23:37:20.070 detox[94527] TRACE: [EXEC_TRY_FAIL, #4] An error was encountered processing the command (domain=NSPOSIXErrorDomain, code=3):
Application termination failed.
FBSSystemService reported failure without an error, possibly because the app is not currently running.

23:37:20.070 detox[94527] DEBUG: [EXEC_TRY, #4] Terminating org.reactjs.native.example.AwesomeProject...
23:37:20.166 detox[94527] DEBUG: [EXEC_FAIL, #4] "/usr/bin/xcrun simctl terminate DD740BE5-5DEF-4404-873E-A611FFB61801 org.reactjs.native.example.AwesomeProject" failed with error = ChildProcessError: Command failed: /usr/bin/xcrun simctl terminate DD740BE5-5DEF-4404-873E-A611FFB61801 org.reactjs.native.example.AwesomeProject
An error was encountered processing the command (domain=NSPOSIXErrorDomain, code=3):
Application termination failed.
FBSSystemService reported failure without an error, possibly because the app is not currently running.
 `/usr/bin/xcrun simctl terminate DD740BE5-5DEF-4404-873E-A611FFB61801 org.reactjs.native.example.AwesomeProject` (exited with error code 3) (code=3), stdout and stderr:

23:37:20.167 detox[94527] DEBUG: [EXEC_FAIL, #4]
23:37:20.167 detox[94527] DEBUG: [EXEC_FAIL, #4] An error was encountered processing the command (domain=NSPOSIXErrorDomain, code=3):
Application termination failed.
FBSSystemService reported failure without an error, possibly because the app is not currently running.

23:37:20.167 detox[94527] TRACE: [ARTIFACTS_LIFECYCLE] artifactsManager.onTerminateApp({
  deviceId: 'DD740BE5-5DEF-4404-873E-A611FFB61801',
  bundleId: 'org.reactjs.native.example.AwesomeProject'
})
23:37:20.167 detox[94527] DEBUG: [EXEC_CMD, #5] /usr/bin/xcrun simctl install DD740BE5-5DEF-4404-873E-A611FFB61801 "/Users/iancosnaye/developer/poc/AwesomeProject/ios/build/Build/Products/Debug-iphonesimulator/AwesomeProject.app"
23:37:20.167 detox[94527] DEBUG: [EXEC_TRY, #5] Installing /Users/iancosnaye/developer/poc/AwesomeProject/ios/build/Build/Products/Debug-iphonesimulator/AwesomeProject.app...
23:37:21.362 detox[94527] DEBUG: [EXEC_SUCCESS, #5] /Users/iancosnaye/developer/poc/AwesomeProject/ios/build/Build/Products/Debug-iphonesimulator/AwesomeProject.app installed
23:37:21.677 ROOT_DESCRIBE_BLOCK[94527] TRACE: [ARTIFACTS_LIFECYCLE] artifactsManager.onRunDescribeStart({ name: 'ROOT_DESCRIBE_BLOCK' })
23:37:21.678 Example[94527] TRACE: [ARTIFACTS_LIFECYCLE] artifactsManager.onRunDescribeStart({ name: 'Example' })
23:37:21.678 detox[94527] INFO:  Example is assigned to DD740BE5-5DEF-4404-873E-A611FFB61801 (iPhone 13)
23:37:21.679 detox[94527] TRACE: [ARTIFACTS_LIFECYCLE] artifactsManager.onBeforeTerminateApp({
  deviceId: 'DD740BE5-5DEF-4404-873E-A611FFB61801',
  bundleId: 'org.reactjs.native.example.AwesomeProject'
})
23:37:21.679 detox[94527] DEBUG: [EXEC_CMD, #6] /usr/bin/xcrun simctl terminate DD740BE5-5DEF-4404-873E-A611FFB61801 org.reactjs.native.example.AwesomeProject
23:37:21.679 detox[94527] DEBUG: [EXEC_TRY, #6] Terminating org.reactjs.native.example.AwesomeProject...
23:37:21.683 detox[94527] INFO:  at __mocks__/express.js:14:11
 Example app listening on port 3000
23:37:22.759 detox[94527] TRACE: [EXEC_TRY_FAIL, #6] An error was encountered processing the command (domain=NSPOSIXErrorDomain, code=3):
Application termination failed.
FBSSystemService reported failure without an error, possibly because the app is not currently running.

23:37:22.759 detox[94527] DEBUG: [EXEC_TRY, #6] Terminating org.reactjs.native.example.AwesomeProject...
23:37:22.862 detox[94527] DEBUG: [EXEC_FAIL, #6] "/usr/bin/xcrun simctl terminate DD740BE5-5DEF-4404-873E-A611FFB61801 org.reactjs.native.example.AwesomeProject" failed with error = ChildProcessError: Command failed: /usr/bin/xcrun simctl terminate DD740BE5-5DEF-4404-873E-A611FFB61801 org.reactjs.native.example.AwesomeProject
An error was encountered processing the command (domain=NSPOSIXErrorDomain, code=3):
Application termination failed.
FBSSystemService reported failure without an error, possibly because the app is not currently running.
 `/usr/bin/xcrun simctl terminate DD740BE5-5DEF-4404-873E-A611FFB61801 org.reactjs.native.example.AwesomeProject` (exited with error code 3) (code=3), stdout and stderr:

23:37:22.863 detox[94527] DEBUG: [EXEC_FAIL, #6]
23:37:22.863 detox[94527] DEBUG: [EXEC_FAIL, #6] An error was encountered processing the command (domain=NSPOSIXErrorDomain, code=3):
Application termination failed.
FBSSystemService reported failure without an error, possibly because the app is not currently running.

23:37:22.863 detox[94527] TRACE: [ARTIFACTS_LIFECYCLE] artifactsManager.onTerminateApp({
  deviceId: 'DD740BE5-5DEF-4404-873E-A611FFB61801',
  bundleId: 'org.reactjs.native.example.AwesomeProject'
})
23:37:22.864 detox[94527] TRACE: [ARTIFACTS_LIFECYCLE] artifactsManager.onBeforeLaunchApp({
  bundleId: 'org.reactjs.native.example.AwesomeProject',
  deviceId: 'DD740BE5-5DEF-4404-873E-A611FFB61801',
  launchArgs: {
    detoxServer: 'ws://localhost:61539',
    detoxSessionId: '728d7154-b2e2-0bab-6838-4cf13a563054'
  }
})
23:37:22.864 detox[94527] DEBUG: [EXEC_CMD, #7] SIMCTL_CHILD_GULGeneratedClassDisposeDisabled=YES SIMCTL_CHILD_DYLD_INSERT_LIBRARIES="/Users/iancosnaye/Library/Detox/ios/50883fdb70e0e6914340505907d8d3c4081cb390/Detox.framework/Detox" /usr/bin/xcrun simctl launch DD740BE5-5DEF-4404-873E-A611FFB61801 org.reactjs.native.example.AwesomeProject --args -detoxServer ws://localhost:61539 -detoxSessionId 728d7154-b2e2-0bab-6838-4cf13a563054 -detoxDisableHierarchyDump YES
23:37:22.864 detox[94527] DEBUG: [EXEC_TRY, #7] Launching org.reactjs.native.example.AwesomeProject...
23:37:22.961 detox[94527] TRACE: [EXEC_SUCCESS, #7] org.reactjs.native.example.AwesomeProject: 94572

23:37:22.962 detox[94527] DEBUG: [EXEC_CMD, #8] /usr/bin/xcrun simctl get_app_container DD740BE5-5DEF-4404-873E-A611FFB61801 org.reactjs.native.example.AwesomeProject
23:37:23.054 detox[94527] TRACE: [EXEC_SUCCESS, #8] /Users/iancosnaye/Library/Developer/CoreSimulator/Devices/DD740BE5-5DEF-4404-873E-A611FFB61801/data/Containers/Bundle/Application/40ED978B-F92C-417E-87A7-E966059681B0/AwesomeProject.app

23:37:23.060 detox[94527] INFO:  [AppleSimUtils.js] org.reactjs.native.example.AwesomeProject launched. To watch simulator logs, run:
        /usr/bin/xcrun simctl spawn DD740BE5-5DEF-4404-873E-A611FFB61801 log stream --level debug --style compact --predicate 'process == "AwesomeProject"'
23:37:23.061 detox[94572] TRACE: [ARTIFACTS_LIFECYCLE] artifactsManager.onLaunchApp({
  bundleId: 'org.reactjs.native.example.AwesomeProject',
  deviceId: 'DD740BE5-5DEF-4404-873E-A611FFB61801',
  launchArgs: {
    detoxServer: 'ws://localhost:61539',
    detoxSessionId: '728d7154-b2e2-0bab-6838-4cf13a563054',
    detoxDisableHierarchyDump: 'YES'
  },
  pid: 94572
})
23:37:23.173 detox[94527] DEBUG: [WSS_CONNECTION, #61558] registered a new connection.
23:37:23.295 detox[94527] TRACE: [WSS_GET_FROM, #61558] {"params":{"role":"app","sessionId":"728d7154-b2e2-0bab-6838-4cf13a563054"},"type":"login","messageId":0}
23:37:23.295 detox[94527] TRACE: [WSS_SEND_TO, #app] {"params":{"testerConnected":true,"appConnected":true},"type":"loginSuccess","messageId":0}
23:37:23.295 detox[94527] TRACE: [SESSION_JOINED] app joined session 728d7154-b2e2-0bab-6838-4cf13a563054
23:37:23.295 detox[94527] TRACE: [WSS_SEND_TO, #tester] {"type":"appConnected"}
23:37:23.296 detox[94527] TRACE: [WS_MESSAGE] {"type":"appConnected"}

23:37:23.296 detox[94527] TRACE: [WS_SEND] {"type":"isReady","params":{},"messageId":-1000}
23:37:23.297 detox[94527] TRACE: [WSS_GET_FROM, #tester] {"type":"isReady","params":{},"messageId":-1000}
23:37:23.297 detox[94527] TRACE: [WSS_SEND_TO, #app] {"type":"isReady","params":{},"messageId":-1000}
23:37:24.699 detox[94527] TRACE: [WSS_GET_FROM, #app] {"params":{},"type":"ready","messageId":-1000}
23:37:24.700 detox[94527] TRACE: [WSS_SEND_TO, #tester] {"params":{},"type":"ready","messageId":-1000}
23:37:24.700 detox[94527] TRACE: [WS_MESSAGE] {"params":{},"type":"ready","messageId":-1000}

23:37:24.702 detox[94527] TRACE: [WS_SEND] {"type":"waitForActive","params":{},"messageId":1}
23:37:24.703 detox[94527] TRACE: [WSS_GET_FROM, #tester] {"type":"waitForActive","params":{},"messageId":1}
23:37:24.703 detox[94527] TRACE: [WSS_SEND_TO, #app] {"type":"waitForActive","params":{},"messageId":1}
23:37:24.704 detox[94527] TRACE: [WSS_GET_FROM, #app] {"params":{},"type":"ready","messageId":-1000}
23:37:24.704 detox[94527] TRACE: [WSS_SEND_TO, #tester] {"params":{},"type":"ready","messageId":-1000}
23:37:24.704 detox[94527] TRACE: [WS_MESSAGE] {"params":{},"type":"ready","messageId":-1000}

23:37:24.704 detox[94527] TRACE: [WSS_GET_FROM, #app] {"params":{},"type":"ready","messageId":-1000}
23:37:24.704 detox[94527] TRACE: [WSS_SEND_TO, #tester] {"params":{},"type":"ready","messageId":-1000}
23:37:24.705 detox[94527] TRACE: [WS_MESSAGE] {"params":{},"type":"ready","messageId":-1000}

23:37:24.705 detox[94527] TRACE: [WSS_GET_FROM, #app] {"params":{},"type":"waitForActiveDone","messageId":1}
23:37:24.706 detox[94527] TRACE: [WSS_SEND_TO, #tester] {"params":{},"type":"waitForActiveDone","messageId":1}
23:37:24.706 detox[94527] TRACE: [WS_MESSAGE] {"params":{},"type":"waitForActiveDone","messageId":1}

23:37:24.706 detox[94572] TRACE: [ARTIFACTS_LIFECYCLE] artifactsManager.onAppReady({
  deviceId: 'DD740BE5-5DEF-4404-873E-A611FFB61801',
  bundleId: 'org.reactjs.native.example.AwesomeProject',
  pid: 94572
})
23:37:24.708 detox[94527] INFO:  Example: api mocking failed by axios-mock-adapter
23:37:24.709 detox[94527] TRACE: [DETOX_BEFORE_EACH] running test: "Example api mocking failed by axios-mock-adapter"
23:37:24.710 detox[94527] TRACE: [ARTIFACTS_LIFECYCLE] artifactsManager.onTestStart({
  title: 'api mocking failed by axios-mock-adapter',
  parent: 'Example',
  fullName: 'Example api mocking failed by axios-mock-adapter',
  functionCode: 'function () {\n' +
    '    var self = this,\n' +
    '        args = arguments;\n' +
    '    return new Promise(function (resolve, reject) {\n' +
    '      var gen = fn.apply(self, args);\n' +
    '\n' +
    '      function _next(value) {\n' +
    '        asyncGeneratorStep(gen, resolve, reject, _next, _throw, "next", value);\n' +
    '      }\n' +
    '\n' +
    '      function _throw(err) {\n' +
    '        asyncGeneratorStep(gen, resolve, reject, _next, _throw, "throw", err);\n' +
    '      }\n' +
    '\n' +
    '      _next(undefined);\n' +
    '    });\n' +
    '  }',
  invocations: 1,
  status: 'running'
})
23:37:24.712 detox[94527] TRACE: [WS_SEND] {"type":"reactNativeReload","params":{},"messageId":-1000}
23:37:24.712 detox[94527] TRACE: [WSS_GET_FROM, #tester] {"type":"reactNativeReload","params":{},"messageId":-1000}
23:37:24.713 detox[94527] TRACE: [WSS_SEND_TO, #app] {"type":"reactNativeReload","params":{},"messageId":-1000}
23:37:24.996 detox[94527] TRACE: [WSS_GET_FROM, #app] {"messageId":-1000,"type":"ready","params":{}}
23:37:24.996 detox[94527] TRACE: [WSS_SEND_TO, #tester] {"messageId":-1000,"type":"ready","params":{}}
23:37:24.996 detox[94527] TRACE: [WS_MESSAGE] {"messageId":-1000,"type":"ready","params":{}}

23:37:24.998 detox[94527] TRACE: [WS_SEND] {"type":"invoke","params":{"type":"action","action":"tap","predicate":{"type":"id","value":"login-submit-btn"}},"messageId":2}
23:37:24.998 detox[94527] TRACE: [WSS_GET_FROM, #tester] {"type":"invoke","params":{"type":"action","action":"tap","predicate":{"type":"id","value":"login-submit-btn"}},"messageId":2}
23:37:24.998 detox[94527] TRACE: [WSS_SEND_TO, #app] {"type":"invoke","params":{"type":"action","action":"tap","predicate":{"type":"id","value":"login-submit-btn"}},"messageId":2}
23:37:26.221 detox[94527] TRACE: [WSS_GET_FROM, #app] {"type":"invokeResult","params":{},"messageId":2}
23:37:26.221 detox[94527] TRACE: [WSS_SEND_TO, #tester] {"type":"invokeResult","params":{},"messageId":2}
23:37:26.221 detox[94527] TRACE: [WS_MESSAGE] {"type":"invokeResult","params":{},"messageId":2}

23:37:26.223 detox[94527] TRACE: [DETOX_AFTER_EACH] passed test: "Example api mocking failed by axios-mock-adapter"
23:37:26.223 detox[94527] TRACE: [ARTIFACTS_LIFECYCLE] artifactsManager.onTestDone({
  title: 'api mocking failed by axios-mock-adapter',
  parent: 'Example',
  fullName: 'Example api mocking failed by axios-mock-adapter',
  functionCode: 'function () {\n' +
    '    var self = this,\n' +
    '        args = arguments;\n' +
    '    return new Promise(function (resolve, reject) {\n' +
    '      var gen = fn.apply(self, args);\n' +
    '\n' +
    '      function _next(value) {\n' +
    '        asyncGeneratorStep(gen, resolve, reject, _next, _throw, "next", value);\n' +
    '      }\n' +
    '\n' +
    '      function _throw(err) {\n' +
    '        asyncGeneratorStep(gen, resolve, reject, _next, _throw, "throw", err);\n' +
    '      }\n' +
    '\n' +
    '      _next(undefined);\n' +
    '    });\n' +
    '  }',
  invocations: 1,
  status: 'passed',
  errors: undefined,
  asyncError: undefined,
  timedOut: false
})
23:37:26.224 detox[94527] INFO:  Example: api mocking failed by axios-mock-adapter [OK]
23:37:26.226 Example[94527] TRACE: [ARTIFACTS_LIFECYCLE] artifactsManager.onRunDescribeFinish({ name: 'Example' })

23:37:26.227 ROOT_DESCRIBE_BLOCK[94527] TRACE: [ARTIFACTS_LIFECYCLE] artifactsManager.onRunDescribeFinish({ name: 'ROOT_DESCRIBE_BLOCK' })
23:37:26.228 detox[94527] TRACE: [ARTIFACTS_LIFECYCLE] artifactsManager.onBeforeCleanup()
23:37:26.229 detox[94527] TRACE: [WS_SEND] {"type":"cleanup","params":{"stopRunner":true},"messageId":-49642}
23:37:26.230 detox[94527] TRACE: [WSS_GET_FROM, #tester] {"type":"cleanup","params":{"stopRunner":true},"messageId":-49642}
23:37:26.230 detox[94527] TRACE: [WSS_SEND_TO, #app] {"type":"cleanup","params":{"stopRunner":true},"messageId":-49642}
23:37:26.231 detox[94527] TRACE: [WSS_GET_FROM, #app] {"messageId":-49642,"type":"cleanupDone","params":{}}
23:37:26.231 detox[94527] TRACE: [WSS_SEND_TO, #tester] {"messageId":-49642,"type":"cleanupDone","params":{}}
23:37:26.231 detox[94527] TRACE: [WS_MESSAGE] {"messageId":-49642,"type":"cleanupDone","params":{}}

Device logs
Device logs
23:35:35.608 detox[94364] INFO:  [test.js] DETOX_CONFIGURATION="ios" DETOX_RECORD_LOGS="all" DETOX_REPORT_SPECS=true DETOX_START_TIMESTAMP=1665243335605 DETOX_USE_CUSTOM_LOGGER=true jest --config e2e/config.js --testNamePattern '^((?!:android:).)*$' e2e
watchman warning:  Recrawled this watch 3 times, most recently because:
MustScanSubDirs UserDroppedTo resolve, please review the information on
https://facebook.github.io/watchman/docs/troubleshooting.html#recrawl
To clear this warning, run:
`watchman watch-del '/Users/iancosnaye/developer/poc/AwesomeProject' ; watchman watch-project '/Users/iancosnaye/developer/poc/AwesomeProject'`

23:35:39.340 detox[94365] INFO:  Example is assigned to DD740BE5-5DEF-4404-873E-A611FFB61801 (iPhone 13)
23:35:39.347 detox[94365] INFO:  at __mocks__/express.js:14:11
 Example app listening on port 3000
23:35:40.953 detox[94365] INFO:  [AppleSimUtils.js] org.reactjs.native.example.AwesomeProject launched.
No response

Please follow the mocking guide https://wix.github.io/Detox/docs/guide/mocking

@noomorph thanks for your prompt reply. Yes, I've read the mocking guide. But it seems that instruct us to point to a local api server which is the same as I did about setting up a local express server instead of using those api mocking libraries' utilities right? Or do I misunderstand?

How does your app know it needs to go for the mock server? Where do you switch the railroads? Where is your alternative file next to the original file? Where does Metro bundler pick it instead of the original one?

Sorry, please correct me if i am wrong.
The purpose of .mock.js thing listed in the mocking guide seems to switch the api endpoint from production endpoint to local mocking server. I know how to do the switch if for this approach.
But what i'm seeking is just letting the libraries intercept the xmlhttprequest automatically instead of pointing to another endpoint.
Or do you mean I should setup .mock.js files for automatically intercepts even not for switching the api point?

@CoSNaYe , I was able to mock with axios-mock-adapter using detox. I used a different axios instance to call Api when in detox test mode.

@faizandebugger could you kindly share how you do it? thanks!


nixos-tests: bring back quake3 test

Description of changes

Things done

Built on platform(s)

[ ] 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
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.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
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

I think in the current state, hydra will build this? Not sure if that's desirable. But this is definitely a really cool demo for showcasing the power of NixOS tests in a very tangible way, and is worth keeping around.

Hm, I've been reminded that we have the openarena test as a ~replacement for this. I still think having something well-known like quake is nice though.

Never underestimate the effectiveness of Quake3 for evaluating operating system performance.


Added Create Ped api

Added Create Ped api
Added Async Create Ped api

I'm looking for workaround to create ped in async context in C# server resource, is it possible? AltVAsync is inaccesible from resource code

I'm looking for workaround to create ped in async context in C# server resource, is it possible? AltVAsync is inaccesible from resource code


messenger and telegram UNKOWN_URL_SCHEME

I have an issue with url_launcher: ^6.1.3, flutter version 3.0.1, and dart version 2.17.1  when lunch to messenger and telegram.

Hi @KuntheasSoung
This issue doesn't seem to describe a bug or a feature request. Please see https://flutter.dev/community for resources and asking questions like this,
you may also get some help if you post it on Stack Overflow and if you need help with your code, please see https://www.reddit.com/r/flutterhelp/
Closing, as this isn't an issue with Flutter itself. If you disagree, please write in the comments and I will reopen it.
Thank you


Overriding Written By Image

the image displayed in the Written By section seems to be hardcoded
https://github.com/binokochumolvarghese/lightbi-hugo/blob/201e52f53b75b0f86b35bbb76b0d0beed2974dcc/layouts/_default/single.html#L54
Should this be a value that can be overridden ?

nevermind, just created static/img/bino-about-small.jpg