Support sending "null" message to LangGraph stream

I'm trying to do pause-resume scenario with LangGraph and works very nicely but I had to tweak chatApi.ts
https://github.com/Yonom/assistant-ui/blob/main/examples/with-langgraph/lib/chatApi.ts#L44
So it would be cool to have more "native" support for it.
The trick here is that after sending an update the status of specific node sendUpdate  like this
            await updateState(threadId, {
              newState: { messages: [tool_message] },
              asNode: "humanInput",
            })

It's important to send message that "continue" the workflow from THAT node. And it's done via
    // passing null means "continue"
    const stream = await app.stream(null,  config);

It's crucial to pass "null" and not  "toolMessage with empty content".
The issue with current implementation is when I'm calling addResult(null); in my component it sends ToolMessage with content='' which sends an empty message.
So I tweaked the chatApi.ts to ignore that and send "null" to continue the workflow. Then workflow nicely continued on "humanInput" node as expected and is not going through START node.
Could you please add some better support to sending "null" into the stream?
Langgraph docs for reference: https://langchain-ai.github.io/langgraph/cloud/how-tos/human_in_the_loop_user_input/#invoking-after-receiving-human-input

@lkrzyzanek Hi
can you clarify further how you did it? I am trying to make a pull request to fix a similar problem


Specifying the --shared Flag in CLI with Package List does not Work as Expected

The following command should list only public packages, but instead shows all packages.
wsk package list --shared true

In additon, the following call should show only private packages.
wsk package list --shared false

The request from the CLI to the controller seems not to return the proper result
https://{deployment_address}/api/v1/namespaces/_/packages?limit=30&public=true&skip=0

This is explicitly disabled today.

Okay, sounds like we should hide the option from the CLI then.

https://github.com/apache/incubator-openwhisk/blob/master/tests/src/test/scala/whisk/core/controller/test/PackagesApiTests.scala#L157


double quotes for static_dataset_info key

Testing this example:
https://github.com/usegalaxy-eu/tpv-metascheduler-api/blob/6eb738166a9635a51f14793738e5bd02c644daad/main.py#L82-L113
With 0 as the key in:
    "static_dataset_info": {
        0: {
            "object_store_id": "object_store_australia",
            "size":<PHONE_NUMBER>000
        }
    }

Returns
{
  "detail": [
    {
      "type": "json_invalid",
      "loc": [
        "body",
        199
      ],
      "msg": "JSON decode error",
      "input": {},
      "ctx": {
        "error": "Expecting property name enclosed in double quotes"
      }
    }
  ]
}

After https://github.com/usegalaxy-eu/tpv-metascheduler-api/pull/19 this is no longer relevant, so closing


A way to serve static files

Meridian needs a way to serve static files like CSS and JS and images. Having surveyed the options, I think some kind of #filePath based approach is the best way to do it. (Bundled files work on mac OS but not Linux)

Fixed in 0729a4d994d. Special thanks to @grennis! Without his work on this PR this feature would have been much harder.


Deploy to Heroku button fails

Breaks on the "Build app" phase.
Full build log: https://gist.github.com/csu/6cbc830ade3bb403f5bb
Seems to be a Heroku problem though (???)

Duplicate of #716

Feel free to continue discussion in that issue.

@knownasilya Ah, thanks. Thought it was a different error because it looked like npm install was successful.

Sorry, I think it was actually #433


Enable pylint for eip7594

This fixes the typing issues in the eip7594 spec & enables pylint.
Using remerkleable types in cryptography is very slow. We might want to consider using int (instead of BLSFieldElement) in all of the internal functions. This isn't ideal either, but I don't know of a better idea.
This PR removes the PolynomialCoeff type because converting to it over-and-over was very slow. It also modifies the verify_cell_kzg_proof_batch tests so cells/proofs aren't computed multiple times unnecessarily.
I don't love the changes in this PR but it's a necessary evil.

I'm not a fan of this. I'm going to close it & work on a different solution.


Issues within the learning rate schedule and optimizer initialization

Describe the bug
There are three parameter groups defined in yolo/utils/model_utils.py/create_optimizer. One for biases, one for batch_norm weights and one for the convolutional weights. In the stable implementation, the learning rate for each of these groups is the same during training, they only differ in their weight_decay (only the conv weights have it), however, in the current implementation the bias learning rate starts hight during warmup, then quickly converges towards zero right after the warmup epochs, basically freezing the bias values after a couple of epochs! This issue stems most likely from Line 79 in yolo/utils/model_utils.py/create_optimizer:
    optimizer.max_lr = [0.1, 0, 0], where the max_lr is initialized differently for the bias parameters group.
An additional problem is, that the momentum values for the optimizer are hardcoded to be 0.8 instead of using the value found in train.yaml, which is 0.937 in the following code snippet (Lines 55-57):
        {"params": bias_params, "momentum": 0.8, "weight_decay": 0},
        {"params": conv_params, "momentum": 0.8},
        {"params": norm_params, "momentum": 0.8, "weight_decay": 0},

To Reproduce
Steps to reproduce the behavior:

Train a network with tensorboard enabled.
Observe the learning rate of the parameter groups.

Expected behavior
The bias learning rate not to converge towards zero early.
Screenshots
Learning rate schedule for the three parameter group in the current implementation:

Learning rate schedule for the same parameter groups in the "stable" implementation:

Proposed solution

Set Line 79 to     optimizer.max_lr = [0, 0, 0] for the learning rates to be identical.
Remove the fix momentum values from Line 55-57, in which case the optimizer is initialized with value provided in train.yaml

Hi
Generally, the warm-up learning rate of the bias term is 0.1 and the others are 0, they will align to 0.01 after the warm-up epoch.
This is my learning rate curve in wandb, it seems to work regularly now, can you tell me your configuration?
$python yolo/lazy.py task=train # the basic configuration

best regards,
HenryTsui

Hey,
Yes, I modified the learning rate in train.yaml to 0.001 from 0.01 for the training on the first screenshot. All else learning rate schedule related should be the same.

Hi @henrytsui000 ,
I am sorry, it is my bad. The bias learning rate indeed converged to the same value as the remaining two groups. It just looked zero like compared to the 0.1 start:

I close this issue, as it was a mistake.


Question: do i have to set labels for each container when using WUD_WATCHER_CGM1_WATCHBYDEFAULT=true

I want to have all containers monitored and updated (dockercompose)
I have a lot of containers and I do not want to set labels for each of them, only for the ones that I want to exclude
I understand that WUD_WATCHER_CGM1_WATCHBYDEFAULT=true will do that
Is this rigth ?

Hi,
Yes, it's right.
You can chose the best strategy based on your situation:

Either watching by default ALL containers but excluding some of them by setting wud.watch=false on them
Or watching by default NO containers but including some of them by setting wud.watch=true on them


Guideline needed for the insertion of a foreign pdk like gpdk45 into OpenRAM flow

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
What did you do to demonstrate the bug?
Please include your configuration file used.
Expected behavior
A clear and concise description of what you expected to happen.
Logs
If applicable, add logs or output to help explain your problem.
Additional context
Add any other context about the problem here.

Hi,
There is a section in the documentation on porting to a new technology. If you have updates to it, please submit a PR.
Matt


Missing Generic Node type in applyNodeChanges

Describe the Bug
applyNodeChanges should have generics for the Node type.
The current type definition of applyNodeChanges is:
export declare function applyNodeChanges<NodeData = any>(changes: NodeChange[], nodes: Node<NodeData>[]): Node<NodeData>[];

But this is problematic when you use it with custom nodes, with NodeData and NodeType

To fix this, we should have a type definition of applyNodeChanges like this:
export declare function applyNodeChanges<NodeData = any, NodeTypes = any>(changes: NodeChange[], nodes: Node<NodeData, NodeTypes>[]): Node<NodeData, NodeTypes>[];

Your Example Website or App
No response
Steps to Reproduce the Bug or Issue

Follow the Zustand guide
Create and use custom Nodes with a custom NodeData & NodeType with the following type definitions

type CustomNodeData = {
  name: string;
};

type WidgetType = 'port' | 'adapter';

Node<CustomNodeData, WidgetType>[];

Expected behavior
As a developer, I expect the return type of applyNodeChanges to be the same as the input nodes from the parameter so that I can have a full type-safe code.
Screenshots or Videos
Return type error with the current applyNodeChanges type definition

Fixed with the proposed type definition

Platform

OS: all
Browser: all
Version: 11.7.0

Additional context
No response

That's a good point. We will add it in the next release.

I thought about this issue again and I think that a real fix for this would be a breaking change. We could add another generic as you said like applyNodeChanges<NodeData, NodeType> but this would only help if you always use the same NodeData. If you have multiple types with different data structures like:
type CustomNodeA = Node<{ label: 'string' }, 'type-a'>;
type CustomNodeB = Node<{ number: 2 }, 'type-b'>;

you would loose the information which type belongs to which data structure. I would suggest that we wait for the next major release and change the types for applyNodeChanges like this:
function applyNodeChanges<CustomNode extends Node>(changes: NodeChange[], nodes: CustomNode[]): CustomNode[] {
  return applyChanges(changes, nodes) as CustomNode[];
}

After such a change we could define different nodes with different data structures:
type NodeA = Node<{ label: string }, 'str'>;
type NodeB = Node<{ value: number }, 'num'>;

type CustomNode = NodeA | NodeB;

and pass them to the applyNodeChanges like this:
applyNodeChanges<CustomNode>(changes, nodes))

This would be easier and more flexible. There are probably lots of other parts in the code where we could use this structure.

hey @Esequiel378 so how did you solve it in the meantime? 😅
I am facing the same issue.

Hello there! I've ended up creating an external function that returns the expected types like this
function applyNodeChangesWithTypes(changes: NodeChange[], nodes: CustomNode[]) {
  // @ts-ignore
  return applyNodeChanges(changes, nodes) as unknown as CustomNode[];
}

Oh thank you.. that's super helpful.

Hi, I'm sorry to bother if I'm by some chance missing something but the comment above that proposes the solution seems to already be what's going on in the main branch of the project at the current  time I'm commenting this:

...
you would loose the information which type belongs to which data structure. I would suggest that we wait for the next major release and change the types for applyNodeChanges like this:
function applyNodeChanges<CustomNode extends Node>(changes: NodeChange[], nodes: CustomNode[]): CustomNode[] {
  return applyChanges(changes, nodes) as CustomNode[];
}

Current MAIN branch
https://github.com/xyflow/xyflow/blob/14c4f6512465425ad3c977cc88b45705631fa7d3/packages/react/src/utils/changes.ts#L191-L193
The only piece of the puzzle I believe is to pass down the generic into the NodeChange event and I believe I fixed it in this PR without adding a breaking change

https://github.com/xyflow/xyflow/pull/3791

I'm pretty sure the way this issue is framed is outdated but the problem still exists 🙂

Fixed in React Flow 12! If you are using 11, you can find the migration guide here: https://reactflow.dev/learn/troubleshooting/migrate-to-v12


Update to 1.5beta3 upstream release

cc @paultag

Still need to figure out what to do with the monstrous debian/copyright, as mwhudson pointed out.  Will be looking at the Ubuntu diff now.

