Update the model with status of data

Currently model shows only the data from where it has been collected. It should also show from how long( time period) it has been collected and what data. Basically, information about the data (both deploy and AWS).

The model was updated with the current status of data describing about the logs and from where they are taken.


feature: add support for the new TypeScript / Webpack  ... resolve: {   alias: {

please add support for the new TypeScript relative path shortcuts / alias in ng cli

{
    "compilerOptions": {
        "module": "commonjs",
        "moduleResolution": "node",
        "baseUrl": "src",
        "paths": [
            "actions/*": [ "app/actions/*" ],
            "selectors/*": [ "app/selectors/*" ],
            "ui/*": [ "app/ui/*" ],
            "logger": [ "util/logger" ],
        ]
    }
}

You learn more about it here:
https://decembersoft.com/posts/say-goodbye-to-relative-paths-in-typescript-imports/
which will be awesome so we can use in angular alias paths and not have to ../../../../SomeComponent
Thanks as always for a great product,
Sean

This is already covered with tsconfig.json

ha missed it, tx!!!

born2net, does it work for you?
I've added this to my tsconfig.json:
"compilerOptions": {
  "baseUrl": "src",
  "paths": {
      "shared/*": ["app/shared/*"]
  }
}

Path to the constants file: src/app/shared/constants/index.ts
When I import it as usual import { testConst } from './shared/constants/index';, it works fine:
But when I use absolute path, it crashes:
import { testConst } from 'shared/constants/index';
Webpack error:
ERROR in C:/Projects/myProject/UI/src/app/app.component.ts (2,27): Cannot find module 'shared/constants/index'.)
ERROR in ./src/app/app.component.ts
Module not found: Error: Can't resolve 'shared/constants/index' in 'C:\Projects\myProject\UI\src\app'

hansl, could you please confirm that this feature works as it should? Maybe we need to add additional configuration somewhere?

@andrii-oleksyshyn this is a scenario that we test for and support.
See https://github.com/angular/angular-cli/blob/master/tests/e2e/tests/build/ts-paths.ts for an example.
Make your you're changing the right tsconfig, in this case src/tsconfig.app.json.

I tried adding the paths option to my tsconfig.app.json file, but when I then run 'ng build', it will hang and eventually crash with a heap error:

13% building modules 25/58 modules 33 active ...ode_modules\webpack\buildin\global.js
<--- Last few GCs --->
[13780:0000020FEDA4C940]   370034 ms: Mark-sweep 1525.0 (1638.4) -> 1525.0 (1638.4) MB, 1614.4 / 0.0 ms  last resort
<--- JS stacktrace --->
==== JS stack trace =========================================
Security context: 0000020C133A66A1
1: /* anonymous */ [C:\Dev\my-project\node_modules\enhanced-resolve\lib\UnsafeCachePlugin.js:~28] [pc=000002AC25ADC024](this=000003231ADBDC39 <a Resolv
er with map 000002EB11A41131>,request=000000506A8C04E9 <an Object with map 0000007A023C8351>,callback=000001BD49293171 <JS Function (SharedFunctionInfo 0000031
D6CDBBDE9)>)
2: applyPluginsParallelBailResult1 [C:\Dev\my-project\no...
FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory

This is easy to duplicate.
1- Create a new cli project
2- npm install gridstack --save
3- ng build <-- this will build correctly without issue
4- Add let gridstackjQuery = require('gridstack/dist/gridstack.jQueryUI.js'); to the app.component.ts file.
5- ng build <-- this will output errors that it can't resolve 'jquery-ui/<some component'.  That's because all the components are located one folder lower in 'jquery-ui/ui'.
6- Add paths option to the tsconfig.app.json file:
"paths":{
"jquery-ui/":["jquery-ui/ui/"]
},
7- ng build  <-- This will result in the above crash.
Am I aliasing my paths wrong?  Is there a supported way to change the paths that gridstack is expecting?
I have asked the gridstack folks to change their requires, but until they do, I'm hoping there is a way to work around this in Angular.

Make your you're changing the right tsconfig, in this case src/tsconfig.app.json.

I am changing the right tsconfig but still having issues. A simplified example of my set up is below.
Structure:
project
└─── packages
│   └─── foobar
│       │   index.ts
│       │   ...
│
└─── src
│   │   tsconfig.app.json
│   │   ...
│   └─── app
│       │   app.component.ts
│       │   ...

tsconfig.app.json:
{
  "compilerOptions": {
    ...
    "baseUrl": "./",
  },
  "paths": {
    "@packages/*": ["../packages/*"]
  }
}

Could this be because my packages are outside of the src folder?

Same for me, using cli v1.3.0. Using baseUrl and paths in my tsconfig.app.json doesn't work. I'm not sure why this issue is closed?
My setup is:
.
|--demo-app
|  |--src
|  |  |--tsconfig.app.json
|--packages
|  |--core
|  |  |--index.ts

And the tsconfig.app.json has, among other things:
"compilerOptions": {
    "baseUrl": "./",
    "paths": {
      "@cdux/ng-core": [
        "../../packages/core"
      ]
    },

But when I build, I get errors that @cdux/ng-core cannot be found. And the module resolution debug output shows that it never even attempts to look in ../../packages/core for those modules:
Module not found: Error: Can't resolve '@cdux/ng-core' in '/Users/brad.ball/dev/cdi/cdux-ng/dev-app/src/app'
...
[/Users/brad.ball/dev/cdi/cdux-ng/dev-app/src/app/node_modules]
[/Users/brad.ball/dev/cdi/cdux-ng/dev-app/src/node_modules]
[/Users/brad.ball/dev/cdi/node_modules]
[/Users/node_modules]
[/node_modules]
[/Users/brad.ball/node_modules/package.json]
[/Users/brad.ball/dev/cdi/cdux-ng/dev-app/node_modules/@cdux/ng-core]
[/Users/brad.ball/dev/cdi/cdux-ng/node_modules/@cdux/ng-core]
[/Users/brad.ball/dev/node_modules/@cdux/ng-core]
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>[/Users/brad.ball/node_modules/@cdux/ng-core]
[/Users/brad.ball/dev/cdi/cdux-ng/dev-app/node_modules/@cdux/ng-core]
[/Users/brad.ball/dev/cdi/cdux-ng/node_modules/@cdux/ng-core]
[/Users/brad.ball/dev/node_modules/@cdux/ng-core]
<EMAIL_ADDRESS><EMAIL_ADDRESS>[/Users/brad.ball/node_modules/@cdux/ng-core]
[/Users/brad.ball/dev/cdi/cdux-ng/dev-app/node_modules/@cdux/ng-core]
<EMAIL_ADDRESS><EMAIL_ADDRESS>[/Users/brad.ball/dev/cdi/cdux-ng/dev-app/node_modules/@cdux/ng-core]
[/Users/brad.ball/dev/cdi/cdux-ng/dev-app/src/@cdux/ng-core]
<EMAIL_ADDRESS><EMAIL_ADDRESS>[/Users/brad.ball/dev/cdi/cdux-ng/dev-app/src/@cdux/ng-core]
[/Users/brad.ball/dev/cdi/cdux-ng/dev-app/src/@cdux/ng-core]
<EMAIL_ADDRESS><EMAIL_ADDRESS>[/Users/brad.ball/dev/cdi/cdux-ng/dev-app/src/@cdux/ng-core]

In other, non-cli projects I've worked on, I've found that I need to set the paths property in my tsconfig.json AND set the `resolve: { alias: {} } property in my webpack config. It seems like the cli currently doesn't provide any way for us to specify the resolve.alias property to go in the webpack config.

You must set baseUrl and paths in the same time to make it work correctly.And the routes in paths values are based on the baseUrl.

Is this working yet? I experienced the same problems as everyone on this thread-


Variant name is not displayed for recursive Rust enums.

OS: MacOS 12.5
VSCode version: 1.73.1
CodeLLDB version: v1.8.1
Compiler:  rustc 1.65.0
Debuggee:
Hi,
When trying to debug an enum the enum is not shown if one of the variants has a discriminant
Code snippet to reproduce:

enum ThisEnumWorks{
    FirstVariant,
    SecondVariant
}

enum ThisDoesnt{
    FirstVariant,
    SecondVariant,
    ThirdVarinat(String)
}

fn main() {
    let _variant_1_working = ThisEnumWorks::FirstVariant;
    let _variant_1_not_working = ThisDoesnt::FirstVariant;
    let _break_point = "stop";
}

and the corresponding debugger view in vscode

I'm running on aarch64-apple-darwin  and haven't been abele to confirm that this issue is present on any other rustc target

I can confirm this issue.
For enum values, which have a discrimant (a and b) , at least the value of the discriminant is shown in the debugger view:

But the other visible number in the debugger view is always 0, regardless of the actual value of the enum.
OS: Ubuntu 22.04
VSCode version:  1.74.2
CodeLLDB version: v1.8.1
Compiler: rustc 1.65.0
Running within a vscode developer container. target shown with rustc --version --verbose:  x86_64-unknown-linux-gnu

This is a limitation of Rust plugin's debug info parser.  The variant name is reported in type (which is shown in tooltip when you hover over the variable name).  The exception are C-like enums that consist only of the discriminant.

This is a limitation of Rust plugin's debug info parser. The variant name is reported in type (which is shown in tooltip when you hover over the variable name). The exception are C-like enums that consist only of the discriminant.

I hover over the variable name but I can't get the variant name. I'm using this example with CodeLLDB version 1.10.0.

This is a limitation of Rust plugin's debug info parser. The variant name is reported in type (which is shown in tooltip when you hover over the variable name). The exception are C-like enums that consist only of the discriminant.

I hover over the variable name but I can't get the variant name. I'm using this example with CodeLLDB version 1.10.0. The rustc version is 1.65.0 and is hosted on x86_64-unknown-linux-gnu.
...

I found the correct way to get the variant name.  Simply hover over the variable name within the "variables" side panel, rather than within the editor area.

I found the correct way to get the variant name.  Simply hover over the variable name within the "variables" side panel, rather than within the editor area.

This seems to be fixed for you as unlike the on the OP's screenshot, you can expand the enum variable

I found the correct way to get the variant name.  Simply hover over the variable name within the "variables" side panel, rather than within the editor area.
...
This seems to be fixed for you as unlike the on the OP's screenshot, you can expand the enum variable

You're right. Just leaving this solution here to help anyone who might encounter this issue (cannot get the variant when hovering over a enum value but not the OP's one), as the following content is a little misleading to newbies.

This is a limitation of Rust plugin's debug info parser. The variant name is reported in type (which is shown in tooltip when you hover over the variable name). The exception are C-like enums that consist only of the discriminant.

And even if I can expand the enum variable (on linux but not on macos), the expanded content does not provide meaningful distinctions between the variants.


LogFactory - AutoShutdown to allow users to control shutdown logic

Support Microsoft Extension IHostBuilder controlling when to shutdown. Because AppDomain-Unload is called premature (compared to IIS).
See also  #3284
Note merge to master

Didnt want to add test before the initial change was approved. Going to abuse medium trust test of appdomain.
But you approve the direction?
Sent from my Sony Xperia
---- Julian Verdurmen wrote ----
@304NotModified commented on this pull request.

In src/NLog/LogFactory.cshttps://github.com/NLog/NLog/pull/3578#discussion_r320027418:

@@ -185,6 +185,25 @@ public static IAppDomain CurrentAppDomain
///
public bool KeepVariablesOnReload { get; set; }

   /// <summary>

   /// Gets or sets a value indicating whether to automatically call <see cref="LogFactory.Shutdown"/>

   /// on AppDomain.Unload or AppDomain.ProcessExit

   /// </summary>

   public bool? AutoShutdown

   {

       get { return _autoShutdown; }

       set

       {

+#if !SILVERLIGHT && !IOS && !ANDROID && !NETSTANDARD1_3

           LoggerShutdown -= OnStopLogging;

Add test?

In src/NLog/LogFactory.cshttps://github.com/NLog/NLog/pull/3578#discussion_r320489113:

   /// <summary>

   /// Gets or sets a value indicating whether to automatically call <see cref="LogFactory.Shutdown"/>

   /// on AppDomain.Unload or AppDomain.ProcessExit

   /// </summary>

   public bool AutoShutdown

   {

       get { return _autoShutdown; }

       set

       {

           if (value != _autoShutdown)

           {

               _autoShutdown = value;

+#if !SILVERLIGHT && !IOS && !ANDROID && !NETSTANDARD1_3

               LoggerShutdown -= OnStopLogging;

               if (value)

                   LoggerShutdown += OnStopLogging;

@snakefoothttps://github.com/snakefoot should we assert this in the tests? I think this is the most important lines to assert:
                LoggerShutdown -= OnStopLogging;
                if (value)
                    LoggerShutdown += OnStopLogging;

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/NLog/NLog/pull/3578?email_source=notifications&email_token=ACXZ7HDULN2MYD3TZXDNOVLQH3KK3A5CNFSM4IS625K2YY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOCDMWBAY#pullrequestreview-282681475, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ACXZ7HFBWO2SKTTCYQDTDFLQH3KK3ANCNFSM4IS625KQ.

That's understandable :angel:

But you approve the direction?

Yes! Looks good, also nice it could be set in the nlog.config 👍 👍


use tscn format

As tscn format is the new default, and more conveniet for git, I converted the old scn files to new format.

When we made the demo, there was a bug in the tscn format that was failing
to load the lightmaps on the main screens, we should test if that's fixed
in the last stable release first..
On 18 November 2016 at 20:09, Ranito<EMAIL_ADDRESS>wrote:

@Ranito requested changes on this pull request.
A few dependencies need to be fixed, or else the template game won't start.
In device/ui/inventory.tscn
https://github.com/godotengine/escoria/pull/4#pullrequestreview-9324278:

@@ -0,0 +1,97 @@
+[gd_scene load_steps=3 format=1]

+[ext_resource path="res://globals/inventory.gd" type="Script" id=1]
+[ext_resource path="res://game/inventory_items.scn" type="PackedScene" id=2]
Fixed dependency:
[ext_resource path="res://game/inventory_items.tscn" type="PackedScene"
id=2]
In device/ui/hud.tscn
https://github.com/godotengine/escoria/pull/4#pullrequestreview-9324278:

@@ -0,0 +1,50 @@
+[gd_scene load_steps=4 format=1]

+[ext_resource path="res://globals/hud.gd" type="Script" id=1]
+[ext_resource path="res://ui/inventory.scn" type="PackedScene" id=2]
This dependency needs fixing.
[ext_resource path="res://ui/inventory.tscn" type="PackedScene" id=2]
In device/ui/hud.tscn
https://github.com/godotengine/escoria/pull/4#pullrequestreview-9324278:

@@ -0,0 +1,50 @@
+[gd_scene load_steps=4 format=1]

+[ext_resource path="res://globals/hud.gd" type="Script" id=1]
+[ext_resource path="res://ui/inventory.scn" type="PackedScene" id=2]
+[ext_resource path="res://ui/verb_menu.scn" type="PackedScene" id=3]
This dependency needs to be fixed.
[ext_resource path="res://ui/verb_menu.tscn" type="PackedScene" id=3]
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/godotengine/escoria/pull/4#pullrequestreview-9324278,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGVmPaK0ndFTKWY2iF1GrBWMztTqpP_8ks5q_jBBgaJpZM4KksTa
.

@punto- The lightmap bug is still present in current 2.1.3. I'll check if there's an issue related to this.

@c-cesar There are some missing errors in TSCN files you missed.
Please look at https://github.com/StraToN/escoria/tree/c-cesar-master to update your PR if you wish (else we'll use mine)
We won't pull this until the related bug is not fixed in Godot.

JFYI, I am starting from this PR to adapt current Escoria to Godot 3.


New Content Update Request: Update Partner Inquiry Page

On this page change first name last name to just full name

its better for crm to have it split


Integration configuration has two unlabeled slider bars and a checkbox

Thanks for working on this integration - I'm looking forward to trying it!   At first I thought it was my theme, but even changing to the default theme doesn't expose any labels.  What do they control?

Hi,
This is a caching issue. You must have had the previous version installed. I've seen this a few times during development. Try and clear your cache, before installing. It will show correctly after a bit of time.

I assume you mean browser cache?   This is the first time installing the integration and I've pulled it up on two different computers.  Tried F5, to no effect.

I should note that I haven't had time to go though the breaking changes, so I am still on 0.108.x.  If this might be due to any of the theming changes in the past two releases, then we can wait a few weeks, when I plan to upgrade to 0.111.

This is really strange. I just double checked the 0.10 files that are downloaded, and all the text and references are in the files that will be downloaded. The version of HA you are running should not make a difference. I cannot reproduce this error on any of my installations.

I've tried the following:

Reboot
Used Chrome inspector - don't see any selectable text items surrounding the bars
Removed browser_mod
Upgraded weatherbit
Reboot again

It said "please wait" while installing the upgraded integration when I went there immediately after that last reboot, but still no other text surrounding things.
I'm willing to help with further debug if I can be of help.

One more thought: Did you do a manual install? If yes, did you remember to copy the files in the translations directory? That is were the text definitions are pulled from.

I just managed to get the 'missing text' on an installation. (Running in Chrome Browser). I then  went to the Browser section 'More Tools' and then 'Clear Browsing Data' and marked 'Cached images and Files' and then pressed the button 'Clear data'. I then refreshed the browser on the Home Assistant page and went back to add the Weatherbit integration. I now had the text on the screen as expected.

As there has been no reply on this for more than a week, I assume it has been resolved, so I will close this now. Re-Open if you still have the issue.


sharding support

this is pretty much ready for review/discussion
with the current system you always have a sharding.ShardManager
I can think of having either of both on the Bot struct
need ur input on that @Skye-31 :)

The core.Bot struct is missing some methods which use context.Context

this is pretty much ready for review/discussion
with the current system you always have a sharding.ShardManager instead of gateway.Gateway
I can think of having either of both on the Bot struct
methods using the gateway would be checking which one is used ofc
need ur input on that @Skye-31 :)

I'd say allow both, and if a sharding manager isn't specified, provide a reasonable default

Could also be nice to have an option for the time delay between spawning each shard, and the maximum amount of time to wait when a shard is launching before throwing an error

Could also be nice to have an option for the time delay between spawning each shard, and the maximum amount of time to wait when a shard is launching before throwing an error

for starting a single shard it takes an context & I can add that time to the ratelimiter config 👍🏻

Could also be nice to have an option for the time delay between spawning each shard

done that :)

what do you think of the init flow via the opts? @Skye-31

lgtm


(Chore) Refactor auth0 domain workaround for native

Description
Torus strategies auth0Domain refactor as proposed in the issue, but removing 'https://' on native instead
About #2829
How Has This Been Tested?
Please describe the tests that you ran to verify your changes.
Checklist:

[x] PR title matches follow: (Feature|Bug|Chore) Task Name
[x] My code follows the style guidelines of this project
[x] I have followed all the instructions described in the initial task (check Definitions of Done)
[x] I have performed a self-review of my own code
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[x] I have added reference to a related issue in the repository
[x] I have added a detailed description of the changes proposed in the pull request. I am as descriptive as possible, assisting reviewers as much as possible.
[ ] I have added screenshots related to my pull request (for frontend tasks)
[ ] I have pasted a gif showing the feature.
[x] @mentions of the person or team responsible for reviewing proposed changes

@serdiukov-o-nordwhale @WolfVV please verify this hasnt broken web auth0 login


sqlsafe not compatible with sqlfluff

Really like this package. However I've stumbled upon an issue. I'm trying to create queries for dynamic tables and have to use the sqlsafe filter to do so. However, sqlfluff is then complaing that it cannot find the filter. Perhaps there's a way around this?
Failure to parse jinja template: no filter named 'sqlsafe'

Sample bigquery query that generates this issue for me
SELECT *
FROM `{{ project | sqlsafe }}.{{ dataset | sqlsafe }}.{{ table | sqlsafe }}`

This is outside the scope of JinjaSQL.
From what I understand, Sqlfluff was designed for Jinja2 templates. JinjaSQL is an extension on top of Jinja2, and adds the sqlsafe parameter which Jinja2 does not have. As a result, Sqlfluff complains about this filter.
Unfortunately, this is something that sqlfluff would have to implement.


Add german contributing guidelines

What does this PR do?
Add a German version of the contribution guidelines.
For resources
Description
Complementing the work on https://github.com/EbookFoundation/free-programming-books/pull/5684, I added a translation for the contribution guidelines in German and added links to all other contribution files' Read this in other languages lines.
Instead of appending the link to the end of the list, I re-ordered the first part of the list alphabetically. Let me know if there's a reason why it wasn't alphabetical before, and I will change it accordingly.
Why is this valuable (or not)?
It improves accessibility for the community beyond native english speakers.
Checklist:

[x] Read our contributing guidelines
[x] Search for duplicates.

Follow-up

[x] Check the status of GitHub Actions and resolve any reported warnings!

Sure, will do. Where should the German link go then at the end, or is there any other concept?

I swapped back French and Spanish. If you want me to put German at the end or anywhere else, please let me know. 👍

Sure, will do. Where should the German link go then - at the end, or is there any other concept?

At the moment as it is. To handle at #5762

Sure, will do. Where should the German link go then - at the end, or is there any other concept?

At the moment as it is. To handle at #5762

Nice 👍 You sure have an issue for just about everything 😲

I agree that there should be some order to the language lists, but now is a bad time to do it because of conflicts. Could you add an issue about that so it gets taken care of?
Thanks, and welcome to free-programming-books!

I agree that there should be some order to the language lists, but now is a bad time to do it because of conflicts. Could you add an issue about that so it gets taken care of? Thanks, and welcome to free-programming-books!

Yes, agreed. An issue already exists at https://github.com/EbookFoundation/free-programming-books/issues/5762 as @davorpa pointed out earlier.
Glad to contribute. Thanks for your work on the repo!


Custom output payloads inconsistent documentation

Rasa version: 1.8.2
Python version: 3.6.9
Operating system (windows, osx, ...): Ubuntu 18.04
Issue:
The Rasa documentation for custom payloads shows an example payload:
responses:
  utter_take_bet:
  - custom:
      blocks:
      - type: section
        text:
          text: "Make a bet on when the world will end:"
          type: mrkdwn
        accessory:
          type: datepicker
          initial_date: '2019-05-21'
          placeholder:
            type: plain_text
            text: Select a date

Using this example yields an empty response on an socket.io channel:
["bot_uttered", null]
0: "bot_uttered"
1: null

I've traced this to the socket.io channel implementation at line #107. At this point the json object looks like:
{"blocks": [{"accessory": {"initial_date": "2019-05-21", "placeholder": {"text": "Select a date", "type": "plain_text"}, "type": "datepicker"}, "text": {"text": "Make a bet on when the world will end:", "type": "mrkdwn"}, "type": "section"}]}

The object is unpacked into the socket.io emit function which doesn't have a blocks parameter.
To get the custom response either the blocks item in the yaml example has to be changed to data (i.e. the name of the parameter in the emit function) or the json object should just be passed on into the emit function instead of being unpacked.

Thanks for the issue, @alwx will get back to you about it soon!
You may find help in the docs and the forum, too 🤗

Hi @Flythe, it is specified that this payload is a slack payload:
For example, although date pickers are not a defined parameter in responses because they are not supported by most channels, a Slack date picker can be sent like so:

Notive that is says it is supported by slack and not most channels. This payload will not work in socket.io; that is why it is a custom payload.

That specific example is said to be slack only. But the documentation also states that:

You can also send any arbitrary output to the output channel using the custom: key.

However, for the socket.io channel this will only work when the first key inside the custom key is data. Like so:
- custom:
    data:
      - text: "test"

This could be stated more clearly in the documentation. Or the socket.io channel's send_custom_json function could be adjusted to not unpack the json_message variable.

I'd prefer to keep it the way that is is (need to wrap in data) to match the documentation here. Would you like to contribute documentation to that point about how to send custom data? I think it should live on the socketio docs, as its not scalable to put information about all of the connectors on that domains page. in other words here: https://rasa.com/docs/rasa/user-guide/connectors/your-own-website/#websocket-channel

I guess an alternative contribution could be handling both -- i.e. look for the data param, and if it's not there, try to wrap it that way. You should also print a UserWarning to tell the user that they should wrap it in the data param after sending it through. What do you think?

That sounds like a good solution, I'll put it on my backlog to contribute this change.

Awesome, we'd love your contribution.


docs: update stacking readme

This PR was published to npm with the version 6.0.3-pr.fb44b60.0
e.g. npm install<EMAIL_ADDRESS>--save-exact

update 2.1 stacking docs
changes language to "pool" instead of "delegator" in some places, to avoid confusion

Codecov Report

Merging #1410 (abb6f2d) into master (272028e) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1410   +/-   ##
=======================================
  Coverage   63.49%   63.49%
=======================================
  Files         116      116
  Lines        8500     8500
  Branches     1875     1875
=======================================
  Hits         5397     5397
  Misses       2974     2974
  Partials      129      129

Impacted Files
Coverage Δ

packages/stacking/src/index.ts
90.27% <ø> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


z-tech/stir

What does this PR do?

implements STIR found at https://github.com/WizardOfMenlo/stir
implements direct LDT
implements traits for LDT, Prover, and Verifier
implements traits for Statement and Witness

What does this PR not include?

FRI mapped to the same traits comes in a separate branch

Future plans:

Nimue
Rayon

@Pratyush @WizardOfMenlo there's an open question about if we want to include blake3 as a Merkle tree in crypto-primitives. See this file: https://github.com/WizardOfMenlo/stir/blob/main/src/crypto/merkle_tree/blake3.rs
I'm resolving all other comments related this for now.


⚠ GitLab Server has degraded performance

In a5005e5, GitLab Server (https://gitlab01.its-telekom.eu) experienced degraded performance:

HTTP code: 200
Response time: 17893 ms

Resolved: GitLab Server performance has improved in 9052044.


Forks Don't Fork Data

Need to implement data forking on DoltLab

Disabled forking in DoltLab as of doltlab-v0.2.0


Update to 16.04 final release

Not tested; simply data on http://releases.ubuntu.com/16.04/ were my
friend.

Sorry I don't think this will work. 16.04 still have  the bug that 15.10 have that requires another boot_command.

Sorry I don't think this will work. 16.04 still have the bug that 15.10 have that requires another boot_command.

@rickard-von-essen are you sure? All I did is update already existing Ubuntu 16.04 Beta file which presumably was successfully used to make the boxcutter Ubuntu 16.04 Beta box on Atlas. But maybe there is some circumstance I am missing?

👍 Seems OK on VMware Fusion 7


task ':app:shrinkReleaseRes'.

This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.
Originally posted by @github-actions[bot] in https://github.com/flutter/flutter/issues/58791#issuecomment-901633729
* What went wrong:
Execution failed for task ':app:shrinkReleaseRes'.
> Multiple task action failures occurred:
   > A failure occurred while executing com.android.build.gradle.internal.tasks.ShrinkResourcesOldShrinkerTask$SplitterRunnable
      > org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 37; A pseudo attribute name is expected.
   > A failure occurred while executing com.android.build.gradle.internal.tasks.ShrinkResourcesOldShrinkerTask$SplitterRunnable
      > org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 37; A pseudo attribute name is expected.
   > A failure occurred while executing com.android.build.gradle.internal.tasks.ShrinkResourcesOldShrinkerTask$SplitterRunnable
      > org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 37; A pseudo attribute name is expected.

@vishweshsoni
Please don't use an issue comment to file a new issue. There's a new issue template that you can use and fill out requested details so that we'll have enough details to properly address this issue. Currently there's not enough details with what you provided above to make it actionable.
Please provide flutter doctor -v, steps to replicate and a complete minimal reproducible code sample that shows the exception you are getting.


/sdcard has encryption enabled and files are not useable

After booting into the recovery and browsing the filesystem, everything looks a little bit "garbled". Especially the /sdcard doesn't seem to be alright. Here you can only see folders with "GUID"-like names and no contents. Also there are two drives with zero bytes able to select when trying to change between external and internal memory.
My guess is, that the fstab is either not compatible or flat out wrong. Maybe a switch to that ominous fstab v2 format could fix it, but I need to do some more research.

https://github.com/ADeadTrousers/twrp_device_Unihertz_Atom_XL/commit/78cb78abda554bbbe44a95b6330865f11921d9f6

Still no luck in getting decryption to work.

Still no luck in getting decryption to work.

According to https://github.com/PeterCxy/android_device_umidigi_F1/tree/twrp-9.0 and https://github.com/Vgdn1942/android_device_blackview_bv9500plus one would need a keystore*.so file but I couldn't find any in the stock rom.
1c54597e6008364eba9e6b909985750dc62db5e9
Latest try prevents a successful boot so as a workaround I deactivated /data completely. Can't factory reset now though.

The trustkernel daemon (teed) seems to be operational now: 6a79d27a39a9dabb12995af7c24666a36b2e44d1
I'm more and more convinced that the Atom L/XL uses FBE instead of FDE and according to some sources on the net TWRP only supports FDE.

Ok, I need to revoke my previous comment: There is a FBE switch in TWRP e590bd635c0cb3bc2368b05f215370fae3a55aea
It's just not working though.

By logging through the code I came to the function "decryptWithKeymasterKey" in "KeyStorage.cpp" which fails.
So it seems that the problem lies with correctly registering keymaster service. I'm looking at you manifest.xml and compatibility_matrix.xml.
Including them at the correct patch ".../etc/vintf" lets TWRP freeze on boot. So something must be going on there. Need more intel.

ErrorCode in Keymaster4.cpp in function Keymaster::begin at mDevice->begin is -33.
According to hardware/interfaces/keymaster/4.0/types.hal this means ErrorCode::INVALID_KEY_BLOB
Could it be that a 'wrong' keymaster instance is being used?

Maybe a little bit more elaboration:
According to KeyStorage.cpp the keyfile is stored in /data/unencrypted/key/keymaster_key_blob.
A little bit of research brought me to https://forum.xda-developers.com/t/rom-official-nightly-lineageos-16-0-for-oneplus-3-3t.3866517/post-80122746
So there seems to be a problem with formatting of the key blob.

Finally!
Decryption is working now. One needs to set PLATFORM_SECURITY_PATCH 4376593c79c5cd133e30ed3e18a8af8329ada8d9
Now the ErrorCode::KEY_REQUIRES_UPGRADE is thrown. I believe that's because the key blob is created with a lower timestamp than 2099-12-31. Anyway now TWRP logs that it was able to decrypt /data. Checking with File Manager or adb shell confirms that.
BUT
Everything in the user scope /data/media/0 is still encrypted. According to the logs the file /data/system/gatekeeper.pattern.key is missing. Only that this file doesn't even exists when the system boots and that encrypts just fine.
So my guess is that it is either named differently, located somewhere else or another authentication method than gatekeeper is used by LineageOS.

I'm pretty sure now that LOS (Stock Android 10?) is using the synthetic password method. According to Decrypt.cpp all information is stored in /data/system_de/<userid>. Checking this folder from LOS I can see various key and pwd files but navigating to it from TWRP it's still garbled (= encrypted). As I now already have a decrypted /data/system there needs to be another step in decryption that is still missing for /data/system_de.


Build error when deploying via Now - unable to use styled-components

I'm interested in using styled-components with NextJS SSR and deploying via Now. While everything builds and runs without errors locally (as shown in the image below), attempting to deploy via Now results in one of two errors as shown below in the current behavior section.
Expected Behavior
The app should deploy via Now successfully and render index.js with styled-components just as it does when running npm run dev or npm run start.
This is what the rendered page should look like:

This is the expected response from now-cli:

Current Behavior
Error 1 (no longer appearing for some reason):

Error 2 (this one is now constantly appearing):

Steps to Reproduce (for bugs)

Download and install Now - https://zeit.co/now#get-started
Clone my repo: git clone https://github.com/tedjames/nextjs-deploy.git
Run: npm install
Run: npm run build
Run: now

Context

The application can only be deployed via Now by removing the styled-components package and removing all instances of styled-components from pages/index.js and pages/_document.js
I'm using this tutorial for configuring styled-components: https://bilalbudhani.com/using-next-js-with-styled-components/

Your Environment

Tech
Version

npm
5.8.0

yarn
1.5.1

node
8.9.4

next
^5.1.0

OS
Mac OS Sierra 10.12.6 (16G1114)

browser
Google Chrome

express
^4.16.3

react
^16.3.0

styled-components
^3.2.5

Any help would be greatly appreciated!
I'm really excited about using NextJS but without knowing why a simple app like this can't be deployed via Now, I don't feel comfortable using this framework on some upcoming projects that could really benefit from SSR.
Thanks,
Ted

Thanks to @timneutkens, this issue has been solved 🎉
I had somehow ended up with both a package-lock.json and yarn.lock which caused the error.
After deleting both those files and running yarn to regenerate the lock file, I was able to finally deploy via Now.
On another note, the lack of an error message is apparently a separate issue itself which @timneutkens is now in the process of resolving. I'll leave this issue open for now until this has been resolved or until a separate issue has been opened.

Opened a PR 👍


Added Structurer 1.2

Seeing as url doesn’t point to a specific version, this cask should use version :latest and sha256 :no_check. See an example.

Thanks, I committed the changes you recommended


feat: create application

Create Microsoft Entra ID application and corresponding service principal.

@equinor/ops-coredev, could you please take a look? I'm unsure as to what more would be needed/recommended here.

Can't approve my own PR, but looks like a good starting point to me 🙂


Form Validation Zod Type Error on Validators

Describe the bug
Noticed this type error appears when validating on form level. Stackblitz isn't previewing for me so not sure if the link will work and you might have to open it locally.
const formSchema = z.object({
	firstName: z.string().min(3, "First name must be at least 3 characters"),
	lastName: z.string().min(3, "Last name must be at least 3 characters"),
});

type FormSchema = z.infer<typeof formSchema>;

const form = useForm<FormSchema, ZodValidator>({
		defaultValues: {
			firstName: "",
			lastName: "",
		},
		onSubmit: async ({ value }) => {
			// Do something with form data
			console.log(value);
		},
		validators: {
			// Error: Type '({ value }: { value: any; }) => string | undefined' is not assignable to type 'ZodType<any, ZodTypeDef, any>'.
			onChange({ value }) {
				const result = formSchema.safeParse(value)

				return result.success
					? undefined
					: result.error.errors.map((err) => err.message).join(", ");
			},
		},
		// Add a validator to support Zod usage in Form and Field
		validatorAdapter: zodValidator(),
	});

Your minimal, reproducible example
https://stackblitz.com/edit/tanstack-form-rbhrif?file=src/index.tsx
Steps to reproduce
run repro
Expected behavior
no error
How often does this bug happen?
None
Screenshots or Videos
No response
Platform
macos
TanStack Form adapter
react-form
TanStack Form version
0.29.2
TypeScript version
No response
Additional context
No response

Good news, the error is correct and we can simplify your code to make it work :)
Here you declared that you using a validator (zod) and you made explicit with the type:
const form = useForm<FormSchema, ZodValidator>({
  ...
  validatorAdapter: zodValidator()
}

Which is the same as telling the form "hey, I'm not defining a validator myself, I'm gonna use zod".
However in the onChange function you provided a manual validator, when the form was expecting a zod schema.
If you want to get the best out of the validator, your onChange will be as simple as:
onChange: formSchema

And you can also remove the explicit types from the form definition, they're only needed when creating custom components but as long as you don't need to pass the form instance anywhere, types are inferred automatically
-const form = useForm<FormSchema, ZodValidator>({
+const form = useForm({


Fixing minor typos in error messages

While reading through the source I've stumbled upon two minor typos in some error messages. Hope this helps. Cheers!

@timbuckley wouldn't be a problem - batching this will make it easier for everyone :-), I think there will be time on the weekend.

Closing request, commits have been merged into #1666


feat: Tower.context

closes #94

Releasing and testing out #98 for a while, then will come back to this one and re-evaluate


Build error

When tried to build using make -j, I get the following error:
system/manager.cpp:69:6: error: this ‘for’ clause does not guard... [-Werror=misleading-indentation]
for (UInt32 i = 0; i < g_thread_cnt; i++)
^~~
system/manager.cpp:72:3: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘for’
if (min > _min_ts)
^~
cc1plus: all warnings being treated as errors
Makefile:28: recipe for target 'system/manager.o' failed
make: *** [system/manager.o] Error 1
make: *** Waiting for unfinished jobs....
It seems like this stops the build from completing.

Hi,
I have fixed the indentation and pushed the code. Please try again.
Thanks

Hello,
Thank you and it did fix the error issue. However, another error shows up as
/usr/bin/ld: ./libs/libjemalloc.a(jemalloc.o): relocation R_X86_64_32 against undefined hidden symbol je_arenas_lock' can not be used when making a PIE object /usr/bin/ld: ./libs/libjemalloc.a(arena.o): relocation R_X86_64_32 against hidden symbol je_tcache_thread_cleanup' can not be used when making a PIE object
/usr/bin/ld: ./libs/libjemalloc.a(base.o): relocation R_X86_64_32 against .bss' can not be used when making a PIE object; recompile with -fPIC /usr/bin/ld: ./libs/libjemalloc.a(chunk.o): relocation R_X86_64_32 against undefined hidden symbol je_chunks_mtx' can not be used when making a PIE object
/usr/bin/ld: ./libs/libjemalloc.a(chunk_dss.o): relocation R_X86_64_32 against .bss' can not be used when making a PIE object; recompile with -fPIC /usr/bin/ld: ./libs/libjemalloc.a(chunk_mmap.o): relocation R_X86_64_32 against .rodata.str1.8' can not be used when making a PIE object; recompile with -fPIC
/usr/bin/ld: ./libs/libjemalloc.a(ctl.o): relocation R_X86_64_32 against .rodata' can not be used when making a PIE object; recompile with -fPIC /usr/bin/ld: ./libs/libjemalloc.a(huge.o): relocation R_X86_64_32 against undefined hidden symbol je_huge_mtx' can not be used when making a PIE object
/usr/bin/ld: ./libs/libjemalloc.a(mutex.o): relocation R_X86_64_32 against .rodata.str1.8' can not be used when making a PIE object; recompile with -fPIC /usr/bin/ld: ./libs/libjemalloc.a(prof.o): relocation R_X86_64_32 against undefined hidden symbol je_opt_prof_prefix' can not be used when making a PIE object
/usr/bin/ld: ./libs/libjemalloc.a(quarantine.o): relocation R_X86_64_32S against undefined hidden symbol je_arena_bin_info' can not be used when making a PIE object /usr/bin/ld: ./libs/libjemalloc.a(stats.o): relocation R_X86_64_32 against .rodata.str1.1' can not be used when making a PIE object; recompile with -fPIC
/usr/bin/ld: ./libs/libjemalloc.a(tcache.o): relocation R_X86_64_32S against undefined hidden symbol je_arena_bin_info' can not be used when making a PIE object /usr/bin/ld: ./libs/libjemalloc.a(util.o): relocation R_X86_64_32 against .rodata.str1.1' can not be used when making a PIE object; recompile with -fPIC
/usr/bin/ld: ./libs/libjemalloc.a(tsd.o): relocation R_X86_64_32S against .bss' can not be used when making a PIE object; recompile with -fPIC /usr/bin/ld: ./libs/libjemalloc.a(ckh.o): relocation R_X86_64_32 against hidden symbol je_tcache_thread_cleanup' can not be used when making a PIE object
/usr/bin/ld: final link failed: Nonrepresentable section on output
collect2: error: ld returned 1 exit status
Makefile:20: recipe for target 'rundb' failed
make: *** [rundb] Error 1
As a result, the rundb isn't created. Also this time the error doesn't appear like other errors on terminal which is in bold red.
Thanks for your time

Someone posted an issue on this before:
https://github.com/yxymit/DBx1000/issues/24#issue-500864868
Just add  -no-pie  to Makefile.

Thank you and it has fixed the issue! Have a great evening


use 20 plus period for idbr date (not submitted_at), use 1604 as test…

… period - more realistic data

Noted we've taken out NEW_LINE, which is good. Not used, but I was thinking that's going to depend on the downstream system rather than the system we're doing the transform on?


This is a security test as part of a bug bouty, plese ignore.  xfcngo

This is a security test as part of a bug bouty, plese ignore.  xfcngo

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


WIP Add SYMBOLPREFIX and/or SYMBOLSUFFIX to cblas prototypes

for #2751

Thanks for the PR. I applied the changes and noticed some glitches:
float  cblas_sasum _64(OPENBLAS_CONST blasint n, OPENBLAS_CONST float  *x, OPENBLAS_CONST blasint incx);
double cblas_dasum _64(OPENBLAS_CONST blasint n, OPENBLAS_CONST double *x, OPENBLAS_CONST blasint incx);
float  cblas_scasum_64(OPENBLAS_CONST blasint n, OPENBLAS_CONST void  *x, OPENBLAS_CONST blasint incx);
double cblas_dzasum_64(OPENBLAS_CONST blasint n, OPENBLAS_CONST void *x, OPENBLAS_CONST blasint incx);

Yes, also entries like cblas_srotg where the first argument is not an OPENBLAS_CONST, I beed to come up with a better replacement rule for sed (I know that it is possible to search-replace with wildcards so cblas_something transforms into prefix_cblas_something_suffix, I just need to look up the exact syntax).

@Zha0q1 Can you confirm whether #2753 solves the issue? @martin-frbg Thanks for quickly providing a fix !

Sure, I replied to the PR last week and have not been able to test the new version. Will find time to do so and reply to the PR directly. @martin-frbg  Thanks for the update!


infinite recursion error during sage compilation

After brew cask install sage, the resulting sage build complains that it didn't complete properly.
$ sage
RuntimeError: maximum recursion depth exceeded during compilation
┌────────────────────────────────────────────────────────────────────┐
│ SageMath Version 6.10, Release Date: 2015-12-18                    │
│ Type "notebook()" for the browser-based notebook interface.        │
│ Type "help()" for help.                                            │
└────────────────────────────────────────────────────────────────────┘
The Sage installation tree has moved
from /Users/buildslave-sage/slave/binary_pkg/build/source/SageMath/jc4b6yulaujayb9sr94ia88eourzeqip0oidma
  to /opt/homebrew-cask/Caskroom/sage/6.10/SageMath-6.10.app/Contents/Resources/sage
Updating various hardcoded paths...
(Please wait at most a few minutes.)
DO NOT INTERRUPT THIS.
Done updating paths.
Traceback (most recent call last):
  File "/opt/homebrew-cask/Caskroom/sage/6.10/SageMath-6.10.app/Contents/Resources/sage/src/bin/sage-ipython", line 8, in <module>
    from sage.repl.readline_extra_commands import *
ImportError: dlopen(/opt/homebrew-cask/Caskroom/sage/6.10/SageMath-6.10.app/Contents/Resources/sage/local/lib/python2.7/site-packages/sage/repl/readline_extra_commands.so, 2): Library not loaded: /Users/buildslave-sage/slave/binary_pkg/build/source/SageMath/jc4b6yulaujayb9sr94ia88eourzeqip0oidma/local/lib/libreadline.6.dylib
  Referenced from: /opt/homebrew-cask/Caskroom/sage/6.10/SageMath-6.10.app/Contents/Resources/sage/local/lib/python2.7/site-packages/sage/repl/readline_extra_commands.so
  Reason: image not found

$ specs brew os
specs --version
0.21

brew --version
Homebrew 0.9.5 (git revision 97159; last commit 2016-02-06)

system_profiler SPSoftwareDataType | grep 'System Version'
    System Software Overview:
      System Version: OS X 10.11.3 (15D21)
      System Integrity Protection: Enabled

~$ specs sage brew os
specs --version
0.21

sage --version
RuntimeError: maximum recursion depth exceeded during compilation
SageMath Version 6.10, Release Date: 2015-12-18

brew --version
Homebrew 0.9.5 (git revision 97159; last commit 2016-02-06)

system_profiler SPSoftwareDataType | grep 'System Version'
    System Software Overview:
      System Version: OS X 10.11.3 (15D21)
      System Integrity Protection: Enabled

Only thing we do is download it and link it, we don’t change it. You’ll have to contact them.
Also, try to install it manually.


Request adding get_confirmed_transaction_with_config

I want to know whether a transaction succeeds in 1 confirmation but get_confirmed_transaction will wait about 19 seconds for about 25 confirmations.

Because get_confirmed_transaction returns transactions at the finalized commitment level by default (due to historical reasons).
We recently added a get_confirmed_transaction_with_config method, and through the config struct you can request CommitmentConfig::confirmed() [2] instead of the default of CommitmentConfig::finalized()

from mvines core contributor of solana

Closed as getConfirmedTransaction has since been deprecated


Start Warzone/ColdWare - battlenet fail

Description
When I launch blizzard games,
it often happens (70% of the time) that the launcher battlenet starts but waits for you to click on "Play".
The problem often occurs when the launcher service is not yet started on the computer.
My friend also has the same problem.
To Reproduce
start warzone/coldwar in playnite
screenshot
https://www.youtube.com/watch?v=-6yXOk-P6vw
Diagnostics ID
Playnite Version : 8.11
Battlenet launcher : <IP_ADDRESS>79
Windows 10 Pro 1909 ( Build 18363.1979 )
I see this issue seem to be fixed : https://github.com/JosefNemec/Playnite/issues/692

Closing since this is not issue on our side.


[apptools-android] Add case to test the app icon for apptools android

The better fitting size icon is used as app icon
Impacted tests(approved): new 1, update 0, delete 0
Unit test platform: [Android]
Unit test result summary: pass 1, fail 0, block 0
https://crosswalk-project.org/jira/browse/XWALK-5079
https://crosswalk-project.org/jira/browse/XWALK-5082

The test case name does not make sense, does not indicate the checkpoint.

The checkpoint of this case is that the better fitting size icon will be used as the app icon.

LGTM


Housekeeping: deps upgrade

Proposed changes:

moto upgrade: https://github.com/RasaHQ/rasa/pull/12002

Status (please check what you already did):

[ ] added some tests for the functionality
[ ] updated the documentation
[ ] updated the changelog (please check changelog for instructions)
[ ] reformat files using black (please check Readme for instructions)

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


nmea2tfpose sim mode not working.

Bug report
Required information:

Operating system and version:

Ubuntu 18.04

Autoware installation type:

Locally generated docker container

Autoware version or commit hash

43330aef349dde0d17d9a7050f5ae6bf808b73b3

ROS distribution and version:

melodic

ROS installation type:

ROS was installed by docker script.

Package or library, if applicable:

gnss_localizer

Description of the bug

In gnss_localizer, nmea2tfpose has Simulation Mode. When I clicked it, /gnss_pose topic was not applied for simulation mode. With simulation mode activated, plane number 0 should be applied internally. However, regardless of simulation mode activation, existed plane number is still be applying to the gnss_localizer node.
Steps to reproduce the bug

Launch lgsvl simulator.
Launch runtime_manager

$ roslaunch runtime_manager runtime_manager.launch

On the Quick Start tab, activate Map, Sensing, Localization.
On Computing tab, click app for nmea2tfpose in gnss_localizer.
Click Simulation Mode.
Check rostopic echo like the following

$ rostopic echo /gnss_pose -n 1

Expected behavior

/gnss_pose has pose without adding origin coordinate
When plane number is 7, simulation mode is activated
$ rostopic echo /gnss_pose -n 1
header:
  seq: 78
  stamp:
    secs:<PHONE_NUMBER>
    nsecs: 615610624
  frame_id: "map"
pose:
  position:
    x: -9.03081818061
    y: 50.3633886972
    z: -1.122381
  orientation:
    x: 0.550936004788
    y: 0.569652790116
    z: 0.42817032443
    w: 0.434321759319
---

Actual behavior

When plane number is 7, simulation mode is activated
$ rostopic echo /gnss_pose -n 1
header:
  seq: 0
  stamp:
    secs:<PHONE_NUMBER>
    nsecs: 445789184
  frame_id: "map"
pose:
  position:
    x: -86029096.0418
    y: -3981885.24795
    z: -1.122381
  orientation:
    x: 0.550936004788
    y: 0.569652790116
    z: 0.42817032443
    w: 0.434321759319
---

Screenshots

Additional information

Closed by #11.


US152271 - Cleanup appropriate folders in the plugin during runs

Option 2 - alternative to https://github.com/BrightspaceUI/testing/pull/32.
After using both I prefer this one - the things that get cleared "make sense" and feel intuitive, whereas the other solution has some compromises.

I agree that this one feels better somehow... like the code responsible for creating the mess is also cleaning it up. Except that the reporter makes the report.html files.

And I think we'll need some kind of info manager to pass things between the plugin and the reporter for that, and that manager can own the name for report.html


I have question

Can Enable / Disable per world ?
Sample:
//Blacklist Plugin Quests per world
Blacklist:

world_Nether
world_End

Blacklist if for players only. If you which to disable features per-world, use a permissions plugin.

For example:
a player get quests Kill Player in world name: Survival and When player teleport to world name: minigame. and a player play the Bedwars Game. When player kill other player in Bedwars Game so Quests Kill Player still running
I must use permission ??
Sorry for My English is not good

@jomjonejame Ah that makes sense. I believe revoking Quest permissions in the minigame world should fix the problem. If not, open a new Github issue with a sample quest (from the quests.yml file).


how to use it

the old codeplex is gone, as I am sure you are aware. Maybe mention this site in the readme https://www.devtrends.co.uk/blog/validating-wcf-service-operations-using-system.componentmodel.dataannotations

Done


fftpack.rfft overwrites data when input is a pandas series

Reproduce:
import pandas as pd
import numpy as np
from scipy import fftpack

x = np.array([1.,2.,3.,4.,5.])
xs = pd.Series(x)

print x
tmp = fftpack.rfft(x)
print x

print x
tmp = fftpack.rfft(xs)
print x

"""
output:
[ 1.  2.  3.  4.  5.]
[ 1.  2.  3.  4.  5.]
[ 1.  2.  3.  4.  5.]
[ 15.          -2.5          3.4409548   -2.5          0.81229924]
"""

posted also in scipy.github:
https://github.com/scipy/scipy/issues/5790

I would say this is a scipy issue. Series is essentially a duck-like ndarray, so I don't see why it should inplace modify it.


Mask visualization problem

I tried to visualize the mask image with the code below:
output = 1-(occ_mask - occ_mask.min()) / (occ_mask.max() - occ_mask.min())
io.imsave(os.path.join(seq_output_folder, fname), output)
The result is not the same with your paper claimed.
Are there any problems here?

The code is misleading - MaskFlownet model does not return occlusions. If you look at the paper, this model is composed of several MaskFlownet_S, with no occlusion output in the end (figure 2 in the paper).
Thus, occlusions can be obtained only from running MaskFlownet_S, and the results are similar to the visualization.
You don't need to use normalisation there, checking min and max shows that occlusions are in range [0, 1]. Meanwhile when I ran MaskFlownet, the output was obviously optical flow, not occlusions.

@lizzardhub Thank you very much. I have tried to use MaskFlownet_S configuration and model, the output occ_mask is the same with paper claimed.

Thanks a lot. But, how can I infer in my own data by MaskFlownet_S?

@lizzardhub Thank you very much. I have tried to use MaskFlownet_S configuration and model, the output occ_mask is the same with paper claimed.

The code is misleading - MaskFlownet model does not return occlusions. If you look at the paper, this model is composed of several MaskFlownet_S, with no occlusion output in the end (figure 2 in the paper).
Thus, occlusions can be obtained only from running MaskFlownet_S, and the results are similar to the visualization.
You don't need to use normalisation there, checking min and max shows that occlusions are in range [0, 1]. Meanwhile when I ran MaskFlownet, the output was obviously optical flow, not occlusions.


Crash when using with mocha

While using as compiler to mocha it breaks when trying to load the file because it lacks an test/ in the path, like in:
Test routines path: /home/user/projects/project/test
Tmp path (to transpired test routines): /home/user/projects/project/tmp/tsreq/test/test

After some other tests, it actually doesn't lacks one test/ in the path. It seems to get confused while joining the string to generate the full path. I managed to hard code the missing segment. It worked in the first time, but then it started to add another equal segment and the path still broken.

@fmsouza had the same issues, I switched to espower-typescript. ts-node was acting up with jsdom

@mendrik I stopped using this module long ago. At first, I was compiling the code to commonjs with gulp and running the tests with the js code. Then I discovered ts-node and used it's driver in mocha to run the tests directly. Worked very well.


[BUG] in sample: LinkedIn Auth __session cookie does not persist when function is called by popup.html

Which sample has a bug?
LinkedIn Auth
How to reproduce the issue
Use popup.html and cloud functions as expected, however, due to node-linkedin deprecation, use axios to query for profile data. I would be willing to submit this for a PR once this bug is figured out.
Steps to set up and reproduce
Follow LinkedIn sign in flow, redirect function -> token function, etc.
Debug output
req.cookies.__session returns null. However, if the token function is called manually (i.e., console.log popup.html's script.src and following the link), the __session cookie is there.
Errors in the
console logs
Screenshots

Cookie in redirect

Cookie in token function when called by popup

Cookie in token function when called manually
Expected behavior
Cookie is null
Actual behavior
Cookie persists

Hi, I am facing the same issue. Have you resolved this?


feat: android media control notification naming customize

change to notification name & id for strings.xml

@dcvz sure, i fixed two of your requests. Please check them out


Setting the mode of multiple Homebase units. Stops working and then needs to be reloaded to make it work again.

I am usinf the eufy_security integration together with the eufy-security-ws add on.
I have three Homebase Units 1,2 and 3.
I have one Eufy Keypad connected to Homebase 1 and have written automation rountines to set two other Homebase units (2 and 3) to whatever mode Homebase 1 is set to with the keypad (Home, Away, Off)
This all works fine but for some reason stops working on a daily basis (one thing to note is that my Homeassisant PC automatically reboots every day just after midnight) which might be connected?
I do not know the cause of what makes it stop working but restarting eufy-security-ws and reloading the eufy_security integration fixes it.
Anyone have any ideas?

Home Assistant Installation Type (OS):
Home Assistant Core Version: core-2023.11.0
Eufy Security Add-on Version: 1.6.4
Eufy Security Integration Version: I do not know where to find this?

Hardware Information;

Camera Model:n/a

Live Streaming Protocol (RTSP/P2P): n/a

Debug Logs from Home Assistant (https://github.com/fuatakgun/eufy_security/discussions/624) - Without this, I will automatically resolve this issue

Logs from Eufy Security Add-on (either from Add-ons page of Home Assistant or Docker output):

Would you share your device with me in case further debugging required? (Yes/No):

Additional context
This error was noted....
Error: <Task finished name='Task-483716' coro=<WebSocketClient._process_messages() done, defined at /config/custom_components/eufy_security/eufy_security_api/web_socket_client.py:62> result=None>

Follow the bug template and fill all the fields. Be sure that you are on the latest version of integration as it is supposed to recover itself from broken connection

I am running into this myself. Everything else works for me (which is a doorbell, I do not have a camera or anything else from eufy yet), but eventhough the selection of the guard mode seems to work, it does not apply this setting. I can reboot the homebase from the integration no problem, so there seems to be a working connection.
Restarting both the add-on and reloading the integration fixes it.
I will be updating you as it happens again and will try to gather a little more information for you to work with.

I added some automation that checks the state of my three homebase units 'whenever there is a state change in one of them'. This returns an 'alarm set correctly' or 'alarm did not set correctly' warning. I linked this to an alexa announcement so at least this will tell me when it did not work and allow me to investigate the log.

It failed this morning and here is the log... I have xxxx out the IP and the first part of the station ID
I am running eufy-security-ws version: 1.7.1
Core 2023.11.2
Supervisor 2023.11.0
Operating System 11.1
Frontend 20231030.2
}
2023-11-14 02:27:10.430  WARN Heartbeat check failed for station xxxBA. Connection seems lost. Try to reconnect...
2023-11-14 02:27:10.435  INFO  Disconnected from station xxxBA
2023-11-14 02:27:30.723  WARN Tried all hosts, no connection could be established to station xxxBA.
2023-11-14 02:27:30.725  INFO  Timeout connecting to station xxxBA
2023-11-14 02:27:55.770  WARN Tried all hosts, no connection could be established to station xxxBA.
2023-11-14 02:27:55.773  INFO  Timeout connecting to station xxxBA
2023-11-14 02:28:16.083  INFO  Connected to station xxxBA on host 192.168.xxx.xxx and port xxxxx
2023-11-14 03:28:36.734  WARN Heartbeat check failed for station xxxBA. Connection seems lost. Try to reconnect...
2023-11-14 03:28:36.736  INFO  Disconnected from station xxxBA
2023-11-14 03:28:57.009  WARN Tried all hosts, no connection could be established to station xxxBA.
2023-11-14 03:28:57.011  INFO  Timeout connecting to station xxxBA
2023-11-14 03:29:22.058  WARN Tried all hosts, no connection could be established to station xxxBA.
2023-11-14 03:29:22.062  INFO  Timeout connecting to station xxxBA
2023-11-14 03:29:57.071  ERROR All address lookup tentatives failed.
{
stationSN: 'xxxBA'
}
2023-11-14 03:29:57.084  INFO  Timeout connecting to station xxxBA
2023-11-14 05:50:02.838  INFO  Push notification connection closed
2023-11-14 05:50:08.332  INFO  Push notification connection successfully established
2023-11-14 06:34:58.336  WARN Heartbeat check failed for station xxx84. Connection seems lost. Try to reconnect...
2023-11-14 06:34:58.338  INFO  Disconnected from station xxx84
2023-11-14 06:35:18.637  WARN Tried all hosts, no connection could be established to station xxx84.
2023-11-14 06:35:18.642  INFO  Timeout connecting to station xxx84
2023-11-14 06:35:43.689  WARN Tried all hosts, no connection could be established to station xxx84.
2023-11-14 06:35:43.691  INFO  Timeout connecting to station xxx84
2023-11-14 06:36:18.703  ERROR All address lookup tentatives failed.
{
stationSN: 'xxx84'
}
2023-11-14 06:36:18.705  INFO  Timeout connecting to station xxx84
2023-11-14 06:36:48.728  INFO  Connected to station xxx84 on host 192.168.xxx.xxx and port xxxxx
2023-11-14 08:37:37.058  INFO  Received push notification for changing guard mode
{
guard_mode: 3,
current_mode: 3,
stationSN: 'xxx84'
}
Let me know if you need any further info. @fuatakgun

thanks for detailed logs but you see that add-on is having issues communicating with your station devices (home bases) right?
Throughout these failures, messages will be lost or commands will not be sent to physical devices.
So, I would blame the network directly and I would suggest you to set up an ping based device tracker on home assistant to check if home base devices are having connection issues at all. If yes, you should fix network issues, if not, you should reach out to bropat to help us the root cause why the connection is dropping.

thanks for detailed logs but you see that add-on is having issues communicating with your station devices (home bases) right? Throughout these failures, messages will be lost or commands will not be sent to physical devices.
So, I would blame the network directly and I would suggest you to set up an ping based device tracker on home assistant to check if home base devices are having connection issues at all. If yes, you should fix network issues, if not, you should reach out to bropat to help us the root cause why the connection is dropping.

I agree the issue is something to do with the homebase connection issues, I have no idea why they are losing connection but I will look at this. However, this is the part of the log from today...
023-11-23 02:03:19.624  WARN Heartbeat check failed for station xxxBA. Connection seems lost. Try to reconnect...
2023-11-23 02:03:19.627  INFO  Disconnected from station xxxBA
2023-11-23 02:03:39.944  WARN Tried all hosts, no connection could be established to station xxxBA.
2023-11-23 02:03:39.946  INFO  Timeout connecting to station xxxBA
2023-11-23 02:03:50.032  INFO  Connected to station xxxBA on host 192.168.18.xxx and port xxxxx
2023-11-23 02:42:55.085  WARN Heartbeat check failed for station xxx84. Connection seems lost. Try to reconnect...
2023-11-23 02:42:55.088  INFO  Disconnected from station xxx84
2023-11-23 02:43:15.341  WARN Tried all hosts, no connection could be established to station xxx84.
2023-11-23 02:43:15.344  INFO  Timeout connecting to station xxx84
2023-11-23 02:43:25.368  INFO  Connected to station xxx84 on host 192.168.18.xxx and port xxxxx
But this time round the xxxBA and xxx84 homebase units re-connected, but in the previous log there was

ERROR All address lookup tentatives failed.
I dont know how long the add-on waits to before it decides to fail? And once it fails does it never attempt to connect again?

There is a maximum number of retries before giving up.

.

Do you know if there is a way I could montor for this "ERROR All address lookup tentatives failed" in the log and restart the add-on?

I fixed it :-). I added an automation which monitors the state of the hombase units and if they are not syncronised after changing a mode, it uses  Home Assistant Supervisor: Restart add-on. to restart the Eufy_security_WS add on.

In the meantime, i am working on a connection sensor to be used for this.

For the true fix, find the culprit if it is the network or hardware:-)

Makes sense, check in next release for connection specific sensor and you can react on it rather than waiting for them to be out of sync.
Resolving as of now


Modified the logging configuration

Moved the logging config from application.yml to logback.xml and logback-test.xml for separate configuration for testing. Stdout is now on by default for tests as there's much less noise thanks to root being set to error.
As a result it's now reasonable to use loggers in test classes, hopefully making for easier debugging. Travis logs should be siginificantly more readable as well.

Coverage remained the same at 81.605% when pulling e67b4eb3fe626cca569d86de2cdfba73782c1331 on Heliozoa:test-logging into abb28ffbeb516848d925f7d155f66295fda0aa3c on tdd-pingis:master.

Coverage remained the same at 81.605% when pulling a7f920c076ce9cd73cb376acba8b23e95d7ddb44 on Heliozoa:test-logging into abb28ffbeb516848d925f7d155f66295fda0aa3c on tdd-pingis:master.

Coverage remained the same at 81.605% when pulling a7f920c076ce9cd73cb376acba8b23e95d7ddb44 on Heliozoa:test-logging into abb28ffbeb516848d925f7d155f66295fda0aa3c on tdd-pingis:master.


ManagedClusterUpgradeProfileProperties.agentPoolProfiles is not marked as nullable

https://github.com/Azure/azure-sdk-for-rust/blob/8530b14828869e93f200894c7f79b6be3a3ed5e3/services/mgmt/containerservice/src/package_2021_03/models.rs#L1019-L1024
I can query this part of the API via a route such as azure_mgmt_containerservice::operations::managed_clusters::get_upgrade_profile().
Depending on the resources, of course, but I can get a null ("agentPoolProfiles": null) result for ManagedClusterUpgradeProfileProperties.agentPoolProfiles. This API/SDK will then error out during deserialization, throwing a:
Error: DeserializeError { source: Error("invalid type: null, expected a sequence", line: 18, column: 28)

for a JSON response like:
{
  "id": "/subscriptions/decafbad-d3ad-b33f-b000-deadf00dba11/resourcegroups/RedactedGroup/providers/Microsoft.ContainerService/managedClusters/RedactedCluster/upgradeprofiles/default",
  "name": "default",
  "type": "Microsoft.ContainerService/managedClusters/upgradeprofiles",
  "properties": {
   "controlPlaneProfile": {
    "kubernetesVersion": "1.18.17",
    "osType": "Linux",
    "upgrades": [
     {
      "kubernetesVersion": "1.19.7"
     },
     {
      "kubernetesVersion": "1.19.9"
     }
    ]
   },
   "agentPoolProfiles": null
  }
 }

Therefore, I believe this field (both, probably?) should be marked as an Option and skip_serializing_if = "Option::is_none")
However - this might be an error on the upstream api spec? re: https://github.com/Azure/azure-rest-api-specs/blob/1b0ed8edd58bb7c9ade9a27430759527bd4eec8e/specification/containerservice/resource-manager/Microsoft.ContainerService/stable/2020-03-01/managedClusters.json#L2187-L2193, it's not marked "x-nullable": true or non-required.

Probably something like https://github.com/serde-rs/serde/issues/1098 is needed for a type is "x-nullable": true.


[OPPRO-316] Support StddevSamp on Velox backend

What changes were proposed in this pull request?
This PR supports StddevSamp on Velox backend.
How was this patch tested?
Verified on Jenkins.

Thanks for your review!


autocast=False not respected when saving/loading Keras model

Please go to TF Forum for help and support:
https://discuss.tensorflow.org/tag/keras
If you open a GitHub issue, here is our policy:
System information.

Have I written custom code (as opposed to using a stock example script provided in Keras): Yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Windows 10
TensorFlow installed from (source or binary): Binary
TensorFlow version (use command below): 2.9.3
Python version: 3.9
Bazel version (if compiling from source): -
GPU model and memory: -
Exact command to reproduce: -

Describe the problem.
See https://github.com/tensorflow/tensorflow/issues/58940
In the below code, the intention is to create a model that takes an input of type float32 when saved, even if it is trained with mixed_precision. In this example, training code is omitted, and call() is just a placeholder for conciseness, but it still shows the issue.
The problem comes when loading the model. Because it has autocast=False I would expect that the model is saved with an input type of tf.float32. But it seems that the model is saved in an invalid state, because it loads with an error. If I use an input signature to force the input to be of type tf.float32, the error is the same.
The error is the same even if you call tf.keras.mixed_precision.set_global_policy("float32") before loading the model.
Standalone code to reproduce the issue.
import keras
import tensorflow as tf

class MyModel(keras.Model):
    def __init__(self):
        super().__init__(autocast=False)

    def call(self, inputs):
        return 0

def main():
    tf.keras.mixed_precision.set_global_policy("mixed_float16")

    model = MyModel()

    inputs = tf.zeros(shape=(1, 1), dtype=tf.float32)

    prediction_0 = model(inputs)

    model_path = "test_model"

    model.save(model_path)

    loaded_model = keras.models.load_model(model_path)

    prediction_1 = loaded_model(inputs)

if __name__ == "__main__":
    main()

Source code / logs.
ValueError: Exception encountered when calling layer "my_model" (type MyModel).

Could not find matching concrete function to call loaded from the SavedModel. Got:
  Positional arguments (1 total):
    * <tf.Tensor 'inputs:0' shape=(1, 1) dtype=float16>
  Keyword arguments: {}

 Expected these arguments to match one of the following 2 option(s):

Option 1:
  Positional arguments (1 total):
    * TensorSpec(shape=(None, 1), dtype=tf.float32, name='inputs')
  Keyword arguments: {}

Option 2:
  Positional arguments (1 total):
    * TensorSpec(shape=(None, 1), dtype=tf.float32, name='input_1')
  Keyword arguments: {}

Call arguments received by layer "my_model" (type MyModel):
  • args=('tf.Tensor(shape=(1, 1), dtype=float16)',)
  • kwargs=<class 'inspect._empty'>

Process finished with exit code 1

@SuryanarayanaY I was able to replicate the issue, please find the gist here. Thank you!

Similar to issue  #58937 with minor difference that this issue is without tf.function wrapper.

In the below code, the intention is to create a model that takes an input of type float32 when saved, even if it is trained with mixed_precision.

If you want a model that takes in an input of type float32, you instead can pass dtype="float32" to the the super constructor:
class MyModel(keras.Model):
  def __init__(self):
    super().__init__(dtype="float32")

  def call(self, inputs):
    return 0

This will cause the inputs in call to be float32 (even if float16 inputs are passed). Any layers you create in the model will still use the global policy dtype of mixed_float16 and therefore cast their inputs to float16. This is useful if you want the inputs and the initial computations of the model to be float32 but keep the rest of the model in mixed precision.
Still, this is a bug and should be fixed. But I'm not familiar with SavedModel enough to address this issue. @hertschuh, can you reassign to someone who works on SavedModel?

@reedwm Thanks for the suggested workaround! However it doesn't seem to work in the case of nested models, where we want the outer model to accept float32 input and the inner models to use float16 computation, e.g.
import keras
import tensorflow as tf
import numpy as np
from keras import Model, Input

class InnerModel(keras.Model):
    def call(self, inputs, training=None, mask=None):
        return inputs

class OuterModel(keras.Model):
    def __init__(self):
        super().__init__(autocast=False, dtype=tf.float32)
        self.inner_model = InnerModel()
        self.model = self.make_model()

    def call(self, inputs, training=None, mask=None):
        return self.model(inputs, training, mask)

    def make_model(self):
        im_input = Input(shape=())
        x = self.inner_model(im_input)
        return Model(inputs=[im_input], outputs=x)

def main():
    tf.keras.mixed_precision.set_global_policy("mixed_float16")

    model = OuterModel()

    inputs = [np.zeros(shape=(1,), dtype=np.float32)]

    prediction_0 = model(inputs)

    model_path = "test_model"

    model.save(model_path)

    loaded_model = keras.models.load_model(model_path)

    prediction_1 = loaded_model(inputs)

    print(prediction_1)

if __name__ == "__main__":
    main()

The above has the error TypeError: No common supertype of TensorSpec(shape=(None,), dtype=tf.float32, name=None) and TensorSpec(shape=(None,), dtype=tf.float16, name='inputs').

Unfortunately I'm not sure of a workaround in this case. The example above fails even if you remove autocast=False, in which case it looks like a fairly typical example with nested models and mixed precision. @k-w-w, can you take a look?

@reedwm @k-w-w appreciate you all looking into this.
Since we would really love to implement fp16 training, I was wondering if you could suggest any other workarounds that would allow us to save our models in a valid state after training on fp16? I don't really mind (for the moment) if inference is done in fp32 / fp16, but the input to the model ideally needs to be fp32.

This was fixed in https://github.com/keras-team/keras/commit/0b96ba57c7b3cd200ff571c56443230166f79708.

@reedwm This fix does work for the original case, but not for the nested model case (https://github.com/keras-team/keras/issues/17362#issuecomment-1378162050)
The error there is: TypeError: No common supertype of TensorSpec(shape=(None,), dtype=tf.float32, name=None) and TensorSpec(shape=(None,), dtype=tf.float16, name='inputs').
Any ideas/workarounds?


Fix typo in bio. #issue39

Thanks for your PR! This isn't a typo though. Would happily take future contributions -- I'm working on some good first issue suggestions!


docs: contributing file update

What problem does this PR solve?

Issue Number: close #435
Problem Summary
The problem solve the few grammatical errors and also typos present in the CONTRIBUTING.md file
Check List

Tests

[ ] Unit test
[ ] Integration test
[ ] Manual test (add detailed scripts or steps below)
[x] No code

Because you didnt chose a different brench I think youve added the function in this PR too


AutoRest merge checked in files with merge conflict markers

PR #29179 didn't merge cleanly and checked in files with merge conflict markers like https://github.com/Azure/azure-sdk-for-net/blame/7e4057f6a2932d31d075a28332fe7e20790f4483/sdk/cognitivelanguage/Azure.AI.Language.QuestionAnswering/src/Generated/QuestionAnsweringProjectsClient.cs#L1736.
/cc @pshao25 @annelo-msft

By grep'ing files in the commit only, this seems to have only affected one file:
sdk\cognitivelanguage\Azure.AI.Language.QuestionAnswering\src\Generated\QuestionAnsweringProjectsClient.cs:1736:<<<<<<< HEAD
sdk\cognitivelanguage\Azure.AI.Language.QuestionAnswering\src\Generated\QuestionAnsweringProjectsClient.cs:1785:<<<<<<< HEAD
sdk\cognitivelanguage\Azure.AI.Language.QuestionAnswering\src\Generated\QuestionAnsweringProjectsClient.cs:2151:<<<<<<< HEAD
sdk\cognitivelanguage\Azure.AI.Language.QuestionAnswering\src\Generated\QuestionAnsweringProjectsClient.cs:2202:<<<<<<< HEAD

I will fix this up since it's blocking.


Optimize coordinate wrappers

postfix.js has a number of wrappers to avoid errors converting coordinate arrays to structs. When the source array length is longer than expected, we slice the array to avoid an error. This approach creates unnecessary GC overhead and in quick testing incurred a ~10-15% performance penalty over a wrapper that passes the lon/lat values directly to the function (with a double lon, double lat function signature). We should investigate how these calls can be better optimized.

:tada: This issue has been resolved in version 1.2.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Proposal: Good Market

Description

Good Market is a decentralized e-commerce platform that allows users to buy and sell goods and services directly without intermediaries. Users can easily post ads, search for products by category and interact through reviews. All transactions are managed by smart contracts, ensuring transparency and safety. Cho Tot aims to create a trustworthy and efficient trading community.

Bounty track

Defi
SocialFi

hmm... can you do an ecom platform that is nextjs based (serverless deployment) with Sign In With Ethereum (connect wallet to sign into account) but accepts crypto as payment?
This is an easier approach than your proposal because you will have to work on an arbitration system for that. Plus ecom with crypto is trending right now.


Move to aperture from GDA before rotation

We should move to the correct aperture for the rotation as part of the rotation scan call in Hyperion, rather than relying on GDA to do the move.
Acceptance Criteria

GDA passes in the aperture with which to do the scan
Hyperion accepts this aperture and moves to it as part of setting up the sample environment for rotations

Add selected aperture into rotation parameters, put this in the diffraction experiment parent
Rotation plan moves the aperture as the first thing it does
Small to medium


so many op not support ,i feel heart broken,please add them ,thanks so much

hhh why I feel it is so jollying of you.... hope you can solve your problem as soon as possible

@yokings  Hello , did you solve the problem


[ 1.5.0rc2 ] : Allowing log verbosity configuration in the "elasticsearch" output.

Guys, Hi. I am testing the latest "1.5.0 rc2". I have a couple of Rabbit inputs with four threads each. The output uses the latest "elasticsearch" plugin. There is one very annoying difference between the latter and the deprecated "elasticsearch_http" plugin. Any "POST /_bulk" response with one or more records with a "status" of, for example, 400 or 429, etc..., will generate "warn" level log data corresponding to the original bulk request. In my case I can have dozens of megabytes per seconds. A configuration option controlling this behaviour would be mostly welcome. (i.e.: the Rabbit input has it by the way)
Thanks in advance.
Regards, Andrei
P.S.: transferred from https://github.com/elastic/logstash/issues/2847

Please re-submit to the correct repository:  https://github.com/logstash-plugins/logstash-output-elasticsearch

Sorry, not sure what happened. Done @ https://github.com/logstash-plugins/logstash-output-elasticsearch/issues/75 Regards, Andrei


CLiXO search fails or spins forever

Searching for CLiXO: 10651 should light up the corresponding term on the CLiXO network

The query itself works for the current branch (1.1.0), but does not return exact match.


Error/Warning counter on status bar

It would be really nice to have an error/warning counter in the status bar.
This way if the issue is not in the editor's current visible area you can still know there's something wrong.

This idea has been implemented, so closing this issue. Thanks for the suggestion!


Add TinyC grammar example.

Reference.
https://github.com/antlr/grammars-v4/blob/master/tinyc/tinyc.g4

Maybe even use that grammar as a basis for an expended tutorial for a front-end compiler
for a language service?


[FEAT] Make wash claims aware of wasmcloud.toml

Feature or Problem
Just like wash build infers information about a project from the wasmcloud.toml file, it should be a one step process to run wash claims sign to sign an existing wasm file without building.
Related Issues
#1101
Release Information
wash-cli v0.24.1
Consumer Impact
better dx
Testing
Unit Test(s)
all existing tests work as expected; refactor has no regression
Acceptance or Integration
all existing tests work as expected; refactor has no regression

hey @brooksmtownsend, you mentioned

the ability to sign using claims in a wasmcloud.toml key directory
by claims here, i assume you mean the signing nk key that is found/created in the key directory

The rest of the issue, signing with capability claims for example, can be completed as a followup or in this PR 😄
i actually didn't get this at all originally. but now that you mentioned it, it sounds like we want to be  able to set fields on ActorMetadata and ProviderMetadata based on configuration in wasmcloud.toml (ie, when the user does specify via cli args or env vars). If that is the case, can you confirm the following configuration keys of interest:

ActorMetadata => actor.claims, actor.call_alias, actor.destination, actor.tags?, version, revision, name
ProviderMetadata => provider.capability_id, provider.vendor, version, revision, name

hey @brooksmtownsend  thanks for the feedback on my last inquiry. I have two more questions that came when i resumed word on this...
should name, rev, ver become optional on ActorMetadata now that the claims command is supposed to be wasmcloud.toml aware? The awareness of the project config is, otherwise, not useful for those particular args.
In addition, should the provider flag be removed on that same struct at this point?

@ahmedtadde Great questions, I think both of your assumptions are correct when it comes to unioning the caps + tags, we can handle those cases but it would be nice to just have folks use the wasmcloud.toml file.

should name, rev, ver become optional on ActorMetadata now that the claims command is supposed to be wasmcloud.toml aware?
I think they can be optional command line arguments, but I think they are still required when it comes to signing so if they aren't supplied then a project config is required.

In addition, should the provider flag be removed on that same struct at this point?
I think so, I can't think of any reason why we should keep it


install-extension vadimcn.vscode-lldb: wrong platform aarch64 expecting x86-64

Local OS: ubuntu20.04
Remote OS: ubuntu20.04
Remote Architecture: x86_64
code-server --version: 3.8.0 c4610f7829701aadb045d450013b84491c30580d

REF: https://github.com/vadimcn/vscode-lldb/issues/402
on a fresh install with cache dir's cleared:
code-server -vvv --install-extension vadimcn.vscode-lldb

installs extension but for the wrong platform (ARM aarch64 when expecting x86_64)
s8weber@jupyter-p03:~/.local/share/code-server/extensions/vadimcn.vscode-lldb-1.6.0/adapter$ file ./codelldb
./codelldb: ELF 64-bit LSB shared object, ARM aarch64, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, BuildID[sha1]=89f52b409d1971f91b4192d84e1b624aa4e942ab, not stripped

Logs show:
[2020-12-22 15:07:24.745] [cli] [trace] Started scanning user extensions
[2020-12-22 15:07:24.745] [cli] [trace] Scanned user extensions: 0
[2020-12-22 15:07:24.745] [cli] [trace] Extension VSIX downlads cache dir does not exist
[2020-12-22 15:07:24.748] [cli] [trace] RequestService#request https://extensions.coder.com/api/extensionquery
[2020-12-22 15:07:24.836] [cli] [trace] RequestService#request https://storage.googleapis.com/vscode-extension-assets/vscode-extensions/vscode/vadimcn/vscode-lldb/1.6.0/Microsoft.VisualStudio.Code.Manifest
[2020-12-22 15:07:24.883] [cli] [trace] ExtensionManagementService.refreshReportedCache
[2020-12-22 15:07:24.883] [cli] [trace] ExtensionManagementService.refreshReportedCache - got 0 reported extensions from service
[2020-12-22 15:07:24.884] [cli] [info] Installing extension: vadimcn.vscode-lldb
[2020-12-22 15:07:24.884] [cli] [trace] Started scanning user extensions
[2020-12-22 15:07:24.884] [cli] [trace] Scanned user extensions: 0
[2020-12-22 15:07:24.884] [cli] [trace] Started downloading extension: vadimcn.vscode-lldb
[2020-12-22 15:07:24.885] [cli] [trace] ExtensionGalleryService#download vadimcn.vscode-lldb
[2020-12-22 15:07:24.885] [cli] [trace] RequestService#request https://storage.googleapis.com/vscode-extension-assets/vscode-extensions/vscode/vadimcn/vscode-lldb/1.6.0/Microsoft.VisualStudio.Services.VSIXPackage?redirect=true&install=true
[2020-12-22 15:07:26.636] [cli] [info] Downloaded extension: vadimcn.vscode-lldb undefined
[2020-12-22 15:07:26.779] [cli] [trace] Started extracting the extension from /home/s8weber/.local/share/code-server/CachedExtensionVSIXs/vadimcn.vscode-lldb-1.6.0 to /home/s8weber/.local/share/code-server/extensions/.vadimcn.vscode-lldb-1.6.0
[2020-12-22 15:07:27.067] [cli] [info] Extracted extension to /home/s8weber/.local/share/code-server/extensions/.vadimcn.vscode-lldb-1.6.0: vadimcn.vscode-lldb
[2020-12-22 15:07:27.067] [cli] [info] Renamed to /home/s8weber/.local/share/code-server/extensions/vadimcn.vscode-lldb-1.6.0
[2020-12-22 15:07:27.070] [cli] [info] Installation completed. vadimcn.vscode-lldb
[2020-12-22 15:07:27.072] [cli] [info] Extensions installed successfully: vadimcn.vscode-lldb

When manually downloading https://storage.googleapis.com/vscode-extension-assets/vscode-extensions/vscode/vadimcn/vscode-lldb/1.6.0/Microsoft.VisualStudio.Services.VSIXPackage?redirect=true&install=true I find that the package is for ARM.
I'm not sure if this is a bug in the extension manifest or platform detection that might be passed through a web request.

note:
https://storage.googleapis.com/vscode-extension-assets/vscode-extensions/vscode/vadimcn/vscode-lldb/1.6.0/Microsoft.VisualStudio.Code.Manifest
has a config > platformPackages section that seems to be ignored.. /perhaps that's normal/
config
platformPackages |
url | "https://github.com/vadimcn/vscode-lldb/releases/download/v${version}/${platformPackage}"
platforms |
x64-linux | "codelldb-x86_64-linux.vsix"
arm64-linux | "codelldb-aarch64-linux.vsix"
arm-linux | "codelldb-arm-linux.vsix"
x64-darwin | "codelldb-x86_64-darwin.vsix"
x64-win32 | "codelldb-x86_64-windows.vsix"
ia32-win32 | "codelldb-x86_64-windows.vsix"

The culprit seems to be the process code-server uses to populate its marketplace.  The FAQ says "It works by scraping GitHub for VS Code extensions and building them", however CodeLLDB's build process is rather involved, so I doubt that this works.  Instead, it probably falls back to picking .vsix packages from Releases, in which case this all makes sense, because codelldb-aarch64-linux.vsix happens to be the first one.

It is indeed because we are scraping the Releases from GitHub repos - as a stopgap, I think it would be best to download the version that corresponds to your architecture and OS and then install it via code-server --install-extension.

I think it would be best to download the version that corresponds to your architecture and OS and then install it via code-server --install-extension.

Sure, but this only works after the user has realized what the problem is.
If you want to make this smooth for your users, you need to arrange that your scraping process picks codelldb-bootstrap.vsix package (which is the one I publish to MS Marketplace).    Upon activation, it detects current platform and downloads the appropriate full package.


Update Resources docs to include test results feature

@katiealoisi are you able to tag Heather here (couldn't find her GitHub name) to provide more context? I heard she has mockups. Not sure what exactly is needed here, any detail would be helpful!

Just added @hmyers-cms to this repo: Heather, see the comment above.

maybe @katiealoisi has context to provide?

@katiealoisi texting test results has been live for some time now as far as I know.

Thx @maya. In that case, this should be included in the content clearance package for this sprint. @Rebecca-LM if you're not available to support SimpleReport work this sprint, you can assign this to me (but please link me to the latest content doc so I can make sure I'm making the updates in the correct place)

Katie, you should have the link to the latest content resources document so
feel free to add this task there. I'm working on some of the docs
related to content strategy so if you're able to take this on that'd be
great:
https://docs.google.com/document/d/1Ekr6bl5FL4SucRcIpVFjxOQ8deitWVphSoixNxUCKSk/edit?ts=60620d67
On Tue, Mar 30, 2021 at 6:34 PM Katherine Aloisi @.***>
wrote:

Thx @maya https://github.com/maya. In that case, this should be
included in the content clearance package for this sprint. @Rebecca-LM
https://github.com/Rebecca-LM if you're not available to support
SimpleReport work this sprint, you can assign this to me (but please link
me to the latest content doc so I can make sure I'm making the updates in
the correct place)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/CDCgov/prime-simplereport-site/issues/91#issuecomment-810446216,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARMQ6WXJKNEF6KGGL364KBTTGIDRXANCNFSM4Z2KGT5Q
.

any update on this @katiealoisi?

I updated the text but can't update the simplified UI screenshot. Willys created these with Snagit, which USDS does not have access to.
Also, clearance of this content should be bundled with the updates in ticket 94.

Need to figure out solution that's not Snagit

@LGFranklin Willys mentioned that Skylight would likely support us getting another Snagit account if needed, though I believe (?) it's a mobile app, so only one person can use it..


Mention {*} as ALL type for parameters

The @param page should define a {*} type representing any kind of parameter as it's done at the Closure Compiler page.
I first stumbled over this reading a stackoverflow thread.
Sebastian

Hi @hegemonic, is the page now supposed to show {*}? It doesn't seem to be on there.

Yes, it's there, under "Allows any type."


Feature: Automated Creation Based on Example for PyTorch Linear Modules with ReLU Activations

Work in progress
The PR addresses #124
Automated generation from PyTorch module class ``torch.nn.modulechild, leveragingtorchinfoarchitecture summary interface, comparable with TensorFlow/Kerassummary` method.

This is created from the following code:
# Define example module
import torch as th

class MLP(th.nn.Module):

    def __init__(self):
        super(MLP, self).__init__()
        self.net = th.nn.Sequential(
            th.nn.Linear(2, 16),
            th.nn.ReLU(),
            th.nn.Linear(16, 16),
            th.nn.ReLU(),
            th.nn.Linear(16, 1)
        )

    def forward(self, x):
        x = self.net(x)
        return x

# Parse the example module
from pycore.torchparse import TorchArchParser
from pycore.tikzeng import to_generate

mlp = MLP()
parser = TorchArchParser(torch_module=mlp, input_size=(1,2))
arch = parser.get_arch()
to_generate(arch, pathname="./test_torch_mlp.tex")

[x] Initial PyTorch support with Linear and ReLU in Sequential module structure
[x] Added interface for custom fill colors, hack of Conv for fully connected layer until a specialized function is provided.

TODOs for subsequent PRs

Variable generation with respect to PyTorch layer and Activation Functions~~
Keras support

Addressed #124 with respect to PyTorch

Please feel free to feed back and contribute to this feature.

Ready as initial functionality for PyTorch automated generation support. Please review and merge if deemed OK.

hey guys, any plan to support conv layer ?

Hey @space192 I am currently occupied to push the PR further but we happily accept your extension to CNNs.


SwingPanel doesn't change its size on window resize

Compose 0.4.0, 0.4.0-build174 (everything is ok in 0.4.0-build173)

run this code:

import androidx.compose.desktop.SwingPanel
import androidx.compose.desktop.Window
import androidx.compose.foundation.layout.fillMaxSize
import androidx.compose.ui.Modifier
import java.awt.Color
import javax.swing.JPanel

fun main() = Window {
    SwingPanel(
        factory = {
            JPanel().apply {
                background = Color.RED
            }
        },
        modifier = Modifier.fillMaxSize()
    )
}

try to resize the window

Expected: panel is resized
Actual: size of the panel doesn't change
The problem lies in Modifier.onGloballyPositioned that is used by SwingPanel. This code also works in 0.4.0-build173:
import androidx.compose.desktop.Window
import androidx.compose.foundation.layout.fillMaxSize
import androidx.compose.ui.Modifier
import androidx.compose.ui.layout.Layout
import androidx.compose.ui.layout.onGloballyPositioned

fun main() = Window {
    Layout(
        content = {},
        modifier = Modifier.fillMaxSize().onGloballyPositioned { childCoordinates ->
            val coordinates = childCoordinates.parentCoordinates!!
            val size = coordinates.size
            println("Size ${size.width}")
        },
        measurePolicy = { _, _ ->
            layout(0, 0) {}
        }
    )
}

It seems this code works:
import androidx.compose.desktop.SwingPanel
import androidx.compose.desktop.Window
import androidx.compose.foundation.background
import androidx.compose.foundation.layout.Box
import androidx.compose.foundation.layout.fillMaxSize
import androidx.compose.ui.Modifier
import java.awt.Color
import javax.swing.JPanel
fun main() = Window {
    Box(
        modifier = Modifier.fillMaxSize().background(color = androidx.compose.ui.graphics.Color.Green )
    ) {
        SwingPanel(
            factory = {
                JPanel().apply {
                    background = Color.RED
                }
            }
        )
    }
}

But doesn't work if when we add Modifier.fillMaxSize() to the SwingPanel

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


Add a tutorial to the PhysicsJS activity

Add a tutorial to the Physics activity following tutorial 9 in Sugarizer development tutorial: https://github.com/llaske/sugarizer/blob/dev/docs/tutorial_step9.md
The tutorial:

[ ] Should display a welcome message to explain the activity (could reuse the help message describing the activity in Sugarizer activities List view)
[ ] Should explain usage of each button in the toolbar
[ ] Should be localized
[ ] Should respect the Sugarizer UI, as explained in tutorial

Fixed in https://github.com/llaske/sugarizer/pull/521


Add win animation to the result

Hey man,
I suggest adding a win animation or something like a jackpot celebration to the selected technologies.
Well I'm not a frontend guy xD, I'm not sure if I can implement the idea as described but I can try to do something simple and then someone else improve it
thanks

Hello @YassineDeriouch thats a great idea! Feel free to go ahead with it


How do I use shaders

What is your question?
I have no idea how to use shaders

soft coded do not work 5.2h removed them those are leftovers

but why :(((

but why :(((

Adding shaders is a costly procedure.
Too costly for Lua...

but why :(((

Adding shaders is a costly procedure.
Too costly for Lua...

That's not why it was removed bro
It was using code from people without their consent, that's why i removed it

but why :(((

Adding shaders is a costly procedure.

Too costly for Lua...

That's not why it was removed bro
It was using code from people without their consent, that's why i removed it

Oki