Alchemy polishing

Scope
Assortment of small changes to Alchemy to improve the overall feel of gameplay.
Suggestion

[x] Reduce flowrates through conduits, capacity to make reagent movement less instant, more controllable, more visible, and reduce reagent storage in the conduits themselves
[x] Change reagent quantities and capacities to be based on stack sizes (multiples of 64/32/8) instead of multiples of 10
[ ] Improve the graphic for reagents in conduits/vessels/etc
[x] Overhaul the glassware stand so that automation can insert/remove glassware
[ ] Make changing the temperature of reagents use non-negligible amounts of heat from heat cables
[ ] Add the ability to charge FE-storing items from other mods (instead of just leyden jars)

ange or replace the limiter conduit to not be a single-purpose single-solution for controlling quantities in reaction vessels
Justification
While most every other part of the mod has been reworked multiple times since first being introduced, Alchemy has been basically unchanged (other than a few additions) from the first public release. While it's held up pretty well, it's generally overdue for a bit of polishing to bring it up to the standards of the rest of the mod.
Impact
Balance and progression will be basically unchanged, but a lot of the jankiness in Alchemy should be fixed. Automating some of the special reactions (ignis infernum, making philospher's stone, etc) will be a bit more difficult.

Linking relevant commit: dd01ac6

Related: 8fdcbb9


Text widget shows a wrong behaivor in IE11

I just want to show listview, it's a very simple listview using ListTitle.
The result is ok in Chrome, Safari, Firefox except in IE11 or Edge.
If you show a long text in Text widget as title or subTitle in ListTitle, and  when you narrow the window of IE11,  and before the width is the larger than or the same as text length, all is ok. But when the width is shorter than text length, title or subTitle will become 2 rows and take a very large space, that is to say, the whole window of IE11 will only show one item of ListView.
1、snapshot
1
2
3
4
2、flutter doctor -v
> [✓] Flutter (Channel beta, v1.17.0, on Mac OS X 10.15.1 19B88, locale
    zh-Hans-CN)
    • Flutter version 1.17.0 at /Users/sun/development/flutter
    • Framework revision d3ed9ec945 (10 days ago), 2020-04-06 14:07:34 -0700
    • Engine revision c9506cb8e9
    • Dart version 2.8.0 (build 2.8.0-dev.18.0 eea9717938)

> [✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
    • Android SDK at /Users/sun/Library/Android/sdk
    • Platform android-R, build-tools 29.0.2
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_212-release-1586-b4-5784211)
    • All Android licenses accepted.

> [✓] Xcode - develop for iOS and macOS (Xcode 11.3.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.3.1, Build version 11C504
    • CocoaPods version 1.8.4

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

> [✓] Android Studio (version 3.6)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 45.1.1
    • Dart plugin version 192.7761
    • Java version OpenJDK Runtime Environment (build
      1.8.0_212-release-1586-b4-5784211)

> [!] IntelliJ IDEA Community Edition (version 2020.1)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
    • For information about installing plugins, see
      https://flutter.dev/intellij-setup/#installing-the-plugins

> [✓] VS Code (version 1.41.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.7.1

> [✓] Connected device (2 available)
    • Chrome     • chrome     • web-javascript • Google Chrome 81.0.4044.113
    • Web Server • web-server • web-javascript • Flutter Tools

3、my code
(1) article widget
import 'package:flutter/material.dart';

import 'entity/article.dart';

class ArticlesPage extends StatefulWidget {
  @override
  _ArticlesPageState createState() => _ArticlesPageState();
}

class _ArticlesPageState extends State<ArticlesPage>
    with AutomaticKeepAliveClientMixin {
  @override
  bool get wantKeepAlive => true;

  List<Article> articles = [
    Article(title: "00%sRGB屏幕！这款游戏本“等等党”值得期待",
        description: "联想在其官方微博@联想拯救者发布消息，2020款拯救者Y7000/R7000屏幕色彩和亮度表现全面提升，同时官方还表示“将开启游戏本的高色域普及风暴！”",
        picture:"images/01.jpg"),
    Article(title: "买QLC SSD=买垃圾？别冤枉好人！淘汰HDD就靠它了",
        description: "现在舆论都说QLC固态硬盘是垃圾，那么它真的是垃圾吗？今天就和大家讨论一下这个问题，毕竟现在大家都把QLC SSD视为洪水猛兽。",
        picture:"images/02.jpg"),
    Article(title: "曝Android超级恶意软件 重置仍可自动安装",
        description: "一款名为xHelper的Android超级恶意软件正在肆意传播。之所以定级为“超级”，原因在于用户一旦被xHelper感染，即便删除甚至恢复原厂设置，该病毒仍能在被感染的设备上重新安装。",
        picture:"images/03.jpg")
  ];

  @override
  Widget build(BuildContext context) {
    super.build(context);
    return Scaffold(
      //appBar: AppBar(title: Text('Home'),),
      body: Padding(
        padding: const EdgeInsets.symmetric(vertical: 16.0, horizontal: 8.0),
        child: ListView.separated(
          itemCount: articles.length,
          separatorBuilder: (context, index) {
            return Divider(
                indent: 8.0,
                endIndent: 8.0,
                thickness: 0.2,
                color: Colors.grey);
          },
          itemBuilder: (context, index) {
            return buildItem1(index);
          },
        ),
      ),
    );
  }

  Widget buildItem1(int index) {
    return ListTile(
        title: Container(
          color: Colors.amberAccent,
          child: Text(
            articles[index].title,
            overflow: TextOverflow.clip,
            style: TextStyle(
                color: index == 0 ? Colors.deepOrange : Colors.black),
          ),
        ),
        leading: Image.network(
          '${articles[index].picture}',
          width: 80,
          height: 60,
        ),
        subtitle: Container(
          color: Colors.black26,
          child: Text(
              articles[index].description,
              //maxLines: 4,
              overflow: TextOverflow.visible,
              textAlign: TextAlign.justify
          ),
        ),
        onTap: () => {}
    );
  }

}

(2)Article class
class Article {
  String description;
  String picture;
  String title;

  Article(
      {this.description,
        this.picture,
        this.title});

}

4、how to repoduce
It's easy, just build web application, and visit it using Microsoft IE 11.
You can see the wrong behaivor the same as you narrow the width of the IE11 window.

Hi @sunslife
could you please provide the link to the static website you tested in screenshot above
thank you

Hi @sunslife
could you please provide the link to the static website you tested in screenshot above
thank you
related to #53218

Thanks you for your quick reply!
I have upload the website in https://sunslife.github.io, You can see the result. Hope to hear good news.

Hi again @sunslife
thank you for the link

/cc @mdebbar

I found another problem.  when I use "Web Server(Web)" selected from Android Studio as a web server, and use safari to browse the web app,  and when I narrow the width of the window of safari, all pictures whose links start with "http://localhost" are blinking. I entered the development mode of safari, I saw the response type of those pictures became "Content-Type: text/plain; charset=utf-8", so when I changed the size of safari window, safari reloaded those pictures again and again and made the pictures blinking again and again.
Here is the network info:

摘要
URL: http://localhost:49549/images/02.jpg
状态: 304 Not Modified
来源: 内存缓存
地址: ::1.49549
初始化程序:
html_image_codec.dart:149
请求
GET /images/02.jpg HTTP/1.1
Accept: image/png,image/svg+xml,image/;q=0.8,video/;q=0.8,/;q=0.5
Cookie: _ga=GA1.1.685050703.1583800937
Accept-Encoding: gzip, deflate
If-None-Match: 2020-04-16T15:17:47.000/Users/sun/Desktop/FlutterDev/flutter_web_04/web/images/02.jpg
Host: localhost:49549
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_1) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/13.0.3 Safari/605.1.15
Accept-Language: zh-cn
Referer: http://localhost:49549/
Connection: keep-alive
响应
HTTP/1.1 304 Not Modified
X-Content-Type-Options: nosniff
Content-Type: text/plain; charset=utf-8
Date: Sat, 18 Apr 2020 00:19:02 GMT
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
Content-Length: 0
Server: dart:io with Shelf

The problem only happens in safari browser when I use "Web Server(Web)" as a web server. There are some snapshot:
13
14
15: some times you will see ...
16: some times you will see ...

/cc @mdebbar

What's the meanings of " Goals milestone"? It means they "are worth fixing in the coming years"?
Although Chrome has a larger market share, Microsoft Windows has still an absolutely large market share in PC, that is to say ,  a very large numbers of users are using IE11 /Edge browsers.  If this basic problem cannot be solved as quick as possible, at least with a few months, HOW will we face those customs "in the recent years"?
So please change the timeline.
Thanks a lot.

Today, I did more test about  the wrong behaivor of Text widget in Windows_10_LTS_1607 and Windows_10_LTS_1903. The conclusion is that the wrong behaivor of Text widget appears in IE11of all windows versions  ,while Edge browser worked well.
I think there still many people use IE11, and I checked the market share in 2019, it is about 5%. This is a number that cannot be ignored

If It's possible ,please let flutter web app can be run in IE9/10.

@yjbanov
https://trusting-villani-fa0e54.netlify.app/#/
Not able to reproduce this issue, beta, and master, both show a blank page on IE 11, same issue on canvaskit as well
Is IE 11 still supported?

flutter doctor -v
[✓] Flutter (Channel master, 1.22.0-10.0.pre.39, on Mac OS X 10.15.6 19G2021, locale en-GB)
    • Flutter version 1.22.0-10.0.pre.39 at /Users/tahatesser/Code/flutter_master
    • Framework revision a8281e31af (18 hours ago), 2020-09-01 10:57:59 -0700
    • Engine revision 165abef0a2
    • Dart version 2.10.0 (build 2.10.0-77.0.dev)

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

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

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

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

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

[✓] Connected device (5 available)
    • Taha’s iPhone (mobile) • 00008020-001059882212002E            • ios            • iOS 13.7
    • iPhone 11 (mobile)     • EDB19945-0B9F-4A6E-BAA1-425E68E3B6D6 • ios            •
      com.apple.CoreSimulator.SimRuntime.iOS-13-7 (simulator)
    • macOS (desktop)        • macos                                • darwin-x64     • Mac OS X
      10.15.6 19G2021
    • Web Server (web)       • web-server                           • web-javascript • Flutter
      Tools
    • Chrome (web)           • chrome                               • web-javascript • Google
      Chrome 85.0.4183.83

• No issues found!

IE11 is no longer supported


chore Don't build useless third-party stuff

Proposed changes
Issue Number: close #xxx
Problem summary
On macOS, we need some extra libraries to build the codebase, therefore two packages were introduced to the project. They are binutils and gettext.
It takes a lot of time to build these packages completely. This PR introduces a way to build the needed libraries and other stuff are skipped to build. It can save the time to build the third-party libraries on macOS.
Checklist(Required)

Does it affect the original behavior:

[ ] Yes
[x] No
[ ] I don't know

Has unit tests been added:

[ ] Yes
[ ] No
[x] No Need

Has document been added or modified:

[ ] Yes
[ ] No
[x] No Need

Does it need to update dependencies:

[ ] Yes
[x] No

Are there any changes that cannot be rolled back:

[ ] Yes (If Yes, please explain WHY)
[x] No

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 35.57 seconds
load time: 485 seconds
storage size:<PHONE_NUMBER>1 Bytes
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20230110084507_clickbench_pr_76611.html


improve git functionality for vapor new

Currently every project created with vapor new is based on the vapor example project. That results in boilerplate code which is more suitable for demonstration purposes than actual starting ground for new projects. In example the mustache example functionality and dependency likely is going to be removed every time.
The solution would be to introduce the example argument for the vapor command line application, which creates an new project based on the example.
In parallel the new argument will be modified to create a barebone project with just the minimal content necessary to get going (requires a new repository as a source). In addition there is an option (argument --template, other suggestions welcome) to specify the repository to use as the template for creating a new project.
This enables new starting points when creating new projects.
Example
vapor new Vaporizer

Creates a new project in the Vaporizer directory based on the minimal, default project template. Invokes dependency installation and build automatically (vapor build).
vapor new Vaporizer --template=https://github.com/alomvar/vapor-blog-template

Creates a new project in the Vaporizer directory based on the provided project template (a Git repository). Invokes dependency installation and build automatically (vapor build).
vapor example

Creates a new project in VaporExample based on the official Vapor example project. Invokes dependency installation and build automatically (vapor build) and runs it afterwards.

Can we merge #214 and #215 into a more comprehensive issue about improving the vapor new functionality?

We could, it just seemed to be a good idea to keep this actually separate concerns in separate issues and pull requests, even though they are simple. By experience doing small steps is better than a big leap.

That makes sense. But, I'm pretty sure this could be handled in one PR and won't be very much code. If it were big, unrelated features that would make more sense to keep them separate.

I left out #214 because I already created a branch and by now there already is a badly named pull request (#222). Thinking and rewriting the issue shows that combining #215 and #216 actually is a good idea.

You can change all of the information in a PR, including the name. GitHub is very dynamic. :)

By stripping down the Vapor example to essential parts I created a new project template:
https://github.com/alomvar/vapor-template
Please take a look. Further steps would be agreeing on it and then moving it to qutheory so changes to the Vapor CLI can be made.

I'd like to at least include the Controllers, Models, Middleware folders, even if their empty. We can just put a .gitignore or .gitempty in them, right?

Yeah, right, at first I thought more minimal, less opinionated would be better but without controllers, models and alike there actually is no point to use Vapor instead of in example static HTML files.

I added the directories with .gitignore files and upgraded it to Vapor 0.8

I added the directories with .gitignore files and upgraded it to Vapor 0.8
Closing this issue was not intended.

What would you think about vapor new <name> automatically using the template version and a new command like vapor example cloning and running the example?

I am not sure what you mean, maybe I just described my idea not clear enough. I updated the issue comment above with examples. However I picked up on the idea that providing a name for creating the example project is not necessary. But I think it is still for normally creating a new project.
In case of the example, running it would be another nice addition, too.

@tannernelson @alomvar I think using urls gives the user more control although I don't have anything against named templates. Maybe we should take a look on how heroku handles buildpacks?

It depends how many named templates should be available. If there a few, official and well maintained that is easy to do with a dictionary inside the Vapor CLI. Otherwise it would require some additional infrastructure and thus hassle (if I did not forget something).
I assume there will be an official Swift package registry at some time which can handle the resolution of names to repositories, as it happens with in example Composer packages on Packagist. As long as Swift package manager itself relies on Git repository URLs we should maybe do so, too.
Anyway, named templates or not, repository URLs should be possible either way.

@alomvar the updated issue comment looks perfect :+1:

I really like the idea of implementing a url parameter, perhaps we need some way to define what exactly a template is and how we interact with it. It could be as simple as an empty repo that we clone completely.
This will affect some parts of our tooling, for example, some features rely on the application being named App. This isn't an actual requirement, but it is a requirement of our CLI and it would be nice to be able to evaluate a template.
Maybe include a mention like:
This template doesn't appear to be a properly formatted Vapor template, some CLI commands may be unavailable.

Ideally there'd be a way to prevent just any repo from being cloned.
I'm also partial to username/name-of-proj defaulting to github.

Regarding the template parameter: As a techie I always wonder how stuff works under the hood. If the template parameter is a URL I immediately know where it's from and where I can go look for more details. I suspect that's true for a lot of the users as well.
So I'd go with just a URL rather than a mapping that you need to maintain.

First: Should this be "moved" to the Vapor CLI issues? I do not know how except for closing it here and opening a new one there.
@feinstruktur If implemented as @LoganWright described it, it would still be transparent because user/repository would only be a shorthand form of https://github.com/user/repository.git without any mapping.

Create a new issue in the Vapor CLI repo, then reference this issue from there (using the qutheory/repo#number syntax)

I came here because I was looking for the same thing: a barebones version of the project to start from.  The example project is nice but it would be useful to have something more basic to use as a starting point.
On a related note:  what's the recommended way to rename a Vapor project?  @LoganWright mentioned that the application itself needs to be called App, but what about the Xcode project?  I attempted to change one using Xcode's rename tool, but it broke some dependencies.

I'm going to close this branch, it's gotten a bit stale and we've improved some of the git functionality quite a bit since this originally went up. If we have further discussions, let's reopen a thread @qutheory/vapor-cli
Thanks to everyone for participating!

You can now do vapor new <name> --template=... and clone any repository. It will update the Package.swift name with whatever <name> is. Now it's up to us to create new templates.


OCPBUGS-34865: Fix name resolution for HTTPS konnectivity proxy

What this PR does / why we need it:
The new HTTPS konnectivity proxy requires that DNS names be resolved before generating a proper CONNECT string for the Konnectivity server. However the dialer was returning a nil IP if it didn't think it needed to resolve a name through the hosted cluster. This fix is to always resolve a name if using the HTTPS konnectivity proxy.
Which issue(s) this PR fixes (optional, use fixes #<issue_number>(, fixes #<issue_number>, ...) format, where issue_number might be a GitHub issue, or a Jira story:
Fixes #OCPBUGS-34865
Checklist

[x] Subject and description added to both, commit and PR.
[x] Relevant issues have been referenced.

/test e2e-conformance

/cheerry-pick release-4.16

/cherry-pick release-4.16


https://tii.la bypass

Link
https://tii.la
Version
Manifest-v3
What browser(s) are you using?
Chrome browsers (includes brave, edge, opera, etc)
What platform are you using?
Computer (Windows, Linux, MacOS)
(Optional) Anything else?
Pls add this site

please provide an example link

Here https://tii.la/LhsXGpMS
On Wed, Oct 11, 2023, 19:07 supernova @.***> wrote:

please provide an example link
—
Reply to this email directly, view it on GitHub
https://github.com/FastForwardTeam/FastForward/issues/1170#issuecomment-1758030763,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A5X52XVKC4PIIHXF4WW3Y3LX62745ANCNFSM6AAAAAA54GY7NM
.
You are receiving this because you authored the thread.Message ID:
@.***>


TypeError in address at index.android.bundle:1

Error in UniceNotes
TypeError in address at index.android.bundle:1
Cannot read property 'toString' of undefined
View on Bugsnag
Stacktrace
address at index.android.bundle:1 - ?anon_0_

View full stacktrace
Created automatically via Bugsnag

voir #15
Comment added in Bugsnag by Hugo
TypeError in address at index.android.bundle:1

An error linked to this issue has been reopened in Bugsnag
TypeError in address at index.android.bundle:1

fixed as by maintenance problem
Comment added in Bugsnag by Hugo
TypeError in address at index.android.bundle:1

An error linked to this issue has been marked as fixed in Bugsnag
TypeError in address at index.android.bundle:1

An error linked to this issue has been reopened in Bugsnag
TypeError in address at index.android.bundle:1


Vite Plugin Peer Dependency Prevents Vite 3.0

Describe the bug
Now that Vite 3 is out, there don't appear to be any changes preventing Vanilla Extract from supporting "vite": "^2.2.3 || ^3.0.0-0" as a peer dependency.
Without updating the peer dependency in this repo, and attempting to install the Vite 3 gives:
npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/vite
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@vanilla-extract/vite-plugin
npm ERR!   dev<EMAIL_ADDRESS>from the root project

Reproduction
Reproduction
System Info
System:
    OS: macOS 12.2.1
    CPU: (10) arm64 Apple M1 Pro
    Memory: 2.33 GB / 32.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 16.13.1 - ~/.asdf/installs/nodejs/16.13.1/bin/node
    Yarn: 1.22.17 - /opt/homebrew/bin/yarn
    npm: 8.5.5 - ~/.asdf/plugins/nodejs/shims/npm

Used Package Manager
npm
Logs
npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/vite
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@vanilla-extract/vite-plugin
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution

Validations

[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] The provided reproduction is a minimal reproducible example of the bug.

This is my workaround to prevent the peer dependency error:
  // package.json
  "overrides": {
    "@vanilla-extract/vite-plugin": {
      "vite": "^3"
    }
  },

Any updates on this? I've hoped that this would be added to the new release of the vite plugin. Forcing the install and using actual version does work as far as i can see; so there is no reason to keep the old peer dependency?

It appears that there are no breaking changes in Vite 3, I've created a PR to add it to the peer dependencies.


"work in progress - do not merge yet"

Issue #2530 initial development supplied for feedback.

Hi.  You're editing the moment.js file directly.  Please read the Contributing file, which explains which files you should be editing.  Thanks.

Also, I suggest you start with the unit tests, in true TDD style.  That way we can agree on the API, input and output before you invest too much on implementation.

Also, I'm not sure I would go so far to call it the "IETF format".  IETF manages the RFC/BCP process, and the prevailing date format is RFC3339, which is similar to ISO8601.  Let's just stick with the name RFC2822.  Thanks.

@TracyGJG you need to modify files under src/. moment.js is autogenerated. Any progress addressing the comments from mj1856 ?

I have had troubles with node paths so am in the process of reinstalling. I understand the point made. It was only changed to raise questions not as a candidate solution.

@tracygjg i recommend nenv - it makes dealing with node so much easier.

Now obsolete


fix(dataset): prefer implicit return types

get_dataset() returns a CocoDataset, not a Dataset.

My bad, I wonder how is mypy missing these typing faults

My bad, I wonder how is mypy missing these typing faults

Or maybe kwcocos actually fit the traits types

I'm confused too.


⚠ Samsung has degraded performance

In e5b7e3e, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2745 ms

Resolved: Samsung performance has improved in 587a44e.


Update diagnostic messages to ES2015 instead of ES6

Also the messages for generator and async have slightly different wording:

1220: Generators are only available when targeting ECMAScript 6 or higher.
1311: Async functions are only available when targeting ECMAScript 6 and higher.

I only noticed trying to search the phrase EcmaScript 6 or higher.

sigh... ES6 is much easier to read than ES 2015.
PRs are welcomed. changes should be mainly in https://github.com/Microsoft/TypeScript/blob/master/src/compiler/diagnosticMessages.json and places in the code the report the errors.

sigh... ES6 is much easier to read than ES 2015.

I agree but I noticed the configs were updated already. I'll PR momentarily.


Odometry Telemetry stream added

Odometry stream in Telemetry.
Unused fields and types are not included (see send odometry func).
Tested with MAVSDK-Python and real UAV.

Should I do smth more?
RPs https://github.com/mavlink/MAVSDK-Proto/pull/107 and https://github.com/mavlink/MAVSDK-Python/pull/109 merged and continued development is a little difficult for me because of only this PR is not merged yet.

Sorry, I should have merged. I'll merge tonight when the CI has passed! :blush:


Angular Scaffolding is broken

Description
Scaffolding with jss scaffold in Angular project is currently non-operational.
Refer to this SO question https://sitecore.stackexchange.com/questions/15464/error-when-trying-to-scaffold-an-angular-component
Steps To Reproduce

jss create foo angular
jss scaffold Foo

Feedback Wanted

The scaffolding system seems to be broken due to major breaking changes in the Angular Schematics module. JSS Angular scaffolding is based on the ng generate component schematic, which is unfortunately not particularly extensible and there's more code copying than I'd like.
There are a couple ways we could go about fixing this, and I'd like to hear from those who care with input on it:
Stop using schematics
This is not the first time Angular breaking changes have caused problems for JSS. Given the simple nature of JSS scaffolding (and aim to allow users to customize it), we could dump schematics and use pure JS like the React and Vue samples do. This would lose the extra parameters that come with the component scaffold. It would also improve our ability to support multiple Angular versions as we would not be tied to breaking changes in the schematics module.
Scaffold only the disconnected definition
We could make jss scaffold for Angular scaffold only the disconnected definition file. You'd use ng generate component directly for the rest of it.
Some combination of the above
We could look into making jss scaffold scaffold the disconnected file and then invoke ng generate, noting that there wouldn't be any JSS-specific tweaks to the generated components.

I think the third option of scaffolding the disconnected definition and invoking ng generate aligns better with what it looks like the React and Vue scaffold commands do. I personally don't mind doing a little more manual work to connect my component to the rest of my application as long as I'm not tied to a feature that has the possibility of breaking everything.

#106 fixes the scaffolding itself without any semantic changes


ARMv8 doesn't work

My ARMv8 device:
root@aml:~# arch
aarch64

With correct SDRPlay API installed (https://www.sdrplay.com/arm64dl.php)
Besides, modules were blacklisted correctly. It looks like everything is OK.
At this time, RSP1 can be detected by typing the lsusb command.
root@aml:~# lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 1df7:2500
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

What is puzzling me is that I got an error after executing the SoapySDRUtil --probe command.
root@aml:~# SoapySDRUtil --probe
######################################################
##     Soapy SDR -- the SDR abstraction library     ##
######################################################

Probe device
Error probing device: no sdrplay device found

What's more, I can't use the command lsusb to detect my RSP1 again.
root@aml:~# lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

I have been confused by this problem for a long time, I wonder if my RSP1 is broken.

Problem was solved, due to the inferior cable…


fix(core): capture command data for SDK v3 clients

Issue #, if available: #460
Description of changes:
Changes based on @SergeyPoluektov's PR: #527 since it looks abandoned.
I simply validated their changes, and added the requested unit test to this PR. The test validates that command inputs and outputs get mapped correctly into the generated segments.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report
Patch and project coverage have no change.

Comparison is base (e32dd95) 83.38% compared to head (52f1e4d) 83.38%.

:exclamation: Current head 52f1e4d differs from pull request most recent head 3414373. Consider uploading reports for the commit 3414373 to get more accurate results

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #611   +/-   ##
=======================================
  Coverage   83.38%   83.38%
=======================================
  Files          37       37
  Lines        1794     1794
=======================================
  Hits         1496     1496
  Misses        298      298

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


Add envs to python path

Hi Thomas! I was testing this code, and for me it said
ModuleNotFoundError: No module named 'envs'

Please advise if this looks like a good fix?

Also, since the default directory is checkpoints/cubes, we want to not throw an error if checkpoints folder doesn't exist :)

Fantastic, thanks!


Kevin autocomplete

Autocomplete for DictionarySource and KeywordSource

Good start!  A few minor comments: (1) Include the issue number in the subject; (2) Don't use a committer's name in the subject.  It will be easier to schedule a F2F review with @henrychen0220 and @zuozhiw.

I wonder whether it's better to split this PR to two PRs, one for adding the Metadata functionality (with test cases), and another one for enabling auto-complete.  Also do we have test cases for the frontend?  If not, we should.

Yeah we can do that. Let talk about details during the meeting tomorrow.


feat: provide discriminator in throttle_data

Closes #420

LTGM, we need it too 👍

That was fast! Thank you!


cFE Integration candidate: 2021-02-23

Describe the contribution
Fix #139, Do file writes in background
Fix #978, put task parameters into task record
Fix #790, allow directories and symlinks in FILELIST.
Fix #735, add comment if null terminated or not.
Fix #1160, Shorten task info default filename
Fix #1172, Update to use Ut_Stub_CheckDefaultReturnValue API
Testing performed
See https://github.com/nasa/cFS/pull/193/checks
Expected behavior changes
PR #1148 - Implements a generic FS facility to perform file writes as a background job. Applications wanting to use this need to instantiate a state object (metadata) in global memory and two callback APIs, one to get a data record, another to send events. The following file requests are changed to use this facility:

ES ER Log dump
SB Pipe Info
SB Message Map
SB Route Info
TBL Registry Dump

Changes the internal SB member names for consistency and thus fixes propagation of Depth and CurrentDepth into files:

MaxQueueDepth for maximum depth at queue creation time (previously was QueueDepth or Depth depending on context)
CurrentQueueDepth for the running count (previously was InUse or CurrentDepth depending on context)
PeakQueueDepth for the highest "watermark" (previously was PeakInUse or PeakDepth depending on context)

PR #1151 - No public API change. Encapsulates all parameters for apps and tasks into a structure object. Cleans up internal APIs to pass this new object rather than individual parameters. Adds details to the relevant record (i.e. a task record has all relevant task details) which eliminates the need to traverse the app record to find some data.
PR #1158 - Enables items in FILELIST to be in a target name directory as well as symlinks. arch_build.cmake now checks a name-based subdirectory under ${MISSION_DEFS} for files listed in the FILELIST for that target. If file is a symlink, the link should be followed so the correct content is installed, not a symlink.
PR #1168 - Mo impacts to behavior. Adds documentation on  inclusion presence of null terminators for length parameters.
PR #1175 - Shortened CFE_PLATFORM_ES_DEFAULT_TASK_LOG_FILE name so it is within the OSAL_MAX_FILE_NAME size limit. Will now output task info to default filename if no filename is provided in command.
PR #1173  - Replaces UT_Stub_SetForceFail with UT_Stub_SetDefaultReturnValue. No behavior change.
System(s) tested on
Ubuntu 18.04
Additional context
Part of https://github.com/nasa/cFS/pull/193
Third party code
None
Contributor Info - All information REQUIRED for consideration of pull request
@jphickey
@zanzaben

CodeQL fails due to dependency on osal, cFS bundle level PR checks are succesful


chore(deps): remove object-assign

Ref. #585

@azu, sorry for not contributing to the project recently! I'm slowly back to work as a contributor. Please review the pull request at your spare time. Thank you.


Installation Error

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to Terminal
After clone repo and give permission to setup.py
Run ./setup.py install
See error
THE SOFTWARE IS PROVIDED AS: File name too long
./setup.py: 25: from: not found
./setup.py: 27: Syntax error: word unexpected (expecting ")")

Screenshots
Desktop (please complete the following information):

OS: Kali 2023

@iamdevakumar Try executing pip3 install . instead of running setup.py directly.


pythonPackages.surt: init at 0.3.1

Motivation for this change
This adds surt from https://github.com/internetarchive/surt.
Things done

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

[x] NixOS
[x] 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 nixpkgs-review --run "nixpkgs-review wip"
[ ] 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)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@ofborg build python3Packages.surt

Result of nixpkgs-review pr 119441 at de9b721b run on aarch64-linux 1

2 packages built successfully:

python38Packages.surt
python39Packages.surt


[Bug]: archive node /cosmos/staking/v1beta1/pool fails on old blocks

What happened?
We are querying an archive node at block 12m: /cosmos/staking/v1beta1/pool and it returns:
{"code":13,"message":"invalid denom: ","details":[]}

Newer blocks work as expected (13m for example):
{"pool":{"not_bonded_tokens":"14127857404284","bonded_tokens":"335061758936683"}}

Osmosis Version
latest
How to reproduce?
Query the node at 12m block height, example:
curl -X GET -H "Content-Type: application/json" -H "x-cosmos-block-height: 12000000" https://archive-node/cosmos/staking/v1beta1/pool

hey @gilxgil, does the same error occur in any of the blocks prior to block height 12m?

Yes, same results all the way to genesis.
I did a binary search and this is where the problem starts (maybe it coincides with an upgrade).
Working block 12834100:
{"pool":{"not_bonded_tokens":"13862733148321","bonded_tokens":"335222421855613"}}

Not working block and lower 12834099:
{"code":13,"message":"invalid denom: ","details":[]}

It does coincide with the v21 upgrade, which is the upgrade that we unforked the sdk

I looked into this, its because the query calls GetParams, which prior to v21 was store in the legacyparams store, but now we store and retrieve from the individual ParamsKey of the specific module.
We could probably add a logic gate that pulls from legacyparams IFF the response is nil/zero

This issue exists for every query that revolves around the legacy param store

For anyone planning to work on it:
We call BondDenom here https://github.com/osmosis-labs/cosmos-sdk/blob/734f99fba785cc04bfd369baf6123a5a6e182b9a/x/staking/keeper/grpc_query.go#L453
Which pulls from the module params here https://github.com/osmosis-labs/cosmos-sdk/blob/9345069d96188b8e38e8e21a8296546662b70909/x/staking/keeper/params.go#L34C1-L37C2
Prior to v21, we would pull from paramstore https://github.com/osmosis-labs/cosmos-sdk/blob/734f99fba785cc04bfd369baf6123a5a6e182b9a/x/staking/keeper/params.go#L36C1-L40C2
So because the per module param store didn't exist prior to v21, it returns blank for the denom. A solution could be in the querier, if the params returns is blank, we fall back to pulling params from the legacyparamstore

This isn't forked code correct? If so, imo we should put it in the SDK? (Any change we make here, I'd also want to get into the SDK)
The real solution for this is to have queries like this to an archive node get sent to different binaries based on block hegiht requested, rather than a single archive for all versions

Going to close, with the solution needed is that we need tooling to make an archive node / architecture that makes a separate DB per app version. I am told Cosmosia has tooling for this. https://github.com/cosmos/cosmos-sdk/issues/12686

Closing as this was reopened by mistake


Fix Izhikevich synaptic weights

Need to also look at the units we use in the code, the difference between that and that Matlab reference code, and which makes sense for us to use.

For now, let's put this in the code as comments. Later, we'll document this better when pulled out into parameter files.


merge update

Hi @zzl81cn, was this a mistakenly opened PR?  If not please describe what you are going go.


Potential missed ListingCreated events

Seen a few occurrences of this in prod recently.  I don't know if this is causing issues or is intentional.  Just looks weird to me.
[INFO]  dshop.utils.handleLog: Event ListingCreated for listing Id 1-001-2465
[DEBUG] dshop.utils.handleLog: Event is not for a registered dshop. Skipping.

The listing JSON does appear to be a Dshop listing:
{
  "__typename": "UnitListing",
  "schemaId": "https://schema.originprotocol.com/listing_3.0.0.json",
  "listingType": "unit",
  "category": "schema.forSale",
  "subCategory": "schema.clothingAccessories",
  "language": "en-US",
  "description": "Origin DShop Store",
  "media": [],
  "price": {
    "amount": "0",
    "currency": "fiat-USD"
  },
  "amount": "0",
  "currency": "fiat-USD",
  "acceptedTokens": ["token-ETH"],
  "commission": {
    "currency": "OGN",
    "amount": "0"
  },
  "commissionPerUnit": {
    "currency": "OGN",
    "amount": "0"
  },
  "requiresShipping": false,
  "unitsTotal": 1000
}

Could be from a custom deployment, which would make this sane and okay.  There's no DB entries matching this listing(may or may not be expected).  The numbers aren't really expected, however.

I wonder if this is a race condition:

A listing is created for a new shop on the front-end via MetaMask
Transaction get mined
The back-end listener may pick up the event faster than the front-end
In that case the front-end won't have updated listing_id in the shops table, which would explain why the listener does not find it...

The good news is that the logic does not process ListingCreated event (only Offer events are). See code.
One minor impact though is that we won't record that event in the DB which down the road could be useful. See code.

Now, I checked the DB and I don't see any row in the shops table associated with listing id 1-001-2465.
It's possible the user did not wait for the transaction to be mined before killer their browser tab running the dshop deployer, resulting in the front-end not registering the listing id with the back-end?

I'm actually seeing a lot of holes in the sequence of listing ids registered with the back-end in the shops table.
select id, created_at, listing_id from shops order by listing_id desc;
...
 328 | 2020-07-31 04:19:28.859+00 | 1-001-2488
 304 | 2020-07-31 02:33:14.842+00 | 1-001-2486
 297 | 2020-07-31 01:55:52.233+00 | 1-001-2480
 276 | 2020-07-31 00:47:10.941+00 | 1-001-2479
 292 | 2020-07-31 01:31:21.013+00 | 1-001-2478
 271 | 2020-07-31 00:35:05.692+00 | 1-001-2474
 280 | 2020-07-31 00:57:06.253+00 | 1-001-2473
 240 | 2020-07-30 23:30:04.903+00 | 1-001-2471
 194 | 2020-07-25 17:52:10.445+00 | 1-001-2469
 263 | 2020-07-31 00:06:46.916+00 | 1-001-2468
 242 | 2020-07-30 23:36:34.329+00 | 1-001-2466
 218 | 2020-07-30 23:14:25.186+00 | 1-001-2463
 211 | 2020-07-30 22:17:27.288+00 | 1-001-2460

This could indicate a bug in the front-end where it does not register the listing id with the back-end ?

Something odd.
These server logs indicates that there was a shop with listing_id 1-001-2476. Otherwise the Upsert event would not have happened (see this code).
I 2020-07-31T01:33:56.276293250Z [INFO]  dshop.utils.handleLog: Event ListingCreated for listing Id 1-001-2476
I 2020-07-31T01:33:56.280307432Z [DEBUG] dshop.utils.events: Upsert event...

And querying the DB confirms an event for listing id 2476 was inserted in the events table.
BUT when querying the shops table, I do not see any shop associated with that listing!
dshop=> select id, created_at, name from shops where listing_id='1-001-2476';
 id | created_at | name
----+------------+------
(0 rows)

This could indicate that after that event got inserted, the shop got updated and the listing_id deleted from the shop DB row?

Confirmed that listing id 2476, 2477, 2478 were created by the same address  starting with 0xde7245...
So that would explain the holes in the listing ids in the shops table for that range of listing Ids.
I wonder what causes that user to create 3 listings?
I'll check for other listing Id ranges.

The current mechanism of waiting for the tx to be mined, then updating the backend via the UI isn't great. Instead, we could do the following:

Add a listingCreatedTx column to the shops db table
Send the txHash and owner wallet to the backend from the UI as soon as we get it (ie don't wait for it to be mined)
Listener watches for ListingCreated events, and updates any shops in the db with matching tx + owner with the eventually mined listingId

Caveat: if the user 'speeds up' the transaction, a new txHash will be generated but the old txHash could still be mined first. For that reason we should probably have the ability to either a) monitor multiple txHashes for the same shop on the backend, or b) find the shop that has the same sellerWallet as in the ListingCreated event, but with no listingId yet, and update that.
The former is more complex but probably better, as users could conceivably try to create multiple shops in quick succession

I looked at another range of listing ids and it has a similar pattern.
Listing Ids range [1-991-2497, 1-991-2499].
All those 3 listings were created by the same shop (id 374).
It seems a pretty common pattern so worth putting in a fix.
I'll look at the backend piece and then we can integrate the front-end.

Lowering to P2 since now that we moved things off-chain, the listener is not involved for setting up a shop and orders processing.

Closing this code is not active in prod and therefore we don't have any new data to investigate on.


How to change animation when movement success

I'm trying to move an element between containers. If unsuccessful, the overlay will return to its original position, displaying an animation that disappears towards the target container when successful.
But in my case the animation always back to original position.
If the overlay disappeared to target container when the movement is success will be more intuitive.
Is it possible to handle the animation? any advice or sample will be very appreciate .
my code as following.
  const dropAnimation = {
    duration: 250,
    easing: 'cubic-bezier(0.1, 0.7, 1.0, 0.1)',
    sideEffects: defaultDropAnimationSideEffects({
      styles: {
        active: {
          opacity: '0',
        },
      },
    }),
  };

  <DndContext
    sensors={sensors}
    collisionDetection={customCollisionDetectionAlgorithm}
    onDragEnd={handleDragEnd}
  >
    <div className={`${gridClass} original-scroll pr-1`}>
    ...

    {createPortal(
      <DragOverlay adjustScale={false} dropAnimation={dropAnimation}>

      </DragOverlay>,
      document.body
    )}
  </DndContext>

https://user-images.githubusercontent.com/44263972/170852547-d3f6667c-ac9f-45ed-86d9-2df232fef275.mp4

indeed, this seems relevant with React v18

i have the same issue , finnally i found it cause by i have not set unique_key in each ITEM.
you could set a key with a unique_key in each Item, but it cannot be the index of the list, like id in database or something

Do you show the code how it works?
It's not working in my case.
My code as follows
  const {
    attributes,
    isDragging,
    listeners,
    setNodeRef,
    transform,
    transition,
  } = sortable;

  const style = {
    transform: CSS.Transform.toString(transform),
    transition,
  };

  return (
    <div
      ref={setNodeRef}
      style={style}
      key={`setNodeRef:${item.xinfo_uuid}`}
      {...attributes}
      {...listeners}
    >
      <DrawCard
        key={`drawcard:${item.xinfo_uuid}`}
        xshar_uuid={xinfo_parent}
        parent={parent}
        item={item}
        onClickActive={onClickActive}
        onComplete={onComplete}
        innerHeight={innerHeight}
        className={isDragging ? 'border-dashed-info-50' : ''}
      />

  );

the unique id suggestion was on the spot, i made it work. thanks a lot!


fix: Don't prompt for LUIS key if not needed

Description
botIndexer::shouldUseLuis function is used to check if LUIS is needed. Inside, it checks against the dialog.luProvider property. If it is not present or is Microsoft.LuisRecognizer, LUIS is assumed to be used.
But the luProvider property is not added to the dialog unless using the dialogsWithLuProviderSelectorFamily selector. This PR switches all needed selectors that make this LUIS check to use dialogsWithLuProviderSelectorFamily so this property is filled.  This allows Orchestrator to be selected, and if Luis is not used, no keys will be prompted for.
If  LUIS is used anywhere else, the key gets prompted again as expected.
Task Item
closes #6074

Coverage remained the same at 53.756% when pulling 4da8128707e19e41f70612bedd90db11097116e2 on tachou/orchLuisKeyFix into 0728122fa19c823eea54040b59eb2cca0487455f on main.

@lei9444  can you help confirm this fix?


pacmod3: 1.1.0-0 in 'lunar/distribution.yaml' [bloom]

Increasing version of package(s) in repository pacmod3 to 1.1.0-0:

upstream repository: https://github.com/astuff/pacmod3.git
release repository: https://github.com/astuff/pacmod3-release.git
distro file: lunar/distribution.yaml
bloom version: 0.6.6
previous version for package: null

pacmod3
* A boost::shared_ptr error would occur on some vehicles on shutdown.
  Moving the allocation of all of the optional subscribers to after
  ros::init is called fixes this error and should not impact functionality
  or performance.
* Temporarily disabling Vehicle 5 steering wheel controls.
* First attempt at adding an All System Statuses topic.
* Changing CAN factors for Steer Aux rpt values.
* Removed incorrect conversion factor for as_tx/vehicle_speed
* Adding publishing for door, interior lights, rear lights, and occupancy rpt.
* Removing wipers from VEHICLE_5.
  This system will not be availble in the initial vehicle release.
* Changes for vehicle 4
* Adding unknown vehicle mfg and year to VIN rpt.
* Adds the ability to parse Dash Controls, CC Btns, and Media Btns.
* Add config_fault_active to global report.
  This indicates that a fault occurred while reading the configuration file.
* Creating framework for publishing of all current Aux msgs.
  Created parsing and publishing framework for Aux messages on the
  following systems: Accel, Brake, Headlights, Shift, Steer, Turn, and
  Wipers.
* Adding VehSpecificRpt1. Removing SteerRpt2 and SteerRpt3.
  VehicleControlsRpt was replaced with VehicleSpecificRpt1. SteerRpt2
  and SteerRpt3 were deemed unnecessary given the addition of SteerAuxRpt.
* Command values for SystemCmdBools were reversed.
  This commit fixes the reversal (commanded true now encodes a 1
  in the CAN message instead of a 0 and vice versa).
* Added report messages DetectedObjectRpt, VehicleControlsRpt, and VehicleDynamicsRpt
* This commit removes state mgmt and the global enable.
  If any system is disabled, it should either be due to a disable
  being sent from the user, an override, or a fault. This means that
  there is no need for us to maintain all systems' states in the driver.
  We can just continue to spam the most recent command and only modify
  it if we receive an override_active or fault_active flag on the global
  command. If either of those are true, we immediately disable all
  systems.
* CAN ID reorganization.
  After talking with the team, reorganizing the CAN IDs prior to
  the use of a PACMod3 in production made sense. This includes
  consideration for priority, grouping based on function, and leaving
  space for future additions.
* Adds clear_override flag to all PACMod 3 command messages.
  This requires approval of the maint/add_clear_override_flag branch
  on astuff_sensor_messages - hence the change to .travis.rosinstall.
  Will have to change this back to master once that branch is approved
  and this is merged into master here.
* Adding Aux rpts for brake/accel/shift/steer. Door/Occ/IntLights/ExtLights rpts.
  Adding framework for parsing Aux reports from brake, accel, shift, and steer systems.
  Adding parsing framework for DoorRpt, OccupancyRpt, InteriorLightsRpt,
  and ExteriorLightsRpt.
* Adding state_change_debounce_counts for each system.
  This will help to prevent quick enable/disable flashes
  on the PACMods and PACMinis by stopping listening to their reports
  for X number of loops after a state change (enable->disable/disable
  ->enable.
* Turn signal was defaulting to 0 (TURN_LEFT). Fixed.
* Fixing Horn cmd type.
* Only listen to system reported state if PACMod is disabling the system.
* Removing recent_state_change stuff. It isn't helping anyway.
* Only saving output value to command if disabled and no recent state change.
* Start debounce count with high number to avoid missing the first state change.
* Finished implementing state change debouncing for all systems.
* Implementing state change debouncing.
* Filling commands with no matching parser with 0s instead of 255s (much safter).
* Added proper class initialization.
* Fixing type difference in can_id value. Fixing bug in SystemRptBool parsing.
* Horn is Bool, not Int.
* Adding additional fault reporting to global rpt and system reports.
* Changing name of CruiseControlSystem to be more accurate (CruiseControlButtonsSystem).
* Adding support for additional vehicle systems.
* Fixing enable/disable problem.
* Setting command = output while disabled for each system.
* Adding clear_override flag.
* First commit with most things changed to pacmod3 (untested).
* Contributors: Daniel-Stanek, Joe Driscoll, Joe Kale, Josh Whitley, Joshua F WHitley, Joshua Whitley, Kyle Rector, Lucas Buckland, Nishanth Samala, Sam Rustan, Samuel Rustan, driscoll85

Done.


Handling of the CTRL+C signal is not consistent across platforms

I'm seeing this behave strangely in different contexts, and so I might just remove it until I figure out what is going on. OSX seems to be the strangest.

What strange behaviour did you observe? I have no problems with CTRL+C under OSX. I read that sometimes there are problems with catching signals when running via go run, but I have no problems doing it this way, too.
The docs also say os.Interrupt is available on all systems.

Should be good now.


Include ghz support at initial readme.md

A very little contribuition at doc.

hello @ldeitos, thanks for the contribution, we are working on fix linting, once done we will merge this

Codecov Report

Merging #165 (eff9ecf) into master (339a574) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #165   +/-   ##
=======================================
  Coverage   59.80%   59.80%
=======================================
  Files          35       35
  Lines        2458     2458
=======================================
  Hits         1470     1470
  Misses        883      883
  Partials      105      105

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 339a574...eff9ecf. Read the comment docs.

hey @ldeitos, could you please rebase your changes with master branch?

hello @ldeitos, thanks for the contribution, we are working on fix linting, once done we will merge this

done!


Failed Installation

I'm having an issue installing bxtools on the cluster at the Broad institute. I've pasted some of the output below. The issue begins when I try to make

Looks like an old compiler version. Try "reuse GCC-5.2" first, then compiling.

On Apr 3, 2017, at 4:55 PM, sherifgerges<EMAIL_ADDRESS>wrote:
I'm having an issue installing bxtools on the cluster at the Broad institute. I've pasted some of the output below. The issue begins when I try to make
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Any luck with updating GCC / recompiling?

Hey Jeremiah!
I think I got it to compile, although I've been occupied with non-10x
Genomics work at the moment. Will certainly reach out if I have more
problems!
Thanks so much,
Best,
Sherif
On Wed, Apr 19, 2017 at 3:15 PM, Jeremiah Wala<EMAIL_ADDRESS>wrote:

Any luck with updating GCC / recompiling?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/walaj/bxtools/issues/5#issuecomment-295398091, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AXyyAIZx30gYgdoZw0un9hJmfKEi4LA4ks5rxl07gaJpZM4MyFJZ
.

--
Sherif Gerges
Graduate Student
Harvard Medical School


Handling responses

I've been looking through the example code to auth & capture a sale on a credit card found here:
PaymentTransactions/charge-credit-card.
The error handling feels fairly clunky and full of potential gotchas. Conditionals get nested up to 4-levels deep, there are weak equality checks against NULL which behaves in tricky ways (almost like empty(), but not... see the php docs ), and the error/message arrays are accessed only at index 0 for codes & descriptions (no looped printing of messages? if always a single element in an array, why an array?).
I understand that an auth & capture can have many conditions to a failure, and that this code is meant to show off as much of the inner workings of the SDK as possible, but is there not a way to expose a success variable that isn't deeply nested and conditional? Why can the result code come back 'ok', but the transaction still fail?
As I dig deeper into these questions by reviewing your reference docs, I feel like there is a lot that is left out of this example. Just trying to wrap my head around the features and the mechanics of this SDK so I can robustly handle transactions.

This is the more robust response handling I'm attempting:
<?php

$response = $controller->executeWithApiResponse( $this->authNetAPIEndpoint );
$result = TransactionResult::newFromResponse( $response );
echo $result->toJson( JSON_PRETTY_PRINT );

Which outputs:
{
    "responseCode": "Ok",
    "messages": [
        {
            "code": "I00001",
            "text": "Successful."
        }
    ],
    "transactionResponse": {
        "success": true,
        "responseCode": "1",
        "transId": "60020226802",
        "authCode": "68WTTL",
        "accountNumber": "XXXX1111",
        "accountType": "Visa",
        "cvv": {
            "cvvResultCode": "M",
            "description": "Match."
        },
        "avs": {
            "avsResultCode": "Y",
            "description": "Address (Street) and five digit ZIP match."
        },
        "cavv": {
            "cavvResultCode": "2",
            "description": "CAVV passed validation."
        },
        "errors": [],
        "messages": [
            {
                "code": "1",
                "description": "This transaction has been approved."
            }
        ]
    }
}

Hi @alexsasharegan,
There are essentially two main responses to a card transaction. There's the API response (the first "responseCode" and "messages" elements in your example), and the transaction response (the "transactionResponse" element). transactionResponse in turn might contain other types of responses for specific situations like the AVS response and the CVV response.
It's a lot easier to troubleshoot something when you know which part of it failed, and this kind of granular response enables that. An API request is either going to succeed or fail, where success means "I got a properly formatted request, and I was able to perform actions on the data that it contained". Failure means "I could not perform any action on that request, either because I don't recognize the formatting as valid, or I've got a problem on my end, or whatever" with the details in the "messages" object.
There are a lot of usages of our API that aren't charging a card, so we need a standardized way to indicate success at the API level independent of whatever success would be at the card processing level.
The transactionResponse contains the actual disposition of the transaction itself, i.e. was the card authorized or not.
So, you really need to be testing first if your request was successfully processed by the API (is the resultCode = "Ok") and dealing with any failures there separately. Then, if the API request was successful and your input was sent off for action, test what the result of that action was (look for responseCode=1 within transactionResponse).
I agree it can be a little confusing, and if I could go back in time I would try to name things a little better (i.e. not "resultCode" and "responseCode"), but that's how it is for now.
We're always looking for ways to make the SDKs better, so if that means we have to abstract more in future versions so that responses no longer map to how the actual API is sending them, we'd do that if the net benefit was positive.

@adavidw ,
Thanks for the explanation!
I would say that understanding the API has a bit of overhead before productivity starts. I completely see now what you are explaining, and I was starting to understand that on my own. I don't hate that granularity at all—it's quite useful—but I almost wish your response here was included as part of the documentation. With an SDK this big, there can be a lot to digest at first, and you explanation would have helped me grock the method to the structure and choose an approach must faster.
That said, I still think the example code could be a bit clearer and use some more strict methods to handle the conditions. I think even commenting the code to basically include the gist of your explanation would be quite beneficial.
More abstraction could be worthwhile in the way of a response parsing class. Something JsonSerializable, ArrayAccessible, etc. to be flexible. Some convenient methods for things like: requestWasSuccessful(), transactionWasAccepted(), getTransactionFailureCode(), getTransactionFailureDescription(), toJson(), toArray(). This could really reduce the time to a successful integration as well as provide a canonical way to handle responses. You can build an Interface that all API responses adhere to for some of these methods, and then implement additional methods that pertain to the specific API actions requested.
Just some thoughts. I appreciate the well explained response!

Thanks for the followup. I agree with everything you say, and I'm on a crusade to improve things, one little pain point at a time. Better documentation for the SDKs is a must, including better getting started instructions, as well as thorough commenting of the samples and the SDKs themselves.
At some point, though, we do have to allocate resources between improving existing efforts and starting new ones. Something like making the existing SDKs more abstract and JSON-ified can bring real rewards to developers. But, applying the same resources to creating, say, a new fully REST-ful API that's already better organized can bring a different set of rewards.
So, I can't promise which specific way we'll solve any particular problem or remove any particular pain point. However, I can promise we'll be always improving and making things better overall.
I'm going to leave this open as a reminder to me to clean up my previous explanation and try to get that into an appropriate place in the SDK to help others

@adavidw ,
I've been playing with my own ways to JSONify the response objects returned. Since each request returns a response object with different kinds of nested objects (and all with private props I can't json_encode), I would have to build individual response parsing objects for each request type. Obviously not ideal.
I played with some recursive reflection, and so far, the results are a perfect match to the "pretend" JSON shape of responses as shown in the reference docs. I do have to build the root-level response prop "messages" manually (still not sure why reflection doesn't catch that one), but that's not too big of a price to pay.
Normally, I would consider this kind of code a hack (I'm messing with hidden props), but since all these classes are built on the fly with yaml, I really don't see the harm in exposing the hidden props to an array. They all are built with getters and setters anyways.
I'll include the recursive reflection function if you want to take a look at it and weigh in on how good or bad of an idea this is.
<?php

function extractAllObjectPropsToArray( $object )
{
  $properties = [];
  $reflection = new ReflectionClass( $object );

  foreach ( $reflection->getProperties() as $property )
  {
    $property->setAccessible( TRUE );

    $propName  = $property->getName();
    $propValue = property_exists( $object, $propName )
      ? $property->getValue( $object )
      : NULL;

    switch ( TRUE )
    {
      case is_array( $propValue ):
        $properties[ $propName ] = [];

        foreach ( $propValue as $value )
        {
          $properties[ $propName ][] = is_object( $value )
            ? extractAllObjectPropsToArray( $value )
            : $properties[ $propName ][] = $value;
        }
        break;
      case is_object( $propValue ):
        $properties[ $propName ] = extractAllObjectPropsToArray( $propValue );
        break;
      default:
        $properties[ $propName ] = $propValue;
        break;
    }
  }

  return $properties;
}

I can't access root-level props like "messages" because they are private members of a parent class. I made some modifications to that function that invoke the parent class getters and then introspect the return value to get their values.
Rather than dump more code in here, let me include a link to the gist.

I've made some updates to that gist. Essentially now, it just recursively calls every getter on the object while setting the value to the method name without the get, and lower-cased on the first letter. It traverses up the inheritance tree as well.

I don't have to much to offer specifically on your code, but you hit upon a good point about the generated code. There's a definite difference between an SDK that was designed and one that was generated. Ours looks too much like that latter. A well-designed SDK is created by people who think through how it's going to work and how people are going to use it. The SDK will reflect that with more abstracted functionality in the areas where it makes more sense, but still leave everything broken apart in the areas where that's appropriate.
I think our SDKs have often fallen short there, but the good news is that we're all on the same page here about the idea of what makes a good SDK, so any work on the next major revs of the SDKs should hopefully reflect that.
I fear people might get tired of me promising that the REST API will solve all the problems with the current API and the next version of the SDK will solve all the problems with the current ones. But, that's our intention here at least, to take all of the lessons learned from any problems we've caused in the past and rectify them for the future.

@adavidw ,
Wait, is this REST API production ready, or is this a coming-soon thing? I was under the impression that using this SDK (v1.9) was the current standard for processing through Authorize.Net. My goal here is to bring our company up to date with your most current tools (coming from v1.1) so we can start taking advantage of your newer payment methods and feature sets. Just want to make sure I didn't miss something!

No, the REST API isn't production ready yet, but we expect a beta-level release fairly soon, and we'll definitely be in touch with you about that.
The latest SDK does support the latest released technologies on our side, but we'll rev the SDK to support the REST API. At that time, we'll take the opportunity to solve all of its other problems as well.

Thanks for the update! This is great news! I really appreciate your patience and understanding in all this. Please do reach out as release comes around!

When i'm trying to connect apple pay with my sandbox account,im getting an error "there was an error processing payment data invalid ownership".

Hi @praveenkumarS7
Can you please provide more  information about the error, including:

Is the Apple pay account used by you a developer/sandbox account?
Are you trying to connect your Apple pay with your sandbox account in merchant interface? Or, are you trying to make a transaction using the blob generated by your Apple Pay account?
If you are using the API, what is the error code for the above error message? For this, you can share the response from your phplog file for this purpose. It is generated in the same folder as your sdk path. In this file, you would see the response in a line containing : Response from AnetApi: <?xml version="1.0" encoding="utf-8"?  The response will have your credentials masked, so it is okay to share.
What are the steps you are using to generate the blob for Apple pay?


Using Globalize in Angular CLI project

I use latest version Angular and Angular CLI it's 6+.
Devextreme and Devextreme-angular has versions 18.1.3.

I can use "devextreme-intl" and "loadMessages" function and localized components, but not all of I need.
When i install cldr-data + globalize and try to use different functions like:
Globalize.load(     deCaGregorian, deNumbers, deCurrencies,     ruCaGregorian, ruNumbers, ruCurrencies );
I get a lot of errors in console related with working globalize with "cldr" and "cldr/event".
Can you create example project with Angular CLI + Globalize and Globalize.load() ?
The main what i need it's use Globalize.load().

I have the same problem with my Angular 5 and CLI 1.7 version and dev-extreme 18.1.3 version. Globalize not working with CLI (

I recommend that you refer to the following thread where a similar inquiry was discussed: Can't get Globalize to work inside an Angular CLI project

Excellent! Working! Thank you!


[enhanced-enums] A value declaration is a constant context

Consider the following program:
enum E {
    v([]); // No error.
  const E(_);
}

The program uses --enable-experiment=enhanced-enums. It does not have any errors, in particular, [] can be used as an actual argument because the spec has:

where args are considered as occurring in a const context, ...

However, the CFE reports an error at [] (two, actually):
n017.dart:2:7: Error: Constant expression expected.
Try inserting 'const'.
    v([]);
      ^
n017.dart:2:7: Error: Non-constant list literal is not a constant expression.
    v([]);
      ^

The analyzer rejects the program as follows:
ERROR|COMPILE_TIME_ERROR|CONST_CONSTRUCTOR_WITH_NON_CONST_SUPER|/usr/local/google/home/eernst/lang/dart/scratch/202201/n017.dart|3|9|1|A constant constructor can't call a non-constant super constructor of 'Enum'.

which means that the analyzer may or may not have the same fault, but we don't get to see it because we encounter an error with the Enum constructor (which could be a fault in the analyzer, or in the declaration of Enum, or both).
So we have at least one platform where there is a need to make this change: An enum value declaration is a constant context.

Subtasks:

[ ] CFE.
[ ] Analyzer?

@scheglov, do you agree that the CONST_CONSTRUCTOR_WITH_NON_CONST_SUPER issue that seems to affect the analysis of every enhanced enum declaration could mask errors on the enum members? Is it expected to be resolved soon?

Yes, I agree. https://dart-review.googlesource.com/c/sdk/+/230321 should fix this.

Thanks! I added https://github.com/dart-lang/sdk/issues/48237 just in case there is a need to change the analyzer as well.


App doesn't seem to die properly on windows

Always have to go into task mangler to kill the process...

current workaround is using Git Bash, problem persists with the windows command promopt

there is no problem on linux either, any word from a mac user?
@ian-h-chamberlain @UuqV

Works on mac

Determined to not be our problem


Error with Kmodel Version

I can't upload the demo_find_face.py script. I just got the error: ValueError: [MAIXPY]kpu: load error:2002, ERR_KMODEL_VERSION: only support kmodel V3/V4 now, but I flashed the  maixpy_v0.6.2_16_gaefa3193d_openmv_kmodel_v4_with_ide_support.bin file to the MaixBit.
Is something wrong with my device? Could anybody help me?

I have the same issue, using the script above with firmware 0.6.2.  is the v4 model loaded on another address?

It looks like the firmware doesn't have the right model embedded. The demo worked if you load http://dl.sipeed.com/MAIX/MaixPy/model/face_model_at_0x300000.kfpkg with the KFlash tool. @Bashdog

Ok thank you!

Where to load this ?? Ive already loaded :-
FaceDetection (0X300000),
FaceExtraction(0X500000),
FaceLandmarkDetection(0X400000)
and then I loaded :-
maixpy_v0.6.2_57_gae955b706_openmv_kmodel_v4_with_ide_support.bin  at (0X0000)

It looks like the firmware doesn't have the right model embedded. The demo worked if you load http://dl.sipeed.com/MAIX/MaixPy/model/face_model_at_0x300000.kfpkg with the KFlash tool. @Bashdog

It looks like the firmware doesn't have the right model embedded. The demo worked if you load http://dl.sipeed.com/MAIX/MaixPy/model/face_model_at_0x300000.kfpkg with the KFlash tool. @Bashdog

After loading all the files, I flashed your .kpfg still face_recognition giving error about KMODEL

i m facing same issue what should i do now ??


Merge pull request #1 from Xenrid/master

Fix for error preventing playback when selecting episodes directly on Android devices.

i have a question when i opene simpletv dont show anythinh and show mw a message tell me you pasword simpetv incorrect


Unable to use Mapper with EndpointWithoutRequest

Unable to use Mapper with EndpointWithoutRequest.
Basically i am trying to use mapper object for GetAll Endpoint but it dont suport it
Any help?

you can do Endpoint<EmptyRequest, EmptyResponse, Mapper>


How does Repository#save work?

It is stated in the docs that You also use .save to update an existing entity, but how does it know if there is an existing entity?

It doesn't. Redis (and by extension) Redis OM always does upserts.

So to update, for example, a user whose email (but not id) is known I have to search for that user first and save it afterward, and there is no way to do it in a single query, right?

Correct.

Thanks


How to train the images on our own Dataset.

Can you please specify how can we train the model with our own dataset?

Hi @krishmadubey
The model given is a generalized model so it should work on any type of input but in any case if you wanna fine-tune the weights you'll probably have to write a finetuning script.
I do not have that in the repo because I haven't written it, but I can tell you how to go about it if you need that.
Although in my opinion, there have been a lot of new advancements in object removal since I wrote this code.
One of the better ones was published in CVPR 2019 called Pluralistic-Inpainting. They provide a training script as well as pre-trained weights. You can have a look at that as well.

Thanks @VPanjeta .

Thanks @VPanjeta .


PopOver Does not close from another component.

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯
PopOver does not close, only esC button will close it.

Expected Behavior 🤔
Close PopOver when click outside of it

Steps to Reproduce 🕹

Steps:

Click Emoji icon
2.Try to close it

https://codesandbox.io/embed/zealous-maxwell-3115b?fontsize=14&hidenavigation=1&theme=dark
Context 🔦

Your Environment 🌎

Tech
Version

Material-UI
v4.9.9

React
latest

Browser
firefox

TypeScript

etc.

Thank you.
this is the link to stackoverflow.
https://stackoverflow.com/questions/61031116/material-popover-does-not-close-upon-onclose-call


Is there any way to use embed_schema?

https://hexdocs.pm/ecto/Ecto.Schema.html#embeds_many/3-examples
It's more of a doubt than an issue I faced.
But my new schema has an attributes jsonb which is a string in ch, which is originally an embed for me.
For a simple JSONB as is I used a strategy like this:
defmodule App.ClickHouse.Jsonb do
  use Ecto.Type

  def type, do: Ecto.ParameterizedType.init(Ch, type: "String")

  def cast(value) do
    {:ok, value}
  end

  def dump(value) do
    Jason.encode(value)
  end

  def load(value) do
    Jason.decode(value)
  end
end

And I declared it like this:
field :attributes, Jsonb

Not sure if I could do it in any other way.

However... even if the approach above worked for a common insert.
For a stream insert as RepoClickhouse.insert_stream(PositionReplicated, positions, settings: [async_insert: 1])
I got:
** Reason for termination ==
** (DBConnection.ConnectionError) client #PID<0.2610.0> stopped: ** (CaseClauseError) no case clause matching: %{}
    (ch 0.1.14) lib/ch/row_binary.ex:180: Ch.RowBinary.encode/2
    (ch 0.1.14) lib/ch/row_binary.ex:76: Ch.RowBinary._encode_rows/4
    (ch 0.1.14) lib/ch/row_binary.ex:76: Ch.RowBinary._encode_rows/4

The code in question from deps/ch/lib/ch/row_binary.ex:
  def encode(type, str) when type in [:string, :binary] do
    case str do
      _ when is_binary(str) -> [encode(:varint, byte_size(str)) | str]
      _ when is_list(str) -> [encode(:varint, IO.iodata_length(str)) | str]
      nil -> 0
    end
  end

@ruslandoga I saw you closed this, but there is any example about using embed schemas?

I haven't used embedded schemas with this adapter yet. What have you tried?

Sorry for closing it, I thought your question was about your JSON type.

Sorry for closing it, I thought your question was about your JSON type.

No problems, you're doing a great job so far.
I will try something and give you samples soon.

@daviaws 👋
Can this issue be closed?

Well, we dropped the usage of clickhouse... so I won't be needing any support anymore for now.
We were receiving a lot of inconsistent data on queries and we did not achieved so great performance as the benchmarks first tells...
Postgresql is doing better for us... I would like to know where we did wrong... but this answer never came and we rolled back the plan.
If you do not see any value on embed_schemas feel free to close this request and any other of mine.
Good luck and thank you for all the support.


Recheck cwh regarding commy2's remark

WeaponHolder and child classes inherit from Static, so don't have XEH. WeaponHolderSimulated and child classes inherit from ThingX and so don't have XEH either.
Could be changed in CBA I suppose.
    class WeaponHolder: ReammoBox {
        XEH_ENABLED;
    };

    class WeaponHolderSimulated: ThingX {
        XEH_ENABLED;
    };

There.

https://github.com/CBATeam/CBA_A3/pull/1228


Add IQueryTypeConfiguration

Please check if the PR fulfills these requirements

[x] The code builds and tests pass (verified by our automated build checks)
[ ] Commit messages follow this format

    Summary of the changes
    - Detail 1
    - Detail 2

    Fixes #11257

[x] Tests for the changes have been added (for bug fixes / features)
[x] Code meets the expectations our engineering guidelines. https://github.com/aspnet/Home/wiki/Engineering-guidelines.

This is my first PR for EF, so please be patient with me 😃

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

Should I rebase it?

@ilmax Yes, thanks!

@anpete Done, let me know if something is missing!

Any idea about build failures? To me it seems unrelated to the change

@ilmax - I have triggered appveyor/travis builds again. Rest of the CIs are passing so its good sign.
Travis is hitting intermittent issue with SQLite - database is locked error.
AppVeyor failed because we had local build break.

Also can you rebase on release/2.1 branch?

Yes, will do tomorrow CET time

Merged thanks!


Receive: Implement a sloppy quorum

An idea that I had for some time, I was wondering about opinion of others.
Is your proposal related to a problem?
Even though receiver is scalable, when replication is on, by increasing / decreasing number of nodes in a hashring, the fact is that due to how receiver handles requests (batch smaller request for each node + replicate the batched requests) a user can afford to lose only small number of nodes before we cannot guarantee quorum anymore and have to respond with failure to client (for example for replication factor 3 it's only one node). This means that even if we increase number of nodes in the hashring, it will not increase the resiliency of the system. The larger the number of nodes in the hashring, the higher the probability more than one node will be out at the same time.
Under normal circumstances and for many use cases, this might be fine - as is widely known, Prometheus clients will keep retrying if 5xx is returned up to 2 hours, which should be enough to resolve issues, so there's only small danger of data loss. However, for users which want to guarantee higher write availability and "near-live" data querying, the time window < 2 hours can be unacceptable. Good example would be users that have alerts defined depending on metrics written to receiver - in such situation, users are clearly interested in having those metrics available ASAP. Even though receiver does not do any rollback in case of partial writes (i.e. even if quorum is not reached, it might be that some requests are written despite receiver returning 5xx error) and therefore these metrics might be available, it cannot be guaranteed and for the duration of any outage, it is unknown whether the request will be written to at least one node.
Describe the solution you'd like
For cases when higher availability of receive writes is desired, we could consider accepting sloppy quorum. This could have a form of nodes accepting and temporarily storing writes on behalf of others and then retrying to send data to the appropriate node with backoff. A very rough idea would be to use something akin to agent, which would periodically retry to deliver data to the appropriate node.
To ensure instant read availability, we might consider to accept sloppy quorum only if at least one replication successfully ended up on the correct node and can be queried. Other option, although probably more complex and less performant, would be to make it possible to query data that is being temporarily stored on behalf of other node.
Describe alternatives you've considered

Take advantage of the in-built forward retry mechanism in receiver - this works fine for intermittent network errors, but cannot help during a longer node outages
Increase the replication number - with higher replication factor, user can afford to lose more nodes. However, this would result in unnecessary data redundancy and overhead of storing the extra replicated data, even though user does not have a need for it.

Additional context
Performance implications should certainly be considered here, as receivers have large footprint already (see e.g. https://github.com/thanos-io/thanos/issues/5751). Nevertheless, the trade-off might be favorable for the use cases described above.
cc @PhilipGough

Hello, Starting to implement stateless ruler which now query receive for ALERTS_FOR_STATE in receive.
We would be super interested in this, as of today if 1 receive ingester is down and for whatever reason does not recover fast, we have problems whatever the replication factor we set.

Thanks @ahurtaud, unfortunately I think I'd be able to take this on in the foreseeable future 😢 , but I'd be happy to let someone else take over / help review etc.


Webapp 450 make text required for negative feedback

This pull request belongs to an issue on our bugtracker.
You can find it there by looking for an issue with the key which is mentioned in the title of this pull request.
It starts with the keyword WEBAPP.

we should probably add some kind of indication why you cannot submit an empty feedback. Maybe append "*" to the question "Was können wir besser machen?". Opinions?

Yes, we should definitely find a way to indicate it, a star is probably a good solution.
Another possible option would probably be to automatically focus the text field and show a red indicator if the focus is changed. Or leave the button clickable and show a red indicator if it is clicked and no text is entered.
You should probably take a look at how different pages are handling similar stuff and choose the option that suites you the most.

So now I added just a red star to the question, as changing the border of the comment field feels like we'd have to juggle the comment state around too much. If you still like that solution better we should probably consider using form fields or sth.

I guess this is fine, I like it :+1: Did you check how it looks with RTL languages?
I don't know if it makes sense to add the star after Wofür ist das Feedback? since the category is also required, although an option is already selected by default.
We should probably also think about whether we need a hint in the text are.

Make sure to name your PRs: WEBAPP-450: ----
It makes it easier to copy the reference to Jira :)

I think it actually could make sense to record downvotes. For example if one page gets many downvotes then it is maybe an empty page and nobody bothered to write a comment.

@maxammann actually I'm quite sure we discussed this at a conference (or even multiple times) and agreed on making the text required for negative feedback. We had the same arguments, but in the end agreed on this. And now I am also convinced this is right. Negative feedback without a comment could mean anything and does not provide any benefit in the most cases.

I don't know if it makes sense to add the star after Wofür ist das Feedback? since the category is also required, although an option is already selected by default.

I don't think this is necessary, as you would automatically open the dropdown to see what other options you have. Otherwise we would have to deal with checking for no selection.

We should probably also think about whether we need a hint in the text area.
I looked at a few other solutions to submit feedback like Jira, OneDrive/Word (where you can submit empty feedback o.o), gitkraken, sourceTree (where every few versions the application crashes after submitting feedback), youtube (where you can't even write text), ...
And I liked Jiras solution the best.

:+1:

@maxammann you currently just don't want to approve, do you? :stuck_out_tongue:

Apart from @lulo4907 comment and the failing test :+1:


configuration is not working with mesa 7i97 card

Version and Build Date
Version = 1.2.1
Build Date =10/1/2023
Describe the bug
The config produced by the tool is not usable
To Reproduce
Steps to reproduce the behavior:
Create a default config with 7i97 card
Expected behavior
working conf
Config File
[Attach the ini file that has the bug in it.
the files are attached
01-10-23-09:25:09.zip
Operating System
OS =  Debian 10
Additional context
If you haven't a mesa 7i97 card we can organize a meeting and you can connect to my machine using anydesk.
Best regard
I attached also a screen shoot

Thanks for your work !

Axis loads ok? What is not working?
I do not have a 7i97 in stock to test with here.

At the very bottom of your ini file I see some duplicate section/key/values
[JOINT_0]HOME_SEQUENCE =  0
[JOINT_1]HOME_SEQUENCE =  1
[JOINT_2]HOME_SEQUENCE =  1
Did you add those?

Not at all.
As you can see on the screen capture, It's only axes X and Z. Both axes are
disabled.
Many thanks for your help. I can provide as many files and that you need.
Anydesk connetion is also possible.
Best regards
Thierry Vorms
Le jeu. 12 janv. 2023, 08 h 46, jethornton @.***> a
écrit :

At the very bottom of your ini file I see some duplicate section/key/values
[JOINT_0]HOME_SEQUENCE = 0
[JOINT_1]HOME_SEQUENCE = 1
[JOINT_2]HOME_SEQUENCE = 1
Did you add those?
—
Reply to this email directly, view it on GitHub
https://github.com/jethornton/mesact/issues/80#issuecomment-1380379411,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA6QD4OJ2VR4H24BIVKM6V3WSADKJANCNFSM6AAAAAATW33ZWU
.
You are receiving this because you authored the thread.Message ID:
@.***>

That is the expected behavior when the E-Stop is on and power is off.

Hello,
Yes axis loads and work.
Yes you are right,, there was mistake added by me:
[JOINT_0]HOME_SEQUENCE = 0
[JOINT_1]HOME_SEQUENCE = 1
[JOINT_2]HOME_SEQUENCE = 1
I remove it and sorry for disturbing you with that.
But when I start linuxcnc with the conf, there is in the display only axe X
and Z but not the Y why ?
I can help you as you want.
Best regards
Thierry
Le jeu. 12 janv. 2023 à 08:03, jethornton @.***> a
écrit :

Axis loads ok? What is not working?
I do not have a 7i97 in stock to test with here.
—
Reply to this email directly, view it on GitHub
https://github.com/jethornton/mesact/issues/80#issuecomment-1380311156,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA6QD4NPIHSJTCYCOZGIC3DWR76LJANCNFSM6AAAAAATW33ZWU
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
Thierry Vorms
Québec Canada


Ameerul / Fix missing translations

Wrapped strings that were not wrapped with localize.

Some examples of what needed to be fixed

Pull Request Test Coverage Report for Build<PHONE_NUMBER>4
Details

34 of 34 (100.0%)  changed or added relevant lines in 15 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.03%) to 85.611%

Totals

Change from base Build<PHONE_NUMBER>3:
0.03%

Covered Lines:
5686

Relevant Lines:
6181

💛  - Coveralls


Enhancement : allow to set the HTTP client's timeout period

Certain operations (namely, drop measurements) can take longer than the current time out (= 100s), and thus, an OperationCanceledException is raised. It would be nice to be able to set up the time out period.
Currently, the HTTP client is constructed with the default options, including its Timeout property.

I will add this as a property directly on InfluxClient.

I have uploaded a new version with this included.


Add python 3.8 and 3.9 support

[sc-132132]

Failing integration tests are actually only warnings, merging this


Unable to run safari in parallel

Hi,
I have done selenoid setup in Mac machines as per  https://medium.com/@aandryashin/selenium-an-apple-story-ab0c0b68cd35 and selenoid is pointing to 4444
When I try to run tests in parallel, it invokes only one session executes first test and throws below error for remaining tests.
"selenium.common.exceptions.SessionNotCreatedException: Message: Could not create a session: The Safari instance is already paired with another WebDriver session."
Mac Configuration: Processor Name: Dual-Core Intel Core i5
Processor Speed: 2.6 GHz
Number of Processors: 1

When I run 3 test in parallel selenoid assigns 3 nodes for each tests but runs first test and throws above mentioned error for remaining 2 tests. refer screenshot.
Thanks.

@RameshEmis this is Safari limitation, because webkit port is hard-coded in this browsers.

@RameshEmis this is Safari limitation, because webkit port is hard-coded in this browser.

@vania-pooh so we cannot achieve parallel execution with safari browser. is there any workaround for this.?

@RameshEmis this was working in previous versions of safaridriver but not in the latest one.


[#1.1] Add habit

As a doer, I want to add a habit, giving it a brief title, reason, date to start, and whether it is public or private.

Tasks:

[ ] Entry fields:

[ ] Enter a name
[ ] Enter a date range
[ ] Enter days of the week
[ ] Enter habit reason

[ ] Create a Habit object with the entered information


Stuck on "Joining world..." screen when launching any game, solo or server

Latest version of the modpack provided, dowloaded off of CurseForge app.
So I don't know if anyone's still working on this, seeing when were the last updates but i'll try this anyways.
We wanted to try this modpack with some friends on a server. The server itself seems to have no issues for now,
but we can't figure out a way to actually play the game, as said in the title, the game both on single and multi - player doesn't let you past the "Joining world..." screen with a weird fade effect.

(As this was on the server, I tried killing my character via the console)
The game is running in the background as you can see the particles and hear all the game sounds, but nothing else
I didn't know what file would be interesting to provide so ask anything, we're actually quite exited about this modpack, would be a shame if nothing was possible to fix this.

Hey thanks for wanting to play my modpack it really does make me happy!
I will get back to you about this issue and try to resolve it when I'm back from work 😃
I'm also currently not working on this modpack anymore I'm trying to make a nicer 1.19.2 version still not ready to be played or uploaded yet tho. But I kinda have hard time managing time because of work and uni

Also if I remember correctly I'm at the time of creating this modpack there was an issue with one of the mods that caused what you are experiencing. And I think it got resolved with an update but I'm not sure.
So if u don't want to wait then maybe you can try copying the modpack and removing mods to see which one caused the error. (Remove half of the mods and start, if error resides then remove half of the mods again and so on). Then maybe try updating the mod or checking it's channeling to see if it got resolved

Hey, thank you for answering that quick :)
I tried removing one - I'd have to double check the name, but it was one that supposedly needed an update - didn't change anything. Just wanted to confirm that we tired on every single one of our pcs and same exact bug for each of us.
I wanted to ask you about those JVM arguments that you included in the CurseForge description of the modpack. Could those be helpful to resolve this issue or purely performance related ? And also would there be any way to see wich one of the mods could cause any issue ? Not that I'm not a fan of checking every single one of the 400ish mods one by one but y'know... :)
Sorry if that doesn't make sense, I'm really not the best when it comes to makin computers work the way they should ^^

I think it was Danny's Expansion? but not I'm entirely sure.
I wouldn't recommend playing this pack but if you really want to, I can try to see what's the cause in the weekend.


Click handlers not firing on mesh

Issue already resolved, only filing it so others are aware of it if they encounter the same problem.
I added a click handler to a mesh that never fired:
commands
  .spawn((
      MaterialMesh2dBundle {
          mesh: mesh_handle.clone().into(),
          ..default()
      },
      On::<Pointer<Click>>::run(click_handler),
  ));

Turns out the mesh created from code and before picking I only needed it to exist while rendering:
    Mesh::new(
        PrimitiveTopology::TriangleList,
        RenderAssetUsages::RENDER_WORLD,
    )

Picking does need it in the MAIN_WORLD though, so it should be
    Mesh::new(
        PrimitiveTopology::TriangleList,
        RenderAssetUsages::all(),
    )

To add more context, picking doesn't need this, the mod_raycast backend for picking does. If you are using a picking shader as the backend, you would not need the mesh to stay loaded on the CPU.

Thankyou @mahulst for posting here. I have been losing my mind as to why my click event wasn't firing! 🙏  👏
I was using RaycastPickable as part of my bundle, I am just coming back to this project from a few months prior and bumped versions etc.
I appreciate the answer too Aevyrie, although I'm not 100% clear. I am not sure what I lose by removing the RaycastPickable.
Also I was confused how I was supposed to add the RenderAssetUsages::all() to my mesh bundle.
e.g:
// Where does this fit in?
    let mesh = Mesh::new(PrimitiveTopology::TriangleList, RenderAssetUsages::all());

  // This was the previous bundle:
    let bundle = MaterialMesh2dBundle {
        mesh: meshes.add(Circle::new(radius)).into(),
        material: materials.add(ColorMaterial {
            color: colour.into(),
            texture: None,
        }),
        transform: *transform,
        ..default()
    }

Not that I need to now I've removed the RaycastPickable!

although I'm not 100% clear. I am not sure what I lose by removing the RaycastPickable.

This is documented:
https://docs.rs/bevy_picking_raycast/0.20.0/bevy_picking_raycast/struct.RaycastPickable.html
You likely inherited this from an old version of the plugin, and did not remove it when it became optional.


Test the various different K8S providers

Install and test bearer token with:

Minikbue
Docker Desktop
GCP
IKS

Approach :

Create an environment
Run make start
Run  make test
Run  make test-e2e


build(node): replace broken & unmaintained gradle node plugin

Checklist

[x] The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
[ ] Links to related issues (if applicable)
[ ] Tests for the changes have been added/updated (if applicable)
[ ] Docs related to the changes have been added/updated (if applicable)

FYI @cptran777 & @igbopie


Swan's Jupyter fix

Base image is now versioned.
Fixes issue of failing Jupyter because changes in base image.
Testing done:

UT

run integration tests