Ok, copyright is updated now, too! (mostly from https://patches.ubuntu.com/g/golang/golang_2:1.4.2-3ubuntu2.patch / http://changelogs.ubuntu.com/changelogs/pool/universe/g/golang/golang_1.4.2-3ubuntu2/copyright)

root@01f9a46e4f31:/usr/src/golang# dpkg --unpack --auto-deconfigure ../*.deb
(Reading database ... 30249 files and directories currently installed.)
Preparing to unpack .../golang-doc_1.5~beta3-1_all.deb ...
Unpacking golang-doc (2:1.5~beta3-1) over (2:1.4.2-3) ...
Preparing to unpack .../golang-go_1.5~beta3-1_amd64.deb ...
Unpacking golang-go (2:1.5~beta3-1) over (2:1.4.2-3) ...
Selecting previously unselected package golang-pkg.
dpkg: considering deconfiguration of golang-go-linux-amd64, which would be broken by installation of golang-pkg ...
dpkg: yes, will deconfigure golang-go-linux-amd64 (broken by golang-pkg)
Preparing to unpack .../golang-pkg_1.5~beta3-1_amd64.deb ...
De-configuring golang-go-linux-amd64 (2:1.4.2-3) ...
Unpacking golang-pkg (2:1.5~beta3-1) ...
Replacing files in old package golang-go-linux-amd64 (2:1.4.2-3) ...
Preparing to unpack .../golang-src_1.5~beta3-1_amd64.deb ...
Unpacking golang-src (2:1.5~beta3-1) over (2:1.4.2-3) ...
Preparing to unpack ../golang_1.5~beta3-1_all.deb ...
Unpacking golang (2:1.5~beta3-1) over (2:1.4.2-3) ...
Processing triggers for man-db (<IP_ADDRESS>-5) ...
root@01f9a46e4f31:/usr/src/golang# apt-get install -f
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following packages will be REMOVED:
   golang-go-linux-amd64 (1.4.2-3)
0 upgraded, 0 newly installed, 1 to remove and 34 not upgraded.
6 not fully installed or removed.
After this operation, 79.8 MB disk space will be freed.
Do you want to continue? [Y/n]
(Reading database ... 30823 files and directories currently installed.)
Removing golang-go-linux-amd64 (2:1.4.2-3) ...
Setting up golang-src (2:1.5~beta3-1) ...
Setting up golang-pkg (2:1.5~beta3-1) ...
Setting up golang-go (2:1.5~beta3-1) ...
debconf: unable to initialize frontend: Dialog
debconf: (No usable dialog-like program is installed, so the dialog based frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 76.)
debconf: falling back to frontend: Readline
Setting up golang-doc (2:1.5~beta3-1) ...
Setting up golang (2:1.5~beta3-1) ...
root@01f9a46e4f31:/usr/src/golang# export GOPATH=/go
root@01f9a46e4f31:/usr/src/golang# go get -v github.com/tianon/rawdns/src/cmd/rawdns
github.com/tianon/rawdns (download)
github.com/miekg/dns (download)
github.com/miekg/dns
github.com/tianon/rawdns/src/cmd/rawdns
root@01f9a46e4f31:/usr/src/golang# /go/bin/rawdns
2015/07/30 04:31:22 rawdns v1.2 (go1.5beta3 on linux/amd64; gc)
2015/07/30 04:31:22 error: unable to read config file example-config.json: open example-config.json: no such file or directory
root@01f9a46e4f31:/usr/src/golang# go version
go version go1.5beta3 linux/amd64

Ok, the only change left I haven't made is consolidating all three golang-* binary packages into a single golang binary package, because I wasn't sure whether it was worth introducing golang-pkg first and consolidating in an update, or whether we should go all-in-one right away and rip the band-aid off (probably leaving golang-doc and golang-go as installable virtuals for a while).

I've pushed 590c329 which is a first pass at consolidating these down into just golang-go and golang-doc.  I do wonder whether any of the binaries that used to be in golang-go can be used without the compiled stdlib though -- I'm pretty sure at least gofmt is reasonably independent, but I'm not sure what the demand for that separately might be.

I've just found a package -- direnv -- that build-deps on golang-src (for god knows what reason), with confusing results (it installed the 1.4 golang-src). I think either we should provide a dummy golang-src package or conflicts/replaces/whatever golang-src so at least this blows up in a more predictable way.

Ok, that makes me think I've gone too far and missed something, so I'm in the process of putting back golang-src, but plan to leave the compiled bits in golang-go.  Easy enough to change that stuff later on if it turns out to be something we can reasonably do. :+1:

Updated with more of the fixes discussed.


Is there a way to balance the processing of the argument with the "--version" option?

Is there a way to balance the processing of the argument with the "--version" option?
Here is my sample code. This command is simple echo, prints argument and prints version number if --version flag is applied.
import ArgumentParser

struct MyEcho: ParsableCommand {

    @Flag(name: .shortAndLong)
    var version: Bool

    @Argument()
    var text: String

    func run() {
        if version {
            print("v1.0.0")
            return
        }

        print(text)
    }
}

MyEcho.main()

However this sample code does not work well when you run myEcho --version because default validation by parser detects no argument. Like this
% myEcho --version
Error: Missing expected argument '<text>'
Usage: my-echo <text> [--version]

If I change var text: String property as optional, then myEcho --version works well but I have to handle a situation that no argument applied.
Here is my current solution bellow. Is there a better way to handle this situation?
struct MyEcho: ParsableCommand {

    @Flag(name: .shortAndLong)
    var version: Bool

    @Argument()
    var text: String?

    func run() throws {
        if version {
            print("ver 1.0.0")
            return
        }

        guard let text = text else {
            throw ValidationError("need argument")
        }

        print(text)
    }
}

Related to version, it would be cool if --version came out of the box like help does. :)

@alexito4
Yes! I really would like to have that support.

I think we probably should support --version directly. Here's a workaround until then:
struct Command: ParsableCommand {
    struct Version: ParsableArguments {
        @Flag() var version: Bool
        func validate() throws {
            if version { throw CleanExit.message("1.0.0") }
        }
    }

    @OptionGroup() var version: Version
    // ...
}

Thank you @natecook1000 I'll give it a try!

@natecook1000
I tried your workaround and it works great! Thank you. However, I have come across a slightly mysterious behavior.
This code bellow prints Error: Missing expected argument '<text>' when I run myEcho -v
struct MyEcho: ParsableCommand {

    struct Version: ParsableArguments {
        @Flag(name: .shortAndLong) var version: Bool
        func validate() throws {
            if version { throw CleanExit.message("3.0.0") }
        }
    }

    struct Options: ParsableArguments {
        @OptionGroup()
        var version: Version

        @Argument()
        var text: String

        var url = URL(string: "https://apple.com")

        enum CodingKeys: String, CodingKey {
            case text
            case version
        }
    }

    @OptionGroup()
    var option: Options

    func run() throws {
        let text = option.text

        print(text)
    }
}

MyEcho.main()

When I fix CodingKeys declarations and struct's property declarations in the same order, then no longer cause problems.
Do I need to keep them in the same order?


Option to disable on mobile device

Add an option to disable the plugin on mobile devices.

In order to keep the package as small as possible with no dependencies, this feature won't be implemented.

For those who want to init the library based on device detection, I recommend use of https://github.com/lancedikson/bowser.


Fix url path of audio and video files to resolve streamlit cloud errors

Description
The file path used to access both the video and audio files were updated to  the root file paths of the current system accessed via the os library.
Testing
The web application was deployed on streamlit to ensure both files can be accessed.
Reviewers
@wsedor

@markowusu can you also test the local setup to make sure that also works?


Add David. Watching your node.js dependencies.

https://david-dm.org/calebmer/postgraphql

@calebmer You can also integrate https://greenkeeper.io/ to automatically test new if tests pass with new dependencies :-)

Yeah, I'd rather do Greenkeeper because it will send a notification in the form of a PR 😊
As for tests, it should just run the Travis setup which will work.

Enabled Greenkeeper, see #105. Thanks :+1:

You can have both, greenkeper and David for badges, it is good combination.. ;-)

You'll note that I also don't have the Travis build status button, that's because I really don't want someone's first impression to be "build failing" and/or "dependencies out of date" 😊
I definitely want to know when these things are breaking/outdated, but I consider part of the READMEs job is to be marketing material (especially because we don't have a site yet…).
I may reconsider once we put up a docs site.


Changing Push Message Type to TEXT instead of VARCHAR

The type VARCHAR that is used in database for sending push messages is not good because it does not support unicode characters and users cannot send messages in some languages to their clients. (For example: Arabic, Persian, Urdu, etc)
The options are using NVARCHAR, TEXT and LONGTEXT.
I changed the database column type to LONGTEXT since I am sending push messages to different users that are found from my own database from multiple queries with a complicated logic.
One of my push messages contained almost 40 million characters, including more than 20k user device tokens.
I also changed hibernate settings to let the database exceed the limit of 4500 characters.
After doing the changes, it both supports unicode characters and long texts.

Hi, @sinarz
the Travis CI job failed:
Results :

Tests in error:
   Â» DatabaseCreatorFailure DDL execution failed. DB URL: 'jdbc:derby:memory:tes...

@matzew, trying to figure out why it has an error and fix this...

@matzew
I don't know what is wrong with this file:
2015-07-08-normalize-push-message-information.xml
I changed it to the version it was before i made any changes and it still gives Travis-CI Check Failed error.

ok, thanks for looking at it.
After my vacation, I'll take a look here too!
On Wed, Mar 30, 2016 at 1:35 PM, sinarz<EMAIL_ADDRESS>wrote:

@matzew https://github.com/matzew
I don't know what is wrong with this file:
2015-07-08-normalize-push-message-information.xml
I changed it to the version it was before i made any changes and it still
gives Travis-CI Check Failed error.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/aerogear/aerogear-unifiedpush-server/pull/702#issuecomment-203389809

--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf

@matzew thank you for the link you provided.
I checked the code and changed LONGTEXT to CLOB but Travis-CI build failed again.
I tried and changed it to VARCHAR(4500) and got a Travs CI build failed error too. Don't really get what is wrong with this. I'm trying to make it right in my forked repository and update it here when its working correctly.

closing as suggested. @sinarz feel free to submit one, when you got it working


Add CA and LA indicators

CA indicators
County metrics

[x] Daily number of deaths, past 7-day average (Target: 7-day average number of deaths has not increased over the past 14 days)
[ ] Daily number of deaths, past 7-day average by Race/Ethnicity (Target: 7-day average number of deaths has not increased over the past 14 days)
[ ] Daily number of deaths, past 7-day average by Area Poverty (Target: 7-day average number of deaths has not increased over the past 14 days)
[ ] Daily number of hospitalized COVID-19 patients, past 3-day average (Target: the 3-day average number of hospitalized patients has not increased over the past 14 days.)
[x] Daily number of available ICU beds, past 3-day average (Target: past 3-day average number of available ICU beds has not decreased over the past 14 days AND accounts for at least 10% of total ICU bed capacity)
[x] Daily number of available ventilators, past 3-day average (Target: past 3-day average number of available ventilators has not decreased over the past 14 days AND accounts for at least 20% of total ventilator capacity)
[ ] Percentage of hospitals that have 15+ days of available PPE, including N95 masks, other masks, eye protection, face shields, gloves, and gowns (Target: at least 60% of hospitals have 15+ days of available PPE)
[x] Daily Reported Number of COVID-19 Diagnostic Tests, Past 7 day Average (Target: an average of at least 15,000 tests (equal to 1.5 tests per 1,000 residents) have been done each day over the past 7 days)
[ ] Percentage of COVID-19 cases that have follow-up investigation initiated within 1 day of assignment (Target: at least 90% of COVID-19 cases have had follow-up investigation initiated within 1 day of assignment)

LA sets the following as benchmarks that we don't use in our report for hospital capacity:

ventilators (20%)
ICU (10%)
Right now, we use 30% as threshold for all hospital equipment. Need to think about whether we want 3 different thresholds on our chart. Concern is that 10% is a very low bar...we've been hovering around there for past couple months. If we already have 10% ICU beds available, then if we're thinking about adapting for possible surge as we reopen, we need to a higher % available.

Adding new hospital chart: acute beds, ICU beds, and ventilators used by COVID-occupied and COVID-under investigation patients in #17

Adding new hospitalizations chart with CA benchmark: stable hospitalizations of COVID individuals on a 7-day average of daily percent change of less than 5% OR no more than 20 COVID hospitalizations on any single day in the past 14 days in #18


Exclude directories from external resources to be compatible with Elixir 1.15

Elixir 1.15 handles external resources differently:
https://github.com/elixir-lang/elixir/blob/v1.15.0/CHANGELOG.md#mix
[mix compile] Track digests of @external_resources
It will try to read the file content and compute a digest to know if the file should be recompiled. https://github.com/elixir-lang/elixir/blob/96996cef7dbdbb5daa8c8009d1e51582d4c4023e/lib/mix/lib/mix/compilers/elixir.ex#L445C1-L445C1
Because rustler includes directories in the @external_resources module attribute, trying to recompile after a first compilation will fail with this error:
** (File.Error) could not read file "native/name_of_project/src": illegal operation on a directory
    (elixir 1.15.0) lib/file.ex:358: File.read!/1
    (mix 1.15.0) lib/mix/compilers/elixir.ex:441: Mix.Compilers.Elixir.digest_file!/1
    (mix 1.15.0) lib/mix/compilers/elixir.ex:426: Mix.Compilers.Elixir.stale_external?/3
    (elixir 1.15.0) lib/enum.ex:4190: Enum.predicate_list/3
    (mix 1.15.0) lib/mix/compilers/elixir.ex:394: anonymous fn/6 in Mix.Compilers.Elixir.compiler_info_from_updated/9
    (elixir 1.15.0) lib/enum.ex:2510: Enum."-reduce/3-lists^foldl/2-0-"/3
    (mix 1.15.0) lib/mix/compilers/elixir.ex:385: Mix.Compilers.Elixir.compiler_info_from_updated/9
    (mix 1.15.0) lib/mix/compilers/elixir.ex:134: Mix.Compilers.Elixir.compile/7

Note that we also have a fix for this in Elixir but I also recommend merging this. :)


Fishious Rend

Dracovishs new move Fishious rend seems to have an error where NPC battles swaps out a poke it fails instead of actually hitting (double damage).  Seems to work fine in regular player battles as tk and i were going through Anniversary Surprise where we saw it fail multiple times.

Mind testing this in a Singleplayer world? If you can replicate it in a singleplayer will mean it is a Pixelmon issue rather than server side, at that point will need to make a ticket on the Pixelmon bug tracker

Seems to be a pixelmon issue just tested it in singleplayer.

Please report directly to https://www.pixelmonmod.com/tracker.php?p=2, since this is a mod's issue.


What about Symfony 4 and Mysql?

Upgrade to the Symfony 4 is planned in the near future. Using MySQL is not planned.

Its bad


Adjust or redesign genre navigation bar

Make sure all genre names are in one single line side by side.

@QAZIMAAZARSHAD  i'll would like to work on this issue

I will assign you this issue when the contribution period starts then you can start working on this issue.

Is this alright or You want some other changes?

This is almost similar, I don't see any change.
I want all genre names in one single line, so it looks nice.
Like Home, Movies, Web Series, Kids, navigation bar. See these in one line.

But comedy is now in one line along with others @QAZIMAAZARSHAD

I'll try to make Suspense & Thriller and SciFy & Fantasy in one line as well

yes

Is this fine now @QAZIMAAZARSHAD ?

Yes, nice
But do not make any pull requests now because points will be awarded only for pull requests merged during the contribution period which is starting from 10th June.
Also while making the pull requests don't forget to mention the issue number.

But when we are hovering over it ,then it appears like this. Is it okay?

You can improve this issue, there is plenty of time.

Should i create a new issue for that?

No, since your improvement has not been accepted yet
You can improve your design.

okk thanks @QAZIMAAZARSHAD sir

Now hovering problem is solved as well @QAZIMAAZARSHAD

But I have changed the Font size of text. Is is a Problem for you sir?

It's better than before. Nice!
You can always try to improve.

Thanks @QAZIMAAZARSHAD

Should i create a PR now?

No,
After 10th June when I will assign you this issue.
In any open-source event don't make PR's directly if you are not assigned. You might not gain points for your work.

Okk thanks a lot @QAZIMAAZARSHAD sir

Can I also work upon this issue?

@rucha0702 I think @Sourav61 has already resolved this issue.
When I will merge @Sourav61's PR and if any error or scope of improvement will be there I will assign you this issue.

okay

I would like to work on this issue

I would like to work on this issue

Already solved.


Grid header, toolbar, footer always show in Chrome version Version 58.0.3029.110 (64-bit)

/* w2ui 1.5.x (nightly) (c) http://w2ui.com<EMAIL_ADDRESS>*/
This version incorrectly always shows the header, footer and toolbar by default and also if configured as false in the grid component in Chrome Version 58.0.3029.110 (64-bit).
It is okay in Edge, and Firefox.
Jim Dale

I can not reproduce the problem.
http://jsfiddle.net/ybu890ot/
The grid in this fiddle only shows the column headers and the empty rows, nothing else.
JS used in fiddle: http://rawgit.com/vitmalina/w2ui/master/dist/w2ui.min.js

/* w2ui 1.5.x (nightly) (c) http://w2ui.com<EMAIL_ADDRESS>*/

Chrome Portable, Version 58.0.3029.110 (64-bit)
Fiddle based on: http://w2ui.com/web/demos/#!grid/grid-1

@mpf82 GitHub has now https://github.com/blog/2111-issue-and-pull-request-templates
Maybe someone with admin rights to this repo should configure it, so that users are requested to provide a jsfiddle or at least an online link of the problem?

@aadrian agreed. Btw, I like the template used by CherryPy - ofc it would have to be adapted to the needs of w2ui.
Let's hope @vitmalina and/or @mrg2001  read this and find the time to set it up =)

Created template, see if you like it.

Created template, see if you like it.

Nice.

Created template, see if you like it.

Looks good, but maybe you could add the link to the w2ui related Stack Overflow questions in the top block. https://stackoverflow.com/questions/tagged/w2ui

Hi Mike,
Chrome on the left, Firefox on the right.
Running http://localhost/w2ui-master/demos/#!grid/grid-4 from your
latest download on Apache server, Windows 10.
Same result for grid1 demo.
[image: Inline image 1]
Jim
*“Success is a function of persistence and doggedness and the willingness
to work hard for 22 minutes to make sense of something that most people
would give up on after 30 seconds.”  *
Outliers Quote by Malcome Gladwell
On Tue, May 23, 2017 at 6:17 PM, Mike<EMAIL_ADDRESS>wrote:

I can not reproduce the problem.
http://jsfiddle.net/ybu890ot/
The grid in this fiddle only shows the column headers and the empty rows,
nothing else.
JS used in fiddle: http://rawgit.com/vitmalina/
w2ui/master/dist/w2ui.min.js
/* w2ui 1.5.x (nightly) (c) http://w2ui.com<EMAIL_ADDRESS>*/
Chrome Portable, Version 58.0.3029.110 (64-bit)
Fiddle based on: http://w2ui.com/web/demos/#!grid/grid-1
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/vitmalina/w2ui/issues/1602#issuecomment-303367428,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AM3xp9V7vbDDQQGOW6iRZbmBIZtCCUz-ks5r8sBXgaJpZM4NjZTJ
.

Hi Jim,
your screenshot does not show.
Anyway, it's hard to fix if it can not be reproduced. I even tried the same Chrome version you specified.
If you do not set grid.show.footer = true, the HTML code for the footer should not even be generated (no matter which browser you use).
For your local w2ui files, you could search for this code block:
        // -- footer
        if (this.show.footer) {
            $('#grid_'+ this.name +'_footer').html(this.getFooterHTML()).show();
        } else {
            $('#grid_'+ this.name +'_footer').hide();
        }

and debug it (either with an actual JS debugger or by using console.log()) to see which part of the if block gets executed.
Cheers =)

Thanks Mike,
I will debug.
I am enjoying the size of your library. I am currently using jqWidgets and
they are getting very bloated so I am ready to move to w2ui.
Jim
*“Success is a function of persistence and doggedness and the willingness
to work hard for 22 minutes to make sense of something that most people
would give up on after 30 seconds.”  *
Outliers Quote by Malcome Gladwell
On Wed, May 24, 2017 at 1:34 PM, Mike<EMAIL_ADDRESS>wrote:

Hi Jim,
your screenshot does not show.
Anyway, it's hard to fix if it can not be reproduced. I even tried the
same Chrome version you specified.
If you do not set grid.show.footer = true, the HTML code for the footer
should not even be generated (no matter which browser you use).
For your local w2ui files, you could search for this code block:
    // -- footer
    if (this.show.footer) {
        $('#grid_'+ this.name +'_footer').html(this.getFooterHTML()).show();
    } else {
        $('#grid_'+ this.name +'_footer').hide();
    }

and debug it (either with an actual JS debugger or by using console.log())
to see which part of the if block gets executed.
Cheers =)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/vitmalina/w2ui/issues/1602#issuecomment-303631067,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AM3xp_NZupxsM7K809gyHWRRKn3mncN7ks5r8895gaJpZM4NjZTJ
.

Hi Mike,
Debug results:
I inserted:
        // -- footer
        if (this.show.footer) {
            console.log('footer status',this.show.footer);
            $('#grid_'+ this.name

+'footer').html(this.getFooterHTML()).show();
} else {
console.log('footer status',this.show.footer);
$('#grid'+ this.name +'_footer').hide();
}
I tried it in Chrome, Edge, and Opera.  Opera and Edge ok but chrome fires
the footer code twice whereas Edge and Opera fire it once.  Puzzled? Any
thoughts?
If I execute:
w2ui['grid'].show.toolbar = false;
w2ui['grid'].refresh();
from the console, the toolbar disappears from Chrome.
Chrome:
[image: Inline image 1]
Edge:
[image: Inline image 2]
Opera:
[image: Inline image 3]
Source:

W2UI Demo: grid-4

Jim
*“Success is a function of persistence and doggedness and the willingness
to work hard for 22 minutes to make sense of something that most people
would give up on after 30 seconds.”  *
Outliers Quote by Malcome Gladwell
On Wed, May 24, 2017 at 1:34 PM, Mike<EMAIL_ADDRESS>wrote:

Hi Jim,
your screenshot does not show.
Anyway, it's hard to fix if it can not be reproduced. I even tried the
same Chrome version you specified.
If you do not set grid.show.footer = true, the HTML code for the footer
should not even be generated (no matter which browser you use).
For your local w2ui files, you could search for this code block:
    // -- footer
    if (this.show.footer) {
        $('#grid_'+ this.name +'_footer').html(this.getFooterHTML()).show();
    } else {
        $('#grid_'+ this.name +'_footer').hide();
    }

and debug it (either with an actual JS debugger or by using console.log())
to see which part of the if block gets executed.
Cheers =)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/vitmalina/w2ui/issues/1602#issuecomment-303631067,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AM3xp_NZupxsM7K809gyHWRRKn3mncN7ks5r8895gaJpZM4NjZTJ
.

Hi Mike,
Further debugging of elements shows that:
style="display: none;"
does not get set in Chrome for some reason.
Chrome:
[image: Inline image 1]
Opera:
[image: Inline image 2]
Jim
*“Success is a function of persistence and doggedness and the willingness
to work hard for 22 minutes to make sense of something that most people
would give up on after 30 seconds.”  *
Outliers Quote by Malcome Gladwell
On Wed, May 24, 2017 at 3:32 PM, Jim Dale<EMAIL_ADDRESS>wrote:

Thanks Mike,
I will debug.
I am enjoying the size of your library. I am currently using jqWidgets and
they are getting very bloated so I am ready to move to w2ui.
Jim
*“Success is a function of persistence and doggedness and the willingness
to work hard for 22 minutes to make sense of something that most people
would give up on after 30 seconds.”  *
Outliers Quote by Malcome Gladwell
On Wed, May 24, 2017 at 1:34 PM, Mike<EMAIL_ADDRESS>wrote:

Hi Jim,
your screenshot does not show.
Anyway, it's hard to fix if it can not be reproduced. I even tried the
same Chrome version you specified.
If you do not set grid.show.footer = true, the HTML code for the footer
should not even be generated (no matter which browser you use).
For your local w2ui files, you could search for this code block:
    // -- footer
    if (this.show.footer) {
        $('#grid_'+ this.name +'_footer').html(this.getFooterHTML()).show();
    } else {
        $('#grid_'+ this.name +'_footer').hide();
    }

and debug it (either with an actual JS debugger or by using console.log())
to see which part of the if block gets executed.
Cheers =)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/vitmalina/w2ui/issues/1602#issuecomment-303631067,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AM3xp_NZupxsM7K809gyHWRRKn3mncN7ks5r8895gaJpZM4NjZTJ
.

Hi Jim,

I am enjoying the size of your library.

It's not my library, I'm just a contributor, but I'm sure @vitmalina is reading this too and appreciates it.

Debug results:
...

Again, your screenshots do not appear on the github page.

Any thoughts?

No, because I can not reproduce it with my Chrome Portable in the exact same version.

but chrome fires the footer code twice

Since I can not see your screenshots ... is the code (console.log('footer status',this.show.footer); logging once with false and next time with true?

style="display: none;"  does not get set in Chrome for some reason.

That could be the case if refresh is called with different values of this.show.footer (well, if the last value is true, that is)

If I execute: w2ui['grid'].show.toolbar = false; w2ui['grid'].refresh(); from the console, the toolbar disappears from Chrome.

At least in this case, the grid works as expected.

Source:
...

You should really create a jsfiddle instead or update an existing fiddle - this will allow other users to easily execute the same code.
Conclusion: I'm not sure anyone can help right now, until the problem can be reproduced.
Cheers =)

Hi Mike,
Just wanted to let you know I have discovered what the problem is:
I uploaded the grid1 sample to my server that runs IIS and it executes
correctly with no toolbar, in Chrome.
This was only a problem with Apache and Chrome.
I looked at the network activity for both servers and IIS loads the w2ui.js
and css files once, whereas
on the apache server with Chrome they get loaded twice, which is causing
the problem somehow.
I checked the internet and this issue with Chrome loading files from apache
twice is very common:
https://bugs.chromium.org/p/chromium/issues/detail?id=64810
https://bugs.chromium.org/p/chromium/issues/detail?id=64810
So the good news is no problem with w2ui, but if you are developing using
Chrome and Apache then you best use some other browser or you may end up
chasing phantom bugs in your app and/or libraries.
Jim
*“Success is a function of persistence and doggedness and the willingness
to work hard for 22 minutes to make sense of something that most people
would give up on after 30 seconds.”  *
Outliers Quote by Malcome Gladwell
On Wed, May 24, 2017 at 7:49 PM, Mike<EMAIL_ADDRESS>wrote:

Hi Jim,
I am enjoying the size of your library.
It's not my library, I'm just a contributor, but I'm sure @vitmalina
https://github.com/vitmalina is reading this too and appreciates it.
Debug results:
...
Again, your screenshots do not appear on the github page.
Any thoughts?
No, because I can not reproduce it with my Chrome Portable in the exact
same version.
but chrome fires the footer code twice
Since I can not see your screenshots ... is the code (console.log('footer
status',this.show.footer); logging once with false and next time with true
?
style="display: none;" does not get set in Chrome for some reason.
That could be the case if refresh is called with different values of
this.show.footer (well, if the last value is true, that is)
If I execute: w2ui['grid'].show.toolbar = false; w2ui['grid'].refresh();
from the console, the toolbar disappears from Chrome.
At least in this case, the grid works as expected.
Source:
...
You should really create a jsfiddle instead or update an existing fiddle -
this will allow other users to easily execute the same code.
Conclusion: I'm not sure anyone can help right now, until the problem can
be reproduced.
Cheers =)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/vitmalina/w2ui/issues/1602#issuecomment-303713604,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AM3xp3zE0XyIrUM0ulWt03-92SwtvetMks5r9CdagaJpZM4NjZTJ
.

Well, since @JimmyDale mentioned it is "no problem with w2ui", I am closing this issue.


Just wanted to say that this project is awesome

Lots of apps can benefit from this type of WASM solution as opposed to bundling a full build of ffmpeg client-side or (even more work) adding to an async task queue for backend rendering.
Great job, Matt -- feel free to close this issue 😄

Also, are you sure you want to publish your build/ artifacts to GitHub?

Thanks!


[Doc] Proofreading documentation

This PR addresses issues with grammar, punctuation, sentence styling and formatting found in .rst and .md articles.

Hi @sgolebiewski-intel, thank you for the PR. currently it is hard to distinguish the changes that are changing the grammar/style vs breaking up sentences into multiple line in markdown. Is it possible to update this PR to only about the content change?

Hi @sgolebiewski-intel, thank you for the PR. currently it is hard to distinguish the changes that are changing the grammar/style vs breaking up sentences into multiple line in markdown. Is it possible to update this PR to only about the content change?

Sure, I will revert the line breaks.

I got rid of additional line breaks.

/ready

Please see the failed documentation build at https://buildkite.com/vllm/ci-aws/builds/7975#0191b133-34dd-4462-bcd4-6d19d79ebbc9

Please see the failed documentation build at https://buildkite.com/vllm/ci-aws/builds/7975#0191b133-34dd-4462-bcd4-6d19d79ebbc9

@simon-mo I have provided the fix. Thank you.

@sgolebiewski-intel this PR now has conflicts that will have to be resolved.
I suspect you'll have an easier time getting these changes in if you submit it in smaller chunks.


[Doc] - Document Limitation in 1.13

"Documentation and calls-to-action (aka: link to get a trial enterprise key)
for the parallelism and pipeline limits would certainly be good to add to the documentation
(both in those respective fields as a “note” and also in the enterprise docs."

The limitation of the total number of pipelines and the total number of workers per pipeline run in the Community Edition  should be documented as follow:
1-  Add a full page explaining what those limitations are and what happens when they are crossed. Possibly add a mention of how they came to be although this part might belong elsewhere than in the technical documentation.(Still need to be validated)
2- Add a Troubleshooting section with both error messages mentioned. In the case where either/both limits are exceeded by a user, she/he should be able to easily search all or part of the error message and land on this page. The page will explain what to do and refer to:
- the page allowing to generate tokens
- the general explanation of those limitations (see item 1)
3- Additionally, the page listing the various ways to request an enterprise token should be updated to highlight a third way to obtain those tokens (Web Form). Add a deprecation notice next to the CLI and Dash options.


Where For Dinner supports TLS in redis connections with legacy spring cloud binding.

Where For Dinner search-proc service can use redis as a cache, however it does not support TLS connections when using legacy spring-cloud-binding.  This enhancement will add a default "false" value for TLS and will support enabling TLS using spring-cloud-binding.  The need for explicitly setting TLS has been noticed mainly in managed Redis implementation (such as AWS Elasticache)

Addressed in PR #266


Bundler/OrderedGems autocorrection doesn't move inline comments

Expected behavior
When the Bundler/OrderedGems moves gems between lines of a Gemfile, their inline comments should move with them
Actual behavior
The gem declaration moves, but the comments stay on the same line, which means that comments no longer match up with the lines they were intended for.
Steps to reproduce the problem
Create a simple Gemfile
gem 'rubocop', github: 'bbatsov/rubocop' # The good stuff
gem 'bundler'

Run rubocop
$ rubocop -a Gemfile
Inspecting 1 file
C

Offenses:

Gemfile:2:1: C: [Corrected] Gem bundler should appear before rubocop in their gem group.
gem 'bundler'
^^^^^^^^^^^^^

1 file inspected, 1 offense detected, 1 offense corrected

Note the new Gemfile
gem 'bundler' # The good stuff
gem 'rubocop', github: 'bbatsov/rubocop'

RuboCop version
$ rubocop -V
0.46.0 (using Parser <IP_ADDRESS>, running on ruby 2.3.3 x86_64-darwin16)

cc @pocke

Hi, thanks for your feedback.
I'll fix this problem.


E688 more targets than list items ;rJ Up to date rtags, vim-rtags, and vim (8.1)

Seems like this was a previous issue that was solved. Unclear why I'm seeing it again. I'm trying to get this set up for the first time.
Thanks for the help,
Rob
previous issue: https://github.com/lyuts/vim-rtags/issues/79
I checked that the suggested code change had been applied.
I also checked that my rc works properly. I can use it to follow-location accurately.
The error when I do ;rJ
"Error deteched while processing function 42[1]..rtags#HandleResults[11]..rtags#Excutehandlers[6]..rtags#JumpToHandler
E688: More targets than ListItems
E121: Undefined variable: jump_file
E116: Invalid argument for function rtags#jumpToLocation(jump_file, lnmu, col)
Rtags:
$ git log
commit 6289e66a69d0d5ff20b12da91e735d3984ad6f88
Merge: a174058 68c0d1e
Author: Christian Schwarzgruber<EMAIL_ADDRESS>Date:   Sat Aug 24 16:11:44 2019 +0200
Merge pull request #1338 from Krzmbrzl/patch-1

Improve error message

vim rtags:
$ git log
commit 3ef48de532c2e875f0fc3c33b34befed2bf37016
Merge: b6629a4 00340be
Author: lyuts<EMAIL_ADDRESS>Date:   Sun Jul 22 17:55:50 2018 -0700
Merge pull request #107 from flackr/show-hierarchy

Add <Leader>rh command to show class hierarchy

vim is at 8.1
$ vim --version
VIM - Vi IMproved 8.1 (2018 May 18, compiled Jul 26 2019 08:43:04)
Included patches: 1-1749
Compiled by wlee@ld-dbn-crcvt003
Huge version with GTK2 GUI.   There appears to be some issue connecting to the server.

echo results
['Can''t seem to connect to server (/run/user/7589/rdm.socket)']

line 1: let results = a:results
line 2: let open_opt = a:args['open_opt']
line 3: if len(results) >= 0 && open_opt != g:SAME_WINDOW
line 5: endif
line 7: if len(results) > 1
line 9: elseif len(results) == 1
line 10: let [location; symbol_detail] = split(results[0], '\s+')
line 11: let [jump_file, lnum, col; rest] = split(location, ':')

echo results
['Can''t seem to connect to server (/run/user/7589/rdm.socket)']

okay it seems like I have to run vim in the same bash as the rdm process is running.

Maybe not the same bash ?  But same user ??  I can run from a different bach ok.


Tabs Don't Highlight if error caused during ionViewDidLoad

Ionic version:  (check one with "x")
[ ] 1.x
[ ] 2.x
[x] 3.x
I'm submitting a ...  (check one with "x")
[x] bug report
[ ] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:
If you have a page with a bound ngFor and in that ngFor is an invalid binding to another item, pushing the tabs page as root causes tabs to not highlight but still work.  There is also no error in the console. This only happens if the for binding is populated in the ionViewDidLoad. If the for binding is populated in the WillEnter/DidEnter/Constructor the error is thrown and ionic displays the error page.
My guess is that the ionViewDidLoad is catching the error and not displaying anything. Though the functionality of the tabs still works.. the highlighting doesn't.
Expected behavior:
Error in console and ionic error visible.
Steps to reproduce:
Git Repo: https://github.com/davec21/taberror.git
Repo home: https://github.com/davec21/taberror
Basically.. create a landing page (not the tabs page) and set it as root in the app. Have a bound array that is looped through using *ngFor have code that would echo out an invalid item: ie {{notMy.item}}.  Have the array be empty until ionViewDidLoad() is called. By setting the array to have items in the ionViewDidLoad() function, angular rebinds and will run the *ngFor and try to parse the invalid item.
Have a button to set root to the tabs page, and notice that the tabs function but do not highlight.
Having the array be populated anywhere else will throw the error.  If you use my repo change ionViewDidLoad() to ionViewWillEnter() and see the problem.  Commenting out the populating of the array causes the *ngFor to not run (as no data) and tabs will highlight fine.
It's sort of a confusing error, so if you need more info.. let me know.
Related code:
Git repo posted above.
Other information:
Cordova CLI: 6.5.0
Ionic Framework Version: 3.0.1
Ionic CLI Version: 2.2.2
Ionic App Lib Version: 2.2.1
Ionic App Scripts Version: 1.3.0
ios-deploy version: Not installed
ios-sim version: Not installed
OS: Windows 10
Node Version: v6.7.0
Xcode version: Not installed

Hello, thanks for opening an issue with us, we will look into this.


Add option to silence driver extension errors

To be used for testing where exceptions are expected

The error is still returned to the driver script, it just isn't logged.

Ah ok, great. Please make sure to document where exactly error messages will be sent so that they can be properly handled, since presumably otherwise this won't actually do anything useful (the error messages won't print, but then they're promptly cause the test to fail anyway, right? Unless you catch them somehow).

Updated the doc comment to indicate how errors are returned


🐛 [firebase_messaging] Different notification data on iOS onMessage between 11.2.10 and 11.2.11

Bug report
I updated firebase_messaging and the message in the onMessage callback completely changed.

11.2.10
11.2.11

I don't know what the backend sends but the scope field in data is missed.
Expected behavior
All data should be available in the onMessage callback.
Flutter doctor
Run flutter doctor and paste the output below:
Click To Expand
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.0.0, on macOS 12.4 21F79 darwin-arm, locale
    en-PL)
[✓] Android toolchain - develop for Android devices (Android SDK version 32.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 13.4)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2021.2)
[✓] IntelliJ IDEA Ultimate Edition (version 2022.1.1)
[✓] VS Code (version 1.67.1)
[✓] Connected device (4 available)
[✓] HTTP Host Availability

Flutter dependencies
Run flutter pub deps -- --style=compact and paste the output below:
Click To Expand
Dart SDK 2.17.0
Flutter SDK 3.0.0
td_flutter 1.53.0+405

dependencies:
- bloc 6.1.3 [meta]
- cached_network_image 3.2.1 [flutter flutter_cache_manager octo_image cached_network_image_platform_interface cached_network_image_web]
- chewie 1.1.0 [cupertino_icons flutter video_player wakelock]
- collection 1.16.0
- connectivity 3.0.6 [flutter meta connectivity_platform_interface connectivity_macos connectivity_for_web]
- cupertino_icons 1.0.4
- dotted_line 3.1.0 [flutter]
- email_validator 2.0.1
- equatable 1.2.6 [collection meta]
- file_picker 3.0.4 [flutter flutter_web_plugins flutter_plugin_android_lifecycle plugin_platform_interface]
- firebase_messaging 11.2.11 [firebase_core firebase_core_platform_interface firebase_messaging_platform_interface firebase_messaging_web flutter meta]
- flutter 0.0.0 [characters collection material_color_utilities meta vector_math sky_engine]
- flutter_bloc 6.1.3 [flutter bloc provider]
- flutter_braintree 1.1.0+1 [flutter meta]
- flutter_calendar_carousel 1.5.3 [intl flutter]
- flutter_html 2.0.0-nullsafety.0 [html csslib css_colors flutter_layout_grid video_player chewie webview_flutter chewie_audio flutter_svg flutter]
- flutter_i18n 0.22.4 [flutter flutter_localizations flutter_web_plugins intl yaml xml2json path]
- flutter_localizations 0.0.0 [flutter intl characters clock collection material_color_utilities meta path vector_math]
- flutter_masked_text 0.8.0 [flutter]
- flutter_native_timezone 1.1.0 [flutter_web_plugins flutter js]
- flutter_pdfview 1.2.2 [flutter]
- flutter_secure_storage 3.3.5 [meta flutter]
- flutter_speed_dial 6.0.0 [flutter]
- flutter_svg 0.21.0+1 [flutter meta path_drawing vector_math xml]
- flutter_typeahead 3.2.7 [flutter flutter_keyboard_visibility]
- flutter_uploader 1.2.1 [flutter]
- flutter_user_agent 1.2.2 [flutter]
- font_awesome_flutter 10.1.0 [flutter]
- html 0.15.0 [csslib source_span]
- http 0.13.4 [async http_parser meta path]
- intercom_flutter 7.2.0 [flutter flutter_web_plugins intercom_flutter_platform_interface intercom_flutter_web]
- intl 0.17.0 [clock path]
- jose 0.3.2 [crypto_keys meta typed_data x509 http http_parser asn1lib collection]
- json_annotation 3.1.1
- local_auth 1.1.11 [flutter flutter_plugin_android_lifecycle intl platform]
- merge_map 1.0.2
- meta 1.7.0
- mime 1.0.2
- oauth2 2.0.0 [collection crypto http http_parser]
- open_file 3.2.1 [flutter ffi]
- package_info 0.4.3+4 [flutter]
- path 1.8.1
- path_provider 2.0.10 [flutter path_provider_android path_provider_ios path_provider_linux path_provider_macos path_provider_platform_interface path_provider_windows]
- permission_handler 8.3.0 [flutter meta permission_handler_platform_interface]
- rxdart 0.26.0
- sentry_flutter 6.5.1 [flutter flutter_web_plugins sentry package_info_plus meta]
- share 2.0.4 [meta mime flutter]
- stream_transform 2.0.0
- uni_links 0.4.0 [flutter]
- url_launcher 6.1.2 [flutter url_launcher_android url_launcher_ios url_launcher_linux url_launcher_macos url_launcher_platform_interface url_launcher_web url_launcher_windows]
- uuid 3.0.6 [crypto]
- video_player 2.4.2 [flutter html video_player_android video_player_avfoundation video_player_platform_interface video_player_web]
- vimeo_player_flutter 0.0.3+1 [flutter webview_flutter]
- webview_flutter 2.8.0 [flutter webview_flutter_android webview_flutter_platform_interface webview_flutter_wkwebview]
- youtube_player_iframe 2.3.0 [flutter flutter_inappwebview url_launcher]

dev dependencies:
- build_runner 1.11.5 [args async build build_config build_daemon build_resolvers build_runner_core code_builder collection crypto dart_style glob graphs http_multi_server io js logging meta mime path pedantic pool pub_semver pubspec_parse shelf shelf_web_socket stack_trace stream_transform timing watcher web_socket_channel yaml]
- flutter_launcher_icons 0.9.2 [args image path yaml]
- flutter_test 0.0.0 [flutter test_api path fake_async clock stack_trace vector_math async boolean_selector characters charcode collection matcher material_color_utilities meta source_span stream_channel string_scanner term_glyph]
- json_serializable 3.5.2 [analyzer build build_config json_annotation meta path source_gen]
- lint 1.8.2

dependency overrides:
- analyzer 1.7.2 [_fe_analyzer_shared cli_util collection convert crypto glob meta package_config path pub_semver source_span watcher yaml pedantic]
- platform 3.1.0

transitive dependencies:
- _fe_analyzer_shared 22.0.0 [meta]
- archive 3.3.0 [crypto path]
- args 2.3.1
- asn1lib 1.1.0
- async 2.8.2 [collection meta]
- boolean_selector 2.1.0 [source_span string_scanner]
- build 1.6.3 [analyzer async convert crypto glob logging meta path]
- build_config 0.4.6 [checked_yaml json_annotation meta path pubspec_parse yaml]
- build_daemon 2.1.10 [built_collection built_value http_multi_server logging pedantic path pool shelf shelf_web_socket stream_transform watcher web_socket_channel]
- build_resolvers 1.5.4 [analyzer build crypto graphs logging meta path package_config pool pub_semver]
- build_runner_core 6.1.10 [async build build_config build_resolvers collection convert crypto glob graphs logging meta path package_config pedantic pool timing watcher yaml]
- built_collection 5.1.1
- built_value 8.3.0 [built_collection collection fixnum meta]
- cached_network_image_platform_interface 1.0.0 [flutter flutter_cache_manager]
- cached_network_image_web 1.0.1 [flutter flutter_cache_manager cached_network_image_platform_interface]
- characters 1.2.0
- charcode 1.3.1
- checked_yaml 1.0.4 [json_annotation source_span yaml]
- chewie_audio 1.3.0 [cupertino_icons flutter video_player]
- cli_util 0.3.5 [meta path]
- clock 1.1.0
- code_builder 3.7.0 [built_collection built_value collection matcher meta]
- connectivity_for_web 0.4.0+1 [connectivity_platform_interface flutter_web_plugins flutter]
- connectivity_macos 0.2.1+2 [flutter connectivity_platform_interface]
- connectivity_platform_interface 2.0.1 [flutter meta plugin_platform_interface]
- convert 3.0.1 [typed_data]
- crypto 3.0.2 [typed_data]
- crypto_keys 0.3.0 [pointycastle meta collection quiver]
- css_colors 1.1.1 [flutter]
- csslib 0.17.1 [source_span]
- dart_style 1.3.14 [analyzer args path pub_semver source_span]
- fake_async 1.3.0 [clock collection]
- ffi 1.2.1
- file 6.1.2 [meta path]
- firebase_core 1.17.0 [firebase_core_platform_interface firebase_core_web flutter meta]
- firebase_core_platform_interface 4.4.0 [collection flutter meta plugin_platform_interface]
- firebase_core_web 1.6.4 [firebase_core_platform_interface flutter flutter_web_plugins js meta]
- firebase_messaging_platform_interface 3.5.0 [firebase_core flutter meta plugin_platform_interface]
- firebase_messaging_web 2.4.0 [firebase_core firebase_core_web firebase_messaging_platform_interface flutter flutter_web_plugins js meta]
- fixnum 1.0.1
- flutter_blurhash 0.7.0 [flutter]
- flutter_cache_manager 3.3.0 [clock collection file flutter http path path_provider pedantic rxdart sqflite uuid]
- flutter_inappwebview 5.4.3+7 [flutter]
- flutter_keyboard_visibility 5.2.0 [meta flutter_keyboard_visibility_platform_interface flutter_keyboard_visibility_web flutter]
- flutter_keyboard_visibility_platform_interface 2.0.0 [flutter meta plugin_platform_interface]
- flutter_keyboard_visibility_web 2.0.0 [flutter_keyboard_visibility_platform_interface flutter_web_plugins flutter]
- flutter_layout_grid 1.0.6 [flutter collection meta quiver]
- flutter_plugin_android_lifecycle 2.0.6 [flutter]
- flutter_web_plugins 0.0.0 [flutter js characters collection material_color_utilities meta vector_math]
- glob 2.0.2 [async collection file path string_scanner]
- graphs 0.2.0
- http_multi_server 2.2.0 [async]
- http_parser 4.0.1 [collection source_span string_scanner typed_data]
- image 3.1.3 [archive meta xml]
- intercom_flutter_platform_interface 1.2.0 [flutter plugin_platform_interface]
- intercom_flutter_web 0.2.0 [flutter flutter_web_plugins intercom_flutter_platform_interface uuid]
- io 0.3.5 [meta path string_scanner]
- js 0.6.4
- logging 1.0.2
- matcher 0.12.11 [stack_trace]
- material_color_utilities 0.1.4
- nested 1.0.0 [flutter]
- octo_image 1.0.2 [flutter flutter_blurhash]
- package_config 2.0.2 [path]
- package_info_plus 1.4.2 [flutter package_info_plus_platform_interface package_info_plus_linux package_info_plus_macos package_info_plus_windows package_info_plus_web]
- package_info_plus_linux 1.0.5 [package_info_plus_platform_interface flutter path]
- package_info_plus_macos 1.3.0 [flutter]
- package_info_plus_platform_interface 1.0.2 [flutter meta plugin_platform_interface]
- package_info_plus_web 1.0.5 [flutter flutter_web_plugins http meta package_info_plus_platform_interface]
- package_info_plus_windows 1.0.5 [package_info_plus_platform_interface ffi flutter win32]
- path_drawing 0.5.1+1 [vector_math meta path_parsing flutter]
- path_parsing 0.2.1 [vector_math meta]
- path_provider_android 2.0.14 [flutter path_provider_platform_interface]
- path_provider_ios 2.0.9 [flutter path_provider_platform_interface]
- path_provider_linux 2.1.6 [ffi flutter path path_provider_platform_interface xdg_directories]
- path_provider_macos 2.0.6 [flutter path_provider_platform_interface]
- path_provider_platform_interface 2.0.4 [flutter platform plugin_platform_interface]
- path_provider_windows 2.0.6 [ffi flutter path path_provider_platform_interface win32]
- pedantic 1.11.1
- permission_handler_platform_interface 3.7.0 [flutter meta plugin_platform_interface]
- petitparser 5.0.0 [meta]
- plugin_platform_interface 2.1.2 [meta]
- pointycastle 3.6.0 [collection convert js]
- pool 1.5.0 [async stack_trace]
- process 4.2.4 [file path platform]
- provider 4.3.3 [collection flutter nested]
- pub_semver 2.1.1 [collection meta]
- pubspec_parse 0.1.8 [checked_yaml json_annotation pub_semver yaml]
- quiver 3.1.0 [matcher]
- sentry 6.5.1 [http meta stack_trace uuid]
- shelf 1.3.0 [async collection http_parser path stack_trace stream_channel]
- shelf_web_socket 0.2.4+1 [shelf stream_channel web_socket_channel]
- sky_engine 0.0.99
- source_gen 0.9.10+3 [analyzer async build dart_style glob meta path pedantic source_span]
- source_span 1.8.2 [collection path term_glyph]
- sqflite 2.0.2+1 [flutter sqflite_common path]
- sqflite_common 2.2.1+1 [synchronized path meta]
- stack_trace 1.10.0 [path]
- stream_channel 2.1.0 [async]
- string_scanner 1.1.0 [charcode source_span]
- synchronized 3.0.0+2
- term_glyph 1.2.0
- test_api 0.4.9 [async boolean_selector collection meta source_span stack_trace stream_channel string_scanner term_glyph matcher]
- timing 0.1.1+3 [json_annotation]
- typed_data 1.3.1 [collection]
- url_launcher_android 6.0.17 [flutter url_launcher_platform_interface]
- url_launcher_ios 6.0.16 [flutter url_launcher_platform_interface]
- url_launcher_linux 3.0.1 [flutter url_launcher_platform_interface]
- url_launcher_macos 3.0.1 [flutter url_launcher_platform_interface]
- url_launcher_platform_interface 2.0.5 [flutter plugin_platform_interface]
- url_launcher_web 2.0.11 [flutter flutter_web_plugins url_launcher_platform_interface]
- url_launcher_windows 3.0.1 [flutter url_launcher_platform_interface]
- vector_math 2.1.2
- video_player_android 2.3.4 [flutter video_player_platform_interface]
- video_player_avfoundation 2.3.4 [flutter video_player_platform_interface]
- video_player_platform_interface 5.1.2 [flutter plugin_platform_interface]
- video_player_web 2.0.10 [flutter flutter_web_plugins video_player_platform_interface]
- wakelock 0.5.6 [flutter meta wakelock_macos wakelock_platform_interface wakelock_web wakelock_windows]
- wakelock_macos 0.4.0 [flutter flutter_web_plugins wakelock_platform_interface]
- wakelock_platform_interface 0.3.0 [flutter meta]
- wakelock_web 0.4.0 [flutter flutter_web_plugins js wakelock_platform_interface]
- wakelock_windows 0.2.0 [flutter wakelock_platform_interface win32]
- watcher 1.0.1 [async path]
- web_socket_channel 1.2.0 [async crypto stream_channel]
- webview_flutter_android 2.8.8 [flutter webview_flutter_platform_interface]
- webview_flutter_platform_interface 1.9.0 [flutter meta plugin_platform_interface]
- webview_flutter_wkwebview 2.7.5 [flutter path webview_flutter_platform_interface]
- win32 2.6.1 [ffi]
- x509 0.2.2 [asn1lib quiver crypto_keys]
- xdg_directories 0.2.0+1 [meta path process]
- xml 5.4.1 [collection meta petitparser]
- xml2json 5.3.2 [xml]
- yaml 3.1.1 [collection source_span string_scanner]

Thanks for the report. Keeping it open for further insights from the team.
/cc @russellwheatley

I closed this because it turns out that only data messages don't work. I opened a better described issue https://github.com/firebase/flutterfire/issues/9902


Fallback plugin logic faulty

🐛 Bug
Dragging and dropping an (apparently malformed 😅) multiscale .zarr folder to napari gave me the following error:
INFO:napari_plugin_engine.manager:loaded 3 plugins:
  <module 'napari.plugins._builtins' from '/Users/jni/conda/envs/all/lib/python3.8/site-packages/napari/plugins/_builtins.py'>
  <module 'napari_svg' from '/Users/jni/conda/envs/all/lib/python3.8/site-packages/napari_svg/__init__.py'>
  <module 'ome_zarr' from '/Users/jni/conda/envs/all/lib/python3.8/site-packages/ome_zarr.py'>
  <module 'napari_plugin_engine' from '/Users/jni/conda/envs/all/lib/python3.8/site-packages/napari_plugin_engine/__init__.py'>
ERROR:napari.plugins.io:PluginError: Error in plugin 'builtins', hook 'napari_get_reader': local variable 'image' referenced before assignment
  Cause was: local variable 'image' referenced before assignment
    version: 0.3.0
    package: napari

ERROR:napari.components.add_layers_mixin:No plugin found capable of reading /Volumes/datac/napari-data/covid-gut/.

Note "local variable image referenced before assignment". This should never happen.

Another logic issue: if data is a list BUT the arrays are not in decreasing order of size, we throw an AttributeError:
~/conda/envs/all/lib/python3.8/site-packages/napari/layers/image/image.py in __init__(self, data, rgb, colormap, contrast_limits, gamma, interpolation, rendering, iso_threshold, attenuation, name, metadata, scale, translate, opacity, blending, visible, multiscale)
    162             init_shape = data[0].shape
    163         else:
--> 164             init_shape = data.shape
    165
    166         # Determine if rgb

AttributeError: 'list' object has no attribute 'shape'

In this case this happened because the plugin (I'm still trying to figure out why) ended up providing the arrays in lexicographical (0, 1, 10, 2) order rather than numerical.
We should detect malformed data and quit gracefully (or re-sort, but I like that less), rather than crash with a mysterious error.

do you have the full stack trace on that first one?   I think (but I'm not sure) that that's an error in magic_imread (based on the variable name image) ...
(plugin errors will usually be using raise from ... so the plugin error is probably the one above that one)

@tlambert03

do you have the full stack trace

Not just yet, and that might be a problem. ;) ie I can't get the stack trace if I launched napari from the command line.
Anyway, I think you're right. In this chunk:
    for filename in filenames_expanded:
        ext = os.path.splitext(filename)[-1]
        if ext == '.zarr':
            image, zarr_shape = read_zarr_dataset(filename)
            if shape is None:
                shape = zarr_shape
        else:
            if shape is None:
                image = imread(filename)
                shape = image.shape
                dtype = image.dtype
            if use_dask:
                image = da.from_delayed(
                    delayed(imread)(filename), shape=shape, dtype=dtype
                )
            elif len(images) > 0:  # not read by shape clause
                image = imread(filename)
        images.append(image)

image can be unassigned by the time you hit append.
I'll keep investigating.

I can't get the stack trace if I launched napari from the command line.

not even in the plugin error reporter?  under builtins?
ohhh ... do you mean you launch it with a filepath and it quits immediately??  hadn't thought about that!

if it's the covid-gut folder you're using, from Josh's download code the other day...  I get the same error.  i just ran it through a debugger and it's a couple things:

filenames_expanded remains empty after the if os.path.isdir(filename) and not ext == '.zarr': block... because it strips all the subdirectories...
then
line 224 then fails because the attempt to catch the ValueError and provide a helpful message is (my) bad.  the exception clause should have a else: raise e to re-reraise the error regardless

do you mean you launch it with a filepath and it quits immediately?? hadn't thought about that!

Well, the thing is, that should never ever ever happen, so it's fair enough. We just need to iron out all the bugs from failures when the plugins fail.

btw, @tlambert03, yes, it's from that covid folder, except you need to add a .zgroup file to the root folder with the contents {"zarr_format":2}.
After I do that, I get the second error due to the pyramid checks failing. Not sure yet if it's an issue with the plugin or with how I downloaded the folder. But if I delete the 10.zarr level (and the corresponding dict in the json) it works! 🎉 😂

Awesome! Ok, well I’ll make a PR to fix those issues anyway, since they’re still bugs

Closing this as main bugs were fixed by #1218 and remaining error now has its own issue in #1231


Adding custom characters in 0.7.1h

Describe your problem here.
I was doing stuff, i tried to add custom characters, and it stuck on daddy's sprites. Source code overhauled in 0.7.1h, so i need a new tutorial, thanks.
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
nah

i think the overhaul won't change much for the sprites, it works just fine on my end. just remember to use the right sprites on the character editor, and to use the right character on the chart editor

Yeah, i was dumb, and the name in xml didn't match with the actual name.


Add waiting_for_inventory_refresh state to InfraConversionJob

For IMS 1.3 we're moving state machine handling from automate into core. For ease of writing and review, we're breaking this down into (hopefully) easily digestible bits, one state at a time. Each PR will ultimately have a corresponding PR in manageiq-content that deletes the relevant bit of code from automate.
Original automate code:
https://github.com/ManageIQ/manageiq-content/blob/master/content/automate/ManageIQ/Transformation/Infrastructure/VM/Common.class/__methods__/checkvmininventory.rb
This PR adds waiting_for_inventory_refresh state to the state machine. The state machine is changed to allow transition from transforming_vm.
RHBZ: https://bugzilla.redhat.com/show_bug.cgi?id=1747338
Depends on #19149, #19150, #19154, #19177, #19200, #19216, #19222

@miq-bot add-label transformation, refactoring, ivanchuk/yes
@miq-bot add-reviewer @agrare

@miq-bot add-reviewer @djberg96

Closing in favor of https://github.com/ManageIQ/manageiq/pull/19238.


Expose Groups function

Codecov Report

Merging #1 into master will increase coverage by 0.25%.
The diff coverage is 80.00%.

@@            Coverage Diff             @@
##           master       #1      +/-   ##
==========================================
+ Coverage   91.86%   92.12%   +0.25%
==========================================
  Files           2        2
  Lines         123      127       +4
==========================================
+ Hits          113      117       +4
  Misses          6        6
  Partials        4        4

Impacted Files
Coverage Δ

regroup.go
91.08% <80.00%> (+0.36%)
:arrow_up:

Continue to review full report at Codecov.

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


Try out docker-compose 2.5.0

The Problem/Issue/Bug:
docker-compose 2.5.0 has been released, and it may solve some of the problems that have plagued previous versions.
How this PR Solves The Problem:
Manual Testing Instructions:
Automated Testing Overview:

Related Issue Link(s):
Release/Deployment notes:

This time the problem is that relative paths (or at least short relative paths) are no longer supported for bind mounts. So .:/mnt/ddev_config and ../:/var/www/html seem to fail.
The ../:/var/www/html is probably essential for PhpStorm with WSL2.

Opened

https://github.com/docker/compose/issues/9428
for this issue. Will try again when it's fixed and released.


[WIP] fix/Develop-Dockerfile

Proposed changes
The images for the open-aea repository have not been updated to account for the SSL issue raised in the open-autonomy repository.
This pr does 2 things;
resolves the ssl issue for develop branch -> see dockerfile from the open-autonomy repository
adds golang as a dependency to enable tests Potentially this should be removed?

Branched from main.
Fixes
If it fixes a bug or resolves a feature request, be sure to link to that issue.
Types of changes
What types of changes does your code introduce to agents-aea?
Put an x in the boxes that apply

[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist
Put an x in the boxes that apply.

[ ] I have read the CONTRIBUTING doc
[ ] I am making a pull request against the develop branch (left side). Also you should start your branch off our develop.
[ ] Lint and unit tests pass locally with my changes and CI passes too
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have checked that code coverage does not decrease.
[ ] I have added necessary documentation (if appropriate)
[ ] Any dependent changes have been merged and published in downstream modules

Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...
DELETE INCLUSIVE THIS AND BELOW FOR STANDARD PR
Release summary
Version number: [e.g. 1.0.1]
Release details
Describe in short the main changes with the new release.
Checklist
Put an x in the boxes that apply.

[ ] I have read the CONTRIBUTING doc
[ ] I am making a pull request against the main branch (left side), from develop
[ ] Lint and unit tests pass locally and in CI
[ ] I have checked the fingerprint hashes are correct by running (aea hash all --check)
[ ] I have regenerated the latest API docs
[ ] I built the documentation and updated it with the latest changes
[ ] I have added an item in HISTORY.md for this release
[ ] I bumped the version number in the aea/__version__.py file.
[ ] I bumped the version number in every Docker image of the repo and published it. Also, I built and published them with tag latest
(check the READMEs of aea-develop
and aea-user)
[ ] I have pushed the latest packages to the registry.
[ ] I have uploaded the latest aea to PyPI.
[ ] I have uploaded the latest plugins to PyPI.

Further comments
Write here any other comment about the release, if any.

Codecov Report

Merging #235 (4b688be) into main (ebe592d) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #235   +/-   ##
=======================================
  Coverage   94.55%   94.55%
=======================================
  Files         312      312
  Lines       25157    25157
=======================================
  Hits        23786    23786
  Misses       1371     1371

Flag
Coverage Δ

unittests
94.55% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Continue to review full report at Codecov.

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


Changes to onboard WOPI android documentation - Part 1

This includes: Overview- all subpages, Scenarios - Browsing opening and saving from office.
The next part would include: Scenarios - Opening files from your app, app to app sign-in.

@jj-invincible,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


M3-4951 change: remove overriding font style for receive transfer modal

Description
Removes the overriding font styles for the receive service transfer modal, using Typography's body font-style of 0.875rem(14px) instead.
Before:

After:

Type of Change

Non breaking change ('update', 'change')

@HanaXu be sure to assign the PRs you open to yourself in the "Assignees" section on the right 👍

Hmm doesn't seem like I can assign myself now. Is that something that needs to be done before opening the PR?


IoTConvert.GsmCommunicationJsonToBusinessObject fails with locals not using dot as decimal separator

IoTConvert.GsmCommunicationJsonToBusinessObject expects a json formatted string as parameter.
Problem:
The methods that are called internally are using float.Parse(s) without passing InvariantCulture as  NumberFormatInfo parameter so the process fails if executed on a system where the decimal separator is not a ".".
Example this happens in the (internal) CommandRuleCapitalM.ParseCurrentValuesOfSelectedChannels method
Some further thoughts:

The GsmCommunicationToJson(string) method returns numeric values as strings but should use numerics.
Example:
"F": {
"e": "0"
}
should be:
"F": {
"e": 0
}

GsmCommunicationToJson(string) should return a JObject instead of a string. Is there a reason why the methods expecting a JObject are not public?

Consequently GsmCommunicationJsonToBusinessObject should take a JObject instead of (or optionally) a string.

As a work around we can set CurrentCulture to "en-US" but would like to get rid of this as soon as possible.
In general this library is of great help to us to process files sent to us from the Keller waterlevel sensors. Thanks for that!
Best wishes
AM

Sorry for the long wait. This issue was on my todo list but it would not make it to the top....  :-(
I could verify the issue -> https://github.com/KELLERAGfuerDruckmesstechnik/KellerAg.Shared.IoT.Converters/commit/5e7e450ae14e058e495b6ff6ab98b48742707d2b#r84188844
Today, I finally uploaded all the missing source. We also fixed the issue with 2801f202586760d422e99b65c497bffd8beb10af
I also updated the nuget package but in your case you might better just take the project/s to .
Next week I plan to upgrade the live editor, too and hope to add .NET 6 support.
Again, sorry for the long waiting time!

Hi Sebastian,
thanks for the nice reply, I appreciate it and your work also.
Now hopefully the update makes its way on top of my todo list soon. ;-)
Have a nice weekend.
Best greetings from Graz
Alois
Mit freundlichen Grüßen
Alois Maierhofer
Lead Software Engineer
GEODATA Informationstechnologie GmbH
Klosterwiesgasse 103b, A-8010 Graz
Tel: +43 (3842) 26 555 60
Mobil: +43 (664) 15 12 205
e-mail: @.*** Web: www.geodata.comhttp://www.geodata.com

From: Sebastian Mojado @.>
Sent: Friday, September 16, 2022 6:29:33 PM
To: KELLERAGfuerDruckmesstechnik/KellerAg.Shared.IoT.Converters @.>
Cc: Alois Maierhofer @.>; Author @.>
Subject: Re: [KELLERAGfuerDruckmesstechnik/KellerAg.Shared.IoT.Converters] IoTConvert.GsmCommunicationJsonToBusinessObject fails with locals not using dot as decimal separator (Issue #1)
Sorry for the long wait. This issue was on my todo list but it would not make it to the top.... :-(
I could verify the issue -> 5e7e450#r84188844https://github.com/KELLERAGfuerDruckmesstechnik/KellerAg.Shared.IoT.Converters/commit/5e7e450ae14e058e495b6ff6ab98b48742707d2b#r84188844
Today, I finally uploaded all the missing source. We also fixed the issue with 2801f20https://github.com/KELLERAGfuerDruckmesstechnik/KellerAg.Shared.IoT.Converters/commit/2801f202586760d422e99b65c497bffd8beb10af
I also updated the nuget package but in your case you might better just take the project/s to .
Next week I plan to upgrade the live editor, too and hope to add .NET 6 support.
Again, sorry for the long waiting time!
—
Reply to this email directly, view it on GitHubhttps://github.com/KELLERAGfuerDruckmesstechnik/KellerAg.Shared.IoT.Converters/issues/1#issuecomment-1249562370, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AXV3OGG7PK3NY2XMMS6735DV6SN63ANCNFSM5N5MWWEA.
You are receiving this because you authored the thread.Message ID: @.***>


Make background scanning enabled by default

Description:
Currently iOS default background scan is set to enabled and 5 minutes interval.
Let's make the same default for Android.

QA passed


Error in log and map doesn't update

Which addon?
ICantBelieveItsNotValetudo
Describe the bug
Errors in log and no map produced
To Reproduce

Start addon
See error in log:

SyntaxError: Unexpected token  in JSON at position 0
    at JSON.parse (<anonymous>)
    at MqttClient.<anonymous> (/app/lib/MqttClient.js:145:43)
    at MqttClient.emit (events.js:315:20)
    at MqttClient._handlePublish (/app/node_modules/mqtt/lib/client.js:1277:12)
    at MqttClient._handlePacket (/app/node_modules/mqtt/lib/client.js:410:12)
    at work (/app/node_modules/mqtt/lib/client.js:321:12)
    at Writable.writable._write (/app/node_modules/mqtt/lib/client.js:335:5)
    at doWrite (/app/node_modules/mqtt/node_modules/readable-stream/lib/_stream_writable.js:409:139)
    at writeOrBuffer (/app/node_modules/mqtt/node_modules/readable-stream/lib/_stream_writable.js:398:5)
    at Writable.write (/app/node_modules/mqtt/node_modules/readable-stream/lib/_stream_writable.js:307:11)

System

Supervisor version: supervisor-2021.03.4
Host system version: Home Assistant OS 5.12

Please take a look at #187, maybe the issue could be solved with the information there.

This is my mistake, I forgot that I tried ValetudoRE instead and apparently the map data goes differently. I will test valetudo mapper instead. Appologies.

All good 😉


#6013 support for json return in helm search

Signed-off-by: Art Begolli<EMAIL_ADDRESS>
What this PR does / why we need it:
closes #6013
Special notes for your reviewer:
If applicable:

[x] this PR contains documentation
[x] this PR contains unit tests
[x] this PR has been tested for backwards compatibility

Sorry for not getting back to you sooner. The team has been focusing for the past few months on getting Helm 3 out the door, and that has meant it's been harder to find time to review feature additions for Helm 2.
Helm 2.15 is soon to be released, and will be the last feature release for Helm 2. Because of the time commitment required to review and test this, we won't be able to find the time to review.
That being said, if you want to try again by reconsidering this for Helm 3, that would be much appreciated. I'd hold off for a few weeks until 2.15 is out as we are planning to move the dev-v3 branch over to be the new master branch, so there will be some shuffling around for a bit, but once that's done we'd be happy to consider this for the 3.1.0 release. I'd highly suggest taking a look at Helm 3 first to make sure this hasn't already been addressed.
Thanks again!


Views cannot discovered automatically from an external assembly in net core 2.x

I have an RazorUIClassLib project with 1 view and 1 controller.
When i refrence project's dlls to another mvc core 2.1 project, the controller and view can not discovered automatically.
By adding this lines to startup, Controller discovered
services.AddMvc()
.AddApplicationPart(typeof(MyController).GetTypeInfo().Assembly)
.AddControllersAsServices();
But view still not found.
If i make nuget package from RazorUIClassLib project and install it on target project then controller and view discovered automatically but i need to use direct reference to target projects.

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

ID: 9fd019c7-ceb7-6ef3-26ba-6b44341b6fc5
Version Independent ID: fd116d00-0dc7-efaf-c714-34d77b345a05
Content: Reusable Razor UI in class libraries with ASP.NET Core
Content Source: aspnetcore/razor-pages/ui-class.md
Product: aspnet-core
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

@pranavkm please comment

Views are in a separate assembly, and they need to be registered as an application part. Here's the equivalent code:
https://github.com/pranavkm/PluginApp/blob/master/MainApp/Startup.cs#L81-L89
That said, if you have project reference to the class library project or reference it as a package, you shouldn't have to do any of this.

@hamed-shirbandi This could be similar to the issue #13951 I experienced. You need to use dotnet pack instead of nuget pack.


New release date

Hi @msawczyn, how are you?
When do you plan to release the next release?
Thank you

Very soon now. Just getting a few loose ends (read: bugs) tidied up and the end-to-end testing finalized.
No firm date, unfortunately. Depends on how much I get piled on in my real job. It's been pretty busy for quite a while now.

Hello @msawczyn, how are you?
Will we be getting a new release soon?
I see the RC2 was ready in Feb of '24.
Thank you.


Can't login to a brand new app unless CORS allowed-origins is modified

Describe the bug
If I create a new app with jhipster jdl bug-tracker.jdl --blueprints react-native, I cannot log in because of CORS.

Maybe it's always been this way? If I look at the last tutorial I wrote about it, the origin was http://localhost:19006 and you needed to add it. It seems like we should be able to modify CORS as part of the generation process so people have a better developer experience.
It also doesn't generate any entities in the React Native client.

There are entities generated in the JHipster app.

I noticed this happens with the Ionic blueprint too. I didn't think anything of it when I saw it earlier, but it appears to be a bug.
I also had to run npm install in both generated clients, which doesn't follow the main generator's process of installing everything by default.
Instructions To reproduce
jhipster jdl bug-tracker.jdl --blueprints react-native

If I try with the following (after running npm link in the project):
jhipster jdl bug-tracker.jdl --blueprints react-native --skip-jhipster-dependencies

It get a different error and npm start doesn't work when choosing the w option:

JHipster app's .yo-rc.json
{
  "generator-jhipster": {
    "baseName": "jhipster",
    "blueprints": [
      {
        "name": "generator-jhipster-react-native",
        "version": "4.4.0"
      }
    ],
    "devServerPort": 4200,
    "entities": ["Project", "Label", "Ticket", "Attachment", "Comment"],
    "jhipsterVersion": "8.5.0",
    "jwtSecretKey": "YzcwZjFiY2M3NjAzYTk2YWU2MGJiODQ5NDlhNzc2MmJjYmNmYWVlMzc0NDVmOTEwMThjMTkzYWE0NzkzOGFlZDExZDgxOTY4NTUyNjc5NDY4MzQ2MWRjYjA2OTY3YTJiMmYxMDg0NDkzZTc3MTgwNDg5YzdiNmQ1OTE5NTVhZmY=",
    "languages": ["en"],
    "lastLiquibaseTimestamp":<PHONE_NUMBER>000,
    "nativeLanguage": "en",
    "prodDatabaseType": "postgresql",
    "skipJhipsterDependencies": true
  },
  "generator-jhipster-react-native": {
    "appDir": null,
    "reactNativeDir": "../client"
  }
}

Entity JDL or JSON files
entity Project {
  name String
}

entity Label {
  label String required minlength(3)
}

application {
  config {
    prodDatabaseType postgresql,
  }
  entities *
}

entity Ticket {
  title String required
  description String
  dueDate LocalDate
  date ZonedDateTime
  status Status
  type Type
  priority Priority
}

entity Attachment {
  name String required minlength(3)
  file Blob
}

relationship ManyToMany {
  Ticket{label(label)} to Label{ticket}
}

relationship ManyToOne {
  Ticket{project(name)} to Project
  Ticket{assignedTo(login)} to User with builtInEntity
  Ticket{reportedBy(login)} to User with builtInEntity
  Comment{login} to User with builtInEntity
}

relationship OneToMany {
  Comment{parent} to Comment{child}
  Ticket to Attachment
}

enum Status {
  OPEN("Open")
  WAITING_FOR_RESPONSE("Waiting for Customer Response")
  CLOSED("Closed")
  DUPLICATE("Duplicate")
  IN_PROGRESS("In Progress")
  REOPENED("Reopened")
  CANNOT_REPRODUCE("Cannot Reproduce")
  SOLVED("Solved")
  WONT_IMPLEMENT("Won't Implement")
  VERIFIED("Verified")

}

enum Type {
  BUG("Bug"),
  FEATURE("Feature")
}

enum Priority {
  HIGHEST("Highest")
  HIGHER("Higher")
  HIGH("High")
  NORMAL("Normal")
  LOW("Low")
  LOWER("Lower")
  LOWERST("Lowest")
}

entity Comment {
  date ZonedDateTime
  text String
}

paginate Ticket with pagination

Versions (please complete the following information):

JHipster React Native Version: main

I was able to fix the Error: EMFILE: too many open files, watch error with brew install watchman.
Source: https://stackoverflow.com/a/58675202/65681

We should copy the server generator from ionic.
https://github.com/jhipster/generator-jhipster-ionic/tree/main/generators/server

@mshima It's interesting that this exists because the main generator allows Ionic by default.

@mshima It's interesting that this exists because the main generator allows Ionic by default.

@mraible only for ionic serve, simulators requires capacitor://localhost and http://localhot.

@mshima Yes, you are correct. I'm wondering if we should add React Native's web by default, or remove Ionic and tell folks to add it. I kinda like that everything works when running in "dev" mode.


Error when publishing a release to github

For some reason I started getting this error when publishing to GitHub, although it seems as though the actual release works fine:
><EMAIL_ADDRESS>github-release /Users/fergusmcdowall/node/search-index-adder
> conventional-github-releaser -p angular

[ { url: 'https://api.github.com/repos/fergiemcdowall/search-index-adder/releases/6932093',
    assets_url: 'https://api.github.com/repos/fergiemcdowall/search-index-adder/releases/6932093/assets',
    upload_url: 'https://uploads.github.com/repos/fergiemcdowall/search-index-adder/releases/6932093/assets{?name,label}',
    html_url: 'https://github.com/fergiemcdowall/search-index-adder/releases/tag/v0.3.6',
    id: 6932093,
    tag_name: 'v0.3.6',
    target_commitish: 'master',
    name: 'v0.3.6',
    draft: false,
    author:
     { login: 'fergiemcdowall',
       id: 1122333,
       avatar_url: 'https://avatars2.githubusercontent.com/u/1122333?v=3',
       gravatar_id: '',
       url: 'https://api.github.com/users/fergiemcdowall',
       html_url: 'https://github.com/fergiemcdowall',
       followers_url: 'https://api.github.com/users/fergiemcdowall/followers',
       following_url: 'https://api.github.com/users/fergiemcdowall/following{/other_user}',
       gists_url: 'https://api.github.com/users/fergiemcdowall/gists{/gist_id}',
       starred_url: 'https://api.github.com/users/fergiemcdowall/starred{/owner}{/repo}',
       subscriptions_url: 'https://api.github.com/users/fergiemcdowall/subscriptions',
       organizations_url: 'https://api.github.com/users/fergiemcdowall/orgs',
       repos_url: 'https://api.github.com/users/fergiemcdowall/repos',
       events_url: 'https://api.github.com/users/fergiemcdowall/events{/privacy}',
       received_events_url: 'https://api.github.com/users/fergiemcdowall/received_events',
       type: 'User',
       site_admin: false },
    prerelease: false,
    created_at: '2017-07-03T05:13:19Z',
    published_at: '2017-07-05T05:56:41Z',
    assets: [],
    tarball_url: 'https://api.github.com/repos/fergiemcdowall/search-index-adder/tarball/v0.3.6',
    zipball_url: 'https://api.github.com/repos/fergiemcdowall/search-index-adder/zipball/v0.3.6',
    body: '### Features\n\n* **indexing:** can now do appendOnly ([be5167e](https://github.com/fergiemcdowall/search-index-adder/commit/be5167e))',
    meta:
     { 'x-ratelimit-limit': '5000',
       'x-ratelimit-remaining': '4997',
       'x-ratelimit-reset': '1499234292',
       'x-oauth-scopes': 'repo',
       location: 'https://api.github.com/repos/fergiemcdowall/search-index-adder/releases/6932093',
       etag: '"48c9e37b6d98af87149133b3ae640fe5"',
       status: '201 Created' } } ]

npm ERR! Darwin 16.6.0
npm ERR! argv "/Users/fergusmcdowall/.nvm/versions/node/v7.9.0/bin/node" "/Users/fergusmcdowall/.nvm/versions/node/v7.9.0/bin/npm" "run" "github-release"
npm ERR! node v7.9.0
npm ERR! npm  v4.2.0
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>github-release: `conventional-github-releaser -p angular`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>github-release script 'conventional-github-releaser -p angular'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the search-index-adder package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     conventional-github-releaser -p angular
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs search-index-adder
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls search-index-adder
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/fergusmcdowall/.npm/_logs/2017-07-05T05_56_41_987Z-debug.log

@1.1.10 works fine- this problem appeared in @1.1.11

@fergiemcdowall, I looked through out changes between version 1.1.10 and 1.1.11, of which there were three, and all three touch either our CI setup, or relax our Node requirements.
Can you please confirm you're using version 1.1.11 of conventional-github-releaser?

I got this error on 1.1.12.

Yes, actually it seems like the problem appeared in 1.1.12 for me too

Version 1.1.12 was released with the following commit (7c1e4d9) that introduced a fix to cause conventional-github-releaser to fail if, and only if, one or more POST requests to GitHub failed (400 or 500 errors).
I can't tell if that's actually what's happening based on the example output in the initial comment. I see a 201 response code, but my assumption is that github.releases.createRelease (here would be calling the callback function with null for the error since 201 is a valid success response. Therefore, we should be seeing a resolved promise, not a rejected promise followed by an error to console.
I'll put together a test case to walk through conventional-github-releaser and see how a 201 response is treated.
If y'all have a set of steps to quickly and easily reproduce this error, in addition to an example repository, it would really help me speed up the debugging process.

I have the same issue, it seems that this check is failing: https://github.com/conventional-changelog/conventional-github-releaser/blob/master/src/cli.js#L120-L129
The state property does not exist when using Q.all and only works with Q.allSettled.
I create a PR.

Thanks to a bug fix submitted by @danez, version v1.1.13 has been released to address this issue.

Hello, is this related?
→ conventional-github-releaser --version
2.0.0
0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/Cellar/node/8.7.0/bin/node',
1 verbose cli   '/usr/local/bin/npm',
1 verbose cli   'run',
1 verbose cli   'github-release' ]
2 info using<EMAIL_ADDRESS>3 info using<EMAIL_ADDRESS>4 verbose run-script [ 'pregithub-release', 'github-release', 'postgithub-release' ]
5 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>6 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>7 verbose lifecycle<EMAIL_ADDRESS>unsafe-perm in lifecycle true
8 verbose lifecycle<EMAIL_ADDRESS>PATH: /usr/local/lib/node_modules/npm/bin/node-gyp-bin:/Users/Sammy/Projects/hidsi-web/node_modules/.bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin
9 verbose lifecycle<EMAIL_ADDRESS>CWD: /Users/Sammy/Projects/hidsi-web
10 silly lifecycle<EMAIL_ADDRESS>Args: [ '-c', 'conventional-github-releaser -p angular' ]
11 silly lifecycle<EMAIL_ADDRESS>Returned: code: 1  signal: null
12 info lifecycle<EMAIL_ADDRESS>Failed to exec github-release script
13 verbose stack Error<EMAIL_ADDRESS>github-release: `conventional-github-releaser -p angular`
13 verbose stack Exit status 1
13 verbose stack     at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:280:16)
13 verbose stack     at emitTwo (events.js:125:13)
13 verbose stack     at EventEmitter.emit (events.js:213:7)
13 verbose stack     at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack     at emitTwo (events.js:125:13)
13 verbose stack     at ChildProcess.emit (events.js:213:7)
13 verbose stack     at maybeClose (internal/child_process.js:927:16)
13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)
14 verbose pkgid<EMAIL_ADDRESS>15 verbose cwd /Users/Sammy/Projects/hidsi-web
16 verbose Darwin 16.7.0
17 verbose argv "/usr/local/Cellar/node/8.7.0/bin/node" "/usr/local/bin/npm" "run" "github-release"
18 verbose node v8.7.0
19 verbose npm  v5.5.1
20 error code ELIFECYCLE
21 error errno 1
22 error<EMAIL_ADDRESS>github-release: `conventional-github-releaser -p angular`
22 error Exit status 1

@picosam I can't really tell from the output.
Can you please file a new issue, and let's work through debugging the issue?